Addressing more sysvinit bugs
Jesse Smith
jessefrgsmith at yahoo.ca
Fri Nov 2 14:43:45 GMT 2018
On 11/2/18 8:05 AM, KatolaZ wrote:
> On Thu, Nov 01, 2018 at 07:24:26PM -0300, Jesse Smith wrote:
>> Hello gang, I've been gradually making my way through the init-related
>> issues in the Debuan bug tracker. So far I've gone through about 50
>> reports, fixed some, made comments on others as to whether they can be
>> closed or if it seem the bug could be better addressed elsewhere. It
>> feels like progress and I'm slowly running out of patches to apply
>> upstream. :)
>>
>> Here is a summary of the last handful of reports I've read and
>> addressed, or suggested they can be handled in initscripts or packaging.
>>
>
>
> Dear Jesse,
>
> thanks a lot for your valuable work in going through the bug reports,
> and for actually being able of busting some of them. Just one
> question: when you mark a bug as "fixed upstream" in your list, do you
> mean it has been solved in the current HEAD (2.91) or in any older
> version?
>
> Thanks again
>
> KatolaZ
>
In cases where I have listed the bug as "fixed" or "fixed upstream" it
indicates the issue is solved in the current development branch of
sysvinit. In this case it's the 2.92 branch, which will likely reach a
stable state around the start of 2019.
The 2.91 branch was made "stable" last month and is not receiving any
new changes.
- Jesse
More information about the Debian-init-diversity
mailing list