Running into a couple of issues while trying to update using yay

General system Newbie
1

I’ve been using endeavour for a couple of years now with virtually no issues. However, I went to update my system today by running yay and there is a core package icu that runs into an issue:

:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: installing icu (75.1-1) breaks dependency 'libicui18n.so=74-64' required by electron27
:: installing icu (75.1-1) breaks dependency 'libicuuc.so=74-64' required by electron27
:: installing icu (75.1-1) breaks dependency 'libicui18n.so=74-64' required by electron28
:: installing icu (75.1-1) breaks dependency 'libicuuc.so=74-64' required by electron28
:: installing icu (75.1-1) breaks dependency 'libicui18n.so=74-64' required by electron29
:: installing icu (75.1-1) breaks dependency 'libicuuc.so=74-64' required by electron29
:: installing icu (75.1-1) breaks dependency 'libicui18n.so=74-64' required by electron30
:: installing icu (75.1-1) breaks dependency 'libicuuc.so=74-64' required by electron30
:: installing icu (75.1-1) breaks dependency 'libicuuc.so=74-64' required by gspell
:: installing icu (75.1-1) breaks dependency 'libicuuc.so=74-64' required by harfbuzz-icu
:: installing icu (75.1-1) breaks dependency 'libicuuc.so=74-64' required by raptor
 -> error installing repo packages

Another package qqc2-desktop-style5 won’t update either. I get this error:

error: failed to commit transaction (conflicting files)
qqc2-desktop-style5: /usr/share/locale/ca/LC_MESSAGES/qqc2desktopstyle_qt.qm exists in filesystem (owned by qqc2-desktop-style)
qqc2-desktop-style5: /usr/share/locale/ca@valencia/LC_MESSAGES/qqc2desktopstyle_qt.qm exists in filesystem (owned by qqc2-desktop-style)
qqc2-desktop-style5: /usr/share/locale/cs/LC_MESSAGES/qqc2desktopstyle_qt.qm exists in filesystem (owned by qqc2-desktop-style)
qqc2-desktop-style5: /usr/share/locale/de/LC_MESSAGES/qqc2desktopstyle_qt.qm exists in filesystem (owned by qqc2-desktop-style)
qqc2-desktop-style5: /usr/share/locale/es/LC_MESSAGES/qqc2desktopstyle_qt.qm exists in filesystem (owned by qqc2-desktop-style)
qqc2-desktop-style5: /usr/share/locale/fr/LC_MESSAGES/qqc2desktopstyle_qt.qm exists in filesystem (owned by qqc2-desktop-style)
qqc2-desktop-style5: /usr/share/locale/it/LC_MESSAGES/qqc2desktopstyle_qt.qm exists in filesystem (owned by qqc2-desktop-style)
qqc2-desktop-style5: /usr/share/locale/nl/LC_MESSAGES/qqc2desktopstyle_qt.qm exists in filesystem (owned by qqc2-desktop-style)
qqc2-desktop-style5: /usr/share/locale/sl/LC_MESSAGES/qqc2desktopstyle_qt.qm exists in filesystem (owned by qqc2-desktop-style)
qqc2-desktop-style5: /usr/share/locale/tr/LC_MESSAGES/qqc2desktopstyle_qt.qm exists in filesystem (owned by qqc2-desktop-style)
qqc2-desktop-style5: /usr/share/locale/uk/LC_MESSAGES/qqc2desktopstyle_qt.qm exists in filesystem (owned by qqc2-desktop-style)
qqc2-desktop-style5: /usr/share/locale/zh_CN/LC_MESSAGES/qqc2desktopstyle_qt.qm exists in filesystem (owned by qqc2-desktop-style)
qqc2-desktop-style5: /usr/share/locale/zh_TW/LC_MESSAGES/qqc2desktopstyle_qt.qm exists in filesystem (owned by qqc2-desktop-style)
Errors occurred, no packages were upgraded.
 -> error installing repo packages

Not sure how I can go about fixing these issues. Would it be safe for me to ignore these two packages and update everything else for the time being? These are the list of updates I have available:

