Your message dated 17 Apr 2002 22:33:56 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in quickppp 1.2.0-1.1
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.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at maintonly) by bugs.debian.org; 5 Sep 1999 03:23:06 +0000
Received: (qmail 14216 invoked from network); 5 Sep 1999 03:23:01 -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:23:01 -0000
Received: (qmail 30490 invoked by uid 500); 5 Sep 1999 03:22:22 -0000
Date: 5 Sep 1999 03:22:22 -0000
Message-ID: <[EMAIL PROTECTED]>
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: this package is not native

Package: quickppp
Version: debian unstable as of 4 Sep 99

It seems that quickppp 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 quickppp.tar.gz, not a quickppp.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 quickppp, 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 44292-done) by bugs.debian.org; 18 Apr 2002 04:35:17 +0000
>From [EMAIL PROTECTED] Wed Apr 17 23:35:16 2002
Return-path: <[EMAIL PROTECTED]>
Received: from jagor.srce.hr [161.53.2.130] (root)
        by master.debian.org with esmtp (Exim 3.12 1 (Debian))
        id 16y3dc-0006zQ-00; Wed, 17 Apr 2002 23:35:16 -0500
Received: (from [EMAIL PROTECTED])
        by jagor.srce.hr (8.9.3/8.9.3) id GAA07338
        for [EMAIL PROTECTED]; Thu, 18 Apr 2002 06:35:06 +0200 (MEST)
Received: from fuzz ([EMAIL PROTECTED] [193.198.129.87])
        by jagor.srce.hr (8.9.3/8.9.3) with ESMTP id GAA07262;
        Thu, 18 Apr 2002 06:34:46 +0200 (MEST)
Received: from mvela by fuzz with local (Exim 3.35 #1 (Debian))
        id 16y3ar-0000R5-00; Thu, 18 Apr 2002 06:32:25 +0200
From: Matej Vela <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED], [EMAIL PROTECTED],
        [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Fixed in quickppp 1.2.0-1.1
Date: 17 Apr 2002 22:33:56 +0200
Message-ID: <[EMAIL PROTECTED]>
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Lines: 13
Sender: Matej Vela <[EMAIL PROTECTED]>
X-Virus-Scanned: by AMaViS perl-11
Delivered-To: [EMAIL PROTECTED]

Now that quickppp is orphaned, NMU fixed bugs can be closed.

Here is the relevant changelog entry:

  quickppp (1.2.0-1.1) unstable; urgency=low

    * Non-Maintainer upload
    * Made package FHS compliant (Closes: Bug#91008, Bug#91633)
    * New upstream release (Closes: Bug#94258)
    * Not a native package (Closes: Bug#44292)
    * Added a slightly better man page

   -- Gergely Nagy <[EMAIL PROTECTED]>  Tue, 17 Apr 2001 17:28:39 +0200


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to