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

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

Your message dated Sun, 22 Dec 2024 20:23:56 +0100
with message-id <Z2hnTIWkI-wFmc5S@ramacher.at>
and subject line Re: Bug#1088607: transition: dpdk
has caused the Debian Bug report #1088607,
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.)


-- 
1088607: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1088607
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
X-Debbugs-CC: pkg-dpdk-devel@lists.alioth.debian.org zigo@debian.org

Hello Thomas and Release Team,

As we did for Bullseye and Bookworm, we are proposing the following
plan to allow Trixie to ship with the latest LTS versions of DPDK and
OVS. This will let us make use of the full LTS support windows for both
projects, as we have done for the past few releases.

Upload OVS snapshot from git (with new sonames/package renames if
necessary), new OVN, DPDK 24.11 (currently in experimental) in early-
to-mid December to unstable, to finish the transition. All other
reverse build-deps of DPDK have already been prepared and uploaded to
unstable/testing, and just need a binNMU (collectd, suricata, uhd).

Then, after OVS 3.5 releases in February, upload it unstable (no
soname/transition required, as only bug fixes will go in at that
point after the git snapshot).

The reason to use the git snapshot is that the OVS release that
supports DPDK 24.11 is only scheduled for February, which will likely
be too late for ABI transitions.

Would this plan work for everyone?

Bullseye and Bookworm tickets for reference:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024322
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974588
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974667

--- End Message ---
--- Begin Message --- 
On 2024-12-16 15:40:57 +0000, Luca Boccassi wrote:
> On Sun, 15 Dec 2024 at 19:45, Sebastian Ramacher <sramacher@debian.org> wrote:
> >
> > Control: tags -1 confirmed
> > Control: forwareded -1 https://release.debian.org/transitions/html/auto-dpdk.html
> >
> > On 2024-12-12 13:36:18 +0000, Luca Boccassi wrote:
> > > We now have both dpdk and openvswitch in experimental, all built and
> > > autopkgtest'ed and ready to go. Any chance we could please get this one
> > > going so we can sort it before we all go out for the winter holidays?
> >
> > Please go ahead.
> 
> Thank you, uploaded dpdk and openvswitch to unstable, all built fine
> so will be in the next dinstall.
> Please schedule binmus for collectd, uhd, suricata at your earliest
> convenience. Thanks!

The old binaries got removed from testing. Closing

Cheers
-- 
Sebastian Ramacher

--- End Message ---
Reply to: