Where are all of the packages, at Fedora Packages?

(Or: Is apps.fedoraproject.org broken?)

Looking for information on the python3-colorlog package earlier, I followed the Bug URL link in the RPM metadata (abbreviated output):

$ rpm -qi python3-colorlog
Name        : python3-colorlog
Version     : 4.1.0
Release     : 1.fc31
Architecture: noarch
Source RPM  : python-colorlog-4.1.0-1.fc31.src.rpm
URL         : https://github.com/borntyping/python-colorlog
Bug URL     : https://bugz.fedoraproject.org/python-colorlog
Summary     : A colored formatter for the Python logging module
Description :
"colorlog.ColoredFormatter is a formatter for use with Python's logging
 module that outputs records using terminal colors."

…That redirects to https://apps.fedoraproject.org/packages/python-colorlog/bugs/all, which in turn produces another redirect with very strange contents:

$ curl https://apps.fedoraproject.org/packages/python-colorlog/bugs/all
<html>
 <head>
<script type="text/javascript" src="/packages/tw2/resources/tw2.jquery/static/jquery/1.7.1/jquery.js" ></script>

<script type="text/javascript" src="/packages/tw2/resources/moksha.wsgi.widgets.moksha_js/static/moksha.js" ></script>

<script type="text/javascript" src="/packages/tw2/resources/fedoracommunity.connectors.widgets.widgets/static/js/fcomm.js" ></script>
  <title>302 Found</title>
 </head>
 <body>
  <h1>302 Found</h1>
  The resource was found at <a href="http://localhost:10016/packages/s/python-colorlog">http://localhost:10016/packages/s/python-colorlog</a>;
you should be redirected automatically.


 </body>
</html>

A 302 redirect to some port for a service (that is most assuredly not running) on localhost?! What’s up with that?

And perhaps as a result, python-colorlog has no listing at apps.fedoraproject.org. It does, at src.fedoraproject.org. But its Fedora Packages listing has gone AWOL. (Or, perhaps, moved to my localhost!)

Then I started checking my own packages:

Out of 5 packages, only one is listed at apps.fedoraproject.org. What gives?

1 Like

Filed a bug at https://github.com/fedora-infra/fedora-packages/issues/436

Actually it appears to be a known problem, based on #432

3 Likes

This seems to happen quite often. I remember @cverna explaining why it does too, probably on the infrastructure mailing list. There is a rewrite in progress here, but I’m not sure how mature it is and when it’ll replace the current version:

1 Like

I’m not sure “in progress” is quite the correct term, since all of the commits there were made between Oct 21 and Nov 8, and it’s been dormant since.