Hello,

After the upgrade from Bookworm 12 to Trixie 13, completion of SysVInit services targets fails

As it seems to be related to changes done in bash-completion v2.12, the issue also has been submitted upstream: https://github.com/scop/bash-completion/issues/1498

Cheers,
B.

Scratch the provided patch.

Proper solution has been merged in main:
https://github.com/scop/bash-completion/pull/1499

It will probably be part of the next 2.17 release.
A request for backport to 2.16 has been made on the PR.

Even if it fails, the patch would apply to 2.16 branch, used by Debian
stable.
As a fallback, cherry-picking it by the maintainer would be welcome.

This is one particularly annoying defect regarding SySVinit services.

Though I saw the commit upstream, I appreciate you letting me know. I'll get it backported as soon as possible. :)

I thought you wanted the backport done to Debian unstable/testing, which is easily done. Creating a package for Debian backports is more involved, so this is just a heads-up that that 'as soon as possible' might be longer.

As you saw on my comment on the upstream project, I askem them to
backport, at their level, the fix to the 2.16 version, the one used in
Debian stable.
Their current version is 2.17. Hence I thought theyed need to backport
the fix to 2.16. If you do not need that and prefer to cherry-pick (the
fix seems to apply straightforwardely to any version 2.12 - 2.17
inclusive), choose what fits you best.

What I would like, and I think what is reasonable the most, is a fix to
the 2.16 stable, through an update package, as it is a rather suprising,
annoying & quickly triggered bug for SysVinit users.

As a maintainer, I would count on your knowledge of the processes at
Debian's to manage requirements & timetables. (o:

Any news on this?
Any help required to push this through?