29 Nov
2012
29 Nov
'12
19:11
Hi, I know this is more of an obs question than a packaging question. Say I know I released a buggy package in a big and busy repo. A new version has been committed but it won't be published because the repo never comes to rest, is always getting commits before all builts affecting it are done and as I understand a repo will only publish when it's come to rest. Is there a way I could say "don't schedule new builds before the current queue is done and published" ? -- Ralf Lang Linux Consultant / Developer Tel.: +49-170-6381563 Mail: lang@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537