On Sat, Apr 23, 2016 at 04:36:26PM +0100, Dominic Hargreaves wrote: > Source: perl > Version: 5.20.2-3+deb8u4
> I analysed the 165 commits in upstream's git repository between > 5.20.2 and 5.20.3 and selected what I believe to be the 40-odd > relevant patches (the others are either non-functional changes in > release notes, Module::CoreList or changes for platforms Debian does > not support). Thanks for doing this! > In terms of practicalities, my preferred approach would be to cherry-pick > the commits individually into the git-dpm patched branch, thus producing > patch files in the usual way. The alternative would be to make a combined > patch fixing all issues in one file, but this seems to have no real > benefits and plenty of downsides. Separate commits would definitely be preferrable IMO. I wonder if it would be useful to prefix the patch (file)names with something else than the current 'debian/' or 'fixes/', perhaps '5.20.3/', to highlight their origins? This might at least make 'perl -V' output a bit clearer. Another thing: we need to make sure the fixes are in unstable + testing before pushing them to stable. In this case, given 5.20.3 was released before 5.22.1 (see perlhist.pod), I expect it's all fine but it shouldn't hurt to check. I guess I'm sort of volunteering :) -- Niko