Bug 863442
| Summary: | F10 support is useless / broken | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | barsnick |
| Component: | mediatomb | Assignee: | Gwyn Ciesla <gwync> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 19 | CC: | gwync |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-02-17 14:29:08 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: | |||
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19 This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 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 Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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 Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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 Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |
Description of problem: Building of mediatomb for F10 is supported in its SPEC file. But as far as I can tell, it is broken, and should either be fixed or removed. Version-Release number of selected component (if applicable): 0.12.1-17 How reproducible: Always on F10 Steps to Reproduce: 1. rpmbuild --rebuild mediatomb-0.12.1-17.fc18.src.rpm Actual results: - syntax error in SPEC: "error: syntax error while parsing == error: /usr/src/redhat/SPECS/mediatomb.spec:88: parseExpressionBoolean returns -1" Fixed by replacing %if 0%{?fedora} = 10 with %if 0%{?fedora} == 10 - compile error: ../src/scripting/import_script.cc: In constructor 'ImportScript::ImportScript(zmm::Ref<Runtime>)': ../src/scripting/import_script.cc:57: error: 'JS_AddNamedObjectRoot' was not declared in this scope ../src/scripting/import_script.cc: In destructor 'virtual ImportScript::~ImportScript()': ../src/scripting/import_script.cc:120: error: 'JS_RemoveObjectRoot' was not declared in this scope These are introduced by the patches mediatomb-0.12.1.tonewjs.patch and mediatomb-0.12.1-jsparse.patch which make use of symbols not available in F10's js (xulrunner-devel-1.9.0.15-1.fc10.i386), so they need to be conditionalized. Something like %if 0%{?fedora} >= 11 %patch3 -p1 %patch4 -p1 %endif - "RPM build errors: File must begin with "/": %{_unitdir}/mediatomb.service" This is due to illegal use of %{_unitdir}. a) F10 does not support systemd, you would have to bring back the old /etc/rc.d/init.d mechanisms (conditionalized). b) This is a generic bug, not restricted to F10. See http://fedoraproject.org/wiki/Packaging:Systemd#Filesystem_locations "Please note that in order for the %{_unitdir} macro to exist, your package must have: BuildRequires: systemd-units" Expected results: Builds and runs fine. Additional info: Yes, I still have an F10 system around. Flame me! ;-) Or drop the obsolete alleged support for older Fedoras. And fix the "BuildRequires: systemd-units" bug please. (I can file that separately.)