[opensuse-buildservice] OBS: set release number of package?
Is there a way to tell the OBS to set the release number of a package to some arbitrary number (or to increase it by some number)? For example, let's say foo version 1.0 and has been checked in 3 times and rebuilt twice. I think the package would then be foo-1.0-3.2.$arch.rpm. Let's say I'd like to set the check in count to 5 (and reset the build count). Is there an easy way to do this without /actually/ checking in a number of dummy commits? -- Jon -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 2010-08-17 09:54:00 -0500, Jon Nelson wrote:
Is there a way to tell the OBS to set the release number of a package to some arbitrary number (or to increase it by some number)?
For example, let's say foo version 1.0 and has been checked in 3 times and rebuilt twice. I think the package would then be foo-1.0-3.2.$arch.rpm. Let's say I'd like to set the check in count to 5 (and reset the build count). Is there an easy way to do this without /actually/ checking in a number of dummy commits?
check in a spec that has Release: 5 darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Tue, Aug 17, 2010 at 9:55 AM, Marcus Rueckert
On 2010-08-17 09:54:00 -0500, Jon Nelson wrote:
Is there a way to tell the OBS to set the release number of a package to some arbitrary number (or to increase it by some number)?
For example, let's say foo version 1.0 and has been checked in 3 times and rebuilt twice. I think the package would then be foo-1.0-3.2.$arch.rpm. Let's say I'd like to set the check in count to 5 (and reset the build count). Is there an easy way to do this without /actually/ checking in a number of dummy commits?
check in a spec that has Release: 5
According to the docs here:
http://en.opensuse.org/openSUSE:Build_Service_Tips_and_Tricks#How_to_control...
The release field in the spec file is ignored and replaced by
On Tuesday 17 August 2010 17:01:15 Jon Nelson wrote:
On Tue, Aug 17, 2010 at 9:55 AM, Marcus Rueckert
wrote: On 2010-08-17 09:54:00 -0500, Jon Nelson wrote:
Is there a way to tell the OBS to set the release number of a package to some arbitrary number (or to increase it by some number)?
For example, let's say foo version 1.0 and has been checked in 3 times and rebuilt twice. I think the package would then be foo-1.0-3.2.$arch.rpm. Let's say I'd like to set the check in count to 5 (and reset the build count). Is there an easy way to do this without /actually/ checking in a number of dummy commits?
check in a spec that has Release: 5
According to the docs here:
http://en.opensuse.org/openSUSE:Build_Service_Tips_and_Tricks#How_to_control...
The release field in the spec file is ignored and replaced by
. , where represents the check-in count and represents the build count. Is that not accurate?
it is correct. But if the release number in the spec file is higher than CI_CNT, CI_CNT will get increased to its value. bye 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
On Tue, Aug 17, 2010 at 10:10 AM, Adrian Schröter
On Tuesday 17 August 2010 17:01:15 Jon Nelson wrote:
On Tue, Aug 17, 2010 at 9:55 AM, Marcus Rueckert
wrote: On 2010-08-17 09:54:00 -0500, Jon Nelson wrote:
Is there a way to tell the OBS to set the release number of a package to some arbitrary number (or to increase it by some number)?
For example, let's say foo version 1.0 and has been checked in 3 times and rebuilt twice. I think the package would then be foo-1.0-3.2.$arch.rpm. Let's say I'd like to set the check in count to 5 (and reset the build count). Is there an easy way to do this without /actually/ checking in a number of dummy commits?
check in a spec that has Release: 5
According to the docs here:
http://en.opensuse.org/openSUSE:Build_Service_Tips_and_Tricks#How_to_control...
The release field in the spec file is ignored and replaced by
. , where represents the check-in count and represents the build count. Is that not accurate? it is correct. But if the release number in the spec file is higher than CI_CNT, CI_CNT will get increased to its value.
Sweet! Perhaps that ought to be added to the docs. Is that something I can do? -- Jon -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Tuesday 17 August 2010 17:33:13 Jon Nelson wrote:
On Tue, Aug 17, 2010 at 10:10 AM, Adrian Schröter
wrote: On Tuesday 17 August 2010 17:01:15 Jon Nelson wrote:
On Tue, Aug 17, 2010 at 9:55 AM, Marcus Rueckert
wrote: On 2010-08-17 09:54:00 -0500, Jon Nelson wrote:
Is there a way to tell the OBS to set the release number of a package to some arbitrary number (or to increase it by some number)?
For example, let's say foo version 1.0 and has been checked in 3 times and rebuilt twice. I think the package would then be foo-1.0-3.2.$arch.rpm. Let's say I'd like to set the check in count to 5 (and reset the build count). Is there an easy way to do this without /actually/ checking in a number of dummy commits?
check in a spec that has Release: 5
According to the docs here:
http://en.opensuse.org/openSUSE:Build_Service_Tips_and_Tricks#How_to_control...
The release field in the spec file is ignored and replaced by
. , where represents the check-in count and represents the build count. Is that not accurate? it is correct. But if the release number in the spec file is higher than CI_CNT, CI_CNT will get increased to its value.
Sweet! Perhaps that ought to be added to the docs. Is that something I can do?
PLEASE ! We need more people who improve the OBS docu in the wiki. thanks a lot 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
On Tue, Aug 17, 2010 at 10:33 AM, Jon Nelson
it is correct. But if the release number in the spec file is higher than CI_CNT, CI_CNT will get increased to its value.
A question, then. I assume that the "check-in count" is stored somewhere. Let's say the value is 3 (and the 'Release' value in the specfile is 1). So then I make a change, and set the 'Release' value in the specfile to 10. Does that also change the 'check-in count' to 10, such that if I make yet another change to the specfile where I set it to, say, 5, that the 'check-in count' would then be 11? (I hope you followed that...) -- Jon -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Tuesday 17 August 2010 17:49:10 Jon Nelson wrote:
On Tue, Aug 17, 2010 at 10:33 AM, Jon Nelson
wrote: it is correct. But if the release number in the spec file is higher than CI_CNT, CI_CNT will get increased to its value.
A question, then. I assume that the "check-in count" is stored somewhere. Let's say the value is 3 (and the 'Release' value in the specfile is 1). So then I make a change, and set the 'Release' value in the specfile to 10. Does that also change the 'check-in count' to 10, such that if I make yet another change to the specfile where I set it to, say, 5, that the 'check-in count' would then be 11?
Yep, that is the behaviour bye 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
On Tue, Aug 17, 2010 at 11:02 AM, Adrian Schröter
On Tuesday 17 August 2010 17:49:10 Jon Nelson wrote:
On Tue, Aug 17, 2010 at 10:33 AM, Jon Nelson
wrote: it is correct. But if the release number in the spec file is higher than CI_CNT, CI_CNT will get increased to its value.
A question, then. I assume that the "check-in count" is stored somewhere. Let's say the value is 3 (and the 'Release' value in the specfile is 1). So then I make a change, and set the 'Release' value in the specfile to 10. Does that also change the 'check-in count' to 10, such that if I make yet another change to the specfile where I set it to, say, 5, that the 'check-in count' would then be 11?
Yep, that is the behaviour
I just tested this and, maybe I'm doing something wrong, but, it didn't work. I set the Release to 10 (in the specfile), and the newly-produced rpm had a release of 3.3. :-( -- Jon -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (3)
-
Adrian Schröter
-
Jon Nelson
-
Marcus Rueckert