ICU 76.1.1 Issue [SOLVED]

egayghost · 2025-02-20 12:42:29

Hi, while I was trying to update my system, it showed this message instead

error: failed to prepare transaction (could not satisfy dependencies)
:: installing icu (76.1-1) breaks dependency 'libicui18n.so=75-64' required by electron29
:: installing icu (76.1-1) breaks dependency 'libicuuc.so=75-64' required by electron29

Last edited by egayghost (2025-02-20 12:51:35)

Scimmia · 2025-02-20 12:44:38

electron29 isn't in the repos. Do you need it?

egayghost · 2025-02-20 12:46:53

Scimmia wrote:

electron29 isn't in the repos. Do you need it?

Guess so, I know some of my applications relies on Electron

Scimmia · 2025-02-20 12:49:10

Don't guess, check.

If you do need it, you'll have to rebuild it with a bundled ICU.

egayghost · 2025-02-20 12:51:00

Scimmia wrote:

Don't guess, check.
If you do need it, you'll have to rebuild it with a bundled ICU.

aight, thanks man, will close this now.

WorMzy · 2025-02-20 13:31:31

Mod note: Moving to AUR Issues.

linuxadmin · 2025-02-20 16:20:42

I think it is not AUR issue. Mine shows errors with packages from repo

error: failed to prepare transaction (could not satisfy dependencies)
:: installing icu (76.1-1) breaks dependency 'libicuuc.so=75-64' required by freerdp2
:: installing icu (76.1-1) breaks dependency 'libicuuc.so=75-64' required by gspell
:: installing icu (76.1-1) breaks dependency 'libicuuc.so=75-64' required by harfbuzz-icu
:: installing icu (76.1-1) breaks dependency 'libicuuc.so=75-64' required by raptor
:: installing icu (76.1-1) breaks dependency 'libicui18n.so=75-64' required by thunderbird
:: installing icu (76.1-1) breaks dependency 'libicuuc.so=75-64' required by thunderbird

nachitodev · 2025-02-20 16:54:44

I agree with the last post, i'm not only having errors with Electron29, i'm having errors with a lot of packages from the repo!

(Using ES-ES lang)
error: no se pudo preparar la operación (no se pudieron satisfacer las dependencias)
:: instalando icu (76.1-1) se rompe la dependencia con «libicuuc.so=75-64», necesaria para el paquete brltty
:: instalando icu (76.1-1) se rompe la dependencia con «libicui18n.so=75-64», necesaria para el paquete electron31
:: instalando icu (76.1-1) se rompe la dependencia con «libicuuc.so=75-64», necesaria para el paquete electron31
:: instalando icu (76.1-1) se rompe la dependencia con «libicui18n.so=75-64», necesaria para el paquete electron33
:: instalando icu (76.1-1) se rompe la dependencia con «libicuuc.so=75-64», necesaria para el paquete electron33
:: instalando icu (76.1-1) se rompe la dependencia con «libicui18n.so=75-64», necesaria para el paquete electron34
:: instalando icu (76.1-1) se rompe la dependencia con «libicuuc.so=75-64», necesaria para el paquete electron34
:: instalando icu (76.1-1) se rompe la dependencia con «libicuuc.so=75-64», necesaria para el paquete freerdp2
:: instalando icu (76.1-1) se rompe la dependencia con «libicuuc.so=75-64», necesaria para el paquete harfbuzz-icu
:: instalando icu (76.1-1) se rompe la dependencia con «libicui18n.so=75-64», necesaria para el paquete mpd
:: instalando icu (76.1-1) se rompe la dependencia con «libicuuc.so=75-64», necesaria para el paquete mpd
:: instalando icu (76.1-1) se rompe la dependencia con «libicui18n.so=75-64», necesaria para el paquete ncmpcpp
:: instalando icu (76.1-1) se rompe la dependencia con «libicuuc.so=75-64», necesaria para el paquete ncmpcpp
:: instalando icu (76.1-1) se rompe la dependencia con «libicuuc.so=75-64», necesaria para el paquete raptor

Scimmia · 2025-02-20 17:27:40

linuxadmin wrote:

I think it is not AUR issue. Mine shows errors with packages from repo

Because you have completely different, unrelated errors.

