[prev in list] [next in list] [prev in thread] [next in thread] 

List:       opensuse-factory
Subject:    Re: [opensuse-factory] Re: KDE 4.9 is now in Tumbleweed:Testing,
From:       Dimstar / Dominique Leuenberger <dimstar () opensuse ! org>
Date:       2012-11-20 20:35:07
Message-ID: 1353443707.3249.2.camel () laran ! leuenberger ! net
[Download RAW message or body]

On Tue, 2012-11-20 at 12:30 -0800, Greg KH wrote: 
> On Tue, Nov 20, 2012 at 08:46:08PM +0100, Jiri Slaby wrote:
> > On 11/20/2012 07:25 PM, Greg KH wrote:
> > > I do not know of any way to resolve this, does anyone else?
> > 
> > Maybe we can redefine release number to have precedence over others
> > and testing to have a bit lower than real tumbleweed. prjconf like
> > this should do this (untested):
> > In tumbleweed:
> > Release: tw1.<CI_CNT>.<B_CNT>
> > in tumblweed:testing:
> > Release: tw0.<CI_CNT>.<B_CNT>
> > 
> > Hmm, but then adding whatever is in tumbleweed into tumbleweed:testing
> > wouldn't dup packages from testing. Oh, testing should have higher
> > priority when people have testing enabled. So the above the other way
> > round?
> 
> Either way would help out when I have updated packages in tumbleweed,
> yet because of the build number being lower than what is in the 12.2
> repo, they never get updated.

CAREFUL:

prefixing the 'release' tag with tw will ALLWAYS make it lower than
12.2...

1.0-1 > 1.0-tw7.15

So you wouldn't win anything to what you have now (well, you would win
consistency.. all packages would always have a lower release and only
the version number would ever be considered).

Dominique

PS: you can conveniently use zypper to verify what is higher:
zypper vcmp 12.2-1.0 12.2-tw1.0

-- 
To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org
To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

[prev in list] [next in list] [prev in thread] [next in thread]