[opensuse-buildservice] release numbering
Hi, just right now I've updated a few packages but release number generation seems to be heavily confused. It's ignoring Release in spec file, it doesn't count changes within the first digit but only rebuilds in the second one. And it reset the release number to 1 so I don't get the updated package. That's a critical thing, please help. Wolfgang -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
The release number generated by OBS contains too numbers, checkin_count and build_count. checkin_count is only incremented when a commit is made to an OBS package, the build_count is incremented for any rebuild of that checkin_count. The default format for the replacement of the Release line of the spec can be altered by adding a Release: <CI_CNT>.<B_CNT> tag to the prjconf meta data for the project in which your package is building. It would be helpful to now your project/package so we could look at your specific log files. On Tue, 2009-12-15 at 04:06 -0600, Wolfgang Rosenauer wrote:
Hi,
just right now I've updated a few packages but release number generation seems to be heavily confused. It's ignoring Release in spec file, it doesn't count changes within the first digit but only rebuilds in the second one. And it reset the release number to 1 so I don't get the updated package.
That's a critical thing, please help.
Wolfgang
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Dienstag, 15. Dezember 2009 13:17:37 schrieb Luke Imhoff:
The release number generated by OBS contains too numbers, checkin_count and build_count. checkin_count is only incremented when a commit is made to an OBS package, the build_count is incremented for any rebuild of that checkin_count. The default format for the replacement of the Release line of the spec can be altered by adding a
Release: <CI_CNT>.<B_CNT>
tag to the prjconf meta data for the project in which your package is building. It would be helpful to now your project/package so we could look at your specific log files.
Yes, but this should not be needed to touch (and you can even cause problems here). However, is it important for you to set the number to keep two independend builds in sync ? We have a special feature for that. You can rename your sync tag, so for example package X and Y use the same tag Z, which means the build numbers (B_CNT) are always kept in sync. You can see an example in osc meta pkg openSUSE:Factory glibc.i686 which is enforced to keep in sync with glibc package. You need also to keep the CI_CNT in sync. This can be specified in source links, just check the link in that package as well osc cat openSUSE:Factory glibc.i686 _link the cicount="copy" parameter is doing this. bye adrian
On Tue, 2009-12-15 at 04:06 -0600, Wolfgang Rosenauer wrote:
Hi,
just right now I've updated a few packages but release number generation seems to be heavily confused. It's ignoring Release in spec file, it doesn't count changes within the first digit but only rebuilds in the second one. And it reset the release number to 1 so I don't get the updated package.
That's a critical thing, please help.
Wolfgang
-- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 12/15/2009 01:17 PM, Luke Imhoff wrote:
The release number generated by OBS contains too numbers, checkin_count and build_count. checkin_count is only incremented when a commit is made to an OBS package, the build_count is incremented for any rebuild of that checkin_count. The default format for the replacement of the Release line of the spec can be altered by adding a
It's about mozilla/MozillaFirefox-branding-openSUSE and I basically know how that works. The issue is that I modified the package and the checkin_count went to 1 for whatever reason (also the build_count but that makes sense). Also specifying "Release: 19" in the specfile and commit an updated version didn't change the checkin_count to 19 (or even 2). Meanwhile the checkin_count increased again a bit (to 3). Wolfgang -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Dienstag, 15. Dezember 2009 13:46:59 schrieb Wolfgang Rosenauer:
On 12/15/2009 01:17 PM, Luke Imhoff wrote:
The release number generated by OBS contains too numbers, checkin_count and build_count. checkin_count is only incremented when a commit is made to an OBS package, the build_count is incremented for any rebuild of that checkin_count. The default format for the replacement of the Release line of the spec can be altered by adding a
It's about mozilla/MozillaFirefox-branding-openSUSE
and I basically know how that works. The issue is that I modified the package and the checkin_count went to 1 for whatever reason (also the build_count but that makes sense). Also specifying "Release: 19" in the specfile and commit an updated version didn't change the checkin_count to 19 (or even 2). Meanwhile the checkin_count increased again a bit (to 3).
Sorry, you just found a very new introduced bug (yesterday afternoon). It is fixed now. You will get a correct numbering again on next checkin. Just make any dummy change. sorry for that. adrian -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (3)
-
Adrian Schröter -
Luke Imhoff -
Wolfgang Rosenauer