Your message dated Thu, 10 Feb 2005 16:34:08 +1100
with message-id <[EMAIL PROTECTED]>
and subject line tagging 292304
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; 26 Jan 2005 08:52:54 +0000
>From [EMAIL PROTECTED] Wed Jan 26 00:52:54 2005
Return-path: <[EMAIL PROTECTED]>
Received: from ns1.u-strasbg.fr [130.79.200.1] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1Ctiuz-0004Ym-00; Wed, 26 Jan 2005 00:52:54 -0800
Received: from sokaris.u-strasbg.fr (sokaris.u-strasbg.fr 
[IPv6:2001:660:2402::101])
          by ns1.u-strasbg.fr (8.12.9p2/jtpda-5.4) with ESMTP id j0Q8qpUQ042731
          for <[EMAIL PROTECTED]>; Wed, 26 Jan 2005 09:52:51 +0100 (CET)
Received: from subrosa.u-strasbg.fr (subrosa.u-strasbg.fr [130.79.188.35])
          by sokaris.u-strasbg.fr (8.12.9/jtpda-5.4) with SMTP id j0Q8qpBE000968
          ; Wed, 26 Jan 2005 09:52:51 +0100 (CET)
Message-Id: <[EMAIL PROTECTED]>
Received: by subrosa.u-strasbg.fr (sSMTP sendmail emulation); Wed, 26 Jan 2005 
09:53:08 +0100
From: "Marc Chantreux" <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: libembperl-perl: Apache/Server.pm ( dropped in libapache2-mod-perl2
 1.999.20-1 ) required
X-Mailer: reportbug 3.2
Date: Wed, 26 Jan 2005 09:53:08 +0100
X-Greylist: Message not sent from an IPv4 address, not delayed by 
milter-greylist-1.5.3 (ns1.u-strasbg.fr [IPv6:2001:660:2402::1]); Wed, 26 Jan 
2005 09:52:51 +0100 (CET)
X-Antivirus: scanned by sophos at u-strasbg.fr
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=-7.3 required=4.0 tests=BAYES_00,HAS_PACKAGE,
        MSGID_FROM_MTA_HEADER autolearn=no 
        version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 

Package: libembperl-perl
Version: 2.0debian-4
Severity: grave
Justification: renders package unusable


Hi,

Embperl depends on Apache/Server.pm that is dropped in the last version
of modperl2 ( libapache2-mod-perl2 1.999.20-1 ).

Other packages have the same problem :

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=292029

thanks and regards


-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-1-386
Locale: LANG=fr_FR, LC_CTYPE=fr_FR (charmap=ISO-8859-1)

Versions of packages libembperl-perl depends on:
ii  libc6                       2.3.2.ds1-20 GNU C Library: Shared libraries an
ii  libwww-perl                 5.803-3      WWW client/server library for Perl
ii  libxml2                     2.6.11-5     GNOME XML library
ii  libxslt1.1                  1.1.8-5      XSLT processing library - runtime 
ii  perl                        5.8.4-5      Larry Wall's Practical Extraction 
ii  perl-base [perlapi-5.8.4]   5.8.4-5      The Pathologically Eclectic Rubbis
ii  perl-modules [libcgi-pm-per 5.8.4-5      Core Perl modules
ii  zlib1g                      1:1.2.2-3    compression library - runtime

-- no debconf information

---------------------------------------
Received: (at 292304-done) by bugs.debian.org; 10 Feb 2005 05:34:56 +0000
>From [EMAIL PROTECTED] Wed Feb 09 21:34:56 2005
Return-path: <[EMAIL PROTECTED]>
Received: from emu.urnet.com.au [203.7.149.10] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1Cz6yd-0001cf-00; Wed, 09 Feb 2005 21:34:55 -0800
Received: from lambast.inside.urnet.com.au ([10.0.6.19])
        by emu.urnet.com.au with esmtp (Exim 3.35 #1 (Debian))
        id 1Cz6xu-0004Us-00; Thu, 10 Feb 2005 16:34:10 +1100
Received: from localhost ([127.0.0.1] helo=lambast.inside.urnet.com.au)
        by lambast.inside.urnet.com.au with esmtp (Exim 3.36 #1 (Debian))
        id 1Cz6xs-0006A8-00; Thu, 10 Feb 2005 16:34:08 +1100
Date: Thu, 10 Feb 2005 16:34:08 +1100
Message-ID: <[EMAIL PROTECTED]>
From: Angus Lees <[EMAIL PROTECTED]>
To: Colin Watson <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]
Subject: Re: tagging 292304
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
User-Agent: Wanderlust/2.10.1 (Watching The Wheels) XEmacs/21.4 (Corporate 
Culture)
X-NSA-Fodder: COSCO JFK Ft. Bragg Legion of Doom Noriega nuclear Ft. Knox spy
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
X-MailScanner: Found to be clean
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=-3.0 required=4.0 tests=BAYES_00 autolearn=no 
        version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 

At Wed, 9 Feb 2005 15:45:30 +0000, Colin Watson wrote:
> On Wed, Feb 09, 2005 at 04:54:20PM +1100, Angus Lees wrote:
> > # Automatically generated email from bts, devscripts version 2.8.5
> > tags 292304 + sarge
> 
> libembperl-perl is not in sarge; why this tag?
> 
>   libembperl-perl | 2.0debian-4 |      unstable | arm
>   libembperl-perl |   2.0rc2-1 |      unstable | m68k
>   libembperl-perl |   2.0rc2-2 |      unstable | source, alpha, hppa, i386, 
> ia64, mips, mipsel, powerpc, s390, sparc

Blah, I forgot.  It /was/ in sarge, but got kicked due to this bug from
a new mod_perl2 API change.  Now I get to do the apache2 build-dep
dance with the buildds to try and get the package back in again.

I guess what I want to say is "this bug is fixed in unstable, please
reinclude this package in sarge" - so I'm closing this bug
accordingly.

-- 
 - Gus


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

Reply via email to