Your message dated Sun, 08 May 2005 19:02:29 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#304124: fixed in unison 2.9.1-2sarge1
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; 4 May 2005 21:05:31 +0000
>From [EMAIL PROTECTED] Wed May 04 14:05:31 2005
Return-path: <[EMAIL PROTECTED]>
Received: from emailhub.stusta.mhn.de (mailout.stusta.mhn.de) [141.84.69.5] 
        by spohr.debian.org with smtp (Exim 3.35 1 (Debian))
        id 1DTR3j-0004Dz-00; Wed, 04 May 2005 14:05:31 -0700
Received: (qmail 8929 invoked from network); 4 May 2005 21:04:59 -0000
Received: from r063144.stusta.swh.mhn.de (10.150.63.144)
  by mailhub.stusta.mhn.de with SMTP; 4 May 2005 21:04:59 -0000
Received: by r063144.stusta.swh.mhn.de (Postfix, from userid 1000)
        id C3787BB4FC; Wed,  4 May 2005 23:04:59 +0200 (CEST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Adrian Bunk <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: unison: Can't fulfill the build dependencies in sarge
X-Mailer: reportbug 3.9
Date: Wed, 04 May 2005 23:04:59 +0200
Message-Id: <[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=-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: unison
Version: 2.9.1-2
Severity: serious
Tags: sarge


The build dependency on ocaml-nox-3.08 can't be fulfilled in sarge.

---------------------------------------
Received: (at 304124-close) by bugs.debian.org; 8 May 2005 23:16:39 +0000
>From [EMAIL PROTECTED] Sun May 08 16:16:39 2005
Return-path: <[EMAIL PROTECTED]>
Received: from newraff.debian.org [208.185.25.31] (mail)
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1DUv0p-0007ou-00; Sun, 08 May 2005 16:16:39 -0700
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
        id 1DUun7-0003DB-00; Sun, 08 May 2005 19:02:29 -0400
From: Sylvain Le Gall <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.55 $
Subject: Bug#304124: fixed in unison 2.9.1-2sarge1
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Sun, 08 May 2005 19:02:29 -0400
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: 

Source: unison
Source-Version: 2.9.1-2sarge1

We believe that the bug you reported is fixed in the latest version of
unison, which is due to be installed in the Debian FTP archive:

unison-gtk_2.9.1-2sarge1_i386.deb
  to pool/main/u/unison/unison-gtk_2.9.1-2sarge1_i386.deb
unison_2.9.1-2sarge1.diff.gz
  to pool/main/u/unison/unison_2.9.1-2sarge1.diff.gz
unison_2.9.1-2sarge1.dsc
  to pool/main/u/unison/unison_2.9.1-2sarge1.dsc
unison_2.9.1-2sarge1_i386.deb
  to pool/main/u/unison/unison_2.9.1-2sarge1_i386.deb



A summary of the changes between this version and the previous one is
attached.

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

Debian distribution maintenance software
pp.
Sylvain Le Gall <[EMAIL PROTECTED]> (supplier of updated unison package)

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


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

Format: 1.7
Date: Mon,  9 May 2005 00:11:26 +0200
Source: unison
Binary: unison-gtk unison
Architecture: source i386
Version: 2.9.1-2sarge1
Distribution: testing-proposed-updates
Urgency: high
Maintainer: Sylvain Le Gall <[EMAIL PROTECTED]>
Changed-By: Sylvain Le Gall <[EMAIL PROTECTED]>
Description: 
 unison     - A file-synchronization tool for Unix and Windows
 unison-gtk - A file-synchronization tool for Unix and Windows - GTK interface
Closes: 304124
Changes: 
 unison (2.9.1-2sarge1) testing-proposed-updates; urgency=high
 .
   * Release made by sponsor (Robert McQueen) and reviewed by maintainer
     (Sylvain Le Gall)
   * Merge the 2.9.1-2.1 NMU patch and upload to testing-proposed-updates to fix
     the FTBFS in sarge, because the 2.10.2 upload prevented it from reaching
     testing. (Closes: #304124)
   * debian/unison-manual.{html,ps}:
      - remove because they were obtained from the upstream website, and they
         apparently have no license or source
   * debian/unison.doc{s,-base}:
      - remove mention of the HTML and PostScript manuals
   * Use the watch file provided in unison2.9.1
   * Use a substvars to add dependency on ocaml-base when we are compiling for
     non-native arch (since we will need ocamlrun to run the program)
Files: 
 db2f8728f0b5a0f201c19192173c79bb 660 net optional unison_2.9.1-2sarge1.dsc
 4562a3588b3163925f6f6c9c8bf3e006 218475 net optional 
unison_2.9.1-2sarge1.diff.gz
 61d41d3ce0659dd27c0b2e3d5ae7dd3a 426004 net optional 
unison_2.9.1-2sarge1_i386.deb
 c525dd8ac91cf5aac95ed5008f18d0d4 516064 net optional 
unison-gtk_2.9.1-2sarge1_i386.deb

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

iD8DBQFCfpmQXcrf4TUB5sURAjKWAJsFii0D280gxv/wtejfBBIGxrc+2gCfTOX5
vBhFe5lj0WTCvarLAYC+7KU=
=VbNu
-----END PGP SIGNATURE-----


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

Reply via email to