Summary: | net-irc/unrealircd-3.2.7-r2 USE="curl ipv6" - incomplete die message | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Sebastian Meyer <public> |
Component: | New packages | Assignee: | Packages in net-irc <net-irc> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | kensington |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Sebastian Meyer
2008-12-15 12:31:20 UTC
Ok, my fault. I should learn the whole thing about words, sentences and so on (reading...) again ;-) The eerror contains IPv6 information, only the die-Message does not. Perhaps one could modify the die-Message? Another idea: Does the eerror mean, net-misc/curl did not support ipv6 when the ebuild was written or does it mean net-misc/curl with ipv6 is broken (for net-irc/unrealircd)? Recent versions of c-ares now support IPv6, so that restriction may be able to be lifted. The ebuild in the tree has been updated to use EAPI 2 so the die message in question no longer exists. As for whether the original condition triggering that message was valid or not, it has been changed in the proposed ebuild in #260806 As Michael mentioned, the ebuilds which have this problem are replaced and now aren't even in tree anymore. I fixed unrealircd to depend on curl[ares] too now (necessary so that the IRCd doesn't freeze on rehash when curl does synchronous hostname lookups). Thus, this issue should be gone :-). |