Control: found -1 1.1-2 On 2013-08-04 10:56, Julien Cristau wrote: > On Tue, May 21, 2013 at 03:58:07 +0200, Andreas Beckmann wrote: >> This looks like a missing-dependency on dpkg-dev, but having a >> library depending on dpkg-dev looks very wrong. >> > So it looks like you've done the very wrong thing... Reopening, there's > absolutely no reason your package should need to run dpkg-architecture > in postinst. It's an arch:any package, it knows which architecture it > is.
Also a (Pre-)Depends: dpkg-dev does not guarantee that it is available at purge time: Removing libunwind-setjmp0 ... Purging configuration files for libunwind-setjmp0 ... /var/lib/dpkg/info/libunwind-setjmp0.postrm: 1: /var/lib/dpkg/info/libunwind-setjmp0.postrm: dpkg-architecture: not found dpkg: error processing libunwind-setjmp0 (--purge): subprocess installed post-removal script returned error exit status 127 (OK, in this case it's just noise as the value is not being used at all). But looking at what your maintainer scripts do, it is clear that the run-time approach of calling dpkg-architecture would fail in a multiarch installation (currently not possible because the package is not M-A: same) as regardless of the package architecture you would always divert the same files: that for the host architecture. On 2013-08-04 12:25, Daigo Moriwaki wrote: > Can I generate .postrm/.preinst files at package build time with a special > string substituted as an example following? >> debian/%.install: debian/%.install.in > >> + sed 's/@DEB_HOST_MULTIARCH@/$(DEB_HOST_MULTIARCH)/g' $< > $@ Yes, that is exactly the right way to do it in your case. (and don't forget to delete the generated files in debian/rules clean) Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
