On Tue, Mar 22, 2011 at 11:12 AM, Greg KH wrote:

On Tue, Mar 22, 2011 at 10:55:54AM -0400, Greg Freemyer wrote:

...

All,

I just initiated a "zypper dup --from Tumbleweed" and I get 8 packages it wants to download.

== The following packages are going to be downgraded:   libldb0 libtalloc2 libtalloc2-32bit libtdb1 libtdb1-32bit libtevent0 virtualbox virtualbox-qt ==

looking at virtualbox as a specific example, it looks like the vanilla 11.4 version is indeed newer.

...

sudo zypper se -s virtualbox | grep " virtualbox " i | virtualbox                             | package    | 4.0.4-1.2.3              | x86_64 | openSUSE-11.4 OSS v | virtualbox                             | package    | 4.0.4-1.2              | x86_64 | Tumbleweed v | virtualbox                             | package    | 4.0.4-1.2.3              | i586   | openSUSE-11.4 OSS v | virtualbox                             | package    | 4.0.4-1.2              | i586   | Tumbleweed   | virtualbox                             | srcpackage | 4.0.4-1.2              | noarch | Tumbleweed

Is there a problem with Tumbleweed?  I thought it should always have newer packages than OSS.

It "should" normally, but for virtualbox, I had to link to the current version in the tree, because our kernel updated, and you do want to be able to run the virtualbox kmp in our new kernel, right?

If you look close, the minor (i.e. build) number should just be smaller for virtualbox, not the version number, right?  So all should be fine, the package was just rebuilt for the Tumbleweed repo (i.e. against the newer kernel)

If not, let me know and I'll see what happened, as I did link to the openSUSE:Factory version of virtualbox, should I have grabbed a different one instead?

thanks,

greg k-h

Well, I'm not sure. Look at libtdb1 (zypper se -s libtdb1) For the main 11.4 OSS repo it's 1.2.1-2.17.1 For tumbleweed it's 1.2.1-2.1 I don't know the numbering nomenclature well enough to be sure, but that looks to me like tumbleweed is behind. If these are actually builds from the same source, it would be nice if zypper could be taught not to call them downgrades, but I'm not sure that's feasible. Greg -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

On Tue, Mar 22, 2011 at 01:28:26PM -0700, Greg KH wrote:

On Tue, Mar 22, 2011 at 04:15:41PM -0400, Greg Freemyer wrote:

...

On Tue, Mar 22, 2011 at 11:12 AM, Greg KH wrote:

...

On Tue, Mar 22, 2011 at 10:55:54AM -0400, Greg Freemyer wrote:

...

I just initiated a "zypper dup --from Tumbleweed" and I get 8 packages it wants to download.

== The following packages are going to be downgraded:   libldb0 libtalloc2 libtalloc2-32bit libtdb1 libtdb1-32bit libtevent0 virtualbox virtualbox-qt ==

looking at virtualbox as a specific example, it looks like the vanilla 11.4 version is indeed newer.

...

sudo zypper se -s virtualbox | grep " virtualbox " i | virtualbox                             | package    | 4.0.4-1.2.3              | x86_64 | openSUSE-11.4 OSS v | virtualbox                             | package    | 4.0.4-1.2              | x86_64 | Tumbleweed v | virtualbox                             | package    | 4.0.4-1.2.3              | i586   | openSUSE-11.4 OSS v | virtualbox                             | package    | 4.0.4-1.2              | i586   | Tumbleweed   | virtualbox                             | srcpackage | 4.0.4-1.2              | noarch | Tumbleweed

Is there a problem with Tumbleweed?  I thought it should always have newer packages than OSS.

It "should" normally, but for virtualbox, I had to link to the current version in the tree, because our kernel updated, and you do want to be able to run the virtualbox kmp in our new kernel, right?

If you look close, the minor (i.e. build) number should just be smaller for virtualbox, not the version number, right?  So all should be fine, the package was just rebuilt for the Tumbleweed repo (i.e. against the newer kernel)

