"Aaron M. Ucko" <u...@debian.org> writes: > Yes, it looks like I may have time this week, possibly even tonight.
AFAICT, the only issue here is that the build process regenerates debian/patches/debian-changes without the patch adding a top-level .gitignore, so *subsequent* gbp buildpackage runs fail per this formal change unless you explicitly revert it in between. (debian-changes covers .gitignore for the sake of dgit.) The best long-term solution would of course be switching to a manually-managed quilt series, but I don't have time to split the patch up properly at the moment. I had an idea for a kludge involving making this file dynamic (as appropriate, copied from under debian/ and cleaned back up), but it yielded a somewhat cryptic error from dgit. Initial builds (including in particular automated ones) should be unaffected, so I'll leave everything as on this front for now; sorry for any inconvenience. At any rate, I will want to upload these changes myself, both to keep dgit happy and because I have one or two more formal tweaks to make first; I should have time this weekend. -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
