[gentoo-dev] is gnome2.2 in stable or not?

[gentoo-dev] is gnome2.2 in stable or not?

[Alan]

Just wondering if gnome 2.2 is supposed to be in stable or not?  I
notice that the main gnome package is updated to 2.2 (on x86) but many
of the dependancies (gst-plugins, gstreamer, etc) are still tagged as
~x86, and are giving me errors like the following when I try an update
world:

phoenix alan # emerge world -up

These are the packages that I would merge, in order:

Calculating world dependencies \
!!! all ebuilds that could satisfy ">=media-libs/gst-plugins-0.6.0-r1"
have been masked.
!!!    (dependency required by "gnome-base/gnome-2.2-r1" [ebuild])
phoenix alan #

Is this something that should be bugged, an oversight, or am I coming in
the middle of the transition and should wait a bit before trying?

Another possibility is that my portage tree is messed up somehow, but
several emerge syncs give me the same result.

TIA

Alan

-- 
Alan <alan@ufies.org> - http://arcterex.net
---------------------------------------------------------------------
"The only thing that experience teaches us is that experience teaches 
us nothing.	        -- Andre Maurois (Emile Herzog)

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] is gnome2.2 in stable or not?

[Ingo Krabbe]

This sounds to me exactly as the error means:
gnome2.2 is stable but some of the dependancies aren't so if you want to
update to gnome2.2 you have either to accept beta packages or stream
down the gnome2.2 if you can mask out one or some other package from the
dependancy list.

Since gnome2.2 should be some kind of virtual package it shouldn't be
stable until all of its dependancies are. So this also could be
understood as an error.

BUT ! The dependancies might vary by change of use flags.  So gnome2.2
could be called stable once all possible use variations that effect its
dependancy tree will also mask completly stable.

This sounds like a hard rule for a real intelligent software.

At least it turns out that YOU are the most intelligent part in that
process, so you have to tune on that error, not your software.  I fear
that you have to accept that gnome2.2 isn't stable for you yet, so you
should mask itself out with ~x86 (in you personal portage tree) or
accept beta packages at least to emerge -u gnome.

But that's only my opinion: I would vote against calling this an error
actually.

BYE INGO

On Mon, Feb 10, 2003 at 11:46:23AM -0800, Alan wrote:
> Just wondering if gnome 2.2 is supposed to be in stable or not?  I
> notice that the main gnome package is updated to 2.2 (on x86) but many
> of the dependancies (gst-plugins, gstreamer, etc) are still tagged as
> ~x86, and are giving me errors like the following when I try an update
> world:
> 
> phoenix alan # emerge world -up
> 
> These are the packages that I would merge, in order:
> 
> Calculating world dependencies \
> !!! all ebuilds that could satisfy ">=media-libs/gst-plugins-0.6.0-r1"
> have been masked.
> !!!    (dependency required by "gnome-base/gnome-2.2-r1" [ebuild])
> phoenix alan #
> 
> Is this something that should be bugged, an oversight, or am I coming in
> the middle of the transition and should wait a bit before trying?
> 
> Another possibility is that my portage tree is messed up somehow, but
> several emerge syncs give me the same result.
> 
> TIA
> 
> Alan
> 
> -- 
> Alan <alan@ufies.org> - http://arcterex.net
> ---------------------------------------------------------------------
> "The only thing that experience teaches us is that experience teaches 
> us nothing.	        -- Andre Maurois (Emile Herzog)
> 
> --
> gentoo-dev@gentoo.org mailing list
> 
> 

----- End forwarded message -----

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] is gnome2.2 in stable or not?

[Alan]

On Mon, Feb 10, 2003 at 08:58:56PM +0100, Ingo Krabbe wrote:
> This sounds to me exactly as the error means:
> gnome2.2 is stable but some of the dependancies aren't so if you want to
> update to gnome2.2 you have either to accept beta packages or stream
> down the gnome2.2 if you can mask out one or some other package from the
> dependancy list.
> 
> Since gnome2.2 should be some kind of virtual package it shouldn't be
> stable until all of its dependancies are. So this also could be
> understood as an error.
> 
> BUT ! The dependancies might vary by change of use flags.  So gnome2.2
> could be called stable once all possible use variations that effect its
> dependancy tree will also mask completly stable.
> 
> This sounds like a hard rule for a real intelligent software.
> 
> At least it turns out that YOU are the most intelligent part in that
> process, so you have to tune on that error, not your software.  I fear
> that you have to accept that gnome2.2 isn't stable for you yet, so you
> should mask itself out with ~x86 (in you personal portage tree) or
> accept beta packages at least to emerge -u gnome.
> 
> But that's only my opinion: I would vote against calling this an error
> actually.