Skipple · 2025-02-20 18:25:13

I'm receiving similar error when attempting to update my system. If someone wouldn't mind letting me know how to address, I would be greatful.

:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: installing icu (76.1-1) breaks dependency 'libicui18n.so=75-64' required by electron28
:: installing icu (76.1-1) breaks dependency 'libicuuc.so=75-64' required by electron28
:: installing icu (76.1-1) breaks dependency 'libicui18n.so=75-64' required by electron29
:: installing icu (76.1-1) breaks dependency 'libicuuc.so=75-64' required by electron29
:: installing icu (76.1-1) breaks dependency 'libicui18n.so=75-64' required by electron30
:: installing icu (76.1-1) breaks dependency 'libicuuc.so=75-64' required by electron30

Scimmia · 2025-02-20 18:26:55

Solution was posted in post #2 and #4

mithrial · 2025-02-20 18:27:32

You have to wait until the rebuilds finish and the mirrors are synced.
It will resolve in a couple of hours.

Scimmia · 2025-02-20 18:29:50

mithrial wrote:

You have to wait until the rebuilds finish and the mirrors are synced.
It will resolve in a couple of hours.

Completely false. Rebuilds have been done for days and mirrors syncing has nothing to do with this thread.

Skipple · 2025-02-20 18:30:20

Scimmia wrote:

Solution was posted in post #2 and #4

Forgive me, but the answer is flying over my head. I'm unsure what "rebuild it with a bundled ICU." means.

mithrial wrote:

You have to wait until the rebuilds finish and the mirrors are synced.
It will resolve in a couple of hours.

Thanks, I'll do this.

Scimmia · 2025-02-20 18:31:53

Skipple wrote:

Scimmia wrote:
Solution was posted in post #2 and #4
Forgive me, but the answer is flying over my head. I'm unsure what "rebuild it with a bundled ICU." means.

If the maintainer of the AUR packages in question haven't already made that change, talk to them.

mackin_cheese · 2025-02-20 18:35:34

linuxadmin wrote:

I think it is not AUR issue. Mine shows errors with packages from repo
error: failed to prepare transaction (could not satisfy dependencies)
:: installing icu (76.1-1) breaks dependency 'libicuuc.so=75-64' required by freerdp2
:: installing icu (76.1-1) breaks dependency 'libicuuc.so=75-64' required by gspell
:: installing icu (76.1-1) breaks dependency 'libicuuc.so=75-64' required by harfbuzz-icu
:: installing icu (76.1-1) breaks dependency 'libicuuc.so=75-64' required by raptor
:: installing icu (76.1-1) breaks dependency 'libicui18n.so=75-64' required by thunderbird
:: installing icu (76.1-1) breaks dependency 'libicuuc.so=75-64' required by thunderbird

for the OP it was a aur issue, for you, it's packages in the official repo that are/were out of date, which you would have to flag as out of date. Freerdp2 has been updated, thunderbird hasn't as of yet. Just wait a few but don't ignore the icu update

Scimmia · 2025-02-20 18:38:47

mackin_cheese wrote:

Freerdp2 has been updated, thunderbird hasn't as of yet. Just wait a few but don't ignore the icu update

They have all already been rebuilt.

san04 · 2025-02-20 20:35:32

I had the same issue and I guess previous electron packages were installed by the code-package in my case.

Could not find reverse dependencies (pacman -Qi) and since electron32 is currently in the repos, I decided to delete older versions manually. Afterwards I could update succesfully.

Is this really an AUR issue?

mackin_cheese · 2025-02-20 20:46:29

san04 wrote:

I had the same issue and I guess previous electron packages were installed by the code-package in my case.
Could not find reverse dependencies (pacman -Qi) and since electron32 is currently in the repos, I decided to delete older versions manually. Afterwards I could update succesfully.
Is this really an AUR issue?

it's not specifically an AUR issue. it's a "packages need to be updated" issue regardless if it's in official repos or aur. For OP, it was AUR packages. Packages in official repos are pretty much updated now. what's left is aur packages but that's the responsibility of the AUR maintainer to determine what actions need to take place with said packages.

dawalters · 2025-02-20 23:08:10

