Search Criteria
Package Details: ros2-pyqt5-sip-compat 0.2-1
Package Actions
- View PKGBUILD / View Changes
- Download snapshot
- Search wiki
- Flag package out-of-date
- 1 pending request
- Submit Request
| Git Clone URL: | https://aur.archlinux.org/ros2-pyqt5-sip-compat.git (read-only, click to copy) |
|---|---|
| Package Base: | ros2-pyqt5-sip-compat |
| Description: | pyqt5-sip compatibility symlinks for building ros2 |
| Upstream URL: | None |
| Licenses: | MIT |
| Submitter: | rmsc |
| Maintainer: | None |
| Last Packager: | rmsc |
| Votes: | 0 |
| Popularity: | 0.000000 |
| First Submitted: | 2021-11-10 19:06 (UTC) |
| Last Updated: | 2021-12-13 22:04 (UTC) |
Latest Comments
MarsSeed commented on 2023-11-30 17:55 (UTC)
ros2-foxy is EOL since 2023-03 and unbuildable, broken. I have closed an earlier deletion request for it and created a new one: PRQ#49195.
This package is also long broken but safe to delete.
oljik commented on 2021-12-25 16:15 (UTC)
Is there workaround for python-pyqt5 dropping sip4?
rmsc commented on 2021-12-20 10:25 (UTC)
Removing
/usr/share/sip/PyQt5may be enough to get this package installed, but on my system there were also stray symlinks in/usr/lib/python3.9/site-packages/PyQt5/(orpython3.10).Perhaps this may be useful: https://wiki.archlinux.org/title/Pacman/Tips_and_tricks#Identify_files_not_owned_by_any_package
LuTri commented on 2021-12-20 04:09 (UTC) (edited on 2021-12-20 04:24 (UTC) by LuTri)
How do I go about removing the symlinks by hand? I am running into this issue as well.
Edit: I was impatient. Found out. go to: /usr/share/sip There should be a file called PyWt5. If you delete that, it deletes the symlink.
rmsc commented on 2021-12-09 10:43 (UTC) (edited on 2021-12-20 10:26 (UTC) by rmsc)
pacmanwill not touch any files/symlinks created by hand. If you created the symlinks by hand, you need to remove them manually.Older versions of
ros2-galacticalso created symlinks "by hand", so they need to be removed manually as well.The new symlinks created by this package actually belong to the package, so they're now managed by
pacman.In order to find and remove the stray symlinks, this may be useful: https://wiki.archlinux.org/title/Pacman/Tips_and_tricks#Identify_files_not_owned_by_any_package
oljik commented on 2021-12-08 13:59 (UTC) (edited on 2021-12-08 14:14 (UTC) by oljik)
fails to create symbolic links as they already exist.
Update: I remembered doing what this package does by hand in the past.