Re: [jboss-rpm] RPM EPEL COPR
by Benjamin Lefoul
Thanks very much for your time. /Benjamin
________________________________________
From: gil <puntogil(a)libero.it>
Sent: 26 May 2016 16:09
To: Marek Goldmann; Benjamin Lefoul
Cc: jboss-rpm(a)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(a)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
8 years, 6 months
- 2
- 1
Re: [jboss-rpm] RPM EPEL COPR
by Marek Goldmann
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(a)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
8 years, 7 months
- 1
- 0
- ← Newer
- 1
- Older →