To drill home what Scimmia has been saying, for the people who are having this issue with older electrons (28, 29, 30, 31), check that you use them for something:

pacman -Qi electron<version-you-want-to-check>

This will have a line saying "Required By:". Check that this doesn't say "None". If it says "None", it's probably because some other app that uses electron has moved to another version, and the old ones are left behind.
You can then remove them if they aren't used:

sudo pacman -Rs electron<version-you-dont-need>

For example, `code` currently uses `electron32`. I suspect that it is probably the reason I had these older electrons installed.

DrLlap · 2025-02-21 00:20:40

Got the same error as op. Turned out I had electron30-electron33 installed. I didn't have anything that depended on electron30-32 and the only thing that depended on electron33 is obsidian.
1. So I'm guessing that obsidian used to depend on electron30-32 but now depends on electron33?
2. Should the the electron version be removed automatically when nothing depends on it anymore? (is there something potentially wrong with the obsidian package?)
3. Should I periodically check if I have packages installed that nothing depends on?

Scimmia · 2025-02-21 00:29:52

DrLlap wrote:

Got the same error as op. Turned out I had electron30-electron33 installed. I didn't have anything that depended on electron30-32 and the only thing that depended on electron33 is obsidian.
1. So I'm guessing that obsidian used to depend on electron30-32 but now depends on electron33?
2. Should the the electron version be removed automatically when nothing depends on it anymore? (is there something potentially wrong with the obsidian package?)
3. Should I periodically check if I have packages installed that nothing depends on?

1. Check the git history
2. No
3. Yes. https://wiki.archlinux.org/title/Pacman … _(orphans)

walteweiss · 2025-02-21 09:49:55

dawalters wrote:

To drill home what Scimmia has been saying, for the people who are having this issue with older electrons (28, 29, 30, 31), check that you use them for something:
pacman -Qi electron<version-you-want-to-check>
This will have a line saying "Required By:". Check that this doesn't say "None". If it says "None", it's probably because some other app that uses electron has moved to another version, and the old ones are left behind.
You can then remove them if they aren't used:
sudo pacman -Rs electron<version-you-dont-need>
For example, `code` currently uses `electron32`. I suspect that it is probably the reason I had these older electrons installed.

Huge thanks for that explanation! And for registering to only post that helpful instruction.

Honestly, I don’t understand why spam the entire thread by comments that provide no real help for those who seek the solution of their issue. If I’m a novice, I may not understand how to properly check if the package required by any other one. At least a link to a proper section in the wiki would help much more than play this game with replying with one word of wisdom to others. I’m not a novice, yet I was unsure what to do here, since it’s my first time dealing with such an issue. I, too, thought that the orphans are removed automatically when they aren’t needed by any other package and I did not explicitly install them. I am surprised it’s an issue I should deal with.

Removing the unused old electrons helped me. In my case, they were installed by code, and were versions 28-30. I don’t remember installing them from AUR, more likely they were present in the repositories at some point and are no longer there.

The recommended Removing unused packages (orphans) command,

sudo pacman -Qdtq | sudo pacman -Rns -

returned a lot of packages marked as ‘optionally requires,’ e.g.

:: gegl optionally requires graphviz: for gegl-introspect
:: gperftools optionally requires graphviz: pprof graph generation

Which I’m not sure whether I want to remove them or it’s better to leave them untouched.

In the wiki, as always, the information is obscure. The following note `The arguments -Qt list only true orphans.` is of no help, that’s not what one looks for when wants to remove only the orphans that aren’t needed anywhere. E.g. when I want to remove only the things that are not required at all, and not touch what is optionally required.

Man page makes it not clear to me either, so I guess I need to invest much more resources into that, if I’m looking to understand how to deal with this situation in the future. `-t` is a substitute for `--unrequired` which is

Restrict or filter output to print only packages neither required nor optionally required by any currently installed package. Specify this option twice to include packages which are optionally, but not directly, required by another package.

But if I do `sudo pacman -Qt`, that’s a lot of the packages that I use daily. So are they true orphans, really?

---

So, on the topic: explicitly removing only the electrons solved the issue for me, while the rest of the orphans is more likely just another topic to discuss.

