That does not look good....you are sure there is a new libc installed? I will have a look at my MintPPC32 system and see which packages will be upgraded.
I had a look at buildd.debian.org and indeed libc6 (built from glibc) has been upgraded to 2.41-12 9 days ago. I would file a bug report in Debian bugs, package glibc. If you install again, don't upgrade until the bug has been fixed.
Changelog:
https://metadata.ftp-master.debian.org/ ... _changelog
I don't dare to upgrade my system...since the release of Trixie, sid has now 250 new packages....I will first make a copy, just in case...
MintPPC
Re: MintPPC
I now see that systemd has also been upgraded. Your error might also come from there. It basically upgrades to the beginning of 'Forky'.
Re: MintPPC
My MintPPC32 upgraded successfully without any errors. I run MintPPC32 at the moment in QEMU, with a PowerPC G4 chip emulation.
Re: MintPPC
PPC G4 has Altivec instructions doesn't it? I think my PowerBook does.
At some point over the weekend I'll start again on a fresh disk and see if it happens on upgrade again or if it was just a random issue.
At some point over the weekend I'll start again on a fresh disk and see if it happens on upgrade again or if it was just a random issue.
Re: MintPPC
So, I did a fresh install and before bothering to get X working (I need to create a manual config) I figured I'd look at the upgrade again. I fixed the mesa issue, then just did a global apt update / upgrade and just hit the same problem again so it wasn't just some random issue. Which is actually sort of nice that it's not just me!
I'm pretty sure this is a problem with libc. Yes, systemd was also updated but the package everything seems to get stuck on seems to be libc.
I get a tonne of these messages during the upgrade - zoom the images below to be able to read them!:
Maybe it's naive of me to think that I can do this, but I have tried to downgrade libc-bin to the last version the log says was installed and it's like libc-bin doesn't exist. So that's probably my understanding of how the packaging works (again, zoom to read):
So at this point I'm a bit stuck. I have a lot of failed packages and seemingly no way to fix them. I need to go out this afternoon which means powering off the machine and will lose the ability to boot the install again.
I'm pretty sure this is a problem with libc. Yes, systemd was also updated but the package everything seems to get stuck on seems to be libc.
I get a tonne of these messages during the upgrade - zoom the images below to be able to read them!:
Re: MintPPC
You can’t just install an older libc, it will break everything.
I am not sure what you have to do. Maybe filing a bug report and wait for a fix before upgrading from a fresh installation?
I am not sure what you have to do. Maybe filing a bug report and wait for a fix before upgrading from a fresh installation?
Re: MintPPC
Add your story here, it seems related:
https://bugs.debian.org/cgi-bin/bugrepo ... ug=1111141
It might be because of systemd only. You could try to downgrade it to stable 257.7-1 and apt hold it for the moment.
http://snapshot.debian.org/binary/systemd/
https://bugs.debian.org/cgi-bin/bugrepo ... ug=1111141
It might be because of systemd only. You could try to downgrade it to stable 257.7-1 and apt hold it for the moment.
http://snapshot.debian.org/binary/systemd/
Re: MintPPC
Quote from that same guy who filed the bug report:
“
sudo apt -t forky install systemd/forky systemd-sysv/forky libpam-systemd/forky udev/forky systemd-container/forky systemd-resolved/forky systemd-timesyncd/forky
solved the issue for me. The additional packages were needed to satisfy
dependencies.”
Forky is the same as Trixie, i.e. 257.7-1.
“
sudo apt -t forky install systemd/forky systemd-sysv/forky libpam-systemd/forky udev/forky systemd-container/forky systemd-resolved/forky systemd-timesyncd/forky
solved the issue for me. The additional packages were needed to satisfy
dependencies.”
Forky is the same as Trixie, i.e. 257.7-1.
Re: MintPPC
Right, I haven't added to the bug report yet as firstly my priority was to regain a working system and also I'd prefer to post something constructive there rather than just a "this happens on powerpc e5500 too", although that would probably still be useful information.
I wasn't able to recover my system, although in hindsight that was my inexperience. With what I know now, I would have been able to via a chroot and a USB stick. So I re-imaged the root partition again, sorted my X config (and backed it up this time!) and got a working desktop. But by its very nature the desktop has automatically gone and run an update of source, so without thinking, when I went to install SDL2 libs systemd got upgraded again because I had forgotten to hold it.
This forced me to add a script to download the required deb files for the old version, apply them with dpkg and then hold them. I won't post it yet as I haven't got the order of dependencies quite right and I need to run it twice. I imagine I can sort that.
That gives me back a bootable system that seems to work fine - although I haven't done much with it yet. With one problem.
I now can't do the Mesa downgrade. It says there's an unmet dependency. I think it's completely unrelated and something else I just haven't got quite right but it's a problem for tonight or another day as I can't spend any more time on it just now. Once I've got it nailed I can share my scripts.
I wasn't able to recover my system, although in hindsight that was my inexperience. With what I know now, I would have been able to via a chroot and a USB stick. So I re-imaged the root partition again, sorted my X config (and backed it up this time!) and got a working desktop. But by its very nature the desktop has automatically gone and run an update of source, so without thinking, when I went to install SDL2 libs systemd got upgraded again because I had forgotten to hold it.
This forced me to add a script to download the required deb files for the old version, apply them with dpkg and then hold them. I won't post it yet as I haven't got the order of dependencies quite right and I need to run it twice. I imagine I can sort that.
That gives me back a bootable system that seems to work fine - although I haven't done much with it yet. With one problem.
I now can't do the Mesa downgrade. It says there's an unmet dependency. I think it's completely unrelated and something else I just haven't got quite right but it's a problem for tonight or another day as I can't spend any more time on it just now. Once I've got it nailed I can share my scripts.
Re: MintPPC
Just a heads-up. This is now fixed upstream so an apt upgrade will no longer break the system.