[09:54] Hi, is there any way to maintain a list of patches to be applied while `debuild` is running? Afaik dpatch and quilt are supposed to be ran by the maintainer manually, before debuild... [10:00] IIRC quilt uses a "series" file where the patches (and their order) are listed (don't remember how dpatch is doing it) as the buildd needs to apply them too. But I don't know how it interacts with pure debuild (I've been always using pbuilder). [10:03] geser: thank you, I tried using the debian/ dir of a package that uses quilt, and the stock upstream/ dir, and nothing called quilt to apply the patches to the upstream dir when I ran debuild [10:03] So I'm guessing it's a manual process, unless there's something missing in debian/rules... [10:04] I don't think pbuilder would be any different; the source would still need to be pre-patched there, right? [10:04] I don't remember the details how quilt was used. You either had debian/rules to it or cdbs or debhelper [10:04] If you use the source format 3.0 (quilt) then this is done for you by dpkg-source [10:04] If you use 1.0 then you need code in debian/rules to apply and unapply the patches, and there are various helpers to do that [10:05] But most people should do the former [10:06] Laney: thank you, I'm using `git pull` to fetch the upstream source, that's why I'd like to avoid the use of `dpkg-source` or other utilities that would mess with the git tree... [10:06] If there's no infrastructure to let me apply pathes *while building*, then yeah I should revisit my choices :) [10:09] alkisg: Use a seperate branch for the Debian work. [10:10] Thank you Rhonda :) [10:11] Personally I also don't commit the patched files to git and am likewise annoyed with that dpkg insists of having the patches applied at all times, but that's the way things work these days, so … [10:12] I see little sense to have a) the files in debian/patches/* commited and on top of that the applied patches, too. That's somehow doubled. [10:20] That's exactly how I feel too :) [10:45] alkisg: I think there is some local option that you can set in the debian/source directory, but I stoped bothering and getting wound up about it. It feels awkward about it but managed to live with it. [10:46] alkisg: Thing is, dpkg(-source) needs to apply the patches to make sure that it wouldn't fail when starting to build it. So it's a safety thing to have them applied all the times. Seemingly that happened regularly enough to people that it was put in as a hard requirement. === alan_g_ is now known as alan_g|EOD