Re: [opensuse-buildservice] release number for moved packages
Reply on 10-11-2006 12:32:07 <<<> On Thu, Nov 09, 2006 at 11:25:29AM +0100, Dr. Peter Poeml wrote: If we move or copy a package from one project to another, what happens to the release number?
I suppose, it starts to count from the beginning. Is that correct?
It starts with the release number contained in the specfile.
Hi, I guess that is a not-yet-implemented theorie. Up to now, I've never seen BS using my Release-Number inside a spec file, but always replacing it with n.1 / n+m.1 (or by retriggering n.o / n.o+1) But it would be nice if at least the spec file would be respected (as on a local build, the spec file is fully respected for this) Dominique
On 2006-11-10 11:34:02 +0100, Dominique Leuenberger wrote:
Reply on 10-11-2006 12:32:07 <<<> On Thu, Nov 09, 2006 at 11:25:29AM +0100, Dr. Peter Poeml wrote: If we move or copy a package from one project to another, what happens to the release number?
I suppose, it starts to count from the beginning. Is that correct?
It starts with the release number contained in the specfile.
Hi,
I guess that is a not-yet-implemented theorie. Up to now, I've never seen BS using my Release-Number inside a spec file, but always replacing it with n.1 / n+m.1 (or by retriggering n.o / n.o+1)
But it would be nice if at least the spec file would be respected (as on a local build, the spec file is fully respected for this)
i am getting tired to explain this. the buildservice _has_ to keep its release number. if it would always honor the release number you could get into the situation where you cant update your package as you have a smaller release number. with the current way we guarantee your newly build packages are always installable. 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 Fri, Nov 10, 2006 at 11:34:02AM +0100, Dominique Leuenberger wrote:
It starts with the release number contained in the specfile.
I guess that is a not-yet-implemented theorie.
No, it's implemented. It just works not the way you expect.
Up to now, I've never seen BS using my Release-Number inside a spec file, but always replacing it with n.1 / n+m.1 (or by retriggering n.o / n.o+1)
Yes, but n is at least as big as the number in the spec file. And yes, there should be a way to tell the build service to not mess with the release number. Cheers, Michael. -- Michael Schroeder mls@suse.de main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Mon, Nov 13, 2006 at 01:55:29PM +0100, Michael Schroeder wrote:
On Fri, Nov 10, 2006 at 11:34:02AM +0100, Dominique Leuenberger wrote:
Up to now, I've never seen BS using my Release-Number inside a spec file, but always replacing it with n.1 / n+m.1 (or by retriggering n.o / n.o+1)
Yes, but n is at least as big as the number in the spec file.
And yes, there should be a way to tell the build service to not mess with the release number.
When pondering future implementation possibilities, it would be nice
to have the build service modifiy the release number by appending its
build revision to the release, not just overwriting it; e.g. X.n where
n is added by the buildservice. For all the packages I have in the
buildservice (currently, anyway), the release number as submitted is
the subversion repository version number; I'd like to keep that intact
in some way so that I can do a reverse mapping from a package back to
the specific version in subversion.
(I'd prefer to avoid adding my repo version to the Version number for
the package, if possible.)
--
Steve Beattie
SUSE Labs, Novell Inc.
On Mon, Nov 13, 2006 at 10:09:48AM -0800, Steve Beattie wrote:
On Mon, Nov 13, 2006 at 01:55:29PM +0100, Michael Schroeder wrote:
On Fri, Nov 10, 2006 at 11:34:02AM +0100, Dominique Leuenberger wrote:
Up to now, I've never seen BS using my Release-Number inside a spec file, but always replacing it with n.1 / n+m.1 (or by retriggering n.o / n.o+1)
Yes, but n is at least as big as the number in the spec file.
And yes, there should be a way to tell the build service to not mess with the release number.
When pondering future implementation possibilities, it would be nice to have the build service modifiy the release number by appending its build revision to the release, not just overwriting it; e.g. X.n where n is added by the buildservice. For all the packages I have in the buildservice (currently, anyway), the release number as submitted is the subversion repository version number; I'd like to keep that intact in some way so that I can do a reverse mapping from a package back to the specific version in subversion.
Yes, that's not hard to implement so we should make this configuration option possible. Cheers, Michael. -- Michael Schroeder mls@suse.de main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (4)
-
Dominique Leuenberger -
Marcus Rueckert -
Michael Schroeder -
Steve Beattie