Debian Bug report logs - #446730
bittornado: fails to start: ImportError: No module named BitTornado

Toggle useless messages

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

From: Lionel Elie Mamane <lionel@mamane.lu>

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

Subject: bittornado: fails to start: ImportError: No module named BitTornado

Date: Mon, 15 Oct 2007 09:36:46 +0200

Package: bittornado
Version: 0.3.18-3
Severity: grave
Justification: renders package unusable

Bittornado completely fails to start:

lionelm@harif:~/ST/debian/etch$ btdownloadcurses debian-40r0-amd64-businesscard.iso.torrent
Traceback (most recent call last):
  File "/usr/bin/btdownloadcurses", line 8, in ?
    from BitTornado import PSYCO
ImportError: No module named BitTornado
lionelm@harif:~/ST/debian/etch$ btdownloadgui debian-40r0-amd64-businesscard.iso.torrent
Traceback (most recent call last):
  File "/usr/bin/btdownloadgui", line 7, in ?
    from BitTornado import PSYCO
ImportError: No module named BitTornado
lionelm@harif:~/ST/debian/etch$ btdownloadheadless debian-40r0-amd64-businesscard.iso.torrent
Traceback (most recent call last):
  File "/usr/bin/btdownloadheadless", line 6, in ?
    from BitTornado import PSYCO
ImportError: No module named BitTornado
lionelm@harif:~/ST/debian/etch$ btlaunchmanycurses
Traceback (most recent call last):
  File "/usr/bin/btlaunchmanycurses", line 8, in ?
    from BitTornado import PSYCO
ImportError: No module named BitTornado


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

Kernel: Linux 2.6.22-amd64+deb-3
Locale: LANG=fr_LU.UTF-8, LC_CTYPE=fr_LU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages bittornado depends on:
ii  python                        2.4.4-6    An interactive high-level object-o
ii  python-support                0.7.4      automated rebuilding support for p

Versions of packages bittornado recommends:
ii  mime-support               3.39-1        MIME files 'mime.types' & 'mailcap
ii  python-crypto              2.0.1+dfsg1-2 cryptographic algorithms and proto

-- no debconf information

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

From: "Cameron Dale" <camrdale@gmail.com>

To: "Lionel Elie Mamane" <lionel@mamane.lu>, 446730@bugs.debian.org

Subject: Re: Bug#446730: bittornado: fails to start: ImportError: No module named BitTornado

Date: Mon, 15 Oct 2007 12:39:37 -0700

There were a few reports like this s while back that were
python-support related, so I'm thinking of reassigning this to the
python-support package. Just to be sure, could you let me know the
output of this command:

locate -e BitTornado | sed -e 's#/[^/]*$##' | sort -u

It should show some entries in /usr/share/python-support and
/var/lib/python-support/python2.4. Also, was this a new install of
BitTornado, or an upgrade from a previous version?

You could probably fix this problem by reinstalling BitTornado, but if
you can wait then it would be better NOT to reinstall until we (or the
python-support people) can figure out what's causing these problems.

Thanks,
Cameron

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

From: Lionel Elie Mamane <lionel@mamane.lu>

To: Cameron Dale <camrdale@gmail.com>

Cc: 446730@bugs.debian.org

Subject: Re: Bug#446730: bittornado: fails to start: ImportError: No module named BitTornado

Date: Mon, 15 Oct 2007 21:56:27 +0200

On Mon, Oct 15, 2007 at 12:39:37PM -0700, Cameron Dale wrote:

> could you let me know the output of this command:

> locate -e BitTornado | sed -e 's#/[^/]*$##' | sort -u

lionelm@harif:~$ locate -e /BitTornado  | sed -e 's#/[^/]*$##' | sort -u
/usr/share/python-support/bittornado
/usr/share/python-support/bittornado/BitTornado
/usr/share/python-support/bittornado/BitTornado/BT1

> It should show some entries in /usr/share/python-support and
> /var/lib/python-support/python2.4. Also, was this a new install of
> BitTornado, or an upgrade from a previous version?

/var/log/aptitude.1.gz:[UPGRADE] bittornado 0.3.18-3 -> 0.3.18-4

