On Sat, Feb 24, 2018 at 10:50 AM, Matthew Vernon <matt...@debian.org> wrote: > How so? Is there some difficulty with "git cherry-pick" or similar that I'm > missing?
It is a problem for anyone who expects for Debian packaging to be complete in the files provided in the Debian archives ( http://ftp.debian.org/debian/pool/main/p/pcre2/ ) If I have 5 patches to apply to a particular version, the debdiff and the .diff.gz provided make it very difficult for a Stable Release Team member (or anyone) to understand those changes since they are not logically split out. The release teams use debdiffs, not git repos, to review and approve packaging updates. > I think > the primarily git-based workflow dgit-maint-merge provides is the most > natural way to manage the package in Debian. gbp with 3.0 (quillt) is far more popular. The packaging workflow you are using here is rare in Debian. I don't use dgit, but I think the gbp workflow might actually be just about as smooth for you when packaging new versions as the maint-merge workflow. If so, it would allow your packaging to be more useful to the rest of the Debian community. >> Could you investigate switching to the dgit-maint-gbp workflow? > I have considered it, and I don't think it's appropriate for pcre2. After several months, I think we're repeating the same arguments and not really making any progress. So if you're unwilling to change, I suppose it's fine for this bug to be closed or wontfixed. Thanks, Jeremy Bicha
