Project

General

Profile

Bug #3192

Servers - Bug #3178: [parabola-repolint]: failed to detect registered, but missing package file

[zstd] zstd packages for armv7h not in repos or any mirrors

ryry - about 2 years ago - . Updated about 2 years ago.

Status:
in progress
Priority:
bug
Assignee:
-
% Done:

0%

Description

When running the update on a armv7h device, it errors with 404 and the package fails to be downloaded, causing the update to error and fail. After further inspection of https://repo.parabola.nu/core/os/armv7h/zstd-1.5.2-2-armv7h.pkg.tar.xz and the file tree, the package seems to not be in the repos as it is for the other architectures. Looking at other mirrors in sync, it is not there either. Not sure if its intentional or not.

Many Thanks
ryry

History

#1

Updated by bill-auger about 2 years ago

  • Parent task set to #3178
  • Status changed from unconfirmed to confirmed
#2

Updated by bill-auger about 2 years ago

  • Status changed from confirmed to in progress
#3

Updated by GNUtoo about 2 years ago

Hi,

There is also curl and dosfstools missing.

I've looked a bit at this and compared some packages.

Between bzip2 and zstd from archlinux arm armv7h the .BUILDINFO is different. We have something like that:

-format = 1
+format = 2
+startdir = /startdir
+buildtool = makepkg
+buildtoolver = 6.0.1
+options = !lto

Between curl from arch linux x86_64 and curl from archlinux arm armv7h the format is the same but we still have differences:

-buildtool = devtools
+buildtool = makepkg
-buildtoolver = 20220126-1-any
+buildtoolver = 6.0.1
-buildenv = !distcc
+buildenv = distcc
+options = !upx
-options = lto
+options = !lto

#4

Updated by GNUtoo about 2 years ago

While we have a failing pacman-keyring (due to a bug in pacman package or pacman1):

[gnutoo@winston ~]$ systemctl --failed
[...]
● pacman-keyring.service     loaded failed failed Refresh pacman keyring                      
[...]

When downloading the package by hand, verifying the signature works fine:

[gnutoo@winston ~]$ pacman-key --verify curl-7.81.0-2-armv7h.pkg.tar.xz.sig
==> Checking curl-7.81.0-2-armv7h.pkg.tar.xz.sig... (detached)
gpg: Signature made Sun 30 Jan 2022 04:08:02 PM GMT
gpg:                using RSA key 68B3537F39A313B3E574D06777193F152BDBE6A6
gpg: Note: trustdb not writable
gpg: Good signature from "Arch Linux ARM Build System <builder@archlinuxarm.org>" [full]
[gnutoo@winston ~]$

1 See bug #3193

#5

Updated by GNUtoo about 2 years ago

For quite some time we still have dosfstools that is not there on ARM:

:: Proceed with installation? [Y/n] 
:: Retrieving packages...
 dosfstools-4.2-2-armv7h.pkg.tar.xz failed to download
 Total ( 1/20)                                    6.8 MiB   679 MiB/s 00:00 [##########################################] 100%
error: failed retrieving file 'dosfstools-4.2-2-armv7h.pkg.tar.xz' from 192.168.10.1 : The requested URL returned error: 404
warning: failed to retrieve some files
error: failed to commit transaction (failed to retrieve some files)
Errors occurred, no packages were upgraded.
# pacman -sS dosfstools
core/dosfstools 4.2-2
    DOS filesystem utilities

edit1: added log

#6

Updated by GNUtoo about 2 years ago

For dosfstools I added a package in pcr for armv7h.

I've not blacklisted it since i686 and x86_64 use the one coming from arch.

So for upgrades it still tries to download dosfstools from core.

I've now removed the armv7h dosfstools from core.db (and accidentally from pcr.db so I'll re-upload the package). So we need to see if that sticks or not.

In any case we can still manually install dosfstools from pcr with pacman -S pcr/dosfstools and the upgrade will work again. Though that might not work for pacstrap unless we specify to install dosfstools manually (so that might break libremakepkg for instance).

Also available in: Atom PDF