Re: Bug#133306: apt-listchanges: Does not handle .pyc files correctly

2002-02-19 Thread Christian Kurz
On 18/02/02, Bastian Kleineidam wrote: > On Mon, Feb 18, 2002 at 12:48:02PM -0500, Matt Zimmerman wrote: > > Good plan; why not do that for python? How about a > > /usr/sbin/python-pkgtool --install > > /usr/sbin/python-pkgtool --remove > Look at http://people.debian.org/~calvin/python-central/

tmda

2002-02-19 Thread Matthias Klose
reopen 128531 thanks > From: [EMAIL PROTECTED] (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 (

Re: Bug#128531: tmda

2002-02-19 Thread Adam McKenna
On Wed, Feb 20, 2002 at 12:55:59AM +0100, Matthias Klose wrote: > reopen 128531 > thanks > > > From: [EMAIL PROTECTED] (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

Re: Bug#128531: tmda

2002-02-19 Thread Sean 'Shaleh' Perry
> > 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. > A program run by a user will never be able to write out the .py[co] files so the files MUST be ge