Hi,
Was trying to delete my development branches (phpsass, assetic, sprites and compasscompile) for quite some time now but got:

error: Cannot access URL http://git.drupal.org/project/sasson.git/, return code 22
fatal: git-http-push failed

Just found:

In order for your module to work correctly with the Drupal.org testing system and supporting projects like Git Deploy, development branches should always be named using the [Drupal version]-[Module version] pattern, never as master or develop.

So I guess this is the reason for this issue.

Would you be kind and help me get rid of these (already merged) branches ?

Comments

tsi’s picture

Please?

tsi’s picture

The problem now seems a bit different - I says the branches don't exist, but the version control page shows them in the select box. this is what I get

$ git push origin :compasscompile
error: unable to push to unqualified destination: compasscompile
The destination refspec neither matches an existing ref on the remote nor
begins with refs/, and we are unable to guess a prefix based on the source ref.
error: failed to push some refs to 'tsi@git.drupal.org:project/sasson.git'
helmo’s picture

Project: Git on Drupal.org » Version Control API -- Git backend
Version: » 6.x-2.x-dev
Component: Git » Git interaction

Well the 'compasscompile' branch definitely doesn't exist in Git anymore. I can confirm that via the repo viewer and by cloning the project myself.

The Version control tab gets the info from the Version Control API -- Git backend.
So there must be some caching issue in between that is stuck...?

I'm moving this to the versioncontrol_git queue to get some attention from the right people.

marvil07’s picture

Project: Version Control API -- Git backend » Git on Drupal.org
Version: 6.x-2.x-dev »
Component: Git interaction » Git
Category: support » bug
Status: Active » Postponed (maintainer needs more info)

This can be a real bug, but not sure.

What I think is happening: under some conditions, a branch removal is not actually removing the label from the database. Not sure what could be causing that. It could be as simple as the job on the beanstalkd queue was missed.

I have also reviewed that a full sync(vcapi-sync-repositories) solved the problem, so if there is not a way to reproduce the problem, the way to solve this project problem would be to execute drush vcapi-sync-repositories 31168 on the production server.

If possible, please provide a way to reproduce this.

tsi’s picture

Status: Postponed (maintainer needs more info) » Active

Seems like this is happening on Drupal's main repo too. there's a branch called "916388-menu-links-entities-reboot", see here: https://drupal.org/node/3060/git-instructions/916388-menu-links-entities...

I'm not sure what you're reffering to as the production server but I guess I don't have access to it.
All I really wanted was to get rid of the redundant branches, mainly "compasscompile" and "sprites".

helmo’s picture

Issue summary: View changes

One thing that might just work is to create a new compasscompile locally, push it and then try to delete it again.