Your message dated Wed, 13 Jul 2005 07:02:55 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#190554: fixed in rubber 1.0-1
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; 24 Apr 2003 12:04:49 +0000
>From [EMAIL PROTECTED] Thu Apr 24 07:04:48 2003
Return-path: <[EMAIL PROTECTED]>
Received: from dhcp11.tat.physik.uni-tuebingen.de (because.homelinux.net) 
[134.2.170.139] 
        by master.debian.org with esmtp (Exim 3.12 1 (Debian))
        id 198fT6-0001BQ-00; Thu, 24 Apr 2003 07:04:48 -0500
Received: from eschnett by because.homelinux.net with local (Exim 3.36 #1 
(Debian))
        id 198fT1-0002TH-00; Thu, 24 Apr 2003 14:04:43 +0200
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Erik Schnetter <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: rubber: Please report undefined references
X-Mailer: reportbug 2.10.1
Date: Thu, 24 Apr 2003 14:04:42 +0200
Message-Id: <[EMAIL PROTECTED]>
Sender: Erik Schnetter <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Status: No, hits=-6.0 required=4.0
        tests=BAYES_01,HAS_PACKAGE
        version=2.53
X-Spam-Level: 
X-Spam-Checker-Version: SpamAssassin 2.53 (1.174.2.15-2003-03-30-exp)

Package: rubber
Version: 0.99.6-1
Severity: wishlist
Tags: upstream

Please report when latex encounters an undefined reference.  Depending
on the verbosity / a command line switch, it might be enough to report
the fact that there were undefined references.  Such undefined
references are usually rather easy to find, because latex emits a
fixed message similar to "there were undefined references" in one of
the last lines of the log file.

Currently, the only way to find undefined references is to look for
"??" markers in the document, or to look at the log file manually.
Both are somewhat contrary to rubber's spirit.

-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux because 2.4.20-1-686 #1 Sat Mar 22 13:16:21 EST 2003 i686
Locale: LANG=C, [EMAIL PROTECTED]

Versions of packages rubber depends on:
ii  python                        2.2.2-6    An interactive object-oriented scr
ii  tetex-bin                     2.0.2-3    teTeX binary files

-- no debconf information


---------------------------------------
Received: (at 190554-close) by bugs.debian.org; 13 Jul 2005 11:08:05 +0000
>From [EMAIL PROTECTED] Wed Jul 13 04:08:05 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 1Dsf5x-00065h-00; Wed, 13 Jul 2005 04:08:05 -0700
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
        id 1Dsf0x-0000fs-00; Wed, 13 Jul 2005 07:02:55 -0400
From: Emmanuel Beffara <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.56 $
Subject: Bug#190554: fixed in rubber 1.0-1
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Wed, 13 Jul 2005 07:02:55 -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: rubber
Source-Version: 1.0-1

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

rubber_1.0-1.diff.gz
  to pool/main/r/rubber/rubber_1.0-1.diff.gz
rubber_1.0-1.dsc
  to pool/main/r/rubber/rubber_1.0-1.dsc
rubber_1.0-1_all.deb
  to pool/main/r/rubber/rubber_1.0-1_all.deb
rubber_1.0.orig.tar.gz
  to pool/main/r/rubber/rubber_1.0.orig.tar.gz



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.
Emmanuel Beffara <[EMAIL PROTECTED]> (supplier of updated rubber 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, 11 Jul 2005 14:52:35 +0200
Source: rubber
Binary: rubber
Architecture: source all
Version: 1.0-1
Distribution: unstable
Urgency: low
Maintainer: Emmanuel Beffara <[EMAIL PROTECTED]>
Changed-By: Emmanuel Beffara <[EMAIL PROTECTED]>
Description: 
 rubber     - an automated system for building LaTeX documents
Closes: 190554 278453 283448 284530 316548 317445
Changes: 
 rubber (1.0-1) unstable; urgency=low
 .
   * New release.
   * Various bugfixes (closes: #278453, #317445).
   * New system for detecting graphics conversion rules (closes: #283448).
   * Fixed the command line for some external tools (closes: #284530, #316548).
   * Some new command-line switches (closes: #190554).
Files: 
 4041e1ec186b95061e86cb1ac6de0ef4 632 tex optional rubber_1.0-1.dsc
 0b28fb8d7125491f41995b225f2f5d33 76218 tex optional rubber_1.0.orig.tar.gz
 8f166c5e492485e51950ced8abd3decc 3459 tex optional rubber_1.0-1.diff.gz
 46431bccb80e48fc8fc6a093a6ab9aaa 75642 tex optional rubber_1.0-1_all.deb

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

iD8DBQFC1O8ZHCar6qtHRZgRAktQAKDGDon8D7TLlCGpwmwEL26xz4CuNgCgyzxK
xFqDuziemllvomuXxmVDlCM=
=3772
-----END PGP SIGNATURE-----


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

Reply via email to