Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.java > #10470 > unrolled thread

After move to Salsa: Tried to upgrade some packages I feel responsible

Back to article view | Back to linux.debian.maint.java

Contents

  After move to Salsa: Tried to upgrade some packages I feel  responsible Andreas Tille <andreas@an3as.eu> - 2018-05-03 09:40 +0200
    Re: After move to Salsa: Tried to upgrade some packages I feel  responsible Emmanuel Bourg <ebourg@apache.org> - 2018-05-03 15:00 +0200
    Re: After move to Salsa: Tried to upgrade some packages I feel responsible Vincent Privat <vincent.privat@gmail.com> - 2018-05-04 01:30 +0200
      Re: After move to Salsa: Tried to upgrade some packages I feel  responsible Andreas Tille <andreas@an3as.eu> - 2018-05-07 16:20 +0200
        Re: After move to Salsa: Tried to upgrade some packages I feel  responsible Markus Koschany <apo@debian.org> - 2018-05-07 16:40 +0200

#10470 — After move to Salsa: Tried to upgrade some packages I feel responsible

Hi,

I considered the move to Salsa a good reason to have a look into some
packages I maintain (or rather do not really maintain but where I'm
mentioned in the Uploaders field - sorry for my weak job here) in the
Debian Java team.  The following packages went smoothly:

    snappy-java
    tcode

I upgraded the following packages in Git to the latest upstream version
but these were running into build issues where I have no idea how to
fix:

    libejml-java
      Could not determine java version from '9.0.4'.

    libexternalsortinginjava-java
      [ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar (default-cli) on project externalsortinginjava: Execution default-cli of goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar failed.: NullPointerException -> [Help 1]

    libjsonp-java
      Strange error in clean target - I've droped a note in d/changelog


I'm personally fine with the current versions in Debian and just want
to tell that I tried but have no sufficient time cycles to continue
with these packages.  May be some kind soul who is interested might
like to pick up from here.

Some other packages are left.  I'll pick them up once bug #897401 which
makes upgrading Java packages more fun. :-)

Kind regards

      Andreas.


-- 
http://fam-tille.de

[toc] | [next] | [standalone]

#10471

Hi Andreas,

Le 03/05/2018 à 09:32, Andreas Tille a écrit :

> I considered the move to Salsa a good reason to have a look into some
> packages I maintain in the Debian Java team.

Thank you!


> I upgraded the following packages in Git to the latest upstream version
> but these were running into build issues where I have no idea how to
> fix:
> 
>     libejml-java
>       Could not determine java version from '9.0.4'.

It looks like a Java version parsing not supporting the new versioning
scheme.


>     libexternalsortinginjava-java
>       [ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar (default-cli) on project externalsortinginjava: Execution default-cli of goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar failed.: NullPointerException -> [Help 1]

This one is a Java 10 regression affecting all Maven based packages
building a javadoc. libcommons-lang3-java needs an update, I'm working
on it.


> Some other packages are left.  I'll pick them up once bug #897401 which
> makes upgrading Java packages more fun. :-)

Thank you for filing 897401, I'm not sure to understand the impact
though :) What tools are affected by this?

Emmanuel Bourg

[toc] | [prev] | [next] | [standalone]

#10477 — Re: After move to Salsa: Tried to upgrade some packages I feel responsible

[Multipart message — attachments visible in raw view] — view raw

2018-05-03 9:32 GMT+02:00 Andreas Tille <andreas@an3as.eu>:

>
>     libejml-java
>       Could not determine java version from '9.0.4'.
>

I think this is because you call "gradle" instead of "./gradlew".
Current version of gradle debian package is 3.4.1. The minimal version
compatible with Java 9 is 4.2.1, see
https://discuss.gradle.org/t/could-not-determine-java-version-from-9-0-1/24457

I can build libejml by calling ./gradlew (gradle 4.3 is being downloaded).
Cheers,
Vincent

[toc] | [prev] | [next] | [standalone]

#10486

Hi Vincent,

On Fri, May 04, 2018 at 01:25:48AM +0200, Vincent Privat wrote:
> >     libejml-java
> >       Could not determine java version from '9.0.4'.
> 
> I think this is because you call "gradle" instead of "./gradlew".

Thanks for the hint and feel free to push your changes to Git.  I hope
I implemented your suggestion correctly[1].

> Current version of gradle debian package is 3.4.1. The minimal version
> compatible with Java 9 is 4.2.1, see
> https://discuss.gradle.org/t/could-not-determine-java-version-from-9-0-1/24457
> 
> I can build libejml by calling ./gradlew (gradle 4.3 is being downloaded).

Wait a moment - its really downloading something?  I have no idea why
this works in a pbuilder chroot and whether this should be uploaded.
Should pbuilder not work on a disconnected system?  IMHO this means that
we need to upgrade gradle first, right?

Kind regards

       Andreas.

PS: Everybody who feels obligated to fix and upload this package is
perfectly welcome.  I'm just in Uploaders since this was used as a
predepency and I'm not keen on sitting with my obviously poor knowledge
on the package for ever.

[1] https://salsa.debian.org/java-team/libejml-java/commit/e05463e8d8e3ec4b995bed9dd1d72465917b5b3d

-- 
http://fam-tille.de

[toc] | [prev] | [next] | [standalone]

#10487

[Multipart message — attachments visible in raw view] — view raw

Hi,

Am 07.05.2018 um 16:13 schrieb Andreas Tille:
[...]
>> I can build libejml by calling ./gradlew (gradle 4.3 is being downloaded).
> 
> Wait a moment - its really downloading something?  I have no idea why
> this works in a pbuilder chroot and whether this should be uploaded.
> Should pbuilder not work on a disconnected system?  IMHO this means that
> we need to upgrade gradle first, right?

You are not allowed to call gradlew in Debian because it will download
binary files without source from the internet at build time. This can
only be resolved by updating the Gradle package in Debian.

Regards,

Markus

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.maint.java

csiph-web