* Gabriel F. T. Gomes wrote:
> Though I can certainly do it. If Debian's libsecret maintainers are
> fine with waiting for a new release of bash-completion, then I'll
> wait, as well, and avoid the backport.
Sorry for the weird punctuation. What I meant is that I can backport
the fix from upstrea
* Jeremy Bícha wrote:
> I suggest doing the bash-completion backport and then we can follow
> with a libsecret upload to include the bash-completion file (with
> appropriate Breaks/Replaces) and then we don't have to think about
> this issue later.
Yeah, not thinking about it in the future makes
I guess you might need to make bash-completion's autopkgtests only run
on specific architectures to enable it to migrate to Testing.
Thank you,
Jeremy Bícha
On Sun, Jan 26, 2025 at 1:42 PM Gabriel F. T. Gomes
wrote:
> I don't know if Debian's libsecret maintainers have already incorporate
> this change and if they want to reinstate their completion file,
> already. If so, I will have to backport the deprecation patch from
> upstream bash-completion. T
Upstream bash-completion has a patch to deprecate the completion for
libsecret in their master branch[1]. This has not been release, yet, so
it's not on Debian's package.
Likewise, upstream libsecret incorporate the completion file from
upstream bash-completion, since the latter was ruled better[2
5 matches
Mail list logo
