Ticket #12321 (new defect)
libnet and libnet11 conflict
| Reported by: | bahamat@… | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | Cc: | jim@…, pmq@…, etherflan@…, snc@…, ryandesign@…, vh3@…, kngspook@… | |
| Port: | libnet, libnet11 |
Description
I use both dsniff and arping for work, but dsniff depends on libnet and arping depends on libnet11. Libnet and libnet11 can't be installed simultaneously.
Change History
comment:1 Changed 6 years ago by pmq@…
- Priority changed from Blocker to Important
- Cc jim@…, pmq@…, bahamat@… added
- Summary changed from dsniff depends on libnet, arping depends on libnet11 to BUG: libnet and libnet11 conflict
- Milestone set to Port Bugs
comment:2 Changed 6 years ago by nox@…
- Cc changed from jim@geovedi.com,pmq@macports.org,bahamat@digitalelf.net to jim@geovedi.com, pmq@macports.org, bahamat@digitalelf.net
- Priority changed from Important to Normal
- Version 1.5.0 deleted
comment:6 Changed 4 years ago by snc@…
- Owner changed from macports-tickets@… to snc@…
- Status changed from new to assigned
comment:7 Changed 4 years ago by snc@…
- Cc snc@… added
- Status changed from assigned to new
- Owner changed from snc@… to macports-tickets@…
comment:9 in reply to: ↑ description Changed 3 years ago by ryandesign@…
- Cc ryandesign@… added
- Summary changed from BUG: libnet and libnet11 conflict to libnet and libnet11 conflict
comment:12 Changed 2 months ago by snc@…
Have there been updates for packages that depend on libnet so they can handle libnet11? Libnet 1.2 is now available upstream: should I make another (conflicting) libnet12 so that people can upgrade when their packages are ready?
Note: See
TracTickets for help on using
tickets.
Cc'ing the libnet maintainer. Unless someone releases its private dsniff-on-libnet11 patch, we need to fix the ports just like apr/apr0.