Your message dated Thu, 27 Nov 2025 15:06:31 +0100
with message-id <[email protected]>
and subject line Re: Bug#1121267: Should gourmand be removed from unstable?
has caused the Debian Bug report #1121267,
regarding Should gourmand be removed from unstable?
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.)
--
1121267: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1121267
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: gourmand
Severity: important
User: [email protected]
Usertags: sidremove
Dear maintainer,
I suggest removing gourmand from Debian for the following reasons:
* It accumulated one RC-bug:
+ #1074472: sqlalchemy.exc.ArgumentError: expected schema argument to be a
string
Last modified: 1 year, 10 days
* It is not part of trixie or forky and is not a key package.
This bug serves as a pre-removal warning. After one month, the bug will be
reassigned to ftp.debian.org to actually request removal of the package.
In case the package should be kept in unstable, please evaluate each of the
RC-bugs listed above.
* If the bug is meant to permanently prevent the package from entering testing
or a stable release, but this package should stay part of unstable, please
add a usertag:
user [email protected]
usertags NNN + sidremove-ignore
* If the bug no longer applies, please close it. If it is closed, check
whether the fixed version is correct and adjust if necessary.
* Is the bug really release-critical? If not, please downgrade.
* If the bug still applies, please send a status update at least once a year.
Once all of the mentioned RC bugs have been acted upon in one way or another,
please close this bug.
In case the package should be removed from unstable, you may reassign this
bug report:
Control: severity -1 normal
Control: retitle -1 RM: gourmand -- RoM; rc-buggy
Control: reassign -1 ftp.debian.org
Control: affects -1 + src:gourmand
Alternatively, you may wait a month and have it reassigned.
In case you disagree with the above, please add a wontfix tag to this bug.
Control: tags -1 + wontfix
Doing so will also prevent automatic reassignment.
Kind regards
A tool for automatically removing packages from unstable
This bug report has been automatically filed with little human intervention.
If the filing is unclear or in error, don't hesitate to contact
Helmut Grohne <[email protected]> for assistance.
--- End Message ---
--- Begin Message ---
user [email protected]
usertags 1121267 + sidremove-ignore
thanks
On 23 nov. 2025 21:47, Helmut Grohne <[email protected]> wrote:
> Source: gourmand
> Severity: important
> User: [email protected]
> Usertags: sidremove
>
> Dear maintainer,
Hi Helmut,
> I suggest removing gourmand from Debian for the following reasons:
I want to keep gourmand until the sqlalchemy bug is fixed.
Christian
--- End Message ---
