Yves-Alexis Perez wrote: > What I don't understand is why is the behavior different when one builds > arch:all + arch:any package and when one builds only arch:any. > > I use the minimal rule file which, aiui, install files using root as > debian/$package/ when building with: > dpkg-buildpackage -rfakeroot -us -uc -B > > installing ur.gmo as > /build/buildd/xfce4-dict-0.4.0/debian/xfce4-dict/usr/share/locale/ur/LC_MESSAGES/xfce4-dict.mo > > But the same rule files, when building using: > dpkg-buildpackage -rfakeroot -us -uc, installs stuff in debian/tmp > > installing ur.gmo as > /home/corsac/debian/sources/xfce4-dict-0.4.0/debian/tmp/usr/share/locale/ur/LC_MESSAGES/xfce4-dict.mo > > So maybe the problem is not in dh_install at all, but still the DESTDIR > isn't consistent wether I use -B or not.
Aha, so the problem is that dh_auto_install installs into debian/<package> if there is only one package to act on, but debian/tmp if there are multiple packages. This behavior makes sense for a single binary package, and for a multiple-binary package where all the binary packages are built for the same architecture. But it falls apart when one binary is arch all and one any, since in this case dh_auto_install will behave differently depending on whether the arch all package is being built or not. So what it should really do is detect this case is use debian/tmp even if it's only acting on one of the available packages. I'll try to figure out an approach for handling this case right and fix this bug. -- see shy jo
signature.asc
Description: Digital signature
