Opened 14 years ago
Closed 14 years ago
#28447 closed defect (fixed)
unbound should not conflict with ldns
| Reported by: | arhbkb@… | Owned by: | nerdling (Jeremy Lavergne) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 1.9.2 |
| Keywords: | Cc: | deric@…, ryandesign (Ryan Carsten Schmidt) | |
| Port: | unbound |
Description
The current Unbound port (1.4.8) refuses to install on my system. It has a conflict with the ldns port. That doesn't make sense, because this Unbound port compiles with the built-in ldns. There's no reason for it to conflict against ldns compiled from ports.
I would like to be able to have both Unbound and ldns on my system, so please fix this port by removing the "conflicts" line.
Change History (3)
comment:1 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | snc@… removed |
|---|---|
| Owner: | changed from macports-tickets@… to snc@… |
| Summary: | Unbound 1.4.8 fails to install → unbound should not conflict with ldns |
comment:2 Changed 14 years ago by arhbkb@…
The problem has indeed been solved upstream. The unbound package links against the built-in ldns, so the conflicts line can be removed. Will someone please remove the conflicts line?
comment:3 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | ryandesign@… added |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
The conflicts line was added because the ports did in fact conflict; see #24014. But according to that, it looks like the conflict was resolved upstream.