> You could probably fix this problem by reinstalling BitTornado, but if
> you can wait then it would be better NOT to reinstall until we (or the
> python-support people) can figure out what's causing these problems.

I can wait.

-- 
Lionel

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

From: "Cameron Dale" <camrdale@gmail.com>

To: "Lionel Elie Mamane" <lionel@mamane.lu>

Cc: 446730@bugs.debian.org, control@bugs.debian.org

Subject: Re: Bug#446730: bittornado: fails to start: ImportError: No module named BitTornado

Date: Mon, 15 Oct 2007 13:23:20 -0700

reassign 446730 python-support
thanks

On 10/15/07, Lionel Elie Mamane <lionel@mamane.lu> wrote:
> On Mon, Oct 15, 2007 at 12:39:37PM -0700, Cameron Dale wrote:
>
> > could you let me know the output of this command:
>
> > locate -e BitTornado | sed -e 's#/[^/]*$##' | sort -u
>
> lionelm@harif:~$ locate -e /BitTornado  | sed -e 's#/[^/]*$##' | sort -u
> /usr/share/python-support/bittornado
> /usr/share/python-support/bittornado/BitTornado
> /usr/share/python-support/bittornado/BitTornado/BT1

This seems to confirm that it is a python-support bug, therefore I am
reassigning it there. There were 2 previous instances of an error
similar to this one in BitTornado: 383799 and 386272. I can't find any
other packages that report errors similar to this related to
python-support, but I can't see any errors in the BitTornado packaging
that would cause this, and also the error is intermittent (a reinstall
will fix it). These all lead me to believe it is python-support
related and so I have assigned it there.

> > It should show some entries in /usr/share/python-support and
> > /var/lib/python-support/python2.4. Also, was this a new install of
> > BitTornado, or an upgrade from a previous version?
>
> /var/log/aptitude.1.gz:[UPGRADE] bittornado 0.3.18-3 -> 0.3.18-4
>
> > You could probably fix this problem by reinstalling BitTornado, but if
> > you can wait then it would be better NOT to reinstall until we (or the
> > python-support people) can figure out what's causing these problems.
>
> I can wait.

That's great, hopefully the python-support maintainer will be able to
help you with this.

Thanks,
Cameron

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

From: Josselin Mouette <joss@debian.org>

To: Cameron Dale <camrdale@gmail.com>

Cc: Lionel Elie Mamane <lionel@mamane.lu>, 446730@bugs.debian.org

Subject: Re: Bug#446730: bittornado: fails to start: ImportError: No module named BitTornado

Date: Mon, 15 Oct 2007 23:10:30 +0200

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

Hi,

Le lundi 15 octobre 2007 à 13:23 -0700, Cameron Dale a écrit :
> 
> On 10/15/07, Lionel Elie Mamane <lionel@mamane.lu> wrote:
> > On Mon, Oct 15, 2007 at 12:39:37PM -0700, Cameron Dale wrote:
> >
> > > could you let me know the output of this command:
> >
> > > locate -e BitTornado | sed -e 's#/[^/]*$##' | sort -u
> >
> > lionelm@harif:~$ locate -e /BitTornado  | sed -e 's#/[^/]*$##' | sort -u
> > /usr/share/python-support/bittornado
> > /usr/share/python-support/bittornado/BitTornado
> > /usr/share/python-support/bittornado/BitTornado/BT1
> 
> This seems to confirm that it is a python-support bug, therefore I am
> reassigning it there. There were 2 previous instances of an error
> similar to this one in BitTornado: 383799 and 386272. I can't find any
> other packages that report errors similar to this related to
> python-support, but I can't see any errors in the BitTornado packaging
> that would cause this, and also the error is intermittent (a reinstall
> will fix it). These all lead me to believe it is python-support
> related and so I have assigned it there.

Well, I still don't understand, especially why this bug only happens
with bittornado while this package has nothing special. All upgrade
issues I can think of should either be without effect or trigger an
error, but not fail silently.

> > > It should show some entries in /usr/share/python-support and
> > > /var/lib/python-support/python2.4. Also, was this a new install of
> > > BitTornado, or an upgrade from a previous version?
> >
> > /var/log/aptitude.1.gz:[UPGRADE] bittornado 0.3.18-3 -> 0.3.18-4

