Hi!

On Wed, 2016-02-03 at 09:22:51 -0500, James McCoy wrote:
> Package: apt
> Version: 1.2.1
> Followup-For: Bug #812994
> 
> I just noticed some interesting behavior related to this bug.  Looking
> back at Rohan's initial term.log, we see this:
> 
>     Log started: 2016-01-28  12:13:31
>     ...
>     Selecting previously unselected package 
> libglobus-xio-gridftp-driver-dev:amd64.
>     Preparing to unpack .../libpipeline1_1.4.1-2_amd64.deb ... 
>     Unpacking libglobus-xio-gridftp-driver-dev:amd64 (2.11-1) ... 
>     ...
>     dpkg: error processing package libpipeline1 (--configure):
>      no package named 'libpipeline1' is installed, cannot configure
> 
> Now, the "Selecting previously unselected", "Preparing to unpack", etc.
> lines come from dpkg.  From what I can tell, those 3 lines should all
> refer to the same archive, and they do for the rest of the log.

Yeah, we also noticed this today on #debian-dpkg.

> I had a similar problem today.

> ...
> Selecting previously unselected package libn32atomic1-mips64el-cross.
> Preparing to unpack .../libjpeg62-turbo_1%3a1.4.2-2_amd64.deb ...
> Unpacking libn32atomic1-mips64el-cross (5.3.1-7cross1) ...
> ...
> dpkg: error processing package libjpeg62-turbo:amd64 (--configure):
>  package libjpeg62-turbo:amd64 is already installed and configured
> ...

The first and third lines come supposedly from the .deb control file,
the second from the filename.

If this is just a problem with wrong strings, then libjpeg62-turbo:amd64
in theory would not be already configured, just unpacked (but I might be
missing context here).

> $ dpkg-query -l libjpeg62-turbo
> Desired=Unknown/Install/Remove/Purge/Hold
> | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
> |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
> ||/ Name                            Version              Architecture         
> Description
> +++-===============================-====================-====================-===================================================================
> ii  libjpeg62-turbo:amd64           1:1.4.1-2            amd64                
> libjpeg-turbo JPEG runtime library

> Even though there was no reason for libn32atomic1-mips64el-cross to be
> installed, apt didn't download the archive, and I don't have the .deb
> for it in /var/cache/apt/archives, dpkg thought it was unpacked instead
> of libjpeg62-turbo.

Weird.

> >From /var/log/dpkg.log:
> 
> 2016-02-03 08:53:33 startup archives unpack
> ...
> 2016-02-03 08:53:40 install libn32atomic1-mips64el-cross:all <none> 
> 5.3.1-7cross1
> 2016-02-03 08:53:40 status half-installed libn32atomic1-mips64el-cross:all 
> 5.3.1-7cross1
> 2016-02-03 08:53:40 status unpacked libn32atomic1-mips64el-cross:all 
> 5.3.1-7cross1
> 2016-02-03 08:53:40 status unpacked libn32atomic1-mips64el-cross:all 
> 5.3.1-7cross1

Just to make sure, if you have the libjpeg62-turbo_1%3a1.4.2-2_amd64.deb
around could you check that it really contains the libjpec62-turbo
package inside with say dpkg-deb, or manually with ar+tar?

If you have the previous status file in /var/backups, and you could
try to reproduce this that would be great, otherwise, sending it here
or to me and the apt maintainers in case of privacy concerns might help
too.

> I'm not sure if this is something to do with how apt is driving dpkg or
> dpkg itself is getting confused, but hopefully this helps.

(It could well be dak being confused perhaps? But… :)

Thanks,
Guillem

Reply via email to