You are not logged in.

#1 2022-12-03 17:13:28

gabx
Member
From: Geneva, Switzerland
Registered: 2011-11-20
Posts: 135
Website

issue upgrading systemd: files already exist in filesystem [SOLVED]

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

#2 2022-12-03 17:17:06

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 29,521
Website

Re: issue upgrading systemd: files already exist in filesystem [SOLVED]

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

#3 2022-12-03 17:53:27

seth
Member
Registered: 2012-09-03
Posts: 50,981

Re: issue upgrading systemd: files already exist in filesystem [SOLVED]

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

#4 2022-12-03 17:56:54

gabx
Member
From: Geneva, Switzerland
Registered: 2011-11-20
Posts: 135
Website

Re: issue upgrading systemd: files already exist in filesystem [SOLVED]

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

#5 2022-12-04 05:50:37

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 7,132

Re: issue upgrading systemd: files already exist in filesystem [SOLVED]

gabx wrote:

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

#6 2022-12-04 18:06:16

gabx
Member
From: Geneva, Switzerland
Registered: 2011-11-20
Posts: 135
Website

Re: issue upgrading systemd: files already exist in filesystem [SOLVED]

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

#7 2022-12-04 18:15:46

seth
Member
Registered: 2012-09-03
Posts: 50,981

Offline

#8 2022-12-04 18:28:20

gabx
Member
From: Geneva, Switzerland
Registered: 2011-11-20
Posts: 135
Website

Re: issue upgrading systemd: files already exist in filesystem [SOLVED]

seth wrote:

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

#9 2022-12-04 19:05:35

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 7,132

Re: issue upgrading systemd: files already exist in filesystem [SOLVED]

gabx wrote:

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

#10 2022-12-04 23:04:23

gabx
Member
From: Geneva, Switzerland
Registered: 2011-11-20
Posts: 135
Website

Re: issue upgrading systemd: files already exist in filesystem [SOLVED]

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

Board footer

Powered by FluxBB