Package Details: python2-pylibacl 0.5.3-5

Git Clone URL: https://aur.archlinux.org/python-pylibacl.git (read-only)
Package Base: python-pylibacl
Description: A python extension module that allows you to manipulate the POSIX.1e ACLs.
Upstream URL: http://pylibacl.k1024.org/
Licenses: LGPL
Conflicts: pylibacl
Provides: pylibacl
Submitter: sanerb
Maintainer: sanerb
Last Packager: sanerb
Votes: 1
Popularity: 0.015788
First Submitted: 2017-04-29 23:55
Last Updated: 2018-05-26 13:52

Dependencies (5)

Required by (4)

Sources (2)

Pinned Comments

sanerb commented on 2017-04-30 00:01

# Bug reports can be filed at https://bugs.square-r00t.net/index.php?project=3
# News updates for packages can be followed at https://devblog.square-r00t.net

(If you want an RSS-feed only pertaining to my AUR packages, you can subscribe to https://devblog.square-r00t.net/rss/?category=aur in your favourite RSS reader.)

Note that you should still use the AUR web interface for flagging packages as out-of-date if a new version is released; the aforementioned bug tracker is to aid in issues with building/packaging/the PKGBUILD formats/etc. specifically.

GPG signature "errors" are explained here:
https://devblog.square-r00t.net/articles/a-note-on-using-gpg-signatures-in-pkgbuilds

Please read; it's not a bug.


Thanks!

Latest Comments

sanerb commented on 2018-05-26 13:53

@sl1pkn07-

it was ALREADY FIXED. you know what? fine.

new version pushed. stop nitpicking. provides for both versions does not break specification for PKGBUILD as it'd be future-proofing in the instance Arch adds python3 support to community/pylibacl. further comments will be ignored. open a task in my bugtracker (which you should have done anyways, per pinned comment) if you have anything valuable to add.

sl1pkn07 commented on 2018-05-26 13:37

2 aur/python-pylibacl 0.5.3-4 [installed: 0.5.3-3] (1) (0,05)
    A python extension module that allows you to manipulate the POSIX.1e 
    ACLs. (Fixed for python 3)
3 aur/python2-pylibacl 0.5.3-4 [installed: 0.5.3-3] (1) (0,05)
    A python extension module that allows you to manipulate the POSIX.1e 
    ACLs. (Fixed for python 3)

you need set pkgdesc in package_python2-pylibacl and package_python-pylibacl

and also need add provides=('pylibacl') in package_python2-pylibacl, because is a directly replace of pylibacl

like this

https://pastebin.com/dPzhvLVi

sanerb commented on 2018-05-26 10:43

@sl1pkn07-

The description is correct. :) community/pylibacl installs no Python 3 version:

[bts@cylon ~]$ pacman -Ql pylibacl
pylibacl /usr/
pylibacl /usr/lib/
pylibacl /usr/lib/python2.7/
pylibacl /usr/lib/python2.7/site-packages/
pylibacl /usr/lib/python2.7/site-packages/posix1e.so
pylibacl /usr/lib/python2.7/site-packages/pylibacl-0.5.3-py2.7.egg-info/
pylibacl /usr/lib/python2.7/site-packages/pylibacl-0.5.3-py2.7.egg-info/PKG-INFO
pylibacl /usr/lib/python2.7/site-packages/pylibacl-0.5.3-py2.7.egg-info/SOURCES.txt
pylibacl /usr/lib/python2.7/site-packages/pylibacl-0.5.3-py2.7.egg-info/dependency_links.txt
pylibacl /usr/lib/python2.7/site-packages/pylibacl-0.5.3-py2.7.egg-info/top_level.txt

by "fixed for python 3", i mean "installs a python3 version".

good call on moving the conflicts. i added the provides for both python3 and python2 subpackages, however.

sl1pkn07 commented on 2018-05-26 10:22

python2-pylibacl have typo in the description (python3 -> python2)

also needs set provides() conflicts() with pylibacl, only in python2 package

sanerb commented on 2017-04-30 00:01

# Bug reports can be filed at https://bugs.square-r00t.net/index.php?project=3
# News updates for packages can be followed at https://devblog.square-r00t.net

(If you want an RSS-feed only pertaining to my AUR packages, you can subscribe to https://devblog.square-r00t.net/rss/?category=aur in your favourite RSS reader.)

Note that you should still use the AUR web interface for flagging packages as out-of-date if a new version is released; the aforementioned bug tracker is to aid in issues with building/packaging/the PKGBUILD formats/etc. specifically.

GPG signature "errors" are explained here:
https://devblog.square-r00t.net/articles/a-note-on-using-gpg-signatures-in-pkgbuilds

Please read; it's not a bug.


Thanks!