"bzr update" command does not work

Bug #494522 reported by aidave on 2009-12-09
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Bazaar
Low
Unassigned
Kabikaboo
Undecided
Unassigned

Bug Description

This is hands down the most frustrating thing about using Bazaar.

It is easy to replicate on one of my launchpad projects. Simply try:
bzr branch lp:kabikaboo
Wait until there is a new revision, then run
bzr update

It NEVER pulls the new revision.
Instead, I have to delete the entire directory and run "bzr branch" again.

Whats the point of this VCS if the update command doesn't even get the newest files???

aidave (aidave) on 2009-12-09
Changed in kabikaboo:
importance: Undecided → High
status: New → Confirmed
aidave (aidave) wrote :

"bzr update" also gives the message "up to date at revision xx" when on Launchpad's site it clearly says there is a new revision.

Gordon Tyler (doxxx) wrote :

As for why "update" doesn't work, the description of the "branch" command says: "Update a tree to have the latest code committed to its branch." The tree here is your working tree, and its branch is your local branch of lp:kabikaboo. So when you do bzr update, it doesn't have anything to do because your working tree is up to date with its branch. "bzr update" is intended for use with checkouts, I believe.

Try "bzr pull" instead. If it complains that the branches have diverged, then you will have to use "bzr merge" to merge the latest revisions from lp:kabikaboo into your branch.

Changed in bzr:
status: New → Incomplete
importance: Undecided → Low
Gordon Tyler (doxxx) wrote :

Sorry, that first line should read: As for why "update" does work, the description of the update command...

Gordon Tyler (doxxx) wrote :

I'm really on a roll today. Let's try that at again: As for why "update" doesn't work, the description of the "update" command...

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Gordon Tyler wrote:
> Sorry, that first line should read: As for why "update" does work, the
> description of the update command...
>

To put another way

If you use "bzr branch" then to get the latest version from launchpad,
you need to do "bzr pull".

If you wanted a checkout, then you could have done "bzr checkout lp..."
and then "bzr update" would pull in the latest version from tip.

Arguably we could check if

1) The tree is already 'up-to-date'
2) And the tree is colocated with its branch
3) And then mention that what you may have meant was 'bzr pull'

 status confirmed
 importance low
 tags doc easy

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEUEARECAAYFAksf4I8ACgkQJdeBCYSNAAMamgCaAov9Tly6kKqhMyA42CQy25nT
+WkAlRzivcn7LCHeSoIYnYzJx2Cv6aQ=
=Frt8
-----END PGP SIGNATURE-----

Changed in bzr:
status: Incomplete → Confirmed

John, your idea is clever. Maybe too clever. I believe there has
been much discussion of confused expectations of the distinction
between branches and checkouts in the past. Your idea has the
potential to further blur that line in the mind of the new user.

On 12/9/09, John A Meinel <email address hidden> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Gordon Tyler wrote:
>> Sorry, that first line should read: As for why "update" does work, the
>> description of the update command...
>>
>
> To put another way
>
> If you use "bzr branch" then to get the latest version from launchpad,
> you need to do "bzr pull".
>
> If you wanted a checkout, then you could have done "bzr checkout lp..."
> and then "bzr update" would pull in the latest version from tip.
>
> Arguably we could check if
>
> 1) The tree is already 'up-to-date'
> 2) And the tree is colocated with its branch
> 3) And then mention that what you may have meant was 'bzr pull'
>
> status confirmed
> importance low
> tags doc easy
>
> John
> =:->
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (Cygwin)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEUEARECAAYFAksf4I8ACgkQJdeBCYSNAAMamgCaAov9Tly6kKqhMyA42CQy25nT
> +WkAlRzivcn7LCHeSoIYnYzJx2Cv6aQ=
> =Frt8
> -----END PGP SIGNATURE-----
>
> ** Changed in: bzr
> Status: Incomplete => Confirmed
>
> --
> "bzr update" command does not work
> https://bugs.launchpad.net/bugs/494522
> You received this bug notification because you are a member of bzr-qa,
> which is subscribed to Bazaar.
>
> Status in Bazaar Version Control System: Confirmed
> Status in Kabikaboo: Confirmed
>
> Bug description:
> This is hands down the most frustrating thing about using Bazaar.
>
> It is easy to replicate on one of my launchpad projects. Simply try:
> bzr branch lp:kabikaboo
> Wait until there is a new revision, then run
> bzr update
>
> It NEVER pulls the new revision.
> Instead, I have to delete the entire directory and run "bzr branch" again.
>
> Whats the point of this VCS if the update command doesn't even get the
> newest files???
>
>
>

Matthew Fuller (fullermd) wrote :

> Your idea has the potential to further blur that line in the mind of
> the new user.

I agree.

Jeremy Bicha (jbicha) on 2011-04-24
Changed in kabikaboo:
status: Confirmed → Invalid
importance: High → Undecided
Ernesto Palacios (ernestop) wrote :

I got confused with "bzr update" too, "bzr pull" was what i was looking for.
Maybe you should put this command on the five minutes tutorial:

http://doc.bazaar.canonical.com/latest/en/mini-tutorial/

It's not as intuitive as you may think.

Jelmer Vernooij (jelmer) on 2017-11-09
tags: added: check-for-breezy
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers