Mailinglist Archive: opensuse-factory (379 mails)

[Jiri Slaby <jslaby@xxxxxxx>]

On 04/05/2011 05:16 PM, Greg KH wrote:
> On Tue, Apr 05, 2011 at 05:04:32PM +0200, Marcus Meissner wrote:
> > On Tue, Apr 05, 2011 at 05:02:02PM +0200, Michael Schroeder wrote:
> > > On Tue, Apr 05, 2011 at 06:52:59AM -0700, Greg KH wrote:
> > > > On Tue, Apr 05, 2011 at 10:56:51AM +0200, Michael Schroeder wrote:
> > > > > On Mon, Apr 04, 2011 at 07:26:21PM -0700, Greg KH wrote:
> > > > > > But, for some library work, we will need to rebuild packages that are
> > > > > > identical to the 11.4 version, and I will use links, but how do you
> > > > > > create a "source link" that will keep the version number greater, than
> > > > > > the 11.4 one?
> > > > >
> > > > > You mean the release number? If it's a source link, the built
> > > > > packages will always have a bigger release number.
> > > >
> > > > Yes, the release number will always be the same, that's easy, it's the
> > > > "build number" that is the issue.  When linking a new package into
> > > > tumbleweed, the build number starts over and I know of no way to have it
> > > > start at a higher number other than to manually rebuild it multiple
> > > > times :(
> > >
> > > Hmm, the "checkin counter" of the resulting rpm (i.e. the first
> > > part of the release number) should be bigger than the 11.4 one.
> > > Do you have an example where this isn't the case?
> >
> > I think one issue is that Greg not just links to openSUSE:Factory,
> > but also to other devel projects.
>
> No, that's not the issue, when I do that, the main release number will
> always be bigger than what is in openSUSE:11.4 (otherwise why would it
> be an update?)
>
> The issue is when I link to packages in openSUSE:11.4.  When doing that,
> the build number is reset to start over and doesn't have any relation to
> the build number of the package in openSUSE:11.4.

I'm confused a bit by the terminology here. I'm not sure what do you
call a build number? In this example:
kernel-source-2.6.38-18.5.src.rpm
is build number == 5?

If that's the case, doesn't the _link where this is an issue contain a
cicount attribute? OBS should default to "add" behaviour so it should
add 1 to the original "build number". If you have cicount=local or copy
it will start over from 0 or be the same as linked package respectively.

regards,
-- 
js
suse labs
-- 
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx