Hello, sorry then, I usually prefer to mention each backport what changed between the stable/testing and the backport itself, but if documentation says that this is not needed, I'm sorry for having changed it...
but the real question that comes out is: why aren't you a DD? :) you know your stuff, I never had to change a line on what I sponsor to you... and when I do it, it turns out its a mistake from my side :p I'm ready to advocate you G. Il giovedì 12 novembre 2020, 00:27:19 CET, Nicholas D Steeves <[email protected]> ha scritto: Hi Gianfranco, Thank you for sponsoring! Gianfranco Costamagna <[email protected]> writes: > Hello > Sponsored after adding > * Drop hardcoded dep on modern libgcc-s1, and breaks old initramfs-tools, > because these are not applicable to the backport. > > to changelog... > G. > I don't understand why adding this line was required, because I'm using best-practises for backports (merged changelog), and merging tag from testing, rather than forking for each release, and I'm generating the .changes file relative to the last upload to buster-backports (which is why this entry didn't appear the 5.9-1~bpo10+1 entry). Full changelog for buster-backports shows: btrfs-progs (5.9-1~bpo10+1) buster-backports; urgency=medium * Rebuild for buster-backports. -- Nicholas D Steeves <[email protected]> Thu, 05 Nov 2020 16:18:31 -0500 btrfs-progs (5.9-1) unstable; urgency=medium * New upstream release. -- Adam Borowski <[email protected]> Fri, 23 Oct 2020 21:22:35 +0200 btrfs-progs (5.7-1~bpo10+1) buster-backports; urgency=medium * Rebuild for buster-backports. * Drop hardcoded dep on modern libgcc-s1, and breaks old initramfs-tools, because these are not applicable to the backport. -- Nicholas D Steeves <[email protected]> Tue, 28 Jul 2020 20:31:55 -0400 btrfs-progs (5.7-1) unstable; urgency=medium Regards, Nicholas
