| Summary: | wrong dependencies for 3.5.0_beta2 split ebuilds depending on 3.5_beta1 ebuilds | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Hans-Christian Armingeon <mog.johnny> |
| Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | jdaluz |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Hans-Christian Armingeon
2005-10-19 07:32:55 UTC
The problem is more general, it seems that $(deprange 3.5_beta1 3.5.0_beta2) doesn't work as expected... any ideas? *** Bug 109888 has been marked as a duplicate of this bug. *** It definitely works here, and for everyone else I've spoken to so far. It shouldn't matter, but perhaps try emerge --regen. BTW, #109888 isn't exactly a dup of this - it looks there as though the reporter has an old kde-functions.eclass. well, I changed =kde-base/kde-meta-3.5.0_beta2 line to kde-base/kde-meta and now it works. Johnny I was the reporter on 109888. After reading this bug, I tried emerge --regen and saw this issue pop up with 10-12 kde packages, but not kcontrol (which I had reported). I also noticed a big slowdown when the regen hit the kde packages, which eventually made me realize the problem: Gentopia. I had removed Gentopia from my PORTDIR_OVERLAY when kde 3.5_beta1 came out because they, for some godforsaken reason, decided to release the beta1 ebuilds *after* they were already in portage (masked), and I copied the few Gentopia packages I used into a separate overlay. When beta2 came out I thought that I could include them again, but doing so seems to be why the obsolete eclass is showing up. Removing them from the overlay removes the problem. Reopen to dupe... |