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:
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:
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
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;
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
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
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
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
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
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
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.
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
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)
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
: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
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
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
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
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
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
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
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
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 <<<
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
-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-r
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
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,
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
.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 201
ion 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
*
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:
+ 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
This has been fixed upstream [1], but there has been no new release so far.
[1] https://github.com/lxc/lxc/commit/66b66624fce21606d11f24f5b615776074d212ae
-thanks
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,
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
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
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
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
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
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
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
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.
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
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
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
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
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
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
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:
(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
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
] 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
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.
*
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__
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):
-
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
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
57 matches
Mail list logo
