You are not logged in.
hi, i'm running into big troubles due to glibc 2.33. i did not update to 2.33 because firejail won't work properly.
after applying today's pacman-5.2.2 update i can't update/downgrade/remove/install anything with pacman.
sudo pacman -Syu
pacman: /usr/lib/libc.so.6: version `GLIBC_2.33' not found (required by pacman)
pacman: /usr/lib/libc.so.6: version `GLIBC_2.33' not found (required by /usr/lib/libalpm.so.12)
i tried to arch-chroot (the mounted system) but no succes, same errors, and now i'm not sure how to downgrade pacman using pacstrap.
i don't want to crash my arch so i'm asking to avoid mistakes.
jim
Last edited by jim002 (2021-02-09 21:11:37)
Offline
This is your third thread on what amounts to be the same issue. You shouldn't break your system due to a not yet correct firejail configuration that you were guided on how to fix properly in your earlier thread.
Since you now see a perfect and close to worst case scenario of https://wiki.archlinux.org/index.php/Sy … nsupported you should stop thinking about downgrading your system or packages (as you'd need to go hard and FREEZE EVERYTHING on a date before glibc 2.33) or just fix the one thing that got broken with a patch.
To fix this in this case use pacman -Syu --sysroot or pacstrap to upgrade your system. Stop thinking about downgrading, it will end badly, update everything, go back to your earlier thread and fix firejail.
Last edited by V1del (2021-02-09 15:24:12)
Offline
yes, you are absolutely right. no good idea. lesson learned. if I had known the consequences, I would not have tried to ...
--root does not work.
sudo pacman -Syu --root
pacman: /usr/lib/libc.so.6: version `GLIBC_2.33' not found (required by pacman)
pacman: /usr/lib/libc.so.6: version `GLIBC_2.33' not found (required by /usr/lib/libalpm.so.12)
how to upgrade with pacstrap? i can't find a hint in archwiki.
i need old pacman 5.2.1 back and would install the updates first (glibc,gcc,gcc-libs,udisks2) and at last update pacman to 5.2.2.
something like this ???
[root@archiso /] pacstrap -U /mnt/var/cache/pacman/pkg/pacman-5.2.1-6-x86_64.pkg.tar.zst /mnt
note: arch-chroot does not work anymore and i'm using an old install media.
Last edited by jim002 (2021-02-09 11:07:08)
Offline
https://wiki.archlinux.org/index.php/Pa … an_upgrade
Use the --sysroot approach, don't even think about chrooting somewhere.
Edit: https://bbs.archlinux.org/viewtopic.php … 9#p1948359
Last edited by seth (2021-02-09 14:11:51)
Online
thank you, but your EDIT is crap. i'm no native speaker and just read 'SuperTurboTurkey in JailOffice'.
Pacman crashes during an upgrade:
i don't understand
3. Mount the proc, sys and dev filesystems as well: mount -t proc proc /mnt/proc; mount --rbind /sys /mnt/sys; mount --rbind /dev /mnt/dev
if i mount /dev/mapper/root /mnt then the directories /mnt/proc, /mnt/sys/ and /mnt/dev are existing and in use already.
shall i follow this without any reservation?
and how to upgrade with pacstrap as mentionrd above?
Offline
If you just mounted /dev/mapper/root to /mnt then /mnt/proc, /mnt/sys/ and /mnt/dev should all now exist as you just mounted the root file-system but how can they already be in use?
Edit:
What is the output of:
findmnt /mnt
findmnt /mnt/proc
findmnt /mnt/sys
findmnt /mnt/dev
Last edited by loqs (2021-02-09 15:25:43)
Offline
it's confusing. even your question. all i need is pacman 5.2.1. what to do now and how to do it with pacstrap? would
pacstrap /mnt glibc gcc gcc-libs udisks2 pacman
overwrite existing pkgs and work after the reboot?
Last edited by jim002 (2021-02-09 15:29:03)
Offline
As it is unclear what is mounted to /mnt I do not know what the result of executing any command on that directory would be.
Edit:
Please provide the output requested from post #6.
Last edited by loqs (2021-02-09 15:32:04)
Offline
That should afaik be possible, but I haven't had a need to do that so I might be off here. Properly using --sysroot is definitely the "more proper" way of doing this, and I'm not sure what's this different on your system that the linked instructions wouldn't work on your system.
FWIW if I'm reading your correctly, you are wondering whether it's normal that these directories are present after the mount of the root partition to /mnt? Yes that's normal, and they will likely all be empty, and even if they weren't, mounting the live systems files over them temporarily is safe regardless.
Offline
cryptsetup luksOpen /dev/sdaX root
mount /dev/mapper/root /mnt
mount /dev/sdaY /mnt/boot
1 root, 1 boot partition, no home and no swap partition
ok, 'mounting over' is safe.
the output of findmnt /mnt is empty maybe because i'm not on root@archiso but still using this damaged arch. till now it works properly but can't update/downgrade.
Last edited by jim002 (2021-02-09 15:44:15)
Offline
Then you need to mount the pseudo file-systems
mount -t proc proc /mnt/proc
mount --rbind /sys /mnt/sys
mount --rbind /dev /mnt/dev
Offline
You are not mounting over anything.
findmnt /mnt/proc
If it produces no output, nothing is mounted there.
Last edited by loqs (2021-02-09 15:42:16)
Offline
i tried to follow the --sysroot instructions using a recent media and the additional mount options
but ran into (expected) troubles with my ethernet and could not retrieve any packages (broadcom - tg3).
looking for another method i found this to install from local directory: https://bbs.archlinux.org/viewtopic.php … 4#p1889404
it worked because i just had to update the downgraded packages and pacman selects the latest version by default:
[root@archiso / ] pacman --root /mnt --cachedir=/mnt/var/cache/pacman/pkg -S glibc gcc gcc-libs udisks2
thanks for your help,
jim
Offline