Your message dated Tue, 17 Jan 2006 14:58:23 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#348546: fixed
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 submit) by bugs.debian.org; 17 Jan 2006 17:52:25 +0000
>From [EMAIL PROTECTED] Tue Jan 17 09:52:25 2006
Return-path: <[EMAIL PROTECTED]>
Received: from undies.thedogstar.org ([207.210.65.170] helo=mx1.thedogstar.org)
        by spohr.debian.org with esmtp (Exim 4.50)
        id 1Eyv0L-0000UM-Ol
        for [EMAIL PROTECTED]; Tue, 17 Jan 2006 09:52:25 -0800
Received: from 104-55.echostar.pl ([213.156.104.55] helo=quantum)
        by mx1.thedogstar.org with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA:32)
        (Exim 4.50)
        id 1Eyv0G-0001MJ-VW; Wed, 18 Jan 2006 06:52:22 +1300
Received: by quantum (Postfix, from userid 1000)
        id C9109EE9E; Tue, 17 Jan 2006 18:52:15 +0100 (CET)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Marek Habersack <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: Please remove pike7.2 from the unstable distribution
Reply-To: Marek Habersack <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
X-Mailer: reportbug 3.18ubuntu1
Date: Tue, 17 Jan 2006 18:52:15 +0100
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level: 
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02

Package: ftp.debian.org
Severity: normal

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Please remove the pike7.2 source package along with all its binary packages 
from the Debian/unstable distribution. 

The reason for the request is that pike7.2 is legacy code, no longer 
depended upon by any other Debian packages (with the exception of roxen3 
whose removal request should follow soon) and there is little to no demand for 
that version of Pike in general. The current version of Pike is 7.6 with 7.8 
to follow in the near future.

The binary package names produced from the pike7.2 source are:

pike7.2
pike7.2-crypto
pike7.2-gdbm
pike7.2-gl
pike7.2-gtk
pike7.2-gz
pike7.2-image
pike7.2-mysql
pike7.2-odbc
pike7.2-pexts-admintools
pike7.2-pexts-bzip2
pike7.2-pexts-curses
pike7.2-pexts-geoip
pike7.2-pexts-mcrypt
pike7.2-pexts-mhash
pike7.2-pexts-newt
pike7.2-pexts-pcre
pike7.2-pg
pike7.2-sane

thank you,

marek

- -- System Information:
Debian Release: testing/unstable
  APT prefers dapper-updates
  APT policy: (500, 'dapper-updates'), (500, 'dapper-security'), (500, 'dapper')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-12-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFDzS7Oq3909GIf5uoRAixMAJ9xX8Lhthc9X51Fcf1wbLaT2/j3ewCePXse
OuQZ0fgYXDFrVwVKBYatBfA=
=N2gY
-----END PGP SIGNATURE-----

---------------------------------------
Received: (at 348546-close) by bugs.debian.org; 17 Jan 2006 23:02:29 +0000
>From [EMAIL PROTECTED] Tue Jan 17 15:02:29 2006
Return-path: <[EMAIL PROTECTED]>
Received: from jeroen by spohr.debian.org with local (Exim 4.50)
        id 1EyzmR-0006MX-HO; Tue, 17 Jan 2006 14:58:23 -0800
From: Debian Archive Maintenance <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: melanie $Revision: 1.44 $
Cc: [EMAIL PROTECTED], [EMAIL PROTECTED] 
Subject: Bug#348546: fixed
Message-Id: <[EMAIL PROTECTED]>
Sender: Jeroen van Wolffelaar <[EMAIL PROTECTED]>
Date: Tue, 17 Jan 2006 14:58:23 -0800
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level: 
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02

We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

      pike | 7.2.580-3.1 | m68k
      pike |  7.2.580-4 | alpha, arm, hppa, i386, ia64, mips, mipsel, powerpc, 
