Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#21807 - [httplib2] is not packaged for python3

Attached to Project: Arch Linux
Opened by Jesse Young (jlyo) - Tuesday, 23 November 2010, 21:10 GMT
Last edited by Rémy Oudompheng (remyoudompheng) - Friday, 08 July 2011, 06:28 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Rémy Oudompheng (remyoudompheng)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Current httplib2 depends on python2 when it is available for python3 as well.

Here are PKGBUILDs for each, httplib2 becomes python2-httplib2, and the package for python3 is called python-httplib2.

I considered making a split package, but it requires separate build steps. While I could copy directories around, it seemed simpler to create separate packages. Is this what you would do?

Thanks,
Jesse
   PKGBUILD (0.9 KiB)
   PKGBUILD (0.9 KiB)
This task depends upon

Closed by  Rémy Oudompheng (remyoudompheng)
Friday, 08 July 2011, 06:28 GMT
Reason for closing:  Implemented
Comment by Thomas Dziedzic (tomd123) - Thursday, 25 November 2010, 05:32 GMT
I think the best way to go about this, is to leave the python2 package in extra and for you to put the python3 version into the aur to close this bug.
Comment by Jesse Young (jlyo) - Thursday, 25 November 2010, 18:48 GMT
Hi Thomas,

I respectfully disagree that the python3 httplib2 should be in AUR while the python2 httplib2 remains in extra. Now that python3 is now the default python, we should begin migrating packages to python3. In the interim period where python2 and python3 are being maintained in parallel, I beleive that library packages should be maintained in parallel (ie. same repo).

I think the path of action should be to keep python-* and python2-* packages together in the same repository, then, as python2 becomes less supported in the years to come, we move the python2* packages to community, and drop them alltogether as they become completely unsupported.

Essentially, my point is, in order to move forward we should make python3 libraries available as default now that python3 is default.

If I should have reported this as an out of date package, please excuse my reporting this as a bug. It's not _quite_ an out of date package, since upstream didn't increase the version number.

Thanks,
Jesse
Comment by Thomas Dziedzic (tomd123) - Friday, 26 November 2010, 03:07 GMT
You make a good point, I retract my previous statement and agree with Jesse on this one if upstream supports python3.
Comment by Jan de Groot (JGC) - Friday, 26 November 2010, 09:06 GMT
If upstream supports python3 for something, and all dependencies required for that also do that, we should package them both in a split package. That way we always update both in one run without having inconsistencies.
Comment by Jesse Young (jlyo) - Saturday, 27 November 2010, 22:07 GMT
Here is the split PKGBUILD for python2-httplib2 and python-httplib2.
   PKGBUILD (1.6 KiB)

Loading...