Weird 404 error with package repository

Rocky Linux General
1

Hi,

I’m running my own package repository for some desktop-related packages for Rocky Linux 8 that aren’t provided by the usual suspects of third party repositories like EPEL or RPMFusion:

https://www.microlinux.fr/pub/rockylinux/8/x86_64/packages/

Here’s the corresponding repository configuration file on one of the desktop clients:

# /etc/yum.repos.d/microlinux.repo

[microlinux]
name=Microlinux
baseurl=https://www.microlinux.fr/pub/rockylinux/$releasever/$basearch
enabled=1
priority=10
gpgcheck=1
gpgkey=https://www.microlinux.fr/pub/rockylinux/RPM-GPG-KEY

Now here’s something very weird:

The repo seems to work perfectly for pretty much any package. I can do a dnf install asunder or a dnf install normalize, and packages get downloaded and installed.

Packages related to owncloud-client don’t get installed, because DNF spews back a 404 error:

[MIRROR] owncloud-client-2.10.1-1.el8.x86_64.rpm: Status code: 404 for https://www.microlinux.fr/pub/rockylinux/8/x86_64/packages/owncloud-client-2.10.1-1.el8.x86_64.rpm (IP: 51.159.21.129)
[MIRROR] owncloud-client-libs-2.10.1-1.el8.x86_64.rpm: Status code: 404 for https://www.microlinux.fr/pub/rockylinux/8/x86_64/packages/owncloud-client-libs-2.10.1-1.el8.x86_64.rpm (IP: 51.159.21.129)
[MIRROR] owncloud-client-2.10.1-1.el8.x86_64.rpm: Status code: 404 for https://www.microlinux.fr/pub/rockylinux/8/x86_64/packages/owncloud-client-2.10.1-1.el8.x86_64.rpm (IP: 51.159.21.129)
[MIRROR] owncloud-client-libs-2.10.1-1.el8.x86_64.rpm: Status code: 404 for https://www.microlinux.fr/pub/rockylinux/8/x86_64/packages/owncloud-client-libs-2.10.1-1.el8.x86_64.rpm (IP: 51.159.21.129)
[FAILED] owncloud-client-libs-2.10.1-1.el8.x86_64.rpm: No more mirrors to try - All mirrors were already tried without success

Even more weirdly, I can open this repository in a console-based web browser like links and download and install the RPM packages manually. No 404 error here.

Any idea what’s going on here ? I’m puzzled.

2

Did you update the metadata in that repo the last time you dropped packages in it (eg createrepo --update)?

The 404 seems to be because those packages aren’t actually there. For example, I see owncloud-client-2.10.1-2.el8.x86_64.rpm but not owncloud-client-2.10.1-1.el8.x86_64.rpm on Index of /pub/rockylinux/8/x86_64/packages

1 Like