Bug#911154: netkit-ntalk misses the generator for configure

[Alberto Gonzalez Iniesta]

On Thu, Dec 06, 2018 at 06:42:33AM +0100, Christoph Biedl wrote:
> tags -1 patch
> user debian-rele...@lists.debian.org
> usertags -1 + bsp-2018-12-ch-bern
> thanks
> 
> So here we go ...
> 
> The files resulting from the conversion to cmake are not as terse as I
> hoped they would be. Still, at least for me, this is an improvement
> over to several handcrafted rules, especially for any future changes in
> the Debian build system.
> 
[snip]
> ### Packages maintained by Alberto Gonzalez Iniesta 
> 
> * netkit-bootparamd
> * netkit-ntalk
> * netkit-rsh
> * netkit-rusers
> * netkit-rwall
> * netkit-rwho
> * netkit-tftp
> 
> Alberto, you'll do me a favour if you could refrain from uploading
> for a few days - I'll do some more checks and expect one or two more
> things will come up that require an adjustment.
> 
> Also, some formatting was done in my personal style. Feel free to apply
> your $QUILT_REFRESH_ARGS on top of this.


Hello, Christoph.

Huge thanks for your massive work on this. I'll wait for any news from
you for a few days. No problem at all.

Cheers,

Alberto


-- 
Alberto Gonzalez Iniesta| Formación, consultoría y soporte técnico
mailto/sip: a...@inittab.org | en GNU/Linux y software libre
Encrypted mail preferred| http://inittab.com

Key fingerprint = 5347 CBD8 3E30 A9EB 4D7D  4BF2 009B 3375 6B9A AA55

Bug#914953: [3dprinter-general] Bug#914953: FTBFS with Python 3.7 on many architectures

[Gregor Riepl]

> I suspect that many optional symbols on the symbols file of this package
> could be squashed with a regex, but alas I can't help with that now
> since I'll be soon leaving for a 2-weeks travel and I don't think I
> would ever find the time to also look at this.  Anyway, look at the gdcm
> repo for an idea of what I'm talking about.

Not sure if a regex is appropriate here, since some of the symbols come and
go, depending on the compiler, dependencies and architecture.

But I'll take look, thanks for the hint.

> Anyway, the problem that dpkg-gensymbols is complaining about, it's
> because you missed a quote sign in
> a4f32173da0f7ab5c173d89fd556f0af242d2deb (didn't you notice this while
> test building before asking for sponsorship?).

Ouch, thanks for pointing that out.
I totally didn't see this.
Thought there was something wrong with the Debian-tagged version I added.

> After that my local build failed because I locally export
> DPKG_GENSYMBOLS_CHECK_LEVEL=4 and it seems this new symbol is new:
>
>
_ZNSt10_HashtableIPKN6google8protobuf10DescriptorESt4pairIKS4_jESaIS7_ENSt8__detail10_Select1stESt8equal_toIS4_ESt4hashIS4_ENS9_18_Mod_range_hashingENS9_20_Default_ranged_hashENS9_20_Prime_rehash_policyENS9_17_Hashtable_traitsILb0ELb0ELb121_M_insert_unique_nodeEmmPNS9_10_Hash_nodeIS7_Lb0EEEm@Base>>
Anyway, that's yet another std:: function leaked from who knows where,
> so nvm that…

I'll raise the issue on the developer's issue tracker and see if I can send
them a patch. Far too much time has been wasted on this already.

Processed: bug 906625 is forwarded to https://github.com/rails/globalid/issues/112

[Debian Bug Tracking System]

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

> forwarded 906625 https://github.com/rails/globalid/issues/112
Bug #906625 [src:ruby-globalid] ruby-globalid: FTBFS in buster/sid (failing 
tests)
Set Bug forwarded-to-address to 'https://github.com/rails/globalid/issues/112'.
> thanks
Stopping processing here.

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

Bug#912133: netkit-tftp misses the generator for configure

[Christoph Biedl]

tags -1 patch
user debian-rele...@lists.debian.org
usertags -1 + bsp-2018-12-ch-bern
thanks

Find attached the fix for netkit-tftp.

For a full explanation, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911154#44

Regards,

Christoph

diff -Nru netkit-tftp-0.17/debian/control netkit-tftp-0.17/debian/control
--- netkit-tftp-0.17/debian/control 2018-07-04 11:26:25.0 +0200
+++ netkit-tftp-0.17/debian/control 2018-07-04 11:26:25.0 +0200
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Alberto Gonzalez Iniesta 
 Standards-Version: 4.1.4
-Build-Depends: debhelper (>= 11)
+Build-Depends: debhelper (>= 11), cmake
 
 Package: tftp
 Architecture: any
diff -Nru netkit-tftp-0.17/debian/not-installed 
netkit-tftp-0.17/debian/not-installed
--- netkit-tftp-0.17/debian/not-installed   1970-01-01 01:00:00.0 
+0100
+++ netkit-tftp-0.17/debian/not-installed   2018-07-04 11:26:25.0 
+0200
@@ -0,0 +1,2 @@
+
+usr/share/man/man8/tftpd.8
diff -Nru netkit-tftp-0.17/debian/patches/875885.patch 
netkit-tftp-0.17/debian/patches/875885.patch
--- netkit-tftp-0.17/debian/patches/875885.patch2018-07-04 
11:26:25.0 +0200
+++ netkit-tftp-0.17/debian/patches/875885.patch1970-01-01 
01:00:00.0 +0100
@@ -1,37 +0,0 @@
-Index: netkit-tftp/configure
-===
 netkit-tftp.orig/configure 2018-07-03 17:30:02.671087917 +0200
-+++ netkit-tftp/configure  2018-07-03 17:30:08.663136286 +0200
-@@ -1,4 +1,5 @@
- #!/bin/sh
-+set -e
- #
- # This file was generated by confgen version 2.
- # Do not edit.
-@@ -85,7 +86,7 @@
- echo 'failed.'
- echo 'Cannot find a C compiler. Run configure with --with-c-compiler.'
- rm -f __conftest*
--exit
-+exit 33
- fi
- echo "$CC"
- else
-@@ -99,7 +100,7 @@
-  echo 'no'
-  echo 'Compiler '"$CC"' does not exist or cannot compile C; try 
another.'
-  rm -f __conftest*
-- exit
-+ exit 33
-  fi
- fi
- 
-@@ -186,7 +187,7 @@
- echo 'no'
- echo 'Cannot work out what to use for socklen_t. Help...'
- rm -f __conftest*
--exit
-+exit 33
- fi
- fi
- fi
diff -Nru netkit-tftp-0.17/debian/patches/cross.patch 
netkit-tftp-0.17/debian/patches/cross.patch
--- netkit-tftp-0.17/debian/patches/cross.patch 2018-07-04 11:26:25.0 
+0200
+++ netkit-tftp-0.17/debian/patches/cross.patch 1970-01-01 01:00:00.0 
+0100
@@ -1,26 +0,0 @@
 netkit-tftp-0.17.orig/configure
-+++ netkit-tftp-0.17/configure
-@@ -75,10 +75,7 @@
- if [ x"$CC" = x ]; then
- echo -n 'Looking for a C compiler... '
- for TRY in egcs gcc g++ CC c++ cc; do
--   (
--   $TRY __conftest.c -o __conftest || exit 1;
--   ./__conftest || exit 1;
--   ) >/dev/null 2>&1 || continue;
-+   $TRY __conftest.c -o __conftest >/dev/null 2>&1 || continue;
-CC=$TRY
-break;
- done
-@@ -91,10 +88,7 @@
- echo "$CC"
- else
- echo -n 'Checking if C compiler works... '
--if (
--  $CC __conftest.c -o __conftest || exit 1
--  ./__conftest || exit 1
--   ) >/dev/null 2>&1; then
-+if $CC __conftest.c -o __conftest >/dev/null 2>&1; then
-  echo 'yes'
-  else
-  echo 'no'
diff -Nru netkit-tftp-0.17/debian/patches/debian_changes_0.17-18.patch 
netkit-tftp-0.17/debian/patches/debian_changes_0.17-18.patch
--- netkit-tftp-0.17/debian/patches/debian_changes_0.17-18.patch
2018-07-04 11:26:25.0 +0200
+++ netkit-tftp-0.17/debian/patches/debian_changes_0.17-18.patch
2018-07-04 11:26:25.0 +0200
@@ -3,10 +3,8 @@
 Reviewed-By: Alberto Gonzalez Iniesta 
 Last-Update: 2018-07-03
 
-Index: netkit-tftp/MRULES
-===
 netkit-tftp.orig/MRULES2018-07-03 11:26:05.579450753 +0200
-+++ netkit-tftp/MRULES 2018-07-03 11:26:05.575450719 +0200
+--- a/MRULES
 b/MRULES
 @@ -1,8 +1,8 @@
  # Standard compilation rules (don't use make builtins)
  
@@ -18,23 +16,8 @@
 -  $(CC) $(CFLAGS) -I../include $< -c
 +  $(CC) $(CFLAGS) $< -c
  
-Index: netkit-tftp/tftp/Makefile
-===
 netkit-tftp.orig/tftp/Makefile 2018-07-03 11:26:05.579450753 +0200
-+++ netkit-tftp/tftp/Makefile  2018-07-03 11:26:05.575450719 +0200
-@@ -12,7 +12,7 @@
- tftp.o: ../version.h
- 
- install: tftp
--  install -s -m$(BINMODE) tftp $(INSTALLROOT)$(BINDIR)
-+  install -m$(BINMODE) tftp $(INSTALLROOT)$(BINDIR)
-   install -m$(MANMODE) tftp.1 $(INSTALLROOT)$(MANDIR)/man1
- 
- clean:
-Index: netkit-tftp/tftp/main.c
-===
 netkit-tftp.orig/tftp/main.c   2018-07-03 11:26:05.579450753 +0200
-+++ netkit-tftp/tftp/main.c2018-07-03 11:26:05.575450719 +0200
+--- a/tftp/main.

Bug#912130: netkit-rwho misses the generator for configure

[Christoph Biedl]

tags -1 patch
user debian-rele...@lists.debian.org
usertags -1 + bsp-2018-12-ch-bern
thanks

Find attached the fix for netkit-rwho.

For a full explanation, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911154#44

Regards,

Christoph

diff -Nru netkit-rwho-0.17/debian/compat netkit-rwho-0.17/debian/compat
--- netkit-rwho-0.17/debian/compat  2013-06-05 10:21:50.0 +0200
+++ netkit-rwho-0.17/debian/compat  2013-06-05 10:21:50.0 +0200
@@ -1 +1 @@
-7
+10
diff -Nru netkit-rwho-0.17/debian/control netkit-rwho-0.17/debian/control
--- netkit-rwho-0.17/debian/control 2013-06-05 10:21:50.0 +0200
+++ netkit-rwho-0.17/debian/control 2013-06-05 10:21:50.0 +0200
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Alberto Gonzalez Iniesta 
 Standards-Version: 3.9.4
-Build-Depends: debhelper (>= 7)
+Build-Depends: debhelper (>= 10~), cmake
 
 Package: rwhod
 Architecture: any
diff -Nru netkit-rwho-0.17/debian/patches/pre-0.17-13-changes.patch 
netkit-rwho-0.17/debian/patches/pre-0.17-13-changes.patch
--- netkit-rwho-0.17/debian/patches/pre-0.17-13-changes.patch   2013-06-05 
10:21:50.0 +0200
+++ netkit-rwho-0.17/debian/patches/pre-0.17-13-changes.patch   2013-06-05 
10:21:50.0 +0200
@@ -2,8 +2,8 @@
 Origin: Several people in history
 Reviewed-by: Alberto Gonzalez Iniesta
 Last-Update: 2013-06-13
 netkit-rwho-0.17.orig/ruptime/ruptime.c
-+++ netkit-rwho-0.17/ruptime/ruptime.c
+--- a/ruptime/ruptime.c
 b/ruptime/ruptime.c
 @@ -212,7 +212,7 @@
static char resbuf[32];
int days, hours, minutes;
@@ -26,35 +26,8 @@
updown, hours, minutes);
return(resbuf);
  }
 netkit-rwho-0.17.orig/rwho/Makefile
-+++ netkit-rwho-0.17/rwho/Makefile
-@@ -3,8 +3,6 @@
- include ../MCONFIG
- include ../MRULES
- 
--CFLAGS += -I../include
--
- rwho: rwho.o
-   $(CC) $(LDFLAGS) $^ $(LIBS) -o $@
- 
 netkit-rwho-0.17.orig/rwhod/Makefile
-+++ netkit-rwho-0.17/rwhod/Makefile
-@@ -3,8 +3,11 @@
- include ../MCONFIG
- include ../MRULES
- 
--CFLAGS += -I../include
--OBJS = rwhod.o daemon.o
-+ifneq ($(USE_GLIBC),1)
-+CFLAGS += -D_GNU_SOURCE
-+endif
-+
-+OBJS = rwhod.o
- 
- rwhod: $(OBJS)
-   $(CC) $(LDFLAGS) $^ $(LIBS) -o $@
 netkit-rwho-0.17.orig/rwhod/rwhod.8
-+++ netkit-rwho-0.17/rwhod/rwhod.8
+--- a/rwhod/rwhod.8
 b/rwhod/rwhod.8
 @@ -32,7 +32,10 @@
  .\" from: @(#)rwhod.8 6.5 (Berkeley) 3/16/91
  .\"   $Id: rwhod.8,v 1.16 2000/07/30 23:57:06 dholland Exp $
@@ -181,8 +154,8 @@
 +.Pp
 +Philippe Troin  implemented forwarding and interface
 +selection flags.
 netkit-rwho-0.17.orig/rwhod/rwhod.c
-+++ netkit-rwho-0.17/rwhod/rwhod.c
+--- a/rwhod/rwhod.c
 b/rwhod/rwhod.c
 @@ -29,6 +29,10 @@
   * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
   * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
diff -Nru netkit-rwho-0.17/debian/patches/series 
netkit-rwho-0.17/debian/patches/series
--- netkit-rwho-0.17/debian/patches/series  2013-06-05 10:21:50.0 
+0200
+++ netkit-rwho-0.17/debian/patches/series  2013-06-05 10:21:50.0 
+0200
@@ -1,2 +1,3 @@
 pre-0.17-13-changes.patch
 show_in_all_ifaces.patch
+use-cmake-as-buildsystem.patch
diff -Nru netkit-rwho-0.17/debian/patches/use-cmake-as-buildsystem.patch 
netkit-rwho-0.17/debian/patches/use-cmake-as-buildsystem.patch
--- netkit-rwho-0.17/debian/patches/use-cmake-as-buildsystem.patch  
1970-01-01 01:00:00.0 +0100
+++ netkit-rwho-0.17/debian/patches/use-cmake-as-buildsystem.patch  
2013-06-05 10:21:50.0 +0200
@@ -0,0 +1,70 @@
+Description: Use cmake as build system
+Author: Christoph Biedl 
+Bug-Debian: https://bugs.debian.org/912130
+Last-Update: 2018-11-25
+
+--- /dev/null
 b/CMakeLists.txt
+@@ -0,0 +1,10 @@
++cmake_minimum_required(VERSION 3.7)
++project(netkit-rwho)
++
++set(BIN_DIR "${CMAKE_INSTALL_PREFIX}/bin")
++set(SBIN_DIR "${CMAKE_INSTALL_PREFIX}/sbin")
++set(MAN_DIR "${CMAKE_INSTALL_PREFIX}/share/man")
++
++add_subdirectory(ruptime)
++add_subdirectory(rwho)
++add_subdirectory(rwhod)
+--- /dev/null
 b/ruptime/CMakeLists.txt
+@@ -0,0 +1,14 @@
++
++add_executable(
++ruptime
++ruptime.c
++)
++install(
++TARGETS ruptime
++DESTINATION ${BIN_DIR}
++)
++
++install(
++FILES ruptime.1
++DESTINATION ${MAN_DIR}/man1/
++)
+--- /dev/null
 b/rwho/CMakeLists.txt
+@@ -0,0 +1,14 @@
++
++add_executable(
++rwho
++rwho.c
++)
++install(
++TARGETS rwho
++DESTINATION ${BIN_DIR}
++)
++
++install(
++FILES rwho.1
++DESTINATION ${MAN_DIR}/man1/
++)
+--- /dev/null
 b/rwhod/CMakeLists.txt
+@@ -0,0 +1,15 @@
++
++add_executable(
++rwhod
++rwhod.c
++daemon.c
++)
++install(
++TARGETS rwhod
++DESTINATION ${SBIN_DIR}
++)
++
++install(
++FILES rwhod.8
++DESTINATION ${MAN_DIR}/man8/
++)
diff -Nru netkit-rwho-0.17/debian/rules netkit-rwho-0.17/debian/rules
--- netkit-rwho-0.17/debian/rules   2013-06

Bug#912129: netkit-rwall misses the generator for configure

[Christoph Biedl]

tags -1 patch
user debian-rele...@lists.debian.org
usertags -1 + bsp-2018-12-ch-bern
thanks

Find attached the fix for netkit-rwall.

For a full explanation, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911154#44

Regards,

Christoph

diff -Nru netkit-rwall-0.17/debian/compat netkit-rwall-0.17/debian/compat
--- netkit-rwall-0.17/debian/compat 2018-12-05 19:20:50.0 +0100
+++ netkit-rwall-0.17/debian/compat 2010-01-15 17:17:00.0 +0100
@@ -1 +1 @@
-7
+10
diff -Nru netkit-rwall-0.17/debian/control netkit-rwall-0.17/debian/control
--- netkit-rwall-0.17/debian/control2018-12-05 19:20:50.0 +0100
+++ netkit-rwall-0.17/debian/control2010-01-15 17:17:00.0 +0100
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Alberto Gonzalez Iniesta 
 Standards-Version: 3.8.3
-Build-Depends: debhelper (>= 7)
+Build-Depends: debhelper (>= 10~), cmake
 
 Package: rwalld
 Architecture: any
diff -Nru netkit-rwall-0.17/debian/not-installed 
netkit-rwall-0.17/debian/not-installed
--- netkit-rwall-0.17/debian/not-installed  1970-01-01 01:00:00.0 
+0100
+++ netkit-rwall-0.17/debian/not-installed  2010-01-15 17:17:00.0 
+0100
@@ -0,0 +1 @@
+debian/tmp/usr/share/man/man8/rwalld.8
diff -Nru netkit-rwall-0.17/debian/patches/define-salen.patch 
netkit-rwall-0.17/debian/patches/define-salen.patch
--- netkit-rwall-0.17/debian/patches/define-salen.patch 1970-01-01 
01:00:00.0 +0100
+++ netkit-rwall-0.17/debian/patches/define-salen.patch 2010-01-15 
17:17:00.0 +0100
@@ -0,0 +1,17 @@
+Description: Define initial value for salen
+Author: Herbert Xu  (presumably)
+Date: 1999-11-03
+Last-Update: 2018-11-25
+
+--- a/rpc.rwalld/rwalld.c
 b/rpc.rwalld/rwalld.c
