Le mar 22 août 2006 19:18, Joey Hess a écrit : > Joey Hess wrote: > > Setting up duplicity (0.4.2-2+sftp+amazons3+compression.2) ... > > [EMAIL PROTECTED]:~>ls -l > > /usr/lib/python2.3/site-packages/duplicity/__init__.py* -rw-r--r-- > > 1 root root 134 Aug 6 21:09 > > /usr/lib/python2.3/site-packages/duplicity/__init__.pyc -rw-r--r-- > > 1 root root 134 Aug 6 21:09 > > /usr/lib/python2.3/site-packages/duplicity/__init__.pyo > > Ah, right, .pyc and .pyo, but no .py files remain. The .pyc etc files > are left behind after the upgrade, since the old version of duplicity > is broken and has a postinst that runs compileall, but no prerm to > remove the old compiled files. > > If you had used debhelper, this wouldn't have happened, but since you > didn't, you're left needing to clean this mess up in the postinst > when the package is upgraded to a new version.
s/me/maxx/ I only did the last NMU, and failed to see that the previous package was completely braindead wrt that pyo/pyc cleaning. I'll let the maintainer clean that, and you're right, the severity has to be raised. I suppose the correct fix is to: rm -rf /usr/lib/python2.3/site-packages/duplicity/ somewhere in the preinst *eek*. I only answered because I do monitor the packages I NMUed for the python policy update, but here it's not a bug I did created (I just revealed it) so the maintainer really has to fix it. Cheers, -- ·O· Pierre Habouzit ··O [EMAIL PROTECTED] OOO http://www.madism.org
pgpom7x2nUPgV.pgp
Description: PGP signature
