--no-strict warning printed as tuple

Bug #562665 reported by Jelmer Vernooij on 2010-04-13
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Vincent Ladeuil

Bug Description

  affects bzr

The new --no-strict warning is printed as tuple. I now get:

(u'Working tree "/home/jelmer/src/subvertpy/trunk/" has uncommitted
changes (See bzr status). Use --no-strict to force the push.',)

while pushing.



Related branches

Robert Collins (lifeless) wrote :

Jelmer, as a member of ~bzr you can set bug status and importance - please do so when filing bugs unless you explicitly don't have an opinion :P.

Changed in bzr:
status: New → Confirmed
importance: Undecided → Critical
Vincent Ladeuil (vila) wrote :
Changed in bzr:
assignee: nobody → Vincent Ladeuil (vila)
milestone: none → 2.2b2
status: Confirmed → In Progress
Vincent Ladeuil (vila) on 2010-04-16
Changed in bzr:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers