Bug 788292

Summary:	splashy still used because the package suspend holds on to it
Product:	[openSUSE] openSUSE 12.2	Reporter:	Forgotten User --EoyBps8f <forgotten_--EoyBps8f>
Component:	Other	Assignee:	Thomas Renninger <trenn>
Status:	RESOLVED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	auxsvr, riggwelter
Version:	Final
Target Milestone:	---
Hardware:	Other
OS:	openSUSE 12.2
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Forgotten User --EoyBps8f 2012-11-06 09:31:27 UTC

User-Agent:       Mozilla/5.0 (X11; Linux i686) AppleWebKit/537.13 (KHTML, like Gecko) Chrome/24.0.1290.0 Safari/537.13 SUSE/24.0.1290.0

In 12.2 plymouth should be used instead of splashy. However it seems splashy is still used and removing it results in the removal of:

plymouth plymouth-branding-openSUSE plymouth-scripts splashy splashy-branding-openSUSE suspend

and the installtion of:

bootsplash

A guess: suspend still holds on to splashy and bootsplash conflicts with plymouth.

Expected behaviour: 12.2's suspend should not depend on splashy and removing splashy should make plymouth the tool to be used for splashy's job.

Reproducible: Always

Comment 1 James Ogley 2012-11-06 09:45:20 UTC

It's down to linking rather than an explicit reference in the spec file:

ogley@capybara:~> rpm -q --requires suspend | grep splash
libsplashy.so.1()(64bit)  

This could well be because the spec file still has:

BuildRequires:  splashy-devel
...
        --enable-splashy \

Comment 2 James Ogley 2012-11-06 11:50:07 UTC

There are test packages with these references removed in home:riggwelter:branches:openSUSE:12.2:Update - they appear to work but I can't confirm because of bug #782817 - can someone for whom that bug doesn't occur test them please?

Comment 3 Forgotten User --EoyBps8f 2012-11-06 12:30:23 UTC

The test packages work in regard to removing splashy only.

Since I encounter the splash=y bug as well, I cannot test that aspect either. :(

Comment 5 Thomas Renninger 2013-03-19 15:17:34 UTC

I took over the package, but do not have a good overview yet (it's some time ago I looked at suspend bugs and those were more lower leveled).
I doubt it makes sense to change splashy dependencies or usage in 12.2 anymore.
Even for 12.3 it may be difficult, first things should definitely get fixed for latest code base.
Is your cleanup still necessary for factory?
Could you attach a diff (eosc diff) for review, please.

Comment 6 Thomas Renninger 2014-06-16 11:02:40 UTC

This could well be because the spec file still has:
BuildRequires:  splashy-devel
...
        --enable-splashy \

This is not the case anymore (suspend.spec):
This could well be because the spec file still has:
BuildRequire: splashy-devel is gone and it has:
        --disable-splashy

Resolved fixed. Probably not for 12.2, but at least for Factory.