Launchpad itself

Pushing to my branch does not result in any content on that branch

Asked by Helen McCall

I am trying to push my first contents to the branch I created a few days ago.

I have registered my key, and bzr appears to be pushing the data correctly. Except for two things:

1) at the end of the bzr output it says it created a new branch!

2) The branch lp:openshot/help-manual is still empty!

Here is what I did with bzr:

helen@pliny:~/projects/filming/OpenShot_development/openshot-help$ bzr launchpad-login wildnfree

helen@pliny:~/projects/filming/OpenShot_development/openshot-help$ ls -al
total 16
drwxr-xr-x 4 helen helen 4096 2009-07-22 01:17 .
drwxr-xr-x 7 helen helen 4096 2009-07-22 02:00 ..
drwxr-xr-x 6 helen helen 4096 2009-07-22 01:17 .bzr
drwxr-xr-x 3 helen helen 4096 2009-07-19 20:15 usr
helen@pliny:~/projects/filming/OpenShot_development/openshot-help$ bzr push lp:~wildnfree/openshot/help-manual --use-existing-dir
The authenticity of host 'bazaar.launchpad.net (91.189.90.11)' can't be established.
RSA key fingerprint is 9d:38:3a:63:b1:d5:6f:c4:44:67:53:49:2e:ee:fc:89.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added 'bazaar.launchpad.net,91.189.90.11' (RSA) to the list of known hosts.
Using default stacking branch /~openshot.developers/openshot/main at bzr+ssh://bazaar.launchpad.net/%7Ewildnfree/openshot/
Created new branch.

helen@pliny:~/projects/filming/OpenShot_development/openshot-help$ bzr push lp:~wildnfree/openshot/help-manual --use-existing-dir
No new revisions to push.

Question information

Language:
English Edit question
Status:
Answered
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Jeroen T. Vermeulen (jtv) said : 		#1

The "created new branch" message pretty much means that registering the branch did not allocate any actual storage for the branch on the server yet—since there was nothing to store—whereas your initial push did.

The output from the second push makes perfect sense: you pushed the branch once, which pushed everything that had been committed to it to the server, and then you do the same thing again which of course has no new information to push to the server.

But did you actually commit any changes to the branch? For instance, did you "bzr add usr" followed by "bzr commit"? You can tell whether there are any uncommitted files in your branch by doing "bzr st"

Can you help with this problem?

Provide an answer of your own, or ask Helen McCall for more information if necessary.

To post a message you must log in.