Summary: | The ebuild "beecrypt" blocks "rpm" of which it is a dependancy | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | thegarbageman <isaachanson> |
Component: | Current packages | Assignee: | Aron Griffis (RETIRED) <agriffis> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | cretin |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
thegarbageman
2003-11-21 08:40:55 UTC
so do emerge -C rpm && emerge rpm This is correct, beecrypt only blocks the old rpm, not the new one. !<app-arch/rpm-4.2.1 is used not !<=app-arch/rpm-4.2.1 ( which would be the bug) This is the intended result, portage just cannot handle it automatically. Blocking ebuilds which provide the same files is standard practice. Aha. Understood. It might be helpful for me to mention that my confusion arose because I did not notice the "<" symbol, on the line notifying me of the "block", and I thought rpm-4.2.1 was being blocked. Perhaps it would be helpful if portage displayed each affected package instead: [blocks B ] app-arch/rpm-4.2_pre069 (from pkg dev-libs/beecrypt-3.1.0-r1) instead of: [blocks B ] <app-arch/rpm-4.2.1 (from pkg dev-libs/beecrypt-3.1.0-r1) Just a thought. Thanks for your help. |