Bug#895811: marked as done (inotify-tools: do not enable sanitizers in production)

[Debian Bug Tracking System]

Your message dated Wed, 18 Apr 2018 05:49:51 +
with message-id 
and subject line Bug#895811: fixed in inotify-tools 3.14-5
has caused the Debian Bug report #895811,
regarding inotify-tools: do not enable sanitizers in production
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.)


-- 
895811: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895811
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: inotify-tools
Version: 3.14-4
Severity: grave

Hi,

In inotify-tools 3.14-4, all the qa sanitizers were enabled in
DEB_BUILD_MAINT_OPTIONS. This should not be done in production.

* Many architectures do not support sanitizers. Your package FTBFS on
mips* due to this. While clang supports ASan on mips, gcc does not.

* The man page for dpkg-buildflags explicitly states these options
should not be used in production builds and are for debugging only.

* Enabling sanitizers causes an approx 2x performance penalty.

* Enabling ASan changes the behavior of a program in some circumstances
(mainly relating to memory management and things like LD_PRELOAD no
longer work without hacks). Enabling ASan in a library package is even
worse because you will impose these behavior changes on all users of
your library who may not be expecting them.

* ASan complains about memory leaks and these are easy to reproduce with
inotify-tools. While this is very useful during development, I do not
think users should be subjected to these types of bugs which are mostly
harmless. Eg run inotifywait without any arguments are ASan will
complain loudly.

* Users of libinotifytools0 must now enable ASan themselves or use the
LD_PRELOAD hack otherwise they will not start. For example, the attached
simple test program fails to run with:

==19349==ASan runtime does not come first in initial library list; you
should either link runtime to your application or manually preload it
with LD_PRELOAD.

Thanks,
James
#include 

int main(void)
{
inotifytools_initialize();
return 0;
}


signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: inotify-tools
Source-Version: 3.14-5

