Your message dated Tue, 21 Apr 2009 12:02:04 +0000
with message-id <e1lwefs-00073h...@ries.debian.org>
and subject line Bug#524854: fixed in liblunar 2.0.1-2
has caused the Debian Bug report #524854,
regarding python-lunar fails to install in squeeze; update-python-modules fails
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 ow...@bugs.debian.org
immediately.)


-- 
524854: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=524854
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-lunar
Version: 2.0.1-1
Severity: grave
Justification: renders package unusable


When aptitude tried to install python-lunar, it said: <quote>

Errors were encountered while processing:
 python-lunar
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install.  Trying to recover:
Setting up python-lunar (2.0.1-1) ...
Usage: update-python-modules [-v] [-c] package_directory [...]
       update-python-modules [-v] [-c] package.dirs [...]
       update-python-modules [-v] [-al-fl-p]

update-python-modules: error: /usr/share/python-support/python-lunar.public is 
not a directory
dpkg: error processing python-lunar (--configure):
 subprocess post-installation script returned error exit status 2
Errors were encountered while processing:
 python-lunar
Press return to continue.

</quote> (give or take any typos when I transcribed it from the
console).  A freshly-started python session is subsequently unable to
import lunar, so the package is unusable.

The update-python-modules script is provided by:
ii  python-support         0.8.7             automated rebuilding support for 
Python modules

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores)
Locale: LANG=en_GB.ISO-8859-15, LC_CTYPE=en_GB.ISO-8859-15 (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash

Versions of packages python-lunar depends on:
ii  libatk1.0-0            1.24.0-2          The ATK accessibility toolkit
ii  libc6                  2.9-4             GNU C Library: Shared libraries
ii  libcairo2              1.8.6-2+b1        The Cairo 2D vector graphics libra
ii  libfontconfig1         2.6.0-3           generic font configuration library
ii  libfreetype6           2.3.9-4           FreeType 2 font engine, shared lib
ii  libglib2.0-0           2.20.0-2          The GLib library of C routines
ii  libgtk2.0-0            2.14.7-5          The GTK+ graphical user interface 
ii  libgtksourceview2.0-0  2.4.2-1           shared libraries for the GTK+ synt
ii  liblunar-1-0           2.0.1-1           Chinese Lunar library
ii  libpango1.0-0          1.24.0-3+b1       Layout and rendering of internatio
ii  python2.5              2.5.4-1           An interactive high-level object-o
ii  zlib1g                 1:1.2.3.3.dfsg-13 compression library - runtime

python-lunar recommends no packages.

python-lunar suggests no packages.

-- no debconf information



--- End Message ---
--- Begin Message ---
Source: liblunar
Source-Version: 2.0.1-2

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

liblunar-1-0-dbg_2.0.1-2_amd64.deb
  to pool/main/libl/liblunar/liblunar-1-0-dbg_2.0.1-2_amd64.deb
liblunar-1-0_2.0.1-2_amd64.deb
  to pool/main/libl/liblunar/liblunar-1-0_2.0.1-2_amd64.deb
liblunar-1-dev_2.0.1-2_amd64.deb
  to pool/main/libl/liblunar/liblunar-1-dev_2.0.1-2_amd64.deb
liblunar-1-doc_2.0.1-2_all.deb
  to pool/main/libl/liblunar/liblunar-1-doc_2.0.1-2_all.deb
liblunar_2.0.1-2.diff.gz
  to pool/main/libl/liblunar/liblunar_2.0.1-2.diff.gz
liblunar_2.0.1-2.dsc
  to pool/main/libl/liblunar/liblunar_2.0.1-2.dsc
python-lunar_2.0.1-2_amd64.deb
  to pool/main/libl/liblunar/python-lunar_2.0.1-2_amd64.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 524...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
LI Daobing <lidaob...@debian.org> (supplier of updated liblunar 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 ftpmas...@debian.org)


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

Format: 1.8
Date: Tue, 21 Apr 2009 19:23:11 +0800
Source: liblunar
Binary: liblunar-1-dev liblunar-1-0 liblunar-1-0-dbg liblunar-1-doc python-lunar
Architecture: source amd64 all
Version: 2.0.1-2
Distribution: unstable
Urgency: low
Maintainer: LI Daobing <lidaob...@debian.org>
Changed-By: LI Daobing <lidaob...@debian.org>
Description: 
 liblunar-1-0 - Chinese Lunar library
 liblunar-1-0-dbg - Chinese Lunar library
 liblunar-1-dev - Development files for the Chinese Lunar library
 liblunar-1-doc - Documentation for the Chinese Lunar library
 python-lunar - Python bindings for the Chinese Lunar library
Closes: 524854
Changes: 
 liblunar (2.0.1-2) unstable; urgency=low
 .
   * debian/control:
     - change maintainer's email.
     - bump standards version to 3.8.1
     - change section of liblunar-1-0-dbg to debug
     - add python-support (>= 1.0) to build depends and depends of python-lunar
       (Closes: #524854)
Checksums-Sha1: 
 9b07f9f6e63b7356238e752d7db61aa43610b402 1348 liblunar_2.0.1-2.dsc
 6fbc77e757d64f39be832907e80dbe886d451876 3820 liblunar_2.0.1-2.diff.gz
 5e6198cfa41d9f1d25fe8206d22d3a66e8bf72f4 10400 liblunar-1-dev_2.0.1-2_amd64.deb
 2c44fa06df0b057dbd0782be240d392a219fc750 43072 liblunar-1-0_2.0.1-2_amd64.deb
 c97da08f76f732918479402a3f9d2393c9170592 6100 
liblunar-1-0-dbg_2.0.1-2_amd64.deb
 ca31c1b2f1327fd4b2d319c263c1f2d48795b9c4 11682 python-lunar_2.0.1-2_amd64.deb
 cdc257019cb826f26dada81a0f63a26c32b87963 16576 liblunar-1-doc_2.0.1-2_all.deb
Checksums-Sha256: 
 ec8ac851500e9a053b3e801456ed150f4fb1bae380254b13b35448a5c3498a11 1348 
liblunar_2.0.1-2.dsc
 3cf26eb5eca58d19106f1edc29ac5316c5d35033fbf1c45735260cf6e6ae18fd 3820 
liblunar_2.0.1-2.diff.gz
 c723c5b00dbb9edf12cfe7c5e44da297893eec6b57d9eccf7f574ba222ff5f08 10400 
liblunar-1-dev_2.0.1-2_amd64.deb
 0e974fc71d3da9b47523e0b795948cfa629c3da63010b7004cced7824bdfd7f3 43072 
liblunar-1-0_2.0.1-2_amd64.deb
 e4e4d8da0c428ee98990151279dcc343d5be28a64e2fcdccd4cfd44a4d514b99 6100 
liblunar-1-0-dbg_2.0.1-2_amd64.deb
 273be1b7eebb97f8c277f275582581c4dd4d41e31a747c24a6c6466383879069 11682 
python-lunar_2.0.1-2_amd64.deb
 65a1a0d7394cd28c64e233089a90d8dbb6f9d59d074e64517acebef9a5f6bd04 16576 
liblunar-1-doc_2.0.1-2_all.deb
Files: 
 8b5cb6837441d42a012b9bb5db6480c9 1348 libs optional liblunar_2.0.1-2.dsc
 1685f3aa8f9dbfeb04dad4635e349618 3820 libs optional liblunar_2.0.1-2.diff.gz
 70f266daff4c89f7b2542326c121b833 10400 libdevel optional 
liblunar-1-dev_2.0.1-2_amd64.deb
 2b3e1a49c6e4c7074115973af99161ab 43072 libs optional 
liblunar-1-0_2.0.1-2_amd64.deb
 4bf1b55d90759c0b2ba9637d7a5bacb9 6100 debug extra 
liblunar-1-0-dbg_2.0.1-2_amd64.deb
 78aac0a36a845d079dee45ca2e003fa8 11682 python optional 
python-lunar_2.0.1-2_amd64.deb
 c3aa085f331ae7f351e4cfe812727896 16576 doc optional 
liblunar-1-doc_2.0.1-2_all.deb

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

iD8DBQFJ7bKO5TUK4GCH0vgRAnV5AKCUZKytj2qAgDsXs94fnDhbPOOMXwCfX6xz
qe0hmu1I6JzB2BmgVX3Rv9c=
=Cpqe
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to