Your message dated Sat, 7 Apr 2018 23:53:05 +0200
with message-id <20180407215304.gh17...@mapreri.org>
and subject line Re: [Qa-jenkins-dev] Bug#862600: tests.r-b.o: tests version
from sid in testing due to the source is in testing due to Built-Using:…
has caused the Debian Bug report #862600,
regarding tests.r-b.o: tests version from sid in testing due to the source is
in testing due to Built-Using:…
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
862600: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862600
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: jenkins.debian.org
Severity: normal
x-debbugs-cc: b...@debian.org
Dear Maintainer,
< bunk>
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-rackspace-gophercloud.html
< bunk> This seems confused by the more recent source that is in stretch due to
Built-Using?
< h01ger> | oh! it builds the sid version in stretch!
< h01ger> | bunk: so the sid version "is in stretch" because some packages
in stretch were build using the sid version and then migrated. wow. i think i
have discussed this with ivodd once in a corridor at the bsp at credativ in
march 2017 or so…
< h01ger> | i also think this is a topic for #-release
< h01ger> | (unless they know)
< h01ger> | and then its also a bug in the tests.r-b.o setup, to test the
wrong version…
< h01ger> | fwiw:
< h01ger> | $ rmadison golang-github-rackspace-gophercloud
< h01ger> | debian:
< h01ger> | golang-github-rackspace-gophercloud |
1.0.0+git20160603.920.934dbf8-1 | stretch | source
< h01ger> | golang-github-rackspace-gophercloud |
1.0.0+git20161013.1012.e00690e8-1 | sid | source
< h01ger> | and tests.r-b.o only shows the sid version being tested in
stretch+sid…
< bunk> | h01ger: How does r-b pick the version? Sources?
< h01ger> | etootired. check bin/reproducible_build.sh in jenkins.d.n.git
please…
< bunk>
https://anonscm.debian.org/cgit/qa/jenkins.debian.net.git/tree/bin/reproducible_build.sh#n540
< bunk> apt-get -- --download-only --only-source source ${SRCPACKAGE}
< bunk> (if I read the script correctly)
< h01ger> | bunk: may i quote your initial question into the BTS?
< h01ger> | +could be it… ;)
< bunk> sure
Thanks for the bug report, Adrian!
--
cheers,
Holger
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
On Mon, May 15, 2017 at 01:53:57AM +0200, Holger Levsen wrote:
> < bunk>
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-rackspace-gophercloud.html
> < bunk> This seems confused by the more recent source that is in stretch due
> to Built-Using?
> < h01ger> | oh! it builds the sid version in stretch!
So, the very same day (May 15th 2017) we fixed the source importer to
ignore Extra-Source-Only:yes packages, but we didn't fix the several
affected entries.
I did it now, by manually hacking my way through the db...
The affected sources:
buster+stretch:
golang-github-rackspace-gophercloud is faulty:
sources=1.0.0+git20160603.920.934dbf8-1 | db=1.0.0+git20161013.1012.e00690e8-1
runc is faulty: sources=0.1.1+dfsg1-2 | db=1.0.0~rc2+git20161109.131.5137186-2
stretch only:
golang-github-dgrijalva-jwt-go is faulty: sources=3.0.0+REALLY.2.6.0-1 |
db=3.0.0.1+REALLY.2.6.0-1
golang-github-opencontainers-specs is faulty: sources=1.0.0~rc1-1 |
db=1.0.0~rc2+git20160926.38.1c7c27d-1
golang-github-spf13-cobra is faulty: sources=0.0~git20161229.0.1dd5ff2-1 |
db=0.0~git20170314.0.7be4bed-1
golang-github-vishvananda-netlink is faulty:
sources=0.0~git20160629.0.e73bad4-1 | db=0.0~git20170117.0.ebdfb74-1
golang-gogoprotobuf is faulty: sources=0.3-1 | db=0.3+git20170120.144.265e960d-1
golang-goleveldb is faulty: sources=0+git20160825.6ae1797-2 |
db=0.0~git20170302.0.3c5717c-4
influxdb is faulty: sources=1.0.2+dfsg1-1 | db=1.1.1+dfsg1-4
snappy is faulty: sources=1.1.3-3 | db=1.1.4-1
I've deleted the faulty builds as well, the scheduler should pick them
up (as they are "untested" now).
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature
--- End Message ---
