Bug#980017: argus-clients FTBFS due to missing link and includes for tirpc library

[Tiago Stürmer Daitx]

Source: argus-clients
Version: 3.0.8.2-6
Severity: important

Dear Maintainer,

This package failed to rebuild in Ubuntu with "fatal error: rpc/type.h".
Sun RPC used to be included in glibc and now it must be added from
TI-RPC library (libtirpc-dev).  

To fix it a simple change was needed:

configure.ac:
+AC_CHECK_LIB([tirpc],[rpc_call],,
+ [AC_MSG_ERROR([no tirpc library, exiting...!])])
+V_INCLS="$V_INCLS -I/usr/include/tirpc"
 AC_CHECK_FUNCS(xdrmem_create)

The full debdiff is available at:
https://launchpadlibrarian.net/516883019/argus-clients_1%3A3.0.8.2-6ubuntu1_1%3A3.0.8.2-6ubuntu2.diff.gz

Best regards,
Tiago


-- System Information:
Debian Release: bullseye/sid
  APT prefers focal-updates
  APT policy: (500, 'focal-updates'), (500, 'focal-security'), (500, 'focal'), 
(400, 'focal-proposed'), (100, 'focal-backports')
Architecture: amd64 (x86_64)

Kernel: Linux 5.8.0-36-generic (SMP w/12 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#980016: argus FTBFS due to missing link and includes for tirpc library

[Tiago Stürmer Daitx]

Source: argus
Version: 2:3.0.8.2-2
Severity: important

Dear Maintainer,

This package failed to rebuild in Ubuntu with "fatal error: rpc/type.h".
Sun RPC used to be included in glibc and now it must be added from
TI-RPC library (libtirpc-dev).

To fix it 3 changes were required:

configure.ac:
+AC_CHECK_LIB([tirpc],[rpc_call],,
+ [AC_MSG_ERROR([no tirpc library, exiting...!])])
 AC_CHECK_FUNCS(xdrmem_create)

reordering library inclusion in argus/Makefile.in:
-LIB = @LIBS@ @V_THREADS@ $(WRAPLIBS) $(SASLLIBS) $(COMPATLIB) 
../lib/argus_common.a -lm
+LIB = ../lib/argus_common.a -lm @LIBS@ @V_THREADS@ $(WRAPLIBS) $(SASLLIBS) 
$(COMPATLIB)

and finally the header include in debian/rules
+export DEB_CFLAGS_MAINT_APPEND  = -I/usr/include/tirpc

I tried the header inclusion through V_INCLS but it was being overriden
by the wrap macro, and this quick workaround was fine.

The full debdiff is available at:
https://launchpad.net/ubuntu/+archive/primary/+files/argus_2%3A3.0.8.2-2_2%3A3.0.8.2-2ubuntu1.diff.gz

Best regards,
Tiago

-- System Information:
Debian Release: bullseye/sid
  APT prefers focal-updates
  APT policy: (500, 'focal-updates'), (500, 'focal-security'), (500, 'focal'), 
(400, 'focal-proposed'), (100, 'focal-backports')
Architecture: amd64 (x86_64)

Kernel: Linux 5.8.0-36-generic (SMP w/12 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#980015: alberta: FTBFS due to missing link and include for tirpc library

[Tiago Stürmer Daitx]

Source: alberta
Version: 3.0.1-2
Severity: important

Dear Maintainer,

This package failed to rebuild in Ubuntu with "fatal error: rpc/type.h".
Sun RPC used to be included in glibc and now it must be added from
TI-RPC library (libtirpc-dev).

I was able to build it after adding a check lib in configure.ac right
before check headers for rpc/types.h
+AC_CHECK_LIB([tirpc],[rpc_call],,
+ [AC_MSG_ERROR([no tirpc library, exiting...!])])

and including the library in debian/rules
+export DEB_CFLAGS_MAINT_APPEND = -I/usr/include/tirpc

There might a better way to include that library directly in
configure.ac, but this is what worked for me.

Regards,
Tiago

-- System Information:
Debian Release: bullseye/sid
  APT prefers focal-updates
  APT policy: (500, 'focal-updates'), (500, 'focal-security'), (500, 'focal'), 
(400, 'focal-proposed'), (100, 'focal-backports')
Architecture: amd64 (x86_64)

Kernel: Linux 5.8.0-36-generic (SMP w/12 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#965047: jtreg won't run as it can't locate its own jar file

[Tiago Stürmer Daitx]

Package: jtreg
Version: 5.1-b01-1
Severity: important

Dear Maintainer,

Since jtreg 5.1-b01-1 it will no longer run without having JTREG_HOME (or
JT_HOME) explicitly set on the environment, previous versions worked ok.

It will exit 1 when trying to run it:
$ jtreg
Cannot determine JTREG_HOME; please set it explicitly

The reason is a change in debian/patches/launcher.patch that adds the check

 if [ -z "${JTREG_HOME}" ]; then
 JTREG_HOME="/usr/share/jtreg"
 fi

too further down compared to the previous jtreg version. This causes the code
to search for lib/jtreg.jar in the script's path (/usr/bin) first, which does
not work and then calls exit 1.

That check is added exclusively for Debian/Ubuntu by d/p/launcher.patch and
should come before jtreg will try to look for lib/jtreg.jar by itself.

This also affects openjdk autopkgtests, which don't get run becuse jtreg
fails to start.

Thanks!

-- System Information:
Debian Release: bullseye/sid
  APT prefers focal
  APT policy: (500, 'focal'), (400, 'focal-proposed')
Architecture: amd64 (x86_64)

Kernel: Linux 5.4.0-26-generic (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#938969: python-packaging: test failures due to wrong arch check

[Tiago Stürmer Daitx]

Package: python-packaging
Version: 19.0-1
Severity: important

Dear Maintainer,

Since 19.1-1 python-packaging introduced a Tags class that has methods
that depend upon distutils.util.get_platform(). 

The problem is that the behavior of get_platform() changes during build
time, as pybuild sets _PYTHON_HOST_PLATFORM which overrides the default
output of get_platform().

This causes linux-x86_64 to be changed to linux-amd64, leading to 2 test
failures and some if clauses to run amok as they expect the string x86_64.

Both tests/test_tags.py and packaging/tags.py require updates to deal
with the build time get_platform changes.

Regards,
Tiago

-- System Information:
Debian Release: buster/sid
  APT prefers eoan
  APT policy: (500, 'eoan'), (400, 'eoan-proposed')
Architecture: amd64 (x86_64)

Kernel: Linux 5.0.0-20-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python-packaging depends on:
ii  python2.7.16-1
ii  python-pyparsing  2.2.0+dfsg1-2
ii  python-six1.12.0-1build1

python-packaging recommends no packages.

python-packaging suggests no packages.

-- no debconf information

Bug#925320: android-platform-tools-apksig: apksigner fails to run on OpenJDK 8 due to UnsupportedClassVersionError

[Tiago Stürmer Daitx]

Package: android-platform-tools-apksig
Version: 0.8-2
Severity: important

Dear Maintainer,

The apksigner binary from android-platform-tools-apksig 0.8-2 fails to
run under OpenJDK 8 because it is not being targetted to java 8 level.

Please note that if OpenJDK 11 is installed it will be used instead even
if the system is set to use OpenJDK 8 binaries by default, so if trying
to reproduce this make sure that *only* OpenJDK 8 runtime is installed.

The error is:
$ apksigner
Error: A JNI error has occurred, please check your installation and try again
Exception in thread "main" java.lang.UnsupportedClassVersionError: 
com/android/apksigner/ApkSignerTool has been compiled by a more recent version 
of the Java Runtime (class file version 55.0), this version of the Java Runtime 
only recognizes class file versions up to 52.0
 at java.lang.ClassLoader.defineClass1(Native Method)
 at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
 at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
 at java.net.URLClassLoader.defineClass(URLClassLoader.java:468)
 at java.net.URLClassLoader.access$100(URLClassLoader.java:74)
 at java.net.URLClassLoader$1.run(URLClassLoader.java:369)
 at java.net.URLClassLoader$1.run(URLClassLoader.java:363)
 at java.security.AccessController.doPrivileged(Native Method)
 at java.net.URLClassLoader.findClass(URLClassLoader.java:362)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
 at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
 at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
 at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:495)

The fix is to replace the '-source 8' entry with '--release 8' in the
rules file. While adding '-target 8' would also work, using '--release'
is better as it also sets the right '-bootclasspath' without much fuzz.

Regards,
Tiago

-- System Information:
Debian Release: buster/sid
  APT prefers disco
  APT policy: (500, 'disco'), (400, 'disco-proposed')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-13-generic (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#925225: gradle: Fix gradle compatibility with OpenJDK 8

[Tiago Stürmer Daitx]

Package: gradle
Version: 4.4.1-5
Severity: normal

Dear Maintainer,

Since the fix for bug #909905 in gradle 4.4.1-1 it has been not possible
to run the generated binaries with OpenJDK 8.

The patch introduced in 4.4.1-1 was loosely based on the actual upstream
patch and - differently from upstream - it replaced OpenJDK 8 classloading
with OpenJDK 9+ classloading scheme. The upstream patch modified
classloading to _add_ OpenJDK 11 support. The 4.4.1-1 also modified
gradle's Depends: to java 9.

gradle 4.4.1 in itself is actually compatible with OpenJDK 8 and the
packaging just added the minimum support to build and run it with OpenJDK
11. Still, that shouldn't be done in a way to remove the possibility of
running gradle with OpenJDK 8.

Regards,
Tiago


-- System Information:
Debian Release: buster/sid
  APT prefers disco
  APT policy: (500, 'disco'), (400, 'disco-proposed')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-13-generic (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#923800: mapsforge: please include minimum versions in build-depends

[Tiago Stürmer Daitx]

Package: mapsforge
Version: 0.10.0+dfsg.1-1
Severity: normal

Dear Maintainer,

mapsforge version 0.10.0+dfsg.1-1 does declare runtime version
dependency but does not explicitly declares the required build time
dependency versions.

This would better show what is required for build and would help any
future backports. I have run into this issue while backporting this
package into Ubuntu Bionic (as part of the OpenJDK 11 transition).


--- mapsforge-0.10.0+dfsg.1/debian/control  2018-10-25 20:30:27.0 
+
+++ mapsforge-0.10.0+dfsg.1/debian/control  2019-03-05 08:43:02.0 
+
@@ -1,12 +1,12 @@
gradle-debian-helper,
javahelper (>= 0.70),
junit4,
-   libjaxb-java,
-   libjts-java,
-   libkxml2-java,
+   libjaxb-java (>= 2.3.0.1),
+   libjts-java (>= 1.15.0),
+   libkxml2-java (>= 2.3.0),
libsvgsalamander-java,
-   libtrove3-java,
+   libtrove3-java (>= 3.0.3),
maven-repo-helper,
-   osmosis
+   osmosis (>= 0.46)
 Standards-Version: 4.1.2
 Homepage: https://wiki.openstreetmap.org/wiki/Mapsforge

Regards,
Tiago Daitx

-- System Information:
Debian Release: buster/sid
  APT prefers disco
  APT policy: (500, 'disco'), (400, 'disco-proposed')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-13-generic (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#913853: jtreg fails to run under openjdk-8 due to api incompatibility with openjdk-9 or later

[Tiago Stürmer Daitx]

Package: jtreg
Version: 4.2-b13-1
Severity: important

Dear Maintainer,

openjdk-9 introduced a few api changes that result in runtime errors when 
trying to run the java classes under openjdk 8 (or earlier) even when 
-source/-target are properly set.

The fix is to build such code using the new openjdk-9 flag "--release" instead 
of the "-source/-target" pair.

When running Cosmic's jtreg 4.2-b13-1 with agentvm under openjdk-8 it will fail 
and output a few lines such as:
stderr: Exception: java.lang.NoSuchMethodError thrown from the 
UncaughtExceptionHandler in thread "main"

The java.lang.NoSuchMethodError is actually caused by 
"java.lang.NoSuchMethodError: java.nio.ByteBuffer.flip()Ljava/nio/ByteBuffer" 
which can be easily solved by building jtreg with the "--release 7" argument.

[Test Case]
For this test case we need to create an empty TEST.ROOT file and a test class 
to satisfy jtreg requirements of a minimum test. jtreg must also be forced to 
use openjdk-8.

$ sudo apt install openjdk-8-jdk jtreg
$ touch TEST.ROOT
$ cat > Hello.java << EOF
/*
 * @test
 * @bug 2718282
 * @summary Hello test
 */

public class Hello {
public static void main(String [] args) throws Exception {
if (true)
System.out.println("Hello World!");
else
throw new Exception("??");
}
}
EOF
$ JT_JAVA=/usr/lib/jvm/java-8-openjdk-amd64/ jtreg -va -agentvm Hello.java
[2018-11-15 23:42:34,720] Agent[0]: stderr:
[2018-11-15 23:42:34,721] Agent[0]: stderr: Exception: 
java.lang.NoSuchMethodError thrown from the UncaughtExceptionHandler in thread 
"main"
--
TEST: Hello.java
TEST JDK: /usr/lib/jvm/java-8-openjdk-amd64
[snipped]
Test results: error: 1
Report written to /tmp/JTreport/html/report.html
Results written to /tmp/JTwork
Error: Some tests failed or other problems occurred.

The expected response from jtreg does not contain the "stderr:" lines as in:
$ JT_JAVA=/usr/lib/jvm/java-8-openjdk-amd64/ jtreg -va -agentvm Hello.java
--
TEST: Hello.java
TEST JDK: /usr/lib/jvm/java-8-openjdk-amd64
[snipped]
Test results: passed: 1
Report written to /tmp/JTreport/html/report.html
Results written to /tmp/JTwork

Alternatively one can also check that openjdk-lts is not affected by the 
change, it should output the same before and after the fix:
$ sudo apt install openjdk-11-jdk
$ JT_JAVA=/usr/lib/jvm/java-11-openjdk-amd64/ jtreg -va -agentvm Hello.java
--
TEST: Hello.java
TEST JDK: /usr/lib/jvm/java-11-openjdk-amd64
[snipped]
Test results: passed: 1
Report written to /tmp/JTreport/html/report.html
Results written to /tmp/JTwork

[Regression Potential]
1. The --release argument is jdk9+ only, if jtreg is ever build with an older 
jdk it will FTBFS, so this change should only be backported on releases where 
the default-jdk is 9+.
2. The --release N argument is equivalent to setting -source N/-target 
N/-bootclasspath , which can cause issues if the compiled 
classes use APIs that have been removed or are considered internal. The current 
jtreg version does not rely on internal classes from jdk 8 (otherwise it would 
FTBFS) but if a later version does that it will probably FTBFS - note that this 
is very unlikely as it would mean that upstream decided to break building jtreg 
with newer jdks.

[Other Info]
See https://github.com/apache/felix/pull/114 for a good overview on the methods 
that changed on OpenJDK 9 and a better description on the cause. Note that they 
propose patching the methods to cast ByteBuffer to Buffer when calling the 
affected methods, but this can be easily prevented by using the --release 
argument instead.


I will follow-up with a patch as soon as I have a bug # to put on the
changelog and the patch dep3 header.

Regards,
Tiago


-- System Information:
Debian Release: buster/sid
  APT prefers disco
  APT policy: (500, 'disco'), (400, 'disco-proposed')
Architecture: amd64 (x86_64)

Kernel: Linux 4.18.0-10-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#910773: clojure1.8: clojure fails to run with openjdk-11

[Tiago Stürmer Daitx]

Package: clojure1.8
Version: 1.8.0-7
Severity: important

Dear Maintainer,

when trying to run clojure1.8 with openjdk-11 it fails with

Exception in thread "main" java.lang.ExceptionInInitializerError
 at clojure.main.(main.java:20)
Caused by: java.lang.IllegalArgumentException: Must hint overloaded method: 
toArray, compiling:(clojure/gvec.clj:131:1)
 at clojure.lang.Compiler.analyzeSeq(Compiler.java:6875)
 at clojure.lang.Compiler.analyze(Compiler.java:6669)
 at clojure.lang.Compiler.analyze(Compiler.java:6625)
 at clojure.lang.Compiler$BodyExpr$Parser.parse(Compiler.java:6003)
 at clojure.lang.Compiler$LetExpr$Parser.parse(Compiler.java:6319)
 at clojure.lang.Compiler.analyzeSeq(Compiler.java:6868)
 at clojure.lang.Compiler.analyze(Compiler.java:6669)
 at clojure.lang.Compiler.analyze(Compiler.java:6625)
 at clojure.lang.Compiler$BodyExpr$Parser.parse(Compiler.java:6005)
 at clojure.lang.Compiler$FnMethod.parse(Compiler.java:5380)
 at clojure.lang.Compiler$FnExpr.parse(Compiler.java:3972)
 at clojure.lang.Compiler.analyzeSeq(Compiler.java:6866)
 at clojure.lang.Compiler.analyze(Compiler.java:6669)
 at clojure.lang.Compiler.eval(Compiler.java:6924)
 at clojure.lang.Compiler.load(Compiler.java:7379)
 at clojure.lang.RT.loadResourceScript(RT.java:372)
 at clojure.lang.RT.loadResourceScript(RT.java:363)
 at clojure.lang.RT.load(RT.java:453)
 at clojure.lang.RT.load(RT.java:419)
 at clojure.core$load$fn__1621.invoke(core.clj:5893)
 at clojure.core$load.invokeStatic(core.clj:5892)
 at clojure.core$load.doInvoke(core.clj:5876)
 at clojure.lang.RestFn.invoke(RestFn.java:408)
 at clojure.core$eval3106.invokeStatic(core.clj:6523)
 at clojure.core$eval3106.invoke(core.clj:6523)
 at clojure.lang.Compiler.eval(Compiler.java:6927)
 at clojure.lang.Compiler.load(Compiler.java:7379)
 at clojure.lang.RT.loadResourceScript(RT.java:372)
 at clojure.lang.RT.loadResourceScript(RT.java:363)
 at clojure.lang.RT.load(RT.java:453)
 at clojure.lang.RT.load(RT.java:419)
 at clojure.lang.RT.doInit(RT.java:461)
 at clojure.lang.RT.(RT.java:331)
 ... 1 more
Caused by: java.lang.IllegalArgumentException: Must hint overloaded method: 
toArray
 at clojure.lang.Compiler$NewInstanceMethod.parse(Compiler.java:8206)
 at clojure.lang.Compiler$NewInstanceExpr.build(Compiler.java:7798)
 at 
clojure.lang.Compiler$NewInstanceExpr$DeftypeParser.parse(Compiler.java:7678)
 at clojure.lang.Compiler.analyzeSeq(Compiler.java:6868)
 ... 33 more

This is related to https://dev.clojure.org/jira/browse/CLJ-2374 and the 
proposed fix upstream is available at 
https://github.com/tirkarthi/clojure/commit/63dab8e6cb702a6b0c5b279721bee7eff0aba44f.patch

Regards,
Tiago

-- System Information:
Debian Release: buster/sid
  APT prefers cosmic
  APT policy: (500, 'cosmic'), (400, 'cosmic-proposed')
Architecture: amd64 (x86_64)

Kernel: Linux 4.18.0-7-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#910098: groovy: improve doc linking and add missing dependencies

[Tiago Stürmer Daitx]

Package: groovy
Version: 2.4.15-3
Severity: normal

Dear Maintainer,

The groovy doc linking can be improved by adding a few docs that
have been packaged in Debian. Also, the previous fix for the jre
doc link was using a URI with a single slash, which although works
is not the standard.

Additionally to that it was linking to default-jre/api, even though
the actual doc apis files are in the default-jdk-doc package which
is included in the b-deps. IMHO since the files and b-deps are from
this package the hardcoded path should be enforced to use the same
default-jdk-doc api path.

I will attach the patch as soon as I have a bug number for the
changelog entry.

Regards,
Tiago

-- System Information:
Debian Release: buster/sid
  APT prefers cosmic
  APT policy: (500, 'cosmic'), (400, 'cosmic-proposed')
Architecture: amd64 (x86_64)

Kernel: Linux 4.18.0-7-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#910093: maven-compiler-plugin: tests fail due to hardcoded junit jar path and missing JAVA_HOME

[Tiago Stürmer Daitx]

Package: maven-compiler-plugin
Version: 3.8.0-1
Severity: minor

Dear Maintainer,

Currently maven-compiler-plugin tests are failing due to 2 different
reasons:
1. Some tests depend on JAVA_HOME being set
2. The junit jar file is hardcoded to version 3.8.1

Excerpt of the buildlog with the test failures:
[ERROR] Tests run: 12, Failures: 0, Errors: 4, Skipped: 0, Time elapsed: 8.983 
s <<< FAILURE! - in org.apache.maven.plugin.compiler.CompilerMojoTestCase
[ERROR] 
testCompilerBasic(org.apache.maven.plugin.compiler.CompilerMojoTestCase)  Time 
elapsed: 5.642 s  <<< ERROR!
org.apache.maven.plugin.compiler.CompilationFailureException: Compilation 
failure
at 
org.apache.maven.plugin.compiler.CompilerMojoTestCase.testCompilerBasic(CompilerMojoTestCase.java:99)

[ERROR] 
testCompilerIncludesExcludes(org.apache.maven.plugin.compiler.CompilerMojoTestCase)
  Time elapsed: 0.784 s  <<< ERROR!
org.apache.maven.plugin.compiler.CompilationFailureException: Compilation 
failure
at 
org.apache.maven.plugin.compiler.CompilerMojoTestCase.testCompilerIncludesExcludes(CompilerMojoTestCase.java:190)

[ERROR] 
testCompileSkipMain(org.apache.maven.plugin.compiler.CompilerMojoTestCase)  
Time elapsed: 0.369 s  <<< ERROR!
org.apache.maven.plugin.compiler.CompilationFailureException: Compilation 
failure
at 
org.apache.maven.plugin.compiler.CompilerMojoTestCase.testCompileSkipMain(CompilerMojoTestCase.java:359)

[ERROR] testCompilerFork(org.apache.maven.plugin.compiler.CompilerMojoTestCase) 
 Time elapsed: 0.163 s  <<< ERROR!
org.apache.maven.plugin.MojoExecutionException: Fatal error compiling
at 
org.apache.maven.plugin.compiler.CompilerMojoTestCase.testCompilerFork(CompilerMojoTestCase.java:215)
Caused by: org.codehaus.plexus.compiler.CompilerException: Error while 
executing the external compiler.
at 
org.apache.maven.plugin.compiler.CompilerMojoTestCase.testCompilerFork(CompilerMojoTestCase.java:215)
Caused by: org.codehaus.plexus.util.cli.CommandLineException: Error while 
executing process.
at 
org.apache.maven.plugin.compiler.CompilerMojoTestCase.testCompilerFork(CompilerMojoTestCase.java:215)
Caused by: java.io.IOException: Cannot run program "bin/javac" (in directory 
"/<>"): error=2, No such file or directory
at 
org.apache.maven.plugin.compiler.CompilerMojoTestCase.testCompilerFork(CompilerMojoTestCase.java:215)
Caused by: java.io.IOException: error=2, No such file or directory
at 
org.apache.maven.plugin.compiler.CompilerMojoTestCase.testCompilerFork(CompilerMojoTestCase.java:215)

[INFO]
[INFO] Results:
[INFO]
[ERROR] Errors:
[ERROR]   CompilerMojoTestCase.testCompileSkipMain:359 ? CompilationFailure 
Compilation ...
[ERROR]   CompilerMojoTestCase.testCompilerBasic:99 ? CompilationFailure 
Compilation fai...
[ERROR]   CompilerMojoTestCase.testCompilerFork:215 ? MojoExecution Fatal error 
compilin...
[ERROR]   CompilerMojoTestCase.testCompilerIncludesExcludes:190 ? 
CompilationFailure Com...
[INFO]
[ERROR] Tests run: 12, Failures: 0, Errors: 4, Skipped: 0
[INFO]
[ERROR] There are test failures.


Expected result with passing tests:
[INFO] Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 51.216 
s - in org.apache.maven.plugin.compiler.CompilerMojoTestCase
[INFO]
[INFO] Results:
[INFO]
[INFO] Tests run: 12, Failures: 0, Errors: 0, Skipped: 0


I will be attaching the debdiff with a fix as soon as I have a bug
number to reference to in the changelog.

Regards,
Tiago

-- System Information:
Debian Release: buster/sid
  APT prefers cosmic
  APT policy: (500, 'cosmic'), (400, 'cosmic-proposed')
Architecture: amd64 (x86_64)

Kernel: Linux 4.18.0-7-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#909905: gradle FTBFS when building with openjdk-11 (needs update to 4.7.0 or upstream patch)

[Tiago Stürmer Daitx]

Package: gradle
Version: 4.4-2
Severity: normal

Dear Maintainer,

gradle 4.4-2 currently FTBFS when build with openjdk-11.

* Exception is:
java.lang.IllegalArgumentException: Could not determine java version from '11'.
at org.gradle.api.JavaVersion.toVersion(JavaVersion.java:72)
at org.gradle.api.JavaVersion.current(JavaVersion.java:82)
at 
org.gradle.internal.jvm.UnsupportedJavaRuntimeException.assertUsingVersion(UnsupportedJavaRuntimeException.java:42)
at 
org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:32)
at 
org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:24)
at 
org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:33)
at 
org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:22)
at 
org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:257)
at 
org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:191)
at org.gradle.launcher.Main.doAction(Main.java:33)
at org.gradle.launcher.bootstrap.EntryPoint.run(EntryPoint.java:45)
at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at 
org.gradle.launcher.bootstrap.ProcessBootstrap.runNoExit(ProcessBootstrap.java:60)
at 
org.gradle.launcher.bootstrap.ProcessBootstrap.run(ProcessBootstrap.java:37)
at org.gradle.launcher.GradleMain.main(GradleMain.java:23)

