This bug was fixed in the package apport - 2.0.1-0ubuntu11
---------------
apport (2.0.1-0ubuntu11) precise-proposed; urgency=low
* data/package-hooks/source_linux.py: If we report against an -lts-quantal
source package, move the source to "linux" and add a qa-kernel-lts-testing
tag, as per kernel team request in LP: #1004101 . Add source package hook
symlinks for source_linux-{,meta-}lts-quantal.py to source_linux.py.
* data/apport: apport: Also treat a binary as modified if the /proc/pid/exe
symlink does not point to an existing file any more. Backported from trunk
r2406. (LP: #984944)
apport (2.0.1-0ubuntu10) precise-proposed; urgency=low
* debian/apport.install: Actually ship the native-origins.d directory, so
that the previous bug fix for LP: #1004101 actually works.
apport (2.0.1-0ubuntu9) precise-proposed; urgency=low
[ Martin Pitt ]
* data/apport: Ignore a crash if the executable was modified after the
process started. This often happens if the package is upgraded and a
long-running process is not stopped before. Patch cherry-picked from trunk
r2296. (LP: #984944)
* Add etc/apport/native-origins.d/lts-q-backports: Accept
ppa:ubuntu-x-swat/q-lts-backport as official Ubuntu package repository, so
that users can report bugs and crashes against the backported kernel and
X.org stack. (LP: #1004101)
* data/general-hooks/ubuntu.py: Do not assume that all reports have a
ProblemType field. This will not be the case for updating a bug with
"apport-collect". (LP: #1004029)
* report.py: Do not change the SourcePackage: field if the binary package is
not installed and does not exist. This fixes source package hooks to
actually work in some cases where source and binary package names overlap.
Patch cherry-picked from trunk r2332. (part of LP: #993810)
* apport-gtk, apport-kde: Avoid collecting information twice in "bug update"
mode. This caused a crash in cases where the source package in a bug
report does not correspond to an installed binary package. Patch
cherry-picked from trunk r2334. (LP: #993810)
[ Brian Murray ]
* data/general-hooks/ubuntu.py: block reporting of package install failures
with error regarding 'not a debian format archive'. (LP: #1002535)
-- Martin Pitt <[email protected]> Thu, 28 Jun 2012 09:01:41 +0200
** Changed in: apport (Ubuntu Precise)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1002535
Title:
'not a debian format' package install failures should be Unreportable
Status in “apport” package in Ubuntu:
Fix Released
Status in “apport” source package in Precise:
Fix Released
Bug description:
In bug 1001715 we can see a package installation failure with the
message:
dpkg-deb: error: `/var/cache/apt/archives/openjdk-7-jre-
lib_7~u3-2.1.1~pre1-1ubuntu2_all.deb' is not a debian format archive
These should not be reportable as they are indicative a corrupt or
faulty package. I've committed a fix for this to apport for Quantal:
http://bazaar.launchpad.net/~ubuntu-core-
dev/ubuntu/quantal/apport/ubuntu/revision/1961
However, only 24 of these have been reported so far:
https://bugs.launchpad.net/ubuntu/?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=NEW&field.status%3Alist=INVALID&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field
.component-empty-marker=1&field.tag=not-debian-
format&field.tags_combinator=ANY&field.status_upstream-empty-
marker=1&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_no_package.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on
so an SRU may not be worth the work. In the event the we decide it is
Steve Langasek came up with the following for recreating the error
with a good package:
#!/bin/sh
set -e
for i in "$@"
do
case $i in
/var/cache/apt/archives/*.deb)
cp /bin/bash $i
;;
esac
done
exec /usr/bin/dpkg.real "$@"
SRU REGRESSION POTENTIAL: Very low, the new condition is very specific
on the error message in dpkg.log. It could potentially prevent real
bugs from being reported if a package file "a.deb" is damaged, but you
are trying to install a package "b.deb" in the same run which fails
for some other reason. That seems to be a corner case, though, and on
a system which managed to corrupt .deb files we do not have a lot of
faith in any more anyway.
SRU TEST CASE:
- Move dpkg aside: sudo mv /usr/bin/dpkg{,.real}
- Replace /usr/bin/dpkg with the wrapper from above, and make it executable
- Try to install a package, e. g. "sudo apt-get install pmount"
- Confirm that it fails with "is not a debian format archive"
- Apport should pop up; try to report the bug
- It will succeed in the precise version, but will abort with "cannot be
reported" with this fix.
- After that, don't forget to restore dpkg: sudo mv /usr/bin/dpkg{.real,}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1002535/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
