Bug 19650

Summary:	mp3-tagging fails in abcde if CDDB does not provide YEAR
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/107
Whiteboard:
Source RPM:	abcde-2.5.4-5.mga5.src.rpm	CVE:
Status comment:

Description Claudia Baetz 2016-10-24 20:29:39 CEST

Description of problem:
abcde uses eyeD3 to tag mp3-tracks. If the CDDB data contains no year, eyeD3 fails with following error message:
"eyeD3: error: argument -Y/--release-year: invalid PositiveIntArg value: ''
[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  -G  -n 1 -N 10 /home/user/abcde.9b12b90a/track1.mp3
Finished. Not cleaning /home/user/abcde.9b12b90a."

(If a year is given, eyeD3 fails with the next [https://bugs.mageia.org/show_bug.cgi?id=19649  Bug 19649].)

There is a patch for abcde under https://code.google.com/archive/p/abcde/issues/107.

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 if there is no year in the CDDB data.

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 no CDDB match, press enter. Otherwise type "y" and delete the year after "DYEAR=". Save with ":wq"
4. Press enter
5. abcde ends with an error ("eyeD3: error: argument -Y/--release-year: invalid PositiveIntArg value: ''")

David Walser 2016-10-25 14:02:00 CEST

Assignee: bugsquad => shlomif

Comment 1 Marja Van Waes 2018-05-03 07:48:19 CEST

Hi again, 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:43 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. <==

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