From: Joe Doss <joe@solidadmin.com>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Fedora DKMS Issues
Date: Mon, 4 Feb 2019 11:01:28 -0600 [thread overview]
Message-ID: <15503e7e-cc33-294e-b166-29ad0ddabcb4@solidadmin.com> (raw)
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
next reply other threads:[~2019-02-04 17:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-04 17:01 Joe Doss [this message]
2019-02-04 18:09 ` Joe Doss
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=15503e7e-cc33-294e-b166-29ad0ddabcb4@solidadmin.com \
--to=joe@solidadmin.com \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).