Your message dated Thu, 22 May 2025 08:20:18 +0000 with message-id <5a18dbb3de8b29ade9692945ff469...@posteo.de> and subject line wontfix has caused the Debian Bug report #1061977, regarding bugs.debian.org: "done" for the future not working 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 ow...@bugs.debian.org immediately.) -- 1061977: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061977 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: bugs.debian.org Severity: minor Dear Maintainer, I tried to schedule a bug to be closed at a specific version for a version that has not yet reached Debian repo. Here is the example: <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990343> The bug is fixed in upstream without having a release. The next planed release is "1.4.2". My intention was to do "close 990343 1.4.2" to inform Debian about that so the bug can be closed if "1.4.2" hits the Debian repo. But it did not work. The result is that "fixed in version 1.4.2" is set, but also "done" is set and the ticket closed. >From users perspective this doesn't make sense. Expected behavior is that the ticket is still open and will be automatically closed when 1.4.2 hits the Debian repo. Kind
--- End Message ---
--- Begin Message --- It seems no one will fixing this, because no one sees this as problematic as I do.
--- End Message ---
