[MASTER] <type 'exceptions.NameError'>: global name 'trans' is not defined with aptd 0.41+bzr646-0ubuntu2
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
aptdaemon (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Natty |
Fix Released
|
High
|
Unassigned |
Bug Description
Binary package hint: aptdaemon
this error just poped up when i was updating
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: aptdaemon 0.41+bzr646-
ProcVersionSign
Uname: Linux 2.6.38-8-generic i686
NonfreeKernelMo
Annotation: Applying software changes failed
Architecture: i386
Date: Mon Apr 18 12:03:41 2011
DesktopFile: /usr/share/
ExecutablePath: /usr/sbin/aptd
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110413.1)
PackageArchitec
SourcePackage: aptdaemon
Title: <type 'exceptions.
TransactionDepends: [[], [], [], [], [], [], []]
TransactionErro
TransactionKwargs: {}
TransactionLocale: en_US.UTF8
TransactionOutput:
TransactionPack
TransactionRole: role-commit-
UpgradeStatus: No upgrade log present (probably fresh install)
Changed in aptdaemon (Ubuntu): | |
importance: | Undecided → High |
status: | New → Triaged |
summary: |
- Error while updating or installing? --> [MASTER] <type - 'exceptions.NameError'>: global name 'trans' is not defined + [MASTER] <type 'exceptions.NameError'>: global name 'trans' is not + defined |
summary: |
[MASTER] <type 'exceptions.NameError'>: global name 'trans' is not - defined + defined with aptd 0.41+bzr646-0ubuntu2 |
I suspect this is actully a bug in 0.41+bzr646- 0ubuntu1 that just happens to get triggered on the update to 0ubuntu2
0.41+bzr646-
The relevant fix is: 0ubuntu2) natty; urgency=low
aptdaemon (0.41+bzr646-
* debian/ patches/ 01_fix_ locking. patch: patches/ 02_fix_ crash_on_ dpkg_disappear. patch:
- cherry pick from evfool, many thanks (LP: #764422)
* debian/
- add (empty) mapping the apt progress message that is triggered
when a empty package disappears
-- Michael Vogt <email address hidden> Mon, 18 Apr 2011 13:48:38 +0200
The bug is triggered of at the end of a transaction, so at the time that aptdaemon was updated it would trigger
the bug in the old (currently running) version.