Bug 404841 - Missing repodata for http://koji.fedoraproject.org/packages/**
Missing repodata for http://koji.fedoraproject.org/packages/**
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: buildsystem (Show other bugs)
rawhide
All Linux
low Severity low
: ---
: ---
Assigned To: Seth Vidal
Fedora Extras Quality Assurance
http://koji.fedoraproject.org/packages/
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-11-29 13:51 EST by Jan Kratochvil
Modified: 2007-11-30 17:12 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-11-29 14:06:13 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jan Kratochvil 2007-11-29 13:51:53 EST
Description of problem:
While trying to use RHTS (Red Hat Test System - its Free version is
http://testing.108.redhat.com/) for freshly built packages I need repodata (from
createrepo).
It is simple for internal Red Hat Brew build system as I have the built rpm
files on NFS so I can use createrepo(1) and even symlink it etc.
For HTTP remote http://koji.fedoraproject.org/packages/ directory I have to
download everything first.

Steps to Reproduce:
1. Build http://koji.fedoraproject.org/packages/gdb/6.6/36.fc8/
2. Try to insert this fresh build into a new file: /etc/yum.repos.d/fresh.repo

Actual results:
wget -r ...
Own webhosting.

Expected results:
Insert URL:
http://koji.fedoraproject.org/repodata/packages/gdb/6.6/36.fc8/
or
http://koji.fedoraproject.org/packages/gdb/6.6/36.fc8/repodata/

Additional info:
The same request applies to the subdirectories of:
http://koji.fedoraproject.org/scratch/

Never list the illustrative URL http://koji.fedoraproject.org/packages/ root
directory itself as it is really too slow.
Comment 1 Seth Vidal 2007-11-29 14:06:13 EST
I think you want to file a ticket with the fedora infrastructure team here:

https://hosted.fedoraproject.org/projects/fedora-infrastructure/report/1

Note You need to log in before you can comment on or make changes to this bug.