SleepDevil commented on issue #2998:
URL: https://github.com/apache/couchdb/issues/2998#issuecomment-657004360


   I find that I forgot to enable the Apache CouchDB package repository,but 
when I have enabled,there is still an error:
   ```
   http://apache.bintray.com/couchdb-rpm/el7/x86_64/repodata/repomd.xml: [Errno 
14] curl#6 - "Could not resolve host: apache.bintray.com; Unknown error"
   Trying other mirror.
    One of the configured repositories failed (bintray--apache-couchdb-rpm),
    and yum doesn't have enough cached data to continue. At this point the only
    safe thing yum can do is fail. There are a few ways to work "fix" this:
        1. Contact the upstream for the repository and get them to fix the 
problem.
        2. Reconfigure the baseurl/etc. for the repository, to point to a 
working
           upstream. This is most often useful if you are using a newer
           distribution release than is supported by the repository (and the
           packages for the previous distribution release still work).
   
        3. Run the command with the repository temporarily disabled
               yum --disablerepo=bintray--apache-couchdb-rpm ...
        4. Disable the repository permanently, so yum won't use it by default. 
Yum
           will then just ignore the repository until you permanently enable it
           again or use --enablerepo for temporary usage:
   
               yum-config-manager --disable bintray--apache-couchdb-rpm
           or
               subscription-manager repos --disable=bintray--apache-couchdb-rpm
        5. Configure the failing repository to be skipped, if it is unavailable.
           Note that yum will try to contact the repo. when it runs most 
commands,
           so will have to try and fail each time (and thus. yum will be be much
           slower). If it is a very temporary problem though, this is often a 
nice
           compromise:
   ```


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to