Bug 5538 - Rubyripper lost ability to connect to freedb.org server
Summary: Rubyripper lost ability to connect to freedb.org server
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 2
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Rémy CLOUARD (shikamaru)
QA Contact:
URL: http://code.google.com/p/rubyripper/i...
Whiteboard:
Keywords: PATCH, UPSTREAM
Depends on:
Blocks:
 
Reported: 2012-04-21 18:53 CEST by Drew Edwards
Modified: 2013-11-23 16:14 CET (History)
0 users

See Also:
Source RPM: rubyripper-0.6.0-1.mga1
CVE:
Status comment:


Attachments

Description Drew Edwards 2012-04-21 18:53:18 CEST
Description of problem:

Fully up-to-date cauldron, x86_64 installation.

For the last two weeks I have been re-ripping some of my cd collection into flac files using rubyripper.  As of this morning, the freedb.org lookup no longer works.

I don't think the rubyripper package has been updated, not sure what would cause this.

cli output here:

$ rrip_cli -v
ruby-gettext is not found. Translations are disabled!
Verbose output specified.
Audio-disc found, number of tracks : 6, total playlength : 51:07
Fetching freedb info...
Exception thrown: undefined method `[]=' for false:FalseClass
Couldn't connect to freedb server. Network down?

Default values will be shown...
Do you want to change your settings? (y/n) :  [y] n
Comment 1 Drew Edwards 2012-04-21 18:59:49 CEST
Forgot to mention:  grip connects successfully, so there is no network/server problem.
Manuel Hiebel 2012-04-21 22:40:15 CEST

Assignee: bugsquad => shikamaru

Comment 2 Drew Edwards 2012-04-27 02:57:12 CEST
This looks like the same issue:

http://code.google.com/p/rubyripper/issues/detail?id=496
Manuel Hiebel 2012-04-27 11:42:53 CEST

Keywords: (none) => PATCH, UPSTREAM
URL: (none) => http://code.google.com/p/rubyripper/issues/detail?id=496

Comment 3 Marja Van Waes 2012-05-26 13:03:28 CEST
Hi,

This bug was filed against cauldron, but we do not have cauldron at the moment.

Please report whether this bug is still valid for Mageia 2.

Thanks :)

Cheers,
marja

Keywords: (none) => NEEDINFO

Comment 4 Drew Edwards 2012-06-08 03:00:19 CEST
Currently valid for Mageia 2, I will check whether it still applies to Cauldron which is active again.

Version: Cauldron => 2

Manuel Hiebel 2012-06-17 02:08:13 CEST

Keywords: NEEDINFO => (none)

Comment 5 Manuel Hiebel 2013-10-22 12:11:03 CEST
This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life.  If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete.

-- 
The Mageia Bugsquad
Comment 6 Manuel Hiebel 2013-11-23 16:14:26 CET
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no
longer maintained, which means that it will not receive any further security or
bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

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


Note You need to log in before you can comment on or make changes to this bug.