Description of problem: Please move this into the EPEL repo Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Correction. Please **ADD** this to the EPEL repository. Thanks
I guess this request should be done in Package review of netatalk - https://bugzilla.redhat.com/show_bug.cgi?id=226190 - as request for additional branch. Additionally - which EPEL ? I guess epel6 - as netatalk is in rhel-5 - but it is always better to specify all the information
Yes, EPEL 6, I believe. Its for CentOS 5. I was directed by Remi Collet to request this via this link: http://forums.famillecollet.com/viewtopic.php?pid=1199#p1199 On there he cited the availability of the package via this link: http://rpms.famillecollet.com/rpmphp/zoom.php?rpm=netatalk Any help is appreciated!
Rereading your post and the linked post, I'm a bit lost where you are directing me to request this or is this something you already took care of? Thanks!
If CentOS 5, then I'm a bit lost, because netatalk is afaik included in RHEL-5 trees (and you would need epel5 branch) ... For epel6, see http://fedoraproject.org/wiki/PackageMaintainers/CVSAdminProcedure#other ... and add scm request to the package review bugzilla I provided in comment#2 ...
Anyway - ask Jirka if he is ok with maintaining epel6 branch if you are going to fill the scm request.
(In reply to comment #5) > because netatalk is afaik included in RHEL-5 trees I don't find it in EPEL nor RHEL (5.6) repository. > and add scm request to the package review ... This should be done by the package owner
(In reply to comment #7) > (In reply to comment #5) > > because netatalk is afaik included in RHEL-5 trees > I don't find it in EPEL nor RHEL (5.6) repository. You are right - I can't see it in the rhel-5.6 repository as well - so it's not included in the release. It was probably removed from the final component list in alpha/beta phase before GA. Sorry for confusion. > > and add scm request to the package review ... > This should be done by the package owner Or by the one who will maintain the epel6 branch. It's not a rule that epel package has same owner as Fedora one.
(sorry, I meant epel5 branch ... of course - but maybe epel6 too)
Ondrej, I went to the link you said to make the request and when I clicked on the link: https://admin.fedoraproject.org/pkgdb/acls to do so, its broken. Do you have another way? I emailed the author listed on the package, Jiri Skala, but I've received no response. Any other suggestions?
Hi, I've just requested getting netatalk into EPEL 5 and 6. The details are available here: https://bugzilla.redhat.com/show_bug.cgi?id=226190#c15
netatalk-2.0.5-1.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/netatalk-2.0.5-1.el5
netatalk-2.1.5-1.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/netatalk-2.1.5-1.el6
Hi Steffan, as you can see I've used netatalk-2.0.5 for epel 5 because there would have to be compat-db47 package in epel 5 to cover netatalk's dependency. This currently is not feasible.
netatalk-2.1.5-1.el6 has been pushed to the Fedora EPEL 6 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update netatalk'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/netatalk-2.1.5-1.el6
netatalk-2.0.5-1.el5 has been pushed to the Fedora EPEL 5 stable repository. If problems still persist, please make note of it in this bug report.
netatalk-2.1.5-1.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.