Your message dated Tue, 23 Jun 2026 23:03:18 +0200
with message-id <[email protected]>
and subject line Re: Bug#1140550: RM: openvpn-dco-dkms/0.0+git20251017-1
has caused the Debian Bug report #1140550,
regarding RM: openvpn-dco-dkms/0.0+git20251017-1
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.)
--
1140550: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1140550
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: [email protected], [email protected]
Control: affects -1 + src:openvpn-dco-dkms
User: [email protected]
Usertags: rm
Per the package description:
"You need OpenVPN 2.6.x with dco-support compiled in to use this.
This module does _not_ accelerate OpenVPN 2.7. For OpenVPN 2.7 you need the new
upstreamed kernel module ovpn (released first in Linux 6.16)."
In sid/testing openvpn is at version 2.7 and kernel 7+, so this package seems
useless (unless you want to backport to stable).
Eventually consider if useful to leave it in sid or remove there also.
Thanks.
--- End Message ---
--- Begin Message ---
Dear Fabio,
Am 22.06.26 um 16:22 schrieb Fabio Pedretti:
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: [email protected], [email protected]
Control: affects -1 + src:openvpn-dco-dkms
User: [email protected]
Usertags: rm
Per the package description:
"You need OpenVPN 2.6.x with dco-support compiled in to use this.
This module does _not_ accelerate OpenVPN 2.7. For OpenVPN 2.7 you need the new
upstreamed kernel module ovpn (released first in Linux 6.16)."
In sid/testing openvpn is at version 2.7 and kernel 7+, so this package seems
useless (unless you want to backport to stable).
Eventually consider if useful to leave it in sid or remove there also.
Please don't file RM requests without *any* coordination with the
maintainer.
While I agree that this module should be removed from Testing eventually
and should not be released with Forky, now is not the time. Partial
upgrades are a thing, and since it is so easy to install the forky
package in stable it can also serve as viable testing grounds.
It does no harm to keep it for now.
Bernhard
--- End Message ---
