Updated, thanks for the note mothran! Would you be interested in maintaining this package? I rarely use this library in my work (haven't used it in quite some time now). If you'd like I could orphan it so you could take it over. It's fine if not though.
Search Criteria
Package Details: python2-pcapy 0.10.8-2
Package Actions
| Package Base: | python2-pcapy |
|---|---|
| Description: | Python module for the libpcap packet capture library. |
| Upstream URL: | http://corelabs.coresecurity.com/index.php?module=Wiki&action=view&type=tool&name=Pcapy |
| Category: | lib |
| Licenses: | |
| Submitter: | tom5760 |
| Maintainer: | tom5760 |
| Last Packager: | tom5760 |
| Votes: | 19 |
| First Submitted: | 2013-05-15 16:13 |
| Last Updated: | 2014-07-17 18:10 |
Sources
- LICENSE
- pcapy-0.10.8.tar.gz
- pcapy_open_live_lo_error.patch
Latest Comments
Comment by tom5760
Comment by mothran
After installing this package I noticed that the upstream maintainers never patched this bug (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=500041) from Debian, would it be possible to add it to this package?
Comment by tom5760
No problem =) Perhaps sometime in the future I'll change this.
Comment by martvefun
I didn't know, thanks for your answer.
Comment by tom5760
No, I would essentially have to create a whole new AUR entry for a python2-pcapy package, then email the AUR mailing list and ask a TU to delete the old one. Then, any packages that depend on pcapy would have to be updated to reflect the new name. If it was simpler, then I wouldn't hesitate as much.
Comment by martvefun
Ok as you want, it's not a big deal, the package does not seem to be maintained by the author anyway.
Just for the sake of curiosity, does not the name-change of packages in AUR automatically reflected to the other packages that use it ?
Comment by tom5760
I totally agree, but this package has been named this way for a while (I haven't updated this package since early last year, and the last official release was in 2007). There's also one other AUR package that seems to depend on this. So, for now at least, I'd probably rather leave things the way they are. Also, I'd imagine that since the python2 dependency is listed on the page, its pretty clear that this package is for python 2 (and not 3).
Comment by martvefun
The name and description is maybe not adequate.
Shouldn't python modules be named with the syntax python2-pycapy ? (I'm not a packager specialist though)
Also the description specify "Python module" where "Python2 module" would have been more informative.
Comment by tom5760
Done, thanks for the note.
Anonymous comment
Yuo must update this package for python2