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

Bug#416972: marked as done (ITA: chmlib -- library for dealing with Microsoft CHM format files)

Your message dated Mon, 09 Apr 2007 09:47:02 +0000
with message-id <E1HaqSk-0001sQ-Gi@ries.debian.org>
and subject line Bug#416954: fixed in chmlib 2:0.39-4
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

The maintainer of chmlib, Julien Lemoine, has orphaned it.

If you want to be the new maintainer, please take it. See
http://www.debian.org/devel/wnpp/index.html#howto-o for detailed
instructions about how to adopt a package properly.

Some information about this package:

Package: chmlib
Binary: libchm1, libchm-bin, libchm-dev
Version: 2:0.39-3
Priority: optional
Section: libs
Maintainer: Debian QA Group <packages@qa.debian.org>
Build-Depends: debhelper (>> 4.0.0), libtool, autotools-dev
Architecture: any
Standards-Version: 3.7.2
Format: 1.0
Directory: pool/main/c/chmlib
Files:
 e796607f1720bb759fb807a3837df82b 612 chmlib_0.39-3.dsc
 895db85bb48bae4c483c3e4675939c80 358247 chmlib_0.39.orig.tar.gz
 c0c90c25388bf2eb70da00d511b7e641 5626 chmlib_0.39-3.diff.gz

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

Format: 1.7
Date: Sat, 31 Mar 2007 19:42:55 +0200
Source: chmlib
Binary: libchm-dev libchm-bin libchm1
Architecture: source i386
Version: 2:0.39-3
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Julien Lemoine <speedblue@debian.org>
Description: 
 libchm-bin - library for dealing with Microsoft CHM format files
 libchm-dev - library for dealing with Microsoft CHM format files
 libchm1    - library for dealing with Microsoft CHM format files
Changes: 
 chmlib (2:0.39-3) unstable; urgency=low
 .
   * Orphan package
Files: 
 e796607f1720bb759fb807a3837df82b 612 libs optional chmlib_0.39-3.dsc
 c0c90c25388bf2eb70da00d511b7e641 5626 libs optional chmlib_0.39-3.diff.gz
 2f593d33d58649cb9fb67703bd03e29e 27738 libs optional libchm1_0.39-3_i386.deb
 aa843fd53ddcd9ae5d06e7558a0eac3a 17316 libdevel optional libchm-bin_0.39-3_i386.deb
 01aa29706034f43b5ae486c93c82baa8 24822 libdevel optional libchm-dev_0.39-3_i386.deb

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

iD8DBQFGDp/ac29c8N2YKnURAu6FAKDBwty0fJFELNozts/pkCNPGL/sKQCfSvp/
Ebn6U2HKNTH46EhFmG7mGW0=
=l6X4
-----END PGP SIGNATURE-----

Aníbal Monsalve Salazar
--
http://v7w.com/anibal

Attachment: signature.asc
Description: Digital signature


--- End Message ---
--- Begin Message --- 
Source: chmlib
Source-Version: 2:0.39-4

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

chmlib_0.39-4.diff.gz
  to pool/main/c/chmlib/chmlib_0.39-4.diff.gz
chmlib_0.39-4.dsc
  to pool/main/c/chmlib/chmlib_0.39-4.dsc
libchm-bin_0.39-4_all.deb
  to pool/main/c/chmlib/libchm-bin_0.39-4_all.deb
libchm-dev_0.39-4_i386.deb
  to pool/main/c/chmlib/libchm-dev_0.39-4_i386.deb
libchm1_0.39-4_i386.deb
  to pool/main/c/chmlib/libchm1_0.39-4_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 416954@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Kartik Mistry <kartik.mistry@gmail.com> (supplier of updated chmlib 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: Sat, 07 Apr 2007 14:15:55 +0530
Source: chmlib
Binary: libchm-dev libchm-bin libchm1
Architecture: source i386 all
Version: 2:0.39-4
Distribution: unstable
Urgency: low
Maintainer: Kartik Mistry <kartik.mistry@gmail.com>
Changed-By: Kartik Mistry <kartik.mistry@gmail.com>
Description: 
 libchm-bin - Transition package for libchm-bin merge with libchm-dev
 libchm-dev - library for dealing with Microsoft CHM files (development)
 libchm1    - library for dealing with Microsoft CHM format files
Closes: 416954 416972
Changes: 
 chmlib (2:0.39-4) unstable; urgency=low
 .
   * New Maintainer (Closes: #416954, #416972)
   * debian/copyright: formatted to standard copyright file
   * debian/control: added ${misc:Depends}, minor cleanups, made description
     meaningful shorter
   * Updated debhelper compability to 5
   * debian/rules: minor cleanups, config.guess/config.sub need to be present
     in .diff.gz
   * Merged libchm-bin into libchm-dev since separate dedicated package only for
     testing is not good idea
   * Added libchm-bin as a transition package
   * All manpages are now standard manpages, removed useless commented parts
   * debian/docs is prefixed now
   * Removed useless *.dirs files
   * Instead of moving files by hand using mv *.install is taking care now
   * Added libchm-dev.manpages to make debian/rules simple
Files: 
 9e932ceef379b53816dc65ff9986f0db 607 libs optional chmlib_0.39-4.dsc
 87408d4020f863ffefc9098184179f81 5919 libs optional chmlib_0.39-4.diff.gz
 6b4d4e5f84cad861c2f6b666e5718237 28140 libs optional libchm1_0.39-4_i386.deb
 0f243b3cc9ba9f3c0717e08542af04af 38144 libdevel optional libchm-dev_0.39-4_i386.deb
 f20ae57cb087ff8555d02bff8a794452 3980 libs optional libchm-bin_0.39-4_all.deb

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

iD8DBQFGGgqZ+C5cwEsrK54RAvCrAJ4gJFV6lTRe7GZ7Uhue06aSy6xKRQCeNkAK
9R1ylzbviAjYL2reNDNxoy8=
=4OUU
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: