[Piuparts-devel] Bug#440183: Bug#440183: Bug#440183: piuparts: wrongly complains if processes are running inside chroot

[John Wright]

On Thu, Aug 30, 2007 at 06:40:08PM +0300, Lars Wirzenius wrote:
> to, 2007-08-30 kello 15:45 +0200, Lucas Nussbaum kirjoitti:
> > During an upgrade test, in the second chroot (the one used to install
> > the package):
> > - piuparts installs the package to test in etch
> > - piuparts upgrades the chroot
> > - piuparts tests for running processes <-- THIS IS WRONG!
> > - piuparts removes and purges packages
> > 
> > Testing for running processes after the upgrade is wrong. If the package
> > is a daemon, or depends on daemons, of course, it will still be running
> > after the upgrade! It should only test for running processes after the
> > purge.
> 
> Unless things have changed since I last looked at piuparts in detail,
> which they of course may well have done, it is wrong for any processes
> to exist in the chroot, after a package is installed, since piuparts
> does its best to prevent daemons from starting up at all. Thus, I would
> not classify this as a bug in piuparts.

Yes, piuparts still creates a policy-rc.d file that postinst scripts
ought to obey.  However, I cannot reproduce this.  (I notice Ana has
already attached a log file, and it looks very similar to the one I
have, so I won't duplicate...)

Usually, this happens when a package's postinst calls
    /etc/init.d/<pkg> restart
directly, rather than using invoke-rc.d, but that isn't the case for ud.
Lucas, does this happen for you when you generate a fresh chroot
(run piuparts without -b)?

Thanks,
John