Re: yum-presto occasionally goes into eternal loop looking for deltas
On Thu, 7 Jan 2010, James Antill wrote:
On Thu, 2010-01-07 at 21:19 +0200, Jonathan Dieter wrote:
On Thu, 2010-01-07 at 20:44 +0200, Pekka Pietikainen wrote:
Presto is one of the best things ever, but occasionally it ends up not
finding the delta files from any of the mirrors in the mirror list and just
loops through them without making any progress. --disablepresto works
a-ok, I think yum clean all; yum update also did the trick once.
Still, this can probably be made a lot better. It shouldn't do that even if the
mirrors
are out-of-sync. Maybe add some logic that just disables
presto if the deltas are nowhere to be found after a few attempts? Anyone
else even see this happen?
Yeah, see https://bugzilla.redhat.com/show_bug.cgi?id=540140. To
summarize, the problem is that new updates have been pushed to the
server between the time you loaded primary.sqlite and prestodelta.xml.
When you run 'yum clean metadata' or 'yum clean all' it removes the
outdated cached primary.sqlite and downloads the newer version.
The bug has been closed as WONTFIX because there have only been a few
reports; I wouldn't mind revisiting that decision if someone has a
clever way of fixing it. (And I'm not convinced that checking n mirrors
and then giving up is the solution.)
The plugin could require yum = 3.2.25, and then do something like (in
config or prereposetup):
for repo in repos:
repo.mdpolicy.append('prestodelta')
...which would auto download presto MD when yum gets new repomd/primary.
People might complain though :) ... another kind of fix would be for the
plugin to call .cleanExpireCache() if the MD fails to download.
The nice server side fix is to keep around more than one complete set
of MD (possible now we have unique MD filenames), so there would have to
be two updates within the client side cache timeout. But I'm not sure
how easy that is.
But not all the drpms would be kept so if a largish number of them
changed
-sv
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: yum-presto and comps
Jens Petersen wrote: In F12 we shipped yum-presto in @gnome-desktop - a kind of a compromise I guess. Presto/deltarpm is very useful for machines with low net connectivity to mirrors but enough resources to rebuild rpms. But yum-presto is not a desktop package at all and certainly does not belong in the gnome-desktop group. [1] +1 In fact, we voted in FESCo that it should be added to one of the base groups instead (@base, I guess). It makes no sense to have it in @gnome-desktop nor in the KDE .ks file (which is where it is at the moment – for KDE, it's in the .ks because we refused to add it to @kde-desktop as it has nothing to do with KDE). Kevin Kofler -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: yum-presto and comps
On Fri, 08 Jan 2010 21:42:06 +0100 Kevin Kofler kevin.kof...@chello.at wrote: Jens Petersen wrote: In F12 we shipped yum-presto in @gnome-desktop - a kind of a compromise I guess. Presto/deltarpm is very useful for machines with low net connectivity to mirrors but enough resources to rebuild rpms. But yum-presto is not a desktop package at all and certainly does not belong in the gnome-desktop group. [1] +1 In fact, we voted in FESCo that it should be added to one of the base groups instead (@base, I guess). It makes no sense to have it in @gnome-desktop nor in the KDE .ks file (which is where it is at the moment – for KDE, it's in the .ks because we refused to add it to @kde-desktop as it has nothing to do with KDE). I guess I would be fine with it being in @base or something. We can always - it in the Xfce kickstart or any other spin that doesn't want it by default. kevin signature.asc Description: PGP signature -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
yum-presto and comps
In F12 we shipped yum-presto in @gnome-desktop - a kind of a compromise I guess. Presto/deltarpm is very useful for machines with low net connectivity to mirrors but enough resources to rebuild rpms. But yum-presto is not a desktop package at all and certainly does not belong in the gnome-desktop group. [1] Perhaps the right approach for f13 is to install yum-presto by default but to disable it by default? Lighter compression might also help to reduce the resource requirements for older machines? Jens [1] https://bugzilla.redhat.com/show_bug.cgi?id=549659 -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: yum-presto and comps
On Thu, 2010-01-07 at 04:44 -0500, Jens Petersen wrote: In F12 we shipped yum-presto in @gnome-desktop - a kind of a compromise I guess. Presto/deltarpm is very useful for machines with low net connectivity to mirrors but enough resources to rebuild rpms. But yum-presto is not a desktop package at all and certainly does not belong in the gnome-desktop group. Perhaps the right approach for f13 is to install yum-presto by default but to disable it by default? It looks like there are a couple of questions to deal with: 1) yum-presto is in @gnome-desktop and shouldn't be 2) yum-presto is enabled by default If we don't want (2), then remove it from @gnome-desktop. People who need/want it can install it using yum install yum-presto, and it will start working immediately. If we do want (2), then we just need to work out how to fix (1). If not @gnome-desktop (which is probably not where it belongs), then possibly @base? FWIW, my opinion on (2) (as the yum-presto maintainer) is that it should be installed by default, but I'm obviously biased. Lighter compression might also help to reduce the resource requirements for older machines? IIRC we've already reduced the xz compression level in our rpms from 7 to 2. (See http://osdir.com/ml/fedora-devel-list/2009-09/msg00946.html) Jonathan signature.asc Description: This is a digitally signed message part -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: yum-presto and comps
On Thu, 2010-01-07 at 04:44 -0500, Jens Petersen wrote: In F12 we shipped yum-presto in @gnome-desktop - a kind of a compromise I guess. Presto/deltarpm is very useful for machines with low net connectivity to mirrors but enough resources to rebuild rpms. But yum-presto is not a desktop package at all and certainly does not belong in the gnome-desktop group. [1] Perhaps the right approach for f13 is to install yum-presto by default but to disable it by default? Lighter compression might also help to reduce the resource requirements for older machines? I don't think that there really is something to fix here, and I don't know that I can make you happy. If I do the customization in the kickstart file, you complain as well (see PK-command-not-found) -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
yum-presto occasionally goes into eternal loop looking for deltas
Presto is one of the best things ever, but occasionally it ends up not finding the delta files from any of the mirrors in the mirror list and just loops through them without making any progress. --disablepresto works a-ok, I think yum clean all; yum update also did the trick once. Still, this can probably be made a lot better. It shouldn't do that even if the mirrors are out-of-sync. Maybe add some logic that just disables presto if the deltas are nowhere to be found after a few attempts? Anyone else even see this happen? -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: yum-presto occasionally goes into eternal loop looking for deltas
On Thu, 2010-01-07 at 20:44 +0200, Pekka Pietikainen wrote: Presto is one of the best things ever, but occasionally it ends up not finding the delta files from any of the mirrors in the mirror list and just loops through them without making any progress. --disablepresto works a-ok, I think yum clean all; yum update also did the trick once. Still, this can probably be made a lot better. It shouldn't do that even if the mirrors are out-of-sync. Maybe add some logic that just disables presto if the deltas are nowhere to be found after a few attempts? Anyone else even see this happen? Yeah, see https://bugzilla.redhat.com/show_bug.cgi?id=540140. To summarize, the problem is that new updates have been pushed to the server between the time you loaded primary.sqlite and prestodelta.xml. When you run 'yum clean metadata' or 'yum clean all' it removes the outdated cached primary.sqlite and downloads the newer version. The bug has been closed as WONTFIX because there have only been a few reports; I wouldn't mind revisiting that decision if someone has a clever way of fixing it. (And I'm not convinced that checking n mirrors and then giving up is the solution.) Jonathan signature.asc Description: This is a digitally signed message part -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: yum-presto occasionally goes into eternal loop looking for deltas
On Thu, 2010-01-07 at 21:19 +0200, Jonathan Dieter wrote:
On Thu, 2010-01-07 at 20:44 +0200, Pekka Pietikainen wrote:
Presto is one of the best things ever, but occasionally it ends up not
finding the delta files from any of the mirrors in the mirror list and just
loops through them without making any progress. --disablepresto works
a-ok, I think yum clean all; yum update also did the trick once.
Still, this can probably be made a lot better. It shouldn't do that even if
the mirrors
are out-of-sync. Maybe add some logic that just disables
presto if the deltas are nowhere to be found after a few attempts? Anyone
else even see this happen?
Yeah, see https://bugzilla.redhat.com/show_bug.cgi?id=540140. To
summarize, the problem is that new updates have been pushed to the
server between the time you loaded primary.sqlite and prestodelta.xml.
When you run 'yum clean metadata' or 'yum clean all' it removes the
outdated cached primary.sqlite and downloads the newer version.
The bug has been closed as WONTFIX because there have only been a few
reports; I wouldn't mind revisiting that decision if someone has a
clever way of fixing it. (And I'm not convinced that checking n mirrors
and then giving up is the solution.)
The plugin could require yum = 3.2.25, and then do something like (in
config or prereposetup):
for repo in repos:
repo.mdpolicy.append('prestodelta')
...which would auto download presto MD when yum gets new repomd/primary.
People might complain though :) ... another kind of fix would be for the
plugin to call .cleanExpireCache() if the MD fails to download.
The nice server side fix is to keep around more than one complete set
of MD (possible now we have unique MD filenames), so there would have to
be two updates within the client side cache timeout. But I'm not sure
how easy that is.
--
James Antill - ja...@fedoraproject.org
http://yum.baseurl.org/wiki/releases
http://yum.baseurl.org/wiki/whatsnew/3.2.26
http://yum.baseurl.org/wiki/YumMultipleMachineCaching
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
System shutoff 1 min after yum update
I did a yum update this morning; picked up about 20Mb of new stuff. 1:20 min later the system just up and powered off. There is nothing in /var/log/messages between the yum update messages and the start messages. ANy thoughts and what caused this? Here is what I got today: Jan 06 08:41:52 Updated: 2:gimp-libs-2.6.8-1.fc12.i686 Jan 06 08:41:55 Updated: krb5-libs-1.7-15.fc12.i686 Jan 06 08:42:28 Updated: 2:gimp-2.6.8-1.fc12.i686 Jan 06 08:42:38 Updated: devhelp-2.28.1-2.fc12.i686 Jan 06 08:42:39 Updated: 2:gimp-help-browser-2.6.8-1.fc12.i686 Jan 06 08:42:41 Updated: krb5-workstation-1.7-15.fc12.i686 Jan 06 08:42:43 Updated: krb5-devel-1.7-15.fc12.i686 Jan 06 08:42:47 Updated: gdb-7.0.1-19.fc12.i686 Jan 06 08:42:49 Updated: less-436-5.fc12.i686 Jan 06 08:42:51 Updated: psacct-6.3.2-59.fc12.i686 Jan 06 08:42:55 Updated: 2:shadow-utils-4.1.4.2-2.fc12.i686 Jan 06 08:43:23 Updated: selinux-policy-3.6.32-63.fc12.noarch -- 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: System shutoff 1 min after yum update
On Wed, Jan 6, 2010 at 11:54 AM, Robert Moskowitz r...@htt-consult.comwrote: I did a yum update this morning; picked up about 20Mb of new stuff. 1:20 min later the system just up and powered off. There is nothing in /var/log/messages between the yum update messages and the start messages. ANy thoughts and what caused this? Here is what I got today: Jan 06 08:41:52 Updated: 2:gimp-libs-2.6.8-1.fc12.i686 Jan 06 08:41:55 Updated: krb5-libs-1.7-15.fc12.i686 Jan 06 08:42:28 Updated: 2:gimp-2.6.8-1.fc12.i686 Jan 06 08:42:38 Updated: devhelp-2.28.1-2.fc12.i686 Jan 06 08:42:39 Updated: 2:gimp-help-browser-2.6.8-1.fc12.i686 Jan 06 08:42:41 Updated: krb5-workstation-1.7-15.fc12.i686 Jan 06 08:42:43 Updated: krb5-devel-1.7-15.fc12.i686 Jan 06 08:42:47 Updated: gdb-7.0.1-19.fc12.i686 Jan 06 08:42:49 Updated: less-436-5.fc12.i686 Jan 06 08:42:51 Updated: psacct-6.3.2-59.fc12.i686 Jan 06 08:42:55 Updated: 2:shadow-utils-4.1.4.2-2.fc12.i686 Jan 06 08:43:23 Updated: selinux-policy-3.6.32-63.fc12.noarch Certainly, it was a hardware problem. Computers worn off, just like us. There is nothing in these updates that justify the shutdown... -- Paulo Roma Cavalcanti LCG - UFRJ -- 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: System shutoff 1 min after yum update
2010/1/6 Paulo Cavalcanti pro...@gmail.com: On Wed, Jan 6, 2010 at 11:54 AM, Robert Moskowitz r...@htt-consult.com wrote: I did a yum update this morning; picked up about 20Mb of new stuff. 1:20 min later the system just up and powered off. There is nothing in /var/log/messages between the yum update messages and the start messages. ANy thoughts and what caused this? Here is what I got today: --SNIP-- Certainly, it was a hardware problem. Computers worn off, just like us. Speak for yourself! There is nothing in these updates that justify the shutdown... -- Paulo Roma Cavalcanti LCG - UFRJ I always suspect motherboard at such cases. I saw similar behaviour 3 times and each time it was broken motherboard. Just my 0.02 rubles... -- Hiisi. Registered Linux User #487982. Be counted at: http://counter.li.org/ -- Spandex is a privilege, not a right. -- SIP: hi...@ekiga.net -- Please avoid sending me Word or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- 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
yum - file conflicts when updating from i?86 to x86_64
Hi, all, I had an interesting time updating a machine from i686 to x86_64 last night. I wound up using rpm alot, and would rather have used yum more, but for problems like the one noted below (just one example out of a large number of similar instances). Is there a way to get yum to not fret about file conflicts when replacing one arch with another with the same base package name? Dependency resolution and RPM seems to be happy, but the transaction check (OK, I don't really know what that means) doesn't seem to understand what's happening. Thanks, -Bill == -- Running transaction check -- Processing Dependency: tor-core = 0.2.0.35-1.fc11 for package: tor-lsb-0.2.0.35-1.fc11.noarch --- Package tor-core.x86_64 0:0.2.1.19-2.fc12 set to be updated -- Running transaction check --- Package tor-lsb.noarch 0:0.2.1.19-2.fc12 set to be updated -- Finished Dependency Resolution Dependencies Resolved Package Arch Version Repository Size Updating: tor-core x86_64 0.2.1.19-2.fc12 fedora 956 k Updating for dependencies: tor-lsb noarch 0.2.1.19-2.fc12 fedora 12 k Transaction Summary Install 0 Package(s) Upgrade 2 Package(s) Total size: 968 k Downloading Packages: Running rpm_check_debug Running Transaction Test Finished Transaction Test Transaction Check Error: file /etc/tor/torrc from install of tor-core-0.2.1.19-2.fc12.x86_64 conflicts with file from package tor-core-0.2.0.35-1.fc11.i586 file /usr/share/man/man1/tor.1.gz from install of tor-core-0.2.1.19-2.fc12.x86_64 conflicts with file from package tor-core-0.2.0.35-1.fc11.i586 file /usr/share/tor/geoip from install of tor-core-0.2.1.19-2.fc12.x86_64 conflicts with file from package tor-core-0.2.0.35-1.fc11.i586 -- Bill McGonigle, Owner BFC Computing, LLC http://bfccomputing.com/ Telephone: +1.603.448.4440 Email, IM, VOIP: b...@bfccomputing.com VCard: http://bfccomputing.com/vcard/bill.vcf Social networks: bill_mcgonigle/bill.mcgonigle -- 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: control-C and yum update
On Sun, 2010-01-03 at 21:42 -0800, Paul Allen Newell wrote: While reinstalling f12 on a machine that I messed up, I was following all my notes and directions and reached the point where the install was successful and it was time to update. I did a su -l and then typed yum update. I realized I had forgotten something and immediately did a control-C in the terminal that I had executed the yum update. To my surprise, it ignored it until it got to the first confirm and then proceeded to kill the process. No problem as the update was stopped but ... I though control-C was an immediate kill of whatever was running and was wondering why yum didn't stop when I tried to kill it. In the yum updating case, it's breaking the current process (downloading some file), but not the thing controlling it. You'd need to CTRL+C more than once, to break the chain of events higher up. The first break will abort the current download, and yum will try to download the same file from another repo, as the next action. This is actually useful, for things like when you notice the download is excruciatingly slow, but you still want to do a yum update. You can simply CTRL+C to make it use another repo mirror. -- [...@localhost ~]$ uname -r 2.6.27.25-78.2.56.fc9.i686 Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- 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: control-C and yum update
On 10-01-05 03:01:45, Tim wrote: ... In the yum updating case, it's breaking the current process (downloading some file), but not the thing controlling it. You'd need to CTRL+C more than once, to break the chain of events higher up. ... No, yum is doing the download in-process. It takes two Ctrl-C's to quit during download so one can switch mirrors with one Ctrl-C. Yum is getting both of them and counting and timing them to decide what to do. The approach I took in my stablemirror yum plugin is to show a short menu of commands and let the user choose one, rather than count and time them. Either way works, but my way offers more choices. -- TonyN.:' mailto:tonynel...@georgeanelson.com ' http://www.georgeanelson.com/ -- 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: yum update question
Marko Vojinovic wrote: On Monday 04 January 2010 05:50:54 Paul Allen Newell wrote: While doing a yum update after an install from DVD, I noticed that I got the following message (this is a write it down and then retype into computer that has mail so I might have a typo: [...] Installing: kernal-PAE-2.6.31.9-174.fc12.i686 W: Possible missing firmware ql8100_fw.bin for module qla2xxx.lo W: Possible missing firmware aic94xx-seq_fw.bin for module aic94xx.lo [...] Did you also get the message like: Processing delta metadata /boot/initramfs-2.6.31.5-127.fc12.x86_64.img: contents have been changed delta does not match installed data or similar, somewhere in the early stages of the update process (before the actual installing of .rpm's)? If yes, then you have probably hit this bug: https://bugzilla.redhat.com/show_bug.cgi?id=544901 In short, those warnings are harmless and you are pretty safe to ignore them. HTH, :-) Marko Marko: Let me check the log tomorrow ... your delta doesn't match sounds familiar and, if such is the case, I will attach myself to the bugzilla you provided Thanks, Paul -- 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: yum update question
On 01/03/2010 11:50 PM, Paul Allen Newell wrote: While doing a yum update after an install from DVD, I noticed that I got the following message (this is a write it down and then retype into computer that has mail so I might have a typo: [...] Installing: kernal-PAE-2.6.31.9-174.fc12.i686 W: Possible missing firmware ql8100_fw.bin for module qla2xxx.lo W: Possible missing firmware aic94xx-seq_fw.bin for module aic94xx.lo [...] The machine is old and I am prepared to understand that it might be getting too old. But I can't figure out how I am decipher this message into something which lets me understand what f12 thinks is missing in my firmware. I checked my f11 install logs on another machine and do not see these warnings. IMHO, it would be nice if yum told me where to look to understand these messages, but MHO might be ignorant of something obvious, so I can't complain until I understand this warning. Thanks in advance, Paul See https://bugzilla.redhat.com/show_bug.cgi?id=523365 -- 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: yum update question
On Monday 04 January 2010 08:15:13 Paul Allen Newell wrote: Marko Vojinovic wrote: On Monday 04 January 2010 05:50:54 Paul Allen Newell wrote: [...] Installing: kernal-PAE-2.6.31.9-174.fc12.i686 W: Possible missing firmware ql8100_fw.bin for module qla2xxx.lo W: Possible missing firmware aic94xx-seq_fw.bin for module aic94xx.lo [...] Did you also get the message like: Processing delta metadata /boot/initramfs-2.6.31.5-127.fc12.x86_64.img: contents have been changed delta does not match installed data Let me check the log tomorrow ... your delta doesn't match sounds familiar and, if such is the case, I will attach myself to the bugzilla you provided I am not sure where is this message logged, but definitely not in yum.log, as I didn't find it there later on when I looked up again. I also don't know where those kernel warnings were logged, if at all... :-) But anyway, there is no need to attach yourself to that bugzilla, just read it to understand what is happening. There is a particular link to the codemonkeys.org website with more clearer explanation. In a nutshell, it's just deltarpm and kernel rpm confusing each other about how big the initramfs.img file should be. And it just so happens that those firmware modules happen to reside in that file, so during the kernel installation you get the warning that they might get missing. But this never happens, because the kernel has those modules already, and just needs to recreate the initramfs, which happens automatically. So nothing to worry about. ;-) Best, :-) Marko -- 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: control-C and yum update
Paul Allen Newell writes: A quick question which is hopefully just an education request ... While reinstalling f12 on a machine that I messed up, I was following all my notes and directions and reached the point where the install was successful and it was time to update. I did a su -l and then typed yum update. I realized I had forgotten something and immediately did a control-C in the terminal that I had executed the yum update. To my surprise, it ignored it until it got to the first confirm and then proceeded to kill the process. No problem as the update was stopped but ... I though control-C was an immediate kill of whatever was running and was wondering why yum didn't stop when I tried to kill it. Probably because if you interrupt packages in the middle of updating, you have an excellent chance of FUBARing your entire system. This has been a long standing problem with rpm. If you interrupt a long update, you'll end up with both the old and the new version of affected packages installed. That's always fun to clean up. Don't do that. pgpvWl9093Y1T.pgp Description: PGP signature -- 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: control-C and yum update
On Mon, 2010-01-04 at 07:14 -0500, Sam Varshavchik wrote: Paul Allen Newell writes: A quick question which is hopefully just an education request ... While reinstalling f12 on a machine that I messed up, I was following all my notes and directions and reached the point where the install was successful and it was time to update. I did a su -l and then typed yum update. I realized I had forgotten something and immediately did a control-C in the terminal that I had executed the yum update. To my surprise, it ignored it until it got to the first confirm and then proceeded to kill the process. No problem as the update was stopped but ... I though control-C was an immediate kill of whatever was running and was wondering why yum didn't stop when I tried to kill it. Probably because if you interrupt packages in the middle of updating, you have an excellent chance of FUBARing your entire system. This has been a long standing problem with rpm. If you interrupt a long update, you'll end up with both the old and the new version of affected packages installed. That's always fun to clean up. Don't do that. -- 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 I have been using Tony Nelson's stablemirror for several years (and Control/C) with yum (currently F12) with no problems. http://www.georgeanelson.com/stablemirror.htm Stablemirror provides working Ctl-C handling during downloads, in a way that I belive is safe for the underlying RPM database. John -- 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: control-C and yum update
On 04/01/2010 12:14, Sam Varshavchik wrote: Paul Allen Newell writes: A quick question which is hopefully just an education request ... While reinstalling f12 on a machine that I messed up, I was following all my notes and directions and reached the point where the install was successful and it was time to update. I did a su -l and then typed yum update. I realized I had forgotten something and immediately did a control-C in the terminal that I had executed the yum update. To my surprise, it ignored it until it got to the first confirm and then proceeded to kill the process. No problem as the update was stopped but ... I though control-C was an immediate kill of whatever was running and was wondering why yum didn't stop when I tried to kill it. Probably because if you interrupt packages in the middle of updating, you have an excellent chance of FUBARing your entire system. This has been a long standing problem with rpm. If you interrupt a long update, you'll end up with both the old and the new version of affected packages installed. That's always fun to clean up. Don't do that. You have to hit Crtl-C twice! not just the once, and within' five seconds of each other -- 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: control-C and yum update
On 10-01-04 08:12:39, John Austin wrote: ... I have been using Tony Nelson's stablemirror for several years (and Control/C) with yum (currently F12) with no problems. http://www.georgeanelson.com/stablemirror.htm Stablemirror provides working Ctl-C handling during downloads, in a way that I belive is safe for the underlying RPM database. I am /astounded/ that it hadn't stopped working with all the changes to yum since 2007. I hadn't been using it myself, as both the mirrors and yum have seen improvement over time, but I did occasionally miss it. I've installed it again and will look for any problems it might have with current yum. Anyone choosing to use stablemirror will probably want to disable fastestmirror. -- TonyN.:' mailto:tonynel...@georgeanelson.com ' http://www.georgeanelson.com/ -- 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: yum update question
Marko Vojinovic wrote: On Monday 04 January 2010 08:15:13 Paul Allen Newell wrote: Marko Vojinovic wrote: On Monday 04 January 2010 05:50:54 Paul Allen Newell wrote: [...] Installing: kernal-PAE-2.6.31.9-174.fc12.i686 W: Possible missing firmware ql8100_fw.bin for module qla2xxx.lo W: Possible missing firmware aic94xx-seq_fw.bin for module aic94xx.lo [...] Did you also get the message like: Processing delta metadata /boot/initramfs-2.6.31.5-127.fc12.x86_64.img: contents have been changed delta does not match installed data Let me check the log tomorrow ... your delta doesn't match sounds familiar and, if such is the case, I will attach myself to the bugzilla you provided I am not sure where is this message logged, but definitely not in yum.log, as I didn't find it there later on when I looked up again. I also don't know where those kernel warnings were logged, if at all... :-) But anyway, there is no need to attach yourself to that bugzilla, just read it to understand what is happening. There is a particular link to the codemonkeys.org website with more clearer explanation. In a nutshell, it's just deltarpm and kernel rpm confusing each other about how big the initramfs.img file should be. And it just so happens that those firmware modules happen to reside in that file, so during the kernel installation you get the warning that they might get missing. But this never happens, because the kernel has those modules already, and just needs to recreate the initramfs, which happens automatically. So nothing to worry about. ;-) Best, :-) Marko Marko: I capture and save a cut-and-paste of screen output of most yum updates I do, so I checked and the delta message is there. Appreciate the additional message ... as I was reading through it I remember having seen a prior post on such. Not certain why it didn't click at the time, maybe it was because I remember something about don't need to worry and therefore it didn't stick. As you suggest, I will blaze ahead and not worry (though I will attach myself to the bug #544901 so I am aware when it is resolved) Thanks again, Paul -- 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: yum update question
s wrote: On 01/03/2010 11:50 PM, Paul Allen Newell wrote: While doing a yum update after an install from DVD, I noticed that I got the following message (this is a write it down and then retype into computer that has mail so I might have a typo: [...] Installing: kernal-PAE-2.6.31.9-174.fc12.i686 W: Possible missing firmware ql8100_fw.bin for module qla2xxx.lo W: Possible missing firmware aic94xx-seq_fw.bin for module aic94xx.lo [...] The machine is old and I am prepared to understand that it might be getting too old. But I can't figure out how I am decipher this message into something which lets me understand what f12 thinks is missing in my firmware. I checked my f11 install logs on another machine and do not see these warnings. IMHO, it would be nice if yum told me where to look to understand these messages, but MHO might be ignorant of something obvious, so I can't complain until I understand this warning. Thanks in advance, Paul See https://bugzilla.redhat.com/show_bug.cgi?id=523365 s: Oh yeah, that is definitely it ... thanks for the bug id # Paul -- 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
control-C and yum update
A quick question which is hopefully just an education request ... While reinstalling f12 on a machine that I messed up, I was following all my notes and directions and reached the point where the install was successful and it was time to update. I did a su -l and then typed yum update. I realized I had forgotten something and immediately did a control-C in the terminal that I had executed the yum update. To my surprise, it ignored it until it got to the first confirm and then proceeded to kill the process. No problem as the update was stopped but ... I though control-C was an immediate kill of whatever was running and was wondering why yum didn't stop when I tried to kill it. Am I missing something about either control-C or yum update .. or both? Thanks in advance for any explanation as I am wondering if I really understand control-C Paul -- 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
yum update question
While doing a yum update after an install from DVD, I noticed that I got the following message (this is a write it down and then retype into computer that has mail so I might have a typo: [...] Installing: kernal-PAE-2.6.31.9-174.fc12.i686 W: Possible missing firmware ql8100_fw.bin for module qla2xxx.lo W: Possible missing firmware aic94xx-seq_fw.bin for module aic94xx.lo [...] The machine is old and I am prepared to understand that it might be getting too old. But I can't figure out how I am decipher this message into something which lets me understand what f12 thinks is missing in my firmware. I checked my f11 install logs on another machine and do not see these warnings. IMHO, it would be nice if yum told me where to look to understand these messages, but MHO might be ignorant of something obvious, so I can't complain until I understand this warning. Thanks in advance, Paul -- 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: control-C and yum update
2010/1/4 Paul Allen Newell pnew...@cs.cmu.edu: I though control-C was an immediate kill of whatever was running and was wondering why yum didn't stop when I tried to kill it. It's an interrupt, which could be blocked or it might be on a different queue. You should be able to background yum and kill it straight away: Ctrl+z kill %1 -c -- 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: control-C and yum update
Chris Smart wrote: 2010/1/4 Paul Allen Newell pnew...@cs.cmu.edu: I though control-C was an immediate kill of whatever was running and was wondering why yum didn't stop when I tried to kill it. It's an interrupt, which could be blocked or it might be on a different queue. You should be able to background yum and kill it straight away: Ctrl+z kill %1 -c Chris: Got it ... this makes sense as there are jobs I run that I have to ps and then kill. If yum blocks until first y/N, it makes sense. Thanks, Paul -- 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: yum update question
On Monday 04 January 2010 05:50:54 Paul Allen Newell wrote: While doing a yum update after an install from DVD, I noticed that I got the following message (this is a write it down and then retype into computer that has mail so I might have a typo: [...] Installing: kernal-PAE-2.6.31.9-174.fc12.i686 W: Possible missing firmware ql8100_fw.bin for module qla2xxx.lo W: Possible missing firmware aic94xx-seq_fw.bin for module aic94xx.lo [...] Did you also get the message like: Processing delta metadata /boot/initramfs-2.6.31.5-127.fc12.x86_64.img: contents have been changed delta does not match installed data or similar, somewhere in the early stages of the update process (before the actual installing of .rpm's)? If yes, then you have probably hit this bug: https://bugzilla.redhat.com/show_bug.cgi?id=544901 In short, those warnings are harmless and you are pretty safe to ignore them. HTH, :-) Marko -- 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
i386 yum update download stops: updates/filelists_db
Trying to do a yum makecache on my fedora 12 i386 machine and it starts downloading updates/filelists_db and the download rate gets slower and slower, from 100s of KBs/second to KBs to 100s of B/s to Bytes/seccond to 0 B/s - basically stopping. I can Control-C to restart but the same happens again. After a couple of Control-C's it switches mirrors but it still happens. Whats up? Thanks. Richard -- 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: i386 yum update download stops: updates/filelists_db
On Wed, Dec 30, 2009 at 1:28 PM, Rich Emberson emberson.r...@gmail.comwrote: Trying to do a yum makecache on my fedora 12 i386 machine and it starts downloading updates/filelists_db and the download rate gets slower and slower, from 100s of KBs/second to KBs to 100s of B/s to Bytes/seccond to 0 B/s - basically stopping. I can Control-C to restart but the same happens again. After a couple of Control-C's it switches mirrors but it still happens. Whats up? Just for giggles, try turning off iptables (#service iptables stop). There's some rule in the default iptables that causes FTP downloads to crawl after a while. It's bitten me before doing FTP software fetches and it's possible that one or more of the repos you have uses FTP. I've never had the time to figure out which iptables rule is causing the issue, I just disable iptables, fetch stuff and turn iptables back on. Perhaps when I'm not so busy... -- Rick Stevens, Nerd Manifique -- 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: i386 yum update download stops: updates/filelists_db
--- On Wed, 12/30/09, Rich Emberson emberson.r...@gmail.com wrote: Trying to do a yum makecache on my fedora 12 i386 machine and it starts downloading updates/filelists_db and the download rate gets slower and slower, from 100s of KBs/second to KBs to 100s of B/s to Bytes/seccond to 0 B/s - basically stopping. I can Control-C to restart but the same happens again. After a couple of Control-C's it switches mirrors but it still happens. Whats up? I got the same behavior with just a normal yum update on my 64-bit system. Solved it with: yum install yum-plugin-fastestmirror. Also check to see if you have yum-presto installed, too. This link will help. http://www.mjmwired.net/resources/mjm-fedora-f12.html#yum B -- 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
Yum command
FC12/KDE How would I do a yum command to enablerepo=updates-testing to update python. I did it this way but it won't work. yum update --enablerepo=updates-testing python -- 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: Yum command
On 12/19/2009 08:51 PM, Jim wrote: FC12/KDE How would I do a yum command to enablerepo=updates-testing to update python. I did it this way but it won't work. yum update --enablerepo=updates-testing python Its working here in F11 [r...@mybox ~]# yum update --enablerepo=updates-testing python Loaded plugins: presto, refresh-packagekit google-chrome | 951 B 00:00 updates-testing/metalink | 4.5 kB 00:00 updates-testing | 4.4 kB 00:00 updates-testing/primary_db | 747 kB 00:04 Setting up Update Process Resolving Dependencies -- Running transaction check yum --version 3.2.24 -- Saurabh Sharma Linux user number: 490644 http://sawrub-blog.blogspot.com/ Open your doors...It's time to look beyond Windows -- 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: Yum command
Jim wrote: FC12/KDE How would I do a yum command to enablerepo=updates-testing to update python. I did it this way but it won't work. yum update --enablerepo=updates-testing python You should give options (--enablerepo) _before the command (update). The yum man page and help output say: Usage: yum [options] COMMAND So you want: yum --enablerepo=updates-testing update python -- ToddOpenPGP - KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ Man was made at the end of the week's work when God was tired. -- Mark Twain pgpE2QDZF6Xpt.pgp Description: PGP signature -- 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: Yum command
Jim wrote: FC12/KDE How would I do a yum command to enablerepo=updates-testing to update python. I did it this way but it won't work. yum update --enablerepo=updates-testing python It should be: yum --enablerepo=updates-testing _update_ python -- 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
yum-presto behaviour on arm
Hi - Is yum-presto known to work on arm? Today I changed our repo to use deltarpms and tested it out. I noticed... 1) On a package where I know the bulk of the unpacked data is some fonts inside an ELF executable that didn't change, the compression result was... not good Old RPM: 25424385 txtr-reader-0.1-417.fc11.armv5tel.rpm New RPM: 25465487 txtr-reader-0.1-420.fc11.armv5tel.rpm Delta RPM: 25465402 txtr-reader-0.1-417.fc11_0.1-420.fc11.armv5tel.drpm So it saved me 85 bytes from 25MByte :-) The actual procedure here is the createrepo is run on an x86_64 box over these arm packages and then rsync'd on a server. 2) Using deltarpms fails Loaded plugins: presto Setting up Update Process Resolving Dependencies There are unfinished transactions remaining. You might consider running yum-complete-transaction first to finish them. -- Running transaction check --- Package txtr-reader.armv5tel 0:0.1-420.fc11 set to be updated -- Finished Dependency Resolution Dependencies Resolved PackageArchVersion Repository Size Updating: txtr-readerarmv5tel0.1-420.fc11txtradevel 24 M Transaction Summary Install 0 Package(s) Update 1 Package(s) Remove 0 Package(s) Total download size: 24 M Downloading Packages: Setting up and reading Presto delta metadata Downloading DeltaRPMs: Rebuilding rpms from deltarpms /var/cache/yum/txtradevel/deltas/txtr-reader-0.1-417.fc11_0.1-420.fc11.armv5tel.drpm: md5 mismatch of result Error rebuilding rpm from txtr-reader-0.1-417.fc11_0.1-420.fc11.armv5tel.drpm! Will download full package. Running rpm_check_debug Running Transaction Test Finished Transaction Test Transaction Test Succeeded Running Transaction Updating : txtr-reader 1/2 Cleanup: txtr-reader 2/2 Updated: txtr-reader.armv5tel 0:0.1-420.fc11 Complete! Any advice welcomed, it would be great to reduce this 25MByte package down since the vast bulk of it is exactly the same each time :-) -Andy -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: yum-presto behaviour on arm
On Wed, 2009-12-16 at 14:06 +, Andy Green wrote: Hi - Is yum-presto known to work on arm? Today I changed our repo to use deltarpms and tested it out. I noticed... 1) On a package where I know the bulk of the unpacked data is some fonts inside an ELF executable that didn't change, the compression result was... not good Old RPM: 25424385 txtr-reader-0.1-417.fc11.armv5tel.rpm New RPM: 25465487 txtr-reader-0.1-420.fc11.armv5tel.rpm Delta RPM: 25465402 txtr-reader-0.1-417.fc11_0.1-420.fc11.armv5tel.drpm So it saved me 85 bytes from 25MByte :-) The actual procedure here is the createrepo is run on an x86_64 box over these arm packages and then rsync'd on a server. 2) Using deltarpms fails snip Any advice welcomed, it would be great to reduce this 25MByte package down since the vast bulk of it is exactly the same each time :-) -Andy If you can get me ssh access to an arm machine, I'll look into both of these problems. Please also open a bug against deltarpm (otherwise, I'll totally forget about this). Jonathan signature.asc Description: This is a digitally signed message part -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: yum-presto behaviour on arm
On 12/16/09 14:12, Somebody in the thread at some point said: Hi - Is yum-presto known to work on arm? Today I changed our repo to use deltarpms and tested it out. I noticed... If you can get me ssh access to an arm machine, I'll look into both of these problems. Please also open a bug against deltarpm (otherwise, I'll totally forget about this). Thanks for the quick reply... I will see about setting something up and get back to you. https://bugzilla.redhat.com/show_bug.cgi?id=548068 -Andy -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: yum install mencoder makes X11 flaky
On Sat, 2009-12-12 at 00:24 +0530, Rahul Sundaram wrote: On 12/11/2009 11:08 PM, Kelly Jones wrote: Ever since I yum install mencoder, my X server's been flaky + frequently crashing. I remember yum installing/upgrading libraries when I ran the command above, but don't remember what the libraries were. How do I find out what yum installed/upgraded, and remove it so my X server behaves properly again? # yum history list # yum history info id number # yum history undo id number Are you sure? I would like this info to post my troubles with sunbird (forthcoming shortly), but # yum history list produces only the usage message. System is F11 with all upgrades. Yum is yum-3.2.24-2.fc11.noarch . Thanks - jon -- 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: yum install mencoder makes X11 flaky
On Wednesday 16 December 2009 12:22 AM, Jonathan Ryshpan wrote: On Sat, 2009-12-12 at 00:24 +0530, Rahul Sundaram wrote: On 12/11/2009 11:08 PM, Kelly Jones wrote: Ever since I yum install mencoder, my X server's been flaky + frequently crashing. I remember yum installing/upgrading libraries when I ran the command above, but don't remember what the libraries were. How do I find out what yum installed/upgraded, and remove it so my X server behaves properly again? # yum history list # yum history infoid number # yum history undoid number Are you sure? I would like this info to post my troubles with sunbird (forthcoming shortly), but # yum history list produces only the usage message. System is F11 with all upgrades. Yum is yum-3.2.24-2.fc11.noarch . Same here, are you using any plugins? It would be an awesome plugin to have though. :) Thanks - jon -- Suvayu Open source is the future. It sets us free. -- 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: yum install mencoder makes X11 flaky
2009/12/16 Jonathan Ryshpan jonr...@pacbell.net: Are you sure? I would like this info to post my troubles with sunbird (forthcoming shortly), but # yum history list produces only the usage message. System is F11 with all upgrades. Yum is yum-3.2.24-2.fc11.noarch . Might be only on F12. Works for me with yum-3.2.25-1.fc12.noarch. -- Regards, Derek -- 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: yum install mencoder makes X11 flaky
On Wed, 2009-12-16 at 00:22 -0800, Jonathan Ryshpan wrote: On Sat, 2009-12-12 at 00:24 +0530, Rahul Sundaram wrote: On 12/11/2009 11:08 PM, Kelly Jones wrote: Ever since I yum install mencoder, my X server's been flaky + frequently crashing. I remember yum installing/upgrading libraries when I ran the command above, but don't remember what the libraries were. How do I find out what yum installed/upgraded, and remove it so my X server behaves properly again? # yum history list # yum history info id number # yum history undo id number Are you sure? I would like this info to post my troubles with sunbird (forthcoming shortly), but # yum history list produces only the usage message. System is F11 with all upgrades. Yum is yum-3.2.24-2.fc11.noarch . Thanks - jon less /var/log/yum.log 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
Yum Cannot retrieve repository metadata error
Hi all, Since my latest rawhide update, performed on Dec 12 (with --skip-broken enabled because of some broken dependencies and a certain laziness on my side), my yum is giving me the following error: Loaded plugins: presto Error: Cannot retrieve repository metadata (repomd.xml) for repository: rawhide. Please verify its path and try again Here's a list of packages which got updated: http://berkenpies.nl/yum.log I'd be more than happy to manually downgrade some packages but does someone have any clue on which package could be causing this? On a side note, yum was also complaining about /var/cache/yum/i386/13/rpmdb-cache which didn't exist. To get rid of this one, I manually created the directory. -- With kind regards / Met vriendelijke groet, Eelko Berkenpies http://blog.berkenpies.nl/ -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Yum Cannot retrieve repository metadata error
I have the same problem. This is what i do to solve it. edit /etc/hosts, add the following hosts 80.239.156.215 mirrors.fedoraproject.org 152.46.7.222download.fedoraproject.org 209.132.183.67 download.fedora.redhat.com use baseurl instead of mirrorlist repos. BUT, when upgrade complete, i can not reboot or bootup On Tue, 2009-12-15 at 09:00 +0100, Eelko Berkenpies wrote: Hi all, Since my latest rawhide update, performed on Dec 12 (with --skip-broken enabled because of some broken dependencies and a certain laziness on my side), my yum is giving me the following error: Loaded plugins: presto Error: Cannot retrieve repository metadata (repomd.xml) for repository: rawhide. Please verify its path and try again Here's a list of packages which got updated: http://berkenpies.nl/yum.log I'd be more than happy to manually downgrade some packages but does someone have any clue on which package could be causing this? On a side note, yum was also complaining about /var/cache/yum/i386/13/rpmdb-cache which didn't exist. To get rid of this one, I manually created the directory. -- With kind regards / Met vriendelijke groet, Eelko Berkenpies http://blog.berkenpies.nl/ -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Yum Cannot retrieve repository metadata error
On Tue, Dec 15, 2009 at 10:32 AM, phenix dalinhu...@gmail.com wrote: I have the same problem. This is what i do to solve it. edit /etc/hosts, add the following hosts 80.239.156.215 mirrors.fedoraproject.org 152.46.7.222 download.fedoraproject.org 209.132.183.67 download.fedora.redhat.com use baseurl instead of mirrorlist repos. Thanks, that did the trick for me. Problem solved, I guess. :) -- With kind regards / Met vriendelijke groet, Eelko Berkenpies http://blog.berkenpies.nl/ -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Yum Cannot retrieve repository metadata error
On Tue, Dec 15, 2009 at 05:32:43PM +0800, phenix wrote: I have the same problem. This is what i do to solve it. edit /etc/hosts, add the following hosts 80.239.156.215 mirrors.fedoraproject.org 152.46.7.222download.fedoraproject.org 209.132.183.67 download.fedora.redhat.com use baseurl instead of mirrorlist repos. We've had some problems with DNS during the Fedora Infrastructure move, but these should be resolved now, eliminating the need to edit /etc/hosts or the yum .repo files. If you find you still have problems, please file a ticket with Fedora Infrastructure. https://fedorahosted.org/fedora-infrastructure/ Thanks, Matt -- Matt Domsch Technology Strategist, Dell Office of the CTO linux.dell.com www.dell.com/linux -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Yum Cannot retrieve repository metadata error
I have this problem too. I believe the problem is in libcurl 7.19.7-8.fc13. If I downgrade to curl/libcurl 7.19.6-10.fc12 the problem goes away. If I run from a command line: $ curl 'https://mirrors.fedoraproject.org/metalink?repo=rawhidearch=i386' I now get: curl: (7) Failed to connect to 2610:28:200:1::fed0:2: Network is unreachable despite the fact that IPv6 is disabled. The ifcfg script includes IPV6INIT=no. $ ifconfig eth1 Link encap:Ethernet HWaddr 00:0C:29:38:C9:7E inet addr:10.117.25.148 Bcast:10.117.25.255 Mask:255.255.255.0 inet6 addr: fe80::20c:29ff:fe38:c97e/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1184 errors:0 dropped:0 overruns:0 frame:0 TX packets:1487 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:541164 (528.4 KiB) TX bytes:137185 (133.9 KiB) Interrupt:19 Base address:0x10a4 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:40 errors:0 dropped:0 overruns:0 frame:0 TX packets:40 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2000 (1.9 KiB) TX bytes:2000 (1.9 KiB) My understanding is that Scope:Link means that is it can not be used for internet access. All other networking appears normal and works okay. -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Strange error with yum update
Christoph Wickert wrote on 12.12.2009 23:41: Am Samstag, den 12.12.2009, 22:10 + schrieb John Lagrue: At first glance this look simple, but it seems to be telling me there's an error. Running rpm_check_debug ERROR with rpm_check_debug vs depsolve: kernel-uname-r = 2.6.30.9-96.fc11.i686.PAE is needed by (installed) kmod-nvidia-2.6.30.9-96.fc11.i686.PAE-190.42-1.fc11.1.i686 Complete! (1, [u'Please report this error in http://yum.baseurl.org/report']) Anyone got any idea of what's wrong? No -- I'd need more output from yum to see what's wrong. There is a new kernel out but the kmod for it is not yet available at rpmfusion. That's not the case from what I can see. And the -102 kmod are in the repos since a few days already. Seems a local, already installed package is the troublemaker here for some strange reason :-/ CU knurd -- 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: Strange error with yum update
what kernel do you use? I think you have kmod-nvidia rpm for kernel 2.6.30.9-96.fc11.i686.PAE but dont have that kernel itself installed -- Terminal je t'aime . I love you terminal Bella Mia. -- 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
Problems updating - YUM - kmod-VirtualBox...
# yum --skip-broken update ... gnome-keyring-sharp i686 1.0.1-0.5.133722svn.fc12 fedora 20 k kmod-nvidia-173xx-2.6.31.6-166.fc12.i686.PAE i686 173.14.22-1.fc12.4 rpmfusion-nonfree-updates 1.8 M Removendo para as dependências: kmod-VirtualBox-OSE-2.6.31.5-127.fc12.i686.PAE i686 3.0.10-1.fc12.4 installed 393 k kmod-nvidia-173xx-2.6.31.5-127.fc12.i686.PAE i686 173.14.22-1.fc12 installed 7.5 M Resumo da transação Instalar 4 Pacote(s) Atualizar 53 Pacote(s) Remover4 Pacote(s) Reinstalar 0 Pacote(s) Desatualizar 0 Pacote(s) Tamanho total: 106 M Correto? [s/N]:s Baixando pacotes: Executando o rpm_check_debug Erro com o rpm_check_debug vs depsolve: kernel-uname-r = 2.6.30.9-96.fc11.i686.PAE is needed by (installed) kmod-VirtualBox-OSE-2.6.30.9-96.fc11.i686.PAE-3.0.10-1.fc11.3.i686 kernel-uname-r = 2.6.30.8-64.fc11.i686.PAE is needed by (installed) kmod-VirtualBox-OSE-2.6.30.8-64.fc11.i686.PAE-3.0.8-1.fc11.i686 kernel-uname-r = 2.6.30.9-90.fc11.i686.PAE is needed by (installed) kmod-VirtualBox-OSE-2.6.30.9-90.fc11.i686.PAE-3.0.10-1.fc11.i686 Concluído! -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Strange error with yum update
At first glance this look simple, but it seems to be telling me there's an error. Running rpm_check_debug ERROR with rpm_check_debug vs depsolve: kernel-uname-r = 2.6.30.9-96.fc11.i686.PAE is needed by (installed) kmod-nvidia-2.6.30.9-96.fc11.i686.PAE-190.42-1.fc11.1.i686 Complete! (1, [u'Please report this error in http://yum.baseurl.org/report']) Anyone got any idea of what's wrong? JDL -- 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: Strange error with yum update
Am Samstag, den 12.12.2009, 22:10 + schrieb John Lagrue: At first glance this look simple, but it seems to be telling me there's an error. Running rpm_check_debug ERROR with rpm_check_debug vs depsolve: kernel-uname-r = 2.6.30.9-96.fc11.i686.PAE is needed by (installed) kmod-nvidia-2.6.30.9-96.fc11.i686.PAE-190.42-1.fc11.1.i686 Complete! (1, [u'Please report this error in http://yum.baseurl.org/report']) Anyone got any idea of what's wrong? There is a new kernel out but the kmod for it is not yet available at rpmfusion. Ether wait 1 or 2 days ot use the akmod. JDL Regards, Christoph -- 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
yum install mencoder makes X11 flaky
Ever since I yum install mencoder, my X server's been flaky + frequently crashing. I remember yum installing/upgrading libraries when I ran the command above, but don't remember what the libraries were. How do I find out what yum installed/upgraded, and remove it so my X server behaves properly again? -- We're just a Bunch Of Regular Guys, a collective group that's trying to understand and assimilate technology. We feel that resistance to new ideas and technology is unwise and ultimately futile. -- 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: yum install mencoder makes X11 flaky
On Fri, 2009-12-11 at 11:38 -0600, Kelly Jones wrote: How do I find out what yum installed/upgraded, and remove it so my X server behaves properly again? less /var/log/yum.log -- MELVILLE THEATRE ~ Melville Sask ~ http://www.melvilletheatre.com -- 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: yum install mencoder makes X11 flaky
On 12/11/2009 11:08 PM, Kelly Jones wrote: Ever since I yum install mencoder, my X server's been flaky + frequently crashing. I remember yum installing/upgrading libraries when I ran the command above, but don't remember what the libraries were. How do I find out what yum installed/upgraded, and remove it so my X server behaves properly again? # yum history list # yum history info id number # yum history undo id number 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
yum doesn't like installonly_limit=1?
I changed the installonly_limit to 1 from the default value 3 in
/etc/yum.conf, and yum blows up.
# yum search boinc
Loaded plugins: presto, refresh-packagekit
Options Error: Error parsing '1': out of range integer value
PackageKit gave me a better traceback:
Traceback (most recent call last):
File /usr/share/PackageKit/helpers/yum/yumBackend.py, line 2956, in __init__
self.repos.confirm_func = self._repo_gpg_confirm
File /usr/lib/python2.6/site-packages/yum/__init__.py, line 717, in lambda
repos = property(fget=lambda self: self._getRepos(),
File /usr/lib/python2.6/site-packages/yum/__init__.py, line 496,
in _getRepos
self.conf # touch the config class first
File /usr/lib/python2.6/site-packages/yum/__init__.py, line 723, in lambda
conf = property(fget=lambda self: self._getConfig(),
File /usr/lib/python2.6/site-packages/yum/__init__.py, line 276,
in _getConfig
self._conf = config.readMainConfig(startupconf)
File /usr/lib/python2.6/site-packages/yum/config.py, line 827, in
readMainConfig
yumconf.populate(startupconf._parser, 'main')
File /usr/lib/python2.6/site-packages/yum/config.py, line 505, in populate
setattr(self, name, value)
File /usr/lib/python2.6/site-packages/yum/config.py, line 94, in __set__
raise ValueError('Error parsing $r: $s' $ (value, str(e)))
ValueError: Error parsing '1': out of range integer value
I changed the value to 0, 2, 3 etc, all of them resulting in a working
yum environment. Is it a known issue, or worth filing a bug?
Yum version is yum-3.2.25-1.fc12.noarch
--
Cheers,
Rajeesh
http://rajeeshknambiar.wordpress.com
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: yum doesn't like installonly_limit=1?
On Thu, 2009-12-10 at 18:00 +0530, Rajeesh K Nambiar wrote: I changed the installonly_limit to 1 from the default value 3 in /etc/yum.conf, and yum blows up. # yum search boinc Loaded plugins: presto, refresh-packagekit Options Error: Error parsing '1': out of range integer value This is an error message, not what I'd usually term blows up. PackageKit gave me a better traceback: This is just more text to say the same thing, 1 is an invalid argument. I changed the value to 0, 2, 3 etc, all of them resulting in a working yum environment. Is it a known issue, or worth filing a bug? Yum version is yum-3.2.25-1.fc12.noarch Maybe3 a better question is: What do you want to achieve by setting this value to 1? -- James Antill - ja...@fedoraproject.org http://yum.baseurl.org/wiki/releases http://yum.baseurl.org/wiki/whatsnew/3.2.25 http://yum.baseurl.org/wiki/YumMultipleMachineCaching -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: yum doesn't like installonly_limit=1?
On 12/10/09, James Antill ja...@fedoraproject.org wrote: On Thu, 2009-12-10 at 18:00 +0530, Rajeesh K Nambiar wrote: I changed the installonly_limit to 1 from the default value 3 in /etc/yum.conf, and yum blows up. # yum search boinc Loaded plugins: presto, refresh-packagekit Options Error: Error parsing '1': out of range integer value This is an error message, not what I'd usually term blows up. I mean - can't install anything, can't search a package. It took me a while to realize that the change made to the config file caused it as I tried to use yum again after couple of days. PackageKit gave me a better traceback: This is just more text to say the same thing, 1 is an invalid argument. I changed the value to 0, 2, 3 etc, all of them resulting in a working yum environment. Is it a known issue, or worth filing a bug? Yum version is yum-3.2.25-1.fc12.noarch Maybe3 a better question is: What do you want to achieve by setting this value to 1? Ah, I realize that it would have the same effect as installonly_limit=0 ? -- James Antill - ja...@fedoraproject.org http://yum.baseurl.org/wiki/releases http://yum.baseurl.org/wiki/whatsnew/3.2.25 http://yum.baseurl.org/wiki/YumMultipleMachineCaching -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list -- Cheers, Rajeesh http://rajeeshknambiar.wordpress.com -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: yum doesn't like installonly_limit=1?
On Thu, 10 Dec 2009, Rajeesh K Nambiar wrote: On 12/10/09, James Antill ja...@fedoraproject.org wrote: On Thu, 2009-12-10 at 18:00 +0530, Rajeesh K Nambiar wrote: I changed the installonly_limit to 1 from the default value 3 in /etc/yum.conf, and yum blows up. # yum search boinc Loaded plugins: presto, refresh-packagekit Options Error: Error parsing '1': out of range integer value This is an error message, not what I'd usually term blows up. I mean - can't install anything, can't search a package. It took me a while to realize that the change made to the config file caused it as I tried to use yum again after couple of days. The message should include what option is not able to be parsed. I'll fix it up. thanks, -sv -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: yum doesn't like installonly_limit=1?
On Thu, 2009-12-10 at 20:45 +0530, Rajeesh K Nambiar wrote: On 12/10/09, James Antill ja...@fedoraproject.org wrote: On Thu, 2009-12-10 at 18:00 +0530, Rajeesh K Nambiar wrote: I changed the installonly_limit to 1 from the default value 3 in /etc/yum.conf, and yum blows up. # yum search boinc Loaded plugins: presto, refresh-packagekit Options Error: Error parsing '1': out of range integer value This is an error message, not what I'd usually term blows up. I mean - can't install anything, can't search a package. It took me a while to realize that the change made to the config file caused it as I tried to use yum again after couple of days. Fair enough, as Seth said we should probably tell you want option is the problem :). What do you want to achieve by setting this value to 1? Ah, I realize that it would have the same effect as installonly_limit=0 ? No, 0 is special and means the same thing as off. 1 would make it act like a normal package (old version removed as new version is installed) ... except the kernel package doesn't work if you do that, so we just disallow it. -- James Antill - ja...@fedoraproject.org http://yum.baseurl.org/wiki/releases http://yum.baseurl.org/wiki/whatsnew/3.2.25 http://yum.baseurl.org/wiki/YumMultipleMachineCaching -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: yum doesn't like installonly_limit=1?
On Thu, Dec 10, 2009 at 9:22 PM, James Antill ja...@fedoraproject.org wrote: On Thu, 2009-12-10 at 20:45 +0530, Rajeesh K Nambiar wrote: On 12/10/09, James Antill ja...@fedoraproject.org wrote: On Thu, 2009-12-10 at 18:00 +0530, Rajeesh K Nambiar wrote: I changed the installonly_limit to 1 from the default value 3 in /etc/yum.conf, and yum blows up. # yum search boinc Loaded plugins: presto, refresh-packagekit Options Error: Error parsing '1': out of range integer value This is an error message, not what I'd usually term blows up. I mean - can't install anything, can't search a package. It took me a while to realize that the change made to the config file caused it as I tried to use yum again after couple of days. Fair enough, as Seth said we should probably tell you want option is the problem :). What do you want to achieve by setting this value to 1? Ah, I realize that it would have the same effect as installonly_limit=0 ? No, 0 is special and means the same thing as off. 1 would make it act like a normal package (old version removed as new version is installed) ... except the kernel package doesn't work if you do that, so we just disallow it. Yeah, that was the intention ;-) Thanks for the answers! -- James Antill - ja...@fedoraproject.org http://yum.baseurl.org/wiki/releases http://yum.baseurl.org/wiki/whatsnew/3.2.25 http://yum.baseurl.org/wiki/YumMultipleMachineCaching -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list -- Cheers, Rajeesh http://rajeeshknambiar.wordpress.com -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: yum download estimates and stalls
On Wed, 9 Dec 2009, Richard W.M. Jones wrote: I don't want to make unfair comparisons to the famous bug in Windows Vista[1], but it seems as if when a yum download stalls, then the estimates can start to look a little large: rawhide/primar 20% [- ] 0.0 B/s | 2.5 MB 2046434610655583470384211558:24 ETA What ver of python-urlgrabber do you have installed? And there is a patch posted I've not merged yet, mainly b/c I was out of the world for the weekend. -sv -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: yum download estimates and stalls
On Wed, Dec 09, 2009 at 12:20:12PM -0500, Seth Vidal wrote: On Wed, 9 Dec 2009, Richard W.M. Jones wrote: I don't want to make unfair comparisons to the famous bug in Windows Vista[1], but it seems as if when a yum download stalls, then the estimates can start to look a little large: rawhide/primar 20% [- ] 0.0 B/s | 2.5 MB 2046434610655583470384211558:24 ETA What ver of python-urlgrabber do you have installed? python-urlgrabber-3.9.1-4.fc12.noarch Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://et.redhat.com/~rjones/virt-top -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
[Bug 507294] [RFE] Allow wildcards/regexps in yum install/upgrade/comps...
Please do not reply directly to this email. All additional comments should be made in the comments box of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=507294 Juan P. Daza P. tcpip4...@gmail.com changed: What|Removed |Added Keywords||FutureFeature, Triaged CC||tcpip4...@gmail.com -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. ___ Fedora-fonts-bugs-list mailing list Fedora-fonts-bugs-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-fonts-bugs-list
yum lockup at Running Transaction
FC12/KDE Yum is hanging up at Running Transaction , how do I correct this problem. Downloading Packages: Setting up and reading Presto delta metadata Processing delta metadata Package(s) data still to download: 9.0 M (1/8): keyutils-libs-devel-1.2-6.fc12.x86_64.rpm| 29 kB 00:00 (2/8): krb5-devel-1.7-10.fc12.x86_64.rpm| 1.0 MB 00:04 (3/8): libcom_err-devel-1.41.9-5.fc12.x86_64.rpm| 35 kB 00:00 (4/8): libselinux-devel-2.0.87-1.fc12.x86_64.rpm| 126 kB 00:00 (5/8): libsepol-devel-2.0.38-1.fc12.x86_64.rpm | 61 kB 00:00 (6/8): mysql-devel-5.1.39-4.fc12.x86_64.rpm | 2.4 MB 00:12 (7/8): mysql-test-5.1.39-4.fc12.x86_64.rpm | 4.2 MB 00:13 (8/8): openssl-devel-1.0.0-0.13.beta4.fc12.x86_64.rpm | 1.2 MB 00:04 --- Total 246 kB/s | 9.0 MB 00:37 Running rpm_check_debug Running Transaction Test Finished Transaction Test Transaction Test Succeeded Running Transaction -- 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
Weird yum remove *.*86
Notice how it tries to remove the 64 bit usbutils. This does not happen with 'yum remove *.i586' (it's identical except for that 1 package) [r...@fedz ~]# yum remove *.*86 Loaded plugins: presto Setting up Remove Process Resolving Dependencies -- Running transaction check --- Package alsa-lib.i686 0:1.0.21-3.fc12 set to be erased --- Package cyrus-sasl-lib.i686 0:2.1.23-4.fc12 set to be erased --- Package db4.i686 0:4.7.25-13.fc12 set to be erased --- Package dbus-libs.i686 1:1.2.16-8.fc12 set to be erased --- Package expat.i686 0:2.0.1-7 set to be erased --- Package flac.i686 0:1.2.1-6.fc12 set to be erased --- Package freetype.i686 0:2.3.9-6.fc12 set to be erased --- Package glibc.i686 0:2.11-2 set to be erased --- Package jack-audio-connection-kit.i686 0:0.118.0-1.fc12 set to be erased --- Package keyutils-libs.i686 0:1.2-6.fc12 set to be erased --- Package krb5-libs.i686 0:1.7-8.fc12 set to be erased --- Package lcms-libs.i686 0:1.18-3.fc12 set to be erased --- Package libICE.i686 0:1.0.6-1.fc12 set to be erased --- Package libSM.i686 0:1.1.0-7.fc12 set to be erased --- Package libX11.i686 0:1.3-1.fc12 set to be erased --- Package libXau.i686 0:1.0.5-1.fc12 set to be erased --- Package libXdamage.i686 0:1.1.2-1.fc12 set to be erased --- Package libXext.i686 0:1.1-1.fc12 set to be erased --- Package libXfixes.i686 0:4.0.4-1.fc12 set to be erased --- Package libXi.i686 0:1.3-1.fc12 set to be erased --- Package libXrender.i686 0:0.9.5-1.fc12 set to be erased --- Package libXtst.i686 0:1.0.99.2-3.fc12 set to be erased --- Package libXxf86vm.i686 0:1.1.0-1.fc12 set to be erased --- Package libasyncns.i686 0:0.8-1.fc12 set to be erased --- Package libattr.i686 0:2.4.43-4.fc12 set to be erased --- Package libavc1394.i686 0:0.5.3-9.fc12 set to be erased --- Package libcap.i686 0:2.16-5.fc12 set to be erased --- Package libcap-ng.i686 0:0.6.2-3.fc12 set to be erased --- Package libcom_err.i686 0:1.41.9-5.fc12 set to be erased --- Package libdrm.i686 0:2.4.15-4.fc12 set to be erased --- Package libexif.i686 0:0.6.16-4.fc12 set to be erased --- Package libfreebob.i686 0:1.0.11-6.fc12 set to be erased --- Package libgcc.i686 0:4.4.2-7.fc12 set to be erased --- Package libgphoto2.i686 0:2.4.7-2.fc12 set to be erased --- Package libiec61883.i686 0:1.2.0-3.fc12 set to be erased --- Package libjpeg.i686 0:6b-46.fc12 set to be erased --- Package libogg.i686 2:1.1.4-2.fc12 set to be erased --- Package libraw1394.i686 0:2.0.4-1.fc12 set to be erased --- Package libselinux.i686 0:2.0.87-1.fc12 set to be erased --- Package libstdc++.i686 0:4.4.2-7.fc12 set to be erased --- Package libtool-ltdl.i686 0:2.2.6-15.fc12 set to be erased --- Package libusb.i686 0:0.1.12-22.fc12 set to be erased --- Package libuuid.i686 0:2.16-10.3.fc12 set to be erased --- Package libvorbis.i686 1:1.2.3-3.fc12 set to be erased --- Package libxcb.i686 0:1.4-1.fc12 set to be erased --- Package libxml2.i686 0:2.7.6-1.fc12 set to be erased --- Package mesa-dri-drivers.i686 0:7.6-0.13.fc12 set to be erased --- Package mesa-libGL.i686 0:7.6-0.13.fc12 set to be erased --- Package mesa-libGLU.i686 0:7.6-0.13.fc12 set to be erased --- Package ncurses-libs.i686 0:5.7-3.20090207.fc12 set to be erased --- Package nss-mdns.i686 0:0.10-8.fc12 set to be erased --- Package nss-softokn-freebl.i686 0:3.12.4-10.fc12 set to be erased --- Package openldap.i686 0:2.4.18-5.fc12 set to be erased --- Package openssl.i686 0:1.0.0-0.13.beta4.fc12 set to be erased --- Package readline.i686 0:6.0-3.fc12 set to be erased --- Package sqlite.i686 0:3.6.17-1.fc12 set to be erased --- Package tcp_wrappers-libs.i686 0:7.6-56.fc12 set to be erased --- Package usbutils.x86_64 0:0.86-2.fc12 set to be erased --- Package wine-capi.i686 0:1.1.32-1.fc12 set to be erased --- Package wine-cms.i686 0:1.1.32-1.fc12 set to be erased --- Package wine-core.i686 0:1.1.32-1.fc12 set to be erased --- Package wine-ldap.i686 0:1.1.32-1.fc12 set to be erased --- Package wine-twain.i686 0:1.1.32-1.fc12 set to be erased --- Package zlib.i686 0:1.2.3-23.fc12 set to be erased -- Finished Dependency Resolution Dependencies Resolved === Package Arch Version RepositorySize === Removing: alsa-lib i686 1.0.21-3.fc12 installed1.1 M cyrus-sasl-lib i686 2.1.23-4.fc12 installed336 k db4 i686 4.7.25-13.fc12 installed1.5 M dbus-libsi686 1:1.2.16-8.fc12 installed278 k expati686 2.0.1-7 installed188 k flac i686 1.2.1-6.fc12 installed716 k freetype i686 2.3.9-6.fc12 installed787 k glibci686 2.11-2 installed 14 M jack-audio-connection-kiti686 0.118.0-1.fc12
Re: Weird yum remove *.*86
On 2009-12-04 06:37, Eric Springer wrote: Notice how it tries to remove the 64 bit usbutils. This does not happen with 'yum remove *.i586' (it's identical except for that 1 package) [r...@fedz ~]# yum remove *.*86 --- Package usbutils.x86_64 0:0.86-2.fc12 set to be erased It matches. See^^ -- Sjoerd Mullender -- 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: Weird yum remove *.*86
Thanks Sjoerd, On Fri, Dec 4, 2009 at 3:54 PM, Sjoerd Mullender sjo...@acm.org wrote: It matches. See ^^ Ah, i see. I didn't realize it was searching version numbers. Thanks for clearing that up -- 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: F12 Yum/package kit bug??
On Wed, 2 Dec 2009, Nathanael D. Noblet wrote: Over the last few days I have been unable to install updates via the package kit applet that pops up. I get the following output after clicking 'install updates'. Error Type: class 'yum.Errors.RepoError' Error Value: Error getting repository data for installed, repository not found File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 3125, in module main() File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 3122, in main backend.dispatcher(sys.argv[1:]) File : /usr/lib/python2.6/site-packages/packagekit/backend.py, line 710, in dispatcher self.dispatch_command(args[0], args[1:]) File : /usr/lib/python2.6/site-packages/packagekit/backend.py, line 657, in dispatch_command self.update_packages(only_trusted, package_ids) File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 1948, in update_packages signed = self._is_package_repo_signed(pkg) File : /usr/share/PackageKit/helpers/yum/yumBackend.py, line 1437, in _is_package_repo_signed repo = self.yumbase.repos.getRepo(pkg.repoid) File : /usr/lib/python2.6/site-packages/yum/repos.py, line 121, in getRepo 'Error getting repository data for $s, repository not found' $ (repoid) However yum update functions properly. Is this a known bug? yes. It's in PK and I believe it's been fixed upstream. -sv -- fedora-devel-list mailing list fedora-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-devel-list
Re: Problem with yum update and libxvidcore4.x86_64
On Tue, 01 Dec 2009 21:39:21 -0500, Charlie wrote: I have had a problem for the last 5 weeks or so whenever I run the yum update command on my F11 machine. No amount of research or reading up on yum and rpm have allowed me to correct my problem. So I am turning to the wizards here on the Fedora List for help. Any help deciphering and correcting my error would be most appreciated. Here is my error when I run yum update: 795 packages excluded due to repository priority protections ^ Might be important! What exactly do you protect here? Very often such activity has lead to dependency problems before. Setting up Update Process Resolving Dependencies -- Running transaction check -- Processing Dependency: libxvidcore4 = 1.2.1-12.fc11 for package: xvidcore-1.2.1-12.fc11.x86_64 RPM Fusion's xvidcore package is at 1.2.1-3.fc11, which is much lower. These libxvidcore4 and xvidcore packages might come from ATrpms. --- Package libxvidcore4.x86_64 0:1.2.2-13.fc11 set to be updated -- Finished Dependency Resolution xvidcore-1.2.1-12.fc11.x86_64 from installed has depsolving problems -- Missing Dependency: libxvidcore4 = 1.2.1-12.fc11 is needed by Could be anything like a missing Obsoletes tag in the libxvidcore4 upgrade or a missing xvidcore upgrade to 1.2.2. I suggest you get in contact with ATrpms or whatever repo that provides these packages. atrpmsATrpms - x86_64 - Stable enabled:677 -- 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: yum-updatesd -- doesn't seem to do anything
On 12/01/2009 07:41 PM, fedora-list-requ...@redhat.com wrote: Message: 1 Date: Tue, 01 Dec 2009 15:02:19 -0600 From: Steven Stern subscribed-li...@sterndata.com Subject: yum-updatesd -- doesn't seem to do anything To: Community assistance, encouragement, and advice for using Fedora. fedora-list@redhat.com Message-ID: 4b15845b.2060...@sterndata.com Content-Type: text/plain; charset=ISO-8859-15 I've installed yum-updatesd on my server (run level 3) and nothing seems to happen. It hasn't reported any updates for a long time, whether on F11 or F12. Yum update works, however. Snip. # automatically install updates do_update = no # automatically download updates do_download = no # automatically download deps of updates do_download_deps = no If you want yum-updatesd to actually do the updates you must set all three of the above to yes. I also set : emit_via = syslog dbus_listener = no yum-updatesd silently does all updates for me on several machines. signature.asc Description: OpenPGP digital signature -- 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
yum-updatesd -- doesn't seem to do anything
I've installed yum-updatesd on my server (run level 3) and nothing seems to happen. It hasn't reported any updates for a long time, whether on F11 or F12. Yum update works, however. The service is running: root 1940 0.0 0.9 28820 9616 ?SN 13:51 0:00 /usr/bin/python -tt /usr/sbin/yum-updatesd The conf file is as follows. I've also tried to have it output to syslog. [main] # how often to check for new updates (in seconds) run_interval = 14400 # how often to allow checking on request (in seconds) updaterefresh = 600 # how to send notifications (valid: dbus, email, syslog) emit_via = email email_to = r...@localhost # should we listen via dbus to give out update information/check for # new updates dbus_listener = yes # automatically install updates do_update = no # automatically download updates do_download = no # automatically download deps of updates do_download_deps = no -- Steve -- 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
is there any inconvenience in defining new yum groups?
is there a way to request new yum groups related to a particular issue? i'm thinking of embedded linux developers, who might want to install the Embedded Linux group, which would contain packages like squashfs-tools, mtd-tools, mtd-tools-ubi and so on. it wouldn't be hard to put together a list of the standard embedded-related packages one would want. is there a protocol for requesting a new group, or is it not worth the trouble? rday -- Robert P. J. Day Waterloo, Ontario, CANADA Linux Consulting, Training and Kernel Pedantry. Web page: http://crashcourse.ca Twitter: http://twitter.com/rpjday -- 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
After doing a yum update I notice these (W)arnings
Greetings, After doing a yum update I notice these (W)arnings? ** Snip ** Updating : abrt-gui-1.0.0-1.fc12.i686 35/79 Updating : coreutils-7.6-7.fc12.i686 36/79 Installing : kernel-PAE-2.6.31.6-145.fc12.i686 37/79 W: Possible missing firmware ql8100_fw.bin for module qla2xxx.ko W: Possible missing firmware aic94xx-seq.fw for module aic94xx.ko Is this something I need to be concerned about? TIA -- Best regards, Chris () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments There's no place like 127.0.0.1 -- 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: is there any inconvenience in defining new yum groups?
On 12/02/2009 03:57 AM, Robert P. J. Day wrote: is there a way to request new yum groups related to a particular issue? i'm thinking of embedded linux developers, who might want to install the Embedded Linux group, which would contain packages like squashfs-tools, mtd-tools, mtd-tools-ubi and so on. it wouldn't be hard to put together a list of the standard embedded-related packages one would want. is there a protocol for requesting a new group, or is it not worth the trouble? Such questions should be directed to fedora-devel list but the process is defined in http://fedoraproject.org/wiki/How_to_use_and_edit_comps.xml_for_package_groups 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: yum-updatesd -- doesn't seem to do anything
Steven Stern wrote: I've installed yum-updatesd on my server (run level 3) and nothing seems to happen. It hasn't reported any updates for a long time, whether on F11 or F12. Yum update works, however. What happens if you manually do yum update? It's likely there is some reason it didn't update. Maybe had to ask your permission for a new key, or maybe a conflict. Too bad it doesn't tell you. -- 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
Problem with yum update and libxvidcore4.x86_64
I have had a problem for the last 5 weeks or so whenever I run the yum update command on my F11 machine. No amount of research or reading up on yum and rpm have allowed me to correct my problem. So I am turning to the wizards here on the Fedora List for help. Any help deciphering and correcting my error would be most appreciated. Here is my error when I run yum update: 795 packages excluded due to repository priority protections Setting up Update Process Resolving Dependencies -- Running transaction check -- Processing Dependency: libxvidcore4 = 1.2.1-12.fc11 for package: xvidcore-1.2.1-12.fc11.x86_64 --- Package libxvidcore4.x86_64 0:1.2.2-13.fc11 set to be updated -- Finished Dependency Resolution xvidcore-1.2.1-12.fc11.x86_64 from installed has depsolving problems -- Missing Dependency: libxvidcore4 = 1.2.1-12.fc11 is needed by package xvidcore-1.2.1-12.fc11.x86_64 (installed) Error: Missing Dependency: libxvidcore4 = 1.2.1-12.fc11 is needed by package xvidcore-1.2.1-12.fc11.x86_64 (installed) You could try using --skip-broken to work around the problem You could try running: package-cleanup --problems package-cleanup --dupes rpm -Va --nofiles --nodigest Here is the output from yum repolist: Loading mirror speeds from cached hostfile * fedora: mirror.cogentco.com * kde-redhat: mirror.unl.edu * kde-redhat-all: mirror.unl.edu * livna: rpm.livna.org * rpmfusion-free: mirror.liberty.edu * rpmfusion-free-updates: mirror.liberty.edu * rpmfusion-nonfree: mirror.liberty.edu * rpmfusion-nonfree-updates: mirror.liberty.edu * updates: serverbeach1.fedoraproject.org repo id repo name status adobe Adobe Systems Incorporated enabled: 17 atrpmsATrpms - x86_64 - Stable enabled:677 fedoraFedora 11 - x86_64 enabled: 16,577 jpackage5 JPackage 5.0 (Generic) enabled: 3,307 jpackage5-nonfree JPackage 5.0 (Non-Free) enabled: 17 kde-redhatKDE-Redhat: Fedora-Specific enabled: 4 kde-redhat-allKDE-Redhat: General Packages enabled:290 livna rpm.livna.org for 11 - x86_64 enabled: 3 planetccrma Planet CCRMA 11 - x86_64 enabled:271 planetcorePlanet CCRMA Core 11 - x86_64 enabled: 44 rpmfusion-freeRPM Fusion for Fedora 11 - Free enabled:423 rpmfusion-free-updatesRPM Fusion for Fedora 11 - Free - Updates enabled:567 rpmfusion-nonfree RPM Fusion for Fedora 11 - Nonfree enabled:121 rpmfusion-nonfree-updates RPM Fusion for Fedora 11 - Nonfree - Updates enabled:263 skype Skype Repository enabled: 1 updates Fedora 11 - x86_64 - Updates enabled: 8,198 repolist: 30,780 Thanks in advance for any and all help. Charlie -- 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: After doing a yum update I notice these (W)arnings
Chris writes: Greetings, After doing a yum update I notice these (W)arnings? ** Snip ** Updating : abrt-gui-1.0.0-1.fc12.i686 35/79 Updating : coreutils-7.6-7.fc12.i686 36/79 Installing : kernel-PAE-2.6.31.6-145.fc12.i686 37/79 W: Possible missing firmware ql8100_fw.bin for module qla2xxx.ko W: Possible missing firmware aic94xx-seq.fw for module aic94xx.ko Is this something I need to be concerned about? Only if you have either the QLogic Fibre Channel HBA Driver or the Adaptec aic94xx SAS/SATA driver in your server. Unless you're using these two, this has no impact. And if you did have one of these, it wouldn't already be working for you, since you still don't have the requisite firmware to load, even with your existing kernel. pgpi4gPIAvohH.pgp Description: PGP signature -- 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: yum-updatesd -- doesn't seem to do anything
On 12/01/2009 07:10 PM, Neal Becker wrote: Steven Stern wrote: I've installed yum-updatesd on my server (run level 3) and nothing seems to happen. It hasn't reported any updates for a long time, whether on F11 or F12. Yum update works, however. What happens if you manually do yum update? It's likely there is some reason it didn't update. Maybe had to ask your permission for a new key, or maybe a conflict. Too bad it doesn't tell you. I don't enable updates in yum-updatesd, just notification. -- Steve -- 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: After doing a yum update I notice these (W)arnings
On Tue, 01 Dec 2009 22:08:35 -0500 Sam Varshavchik mr...@courier-mta.com wrote: Chris writes: Greetings, After doing a yum update I notice these (W)arnings? ** Snip ** Updating : abrt-gui-1.0.0-1.fc12.i686 35/79 Updating : coreutils-7.6-7.fc12.i686 36/79 Installing : kernel-PAE-2.6.31.6-145.fc12.i686 37/79 W: Possible missing firmware ql8100_fw.bin for module qla2xxx.ko W: Possible missing firmware aic94xx-seq.fw for module aic94xx.ko Is this something I need to be concerned about? Only if you have either the QLogic Fibre Channel HBA Driver or the Adaptec aic94xx SAS/SATA driver in your server. Unless you're using these two, this has no impact. And if you did have one of these, it wouldn't already be working for you, since you still don't have the requisite firmware to load, even with your existing kernel. Thanks Sam. I appreciate it. I assumed the same but wanted to get feedback. -- Best regards, Chris () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments There's no place like 127.0.0.1 -- 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
error message in yum
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Bonsoir, I am running f10. trying to update I get this error message from yum: ERREUR de résolution de dépendance par rpm_check_debug : mono(Mono.Addins) is needed by f-spot-0.6.1.3-1.fc10.i386 mono(Mono.Addins.Gui) is needed by f-spot-0.6.1.3-1.fc10.i386 mono(Mono.Addins.Setup) is needed by f-spot-0.6.1.3-1.fc10.i386 Terminé ! (1, [u'Veuillez reporter cette erreur dans http://yum.baseurl.org/report']) OK. There is some problem and I must report it there: http://yum.baseurl.org/report Going there, I don't understand where I can make a report... thanks for lights. - -- François Patte UFR de mathématiques et informatique Université Paris Descartes 45, rue des Saints Pères F-75270 Paris Cedex 06 Tél. +33 (0)1 4286 2145 http://www.math-info.univ-paris5.fr/~patte -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAksS+oQACgkQdE6C2dhV2JV4ZACaAzhOaH+5npwixI4+OhSERzto pQUAn1OlreUUINPcLrDqWoL4ccbw4wYH =O233 -END PGP SIGNATURE- -- 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
F12 yum install wireshark - not added to menus
Hi, I have just installed Wireshark on F12 on the console using 'yum install wireshark' as root. And Wireshark has not appearing on the menus, and it is does not envoke from the command line either. Where does it live and is there anyway to add it to the menus ? Many thanks in advance, Aaron -- 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: F12 yum install wireshark - not added to menus
Le jeudi 26 novembre 2009 à 18:20 +, Aaron Gray a écrit : Hi, I have just installed Wireshark on F12 on the console using 'yum install wireshark' as root. And Wireshark has not appearing on the menus, and it is does not envoke from the command line either. Where does it live and is there anyway to add it to the menus ? Many thanks in advance, Aaron -- 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 Hi, the GUI is in the wireshark-gnome package. -- 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: F12 yum install wireshark - not added to menus
On Thu, Nov 26, 2009 at 20:20, Aaron Gray aaronngray.li...@googlemail.comwrote: Hi, I have just installed Wireshark on F12 on the console using 'yum install wireshark' as root. And Wireshark has not appearing on the menus, and it is does not envoke from the command line either. Where does it live and is there anyway to add it to the menus ? Many thanks in advance, Aaron -- 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 This is the package you want : wireshark-gnome-1.2.2-1.fc12.i686 Do yum install wireshark-gnome -- When you have eliminated the impossible, whatever remains, however improbable, must be the truth - Sherlock Holmes -- 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: F12 yum install wireshark - not added to menus
2009/11/26 ELMORABITY Mohamed pikachu.2...@gmail.com Le jeudi 26 novembre 2009 à 18:20 +, Aaron Gray a écrit : Hi, I have just installed Wireshark on F12 on the console using 'yum install wireshark' as root. And Wireshark has not appearing on the menus, and it is does not envoke from the command line either. Where does it live and is there anyway to add it to the menus ? Hi, the GUI is in the wireshark-gnome package. Thanks, Aaron -- 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: yum install ocaml-lacaml
On Thu, Nov 26, 2009 at 04:27:21PM +0530, onkar bhardwaj wrote: Hi, I did it after your mail but still the problem persists. I also executed updatedb to check the possibility of stale databases. As far as I'm aware, it should work. If it doesn't it may be a bug - please file a bug giving full details of your system and the versions of Fedora and the OCaml packages you are using. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://et.redhat.com/~rjones/virt-df/ ___ Fedora-ocaml-list mailing list Fedora-ocaml-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-ocaml-list
Re: yum install ocaml-lacaml
On Tue, Nov 17, 2009 at 11:43:50AM +0530, onkar bhardwaj wrote: Hi, I executed yum install ocaml-lacaml on my system but I don't know how to use it. Since this was installed using rpm, I am unable to know what module to open or which library to link and where yum has installed these things. Can someone send me a sample example? It will be a big help. Sorry Onkar, didn't see this until now because of all the other status messages on this list. I hope this reply doesn't come too late. You can use lacaml in various ways. Certainly the easiest way is to use ocamlfind / topfind, like this: $ ocaml Objective Caml version 3.11.1 # #use topfind;; - : unit = () Findlib has been successfully loaded. Additional directives: #require package;; to load a package #list;; to list the available packages #camlp4o;;to load camlp4 (standard syntax) #camlp4r;;to load camlp4 (revised syntax) #predicates p,q,...;; to set these predicates Topfind.reset();; to force that packages will be reloaded #thread;; to enable threads - : unit = () # #require lacaml;; /usr/lib64/ocaml/unix.cma: loaded /usr/lib64/ocaml/bigarray.cma: loaded /usr/lib64/ocaml/lacaml: added to search path /usr/lib64/ocaml/lacaml/lacaml.cma: loaded /usr/lib64/ocaml/lacaml/lacaml_top.cma: loaded You can then do: open Lacaml.Impl.S and there are hundreds of functions available. Probably best to read the documentation: http://hg.ocaml.info/release/lacaml/raw-file/release-5.4.7/README.txt In general terms, lacaml on Fedora should behave and act exactly the same way as it does on other OCaml distributions. If there are any differences, they might be bugs, so file a bugzilla. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://et.redhat.com/~rjones/virt-df/ ___ Fedora-ocaml-list mailing list Fedora-ocaml-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-ocaml-list
Re: yum install ocaml-lacaml
Hi, Thanks. One more naive difficulty : I could do #use topfind but #require lacaml wasnt successful. It says no such packgae found though I have lacaml installed in the same /usr/lib64/ocaml directory. I have also added required variables to PATH and LD_LIBRARY_PATH. It does not show lacaml after #list too. I reinstalled lacaml but same thing again. What can be the reason? Regardsm Onkar On 11/26/09, Richard W.M. Jones rjo...@redhat.com wrote: On Tue, Nov 17, 2009 at 11:43:50AM +0530, onkar bhardwaj wrote: Hi, I executed yum install ocaml-lacaml on my system but I don't know how to use it. Since this was installed using rpm, I am unable to know what module to open or which library to link and where yum has installed these things. Can someone send me a sample example? It will be a big help. Sorry Onkar, didn't see this until now because of all the other status messages on this list. I hope this reply doesn't come too late. You can use lacaml in various ways. Certainly the easiest way is to use ocamlfind / topfind, like this: $ ocaml Objective Caml version 3.11.1 # #use topfind;; - : unit = () Findlib has been successfully loaded. Additional directives: #require package;; to load a package #list;; to list the available packages #camlp4o;;to load camlp4 (standard syntax) #camlp4r;;to load camlp4 (revised syntax) #predicates p,q,...;; to set these predicates Topfind.reset();; to force that packages will be reloaded #thread;; to enable threads - : unit = () # #require lacaml;; /usr/lib64/ocaml/unix.cma: loaded /usr/lib64/ocaml/bigarray.cma: loaded /usr/lib64/ocaml/lacaml: added to search path /usr/lib64/ocaml/lacaml/lacaml.cma: loaded /usr/lib64/ocaml/lacaml/lacaml_top.cma: loaded You can then do: open Lacaml.Impl.S and there are hundreds of functions available. Probably best to read the documentation: http://hg.ocaml.info/release/lacaml/raw-file/release-5.4.7/README.txt In general terms, lacaml on Fedora should behave and act exactly the same way as it does on other OCaml distributions. If there are any differences, they might be bugs, so file a bugzilla. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-df lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. http://et.redhat.com/~rjones/virt-df/ -- - Onkar Bhardwaj M.E. 2006-08 (Telecommunication) Indian Institute of Science, Bangalore - ___ Fedora-ocaml-list mailing list Fedora-ocaml-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-ocaml-list
install libgcc without yum rpm etc.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Bonjour, I made a mistake and erased libgcc How can I re-install it without using yum or rpm which seem to depend on this library... Thanks for helping - -- François Patte UFR de mathématiques et informatique Université Paris Descartes 45, rue des Saints Pères F-75270 Paris Cedex 06 Tél. +33 (0)1 4286 2145 http://www.math-info.univ-paris5.fr/~patte -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAksLu3sACgkQdE6C2dhV2JVDSQCdFmZd+woX123/zE/Suexn1P0/ 2v0An37NKXTv0U8zk6Eioq/P4T89ajaA =RLi+ -END PGP SIGNATURE- -- 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: install libgcc without yum rpm etc.
2009/11/24 François Patte francois.pa...@mi.parisdescartes.fr: Bonjour, I made a mistake and erased libgcc How can I re-install it without using yum or rpm which seem to depend on this library... Thanks for helping Not sure if this will work, but maybe boot from a live or rescue mode CD for the same architecture/release version and copy libgcc_s.so* over from /usr/lib or /usr/lib64 as appropriate, then reboot and do a yum install/reinstall/update on the package? -- imalone -- 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: install libgcc without yum rpm etc.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Le 24/11/2009 12:27, Ian Malone a écrit : 2009/11/24 François Patte francois.pa...@mi.parisdescartes.fr: Bonjour, I made a mistake and erased libgcc How can I re-install it without using yum or rpm which seem to depend on this library... Thanks for helping Not sure if this will work, but maybe boot from a live or rescue mode CD for the same architecture/release version and copy libgcc_s.so* over from /usr/lib or /usr/lib64 as appropriate, then reboot and do a yum install/reinstall/update on the package? OK thanks. It works. Instead of rescue mode, I get the file from another install. - -- François Patte UFR de mathématiques et informatique Université Paris Descartes 45, rue des Saints Pères F-75270 Paris Cedex 06 Tél. +33 (0)1 4286 2145 http://www.math-info.univ-paris5.fr/~patte -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAksL5T8ACgkQdE6C2dhV2JXSHACglK/bk3fTk4Sg7mHBh3T5pUso EAwAn2IJ5Smhf0J1jJLwTkmolYlOC9g0 =HmnR -END PGP SIGNATURE- -- 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: F12 yum install of condor on x86_64: Non-fatal POSTIN scriptlet failure in rpm package
On Sun, 22 Nov 2009 23:37:00 -0800 (PST), Rob wrote: Installing : condor-7.2.4-1.fc12.x86_64 3/3 Non-fatal POSTIN scriptlet failure in rpm package condor-7.2.4-1.fc12.x86_64 warning: %post(condor-7.2.4-1.fc12.x86_64) scriptlet failed, exit status 1 I know it says 'non-fatal'; however, by not knowing where the mesage comes from, it worries me mainly because this is going to be crucial condor server! Any ideas what's going wrong? See output of rpm --query --scripts condor and note the postinstall shell script section. It runs into a condition where it doesn't return 0. Make use of the bug reporting link at http://bugz.fedoraproject.org/condor -- 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: Graphical video not working after yum upgrade from fedora 11 to fedora 12
Hi John, I had an up to date fedora 11 install that was working fine. I followed the instructions on the wiki for doing a yum upgrade and everything seemed to go very well until I rebooted and things hung as the graphical interface (I use KDE) was to boot. I am able to boot into single user mode and run level 3 and things appear to be fine. I just can not get the graphical display. Any help would be appreciated. I had some minor issues with the open driver (aka nouveau) when upgrading to Fedora 12 and in my investigations I found a couple of interesting links for people using the proprietary one: - Official howto from RPM Fusion: http://rpmfusion.org/Howto/nVidia - Personal blog with similar problem (solved): http://linuxsoftwareblog.com/blog/?p=232 HTH, David -- 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: f12 yum/rpm commands to list all dependencies on a library
On 11/21/2009 08:37 PM, Tony Nelson wrote: On 09-11-21 21:07:14, Skunk Worx wrote: On f12 I see a package called oprofile-gui depends on the qt3-3.8b rpm. What command(s) can I run inside a local repo (where all the rpm packages are) that will tell me how many f12 Everything packages are still using qt3? # repoquery --whatrequires --alldeps qt3 You may need to specify the repository with --repofrompath=repoid,path/url see `man repoquery`. What command(s) can I run for the locally installed package set that will tell me how many packages are still using qt3? Well, there's always `yum remove qt3` and answer no (as long as assumeyes is not set). I have a project that I am porting to x86_64/qt4 and would prefer not to mix the two subsystems on my development machine. The /etc/profile.d/qt* files are currently pointing the default QTDIR, QTINC, QTLIB, and PATH variables at qt-3.3 locations even though I'v installed qt-devel which is qt-4.5. Possibly this is a use for a chroot, or maybe mock or even mach. (I have not done this.) I used both of the suggestions and they do exactly what I want. There are 257 qt3 projects in the repo, many of which are explicitly qt3 named so the actual list could be shorteronly oprofile_gui is currently installed and requiring qt3. Still undecided on whether to remove the gui and risk future breakage by changing the paths or running chroot etc. Thanks, John -- 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
F12 yum install of condor on x86_64: Non-fatal POSTIN scriptlet failure in rpm package
Hi, I get this message on my freshly installed F12 with the condor package: = [...snip...] Downloading Packages: Setting up and reading Presto delta metadata Processing delta metadata Package(s) data still to download: 9.6 M (1/3): classads-1.0.4-1.fc12.x86_64.rpm | 236 kB 00:00 (2/3): condor-7.2.4-1.fc12.x86_64.rpm| 9.2 MB 00:05 (3/3): gsoap-2.7.13-2.fc12.x86_64.rpm| 182 kB 00:00 Total 1.5 MB/s | 9.6 MB 00:06 Running rpm_check_debug Running Transaction Test Finished Transaction Test Transaction Test Succeeded Running Transaction Installing : classads-1.0.4-1.fc12.x86_64 1/3 Installing : gsoap-2.7.13-2.fc12.x86_64 2/3 Installing : condor-7.2.4-1.fc12.x86_64 3/3 Non-fatal POSTIN scriptlet failure in rpm package condor-7.2.4-1.fc12.x86_64 warning: %post(condor-7.2.4-1.fc12.x86_64) scriptlet failed, exit status 1 Installed: condor.x86_64 0:7.2.4-1.fc12 Dependency Installed: classads.x86_64 0:1.0.4-1.fc12 gsoap.x86_64 0:2.7.13-2.fc12 Complete! = I know it says 'non-fatal'; however, by not knowing where the mesage comes from, it worries me mainly because this is going to be crucial condor server! Any ideas what's going wrong? Thanks, Rob. -- 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
f12 yum/rpm commands to list all dependencies on a library
On f12 I see a package called oprofile-gui depends on the qt3-3.8b rpm. What command(s) can I run inside a local repo (where all the rpm packages are) that will tell me how many f12 Everything packages are still using qt3? What command(s) can I run for the locally installed package set that will tell me how many packages are still using qt3? I have a project that I am porting to x86_64/qt4 and would prefer not to mix the two subsystems on my development machine. The /etc/profile.d/qt* files are currently pointing the default QTDIR, QTINC, QTLIB, and PATH variables at qt-3.3 locations even though I've installed qt-devel which is qt-4.5. --- John -- 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: f12 yum/rpm commands to list all dependencies on a library
Skunk Worx wrote: On f12 I see a package called oprofile-gui depends on the qt3-3.8b rpm. What command(s) can I run inside a local repo (where all the rpm packages are) that will tell me how many f12 Everything packages are still using qt3? What command(s) can I run for the locally installed package set that will tell me how many packages are still using qt3? The repoquery command, from yum-utils, is perfect for this task (though it will just query the repodata rather than look at local packages -- generally I think this is preferable, but it's not exactly what you asked for). To find all the dependencies for qt3, this should do the trick: $ repoquery --whatrequires --alldeps qt3 | sort -- ToddOpenPGP - KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp ~~ To be stupid, selfish, and have good health are three requirements for happiness, though if stupidity is lacking, all is lost. -- Gustave Flaubert pgpPEvL8LjhiS.pgp Description: PGP signature -- 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: f12 yum/rpm commands to list all dependencies on a library
On 09-11-21 21:07:14, Skunk Worx wrote: On f12 I see a package called oprofile-gui depends on the qt3-3.8b rpm. What command(s) can I run inside a local repo (where all the rpm packages are) that will tell me how many f12 Everything packages are still using qt3? # repoquery --whatrequires --alldeps qt3 You may need to specify the repository with --repofrompath=repoid,path/url see `man repoquery`. What command(s) can I run for the locally installed package set that will tell me how many packages are still using qt3? Well, there's always `yum remove qt3` and answer no (as long as assumeyes is not set). I have a project that I am porting to x86_64/qt4 and would prefer not to mix the two subsystems on my development machine. The /etc/profile.d/qt* files are currently pointing the default QTDIR, QTINC, QTLIB, and PATH variables at qt-3.3 locations even though I'v installed qt-devel which is qt-4.5. Possibly this is a use for a chroot, or maybe mock or even mach. (I have not done this.) -- TonyN.:' mailto:tonynel...@georgeanelson.com ' http://www.georgeanelson.com/ -- 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
Graphical video not working after yum upgrade from fedora 11 to fedora 12
I had an up to date fedora 11 install that was working fine. I followed the instructions on the wiki for doing a yum upgrade and everything seemed to go very well until I rebooted and things hung as the graphical interface (I use KDE) was to boot. I am able to boot into single user mode and run level 3 and things appear to be fine. I just can not get the graphical display. Any help would be appreciated. # uname -a Linux home-office 2.6.31.5-127.fc12.x86_64 #1 SMP Sat Nov 7 21:11:14 EST 2009 x86_64 x86_64 x86_64 GNU/Linux # rpm -qa | grep nvidia kmod-nvidia-190.42-1.fc12.4.x86_64 xorg-x11-drv-nvidia-libs-190.42-2.fc12.x86_64 kmod-nvidia-2.6.31.5-127.fc12.x86_64-190.42-1.fc12.4.x86_64 xorg-x11-drv-nvidia-190.42-2.fc12.x86_64 -- 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
