On Sat, Feb 22, 2014 at 11:50:36PM +0100, Guido Berhoerster wrote:
* Greg KH
[2014-02-22 23:41]: On Fri, Feb 21, 2014 at 12:26:16AM +0100, Guido Berhoerster wrote:
* Greg KH
[2014-02-21 00:21]: 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.
You can add a prefix to the release: http://en.opensuse.org/openSUSE:Build_Service_prjconf#Release
I'm not going to edit spec files, sorry, I rely on the build system to handle this by using 'osc setlinkrev'.
This is a setting in prjconf not spec files, it determines how the Release is inserted into the spec files by OBS.
And how would I do that for Tumbleweed? I don't want a "-tw" tag everywhere, do you? Or maybe that would be good to have, makes things more obvious as to where packages came from? thanks, greg k-h -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org