+@@ -78,8 +78,8 @@
+ {
+   SVCXPRT *transp;
+   int s;
+-  socklen_t salen;
+   struct sockaddr_in sa;
++  socklen_t salen = sizeof(sa);
+ int sock = 0;
+ int proto = 0;
+ 
diff -Nru netkit-rwall-0.17/debian/patches/fix-typo.patch 
netkit-rwall-0.17/debian/patches/fix-typo.patch
--- netkit-rwall-0.17/debian/patches/fix-typo.patch 1970-01-01 
01:00:00.0 +0100
+++ netkit-rwall-0.17/debian/patches/fix-typo.patch 2010-01-15 
17:17:00.0 +0100
@@ -0,0 +1,16 @@
+Description: Fix typo in manpage
+Author: A. Costa" 
+Bug-Debian: https://bugs.debian.org/432058
+Last-Update: 2018-11-25
+
+--- a/rwall/rwall.1
 b/rwall/rwall.1
+@@ -63,7 +63,7 @@
+ .It rwall: RPC: Port mapper failure - RPC: Timed out
+ The remote host is not running the portmapper (see
+ .Xr portmap 8 ),
+-and cannot accomodate any RPC-based services.  The host may be down.
++and cannot accommodate any RPC-based services.  The host may be down.
+ .El
+ .Sh SEE ALSO
+ .Xr wall 1 ,
diff -Nru netkit-rwall-0.17/debian/patches/series 
netkit-rwall-0.17/debian/patches/series
--- netkit-rwall-0.17/debian/patches/series 1970-01-01 01:00:00.0 
+0100
+++ netkit-rwall-0.17/debian/patches/series 2010-01-15 17:17:00.0 
+0100
@@ -0,0 +1,3 @@
+define-salen.patch
+fix-typo.patch
+use-cmake-as-buildsystem.patch
diff -Nru netkit-rwall-0.17/debian/patches/use-cmake-as-buildsystem.patch 
netkit-rwall-0.17/debian/patches/use-cmake-as-buildsystem.patch
--- netkit-rwall-0.17/debian/patches/use-cmake-as-buildsystem.patch 
1970-01-01 01:00:00.0 +0100
+++ netkit-rwall-0.17/debian/patches/use-cmake-as-buildsystem.patch 
2010-01-15 17:17:00.0 +0100
@@ -0,0 +1,102 @@
+Description: Use cmake as build system
+Author: Christoph Biedl 
+Bug-Debian: https://bugs.debian.org/912129
+Last-Update: 2018-11-25
+
+--- /dev/null
 b/CMakeLists.txt
+@@ -0,0 +1,9 @@
++cmake_minimum_required(VERSION 3.7)
++project(netkit-rwall)
++
++set(BIN_DIR "${CMAKE_INSTALL_PREFIX}/bin")
++set(SBIN_DIR "${CMAKE_INSTALL_PREFIX}/sbin")
++set(MAN_DIR "${CMAKE_INSTALL_PREFIX}/share/man")
++
++add_subdirectory(rpc.rwalld)
++add_subdirectory(rwall)
+--- /dev/null
 b/rpc.rwalld/CMakeLists.txt
+@@ -0,0 +1,43 @@
++
++include_directories(
++BEFORE
++${CMAKE_CURRENT_BINARY_DIR}
++)
++
++set(
++RWALLX
++${CMAKE_CURRENT_SOURCE_DIR}/../include/rpcsvc/rwall.x
++)
++
++add_executable(
++rpc.rwalld
++daemon.c
++rwalld.c
++rwall.h
++)
++install(
++TARGETS rpc.rwalld
++DESTINATION ${SBIN_DIR}
++)
++
++add_custom_command(
++COMMENT "Creating rwall.h"
++OUTPUT rwall.h
++COMMAND rpcgen
++ARGS
++-h
++-o rwall.h
++${RWALLX}
++DEPENDS ${RWALLX}
++)
++
++install(
++FILES rpc.rwalld.8
++DESTINATION ${MAN_DIR}/man8/
++)
++install(
++CODE "execute_process( \
++COMMAND ${CMAKE_COMMAND} -E create_symlink \
++rpc.rwalld.8 \$ENV{DESTDIR}${MAN_DIR}/man8/rwalld.8 \
++)"
++)
+--- /dev/null
 b/rwall/CMakeLists.txt
+@@ -0,0 +1,36 @@
++
++include_directories(
++BEFORE
++${CMAKE_CURRENT_BINARY_DIR}
++)
++
++set(
++RWALLX
++${CMAKE_CURRENT_SOURCE_DIR}/../include/rpcsvc/rwall.x
++)
++
++

Bug#912127: netkit-rsh misses the generator for configure

[Christoph Biedl]

tags -1 patch
user debian-rele...@lists.debian.org
usertags -1 + bsp-2018-12-ch-bern
thanks

Find attached the fix for netkit-rsh.

For a full explanation, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911154#44

Regards,

Christoph
diff -Nru netkit-rsh-0.17/debian/compat netkit-rsh-0.17/debian/compat
--- netkit-rsh-0.17/debian/compat   2018-03-10 12:09:02.0 +0100
+++ netkit-rsh-0.17/debian/compat   2018-03-10 12:09:02.0 +0100
@@ -1 +1 @@
-9
+10
diff -Nru netkit-rsh-0.17/debian/control netkit-rsh-0.17/debian/control
--- netkit-rsh-0.17/debian/control  2018-03-10 12:09:02.0 +0100
+++ netkit-rsh-0.17/debian/control  2018-03-10 12:09:02.0 +0100
@@ -3,7 +3,7 @@
 Priority: extra
 Maintainer: Alberto Gonzalez Iniesta 
 Standards-Version: 3.8.4
-Build-Depends: debhelper (>= 7), libpam-dev
+Build-Depends: debhelper (>= 10~), libpam-dev, cmake
 
 Package: rsh-client
 Architecture: any
diff -Nru netkit-rsh-0.17/debian/not-installed 
netkit-rsh-0.17/debian/not-installed
--- netkit-rsh-0.17/debian/not-installed1970-01-01 01:00:00.0 
+0100
+++ netkit-rsh-0.17/debian/not-installed2018-03-10 12:09:02.0 
+0100
@@ -0,0 +1,6 @@
+usr/bin/rexec
+usr/share/man/man1/rexec.1
+usr/share/man/man8/in.rlogind.8
+usr/share/man/man8/rexecd.8
+usr/share/man/man8/rlogind.8
+usr/share/man/man8/rshd.8
diff -Nru netkit-rsh-0.17/debian/patches/debian-changes-0.17-17.patch 
netkit-rsh-0.17/debian/patches/debian-changes-0.17-17.patch
--- netkit-rsh-0.17/debian/patches/debian-changes-0.17-17.patch 2018-03-10 
12:09:02.0 +0100
+++ netkit-rsh-0.17/debian/patches/debian-changes-0.17-17.patch 2018-03-10 
12:09:02.0 +0100
@@ -2,95 +2,17 @@
 Author: Alberto Gonzalez Iniesta 
 Last-Update: 2018-03-10
 
 netkit-rsh-0.17.orig/configure
-+++ netkit-rsh-0.17/configure
-@@ -200,64 +200,6 @@ rm -f __conftest*
- 
- ##
- 
--echo -n 'Checking for ncurses... '
--cat <__conftest.c
--#include 
--#include 
--#ifndef KEY_DOWN
--syntax error. /* not ncurses */
--#endif
--int main() {
--endwin();
--return 0;
--}
--
--EOF
--if (
--  $CC $CFLAGS  __conftest.c -lncurses -o __conftest || exit 1
--   ) >/dev/null 2>&1; then
--echo 'yes'
--NCURSES=1
--else
--if (
--  $CC $CFLAGS -I/usr/include/ncurses __conftest.c -lncurses -o 
__conftest || exit 1
--   ) >/dev/null 2>&1; then
--echo '-I/usr/include/ncurses'
--CFLAGS="$CFLAGS -I/usr/include/ncurses"
--NCURSES=1
--else
--echo 'no'
--fi
--fi
--
--if [ x$NCURSES != x ]; then
--LIBTERMCAP=-lncurses
--else
--echo -n 'Checking for traditional termcap... '
--cat <__conftest.c
--#include 
--#include 
--int main() {
--tgetent(NULL, NULL); return 0;
--}
--
--EOF
--if (
--  $CC $CFLAGS  __conftest.c -ltermcap -o __conftest || exit 1
--   ) >/dev/null 2>&1; then
--echo '-ltermcap'
--LIBTERMCAP=-ltermcap
--else
--echo 'not found'
--echo 'This package needs termcap to run.'
--rm -f __conftest*
--exit
--fi
--fi
--rm -f __conftest*
--
--##
--
- echo -n 'Checking for GNU libc... '
- cat <__conftest.c
- #include 
 netkit-rsh-0.17.orig/rcp/Makefile
-+++ netkit-rsh-0.17/rcp/Makefile
-@@ -7,7 +7,7 @@ rcp: rcp.o
-   $(CC) $(LDFLAGS) $^ $(LIBS) -o $@
- 
- install: rcp
--  install -s -o root -m$(SUIDMODE) rcp $(INSTALLROOT)$(BINDIR)
-+  install -o root -m$(SUIDMODE) rcp $(INSTALLROOT)$(BINDIR)
-   install -m$(MANMODE) rcp.1 $(INSTALLROOT)$(MANDIR)/man1
- 
- clean:
 netkit-rsh-0.17.orig/rcp/pathnames.h
-+++ netkit-rsh-0.17/rcp/pathnames.h
+--- a/rcp/pathnames.h
 b/rcp/pathnames.h
 @@ -37,4 +37,4 @@
  #include 
  
  #define   _PATH_CP"/bin/cp"
 -#define   _PATH_RSH   "/usr/bin/rsh"
 +#define   _PATH_RSH   "/usr/bin/netkit-rsh"
 netkit-rsh-0.17.orig/rcp/rcp.c
-+++ netkit-rsh-0.17/rcp/rcp.c
-@@ -50,6 +50,9 @@ char rcsid[] = "$Id: rcp.c,v 1.15 2000/0
+--- a/rcp/rcp.c
 b/rcp/rcp.c
+@@ -50,6 +50,9 @@
  #include 
  #include 
  #include 
@@ -100,7 +22,7 @@
  #include 
  #include 
  #include 
-@@ -64,6 +67,7 @@ char rcsid[] = "$Id: rcp.c,v 1.15 2000/0
+@@ -64,6 +67,7 @@
  #include 
  #include 
  #include 
@@ -108,7 +30,7 @@
  #include "pathnames.h"
  
  #define   OPTIONS "dfprt"
-@@ -90,7 +94,7 @@ static void verifydir(const char *cp);
+@@ -90,7 +94,7 @@
  static int okname(const char *cp0);
  static int susystem(const char *s);
  static void source(int argc, char *argv[]);
@@ -117,7 +39,7 @@
  static void sink(int argc, char *argv[]);
  static BUF *allocbuf(BUF *bp, int fd, int blksize);
  static void nospace(void);
-@@ -262,9 +266,15 @@ toremote(const char *targ, int argc, cha
+@@ -262,9 +266,15 @@
nospace();
(void)snprintf(bp, len, "%s -t %s", cmd, t

Bug#912128: netkit-rusers misses the generator for configure

[Christoph Biedl]

tags -1 patch
user debian-rele...@lists.debian.org
usertags -1 + bsp-2018-12-ch-bern
thanks

Find attached the fix for netkit-rusers.

For a full explanation, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911154#44

Regards,

Christoph

diff -Nru netkit-rusers-0.17/debian/control netkit-rusers-0.17/debian/control
--- netkit-rusers-0.17/debian/control   2018-10-23 17:37:54.0 +0200
+++ netkit-rusers-0.17/debian/control   2018-10-23 17:37:54.0 +0200
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Alberto Gonzalez Iniesta 
 Standards-Version: 4.2.1
-Build-Depends: debhelper (>= 11)
+Build-Depends: debhelper (>= 11), cmake
 
 Package: rusersd
 Architecture: any
diff -Nru netkit-rusers-0.17/debian/not-installed 
netkit-rusers-0.17/debian/not-installed
--- netkit-rusers-0.17/debian/not-installed 1970-01-01 01:00:00.0 
+0100
+++ netkit-rusers-0.17/debian/not-installed 2018-10-23 17:37:54.0 
+0200
@@ -0,0 +1,3 @@
+usr/bin/rup
+usr/share/man/man1/rup.1
+usr/share/man/man8/rusersd.8
diff -Nru netkit-rusers-0.17/debian/patches/pre-2018-debian-changes.patch 
netkit-rusers-0.17/debian/patches/pre-2018-debian-changes.patch
--- netkit-rusers-0.17/debian/patches/pre-2018-debian-changes.patch 
2018-10-23 17:37:54.0 +0200
+++ netkit-rusers-0.17/debian/patches/pre-2018-debian-changes.patch 
2018-10-23 17:37:54.0 +0200
@@ -7,9 +7,9 @@
 ---
 Last-Update: 2018-10-23
 
 netkit-rusers-0.17.orig/rpc.rusersd/Makefile
-+++ netkit-rusers-0.17/rpc.rusersd/Makefile
-@@ -18,7 +18,7 @@ RPCGEN=rpcgen
+--- a/rpc.rusersd/Makefile
 b/rpc.rusersd/Makefile
+@@ -18,7 +18,7 @@
  # the clean target.
  RUSERSX=/usr/include/rpcsvc/rusers.x
  
@@ -18,9 +18,9 @@
$(CC) $(LDFLAGS) $^ $(LIBS) -o $@
  
  install: rusersd
 netkit-rusers-0.17.orig/rpc.rusersd/rusers_proc.c
-+++ netkit-rusers-0.17/rpc.rusersd/rusers_proc.c
-@@ -31,7 +31,7 @@ char rp_rcsid[] =
+--- a/rpc.rusersd/rusers_proc.c
 b/rpc.rusersd/rusers_proc.c
+@@ -31,7 +31,7 @@
  
  #include 
  #include 
@@ -29,7 +29,7 @@
  #include 
  #include 
  #include 
-@@ -217,7 +217,7 @@ rusers_num(void *ign1, struct svc_req *i
+@@ -217,7 +217,7 @@
struct utmp *uptr;
(void)ign1;
(void)ign2;
@@ -38,29 +38,9 @@
  /* only use entries with both name and line fields */
  
setutent();
 netkit-rusers-0.17.orig/rup/Makefile
-+++ netkit-rusers-0.17/rup/Makefile
-@@ -7,8 +7,6 @@ ifeq ($(USE_GLIBC),1)
- CFLAGS += -DGNU_LIBC -D_GNU_SOURCE
- endif
- 
--CFLAGS += -I.
--
- #RPCGEN=../../netkit-base/rpcgen/rpcgen
- RPCGEN=rpcgen
- 
-@@ -16,7 +14,7 @@ RPCGEN=rpcgen
- # the clean target.
- RSTATX=/usr/include/rpcsvc/rstat.x
- 
--rup: rup.o rstat_xdr.o err.o
-+rup: rup.o rstat_xdr.o
-   $(CC) $(LDFLAGS) $^ $(LIBS) -o $@
- 
- rup.o: ../version.h
 netkit-rusers-0.17.orig/rup/err.c
-+++ netkit-rusers-0.17/rup/err.c
-@@ -6,6 +6,7 @@ char err_rcsid[] =
+--- a/rup/err.c
 b/rup/err.c
+@@ -6,6 +6,7 @@
"$Id: err.c,v 1.1 1997/04/05 22:13:31 dholland Exp $";
  
  #include 
@@ -68,9 +48,9 @@
  #include 
  #include 
  
 netkit-rusers-0.17.orig/rup/rup.c
-+++ netkit-rusers-0.17/rup/rup.c
-@@ -256,7 +256,7 @@ onehost(const char *host)
+--- a/rup/rup.c
 b/rup/rup.c
+@@ -256,7 +256,7 @@
memset(&host_stat, 0, sizeof(host_stat));
if (clnt_call(rstat_clnt, RSTATPROC_STATS, 
  (xdrproc_t) xdr_void, NULL, 
@@ -79,9 +59,9 @@
  foo) != RPC_SUCCESS) 
{
warnx("%s",  clnt_sperror(rstat_clnt, host));
 netkit-rusers-0.17.orig/rusers/rusers.c
-+++ netkit-rusers-0.17/rusers/rusers.c
-@@ -44,6 +44,7 @@ char rusers_rcsid[] =
+--- a/rusers/rusers.c
 b/rusers/rusers.c
+@@ -44,6 +44,7 @@
  #include 
  #include 
  #include 
@@ -89,7 +69,7 @@
  
  #include "../version.h"
  
-@@ -237,7 +238,7 @@ onehost(char *host)
+@@ -237,7 +238,7 @@
memset(&up, 0, sizeof(up));
memset(&addr, 0, sizeof(addr));
if (clnt_call(rusers_clnt, RUSERSPROC_NAMES, (xdrproc_t)xdr_void, NULL,
diff -Nru netkit-rusers-0.17/debian/patches/series 
netkit-rusers-0.17/debian/patches/series
--- netkit-rusers-0.17/debian/patches/series2018-10-23 17:37:54.0 
+0200
+++ netkit-rusers-0.17/debian/patches/series2018-10-23 17:37:54.0 
+0200
@@ -1,2 +1,4 @@
 pre-2018-debian-changes.patch
 system-headers-location.patch
+use-cmake-as-buildsystem.patch
+use-cmake-as-buildsystem-debian-extras.patch
diff -Nru netkit-rusers-0.17/debian/patches/system-headers-location.patch 
netkit-rusers-0.17/debian/patches/system-headers-location.patch
--- netkit-rusers-0.17/debian/patches/system-headers-location.patch 
2018-10-23 17:37:54.0 +0200
+++ netkit-rusers-0.17/debian/patches/system-headers-location.patch 
2018-10-23 17:37:54.0 +0200
@@ -1,55 +1,11 @@
-Index: netkit-rusers/rpc.rusersd/Makefile
-===
 netkit-rusers.orig/rpc.rus

Bug#912124: netkit-bootparamd misses the generator for configure

[Christoph Biedl]

tags -1 patch
user debian-rele...@lists.debian.org
usertags -1 + bsp-2018-12-ch-bern
thanks

Find attached the fix for netkit-bootparamd.

For a full explanation, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911154#44

Additional remarks:

* Bogus debian/bootparams.5 was removed
* Consider restricting architecture to linux-*

Christoph
diff -Nru netkit-bootparamd-0.17/debian/bootparamd.dirs 
netkit-bootparamd-0.17/debian/bootparamd.dirs
--- netkit-bootparamd-0.17/debian/bootparamd.dirs   2018-12-05 
19:20:47.0 +0100
+++ netkit-bootparamd-0.17/debian/bootparamd.dirs   1970-01-01 
01:00:00.0 +0100
@@ -1,5 +0,0 @@
-etc
-usr/sbin
-usr/share/doc/bootparamd
-usr/share/man/man5
-usr/share/man/man8
diff -Nru netkit-bootparamd-0.17/debian/bootparamd.install 
netkit-bootparamd-0.17/debian/bootparamd.install
--- netkit-bootparamd-0.17/debian/bootparamd.install1970-01-01 
01:00:00.0 +0100
+++ netkit-bootparamd-0.17/debian/bootparamd.install2008-03-21 
19:02:52.0 +0100
@@ -0,0 +1,2 @@
+
+debian/bootparams   etc/
diff -Nru netkit-bootparamd-0.17/debian/bootparams.5 
netkit-bootparamd-0.17/debian/bootparams.5
--- netkit-bootparamd-0.17/debian/bootparams.5  2018-12-05 19:20:47.0 
+0100
+++ netkit-bootparamd-0.17/debian/bootparams.5  1970-01-01 01:00:00.0 
+0100
@@ -1,68 +0,0 @@
-.\" bootparams - bootparamd(8) configuration file
-.\" Copyright (c) 1999 by Martin Schulze 
-.\" 
-.\" 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; either version 2 of the License, or
-.\" (at your option) any later version.
-.\" 
-.\" 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 General Public License
-.\" along with this program; if not, write to the Free Software
-.\" Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111, USA.
-.\"
-.TH BOOTPARAMS 5 "24 October 1999" "" "Linux System Administration"
-.SH NAME
-bootparams \- bootparamd(8) configuration file
-.SH DESCRIPTION
-The
-.I bootparams
-file is the main configuration file for the
-.BR bootparamd (8)
-that answers to boot parameter requests.  This daemon is used by old
-HP9000 boxes, for example.
-.SH FORMAT
-The format of this file is very easy.  Each line starting with a hash
-sign (`#') is considered a comment.  All other lines look like:
-
-.IP
-.nf
-client id=server:path
-.fi
-.LP
-
-Where
-.I client
-is the name of the client machine,
-.I server
-is the hostname, fqdn or ip address of the server and
-.I path
-is the path to the resource in question.  Fields are separated by
-whitespace characters.  Each entry has its own line.
-
-You may break up lines by using the backslash (`\\') character.  In
-that case you will have to use a whitespace character before the
-backslash or the server will run into an endless loop.  You may use
-whitespace characters at the beginning of a new line.
-.SH EXAMPLES
-This will configure the host kataja:
-.IP
-.nf
-kataja root=finlandia:/var/lib/nfs/kataja
-.fi
-.LP
-While this configures the host kuusi, probably using the same scheme:
-.IP
-.nf
-kuusi.infodrom.north.de \\
-   root=finlandia.infodrom.north.de:/var/lib/nfs/kuusi
-.fi
-.LP
-.SH FILES
-.IR /etc/bootparams .
-.SH "SEE ALSO"
-.BR bootparamd (8).
diff -Nru netkit-bootparamd-0.17/debian/compat 
netkit-bootparamd-0.17/debian/compat
--- netkit-bootparamd-0.17/debian/compat2018-12-05 19:20:47.0 
+0100
+++ netkit-bootparamd-0.17/debian/compat2008-03-21 19:02:52.0 
+0100
@@ -1 +1 @@
-6
+10
diff -Nru netkit-bootparamd-0.17/debian/control 
netkit-bootparamd-0.17/debian/control
--- netkit-bootparamd-0.17/debian/control   2018-12-05 19:20:47.0 
+0100
+++ netkit-bootparamd-0.17/debian/control   2008-03-21 19:02:52.0 
+0100
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Alberto Gonzalez Iniesta 
 Standards-Version: 3.7.3
-Build-Depends: debhelper (>= 5)
+Build-Depends: debhelper (>= 10~), cmake
 
 Package: bootparamd
 Architecture: any
diff -Nru netkit-bootparamd-0.17/debian/patches/fix-getopt-return-type.patch 
netkit-bootparamd-0.17/debian/patches/fix-getopt-return-type.patch
--- netkit-bootparamd-0.17/debian/patches/fix-getopt-return-type.patch  
1970-01-01 01:00:00.0 +0100
+++ netkit-bootparamd-0.17/debian/patches/fix-getopt-return-type.patch  
2008-03-21 19:02:52.0 +0100
@@ -0,0 +1,16 @@
+Description: Fixed getopt return type
+Author: Tomas Berndtsson 
+Bug-Debian: https://bugs.debian.org/75806
+Last-Update: 2018-11-25
+
+--- a/rpc.bootparamd/main.c
 b/rpc.bootparamd/main.c
+@@ -37,7 +37,7 @@
+ int s, pid;
+ struct hostent *he;
+ str

Bug#911154: netkit-ntalk misses the generator for configure

[Christoph Biedl]

tags -1 patch
user debian-rele...@lists.debian.org
usertags -1 + bsp-2018-12-ch-bern
thanks

So here we go ...

The files resulting from the conversion to cmake are not as terse as I
hoped they would be. Still, at least for me, this is an improvement
over to several handcrafted rules, especially for any future changes in
the Debian build system.

This goes far beyond a usual NMU, so several more remarks:


## For upstream

The primary goal was to provide a distribution-agnostic replacement
for the specific and fairly limited build system, using cmake. Not
all features have been re-implemented, though.


## For Debian

* Any Patches not in 3.0 (quilt) format were converted accordingly.
  For most packages, this could take a refinement, read: Split the
  single patch into several smaller ones, reflecting the reason for
  each patch.

* Any debhelper compat level below 10 was raised accordingly.

* The debian/rules file was converted to dh style, moving all the
  install logic to other places. Obsolete debian/*dir were removed.

* All modifications to the no-longer used build system files
  (configure, Makefile, */Makefile) were reverted, and hopefully
  re-created by other means. There were several additional
  modifications, install paths and names to most. Some of them were
  re-implemented by modifying CMakeLists.txt - there is a second patch
  then.

* Probably all packagings need some review and further improvement.
  Good starting points are the messages emitted by lintian and gcc.

* Since there are no test suites, there is quite a risk some
  regressions were introduced without noticing. To detect at least the
  worst mistakes, the contents of each created package was compared
  using debdiff, and the flags in the build logs.

* Personally I'd merge the *-ssl src:packages into the related
  plain-text package as they share the same source tarball.


## Outlook

The patches will be release in in three batches:

### Packages maintained by Alberto Gonzalez Iniesta 

* netkit-bootparamd
* netkit-ntalk
* netkit-rsh
* netkit-rusers
* netkit-rwall
* netkit-rwho
* netkit-tftp

Alberto, you'll do me a favour if you could refrain from uploading
for a few days - I'll do some more checks and expect one or two more
things will come up that require an adjustment.

Also, some formatting was done in my personal style. Feel free to apply
your $QUILT_REFRESH_ARGS on top of this.

### Packages by other maintainers

* biff
* bsd-finger

These will be fixed by an NMU

### Packages with an SSL variant

They will have an extra round of review first

* netkit-ftp
* netkit-ftp-ssl
* netkit-telnet
* netkit-telnet-ssl
* linux-ftpd
* linux-ftpd-ssl


## For future reference: Translation of some MCONFIG.in keywords

Not all features have been re-implemented - some like BINDIR and
permissions are hardcoded now.

The following lists those keywords that required some action. Some
statement in to top-level CMakeLists.txt, usually to detect some
libraries. And possible additions to particultar binaries to be built
("targets").

### BSDSIGNAL

Always true

### FN(crypt)

find_library(USE_CRYPT crypt REQUIRED)

target_link_libraries(
...
crypt
)

### FN(forkpty)

target_link_libraries(
...
util
)

### FN(logwtmp)

target_link_libraries(
...
util
)

### FN(snprintf)

Always true


### GLIBC

Always true

set(USE_GLIBC 1)

### LDFLAGS

No-op

### LIBCURSES

find_library(NCURSES lncurses REQUIRED)

target_link_libraries(
...
ncurses
)

Note: Fallback to traditional curses is not supported

### LIBS

No-op

### LIBTERMCAP

find_library(USE_CRYPT lncurses REQUIRED)

target_link_libraries(
...
ncurses
)

Note: Fallback to traditional curses is not supported

### PAM

find_library(USE_PAM pam)

Disabling PAM is not supported

### READLINE

find_library(USE_READLINE readline)

target_link_libraries(
...
readline
)

### SHADOW

No-op as PAM is enabled

Disabling shadow is not supported

### TYPE(socklen_t)

No-op

### YACC

Use yacc. Currently hardcoded, might be refined to use some cmake
logic.


Cheers,

Christoph
diff -Nru netkit-ntalk-0.17/debian/compat netkit-ntalk-0.17/debian/compat
--- netkit-ntalk-0.17/debian/compat 2018-12-05 19:20:49.0 +0100
+++ netkit-ntalk-0.17/debian/compat 2012-06-14 12:54:26.0 +0200
@@ -1 +1 @@
-5
+10
diff -Nru netkit-ntalk-0.17/debian/control netkit-ntalk-0.17/debian/control
--- netkit-ntalk-0.17/debian/control2018-12-05 19:20:49.0 +0100
+++ netkit-ntalk-0.17/debian/control2012-06-14 12:54:26.0 +0200
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Alberto Gonzalez Iniesta 
 Standards-Version: 3.9.3
-Build-Depends: debhelper (>> 7), libncurses-dev, libwrap0-dev
+Build-Depends: debhelper (>> 10~), libncurses-dev, libwrap0-dev, cmake
 
 Package: talk
 Architecture: any
diff -Nru netkit-ntalk-0.17/d

Bug#915692: collectd - Recommends deprecated liblvm2app

[Bastian Blank]

Package: colectd
Version: 5.8.1-1
Severity: serious

liblvm2app is deprecated and will be not longer shipped with Buster.
Please drop it's usage.

Further references are found here:
https://bugzilla.redhat.com/show_bug.cgi?id=1489590
https://github.com/collectd/collectd/issues/2647

Bastian

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

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

Bug#915691: glusterfs-common - Depends on deprecated liblvm2app

[Bastian Blank]

Package: glusterfs-common
Version: 5.1-2
Severity: serious

liblvm2app is deprecated and will be not longer shipped with Buster.
Please drop it's usage.

Further references are found here:
https://bugzilla.redhat.com/show_bug.cgi?id=1489590

Bastian

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

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

Versions of packages glusterfs-common depends on:
pn  attr 
ii  e2fsprogs1.44.4-2
ii  libacl1  2.2.52-3+b1
pn  libacl1-dev  
ii  libaio1  0.3.111-1
ii  libc62.27-8
pn  libibverbs1  
ii  liblvm2app2.22.02.176-4.1
ii  libncurses5  6.1+20181013-1
ii  libncurses6  6.1+20181013-1
ii  libpython2.7 2.7.15-5
ii  libpython3.7 3.7.1-1
pn  librdmacm1   
ii  libreadline7 7.0-5
ii  libsqlite3-0 3.25.3-2
ii  libssl1.11.1.1a-1
ii  libtinfo56.1+20181013-1
ii  libtinfo66.1+20181013-1
pn  libtirpc3
pn  liburcu4 
pn  liburcu6 
ii  libuuid1 2.32.1-0.1
ii  libxml2  2.9.4+dfsg1-7+b2
ii  psmisc   23.2-1
ii  python   2.7.15-3
ii  python3  3.6.7-1
pn  python3-jwt  
pn  python3-prettytable  
ii  python3-requests 2.20.0-2
pn  xfsprogs 
ii  zlib1g   1:1.2.11.dfsg-1

glusterfs-common recommends no packages.

glusterfs-common suggests no packages.

Bug#915690: kvpm - Depends on deprecated liblvm2app

[Bastian Blank]

Package: kvpm
Version: 0.9.10-1.1
Severity: serious

liblvm2app is deprecated and will be not longer shipped with Buster.
Please drop it's usage.

Further references are found here:
https://bugzilla.redhat.com/show_bug.cgi?id=1489590

Bastian

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

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

Versions of packages kvpm depends on:
ii  libblkid1   2.32.1-0.1
ii  libc6   2.27-8
ii  libdevmapper1.02.1  2:1.02.145-4.1
ii  libgcc1 1:8.2.0-9
pn  libkf5configcore5   
pn  libkf5configgui5
pn  libkf5configwidgets5
pn  libkf5coreaddons5   
pn  libkf5i18n5 
pn  libkf5kdelibs4support5  
pn  libkf5widgetsaddons5
pn  libkf5xmlgui5   
ii  liblvm2app2.2   2.02.176-4.1
ii  libparted2  3.2-23
ii  libqt5core5a5.11.2+dfsg-7
ii  libqt5gui5  5.11.2+dfsg-7
ii  libqt5widgets5  5.11.2+dfsg-7
ii  libstdc++6  8.2.0-9

Versions of packages kvpm recommends:
pn  dosfstools 
ii  e2fsprogs  1.44.4-2
pn  jfsutils   
pn  ntfs-3g
pn  reiserfsprogs  
pn  xfsprogs   

Versions of packages kvpm suggests:
ii  btrfs-progs   4.17-1
ii  btrfs-tools   4.15.1-2
pn  reiser4progs  

Bug#915689: prevent from migrating to testing

[Aron Xu]

Package: rng-tools
Version: 5-1
Severity: serious
Tags: sid

We need to prevent this version of rng-tools from migrating to testing
before finding a solution of coordinating with the rng-tools5 package.

Aron

Bug#915108: marked as done (caffe: FTBFS on mips and mips64el: test failures)

[Debian Bug Tracking System]

Your message dated Thu, 06 Dec 2018 05:04:25 +
with message-id 
and subject line Bug#915108: fixed in caffe 1.0.0+git20180821.99bd997-2
has caused the Debian Bug report #915108,
regarding caffe: FTBFS on mips and mips64el: test failures
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.)


-- 
915108: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915108
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: caffe
Version: 1.0.0+git20180821.99bd997-1
Severity: serious
Tags: ftbfs

Hi,

Your package failed to build on mips:

[  FAILED  ] 2 tests, listed below:
[  FAILED  ] AdaDeltaSolverTest/0.TestSnapshot, where TypeParam = 
caffe::CPUDevice
[  FAILED  ] AdaDeltaSolverTest/1.TestSnapshotShare, where TypeParam = 
caffe::CPUDevice

and again on mips on a second try:

[  FAILED  ] 3 tests, listed below:
[  FAILED  ] AdaDeltaSolverTest/0.TestSnapshotShare, where TypeParam = 
caffe::CPUDevice
[  FAILED  ] AdaDeltaSolverTest/0.TestSnapshot, where TypeParam = 
caffe::CPUDevice
[  FAILED  ] 
AdaDeltaSolverTest/0.TestLeastSquaresUpdateWithEverythingAccumShare, where 
TypeParam = caffe::CPUDevice

and on mips64el:

[  FAILED  ] 2 tests, listed below:
[  FAILED  ] AdaDeltaSolverTest/0.TestAdaDeltaLeastSquaresUpdateWithEverything, 
where TypeParam = caffe::CPUDevice
[  FAILED  ] AdaDeltaSolverTest/1.TestSnapshot, where TypeParam = 
caffe::CPUDevice

mipsel built fine. Perhaps the different buildds are relevant, as some
mips* ones lack an FPU.

Cheers,
Emilio

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (800, 'unstable'), (700, 'experimental'), (650, 'testing'), (500, 
'unstable-debug'), (500, 'testing-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: caffe
Source-Version: 1.0.0+git20180821.99bd997-2

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

Debian distribution maintenance software
pp.
Mo Zhou  (supplier of updated caffe 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, 06 Dec 2018 04:24:33 +
Source: caffe
Binary: caffe-cpu caffe-tools-cpu libcaffe-cpu1 libcaffe-cpu-dev 
python3-caffe-cpu caffe-doc
Architecture: source
Version: 1.0.0+git20180821.99bd997-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Mo Zhou 
Description:
 caffe-cpu  - Fast, open framework for Deep Learning (Meta)
 caffe-doc  - Caffe's doxygen docs and examples
 caffe-tools-cpu - Tools for fast, open framework for Deep Learning (CPU_ONLY)
 libcaffe-cpu-dev - development files for Caffe (CPU_ONLY)
 libcaffe-cpu1 - library of Caffe, deep learning framework (CPU_ONLY)
 python3-caffe-cpu - Python3 interface of Caffe (CPU_ONLY)
Closes: 915108
Changes:
 caffe (1.0.0+git20180821.99bd997-2) unstable; urgency=medium
 .
   * Ignore precision issue on mips* machines which may lack an FPU.
 (Closes: #915108)
Checksums-Sha1:
 47976fa495c7c10eeeadb967e080a3113840a4cb 3072 
caffe_1.0.0+git20180821.99bd997-2.dsc
 f5ccfc44ea440f9decf425bf9090cb26755fa6a9 14980 
caffe_1.0.0+git20180821.99bd997-2.debian.tar.xz
 a6953b473649bf733c4dd23b60f2818dc77a92c8 22198 
caffe_1.0.0+git20180821.99bd997-2_source.buildinfo
Checksums-Sha256:
 c607d6c53b0da32a1c73de17720dbb4f16e5fec08cc56699f55564d05cf57df6 3072 
caffe_1.0.0+git20180821.99bd997-2.dsc
 6409acc19ad2a1a6c62ed0e781e97c8bc777236b781476eb4051b38e0f65c508 14980 
caffe_1.0.0+git20180821.99bd997-2.debian.tar.xz
 07ab4310ecedb2d0ebf39463633958d2b65df8f7d3abbda97da9866c8bbf288a 22198 
caffe_1.0.0+git20180821.99bd997-2_source.buildinfo
Files:
 3757864dcb95a6de3f240ae275430f72 3072 science optional 
caffe_1.0.0+git20180821.99bd997-2.dsc
 059a80a8b9141faeb4c3bea6d0919c44 14980 science optional 
caffe_1.0.0+git20180821.99

Bug#915640: marked as done (spyder-reports FTBFS with spyder 3.3.2+dfsg1-1)

[Debian Bug Tracking System]

Your message dated Thu, 06 Dec 2018 04:50:03 +
with message-id 
and subject line Bug#915640: fixed in spyder-reports 0.1.1-3
has caused the Debian Bug report #915640,
regarding spyder-reports FTBFS with spyder 3.3.2+dfsg1-1
to be marked as done.

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

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


-- 
915640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915640
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: spyder-reports
Version: 0.1.1-1
Severity: serious
Tags: ftbfs

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

...
   dh_auto_test -O--buildsystem=pybuild
I: pybuild base:217: cd 
/build/1st/spyder-reports-0.1.1/.pybuild/cpython3_3.6_spyder-reports/build; 
python3.6 -m pytest 
= test session starts ==
platform linux -- Python 3.6.7, pytest-3.10.1, py-1.7.0, pluggy-0.8.0 -- 
/usr/bin/python3.6
cachedir: .pytest_cache
PyQt5 5.11.3 -- Qt runtime 5.11.2 -- Qt compiled 5.11.2
rootdir: /build/1st/spyder-reports-0.1.1, inifile: setup.cfg
plugins: xvfb-1.0.0, qt-2.3.1, cov-2.6.0
collecting ... 
 ERRORS 
 ERROR collecting 
.pybuild/cpython3_3.6_spyder-reports/build/spyder_reports/tests/test_plugin.py 
ImportError while importing test module 
'/build/1st/spyder-reports-0.1.1/.pybuild/cpython3_3.6_spyder-reports/build/spyder_reports/tests/test_plugin.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
spyder_reports/__init__.py:11: in 
from .reportsplugin import ReportsPlugin
spyder_reports/reportsplugin.py:34: in 
from spyder.utils.programs import TEMPDIR
E   ImportError: cannot import name 'TEMPDIR'
=== 1 error in 0.47 seconds 
E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: cd 
/build/1st/spyder-reports-0.1.1/.pybuild/cpython3_3.6_spyder-reports/build; 
python3.6 -m pytest 
dh_auto_test: pybuild --test --test-pytest -i python{version} -p "3.6 3.7" 
returned exit code 13
make: *** [debian/rules:10: build] Error 25
--- End Message ---
--- Begin Message ---
Source: spyder-reports
Source-Version: 0.1.1-3

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

Debian distribution maintenance software
pp.
Drew Parsons  (supplier of updated spyder-reports 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: Thu, 06 Dec 2018 12:13:54 +0800
Source: spyder-reports
Binary: python3-spyder-reports
Architecture: source
Version: 0.1.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Drew Parsons 
Description:
 python3-spyder-reports - plugin to render scientific reports within the Spyder 
IDE
Closes: 915640
Changes:
 spyder-reports (0.1.1-3) unstable; urgency=medium
 .
   * Team upload.
   * Use versioned Build-Depends: python3-spyder (>= 3.3.2)
 to support debian patch 0002-set-TEMPDIR.patch. Closes: #915640.
Checksums-Sha1:
 ce9ee20ea8db16a56fcdab559a6ac8131e0b173f 2421 spyder-reports_0.1.1-3.dsc
 296b598fb75361f8c64894cbc85fbef23ce6082c 3264 
spyder-reports_0.1.1-3.debian.tar.xz
Checksums-Sha256:
 0a9440331942f7454952cbee0a4f424057e1f6c48eadf69ee30f53948623dbd9 2421 
spyder-reports_0.1.1-3.dsc
 805cfb6a765d267196385fe0dd416eeb339a5d3e4bbb132ba08db8429e3cb906 3264 
spyder-reports_0.1.1-3.debian.tar.xz
Files:
 ab4d220e513e18524ab1319e35ead27b 2421 python optional 
spyder-reports_0.1.1-3.dsc
 03bb239a755ea097c9fe2844813777e5 3264 python optional 
spyder-reports_0.1.1-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAlwIpzMACgkQVz7x5L1a
AfozDxAAkJskyaaZYJU5d9M08MpjCYKP5lsp7e/O/cTx6+b3r7ayVFQUNOPDCFYw
YHp431cduBuMnkOYyvM37r2Qs6/hNyQHIdYhoTzT2yS7lDpXA+QJdXB8FSl3TGG7
CF0zGjE7gCyQUj6jol3b7Do32KupVMjUwoBMAP9VJpL4IeQHhFxje6p8/yEtbc+s
qz3lqCLn5AflWwIxzYT9dkE1qhNZh1UFom4/pXlFPezS4h1iwtdvjJNaHWo6LLFR
B0IZloiB1unKeUS8ACIue284sDxLuCeOW+lV7Z6cPxfVKhIsWc+1WP+Zt6ctmXeJ
hiNruQdvvS0lZB7X0g

Bug#915686: src:bmap-tools: FTBFS with Python 3.7 as default

[Logan Rosen]

Package: src:bmap-tools
Version: 3.5-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

bmap-tools fails to build from source with the new Python 3.7 default.
You can see the Ubuntu build failure (which I was able to reproduce in a clean
sid chroot) here. [1]

The tests are failing with this error:
RuntimeError: generator raised StopIteration

Thanks,
Logan

[1] 
https://launchpadlibrarian.net/399583193/buildlog_ubuntu-disco-amd64.bmap-tools_3.5-1_BUILDING.txt.gz

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

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

Bug#914687: lagan: /usr/bin/chaos is already provided by emboss

[Michael Brudno]

Hi Andreas,

Lagan is no longer maintained (has not been for over 10 years). Please
feel free to make any changes necessary. There are a few minor fixes
others have made to make the system more portable: some changes to
make the sort calls more modern, and also renaming one sub-function
that had a name conflict (getline, iirc).

e.g. https://github.com/incertae-sedis/lagan

Best of luck,

Mike
On Tue, Dec 4, 2018 at 2:19 AM Andreas Tille  wrote:
>
> Control: forwarded -1 Michael Brudno 
>
> Hi Michael,
>
> recently the Debian Med team has packaged lagan for official Debian.
> This has uncovered the fact that there is a name space conflict with
> EMBOSS.  This is specifically unfortunate since both packages are
> from the field of bioinformatics and it should be avoided.  (Remark:
> I even think that the choice of /usr/bin/chaos is a bit unfortunate
> in general since it is quite a generic name.)
>
> In Debian the package that has occupied a name first usually wins and
> the other package has to rename.  In this case I also think that EMBOSS
> is quite famous and has lots of users (according to Debian popularity
> contest which is measuring the number of users of a package).  Thus we
> need to choose a different name for chaos provided by lagan.
>
> For the moment I would solve this bug in Debian by moving /usr/bin/chaos
> to /usr/lib/lagan/bin/chaos and provide a symlink /usr/bin/lagan_chaos.
> I will document this in /usr/share/doc/lagan/README.Debian.
>
> I would consider it a good idea if you would remove chaos in your
> distribution as well since this name space conflict might happen also
> for other users and it might create some confusion you probably want
> to avoid.
>
> Kind regards and thanks for providing lagan as Free Software
>
>Andreas.
>
> On Mon, Nov 26, 2018 at 11:03:47AM +0100, Andreas Beckmann wrote:
> > Package: lagan
> > Version: 2.0-2
> > 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/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
> >
> > >From the attached log (scroll to the bottom...):
> >
> >   Preparing to unpack .../archives/lagan_2.0-2_amd64.deb ...
> >   Unpacking lagan (2.0-2) ...
> >   dpkg: error processing archive 
> > /var/cache/apt/archives/lagan_2.0-2_amd64.deb (--unpack):
> >trying to overwrite '/usr/bin/chaos', which is also in package emboss 
> > 6.6.0+dfsg-7
> >   dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
> >   Errors were encountered while processing:
> >/var/cache/apt/archives/lagan_2.0-2_amd64.deb
>
> --
> http://fam-tille.de

Bug#914953: [3dprinter-general] Bug#914953: FTBFS with Python 3.7 on many architectures

[Mattia Rizzolo]

On Wed, Dec 05, 2018 at 07:50:30PM +0100, Gregor Riepl wrote:
> I'm inclined to drop the symbols file altogether, as it really doesn't add any
> value.

I beg to disagree, I tend to find symbols tracking quite important, and
helped detecting and/or demostrating several ABI breakages in the past
where upstream did not even realize they did.  Or symbols that changes
due to changes in some other libraries (recently I sheparded a library
that moved vtk6 to vtk7, breaking ABI; not noticed because it didn't
have a symbols file), etc etc.

> The correct solution would be to use -fvisibility=hidden [1] and
> properly tag symbols for the public API of libArcus and libSavitar.

Yes, that would be the best indeed.  It's quite sad that TTBOMK symbols
visibility is not really standardized and it's a copiler-dependant thing
... :(


I suspect that many optional symbols on the symbols file of this package
could be squashed with a regex, but alas I can't help with that now
since I'll be soon leaving for a 2-weeks travel and I don't think I
would ever find the time to also look at this.  Anyway, look at the gdcm
repo for an idea of what I'm talking about.


Anyway, the problem that dpkg-gensymbols is complaining about, it's
because you missed a quote sign in
a4f32173da0f7ab5c173d89fd556f0af242d2deb (didn't you notice this while
test building before asking for sponsorship?).

diff --git a/debian/libarcus3.symbols b/debian/libarcus3.symbols
index 6bc9ef2..d44af1c 100644
--- a/debian/libarcus3.symbols
+++ b/debian/libarcus3.symbols
@@ -4,7 +4,7 @@ libArcus.so.3 libarcus3 #MINVER#
  (c++)"ErrorCollector::AddError(std::__cxx11::basic_string, std::allocator > const&, int, int, 
std::__cxx11::basic_string, std::allocator > 
const&)@Base" 2.3.1
  (c++)"ErrorCollector::~ErrorCollector()@Base" 2.3.1
  (c++|optional)"std::_Hashtable, std::allocator >, std::__detail::_Select1st, 
std::equal_to, std::hash, 
std::__detail::_Mod_range_hashing, std::__detail::_Default_ranged_hash, 
std::__detail::_Prime_rehash_policy, std::__detail::_Hashtable_traits >::_M_insert_unique_node(unsigned long, unsigned long, 
std::__detail::_Hash_node, false>*, unsigned long)@Base" 3.3.0-2~
- (c++|optional)"std::_Hashtable, std::allocator >, std::__detail::_Select1st, 
std::equal_to, std::hash, 
std::__detail::_Mod_range_hashing, std::__detail::_Default_ranged_hash, 
std::__detail::_Prime_rehash_policy, std::__detail::_Hashtable_traits >::_M_insert_unique_node(unsigned int, unsigned int, 
std::__detail::_Hash_node, false>*, unsigned int)@Base 3.3.0-2~
+ (c++|optional)"std::_Hashtable, std::allocator >, std::__detail::_Select1st, 
std::equal_to, std::hash, 
std::__detail::_Mod_range_hashing, std::__detail::_Default_ranged_hash, 
std::__detail::_Prime_rehash_policy, std::__detail::_Hashtable_traits >::_M_insert_unique_node(unsigned int, unsigned int, 
std::__detail::_Hash_node, false>*, unsigned int)@Base" 3.3.0-2~
  (c++|optional)"void std::__cxx11::basic_string, 
std::allocator >::_M_construct(char const*, char const*, 
std::forward_iterator_tag)@Base" 3.3.0-2~
  (c++|optional)"void std::__cxx11::basic_string, 
std::allocator >::_M_construct(char*, char*, 
std::forward_iterator_tag)@Base" 3.3.0-2~
  (c++|optional)"std::_Sp_make_shared_tag::_S_ti()::__tag@Base" 3.3.0-2~


After that my local build failed because I locally export
DPKG_GENSYMBOLS_CHECK_LEVEL=4 and it seems this new symbol is new:

_ZNSt10_HashtableIPKN6google8protobuf10DescriptorESt4pairIKS4_jESaIS7_ENSt8__detail10_Select1stESt8equal_toIS4_ESt4hashIS4_ENS9_18_Mod_range_hashingENS9_20_Default_ranged_hashENS9_20_Prime_rehash_policyENS9_17_Hashtable_traitsILb0ELb0ELb121_M_insert_unique_nodeEmmPNS9_10_Hash_nodeIS7_Lb0EEEm@Base


Anyway, that's yet another std:: function leaked from who knows where,
so nvm that…

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature

Processed: reassign 910008 to ghc, fixed 910008 in 8.4.3+dfsg1-3, affects 910008, reassign 878691 to src:m17n-db ...

[Debian Bug Tracking System]

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

> reassign 910008 ghc 8.4.3+dfsg1-2
Bug #910008 {Done: Clint Adams } [libghc-mtl-dev] 
haskell-mtl: Package libghc-mtl-dev not co-installable with ghc due to file 
conflicts
Bug reassigned from package 'libghc-mtl-dev' to 'ghc'.
No longer marked as found in versions haskell-mtl/2.2.2-2.
No longer marked as fixed in versions ghc/8.4.3+dfsg1-3.
Bug #910008 {Done: Clint Adams } [ghc] haskell-mtl: Package 
libghc-mtl-dev not co-installable with ghc due to file conflicts
Marked as found in versions ghc/8.4.3+dfsg1-2.
> fixed 910008 8.4.3+dfsg1-3
Bug #910008 {Done: Clint Adams } [ghc] haskell-mtl: Package 
libghc-mtl-dev not co-installable with ghc due to file conflicts
Marked as fixed in versions ghc/8.4.3+dfsg1-3.
> affects 910008 + src:haskell-mtl
Bug #910008 {Done: Clint Adams } [ghc] haskell-mtl: Package 
libghc-mtl-dev not co-installable with ghc due to file conflicts
Added indication that 910008 affects src:haskell-mtl
> reassign 878691 src:m17n-db 1.7.0-2
Bug #878691 {Done: Boyuan Yang } [m17n-contrib] please drop 
transitional package m17n-contrib
Bug reassigned from package 'm17n-contrib' to 'src:m17n-db'.
No longer marked as found in versions m17n-db/1.7.0-2.
No longer marked as fixed in versions m17n-db/1.8.0-1.
Bug #878691 {Done: Boyuan Yang } [src:m17n-db] please drop 
transitional package m17n-contrib
Marked as found in versions m17n-db/1.7.0-2.
> fixed 878691 1.8.0-1
Bug #878691 {Done: Boyuan Yang } [src:m17n-db] please drop 
transitional package m17n-contrib
Marked as fixed in versions m17n-db/1.8.0-1.
> tags 878691 + sid buster
Bug #878691 {Done: Boyuan Yang } [src:m17n-db] please drop 
transitional package m17n-contrib
Added tag(s) buster and sid.
> fixed 772554 1.0.27-1~experimental1
Bug #772554 {Done: Jörg Frings-Fürst } 
[src:sane-backends] libsane: epson perfection 1260 no more supported
Marked as fixed in versions sane-backends/1.0.27-1~experimental1.
> notfixed 843497 238
Bug #843497 {Done: Michael Biebl } [systemd] systemd-networkd 
block the shutdown process of my nspawn container
There is no source info for the package 'systemd' at version '238' with 
architecture ''
Unable to make a source version for version '238'
No longer marked as fixed in versions 238.
> fixed 843497 238-1
Bug #843497 {Done: Michael Biebl } [systemd] systemd-networkd 
block the shutdown process of my nspawn container
Marked as fixed in versions systemd/238-1.
> reassign 910417 src:fabulous 0.3.0+dfsg1-4
Bug #910417 {Done: Jonathan Carter } [python3-fabulous-doc] 
python3-fabulous-doc: broken symlink: /usr/share/doc/python3-fabulous-doc/rst 
-> html/_sources
Bug reassigned from package 'python3-fabulous-doc' to 'src:fabulous'.
No longer marked as found in versions fabulous/0.3.0+dfsg1-4.
No longer marked as fixed in versions fabulous/0.3.0+dfsg1-5.
Bug #910417 {Done: Jonathan Carter } [src:fabulous] 
python3-fabulous-doc: broken symlink: /usr/share/doc/python3-fabulous-doc/rst 
-> html/_sources
Marked as found in versions fabulous/0.3.0+dfsg1-4.
> fixed 910417 0.3.0+dfsg1-5
Bug #910417 {Done: Jonathan Carter } [src:fabulous] 
python3-fabulous-doc: broken symlink: /usr/share/doc/python3-fabulous-doc/rst 
-> html/_sources
Marked as fixed in versions fabulous/0.3.0+dfsg1-5.
> reassign 798946 icedtea-netx 1.5.2-1.1
Bug #798946 {Done: Emmanuel Bourg } [icedtea-netx-common] 
javaws binary and desktop file in different packages
Bug reassigned from package 'icedtea-netx-common' to 'icedtea-netx'.
No longer marked as found in versions icedtea-web/1.5.2-1.1.
No longer marked as fixed in versions icedtea-web/1.7.1-1.
Bug #798946 {Done: Emmanuel Bourg } [icedtea-netx] javaws 
binary and desktop file in different packages
Marked as found in versions icedtea-web/1.5.2-1.1.
> fixed 798946 1.7.1-1
Bug #798946 {Done: Emmanuel Bourg } [icedtea-netx] javaws 
binary and desktop file in different packages
Marked as fixed in versions icedtea-web/1.7.1-1.
> fixed 762141 0.17.1.14-1
Bug #762141 {Done: Jonathan Dowland } [trash-cli] trash-cli: 
trash-list crash piping to less
Marked as fixed in versions trash-cli/0.17.1.14-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
762141: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762141
772554: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772554
798946: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798946
843497: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843497
878691: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878691
910008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910008
910417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910417
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#915661: marked as done (context: upgrade of context hangs on "Pregenerating ConTeXt MarkIV format.")

[Debian Bug Tracking System]

Your message dated Thu, 6 Dec 2018 11:08:47 +0900
with message-id <20181206020847.gb5...@bulldog.preining.info>
and subject line Re: Bug#915661: context: upgrade of context hangs on 
"Pregenerating ConTeXt MarkIV format."
has caused the Debian Bug report #915661,
regarding context: upgrade of context hangs on "Pregenerating ConTeXt MarkIV 
format."
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.)


-- 
915661: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915661
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: context
Version: 2018.04.04.20181118-1
Severity: grave
Justification: renders package unusable

When upgrading context:

Setting up context (2018.04.04.20181118-1) ...
Running mtxrun --generate. This may take some time... done.
Pregenerating ConTeXt MarkIV format. This may take some time... 

This is due to:

root  9619  9618  0 17:36 pts/400:00:00 luatex --ini 
--lua=/usr/share/texmf/tex/context/base/mkiv/luat-cod.lua 
/usr/share/texmf/tex/context/base/mkiv/cont-en.mkiv dump

which started 20 minutes ago and has no activity according to
"strace -p 9619".

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

Kernel: Linux 4.18.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=POSIX 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages context depends on:
ii  lmodern   2.004.5-5
ii  ruby  1:2.5.1
ii  tex-common6.10
ii  tex-gyre  20180621-2
ii  texlive-base  2018.20181106-1
ii  texlive-binaries  2018.20181104.49075-1
ii  texlive-metapost  2018.20181106-1

Versions of packages context recommends:
pn  context-modules   
pn  fonts-freefont
ii  fonts-gfs-artemisia   1.1-5
ii  fonts-gfs-baskerville 1.1-5
ii  fonts-gfs-bodoni-classic  1.1-5
ii  fonts-gfs-didot   1.1-6
ii  fonts-gfs-didot-classic   1.1-5
ii  fonts-gfs-gazis   1.1-5
ii  fonts-gfs-neohellenic 1.1-6
ii  fonts-gfs-olga1.1-5
ii  fonts-gfs-porson  1.1-6
ii  fonts-gfs-solomos 1.1-5
ii  fonts-gfs-theokritos  1.1-5
ii  fonts-sil-gentium 20081126:1.03-2

Versions of packages context suggests:
pn  context-doc-nonfree  
pn  context-nonfree  
pn  fontforge
ii  libxml-parser-perl   2.44-2+b4
ii  perl-tk  1:804.033-2+b3

-- no debconf information
--- End Message ---
--- Begin Message ---
On Thu, 06 Dec 2018, Vincent Lefevre wrote:
> error in callback: /usr/share/texmf/tex/context/base/mkiv/luat-cod.lua:194: 
> attempt to call upvalue 'isfile' (a nil value)


Ahh that one ...

> Note: The issue cannot be reproduced with the latest texlive-binaries
> version. Perhaps a missing versioned dependency (or a Breaks...)?

Which version do you have installed of texlive-binaries? At least none
that is in any archive version at the moment, right?

This is an intermediate bug in texlive-binaries due to wrong luatex
version. An transitional artifact of Debian/unstable.

Closing this bug as it is not an any suite now.

Norbert

--
PREINING Norbert   http://www.preining.info
Accelia Inc. +JAIST +TeX Live +Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13--- End Message ---

Bug#915661: context: upgrade of context hangs on "Pregenerating ConTeXt MarkIV format."

[Vincent Lefevre]

Hi Norbert,

On 2018-12-06 09:19:27 +0900, Norbert Preining wrote:
> tags 915661 + unreproducible moreinfo
> thanks
> 
> Hi Vincent,
> 
> thanks for your message, very interesting.
> 
> On Wed, 05 Dec 2018, Vincent Lefevre wrote:
> > root  9619  9618  0 17:36 pts/400:00:00 luatex --ini 
> > --lua=/usr/share/texmf/tex/context/base/mkiv/luat-cod.lua 
> > /usr/share/texmf/tex/context/base/mkiv/cont-en.mkiv dump
> > 
> > which started 20 minutes ago and has no activity according to
> > "strace -p 9619".
> 
> I don't think that the strace on 9619 is useful, I guess there are other
> processes started that luatex is waiting for.

No, that was the leaf of the (here, linear) ps tree.

Since I can reproduce the problem with texlive-binaries
2018.20181104.49075-1 (this is what I had when I did the
upgrade) and using "apt install --reinstall context":

ypig:~> tps :r21384
root 21384  apt install --reinstall context
root └─> 21465  dpkg --status-fd 61 --configure --pending
root   └─> 21545  sh context.postinst configure 2018.04.04.20181118-1
root └─> 21553  sh luatools --make cont-en
root   └─> 21554  texlua mtxrun --script base --make cont-en
root └─> 21557  sh -c luatex --ini  
--lua=/usr/share/texmf/tex/context/base/mkiv/luat-cod.lua cont-en.mkiv  \dump 
root   └─> 21558  luatex --ini 
--lua=/usr/share/texmf/tex/context/base/mkiv/luat-cod.lua cont-en.mkiv dump

> Most probably it is the font caching that is done by context.
> 
> So if you have loads of big fonts or maybe strange fonts, then this
> might create problems.
> 
> Can please look into what other depending processes are running?
> I found
>   px 9619
> (or the PID of the luatex process on the next run) which uses px from
> the px package a very useful tool ;-)


ypig:/home/vlefevre# px 21558
luatex
  --ini
  --lua=/usr/share/texmf/tex/context/base/mkiv/luat-cod.lua
  /usr/share/texmf/tex/context/base/mkiv/cont-en.mkiv
  dump

kernel(0)root
  init(1)root
sshd(2786)   root
  sshd:(22260)   root
sshd:(22274) vlefevre
  -zsh(22275)vlefevre
su(11172)root
  bash(11173)root
apt(21384)   root
  dpkg(21465)root
context.postinst(21545)  root
  luatools(21553)root
texlua(21554)root
  sh(21557)  root
--> luatex(21558)root

2m22s ago luatex was started, at 2018-12-06T02:11:46+01:00.

Other processes started close to luatex(21558):
  dpkg(21465) was started 4.0s before luatex(21558)
  context.postinst(21545) was started 3.0s before luatex(21558)
  luatools(21553) was started just before luatex(21558)
  sh(21557) was started just before luatex(21558)
  texlua(21554) was started just before luatex(21558)

Users logged in when luatex(21558) started:
  vlefevre from 140.77.51.8

2018-12-06T02:14:08.869324: Now invoking lsof, this can take over a minute on a 
big system...
2018-12-06T02:14:09.275548: lsof done, proceeding.

File descriptors:
  stdin : [CHR] /dev/pts/2
  stdout: /tmp/luatools.cEMlPzbw
  stderr: /tmp/luatools.cEMlPzbw

Network connections:

Inter Process Communication:

For a list of all open files, do "sudo lsof -p 21558", or "sudo watch lsof -p 
21558" for a live view.


and /tmp/luatools.cEMlPzbw contains:

resolvers   | formats | using format path 
'/var/lib/texmf/luatex-cache/context/b47c3d3cee7cb6c86268d0595268c442/formats/luatex'
resolvers   | resolving | using given filetype 'tex'
resolvers   | methods | resolving, method 'concatinators', how 'tag', tag 
'file'
resolvers   | methods | resolving, method 'concatinators', how 'tag', tag 
'file'
resolvers   | resolving | remembering file 'cont-en.mkiv' using hash 
'tex::cont-en.mkiv'
resolvers   | formats | using tex source file 
'/usr/share/texmf/tex/context/base/mkiv/cont-en.mkiv'
resolvers   | resolving | checking qualified name 
'/usr/share/texmf/tex/context/base/mkiv/cont-en.lus'
resolvers   | resolving | using given filetype 'tex'
resolvers   | resolving | remembering file 
'/usr/share/texmf/tex/context/base/mkiv/cont-en.lus' using hash 
'tex::/usr/share/texmf/tex/context/base/mkiv/cont-en.lus'
resolvers   | resolving | remembering file 
'/usr/share/texmf/tex/context/base/mkiv/context.lus' using hash 
'tex::/usr/share/texmf/tex/context/base/mkiv/context.lus'
resolvers   | formats | executing runner 'make luatex format': luatex --ini 
 --lua=/usr/share/texmf/tex/context/base/mkiv/luat-cod.lua 

Bug#915680: mender-client: broken symlink: /var/lib/mender -> /data/mender, target violates FHS

[Andreas Beckmann]

Package: mender-client
Version: 1.6.0b1+git20181015.3032b74-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

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

0m34.2s ERROR: FAIL: Broken symlinks:
  /var/lib/mender -> /data/mender (mender-client)

If the target would be created, it would violate the FHS.


cheers,

Andreas


mender-client_1.6.0b1+git20181015.3032b74-1.log.gz
Description: application/gzip

Bug#915679: pcc: broken symlinks on i386: /usr/bin/x86_64-linux-gnu-p* -> x86_64-linux-gnu-pcc

[Andreas Beckmann]

Package: pcc
Version: 1.2.0~DEVEL+20180604-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

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

0m27.7s ERROR: FAIL: Broken symlinks:
  /usr/bin/x86_64-linux-gnu-pcpp -> x86_64-linux-gnu-pcc (pcc)
  /usr/bin/x86_64-linux-gnu-p++ -> x86_64-linux-gnu-pcc (pcc)

Please note that this is in the i386 package (and maybe also in
any other !amd64 package).


cheers,

Andreas


pcc_1.2.0~DEVEL+20180604-2.log.gz
Description: application/gzip

Bug#857298: python-cassandra-dbg is an empty package on hppa, m68k, mips, powerpc, powerpcspe, ppc64, s390x, and sparc64

[eamanu15]

Tags: fixed
Tags: help
Owner: emmanuelaria...@gmail.com

Hello everybody,

I am trying to upload python-cassandra-driver.

I push version 3.16.0-1 to salsa, and this must close this issue.

Please review it, and then I will search a sponsor.

Thanks!

Regards!

-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest

Bug#912202: marked as done (Uses git in debian/rules)

[Debian Bug Tracking System]

Your message dated Thu, 06 Dec 2018 00:34:43 +
with message-id 
and subject line Bug#912202: fixed in freeipa 4.7.1-3
has caused the Debian Bug report #912202,
regarding Uses git in debian/rules
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.)


-- 
912202: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912202
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:freeipa
Version: 4.7.0~pre1+git20180411-1
Severity: serious

override_dh_clean: gencontrol
dh_clean
if [ -f /usr/bin/git ]; then \
git checkout -- po; \
fi


This is unacceptable for several reasons, main one being that the package FTBFS
on systems with /usr/bin/git.

You are also rewriting debian/control and you should remember that this is
forbidden if the file actually changes (and a no-op otherwise).



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

Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: freeipa
Source-Version: 4.7.1-3

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

Debian distribution maintenance software
pp.
Timo Aaltonen  (supplier of updated freeipa 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, 06 Dec 2018 02:22:35 +0200
Source: freeipa
Binary: freeipa-admintools freeipa-common freeipa-client python-ipaclient 
python-ipalib freeipa-server freeipa-server-dns freeipa-server-trust-ad 
freeipa-tests python-ipaserver python-ipatests
Architecture: source
Version: 4.7.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian FreeIPA Team 
Changed-By: Timo Aaltonen 
Description:
 freeipa-admintools - transitional dummy package
 freeipa-client - FreeIPA centralized identity framework -- client
 freeipa-common - FreeIPA centralized identity framework -- common files
 freeipa-server - FreeIPA centralized identity framework -- server
 freeipa-server-dns - FreeIPA centralized identity framework -- IPA DNS 
integration
 freeipa-server-trust-ad - FreeIPA centralized identity framework -- AD trust 
installer
 freeipa-tests - FreeIPA centralized identity framework -- tests
 python-ipaclient - FreeIPA centralized identity framework -- Python modules 
for ipac
 python-ipalib - FreeIPA centralized identity framework -- shared Python modules
 python-ipaserver - FreeIPA centralized identity framework -- Python modules 
for serv
 python-ipatests - FreeIPA centralized identity framework -- Python modules for 
test
Closes: 851158 912202
Changes:
 freeipa (4.7.1-3) unstable; urgency=medium
 .
   * control: Replace libsvrcore-dev build-dep with 389-ds-base-dev.
   * tests: Install only the packages which are used for testing.
   * rules: Don't run git on clean. (Closes: #912202)
   * control: Nodejs is not available on all archs, build server packages
 only where it is.
   * control: Add systemd to python-ipalib depends. (Closes: #851158)
Checksums-Sha1:
 b70ebc7544fa5fbf248b411761e38fbfb3a2d4e4 3710 freeipa_4.7.1-3.dsc
 a73ca45f162ea62edca90536bf8c6f1baf1c83e7 281168 freeipa_4.7.1-3.debian.tar.xz
 76af27e9e3e73e8d2e761b5588e6f5d9cca84783 8983 freeipa_4.7.1-3_source.buildinfo
Checksums-Sha256:
 b77bf7ae236a84d2cc4e4f516fcf9c063e44dfc6e8616210c50f26e0739969d4 3710 
freeipa_4.7.1-3.dsc
 57b1cd7bd3211ffc1514cf8d0fe7d0ef3f2d42d99f43a53b965e9b96736c31fd 281168 
freeipa_4.7.1-3.debian.tar.xz
 f22a22e7f96ad99858a14bad2f0bb44b4bd89e505d52e96a3143dc2b79216605 8983 
freeipa_4.7.1-3_source.buildinfo
Files:
 7ee82d85f690997304adf91f2f671a05 3710 net optional freeipa_4.7.1-3.dsc
 5149dabba3298181a648be0bec36cb6d 281168 net optional 
freeipa_4.7.1-3.debian.ta

Bug#906977: marked as done (parley: FTBFS in buster/sid ('QItemSelection' does not name a type))

[Debian Bug Tracking System]

Your message dated Thu, 06 Dec 2018 00:36:16 +
with message-id 
and subject line Bug#906977: fixed in parley 4:17.08.3-1.1
has caused the Debian Bug report #906977,
regarding parley: FTBFS in buster/sid ('QItemSelection' does not name a type)
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.)


-- 
906977: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906977
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:parley
Version: 4:17.08.3-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
/usr/share/pkg-kde-tools/qt-kde-team/3/dhmk.pl --with=kf5,pkgkde-symbolshelper 
dpkg-buildflags --export=make > debian/dhmk_env.mk
/usr/bin/make -f debian/rules dhmk_run_configure_commands 
DHMK_TARGET="configure"
make[1]: Entering directory '/<>'
dh_testdir  # [-i]
dh_auto_configure '--buildsystem=kf5' --parallel  # [-i]
cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON "-GUnix Makefiles" 
-DCMAKE_BUILD_TYPE=Debian -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DKDE_INSTALL_USE_QT_SYS_PATHS=ON ..
-- The C compiler identification is GNU 8.2.0
-- The CXX compiler identification is GNU 8.2.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done

[... snipped ...]

cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++  -DKCOREADDONS_LIB 
-DQT_CONCURRENT_LIB -DQT_CORE_LIB -DQT_DBUS_LIB -DQT_GUI_LIB 
-DQT_MULTIMEDIA_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG -DQT_NO_URL_CAST_FROM_STRING 
-DQT_SCRIPT_LIB -DQT_SVG_LIB -DQT_USE_FAST_CONCATENATION 
-DQT_USE_FAST_OPERATOR_PLUS -DQT_WIDGETS_LIB -DQT_XML_LIB -D_GNU_SOURCE 
-D_LARGEFILE64_SOURCE -I/<>/obj-x86_64-linux-gnu/src 
-I/<>/src 
-I/<>/obj-x86_64-linux-gnu/src/parley_LIB_autogen/include 
-I/<>/src/collection -I/<>/src/editor 
-I/usr/include/libxml2 -isystem /usr/include/libkeduvocdocument -isystem 
/usr/include/x86_64-linux-gnu/qt5 -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtXml -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 
/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem 
/usr/include/KF5/KrossCore -isystem /usr/include/KF5 -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtScript -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtSv
 g -isystem /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem /usr/include/KF5/KI18n 
-isystem /usr/include/KF5/KNewStuff3 -isystem /usr/include/KF5/KNewStuff3/KNS3 
-isystem /usr/include/KF5/KNewStuff3/knscore -isystem 
/usr/include/KF5/KNewStuff3/kns3 -isystem /usr/include/KF5/KNewStuff3/KNSCore 
-isystem /usr/include/KF5/Attica -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem 
/usr/include/KF5/KCoreAddons -isystem /usr/include/KF5/KXmlGui -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtDBus -isystem /usr/include/KF5/KConfigCore 
-isystem /usr/include/KF5/KConfigWidgets -isystem /usr/include/KF5/KCodecs 
-isystem /usr/include/KF5/KWidgetsAddons -isystem /usr/include/KF5/KConfigGui 
-isystem /usr/include/KF5/KAuth -isystem /usr/include/KF5/KService -isystem 
/usr/include/KF5/SonnetCore -isystem /usr/include/KF5/SonnetUi -isystem 
/usr/include/KF5/KCMUtils -isystem /usr/include/KF5/KCompletion -isystem 
/usr/include/KF5/KTextWidgets 
 -isystem /usr/include/KF5/KIOWidgets -isystem /usr/include/KF5/KIOCore 
-isystem /usr/include/x86_64-linux-gnu/qt5/QtConcurrent -isystem 
/usr/include/KF5/KJobWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtMultimedia -isystem 
/usr/include/KF5/KNotifications -isystem /usr/include/KF5/KCrash  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time 
-D_FORTIFY_SOURCE=2 -std=c++0x -fno-operator-names -fno-exceptions -Wall 
-Wextra -Wcast-align -Wchar-subscripts -Wformat-security -Wno-long-long 
-Wpointer-arith -Wundef -Wnon-virtual-dtor -Woverloaded-virtual 
-Werror=return-type -Wvla -Wdate-time -fvisibility=hidden 
-fvisibility-inlines-hidden   -fPIC -std=gnu++11 -o 
CMakeFiles/parley_LIB.dir/editor/comparisonwidget.cpp.o -c 
/<>/src/editor/comparisonwidget.cpp
[ 45%] Building CXX object 
src/CMakeFiles/parley_LIB.dir/editor/inflectionwidget.cpp.o
cd /<>/

Processed: Re: Bug#915661: context: upgrade of context hangs on "Pregenerating ConTeXt MarkIV format."

[Debian Bug Tracking System]

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

> tags 915661 + unreproducible moreinfo
Bug #915661 [context] context: upgrade of context hangs on "Pregenerating 
ConTeXt MarkIV format."
Added tag(s) unreproducible and moreinfo.
> thanks
Stopping processing here.

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

Bug#915661: context: upgrade of context hangs on "Pregenerating ConTeXt MarkIV format."

[Norbert Preining]

tags 915661 + unreproducible moreinfo
thanks

Hi Vincent,

thanks for your message, very interesting.

On Wed, 05 Dec 2018, Vincent Lefevre wrote:
> root  9619  9618  0 17:36 pts/400:00:00 luatex --ini 
> --lua=/usr/share/texmf/tex/context/base/mkiv/luat-cod.lua 
> /usr/share/texmf/tex/context/base/mkiv/cont-en.mkiv dump
> 
> which started 20 minutes ago and has no activity according to
> "strace -p 9619".

I don't think that the strace on 9619 is useful, I guess there are other
processes started that luatex is waiting for. Most probably it is the
font caching that is done by context.

So if you have loads of big fonts or maybe strange fonts, then this
might create problems.

Can please look into what other depending processes are running?
I found
px 9619
(or the PID of the luatex process on the next run) which uses px from
the px package a very useful tool ;-)

Best

Norbert

--
PREINING Norbert   http://www.preining.info
Accelia Inc. +JAIST +TeX Live +Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#906187: marked as done (facter-dev: missing Depends: libfacter3.11.0 (= ${binary:Version}))

[Debian Bug Tracking System]

Your message dated Thu, 06 Dec 2018 00:04:19 +
with message-id 
and subject line Bug#906187: fixed in facter 3.11.0-1.1
has caused the Debian Bug report #906187,
regarding facter-dev: missing Depends: libfacter3.11.0 (= ${binary:Version})
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.)


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

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

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

0m28.1s ERROR: FAIL: Broken symlinks:
  /usr/lib/x86_64-linux-gnu/libfacter.so -> libfacter.so.3.11.0


BTW, why isn't the -dev package called libfacter-dev as it is usual?


cheers,

Andreas


facter-dev_3.11.0-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: facter
Source-Version: 3.11.0-1.1

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated facter 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: Sat,  1 Dec 2018 00:21:52 CET
Source: facter
Binary: facter libfacter3.11.0 facter-dev
Architecture: source
Version: 3.11.0-1.1
Distribution: unstable
Urgency: medium
Maintainer: Puppet Package Maintainers 

Changed-By: gregor herrmann 
Description: 
 facter - collect and display facts about the system
 libfacter3.11.0 - collect and display facts about the system -- shared library
 facter-dev - collect and display facts about the system -- development files
Closes: 906187
Changes:
 facter (3.11.0-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix "missing Depends: libfacter3.11.0 (= ${binary:Version})":
 add the Depends, as suggested by Andreas Beckmann.
 (Closes: #906187)
Checksums-Sha256: 
 799b49980d456e65399ba6d0526fd37aba2a0b2a05391a75b2dbe1b9f8698799 2919 
facter_3.11.0-1.1.dsc
 6d060c19edd18a25328a7147a7ca11b440557fdec4eecb70f5f48f7009ef2cfe 11664 
facter_3.11.0-1.1.debian.tar.xz
 100f3c5fbc8fa8b4ab2e6fc5efb7d3d5f70301b3549f8624f200a488fc005470 10847 
facter_3.11.0-1.1_sourceonly.buildinfo
Checksums-Sha1: 
 c1b06fdb34e91bc6bc88e9e39e6590902e850f7f 2919 facter_3.11.0-1.1.dsc
 85fbce34a028b0c705f9ce2c8c155309e1bdd421 11664 facter_3.11.0-1.1.debian.tar.xz
 33e9ce6fcc4873d0018e4538a0b13693457d955d 10847 
facter_3.11.0-1.1_sourceonly.buildinfo
Files: 
 4e49ccd3a462ab1c4e72a897c84b97cd 2919 admin optional facter_3.11.0-1.1.dsc
 c6bd23974917cf5139805b877280f816 11664 admin optional 
facter_3.11.0-1.1.debian.tar.xz
 58c931e81860bbb42f830f098f383a42 10847 - - 
facter_3.11.0-1.1_sourceonly.buildinfo

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAlwBxhFfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgaJ7Q//eTQRkfzfJ3VnPS0oiqckgMtqTy10/8pIHF2Bb6+tMTTtdDOV6LCPjCXn
cyzkzX1Sqzg6xTnYColMAP0rao2ZB3j7jA91x16VwBjWFwRfiwN/z9G3aBpEW7ow
9gerXwffJHN7BHW6iCjwspvzIS/nDtrqdY9v8bahMKTaGwg7LcnCtrbisigr/n5b
NHcOu60U297zGSBv0m8n+aUiVqvjOt4umutp1va0v3mf3Rvrexe4QNvHMZcQcDrr
bwiA1GN/ng09nYRYXtg4umcz6YxbLLauBbQfa2yvmP/2Qi88Rjt2U0o6tRVocqz1
bJ10Qo1FsNcOs7y5JCZdFcHL050qMiwKAl4Xc85bl1ejiV+vNqLaiXV40qbMS+0y
FnwMmA9zHorljg+yz4jTtkcFIrCbYEeGFGBy2kAG4FGKV8LCH7tWzLNJUqF7zw31
zqCnTHHTnsU5OlDWK5LO7knqi5GnbLkZa6R6SnT8GeHBqwULw/Z/det7gmnD9jfd
V4Hbkv3o5mr74vGroL4SQg7qKoRhHjWfmaGJdkLQEOkkLu2O4HeXUs+9z/GJLJQt
DdFgicrlBzQK/yDeAlYwgP6tkQCSDGI2Ib0jjJM1tcdYwrtjbMISq07lPkFm1rVa
e0TQcq8dk0oUYhoqVT4RgGHolm3CPLbU7jR8FZZ2rvVpxQE0rPo=
=kFp4
-END PGP SIGNATURE End Message ---

Bug#915666: linux: data corruption with blk-mq

[Christoph Anton Mitterer]

For those reading along, Jens Axboe gave a summary on how to
check whether one's affected or not:

Quoting from: https://bugzilla.kernel.org/show_bug.cgi?id=201685#c294
> scsi_mod.use_blk_mq=0 will do the trick, as will just ensuring that you have
> a scheduler for your device. Eg for sda, check:
> 
> # cat /sys/block/sda/queue/scheduler
> bfq [mq-deadline] none
> 
> As long as that doesn't say [none], you are fine as well. Also note that
> this seems to require a special circumstance of timing and devices to even
> be possible in the first place. But I would recommend ensuring that one of
> the above two conditions are true, and I'd further recommend just using
> mq-deadline (or bfq or kyber, whatever is your preference) instead of
> turning scsi-mq off.
> 
> Once you've ensured that after a fresh boot, I'd double check by running
> fsck on the file systems hosted by a SCSI/SATA device.


It seems that all my own systems (with blk-mq) run with [mq-deadline]
out of the box.
Maybe Debian maintainers can tell whether this is the default (since
long) so people can easier find out whether they need to check their
data for corruptions.



Cheers,
Chris.

Bug#899123: marked as done (nuxwdog: FTBFS: javah missing with openjdk-10)

[Debian Bug Tracking System]

Your message dated Wed, 05 Dec 2018 23:36:14 +
with message-id 
and subject line Bug#899123: fixed in nuxwdog 1.0.5-2
has caused the Debian Bug report #899123,
regarding nuxwdog: FTBFS: javah missing with openjdk-10
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.)


-- 
899123: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899123
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nuxwdog
Version: 1.0.3-4
Severity: serious
Justification: FTBFS
User: debian-p...@lists.debian.org
Usertags: hh2018

When testing packages against the upcoming release of perl, we found
an unrelated FTBFS on a clean sid chroot:

BUILD FAILED
/<>/build.xml:85: Execute failed: java.io.IOException: Cannot run 
program "javah" (in directory "/<>"): error=2, No such file or 
directory
at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1128)
at java.base/java.lang.ProcessBuilder.start(ProcessBuilder.java:1071)
at java.base/java.lang.Runtime.exec(Runtime.java:635)
[...]

This seems to be due to switching to openjdk-10, which does not include
javah.
--- End Message ---
--- Begin Message ---
Source: nuxwdog
Source-Version: 1.0.5-2

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

Debian distribution maintenance software
pp.
Timo Aaltonen  (supplier of updated nuxwdog 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, 06 Dec 2018 01:22:15 +0200
Source: nuxwdog
Binary: nuxwdog libnuxwdog0 libnuxwdog-dev libnuxwdog-java
Architecture: source
Version: 1.0.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian FreeIPA Team 
Changed-By: Timo Aaltonen 
Description:
 libnuxwdog-dev - Watchdog server -- development headers
 libnuxwdog-java - Watchdog server -- Java class
 libnuxwdog0 - Watchdog server -- shared library
 nuxwdog- Watchdog server -- daemon
Closes: 899123
Changes:
 nuxwdog (1.0.5-2) unstable; urgency=medium
 .
   * support-jdk11.diff: Fix build with current JDK. (Closes: #899123)
   * control, rules: Build with default jdk again.
Checksums-Sha1:
 d1a6d9d680c4348b13fcb6a79df22604256669f8 2182 nuxwdog_1.0.5-2.dsc
 962c732c698674332dd492a98f1924115243e501 4356 nuxwdog_1.0.5-2.debian.tar.xz
 e6255428853f7cee9755256fa1daf14b0f121306 8244 nuxwdog_1.0.5-2_source.buildinfo
Checksums-Sha256:
 9bd8412d0f2593c83461caefd63f8791c4462616e67174bb7341639b1276924f 2182 
nuxwdog_1.0.5-2.dsc
 b87fce57b966029eb2f12c243a928f8ebbaa6ba751afcc680fd54f5dbafa8b3e 4356 
nuxwdog_1.0.5-2.debian.tar.xz
 fe3b0dc855981d9230880caaba3d0f7f774e5919ef8dcce17c8957e60a50629c 8244 
nuxwdog_1.0.5-2_source.buildinfo
Files:
 b021daf04fe985452870ba7c37cd7932 2182 admin optional nuxwdog_1.0.5-2.dsc
 927235e93450dde785f5e1010f58c109 4356 admin optional 
nuxwdog_1.0.5-2.debian.tar.xz
 517ff3215d3c1eb947f4ef2ced16d45d 8244 admin optional 
nuxwdog_1.0.5-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEdS3ifE3rFwGbS2Yjy3AxZaiJhNwFAlwIXbYACgkQy3AxZaiJ
hNyNfQ//UezGrQ298ON/R6/Vgj5t3Uf8hYBb0HjpmpfKrE92fNn32gmzqDqg7oNA
cIrzQ3Ycp3ZlcfcGKxwTUUfd5a7uVlTZs+UYSRJeLyWtu4ntEhhW0RE2If0t54ji
O3MEau7CgHBWVRR9WCk3O1quSn/KbRk4maNebw6JykZBqXDTNHY6OqyuJXwnHAFn
WD2O1rFIefaE67GiZ1yAGmSPJ6nB/CRmd8kyCutIkKHfhEBxcm+b2fZEHC2ffNqD
Fmj75og3Od4em4YS19yNQf0d3oDYBD/1eUISy8IeO7g/bKJEUQTQHe+cre2OJ2o/
2XltwO0iDP4hiCUiO78pT8KyraecwGach53SmLRWMq58cDcpVQWR4A2YqcYUzi3H
PdWyg4kfPIToxczZjEGzMnDfQ5TvPaQvX+7WU32WaH+0I2Hg+KdozghAeR5FJ+xC
70JvrwnpFWfXYLF8HpFgk6eRHSB0YCMFpCtEf69gg0uAP0dSLd2aZ1wqvAd2Hyvo
ryRPsoRzqj0pHCB2W++OAbw+fQk816AM6IfUsSAzhHMpbWqPbHLV+BSYhjK+9k40
k/C8v0Lf9welQjL/OPTiSr28Ru4ZaptoxvF9h9yxip3Oia2gmL12W/Z9Ee3ib3ef
/qfsu9GSH9Fm6Jm9kiEW8j9QNpFU6ZoRBNL7/eNS5z2qO6cotBA=
=p8g1
-END PGP SIGNATURE End Message ---

Bug#910982: marked as done (389-ds-base FTBFS on armel/mips/mipsel: undefined reference to `__atomic_fetch_add_8')

[Debian Bug Tracking System]

Your message dated Wed, 05 Dec 2018 23:19:09 +
with message-id 
and subject line Bug#910982: fixed in 389-ds-base 1.4.0.19-2
has caused the Debian Bug report #910982,
regarding 389-ds-base FTBFS on armel/mips/mipsel: undefined reference to 
`__atomic_fetch_add_8'
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.)


-- 
910982: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910982
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: 389-ds-base
Version: 1.4.0.18-1
Severity: serious
Tags: patch ftbfs

https://buildd.debian.org/status/package.php?p=389-ds-base&suite=sid

...
/usr/bin/ld: 
src/nunc-stans/test/test_nuncstans_stress_small-test_nuncstans_stress_core.o: 
in function `client_initiate_connection_cb':
./build/../src/nunc-stans/test/test_nuncstans_stress_core.c:374: undefined 
reference to `__atomic_fetch_add_8'
/usr/bin/ld: ./build/../src/nunc-stans/test/test_nuncstans_stress_core.c:360: 
undefined reference to `__atomic_fetch_add_8'
/usr/bin/ld: 
src/nunc-stans/test/test_nuncstans_stress_small-test_nuncstans_stress_core.o: 
in function `client_response_cb':
./build/../src/nunc-stans/test/test_nuncstans_stress_core.c:339: undefined 
reference to `__atomic_fetch_add_8'
/usr/bin/ld: ./build/../src/nunc-stans/test/test_nuncstans_stress_core.c:325: 
undefined reference to `__atomic_fetch_add_8'
/usr/bin/ld: 
src/nunc-stans/test/test_nuncstans_stress_small-test_nuncstans_stress_core.o: 
in function `server_conn_read':
./build/../src/nunc-stans/test/test_nuncstans_stress_core.c:221: undefined 
reference to `__atomic_fetch_add_8'
/usr/bin/ld: 
src/nunc-stans/test/test_nuncstans_stress_small-test_nuncstans_stress_core.o:./build/../src/nunc-stans/test/test_nuncstans_stress_core.c:176:
 more undefined references to `__atomic_fetch_add_8' follow
collect2: error: ld returned 1 exit status
make[3]: *** [Makefile:6801: test_nuncstans_stress_small] Error 1


The following patch also fixes it for some ports architectures
that currently don't FTBFS due to building with nocheck.

--- debian/rules.old2018-10-14 07:59:39.722984897 +
+++ debian/rules2018-10-14 08:04:53.094937417 +
@@ -3,6 +3,10 @@
 
 export DEB_BUILD_MAINT_OPTIONS = hardening=+pie
 
+ifneq (,$(filter $(DEB_HOST_ARCH), armel m68k mips mipsel powerpc powerpcspe 
sh4))
+  export DEB_LDFLAGS_MAINT_APPEND=-latomic
+endif
+
 # Keep track of files we don't install
 NOT_INSTALLED := \
usr/share/cockpit/389-console/static/bootstrap.min.js \
--- End Message ---
--- Begin Message ---
Source: 389-ds-base
Source-Version: 1.4.0.19-2

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

Debian distribution maintenance software
pp.
Timo Aaltonen  (supplier of updated 389-ds-base 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, 06 Dec 2018 01:06:37 +0200
Source: 389-ds-base
Binary: 389-ds 389-ds-base-libs 389-ds-base-dev 389-ds-base python3-lib389 
cockpit-389-ds
Architecture: source
Version: 1.4.0.19-2
Distribution: unstable
Urgency: medium
Maintainer: Debian FreeIPA Team 
Changed-By: Timo Aaltonen 
Description:
 389-ds - 389 Directory Server suite - metapackage
 389-ds-base - 389 Directory Server suite - server
 389-ds-base-dev - 389 Directory Server suite - development files
 389-ds-base-libs - 389 Directory Server suite - libraries
 cockpit-389-ds - Cockpit user interface for 389 Directory Server
 python3-lib389 - Python3 module for accessing and configuring the 389 
Directory Se
Closes: 910982
Changes:
 389-ds-base (1.4.0.19-2) unstable; urgency=medium
 .
   * rules: Add -latomic to LDFLAGS on archs failing to build. (Closes:
 #910982)
Checksums-Sha1:
 03ebb0c59ba4214cafcc4609d1992a840172c563 2641 389-ds-base_1.4.0.19-2.dsc
 90464c432e5a409356735f1d10c0f2ac7f5b7e25 444296 
389-ds-base_1.4.0.19-2.debian.tar.xz
 50a444e32d478241c4ee01516aece2f6bb3df281 7793 
389-ds-base_1.4.0.19-2_source.buildinfo
Checksums-Sha256:
 e18a5bc9150c2ae54c3f2224fac998ee2cca8f82161733a45592ba430a1a87e5 2641 
389-ds-base_1.4.0.19-2.dsc
 859fa0058

Bug#899583: marked as done (libmozilla-ldap-perl: Invalid maintainer address pkg-fedora-ds-maintain...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Wed, 05 Dec 2018 23:20:08 +
with message-id 
and subject line Bug#899583: fixed in libmozilla-ldap-perl 1.5.3-3
has caused the Debian Bug report #899583,
regarding libmozilla-ldap-perl: Invalid maintainer address 
pkg-fedora-ds-maintain...@lists.alioth.debian.org
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.)


-- 
899583: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899583
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libmozilla-ldap-perl
Version: 1.5.3-2
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of libmozilla-ldap-perl,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package libmozilla-ldap-perl since the list address
pkg-fedora-ds-maintain...@lists.alioth.debian.org used in the
Maintainer: field was not transferred to the alioth-lists service that
provides a continuation for the lists in the @lists.alioth.debian.org
domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
pkg-fedora-ds-maintain...@lists.alioth.debian.org is 10.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: libmozilla-ldap-perl
Source-Version: 1.5.3-3

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

Debian distribution maintenance software
pp.
Timo Aaltonen  (supplier of updated libmozilla-ldap-perl 
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, 04 Dec 2018 12:40:45 +0200
Source: libmozilla-ldap-perl
Binary: libmozilla-ldap-perl
Architecture: source
Version: 1.5.3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian FreeIPA Team 
Changed-By: Timo Aaltonen 
Description:
 libmozilla-ldap-perl - LDAP Perl module for the OpenLDAP C SDK
Closes: 899583
Changes:
 libmozilla-ldap-perl (1.5.3-3) unstable; urgency=medium
 .
   * control: Update VCS urls.
   * watch: Updated.
   * control: Bump debhelper to 11.
   * control: Update maintainer address, drop Ghe Rivero from uploaders.
 (Closes: #899583)
   * control: Bump policy to 4.2.1.
Checksums-Sha1:
 204a000e62de75ce974c288d8b2dbc5782f67ca2 2132 libmozilla-ldap-perl_1.5.3-3.dsc
 a51b802b40f57d015b73fe26398e8c58359f11eb 12700 
libmozilla-ldap-perl_1.5.3-3.debian.tar.xz
 01ca7a52c1068a7a07122fcfccd5ea1aebd284d9 7512 
libmozilla-ldap-perl_1.5.3-3_source.buildinfo
Checksums-Sha256:
 295cf36e48b6299d430f9199cdef6409f8471a3b58981e15b688342b334951d2 2132 
libmozilla-ldap-perl_1.5.3-3.dsc
 547a7653ea56363a2d10c9bf3f04dea0078577bd38115d18e0b8059b3e87 12700 
libmozilla-ldap-perl_1.5.3-3.debian.tar.xz
 b0576d46513c32

Bug#915626: python-django: FTBFS: _pickle.PicklingError: Can't pickle : it's not the same object as django.contrib.admin.templatetags.admin_list.paginator_

[Chris Lamb]

Chris Lamb wrote:

>   $ PYTHONPATH=.. python3 ./runtests.py --parallel=1 --failfast
>   […]
>   Testing against Django installed in '/home/lamby/git/debian/python-
> team/modules/python-django/django'
>   Creating test database for alias 'default'...
>   Creating test database for alias 'other'...
>   System check identified no issues (14 silenced).
>   
[…]
>   ==
>   ERROR: test_dumpdata_with_excludes (fixtures.tests.FixtureLoadingTests)

I can reproduce this on upstream's master branch, as well as the 2.1.3
tag and 2.1.2. (I will hunt a bit more later, but it's now looking
like some toolchain issue.)


Regards,

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

Bug#908147: marked as done (restarting cups-browsed deleted print jobs)

[Debian Bug Tracking System]

Your message dated Wed, 05 Dec 2018 22:49:13 +
with message-id 
and subject line Bug#908147: fixed in cups-filters 1.21.5-1
has caused the Debian Bug report #908147,
regarding restarting cups-browsed deleted print jobs
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.)


-- 
908147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908147
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cups-browsed
Version: 1.21.1-1
Severity: grave

I had an two jobs of online receipts set to print to a cups-browsed
remote print queue (a PDF printer on a remote machine), and a bit after
printing noticed that print handn't completed. I checked the local CUPS
status page and saw a message that cups-pdf hadn't provided a host name,
confirm it is running (compare bug #887495).

I checked (via systemctl status), it was running:

root@Zia:~# systemctl status cups-browsed.service 
● cups-browsed.service - Make remote CUPS printers available locally
   Loaded: loaded (/lib/systemd/system/cups-browsed.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Thu 2018-09-06 00:00:04 EDT; 13h ago
 Main PID: 31796 (cups-browsed)
Tasks: 3 (limit: 4915)
   Memory: 5.0M
   CGroup: /system.slice/cups-browsed.service
   └─31796 /usr/sbin/cups-browsed

Sep 06 00:00:04 Zia systemd[1]: Started Make remote CUPS printers available 
locally.

... since it wasn't working, I did the obvious thing: systemctl restart 
cups-browsed.service

After doing so, the queue in the browser refreshed and showed empty. But
I checked — the PDFs were not created. Showing completed jobs shows
nothing. Looking in /var/spool/cups (on both the local machine and the
remote machine) shows no sign of the two jobs.

So it appears restarting cups-browsed deletes all pending print jobs.
Unfortunately, they're just gone ... hope I don't need those receipts.

A test page now works, so at least it fixed the queue. Testing
restarting it again, the job history is indeed gone, so that confirms
its deleting the data.

Unexpectedly and without warning discarding user data (pending print
jobs) really isn't OK, especially when CUPS itself is suggesting the
action that led to it.

Also, it looks like it was automatically restarted yesterday & this morning at
midnight; that makes this worse.

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

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

Versions of packages cups-browsed depends on:
ii  cups-daemon   2.2.8-5
ii  libavahi-client3  0.7-4
ii  libavahi-common3  0.7-4
ii  libavahi-glib10.7-4
ii  libc6 2.27-5
ii  libcups2  2.2.8-5
ii  libcupsfilters1   1.21.1-1
ii  libglib2.0-0  2.56.1-2
ii  libldap-2.4-2 2.4.46+dfsg-5
ii  lsb-base  9.20170808

Versions of packages cups-browsed recommends:
ii  avahi-daemon  0.7-4

cups-browsed suggests no packages.

-- Configuration Files:
/etc/cups/cups-browsed.conf changed:
BrowseRemoteProtocols dnssd cups
BrowsePoll watt.home


-- no debconf information
--- End Message ---
--- Begin Message ---
Source: cups-filters
Source-Version: 1.21.5-1

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

Debian distribution maintenance software
pp.
Didier Raboud  (supplier of updated cups-filters 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, 05 Dec 2018 23:03:42 +0100
Source: cups-filters
Binary: libcupsfilters1 libfontembed1 cups-filters cups-filters-core-drivers 
libcupsfilters-dev libfontembed-dev cups-browsed
Architecture: source
Version: 1.21.5-1
Distribution: unstable
Urgency: medium
Maintainer: D

Bug#915364: qbittorrent again crashes when starting talks of symbol lookup error

[Bernhard Übelacker]

Dear Maintainer,
sorry, tried to mark it as fixed in the rebuild 1.1.9-1+b1.
But cont...@bugs.debian.org processed just version 1.1.9-1.

Kind regards,
Bernhard

Bug#908147: restarting cups-browsed deleted print jobs

[Till Kamppeter]

Anthony, thanks for testing. The fix is on its way into Debian and Ubuntu.

   Till

Processed: Re: Bug#915364: qbittorrent again crashes when starting talks of symbol lookup error

[Debian Bug Tracking System]

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

> reassign 915364 libtorrent-rasterbar9 1.1.9-1
Bug #915364 [qbittorrent] qbittorrent again crashes when starting talks of 
symbol lookup error
Bug reassigned from package 'qbittorrent' to 'libtorrent-rasterbar9'.
No longer marked as found in versions qbittorrent/4.1.4-1.
Ignoring request to alter fixed versions of bug #915364 to the same values 
previously set
Bug #915364 [libtorrent-rasterbar9] qbittorrent again crashes when starting 
talks of symbol lookup error
Marked as found in versions libtorrent-rasterbar/1.1.9-1.
> fixed915364 1.1.9-1+b1
Bug #915364 [libtorrent-rasterbar9] qbittorrent again crashes when starting 
talks of symbol lookup error
Marked as fixed in versions libtorrent-rasterbar/1.1.9-1.
> thanks
Stopping processing here.

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

Bug#908147: restarting cups-browsed deleted print jobs

[Anthony DeRobertis]

On 12/5/18 4:49 PM, Till Kamppeter wrote:
cups-browsed is part of cups-filters, not of CUPS. The patch you find 
here:


https://github.com/OpenPrinting/cups-filters/commit/0d29084a864ca80ada8b4eafc2d36f072e06f984 




I applied your patch and it has fixed the problem for me. Thank you!

Bug#908147: restarting cups-browsed deleted print jobs

[Didier 'OdyX' Raboud]

Le mercredi, 5 décembre 2018, 22.49:57 h CET Till Kamppeter a écrit :
> cups-browsed is part of cups-filters, not of CUPS. The patch you find here:
> 
> https://github.com/OpenPrinting/cups-filters/commit/0d29084a864ca80ada8b4eaf
> c2d36f072e06f984

I'm uploading a fixed cups-filters with this patch cherry-picked "as we 
speak".

Cheers,
OdyX

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

Bug#908147: restarting cups-browsed deleted print jobs

[Till Kamppeter]

cups-browsed is part of cups-filters, not of CUPS. The patch you find here:

https://github.com/OpenPrinting/cups-filters/commit/0d29084a864ca80ada8b4eafc2d36f072e06f984

   Till

Bug#828429: marked as done (mailavenger: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Wed, 05 Dec 2018 21:51:37 +
with message-id 
and subject line Bug#828429: fixed in mailavenger 0.8.5-1
has caused the Debian Bug report #828429,
regarding mailavenger: FTBFS with openssl 1.1.0
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.)


-- 
828429: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828429
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mailavenger
Version: 0.8.4-4
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/mailavenger_0.8.4-4_amd64-20160529-1448

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

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

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


Kurt
--- End Message ---
--- Begin Message ---
Source: mailavenger
Source-Version: 0.8.5-1

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

Debian distribution maintenance software
pp.
Ulises Vitulli  (supplier of updated mailavenger 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, 05 Dec 2018 08:20:10 -0300
Source: mailavenger
Binary: mailavenger
Architecture: source amd64
Version: 0.8.5-1
Distribution: unstable
Urgency: medium
Maintainer: Ulises Vitulli 
Changed-By: Ulises Vitulli 
Description:
 mailavenger - Highly configurable, MTA-independent SMTP filter server
Closes: 828429
Changes:
 mailavenger (0.8.5-1) unstable; urgency=medium
 .
   * FTBFS with openssl 1.1.0 (Closes: #828429).
   * Install new systemd service unit.
   * Upgrade to debhelper 11 standard.
   * Bump up Standard-version to 4.2.1.5.
   * Fix some typos from README.Debian.
Checksums-Sha1:
 d752118c2a28d326f4491d53f8c67a2b16c362e3 1798 mailavenger_0.8.5-1.dsc
 17586dab7defe0103ade330ee3c242b2c501468d 910358 mailavenger_0.8.5.orig.tar.gz
 68856fd9d0a773df9292ad9161c4e0fc815e3cf1 10696 
mailavenger_0.8.5-1.debian.tar.xz
 825b38b37e2f07fd21b99bf8655b3479121ab157 3473964 
mailavenger-dbgsym_0.8.5-1_amd64.deb
 59a1ae4536e469052670c8ee64fae407243d20c2 5998 
mailavenger_0.8.5-1_amd64.buildinfo
 db26b23cdc12cf8164d015b4e3fd1fc66bf8ac91 517064 mailavenger_0.8.5-1_amd64.deb
Checksums-Sha256:
 058ebfedef8b8f3f3e5088d6d44cdfd23d7f53cd000d0e36cee38af2306e3fb8 1798 
mailavenger_0.8.5-1.dsc
 b0fc3e2e03ed010e95e561367fce7b087968df7ea6056251eba95cad14d26d37 910358 
mailavenger_0.8.5.orig.tar.gz
 4318960e023ce843115f035a722a3a1e351094c61691dff84f71f648dcc1c3ba 10696 
mailavenger_0.8.5-1.debian.tar.xz
 4843a2beb62d13a73f0834cf0eb7437c0ff6c2d587ba3175ce7f72c2923ec156 3473964 
mailavenger-dbgsym_0.8.5-1_amd64.deb
 2d704c765729f835b993ebbc8144b602e4e3c9c39cb529f77379161bf49674e7 5998 
mailavenger_0.8.5-1_amd64.buildinfo
 a2aaa64bf4fca88ed9927e388cbee4e49a4d1b7a573972eca2d0922b1be63db1 517064 
mailavenger_0.8.5-1_amd64.deb
Files:
 de75b2e800cb32652c79efd423d3a055 1798 mail optional mailavenger_0.8.5-1.dsc
 2750b1af5e2adf41d8a61ac9dcecd2aa 910358 mail optional 
mailavenger_0.8.5.orig.tar.gz
 1051c80f56d34881472f660129c92b98 10696 mail optional 
mailavenger_0.8.5-1.debian.tar.xz
 bd89d405a908713ce517327cc6001f42 3473964 debug optional 
mailavenger-dbgsym_0.8.5-1_amd64.deb
 6d0968498b298521c18f5c0b52f1c847 5998 mail optional 
mailavenger_0.8.5-1_amd64.buildinfo
 0cab047d6e538e181da3463a140d7587 517064 mail optional 
mailavenger_0.8.5-1_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEvQqKQ/VtTywBCMYlg8MHkAqShqAFAlwIOi0ACgkQg8MHkAqS
hqDWkA//cE0r6mVF30PHr86AVOo8dXfvayBYgShiEZ8cTzv+2663gEH50UPm1wSY
jdHIzoRf+J0OK73/dqPCYkkZqlCqCl8IxIwx/MfWUceHfSjPb0vlU8E6MkH2QD6u
k6Dc+f/5BK09YF/3BT6yrCf9Dn1oI4xr

Bug#908147: restarting cups-browsed deleted print jobs

[Anthony DeRobertis]

On 12/5/18 4:20 PM, Till Kamppeter wrote:
Anyone suffering this problem, can you apply my upstream fix and check 
again whether this solves the problem? Thanks.


   Till


I can't find 0d29084a864c anywhere. I checked:

 * https://github.com/apple/cups
 * https://github.com/tillkamppeter/cups
 * https://salsa.debian.org/printing-team/cups

Could you please point to where you've published it (or, alternatively, 
email the patch). I hope it applies against 2.2.9 which Debian currently 
has, or this could get interesting.

Processed: tagging 915619

[Debian Bug Tracking System]

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

> tags 915619 + pending
Bug #915619 [src:golang-gopkg-lxc-go-lxc.v2] golang-gopkg-lxc-go-lxc.v2: not 
compatible with LXC v3
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#908147: restarting cups-browsed deleted print jobs

[Till Kamppeter]

I have (hopefully) fixed this bug upstream now (commit 0d29084a864c).

In case of a shutdown of cups-browsed the queues were even removed with 
jobs. This I have corrected now, now cups-browsed really only removes 
print queues when they do not have jobs.


The problem occurred independent of whether the remote queues are 
discovered from the local network or via BrowsePoll.


   Till

Bug#908147: restarting cups-browsed deleted print jobs

[Anthony DeRobertis]

On 12/5/18 3:41 PM, Till Kamppeter wrote:


Anyone here who can reproduce the vanishing of print jobs when 
stopping or restarting cups-browsed, please put cups-browsed in debug 
logging mode by stopping it, editing /etc/cups/cups-browsed.conf to 
contain a line


DebugLogging file


I've attached three cups-browsed_log logs and my cups-browsed.conf.

The three logs were made from four restarts of cups-browsed. After each 
start, I did a "mv cups-browsed_log cbl-N" to keep each start separate 
(it kept writing to the same file after mv):


(a) un-comment DebugLogging file, restart [finishes none, this starts 
log #1]


(b) pause printer, send print job, restart cups-browsed [finishes #1, 
starts #2]


(c) pause printer, send print job, restart cups-browsed [finishes #2, 
starts #3]


(d) comment back out DebugLogging, restart [finishes #3, starts none]

The print job from (b) was preserved and sent on; the print job from (c) 
was lost.


PS: On the off-chance the implicitclass being lowercased every other 
restart was a cause, I created a second PDF queue "lcpdf" on Watt, so 
that there wouldn't be a miss-match every other restart. That one always 
displays lowercase, but it still exhibits the every-other-restart 
behavior w/r/t/ deleting jobs.




cups-browsed.conf.gz
Description: application/gzip


cbl-1.gz
Description: application/gzip


cbl-2.gz
Description: application/gzip


cbl-3.gz
Description: application/gzip

Bug#908147: restarting cups-browsed deleted print jobs

[Till Kamppeter]

Anyone suffering this problem, can you apply my upstream fix and check 
again whether this solves the problem? Thanks.


   Till

Processed: reassign 900912 to openjdk-11

[Debian Bug Tracking System]

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

> reassign 900912 openjdk-11
Bug #900912 [src:openjdk-10] openjdk-10: Accessibility does not get loaded
Bug reassigned from package 'src:openjdk-10' to 'openjdk-11'.
No longer marked as found in versions openjdk-10/10.0.1+10-4.
Ignoring request to alter fixed versions of bug #900912 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed (with 1 error): Re: Bug#900912 closed by Debian FTP Masters (Bug#915601: Removed package(s) from unstable)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #900912 {Done: Debian FTP Masters } 
[src:openjdk-10] openjdk-10: Accessibility does not get loaded
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 10.0.2+13-2+rm.
> reassign openjdk-11
Unknown command or malformed arguments to command.


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

Bug#900912: closed by Debian FTP Masters (Bug#915601: Removed package(s) from unstable)

[Samuel Thibault]

Control: reopen -1
Control: reassign openjdk-11

Migrating the still-existing bug to openjdk 11.

Samuel

Bug#908147: restarting cups-browsed deleted print jobs

[Brian Potkin]

On Wed 05 Dec 2018 at 15:13:53 -0500, Anthony DeRobertis wrote:

> Actually, I'm using cups-browsed's BrowsePoll here, the printers are on
> another network over a VPN. I have no idea if that matters.

Of course it matters. I would never have entered this conversation if I
had known that. VPN's are outside my experience, and I have no plans to
explore further.
 
> The alternative to using cups-browsed for that use case is, so far as I
> know, to just configure the printers statically. I prefer not to, as that
> means copying around a bunch of config.
> 
> I'm glad someone else is seeing this too, though. Especially after
> determining it was deleting jobs every other restart I was beginning to
> worry that I might just be a crazy person :-/

I most probably will look at this further, but only without BrowsePoll
and a VPN.

-- 
Brian.

Bug#911685: marked as done (yade FTBFS: ... has no member named 'move_point'; did you mean 'Bare_point')

[Debian Bug Tracking System]

Your message dated Wed, 05 Dec 2018 20:46:51 +
with message-id 
and subject line Bug#911685: fixed in yade 2018.02b-5
has caused the Debian Bug report #911685,
regarding yade FTBFS: ... has no member named 'move_point'; did you mean 
'Bare_point'
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.)


-- 
911685: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911685
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: yade
Version: 2018.02b-4
Severity: serious
Tags: ftbfs

yade fails to build from source in unstable/amd64.

https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/yade_2018.02b-4.rbuild.log.gz

| [ 59%] Building CXX object 
CMakeFiles/yade.dir/pkg/dem/TesselationWrapper.cpp.o
| /usr/bin/c++  -DBOOST_MATH_DISABLE_FLOAT128=1 -DNDEBUG -DQT_CORE_LIB 
-DQT_GUI_LIB -DQT_NO_DEBUG -DQT_OPENGL_LIB -DQT_WIDGETS_LIB -DQT_XML_LIB 
-DSUITESPARSE_VERSION_4 -DYADE_ODEINT -DYADE_SPH -DYADE_VTK6 -Dyade_EXPORTS 
-I/build/1st/yade-2018.02b/debian/build/yade_autogen/include 
-I/build/1st/yade-2018.02b 
-I/usr/lib/python2.7/dist-packages/numpy/core/include -I/usr/include/python2.7 
-I/usr/include/eigen3 -I/usr/include/vtk-6.3 -I/usr/include/x86_64-linux-gnu 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/suitesparse -I/build/1st/yade-2018.02b/debian/build 
-I/build/1st/yade-2018.02b/debian/build/pkg/pfv -isystem 
/usr/include/x86_64-linux-gnu/qt5 -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 
/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtXml -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtOpenGL  -g -O2 
-ffile-prefix-map=/build/1st/yade-2018.02b=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -O2 
--param=ssp-buffer-size=4 -Wformat -Wformat-security -Werror=format-security 
-Wall -std=c++11 -DYADE_VTK -DYADE_OPENMP -fopenmp -DYADE_GTS  
-DQGLVIEWER_FOUND -DYADE_OPENGL -DYADE_QT5  -DYADE_CGAL -DFLOW_ENGINE 
-DTWOPHASEFLOW  -DLINSOLV -DFLOW_ENGINE -DYADE_GL2PS -DLBM_ENGINE -fPIC   
-ftrack-macro-expansion=0 -save-temps -fstack-protector-strong 
-DEIGEN_DONT_VECTORIZE -DEIGEN_DONT_ALIGN 
-DEIGEN_DISABLE_UNALIGNED_ARRAY_ASSERT -DCGAL_DISABLE_ROUNDING_MATH_CHECK 
-frounding-math -fPIC -std=gnu++11 -o 
CMakeFiles/yade.dir/pkg/dem/TesselationWrapper.cpp.o -c 
/build/1st/yade-2018.02b/pkg/dem/TesselationWrapper.cpp
| In file included from 
/usr/lib/python2.7/dist-packages/numpy/core/include/numpy/ndarraytypes.h:1816,
|  from 
/usr/lib/python2.7/dist-packages/numpy/core/include/numpy/ndarrayobject.h:18,
|  from 
/usr/lib/python2.7/dist-packages/numpy/core/include/numpy/arrayobject.h:4,
|  from /build/1st/yade-2018.02b/lib/pyutil/numpy_boost.hpp:40,
|  from 
/build/1st/yade-2018.02b/pkg/dem/TesselationWrapper.cpp:15:
| 
/usr/lib/python2.7/dist-packages/numpy/core/include/numpy/npy_1_7_deprecated_api.h:15:2:
 warning: #warning "Using deprecated NumPy API, disable it by " "#defining 
NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION" [-Wcpp]
|  #warning "Using deprecated NumPy API, disable it by " \
|   ^~~
| In file included from 
/build/1st/yade-2018.02b/lib/triangulation/Tesselation.h:202,
|  from 
/build/1st/yade-2018.02b/pkg/dem/TesselationWrapper.hpp:15,
|  from 
/build/1st/yade-2018.02b/pkg/dem/TesselationWrapper.cpp:12:
| /build/1st/yade-2018.02b/lib/triangulation/Tesselation.ipp: In instantiation 
of 'CGT::_Tesselation::VertexHandle CGT::_Tesselation::move(CGT::Real, 
CGT::Real, CGT::Real, CGT::Real, unsigned int) [with TT = 
CGT::TriangulationTypes; 
CGT::_Tesselation::VertexHandle = 
CGAL::internal::CC_iterator >, 
CGAL::Boolean_tag, CGAL::Boolean_tag >, 
CGAL::Alpha_shape_cell_base_3 >, 
CGAL::Boolean_tag, CGAL::Boolean_tag >, CGAL::Sequential_tag> > > 
>, CGAL::Boolean_tag, CGAL::Boolean_tag >, CGAL::Default, 
CGAL::Default, CGAL::Default>, false>; CGT::Real = double]':
| /build/1st/yade-2018.02b/pkg/dem/TesselationWrapper.cpp:186:28:   required 
from here
| /build/1st/yade-2018.02b/lib/triangulation/Tesselation.ipp:78:12: error: 
'CGT::_Tesselation >::RTriangulation' {aka 'class 
CGAL::Regular_triangulation_3 >, 
CGAL::Boolean_tag, CGAL::Boolean_tag >, 
CGAL::Alpha_shape_cell_base_3 >, 
CGAL::Boolean_tag, CGAL::Boolean_tag >, CGAL::Sequential_tag>, 
CGAL::Default>'} has no member named 'move_point'; did you mean 'Bare_point'?
|   Vh = Tri->m

Bug#915308: marked as done (orocos-bfl FTBFS: test_complete_filter (Failed))

[Debian Bug Tracking System]

Your message dated Wed, 05 Dec 2018 20:46:07 +
with message-id 
and subject line Bug#915308: fixed in orocos-bfl 0.8.0-5
has caused the Debian Bug report #915308,
regarding orocos-bfl FTBFS: test_complete_filter (Failed)
to be marked as done.

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

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


-- 
915308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915308
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: orocos-bfl
Version: 0.8.0-4
Severity: serious
Tags: ftbfs

Some recent change in unstable makes orocos-bfl FTBFS:

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

...
test 7
Start 7: test_complete_filter

7: Test command: 
/build/1st/orocos-bfl-0.8.0/obj-x86_64-linux-gnu/tests/test_complete_filter
7: Test timeout computed to be: 1000
7: .Running 4 different filters. This may take a few minutes... 
7: .F
7: 
7: complete_filter_test.cpp:458:Assertion
7: Test name: Complete_FilterTest::testComplete_FilterValue_Discr
7: assertion failed
7: - Expression: posterior->ProbabilityGet(state) >0.9
7: 
7: Failures !!!
7: Run: 2   Failure total: 1   Failures: 1   Errors: 0
7/7 Test #7: test_complete_filter .***Failed7.74 sec
.Running 4 different filters. This may take a few minutes... 
.F

complete_filter_test.cpp:458:Assertion
Test name: Complete_FilterTest::testComplete_FilterValue_Discr
assertion failed
- Expression: posterior->ProbabilityGet(state) >0.9

Failures !!!
Run: 2   Failure total: 1   Failures: 1   Errors: 0


86% tests passed, 1 tests failed out of 7

Total Test time (real) =   8.00 sec

The following tests FAILED:
  7 - test_complete_filter (Failed)
Errors while running CTest
make[4]: *** [tests/CMakeFiles/check.dir/build.make:63: tests/CMakeFiles/check] 
Error 8
--- End Message ---
--- Begin Message ---
Source: orocos-bfl
Source-Version: 0.8.0-5

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

Debian distribution maintenance software
pp.
Jochen Sprickerhof  (supplier of updated orocos-bfl 
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, 05 Dec 2018 21:26:30 +0100
Source: orocos-bfl
Binary: liborocos-bfl0.8 liborocos-bfl-dev liborocos-bfl-examples
Architecture: source
Version: 0.8.0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Jochen Sprickerhof 
Description:
 liborocos-bfl-dev - Orocos Bayesian Filtering Library development files
 liborocos-bfl-examples - Orocos Bayesian Filtering Library examples
 liborocos-bfl0.8 - Orocos Bayesian Filtering Library
Closes: 915308
Changes:
 orocos-bfl (0.8.0-5) unstable; urgency=medium
 .
   * Add upstream patch for broken test (Closes: #915308)
   * Bump policy version
   * scrap symbols files
Checksums-Sha1:
 fdc0e61ca7d352035309a76750288c5d88269431 2282 orocos-bfl_0.8.0-5.dsc
 761697bf908d540ec2a4544601c4a1da2a5a47b4 5748 orocos-bfl_0.8.0-5.debian.tar.xz
 74cb4212f828223593ef13525ac66489405a09e5 6661 
orocos-bfl_0.8.0-5_source.buildinfo
Checksums-Sha256:
 e3dfe01a5e8d87aa975d8441443c699c86a3b7ffb4ddf18cb4c6162d790d33d6 2282 
orocos-bfl_0.8.0-5.dsc
 80c732173576ba6ba02d7ffddf901e57fd8a4d998efd5fc310166579b2479a14 5748 
orocos-bfl_0.8.0-5.debian.tar.xz
 8cfa45bdd2560a6f2ff3afefe5a1f68d641826d6284722a2e6c6d795f82a63bf 6661 
orocos-bfl_0.8.0-5_source.buildinfo
Files:
 0d038da43dd10d394eb8ffea8f2b2835 2282 devel optional orocos-bfl_0.8.0-5.dsc
 dc90630ed33fd30f574c3022fbfb 5748 devel optional 
orocos-bfl_0.8.0-5.debian.tar.xz
 c2d971bbf870ffd2ee232a81cf88f293 6661 devel optional 
orocos-bfl_0.8.0-5_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAlwINIgUHGpzcHJpY2tl
QGRlYmlhbi5vcmcACgkQW//cwljmlDNFWBAAknBCziST+zHdsHscU++ws9l4Dv0C
yGoOXx7dSHXVb+43qilcrNhx5KfRFdVs2kU5X14itJX+kdrD1cAqVZMgpp9gl4OD
zqWsM0rGh8IiMBW0QUsjOEDrkAU3kI6wQ6EVkTPw32a1/qxAGwpOFWAcFs7wnwrg
1qEexGnlR5/HRqXTQHozRvAlFBNPTHy48UUxQVIgkMTQXpKPh0+Tf0iR8TdIgYVL
x5wSnskHWYCCCAci2LLRnM

Bug#893142: marked as done (dogtag-pki FTBFS with openjdk-9)

[Debian Bug Tracking System]

Your message dated Wed, 05 Dec 2018 20:44:23 +
with message-id 
and subject line Bug#893142: fixed in dogtag-pki 10.6.8-1
has caused the Debian Bug report #893142,
regarding dogtag-pki 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.)


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

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

...
netscape/security/x509/RevocationReasonAdapter.java:20: error: package 
javax.xml.bind.annotation.adapters is not visible
import javax.xml.bind.annotation.adapters.XmlAdapter;
^
  (package javax.xml.bind.annotation.adapters is declared in module 
java.xml.bind, which is not in the module graph)
--- End Message ---
--- Begin Message ---
Source: dogtag-pki
Source-Version: 10.6.8-1

We believe that the bug you reported is fixed in the latest version of
dogtag-pki, 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.
Timo Aaltonen  (supplier of updated dogtag-pki 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, 05 Dec 2018 22:21:50 +0200
Source: dogtag-pki
Binary: dogtag-pki pki-base pki-base-java python3-pki-base pki-tools pki-server 
pki-ca dogtag-pki-console-theme dogtag-pki-server-theme pki-console pki-kra 
pki-ocsp pki-tks pki-tps pki-tps-client pki-javadoc libsymkey-java libsymkey-jni
Architecture: source
Version: 10.6.8-1
Distribution: unstable
Urgency: medium
Maintainer: Debian FreeIPA Team 
Changed-By: Timo Aaltonen 
Description:
 dogtag-pki - Dogtag Public Key Infrastructure (PKI) Suite
 dogtag-pki-console-theme - Certificate System - PKI Console User Interface
 dogtag-pki-server-theme - Certificate System - PKI Server User Interface
 libsymkey-java - Symmetric Key Java library
 libsymkey-jni - Symmetric Key JNI Library
 pki-base   - Certificate System - PKI Framework
 pki-base-java - Certificate System - PKI Framework -- java client support
 pki-ca - Certificate System - Certificate Authority
 pki-console - Certificate System - PKI Console
 pki-javadoc - Certificate System - PKI Framework Javadocs
 pki-kra- Certificate System - Data Recovery Manager
 pki-ocsp   - Certificate System - Online Certificate Status Protocol Manager
 pki-server - Certificate System - PKI Server Framework
 pki-tks- Certificate System - Token Key Service
 pki-tools  - Certificate System - PKI Tools
 pki-tps- Certificate System - Token Processing System
 pki-tps-client - Certificate System - Token Processing System client
 python3-pki-base - Certificate System - PKI Framework -- python3 client support
Closes: 893142
Changes:
 dogtag-pki (10.6.8-1) unstable; urgency=medium
 .
   * New upstream release.
   * control: Bump depends on nuxwdog and tomcatjss.
   * control, use-new-pkcs11-interface.diff: Bump libjss-java depends to
 4.5.1, fix build against jdk9+. (Closes: #893142)
   * patches: Refreshed.
   * control: Add libjackson2-core-java, -databind-java to build-depends.
   * dogtag-pki-server-theme.install: Updated.
   * control, rules: Build-depend on default-jdk again, set JAVA_HOME to
 match.
   * tests: Force C locale so that error messages from python can be shown.
   * control: Bump libresteasy3.0-java dependency for jackson2 provider.
   * control, rules: Replace libjboss-annotations-1.2-api-java with
 libgeronimo-annotation-1.3-spec-java. Drop dependency on
 libscannotation-java.
Checksums-Sha1:
 b9593df863ddfee2ec3ea7f05d6e8a4e210e0f13 3752 dogtag-pki_10.6.8-1.dsc
 da3ef7a4c745f73a25bad59b4e7a72c3f001508c 3975924 dogtag-pki_10.6.8.orig.tar.xz
 042e315a7a06d26532878f12b61d32df7bc53760 32084 
dogtag-pki_10.6.8-1.debian.tar.xz
 e26fe724d4ee4550edc9f04d303192b917609a2b 9720 
dogtag-pki_10.6.8-1_source.buildinfo
Checksums-Sha256:
 df94c3f10c2227a6387b4757e1704ebac9d07ca169957fe380376a47e0e70f32 3752 
dogtag-pki_10.6.8-1.dsc
 36687190328b6331c89161cb55a07fc34813d603580e50e71c289695e55e2

Bug#915339: marked as done (libc6 needs Conflicts with unfixed r-cran-later)

[Debian Bug Tracking System]

Your message dated Wed, 05 Dec 2018 20:44:59 +
with message-id 
and subject line Bug#915339: fixed in glibc 2.28-2
has caused the Debian Bug report #915339,
regarding libc6 needs Conflicts with unfixed r-cran-later
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.)


-- 
915339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915339
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-treespace
Version: 1.1.3+dfsg-1
Severity: serious
Tags: ftbfs

Some recent change in unstable makes r-cran-treespace FTBFS:

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

...
installing to 
/build/1st/r-cran-treespace-1.1.3+dfsg/debian/r-cran-treespace/usr/lib/R/site-library/treespace/libs
** R
** data
*** moving datasets to lazyload DB
** inst
** byte-compile and prepare package for lazy loading
terminate called after throwing an instance of 'std::runtime_error'
  what():  Mutex creation failed
Aborted
dh_auto_install: R CMD INSTALL -l 
/build/1st/r-cran-treespace-1.1.3\+dfsg/debian/r-cran-treespace/usr/lib/R/site-library
 --clean . "--built-timestamp='Thu, 07 Jun 2018 11:53:16 +0200'" returned exit 
code 134
make: *** [debian/rules:4: binary] Error 2
--- End Message ---
--- Begin Message ---
Source: glibc
Source-Version: 2.28-2

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

Debian distribution maintenance software
pp.
Aurelien Jarno  (supplier of updated glibc 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, 05 Dec 2018 19:50:21 +0100
Source: glibc
Binary: libc-bin libc-dev-bin libc-l10n glibc-doc glibc-source locales 
locales-all nscd multiarch-support libc6 libc6-dev libc6-dbg libc6-pic 
libc6-udeb libc6.1 libc6.1-dev libc6.1-dbg libc6.1-pic libc6.1-udeb libc0.3 
libc0.3-dev libc0.3-dbg libc0.3-pic libc0.3-udeb libc0.1 libc0.1-dev 
libc0.1-dbg libc0.1-pic libc0.1-udeb libc6-i386 libc6-dev-i386 libc6-sparc 
libc6-dev-sparc libc6-sparc64 libc6-dev-sparc64 libc6-s390 libc6-dev-s390 
libc6-amd64 libc6-dev-amd64 libc6-powerpc libc6-dev-powerpc libc6-ppc64 
libc6-dev-ppc64 libc6-mips32 libc6-dev-mips32 libc6-mipsn32 libc6-dev-mipsn32 
libc6-mips64 libc6-dev-mips64 libc0.1-i386 libc0.1-dev-i386 libc6-x32 
libc6-dev-x32 libc6-xen libc0.3-xen libc6.1-alphaev67
Architecture: source
Version: 2.28-2
Distribution: unstable
Urgency: medium
Maintainer: GNU Libc Maintainers 
Changed-By: Aurelien Jarno 
Description:
 glibc-doc  - GNU C Library: Documentation
 glibc-source - GNU C Library: sources
 libc-bin   - GNU C Library: Binaries
 libc-dev-bin - GNU C Library: Development binaries
 libc-l10n  - GNU C Library: localization files
 libc0.1- GNU C Library: Shared libraries
 libc0.1-dbg - GNU C Library: detached debugging symbols
 libc0.1-dev - GNU C Library: Development Libraries and Header Files
 libc0.1-dev-i386 - GNU C Library: 32bit development libraries for AMD64
 libc0.1-i386 - GNU C Library: 32bit shared libraries for AMD64
 libc0.1-pic - GNU C Library: PIC archive library
 libc0.1-udeb - GNU C Library: Shared libraries - udeb (udeb)
 libc0.3- GNU C Library: Shared libraries
 libc0.3-dbg - GNU C Library: detached debugging symbols
 libc0.3-dev - GNU C Library: Development Libraries and Header Files
 libc0.3-pic - GNU C Library: PIC archive library
 libc0.3-udeb - GNU C Library: Shared libraries - udeb (udeb)
 libc0.3-xen - GNU C Library: Shared libraries [Xen version]
 libc6  - GNU C Library: Shared libraries
 libc6-amd64 - GNU C Library: 64bit Shared libraries for AMD64
 libc6-dbg  - GNU C Library: detached debugging symbols
 libc6-dev  - GNU C Library: Development Libraries and Header Files
 libc6-dev-amd64 - GNU C Library: 64bit Development Libraries for AMD64
 libc6-dev-i386 - GNU C Library: 32-bit development libraries for AMD64
 libc6-dev-mips32 - GNU C Library: o32 Development Libraries for MIPS
 libc6-dev-mips64 - GNU C Library: 64bit Development Libraries for MIPS64
 libc6-dev-mips

Bug#908147: restarting cups-browsed deleted print jobs

[Till Kamppeter]

Usually cups-browsed does not remove a print queue if it still has jobs. 
If it is stopped and one of its queues still has jobs, this queue is 
left intact. Next time it starts it connects the this remaining queue 
with its printer if it re-discovers the printer, or removes it if the 
printer has disappered (also only when there are no jobs).


Anyone here who can reproduce the vanishing of print jobs when stopping 
or restarting cups-browsed, please put cups-browsed in debug logging 
mode by stopping it, editing /etc/cups/cups-browsed.conf to contain a line


DebugLogging file

and start it again. Then do all the reproducer steps as described in the 
previous postings here and after that, attach your 
/etc/cups/cups-browsed.conf to this bug report. Thanks.


   Till

Processed: found 915025 in 3.1.3-3

[Debian Bug Tracking System]

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

> found 915025 3.1.3-3
Bug #915025 [libopenmpi-dev] libopenmpi-dev: fails to upgrade from 'stretch': 
new libopenmpi-dev package pre-installation script subprocess returned error 
exit status 2
Marked as found in versions openmpi/3.1.3-3.
> thanks
Stopping processing here.

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

Processed: severity of 915636 is serious

[Debian Bug Tracking System]

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

> severity 915636 serious
Bug #915636 [python3-virtualenv] python3-virtualenv: incompatible with 
python3-pip 18.1 - AttributeError pip.main - please upgrade to 16.1.0
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: bug 915666 is forwarded to https://bugzilla.kernel.org/show_bug.cgi?id=201685

[Debian Bug Tracking System]

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

> forwarded 915666 https://bugzilla.kernel.org/show_bug.cgi?id=201685
Bug #915666 [src:linux] linux: data corruption with blk-mq
Set Bug forwarded-to-address to 
'https://bugzilla.kernel.org/show_bug.cgi?id=201685'.
> thanks
Stopping processing here.

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

Bug#908147: restarting cups-browsed deleted print jobs

[Anthony DeRobertis]

Actually, I'm using cups-browsed's BrowsePoll here, the printers are on 
another network over a VPN. I have no idea if that matters.


The alternative to using cups-browsed for that use case is, so far as I 
know, to just configure the printers statically. I prefer not to, as 
that means copying around a bunch of config.


I'm glad someone else is seeing this too, though. Especially after 
determining it was deleting jobs every other restart I was beginning to 
worry that I might just be a crazy person :-/

Bug#915666: linux: data corruption with blk-mq

[Christoph Anton Mitterer]

Source: linux
Version: 4.18.20-2
Severity: critical
Tags: upstream patch
Justification: causes serious data loss


Hi.

There's a bug in the blk-mq schedulers which may cause serious data
curruption...
See https://bugzilla.kernel.org/show_bug.cgi?id=201685

Seems like a patch was made recently,... maybe it would make sense
to cherry pick that one before it makes its way via the stable kernels.

AFAIU the discussions, at least 4.18 may be affected as well.


Cheers,
Chris.


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

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

Bug#908147: restarting cups-browsed deleted print jobs

[Brian Potkin]

On Wed 05 Dec 2018 at 12:06:39 -0500, Anthony DeRobertis wrote:

> Just re-tested:
> 
> 1. Went to http://localhost:631/printers/PDF_watt_home and under
>"Maintenance" picked "pause printer". Entered username & password
>when prompted.
> 2. Generated a print job with: fortune -s | lpr -PPDF_watt_home
> 3. Confirmed a print job in the queue at
>http://localhost:631/printers/PDF_watt_home
> 4. Ran systemctl restart cups-browsed.service
> 5. Job stayed...
> 6. Ran systemctl stop cups-browsed.service ; systemctl start
>cups-browsed.service
> 7. Job vanished.

More or less the same for me, but I have no explanation.

It is not compulsory to use cups-browsed; 'lpstat -e' should show your
print queue when it is stopped. 'lp -d PDF_watt_home' might be a way of
of getting the job done.

Regards,

Brian.

Bug#915603: (no subject)

[Ted Percival]

Bug 871306[2] says graphicsmagick needs to Build-Depend on g++ (>= 4:7) to get
the new & old ABIs, but I don't see a versioned Build-Depends on g++ since the
bug was closed in version 1.3.26-5.

> For new
> executables to build without undefined references, your library will
> need rebuilding with GCC 7.

So the solution might just be to add the versioned Build-Depends: g++ (>= 4:7)
and rebuild to get the old symbols back into the library, rather than bumping
the soname.

[1] https://wiki.debian.org/GCC7#GCC_7_name_mangling_bug_fix
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871306

Bug#908147: restarting cups-browsed deleted print jobs

[Brian Potkin]

On Sat 01 Dec 2018 at 18:04:15 +0100, gregor herrmann wrote:

> On Thu, 06 Sep 2018 13:31:51 -0400, Anthony DeRobertis wrote:
> 
> > After doing so, the queue in the browser refreshed and showed empty. But
> > I checked — the PDFs were not created. Showing completed jobs shows
> > nothing. Looking in /var/spool/cups (on both the local machine and the
> > remote machine) shows no sign of the two jobs.
> 
> I can't reproduce this bug but maybe I did something wrong. What I
> did was:
> 
> - print to a printer which is not available
> - check in the cups web ui and in /var/spool/cups that the print job
>   is there
> - service cups-browsed restart
> - and the job is still in the spool and the web ui still shows the job
>   and the problem (printer not responding; well, it's a few hundred
>   kilometers away)
> 
> (In the spirit of full disclosure: this is with sysv-init and not
> systemd, in case this makes a difference.)

I would doubt the init system is a factor. Additionally, your print
queue/printer is not on the local network so discovery via Bonjour
broadcasting is not involved, as it would seem to be with Anthony
DeRobertis. So, I am unsure how pertinent your observation is.

> Cheers,
> gregor, from the Bern BSP

Thanks for your participation in the BSP. All work and no beer I
imagine. Or did Odyx buy you a few? :)

Regards,

Brian.

Bug#914953: [3dprinter-general] Bug#914953: FTBFS with Python 3.7 on many architectures

[Gregor Riepl]

I'm inclined to drop the symbols file altogether, as it really doesn't add any
value. The correct solution would be to use -fvisibility=hidden [1] and
properly tag symbols for the public API of libArcus and libSavitar.

For what it's worth, libArcus.so.3 is currently only used by python3-arcus and
CuraEngine anyway, and it's unlikely that this will change.

Another option would be to put all the internal Cura libraries into a private
lib folder, but I suspect this is risky and even more work than adding symbol
visibility.


[1] http://gcc.gnu.org/wiki/Visibility

Bug#915639: shibboleth-resolver: FTBFS: missing pkg-config/log4shib/log4cpp

[Ferenc Wágner]

Andreas Beckmann  writes:

> shibboleth-resolver FTBFS everywhere:
>
> checking for pkg-config... no

It's just pkg-config missing from Build-Depends.
Sam, are you around to fix this?
-- 
Thanks,
Feri

Bug#914953: [3dprinter-general] Bug#914953: FTBFS with Python 3.7 on many architectures

[Gregor Riepl]

> Hi, I saw that you asked for sponsorship on the ML¹ but then pere failed
> to build the package².  Could you please have a look soon?

Sorry, got held up by the mess that is symbols files for C++ libraries that
don't properly hide internal symbols.

I'll try to get this sorted out ASAP.

Do you know who I could talk to for help with C++ symbols file issues?

Bug#914146: marked as done (dogecoin FTBFS with boost 1.67)

[Debian Bug Tracking System]

Your message dated Wed, 05 Dec 2018 17:49:34 +
with message-id 
and subject line Bug#914146: fixed in dogecoin 1.10.0-6
has caused the Debian Bug report #914146,
regarding dogecoin FTBFS with boost 1.67
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.)


-- 
914146: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914146
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dogecoin
Version: 1.10.0-5
Severity: serious
Tags: ftbfs buster sid

https://buildd.debian.org/status/package.php?p=dogecoin&suite=sid

...
g++ -DHAVE_CONFIG_H -I. -I../src/config  -I. -I./obj -pthread -I/usr/include 
-I./leveldb/include -I./leveldb/helpers/memenv   -I./secp256k1/include   
-Wdate-time -D_FORTIFY_SOURCE=2 -DBOOST_SPIRIT_THREADSAFE -DHAVE_BUILD_INFO 
-D__STDC_FORMAT_MACROS  -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security  -Wstack-protector -fstack-protector-all -fPIC -c -o 
libbitcoin_server_a-rpcserver.o `test -f 'rpcserver.cpp' || echo 
'./'`rpcserver.cpp
rpcserver.cpp:507:102: error: wrong number of template arguments (2, should be 
1)
 static void RPCAcceptHandler(boost::shared_ptr< 
basic_socket_acceptor > acceptor,

  ^
In file included from /usr/include/boost/asio.hpp:30,
 from rpcprotocol.h:15,
 from rpcserver.h:10,
 from rpcserver.cpp:6:
/usr/include/boost/asio/basic_socket_acceptor.hpp:73:7: note: provided for 
'template class boost::asio::basic_socket_acceptor'
 class basic_socket_acceptor
   ^
rpcserver.cpp:507:104: error: template argument 1 is invalid
 static void RPCAcceptHandler(boost::shared_ptr< 
basic_socket_acceptor > acceptor,

^
rpcserver.cpp:517:95: error: wrong number of template arguments (2, should be 1)
 static void RPCListen(boost::shared_ptr< basic_socket_acceptor > acceptor,

   ^
In file included from /usr/include/boost/asio.hpp:30,
 from rpcprotocol.h:15,
 from rpcserver.h:10,
 from rpcserver.cpp:6:
/usr/include/boost/asio/basic_socket_acceptor.hpp:73:7: note: provided for 
'template class boost::asio::basic_socket_acceptor'
 class basic_socket_acceptor
   ^
rpcserver.cpp:517:97: error: template argument 1 is invalid
 static void RPCListen(boost::shared_ptr< basic_socket_acceptor > acceptor,

 ^
rpcserver.cpp: In function 'void RPCListen(int, boost::asio::ssl::context&, 
bool)':
rpcserver.cpp:522:109: error: base operand of '->' is not a pointer
 boost::shared_ptr< AcceptedConnectionImpl > conn(new 
AcceptedConnectionImpl(acceptor->get_io_service(), context, fUseSSL));

 ^~
rpcserver.cpp:524:13: error: base operand of '->' is not a pointer
 acceptor->async_accept(
 ^~
rpcserver.cpp: At global scope:
rpcserver.cpp:540:102: error: wrong number of template arguments (2, should be 
1)
 static void RPCAcceptHandler(boost::shared_ptr< 
basic_socket_acceptor > acceptor,

  ^
In file included from /usr/include/boost/asio.hpp:30,
 from rpcprotocol.h:15,
 from rpcserver.h:10,
 from rpcserver.cpp:6:
/usr/include/boost/asio/basic_socket_acceptor.hpp:73:7: note: provided for 
'template class boost::asio::basic_socket_acceptor'
 class basic_socket_acceptor
   ^
rpcserver.cpp:540:104: error: template argument 1 is invalid
 static void RPCAcceptHandler(boost::shared_ptr< 
basic_socket_acceptor > acceptor,

^
rpcserver.cpp: In function 'void RPCAcceptHandler(int, 
boost::asio::ssl::context&, bool, boost::shared_ptr, const 
boost::system::error_code&)':
rpcserver.cpp:547:67: error: base operand of '->' is not a pointer
 if (error != boost::asio::error::operation_aborted && acceptor->is_open())
   ^~
rpcserver.cpp:548:

Processed: Re: Bug#912168: node-marked breaks node-marked-man autopkgtest

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #912168 [src:node-marked, src:node-marked-man] node-marked breaks 
node-marked-man autopkgtest
Severity set to 'serious' from 'normal'
> tags -1 ftbfs
Bug #912168 [src:node-marked, src:node-marked-man] node-marked breaks 
node-marked-man autopkgtest
Added tag(s) ftbfs.

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

Bug#883417: Debdiff for FTBFS

[Aurimas Fišeras]

Here is a debdiff from phpmyadmin 4:4.6.6-5 to our local phpmyadmin 
build that fixes FTBFS at least when building in Ubuntu Bionic chroot 
(with phpunit 6.5.5).
diff -Nru phpmyadmin-4.6.6/debian/changelog phpmyadmin-4.6.6/debian/changelog
--- phpmyadmin-4.6.6/debian/changelog	2017-07-10 13:43:06.0 +0300
+++ phpmyadmin-4.6.6/debian/changelog	2018-12-05 19:01:54.0 +0200
@@ -1,3 +1,11 @@
+phpmyadmin (4:4.6.6-6~vp1) bionic; urgency=medium
+
+  * PHP 7.2 compatibility for often used functionality (#890595).
+  * Backport 45828153b to fix build with phpunit 6,
+add additional phpunit 6 compatibility fixes (Closes: #883417).
+
+ -- Aurimas Fišeras   Wed, 05 Dec 2018 19:01:54 +0200
+
 phpmyadmin (4:4.6.6-5) unstable; urgency=medium
 
   * Add alternate dependency to php-mysqli. This seems to help in case people
diff -Nru phpmyadmin-4.6.6/debian/patches/debian.patch phpmyadmin-4.6.6/debian/patches/debian.patch
--- phpmyadmin-4.6.6/debian/patches/debian.patch	2017-04-07 20:21:37.0 +0300
+++ phpmyadmin-4.6.6/debian/patches/debian.patch	2018-12-05 14:51:20.0 +0200
@@ -4,9 +4,11 @@
  - config file consists of several included files, so we skip mtime check
 From: Michal Čihař 
 Forwarded: not-needed
 a/libraries/vendor_config.php
-+++ b/libraries/vendor_config.php
-@@ -17,13 +17,13 @@
+Index: phpmyadmin-4.6.6/libraries/vendor_config.php
+===
+--- phpmyadmin-4.6.6.orig/libraries/vendor_config.php
 phpmyadmin-4.6.6/libraries/vendor_config.php
+@@ -17,13 +17,13 @@ if (! defined('PHPMYADMIN')) {
   * Path to changelog file, can be gzip compressed. Useful when you want to
   * have documentation somewhere else, eg. /usr/share/doc.
   */
@@ -22,7 +24,7 @@
  
  /**
   * Directory where SQL scripts to create/upgrade configuration storage reside.
-@@ -35,7 +35,7 @@
+@@ -35,7 +35,7 @@ define('SQL_DIR', './sql/');
   * It is not used directly in code, just a convenient
   * define used further in this file.
   */
@@ -31,7 +33,7 @@
  
  /**
   * Filename of a configuration file.
-@@ -55,23 +55,27 @@
+@@ -55,23 +55,27 @@ define('CUSTOM_FOOTER_FILE', CONFIG_DIR
  /**
   * Default value for check for version upgrades.
   */
diff -Nru phpmyadmin-4.6.6/debian/patches/fix-build-with-phpunit6.patch phpmyadmin-4.6.6/debian/patches/fix-build-with-phpunit6.patch
--- phpmyadmin-4.6.6/debian/patches/fix-build-with-phpunit6.patch	1970-01-01 03:00:00.0 +0300
+++ phpmyadmin-4.6.6/debian/patches/fix-build-with-phpunit6.patch	2018-12-05 19:00:53.0 +0200
@@ -0,0 +1,2073 @@
+Only in phpmyadmin-4.6.6-temp/debian/patches: .fix-build-with-phpunit6.patch.swp
+Index: phpmyadmin-4.6.6/test/classes/gis/GISFactoryTest.php
+===
+--- phpmyadmin-4.6.6.orig/test/classes/gis/GISFactoryTest.php
 phpmyadmin-4.6.6/test/classes/gis/GISFactoryTest.php
+@@ -12,7 +12,8 @@ use PMA\libraries\gis\GISFactory;
+  *
+  * @package PhpMyAdmin-test
+  */
+-class GISFactoryTest extends PHPUnit_Framework_TestCase
++use PHPUnit\Framework\TestCase;
++class GISFactoryTest extends TestCase
+ {
+ 
+ /**
+Index: phpmyadmin-4.6.6/test/classes/gis/GISGeometrycollectionTest.php
+===
+--- phpmyadmin-4.6.6.orig/test/classes/gis/GISGeometrycollectionTest.php
 phpmyadmin-4.6.6/test/classes/gis/GISGeometrycollectionTest.php
+@@ -15,7 +15,8 @@ require_once TCPDF_INC;
+  *
+  * @package PhpMyAdmin-test
+  */
+-class GISGeometryCollectionTest extends PHPUnit_Framework_TestCase
++use PHPUnit\Framework\TestCase;
++class GISGeometryCollectionTest extends TestCase
+ {
+ 
+ /**
+Index: phpmyadmin-4.6.6/test/classes/gis/GISGeometryTest.php
+===
+--- phpmyadmin-4.6.6.orig/test/classes/gis/GISGeometryTest.php
 phpmyadmin-4.6.6/test/classes/gis/GISGeometryTest.php
+@@ -11,7 +11,8 @@
+  *
+  * @package PhpMyAdmin-test
+  */
+-class GISGeometryTest extends PHPUnit_Framework_TestCase
++use PHPUnit\Framework\TestCase;
++class GISGeometryTest extends TestCase
+ {
+ /**
+  * @access protected
+Index: phpmyadmin-4.6.6/test/classes/gis/GISGeomTest.php
+===
+--- phpmyadmin-4.6.6.orig/test/classes/gis/GISGeomTest.php
 phpmyadmin-4.6.6/test/classes/gis/GISGeomTest.php
+@@ -11,7 +11,8 @@
+  *
+  * @package PhpMyAdmin-test
+  */
+-abstract class GISGeomTest extends PHPUnit_Framework_TestCase
++use PHPUnit\Framework\TestCase;
++abstract class GISGeomTest extends TestCase
+ {
+ 
+ /**
+Index: phpmyadmin-4.6.6/test/classes/properties/options/groups/OptionsPropertyMainGroupTest.php
+===
+--- phpmyadmin-4.6.6.orig/test/classes/properties/options/groups/OptionsPropertyMainGroupTest.php
 phpmyadmin-4.6.6/test/classes/properties/options/groups/Opti

Processed: reassign 879469 to resteasy

[Debian Bug Tracking System]

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

> reassign 879469 resteasy
Bug #879469 [resteasy3.0] Should not enter testing
Bug reassigned from package 'resteasy3.0' to 'resteasy'.
Ignoring request to alter found versions of bug #879469 to the same values 
previously set
Ignoring request to alter fixed versions of bug #879469 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#879469: Should not enter testing

[Timo Aaltonen]

On 22.10.2017 1.13, Timo Aaltonen wrote:
> Package: resteasy3.0
> Severity: serious
> 
> Resteasy 3.0 was reintroduced to sid in order to allow porting new
> versions of Dogtag and Freeipa. It should not enter testing though.
> Hopefully upstream will finish porting Dogtag to 3.1 or newer before too
> long.

Upstream/Redhat has no immediate plans to move to a newer branch of
Resteasy (they still have 3.0.19), so I think the best plan for buster
is to ship with src:resteasy3.0 and instead keep src:resteasy out of the
release. Nothing depends on it anyway.

FTR, Dogtag does build with Resteasy 3.6.2, but there probably would be
runtime issues, also adding Jackson2 provider (which Dogtag 10.6.8
needs) would require packaging a bunch of new packages.

-- 
t

Bug#915364: Bug #915364: qbittorrent again crashes when starting talks of symbol lookup error

[subhuman]

Looks good after the upgrade. Thanks a lot for the quick help!

The bug should be downgraded to one concerning Debian package dependencies.



On Wed, 5 Dec 2018 11:56:29 +0100
Bernhard Übelacker  wrote:

> Hello Martin Haase,
> 
> > ii  libtorrent-rasterbar9  1.1.9-1
> 
> You probably have also to update your libtorrent-rasterbar9
> package to version 1.1.9-1+b1.
> 
> 
> libtorrent-rasterbar (1.1.9-1+b1) sid; urgency=low, binary-only=yes
> 
>   * Binary-only non-maintainer upload for amd64; no source changes.
>   * Rebuild against boost1.67.
> 
>  -- amd64 / i386 Build Daemon (x86-ubc-01) 
>   Sat, 17 Nov 2018 00:04:35 +
> 
> 
> Kind regards,
> Bernhard

Bug#908147: restarting cups-browsed deleted print jobs

[Anthony DeRobertis]

Just re-tested:

1. Went to http://localhost:631/printers/PDF_watt_home and under
   "Maintenance" picked "pause printer". Entered username & password
   when prompted.
2. Generated a print job with: fortune -s | lpr -PPDF_watt_home
3. Confirmed a print job in the queue at
   http://localhost:631/printers/PDF_watt_home
4. Ran systemctl restart cups-browsed.service
5. Job stayed...
6. Ran systemctl stop cups-browsed.service ; systemctl start
   cups-browsed.service
7. Job vanished.

That is... odd. So I tried printing another job, getting an "No 
destination host name supplied by cups-browsed for printer 
\"pdf_watt_home\", is cups-browsed running?" error showing up in the 
CUPS error log (and webui) eventually. After that, "systemctl restart 
cups-browsed.service" made the job vanish.


Now that printer seems permanently broken (with that no destination 
error). So I restarted cups.service (which also deleted the print job). 
Still got the error.


It's weird I'm also getting errors in the CUPS error log like:

E [05/Dec/2018:11:38:24 -0500] [Client 22] Returning IPP 
client-error-bad-request for CUPS-Add-Modify-Printer 
(ipp://localhost:631/printers/pdf_watt_home) from localhost.


To get it back working, I stopped cups-browsed.service, deleted all the 
printers it added via CUPS webui, stopped cups.service, started 
cups.service, and then started cups-browsed.service again. Got those 
weird error log entries again.


After that, tested again and it didn't delete the job, but restarting 
cups-browsed.service resumed the print queue (which it probably 
shouldn't, since I manually paused it, but that's much more minor).


Just to be sure, paused it again, added another job, and restarted 
cups-browsed.service: it deleted the job.


Tested again: unpaused, job not lost.

Tested again: job lost

Tested again: unpaused, not lost.

Tested again: job lost

Tested again: unpaused, not lost

... so... umm... it seems to lose jobs every other restart.

So I restarted it immediately again, without sending a print job. Then 
tested again, and not lost. It really does appear to be every other restart.


I think I've noticed something though. On restarting it, the 
"Connection:" changes in the CUPS web ui. Sometimes its 
"implicitclass://pdf_watt_home/" other times 
"implicitclass://PDF_watt_home/".  Each restart of cups-browsed.service 
changes back and forth. And it appears lowercased printer names lose 
jobs on restart.


I have two remote printers, and they have opposite lowercase-states. I 
haven't tested as much with the other printer (it's a real printer, so 
testing wastes paper & toner), but it appears to follow the same 
lowercase-means-jobs-lost rule. (BTW: It gets the error log entries too).


I tried to find more details about the bad requests, but it doesn't 
appear to actually be sending IPP requests — or at least, not one that 
Wireshark can capture on lo (it sees the requests from Firefox, so it's 
working). Possibly it sends them over the cups UNIX socket.


On 12/1/18 12:04 PM, gregor herrmann wrote:

On Thu, 06 Sep 2018 13:31:51 -0400, Anthony DeRobertis wrote:


After doing so, the queue in the browser refreshed and showed empty. But
I checked — the PDFs were not created. Showing completed jobs shows
nothing. Looking in /var/spool/cups (on both the local machine and the
remote machine) shows no sign of the two jobs.

I can't reproduce this bug but maybe I did something wrong. What I
did was:

- print to a printer which is not available
- check in the cups web ui and in /var/spool/cups that the print job
   is there
- service cups-browsed restart
- and the job is still in the spool and the web ui still shows the job
   and the problem (printer not responding; well, it's a few hundred
   kilometers away)

(In the spirit of full disclosure: this is with sysv-init and not
systemd, in case this makes a difference.)


Cheers,
gregor, from the Bern BSP

Bug#915661: context: upgrade of context hangs on "Pregenerating ConTeXt MarkIV format."

[Vincent Lefevre]

Package: context
Version: 2018.04.04.20181118-1
Severity: grave
Justification: renders package unusable

When upgrading context:

Setting up context (2018.04.04.20181118-1) ...
Running mtxrun --generate. This may take some time... done.
Pregenerating ConTeXt MarkIV format. This may take some time... 

This is due to:

root  9619  9618  0 17:36 pts/400:00:00 luatex --ini 
--lua=/usr/share/texmf/tex/context/base/mkiv/luat-cod.lua 
/usr/share/texmf/tex/context/base/mkiv/cont-en.mkiv dump

which started 20 minutes ago and has no activity according to
"strace -p 9619".

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

Kernel: Linux 4.18.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=POSIX 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages context depends on:
ii  lmodern   2.004.5-5
ii  ruby  1:2.5.1
ii  tex-common6.10
ii  tex-gyre  20180621-2
ii  texlive-base  2018.20181106-1
ii  texlive-binaries  2018.20181104.49075-1
ii  texlive-metapost  2018.20181106-1

Versions of packages context recommends:
pn  context-modules   
pn  fonts-freefont
ii  fonts-gfs-artemisia   1.1-5
ii  fonts-gfs-baskerville 1.1-5
ii  fonts-gfs-bodoni-classic  1.1-5
ii  fonts-gfs-didot   1.1-6
ii  fonts-gfs-didot-classic   1.1-5
ii  fonts-gfs-gazis   1.1-5
ii  fonts-gfs-neohellenic 1.1-6
ii  fonts-gfs-olga1.1-5
ii  fonts-gfs-porson  1.1-6
ii  fonts-gfs-solomos 1.1-5
ii  fonts-gfs-theokritos  1.1-5
ii  fonts-sil-gentium 20081126:1.03-2

Versions of packages context suggests:
pn  context-doc-nonfree  
pn  context-nonfree  
pn  fontforge
ii  libxml-parser-perl   2.44-2+b4
ii  perl-tk  1:804.033-2+b3

-- no debconf information

Bug#913915: marked as done (juce: VST2 support has been dropped)

[Debian Bug Tracking System]

Your message dated Wed, 05 Dec 2018 16:34:40 +
with message-id 
and subject line Bug#913915: fixed in juce 5.4.1+really5.3.2~repack-1
has caused the Debian Bug report #913915,
regarding juce: VST2 support has been dropped
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.)


-- 
913915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913915
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: juce
Severity: serious
Tags: upstream
Justification: makes rdeps FTBFS

juce-5.4 has dropped the built-in VST2 support and now depends on the Steinberg
SDK (which - apart from being proprietary and non-free - is no longer
available) for download at all.
This has severe implications on the the usability of JUCE (as it can no longer
be used to build VST2 plugins).

Until there is a proper solution for the problem, i suggest to keep JUCE from
migrating to testing.


-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
LANGUAGE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: juce
Source-Version: 5.4.1+really5.3.2~repack-1

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

Debian distribution maintenance software
pp.
IOhannes m zmölnig (Debian/GNU)  (supplier of updated juce 
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: Wed, 05 Dec 2018 17:06:00 +0100
Source: juce
Binary: juce-modules-source juce-tools libjuce-doc
Architecture: source
Version: 5.4.1+really5.3.2~repack-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: IOhannes m zmölnig (Debian/GNU) 
Description:
 juce-modules-source - Jules' Utility Class Extensions (module sources)
 juce-tools - JUCE's project management tools
 libjuce-doc - Jules' Utility Class Extensions (documentation)
Closes: 913915
Changes:
 juce (5.4.1+really5.3.2~repack-1) unstable; urgency=medium
 .
   * Reverted to upstream version 5.3.2 (due to VST issues)
 (Closes: #913915)
 .
   * Fixed cmdline flag for Projucer for the autopkgtest
   * Updated licensecheck ignores
Checksums-Sha1:
 e47a748e1b1f524a41a2d1cbe8c5dbfceecafc5f 2559 
juce_5.4.1+really5.3.2~repack-1.dsc
 e0c160ccfe5b6daf2cb99df6f69e1129fa65a9e0 10356546 
juce_5.4.1+really5.3.2~repack.orig.tar.gz
 f257b6e2789a7cabf39b1e49d364f9c372d89155 52816 
juce_5.4.1+really5.3.2~repack-1.debian.tar.xz
 6a17e405efc18bcfae875882df80c4fd6feb7f4f 16587 
juce_5.4.1+really5.3.2~repack-1_amd64.buildinfo
Checksums-Sha256:
 f5316d421b983a196d8074ba71a9a884dde098cd5ecf4b1e50fa2b11b0b796ed 2559 
juce_5.4.1+really5.3.2~repack-1.dsc
 333f73f10009babe9607cfa084785a34821a22a70391f23e28395738dcf8e129 10356546 
juce_5.4.1+really5.3.2~repack.orig.tar.gz
 a2c0bc7e1514d59ff56394e2bef2ef8471fcf59e03af4a22e15096254cbd44ad 52816 
juce_5.4.1+really5.3.2~repack-1.debian.tar.xz
 7f8ae59a4990001a3bce11c7e917be5e9df7ca24934ffb61815b1505d3078e31 16587 
juce_5.4.1+really5.3.2~repack-1_amd64.buildinfo
Files:
 922dec6a19b0817eb83763becd8d936e 2559 devel optional 
juce_5.4.1+really5.3.2~repack-1.dsc
 5ebc86166100a16ff70e804cb6bb1e8f 10356546 devel optional 
juce_5.4.1+really5.3.2~repack.orig.tar.gz
 6d3e4a46955b0b0265dba66231ffcb41 52816 devel optional 
juce_5.4.1+really5.3.2~repack-1.debian.tar.xz
 78c1264ef86fcb660c93ca7301160e59 16587 devel optional 
juce_5.4.1+really5.3.2~repack-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEdAXnRVdICXNIABVttlAZxH96NvgFAlwH+f4ACgkQtlAZxH96
NvicrA/8D1/LszKiCMc5PjCEalVHphm+N1oxxCvsQdt9Rjbq+CL0TmVuNC/ew2JM
G5JaAVFcod2/fO02Ytxidykw5JwQ0l2jBxUHRKY0wlrldGTTDrYKJjNUTW7QHyt/
jh5PN/Szi8NOig1McxerDFBrfD7jda5ezwPYai8LXmMYBSHfYBM0SYYC7e6Ny7j1
1+ciiE5s

Bug#915511: marked as done (ucspi-tcp: package broken)

[Debian Bug Tracking System]

Your message dated Wed, 05 Dec 2018 16:21:15 +
with message-id 
and subject line Bug#915511: fixed in ucspi-tcp 1:0.88-5
has caused the Debian Bug report #915511,
regarding ucspi-tcp: package broken
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.)


-- 
915511: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915511
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ucspi-tcp
Version: 1:0.88-4
Severity: grave

>From /usr/bin/date@:

+---
| /build/ucspi-tcp-J4veAW/ucspi-tcp-0.88/debian/ucspi-tcp/usr/bin/tcpclient 
-RHl0 -- "${1-0}" 13 sh -c 'exec 
/build/ucspi-tcp-J4veAW/ucspi-tcp-0.88/debian/ucspi-tcp/usr/bin/delcr <&6' | 
cat -v
+---

Similar for other scripts.

[ This bug report was sponsored by usrmerge. ]

Ansgar
--- End Message ---
--- Begin Message ---
Source: ucspi-tcp
Source-Version: 1:0.88-5

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

Debian distribution maintenance software
pp.
Dmitry Bogatov  (supplier of updated ucspi-tcp 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, 05 Dec 2018 15:47:18 +
Source: ucspi-tcp
Binary: ucspi-tcp ucspi-tcp-ipv6
Architecture: source
Version: 1:0.88-5
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Bogatov 
Changed-By: Dmitry Bogatov 
Description:
 ucspi-tcp  - command-line tools for building TCP client-server applications
 ucspi-tcp-ipv6 - command-line tools for building TCP client-server 
applications (I
Closes: 915511
Changes:
 ucspi-tcp (1:0.88-5) unstable; urgency=medium
 .
   * Do not include build path into resulting scripts (Closes: #915511)
 + Make upstream build system respect $(DESTDIR) variable
Checksums-Sha1:
 7f1ae6ac0b435f1f27d98bf020f2c66ffdcab4e1 2022 ucspi-tcp_0.88-5.dsc
 1fa46c2863321dfaa9891cc2831394fff7a2bd3a 34544 ucspi-tcp_0.88-5.debian.tar.xz
Checksums-Sha256:
 ce9e45f6144fc4b12aa09e5447c7f3e9ed6198e0efa76aff53ece568bc2fceb1 2022 
ucspi-tcp_0.88-5.dsc
 9176271118683945eff1278b1b244bfc6f4a93d52843d0265e423f4eb69febc1 34544 
ucspi-tcp_0.88-5.debian.tar.xz
Files:
 63a6a4c35548e93cd42ca07f15418c02 2022 net optional ucspi-tcp_0.88-5.dsc
 5bb442e58abe00e115bcbe9a472db870 34544 net optional 
ucspi-tcp_0.88-5.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEEhnHVzDbtdH7ktKj4SBLY3qgmEeYFAlwH86sTHGthY3Rpb25A
ZGViaWFuLm9yZwAKCRBIEtjeqCYR5h6YEACYkGkLNupfLEOBJIpyfSCjinugZdz0
BWLXR34zTc0aMIYFqRDsL9iICKk4OHqHYFRkgT49BuiG3Jrr0OW9N7Vfqv7wlUFR
YYa4Kv66lhCJ6PicWbf+zymnxugmdJQ8vuTdhbhAvYKSjKcovBn2nX2M/sT+y5/G
GiiWEPJJAfy2cSK8OVQbR63FSv+tQqVvjBmcPese2q7tmB3U1GejL0uL9QmFzox2
+rdJ6hmegwxT3KwkdTU48TmA3VYF57b6dcxezyqPM9CWGHN7qz1qqRe+kLtvYyXO
8R3HvSyUt+srJRMJ2f850DkldZQAiXdnLgxLtCTYtmp8IgNJpaa8xKw0LhpQWM76
N5WOjcbrA7yyOVZFIjh5cUwS5Y1Y88CaDSTCgK9mpM4gkiujrTmKOVlDXS5Xfq7f
LA2JPRcH0Cqhp1Cwhzi6df1hkN3bLT3Coxt34pXwVHWWUORA+7XQnrWWVzfuShGA
CnuoHw8UIFeNFhYsYXGRXl9+LdQt/dMncPmzx3m+qD6guJCuQa+UHnH1Ac4oFfS+
hKB480V2DohcWs1Gfn82XctPORH9306cjW3Hn/a8SHXr/JIpvFXcfJ+eENstsGM2
LciYbcMhXd4Ede/WajzrZdMdmTtL+t6+rvIJ/wGFQlDZDsz1QqnBXcfQCDW2kB/W
JkWVsSsZuGfXgA==
=MryS
-END PGP SIGNATURE End Message ---

Bug#915657: google-android-installers NMU binaries cannot be installed due to unchanged version of the binary packages

[Adrian Bunk]

Source: google-android-installers
Version: 1472023576+nmu1
Severity: serious

Your upload included the binary package google-android-platform-21-installer,
version 21+r02, for all, however stable already has version 21+r02.

Processed: reassign 911616 to emacs-nox,emacs-gtk,emacs-lucid, found 911616 in 1:25.2+1-11

[Debian Bug Tracking System]

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

> reassign 911616 emacs-nox,emacs-gtk,emacs-lucid
Bug #911616 [emacs-common] emacs-common: copyright file missing after upgrade 
of emacs-nox from stretch
Bug reassigned from package 'emacs-common' to 'emacs-nox,emacs-gtk,emacs-lucid'.
No longer marked as found in versions emacs/1:25.2+1-11.
Ignoring request to alter fixed versions of bug #911616 to the same values 
previously set
> found 911616 1:25.2+1-11
Bug #911616 [emacs-nox,emacs-gtk,emacs-lucid] emacs-common: copyright file 
missing after upgrade of emacs-nox from stretch
Marked as found in versions emacs/1:25.2+1-11.
> thanks
Stopping processing here.

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

Bug#915653: python-pytest-timeout FTBFS with Python 3.7

[Adrian Bunk]

Source: python-pytest-timeout
Version: 1.3.1-1
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-pytest-timeout.html

...
= test session starts ==
platform linux -- Python 3.7.1, pytest-3.10.1, py-1.7.0, pluggy-0.8.0
rootdir: /build/1st/python-pytest-timeout-1.3.1, inifile: tox.ini
plugins: timeout-1.3.1
collected 35 items

test_pytest_timeout.py ..F..F.F.F.F..F.F.F.F..FF..F..s   [100%]

=== FAILURES ===
_ test_thread __

testdir = 

def test_thread(testdir):
testdir.makepyfile("""
import time

def test_foo():
time.sleep(2)
""")
result = testdir.runpytest('--timeout=1', '--timeout-method=thread')
result.stderr.fnmatch_lines([
'*++ Timeout ++*',
'*~~ Stack of MainThread* ~~*',
'*File *, line *, in *',
>   '*++ Timeout ++*',
])
E   Failed: remains unmatched: '*++ Timeout ++*'

/build/1st/python-pytest-timeout-1.3.1/test_pytest_timeout.py:61: Failed
- Captured stdout call -
running: /usr/bin/python3 -mpytest 
--basetemp=/tmp/pytest-of-pbuilder1/pytest-0/test_thread0/runpytest-0 
--timeout=1 --timeout-method=thread
 in: /tmp/pytest-of-pbuilder1/pytest-0/test_thread0
...
= 12 failed, 22 passed, 1 skipped, 2 warnings in 90.64 seconds =
make[1]: *** [debian/rules:25: override_dh_auto_test] Error 1

Bug#911616: emacs-common: copyright file missing after upgrade of emacs-nox from stretch

[Andreas Beckmann]

On Mon, 22 Oct 2018 17:49:39 +0200 Andreas Beckmann  wrote:
> This does not seem to be the typical dir_to_symlink problem.

It is. Just badly handled so that it became hard to recognize.

from emacs-nox.preinst:

doc_dir=/usr/share/doc/emacs-nox
case "$1" in
install|upgrade)
# Before the unversioning, emacs-{gtk,lucid,nox} packages were
# in a different source package (emacs-defaults) and were arch
# all, and dpkg can't handle dir to symlink transitions.
rm -rf "$doc_dir"
;;

There is dpkg-maintscript-helper for this task.

You most likely want to drop the .preinst and create
emacs-nox.maintscript instead with this content (one line):

< 8< debian/emacs-nox.maintscript >
dir_to_symlink /usr/share/doc/emacs-nox emacs-common 1:25.2+1-12~
< >8 >

and do the same for -gtk and -lucid with adjusted paths.


Andreas

Processed: user debian...@lists.debian.org, usertagging 902513, affects 902513

[Debian Bug Tracking System]

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

> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 902513 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 902513 + python3-openturns
Bug #902513 [src:openturns] openturns: FTBFS in buster/sid (nlopt.hpp: No such 
file or directory)
Added indication that 902513 affects python3-openturns
> thanks
Stopping processing here.

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

Bug#915654: pyavm FTBFS: test failure

[Adrian Bunk]

Source: pyavm
Version: 0.9.4-2
Severity: serious
Tags: ftbfs

Some recent change in unstable makes pyavm FTBFS:

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

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/pyavm-0.9.4'
python2 -m pytest
= test session starts ==
platform linux2 -- Python 2.7.15+, pytest-3.10.1, py-1.7.0, pluggy-0.8.0
rootdir: /build/1st/pyavm-0.9.4, inifile:
collected 712 items

pyavm/tests/test_avm.py  [  0%]
pyavm/tests/test_header.py   [  1%]
pyavm/tests/test_io.py . [  8%]
 [ 18%]
 [ 28%]
 [ 38%]
...  [ 42%]
pyavm/tests/test_main.py ... [ 48%]
 [ 58%]
 [ 68%]
 [ 79%]
 [ 89%]
..   [ 92%]
pyavm/tests/test_specs.py ..F[ 93%]
pyavm/tests/test_wcs_utils.py .. [ 99%]
..   [100%]

=== FAILURES ===
_ test_warning _

def test_warning():

# Start of with a version=1.2 AVM object
a = AVM(version=1.2)
a.ProposalID = ["25661"]

# Then change to version=1.1, which doesn't contain ProposalID
with warnings.catch_warnings(record=True) as w:
a.MetadataVersion = 1.1
>   assert len(w) == 1
E   assert 0 == 1
E+  where 0 = len([])

pyavm/tests/test_specs.py:118: AssertionError
...
== 1 failed, 711 passed, 25 warnings in 9.45 seconds ===
make[1]: *** [debian/rules:11: override_dh_auto_test] Error 1

Bug#899309: autofill-forms: Replace it with non legacy autofillforms-e10 to be compatible with ff 60.

[Sascha Girrulat]

Hi,

yes, i do.

Regards
Sascha

Am 4. Dezember 2018 00:00:35 MEZ schrieb "Moritz Mühlenhoff" :
>On Tue, May 22, 2018 at 03:57:10PM +0200, Sascha Girrulat wrote:
>> Source: autofill-forms
>> Version: 1.1.3-1
>> Severity: normal
>> 
>> Dear Maintainer,
>> 
>> the current version is not compatible with webextensions api but
>there
>> is a never version[1] called autofillforms-e10s. We should replace
>the
>> current with this version.
>
>Does anyone intend/plan to switch the package to the web extention?
>Otherwise it should be removed from the archive.
>
>Cheers,
>Moritz

-- 
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

Bug#914897: #914897: debootstrap, buster: Please disabled merged /usr by default

[Gunnar Wolf]

Ansgar Burchardt dijo [Wed, Dec 05, 2018 at 08:17:56AM +0100]:
> The Reproducible Builds project was so kind to help and now runs one
> build in a non-merged-/usr and a second build in a merged-/usr
> environment.  Packages that hardcode the path to utilities, but would
> pick up the wrong one in a merged-/usr environment will result in a
> difference between the two builds and can thus be found.
> 
> See [1] for an overview of issues found this way; as the entire archive
> was already rebuilt in this setup, there shouldn't be many more issues
> of this type that we don't know about[2].
> (...)

Thanks for this report, Ansgar. This clearly sums up the issue. I am
amazed the whole archive managed to be rebuilt on such a short time!

I guess the next step is to file the multiple bugs pending to be
filed.

> Bug reports were already submitted for over half the packages, often
> including a simple patch (usually something like adding BASH=/bin/bash
> to dh_auto_configure).
> 
> So we look to be on a good track to address the remaining issues.

...And I guess this points towards the Technical Committee not having
to intervene in the issue. Which is, IMO, the best possible outcome.

Thanks to everybody following through with this!

Bug#915650: openjdk-12: don't release with Buster

[Jeremy Bicha]

Source: openjdk-12
Version: 12~22-1
Severity: serious

Since Oracle will only support Java 12 until September 2019, it
doesn't make sense to include it in the Buster release (or in Ubuntu
19.04 in my opinion).

We'll be shipping Java 11 LTS instead.

https://www.oracle.com/technetwork/java/java-se-support-roadmap.html

Thanks,
Jeremy Bicha

Bug#915019: libreoffice-mysql-connector: copyright file missing after upgrade (policy 12.5)

[Andreas Beckmann]

On 2018-11-29 22:53, Rene Engelhard wrote:
>> Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
> 
> Please update your template :)

Thanks, fixed.


Andreas

Bug#914897: debating the wrong thing

[Gunnar Wolf]

Svante Signell dijo [Wed, Dec 05, 2018 at 02:03:19PM +0100]:
> > If we keep merged-/usr as default then we can /recommend/ people to
> > install usrmerge to switch to merged-/usr; reducing the difference
> > between newly-installed and existing setups is a good idea IMHO.  I
> > think I filed a report for this two years ago.
> > 
> > Maybe we should also mention somewhere that it might be useful to not
> > switch build environments (yet).
> 
> How about this case:
> 
> - Make as default non merged-/usr for all buildds.
> - Make a choice of non merged-/usr or merged-/usr in the installer.
> - Users wanting merged-/usr install the usrmerge package and convert to 
> merged-
> /usr.
> 
> - We have two alternatives here:
> 1) For those not wanting merged-/usr: 
>All is fine.
> 
> 2) For those having merged-/usr installed:
>Re-run usrmerge to convert all newly installed packages to merged-/usr.
>Is this possible or is installing that package a install-once-only?

AFAICT, this would mostly cover the issues, at least as far as I
understand them. There is still one extra point: Computers used by
Debian contributors to build their packages on. If I build my package
on a merged-/usr system, it might end up breaking in non-merged
systems.

Throwaway binary uploads seems like a safe bet for this issue. Now -
Are we ready to do it?


signature.asc
Description: PGP signature

Bug#915646: FTBFS: haddock: internal error: internal: extractDecl

[Ilias Tsitsimpis]

Source: haskell-esqueleto
Version: 2.5.3.git20180402-3
Severity: serious
Justification: fails to build from source (but built successfully in the past)

libghc-esqueleto-doc FTBFS with the following error:

   haddock: internal error: internal: extractDecl

This is most probably a Haddock bug[1], fixed in a newer version of GHC.

On the other hand, haskell-esqueleto is not currently needed, is not
part of the latest LTS, and Debian uses an unpublished snapshot of the
code[2]. Should we remove this package from Debian?

[1] https://github.com/haskell/haddock/issues/775
[2] https://github.com/bitemyapp/esqueleto/issues/105

-- 
Ilias

Bug#812574: ubuntu bug 564853

[Scott Moser]

This is also reported in ubuntu bug 564853
(https://bugs.launchpad.net/bugs/564853).
There is a recreate script attached to the bug there.

As diagnosed there, the prompt will occur if the user has made *both*:
a. changes to grub-pc.postinst fields:
  GRUB_CMDLINE_LINUX, GRUB_CMDLINE_LINUX_DEFAULT, GRUB_TIMEOUT,
GRUB_HIDDEN_TIMEOUT
b. any other changes

Bug#915624: marked as done (mupen64plus-video-z64 FTBFS with glew 2.1.0)

[Debian Bug Tracking System]

Your message dated Wed, 05 Dec 2018 14:54:28 +
with message-id 
and subject line Bug#915624: fixed in mupen64plus-video-z64 2.0.0+13+g72af4f0-7
has caused the Debian Bug report #915624,
regarding mupen64plus-video-z64 FTBFS with glew 2.1.0
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.)


-- 
915624: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915624
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mupen64plus-video-z64
Version: 2.0.0+13+g72af4f0-6
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/mupen64plus-video-z64.html

...
In file included from ../../src/glshader.cpp:39:
/usr/include/GL/glext.h:12066:105: error: conflicting declaration 'typedef void 
(* PFNGLFRAGMENTLIGHTFVSGIXPROC)(GLenum, GLenum, const GLfloat*)'
 typedef void (APIENTRYP PFNGLFRAGMENTLIGHTFVSGIXPROC) (GLenum light, GLenum 
pname, const GLfloat *params);

 ^
In file included from ../../src/glshader.cpp:22:
/usr/include/GL/glew.h:18734:28: note: previous declaration as 'typedef void (* 
PFNGLFRAGMENTLIGHTFVSGIXPROC)(GLenum, GLenum, GLfloat*)'
 typedef void (GLAPIENTRY * PFNGLFRAGMENTLIGHTFVSGIXPROC) (GLenum light, GLenum 
pname, GLfloat* params);
^~~~
...
--- End Message ---
--- Begin Message ---
Source: mupen64plus-video-z64
Source-Version: 2.0.0+13+g72af4f0-7

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

Debian distribution maintenance software
pp.
Sven Eckelmann  (supplier of updated mupen64plus-video-z64 
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, 05 Dec 2018 15:05:56 +0100
Source: mupen64plus-video-z64
Binary: mupen64plus-video-z64
Architecture: source amd64
Version: 2.0.0+13+g72af4f0-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Sven Eckelmann 
Description:
 mupen64plus-video-z64 - low-level rdp emulation for mupen64plus
Closes: 915624
Changes:
 mupen64plus-video-z64 (2.0.0+13+g72af4f0-7) unstable; urgency=medium
 .
   * debian/patches:
 - Add Replace-glext-with-glew.patch, Replace glext with glew
   (Closes: #915624)
Checksums-Sha1:
 9141a0637f9c0c0e33252aff7c94a55e5b14a770 2300 
mupen64plus-video-z64_2.0.0+13+g72af4f0-7.dsc
 60f3ef94d538ce8ee5425ac525bc424304aacb63 12440 
mupen64plus-video-z64_2.0.0+13+g72af4f0-7.debian.tar.xz
 c3d42cd1ec4da01b5f79dd3f1d116908c0289b84 750060 
mupen64plus-video-z64-dbgsym_2.0.0+13+g72af4f0-7_amd64.deb
 d6307a074547e6ce4d639255b313fe6c4beb33dc 10708 
mupen64plus-video-z64_2.0.0+13+g72af4f0-7_amd64.buildinfo
 0de62d41b1bf11c832d96250833b7dd070bd9893 40428 
mupen64plus-video-z64_2.0.0+13+g72af4f0-7_amd64.deb
Checksums-Sha256:
 ad0024f1717b4042a7cf33ebcae487eb3fe456969d9c28b0843fffa95b25fa8c 2300 
mupen64plus-video-z64_2.0.0+13+g72af4f0-7.dsc
 0aaa567dabf4cc7d5d5648cce296cc57c702eafc1546898bcbfacf7a6c2c8987 12440 
mupen64plus-video-z64_2.0.0+13+g72af4f0-7.debian.tar.xz
 311670b24a7af378d71c33c708d044be85416ed741ffc51f2d57e2d5b0a523bc 750060 
mupen64plus-video-z64-dbgsym_2.0.0+13+g72af4f0-7_amd64.deb
 3fcf5c0e198dd1394b21ccd52d20c49749c337404473451208c859d0c682785f 10708 
mupen64plus-video-z64_2.0.0+13+g72af4f0-7_amd64.buildinfo
 067110f310c155fd9ed1df6de2120f6057288e98037191030b0438c698da3d3e 40428 
mupen64plus-video-z64_2.0.0+13+g72af4f0-7_amd64.deb
Files:
 c7af27848a87f006a00fe41fe4023b05 2300 games optional 
mupen64plus-video-z64_2.0.0+13+g72af4f0-7.dsc
 506c7c9bdd1b56d878fae61daf275a40 12440 games optional 
mupen64plus-video-z64_2.0.0+13+g72af4f0-7.debian.tar.xz
 e9b78bfc026beb51f7682b6ad9b9e8bd 750060 debug optional 
mupen64plus-video-z64-dbgsym_2.0.0+13+g72af4f0-7_amd64.deb
 e423442d10def58890f81eb76b136c42 10708 games optional 
mupen64plus-video-z64_2.0.0+13+g72af4f0-7_amd64.buildinfo
 0a872a02229e4d4563f9cacde9852121 40428 games optional 
mupen64plus-video-z64_2.0.0+13+g72af4f0-7_amd64.deb

-BEGIN PGP

Processed: affects 915603

[Debian Bug Tracking System]

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

> affects 915603 python3-pgmagick
Bug #915603 [libgraphicsmagick++-q16-12] libgraphicsmagick++-q16-12: Requires 
soname/shlibs bump for libstdc++11 transition
Bug #915606 [libgraphicsmagick++-q16-12] libgraphicsmagick++-q16-12: Requires 
soname/shlibs bump for C++11 ABI changes
Added indication that 915603 affects python3-pgmagick
Added indication that 915606 affects python3-pgmagick
> thanks
Stopping processing here.

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

Processed: severity of 915603 is serious

[Debian Bug Tracking System]

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

> severity 915603 serious
Bug #915603 [libgraphicsmagick++-q16-12] libgraphicsmagick++-q16-12: Requires 
soname/shlibs bump for libstdc++11 transition
Bug #915606 [libgraphicsmagick++-q16-12] libgraphicsmagick++-q16-12: Requires 
soname/shlibs bump for C++11 ABI changes
Severity set to 'serious' from 'important'
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: severity of 915633 is important

[Debian Bug Tracking System]

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

> severity 915633 important
Bug #915633 [src:pcc-libs] pcc-libs: FTBFS on !amd64
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#900160: marked as done (ruby-eventmachine: FTBFS against openssl 1.1.1)

[Debian Bug Tracking System]

Your message dated Wed, 05 Dec 2018 13:52:17 +
with message-id 
and subject line Bug#900160: fixed in ruby-eventmachine 1.0.7-4.2
has caused the Debian Bug report #900160,
regarding ruby-eventmachine: FTBFS against openssl 1.1.1
to be marked as done.

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

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


-- 
900160: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900160
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-eventmachine
Version: 1.0.7-4
Severity: important
User: pkg-openssl-de...@lists.alioth.debian.org
Usertags: openssl-1.1.1

The new openssl 1.1.1 is currently in experimental [0]. This package
failed to build against this new package [1] while it built fine against
the openssl version currently in unstable [2].
Could you please have a look?

The Error
|TestSSLMethods: 
|  test_ssl_methods:
140136548670336:error:140AB18F:SSL routines:SSL_CTX_use_certificate:ee key too 
small:../ssl/ssl_rsa.c:310:
|ruby2.5: ssl.cpp:173: SslContext_t::SslContext_t(bool, const string&, const 
string&): Assertion `e > 0' failed.
|Aborted

is due to:
1.1.1~~pre6-1 changelog):
|   * Increase default security level from 1 to 2. This moves from the 80 bit
| security level to the 112 bit securit level and will require 2048 bit RSA
| and DHE keys.

[0] https://lists.debian.org/msgid-search/20180501211400.ga21...@roeckx.be
[1] 
https://breakpoint.cc/openssl-rebuild/2018-05-03-rebuild-openssl1.1.1-pre6/attempted/ruby-eventmachine_1.0.7-4_amd64-2018-05-01T21%3A04%3A28Z
[2] 
https://breakpoint.cc/openssl-rebuild/2018-05-03-rebuild-openssl1.1.1-pre6/successful/ruby-eventmachine_1.0.7-4_amd64-2018-05-02T18%3A51%3A11Z

Sebastian
--- End Message ---
--- Begin Message ---
Source: ruby-eventmachine
Source-Version: 1.0.7-4.2

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

Debian distribution maintenance software
pp.
Dimitri John Ledkov  (supplier of updated ruby-eventmachine 
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, 05 Dec 2018 12:54:17 +
Source: ruby-eventmachine
Binary: ruby-eventmachine
Architecture: source
Version: 1.0.7-4.2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Dimitri John Ledkov 
Description:
 ruby-eventmachine - Ruby/EventMachine library
Closes: 900160
Changes:
 ruby-eventmachine (1.0.7-4.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Revert below upload and build with OpenSSL 1.1+.
   * Add a patch to clamp SSL version to TLS1.2, and allow using small
 keys, as the rest of the codebase is not ready for TLS1.3. (Closes:
 #900160)
Checksums-Sha1:
 45d1b205cafb28c4cacc88ca14d447accff44558 1962 ruby-eventmachine_1.0.7-4.2.dsc
 165aef3f7d0596dde802aab62420b1cf44580b64 7052 
ruby-eventmachine_1.0.7-4.2.debian.tar.xz
 b4e049f24baa676b9be6ad792b4d75b6d6d11932 6274 
ruby-eventmachine_1.0.7-4.2_source.buildinfo
Checksums-Sha256:
 5ba27551c22f3bcaa1ea3a1b4798f5358aa8758c9ae7eea47133dfb5bcd0f530 1962 
ruby-eventmachine_1.0.7-4.2.dsc
 738047c5b87fe534e37ea70c7b6f86306abb8f87b361642aa22d7f2debd9ed97 7052 
ruby-eventmachine_1.0.7-4.2.debian.tar.xz
 7f113986b227f6475567cab9356916d5595469cf65c2521985b560c07421a575 6274 
ruby-eventmachine_1.0.7-4.2_source.buildinfo
Files:
 5c00cd7579e8f1437195d7b30d41717a 1962 ruby optional 
ruby-eventmachine_1.0.7-4.2.dsc
 09e0f392a1b897e6a2c29d5e9de68239 7052 ruby optional 
ruby-eventmachine_1.0.7-4.2.debian.tar.xz
 d7a35b709bb69ae1d64a1a4224a8adc8 6274 ruby optional 
ruby-eventmachine_1.0.7-4.2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFEBAEBCgAuFiEEdzyZ69ChEXIhenw/ysLYuc0spfkFAlwH0UEQHHhub3hAZGVi
aWFuLm9yZwAKCRDKwti5zSyl+aAXCACatlLs9nz+jTwX8+vlr+aeu52s+JnmWFZa
QtByPomx9xro2LCr8h+lWIXxtl0cgG3Ksd7C82HaBZH7gqzj4Zn/DNhPPSa82p7q
+AjqEzwGWNxfEti/Dr2KXIu6N+YBRBPpH76C5Q91LPAxV9zSNcNlMEd+8Vel+g/a
69IvnXwXKRiapvARq6dLnAupx3hX66YHwseQNZo65GZ88I6GKzighzjX8FEFQ/WS
VQ3YIsRnW3TejyD+uMSBpLjwnyOxvnhFZ5/eemPPe1Jghq/yszeilZYCVM+L6FPv
npmhvHJq+fm/C2XhA6EhMkFuuV3ekwf10AO9kArKh

Bug#915642: AuthBasicProvider PAM crashes apache

[Christoph Berg]

Package: libapache2-mod-authnz-pam
Version: 1.2.0-1
Severity: grave

Hi,

we were using libapache2-mod-authnz-pam for apache2 basic
authentication in the elephant-shed.io project, but some time ago,
apache2 started crashing when it is used. (Could be related to the
1.2.0-1 upload, not sure.)

I can reproduce it with this /etc/apache2/sites-enabled/default.conf:


# The ServerName directive sets the request scheme, hostname and port 
that
# the server uses to identify itself. This is used when creating
# redirection URLs. In the context of virtual hosts, the ServerName
# specifies what hostname must appear in the request's Host: header to
# match this virtual host. For the default virtual host (this file) this
# value is not decisive as it is used as a last resort host regardless.
# However, you must set it for any further virtual host explicitly.
#ServerName www.example.com

ServerAdmin webmaster@localhost
DocumentRoot /var/www/html

# Available loglevels: trace8, ..., trace1, debug, info, notice, warn,
# error, crit, alert, emerg.
# It is also possible to configure the loglevel for particular
# modules, e.g.
#LogLevel info ssl:warn

ErrorLog ${APACHE_LOG_DIR}/error.log
CustomLog ${APACHE_LOG_DIR}/access.log combined

# For most configuration files from conf-available/, which are
# enabled or disabled at a global level, it is possible to
# include a line for only one particular virtual host. For example the
# following line enables the CGI configuration for this host only
# after it has been globally disabled with "a2disconf".
#Include conf-available/serve-cgi-bin.conf


AuthType Basic
AuthName "PAM Authentication"
AuthBasicProvider PAM




# vim: syntax=apache ts=4 sw=4 sts=4 sr noet


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (700, 'testing'), (600, 'unstable'), (150, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages libapache2-mod-authnz-pam depends on:
ii  apache2-bin [apache2-api-20120211]  2.4.37-1
ii  libc6   2.27-8
ii  libpam0g1.1.8-3.8

libapache2-mod-authnz-pam recommends no packages.

libapache2-mod-authnz-pam suggests no packages.

-- no debconf information

Christoph

Processed: forwarded 915638

[Debian Bug Tracking System]

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

> forwarded 915638 https://github.com/Blosc/bloscpack/issues/89
Bug #915638 [bloscpack] bloscpack: FTBFS on i386: FAIL: 
test_numpy_io.test_itemsize_chunk_size_mismatch
Set Bug forwarded-to-address to 'https://github.com/Blosc/bloscpack/issues/89'.
> thanks
Stopping processing here.

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

Bug#915640: spyder-reports FTBFS with spyder 3.3.2+dfsg1-1

[Adrian Bunk]

Source: spyder-reports
Version: 0.1.1-1
Severity: serious
Tags: ftbfs

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

...
   dh_auto_test -O--buildsystem=pybuild
I: pybuild base:217: cd 
/build/1st/spyder-reports-0.1.1/.pybuild/cpython3_3.6_spyder-reports/build; 
python3.6 -m pytest 
= test session starts ==
platform linux -- Python 3.6.7, pytest-3.10.1, py-1.7.0, pluggy-0.8.0 -- 
/usr/bin/python3.6
cachedir: .pytest_cache
PyQt5 5.11.3 -- Qt runtime 5.11.2 -- Qt compiled 5.11.2
rootdir: /build/1st/spyder-reports-0.1.1, inifile: setup.cfg
plugins: xvfb-1.0.0, qt-2.3.1, cov-2.6.0
collecting ... 
 ERRORS 
 ERROR collecting 
.pybuild/cpython3_3.6_spyder-reports/build/spyder_reports/tests/test_plugin.py 
ImportError while importing test module 
'/build/1st/spyder-reports-0.1.1/.pybuild/cpython3_3.6_spyder-reports/build/spyder_reports/tests/test_plugin.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
spyder_reports/__init__.py:11: in 
from .reportsplugin import ReportsPlugin
spyder_reports/reportsplugin.py:34: in 
from spyder.utils.programs import TEMPDIR
E   ImportError: cannot import name 'TEMPDIR'
=== 1 error in 0.47 seconds 
E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: cd 
/build/1st/spyder-reports-0.1.1/.pybuild/cpython3_3.6_spyder-reports/build; 
python3.6 -m pytest 
dh_auto_test: pybuild --test --test-pytest -i python{version} -p "3.6 3.7" 
returned exit code 13
make: *** [debian/rules:10: build] Error 25

Bug#915638: bloscpack: FTBFS on i386: FAIL: test_numpy_io.test_itemsize_chunk_size_mismatch

[Daniel Stender]

Package: bloscpack
Version: 0.15.0-1
Severity: serious
Justification: fails to build from source

Building on i386 there are two test failures:


==
FAIL: test_numpy_io.test_itemsize_chunk_size_mismatch(, , array([  0,   1,   2,   3,   4,   5,   6,   7,   8,   9,  10,  
11,  12,
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
AssertionError: ChunkSizeTypeSizeMismatch not raised by pack_ndarray_str

==
FAIL: test_numpy_io.test_itemsize_chunk_size_mismatch(, , array([  0,   1,   2,   3,   4,   5,   6,   7,   8,   9,  10,  
11,  12,
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
AssertionError: ChunkSizeTypeSizeMismatch not raised by pack_ndarray_str

--
Ran 582 tests in 7.203s

FAILED (failures=2)


DS

-- System Information:
Debian Release: 9.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

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

Versions of packages bloscpack depends on:
ii  python33.5.3-1
ii  python3-blosc  1.4.4+ds1-3
ii  python3-numpy  1:1.12.1-3
ii  python3-six1.10.0-3

bloscpack recommends no packages.

bloscpack suggests no packages.

-- no debconf information