I take it that bittornado worked before this upgrade.

Could you send the corresponding /var/log/dpkg.log? I'm interested to
know whether other things were updated in the same run, and in which
order.

> > > You could probably fix this problem by reinstalling BitTornado, but if
> > > you can wait then it would be better NOT to reinstall until we (or the
> > > python-support people) can figure out what's causing these problems.

Just to be sure, please check if there are
any /var/lib/python-support/*/BitTornado* directories and check the
contents of the /var/lib/python-support/python2.4/.path file.

Thanks,
-- 
 .''`.
: :' :      We are debian.org. Lower your prices, surrender your code.
`. `'       We will add your hardware and software distinctiveness to
  `-        our own. Resistance is futile.

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

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

From: Lionel Elie Mamane <lionel@mamane.lu>

To: Josselin Mouette <joss@debian.org>

Cc: Cameron Dale <camrdale@gmail.com>, 446730@bugs.debian.org

Subject: Re: Bug#446730: bittornado: fails to start: ImportError: No module named BitTornado

Date: Tue, 16 Oct 2007 08:08:49 +0200

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

On Mon, Oct 15, 2007 at 11:10:30PM +0200, Josselin Mouette wrote:
> Le lundi 15 octobre 2007 ? 13:23 -0700, Cameron Dale a ?crit :
>> On 10/15/07, Lionel Elie Mamane <lionel@mamane.lu> wrote:
>>> On Mon, Oct 15, 2007 at 12:39:37PM -0700, Cameron Dale wrote:

>>>> It should show some entries in /usr/share/python-support and
>>>> /var/lib/python-support/python2.4. Also, was this a new install of
>>>> BitTornado, or an upgrade from a previous version?

>>> /var/log/aptitude.1.gz:[UPGRADE] bittornado 0.3.18-3 -> 0.3.18-4

> I take it that bittornado worked before this upgrade.

Yes. The previous bittornado upgrade was in May and I'm sure I used it
since then :) It is possible, though, that a previous upgrade of
python-support or python2.x broke it; I don't use bittornado often.

> Could you send the corresponding /var/log/dpkg.log? I'm interested
> to know whether other things were updated in the same run, and in
> which order.

Among others, python-support.

> Just to be sure, please check if there are
> any /var/lib/python-support/*/BitTornado* directories and check the
> contents of the /var/lib/python-support/python2.4/.path file.

lionelm@harif:~$ ls /var/lib/python-support/*/BitTornado*
ls: /var/lib/python-support/*/BitTornado*: No such file or directory
lionelm@harif:~$ cat /var/lib/python-support/python2.4/.path
/var/lib/python-support/python2.4
gtk-2.0
/var/lib/python-support/python2.4/gtk-2.0

-- 
Lionel

[dpkg.log.1.bz2 (application/octet-stream, attachment)]

[aptitude.1.gz (application/octet-stream, attachment)]

[dpkg.log.2.gz (application/octet-stream, attachment)]

[aptitude.2.gz (application/octet-stream, attachment)]

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

From: Josselin Mouette <joss@debian.org>

To: Lionel Elie Mamane <lionel@mamane.lu>, 446730@bugs.debian.org

Cc: Cameron Dale <camrdale@gmail.com>

Subject: Re: Bug#446730: bittornado: fails to start: ImportError: No module named BitTornado

Date: Tue, 16 Oct 2007 09:20:02 +0200

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

Hi,

Le mardi 16 octobre 2007 à 08:08 +0200, Lionel Elie Mamane a écrit :
> On Mon, Oct 15, 2007 at 11:10:30PM +0200, Josselin Mouette wrote:
> > Le lundi 15 octobre 2007 ? 13:23 -0700, Cameron Dale a ?crit :
> >> On 10/15/07, Lionel Elie Mamane <lionel@mamane.lu> wrote:
> 
> >>> /var/log/aptitude.1.gz:[UPGRADE] bittornado 0.3.18-3 -> 0.3.18-4
> 
> > I take it that bittornado worked before this upgrade.
> 
> Yes. The previous bittornado upgrade was in May and I'm sure I used it
> since then :) It is possible, though, that a previous upgrade of
> python-support or python2.x broke it; I don't use bittornado often.
> 
> > Could you send the corresponding /var/log/dpkg.log? I'm interested
> > to know whether other things were updated in the same run, and in
> > which order.
> 
> Among others, python-support.

