[ 
https://issues.jenkins-ci.org/browse/JENKINS-13711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Steve Koppelman updated JENKINS-13711:
--------------------------------------

    Description: 
The yum repo at http://pkg.jenkins-ci.org/redhat is missing the yum metadata, 
which IIRC should be located in {{repodata/repomd.xml}} relative to the base of 
the repo.

Without this file, many yum operations, including installs, fail. In our case, 
we use Red Hat Satellite to replicate repos for intranet use, as individual 
nodes cannot install software directly over the internet. Replication via the 
reposync utility fails because this metadata file is not present.

A yum repo is more than a directory of package files. It also serves an index 
containing package metadata so that client systems can check for updates and 
resolve dependencies without downloading the packages themselves.

Please generate the {{repodata/}} directory and its constituent files.. and 
regenerate the files whenever new RPMs are released. This is usually done with 
the {{createrepo}} utility either directly or as part of the publish process.

  was:
The yum repo at http://pkg.jenkins-ci.org/redhat is missing the yum metadata, 
which should be located in {{repodata/repomd.xml}} relative to the base of the 
repo.

Without this file, many yum operations, including installs, fail. In our case, 
we use Red Hat Satellite to replicate repos for intranet use, as individual 
nodes cannot install software directly over the internet. Replication via the 
reposync utility fails because this metadata file is not present.

A yum repo is more than a directory of package files. It also serves an index 
containing package metadata so that client systems can check for updates and 
resolve dependencies without downloading the packages themselves.

Please generate the {{repodata/}} directory and its constituent files.. and 
regenerate the files whenever new RPMs are released. This is usually done with 
the {{createrepo}} utility either directly or as part of the publish process.

    
> Official Redhat yum repo (and mirrors) missing required repomd.xml
> ------------------------------------------------------------------
>
>                 Key: JENKINS-13711
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13711
>             Project: Jenkins
>          Issue Type: Bug
>          Components: infrastructure
>    Affects Versions: current
>            Reporter: Steve Koppelman
>              Labels: website, yum
>
> The yum repo at http://pkg.jenkins-ci.org/redhat is missing the yum metadata, 
> which IIRC should be located in {{repodata/repomd.xml}} relative to the base 
> of the repo.
> Without this file, many yum operations, including installs, fail. In our 
> case, we use Red Hat Satellite to replicate repos for intranet use, as 
> individual nodes cannot install software directly over the internet. 
> Replication via the reposync utility fails because this metadata file is not 
> present.
> A yum repo is more than a directory of package files. It also serves an index 
> containing package metadata so that client systems can check for updates and 
> resolve dependencies without downloading the packages themselves.
> Please generate the {{repodata/}} directory and its constituent files.. and 
> regenerate the files whenever new RPMs are released. This is usually done 
> with the {{createrepo}} utility either directly or as part of the publish 
> process.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to