Your message dated Tue, 10 May 2005 15:26:43 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#308225: python-id3lib: It seems this still exists
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)
--------------------------------------
Received: (at submit) by bugs.debian.org; 8 May 2005 21:09:35 +0000
>From [EMAIL PROTECTED] Sun May 08 14:09:35 2005
Return-path: <[EMAIL PROTECTED]>
Received: from dkv254.neoplus.adsl.tpnet.pl (mp.pl.eu.org) [83.24.25.254]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DUt1q-0007cI-00; Sun, 08 May 2005 14:09:35 -0700
Received: from mike by mp.pl.eu.org with local (Exim 3.36 #1 (Debian))
id 1DUt1L-0003YS-00
for <[EMAIL PROTECTED]>; Sun, 08 May 2005 23:09:03 +0200
Date: Sun, 8 May 2005 23:09:03 +0200
From: Michal Politowski <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: python-id3lib: uninstallable
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="BOKacYhQ+x31HxR3"
Content-Disposition: inline
X-Reportbug-Version: 3.11
X-PGP: 1024D/6B757C5B; 1C98 622F 6A6D 822D 3E95 2626 14EB 98C1 6B75 7C5B;
2004-02-29 -- 2006-02-28
User-Agent: Mutt/1.5.9i
Sender: Michal Politowski <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
--BOKacYhQ+x31HxR3
Content-Type: text/plain; charset=iso-8859-2
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Package: python-id3lib
Version: 0.5.1-4
Severity: grave
Justification: renders package unusable
/usr/lib/python2.3/site-packages/pyid3lib.so
is in this dummy package, probably accidentally,
and causes a conflict with python2.3-id3lib.
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.10
Locale: LANG=3Dpl_PL, LC_CTYPE=3Dpl_PL (charmap=3DISO-8859-2)
Versions of packages python-id3lib depends on:
ii python 2.3.5-2 An interactive high-level obje=
ct-o
ii python2.3-id3lib 0.5.1-4 id3lib wrapper for Python - li=
brar
--=20
Micha=B3 Politowski
Talking has been known to lead to communication if practised carelessly.
--BOKacYhQ+x31HxR3
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
iD8DBQFCfn/vFOuYwWt1fFsRAvQcAKCPAW1rnwRzwUugSAb06xW/xwO4LACeOoT4
jXuANuCxedNs904kMEUI3oY=
=LA/y
-----END PGP SIGNATURE-----
--BOKacYhQ+x31HxR3--
---------------------------------------
Received: (at 308225-done) by bugs.debian.org; 10 May 2005 20:26:40 +0000
>From [EMAIL PROTECTED] Tue May 10 13:26:40 2005
Return-path: <[EMAIL PROTECTED]>
Received: from buffy.riseup.net (mail.riseup.net) [69.90.134.155]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DVbJQ-0000Yp-00; Tue, 10 May 2005 13:26:40 -0700
Received: from localhost (localhost [127.0.0.1])
by mail.riseup.net (Postfix) with ESMTP id 28BE7A2FC7;
Tue, 10 May 2005 13:26:06 -0700 (PDT)
Received: from mail.riseup.net ([127.0.0.1])
by localhost (buffy [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
id 25090-25; Tue, 10 May 2005 13:26:06 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(No client certificate requested)
by mail.riseup.net (Postfix) with ESMTP id E68FEA2FC5;
Tue, 10 May 2005 13:26:05 -0700 (PDT)
Received: by pond (Postfix, from userid 1000)
id AF4C33A80E; Tue, 10 May 2005 15:26:43 -0500 (CDT)
Date: Tue, 10 May 2005 15:26:43 -0500
From: Micah Anderson <[EMAIL PROTECTED]>
To: Jonas Smedegaard <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]
Subject: Re: Bug#308225: python-id3lib: It seems this still exists
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[EMAIL PROTECTED]>
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at riseup.net
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Jonas Smedegaard schrieb am Tuesday, den 10. May 2005:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 09-05-2005 21:00, Micah Anderson wrote:
> > Package: python-id3lib
> > Version: 0.5.1-3
> > Followup-For: Bug #308225
> >
> > My installation gives this error:
> >
> > Unpacking replacement python-id3lib ...
> > dpkg: error processing
> > /var/cache/apt/archives/python-id3lib_0.5.1-4_all.deb (--unpack):
> > trying to overwrite /usr/lib/python2.3/site-packages/pyid3lib.so',
> > which is also in package python2.3-id3lib
> > dpkg-deb: subprocess paste killed by signal (Broken pipe)
>
> Hi Micah,
>
> You (or your "reportbug" script?) says this bugreport is about 0.5.1-3
> but in fact it appeared in -4 and (I believe) was fixed in -5.
Hey Jonas,
reportbug seems to give the version information for the package that
is currently installed, and is not smart enough to change that version
if a newer version of the package fails to install properly. So, yes,
reportbug showed 0.5.1-3, which was installed at the time of me trying
to upgrade to 0.5.1-4, which failed.
However, all of this is moot, since I upgraded to 0.5.1-5, which
appears to fix this problem completely. My mirror apparantly had not
gotten that debian revision yet, so I apologize for the over-eager bug
report :)
I'm closing this...
see you in hel?
micah
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
