Description of problem:
Please rebuild arj for EPEL 4 and 5
Version-Release number of selected component (if applicable):
No arj in EPEL 4 and 5
Package arj in EPEL 4 and 5, because it's an amavisd-new dependency.
Please let me know, when you're not interested in maintaining the package
Mockbuild in EPEL 5 succeded for me and looks fine, too:
I don't have any EPEL machines / installs and thus do not feel capable of
maintaining packages in EPEL (atleast not by myself). Here is my usual solution
You own arj in EPEL, with me as co-maintainer and you become a co-maintainer in
Fedora. That way we will always both know whats going on on the other side of
the "fence" and see each others bug reports. I will be more then willing to help
with any EPEL issues as the arise, but I do not feel comfortable maintaining it
If you agree, please create a CVS admin request in bugzilla requesting the
I don't mind co-maintaining the EPEL branches, since it is a dependency of my
I also could co-maintain the package. Steven: You or me?
(In reply to comment #3)
> I also could co-maintain the package. Steven: You or me?
How about we say "all of the above" and really give the co-maintainer thing a try?
Package Change Request
Package Name: arj
New Branches: EL-4 EL-5
Updated Fedora Owners: firstname.lastname@example.org,robert
Updated EPEL Owners: robert,email@example.com
In reply to comment #4: Did you wish to be listed as a co-maintainer as well
Steven? If so, add another request and reset the flag.
Robert, you're now the proud owner of this bug, close it when arj is build for
EPEL-4 and 5
I'm already working on this, but the buildsys.fedoraproject.org builders
currently have a problem; already contacted Mike McGrath...
No problem, I just wanted to get this of my list of open bugs, hence the reassign.
Build on target fedora-5-epel succeeded.
Build on target fedora-4-epel succeeded.