In Woody, there is:
id3v2 0.1
Uses id3lib-3.7.13


anthony@Maxwell:SeanHanity$ id3v2 -l 2004-02-03.mp3
id3v1 tag info for 2004-02-03.mp3:
Title  : Radio Show: 2004-02-03.mp3      Artist: Sean Hanity
Album  :                                 Year: 2004, Genre: Speech (255)
Comment:                                 Track: 0
id3v2 tag info for 2004-02-03.mp3:
Title/songname/content description: Radio Show: 2004-02-03.mp3
Lead performer(s)/Soloist(s): Sean Hanity
Year: 2004
Content type: Talk Radio



But the version in Sarge says:
id3v1 tag info for 2004-02-03.mp3:
Title  : Radio Show: 2004-02-03.mp3      Artist: Sean Hanity
Album  :                                 Year: 2004, Genre: Speech (101)
Comment:                                 Track: 0
id3v2 tag info for 2004-02-03.mp3:
TIT2 (Title/songname/content description): Radio Show: 2004-02-03.mp3
TPE1 (Lead performer(s)/Soloist(s)): Sean Hanity
TYER (Year): 2004
TCON (Content type): Blues Talk Radio


Note the 'Blues' before 'Talk Radio'


eyeD3 shows 'Talk Radio' (though it says its an invalid genre). mpg321
says 'Talk Radio'. I think iTunes does as well (would have to check
again to be sure). Even 'strings' shows 'Talk Radio' in the file. I
think the new version of id3v2 is making up the word 'Blues'

- -- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux bohr 2.4.22-bohr #1 SMP Fri Dec 5 08:58:30 EST 2003 i686
Locale: LANG=en_US, LC_CTYPE=en_US

Versions of packages id3v2 depends on:
ii  libc6                       2.3.2.ds1-10 GNU C Library: Shared libraries an
ii  libgcc1                     1:3.3.2-4    GCC support library
ii  libid3-3.8.3                3.8.3-3      Library for manipulating ID3v1 and
ii  libstdc++5                  1:3.3.2-4    The GNU Standard C++ Library v3
ii  zlib1g                      1:1.2.1-3    compression library - runtime

- -- no debconf information
iD8DBQFAIEfS+z+IwlXqWf4RAjGjAJ0ZJiGjn5/nrQUbGG3czDHnaDPUxgCfXg1u
Gb8nzgSrQcltRx/gyVv82b0=
=UB0/
-----END PGP SIGNATURE-----

Hi

I cannot seem to reproduce this (admittedly rather old) bug, do you
happen to know whether it still occurs?

If not, I'm going to assume that it has been fixed by upstream since
and close this one.

cheers

This bug appears to be fixed upstream since 0.1.12-1.
I'm closing this bug report.

Martin