When a bug is a bug?

To: Debian Policy <debian-policy@lists.debian.org>
Cc: octave@packages.debian.org
Subject: When a bug is a bug?
From: Santiago Vila <sanvila@unex.es>
Date: Tue, 7 Apr 1998 14:54:41 +0200 (CEST)
Message-id: <[🔎] Pine.LNX.3.96.980407144745.4057A-100000@cantor.unex.es>

-----BEGIN PGP SIGNED MESSAGE-----

I have a great difficulty in convincing the Debian octave maintainer that
Bug #20561 is a bug. I have explained him in great detail why it is a bug
but he still says it is not and even *refuses* to discuss about it.

May I also close all my bugs by saying they are not bugs?

I think we need *urgently* some clear guidelines for managing bugs.

Thanks.

-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: latin1

iQCVAgUBNSoiACqK7IlOjMLFAQE99gQAsB94zVvJ8VsMO84+jR0f2hWXf2TJEUk1
UzEJ5Omo+J1JJ5OzXnHjZr5P1Zc2UjydbDSWnPKqZfOwfi+iN6A5Sod2UgusHiTZ
A95+t2Vq7S3eInX83rOVGDiDf6b+Gt+91nJ17F99+ENzvnoHI5ubHpn9ckrznCka
FLjmECT4sIo=
=ScvZ
-----END PGP SIGNATURE-----


--
To UNSUBSCRIBE, email to debian-policy-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Reply to:

Follow-Ups:
- Re: When a bug is a bug?
  - From: Manoj Srivastava <srivasta@datasync.com>
- Re: When a bug is a bug?
  - From: Ian Jackson <ian@chiark.greenend.org.uk>

Prev by Date: Re: Conffiles and Configuration files (again)
Next by Date: Re: IMPORTANT: calling ldconfig in maintainer scripts
Previous by thread: Re: Namespace pollution
Next by thread: Re: When a bug is a bug?
Index(es):
- Date
- Thread