Summary: | I wrongly get "<net-ftp/vsftpd-2.0.3-r1 (is blocking net-ftp/ftpbase-0.00)" | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Peter Thomassen <mail> |
Component: | [OLD] Server | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED DUPLICATE | ||
Severity: | major | CC: | drjag, gentoo, kend, nes.yarug, rust710 |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Other | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Peter Thomassen
2005-06-29 14:26:17 UTC
Unmerge the old vsftpd version and emerge the new one. Portage is working OK. net-ftp/ftpbase-0.00 <snip> DEPEND="pam? ( || ( virtual/pam sys-libs/pam ) ) !<net-ftp/proftpd-1.2.10-r6 !<net-ftp/pure-ftpd-1.0.20-r2 !<net-ftp/vsftpd-2.0.3-r1" </snip> I think it is not working ok because the upgrade function aborts with the error I mentioned, but unmerging the old version an reemerging the new basically _is_ an upgrade. So why doesn't Portage ignore those dependency pseudo errors which are automatically solved after an upgrade? Why do I have to intervene? I first thougt this was a typo in ftpbase-0.00.ebuild which is why I assigned this to component Server, but I really think Portage could handle this in a better way. ... See Bug 79606. Portage won't handle this for you, sorry. *** This bug has been marked as a duplicate of 79606 *** *** Bug 97534 has been marked as a duplicate of this bug. *** *** Bug 100783 has been marked as a duplicate of this bug. *** *** Bug 102182 has been marked as a duplicate of this bug. *** *** Bug 104724 has been marked as a duplicate of this bug. *** *** Bug 157345 has been marked as a duplicate of this bug. *** |