Processed: libsecret-tools: file conflict with bash-completion

[Debian Bug Tracking System]

found -1 libsecret-tools/0.21.6-1

Bug #1093258 [libsecret-tools,bash-completion] libsecret-tools: file conflict with bash-completion
The source libsecret-tools and version 0.21.6-1 do not appear to match any binary packages
Marked as found in versions libsecret-tools/0.21.6-1.

found -1 bash-completion/1:2.16.0-6

Bug #1093258 [libsecret-tools,bash-completion] libsecret-tools: file conflict with bash-completion
Marked as found in versions bash-completion/1:2.16.0-6.

[Jeremy Bícha]

Control: tag -1 pending

Hello,

Bug #1093258 in libsecret reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/gnome-team/libsecret/-/commit/be40395c91f8b69863af73f4db93478cb3ade8b8

------------------------------------------------------------------------
Remove bash completion files that conflict with those provided

by bash-completion

Closes: #1093258

Gbp-Dch: Full
------------------------------------------------------------------------

(this message was generated automatically)

[Debian Bug Tracking System]

Post by Jeremy Bícha
tag -1 pending

Bug #1093258 [libsecret-tools,bash-completion] libsecret-tools: file conflict with bash-completion
Added tag(s) pending.

[Debian Bug Tracking System]

Your message dated Fri, 17 Jan 2025 01:23:40 +0000
with message-id <E1tYb5I-00Fm5w-***@fasolo.debian.org>
and subject line Bug#1093258: fixed in libsecret 0.21.6-2
has caused the Debian Bug report #1093258,
regarding libsecret-tools: file conflict with bash-completion
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ***@bugs.debian.org
immediately.)