And speaking of ‘unrelated issues,’ they look very related to me, all of them are broken with the update of icu. As all the packages strictly specify, they want the icu to be no newer than v.75. AUR or no AUR, it makes no difference here, I’d say. It rather specifies where you should look for updates, the official repository or not.

Saying all that, for me the solution looks like:

- either to wait for the repository maintainers to rebuild packages (so the issue will resolve itself)
- and/or remove your local packages that were in the repository when you installed them, but are no longer there (and in AUR now). If you don’t need them. As is the case for me, with the electron28,29,30. I see electron27,31,32,33,34 are in the repository.
- or if you cannot afford to remove the packages, rebuild them with the newer icu, right? (I don’t know how to properly do that, so no help from me here.)

Last edited by walteweiss (2025-02-21 09:54:06)

Endali · 2025-02-21 10:22:15

To just add in another possible solution that helped me:

If you DO need the package, you might be able to change to electron29-bin AUR package instead. Both the app that was using it (caprine) is still working, and the update should proceed as expected.

dynamic_byte · 2025-02-21 16:44:52

dawalters wrote:

To drill home what Scimmia has been saying, for the people who are having this issue with older electrons (28, 29, 30, 31), check that you use them for something:
pacman -Qi electron<version-you-want-to-check>
This will have a line saying "Required By:". Check that this doesn't say "None". If it says "None", it's probably because some other app that uses electron has moved to another version, and the old ones are left behind.
You can then remove them if they aren't used:
sudo pacman -Rs electron<version-you-dont-need>
For example, `code` currently uses `electron32`. I suspect that it is probably the reason I had these older electrons installed.

Thank you for posting this. This helped me to determine that I needed to pull the latest changes to an AUR package and rebuilt it, then I was able to remove the outdated electron dependency.

Arch Linux

#1 2025-02-20 12:42:29

ICU 76.1.1 Issue [SOLVED]

#2 2025-02-20 12:44:38

Re: ICU 76.1.1 Issue [SOLVED]

#3 2025-02-20 12:46:53

Re: ICU 76.1.1 Issue [SOLVED]

#4 2025-02-20 12:49:10

Re: ICU 76.1.1 Issue [SOLVED]

#5 2025-02-20 12:51:00

Re: ICU 76.1.1 Issue [SOLVED]

#6 2025-02-20 13:31:31

Re: ICU 76.1.1 Issue [SOLVED]

#7 2025-02-20 16:20:42

Re: ICU 76.1.1 Issue [SOLVED]

#8 2025-02-20 16:54:44

Re: ICU 76.1.1 Issue [SOLVED]

#9 2025-02-20 17:27:40

Re: ICU 76.1.1 Issue [SOLVED]

#10 2025-02-20 18:25:13

Re: ICU 76.1.1 Issue [SOLVED]

#11 2025-02-20 18:26:55

Re: ICU 76.1.1 Issue [SOLVED]

#12 2025-02-20 18:27:32

Re: ICU 76.1.1 Issue [SOLVED]

#13 2025-02-20 18:29:50

Re: ICU 76.1.1 Issue [SOLVED]

#14 2025-02-20 18:30:20

Re: ICU 76.1.1 Issue [SOLVED]

#15 2025-02-20 18:31:53

Re: ICU 76.1.1 Issue [SOLVED]

#16 2025-02-20 18:35:34

Re: ICU 76.1.1 Issue [SOLVED]

#17 2025-02-20 18:38:47

Re: ICU 76.1.1 Issue [SOLVED]

#18 2025-02-20 20:35:32

Re: ICU 76.1.1 Issue [SOLVED]

#19 2025-02-20 20:46:29

Re: ICU 76.1.1 Issue [SOLVED]

#20 2025-02-20 23:08:10

Re: ICU 76.1.1 Issue [SOLVED]

#21 2025-02-21 00:20:40

Re: ICU 76.1.1 Issue [SOLVED]

#22 2025-02-21 00:29:52

Re: ICU 76.1.1 Issue [SOLVED]

#23 2025-02-21 09:49:55

Re: ICU 76.1.1 Issue [SOLVED]

#24 2025-02-21 10:22:15

Re: ICU 76.1.1 Issue [SOLVED]

#25 2025-02-21 16:44:52

Re: ICU 76.1.1 Issue [SOLVED]

Board footer