[project] software.opensuse.org and download.opensuse.org are miserable re: MC and pegging CPU waiting to connect and waiting to load
https://software.opensuse.org/download/package?package=mc&project=openSU... clearly lists mc 4.8.26 availability @ https://download.opensuse.org/repositories/openSUSE:/Factory/standard/x86_64... which apparently doesn't exist, as also not https://download.opensuse.org/repositories/openSUSE:/Factory/standard/
If I try to fetch it, it redirects to https://download.opensuse.org/tumbleweed/repo/oss/x86_64/mc-4.8.25-1.4.x86_6... which is very much not what I'm interested in.
All download.opensuse.org, as previously reported, take forever to load when trying to check in a web browser: https://progress.opensuse.org/issues/69736 https://progress.opensuse.org/issues/62255
mc 4.8.26 was officially released more than 3 months ago.
On Sa, Mär 27, 2021 at 02:24, Felix Miata mrmazda@earthlink.net wrote:
All download.opensuse.org, as previously reported, take forever to load when trying to check in a web browser: https://progress.opensuse.org/issues/69736 https://progress.opensuse.org/issues/62255
I was gonna have the css load from static so we can use the same cache as the rest of the websites, maybe that will help some https://progress.opensuse.org/issues/90447 We have been using html printed version of the file index since at least 2018 (which you can check with web archive), so I'm not sure why that popped up recently? I can adjust the theme so it works with plaintext listing, though in case of download.opensuse.org you will never see the listing for Leap 15.2 x86_64 repos be 2.9M like the mirrors, because it does contain more info per line. The best case scenario will end up being maybe 20% difference at best, though from my quick look at the lines it may not end up being even 10% for larger pages.
The current gwdg.de mirror listing line ``` <a href="0ad-0.0.23b-lp152.1.2.x86_64.rpm">0ad-0.0.23b-lp152.1.2.x86_64.rpm</a> 16-May-2020 21:10 3435288 ```
gwdg.de if it was html ``` <tr><td><a href="0ad-0.0.23b-lp152.1.2.x86_64.rpm">0ad-0.0.23b-lp152.1.2.x86_64.rpm</a></td><td align="right">16-May-2020 21:10 </td><td align="right">3435288 </td></tr> ```
The current download.o.o listing line: ``` <tr><td valign="top"><a href="0ad-0.0.23b-lp152.1.2.x86_64.rpm"><img src="/theme/icons/package.svg" alt="[ ]" width="16" height="16" /></a></td><td><a href="0ad-0.0.23b-lp152.1.2.x86_64.rpm">0ad-0.0.23b-lp152.1.2.x86_64.rpm</a></td><td align="right">16-May-2020 21:10 </td><td align="right">3.3M </td><td><a href="0ad-0.0.23b-lp152.1.2.x86_64.rpm.mirrorlist">Details</a></td></tr> ```
download.o.o if it was plaintext ``` <a href="0ad-0.0.23b-lp152.1.2.x86_64.rpm"><img src="/theme/icons/package.svg" alt="[ ]" width="16" height="16" /></a> <a href="0ad-0.0.23b-lp152.1.2.x86_64.rpm">0ad-0.0.23b-lp152.1.2.x86_64.rpm</a> 16-May-2020 21:10 3.3M <a href="0ad-0.0.23b-lp152.1.2.x86_64.rpm.mirrorlist">Details</a> ```
The difference in length would be minimal, mainly because all the extra spaces, the best way to actually have the lines be shorter would be to remove all of the extra markup from html ``` <tr><td><a href="0ad-0.0.23b-lp152.1.2.x86_64.rpm"><img src="/theme/icons/package.svg" alt="[ ]"/> 0ad-0.0.23b-lp152.1.2.x86_64.rpm</a></td><td>16-May-2020 21:10</td><td>3.3M</td><td><a href="0ad-0.0.23b-lp152.1.2.x86_64.rpm.mirrorlist">Details</a></td></tr> ```
Which would retain all the features and would beat plaintext in length every time: though we don't have that amount of control, because it's not provided by the autoindex apache2 module. If somebody wants to contribute that, be my guest (you could also fix https://github.com/openSUSE/download-o-o/issues/1 while you are at it)
LCP [Sasi] https://lcp.world
Felix Miata wrote:
https://software.opensuse.org/download/package?package=mc&project=openSU... clearly lists mc 4.8.26 availability @ https://download.opensuse.org/repositories/openSUSE:/Factory/standard/x86_64... which apparently doesn't exist, as also not https://download.opensuse.org/repositories/openSUSE:/Factory/standard/
If I try to fetch it, it redirects to https://download.opensuse.org/tumbleweed/repo/oss/x86_64/mc-4.8.25-1.4.x86_6... which is very much not what I'm interested in.
Felix, this list is just about the poorest place to report such operational issues to.
Per Jessen composed on 2021-03-27 19:58 (UTC+0100):
Felix Miata wrote:
https://software.opensuse.org/download/package?package=mc&project=openSU... clearly lists mc 4.8.26 availability @ https://download.opensuse.org/repositories/openSUSE:/Factory/standard/x86_64... which apparently doesn't exist, as also not https://download.opensuse.org/repositories/openSUSE:/Factory/standard/
If I try to fetch it, it redirects to https://download.opensuse.org/tumbleweed/repo/oss/x86_64/mc-4.8.25-1.4.x86_6... which is very much not what I'm interested in.
Felix, this list is just about the poorest place to report such operational issues to.
It's not entirely clear where to look to discover good or best place. I don't routinely get a sense I did the right thing when I bring such things up to heroes@, a list of apparently limited participation. admin is just a redirector to one of too many bug trackers. www is inactive. web doesn't exist.
Maybe it's just this language bothers me: "Discussion list of the openSUSE infrastructure admins"
To me it reads as not for mere users to report issues, instead being limited to those in position to actually do anything about and/or working on issues.
Felix Miata wrote:
Per Jessen composed on 2021-03-27 19:58 (UTC+0100):
Felix Miata wrote:
https://software.opensuse.org/download/package?package=mc&project=openSU... clearly lists mc 4.8.26 availability @ https://download.opensuse.org/repositories/openSUSE:/Factory/standard/x86_64... which apparently doesn't exist, as also not
https://download.opensuse.org/repositories/openSUSE:/Factory/standard/
If I try to fetch it, it redirects to https://download.opensuse.org/tumbleweed/repo/oss/x86_64/mc-4.8.25-1.4.x86_6... which is very much not what I'm interested in.
Felix, this list is just about the poorest place to report such operational issues to.
It's not entirely clear where to look to discover good or best place.
Yeah, I agree, that is not always easy.
I don't routinely get a sense I did the right thing when I bring such things up to heroes@, a list of apparently limited participation.
The Heroes list is primarily for the Heroes team, and not used an awful lot.
admin is just a redirector to one of too many bug trackers.
Well, it is _the_ place to report issues with the openSUSE infrastructure. In this specific case, I would likely have brought up the issue on a users list/forum first, and then eventually reported it to admin@o.o
-
Felix Miata -
Per Jessen -
Sasi Olin