From: Jipok <Jipok@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: "linux6.5: configured successfully" without initramfs
Date: Sat, 16 Sep 2023 18:48:41 +0200 [thread overview]
Message-ID: <20230916164841.VTIr1ulROBkoLnVH2I0-_nDqbq53cP2RbpUmtDm7zB0@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: 782 bytes --]
New comment by Jipok on void-packages repository
https://github.com/void-linux/void-packages/issues/46006#issuecomment-1722268888
Comment:
> The issue you're reporting is that XBPS happily ignores failed post-install triggers when they fail. This is an XBPS issue and should be discussed there.
You are generalizing to a more complex problem. Which few people want to solve. And which can last for years.
Whereas the current problem, in my opinion, requires an urgent solution with some kind of hack. And if I understand correctly, the hack should be located in one of the packages. So this question is open here. Although it is related to the xbps problem you described, it has its own importance because it is the damn kernel and without it you get an unbootable machine.
next prev parent reply other threads:[~2023-09-16 16:48 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
2023-09-10 22:07 ` Jipok
2023-09-16 15:19 ` ahesford
2023-09-16 15:19 ` [ISSUE] [CLOSED] " ahesford
2023-09-16 16:13 ` Jipok
2023-09-16 16:21 ` ahesford
2023-09-16 16:48 ` Jipok [this message]
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=20230916164841.VTIr1ulROBkoLnVH2I0-_nDqbq53cP2RbpUmtDm7zB0@z \
--to=jipok@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).