On 14/08/07, Michel Salim wrote:

On 14/08/07, Michel Salim wrote:

...

Hello,

Is there a way to tell the buildserver to use the release number specified in the spec file? When building a package imported from another repository it automatically adds '.1' to the release number, which is fine, but if I override the .spec file with one of my own, shouldn't the revision number in the new spec be used?

Ah, found the answer: http://files.opensuse.org/opensuse/en/1/19/Oss_whitepaper.pdf

Kind of weird that my pidgin-otr's release number is up to 35.x, though, since I'm pretty sure I did not change the source 35 times (in the one week I've been using the service)!

(Also, this is probably heretical, but would it be possible to reset the release number everytime the version number is bumped? I don't really care if a given spec file has been modified n times, if some of the modifications pertain to older versions that are radically different in their build process and/or file listing) -- Michel --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

On 20/08/07, Michael Schroeder wrote:

On Tue, Aug 14, 2007 at 09:11:12PM +0700, Michel Salim wrote:

...

(Also, this is probably heretical, but would it be possible to reset the release number everytime the version number is bumped?

It already does that, it's just that it uses the "Release:" field from the spec file as start number. Next time you change the version just don't forget to set the Release tag back to "1".

Ah. Is the precise formula the release tag + the number of comments in the .changes file? Thanks, -- Michel --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org