:: 68 packages to upgrade/install.
68  core/icu                     74.2-2      -> 75.1-1
67  core/libxml2                 2.12.6-2    -> 2.12.7-1
66  core/xfsprogs                6.7.0-1     -> 6.8.0-2
65  extra/attica5                5.115.0-1   -> 5.116.0-1
64  extra/bluez-qt5              5.115.0-1   -> 5.116.0-1
63  extra/frameworkintegration5  5.115.0-1   -> 5.116.0-1
62  extra/glances                3.4.0.5-3   -> 4.0.5-1
61  extra/kactivities-stats5     5.115.0-1   -> 5.116.0-1
60  extra/kactivities5           5.115.0-1   -> 5.116.0-1
59  extra/karchive5              5.115.0-1   -> 5.116.0-1
58  extra/kauth5                 5.115.0-1   -> 5.116.0-1
57  extra/kbookmarks5            5.115.0-1   -> 5.116.0-1
56  extra/kcmutils5              5.115.0-1   -> 5.116.0-1
55  extra/kcodecs5               5.115.0-1   -> 5.116.0-1
54  extra/kcompletion5           5.115.0-1   -> 5.116.0-1
53  extra/kconfig5               5.115.0-1   -> 5.116.0-1
52  extra/kconfigwidgets5        5.115.0-1   -> 5.116.0-1
51  extra/kcontacts5             5.115.0-1   -> 5.116.0-1
50  extra/kcoreaddons5           5.115.0-1   -> 5.116.0-1
49  extra/kcrash5                5.115.0-1   -> 5.116.0-1
48  extra/kdbusaddons5           5.115.0-1   -> 5.116.0-1
47  extra/kdeclarative5          5.115.0-1   -> 5.116.0-1
46  extra/kded5                  5.115.0-1   -> 5.116.0-1
45  extra/kdelibs4support        5.115.0-1   -> 5.116.0-1
44  extra/kdesu5                 5.115.0-1   -> 5.116.0-1
43  extra/kdnssd5                5.115.0-1   -> 5.116.0-1
42  extra/kemoticons             5.115.0-1   -> 5.116.0-1
41  extra/kfilemetadata5         5.115.0-1   -> 5.116.0-1
40  extra/kglobalaccel5          5.115.0-3   -> 5.116.0-1
39  extra/kguiaddons5            5.115.0-2   -> 5.116.0-1
38  extra/kholidays5             1:5.115.0-1 -> 1:5.116.0-1
37  extra/ki18n5                 5.115.1-1   -> 5.116.0-1
36  extra/kiconthemes5           5.115.0-1   -> 5.116.0-1
35  extra/kidletime5             5.115.0-1   -> 5.116.0-1
34  extra/kimageformats5         5.115.0-2   -> 5.116.0-1
33  extra/kinit                  5.115.0-1   -> 5.116.0-1
32  extra/kio5                   5.115.0-3   -> 5.116.0-1
31  extra/kirigami2              5.115.0-1   -> 5.116.0-1
30  extra/kitemmodels5           5.115.0-1   -> 5.116.0-1
29  extra/kitemviews5            5.115.0-1   -> 5.116.0-1
28  extra/kjobwidgets5           5.115.0-1   -> 5.116.0-1
27  extra/knewstuff5             5.115.0-1   -> 5.116.0-1
26  extra/knotifications5        5.115.0-1   -> 5.116.0-1
25  extra/knotifyconfig5         5.115.0-1   -> 5.116.0-1
24  extra/kpackage5              5.115.0-1   -> 5.116.0-1
23  extra/kparts5                5.115.0-1   -> 5.116.0-1
22  extra/kpeople5               5.115.0-1   -> 5.116.0-1
21  extra/kpty5                  5.115.0-1   -> 5.116.0-1
20  extra/kservice5              5.115.0-2   -> 5.116.0-1
19  extra/ktexteditor5           5.115.0-1   -> 5.116.0-1
18  extra/ktextwidgets5          5.115.0-1   -> 5.116.0-1
17  extra/kunitconversion5       5.115.0-1   -> 5.116.0-1
16  extra/kwallet5               5.115.0-2   -> 5.116.0-1
15  extra/kwayland5              5.115.0-1   -> 5.116.0-1
14  extra/kwidgetsaddons5        5.115.0-1   -> 5.116.0-1
13  extra/kwindowsystem5         5.115.0-1   -> 5.116.0-1
12  extra/kxmlgui5               5.115.0-1   -> 5.116.0-1
11  extra/modemmanager-qt5       5.115.0-1   -> 5.116.0-1
10  extra/networkmanager-qt5     5.115.0-1   -> 5.116.0-1
 9  extra/plasma-framework5      5.115.0-3   -> 5.116.0-1
 8  extra/prison5                5.115.0-1   -> 5.116.0-1
 7  extra/purpose5               5.115.0-3   -> 5.116.0-1
 6  extra/qqc2-desktop-style5    5.115.0-1   -> 5.116.0-1
 5  extra/solid5                 5.115.0-1   -> 5.116.0-1
 4  extra/sonnet5                5.115.0-1   -> 5.116.0-1
 3  extra/syndication5           5.115.0-1   -> 5.116.0-1
 2  extra/syntax-highlighting5   5.115.0-2   -> 5.116.0-1
 1  extra/threadweaver5          5.115.0-1   -> 5.116.0-1
