Forum › Forums › New users › New Users and General Questions › [SOLVED]: Synaptic upgrade broken
- This topic has 5 replies, 4 voices, and was last updated May 2-6:57 am by antique23.
-
AuthorPosts
-
May 1, 2023 at 11:46 pm #105800Member
antique23
It well may be my mistake because after engaging the test repo (which I’ve now disengaged) I blindly then did an upgrade. All seemed ok until next reboot when now I can’t seek updates or upgrades. My QSI is hereunder and I provide this info from the CLI when trying to update ….
apt: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32′ not found (required by /lib/x86_64-linux-gnu/libapt-pkg.so.6.0)
apt: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34′ not found (required by /lib/x86_64-linux-gnu/libapt-pkg.so.6.0)
apt: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33′ not found (required by /lib/x86_64-linux-gnu/libapt-pkg.so.6.0)
apt: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29′ not found (required by /lib/x86_64-linux-gnu/libapt-pkg.so.6.0)
====
I am new to antiX and had not yet implemented Timeshift nor any other form of backup so reverting to an earlier state is sadly not an option. If I have to reinstall, it won’t be too onerous but I’d prefer not to have to so if anyone can suggest a solution I’d be grateful.- This topic was modified 6 days, 22 hours ago by Brian Masinick. Reason: SOLVED
Attachments:
May 2, 2023 at 12:22 am #105807Moderator
christophe
::I think you are probably right about the cause. If it were my situation, I’d reinstall, unless someone else here knows how to guide you.
confirmed antiX frugaler, since 2019
May 2, 2023 at 4:58 am #105809Memberantique23
::Thanks christophe. I hope someone like anticapitalista or dolphin oracle might chime in but I am guessing you are on the right track and a reinstall will be what will fix it. I know I violated the long run golden rule of not blindly allowing updates especially from the test repo but I was keen to get the latest and (perhaps not) greatest installed into what is a great distro. I should have at least had a Timeshift and snapshot backup but alas I didn’t. Anyway, I’m not too far into tweaking and configuring the distro to my liking so a reinstall won’t be too problematic.
May 2, 2023 at 6:51 am #105812MemberRJP
::It well may be my mistake because after engaging the test repo (which I’ve now disengaged) I blindly then did an upgrade. All seemed ok until next reboot when now I can’t seek updates or upgrades. My QSI is hereunder and I provide this info from the CLI when trying to update ….
apt: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32′ not found (required by /lib/x86_64-linux-gnu/libapt-pkg.so.6.0)
apt: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34′ not found (required by /lib/x86_64-linux-gnu/libapt-pkg.so.6.0)
apt: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33′ not found (required by /lib/x86_64-linux-gnu/libapt-pkg.so.6.0)
apt: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29′ not found (required by /lib/x86_64-linux-gnu/libapt-pkg.so.6.0)
====
I am new to antiX and had not yet implemented Timeshift nor any other form of backup so reverting to an earlier state is sadly not an option. If I have to reinstall, it won’t be too onerous but I’d prefer not to have to so if anyone can suggest a solution I’d be grateful.I suppose that you can copy those files to your installed system from live-USB using root rox-filer or zzzFM.
May 2, 2023 at 6:56 am #105813MemberRobin
::There is a slight chance to rescue your existing system:
1.) Restore apt functionallity first. You’ll need to manually download the apt version matching your libc6 version present on your system currently. Since version 2.32 and above wasn’t found, I guess you run still the default antiX 21/22 libc6 version 2.31-13+deb11u5. Hence try reinstalling the default antiX 22 apt version, 64bit, since your system is 64bit according to your inxi output. This will hopefully make apt work again:
$ wget 'https://mirror.23media.com/mx-packages/antix/bullseye/pool/nosystemd/a/apt/apt_2.2.4.0nosystemd1_amd64.deb' $ sudo dpkg -i './apt_2.2.4.0nosystemd1_amd64.deb'Check whether apt works again:
$ apt list --installedOnly if apt works fine (if not, let me see its error output), proceed:
2.) Make absolutely sure to manually set the proper repos in all your /etc/apt/sources.list.d/… files now.
3.) Run the commands:
$ sudo su # apt-get clean # apt-get update # apt list --installed | tail -n +1 | cut --delimiter=/ --fields=1 | xargs apt-get --allow-downgrades --reinstall --assume-yes install # apt-get install --fix-broken # apt-get autoremoveThe commands above do the following:
1. make yourself root for the following commands within the very terminal window.
2. delete all cached package copies existing on your system, so everything will be freshly downloaded from the mirrors
3. update the local apt database
4. enforce reinstall all packages living on your system, some of them might get downgraded from currently wrong version back to antiX22 default.
5. fix any broken left over installs
6. make sure no unneeded packages are still on your systemThis might save you, but it also might not restore your broken system functional. So only apply it once you are about to completely reinstall antiX from scratch anyway, in this moment you might want to give it a try. No guarantee it will work on your system, just understand it as an experiment, and smile if you succeed.
Windows is like a submarine. Open a window and serious problems will start.
May 2, 2023 at 6:57 am #105814Memberantique23
::Yes thanks RJP, however, after contemplating using the liveusb route, I actually reinstalled (via a liveusb) the distro again. Now all I have to do is retrace the various tweaks I originally did. Fortunately, I didn’t have any needed documents etc in the original install as I am still only exploring all the things in antiX. If I could mark this thread solved I would but I suppose this reply will serve the same purpose.
-
AuthorPosts
- You must be logged in to reply to this topic.