Your message dated Sun, 10 Jan 2021 17:33:42 +0000
with message-id <[email protected]>
and subject line Bug#974588: fixed in openvswitch 
2.15.0~git20210104.def6eb1ea+dfsg1-1
has caused the Debian Bug report #974588,
regarding openvswitch: DPDK 20.11 support and transition for bullseye
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 [email protected]
immediately.)


-- 
974588: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974588
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: openvswitch
Version: 2.13.0+dfsg1-12
Severity: normal
X-Debbugs-CC: [email protected] 
[email protected]
Tags: bullseye

Dear Openvswitch Maintainers,

We are scoping the src:dpdk 19.11 -> 20.11 transition. If possible,
we'd really like to go to bullseye with the latest upstream LTS, as
19.11 is EOL at the end of next year.

OVS support for DPDK 20.11 will be released upstream in v2.15, which is
due for release on February 15 [1].
Bullseye transition freeze is on January 12 [2], so the dates
don't align very well.

So we are looking to formulate a plan that you can agree with, to sort
this out.

Based on experience, what Ubuntu usually does to meet release deadlines
is to upload from git earlier than the release, so that all major
incompatibilities can be sorted. And then after the freeze, once the
release is officially out, do a final upgrade to the released version -
since a similar enough version was uploaded from git, and at the end of
a release cycle it's mostly bug fixes that land upstream, such an
upload is acceptable.

So we'd like to propose the following ideas:

- between now and December: upload v2.14, to minimize the later jump
- by the first week of January: upload 2.15~git from the tip of the
master branch to experimental
- stabilize and sort eventual build issues
- upload dpdk 20.11 and ovs 2.15~git to unstable
- upload 2.15 proper in February as a bug fix upload to unstable

What do you think? Does this sound like a workable plan?

We are of course happy to help - Ubuntu will go through the exact same
process for 21.04, so a lot of the work is "shared".

Thank you!

-- 
Kind regards,
Luca Boccassi

[1] https://docs.openvswitch.org/en/latest/internals/release-process/
[2] https://release.debian.org/bullseye/freeze_policy.html

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


--- End Message ---
--- Begin Message ---
Source: openvswitch
Source-Version: 2.15.0~git20210104.def6eb1ea+dfsg1-1
Done: Thomas Goirand <[email protected]>

We believe that the bug you reported is fixed in the latest version of
openvswitch, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thomas Goirand <[email protected]> (supplier of updated openvswitch package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Sun, 10 Jan 2021 14:56:30 +0100
Source: openvswitch
Architecture: source
Version: 2.15.0~git20210104.def6eb1ea+dfsg1-1
Distribution: unstable
Urgency: high
Maintainer: Debian OpenStack <[email protected]>
Changed-By: Thomas Goirand <[email protected]>
Closes: 974588
Changes:
 openvswitch (2.15.0~git20210104.def6eb1ea+dfsg1-1) unstable; urgency=high
 .
   [ Luca Boccassi ]
   * Merge branch 'master-dfsg' into 2.15
   * Bump dependency on libbpdk-dev >= 20.11 (Closes: #974588)
   * Refresh py3-compat.patch for v2.15
   * Realign armhf test skip range due to upstream changes
   * Use new --with-dpdk=shared configure flag value
 .
   [ Thomas Goirand ]
   * Blacklist test 532 (because non-deterministic).
Checksums-Sha1:
 b902739fa11b0ce97aaf2991009d45b2dd45fe71 3316 
openvswitch_2.15.0~git20210104.def6eb1ea+dfsg1-1.dsc
 a6c1a227f49995f50200c3864e2afafce3c05870 3711084 
openvswitch_2.15.0~git20210104.def6eb1ea+dfsg1.orig.tar.xz
 1018622824414351df7bf480661791f76983b7ef 50752 
openvswitch_2.15.0~git20210104.def6eb1ea+dfsg1-1.debian.tar.xz
 e6ca3aee2e534abc3be17fa55a53f748e623a07a 20154 
openvswitch_2.15.0~git20210104.def6eb1ea+dfsg1-1_amd64.buildinfo
Checksums-Sha256:
 2b947b94909b5a51bc3be64e34f44773ef977e17b190a4cb94408868bfec607e 3316 
openvswitch_2.15.0~git20210104.def6eb1ea+dfsg1-1.dsc
 bebd054c8a1c13433f64a91f11e85e7f3293a9ef29deec5dced39f8ceff3f397 3711084 
openvswitch_2.15.0~git20210104.def6eb1ea+dfsg1.orig.tar.xz
 fc9b5a3f83bcfcf080552d3ac5d4115ba69f40e50ae037e52d449f47da769f5e 50752 
openvswitch_2.15.0~git20210104.def6eb1ea+dfsg1-1.debian.tar.xz
 078108f84d87d191945e272e738289c2597eef25c735333315609fae06facfd1 20154 
openvswitch_2.15.0~git20210104.def6eb1ea+dfsg1-1_amd64.buildinfo
Files:
 c045e6d0714e91afbff75d95cca01d4a 3316 net optional 
openvswitch_2.15.0~git20210104.def6eb1ea+dfsg1-1.dsc
 1d283e0caebacdb1d019dc72b9dd6e55 3711084 net optional 
openvswitch_2.15.0~git20210104.def6eb1ea+dfsg1.orig.tar.xz
 ddd148d9150ce9681bc4a5f307468fc1 50752 net optional 
openvswitch_2.15.0~git20210104.def6eb1ea+dfsg1-1.debian.tar.xz
 ca01f60d95b26e8df6ae533f08f2c42d 20154 net optional 
openvswitch_2.15.0~git20210104.def6eb1ea+dfsg1-1_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAl/7NJUACgkQ1BatFaxr
Q/4H8RAAl7jhLtzYTwLiaFjrDW26WvyQ51uw+s5y6rpJ73/6RjRlphnMjjxlp+ML
Y96vuXPHGJteNoZoh4zo07rC5d88RYPS75/0CC8uDQBloqw/YnHXyn4vCkt/Ji83
HEHTEv0DZHm05mUJe2JUoY/zmtY8VtcmmJ6HiCtnoi/AaoVI3bWXu3DjtOym+0RR
fjHpkA1VtOV2SWSPBhG+BT6qQKECdkCN4ai9eKdvg1L8Kq6aG3LnCtlmhXNp+VkR
McoumUoMsrBTc2mpct0/IgS/mBKyLkSs0LK9DbswTgvtC/p9wmcFVKOqjlikEyVy
l724ASkqpiEoY6hYqYPT+XjoOdjgSaIkvBi+VUcsEZuA0vDaoDtKPcMcPljjZpYi
fNDXE+f1UOrfIus3tAQoNtUnQdS47ngpefrzmzVjQMhFUED4v2nhq8BuQngRZjGt
fjVSwI+ZJMXVFGtpRdlYznye/7D6x5g3bg67hR8+6nElEVpWNJOtNG+5G+UrP6qk
nU/qNIGr2nWsVWLFQXYpBatO+vcjXuxvtVyVuQ4HDMNtx6FFGESfeEM8DPbonI60
tmsIBplNi0s3/YjjU3Nt4hWvAVgP3ACko0JRkRWKhnbI2Iq9bgvXNdpfB3mWcZzQ
QbiQihz0ACFdjy3MAyI0ojujy5ST190GAUuL18y2HzUTGfcDGeE=
=NGJm
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to