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

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

New issue by beginner3456789 on void-packages repository

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

Description:
### Is this a new report?

Yes

### System Info

Void 5.15.72_1 armv7l Unknown uptodate hold rFFFF

### Package(s) Affected

tz-data-2022f_2

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

unknown

### Expected behaviour

The tz-data failed and would not allow the update to continue. This happened when updating both my raspberry pi zero (armv6) and raspberry pi 2 (armv7) for the first time since almost a year ago. That happened after first updating xbps and then downloading about a hundred packages. I put the old tz-data on hold to allow the update for the rest of the packages and then tried again with the same failure as shown below. I can't find the reason with the Canada problem shown below.

### Actual behaviour

-bash-5.1# xbps-pkgdb -m unhold tzdata-2021c_1
-bash-5.1# xbps-install -Su
[*] Updating repository `https://repo-default.voidlinux.org/current/armv7l-repodata' ...

Name   Action    Version           New version            Download size
tzdata update    2021c_1           2022f_2                - 

Size required on disk:        1161KB
Space available on disk:        56GB

Do you want to continue? [Y/n] 

[*] Verifying package integrity
tzdata-2022f_2: verifying RSA signature...

[*] Collecting package files
tzdata-2022f_2: collecting files...
tzdata-2021c_1: collecting files...
ERROR: tzdata-2022f_2: directory `./usr/share/zoneinfo/posix/Canada' can not be deleted.
Transaction failed! see above for errors.
-bash-5.1# 


### Steps to reproduce

Problem happens when updating from 2021c_1 to 2022f_2 on both the raspberry pi zero and raspberry pi 2.


             reply	other threads:[~2022-11-06 13:33 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-06 13:33 beginner3456789 [this message]
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
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40357@inbox.vuxu.org \
    --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).