Github messages for voidlinux
 help / color / mirror / Atom feed
From: drichline <drichline@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: ZFS DKMS build fails on freshly installed system
Date: Fri, 30 Sep 2022 16:02:45 +0200	[thread overview]
Message-ID: <20220930140245.GWFs8IIPJXIlF0BZpB8hHyj9r-QBESt0NXtVVXw0kno@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39539@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1012 bytes --]

New comment by drichline on void-packages repository

https://github.com/void-linux/void-packages/issues/39539#issuecomment-1263617453

Comment:
> Looks like you are missing the `linux5.19-headers` package, which should have been installed through the `linux` meta package.

Thanks, but it was already installed

> I recommend you run `xbps-pkgdb -a` to confirm that everything on your system is as expected.

Thanks! Even though it's a fresh install, it returned:

```
ERROR: linux5.19: /boot/config-5.19.10_1 mtime mismatch (current: 1664005020, stored 1664005021)
ERROR: linux5.19: /boot/vmlinuz-5.19.10_1 mtime mismatch (current: 1664005020, stored 1664005021)
ERROR: linux5.19: files check FAILED.

```
Reinstalling `linux` didn't change anything, and DKMS still fails with the same error; do you have any suggestions on how to proceed? I'm just confused because this error doesn't seem widespread, but I've encountered it on two brand-new Void installations. Thanks so much for the help 💜

  parent reply	other threads:[~2022-09-30 14:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-30  9:36 [ISSUE] " drichline
2022-09-30 13:14 ` Duncaen
2022-09-30 13:14 ` Duncaen
2022-09-30 13:31 ` ahesford
2022-09-30 14:02 ` drichline
2022-09-30 14:02 ` drichline [this message]
2022-09-30 14:10 ` ahesford
2022-09-30 15:33 ` drichline
2022-09-30 15:33 ` [ISSUE] [CLOSED] " drichline

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=20220930140245.GWFs8IIPJXIlF0BZpB8hHyj9r-QBESt0NXtVVXw0kno@z \
    --to=drichline@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /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).