Your message dated Mon, 30 Apr 2012 03:32:38 +0000
with message-id <[email protected]>
and subject line Bug#656543: fixed in python-libpcap 0.6.2-0.2
has caused the Debian Bug report #656543,
regarding [python-pypcap, python-libpcap] Both package have a module named
pcap, therefore should be marked as a conflict
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
656543: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656543
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: python-pypcap,python-libpcap
Version: python-pypcap/1.1.2+debian-2.1
Version: python-libcpcap/0.6.2-0.1+b2
Severity: normal
The packages above mentioned provide similar libpcap-based capturing and
injection funcionalities. The issue is presented when loading pcap
python module and we having both packages installed, a conflict could be
produced if the wrong library is loaded first e.g.[0].
This packages should conflict between each other.
[0]/usr/share/doc/python-libpcap/examples/sniff.py
--
TiN
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: python-libpcap
Source-Version: 0.6.2-0.2
We believe that the bug you reported is fixed in the latest version of
python-libpcap, which is due to be installed in the Debian FTP archive:
python-libpcap_0.6.2-0.2.diff.gz
to main/p/python-libpcap/python-libpcap_0.6.2-0.2.diff.gz
python-libpcap_0.6.2-0.2.dsc
to main/p/python-libpcap/python-libpcap_0.6.2-0.2.dsc
python-libpcap_0.6.2-0.2_i386.deb
to main/p/python-libpcap/python-libpcap_0.6.2-0.2_i386.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Shell Xu <[email protected]> (supplier of updated python-libpcap package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Mon, 30 Apr 2012 11:11:07 +0800
Source: python-libpcap
Binary: python-libpcap
Architecture: source i386
Version: 0.6.2-0.2
Distribution: unstable
Urgency: low
Maintainer: Thomas Bläsing <[email protected]>
Changed-By: Shell Xu <[email protected]>
Description:
python-libpcap - python libpcap wrapper
Closes: 656543
Changes:
python-libpcap (0.6.2-0.2) unstable; urgency=low
.
* Non-maintainer upload.
* (Closes: #656543) python-pypcap python-libpcap marked as conflict.
Checksums-Sha1:
beaf6363c1c7b509fd070c9b47a93aa2aa52972d 1281 python-libpcap_0.6.2-0.2.dsc
91f7da8ad583a4a6f5f41fc0930a6173e14e3ce1 2915 python-libpcap_0.6.2-0.2.diff.gz
91b49ffe356155a1237e079899de9e5e86ba0df8 58760
python-libpcap_0.6.2-0.2_i386.deb
Checksums-Sha256:
59da5f1bc64b960d91d5b45e6229bb1cdb8e01859121ea71d5f48ab4b1e261ad 1281
python-libpcap_0.6.2-0.2.dsc
a0f47e94afb26b74b858b8a51e1d03f0def4942ca1f9e6008e66b76071e6b8fd 2915
python-libpcap_0.6.2-0.2.diff.gz
f64603d11a51a8938bc0966068f23dac5ddac58ab1012978daa75d9dd4c5e603 58760
python-libpcap_0.6.2-0.2_i386.deb
Files:
51fb0ffaffc332dbe1513a8a7e42543f 1281 python optional
python-libpcap_0.6.2-0.2.dsc
0470062384f072a0bf27691f54e3219c 2915 python optional
python-libpcap_0.6.2-0.2.diff.gz
42e3a53b1c38ed66753e663625d86a68 58760 python optional
python-libpcap_0.6.2-0.2_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAk+eBjMACgkQ+MQbLPcULsLBQgCfYN8GjSgp2C0u/tK8cNUu8hyt
Qs4An1GdSqbsZgOrfLp6QeGh3ILvzRMj
=mXnm
-----END PGP SIGNATURE-----
--- End Message ---
