On Mon, Feb 16, 2009 at 02:35:20AM +0800, Thomas Goirand wrote:
> Philipp Kern wrote:
> > I'm curious why python-pyme is not sufficient.
> It's simply a MISTAKE that has been done by the last maintainer of yum,
> python-pyme is NOT the correct python package, python-gpgme is the right
> one. python-pyme is fully in python, while python-gpgme is written in C.
> Maybe it would be possible to have yum working with python-pyme (I
> didn't dive into it, and have no intention to do so), but I think it's
> really not worth so much trouble having a special crafted yum that will
> be different from upstream, when the solution is to use the correct package.
Did you take a look at the source? Well, I did now. Exactly two functions
are affected: return_keyids_from_pubring and import_key_to_pubring, both
While it was obviously wrong by the yum maintainer to apply that patch
to correct the import, it should also be easy to port it to pyme.
Considering that only few lines of Python are needed, maybe you could
concentrate on that.
> No new package == no working yum.
Re python-iniparse: why should it be needed? There is a ImportError
guard in the source so that it falls back to Python's ConfigParser.
Paste the error to the bug report and maybe fix the import.
Leaving your rant aside: maybe you should just get someone who knows
Python to fix the bug. It seems reasonably easy to be and within the
scope of a patch that could be accepted.
.'`. Philipp Kern Debian Developer
: :' : http://philkern.de Release Assistant
`. `' xmpp
firstname.lastname@example.org Stable Release Manager
`- finger email@example.com