From: paper42 <paper42@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] dash update gets installed sooner than glibc which breaks updates from 20221001 images
Date: Sun, 22 Jan 2023 14:03:56 +0100 [thread overview]
Message-ID: <20230122130356.F_hYwdtKT919n3Z-eE8xO7alOBbB8eLlkx1_ICQf4Bg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41799@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1081 bytes --]
Closed issue by chloris-pale-green on void-packages repository
https://github.com/void-linux/void-packages/issues/41799
Description:
I hope I am posting this in the right place. I've tried to set up a fresh install of Void on Raspberry Pi 4 (8 GB RAM, 64 GB MMC), but both the image method and the rootfs method resulted in the same issue: the installation was unable to upgrade.
When performing the first upgrade using `xbps-install -Su`, the following shows up (had to type this to my main PC, might contain some errors):
```text
diffutils-3.8_1: updating to 3.9_1 ...
/bin/sh: /usr/lib64/libc.so.6: version 'GLIBC_2.33' not found (required by /bin/sh)
/bin/sh: /usr/lib64/libc.so.6: version 'GLIBC_2.34' not found (required by /bin/sh)
```
I think it has nothing to do with `diffutils`, since very similar error pops up whenever I try to run `/bin/sh` or `dash` afterwards. The system did not show any graphic output after rebooting either (suggesting a broken shell?).
Is it possible that the image and tarball have to be rebuilt with correct Glibc versions?
next prev parent reply other threads:[~2023-01-22 13:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-22 13:02 [ISSUE] Glibc version issue on `rpi-aarch64` 20221001 image chloris-pale-green
2023-01-22 13:03 ` dash update gets installed sooner than glibc which breaks updates from 20221001 images paper42
2023-01-22 13:03 ` paper42 [this message]
2023-01-22 14:15 ` chloris-pale-green
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=20230122130356.F_hYwdtKT919n3Z-eE8xO7alOBbB8eLlkx1_ICQf4Bg@z \
--to=paper42@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).