Summary: | Circular upgrade of kdelibs 3.1-r2 -> 3.1-r3 -> 3.1-r2 on '~x86' system with -uD option. | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Peter Beekman <pbeekm> |
Component: | Unclassified | Assignee: | Nicholas Jones (RETIRED) <carpaski> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | danarmak, ehmsen |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Peter Beekman
2003-03-13 08:38:33 UTC
This bug is caused because kdebase-3.1-r1 has a dependancy that was not updated to point to kdelibs-3.1-r3. the line -------------------------------- newdepend "=kde-base/kdelibs-3.1-r2" -------------------------------- should be changed to -------------------------------- newdepend "=kde-base/kdelibs-3.1-r3" -------------------------------- Can someone with cvs access change this? Thanks Naren Sankar I'm sorry about this situation. If only we had portage support for dep range specification, this wouldn't happen... I'm upgrading the kdebase dep to >=kdelibs-3.1-r2. That means kdelibs-5 (the cvs ebuild) will satisfy it too but better that than this problem for all the ~x86 profile ppl. This situation will be remedied when we (very soon) go to kde 3.1.1 and start from r0 again, but it could be created again... Now that we have 3.1.1, 3.1.1a and (soon) 3.1.2, this bug should not longer be valid. |