it needs either to be updated to 4.7 or have the upstream patch [1]
applied.

References:
[1] 
https://github.com/gradle/gradle/commit/ac15612d41b43c39c8e39d12fdd6621589b0f782#diff-1992c69962eb418e832c020dd61b2f1b.diff


-- System Information:
Debian Release: buster/sid
  APT prefers cosmic
  APT policy: (500, 'cosmic'), (400, 'cosmic-proposed')
Architecture: amd64 (x86_64)

Kernel: Linux 4.18.0-7-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#905675: testng missing dependency on guava causes tests to fails

[Tiago Stürmer Daitx]

Package: testng
Version: 6.9.12-3
Severity: normal

Dear Maintainer,

While running OpenJDK 10 tests I noticed that quite a few tests that
depend on testng fail due to a missing guava class.

The package libguava-java has the class but it is not declared as a
dependency.

The bug has been reported upstream back in 2016 [1] and fixed a few days
after that [2]. The guava class import was replaced with a new internal
class [3].

testng should be updated to a newer version or that particular patch [3]
should be applied to the existing package.

References:
[1] https://github.com/cbeust/testng/issues/1085
[2] https://github.com/cbeust/testng/pull/1086
[3] 
https://github.com/cbeust/testng/pull/1086/commits/deeb5847282ae3b5b185c046a8146814bf98b124


Error output example:

java.lang.NoClassDefFoundError: com/google/common/primitives/Ints
at 
org.testng.internal.annotations.JDK15TagFactory.createDataProviderTag(JDK15TagFactory.java:335)
at 
org.testng.internal.annotations.JDK15TagFactory.createTag(JDK15TagFactory.java:59)
at 
org.testng.internal.annotations.JDK15AnnotationFinder.findAnnotation(JDK15AnnotationFinder.java:217)
at 
org.testng.internal.annotations.JDK15AnnotationFinder.findAnnotation(JDK15AnnotationFinder.java:111)
at org.testng.internal.Parameters.findDataProvider(Parameters.java:326)
at org.testng.internal.Parameters.findDataProvider(Parameters.java:261)
at org.testng.internal.Parameters.handleParameters(Parameters.java:418)
at org.testng.internal.Invoker.handleParameters(Invoker.java:1240)
at org.testng.internal.Invoker.createParameters(Invoker.java:980)
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1070)
at 
org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.

Regards,
Tiago Daitx

-- System Information:
Debian Release: buster/sid
  APT prefers cosmic
  APT policy: (500, 'cosmic'), (400, 'cosmic-proposed')
Architecture: amd64 (x86_64)

Kernel: Linux 4.15.0-23-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages testng depends on:
ii  libbsh-java 2.0b4-19
pn  libjcommander-java  

Versions of packages testng recommends:
ii  ant 1.10.4-2
ii  junit4  4.12-7
pn  libyaml-snake-java  

testng suggests no packages.

Bug#898678: ca-certificates-java: convert PKCS12 cacerts keystore to JKS

[Tiago Stürmer Daitx]

Package: ca-certificates-java
Version: 20180413
Severity: important

Dear Maintainer,

The fix for bug #894979 which updated ca-certificates-java to generate
JKS keystores by default - instead OpenJDK's 9+ default of PKCS12 - only
fixes new installs.

Any user already affected by that issue won't benefit from the fix, as
the file /etc/ssl/certs/java/cacerts is at most updated by the
jks-keystore hook. The only way to actually change it from the PKCS12
to the JKS format is to remove the cacerts file and then calling
'update-ca-certificates -f' - which is also accomplished by removing and
then reinstalling the ca-certificates-java package.

The attached patch fixes this behavior by:
1) Detecting if a PKCS12 cacert exists
2) Converting it to JKS and saving it to cacerts.dpkg-new

Finally, if, and only if, 'cacerts_updates' is set to 'yes':
3) Moving the old PKCS12 cacerts to a cacerts.dpkg-old and the dpkg-new
into /etc/ssl/certs/java/cacerts.

Additionally, a few other fixes are also addressed in the debdiff:
1) Only set JAVA_HOME if a jvm is found. Previously if none of the the
jvms in the list were found the last one jvm was used - although that
didn't cause any unexpected errors, it was wrong.
2) Avoid generating a jvm.cfg as openjdk has it's own logic for
providing a well defined default jvm.cfg in such scenarios.
3) On Ubuntu it should depend on openjdk-11-jre-headless instead
of openjdk-8.


Please review and consider applying the provided debdiff.

Regards,
Tiago Daitx

-- System Information:
Debian Release: buster/sid
  APT prefers cosmic
  APT policy: (500, 'cosmic'), (400, 'cosmic-proposed')
Architecture: amd64 (x86_64)

