Breezy ignores BZR_EMAIL environment variable

Bug #1869178 reported by James Henstridge on 2020-03-26
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Breezy
Medium
Jelmer Vernooij

Bug Description

This is either a code bug or a documentation bug. A colleague found that his bzr configuration that relied on setting his email via an environment variable had stopped working after the upgrade to Breezy.

The user guide documents that the user can set their email address via the BZR_EMAIL environment variable, the same as bzr supported:

https://code.breezy-vcs.org/breezy/trunk/view/7500/doc/en/user-guide/setting_up_email.txt#L33

However, the code instead looks for BRZ_EMAIL:

https://code.breezy-vcs.org/breezy/trunk/view/7500/breezy/config.py#L538

If Breezy is intended to be a drop-in replacement for bzr, then I would expect it to respect the old tool's environment variables. Is there actually any benefit to renaming this environment variable?

Related branches

Jelmer Vernooij (jelmer) on 2020-03-26
Changed in brz:
status: New → Triaged
importance: Undecided → High
importance: High → Medium
assignee: nobody → Jelmer Vernooij (jelmer)
milestone: none → 3.1.0
Jelmer Vernooij (jelmer) on 2020-03-26
Changed in brz:
status: Triaged → Fix Committed
Jelmer Vernooij (jelmer) on 2020-06-08
Changed in brz:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers