Package Base Details: python-sip-pyqt4

Git Clone URL: (read-only, click to copy)
Submitter: graysky
Maintainer: LaughingMan
Last Packager: LaughingMan
Votes: 31
Popularity: 0.051085
First Submitted: 2019-01-06 15:57
Last Updated: 2021-03-18 02:11

Latest Comments

« First ‹ Previous 1 2

rezaarifandee commented on 2019-04-28 07:04

i can't download from riverbankcomputing, heck i cant even open their website. Anybody got a mirror for sip-4.19.16.tar.gz?

Edit: Found a mirror on

buzo commented on 2019-04-20 18:49

jvandrew: Please note that AUR helpers are not supported. You should try to get help from the yay developers, or just learn how to build manually (which works fine, btw).

jvandrew commented on 2019-04-20 18:08

Installing with yay, I get this error:

Could not find PKGDEST for: python2-sip-pyqt4

I assume this has something to do with the merger of this package into python-sip-pyqt4? This prevents updating pyqt4-common as well.

buzo commented on 2019-04-02 15:37

Sorry, I have been busy lately. I have updated it now.

dmp1ce commented on 2019-03-30 18:35

I agree. This package should be updated. It is breaking pybitmessage at the moment because it hasn't been updated. Fix is here:

diff --git a/PKGBUILD b/PKGBUILD
index de7f094..d577e4e 100644
@@ -4,14 +4,14 @@
 # based on


 prepare() {
   mkdir -p build-pyqt4-py2

jheinz commented on 2019-03-25 14:37

The download URL is wrong or has changed. The valid one is:

eschwartz commented on 2019-03-20 17:46

Why not update this package in the meantime, and discuss with graysky the possibility of merging them?

Has graysky ever been contacted about it? Do you know whether he knows about the proposal at all, or whether he considers it desirable?

fbrennan commented on 2019-03-09 23:39

Hello world:

User alexei flagged the package and buzo filed an orphan request.

alexei wrote, among other things, that:

Btw, could you please merge the python-sip-pyqt4 and python2-sip-pyqt4 into one split package?

This is impossible as the counterpart package is already owned by someone else, graysky. So I decided it would be prudent to wait for them to request deletion of this package, presumably when they have a split package available.

That hasn't happened. This package should not be orphaned, it should be deleted. But it shouldn't be deleted until graysky requests as such because only he can make a split package. Alternatively, he can add me as a comaintainer to his package, then I can push the split package.