[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#990921: marked as done (unblock: bouncycastle/1.68-2)

Your message dated Sun, 11 Jul 2021 18:43:59 +0000
with message-id <E1m2eQp-0002x7-EE@respighi.debian.org>
and subject line unblock bouncycastle
has caused the Debian Bug report #990921,
regarding unblock: bouncycastle/1.68-2
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 owner@bugs.debian.org
immediately.)


-- 
990921: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990921
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock

Please unblock package bouncycastle

  * Update poms for upstream version 1.68 (Closes: #988486)
(change by tony mancill)

Quoting Tony in #988486:
  Now that this is fixed in unstable, any thoughts from the Java Team
  about whether I should request an unblock from the Release Team for this
  bug for Bullseye?  It may prevent some potential confusion but is
  otherwise, as far as I can tell, purely cosmetic.  Thus, although there
  is no risk, I'm not certain about how to justify the request.

  I could wait and request an update via s-p-u.


Doing s-p-u later would be more hassle than unblocking a package
that has been for 2 months in unstable, IMHO for bullseye this
is now or never.

--- End Message ---
--- Begin Message --- 
Unblocked.

--- End Message ---
Reply to: