Bug#909155: apt-cache show multiple packages produces invalid output

[Helmut Grohne]

Package: apt
Version: 1.7.0~rc1
Severity: serious
File: /usr/bin/apt-cache

If you do a fresh sid debootstrap and then you can get the following
interaction:

$ apt-cache show gcc-8-base=installed libgcc1=installed
Package: gcc-8-base
Source: gcc-8
Version: 8.2.0-7
Installed-Size: 244
Maintainer: Debian GCC Maintainers <debian-***@lists.debian.org>
Architecture: amd64
Breaks: gcc-4.4-base (<< 4.4.7), gcc-4.7-base (<< 4.7.3), gcj-4.4-base (<< 4.4.6-9~), gcj-4.6-base (<< 4.6.1-4~), gnat-4.4-base (<< 4.4.6-3~), gnat-4.6 (<< 4.6.1-5~)
Description: GCC, the GNU Compiler Collection (base package)
Description-md5: b6e93638a6d08ea7a18929d7cf078e5d
Multi-Arch: same
Homepage: http://gcc.gnu.org/
Tag: role::shared-lib
Section: libs
Priority: optional
Filename: pool/main/g/gcc-8/gcc-8-base_8.2.0-7_amd64.deb
Size: 187052
MD5sum: 5ae3d2f575c9924ae67fa8dcc4af1e21
SHA256: 9e3dcd13005ccadbb57a8f117cde66aec8b8b8a21492e3aa02d6f54c1288bfb4

Package: libgcc1
Source: gcc-8 (8.2.0-7)
Version: 1:8.2.0-7
Installed-Size: 116
Maintainer: Debian GCC Maintainers <debian-***@lists.debian.org>
Architecture: amd64
Depends: gcc-8-base (= 8.2.0-7), libc6 (>= 2.14)
Breaks: gcc-4.3 (<< 4.3.6-1), gcc-4.4 (<< 4.4.6-4), gcc-4.5 (<< 4.5.3-2)
Description: GCC support library
Description-md5: bbd60d723e97d8e06c04228ee4c76f10
Tag: role::shared-lib
Section: libs
Priority: optional
Filename: pool/main/g/gcc-8/libx32gomp1_8.2.0-7_amd64.deb
Size: 77204
MD5sum: 61275848d23df37f647cb6a9b21f4135
SHA256: b8c56221460897e2640baf7bd6e1a9f645346d4178265508a18d48bf8c68e752

Package: libx32gomp1-dbg
Source: gcc-8
Version: 8.2.0-7
Installed-Size: 346
Maintainer: Debian GCC Maintainers <de
$

Please observe that a third package is included, but truncated. This is
just an example. For other combinations of packages, you get other
invalid output. I've also seen "Multi-Arch: forei" and other crap.

I'm filing this at severity serious, because I think it is the tip of an
iceberg. The rc severity will prevent apt-listbugs users from installing
to leave time for investigation. Please downgrade the severity once the
problem is understood to be harmless.

Helmut

[Julian Andres Klode]

Control: tag -1 confirmed

Post by Helmut Grohne
Package: apt
Version: 1.7.0~rc1
Severity: serious
File: /usr/bin/apt-cache
If you do a fresh sid debootstrap and then you can get the following
$ apt-cache show gcc-8-base=installed libgcc1=installed
Package: gcc-8-base

[...]

Post by Helmut Grohne
Package: libgcc1

[...]

Post by Helmut Grohne
Package: libx32gomp1-dbg

[...]

git bisect says

bf53f39c9a0221b670ffff74053ed36fc502d5a0 is the first bad commit
commit bf53f39c9a0221b670ffff74053ed36fc502d5a0
Author: David Kalnischkies <***@kalnischkies.de>
Date: Wed Apr 11 12:59:06 2018 +0200

Support --with-source in show & search commands


This changed how show worked, so it's a fairly isolated problem.

Post by Helmut Grohne
I'm filing this at severity serious, because I think it is the tip of an
iceberg. The rc severity will prevent apt-listbugs users from installing
to leave time for investigation. Please downgrade the severity once the
problem is understood to be harmless.

We've been running 1.7.y in Ubuntu with this commit since June, and
not noticed the problem. It's a problem strictly in show. That said,
I don't want that to be broken in testing either, so I'll leave it as RC.

[Debian Bug Tracking System]

Post by Julian Andres Klode
tag -1 confirmed

Bug #909155 [apt] apt-cache show multiple packages produces invalid output
Added tag(s) confirmed.

[Debian Bug Tracking System]

tag -1 pending

Bug #909155 [apt] apt-cache show multiple packages produces invalid output
Added tag(s) pending.

[Debian Bug Tracking System]

Your message dated Thu, 20 Sep 2018 19:19:14 +0000
with message-id <E1g34Tq-000CZy-***@fasolo.debian.org>
and subject line Bug#909155: fixed in apt 1.7.0~rc2
has caused the Debian Bug report #909155,
regarding apt-cache show multiple packages produces invalid output
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ***@bugs.debian.org
immediately.)