Merge lp:~gz/bzr/non_ascii_bzr_log_312841 into lp:bzr/2.5
Proposed by
Martin Packman
Status: | Merged |
---|---|
Approved by: | Jelmer Vernooij |
Approved revision: | no longer in the source branch. |
Merged at revision: | 6469 |
Proposed branch: | lp:~gz/bzr/non_ascii_bzr_log_312841 |
Merge into: | lp:bzr/2.5 |
Prerequisite: | lp:~gz/bzr/get_home_dir |
Diff against target: |
64 lines (+26/-7) 3 files modified
bzrlib/tests/blackbox/test_version.py (+17/-0) bzrlib/trace.py (+6/-7) doc/en/release-notes/bzr-2.5.txt (+3/-0) |
To merge this branch: | bzr merge lp:~gz/bzr/non_ascii_bzr_log_312841 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Jelmer Vernooij (community) | Approve | ||
Review via email: mp+91076@code.launchpad.net |
Commit message
Store the path to .bzr.log as unicode so it can be safely printed by `bzr version`
Description of the change
Fixes a UnicodeDecodeError where someone has a non-ascii home dir or sets one of the variables used to influence the location of .bzr.log to a non-ascii value. As per other changes along these, the trade off is that someone who sets BZR_LOG on a posix system to some random bytestring not in their locale will now get an error. That's a less likely scenario and can't be fixed without some bigger changes to how bzr deals with paths.
To post a comment you must log in.
On Wed, Feb 01, 2012 at 01:49:33PM -0000, Martin Packman wrote: /bugs.launchpad .net/bzr/ +bug/312841 /code.launchpad .net/~gz/ bzr/non_ ascii_bzr_ log_312841/ +merge/ 91076
> Martin Packman has proposed merging lp:~gz/bzr/non_ascii_bzr_log_312841 into lp:bzr/2.5 with lp:~gz/bzr/get_home_dir as a prerequisite.
>
> Requested reviews:
> bzr-core (bzr-core)
> Related bugs:
> Bug #312841 in Bazaar: "UnicodeDecodeError from bzr version when log file has non-ascii path"
> https:/
>
> For more details, see:
> https:/
>
> Fixes a UnicodeDecodeError where someone has a non-ascii home dir or sets one of the variables used to influence the location of .bzr.log to a non-ascii value. As per other changes along these, the trade off is that someone who sets BZR_LOG on a posix system to some random bytestring not in their locale will now get an error. That's a less likely scenario and can't be fixed without some bigger changes to how bzr deals with paths.
I'm sure there's a unicode symbol symbol expressing approval
somewhere, but I can't find it at the moment. For now, then:
merge approve
Cheers,
Jelmer