Long descriptions missing from apt cache - affects software-center etc

Thanks for taking your time to reporting this issue and help making Ubuntu better.

I can confirm this issue, I don't see the long description with apt 1.0.9.10ubuntu6 on Ubuntu Wily either.

On my 15.04 system, I get the following output when looking up gimp:
...
SHA1: 5f4efa1fc89b4d78ebdecf4556ac17c5c477373d
SHA256: efd0f5e0ec64d921fca0b25b0333b83907fc63654b3c4657c144d41bc8923a68
Description-en: The GNU Image Manipulation Program
 GIMP is an advanced picture editor. You can use it to edit, enhance, and
 retouch photos and scans, create drawings, and make your own images.
 It has a large collection of professional-level editing tools and
 filters, similar to the ones you might find in Photoshop. Numerous
 fine-control settings and features like layers, paths, masks, and
 scripting give you total control over your images.
 .
 Many image file formats are supported, including JPEG, Photoshop (.psd),
 and Paint Shop Pro (.psp) files. It can also be used to scan and print
 photos.
 .
 To open files remotely (like over HTTP), install the gvfs-backends
 package.
 .
 To use a MIDI device (like a musical keyboard) as an input controller in GIMP,
 install libasound2 and read the how-to at /usr/share/doc/gimp/README.MIDI
Description-md5: ad6dd18a09fb86ea4529ac53f33168b9
Homepage: http://www.gimp.org/
...

Same problem here.

If you delete the /var/lib/apt/lists, then apt-cache show will show the long description.

If you apt-get update, then apt-cache show will once more not show the long description.

I've had a look into this and it seems that if I take the latest version of apt in wily and apply the changes as set out in https://github.com/Debian/apt/commit/8965b2f8e6738463c20f69e76ba888a8d77225e3 then I consistently get all descriptions showing both in English and other languages. I don't know the apt codebase, nor do I know c++, so this should be looked over by someone with a bit more knowledge.

They didn't transition apt* to gcc5
Maybe it should be considered to use 1.0.10.2 from Debian Stretch, installing here fixes this -
apt_1.0.10.2
apt-utils_1.0.10.2
apt-transport-https_1.0.10.2
libapt-pkg4.16_1.0.10.2

Otherwise some cherry picks or just wait for 16.04 which possibly could get more attention during dev, ect.

The patchset applied in ubuntu for the gcc5 transition wasn't complete; I thought that it would have been synced back by now, but it seems not… – I had added a few more changes on top of Michaels changes (including the one Kiwinote referred to) to make it not only build, but also build something passing our testcases (as the only partly working Translation-* trashes our testcases). That is also the cause for other recent bugreport like #1497534 here I would guess.

It is probably not the worst idea to think about applying 8965b2f8 (the one mentioned above) – even if it is technically an abibreak, in practice only libapt itself is using (and is actually able to use) the symbol which is why in newer libapt versions the symbol isn't even exported anymore. 130f34b7 should be applied as well for entirely different reasons (even through it isn't a security fix in any way, it should be dealt with as one). No idea where Ubuntu is in the release cycle frankly as I have other things to worry about at the moment, but instead of cherry-picking these it might be better to use the entire release. They are well tested by now and bugfix only…

Feel free to ask me for more details if need be, but expect delays as I read mail between two grape presses at the Most (pun intended, even through mostly a my-region-only pun).

And a, btw mc3man: I wouldn't advice to install the Debian version directly on Ubuntu – it depends on the wrong archive-keyring for example. At the very least, you should recompile it, then the buildsystem will take care of setting the right things.

I think merging to the latest Debian apt release is the saner thing here, as David hints at. It just needs me or Michael to find a few spare moments to get it done and uploaded. Will look in a bit.

This bug was fixed in the package apt - 1.0.10.2ubuntu1

---------------
apt (1.0.10.2ubuntu1) wily; urgency=medium

  * merged from debian/sid (LP: #1486061)
  * this fixes a subtle ABI difference between debian and ubuntu
  * add breaks for rdepends to ensure smooth wily->wily transtition
    for the ABI fix. this can be dropped post-wily

apt (1.0.10.2) unstable; urgency=high

  * Do not parse Status fields from remote sources

apt (1.0.10.1) unstable; urgency=medium

  * hide first pdiff merge failure debug message (Closes: 793444)
  * mark again deps of pkgs in APT::Never-MarkAuto-Sections as manual.
    Thanks to Raphaël Hertzog and Adam Conrad for detailed reports and
    initial patches (Closes: 793360) (LP: #1479207)
  * explicitly build-dep on g++ (>= 4:5.2) for gcc5 transition

apt (1.0.10) unstable; urgency=medium

  [ Zhou Mo ]
  * po: update zh_CN translation slightly
  * po: Update Simplified Chinese programs translation

  [ Mert Dirik ]
  * Turkish translation update for apt (Closes: #789491)

  [ Yuri Kozlov ]
  * Russian program translation update (Closes: 789709)

  [ Milo Casagrande ]
  * Italian program translation update (Closes: 782122)

  [ Beatrice Torracca ]
  * Italian manpage translation update (Closes: 776702)

  [ Julian Andres Klode ]
  * ExecFork: Use /proc/self/fd to determine which files to close
    (Closes: #764204)

  [ Michael Vogt ]
  * Prepare new 1.0.10 release with gcc5 abi transition

  [ David Kalnischkies ]
  * stop depending on copy-on-write for std::string
  * bump next-abi check above gcc5-abi bump
  * update symbols file to use gcc5 abi mangling

 -- Michael Vogt <email address hidden> Mon, 05 Oct 2015 16:20:37 +0200