broken DDPO by not-so-broken reproducible-tracker.json

[Holger Levsen]

Hi,

On Thu, Nov 03, 2016 at 05:47:17PM +0000, Mattia Rizzolo wrote:
> This thread doesn't seem to make progress, anyway:

(it was still on my to-reply list…)
 
> On Tue, Oct 18, 2016 at 09:54:39PM +0000, Mattia Rizzolo wrote:
> > 4. figure out why the hell DDPO doesn't deal with that edit in the json,
> >    see the code⁵ in Debian's QA Team SVN repo, and leave the json to
> >    display testing data as it is now
> This happened now, thanks to myon.  Not sure what this means with
> regards to this dicussion, but I figured I'd let you all know.

to me it means we'll leave -tracker.json as it is now, until we have
released stretch (when I'll probably be fine switching -tracker.json to carry
results for unstable again).

This means there is a delay between an upload and showing that it worked
on DDPO, yes. But if you did an upload and want to know, you can always
check manually on t.r-b.o/debian/unstable/$your_pkg yourself.


-- 
cheers,
	Holger
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 811 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/reproducible-builds/attachments/20161110/28f737f1/attachment.sig>