Re: Bug#386211: Who is supposed to remove the .pyc files? (see #386211)
Le 08.09.2006, à 15:21:50, Pierre Habouzit a écrit:
> Le ven 8 septembre 2006 14:51, Ludovic Rousseau a écrit :
> > Le 07.09.2006, à 16:55:59, Pierre Habouzit a écrit:
> > > # sorry pal, but such a bug renders the package completely
> > > unusable, and # is also a policy violation.
> >
> > Why is the package completely unusable? I just see a complain by dpkg
> > that /usr/lib/python2.3/site-packages/PyPlucker/ is not empty.
> >
> > I agree with the policy violation. Note that I adopted the package
> > recently and the problem was already there.
>
> the problem is that under some condition, even with the missing .py,
> the .pyc are seen as validate candidates to do an import.
>
> this often lead in broken setups.
OK. I uploaded a new version that removes
/usr/lib/python2.3/site-packages/PyPlucker/ in preinst.
> > So only people using unstable or testing _and_ running the scripts as
> > root will suffer from this bug. How long should I keep the "rm" in
> > preinst? Until etch is released ?
>
> yes you will be able to drop that in etch+1, because upgrades from a
> stable release to the one after the next is not supported. We assume
> users always upgrade from one stable to the next.
Users of sarge do not have plucker (plucker is not available in stable)
so will not have this bug and will not have problems with the upgrade.
> > Or can I just close the bug without adding anything in preinst since
> > packages in unstable/testing _may_ have bugs.
>
> no, packages un unstable/testing cannot have known bugs. they *may* have
> not-yet-known ones.
No plucker package in unstable/testing right now is buggy. Previous
packages were buggy but are not available any more (either in stable,
testing or unstable). So the bug have been solved already. What need to
be solved now is side effects of the bug.
This should be solved now. Thanks for your help.
--
Dr. Ludovic Rousseau Ludovic.Rousseau@free.fr
-- Normaliser Unix c'est comme pasteuriser le camembert, L.R. --
Reply to: