[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#934308: buster-pu: package dpdk/18.11.2-2+deb10u1



On Mon, 2019-09-02 at 14:03 +0100, Adam D. Barratt wrote:
> On 2019-08-21 12:48, Luca Boccassi wrote:
> > On Tue, 2019-08-20 at 23:49 +0100, Adam D. Barratt wrote:
> > > Control: tags -1 + confirmed
> > > 
> > > This request never made it to debian-release, most likely due to
> > > the
> > > size of the diff.
> > 
> > Sorry, didn't notice that!
> > 
> > > On Fri, 2019-08-09 at 13:54 +0100, Luca Boccassi wrote:
> > > > We would like to upload a new LTS release version of DPDK to
> > > > buster.
> > > > We have already done this previously in stretch, and it was
> > > > approved
> > > > for the 16.11 LTS series [1][2][3], but given this is a new
> > > > Debian
> > > > release in combination with a new LTS release train I have not
> > > > yet
> > > > uploaded to p-u and will wait for an explicit ACK. We would
> > > > like to
> > > > upload new 18.11 LTS versions as they are released upstream to
> > > > buster
> > > > -
> > > > EOL is projected in November 2020.
> > > 
> > > What's the plan for after that point?
> > 
> > Same as for stretch and 16.11 LTS - if there are critical and/or
> > security related bugs that affect the branch, we will do our best
> > to
> > backport the fixes as downstream maintainers.
> 
> This is partly my fault for assuming what you'd done, rather than 
> checking, but it appears that the fixes included in this upload are
> not 
> currently in unstable, which is one of the basic requirements for 
> updates via p-u. Further, p-u now has a higher version number than
> the 
> package in unstable.
> 
> As it stands currently, our choices for Saturday's point release are 
> either deciding to skip the dpdk update until 10.2, or asking ftp-
> master 
> to push the package from p-u to unstable (and testing) during the
> point 
> release.
> 
> Regards,
> 
> Adam

Hello Adam,

First of all, sorry for any troubles caused and thanks for checking.

I'm slightly confused though: unstable has 18.11.2-2, and p-u has a
+deb10u1 changelog-only rebuild of that - is this not the right
procedure? What is missing from unstable/testing?

-- 
Kind regards,
Luca Boccassi

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: