Re: Update failure
On Tue, Oct 6, 2009 at 8:38 AM, Adam Hough a...@gradientzero.com wrote: On Mon, Oct 5, 2009 at 1:05 PM, Fabio Jara roninteko...@gmail.com wrote: Hello Patel On Mon, 2009-10-05 at 11:58 -0430, Patrick O'Callaghan wrote: On Mon, 2009-10-05 at 11:37 -0400, Fabio Jara wrote: Hello Patel, On Mon, 2009-10-05 at 08:12 -0430, Patrick O'Callaghan wrote: On Mon, 2009-10-05 at 08:03 -0400, Fabio Jara wrote: I hope Tim (ignored_mailbox) will not see your advice. He recently was very angry about yum clean all. Now it's forbidden to give such advice ;-) Why is that? that worked for me two times in a row now, why is it forbidden? O_o For future reference. The only reason to use yum clean all instead of yum clean metadata is if you're running out of space because of cached packages. Then you get to waste bandwidth (not to mention server resources) downloading them again. yum clean metadata has solved every problem I've ever had that yum clean all would have solved. I would be interested to hear *reasoned* argument about why this might not always be the case (apart from the disk space issue already mentioned). A while ago i try to update my notebook with yum, and for some reason there was a conflict between the kmod-nvidia driver and another package. So i did all the normal methods that the error suggest me, also yum clean metadata. But when i try to update the same error got me again, so i got wild and type yum clean all. Try again and it work! So, that's why i suggested to do the same. :) I think that with the package-cleanup --problems and the --dupes something was still there, so the clean all remove it. That would indicate a bug in yum clean metadata. If this happens again you should report it. In any case the sequence yum clean metadata and only if that doesn't work then yum clean all is perfectly reasonable. And a short time ago i was having almost the same issue, i asked for help in the mailing list, and the problem this time was that the package have been updated in the mirror but not it's dependencies. So after a couple of days the error wasn't there anymore. I don't see the relevance of this last comment. If the package dependencies haven't been updated in a mirror, neither clean all nor clean metadata is going to fix the problem. This last comment was just for some people to notice that sometimes the error seems to be the same if the dependencies aren't ready yet, but these errors are not the same. poc My best regards. https://www.redhat.com/mailman/listinfo/fedora-listhttp://fedoraproject.org/wiki/Communicate/MailingListGuidelines So I had a similar issue for the pst week on my desktop machine. At some point updates did not get applied right. Either I accidentally rebooted the system while updating or something else messed up. I could not update several of the packages that claimed they were missing files or prerequisites. If you run rpm -Va --nofiles --nodigest and you see Unsatisfied dependencies error messages, then you might have the same issue I had. Now if that is the case you will need to re-download and reinstall the software and you might have to force the re-install of those packages. Now you should just have to re-download the dependancies of the packages you need to get everything updated to the current level. -- Hello After doing 'yum clean all' and yum clean metedata'.there is error in update.. I am not able to update my systemThe error is as follows: [r...@dcis ~]# yum update Loaded plugins: refresh-packagekit adobe-linux-i386 | 951 B 00:00 adobe-linux-i386/primary | 12 kB 00:00 adobe-linux-i386 17/17 Error: Cannot retrieve repository metadata (repomd.xml) for repository: fedora. Please verify its path and try again Please suggest me.what shall I do? fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines -- Sandeep Kumar Patel University of Hyderabad -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Update failure
Hello Patel, On Mon, 2009-10-05 at 09:56 +0400, Hiisi wrote: 2009/10/5 Fabio Jara roninteko...@gmail.com: Hello Patel, I personally recommend to clean all of yum #yum clean all After that tray to update normally, if it gives you the same error just wait. one or two days. I have had the same error and trust me, you don't want to force the update with #yum update --skip-broken I did that, and it gave me a conflict with my nvidia drive, kmod-nvidia. The problem is probably that a new package have been release and the mirror your connecting does not have all the package yet. Hope my advice help you. I hope Tim (ignored_mailbox) will not see your advice. He recently was very angry about yum clean all. Now it's forbidden to give such advice ;-) Why is that? that worked for me two times in a row now, why is it forbidden? O_o For future reference. Best regards. --SNIP-- -- Hiisi. Registered Linux User #487982. Be counted at: http://counter.li.org/ -- Spandex is a privilege, not a right. -- SIP: hi...@ekiga.net -- pub 1024D/085B139A -- Powered by Fedora: http://fedoraproject.org/ -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Update failure
On Mon, 2009-10-05 at 08:03 -0400, Fabio Jara wrote: I hope Tim (ignored_mailbox) will not see your advice. He recently was very angry about yum clean all. Now it's forbidden to give such advice ;-) Why is that? that worked for me two times in a row now, why is it forbidden? O_o For future reference. The only reason to use yum clean all instead of yum clean metadata is if you're running out of space because of cached packages. Then you get to waste bandwidth (not to mention server resources) downloading them again. yum clean metadata has solved every problem I've ever had that yum clean all would have solved. I would be interested to hear *reasoned* argument about why this might not always be the case (apart from the disk space issue already mentioned). poc -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Update failure
Patrick O'Callaghan wrote: On Mon, 2009-10-05 at 08:03 -0400, Fabio Jara wrote: I hope Tim (ignored_mailbox) will not see your advice. He recently was very angry about yum clean all. Now it's forbidden to give such advice ;-) Why is that? that worked for me two times in a row now, why is it forbidden? O_o For future reference. The only reason to use yum clean all instead of yum clean metadata is if you're running out of space because of cached packages. Then you get to waste bandwidth (not to mention server resources) downloading them again. yum clean metadata has solved every problem I've ever had that yum clean all would have solved. I would be interested to hear *reasoned* argument about why this might not always be the case (apart from the disk space issue already mentioned). I have a single /var/cache/yum filesystem on NFS which allows me to not only save disk and bandwidth, but to speed updates considerably. I'm sure using it from more than one machine at a time could cause a problem, but it is a useful stopgap here. It avoids having a mirror of everything, while pulling down each rpm only once, and only those actually used here. The ideal solution would take care of this, but with only two admins doing updates manual sync works for us. I had a tool to do a more perfect job of contention control, but it proved to be overkill. -- Bill Davidsen david...@tmr.com We have more to fear from the bungling of the incompetent than from the machinations of the wicked. - from Slashdot -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Update failure
Hello Patel, On Mon, 2009-10-05 at 08:12 -0430, Patrick O'Callaghan wrote: On Mon, 2009-10-05 at 08:03 -0400, Fabio Jara wrote: I hope Tim (ignored_mailbox) will not see your advice. He recently was very angry about yum clean all. Now it's forbidden to give such advice ;-) Why is that? that worked for me two times in a row now, why is it forbidden? O_o For future reference. The only reason to use yum clean all instead of yum clean metadata is if you're running out of space because of cached packages. Then you get to waste bandwidth (not to mention server resources) downloading them again. yum clean metadata has solved every problem I've ever had that yum clean all would have solved. I would be interested to hear *reasoned* argument about why this might not always be the case (apart from the disk space issue already mentioned). A while ago i try to update my notebook with yum, and for some reason there was a conflict between the kmod-nvidia driver and another package. So i did all the normal methods that the error suggest me, also yum clean metadata. But when i try to update the same error got me again, so i got wild and type yum clean all. Try again and it work! So, that's why i suggested to do the same. :) I think that with the package-cleanup --problems and the --dupes something was still there, so the clean all remove it. And a short time ago i was having almost the same issue, i asked for help in the mailing list, and the problem this time was that the package have been updated in the mirror but not it's dependencies. So after a couple of days the error wasn't there anymore. That's my history XD, a very short one. poc My kind regards. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Update failure
On Mon, 2009-10-05 at 11:37 -0400, Fabio Jara wrote: Hello Patel, On Mon, 2009-10-05 at 08:12 -0430, Patrick O'Callaghan wrote: On Mon, 2009-10-05 at 08:03 -0400, Fabio Jara wrote: I hope Tim (ignored_mailbox) will not see your advice. He recently was very angry about yum clean all. Now it's forbidden to give such advice ;-) Why is that? that worked for me two times in a row now, why is it forbidden? O_o For future reference. The only reason to use yum clean all instead of yum clean metadata is if you're running out of space because of cached packages. Then you get to waste bandwidth (not to mention server resources) downloading them again. yum clean metadata has solved every problem I've ever had that yum clean all would have solved. I would be interested to hear *reasoned* argument about why this might not always be the case (apart from the disk space issue already mentioned). A while ago i try to update my notebook with yum, and for some reason there was a conflict between the kmod-nvidia driver and another package. So i did all the normal methods that the error suggest me, also yum clean metadata. But when i try to update the same error got me again, so i got wild and type yum clean all. Try again and it work! So, that's why i suggested to do the same. :) I think that with the package-cleanup --problems and the --dupes something was still there, so the clean all remove it. That would indicate a bug in yum clean metadata. If this happens again you should report it. In any case the sequence yum clean metadata and only if that doesn't work then yum clean all is perfectly reasonable. And a short time ago i was having almost the same issue, i asked for help in the mailing list, and the problem this time was that the package have been updated in the mirror but not it's dependencies. So after a couple of days the error wasn't there anymore. I don't see the relevance of this last comment. If the package dependencies haven't been updated in a mirror, neither clean all nor clean metadata is going to fix the problem. poc -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Update failure
Hello Patel On Mon, 2009-10-05 at 11:58 -0430, Patrick O'Callaghan wrote: On Mon, 2009-10-05 at 11:37 -0400, Fabio Jara wrote: Hello Patel, On Mon, 2009-10-05 at 08:12 -0430, Patrick O'Callaghan wrote: On Mon, 2009-10-05 at 08:03 -0400, Fabio Jara wrote: I hope Tim (ignored_mailbox) will not see your advice. He recently was very angry about yum clean all. Now it's forbidden to give such advice ;-) Why is that? that worked for me two times in a row now, why is it forbidden? O_o For future reference. The only reason to use yum clean all instead of yum clean metadata is if you're running out of space because of cached packages. Then you get to waste bandwidth (not to mention server resources) downloading them again. yum clean metadata has solved every problem I've ever had that yum clean all would have solved. I would be interested to hear *reasoned* argument about why this might not always be the case (apart from the disk space issue already mentioned). A while ago i try to update my notebook with yum, and for some reason there was a conflict between the kmod-nvidia driver and another package. So i did all the normal methods that the error suggest me, also yum clean metadata. But when i try to update the same error got me again, so i got wild and type yum clean all. Try again and it work! So, that's why i suggested to do the same. :) I think that with the package-cleanup --problems and the --dupes something was still there, so the clean all remove it. That would indicate a bug in yum clean metadata. If this happens again you should report it. In any case the sequence yum clean metadata and only if that doesn't work then yum clean all is perfectly reasonable. And a short time ago i was having almost the same issue, i asked for help in the mailing list, and the problem this time was that the package have been updated in the mirror but not it's dependencies. So after a couple of days the error wasn't there anymore. I don't see the relevance of this last comment. If the package dependencies haven't been updated in a mirror, neither clean all nor clean metadata is going to fix the problem. This last comment was just for some people to notice that sometimes the error seems to be the same if the dependencies aren't ready yet, but these errors are not the same. poc My best regards. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Update failure
On Mon, Oct 5, 2009 at 1:05 PM, Fabio Jara roninteko...@gmail.com wrote: Hello Patel On Mon, 2009-10-05 at 11:58 -0430, Patrick O'Callaghan wrote: On Mon, 2009-10-05 at 11:37 -0400, Fabio Jara wrote: Hello Patel, On Mon, 2009-10-05 at 08:12 -0430, Patrick O'Callaghan wrote: On Mon, 2009-10-05 at 08:03 -0400, Fabio Jara wrote: I hope Tim (ignored_mailbox) will not see your advice. He recently was very angry about yum clean all. Now it's forbidden to give such advice ;-) Why is that? that worked for me two times in a row now, why is it forbidden? O_o For future reference. The only reason to use yum clean all instead of yum clean metadata is if you're running out of space because of cached packages. Then you get to waste bandwidth (not to mention server resources) downloading them again. yum clean metadata has solved every problem I've ever had that yum clean all would have solved. I would be interested to hear *reasoned* argument about why this might not always be the case (apart from the disk space issue already mentioned). A while ago i try to update my notebook with yum, and for some reason there was a conflict between the kmod-nvidia driver and another package. So i did all the normal methods that the error suggest me, also yum clean metadata. But when i try to update the same error got me again, so i got wild and type yum clean all. Try again and it work! So, that's why i suggested to do the same. :) I think that with the package-cleanup --problems and the --dupes something was still there, so the clean all remove it. That would indicate a bug in yum clean metadata. If this happens again you should report it. In any case the sequence yum clean metadata and only if that doesn't work then yum clean all is perfectly reasonable. And a short time ago i was having almost the same issue, i asked for help in the mailing list, and the problem this time was that the package have been updated in the mirror but not it's dependencies. So after a couple of days the error wasn't there anymore. I don't see the relevance of this last comment. If the package dependencies haven't been updated in a mirror, neither clean all nor clean metadata is going to fix the problem. This last comment was just for some people to notice that sometimes the error seems to be the same if the dependencies aren't ready yet, but these errors are not the same. poc My best regards. https://www.redhat.com/mailman/listinfo/fedora-listhttp://fedoraproject.org/wiki/Communicate/MailingListGuidelines So I had a similar issue for the pst week on my desktop machine. At some point updates did not get applied right. Either I accidentally rebooted the system while updating or something else messed up. I could not update several of the packages that claimed they were missing files or prerequisites. If you run rpm -Va --nofiles --nodigest and you see Unsatisfied dependencies error messages, then you might have the same issue I had. Now if that is the case you will need to re-download and reinstall the software and you might have to force the re-install of those packages. Now you should just have to re-download the dependancies of the packages you need to get everything updated to the current level. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Update failure
On 10/04/2009 10:48 PM, sandeep Patel wrote: Hello everyone when i do update in fedora 11(x86_64).then it shows error like this Please suggest me.what shall i do to get update. You seem to be hitting a stale mirror. # yum clean metadata # yum update If that doesn't work, try # yum update --skip-broken Details at http://mether.wordpress.com/2009/10/01/preventing-dependency-breakage-part-ii/ Rahul -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Update failure
Hello Patel, I personally recommend to clean all of yum #yum clean all After that tray to update normally, if it gives you the same error just wait. one or two days. I have had the same error and trust me, you don't want to force the update with #yum update --skip-broken I did that, and it gave me a conflict with my nvidia drive, kmod-nvidia. The problem is probably that a new package have been release and the mirror your connecting does not have all the package yet. Hope my advice help you. Best regards. On Sun, Oct 4, 2009 at 1:46 PM, Rahul Sundaram sunda...@fedoraproject.orgwrote: On 10/04/2009 10:48 PM, sandeep Patel wrote: Hello everyone when i do update in fedora 11(x86_64).then it shows error like this Please suggest me.what shall i do to get update. You seem to be hitting a stale mirror. # yum clean metadata # yum update If that doesn't work, try # yum update --skip-broken Details at http://mether.wordpress.com/2009/10/01/preventing-dependency-breakage-part-ii/ Rahul -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines -- Fabio Jara. Universidad Privada del Este - Paraguay. IT Manager. Fedora Ambassador for Paraguay. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Update failure
2009/10/5 Fabio Jara roninteko...@gmail.com: Hello Patel, I personally recommend to clean all of yum #yum clean all After that tray to update normally, if it gives you the same error just wait. one or two days. I have had the same error and trust me, you don't want to force the update with #yum update --skip-broken I did that, and it gave me a conflict with my nvidia drive, kmod-nvidia. The problem is probably that a new package have been release and the mirror your connecting does not have all the package yet. Hope my advice help you. I hope Tim (ignored_mailbox) will not see your advice. He recently was very angry about yum clean all. Now it's forbidden to give such advice ;-) Best regards. --SNIP-- -- Hiisi. Registered Linux User #487982. Be counted at: http://counter.li.org/ -- Spandex is a privilege, not a right. -- SIP: hi...@ekiga.net -- pub 1024D/085B139A -- Powered by Fedora: http://fedoraproject.org/ -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
