Bug #3477
Housekeeping #3487: [STICKY][python]: and friends (x86_64)
[python-pyqt5] rebuild against latest python
0%
Description
installing python (3.11.3-1) breaks dependency 'python<3.11' required by python-pyqt5
History
Updated by pavelsayekat 12 months ago
# pacman -Syu :: Synchronizing package databases... libre is up to date kernels is up to date core is up to date extra is up to date community is up to date pcr is up to date libre-multilib is up to date multilib is up to date :: Starting full system upgrade... resolving dependencies... warning: cannot resolve "gst-plugins-bad-libs=1.22.2", a dependency of "gst-plugin-gtk" warning: cannot resolve "perl=5.36.1", a dependency of "polymake" :: The following packages cannot be upgraded due to unresolvable dependencies: gst-plugin-gtk polymake :: Do you want to skip the above packages for this upgrade? [y/N] y looking for conflicting packages... error: failed to prepare transaction (could not satisfy dependencies) :: installing gst-plugins-base-libs (1.22.2-1) breaks dependency 'gst-plugins-base-libs=1.22.1' required by gst-plugin-wpe :: installing gst-plugins-base-libs (1.22.2-1) breaks dependency 'gst-plugins-base-libs=1.22.1' required by gst-plugins-bad-libs :: installing python (3.11.3-1) breaks dependency 'python<3.11' required by python-pyqt5
Updated by eliotime3000 12 months ago
Same result I have today.
Also, the gst-plugins-bad-libs
package also requires to be updated against the latest version of gst-plugins-gtk
and/or other related packages.
Updated by poisson-aerohead 12 months ago
Hi, has there been any movement on this? I reported it as well (https://labs.parabola.nu/issues/3479) and interfux directed me here. It seems to me like it is just a dependency misnomer, not a real bug or anything.
Updated by pavelsayekat 12 months ago
Well, I've rebuilt my gst-plugins-bad-libs and python-pyqt5 locally to fix this, thanks to abslibre git.
Updated by bill-auger 11 months ago
- Parent task set to #3487
- Assignee set to bill-auger
- Status changed from unconfirmed to in progress
Updated by bill-auger 11 months ago
It seems to me like it is just a dependency misnomer, not a real bug or anything.
that is correct - both this and the 'gst-plugins-bad-libs' issue are routine, usually simple rebuilds - they simply coincided this time
see #3480 for the 'gst-plugins-bad-libs' issue - that one should be fixed now