[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#264107: marked as done (O: dia2code -- a dia-UML code generator)

Your message dated Wed, 19 Dec 2007 22:32:05 +0000
with message-id <E1J57SP-0006LJ-66@ries.debian.org>
and subject line Bug#264107: fixed in dia2code 0.8.3-3
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)
--- Begin Message --- 
Package: WNPP
Severity: normal

I really don't know what I'm doing with this anymore, and I am unable to 
give it the attention that it needs, so therefore I am orphaning it.

This package really needs someone to take over the upstream, it's pretty 
safe to say that they are dead considering their last release was in 
January of 2002. If nobody comes along to take over in a little while, 
I'm going to go ahead and suggest the removal of this package from Debian.

Morgan

--- End Message ---
--- Begin Message --- 
Source: dia2code
Source-Version: 0.8.3-3

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

dia2code_0.8.3-3.diff.gz
  to pool/main/d/dia2code/dia2code_0.8.3-3.diff.gz
dia2code_0.8.3-3.dsc
  to pool/main/d/dia2code/dia2code_0.8.3-3.dsc
dia2code_0.8.3-3_i386.deb
  to pool/main/d/dia2code/dia2code_0.8.3-3_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 264107@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Francesco Aloe <francescoaloe4gnulinux@gmail.com> (supplier of updated dia2code 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 ftpmaster@debian.org)


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

Format: 1.7
Date: Wed, 19 Dec 2007 18:33:39 +0100
Source: dia2code
Binary: dia2code
Architecture: source i386
Version: 0.8.3-3
Distribution: unstable
Urgency: low
Maintainer: Francesco Aloe <francescoaloe4gnulinux@gmail.com>
Changed-By: Francesco Aloe <francescoaloe4gnulinux@gmail.com>
Description: 
 dia2code   - a dia-UML code generator
Closes: 264107
Changes: 
 dia2code (0.8.3-3) unstable; urgency=low
 .
   * debian/watch: fixed obsolete and not working watch file. Closes #49789.
   * debian/control: removed build-dep on automake1.4 and added automake.
   * debian/dirs: removed this file because it was not needed.
   * Removed some superfluous newlines, trailing whitespaces and fixed typos.
 .
 dia2code (0.8.3-2) unstable; urgency=low
 .
   * New maintainer (Closes: #264107)
   * debian/control: updated standards version to 3.7.3
   * debian/control: removed build-dep on doc-to-man and added cdbs, patchutils
   * debian/rules: switched to cdbs
   * debian/compat: updated to 5
   * debian/patches: managed patches by cdbs simple-patchsys
   * Fixed manpage: added some options missing
   * debian/dia2code.sgml: removed this file because it was used for to generate
     the manpage, is now being used the upstream manpage
Files: 
 8f00d18f4745b446cbacef6fddab02a5 645 devel optional dia2code_0.8.3-3.dsc
 bf7f5d467dda74effc6362bf6a7bb82c 4389 devel optional dia2code_0.8.3-3.diff.gz
 af2419a62d524e143638c1bb03fb4dc8 52628 devel optional dia2code_0.8.3-3_i386.deb

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

iD8DBQFHaZhNHYflSXNkfP8RAqkUAKCDIDeanUVnrPZ0teSRnzdEIrscsACfTIYu
URIrUq0+pgO4nxjOfY/+gYA=
=L4jG
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: