https://bugzilla.redhat.com/show_bug.cgi?id=1247243 gil cattaneo <puntogil@xxxxxxxxx> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment|0 |1 #1195546 is| | obsolete| | --- Comment #41 from gil cattaneo <puntogil@xxxxxxxxx> --- (In reply to Michal Karm Babacek from comment #39) > No problem, I just thought it was supposed to be 1 because it is the first > build of mod_cluster 1.3.3. I used 4 (actually 5) as you suggested though. > > So far, I pushed to rawhide: > > * 1.3.3-4 > http://pkgs.fedoraproject.org/cgit/rpms/mod_cluster.git/commit/ > ?id=6bf9d20ffd40b625762637ffeb43a1570f3a7785 > * 1.3.3-5 > http://pkgs.fedoraproject.org/cgit/rpms/mod_cluster.git/commit/ > ?id=0e223e9831a01f92de47be11d8a652bbe87f6e07 > * http://koji.fedoraproject.org/koji/taskinfo?taskID=15431508 > > and I tested upgrade from 1.2.6 on f24. Wildfly would need additional > testing as soon as it's updated, because I used Wildfly from zip and just > replaced mod_cluster libs so as to make sure mod_cluster rpm provides all > necessary classes. > > Any reason not to carry on with f25 and f24? There is none from the > mod_cluster project view, nobody could use mod_cluster in Fedora these days > in any production env because it actually doesn't work (numerous bugs, > performance issues, CVEs...). Unfortunately, for Wildfly (10.1.0), import in the other branches, different from the master, is not possible ... Some dependencies if you update would create a lot of compatibility problems ... not to mention the jackson libraries (2.7.x) ... If you want update mod_cluster in other branches for me is ok if this not cause compatibility problems -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://lists.fedoraproject.org/admin/lists/package-review@xxxxxxxxxxxxxxxxxxxxxxx