Bug 116154

Summary:	mplayer update
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Jean-Daniel Dodin <jdd>
Component:	YaST2	Assignee:	Jiri Srain <jsrain>
Status:	RESOLVED WONTFIX	QA Contact:	Klaus Kämpf <kkaempf>
Severity:	Enhancement
Priority:	P5 - None
Version:	RC 1
Target Milestone:	---
Hardware:	Other
OS:	All
Whiteboard:
Found By:	Beta-Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	conflict in updating and mplayer

Description Jean-Daniel Dodin 2005-09-09 15:14:12 UTC

I'm not really sure of what is the starting point. As long as I remember I
installed mplayer myself. It is now in my Yast2 list, but I found no way to know
 from what source it's from.

Anyway I installed mplayer and, with pain, all the necessary libs to play mp3,
mpg... it worked fine (on beta3)

when I updated to RC1 I got the lib conflict (see attached file).

I said "keep all", was warned this was dangerous and all when well (and mplayer
still works nicely).

the fact is mplayer was detected by Yast2, but not the libs.

I say this is a bug only because the message is frightening :-). I know these
libs are not suse-supported and will not be.

But this probably notes that there is a problem with the libs listing. maybe the
rpm database is not a sufficient knowledge source? (it was so difficult to have
all this working, I can't trace how I did success).

anyway, if the mplayer source is my disk and not suse's, Yast should know that.
It could have said "I have a dependency problem, it's because a package _you_
installed but is not in suse disks, you may need to fix this yourself" what is
perfectly reasonable.

Comment 1 Jean-Daniel Dodin 2005-09-09 15:15:19 UTC

Created attachment 49423 [details]
conflict in updating and mplayer

yast update report of update conflict with mplayer libraries

Comment 2 Michael Gross 2005-09-09 15:34:19 UTC

> I say this is a bug only because the message is frightening :-). I know these
> libs are not suse-supported and will not be.

Nice that you've noticed.
When you're installing foreign-packages, how should YaST notice that? This might
be an enhancement for one of the upcoming releases (10.1+).

A tip anyway: compiling these things from source, putting them somewhere on /opt
will not mess up your package-database and it might even work easier to get it
running.

I'll change this to enhancement, assign it to the yast2-team. They can decide if
this is realizable and would make sense.

Comment 3 Michael Gross 2005-09-09 15:38:10 UTC

Forgot to close with reso:later.

Comment 4 Jean-Daniel Dodin 2005-09-09 16:25:13 UTC

(In reply to comment #2)
> > I say this is a bug only because the message is frightening :-). I know these
> > libs are not suse-supported and will not be.
> 
> Nice that you've noticed.
> When you're installing foreign-packages, how should YaST notice that?

for packages, I don't see, but for libs it's seems easy, is there not a
libcache? Yast said there a no libs and there are here

> I'll change this to enhancement,

sure :-)

this problem is prone to arise anytime only part of a package is given by rpm's.
Yast should be able to know that this package is _not_ from suse and act acordingly.

 assign it to the yast2-team. They can decide if
> this is realizable and would make sense.

of course
thanks

Comment 5 Stephan Kulow 2008-06-25 09:33:12 UTC

mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)

Comment 6 Stephan Kulow 2008-06-25 09:34:49 UTC

mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)

Comment 7 Stephan Kulow 2008-06-25 09:41:04 UTC

mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)

Comment 8 Stephan Kulow 2008-06-25 09:52:42 UTC

Closing old LATER+REMIND bugs as WONTFIX - if you still plan to work on it, feel free to reopen and set to ASSIGNED.

In case the report saw repeated reopen comments, it's due to bugzilla timing out on the huge request ;(