Le 21/07/2016 à 11:09, Lucas Nussbaum a écrit :
> I can confirm that they all built fine. Thanks!
Excellent! Thank you for confirming.
Emmanuel Bourg
On 21/07/16 at 00:43 +0200, Emmanuel Bourg wrote:
> Le 20/07/2016 à 21:47, Lucas Nussbaum a écrit :
>
> > Once the issue is fixed in maven-repo-helper, those packages should be
> > build-tested again (I can do that if needed; please ping me).
>
> The 'mh_install -i' issue is fixed in maven-repo-h
Le 20/07/2016 à 21:47, Lucas Nussbaum a écrit :
> Once the issue is fixed in maven-repo-helper, those packages should be
> build-tested again (I can do that if needed; please ping me).
The 'mh_install -i' issue is fixed in maven-repo-helper 1.9.2.
Could you test again the packages previously aff
On 20/07/16 at 22:31 +0200, Emmanuel Bourg wrote:
> Le 20/07/2016 à 21:47, Lucas Nussbaum a écrit :
>
> > So, it would make sense to fix that bug on the maven-repo-helper side,
> > rather
> > than require changes to each of those packages individually.
>
> Thank you for investigating this Lucas.
Le 20/07/2016 à 21:47, Lucas Nussbaum a écrit :
> So, it would make sense to fix that bug on the maven-repo-helper side, rather
> than require changes to each of those packages individually.
Thank you for investigating this Lucas. Please do not start a mass bug
filing for these packages though, t
Hi,
I did some work to try to confirm/verify/extend the list of issues
already identified by Santiago Vila, and ran into this bug.
The full list of affected packages is:
android-platform-libcore
android-platform-tools-base
apache-pom
classycle
closure-compiler
commons-parent
cup
findbugs-bcel
ge
On 07/16/2016 03:35 PM, Santiago Vila wrote:
> On Sat, 16 Jul 2016, tony mancill wrote:
>
>> The first two packages I tried, src:pegdown and src:libjbcrypt-java,
>> both appear in the "successfully built reproducibly" set here [1], and
>> neither has any bugs assigned to it. Maybe I'm looking in
On Sat, 16 Jul 2016, tony mancill wrote:
> The first two packages I tried, src:pegdown and src:libjbcrypt-java,
> both appear in the "successfully built reproducibly" set here [1], and
> neither has any bugs assigned to it. Maybe I'm looking in the wrong place?
If those packages generate only "A
On 07/16/2016 01:58 PM, Santiago Vila wrote:
> On Sat, 16 Jul 2016, tony mancill wrote:
>
>>> https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=binary-indep;users=sanv...@debian.org
>>
>> Hi Santiago,
>>
>> Thanks for the list. For 806640, the only bug that appears in this list
>> related to mh_i
On Sat, 16 Jul 2016, tony mancill wrote:
> > https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=binary-indep;users=sanv...@debian.org
>
> Hi Santiago,
>
> Thanks for the list. For 806640, the only bug that appears in this list
> related to mh_install 805228, I will mark it as blocked by 805228,
On 07/16/2016 01:47 PM, tony mancill wrote:
> Thanks for the list. For 806640, the only bug that appears in this list
> related to mh_install 805228, I will mark it as blocked by 805228, but I
> won't reassign.
Grrr sorry for the typos. I meant 806630, and to say that I will
mark it blocked
On 07/16/2016 01:31 PM, Santiago Vila wrote:
> On Sat, 16 Jul 2016, Markus Koschany wrote:
>
>> On 16.07.2016 18:22, tony mancill wrote:
>> [...]
>>> I'd like to discuss options with the Java Team. For example, we could
>>> change mh_install to ignore '-i' when not passed in conjunction with a
>>
On Sat, 16 Jul 2016, Markus Koschany wrote:
> On 16.07.2016 18:22, tony mancill wrote:
> [...]
> > I'd like to discuss options with the Java Team. For example, we could
> > change mh_install to ignore '-i' when not passed in conjunction with a
> > maven.ignoreRules file, or change the DH sequence
On 16.07.2016 18:22, tony mancill wrote:
[...]
> I'd like to discuss options with the Java Team. For example, we could
> change mh_install to ignore '-i' when not passed in conjunction with a
> maven.ignoreRules file, or change the DH sequencer, and probably some
> other better options that I'm no
14 matches
Mail list logo
