Your message dated Mon, 17 Jan 2005 13:23:47 +0000
with message-id <[EMAIL PROTECTED]>
and subject line [EMAIL PROTECTED]: Bug#283145: 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; 9 Nov 2004 23:52:06 +0000
>From [EMAIL PROTECTED] Tue Nov 09 15:52:06 2004
Return-path: <[EMAIL PROTECTED]>
Received: from through.apexcovantage.com (through.acv.apexcovantage.com)
[65.166.131.3]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CRfmP-00027k-00; Tue, 09 Nov 2004 15:52:05 -0800
Received: from apex.acv.apexcovantage.com ([192.168.0.1])
by through.acv.apexcovantage.com
(8.12.8/8.12.8/apexcovantage-gateway-1.0) with ESMTP id iA9Nps3I023791;
Tue, 9 Nov 2004 18:51:54 -0500
Received: from soup (soup.acv.apexcovantage.com [192.168.0.5])
by apex.acv.apexcovantage.com (8.12.8/8.12.8/ads-apexcovantage-hub-1.1)
with ESMTP id iA9Nps4R020343;
Tue, 9 Nov 2004 18:51:54 -0500
Received: from ejb by soup with local (Exim 4.34)
id 1CRfmD-0004vG-Rr; Tue, 09 Nov 2004 18:51:53 -0500
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Jay Berkenbilt <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: vips7.8: this package should not be included in sarge
X-Mailer: reportbug 2.99.5
Date: Tue, 09 Nov 2004 18:51:53 -0500
Message-Id: <[EMAIL PROTECTED]>
X-Apex-MailScanner-Information: Scanned by Apex with MailScanner
X-Apex-MailScanner: Found to be clean
X-MailScanner-From: [EMAIL PROTECTED]
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level:
Package: vips7.8
Severity: normal
Vips 7.10 has been released and uploaded to unstable (though it still
has to appear in the override file). After discussion with upstream,
we decided that we don't want vips7.8 to appear in sarge at all, even
recognizing that vips7.10 may not make it through the override process
fast enough.
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.26-1-686-smp
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8
---------------------------------------
Received: (at 280523-done) by bugs.debian.org; 17 Jan 2005 13:23:54 +0000
>From [EMAIL PROTECTED] Mon Jan 17 05:23:54 2005
Return-path: <[EMAIL PROTECTED]>
Received: from sorrow.cyrius.com [65.19.161.204]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CqWrK-0000If-00; Mon, 17 Jan 2005 05:23:54 -0800
Received: by sorrow.cyrius.com (Postfix, from userid 10)
id 0862564D45; Mon, 17 Jan 2005 13:23:51 +0000 (UTC)
Received: by deprecation.cyrius.com (Postfix, from userid 1000)
id 8B96F4EF41; Mon, 17 Jan 2005 13:23:47 +0000 (GMT)
Date: Mon, 17 Jan 2005 13:23:47 +0000
From: Martin Michlmayr <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: [EMAIL PROTECTED]: Bug#283145: fixed]
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.6+20040907i
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-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
X-Spam-Level:
it's gone
----- Forwarded message from Debian Archive Maintenance <[EMAIL PROTECTED]>
-----
From: Debian Archive Maintenance <[EMAIL PROTECTED]>
Subject: Bug#283145: fixed
Date: Sun, 16 Jan 2005 22:57:39 -0500
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED], [EMAIL PROTECTED]
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:
libvips7.8 | 7.8.14-1 | alpha, arm, hppa, i386, ia64, m68k, mips, mipsel,
powerpc, s390, sparc
libvips7.8-dev | 7.8.14-1 | alpha, arm, hppa, i386, ia64, m68k, mips, mipsel,
powerpc, s390, sparc
libvips7.8-doc | 7.8.14-1 | all
libvips7.8-tools | 7.8.14-1 | alpha, arm, hppa, i386, ia64, m68k, mips,
mipsel, powerpc, s390, sparc
vips7.8 | 7.8.14-1 | source
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.
Anthony Towns (the ftpmaster behind the curtain)
----- End forwarded message -----
--
Martin Michlmayr
http://www.cyrius.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
