Am 21.02.2014 00:23, schrieb Greg KH:
On Thu, Feb 20, 2014 at 10:53:10PM +0100, Yamaban wrote:
On Thu, 20 Feb 2014 21:38, Greg KH
wrote: On Thu, Feb 20, 2014 at 07:38:29PM +0100, Christian Boltz wrote:
Am Mittwoch, 19. Februar 2014 schrieb Achim Gratz: <snip> That said - I wonder why this happens at all. Tumbleweed builds against 13.1:Update, so in theory OBS should ensure that the version number is always higher (or does this only work with _link'ed packages?).
We do use linked packages in Tumbleweed, but rebuild numbers do not cross OBS projects. And, after thinking about it for a while, you will see that this is a good thing, otherwise it would be totally crazy to try to work things out.
Preface: I'm no OBS guru.
That said: Is it possible to 'preset' the build numbers?
Not that I know of, sorry.
Hi Greg, The Release: field in the spec file is actually a minimum, but that is a bit too much work. If you link to a package, the release will be higher than the one in the link target - but only if you link plainly. Tumbleweed puts a rev in the _link file, which breaks this concept. To fix that you also need to include a vrev in your _link file. E.g. coolo@goneril#~>osc api /source/KDE:Release:412/amor?view=info <sourceinfo package="amor" rev="5" vrev="30" srcmd5="56369c0dd5120993abdea6278cef96e7" lsrcmd5="73552d985f98e9e614fafb438125f5b8" verifymd5="7aff2d609b5c805b1a7d29d1c59dc999"> <filename>amor.spec</filename> <linked project="KDE:Distro:Factory" package="amor" /> </sourceinfo> So amor in KDE prj has a release of 30 (vrev). So you put in your _link file rev="56369c0dd5120993abdea6278cef96e7" (you're already doing that) and vrev="31". Greetings, Stephan -- Ma muaß weiterkämpfen, kämpfen bis zum Umfalln, a wenn die ganze Welt an Arsch offen hat, oder grad deswegn. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org