[pkg-cryptsetup-devel] Bug#1020553: marked as done (cryptsetup-suspend: resume from suspend to RAM stuck after upgrading to 2:2.5.0-3)

[Debian Bug Tracking System]

Your message dated Tue, 04 Oct 2022 01:18:58 +0000
with message-id <E1ofWaI-005Xqb-6l at fasolo.debian.org>
and subject line Bug#1020553: fixed in cryptsetup 2:2.5.0-4
has caused the Debian Bug report #1020553,
regarding cryptsetup-suspend: resume from suspend to RAM stuck after upgrading to 2:2.5.0-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 owner at bugs.debian.org
immediately.)


-- 
1020553: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020553
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Yuya Nishihara <yuya at tcha.org>
Subject: cryptsetup-suspend: resume from suspend to RAM stuck after upgrading to 2:2.5.0-3
Date: Fri, 23 Sep 2022 16:47:19 +0900
Size: 19013
URL: <http://alioth-lists.debian.net/pipermail/pkg-cryptsetup-devel/attachments/20221004/77416aa1/attachment.eml>
-------------- next part --------------
An embedded message was scrubbed...
From: Debian FTP Masters <ftpmaster at ftp-master.debian.org>
Subject: Bug#1020553: fixed in cryptsetup 2:2.5.0-4
Date: Tue, 04 Oct 2022 01:18:58 +0000
Size: 6736
URL: <http://alioth-lists.debian.net/pipermail/pkg-cryptsetup-devel/attachments/20221004/77416aa1/attachment-0001.eml>