Show bzr push command for empty branches

[thorwil]

It would be a great help to see the exact bzr push command needed for new, empty branches on the overview page. Could take the place of Recent Revisions.

[Diogo Matsubara (matsubara)]

What page are you looking at?

[thorwil (t-w-)]

The "Details" page for branches in "Code", for example:
https://code.launchpad.net/~t-w-/+junk/dynamic_scrollbar
Before there are revisions to list, of course.

[Christian Reis (kiko)]

AFAIK, if you are logged in and own the branch, you do get the exact command to push a branch in the "Update this branch" line. Can you show me a situation in which that isn't the case?

[thorwil (t-w-)]

Well, i created https://code.launchpad.net/~t-w-/+junk/dummy to be sure.

You do get to see:
  Update this branch: bzr push lp:~t-w-/+junk/dummy

Note that it says "Update", which is a bit too brief for a newcomer, I'd say. But the real problem with it is:

$ bzr push lp:~t-w-/+junk/dummy
bzr: ERROR: Transport operation not possible: http does not support mkdir()

I mean to recall it was sftp with full path and bzr+ssh should also work, but I had to research that and memory is fading already :}

[Christian Reis (kiko)]

On Sat, Aug 23, 2008 at 03:44:19PM -0000, thorwil wrote:
> $ bzr push lp:~t-w-/+junk/dummy
> bzr: ERROR: Transport operation not possible: http does not support mkdir()

If you bzr launchpad-login first, does this then work?
--
Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 3376 0125

[thorwil (t-w-)]

Yes, almost. I wasn't even aware of that command, which only supports my point.
There still seems to be a need for --use-existing-dir.

$ bzr launchpad-login t-w-
$ bzr push lp:~t-w-/+junk/dummy
bzr: ERROR: Target directory lp:~t-w-/+junk/dummy already exists, but does not have a valid .bzr directory. Supply --use-existing-dir to push there anyway.
$ bzr push --use-existing-dir lp:~t-w-/+junk/dummy
Created new branch.

[thorwil (t-w-)]

I fail to see how this is be a duplicate of https://bugs.launchpad.net/bugs/221343
Hmm, there's no way to mark bugs as related?
So I guess a solution to that other bug would remove the need for --use-existing-dir?
But then the user should still be shown that he should do a bzr launchpad-login before he can push the first time.

[Jonathan Lange (jml)]

Although bug 221343 starts off suggesting that "Register branch" initialize a Bazaar branch at the location, follow up comments suggest that the Register branch page include instructions for how to populate that branch.

What I'd really like to do is merge the two bug reports, seeing as they both are concerned with the same root problem—registering a hosted branch is confusing—and any good solution should fix them both.

It would really help me if you could summarize bug 221343, summarize bug 258610 and then (if it's not already obvious), list the ways they are different. That way I'll know we're on the same page.

[thorwil (t-w-)]

Bug 221343:
- Use "Register Branch" from a pre-existing, remotely hosted project. Choose "Branch Type: Hosted".
- Result: empty branch
- Expected(?): Create a branch using either of the "Team Collaboration" models with --no-trees set. (I don't have the insight to understand the consequences here)
- Alternative: Create empty branch and inform about necessary next step

Bug 258610:
- Use "Register Branch" to create an independent empty branch. Branch Type: Hosted.
- Result: empty branch as expected, but no correct info on how to continue.
- Desired: to see the exact steps required to push to the branch for the first time. To see the plain push command for any following push after first push has happened (that the link is stored for bzr push with no arguments is also a valuable info).

The initial difference is branching from a project vs creating an independent branch.
The first bug seems to have at least 2 solutions, the 2nd only one, afaics.
The common aspect is a possible fix by giving the necessary info (about state and) required next steps.

[Stéphane Maniaci (stephh)]

«
$ bzr push lp:~t-w-/+junk/dummy
bzr: ERROR: Target directory lp:~t-w-/+junk/dummy already exists, but does not have a valid .bzr directory. Supply --use-existing-dir to push there anyway.
»

Does anybody know why BZR is complaining about that on the first push ?

[mihai.ile (mihai.ile)]

Same thing happening to me "already exists, but does not have a valid .bzr directory. Supply --use-existing-dir to push there anyway."

[Launchpad QA Bot (lpqabot)]

Fixed in stable r12077 <http://bazaar.launchpad.net/~launchpad-pqm/launchpad/stable/revision/12077>.