Debian Bug report logs - #520992
ImportError: No module named lsb_release

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Paul Menzel <pm.debian@googlemail.com>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: ImportError: No module named lsb_release

Date: Tue, 24 Mar 2009 09:21:22 +0100

[Message part 1 (text/plain, inline)]

Subject: ImportError: No module named lsb_release
Package: postgresql-common
Version: 97
Severity: important

*** Please type your report below this line ***

Dear Debian folks,


updating postgresql today with

sudo aptitude safe-upgrade

the following was shown.

Richte postgresql-common ein (97) ...
Traceback (most recent call last):
  File "/usr/bin/lsb_release", line 26, in <module>
    import lsb_release
ImportError: No module named lsb_release
Traceback (most recent call last):
  File "/usr/bin/lsb_release", line 26, in <module>
    import lsb_release
ImportError: No module named lsb_release
supported_versions: WARNING! Unknown distribution: 
Please submit this as a bug report to your distribution.

I am tagging it as important, because an ImportError should not be
displayed when updating a package, because it confused or scares the
user. ;-)

Please tell me if I can provide other information.


Thanks,

Paul

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (x86_64)

Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages postgresql-common depends on:
ii  adduser                       3.110      add and remove users and groups
ii  debconf [debconf-2.0]         1.5.26     Debian configuration management sy
ii  lsb-base                      3.2-22     Linux Standard Base 3.2 init scrip
ii  postgresql-client-common      97         manager for multiple PostgreSQL cl
ii  procps                        1:3.2.7-11 /proc file system utilities

Versions of packages postgresql-common recommends:
ii  ssl-cert                      1.0.23     simple debconf wrapper for OpenSSL

postgresql-common suggests no packages.

-- debconf information:
  postgresql-common/obsolete-major:

[signature.asc (application/pgp-signature, inline)]

Message #12 received at 520992@bugs.debian.org (full text, mbox, reply):

From: Chris Lawrence <lawrencc@debian.org>

To: 520992@bugs.debian.org, 520992-submitter@bugs.debian.org, Martin Pitt <mpitt@debian.org>

Subject: order of postinsts?

Date: Tue, 24 Mar 2009 08:57:01 -0500

