OK, a few news from me on this topic. I made following:
1. Prepared a netty4 compat package for F20 *only*,
2. Prepared a netty package upgrade from version 3 to 4 for Rawhide,
3. Prepared a netty3 compat package for Rawhide.
These packages are available here:
It would be great to not introduce netty3 package into Rawhide. We
should do everything to not require it :)
I would need a bit of help from you:
1. Please make sure these packages are OK (I still need to to add the
Obsoletes and so on) The .src.rpm files are there too.
2. Please test your packages against these (new netty from Rawhide)
I would like to proceed with the upgrade ASAP, since wildfly 8.0.0.CR1
was already released and its dependencies require upgrade to netty 4.
On 16.12.2013 14:53, Marek Goldmann wrote:
> Any progress on this?
> It seems that I'll need the netty 4 package very soon for hornetq and
> wildfly updates.
> On 06.11.2013 10:38, Marek Goldmann wrote:
>> I think this is the route I would like to go. I'm happy to create a
>> netty4 compat package based on what Jon creates for netty package in
>> On 05.11.2013 15:49, Stanislav Ochotnicky wrote:
>>> Quoting Marek Goldmann (2013-11-05 12:36:33)
>>>> OK, I have new info on this.
>>>> Netty is actually pulled by HornetQ, WildFly JMS implementation. There
>>>> is an open bug upstream to upgrade to Netty 4:
>>>> The fix version is the next release (2.4.0.CR1) and this version
>>>> will be
>>>> used by next pre-release (and later Final of course) of WildFly. As
>>>> can imagine I want to package it for Fedora 20 and Rawhide. I don't
>>>> to leave Beta1 in Fedora 20.
>>>> So, here is the thing:
>>>> This would require upgrading netty in Fedora 20 too, because if we
>>>> do it - WildFly will not be able to get any new updates to Fedora 20
>>>> which is a tragedy for me :)
>>>> Is it doable, any ideas?
>>> There's an idea (even if an ugly one) to package netty4 in F20 only
>>> netty package there on 3.x). In F21+ we'd migrate all other packages
>>> to netty
>>> 4.x, update netty package to 4.x and make it obsolete netty4 from F20.
>>> With XMvn there would be no (or minor) changes needed to packages that
>>> like to build against 4.x (and those changes would likely work in
>>> rawhide as
>>> well). Most like all you'd have to do is ifdef for (build)requires.
>> java-devel mailing list
> java-devel mailing list
java-devel mailing list