[Reproducible-builds] on manual rescheduling uploaded packages (Re: [Qa-jenkins-dev] Different versions

[Holger Levsen]

Hi,

cc:ing the regular reproducible list, as others also fail for this 
misconception…

On Donnerstag, 8. Oktober 2015, Santiago Vila wrote:
> I've rescheduled w3c-markup-validator a few minutes ago.
[...]
> I see that it has built 1.3+dfsg-2 again, not -3.

rescheduling is for _rescheduling_ already tested versions, not for scheduling 
new versions, those are best scheduled (automatically) by the regular 
scheduler which is run every hour and which schedules new versions once they 
are available.

Why? There are delays between until newly uploaded packages appear on the 
mirror and until the mirror is updated on the reproducible build nodes and and 
until the reproducible db picks it up. 

Best *dont* manually schedule packages you have just uploaded, instead just 
let the scheduler schedule them when they are ready.


cheers,
	Holger
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 828 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.alioth.debian.org/pipermail/reproducible-builds/attachments/20151008/efd8fb51/attachment.sig>