From mgoldman at redhat.com  Thu May 26 09:48:58 2016
From: mgoldman at redhat.com (Marek Goldmann)
Date: Thu, 26 May 2016 15:48:58 +0200
Subject: [jboss-rpm] RPM EPEL COPR
In-Reply-To: <HE1PR06MB1387F14471B11E74889AE3D19B410@HE1PR06MB1387.eurprd06.prod.outlook.com>
References: <HE1PR06MB1387F14471B11E74889AE3D19B410@HE1PR06MB1387.eurprd06.prod.outlook.com>
Message-ID: <CAK+Nnm+p-2PAJH26yMRMwjEBw52E97JDi3_eRGdNSmaLcE8tZQ@mail.gmail.com>

Hey Ben,

The reason is fairly simple: it's too much work to make it happen. But
that's not everything - someone needs to maintain it afterwards.

We're talking here about adding about 150 new packages to EPEL. Even
in Fedora there is no latest WildFly release because of this problem.
With each upstream release there is a need to update about 50
packages, fix all incompatibility issues and so on. This is a full
time job for at least one person. Only Gil (CCed) is working on
updating packages in Fedora to ship newest WildFly in his spare time.
There is interest to make it happen, but we need actions and people
doing the actual job. I'm not able to lead it anymore.

--Marek


On Thu, May 26, 2016 at 3:37 PM, Benjamin Lefoul
<benjamin.lefoul at nwise.se> wrote:
> Hello Marek,
>
> I have tried contacting you before about wildfly in EPEL and COPR. I am also CC:ing to this apparently abandoned list, but you never know.
> I am really having a hard time finding information about what stand in the way of a wildfly package entering EPEL and upgrading to 10.
> Is it simply that this is overwhelmed for you, as the main packager, and if so would you need help? Or is this a decision from further up in the Fedora project?
>
> Regards,
>
> Benjamin Lefoul

From benjamin.lefoul at nwise.se  Thu May 26 10:14:16 2016
From: benjamin.lefoul at nwise.se (Benjamin Lefoul)
Date: Thu, 26 May 2016 14:14:16 +0000
Subject: [jboss-rpm] RPM EPEL COPR
In-Reply-To: <b25172a4-7fc0-07f7-3004-0ed0bfe96c39@libero.it>
References: <HE1PR06MB1387F14471B11E74889AE3D19B410@HE1PR06MB1387.eurprd06.prod.outlook.com>
	<CAK+Nnm+p-2PAJH26yMRMwjEBw52E97JDi3_eRGdNSmaLcE8tZQ@mail.gmail.com>,
	<b25172a4-7fc0-07f7-3004-0ed0bfe96c39@libero.it>
Message-ID: <HE1PR06MB1387CA358F46EC8C2E910A819B410@HE1PR06MB1387.eurprd06.prod.outlook.com>

Thanks very much for your time. /Benjamin

________________________________________
From: gil <puntogil at libero.it>
Sent: 26 May 2016 16:09
To: Marek Goldmann; Benjamin Lefoul
Cc: jboss-rpm at lists.jboss.org
Subject: Re: RPM EPEL COPR

Hi

for now the status is this:

at the moment are needed new 2 [1] packages for import wildfly-core [2]
(spec file is almost ready[3])

[1]
wildfly-build-tools https://bugzilla.redhat.com/show_bug.cgi?id=1328065
wildfly-elytron https://bugzilla.redhat.com/show_bug.cgi?id=1328064
see spec file for see the packages which should be updated.
exception for wildfly-common and metainf-services

[2] https://github.com/wildfly/wildfly-core
[3] compatibility problems with our log4j libraries (use both 1.2.X and 2.X)
  regards
.g

Il 26/05/2016 15:48, Marek Goldmann ha scritto:
> Hey Ben,
>
> The reason is fairly simple: it's too much work to make it happen. But
> that's not everything - someone needs to maintain it afterwards.
>
> We're talking here about adding about 150 new packages to EPEL. Even
> in Fedora there is no latest WildFly release because of this problem.
> With each upstream release there is a need to update about 50
> packages, fix all incompatibility issues and so on. This is a full
> time job for at least one person. Only Gil (CCed) is working on
> updating packages in Fedora to ship newest WildFly in his spare time.
> There is interest to make it happen, but we need actions and people
> doing the actual job. I'm not able to lead it anymore.
>
> --Marek
>
>
> On Thu, May 26, 2016 at 3:37 PM, Benjamin Lefoul
> <benjamin.lefoul at nwise.se> wrote:
>> Hello Marek,
>>
>> I have tried contacting you before about wildfly in EPEL and COPR. I am also CC:ing to this apparently abandoned list, but you never know.
>> I am really having a hard time finding information about what stand in the way of a wildfly package entering EPEL and upgrading to 10.
>> Is it simply that this is overwhelmed for you, as the main packager, and if so would you need help? Or is this a decision from further up in the Fedora project?
>>
>> Regards,
>>
>> Benjamin Lefoul



