You are not logged in.
good morning
having a small problem with updating, arch.
the morning update come up with this:
pacman -Syu
:: Synchronizing package databases...
core 126.5 KiB 133 KiB/s 00:01 [--------------------------------] 100%
extra 8.3 MiB 1537 KiB/s 00:06 [--------------------------------] 100%
multilib 127.5 KiB 130 KiB/s 00:01 [--------------------------------] 100%
chaotic-aur 661.5 KiB 50.4 KiB/s 00:13 [--------------------------------] 100%
arcolinux_repo 49.5 KiB 105 KiB/s 00:00 [--------------------------------] 100%
arcolinux_repo_3party 150.1 KiB 243 KiB/s 00:01 [--------------------------------] 100%
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: unable to satisfy dependency 'libjpeg' required by gtk4-git
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: installing libjpeg-turbo (3.2.0-2) breaks dependency 'libjpeg' required by gtk4-giti tried reinstalling gtk4-git
subo pacman -S gtk4-giti tryed to remove libjpeg
sudo pacman -R libjpeg
error: target not found: libjpegso i'm stuck at this point? is there any thing i cam do?
i
Last edited by klein (Yesterday 14:48:52)
Offline
The virtual libjpeg was removed on purpose , see Remove the provision for libjpeg
Change libjpeg to libjpeg.so or libjpeg-turbo in the PKGBUILD.
Also add a comment about this on the gtk4-git aur page.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
After changing that in your PKGBUILDs, you need to rebuild and install them. In some affected cases a rebuild may be required simply because the so version has changed.
If you rely on somebody else’s PKGBUILDs (e.g. over AUR) and don’t want to keep your own PKBUILD separate from theirs (for whatever reason), you may temporarily make pacman think libjpeg dependency is satisfied with: `--assume-installed=libjpeg`. This will not help with packages that require a rebuild, This is also a temporary circumvention only(!) — to let the official packages be updated ASAP, while fixing the foreign ones is in progress.
That may also be needed if you don’t build in clean chroot and wish to avoid rebuilding packages twice: once merely to satisfy dependencies, once for the updated libjpeg-turbo.
Last edited by mpan (Yesterday 12:41:20)
Offline
i fixed it by :
octopi
removed gtk4-git
installed gtk4
it looks to me this has already been reported in 2026.
the gtk4 makes firefox look a lot better.
Offline
the gtk4 makes firefox look a lot better.
Firefox uses GTK3, so no.
https://bugzilla.mozilla.org/show_bug.cgi?id=1701123
Unless you actually compiled FF from this branch.
Offline
I had this exact error today. I solved it by replacing electron27 with electron27-bin from the AUR. After that regular updates worked. No editing of files needed.
Offline
I have similar errors, but others packages are also affected :
error: failed to prepare transaction (could not satisfy dependencies)
:: installing libjpeg-turbo (3.2.0-2) breaks dependency 'libjpeg' required by electron19
:: installing libjpeg-turbo (3.2.0-2) breaks dependency 'libjpeg' required by electron27
:: installing libtiff (4.7.2-1) breaks dependency 'libtiff=4.7.1' required by lib32-libtiff
:: installing libjpeg-turbo (3.2.0-2) breaks dependency 'libjpeg' required by ntk-git
:: installing libjpeg-turbo (3.2.0-2) breaks dependency 'libjpeg' required by xsaneWhich package can replace xsane ?
Last edited by Potomac (Today 16:38:53)
Offline
Mod note: Moving to AUR Issues.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Online
Potomac, you don’t have to replace anything. Not due to the issue discussed in this thread, at least.
The packages declare a wrong dependency. That is all! All affected packages did work with libjpeg-turbo for years and, unless API backward compatibility is broken, are going to continue working with libjpeg-turbo for the foreseeable future. It’s an issue in package’s description. You can just rebuild the package with `depends` array corrected to indicate libjpeg-turbo instead of libjpeg.
If you delegate maintaining PKGBUILDs to somebody else (e.g. some AUR user) ping them about the need to make that update. In the meantime you may use my advice above as a temporary remedy where a rebuild due to so version change isn’t needed. Where needed, you’d have to rebuild anyway. With or without the libjpeg dependency situation.
Offline