On Tue, Aug 25, 2015 at 11:52:47PM +0200, Markus Koschany wrote:
>
> I suggest to ask the release team for an exception and to provide the
> security fix via testing-proposed-updates. The CVE-fix appears to be
> straightforward and could be uploaded afterwards to stable-proposed-updates.
Thanks
On Wed, 29 Jul 2015 10:49:12 -0300 Miguel Landaeta nomad...@debian.org
wrote:
On Wed, Jul 29, 2015 at 10:00:16AM +0100, Russel Winder wrote:
Emmanuel, Miguel,
Hi Russel,
Apache Groovy 1.x series is no longer maintained. All effort is now on
the Apache Groovy 2.4.x and 2.5-SNAPSHOT
Emmanuel, Miguel,
On Wed, 2015-07-29 at 09:57 +0200, Emmanuel Bourg wrote:
Le 29/07/2015 03:35, Miguel Landaeta a écrit :
Since you have worked upstream with libcommons-cli-java, I hope to
don't bother you with this help request.
commons-cli provides several parsers with different
Le 29/07/2015 03:35, Miguel Landaeta a écrit :
Since you have worked upstream with libcommons-cli-java, I hope to
don't bother you with this help request.
commons-cli provides several parsers with different behaviors. Up to 1.2
there was a gnu and a posix parsers, and starting with 1.3 I
On 29/07/2015 8:24 PM, Paul King wrote:
On 29/07/2015 7:00 PM, Russel Winder wrote:
Emmanuel, Miguel,
[...snip...]
The 2.4.x stream is a mostly maintenance stream (i.e. bug fixes
and only minor functional changes/enhancements). At this stage,
there aren't any plans for doing a 2.4.x release
On 29/07/2015 7:00 PM, Russel Winder wrote:
Emmanuel, Miguel,
On Wed, 2015-07-29 at 09:57 +0200, Emmanuel Bourg wrote:
Le 29/07/2015 03:35, Miguel Landaeta a écrit :
Since you have worked upstream with libcommons-cli-java, I hope to
don't bother you with this help request.
commons-cli
On Wed, Jul 29, 2015 at 10:00:16AM +0100, Russel Winder wrote:
Emmanuel, Miguel,
Hi Russel,
Apache Groovy 1.x series is no longer maintained. All effort is now on
the Apache Groovy 2.4.x and 2.5-SNAPSHOT versions. If Debian is to
remove Commons CLI 1.2 then I suggest removing the groovy
On Wed, Jul 29, 2015 at 09:57:35AM +0200, Emmanuel Bourg wrote:
Le 29/07/2015 03:35, Miguel Landaeta a écrit :
Since you have worked upstream with libcommons-cli-java, I hope to
don't bother you with this help request.
commons-cli provides several parsers with different behaviors. Up to
tags 793630 + help
thanks
Hi Emmanuel, how are you?
I'm writing you due to #793630. It's an FTBFS that I strongly suspect
is caused by libcommons-cli-java 1.3. When I try to build groovy with
libcommons-cli 1.2-3 it builds OK but it fails with 1.3.1-2 due to
groovyc not recognizing a flag.
I
9 matches
Mail list logo