Yes, I came the the same conclusions.  It just seems strange that all
packages are not set to stable when the main meta package (gnome) is.
Normally things that cause those sorts of problems stay away from
stable. 

-- 
Alan <alan@ufies.org> - http://arcterex.net
---------------------------------------------------------------------
"The only thing that experience teaches us is that experience teaches 
us nothing.	        -- Andre Maurois (Emile Herzog)

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] is gnome2.2 in stable or not?

[foser]

gnome 2.2 is stable and marked as such for x86, as announced on the 
mainpage. And the gnome meta package has been marked stable as last 
package after all of it's deps, so i dunno what's going on your side but 
it's no good. Either you getting your tree from a faulty rsync or you 
might see problems like in bug #15436 due to a GRP install (something 
which should be looked into).

- foser

Alan wrote:
> On Mon, Feb 10, 2003 at 08:58:56PM +0100, Ingo Krabbe wrote:
> 
>>This sounds to me exactly as the error means:
>>gnome2.2 is stable but some of the dependancies aren't so if you want to
>>update to gnome2.2 you have either to accept beta packages or stream
>>down the gnome2.2 if you can mask out one or some other package from the
>>dependancy list.
>>
>>Since gnome2.2 should be some kind of virtual package it shouldn't be
>>stable until all of its dependancies are. So this also could be
>>understood as an error.
>>
>>BUT ! The dependancies might vary by change of use flags.  So gnome2.2
>>could be called stable once all possible use variations that effect its
>>dependancy tree will also mask completly stable.
>>
>>This sounds like a hard rule for a real intelligent software.
>>
>>At least it turns out that YOU are the most intelligent part in that
>>process, so you have to tune on that error, not your software.  I fear
>>that you have to accept that gnome2.2 isn't stable for you yet, so you
>>should mask itself out with ~x86 (in you personal portage tree) or
>>accept beta packages at least to emerge -u gnome.
>>
>>But that's only my opinion: I would vote against calling this an error
>>actually.
> 
> 
> Yes, I came the the same conclusions.  It just seems strange that all
> packages are not set to stable when the main meta package (gnome) is.
> Normally things that cause those sorts of problems stay away from
> stable. 
> 



--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] is gnome2.2 in stable or not?

[Alan]

On Tue, Feb 11, 2003 at 01:21:51AM +0100, foser wrote:
> gnome 2.2 is stable and marked as such for x86, as announced on the 
> mainpage. And the gnome meta package has been marked stable as last 
> package after all of it's deps, so i dunno what's going on your side but 
> it's no good. Either you getting your tree from a faulty rsync or you 
> might see problems like in bug #15436 due to a GRP install (something 
> which should be looked into).

I'm thinking that something might be messed up with my setup here.  


phoenix alan # emerge world -up

These are the packages that I would merge, in order:

Calculating world dependencies \
!!! all ebuilds that could satisfy ">=media-libs/gst-plugins-0.6.0-r1"
have been masked.
!!!    (dependency required by "gnome-base/gnome-2.2-r1" [ebuild])

Ok, so gst-plugins is masked, what version do I have:

phoenix alan # emerge -s gst-plugins
Searching...
[ Results for search key : gst-plugins ]
[ Applications found : 1 ]

*  media-libs/gst-plugins
   Latest version available: 0.5.2
   Latest version installed: 0.4.2-r2
	[...]

phoenix alan # grep KEYWORDS /usr/portage/media-libs/gst-plugins/gst-plugins-0.6.0-r1.ebuild
KEYWORDS="x86 ~sparc ~ppc"
phoenix alan # grep gst-plugins /usr/portage/profiles/package.mask
phoenix alan #

I don't have ACCEPT_KEYWORDS set to anything, so I'm wondering why a
stable gst-plugins (and others as I'm looking through various ebuilds)
isn't being caught by portage.

Is there a recommended way of fixing this, rebuilding my portage cache
other than an emerge sync (just did one, no change).

alan

-- 
Alan <alan@ufies.org> - http://arcterex.net
---------------------------------------------------------------------
"The only thing that experience teaches us is that experience teaches 
us nothing.	        -- Andre Maurois (Emile Herzog)

--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] is gnome2.2 in stable or not?

[foser]

