Bug 962747

Summary:	Unwanted direct dep on mysql-libs and expat and wrong perms on service file.
Product:	[Fedora] Fedora	Reporter:	Terje Røsten <terje.rosten>
Component:	mediatomb	Assignee:	Gwyn Ciesla <gwync>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	17	CC:	gwync
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	mediatomb-0.12.1-28.fc17.20120403gitb66dc1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-05-24 20:47:42 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Terje Røsten 2013-05-14 11:28:13 UTC

Description of problem:

mediatomb links against mysql and expat and rpmbuild picks up the deps:

libmysqlclient.so.18, libmysqlclient.so.18(libmysqlclient_16) and
libexpat.so.1

However, mediatomb also have a direct dep on mysql-libs and expat

Requires: mysql-libs, expat

There are no need for these explicit reqs.

Ref: http://koji.fedoraproject.org/koji/rpminfo?rpmID=3921658

rpmlint error:

mediatomb.x86_64: E: explicit-lib-dependency mysql-libs

mediatombs also installs service with execute bit, that's wrong,
it's a config file which correct perms is 0644.

mediatomb.x86_64: E: script-without-shebang /usr/lib/systemd/system/mediatomb.service

Comment 1 Fedora Update System 2013-05-14 12:07:35 UTC

mediatomb-0.12.1-27.fc19.20120403gitb66dc1 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/mediatomb-0.12.1-27.fc19.20120403gitb66dc1

Comment 2 Fedora Update System 2013-05-14 12:08:31 UTC

mediatomb-0.12.1-27.fc18.20120403gitb66dc1 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/mediatomb-0.12.1-27.fc18.20120403gitb66dc1

Comment 3 Fedora Update System 2013-05-14 12:09:21 UTC

mediatomb-0.12.1-27.fc17.20120403gitb66dc1 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/mediatomb-0.12.1-27.fc17.20120403gitb66dc1

Comment 4 Terje Røsten 2013-05-14 13:36:59 UTC

Thanks!

Comment 5 Fedora Update System 2013-05-14 17:46:57 UTC

Package mediatomb-0.12.1-27.fc19.20120403gitb66dc1:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing mediatomb-0.12.1-27.fc19.20120403gitb66dc1'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-8159/mediatomb-0.12.1-27.fc19.20120403gitb66dc1
then log in and leave karma (feedback).

Comment 6 Fedora Update System 2013-05-14 19:33:32 UTC

mediatomb-0.12.1-28.fc19.20120403gitb66dc1 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/mediatomb-0.12.1-28.fc19.20120403gitb66dc1

Comment 7 Fedora Update System 2013-05-24 20:47:42 UTC

mediatomb-0.12.1-28.fc19.20120403gitb66dc1 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 8 Fedora Update System 2013-05-25 11:59:26 UTC

mediatomb-0.12.1-28.fc18.20120403gitb66dc1 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 9 Fedora Update System 2013-05-25 12:08:05 UTC

mediatomb-0.12.1-28.fc17.20120403gitb66dc1 has been pushed to the Fedora 17 stable repository.  If problems still persist, please make note of it in this bug report.