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

Bug#884695: marked as done (transition: dpdk)

Your message dated Fri, 22 Dec 2017 12:34:24 +0100
with message-id <2d1b1189-e744-7912-6e79-4aea1d3c3b56@debian.org>
and subject line Re: Bug#884695: transition: dpdk
has caused the Debian Bug report #884695,
regarding transition: dpdk
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
884695: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884695
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
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.

Thanks!

-- 
Kind regards,
Luca Boccassi

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881641

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


--- End Message ---
--- Begin Message --- 
On 18/12/17 20:53, Luca Boccassi wrote:
> On Mon, 2017-12-18 at 18:42 +0000, Luca Boccassi wrote:
>> 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!
> 
> The upload to unstable is done. Thanks!

Good. Let's close this, as there's no transition to track. dpdk should migrate
normally.

Cheers,
Emilio

--- End Message ---
Reply to: