Bug#745815: libjarjar-java: generate jars with invalid information

2014-06-07 Thread Miguel Landaeta
On Sun, May 25, 2014 at 01:11:39PM +0200, Damien Raude-Morvan wrote: Hi Miguel, hi Emmanuel ! Sorry to come back to you so late... Hi Damien, No problem. I'm also very slow with my email lately. I've cherry-picked this patch after having issues with some maven plugins but you're right it

Bug#745815: libjarjar-java: generate jars with invalid information

2014-05-25 Thread Damien Raude-Morvan
Hi Miguel, hi Emmanuel ! Sorry to come back to you so late... 2014-05-03 19:50 GMT+02:00 Miguel Landaeta nomad...@debian.org: On Sat, May 03, 2014 at 07:30:20PM +0200, Emmanuel Bourg wrote: Le 03/05/2014 18:41, Miguel Landaeta a écrit : Well, the bug was not introduced by upstream as I

Bug#745815: libjarjar-java: generate jars with invalid information

2014-05-07 Thread Miguel Landaeta
On Sat, May 03, 2014 at 02:50:29PM -0300, Miguel Landaeta wrote: Any opinion about disabling this? I'm uploading a new release of jarjar disabling the problematic patch. I rebuilt all its reverse dependencies and everything builds without issues. If that patch is really needed please file a

Bug#745815: libjarjar-java: generate jars with invalid information

2014-05-03 Thread Miguel Landaeta
On Fri, May 02, 2014 at 06:35:25PM -0300, Miguel Landaeta wrote: So, I guess to fix this I'll have to check all the commits since jarjar 1.1 to determine which is the breaking change. Well, the bug was not introduced by upstream as I thought. I can only reproduce this bug when patch

Bug#745815: libjarjar-java: generate jars with invalid information

2014-05-03 Thread Emmanuel Bourg
Le 03/05/2014 18:41, Miguel Landaeta a écrit : Well, the bug was not introduced by upstream as I thought. I can only reproduce this bug when patch szzepiq_jar_resources.diff is applied. When I remove that patch, jarjar works OK for me. Interesting, the question is to know what issue this

Bug#745815: libjarjar-java: generate jars with invalid information

2014-05-03 Thread Miguel Landaeta
On Sat, May 03, 2014 at 07:30:20PM +0200, Emmanuel Bourg wrote: Le 03/05/2014 18:41, Miguel Landaeta a écrit : Well, the bug was not introduced by upstream as I thought. I can only reproduce this bug when patch szzepiq_jar_resources.diff is applied. When I remove that patch, jarjar

Bug#745815: libjarjar-java: generate jars with invalid information

2014-05-02 Thread Miguel Landaeta
owner 745815 ! thanks miguel@nina:~/packages/groovy/bug/groovy-1.8.6$ dpkg-query -l groovy | grep ^ii ii groovy 1.8.6-3~miguel1 all Agile dynamic language for the Java Virtual Machine miguel@nina:~/packages/groovy/bug/groovy-1.8.6$ dpkg-query -l libjarjar-java | grep ^ii ii

Processed: Re: Bug#745815: libjarjar-java: generate jars with invalid information

2014-05-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: owner 745815 ! Bug #745815 [libjarjar-java] libjarjar-java: generate jars with invalid information Owner recorded as Miguel Landaeta nomad...@debian.org. thanks Stopping processing here. Please contact me if you need assistance. -- 745815:

Bug#745815: libjarjar-java: generate jars with invalid information

2014-04-25 Thread Miguel Landaeta
Package: libjarjar-java Version: 1.4+svn142-1 Severity: important groovy package generates two jar files during build time and one of them (groovy-all.jar) is manipulated with libjarjar-java during its creation. This worked OK until 1.1-3 but stopped working on 1.4+svn142-1 with the inclusion of

Bug#745815: libjarjar-java: generate jars with invalid information

2014-04-25 Thread Emmanuel Bourg
I compared the dgminfo files from groovy-all.jar in stable and unstable, in unstable the 0x0D bytes have been replaced by 0x0A. It looks like the file was erroneously processed as a text file and the line terminators were transformed. I fail to see what change in jarjar 1.4 caused this though.

Bug#745815: libjarjar-java: generate jars with invalid information

2014-04-25 Thread Miguel Landaeta
On Fri, Apr 25, 2014 at 04:10:25PM +0200, Emmanuel Bourg wrote: I compared the dgminfo files from groovy-all.jar in stable and unstable, in unstable the 0x0D bytes have been replaced by 0x0A. It looks like the file was erroneously processed as a text file and the line terminators were