Kernel: Linux 4.15.0-20-lowlatency (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru ca-certificates-java-20180413/debian/changelog 
ca-certificates-java-20180413.1/debian/changelog
--- ca-certificates-java-20180413/debian/changelog  2018-04-13 
09:15:39.0 -0300
+++ ca-certificates-java-20180413.1/debian/changelog2018-05-14 
23:16:43.0 -0300
@@ -1,3 +1,18 @@
+ca-certificates-java (20180413.1) unstable; urgency=medium
+
+  [ Tiago Stürmer Daitx ]
+  * debian/jks-keystore.hook.in: Don't create a jvm-*.cfg file, a default file
+with the right configuration is already supplied by the openjdk packages.
+  * debian/jks-keystore.hook.in, debian/postinst.in: Only export JAVA_HOME
+and update PATH if a known jvm was found.
+  * debian/postinst.in: Detect PKCS12 cacert keystore generated by
+previous ca-certificates-java and convert them to JKS.
+
+  [ Matthias Klose ]
+  * Explicitly depend on openjdk-11-jre-headless, needed to configure.
+
+ -- Tiago Stürmer Daitx <tiago.da...@ubuntu.com>  Tue, 15 May 2018 02:16:43 
+
+
 ca-certificates-java (20180413) unstable; urgency=medium
 
   * Team upload.
diff -Nru ca-certificates-java-20180413/debian/jks-keystore.hook.in 
ca-certificates-java-20180413.1/debian/jks-keystore.hook.in
--- ca-certificates-java-20180413/debian/jks-keystore.hook.in   2018-04-13 
09:02:14.0 -0300
+++ ca-certificates-java-20180413.1/debian/jks-keystore.hook.in 2018-05-14 
23:16:43.0 -0300
@@ -45,20 +45,12 @@
oracle-java10-jre-$arch oracle-java10-server-jre-$arch 
oracle-java10-jdk-$arch \
java-11-openjdk-$arch java-11-openjdk \
oracle-java11-jre-$arch oracle-java11-server-jre-$arch 
oracle-java11-jdk-$arch; do
-if [ -x /usr/lib/jvm/$jvm/bin/java ]; then
+if [ -x /usr/lib/jvm/$jvm/bin/java ]; then
+export JAVA_HOME=/usr/lib/jvm/$jvm
+PATH=$JAVA_HOME/bin:$PATH
break
-fi
+fi
 done
-export JAVA_HOME=/usr/lib/jvm/$jvm
-PATH=$JAVA_HOME/bin:$PATH
-
-temp_jvm_cfg=
-if [ ! -f /etc/${jvm%-$arch}/jvm-$arch.cfg ]; then
-# the jre is not yet configured, but jvm.cfg is needed to run it
-temp_jvm_cfg=/etc/${jvm%-$arch}/jvm-$arch.cfg
-mkdir -p /etc/${jvm%-$arch}
-printf -- "-server KNOWN\n" > $temp_jvm_cfg
-fi
 
 if dpkg-query --version >/dev/null; then
 nsspkg=$(dpkg-query -L "$(nsslib_name)" | sed -n 
's,\(.*\)/libnss3\.so$,\1,p'|head -n 1)
diff -Nru ca-certificates-java-20180413/debian/postinst.in 
ca-certificates-java-20180413.1/debian/postinst.in
--- ca-certificates-java-20180413/debian/postinst.in2018-04-13 
09:03:15.0 -0300
+++ ca-certificates-java-20180413.1/debian/postinst.in  2018-05-14 
23:16:43.0 -0300
@@ -35,12 +35,50 @@
oracle-java10-jre-$arch oracle-java10-server-jre-$arch 
oracle-java10-jdk-$arch \
java-11-openjdk-$arch java-11-openjdk \
oracle-java11-jre-$arch oracle-java11-server-jre-$arch 
oracle-java11-jdk-$arch; do
-if [ -x /usr/lib/jvm/$jvm/bin/java ]; then
-break
+if [ -x /usr/lib/jvm/$jvm/bin/java ]; then
+ex

Bug#897612: groovy: [FTBFS] groovy: 2.4.15-1 ftbfs due to invalid javadoc links

[Tiago Stürmer Daitx]

Package: groovy
Version: 2.4.15-1
Severity: important

Dear Maintainer,


Note: Copied from Ubuntu bug #1765885 [1].

Starting with openjdk-10 all invalid, unreachable, or nonexistent javadoc links 
cause the javadoc to throw out an error - until openjdk-9 they were simply 
ignored with at most a warning.

groovy currently FTBFS due to:

Starting process 'command '/usr/lib/jvm/java-11-openjdk-amd64/bin/javadoc''. 
Working directory: /<> Command: 
/usr/lib/jvm/java-11-openjdk-amd64/bin/javadoc 
@/<>/target/tmp/javadocAll/javadoc.options -J-Xmx1g
Successfully started process 'command 
'/usr/lib/jvm/java-11-openjdk-amd64/bin/javadoc''
javadoc: error - Error fetching URL: http://docs.oracle.com/javase/8/docs/api/
javadoc: error - Error fetching URL: http://docs.oracle.com/javaee/7/api/
javadoc: error - Error fetching URL: 
http://commons.apache.org/proper/commons-cli/javadocs/api-release/
javadoc: error - Error fetching URL: http://junit.org/junit4/javadoc/latest/
javadoc: error - Error fetching URL: http://docs.oracle.com/javaee/6/api/
javadoc: error - Error fetching URL: http://www.antlr2.org/javadoc/

The fix is to replace all links with locally available apis and have the 
package build depend upon the packages that provide these files.


Please consider the proposed fix applied by Ubuntu at:
https://launchpadlibrarian.net/366649973/groovy_2.4.15-1_2.4.15-1ubuntu1.diff.gz

References:
[1] https://bugs.launchpad.net/ubuntu/+source/groovy/+bug/1765885


thanks

-- System Information:
Debian Release: buster/sid
  APT prefers cosmic
  APT policy: (500, 'cosmic'), (400, 'cosmic-proposed')
Architecture: amd64 (x86_64)

Kernel: Linux 4.15.0-20-lowlatency (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#897611: cmake: handle new openjdk versioning

[Tiago Stürmer Daitx]

Package: cmake
Version: 3.11.1-1
Severity: important

Dear Maintainer,

cmake 3.11.1 checks the wrong java version when deciding if javah is
available: instead of "1.10" it should be "10".

The bug was reported upstream at
https://gitlab.kitware.com/cmake/cmake/issues/17938
and fixed at
https://gitlab.kitware.com/cmake/cmake/commit/5482f485b8c3114d258c4cd1a379a6cd12921cb1
Please notice that the above commit includes fixes for cmake's windows
build as well.

Ubuntu has applied a simplified patch:
https://launchpadlibrarian.net/367159256/cmake_3.10.2-1ubuntu1_3.10.2-1ubuntu2.diff.gz

Please consider applying the patch or upgrading cmake to 3.11.2 as soon
as it is released (at least that is the expected version that will
contain the fix, this should be double checked on release).

I set this as important because debian's default-jdk has been updated
to use openjdk-10.

thanks

-- System Information:
Debian Release: buster/sid
  APT prefers cosmic
  APT policy: (500, 'cosmic'), (400, 'cosmic-proposed')
Architecture: amd64 (x86_64)

Kernel: Linux 4.15.0-20-lowlatency (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#896439: gradle-debian-helper points to an invalid java api directory

[Tiago Stürmer Daitx]

Package: gradle-debian-helper
Version: 1.6
Severity: important

Dear Maintainer,

Thus I would like to discuss the possibility of:
1) declaring the binary package gradle-debian-helper as dependend upon
default-jdk-doc;
2) using the directory file:///usr/share/doc/default-jdk-doc/api in
DebianHelperPlugin.java instead of the current default-jdk one.


The reason for this change is that until openjdk-9 the javadoc binary
would ignore invalid javadoc links and at most throw out a warning, but
since openjdk-10 this behavior changed to an error which causes packages
that calls the javadoc binary to FTBFS whenever an invalid, nonexistent,
or unreacheable link is given.


In gradle-debian-helper the file
gradle-helper-plugin/src/main/java/org/debian/gradle/DebianHelperPlugin.java
currently sets the first javadoc link to
file:///usr/share/doc/default-jdk/api 

First, this seems to indicates that the plugin expects that the default-jdk
package will be installed when it's used, but this is not reflected upon
its 'Depends:' (or 'Recommends:').

Second, even if the default-jdk is installed this is problematic because that
directory is actually a relative link to
../openjdk-X-doc/api 
which in turn belongs to an openjdk-X-doc package - such package is not
installed by the default-jdk package. Instead of looking for a default-jdk
directory I proposed that it should instead look for a default-jdk-doc
directory as the api link because the default-jdk-doc package does depends
on an openjdk-X-doc package.


This change shouldn't cause much problem for any packages currently
building with the default-jdk set to openjdk-9 (or 8), since if
/usr/share/doc/default-jdk-doc does not exist then the default-jdk-doc
was not installed anyway and the original link to
/usr/share/doc/default-jdk/api would be invalid anyway and these openjdk
versions ignore that.

Without the proposed changes packages would FTBFS unless both default-jdk
and default-jdk-doc are installed after the default-jdk moves to
openjdk-10 (or 11). Also, packages that depend upon default-jdk-headless
would FTBFS unless they moved to depend upon default-jdk.


Regards,
Tiago

-- System Information:
Debian Release: buster/sid
  APT prefers bionic
  APT policy: (500, 'bionic'), (400, 'bionic-proposed')
Architecture: amd64 (x86_64)

Kernel: Linux 4.15.0-17-lowlatency (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#896436: gradle FTBFS: error fetching java api url when building with openjdk-10

[Tiago Stürmer Daitx]

Package: gradle
Version: 3.4.1-7
Severity: normal

Dear Maintainer,

When using openjdk-10 as the default-jdk gradle will fail with the
following error:

:signing:assemble
:docs:javadocAlljavadoc: error - Error fetching URL: 
file:/usr/share/doc/default-jdk/api/
javadoc: warning - You have not specified the version of HTML to use.

Until openjdk-9 any missing api URLs were considered a warning but from
openjdk-10 upwards this was changed to an error.

The URL is missing because it has been hardcoded in the
subprojects/docs/docs.gradle file as:

def javaApiUrl = "file:///usr/share/doc/default-jdk/api/"

but the path /usr/share/doc/default-jdk is a link that belongs to the
default-jdk package which is not a build dependency of gradle (it is
in fact listed as an alternate dependency of default-jdk-headless).
Still, that is not enough as the default-jdk package does neither
contain nor depend on a package that holds the required api files.
Those files are in the openjdk-X-doc package and the dependency on it
is done through default-jdk-doc.

gradle already build depends on default-jdk-doc and even gradle-doc has
a dependency on it. By changing the javaApiUrl to point to the right api
directory, as in:

def javaApiUrl = "file:///usr/share/doc/default-jdk-doc/api/"

the build works as expected.

The patch debian/patches/use-local-artifacts.patch should be updated to
reflect this new patch.

thanks

Tiago

-- System Information:
Debian Release: buster/sid
  APT prefers bionic
  APT policy: (500, 'bionic'), (400, 'bionic-proposed')
Architecture: amd64 (x86_64)

Kernel: Linux 4.15.0-17-lowlatency (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#895619: plexus-compiler: use --release instead of -source/-target for jdk9+ when setting defaults

[Tiago Stürmer Daitx]

Source: plexus-compiler
Version: 2.8.2-5
Severity: normal

Dear Maintainer,

plexus-compiler currently will default -source and/or -target to 1.7
whenever the following occours:
1) whenever either has not being set
2) whenever either has been set to 1.6 or earlier

This patch modifies the detection logic in order to be able to set the
'--release' flag when (and only when):
- the '--release' is *not* set
- AND both -source and -target are being set to a default value
- AND the running jvm is jdk9 or newer

This prevents errors such as the infamous "Method
flip()Ljava/nio/ByteBuffer; does not exist in class java.nio.ByteBuffer"
that is caused by building with openjdk-9 with -source set without
setting the proper bootclasspath [1,2]. JEP-247 [3] has provided the
--release to prevent such issues and should be used instead of -source
whenever the javac being used is jdk9 or higher.


I have tested and I can confirm it works fine, but I would like some
review to make sure it is sane and get opinions on other (better?) ways
to do this - specially concerning the detection of the jvm being run.

Also, fork and an alternative javac compiler might be set, thus I would
like to discuss as to what behavior it should default it in that case.

Regards,
Tiago Daitx

References:
[1] https://bugs.launchpad.net/ubuntu/+source/gradle/+bug/1760359
[2] https://github.com/plasma-umass/doppio/issues/497
[3] http://openjdk.java.net/jeps/247


-- System Information:
Debian Release: buster/sid
  APT prefers bionic
  APT policy: (500, 'bionic'), (400, 'bionic-proposed')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.15.0-13-generic (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#895616: gradle: fix support for openjdk-9 --release flag

[Tiago Stürmer Daitx]

Source: gradle
Version: 3.4.1-7
Severity: normal

Dear Maintainer,

gradle 3.4.1 still detects and relies on the '-release' compiler
argument, but newer openjdk-9 has moved to a '--release' gnu-style
argument.

Upstream has fixed that on commit
https://github.com/gradle/gradle/commit/142f2f5233e77ba33146efe3815cd3b4b1245993

Please consider applying the patch. A debdiff will follow shortly (need
the bug # for the DEP-3 header).

thanks

-- System Information:
Debian Release: buster/sid
  APT prefers bionic
  APT policy: (500, 'bionic'), (400, 'bionic-proposed')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.15.0-13-generic (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#895587: openjdk-10: exclude element-list from being compressed

[Tiago Stürmer Daitx]

Package: openjdk-10
Version: 10~46-5
Severity: important

Dear Maintainer,

The file element-list has replaced package-list in the javadoc api
directory is now used by the javadoc binary. As it is not currently
excluded when calling dh_compress it will be gzip and that causes
javadoc to fail to recognize the /usr/share/doc/openjdk-10-jre-headless/api/
directory. This causes quite a few packages to FTBFS, the most proeminent
being gradle and groovy.

thanks

-- System Information:
Debian Release: buster/sid
  APT prefers bionic
  APT policy: (500, 'bionic'), (400, 'bionic-proposed')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.15.0-13-generic (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#895583: libcommons-lang3-java FTBFS due to unsupported locale type

[Tiago Stürmer Daitx]

Package: libcommons-lang3-java
Version: 3.5-1
Severity: normal

Dear Maintainer,

With bug #895234 [1] fixed, libcommons-lang3-java will FTBFS as bellow:

[INFO] Running org.apache.commons.lang3.LocaleUtilsTest
[ERROR] Tests run: 15, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.007 
s <<< FAILURE! - in org.apache.commons.lang3.LocaleUtilsTest
[ERROR] testParseAllLocales(org.apache.commons.lang3.LocaleUtilsTest)  Time 
elapsed: 0.004 s  <<< ERROR!
java.lang.IllegalArgumentException: Invalid locale format: ji_001
at 
org.apache.commons.lang3.LocaleUtilsTest.testParseAllLocales(LocaleUtilsTest.java:578)

Which has been fixed upstream by LANG-1312 [2]. The patch provided in
the bug report applies cleanly.

A debdiff will be provided shortly.


References:
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895234
[2] https://issues.apache.org/jira/browse/LANG-1312

-- System Information:
Debian Release: buster/sid
  APT prefers bionic
  APT policy: (500, 'bionic'), (400, 'bionic-proposed')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.15.0-13-generic (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libcommons-lang3-java depends on:
ii  libcommons-parent-java  43-1

libcommons-lang3-java recommends no packages.

Versions of packages libcommons-lang3-java suggests:
pn  libcommons-lang3-java-doc  

-- no debconf information

Bug#893739: gettext: FTBFS with openjdk-9 as default-jdk

[Tiago Stürmer Daitx]

Package: gettext
Version: 0.19.8-2
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***

Content-Type: multipart/mixed; boundary="===3187527196013602937=="
MIME-Version: 1.0
From: =?utf-8?q?Tiago_St=C3=BCrmer_Daitx?= 
To: Debian Bug Tracking System 
Subject: gettext: FTBFS with openjdk 9 as default-jdk
Message-ID: <152167117225.13763.14111882470295268469.reportbug@tdaitx-P65>
X-Mailer: reportbug 7.1.8ubuntu1
Date: Wed, 21 Mar 2018 23:26:12 +0100
X-Debbugs-Cc: tiago.da...@canonical.com

This is a multi-part MIME message sent by reportbug.


--===3187527196013602937==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Package: gettext
Version: 0.19.8-2
Severity: important

Dear Maintainer,

Currently gettext FTBFS when building with openjdk-9 due to:

cp: cannot stat 'debian/tmp/usr/share/gettext/libintl.jar': No such file or 
directory

which in turn is caused by a configure failing to detect openjdk:

checking for Java virtual machine... java
configure: WARNING: unknown target-version 9, please update gt_JAVACOMP macro
checking for Java compiler... no


For comparison, the above message, when compiling with OpenJDK 8 is:
checking for Java virtual machine... java
configure: WARNING: unknown target-version 1.8, please update gt_JAVACOMP macro
checking for Java compiler... /usr/lib/jvm/default-java/bin/javac -target 1.1 
-source 1.3


The attached debdiff, copied from opensuse and modified to include
support for source/target 1.7 and 1.8, fixes this issue.

The configure message, with the patch applied, is:
checking for Java virtual machine... java
configure: WARNING: unknown target-version 9, please update gt_JAVACOMP macro
checking for Java compiler... no


Please consider applying it to enable the work for transitioning
default-jdk from openjdk-8 to openjdk-9.

thanks
Tiago Daitx

-- System Information:
Debian Release: buster/sid
  APT prefers bionic
  APT policy: (500, 'bionic'), (400, 'bionic-proposed')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.15.0-10-generic (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

--===3187527196013602937==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: attachment; 
filename="gettext_0.19.8-1_debdiff_0.19.8-2.patch"

ZGlmZiAtTnJ1IGdldHRleHQtMC4xOS44LjEvZGViaWFuL2NoYW5nZWxvZyBnZXR0ZXh0LTAuMTku
OC4xL2RlYmlhbi9jaGFuZ2Vsb2cKLS0tIGdldHRleHQtMC4xOS44LjEvZGViaWFuL2NoYW5nZWxv
ZwkyMDE4LTAzLTA0IDA5OjI0OjA1LjAwMDAwMDAwMCArMDEwMAorKysgZ2V0dGV4dC0wLjE5Ljgu
MS9kZWJpYW4vY2hhbmdlbG9nCTIwMTgtMDMtMjAgMTk6NDc6MTkuMDAwMDAwMDAwICswMTAwCkBA
IC0xLDMgKzEsMTAgQEAKK2dldHRleHQgKDAuMTkuOC4xLTR1YnVudHU1fjAyKSBVTlJFTEVBU0VE
OyB1cmdlbmN5PW1lZGl1bQorCisgICogZC9wLzA0LWVuYWJsZS1qZGs5LWNvbXBhdGliaWxpdHku
cGF0Y2g6IGVuYWJsZSBidWlsZGluZyB3aXRoCisgICAgc291cmNlIGFuZCB0YXJnZXQgZmxhZ3Mg
c2V0IHRvIDEuODsgdXBkYXRlIGd0X0pBVkFDT01QIG1hY3JvLgorCisgLS0gVGlhZ28gU3TDvHJt
ZXIgRGFpdHggPHRpYWdvLmRhaXR4QHVidW50dS5jb20+ICBUdWUsIDIwIE1hciAyMDE4IDE4OjQ3
OjE5ICswMDAwCisKZ2V0dGV4dCAoMC4xOS44LjEtNCkgdW5zdGFibGU7IHVyZ2VuY3k9bWVkaXVt
CgogICogQXZvaWQgZXh0cmFuZW91cyBOVUwgYnl0ZXMgaW4gLm1vIGZpbGVzLiBDbG9zZXM6ICM4
NzI4NjkuCmRpZmYgLU5ydSBnZXR0ZXh0LTAuMTkuOC4xL2RlYmlhbi9wYXRjaGVzLzA0LWVuYWJs
ZS1qZGs5LWNvbXBhdGliaWxpdHkucGF0Y2ggZ2V0dGV4dC0wLjE5LjguMS9kZWJpYW4vcGF0Y2hl
cy8wNC1lbmFibGUtamRrOS1jb21wYXRpYmlsaXR5LnBhdGNoCi0tLSBnZXR0ZXh0LTAuMTkuOC4x
L2RlYmlhbi9wYXRjaGVzLzA0LWVuYWJsZS1qZGs5LWNvbXBhdGliaWxpdHkucGF0Y2gJMTk3MC0w
MS0wMSAwMTowMDowMC4wMDAwMDAwMDAgKzAxMDAKKysrIGdldHRleHQtMC4xOS44LjEvZGViaWFu
L3BhdGNoZXMvMDQtZW5hYmxlLWpkazktY29tcGF0aWJpbGl0eS5wYXRjaAkyMDE4LTAzLTIwIDE5
OjQ3OjE5LjAwMDAwMDAwMCArMDEwMApAQCAtMCwwICsxLDIzNSBAQAorRGVzY3JpcHRpb246IEVu
YWJsZSBjb21wYXRpYmlsaXR5IHdpdGggSkRLIDkrCisgQWNjb3JkaW5nIHRvIEpFUC0xODIgT3Bl
bkpESyA5IHdpbGwgb25seSBzdXBwb3J0IDEuNiBvciBsYXRlciBmb3Igc291cmNlIGFuZAorIHRh
cmdldCBmbGFncy4gVGhpcyBwYXRjaCBhZGRzIHN1cHBvcnRzIGZvciAxLjYsIDEuNywgYW5kIDEu
OCBmbGFncyBmb3IKKyBkZXRlY3RpbmcgYW5kIGJ1aWxkaW5nIGdldHRleHQgamF2YS4KKyBNb2Rp
ZmllZCBmcm9tIG9wZW5zdXNlIHRvIGluY2x1ZGUgc3VwcG9ydCBmb3IgMS43IGFuZCAxLjguCitP
cmlnaW46IG9wZW5zdXNlLCBodHRwczovL2J1aWxkLm9wZW5zdXNlLm9yZy9wYWNrYWdlL3ZpZXdf
ZmlsZS9vcGVuU1VTRTpGYWN0b3J5L2dldHRleHQtcnVudGltZS9nZXR0ZXh0LTAuMTkuOC4xLWpk
azkucGF0Y2gKK0J1Zy1EZWJpYW46IAorRm9yd2FyZGVkOiBubworTGFzdC1VcGRhdGU6IDIwMTgt

Bug#893487: gradle FTBFS due to missing cast "as long"

[Tiago Stürmer Daitx]

Package: gradle
Version: 3.4.1-2
Followup-For: Bug #893487

Dear Maintainer,

please consider the attached debdiff for a suggested fix.

thanks

Tiago Daitx

-- System Information:
Debian Release: buster/sid
  APT prefers bionic
  APT policy: (500, 'bionic'), (400, 'bionic-proposed')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.15.0-10-generic (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru gradle-3.4.1/debian/changelog gradle-3.4.1/debian/changelog
--- gradle-3.4.1/debian/changelog   2017-11-29 16:09:02.0 +0100
+++ gradle-3.4.1/debian/changelog   2018-03-19 12:19:49.0 +0100
@@ -1,3 +1,10 @@
+gradle (3.4.1-3) UNRELEASED; urgency=medium
+
+  * d/p/cast-estimated-runtime-to-long.patch: fix FTBFS due to missing cast.
+(Closes: #893487)
+
+ -- Tiago Stürmer Daitx <tiago.da...@ubuntu.com>  Mon, 19 Mar 2018 11:19:49 
+
+
 gradle (3.4.1-2) experimental; urgency=medium
 
   * Team upload.
diff -Nru gradle-3.4.1/debian/patches/cast-estimated-runtime-to-long.patch 
gradle-3.4.1/debian/patches/cast-estimated-runtime-to-long.patch
--- gradle-3.4.1/debian/patches/cast-estimated-runtime-to-long.patch
1970-01-01 01:00:00.0 +0100
+++ gradle-3.4.1/debian/patches/cast-estimated-runtime-to-long.patch
2018-03-19 12:15:47.0 +0100
@@ -0,0 +1,22 @@
+Description: gradle 3.4.1 FTBFS with a missing cast to long
+ estimatedRuntime must be cast to long otherwise gradle 3.4.1 FTBFS with
+ buildSrc/src/main/groovy/org/gradle/testing/DistributedPerformanceTest.groovy:
+ 134: [Static type checking] - Cannot assign value of type java.math.BigDecimal
+ to variable of type long.
+Author: Tiago Stürmer Daitx <tiago.da...@ubuntu.com>
+Bug-Debian: https://bugs.debian.org/893487
+Forwarded: no
+Last-Update: 2018-03-19
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- 
a/buildSrc/src/main/groovy/org/gradle/testing/DistributedPerformanceTest.groovy
 
b/buildSrc/src/main/groovy/org/gradle/testing/DistributedPerformanceTest.groovy
+@@ -131,7 +131,7 @@ class DistributedPerformanceTest extends
+ def scenarios = scenarioList.readLines()
+ .collect { line ->
+ def parts = Splitter.on(';').split(line).toList()
+-new Scenario(id : parts[0], estimatedRuntime: new 
BigDecimal(parts[1]), templates: parts.subList(2, parts.size()))
++new Scenario(id : parts[0], estimatedRuntime: new 
BigDecimal(parts[1]) as long, templates: parts.subList(2, parts.size()))
+ }
+ .sort{ -it.estimatedRuntime }
+ 
diff -Nru gradle-3.4.1/debian/patches/series gradle-3.4.1/debian/patches/series
--- gradle-3.4.1/debian/patches/series  2017-11-29 16:07:56.0 +0100
+++ gradle-3.4.1/debian/patches/series  2018-03-19 11:55:59.0 +0100
@@ -23,3 +23,4 @@
 use-local-artifacts.patch
 jansi.patch
 commons-io.patch
+cast-estimated-runtime-to-long.patch

Bug#893487: gradle FTBFS due to missing cast "as long"

[Tiago Stürmer Daitx]

Package: gradle
Version: 3.4.1-2
Severity: normal

Dear Maintainer,

gradle 3.4.1-2 FTBFS due to a missing cast, as per build log:


:compileJava - is not incremental (e.g. outputs have changed, no previous 
execution, etc.).
Note: /<>/buildSrc/src/main/java/WriteProperties.java uses or 
overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
:buildSrc:compileGroovywarning: Implicitly compiled files were not subject to 
annotation processing.
  Use -proc:none to disable annotation processing or -implicit to specify a 
policy for implicit compilation.
1 warning
startup failed:
/<>/buildSrc/src/main/groovy/org/gradle/testing/DistributedPerformanceTest.groovy:
 134: [Static type checking] - Cannot assign value of type java.math.BigDecimal 
to variable of type long
 @ line 134, column 61.
   d : parts[0], estimatedRuntime: new BigD
 ^

1 error

 FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':compileGroovy'.
> Compilation failed; see the compiler error output for details.

* Try:
Run with --info or --debug option to get more log output.

* Exception is:
org.gradle.api.tasks.TaskExecutionException: Execution failed for task 
':compileGroovy'.
at 
org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:84)
at 
org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:55)
at 
org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter.execute(SkipUpToDateTaskExecuter.java:61)
at 
org.gradle.api.internal.tasks.execution.ValidatingTaskExecuter.execute(ValidatingTaskExecuter.java:58)
at 
org.gradle.api.internal.tasks.execution.SkipEmptySourceFilesTaskExecuter.execute(SkipEmptySourceFilesTaskExecuter.java:88)
at 
org.gradle.api.internal.tasks.execution.ResolveTaskArtifactStateTaskExecuter.execute(ResolveTaskArtifactStateTaskExecuter.java:45)
at 
org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:51)
at 
org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:54)
at 
org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter.execute(ExecuteAtMostOnceTaskExecuter.java:43)
at 
org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:34)
at 
org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:233)
at 
org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:215)
at 
org.gradle.execution.taskgraph.AbstractTaskPlanExecutor$TaskExecutorWorker.processTask(AbstractTaskPlanExecutor.java:74)
at 
org.gradle.execution.taskgraph.AbstractTaskPlanExecutor$TaskExecutorWorker.run(AbstractTaskPlanExecutor.java:55)
at 
org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:54)
at 
org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:40)
Caused by: org.gradle.api.internal.tasks.compile.CompilationFailedException: 
Compilation failed; see the compiler error output for details.
at 
org.gradle.api.internal.tasks.compile.ApiGroovyCompiler.execute(ApiGroovyCompiler.java:179)
at 
org.gradle.api.internal.tasks.compile.ApiGroovyCompiler.execute(ApiGroovyCompiler.java:60)
at 
org.gradle.api.internal.tasks.compile.daemon.CompilerDaemonServer.execute(CompilerDaemonServer.java:31)
at 
org.gradle.process.internal.worker.request.WorkerAction.run(WorkerAction.java:87)
at 
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:35)
at 
org.gradle.internal.dispatch.ReflectionDispatch.dispatch(ReflectionDispatch.java:24)
at 
org.gradle.internal.remote.internal.hub.MessageHub$Handler.run(MessageHub.java:377)
... 2 more


BUILD FAILED

Total time: 45.972 secs
debian/rules:39: recipe for target 'override_dh_auto_build' failed


thanks

Tiago Daitx


