Github messages for voidlinux
 help / color / mirror / Atom feed
From: g4s8 <g4s8@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: XBPS doesn't fail kernel installation if post-install kernel hook failed
Date: Fri, 12 May 2023 11:49:26 +0200	[thread overview]
Message-ID: <20230512094926.qOLPKKHaexl87J-IgIfbJcu8ZoUufhyRtv_3gvE7O2M@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42047@inbox.vuxu.org>

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

New comment by g4s8 on void-packages repository

https://github.com/void-linux/void-packages/issues/42047#issuecomment-1545479958

Comment:
@classabbyamp @Duncaen I added `exit 1` to kernel-hook in #43852 and tested any hook fails parent hook script (with debug logs), but the problem is still here - the hook script fails but xbps successfully install or reconfigure the package:
```
Executing post-install kernel hook: 20-initramfs ...
dracut-install: ERROR: installing '/boot/volume1.key'
dracut: FAILED: /usr/lib/dracut/dracut-install -D /var/tmp/dracut.da3HNp/initramfs -a /boot/volume1.key /etc/crypttab
cp: cannot create regular file 'boot/initramfs-6.2.13_1.img': No such file or directory
dracut: Creation of boot/initramfs-6.2.13_1.img failed
DEBUG: !!! hook etc/kernel.d/post-install/20-initramfs failed
linux6.2-6.2.13_1: configured successfully.
```

  parent reply	other threads:[~2023-05-12  9:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-02 22:18 [ISSUE] " g4s8
2023-02-02 22:19 ` Duncaen
2023-05-04  1:51 ` github-actions
2023-05-12  9:49 ` g4s8 [this message]
2023-05-25 18:42 ` ahesford

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=20230512094926.qOLPKKHaexl87J-IgIfbJcu8ZoUufhyRtv_3gvE7O2M@z \
    --to=g4s8@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).