Beeing in debian for many of us is a matter of principles, and ideals. I do not negociate my principles and ideals, because it's who I am, and I don't negogiate who I am. You don't like me ? Fine, it's fair. But I won't change to make you happy.

That's the difference between compromise and compromission^[1].

              -- Pierre Habouzit

C'est par le réel qu'on vit ; c'est par l'idéal qu'on existe. Or, veut-on se rendre compte de la différence ? Les animaux vivent, l'homme existe.

               -- Victor Hugo

after many years of care, Matt Zimmerman gave me his beloved package.

I've already cleansed the package from many old bugs.

Matt also handed me his cvs snapshot, I've converted it into a git repository:

• that you can browse on http://git.madism.org/gitweb/
• that you can clone on http://git.madism.org/apt-listchanges.git/

Long live apt-listchanges reloaded !

You thought that buglist was soon over ?

sadly for you, I've tracked (using the Contents.gz of the archive) all the packages that seemed to have private python modules. I've found many that were even not compliant with the previous python policy (and that shiped public extensions btw), and a big lot that need update.

I'm way to tired to launch the big mass bug now, because I've worked more than 2 hours straight on that, looking at almost a hundred of packages list files in the eyes, to know if there was a tiiiiiiny python module hidden in there. Still expect it soon…

Sadly, it does not looks so good: my first list was 265 packages long, I suppose there is a whole bunch of false-positives, but I fear there will remain in the 200 bugs.

Though, this is the final step. If you do maintain a package that depends upon python, please help ! Migrating your package to the new policy is often easy if you use debhelper/cdbs/… and other high-level packaging tools.