From karm at redhat.com  Mon May 30 10:17:08 2016
From: karm at redhat.com (Michal Karm Babacek)
Date: Mon, 30 May 2016 10:17:08 -0400 (EDT)
Subject: [jboss-rpm] RPM EPEL COPR   /pitching in/
In-Reply-To: <HE1PR06MB1387CA358F46EC8C2E910A819B410@HE1PR06MB1387.eurprd06.prod.outlook.com>
References: <HE1PR06MB1387F14471B11E74889AE3D19B410@HE1PR06MB1387.eurprd06.prod.outlook.com>
	<CAK+Nnm+p-2PAJH26yMRMwjEBw52E97JDi3_eRGdNSmaLcE8tZQ@mail.gmail.com>
	<b25172a4-7fc0-07f7-3004-0ed0bfe96c39@libero.it>
	<HE1PR06MB1387CA358F46EC8C2E910A819B410@HE1PR06MB1387.eurprd06.prod.outlook.com>
Message-ID: <1612079098.52977.1464617828981.JavaMail.zimbra@redhat.com>

If there is any new JBoss RPM movement arising from the ashes
in Fedora, I could resurrect the late initiative on updating
mod_cluster https://bugzilla.redhat.com/show_bug.cgi?id=1247243

Sincerely yours
mod_cluster upstream

----- Original Message -----
> From: "Benjamin Lefoul" <benjamin.lefoul at nwise.se>
> To: "gil" <puntogil at libero.it>, "Marek Goldmann" <mgoldman at redhat.com>
> Cc: jboss-rpm at lists.jboss.org
> Sent: Thursday, May 26, 2016 4:14:16 PM
> Subject: Re: [jboss-rpm] RPM EPEL COPR
> 
> Thanks very much for your time. /Benjamin
> 
> ________________________________________
> From: gil <puntogil at libero.it>
> Sent: 26 May 2016 16:09
> To: Marek Goldmann; Benjamin Lefoul
> Cc: jboss-rpm at lists.jboss.org
> Subject: Re: RPM EPEL COPR
> 
> Hi
> 
> for now the status is this:
> 
> at the moment are needed new 2 [1] packages for import wildfly-core [2]
> (spec file is almost ready[3])
> 
> [1]
> wildfly-build-tools https://bugzilla.redhat.com/show_bug.cgi?id=1328065
> wildfly-elytron https://bugzilla.redhat.com/show_bug.cgi?id=1328064
> see spec file for see the packages which should be updated.
> exception for wildfly-common and metainf-services
> 
> [2] https://github.com/wildfly/wildfly-core
> [3] compatibility problems with our log4j libraries (use both 1.2.X and 2.X)
>   regards
> .g
> 
> Il 26/05/2016 15:48, Marek Goldmann ha scritto:
> > Hey Ben,
> >
> > The reason is fairly simple: it's too much work to make it happen. But
> > that's not everything - someone needs to maintain it afterwards.
> >
> > We're talking here about adding about 150 new packages to EPEL. Even
> > in Fedora there is no latest WildFly release because of this problem.
> > With each upstream release there is a need to update about 50
> > packages, fix all incompatibility issues and so on. This is a full
> > time job for at least one person. Only Gil (CCed) is working on
> > updating packages in Fedora to ship newest WildFly in his spare time.
> > There is interest to make it happen, but we need actions and people
> > doing the actual job. I'm not able to lead it anymore.
> >
> > --Marek
> >
> >
> > On Thu, May 26, 2016 at 3:37 PM, Benjamin Lefoul
> > <benjamin.lefoul at nwise.se> wrote:
> >> Hello Marek,
> >>
> >> I have tried contacting you before about wildfly in EPEL and COPR. I am
> >> also CC:ing to this apparently abandoned list, but you never know.
> >> I am really having a hard time finding information about what stand in the
> >> way of a wildfly package entering EPEL and upgrading to 10.
> >> Is it simply that this is overwhelmed for you, as the main packager, and
> >> if so would you need help? Or is this a decision from further up in the
> >> Fedora project?
> >>
> >> Regards,
> >>
> >> Benjamin Lefoul
> 
> 
> _______________________________________________
> jboss-rpm mailing list
> jboss-rpm at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-rpm
> 


-- 
Sent from my Hosaka Ono-Sendai Cyberspace 7

--
Michal Karm Babacek
    ? JBoss QE    
Red Hat Czech | GMT+2

? +420 737 778 560 (cell)
? +420 532 294 547 (?forwarded?)
freenode: #wildfly #mod_cluster #fedora-devel
? http://modcluster.io ? karm at redhat.com