Why do we have scapy and scapy3k and which do we keep?

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Why do we have scapy and scapy3k and which do we keep?

David C. Rankin
Archdevs,

  Attempting a system update tonight, I was hit with:

# pacman -Syu
...
looking for conflicting packages...
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: scapy3k and scapy are in conflict

  They both seem to be similar, but which one do we keep? There was never a
conflict before. I removed scapy3k, then curiously on one machine, it then
proceeded to reinstall, along with scapy. I don't know how either were
originally installed, I'd never heard of the package before the conflict
popped up.

  Which should be keep? Or was this a packaging hiccup?

--
David C. Rankin, J.D.,P.E.
Reply | Threaded
Open this post in threaded view
|

Re: Why do we have scapy and scapy3k and which do we keep?

beest
On Thu, Apr 05, 2018 at 09:53:36PM -0500, David C. Rankin wrote:

>   Attempting a system update tonight, I was hit with:
>
> # pacman -Syu
> ...
> looking for conflicting packages...
> error: unresolvable package conflicts detected
> error: failed to prepare transaction (conflicting dependencies)
> :: scapy3k and scapy are in conflict
>
>   They both seem to be similar, but which one do we keep? There was never a
> conflict before. I removed scapy3k, then curiously on one machine, it then
> proceeded to reinstall, along with scapy. I don't know how either were
> originally installed, I'd never heard of the package before the conflict
> popped up.
>
>   Which should be keep? Or was this a packaging hiccup?

AFAIR, scapy3k was a python3 fork of scapy. Now that scapy supports
python3, it has been added to the conflicts array of scapy3k. You can
probably safely remove scapy3k as nothing depends on it in the Arch
repos; check your system.