> Have you tried push --overwrite to the branch?
Yes, but since the branch was already up-to-date nothing happened.
> If push --overwrite does not fix this, you can try:
>
> - rename the branch to say 2.x-broken
> - push a new branch
I've tried it two times. I once pushed with --overwrite, and once without. Both times it doesn't work, I think because it's still stacked on a (according to the file 814632-branches.tgz damaged) branch: 'Created new stacked branch referring to /+branch-id/450725.' I now reverted it all to the original situation.
> Marten, if you attach a tarball of your working copy of the branch to this bug,
> perhaps the Launchpad operators can replace the copy on the server with that.
> I'll save a copy of it so that we can investigate this later.
Done :)
> Have you tried push --overwrite to the branch?
Yes, but since the branch was already up-to-date nothing happened.
> If push --overwrite does not fix this, you can try: id/450725. ' I now reverted it all to the original situation.
>
> - rename the branch to say 2.x-broken
> - push a new branch
I've tried it two times. I once pushed with --overwrite, and once without. Both times it doesn't work, I think because it's still stacked on a (according to the file 814632-branches.tgz damaged) branch: 'Created new stacked branch referring to /+branch-
> Marten, if you attach a tarball of your working copy of the branch to this bug,
> perhaps the Launchpad operators can replace the copy on the server with that.
> I'll save a copy of it so that we can investigate this later.
Done :)
Thanks everybody for the help!