On Tue, 2019-03-26 at 17:51 +0100, Emilio Pozuelo Monfort wrote: > On 25/03/2019 18:20, Ben Hutchings wrote: > > On Tue, 2019-03-05 at 22:00 +0000, Ben Hutchings wrote: > > > On Fri, 2019-03-01 at 14:05 +0100, Emilio Pozuelo Monfort wrote: > > [...] > > > > (It > > > > may be unlikely for old suites to have users with new hardware, however it's > > > > possible and users that don't have it will be unaffected by the new firmware, so > > > > it wouldn't hurt to ship it.) > > > > > > > > My branch is for jessie but I can prepare it for stretch too if you think that's > > > > worth it. > > > > > > The current jessie-security version of firmware-nonfree is really a > > > backport from stretch. So I would prefer it if you update the stretch > > > branch first and then merge that to jessie-security. > > > > I've merged your changes to stretch, uploaded to stretch, and then > > merged stretch to jessie-security. Let me know if you want to do the > > upload to jessie-security or if I should do it. > > I don't mind either way. We should use -4~deb8u2 rather than -5~deb8u1 so that > we don't (temporarily) have a higher version in jessie than stretch until the > point release. I disagree. An upgrade should not undo security fixes, if we can avoid it. Ben. -- Ben Hutchings Beware of bugs in the above code; I have only proved it correct, not tried it. - Donald Knuth
Attachment:
signature.asc
Description: This is a digitally signed message part