Bug#894068: ocrmypdf: New dependency on PyMuPDF for v6.0.0

[James R. Barlow]

Package: ocrmypdf
Version: v6.0.0
Severity: serious
Tags: newcomer
Justification: fails to build from source (but built successfully in the past)

Dear Sean,

In v6.0.0, which addresses and hopefully fixes #888917, I have introduced a
new dependency on PyMuPDF (Python bindings for MuPDF).  Unfortunately PyMuPDF
isn't available in Debian as yet (I have checked there is no python3-pymupdf).

The build procedure should go like this:

  - download/unpack MuPDF to mupdf/
  - download/unpar PyMuPDF to pymupdf/
  - cp pymupdf/fitz/_mupdf_config.h mupdf/include/mupdf/fitz/config.h
  - export CFLAGS=-fPIC 
  - make HAVE_X11=no HAVE_GLFW=no HAVE_GLUT=no
  - patch pymupdf/setup.py to point library_dirs and include_dirs to the
output of mupdf/ build

The reason for this circumlocution is that the vendor of MuPDF, Artifex, 
does not provide or support dynamic libraries or a stable ABI, and 
compiling the Python bindings requires a dynamic library.  Perhaps as a way
to warn people about their stance, they don't enable -fPIC by default and
link their application statically.

This means that unfortunately, one cannot link to libmupdf-dev (and 
actually, I'm not sure if libmupdf-dev serves any purpose at all, unless 
it were rebuilt with -fPIC).  Certainly if the maintainers of this 
package could be persuaded to build it with -fPIC that would make this 
much easier.

