Debian bug report logs - #1752, boring messages

Subject: Bug#1752: inewsinn recommends trn
Reply-To: Bdale Garbee <bdale@gag.com>, debian-bugs@pixar.com
Resent-From: Bdale Garbee <bdale@gag.com>
Resent-To: debian-devel@pixar.com
Resent-Date: Tue, 24 Oct 1995 15:48:03 GMT
Resent-Message-ID: <debian-bugs-handler.1752.B10241537540@pixar.com>
Resent-Sender: iwj10@cus.cam.ac.uk
X-Debian-PR-Package: inewsinn
X-Debian-PR-Keywords: 
Received: via spool for debian-bugs; Tue, 24 Oct 1995 15:48:03 GMT
Received: with rfc822 via encapsulated-mail; Tue, 24 Oct 1995 15:37:52 GMT
Received: from pixar.com by mongo.pixar.com with smtp
	(Smail3.1.28.1 #15) id m0t7lO4-000BeIC; Tue, 24 Oct 95 08:35 PDT
Received: from chunks.gag.com by pixar.com with SMTP id AA06018
  (5.67b/IDA-1.5 for debian-bugs-pipe@mongo.pixar.com); Tue, 24 Oct 1995 08:35:04 -0700
Received: (from bdale@localhost) by chunks.gag.com (8.6.12/8.6.12) id JAA07241 for debian-bugs@pixar.com; Tue, 24 Oct 1995 09:33:04 -0600
Date: Tue, 24 Oct 1995 09:33:04 -0600
From: Bdale Garbee <bdale@gag.com>
Message-Id: <199510241533.JAA07241@chunks.gag.com>
To: debian-bugs@pixar.com

Package: inewsinn
Version: 1.4sec-7

I find it *really* annoying that inewsinn recommends trn, since I want tin,
which requires inewsinn or inn, but don't want trn.  This makes me have to
go through conflict resolution every time.

Isn't it sufficient that trn and tin require inn or inewsinn?

Bdale

From: iwj10@thor.cam.ac.uk (Ian Jackson)
To: Bdale Garbee <bdale@gag.com>
Subject: Bug#1752: Acknowledgement (was: inewsinn recommends trn)
In-Reply-To: <199510241533.JAA07241@chunks.gag.com>
References: <199510241533.JAA07241@chunks.gag.com>

Thank you for the problem report you have sent regarding Debian GNU/Linux.
This is an automatically generated reply, to let you know your message has
been received.  It is being forwarded to the developers' mailing list for
their attention; they will reply in due course.

If you wish to submit further information on your problem, please send
it to debian-bugs@pixar.com, but please ensure that the Subject
line of your message starts with "Bug#1752" or "Re: Bug#1752" so that
we can identify it as relating to the same problem.

Please do not reply to the address at the top of this message,
unless you wish to report a problem with the bug-tracking system.

Ian Jackson
(maintainer, debian-bugs)