Bug#775450: clojure1.6: clojure 1.6 doesn't work with gij/gcj 4.9 instead of openjdk

[Alex Vong]

Package: clojure1.6
Version: 1.6.0+dfsg-1
Followup-For: Bug #775450

Hi,

I have run into the same problem and I find the solution is to insert
the "-noverify" flag when invoking java. The following command works
for me:
  $ java -noverify -cp /usr/share/java/clojure-1.6.jar clojure.main

Should we patch the clojure wrapper script so that we automatically
add this flag when we detect we are using gij?

Cheers,
Alex


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.3.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=zh_TW.utf8, LC_CTYPE=zh_TW.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages clojure1.6 depends on:
ii  gcj-5-jre-headless [java2-runtime-headless]  5.3.1-8
ii  gcj-jre-headless [java2-runtime-headless]4:5.3.1-1
ii  libasm4-java 5.0.4-1
ii  libjsr166y-java  1.7.0-2

Versions of packages clojure1.6 recommends:
ii  rlwrap  0.41-1+b1

clojure1.6 suggests no packages.

-- no debconf information

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Bug#775450: clojure1.6: clojure 1.6 doesn't work with gij/gcj 4.9 instead of openjdk

[Emmanuel Bourg]

Clojure 1.6 requires Java 6 or higher, I don't think adding the
-noverify flag will fix all the compatibility issues with GCJ. We should
adjust the package dependencies instead.

Emmanuel Bourg

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Bug#775450: clojure1.6: clojure 1.6 doesn't work with gij/gcj 4.9 instead of openjdk

[Emmanuel Bourg]

Le 7/02/2016 17:21, Alex Vong a écrit :

> You are right, it is more of a workaround than an actual fix, in case
> we need to use gcj with clojure for some reason. By the way, may I ask
> why all clojure version has +dfsg suffice? My guess is that because
> the upstream tarball contains pre-built jar. Should we document it in
> `README.source'?

You're probably right about the removed jar files, but that's so common
for the Java packages that we don't bother documenting it.

Emmanuel Bourg

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Bug#775450: clojure1.6: clojure 1.6 doesn't work with gij/gcj 4.9 instead of openjdk

[Markus Koschany]

Am 07.02.2016 um 21:38 schrieb Emmanuel Bourg:
> Le 7/02/2016 17:21, Alex Vong a écrit :
> 
>> You are right, it is more of a workaround than an actual fix, in case
>> we need to use gcj with clojure for some reason. By the way, may I ask
>> why all clojure version has +dfsg suffice? My guess is that because
>> the upstream tarball contains pre-built jar. Should we document it in
>> `README.source'?
> 
> You're probably right about the removed jar files, but that's so common
> for the Java packages that we don't bother documenting it.

Usually every package should provide either a get-orig-source target or
a README.source file if you repack the tarball. It is in general a good
idea to create a simple get-orig-source target in debian/rules like

get-orig-source:
uscan --download-current-version --force-download

If your debian/watch file is up-to-date and works it will download the
corresponding upstream sources. If you need to repack them, you could
also use the Files-Excluded field in debian/copyright, e.g.

Files-Excluded:
*.jar

and enhance the get-orig-source target like that:

get-orig-source:
uscan --download-current-version --force-download --repack -compression 
xz

and all pre-built jar files will be removed while downloading the
original sources.

This is usually an adequate documentation and a comfortable method to
quickly obtain the upstream sources. Since it is indeed rather common
for Java packages to include pre-built jar files, you can also omit the
+dfsg suffix. That's up to you. I

Markus



signature.asc
Description: OpenPGP digital signature
__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

xml-maven-plugin 1.0.1-1 MIGRATED to testing

[Debian testing watch]

FYI: The status of the xml-maven-plugin source package
in Debian's testing distribution has changed.

  Previous version: 1.0-3
  Current version:  1.0.1-1

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Bug#775450: clojure1.6: clojure 1.6 doesn't work with gij/gcj 4.9 instead of openjdk

[Alex Vong]

