apt-utils: APT::FTPArchive::Packages::SHA512 option does the wrong thing
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apt (Debian) |
Fix Released
|
Unknown
|
|||
apt (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Precise |
Fix Released
|
High
|
Colin Watson |
Bug Description
SRU justification:
[Impact] Configuration of whether to generate SHA512 checksums for Packages files in apt-ftparchive doesn't work properly; setting APT::FTPArchive
[Test Case] Generate Packages files with APT::FTPArchive
[Regression Potential] Confined to apt-ftparchive. Probably best to diff Packages/Sources files before and after.
Original report follows:
Imported from Debian bug http://
Package: apt-utils
Version: 0.9.7.1
Severity: normal
Dear Maintainer,
I see a typo in ftparchive/
DoSHA1 = _config-
DoSHA256 = _config-
DoSHA256 = _config-
Second Do should be DoSHA512 and should use DoSHA512 option defined line 68
DoMD5 = _config-
DoSHA1 = _config-
DoSHA256 = _config-
DoSHA512 = _config-
Christian
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 3.4.4 (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=
Shell: /bin/sh linked to /bin/dash
Versions of packages apt-utils depends on:
ii libapt-inst1.5 0.9.7.1
ii libapt-pkg4.12 0.9.7.1
ii libc6 2.13-34
ii libdb5.1 5.1.29-5
ii libgcc1 1:4.7.1-3
ii libstdc++6 4.7.1-3
apt-utils recommends no packages.
Versions of packages apt-utils suggests:
ii xz-utils 5.1.1alpha+
-- no debconf information
Related branches
Changed in apt (Debian): | |
importance: | Undecided → Unknown |
status: | New → Fix Released |
description: | updated |
description: | updated |
tags: |
added: verification-done removed: verification-needed |
summary: |
- apt-utils: Ignore APT::FTPArchive::Packages::SHA512 option + apt-utils: APT::FTPArchive::Packages::SHA512 option does the wrong thing |
This was fixed in quantal (upstream git commit 8e5d47a3a4e7358 35498574a58e0a3 3de04a0377) , but needs to be fixed in precise. We should get this done before Launchpad production is upgraded from lucid to precise.