apt-utils: xz support is gone.

Bug #1553770 reported by Colin Watson
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apt (Debian)
Fix Released
Unknown
apt (Ubuntu)
Fix Released
Undecided
Unassigned
Trusty
Fix Released
Undecided
Unassigned

Bug Description

Stable release update justification:

[Impact] apt-ftparchive fails to produce .xz compressed files with sufficiently large data sets. This prevents migration of the Ubuntu archive to .xz.
[Test Case] Grab trusty/main/amd64 with debmirror, construct a suitable file list, and ask apt-ftparchive to generate files for this with Packages::Compress set to include xz. We can easily test this on the Launchpad "dogfood" instance where we do QA of the archive publisher.
[Regression Potential] Confined to lzma/xz compression, which I think is basically just apt-ftparchive, but we should make sure that other compression methods still work there.

Original report follows:

Imported from Debian bug http://bugs.debian.org/751688:

Package: apt-utils
Version: 0.9.15.5
Severity: normal

Dear Maintainer,

Tested with 1.0.4 and reinstalled working 0.9.15.5

Packages::Compress seems to not work anymore with xz compression.

Only . (uncompressed), gzip and bzip2 seems to work, xz now return errors
(see at the bottom).

Same error with Sources::Compress

Christian

$ apt-ftparchive generate apt.conf
 dists/unstable/main/binary-amd64/:E: write, still have 32768 to write but
couldn't
E: IO to subprocess/file failed - write (0: Success)
E: write, still have 32768 to write but couldn't
E: IO to subprocess/file failed - write (0: Success)
E: write, still have 4096 to write but couldn't
E: IO to subprocess/file failed - write (0: Success)
E: write, still have 4096 to write but couldn't
E: IO to subprocess/file failed - write (0: Success)
E: write, still have 4096 to write but couldn't
E: IO to subprocess/file failed - write (0: Success)
E: write, still have 4096 to write but couldn't
E: IO to subprocess/file failed - write (0: Success)
E: write, still have 4096 to write but couldn't
E: IO to subprocess/file failed - write (0: Success)
E: write, still have 4096 to write but couldn't
E: IO to subprocess/file failed - write (0: Success)
E: write, still have 4096 to write but couldn't
E: IO to subprocess/file failed - write (0: Success)
E: write, still have 4096 to write but couldn't
E: IO to subprocess/file failed - write (0: Success)
E: write, still have 4096 to write but couldn't
E: IO to subprocess/file failed - write (0: Success)
E: write, still have 4096 to write but couldn't
E: IO to subprocess/file failed - write (0: Success)
E: write, still have 4096 to write but couldn't
E: IO to subprocess/file failed - write (0: Success)
E: write, still have 4096 to write but couldn't
E: IO to subprocess/file failed - write (0: Success)

E: Sub-process Compress child returned an error code (100)

Colin Watson (cjwatson)
description: updated
no longer affects: apt (Ubuntu Precise)
description: updated
Changed in apt (Debian):
importance: Undecided → Unknown
status: New → Fix Released
Revision history for this message
Colin Watson (cjwatson) wrote :

apt (1.2.5) unstable; urgency=medium

  [ Daniel Kahn Gillmor ]
  * apt-key del should correctly handle keyids prefixed with 0x

  [ David Kalnischkies ]
  * support APT::Get::Build-Dep-Automatic again in build-dep
  * add test for apt-key 0xKEY and use parameter expansion.
    Thanks to James McCoy for the suggestion. (Closes: 816691)
  * do not move not-failed pdiff-patches into CWD on failure (Closes: #816837)
  * get group again after potential remap in Source: parse.
    Thanks to Francesco Poli and Marc Haber for testdata. (Closes: 812251)

  [ Colin Watson ]
  * Fix lzma write support to handle "try again" case (Closes: #751688)

  [ Julian Andres Klode ]
  * Prevent double remapping of iterators and string views
  * debian/control: Set Standards-Version to 3.9.7

 -- Julian Andres Klode <email address hidden> Sun, 06 Mar 2016 19:47:45 +0100

Changed in apt (Ubuntu):
status: New → Fix Released
Revision history for this message
Adam Conrad (adconrad) wrote : Please test proposed package

Hello Colin, or anyone else affected,

Accepted apt into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.0.1ubuntu2.12 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in apt (Ubuntu Trusty):
status: New → Fix Committed
tags: added: verification-needed
Colin Watson (cjwatson)
tags: added: verification-done
removed: verification-needed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package apt - 1.0.1ubuntu2.12

---------------
apt (1.0.1ubuntu2.12) trusty; urgency=medium

  [ Colin Watson ]
  * Fix lzma write support to handle "try again" case (closes: #751688,
    LP: #1553770).

  [ David Kalnischkies ]
  * Handle moved mmap after UniqFindTagWrite call (closes: #753941,
    LP: #1445436).

 -- Colin Watson <email address hidden> Sun, 06 Mar 2016 19:01:04 +0000

Changed in apt (Ubuntu Trusty):
status: Fix Committed → Fix Released
Revision history for this message
Adam Conrad (adconrad) wrote : Update Released

The verification of the Stable Release Update for apt has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.