Bug#333332: marked as done (evince: Reading from stdin apparently not possible)

Sat Oct 15 08:51:09 UTC 2016

Your message dated Sat, 15 Oct 2016 03:48:25 -0500
with message-id <20161015084825.kexqgy5fkchlbfe4 at knives.aquaticape.us>
and subject line Re: Bug#333332: evince: Reading from stdin apparently not possible
has caused the Debian Bug report #333332,
regarding evince: Reading from stdin apparently not possible
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.)

-- 
333332: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=333332
Debian Bug Tracking System
Contact owner at bugs.debian.org with problems
-------------- next part --------------
An embedded message was scrubbed...
From: Harri Haataja <harriha at mail.student.oulu.fi>
Subject: evince: Reading from stdin apparently not possible
Date: Tue, 11 Oct 2005 14:46:10 +0300
Size: 6321
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20161015/8b15672b/attachment.mht>
-------------- next part --------------
An embedded message was scrubbed...
From: Jason Crain <jason at inspiresomeone.us>
Subject: Re: Bug#333332: evince: Reading from stdin apparently not possible
Date: Sat, 15 Oct 2016 03:48:25 -0500
Size: 2937
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20161015/8b15672b/attachment-0001.mht>