Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#77555 - possible issue with mirror.checkdomain.de

Attached to Project: Arch Linux
Opened by Evy Bongers (evybongers) - Friday, 17 February 2023, 14:21 GMT
Last edited by Anton Hvornum (Torxed) - Saturday, 04 March 2023, 16:16 GMT
Task Type Bug Report
Category Mirrors
Status Closed
Assigned To Florian Pritz (bluewind)
Johannes Löthberg (demize)
Anton Hvornum (Torxed)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

For a while now, I get an error on one specific mirror. I'm not exactly sure if this is an issue with reflector or an error with the mirror.
The source code documents using the community database for rating mirrors:

> Rate mirrors by timing the download of the community repo's database from
> each one. Keyword arguments are passed through to rate_rsync and rate_http.

In particular, it uses a hardcoded subpath for locating the db:

> DB_SUBPATH = 'community/os/x86_64/community.db'

When rating this particular mirror, a 403 status is returned, as the mirror does not host a community.db file. Upon inspection, I found that the mirror only hosts a tarball: community.db.tar.gz. The same is true for the core, extra, multilib and *-staging and *-testing databases.

I haven't been able to find documentation on what files should be present on a mirror (I'm assuming the file is skipped during sync or deleted afterwards), nor have I been able to find where/how to report issues with mirrors. That's why I'm filing this request here.

Is this an issue with the mirror? If so, how/where should I report it?

Additional info:
* package version(s): reflector 2021.11-5
* mirror: https://mirror.checkdomain.de/archlinux/

Steps to reproduce:
Run reflector with the following options: reflector --protocol https --country Germany --latest 20 --fastest 5 --sort age
This task depends upon

Closed by  Anton Hvornum (Torxed)
Saturday, 04 March 2023, 16:16 GMT
Reason for closing:  No response
Additional comments about closing:  Contact mail bounces.
Comment by Toolybird (Toolybird) - Saturday, 18 February 2023, 01:11 GMT
I'm not sure either...but it does possibly seem like an issue with that mirror...so I'd say you're almost in the right place [1].

[1] https://wiki.archlinux.org/title/Mirrors#Misbehaving_mirrors
Comment by Anton Hvornum (Torxed) - Saturday, 04 March 2023, 15:48 GMT
I've marked the mirror as inactive for now while we give the mirror admin some time to respond.
They've been notified about this issue and we're awaiting response.
Comment by Anton Hvornum (Torxed) - Saturday, 04 March 2023, 16:16 GMT
Mail to admin bounces. And no available workaround via whois lookups.
Therefore I'll keep this mirror marked as inactive and non-public.

Loading...