openSUSE admin

For example use pacman to download that package => https://software.opensuse.org//download.html?project=home%3Ahawkeye116477%3Awaterfox&package=waterfox-alpha-kde. Latest available version is 68.0a2 (but pacman still see 68.0a1, because it gets informations from db file => https://download.opensuse.org/repositories/home:/hawkeye116477:/waterfox/Arch/x86_64/home_hawkeye116477_waterfox_Arch.db and that db file points to mirror which still has old version 68.0a1, then it tries to download old version, but can't, because https://download.opensuse.org hasn't that version, because it was replaced with new version 68.0a2. So in that case it's impossible to download new version or redownload old version, I must wait few days when mirror will have new version or replace server with https://downloadcontent.opensuse.org/.. instead of https://download.opensuse.org/...

When you use http://download.o.o, you are redirected to a mirror site which has the content you're after. For home repos, there are not so many mirrors. I guess a mirror could be out-of-date, maybe if the rsync isn't working properly, but we would normally notice that and not redirect you to that mirror.

Which mirror do you see the problem with? (pacman is not a mirror).

Which mirror do you see the problem with?

It's https://ftp.gwdg.de.

Yes, it it's pushed with some delay, but in the meantime unfortunately if I uninstall package, then I can't re-download old version or download new version through pacman until I change server to https://downloadcontent.opensuse.org. Anyway, I hope that will be solved soon :-)

This issue unfortunately still appears, when I release new version, then if new version isn't available yet on mirrors, then it's not possible to download older or new version through pacman (directly from site works), it tries to download old version and I got 404 from download.opensuse.org, because old version was replaced by new version on download.opensuse.org and syncing doesn't help.

I'm sorry, but I can't work out what you are trying to say.

Trying to investigate any inconsistencies after the fact is very difficult. I can look at the logs and see that repo push to gwdg is working just fine.
Perhaps you could try to provide some detailed information - which package is or is not available, where and at what time?

For your userid, I see some projects being pushed on 2020/02/02 and 2020/02/03 (times are in UTC) :

Sun Feb  2 04:15:57 2020 ftp.gwdg.de: home:/hawkeye116477:/waterfox/Debian_Unstable
Sun Feb  2 04:16:15 2020 ftp.gwdg.de: home:/hawkeye116477:/waterfox/Debian_Testing
Sun Feb  2 04:53:09 2020 ftp.gwdg.de: home:/hawkeye116477:/waterfox/xUbuntu_18.04
Mon Feb  3 13:48:40 2020 ftp.gwdg.de: home:/hawkeye116477:/waterfox/Fedora_Rawhide
Mon Feb  3 14:19:35 2020 ftp.gwdg.de: home:/hawkeye116477:/waterfox/Fedora_30
Mon Feb  3 14:31:28 2020 ftp.gwdg.de: home:/hawkeye116477:/waterfox/xUbuntu_Next
Mon Feb  3 21:10:47 2020 ftp.gwdg.de: home:/hawkeye116477:/waterfox/Debian_Testing
Mon Feb  3 21:14:15 2020 ftp.gwdg.de: home:/hawkeye116477:/waterfox/Debian_Unstable
Mon Feb  3 22:06:46 2020 ftp.gwdg.de: home:/hawkeye116477:/waterfox/Arch

In general, home repos will always be "pushed with some delay" - they have the lowest priority.

Perhaps you could try to provide some detailed information - which package is or is not available, where and at what time?

For example waterfox-current-kpe, if I type to console sudo pacman -Syy, then sudo pacman -S waterfox-current-kpe, I got this:

resolving dependencies...
looking for conflicting packages...

Packages (1) waterfox-current-kpe-2020.01-0

Total Download Size: 48,82 MiB
Total Installed Size: 189,35 MiB

:: Proceed with installation? [Y/n] y
:: Retrieving packages...
error: failed retrieving file 'waterfox-current-kpe-2020.01-0-x86_64.pkg.tar.xz' from download.opensuse.org : 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.

This is old version, which of course currently isn't available on download.opensuse.org, but still available on mirror. Same situation is always when latest version isn't on mirror. It should rather see latest version and download it from downloadcontent.opensuse.org if mirrors aren't available just like in case of for example Debian or Ubuntu repos.

we don't have such fine-grained control over our mirrors, it would mean tracking the individual status of thousands and thousands of packages.

I don't know that there is much I can do - if you can provide detailed information of a mirror being e.g. 30mins out-of-sync for repositories, I can try to contact them to set up a push job.

So you mean that's possible in case of Debian, but not in case of Arch Linux?

In case of Debian repo (on OBS), when I publish new version, then it's not available on mirror for some time since the introduction of the new version, but downloading through apt still works, it detects new version and downloads from downloadcontent.opensuse.org and that's fine. In case of Arch Linux repos unfortunately this doesn't work same when I'm introducing new version (I set https://download.opensuse.org/repositories/home:/hawkeye116477:/waterfox/Arch/$arch as server).

hawkeye116477 wrote:

we don't have such fine-grained control over our mirrors, it would mean tracking the individual status of thousands and thousands of packages.
I don't know that there is much I can do - if you can provide detailed information of a mirror being e.g. 30mins out-of-sync for repositories, I can try to contact them to set up a push job.

So you mean that's possible in case of Debian, but not in case of Arch Linux?

No, we don't treat them any differently. A home repo is a home repo whatever you are building.

In case of Debian repo (on OBS), when I publish new version, then it's not available on mirror for some time,

Quite possible.

but downloading through apt still works, it detects new version and downloads from downloadcontent.opensuse.org and that's fine.

That is probably because downloadcontent is our fallback mirror.

In case of Arch Linux repos unfortunately this doesn't work.

There is no reason it shouldn't, like I said, we don't know the difference.