while using yum.repo. I had not used my nc4010 for a while and the kernel was at 2.6.18-53.1.13 (update took it to 1.21). media://1161131669.029329%233/Fedora/RPMS/emacs-21.4-17.i386.rpm: [Errno 4] IOError:
Add an online repo from RHEL or CentOS... Now #yum install "package name " worked. [[email protected] yum.repos.d]# yum install xorg-x11-proto-devel.i386 Loading "installonlyn" plugin Loading "rhnplugin" plugin This system is not registered with RHN. This lets us point our yum.conf on the test server to a working repo on the install server, without taking up a ton of room on the install server. Code blocks~~~ Code surrounded in tildes is easier to read ~~~ Links/URLs[Red Hat Customer Portal](https://access.redhat.com) Learn more Close Red Hat Bugzilla – Bug212180 yum problem: urlopen error unknown url type: media
As you can see, the repository was built successfully and the primary.xml.gz was also read successfully; but the urlopen error occurs when the header of a package is fetched. reply | permalink Toby Bluhm Just some guesses here . . . I then pointed my CentOS-Base.repo to my 5.2 repo. It seems that because of the "unusual" protocol, media:, we're unable to (easily) set up our PXE server to grab packages from the resultant yum repo.
reply | permalink Kai Schaetzl Then, as Toby says, there might be something wrong with your local yum/repo config. Search this Thread 01-24-2010, 10:49 PM #1 yuanjunliang LQ Newbie Registered: Apr 2009 Posts: 22 Rep: yum IOError:
Visit the following links: Site Howto | Site FAQ | Sitemap | Register Now If you have any problems with the registration process or your account login, please contact us. First I updated to 'current' 5.1 (by current I mean I have not synced my 5.1 local repo since building my 5.2 repo). The problem remains the same. Command to check CPU, CORE and SOCKET + LINUX Basic monitoring commands for solaris SUN 5.10 How to remove Logical Drive + HP UX "IOError: urlopen error unknown url type: media"
Regards, Razvan Comment 21 Wart 2006-11-02 20:33:00 EST (In reply to comment #20) > Is there an "elegant" way to fix this, please - such as a corrected version of > But this method does not work in FC6.. Could also clear out all non Centos specific repos just to reducethe noise.Just an FYI, in VI, the "l" command will show "hidden" characters in anunambiguous way. If this is your first visit, be sure to check out the FAQ by clicking the link above.
There's nothing in yum that can > handle them only in the superclass added in anaconda so it can use yum for the > depsolving component, etc. carltm View Public Profile View LQ Blog View Review Entries View HCL Entries Visit carltm's homepage! FC6 managed to break this for DVDs too: https://bugzilla.redhat.com/bugzilla....cgi?id=212180 SaGS View Public Profile Find all posts by SaGS #3 3rd November 2006, 03:13 PM bob Offline Administrator (yeah, back Comment 50 Jason Mack 2007-01-17 17:11:50 EST Jeremy, since this is also a problem in RHEL5 public Beta, should we clone this, or change the Product variable?
When I try to use this server to upgrade other machines, the quoted message locks me up. navigate here If I recall right you have a few (5.1, 5.2) repos "flyingaround" and also installed from DVD in the past, so, you may simply beusing the wrong Base.repo file or the Lotsto bring up to snuff. Either a new sync orclean all got you going last time ;-)Kai--Kai Sch?tzl, Berlin, GermanyGet your web at Conactive Internet Services: http://www.conactive.com reply | permalink Robert Moskowitz The other times a
I wait for ur response .. It happened to me after an upgrade from FC5 to FC6, on more than one machine. For an unadvised webserver administrator, this can be a problem too, because he will loopback-mount the ISO image & publish it, making inoperable a whole Fedora mirror... Check This Out Yum Ioerror?
Please wait.---> Downloading header for yum-metadata-parser to pack into transactionset.media://1213888991.267240%231/CentOS/yum-metadata-parser-1.1.2-2.el5.i386.rpm:[Errno 4] IOError:
Please wait. ---> Downloading header for mc to pack into transaction set.
For now I just change to that directory and use yum localinstall. How can you be so sure > about your technique ? As you can see, the repository was built successfully and > the primary.xml.gz was also read successfully; but the urlopen error occurs when > the header of a package is fetched. Also, a diff between the two files would catch some overlooked typo.
Also, a diff between the two files would catch someoverlooked typo.The problem is deeper than this. If I recall right you have a few (5.1, 5.2) repos "flying around" and also installed from DVD in the past, so, you may simply be using the wrong Base.repo file I ran the createrepo to create the repository. this contact form They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
I thought that was the problem but isn't. > > I see the same problem that was originally reported, with the minor difference > that in my configuration, where ? > Friends , I want to install package using yum from DVD in RHEL 5 . Could it be a bug in FC6 version of yum? ran rpm -ivh "createrepo......" It got installed. 9.
But still I got the below error : [[email protected] yum.repos.d]# yum install ksh* Loading "rhnplugin" plugin Loading "installonlyn" plugin This system is not registered with RHN. See that in the log. Yum ought to work when pointed to a local loop mounted ISO image. The time now is 06:58 AM.
Nobody cares about where precisely in the expansive yum class hierarchy this error message gives birth. Comment 8 josip 2006-10-28 03:47:02 EDT I see the same problem. Any ideas how to do this? If I recall right you have a few (5.1, 5.2) repos "flyingaround" and also installed from DVD in the past, so, you may simply beusing the wrong Base.repo file or the
If the broken still looks right, try making a backup of the broken & copy in the working - there may be some overlooked typo or a character that's invisible to DVD of FC5 don't have this bug. > > There's no bug here. So, what was a five-minute matter of making some symlinks is now a multi-hour process for newer RH dists, RHEL Public Beta, FC6, etc. At home I have no internet - at work, I do..
Perhaps some Robert Moskowitz at Jul 3, 2008 at 4:21 pm ⇧ William L. The time now is 01:58 AM. Try comparing the broken with the working. Reply With Quote 03-27-2009 #5 zengmao View Profile View Forum Posts Private Message View Articles Just Joined!