Package Details: sip4 4.19.25-7

Git Clone URL: https://aur.archlinux.org/sip4.git (read-only, click to copy)
Package Base: sip4
Description: A tool that makes it easy to create Python bindings for C and C++ libraries
Upstream URL: https://www.riverbankcomputing.com/software/sip/intro
Licenses: LicenseRef-sip
Provides: sip4
Submitter: arojas
Maintainer: daizhirui
Last Packager: daizhirui
Votes: 5
Popularity: 0.013939
First Submitted: 2022-09-01 20:08 (UTC)
Last Updated: 2024-04-28 17:59 (UTC)

Latest Comments

1 2 3 Next › Last »

JstKddng commented on 2024-03-27 03:49 (UTC)

orphaning since I no longer use this package

MarsSeed commented on 2024-02-05 10:01 (UTC) (edited on 2024-03-26 20:00 (UTC) by MarsSeed)

@chaotic_bruno, ROS2 does not actually need sip4.

Even ROS1 Noetic AUR packages shouldn't require it, if @aczx would mind addig the official backported patches to the few relevant PKGBUILDs.

lprobsth commented on 2024-02-05 07:27 (UTC)

I think that the packages depending on sip4 should update their dependencies to clarify which sip version is needed by them. My workaround for now is to patch the conflicts attribute on each system where I need sip4. I'm working with ROS2 and the conflicts attribute regularly breaks automation.

xiota commented on 2024-01-29 00:24 (UTC)

@atheo Looks like a yaourt problem. The basename of the package is sip4. Use a different aur helper or try building in a clean chroot.

atheo commented on 2024-01-27 18:33 (UTC)

package is completely broken rn. while installing getting this:

$ yaourt -S python-sip4

==> Downloading python-sip4 PKGBUILD from AUR...
==> ERROR: python-sip4 not found in AUR.

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/{sipconfig.py, sip.so, sipdistutils.py, sip.pyi}. They don't conflict each other at all.

Here is the candidate fix: https://github.com/daizhirui/sip4.git