Library icu 76 conflicts with 75 version

[Dell]

:: 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 'libicuuc.so=75-64' required by qt5-webkit
:: installing icu (76.1-1) breaks dependency 'libicui18n.so=75-64' required by qt5-webkit

yay icu75

:: icu75-75.1-9 and icu-75.1-2 are in conflict. Remove icu? [y/N] Y
:: icu75-75.1-9 and lib32-icu-75.1-1 are in conflict (libicudata.so). Remove lib32-icu? [y/N] Y
error: failed to prepare transaction (failed to satisfy dependencies)
:: removing icu breaks dependency 'icu' required by bind
:: removing icu breaks dependency 'icu' required by boost-libs
:: removing icu breaks dependency 'icu' required by chromium
:: removing icu breaks dependency 'icu' required by gspell
:: removing icu breaks dependency 'icu' required by harfbuzz-icu
:: removing icu breaks dependency 'icu' required by kdeplasma-addons
:: removing icu breaks dependency 'icu' required by kdiff3
:: removing icu breaks dependency 'icu' required by konsole
:: removing lib32-icu breaks dependency 'lib32-icu' required by lib32-libxml2
:: removing icu breaks dependency 'icu' required by libcdr
:: removing icu breaks dependency 'icu' required by libe-book
:: removing icu breaks dependency 'icu' required by libmspub
:: removing icu breaks dependency 'icu' required by libqalculate
:: removing icu breaks dependency 'icu' required by libqxp
:: removing icu breaks dependency 'icu' required by libreoffice-fresh
:: removing icu breaks dependency 'icu' required by libvisio
:: removing icu breaks dependency 'icu' required by libxml2
:: removing icu breaks dependency 'icu' required by libzmf
:: removing icu breaks dependency 'icu' required by plasma-desktop
:: removing icu breaks dependency 'icu' required by plasma-workspace
:: removing icu breaks dependency 'icu' required by qt5-webkit
:: removing icu breaks dependency 'icu' required by qt6-5compat
:: removing icu breaks dependency 'icu' required by qt6-base
:: removing icu breaks dependency 'icu' required by qt6-webengine
:: removing icu breaks dependency 'icu' required by raptor
:: removing icu breaks dependency 'icu' required by smbclient
:: removing icu breaks dependency 'icu' required by tinysparql
:: removing icu breaks dependency 'icu' required by vte3
:: removing icu breaks dependency 'icu' required by webkit2gtk-4.1
 -> installation error: [/home/user/.cache/yay/icu75/icu75-75.1-9-x86_64.pkg.tar.zst] - exit status 1

I tried to do it too remove caprine, electron29, electron28, electron30, (writes they are not there) (I read it on the internet)

pacman -S qt5-webkit
error: target not found: qt5-webkit

pacman -R qt5-webkit
removing qt5-webkit breaks dependency ‘qt5-webkit’ required by acetoneiso2

pacman -Q icu
icu 75.1-2

I’m confused… and I can’t figure anything out.
I did all this from ddy4 too

[Dell]

@Dell

acetoneiso2

I don’t know how stable it will work.
But I think I fixed it.

I deleted acetoneiso2 and then qt5-webkit

The update has started

[dalto]

This happens when an AUR package depends on a specific version of a library.

In this case, remove it and then rebuild it after the upgrade.

sudo pacman -Rdd qt5-webkit
sudo pacman -Syu
yay -Su qt5-webkit

[Locutus]

Surprised that you got that at all since it’s been addressed by the maintainer(s) of the dependencies for just under or over a week now.

[dalto]

@Locutus

Surprised that you got that at all since it’s been addressed by the maintainer(s) of the dependencies for just under or over a week now.

It is because repo packages are updated before AUR packages.

So if you have an AUR package that has a specific version dependency you will get this issue. Even if the AUR package has already been updated it will still happen.

[Locutus]

This issue was already resolved as I stated.

[dalto]

@Locutus

This issue was already resolved as I stated.

You are missing the point. This will always happen with AUR packages even after the issue is resolved.

[Locutus]

@dalto

You are missing the point. This will always happen with AUR packages even after the issue is resolved.

I didn’t a damn thing. The tread was and is about a issue that was already resolved not about which items get updated first.

[dalto]

@Locutus

The tread was and is about a issue that was already resolved not about which items get updated first.

No, it isn’t. This is simply due to the way pacman works with AUR packages.

qt5-webkit is an AUR package on EOS. paru and yay both call pacman to update the packages. When pacman hits an AUR package that is built against a specific version of a library, it will always fail like this.

It makes no difference if the AUR maintainer has updated something or not.

This is because pacman doesn’t even look in the AUR. This will always happen. There is no “resolving” this issue. It is something the user has to handle.

Are using a 3rd party repo or thinking about different distro where qt5-webkit is in a repo? In that case, you would need to wait for that package to be rebuilt.

[Locutus]

libicuuc.so=75-64 and libicui18n.so=75-64 were not updated when icu was and caused a host of issues. in my case it was fsearch I had to remove, wait about half a day, rerun my updates, reinstall fsearch and all was well. In some case it it was various electron versions and in this instance it’s qt5-webkit.

[dalto]

@Locutus

libicuuc.so=75-64 and libicui18n.so=75-64 were not updated

Those don’t get updated separately. They are part of icu.

>> pacman -Qo /usr/lib/libicuuc.so
/usr/lib/libicuuc.so is owned by icu 75.1-2

The error in the OPs post isn’t caused by a package not being updated. It is just the way pacman handles foreign packages.

@Locutus

n my case it was fsearch I had to remove, wait about half a day, rerun my updates, reinstall fsearch

In this case, as long as fsearch was coming from the AUR, it was removing fsearch that resolved the issue.

It could have been immediately reinstalled it after updating. Waiting half a day would not have mattered in that case.

fsearch in the AUR hasn’t been updated since August, 25th 2024.

[Locutus]

Actually not accurate the files in question did not get updated til later in the day. I know cause I had tried several updates after putting fsearch back in only for it to fail because of those two files.

[dalto]

@Locutus

Actually not accurate the files in question did not get updated til later in the day. I know cause I had tried several updates after putting fsearch back in only for it to fail because of those two files.

As you can see, the package was last updated last year.

If you saw something different than this then you are likely not using AUR but getting the fsearch package from a 3rd party repo. In that case, you would need to wait to for that repo to rebuild the package. However, that is not the situation that the OP was facing.