Your message dated Fri, 12 Feb 2021 20:47:43 +0100
with message-id <ba1a655a-d8b1-d1a6-16bf-e2838c651...@debian.org>
and subject line Re: Bug#982606: unblock: win32-loader/0.10.4
has caused the Debian Bug report #982606,
regarding unblock: win32-loader/0.10.4
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.)
--
982606: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982606
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian....@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: debian-b...@lists.debian.org
Please unblock package win32-loader in its 0.10.4 version
[ Reason ]
win32-loader is one of the rare packages always blocked, because it has a
'byhand' counterpart per release: `/debian/tools/win32-loader/{release}`, and
therefore needs a manual action by FTP masters in sync ("around the time of")
with the unblock.
[ Impact ]
It's been since 0.10.1 (September 2020) that it hasn't been migrated, and I (as
co-maintainer), want the 0.10.4 changes in for Bullseye.
[ Tests ]
There are no significant error reports for the version in unstable, I deem
this version as really safe to migrate. If it were a normal package, it would
have migrated for every version.
Please CC ftpmas...@debian.org when granting this unblock, for them to proceed
with their magic.
Best regards, and thanks for your work,
OdyX
unblock win32-loader/0.10.4
P.S. Yes. That's an almost verbatim copy of #967048
--- End Message ---
--- Begin Message ---
Hi Didier,
On 12-02-2021 14:01, Didier 'OdyX' Raboud wrote:
> Please unblock package win32-loader in its 0.10.4 version
Sure thing.
As discussed last time on IRC, how about you manage this yourself via RC
bugs? The idea would be that you always have an RC bug against
win32-loader. If you want to have win32-loader migrate, you `notfound`
the version you want to migrate and `found` the next version. That way I
think you can manage without the involvement of the release team.
Paul
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
