Your message dated 26 Oct 1999 10:48:23 +1000
with message-id <[EMAIL PROTECTED]>
and subject line display-dhammapada is not native
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Darren Benham
(administrator, Debian Bugs database)
--------------------------------------
Received: (at maintonly) by bugs.debian.org; 5 Sep 1999 03:22:57 +0000
Received: (qmail 14088 invoked from network); 5 Sep 1999 03:22:56 -0000
Received: from adsl-63-193-116-241.dsl.snfc21.pacbell.net (HELO kitenet.net)
(63.193.116.241)
by master.debian.org with SMTP; 5 Sep 1999 03:22:56 -0000
Received: (qmail 30356 invoked by uid 500); 5 Sep 1999 03:22:21 -0000
Date: 5 Sep 1999 03:22:20 -0000
Message-ID: <[EMAIL PROTECTED]>
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: this package is not native
Package: display-dhammapada
Version: debian unstable as of 4 Sep 99
It seems that display-dhammapada is not really a debian native package;
examination
of the copyright file shows that the sources for it were obtained from
elsewhere, not written by a debian developer. And yet, in the debian
archive, there is only a display-dhammapada.tar.gz, not a
display-dhammapada.orig.tar.gz.
Any package that's not a native package is supposed to have a .orig.tar.gz
file and an accompanying .diff.gz file that contains any debian changes.
(See section 3.3 of the policy manual for details.) This has a number of
benefits, including letting people see what changes were made for debian,
and making it easy to apply those changes to new upstream versions of the
package.
Please download the pristine upstream source of display-dhammapada, and use it
to
create a .orig.tar.gz file, and then rebuild your package with
"dpkg-buildpackage -sa" so that the .orig.tar.gz file will be uploaded to
the debian archive.
(I realize there might be situtations where doing that is not possible, or I
may have misidentified your package as having this problem when it is really
a native package. If so, simply close this semi-autogenerated bug report.)
---------------------------------------
Received: (at 44260-done) by bugs.debian.org; 26 Oct 1999 00:36:39 +0000
Received: (qmail 28047 invoked from network); 26 Oct 1999 00:36:38 -0000
Received: from vasquez.zip.com.au ([EMAIL PROTECTED])
by master.debian.org with SMTP; 26 Oct 1999 00:36:38 -0000
Received: from localhost (banana19.zip.com.au [61.8.30.51])
by vasquez.zip.com.au (8.9.2/8.9.1) with ESMTP id KAA13216
for <[EMAIL PROTECTED]>; Tue, 26 Oct 1999 10:36:18 +1000 (EST)
Received: from gg by localhost with local (Exim 2.05 #1 (Debian))
id 11fuml-0000TC-00; Tue, 26 Oct 1999 10:48:23 +1000
To: [EMAIL PROTECTED]
Subject: display-dhammapada is not native
From: Kevin Ryde <[EMAIL PROTECTED]>
Date: 26 Oct 1999 10:48:23 +1000
Message-ID: <[EMAIL PROTECTED]>
Lines: 2
User-Agent: Gnus/5.07009701 (Pterodactyl Gnus v0.97.1) Emacs/20.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Starting with version 0.20, now uploaded, this package has become
non-native.
