bzr update of revisionless master falsely claims succes

Bug #259146 reported by Wouter van Heyst
4
Affects Status Importance Assigned to Milestone
Bazaar
Confirmed
Low
Unassigned

Bug Description

On irc a user (Tak) reported a problem where bzr told him to run update when he tried to commit, he did so, bzr told him all was fine, he committed again and got the exact same message. Message in question:

  bzr: ERROR: Bound branch BzrBranch6('file:///home/larstiq/tmp/ex/slave/') is out
   of date with master branch BzrBranch6('file:///home/larstiq/tmp/ex/master/').
  To commit to master branch, run update and then commit.
  You can also pass --local to commit to continue working disconnected.

Steps to reproduce:

bzr init master
bzr co master slave
cd slave
touch foo
bzr add foo
bzr ci --local -m 1
bzr ci # get message
bzr up # updated to revision 1
bzr ci # get message again

Revision history for this message
Matthew Fuller (fullermd) wrote :

Well, on the upside, if it DID succeed, it might run into bug 82555 8-}

Revision history for this message
James Westby (james-w) wrote :

Hi,

I can confirm this behaviour.

Thanks,

James

Changed in bzr:
importance: Undecided → Low
status: New → Confirmed
Jelmer Vernooij (jelmer)
tags: added: check-for-breezy
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.