Description of problem: The spec file of mythtv-mythweb has missing dependencies php-pcre php-posix php-json apache-mod_env apache-mod_rewrite and finally php-mythtv It took me hours to work out I needed php-mythtv All the others were listed in the INSTALL file and most of them got installed along with phpmyadmin. The second issue with the spec file is /etc/httpd/conf/webapps.d/mythweb.conf I think the intent of the spec file is to prepend the standard mythweb.conf.apache file with the stanza <Directory /var/www/mythweb> Order allow,deny Deny from all </Directory> Instead it replaces the mythweb.conf file. Steps to Reproduce: 1. mythweb is inoperable until required dependencies have been located and mythweb.conf replaced.
Keywords: (none) => Junior_jobAssignee: bugsquad => mageia
Thanks for the report. I've now fixes this problem. In terms of the deps, there is no need to specify php-pcre or php-posix as they are both required by apache-mod_php, php-json is already required by php-mythtv, and (finally) the two apache modules mentioned are provided by the default apache install so again, no need to specify them explicitly. With regards to php-mythtv, it requires php-mysql, so I just replaced the old require on php-mysql in mythweb package with a require on php-mythtv so everything should be good. I've fixed up the config properly now for the mythweb. Please try the latest packages that will be coming to updates_testing soon. I'm also still trying to debug #5716 so an official update will contain both fixes.
Thanks for that Colin. Confirmed dependencies for mythtv-mythweb-0.25-20120602.0.2.mga2 are OK now. Tested with a clean install. With respect to mythweb.conf there is one small (nit picking) comment. The mageia customisations appear at the bottom of the file below the line saying "You really shouldn't have to edit anything below this line so please don't unless you know what you are doing"
Oh yeah :) Well I would personally prefer to make changes in a new file in vhosts.d anyway (tho' it may not specifically refer to a vhost per-se!), but I just prefer using my own files rather than package ones for such circumstances! I think the mga bits will work fine if they were at the top tho', so I'll try and remember to shuffle it around :)
Please look at the bottom of this mail to see whether you're the assignee of this bug, if you don't already know whether you are. If you're the assignee: We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead. If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard. Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why. Thanks :) **************************** @ the reporter and persons in the cc of this bug: If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us. @ the reporter of this bug If you didn't reply yet to a request for more information, please do so within two weeks from now. Thanks all :-D
This message is a reminder that Mageia 2 is nearing its end of life. Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'. 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 Mageia version prior to Mageia 2's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 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 Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. 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 Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- The Mageia Bugsquad
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 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 Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => OLD