Mule Orphaned Package

Hi All,

I'm a mule developer and fedora user.  Recently, I noticed that the version
of mule packaged with fedora is not only very behind the current upstream
version but it is also orphaned.  I'd like to take over maintaining the
packaging of mule on fedora if there are no objections.

Thanks,

Tim

[Richard W.M. Jones]

On Sun, Jun 29, 2014 at 10:59:22AM -0400, tspauld98(a)yahoo.com wrote:
>  Hi All,
>  
>  I'm a mule developer and fedora user.  Recently, I noticed that the version
>  of mule packaged with fedora is not only very behind the current upstream
>  version but it is also orphaned.  I'd like to take over maintaining the
>  packaging of mule on fedora if there are no objections. 
https://admin.fedoraproject.org/pkgdb/package/mule/

It looks like the package is currently orphaned, so you can take it
over without asking anyone, once you become a packager.  To become a
packager you need to look at these pages:

https://fedoraproject.org/wiki/Join_the_package_collection_maintainers
https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group

Best of luck,

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-builder quickly builds VMs from scratch
http://libguestfs.org/virt-builder.1.html

[Andy Grimm]

On Sun, Jun 29, 2014 at 10:59 AM, tspauld98(a)yahoo.com
<tspauld98(a)gmail.com&gt; wrote:
>  Hi All,
>
>  I'm a mule developer and fedora user.  Recently, I noticed that the version
>  of mule packaged with fedora is not only very behind the current upstream
>  version but it is also orphaned.  I'd like to take over maintaining the
>  packaging of mule on fedora if there are no objections. 
This was originally my package; it was packaged as part of the effort
to get Eucalyptus into Fedora a few releases ago, and at the time I
packaged something close to what upstream Eucalyptus code bundled as a
dependency.  Thankfully, Eucalyptus updated most of their dependencies
in 4.0, so there should be nothing depending on the old version now.

Andy

>  Thanks,
>
>  Tim
>
>  --
>  devel mailing list
>  devel(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/devel
>  Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

[Christopher Meng]

How many patches needed for the latest mule?

Are these[1] merged already?

[1]---http://pkgs.fedoraproject.org/cgit/mule.git/tree/

[Andy Grimm]

On Mon, Jun 30, 2014 at 1:54 AM, Christopher Meng <cickumqt(a)gmail.com&gt; wrote:
>  How many patches needed for the latest mule?
>
>  Are these[1] merged already? 
I'm not sure how many of those will be needed.  Several of them were
for building the old version of mule against newer dependencies (like
spring 3.1), and newer versions of mule already support the newer
deps.  Other patches (like the one to disable spring-jms) were because
certain deps were missing from Fedora, and can be removed if the dep
is now present in the distro.

Andy


>  [1]---http://pkgs.fedoraproject.org/cgit/mule.git/tree/
>  --
>  devel mailing list
>  devel(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/devel
>  Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct