Hey,
From time to time I catch a yum warning. Last time it was today:
# yum update
...
Downloading Packages: vsftpd-2.2.2-6.el6_2.1.x86_64.rpm | 149 kB 00:01 Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction Warning: RPMDB altered outside of yum. Updating : vsftpd-2.2.2-6.el6_2.1.x86_64 1/2 Cleanup : vsftpd-2.2.2-6.el6_0.1.x86_64 2/2 Updated: vsftpd.x86_64 0:2.2.2-6.el6_2.1 Complete!
How come a simple update of a a single package from CentOS update
would "alter RPMDB outside of yum"...? Could that be a plugin? yum-3.2.29-22.el6.centos.noarch yum-metadata-parser-1.1.2-16.el6.x86_64 yum-plugin-fastestmirror-1.1.30-10.el6.noarch yum-plugin-priorities-1.1.30-10.el6.noarch yum-utils-1.1.30-10.el6.noarch
Anyone else?
Thx, JD
On Thu, 5 Jan 2012, John Doe wrote:
How come a simple update of a a single package from CentOS update
would "alter RPMDB outside of yum"...? Could that be a plugin? yum-3.2.29-22.el6.centos.noarch yum-metadata-parser-1.1.2-16.el6.x86_64 yum-plugin-fastestmirror-1.1.30-10.el6.noarch yum-plugin-priorities-1.1.30-10.el6.noarch yum-utils-1.1.30-10.el6.noarch
Anyone else?
It's not saying it's just done that, it's saying that someone's added/removed packages using rpm not yum. Is that something you're likely to have done? If so, and you're okay with that, don't worry about the warning too much.
jh
From: John Hodrien J.H.Hodrien@leeds.ac.uk
On Thu, 5 Jan 2012, John Doe wrote:
How come a simple update of a a single package from CentOS update would "alter RPMDB outside of yum"...?
It's not saying it's just done that, it's saying that someone's added/removed packages using rpm not yum.
Ah, now that I reread the sentence, I get it...
Thx! JD
John R Pierce wrote:
On 01/05/12 6:17 AM, John Doe wrote:
How come a simple update of a a single package from CentOS update
would "alter RPMDB outside of yum"...?
I've gotten those messages when I've installed an RPM without using yum.
yes, it appears yum is trying to become more than a depsolver and frontend for the package manager, ie rpm. Meaning we'll have fewer options available... depsolver lock-in? oh well...
On Thu, 5 Jan 2012, Nicolas Thierry-Mieg wrote:
yes, it appears yum is trying to become more than a depsolver and frontend for the package manager, ie rpm. Meaning we'll have fewer options available... depsolver lock-in? oh well...
Don't take it that seriously. It's a warning, you're free to ignore it. If you use something like spacewalk, using yum to remove a package has the advantage that spacewalk is immediately aware you've done it.
jh
On Thursday 05 January 2012 06:17:17 John Doe wrote:
# yum update ... Downloading Packages: vsftpd-2.2.2-6.el6_2.1.x86_64.rpm | 149 kB 00:01 Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction Warning: RPMDB altered outside of yum. Updating : vsftpd-2.2.2-6.el6_2.1.x86_64 1/2 Cleanup : vsftpd-2.2.2-6.el6_0.1.x86_64 2/2 Updated: vsftpd.x86_64 0:2.2.2-6.el6_2.1 Complete!
How come a simple update of a a single package from CentOS update would "alter RPMDB outside of yum"...?
The warning is generated by yum, saying that its own database of installed packages does not match the rpm database. This basically means that sometime back you have used rpm directly to install/remove some package, circumventing yum. You are not supposed to install rpm packages behind yum's back. :-)
The warning has nothing to do with the vsftpd package which is being updated in this instance. It's rather yum performing the database check when the transaction starts.
HTH, :-) Marko
On 01/05/2012 04:01 PM, Marko Vojinovic wrote:
On Thursday 05 January 2012 06:17:17 John Doe wrote:
How come a simple update of a a single package from CentOS update would "alter RPMDB outside of yum"...?
The warning is generated by yum, saying that its own database of installed packages does not match the rpm database. This basically means that sometime back you have used rpm directly to install/remove some package, circumventing yum. You are not supposed to install rpm packages behind yum's back. :-)
The warning has nothing to do with the vsftpd package which is being updated in this instance. It's rather yum performing the database check when the transaction starts.
This can be avoided using "yum localinstall <package-filename>" from the location where that package is, instead of "rpm -ivh <package-filename>".
On Thu, 5 Jan 2012, Ljubomir Ljubojevic wrote:
This can be avoided using "yum localinstall <package-filename>" from the location where that package is, instead of "rpm -ivh <package-filename>".
AFAIK localinstall is the same as install now, so you can just use:
yum install <package-filename>
jh
On Thu, Jan 05, 2012 at 03:01:33PM +0000, Marko Vojinovic wrote:
On Thursday 05 January 2012 06:17:17 John Doe wrote:
# yum update ...
...
Running Transaction Test Transaction Test Succeeded Running Transaction Warning: RPMDB altered outside of yum.
...
How come a simple update of a a single package from CentOS update would "alter RPMDB outside of yum"...?
The warning is generated by yum, saying that its own database of installed packages does not match the rpm database. This basically means that sometime back you have used rpm directly to install/remove some package, circumventing yum. You are not supposed to install rpm packages behind yum's back. :-)
you can but then you need to resync yum and rpm databases:
[tru@centos6 ~]$ yum history sync will "fix" your warnings
Tru
From: Tru Huynh tru@centos.org
you can but then you need to resync yum and rpm databases: [tru@centos6 ~]$ yum history sync will "fix" your warnings
Cool!
Thx, JD
-
John Doe -
John Hodrien -
John R Pierce -
Ljubomir Ljubojevic -
Marko Vojinovic -
Nicolas Thierry-Mieg -
Tru Huynh