If not, let me know and I'll see what happened, as I did link to the openSUSE:Factory version of virtualbox, should I have grabbed a different one instead?

Well, I'm not sure. Look at libtdb1 (zypper se -s libtdb1)

For the main 11.4 OSS repo it's 1.2.1-2.17.1

For tumbleweed it's 1.2.1-2.1

I don't know the numbering nomenclature well enough to be sure, but that looks to me like tumbleweed is behind.

It's not.

libtdb1 is a subpackage made from the Samba tar ball. At the time we moved with Samba to 3.5.8 I asked Greg to link Tumbleweed Samba to network:samba:STABLE. And the libtdb1 in version 1.2.1 from there has 30.1 as release number. Would it make sense for all packages living in Tumbleweed to add an additional subrelease - resulting for libtdb1 in 1.2.1-30.1.2 for example - while we - I hope the OBS is able to handle this with out any extra manual action - keep this digit strictly monotonous growing? Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany

On Tue, Mar 22, 2011 at 5:57 PM, Greg KH wrote:

On Tue, Mar 22, 2011 at 10:22:55PM +0100, Lars Müller wrote:

...

On Tue, Mar 22, 2011 at 01:28:26PM -0700, Greg KH wrote:

...

On Tue, Mar 22, 2011 at 04:15:41PM -0400, Greg Freemyer wrote:

...

On Tue, Mar 22, 2011 at 11:12 AM, Greg KH wrote:

...

On Tue, Mar 22, 2011 at 10:55:54AM -0400, Greg Freemyer wrote:

...

I just initiated a "zypper dup --from Tumbleweed" and I get 8 packages it wants to download.

== The following packages are going to be downgraded:   libldb0 libtalloc2 libtalloc2-32bit libtdb1 libtdb1-32bit libtevent0 virtualbox virtualbox-qt ==

looking at virtualbox as a specific example, it looks like the vanilla 11.4 version is indeed newer.

> sudo zypper se -s virtualbox | grep " virtualbox " i | virtualbox                             | package    | 4.0.4-1.2.3              | x86_64 | openSUSE-11.4 OSS v | virtualbox                             | package    | 4.0.4-1.2              | x86_64 | Tumbleweed v | virtualbox                             | package    | 4.0.4-1.2.3              | i586   | openSUSE-11.4 OSS v | virtualbox                             | package    | 4.0.4-1.2              | i586   | Tumbleweed   | virtualbox                             | srcpackage | 4.0.4-1.2              | noarch | Tumbleweed

Is there a problem with Tumbleweed?  I thought it should always have newer packages than OSS.

It "should" normally, but for virtualbox, I had to link to the current version in the tree, because our kernel updated, and you do want to be able to run the virtualbox kmp in our new kernel, right?

If you look close, the minor (i.e. build) number should just be smaller for virtualbox, not the version number, right?  So all should be fine, the package was just rebuilt for the Tumbleweed repo (i.e. against the newer kernel)

If not, let me know and I'll see what happened, as I did link to the openSUSE:Factory version of virtualbox, should I have grabbed a different one instead?

Well, I'm not sure. Look at libtdb1  (zypper se -s libtdb1)

For the main 11.4 OSS repo it's 1.2.1-2.17.1

For tumbleweed it's 1.2.1-2.1

I don't know the numbering nomenclature well enough to be sure, but that looks to me like tumbleweed is behind.

It's not.

libtdb1 is a subpackage made from the Samba tar ball.

Oops, wrong project :)

...

At the time we moved with Samba to 3.5.8 I asked Greg to link Tumbleweed Samba to network:samba:STABLE.

And the libtdb1 in version 1.2.1 from there has 30.1 as release number.

Would it make sense for all packages living in Tumbleweed to add an additional subrelease - resulting for libtdb1 in 1.2.1-30.1.2 for example - while we - I hope the OBS is able to handle this with out any extra manual action - keep this digit strictly monotonous growing?

