Re: Bug#128531: tmda
Adam McKenna writes:
> On Wed, Feb 20, 2002 at 12:55:59AM +0100, Matthias Klose wrote:
> > reopen 128531
> > thanks
> >
> > > From: adam@debian.org (Adam D. McKenna)
> > > Changes:
> > > tmda (0.46-1) unstable; urgency=low
> > > .
> > > * New upstream release
> > > * Package split into 3 packages to help attempt to conform to Debian's
> > > braindead Python policy. New packages are:
> > > python-tmda (Python libraries only)
> > > tmda (tmda and configuration files)
> > > python2-tmda (dummy package)
> > > (Closes: Bug#128531, Bug#131294)
> >
> > I really like such ChangeLog entries :-(((
> >
> > If you think, that the proposed Python policy is braindead, then
> > explain why.
> >
> > Your package restructering is braindead on its own and doesn't fix the
> > bug reported. Why adding a python2-tmda dummy package?
>
> Any policy that forces me to compile .py{c,o} object files in my postinst is
> braindead. Then I also have to delete them in purge/postrm, and the
> packaging system knows nothing about them.
In the changelog entry you complained about splitting the package, now
you complain about compiling the .py files. So the changelog entry is
simply false.
You have to remove the compiled python files in the postrm. Call as
root: python -O -c 'import TMDA' and try to remove the package ...
> The dummy package is there so that people already running tmda will get the
> new version automatically. It will be removed in the next revision of the
> package.
This doesn't help. You don't know, from which version someone upgrades.
Package: python-tmda
Conflicts: python2-tmda
Replaces: python2-tmda
Reply to: