Red Hat Bugzilla – Bug 425825
moodle: broken deps
Last modified: 2008-01-22 08:27:13 EST
Description of problem: package: moodle - 1.8.2-1.el5.noarch from epel5-testing unresolved deps: perl(Text::Aspell) mimetex Additional info: I'd like to see the above problems solved. Jerry, would you be willing to take care of perl(Text::Aspell) in EPEL5? Jorge, would you be willing to take care of mimetex in EPEL5?
I've never contributed to EPEL before, so I don't really know what's involved. As long as I can do mock builds for EPEL on my Fedora 8 machine, it should be fine. I'll give it a try, but possibly not until I start my Christmas holiday in a week. I'll try to do it sooner, but I'm not going to promise. The Summary line on this bug needs a typo fix: moddle -> moodle.
(In reply to comment #1) > I've never contributed to EPEL before, so I don't really know what's involved. See http://fedoraproject.org/wiki/EPEL/ > As long as I can do mock builds for EPEL on my Fedora 8 machine, it should be > fine. Should work. > I'll give it a try, but possibly not until I start my Christmas holiday > in a week. I'll try to do it sooner, but I'm not going to promise. thx > The Summary line on this bug needs a typo fix: moddle -> moodle. you (afaik) could have done that yourself ;-)
May I ask how a mock build of a PHP app would be helpful? PHP app requires checking is a painstaking process involving the manual checking of the spec against the repo, a process that can take some time and has for me on other packages, and is a process that I have obviously failed to do properly for Moodle. :)
(In reply to comment #3) > May I ask how a mock build of a PHP app would be helpful? Please use the mailing list https://www.redhat.com/mailman/listinfo/epel-devel-list I can't answer this, sorry.
Sorry, forgot to include the <rhetorical> tag. :)
(In reply to comment #5) > Sorry, forgot to include the <rhetorical> tag. :) And I maybe should have looked closer/read the comment properly ;)
Jerry, all you really would need to do is request a branch for EL-5, then build. Honestly, EPEL contribtion is very easy. I've yet to catch any bug from EPEL until this one, simply because most get found and fixed in Fedora, or usually rawhide. You don't even have to worry about updates, with the exception of security. If you'd rather not, I'll be happy to co-maintain for EPEL purposes, just request the branch and let me take ownership. That goes for Jorge as well.
I have verified that perl-Text-Aspell builds in mock, and have requested a CVS branch for it. Stand by for a build.
Okay, it's built. Have fun!
(In reply to comment #9) > Okay, it's built. Have fun! thx Jerry. Jorge, any plans for mimetex in EPEL?
Note that there is still a broken dep on mimetex: package: moodle - 1.8.2-1.el5.noarch from epel-testing unresolved deps: mimetex
No response here from Jorge. How would I go about branching mimetext for EPEL, cvsadmin request?
(In reply to comment #12) > No response here from Jorge. How would I go about branching mimetext for EPEL, > cvsadmin request? http://fedoraproject.org/wiki/EPEL/GuidelinesAndPolicies Section "EPEL branching if Fedora maintainer does not react"
Requested branches and EPEL maintainership. https://bugzilla.redhat.com/show_bug.cgi?id=170225
Granted, built mimetex for EL-5 and EL-4.