Community Packages

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#25614 - [pyxattr] Not packaged for python 3 (PKGBUILD provided)

Attached to Project: Community Packages
Opened by Jon Bergli Heier (snakebite) - Tuesday, 16 August 2011, 21:03 GMT
Last edited by Lukas Fleischer (lfleischer) - Monday, 22 August 2011, 08:04 GMT
Task Type Feature Request
Category Packages
Status Closed
Assigned To Lukas Fleischer (lfleischer)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

The current pyxattr package is not packaged for python 3, in addition to being inconsistently named. I've attached a split PKGBUILD to package python2-pyxattr and python-pyxattr for python 2 and python 3, respectively (based on the official PKGBUILD).
   PKGBUILD (0.9 KiB)
This task depends upon

Closed by  Lukas Fleischer (lfleischer)
Monday, 22 August 2011, 08:04 GMT
Reason for closing:  Implemented
Additional comments about closing:  Implemented in 0.5.0-2.
Comment by Lukas Fleischer (lfleischer) - Saturday, 20 August 2011, 20:32 GMT
Why should we have both packages depend on Python 2.x and Python 3.x at the same time? Same applies to makedepends :)
Comment by Jon Bergli Heier (snakebite) - Saturday, 20 August 2011, 21:19 GMT
My bad, attaching new PKGBUILD with fixed depends and makedepends.
   PKGBUILD (0.9 KiB)

Loading...