2

No, you should never do that. It is called a partial update and can result in broken system. Either update all of your repo packages or none of them.

That looks to me like something may be wrong with that mirror or it is partially updated. Try re-sorting your mirrors and see if that fixes the issue.

3

As @dalto said , re-rate your mirrors and use sudo pacman -Syyu instead of yay . I have had also run into the same issues as yours in the past usually due to un-updated mirrors and stale .db(s) .

4

Just updated the mirrors and I’m still running into the same issues.

5

Running sudo pacman -Syyu gives me the same error unfortunately.

6

Maybe you got reconnected to the same mirror. Try commenting out the first mirror on your mirrorlist.

7

Try inserting this in the very first lines of your /etc/pacman.d/mirrorlist file:

Server = https://geo.mirror.pkgbuild.com/$repo/os/$arch
Server = https://mirror.onet.pl/pub/mirrors/archlinux/$repo/os/$arch
Server = https://mirror.rackspace.com/archlinux/$repo/os/$arch

8

I commented out the first mirror, but it still runs into the icu dependency issue

9

Doing this gives me:

error: failed retrieving file 'endeavouros.db' from geo.mirror.pkgbuild.com : The requested URL returned error: 404
error: failed retrieving file 'endeavouros.db' from mirror.onet.pl : The requested URL returned error: 404
error: failed retrieving file 'endeavouros.db' from mirror.rackspace.com : The requested URL returned error: 404

Nevermind, as @dalto pointed out, I foolishly input the lines into the wrong file. This method worked and I was able to update my system. The qqc2-desktop-style5 package still gave me the error, but I removed it since I already had another qqc2-desktop-style package installed. I assumed it was left over from plasma 5. Removed it and I haven’t run into any issues. Thanks!

1 Like
10

I have same issue. Removed the package yay -Rs qqc2-desktop-style5 and updated my system. When the package conflict is resolved, then I will reinstall it back. It’s just this package, nothing else got removed. Don’t know if this is recommended though.

11

You put the lines in the wrong file.

12

I’m in Canada and was having the same issue. What I did is:

Open /etc/etc/pacman.d/mirrorlist in a text editor
Comment out the first mirror #Server = https://mirror.accuris.ca/archlinux/$repo/os/$arch
Then run sudo pacman -Syyu

I’m not super familiar with EndeavourOS yet but I no longer have errors

14

Wow, I’m dumb. Thanks, that worked!

15

I would recommend to use the reflector-simple program each time a issue like this occurs. Select the worldwide mirror and your country of residence mirror in such issues. Hope you enjoy Archlinux/EndeavourOS as much as we all do !

3 Likes
16

I still have this issue even after re-rating my mirrors, any help? I am in the UK if that affects anything

17

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.