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 astromenace. > (Reading database ... 7531 files and directories currently installed.) > Unpacking astromenace (from .../astromenace_1.3.1+repack-2_amd64.deb) ... > Setting up astromenace (1.3.1+repack-2) ... > tar (child): xz: Cannot exec: No such file or directory > tar (child): Error is not recoverable: exiting now > tar: Child returned status 2 > tar: Error is not recoverable: exiting now > dpkg: error processing astromenace (--configure): > subprocess installed post-installation script returned error exit status 2 > Errors were encountered while processing: > astromenace > > xz-utils was recently demoted from required to standard, therefore packages > using it must depend on xz-utils.
As we can see in dpkg changelog [1] for version 1.16.4: > * Add support for liblzma to handle .xz and .lzma compressed files, and > switch to it instead of using xz-utils. This removes the xz-utils > Pre-Depends from dpkg. Thanks to Jonathan Nieder <jrnie...@gmail.com>. I am wondering why it was not used. Any ideas? [1] http://ftp-master.metadata.debian.org/changelogs//main/d/dpkg/dpkg_1.16.10_changelog Best regards, Boris -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
