The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.This may go away after a while as the daemon eventually refreshes things (?) but I've not encountered this issue before so thought I'd note it.
I've had a sandbox project https://drupal.org/project/freebase_api for a few years. I finally did a D7 upgrade and need to start making downloadable releases (to use on http://simplytest.me/ etc)
I 'Promoted' the project as normal, and gave it the normal, reserved project name 'freebase_api'.
Nothing appeared to go wrong at that time, and I could set a recommended branch alright, and can 'create a release' that seems to identify my code correctly (! it sees my 7.x branch) but
- the version control tab https://drupal.org/project/freebase_api/git-instructions still refers to the sandbox URL dman@git.drupal.org:project/1126680.git
- the repository viewer linked to from the project page is now blank http://drupalcode.org/project/1126680.git
- the expected repo url is also blank http://drupalcode.org/project/freebase_api.git
- My development environment now has no valid 'origin' to point to, as although drupalcode can still see the old http://drupalcode.org/sandbox/dman/1126680.git , I can no longer work with it via git at dman@git.drupal.org:sandbox/dman/1126680.git
fatal: remote error: Repository does not exist. Verify that your remote is correct.
It feels like something fell over halfway through the promote/rename. I genuinely did give it the intended shortname when promoting. I don't have visibility to probe further.
Comments
Comment #1
dman commentedNot only does *something* know where my code is, I was able to get it to roll a 7.x-1.x release!
and it documents commits at https://drupal.org/node/1126680/commits
But where has the actual repo gone?
Comment #2
dman commentedDoes anybody know what I can do about this?
The only option open to me at the moment seems to be to fork my own project into a new namespace and try again. This is obviously a messy way to approach this, and I'd like to avoid leaving it in such a state.
Does anyone have the ability to correct the project name directly, or should I look at leaving this as unfixable/dead and start a new project?
I've been building functionality for someone else to test, and really need to get the d.o git repo co-operating.
Comment #3
dman commentedbump please...
I was demo-ing this to a number of folk at DrupalSouth this week, but I can't publish the updates for anyone to play with.
Comment #4
dman commentedOK.
So I've migrated the project to
https://drupal.org/project/freebaseapi
and am shutting down the broken
https://drupal.org/project/freebase_api
Looks like the promotion went smooth this time, still not sure what went wrong in the other one.
If someone finds any loose ends dangling in the freebase_api project, please delete everything there.