Bug#617958: marked as done (libnotify-bin: Critical notifications should not expire)

Wed Apr 27 19:15:02 BST 2022

Your message dated Wed, 27 Apr 2022 20:11:17 +0200
with message-id <53C29F39-FC84-4C61-B64A-AC22F14CCD9B at getmailspring.com>
and subject line Bug #617958
has caused the Debian Bug report #617958,
regarding libnotify-bin: Critical notifications should not expire
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.)

-- 
617958: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=617958
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: ahiroito <ahiroito at yahoo.com>
Subject: libnotify-bin: Critical notifications should not expire
Date: Sat, 12 Mar 2011 18:06:46 -0300
Size: 2846
URL: <http://alioth-lists.debian.net/pipermail/pkg-gnome-maintainers/attachments/20220427/b1a6d452/attachment.eml>
-------------- next part --------------
An embedded message was scrubbed...
From: Marco Trevisan <marco at trevi.me>
Subject: Bug #617958
Date: Wed, 27 Apr 2022 20:11:17 +0200
Size: 3185
URL: <http://alioth-lists.debian.net/pipermail/pkg-gnome-maintainers/attachments/20220427/b1a6d452/attachment-0001.eml>