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

Bug#884695: transition: dpdk



On Mon, 2017-12-18 at 19:33 +0100, Emilio Pozuelo Monfort wrote:
> Control: tags -1 confirmed
> 
> On 18/12/17 13:16, Luca Boccassi wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian.org@packages.debian.org
> > Usertags: transition
> > 
> > Dear release team,
> > 
> > We would like to move the new DPDK LTS release 17.11-2 from
> > experimental to unstable. This breaks the various libraries ABI
> > compat,
> > so a transition is needed.
> > 
> > https://tracker.debian.org/pkg/dpdk
> > 
> > Reverse build dependency source package:
> > 
> > collectd
> > 
> > The reverse dependency builds fine with the new version of DPDK
> > without
> > any source changes. Note that it currently FTBS due to a different
> > and
> > unrelated build-dep [1]. Tested by disabling that other plugin and
> > rebuilding with the new DPDK version.
> > 
> > The new DPDK packages are all in experimental, having passed the
> > NEW
> > queue, and have built on all supported architectures.
> > 
> > Note that from this release we started to follow a boost-like
> > model, so
> > the ABI revision is named after the upstream major version (eg:
> > librte-
> > eal3 -> librte-eal17.11). This is done because most libraries built
> > from DPDK break ABI compat on every single major release.
> 
> There are no rdeps so no transition tracker... Since you confirm the
> only
> build-rdep is fine, please go ahead.
> 
> Emilio

Ah I see, I though reverse-recommends needed a transition as well.
Thanks!

-- 
Kind regards,
Luca Boccassi

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


Reply to: