Your message dated Mon, 24 Jul 2017 21:10:03 +0900
with message-id <[email protected]>
and subject line Re: Bug#628655: sigscheme: Please update libgcroots to 0.2.3.
has caused the Debian Bug report #628655,
regarding sigscheme: Please update libgcroots to 0.2.3.
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.)


-- 
628655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=628655
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: sigscheme
Version:0.8.5-2
Severity: wishlist
X-Debbugs-CC: [email protected], [email protected]

Hi,

The new version of sigscheme is not released,
but new version of libgcroots included in sigscheme is released.
Would you upload sigscheme which updated libgcroots?
uim 1.7.0 needs libgcroots 0.2.3.

http://code.google.com/p/uim/source/browse/#svn%2Ftags%2Flibgcroots-0.2.3

Best regards,
 Nobuhiro

--
Nobuhiro Iwamatsu
   iwamatsu at {nigauri.org / debian.org}
   GPG ID: 40AD1FA6



--- End Message ---
--- Begin Message ---
Control: affects -1 = src:uim
Control: tags -1 = upstream wontfix

On Tue, May 31, 2011 at 01:36:04PM +0900, Nobuhiro Iwamatsu wrote:
> The new version of sigscheme is not released,
> but new version of libgcroots included in sigscheme is released.
> Would you upload sigscheme which updated libgcroots?
> uim 1.7.0 needs libgcroots 0.2.3.

libgcroots' diff between 0.2.2 and 0.2.3 is just version number.
Patched uim needs libgcroots 0.2.2 and upstream is dormant for years.
So let's close it.
-- 
Regards,
        dai

GPG Fingerprint = 0B29 D88E 42E6 B765 B8D8 EA50 7839 619D D439 668E

Attachment: signature.asc
Description: PGP signature


--- End Message ---

Reply via email to