Github messages for voidlinux
 help / color / mirror / Atom feed
From: beginner3456789 <beginner3456789@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: tz-data won't update on armv6 armv7
Date: Sun, 04 Dec 2022 17:41:38 +0100	[thread overview]
Message-ID: <20221204164138.sA1FhQ9tDZQmKVLcmXhWz5zf_OO0FLj1BOocqMDifB8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40357@inbox.vuxu.org>

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

New comment by beginner3456789 on void-packages repository

https://github.com/void-linux/void-packages/issues/40357#issuecomment-1336438040

Comment:
Thanks for the explanation Duncaen. So I have been looking into the files.plist info since that is probably where the update is halted. I found an old xbps file from my saved /var/cache/xbps backup:

    tzdata-2017c_1.noarch.xbps

This doesn't have the East-Saskatchewan entries at all and they are not listed in the files.plist. Maybe that is where the tracking was dropped. I haven't yet found an older tzdata xbps except might have one on an older machine that hasn't been started for a couple of years.

I wonder if the East-Saskatchewan could be added to the files.plist and then removed in the script? Otherwise this looks like it might be one of those "won't fix" problems.

EDIT: This is strange. I found the tzdata-2018e_1.noarch.xbps dated 3 May 2018 and there is no entry anywhere for East-Saskatchewan yet my raspberry pi still has the East-Saskatchewan files dated 3 May 2018.


  parent reply	other threads:[~2022-12-04 16:41 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-06 13:33 [ISSUE] " beginner3456789
2022-11-06 14:23 ` beginner3456789
2022-11-06 22:16 ` Duncaen
2022-11-07  1:54 ` beginner3456789
2022-11-10 11:02 ` superiums
2022-11-12 21:39 ` paper42
2022-11-14  0:48 ` beginner3456789
2022-11-25 12:39 ` dataCobra
2022-11-27 14:22 ` beginner3456789
2022-11-27 14:26 ` beginner3456789
2022-11-27 14:31 ` beginner3456789
2022-11-27 14:41 ` beginner3456789
2022-11-27 14:45 ` beginner3456789
2022-11-27 14:57 ` beginner3456789
2022-12-03  0:59 ` beginner3456789
2022-12-03  1:10 ` beginner3456789
2022-12-03  2:40 ` sgn
2022-12-03 19:32 ` beginner3456789
2022-12-03 19:51 ` Duncaen
2022-12-04 14:14 ` beginner3456789
2022-12-04 14:29 ` Duncaen
2022-12-04 14:30 ` Duncaen
2022-12-04 14:31 ` Duncaen
2022-12-04 14:32 ` Duncaen
2022-12-04 14:33 ` Duncaen
2022-12-04 14:34 ` Duncaen
2022-12-04 15:21 ` beginner3456789
2022-12-04 16:41 ` beginner3456789 [this message]
2023-09-16 23:41 ` 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=20221204164138.sA1FhQ9tDZQmKVLcmXhWz5zf_OO0FLj1BOocqMDifB8@z \
    --to=beginner3456789@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).