Wow, from your dpkg.log I can gather at least 3 issues.

2007-10-09 10:38:41 upgrade python-support 0.6.4 0.7.4
2007-10-09 10:38:41 status half-configured python-support 0.6.4
2007-10-09 10:38:41 status unpacked python-support 0.6.4
2007-10-09 10:38:41 status half-installed python-support 0.6.4
2007-10-09 10:38:42 status half-installed python-support 0.6.4
2007-10-09 10:38:42 status unpacked python-support 0.7.4
2007-10-09 10:38:42 status unpacked python-support 0.7.4
2007-10-09 10:45:25 upgrade bittornado-gui 0.3.18-3 0.3.18-4
2007-10-09 10:45:25 status half-configured bittornado-gui 0.3.18-3
2007-10-09 10:45:26 status unpacked bittornado-gui 0.3.18-3
2007-10-09 10:45:26 status half-installed bittornado-gui 0.3.18-3
2007-10-09 10:45:26 status half-installed bittornado-gui 0.3.18-3
2007-10-09 10:45:26 status unpacked bittornado-gui 0.3.18-4
2007-10-09 10:45:26 status unpacked bittornado-gui 0.3.18-4
2007-10-09 10:45:26 upgrade bittornado 0.3.18-3 0.3.18-4
2007-10-09 10:45:26 status half-configured bittornado 0.3.18-3
2007-10-09 10:45:28 status installed bittornado 0.3.18-3
2007-10-09 10:54:58 status unpacked python-support 0.7.4
2007-10-09 10:54:58 status half-configured python-support 0.7.4
2007-10-09 10:54:58 status installed python-support 0.7.4

First of all, bittornado failed to upgrade. I think this was either
caused by a prerm failure or an unpack failure, leading in the end to
have only bittornado 0.3.18-3 installed. So there's probably a bug in
bittornado. It would be nice if you could tell us how 

Secondly, when an upgrade fails, the old postinst is executed with the
"abort-upgrade" option. In this case, it seems a convention in debhelper
snippets not to do anything. *This is definitely a bug* for several of
them, including dh_pysupport. I will fix python-support for that issue
and report another bug against debhelper.

Thirdly, I notice that the postinst was executed before python-support
was considered installed. This is harmless as it should work when only
unpacked, but as bittornado has a Depends: on python-support, this looks
like a bug in dpkg.

Cheer up, four bugs in one :)
-- 
 .''`.
: :' :      We are debian.org. Lower your prices, surrender your code.
`. `'       We will add your hardware and software distinctiveness to
  `-        our own. Resistance is futile.

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

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

From: "Cameron Dale" <camrdale@gmail.com>

To: "Josselin Mouette" <joss@debian.org>

Cc: "Lionel Elie Mamane" <lionel@mamane.lu>, 446730@bugs.debian.org

Subject: Re: Bug#446730: bittornado: fails to start: ImportError: No module named BitTornado

Date: Tue, 16 Oct 2007 23:22:56 -0700

On 10/16/07, Josselin Mouette <joss@debian.org> wrote:
> First of all, bittornado failed to upgrade. I think this was either
> caused by a prerm failure or an unpack failure, leading in the end to
> have only bittornado 0.3.18-3 installed. So there's probably a bug in
> bittornado. It would be nice if you could tell us how

I'm not sure what the bug could be in bittornado, as I have done the
same upgrade on 2 machines and the other maintainer has as well, all
without problems. One difference I noted is that Lionel also upgraded
python-support at the same time, so I downgraded bittornado to do the
same upgrade. Here are the results, which generated no errors at all:

