On 22/03/11 23:18, Greg KH wrote:
On Tue, Mar 22, 2011 at 11:06:46PM +0000, Tejas
On 22/03/11 22:16, Greg KH 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,
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
In any case to link each package copying build numbers and checkin counts
look at bsynctag in package meta
and cicount in _link file.
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?
Defining Release: in the prjconf works
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.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-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
which will have release numbers >1000, probably greater than whatever is
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-factory+help(a)opensuse.org