Control: reopen -1 On Tue, May 21, 2013 at 03:58:07 +0200, Andreas Beckmann wrote:
> Package: libunwind-setjmp0 > Version: 1.1-1 > Severity: serious > User: debian...@lists.debian.org > Usertags: piuparts > > Hi, > > during a test with piuparts I noticed your package failed to install. As > per definition of the release team this makes the package too buggy for > a release, thus the severity. > > >>From the attached log (scroll to the bottom...): > > Selecting previously unselected package libunwind-setjmp0. > (Reading database ... 6685 files and directories currently installed.) > Unpacking libunwind-setjmp0 (from .../libunwind-setjmp0_1.1-1_amd64.deb) ... > /var/lib/dpkg/tmp.ci/preinst: 1: /var/lib/dpkg/tmp.ci/preinst: > dpkg-architecture: not found > dpkg: error processing > /var/cache/apt/archives/libunwind-setjmp0_1.1-1_amd64.deb (--unpack): > subprocess new pre-installation script returned error exit status 127 > /var/lib/dpkg/tmp.ci/postrm: 1: /var/lib/dpkg/tmp.ci/postrm: > dpkg-architecture: not found > dpkg: error while cleaning up: > subprocess new post-removal script returned error exit status 127 > Errors were encountered while processing: > /var/cache/apt/archives/libunwind-setjmp0_1.1-1_amd64.deb > > > 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. Cheers, Julien
signature.asc
Description: Digital signature