2007-10-16 23:11:17 upgrade python-support 0.6.4 0.7.4
2007-10-16 23:11:17 status half-configured python-support 0.6.4
2007-10-16 23:11:17 status unpacked python-support 0.6.4
2007-10-16 23:11:17 status half-installed python-support 0.6.4
2007-10-16 23:11:18 status half-installed python-support 0.6.4
2007-10-16 23:11:18 status unpacked python-support 0.7.4
2007-10-16 23:11:18 status unpacked python-support 0.7.4
2007-10-16 23:11:18 upgrade bittornado-gui 0.3.18-3 0.3.18-4
2007-10-16 23:11:18 status half-configured bittornado-gui 0.3.18-3
2007-10-16 23:11:18 status unpacked bittornado-gui 0.3.18-3
2007-10-16 23:11:18 status half-installed bittornado-gui 0.3.18-3
2007-10-16 23:11:18 status half-installed bittornado-gui 0.3.18-3
2007-10-16 23:11:18 status unpacked bittornado-gui 0.3.18-4
2007-10-16 23:11:18 status unpacked bittornado-gui 0.3.18-4
2007-10-16 23:11:18 upgrade bittornado 0.3.18-3 0.3.18-4
2007-10-16 23:11:18 status half-configured bittornado 0.3.18-3
2007-10-16 23:11:19 status unpacked bittornado 0.3.18-3
2007-10-16 23:11:19 status half-installed bittornado 0.3.18-3
2007-10-16 23:11:19 status half-installed bittornado 0.3.18-3
2007-10-16 23:11:19 status unpacked bittornado 0.3.18-4
2007-10-16 23:11:19 status unpacked bittornado 0.3.18-4
2007-10-16 23:11:20 status unpacked python-support 0.7.4
2007-10-16 23:11:20 status half-configured python-support 0.7.4
2007-10-16 23:11:20 status installed python-support 0.7.4
2007-10-16 23:11:20 status unpacked bittornado 0.3.18-4
2007-10-16 23:11:20 status half-configured bittornado 0.3.18-4
2007-10-16 23:11:22 status installed bittornado 0.3.18-4
2007-10-16 23:11:22 status unpacked bittornado-gui 0.3.18-4
2007-10-16 23:11:22 status half-configured bittornado-gui 0.3.18-4
2007-10-16 23:11:22 status installed bittornado-gui 0.3.18-4

One interesting thing I noticed was that the bittornado 0.3.18-4 in
the archive depends on python-support >= 0.7.1, whereas the one I
built locally only depends on python-support >= 0.2. I assume that
means it was built (by my sponsor) with a newer version of
python-support than mine was, which I'm not sure how it would cause
this problem, but I thought I'd mention it anyway.

Thanks,
Cameron

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

From: Josselin Mouette <joss@debian.org>

To: 446730-close@bugs.debian.org

Subject: Bug#446730: fixed in python-support 0.7.5

Date: Wed, 31 Oct 2007 18:17:14 +0000

Source: python-support
Source-Version: 0.7.5

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

python-support_0.7.5.dsc
  to pool/main/p/python-support/python-support_0.7.5.dsc
python-support_0.7.5.tar.gz
  to pool/main/p/python-support/python-support_0.7.5.tar.gz
python-support_0.7.5_all.deb
  to pool/main/p/python-support/python-support_0.7.5_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 446730@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Josselin Mouette <joss@debian.org> (supplier of updated python-support 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, 31 Oct 2007 18:51:10 +0100
Source: python-support
Binary: python-support
Architecture: source all
Version: 0.7.5
Distribution: unstable
Urgency: low
Maintainer: Josselin Mouette <joss@debian.org>
Changed-By: Josselin Mouette <joss@debian.org>
Description: 
 python-support - automated rebuilding support for python modules
Closes: 446730
Changes: 
 python-support (0.7.5) unstable; urgency=low
 .
   * dh_pysupport:
     + Cut out some unused code.
     + Unify script generation, cutting obsolete -i and -b options.
   * {postinst,prerm}-python-support:
     + Update snippets accordingly.
     + Launch the postinst in all cases, not only in the configure case.
       Closes: #446730.
Files: 
 563ca7a334779a7ee3d144507da601ad 553 python standard python-support_0.7.5.dsc
 5e83909c4725f334904d3eea2db6bd19 29272 python standard python-support_0.7.5.tar.gz
 13da6efc866ab71727e31241b81726ae 26458 python standard python-support_0.7.5_all.deb

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

iD8DBQFHKMP6rSla4ddfhTMRAl88AKCDblYRg2L+Aa97O1DeHTqdbYf5dQCfW3lP
wiT+gOB5yTeUoYWxUx0BYIE=
=t6fg
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.