Summary: | Stable request: app-misc/beagle-0.3.7-r1 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Arun Raghavan (RETIRED) <ford_prefect> |
Component: | [OLD] Unspecified | Assignee: | Cédric Krier <cedk> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | magowiz, nirbheek, pacho |
Priority: | High | Keywords: | STABLEREQ |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 210447, 230175, 230177, 230179, 230181 | ||
Bug Blocks: | 229717 |
Description
Arun Raghavan (RETIRED)
2008-06-30 13:10:13 UTC
Add archs What about bug #210447? Add to depends. I was not aware of this issue. ppc stable Seems that this must be stabilized at the same time than gnome-2.22 and latest evolution-sharp, if I add beagle-0.3.7-r1 to my package.keywords I get: !!! Multiple versions within a single package slot have been !!! pulled into the dependency graph: app-misc/beagle:0 ('installed', '/', 'app-misc/beagle-0.2.18-r1', 'nomerge') pulled in by ('installed', '/', 'app-cdr/brasero-0.7.1', 'nomerge') ('ebuild', '/', 'app-misc/beagle-0.3.7-r1', 'merge') pulled in by ('installed', '/', 'gnome-extra/yelp-2.20.0', 'nomerge') ('installed', '/', 'gnome-base/nautilus-2.20.0-r1', 'nomerge') I thought that portage would simply keep on 0.2.18-r1 instead of failling but seems that this is the current behavior :-/ ping? (In reply to comment #5) > Seems that this must be stabilized at the same time than gnome-2.22 and latest > evolution-sharp, if I add beagle-0.3.7-r1 to my package.keywords I get: > !!! Multiple versions within a single package slot have been > !!! pulled into the dependency graph: > > app-misc/beagle:0 > > ('installed', '/', 'app-misc/beagle-0.2.18-r1', 'nomerge') pulled in by > ('installed', '/', 'app-cdr/brasero-0.7.1', 'nomerge') > > ('ebuild', '/', 'app-misc/beagle-0.3.7-r1', 'merge') pulled in by > ('installed', '/', 'gnome-extra/yelp-2.20.0', 'nomerge') > ('installed', '/', 'gnome-base/nautilus-2.20.0-r1', 'nomerge') > > > I thought that portage would simply keep on 0.2.18-r1 instead of failling but > seems that this is the current behavior :-/ > This was my own problem because of an old nautilus ebuild in my local overlay (bug 232496). Sorry (In reply to comment #6) > ping? The kerry bug (210447) has a patch ready. As soon as that is applied and a stable version availabl, you can just go on. Worked fine here with all depending bugs. (In reply to comment #8) [...] > The kerry bug (210447) has a patch ready. As soon as that is applied and a > stable version availabl, you can just go on. Worked fine here with all > depending bugs. Considering that there is no current stable version of kerry in tree, is this really a blocker for beagle stabilization? *** Bug 229389 has been marked as a duplicate of this bug. *** amd64 done x86 stable, closing |