Your message dated Tue, 19 Nov 2024 13:53:24 +0900
with message-id <73d4d3996a36ffe59e2a3f1d18462...@duckcorp.org>
and subject line RM: dxvk -- RoQA; rc-buggy
has caused the Debian Bug report #1081216,
regarding RM: dxvk -- RoQA; rc-buggy
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.)
--
1081216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081216
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dxvk
Severity: important
User: helm...@debian.org
Usertags: sidremove
Dear maintainer,
I suggest removing dxvk from Debian for the following reasons:
* It accumulated one RC-bug:
+ #982159: dxvk: Dependency on development version of WINE might not be
justified
Last modified: 1 year, 8 months
* It is not part of bookworm or trixie 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 helm...@debian.org
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: dxvk -- RoM; rc-buggy
Control: reassign -1 ftp.debian.org
Control: affects -1 + src:dxvk
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 <hel...@subdivi.de> for assistance.
--- End Message ---
--- Begin Message ---
Quack,
As the maintainer of this package I object to this removal. Honestly I
just don't see the point of this request. Maintainers of
wine-development opened #988246 to block the package from being
released, and since it is a build-dependency for the same reason dxvk is
blocked, that does not make it a broken package. And in fact I'm using
it regularly and I can assure you it works fine.
As mentioned in the RC bug it was not possible to use stable version
since newer dxvk version required a more recent wine not available at
the time. In #1077188 someone mentioned things have change and I'm
looking into it now.
It feels like this bug report was submitted automatically without any
check of the context and that not very useful IMHO.
Anyway, closing.
\_O<
--
Marc Dequènes
--- End Message ---
