Bug 429697 - Many Rawhide (development) mirrors incomplete
Summary: Many Rawhide (development) mirrors incomplete
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: yum
Version: rawhide
Hardware: i386
OS: Linux
low
low
Target Milestone: ---
Assignee: Seth Vidal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-01-22 14:55 UTC by Γριφεγ
Modified: 2014-01-21 23:01 UTC (History)
5 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2008-01-22 15:18:56 UTC


Attachments (Terms of Use)
The mirrorlist that I get (1.71 KB, text/plain)
2008-01-22 14:55 UTC, Γριφεγ
no flags Details

Description Γριφεγ 2008-01-22 14:55:01 UTC
Description of problem:
I have read about the yum-security plugin in Red Hat Magazine. Then I tried
installing it, but this happened:

[root@localhost ~]# yum install yum-security
livna-development         100% |=========================| 2.1 kB    00:00    
adobe-linux-i386          100% |=========================|  951 B    00:00    
development               100% |=========================| 2.2 kB    00:00    
Setting up Install Process
Parsing package install arguments
No package yum-security available.
Nothing to do
[root@localhost ~]# 

...so I thought maybe it's only available in Enterprise Linux. But no! I
searched the web and it is listed on many Fedora mirrors. Days later, I issued
the command again, and then it found the package.

Version-Release number of selected component (if applicable):


How reproducible:
~80%

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Maybe this applies to other branches as well (F8, F7, ...). I think there is
already a script that checks if mirrors are up-to-date, but where is it?

Comment 1 Γριφεγ 2008-01-22 14:55:01 UTC
Created attachment 292520 [details]
The mirrorlist that I get

Comment 2 Seth Vidal 2008-01-22 15:18:56 UTC
2 days ago rawhide was pretty well damaged by something in the build process.
Lots of packages were not pushed into the tree. That's what you're seeing.


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