Christian Seiler <email@example.com> (2016-08-13): > (dropping a lot of stuff from Cc, including the bug report, > because this reply is just debian-boot related) (ack.) > How does one do these checks oneself (especially if the package is not > in sid yet, i.e. before the upload)? Because the test matrix for > open-iscsi is already nontrivial, and I don't want to have to build a > custom installer and test it before each package change. Code lives here: https://anonscm.debian.org/viewvc/d-i/trunk/scripts/dose4udebs-wrapper?view=log https://anonscm.debian.org/viewvc/d-i/trunk/scripts/dose4udebs?view=log called from a crontab entry: ./dose4udebs-wrapper /srv/mirrors/debian dose.tmp $WWW/dose You might have to tweak it a bit to run it locally and to allow for custom packages. > Also, would it be possible to perform these checks not only on sid but > also on sid + experimental? The change that broke here was in > experimental for 10-11 days - and I uploaded the package to > experimental first to find these kinds of issues before doing a sid > upload - and it appears that plan failed miserably. ;-) The question is likely how to merge sid and experimental. I suspect one might consider dropping all binaries from sid for which sources have an updated version in experimental, and picking all binaries from said updated sources. But I fear edge cases might pop up. Might be worth implementing anyway though. KiBi.
Description: Digital signature