Your message dated Wed, 09 May 2007 10:02:12 +0000
with message-id <[EMAIL PROTECTED]>
and subject line Bug#422720: fixed in lastfm 1:1.1.3.0-3
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: lastfm
Version: 1:1.1.3.0-2
Severity: normal

--- Please enter the report below this line. ---

lastfm 1.1.3.0-2 fails to install. aptitude log:

Preparing to replace lastfm 1:1.1.3.0-1 (using .../lastfm_1%3a1.1.3.0-2_i386.deb) ...
Unpacking replacement lastfm ...
dpkg: error processing /var/cache/apt/archives/lastfm_1%3a1.1.3.0-2_i386.deb (--unpack): trying to overwrite `/usr/share/gconf/schemas/lastfm.schemas', which is also in package last-exit
dpkg-deb: subprocess paste killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/lastfm_1%3a1.1.3.0-2_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install.  Trying to recover:

Regards,
 Dmitry

--- System information. ---
Architecture: i386
Kernel: Linux 2.6.18-4-686

Debian Release: lenny/sid
500 unstable ftp.debian.org
500 testing ftp.debian.org
1 experimental ftp.debian.org

--- Package information. ---
Depends (Version) | Installed
=============================-+-==============
libasound2 (>> 1.0.12) | 1.0.13-2
libc6 (>= 2.5-5) | 2.5-7
libgcc1 (>= 1:4.1.2) | 1:4.1.2-6
libqt4-core (>= 4.2.3) | 4.2.3-1+b1
libqt4-gui (>= 4.2.3) | 4.2.3-1+b1
libstdc++6 (>= 4.1.2) | 4.1.2-6
libx11-6 | 2:1.0.3-7
gconf2 (>= 2.10.1-2) | 2.18.0.1-3



--- End Message ---
--- Begin Message ---
Source: lastfm
Source-Version: 1:1.1.3.0-3

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

lastfm_1.1.3.0-3.diff.gz
  to pool/main/l/lastfm/lastfm_1.1.3.0-3.diff.gz
lastfm_1.1.3.0-3.dsc
  to pool/main/l/lastfm/lastfm_1.1.3.0-3.dsc
lastfm_1.1.3.0-3_i386.deb
  to pool/main/l/lastfm/lastfm_1.1.3.0-3_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 [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
John Stamp <[EMAIL PROTECTED]> (supplier of updated lastfm 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 [EMAIL PROTECTED])


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

Format: 1.7
Date: Tue, 08 May 2007 09:23:50 -0700
Source: lastfm
Binary: lastfm
Architecture: source i386
Version: 1:1.1.3.0-3
Distribution: unstable
Urgency: low
Maintainer: John Stamp <[EMAIL PROTECTED]>
Changed-By: John Stamp <[EMAIL PROTECTED]>
Description: 
 lastfm     - an audio player for last.fm personalized radio
Closes: 422720
Changes: 
 lastfm (1:1.1.3.0-3) unstable; urgency=low
 .
   * Remove the gconf schemas file and re-add the gconf defaults file from
     1.1.90.  This prevents a conflict with last-exit.  (Closes: #422720)
     This also reopens #369907 for now.  The keys will exist, but gconf-editor
     will report "This key has no schema".
Files: 
 488b2c63d8335dd9084aa879d3ef1e94 722 sound optional lastfm_1.1.3.0-3.dsc
 4e5dcee97664b636c0adb53758b2b8c2 103672 sound optional lastfm_1.1.3.0-3.diff.gz
 a0c60637a0aa42360ab434bb008b47c2 1256444 sound optional 
lastfm_1.1.3.0-3_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Signed by Adeodato Simó <[EMAIL PROTECTED]>

iEYEARECAAYFAkZBl7EACgkQgyNlRdHEGIKwoQCfTn7H6FooUWcMHmon27/4yASe
5gMAn2PjBy9qUyCv6VoUS0A6+0gNn7EQ
=x6TX
-----END PGP SIGNATURE-----


--- End Message ---

Reply via email to