On Wed, Nov 10, 2010 at 3:54 AM, James Antill <james-yum@xxxxxxx> wrote:
Thanks for the suggestion, but it still outputs garbage.
# yum -y -q --security check-update 2>/dev/null
aalib.x86_64 1.4.0-5.el5.rf rpmforge
[many lines of output elided.....]
udftools.x86_64 1.0.0b3-3.el5.rf rpmforge
xvidcore.x86_64
Actually, the -y is not required, since this operation does not change the state of anything. It's just supposed to succeed or fail depending on whether there are security-related updates available or not. It never asks for permission to change something, because it never changes anything.
# yum -q --security check-update 2>/dev/null
aalib.x86_64 1.4.0-5.el5.rf rpmforge
blas.x86_64 3.1.1-1.el5.rf
[bla bla bla]
I have this running in a cron job on several machines running centos 5.5. Only on this one machine does this command spam me with this useless output. I thought at first it might be a new buggy version of yum-security, but the same versions are running on my other machines where the command works correctly.
# rpm -qa|grep -i yum
yum-updatesd-0.9-2.el5
yum-security-1.1.16-14.el5.centos.1
yum-metadata-parser-1.1.2-3.el5.centos
yum-fastestmirror-1.1.16-14.el5.centos.1
yum-3.2.22-26.el5.centos
yum-priorities-1.1.16-14.el5.centos.1
Somehow the configuration has become corrupt? It seems to have to do with the rpmforge repo, when I disable that one everything works properly:
# yum -q --disablerepo=rpmforge --security check-update 2>/dev/null
#
I'd love to point the finger at a bug in yum-security or the config of the rpmforge repo, but both of these are present (same version) and working fine on all my machines except this one.
Okay, something was definitely corrupt in my rpmforge repo config. I uninstalled rpmforge and then reinstalled it, and the problem went away.
Thanks y'all
Dave
David Burns <tdbtdb@xxxxxxxxx> writes:[...]
> I thought -q meant 'no output'. Recently yum -q has started spewing the
> following garbage, can anyone tell me why?
> # yum -yq --security check-update 2>/dev/nullUse:
# yum -y -q --security check-update 2>/dev/null
...and it'll work.
Thanks for the suggestion, but it still outputs garbage.
# yum -y -q --security check-update 2>/dev/null
aalib.x86_64 1.4.0-5.el5.rf rpmforge
[many lines of output elided.....]
udftools.x86_64 1.0.0b3-3.el5.rf rpmforge
xvidcore.x86_64
Long story:
The problem is that options can only be parsed after initial
configuration has been setup, but some options have to be parsed
before initial configuration (Eg. -c --noplugins --installroot
etc. ... and -q).
The way we work around this is to have a custom option parser for
just those special options. However that special option parser doesn't
understand that "-yq" means "-y -q" (or -yc blah.conf etc.).
Actually, the -y is not required, since this operation does not change the state of anything. It's just supposed to succeed or fail depending on whether there are security-related updates available or not. It never asks for permission to change something, because it never changes anything.
# yum -q --security check-update 2>/dev/null
aalib.x86_64 1.4.0-5.el5.rf rpmforge
blas.x86_64 3.1.1-1.el5.rf
[bla bla bla]
I have this running in a cron job on several machines running centos 5.5. Only on this one machine does this command spam me with this useless output. I thought at first it might be a new buggy version of yum-security, but the same versions are running on my other machines where the command works correctly.
# rpm -qa|grep -i yum
yum-updatesd-0.9-2.el5
yum-security-1.1.16-14.el5.centos.1
yum-metadata-parser-1.1.2-3.el5.centos
yum-fastestmirror-1.1.16-14.el5.centos.1
yum-3.2.22-26.el5.centos
yum-priorities-1.1.16-14.el5.centos.1
Somehow the configuration has become corrupt? It seems to have to do with the rpmforge repo, when I disable that one everything works properly:
# yum -q --disablerepo=rpmforge --security check-update 2>/dev/null
#
I'd love to point the finger at a bug in yum-security or the config of the rpmforge repo, but both of these are present (same version) and working fine on all my machines except this one.
Okay, something was definitely corrupt in my rpmforge repo config. I uninstalled rpmforge and then reinstalled it, and the problem went away.
Thanks y'all
Dave
_______________________________________________ Yum mailing list Yum@xxxxxxxxxxxxxxxxx http://lists.baseurl.org/mailman/listinfo/yum
