On 28 July 2010 22:06, James Vega <[email protected]> wrote: > This happens because as soon as we see a non-debuild option, we break > out of our option parsing and treat the rest as options for the other > tools that get invoked.
Errr... Not so fast at closing the bug - it isn't resolved yet... The problem is that this command line is generated automatically by git-buildpackage, and git-buildpackage puts the "-i -I" options first, before any other options on given on the git-buildpackage command line. i.e. git-buildpackage --username value becomes debuild -i -I --username value Are you saying git-buildpackage needs to sort the options and put debuild options first? That sounds like debuild needs to have a hardcoded list of what options debuild takes, which sounds very error prone and likely to break with new versions of debuild. -- Brian May <[email protected]> -- To unsubscribe, send mail to [email protected].