I don't know how to do this with links in obs, does anyone else?

I don't think it's a real problem as it will only increase as time goes on, the next time this would come up would be after the next major openSUSE release when we add packages back to Tumbleweed again.

thanks,

greg k-h

Won't it happen anytime you (Greg KH) add a upgraded package to tumbleweed that has non-upgraded sub-packages? That's what triggered it for Samba's sub-package. I would think that was rather common. Greg -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

On 22/03/11 22:16, Greg KH wrote:

...

Won't it happen anytime you (Greg KH) add a upgraded package to tumbleweed that has non-upgraded sub-packages?

That's what triggered it for Samba's sub-package.

I would think that was rather common. I don't know how common it is for projects to have "multiple" parts like

On Tue, Mar 22, 2011 at 06:03:02PM -0400, Greg Freemyer wrote: this, do you?

Anyway, zypper handles everything properly, so it should be fine.

Unless someone knows how to artifically bump up the build number that doesn't involve me rebuilding the package multiple times? :)

thanks,

greg k-h OBS starts the release number from the one specified in the spec file, so if each package had "Release:" >= its final 11.4 value, that might work. Or to do this globally, in the Tumbleweed project config, you could redefine release from %checkin_count.%build_count to something like tw.%ci_count.%build_count (tw for tumbleweed, like packman does, though i've not tested if this would compare as desired).

Regards, Tejas -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

On 22/03/11 23:18, Greg KH wrote:

On Tue, Mar 22, 2011 at 11:06:46PM +0000, Tejas Guruswamy wrote:

...

...

I don't know how common it is for projects to have "multiple" parts like this, do you?

Anyway, zypper handles everything properly, so it should be fine.

Unless someone knows how to artifically bump up the build number that doesn't involve me rebuilding the package multiple times? :) OBS starts the release number from the one specified in the spec file, so if each package had "Release:"> its final 11.4 value,

On 22/03/11 22:16, Greg KH wrote: that might work. No, it overwrites the release number, try it and see :) Hmm, I'm sure I read somewhere it should do this ... for example adrian here http://lists.opensuse.org/opensuse-buildservice/2010-08/msg00117.html

In any case to link each package copying build numbers and checkin counts look at bsynctag in package meta and cicount in _link file. see http://lists.opensuse.org/opensuse-buildservice/2009-12/msg00166.html and example of glibc.i686 in openSUSE:Factory

...

Or to do this globally, in the Tumbleweed project config, you could redefine release from %checkin_count.%build_count to something like tw.%ci_count.%build_count (tw for tumbleweed, like packman does, though i've not tested if this would compare as desired). Hm, I don't know if we want to mark the packages all with a "tw" but it might make sense to.

Care to provide the line in the config that would do this?

thanks,

greg k-h Defining Release: in the prjconf works Release: ..%%{?dist}

but still compares less than equivalent 11.4 release if the release is less

zypper versioncmp a-4.5-1.0.tw.i586.rpm a-4.5-1.1.i586.rpm # a-4.5-1.0.tw.i586.rpm is older than a-4.5-1.1.i586.rpm

zypper versioncmp a-4.5-tw.1.0.i586.rpm a-4.5-1.1.i586.rpm # a-4.5-tw.1.0.i586.rpm is older than a-4.5-1.1.i586.rpm

so if you want to do it this way maybe the only solution is to do something like Release: 100. which will have release numbers >1000, probably greater than whatever is in 11.4. Regards, Tejas -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org

On Tue, 22 Mar 2011, Greg KH wrote:

Hm, I don't know if we want to mark the packages all with a "tw" but it might make sense to.

I like the idea! FWIW, Fedora does that, too, with all their packages (where if something is not changed, you may have a few .fc12 and .fc13 packages in your addition to load of .fc14 when running Fedora 14). Gerald -- Dr. Gerald Pfeifer Director Product Management, SUSE Linux Enterprise, openSUSE, Appliances -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org