On 2008-06-11 18:22 +0200, Petter Reinholdtsen wrote:
> [Sven Joachim]
>> I couldn't really believe it, so I removed /etc/rc4.d/S18portmap,
>> switched to runlevel 4 with "init 4" and rebooted. And voila,
>> S32portmap ran successfully.
>
> This was an old bug in sysv-rc, now fixed in unstable and testing.
> Because of this, I believe this portmap bug can be closed as fixed.
Indeed the bug is (was) in sysv-rc, the reason why I cloned rather than
reassigned it was to prevent portmap from transitioning to testing.
It must not go in there before the fixed sysv-rc is ready.
> Not sure if it should be reassigned and closed as a bug against
> sysv-rc, or closed here after adding a dependency on the sysv-rc bug,
> so I leave it open for the maintainer or the relase managers to
> decide.
I think portmap should conflict with sysv-rc (< 2.86.ds1-58) to ensure
that the problem does not show up on users' systems.
Cheers,
Sven
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