Alan wrote:
> On Tue, Feb 11, 2003 at 01:21:51AM +0100, foser wrote:
> 
>>gnome 2.2 is stable and marked as such for x86, as announced on the 
>>mainpage. And the gnome meta package has been marked stable as last 
>>package after all of it's deps, so i dunno what's going on your side but 
>>it's no good. Either you getting your tree from a faulty rsync or you 
>>might see problems like in bug #15436 due to a GRP install (something 
>>which should be looked into).
> 
> 
> I'm thinking that something might be messed up with my setup here.  
> 
> 
> phoenix alan # emerge world -up
> 
> These are the packages that I would merge, in order:
> 
> Calculating world dependencies \
> !!! all ebuilds that could satisfy ">=media-libs/gst-plugins-0.6.0-r1"
> have been masked.
> !!!    (dependency required by "gnome-base/gnome-2.2-r1" [ebuild])
> 
> Ok, so gst-plugins is masked, what version do I have:
> 
> phoenix alan # emerge -s gst-plugins
> Searching...
> [ Results for search key : gst-plugins ]
> [ Applications found : 1 ]
> 
> *  media-libs/gst-plugins
>    Latest version available: 0.5.2
>    Latest version installed: 0.4.2-r2
> 	[...]
> 
> phoenix alan # grep KEYWORDS /usr/portage/media-libs/gst-plugins/gst-plugins-0.6.0-r1.ebuild
> KEYWORDS="x86 ~sparc ~ppc"
> phoenix alan # grep gst-plugins /usr/portage/profiles/package.mask
> phoenix alan #
> 
> I don't have ACCEPT_KEYWORDS set to anything, so I'm wondering why a
> stable gst-plugins (and others as I'm looking through various ebuilds)
> isn't being caught by portage.
> 
> Is there a recommended way of fixing this, rebuilding my portage cache
> other than an emerge sync (just did one, no change).
> 

see the bugreport i mentioned


--
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] is gnome2.2 in stable or not?

[Alan]

> >>gnome 2.2 is stable and marked as such for x86, as announced on the 
> >>mainpage. And the gnome meta package has been marked stable as last 
> >>package after all of it's deps, so i dunno what's going on your side but 
> >>it's no good. Either you getting your tree from a faulty rsync or you 
> >>might see problems like in bug #15436 due to a GRP install (something 
> >>which should be looked into).
> >Is there a recommended way of fixing this, rebuilding my portage cache
> >other than an emerge sync (just did one, no change).
> see the bugreport i mentioned

Duh, my bad, yes, removing the /var/cache/edb/dep/* files forced a
rebuild of my deps and all is well, with gnome2.2 compiling in the
background.  Thanks!

alan
-- 
Alan <alan@ufies.org> - http://arcterex.net
---------------------------------------------------------------------
"The only thing that experience teaches us is that experience teaches 
us nothing.	        -- Andre Maurois (Emile Herzog)

--
gentoo-dev@gentoo.org mailing list

RE: [gentoo-dev] is gnome2.2 in stable or not?

[Yavor Goulishev]

Hi,
Why portage-20030208.tar.bz2 doesn't contain gnome-2.2-r1.ebuild ?
This is the latest snapshot available.

$ls -l /usr/portage/gnome-base/gnome
total 68
-rw-r--r--    1 574      574          9729 Feb  6 15:13 ChangeLog
drwxr-xr-x    2 4040     4034         4096 Feb 11 12:25 files
-rw-r--r--    1 574      574           544 Dec  9 15:25 gnome-1.4-r3.ebuild
-rw-r--r--    1 574      574          2520 Oct  4 08:33 gnome-2.0.0-r2.ebuild
-rw-r--r--    1 574      574          2307 Oct  4 08:33 gnome-2.0.0.ebuild
-rw-r--r--    1 574      574          2493 Oct  4 08:33 gnome-2.0.1.ebuild
-rw-r--r--    1 574      574          2491 Oct  4 08:33 gnome-2.0.1_rc1.ebuild
-rw-r--r--    1 574      574          2506 Dec 15 12:44 gnome-2.0.2-r1.ebuild
-rw-r--r--    1 574      574          2592 Dec 15 12:44 gnome-2.0.2-r2.ebuild
-rw-r--r--    1 574      574          2501 Dec  9 06:22 gnome-2.0.2.ebuild
-rw-r--r--    1 574      574          2582 Jan 18 14:39 gnome-2.0.3-r1.ebuild
-rw-r--r--    1 574      574          2586 Dec 15 14:35 gnome-2.0.3.ebuild
-rw-r--r--    1 574      574          3265 Feb  6 15:13 gnome-2.2.ebuild
-rw-r--r--    1 574      574          3240 Feb  6 02:24 gnome-2.2_rc2-r99.ebuild
-rw-r--r--    1 574      574          3159 Feb  3 15:10 gnome-2.2_rc2.ebuild

Best Regards, Yavor Goulishev



--
gentoo-dev@gentoo.org mailing list