Issue Type: Bug Bug
Affects Versions: current
Assignee: magnayn
Components: repository
Created: 01/Sep/14 10:02 AM
Description:

[root@localhost yum.repos.d]# yum update jenkins
Resolving Dependencies
--> Running transaction check
---> Package jenkins.noarch 0:1.554.1-1.1 will be updated
---> Package jenkins.noarch 0:1.562-1.1 will be an update
--> Finished Dependency Resolution

Dependencies Resolved

========================================================================================================================================================
Package Arch Version Repository Size
========================================================================================================================================================
Updating:
jenkins noarch 1.562-1.1 jenkins 59 M

Transaction Summary
========================================================================================================================================================
Upgrade 1 Package

Total download size: 59 M
Is this ok [y/d/N]: y
Downloading packages:

One of the configured repositories failed (Unknown),
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. Disable the repository, 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 <repoid>

4. 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:

yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: jenkins

Environment: Fedora 19 on a x86_64
Project: Jenkins
Priority: Minor Minor
Reporter: Vittorio Boccone
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to