From: rdslw <rdslw@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: linux5.15 package install scripts fails if /boot is mounted on vfat fstype
Date: Wed, 01 Nov 2023 19:38:08 +0100 [thread overview]
Message-ID: <20231101183808.8jB3j_AETUXHzaRd7mb4xQp5_XxvW73H6abeVj3CFRA@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: 952 bytes --]
New comment by rdslw on void-packages repository
https://github.com/void-linux/void-packages/issues/47011#issuecomment-1789462848
Comment:
@Duncaen sure, I can. Here I was using 'xbps-install -Su' command, would you like to just strace it, and try to find calls around error/post log?
Currently I'm only able to downgrade linux kernel package, as I have the newest one installed today. Can you guide me how to do it, as simple ```xbps-install --force --debug /var/cache/xbps/linux5.15-5.15.131_1.x86_64-musl.xbps``` results in error: _Package '/var/cache/xbps/linux5.15-5.15.131_1.x86_64-musl.xbps' not found in repository pool_
P.S. My guess about chmod/chown is because after each command/error, the offending file from error message *is* unpacked to /boot, but the whole command aborts while the next (exactly the same xbps-install -Su) invocation moves forward and fails on another file, then third call succeeds. I might be wrong though.
next prev parent reply other threads:[~2023-11-01 18:38 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 [this message]
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 ` [ISSUE] [CLOSED] " ahesford
2023-12-03 1:01 ` ahesford
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=20231101183808.8jB3j_AETUXHzaRd7mb4xQp5_XxvW73H6abeVj3CFRA@z \
--to=rdslw@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).