s390, sparc
pike-crypto | 7.2.580-3.1 | m68k
pike-crypto |  7.2.580-4 | alpha, arm, hppa, i386, ia64, mips, mipsel, powerpc, 
s390, sparc
 pike-gdbm | 7.2.580-3.1 | m68k
 pike-gdbm |  7.2.580-4 | alpha, arm, hppa, i386, ia64, mips, mipsel, powerpc, 
s390, sparc
   pike-gz | 7.2.580-3.1 | m68k
   pike-gz |  7.2.580-4 | alpha, arm, hppa, i386, ia64, mips, mipsel, powerpc, 
s390, sparc
pike-image | 7.2.580-3.1 | m68k
pike-image |  7.2.580-4 | alpha, arm, hppa, i386, ia64, mips, mipsel, powerpc, 
s390, sparc
pike-mysql | 7.2.580-3.1 | m68k
pike-mysql |  7.2.580-4 | alpha, arm, hppa, i386, ia64, mips, mipsel, powerpc, 
s390, sparc
   pike-pg | 7.2.580-3.1 | m68k
   pike-pg |  7.2.580-4 | alpha, arm, hppa, i386, ia64, mips, mipsel, powerpc, 
s390, sparc
   pike7.2 | 7.2.580-3.1 | m68k
   pike7.2 |  7.2.580-4 | source, alpha, arm, hppa, i386, ia64, mips, mipsel, 
powerpc, s390, sparc
pike7.2-crypto | 7.2.580-3.1 | m68k
pike7.2-crypto |  7.2.580-4 | alpha, arm, hppa, i386, ia64, mips, mipsel, 
powerpc, s390, sparc
pike7.2-gdbm | 7.2.580-3.1 | m68k
pike7.2-gdbm |  7.2.580-4 | alpha, arm, hppa, i386, ia64, mips, mipsel, 
powerpc, s390, sparc
pike7.2-gl | 7.2.580-3.1 | m68k
pike7.2-gl |  7.2.580-4 | alpha, arm, hppa, i386, ia64, mips, mipsel, powerpc, 
s390, sparc
pike7.2-gtk | 7.2.580-3.1 | m68k
pike7.2-gtk |  7.2.580-4 | alpha, arm, hppa, i386, ia64, mips, mipsel, powerpc, 
s390, sparc
pike7.2-gz | 7.2.580-3.1 | m68k
pike7.2-gz |  7.2.580-4 | alpha, arm, hppa, i386, ia64, mips, mipsel, powerpc, 
s390, sparc
pike7.2-image | 7.2.580-3.1 | m68k
pike7.2-image |  7.2.580-4 | alpha, arm, hppa, i386, ia64, mips, mipsel, 
powerpc, s390, sparc
pike7.2-mysql | 7.2.580-3.1 | m68k
pike7.2-mysql |  7.2.580-4 | alpha, arm, hppa, i386, ia64, mips, mipsel, 
powerpc, s390, sparc
pike7.2-odbc | 7.2.580-3.1 | m68k
pike7.2-odbc |  7.2.580-4 | alpha, arm, hppa, i386, ia64, mips, mipsel, 
powerpc, s390, sparc
pike7.2-pg | 7.2.580-3.1 | m68k
pike7.2-pg |  7.2.580-4 | alpha, arm, hppa, i386, ia64, mips, mipsel, powerpc, 
s390, sparc
pike7.2-sane | 7.2.580-3.1 | m68k
pike7.2-sane |  7.2.580-4 | alpha, arm, hppa, i386, ia64, mips, mipsel, 
powerpc, s390, sparc

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive (ftp-master.debian.org) and will not propagate to any
mirrors (ftp.debian.org included) until the next cron.daily run at the
earliest.

Packages are never removed from testing by hand.  Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [EMAIL PROTECTED]

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[EMAIL PROTECTED]

Debian distribution maintenance software
pp.
Jeroen van Wolffelaar (the ftpmaster behind the curtain)


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

Reply via email to