Bug 3440 - Sound-Juicer requires for profile editor are missing (was: incomplete)
Summary: Sound-Juicer requires for profile editor are missing (was: incomplete)
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2011-11-25 01:09 CET by Juan Magallon
Modified: 2014-05-08 18:07 CEST (History)
7 users (show)

See Also:
Source RPM: sound-juicer-3.3.90-1.mga2.src.rpm
CVE:
Status comment:


Attachments

Description Juan Magallon 2011-11-25 01:09:51 CET
I tried to edit the ripping profiles in sound-juicer preferences
and got a message about a missing ui file, from libgnome-media-profiles.
I installed it and the editor worked.

Diagnose:

werewolf:~# rpm -q --requires sound-juicer | grep profiles
libgnome-media-profiles-3.0.so.0()(64bit)  

werewolf:~# rpm -q --provides lib64gnome-media-profiles0
libgnome-media-profiles-3.0.so.0()(64bit)  
lib64gnome-media-profiles0 = 3.0.0-8.mga2
lib64gnome-media-profiles0(x86-64) = 3.0.0-8.mga2

So it just requires the lib. Missing part, the binaries and UI files:

werewolf:~# rpm -q --provides libgnome-media-profiles
libgnome-media-profiles = 3.0.0-8.mga2
libgnome-media-profiles(x86-64) = 3.0.0-8.mga2

Perhaps other apps are in the same state.
Q'n'Dirty solution, make lib require binaries.
Comment 1 Manuel Hiebel 2011-11-25 01:20:54 CET
Hi, thanks for reporting this bug.
As there is no maintainer for this package I added the committers in CC.

CC: (none) => dmorganec, eandry
Summary: SJ requires for profile editor are incomplete => Sound-Juicer requires for profile editor are incomplete

Comment 2 Marja Van Waes 2012-01-22 19:52:33 CET
still no maintainer for sound-juicer

CC: (none) => marja11

Comment 3 Marja Van Waes 2012-04-13 17:08:49 CEST
Sound-juicer has a totally different version in cauldron now, is this bug still valid?
sound-juicer-3.3.90-1.mga2

Keywords: (none) => NEEDINFO

Comment 4 Marja Van Waes 2012-05-02 09:17:57 CEST
@ JA Magallón, 

could you please reply to the previous question? If you won't reply within two weeks from now, I will have to close this bug as OLD. Thank you.
Comment 5 Juan Magallon 2012-05-04 00:07:44 CEST
I've been able to delete the profile libs and still launch and rip with sound-juicer:
werewolf:~# urpme lib64gnome-media-profiles0-3.0.0-8.mga2 libgnome-media-profiles-3.0.0-8.mga2
To satisfy dependencies, the following 3 packages will be removed (5.8MB):
  gnome-media-2.91.2-1.mga2.x86_64
   (due to missing libgnome-media-profiles-3.0.so.0()(64bit))
  lib64gnome-media-profiles0-3.0.0-8.mga2.x86_64
  libgnome-media-profiles-3.0.0-8.mga2.x86_64
   (due to missing libgnome-media-profiles-3.0.so.0()(64bit))
Remove 3 packages? (y/N) y

In fact, preferences in Sound Juicer do not offer the same profiles for ripping that you can see with gnome-audio-profiles-properties.

So the dependency is fixed, because it is not needed anymore.

But that raises a new question, how can I edit profiles now ?

CC: (none) => jamagallon

Comment 6 Juan Magallon 2012-05-04 00:11:43 CEST
I found that there is a new version of gnome-media 3.4.0, vs 2.91.2 in Cauldron.
Time to bug...
Comment 7 Juan Magallon 2012-05-04 00:35:22 CEST
BTW, I also found that sound-juicer 3.4.0 final is there.
Comment 8 Marja Van Waes 2012-05-04 07:58:23 CEST
(In reply to comment #5)
> I've been able to delete the profile libs and still launch and rip with
> sound-juicer:
> werewolf:~# urpme lib64gnome-media-profiles0-3.0.0-8.mga2
> libgnome-media-profiles-3.0.0-8.mga2
> To satisfy dependencies, the following 3 packages will be removed (5.8MB):
>   gnome-media-2.91.2-1.mga2.x86_64
>    (due to missing libgnome-media-profiles-3.0.so.0()(64bit))
>   lib64gnome-media-profiles0-3.0.0-8.mga2.x86_64
>   libgnome-media-profiles-3.0.0-8.mga2.x86_64
>    (due to missing libgnome-media-profiles-3.0.so.0()(64bit))
> Remove 3 packages? (y/N) y
> 
> In fact, preferences in Sound Juicer do not offer the same profiles for ripping
> that you can see with gnome-audio-profiles-properties.
> 
> So the dependency is fixed, because it is not needed anymore.
> 
> But that raises a new question, how can I edit profiles now ?

(In reply to comment #6)
> I found that there is a new version of gnome-media 3.4.0, vs 2.91.2 in
> Cauldron.
> Time to bug...

(In reply to comment #7)
> BTW, I also found that sound-juicer 3.4.0 final is there.

cc'ing two more committers of sound-juicer, wally and ovitters 

There isn't a maintainer for gnome-media either.

cc'ing coling and boklm who both once committed gnome-media.

Keywords: NEEDINFO => (none)
CC: (none) => boklm, jani.valimaa, mageia, olav
Summary: Sound-Juicer requires for profile editor are incomplete => Sound-Juicer requires for profile editor are missing (was: incomplete)
Source RPM: sound-juicer-2.32.0-3.mga2.src.rpm => sound-juicer-3.3.90-1.mga2.src.rpm

Comment 9 Marja Van Waes 2012-05-26 13:10:19 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 10 Marja Van Waes 2012-06-12 11:51:56 CEST
This one was still valid May 4th

@ JA Magallón

I can imagine very well you're fed up with confirming again the bug is still valid.

However we need to know again. Please remove NEEDINFO from the Keywords and put MGA2TOO on the whiteboard if is.

Thanks :)
Comment 11 Marja Van Waes 2012-07-01 15:49:05 CEST
2x no reply, closing as old.

Feel free to reopen when needed and tell in which fully updated Mageia version(s) you still have this bug
Comment 12 Marja Van Waes 2012-07-01 15:49:21 CEST
(In reply to comment #11)
> 2x no reply, closing as old.
> 
> Feel free to reopen when needed and tell in which fully updated Mageia
> version(s) you still have this bug

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

Nicolas Vigier 2014-05-08 18:07:19 CEST

CC: boklm => (none)


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