From: kwshi <kwshi@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: `tzdata-2022c_1` fails to install on 20210930 rootfs
Date: Tue, 30 Aug 2022 10:10:03 +0200 [thread overview]
Message-ID: <20220830081003.BU1FV61VxrMurgMDX2rfJQQmoFv70Rk6SMRybMJfJ_0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38977@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 923 bytes --]
New comment by kwshi on void-packages repository
https://github.com/void-linux/void-packages/issues/38977#issuecomment-1231310557
Comment:
More interesting updates! It might well be that this is coming from https://github.com/containers/fuse-overlayfs/issues/368, which, if true, should be resolved pretty soon since a PR fixing it (fuse-overlayfs#369) has been merged already. Indeed, my current version of podman, 4.2.0, still reproduces the issue mentioned in that thread, and the inexplicable "No such file or directory" errors associated with "copying from a deleted file" sound largely in line with the factors at play here (updating tzdata needs to delete and rewrite a bunch of tzinfo files; it's likely somewhere in there this bug is getting triggered).
Anyways, fingers crossed podman updates its fuse-overlayfs dependency soon, and this'll be fixed. In the meantime, I'll hang tight and do nothing! :D
next prev parent reply other threads:[~2022-08-30 8:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 6:07 [ISSUE] " kwshi
2022-08-30 6:34 ` sgn
2022-08-30 6:36 ` sgn
2022-08-30 6:41 ` sgn
2022-08-30 7:29 ` [ISSUE] [CLOSED] " kwshi
2022-08-30 7:29 ` kwshi
2022-08-30 7:33 ` kwshi
2022-08-30 8:10 ` kwshi [this message]
2022-10-24 8:57 ` superiums
2022-10-24 9:02 ` superiums
2022-10-24 9:23 ` sgn
2022-11-08 2:46 ` superiums
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=20220830081003.BU1FV61VxrMurgMDX2rfJQQmoFv70Rk6SMRybMJfJ_0@z \
--to=kwshi@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).