On 8/17/19 3:29 PM, Ian Jackson wrote:
> Jesse Smith writes ("Bug#934945: startpar: insserv attemps to write to
> /etc/.boot.* even with -p option"):
>> The change has been made upstream so this should be fixed when the next
>> version comes out, probably around the end of September. That would
Jesse Smith writes ("Bug#934945: startpar: insserv attemps to write to
/etc/.boot.* even with -p option"):
> The change has been made upstream so this should be fixed when the next
> version comes out, probably around the end of September. That would save
> the trouble of patching the test
On 8/17/19 2:14 PM, Ian Jackson wrote:
> Jesse Smith writes ("Bug#934945: startpar: insserv attemps to write to
> /etc/.boot.* even with -p option"):
>> On a related note, in the startpar build log it shows the version of
>> startpar being tested is located at /lib/startpar/startpar. Upstream
>>
Jesse Smith writes ("Bug#934945: startpar: insserv attemps to write to
/etc/.boot.* even with -p option"):
> On a related note, in the startpar build log it shows the version of
> startpar being tested is located at /lib/startpar/startpar. Upstream
> we use the startpar executable in the local
> Folks, we have serious regression. Not sure, whether it is bug in
> startpar test suite, which invokes `insserv' with `-p', but without
> `-i', or it is regression in `insserv'.
It's sort of a fore-gression. The Startpar testsuite was set up to work
with older versions of insserv, like
Package: startpar
Affects: inserv
Version: 1.20.0-2
Severity: important
Tags: upstream help
Folks, we have serious regression. Not sure, whether it is bug in
startpar test suite, which invokes `insserv' with `-p', but without
`-i', or it is regression in `insserv'.
Either way, insserv does not
6 matches
Mail list logo
