[Users] vzpkg2 on Debian Lenny: some yum bugs

Miguel Filho miguel.filho at gmail.com
Sun Jan 4 20:06:04 EST 2009

Hello, me again!

Well, my usage of vzpkg2 resulted in more trouble than I would espect,
but that is the fun part, isn't it?

First of all, the yum version in Lenny is 3.2.12. I believe that
version will not change anytime soon, and Lenny will be released (God
knows when) with it. So, IMHO, we better have some workarounds for it.

Here we go again:

1) Yum fails to bootstrap CentOS 5 with this error:

Error: Failure finding best provider of libc.so.6 for ..., exceeded
maximum loop length

Googling around I've found this bug:

Basically adding glibc before all packages does the trick and the
template creation finishes without errors.

Curiously, fedora9 and centos4 work fine.

A manually added glibc to be the first package on minimal.list. Ugly
but functional.

2) Yum fails to bootstrap CentOS 5 again with this error:

File "/var/lib/python-support/python2.5/yum/misc.py", line 278, in
    ctx = gpgme.Context()
AttributeError: 'module' object has no attribute 'Context'

Once again, I've found this bug:

I did a long research on yum's code and the GPG handling in 3.2.12 is
broken. I talked with James Antill (yum's author) on IRC about this

<miguelzinho> hi there, I'm using yum 3.2.12 on Debian Lenny with vzpkg2
<miguelzinho> vzpkg2 bootstraps various distros
<miguelzinho> when bootstraping centos5
<miguelzinho> I got this
<miguelzinho> File "/var/lib/python-support/python2.5/yum/misc.py",
line 278, in import_key_to_pubring
<miguelzinho>     ctx = gpgme.Context()
<miguelzinho> AttributeError: 'module' object has no attribute 'Context'
<miguelzinho> i've take a look at the current misc.py and the gpg code
is a little different
<miguelzinho> based on what I see in the current code, returning False
on import_key_to_pubring() and some other functions does not affect
yum's behavior
<miguelzinho> I changed misc.py to always return False on 3.2.12 and
the bootstrap operation works fine
<geppetto> miguelzinho: 3.2.12 is basically unsupported by anyone at this point
<geppetto> miguelzinho: if what you did just disabled pgp on repo
keyrings (possible from my memory) ... then yeh, the fix is fine and
don't worry about it (that functionality wasn't really tested/working
in 3.2.12)
<geppetto> miguelzinho: But you might want to just update to something
more recent (best options: 3.2.19 as in RHEL/CentOS soon, or 3.2.21
when that's released soon)

There you go.

I kept looking and I've found out that vzpkg2 imports the GPG keys
using rpm, before calling yum --installroot.

Plus, the key for the centos-vz-addons repository was not available on
the gpgkeys directory. I've downloaded the key and then yum will not
bother trying importing it, so the bug is not triggered.

I think that's all for now.

Is there any bugtracker that I can report all these stuff?



More information about the Users mailing list