Bug 19649

Summary:	mp3-tagging fails when ripping/encoding a audio CD with abcde
Product:	Mageia	Reporter:	Claudia Baetz <allanna>
Component:	RPM Packages	Assignee:	Shlomi Fish <shlomif>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	marja11
Version:	5
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
URL:	https://code.google.com/archive/p/abcde/issues/116
Whiteboard:
Source RPM:	abcde-2.5.4-5.mga5.src.rpm	CVE:
Status comment:

Description Claudia Baetz 2016-10-24 19:20:16 CEST

Description of problem:
abcde ends with an error if I want to rip and encode an audio cd with mp3 as output format. The problem seems to be that eyeD3 is called with wrong arguments and so fails to tag the tracks. The arguments for eyeD3 changed with v0.7 but abcde in Mageia uses the syntax for <v0.7. There is a patch for abcde under https://code.google.com/archive/p/abcde/issues/116 which introduces the eyeD3 v0.7+ syntax. 

The error message in abcde is:
"eyeD3: error: unrecognized arguments: --set-encoding=utf16-LE
[ERROR] abcde: The following commands failed to run:
tagtrack-mp3-1: returned code 1: nice -n 10 eyeD3 --set-encoding=utf16-LE --comment=:: -A Unknown Album -a Unknown Artist -t Track 1 -Y 2015 -G  -n 1 -N 10 /home/user/abcde.9b12b90a/track1.mp3
Finished. Not cleaning /home/user/abcde.9b12b90a."

Version-Release number of selected component (if applicable):
abcde-2.5.4-5.mga5, python-eyed3-0.7.4-7.mga5

How reproducible:
Every time I choose mp3 as output format.

Steps to Reproduce:
1. Insert an audio cd.
2. Rip the 1st track with "abcde -o mp3 1" on command line
3. If there is a CDDB match then press enter. If there is no CDDB match, you have to insert a year (this is another bug)-type "y" and insert a year behind "DYEAR=". Type ":wq"
4. Press enter
5. abcde ends with an error.

David Walser 2016-10-25 14:01:31 CEST

Assignee: bugsquad => shlomif

Comment 1 Marja Van Waes 2018-05-03 07:47:42 CEST

Hi Claudia,

Thank you for having taken the needed time to report this issue!

Did this bug get fixed? If so, please change its status to RESOLVED - FIXED

If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It only continued to get important security updates since then, because we are waiting for a big Plasma5 update in Mageia 6, that'll fix many of the Mageia 5 => 6 upgrade issues.

If you haven't seen that this bug got fixed, then please check whether this bug still exists in Mageia 6. If it does, then please change the Version (near the top, at the left) to "6". If you know it exists in Cauldron, then change Version to Cauldron. If you see it in both Cauldron and Mageia 6, then please set Version to Cauldron and add MGA6TOO on the Whiteboard.

Thanks,
Marja

CC: (none) => marja11

Comment 2 Marja Van Waes 2018-10-06 13:27:07 CEST

No reply, so closing as OLD.

@ Claudia

==> If you didn't reset your password after February 2018, then you'll need to reset it here https://identity.mageia.org/forgot_password to be able to log in and comment in this report. <==

Status: NEW => RESOLVED
Resolution: (none) => OLD