On Mon, Jul 29, 2019 at 07:13:02PM +0200, Guillem Jover wrote: > On Sat, 2019-07-27 at 03:28:23 +0200, Adam Borowski wrote: > > If a package has single-debian-patch in debian/source/options, quilt is not > > supposed to be used (it is technically still used because there's no > > quilt-less non-native format, and 3.0 has many upsides besides the downside > > of quilt). > > quilt(1) is never used nor depended on by dpkg-source. This is just a > serialization format, I guess the name is a bit unfortunate as it seems > to trip over people that dislike the tool.
Alas, I get hit by quilt errors pretty often. It also has a failure mode where it'll unapply whatever change I just did -- which can be data loss if not already committed to git. None of these errors happen on purely single-debian-patch trees, but outside contributors tend to separate out patches. > For example I've had in mind adding an extraction option that would > unpack the source, make it a git tree, and import the patch series > as git commits. That'd be nice for the initial import, yeah. > > Yet, the produced single patch still receives DEP3 headers. > > > These headers won't ever be filled out (there's no chance to do so without > > employing additional steps), are likely to contain invalid/outdated data, > > and tend to leak some state of intermediate development of the package > > I see how this is inconvenient. So I guess I'll either disable them > for the single-debian-patch case, or perhaps add a generic header stating > that this is an autogenerated patch due to the single-debian-patch option > or similar, and that there's no further information available. Yeah, either option would do the trick, thanks. > I think what you might actually want is to use debian/source/patch-header > or debian/source/local-patch-header, as documented in the dpkg-source(1) > man page to note where the actual patches are located, etc. Which would > have prevented the autogenerated headers to be output. Oooh, nice! Even an empty file would do. > > Thus, these headers do no good, and can do harm -- and in any case, they're > > spam. Thus, please suppress these headers if single-debian-patch is used. > > [ I think “spam” here is way over the top, but oh well. ] Automated useless text that comes repeatedly. :p But yeah, that's a pretty nasty word to use. A single big spam run can take as much of human time from the society as a murder -- thus I consider it to be as harmful. Pointless DEP3 headers are a papercut in comparison. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian is one big family. Including that weird uncle ⢿⡄⠘⠷⠚⠋⠀ and ultra-religious in-laws. ⠈⠳⣄⠀⠀⠀⠀
