Launchpad projet edit default branch not possible

Asked by Valentin Hamon

Hello,

I got an error message when I try to modify a project's code default branch :

<<
Oops!
Sorry, something just went wrong in Launchpad.
We’ve recorded what happened, and we’ll fix it as soon as possible. Apologies for the inconvenience.
(Error ID: OOPS-a9a918a3f409915cdf7947c22ff834de)
>>

https://code.launchpad.net/~armadito/armadito-web-ui/+git/main/+edit

I'm trying to change from /refs/heads/master to /refs/heads/DEV.
Do you have any idea of what could lead to that error ?

Thanks in advance,

Valentin.

Question information

Revision history for this message
Colin Watson (cjwatson) said :
#1

That's an imported repository, and you can't change properties of those in Launchpad. The default branch is supposed to be mirrored from GitHub, and it's a bug that it doesn't appear to be happening in this case. Could you please create a bug report from this question and we'll look into that?

I'd suggest also filing a separate bug report about the fact that this was an OOPS rather than an inline error in the page.

Revision history for this message
Valentin Hamon (vhamon) said :
#2

Okay, I think that I know the reason for this bug.

In fact, that project had no branch master on github when I imported it to launchpad. Then, I had problems building recipe because HEAD was not found. Also, I solved that problem by adding a master branch on github. Building recipe was then possible with master branch.

Also, now when I re-import from github, I got that error message :

2017-01-25 13:08:39 INFO error: Multiple remote HEAD branches. Please choose one explicitly with:
2017-01-25 13:08:39 INFO git remote set-head source DEV
2017-01-25 13:08:39 INFO git remote set-head source master
2017-01-25 13:08:39 INFO Unable to fetch default branch: Command '['git', 'remote', 'set-head', 'source', '--auto']' returned non-zero exit status 1

Do you think that there is there anything I can do on my side ?

Revision history for this message
Colin Watson (cjwatson) said :
#3

Yes, that error message is the problem here. I don't think there's anything you can do on your side, no; that's why I asked you to turn this into a bug report.

Revision history for this message
Valentin Hamon (vhamon) said :
#4

Okay, I created two bugs like you asked.

Can you help with this problem?

Provide an answer of your own, or ask Valentin Hamon for more information if necessary.

To post a message you must log in.