Peter Green writes ("Bug#1054630: dgit - cant import llvm-toolchain-15."):
> Correct me if I'm wrong here, but doesn't the import process
> only use information from the topmost changelog entry.I'm investigsting now. The faulty changelog entry indeed isn't the topmost one. However, dgit needs to use the changelog entry corresponding to the (first) import of that upstream version, for its synthetic commits representing the .origs. (dgit tries to make these stable, as that improves the synthetic git commit structure.) I think the best thing is to use dummy data for the authorship, and the date of the last non-broken changelog entry before the one it wants. But perhaps that's too complicated and dgit should just use today's data and dummy authorship if any of this archaeology fails. I'll work on some kind of fix. Ian. -- Ian Jackson <ijack...@chiark.greenend.org.uk> These opinions are my own. Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.
