helpSavannah Administration - Support: sr #110315, remove master and placeholder...


sr #110315: remove master and placeholder branch

Submitter:  Mark J. Olesen <markjolesen>
Submitted:  Thu 24 Sep 2020 04:29:32 PM UTC
Category:  Source code repositories - developer access Priority:  5 - Normal
Severity:  1 - Wish Status:  In Progress
Assigned to:  rwp Operating System:  GNU/Linux
Open/Closed:  Open
* Mandatory Fields

Add a New Comment (Rich Markup)

Comment Type & Canned Response:


( Jump to the original submission )

Tue 20 Jul 2021 10:03:37 PM UTC, comment #6: 

this issue can be closed. thanks

Mark J. Olesen <markjolesen>
Tue 06 Oct 2020 10:34:21 PM UTC, comment #5: 

I appreciate your efforts. You can actually just completely remove the git repository.

I am waiting to hear back from GNU eval folks on the submission status of KasoVerb v3. I think because of COVID and fixing (non-compliant) issues in between, it has been a very lengthy process.
The last communication I had with eval is nobody has looked at it yet. However, the person who has worked on it in the past (ineiev) has been remarkable.

If it is approved, I will upload the tarball reviewed and create a git repository on the new GNU Savannah project page.

If it is not approved, well, I guess I will recreate the git repository and load everything there.

Either way KasoVerb v1 and KasoVerb v2 bzr repo can remain intact as an archive.

Hopefully that clarifies what we are up to? If you have other questions do not hesitate to ask.

Thank you

Mark J. Olesen <markjolesen>
Fri 02 Oct 2020 08:23:05 PM UTC, comment #4: 

I'll wait until you have successfully uploaded your new master branch just in case there is some unexpected trouble there. I am just a little nervous that there will be an error occur when you make the next push because I am often nervous due to errors springing up eternally in the most unexpected places. :-)

Bob Proulx <rwp>
Site Administrator
Fri 02 Oct 2020 07:37:52 PM UTC, comment #3: 


I see the branch and also see history at the web interface page:

You can safely remove everything from git at this time and then close the ticket.

Thanks for quick turnaround and help.

Mark J. Olesen <markjolesen>
Fri 02 Oct 2020 12:06:19 AM UTC, comment #2: 

I'll say done but will hold the ticket open until you complete what you are wanting to do.

I made a safety backup copy of master as master-oldconversion so that nothing would be lost.  Then noting that "placeholder" was the same I deleted both placeholder and master branches.  With those out of the way I believe that should enable you to upload your new repository branches with no trouble.

As far as the bzr repository goes we would normally advise to keep it around for historical reasons.  For exactly the reasons you mention.  It's the original history of the project through that time.  Therefore by default we would preserve it.

Please let us know if the git repository changes are okay for you and I will then close out the ticket.

Bob Proulx <rwp>
Site Administrator
Thu 24 Sep 2020 04:32:32 PM UTC, comment #1:

Mark J. Olesen <markjolesen>
Thu 24 Sep 2020 04:29:32 PM UTC, original submission:  

I migrated from bzr to git sometime ago. The git changes are a massive refactor and allot of reformatting.

I would like to keep the bzr repository intact. The bzr repository contains real history.

I would like to remove or delete the git repository and then push or create the repo with one big change.

I tried doing this manually but get an error:'
$ git push origin :master   
Enter passphrase for key '/home/markjolesen/.ssh/id_rsa':
remote: error: By default, deleting the current branch is denied, because the next
remote: error: 'git clone' won't result in any file checked out, causing confusion.
remote: error:
remote: error: You can set 'receive.denyDeleteCurrent' configuration variable t
remote: error: 'warn' or 'ignore' in the remote repository to allow deleting th
remote: error: current branch, with or without a warning message.
remote: error:
remote: error: To squelch this message, you can set it to 'refuse'.
remote: error: refusing to delete the current branch: refs/heads/master
 ! [remote rejected] master (deletion of the current branch prohibited)
error: failed to push some refs to ''

Thank you.

Mark J. Olesen <markjolesen>


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

Attach Files:

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 markjolesen (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 2 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2020-10-02 rwp StatusNone In Progress
        Assigned toNone rwp

    Back to the top

    Powered by Savane 3.9