Summary: | net-libs/gnutls-2.8.5 should specify dependency as >dev-scheme/guile-2.6.8[networking] | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Maciej Piechotka <uzytkownik2> |
Component: | [OLD] Library | Assignee: | Crypto team [DISABLED] <crypto+disabled> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | ecyoung |
Priority: | High | ||
Version: | 2008.0 | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://trac.pioto.org/paludis/ticket/781 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | patched ebuild for version 2.6.6 |
Description
Maciej Piechotka
2010-01-28 12:16:09 UTC
Maybe you should upgrade dev-scheme/guile, then. Two more recent versions than 1.6.8 are stable (. Otherwise it would be a paludis bug and you shouldn't be reporting it here. (In reply to comment #1) > Maybe you should upgrade dev-scheme/guile, then. Two more recent versions than > 1.6.8 are stable (. Otherwise it would be a paludis bug and you shouldn't be > reporting it here. > No - you misunderstood me. I have installed guile 1.8.x since a long time (I have ~amd64 system updated nearly daily), % ls -d /var/db/pkg/dev-scheme/guile-1.8.7/ /var/db/pkg/dev-scheme/guile-1.8.7/ As I explained already, in case the installed version isn't the problem, the problem would be in paludis, not in the ebuilds. So you shouldn't report it here but at http://paludis.pioto.org/ . Hmm. Paludis dev thinks it is problem with ebuild: http://trac.pioto.org/paludis/ticket/781 That explains it better. I understend that there is no 5 minute fixes but this bug's fix seems to not belong to much longer category. Created attachment 233457 [details]
patched ebuild for version 2.6.6
Why is this bug still open? Attached an updated ebuild for version 2.6.6 of gnutls
Fixed in 2.10.2-r1 and 2.11.4-r1 + 12 Nov 2010; Dane Smith <c1pher@gentoo.org> gnutls-2.10.2-r1.ebuild, + gnutls-2.11.4-r1.ebuild: + Changed guile dependency in 2.10.2-r1 and 2.11.4-r1 to be >=1.8 wrt bug + 302619. + (In reply to comment #6) > I understend that there is no 5 minute fixes but this bug's fix seems to not > belong to much longer category. > See bug 302033 for the ongoing situation... (In reply to comment #9) > (In reply to comment #6) > > I understend that there is no 5 minute fixes but this bug's fix seems to not > > belong to much longer category. > > > > See bug 302033 for the ongoing situation... > That should be bug 322033 Sorry |