Re: Fixing Wireguard spec file

2019-02-04 Thread Joe Doss
On 2/4/19 6:38 PM, Dominique Martinet wrote: It's the second time I read wireguard would be coming in the 5.0 kernel here - what makes you folk say that? I certainly haven't seen anything to that extent lately and 5.0 is petty well under way, something as big a zinc likely won't make the cut this

Re: Fixing Wireguard spec file

2019-02-04 Thread Dominique Martinet
Joe Doss wrote on Mon, Feb 04, 2019 at 03:43:59PM +: > I know what akmods are and I don't have the bandwidth on my end to > switch to them with WireGuard coming in the 5.0 kernel. It's the second time I read wireguard would be coming in the 5.0 kernel here - what makes you folk say that? I ce

Re: Fixing Wireguard spec file

2019-02-04 Thread Joe Doss
Was dkms working before you did the upgrade or was it already in a broken state? wireguard-dkms-0.0.20190123-2.fc29.noarch won't fix an already broken install, so you need to remove it and then install the new version. It should hopefully fix it moving forward. I started a thread on the WireGua

Re: Fixing Wireguard spec file

2019-02-04 Thread Joe Doss
I know what akmods are and I don't have the bandwidth on my end to switch to them with WireGuard coming in the 5.0 kernel. Joe ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Fixing Wireguard spec file

2019-01-31 Thread Germano Massullo
Joe, I found a machine on which I can reproduce the problem. I installed wireguard-dkms-0.0.20190123-2.fc29.noarch on top of wireguard-dkms-0.0.20190123-1.fc29.noarch but the machine while running # dkms autoinstall still returns Error! Could not locate dkms.conf file. File: /var/lib/dkms/wireguard

Re: Fixing Wireguard spec file

2019-01-31 Thread Germano Massullo
Il giorno gio 31 gen 2019, 00:15 Joe Doss ha scritto: > Hey Germano, > > I have a working RPM that does not error out with Error! Could not locate > dkms.conf file if you want to test it out before I push it to copr. > Hi Joe, I can test it on next Wireguard snapshot release, actually I cannot

Re: Fixing Wireguard spec file

2019-01-31 Thread Fabio Valentini
On Thu, Jan 31, 2019, 00:15 Joe Doss Hey Germano, > > I have a working RPM that does not error out with Error! Could not locate > dkms.conf file if you want to test it out before I push it to copr. > > > https://copr-be.cloud.fedoraproject.org/results/jdoss/wireguard-testing/fedora-29-x86_64/00852

Re: Fixing Wireguard spec file

2019-01-30 Thread Joe Doss
Hey Germano, I have a working RPM that does not error out with Error! Could not locate dkms.conf file if you want to test it out before I push it to copr. https://copr-be.cloud.fedoraproject.org/results/jdoss/wireguard-testing/fedora-29-x86_64/00852015-wireguard-dkms/wireguard-dkms-0.0.20190123

Re: Fixing Wireguard spec file

2019-01-30 Thread Joe Doss
I am actively trying to track down why DKMS is not removing the old WireGuard version correctly. I suspect it is something to do with DKMS as other WireGuard users that use DKMS for things like ZFS (https://utcc.utoronto.ca/~cks/space/blog/linux/MyKernelUpdateSteps) are setting the same kinds o

Re: Fixing Wireguard spec file

2019-01-29 Thread Germano Massullo
Il giorno mar 29 gen 2019 alle ore 17:39 Nicolas Chauvet ha scritto: > There is a wireguard package maintained by Robert-André Mauchin on RPM > Fusion that at least... works. Ah I did not know that, thank you ___ devel mailing list -- devel@lists.fedora

Re: Fixing Wireguard spec file

2019-01-29 Thread Nicolas Chauvet
Le mar. 29 janv. 2019 à 16:33, Germano Massullo a écrit : > > This [1] is the Wireguard spec file from upstream Copr repo [2]. > Wireguard will be included in kernel 5.0, but meanwhile we are using it as > dkms. There is a wireguard package maintained by Robert-André Mauchin on RPM Fusion that at

Fixing Wireguard spec file

2019-01-29 Thread Germano Massullo
This [1] is the Wireguard spec file from upstream Copr repo [2]. Wireguard will be included in kernel 5.0, but meanwhile we are using it as dkms. The only problem is that at every Wireguard upgrade, a manual action is required. For example now that I have installed 0.0.20190123, I have to remove t