On Sun, 2010-06-06 at 13:12 +0200, Andreas Barth wrote: > First, I intended to create a state "known", which is the maximum of > installed and needs-build, i.e. for take, failed, attempted, ... it > behaves like needs-build, for binNMU it behaves like installed, and it > doesn't set packages from needs-build to known unless directed to do > so. Which of course means we need to adjust a couple of things, and we > need an way to specify "--needs-build". (Then I thought we could use > use --binNMU 0 to say "needs-build". That is an ugly hack, but gave me > the following thought.)
fwiw, binNMU version 0 is already reserved, to mean "cancel any current binNMU and set the package back to Installed". Adam -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