We believe that the bug you reported is fixed in the latest version of
inotify-tools, 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 895...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dmitry Bogatov  (supplier of updated inotify-tools 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: Tue, 17 Apr 2018 22:22:55 +0300
Source: inotify-tools
Binary: libinotifytools0 libinotifytools0-dev inotify-tools
Architecture: source
Version: 3.14-5
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Bogatov 
Changed-By: Dmitry Bogatov 
Description:
 inotify-tools - command-line programs providing a simple interface to inotify
 libinotifytools0 - utility wrapper around inotify
 libinotifytools0-dev - Development library and header files for 
libinotifytools0
Closes: 895811
Changes:
 inotify-tools (3.14-5) unstable; urgency=medium
 .
   * Disable sanitize build flags (Closes: #895811)
   * Remove sanitize symbols from symbols file
Checksums-Sha1:
 3770863da28cfd2b2ddf4d430a31a72cdb7006c0 2194 inotify-tools_3.14-5.dsc
 9205cbcf4f73d61c655c896fb8e347958e51bf01 6832 inotify-tools_3.14-5.diff.gz
Checksums-Sha256:
 7318692288a7d17621ba9c599962aba60e569a5bff7098d6145b25e526ed8528 2194 
inotify-tools_3.14-5.dsc
 05c837ee4e66d57f9c7538145327de82d1ee2a8f28315689d8931024945f3ab9 6832 
inotify-tools_3.14-5.diff.gz
Files:
 b18782f7d24957de71476a62f000219f 2194 misc optional inotify-tools_3.14-5.dsc
 d82f8f7981dd5f4246a7db2de31aceec 6832 misc optional 
inotify-tools_3.14-5.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEm5FwB64DDjbk/CSLaVt65L8GYkAFAlrW2FkACgkQaVt65L8G
YkBXDw/5AYOSi/jDlckHeog5l50TSu65ZvtsymLUGeVEGaa4gw9+0K6DpRuIZEeT
jyHkkliTK/qbQ5httOdbGQz4Vge6OVXtS/25o3H2M8NMG+S7qqlyK/yay2ia0dMW
qli8I6qFwmSXM79A14rHh0o6X9ZiBl88KVjJWn4dLtf/8USPSE+WCluX+HqfxNjA
7XM7K6upMv/PAX1S42i/m5LF+ashP/LCxY6OdzqFmZH3AYaarNoePsMAilrbv9Ur

Processed: severity of 895315 is important, tagging 895315

[Debian Bug Tracking System]

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

> # still works with Firefox ESR
> severity 895315 important
Bug #895315 [xul-ext-greasemonkey] xul-ext-greasemonkey: Could not use script 
with recent firefox need to upgrade to 4.x
Severity set to 'important' from 'grave'
> tags 895315 + sid buster
Bug #895315 [xul-ext-greasemonkey] xul-ext-greasemonkey: Could not use script 
with recent firefox need to upgrade to 4.x
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Processed: tagging 895463, user ubuntu-de...@lists.ubuntu.com, usertagging 895463

[Debian Bug Tracking System]

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

> tags 895463 + patch
Bug #895463 [src:keyutils] keyutils FTBFS: Can't Determine Endianness
Added tag(s) patch.
> user ubuntu-de...@lists.ubuntu.com
Setting user to ubuntu-de...@lists.ubuntu.com (was vor...@debian.org).
> usertags 895463 ubuntu-patch bionic
There were no usertags set.
Usertags are now: ubuntu-patch bionic.
> thanks
Stopping processing here.

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

Bug#895463: keyutils FTBFS: Can't Determine Endianness

[Steve Langasek]

Package: keyutils
Followup-For: Bug #895463
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu bionic ubuntu-patch

Dear Christian,

This bug is reproducible in Ubuntu, and I tracked it down to the change to
build /bin/bash with -fPIE, which changes the 'file' signature for
/proc/$$/exe (aka /bin/bash) to no longer report that it is an "[LM]SB
executable".

I have uploaded the attached patch to Ubuntu, which makes keyutils'
endianness detection portable to systems which build with -fPIE.  Please
consider including it in Debian as well.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru keyutils-1.5.9/debian/patches/endianness-and-PIE.patch 
keyutils-1.5.9/debian/patches/endianness-and-PIE.patch
--- keyutils-1.5.9/debian/patches/endianness-and-PIE.patch  1969-12-31 
16:00:00.0 -0800
+++ keyutils-1.5.9/debian/patches/endianness-and-PIE.patch  2018-04-17 
21:21:12.0 -0700
@@ -0,0 +1,24 @@
+Description: fix regexp match against `file /proc/$$/exe` for -fPIE bash
+ Now that bash is built with PIE enabled, keyutils' check for endianness
+ fails because file no longer returns "executable", but instead returns
+ "shared object".  Update our regexps to be portable.
+Author: Steve Langasek 
+Last-Modified: 2018-04-17
+
+Index: keyutils-1.5.9/tests/toolbox.inc.sh
+===
+--- keyutils-1.5.9.orig/tests/toolbox.inc.sh
 keyutils-1.5.9/tests/toolbox.inc.sh
+@@ -19,10 +19,10 @@
+ echo === $OUTPUTFILE ===
+ 
+ endian=`file -L /proc/$$/exe`
+-if expr "$endian" : '.* MSB executable.*' >&/dev/null
++if expr "$endian" : '.* MSB \(executable\|shared object\).*' >&/dev/null
+ then
+ endian=BE
+-elif expr "$endian" : '.* LSB executable.*' >&/dev/null
++elif expr "$endian" : '.* LSB \(executable\|shared object\).*' >&/dev/null
+ then
+ endian=LE
+ else
diff -Nru keyutils-1.5.9/debian/patches/series 
keyutils-1.5.9/debian/patches/series
--- keyutils-1.5.9/debian/patches/series2017-11-21 08:14:40.0 
-0800
+++ keyutils-1.5.9/debian/patches/series2018-04-17 21:18:02.0 
-0700
@@ -16,3 +16,4 @@
 Make-build-reproducible.patch
 Drop-tests-requiring-CONFIG_BIG_KEYS.patch
 Adjust-tests-for-3.18-kernel-change.patch
+endianness-and-PIE.patch

Bug#889530: marked as done (acm FTBFS with gdbm 1.14.1-2)

[Debian Bug Tracking System]

Your message dated Wed, 18 Apr 2018 03:04:57 +
with message-id 
and subject line Bug#889530: fixed in acm 5.0-29.2
has caused the Debian Bug report #889530,
regarding acm FTBFS with gdbm 1.14.1-2
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.)


-- 
889530: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889530
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: acm
Version: 5.0-29.1
Severity: serious
Tags: buster sid

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

...
gcc -DSDBM -DDUFF  -DSTDC_HEADERS=1 -DHAVE_SYS_TIME_H=1 -DHAVE_STDLIB_H=1 
-DHAVE_UNISTD_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_FCNTL_H=1 
-DTIME_WITH_SYS_TIME=1 -DHAVE_MSG_CONTROL=1 -DHAVE_RECVMSG=1 -DHAVE_STRDUP=1 
-DHAVE_NEW_RPCGEN=1   -Wdate-time -D_FORTIFY_SOURCE=2  -c -o dbe.o dbe.c
dbe.c:4:10: fatal error: gdbm-ndbm.h: No such file or directory
 #include 
  ^
compilation terminated.
: recipe for target 'dbe.o' failed
make[3]: *** [dbe.o] Error 1
--- End Message ---
--- Begin Message ---
Source: acm
Source-Version: 5.0-29.2

We believe that the bug you reported is fixed in the latest version of
acm, 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 889...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated acm 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: Wed, 18 Apr 2018 03:18:08 +0200
Source: acm
Binary: acm
Architecture: source
Version: 5.0-29.2
Distribution: unstable
Urgency: medium
Maintainer: Phil Brooke 
Changed-By: Markus Koschany 
Description:
 acm- Multi-player classic aerial combat simulation
Closes: 889530
Changes:
 acm (5.0-29.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Build-depend on libgdbm-compat-dev and fix the FTBFS with newer gdbm
 versions. (Closes: #889530)
   * wrap-and-sort -sa.
   * Switch to compat level 11 (was 6).
   * d/rules: Use the correct dpkg buildflag variable CFLAGS instead of
 DEBCFLAGS. This will also ensure that the -dbgsym package is created
 correctly.
   * Fix error "format-not-a-string-literal".
Checksums-Sha1:
 ac756603b56bf1621956078658c07137de801fbb 1873 acm_5.0-29.2.dsc
 f4727a282d9dfa44a2a0fb578ea8c5cce8e9bb1d 387140 acm_5.0-29.2.diff.gz
 7779e963ba8b924fc976f2c9a950539572bae938 6431 acm_5.0-29.2_amd64.buildinfo
Checksums-Sha256:
 ec48fd1d17e619111988db5552b5c4d9a204c3c2486911099af9aeed70b5ecf1 1873 
acm_5.0-29.2.dsc
 6ff55bbf5fd883e972ff561ee5d6b685c34e5b0189dcf4f65662eef70df68074 387140 
acm_5.0-29.2.diff.gz
 1de8af008363cb1c47d59bb34cf2deaae53ef3c18c03385876ad64ae6811bbab 6431 
acm_5.0-29.2_amd64.buildinfo
Files:
 8d251dd86d33e9583e4a6b84b8e5a461 1873 games optional acm_5.0-29.2.dsc
 248afcb63a0bf62e9ff44992b8032bf1 387140 games optional acm_5.0-29.2.diff.gz
 3c439bed3996c621ea46fa455b87875c 6431 games optional 
acm_5.0-29.2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAlrWoTpfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD
RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp
YW4ub3JnAAoJENmtFLlRO1HkItcQAKuM2gowhw/bY3+HcS4TbTsR2KIRUt/RxzqO
XjNb9YCSMNMjXE4A47qJVPQDKwI7f00i9GlTO3r5w8PnfXymYQwo2BduJo8j0sOI
GcVQP/L3A42j3BBBeFJIc6Jkcn8cHNVHThgyWO0ZH0JSxuuVmhIXKIEnaUjjn1pw
V1+aLJIMxU/kVqf3ZijDXtcJh2e6A9gNPBYcSROc7z51YYep2ovkL9a5obnnbNwX
aOxy+EQIy7vyBk5dETrNA3NDmLujzDEsfr9dKHNTJhO/y47ckZ/CgtSANsbjHuCv
FGatM604jpMF1FqC04Y4hHPXsAmUt57vUe1UxmJlVX6rEzfy+b3wHKdUoFa0F/Pc
05KkhSSqglp605qr8wQiYe7K529oI154QbJsVHBdTZCOrLp/i1NbJUklnng86/kh
vQXr8E1mc4YaDzsIBcP9DTYkoJXWMfJRZHlNK1QKp+VKfclc9Ru4zBdeSZpHmi24
gqNWpkEBvMj+mEZoeYSYrEamV/gcaC3u+KWlCIAVnnYgnCF3QTJVd/IG/oVqLcQF
VEG/i0VHINk05gUvg+vCn0RWLkcrPZmJHEv0/oTwkd/1O6ytpbYRtMPl05JT0lzW
Bs7GQzO0vKbzmi9Vnu+/AuPtTL7H4cF1JPXC7DKT+quceKEqUL78iB7C/QKvIlc1
jHU29UDt
=hguB
-END PGP SIGNATURE End Message ---

Bug#889530: acm FTBFS with gdbm 1.14.1-2

[Markus Koschany]

Control: tags -1 pending

Dear maintainer,

I've uploaded a new revision of acm versioned as 5.0-29.2 to fix Debian
bug #889530.

In addition I switched to compat level 11 because compat level 6 is
deprecated and will lead to another RC bug in the near future.
Furthermore I ensured that the -dbgsym package is built correctly and
format-not-a-string-literal errors were fixed as well. The rest were
some cosmetic changes like removing trailing whitespace and ordering
some lines.

The game builds fine again but I noticed the black screen and even a
segmentation fault which seems related to #765815.

Please find attached the debdiff.

Regards,

Markus
diff -u acm-5.0/debian/acm.dirs acm-5.0/debian/acm.dirs
--- acm-5.0/debian/acm.dirs
+++ acm-5.0/debian/acm.dirs
@@ -9 +8,0 @@
-
diff -u acm-5.0/debian/changelog acm-5.0/debian/changelog
--- acm-5.0/debian/changelog
+++ acm-5.0/debian/changelog
@@ -1,3 +1,17 @@
+acm (5.0-29.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Build-depend on libgdbm-compat-dev and fix the FTBFS with newer gdbm
+versions. (Closes: #889530)
+  * wrap-and-sort -sa.
+  * Switch to compat level 11 (was 6).
+  * d/rules: Use the correct dpkg buildflag variable CFLAGS instead of
+DEBCFLAGS. This will also ensure that the -dbgsym package is created
+correctly.
+  * Fix error "format-not-a-string-literal".
+
+ -- Markus Koschany   Wed, 18 Apr 2018 03:18:08 +0200
+
 acm (5.0-29.1) unstable; urgency=medium
 
   * Non-maintainer upload.
@@ -63,7 +77,7 @@
   * Update to standards-version 3.8.2.
   * Replaced build-dependency on x-dev with x11proto-core-dev
 (closes: #515356).
-  * Bump debian/compat to 6 and build-depends on debhelper.
+  * Bump debian/compat to 6 and build-depends on debhelper.
   * Now refer to GPL-2 common licence, not the GPL.
   * Adjust copyright notice in debian/copyright to add dates.
 
@@ -100,7 +114,7 @@
   * Applied patch from Mohammed Adnène Trojette:
   * Correct copyright file to show original source (closes: #372495).
   * Bump standards-version to 3.7.2 (no changes needed).
-  * Added PostScript version of acmdoc.rtf (HTML conversion lost images) 
+  * Added PostScript version of acmdoc.rtf (HTML conversion lost images)
 (closes: #372496).
 
  -- Phil Brooke   Sat, 10 Jun 2006 14:01:11 +0100
@@ -124,7 +138,7 @@
 
 acm (5.0-19) unstable; urgency=low
 
-  * Applied patch from Andreas Jochens to fix dis/sdbm/util.c so that 
+  * Applied patch from Andreas Jochens to fix dis/sdbm/util.c so that
 acm builds with amd64/gcc-3.4 (Closes: #280272).
 
  -- Phil Brooke   Thu, 11 Nov 2004 18:50:05 +
@@ -146,7 +160,7 @@
 
 acm (5.0-16) unstable; urgency=low
 
-  * Adding missing includes to prevent `assignment makes pointer from 
+  * Adding missing includes to prevent `assignment makes pointer from
 integer without a cast' warnings that are fatal on ia64
 (Closes: #226558).
   * Cleaned up similar warnings from audio.c.
@@ -237,7 +251,7 @@
 acm (5.0-6) unstable; urgency=low
 
   * Folding in suggested changes to audio code from Giuseppe Borzi'.
-  * Added -dis-silent switch.  
+  * Added -dis-silent switch.
   * More comments added to README.Debian.
 
  -- Phil Brooke   Tue, 16 Jul 2002 13:20:25 +0100
diff -u acm-5.0/debian/compat acm-5.0/debian/compat
--- acm-5.0/debian/compat
+++ acm-5.0/debian/compat
@@ -1 +1 @@
-6
+11
diff -u acm-5.0/debian/control acm-5.0/debian/control
--- acm-5.0/debian/control
+++ acm-5.0/debian/control
@@ -2,12 +2,23 @@
 Section: games
 Priority: optional
 Maintainer: Phil Brooke 
-Build-Depends: debhelper (>> 6.0.0), libx11-dev, libxext-dev, 
x11proto-core-dev, libgdbm-dev, libaudio-dev, libelfg0-dev [hurd-i386], 
sharutils
+Build-Depends:
+ debhelper (>= 11),
+ libaudio-dev,
+ libelfg0-dev [hurd-i386],
+ libgdbm-compat-dev,
+ libgdbm-dev,
+ libx11-dev,
+ libxext-dev,
+ sharutils,
+ x11proto-core-dev
 Standards-Version: 3.9.6
 
 Package: acm
 Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}
+Depends:
+ ${misc:Depends},
+ ${shlibs:Depends}
 Description: Multi-player classic aerial combat simulation
  A multiplayer aerial combat simulation. Players engage in air to air
  combat against one another using heat seeking missiles and cannons.
@@ -25,2 +35,0 @@
-
-
diff -u acm-5.0/debian/copyright acm-5.0/debian/copyright
--- acm-5.0/debian/copyright
+++ acm-5.0/debian/copyright
@@ -9,14 +9,14 @@
   This program is free software; you can redistribute it and/or modify
   it under the terms of the GNU General Public License as published by
   the Free Software Foundation; version 2 dated June, 1991.
-  
+
   This program is distributed in the hope that it will be useful,
   but WITHOUT ANY WARRANTY; without even the implied warranty of
   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
   GNU General Public License for more details.
-  
+
   You should have received a copy of the GNU 

Processed: Re: acm FTBFS with gdbm 1.14.1-2

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #889530 [src:acm] acm FTBFS with gdbm 1.14.1-2
Added tag(s) pending.

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

Bug#895965: FTBFS: needs to be patched for newer persistent

[Clint Adams]

Source: haskell-esqueleto
Version: 2.5.3-2
Severity: serious
Forwarded: https://github.com/bitemyapp/esqueleto/issues/80

.

Bug#895138: marked as done (gimp: GIMP 2.10 requires BABL >= 0.1.44 to start)

[Debian Bug Tracking System]

Your message dated Wed, 18 Apr 2018 01:19:34 +
with message-id 
and subject line Bug#894471: fixed in gegl 0.3.34-1
has caused the Debian Bug report #894471,
regarding gimp: GIMP 2.10 requires BABL >= 0.1.44 to start
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.)


-- 
894471: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894471
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gimp
Version: 2.10.0~RC1-1
Severity: important

Dear Maintainer,

GIMP 2.10.0~RC1 installed from experimental fails to start due to outaded BABL.
Could you please refresh the vesionned dependency to >= 0.1.44 ?

Error message where trying to start:
===
BABL version too old!

GIMP requires BABL version 0.1.44 or later.
Installed BABL version is 0.1.42.

Somehow you or your software packager managed
to install GIMP with an older BABL version.

Please upgrade to BABL version 0.1.44 or later.
===

Thanks,
--
Aurélien



-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing'), (200, 'unstable'), (150, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.16.0-rc6-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr 
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gimp depends on:
ii  gimp-data2.10.0~RC1-1
ii  libaa1   1.4p5-44+b1
ii  libbabl-0.1-00.1.42-1
ii  libbz2-1.0   1.0.6-8.1
ii  libc62.27-3
ii  libcairo21.15.10-1
ii  libfontconfig1   2.12.6-0.1
ii  libfreetype6 2.8.1-2
ii  libgcc1  1:8-20180321-1
ii  libgdk-pixbuf2.0-0   2.36.11-2
ii  libgegl-0.3-00.3.30-1
ii  libgexiv2-2  0.10.8-1
ii  libgimp2.0   2.10.0~RC1-1
ii  libglib2.0-0 2.56.0-4
ii  libgs9   9.22~dfsg-2
ii  libgtk2.0-0  2.24.32-1
ii  libgudev-1.0-0   232-2
ii  libharfbuzz0b1.7.2-1
ii  libilmbase23 2.2.1-2
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  liblcms2-2   2.9-1
ii  liblzma5 5.2.2-1.3
ii  libmng1  1.0.10+dfsg-3.1+b5
ii  libmypaint-1.3-0 1.3.0-2
ii  libopenexr23 2.2.1-4
ii  libopenjp2-7 2.3.0-1
ii  libpango-1.0-0   1.42.0-1
ii  libpangocairo-1.0-0  1.42.0-1
ii  libpangoft2-1.0-01.42.0-1
ii  libpng16-16  1.6.34-1
ii  libpoppler-glib8 0.62.0-2
ii  librsvg2-2   2.40.20-2
ii  libstdc++6   8-20180321-1
ii  libtiff5 4.0.9-4
ii  libwebp6 0.6.1-2
ii  libwebpdemux20.6.1-2
ii  libwebpmux3  0.6.1-2
ii  libwmf0.2-7  0.2.8.4-12
ii  libx11-6 2:1.6.5-1
ii  libxcursor1  1:1.1.15-1
ii  libxext6 2:1.3.3-1+b2
ii  libxfixes3   1:5.0.3-1
ii  libxmu6  2:1.1.2-2
ii  libxpm4  1:3.5.12-1
ii  python   2.7.14-4
ii  python-gtk2  2.24.0-5.1+b1
ii  python2.72.7.14-8
ii  xdg-utils1.1.2-2
ii  zlib1g   1:1.2.8.dfsg-5

Versions of packages gimp recommends:
ii  ghostscript  9.22~dfsg-2

Versions of packages gimp suggests:
ii  gimp-data-extras  1:2.0.2-1
pn  gimp-help-en | gimp-help  
pn  gvfs-backends 
ii  libasound21.1.3-5

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: gegl
Source-Version: 0.3.34-1

We believe that the bug you reported is fixed in the latest version of
gegl, 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 894...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jeremy Bicha  (supplier of updated gegl 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: Tue, 17 Apr 2018 20:50:32 -0400
Source: gegl
Binary: gegl libgegl-0.3-0 libgegl-dev libgegl-doc gir1.2-gegl-0.3
Architecture: source
Version: 0.3.34-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Bug#894471: marked as done (gegl: libbabl-dev build dependency should be raised to (>= 0.1.44))

[Debian Bug Tracking System]

Your message dated Wed, 18 Apr 2018 01:19:34 +
with message-id 
and subject line Bug#894471: fixed in gegl 0.3.34-1
has caused the Debian Bug report #894471,
regarding gegl: libbabl-dev build dependency should be raised to (>= 0.1.44)
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.)


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

https://buildd.debian.org/status/fetch.php?pkg=gegl=s390x=0.3.30-1=1522190230=0

...
checking for BABL... no
configure: error: Package requirements (babl >= 0.1.44) were not met:

Requested 'babl >= 0.1.44' but version of babl is 0.1.42
--- End Message ---
--- Begin Message ---
Source: gegl
Source-Version: 0.3.34-1

We believe that the bug you reported is fixed in the latest version of
gegl, 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 894...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jeremy Bicha  (supplier of updated gegl 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: Tue, 17 Apr 2018 20:50:32 -0400
Source: gegl
Binary: gegl libgegl-0.3-0 libgegl-dev libgegl-doc gir1.2-gegl-0.3
Architecture: source
Version: 0.3.34-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bicha 
Description:
 gegl   - Generic Graphics Library Test Program
 gir1.2-gegl-0.3 - GObject introspection data for the Generic Graphics Library
 libgegl-0.3-0 - Generic Graphics Library
 libgegl-dev - Generic Graphics Library (development files)
 libgegl-doc - Generic Graphics Library (documentation)
Closes: 894471
Changes:
 gegl (0.3.34-1) unstable; urgency=medium
 .
   * New upstream release
   * Bump minimum babl to 0.1.46 (Closes: #894471)
   * debian/libgegl-0.3-0.symbols: Add new symbols
   * Bump Standards-Version to 4.1.4
Checksums-Sha1:
 5ba8a54b4c37d160f25a1c7a1621e2ac316d930f 2754 gegl_0.3.34-1.dsc
 fa4c402fbdf896d7a0559403bbd5abc9e668998a 6707964 gegl_0.3.34.orig.tar.bz2
 a2c81982cad981c1b883452b23eae75fdeee7ddd 19332 gegl_0.3.34-1.debian.tar.xz
 972b38851e3bf186fed71d3e03c0c38e351fefcc 15146 gegl_0.3.34-1_source.buildinfo
Checksums-Sha256:
 ec3d5d970d7e1b57ca499702c368e5d903a521be9591e4f10156c130c52f746c 2754 
gegl_0.3.34-1.dsc
 5ca2227655ebf1ab2e252cee3eede219c758336394288ef301b93264b9411304 6707964 
gegl_0.3.34.orig.tar.bz2
 b547e353f81bd2d387c54030b65576583628aa6cfdbb68c28d7e280634c28392 19332 
gegl_0.3.34-1.debian.tar.xz
 06f0a5aa141dee77c2665b1cbee4ee4734c93e74365a7e7c6bc09b2005ab3ec1 15146 
gegl_0.3.34-1_source.buildinfo
Files:
 212977f120a32c7d783b834a1dd82f4e 2754 devel optional gegl_0.3.34-1.dsc
 e6758d2526c27dd3a34d3470aa844112 6707964 devel optional 
gegl_0.3.34.orig.tar.bz2
 5d7cf8d785fa5bcd931efa51dbfb3ddc 19332 devel optional 
gegl_0.3.34-1.debian.tar.xz
 b4021099859f9b68b55b313e70a6b3d6 15146 devel optional 
gegl_0.3.34-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAlrWlokACgkQ5mx3Wuv+
bH2YNBAAyMIt5UaDt0pka0kWwxjv5N5/FgQLcRXYBGXYn2397cbCvqOY06e6pBLN
vthy0FLQgl1jmOjJLBlJNhxrhz1/k5cZ9Eh6Qn5JSk9Fal/FT0BHBzOEHENdvy1F
SedrV3QnoS1mhcSGLTfI3F3LHoz4mY+ym8XK4jgncpdGIJe3Khv8WeNTqdFXyPrb
ZP+NMvP6ncNbLzRYfcgmVxB31IFnR8stv88+S1/0pRP7f7YTN1yJIrY5xvkpYxrI
6iJZrgkPPnDQ+YW/CqTWq1ITx+vgBEKTD4mUu6PpGMibSLmG3I9RBIoiyXoxz8qZ
Y0MyfdaJKyS/ca4RNFLGKeIDRuZqOyU4Y+G5qOsj8pXvr5bQMol76B2fWTm+17ZT
LSzCMGD9wREYLZMrPR8sPh1MBGEzSNmwlcilTsTYG577tw8Kc8v81fNKjk9C11uM
7xrCWBvlSlGDto1NxHlLi0S/rPggt+n0tue0GB/RS9YE36Oz0LKO25tvQrfYb5Yt
u5wt0PUIiEoq62sjX4jU5Ylbbf9Rz5cdIQjb5akzjmx/sJpE46nFU3rex0TQUzyO
qVvRc6zTnb3y8BK/mB+uSwbBNMR5RBKiV7YnXLaV2dtQrjR+7bZaiO/PA/kKzQYC
DPoy7VBbeJIzWLgk4KfY2JK7+zxW5/rwxKDWiirHuyCpWUeRgSI=
=foKI
-END PGP SIGNATURE End Message ---

Bug#853502: marked as done (libpam-chroot: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Wed, 18 Apr 2018 01:20:09 +
with message-id 
and subject line Bug#853502: fixed in libpam-chroot 0.9-4.3
has caused the Debian Bug report #853502,
regarding libpam-chroot: 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.)


-- 
853502: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853502
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libpam-chroot
Version: 0.9-4.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/libpam-chroot_0.9-4.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

[...]
dpkg-buildpackage: info: source package libpam-chroot
dpkg-buildpackage: info: source version 0.9-4.2
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by gregor herrmann 
 dpkg-source --before-build libpam-chroot-0.9
dpkg-buildpackage: info: host architecture amd64
 fakeroot debian/rules clean
dh_testdir
dh_testroot
rm -f build-stamp 
/usr/bin/make clean
make[1]: Entering directory '/<>'
rm -f *.o pam_chroot.so
make[1]: Leaving directory '/<>'
dh_clean
dh_clean: Compatibility levels before 9 are deprecated (level 5 in use)
 dpkg-source -b libpam-chroot-0.9
dpkg-source: warning: no source format specified in debian/source/format, see 
dpkg-source(1)
dpkg-source: info: using source format '1.0'
dpkg-source: info: building libpam-chroot using existing 
libpam-chroot_0.9.orig.tar.gz
dpkg-source: info: building libpam-chroot in libpam-chroot_0.9-4.2.diff.gz
dpkg-source: warning: the diff modifies the following upstream files: 
 Makefile
 TROUBLESHOOTING
 chroot.conf
 example/README.example
 example/chroot.conf
 example/chrooted-directory-tree.txt
 example/setup-chrootdir-rsync.sh
 example/setup-chrootdir-shell.sh
 example/setup-chrootdir-template.sh
 pam_chroot.c
dpkg-source: info: use the '3.0 (quilt)' format to have separate and documented 
changes to upstream files, see dpkg-source(1)
dpkg-source: info: building libpam-chroot in libpam-chroot_0.9-4.2.dsc
 debian/rules build
dh_testdir
/usr/bin/make
make[1]: Entering directory '/<>'
gcc -fPIC -O2 -Wall -Werror -pedantic -I.  -c -o pam_chroot.o pam_chroot.c
pam_chroot.c: In function 'pam_sm_open_session':
pam_chroot.c:873:18: error: '*' in boolean context, suggest '&&' instead 
[-Werror=int-in-bool-context]
if(opts.flags * _PAM_OPTS_DEBUG) {
  ^
cc1: all warnings being treated as errors
: recipe for target 'pam_chroot.o' failed
make[1]: *** [pam_chroot.o] Error 1
make[1]: Leaving directory '/<>'
debian/rules:16: recipe for target 'build-stamp' failed
make: *** [build-stamp] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
--- End Message ---
--- Begin Message ---
Source: libpam-chroot
Source-Version: 0.9-4.3

We believe that the bug you reported is fixed in the latest version of
libpam-chroot, 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 853...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Adam Borowski  (supplier of updated libpam-chroot package)

(This message was generated automatically at their request; if you
believe that there is a problem with 

Bug#886968: btrfs-progs-udeb: depends on non-udeb: libzstd1

[Cyril Brulebois]

Hi,

Dimitri John Ledkov  (2018-04-17):
> First, I apologize for not responding to this email earlier, as I have
> missed it in my mailbox.

It's a mail from hours ago, so there's no apology needed.

> Secondly, my work has been blocked by this NEW processing too for
> btrfs-progs. I'm not aware as to which Helmut's work was blocked,
> could you please elaborate what Helmut is blocked on? And/or how can
> libzstd/me help to unblock Helmut? -> is that about patches for
> crossbuilding that are part of

[sentenced cut in the middle but] Yes, Helmut works quite a lot on
crossbuilding and commits sitting in git master looked like what he was
alluding to.

> Now to respond to your main inquiry. I find the tone of above message
> unacceptable. It reads accusational to me, rather than inquisitive.
> 
> It would have been much better to state:
> "I notice that a call to dh_makeshlibs does not pass the -V flag as it
> is custom for many libraries. Why have you not specified a minimum
> required version in this case?"

I suppose that's a fair way to word it. But I did mean to point out that
packages having an impact on the installer should be reviewed by the
installer team, at least for their initial addition; as I tried to make
people aware a few times already (dda@, talks, replies to threads where
udeb additions were mentioned, etc.); since that simple and natural
process wasn't followed here, I did point that out.

> It also feels like you (or others who were made aware of this lack of
> -V) possibly wanted to make this a bug report, and follow-on out of
> band events made it seem like it was felt that it is RC buggy and
> shouldn't clear NEW and/or migrate to testing if passed NEW. In that
> case  a new bug report should have been opened, with above request at
> an RC priority.

I didn't comment on the fact it should get accepted or rejected from
NEW. People pointed me to the udeb addition that probably get some input
from me, so I've briefly looked at it and spotted that issue.

> However, it is good to point out at this time, that udeb version of
> libraries do not currently ship or use symbols files at all to
> generate dependencies.
> But also note that since libzstd1-udeb is a brand new package, any
> version of thereof would correctly and strictly satisfy any udeb
> package that gains a dependency on it. There are no linking or
> dependency bugs in above libzstd1, nor udeb edition of the binary
> packages.

I'm not sure why stashing a -V there once and for all to be future-proof
wouldn't be adequate or desireable. People can argue all they like about
whether the package is RC buggy in this specific revision, but it seems
rather pointless, I really do care about mid/long-term maintenance. I
have enough on my plate to not want to monitor such packages closely,
and open a specific bug report in their next revision…

> This is no different to some other library udebs, e.g. liblzo2-2-udeb

That's another perfect example why udeb additions should get reviewed:
we would have noticed another buggy package, and its bugginess might not
have been copied over to another package.

> Personally, I find it odd to have minimum -V arg version dependencies
> for udebs only, when symbols are present for the deb edition of the
> library. For example, btrfs-progs depends on libc6 (>= 2.8), yet
> btrfs-progs-udeb depends on libc6-udeb (>= 2.27). This causes an
> immense amount of pain, when rebuilding packages locally, mixing &
> matching packages when debugging issues in d-i, and does not at all
> correctly generate private dependencies for udebs that use e.g.
> @GLIBC_PRIVATE and thus require libc6-udeb (>> 2.27), libc6-udeb (<<
> 2.28) style dependency instead. I'm not sure where/how .symbols should
> be used or shipped, to start generate genuinely correct version
> dependencies for udebs across the board. Debhelper? Dpkg?

I have done my share part of performing local builds and various
combinations of udebs, and I never experienced this “immense amount of
pain”.

Are you volunteering to introduce separate symbols support for udebs to
all the required components and to maintain it over time?

> Based on all of the above, I believe libzstd1, and libzstd1-udeb are
> both policy complaint as previously uploaded.

I like the typo.

> If you are still concerned about minimum version dependencies which
> are generated by packages that build/link/gain dependency on libzstd1
> and/or libzstd1-udeb, I welcome you, ftp masters, or anybody else to
> open a new (or clone this) bug report against libzstd for
> consideration. I also welcome references from the Debian Policy to
> educate myself further about library dependencies, and if and how,
> this package is not policy complaint and pointers on how to best fix
> it.

I'm not sure what the issue is with talking to the debian installer team
when you're touching udeb packages and trusting their assessment?

If someone wants to drive an effort to make -V a must for 

Bug#893269: marked as done (libproxool-java FTBFS with openjdk-9)

[Debian Bug Tracking System]

Your message dated Tue, 17 Apr 2018 22:05:15 +
with message-id 
and subject line Bug#893269: fixed in libproxool-java 0.9.1-10
has caused the Debian Bug report #893269,
regarding libproxool-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.)


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

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

...
test:
 [echo] Running tests, this can take a few minutes.
 [java] 17 Mar 2018 04:28:38,291 [ERROR] {GlobalTest.java:98} 
org.logicalcobwebs.proxool.GlobalTest - Problem while loading test configuration
 [java] java.lang.NullPointerException: inStream parameter is null
 [java] at java.base/java.util.Objects.requireNonNull(Objects.java:246)
 [java] at java.base/java.util.Properties.load(Properties.java:365)
 [java] at 
org.logicalcobwebs.proxool.GlobalTest.initTestConstants(GlobalTest.java:94)
 [java] at 
org.logicalcobwebs.proxool.GlobalTest.initTestConstants(GlobalTest.java:79)
 [java] at 
org.logicalcobwebs.proxool.GlobalTest.globalSetup(GlobalTest.java:65)
 [java] at 
org.logicalcobwebs.proxool.GlobalTest$1.setUp(GlobalTest.java:150)
 [java] at junit.extensions.TestSetup$1.protect(TestSetup.java:20)
 [java] at junit.framework.TestResult.runProtected(TestResult.java:124)
 [java] at junit.extensions.TestSetup.run(TestSetup.java:25)
 [java] at junit.textui.TestRunner.doRun(TestRunner.java:121)
 [java] at junit.textui.TestRunner.start(TestRunner.java:185)
 [java] at junit.textui.TestRunner.main(TestRunner.java:143)
 [java] E
 [java] Time: 2.36
 [java] There was 1 error:
 [java] 1) 
junit.framework.testsu...@2b6856ddjava.lang.IllegalArgumentException: Couldn't 
load resources from /org/logicalcobwebs/proxool/testconfig-hsqldb.properties
 [java] at 
org.logicalcobwebs.proxool.GlobalTest.initTestConstants(GlobalTest.java:99)
 [java] at 
org.logicalcobwebs.proxool.GlobalTest.initTestConstants(GlobalTest.java:79)
 [java] at 
org.logicalcobwebs.proxool.GlobalTest.globalSetup(GlobalTest.java:65)
 [java] at 
org.logicalcobwebs.proxool.GlobalTest$1.setUp(GlobalTest.java:150)
 [java] at junit.extensions.TestSetup$1.protect(TestSetup.java:20)
 [java] at junit.extensions.TestSetup.run(TestSetup.java:25)
 [java] Caused by: java.lang.NullPointerException: inStream parameter is 
null
 [java] at java.base/java.util.Objects.requireNonNull(Objects.java:246)
 [java] at java.base/java.util.Properties.load(Properties.java:365)
 [java] at 
org.logicalcobwebs.proxool.GlobalTest.initTestConstants(GlobalTest.java:94)
 [java] ... 9 more
 [java] 
 [java] FAILURES!!!
 [java] Tests run: 0,  Failures: 0,  Errors: 1
 [java] 

BUILD FAILED
/build/1st/libproxool-java-0.9.1/debian/build.xml:49: Java returned: 1

Total time: 35 seconds
make: *** [/usr/share/cdbs/1/class/ant.mk:56: debian/stamp-ant-check] Error 1
--- End Message ---
--- Begin Message ---
Source: libproxool-java
Source-Version: 0.9.1-10

We believe that the bug you reported is fixed in the latest version of
libproxool-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.
Emmanuel Bourg  (supplier of updated libproxool-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: SHA512

Format: 1.8
Date: Tue, 17 Apr 2018 23:39:07 +0200
Source: libproxool-java
Binary: libproxool-java
Architecture: source
Version: 0.9.1-10
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 libproxool-java - Java JDBC connection pool
Closes: 893269
Changes:
 libproxool-java (0.9.1-10) unstable; urgency=medium
 .
   * 

Bug#886968: btrfs-progs-udeb: depends on non-udeb: libzstd1

[Dimitri John Ledkov]

On 17 April 2018 at 19:01, Cyril Brulebois  wrote:
> Dimitri John Ledkov  (2018-01-15):
>> On 15 January 2018 at 00:27, Cyril Brulebois  wrote:
>> > Hi,
>> >
>> > Cyril Brulebois  (2018-01-12):
>> >> Your package is no longer installable (along with its rev-dep
>> >> partman-btrfs) because it now depends on libzstd1, which isn't
>> >> a udeb.
>> >
>> > It seems zstd is only an option for btrfs-progs, and I've just confirmed
>> > that setting --disable-zstd on the dh_auto_configure line lets btrfs-progs
>> > build just fine, without the libzstd1 dependency. As far as I can tell,
>> > there's no absolute need for this feature in d-i, and we could consider
>> > building the udeb without zstd support, instead of requesting the addition
>> > of a libzstd1-udeb. What do you think?
>> >
>>
>> That's an oversight on my part. From the recovery point of view, it
>> would be desired to have zstd compression support built-into
>> btrfs-progs-udeb such that one can use d-i recovery mode to
>> backup/restore btrfs filesystems with zstd compression.
>
> Your unreviewed addition of udeb as seen in NEW (currently holding back
> Helmut's work as noticed on #debian-ftp) is broken. It's missing a
> version.
>
> Repeating the same request and piece of advice (since 2012 or so):
> please get udeb-related things reviewed by debian-boot@/me?
>
> Thanks already.

First, I apologize for not responding to this email earlier, as I have
missed it in my mailbox.

Secondly, my work has been blocked by this NEW processing too for
btrfs-progs. I'm not aware as to which Helmut's work was blocked,
could you please elaborate what Helmut is blocked on? And/or how can
libzstd/me help to unblock Helmut? -> is that about patches for
crossbuilding that are part of

Now to respond to your main inquiry. I find the tone of above message
unacceptable. It reads accusational to me, rather than inquisitive.

It would have been much better to state:
"I notice that a call to dh_makeshlibs does not pass the -V flag as it
is custom for many libraries. Why have you not specified a minimum
required version in this case?"

It also feels like you (or others who were made aware of this lack of
-V) possibly wanted to make this a bug report, and follow-on out of
band events made it seem like it was felt that it is RC buggy and
shouldn't clear NEW and/or migrate to testing if passed NEW. In that
case  a new bug report should have been opened, with above request at
an RC priority.

I hope above is an adequate description, of the technical question you
are alluding to.

The proposed update that got rejected from NEW had
```
override_dh_makeshlibs:
dh_makeshlibs -plibzstd1 --add-udeb=libzstd1-udeb
```
(I hope this is enough context from said upload, for more details see
tree at 
https://salsa.debian.org/med-team/libzstd/tree/50c4849ef0ea5d79d7d5f84fd0a46b6404a413eb)

Note, that libzstd1 provides a symbols file, therefore packages that
link against it, normally get the correct minimum version dependency
based on the symbols file.
Therefore lack of -V flag is irrelevant for the actual dependencies
generated on packages that link/depend on libzstd1.

However, it is good to point out at this time, that udeb version of
libraries do not currently ship or use symbols files at all to
generate dependencies.
But also note that since libzstd1-udeb is a brand new package, any
version of thereof would correctly and strictly satisfy any udeb
package that gains a dependency on it. There are no linking or
dependency bugs in above libzstd1, nor udeb edition of the binary
packages.

This is no different to some other library udebs, e.g. liblzo2-2-udeb

Personally, I find it odd to have minimum -V arg version dependencies
for udebs only, when symbols are present for the deb edition of the
library. For example, btrfs-progs depends on libc6 (>= 2.8), yet
btrfs-progs-udeb depends on libc6-udeb (>= 2.27). This causes an
immense amount of pain, when rebuilding packages locally, mixing &
matching packages when debugging issues in d-i, and does not at all
correctly generate private dependencies for udebs that use e.g.
@GLIBC_PRIVATE and thus require libc6-udeb (>> 2.27), libc6-udeb (<<
2.28) style dependency instead. I'm not sure where/how .symbols should
be used or shipped, to start generate genuinely correct version
dependencies for udebs across the board. Debhelper? Dpkg?

Based on all of the above, I believe libzstd1, and libzstd1-udeb are
both policy complaint as previously uploaded.

If you are still concerned about minimum version dependencies which
are generated by packages that build/link/gain dependency on libzstd1
and/or libzstd1-udeb, I welcome you, ftp masters, or anybody else to
open a new (or clone this) bug report against libzstd for
consideration. I also welcome references from the Debian Policy to
educate myself further about library dependencies, and if and how,
this package is not policy complaint and 

Processed: Pending fixes for bugs in the libproxool-java package

[Debian Bug Tracking System]

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

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

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

Bug#893269: Pending fixes for bugs in the libproxool-java package

[pkg-java-maintainers]

tag 893269 + pending
thanks

Some bugs in the libproxool-java package are closed in revision
af1201b304707af8f4e6c8e31379d8a66159329b in branch 'master' by
Emmanuel Bourg

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

Commit message:

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

Bug#893770: libgnomecanvas will be adopted

[Gert Wollny]

Control: severity -1 important 

In light of #895249 I downgrade the bug severity. Autoremove will still
happen since src:libgnomecanvas still has a few RC bugs.

Best,
Gert

Processed: libgnomecanvas will be adopted

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #893770 [src:amide] amide: Don't depend on libgnomecanvas
Severity set to 'important' from 'serious'

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

Bug#893240: marked as done (libhibernate3-java FTBFS with openjdk-9)

[Debian Bug Tracking System]

Your message dated Tue, 17 Apr 2018 21:37:14 +
with message-id 
and subject line Bug#893240: fixed in libhibernate3-java 3.6.10.Final-9
has caused the Debian Bug report #893240,
regarding libhibernate3-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.)


-- 
893240: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893240
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libhibernate3-java
Version: 3.6.10.Final-8
Severity: serious

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

...
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:aggregate (default-cli) on 
project hibernate: An error has occurred in Javadoc report generation: 
[ERROR] Exit code: 1 - 
/build/1st/libhibernate3-java-3.6.10.Final/project/hibernate-core/src/main/java/org/hibernate/bytecode/cglib/AccessOptimizerAdapter.java:38:
 warning - Tag @link: reference not found: ReflectionOptimizer#AccessOptimizer
[ERROR] 
/build/1st/libhibernate3-java-3.6.10.Final/project/hibernate-core/src/main/java/org/hibernate/bytecode/javassist/AccessOptimizerAdapter.java:33:
 warning - Tag @link: reference not found: ReflectionOptimizer#AccessOptimizer
[ERROR] 
/build/1st/libhibernate3-java-3.6.10.Final/project/hibernate-core/src/main/java/org/hibernate/bytecode/javassist/InstantiationOptimizerAdapter.java:33:
 warning - Tag @link: reference not found: 
ReflectionOptimizer#InstantiationOptimizer
[ERROR] 
/build/1st/libhibernate3-java-3.6.10.Final/project/hibernate-core/src/main/java/org/hibernate/cache/CacheConcurrencyStrategy.java:46:
 warning - invalid usage of tag >
[ERROR] 
/build/1st/libhibernate3-java-3.6.10.Final/project/hibernate-core/src/main/java/org/hibernate/cache/CacheConcurrencyStrategy.java:46:
 warning - invalid usage of tag >
[ERROR] 
/build/1st/libhibernate3-java-3.6.10.Final/project/hibernate-core/src/main/java/org/hibernate/cache/CacheConcurrencyStrategy.java:47:
 warning - invalid usage of tag >
[ERROR] 
/build/1st/libhibernate3-java-3.6.10.Final/project/hibernate-core/src/main/java/org/hibernate/cache/CacheConcurrencyStrategy.java:47:
 warning - invalid usage of tag >
[ERROR] 
/build/1st/libhibernate3-java-3.6.10.Final/project/hibernate-core/src/main/java/org/hibernate/cache/CacheConcurrencyStrategy.java:48:
 warning - invalid usage of tag >
[ERROR] 
/build/1st/libhibernate3-java-3.6.10.Final/project/hibernate-core/src/main/java/org/hibernate/cache/CacheConcurrencyStrategy.java:53:
 warning - invalid usage of tag >
[ERROR] 
/build/1st/libhibernate3-java-3.6.10.Final/project/hibernate-core/src/main/java/org/hibernate/cache/CacheConcurrencyStrategy.java:53:
 warning - invalid usage of tag >
[ERROR] 
/build/1st/libhibernate3-java-3.6.10.Final/project/hibernate-core/src/main/java/org/hibernate/cache/CacheConcurrencyStrategy.java:56:
 warning - invalid usage of tag >
[ERROR] 
/build/1st/libhibernate3-java-3.6.10.Final/project/hibernate-ehcache/src/main/java/org/hibernate/cache/EhCache.java:39:
 warning - Tag @link: reference not found: net.sf.ehcache.store.DiskStore
[ERROR] 
/build/1st/libhibernate3-java-3.6.10.Final/project/hibernate-ehcache/src/main/java/org/hibernate/cache/EhCache.java:40:
 warning - Tag @link: reference not found: net.sf.ehcache.store.DiskStore
[ERROR] 
/build/1st/libhibernate3-java-3.6.10.Final/project/hibernate-ehcache/src/main/java/org/hibernate/cache/SingletonEhCacheProvider.java:60:
 warning - invalid usage of tag <
[ERROR] 
/build/1st/libhibernate3-java-3.6.10.Final/project/hibernate-core/src/main/java/org/hibernate/cache/access/CollectionRegionAccessStrategy.java:34:
 warning - invalid usage of tag >
[ERROR] 
/build/1st/libhibernate3-java-3.6.10.Final/project/hibernate-core/src/main/java/org/hibernate/cache/access/CollectionRegionAccessStrategy.java:34:
 warning - invalid usage of tag >
[ERROR] 
/build/1st/libhibernate3-java-3.6.10.Final/project/hibernate-core/src/main/java/org/hibernate/cache/access/CollectionRegionAccessStrategy.java:38:
 warning - invalid usage of tag >
[ERROR] 
/build/1st/libhibernate3-java-3.6.10.Final/project/hibernate-core/src/main/java/org/hibernate/cache/access/CollectionRegionAccessStrategy.java:38:
 warning - invalid usage of tag >
[ERROR] 
/build/1st/libhibernate3-java-3.6.10.Final/project/hibernate-core/src/main/java/org/hibernate/cache/access/EntityRegionAccessStrategy.java:33:
 warning - invalid usage of tag >
[ERROR] 

Bug#893240: Pending fixes for bugs in the libhibernate3-java package

[pkg-java-maintainers]

tag 893240 + pending
thanks

Some bugs in the libhibernate3-java package are closed in revision
c9efed7050bc7b39305e25177a176694ede8a29e in branch 'master' by
Emmanuel Bourg

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

Commit message:

Removed the -java-doc package to work around the build failure with Java 9 
(Closes: #893240)

Processed: Pending fixes for bugs in the libhibernate3-java package

[Debian Bug Tracking System]

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

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

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

Bug#858938: kopete: Please migrate to openssl1.1 in buster

[Pino Toscano]

In data martedì 17 aprile 2018 20:46:24 CEST, Emilio Pozuelo Monfort ha scritto:
> ¡Hola Lisandro!
> 
> On 25/02/18 17:40, Lisandro Damián Nicanor Pérez Meyer wrote:
> > Hi Emilio!
> > 
> > El 25 feb. 2018 7:00 a.m., "Emilio Pozuelo Monfort" 
> > escribió:
> > 
> > Hi,
> > 
> > On Thu, 12 Oct 2017 23:44:27 +0200 Sebastian Andrzej Siewior
> >  wrote:
> >> this is a remainder about the openssl transition [0]. We really want to
> >> remove libssl1.0-dev from unstable for Buster. I will raise the severity
> >> of this bug to serious in a month. Please react before that happens.
> > It looks like kopete only wants openssl for jingle support in XMPP. Can you
> > temporarily disable that, and forward this bug upstream so they add support
> > for
> > openssl 1.1?
> > 
> > 
> > I haven't checked, but maybe it depends on qt itself. If that's the case
> > then waiting upon qt 5.10 might be the best thing here. We are not that far
> > from asking a transition for it.
> > 
> > Of course If that's not the case then it's a possibility.
> 
> Now that we have Qt 5.10 in sid, can you check if kopete can be built with
> OpenSSL 1.1? Otherwise, disabling jingle could solve this for the time being.

The version of openssl used to build Qt is irrelevant for the jingle
code that uses openssl directly; nobody did anything about that, so the
status is the same as before.

If the openssl maintainers want to get rid of openssl 1.0, why don't
they *cooperate* with *upstream* communities on the migration to the
newer version of openssl? That would certainly help, and surely way
more than useless "please migrate, ktnxbye" nagging.

-- 
Pino Toscano

signature.asc
Description: This is a digitally signed message part.

Bug#895952: FTBFS: incompatible with terminal-progress-bar 0.2

[Clint Adams]

Source: haskell-bytestring-progress
Version: 1.0.9-1
Severity: serious
Forwarded: https://github.com/acw/bytestring-progress/issues/9

.

Bug#858938: kopete: Please migrate to openssl1.1 in buster

[Lisandro Damián Nicanor Pérez Meyer]

Hi Emilio, Pino, Maxy!

I'm CCing Pboth Pino and Maxy because they are the ones following the
KDE parts of the team (I normally do just Qt stuff).


On 17 April 2018 at 15:46, Emilio Pozuelo Monfort  wrote:
> ¡Hola Lisandro!
>
[snip]

> Now that we have Qt 5.10 in sid, can you check if kopete can be built with
> OpenSSL 1.1? Otherwise, disabling jingle could solve this for the time being.

Kopete using kf5/Qt5 is in experimental, but I don't know it's status.
Kopete in unstable/testing is still using Qt4.

Maybe Pino and/or Maxy can help here.

Cheers!

-- 
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/

Bug#828451: netty fix released, netty-tcnative patch accepted

[Emilio Pozuelo Monfort]

On Wed, 24 Jan 2018 11:07:19 + deb...@fau.xxx wrote:
> Upstream have accepted both patches. netty 4.1.20 has been released,
> which will run against a patched netty-tcnative. There hasn't been a
> netty-tcnative release.

There's a new netty-tcnative release, 2.0.8. Is that incompatible with the
current version of netty, or why can't we update to that? Sorry, I'm not
familiar with netty, just looking at this as I'd like to get rid of openssl1.0
for buster.

Emilio

Bug#858938: kopete: Please migrate to openssl1.1 in buster

[Emilio Pozuelo Monfort]

¡Hola Lisandro!

On 25/02/18 17:40, Lisandro Damián Nicanor Pérez Meyer wrote:
> Hi Emilio!
> 
> El 25 feb. 2018 7:00 a.m., "Emilio Pozuelo Monfort" 
> escribió:
> 
> Hi,
> 
> On Thu, 12 Oct 2017 23:44:27 +0200 Sebastian Andrzej Siewior
>  wrote:
>> this is a remainder about the openssl transition [0]. We really want to
>> remove libssl1.0-dev from unstable for Buster. I will raise the severity
>> of this bug to serious in a month. Please react before that happens.
> It looks like kopete only wants openssl for jingle support in XMPP. Can you
> temporarily disable that, and forward this bug upstream so they add support
> for
> openssl 1.1?
> 
> 
> I haven't checked, but maybe it depends on qt itself. If that's the case
> then waiting upon qt 5.10 might be the best thing here. We are not that far
> from asking a transition for it.
> 
> Of course If that's not the case then it's a possibility.

Now that we have Qt 5.10 in sid, can you check if kopete can be built with
OpenSSL 1.1? Otherwise, disabling jingle could solve this for the time being.

Thanks,
Emilio

Bug#884703: marked as done (osmo-ggsn: fails to upgrade from 'sid' - trying to overwrite /usr/bin/sgsnemu)

[Debian Bug Tracking System]

Your message dated Tue, 17 Apr 2018 18:04:54 +
with message-id 
and subject line Bug#884703: fixed in osmo-ggsn 1.1.0-2
has caused the Debian Bug report #884703,
regarding osmo-ggsn: fails to upgrade from 'sid' - trying to overwrite 
/usr/bin/sgsnemu
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.)


-- 
884703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884703
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: osmo-ggsn
Version: 1.1.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package osmo-ggsn.
  Preparing to unpack .../8-osmo-ggsn_1.1.0-1_amd64.deb ...
  Unpacking osmo-ggsn (1.1.0-1) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-IS2ifk/8-osmo-ggsn_1.1.0-1_amd64.deb (--unpack):
   trying to overwrite '/usr/bin/sgsnemu', which is also in package openggsn 
0.92-2
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-IS2ifk/8-osmo-ggsn_1.1.0-1_amd64.deb


cheers,

Andreas


openggsn=0.92-2_osmo-ggsn=1.1.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: osmo-ggsn
Source-Version: 1.1.0-2

We believe that the bug you reported is fixed in the latest version of
osmo-ggsn, 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 884...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thorsten Alteholz  (supplier of updated osmo-ggsn 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: Tue, 17 Apr 2018 18:47:14 +0100
Source: osmo-ggsn
Binary: osmo-ggsn libgtp2 libgtp-dev
Architecture: source amd64
Version: 1.1.0-2
Distribution: sid
Urgency: medium
Maintainer: Debian Mobcom Maintainers 

Changed-By: Thorsten Alteholz 
Description:
 libgtp-dev - Development files for libgtp
 libgtp2- library implementing the GTP protocol between SGSN and GGSN
 osmo-ggsn  - Osmocom Gateway GPRS Support Node (GGSN)
Closes: 874492 884703
Changes:
 osmo-ggsn (1.1.0-2) unstable; urgency=medium
 .
   * move to unstable
   * debian/control: move to debian-mobcom maintainer
   * debian/control: add salsa URLs
   * debian/control: use dh11
   * debian/control: bump standard to 4.1.4 (no changes)
   * debian/control: declare Breaks:/Replaces: to openggsn
 (Closes: #884703)
   * debian/rules: don't run tests on BE CPUs
   * package was renamed upstream (Closes: #874492)
 (osmo-ggsn is the new one, openggsn was the old package name)
Checksums-Sha1:
 a55776fbf03efe3fdd85afa11a060ebb52a15121 2274 osmo-ggsn_1.1.0-2.dsc
 91333a7b630452bbd6cbacc4101d3334ca75e99f 144140 osmo-ggsn_1.1.0.orig.tar.xz
 0b4880a750dbe2864e1011ed026dec52d2aeed49 7044 osmo-ggsn_1.1.0-2.debian.tar.xz
 851657440ef391c601ed576451239b3d0d78d4bd 38564 libgtp-dev_1.1.0-2_amd64.deb
 62d8d0c674f3cee9d1c0ad0100bb8e670a9bcce9 55544 libgtp2-dbgsym_1.1.0-2_amd64.deb
 3ac4d4705c268bb46828ae7ccca006d5f731da8d 28364 libgtp2_1.1.0-2_amd64.deb
 aaba5679d391ace2cd7afb8458c3e45c8250b10d 147388 
osmo-ggsn-dbgsym_1.1.0-2_amd64.deb
 8ae381ea2fe6b4deb8a3bd87fcb779b2c7a13825 7640 osmo-ggsn_1.1.0-2_amd64.buildinfo
 5ff5109b9a89492984ad4e985774cb99f528a6e1 60944 osmo-ggsn_1.1.0-2_amd64.deb
Checksums-Sha256:
 fd8cf5bbdaeebb314c3d6bca70021ce1fb1b2ae7abcd4ce379f3bbce01570649 2274 
osmo-ggsn_1.1.0-2.dsc
 8ad1a383d602f793c02acad1c0b8eba82b3653ab85f08b0e4eda0e7d961584c2 144140 
osmo-ggsn_1.1.0.orig.tar.xz
 79a2b5f9d30aab88c882ce7dad9e5c530f35c788a963e9c4ba5755918a1ede19 7044 
osmo-ggsn_1.1.0-2.debian.tar.xz
 b9e956104b0823059c6b1351725867a4a060a6621dfc81dbd1c6ff26b8217871 38564 

Bug#886968: btrfs-progs-udeb: depends on non-udeb: libzstd1

[Cyril Brulebois]

Dimitri John Ledkov  (2018-01-15):
> On 15 January 2018 at 00:27, Cyril Brulebois  wrote:
> > Hi,
> >
> > Cyril Brulebois  (2018-01-12):
> >> Your package is no longer installable (along with its rev-dep
> >> partman-btrfs) because it now depends on libzstd1, which isn't
> >> a udeb.
> >
> > It seems zstd is only an option for btrfs-progs, and I've just confirmed
> > that setting --disable-zstd on the dh_auto_configure line lets btrfs-progs
> > build just fine, without the libzstd1 dependency. As far as I can tell,
> > there's no absolute need for this feature in d-i, and we could consider
> > building the udeb without zstd support, instead of requesting the addition
> > of a libzstd1-udeb. What do you think?
> >
> 
> That's an oversight on my part. From the recovery point of view, it
> would be desired to have zstd compression support built-into
> btrfs-progs-udeb such that one can use d-i recovery mode to
> backup/restore btrfs filesystems with zstd compression.

Your unreviewed addition of udeb as seen in NEW (currently holding back
Helmut's work as noticed on #debian-ftp) is broken. It's missing a
version.

Repeating the same request and piece of advice (since 2012 or so):
please get udeb-related things reviewed by debian-boot@/me?

Thanks already.


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


signature.asc
Description: PGP signature

Bug#866493: marked as done (weboob: depends on obsolete python-imaging (replace with python3-pil or python-pil))

[Debian Bug Tracking System]

Your message dated Tue, 17 Apr 2018 17:37:50 +
with message-id 
and subject line Bug#866493: fixed in weboob 1.3-1
has caused the Debian Bug report #866493,
regarding weboob: depends on obsolete python-imaging (replace with python3-pil 
or python-pil)
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.)


-- 
866493: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866493
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:weboob
Version: 1.2-1
Severity: important
Tags: sid buster
User: d...@debian.org
Usertags: imaging-pillow

One or more binary packages built from this source depends on or
recommends python-imaging, which is obsolete for some years now.
Please build the source using the python-pil package. If your
package doesn't need to be built with Python2, please consider using
Python3 and depend on python3-pil.

Planning to remove python-imaging for the buster release, so the
severity of this issues might be raised.
--- End Message ---
--- Begin Message ---
Source: weboob
Source-Version: 1.3-1

We believe that the bug you reported is fixed in the latest version of
weboob, 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 866...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Marc Dequènes (Duck)  (supplier of updated weboob 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: Wed, 18 Apr 2018 02:15:41 +0900
Source: weboob
Binary: python-weboob python-weboob-core weboob weboob-qt
Architecture: source all
Version: 1.3-1
Distribution: unstable
Urgency: medium
Maintainer: Romain Bignon 
Changed-By: Marc Dequènes (Duck) 
Description:
 python-weboob - Weboob, Web Out Of Browsers - library
 python-weboob-core - transitional dummy package
 weboob - CLI applications to interact with websites
 weboob-qt  - Qt applications to interact with websites
Closes: 866493 879211
Changes:
 weboob (1.3-1) unstable; urgency=medium
 .
   [ Marc Dequènes (Duck) ]
   * New Upstream Release (Closes: #879211).
   * Updated VCS URLs (Alioth->Salsa).
   * Added myself to uploaders.
   * Switch to compat level 11.
   * Install bash completion in the new directory.
   * Switch copyright format link to HTTPS.
   * Bump Standards-Version to 4.1.4.
   * Override false positive on python-script-but-no-python-dep.
   * Added missing dependencies/recommends (thanks ntome).
   * python-pil replaces python-imaging/pillow (Closes: #866493).
   * Removed recommends on python-clientform, integrated into python-
 mechanize now.
 .
   [ Stefano Zacchiroli ]
   * drop obsolete patch 0001-do-not-install-modules, integrated upstream
   * debian/*.install: ship new [q]galleroob applications
Checksums-Sha1:
 deef2501ce8a1189cdc51dda64533ed6b7a1f00f 2098 weboob_1.3-1.dsc
 3e358093789851a913078f1a96ff64f8f475fa21 2688899 weboob_1.3.orig.tar.gz
 7688128900b078fd9e652f8798b69bbe289355ed 17120 weboob_1.3-1.debian.tar.xz
 ab75c727d0834cd230417c34c0d8c119a44935e7 93956 python-weboob-core_1.3-1_all.deb
 7182d8e61e7a152e03eb2fd9d986e97b8e5d1ce9 261220 python-weboob_1.3-1_all.deb
 20e9300ca00cd4edfc36a7c5196b49817273b76b 263316 weboob-qt_1.3-1_all.deb
 1f954e42373fe3a804acf087b2467871af17db78 595204 weboob_1.3-1_all.deb
 cfc43f7972bce1ef0711637a75e241931ae4d2e9 10125 weboob_1.3-1_amd64.buildinfo
Checksums-Sha256:
 30842ec66b939d0db492252f030c8335b58be72984c38a5a900f8caab7fc8c8f 2098 
weboob_1.3-1.dsc
 c991785c889877c76f18d19e372ed4ae0c3f8b819fd1e8da296bd34b1381be54 2688899 
weboob_1.3.orig.tar.gz
 01dc3efbd34f4b77a5a883e0835c36f2621042b87b31dfb0211d43c99669f3db 17120 
weboob_1.3-1.debian.tar.xz
 9d0c26591165bd53713114811fe6cccd4930c9cd5301326f5a6ae7d76cb833bb 93956 
python-weboob-core_1.3-1_all.deb
 48c07d095d08240647914bd501a99c69e3f95106a37060dc3440255ce0404617 261220 
python-weboob_1.3-1_all.deb
 e3baae6ccf3c9a654e623853f951f16bd7b5c7ec5a212eb2bce0fb1ec28b1d5a 263316 
weboob-qt_1.3-1_all.deb
 b546f389897d6fc637aefef7ad5ad3ec919acb936cef76272fe058c1aa2490b6 595204 
weboob_1.3-1_all.deb
 

Bug#891740: marked as done (pyvo FTBFS: ModuleNotFoundError: No module named 'requests')

[Debian Bug Tracking System]

Your message dated Tue, 17 Apr 2018 16:41:08 +
with message-id 
and subject line Bug#891740: fixed in pyvo 0.6.1+dfsg-1.1
has caused the Debian Bug report #891740,
regarding pyvo FTBFS: ModuleNotFoundError: No module named 'requests'
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.)


-- 
891740: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891740
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyvo
Version: 0.6.1+dfsg-1
Severity: serious

Some recent change in unstable makes pyvo FTBFS:

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

...
==
ERROR: pyvo (unittest.loader._FailedTest)
--
ImportError: Failed to import test module: pyvo
Traceback (most recent call last):
  File "/usr/lib/python3.6/unittest/loader.py", line 462, in _find_test_path
package = self._get_module_from_name(name)
  File "/usr/lib/python3.6/unittest/loader.py", line 369, in 
_get_module_from_name
__import__(name)
  File 
"/build/1st/pyvo-0.6.1+dfsg/.pybuild/pythonX.Y_3.6/build/pyvo/__init__.py", 
line 41, in 
from . import registry
  File 
"/build/1st/pyvo-0.6.1+dfsg/.pybuild/pythonX.Y_3.6/build/pyvo/registry/__init__.py",
 line 7, in 
from . import regtap
  File 
"/build/1st/pyvo-0.6.1+dfsg/.pybuild/pythonX.Y_3.6/build/pyvo/registry/regtap.py",
 line 21, in 
from ..dal import scs, sia, ssa, sla, tap, query as dalq
  File 
"/build/1st/pyvo-0.6.1+dfsg/.pybuild/pythonX.Y_3.6/build/pyvo/dal/__init__.py", 
line 2, in 
from .sia import search as imagesearch
  File 
"/build/1st/pyvo-0.6.1+dfsg/.pybuild/pythonX.Y_3.6/build/pyvo/dal/sia.py", line 
39, in 
from .query import DALResults, DALQuery, DALService, Record, mime2extension
  File 
"/build/1st/pyvo-0.6.1+dfsg/.pybuild/pythonX.Y_3.6/build/pyvo/dal/query.py", 
line 35, in 
import requests
ModuleNotFoundError: No module named 'requests'


--
Ran 1 test in 0.001s

FAILED (errors=1)
E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: cd 
/build/1st/pyvo-0.6.1+dfsg/.pybuild/pythonX.Y_3.6/build; python3.6 -m unittest 
discover -v 
dh_auto_test: pybuild --test -i python{version} -p 3.6 returned exit code 13
make: *** [debian/rules:7: build] Error 25
--- End Message ---
--- Begin Message ---
Source: pyvo
Source-Version: 0.6.1+dfsg-1.1

We believe that the bug you reported is fixed in the latest version of
pyvo, 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 891...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ole Streicher  (supplier of updated pyvo 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: Thu, 12 Apr 2018 17:33:18 +0200
Source: pyvo
Binary: python-pyvo python3-pyvo
Architecture: source
Version: 0.6.1+dfsg-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Astronomy Maintainers 

Changed-By: Ole Streicher 
Description:
 python-pyvo - Python library for data services of the Virtual observatory (VO)
 python3-pyvo - Python 3 library for data services of the Virtual observatory 
(VO
Closes: 891740
Changes:
 pyvo (0.6.1+dfsg-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Build-depend on python3-requests (Closes: #891740)
   * Disable build time tests
Checksums-Sha1:
 550213b9dcd4fabff3446e495edbad8668200bda 2344 pyvo_0.6.1+dfsg-1.1.dsc
 5e7a3591cfd7dc34fd1f4e9f4d410aede1a055d4 5008 pyvo_0.6.1+dfsg-1.1.debian.tar.xz
Checksums-Sha256:
 9cc7a5f4fd1eefaebd63a1704c95b6e136fbb343397814265e35f960c65f9699 2344 
pyvo_0.6.1+dfsg-1.1.dsc
 a6577f5496cc02cce53bee9f55d688f2d697355f5f31a0a72acf313a7e8b21ea 5008 
pyvo_0.6.1+dfsg-1.1.debian.tar.xz
Files:
 12b89fd0524b6100b6b176b99cc9f7b0 2344 python optional pyvo_0.6.1+dfsg-1.1.dsc
 7e3d48492612cf34675100fefa663624 5008 python optional 

Bug#895889: [pkg-go] Bug#895889: golang-github-weaveworks-mesh: new version causes regression in prometheus-alertmanager

[Paul Gevers]

Hi Martín,

On 17-04-18 17:35, Martín Ferrari wrote:
> I did not notice the update of mesh would break the current alertmanager
> in testing.

Not in testing *yet* (that is the purpose of this bug), but it would
break it if allowed to migrate.

> I did the upload yesterday in preparation for a new upload
> of the alertmanager, so this FTBFS will be solved as soon as I am finished.

From the fundamental point of tracking dependencies and such,
golang-github-weaveworks-mesh needs an appropriate Breaks:
prometheus-alertmanager (< $the_next_version) or something along those
lines.

> Sadly, the golang ecosystem is very immature and has not yet learned
> about API stability or even releases...

Ack. (So from the practical point of view, I am not sure if the Breaks
is worth the effort, but I leave you to judge that).

Paul



signature.asc
Description: OpenPGP digital signature

Processed: affects 887924

[Debian Bug Tracking System]

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

> affects 887924 src:slurm-drmaa
Bug #887924 [src:slurm-llnl] slurm-drmaa FTBFS with slurm-llnl 17.11.2-1
Added indication that 887924 affects src:slurm-drmaa
> thanks
Stopping processing here.

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

Processed: reassign 887924 to src:slurm-llnl

[Debian Bug Tracking System]

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

> reassign 887924 src:slurm-llnl 17.11.2-1
Bug #887924 [slurm-llnl] slurm-drmaa FTBFS with slurm-llnl 17.11.2-1
Bug reassigned from package 'slurm-llnl' to 'src:slurm-llnl'.
Ignoring request to alter found versions of bug #887924 to the same values 
previously set
Ignoring request to alter fixed versions of bug #887924 to the same values 
previously set
Bug #887924 [src:slurm-llnl] slurm-drmaa FTBFS with slurm-llnl 17.11.2-1
Marked as found in versions slurm-llnl/17.11.2-1.
> thanks
Stopping processing here.

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

Bug#895889: [pkg-go] Bug#895889: golang-github-weaveworks-mesh: new version causes regression in prometheus-alertmanager

[Martín Ferrari]

Paul, Adrian,

On 17/04/18 11:23, Adrian Bunk wrote:
> On Tue, Apr 17, 2018 at 11:20:13AM +0200, Paul Gevers wrote:
>> ...
>> As the it seems that the same code is used to build the
>> prometheus-alertmanager package, I think this means that that now FTBFS
>> (haven't verified).
>> ...
> 
> prometheus-alertmanager does FTBFS now:
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/prometheus-alertmanager.html

I did not notice the update of mesh would break the current alertmanager
in testing. I did the upload yesterday in preparation for a new upload
of the alertmanager, so this FTBFS will be solved as soon as I am finished.

Sadly, the golang ecosystem is very immature and has not yet learned
about API stability or even releases...


-- 
Martín Ferrari (Tincho)

Bug#876571: marked as done (mpage is no longer available on Debian)

[Debian Bug Tracking System]

Your message dated Tue, 17 Apr 2018 15:13:56 +
with message-id 
and subject line Bug#876571: fixed in gjots2 2.4.1-5
has caused the Debian Bug report #876571,
regarding mpage is no longer available on Debian
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.)


-- 
876571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876571
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gjots2
Version: 2.4.1-2
Severity: important
Tags: newcomer

Dear maintainer,

Your package recommends mpage, removed from Debian on 2017-09-22 (see #876197).
Please, drop mpage from Recommends field.

Regards,

Eriberto
--- End Message ---
--- Begin Message ---
Source: gjots2
Source-Version: 2.4.1-5

We believe that the bug you reported is fixed in the latest version of
gjots2, 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 876...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Rolf Leggewie  (supplier of updated gjots2 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: Tue, 17 Apr 2018 22:36:57 +0800
Source: gjots2
Binary: gjots2
Architecture: source all
Version: 2.4.1-5
Distribution: unstable
Urgency: medium
Maintainer: Rolf Leggewie 
Changed-By: Rolf Leggewie 
Description:
 gjots2 - Simple jotter (outline processor) for X11/gtk-gnome
Closes: 876571
Changes:
 gjots2 (2.4.1-5) unstable; urgency=medium
 .
   * control:
 - use publicly accessible Vcs-Git URI
 - demote gv, mpage and python-gtksourceview2 to Suggests. Closes: #876571
Checksums-Sha1:
 b57ec2f28af23240655d532e6eb16ca727a9e791 1805 gjots2_2.4.1-5.dsc
 f589a9eb0c47ac6693159455565144e47ed923f7 6940 gjots2_2.4.1-5.debian.tar.xz
 d6b690b68a466d73d0d378d91c5724cd01b72343 154048 gjots2_2.4.1-5_all.deb
 a9e90f22effe56e8a642b4b03fe42df752d67c38 5822 gjots2_2.4.1-5_i386.buildinfo
Checksums-Sha256:
 75bc543c824c5bf3234059ed24d5b9133ac67d96aee53eb20fdc4bfd6aa9e661 1805 
gjots2_2.4.1-5.dsc
 c5001f74a89c4c9793cdaca363395d7553c578e6f5b17a5fb0b0cef677834854 6940 
gjots2_2.4.1-5.debian.tar.xz
 3983102a0175b0be4c87462861e4657c827864f445e245291df455f30dbe6f41 154048 
gjots2_2.4.1-5_all.deb
 644da2f7f954f66c72ec448e3358fef9d6d5dc5b0def521c06659d5fa10da5f7 5822 
gjots2_2.4.1-5_i386.buildinfo
Files:
 02fb180559a72dfd2005737bcc493f22 1805 gnome optional gjots2_2.4.1-5.dsc
 eb60b1c08ba7719c23b2a79b21f38cd5 6940 gnome optional 
gjots2_2.4.1-5.debian.tar.xz
 807105bddd1ecd71cddaa2a8cc0345b9 154048 gnome optional gjots2_2.4.1-5_all.deb
 c87d024e18c47e4daf9489b93f46966f 5822 gnome optional 
gjots2_2.4.1-5_i386.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEA4bPBUqBlI1tn6fqlIQryG5RHDEFAlrWCfsACgkQlIQryG5R
HDGoGA/8DYVWS0asZVy61/q78luy4VY8V8ND0KstEEYWnbRUw40f074Ui3z2djXB
f9bSaSib/UOgnFHdEKorzrxI3iam/rklyC1Lc0PIV2ktQ9/lTRNNbi4v3bRLDzXS
jKmZGSNFm+M+170wDS0zlcHrovbMzB6c/P3WikaNUiTR1pwKchdv+r6DXtcOmWgQ
cfHOrnMSaov2808j7nJWfdlgNnlptp/sI8e9MQV0zSAc7AbZqjt5kUI48rxheMir
on1UggPWccuZuohj29ATiyvGursQ4Ps+Qr+Ee3zkEnUviJm3jf9aYM1B8HFyDhU8
T55czWySfCi10INeQzFImE+Fjw1hFRFsdQn2DPPSk1hw5mwj++NTFKK3BBQ8qDVH
RMRYm/oODU2BrQnub7RhnSMAjONazkCMsQbUXNTPPhIvv7z1lWIw91g2sTjCo4+r
eWLr277lOaC6M54zIPdZRrn5frAZ1jX2uXDQu2HA/A0g9ph+qfO1apWMBUURgiQq
haMyO0+Uxm5eiKqNLXQAihE5XM+HGnLJRGbZ8z2fBacjMfjbCPuEeCJqqrQ5uGbT
+gT5QIqr1BRCgc7TUI3/34BZDFpzY5ASxnp2GBkCbhcG7goixob6AGvsN/eDBoF3
xagSW1GwP8hTAG4/FB1Oglp376xgNtxth9PQDV4qm/A8dOmyzLc=
=Kpxx
-END PGP SIGNATURE End Message ---

Processed: your mail

[Debian Bug Tracking System]

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

> tags 893039 + pending
Bug #893039 [libccnet0] libccnet0: contains a python module
Added tag(s) pending.
> tags 890907 + confirmed upstream
Bug #890907 [src:cjose] cjose FTBFS on big endian: test failure
Added tag(s) confirmed and upstream.
> tags 893040 + confirmed
Bug #893040 [libseafile0] libseafile0: contains a python module
Added tag(s) confirmed.
>
End of message, stopping processing here.

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

Bug#895923: ruby-pkg-config: FTBFS and Debci failure

[Adrian Bunk]

Source: ruby-pkg-config
Version: 1.2.9-1
Severity: serious

Some recent change in unstable makes ruby-pkg-config FTBFS and Debci fail:

https://ci.debian.net/packages/r/ruby-pkg-config/unstable/amd64/
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-pkg-config.html

...
┌──┐
│ Run tests for ruby2.5 from debian/ruby-tests.rb  │
└──┘

RUBYLIB=/build/1st/ruby-pkg-config-1.2.9/debian/ruby-pkg-config/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-pkg-config/usr/share/rubygems-integration/all:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 debian/ruby-tests.rb
Loaded suite debian/ruby-tests
Started
F
===
Failure: test_cflags(PkgConfigTest)
/build/1st/ruby-pkg-config-1.2.9/test/test_pkg_config.rb:122:in 
`assert_pkg_config'
/build/1st/ruby-pkg-config-1.2.9/test/test_pkg_config.rb:28:in `test_cflags'
 25:   end
 26: 
 27:   def test_cflags
  => 28: assert_pkg_config("cairo", ["--cflags"], @cairo.cflags)
 29: only_pkg_config_version(0, 29)
 30: assert_pkg_config("cairo-png", ["--cflags"], @cairo_png.cflags)
 31:   end
<"-I/usr/include/cairo -I/usr/include/glib-2.0 
-I/tmp/local/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/uuid 
-I/usr/include/freetype2 -I/usr/include/libpng16">(US-ASCII) expected but was
<"-I/usr/include/cairo -I/usr/include/glib-2.0 
-I/tmp/local/lib/glib-2.0/include -I/usr/include/pixman-1 
-I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/uuid">(UTF-8)

diff:
? -I/usr/include/cairo -I/usr/include/glib-2.0 
-I/tmp/local/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/uuid 
-I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/uuid
  
? Encoding: US -ASCII
?TF 8
===
F
===
Failure: test_cflags_only_I(PkgConfigTest)
/build/1st/ruby-pkg-config-1.2.9/test/test_pkg_config.rb:122:in 
`assert_pkg_config'
/build/1st/ruby-pkg-config-1.2.9/test/test_pkg_config.rb:34:in 
`test_cflags_only_I'
 31:   end
 32: 
 33:   def test_cflags_only_I
  => 34: assert_pkg_config("cairo", ["--cflags-only-I"], 
@cairo.cflags_only_I)
 35: only_pkg_config_version(0, 29)
 36: assert_pkg_config("cairo-png", ["--cflags-only-I"], 
@cairo_png.cflags_only_I)
 37:   end
<"-I/usr/include/cairo -I/usr/include/glib-2.0 
-I/tmp/local/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/uuid 
-I/usr/include/freetype2 -I/usr/include/libpng16">(US-ASCII) expected but was
<"-I/usr/include/cairo -I/usr/include/glib-2.0 
-I/tmp/local/lib/glib-2.0/include -I/usr/include/pixman-1 
-I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/uuid">(UTF-8)

diff:
? -I/usr/include/cairo -I/usr/include/glib-2.0 
-I/tmp/local/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/uuid 
-I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/uuid
  
? Encoding: US -ASCII
?TF 8
===
.

Finished in 0.686665821 seconds.
--
11 tests, 26 assertions, 2 failures, 0 errors, 0 pendings, 0 omissions, 0 
notifications
81.8182% passed
--
16.02 tests/s, 37.86 assertions/s
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install 
/build/1st/ruby-pkg-config-1.2.9/debian/ruby-pkg-config returned exit code 1
make: *** [debian/rules:15: binary] Error 1

Bug#893312: lombok FTBFS with openjdk-9

[Markus Koschany]

I've fixed the original errors in Javac.java but there are more later on
due to our friend OpenPain 9. I had no choice but to upgrade to a newer
lombok version. Now I'm stuck because ecj can't be found.

Markus



signature.asc
Description: OpenPGP digital signature

Processed: your mail

[Debian Bug Tracking System]

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

> reassign 887924  slurm-llnl
Bug #887924 [src:slurm-drmaa] slurm-drmaa FTBFS with slurm-llnl 17.11.2-1
Bug reassigned from package 'src:slurm-drmaa' to 'slurm-llnl'.
No longer marked as found in versions slurm-drmaa/1.0.7-1.
Ignoring request to alter fixed versions of bug #887924 to the same values 
previously set
>
End of message, stopping processing here.

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

Bug#895920: ecj: only a virtual package and not installable

[Markus Koschany]

Source: ecj
Version: 3.13.2-2
Severity: serious

while I was having some fun with lombok, I discovered that ecj is just
a virtual package and not installable. I don't think that's intended.

Markus

Bug#894289: marked as done (htsjdk FTBFS with openjdk-9)

[Debian Bug Tracking System]

Your message dated Tue, 17 Apr 2018 14:05:05 +
with message-id 
and subject line Bug#894289: fixed in htsjdk 2.14.3+dfsg-1
has caused the Debian Bug report #894289,
regarding htsjdk 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.)


-- 
894289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894289
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: htsjdk
Version: 2.8.1+dfsg-2
Severity: serious

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

...
/build/1st/htsjdk-2.8.1+dfsg/src/main/java/htsjdk/samtools/SAMSequenceDictionary.java:35:
 error: package javax.xml.bind.annotation is not visible
import javax.xml.bind.annotation.XmlElement;
 ^
  (package javax.xml.bind.annotation is declared in module java.xml.bind, which 
is not in the module graph)
/build/1st/htsjdk-2.8.1+dfsg/src/main/java/htsjdk/samtools/SAMSequenceDictionary.java:36:
 error: package javax.xml.bind.annotation is not visible
import javax.xml.bind.annotation.XmlRootElement;
 ^
  (package javax.xml.bind.annotation is declared in module java.xml.bind, which 
is not in the module graph)
/build/1st/htsjdk-2.8.1+dfsg/src/main/java/htsjdk/samtools/SAMSequenceDictionary.java:37:
 error: package javax.xml.bind.annotation is not visible
import javax.xml.bind.annotation.XmlTransient;
 ^
  (package javax.xml.bind.annotation is declared in module java.xml.bind, which 
is not in the module graph)
/build/1st/htsjdk-2.8.1+dfsg/src/main/java/htsjdk/samtools/SAMSequenceRecord.java:35:
 error: package javax.xml.bind.annotation is not visible
import javax.xml.bind.annotation.XmlAttribute;
 ^
  (package javax.xml.bind.annotation is declared in module java.xml.bind, which 
is not in the module graph)
/build/1st/htsjdk-2.8.1+dfsg/src/main/java/htsjdk/samtools/SAMSequenceRecord.java:36:
 error: package javax.xml.bind.annotation is not visible
import javax.xml.bind.annotation.XmlRootElement;
 ^
  (package javax.xml.bind.annotation is declared in module java.xml.bind, which 
is not in the module graph)
/build/1st/htsjdk-2.8.1+dfsg/src/main/java/htsjdk/samtools/SAMSequenceRecord.java:37:
 error: package javax.xml.bind.annotation is not visible
import javax.xml.bind.annotation.XmlValue;
 ^
  (package javax.xml.bind.annotation is declared in module java.xml.bind, which 
is not in the module graph)
/build/1st/htsjdk-2.8.1+dfsg/src/main/java/htsjdk/samtools/AbstractSAMHeaderRecord.java:31:
 error: package javax.xml.bind.annotation is not visible
import javax.xml.bind.annotation.XmlTransient;
 ^
  (package javax.xml.bind.annotation is declared in module java.xml.bind, which 
is not in the module graph)
7 errors
--- End Message ---
--- Begin Message ---
Source: htsjdk
Source-Version: 2.14.3+dfsg-1

We believe that the bug you reported is fixed in the latest version of
htsjdk, 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 894...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated htsjdk 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: Tue, 17 Apr 2018 15:14:40 +0200
Source: htsjdk
Binary: libhtsjdk-java libhtsjdk-java-doc
Architecture: source
Version: 2.14.3+dfsg-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 libhtsjdk-java - Java API for high-throughput sequencing data (HTS) formats
 libhtsjdk-java-doc - Documentation for the java HTSJDK library
Closes: 894289
Changes:
 htsjdk (2.14.3+dfsg-1) experimental; urgency=medium
 .
   [ Andreas Tille ]
   * New upstream version
 Closes: #894289
   * cme fix dpkg-control
   * Standards-Version: 4.1.4
   * Point Vcs-fields to salsa.d.o
   * Update d/copyright
   * d/rules: fix get-poms target
   * Use 2to3 to convert Python script to Python3
 .
   [ Olivier Sallou ]
   * 

Bug#886040: marked as done (sugar-session: Depends on gconf)

[Debian Bug Tracking System]

Your message dated Tue, 17 Apr 2018 13:35:53 +
with message-id 
and subject line Bug#886040: fixed in sugar 0.112-3
has caused the Debian Bug report #886040,
regarding sugar-session: Depends on gconf
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.)


-- 
886040: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886040
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sugar-session
Version: 0.112-1
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs gconf
Tags: sid buster

sugar-session depends and build-depends on gconf, but gconf will be
removed from Debian soon.

gconf's last release was about 5 years ago. It has been replaced by
gsettings (provided in Debian by source glib2.0 )

References
--
https://developer.gnome.org/gio/stable/ch34.html
https://developer.gnome.org/gio/stable/GSettings.html

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: sugar
Source-Version: 0.112-3

We believe that the bug you reported is fixed in the latest version of
sugar, 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 886...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Santiago Ruano Rincón  (supplier of updated sugar 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: Tue, 17 Apr 2018 13:49:19 +0200
Source: sugar
Binary: sucrose sugar-session python-jarabe
Architecture: source
Version: 0.112-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Sugar Team 
Changed-By: Santiago Ruano Rincón 
Description:
 python-jarabe - Sugar Learning Platform - graphical shell
 sucrose- Sugar Learning Platform - Sucrose
 sugar-session - Sugar Learning Platform - window manager
Closes: 886040
Changes:
 sugar (0.112-3) unstable; urgency=medium
 .
   [ Santiago Ruano Rincón ]
   * Add upstream_0001-jarabe-extensions-remove-GConf-compatibility.patch
 (Closes: #886040)
   * debian/control: remove Build-Depends on libgconf2-dev
 .
   [ Jeremy Bicha ]
   * Drop more gconf dependencies
   * Run autoreconf so that patch works
Checksums-Sha1:
 1aeae60ffe1047152be4b2403fd4464905a93a17 2190 sugar_0.112-3.dsc
 3f6b688a3a6d23986457d1edf1c32b1d3f267e1e 38952 sugar_0.112-3.debian.tar.xz
 4de8143123c2c78c773a05094127d84b03117728 15355 sugar_0.112-3_armhf.buildinfo
Checksums-Sha256:
 11263b2ae2f26b4c23be4584ce80b7652184c3b6982f0aba4e092bb673169dc8 2190 
sugar_0.112-3.dsc
 e628205956b28ca9940d1d14b06ba001ff66bf8a160a3a156c923a9fcf7f1d76 38952 
sugar_0.112-3.debian.tar.xz
 a77ad77f26a78980eed4b24a78eb0a6225e70e48d2e9e5c714c9ec4a02d8d446 15355 
sugar_0.112-3_armhf.buildinfo
Files:
 0b0d90bdb78117f3df1d480d0c438501 2190 x11 optional sugar_0.112-3.dsc
 499683e1f8cdc643815fc6b87e233f50 38952 x11 optional sugar_0.112-3.debian.tar.xz
 25c3a523326f6d9d66fccb97d8d37225 15355 x11 optional 
sugar_0.112-3_armhf.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEwUqnBPVvaa0NAVzHFX/a4RXx4q0FAlrV868ACgkQFX/a4RXx
4q3jWQ/9GnINGf94nInITDqqDIcPIUEfa6z/GaFhe/nbLBUKvTLbJGoP5A9r6AKz
kUhnaWemtbsDFgBIG5/xLBLDBLPkLPn02h2GAIJ2iv8+AsbcJKge44iNxOhNaO5N
fRGEM4I9k7xJqoc83N+SxUIx39Bh3kj38J30hJA1w19Bm0dQtAxcjtZEvWYzt+FW
AL4ox7tN3jP/Fj/oiQ1M5Y1MF7/K3JaMnerMOYBoeO9UrRkJWZkNUm5KhyqW5PvU
cb9eaP5NUyLyVgpoG4taqzsDaKtYYKaEhx+Iy6/qF4CdFHq7WywuqyH2F02/fnxI
T74HnYhBTWm1JFUVFxYYgR0y4VhlbgIZO+1ZX/dM8C2W/IsHEPFrLZ0rE3svxhN9
HMYapADs+uYErE61gXc8E+Qum7z09bpD4aVZPiTLcC15P0rK7BV/UUyFjxK8GG9V
w+rCGNwU5Uv8PmwYvxm/a5AV398pbdhfFRZUMMFlwAWd2lq/+LGIAG002jqQAMIt
22hQNPwbV/YXZ8SiNnpctFPdAv0v0jOMvq/WZS3wUS4uTvWPuhiWhnQ0DYH+c6Xa
XeZiC9oH5VfCSLTqmWOjGKeCVpRKyGGiYB07ej108r3HewYyjkPJTQidMCtnKbBF
GCxyklzM8ZT4gSYZ4Nibj3V10y42IO4ty5VSa/C6HWP/ZOAHsvc=
=GWhQ
-END PGP SIGNATURE End Message ---

Bug#895208: marked as done (gnumeric: missing build dependency on libxml2-utils)

[Debian Bug Tracking System]

Your message dated Tue, 17 Apr 2018 12:19:33 +
with message-id 
and subject line Bug#895208: fixed in gnumeric 1.12.35-1.1
has caused the Debian Bug report #895208,
regarding gnumeric: missing build dependency on libxml2-utils
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.)


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

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

...
checking for perl... perl
checking
 for perl ExtUtils::Embed module... yes
checking Checking for perl compiler, linker, libraries and headers... yes
checking for python... /usr/bin/python
checking
 for python = 2.x... yes
checking
 Look for /usr/include/python2.7/Python.h... yes
checking for PYGOBJECT... yes
checking for itstool... itstool
checking for xmllint... no
configure: error: xmllint not found
--- End Message ---
--- Begin Message ---
Source: gnumeric
Source-Version: 1.12.35-1.1

We believe that the bug you reported is fixed in the latest version of
gnumeric, 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 895...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated gnumeric 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: Tue, 17 Apr 2018 12:51:49 +0200
Source: gnumeric
Binary: gnumeric gnumeric-common gnumeric-doc gnumeric-plugins-extra 
gir1.2-gnumeric
Architecture: source
Version: 1.12.35-1.1
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Smirnov 
Changed-By: Andreas Tille 
Description:
 gir1.2-gnumeric - GObject introspection data for the Gnumeric spreadsheet
 gnumeric   - spreadsheet application for GNOME - main program
 gnumeric-common - spreadsheet application for GNOME - common files
 gnumeric-doc - spreadsheet application for GNOME - documentation
 gnumeric-plugins-extra - spreadsheet application for GNOME - additional plugins
Closes: 895208
Changes:
 gnumeric (1.12.35-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Moved packaging from Alioth to Salsa with permission of maintainer
   * Add missing Build-Depends: libxml2-utils
 Closes: #895208
Checksums-Sha1:
 2eac68f299a547e3d20bf4ab8fd783fc9a99a4be 2575 gnumeric_1.12.35-1.1.dsc
 20b1deee0aaf0f2469033d855cc301ceb5fc15d4 43044 
gnumeric_1.12.35-1.1.debian.tar.xz
 f88d83059adc42a51de905a325163a5785c8f567 16692 
gnumeric_1.12.35-1.1_source.buildinfo
Checksums-Sha256:
 ff51dc8168c178c323467f95c83de62141c76e4d88a2519fb3fe891844bca76d 2575 
gnumeric_1.12.35-1.1.dsc
 d0d7f3d8c9ae345df4cfd79be8685c7a464d3c37a24e48100c67e795fe322015 43044 
gnumeric_1.12.35-1.1.debian.tar.xz
 1b19d8f7e83a0afd99679bfb24f9345baf85b42b44ba67127e4a7b4973e595e9 16692 
gnumeric_1.12.35-1.1_source.buildinfo
Files:
 2bda8495959eade38e272920a50213a2 2575 math optional gnumeric_1.12.35-1.1.dsc
 9e21f8713e67a5d957a0fc771e9d6a1b 43044 math optional 
gnumeric_1.12.35-1.1.debian.tar.xz
 b9b60eb9773818cb94481954eac64033 16692 math optional 
gnumeric_1.12.35-1.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJCBAEBCAAsFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlrV4+QOHHRpbGxlYUBy
a2kuZGUACgkQV4oElNHGRtHfow/8DeXz/UejYtTHJMz/N31gsgzthbxUg2u06KMK
/FuLvNNaqcWMlEeaM5bmteyKkog1hpjj7T2HzpS8h1whgpj2BjHLB/eXgywGw1NI
jW27/D2ha/ZKu/nUZ6BGyEtfP2XkeQszrJsGbxla8H/CzOZSucf18SiSOzjTcQEE
DVVWctGsqHhNqoWchSTD2D/WIi4Zyak73XZLMaZCPXrmHRwvt6XzJ9RQy+z90Ff/
HHzjZ0pa+eViDhhi0XLDb/h7/LX7KN22+UXkssIfUMuHKeYxDw/gXokYnjE10HMd
Tep9fLwMuVCrST7HLT7wAqrcqZto/2uD5x9MKTuvrMIun/wMrcGTpNK0LhmsdbV4
iTqwYYAJpL1JDeMe8JoMNbOeubTv1RUy2w7RldakiRmGu2Z1Ecr0HjjkHH3D1vcN
atm6jjw9OCD9EB3sR4nxTeXX0J2SM4rVV4rQw2qOmOrWLgDgdg5AXNKqH7Q9FM4F
mUTiS+GyPjypF7FTvGan+3lY5GdHB5drh/E67warDYLprqSwpzMKlgm4YLuzJdMJ
evYvgRp3CCw039J4POgwG0u+JUAX+a6QSYL2/OrkRctWREgiVrUauvJK6/rBruBH
UnS8U3FP/rg3TGxcHAmVCvwCMtfL/xRq/DSh5sNxlZS1/C6B34GgGM0IMVI5djLv
SvE4Ai4=
=qXS9
-END PGP SIGNATURE End Message ---

Bug#895208: gnumeric: missing build dependency on libxml2-utils

[Andreas Tille]

Hi Dmitry,

On Tue, Apr 17, 2018 at 06:53:11PM +1000, Dmitry Smirnov wrote:
> 
> I would appreciate any help with migration to Salsa. Please go ahead with NMU 
> as well if you feel it is urgent. I'm planning to spend some time on Gnumeric 
> hopefully this weekend...

Gnumeric moved to

https://salsa.debian.org/debian/gnumeric

adapted Vcs-fields, fixed bug and uploaded.

Kind regards

   Andreas.


-- 
http://fam-tille.de

Bug#895899: libhtmlcleaner-java FTBFS with openjdk-9

[Adrian Bunk]

Source: libhtmlcleaner-java
Version: 2.21-2
Severity: serious

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

...
[INFO] ---
[INFO]  T E S T S
[INFO] ---
[INFO] Running org.htmlcleaner.UtilsTest
[INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.136 s 
- in org.htmlcleaner.UtilsTest
[INFO] Running org.htmlcleaner.DomSerializerTest
[WARNING] Tests run: 5, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.231 
s - in org.htmlcleaner.DomSerializerTest
[INFO] Running org.htmlcleaner.ScriptTest
[INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.022 s 
- in org.htmlcleaner.ScriptTest
[INFO] Running org.htmlcleaner.NamespacesTest
[INFO] Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.088 s 
- in org.htmlcleaner.NamespacesTest
[INFO] Running org.htmlcleaner.TagBalancingTest
[INFO] Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.292 s 
- in org.htmlcleaner.TagBalancingTest
[INFO] Running org.htmlcleaner.VisitorTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.006 s 
- in org.htmlcleaner.VisitorTest
[INFO] Running org.htmlcleaner.XmlDeclarationsTest
[INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.013 s 
- in org.htmlcleaner.XmlDeclarationsTest
[INFO] Running org.htmlcleaner.JDomSerializerTest
[INFO] Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.053 s 
- in org.htmlcleaner.JDomSerializerTest
[INFO] Running org.htmlcleaner.RandomCloseTagTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - in 
org.htmlcleaner.RandomCloseTagTest
[INFO] Running org.htmlcleaner.BadTerminationTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - in 
org.htmlcleaner.BadTerminationTest
[INFO] Running org.htmlcleaner.TagManipulationTest
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 s 
- in org.htmlcleaner.TagManipulationTest
[INFO] Running org.htmlcleaner.SpecialEntitiesTest
[INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 s 
- in org.htmlcleaner.SpecialEntitiesTest
[INFO] Running org.htmlcleaner.EntityDeserializationTest
[INFO] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.008 s 
- in org.htmlcleaner.EntityDeserializationTest
[INFO] Running org.htmlcleaner.SVGTest
[INFO] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.015 s 
- in org.htmlcleaner.SVGTest
[INFO] Running org.htmlcleaner.HtmlCleanerTest
[ERROR] Tests run: 56, Failures: 0, Errors: 1, Skipped: 4, Time elapsed: 0.493 
s <<< FAILURE! - in org.htmlcleaner.HtmlCleanerTest
[ERROR] attributeNames(org.htmlcleaner.HtmlCleanerTest)  Time elapsed: 0.193 s  
<<< ERROR!
java.lang.StringIndexOutOfBoundsException: begin 117, end -1, length 161
at 
org.htmlcleaner.HtmlCleanerTest.attributeNames(HtmlCleanerTest.java:61)

[INFO] Running org.htmlcleaner.ClosedTagReopenTest
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 s 
- in org.htmlcleaner.ClosedTagReopenTest
[INFO] Running org.htmlcleaner.BrowserCompactXmlSerializerTest
[INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 s 
- in org.htmlcleaner.BrowserCompactXmlSerializerTest
[INFO] Running org.htmlcleaner.TransformationTest
[INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 s 
- in org.htmlcleaner.TransformationTest
[INFO] Running org.htmlcleaner.ConstructorTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - in 
org.htmlcleaner.ConstructorTest
[INFO] Running org.htmlcleaner.ThreadSafetyTest
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.276 s 
- in org.htmlcleaner.ThreadSafetyTest
[INFO] Running org.htmlcleaner.PropertiesTest
[INFO] Tests run: 27, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.093 s 
- in org.htmlcleaner.PropertiesTest
[INFO] Running org.htmlcleaner.TagCopyingAndLimitingTest
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.016 s 
- in org.htmlcleaner.TagCopyingAndLimitingTest
[INFO] Running org.htmlcleaner.CDATATest
[INFO] Tests run: 20, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.07 s 
- in org.htmlcleaner.CDATATest
[INFO] Running org.htmlcleaner.XPatherTest
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.404 s 
- in org.htmlcleaner.XPatherTest
[INFO] Running org.htmlcleaner.RandomPageTest
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 s 
- in org.htmlcleaner.RandomPageTest
[INFO] Running org.htmlcleaner.DocTypesTest
[INFO] Tests run: 40, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.04 s 
- in org.htmlcleaner.DocTypesTest
[INFO] Running org.htmlcleaner.CollapseHtmlTest
[INFO] Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time 

Bug#876528: marked as done (python-intbitset binary-all FTBFS: ImportError: No module named intbitset)

[Debian Bug Tracking System]

Your message dated Tue, 17 Apr 2018 11:05:14 +
with message-id 
and subject line Bug#876528: fixed in python-intbitset 2.3.0-3
has caused the Debian Bug report #876528,
regarding python-intbitset binary-all FTBFS: ImportError: No module named 
intbitset
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.)


-- 
876528: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876528
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-intbitset
Version: 2.3.02.3.0-2
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=python-intbitset=all=2.3.0-2=1504955651=0

...
make[1]: Leaving directory '/<>'
   dh_auto_test -i -O--buildsystem=pybuild
I: pybuild base:184: cd /<>/.pybuild/pythonX.Y_2.7/build; 
python2.7 -m nose tests
EE
==
ERROR: intbitset - ascii bit dump
--
Traceback (most recent call last):
  File "/<>/.pybuild/pythonX.Y_2.7/build/tests/test_intbitset.py", 
line 42, in setUp
from intbitset import intbitset
ImportError: No module named intbitset

==
ERROR: intbitset - list dump
--
Traceback (most recent call last):
  File "/<>/.pybuild/pythonX.Y_2.7/build/tests/test_intbitset.py", 
line 42, in setUp
from intbitset import intbitset
ImportError: No module named intbitset

==
ERROR: intbitset - marshalling
--
Traceback (most recent call last):
  File "/<>/.pybuild/pythonX.Y_2.7/build/tests/test_intbitset.py", 
line 42, in setUp
from intbitset import intbitset
ImportError: No module named intbitset

==
ERROR: intbitset - test no segmentation fault with foreign data types
--
Traceback (most recent call last):
  File "/<>/.pybuild/pythonX.Y_2.7/build/tests/test_intbitset.py", 
line 42, in setUp
from intbitset import intbitset
ImportError: No module named intbitset

==
ERROR: intbitset - pickling
--
Traceback (most recent call last):
  File "/<>/.pybuild/pythonX.Y_2.7/build/tests/test_intbitset.py", 
line 42, in setUp
from intbitset import intbitset
ImportError: No module named intbitset

==
ERROR: intbitset - clearing
--
Traceback (most recent call last):
  File "/<>/.pybuild/pythonX.Y_2.7/build/tests/test_intbitset.py", 
line 42, in setUp
from intbitset import intbitset
ImportError: No module named intbitset

==
ERROR: intbitset - set cloning
--
Traceback (most recent call last):
  File "/<>/.pybuild/pythonX.Y_2.7/build/tests/test_intbitset.py", 
line 42, in setUp
from intbitset import intbitset
ImportError: No module named intbitset

==
ERROR: intbitset - (non infinite) set comparison
--
Traceback (most recent call last):
  File "/<>/.pybuild/pythonX.Y_2.7/build/tests/test_intbitset.py", 
line 42, in setUp
from intbitset import intbitset
ImportError: No module named intbitset

==
ERROR: intbitset - set consistence
--
Traceback (most recent call last):
  File "/<>/.pybuild/pythonX.Y_2.7/build/tests/test_intbitset.py", 
line 42, in setUp
from intbitset import intbitset
ImportError: No module named intbitset

==
ERROR: intbitset - set corruption
--
Traceback (most recent call last):
  File "/<>/.pybuild/pythonX.Y_2.7/build/tests/test_intbitset.py", 
line 42, in setUp
from intbitset import intbitset
ImportError: No module 

Bug#895889: golang-github-weaveworks-mesh: new version causes regression in prometheus-alertmanager

[Adrian Bunk]

On Tue, Apr 17, 2018 at 11:20:13AM +0200, Paul Gevers wrote:
>...
> As the it seems that the same code is used to build the
> prometheus-alertmanager package, I think this means that that now FTBFS
> (haven't verified).
>...

prometheus-alertmanager does FTBFS now:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/prometheus-alertmanager.html

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

Bug#895890: pandas: FTBFS on mips and powerpc: test_unstack_odd_failure crashes

[Graham Inggs]

Source: pandas
Version: 0.22.0-2
Severity: serious

Hi Science Team

Since the upload of 0.22.0-2, pandas has FTBFS on mips and powerpc with 
errors similar to the following:


../debian/tmp/usr/lib/python2.7/dist-packages/pandas/tests/test_multilevel.py::TestMultiLevel::test_unstack_odd_failure 
realloc(): invalid next size

Aborted
XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":99"

make[1]: *** [debian/rules:127: python-test2.7] Error 134
make[1]: Leaving directory '/<>'

The errors I have found in the build logs are:
realloc(): invalid next size
malloc(): smallbin double linked list corrupted
Segmentation fault
corrupted double-linked list

Pandas 0.22.0-1 failed for an unrelated reason.
The test_unstack_odd_failure did not fail with any of the 0.20.3-* 
uploads (it either passed, or the build failed for other reasons).


I'm marking this serious as the failure on mips prevents the migration 
of pandas to testing.


Regards
Graham

Bug#893039: libccnet0: contains a python module

[Moritz Schlarb]

Hi Helmut,

I addressed this issue in 6.1.5-2, but since this leads to a new binary
upload, I can't upload it myself since I'm just a DM.
My mentor/sponsor Christoph is currently out of the office, so he can't
do it either.
So I've uploaded it to https://mentors.debian.net/package/ccnet - maybe
you are willing to perform the upload for me (If that went through, I'm
gonna upload the new upstream version myself).

Best regards,
Moritz



signature.asc
Description: OpenPGP digital signature

Processed: your mail

[Debian Bug Tracking System]

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

> forwarded 890907 https://github.com/cisco/cjose/issues/70
Bug #890907 [src:cjose] cjose FTBFS on big endian: test failure
Set Bug forwarded-to-address to 'https://github.com/cisco/cjose/issues/70'.
>
End of message, stopping processing here.

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

Bug#892394: [pkg-boost-devel] Bug#892394: boost1.63: build-depends on GCC 6

[Marc Glisse]

Dimitri John Ledkov:


boost1.65 has been rejected by ftp-masters, on copyright reasons.


Hello,

could you include a reference to the corresponding discussion, please? I 
didn't manage to find it on the debian mailing lists. The only potentially 
relevant thing I found is a discussion in February on the boost mailing 
list about one stackoverflow snippet, but it does not mention debian at 
all and seems too small a reason to reject the library.


--
Marc Glisse

Processed: affected packages for autopkgtest triggers bugs

[Debian Bug Tracking System]

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

> affects 895889 src:prometheus-alertmanager
Bug #895889 [src:golang-github-weaveworks-mesh] golang-github-weaveworks-mesh: 
new version causes regression in prometheus-alertmanager
Added indication that 895889 affects src:prometheus-alertmanager
> affects 895882 src:sphinxcontrib-bibtex
Bug #895882 [src:sphinx] sphinx: version 1.7.2-1 causes regression in 
sphinxcontrib-bibtex (Unknown node: bibliography)
Added indication that 895882 affects src:sphinxcontrib-bibtex
> thanks
Stopping processing here.

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

Bug#895889: golang-github-weaveworks-mesh: new version causes regression in prometheus-alertmanager

[Paul Gevers]

Source: golang-github-weaveworks-mesh
Version: 0.1+git20180323.0c91e69-1
Severity: serious
User: debian...@lists.debian.org
Usertags: triggers
Affects: prometheus-alertmanager

Since the upload of golang-github-weaveworks-mesh version
0.1+git20180323.0c91e69-1, the autopkgtest of prometheus-alertmanager¹
fails with the errors copied below.

As the it seems that the same code is used to build the
prometheus-alertmanager package, I think this means that that now FTBFS
(haven't verified). If you believe this was exaggerated or the issue is
really in prometheus-alertmanager, please don't hesitate to lower it
accordingly and/or reassign to prometheus-alertmanager.

I suggest the maintainers of golang-github-weaveworks-mesh and
prometheus-alertmanager discuss how this issue should be solved (hence
the CC).

Paul

¹ https://ci.debian.net/packages/p/prometheus-alertmanager

dh_auto_build: cd build && go install
-gcflags=\"-trimpath=/tmp/autopkgtest-lxc.6nk_tdek/downtmp/autopkgtest_tmp/build/src\"
-asmflags=\"-trimpath=/tmp/autopkgtest-lxc.6nk_tdek/downtmp/autopkgtest_tmp/build/src\"
-v -p 2 -ldflags " -X
github.com/prometheus/common/version.Version=0.6.2+ds -X
github.com/prometheus/common/version.Revision=0.6.2+ds-5 -X
github.com/prometheus/common/version.Branch=debian/sid -X
github.com/prometheus/common/version.BuildUser=pkg-go-maintain...@lists.alioth.debian.org
-X github.com/prometheus/common/version.BuildDate=20180327-00:03:07 -X
github.com/prometheus/common/version.GoVersion=go1.10rc2"
github.com/prometheus/alertmanager/api
github.com/prometheus/alertmanager/artifacts
github.com/prometheus/alertmanager/cli
github.com/prometheus/alertmanager/cli/format
github.com/prometheus/alertmanager/cmd/alertmanager
github.com/prometheus/alertmanager/cmd/amtool
github.com/prometheus/alertmanager/config
github.com/prometheus/alertmanager/dispatch
github.com/prometheus/alertmanager/examples/webhook
github.com/prometheus/alertmanager/inhibit
github.com/prometheus/alertmanager/nflog
github.com/prometheus/alertmanager/nflog/nflogpb
github.com/prometheus/alertmanager/notify
github.com/prometheus/alertmanager/pkg/parse
github.com/prometheus/alertmanager/provider
github.com/prometheus/alertmanager/provider/mem
github.com/prometheus/alertmanager/silence
github.com/prometheus/alertmanager/silence/silencepb
github.com/prometheus/alertmanager/template
github.com/prometheus/alertmanager/template/internal/deftmpl
github.com/prometheus/alertmanager/test
github.com/prometheus/alertmanager/types
github.com/prometheus/alertmanager/ui returned exit code 2
debian/rules:51: recipe for target 'override_dh_auto_build' failed
make[1]: Leaving directory
'/tmp/autopkgtest-lxc.6nk_tdek/downtmp/autopkgtest_tmp'
make[1]: *** [override_dh_auto_build] Error 2
debian/rules:31: recipe for target 'build' failed
make: *** [build] Error 2



signature.asc
Description: OpenPGP digital signature

Processed (with 1 error): house cleaning

[Debian Bug Tracking System]

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

> forwarded 885280 https://github.com/pixelb/fslint/issues/147
Bug #885280 [src:fslint] fslint: Depends on unmaintained pygtk
Set Bug forwarded-to-address to 'https://github.com/pixelb/fslint/issues/147'.
> forcemerge 875250 851827
Bug #875250 [src:scim] [scim] Future Qt4 removal from Buster
Bug #875258 [src:scim] [scim] Future Qt4 removal from Buster
Unable to merge bugs because:
package of #851827 is 'scim-qt-immodule' not 'src:scim'
Failed to forcibly merge 875250: Did not alter merged bugs.

> fixed 839837 2.44-3
Bug #839837 [fslint] .desktop file does not validate
Marked as fixed in versions fslint/2.44-3.
>
End of message, stopping processing here.

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

Bug#895208: gnumeric: missing build dependency on libxml2-utils

[Dmitry Smirnov]

On Monday, 16 April 2018 4:30:43 PM AEST Andreas Tille wrote:
> I'd volunteer to NMU this package but it seems it also needs migration
> to Salsa.  Since I usually like to push my changes to Git I'd like to
> ask for permission to do the Salsa migration for gnumeric.  I'll assume
> that you agree to this if I do not hear from you soon.

I would appreciate any help with migration to Salsa. Please go ahead with NMU 
as well if you feel it is urgent. I'm planning to spend some time on Gnumeric 
hopefully this weekend...

-- 
Regards,
 Dmitry Smirnov.

---

The surest way to corrupt a youth is to instruct him to hold in higher
esteem those who think alike than those who think differently.
-- Friedrich Nietzsche


signature.asc
Description: This is a digitally signed message part.

Processed: affects 895320

[Debian Bug Tracking System]

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

> affects 895320 src:mk-configure
Bug #895320 [ghostscript] mk-configure FTBFS: Error: /undefined in setupLatin1
Added indication that 895320 affects src:mk-configure
> thanks
Stopping processing here.

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

Processed: tagging 895320

[Debian Bug Tracking System]

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

> tags 895320 + buster sid
Bug #895320 [ghostscript] mk-configure FTBFS: Error: /undefined in setupLatin1
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Processed: found 895860 in 1.32+dfsg-3

[Debian Bug Tracking System]

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

> found 895860 1.32+dfsg-3
Bug #895860 [geany-plugins] geany-plugins: Unroutable maintainer address
Marked as found in versions geany-plugins/1.32+dfsg-3.
> thanks
Stopping processing here.

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

Processed: found 895859 in 0.14.0-1

[Debian Bug Tracking System]

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

> found 895859 0.14.0-1
Bug #895859 [gir-to-d] gir-to-d: Unroutable maintainer address
Marked as found in versions gir-to-d/0.14.0-1.
> thanks
Stopping processing here.

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

Bug#895882: sphinx: version 1.7.2-1 causes regression in sphinxcontrib-bibtex (Unknown node: bibliography)

[Paul Gevers]

Source: sphinx
Version: 1.7.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: triggers
Affects: sphinxcontrib-bibtex

Since the upload of sphinx version 1.7.2-1, the autopkgtest of
sphinxcontrib-bibtex¹ fails with the errors copied below.

As all the failures (25 failures/28 tests) really come from the same
issue (NotImplementedError: Unknown node: bibliography), the ratio
between passes and failures is so high, and the missing node name
suggests core functionality for sphinxcontrib-bibtex I file this bug
with severity *serious* against sphinx. If you believe this was
exaggerated or the issue is really in sphinxcontrib-bibtex, please don't
hesitate to lower it accordingly and/or reassign to sphinxcontrib-bibtex.

I suggest the maintainers of sphinx and sphinxcontrib-bibtex discuss how
this issue should be solved (hence the CC).

Paul

¹ https://ci.debian.net/packages/s/sphinxcontrib-bibtex

==
ERROR: test_bibfilenotfound.test_bibfilenotfound
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File "/usr/lib/python3/dist-packages/sphinx_testing/util.py", line
143, in decorator
func(*(args + (app, status, warning)), **kwargs)
  File
"/tmp/autopkgtest-lxc.pusg50mw/downtmp/autopkgtest_tmp/test/test_bibfilenotfound.py",
line 22, in test_bibfilenotfound
app.builder.build_all()
  File "/usr/lib/python3/dist-packages/sphinx/builders/__init__.py",
line 295, in build_all
self.build(None, summary='all source files', method='all')
  File "/usr/lib/python3/dist-packages/sphinx/builders/__init__.py",
line 399, in build
self.write(docnames, list(updated_docnames), method)
  File "/usr/lib/python3/dist-packages/sphinx/builders/__init__.py",
line 436, in write
self._write_serial(sorted(docnames))
  File "/usr/lib/python3/dist-packages/sphinx/builders/__init__.py",
line 445, in _write_serial
self.write_doc(docname, doctree)
  File "/usr/lib/python3/dist-packages/sphinx/builders/html.py", line
602, in write_doc
self.docwriter.write(doctree, destination)
  File "/usr/lib/python3/dist-packages/docutils/writers/__init__.py",
line 80, in write
self.translate()
  File "/usr/lib/python3/dist-packages/sphinx/writers/html.py", line 56,
in translate
self.document.walkabout(visitor)
  File "/usr/lib/python3/dist-packages/docutils/nodes.py", line 174, in
walkabout
if child.walkabout(visitor):
  File "/usr/lib/python3/dist-packages/docutils/nodes.py", line 166, in
walkabout
visitor.dispatch_visit(self)
  File "/usr/lib/python3/dist-packages/docutils/nodes.py", line 1882, in
dispatch_visit
return method(node)
  File "/usr/lib/python3/dist-packages/sphinx/writers/html.py", line
882, in unknown_visit
raise NotImplementedError('Unknown node: ' + node.__class__.__name__)
NotImplementedError: Unknown node: bibliography

==
ERROR: test_citationnotfound.test_citationnotfound
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File "/usr/lib/python3/dist-packages/sphinx_testing/util.py", line
143, in decorator
func(*(args + (app, status, warning)), **kwargs)
  File
"/tmp/autopkgtest-lxc.pusg50mw/downtmp/autopkgtest_tmp/test/test_citationnotfound.py",
line 22, in test_citationnotfound
app.builder.build_all()
  File "/usr/lib/python3/dist-packages/sphinx/builders/__init__.py",
line 295, in build_all
self.build(None, summary='all source files', method='all')
  File "/usr/lib/python3/dist-packages/sphinx/builders/__init__.py",
line 399, in build
self.write(docnames, list(updated_docnames), method)
  File "/usr/lib/python3/dist-packages/sphinx/builders/__init__.py",
line 436, in write
self._write_serial(sorted(docnames))
  File "/usr/lib/python3/dist-packages/sphinx/builders/__init__.py",
line 445, in _write_serial
self.write_doc(docname, doctree)
  File "/usr/lib/python3/dist-packages/sphinx/builders/html.py", line
602, in write_doc
self.docwriter.write(doctree, destination)
  File "/usr/lib/python3/dist-packages/docutils/writers/__init__.py",
line 80, in write
self.translate()
  File "/usr/lib/python3/dist-packages/sphinx/writers/html.py", line 56,
in translate
self.document.walkabout(visitor)
  File "/usr/lib/python3/dist-packages/docutils/nodes.py", line 174, in
walkabout
if child.walkabout(visitor):
  File "/usr/lib/python3/dist-packages/docutils/nodes.py", line 166, in
walkabout
visitor.dispatch_visit(self)
  File "/usr/lib/python3/dist-packages/docutils/nodes.py", line 1882, in
dispatch_visit
return method(node)
  File "/usr/lib/python3/dist-packages/sphinx/writers/html.py", line
882, in 

Bug#895320: ps2pdf crashes

[Andrew Shadura]

Control: reassign -1 ghostscript

It doesn't seem like a bug in mk-configure, I don't see anything
criminal in the .tex source.

-- 
Cheers,
  Andrew

Processed: ps2pdf crashes

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 ghostscript
Bug #895320 [src:mk-configure] mk-configure FTBFS: Error: /undefined in 
setupLatin1
Bug reassigned from package 'src:mk-configure' to 'ghostscript'.
No longer marked as found in versions mk-configure/0.29.1-2.
Ignoring request to alter fixed versions of bug #895320 to the same values 
previously set

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

Processed: tagging 864719

[Debian Bug Tracking System]

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

> tags 864719 + pending
Bug #864719 [slapd] slapd: fails to configure when olcSuffix contains a 
backslash-escaped umlaut
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#894993: patch: CVE-2018-1000156: input validation vulnerability when processing patch files

[GCS]

On Mon, Apr 16, 2018 at 10:46 PM, Chris Lamb  wrote:
> Moritz Muehlenhoff wrote:
>
>> We're not planning to issue a DSA for this, but Laszlo is working on
>> updates for point releases. Best to sync up directly with him if only to
>> compare the debdiffs you came up with.
>
> Nod, thanks. Well, I wouldn't want to duplicate work ("compare debdiffs").
>
> Laszlo, would you like me to co-ordindate jessie-pu and stretch-pu's or have
> you got this?  (Feel free to drop t...@security.debian.org on any reply..)
 I didn't yet filed for the package updates for Jessie and Stretch as
I got confused: any of you want to review my patches first? Both
package update is ready and quick tested by the way.

Regards,
Laszlo/GCS