helpSavannah Administration - Support: sr #107118, Correction to Bzr access...

 
 

sr #107118: Correction to Bzr access instructions on Savannah project pages.

Submitted by:  Karl Fogel <kfogel>
Submitted on:  Thu 12 Nov 2009 10:50:27 PM UTC  
 
Category:  Savannah website Priority:  5 - Normal
Severity:  3 - Normal Status:  In Progress
Assigned to:  None Operating System:  None
Open/Closed:  Closed

Add a New Comment (Rich Markup)
   

You are not logged in

Please log in, so followups can be emailed to you.

 

( Jump to the original submission)

Thu 03 Jun 2010 07:18:06 PM UTC, comment #7: 

There was a typo in the bug number in comment #5.

https://savannah.gnu.org/support/?107395

Glenn Morris <gm>
Thu 03 Jun 2010 06:52:34 PM UTC, comment #6: 

I get "Error: Item not found" at  https://savannah.gnu.org/support/index.php?10739

Karl Fogel <kfogel>
Thu 03 Jun 2010 06:17:13 PM UTC, comment #5: 
Karl Berry <karl>
Site Administrator
Mon 01 Mar 2010 12:15:05 AM UTC, comment #4: 

A final ping from me on this.

Here are the latest instances of the existing instructions confusing people:

http://lists.gnu.org/archive/html/emacs-devel/2010-02/msg00432.html
http://lwn.net/Articles/376475/

Glenn Morris <gm>
Thu 28 Jan 2010 11:58:55 PM UTC, comment #3: 

Yes, that was a typo, sorry.  The second "emacs-bzr-repository" on that line is a mistake.

Karl Fogel <kfogel>
Thu 28 Jan 2010 07:54:34 PM UTC, comment #2: 

Please consider applying Karl's patch.

Since loggerhead access seems problematic, I would amend
the first section to read something like:

...where PATH/TO/BRANCH varies but can usually be figured out
  by browsing http://bzr.savannah.gnu.org/r/emacs

Is there a typo in the suggested "scp" command line?
"emacs-bzr-repository" appears twice at the end.

Glenn Morris <gm>
Wed 09 Dec 2009 06:14:17 PM UTC, comment #1: 

Heh, obviously in the proposed updated instructions, this

  "Developper [sic]"

should just be:

  "Developer"

Karl Fogel <kfogel>
Thu 12 Nov 2009 10:50:27 PM UTC, original submission:  

I'll use the 'emacs' project as an example, but I assume this applies to all projects that use Bazaar.

The Bazaar instructions at https://savannah.gnu.org/bzr/?group=emacs are wrong.  They currently say:

  Anonymous read-only access

  bzr branch http://bzr.savannah.gnu.org/r/emacs

  Note: these paths are the default paths. Maybe the project is using a different layout.

  Developper [sic] write access (ssh)

  bzr branch sftp://<membername>@bzr.savannah.gnu.org/srv/bzr/emacs

  You can also use scp and rsync if need be.

These instructions will not work for most projects, because the bzr branches are actually located at some deeper level in the repository.  Anyone invoking the above bzr commands will just get an error.  Also, scp and rsync don't know about the sftp:// protocol, so those commands would get an error for a completely different reason.

The instructions should be updated to say this:

  Anonymous Access

  bzr branch http://bzr.savannah.gnu.org/r/emacs/PATH/TO/BRANCH

  ...where PATH/TO/BRANCH varies but can usually be figured out
  by browsing the tree at http://bzr.savannah.gnu.org/lh/emacs

  Developper [sic] write access (ssh)

  bzr branch sftp://<membername>@bzr.savannah.gnu.org/srv/bzr/emacs/PATH/TO/BRANCH

  You may find it faster to just grab the entire repository and all its
  branches via scp or rsync, for example:

  scp -r <membername>@bzr.savannah.gnu.org:/srv/bzr/emacs/emacs emacs-bzr-repository emacs-bzr-repository

  Afterwards, the directory 'emacs-bzr-repository' will have all the data
  in its .bzr subdirectory, and each branch will also be a
  subdirectory (empty except for its own .bzr subdirectory).  To fill
  out a branch's working tree, just do 'cd branch' and 'bzr checkout'.

Karl Fogel <kfogel>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by karl (Posted a comment)
  • -email is unavailable- added by gm (Posted a comment)
  • -email is unavailable- added by djbclark
  • -email is unavailable- added by kfogel (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

     

     

    Follow 2 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2010-06-03 karl StatusNone => In Progress
    2009-12-18 djbclark Carbon-Copy- => Added djbclark

    Back to the top


    Powered by Savane 3.7