similar to: yum: not updating kernel

Well, there's a bug in the globbing for the tcsh with 5.4, and my boss has filed a bug report. Meanwhile, I downgraded tcsh on those systems whose users use that as their shell. Until it's resolved, he wants me to pin the version. Googling, I see someone a few years ago, answering someone's question, suggested adding exclude=openoffice* near the top of /etc/yum.conf. I also see, more

Hi there, is it possible to use regular expressions in the exclude-paramter of rsync ? For example: rsync --exclude "/path/to/*/[Ff][Oo][Ll][Dd][Ee][Rr]" I've tried it, but it will take no effect. -- SET THE CONTROLS FOR THE HEART OF THE SUN Jens

https://bugzilla.samba.org/show_bug.cgi?id=8965 Summary: unexpected --exclude behaviour which can lead to a data breach Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: major Priority: P5 Component: core AssignedTo: wayned at samba.org

I am having trouble using wildcards ("*") with yum in Centos 5. Listing or installing packages using them just immeidately fails with a "No match" error, and I'm not sure why. Here is an example. Any comments? I'd love to fix this. [root at granta ~]# ps -e | grep yum 2706 ? 00:00:22 yum-updatesd [root at granta ~]# yum list | grep kern kernel.x86_64

Help the OCaml compiler by expliciting Guestfs.guestfs as type for 'g' in some functions. --- get-kernel/get_kernel.ml | 2 +- sysprep/sysprep_operation_abrt_data.ml | 2 +- sysprep/sysprep_operation_bash_history.ml | 2 +- sysprep/sysprep_operation_ca_certificates.ml | 2 +- sysprep/sysprep_operation_crash_data.ml

Hi, 'exclude' option fails for yum on centos 5. I tried to yum install a group on a x86_64 machine, but it installs both ix86 version and x86_64 version. So I added the following line to /etc/yum.conf, clears /var/cache/yum/, then run 'yum groupinstall Ruby', but it reports that ix86 version packages will be installed still. Any one know what's the correct syntax to

I am trying to get off the plus kernel. Hasn't helped yet, and my MadWifi does not work with it. So I used YUMEX to remove all of the plus kernel cruft that I could see. I rebooted. ONly the standard kernel was listed in the boot menu (good sign). Start up Yumex, and it is showing that the plus kernel needs updating. Nothing on the regular kernel. Just yum update behaves the same.

On Wednesday, 14 December 2016 13:12:01 CET Richard W.M. Jones wrote: > Remove editor backup files such as *~ and *.bak wherever > they occur within the guest filesystem. > > This also includes a test. > --- Looks nice -- I have few notes below. Also, should this operation include also the swap files that editors can leave while editing? > + let fses = > + match

Thank you both for answering. I tried with and without the "-x" as the manual wasn't clear enough to me. I tried with and without wildcards (e.g., "*SL*", "*SL Series*", "SL Series" for that one). I tried other permutations before asking for help here. ("model" throws an error, "-x model" doesn't, which was confusing) I am not

This morning, I did "yum update" on my wife's box. It did not update the kernel. I ran the command again, and there is a response that no updates are available. Her box is a Compaq Evo D300v Celeron. During the past couple of days, when I did "yum update", on my daughters box and mine (Dell Dimensions), the kernel was updated and in the GRUB menus now, there are two (2)

Hello, I've been stuck for a while with an old version of firefox, installed from local .rpm (I know.. I should have downgraded using yum, instead) and added a exclude=firefox to the relevant .repo file. I did that after a yum-update has brought firefox 52+, and all add-ons were deprecated because of their new add-on scheme. Today that all the add-ons I need are available, I've tried

Hi All, I have finally switched to using hiera (worthy goal!) and I am looking for a flexible way to manage the ''exclude'' line in /etc/yum.conf. I want to be able to specify from different classes RPMs to be excluded in /etc/yum.conf, then build the exclude line from all those classes that set an exclude. In my hiera hierarchy, I use %{calling_module}, but I actually modify

So, regarding wildcards (globs) vs. regular expressions, the latter being used for such matches, I believe (did not check now) the config sections should look like this: [cp] driver = usbhid-ups port = auto desc = "CyberPower UPS CP" model = "CP685AVR-G" vendorid = "0764" product = "CP.*" Note the

Hi Folks, I'm running rsync between an NT client and a Solaris 7 Server (Ver 2.4.6). I'd like to be able to exclude the following directory: /opt/IBMHTTPDLOG/archivelogs but retrieve /opt/IBMHTTPDLOG My setup is: rsync -av -p -e rsync@server1.cna.com:/opt/IBMHTTPDLOG/ F:/opt/IBMHTTDLOG (client) rsync --daemon --exclude-from=/etc/rsync.exclude (server) What I get is

Hi folks, on CentOS 6.5 I run tripwire software which verifies data integrity. My system is automatically updated by yum (as far as I understand the /etc/cron.daily/0yum.cron is responsible for the regular system updates). After a system update I'm then notified by tripwire about the changes on the file system. By browsing those tripwire reports I found that there are files which did

Thank you, looks like the regex idiosyncracy might have been the issue. My current file: [sl] driver = usbhid-ups port = auto desc = "CyberPower UPS SL" product = "SL.*" productid = 0501 vendorid = 0764 #model = "SL Series" [ab] driver = usbhid-ups port = auto desc =

Thanks! FWIW if you do get to test new code, https://github.com/networkupstools/nut/pull/1811 adds warnings for situations like yours. Would be great to check if it works actually, with many "same-serial" devices :) Jim On Sat, Jan 14, 2023, 23:39 Bruce Pleat <bpleat at gmail.com> wrote: > Thank you, looks like the regex idiosyncracy might have been the issue. > > My

Part of what made my life harder is nut-scanner isn't in the package. Once I get a chance, I'll update to 2.8, but that'll be a little while off. (Any clue how to get 2.8 included in the package provider for my Raspberry Pi is presumably beyond the scope of this list, but if someone knows and wants to let me know, I wouldn't complain...) On Sat, Jan 14, 2023 at 3:12 PM Jim

Just a note: recent PRs are naturally not in 2.8.0 release (April 2022), but would be in eventual 2.8.1 Jim On Sun, Jan 15, 2023, 00:51 Bruce Pleat <bpleat at gmail.com> wrote: > Part of what made my life harder is nut-scanner isn't in the package. > > Once I get a chance, I'll update to 2.8, but that'll be a little while off. > (Any clue how to get 2.8 included in

Afternoon all, Is there any particular reason why yum fetches rpms for two architectures on almost any update/install I'd like to perform? This includes both i386 and x86_64. Here's a small excerpt after performing a 'yum update' cups-libs i386 1:1.1.22-0.rc1.9.18 update 107 k cups-libs x86_64 1:1.1.22-0.rc1.9.18 update 112 k