3:29 p.m.
I noticed that kmod-wireguard is being updated on F31, even after WireGuard became a part
of Linux kernel since 5.6.0. Shouldn't kernel>5.6.0 obsolete kmod-wireguard? Is it
kept and updated because it was originally installed via @commandline?
We had a discussion about not removing any obsolete packages recently, but I can't
think of any reason to keep kmod-wireguard---why is it even being updated for new kernel,
given that wireguard.ko is in kernel-core now?
3:35 p.m.
On 6/24/20 4:29 PM, Przemek Klosowski via devel wrote:
I noticed that kmod-wireguard is being updated on F31, even after
WireGuard became a part of Linux kernel since 5.6.0. Shouldn't
kernel>5.6.0 obsolete kmod-wireguard? Is it kept and updated because it
was originally installed via @commandline?
We had a discussion about not removing any obsolete packages recently,
but I can't think of any reason to keep kmod-wireguard---why is it even
being updated for new kernel, given that wireguard.ko is in kernel-core
now?
Can you point to the kmod-wireguard package? Kernel modules are not
allowed to be packaged separately from the kernel in official Fedora
repositories so if there's a kmod-wireguard package it must be from
either a COPR or a 3rd-party repo (unless something has really changed
in the last few months...)
4:02 p.m.
On 6/24/20 4:35 PM, Laura Abbott wrote:
On 6/24/20 4:29 PM, Przemek Klosowski via devel wrote:
> I noticed that kmod-wireguard is being updated on F31, even after
> WireGuard became a part of Linux kernel since 5.6.0. Shouldn't
> kernel>5.6.0 obsolete kmod-wireguard? Is it kept and updated because
> it was originally installed via @commandline?
>
> We had a discussion about not removing any obsolete packages
> recently, but I can't think of any reason to keep
> kmod-wireguard---why is it even being updated for new kernel, given
> that wireguard.ko is in kernel-core now?
>
Can you point to the kmod-wireguard package? Kernel modules are not
allowed to be packaged separately from the kernel in official Fedora
repositories so if there's a kmod-wireguard package it must be from
either a COPR or a 3rd-party repo (unless something has really changed
in the last few months...)
So this is the dnf log from the latest kernel upgrade:
2020-06-18T19:51:13Z DEBUG ---> Package
kmod-wireguard-5.6.15-200.fc31.x86_64.x86_64 0.0.20191219-3.fc31 will be
erased
kmod-wireguard-5.6.15-200.fc31.x86_64 x86_64 0.0.20191219-3.fc31
@@commandline 325 k
kmod-wireguard-5.6.15-200.fc31.x86_64-0.0.20191219-3.fc31.x86_64
2020-06-18T19:53:50Z DDEBUG Command: dnf -y install --disablerepo=*
/tmp/akmods.rRSdDv0E/results/kmod-wireguard-5.6.18-200.fc31.x86_64-0.0.20191219-3.fc31.x86_64.rpm
2020-06-18T19:53:50Z DDEBUG Extra commands: ['-y', 'install',
'--disablerepo=*',
'/tmp/akmods.rRSdDv0E/results/kmod-wireguard-5.6.18-200.fc31.x86_64-0.0.20191219-3.fc31.x86_64.rpm']
2020-06-18T19:53:50Z DEBUG ---> Package
kmod-wireguard-5.6.18-200.fc31.x86_64.x86_64 0.0.20191219-3.fc31 will be
installed
kmod-wireguard-5.6.18-200.fc31.x86_64 x86_64 0.0.20191219-3.fc31
@commandline 97 k
so the repo it's coming from is @commandline, but I am not doing
it---somehow akmods pulls it in? my repolist is:
repo id repo name
code Visual Studio Code (blush)
fedora Fedora 31 - x86_64
fedora-cisco-openh264 Fedora 31 openh264 (From Cisco) - x86_64
fedora-modular Fedora Modular 31 - x86_64
rpmfusion-free RPM Fusion for Fedora 31 - Free
rpmfusion-free-updates RPM Fusion for Fedora 31 - Free - Updates
rpmfusion-nonfree RPM Fusion for Fedora 31 - Nonfree
rpmfusion-nonfree-updates RPM Fusion for Fedora 31 - Nonfree - Updates
updates Fedora 31 - x86_64 - Updates
updates-modular Fedora Modular 31 - x86_64 - Updates
4:17 p.m.
There is an akmod-wireguard package in RPMFusion, so you probably installed
it from there are somepoint. You should be able to just uninstall the akmod.
-Ian
On Wed, Jun 24, 2020 at 10:03 PM Przemek Klosowski via devel <
devel(a)lists.fedoraproject.org> wrote:
On 6/24/20 4:35 PM, Laura Abbott wrote:
>
>
> On 6/24/20 4:29 PM, Przemek Klosowski via devel wrote:
>> I noticed that kmod-wireguard is being updated on F31, even after
>> WireGuard became a part of Linux kernel since 5.6.0. Shouldn't
>> kernel>5.6.0 obsolete kmod-wireguard? Is it kept and updated because
>> it was originally installed via @commandline?
>>
>> We had a discussion about not removing any obsolete packages
>> recently, but I can't think of any reason to keep
>> kmod-wireguard---why is it even being updated for new kernel, given
>> that wireguard.ko is in kernel-core now?
>>
>
> Can you point to the kmod-wireguard package? Kernel modules are not
> allowed to be packaged separately from the kernel in official Fedora
> repositories so if there's a kmod-wireguard package it must be from
> either a COPR or a 3rd-party repo (unless something has really changed
> in the last few months...)
So this is the dnf log from the latest kernel upgrade:
2020-06-18T19:51:13Z DEBUG ---> Package
kmod-wireguard-5.6.15-200.fc31.x86_64.x86_64 0.0.20191219-3.fc31 will be
erased
kmod-wireguard-5.6.15-200.fc31.x86_64 x86_64 0.0.20191219-3.fc31
@@commandline 325 k
kmod-wireguard-5.6.15-200.fc31.x86_64-0.0.20191219-3.fc31.x86_64
2020-06-18T19:53:50Z DDEBUG Command: dnf -y install --disablerepo=*
/tmp/akmods.rRSdDv0E/results/kmod-wireguard-5.6.18-200.fc31.x86_64-0.0.20191219-3.fc31.x86_64.rpm
2020-06-18T19:53:50Z DDEBUG Extra commands: ['-y', 'install',
'--disablerepo=*',
'/tmp/akmods.rRSdDv0E/results/kmod-wireguard-5.6.18-200.fc31.x86_64-0.0.20191219-3.fc31.x86_64.rpm']
2020-06-18T19:53:50Z DEBUG ---> Package
kmod-wireguard-5.6.18-200.fc31.x86_64.x86_64 0.0.20191219-3.fc31 will be
installed
kmod-wireguard-5.6.18-200.fc31.x86_64 x86_64 0.0.20191219-3.fc31
@commandline 97 k
so the repo it's coming from is @commandline, but I am not doing
it---somehow akmods pulls it in? my repolist is:
repo id repo name
code Visual Studio Code (blush)
fedora Fedora 31 - x86_64
fedora-cisco-openh264 Fedora 31 openh264 (From Cisco) - x86_64
fedora-modular Fedora Modular 31 - x86_64
rpmfusion-free RPM Fusion for Fedora 31 - Free
rpmfusion-free-updates RPM Fusion for Fedora 31 - Free - Updates
rpmfusion-nonfree RPM Fusion for Fedora 31 - Nonfree
rpmfusion-nonfree-updates RPM Fusion for Fedora 31 - Nonfree - Updates
updates Fedora 31 - x86_64 - Updates
updates-modular Fedora Modular 31 - x86_64 - Updates
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
4:18 p.m.
On 6/24/20 4:02 PM, Przemek Klosowski via devel wrote:
repo id repo name
code Visual Studio Code (blush)
fedora Fedora 31 - x86_64
fedora-cisco-openh264 Fedora 31 openh264 (From Cisco) - x86_64
fedora-modular Fedora Modular 31 - x86_64
rpmfusion-free RPM Fusion for Fedora 31 - Free
rpmfusion-free-updates RPM Fusion for Fedora 31 - Free - Updates
rpmfusion-nonfree RPM Fusion for Fedora 31 - Nonfree
rpmfusion-nonfree-updates RPM Fusion for Fedora 31 - Nonfree - Updates
updates Fedora 31 - x86_64 - Updates
updates-modular Fedora Modular 31 - x86_64 - Updates
This is most likely coming from the rpmfusion-free repo and it should be
safe to remove if you are running a kernel higher than 5.6.0.
Joe
--
Joe Doss
joe(a)solidadmin.com
4:24 p.m.
I noticed that kmod-wireguard is being updated on F31, even after
WireGuard became a part
of Linux kernel since 5.6.0. Shouldn't kernel>5.6.0 obsolete kmod-wireguard? Is
it
kept and updated because it was originally installed via @commandline?
We had a discussion about not removing any obsolete packages recently, but I can't
think of any reason to keep kmod-wireguard---why is it even being updated for new
kernel,
given that wireguard.ko is in kernel-core now?
wireguard-tools from fedora repo is
the replacement for the rpmfusion wireguard packages.
4:28 p.m.
On 6/24/20 4:29 PM, Przemek Klosowski via devel wrote:
I noticed that kmod-wireguard is being updated on F31, even after
WireGuard became a part of Linux kernel since 5.6.0. Shouldn't
kernel>5.6.0 obsolete kmod-wireguard? Is it kept and updated because
it was originally installed via @commandline?
We had a discussion about not removing any obsolete packages recently,
but I can't think of any reason to keep kmod-wireguard---why is it
even being updated for new kernel, given that wireguard.ko is in
kernel-core now?
It was akmod-wireguard (thanks Laura, Alexander, Joe, Leigh and Ian).
This leaves the question: Shouldn't kernel>5.6.0 obsolete kmod-wireguard
and akmod-wireguard? and maybe replace wireguard with wireguard-tools?
5:03 p.m.
On 6/24/20 4:28 PM, Przemek Klosowski via devel wrote:
It was akmod-wireguard (thanks Laura, Alexander, Joe, Leigh and
Ian).
This leaves the question: Shouldn't kernel>5.6.0 obsolete kmod-wireguard
and akmod-wireguard? and maybe replace wireguard with wireguard-tools?
Looking at this RPM's change log it looks like they are doing that:
* Tue Apr 14 2020 Nicolas Chauvet <kwizart(a)gmail.com> - 0.0.20191219-3
- Disable wireguard until obsoleted
https://pkgs.rpmfusion.org/cgit/free/wireguard-kmod.git/commit/?h=f31&...
--
Joe Doss
joe(a)solidadmin.com
5:16 p.m.
On 6/24/20 6:03 PM, Joe Doss wrote:
On 6/24/20 4:28 PM, Przemek Klosowski via devel wrote:
> It was akmod-wireguard (thanks Laura, Alexander, Joe, Leigh and Ian).
>
> This leaves the question: Shouldn't kernel>5.6.0 obsolete
> kmod-wireguard and akmod-wireguard? and maybe replace wireguard with
> wireguard-tools?
Looking at this RPM's change log it looks like they are doing that:
* Tue Apr 14 2020 Nicolas Chauvet <kwizart(a)gmail.com> - 0.0.20191219-3
- Disable wireguard until obsoleted
https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpkgs.rp...
I think that just prevents the installation of the module---I was
puzzled why the module is getting created in the first place, and the
answer was akmod-wireguard.
I argued that newer kernel installs should cause erasing of the
wireguard-related packages, even though they came from a different
repository (rpmfusion-free*).
5:36 p.m.
> I noticed that kmod-wireguard is being updated on F31, even
after
> WireGuard became a part of Linux kernel since 5.6.0. Shouldn't
> kernel>5.6.0 obsolete kmod-wireguard? Is it kept and updated because
> it was originally installed via @commandline?
>
> We had a discussion about not removing any obsolete packages recently,
> but I can't think of any reason to keep kmod-wireguard---why is it
> even being updated for new kernel, given that wireguard.ko is in
> kernel-core now?
It was akmod-wireguard (thanks Laura, Alexander, Joe, Leigh and Ian).
This leaves the question: Shouldn't kernel>5.6.0 obsolete kmod-wireguard
and akmod-wireguard? and maybe replace wireguard with wireguard-tools?
As rpmfusion isn't an official Fedora repository the kernel wouldn't
obsolete it, how would that work for the 100s of quasi fedora repos
that spring up all over the place?
Maybe rpmfusion should have something akin to fedora-obsolete-package
for components such as kernel-modules that are cleanly replaced by
something like kernel bits that are there by default.
Maybe the wireguard-tools package might want to obsolete it.
7:15 p.m.
On 6/24/20 5:36 PM, Peter Robinson wrote:
As rpmfusion isn't an official Fedora repository the kernel
wouldn't
obsolete it, how would that work for the 100s of quasi fedora repos
that spring up all over the place?
Maybe rpmfusion should have something akin to fedora-obsolete-package
for components such as kernel-modules that are cleanly replaced by
something like kernel bits that are there by default.
Maybe the wireguard-tools package might want to obsolete it.
This package isn't an official install method for WireGuard. My copr and
elrepo for EL are. Obsoleting it isn't something that should be done in
wireguard-tools IMO.
Joe
--
Joe Doss
joe(a)solidadmin.com
11:01 p.m.
We did attempt to obsolete it in f32
https://pkgs.rpmfusion.org/cgit/free/rpmfusion-free-obsolete-packages.git...
TBH I don't really like the idea much, removing peoples VPN isn't cool and leaves
them exposed.
4:48 a.m.
We did attempt to obsolete it in f32
https://pkgs.rpmfusion.org/cgit/free/rpmfusion-free-obsolete-packages.git...
TBH I don't really like the idea much, removing peoples VPN isn't cool and leaves
them exposed.
From what I understood of the thread it's purely removing the akmod
and the new kernels have the module so how does it break their VPNs?
6:33 a.m.
From what I understood of the thread it's purely removing the
akmod
and the new kernels have the module so how does it break their VPNs?
If you remove akmod-wireguard it will also remove the wireguard package which will cause
the VPN to stop functioning.
Wireguard/wireguard-tools is required for a working VPN.
4:48 p.m.
On Thu, Jun 25, 2020 at 6:33 AM Leigh Scott <leigh123linux(a)gmail.com> wrote:
> From what I understood of the thread it's purely removing the akmod
> and the new kernels have the module so how does it break their VPNs?
If you remove akmod-wireguard it will also remove the wireguard package which will cause
the VPN to stop functioning.
Wireguard/wireguard-tools is required for a working VPN.
That would be a rather serious flaw in the wireguard tools package to
have a dep on akmod-wireguard when it has been upstream and included
in the Fedora kernel-modules package for a few months at this point.
Either way, the kernel certainly isn't going to obsolete a package
from a non fedora repository, and kernel modules don't exist in the
fedora repositories, so there isn't much that we can do from the
fedora end.
5 p.m.
On Thu, Jun 25, 2020 at 10:49 PM Justin Forbes <jmforbes(a)linuxtx.org> wrote:
...snip...
That would be a rather serious flaw in the wireguard tools package
to
have a dep on akmod-wireguard when it has been upstream and included
in the Fedora kernel-modules package for a few months at this point.
The wireguard-tools package in the Fedora repo doesn't have a dependency on
any kmods/akmods [1]. The old package that was in RPMFusion (called just
wireguard) pulled in the kmod. Also, it appears that all of the RPMFusion
packages were retired in F32, so they don't exist in F32+.
-Ian
https://src.fedoraproject.org/rpms/wireguard-tools/blob/master/f/wireguar...
5:03 p.m.
On June 25, 2020 4:50:12 PM Justin Forbes <jmforbes(a)linuxtx.org> wrote:
On Thu, Jun 25, 2020 at 6:33 AM Leigh Scott
<leigh123linux(a)gmail.com> wrote:
>
>> From what I understood of the thread it's purely removing the akmod
>> and the new kernels have the module so how does it break their VPNs?
>
> If you remove akmod-wireguard it will also remove the wireguard package
> which will cause the VPN to stop functioning.
> Wireguard/wireguard-tools is required for a working VPN.
That would be a rather serious flaw in the wireguard tools package to
have a dep on akmod-wireguard when it has been upstream and included
in the Fedora kernel-modules package for a few months at this point.
wirerguard-tools has no dep on akmod-wireguard? Unless I'm misunderstanding
the point you are trying to make here?
5:07 p.m.
On Thu, Jun 25, 2020 at 6:04 PM Joe Doss <joe(a)solidadmin.com> wrote:
On June 25, 2020 4:50:12 PM Justin Forbes <jmforbes(a)linuxtx.org> wrote:
> On Thu, Jun 25, 2020 at 6:33 AM Leigh Scott <leigh123linux(a)gmail.com> wrote:
>>
>>
>>> From what I understood of the thread it's purely removing the akmod
>>> and the new kernels have the module so how does it break their VPNs?
>>
>>
>> If you remove akmod-wireguard it will also remove the wireguard package which
will cause the VPN to stop functioning.
>> Wireguard/wireguard-tools is required for a working VPN.
>
>
> That would be a rather serious flaw in the wireguard tools package to
> have a dep on akmod-wireguard when it has been upstream and included
> in the Fedora kernel-modules package for a few months at this point.
wirerguard-tools has no dep on akmod-wireguard? Unless I'm misunderstanding the point
you are trying to make here?
The Fedora wireguard-tools package would probably have a conditional
dep for the wireguard ko if it was going to have any at all:
Requires: (kmod(wireguard.ko) if kernel)
That makes it nice in containers and still ensures that if there is a
kernel installed, the kmod would be present.
--
真実はいつも一つ！/ Always, there's only one truth!
1399
days inactive
1400
days old
18 comments
9 participants
participants (9)
-
Alexander Ploumistos -
Ian McInerney -
Joe Doss -
Justin Forbes -
Laura Abbott -
Leigh Scott -
Neal Gompa -
Peter Robinson -
Przemek Klosowski