[dropped #830267 from CC; it's not directly relevant to this branch of
the discussion]
On 2016-07-24 17:43, Don Armstrong wrote:
On Sun, 24 Jul 2016, Francesco Poli wrote:
[...]
could you please investigate on what happened to bug #830267 on
2016-07-19T10:00 ?
Please take a look at
https://bugs.debian.org/830267#20
https://bugs.debian.org/830267#25
for more context.
Hrm; it was shown as affecting testing at T0600 (and all subsequent
runs):
status-201607190600:number=830267
status-201607190600-testing=1
status-201607190600-unstable=1
but not on the immediately preceding run:
[...]
That's really odd; I haven't changed anything on the BTS side during
that time period which would explain that happening.
Unfortunately, I don't know when the BTS thought that 1.18.9 was
actually in testing and not in unstable. I'll try to check out
snapshots
later this week to see if I can figure out when the transition actually
happened, or if there was something else going on in the archive to
explain it.
Does the BTS take account of entries in Sources marked
"Extra-Source-Only: yes" when determining bugginess?
If so, a possible explanation is that debsig-verify 0.15 migrated to
testing overnight on the 18th/19th. The binary packages have
"Built-Using: dpkg (= 1.18.9)", which would have led dak to add the
corresponding source package to testing with an E-S-O marker.
Regards,
Adam
