[request-tracker-maintainers] git repo at risk; upstream branch breakage

[Niko Tyni]

On Tue, Mar 26, 2013 at 12:50:33AM +0000, Dominic Hargreaves wrote:
 
> I just noticed that the upstream branch (and thus master
> which is merged from upstream) has ended up not being descended
> from the old upstream with the commit history back to 4.0.1.
> This appears to have been caused by git-dpm import-new-upstream,
> of 4.0.10 (the first use of git-dpm in this repo), even though it is
> not expected to do this.
> 
> I don't know why this has happened; clues welcomed if anyone knows
> what's going on here, otherwise please take this as a warning that
> I may have to do a forced push to repair things, meaning that anything
> based on the current master (post-4.0.10 import) will need to be 
> rebased.

Sounds weird. I'll try to have a look when anonscm.debian.org is reachable
again (it's refusing connections atm). No problem with the forced push
on my part FWIW.
-- 
Niko