I did try to build with it with Debian sid against the libmupdf-dev 
library. The error, as with Ubuntu, is:
  relocation R_X86_64_PC32 against symbol `fz_empty_irect' can not be 
used when making a shared object; recompile with -fPIC

The make options and replacement of the header file in mupdf are all 
disabling features unnecessary for PyMuPDF's purposes. It shrinks the 
binary from 30 MB to 3 MB.

The PyMuPDF developers describe their build process here:
https://github.com/rk700/PyMuPDF/wiki/Ubuntu-Installation-Experience

I'm happy to help with the packaging of this dependency, and I got it the
process working for Python binary wheels already.  However, I don't really
know much about Debian processes and policy.

Regards,
James

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

Kernel: Linux 4.4.119-boot2docker (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968), LANGUAGE=C 
(charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages ocrmypdf depends on:
pn  ghostscript   
pn  icc-profiles-free 
pn  liblept5  
ii  python3   3.6.5~rc1-1
pn  python3-cffi-backend-api-max  
pn  python3-cffi-backend-api-min  
pn  python3-img2pdf   
pn  python3-pil   
ii  python3-pkg-resources 39.0.1-1
pn  python3-pypdf2
pn  python3-reportlab 
pn  python3-ruffus
pn  qpdf  
pn  tesseract-ocr 
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages ocrmypdf recommends:
pn  unpaper  

Versions of packages ocrmypdf suggests:
pn  img2pdf  
pn  ocrmypdf-doc 
pn  python-watchdog  

Bug#893247: Intend to take over libjbzip2-java and libnanoxml2-java into Debian Med team

[Andreas Tille]

On Sun, Mar 25, 2018 at 11:56:18PM +0200, Emmanuel Bourg wrote:
> Le 25/03/2018 à 19:55, tony mancill a écrit :
> 
> > Multiple teams wanting to maintain a library is a good problem to have.
> > I propose we consider:
> > 
> > (a) pulling these libraries into the "Debian" project on Salsa, which
> > replaces collab-maint and grants commit permissions to all DDs and any
> > designated guest account
> 
> -1

:-)
 
> > (b) relaxing the default pkg-java permissions to be like those of the
> > Debian Perl Team and allow all DDs by default
> 
> +1, but note that this is basically how it already works today since any
> request to join the pkg-java group (or now java-team on Salsa) is always
> granted.

Same for Debian Med.  Its a bit sad that it can not easily be granted to
any DD any more to enable commits of team uploads / NMUs instantly but
require an extra step.

Kind regards

Andreas.

-- 
http://fam-tille.de

Bug#880886: marked as done (maven-bundle-plugin FTBFS with libmaven-dependency-tree-java 3.0.1-1)

[Debian Bug Tracking System]

Your message dated Sun, 25 Mar 2018 15:16:46 +0800
with message-id 
and subject line Re: maven-bundle-plugin FTBFS with 
libmaven-dependency-tree-java
has caused the Debian Bug report #880886,
regarding maven-bundle-plugin FTBFS with libmaven-dependency-tree-java 3.0.1-1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
880886: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880886
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: maven-bundle-plugin
Version: 2.5.4-6
Severity: serious

Some recent change in unstable makes maven-bundle-plugin FTBFS:

https://tests.reproducible-builds.org/debian/history/maven-bundle-plugin.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/maven-bundle-plugin.html

...
[ERROR] COMPILATION ERROR : 
[INFO] -
[ERROR] 
/build/1st/maven-bundle-plugin-2.5.4/src/main/java/org/apache/maven/shared/dependency/tree/DependencyTreeResolutionListener.java:[35,57]
 package org.apache.maven.shared.dependency.tree.traversal does not exist
[ERROR] 
/build/1st/maven-bundle-plugin-2.5.4/src/main/java/org/apache/maven/shared/dependency/tree/DependencyTreeResolutionListener.java:[68,13]
 cannot find symbol
  symbol:   class DependencyNode
  location: class 
org.apache.maven.shared.dependency.tree.DependencyTreeResolutionListener
[ERROR] 
/build/1st/maven-bundle-plugin-2.5.4/src/main/java/org/apache/maven/shared/dependency/tree/DependencyTreeResolutionListener.java:[73,13]
 cannot find symbol
  symbol:   class DependencyNode
  location: class 
org.apache.maven.shared.dependency.tree.DependencyTreeResolutionListener
[ERROR] 
/build/1st/maven-bundle-plugin-2.5.4/src/main/java/org/apache/maven/shared/dependency/tree/DependencyTreeResolutionListener.java:[402,12]
 cannot find symbol
  symbol:   class DependencyNode
  location: class 
org.apache.maven.shared.dependency.tree.DependencyTreeResolutionListener
[ERROR] 
/build/1st/maven-bundle-plugin-2.5.4/src/main/java/org/apache/maven/shared/dependency/tree/DependencyTreeResolutionListener.java:[440,13]
 cannot find symbol
  symbol:   class DependencyNode
  location: class 
org.apache.maven.shared.dependency.tree.DependencyTreeResolutionListener
[ERROR] 
/build/1st/maven-bundle-plugin-2.5.4/src/main/java/org/apache/maven/shared/dependency/tree/DependencyTreeResolutionListener.java:[464,5]
 cannot find symbol
  symbol:   class DependencyNode
  location: class 
org.apache.maven.shared.dependency.tree.DependencyTreeResolutionListener
[ERROR] 
/build/1st/maven-bundle-plugin-2.5.4/src/main/java/org/apache/maven/shared/dependency/tree/DependencyTreeResolutionListener.java:[494,13]
 cannot find symbol
  symbol:   class DependencyNode
  location: class 
org.apache.maven.shared.dependency.tree.DependencyTreeResolutionListener
[ERROR] 
/build/1st/maven-bundle-plugin-2.5.4/src/main/java/org/apache/maven/shared/dependency/tree/DependencyTreeResolutionListener.java:[550,45]
 cannot find symbol
  symbol:   class DependencyNode
  location: class 
org.apache.maven.shared.dependency.tree.DependencyTreeResolutionListener
[ERROR] 
/build/1st/maven-bundle-plugin-2.5.4/src/main/java/org/apache/felix/bundleplugin/BundleAllPlugin.java:[57,47]
 cannot find symbol
  symbol:   class DependencyNode
  location: package org.apache.maven.shared.dependency.tree
[ERROR] 
/build/1st/maven-bundle-plugin-2.5.4/src/main/java/org/apache/felix/bundleplugin/BundleAllPlugin.java:[58,47]
 cannot find symbol
  symbol:   class DependencyTreeBuilder
  location: package org.apache.maven.shared.dependency.tree
[ERROR] 
/build/1st/maven-bundle-plugin-2.5.4/src/main/java/org/apache/felix/bundleplugin/BundleAllPlugin.java:[59,47]
 cannot find symbol
  symbol:   class DependencyTreeBuilderException
  location: package org.apache.maven.shared.dependency.tree
[ERROR] 
/build/1st/maven-bundle-plugin-2.5.4/src/main/java/org/apache/felix/bundleplugin/BundleAllPlugin.java:[113,13]
 cannot find symbol
  symbol:   class DependencyTreeBuilder
  location: class org.apache.felix.bundleplugin.BundleAllPlugin
[INFO] 12 errors 
[INFO] -
[INFO] 
[INFO] 
[INFO] Skipping Maven Bundle Plugin
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] BUILD 

Bug#893988: wide-dhcpv6-client-udeb: not installable: depends on non-udeb libfl2

[Cyril Brulebois]

Control: tag -1 patch

Hi Roger,

Roger Shimizu  (2018-03-25):
> Do you have any suggestion, except adding udeb support to package flex?

It looks acceptable to me to use the static library in the udeb, so I've
tried building it against libfl.a, and that seems to do the job since
the libfl2 dependency goes away. I'm not sure it's reasonable to do that
for both the deb and the udeb, though; so I've looked into making it
conditional, and only building the udeb against the static library.

Unfortunately, it looks like the build system doesn't support out of
tree builds, so I've had to copy all files under build-{deb,udeb},
instead of just running ../configure, make, make install from there.
I've picked rsync to do this, but feel free to use anything else.

I've also chosen to clean things up using an override_dh_auto_clean
target, so that most modifications are seen at once in debian/rules, but
you may want to use debian/clean instead.

You'll find a patch series attached. I haven't tested the runtime
though.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant
From e63dad86c15e39c56505f0e22428b4d3a158b17e Mon Sep 17 00:00:00 2001
From: Cyril Brulebois 
Date: Sun, 25 Mar 2018 09:40:23 +0200
Subject: [PATCH 1/8] Build under build-deb.

This is a first step to introduce separate deb vs. udeb builds.
---
 debian/rules | 15 +--
 1 file changed, 13 insertions(+), 2 deletions(-)

diff --git a/debian/rules b/debian/rules
index 67e9104..96b2b3b 100755
--- a/debian/rules
+++ b/debian/rules
@@ -9,12 +9,19 @@ export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 %:
 	dh $@
 
-override_dh_auto_configure:
+build-deb/.stamp:
+	rsync --exclude debian/ --exclude .pc/ -a * build-deb && touch $@
+
+override_dh_auto_configure: build-deb/.stamp
+	cd build-deb && \
 	./configure --prefix=/usr --mandir=\$${prefix}/share/man \
 		--with-localdbdir=/var/lib/dhcpv6 --sysconfdir=/etc/wide-dhcpv6
 
+override_dh_auto_build:
+	$(MAKE) -C build-deb
+
 override_dh_auto_install:
-	$(MAKE) prefix=$(CURDIR)/debian/tmp/usr install
+	$(MAKE) -C build-deb prefix=$(CURDIR)/debian/tmp/usr install
 
 override_dh_installinit:
 	dh_installinit --error-handler=true --restart-after-upgrade
@@ -22,3 +29,7 @@ override_dh_installinit:
 override_dh_fixperms:
 	dh_fixperms
 	chmod +x debian/wide-dhcpv6-client/etc/wide-dhcpv6/dhcp6c-*
+
+override_dh_auto_clean:
+	dh_auto_clean
+	rm -rf build-deb
-- 
2.16.2

From 1f71d9b7fa5f05655fcfe1e7a6a974cdc18d2309 Mon Sep 17 00:00:00 2001
From: Cyril Brulebois 
Date: Sun, 25 Mar 2018 09:40:27 +0200
Subject: [PATCH 2/8] Duplicate the deb build into a udeb build.

Let the main (deb) build install everything under debian/tmp as usual
which will let most helpers do the right thing as previously, and
install the results of the udeb build under debian/tmp-udeb.
---
 debian/rules | 11 ++-
 1 file changed, 10 insertions(+), 1 deletion(-)

diff --git a/debian/rules b/debian/rules
index 96b2b3b..a9ee5a3 100755
--- a/debian/rules
+++ b/debian/rules
@@ -12,16 +12,24 @@ export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 build-deb/.stamp:
 	rsync --exclude debian/ --exclude .pc/ -a * build-deb && touch $@
 
-override_dh_auto_configure: build-deb/.stamp
+build-udeb/.stamp:
+	rsync --exclude debian/ --exclude .pc/ -a * build-udeb && touch $@
+
+override_dh_auto_configure: build-deb/.stamp build-udeb/.stamp
 	cd build-deb && \
 	./configure --prefix=/usr --mandir=\$${prefix}/share/man \
 		--with-localdbdir=/var/lib/dhcpv6 --sysconfdir=/etc/wide-dhcpv6
+	cd build-udeb && \
+	./configure --prefix=/usr --mandir=\$${prefix}/share/man \
+		--with-localdbdir=/var/lib/dhcpv6 --sysconfdir=/etc/wide-dhcpv6
 
 override_dh_auto_build:
 	$(MAKE) -C build-deb
+	$(MAKE) -C build-udeb
 
 override_dh_auto_install:
 	$(MAKE) -C build-deb prefix=$(CURDIR)/debian/tmp/usr install
+	$(MAKE) -C build-udeb prefix=$(CURDIR)/debian/tmp-udeb/usr install
 
 override_dh_installinit:
 	dh_installinit --error-handler=true --restart-after-upgrade
@@ -33,3 +41,4 @@ override_dh_fixperms:
 override_dh_auto_clean:
 	dh_auto_clean
 	rm -rf build-deb
+	rm -rf build-udeb
-- 
2.16.2

From 0e9c3a98ec202285076bb3c44d79158b17a15b38 Mon Sep 17 00:00:00 2001
From: Cyril Brulebois 
Date: Sun, 25 Mar 2018 09:47:05 +0200
Subject: [PATCH 3/8] wide-dhcpv6-client-udeb: ship the dhcp6c binary built in
 the udeb tree.

---
 debian/wide-dhcpv6-client-udeb.install | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/debian/wide-dhcpv6-client-udeb.install b/debian/wide-dhcpv6-client-udeb.install
index 0af1fb6..04fb328 100644
--- a/debian/wide-dhcpv6-client-udeb.install
+++ b/debian/wide-dhcpv6-client-udeb.install
@@ -1 +1,2 @@
-usr/sbin/dhcp6c
+# Pick the binary built in the udeb tree:
+../tmp-udeb/usr/sbin/dhcp6c /usr/sbin/
-- 
2.16.2

From 10e34fb743810dea9ffad69824e1c45e35ac6157 Mon Sep 

Processed: Re: Bug#893988: wide-dhcpv6-client-udeb: not installable: depends on non-udeb libfl2

[Debian Bug Tracking System]

Processing control commands:

> tag -1 patch
Bug #893988 [wide-dhcpv6-client-udeb] wide-dhcpv6-client-udeb: not installable: 
depends on non-udeb libfl2
Added tag(s) patch.

-- 
893988: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893988
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#893268: Help needed to build libnanoxml2-java with Java 9 (Was: Intend to take over libjbzip2-java and libnanoxml2-java into Debian Med team)

[Andreas Tille]

Control: tags -1 help

Hi,

as announced below I moved this package to Salsa in Debian Med team
area[1].  I checked the last commit of Chris West but the build time
test is failing.  I made the test output more verbose in another
commit[2].  This leads to

...
cd Test/Lite && \
/usr/lib/jvm/default-java/bin/javac -source 1.8 -nowarn -cp 
.:../../nanoxml-lite.jar `find -iname *.java` && \
for TESTFILE in *.xml; do \
/usr/lib/jvm/default-java/bin/java -cp .:../../nanoxml-lite.jar 
DumpXML_Lite ${TESTFILE} > ${TESTFILE}.test_out ; \
if diff -u ${TESTFILE}.out ${TESTFILE}.test_out ; \
thenecho nanoxml-lite.jar failed ${TESTFILE}; \
exit 1; \
fi; \
done
Note: ./DumpXML_Lite.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
nanoxml-lite.jar failed comments.xml


Unfortunately I have no idea how to fix this.  In short:  I'd happily
continue to maintain the package in the Debian Med team since it seems a
bit orphaned in Debian Java team and has only rdepends in Debian Med.
However, in this case I need help from Java experts.  If some volunteer
from Debian Java wants to take over and keep the package in Debian Java
that's perfectly fine for me and we can easily move back to Debian Java
once the packages of this team are moved to salsa.debian.org.

Kind regards

Andreas.

[1] https://salsa.debian.org/med-team/libnanoxml2-java/
[2] 
https://salsa.debian.org/med-team/libnanoxml2-java/commit/f3311f30890dffd552707565b806ab8873cf0f00

On Sun, Mar 25, 2018 at 09:35:32AM +0200, Andreas Tille wrote:
> Hi,
> 
> due to recently opened bugs (#893247 and #893268) I stumbled upon
> libjbzip2-java and libnanoxml2-java packages.  Both have rdepends
> of Debian Med packages.  Libjbzip2-java is maintained by Debian Med
> members anyway and libnanoxml2-java had the last maintainer upload
> in 2010.  I consider the packages both better "observed" in Debian
> Med team and will take both over to salsa.debian.org/med-team.
> 
> I hope this is OK for everybody.
> 
> Kind regards
> 
>Andreas.
> 
> -- 
> http://fam-tille.de

-- 
http://fam-tille.de

Processed: fixed-upstream

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 893821 https://github.com/geemus/shindo/pull/17
Bug #893821 [src:ruby-shindo] ruby-shindo FTBFS with Ruby 2.5
Set Bug forwarded-to-address to 'https://github.com/geemus/shindo/pull/17'.
> tags 893821 +fixed-upstream
Bug #893821 [src:ruby-shindo] ruby-shindo FTBFS with Ruby 2.5
Added tag(s) fixed-upstream.
> forwarded 893823 
> https://github.com/jeremyevans/minitest-shared_description/commit/c59037f6ec
Bug #893823 [src:ruby-minitest-shared-description] 
ruby-minitest-shared-description FTBFS with Ruby 2.5
Set Bug forwarded-to-address to 
'https://github.com/jeremyevans/minitest-shared_description/commit/c59037f6ec'.
> tags 893823 +fixed-upstream
Bug #893823 [src:ruby-minitest-shared-description] 
ruby-minitest-shared-description FTBFS with Ruby 2.5
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
893821: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893821
893823: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893823
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#880886: maven-bundle-plugin FTBFS with libmaven-dependency-tree-java

[殷啟聰 | Kai-Chung Yan]

forwarded -1 https://issues.apache.org/jira/browse/FELIX-5795



signature.asc
Description: OpenPGP digital signature

Processed: Re: maven-bundle-plugin FTBFS with libmaven-dependency-tree-java

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://issues.apache.org/jira/browse/FELIX-5795
Bug #880886 [src:maven-bundle-plugin] maven-bundle-plugin FTBFS with 
libmaven-dependency-tree-java 3.0.1-1
Set Bug forwarded-to-address to 
'https://issues.apache.org/jira/browse/FELIX-5795'.

-- 
880886: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880886
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#880886: maven-bundle-plugin FTBFS with libmaven-dependency-tree-java

[殷啟聰 | Kai-Chung Yan]

Control:  forwarded -1 https://issues.apache.org/jira/browse/FELIX-5795



signature.asc
Description: OpenPGP digital signature

Processed: Help needed to build libnanoxml2-java with Java 9 (Was: Intend to take over libjbzip2-java and libnanoxml2-java into Debian Med team)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 help
Bug #893268 [src:libnanoxml2-java] libnanoxml2-java FTBFS with openjdk-9
Added tag(s) help.

-- 
893268: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893268
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: wtforms upstream bug

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 893883 https://github.com/wtforms/wtforms/issues/373
Bug #893883 [src:wtforms] wtforms FTBFS with sqlalchemy 1.2.5+ds1-1
Set Bug forwarded-to-address to 'https://github.com/wtforms/wtforms/issues/373'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
893883: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893883
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#894019: ftools-fv: make distclean deletes tcltk/pow/pkgIndex.tcl which is not regenerated

[Andreas Beckmann]

Source: ftools-fv
Version: 5.4+dfsg-3~exp
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

ftools-fv FTBFS twice in a row. The first build succeeds, but the
subsequent debian/rules clean causes tcltk/pow/pkgIndex.tcl to be
deleted, which is not regenerated during the second build.

>From the attached logfile:

[first build skipped]

 fakeroot debian/rules clean
dh clean
   debian/rules override_dh_auto_clean
make[1]: Entering directory '/build/ftools-fv-5.4+dfsg'
fgrep -q WCSLIB_OBJ_TMP tcltk/pow/Makefile || dh_auto_clean -D tcltk/pow
cd tcltk/pow && make -j4 -O distclean
make[2]: Entering directory '/build/ftools-fv-5.4+dfsg/tcltk/pow'
rm -rf *.o *~ libpow.a libpow.so pkgIndex.tcl so_locations
make[2]: Leaving directory '/build/ftools-fv-5.4+dfsg/tcltk/pow'
make[2]: Entering directory '/build/ftools-fv-5.4+dfsg/tcltk/pow'
rm -f config.cache config.status config.log Makefile
make[2]: Leaving directory '/build/ftools-fv-5.4+dfsg/tcltk/pow'
make[1]: Leaving directory '/build/ftools-fv-5.4+dfsg'
   dh_autoreconf_clean
   dh_clean

 dpkg-source -b ftools-fv-5.4+dfsg
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building ftools-fv using existing 
./ftools-fv_5.4+dfsg.orig.tar.gz
dpkg-source: warning: ignoring deletion of file tcltk/pow/pkgIndex.tcl, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file tcltk/pow/configure, use 
--include-removal to override
dpkg-source: warning: ignoring deletion of file tcltk/pow/Makefile, use 
--include-removal to override
dpkg-source: info: building ftools-fv in ftools-fv_5.4+dfsg-3~exp.debian.tar.xz
dpkg-source: info: building ftools-fv in ftools-fv_5.4+dfsg-3~exp.dsc

 debian/rules build
dh build
[...]
   create-stamp debian/debhelper-build-stamp

 fakeroot debian/rules binary
dh binary
   dh_testroot
   dh_prep
   debian/rules override_dh_auto_install
make[1]: Entering directory '/build/ftools-fv-5.4+dfsg'
dh_auto_install -D tcltk/pow
cd tcltk/pow && make -j4 -O install 
DESTDIR=/build/ftools-fv-5.4\+dfsg/debian/tmp AM_UPDATE_INFO_DIR=no
make[2]: Entering directory '/build/ftools-fv-5.4+dfsg/tcltk/pow'
mkdir /build/ftools-fv-5.4+dfsg/debian/tmp/usr/lib/tcltk/i386-linux-gnu/POW
cp libpow.so 
/build/ftools-fv-5.4+dfsg/debian/tmp/usr/lib/tcltk/i386-linux-gnu/POW/
cp: cannot stat 'pkgIndex.tcl': No such file or directory
Makefile:85: recipe for target 'install' failed
make[2]: *** [install] Error 1
make[2]: Leaving directory '/build/ftools-fv-5.4+dfsg/tcltk/pow'
dh_auto_install: cd tcltk/pow && make -j4 -O install 
DESTDIR=/build/ftools-fv-5.4\+dfsg/debian/tmp AM_UPDATE_INFO_DIR=no returned 
exit code 2
debian/rules:18: recipe for target 'override_dh_auto_install' failed
make[1]: *** [override_dh_auto_install] Error 25
make[1]: Leaving directory '/build/ftools-fv-5.4+dfsg'
debian/rules:6: recipe for target 'binary' failed
make: *** [binary] Error 2


I also noticed this error while the package is configured:

checking for gethostbyname... ./configure: line 1514: ac_fn_c_try_link: command 
not found
no

looks like an error in some autotools scripts ...


Andreas


ftools-fv_5.4+dfsg-3~exp_twice.log.gz
Description: application/gzip

Bug#893247: marked as done (libjbzip2-java FTBFS with openjdk-9)

[Debian Bug Tracking System]

Your message dated Sun, 25 Mar 2018 08:51:18 +
with message-id 
and subject line Bug#893247: fixed in libjbzip2-java 0.9.1-4
has caused the Debian Bug report #893247,
regarding libjbzip2-java FTBFS with openjdk-9
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
893247: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893247
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libjbzip2-java
Version: 0.9.1-3
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libjbzip2-java.html

...
   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/1st/libjbzip2-java-0.9.1'
mkdir -p build/org/itadaki/bzip2
javac -source 1.5 -target 1.5 -d build src/org/itadaki/bzip2/*.java
warning: [options] bootstrap class path not set in conjunction with -source 1.5
error: Source option 1.5 is no longer supported. Use 1.6 or later.
error: Target option 1.5 is no longer supported. Use 1.6 or later.
make[1]: *** [debian/rules:12: override_dh_auto_build] Error 2
--- End Message ---
--- Begin Message ---
Source: libjbzip2-java
Source-Version: 0.9.1-4

We believe that the bug you reported is fixed in the latest version of
libjbzip2-java, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 893...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated libjbzip2-java package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 25 Mar 2018 09:58:44 +0200
Source: libjbzip2-java
Binary: libjbzip2-java
Architecture: source
Version: 0.9.1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 libjbzip2-java - bzip2 compression/decompression library
Closes: 893247
Changes:
 libjbzip2-java (0.9.1-4) unstable; urgency=medium
 .
   * Team upload
   * Moved the package from pkg-java SVN to Debian Med team Git
   * Upstream was moved from googlecode to Github
   * cme fix dpkg-control
   * debhelper 11
   * cme fix dpkg-copyright
   * Remove outdated README.source and README.Debian
   * d/rules: remove unneeded get-orig-source target
   * Fix encoding
   * d/control: s/${shlibs:Depends}/${java:Depends}/
   * d/rules: Drop explicit specification of source and target version
 Closes: #893247
Checksums-Sha1:
 64911791b847349a782e27d63599c5416447bf9c 2053 libjbzip2-java_0.9.1-4.dsc
 a0ae565905d47c1d25bb4d5e4ac841e1fcf3e463 3116 
libjbzip2-java_0.9.1-4.debian.tar.xz
 9d3fba3a364c22502d54915a4fb88cbefa5a9876 14694 
libjbzip2-java_0.9.1-4_source.buildinfo
Checksums-Sha256:
 2e51c07a1e467225bf55e8f8233de1deb53af40d40a073e5cc3e4b822e2f1f4e 2053 
libjbzip2-java_0.9.1-4.dsc
 b12fb5620e09104f1a07cbfb77464dc497e30b6ff58fa81098cc75d0479be15b 3116 
libjbzip2-java_0.9.1-4.debian.tar.xz
 625bc2b10c3cc5af738bad8ad76a05764298e302653dd1963f715d1a34bc7241 14694 
libjbzip2-java_0.9.1-4_source.buildinfo
Files:
 22eb81c0efc39e6f2c9039215f17bcd9 2053 java optional libjbzip2-java_0.9.1-4.dsc
 a418e150a3b9c48e8737e571b74a94ff 3116 java optional 
libjbzip2-java_0.9.1-4.debian.tar.xz
 90b5d229df23e33dca9d34ca33600104 14694 java optional 
libjbzip2-java_0.9.1-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJCBAEBCAAsFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlq3WTcOHHRpbGxlYUBy
a2kuZGUACgkQV4oElNHGRtGnDA/7BhCixgM4cU0Idduqq+yda3mojUCPZ/iss1ng
6YWajywRBWdl8vXngVvZrotKSRyhd9TW2A3p67cGbF+AadZCiecgZZWFIQGjHhO9
uVpX4SQnqBypUBuBBOen2WegfeY2/y5a4e7UD9YTA+xsMjlN1b7vAeIE+7vJfNKE
aIhSX00MVca8+v+ZlrSTkXr6/Tsj1e0OBpKHcXQNxqNBgQFRH3y4o1M2WFWR/q/D
yfVEGo6HJKdGqLu9W8wV/JjtwvJDndCpVxTvIlQ99OuZLy15/3HsN3IDEuYvY0Mf
MPsZgWxEDQfgSBMcH95FdE5wmr3gGUSR1YNatgiKXepRebTnbHCyCaPgzJW7rhRd
huVIR4hmqEdBCHymaJ45nfN8jKflERjdDMMa6t56vmIbPYT8ioMjaeRA1aOyuQK8
qauEIuNCsitM9j4vQErD/9TTxh7BjblbQJheaieUgexJIicBsR9iwhCLRqqAj6/0
29kKV5XCJGfOQbxqWgFEO+Gx6/Odn/6eM4xjpbJQWg17s4B+j08+m+ZXE00rX0Xe
l1XG/t1o7RrI99g70/HBr3e5pte5rtbzMZajF23S6iiF+WfUrhrz0lCECHga1Rnx
pQXiIPLkv+YXHbu/XLb5TEW8pkIQRfBAkinr7bouhix5iy4NEjq5u40+q0cHsjVs
RPzB6wI=

Bug#893735: marked as done (paraview FTBFS on armel/armhf: QVTKOpenGLWidget.cxx:458:3: error: 'QOpenGLFunctions_3_2_Core' was not declared in this scope)

[Debian Bug Tracking System]

Your message dated Sun, 25 Mar 2018 10:20:12 +
with message-id 
and subject line Bug#893735: fixed in paraview 5.4.1+dfsg4-2
has caused the Debian Bug report #893735,
regarding paraview FTBFS on armel/armhf: QVTKOpenGLWidget.cxx:458:3: error: 
'QOpenGLFunctions_3_2_Core' was not declared in this scope
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
893735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893735
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: paraview
Version: 5.4.1+dfsg4-1
Severity: serious

https://buildd.debian.org/status/package.php?p=paraview=sid

...
/<>/paraview-5.4.1+dfsg4/VTK/GUISupport/Qt/QVTKOpenGLWidget.cxx: In 
member function 'virtual void QVTKOpenGLWidget::paintGL()':
/<>/paraview-5.4.1+dfsg4/VTK/GUISupport/Qt/QVTKOpenGLWidget.cxx:458:3:
 error: 'QOpenGLFunctions_3_2_Core' was not declared in this scope
   QOpenGLFunctions_3_2_Core* f =
   ^
/<>/paraview-5.4.1+dfsg4/VTK/GUISupport/Qt/QVTKOpenGLWidget.cxx:458:3:
 note: suggested alternative: 'QOpenGLFunctionsPrivate'
   QOpenGLFunctions_3_2_Core* f =
   ^
   QOpenGLFunctionsPrivate
/<>/paraview-5.4.1+dfsg4/VTK/GUISupport/Qt/QVTKOpenGLWidget.cxx:458:30:
 error: 'f' was not declared in this scope
   QOpenGLFunctions_3_2_Core* f =
  ^
/<>/paraview-5.4.1+dfsg4/VTK/GUISupport/Qt/QVTKOpenGLWidget.cxx:459:83:
 error: no matching function for call to 
'QOpenGLContext::versionFunctions()'
 
QOpenGLContext::currentContext()->versionFunctions();

   ^
In file included from 
/usr/include/arm-linux-gnueabihf/qt5/QtGui/QOpenGLContext:1:0,
 from 
/<>/paraview-5.4.1+dfsg4/VTK/GUISupport/Qt/QVTKOpenGLWidget.cxx:18:
/usr/include/arm-linux-gnueabihf/qt5/QtGui/qopenglcontext.h:193:11: note: 
candidate: template TYPE* QOpenGLContext::versionFunctions() const
 TYPE *versionFunctions() const
   ^~~~
/usr/include/arm-linux-gnueabihf/qt5/QtGui/qopenglcontext.h:193:11: note:   
template argument deduction/substitution failed:
VTK/GUISupport/Qt/CMakeFiles/vtkGUISupportQt.dir/build.make:453: recipe for 
target 
'VTK/GUISupport/Qt/CMakeFiles/vtkGUISupportQt.dir/QVTKOpenGLWidget.cxx.o' failed
make[3]: *** 
[VTK/GUISupport/Qt/CMakeFiles/vtkGUISupportQt.dir/QVTKOpenGLWidget.cxx.o] Error 
1


On armel/armhf (and on arm64 in Ubuntu) Qt is compiled for OpenGL ES
instead of full OpenGL.

This is caused by:
https://gitlab.kitware.com/vtk/vtk/commit/53c566782950cd94ccd877cb906607e4cc33e1f7

The following fixes the build:

--- paraview-5.4.1+dfsg4.orig/VTK/GUISupport/Qt/QVTKOpenGLWidget.cxx
+++ paraview-5.4.1+dfsg4/VTK/GUISupport/Qt/QVTKOpenGLWidget.cxx
@@ -19,7 +19,7 @@
 #include 
 #include 
 #include 
-#include 
+//#include 
 #include 
 #include 
 #include 
@@ -453,6 +453,7 @@ void QVTKOpenGLWidget::paintGL()
   // before proceeding with blit-ing.
   this->makeCurrent();
 
+#if 0
   // blit from this->FBO to QOpenGLWidget's FBO.
   vtkQVTKOpenGLWidgetDebugMacro("paintGL::blit-to-defaultFBO");
   QOpenGLFunctions_3_2_Core* f =
@@ -485,6 +486,7 @@ void QVTKOpenGLWidget::paintGL()
 f->glColorMask(colorMask[0], colorMask[1], colorMask[2], colorMask[3]);
 f->glClearColor(clearColor[0], clearColor[1], clearColor[2], 
clearColor[3]);
   }
+#endif  /* 0 */
 }
 
 //-


This is obviously not a patch that should be applied,
it serves only to show that it is really just a small piece
of recently added code that prevents compilation here.

If possible, this should be fixed.


In case fixing is not possible or desirable, please:
- change the build dependency from libqt5opengl5-dev
  to libqt5opengl5-desktop-dev, and
- file a removal bug for the old armel+armhf binaries
  against ftp.debian.org
--- End Message ---
--- Begin Message ---
Source: paraview
Source-Version: 5.4.1+dfsg4-2

We believe that the bug you reported is fixed in the latest version of
paraview, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 893...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Gert Wollny  (supplier of updated paraview package)

(This message was 

Processed: Re: lcm FTBFS with openjdk-9

[Debian Bug Tracking System]

Processing control commands:

> tags -1 fixed-upstream
Bug #893552 [src:lcm] lcm FTBFS with openjdk-9
Added tag(s) fixed-upstream.

-- 
893552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893552
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#893247: Intend to take over libjbzip2-java and libnanoxml2-java into Debian Med team

[Andreas Tille]

Hi,

due to recently opened bugs (#893247 and #893268) I stumbled upon
libjbzip2-java and libnanoxml2-java packages.  Both have rdepends
of Debian Med packages.  Libjbzip2-java is maintained by Debian Med
members anyway and libnanoxml2-java had the last maintainer upload
in 2010.  I consider the packages both better "observed" in Debian
Med team and will take both over to salsa.debian.org/med-team.

I hope this is OK for everybody.

Kind regards

   Andreas.

-- 
http://fam-tille.de

Bug#893215: marked as done (jodconverter-cli FTBFS with openjdk-9)

[Debian Bug Tracking System]

Your message dated Sun, 25 Mar 2018 11:11:16 +0200
with message-id <20180325091116.iugrvtb7wcujb...@var.youpi.perso.aquilenet.fr>
and subject line Re: jodconverter-cli FTBFS with openjdk-9
has caused the Debian Bug report #893215,
regarding jodconverter-cli FTBFS with openjdk-9
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
893215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893215
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jodconverter-cli
Version: 2.2.2-9
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/jodconverter-cli.html

...
   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/1st/jodconverter-cli-2.2.2'
cd src/main/java && \
javac -source 1.5 -target 1.5 -classpath 
/usr/share/java/commons-cli.jar:/usr/share/java/commons-io.jar:/usr/share/java/jodconverter.jar
 `find . -name \*.java` && \
jar c `find . -name \*.class -o -name \*.xml -o -name \*.MF` > 
jodconverter-cli-2.2.2.jar ; \

warning: [options] bootstrap class path not set in conjunction with -source 1.5
error: Source option 1.5 is no longer supported. Use 1.6 or later.
error: Target option 1.5 is no longer supported. Use 1.6 or later.
make[1]: *** [debian/rules:17: override_dh_auto_build] Error 2
--- End Message ---
--- Begin Message ---
Version: 2.2.2-10--- End Message ---

Bug#893552: lcm FTBFS with openjdk-9

[Juhani Numminen]

Control: tags -1 fixed-upstream

On Mon, 19 Mar 2018 22:44:53 +0200 Adrian Bunk  wrote:
> Source: lcm
> Version: 1.3.1+repack1-1
...

> error: Source option 1.5 is no longer supported. Use 1.6 or later.
> error: Target option 1.5 is no longer supported. Use 1.6 or later.

Latest upstream git version is using 1.6.
https://github.com/lcm-proj/lcm/blob/master/lcm-java/CMakeLists.txt#L3

Bug#891547: cairo: test runs into buildd timeout without fpu

[Hugh McMaster]

Hi,

Where are we at with this bug? As things are, it is blocking migration to 
testing.

Thanks

Processed: limit source to cenon.app, tagging 892981

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> limit source cenon.app
Limiting to bugs with field 'source' containing at least one of 'cenon.app'
Limit currently set to 'source':'cenon.app'

> tags 892981 + pending
Bug #892981 [src:cenon.app] cenon.app: Incomplete debian/copyright?
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
892981: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892981
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: bug 893525 is forwarded to http://lists.gnu.org/archive/html/bug-gnu-utils/2018-02/msg00004.html

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 893525 
> http://lists.gnu.org/archive/html/bug-gnu-utils/2018-02/msg4.html
Bug #893525 {Done: Santiago Vila } [src:sharutils] 
CVE-2018-197
Set Bug forwarded-to-address to 
'http://lists.gnu.org/archive/html/bug-gnu-utils/2018-02/msg4.html'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
893525: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893525
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Pending fixes for bugs in the golang-github-jacobsa-crypto package

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tag 891557 + pending
Bug #891557 {Done: Felix Lechner } [src:gocryptfs] 
gocryptfs FTBFS: src/github.com/jacobsa/crypto/cmac/hash.go:97:3: undefined: 
xorBlock
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
891557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891557
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#894025: python-certbot-dns-cloudflare: Fails to build from source

[Andrew Starr-Bochicchio]

On Sun, Mar 25, 2018 at 9:47 AM, Jeremy Bicha  wrote:
>
> error: [Errno 2] No such file or directory:
> '/usr/lib/python3/dist-packages/certbot/tests/testdata/rsa512_key.pem'
>
> Full build log at
> https://launchpad.net/ubuntu/+source/python-certbot-dns-
> cloudflare/0.22.0-1/+build/14491162
>

Looks like this was caused by this change in the main certbot package:

https://salsa.debian.org/letsencrypt-team/certbot/certbot/commit/8bb2938afb15594cb79f8661d951724323f0e754

Harlan, any more context on that or concerns about reverting?

Thanks,

-- Andrew Starr-Bochicchio

   Debian Developer 
   Ubuntu Developer 
   PGP/GPG Key ID: 3B56E2BBD53FDCB1

Bug#853410: marked as done (galera-3: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Sun, 25 Mar 2018 12:05:06 +
with message-id 
and subject line Bug#853410: fixed in galera-3 25.3.23-1
has caused the Debian Bug report #853410,
regarding galera-3: ftbfs with GCC-7
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
853410: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853410
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:galera-3
Version: 25.3.19-2
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/galera-3_25.3.19-2_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-7/porting_to.html

[...]
  |
  |int
  |main() {
  |  
  |return 0;
  |}
  |
gcc -o .sconf_temp/conftest_17.o -c -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -std=c99 -fno-strict-aliasing -pipe -g -O3 -DNDEBUG 
-m64 -pthread -Wall -Wextra -Wno-unused-parameter -Werror -pedantic -Wdate-time 
-D_FORTIFY_SOURCE=2 -D_XOPEN_SOURCE=600 -DHAVE_COMMON_H -DGALERA_USE_GU_NETWORK 
-DHAVE_BYTESWAP_H -DHAVE_ENDIAN_H -DHAVE_EXECINFO_H -DHAVE_BOOST_SHARED_PTR_HPP 
-DHAVE_TR1_UNORDERED_MAP -DBOOST_DATE_TIME_POSIX_TIME_STD_CONFIG=1 
-DHAVE_SYSTEM_ASIO -DHAVE_ASIO_HPP -DHAVE_ASIO_SSL_HPP .sconf_temp/conftest_17.c
gcc -o .sconf_temp/conftest_17 -Wl,-z,relro .sconf_temp/conftest_17.o -lpthread 
-lrt -lssl -lcrypto -lcheck -lm
scons: Configure: yes

scons: Configure: Checking for C library subunit... 
.sconf_temp/conftest_18.c <-
  |
  |
  |
  |int
  |main() {
  |  
  |return 0;
  |}
  |
gcc -o .sconf_temp/conftest_18.o -c -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -std=c99 -fno-strict-aliasing -pipe -g -O3 -DNDEBUG 
-m64 -pthread -Wall -Wextra -Wno-unused-parameter -Werror -pedantic -Wdate-time 
-D_FORTIFY_SOURCE=2 -D_XOPEN_SOURCE=600 -DHAVE_COMMON_H -DGALERA_USE_GU_NETWORK 
-DHAVE_BYTESWAP_H -DHAVE_ENDIAN_H -DHAVE_EXECINFO_H -DHAVE_BOOST_SHARED_PTR_HPP 
-DHAVE_TR1_UNORDERED_MAP -DBOOST_DATE_TIME_POSIX_TIME_STD_CONFIG=1 
-DHAVE_SYSTEM_ASIO -DHAVE_ASIO_HPP -DHAVE_ASIO_SSL_HPP .sconf_temp/conftest_18.c
gcc -o .sconf_temp/conftest_18 -Wl,-z,relro .sconf_temp/conftest_18.o -lpthread 
-lrt -lssl -lcrypto -lcheck -lm -lsubunit
scons: Configure: yes

scons: Configure: Checking for C library rt... 
.sconf_temp/conftest_19.c <-
  |
  |
  |
  |int
  |main() {
  |  
  |return 0;
  |}
  |
gcc -o .sconf_temp/conftest_19.o -c -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -std=c99 -fno-strict-aliasing -pipe -g -O3 -DNDEBUG 
-m64 -pthread -Wall -Wextra -Wno-unused-parameter -Werror -pedantic -Wdate-time 
-D_FORTIFY_SOURCE=2 -D_XOPEN_SOURCE=600 -DHAVE_COMMON_H -DGALERA_USE_GU_NETWORK 
-DHAVE_BYTESWAP_H -DHAVE_ENDIAN_H -DHAVE_EXECINFO_H -DHAVE_BOOST_SHARED_PTR_HPP 
-DHAVE_TR1_UNORDERED_MAP -DBOOST_DATE_TIME_POSIX_TIME_STD_CONFIG=1 
-DHAVE_SYSTEM_ASIO -DHAVE_ASIO_HPP -DHAVE_ASIO_SSL_HPP .sconf_temp/conftest_19.c
gcc -o .sconf_temp/conftest_19 -Wl,-z,relro .sconf_temp/conftest_19.o -lpthread 
-lrt -lssl -lcrypto -lcheck -lm -lsubunit -lrt
scons: Configure: yes


*
if [ -f FAIL ]; then exit 1; fi
debian/rules:28: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 1
make[1]: Leaving directory '/<>'
debian/rules:48: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
--- End Message ---
--- 

Processed: limit source to lynkeos.app, tagging 893442

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> limit source lynkeos.app
Limiting to bugs with field 'source' containing at least one of 'lynkeos.app'
Limit currently set to 'source':'lynkeos.app'

> tags 893442 + pending
Bug #893442 [src:lynkeos.app] lynkeos.app: FTBFS on ppc64el: AltiVec argument 
passed to unprototyped function
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
893442: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893442
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: affects 892181

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # There is no Ncurses-Ruby package installed which is needed by TPP.
> affects 892181 + tpp
Bug #892181 [ruby-ncurses] ruby-ncurses fails to load with Ruby 2.5
Added indication that 892181 affects tpp
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
892181: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892181
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#855251: easytag corrupt ogg files

[James Cowgill]

Hi,

On 03/01/18 16:50, James Cowgill wrote:
> On 16/02/17 01:02, Samuele Battarra wrote:
>> Package: easytag
>> Version: 2.4.3-1
>> Severity: normal
>>
>> Dear Maintainer,
>> I have a ogg file encoded from a live cd, I split it to single tracks with 
>> oggsplt and then tag the tracks with easytag.
>> When I play the files I hear a click at file change.
>> The click is not present in files before the tagging and if I tag with kid3.
> 
> As you might have noticed, I have decided that the best way to fix this
> is to disable support for OGG and related media types in easytag for the
> time being. Solving this bug is apparently quite complex and while the
> upstream bug has been open for over a year, there has not been much
> progress on it. I think it is better to have some version in buster
> (which does not mangle your media files) than nothing at all.

I have just uploaded easytag 2.4.3-4 which reverts an upstream commit
which I think will fix this (you will need to wait a few hours before it
appears on the mirrors). It would be very useful if people could test it
for me before I upload the fix to stable.

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#894025: python-certbot-dns-cloudflare: Fails to build from source

[Jeremy Bicha]

Source: python-certbot-dns-cloudflare
Version: 0.22.0-1
Severity: serious
X-Debbugs-CC: a...@debian.org

python-certbot-dns-cloudflare fails to build from source in a clean
sid chroot. During the build tests, there is this error:

error: [Errno 2] No such file or directory:
'/usr/lib/python3/dist-packages/certbot/tests/testdata/rsa512_key.pem'

Full build log at
https://launchpad.net/ubuntu/+source/python-certbot-dns-cloudflare/0.22.0-1/+build/14491162

This issue also affects these packages:

python-certbot-dns-dnsimple
python-certbot-dns-digitalocean
python-certbot-dns-rfc2136

The Google package works though!

Thanks,
Jeremy Bicha

Bug#893988: wide-dhcpv6-client-udeb: not installable: depends on non-udeb libfl2

[Cyril Brulebois]

Hey,

Roger Shimizu  (2018-03-25):
> On Sun, Mar 25, 2018 at 11:15 PM, Roger Shimizu  
> wrote:
> > Just a nitpicking.
> > The build cannot be triggered again by "dpkg-buildpackage -uc -us"
> > after one build.
> > It was OK in previous version.
> 
> I tested it again, and the problem is gone now.
> Sorry for the false positive info. Bow!

I had tested that and I wasn't able to reproduce this. Maybe what
happened is you had a build with the build-deb directory, you renamed
it build, and there were stray files from the previous build?

You may want to push your tree to git too (I tried git fetch but found
no new commits there). ;)

Thanks for your swift actions, much appreciated!


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant


signature.asc
Description: PGP signature

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 893554 https://github.com/ericniebler/range-v3/issues/812
Bug #893554 [src:range-v3] range-v3 FTBFS
Set Bug forwarded-to-address to 
'https://github.com/ericniebler/range-v3/issues/812'.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
893554: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893554
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#893988: marked as done (wide-dhcpv6-client-udeb: not installable: depends on non-udeb libfl2)

[Debian Bug Tracking System]

Your message dated Sun, 25 Mar 2018 15:14:29 +
with message-id 
and subject line Bug#893988: fixed in wide-dhcpv6 20080615-21
has caused the Debian Bug report #893988,
regarding wide-dhcpv6-client-udeb: not installable: depends on non-udeb libfl2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
893988: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893988
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wide-dhcpv6-client-udeb
Version: 20080615-20
Severity: serious

(Please keep debian-b...@lists.debian.org and me in copy of your
replies.)

Hi,

Your package is no longer installable because it depends on non-udeb
libfl2. That makes netcfg uninstallable as well, which means a very
serious regression for d-i.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant
--- End Message ---
--- Begin Message ---
Source: wide-dhcpv6
Source-Version: 20080615-21

We believe that the bug you reported is fixed in the latest version of
wide-dhcpv6, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 893...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Roger Shimizu  (supplier of updated wide-dhcpv6 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 25 Mar 2018 22:44:40 +0900
Source: wide-dhcpv6
Binary: wide-dhcpv6-server wide-dhcpv6-client wide-dhcpv6-client-udeb 
wide-dhcpv6-relay
Architecture: source
Version: 20080615-21
Distribution: unstable
Urgency: medium
Maintainer: Roger Shimizu 
Changed-By: Roger Shimizu 
Description:
 wide-dhcpv6-client - DHCPv6 client for automatic IPv6 hosts configuration
 wide-dhcpv6-client-udeb - DHCPv6 client for automatic IPv6 hosts configuration 
(udeb)
 wide-dhcpv6-relay - DHCPv6 relay for automatic IPv6 hosts configuration
 wide-dhcpv6-server - DHCPv6 server for automatic IPv6 hosts configuration
Closes: 893988
Changes:
 wide-dhcpv6 (20080615-21) unstable; urgency=medium
 .
   [ Cyril Brulebois ]
   * debian/rules:
 - Introduce separate deb/udeb builds, copying source files under
   {build,build-udeb} since support for out-of-tree build seems
   broken.
 - Don't try to build only the dhcp6c binary in the udeb tree, as the
   install target tries to install everything anyway.
 - Patch Makefile.in to build the dhcp6c binary against static flex
   library in the udeb tree, to avoid a runtime dependency on libfl2
   (Closes: #893988).
   * debian/wide-dhcpv6-client-udeb.install:
 - Update to pick the dhcp6c binary built in the udeb tree and
   installed under the debian/tmp-udeb directory.
   * debian/patches/0017-Remove-unused-linking-with-libfl.patch:
 - Add a comment mentioning the tweak for the udeb build.
   * debian/control:
 - Add a build-dep on rsync for the build tree handling.
Checksums-Sha1:
 704046271cf95e9446f085abb972f1a987c4938a 2189 wide-dhcpv6_20080615-21.dsc
 e5e11e7ebf9c8be0780e2672209ab16d4d6a9251 66468 
wide-dhcpv6_20080615-21.debian.tar.xz
 6db11798162142ee862cf93f36aa61be19df5e45 5964 
wide-dhcpv6_20080615-21_source.buildinfo
Checksums-Sha256:
 139d0865b1fa567beb54765a63fcdba58b9bc05eb43ee48deb937bea7fec7bd7 2189 
wide-dhcpv6_20080615-21.dsc
 7eba369fe9db3c06c7aefb097321ae030174deaf6b1f1a812ce82d4938dc619c 66468 
wide-dhcpv6_20080615-21.debian.tar.xz
 f3db4b914b59ded904e5eee9451e8fead89bf245eca83575d63f6c568309f7ea 5964 
wide-dhcpv6_20080615-21_source.buildinfo
Files:
 ab45088010257cf8cd6dc8ae06d6e84f 2189 net optional wide-dhcpv6_20080615-21.dsc
 2c7b34145b690f1bc295dd1f3ac3b92c 66468 net optional 
wide-dhcpv6_20080615-21.debian.tar.xz
 e4d563ec338d2bff81900bbc0769a5e9 5964 net optional 
wide-dhcpv6_20080615-21_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJLBAEBCgA1FiEECjKtvoA5m+cWOFnspHhrDacDNKgFAlq3qMgXHHJvZ2Vyc2hp
bWl6dUBnbWFpbC5jb20ACgkQpHhrDacDNKiN3hAAjCw9U6GVFAWNbLApOcUlwazs
wlA4Lt0FnrBZ+lGS76NtTDpZggSy/Nx+RBOvOIW+0HuljuVVS7/J9yRWiq475Seh

Bug#892510: marked as done (python-distutils-extra FTBFS: FAIL: test_apport_hook)

[Debian Bug Tracking System]

Your message dated Sun, 25 Mar 2018 14:07:56 +0200
with message-id <20180325120756.ga1...@piware.de>
and subject line Re: Bug#892510: python-distutils-extra FTBFS: FAIL: 
test_apport_hook
has caused the Debian Bug report #892510,
regarding python-distutils-extra FTBFS: FAIL: test_apport_hook
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
892510: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892510
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-distutils-extra
Version: 2.40
Severity: serious
Tags: buster sid

Some recent change in unstable makes python-distutils-extra FTBFS:

https://tests.reproducible-builds.org/debian/history/python-distutils-extra.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-distutils-extra.html

...
==
FAIL: test_apport_hook (__main__.T)
Apport hooks
--
Traceback (most recent call last):
  File "test/auto.py", line 198, in test_apport_hook
self.assertEqual(len(f), 3, f) # 2 hook files plus .egg-info
AssertionError: 0 != 3 : []

--
Ran 26 tests in 17.308s

FAILED (failures=1)
make[1]: *** [debian/rules:9: override_dh_auto_test] Error 1
--- End Message ---
--- Begin Message ---
Hello Adrian,

Adrian Bunk [2018-03-09 23:38 +0200]:
> Some recent change in unstable makes python-distutils-extra FTBFS:
> 
> https://tests.reproducible-builds.org/debian/history/python-distutils-extra.html
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-distutils-extra.html
> 
> ...
> ==
> FAIL: test_apport_hook (__main__.T)
> Apport hooks
> --
> Traceback (most recent call last):
>   File "test/auto.py", line 198, in test_apport_hook
> self.assertEqual(len(f), 3, f) # 2 hook files plus .egg-info
> AssertionError: 0 != 3 : []

I can't reproduce this locally, and the build history in your links above
suggest that this just happened once and has worked again ever since. Maybe
some regression in a python 3 upload that was quickly fixed afterwards again?

I'm closing this now.

Thanks!

Martin--- End Message ---

Bug#891557: Pending fixes for bugs in the golang-github-jacobsa-crypto package

[pkg-go-maintainers]

tag 891557 + pending
thanks

Some bugs in the golang-github-jacobsa-crypto package are closed in
revision aa337dc5ef89ed6cbb6f5c7b3d8f2ac4c1dcd4e3 in branch 'debian'
by Felix Lechner

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-jacobsa-crypto.git/commit/?id=aa337dc

Commit message:

Added changelog entry for revision 2
Reverted to standard architecture tags (Closes: #891557)
Removed pointer size detection and passing in rules and tests
Removed build-essential from dependencies for tests
Deleted README.Debian, which documented this behavior
Marked changelog for release

Bug#873227: Please upgrade to 4.1: Java 9 support

[Markus Koschany]

Hi tony,

Am 25.03.2018 um 06:26 schrieb tony mancill:
[...]

> I'm going to upload to experimental momentarily and ask others on the
> Java Team if there any concern about uploading Gradle 3.4 to unstable.

Let's do it. I remember there were two failing packages with Gradle 3.4
but BND might be fixed already thanks to Kai-Chung Yan. I guess we will
solve the remaining issues as well eventually.

Cheers,

Markus



signature.asc
Description: OpenPGP digital signature

Bug#893988: wide-dhcpv6-client-udeb: not installable: depends on non-udeb libfl2

[Roger Shimizu]

Dear KiBi,

On Sun, Mar 25, 2018 at 5:19 PM, Cyril Brulebois  wrote:
> Control: tag -1 patch
>
> Hi Roger,
>
> Roger Shimizu  (2018-03-25):
>> Do you have any suggestion, except adding udeb support to package flex?
>
> It looks acceptable to me to use the static library in the udeb, so I've
> tried building it against libfl.a, and that seems to do the job since
> the libfl2 dependency goes away. I'm not sure it's reasonable to do that
> for both the deb and the udeb, though; so I've looked into making it
> conditional, and only building the udeb against the static library.

Thanks for your suggestion and patches!
I agree with you that static linking for udeb only.

> Unfortunately, it looks like the build system doesn't support out of
> tree builds, so I've had to copy all files under build-{deb,udeb},
> instead of just running ../configure, make, make install from there.
> I've picked rsync to do this, but feel free to use anything else.

Yes, the build system is quite old, it's a software wrote 10 years ago.
Really thanks for your patches that overcome the issue.

I just don't like the name "build-deb", which is too close to "build-udeb".
So I change it to "build", with some other cleanups.
My patch is enclosed, and it's based on yours.

> I've also chosen to clean things up using an override_dh_auto_clean
> target, so that most modifications are seen at once in debian/rules, but
> you may want to use debian/clean instead.

Just a nitpicking.
The build cannot be triggered again by "dpkg-buildpackage -uc -us"
after one build.
It was OK in previous version.

However, this is small issue, so I already uploaded.

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1
From 42d2b0dd8694a92e5176c993b56f8ec3c54376ed Mon Sep 17 00:00:00 2001
From: Roger Shimizu 
Date: Sun, 25 Mar 2018 22:40:50 +0900
Subject: [PATCH] d/rules: Cleanup

Now build two versions under the directories below:
 - build: nornal version. The same as previous one.
 - build-udeb: udeb version, which staticly linked with libfl2 (flex
   library)
---
 debian/changelog |  3 ++-
 debian/rules | 36 
 2 files changed, 18 insertions(+), 21 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index 200cc24..fb4b5ed 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -2,7 +2,8 @@ wide-dhcpv6 (20080615-21) UNRELEASED; urgency=medium
 
   * debian/rules:
 - Introduce separate deb/udeb builds, copying source files under
-  build-{deb,udeb} since support for out-of-tree build seems broken.
+  {build,build-udeb} since support for out-of-tree build seems
+  broken.
 - Don't try to build only the dhcp6c binary in the udeb tree, as the
   install target tries to install everything anyway.
 - Patch Makefile.in to build the dhcp6c binary against static flex
diff --git a/debian/rules b/debian/rules
index 1f021df..724bb1e 100755
--- a/debian/rules
+++ b/debian/rules
@@ -9,28 +9,26 @@ export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 %:
 	dh $@
 
-build-deb/.stamp:
-	rsync --exclude debian/ --exclude .pc/ -a * build-deb && touch $@
-
-build-udeb/.stamp:
-	rsync --exclude debian/ --exclude .pc/ -a * build-udeb && touch $@
-	# Build against the static flex library to avoid picking an extra dependency on libfl2 (#893988):
-	sed "s,^CLIENTLIBS=.*,CLIENTLIBS=$$(find /usr/lib/$$(dpkg-architecture -qDEB_BUILD_MULTIARCH) -name libfl.a)," -i build-udeb/Makefile.in
-
-override_dh_auto_configure: build-deb/.stamp build-udeb/.stamp
-	cd build-deb && \
-	./configure --prefix=/usr --mandir=\$${prefix}/share/man \
-		--with-localdbdir=/var/lib/dhcpv6 --sysconfdir=/etc/wide-dhcpv6
-	cd build-udeb && \
-	./configure --prefix=/usr --mandir=\$${prefix}/share/man \
-		--with-localdbdir=/var/lib/dhcpv6 --sysconfdir=/etc/wide-dhcpv6
+override_dh_auto_configure:
+	# sed command below is to build against the static flex library
+	# to avoid picking an extra dependency on libfl2 (#893988)
+	for dir in build build-udeb; do \
+		rsync -a --exclude debian/ --exclude .pc/ --exclude .git/ . $$dir; \
+		[ $$dir = "build-udeb" ] && \
+		sed "s,^CLIENTLIBS=.*,CLIENTLIBS=$$(find /usr/lib/$$(dpkg-architecture -qDEB_BUILD_MULTIARCH) -name libfl.a)," \
+			-i $$dir/Makefile.in; \
+		cd $$dir && \
+		./configure --prefix=/usr --mandir=\$${prefix}/share/man \
+			--with-localdbdir=/var/lib/dhcpv6 --sysconfdir=/etc/wide-dhcpv6 && \
+		cd -; \
+	done
 
 override_dh_auto_build:
-	$(MAKE) -C build-deb
+	$(MAKE) -C build
 	$(MAKE) -C build-udeb
 
 override_dh_auto_install:
-	$(MAKE) -C build-deb prefix=$(CURDIR)/debian/tmp/usr install
+	$(MAKE) -C build prefix=$(CURDIR)/debian/tmp/usr install
 	$(MAKE) -C build-udeb prefix=$(CURDIR)/debian/tmp-udeb/usr install
 
 override_dh_installinit:
@@ -42,6 +40,4 @@ override_dh_fixperms:
 
 override_dh_auto_clean:
 	dh_auto_clean
-	rm -rf build-deb
-	rm -rf build-udeb
-	rm -rf debian/tmp-udeb
+	rm -rf build 

Bug#893988: wide-dhcpv6-client-udeb: not installable: depends on non-udeb libfl2

[Roger Shimizu]

On Sun, Mar 25, 2018 at 11:15 PM, Roger Shimizu  wrote:
>
> Just a nitpicking.
> The build cannot be triggered again by "dpkg-buildpackage -uc -us"
> after one build.
> It was OK in previous version.

I tested it again, and the problem is gone now.
Sorry for the false positive info. Bow!

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1

Bug#893988: wide-dhcpv6-client-udeb: not installable: depends on non-udeb libfl2

[Roger Shimizu]

On Sun, Mar 25, 2018 at 11:27 PM, Cyril Brulebois  wrote:
> Hey,
>
> Roger Shimizu  (2018-03-25):
>> On Sun, Mar 25, 2018 at 11:15 PM, Roger Shimizu  
>> wrote:
>> > Just a nitpicking.
>> > The build cannot be triggered again by "dpkg-buildpackage -uc -us"
>> > after one build.
>> > It was OK in previous version.
>>
>> I tested it again, and the problem is gone now.
>> Sorry for the false positive info. Bow!
>
> I had tested that and I wasn't able to reproduce this. Maybe what
> happened is you had a build with the build-deb directory, you renamed
> it build, and there were stray files from the previous build?

Maybe.

> You may want to push your tree to git too (I tried git fetch but found
> no new commits there). ;)

I already pushed the tag.
But still waiting the ftp-master to accept my upload, after that I can
safely push to master branch.

> Thanks for your swift actions, much appreciated!

No problem.
And I just don't want to break d-i.
(although I still need to fix armel later)

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1

Processed: Pending fixes for bugs in the httpunit package

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tag 893158 + pending
Bug #893158 [src:httpunit] httpunit FTBFS with openjdk-9
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
893158: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893158
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#893158: Pending fixes for bugs in the httpunit package

[pkg-java-maintainers]

tag 893158 + pending
thanks

Some bugs in the httpunit package are closed in revision
9639ef643c820283d32ffdf7d9fec91ab536acdc in branch 'master' by
Emmanuel Bourg

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/httpunit.git/commit/?id=9639ef6

Commit message:

Fixed the build failure with Java 9 (Closes: #893158)

Bug#893158: marked as done (httpunit FTBFS with openjdk-9)

[Debian Bug Tracking System]

Your message dated Sun, 25 Mar 2018 23:19:19 +
with message-id 
and subject line Bug#893158: fixed in httpunit 1.7+dfsg-13
has caused the Debian Bug report #893158,
regarding httpunit FTBFS with openjdk-9
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
893158: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893158
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: httpunit
Version: 1.7+dfsg-12
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/httpunit.html

...
compile:
[mkdir] Created dir: /build/1st/httpunit-1.7+dfsg/build/classes
[javac] /build/1st/httpunit-1.7+dfsg/build.xml:136: warning: 
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to 
false for repeatable builds
[javac] Compiling 195 source files to 
/build/1st/httpunit-1.7+dfsg/build/classes
[javac] Using ant.build.javac.target 1.5 is no longer supported, switching 
to 1.6
[javac] Using ant.build.javac.target 1.5 is no longer supported, switching 
to 1.6
[javac] Using ant.build.javac.source 1.5 is no longer supported, switching 
to 1.6
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 1.6
[javac] warning: [options] source value 1.6 is obsolete and will be removed 
in a future release
[javac] warning: [options] target value 1.6 is obsolete and will be removed 
in a future release
[javac] warning: [options] To suppress warnings about obsolete options, use 
-Xlint:-options.
[javac] 
/build/1st/httpunit-1.7+dfsg/src/com/meterware/httpunit/HttpWebResponse.java:92:
 error: unmappable character (0xF6) for encoding US-ASCII
[javac] // by Roger Lindsj?
[javac]   ^
[javac] 
/build/1st/httpunit-1.7+dfsg/src/com/meterware/servletunit/ServletUnitServletContext.java:127:
 error: unmappable character (0xE4) for encoding US-ASCII
[javac] // by Timo Westk?mper
[javac] ^
[javac] 2 errors
[javac] 4 warnings

BUILD FAILED
/build/1st/httpunit-1.7+dfsg/build.xml:136: Compile failed; see the compiler 
error output for details.

Total time: 2 seconds
make[1]: *** [debian/rules:14: override_dh_auto_build] Error 1
--- End Message ---
--- Begin Message ---
Source: httpunit
Source-Version: 1.7+dfsg-13

We believe that the bug you reported is fixed in the latest version of
httpunit, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 893...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated httpunit package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 26 Mar 2018 00:57:32 +0200
Source: httpunit
Binary: libhttpunit-java libhttpunit-java-doc
Architecture: source
Version: 1.7+dfsg-13
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 libhttpunit-java - automated web site testing toolkit
 libhttpunit-java-doc - documentation for libhttpunit-java
Closes: 871863 893158
Changes:
 httpunit (1.7+dfsg-13) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Miguel Landaeta ]
   * Team upload.
   * Remove myself from uploaders list. (Closes: #871863)
   * Wrap and sort dependencies list.
   * Update copyright info.
 .
   [ Emmanuel Bourg ]
   * Fixed the build failure with Java 9 (Closes: #893158)
   * Standards-Version updated to 4.1.3
   * Switch to debhelper level 11
Checksums-Sha1:
 62f459880e7b91ddedeac3fea29e7ac647cd3590 2196 httpunit_1.7+dfsg-13.dsc
 98cea9238c17e17a85287c527b1e721e08250d0d 9976 
httpunit_1.7+dfsg-13.debian.tar.xz
 84f75ee31b14e10296d82b042b8f5ce3bf52243b 11776 
httpunit_1.7+dfsg-13_source.buildinfo
Checksums-Sha256:
 033b87706b0265a443fdd0ae40e9a228b45689603d3cb29d240b109c33260d9c 2196 
httpunit_1.7+dfsg-13.dsc
 1eb16375dbfed8f5c5d0bd36f290cd1ce84fa0cd7266088688588df71572aa5e 9976 
httpunit_1.7+dfsg-13.debian.tar.xz
 

Bug#859545: marked as done (opensmtpd-extras: Please migrate to openssl1.1 in buster)

[Debian Bug Tracking System]

Your message dated Sun, 25 Mar 2018 23:19:39 +
with message-id 
and subject line Bug#859545: fixed in opensmtpd-extras 5.7.1-4
has caused the Debian Bug report #859545,
regarding opensmtpd-extras: Please migrate to openssl1.1 in buster
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
859545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859545
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: opensmtpd-extras
Version: 5.7.1-2
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/opensmtpd-extras_5.7.1-2_amd64-20160530-2113

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt
--- End Message ---
--- Begin Message ---
Source: opensmtpd-extras
Source-Version: 5.7.1-4

We believe that the bug you reported is fixed in the latest version of
opensmtpd-extras, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 859...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ryan Kavanagh  (supplier of updated opensmtpd-extras package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 25 Mar 2018 18:39:37 -0400
Source: opensmtpd-extras
Binary: opensmtpd-extras
Architecture: source amd64
Version: 5.7.1-4
Distribution: unstable
Urgency: medium
Maintainer: Ryan Kavanagh 
Changed-By: Ryan Kavanagh 
Description:
 opensmtpd-extras - addons for the OpenSMTPD SMTP server
Closes: 859545 873731
Changes:
 opensmtpd-extras (5.7.1-4) unstable; urgency=medium
 .
   * Don't include leading slash in install files
   * Set branch to debian/sid in Vcs-Git
   * Bump standards version to 4.1.3
   * Update Vcs-* to point to salsa
   * Drop opensmtpd-extras-experimental: filters are currently broken due to an
 API mismatch with the current version of opensmtpd (Closes: #873731)
   * Dropping filters also means we don't need libssl1.0-dev (Closes: #859545)
   * Change priority from extra to optional
   * Update watch file to connect over https
   * Override depends-on-mail-transport-agent-without-alternatives: we
 legitimately need opensmtpd
   * Turn on hardening
Checksums-Sha1:
 16f7dcfdad43a306801afa2ed74334600ab28e45 3101 opensmtpd-extras_5.7.1-4.dsc
 c9441e61c3ec58db14df806aa868b78a5e2ec9ca 7492 
opensmtpd-extras_5.7.1-4.debian.tar.xz
 39e24a2ee76bf5875e6e1fb4df4fe31bdbe2ec59 322776 
opensmtpd-extras-dbgsym_5.7.1-4_amd64.deb
 d492f656730bbdd60f1dcf8588f5594d8d7b53ba 8148 
opensmtpd-extras_5.7.1-4_amd64.buildinfo
 34e5d389635671d7679208f4ce9b2b726d520aa0 59948 
opensmtpd-extras_5.7.1-4_amd64.deb
Checksums-Sha256:
 8e4740ee6977380c4e2a20d91d2fb72c550d7459570c16c4e658dabad9096a3d 3101 
opensmtpd-extras_5.7.1-4.dsc
 7e8fc9def2cd3841db7cc11cdcbabe2e9dbe54271f59e398a59125fe067e30ad 7492 
opensmtpd-extras_5.7.1-4.debian.tar.xz
 f3b0717ce1ec2522f98ce256a69b94f65fb08edb9dfd7573f6cdaf1f5439e162 322776 
opensmtpd-extras-dbgsym_5.7.1-4_amd64.deb
 849aa862fe9cc796fc5ce389ab6b5f99b15b08ef5e5fccaa1db747de1d333619 8148 
opensmtpd-extras_5.7.1-4_amd64.buildinfo
 4639bf0679eeb6020c467cea083957068d76d29cb57667894e51741340505595 59948 
opensmtpd-extras_5.7.1-4_amd64.deb
Files:
 2c975be0944cda02f74b42faf1924051 3101 mail optional 
opensmtpd-extras_5.7.1-4.dsc
 1d236bdd1bbbac636ff92e6269be58e8 7492 mail optional 
opensmtpd-extras_5.7.1-4.debian.tar.xz
 9eda32713307328fe88c7e6fca2e7d64 322776 debug optional 
opensmtpd-extras-dbgsym_5.7.1-4_amd64.deb
 da360d7f597a4996d8edfef7babdd46c 8148 mail optional 
opensmtpd-extras_5.7.1-4_amd64.buildinfo
 

Bug#845954: marked as done (pyrenamer: depends on python-gnome2 which deprecated)

[Debian Bug Tracking System]

Your message dated Mon, 26 Mar 2018 00:12:34 +
with message-id 
and subject line Bug#893938: Removed package(s) from unstable
has caused the Debian Bug report #845954,
regarding pyrenamer: depends on python-gnome2 which deprecated
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
845954: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845954
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyrenamer
Version: 0.6.0-1.2
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs python-gnome2 gnome-python

Hi,

pyrenamer depends on python-gnome2 or python-gconf, or has a
build-dependency on one those packages. Those are built from
gnome-python which is long deprecated and going to be removed from
the archive. pyrenamer should be ported away from it.

The way forward is to port your app to use GObject Introspection
bindings.

For more information on GObject Introspection see [1] and [2].

Please try to do this before the Stretch release as we're going to
try to remove gnome-python this cycle.

If you have any question don't hesitate to ask.

[1] https://wiki.gnome.org/action/show/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/action/show/Projects/PyGObject 
--- End Message ---
--- Begin Message ---
Version: 0.6.0-1.2+rm

Dear submitter,

as the package pyrenamer has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/893938

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmas...@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Chris Lamb (the ftpmaster behind the curtain)--- End Message ---

Bug#893049: marked as done (libfiu FTBFS: recipe for target 'run-test-basic_ctrl.py' failed)

[Debian Bug Tracking System]

Your message dated Mon, 26 Mar 2018 00:49:33 +
with message-id 
and subject line Bug#893049: fixed in libfiu 0.96-1
has caused the Debian Bug report #893049,
regarding libfiu FTBFS: recipe for target 'run-test-basic_ctrl.py' failed
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
893049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893049
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libfiu
Version: 0.95-5
Severity: serious

https://buildd.debian.org/status/package.php?p=libfiu=sid

...
./generate-test -c tests/malloc.conf -o tests/malloc.c
make[4]: Leaving directory '/<>/tests/generated'
make[4]: Entering directory '/<>/tests/utils'
LD_LIBRARY_PATH=../../libfiu/ ./test-basic_ctrl.py > 
output-test-basic_ctrl.py.txt 2>&1
Makefile:38: recipe for target 'run-test-basic_ctrl.py' failed
make[4]: *** [run-test-basic_ctrl.py] Error 1
--- End Message ---
--- Begin Message ---
Source: libfiu
Source-Version: 0.96-1

We believe that the bug you reported is fixed in the latest version of
libfiu, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 893...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated libfiu package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 25 Mar 2018 20:32:20 -0400
Source: libfiu
Binary: libfiu0 fiu-utils libfiu-dev python-fiu python3-fiu
Architecture: source amd64
Version: 0.96-1
Distribution: unstable
Urgency: medium
Maintainer: Chris Lamb 
Changed-By: Chris Lamb 
Description:
 fiu-utils  - userspace fault injection framework (utilities)
 libfiu-dev - userspace fault injection framework (development libraries)
 libfiu0- userspace fault injection framework
 python-fiu - userspace fault injection framework (Python bindings)
 python3-fiu - userspace fault injection framework (Python 3 bindings)
Closes: 893049
Changes:
 libfiu (0.96-1) unstable; urgency=medium
 .
   * New upstream release. (Closes: #893049)
 - Fix FTBFS due to build/test parellelism. (Closes: #893049)
   * Add explicit python3-distutils Build-Dependency.
Checksums-Sha1:
 a638353bfc540b863fb26413e98f3a23bf347ab2 2133 libfiu_0.96-1.dsc
 8ae728565c05a88f42b0e69516ac84d6e5152bc7 61039 libfiu_0.96.orig.tar.gz
 a0fa3a4c8cd747dee15fd2cbeeadfd2a21e63fc7 5716 libfiu_0.96-1.debian.tar.xz
 112e9a8b1db176fb7facaa90c8944c4ceef2a88e 11856 fiu-utils_0.96-1_amd64.deb
 58b9245470412a294ecb4137f0cc00d54221b59f 28208 libfiu-dev_0.96-1_amd64.deb
 dc1251fc66af1a740435b92c63b2bc26db7a7ee9 66108 libfiu0-dbgsym_0.96-1_amd64.deb
 995af51154627472d201d75eaac0129bd18e758d 26032 libfiu0_0.96-1_amd64.deb
 c0263f7637891c3646ddd3d0a625f86a321ee6b6 8425 libfiu_0.96-1_amd64.buildinfo
 bdcc479a168fb24749f7336e5399259c194de625 12412 
python-fiu-dbgsym_0.96-1_amd64.deb
 ba7fb268702c9fea75ed91152ce042ae656bf53c 11400 python-fiu_0.96-1_amd64.deb
 5156774f5e37a2cdcca44843bc71e7c0d20da90b 13788 
python3-fiu-dbgsym_0.96-1_amd64.deb
 743bae5fae86391a80b923b9d538252beb4f4e1e 11512 python3-fiu_0.96-1_amd64.deb
Checksums-Sha256:
 739da80c7dfd565505d021841efd51faa39710a6dc16ca4bf1917f5de8729605 2133 
libfiu_0.96-1.dsc
 899716d27ab70ebeff46a8b3c012e52b5a5c2bc422b51f7b55d46b52cf0a75b4 61039 
libfiu_0.96.orig.tar.gz
 1dbc5d7a0b33eaf09099c2637cb1599b5e9772545de9c79b0f523b880c4993bb 5716 
libfiu_0.96-1.debian.tar.xz
 51ad569b4e84c523dc2024b2d6958e21b3302573fb92d5d1793ce8ea1c8174f7 11856 
fiu-utils_0.96-1_amd64.deb
 c2f6a0b1d5b7f785c0e6ebd974ec81aeb841109acdf7d8632593b700eee23b71 28208 
libfiu-dev_0.96-1_amd64.deb
 916992568313c6ae30c30e8793128ff5600dc553cd86835778707aecb391cab0 66108 
libfiu0-dbgsym_0.96-1_amd64.deb
 dbc759b5c649f517fa6535e97300b0f4ed5418da5cf7720a453efb1a5d21b083 26032 
libfiu0_0.96-1_amd64.deb
 396340a446442beed87ee1fd04d666e28363fb7dd8ef2997584a31a0bc9a41c5 8425 
libfiu_0.96-1_amd64.buildinfo
 c30e23c04208ff36eb6f8cfcc9dd0bdbad4c4624f3568e14a02643da9760d885 12412 
python-fiu-dbgsym_0.96-1_amd64.deb
 7779de7ebfe4b3add27aadc8e5653a8b087f3b616487e6dbb1875e1cf86541e2 11400 
python-fiu_0.96-1_amd64.deb
 

Processed: Pending fixes for bugs in the jboss-xnio package

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 893359 -pending
Bug #893359 [src:jboss-xnio] jboss-xnio FTBFS with openjdk-9
Removed tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
893359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893359
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#893247: Intend to take over libjbzip2-java and libnanoxml2-java into Debian Med team

[tony mancill]

On Sun, Mar 25, 2018 at 06:37:05PM +0200, Emmanuel Bourg wrote:
> Hi Andreas,
> 
> These are quite generic non-med related libraries, I'd prefer keeping them 
> under the Java Team umbrella.
> 
> Emmanuel Bourg

Hi,

Multiple teams wanting to maintain a library is a good problem to have.
I propose we consider:

(a) pulling these libraries into the "Debian" project on Salsa, which
replaces collab-maint and grants commit permissions to all DDs and any
designated guest account

OR

(b) relaxing the default pkg-java permissions to be like those of the
Debian Perl Team and allow all DDs by default

OR

(c) configuring any other mechanism that would allow the union of these
two teams (and others!) to contribute to the packaging.

As for which team is listed in the Maintainer field, I don't think it
matters much as long as we have a suitable set of interested Uploaders.

Cheers,
tony


signature.asc
Description: PGP signature

Bug#893359: Pending fixes for bugs in the jboss-xnio package

[pkg-java-maintainers]

tag 893359 + pending
thanks

Some bugs in the jboss-xnio package are closed in revision
6322f4b9f51fdd6cb42124b5aa39dfe211c7fe4f in branch 'master' by Markus
Koschany

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/jboss-xnio.git/commit/?id=6322f4b

Commit message:

Add java9.patch and fix FTBFS with Java 9.

Closes: #893359

Processed: Pending fixes for bugs in the jboss-xnio package

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tag 893359 + pending
Bug #893359 [src:jboss-xnio] jboss-xnio FTBFS with openjdk-9
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
893359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893359
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#893359: jboss-xnio FTBFS with openjdk-9

[Markus Koschany]

I could solve one part of the build issues with Java 9 but I am stuck with

"/build/jboss-xnio-3.6.2/api/src/main/java/java/nio/channels/FileChannel.java:[19,1]
package exists in another module: java.base
"

I have read about the new --patch-modules option but I am not sure if
this is the right way. Renaming the package is probably the way forward.
However upstream is still working on Java 9 support and I don't want to
act prematurely. Let's see with what they will come up with. Hopefully
it happens before Buster freezes.



signature.asc
Description: OpenPGP digital signature

Bug#894032: postr: Intent to remove from Debian

[Jeremy Bicha]

Source: postr
Version: 0.13.1-1
Severity: serious
Tags: buster sid

postr's last upstream release and last Debian upload was in 2014.

postr was removed from Debian Testing in December because it depends
on gnome-python which will be removed from Debian soon.

postr was converted to gtk3 in 2012 in git but no release was made for
it. (That would fix the gnome-python dependency bug).

Unless someone uploads postr (with those patches or as a git snapshot)
to Debian soon, I intend to file a bug to remove postr from Debian.

Thanks,
Jeremy Bicha

Bug#894033: jupyter-notebook: jupyter notebook: IOLoop has no attribute initialized

[r.ductor]

Package: jupyter-notebook
Version: 5.4.0-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

jupyter notebook crashes on start:

$ jupyter notebook
Traceback (most recent call last):
  File "/usr/bin/jupyter-notebook", line 11, in 
load_entry_point('notebook==5.4.0', 'console_scripts', 'jupyter-notebook')()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 587, in 
load_entry_point
return get_distribution(dist).load_entry_point(group, name)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2800, 
in load_entry_point
return ep.load()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2431, 
in load
return self.resolve()   
   
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2437, 
in resolve   
module = __import__(self.module_name, fromlist=['__name__'], level=0)   
   
  File "/usr/lib/python3/dist-packages/notebook/notebookapp.py", line 45, in 
  
ioloop.install()
   
  File "/usr/lib/python3/dist-packages/zmq/eventloop/ioloop.py", line 210, in 
install  
assert (not ioloop.IOLoop.initialized()) or \   
   
AttributeError: type object 'IOLoop' has no attribute 'initialized'


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (900, 'testing')
Architecture: amd64 (x86_64)

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

Versions of packages jupyter-notebook depends on:
ii  jupyter-core  4.4.0-2
ii  python3   3.6.4-1
ii  python3-notebook  5.4.0-1

jupyter-notebook recommends no packages.

jupyter-notebook suggests no packages.

-- no debconf information

Bug#893525: CVE-2018-1000097

[Salvatore Bonaccorso]

Hi Santiago, hi Moritz,

On Mon, Mar 19, 2018 at 06:20:44PM +0100, Santiago Vila wrote:
> On Mon, Mar 19, 2018 at 05:58:04PM +0100, Moritz Muehlenhoff wrote:
> > Source: sharutils
> > Severity: grave
> > Tags: security
> > 
> > This has been assigned CVE-2018-197:
> > http://lists.gnu.org/archive/html/bug-gnu-utils/2018-02/msg4.html
> > 
> > Proposed patch at:
> > http://lists.gnu.org/archive/html/bug-gnu-utils/2018-02/msg5.html
> 
> Thanks for the report. Simple question: Is this the same problem as this one?
> 
> http://lists.gnu.org/archive/html/bug-gnu-utils/2018-02/msg3.html
> 
> or there will be another different CVE for that?

That's an issue on it's own, but I do not think it has a CVE assigned
yet. The most recent assigned CVE is for the msg4.html message,
which was adressed with the proposed fix (and can be verified with the
reproducer which first needs to be extracted).

The issue from the msg3.html is in src/unshar.c

391   for (;;)
392 {
393   size_t len = fread (rw_buffer, 1, rw_base_size, file);
394   if (len == 0)
395 break;
396   fwrite (rw_buffer, 1, len, shell_fp);
397 }

specifically at the write in line 396. 

There is no reply on
https://lists.gnu.org/archive/html/bug-gnu-utils/2018-02/msg3.html
so either it has been lost or ignored, might be worth reping the mail.

Regards,
Salvatore

Bug#893442: marked as done (lynkeos.app: FTBFS on ppc64el: AltiVec argument passed to unprototyped function)

[Debian Bug Tracking System]

Your message dated Sun, 25 Mar 2018 18:52:04 +
with message-id 
and subject line Bug#893442: fixed in lynkeos.app 2.10+dfsg1-3
has caused the Debian Bug report #893442,
regarding lynkeos.app: FTBFS on ppc64el: AltiVec argument passed to 
unprototyped function
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
893442: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893442
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lynkeos.app
Version: 2.10+dfsg1-2
Severity: serious
Tags: patch
User: debian-powe...@lists.debian.org
Usertags: ppc64el

I would appreciate if someone knowledgeable from -powerpc confirms
that the attached patch is correct.  The build failure is:

gcc /<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m 
-c \
  -MMD -MP -Wdate-time -D_FORTIFY_SOURCE=2 -I. -I.. 
-I/<>/lynkeos.app-2.10+dfsg1/GNUstep.. 
-I/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources 
-I/<>/lynkeos.app-2.10+dfsg1/GNUstep/../ThreadConnectionSources 
-I/<>/lynkeos.app-2.10+dfsg1/GNUstep/../ThirdPartySources/SMDoubleSlider
 -DNO_FRAMEWORK_CHECK=1 -DGNUSTEP -DGNUSTEP_BASE_LIBRARY=1 -DGNU_GUI_LIBRARY=1 
-DGNU_RUNTIME=1 -DGNUSTEP_BASE_LIBRARY=1 -fno-strict-aliasing -fexceptions 
-fobjc-exceptions -D_NATIVE_OBJC_EXCEPTIONS -pthread -fPIC -Wall -DGSWARN 
-DGSDIAGNOSE -Wno-import -g -O2 -g -O2 
-fdebug-prefix-map=/<>/lynkeos.app-2.10+dfsg1=. 
-fstack-protector-strong -Wformat -Werror=format-security -fgnu-runtime 
-Wno-unknown-pragmas -Wno-cpp -fconstant-string-class=NSConstantString -I. 
-I/usr/local/include/GNUstep -I/usr/include/GNUstep \
   -o obj/Lynkeos.obj/MyDeconvolution.m.o
/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m: In 
function 'vector_Process_One_line':
/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:72:44:
 warning: excess elements in vector initializer
0x04050607, 0x04050607 };
^~
/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:72:44:
 note: (near initialization for 'Vperma')
/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:72:56:
 warning: excess elements in vector initializer
0x04050607, 0x04050607 };
^~
/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:72:56:
 note: (near initialization for 'Vperma')
/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:74:44:
 warning: excess elements in vector initializer
0x0C0D0E0F, 0x0C0D0E0F };
^~
/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:74:44:
 note: (near initialization for 'Vpermb')
/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:74:56:
 warning: excess elements in vector initializer
0x0C0D0E0F, 0x0C0D0E0F };
^~
/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:74:56:
 note: (near initialization for 'Vpermb')
/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:88:13:
 warning: implicit declaration of function 'vec_madd' 
[-Wimplicit-function-declaration]
   Vdx = vec_madd( vec_ld(0,expXptr), Vdy, Vzero );
 ^~~~
/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:88:23:
 warning: implicit declaration of function 'vec_ld'; did you mean 'vector'? 
[-Wimplicit-function-declaration]
   Vdx = vec_madd( vec_ld(0,expXptr), Vdy, Vzero );
   ^~
   vector
/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:88:7: 
error: AltiVec argument passed to unprototyped function
   Vdx = vec_madd( vec_ld(0,expXptr), Vdy, Vzero );
   ^~~
/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:89:41:
 warning: implicit declaration of function 'vec_cmplt' 
[-Wimplicit-function-declaration]
   const __vector __bool int Vmask = vec_cmplt(Vdx,Vthr);
 ^
/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:89:7: 
error: AltiVec argument passed to unprototyped function
   const __vector __bool int Vmask = vec_cmplt(Vdx,Vthr);
   ^
/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:90:27:
 warning: implicit declaration of function 'vec_and'; did you mean 'vscanf'? 

Bug#890400: Any news about a new upstream version with new SONAME?

[Julien Yann Dutheil]

Dear Andreas,

I moved forward with libbpp-seq, but after pushing I got the following
message:

remote: Resolving deltas: 100% (172/172), completed with 152 local objects.
remote:
remote: To create a merge request for pristine-tar, visit:
remote:
https://salsa.debian.org/med-team/libbpp-seq/merge_requests/new?merge_request%5Bsource_branch%5D=pristine-tar
remote:
remote: To create a merge request for upstream, visit:
remote:
https://salsa.debian.org/med-team/libbpp-seq/merge_requests/new?merge_request%5Bsource_branch%5D=upstream
remote:

Clicking on the suggested links leads to a 404 error (I do not have
permission to access this page).

Is everything ok or did I somehow do sthg wrong?

Best,

Julien.

On Thu, Mar 22, 2018 at 11:17 AM, Julien Yann Dutheil <
julien.duth...@univ-montp2.fr> wrote:

> Hi Andreas,
>
> On Thu, Mar 22, 2018 at 10:17 AM, Andreas Tille  wrote:
>
>> Hi Julien,
>>
>> On Wed, Mar 21, 2018 at 09:26:01PM +0100, Julien Yann Dutheil wrote:
>> > I could somehow udate the symbols list, but still get a lintian warning
>> > [1].
>>
>> That was just a typo (see commit 06beb6872bb0c773aff727c25dfe07
>> 77a7c401ca).
>>
>> Ok, thanks.
>
>
>> > I have pushed my commits, would you mind giving them a look? Will
>> > proceed with other libs once I have confirmation that everything is ok.
>>
>> I've just uploaded.  I think the following lintian *infos* (lintian -I)
>> will be interesting for you:
>>
>> I: libbpp-core source: testsuite-autopkgtest-missing
>> N:
>> N:This package does not declare a test suite. Having a test suite
>> helps
>> N:with automated QA in response to changes in the archive. For
>> example, if
>> N:your package has a test suite, it is possible to re-execute that
>> test
>> N:suite when any of the package dependencies has a new version and
>> check
>> N:whether that update caused problems for your package.
>> N:
>> N:To declare a test suite, please add a debian/tests/control file to
>> your
>> N:package.
>> N:
>> N:For more information on how to add functional tests to your package,
>> N:browse to https://ci.debian.net/doc/.
>> N:
>> N:Severity: wishlist, Certainty: certain
>> N:
>> N:Check: testsuite, Type: source
>>
>> May be you see a chance to tweak the build time test into an autopkgtest.
>>
>> Humm... not sure how that integrates with our existing series of unit
> tests at build time?
>
> I: libbpp-core4: spelling-error-in-binary 
> usr/lib/x86_64-linux-gnu/libbpp-core.so.4.0.0
>> colums columns
>> I: libbpp-core4: spelling-error-in-binary 
>> usr/lib/x86_64-linux-gnu/libbpp-core.so.4.0.0
>> controled controlled
>> I: libbpp-core4: spelling-error-in-binary 
>> usr/lib/x86_64-linux-gnu/libbpp-core.so.4.0.0
>> wih with
>>
>> Please verify your code and simply fix with next upstream release if
>> these are no false positives.
>>
>> Wow, impressive! Fixed upstream. fortunately, no interface break :)
>
>>
>> Kind regards and thanks for your cooperation
>>
>> Thanks a lot for your patience and advice!
>
> Julien.
>
>>Andreas.
>>
>> --
>> http://fam-tille.de
>>
>>
>
>
> --
> Julien Y. Dutheil, Ph-D
> 0 (+49) 6421 178 986 <+49%206421%20178986>
>
> § Max Planck Institute for Evolutionary Biology
> Molecular Systems Evolution
> Department of Evolutionary Genetics
> Plön -- GERMANY
>
> § Institute of Evolutionary Sciences - Montpellier
> University of Montpellier 2 -- FRANCE
>



-- 
Julien Y. Dutheil, Ph-D
0 (+49) 4522 763 298

§ Max Planck Institute for Evolutionary Biology
Molecular Systems Evolution
Department of Evolutionary Genetics
Plön -- GERMANY

§ Institute of Evolutionary Sciences - Montpellier
University of Montpellier 2 -- FRANCE

Bug#893532: marked as done (undertow FTBFS with openjdk-9)

[Debian Bug Tracking System]

Your message dated Sun, 25 Mar 2018 15:53:10 +
with message-id 
and subject line Bug#893532: fixed in undertow 1.4.23-2
has caused the Debian Bug report #893532,
regarding undertow FTBFS with openjdk-9
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
893532: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893532
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: undertow
Version: 1.4.23-1
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/undertow.html

...
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar (default-cli) on 
project undertow-core: MavenReportException: Error while generating Javadoc: 
[ERROR] Exit code: 1 - 
/build/1st/undertow-1.4.23/core/target/generated-sources/annotations/io/undertow/websockets/core/WebSocketMessages_$bundle.java:6:
 error: package javax.annotation is not visible
[ERROR] import javax.annotation.Generated;
[ERROR] ^
[ERROR]   (package javax.annotation is declared in module 
java.xml.ws.annotation, which is not in the module graph)
[ERROR] 
/build/1st/undertow-1.4.23/core/target/generated-sources/annotations/io/undertow/websockets/core/WebSocketLogger_$logger.java:5:
 error: package javax.annotation is not visible
[ERROR] import javax.annotation.Generated;
[ERROR] ^
[ERROR]   (package javax.annotation is declared in module 
java.xml.ws.annotation, which is not in the module graph)
[ERROR] 
/build/1st/undertow-1.4.23/core/target/generated-sources/annotations/io/undertow/client/UndertowClientMessages_$bundle.java:6:
 error: package javax.annotation is not visible
[ERROR] import javax.annotation.Generated;
[ERROR] ^
[ERROR]   (package javax.annotation is declared in module 
java.xml.ws.annotation, which is not in the module graph)
[ERROR] 
/build/1st/undertow-1.4.23/core/target/generated-sources/annotations/io/undertow/UndertowMessages_$bundle.java:7:
 error: package javax.annotation is not visible
[ERROR] import javax.annotation.Generated;
[ERROR] ^
[ERROR]   (package javax.annotation is declared in module 
java.xml.ws.annotation, which is not in the module graph)
[ERROR] 
/build/1st/undertow-1.4.23/core/target/generated-sources/annotations/io/undertow/UndertowLogger_$logger.java:21:
 error: package javax.annotation is not visible
[ERROR] import javax.annotation.Generated;
[ERROR] ^
[ERROR]   (package javax.annotation is declared in module 
java.xml.ws.annotation, which is not in the module graph)
[ERROR] 
[ERROR] Command line was: /usr/lib/jvm/java-9-openjdk-amd64/bin/javadoc 
@options @packages
[ERROR] 
[ERROR] Refer to the generated Javadoc files in 
'/build/1st/undertow-1.4.23/core/target/apidocs' dir.
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :undertow-core
dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/build/1st/undertow-1.4.23 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/build/1st/undertow-1.4.23/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/build/1st/undertow-1.4.23/debian 
-Dmaven.repo.local=/build/1st/undertow-1.4.23/debian/maven-repo --batch-mode 
package javadoc:jar javadoc:aggregate -DskipTests -Dnotimestamp=true 
-Dlocale=en_US returned exit code 1
make: *** [debian/rules:4: build] Error 1
--- End Message ---
--- Begin Message ---
Source: undertow
Source-Version: 1.4.23-2

We believe that the bug you reported is fixed in the latest version of
undertow, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 893...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of 

Bug#893247: Intend to take over libjbzip2-java and libnanoxml2-java into Debian Med team

[Emmanuel Bourg]

Hi Andreas,

These are quite generic non-med related libraries, I'd prefer keeping them 
under the Java Team umbrella.

Emmanuel Bourg

Bug#893241: marked as done (libitext-java FTBFS with openjdk-9)

[Debian Bug Tracking System]

Your message dated Sun, 25 Mar 2018 17:05:13 +
with message-id 
and subject line Bug#893241: fixed in libitext-java 2.1.7-12
has caused the Debian Bug report #893241,
regarding libitext-java FTBFS with openjdk-9
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
893241: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893241
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libitext-java
Version: 2.1.7-11
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libitext-java.html

...
compile.rtf:
[mkdir] Created dir: /build/1st/build/bin.rtf
[javac] /build/1st/libitext-java-2.1.7/ant/compile.xml:56: warning: 
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to 
false for repeatable builds
[javac] Using javac -source 1.5 is no longer supported, switching to 1.6
[javac] Using javac -target 1.5 is no longer supported, switching to 1.6
[javac] Compiling 88 source files to /build/1st/build/bin.rtf
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 1.6
[javac] warning: [options] source value 1.6 is obsolete and will be removed 
in a future release
[javac] warning: [options] target value 1.6 is obsolete and will be removed 
in a future release
[javac] warning: [options] To suppress warnings about obsolete options, use 
-Xlint:-options.
[javac] 
/build/1st/libitext-java-2.1.7/rtf/com/lowagie/text/rtf/parser/destinations/RtfDestinationStylesheetTable.java:94:
 error: unmappable character (0xEF) for encoding US-ASCII
[javac]  * Percentage of line occupied by Kashida justification (0 ??? 
low, 10 ??? medium, 20 ??? high).
[javac]^
[javac] 
/build/1st/libitext-java-2.1.7/rtf/com/lowagie/text/rtf/parser/destinations/RtfDestinationStylesheetTable.java:94:
 error: unmappable character (0xBF) for encoding US-ASCII
[javac]  * Percentage of line occupied by Kashida justification (0 ??? 
low, 10 ??? medium, 20 ??? high).
[javac] ^
[javac] 
/build/1st/libitext-java-2.1.7/rtf/com/lowagie/text/rtf/parser/destinations/RtfDestinationStylesheetTable.java:94:
 error: unmappable character (0xBD) for encoding US-ASCII
[javac]  * Percentage of line occupied by Kashida justification (0 ??? 
low, 10 ??? medium, 20 ??? high).
[javac]  ^
[javac] 
/build/1st/libitext-java-2.1.7/rtf/com/lowagie/text/rtf/parser/destinations/RtfDestinationStylesheetTable.java:94:
 error: unmappable character (0xEF) for encoding US-ASCII
[javac]  * Percentage of line occupied by Kashida justification (0 ??? 
low, 10 ??? medium, 20 ??? high).
[javac] 
   ^
[javac] 
/build/1st/libitext-java-2.1.7/rtf/com/lowagie/text/rtf/parser/destinations/RtfDestinationStylesheetTable.java:94:
 error: unmappable character (0xBF) for encoding US-ASCII
[javac]  * Percentage of line occupied by Kashida justification (0 ??? 
low, 10 ??? medium, 20 ??? high).
[javac] 
^
[javac] 
/build/1st/libitext-java-2.1.7/rtf/com/lowagie/text/rtf/parser/destinations/RtfDestinationStylesheetTable.java:94:
 error: unmappable character (0xBD) for encoding US-ASCII
[javac]  * Percentage of line occupied by Kashida justification (0 ??? 
low, 10 ??? medium, 20 ??? high).
[javac] 
 ^
[javac] 
/build/1st/libitext-java-2.1.7/rtf/com/lowagie/text/rtf/parser/destinations/RtfDestinationStylesheetTable.java:94:
 error: unmappable character (0xEF) for encoding US-ASCII
[javac]  * Percentage of line occupied by Kashida justification (0 ??? 
low, 10 ??? medium, 20 ??? high).
[javac] 
  ^
[javac] 
/build/1st/libitext-java-2.1.7/rtf/com/lowagie/text/rtf/parser/destinations/RtfDestinationStylesheetTable.java:94:
 error: unmappable character (0xBF) for encoding US-ASCII
[javac]  * Percentage of line occupied by Kashida justification (0 ??? 
low, 10 ??? medium, 20 ??? high).
[javac] 
   ^
[javac] 

Bug#893525: CVE-2018-1000097

[Santiago Vila]

For completeness, I'm attaching here (so that it's also stored in our
BTS) the test file from the original report in decrypted and
uncompressed from. To reproduce:

unshar heap-buffer-overflow.bin

Thanks.

heap-buffer-overflow.bin
Description: Binary data

Bug#892981: marked as done (cenon.app: Incomplete debian/copyright?)

[Debian Bug Tracking System]

Your message dated Sun, 25 Mar 2018 18:49:56 +
with message-id 
and subject line Bug#892981: fixed in cenon.app 4.0.6+ds1-2
has caused the Debian Bug report #892981,
regarding cenon.app: Incomplete debian/copyright?
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
892981: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892981
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cenon.app
Version: 4.0.6+ds1-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Yavor Doganov 

Hi,

I just ACCEPTed cenon.app from NEW but noticed it was missing 
attribution in debian/copyright for at least Adobe Systems,
NeXT, vhf interservice GmbH, GraphiCode, etc.

(This is not exhaustive so please check over the entire package 
carefully and address these on your next upload.)


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: cenon.app
Source-Version: 4.0.6+ds1-2

We believe that the bug you reported is fixed in the latest version of
cenon.app, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 892...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Yavor Doganov  (supplier of updated cenon.app package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 25 Mar 2018 14:25:12 +0300
Source: cenon.app
Binary: cenon.app cenon.app-common
Architecture: source
Version: 4.0.6+ds1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNUstep maintainers 

Changed-By: Yavor Doganov 
Description:
 cenon.app  - Vector graphics tool for GNUstep
 cenon.app-common - Vector graphics tool for GNUstep (common files)
Closes: 892981
Changes:
 cenon.app (4.0.6+ds1-2) unstable; urgency=medium
 .
   * debian/copyright: Add missing copyright holders vhf interservice GmbH,
 vhf computer GmbH, NeXT Software, Inc., Adobe Systems Incorporated,
 GraphiCode Inc (Closes: #892981).
   * debian/control (cenon.app-common): Mark as M-A: foreign.
   * debian/Cenon.desktop: Change icon path to /usr/share.
Checksums-Sha1:
 82c40d75e204538c74146da44934ab2ee7aaf3b8 2119 cenon.app_4.0.6+ds1-2.dsc
 cdfed08ddd4de5bdc802fd98585921b622ec3149 10404 
cenon.app_4.0.6+ds1-2.debian.tar.xz
 d1a9a6b351b3d4f00e785b6e5b7c5c05affdf4ac 5503 
cenon.app_4.0.6+ds1-2_source.buildinfo
Checksums-Sha256:
 78ac8bec3ef9808b1d337aa00067ff8dc52eff20d6699d5e115ae22696cd95de 2119 
cenon.app_4.0.6+ds1-2.dsc
 f3379ba76c051448246b396799007405a50fe091e732d1a92df0fe4bb3a056e7 10404 
cenon.app_4.0.6+ds1-2.debian.tar.xz
 89b3f7708e629f976b8066ffa64715d36368730a4763cb17b1de87b467624de2 5503 
cenon.app_4.0.6+ds1-2_source.buildinfo
Files:
 c0c4bb712e074543eaac74540d6fc5b1 2119 gnustep optional 
cenon.app_4.0.6+ds1-2.dsc
 a06dd93f0dfd686e64c7b219300b1dd3 10404 gnustep optional 
cenon.app_4.0.6+ds1-2.debian.tar.xz
 56228fe20dc9a58e22a317ccab112884 5503 gnustep optional 
cenon.app_4.0.6+ds1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAlq36fMACgkQweDZLphv
fH454RAArYWhgs2DI0M4ph631Xfkc/G3RBBA2V8/PAJ+73/QvKofrzQhJSOaeFEl
7VBqVEWJ3jEBLg1K9GEjQ5KtJ4ELSh2MqoItXvl26v0yoUk4pYUKlwrN8RJg7Vvk
BhIquBx8nOYvh6d+wVQsh3qJQ0HZhUWDjugMn2VbMLu1/GjmLcFs/UsJ35C9kayb
Ara6YozG7FJUIpeaw0vkHV1mUa2ntyWwkFFJLmks7yG2mXQK6wHhgS2vigTZRq4L
UzEhvss0T/TuBWrWJhHnHvgatvyn1MIopr2SdFl0ldOxWDnYvGF7Cls4yxh+cUHq
oYbA578RcPgRJbYo1MpF6zKzVRNY4C+Y8Xb1xQH65FTlMeaEeDpjf9Z+J8IJsmAB
/2klSGFcRPtUWHIBmLSKVqXN3nTo4rmk+ahx5ZUaafhwo3qzo6mX0OQa68QkijfZ
q6ZXxrpXOkIiHb/owaA2fw1fxsGyHWM9BkiTbG16pRAnyvPhQicy575lArme1i+y
Cnr7I14ObOw7WKZlBo8Bor4rt7Ii8qW1kvdS2NosL+8MFDdHuzLRVSfRq84QzTvw
aG5ziKz0Ckiv5AdRDa1ykFXHEg3Zvbwj6e2uEFuJdBFj1Sio+wYXl1IDpCwpai0h
/SOZYb68aEUFIeZb5UpLGdcHpE+KPmSUdPPAKzemi55DA08YGBY=
=CG09
-END PGP SIGNATURE End Message ---

Processed: mail-notification: Raising severity of libgnome dependency bug

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #868403 [src:mail-notification] mail-notification: Please drop the 
(build-)dependency against gnome-vfs
Severity set to 'serious' from 'important'

-- 
868403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868403
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#894050: xerces-c: CVE-2017-12627: Null pointer dereference while processing the path to DTD allows denial of service

[Salvatore Bonaccorso]

Source: xerces-c
Version: 3.2.0+debian-2
Severity: grave
Tags: patch security upstream

Hi,

the following vulnerability was published for xerces-c.

CVE-2017-12627[0]:
| In Apache Xerces-C XML Parser library before 3.2.1, processing of
| external DTD paths can result in a null pointer dereference under
| certain conditions.

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-12627
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-12627
[1] https://svn.apache.org/viewvc?view=revision=1819998
[2] https://xerces.apache.org/xerces-c/secadv/CVE-2017-12627.txt

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#893049: libfiu FTBFS: recipe for target 'run-test-basic_ctrl.py' failed

[Chris Lamb]

tags 893049 + fixed-upstream
thanks

Hi Alberto,

> That also explains why it works when you go to the failed directory and
> run it manually.

Ahh! Of course. :-)

> Can you give this patch a try?
> https://blitiri.com.ar/git/r/libfiu/c/053239cab98817561187dfca491203401fae5b9c/

Works for me; looking forward to the new release!

(FYI did you see the SYNOPSIS → SYNOPSYS typo correction?)


Best wishes,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Processed: mssh: raising severity of gconf dependency bug

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #886055 [src:mssh] mssh: Depends on gconf
Severity set to 'serious' from 'important'

-- 
886055: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886055
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: morris: raising severity of gconf dependency bug

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #886056 [src:morris] morris: Depends on gconf
Severity set to 'serious' from 'important'

-- 
886056: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886056
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: gpdftext: raising severity of gconf dependency bug

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #885666 [src:gpdftext] gpdftext: Depends on gconf
Severity set to 'serious' from 'important'

-- 
885666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885666
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: gtkwave: raising severity of gconf dependency bug

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #886067 [src:gtkwave] gtkwave: Depends on gconf
Severity set to 'serious' from 'important'

-- 
886067: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886067
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#890400: Any news about a new upstream version with new SONAME?

[Andreas Tille]

Looks strange.  May be you create a fresh clone and try again?

On Sun, Mar 25, 2018 at 08:51:11PM +0200, Julien Yann Dutheil wrote:
> Dear Andreas,
> 
> I moved forward with libbpp-seq, but after pushing I got the following
> message:
> 
> remote: Resolving deltas: 100% (172/172), completed with 152 local objects.
> remote:
> remote: To create a merge request for pristine-tar, visit:
> remote:
> https://salsa.debian.org/med-team/libbpp-seq/merge_requests/new?merge_request%5Bsource_branch%5D=pristine-tar
> remote:
> remote: To create a merge request for upstream, visit:
> remote:
> https://salsa.debian.org/med-team/libbpp-seq/merge_requests/new?merge_request%5Bsource_branch%5D=upstream
> remote:
> 
> Clicking on the suggested links leads to a 404 error (I do not have
> permission to access this page).
> 
> Is everything ok or did I somehow do sthg wrong?
> 
> Best,
> 
> Julien.
> 
> On Thu, Mar 22, 2018 at 11:17 AM, Julien Yann Dutheil <
> julien.duth...@univ-montp2.fr> wrote:
> 
> > Hi Andreas,
> >
> > On Thu, Mar 22, 2018 at 10:17 AM, Andreas Tille  wrote:
> >
> >> Hi Julien,
> >>
> >> On Wed, Mar 21, 2018 at 09:26:01PM +0100, Julien Yann Dutheil wrote:
> >> > I could somehow udate the symbols list, but still get a lintian warning
> >> > [1].
> >>
> >> That was just a typo (see commit 06beb6872bb0c773aff727c25dfe07
> >> 77a7c401ca).
> >>
> >> Ok, thanks.
> >
> >
> >> > I have pushed my commits, would you mind giving them a look? Will
> >> > proceed with other libs once I have confirmation that everything is ok.
> >>
> >> I've just uploaded.  I think the following lintian *infos* (lintian -I)
> >> will be interesting for you:
> >>
> >> I: libbpp-core source: testsuite-autopkgtest-missing
> >> N:
> >> N:This package does not declare a test suite. Having a test suite
> >> helps
> >> N:with automated QA in response to changes in the archive. For
> >> example, if
> >> N:your package has a test suite, it is possible to re-execute that
> >> test
> >> N:suite when any of the package dependencies has a new version and
> >> check
> >> N:whether that update caused problems for your package.
> >> N:
> >> N:To declare a test suite, please add a debian/tests/control file to
> >> your
> >> N:package.
> >> N:
> >> N:For more information on how to add functional tests to your package,
> >> N:browse to https://ci.debian.net/doc/.
> >> N:
> >> N:Severity: wishlist, Certainty: certain
> >> N:
> >> N:Check: testsuite, Type: source
> >>
> >> May be you see a chance to tweak the build time test into an autopkgtest.
> >>
> >> Humm... not sure how that integrates with our existing series of unit
> > tests at build time?
> >
> > I: libbpp-core4: spelling-error-in-binary 
> > usr/lib/x86_64-linux-gnu/libbpp-core.so.4.0.0
> >> colums columns
> >> I: libbpp-core4: spelling-error-in-binary 
> >> usr/lib/x86_64-linux-gnu/libbpp-core.so.4.0.0
> >> controled controlled
> >> I: libbpp-core4: spelling-error-in-binary 
> >> usr/lib/x86_64-linux-gnu/libbpp-core.so.4.0.0
> >> wih with
> >>
> >> Please verify your code and simply fix with next upstream release if
> >> these are no false positives.
> >>
> >> Wow, impressive! Fixed upstream. fortunately, no interface break :)
> >
> >>
> >> Kind regards and thanks for your cooperation
> >>
> >> Thanks a lot for your patience and advice!
> >
> > Julien.
> >
> >>Andreas.
> >>
> >> --
> >> http://fam-tille.de
> >>
> >>
> >
> >
> > --
> > Julien Y. Dutheil, Ph-D
> > 0 (+49) 6421 178 986 <+49%206421%20178986>
> >
> > § Max Planck Institute for Evolutionary Biology
> > Molecular Systems Evolution
> > Department of Evolutionary Genetics
> > Plön -- GERMANY
> >
> > § Institute of Evolutionary Sciences - Montpellier
> > University of Montpellier 2 -- FRANCE
> >
> 
> 
> 
> -- 
> Julien Y. Dutheil, Ph-D
> 0 (+49) 4522 763 298
> 
> § Max Planck Institute for Evolutionary Biology
> Molecular Systems Evolution
> Department of Evolutionary Genetics
> Plön -- GERMANY
> 
> § Institute of Evolutionary Sciences - Montpellier
> University of Montpellier 2 -- FRANCE

-- 
http://fam-tille.de

Bug#894056: gconf-editor: only useful for gconf which is being removed from Debian

[Jeremy Bicha]

Source: gconf-editor
Version: 3.0.1-4
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs gconf
Tags: sid buster

As announced, we are working to remove gconf from Debian. As part of this 
process, I am now filing this RC bug.

References
--
https://lists.debian.org/debian-devel/2018/02/msg00169.html

https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=pkg-gnome-maintain...@lists.alioth.debian.org;tag=gconf

On behalf of the Debian GNOME team,
Jeremy Bicha

Bug#893247: Intend to take over libjbzip2-java and libnanoxml2-java into Debian Med team

[Andreas Tille]

Hi Emmanuel,

On Sun, Mar 25, 2018 at 10:55:54AM -0700, tony mancill wrote:
> On Sun, Mar 25, 2018 at 06:37:05PM +0200, Emmanuel Bourg wrote:
> > These are quite generic non-med related libraries, I'd prefer keeping them 
> > under the Java Team umbrella.

I'm fine with moving libjbzip2-java (which I uploaded today) once
pkg-java has moved to Salsa (or did I missed the move?)
 
> Multiple teams wanting to maintain a library is a good problem to have.
> I propose we consider:
> 
> (a) pulling these libraries into the "Debian" project on Salsa, which
> replaces collab-maint and grants commit permissions to all DDs and any
> designated guest account

Hmmm, I admit I prefer a real team since I have the impression that the
love a package receives is higher than for packages that end up in the
collab-maint / debian "dustbin".
 
> OR
> 
> (b) relaxing the default pkg-java permissions to be like those of the
> Debian Perl Team and allow all DDs by default

I'd prefer this a lot.  We did so for Debian Med on Alioth - I'm not
sure how that works on Salsa but if we found out this will be
established.
 
> OR
> 
> (c) configuring any other mechanism that would allow the union of these
> two teams (and others!) to contribute to the packaging.

Definitely.
 
> As for which team is listed in the Maintainer field, I don't think it
> matters much as long as we have a suitable set of interested Uploaders.

I agree that it does not matter much.  We have some lib*-java as well as
python-* and lib*-perl packages maintained in Debian Med team if there
are only Debian Med rdepends.  If we think about it like in the
libjbzip2-java case we should not only move back this one but also other
packages to the Java team.  That would be fine for me but there are
always cases where one needs to decide between (at least) two teams.

Kind regards

   Andreas.

-- 
http://fam-tille.de

Processed: apcupsd: raising severity of gconf dependency bug

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #885820 [src:apcupsd] apcupsd: Depends on gconf
Severity set to 'serious' from 'important'

-- 
885820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885820
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: ooo-thumbnailer: raising severity of gconf dependency bug

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #886051 [src:ooo-thumbnailer] ooo-thumbnailer: Depends on gconf
Severity set to 'serious' from 'important'

-- 
886051: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886051
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: gnome-commander: raising severity of gconf dependency bug

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #886076 [src:gnome-commander] gnome-commander: Depends on gconf
Severity set to 'serious' from 'important'

-- 
886076: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886076
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: camorama: raising severity of gconf dependency bug

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #886086 [src:camorama] camorama: Depends on gconf
Severity set to 'serious' from 'important'

-- 
886086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886086
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: grdesktop: raising severity of gconf dependency bug

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #886071 [src:grdesktop] grdesktop: Depends on gconf
Severity set to 'serious' from 'important'

-- 
886071: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886071
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: pulseaudio-module-gconf: raising severity of gconf dependency bug

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #757909 [pulseaudio-module-gconf] pulseaudio-module-gconf: migration to a 
dconf PA backend
Severity set to 'serious' from 'important'

-- 
757909: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757909
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: soundconverter: raising severity of gconf dependency bug

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #886046 [src:soundconverter] soundconverter: Depends on gconf
Severity set to 'serious' from 'important'

-- 
886046: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886046
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: plasma-pa: raising severity of gconf dependency bug

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #886048 [src:plasma-pa] plasma-pa: Depends on gconf
Severity set to 'serious' from 'important'

-- 
886048: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886048
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#885819: almanah: Depends on gconf

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #885819 [src:almanah] almanah: Depends on gconf
Severity set to 'serious' from 'important'
> tags -1 +patch
Bug #885819 [src:almanah] almanah: Depends on gconf
Added tag(s) patch.

-- 
885819: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885819
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#893179: Pending fixes for bugs in the icu4j-49 package

[pkg-java-maintainers]

tag 893179 + pending
thanks

Some bugs in the icu4j-49 package are closed in revision
48d80c71fceb30e9374a1f357b1c58231ba5bb61 in branch 'master' by
Emmanuel Bourg

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/icu4j-49.git/commit/?id=48d80c7

Commit message:

Fixed the build failure with Java 9 (Closes: #893179)

Processed: Pending fixes for bugs in the icu4j-49 package

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tag 893179 + pending
Bug #893179 [src:icu4j-49] icu4j-49 FTBFS with openjdk-9
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
893179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893179
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: sugar: raising severity of gconf dependency bug

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #886042 [sugar-read-activity] sugar-read-activity: Depends on gconf
Severity set to 'serious' from 'important'

-- 
886042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886042
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: sugar: raising severity of gconf dependency bug

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #886040 [sugar-session] sugar-session: Depends on gconf
Severity set to 'serious' from 'important'

-- 
886040: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886040
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: sugar: raising severity of gconf dependency bug

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #886043 [sugar-write-activity] sugar-write-activity: Depends on gconf
Severity set to 'serious' from 'important'

-- 
886043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886043
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: sugar: raising severity of gconf dependency bug

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #886041 [sugar-browse-activity] sugar-browse-activity: Depends on gconf
Severity set to 'serious' from 'important'

-- 
886041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886041
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#893247: Intend to take over libjbzip2-java and libnanoxml2-java into Debian Med team

[Emmanuel Bourg]

Le 25/03/2018 à 19:55, tony mancill a écrit :

> Multiple teams wanting to maintain a library is a good problem to have.
> I propose we consider:
> 
> (a) pulling these libraries into the "Debian" project on Salsa, which
> replaces collab-maint and grants commit permissions to all DDs and any
> designated guest account

-1

> (b) relaxing the default pkg-java permissions to be like those of the
> Debian Perl Team and allow all DDs by default

+1, but note that this is basically how it already works today since any
request to join the pkg-java group (or now java-team on Salsa) is always
granted.

Emmanuel Bourg

Bug#893247: Bug#893268: Intend to take over libjbzip2-java and libnanoxml2-java into Debian Med team

[Emmanuel Bourg]

Le 25/03/2018 à 23:29, Andreas Tille a écrit :

> I'm fine with moving libjbzip2-java (which I uploaded today) once
> pkg-java has moved to Salsa (or did I missed the move?)

I'm working on the migration, I haven't finalized the notification hooks
yet.

Bug#893247: Intend to take over libjbzip2-java and libnanoxml2-java into Debian Med team

[gregor herrmann]

On Sun, 25 Mar 2018 23:29:13 +0200, Andreas Tille wrote:

> > (b) relaxing the default pkg-java permissions to be like those of the
> > Debian Perl Team and allow all DDs by default
> I'd prefer this a lot.  We did so for Debian Med on Alioth - I'm not
> sure how that works on Salsa but if we found out this will be
> established.

FWIW, the perl-team projects on Salsa are not DD-writable any more
because that's not as simple as it was on Alioth.
IIRC it's not possible to grant permissions ("share with ..") on a
group or sub-group level, only for each individual project, and that
takes ages via the API and whatnot.

I found my report from January:
https://lists.debian.org/debian-perl/2018/01/msg00045.html
  

Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Rolling Stones


signature.asc
Description: Digital Signature

Bug#893179: marked as done (icu4j-49 FTBFS with openjdk-9)

[Debian Bug Tracking System]

Your message dated Sun, 25 Mar 2018 22:05:17 +
with message-id 
and subject line Bug#893179: fixed in icu4j-49 49.1-3
has caused the Debian Bug report #893179,
regarding icu4j-49 FTBFS with openjdk-9
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
893179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893179
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: icu4j-49
Version: 49.1-2
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/icu4j-49.html

...
dh_auto_clean
ant clean
Buildfile: /build/1st/icu4j-49-49.1/build.xml

BUILD FAILED
/build/1st/icu4j-49-49.1/build.xml:57: The JDK version is too old or unknown.

Total time: 0 seconds
dh_auto_clean: ant clean returned exit code 1
make[1]: *** [debian/rules:19: override_dh_auto_clean] Error 2
--- End Message ---
--- Begin Message ---
Source: icu4j-49
Source-Version: 49.1-3

We believe that the bug you reported is fixed in the latest version of
icu4j-49, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 893...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated icu4j-49 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 25 Mar 2018 23:45:03 +0200
Source: icu4j-49
Binary: libicu4j-49-java
Architecture: source
Version: 49.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Java maintainers 

Changed-By: Emmanuel Bourg 
Description:
 libicu4j-49-java - Library for Unicode support and internationalization
Closes: 893179
Changes:
 icu4j-49 (49.1-3) unstable; urgency=medium
 .
   * Team upload.
   * Fixed the build failure with Java 9 (Closes: #893179)
   * Standards-Version updated to 4.1.3
   * Switch to debhelper level 11
   * Use secure Vcs-* URLs
Checksums-Sha1:
 cc9c841cf0179076a60218e5b7f310baec1872bc 2063 icu4j-49_49.1-3.dsc
 3bb97ffe0a5db91014af31afdb6327ae81901f36 4268 icu4j-49_49.1-3.debian.tar.xz
 2f8022ef1dc575088aa079af3457d7224b0dd271 11375 icu4j-49_49.1-3_source.buildinfo
Checksums-Sha256:
 b9ee2e845b26c9ce6571cb004b07cc5543b3db5d1279851446cf3cced5bdf6fc 2063 
icu4j-49_49.1-3.dsc
 c223e24f59e0e603fc18734edec7de49bd05c77d25c66ec08d63038672af026f 4268 
icu4j-49_49.1-3.debian.tar.xz
 54526113be71fdb832888c48d2f0b86b12e478500e68ec1392846dd5258f9909 11375 
icu4j-49_49.1-3_source.buildinfo
Files:
 2c0a97048f8c6754cb997cedc0aef28f 2063 java optional icu4j-49_49.1-3.dsc
 df3855178975d548d71ca558db5c8d1d 4268 java optional 
icu4j-49_49.1-3.debian.tar.xz
 98295c9aafd3da01d0bd703e77b5709c 11375 java optional 
icu4j-49_49.1-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAlq4GNYSHGVib3VyZ0Bh
cGFjaGUub3JnAAoJEPUTxBnkudCsUaUP/2E61xCitp1XnWgFLI7ah+PVbA3QaQYm
FZR0kh/KciQfaskdEvyEUPW74aw27ItMuKcjWYki6arZNRA5vqY3MfcaQhqoxtDg
DITynsspSDjJvMFMsP88RIsY3ihZ3wI/rzzzwFVOUidyTuUbHsi5u2iBa/JMntHy
LOpe/ROv5OvMOUlGsb0iqNmsxH9Jry8xeylmCNZCqlp0VVlZMGn6ZTuXFoe1EKgd
R7dFJBS5C6b+nvAAh6AauffcqF40aSuG7vhqeemtjID4aSGfGbaFJ99BnfPJyiAz
f+WwJLnB/1UslLKff0OL7I1OItvrhmInBDN4vZ0tb9w+y6TBHB/p8y07KiR4JsXG
FQM4poFyat+RqwqqWjKe22osw6UeKxZM1tMY4ES7BwZNBY1uF+3XGqDJZtLNdIOY
E4Ka6P39ja4yCAzzmpyA+7r3R4vdBe3tCmMb6UXtTzTui0XxgTNJC15RnKVRP+xB
3oIOOCqm06DfzhMeekYDRTNeNlnF8bu04+xUORaHNFluCqKmLomPLumlNcnGq9LH
YICqPusE/6bwEC8On+9Ou2Cynxwrtz7PtTg2iRfr4jDLt8yyLz8Qs38p0HrZ7MWp
jo0Zb7qkAXPeV1UygAA/JwK3Mt5m1Jan9dW8SXS47YS3P7pfpd1VZsnRmfTYWzHR
iimDKLB/9mQt
=IQmh
-END PGP SIGNATURE End Message ---

Bug#863784: policykit-1: Please drop dependency against mozjs 1.8.5

[Martin Pitt]

Control: tag -1 -buster

bi...@debian.org [2017-05-31  9:24 +0200]:
> Source: policykit-1
> Version: 0.113-2
> Severity: normal
> Tags: sid buster
> User: pkg-gnome-maintain...@lists.alioth.debian.org
> Usertags: oldlibs mozjs185
> 
> Dear maintainer,
> 
> Your package is depending against mozjs 1.8.5. This package is old
> and currently orphaned.

Removing buster tag, as this version is only in experimental - for exactly this
reason. We really don't want policykit to use mozjs in any release, both for
maintenance/security reasons and also because it's a rather bad idea in general
to have a touring complete and weakly-typed language to describe security
properties instead of the current declarative rules.

Martin

Processed: Re: Bug#863784: policykit-1: Please drop dependency against mozjs 1.8.5

[Debian Bug Tracking System]

Processing control commands:

> tag -1 -buster
Bug #863784 [src:policykit-1] policykit-1: Please drop dependency against mozjs 
1.8.5
Removed tag(s) buster.

-- 
863784: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863784
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Merge duplicates

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 894033 python3-tornado
Bug #894033 [jupyter-notebook] jupyter-notebook: jupyter notebook: IOLoop has 
no attribute initialized
Bug reassigned from package 'jupyter-notebook' to 'python3-tornado'.
No longer marked as found in versions jupyter-notebook/5.4.0-1.
Ignoring request to alter fixed versions of bug #894033 to the same values 
previously set
> forcemerge 893360 894033
Bug #893360 {Done: Julien Puydt } [python3-tornado] 
python3-tornado 5.0.0 breaks python3-zmq
Bug #893385 {Done: Julien Puydt } [python3-tornado] 
ipykernel FTBFS: test failures
Bug #893474 {Done: Julien Puydt } [python3-tornado] 
jupyter-core: AttributeError on launch since last update of python 3.6 in Sid
Bug #894033 [python3-tornado] jupyter-notebook: jupyter notebook: IOLoop has no 
attribute initialized
Severity set to 'serious' from 'grave'
Marked Bug as done
Added indication that 894033 affects 
src:ipykernel,jupyter-notebook,src:jupyter-notebook,jupyter-nbconvert,python3-ipykernel,src:jupyter-client
Marked as fixed in versions python-tornado/5.0.0-2.
Marked as found in versions python-tornado/5.0.0-1.
Bug #893385 {Done: Julien Puydt } [python3-tornado] 
ipykernel FTBFS: test failures
Removed indication that 893385 affects jupyter-nbconvert, python3-ipykernel, 
jupyter-notebook, src:jupyter-notebook, src:ipykernel, and src:jupyter-client
Added indication that 893385 affects 
src:ipykernel,jupyter-notebook,src:jupyter-notebook,jupyter-nbconvert,python3-ipykernel,src:jupyter-client
Removed indication that 893360 affects src:jupyter-notebook, jupyter-notebook, 
python3-ipykernel, jupyter-nbconvert, src:jupyter-client, and src:ipykernel
Added indication that 893360 affects 
src:ipykernel,jupyter-notebook,src:jupyter-notebook,jupyter-nbconvert,python3-ipykernel,src:jupyter-client
Removed indication that 893474 affects src:ipykernel, src:jupyter-client, 
jupyter-notebook, jupyter-nbconvert, python3-ipykernel, and src:jupyter-notebook
Added indication that 893474 affects 
src:ipykernel,jupyter-notebook,src:jupyter-notebook,jupyter-nbconvert,python3-ipykernel,src:jupyter-client
Bug #893474 {Done: Julien Puydt } [python3-tornado] 
jupyter-core: AttributeError on launch since last update of python 3.6 in Sid
Merged 893360 893385 893474 894033
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
893360: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893360
893385: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893385
893474: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893474
894033: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894033
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#893049: libfiu FTBFS: recipe for target 'run-test-basic_ctrl.py' failed

[Alberto Bertogli]

On Fri, Mar 16, 2018 at 03:28:24PM +, Chris Lamb wrote:
> Hi Alberto and Adrian
> 
> > https://github.com/lamby/pkg-libfiu/commit/9bf63e144117fbd382f4053a4338041b975b8c67
> […]
> > Thanks for coming up with a patch for this!
> 
> Actually the patch doesn't work. Or, rather, it's stranger than that. If
> I build the package using fairly vanilla scripts (or on the official buildds
> as Adrian as pointed out and reopened to match) the package fails to build,
> even with this patch.
> 
> However, if I then go into the failed build directory and run `make test`
> the test passes (same chroot/container!). Does that help diagnose it at
> all? :)

It does!  Sorry for the delay in replying.

It's a build race issue.  I managed to reproduce this locally by running
with -j 8 (but weirdly, not if I teed its output!).

That also explains why it works when you go to the failed directory and
run it manually.


Can you give this patch a try?
https://blitiri.com.ar/git/r/libfiu/c/053239cab98817561187dfca491203401fae5b9c/

Once you confirm it works (fingers crossed), I'll include it in the
master branch and cut a new release (it's been a while and there are
other changes as well).

Thanks a lot!
Alberto

Bug#873227: Please upgrade to 4.1: Java 9 support

[tony mancill]

On Sun, Mar 25, 2018 at 04:03:59PM +0200, Markus Koschany wrote:
> Hi tony,
> 
> Am 25.03.2018 um 06:26 schrieb tony mancill:
> [...]
> 
> > I'm going to upload to experimental momentarily and ask others on the
> > Java Team if there any concern about uploading Gradle 3.4 to unstable.
> 
> Let's do it. I remember there were two failing packages with Gradle 3.4
> but BND might be fixed already thanks to Kai-Chung Yan. I guess we will
> solve the remaining issues as well eventually.

Done, and thank you for the pointer regarding BND.  There was a problem
with ivy failing to parse the POM for gradle-logging due to the
jansi-native dependency being added without a groupId (which just seems
weird to me).  Fortunately specifying the group explicitly resolved the
problem for BND.

Hopefully there is not too much additional fall-out from the update, but
I'll be watching for it.

Cheers,
tony


signature.asc
Description: PGP signature

Processed: gjiten: Raising severity of libgnomeui dependency bug

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #868422 [src:gjiten] gjiten: Please drop the (build-)dependency against 
gnome-vfs
Severity set to 'serious' from 'important'

-- 
868422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868422
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: grdesktop: Raising severity of libgnome dependency bug

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #868427 [src:grdesktop] grdesktop: Please drop the (build-)dependency 
against gnome-vfs
Severity set to 'serious' from 'important'

-- 
868427: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868427
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: found 894050 in 3.1.1-5.1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 894050 3.1.1-5.1
Bug #894050 [src:xerces-c] xerces-c: CVE-2017-12627: Null pointer dereference 
while processing the path to DTD allows denial of service
Marked as found in versions xerces-c/3.1.1-5.1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
894050: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894050
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#894051: kubernetes: CVE-2017-1002102

[Salvatore Bonaccorso]

Source: kubernetes
Version: 1.7.7+dfsg-3
Severity: grave
Tags: patch security upstream
Forwarded: https://github.com/kubernetes/kubernetes/issues/60814

Hi,

the following vulnerability was published for kubernetes.

CVE-2017-1002102[0]:
| In Kubernetes versions 1.3.x, 1.4.x, 1.5.x, 1.6.x and prior to
| versions 1.7.14, 1.8.9 and 1.9.4 containers using a secret, configMap,
| projected or downwardAPI volume can trigger deletion of arbitrary
| files/directories from the nodes where they are running.

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-1002102
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1002102
[1] https://github.com/kubernetes/kubernetes/issues/60814

Regards,
Salvatore

Processed: ogmrip: raising severity of gconf dependency bug

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #886052 [src:ogmrip] ogmrip: Depends on gconf
Severity set to 'serious' from 'important'

-- 
886052: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886052
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: morla: raising severity of gconf dependency bug

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #886058 [src:morla] morla: Depends on gconf
Severity set to 'serious' from 'important'

-- 
886058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886058
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: gxneur: raising severity of gconf dependency bug

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #886066 [src:gxneur] gxneur: Depends on gconf
Severity set to 'serious' from 'important'

-- 
886066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886066
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems