Debian Bug report logs - #384573
Russian id3 tags problem

Toggle useless messages

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

From: "Timur S. Sattarov" <timur@sattaroff.name>

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

Subject: Russian id3 tags problem

Date: Fri, 25 Aug 2006 12:17:37 +0500

Package: libtag1c2a
Version: 1.4-4
Severity: normal
Tags: patch

Hi, I've amarok installed on my system and some files which has russian
id3 tags in windows-1251 codepage inside and I run amarok in UTF8
environment. It uses libtag1c2a as a tool for reading id3 tags and tags
in cp1251 or other russian codepage are not displaying correctly.
There is a patch to taglib for correct detecting codepage of id3 tags available at
http://rusxmms.sourceforge.net/index.php?page=download.php 
could you please apply it to taglib ?

Thanks in advance.

Timur.


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)

Versions of packages libtag1c2a depends on:
ii  libc6                         2.3.6-19   GNU C Library: Shared libraries
ii  libgcc1                       1:4.1.1-10 GCC support library
ii  libstdc++6                    4.1.1-10   The GNU Standard C++ Library v3
ii  zlib1g                        1:1.2.3-13 compression library - runtime

libtag1c2a recommends no packages.

-- no debconf information

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

From: Alexander Myodov <maa_subscriptions@sinn.ru>

To: 384573@bugs.debian.org

Subject: Russian id3 tags problem

Date: Sat, 17 Mar 2007 14:28:48 +0300

Hello,

> Hi, I've amarok installed on my system and some files which has russian
> id3 tags in windows-1251 codepage inside and I run amarok in UTF8
> environment. It uses libtag1c2a as a tool for reading id3 tags and tags
> in cp1251 or other russian codepage are not displaying correctly.
> There is a patch to taglib for correct detecting codepage of id3 tags available at
> http://rusxmms.sourceforge.net/index.php?page=download.php
> could you please apply it to taglib ?

Any news on fixing this bug? This is an issue really painful for many
russian users who have large MP3 collections with russian tags, so
having this library fixed would be really useful.


-- 
With best regards,
 Alexander                          mailto:maa_subscriptions@sinn.ru

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

From: Adeodato Simó <dato@net.com.org.es>

To: Alexander Myodov <maa_subscriptions@sinn.ru>, 384573@bugs.debian.org, "Timur S. Sattarov" <timur@sattaroff.name>

Cc: control@bugs.debian.org

Subject: Re: Bug#384573: Russian id3 tags problem

Date: Fri, 20 Apr 2007 17:11:45 +0200

tag 384573 wontfix
thanks

* Alexander Myodov [Sat, 17 Mar 2007 14:28:48 +0300]:

> Hello,

Hi,

> > Hi, I've amarok installed on my system and some files which has russian
> > id3 tags in windows-1251 codepage inside and I run amarok in UTF8
> > environment. It uses libtag1c2a as a tool for reading id3 tags and tags
> > in cp1251 or other russian codepage are not displaying correctly.
> > There is a patch to taglib for correct detecting codepage of id3 tags available at
> > http://rusxmms.sourceforge.net/index.php?page=download.php
> > could you please apply it to taglib ?

> Any news on fixing this bug? This is an issue really painful for many
> russian users who have large MP3 collections with russian tags, so
> having this library fixed would be really useful.

This patch is rather intrusive and furthermore would make taglib link to
a library that is not even in Debian, so I won't apply it.

I seem to recall that there was an option in amarok to set the charset
of ID3v1 tags, but I can't find it now. Maybe it's more useful that you
see why it was removed, or that you talk with the taglib author to
include your patch.

HTH,

-- 
Adeodato Simó                                     dato at net.com.org.es
Debian Developer                                  adeodato at debian.org
 
We learned that the Linux load average rolls over at 1024. And we
actually found this out empirically.
                -- H. Peter Anvin from kernel.org

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

From: Modestas Vainius <modestas@vainius.eu>

To: ivan <ivan1986@list.ru>

Cc: 384573@bugs.debian.org

Subject: Re: RusXMMS patch

Date: Thu, 20 Nov 2008 15:24:47 +0200

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

Hello,

trečiadienis 19 Lapkritis 2008, jūs rašėte:
> A You agree to add this patch to taglib?
Followup the bug #384573, reattach your current attachment and try to negate 
the arguments why this bug should be unmarked as wontfix. It also looks rather 
intrusive to me and I'm afraid it could break other encodings.

