Bug#812994: apt 1.2.1 fails to configure packages
On Thu, Feb 04, 2016 at 12:56:53AM +0100, Guillem Jover wrote:
> On Wed, 2016-02-03 at 09:22:51 -0500, James McCoy wrote:
> > 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).
Well, version 1:1.4.1-2 of libjpeg62-turbo was already configured and
since the newer version wasn't unpacked (libn32atomic1-mips64el-cross
was instead), there was nothing to configure.
> > $ 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?
I don't, but I've now disabled apt's automatic removal of the .deb when
a package is installed. I'll do this on all my hosts so next time I hit
the issue I'll be able to answer this question.
> 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 downgraded libjpeg62-turbo and performed an upgrade again, but that
specific scenario didn't reproduce.
> > 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… :)
That would have broader visibility, though, wouldn't it?
Cheers,
James
Reply to: