Your message dated Sun, 16 Aug 2026 20:33:53 +0100
with message-id <[email protected]>
and subject line Re: Bug#1144094: gir1.2-fwupd-2.0 has an undeclared file
conflict on /usr/share/gir-1.0/Fwupd-2.0.gir
has caused the Debian Bug report #1144094,
regarding gir1.2-fwupd-2.0 has an undeclared file conflict on
/usr/share/gir-1.0/Fwupd-2.0.gir
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 [email protected]
immediately.)
--
1144094: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1144094
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gir1.2-fwupd-2.0
Version: 2.1.7-3
Severity: serious
User: [email protected]
Usertags: fileconflict
Control: affects -1 + libfwupd-dev
gir1.2-fwupd-2.0 has an undeclared file conflict. This may result in an
unpack error from dpkg.
The file /usr/share/gir-1.0/Fwupd-2.0.gir is contained in the packages
* gir1.2-fwupd-2.0/2.1.7-3 as present in unstable
* libfwupd-dev
* 2.0.20-1~bpo13+1 as present in trixie-backports
* 2.0.20-1~deb13u1 as present in trixie
* 2.1.7-2 as present in forky|unstable
These packages can be unpacked concurrently, because there is no
relevant Replaces or Conflicts relation. Attempting to unpack these
packages concurrently results in an unpack error from dpkg, because none
of the packages installs a diversion for the affected file.
Kind regards
Helmut Grohne
--- End Message ---
--- Begin Message ---
Version: 2.1.7-4
On Sun, 16 Aug 2026 at 18:25:08 +0200, Thomas Uhle wrote:
you have forgotten to close this bug in debian/changelog, so the fixed
version 2.1.7-4 is prevented from migrating to forky as well. I am
not sure if simply closing this bug via [email protected]
would also allow the package to migrate, but it might be worth to give
it a try.
The canonical address is -done rather than -close, although -close also
works. For version-tracking, I believe you also need to mention the
fixed version in the first line of the bug closing email, as I have done
here.
Reference: https://www.debian.org/Bugs/Developer#closing
smcv
--- End Message ---
