On 2016-03-02 20:00 +0100, Sven Joachim wrote: > Package: aptitude > Version: 0.7.7-1 > Severity: important > > Like many people, I have a local repository in a flat directory, managed > by apt-ftp-archive. The latest aptitude version triggers an internal > apt error trying to install packages from this repository and also > messes up the terminal, introducing a "staircase" effect (the error > message itself comes from libapt-pkg, see apt-pkg/deb/dpkgpm.cc in the > apt source): > > ,---- > | $ LANG=C sudo aptitude reinstall linux-image-4.5.0-rc6-nouveau > | The following packages will be REINSTALLED: > | linux-image-4.5.0-rc6-nouveau > | 0 packages upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 12 > not upgraded. > | Need to get 0 B/6490 kB of archives. After unpacking 0 B will be used. > | E: Internal Error, Pathname to install is not absolute > 'linux-image-4.5.0-rc6-nouveau_4.5.0-rc6-1_i386.deb' > | > Failed to perform requested operation on > package. Trying to recover: > | > | $ echo $? > | 255 > `---- > > Downgrading aptitude (and aptitude-common) to 0.7.6-1 fixes this.
Bisection shows commit c447ba44b8c69b5fad7efada9da2832312ec8558 ("Only lock package cache dirs and call pkgAcquire->Run() when necessary (Closes: #766122)") as the one which introduced the problem. Cheers, Sven