[opensuse-buildservice] _buildinfo inconsistency
Hi, $ osc api /build/home:michal-m/openSUSE_11.0/x86_64/nafe/_buildinfo >t1 $ osc api -m POST -d 'Name: test' \ /build/home:michal-m/openSUSE_11.0/x86_64/nafe/_buildinfo >t2 $ diff -u t[12] --- t1 2009-09-08 15:56:54.000000000 +0200 +++ t2 2009-09-08 15:56:57.000000000 +0200 @@ -1,13 +1,5 @@ <buildinfo project="home:michal-m" repository="openSUSE_11.0" package="nafe" downloadurl="http://download.opensuse.org/repositories"> <arch>x86_64</arch> - <srcmd5>4f263493abe82e1f59603b5a5642b4a0</srcmd5> - <verifymd5>4f263493abe82e1f59603b5a5642b4a0</verifymd5> - <rev>2</rev> - <specfile>nafe.spec</specfile> - <file>nafe.spec</file> - <versrel>0.1-2</versrel> - <bcnt>2</bcnt> - <release>2.2</release> <debuginfo>0</debuginfo> <bdep name="aaa_base" preinstall="1" runscripts="1" notmeta="1" version="11.0" release="79.1" arch="x86_64" project="openSUSE:11.0" repository="standard" /> <bdep name="acl" preinstall="1" notmeta="1" version="2.2.45" release="40.1" arch="x86_64" project="openSUSE:11.0" repository="standard" /> Because of the missing <release>2.2</release> element, osc doesn't substitute release numbers when building locally. Should osc work around this (get the buildinfo a second time to find out the release) or should the backend be fixed (bs_repserver, function getbuildinfo(), that doesn't fetch the required pieces when called from getbuildinfo_post())? Michal -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Dienstag, 8. September 2009 16:01:07 schrieb Michal Marek:
Hi,
$ osc api /build/home:michal-m/openSUSE_11.0/x86_64/nafe/_buildinfo >t1 $ osc api -m POST -d 'Name: test' \ /build/home:michal-m/openSUSE_11.0/x86_64/nafe/_buildinfo >t2 $ diff -u t[12] --- t1 2009-09-08 15:56:54.000000000 +0200 +++ t2 2009-09-08 15:56:57.000000000 +0200 @@ -1,13 +1,5 @@ <buildinfo project="home:michal-m" repository="openSUSE_11.0" package="nafe" downloadurl="http://download.opensuse.org/repositories"> <arch>x86_64</arch> - <srcmd5>4f263493abe82e1f59603b5a5642b4a0</srcmd5> - <verifymd5>4f263493abe82e1f59603b5a5642b4a0</verifymd5> - <rev>2</rev> - <specfile>nafe.spec</specfile> - <file>nafe.spec</file> - <versrel>0.1-2</versrel> - <bcnt>2</bcnt> - <release>2.2</release> <debuginfo>0</debuginfo> <bdep name="aaa_base" preinstall="1" runscripts="1" notmeta="1" version="11.0" release="79.1" arch="x86_64" project="openSUSE:11.0" repository="standard" /> <bdep name="acl" preinstall="1" notmeta="1" version="2.2.45" release="40.1" arch="x86_64" project="openSUSE:11.0" repository="standard" />
Because of the missing <release>2.2</release> element, osc doesn't substitute release numbers when building locally. Should osc work around this (get the buildinfo a second time to find out the release) or should the backend be fixed (bs_repserver, function getbuildinfo(), that doesn't fetch the required pieces when called from getbuildinfo_post())?
This is by intention, because it is not an official build. (osc build is always the POST operation). We neither want to increment the build number on the server for each local build, nor we want that your local built package gets not updated by the later build from the server. Is this a problem for you somewhere ? 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
Adrian Schröter napsal(a):
Am Dienstag, 8. September 2009 16:01:07 schrieb Michal Marek:
Because of the missing <release>2.2</release> element, osc doesn't substitute release numbers when building locally. Should osc work around this (get the buildinfo a second time to find out the release) or should the backend be fixed (bs_repserver, function getbuildinfo(), that doesn't fetch the required pieces when called from getbuildinfo_post())?
This is by intention, because it is not an official build. (osc build is always the POST operation).
We neither want to increment the build number on the server for each local build,
osc api /build/home:michal-m/openSUSE_11.0/x86_64/nafe/_buildinfo does not change anything on the server.
nor we want that your local built package gets not updated by the later build from the server.
If I build locally and then check in, the source revision gets incremented, so that should not be a problem. And even if it is, we can add an option to disable this. BTW osc does have code to handle the <release> element, so this is definitely a regression caused by a change in bs_repserver. The question is whether to fix it there or workaround it in osc.
Is this a problem for you somewhere ?
E.g. $ osc co openSUSE:11.1:Update psmisc $ cd openSUSE:11.1:Update/psmisc $ osc build standard x86_64 produces a package called psmisc-22.6-61.<RELEASE27>.x86_64.rpm. Michal -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Am Dienstag, 8. September 2009 20:58:00 schrieb Michal Marek:
Adrian Schröter napsal(a):
Am Dienstag, 8. September 2009 16:01:07 schrieb Michal Marek:
Because of the missing <release>2.2</release> element, osc doesn't substitute release numbers when building locally. Should osc work around this (get the buildinfo a second time to find out the release) or should the backend be fixed (bs_repserver, function getbuildinfo(), that doesn't fetch the required pieces when called from getbuildinfo_post())?
This is by intention, because it is not an official build. (osc build is always the POST operation).
We neither want to increment the build number on the server for each local build,
osc api /build/home:michal-m/openSUSE_11.0/x86_64/nafe/_buildinfo does not change anything on the server.
nor we want that your local built package gets not updated by the later build from the server.
If I build locally and then check in, the source revision gets incremented, so that should not be a problem. And even if it is, we can add an option to disable this. BTW osc does have code to handle the <release> element, so this is definitely a regression caused by a change in bs_repserver.
Not really, the code in osc for this is rather new, but was never used actually.
The question is whether to fix it there or workaround it in osc.
Is this a problem for you somewhere ?
E.g. $ osc co openSUSE:11.1:Update psmisc $ cd openSUSE:11.1:Update/psmisc $ osc build standard x86_64 produces a package called psmisc-22.6-61.<RELEASE27>.x86_64.rpm.
I think we can publish the old release number also in the POST operation, but does make this really something better ? hm, maybe we should set it always to zero, so it gets updated in any case again (and --old-package or --force would be anyway needed as long do not a current +1 what would mean the package would not get updated with the final one from the server). Need to think about this .... good evening 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
Adrian Schröter napsal(a):
Am Dienstag, 8. September 2009 20:58:00 schrieb Michal Marek:
add an option to disable this. BTW osc does have code to handle the <release> element, so this is definitely a regression caused by a change in bs_repserver.
Not really, the code in osc for this is rather new, but was never used actually.
Ok.
E.g. $ osc co openSUSE:11.1:Update psmisc $ cd openSUSE:11.1:Update/psmisc $ osc build standard x86_64 produces a package called psmisc-22.6-61.<RELEASE27>.x86_64.rpm.
I think we can publish the old release number also in the POST operation, but does make this really something better ?
It avoids the ugly angle brackets (that break rpmlint btw).
hm, maybe we should set it always to zero, so it gets updated in any case again (and --old-package or --force would be anyway needed as long do not a current +1 what would mean the package would not get updated with the final one from the server).
Ok, I myself don't really care what the exact value is. thanks, Michal -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 8.9.2009 21:29, Adrian Schröter wrote:
Am Dienstag, 8. September 2009 20:58:00 schrieb Michal Marek:
E.g. $ osc co openSUSE:11.1:Update psmisc $ cd openSUSE:11.1:Update/psmisc $ osc build standard x86_64 produces a package called psmisc-22.6-61.<RELEASE27>.x86_64.rpm.
I think we can publish the old release number also in the POST operation, but does make this really something better ?
hm, maybe we should set it always to zero, so it gets updated in any case again (and --old-package or --force would be anyway needed as long do not a current +1 what would mean the package would not get updated with the final one from the server).
Ping. Is it possible to publish *any* release number in the _buildinfo? Those foo-1.2.3-<RELEASE>.rpm packages suck :(. Michal -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (2)
-
Adrian Schröter -
Michal Marek