On Fri, 14 Oct 2016, Petter Reinholdtsen wrote:

> Control: tags -1 + patch
> I had a look, and while I do not quite understand the build system and why it
> fail to create the directory it need to install, I applied this patch and got
> the 'dpkg-buildpackage -A' build working:
> diff -ur brickos-0.9.0.dfsg/debian/rules brickos-0.9.0.dfsg-pere/debian/rules
> --- brickos-0.9.0.dfsg/debian/rules     2015-02-14 18:21:17.000000000 +0000
> +++ brickos-0.9.0.dfsg-pere/debian/rules        2016-10-14 07:43:21.284198193 
> +0000
> @@ -33,6 +33,7 @@
>  override_dh_auto_install:
>         #  Install the package into debian/brickos.
> +       mkdir -p $(CURDIR)/debian/brickos/usr/bin
>         $(MAKE) install docs-install inst_prefix=/usr 
> prefix=$(CURDIR)/debian/brickos/usr 
> mandir=$(CURDIR)/debian/brickos/usr/share/man
>         #  remove docs we shouldn't install
>         rm -f 
> $(CURDIR)/debian/brickos/usr/share/doc/brickos/html/INSTALL-cygwin*

Ok, now that you mention it, the bug is easy to explain:

Since I was doing "dpkg-buildpackage -A", this means we are creating
arch-independent packages only (i.e. Arch:all), so dh_installdirs does
not create debian/brickos because brickos is arch-dependent (i.e. Arch:any).

The proposed patch is probably ok as a workaround, but if this were my
package, I would drop dh_movefiles and would use override_dh_auto_install
to install into debian/tmp and then would use debian/*.install files
to determine which files go to which packages.

(That's probably the current trend, or the "orthodox way").

Thanks a lot.

Reply via email to