Your message dated Mon, 17 Mar 2008 04:32:02 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#466637: fixed in bisonc++ 2.4.2-1
has caused the Debian Bug report #466637,
regarding bisonc++: package description seems made wrong references 
(debian/control)
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
466637: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=466637
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Package: bisonc++
Version: 2.4.1-1
Severity: wishlist
Tags: patch


Hi,

        While translating the bisonc++ package description in
DDTP, I had the impression that some wrong references are made
about bison++ and bisonc++. Below is a proposed patch, but I'm
a little bit unsure if that is the intended idea. I hope this
helps.

- ---------->8---------->8---------->8---------->8---------->8----------
- --- control.orig        2008-02-20 01:00:32.417542772 -0300
+++ control     2008-02-20 01:01:56.422329932 -0300
@@ -23,13 +23,13 @@
  function. The class can easily be provided with additional members without
  needing polymorphic functions. Consequently, classes generated by bisonc++
  have no virtual members and actually have but one public member: parse(),
- - replacing the old-style bison and bisonc++ yyparse() function.
+ replacing the old-style bison and bison++ yyparse() function.
  .
  Bisonc++ offers many options, among which an option to define classes
  generated by bisonc++ in a separate namespace. This allows developers to
  define additional symbols, even outside of the class generated by bisonc++,
  without encountering name-collision problems. With bisonc++, artificial means
- - to prevent name-collisions, like bison and bisonc++'s yy-convention are not
+ to prevent name-collisions, like bison and bison++'s yy-convention are not
  required anymore when using bisonc++.  Bisonc++ merely generates C++ code. If
  C code is required, bison should be used. Bisonc++'s grammar requirements are
  highly compatible with bison's requirements, so converting a bison grammar
- ----------8<----------8<----------8<----------8<----------8<----------

        Thanks in advance.


- --- System information. ---
Architecture: i386
Kernel: Linux 2.6.22-3-686

Debian Release: lenny/sid
500 testing www.debian-multimedia.org
500 testing security.debian.org
500 testing ftp.br.debian.org

- --
Felipe Augusto van de Wiel (faw)
"Debian. Freedom to code. Code to freedom!"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHu6aECjAO0JDlykYRAnwsAJ9i+Ggo+kx4p/fL2xds4o945f6jMwCgoE4S
+RruXKKOrmTHUNNj1PAJqz4=
=K7x5
-----END PGP SIGNATURE-----



--- End Message ---
--- Begin Message ---
Source: bisonc++
Source-Version: 2.4.2-1

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

bisonc++_2.4.2-1.diff.gz
  to pool/main/b/bisonc++/bisonc++_2.4.2-1.diff.gz
bisonc++_2.4.2-1.dsc
  to pool/main/b/bisonc++/bisonc++_2.4.2-1.dsc
bisonc++_2.4.2-1_i386.deb
  to pool/main/b/bisonc++/bisonc++_2.4.2-1_i386.deb
bisonc++_2.4.2.orig.tar.gz
  to pool/main/b/bisonc++/bisonc++_2.4.2.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.
Frank B. Brokken <[EMAIL PROTECTED]> (supplier of updated bisonc++ 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: Sun, 16 Mar 2008 14:21:37 +0100
Source: bisonc++
Binary: bisonc++
Architecture: source i386
Version: 2.4.2-1
Distribution: unstable
Urgency: low
Maintainer: Frank B. Brokken <[EMAIL PROTECTED]>
Changed-By: Frank B. Brokken <[EMAIL PROTECTED]>
Description: 
 bisonc++   - Bison-style parser generator for C++
Closes: 465575 466637
Changes: 
 bisonc++ (2.4.2-1) unstable; urgency=low
 .
   * New upstream release. (Closes: #465575)
   * Modified package description. (Closes: #466637)
Files: 
 4ba93d458af6fb17c6a9abd2701f53cb 855 devel optional bisonc++_2.4.2-1.dsc
 25bdd10c02067bcfdaaddfe748055765 592677 devel optional 
bisonc++_2.4.2.orig.tar.gz
 e4c8d0bb434b39bc6b0f95a86a3560ec 9851 devel optional bisonc++_2.4.2-1.diff.gz
 023e236465f88d424f18e97fa92fa14a 330474 devel optional 
bisonc++_2.4.2-1_i386.deb

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

iD8DBQFH3fLWpdwBkPlyvgMRAnsoAJ4kVov5GUS7f9lIgWg2NMvSI9KC2QCcDsOi
DDOGgUTFUtUD9QxGCj3ylnU=
=szKC
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to