Lucas Nussbaum wrote:
Have you been able to reproduce this outside of piuparts ? I tried to,
but I really can't :-( I don't know what goes wrong inside piuparts.
Yes: for example, if I stop apache2, and start another process that
binds to port 80 (thus preventing the start of apache2), then postinst
fails when calling the script I mentioned in my previous email. I have
to look in more details at how the script is called and what it returns
(or does not return).
I am not sure what is the correct way for the script to run;
intuitively, posting should _try_ to call the apache2 restart script; if
this fails, then postinst should notice it but maybe not return an error
-- after all, the installation of the package itself went ok, and it
cannot be held responsible for other programs' failure. But maybe there
is a smarter way to handle this.
I modified piuparts so that it displays the debconf values for the
package after installation:
0m22.1s DEBUG: Starting command: ['chroot', '/tmp/tmpDYXi8R',
'debconf-show', 'w3c-markup-validator']
0m22.2s DUMP:
w3c-markup-validator/webserver: Apache2
I dunno if that helps you.
It looks correct.
If the only error reported by piuparts is related to broken symlinks,
then I think it's safe to ignore it (and you can close this bug).
If the restart of the server works ok, then indeed, this is the only error.
Frédéric
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
