Package Base Details: sip4

Git Clone URL: (read-only, click to copy)
Submitter: arojas
Maintainer: JstKddng
Last Packager: JstKddng
Votes: 4
Popularity: 0.038883
First Submitted: 2022-09-01 20:08 (UTC)
Last Updated: 2023-05-06 00:37 (UTC)

Latest Comments

1 2 Next › Last »

joshm commented on 2023-11-07 22:56 (UTC)

This is not updating for me, I get:

==> Entering fakeroot environment...
==> Starting package_sip4()...
make: Entering directory '/home/josh/.cache/pacaur/sip4/src/build/sipgen'
cp -f sip /home/josh/.cache/pacaur/sip4/pkg/sip4/home/josh/.pyenv/versions/3.10.2/bin/sip
cp -f /home/josh/.cache/pacaur/sip4/src/sip-4.19.25/siplib/sip.h /home/josh/.cache/pacaur/sip4/pkg/sip4/home/josh/.pyenv/versions/3.10.2/include/python3.10/sip.h
make: Leaving directory '/home/josh/.cache/pacaur/sip4/src/build/sipgen'
mv: cannot stat '/home/josh/.cache/pacaur/sip4/pkg/sip4/usr/include/python*/sip.h': No such file or directory
==> ERROR: A failure occurred in package_sip4().

daizhirui commented on 2023-10-10 19:38 (UTC)

With sip included in conflicts, users cannot have sip installed by pacman when we also need sip4. This prevents us from working on other SIP projects that uses the latest sip. Since sip4 is not updated by upstream anymore, I think it is better to remove sip from conflicts and other packages should update its dependencies to clearly define which one to use.

FabioLolix commented on 2023-10-10 19:28 (UTC)

The other packages in which is unclear need to check and update then, with a quick look for several is pending a deletion request

JstKddng commented on 2023-10-10 19:15 (UTC)

Changing what this package provides could break other packages. Other packages have a dependency on sip but it's not quite clear which depend on sip4 or regular sip.

daizhirui commented on 2023-10-10 18:52 (UTC) (edited on 2023-10-10 18:52 (UTC) by daizhirui)

This package should not be labled as providing and conflicting with sip. sip provides totally different tool sets, like sip-build, sip-install. sip4 provides a single tool called sip. sip is installed to /usr/lib/python*/site-packges/sip-build while sip4 is installed to /usr/lib/python*/site-packages/{,,, sip.pyi}. They don't conflict each other at all.

Here is the candidate fix:

chaotic_bruno commented on 2023-09-27 14:57 (UTC)

Is it possible that "" should be called with the option "-v /usr/lib/python3.11/site-packages" (see By default the script configures the directory "default_sip_dir" to "/usr/share/sip" in "". But in arch we install the sip-package "PyQt5" to "/usr/lib/python3.11/site-packages". This leads to a compilation error in ROS2 packages when trying to find the PyQt5 installation with the "default_sip_dir" variable....

xiota commented on 2023-09-20 09:17 (UTC)

Please remove replaces directive. Thank you. (No need to reply via comment; AUR now sends commit notifications.)

SeparateWings commented on 2023-07-26 07:10 (UTC)

It should be noticed that sip-build is only in sip but not in this package, I don't know if there exists bugs.

FabioLolix commented on 2023-07-24 17:11 (UTC)

IMO this shouldn't provide sip at all, sip4 and current sip 6.x (sip 5 never published seems) aren't interchangeable, even adding =${pkgver} a pkgbuild like calibre-git will not complain about the dependency then fails the builds because they are different (ModuleNotFoundError: No module named 'sipbuild')

dreieck commented on 2023-07-24 10:46 (UTC)

Can you add =${pkgver} to the provides entries?

This would allow packages that need sip>=6 or sip<5 to specify and match their versioned dependencies correctly.

Thanks for maintaining!