On 24/11/2025 5:46 pm, Arnaud Rebillout wrote:
[2] is not reachable, maybe it's private?
Sorry, that should be fixed now.
Ideally I wanted to be able to fix the existing git repo, rather than
restart from scratch. The repo I gave in this bug report was under my
own namespace (because edited for the purpose of this bug report), but
in fact I have two repositories that are facing this issue, and already
uploaded, so I'd prefer to avoid force-pushing.
But this morning I spend a couple of hours on that again, failed again,
I keep banging my head against a wall it feels, so at this point any
solution will do. And thanks for spending the time on this issue :)
To be honest, I'm not sure the issue is fixable. There is no common
commit history for Git to work with, so even merging upstream and Debian
repositories is not possible.
git add remote ...
git merge <upstreamvcs>
If it were possible, Git would read the submodule information.
While it's a pain to start over, it is probably the least painful option
right now. Plus, you can more forwards.
I'll keep thinking about this.
Hugh
