Hi Josch, > Preparing to replace vpnc 0.5.3r449-2.1 (using > .../vpnc_0.5.3r512-1_amd64.deb) ... > dpkg (subprocess): unable to execute new pre-installation script > (/var/lib/dpkg/tmp.ci/preinst): Exec format error > dpkg: error processing /var/cache/apt/archives/vpnc_0.5.3r512-1_amd64.deb > (--unpack): > subprocess new pre-installation script returned error exit status 2 > configured to not write apport reports > dpkg (subprocess): unable to execute > new post-removal script (/var/lib/dpkg/tmp.ci/postrm): Exec format error > dpkg: error while cleaning up: > subprocess new post-removal script returned error exit status 2 > Errors were encountered while processing: > /var/cache/apt/archives/vpnc_0.5.3r512-1_amd64.deb > E: Sub-process /usr/bin/dpkg returned an error code (1)
uh, that looks awful! But while you're probably right that vpnc's maintainer scripts should be properly marked as shell scripts, I cannot reproduce your problem and I wonder if this is in fact a different issue. Is it possible that there was a hardware issue (partition full, fsck pending, ...) or that for some other reason the preinst / postrm script was empty? Do you know what dpkg version you were using? Googling for dpkg and "Exec format error" brings up lots of issues, e.g. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567089 and http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622094 or even http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=514793 Scripts marked executable but without a #! line are given to the shell (/bin/sh) by default, so I don't think your problem has its root in vpnc... Florian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
