Illegal option names should be ignored
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Fix Released
|
Medium
|
Vincent Ladeuil |
Bug Description
Reported on IRC:
<exarkun> I can't push my branch: bzr: ERROR: Option 1,2 is not defined while expanding "lp:~exarkun/pyopenssl/tlsv1_{1,2}".
<exarkun> Can I work-around that somehow or do I have to pick a different branch name?
<mwhudson> you can't call a branch that on lp
<mwhudson> but that error is pretty special
<mwhudson> is it coming from curl or somethign?
<mwhudson> no, that makes no sense
<exarkun> File "/usr/lib/
<exarkun> raise errors.
<exarkun> ExpandingUnknow
<exarkun> with `return self.get_
<mwhudson> huh huh
<mwhudson> yeah, it's something in the bzr config machinery
<mwhudson> anyway, if you made it work client side, pretty sure lp would tell you to FOAD so try another name i guess
<exarkun> Yea okay. Thanks.
<mwhudson> valid_branch_
While in this specific case launchpad would have refuse the branch, bzr should not try to expand such option names in the first place.
For consistency, trying to register such an option name should also be forbidden (that won't catch the use of illegal option names in option values but is still better than allowing them).
Related branches
- Richard Wilbur: Approve
-
Diff: 59 lines (+11/-5)3 files modifiedbzrlib/config.py (+2/-2)
bzrlib/tests/test_config.py (+6/-0)
doc/en/release-notes/bzr-2.7.txt (+3/-3)
Changed in bzr: | |
assignee: | nobody → Vincent Ladeuil (vila) |
status: | Confirmed → In Progress |
Changed in bzr: | |
milestone: | none → 2.7b1 |
status: | In Progress → Fix Released |
tags: | added: config |