* Re: glibc pinebook pro aarch64: Invalid cross-device link
2024-01-05 7:32 [ISSUE] glibc pinebook pro aarch64: Invalid cross-device link atweiden
@ 2024-01-05 7:39 ` classabbyamp
2024-01-05 7:42 ` classabbyamp
` (5 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: classabbyamp @ 2024-01-05 7:39 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 236 bytes --]
New comment by classabbyamp on void-packages repository
https://github.com/void-linux/void-packages/issues/48071#issuecomment-1878253556
Comment:
what is your partition layout? is `/usr/lib` on a different filesystem than `/usr/bin`?
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: glibc pinebook pro aarch64: Invalid cross-device link
2024-01-05 7:32 [ISSUE] glibc pinebook pro aarch64: Invalid cross-device link atweiden
2024-01-05 7:39 ` classabbyamp
@ 2024-01-05 7:42 ` classabbyamp
2024-01-05 7:46 ` atweiden
` (4 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: classabbyamp @ 2024-01-05 7:42 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 246 bytes --]
New comment by classabbyamp on void-packages repository
https://github.com/void-linux/void-packages/issues/48071#issuecomment-1878256086
Comment:
glibc 2.36 has the same hardlink for `/usr/bin/getconf` so not sure why that would cause an issue
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: glibc pinebook pro aarch64: Invalid cross-device link
2024-01-05 7:32 [ISSUE] glibc pinebook pro aarch64: Invalid cross-device link atweiden
2024-01-05 7:39 ` classabbyamp
2024-01-05 7:42 ` classabbyamp
@ 2024-01-05 7:46 ` atweiden
2024-01-05 7:49 ` classabbyamp
` (3 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: atweiden @ 2024-01-05 7:46 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 446 bytes --]
New comment by atweiden on void-packages repository
https://github.com/void-linux/void-packages/issues/48071#issuecomment-1878259497
Comment:
Same partition, but with these bind mounts in fstab:
```
/usr /usr none bind 0 0
/usr /usr none remount,nodev 0 0
/usr/lib /usr/lib none bind 0 0
/usr/lib /usr/lib none remount,nodev,nosuid 0 0
/usr/lib32 /usr/lib32 none bind 0 0
/usr/lib32 /usr/lib32 none remount,nodev,nosuid 0 0
```
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: glibc pinebook pro aarch64: Invalid cross-device link
2024-01-05 7:32 [ISSUE] glibc pinebook pro aarch64: Invalid cross-device link atweiden
` (2 preceding siblings ...)
2024-01-05 7:46 ` atweiden
@ 2024-01-05 7:49 ` classabbyamp
2024-01-05 7:50 ` atweiden
` (2 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: classabbyamp @ 2024-01-05 7:49 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 153 bytes --]
New comment by classabbyamp on void-packages repository
https://github.com/void-linux/void-packages/issues/48071#issuecomment-1878261669
Comment:
why?
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: glibc pinebook pro aarch64: Invalid cross-device link
2024-01-05 7:32 [ISSUE] glibc pinebook pro aarch64: Invalid cross-device link atweiden
` (3 preceding siblings ...)
2024-01-05 7:49 ` classabbyamp
@ 2024-01-05 7:50 ` atweiden
2024-01-05 11:47 ` ahesford
2024-01-05 11:47 ` [ISSUE] [CLOSED] " ahesford
6 siblings, 0 replies; 8+ messages in thread
From: atweiden @ 2024-01-05 7:50 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 231 bytes --]
New comment by atweiden on void-packages repository
https://github.com/void-linux/void-packages/issues/48071#issuecomment-1878262548
Comment:
To apply different mount options without necessitating the use of separate partitions.
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: glibc pinebook pro aarch64: Invalid cross-device link
2024-01-05 7:32 [ISSUE] glibc pinebook pro aarch64: Invalid cross-device link atweiden
` (4 preceding siblings ...)
2024-01-05 7:50 ` atweiden
@ 2024-01-05 11:47 ` ahesford
2024-01-05 11:47 ` [ISSUE] [CLOSED] " ahesford
6 siblings, 0 replies; 8+ messages in thread
From: ahesford @ 2024-01-05 11:47 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 503 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/issues/48071#issuecomment-1878543192
Comment:
This may be expected behavior (it certainly isn't surprising, given your atypical mounts), or it could be an issue with the kernel, libarchive. I suggest you try manually unpacking the glibc package over the filesystem structure using both GNU tar and bsdtar to try to gain insight.
Regardless of the outcome, this is definitely not a void-packages issue.
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: [ISSUE] [CLOSED] glibc pinebook pro aarch64: Invalid cross-device link
2024-01-05 7:32 [ISSUE] glibc pinebook pro aarch64: Invalid cross-device link atweiden
` (5 preceding siblings ...)
2024-01-05 11:47 ` ahesford
@ 2024-01-05 11:47 ` ahesford
6 siblings, 0 replies; 8+ messages in thread
From: ahesford @ 2024-01-05 11:47 UTC (permalink / raw)
To: ml
[-- Attachment #1: Type: text/plain, Size: 1971 bytes --]
Closed issue by atweiden on void-packages repository
https://github.com/void-linux/void-packages/issues/48071
Description:
### Is this a new report?
Yes
### System Info
Void 6.1.9_1 aarch64 Unknown notuptodate hold rFF
### Package(s) Affected
glibc
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
_No response_
### Expected behaviour
`glibc` package upgrades succeed.
### Actual behaviour
`glibc` package upgrades fail. Third time this has happened during `glibc` upgrade on pinebook pro.
```
[*] Unpacking packages
libxcrypt-compat-4.4.36_3: unpacking ...
libxcrypt-compat-4.4.36_3: unpacked file `./usr/lib/libcrypt.so.1' (0 bytes)
glibc-2.38_2: updating to 2.38_3 ...
glibc-2.38_3: unpacking ...
glibc-2.38_3: unpacked file `./usr/lib/libthread_db.so' (0 bytes)
glibc-2.38_3: unpacked file `./usr/lib/libresolv.so' (0 bytes)
glibc-2.38_3: unpacked file `./usr/lib/libnss_hesiod.so' (0 bytes)
glibc-2.38_3: unpacked file `./usr/lib/libnss_db.so' (0 bytes)
glibc-2.38_3: unpacked file `./usr/lib/libnss_compat.so' (0 bytes)
glibc-2.38_3: unpacked file `./usr/lib/libmvec.so' (0 bytes)
glibc-2.38_3: unpacked file `./usr/lib/libc_malloc_debug.so' (0 bytes)
glibc-2.38_3: unpacked file `./usr/lib/libanl.so' (0 bytes)
glibc-2.38_3: unpacked file `./usr/lib/libBrokenLocale.so' (0 bytes)
glibc-2.38_3: unpacked file `./usr/lib/getconf/POSIX_V7_LP64_OFF64' (0 bytes)
glibc-2.38_3: unpacked file `./usr/lib/getconf/POSIX_V6_LP64_OFF64' (0 bytes)
glibc-2.38_3: unpacked file `./usr/bin/ld.so' (0 bytes)
ERROR: glibc-2.38_3: [unpack] failed to extract file `./usr/bin/getconf': Invalid cross-device link
ERROR: glibc-2.38_3: [unpack] failed to extract files: Invalid cross-device link
ERROR: glibc-2.38_3: [unpack] failed to unpack files from archive: Invalid cross-device link
Transaction failed! see above for errors.
```
### Steps to reproduce
1. Attempt upgrading glibc on Pinebook Pro
^ permalink raw reply [flat|nested] 8+ messages in thread