On Mon, 3 Aug 2009, Martin Vogt wrote:
Seth Vidal wrote:
On Mon, 3 Aug 2009, Martin Vogt wrote:
Yes, the kernel-source.rpm comes from my repo, but the localpackage is
in:
/var/cache/yum/R0_os11.1/packages/kernel-source-2.6.27.25-0.1.1.x86_64.rpm
so its the package which I downloaded from my repo.
(The md5sum for the localpackage and the repo are the same, I checked
that)
And regardless of the critical warning, the package is installed.
A simple rpm -U /var/cache/.../kernel-source.rpm does not show db errors
and doing a
rpm -U http://reposerver/tmp/kernel-source-2.6.27.25-0.1.1.x86_64.rpm
works too.
The only thing which I currently know, is this critical warning with
"yum udpate" and if I update "more" rpms, the db error.
okay - just to verify can you send me the output of:
yum --version
and rpm -q python
vmw169:/var/lib # rpm --version
RPM version 4.4.2.3
vmw169:/var/lib # yum --version
3.2.23
Installed: rpm-4.4.2.3-37.10.1.x86_64 at 2009-07-29 16:21
Built : http://bugs.opensuse.org at 2009-04-28 16:50
Committed: mls@xxxxxxx at 2009-04-27 12:00
Installed: yum-metadata-parser-1.1.2-107.25.x86_64 at 2009-07-29 16:20
Built : http://bugs.opensuse.org at 2008-12-03 11:38
Committed: cthiel@xxxxxxx at 2007-08-29 12:00
vmw169:/var/lib # rpm -q python
python-2.6.0-8.7
My first debug result is:
- If I remove the
vogt[SPECS]>cat changelog.txt | wc -l
29886
entries from the kernel-source.spec it works with yum-update.
(But adding it back and removing the %files section works too) :(
So maybe its a combination. Ridiculous entries in the changelog
and a big file list?
I guess it could be - but that doesn't make much sense why yum would care.
Yum doesn't really DO anything with either of those. All the actual
package installation bits are handled by rpm and thd db-error is certainly
coming from rpm.
What ver of rpm-python do you have installed?
-sv
_______________________________________________
Yum mailing list
Yum@xxxxxxxxxxxxxxxxx
http://lists.baseurl.org/mailman/listinfo/yum
