Bug#506011: [Yum-devel] I'm the new maintainer for yum in Debian

[Thomas Goirand <thomas@goirand.fr>]

Tim Lauridsen wrote:
> I think someone is working on getting iniparse into debian
> http://code.google.com/p/iniparse/issues/detail?id=14&can=1
> 
> It is used instead of the standard ConfigParser, because the it
> preserves the order, comments and formatting of the ini files, when
> written back to
> disk, ConfigParser will totally messup the file when writing til back to
> disk.
> 
> Tim

I know that, there is an ITP (intention do package) filled here:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=506011

What I don't understand is why the ITP has been tagged twice as pending,
then the tag got removed. Maybe Joao Eriberto Mota Filho will be able to
tell us more about the status of his package, and why it's taking 4
months to have it uploaded in SID?

Anyway, even if python-iniparse is uploaded, if I want that the new
package of yum I did reaches Lenny, we can't depend on it. Indeed, the
current yum package in Debian Lenny is broken, as per this entry:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=496137

I'm not sure the package will be accepted in the Lenny point release
though. I'll do my best so it is. And this is all why I am saying that
this iniparse patch is temporary (when trying to have yum sent to Lenny).

Joao Eriberto Mota Filho, is there anything we can do to speedup the
upload process of python-iniparse in SID? Has python-iniparse been
rejected by the ftp masters? What happened?

Thomas