-- System Information:
Debian Release: buster/sid
  APT prefers bionic
  APT policy: (500, 'bionic'), (400, 'bionic-proposed')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.15.0-10-generic (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#892937: cglib: FTBFS with openjdk-9 due to failing tests

[Tiago Stürmer Daitx]

Source: cglib
Version: 3.2.6-1
Severity: normal

Dear Maintainer,

When building with openjdk-9, for which there will be hopefully a
transition soon.

There are currently 5 tests that fail (setting 'nocheck' in
DEB_BUILD_OPTIONS allow the build to succeed).


[ERROR] Tests run: 51, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.821 
s <<< FAILURE! - in net.sf.cglib.proxy.TestEnhancer
[ERROR] testSql(net.sf.cglib.proxy.TestEnhancer)  Time elapsed: 0.021 s  <<< 
ERROR!
net.sf.cglib.core.CodeGenerationException: 
java.lang.reflect.InvocationTargetException-->null
at net.sf.cglib.proxy.TestEnhancer.testSql(TestEnhancer.java:819)
Caused by: java.lang.reflect.InvocationTargetException
at net.sf.cglib.proxy.TestEnhancer.testSql(TestEnhancer.java:819)
Caused by: java.lang.NoClassDefFoundError: net/sf/cglib/proxy/Factory
at net.sf.cglib.proxy.TestEnhancer.testSql(TestEnhancer.java:819)
Caused by: java.lang.ClassNotFoundException: net.sf.cglib.proxy.Factory
at net.sf.cglib.proxy.TestEnhancer.testSql(TestEnhancer.java:819)


[ERROR] Tests run: 12, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.024 
s <<< FAILURE! - in net.sf.cglib.reflect.TestFastClass
[ERROR] 
testPackagePrivateMethod_bootstrapClassLoader(net.sf.cglib.reflect.TestFastClass)
  Time elapsed: 0 s  <<< ERROR!
java.lang.NoSuchMethodException: java.lang.String.getChars([C, int)
at 
net.sf.cglib.reflect.TestFastClass.testPackagePrivateMethod_bootstrapClassLoader(TestFastClass.java:663)


[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.007 s 
<<< FAILURE! - in net.sf.cglib.transform.impl.TestDemo
[ERROR] test(net.sf.cglib.transform.impl.TestDemo)  Time elapsed: 0.007 s  <<< 
ERROR!
java.lang.IllegalAccessError: Update to static final field 
net.sf.cglib.transform.impl.TransformDemo.CGLIB$FIELD_NAMES attempted from a 
different method (CGLIB$STATICHOOK77) than the initializer method 
at net.sf.cglib.transform.impl.TestDemo.test(TestDemo.java:19)


[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.004 s 
<<< FAILURE! - in net.sf.cglib.transform.impl.TestProvideFields
[ERROR] initializationError(net.sf.cglib.transform.impl.TestProvideFields)  
Time elapsed: 0 s  <<< ERROR!
java.lang.IllegalAccessError: Update to static final field 
net.sf.cglib.transform.AbstractTransformTest.CGLIB$FIELD_NAMES attempted from a 
different method (CGLIB$STATICHOOK82) than the initializer method 
at 
net.sf.cglib.transform.impl.TestProvideFields.suite(TestProvideFields.java:69)


[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.022 s 
<<< FAILURE! - in net.sf.cglib.TestAll
[ERROR] initializationError(net.sf.cglib.TestAll)  Time elapsed: 0 s  <<< ERROR!
java.lang.IllegalAccessError: Update to static final field 
net.sf.cglib.transform.AbstractTransformTest.CGLIB$FIELD_NAMES attempted from a 
different method (CGLIB$STATICHOOK108) than the initializer method 
at net.sf.cglib.TestAll.suite(TestAll.java:81)




The summary says:
[INFO] Results:
[INFO]
[ERROR] Errors:
[ERROR]   TestAll.suite:81 ? IllegalAccess Update to static final field 
net.sf.cglib.tra...
[ERROR]   TestEnhancer.testSql:819 ? CodeGeneration 
java.lang.reflect.InvocationTargetEx...
[ERROR]   TestFastClass.testPackagePrivateMethod_bootstrapClassLoader:663 ? 
NoSuchMethod
[ERROR]   TestDemo.test:19 ? IllegalAccess Update to static final field 
net.sf.cglib.tra...
[ERROR]   
TestProvideFields.suite:69->AbstractTransformTest.:-1->AbstractTransformTest.CGLIB$STATICHOOK82:-1
 ? IllegalAccess
[INFO]
[ERROR] Tests run: 156, Failures: 0, Errors: 5, Skipped: 0




I reported these failures upstream at https://github.com/cglib/cglib/issues/119

thanks
Tiago Daitx


-- System Information:
Debian Release: buster/sid
  APT prefers bionic
  APT policy: (500, 'bionic'), (400, 'bionic-proposed')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.15.0-10-generic (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Bug#891893: jtb: groupId change in jtb-1.4.12-1 causes other packages to FTBFS

[Tiago Stürmer Daitx]

Package: jtb
Version: 1.4.12-1
Severity: important

Dear Maintainer,

As per bug #887785 various packages were affected by jtb-1.4.12-1. I
tracked the issue down to a groupId change after the pom was updated
from upstream.

The pom.xml groupId changed from "edu.ucla.cs.compilers" (original
pom.xml [1]) to "edu.purdue.cs" (new pom.xml [2]).

Adding a relocation to debian/jtb.poms fixes the FTBFS in the affected
packages (tested on surefire, javacc-maven-plugin, hawtbuf, avro-java,
and activemq-protobuf).

Please see the attached debdiff for a suggested fix. You might want to
change the relocate version.

Regards,
Tiago

[1] 
https://anonscm.debian.org/cgit/collab-maint/jtb.git/tree/debian/pom.xml?id=cffddde94d57ef60f7415f8c8d400a75ba4c0f30
[2] 
https://anonscm.debian.org/cgit/collab-maint/jtb.git/tree/pom.xml?id=19bafc71af2bdb92a0abe47b01a0aa8504945cab

-- System Information:
Debian Release: buster/sid
  APT prefers bionic
  APT policy: (500, 'bionic'), (400, 'bionic-proposed')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.13.0-32-generic (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages jtb depends on:
ii  default-jre [java8-runtime] 2:1.8-59ubuntu1
pn  jarwrapper  
ii  openjdk-10-jre [java9-runtime]  10~32-0ubuntu1
ii  openjdk-8-jre [java8-runtime]   8u151-b12-1
ii  openjdk-9-jre [java9-runtime]   9.0.1+11-1

jtb recommends no packages.

jtb suggests no packages.

Bug#853335: bogl: ftbfs with GCC-7

[Tiago Stürmer Daitx]

Dear maintainer,

Please consider the attached debdiff to fix the FTBFS on a gcc-7 rebuild.

The fix is the same used for pinfo in bug #853613, that is, remove the
"inline" word from the function.

thanks
diff -u bogl-0.1.18/debian/changelog bogl-0.1.18/debian/changelog
--- bogl-0.1.18/debian/changelog
+++ bogl-0.1.18/debian/changelog
@@ -1,3 +1,10 @@
+bogl (0.1.18-12) UNRELEASED; urgency=medium
+
+  * reduce-font.c: Get rid of inlined function, which breaks buildling
+with gcc7 (Closes: #853335).
+
+ -- Tiago Stürmer Daitx <tiago.da...@ubuntu.com>  Thu, 05 Oct 2017 19:39:45 +
+
 bogl (0.1.18-11) unstable; urgency=medium
 
   * compat: Bump to 9.
diff -u bogl-0.1.18/reduce-font.c bogl-0.1.18/reduce-font.c
--- bogl-0.1.18/reduce-font.c
+++ bogl-0.1.18/reduce-font.c
@@ -17,7 +17,7 @@
 printf ("usage: reduce-font  < text\n");
 }
 
-inline size_t
+size_t
 bits (u_int32_t x)
 {
 size_t r;

Bug#874434: severity is grave

[Tiago Stürmer Daitx]

Resending it with a .patch extension so hopefully BTS will identify it
as an actual text/plain file.

On Thu, 28 Sep 2017 15:18:20 -0700
=?UTF-8?Q?Tiago_St=C3=BCrmer_Daitx?= <tda...@gmail.com> wrote:
> Please consider removing the jvm.cfg checks. OpenJDK 7, 8, and 9 have
> been shipping a default jvm.cfg for quite some time now and it is used
> when a jvm.cfg is not present in the /etc/ directory.
>
> Patch is attached.
>
>
> thanks
diff -Nru ca-certificates-java-20170531+nmu1/debian/changelog ca-certificates-java-20170531+nmu1.1/debian/changelog
--- ca-certificates-java-20170531+nmu1/debian/changelog	2017-06-15 11:33:00.0 -0400
+++ ca-certificates-java-20170531+nmu1.1/debian/changelog	2017-09-28 16:54:50.0 -0400
@@ -1,3 +1,11 @@
+ca-certificates-java (20170531+nmu1.1) UNRELEASED; urgency=medium
+
+  * Remove jvm.cfg temporary generation as openjdk-8 already ships with a
+default jvm.cfg for cases wihere the one in /etc is missing or not yet
+setup. Closes: #874434. 
+
+ -- Tiago Stürmer Daitx <tiago.da...@ubuntu.com>  Thu, 28 Sep 2017 20:54:50 +
+
 ca-certificates-java (20170531+nmu1) unstable; urgency=high
 
   * Non-maintainer upload.
diff -Nru ca-certificates-java-20170531+nmu1/debian/jks-keystore.hook.in ca-certificates-java-20170531+nmu1.1/debian/jks-keystore.hook.in
--- ca-certificates-java-20170531+nmu1/debian/jks-keystore.hook.in	2017-05-31 08:39:26.0 -0400
+++ ca-certificates-java-20170531+nmu1.1/debian/jks-keystore.hook.in	2017-09-28 10:44:15.0 -0400
@@ -48,14 +48,6 @@
 export JAVA_HOME=/usr/lib/jvm/$jvm
 PATH=$JAVA_HOME/bin:$PATH
 
-temp_jvm_cfg=
-if [ ! -f /etc/${jvm%-$arch}/jvm-$arch.cfg ]; then
-# the jre is not yet configured, but jvm.cfg is needed to run it
-temp_jvm_cfg=/etc/${jvm%-$arch}/jvm-$arch.cfg
-mkdir -p /etc/${jvm%-$arch}
-printf -- "-server KNOWN\n" > $temp_jvm_cfg
-fi
-
 if dpkg-query --version >/dev/null; then
 nsspkg=$(dpkg-query -L "$(nsslib_name)" | sed -n 's,\(.*\)/libnss3\.so$,\1,p'|head -n 1)
 nsscfg=/etc/${jvm%-$arch}/security/nss.cfg
@@ -71,7 +63,6 @@
 
 do_cleanup()
 {
-[ -z "$temp_jvm_cfg" ] || rm -f $temp_jvm_cfg
 if [ -n "$nsspkg" ] && [ -n "$nssjdk" ] && [ "$nsspkg" != "$nssjdk" ]
 then
 rm -f $nssjdk/libnss3.so
diff -Nru ca-certificates-java-20170531+nmu1/debian/postinst.in ca-certificates-java-20170531+nmu1.1/debian/postinst.in
--- ca-certificates-java-20170531+nmu1/debian/postinst.in	2017-05-31 08:39:26.0 -0400
+++ ca-certificates-java-20170531+nmu1.1/debian/postinst.in	2017-09-28 10:43:16.0 -0400
@@ -72,7 +72,6 @@
 
 do_cleanup()
 {
-[ -z "$temp_jvm_cfg" ] || rm -f $temp_jvm_cfg
 if [ -n "$nsspkg" ] && [ -n "$nssjdk" ] && [ "$nsspkg" != "$nssjdk" ]
 then
 rm -f $nssjdk/libnss3.so
@@ -95,14 +94,6 @@
 exit 1
 fi
 
-temp_jvm_cfg=
-if [ ! -f /etc/${jvm%-$arch}/jvm-$arch.cfg ]; then
-# the jre is not yet configured, but jvm.cfg is needed to run it
-temp_jvm_cfg=/etc/${jvm%-$arch}/jvm-$arch.cfg
-mkdir -p /etc/${jvm%-$arch}
-printf -- "-server KNOWN\n" > $temp_jvm_cfg
-fi
-
 trap do_cleanup EXIT
 first_install
 fi

Bug#874434: severity is grave

[Tiago Stürmer Daitx]

Please consider removing the jvm.cfg checks. OpenJDK 7, 8, and 9 have
been shipping a default jvm.cfg for quite some time now and it is used
when a jvm.cfg is not present in the /etc/ directory.

Patch is attached.


thanks


ca-certificates-java_20170531+nmu1_20170531+nmu1.1.debdiff
Description: Binary data

Bug#796802: Bug 762449 fix lost in 2.0.10-1

[Tiago Stürmer Daitx]

I have prepared a patch based on Uwe Kleine-König's proposal that
fixes the arm build.

thanks

diff -Nru numactl-2.0.11/debian/changelog numactl-2.0.11/debian/changelog
--- numactl-2.0.11/debian/changelog2016-12-21 18:27:02.0 +
+++ numactl-2.0.11/debian/changelog2017-08-17 22:16:39.0 +
@@ -1,3 +1,13 @@
+numactl (2.0.11-2.2) UNRELEASED; urgency=medium
+
+  * syscall.c:
+- add __arm__ to avoid failure due to missing syscalls.
+- return -1 and set errno to ENOSYS on migrate_pages function
+  if __NR_migrate_pages is undefined, thanks Uwe Kleine-König
+  for the initial patch. Closes: #796802. LP: #1711478.
+
+ -- Tiago Stürmer Daitx <tiago.da...@ubuntu.com>  Thu, 17 Aug 2017
22:16:39 +
+
 numactl (2.0.11-2.1) unstable; urgency=medium

   * Non-maintainer upload.
diff -Nru numactl-2.0.11/debian/patches/fix-arm-nr-missing-pages.patch
numactl-2.0.11/debian/patches/fix-arm-nr-missing-pages.patch
--- numactl-2.0.11/debian/patches/fix-arm-nr-missing-pages.patch
1970-01-01 00:00:00.0 +
+++ numactl-2.0.11/debian/patches/fix-arm-nr-missing-pages.patch
2017-08-17 22:16:39.0 +
@@ -0,0 +1,43 @@
+Description: allow __arm__ to pass syscall check even without migrate_pages
+ numactl build fails on arm because arm does not define __NR_migrate_pages.
+ In order to build it on arm the arch must be added to the syscalls check
+ and the migrate_pages must return with -1 and set errno to ENOSYS.
+ .
+ This patch is based on Uwe Kleine-König's suggestion at
+ https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796802#15
+Author: Tiago Stürmer Daitx <tiago.da...@ubuntu.com>
+Origin: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796802#15
+Bug-Debian: https://bugs.debian.org/796802
+Bug-Ubuntu: https://launchpad.net/bugs/1711478
+Last-Update: 2017-08-17
+
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+
+--- a/syscall.c
 b/syscall.c
+@@ -109,6 +109,10 @@
+
+ #define __NR_migrate_pages272
+
++#elif defined(__arm__)
++// arm does not define __NR_migrate_pages
++// ignore that and continue (Debian #796802)
++
+ #elif !defined(DEPS_RUN)
+ #error "Add syscalls for your architecture or update kernel headers"
+ #endif
+@@ -206,7 +210,13 @@ long WEAK set_mempolicy(int mode, const
+ long WEAK migrate_pages(int pid, unsigned long maxnode,
+ const unsigned long *frommask, const unsigned long *tomask)
+ {
++#if defined(__NR_migrate_pages)
+ return syscall(__NR_migrate_pages, pid, maxnode, frommask, tomask);
++#else
++// See Debian #796802
++errno = ENOSYS;
++return -1;
++#endif
+ }
+
+ long WEAK move_pages(int pid, unsigned long count,
diff -Nru numactl-2.0.11/debian/patches/series
numactl-2.0.11/debian/patches/series
--- numactl-2.0.11/debian/patches/series1970-01-01 00:00:00.0 +
+++ numactl-2.0.11/debian/patches/series2017-08-17 22:16:39.0 +
@@ -0,0 +1 @@
+fix-arm-nr-missing-pages.patch


numactl_2.0.11-2.1_2.0.11-2.2.debdif
Description: Binary data

Bug#853531: reassigning bug to gcc

[Tiago Stürmer Daitx]

This has been fixed upstream [1], but there has been no new release so far.

[1] https://github.com/lxc/lxc/commit/66b66624fce21606d11f24f5b615776074d212ae

-thanks

Bug#865579: libqmi 1.18.0-1 FTBFS when building against glib2.0-2.53.1-1 (or later)

[Tiago Stürmer Daitx]

Source: libqmi
Followup-For: Bug #865579

Dear Maintainer,

Please consider the attached patch to fix libqmi builds when build against 
glib2.0-2.53.1-1 or later.

Thanks!

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

Kernel: Linux 4.10.0-21-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Description: utils: drop useless g_file_test() call
 canonicalize_file_name() returns NULL if file doesn't
 exist, so no need to check file existence with
 g_file_test().

 Without this patch calls to this function (as in the
 test-generated tests) will fail on glib2.0 v2.53+ 
 due to a NULL check introduced in g_file_test. The
 NULL check introduction was tracked at:
 https://bugzilla.gnome.org/show_bug.cgi?id=755046
Author: Mikhail Efremov 
Origin: 
https://cgit.freedesktop.org/libqmi/commit/src/libqmi-glib/qmi-utils.c?id=07da0340043b3b4d3ffc005e0a10b4776157a0fe
Bug-Debian: https://bugs.debian.org/865579
Bug-Ubuntu: https://launchpad.net/bugs/1699599
Forwarded: not-needed
Applied-Upstream: 07da0340043b3b4d3ffc005e0a10b4776157a0fe
Last-Update: 2017-06-22
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
--- a/src/libqmi-glib/qmi-utils.c
+++ b/src/libqmi-glib/qmi-utils.c
@@ -743,8 +743,10 @@ __qmi_utils_get_driver (const gchar *cdc
 path = canonicalize_file_name (tmp);
 g_free (tmp);
 
-if (g_file_test (path, G_FILE_TEST_EXISTS))
-driver = g_path_get_basename (path);
+if (!path)
+continue;
+
+driver = g_path_get_basename (path);
 g_free (path);
 }
 

Bug#865579: libqmi 1.18.0-1 FTBFS when building against glib2.0-2.53.1-1 (or later)

[Tiago Stürmer Daitx]

Package: libqmi
Version: 1.18.0-1
Severity: normal

Dear Maintainer,

libqmi 1.18.0-1 introduced a new function called __qmi_utils_get_driver in 
qmi-utils.c, which in turn calls g_file_test. This ends up being called during 
the test setup for test-generated suite.

The problem is that g_file_test might receive a NULL path and glib2 version 
2.53 (or later) introduced a non-NULL assert on it, causing the test setup to 
fail with:
GLib-CRITICAL **: g_file_test: assertion 'filename != NULL' failed.

Upstream has already fixed it in commit 
07da0340043b3b4d3ffc005e0a10b4776157a0fe [1], althoghno mention is made to the 
failed test it works just as well.

[1] 
https://cgit.freedesktop.org/libqmi/commit/src/libqmi-glib/qmi-utils.c?id=07da0340043b3b4d3ffc005e0a10b4776157a0fe

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

Kernel: Linux 4.10.0-21-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#857500: cups-pdf: cups library should be set last

[Tiago Stürmer Daitx]

Package: cups-pdf
Version: 3.0.1-2
Severity: normal
Tags: patch

Dear Maintainer,

Please consider applying the attached patch in order to move the cups
library as the last argument during the build. Libraries should be
declared later to adhere to standard POSIX-required behavior. This
early declaration currenly causes cups-pdf to FTBFS on Ubuntu Zesty.


Error from buildlog [1]:
x86_64-linux-gnu-gcc -lcups -o src/cups-pdf src/cups-pdf.c -Wdate-time
-D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security
-Wl,-Bsymbolic-functions -Wl,-z,relro  
/tmp/cc4NNYoz.o: In function `init':
./src/cups-pdf.c:359: undefined reference to `cupsBackendDeviceURI'
/tmp/cc4NNYoz.o: In function `read_config_ppd':
./src/cups-pdf.c:281: undefined reference to `ppdOpenFile'
./src/cups-pdf.c:286: undefined reference to `ppdMarkDefaults'
./src/cups-pdf.c:288: undefined reference to `ppdFirstOption'
./src/cups-pdf.c:291: undefined reference to `ppdNextOption'
./src/cups-pdf.c:293: undefined reference to `ppdClose'
/tmp/cc4NNYoz.o: In function `read_config_options':
./src/cups-pdf.c:304: undefined reference to `cupsParseOptions'
collect2: error: ld returned 1 exit status
debian/rules:20: recipe for target 'override_dh_auto_build-arch' failed
make[1]: *** [override_dh_auto_build-arch] Error 1
make[1]: Leaving directory '/<>'
debian/rules:26: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2


Thanks,
Tiago Daitx

[1] https://launchpad.net/ubuntu/+source/cups-pdf/3.0.1-2


-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial'), (400, 'xenial-proposed'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.8.0-34-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#857424: orthanc-dicomweb: Libraries manually set in wrong order

[Tiago Stürmer Daitx]

Package: orthanc-dicomweb
Version: 0.3+dfsg-1
Severity: normal
Tags: patch

Dear Maintainer,

Similar issue as reported for orthanc-webviewer 2.2-1 in bug #857355.

Currently the file debian/patches/cmake is removing cmake's automatic
library linking resolution and adding "missing" libraries manually,
while also unecessarily modifying a link_libraries call on
Orthanc/Resources/CMake/Compiler.cmake.

The uuid library ends up being added twice while linking
libOrthancWebViewer.so. I verified that this is no longer required.

The libraries are being added through LINK_FLAGS, which is not a good
practice. On make this would be the similar to adding libraries to
LD_FLAGS instead of LD_LIBS, which causes 'undefined reference' errors
when stric order is enabled (like in Ubuntu, where the package FTBFS).

I verified that cmake is able to successfully determine the required
gdcm libraries and that the library arguments in LINK_FLAGS can be
safely removed.

Please see the attached patch for the fix.

Regards,
Tiago Daitx

-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial'), (400, 'xenial-proposed'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.8.0-34-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru orthanc-dicomweb-0.3+dfsg/debian/patches/cmake orthanc-dicomweb-0.3+dfsg/debian/patches/cmake
--- orthanc-dicomweb-0.3+dfsg/debian/patches/cmake	2016-06-29 05:58:36.0 -0300
+++ orthanc-dicomweb-0.3+dfsg/debian/patches/cmake	2017-03-10 15:07:31.0 -0300
@@ -15,13 +15,7 @@
  
  include(${ORTHANC_ROOT}/Resources/CMake/BoostConfiguration.cmake)
  include(${ORTHANC_ROOT}/Resources/CMake/GoogleTestConfiguration.cmake)
-@@ -136,15 +136,13 @@ add_library(OrthancDicomWeb SHARED ${COR
-   ${AUTOGENERATED_SOURCES}
-   )
- 
--target_link_libraries(OrthancDicomWeb ${GDCM_LIBRARIES})
--
- message("Setting the version of the library to ${ORTHANC_DICOM_WEB_VERSION}")
+@@ -142,9 +142,9 @@ add_library(OrthancDicomWeb SHARED ${COR
  
  add_definitions(-DORTHANC_DICOM_WEB_VERSION="${ORTHANC_DICOM_WEB_VERSION}")
  
@@ -30,20 +24,7 @@
 -  SOVERSION ${ORTHANC_DICOM_WEB_VERSION}
 +set_target_properties(OrthancDicomWeb PROPERTIES
 +  NO_SONAME ON
-+  LINK_FLAGS "-lgdcmDICT -lgdcmDSED -lgdcmMSFF -lgdcmCommon -luuid -Wl,-soname,libOrthancDicomWeb.so.${ORTHANC_DICOM_WEB_VERSION}"
++  LINK_FLAGS "-Wl,-soname,libOrthancDicomWeb.so.${ORTHANC_DICOM_WEB_VERSION}"
)
  
  install(
-Index: OrthancDicomWeb-0.3/Orthanc/Resources/CMake/Compiler.cmake
-===
 OrthancDicomWeb-0.3.orig/Orthanc/Resources/CMake/Compiler.cmake
-+++ OrthancDicomWeb-0.3/Orthanc/Resources/CMake/Compiler.cmake
-@@ -60,7 +60,7 @@ if (${CMAKE_SYSTEM_NAME} STREQUAL "Linux
-   # Remove the "-rdynamic" option
-   # http://www.mail-archive.com/cmake@cmake.org/msg08837.html
-   set(CMAKE_SHARED_LIBRARY_LINK_CXX_FLAGS "")
--  link_libraries(uuid pthread rt)
-+  link_libraries(pthread rt)
- 
-   if (NOT ${CMAKE_SYSTEM_NAME} STREQUAL "FreeBSD")
- set(CMAKE_EXE_LINKER_FLAGS "${CMAKE_EXE_LINKER_FLAGS} -Wl,--as-needed")

Bug#857355: orthanc-webviewer: Libraries manually set in wrong order

[Tiago Stürmer Daitx]

Package: orthanc-webviewer
Version: 2.2-1
Severity: normal
Tags: patch

Dear Maintainer,

Currently the file debian/patches/cmake is removing cmake's automatic
library linking resolution and adding "missing" libraries manually.

The uuid library ends up being added twice while linking
libOrthancWebViewer.so. I verified that this is no longer required.

The libraries are being added through LINK_FLAGS, which is not a good
practice. On make this would be the similar to adding libraries to
LD_FLAGS instead of LD_LIBS, which causes 'undefined reference' errors
when stric order is enabled (like in Ubuntu, where the package FTBFS).

I verified that cmake is able to successfully determine the required
gdcm libraries and that the library arguments in LINK_FLAGS can be
safely removed.

Please see the attached patch for the fix.

Regards,
Tiago Daitx

-  

-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial'), (400, 'xenial-proposed'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.8.0-34-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru orthanc-webviewer-2.2/debian/patches/cmake orthanc-webviewer-2.2/debian/patches/cmake
--- orthanc-webviewer-2.2/debian/patches/cmake	2016-06-29 05:31:50.0 -0300
+++ orthanc-webviewer-2.2/debian/patches/cmake	2017-03-10 03:21:43.0 -0300
@@ -15,13 +15,7 @@
  
  
  # Check that the Orthanc SDK headers are available or download them
-@@ -177,15 +177,14 @@ if (STATIC_BUILD OR NOT USE_SYSTEM_GDCM)
-   add_dependencies(OrthancWebViewer GDCM)
- endif()
- 
--target_link_libraries(OrthancWebViewer ${GDCM_LIBRARIES})
--
- message("Setting the version of the library to ${ORTHANC_WEBVIEWER_VERSION}")
+@@ -183,9 +183,10 @@ message("Setting the version of the libr
  
  add_definitions(-DORTHANC_WEBVIEWER_VERSION="${ORTHANC_WEBVIEWER_VERSION}")
  
@@ -30,7 +24,7 @@
 -  SOVERSION ${ORTHANC_WEBVIEWER_VERSION})
 +set_target_properties(OrthancWebViewer PROPERTIES
 +  NO_SONAME ON
-+  LINK_FLAGS "-lgdcmMSFF -luuid -Wl,-soname,libOrthancWebViewer.so.${ORTHANC_WEBVIEWER_VERSION}"
++  LINK_FLAGS "-Wl,-soname,libOrthancWebViewer.so.${ORTHANC_WEBVIEWER_VERSION}"
 +  )
  
  install(

Bug#857003: ncurses: Build x32 packages

[Tiago Stürmer Daitx]

Package: ncurses
Version: 6.0+20161126-1
Severity: wishlist
Tags: patch

Dear Maintainer,

Please consider applying the attached patch to add x32 packages to
ncurses. This patch has been a part of Ubuntu since late 2012 [1].

The original patch [2] has outdated symbols.

Many thanks,
Tiago Daitx

[1] https://launchpad.net/ubuntu/+source/ncurses/5.9-10ubuntu2
[2]
http://launchpadlibrarian.net/123000501/ncurses_5.9-10ubuntu1_5.9-10ubuntu2.diff.gz

-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial'), (400, 'xenial-proposed'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.8.0-34-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru ncurses-6.0+20161126/debian/changelog ncurses-6.0+20161126/debian/changelog
--- ncurses-6.0+20161126/debian/changelog	2016-11-29 18:19:08.0 -0200
+++ ncurses-6.0+20161126/debian/changelog	2017-03-03 22:33:14.0 -0300
@@ -1,3 +1,9 @@
+ncurses (6.0+20161126-2) UNRELEASED; urgency=low
+
+  * Build x32 packages.
+
+ -- Matthias Klose   Wed, 14 Nov 2012 11:07:12 +0100
+
 ncurses (6.0+20161126-1) unstable; urgency=low
 
   * New upstream patchlevel.
diff -Nru ncurses-6.0+20161126/debian/control ncurses-6.0+20161126/debian/control
--- ncurses-6.0+20161126/debian/control	2016-11-28 15:50:38.0 -0200
+++ ncurses-6.0+20161126/debian/control	2016-11-30 02:13:08.0 -0200
@@ -403,3 +403,104 @@
  includes the libraries' man pages.
  .
  Non-developers likely have little use for this package.
+
+Package: libx32ncurses5
+Architecture: amd64 i386
+Priority: optional
+Depends: libx32tinfo5 (= ${binary:Version}),
+ ${shlibs:Depends}, ${misc:Depends}
+Build-Profiles: 
+Description: shared libraries for terminal handling (x32)
+ The ncurses library routines are a terminal-independent method of
+ updating character screens with reasonable optimization.
+ .
+ This package contains the shared libraries necessary to run programs
+ compiled with ncurses.
+ .
+ This package supports the x32 ABI variant of your system's
+ architecure.
+
+Package: libx32ncurses5-dev
+Architecture: amd64 i386
+Section: libdevel
+Priority: optional
+Depends: libx32tinfo5 (= ${binary:Version}), libx32ncurses5 (= ${binary:Version}),
+ libx32tinfo-dev (= ${binary:Version}),
+ libncurses5-dev (= ${binary:Version}), libc6-dev-x32, ${misc:Depends}
+Suggests: ncurses-doc
+Build-Profiles: 
+Description: developer's libraries for ncurses (x32)
+ The ncurses library routines are a terminal-independent method of
+ updating character screens with reasonable optimization.
+ .
+ This package contains the header files, static libraries
+ and symbolic links that developers using ncurses will need.
+ .
+ This package supports the x32 ABI variant of your system's
+ architecure.
+
+Package: libx32ncursesw5
+Architecture: amd64 i386
+Priority: optional
+Depends: libx32tinfo5 (= ${binary:Version}),
+ ${shlibs:Depends}, ${misc:Depends}
+Build-Profiles: 
+Description: shared libraries for terminal handling (wide character support) (x32)
+ The ncurses library routines are a terminal-independent method of
+ updating character screens with reasonable optimization.
+ .
+ This package contains the shared libraries necessary to run programs
+ compiled with ncursesw, which includes support for wide characters.
+ .
+ This package supports the x32 ABI variant of your system's
+ architecure.
+
+Package: libx32ncursesw5-dev
+Architecture: amd64 i386
+Section: libdevel
+Priority: optional
+Depends: libx32tinfo5 (= ${binary:Version}), libx32ncursesw5 (= ${binary:Version}),
+ libx32tinfo-dev (= ${binary:Version}),
+ libncursesw5-dev (= ${binary:Version}), libc6-dev-x32, ${misc:Depends}
+Suggests: ncurses-doc
+Build-Profiles: 
+Description: developer's libraries for ncursesw (x32)
+ The ncurses library routines are a terminal-independent method of
+ updating character screens with reasonable optimization.
+ .
+ This package contains the header files, static libraries
+ and symbolic links that developers using ncursesw will need.
+ .
+ This package includes support for wide characters.
+ This package supports the x32 ABI variant of your system's
+ architecure.
+
+Package: libx32tinfo5
+Architecture: amd64 i386
+Priority: optional
+Depends: ${shlibs:Depends}, ${misc:Depends}
+Build-Profiles: 
+Description: shared low-level terminfo library for terminal handling (x32)
+ The ncurses library routines are a terminal-independent method of
+ updating character screens with reasonable optimization.
+ .
+ This package contains the shared low-level terminfo library.
+ .
+ This package supports the x32 ABI variant of your system's architecure.
+
+Package: libx32tinfo-dev
+Architecture: amd64 i386

Bug#857001: ncurses: Build 32bit packages on s390x

[Tiago Stürmer Daitx]

Package: ncurses
Version: 6.0+20161126-1
Severity: wishlist
Tags: patch

Dear Maintainer,

Please consider applying the attached patch to build 32bit packages on
s390x. This patch has been part of Ubuntu for over a year now [1].

The original patch [2] does not apply cleanly as it assumes x32 support
has also been added.

[1] https://launchpad.net/ubuntu/+source/ncurses/6.0+20151024-2ubuntu2
[2]
http://launchpadlibrarian.net/236280845/ncurses_6.0+20151024-2ubuntu1_6.0+20151024-2ubuntu2.diff.gz

Many thanks,
Tiago Daitx

-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial'), (400, 'xenial-proposed'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.8.0-34-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru ncurses-6.0+20161126/debian/changelog ncurses-6.0+20161126/debian/changelog
--- ncurses-6.0+20161126/debian/changelog	2016-11-29 18:19:08.0 -0200
+++ ncurses-6.0+20161126/debian/changelog	2017-03-03 22:33:14.0 -0300
@@ -1,3 +1,9 @@
+ncurses (6.0+20161126-2) unstable; urgency=medium
+
+  * Build 32bit packages on s390x.
+
+ -- Dimitri John Ledkov   Thu, 04 Feb 2016 15:20:19 +
+
 ncurses (6.0+20161126-1) unstable; urgency=low
 
   * New upstream patchlevel.
diff -Nru ncurses-6.0+20161126/debian/control ncurses-6.0+20161126/debian/control
--- ncurses-6.0+20161126/debian/control	2016-11-28 15:50:38.0 -0200
+++ ncurses-6.0+20161126/debian/control	2016-11-30 02:13:08.0 -0200
@@ -1,7 +1,7 @@
 Maintainer: Craig Small 
 Uploaders: Sven Joachim 
 Build-Depends: debhelper (>= 9.20141010),
dpkg-dev (>= 1.17.14),
-   g++-multilib [amd64 i386 powerpc ppc64 s390 sparc] ,
+   g++-multilib [amd64 i386 powerpc ppc64 s390 s390x sparc] ,
libgpm-dev [linux-any],
pkg-config,
autotools-dev,
@@ -206,7 +208,7 @@
  architecture.
 
 Package: lib32ncurses5
-Architecture: amd64 ppc64
+Architecture: amd64 ppc64 s390x
 Priority: optional
 Depends: lib32tinfo5 (= ${binary:Version}),
  ${shlibs:Depends}, ${misc:Depends}
@@ -223,7 +225,7 @@
  architecture.
 
 Package: lib32ncurses5-dev
-Architecture: amd64 ppc64
+Architecture: amd64 ppc64 s390x
 Section: libdevel
 Priority: optional
 Depends: lib32tinfo5 (= ${binary:Version}), lib32ncurses5 (= ${binary:Version}),
@@ -242,7 +244,7 @@
  architecture.
 
 Package: lib32ncursesw5
-Architecture: amd64 ppc64
+Architecture: amd64 ppc64 s390x
 Priority: optional
 Depends: lib32tinfo5 (= ${binary:Version}),
  ${shlibs:Depends}, ${misc:Depends}
@@ -258,7 +260,7 @@
  architecture.
 
 Package: lib32ncursesw5-dev
-Architecture: amd64 ppc64
+Architecture: amd64 ppc64 s390x
 Section: libdevel
 Priority: optional
 Depends: lib32tinfo5 (= ${binary:Version}), lib32ncursesw5 (= ${binary:Version}),
@@ -293,7 +295,7 @@
  This package supports the 64-bit ABI variant of your system's architecture.
 
 Package: lib32tinfo5
-Architecture: amd64 ppc64
+Architecture: amd64 ppc64 s390x
 Priority: optional
 Depends: ${shlibs:Depends}, ${misc:Depends}
 Replaces: lib32ncurses5 (<< 5.9-3)
@@ -308,7 +310,7 @@
  This package supports the 32-bit ABI variant of your system's architecture.
 
 Package: lib32tinfo-dev
-Architecture: amd64 ppc64
+Architecture: amd64 ppc64 s390x
 Section: libdevel
 Priority: optional
 Depends: lib32tinfo5 (= ${binary:Version}),
diff -Nru ncurses-6.0+20161126/debian/rules ncurses-6.0+20161126/debian/rules
--- ncurses-6.0+20161126/debian/rules	2016-11-28 15:50:38.0 -0200
+++ ncurses-6.0+20161126/debian/rules	2017-03-03 22:22:57.0 -0300
@@ -47,6 +47,8 @@
 package-dbgti=libtinfo$(soname)-dbg
 package-term=ncurses-term
 package-examples=ncurses-examples
+
+m32_flag= -m32
 
 workdir=$(shell pwd)
 tempdir=debian/tmp
@@ -93,6 +105,14 @@
 build_64 = build-64
 endif
 
+ifeq ($(DEB_HOST_ARCH),s390x)
+build_32_target = s390-$(DEB_HOST_GNU_SYSTEM)
+build_32 = build-32 build-wide-32
+lib32 = /lib32
+usr_lib32 = /usr/lib32
+m32_flag = -m31
+endif
+
 ifeq ($(DEB_HOST_ARCH),sparc)
 build_64_target = sparc64-$(DEB_HOST_GNU_SYSTEM)
 build_64 = build-64
@@ -213,8 +235,8 @@
 
 	cf_cv_type_of_bool='unsigned char'; export cf_cv_type_of_bool; \
 	cf_cv_working_poll=yes; export cf_cv_working_poll; \
-	cd $(objdir-32) && CFLAGS="$(CFLAGS)" CC="$(HOST_CC) -m32" \
-		BUILD_CC="gcc" CXX="$(HOST_CXX) -m32" \
+	cd $(objdir-32) && CFLAGS="$(CFLAGS)" CC="$(HOST_CC) $(m32_flag)" \
+		BUILD_CC="gcc" CXX="$(HOST_CXX) $(m32_flag)" \
 		$(relsrcdir)/configure \
 		$(CONFARGS) \
 		--host=$(build_32_target) \
@@ -278,8 +315,8 @@
 
 	cf_cv_type_of_bool='unsigned char'; export cf_cv_type_of_bool; \
 	cf_cv_working_poll=yes; export cf_cv_working_poll; \
-	

Bug#857000: ncurses: Add autopkgtest for ncurses

[Tiago Stürmer Daitx]

Package: ncurses
Version: 6.0+20161126-1
Severity: wishlist
Tags: patch

Dear Maintainer,

Please consider applying the following patch (or the original one [1])
to include support for autopkgtest to the ncurses package. This has
been part of Ubuntu since 2013 [1,2] and all tests passes for the
supported archs [3].

[1] 
http://launchpadlibrarian.net/130717116/ncurses_5.9-10ubuntu2_5.9-10ubuntu3.diff.gz
[2] https://launchpad.net/ubuntu/+source/ncurses/5.9-10ubuntu3
[3] https://autopkgtest.ubuntu.com/packages/ncurses

Many thanks,
Tiago Daitx

-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial'), (400, 'xenial-proposed'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.8.0-34-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru ncurses-6.0+20161126/debian/changelog ncurses-6.0+20161126/debian/changelog
--- ncurses-6.0+20161126/debian/changelog	2016-11-29 18:19:08.0 -0200
+++ ncurses-6.0+20161126/debian/changelog	2017-03-03 22:33:14.0 -0300
@@ -1,3 +1,9 @@
+ncurses (6.0+20161126-2) UNRELEASED; urgency=low
+
+  * Add simple autopkgtest to the package.
+
+ -- Vibhav Pant   Thu, 07 Feb 2013 13:50:14 +0530
+
 ncurses (6.0+20161126-1) unstable; urgency=low
 
   * New upstream patchlevel.
diff -Nru ncurses-6.0+20161126/debian/control ncurses-6.0+20161126/debian/control
--- ncurses-6.0+20161126/debian/control	2016-11-28 15:50:38.0 -0200
+++ ncurses-6.0+20161126/debian/control	2016-11-30 02:13:08.0 -0200
@@ -13,6 +14,7 @@
 Vcs-Browser: https://anonscm.debian.org/cgit/collab-maint/ncurses.git
 Vcs-Git: https://anonscm.debian.org/git/collab-maint/ncurses.git
 Homepage: http://invisible-island.net/ncurses/
+XS-Testsuite: autopkgtest
 
 Package: libtinfo5
 Architecture: any
diff -Nru ncurses-6.0+20161126/debian/tests/build ncurses-6.0+20161126/debian/tests/build
--- ncurses-6.0+20161126/debian/tests/build	1969-12-31 21:00:00.0 -0300
+++ ncurses-6.0+20161126/debian/tests/build	2016-05-25 14:41:01.0 -0300
@@ -0,0 +1,93 @@
+#!/bin/sh
+# autopkgtest check: Build and run a program against ncurses, to verify that 
+# the headers and pkg-config file are installed correctly
+# (C) 2012 Canonical Ltd.
+# Author: Vibhav Pant 
+
+set -e
+
+WORKDIR=$(mktemp -d)
+trap "rm -rf $WORKDIR" 0 INT QUIT ABRT PIPE TERM
+cd $WORKDIR
+cat < curses_test.c
+#include 
+#include 
+
+/* Testing printw and friends here.
+ * Since printw expands to wprintw, it is not being tested.
+ */
+void test_printw_functions(WINDOW * win)
+{
+	int x, y;
+	assert(wprintw(win, "Printing on WINDOW win with wprintw") != ERR);
+	wrefresh(win);
+	getyx(win, y, x);
+	assert(mvwprintw
+	   (win, y + 1, x + 1,
+		"Printing on WINDOW win on coordinates %d, %d with mvwprintw\n",
+		y + 1, x + 1) != ERR);
+	wrefresh(win);
+}
+
+/* Testing wgetch */
+void test_input_functions(WINDOW * win)
+{
+	assert(wgetch(win) == 'a');
+	wrefresh(win);
+}
+
+/* Testing vwprintw */
+void test_vwprintw(WINDOW * win, char *fmt, ...)
+{
+	va_list args;
+	va_start(args, fmt);
+	assert(vwprintw(win, fmt, args) != ERR);
+	va_end(args);
+	wrefresh(win);
+}
+
+/* Testing addch and friends */
+void test_addch_functions(WINDOW * win)
+{
+	char ch;
+
+	/* Print all alphabets */
+	for (ch = 'a'; ch <= 'z'; ch++)
+		assert(waddch(win, ch) != ERR);
+	assert(waddch(win, '\n') != ERR);
+
+	wrefresh(win);
+}
+
+/* Test delwin and endwin */
+void test_delete_and_exit_functions(WINDOW * win)
+{
+	assert(delwin(win) != ERR);
+	assert(endwin() != ERR);
+}
+
+int main()
+{
+	WINDOW *win;
+
+	win = initscr();
+	if (win == NULL) {
+		fprintf(stderr, "initscr failed\n");
+		return 1;
+	}
+	test_printw_functions(win);
+	test_addch_functions(win);
+	test_input_functions(win);
+	test_vwprintw(win, "\nTesting mwvprintf\n");
+
+	return 0;
+}
+EOF
+
+gcc -o curses_test curses_test.c `pkg-config --cflags --libs ncurses` -Wall -Werror
+echo "build: OK"
+[ -x curses_test ]
+export TERM=linux
+echo a | ./curses_test
+echo "run: OK"
+
diff -Nru ncurses-6.0+20161126/debian/tests/control ncurses-6.0+20161126/debian/tests/control
--- ncurses-6.0+20161126/debian/tests/control	1969-12-31 21:00:00.0 -0300
+++ ncurses-6.0+20161126/debian/tests/control	2016-05-25 14:41:01.0 -0300
@@ -0,0 +1,2 @@
+Tests: build
+Depends: libncurses5-dev, build-essential, pkg-config

Bug#856569: open-vm-tools: Depend on either libssl1.0-dev or libssl-dev

[Tiago Stürmer Daitx]

Package: open-vm-tools
Version: 10.1.5-5055683
Severity: wishlist

Dear Maintainer,

Please consider improving Build-depends to accept either
libssl1.0-dev or libssl-dev as that will make backporting easier.

The dependency changed from libssl-dev to libssl1.0-dev due to
bug 828476 (ie. open-vm-tools can't be built with openssl 1.1).
Still, series that don't have libssl1.0-dev have libssl-dev
on 1.0 (confirmed for both Debian and Ubuntu).

Please condider the following debdiff:

--- debian/control.orig 2017-03-02 12:02:25.125780791 -0300
+++ debian/control  2017-03-02 11:47:40.200894481 -0300
@@ -8,7 +8,7 @@
  libdumbnet-dev, libfuse-dev, libgtk2.0-dev, libgtkmm-2.4-dev,
  libicu-dev, libnotify-dev, libpam0g-dev, libprocps-dev, libx11-dev,
  libxinerama-dev, libxss-dev, libxtst-dev, dh-autoreconf, dh-systemd,
- libmspack-dev, libssl1.0-dev, libxerces-c-dev, libxml-security-c-dev
+ libmspack-dev, libssl1.0-dev | libssl-dev, libxerces-c-dev, 
libxml-security-c-dev
 Standards-Version: 3.9.6
 Homepage: https://github.com/vmware/open-vm-tools
 Vcs-Git: https://github.com/bzed/pkg-open-vm-tools.git

Thanks!
Tiago

-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial'), (400, 'xenial-proposed'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.8.0-34-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#833933: openjdk-7: jamvm is broken due to missing native methods in sun.misc.Unsafe

[Tiago Stürmer Daitx]

Source: openjdk-7
Version: 7u111-2.6.7-1
Severity: important

Dear Maintainer,

[Issue]
The fix of OpenJDK's bug 8158260
(http://icedtea.classpath.org/hg/release/icedtea7-forest-2.6/hotspot/rev/4f8cbd54a9c6)
introduced 2 new native methods to the sun.misc.Unsafe class:
isBigEndian0 and unalignedAccess0.

This completely broke JamVM and as of now it is impossible to start a
jamvm session.

jtreg summary results for OpenJDK 7:
hotspot - Test results: passed: 5; failed: 309; error: 7
langtools - Test results: passed: 374; failed: 1,593; error: 1

Error output from a hotspot testcase:
--System.err:(6/344)--
Error initialising VM (initialiseMainThread)
Check the README for compatible class-libraries/versions
Exception occurred while printing exception
(java/lang/NullPointerException)...
Original exception was java/lang/UnsatisfiedLinkError
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
result: Failed. Unexpected exit from test [exit code: 1]

Running java -jamvm -version fails the same way.

[Fix]
The simple fix is to add both methods to the natives.c file in the
classlib/openjdk directory.

I have tested this with IcedTea 2.6.7 and now jtreg passes:
hotspot - Test results: passed: 220; failed: 90; error: 11
langtools - Test results: passed: 1,901; failed: 65; error: 2

I have reported this upstream at
https://sourceforge.net/p/jamvm/code/merge-requests/1/ and it is now
waiting review.

Also reported for IcedTea 2.6.7 at
http://icedtea.classpath.org/bugzilla/show_bug.cgi?id=3134

-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (4000, 'xenial-updates'), (4000, 'xenial-security'), (4000, 
'xenial-backports'), (4000, 'xenial')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.4.0-31-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#794190: quota: failure to build on wily proposed due to wrong LDFLAGS usage

[Tiago Stürmer Daitx]

Package: quota
Followup-For: Bug #794190
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu wily ubuntu-patch

Dear Maintainer,

Updated patch to include dep3 information.

*** /tmp/tmpWJcPSN/bug_body

In Ubuntu, the attached patch was applied to achieve the following:

  * Move -ltirpc from LDFLAGS to LIBS in debian/rules (LP: #1480047,
Closes: #794190)
  * Add LIBS to Makefile.in


Thanks for considering the patch.


-- System Information:
Debian Release: jessie/sid
  APT prefers vivid-updates
  APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'), 
(100, 'vivid-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.19.0-26-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -u quota-4.02/debian/changelog quota-4.02/debian/changelog
diff -u quota-4.02/debian/patches/series quota-4.02/debian/patches/series
--- quota-4.02/debian/patches/series
+++ quota-4.02/debian/patches/series
@@ -3,0 +4 @@
+tirpc-libs.diff
diff -u quota-4.02/debian/rules quota-4.02/debian/rules
--- quota-4.02/debian/rules
+++ quota-4.02/debian/rules
@@ -17,7 +17,7 @@
 	dh_quilt_patch
 	# Add here commands to configure the package.
 	( [ "`dpkg --print-architecture`" = "powerpc" ] && CFLAGSDEF += -D__BYTEORDER_HAS_U64__; \
-	  export CFLAGS="$(CFLAGS_DEF) -I/usr/include/tirpc" CPPFLAGS="$(CPPFLAGS_DEF)" LDFLAGS="$(LDFLAGS_DEF) -ltirpc"; \
+	  export CFLAGS="$(CFLAGS_DEF) -I/usr/include/tirpc" CPPFLAGS="$(CPPFLAGS_DEF)" LDFLAGS="$(LDFLAGS_DEF)" LIBS="-ltirpc"; \
  	  ./configure --prefix=/usr --mandir=\$${prefix}/share/man --infodir=\$${prefix}/share/info --sysconfdir=/etc --enable-ext2direct=yes --enable-rpcsetquota=yes --enable-rootsbin=yes --enable-ldapmail=yes --enable-netlink=yes)
 
 	touch configure-stamp
only in patch2:
unchanged:
--- quota-4.02.orig/debian/patches/tirpc-libs.diff
+++ quota-4.02/debian/patches/tirpc-libs.diff
@@ -0,0 +1,75 @@
+Description: Move -ltirpc from LDFLAGS to LIBS
+ The current generated Makefile.in file lacks a LIBS entry. Regenerating it
+ with a current autotools does introducte that entry and would be the right
+ approach, but I'm not sure that won't introduce regressions due to the
+ required autotools version. Thus this patch simply updates Makefile.in to
+ also make use of LIBS.
+Author: Tiago Stürmer Daitx <tda...@gmail.com>
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794190
+Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/quota/+bug/1480047
+Last-Update: 2015-09-08
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/Makefile.in
 b/Makefile.in
+@@ -105,47 +105,47 @@
+ 	-$(INSTALL) -m $(DEF_MAN_MODE) *.8 $(ROOTDIR)$(mandir)/man8
+ 
+ quotaon: quotaon.o quotaon_xfs.o $(LIBOBJS)
+-	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^
++	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^ $(LIBS)
+ 
+ quotacheck: quotacheck.o quotacheck_v1.o quotacheck_v2.o quotaops.o $(LIBOBJS)
+-	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^ $(EXT2LIBS)
++	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^ $(LIBS) $(EXT2LIBS)
+ 
+ quota: quota.o quotaops.o $(LIBOBJS)
+-	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^
++	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^ $(LIBS)
+ 
+ quotasync: quotasync.o $(LIBOBJS)
+-	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^
++	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^ $(LIBS)
+ 
+ quot: quot.o $(LIBOBJS)
+-	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^
++	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^ $(LIBS)
+ 
+ repquota: repquota.o $(LIBOBJS)
+-	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^
++	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^ $(LIBS)
+ 
+ warnquota: warnquota.o $(LIBOBJS)
+-	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^ $(LDAPLIBS)
++	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^ $(LIBS) $(LDAPLIBS)
+ 
+ quotastats: quotastats.o common.o pot.o
+-	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^
++	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^ $(LIBS)
+ 
+ xqmstats: xqmstats.o common.o pot.o
+-	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^
++	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^ $(LIBS)
+ 
+ edquota: edquota.o quotaops.o $(LIBOBJS)
+-	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^
++	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^ $(LIBS)
+ 
+ setquota: setquota.o quotaops.o $(LIBOBJS)
+-	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^
++	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^ $(LIBS)
+ 
+ convertquota: convertquota.o $(LIBOBJS)
+-	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^
++	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^ $(LIBS)
+ 
+ rpc.rquotad: rquota_server.o rquota_svc.o svc_socket.o $(LIBOBJS)
+ 	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^ $(LIBS)
+ 
+ ifneq ($(NETLINKLIBS),)
+ quota_nld: quota_nld.o $(LIBOBJS)
+-	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^ $(NETLINKLIBS)
++	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^ $(LIBS) $(NETLINKLIBS)
+ endif
+ 
+ pot.o: pot.c pot.h

Bug#797816: openscad FTBFS in armhf due to conflict declaration of headers gl3.h and glew.h

[Tiago Stürmer Daitx]

Package: openscad
Version: 2015.03-1+dfsg-2
Severity: important

Dear Maintainer,

openscad 2015.03-1+dfsg-2ubuntu1 FTBFS on armhf due to conflicting headers.

>From the armhf build at 
>https://launchpad.net/ubuntu/+source/openscad/2015.03-1+dfsg-2ubuntu1/+build/7851279

g++ -c -pipe -fno-strict-aliasing -frounding-math -DEIGEN_DONT_ALIGN 
-I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include 
-I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/freetype2 -g 
-O2 -fPIE -fstack-protector-strong -Wformat -Werror=format-security 
-D_FORTIFY_SOURCE=2 -D_REENTRANT -Wall -W -Wno-unused-local-typedefs -fPIC 
-DOPENSCAD_VERSION=2015.03-1 -DOPENSCAD_SHORTVERSION=2015.03 -DOPENSCAD_YEAR=.0 
-DOPENSCAD_MONTH=.0 -DOPENSCAD_DAY=.0 -DENABLE_CGAL -DENABLE_OPENCSG 
-DUSE_SCINTILLA_EDITOR -DQT_NO_DEBUG -DQT_OPENGL_LIB -DQT_PRINTSUPPORT_LIB 
-DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_CONCURRENT_LIB -DQT_CORE_LIB -I. -Isrc 
-isystem /usr/include/arm-linux-gnueabihf/qt5 -Isrc/libtess2/Include -isystem 
/usr/include/arm-linux-gnueabihf/qt5/QtOpenGL -isystem 
/usr/include/arm-linux-gnueabihf/qt5/QtPrintSupport -isystem 
/usr/include/arm-linux-gnueabihf/qt5/QtWidgets -isystem 
/usr/include/arm-linux-gnueabihf/qt5/QtGui -isystem 
/usr/include/arm-linux-gnueabihf/qt5/
 QtConcurrent -isystem /usr/include/arm-linux-gnueabihf/qt5/QtCore -Iobjects 
-isystem /usr/include/eigen3 
-I/usr/lib/arm-linux-gnueabihf/qt5/mkspecs/linux-g++ -o objects/grid.o 
src/grid.cc
In file included from /usr/include/arm-linux-gnueabihf/qt5/QtGui/qopengl.h:97:0,
 from /usr/include/arm-linux-gnueabihf/qt5/QtOpenGL/qgl.h:39,
 from /usr/include/arm-linux-gnueabihf/qt5/QtOpenGL/QGLWidget:1,
 from src/QGLView.h:4,
 from src/QGLView.cc:28:
/usr/include/GLES3/gl3.h:69:25: error: conflicting declaration 'typedef 
khronos_ssize_t GLsizeiptr'
 typedef khronos_ssize_t GLsizeiptr;
 ^
In file included from src/system-gl.h:4:0,
 from src/QGLView.h:3,
 from src/QGLView.cc:28:
/usr/include/GL/glew.h:1663:19: note: previous declaration as 'typedef 
ptrdiff_t GLsizeiptr'
 typedef ptrdiff_t GLsizeiptr;
   ^
In file included from /usr/include/arm-linux-gnueabihf/qt5/QtGui/qopengl.h:97:0,
 from /usr/include/arm-linux-gnueabihf/qt5/QtOpenGL/qgl.h:39,
 from /usr/include/arm-linux-gnueabihf/qt5/QtOpenGL/QGLWidget:1,
 from src/QGLView.h:4,
 from src/QGLView.cc:28:
/usr/include/GLES3/gl3.h:70:26: error: conflicting declaration 'typedef 
khronos_intptr_t GLintptr'
 typedef khronos_intptr_t GLintptr;
  ^
In file included from src/system-gl.h:4:0,
 from src/QGLView.h:3,
 from src/QGLView.cc:28:
/usr/include/GL/glew.h:1662:19: note: previous declaration as 'typedef 
ptrdiff_t GLintptr'
 typedef ptrdiff_t GLintptr;
   ^
In file included from /usr/include/arm-linux-gnueabihf/qt5/QtGui/qopengl.h:97:0,
 from /usr/include/arm-linux-gnueabihf/qt5/QtOpenGL/qgl.h:39,
 from /usr/include/arm-linux-gnueabihf/qt5/QtOpenGL/QGLWidget:1,
 from src/QGLView.h:4,
 from src/QGLView.cc:28:
/usr/include/GLES3/gl3.h:377:60: error: 'void __glewActiveTexture(GLenum)' 
redeclared as different kind of symbol
 GL_APICALL void GL_APIENTRY glActiveTexture (GLenum texture);
^
In file included from src/system-gl.h:4:0,
 from src/QGLView.h:3,
 from src/QGLView.cc:28:
/usr/include/GL/glew.h:15048:40: note: previous declaration 'void (* 
__glewActiveTexture)(GLenum)'
 GLEW_FUN_EXPORT PFNGLACTIVETEXTUREPROC __glewActiveTexture;
^



-- System Information:
Debian Release: jessie/sid
  APT prefers vivid-updates
  APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'), 
(100, 'vivid-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.19.0-26-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#797842: libjoda-time-java: Update libjoda-time-java to 2.8.2 to fix timezone

[Tiago Stürmer Daitx]

Package: libjoda-time-java
Version: 2.7-2
Severity: wishlist

Dear Maintainer,

As reported in LP:# 1491530 jruby FTBFS partly due to an outdated joda-time 
package.
https://bugs.launchpad.net/ubuntu/+source/libjoda-time-java/+bug/1491530


This particular bug lead to 2 mspec test failures causing jruby to FTBFS as 
reported in LP: #1491526 as jruby currently runs OpenJDK 8u66 in wily.

libjoda-time-java will fail to report TZ name and shortname when running under 
OpenJDK 8u60 or earlier.

Upstream bugs https://github.com/JodaOrg/joda-time/issues/288 and 
https://github.com/JodaOrg/joda-time/issues/291

Fixed on 2.8.1. Latest is 2.8.2 with updated TZ data.

Both issues were reported upstream since JRuby should not fail due to 
joda-time: https://github.com/jruby/jruby/issues/3303 and 
https://github.com/jruby/jruby/issues/3303


Snippet from log:
30)
Time#strftime returns the timezone with %Z FAILED
Expected "+00:00"
 to equal "GMT"

/«PKGBUILDDIR»/spec/ruby/core/time/strftime_spec.rb:238:in `(root)'
org/jruby/RubyBasicObject.java:1574:in `instance_eval'
org/jruby/RubyEnumerable.java:1412:in `all?'
org/jruby/RubyFixnum.java:275:in `times'
org/jruby/RubyArray.java:1613:in `each'
/«PKGBUILDDIR»/spec/ruby/core/time/strftime_spec.rb:4:in `(root)'
org/jruby/RubyKernel.java:1059:in `load'
org/jruby/RubyBasicObject.java:1574:in `instance_eval'
org/jruby/RubyArray.java:1613:in `each'

31)
Time#zone returns UTC when called on a UTC time FAILED
Expected "GMT"
 to equal "UTC"


-- System Information:
Debian Release: jessie/sid
  APT prefers vivid-updates
  APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'), 
(100, 'vivid-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.19.0-26-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#797842: libjoda-time-java: Update libjoda-time-java to 2.8.2 to fix timezone

[Tiago Stürmer Daitx]

Package: libjoda-time-java
Followup-For: Bug #797842
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu wily ubuntu-patch

Dear Maintainer,

A debdiff for updating libjoda-time-java from 2.7 to 2.8.2 is attached.

The sources can also be obtained by going to LP: #1491530
https://bugs.launchpad.net/ubuntu/+source/libjoda-time-java/+bug/1491530

*** /tmp/tmp5B_fWw/bug_body

In Ubuntu, the attached patch was applied to achieve the following:

  - 2 JRuby mspec tests for timezone do not fail any longer



  * New upstream release. (LP: #1491530, Closes: #797842)
  * Refresh patches.


Thanks for considering the patch.


-- System Information:
Debian Release: jessie/sid
  APT prefers vivid-updates
  APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'), 
(100, 'vivid-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.19.0-26-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru libjoda-time-java-2.7/debian/changelog libjoda-time-java-2.8.2/debian/changelog
diff -Nru libjoda-time-java-2.7/debian/patches/01-maven2-compatibility.patch libjoda-time-java-2.8.2/debian/patches/01-maven2-compatibility.patch
--- libjoda-time-java-2.7/debian/patches/01-maven2-compatibility.patch	2015-05-01 00:52:13.0 -0300
+++ libjoda-time-java-2.8.2/debian/patches/01-maven2-compatibility.patch	2015-09-01 23:26:56.0 -0300
@@ -3,7 +3,7 @@
 Forwarded: no
 --- a/pom.xml
 +++ b/pom.xml
-@@ -610,7 +610,7 @@
+@@ -614,7 +614,7 @@
  


diff -Nru libjoda-time-java-2.7/pom.xml libjoda-time-java-2.8.2/pom.xml
--- libjoda-time-java-2.7/pom.xml	2015-01-11 22:20:35.0 -0200
+++ libjoda-time-java-2.8.2/pom.xml	2015-08-11 08:57:35.0 -0300
@@ -9,7 +9,7 @@
   joda-time
   jar
   Joda-Time
-  2.7
+  2.8.2
   Date and time library to replace JDK date handling
   http://www.joda.org/joda-time/
 
@@ -65,6 +65,10 @@
   https://github.com/mebigfatguy
 
 
+  Dan Cavallaro
+  https://github.com/dancavallaro
+
+
   Luc Claes
   https://github.com/lucclaes
 
@@ -253,7 +257,7 @@
   
 org.codehaus.mojo  
 exec-maven-plugin
-1.2.1
+1.4.0
 
   
 compile-tzdb
@@ -312,7 +316,7 @@
 src/conf/MANIFEST.MF
 
   ${tz.database.version}
-  Joda-Time-No-TZDB
+  org.joda.time
 
   
 
@@ -432,7 +436,7 @@
   
 com.github.github
 site-maven-plugin
-0.10
+0.12
 
   
 github-site
@@ -455,9 +459,9 @@
   
 org.codehaus.mojo
 clirr-maven-plugin
-2.3
+2.6.1
 
-  2.3
+  2.7
   info
   true
 
@@ -756,28 +760,28 @@
   
   
 
-2.4
-2.9
-2.11
-2.5
-3.1
-2.8.1
-2.8
-1.4
-2.5.1
-2.4
-2.9.1
-2.3
-3.2
-3.0.1
-2.7
-2.3.1
-2.6
-3.3
-2.2.1
-2.16
-2.16
-1.0
+2.5.5
+2.11
+2.16
+2.6.1
+3.3
+2.8.2
+2.10
+1.6
+2.5.2
+2.6
+2.10.3
+2.5
+3.4
+3.5
+2.8
+2.4
+2.7
+3.4
+2.4
+2.18.1
+2.18.1
+1.1
 
 1.5
 1.5
@@ -795,6 +799,6 @@
 
 UTF-8
 UTF-8
-2014j
+2015f
   
 
diff -Nru libjoda-time-java-2.7/README.md libjoda-time-java-2.8.2/README.md
--- libjoda-time-java-2.7/README.md	2015-01-11 22:20:35.0 -0200
+++ libjoda-time-java-2.8.2/README.md	2015-08-11 08:57:35.0 -0300
@@ -46,11 +46,11 @@
 
 
 ### Releases
-[Release 2.7](http://www.joda.org/joda-time/download.html) is the current latest release.
-This release is considered stable and worthy of the 1.x tag.
+[Release 2.8.2](http://www.joda.org/joda-time/download.html) is the current latest release.
+This release is considered stable and worthy of the 2.x tag.
 It depends on JDK 1.5 or later.
 
-Available in the [Maven Central repository](http://search.maven.org/#artifactdetails|joda-time|joda-time|2.7|jar)
+Available in the [Maven Central repository](http://search.maven.org/#artifactdetails|joda-time|joda-time|2.8.2|jar)
 
 
 ### Related projects
diff -Nru libjoda-time-java-2.7/RELEASE-NOTES.txt libjoda-time-java-2.8.2/RELEASE-NOTES.txt
--- libjoda-time-java-2.7/RELEASE-NOTES.txt	2015-01-11 22:20:35.0 -0200
+++ libjoda-time-java-2.8.2/RELEASE-NOTES.txt	2015-08-11 08:57:35.0 -0300
@@ -1,5 +1,5 @@
-Joda-Time version 2.7
--
+Joda-Time version 2.8.2
+---
 
 Joda-Time is a date and time handling library that seeks to replace the JDK
 Date and Calendar classes.
@@ -9,68 +9,30 @@
 
 Joda-Time is licensed under the business-friendly Apache License Version 2.
 This is the same license as all of Apache, plus 

Bug#795178: ceph FTBFS with boost1.58

[Tiago Stürmer Daitx]

Package: ceph
Followup-For: Bug #795178
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu wily ubuntu-patch

Dear Maintainer,

Please consider this updated patch, which now includes dep3 data.

*** /tmp/tmpQjuvXN/bug_body

In Ubuntu, the attached patch was applied to achieve the following:

  - Allow build with boost 1.58.



  * Non-maintainer upload.
  * Fix compile failure with boost 1.58 (LP: #1483403, closes 795178):
- src/mon/OSDMonitor.cc: backport Ceph#11576 remove unused variable


Thanks for considering the patch.


-- System Information:
Debian Release: jessie/sid
  APT prefers vivid-updates
  APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'), 
(100, 'vivid-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.19.0-26-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru ceph-0.94.2/debian/changelog ceph-0.94.2/debian/changelog
diff -Nru ceph-0.94.2/debian/patches/remove-unused-variable-ceph-bug-11576.patch ceph-0.94.2/debian/patches/remove-unused-variable-ceph-bug-11576.patch
--- ceph-0.94.2/debian/patches/remove-unused-variable-ceph-bug-11576.patch	1969-12-31 21:00:00.0 -0300
+++ ceph-0.94.2/debian/patches/remove-unused-variable-ceph-bug-11576.patch	2015-08-31 09:13:06.0 -0300
@@ -0,0 +1,25 @@
+Description: ceph fails to compile with boost 1.58
+ see http://www.boost.org/doc/libs/1_58_0/doc/html/boost/relaxed_get.html 
+ and http://www.boost.org/doc/libs/1_58_0/doc/html/boost/get_idp295310448.html, 
+ boost 1.58 introduced "strict_get" and boost::get is an alias of it. but we 
+ are using boost::get(tuple)
+Author: Kefu Chai 
+Origin: upstream, https://github.com/ceph/ceph/pull/4616
+Bug: http://tracker.ceph.com/issues/11576
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795178
+Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1483403
+Applied-Upstream: 0.94.3, http://tracker.ceph.com/issues/11982
+Last-Update: 2015-08-11
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/src/mon/OSDMonitor.cc
 b/src/mon/OSDMonitor.cc
+@@ -2998,8 +2998,6 @@
+   } else if (prefix == "osd crush get-tunable") {
+ string tunable;
+ cmd_getval(g_ceph_context, cmdmap, "tunable", tunable);
+-int value;
+-cmd_getval(g_ceph_context, cmdmap, "value", value);
+ ostringstream rss;
+ if (f)
+   f->open_object_section("tunable");
diff -Nru ceph-0.94.2/debian/patches/series ceph-0.94.2/debian/patches/series
--- ceph-0.94.2/debian/patches/series	2015-07-09 07:36:07.0 -0300
+++ ceph-0.94.2/debian/patches/series	2015-08-31 09:02:24.0 -0300
@@ -18,3 +18,4 @@
 fix-argparse-defaults.patch
 fix-cycles-arch.patch
 vivid-does-systemd.patch
+remove-unused-variable-ceph-bug-11576.patch

Bug#797356: bluez-tools FTBFS in 64-bit archs due to implicit pointer conversion

[Tiago Stürmer Daitx]

Package: bluez-tools
Version: 0.2.0~20140808-3
Severity: important

Dear Maintainer,

After LDADD fix (LP: #1489661, Debian #797128) bluez-tools build now
fails on 64-bit systems due to implicit pointer conversion in
bt-device.c.

Build logs at:
https://launchpad.net/ubuntu/+source/bluez-tools/0.2.0~20140808-3ubuntu1

gcc -DHAVE_CONFIG_H -I. -I.. -I/usr/include/glib-2.0
-I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -pthread
-I/usr/include/glib-2.0
-I/usr/lib/powerpc64le-linux-gnu/glib-2.0/include -D_FORTIFY_SOURCE=2 -g
-O3 -fstack-protector-strong -Wformat -Werror=format-security -c -o
bt-device.o bt-device.c
bt-device.c: In function '_bt_device_sdp_browse':
bt-device.c:345:50: warning: implicit declaration of function
'g_unix_input_stream_new' [-Wimplicit-function-declaration]
 GInputStream *exec_output = (GInputStream *)
 g_unix_input_stream_new(pipefd[0], TRUE);

-- System Information:
Debian Release: jessie/sid
  APT prefers vivid-updates
  APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'), 
(100, 'vivid-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.19.0-26-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#797356: bluez-tools FTBFS in 64-bit archs due to implicit pointer conversion

[Tiago Stürmer Daitx]

Package: bluez-tools
Followup-For: Bug #797356
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu wily ubuntu-patch

Dear Maintainer,

This patch provides the right includes so gcc can know the right return
type instead of assuming an integer. This fix prevents the implicit
pointer conversion warning from happening.

bt-device.c was missing an include for gio/gunixinputstream.c and
configure.ac had to be updated to include gio-unix-2.0 module.

Fix also forwarded upstream at https://github.com/khvzak/bluez-tools/pull/7

*** /tmp/tmplbrF1k/bug_body

In Ubuntu, the attached patch was applied to achieve the following:

  - fix FTBFS


  * Non-maintainer upload.
  * debian/patches/fix-implicity-pointer-conversion.patch: include
gio-unix-2.0 module to configure.ac and gio/gunixinputstream.h
to bt-device.c (LP: #1490204, Closes: 797356)


Thanks for considering the patch.


-- System Information:
Debian Release: jessie/sid
  APT prefers vivid-updates
  APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'), 
(100, 'vivid-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.19.0-26-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru bluez-tools-0.2.0~20140808/debian/changelog bluez-tools-0.2.0~20140808/debian/changelog
diff -Nru bluez-tools-0.2.0~20140808/debian/patches/fix-implicity-pointer-conversion.patch bluez-tools-0.2.0~20140808/debian/patches/fix-implicity-pointer-conversion.patch
--- bluez-tools-0.2.0~20140808/debian/patches/fix-implicity-pointer-conversion.patch	1969-12-31 21:00:00.0 -0300
+++ bluez-tools-0.2.0~20140808/debian/patches/fix-implicity-pointer-conversion.patch	2015-08-29 19:55:06.0 -0300
@@ -0,0 +1,41 @@
+Description: Fix implicit pointer conversion in bt-device.c
+ Provide the right includes so gcc can know the right return type
+ instead of assuming an integer. This fix prevents the implicit
+ pointer conversion warning from happening (see [1] why it is
+ good to avoid those kind of conversions).
+
+ bt-device.c was missing an include for gio/gunixinputstream.c.
+ configure.ac had to be updated to include gio-unix-2.0 module.
+
+ [1] https://wiki.debian.org/ImplicitPointerConversions
+Author: Tiago Stürmer Daitx tiago.da...@canonical.com
+Bug: https://github.com/khvzak/bluez-tools/pull/7 
+Bug-Debian: https://bugs.launchpad.net/ubuntu/+source/bluez-tools/+bug/1490204
+Bug-Ubuntu: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797356
+Forwarded: URL|no|not-needed, useless if you have a Bug field, optional
+Applied-Upstream: version|URL|commit, identifies patches merged upstream, optional
+Reviewed-by: name and email of a reviewer, optional
+Last-Update: -MM-DD, last update of the meta-information, optional
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/configure.ac
 b/configure.ac
+@@ -39,7 +39,7 @@
+ PKG_PROG_PKG_CONFIG
+ 
+ PKG_CHECK_MODULES([GLIB], [glib-2.0 = 2.24.0])
+-PKG_CHECK_MODULES([GIO], [gio-2.0 = 2.26.0])
++PKG_CHECK_MODULES([GIO], [gio-2.0 = 2.26.0 gio-unix-2.0 = 2.26.0])
+ 
+ # Check for the availability of libreadline
+ AC_CHECK_HEADERS([readline/readline.h], [HAVE_READLINE_H=1])
+--- a/src/bt-device.c
 b/src/bt-device.c
+@@ -32,6 +32,7 @@
+ 
+ #include glib.h
+ #include gio/gio.h
++#include gio/gunixinputstream.h
+ 
+ #include lib/dbus-common.h
+ #include lib/helpers.h
diff -Nru bluez-tools-0.2.0~20140808/debian/patches/series bluez-tools-0.2.0~20140808/debian/patches/series
--- bluez-tools-0.2.0~20140808/debian/patches/series	1969-12-31 21:00:00.0 -0300
+++ bluez-tools-0.2.0~20140808/debian/patches/series	2015-08-29 19:55:06.0 -0300
@@ -0,0 +1 @@
+fix-implicity-pointer-conversion.patch

Bug#797128: bluez-tools FTBFS on wily-proposed due LDFLAGS misuse

[Tiago Stürmer Daitx]

Package: bluez-tools
Version: 0.2.0~20140808
Severity: important

Dear Maintainer,

As reported in LP: #1489661
https://bugs.launchpad.net/ubuntu/+source/bluez-tools/+bug/1489661

bluez-tools FTBFS in wily-proposed with the following error:

gcc  -g -O2 -fstack-protector-strong -Wformat -Werror=format-security
-lglib-2.0  -lgio-2.0 -lgobject-2.0 -lglib-2.0  -Wl,-Bsymbolic-functions
-Wl,-z,relro -o bt-adapter lib/agent-helper.o lib/dbus-common.o
lib/helpers.o lib/manager.o lib/obex_agent.o lib/properties.o lib/sdp.o
lib/bluez/adapter.o lib/bluez/agent_manager.o lib/bluez/alert_agent.o
lib/bluez/alert.o lib/bluez/cycling_speed.o
lib/bluez/cycling_speed_manager.o lib/bluez/device.o
lib/bluez/health_channel.o lib/bluez/health_device.o
lib/bluez/health_manager.o lib/bluez/heart_rate.o
lib/bluez/heart_rate_manager.o lib/bluez/media.o
lib/bluez/media_control.o lib/bluez/media_player.o lib/bluez/network.o
lib/bluez/network_server.o lib/bluez/obex/obex_agent_manager.o
lib/bluez/obex/obex_client.o lib/bluez/obex/obex_file_transfer.o
lib/bluez/obex/obex_message_access.o lib/bluez/obex/obex_message.o
lib/bluez/obex/obex_object_push.o lib/bluez/obex/obex_phonebook_access.o
lib/bluez/obex/obex_session.o lib/bluez/obex/obex_synchronization.o
lib/bluez/obex/obex_transfer.o lib/bluez/profile_manager.o
lib/bluez/proximity_monitor.o lib/bluez/proximity_reporter.o
lib/bluez/sim_access.o lib/bluez/thermometer.o
lib/bluez/thermometer_manager.o bt-adapter.o  
lib/agent-helper.o: In function `_find_device_pin':
/«PKGBUILDDIR»/src/lib/agent-helper.c:329: undefined reference to
`g_hash_table_lookup'
/«PKGBUILDDIR»/src/lib/agent-helper.c:330: undefined reference to
`g_hash_table_lookup'
snip
/«PKGBUILDDIR»/src/bt-adapter.c:301: undefined reference to
`g_variant_get_uint32'
/«PKGBUILDDIR»/src/bt-adapter.c:302: undefined reference to
`g_ascii_strcasecmp'
/«PKGBUILDDIR»/src/bt-adapter.c:303: undefined reference to
`g_variant_get_boolean'
collect2: error: ld returned 1 exit status
make[3]: *** [bt-adapter] Error 1
Makefile:574: recipe for target 'bt-adapter' failed
make[3]: Leaving directory '/«PKGBUILDDIR»/src'
make[2]: *** [all-recursive] Error 1
Makefile:362: recipe for target 'all-recursive' failed
make[2]: Leaving directory '/«PKGBUILDDIR»'
make[1]: *** [all] Error 2
Makefile:303: recipe for target 'all' failed
make[1]: Leaving directory '/«PKGBUILDDIR»'
dh_auto_build: make -j1 returned exit code 2
make: *** [build] Error 2
debian/rules:8: recipe for target 'build' failed
dpkg-buildpackage: error: debian/rules build gave error exit status 2

---

This is due to the libraries being set in LDFLAGS while they should
actually be set on LIBS or LDADD [1,2].

[1]
http://www.gnu.org/savannah-checkouts/gnu/autoconf/manual/autoconf-2.69/html_node/Preset-Output-Variables.html#index-LDFLAGS-112
[2] http://www.gnu.org/software/automake/manual/html_node/Linking.html

-- System Information:
Debian Release: jessie/sid
  APT prefers vivid-updates
  APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'), 
(100, 'vivid-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.19.0-26-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#797128: bluez-tools FTBFS on wily-proposed due LDFLAGS misuse

[Tiago Stürmer Daitx]

Package: bluez-tools
Followup-For: Bug #797128
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu wily ubuntu-patch

Dear Maintainer,

Updated patch to adhere to dep3 standard. (thanks to ciphermox for
the heads up)

*** /tmp/tmp_Nop_S/bug_body

  * Non-maintainer upload.
  * debian/patches/use-ldadd.patch: fix AM_LDFLAGS misuse, use 
LDADD instead (LP: #1489661, Closes: 797128) 


Thanks for considering the patch.


-- System Information:
Debian Release: jessie/sid
  APT prefers vivid-updates
  APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'), 
(100, 'vivid-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.19.0-26-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru bluez-tools-0.2.0~20140808/debian/changelog bluez-tools-0.2.0~20140808/debian/changelog
diff -Nru bluez-tools-0.2.0~20140808/debian/patches/series bluez-tools-0.2.0~20140808/debian/patches/series
--- bluez-tools-0.2.0~20140808/debian/patches/series	1969-12-31 21:00:00.0 -0300
+++ bluez-tools-0.2.0~20140808/debian/patches/series	2015-08-27 20:44:59.0 -0300
@@ -0,0 +1 @@
+use-ldadd.patch
diff -Nru bluez-tools-0.2.0~20140808/debian/patches/use-ldadd.patch bluez-tools-0.2.0~20140808/debian/patches/use-ldadd.patch
--- bluez-tools-0.2.0~20140808/debian/patches/use-ldadd.patch	1969-12-31 21:00:00.0 -0300
+++ bluez-tools-0.2.0~20140808/debian/patches/use-ldadd.patch	2015-08-27 23:04:26.0 -0300
@@ -0,0 +1,31 @@
+Description:  Fix AM_LDFLAGS misuse, use LDADD instead
+ Libraries are wrongly being added to LDFLAGS, they should be set
+ in LIBS or LDADD according to autoconf [1] and automake [2].
+ This causes failure to build from source (FTBFS) in Ubuntu Wily
+ Proposed as reported in Launchpad #1489661 [3] and Debian #797128.
+ 
+Author: Tiago Stürmer Daitx tiago.da...@gmail.com
+Origin: vendor, https://github.com/tdaitx/bluez-tools/commit/355f6af4f59690900445bed586905c5b3a86c364
+Bug: https://github.com/khvzak/bluez-tools/pull/5
+Bug-Ubuntu: https://bugs.launchpad.net/debian/+source/bluez-tools/+bug/1489661
+Bug-Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797128
+Last-Update: 2015-08-27
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/src/Makefile.am
 b/src/Makefile.am
+@@ -1,5 +1,5 @@
+ AM_CPPFLAGS = $(GLIB_CFLAGS) $(GIO_CFLAGS)
+-AM_LDFLAGS = $(GLIB_LIBS) $(GIO_LIBS)
++LDADD = $(GLIB_LIBS) $(GIO_LIBS)
+ 
+ bluez_sources =	lib/bluez/adapter.c lib/bluez/adapter.h \
+ 		lib/bluez/agent_manager.c lib/bluez/agent_manager.h \
+@@ -50,6 +50,6 @@
+ bt_device_SOURCES = $(lib_sources) $(bluez_sources) bt-device.c
+ bt_network_SOURCES = $(lib_sources) $(bluez_sources) bt-network.c
+ bt_obex_SOURCES = $(lib_sources) $(bluez_sources) bt-obex.c
+-bt_obex_LDADD = $(LIBREADLINE)
++bt_obex_LDADD = $(LDADD) $(LIBREADLINE)
+ 
+ dist_man_MANS = bt-adapter.1 bt-agent.1 bt-device.1 bt-network.1 bt-obex.1

Bug#797128: bluez-tools FTBFS on wily-proposed due LDFLAGS misuse

[Tiago Stürmer Daitx]

Package: bluez-tools
Followup-For: Bug #797128
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu wily ubuntu-patch

Dear Maintainer,

The attached patch fixes FTBFS.

*** /tmp/tmpEiwsE1/bug_body

In Ubuntu, the attached patch was applied to achieve the following:

Fix FTBFS.


  * Non-maintainer upload.
  * debian/patches/use-ldadd.patch: fix AM_LDFLAGS misuse, use 
LDADD instead (LP: #1489661, Closes: 797128) 


Thanks for considering the patch.


-- System Information:
Debian Release: jessie/sid
  APT prefers vivid-updates
  APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'), 
(100, 'vivid-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.19.0-26-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru bluez-tools-0.2.0~20140808/debian/changelog bluez-tools-0.2.0~20140808/debian/changelog
diff -Nru bluez-tools-0.2.0~20140808/debian/patches/series bluez-tools-0.2.0~20140808/debian/patches/series
--- bluez-tools-0.2.0~20140808/debian/patches/series	1969-12-31 21:00:00.0 -0300
+++ bluez-tools-0.2.0~20140808/debian/patches/series	2015-08-27 20:44:59.0 -0300
@@ -0,0 +1 @@
+use-ldadd.patch
diff -Nru bluez-tools-0.2.0~20140808/debian/patches/use-ldadd.patch bluez-tools-0.2.0~20140808/debian/patches/use-ldadd.patch
--- bluez-tools-0.2.0~20140808/debian/patches/use-ldadd.patch	1969-12-31 21:00:00.0 -0300
+++ bluez-tools-0.2.0~20140808/debian/patches/use-ldadd.patch	2015-08-27 20:02:35.0 -0300
@@ -0,0 +1,17 @@
+--- a/src/Makefile.am
 b/src/Makefile.am
+@@ -1,5 +1,5 @@
+ AM_CPPFLAGS = $(GLIB_CFLAGS) $(GIO_CFLAGS)
+-AM_LDFLAGS = $(GLIB_LIBS) $(GIO_LIBS)
++LDADD = $(GLIB_LIBS) $(GIO_LIBS)
+ 
+ bluez_sources =	lib/bluez/adapter.c lib/bluez/adapter.h \
+ 		lib/bluez/agent_manager.c lib/bluez/agent_manager.h \
+@@ -50,6 +50,6 @@
+ bt_device_SOURCES = $(lib_sources) $(bluez_sources) bt-device.c
+ bt_network_SOURCES = $(lib_sources) $(bluez_sources) bt-network.c
+ bt_obex_SOURCES = $(lib_sources) $(bluez_sources) bt-obex.c
+-bt_obex_LDADD = $(LIBREADLINE)
++bt_obex_LDADD = $(LDADD) $(LIBREADLINE)
+ 
+ dist_man_MANS = bt-adapter.1 bt-agent.1 bt-device.1 bt-network.1 bt-obex.1

Bug#795178: ceph FTBFS with boost1.58

[Tiago Stürmer Daitx]

Source: ceph
Version: 0.94.2
Severity: important

Dear Maintainer,

ceph currently FTBFS when compiling with boost 1.58. 

Upstream bug report and patch available at
http://tracker.ceph.com/issues/11576

Build log
=
libtool: compile: g++ -DHAVE_CONFIG_H -I. -D__CEPH__ -D_FILE_OFFSET_BITS=64 
-D_REENTRANT -D_THREAD_SAFE -D__STDC_FORMAT_MACROS -D_GNU_SOURCE 
-DCEPH_LIBDIR=\/usr/lib/x86_64-linux-gnu\ 
-DCEPH_PKGLIBDIR=\/usr/lib/x86_64-linux-gnu/ceph\ -DGTEST_HAS_TR1_TUPLE=0 
-D_FORTIFY_SOURCE=2 -I/usr/include/nss -I/usr/include/nspr -Wall -Wtype-limits 
-Wignored-qualifiers -Winit-self -Wpointer-arith -Werror=format-security 
-fno-strict-aliasing -fsigned-char -rdynamic -ftemplate-depth-1024 
-Wnon-virtual-dtor -Wno-invalid-offsetof -fno-builtin-malloc 
-fno-builtin-calloc -fno-builtin-realloc -fno-builtin-free 
-Wstrict-null-sentinel -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -c mon/MDSMonitor.cc -fPIC -DPIC -o 
mon/.libs/MDSMonitor.o
In file included from /usr/include/boost/optional/optional.hpp:28:0,
 from /usr/include/boost/optional/optional_io.hpp:19,
 from ./include/encoding.h:289,
 from ./include/uuid.h:8,
 from ./include/types.h:21,
 from mon/OSDMonitor.h:28,
 from mon/OSDMonitor.cc:21:
/usr/include/boost/variant/get.hpp: In instantiation of 'typename 
boost::add_referenceconst U::type boost::strict_get(const boost::variantT0, 
T1, T2, T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, 
T18, T19) [with U = int; T0 = std::__cxx11::basic_stringchar; T1 = bool; T2 
= long int; T3 = double; T4 = std::vectorstd::__cxx11::basic_stringchar ; 
T5 = boost::detail::variant::void_; T6 = boost::detail::variant::void_; T7 = 
boost::detail::variant::void_; T8 = boost::detail::variant::void_; T9 = 
boost::detail::variant::void_; T10 = boost::detail::variant::void_; T11 = 
boost::detail::variant::void_; T12 = boost::detail::variant::void_; T13 = 
boost::detail::variant::void_; T14 = boost::detail::variant::void_; T15 = 
boost::detail::variant::void_; T16 = boost::detail::variant::void_; T17 = 
boost::detail::variant::void_; T18 = boost::detail::variant::void_; T19 = 
boost::detail::variant::void_; typename boost::add_referenceconst U::type = 
const int]':
/usr/include/boost/variant/get.hpp:299:25: required from 'typename 
boost::add_referenceconst U::type boost::get(const boost::variantT0, T1, T2, 
T3, T4, T5, T6, T7, T8, T9, T10, T11, T12, T13, T14, T15, T16, T17, T18, T19) 
[with U = int; T0 = std::__cxx11::basic_stringchar; T1 = bool; T2 = long int; 
T3 = double; T4 = std::vectorstd::__cxx11::basic_stringchar ; T5 = 
boost::detail::variant::void_; T6 = boost::detail::variant::void_; T7 = 
boost::detail::variant::void_; T8 = boost::detail::variant::void_; T9 = 
boost::detail::variant::void_; T10 = boost::detail::variant::void_; T11 = 
boost::detail::variant::void_; T12 = boost::detail::variant::void_; T13 = 
boost::detail::variant::void_; T14 = boost::detail::variant::void_; T15 = 
boost::detail::variant::void_; T16 = boost::detail::variant::void_; T17 = 
boost::detail::variant::void_; T18 = boost::detail::variant::void_; T19 = 
boost::detail::variant::void_; typename boost::add_referenceconst U::type = 
const int]'
../common/cmdparse.h:47:26: required from 'bool cmd_getval(CephContext*, const 
cmdmap_t, std::__cxx11::string, T) [with T = int; cmdmap_t = 
std::mapstd::__cxx11::basic_stringchar, 
boost::variantstd::__cxx11::basic_stringchar, bool, long int, double, 
std::vectorstd::__cxx11::basic_stringchar   ; std::__cxx11::string = 
std::__cxx11::basic_stringchar]'
mon/OSDMonitor.cc:3002:54: required from here
/usr/include/boost/variant/get.hpp:195:5: error: invalid application of 
'sizeof' to incomplete type 'boost::STATIC_ASSERTION_FAILUREfalse'
 BOOST_STATIC_ASSERT_MSG(
 ^
make[5]: *** [mon/OSDMonitor.lo] Error 1
make[5]: *** Waiting for unfinished jobs
Makefile:16163: recipe for target 'mon/OSDMonitor.lo' failed

-- System Information:
Debian Release: jessie/sid
  APT prefers vivid-updates
  APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'), 
(100, 'vivid-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.19.0-25-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#795178: ceph FTBFS with boost1.58

[Tiago Stürmer Daitx]

Package: ceph
Followup-For: Bug #795178
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu wily ubuntu-patch

*** /tmp/tmpoh2_g2/bug_body

In Ubuntu, the attached patch was applied to achieve the following:

  * Fix compile failure with boost 1.58 (LP: #1483403, closes 795178):
- src/mon/OSDMonitor.cc: backport Ceph#11576 remove unused variable


Thanks for considering the patch.


-- System Information:
Debian Release: jessie/sid
  APT prefers vivid-updates
  APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'), 
(100, 'vivid-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.19.0-25-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru ceph-0.94.2/debian/changelog ceph-0.94.2/debian/changelog
diff -Nru ceph-0.94.2/debian/control ceph-0.94.2/debian/control
--- ceph-0.94.2/debian/control	2015-04-14 05:40:26.0 -0300
+++ ceph-0.94.2/debian/control	2015-08-11 10:58:04.0 -0300
@@ -1,8 +1,7 @@
 Source: ceph
 Section: admin
 Priority: optional
-Maintainer: Ubuntu Developers ubuntu-devel-disc...@lists.ubuntu.com
-XSBC-Original-Maintainer: Ceph Maintainers ceph-maintain...@lists.ceph.com
+Maintainer: Ceph Maintainers ceph-maintain...@lists.ceph.com
 Uploaders:
  Laszlo Boszormenyi (GCS) g...@debian.org,
  James Page jamesp...@debian.org,
diff -Nru ceph-0.94.2/debian/patches/remove-unused-variable-ceph-bug-11576.patch ceph-0.94.2/debian/patches/remove-unused-variable-ceph-bug-11576.patch
--- ceph-0.94.2/debian/patches/remove-unused-variable-ceph-bug-11576.patch	1969-12-31 21:00:00.0 -0300
+++ ceph-0.94.2/debian/patches/remove-unused-variable-ceph-bug-11576.patch	2015-08-10 18:36:43.0 -0300
@@ -0,0 +1,11 @@
+--- a/src/mon/OSDMonitor.cc
 b/src/mon/OSDMonitor.cc
+@@ -2998,8 +2998,6 @@
+   } else if (prefix == osd crush get-tunable) {
+ string tunable;
+ cmd_getval(g_ceph_context, cmdmap, tunable, tunable);
+-int value;
+-cmd_getval(g_ceph_context, cmdmap, value, value);
+ ostringstream rss;
+ if (f)
+   f-open_object_section(tunable);
diff -Nru ceph-0.94.2/debian/patches/series ceph-0.94.2/debian/patches/series
--- ceph-0.94.2/debian/patches/series	2015-04-14 05:40:26.0 -0300
+++ ceph-0.94.2/debian/patches/series	2015-08-10 18:29:45.0 -0300
@@ -11,3 +11,4 @@
 fix-argparse-defaults.patch
 fix-cycles-arch.patch
 vivid-does-systemd.patch
+remove-unused-variable-ceph-bug-11576.patch

Bug#794190: quota: failure to build on wily proposed due to wrong LDFLAGS usage

[Tiago Stürmer Daitx]

Package: quota
Version: 4.02-1.1
Severity: important
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu wily ubuntu-patch

Dear Maintainer,

quota build in Wily proposed is failing due to '-ltirpc' being added to
LDFLAGS instead of LIBS.

As stated in
https://wiki.debian.org/ToolChain/DSOLinking#Only_link_with_needed_libraries
and 
http://www.gnu.org/software/autoconf/manual/autoconf-2.60/html_node/Preset-Output-Variables.html#index-LDFLAGS-93
libraries must be added to LIBS instead of LDFLAGS.

The attached debdiff fixed the issue by:
1. Moving the '-ltirpc' entry from LDFLAGS to LIBS in debian/rules
2. Adding a $(LIBS) entry to binaries builds in Makefile.in

*** /tmp/tmpLCNYAm/bug_body

In Ubuntu, the attached patch was applied to achieve the following:
- fix Wili proposed build (FTBFS); LP: 1480047

  * Non-maintainer upload.
  * Move -ltirpc from LDFLAGS to LIBS in debian/rules
  * Add LIBS to Makefile.in 


Thanks for considering the patch.


-- System Information:
Debian Release: jessie/sid
  APT prefers vivid-updates
  APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'), 
(100, 'vivid-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.19.0-23-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -u quota-4.02/debian/changelog quota-4.02/debian/changelog
diff -u quota-4.02/debian/patches/series quota-4.02/debian/patches/series
--- quota-4.02/debian/patches/series
+++ quota-4.02/debian/patches/series
@@ -3,0 +4 @@
+tirpc-libs.diff
diff -u quota-4.02/debian/rules quota-4.02/debian/rules
--- quota-4.02/debian/rules
+++ quota-4.02/debian/rules
@@ -17,7 +17,7 @@
 	dh_quilt_patch
 	# Add here commands to configure the package.
 	( [ `dpkg --print-architecture` = powerpc ]  CFLAGSDEF += -D__BYTEORDER_HAS_U64__; \
-	  export CFLAGS=$(CFLAGS_DEF) -I/usr/include/tirpc CPPFLAGS=$(CPPFLAGS_DEF) LDFLAGS=$(LDFLAGS_DEF) -ltirpc; \
+	  export CFLAGS=$(CFLAGS_DEF) -I/usr/include/tirpc CPPFLAGS=$(CPPFLAGS_DEF) LDFLAGS=$(LDFLAGS_DEF) LIBS=-ltirpc; \
  	  ./configure --prefix=/usr --mandir=\$${prefix}/share/man --infodir=\$${prefix}/share/info --sysconfdir=/etc --enable-ext2direct=yes --enable-rpcsetquota=yes --enable-rootsbin=yes --enable-ldapmail=yes --enable-netlink=yes)
 
 	touch configure-stamp
only in patch2:
unchanged:
--- quota-4.02.orig/debian/patches/tirpc-libs.diff
+++ quota-4.02/debian/patches/tirpc-libs.diff
@@ -0,0 +1,63 @@
+--- a/Makefile.in
 b/Makefile.in
+@@ -105,47 +105,47 @@
+ 	-$(INSTALL) -m $(DEF_MAN_MODE) *.8 $(ROOTDIR)$(mandir)/man8
+ 
+ quotaon: quotaon.o quotaon_xfs.o $(LIBOBJS)
+-	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^
++	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^ $(LIBS)
+ 
+ quotacheck: quotacheck.o quotacheck_v1.o quotacheck_v2.o quotaops.o $(LIBOBJS)
+-	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^ $(EXT2LIBS)
++	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^ $(LIBS) $(EXT2LIBS)
+ 
+ quota: quota.o quotaops.o $(LIBOBJS)
+-	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^
++	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^ $(LIBS)
+ 
+ quotasync: quotasync.o $(LIBOBJS)
+-	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^
++	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^ $(LIBS)
+ 
+ quot: quot.o $(LIBOBJS)
+-	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^
++	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^ $(LIBS)
+ 
+ repquota: repquota.o $(LIBOBJS)
+-	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^
++	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^ $(LIBS)
+ 
+ warnquota: warnquota.o $(LIBOBJS)
+-	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^ $(LDAPLIBS)
++	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^ $(LIBS) $(LDAPLIBS)
+ 
+ quotastats: quotastats.o common.o pot.o
+-	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^
++	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^ $(LIBS)
+ 
+ xqmstats: xqmstats.o common.o pot.o
+-	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^
++	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^ $(LIBS)
+ 
+ edquota: edquota.o quotaops.o $(LIBOBJS)
+-	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^
++	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^ $(LIBS)
+ 
+ setquota: setquota.o quotaops.o $(LIBOBJS)
+-	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^
++	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^ $(LIBS)
+ 
+ convertquota: convertquota.o $(LIBOBJS)
+-	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^
++	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^ $(LIBS)
+ 
+ rpc.rquotad: rquota_server.o rquota_svc.o svc_socket.o $(LIBOBJS)
+ 	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^ $(LIBS)
+ 
+ ifneq ($(NETLINKLIBS),)
+ quota_nld: quota_nld.o $(LIBOBJS)
+-	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^ $(NETLINKLIBS)
++	$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^ $(LIBS) $(NETLINKLIBS)
+ endif
+ 
+ pot.o: pot.c pot.h

Bug#794009: libedit: Libraries must be added to LIBS instead of LDFLAGS

[Tiago Stürmer Daitx]

Package: libedit
Version: 3.1-20150325-1
Severity: important
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu wily ubuntu-patch

Dear Maintainer,

libedit is failing to build in Wily (proposed) due to LIBBSD_LIBS being added 
to LDFLAGS instead of LIBS.

As stated in 
https://wiki.debian.org/ToolChain/DSOLinking#Only_link_with_needed_libraries 
and 
http://www.gnu.org/software/autoconf/manual/autoconf-2.60/html_node/Preset-Output-Variables.html#index-LDFLAGS-93
 
libraries must be added to LIBS instead of LDFLAGS.

*** /tmp/tmpCmy43w/bug_body

In Ubuntu, the attached patch was applied to achieve the following:

- fix build in Wily (proposed)

  * debian/patches/libbsd.patch: use LIBS instead of LDFLAGS 


Thanks for considering the patch.


-- System Information:
Debian Release: jessie/sid
  APT prefers vivid-updates
  APT policy: (500, 'vivid-updates'), (500, 'vivid-security'), (500, 'vivid'), 
(100, 'vivid-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.19.0-23-generic (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru libedit-3.1-20150325/debian/changelog libedit-3.1-20150325/debian/changelog
diff -Nru libedit-3.1-20150325/debian/patches/libbsd.patch libedit-3.1-20150325/debian/patches/libbsd.patch
--- libedit-3.1-20150325/debian/patches/libbsd.patch	2015-04-28 04:51:33.0 -0300
+++ libedit-3.1-20150325/debian/patches/libbsd.patch	2015-07-29 14:38:41.0 -0300
@@ -1,21 +1,19 @@
-Index: libedit/configure.ac
-===
 libedit.orig/configure.ac
-+++ libedit/configure.ac
-@@ -61,6 +61,12 @@ AC_CHECK_LIB(tinfo, tgetent,,
+--- a/configure.ac
 b/configure.ac
+@@ -61,6 +61,12 @@
)]
  )
  
 +PKG_CHECK_MODULES(LIBBSD, [libbsd-overlay],
 +  [CFLAGS=$CFLAGS $LIBBSD_CFLAGS
-+   LDFLAGS=$LDFLAGS $LIBBSD_LIBS
++   LIBS=$LIBS $LIBBSD_LIBS
 +   MODULES=$MODULES libbsd
 +   AC_SUBST([MODULES])]
 +)
  
  ### use option --enable-widec to turn on use of wide-character support
  EL_ENABLE_WIDEC
-@@ -117,24 +123,32 @@ AC_PROG_GCC_TRADITIONAL
+@@ -117,24 +123,32 @@
  #AC_FUNC_REALLOC
  AC_TYPE_SIGNAL
  AC_FUNC_STAT