So it seems, nice catch. Didn't know that those options need to be supported.
I've added the bug in to the github issue tracking too for the upstream project: https://github.com/spotify/dh-virtualenv/issues/29 My take is that those should probably be allowed but ignored. How does that sound? On Fri, Feb 14, 2014 at 11:38 AM, Michael Prokop <[email protected]> wrote: > Package: dh-virtualenv > Version: 0.6-1 > Severity: normal > > > dh_virtualenv doesn't honor dh's -a option: > > ,---- [ simple demo ] > | % dpkg-buildpackage -B > | [...] > | dh binary-arch --with=python-virtualenv > | dh_testroot -a > | dh_prep -a > | dh_installdocs -a > | dh_installchangelogs -a > | dh_perl -a > | dh_virtualenv -a > | Usage: dh_virtualenv [options] > | > | dh_virtualenv: error: no such option: -a > | make: *** [binary-arch] Error 2 > `---- > > Any dh script should accept -a and -i, quoting from debhelper's source: > > ,---- [ debhelper-9.20131227/doc/PROGRAMMING ] > | Debhelper programs should accept all options listed in the "SHARED > | DEBHELPER OPTIONS" section of debhelper(7), including any long forms of > | these options, like --verbose . If necessary, the options may be ignored. > `---- > > Quoting according section of debhelper(7): > > ,---- [ man 7 debhelper ] > | SHARED DEBHELPER OPTIONS > | [...] > | -a, --arch > | Act on architecture dependent packages that should be built > for the build architecture. > | > | -i, --indep > | Act on all architecture independent packages. > `---- > > regards, > -mika- >