If lsb-release and postgresql-common were upgraded during the same
dpkg/apt run, it's possible lsb-release hadn't been configured yet
(thus the Python module lsb_release.py wasn't in the search path)
when postgresql-common was configured.  Perhaps changing the
dependency on lsb-release to >= 3.2-22 will fix the problem
(e.g. force lsb-release to be configured before postgresql-common)?

I assume lsb_release 3.2-22 works OK in the general case (in part
because I haven't seen any bug reports to this effect, and in part
because it works on my system).


Chris
-- 
Chris Lawrence <lawrencc@debian.org> - http://blog.lordsutch.com/

Message #20 received at 520992@bugs.debian.org (full text, mbox, reply):

From: Martin Pitt <mpitt@debian.org>

To: Chris Lawrence <lawrencc@debian.org>

Cc: 520992@bugs.debian.org, 520992-submitter@bugs.debian.org

Subject: Re: order of postinsts?

Date: Tue, 24 Mar 2009 17:24:00 +0100

[Message part 1 (text/plain, inline)]

reassign 520992 postgresql-common 96

Chris Lawrence [2009-03-24  8:57 -0500]:
> If lsb-release and postgresql-common were upgraded during the same
> dpkg/apt run, it's possible lsb-release hadn't been configured yet
> (thus the Python module lsb_release.py wasn't in the search path)
> when postgresql-common was configured.  Perhaps changing the
> dependency on lsb-release to >= 3.2-22 will fix the problem
> (e.g. force lsb-release to be configured before postgresql-common)?

Eww, thanks for pointing out. I realize now that the program
lsb_release is now actually shipped in the package lsb-release, and
not in lsb-base as in earlier times. Thus I need to update the
dependency to lsb-release.

Sorry for too quick reaction before,

Martin

-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)

[signature.asc (application/pgp-signature, inline)]

Message #32 received at 520992@bugs.debian.org (full text, mbox, reply):

From: Chris Lawrence <lawrencc@debian.org>

To: Martin Pitt <mpitt@debian.org>, 520992@bugs.debian.org

Cc: 520992-submitter@bugs.debian.org

Subject: Re: Bug#520992: order of postinsts?

Date: Tue, 24 Mar 2009 18:08:18 -0500

On Tue, Mar 24, 2009 at 11:24 AM, Martin Pitt <mpitt@debian.org> wrote:
> reassign 520992 postgresql-common 96
>
> Chris Lawrence [2009-03-24  8:57 -0500]:
>> If lsb-release and postgresql-common were upgraded during the same
>> dpkg/apt run, it's possible lsb-release hadn't been configured yet
>> (thus the Python module lsb_release.py wasn't in the search path)
>> when postgresql-common was configured.  Perhaps changing the
>> dependency on lsb-release to >= 3.2-22 will fix the problem
>> (e.g. force lsb-release to be configured before postgresql-common)?
>
> Eww, thanks for pointing out. I realize now that the program
> lsb_release is now actually shipped in the package lsb-release, and
> not in lsb-base as in earlier times. Thus I need to update the
> dependency to lsb-release.
>
> Sorry for too quick reaction before,

If it's any consolation... I missed it too (when running dpkg --status
I saw lsb-base and just assumed lsb-release was there too).  What I
get for not paying close enough attention!


Chris

Message #40 received at 520992-close@bugs.debian.org (full text, mbox, reply):

From: Martin Pitt <mpitt@debian.org>

To: 520992-close@bugs.debian.org

Subject: Bug#520992: fixed in postgresql-common 98

Date: Fri, 10 Apr 2009 05:17:18 +0000

Source: postgresql-common
Source-Version: 98

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

postgresql-client-common_98_all.deb
  to pool/main/p/postgresql-common/postgresql-client-common_98_all.deb
postgresql-common_98.dsc
  to pool/main/p/postgresql-common/postgresql-common_98.dsc
postgresql-common_98.tar.gz
  to pool/main/p/postgresql-common/postgresql-common_98.tar.gz
postgresql-common_98_all.deb
  to pool/main/p/postgresql-common/postgresql-common_98_all.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 520992@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Martin Pitt <mpitt@debian.org> (supplier of updated postgresql-common 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.8
Date: Thu, 09 Apr 2009 21:58:35 -0700
Source: postgresql-common
Binary: postgresql-common postgresql-client-common
Architecture: source all
Version: 98
Distribution: unstable
Urgency: low
Maintainer: Martin Pitt <mpitt@debian.org>
Changed-By: Martin Pitt <mpitt@debian.org>
Description: 
 postgresql-client-common - manager for multiple PostgreSQL client versions
 postgresql-common - PostgreSQL database-cluster manager
Closes: 520992
Changes: 
 postgresql-common (98) unstable; urgency=low
 .
   * debian/control: Add missing lsb-release dependency (which now ships the
     lsb_release program). (Closes: #520992)
   * Add support for 8.4 (pre-release snapshots for now):
     - debian/supported-versions: Support 8.4 everywhere (for backports).
     - cleanpg: Remove 8.4 clusters.
     - pg_createcluster: Clone configure_8_3() as configure_8_4().
     - t/060_obsolete_confparams.t: Add complete set of 8.3 configuration
       options, to test configuration migration to 8.4.
     - PgCommon.pm, get_cluster_locales(): Bail out if calling on 8.4 or later
       cluster (where locales are not associated to clusters any more).
       PgCommon.pm, get_cluster_databases(): Ignore lines from psql -Atl which
       just describe access permissions.
     - pg_ctlcluster: Only do locales check for <= 8.3 for now.
     - "ident sameuser" does not exist any more in 8.4, just use "ident" from
       8.4 on.
     - pg_createcluster: Do not symlink root.crt if
       /etc/postgresql-common/root.crt does not have actual certificates (just
       the help text), since 8.4 gets royally confused about the dummy one.
     - pg_upgradecluster: Migrate obsolete/changed configuration parameters.
     - t/020_create_sql_remove.t: Fix parsing of psql -Atl output for new 8.4
       format.
     - t/030_errors.t: 8.4 now fails on invalid pg_hba.conf, update
       accordingly.
     - t/050_encodings.t: Stop using pg_controldata for checking cluster
       encoding. Just check psql -Atl.
   * pg_upgradecluster: Don't call createdb/dropdb with -q; it got dropped in
     8.4 and is not necessary any more with 8.3 either.
   * t/010_defaultport_cluster.t: Ensure that we run the test with
     LC_MESSAGES=C, so that it succeeds in non-English locales, too.
   * t/051_inconsistent_encoding_upgrade.t: Disable if the oldest available
     cluster is 8.3 or newer; the test is not relevant there, and will fail.
Checksums-Sha1: 
 d4bca39decad322855f75b8b9d163a418c12d1ff 816 postgresql-common_98.dsc
 ba9d47bc215e5a32999531f311075f469f1b30fa 113570 postgresql-common_98.tar.gz
 faaf866edd485924e9ef1ef40f183faba61c3e68 116458 postgresql-common_98_all.deb
 57e0c1d9d63d344539fec358839462c2c8a232fd 48754 postgresql-client-common_98_all.deb
Checksums-Sha256: 
 578dd2250d6dc4c83a18ecf87c99b375b8805756f9e0c217d46541d7bb448a18 816 postgresql-common_98.dsc
 792a7d5c158e81838f1f36df6b8024023943547810dc6d4b23f196d3341549a4 113570 postgresql-common_98.tar.gz
 81d82bda02784ae688da93c1be977ce794715c351f4129c766aeb23b1b2deb33 116458 postgresql-common_98_all.deb
 15f553c39366a400bf3742472f11f9ada1594ece0bf85b11a0d056436e943768 48754 postgresql-client-common_98_all.deb
Files: 
 110ffd2abd99ac3d36f643124cc2371a 816 database optional postgresql-common_98.dsc
 4fdb3d83ddade2045704f1ca50897758 113570 database optional postgresql-common_98.tar.gz
 1dea5fafc716af1c4e4bbfb86bd96abb 116458 database optional postgresql-common_98_all.deb
 601675915c472e7ac5f70e96c9b56fef 48754 database optional postgresql-client-common_98_all.deb

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

iEYEARECAAYFAkne06oACgkQDecnbV4Fd/JQUQCdHAzuO+cS0QCQAGagiEFupemB
604An1qaxULkjGS+guyOTQJtqOXaxQeK
=kUmx
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.