From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: tzdata-2022a_2 fails to install
Date: Sun, 31 Jul 2022 10:19:01 +0200 [thread overview]
Message-ID: <20220731081901.L_gX4zMoG2mm-Ecbstax-Gawf24bxqkNX4kcW22xCe0@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38363@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1625 bytes --]
New comment by sgn on void-packages repository
https://github.com/void-linux/void-packages/issues/38363#issuecomment-1200375592
Comment:
> Mine fails first like this:
>
> (For those reading, `xi` is from the `xtools` package and essentially an `xbps-install -S` shortcut.)
>
> ```
> ❯ xi -y tzdata
> <...>
> tzdata update 2022a_1 2022a_2 -
> <...>
> tzdata-2022a_2: unpacking ...
> tzdata-2022a_2: removed obsolete entry: ./usr/share/zoneinfo/right/US
> ERROR: tzdata-2022a_2: [unpack] failed to extract file `./usr/share/zoneinfo/right': Directory not empty
> ERROR: tzdata-2022a_2: [unpack] failed to extract files: Directory not empty
> ERROR: tzdata-2022a_2: [unpack] failed to unpack files from archive: Directory not empty
> ❯ ls -lR /usr/share/zoneinfo/{right,posix}
> /usr/share/zoneinfo/posix:
> total 4
> drwxr-xr-x 2 root root 4096 Jul 30 17:08 Canada
>
> /usr/share/zoneinfo/posix/Canada:
> total 4
> -rw-r--r-- 1 root root 994 May 3 2018 East-Saskatchewan
>
> /usr/share/zoneinfo/right:
> total 4
> drwxr-xr-x 2 root root 4096 Jul 30 17:08 Canada
>
> /usr/share/zoneinfo/right/Canada:
> total 4
> -rw-r--r-- 1 root root 1534 May 3 2018 East-Saskatchewan
> ```
This timezone is not existed in tzdata. It was removed from tzdata in 2017c. Not sure why it's still there.
>
> And if I run `xi -y tzdata` again I get roughly the same logs as everybody upthread.
>
> If I try upgrading `tzdata` on a brand new `ROOTFS` (`void-x86_64-ROOTFS-20210930.tar.xz`, which comes with `tzdata-2022a_1`) the upgrade works without fault.
next prev parent reply other threads:[~2022-07-31 8:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-30 0:55 [ISSUE] " abenson
2022-07-30 0:56 ` abenson
2022-07-30 1:04 ` abenson
2022-07-30 1:54 ` sgn
2022-07-30 9:53 ` dezifit
2022-07-31 0:12 ` Goorzhel
2022-07-31 0:25 ` Goorzhel
2022-07-31 8:09 ` sgn
2022-07-31 8:19 ` sgn [this message]
2022-07-31 9:56 ` rafeyu
2022-07-31 12:15 ` sgn
2022-07-31 15:48 ` Goorzhel
2022-07-31 15:49 ` Goorzhel
2022-07-31 16:12 ` sgn
2022-07-31 16:13 ` Goorzhel
2022-08-01 1:15 ` sgn
2022-08-01 1:21 ` [ISSUE] [CLOSED] " sgn
2022-11-27 14:21 ` beginner3456789
2022-11-27 14:36 ` beginner3456789
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=20220731081901.L_gX4zMoG2mm-Ecbstax-Gawf24bxqkNX4kcW22xCe0@z \
--to=sgn@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).