Path: csiph.com!goblin2!goblin.stu.neva.ru!aioe.org!bofh.it!news.nic.it!robomod From: =?UTF-8?Q?Sergio_Fern=C3=A1ndez?= Newsgroups: linux.debian.maint.java Subject: Re: libcommons-lang-java packaging? Date: Mon, 19 Oct 2015 17:00:02 +0200 Message-ID: References: X-Original-To: Commons Developers List X-Mailbox-Line: From debian-java-request@lists.debian.org Mon Oct 19 14:51:33 2015 Old-Return-Path: X-Amavis-Spam-Status: No, score=-7.93 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, FOURLA=0.1, HTML_MESSAGE=2, LDO_WHITELIST=-5, ONEWORDBODY=2, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -7 X-Gm-Message-State: ALoCoQknvqp4YnFTX+NCCgTFgC6O4htnLORrqlqT+uZMplc5w6+UHKp+uv4NMTpNerWmZfNB3/+o X-Received: by 10.112.171.69 with SMTP id as5mr14763890lbc.111.1445266269977; Mon, 19 Oct 2015 07:51:09 -0700 (PDT) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary=001a11c38b5ca0dc82052276467a X-Mailing-List: archive/latest/18806 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/CAOfJQJ2oA+JBOLjZVY4y5_Dwq-g26HTK1ARYhEB1MHwbtj944g@mail.gmail.com Approved: robomod@news.nic.it Lines: 123 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Cc: debian-java@lists.debian.org X-Original-Date: Mon, 19 Oct 2015 16:50:30 +0200 X-Original-Message-ID: X-Original-References: <5624FCC9.6080104@apache.org> Xref: csiph.com linux.debian.maint.java:8490 --001a11c38b5ca0dc82052276467a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Emmanuel, On Mon, Oct 19, 2015 at 4:23 PM, Emmanuel Bourg wrote: > Hi Sergio, > > Le 19/10/2015 15:37, Sergio Fern=C3=A1ndez a =C3=A9crit : > > > So, do you really need the build.xml for maintain > > the libcommons-lang-java.deb package? > > libcommons-lang-java contains the old 2.x version, the new 3.x version > is packaged in libcommons-lang3-java and already uses Maven. So removing > the Ant build for Commons Lang will not affect Debian (this isn't true > for all Commons components though). OK, perfect, I've created https://issues.apache.org/jira/browse/LANG-1175 for tracking that. > I've quite good experience with the jdeb plugin [2] for that, and > > I coould volunteer for the task; but I saw you use another helper metho= d > > [3]. What would be the preferable setup? > > Some help for the maintenance of the Apache Commons components (or the > other Apache Java projects) would be really welcome (we are ~10 active > developers maintaining 900 packages spanning the whole Java ecosystem). > If you are interested I can show you how updates are done and sponsor > your changes. Commit access and upload rights can also be granted to > those willing to publish directly the new releases to Debian/Ubuntu. > I can't promise that much time, but I'll do my best to help in the maintenance of packages for the Commons components and other Apache projects. Related, quite some time ago I opened a RFP for another project I'm actively involved https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D739957 So joining you, and if someone could sponsor my contributions, I could understand better how things work. So, tell me, how should we proceed next? Thanks! --=20 Sergio Fern=C3=A1ndez Partner Technology Manager Redlink GmbH m: +43 6602747925 e: sergio.fernandez@redlink.co w: http://redlink.co --001a11c38b5ca0dc82052276467a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi=C2=A0Emmanuel,

On Mon, Oct 19, 2015 at 4:23 PM, Emmanuel Bourg <ebourg@= apache.org> wrote:
Hi Sergio,

Le 19/10/2015 15:37, Sergio Fern=C3=A1ndez a =C3=A9crit :

> So, do you really need the build.xml for maintain
> the libcommons-lang-java.deb package?

libcommons-lang-java contains the old 2.x version, the new 3.x versi= on
is packaged in libcommons-lang3-java and already uses Maven. So removing the Ant build for Commons Lang will not affect Debian (this isn't true<= br> for all Commons components though).

OK, per= fect, I've created=C2=A0https://issues.apache.org/jira/browse/LANG-1175 for tracki= ng that.


> I've quite good experience with the jdeb plugin [2] for that, and<= br> > I coould volunteer for the task; but I saw you use another helper meth= od
> [3]. What would be the preferable setup?

Some help for the maintenance of the Apache Commons components (or t= he
other Apache Java projects) would be really welcome (we are ~10 active
developers maintaining 900 packages spanning the whole Java ecosystem).
If you are interested I can show you how updates are done and sponsor
your changes. Commit access and upload rights can also be granted to
those willing to publish directly the new releases to Debian/Ubuntu.

I can't promise that much time, but I'= ;ll do my best to help in the maintenance of packages for the Commons compo= nents and other Apache projects. Related, quite some time ago I opened a RF= P for another project I'm actively involved https://bugs.debian.org/cgi-bin= /bugreport.cgi?bug=3D739957 So joining you, and if someone could sponso= r my contributions, I could understand better how things work. So, tell me,= how should we proceed next?

Thanks!


--
Sergio Fern=C3= =A1ndez
Partner Technology Manager
Re= dlink GmbH
m: +43 6602747925
e:=C2=A0= sergio.fernandez@redlink.co
w:=C2=A0http://redlink.co
--001a11c38b5ca0dc82052276467a--