Package: yum
Version: 3.2.12-1.2
Severity: normal

I get a Python error when running util-vserver with the 'yum' build method:

# vserver vyum-f8 build -m yum --force -- -d f8
You are using a version of yum which is insecure and broken in chroot
related operations; either apply the patches shipped in the 'contrib/'
directory of util-vserver, or ask the author of yum to apply them
(preferred).

In the meantime, 'vyum' will continue with dirty hacks which might not
work when the vserver is running and local DOS attacks are possible.

Execution will continue in 5 seconds...

=============================================================================
 Package                 Arch       Version          Repository        Size 
=============================================================================
Installing:
 glibc                   i686       2.7-2            fedora            5.4 M
Installing for dependencies:
 basesystem              noarch     8.1-1            fedora            2.9 k
 filesystem              i386       2.4.11-1.fc8     fedora            118 k
 glibc-common            i386       2.7-2            fedora             21 M
 libgcc                  i386       4.1.2-33         fedora             95 k
 setup                   noarch     2.6.10-1.fc8     fedora            125 k
 tzdata                  noarch     2008d-1.fc8      updates           754 k

Transaction Summary
=============================================================================
Install      7 Package(s)         
Update       0 Package(s)         
Remove       0 Package(s)         

Total download size: 27 M
attention: rpmts_HdrFromFdno: EntĂȘte V3 DSA signature: NOKEY, key ID 4f2a6fd2
Importing GPG key 0x4F2A6FD2 "Fedora Project <[EMAIL PROTECTED]>" from 
http://redhat.download.fedoraproject.org/pub/fedora/linux/releases/8/Everything/i386/os/RPM-GPG-KEY-fedora
Traceback (most recent call last):
  File "/usr/bin/yum", line 29, in <module>
    yummain.user_main(sys.argv[1:], exit_code=True)
  File "/usr/share/yum-cli/yummain.py", line 236, in user_main
    errcode = main(args)
  File "/usr/share/yum-cli/yummain.py", line 188, in main
    base.doTransaction()
  File "/usr/share/yum-cli/cli.py", line 364, in doTransaction
    if self.gpgsigcheck(downloadpkgs) != 0:
  File "/usr/share/yum-cli/cli.py", line 464, in gpgsigcheck
    self.getKeyForPackage(po, lambda x, y, z: self.userconfirm())
  File "/var/lib/python-support/python2.5/yum/__init__.py", line 2571, in 
getKeyForPackage
    misc.import_key_to_pubring(rawkey, po.repo.cachedir)
  File "/var/lib/python-support/python2.5/yum/misc.py", line 278, in 
import_key_to_pubring
    ctx = gpgme.Context()
AttributeError: 'module' object has no attribute 'Context'

In this Python trackback, we can see that yum/misc.py is apparently not using 
python-pyme correctly.
Afaics from the yum changelog, there was a number of changes related to gpgme 
since 3.2.12, but I'm not sure upgrading to 3.2.18 is an option at this 
point of the freeze.

Cheers,

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing'), (300, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.25-2-vserver-686 (SMP w/1 CPU core)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages yum depends on:
ii  python                     2.5.2-1       An interactive high-level object-o
ii  python-celementtree        1.0.5-10      Light-weight toolkit for XML proce
ii  python-libxml2             2.6.32.dfsg-2 Python bindings for the GNOME XML 
ii  python-pyme                0.8.0-1       Python interface to the GPGME GnuP
ii  python-rpm                 4.4.2.3-1     Python bindings for RPM
ii  python-sqlite              1.0.1-7       python interface to SQLite 2
ii  python-sqlitecachec        1.1.2-1       A fast metadata parser for YUM
ii  python-support             0.8.4         automated rebuilding support for P
ii  python-urlgrabber          3.1.0-4       A high-level cross-protocol url-gr
ii  rpm                        4.4.2.3-1     Red Hat package manager

yum recommends no packages.

yum suggests no packages.

-- no debconf information



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to