Github messages for voidlinux
 help / color / mirror / Atom feed
From: tsjk <tsjk@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Raspberry PI Updates
Date: Thu, 11 May 2023 17:26:51 +0200	[thread overview]
Message-ID: <20230511152651.F07fdiDwZebgkp-3TQqDXguBm84VJO8OG2mWZAAI7-I@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43600@inbox.vuxu.org>

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

New comment by tsjk on void-packages repository

https://github.com/void-linux/void-packages/pull/43600#issuecomment-1543767511

Comment:
dkms fails instantly during the upgrade of the rpi-kernel package. :(

```
rpi-kernel-6.1.27_1: configuring ...
Executing post-install kernel hook: 10-dkms ...
make: Entering directory '/usr/src/rpi-kernel-headers-6.1.27_1'
  SYNC    include/config/auto.conf.cmd
  HOSTCC  scripts/basic/fixdep
  HOSTCC  scripts/kconfig/conf.o
  HOSTCC  scripts/kconfig/confdata.o
  HOSTCC  scripts/kconfig/expr.o
  HOSTCC  scripts/kconfig/lexer.lex.o
  HOSTCC  scripts/kconfig/menu.o
  HOSTCC  scripts/kconfig/parser.tab.o
  HOSTCC  scripts/kconfig/preprocess.o
  HOSTCC  scripts/kconfig/symbol.o
  HOSTCC  scripts/kconfig/util.o
  HOSTLD  scripts/kconfig/conf
crypto/Kconfig:1399: can't open file "arch/arm64/crypto/Kconfig"
make[2]: *** [scripts/kconfig/Makefile:77: syncconfig] Error 1
make[1]: *** [Makefile:704: syncconfig] Error 2
make: *** [Makefile:805: include/config/auto.conf.cmd] Error 2
make: *** [include/config/auto.conf.cmd] Deleting file 'include/generated/rustc_cfg'
make: *** [include/config/auto.conf.cmd] Deleting file 'include/generated/autoconf.h'
make: Leaving directory '/usr/src/rpi-kernel-headers-6.1.27_1'
```

  parent reply	other threads:[~2023-05-11 15:26 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-24 20:35 [PR PATCH] " kenrap
2023-04-24 21:22 ` classabbyamp
2023-04-24 23:21 ` [PR PATCH] [Updated] " kenrap
2023-04-24 23:24 ` kenrap
2023-04-30 22:00 ` kenrap
2023-04-30 22:23 ` classabbyamp
2023-05-09  7:42 ` tsjk
2023-05-10 14:18 ` leahneukirchen
2023-05-10 14:20 ` classabbyamp
2023-05-10 17:09 ` tsjk
2023-05-10 17:57 ` classabbyamp
2023-05-10 18:44 ` [PR PATCH] [Updated] " kenrap
2023-05-10 18:48 ` kenrap
2023-05-10 19:18 ` classabbyamp
2023-05-10 19:24 ` classabbyamp
2023-05-10 19:26 ` classabbyamp
2023-05-10 19:30 ` tsjk
2023-05-10 19:33 ` kenrap
2023-05-10 19:40 ` tsjk
2023-05-10 19:44 ` tsjk
2023-05-10 19:45 ` tsjk
2023-05-10 20:02 ` [PR PATCH] [Updated] " kenrap
2023-05-10 20:12 ` classabbyamp
2023-05-11 10:27 ` tsjk
2023-05-11 10:28 ` tsjk
2023-05-11 10:48 ` tsjk
2023-05-11 13:28 ` tsjk
2023-05-11 13:37 ` tsjk
2023-05-11 13:41 ` tsjk
2023-05-11 14:51 ` classabbyamp
2023-05-11 14:51 ` classabbyamp
2023-05-11 15:02 ` tsjk
2023-05-11 15:10 ` classabbyamp
2023-05-11 15:13 ` classabbyamp
2023-05-11 15:15 ` tsjk
2023-05-11 15:16 ` tsjk
2023-05-11 15:21 ` tsjk
2023-05-11 15:25 ` tsjk
2023-05-11 15:26 ` tsjk
2023-05-11 15:26 ` tsjk [this message]
2023-05-11 15:29 ` tsjk
2023-06-13 15:07 ` ahesford
2023-06-13 17:19 ` lilmike
2023-06-25  8:41 ` [PR PATCH] [Updated] " classabbyamp
2023-06-25  9:19 ` classabbyamp
2023-07-30 21:25 ` r-ricci
2023-08-03 19:09 ` tsjk
2023-08-03 19:39 ` classabbyamp
2023-09-17 21:07 ` moabeat-berlin
2023-09-17 21:17 ` moabeat-berlin
2023-09-17 21:18 ` moabeat-berlin
2023-09-19 11:16 ` leahneukirchen
2023-09-19 16:13 ` moabeat-berlin
2023-09-19 16:22 ` leahneukirchen
2023-09-19 18:22 ` tsjk
2023-09-19 18:26 ` classabbyamp
2023-09-20 11:34 ` classabbyamp
2023-09-20 11:34 ` classabbyamp
2023-09-20 11:36 ` [PR PATCH] [Closed]: " classabbyamp

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=20230511152651.F07fdiDwZebgkp-3TQqDXguBm84VJO8OG2mWZAAI7-I@z \
    --to=tsjk@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).