However, what is the most important and a real showstopper, there is NO 
librcc-dev in Debian.

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=384573


-- 
Modestas Vainius <modestas@vainius.eu>

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

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

From: ivan <ivan1986@list.ru>

To: Modestas Vainius <modestas@vainius.eu>

Cc: 384573@bugs.debian.org

Subject: Re: RusXMMS patch

Date: Thu, 20 Nov 2008 19:59:33 +0300

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

On Thursday 20 November 2008 16:24:47 Modestas Vainius wrote:

> Followup the bug #384573, reattach your current attachment and try to
> negate the arguments why this bug should be unmarked as wontfix. It also
> looks rather intrusive to me and I'm afraid it could break other encodings.
>
> However, what is the most important and a real showstopper, there is NO
> librcc-dev in Debian.

I build deb packages for librcc and librcd, mayby i create package 
libtag-rusxmms and write Conflicts and Replaces for this?

How i understand this marks give chouse for users - select patched and no 
patched package - and by default non patched of couse.

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

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

From: Modestas Vainius <modestas@vainius.eu>

To: ivan <ivan1986@list.ru>, 384573@bugs.debian.org

Subject: Re: Bug#384573: RusXMMS patch

Date: Thu, 20 Nov 2008 19:51:44 +0200

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

Hello,

ketvirtadienis 20 Lapkritis 2008, ivan rašė:
> I build deb packages for librcc and librcd, mayby i create package
> libtag-rusxmms and write Conflicts and Replaces for this?
When you get needed external libraries (librcc if I understand correctly) into 
Debian, you can get back to me about this bug. Until then, nothing can be 
done.

-- 
Modestas Vainius <modestas@vainius.eu>

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

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

From: ivan <ivan1986@list.ru>

To: Modestas Vainius <modestas@vainius.eu>

Cc: 384573@bugs.debian.org

Subject: Re: Bug#384573: RusXMMS patch

Date: Thu, 20 Nov 2008 23:44:12 +0300

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

On Thursday 20 November 2008 20:51:44 Modestas Vainius wrote:
> Hello,
>
> ketvirtadienis 20 Lapkritis 2008, ivan rašė:
> > I build deb packages for librcc and librcd, mayby i create package
> > libtag-rusxmms and write Conflicts and Replaces for this?
>
> When you get needed external libraries (librcc if I understand correctly)
> into Debian, you can get back to me about this bug. Until then, nothing can
> be done.

I upload this libraries to mentors.debian.net, but i search sponsor for upload 
libraries into Debian. Mb You help?

http://mentors.debian.net/cgi-bin/sponsor-pkglist?action=details;package=librcd
http://mentors.debian.net/cgi-bin/sponsor-pkglist?action=details;package=librcc

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

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

From: Modestas Vainius <modestas@vainius.eu>

To: ivan <ivan1986@list.ru>, 384573@bugs.debian.org

Subject: Re: Bug#384573: RusXMMS patch

Date: Thu, 20 Nov 2008 22:55:36 +0200

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

Hello,

ketvirtadienis 20 Lapkritis 2008, ivan rašė:
> I upload this libraries to mentors.debian.net, but i search sponsor for
> upload libraries into Debian. Mb You help?
Nope. I'm not Debian Developer, I'm only Debian Maintainer and I cannot 
sponsor packages.


-- 
Modestas Vainius <modestas@vainius.eu>

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

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

From: ivan <ivan1986@list.ru>

To: Modestas Vainius <modestas@vainius.eu>

Cc: 384573@bugs.debian.org

Subject: librcc in sid

Date: Wed, 14 Jan 2009 22:38:57 +0300

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

Hello

librcc uploaded in sid, may are You look on patch?

Patch is safe for other languages and by default work on russian, ukrainian 
and belarussian languages - on any other lang string is not change.

I add this patch in package, this patch correct work on my system and long 
time use in ALTLinux. Look in this please, it's normal?

[taglib_1.5-3.1.diff.gz (application/x-gzip, attachment)]

[taglib_1.5-3.1.dsc (text/plain, attachment)]

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

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

From: Modestas Vainius <modestas@vainius.eu>

To: ivan <ivan1986@list.ru>, 384573@bugs.debian.org

Subject: Re: Bug#384573: librcc in sid

Date: Wed, 14 Jan 2009 22:47:29 +0200

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

Hello,

trečiadienis 14 Sausis 2009, ivan rašė:
> librcc uploaded in sid, may are You look on patch?
I see you worked hard to get this library into archive. However:

