- Status Closed
- Percent Complete
- Task Type Bug Report
- Category Packages → Packages: Stable
-
Assigned To
Andreas Baumann - Operating System i686
- Severity Low
- Priority Very Low
- Reported Version
- Due in Version Undecided
-
Due Date
Undecided
- Votes
- Private
Attached to Project: Arch Linux 32
Opened by Francois Dupoux - 10.04.2022
Last edited by Andreas Baumann - 17.04.2022
Opened by Francois Dupoux - 10.04.2022
Last edited by Andreas Baumann - 17.04.2022
FS#251 - [pavucontrol] libcanberra/libcanberra-pulse dependency conflicts
There is currently a problem preventing the installation of pavucontrol on i686:
resolving dependencies... warning: cannot resolve "libcanberra=0.30+2+gc0620e4-3.2", a dependency of "libcanberra-pulse" warning: cannot resolve "libcanberra-pulse", a dependency of "pavucontrol" :: The following package cannot be upgraded due to unresolvable dependencies: pavucontrol error: failed to prepare transaction (could not satisfy dependencies) :: unable to satisfy dependency 'libcanberra=0.30+2+gc0620e4-3.2' required by libcanberra-pulse :: unable to satisfy dependency 'libcanberra-pulse' required by pavucontrol
Mmh, I could install pavucontrol yesterday on all archs and table/testing.
I think the package conflicts are resolved now.
Can you please check again?
Thanks for checking. I tested again but it is still failing sorry.
Here you can see that libcanberra-pulse for i686 requires libcanberra=0.30+2+gc0620e4:
https://www.archlinux32.org/packages/i686/extra/libcanberra-pulse/
And here you can see the current version of libcanberra on i686 is a bit different:
https://www.archlinux32.org/packages/i686/extra/libcanberra/ libcanberra 1:0.30+r2+gc0620e4-1.0
So there is a version mismatch and hence the dependency check fails.
Ah, I could reproduce it. I misread your post and though pavucontrol is the problem.
I'll trigger a rebuild of libcanberra.
The new build has a build version of 1.1, the old one required by libcanberra-pulse 3.2.
How is this possible? Build versions are not supposed to go backwards..
dependency libcanberra=0.30+2+gc0620e4-3.2
I fail to see where this is added.. maybe in the buildmaster itself and the buildmaster
has a wrong idea of what the current pkgver and build version is?
libcanberra is just a pseudo-reference, not a real packages, so force installing should
work as a workaround..
Oh pkgver=0.30+2+gc0620e4 changed to 0.30+r2+gc0620e4 (what version numbers!)
I think, this hard-coded
replaces=("libcanberra-pulse<0.30+2+gc0620e4-4")
is a problem. This version might never have existed in Arch32, I'll try to build
without that one..
Can you try to update your system first with pacman -Syyu and try the installation
of pavucontrol then?
Sorry, it is still failing. It is not a regular system, it is failing when attempting to build a docker image.
I checked with docker, there is nothing wrong with that (BTW, there is a docker git
for Archlinux32 at https://git.archlinux32.org/docker/).
warning: cannot resolve "libcanberra=0.30+2+gc0620e4-3.2", a dependency of "libcanberra-pulse"
it tries to resolve an old version of libcanberra, because it still remembers the days
when libcanberra-pulse was a split package and in version 2-3.2). I see no other way
than to manually remove the libcanberra-pulse package from the repos on the buildmaster.
Or to change all PKBBUILDS requiring libcanberra-pulse to libcanberra only (which would
deviate from upstream)..
But I don't how to fix that properly in the buildmasters guts (aka Mysqldb)
(abaumann summons the master of buildmasters here. )
mmh. I'm trying now another rebuild. If pavucontrol is not containing libcanberra-pulse,
then it should actually work.
So, it should really work now. I really don't know, but I think pavucontrol was not
rebuilt and still referenced libcanberra-pulse.
I confirm it is now working fine, thanks for having sorted this out
Thanks for reporting.