bzr crashed with UnicodeDecodeError in _escape_cdata(): 'ascii' codec can't decode byte 0xc5 in position 11: ordinal not in range(128)

Bug #867808 reported by Philip Muškovac
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bzr (Ubuntu)
New
Undecided
Unassigned

Bug Description

I was committing a packaging change, and thanks to bzr commit now behaving like debcommit I couldn't edit the commit message which resulted in my correctly written name being in the changelog. Bzr doesn't seem to like the 'š' in the name though, so I had to use -m and write the whole changelog again.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: bzr 2.4.1-1ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
BzrDebugFlags: set()
BzrVersion: 2.4.1
CommandLine: ['/usr/bin/bzr', 'ci']
CrashDb: bzr
Date: Tue Oct 4 21:14:08 2011
ExecutablePath: /usr/bin/bzr
FileSystemEncoding: UTF-8
InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427)
InterpreterPath: /usr/bin/python2.7
Locale: en_US.UTF-8
PackageArchitecture: all
Platform: Linux-3.0.0-12-generic-x86_64-with-Ubuntu-11.10-oneiric
ProcCmdline: /usr/bin/python /usr/bin/bzr ci
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
 LANGUAGE=en_US.UTF-8
PythonVersion: 2.7.2
SourcePackage: bzr
Title: bzr crashed with UnicodeDecodeError in _escape_cdata(): 'ascii' codec can't decode byte 0xc5 in position 11: ordinal not in range(128)
UpgradeStatus: No upgrade log present (probably fresh install)
UserEncoding: UTF-8
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Philip Muškovac (yofel) wrote :
tags: removed: need-duplicate-check
Philip Muškovac (yofel)
visibility: private → public
Revision history for this message
Martin Packman (gz) wrote :

Please update to bzr-builddeb 2.7.9 which may fix this issue. If it doesn't please undupe this bug and say if there were any differences in the failure. Thanks!

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.