1) The package is currently not available on other arches but i386. Make sure 
it builds on other arches first (I'm using amd64).

2) You bundle librcc together with gtk/ui frontend of some sort in the single 
package. I surely don't want libtag to depend on gtk. Please split gtk stuff 
off from librcc0, leave only librcc.so.0 in there (I know that this means NEW 
again, but I'm sorry, GTK dependency is not acceptable for taglib).

> Patch is safe for other languages and by default work on russian, ukrainian
> and belarussian languages - on any other lang string is not change.
Which portion of the patch supports this claim? I don't see any locale check 
in the patch.

Then get back to me.

-- 
Modestas Vainius <modestas@vainius.eu>

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

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

From: Modestas Vainius <modestas@vainius.eu>

To: ivan <ivan1986@list.ru>, 384573@bugs.debian.org

Subject: Re: Bug#384573: librcc in sid

Date: Wed, 14 Jan 2009 23:05:38 +0200

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

Hello,

trečiadienis 14 Sausis 2009, ivan rašė:
> librcc uploaded in sid, may are You look on patch?
Ah, and another much more important blocker: librcc is GPL, taglib is LGPL. So 
according to [1], taglib license must be switched to GPL in order to allow 
legal distribution. I am pretty sure that this is not going to happen, so you 
better ask librcc author to relicense the library under LGPL v2 or later. 
Otherwise taglib linked with librcc cannot be distributed legally.

http://www.gnu.org/licenses/gpl-faq.html#compat-matrix-footnote-7

-- 
Modestas Vainius <modestas@vainius.eu>

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

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

From: ivan <ivan1986@list.ru>

To: 384573@bugs.debian.org

Cc: Modestas Vainius <modestas@vainius.eu>

Subject: new librcc

Date: Mon, 19 Jan 2009 00:21:41 +0300

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

Hello

new version of librcc in sid, there not changes in patch and in dependens 
packages.
all bugs fix and new version on LGPL

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

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

From: ivan <ivan1986@list.ru>

To: 384573@bugs.debian.org

Cc: Modestas Vainius <modestas@vainius.eu>

Subject: locale check

Date: Mon, 19 Jan 2009 00:37:36 +0300

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

>Which portion of the patch supports this claim? I don't see any locale check 
in the patch.
Locale check in librcc:

rcc_language rcc_default_languages_embeded[RCC_MAX_LANGUAGES + 1] = {
{rcc_default_language_sn, {rcc_default_charset, NULL}, {
    &rcc_default_engine,
    NULL
}},
{rcc_disabled_language_sn, {rcc_default_charset, NULL}, {
    &rcc_default_engine,
    NULL
}},
{rcc_english_language_sn, {rcc_default_charset, rcc_utf8_charset, "ISO8859-1", 
NULL}, {
    &rcc_default_engine,
    NULL
}},
{rcc_russian_language_sn, 
{rcc_default_charset,"KOI8-R","CP1251",rcc_utf8_charset,"IBM866","MACCYRILLIC","ISO8859-5", 
NULL}, {
    &rcc_default_engine,
#ifdef RCC_RCD_SUPPORT
    &rcc_russian_engine,
#endif /* RCC_RCD_SUPPORT */
    NULL
}},
{rcc_ukrainian_language_sn, 
{rcc_default_charset,"KOI8-U","CP1251",rcc_utf8_charset,"IBM855","MACCYRILLIC","ISO8859-5","CP1125", 
NULL}, {
    &rcc_default_engine,
#ifdef RCC_RCD_SUPPORT
    &rcc_ukrainian_engine,
#endif /* RCC_RCD_SUPPORT */
    NULL
}},
{"be", {rcc_default_charset, 
rcc_utf8_charset, "CP1251", "IBM866", "ISO-8859-5", "ISO-IR-111", "ISO-IR-111", "MACCYRILLIC" "IBM855", 
NULL},{
    &rcc_default_engine,
#ifdef RCC_RCD_SUPPORT
    &rcc_ukrainian_engine,
#endif /* RCC_RCD_SUPPORT */
    NULL
}},
/*{"bg", {rcc_default_charset, 
rcc_utf8_charset, "CP1251", "ISO-8859-5", "IBM855", "maccyr", "ECMA-113", 
NULL},{

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

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

From: Modestas Vainius <modestas@vainius.eu>

To: ivan <ivan1986@list.ru>, 384573@bugs.debian.org

Subject: Re: Bug#384573: new librcc

Date: Mon, 19 Jan 2009 00:07:42 +0200

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

Hello,

sekmadienis 18 Sausis 2009, ivan rašė:
> new version of librcc in sid, there not changes in patch and in dependens
> packages.
> all bugs fix and new version on LGPL
ok. However, I think I'll still provide two versions of libtag1c2a which could 
be used interchangeably: libtag1-vanilla (original) and libtag1-rusxmms (is 
this correct name or is libtag1-rcc (I like the latter more) better?) with 
libtag1-vanilla being default. I think it is a good compromise between 
standard compliance and real world in Russia/Ukraine/Belarus to ask users 
wanting librcc functionality to install libtag1-rcc manually. What is more, I 
believe such broken tags should disappear soon as better player are written. 
Btw, have you tried pushing this to taglib upstream?

-- 
Modestas Vainius <modestas@vainius.eu>

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

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

From: ivan <ivan1986@list.ru>

To: Modestas Vainius <modestas@vainius.eu>

Cc: 384573@bugs.debian.org

Subject: Re: Bug#384573: new librcc

Date: Mon, 19 Jan 2009 02:11:18 +0300

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

On Monday 19 January 2009 01:09:30 you wrote:
> Hello,
>
> sekmadienis 18 Sausis 2009, ivan rašė:
> > new version of librcc in sid, there not changes in patch and in dependens
> > packages.
> > all bugs fix and new version on LGPL
>
> ok. However, I think I'll still provide two versions of libtag1c2a which
> could be used interchangeably: libtag1-vanilla (original) and
> libtag1-rusxmms (is this correct name or is libtag1-rcc (I like the latter
> more) better?) with libtag1-vanilla being default. I think it is a good
> compromise between standard compliance and real world in
> Russia/Ukraine/Belarus to ask users wanting librcc functionality to install
> libtag1-rcc manually. What is more, I believe such broken tags should
> disappear soon as better player are written. 

That's cool, i try to do the same whis other copy of original source, but i 
don't know how build patched and non-patched binary package from one source.
May be this will be useful for You.
I thisk rusxmms is better - this patch know on this name.

> Btw, have you tried pushing this to taglib upstream?

I be try, but they not fix this :(

[taglib-rusxmms_1.5-3.1.diff.gz (application/x-gzip, attachment)]

[taglib-rusxmms_1.5-3.1.dsc (text/plain, attachment)]

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

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

From: ivan <ivan1986@list.ru>

To: Modestas Vainius <modestas@vainius.eu>

Cc: 384573@bugs.debian.org

Subject: Bug#384573

Date: Sat, 31 Jan 2009 21:12:10 +0300

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

Hello.
What results of adding patch now and may i help for somethings?

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

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

From: Modestas Vainius <modestas@vainius.eu>

To: ivan <ivan1986@list.ru>

Cc: 384573@bugs.debian.org

Subject: Re: Bug#384573

Date: Sun, 1 Feb 2009 03:39:01 +0200

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

Hello,

2009 m. Sausis 31 d., šeštadienis, jūs rašėte:
> What results of adding patch now and may i help for somethings?
Please be more patient. Unfortunately, I won't have time for this during 
upcomming week. Thanks for offering help. You can be sure that whenever the 
next upload happens, it will fix this bug.

-- 
Modestas Vainius <modestas@vainius.eu>

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

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

From: Modestas Vainius <modestas@vainius.eu>

To: ivan <ivan1986@list.ru>, 384573@bugs.debian.org

Subject: Re: Bug#384573:

Date: Fri, 20 Mar 2009 02:24:46 +0200

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

Hello,

On 2009 m. January 31 d., Saturday 20:12:10 ivan wrote:
> Hello.
> What results of adding patch now and may i help for somethings?
So I have uploaded 1.5-5 with RusXMMS support to experimental today. However, 
it obviously got stuck in NEW. I would be greatful if you subscribed to taglib 
PTS and took care of any rusxmms bugs when/if they arise.

-- 
Modestas Vainius <modestas@vainius.eu>

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

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

From: Modestas Vainius <modestas@vainius.eu>

To: 384573-close@bugs.debian.org

Subject: Bug#384573: fixed in taglib 1.5-5

Date: Sat, 21 Mar 2009 23:40:22 +0000

Source: taglib
Source-Version: 1.5-5

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

libtag1-dev_1.5-5_amd64.deb
  to pool/main/t/taglib/libtag1-dev_1.5-5_amd64.deb
libtag1-doc_1.5-5_all.deb
  to pool/main/t/taglib/libtag1-doc_1.5-5_all.deb
libtag1-rusxmms_1.5-5_amd64.deb
  to pool/main/t/taglib/libtag1-rusxmms_1.5-5_amd64.deb
libtag1-vanilla_1.5-5_amd64.deb
  to pool/main/t/taglib/libtag1-vanilla_1.5-5_amd64.deb
libtag1c2a_1.5-5_amd64.deb
  to pool/main/t/taglib/libtag1c2a_1.5-5_amd64.deb
libtagc0-dev_1.5-5_amd64.deb
  to pool/main/t/taglib/libtagc0-dev_1.5-5_amd64.deb
libtagc0_1.5-5_amd64.deb
  to pool/main/t/taglib/libtagc0_1.5-5_amd64.deb
taglib_1.5-5.diff.gz
  to pool/main/t/taglib/taglib_1.5-5.diff.gz
taglib_1.5-5.dsc
  to pool/main/t/taglib/taglib_1.5-5.dsc



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 384573@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Modestas Vainius <modestas@vainius.eu> (supplier of updated taglib 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: Fri, 20 Mar 2009 01:36:31 +0200
Source: taglib
Binary: libtag1c2a libtag1-vanilla libtag1-rusxmms libtag1-dev libtag1-doc libtagc0 libtagc0-dev
Architecture: source amd64 all
Version: 1.5-5
Distribution: experimental
Urgency: low
Maintainer: Modestas Vainius <modestas@vainius.eu>
Changed-By: Modestas Vainius <modestas@vainius.eu>
Description: 
 libtag1-dev - TagLib Audio Meta-Data Library [development]
 libtag1-doc - TagLib Audio Meta-Data Library [documentation]
 libtag1-rusxmms - TagLib Audio Meta-Data Library (RusXMMS flavour)
 libtag1-vanilla - TagLib Audio Meta-Data Library (Vanilla flavour)
 libtag1c2a - TagLib Audio Meta-Data Library
 libtagc0   - TagLib Audio Meta-Data Library (C bindings)
 libtagc0-dev - TagLib Audio Meta-Data Library (C bindings) [development]
Closes: 384573
Changes: 
 taglib (1.5-5) experimental; urgency=low
 .
   * Port buildsystem from cdbs to debhelper v7 (>= 7.0.50). cmake
     support implemented via dh_overrides.
   * Pass CMAKE_USE_RELATIVE_PATHS=ON to cmake. Hence build depend on
     cmake 2.6.2.
   * Strip debian/tmp from debian/*.install files. Not needed with dh v7.
   * Add RusXMMS support (Closes: #384573):
     - RusXMMS patch contributed by Ivan Borzenkov, thanks;
     - add two libtag1 flavours: vanilla (libtag1-vanilla) and rusxmms
       libtag1-rusxmms);
     - new libtag1-* flavours replaces old libtag1c2a;
     - libtag1c2a becomes a metapackage which depends on either of flavours
       via alternate depends. Both libtag1-vanilla and libtag1-rusxmms export
       themselves as libtag1c2a via shlibs/symbol files;
     - rework buildsystem and build both flavours in their own build directories
       (builddir-vanilla and builddir-rusxmms);
     - employ some quilt on-the-fly patching hacks to patch and unpatch source
       with rusxmms patch as needed;
     - build depend on librcc-dev. RusXMMS needs it;
     - add more lintian-overrides as the changes above triggered them.
   * Get rid of old conflicts/replaces of the libtag1c2a package.
Checksums-Sha1: 
 743f6098812e99a327fc015a8e5a29c206605ad5 1373 taglib_1.5-5.dsc
 0bb9180e3480625af4bbc661c66dca7df0edc7dd 21616 taglib_1.5-5.diff.gz
 ecad723b8a0b73ce05eef7f7e99911cad74205ed 7064 libtag1c2a_1.5-5_amd64.deb
 0c52f03562fa383c9126fda857537680dece8830 175720 libtag1-vanilla_1.5-5_amd64.deb
 81ba0287043d2236bde20ec736f6f4df6d4093b2 178230 libtag1-rusxmms_1.5-5_amd64.deb
 827d1555b9362e221f348bcb98ace28b35ffb6c1 66474 libtag1-dev_1.5-5_amd64.deb
 20e7a0ade987f8faf86226b99786704d88958ef9 1112056 libtag1-doc_1.5-5_all.deb
 c4ba6d9c144b7a84d50678c23dcfdd3c4270ec71 12582 libtagc0_1.5-5_amd64.deb
 90b512a86e3654e022b44df04099823f78b7b9dc 9958 libtagc0-dev_1.5-5_amd64.deb
Checksums-Sha256: 
 eb67802a3768238fcafc1d6103fc7c8197bbb28b3107d9f771f6d5accab09271 1373 taglib_1.5-5.dsc
 3c5af35cc1903f80e337c0f4743efafa327c702c3db6437c4f961d9d6447fedc 21616 taglib_1.5-5.diff.gz
 7222cbb0767ce68808a5db9cde4313b7b6bed437469cf5544b548c83a15fe822 7064 libtag1c2a_1.5-5_amd64.deb
 495cb6aad8f253e8c86b03b30d96a8f339c6a694d065e48a86642471de7c4272 175720 libtag1-vanilla_1.5-5_amd64.deb
 27132c9f6c422fd0061428a559e32fd93ff69774a26333e3f0a877c138533049 178230 libtag1-rusxmms_1.5-5_amd64.deb
 2d94435aa0022fbe132062776e78a42867be3251f43bcd9d2de68259131a0f9b 66474 libtag1-dev_1.5-5_amd64.deb
 0c9845a6e2733dd2cec7c93c4cac88cf9c592c34f3e91a4ffb90ba8493b5653e 1112056 libtag1-doc_1.5-5_all.deb
 982c007eb41fd4486e0fa9d909a1e6a911a867da77b988cef5f1470bb5ffc4bd 12582 libtagc0_1.5-5_amd64.deb
 ef83606cb8d7d22193a776839a2db57f0338f1e462f0232b0f7bded99f541911 9958 libtagc0-dev_1.5-5_amd64.deb
Files: 
 796f21948380c4d2645b4045dff9bb54 1373 libs optional taglib_1.5-5.dsc
 01a0662525e4064f894f6f28010d4f97 21616 libs optional taglib_1.5-5.diff.gz
 b26abda22cef7a0335bacd12d6ec4e5e 7064 libs optional libtag1c2a_1.5-5_amd64.deb
 70449aa11e4fc2885579b66d69c49214 175720 libs optional libtag1-vanilla_1.5-5_amd64.deb
 bf9c53971a426e805a80a76020967820 178230 libs optional libtag1-rusxmms_1.5-5_amd64.deb
 c046f0950524792da2fa5ea5690d651b 66474 libdevel optional libtag1-dev_1.5-5_amd64.deb
 632fd402e5edb9d740222013716e8539 1112056 doc optional libtag1-doc_1.5-5_all.deb
 2308f8c1a7c8d554f6e23fc88b1fc0f5 12582 libs optional libtagc0_1.5-5_amd64.deb
 980452230dc529a98dc665d0e84ef67b 9958 libdevel optional libtagc0-dev_1.5-5_amd64.deb

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

iEYEARECAAYFAknC2V0ACgkQHO9JRnPq4hQG8wCg1Wz5AQgYGyG1FvxIJ2hZQxbc
9egAoJui0tkvR7k5FY/zUv4L4CUOII3V
=YSIm
-----END PGP SIGNATURE-----

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

From: Modestas Vainius <modestas@vainius.eu>

To: ivan <ivan1986@list.ru>

Cc: 384573@bugs.debian.org

Subject: Re: Bug#384573:

Date: Sun, 22 Mar 2009 14:01:17 +0200

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

Hello,

taglib is in experimental. Please test and report problems if any. I want to 
get this over with and upload that taglib to unstable as soon as possible.

-- 
Modestas Vainius <modestas@vainius.eu>

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

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

From: ivan <ivan1986@list.ru>

To: Modestas Vainius <modestas@vainius.eu>

Cc: 384573@bugs.debian.org

Subject: Bug#384573: all work file

Date: Sun, 22 Mar 2009 17:51:12 +0300

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

On Sunday 22 March 2009 15:01:17 you wrote:

> taglib is in experimental. Please test and report problems if any. I want
> to get this over with and upload that taglib to unstable as soon as
> possible.

Hello,
All work fine - i remove my old packed and update libtagc0 and libtag1c2a
libtag1-vanilla install on depend, then i run amarok and show boroken tags, 
after that i install libtag1-rusxmms - all tags show normal.

Cool, all work :)

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

Send a report that this bug log contains spam.