You are not logged in.
I first post this issue about UEFI boot broken. Thanks to one answer, it seems there has been an issue with systemd-boot 252.1, which is now solved.
I chrooted my Arch system and want to upgrade systemd-252.1 to systemd-252.2. When running pacman, 76 packages have to be updated.If I say Yes to proceed with installation, I get a huge list of files which exists in filesystem and no packages were upgraded.
I need this systemd-boot upgrade to be able to boot again my system but don't know how to deal with all these already existing files. They are much too many to remove them by hand. It is the first time I see so many existing files.
Can anyone gimme some advice about this upgrade? Thank you
Last edited by gabx (2022-12-04 23:05:16)
Offline
What are the files? There should be no need to remove them "by hand":
https://wiki.archlinux.org/title/Pacman … )%22_error
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
Depending on where those files belong, the package database might have taken a hit (interrupted previous update?)
Installing those packages first "--dbonly" might fix that, the actual pacman output should provide more insight into what's going on.
Offline
The list is very long and files belong to systemd, pcre2, util-linux,file,shadow,libseccomp,libelf,curl,libssh2 etc packages. Renaming/removing by hand would takes me too much time.
I honestly never saw such a long list. Anything to do with the fact I am chrooting my Arch system?
Last edited by gabx (2022-12-03 18:02:00)
Offline
Can anyone gimme some advice about this upgrade? Thank you
https://bbs.archlinux.org/viewtopic.php … 9#p2071629
[But hopefully seth is right ....]
Last edited by cfr (2022-12-04 05:52:01)
CLI Paste | How To Ask Questions
Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L
Offline
Yes it seems I have an issue with my pacman DB, and potentially my /var partition which is on a BTRFS subvolume.
When I chroot in my Arch system, I have few weird behaviors:
$ pacman -Q
----> return nothing
# pacman -Syu
....
there is nothing to do
# pacman -Syu systemd
.....
Packages (76)
The above command returns show clearly there is an issue with pacman DB. I need to understand why and my systemd upgrade issue shall be solved
Offline
Offline
Depending on where those files belong, the package database might have taken a hit (interrupted previous update?)
Installing those packages first "--dbonly" might fix that, the actual pacman output should provide more insight into what's going on.
What do you mean by Installing those packages first "--dbonly" ?
Offline
What do you mean by Installing those packages first "--dbonly" ?
pacman -Sh
CLI Paste | How To Ask Questions
Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L
Offline
well, I finally realized I was mounting a wrong /var when chrooting my Arch.
My setup is with a separate /var partition on another HD and I totally forgot this setup.Thus the lack of pacman packages listed, with /var/lib/pacman/local being empty.
I have been able to upgrade systemd to solve my systemd-boot issue.
# pacman -S systemd
....
Packages (1) systemd-252.2-3
....
I couldn't figure out why my pacman was so messy as it has been working perfectly well for long, so I feel much better now.
Thank you for your answers
Last edited by gabx (2022-12-04 23:06:42)
Offline