[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

searching for Dirk Eddelbuettel [Mailer-Daemon@master.debian.org: Mail delivery failed: returning message to sender]



----- Forwarded message from Mail Delivery System <Mailer-Daemon@master.debian.org> -----

Delivery-date: Wed, 25 Jul 2001 18:46:18 +0200
X-Failed-Recipients: edd@edd.debian.net
From: Mail Delivery System <Mailer-Daemon@master.debian.org>
To: owner@bugs.debian.org
Subject: Mail delivery failed: returning message to sender
Date: Wed, 25 Jul 2001 11:44:10 -0500

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. The following address(es) failed:

  edd@edd.debian.net:
    retry time not reached for any host after a long failure period

------ This is a copy of the message, including all the headers. ------

Return-path: <owner@bugs.debian.org>
Received: from gecko by master.debian.org with local (Exim 3.12 1 (Debian))
	id 15OTBh-00039f-00; Sun, 22 Jul 2001 19:03:05 -0500
Subject: Bug#106243: /usr/bin/fax uses make. efax should depend on make.
Reply-To: Alexander Stavitsky <astavitsky@yahoo.com>, 106243@bugs.debian.org
Resent-From: Alexander Stavitsky <astavitsky@yahoo.com>
Resent-To: debian-bugs-dist@lists.debian.org
Resent-CC: Dirk Eddelbuettel <edd@debian.org>
Resent-Date: Mon, 23 Jul 2001 00:03:02 GMT
Resent-Message-ID: <handler.106243.B.99584624311569@bugs.debian.org>
Resent-Sender: owner@bugs.debian.org
X-Debian-PR-Message: report 106243
X-Debian-PR-Package: efax
X-Debian-PR-Keywords: sid
X-Loop: owner@bugs.debian.org
Received: via spool by submit@bugs.debian.org id=B.99584624311569
          (code B ref -1); Mon, 23 Jul 2001 00:03:02 GMT
From: Alexander Stavitsky <astavitsky@yahoo.com>
To: Debian Bug Tracking System <submit@bugs.debian.org>
X-Reportbug-Version: 1.21
X-Mailer: reportbug 1.21
Date: Sun, 22 Jul 2001 19:57:09 -0400
Message-Id: <E15OT5x-0001c1-00@owl.zoo>
Delivered-To: submit@bugs.debian.org

Package: efax
Version: 1:0.9a-5
Severity: normal
Tags: sid

/usr/bin/fax uses make (when converting files to tiff format, I think)
If make is not installed the following error is returned:

/usr/bin/fax: make: command not found

It appears to work nevertheless. I do not notice any ill effects so far.
But I think efax should depend on make or at least recommend it.
Or better yet /usr/bin/fax script should not use make at all.



-- System Information
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux owl 2.4.6 #1 Tue Jul 17 08:54:35 EDT 2001 i586
Locale: LANG=C, LC_CTYPE=C

Versions of packages efax depends on:
ii  debconf                       0.9.81     Debian configuration management sy
ii  libc6                         2.2.3-7    GNU C Library: Shared libraries an
ii  libpaperg                     1.0.8.1    Library for handling paper charact




----- End forwarded message -----
----- Forwarded message from Mail Delivery System <Mailer-Daemon@master.debian.org> -----

Delivery-date: Wed, 25 Jul 2001 19:03:30 +0200
X-Failed-Recipients: edd@edd.debian.net
From: Mail Delivery System <Mailer-Daemon@master.debian.org>
To: owner@bugs.debian.org
Subject: Mail delivery failed: returning message to sender
Date: Wed, 25 Jul 2001 12:01:25 -0500

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. The following address(es) failed:

  edd@edd.debian.net:
    retry time not reached for any host after a long failure period

------ This is a copy of the message, including all the headers. ------

Return-path: <owner@bugs.debian.org>
Received: from gecko by master.debian.org with local (Exim 3.12 1 (Debian))
	id 15OmXf-0000mM-00; Mon, 23 Jul 2001 15:43:03 -0500
Subject: Bug#106335: use of type text in template probably in error
Reply-To: Joey Hess <joey@silk.kitenet.net>, 106335-maintonly@bugs.debian.org
Resent-From: Joey Hess <joey@silk.kitenet.net>
Resent-To: Dirk Eddelbuettel <edd@debian.org>
Resent-Date: Mon, 23 Jul 2001 20:43:01 GMT
Resent-Message-ID: <handler.106335.M.9959165703182@bugs.debian.org>
Resent-Sender: owner@bugs.debian.org
X-Debian-PR-Message: report 106335
X-Debian-PR-Package: efax
X-Debian-PR-Keywords: 
X-Loop: owner@bugs.debian.org
Received: via spool by maintonly@bugs.debian.org id=M.9959165703182
          (code M ref -1); Mon, 23 Jul 2001 20:43:01 GMT
To: maintonly@bugs.debian.org
Message-Id: <E15OlOh-0002Ml-00@silk.kitenet.net>
From: Joey Hess <joey@silk.kitenet.net>
Date: Mon, 23 Jul 2001 15:29:43 -0400
Delivered-To: maintonly@bugs.debian.org

Package: efax

This package has a debconf templates file which has one or more templates
marked as type "text". I suspect that in the vast majority of such cases,
it should really be type "note". Comparing the two types:

  * type "text" is not used by many debconf frontends
  * type "note" is supported by all frontends
  * type "text" is never mailed to the admin if he has debconf configured
    to skip over it.
  * type "note" is

The text type is intended only to make debconf display a little scrap of
text on the screen when it is sumulantaneously displaying other questions.
This could theoretically be useful in some frontends, in some rare
occasions. But since no frontend supports it very well, it's very likely
that you're using it in error and should change it to type note.

This report was automatically generated. Close it if it's wrong.



----- End forwarded message -----
----- Forwarded message from Mail Delivery System <Mailer-Daemon@master.debian.org> -----

Delivery-date: Wed, 25 Jul 2001 19:09:22 +0200
X-Failed-Recipients: edd@edd.debian.net
From: Mail Delivery System <Mailer-Daemon@master.debian.org>
To: owner@bugs.debian.org
Subject: Mail delivery failed: returning message to sender
Date: Wed, 25 Jul 2001 12:07:12 -0500

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. The following address(es) failed:

  edd@edd.debian.net:
    retry time not reached for any host after a long failure period

------ This is a copy of the message, including all the headers. ------

Return-path: <owner@bugs.debian.org>
Received: from gecko by master.debian.org with local (Exim 3.12 1 (Debian))
	id 15OmVZ-0000cf-00; Mon, 23 Jul 2001 15:40:53 -0500
Subject: Bug#106327: use of type text in template probably in error
Reply-To: Joey Hess <joey@silk.kitenet.net>, 106327-maintonly@bugs.debian.org
Resent-From: Joey Hess <joey@silk.kitenet.net>
Resent-To: Dirk Eddelbuettel <edd@debian.org>
Resent-Date: Mon, 23 Jul 2001 20:40:52 GMT
Resent-Message-ID: <handler.106327.M.9959164863020@bugs.debian.org>
Resent-Sender: owner@bugs.debian.org
X-Debian-PR-Message: report 106327
X-Debian-PR-Package: acct
X-Debian-PR-Keywords: 
X-Loop: owner@bugs.debian.org
Received: via spool by maintonly@bugs.debian.org id=M.9959164863020
          (code M ref -1); Mon, 23 Jul 2001 20:40:52 GMT
To: maintonly@bugs.debian.org
Message-Id: <E15OlNK-0002Kk-00@silk.kitenet.net>
From: Joey Hess <joey@silk.kitenet.net>
Date: Mon, 23 Jul 2001 15:28:18 -0400
Delivered-To: maintonly@bugs.debian.org

Package: acct

This package has a debconf templates file which has one or more templates
marked as type "text". I suspect that in the vast majority of such cases,
it should really be type "note". Comparing the two types:

  * type "text" is not used by many debconf frontends
  * type "note" is supported by all frontends
  * type "text" is never mailed to the admin if he has debconf configured
    to skip over it.
  * type "note" is

The text type is intended only to make debconf display a little scrap of
text on the screen when it is sumulantaneously displaying other questions.
This could theoretically be useful in some frontends, in some rare
occasions. But since no frontend supports it very well, it's very likely
that you're using it in error and should change it to type note.

This report was automatically generated. Close it if it's wrong.



----- End forwarded message -----

-- 
Digital Electronic Being Intended for Assassination and Nullification



Reply to: