Bug 230185 – Stable request: app-misc/beagle-0.3.7-r1

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Arun Raghavan (RETIRED) 2008-06-30 13:10:13 UTC]

This is a tracker request for stabling app-misc/beagle-0.3.7 since none of the 0.3 ebuilds are stable. The ebuild has been in tree since 28 May 2008. No outstanding bugs are open against this version.

Note that this is only really useful once Gnome 2.22 goes stable since nautilus-2.20 and yelp-2.20 from the currentl stable Gnome 2.20 will force beagle-0.2*.

Reproducible: Always

[Comment 1 Cédric Krier 2008-07-07 20:14:31 UTC]

Add archs

[Comment 2 Thomas Anderson (tanderson) (RETIRED) 2008-07-08 20:38:17 UTC]

What about bug #210447?

[Comment 3 Cédric Krier 2008-07-08 22:20:22 UTC]

Add to depends. I was not aware of this issue.

[Comment 4 nixnut (RETIRED) 2008-07-16 12:57:42 UTC]

ppc stable

[Comment 5 Pacho Ramos 2008-07-20 16:50:53 UTC]

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 :-/

[Comment 6 Raúl Porcel (RETIRED) 2008-07-24 17:17:42 UTC]

ping?

[Comment 7 Pacho Ramos 2008-07-24 18:26:31 UTC]

(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

[Comment 8 Christian Faulhammer (RETIRED) 2008-07-25 00:04:08 UTC]

(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.

[Comment 9 Arun Raghavan (RETIRED) 2008-07-25 07:02:18 UTC]

(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?

[Comment 10 Pacho Ramos 2008-07-27 17:39:01 UTC]

*** Bug 229389 has been marked as a duplicate of this bug. ***

[Comment 11 Olivier Crete (RETIRED) 2008-07-27 22:51:36 UTC]

amd64 done

[Comment 12 Raúl Porcel (RETIRED) 2008-07-28 15:48:18 UTC]

x86 stable, closing