Bug#1008237: pcapy: Switch to pcapy-ng upstream

2022-03-25 Thread Emmanuel Arias
Hi!

Thanks for the report.

pcapy appears to be unmaintained, upstream contributions have moved to
> the pcapy-ng fork. The rename seems to only apply to the source, not the
> module, so it's a drop-in replacement.


Seems to be an easy issue to fix but IMHO seems to be new maintainers,
and probably follow a new way different to the original project, and we just
need to let it go.

I'd like to know if there was a similar situation before in Debian (I'll
look). Based
on that, perhaps we can make a decision.

Cheers
Emmanuel

>
> https://pypi.org/project/pcapy-ng/
> https://github.com/stamparm/pcapy-ng
>
> SR
>
>


Bug#1008237: pcapy: Switch to pcapy-ng upstream

2022-03-24 Thread Stefano Rivera
Source: pcapy
Version: 0.11.5-1
Severity: normal
Tags: upstream

pcapy appears to be unmaintained, upstream contributions have moved to
the pcapy-ng fork. The rename seems to only apply to the source, not the
module, so it's a drop-in replacement.

https://pypi.org/project/pcapy-ng/
https://github.com/stamparm/pcapy-ng

SR