Re: [wlug] Fedora (the one we support) revisited
Hi All, I did make sure that I had a good repo and plenty of mirrors then "yum update" There were 54 items to d/load. at the 11th file, some three hours later (at 47k), a thing called "gzip" failed to down load so it tried mirror after mirror very slowly. Failing on each occasion. I think it was at the fourteenth unsuccessful mirror attempt that I began cutting 25mm lengths off the modem cord. The mirror sites then went by much more quickly as they were unable to connect. The success in this is that there were TONNES of mirrors to try if only I had waited a couple more days things may have been OK and I could have got on with updating yum and possibly installing mplayer. I am finding Fedora to be bad for my self esteem and I note with horror that I have forced myself into the position of the official "idiot question asker". To this end I am unsubscribing from the mailing list so as not to broadcast my ineptitude to all and sundry when doing fubars in the future. The distro that has given me the least grief is "Mandrake"> (yep. Windows user) If any one is willing to burn me a good copy of the latest issue I would be happy if they would contact me off list. Many thanks to all the list members. Regards John.
A bad checksum probably means the file corrupted while you were downloading it. Possible reasons for this are:
1) a web proxy in your path (transparent or otherwise) has an incomplete copy cached 2) the file changed while you were downloading it 3) yum didn't actually finish downloading the file 4) the copy on the server is incomplete or corrupt.
To fix this, try running 'yum update' then 'yum install mplayer' when the update finishes. If that doesn't work, try adding more yum mirrors to your mirror list - I notice that your output contained comments regarding 'No more mirrors to try' etc.
As to your second question - it carried on because only one part of the download failed, the others are all intact.
Thought I was doing fairly good, Wgot the public
key. >Copied freshrpms, fixed a parsing error but now got a >checksum problem.
I have saved the whole drama if anyone has time to help I would apreciatte it Terminal entries follow:
[root(a)localhost john]# yum install mplayer
..
http://ayo.freshrpms.net/fedora/linux/3/i386/freshrpms/RP MS/mplayer-1.0-0.12.20041025.1.fc3.fr.i386.rpm: >[Errno -1] Package does not match checksum >freshrpms: [Errno 256] No more mirrors to try. >[root(a)localhost john]#
Also why go through the whole download if the thing fails the checksum* Regards John
I wouldn't feel too bad about it. In my experience with Fedora Core 1 and 2, yum and Up2Date were both notorious for hanging, and I generally wgetted (wgot?) tar.gzs and compiled from source just to be sure I'd actually get the darned package in a timely manner. jaytee(a)clear.net.nz wrote:
Hi All, I did make sure that I had a good repo and plenty of mirrors then "yum update" There were 54 items to d/load. at the 11th file, some three hours later (at 47k), a thing called "gzip" failed to down load so it tried mirror after mirror very slowly. Failing on each occasion. I think it was at the fourteenth unsuccessful mirror attempt that I began cutting 25mm lengths off the modem cord. The mirror sites then went by much more quickly as they were unable to connect. The success in this is that there were TONNES of mirrors to try if only I had waited a couple more days things may have been OK and I could have got on with updating yum and possibly installing mplayer. I am finding Fedora to be bad for my self esteem and I note with horror that I have forced myself into the position of the official "idiot question asker". To this end I am unsubscribing from the mailing list so as not to broadcast my ineptitude to all and sundry when doing fubars in the future. The distro that has given me the least grief is "Mandrake"> (yep. Windows user) If any one is willing to burn me a good copy of the latest issue I would be happy if they would contact me off list. Many thanks to all the list members. Regards John.
A bad checksum probably means the file corrupted while you were downloading it. Possible reasons for this are:
1) a web proxy in your path (transparent or otherwise) has an incomplete copy cached 2) the file changed while you were downloading it 3) yum didn't actually finish downloading the file 4) the copy on the server is incomplete or corrupt.
To fix this, try running 'yum update' then 'yum install mplayer' when the update finishes. If that doesn't work, try adding more yum mirrors to your mirror list - I notice that your output contained comments regarding 'No more mirrors to try' etc.
As to your second question - it carried on because only one part of the download failed, the others are all intact.
Thought I was doing fairly good, Wgot the public
key. >Copied freshrpms, fixed a parsing error but now got a >checksum problem.
I have saved the whole drama if anyone has time to help I would apreciatte it Terminal entries follow:
[root(a)localhost john]# yum install mplayer
..
MS/mplayer-1.0-0.12.20041025.1.fc3.fr.i386.rpm: >[Errno -1] Package does not match checksum >freshrpms: [Errno 256] No more mirrors to try. >[root(a)localhost john]#
Also why go through the whole download if the thing fails the checksum* Regards John
_______________________________________________ wlug mailing list | wlug(a)list.waikato.ac.nz Unsubscribe: http://list.waikato.ac.nz/mailman/listinfo/wlug
Yep, I had the same experiences with both tools too when I used Fedora. Joseph. On Wed, 01 Dec 2004 22:26, Bnonn wrote:
I wouldn't feel too bad about it. In my experience with Fedora Core 1 and 2, yum and Up2Date were both notorious for hanging, and I generally wgetted (wgot?) tar.gzs and compiled from source just to be sure I'd actually get the darned package in a timely manner.
jaytee(a)clear.net.nz wrote:
The distro that has given me the least grief is "Mandrake"> (yep. Windows user)
There's the potential there to have a frustrating experience too. Every time I have had a problem with Mandrake I have been unable to quickly find a resolution whereas with Debian you can usually get an answer quickly using google. For example, a while back I upgraded from 9.2 to 10. That screwed up a few things. After fixing that I had to upgrade to kernel 2.6 to make DRI work, that screwed up a few things, one of them being sound, which I didn't really care about at the time. The other day I decided I wanted sound to work again. Looked in the HOWTO, compiled the right module, made sure it was installed correctly. No sound. Couldn't figure out why, spent a couple of hours searching the web and trying things out. Eventually came across something that mentioned alsaconf. Ran that and it all burst into life. I have still not figured out how the Mandrake profile thing works for network setups because it seemed badly broken in 9.2 and still seems badly broken in 10.0. The thing that is broken about it is that network card configs seem to be global, so you can't have a card using dhcp in one profile and static ip in another. g -- Glenn Ramsey <glenn(a)componic.co.nz> 07 8627077 http://www.componic.co.nz
participants (4)
-
Bnonn -
Glenn Ramsey -
jaytee＠clear.net.nz -
Joseph Gibbs