WireGuard Archive on lore.kernel.org
 help / Atom feed
* Fedora DKMS Issues
@ 2019-02-04 17:01 Joe Doss
  2019-02-04 18:09 ` Joe Doss
  0 siblings, 1 reply; 2+ messages in thread
From: Joe Doss @ 2019-02-04 17:01 UTC (permalink / raw)
  To: WireGuard mailing list

Hi All,

We have been seeing some issues where DKMS is no longer upgrading 
cleanly on Fedora. This is due to the older version's DKMS conf file 
getting remove prematurely and you end up with this error `Error! Could 
not locate dkms.conf file.` when running any dkms commands.

I have a working RPM that does not cause this error with my testing on 
Fedora 29 and CentOS 7, so I have pushed it up to Copr 
(https://copr.fedoraproject.org/coprs/jdoss/wireguard/build/854203/). I 
_think_ this should fix things moving forward, but this issue has been 
hard to reproduce, so I am starting this thread to gather feedback if it 
doesn't fix the problem.

Please upgrade to wireguard-dkms-0.0.20190123-2 to give this a try. Once 
Jason releases the next snapshot, we can see if users running this 
version break on the upgrade or not. Please note that this new RPM won't 
fix your WireGuard DKMS install if it is already in a broken state. You 
will need to totally remove the older wireguard-dkms RPM and install 
this new one.

The gist of the underlying issue is this is a DKMS problem that is not 
very well documented. 
https://github.com/dell/dkms/issues/25#issuecomment-360275619 is the GH 
Issue that I followed when trying to track this problem down. Using 
%posttrans vs %post in the RPM feels hacky and not the best solution, 
but it should do for now. From what I can tell ZFS on Linux DKMS RPM had 
similar problems and they solved with with some bash 
(https://github.com/zfsonlinux/zfs/pull/8216). I am hoping this abuse of 
%posttrans limps us along until Linux 5.0.

Please leave feedback on this new version in this thread.

Thanks,
Joe



-- 
Joe Doss
joe@solidadmin.com
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Fedora DKMS Issues
  2019-02-04 17:01 Fedora DKMS Issues Joe Doss
@ 2019-02-04 18:09 ` Joe Doss
  0 siblings, 0 replies; 2+ messages in thread
From: Joe Doss @ 2019-02-04 18:09 UTC (permalink / raw)
  To: wireguard

On 2/4/19 11:01 AM, Joe Doss wrote:
> I have a working RPM that does not cause this error with my testing on 
> Fedora 29 and CentOS 7, so I have pushed it up to Copr 
> (https://copr.fedoraproject.org/coprs/jdoss/wireguard/build/854203/). I 

It looks like Copr is having a case of the Mondays and not building 
anything other than pc64le packages right now. Here is a testing RPM I 
made last week that can be installed manually for anyone itching to test 
things out.

https://copr-be.cloud.fedoraproject.org/results/jdoss/wireguard-testing/fedora-29-x86_64/00852015-wireguard-dkms/wireguard-dkms-0.0.20190123-2.fc29.noarch.rpm

Joe




-- 
Joe Doss
joe@solidadmin.com
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, back to index

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-02-04 17:01 Fedora DKMS Issues Joe Doss
2019-02-04 18:09 ` Joe Doss

WireGuard Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/wireguard/0 wireguard/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 wireguard wireguard/ https://lore.kernel.org/wireguard \
		wireguard@lists.zx2c4.com zx2c4-wireguard@archiver.kernel.org
	public-inbox-index wireguard


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/com.zx2c4.lists.wireguard


AGPL code for this site: git clone https://public-inbox.org/ public-inbox