On 2007-05-22 14:30:42 +0200, Dries Verachtert wrote:
Where can i find the piece of code which alters the release tag of the spec file? Is there maybe a way to avoid or influence this behaviour?
For example the following is logged in the build log:
I have the following modifications for aget-openSUSE_10.2.spec: 10c10 < Release: 5.2.opensuse10.2.rf ---
Release: 17.1
i am not sure if it would be easy to get that string. i dont think we set something like %dist by default. and the distribution tag itself is way too long and contains whitespaces and other ugly chars. just as an example: $ rpm -q --qf '%{NAME}-%{VERSION}-%{RELEASE}_%{DISTRIBUTION}\n' vim-base vim-base-7.0-99.1_home:darix / SUSE_Factory as you see the %DISTRIBUTION tag contains the local project name and the target repository. and i am not sure it would be enough to set %dist to the base distro.
How is the '17' and the '1' calculated? Is it possible to append or prepend something?
x.y: x == number of changes to the package (aka uploaded files) y == number of rebuilds. if b depends on a and a is rebuild, it will trigger a rebuild of b and you will will end with 17.2 (in your example) hope this helps 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