mainSavannah Administration - Support: sr #108639, Delete linux-doc-hr

 
 

sr #108639: Delete linux-doc-hr

Submitter:  Sam Geeraerts <samgee>
Submitted:  Mon 25 Aug 2014 08:02:53 PM UTC
   
 
Category:  Source code repositories - developer access Priority:  5 - Normal
Severity:  2 - Minor Status:  Done
Privacy:  Public Assigned to:  rwp
Operating System:  None Open/Closed:  Closed
* Mandatory Fields

Add a New Comment Rich Markup
   

Thu 17 Nov 2016 11:43:54 PM UTC, comment #4: 

Sounds good.  I am going to say this is done then.  I looked and the bzr repository does indeed look like a directory per branch and that branch directory did indeed seem empty except for the .bzr file.  Not knowing any better and simply taking your word for it I have removed that directory from the repository.

If that doesn't handle this problem then let me know.  Actually either way I welcome feedback on whether simply removing that (mostly) empty directory is the right way to deal with this. :-)

Bob Proulx <rwp>
Site Administrator
Thu 03 Nov 2016 10:17:48 PM UTC, comment #3: 

Thanks for looking into this.

That branch was created with the wrong name, it should have been the Debian package name. I found that I could now delete the branch using the following command (which didn't work for me iirc when I opened the support request).

bzr rmbranch bzr+ssh://samgee@bzr.savannah.gnu.org/gnewsense/packages-ucclia/linux-doc-hr

That just leaves the empty folder. It probably contains a .bzr folder with some artifacts on disk. But the whole linux-doc-hr folder can be deleted. That will get rid of any doubt about where our code for this package is and about which packages we update for our ucclia release.

Sam Geeraerts <samgee>
Wed 02 Nov 2016 03:55:31 AM UTC, comment #2: 

Hi. The simple answer is no there hasn't.  Because there hasn't been any volunteers who are mothering over bzr repositories. I personally don't know very much about bzr at all.

Normally we are archive curators. Which means we never delete anything because that is the safe thing to do. However if the branch is simply a copy of what existed at that time then there isn't any reason to preserve it since the original still exists. Therefore I am sympathetic. If you were to tutor me through the process I would be happy to perform the action. Is that branch just a copy? What needs to be done to delete it? I see two commits by Dennis Worthem on it.


Bob Proulx <rwp>
Site Administrator
Tue 01 Nov 2016 11:06:43 PM UTC, comment #1: 

Any progress on this?

Sam Geeraerts <samgee>
Mon 25 Aug 2014 08:02:53 PM UTC, original submission:  

Please delete Bazaar branch bzr://bzr.sv.gnu.org/gnewsense/packages-ucclia/linux-doc-hr. It was created by mistake (doc-linux-hr is the right one).

Sam Geeraerts <samgee>

 

(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 rwp (Posted a comment)
  • -email is unavailable- added by samgee (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

    Follow 3 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2016-11-17 rwp StatusNone Done
        Open/ClosedOpen Closed
    2016-11-02 rwp Assigned toNone rwp

    Back to the top

    Powered by Savane 3.13-f8d8.
    Corresponding source code