Temporary blocking of updates, now unblocked
From a clean install this failure can happen. There is a workaround though, when the update fails just re-run it before you reboot. The second update should succeed.
What day you have today in USA ?
Is today Friday in USA ?
I wonder there was "update actualization" window popping up today (in Germany ?).
DirtyAngel Harvey cherry-picked some browser package updates to the Stable repository, see here:
https://discuss.getsol.us/d/10594-sync-updates-for-week-19-2024/31
Applied updates no issues to report (Budgie)
Keep up the great work!
Finally got the courage to update my main work/game PC. No issues or errors at all. Plasma version. Will start updating the rest and let my friends and family know to go ahead and update. Will report how that goes. Some are a couple updates behind, others are up to date. All are Plasma.
- Edited
This is the PC for my entertainment center, Plasma, all AMD. I hadn't updated it for about 3-4 weeks due to not enough sun (live offgrid). Just tried to update.
IInstalling 22 / 422
baselayout-1.9.0-81-1-x86_64.eopkg [cached]
Installing baselayout, version 1.9.0, release 81
Upgrading to new distribution release
Extracting the files of baselayout
[✓] Syncing filesystems success
[✗] Updating clr-boot-manager failed
A copy of the command output follows:
[FATAL] cbm (../src/bootman/bootman.c:L560): FATAL: Cannot mount boot device /dev/nvme0n1p1 on /boot: No such device
[✓] Updating hwdb success
[✓] Updating system users success
[✓] Updating systemd tmpfiles success
[✓] Reloading systemd configuration success
[✓] Re-starting vendor-enabled .socket units success
[✓] Re-executing systemd success
[✓] Compiling glib-schemas success
[✓] Creating GIO modules cache success
[✓] Updating manpages database success
[✓] Updating SSL certificates success
[✓] Reloading udev rules success
[✓] Applying udev rules success
System error. Program terminated.
[Errno 2] No such file or directory: 'sbin'
Please use 'eopkg help' for general help.
Use --debug to see a traceback.
amdmediabox@amdmediabox ~ $ sudo eopkg ur && sudo eopkg up -y
[sudo] password for amdmediabox:
Traceback (most recent call last):
File "/usr/bin/eopkg", line 19, in <module>
import pisi
File "/usr/lib/python2.7/site-packages/pisi/init.py", line 51, in <module>
import pisi.api
File "/usr/lib/python2.7/site-packages/pisi/api.py", line 31, in <module>
import pisi.index
File "/usr/lib/python2.7/site-packages/pisi/index.py", line 32, in <module>
import pisi.operations.build
File "/usr/lib/python2.7/site-packages/pisi/operations/build.py", line 44, in <module>
import magic
File "/usr/lib/python2.7/site-packages/magic/init.py", line 209, in <module>
libmagic = loader.load_lib()
File "/usr/lib/python2.7/site-packages/magic/loader.py", line 49, in load_lib
raise ImportError('failed to find libmagic. Check your installation')
ImportError: failed to find libmagic. Check your installation
!<
Used this and it is now updating again:
/usr/bin/wget https://packages.getsol.us/unstable/e/eopkg4-bin/eopkg4-bin-4.0.0-17-1-x86_64.eopkg
/usr/bin/unzip eopkg4-bin-4.0.0-17-1-x86_64.eopkg
/usr/bin/tar xf install.tar.xz
sudo ./usr/bin/eopkg4-bin upHad to also use sudo eopkg update-repo --force to update my pickle.
Rebooted, seems to be working fine.
Did the wife's laptop, same as mine, had not been updated in a month. 0 issues.
We just made some additional changes that will make it so that PCs that were behind on updates should now be able to update reliably. Note that this will not appear as a new update for anyone who has already updated.
This issue should now be completely resolved.
ReillyBrogan Awesome. I'm updating my friends and family network tomorrow remotely, just in case... Will post if I run into any issues. Very much appreciate everyone's help in getting a solution out so quickly!
ReillyBrogan Just finished updating 3 PC and 2 laptops, only have 1 friends PC left to do, and have had 0 issues. Thank you again for all the help, you guys do fantastic work.
- Edited
Hi everyone! Sorry but yesterday I have faced the same problem, and being unable to recovery, used to do the eopkg trick and I was able to update, but I am still unable to get it boot.
When I run the clr-boot update I get the "No kernels detected on system to update".
And still the installed package manager gets the following error :
Traceback (most recent call last):
File "/usr/bin/eopkg", line 19, in <module>
import pisi
ImportError: No module named pisi
jacojacker I have managed to fix it by running the eopkg check oneliner, but I am still unable to reach to the login screen.
sep 29 14:10:25 jaco systemd[1]: Reached target sound.target - Sound Card.
sep 29 14:10:25 jaco cupsd[1008]: Printer drivers are deprecated and will stop working in a future version of CUPS. See https://github.com/OpenPrinting/cups/issues/103
systemd[1]: Started cups.service - CUPS Scheduler.
systemd[1]: Started cups-browsed.service - Make remote CUPS printers available locally.
ystemd-logind[1010]: Failed to connect to system bus: No such file or directory
systemd-logind[1010]: Failed to fully start up daemon: No such file or directory
systemd[1]: systemd-logind.service: Main process exited, code=exited, status=1/FAILURE
systemd[1]: systemd-logind.service: Failed with result 'exit-code'.
systemd[1]: Failed to start systemd-logind.service - User Login Management.
^ these two should probably be moved to the Friday Sync post