Arch Linux

7761 readers

15 users here now

The beloved lightweight distro

founded 4 years ago

MODERATORS

k_o_t@lemmy.ml

Error with recent deepin-icon-theme update, how should I address this? (lemmy.ml)

submitted 1 month ago by christian@lemmy.ml to c/archlinux@lemmy.ml

3 comments fedilink hide all child comments

:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...

Packages (1) deepin-icon-theme-2024.06.21-1

Total Installed Size:  138.93 MiB
Net Upgrade Size:        5.96 MiB

:: Proceed with installation? [Y/n] Y
(1/1) checking keys in keyring                     [########################] 100%
(1/1) checking package integrity                   [########################] 100%
(1/1) loading package files                        [########################] 100%
(1/1) checking for file conflicts                  [########################] 100%
error: failed to commit transaction (conflicting files)
deepin-icon-theme: /usr/share/icons/bloom/icon-theme.cache exists in filesystem
Errors occurred, no packages were upgraded.

Running a search for the error I didn't find one for deepin-icon-theme, but the same error for other packages in arch updates show up and the other ones I saw laid the blame on improper packaging. Given that this is the one from the arch repositories and not some AUR package, I'm nowhere near confident enough in myself to jump to the conclusion that this is someone else's fault, so I'm asking here.

top 3 comments

sorted by: hot top controversial new old

[–] Gyroplast@pawb.social 4 points 1 month ago* (last edited 1 month ago) (1 children)

Delete the existing file /usr/share/icons/bloom/icon-theme.cache, install the package normally without forcing, and don't sweat it. That cache can (and should automatically) be recreated afterwards with gtk4-update-icon-cache /usr/share/icons/bloom, but it's strictly not critical.

The previous version of the package did not include this file, lending credibility to the assumption of a packaging mistake, as does the existence of an issue for that problem already.

Just fix this nag yourself as described, and expect this to be fixed by the packager eventually.

[–] christian@lemmy.ml 2 points 1 month ago

Thanks!

[–] Strit@lemmy.linuxuserspace.show 2 points 1 month ago

Was fixed in 2024.06.21-2.