From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] linux5.15 package install scripts fails if /boot is mounted on vfat fstype
Date: Sun, 03 Dec 2023 02:01:41 +0100 [thread overview]
Message-ID: <20231203010141.yrrW4W7Nv7r6v22X6W_kGo4fGlqqjGYQxTnucqoBGA0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47011@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2115 bytes --]
Closed issue by rdslw on void-packages repository
https://github.com/void-linux/void-packages/issues/47011
Description:
### Is this a new report?
Yes
### System Info
Void x86_musl
### Package(s) Affected
linux5.15-5.15.*
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
no, this is void specific bug.
### Expected behaviour
package linux5.15 is able to install even if /boot is a vfat partition, and chown/chmod commands may return errors, which are ignored by install scripts of linux5 package
### Actual behaviour
If the /boot (where /vmlinuz-XXX and config-XXX and initramfs-XXX are installed) is vfat filesystem (not the ext4/btrfs/others), installation of linux5.15 package fails, due to the inability to set ownership and permissions during xbps install.
What's funny, files ARE copied to /boot, but the install process fails with error after copy. So it is enough to run xpbs install three times in a row (without any fixes) and the third run, completes fine.
Important: this bug is old, it was not introduced recently, but probably been with us for a long time.
Error messages:
```
linux5.15-5.15.131_1: updating to 5.15.137_1 ...
linux5.15-5.15.137_1: unpacking ...
ERROR: linux5.15-5.15.137_1: [unpack] failed to extract file `./boot/vmlinuz-5.15.137_1': Operation not permitted
ERROR: linux5.15-5.15.137_1: [unpack] failed to extract files: Operation not permitted
ERROR: linux5.15-5.15.137_1: [unpack] failed to unpack files from archive: Operation not permitted
linux5.15-5.15.131_1: updating to 5.15.137_1 ...
linux5.15-5.15.137_1: unpacking ...
ERROR: linux5.15-5.15.137_1: [unpack] failed to extract file `./boot/config-5.15.137_1': Operation not permitted
ERROR: linux5.15-5.15.137_1: [unpack] failed to extract files: Operation not permitted
ERROR: linux5.15-5.15.137_1: [unpack] failed to unpack files from archive: Operation not permitted
```
### Steps to reproduce
1. use /boot on vfat partition (for examply to have shared EFI and /boot space).
2. try to upgrade (important) linux5.15 package (newer kernel)
next prev parent reply other threads:[~2023-12-03 1:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 16:01 [ISSUE] " rdslw
2023-11-01 18:19 ` Duncaen
2023-11-01 18:26 ` Duncaen
2023-11-01 18:38 ` rdslw
2023-11-01 18:43 ` classabbyamp
2023-11-01 18:59 ` rdslw
2023-11-01 19:02 ` rdslw
2023-11-01 19:09 ` Duncaen
2023-11-01 19:10 ` Duncaen
2023-11-01 19:24 ` Duncaen
2023-11-01 19:24 ` Duncaen
2023-11-01 19:25 ` classabbyamp
2023-11-01 19:25 ` Duncaen
2023-11-02 16:21 ` rdslw
2023-11-02 23:20 ` Duncaen
2023-11-02 23:20 ` Duncaen
2023-11-02 23:25 ` Duncaen
2023-11-02 23:26 ` Duncaen
2023-11-03 8:07 ` rdslw
2023-12-03 1:01 ` ahesford
2023-12-03 1:01 ` ahesford [this message]
2024-01-13 10:32 ` rdslw
2024-01-13 11:08 ` Duncaen
2024-01-13 12:02 ` rdslw
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=20231203010141.yrrW4W7Nv7r6v22X6W_kGo4fGlqqjGYQxTnucqoBGA0@z \
--to=ahesford@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).