On 07/02/2016, Emmanuel Bourg  wrote:
> Clojure 1.6 requires Java 6 or higher, I don't think adding the
> -noverify flag will fix all the compatibility issues with GCJ. We should
> adjust the package dependencies instead.
>
> Emmanuel Bourg
>
>

You are right, it is more of a workaround than an actual fix, in case
we need to use gcj with clojure for some reason. By the way, may I ask
why all clojure version has +dfsg suffice? My guess is that because
the upstream tarball contains pre-built jar. Should we document it in
`README.source'?

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

cglib 3.2.0-2 MIGRATED to testing

[Debian testing watch]

FYI: The status of the cglib source package
in Debian's testing distribution has changed.

  Previous version: 2.2.2+dfsg2-2
  Current version:  3.2.0-2

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

xmlgraphics-commons 2.1-1 MIGRATED to testing

[Debian testing watch]

FYI: The status of the xmlgraphics-commons source package
in Debian's testing distribution has changed.

  Previous version: 2.0.1-2
  Current version:  2.1-1

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

libslf4j-java 1.7.14-2 MIGRATED to testing

[Debian testing watch]

FYI: The status of the libslf4j-java source package
in Debian's testing distribution has changed.

  Previous version: 1.7.13-1
  Current version:  1.7.14-2

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

avro-java is marked for autoremoval from testing

[Debian testing autoremoval watch]

avro-java 1.7.7-1 is marked for autoremoval from testing on 2016-02-29

It is affected by these RC bugs:
813287: avro-java: FTBFS: Plugin 
com.thoughtworks.paranamer:paranamer-maven-plugin:2.8 or one of its 
dependencies could not be resolved


__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

eclipse-subclipse is marked for autoremoval from testing

[Debian testing autoremoval watch]

eclipse-subclipse 1.10.3-1 is marked for autoremoval from testing on 2016-02-14

It (build-)depends on packages with these RC bugs:
809566: eclipse-mylyn: FTBFS: Unsatisfied import package javax.mail_0.0.0.


__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

reproducible.debian.net status changes for doxia

[Reproducible builds folks]

2016-02-07 05:06 https://tests.reproducible-builds.org/unstable/amd64/doxia 
changed from FTBFS -> unreproducible

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Bug#775450: clojure1.6: clojure 1.6 doesn't work with gij/gcj 4.9 instead of openjdk

[Alex Vong]

On 08/02/2016, Markus Koschany  wrote:
> Am 07.02.2016 um 21:38 schrieb Emmanuel Bourg:
>> Le 7/02/2016 17:21, Alex Vong a écrit :
>>
>>> You are right, it is more of a workaround than an actual fix, in case
>>> we need to use gcj with clojure for some reason. By the way, may I ask
>>> why all clojure version has +dfsg suffice? My guess is that because
>>> the upstream tarball contains pre-built jar. Should we document it in
>>> `README.source'?
>>
>> You're probably right about the removed jar files, but that's so common
>> for the Java packages that we don't bother documenting it.
>
> Usually every package should provide either a get-orig-source target or
> a README.source file if you repack the tarball. It is in general a good
> idea to create a simple get-orig-source target in debian/rules like
>
> get-orig-source:
>   uscan --download-current-version --force-download
>
> If your debian/watch file is up-to-date and works it will download the
> corresponding upstream sources. If you need to repack them, you could
> also use the Files-Excluded field in debian/copyright, e.g.
>
> Files-Excluded:
>   *.jar
>
> and enhance the get-orig-source target like that:
>
> get-orig-source:
>   uscan --download-current-version --force-download --repack -compression 
> xz
>
> and all pre-built jar files will be removed while downloading the
> original sources.
>
> This is usually an adequate documentation and a comfortable method to
> quickly obtain the upstream sources. Since it is indeed rather common
> for Java packages to include pre-built jar files, you can also omit the
> +dfsg suffix. That's up to you. I
>
> Markus
>
>

Thanks you guys for the explanation. I don't know it is a common thing
for java upstream tarball to include jar.

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.