From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: "linux6.5: configured successfully" without initramfs
Date: Sun, 10 Sep 2023 21:04:50 +0200 [thread overview]
Message-ID: <20230910190450.gz1Ei4MfPshdBHLg77koo0U5odCK81Tzyg7jxBFX5Dg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46006@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 855 bytes --]
New comment by classabbyamp on void-packages repository
https://github.com/void-linux/void-packages/issues/46006#issuecomment-1712912739
Comment:
> How can it be "configured successfully." with such a fatal error?
having a hook fail and causing an xbps operation to stop in the middle would be much worse, leading to issues with lots of half-configured packages
> You can't expect the user to meaningfully review every line of logs for every update.
it is kinda important to know what your system is doing, especially for updates. XBPS also puts important messages in the logs for things like breaking changes.
> Building DKMS module: zfs-2.1.12... FAILED!
the current release of ZFS doesn't support 6.5 and i'd suggest sticking to the `linux` or `linux-lts` metapackage when using ZFS, as those are guaranteed to be compatible with ZFS.
next prev parent reply other threads:[~2023-09-10 19:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-10 17:18 [ISSUE] " Jipok
2023-09-10 18:47 ` dkwo
2023-09-10 19:04 ` classabbyamp [this message]
2023-09-10 22:07 ` Jipok
2023-09-16 15:19 ` [ISSUE] [CLOSED] " ahesford
2023-09-16 15:19 ` ahesford
2023-09-16 16:13 ` Jipok
2023-09-16 16:21 ` ahesford
2023-09-16 16:48 ` Jipok
2023-09-16 16:56 ` classabbyamp
2023-09-16 16:56 ` ahesford
2023-09-16 17:01 ` Duncaen
2023-09-16 17:09 ` Jipok
2023-09-16 17:15 ` ahesford
2023-09-16 18:11 ` Duncaen
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=20230910190450.gz1Ei4MfPshdBHLg77koo0U5odCK81Tzyg7jxBFX5Dg@z \
--to=classabbyamp@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).