Your message dated Sat, 30 Apr 2005 19:24:41 +0200
with message-id <[EMAIL PROTECTED]>
and subject line statdataml: FTBFS: Build-Depends cannot be fulfilled in sarge
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; 25 Apr 2005 09:09:42 +0000
>From [EMAIL PROTECTED] Mon Apr 25 02:09:42 2005
Return-path: <[EMAIL PROTECTED]>
Received: from c158131.adsl.hansenet.de (localhost.localdomain) 
[213.39.158.131] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1DPzb4-0004SC-00; Mon, 25 Apr 2005 02:09:42 -0700
Received: from aj by localhost.localdomain with local (Exim 4.50)
        id 1DPzb4-0007Ys-5q; Mon, 25 Apr 2005 11:09:42 +0200
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
From: Andreas Jochens <[EMAIL PROTECTED]>
Subject: statdataml: FTBFS: Build-Depends cannot be fulfilled in sarge
Message-Id: <[EMAIL PROTECTED]>
Date: Mon, 25 Apr 2005 11:09:42 +0200
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=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 

Package: statdataml
Version: 1.0.9-1
Severity: serious
Tags: sarge

When building 'statdataml' in a clean 'testing' chroot,
I get the following error:

Building statdataml testing main amd64...
Reading Package Lists...
Building Dependency Tree...
E: Build-dependencies for statdataml could not be satisfied.

This is because r-base-dev depends on libreadline5-dev and 
octave2.1-headers depends on libreadline4-dev. 

Since libreadline4-dev and libreadline5-dev conflict with each other, 
r-base-dev and octave2.1-headers cannot be installed at the same time.

Regards
Andreas Jochens

---------------------------------------
Received: (at 306248-done) by bugs.debian.org; 30 Apr 2005 17:24:43 +0000
>From [EMAIL PROTECTED] Sat Apr 30 10:24:43 2005
Return-path: <[EMAIL PROTECTED]>
Received: from c223009.adsl.hansenet.de (localhost.localdomain) [213.39.223.9] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1DRvhr-0001hK-00; Sat, 30 Apr 2005 10:24:43 -0700
Received: from aj by localhost.localdomain with local (Exim 4.50)
        id 1DRvhp-0000jy-90; Sat, 30 Apr 2005 19:24:41 +0200
Date: Sat, 30 Apr 2005 19:24:41 +0200
To: Lars Wirzenius <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]
Subject: Re: statdataml: FTBFS: Build-Depends cannot be fulfilled in sarge
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[EMAIL PROTECTED]>
User-Agent: Mutt/1.5.9i
From: Andreas Jochens <[EMAIL PROTECTED]>
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: 

On 05-Apr-30 17:51, Lars Wirzenius wrote:
> Andreas Jochens <[EMAIL PROTECTED]>:
> > Building statdataml testing main amd64...
> > Reading Package Lists...
> > Building Dependency Tree...
> > E: Build-dependencies for statdataml could not be satisfied.
> 
> I don't seem to be able to reproduce this with sarge or sid pbuilder
> setups, or in a sarge or sid chroot, all on i386. For me, the package 
> builds without problems.

This is correct. A new version of octave2.1 which depends on 
libreadline5-dev has entered sarge. Consequently the problem
is solved, thanks.

Regards
Andreas Jochens


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

Reply via email to