Open Aleksa2022 opened 4 months ago
The xargs thing is just a warning. Here is my current work. It is incomplete. I have gone through core and opt. Moved a few things, but this is a good foothold on the next iteration. https://github.com/Thinstation/WIP On Saturday, March 9, 2024 at 04:53:09 AM MST, Alesandro @.***> wrote:
After updating the ports, I decided to try a rollup (environment cleanup - ./setup-root -c). The cleanup went through without any errors, but when I tried to deploy again, I got an error: /bin/bash: error while loading shared libraries: libreadline.so.8: cannot open shared object file: No such file or directory I have updated, including bash and readline. I have checked the availability of libraries - they are there and there are links for them. I tried to overwrite components and references - nothing changed. During the cleanup, there were quite a few messages: xargs: warning: options --max-args and --replace/-I/-i are mutually exclusive, ignoring previous --max-args value I suppose something could have gone wrong at this stage: Cleaning tools There were some strange messages too: Cleaning lzip =======> Removing /ts/ports/components/lshw/lshw-B.02.20.tar.gz Cleaning fribidi =======> Removing /ts/ports/contrib/ffmpeg/ffmpeg-5.1.4.tar.bz2 Cleaning wgetpaste =======> Removing /ts/ports/contrib/usb_modeswitch/usb-modeswitch-2.6.0.tar.bz2 =======> Removing /ts/ports/contrib/usb_modeswitch/usb-modeswitch-data-20191128.tar.bz2 Cleaning coreutils =======> Removing /ts/ports/core/bison/bison/bison-3.8.2.tar.xz Cleaning cpio =======> Removing /ts/ports/core/coreutils/coreutils-8.32.tar.xz Cleaning dhcpcd =======> Removing /ts/ports/core/curl/curl/curl-8.6.0.tar.bz2 Cleaning rtl8821ce =======> Removing /ts/ports/kernel-modules/kernel-TS/linux-6.1.80.tar.xz Cleaning was obviously not what was planned.
It's not clear what and where might have gone astray that started working incorrectly? How can this be corrected?
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: @.***>
I'll have to check out that beachhead sometime. I haven't figured out git yet, so I didn't try to upload anything to avoid breaking anything inadvertently. I've updated quite a few ports, so I thought I'd attach the result of my walkthrough here. The archive contains a collection of pkgfiles (updated and not) - just a copy of the main directory structure. There is also a file "versions", which simply lists the versions of ports from the Pkgfiles directory. The "diff_between_git_and_Updated" file lists the differences with the catalog from git. Maybe this will help speed up TS updates :-). I will note separately that not all port versions are up to date, as not a few ports have switched to other build methods - from "./configure" script to "meson build". I updated to the latest versions, which were built either with minimal changes in the build algorithm or without any changes at all (I tried to stick to this option). First of all, this was done because not a few ports are very outdated - from 2019 and younger. And fonts - in general, the latest versions are from 2010, and there are already from 2023. In general, my goal was just to update the system as much as I can. All ports are installed on my system and the image build goes smoothly. The only problem I encountered was a problem with clearing the chroot environment.... Pkgfiles.zip
After updating the ports, I decided to try a rollup (environment cleanup - ./setup-root -c). The cleanup went through without any errors, but when I tried to deploy again, I got an error: /bin/bash: error while loading shared libraries: libreadline.so.8: cannot open shared object file: No such file or directory I have updated, including bash and readline. I have checked the availability of libraries - they are there and there are links for them. I tried to overwrite components and references - nothing changed. During the cleanup, there were quite a few messages:
xargs: warning: options --max-args and --replace/-I/-i are mutually exclusive, ignoring previous --max-args value
I suppose something could have gone wrong at this stage:Cleaning tools
There were some strange messages too:It's not clear what and where might have gone astray that started working incorrectly? How can this be corrected?