etckeeper with bazaar stopped working for the update manager on upgrade to maverick

Bug #647475 reported by Nick Moffitt on 2010-09-25
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
bzr (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: bzr

I have used etckeeper with bazaar on this machine since karmic or so, and after an upgrade from lucid to maverick bug #616878 now causes update-manager to report an error:

 installArchives() failed: (Reading database ...
 (Reading database ... 5%
 (Reading database ... 10%
 (Reading database ... 15%
 (Reading database ... 20%
 (Reading database ... 25%
 (Reading database ... 30%
 (Reading database ... 35%
 (Reading database ... 40%
 (Reading database ... 45%
 (Reading database ... 50%
 (Reading database ... 55%
 (Reading database ... 60%
 (Reading database ... 65%
 (Reading database ... 70%
 (Reading database ... 75%
 (Reading database ... 80%
 (Reading database ... 85%
 (Reading database ... 90%
 (Reading database ... 95%
 (Reading database ... 100%
 (Reading database ... 290826 files and directories currently installed.)
 Preparing to replace couchdb-bin 1.0.1-0ubuntu2 (using .../couchdb-bin_1.0.1-0ubuntu3_amd64.deb) ...
 Unpacking replacement couchdb-bin ...
 Preparing to replace libunity0 0.2.42-0ubuntu3 (using .../libunity0_0.2.44-0ubuntu1_amd64.deb) ...
 Unpacking replacement libunity0 ...
 Preparing to replace libupower-glib1 0.9.5-2 (using .../libupower-glib1_0.9.5-3_amd64.deb) ...
 Unpacking replacement libupower-glib1 ...
 Preparing to replace totem-plugins 2.31.90-0ubuntu1 (using .../totem-plugins_2.31.90-0ubuntu2_amd64.deb) ...
 Unpacking replacement totem-plugins ...
 Preparing to replace totem-mozilla 2.31.90-0ubuntu1 (using .../totem-mozilla_2.31.90-0ubuntu2_amd64.deb) ...
 Unpacking replacement totem-mozilla ...
 Preparing to replace totem-common 2.31.90-0ubuntu1 (using .../totem-common_2.31.90-0ubuntu2_all.deb) ...
 Unpacking replacement totem-common ...
 Preparing to replace totem 2.31.90-0ubuntu1 (using .../totem_2.31.90-0ubuntu2_amd64.deb) ...
 Unpacking replacement totem ...
 Preparing to replace totem-gstreamer 2.31.90-0ubuntu1 (using .../totem-gstreamer_2.31.90-0ubuntu2_all.deb) ...
 Unpacking replacement totem-gstreamer ...
 Preparing to replace unity-asset-pool 0.8.16-0ubuntu1 (using .../unity-asset-pool_0.8.18-0ubuntu1_all.deb) ...
 Unpacking replacement unity-asset-pool ...
 Preparing to replace unity 0.2.42-0ubuntu3 (using .../unity_0.2.44-0ubuntu1_amd64.deb) ...
 Unpacking replacement unity ...
 Preparing to replace upower 0.9.5-2 (using .../upower_0.9.5-3_amd64.deb) ...
 Unpacking replacement upower ...
 Processing triggers for man-db ...
 Processing triggers for hicolor-icon-theme ...
 Processing triggers for gconf2 ...
 Processing triggers for bamfdaemon ...
 Rebuilding /usr/share/applications/bamf.index...
 Processing triggers for python-gmenu ...
 Rebuilding /usr/share/applications/desktop.en_GB.UTF8.cache...
 Processing triggers for desktop-file-utils ...
 Processing triggers for python-support ...
 Setting up couchdb-bin (1.0.1-0ubuntu3) ...
 Installing new version of config file /etc/couchdb/default.ini ...
 Setting up libunity0 (0.2.44-0ubuntu1) ...
 Setting up libupower-glib1 (0.9.5-3) ...
 Setting up totem-common (2.31.90-0ubuntu2) ...
 Setting up totem (2.31.90-0ubuntu2) ...
 Setting up totem-plugins (2.31.90-0ubuntu2) ...
 Setting up totem-mozilla (2.31.90-0ubuntu2) ...
 Setting up totem-gstreamer (2.31.90-0ubuntu2) ...
 Setting up unity-asset-pool (0.8.18-0ubuntu1) ...
 Setting up unity (0.2.44-0ubuntu1) ...
 Setting up upower (0.9.5-3) ...
 Processing triggers for libc-bin ...
 ldconfig deferred processing now taking place

 | Collecting changes [0] - Stage 1/5

 bzr: ERROR: Unable to determine your name.
 Please, set your name with the 'whoami' command.

If I run "sudo apt-get dist-upgrade" from a terminal, this problem does not occur. Presumably this is because I have 'bzr whoami' set for my account, but root does not. This strikes me as a more common problem than the use case presented in #616878 .

This is a regression from lucid.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: bzr 2.2.0-1
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
Architecture: amd64
Date: Sat Sep 25 13:29:07 2010
EcryptfsInUse: Yes
ProcEnviron:
 LC_COLLATE=C
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: bzr

Nick Moffitt (nick-moffitt) wrote :
Nick Moffitt (nick-moffitt) wrote :

This also breaks the software-centre.

Barry Warsaw (barry) wrote :

An unsatisfying workaround:

% sudo -i
% bzr whoami blah

This seems like basically a dupe of bug 616878, or at least another
manifestation of the same problem.

Nick Moffitt (nick-moffitt) wrote :

Yes, that's how I characterized it in the original filing.

Chris Jones (cmsj) wrote :

Where bzr is aware that it is running as uid=0, it should simply warn about identity and then use root@hostname. Breaking package transactions is an extremely undesirable thing to be doing imo.

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

Other bug subscribers