Bug#906626: mypy failure

[Salvo Tomaselli]

Hello,

thanks for your report. It is indeed failing to build, due to a newer
version of mypy that fails.

I suspect this is actually an issue with mypy,

See this example

NONETYPE = type(None)

def f(a) -> None:
if type(a) == NONETYPE:
pass

I will contact the mypy upstream about this.

But I intend to make a typedload update to workaround this.

Best

-- 
Salvo Tomaselli

"Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di
senso, ragione ed intelletto intendesse che noi ne facessimo a meno."
-- Galileo Galilei

http://ltworf.github.io/ltworf/

Bug#906508: marked as done (riemann-c-client: FTBFS in buster/sid (riemann/proto/riemann.pb-c.h: No such file or directory))

[Debian Bug Tracking System]

Your message dated Mon, 20 Aug 2018 07:23:12 +0200
with message-id <87muthwr0f.fsf@debian>
and subject line Re: riemann-c-client: FTBFS in buster/sid 
(riemann/proto/riemann.pb-c.h: No such file or directory)
has caused the Debian Bug report #906508,
regarding riemann-c-client: FTBFS in buster/sid (riemann/proto/riemann.pb-c.h: 
No such file or directory)
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.)


-- 
906508: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906508
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:riemann-c-client
Version: 1.9.1-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-arch
dh build-arch --no-parallel
   dh_testdir -a
   dh_update_autotools_config -a
   dh_autoreconf -a
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:17: installing './compile'

[... snipped ...]

checking for memset... yes
checking for socket... yes
checking for strcasecmp... yes
checking for strchr... yes
checking for strdup... yes
checking for strerror... yes
checking for stdlib.h... (cached) yes
checking for GNU libc compatible malloc... yes
checking for stdlib.h... (cached) yes
checking for GNU libc compatible realloc... yes
checking for size_t... yes
checking for uint32_t... yes
checking for uint8_t... yes
checking for int64_t... yes
checking for ssize_t... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for PROTOBUF_C... yes
checking for CHECK... yes
checking for JSON_C... yes
checking for GNUTLS... yes
checking whether /usr/bin/ld -m elf_x86_64 supports symbol version scripts... 
yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating lib/riemann/riemann-client.h
config.status: creating lib/riemann/riemann-client.pc
config.status: creating lib/riemann/platform.h
config.status: executing depfiles commands
config.status: executing libtool commands
configure: WARNING: unrecognized options: --disable-maintainer-mode
make[1]: Leaving directory '/<>'
   dh_auto_build -a
cd debian/build-tree && make -j1
make[1]: Entering directory '/<>/debian/build-tree'
gcc -DHAVE_CONFIG_H -I. -I../.. -I./lib/riemann   -Wdate-time 
-D_FORTIFY_SOURCE=2 -I../../lib -I./lib -I/usr/include/json-c  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o src/riemann_client-riemann-client.o `test -f 
'src/riemann-client.c' || echo '../../'`src/riemann-client.c
In file included from ./lib/riemann/riemann-client.h:23,
 from ../../src/riemann-client.c:18:
../../lib/riemann/attribute.h:21:10: fatal error: riemann/proto/riemann.pb-c.h: 
No such file or directory
 #include 
  ^~
compilation terminated.
make[1]: *** [Makefile:1091: src/riemann_client-riemann-client.o] Error 1
make[1]: Leaving directory '/<>/debian/build-tree'
dh_auto_build: cd debian/build-tree && make -j1 returned exit code 2
make: *** [debian/rules:16: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


The build was made with "dpkg-buildpackage -B" in my autobuilder.
Most probably, it also fails here in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/riemann-c-client.html

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Version: 1.10.3-1

Thank you for reporting the FTBFS, I tracked it down to stupid
dependency specification in the Makefile. I released a new upstream
version correcting the issue (among a few other tiny bugs), and uploaded
1.10.3-1 last night, which contains the fix.

-- 
|8]--- End Message ---

Bug#899528: marked as done (graphite-api: Invalid maintainer address pkg-graphite-ma...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Mon, 20 Aug 2018 08:02:25 +0300
with message-id <20180820050225.GX4164@localhost>
and subject line Already fixed in unstable
has caused the Debian Bug report #899528,
regarding graphite-api: Invalid maintainer address 
pkg-graphite-ma...@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.)


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

Dear uploader of graphite-api,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package graphite-api since the list address
pkg-graphite-ma...@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-graphite-ma...@lists.alioth.debian.org is 5.

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 ---
Version: 1.1.3-3

graphite-api (1.1.3-3) unstable; urgency=medium

  * d/control: fix maintainer address to use tracker.debian.org.
...
 -- Vincent Bernat   Wed, 25 Jul 2018 08:40:41 +0200


cu
Adrian

-- 

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

Processed: fixed 899751 in 4.12.5-1

[Debian Bug Tracking System]

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

> fixed 899751 4.12.5-1
Bug #899751 {Done: Yves-Alexis Perez } [src:xfwm4] xfwm4: 
Invalid maintainer address pkg-xfce-de...@lists.alioth.debian.org
Marked as fixed in versions xfwm4/4.12.5-1.
> thanks
Stopping processing here.

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

Processed: le: diff for NMU version 1.16.5-0.1

[Debian Bug Tracking System]

Processing control commands:

> tags 868609 + pending
Bug #868609 [src:le] le FTBFS with latest ncurses
Added tag(s) pending.

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

Bug#906714: paraview: FTBFS in Sid

[Simon Quigley]

Package: paraview
Severity: serious

Dear Maintainer,

Your package fails to build from source in Sid. Here is the build log
after LocutusOfBorg triggered the build in debomatic:

http://debomatic-amd64.debian.net/distribution#unstable/paraview/5.4.1+dfsg4-3/buildlog

Please fix this.

Thanks.

-- 
Simon Quigley
tsimo...@ubuntu.com
tsimonq2 on freenode and OFTC
5C7A BEA2 0F86 3045 9CC8
C8B5 E27F 2CF8 458C 2FA4



signature.asc
Description: OpenPGP digital signature

Processed: shiboken: diff for NMU version 1.2.2-5.1

[Debian Bug Tracking System]

Processing control commands:

> tags 892402 + patch
Bug #892402 [src:shiboken] shiboken: build-depends on GCC 6
Added tag(s) patch.
> tags 892402 + pending
Bug #892402 [src:shiboken] shiboken: build-depends on GCC 6
Added tag(s) pending.

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

Bug#892402: shiboken: diff for NMU version 1.2.2-5.1

[Adrian Bunk]

Control: tags 892402 + patch
Control: tags 892402 + pending

Dear maintainer,

I've prepared an NMU for shiboken (versioned as 1.2.2-5.1) and uploaded 
it to DELAYED/15. Please feel free to tell me if I should cancel it.

cu
Adrian

-- 

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

diff -Nru shiboken-1.2.2/debian/changelog shiboken-1.2.2/debian/changelog
--- shiboken-1.2.2/debian/changelog	2017-08-18 21:42:31.0 +0300
+++ shiboken-1.2.2/debian/changelog	2018-08-20 05:22:26.0 +0300
@@ -1,3 +1,11 @@
+shiboken (1.2.2-5.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop the g++-6 build dependency on mips64el,
+the gcc bug is fixed. (Closes: #892402)
+
+ -- Adrian Bunk   Mon, 20 Aug 2018 05:22:26 +0300
+
 shiboken (1.2.2-5) unstable; urgency=medium
 
   * Team upload.
diff -Nru shiboken-1.2.2/debian/control shiboken-1.2.2/debian/control
--- shiboken-1.2.2/debian/control	2017-08-18 21:42:31.0 +0300
+++ shiboken-1.2.2/debian/control	2018-08-20 05:22:26.0 +0300
@@ -11,9 +11,7 @@
  python-all-dev (>= 2.6.6-3), python-all-dbg (>= 2.6.6-3),
  python-numpy, python-numpy-dbg,
  python3-all-dev, python3-all-dbg,
- python3-numpy, python3-numpy-dbg,
-# Use gcc-6 on mips64el, to drop once #871514 is fixed
- g++-6 [mips64el]
+ python3-numpy, python3-numpy-dbg
 Build-Depends-Indep: python-sphinx
 X-Python-Version: >= 2.6
 X-Python3-Version: >= 3.3
diff -Nru shiboken-1.2.2/debian/rules shiboken-1.2.2/debian/rules
--- shiboken-1.2.2/debian/rules	2017-08-18 21:42:31.0 +0300
+++ shiboken-1.2.2/debian/rules	2018-08-20 05:22:26.0 +0300
@@ -15,14 +15,6 @@
 CMAKE_COMMON_OPTIONS := -DCMAKE_SKIP_RPATH=true \
 			-DLIB_SUFFIX=/$(DEB_HOST_MULTIARCH)
 
-# Use gcc-6 on mips64el, to drop once #871514 is fixed
-DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH)
-ifeq ($(DEB_HOST_ARCH),mips64el)
-	export CC=gcc-6
-	export GCC=gcc-6
-	export CXX=g++-6
-endif
-
  CONFIGURE 
 
 override_dh_auto_configure: configure_2 configure_3

Bug#897532: marked as done (python-memprof: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 3.6 returned exit code 13)

[Debian Bug Tracking System]

Your message dated Mon, 20 Aug 2018 05:15:40 +0300
with message-id <20180820021540.GA7066@localhost>
and subject line Re: Bug#897532: python-memprof: FTBFS: dh_auto_test: pybuild 
--test -i python{version} -p 3.6 returned exit code 13
has caused the Debian Bug report #897532,
regarding python-memprof: FTBFS: dh_auto_test: pybuild --test -i 
python{version} -p 3.6 returned exit code 13
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.)


-- 
897532: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897532
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-memprof
Version: 0.3.4-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20180502 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
>  debian/rules build
> dh build --with python2,python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:217: python2.7 setup.py config 
> running config
> I: pybuild base:217: python3.6 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:217: /usr/bin/python setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython2_2.7_memprof/build/memprof
> copying memprof/memprof.py -> 
> /<>/.pybuild/cpython2_2.7_memprof/build/memprof
> copying memprof/mp_utils.py -> 
> /<>/.pybuild/cpython2_2.7_memprof/build/memprof
> copying memprof/__init__.py -> 
> /<>/.pybuild/cpython2_2.7_memprof/build/memprof
> copying memprof/__main__.py -> 
> /<>/.pybuild/cpython2_2.7_memprof/build/memprof
> running build_ext
> cythoning memprof/getsize.pyx to memprof/getsize.c
> building 'memprof.getsize' extension
> creating build
> creating build/temp.linux-amd64-2.7
> creating build/temp.linux-amd64-2.7/memprof
> x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall 
> -Wstrict-prototypes -fno-strict-aliasing -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
> -I/usr/include/python2.7 -c memprof/getsize.c -o 
> build/temp.linux-amd64-2.7/memprof/getsize.o
> x86_64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions 
> -Wl,-z,relro -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall 
> -Wstrict-prototypes -Wdate-time -D_FORTIFY_SOURCE=2 -g 
> -fdebug-prefix-map=/build/python2.7-jgBwco/python2.7-2.7.15=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
> build/temp.linux-amd64-2.7/memprof/getsize.o -o 
> /<>/.pybuild/cpython2_2.7_memprof/build/memprof/getsize.so
> running build_scripts
> creating build/scripts-2.7
> copying and adjusting scripts/mp_plot -> build/scripts-2.7
> changing mode of build/scripts-2.7/mp_plot from 664 to 775
> I: pybuild base:217: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.6_memprof/build/memprof
> copying memprof/memprof.py -> 
> /<>/.pybuild/cpython3_3.6_memprof/build/memprof
> copying memprof/mp_utils.py -> 
> /<>/.pybuild/cpython3_3.6_memprof/build/memprof
> copying memprof/__init__.py -> 
> /<>/.pybuild/cpython3_3.6_memprof/build/memprof
> copying memprof/__main__.py -> 
> /<>/.pybuild/cpython3_3.6_memprof/build/memprof
> running build_ext
> cythoning memprof/getsize.pyx to memprof/getsize.c
> building 'memprof.getsize' extension
> creating build/temp.linux-amd64-3.6
> creating build/temp.linux-amd64-3.6/memprof
> x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall 
> -Wstrict-prototypes -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.6m -c memprof/getsize.c -o 
> build/temp.linux-amd64-3.6/memprof/getsize.o
> x86_64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions 
> -Wl,-z,relro -Wl,-z,relro -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 build/temp.linux-amd64-3.6/memprof/getsize.o -o 
> /<>/.pybuild/cpython3_3.6_memprof/build/memprof/getsize.cpython-36m-x86_64-linux-gnu.so
> running build_scripts
> creating build/scripts-3.6
> copying and adjusting scripts/mp_plot -> build/scripts-3.6
> changing mode of build/scripts-3.6/mp_plot from 664 to 775
>dh_auto_test -O--buildsystem=pybuild

Processed: your mail

[Debian Bug Tracking System]

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

> tag 905929 +upstream
Bug #905929 [src:sysdig] sysdig FTBFS on arm64/mips*/alpha/riscv64: 
syscall_table.c fails to compile
Added tag(s) upstream.
> forwarded 905929 https://github.com/draios/sysdig/issues/1203
Bug #905929 [src:sysdig] sysdig FTBFS on arm64/mips*/alpha/riscv64: 
syscall_table.c fails to compile
Set Bug forwarded-to-address to 'https://github.com/draios/sysdig/issues/1203'.
> thanks
Stopping processing here.

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

Processed: Re: Bug#906708: hepmc: FTBFS on i386 / arm64 / ppc64el / s390x

[Debian Bug Tracking System]

Processing control commands:

> tags 906708 patch
Bug #906708 [src:hepmc] hepmc: FTBFS on i386 / arm64 / ppc64el / s390x
Ignoring request to alter tags of bug #906708 to the same tags previously set

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

Bug#906708: hepmc: FTBFS on i386 / arm64 / ppc64el / s390x

[Adrian Bunk]

Control: tags 906708 patch

On Sun, Aug 19, 2018 at 08:45:44PM -0400, Boyuan Yang wrote:
> Source: hepmc
> Version: 2.06.09-2
> Severity: serious
> X-Debbugs-CC: cdlumin...@gmail.com b...@debian.org lifong...@gmail.com
> 
> A team upload was made by Mo Zhou to remove multiarch-support pre-dependency 
> as well as fixing the FTBFS. However, the problem is not completely solved. 
> Package hepmc still FTBFS on several release architectures.
> 
> Mo Zhou told me that he will not attempt to fix those FTBFS since he is not 
> confident enough to provide a satisfactory patch, especially when it's a 
> scientific software from CERN.

Fix attached.

> Regards,
> Boyuan Yang

cu
Adrian

-- 

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

>From 2b9ec7bbdb99f721f53ee02b4cafec8e6d035c48 Mon Sep 17 00:00:00 2001
From: Andrii Verbytskyi 
Date: Mon, 29 Aug 2016 13:43:21 +0200
Subject: First set of small fixes

[ only the part required for #906708 ]

--- a/test/testSimpleVector.cc	2018-08-20 01:21:14.923985913 +
+++ b/test/testSimpleVector.cc	2018-08-20 01:21:17.508019107 +
@@ -14,7 +14,7 @@
   
   HepMC::ThreeVector v3copy( v3 );

-  double eps = 1.e-15; // allowed differnce between doubles
+  double eps = 4.e-15; // allowed difference between doubles
   int numbad = 0;
  
   double x = v3.x();

Processed: Re: Bug#906708: hepmc: FTBFS on i386 / arm64 / ppc64el / s390x

[Debian Bug Tracking System]

Processing control commands:

> tags 906708 patch
Bug #906708 [src:hepmc] hepmc: FTBFS on i386 / arm64 / ppc64el / s390x
Added tag(s) patch.

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

Bug#906708: hepmc: FTBFS on i386 / arm64 / ppc64el / s390x

[Boyuan Yang]

Source: hepmc
Version: 2.06.09-2
Severity: serious
X-Debbugs-CC: cdlumin...@gmail.com b...@debian.org lifong...@gmail.com

A team upload was made by Mo Zhou to remove multiarch-support pre-dependency 
as well as fixing the FTBFS. However, the problem is not completely solved. 
Package hepmc still FTBFS on several release architectures.

Mo Zhou told me that he will not attempt to fix those FTBFS since he is not 
confident enough to provide a satisfactory patch, especially when it's a 
scientific software from CERN.


--
Regards,
Boyuan Yang

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

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> unarchive 881018
Bug #881018 {Done: Muammar El Khatib } [src:cegui-mk2] 
cegui-mk2: FTBFS with xerces-c3.2
Unarchived Bug 881018
> forcemerge 881018 880377
Bug #881018 {Done: Muammar El Khatib } [src:cegui-mk2] 
cegui-mk2: FTBFS with xerces-c3.2
Bug #880377 [src:cegui-mk2] cegui-mk2: FTBFS with new gcc / icu
Severity set to 'serious' from 'wishlist'
881127 was blocked by: 881115 881108 881114 881018 881016 881920 881112 881026 
881023
881127 was blocking: 873669
Added blocking bug(s) of 881127: 880377
Marked Bug as done
Marked as fixed in versions cegui-mk2/0.8.7-2.
Added tag(s) buster and sid.
Merged 880377 881018
> thanks
Stopping processing here.

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

Bug#906707: thunderbird build depends on LLVM 4.0 which is scheduled for removal

[Adrian Bunk]

Source: thunderbird
Version: 1:60.0-1
Severity: serious
Control: block 893401 by -1

llvm-toolchain-4.0 is scheduled for removal, see #893401.

Processed: thunderbird build depends on LLVM 4.0 which is scheduled for removal

[Debian Bug Tracking System]

Processing control commands:

> block 893401 by -1
Bug #893401 [ftp.debian.org] RM: llvm-toolchain-4.0 -- ROM; Would like to limit 
the number of versions
893401 was blocked by: 906168 906174 893404 873408 902220 893403 906175 893408 
893405
893401 was not blocking any bugs.
Added blocking bug(s) of 893401: 906707

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

Bug#903524: marked as done (manuel FTBFS with Python 3.7 as supported version)

[Debian Bug Tracking System]

Your message dated Mon, 20 Aug 2018 00:04:01 +
with message-id 
and subject line Bug#903524: fixed in manuel 1.9.0-1
has caused the Debian Bug report #903524,
regarding manuel FTBFS with Python 3.7 as supported 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.)


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

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

...
I: pybuild base:217: python3.7 setup.py test 
...
==
FAIL: /build/1st/manuel-1.8.0/src/manuel/README.txt:Parsing
/build/1st/manuel-1.8.0/src/manuel/README.txt:Parsing
--
Traceback (most recent call last):
  File "/build/1st/manuel-1.8.0/src/manuel/testing.py", line 44, in runTest
'\n' + DIVIDER + DIVIDER.join(results))
AssertionError: 
--
File "/build/1st/manuel-1.8.0/src/manuel/README.txt", line 83, in README.txt
Failed example:
region.start_match
Expected:
<_sre.SRE_Match object...>
Got:

--
File "/build/1st/manuel-1.8.0/src/manuel/README.txt", line 85, in README.txt
Failed example:
region.end_match
Expected:
<_sre.SRE_Match object...>
Got:



--
Ran 60 tests in 0.095s

FAILED (failures=1)
Test failed: 
error: Test failed: 
E: pybuild pybuild:336: test: plugin distutils failed with: exit code=1: 
python3.7 setup.py test 
dh_auto_test: pybuild --test -i python{version} -p "3.7 3.6" returned exit code 
13
make: *** [debian/rules:7: build] Error 25
--- End Message ---
--- Begin Message ---
Source: manuel
Source-Version: 1.9.0-1

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

Debian distribution maintenance software
pp.
James Valleroy  (supplier of updated manuel package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 06 Aug 2018 19:06:24 -0400
Source: manuel
Binary: python-manuel python3-manuel
Architecture: source all
Version: 1.9.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: James Valleroy 
Description:
 python-manuel - Python library for testable documents and documented tests
 python3-manuel - Python3 library for testable documents and documented tests
Closes: 903524
Changes:
 manuel (1.9.0-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * d/copyright: Use https protocol in Format field
   * d/control: Remove ancient X-Python-Version field
   * d/control: Remove ancient X-Python3-Version field
 .
   [ James Valleroy ]
   * Convert from git-dpm to patches unapplied format
   * d/control: Add myself to uploaders
   * Patch doctests to support python3.7 (Closes: #903524)
   * debian/compat: Bump compat level to 11
   * debian/control: Bump Standards-Version to 4.1.5
   * debian/control: Add build-depend on python3-sphinx
   * New upstream version 1.9.0
   * debian/control: Slightly tweak homepage URL
   * debian/control: Bump Standards-Version to 4.2.0
Checksums-Sha1:
 433a81e3fc673c6f19e4c270e624f4bbc20816f2 2381 manuel_1.9.0-1.dsc
 4573da697050e8bf3022854ee7c90fdce9a18266 36729 manuel_1.9.0.orig.tar.gz
 49194a23ddf93ec01df3bcedd401af3cf0097cd9 4804 manuel_1.9.0-1.debian.tar.xz
 9a40090f853a57cccba9a292e51686c1c10c79f6 8236 manuel_1.9.0-1_amd64.buildinfo
 ce50bef412a9f6796504d36b82bd94198a30636c 59236 python-manuel_1.9.0-1_all.deb
 fc1d4799851883ca31bd6a065755246e50612726 59320 python3-manuel_1.9.0-1_all.deb
Checksums-Sha256:
 01e401e10ac8685c81b4e6ce1b1d95af94b2c85ffeb25b8986bac20793f76228 2381 
manuel_1.9.0-1.dsc
 71421009d4fafb183955afb836d31f20427542bffac52c151128fcf960879f8e 36729 
manuel_1.9.0.orig.tar.gz
 

Bug#891990: marked as done (pythia8: Build-Depends on hepmc which is scheduled for removal)

[Debian Bug Tracking System]

Your message dated Mon, 20 Aug 2018 02:15:42 +0300
with message-id <20180819231542.GU4164@localhost>
and subject line The hepmc removal has been cancelled
has caused the Debian Bug report #891990,
regarding pythia8: Build-Depends on hepmc which is scheduled for removal
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.)


-- 
891990: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891990
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pythia8
Version: 8.1.86-1.2
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Control: block 885180 with -1

Hi,

src:hepmc is scheduled for removal (#885180). Please remove the
Build-Depends and Depends on packages from src:hepmc. If src:pythia8
cannot be built without hepmc, please get it removed as well.


Andreas
--- End Message ---
--- Begin Message ---
The hepmc removal has been cancelled. see #885180 for details.

cu
Adrian

-- 

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

Bug#891991: marked as done (rivet: Build-Depends on hepmc which is scheduled for removal)

[Debian Bug Tracking System]

Your message dated Mon, 20 Aug 2018 02:15:42 +0300
with message-id <20180819231542.GU4164@localhost>
and subject line The hepmc removal has been cancelled
has caused the Debian Bug report #891991,
regarding rivet: Build-Depends on hepmc which is scheduled for removal
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.)


-- 
891991: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891991
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rivet
Version: 1.8.3-2
Severity: serious
Control: block 885180 with -1

Hi,

src:hepmc is scheduled for removal (#885180). Please remove the
Build-Depends and Depends on packages from src:hepmc. If src:rivet
cannot be built without hepmc, please get it removed as well.


Andreas
--- End Message ---
--- Begin Message ---
The hepmc removal has been cancelled. see #885180 for details.

cu
Adrian

-- 

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

Bug#891992: marked as done (thepeg: Build-Depends on hepmc which is scheduled for removal)

[Debian Bug Tracking System]

Your message dated Mon, 20 Aug 2018 02:15:42 +0300
with message-id <20180819231542.GU4164@localhost>
and subject line The hepmc removal has been cancelled
has caused the Debian Bug report #891992,
regarding thepeg: Build-Depends on hepmc which is scheduled for removal
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.)


-- 
891992: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891992
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: thepeg
Version: 1.8.0-3
Severity: serious
Control: block 885180 with -1

Hi,

src:hepmc is scheduled for removal (#885180). Please remove the
Build-Depends and Depends on packages from src:hepmc. If src:thepeg
cannot be built without hepmc, please get it removed as well.


Andreas
--- End Message ---
--- Begin Message ---
The hepmc removal has been cancelled. see #885180 for details.

cu
Adrian

-- 

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

Bug#906371: Probable new default version of Java issue: Bug#906371: jmodeltest: FTBFS in buster/sid

[Emmanuel Bourg]

On 17/08/2018 14:56, Andreas Tille wrote:

> Hi Debian Java team,
> 
> do you have any hint how to deal with this issue?

The actual error is:

[javac]
/build/1st/jmodeltest-2.1.10+dfsg/src/main/java/es/uvigo/darwin/jmodeltest/ModelTestService.java:28:
error: package parser does not exist
[javac] import parser.ParseException;
[javac]  ^
[javac]
/build/1st/jmodeltest-2.1.10+dfsg/src/main/java/es/uvigo/darwin/jmodeltest/ModelTestService.java:29:
error: package converter does not exist
[javac] import converter.Converter;
[javac] ^
[javac]
/build/1st/jmodeltest-2.1.10+dfsg/src/main/java/es/uvigo/darwin/jmodeltest/ModelTestService.java:30:
error: package converter does not exist
[javac] import converter.DefaultFactory;
[javac] ^
[javac]
/build/1st/jmodeltest-2.1.10+dfsg/src/main/java/es/uvigo/darwin/jmodeltest/ModelTestService.java:31:
error: package converter does not exist
[javac] import converter.Factory;
[javac] ^

There is an issue with a dependency (alter-sequence-alignment maybe?),
the Java version isn't to blame here.

Emmanuel Bourg

Processed: tesseract 4 is now in testing

[Debian Bug Tracking System]

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

> found 893645 4.3+git20160919-3
Bug #893645 [src:os-autoinst] os-autoinst: FTBFS: FAIL: 02-test_ocr.t
Marked as found in versions os-autoinst/4.3+git20160919-3.
> tags 893645 ftbfs buster sid
Bug #893645 [src:os-autoinst] os-autoinst: FTBFS: FAIL: 02-test_ocr.t
Added tag(s) ftbfs, buster, and sid.
> thanks
Stopping processing here.

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

Bug#901632: marked as done (miniupnpd: Fails to upgrade from buster: postinst: sed: -e expression #1, char 82: unknown option to `s')

[Debian Bug Tracking System]

Your message dated Sun, 19 Aug 2018 22:23:57 +
with message-id 
and subject line Bug#901632: fixed in miniupnpd 2.1-2
has caused the Debian Bug report #901632,
regarding miniupnpd: Fails to upgrade from buster: postinst: sed: -e expression 
#1, char 82: unknown option to `s'
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.)


-- 
901632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901632
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: miniupnpd
Version: 2.1-1
Severity: serious
Justification: fails to upgrade from buster to sid

Hi

miniupnpd upgrade from buster (1.8.20140523-4.2) to sid (2.1-1) fails
with the following:

root@miniupnpd:~# apt-get install miniupnpd
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be upgraded:
  miniupnpd
1 upgraded, 0 newly installed, 0 to remove and 7 not upgraded.
Need to get 99.4 kB of archives.
After this operation, 25.6 kB of additional disk space will be used.
Get:1 http://deb.debian.org/debian sid/main amd64 miniupnpd amd64 2.1-1 [99.4 
kB]
Fetched 99.4 kB in 0s (475 kB/s)
debconf: delaying package configuration, since apt-utils is not installed
(Reading database ... 8892 files and directories currently installed.)
Preparing to unpack .../miniupnpd_2.1-1_amd64.deb ...
Migrating old "/etc/default/miniupnpd"...
Unpacking miniupnpd (2.1-1) over (1.8.20140523-4.2) ...
Processing triggers for systemd (238-5) ...
Setting up miniupnpd (2.1-1) ...

Configuration file '/etc/default/miniupnpd'
 ==> File on system created by you or by a script.
 ==> File also in package provided by package maintainer.
   What would you like to do about it ?  Your options are:
Y or I  : install the package maintainer's version
N or O  : keep your currently-installed version
  D : show the differences between the versions
  Z : start a shell to examine the situation
 The default action is to keep your current version.
*** miniupnpd (Y/I/N/O/D/Z) [default=N] ? Y
Installing new version of config file /etc/default/miniupnpd ...
Installing new version of config file /etc/init.d/miniupnpd ...
Installing new version of config file /etc/miniupnpd/ip6tables_init.sh ...
Installing new version of config file /etc/miniupnpd/ip6tables_removeall.sh ...
Installing new version of config file /etc/miniupnpd/iptables_init.sh ...
Installing new version of config file /etc/miniupnpd/iptables_removeall.sh ...
sed: -e expression #1, char 82: unknown option to `s'
dpkg: error processing package miniupnpd (--configure):
 installed miniupnpd package post-installation script subprocess returned error 
exit status 1
Processing triggers for systemd (238-5) ...
Errors were encountered while processing:
 miniupnpd
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@miniupnpd:~#

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: miniupnpd
Source-Version: 2.1-2

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

Debian distribution maintenance software
pp.
Yangfl  (supplier of updated miniupnpd 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, 15 Aug 2018 16:23:40 +0800
Source: miniupnpd
Binary: miniupnpd
Architecture: source amd64
Version: 2.1-2
Distribution: unstable
Urgency: medium
Maintainer: Thomas Goirand 
Changed-By: Yangfl 
Description:
 miniupnpd  - UPnP and NAT-PMP daemon for gateway routers
Closes: 901632
Changes:
 miniupnpd (2.1-2) unstable; urgency=medium
 .
   * Disable kfreebsd-any due to lack of iptables.
   * Remove obsolete default file in favor of debconf.
   * Add debconf option for `force_igd_desc_v1'.
   * Fix sed command bug in postinst (Closes: #901632).
   * debian/miniupnpd.config: Always prefer configs in debconf to prevent config
 loss during fresh installation.
   * debian/rules: Disable auto enabling systemd service.
   * Bump Standards-Version to 4.2.0.
Checksums-Sha1:
 b03b7188ce9f775616dce63571b570f7e739b8b6 1909 miniupnpd_2.1-2.dsc
 

Bug#905200: marked as done (natpmp-utils,libnatpmp-dev: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE)

[Debian Bug Tracking System]

Your message dated Sun, 19 Aug 2018 22:23:38 +
with message-id 
and subject line Bug#905200: fixed in libnatpmp 20150609-5
has caused the Debian Bug report #905200,
regarding natpmp-utils,libnatpmp-dev: unhandled symlink to directory 
conversion: /usr/share/doc/PACKAGE
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.)


-- 
905200: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905200
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: natpmp-utils,libnatpmp-dev
Version: 20150609-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  stretch -> buster

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/#copyright-information

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/#details-of-unpack-phase-of-installation-or-upgrade

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


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

0m28.4s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/natpmp-utils/changelog.Debian.gz (natpmp-utils) != 
/usr/share/doc/libnatpmp1/changelog.Debian.gz (libnatpmp1)
/usr/share/doc/natpmp-utils -> libnatpmp1
  /usr/share/doc/natpmp-utils/changelog.gz (natpmp-utils) != 
/usr/share/doc/libnatpmp1/changelog.gz (libnatpmp1)
/usr/share/doc/natpmp-utils -> libnatpmp1
  /usr/share/doc/natpmp-utils/copyright (natpmp-utils) != 
/usr/share/doc/libnatpmp1/copyright (libnatpmp1)
/usr/share/doc/natpmp-utils -> libnatpmp1

0m27.9s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/libnatpmp-dev/changelog.Debian.gz (libnatpmp-dev:amd64) != 
/usr/share/doc/libnatpmp1/changelog.Debian.gz (libnatpmp1)
/usr/share/doc/libnatpmp-dev -> libnatpmp1
  /usr/share/doc/libnatpmp-dev/changelog.gz (libnatpmp-dev:amd64) != 
/usr/share/doc/libnatpmp1/changelog.gz (libnatpmp1)
/usr/share/doc/libnatpmp-dev -> libnatpmp1
  /usr/share/doc/libnatpmp-dev/copyright (libnatpmp-dev:amd64) != 
/usr/share/doc/libnatpmp1/copyright (libnatpmp1)
/usr/share/doc/libnatpmp-dev -> libnatpmp1


cheers,

Andreas


natpmp-utils_20150609-4.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libnatpmp
Source-Version: 20150609-5

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

Debian distribution maintenance software
pp.
Yangfl  (supplier of updated libnatpmp 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, 16 Aug 2018 19:42:06 +0800
Source: libnatpmp
Binary: libnatpmp-dev libnatpmp1 natpmp-utils natpmpc python3-libnatpmp
Architecture: source amd64 all
Version: 20150609-5
Distribution: unstable
Urgency: medium
Maintainer: Thomas Goirand 
Changed-By: Yangfl 
Description:
 libnatpmp-dev - portable and fully compliant implementation of NAT-PMP (dev 
files
 

Bug#901658: marked as done (minissdpd: error at install time with the default settings: "option -i needs an argument")

[Debian Bug Tracking System]

Your message dated Sun, 19 Aug 2018 22:23:48 +
with message-id 
and subject line Bug#901658: fixed in minissdpd 1.5.20180223-3
has caused the Debian Bug report #901658,
regarding minissdpd: error at install time with the default settings: "option 
-i needs an argument"
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.)


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

After purging minissdpd yesterday, I've tried to install it again
without changing any default config, but installation failed:

Unpacking minissdpd (1.5.20180223-2) ...
Setting up minissdpd (1.5.20180223-2) ...
Job for minissdpd.service failed because the control process exited with error 
code.
See "systemctl status minissdpd.service" and "journalctl -xe" for details.
invoke-rc.d: initscript minissdpd, action "start" failed.
● minissdpd.service - keep memory of all UPnP devices that announced themselves
   Loaded: loaded (/lib/systemd/system/minissdpd.service; disabled; vendor 
preset: enabled)
   Active: failed (Result: exit-code) since Sat 2018-06-16 13:30:02 CEST; 14ms 
ago
 Docs: man:minissdpd(1)
  Process: 24037 ExecStart=/usr/sbin/minissdpd -i $MiniSSDPd_INTERFACE_ADDRESS 
$MiniSSDPd_OTHER_OPTIONS (code=exited, status=1/FAILURE)

Jun 16 13:30:02 cventin systemd[1]: Starting keep memory of all UPnP devices 
that announced themselves...
Jun 16 13:30:02 cventin minissdpd[24037]: option -i needs an argument.
Jun 16 13:30:02 cventin minissdpd[24037]: Usage: /usr/sbin/minissdpd [-d] [-6] 
[-s socket] [-p pidfile] [-t TTL] [-f device] -i  [-i ] 
...
Jun 16 13:30:02 cventin minissdpd[24037]:is either an IPv4 
address with mask such as
Jun 16 13:30:02 cventin minissdpd[24037]:   192.168.1.42/255.255.255.0, or an 
interface name such as eth0.
Jun 16 13:30:02 cventin minissdpd[24037]:   By default, socket will be open as 
/var/run/minissdpd.sock
Jun 16 13:30:02 cventin minissdpd[24037]:   and pid written to file 
/var/run/minissdpd.pid
Jun 16 13:30:02 cventin systemd[1]: minissdpd.service: Control process exited, 
code=exited status=1
Jun 16 13:30:02 cventin systemd[1]: minissdpd.service: Failed with result 
'exit-code'.
Jun 16 13:30:02 cventin systemd[1]: Failed to start keep memory of all UPnP 
devices that announced themselves.
dpkg: error processing package minissdpd (--configure):
 installed minissdpd package post-installation script subprocess returned error 
exit status 1
Processing triggers for systemd (238-5) ...
Processing triggers for man-db (2.8.3-2) ...
Errors were encountered while processing:
 minissdpd

-- 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.16.0-2-amd64 (SMP w/12 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: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages minissdpd depends on:
ii  debconf [debconf-2.0]  1.5.67
ii  libc6  2.27-3
ii  libnfnetlink0  1.0.1-3+b1
ii  lsb-base   9.20170808

minissdpd recommends no packages.

minissdpd suggests no packages.

-- debconf information:
  minissdpd/ip6: false
* minissdpd/listen:
* minissdpd/start_daemon: false
--- End Message ---
--- Begin Message ---
Source: minissdpd
Source-Version: 1.5.20180223-3

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

Debian distribution maintenance software
pp.
Yangfl  (supplier of updated minissdpd 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, 26 Jul 2018 20:39:35 +0800
Source: minissdpd
Binary: minissdpd
Architecture: source amd64
Version: 1.5.20180223-3
Distribution: 

Bug#899937: marked as done (protobuf: Invalid maintainer address pkg-protobuf-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Mon, 20 Aug 2018 01:03:14 +0300
with message-id <20180819220314.GS4164@localhost>
and subject line Already fixed in experimental
has caused the Debian Bug report #899937,
regarding protobuf: Invalid maintainer address 
pkg-protobuf-de...@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.)


-- 
899937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899937
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:protobuf
Version: 3.0.0-9.1
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of protobuf,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package protobuf since the list address
pkg-protobuf-de...@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-protobuf-de...@lists.alioth.debian.org is 1.

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 ---
Version: 3.5.2-1

protobuf (3.5.2-1) experimental; urgency=medium
...
  * Take over maintainer responsibility.
...
 -- Laszlo Boszormenyi (GCS)   Wed, 25 Apr 2018 21:29:01 +


cu
Adrian

-- 

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

Bug#906701: peewee FTBFS with Python 3.7 as supported version

[Adrian Bunk]

Source: peewee
Version: 2.10.2+dfsg-2
Severity: serious
Tags: ftbfs

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

...
= test session starts ==
platform linux -- Python 3.7.0, pytest-3.6.2, py-1.5.3, pluggy-0.6.0
rootdir: /<>/peewee-2.10.2+dfsg, inifile:
collected 383 items

tests.py ... [ 16%]
 [ 35%]
 [ 54%]
 [ 72%]
...FFF.. [ 91%]
 [100%]

=== FAILURES ===
_ TestQueryResultWrapper.test_iterator _

self = 

def iterator(self):
while True:
>   yield self.iterate()

peewee.py:2353: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = 

def iterate(self):
row = self.cursor.fetchone()
if not row:
self._populated = True
if not getattr(self.cursor, 'name', None):
self.cursor.close()
>   raise StopIteration
E   StopIteration

peewee.py:2345: StopIteration

The above exception was the direct cause of the following exception:

self = 

def test_iterator(self):
User.create_users(10)

with self.assertQueryCount(1):
qr = User.select().order_by(User.id).execute()
>   usernames = [u.username for u in qr.iterator()]

playhouse/tests/test_query_results.py:111: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

.0 = 

>   usernames = [u.username for u in qr.iterator()]
E   RuntimeError: generator raised StopIteration

playhouse/tests/test_query_results.py:111: RuntimeError
-- Captured log call ---
peewee.py 3826 DEBUG('DROP TABLE IF EXISTS "comment"', [])
peewee.py 3826 DEBUG('DROP TABLE IF EXISTS "blog"', [])
peewee.py 3826 DEBUG('DROP TABLE IF EXISTS "users"', [])
peewee.py 3826 DEBUG('CREATE TABLE "users" ("id" INTEGER 
NOT NULL PRIMARY KEY, "username" VARCHAR(255) NOT NULL)', [])
peewee.py 3826 DEBUG('CREATE TABLE "blog" ("pk" INTEGER NOT 
NULL PRIMARY KEY, "user_id" INTEGER NOT NULL, "title" VARCHAR(25) NOT NULL, 
"content" TEXT NOT NULL, "pub_date" DATETIME, FOREIGN KEY ("user_id") 
REFERENCES "users" ("id"))', [])
peewee.py 3826 DEBUG('CREATE INDEX "blog_user_id" ON "blog" 
("user_id")', [])
peewee.py 3826 DEBUG('CREATE TABLE "comment" ("id" INTEGER 
NOT NULL PRIMARY KEY, "blog_id" INTEGER NOT NULL, "comment" VARCHAR(255) NOT 
NULL, FOREIGN KEY ("blog_id") REFERENCES "blog" ("pk"))', [])
peewee.py 3826 DEBUG('CREATE INDEX "comment_blog_id" ON 
"comment" ("blog_id")', [])
peewee.py 3826 DEBUG('INSERT INTO "users" ("username") 
VALUES (?)', ['u1'])
peewee.py 3826 DEBUG('INSERT INTO "users" ("username") 
VALUES (?)', ['u2'])
peewee.py 3826 DEBUG('INSERT INTO "users" ("username") 
VALUES (?)', ['u3'])
peewee.py 3826 DEBUG('INSERT INTO "users" ("username") 
VALUES (?)', ['u4'])
peewee.py 3826 DEBUG('INSERT INTO "users" ("username") 
VALUES (?)', ['u5'])
peewee.py 3826 DEBUG('INSERT INTO "users" ("username") 
VALUES (?)', ['u6'])
peewee.py 3826 DEBUG('INSERT INTO "users" ("username") 
VALUES (?)', ['u7'])
peewee.py 3826 DEBUG('INSERT INTO "users" ("username") 
VALUES (?)', ['u8'])
peewee.py 3826 DEBUG('INSERT INTO "users" ("username") 
VALUES (?)', ['u9'])
peewee.py 3826 DEBUG('INSERT INTO "users" ("username") 
VALUES (?)', ['u10'])
peewee.py 3826 DEBUG('SELECT "t1"."id", "t1"."username" 
FROM "users" AS t1 ORDER BY "t1"."id"', [])
peewee.py 3826 DEBUG('DROP TABLE IF EXISTS "comment"', [])
peewee.py 3826 DEBUG('DROP TABLE IF EXISTS "blog"', [])
peewee.py 3826 DEBUG('DROP TABLE IF EXISTS "users"', [])
 TestQueryResultWrapper.test_iterator_extended _

self = 

def iterator(self):
while True:
>   yield self.iterate()

peewee.py:2353: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = 

def iterate(self):
row = self.cursor.fetchone()
if not row:
self._populated = True
if not getattr(self.cursor, 'name', None):

Bug#906308: marked as done (CVE-2018-14348)

[Debian Bug Tracking System]

Your message dated Sun, 19 Aug 2018 21:49:17 +
with message-id 
and subject line Bug#906308: fixed in libcgroup 0.41-8.1
has caused the Debian Bug report #906308,
regarding CVE-2018-14348
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.)


-- 
906308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906308
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libcgroup
Severity: grave
Tags: security

This was assigned CVE-2018-14348:
https://bugzilla.suse.com/show_bug.cgi?id=1100365
(cgred seems to be cgrulesengd in Debian)

Patch:
https://sourceforge.net/p/libcg/libcg/ci/0d88b73d189ea3440ccaab00418d6469f76fa590/

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: libcgroup
Source-Version: 0.41-8.1

We believe that the bug you reported is fixed in the latest version of
libcgroup, 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.
Markus Koschany  (supplier of updated libcgroup package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 19 Aug 2018 23:10:45 +0200
Source: libcgroup
Binary: cgroup-tools libcgroup1 libcgroup-dev libpam-cgroup cgroup-bin
Architecture: source
Version: 0.41-8.1
Distribution: unstable
Urgency: high
Maintainer: Christian Kastner 
Changed-By: Markus Koschany 
Description:
 cgroup-bin - control and monitor control groups (transitional package)
 cgroup-tools - control and monitor control groups (tools)
 libcgroup-dev - control and monitor control groups (development)
 libcgroup1 - control and monitor control groups (library)
 libpam-cgroup - control and monitor control groups (PAM)
Closes: 906308
Changes:
 libcgroup (0.41-8.1) unstable; urgency=high
 .
   * Non-maintainer upload.
   * Fix CVE-2018-14348:
 It was discovered that the cgrulesengd daemon would create a log file which
 would allow any user to write to it. (Closes: #906308)
Checksums-Sha1:
 10faeaf81643fe61e77d247d4732106730f99808 2307 libcgroup_0.41-8.1.dsc
 938167fdf1c619461ec081457942bc2860845b7e 16624 libcgroup_0.41-8.1.debian.tar.xz
 f5a47776c7f2f722abcc79f83eba1b35b94971d8 7714 
libcgroup_0.41-8.1_amd64.buildinfo
Checksums-Sha256:
 235b9d1af793999747107d57a4227542b3face7076e2b3d3802e3e0eb6c16073 2307 
libcgroup_0.41-8.1.dsc
 5d7cc170ab02692b94bb080428cf92d36018614584e3786a2e83af4abe12 16624 
libcgroup_0.41-8.1.debian.tar.xz
 93663d2f144d32f447ef2eee0e67a55df67dabf5d8a684662c08876570d14668 7714 
libcgroup_0.41-8.1_amd64.buildinfo
Files:
 ea85b13472360ea0d44c4df58056692e 2307 libs optional libcgroup_0.41-8.1.dsc
 49de12c66bdf1c8ecacd398f849e6e8d 16624 libs optional 
libcgroup_0.41-8.1.debian.tar.xz
 07ff91267c9ec3abc0d1de3623ad1b17 7714 libs optional 
libcgroup_0.41-8.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAlt54aVfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD
RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp
YW4ub3JnAAoJENmtFLlRO1HkZwkQALRx+hrvRVe5aaRV7Pb+sjcmcB/1xdMHruio
YkD6WQalwc/URUs83YOVg5nRz6lbW3Xvx61KujWG/swryWKEWcw8LBMWptS4rynC
UbwzPTB0FKYMZlxZ06KXbijJD2a8KJlsi4GEfn4n3pkBggxGauerX/ROb5Yj579M
SAWPSM7uiL3unyFxKNoDIt0thZHDRXzsw/p//Qfai3mWwUeSJoFI28LWskrtmED8
OZyNnZHmkVZOuJaiYcBTt/8nUA+iDemSGvFtaMFCI0P4/4OIfFOLM/XxKgWn1nS5
C6cZmETJZEg8KRyGIitrqj/jqvOyOclmXXESzTQh91eNvHF4yoN9V+PEUw/EuJhQ
TSk6hTlJiCMdYAWY9q4kOYPIvGcW9h8h9yeMA2CL5a+PJes0Z+dzyOZmKUpOleSU
nPdAJW46P7lTUtxPzCJBRq4M5bgpCRYjkg0+k75VLiBVzlPsbym2Jf8LU3YTZTqP
JC30OYIqlfP2Rtle8r2UNFAuwUIkYxzlZSxdiLUWvvQMm5wbJ06YoBAPU2LAE6Wq
W/qv7MnaC79NGpMC0ZRun8+mAHCVSQvGv2fGA41rYmZ4vIirqyJzUJFemTxBbOjT
JkhBKnydQIipsY/rkF/SIcNkOv1eRUDyuLktS//xm4ffcjCvfA2xT+T8z/bZABbr
+FH6v/aN
=fSG+
-END PGP SIGNATURE End Message ---

Bug#906308: CVE-2018-14348

[Markus Koschany]

Dear maintainer,

I've uploaded a new revision versioned as 0.48-8.1 to fix CVE-2018-14348.

Please find attached the debdiff.

Regards,

Markus
diff -Nru libcgroup-0.41/debian/changelog libcgroup-0.41/debian/changelog
--- libcgroup-0.41/debian/changelog 2016-04-24 18:51:45.0 +0200
+++ libcgroup-0.41/debian/changelog 2018-08-19 23:10:45.0 +0200
@@ -1,3 +1,12 @@
+libcgroup (0.41-8.1) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * Fix CVE-2018-14348:
+It was discovered that the cgrulesengd daemon would create a log file which
+would allow any user to write to it. (Closes: #906308)
+
+ -- Markus Koschany   Sun, 19 Aug 2018 23:10:45 +0200
+
 libcgroup (0.41-8) unstable; urgency=medium
 
   * Drop package libcgroup-dbg in favor of automatic dbgsym packages.
diff -Nru libcgroup-0.41/debian/patches/CVE-2018-14348.patch 
libcgroup-0.41/debian/patches/CVE-2018-14348.patch
--- libcgroup-0.41/debian/patches/CVE-2018-14348.patch  1970-01-01 
01:00:00.0 +0100
+++ libcgroup-0.41/debian/patches/CVE-2018-14348.patch  2018-08-19 
23:10:45.0 +0200
@@ -0,0 +1,23 @@
+From: Markus Koschany 
+Date: Sun, 19 Aug 2018 23:09:25 +0200
+Subject: CVE-2018-14348
+
+Bug-Debian: https://bugs.debian.org/906308
+Origin: 
https://sourceforge.net/p/libcg/libcg/ci/0d88b73d189ea3440ccaab00418d6469f76fa590/
+---
+ src/daemon/cgrulesengd.c | 2 --
+ 1 file changed, 2 deletions(-)
+
+diff --git a/src/daemon/cgrulesengd.c b/src/daemon/cgrulesengd.c
+index 367b898..ffd1fc3 100644
+--- a/src/daemon/cgrulesengd.c
 b/src/daemon/cgrulesengd.c
+@@ -886,8 +886,6 @@ int cgre_start_daemon(const char *logp, const int logf,
+   exit(EXIT_SUCCESS);
+   }
+ 
+-  /* Change the file mode mask. */
+-  umask(0);
+   } else {
+   flog(LOG_DEBUG, "Not using daemon mode\n");
+   pid = getpid();
diff -Nru libcgroup-0.41/debian/patches/series 
libcgroup-0.41/debian/patches/series
--- libcgroup-0.41/debian/patches/series2016-04-24 18:51:45.0 
+0200
+++ libcgroup-0.41/debian/patches/series2018-08-19 23:10:45.0 
+0200
@@ -4,3 +4,4 @@
 initscript-return.patch
 Syntax-fixes-for-man-pages.patch
 pam_cgroup-Revert-broken-cache-usage.patch
+CVE-2018-14348.patch


signature.asc
Description: OpenPGP digital signature

Bug#904899: marked as done (mandos: initramfs boot script assumes internal cryptsetup implementation details and is now broken)

[Debian Bug Tracking System]

Your message dated Sun, 19 Aug 2018 20:49:05 +
with message-id 
and subject line Bug#904899: fixed in mandos 1.7.20-1
has caused the Debian Bug report #904899,
regarding mandos: initramfs boot script assumes internal cryptsetup 
implementation details and is now 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.)


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

Hi,

mandos' initramfs boot script reads and parses /conf/conf.d/cryptroot.
Since cryptsetup 2:2.0.3-2 this file no longer exists; we cryptsetup
package maintainers replaced and it changed its format (without notice
as it was undocumented and thus internal to src:cryptsetup).

Packages outside of src:cryptsetup must stick to the documented
interface; and in use cases where it's not enough, ask us to extend it
rather than using internal details that are subject to change without
notice.

Cheers,
-- 
Guilhem.


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: mandos
Source-Version: 1.7.20-1

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

Debian distribution maintenance software
pp.
Teddy Hogeborn  (supplier of updated mandos package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 19 Aug 2018 22:14:04 +0200
Source: mandos
Binary: mandos mandos-client
Architecture: source amd64 all
Version: 1.7.20-1
Distribution: unstable
Urgency: medium
Maintainer: Mandos Maintainers 
Changed-By: Teddy Hogeborn 
Description:
 mandos - server giving encrypted passwords to Mandos clients
 mandos-client - do unattended reboots with an encrypted root file system
Closes: 894495 904899
Changes:
 mandos (1.7.20-1) unstable; urgency=medium
 .
   * New upstream release.
   * Fix "[tethys] mandos-client: Mandos client fails while booting but
 works from chroot into unpacked initramfs" by setting system clock if
 necessary (Closes: #894495)
   * Fix "initramfs boot script assumes internal cryptsetup implementation
 details and is now broken" by only using documented
 interfaces (Closes: #904899)
   * debian/mandos-client.dirs: Add
 "usr/share/initramfs-tools/scripts/local-premount" and
 "usr/share/initramfs-tools/conf.d", and remove
 "usr/share/initramfs-tools/conf-hooks.d".
   * debian/control (mandos-client/Depends): Add "(>= 0.99)" to dependency
 on "initramfs-tools".
   * debian/control (Source: mandos/Rules-Requires-Root): New; set to
 "binary-targets".
 (Standards-Version): Update to "4.2.0".
Checksums-Sha1:
 9c79827cf6c574d581b6e921739cb04c22118b4a 2291 mandos_1.7.20-1.dsc
 addccf4f5b8f40565b1b7aef58bb5a9150bc4757 180955 mandos_1.7.20.orig.tar.gz
 f4ec461e55e5d38a931b6c646ab837c709b3a509 15896 mandos_1.7.20-1.debian.tar.xz
 e63ca8c65fff005cccb3d1f68b7391242710d6b6 175248 
mandos-client-dbgsym_1.7.20-1_amd64.deb
 087ce0813f2d8e98255ac7513fb03d30f6c51f4b 130556 
mandos-client_1.7.20-1_amd64.deb
 2d7b38ada2cf3af593d1f65dc6ff354d5e7a0d3f 88600 mandos_1.7.20-1_all.deb
 7b4c2ad39e97b5b4d7b62d0222305a654762a02d 9497 mandos_1.7.20-1_amd64.buildinfo
Checksums-Sha256:
 43355bfe4be5183775c662f45033711d4e483ba72f9dbf804b672c02d83cd004 2291 
mandos_1.7.20-1.dsc
 84c8712d1a6986d48f504d5ae328ae4a2be6b3d1ae357a67277e4caec96b2c64 180955 
mandos_1.7.20.orig.tar.gz
 18cebed24112e2b0f77987bd0faa4886759bce6c4bca7c50a8fa455c297c3d00 15896 
mandos_1.7.20-1.debian.tar.xz
 94edc794e0ca53b04e0bf5343c4d61944b1858e3cddfb4593817af89cfa566b3 175248 
mandos-client-dbgsym_1.7.20-1_amd64.deb
 23e6b3fb9a80e4a55c381235d397ee0a4de12c6c2951f41200147535d42fe5a9 130556 
mandos-client_1.7.20-1_amd64.deb
 4614cb3b3416f8c2069b7a7250a8712b696ea2dca4b162928947bbc815a42b3f 88600 
mandos_1.7.20-1_all.deb
 f50d85a24af303aa3e00cc5ed4d867c23362b84438e5ae5457a2e0f7f0d4fead 9497 
mandos_1.7.20-1_amd64.buildinfo
Files:
 e8f4492d8b9fe330ad053c4dfab575ff 2291 admin optional mandos_1.7.20-1.dsc
 

Bug#906697: ck: baseline violation on i386

[Adrian Bunk]

Source: ck
Version: 0.6.0-1.1
Severity: serious

ck builds with "-msse -msse2" but SSE is not part
of the i386 baseline.

Bug#901044: libjnr-posix-java-doc_3.0.45-1_all.deb errors encountered while processing

[Robert Elder]

send-detail 901044

Bug#901562: invesalius is marked for autoremoval from testing

[Thiago Franco Moraes]

Hi Andreas,

Thanks, I can push to repository now. I've pushed both the master and
upstream/3.1.1

Best regards

On Sat, Aug 18, 2018 at 2:32 AM Andreas Tille  wrote:
>
> Hi Thiago,
>
> On Fri, Aug 17, 2018 at 09:12:46PM -0300, Thiago Franco Moraes wrote:
> > I' ve created a merge request in the Debian Salsa with a new version
> > tag (3.1.9991) of InVesalius. This new version fixes the bug #901562.
>
> I've added you to the Debian Med team now.  Please check whether you
> can push directly to the repository.
> > This package is not using Python3 because there is not a
> > pyhton3-vtkgdcm package in Debian Testing. But InVesalius is already
> > running with Python3.
>
> I've just opened a bug against gdcm to ask for Python3 support.  As
> I understood Gerd in #895900 this is planed and was just delayed due
> to Invesalius.  So I think we can expect pyhton3-vtkgdcm soon.
>
> Thanks for your work on this
>
>   Andreas.
>
> --
> http://fam-tille.de

Bug#906118: marked as done (openmpi: some builds and autopkgtests time out on i386, armhf)

[Debian Bug Tracking System]

Your message dated Sun, 19 Aug 2018 18:49:19 +
with message-id 
and subject line Bug#906118: fixed in openmpi 3.1.1.real-7
has caused the Debian Bug report #906118,
regarding openmpi: some builds and autopkgtests time out on i386, armhf
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.)


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

Source: openmpi
Version: 3.1.1.real-6
Severity: serious

Hi Alastair

We noticed in Ubuntu, builds and autopkgtests of a couple of 
openmpi-related packages time out on i386 and armhf.  At least some of 
these have been successful with previous versions of libopenmpi3.


I have been able to reproduce some of the build failures in Debian 
[1][2][3].  Unfortunately, Debian do not run autopkgtests on i386, but 
in Ubuntu there are failed logs of esys-particle [4], liggghts [5], 
yorick [6].


Regards
Graham


[1] 
https://tests.reproducible-builds.org/debian/history/i386/med-fichier.html
[2] 
https://tests.reproducible-builds.org/debian/history/armhf/med-fichier.html

[3] https://tests.reproducible-builds.org/debian/history/armhf/slepc.html

[4] http://autopkgtest.ubuntu.com/packages/e/esys-particle/cosmic/i386
[5] http://autopkgtest.ubuntu.com/packages/l/liggghts/cosmic/i386
[6] http://autopkgtest.ubuntu.com/packages/y/yorick/cosmic/i386
--- End Message ---
--- Begin Message ---
Source: openmpi
Source-Version: 3.1.1.real-7

We believe that the bug you reported is fixed in the latest version of
openmpi, 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.
Alastair McKinstry  (supplier of updated openmpi package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 19 Aug 2018 19:06:13 +0100
Source: openmpi
Binary: openmpi-bin libopenmpi-dev libopenmpi3 openmpi-common openmpi-doc
Architecture: source amd64 all
Version: 3.1.1.real-7
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Description:
 libopenmpi-dev - high performance message passing library -- header files
 libopenmpi3 - high performance message passing library -- shared library
 openmpi-bin - high performance message passing library -- binaries
 openmpi-common - high performance message passing library -- common files
 openmpi-doc - high performance message passing library -- man pages
Closes: 906118
Changes:
 openmpi (3.1.1.real-7) unstable; urgency=medium
 .
   * Patch from upstream for OMPI/PMIX hang. Closes: #906118
   * Change openmpi-common to Arch: all
   * Standards-VersioN: 4.2.0
Checksums-Sha1:
 8e96fcd6966ea0e12cc504288a64928f59facf2a 2687 openmpi_3.1.1.real-7.dsc
 6e30835c24bc7dd9f3694356ffc0137db59375e8 62868 
openmpi_3.1.1.real-7.debian.tar.xz
 60235bde5f82e675785ad2988341a261725d7c21 15496 
libopenmpi-dev-dbgsym_3.1.1.real-7_amd64.deb
 2d9bbab13430198fccb3ad614a147e8a0366c111 1051428 
libopenmpi-dev_3.1.1.real-7_amd64.deb
 b262781db9cb0906d4b89fb773c43bed715fc657 35816328 
libopenmpi3-dbgsym_3.1.1.real-7_amd64.deb
 6cc58ea188568a74a565bff468326014061897c6 2489588 
libopenmpi3_3.1.1.real-7_amd64.deb
 f4f1093af5d4837889a064d39473258f0dd1b444 226312 
openmpi-bin-dbgsym_3.1.1.real-7_amd64.deb
 4fa5da69d241d31f6f737554aed0a42229c82498 196708 
openmpi-bin_3.1.1.real-7_amd64.deb
 37f4b4e8e0016273d851a66e5213f067d7cb44ed 161236 
openmpi-common_3.1.1.real-7_all.deb
 a29af30da4950c66c9a938e4669a2398a1c6f644 758220 
openmpi-doc_3.1.1.real-7_all.deb
 638089a13d06df7594c18106880bc7ab552d2905 13392 
openmpi_3.1.1.real-7_amd64.buildinfo
Checksums-Sha256:
 5f5af43eef05758f5f41b647daf7c7ba895cb1612958012aa836ba31e38315fb 2687 
openmpi_3.1.1.real-7.dsc
 6581f2c7d8ab41b44daafd6f65c755750a816549b0a2c16b2abfa31625016e79 62868 
openmpi_3.1.1.real-7.debian.tar.xz
 0fc05f741a7b518103cbaffc6d863dc5b785bbc4320b3e61542528fada54f3f1 15496 
libopenmpi-dev-dbgsym_3.1.1.real-7_amd64.deb
 fd19c9a35ab0565fc1fd7a01d4388edacecbf5c95670d26be0c6ae364c94580a 1051428 
libopenmpi-dev_3.1.1.real-7_amd64.deb
 efa8110d8af6d9f2940d7c6a9e0a4bac1494da7137b46023a35e7873ba010b53 

Bug#906659: keepassxc: FTBFS in buster/sid (invalid use of incomplete type â class QButtonGroupâ )

[Julian Andres Klode]

On Sun, Aug 19, 2018 at 07:30:31PM +0200, Nazar Zhuk wrote:
> This is fixed upstream in 2.3.3.
> Related upstream bug:
> https://github.com/keepassxreboot/keepassxc/issues/2048
> Upstream patch:
> https://github.com/keepassxreboot/keepassxc/commit/3bbc6ac0e6298d27bfe0c41999460cafda8edf18

I packaged it in git, I should upload it. Well, I'll probably wait for .4, I 
think
that's around the corner.

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en

Bug#906688: ruby-netrc: FTBFS in buster/sid (test_missing_environment fails)

[Santiago Vila]

Package: src:ruby-netrc
Version: 0.11.0-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
 fakeroot debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_testroot -i -O--buildsystem=ruby
   dh_prep -i -O--buildsystem=ruby

[... snipped ...]

TestNetrc#test_multi_without_default = 0.00 s = .
TestNetrc#test_set = 0.00 s = .
TestNetrc#test_missing_environment = 0.00 s = F
TestNetrc#test_permission_error = 0.00 s = .
TestNetrc#test_save = 0.00 s = .
TestNetrc#test_entry_splat = 0.00 s = .
TestNetrc#test_get_missing = DEPRECATED: Use assert_nil if expecting nil from 
/<>/test/test_netrc.rb:169. This will fail in Minitest 6.
0.00 s = .
TestNetrc#test_netrc_environment_variable = 0.00 s = .
TestNetrc#test_add_get = 0.00 s = .
TestNetrc#test_add_newlineless = 0.00 s = .
TestNetrc#test_permission_error_windows = 0.00 s = .
TestNetrc#test_multi_with_default = 0.00 s = .
TestNetrc#test_allow_permissive_netrc_file_option = 0.00 s = .
TestNetrc#test_write_entry = 0.00 s = .
TestNetrc#test_parse_file = 0.00 s = .
TestNetrc#test_with_default = 0.00 s = .
TestNetrc#test_entry_implicit_splat = 0.00 s = .
TestNetrc#test_missing_file = 0.00 s = .
TestNetrc#test_parse_empty = 0.00 s = .
TestNetrc#test_set_get = 0.00 s = .
TestNetrc#test_password_file = 0.00 s = .
TestNetrc#test_add = 0.00 s = .
TestNetrc#test_login_file = 0.00 s = .

Finished in 0.022940s, 1787.2391 runs/s, 2571.8807 assertions/s.

  1) Failure:
TestNetrc#test_missing_environment [/<>/test/test_netrc.rb:203]:
--- expected
+++ actual
@@ -1,2 +1 @@
-# encoding: ASCII-8BIT
-"/<>/.netrc"
+"/build/.netrc"


41 runs, 59 assertions, 1 failures, 0 errors, 0 skips
rake aborted!
Command failed with status (1): [ruby -w  
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/test_lex.rb" 
"test/test_netrc.rb" "test/test_parse.rb" -v]

Tasks: TOP => default
(See full trace by running task with --trace)
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install /<>/debian/ruby-netrc returned 
exit code 1
make: *** [debian/rules:6: binary-indep] Error 1
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


The above build was made with sbuild and schroot, under a user called "buildd" 
having
/build as its home directory.

Note: This does not happen in reproducible builds, but I don't know why.
Apparently, this happens every time, in any way it's built (sbuild or by hand),
as far as the build directory is different than the HOME directory.

Thanks.

Processed: patch available

[Debian Bug Tracking System]

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

> tags 902759 + patch
Bug #902759 [src:python-http-parser] python-http-parser FTBFS with Python 3.7
Added tag(s) patch.
> thanks
Stopping processing here.

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

Processed: Re: Bug#906678: newmat: FTBFS in buster/sid (ld: cannot find -lnewmat)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #906678 [src:newmat] newmat: FTBFS in buster/sid (ld: cannot find -lnewmat)
Added tag(s) patch.

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

Bug#906678: newmat: FTBFS in buster/sid (ld: cannot find -lnewmat)

[Adrian Bunk]

Control: tags -1 patch

On Sun, Aug 19, 2018 at 04:36:41PM +, Santiago Vila wrote:
>...
> /bin/bash ./libtool  --tag=CXX   --mode=link x86_64-linux-gnu-g++  -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wall -g  -O2 -std=gnu++98 -lnewmat -Wl,-z,relro 
> -Wl,-z,now -o example example.o  
> libtool: link: x86_64-linux-gnu-g++ -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wall -g -O2 -std=gnu++98 -Wl,-z -Wl,relro -Wl,-z 
> -Wl,now -o example example.o  -lnewmat
> /usr/bin/ld: cannot find -lnewmat
> collect2: error: ld returned 1 exit status
> make[2]: *** [Makefile:570: example] Error 1
>...

A fixed newmat-1.10.4-libtool.diff is attached.

cu
Adrian

-- 

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

Author: Philippe Coval 
Date:   Sat Aug 1 00:56:03 2009 +0200
Description: ???

--- /dev/null
+++ b/configure.in
@@ -0,0 +1,35 @@
+#   -*- Autoconf -*-
+# Process this file with autoconf to produce a configure script.
+AC_PREREQ(2.59)
+AC_INIT(newmat, 1.10.2, r...@users.sf.net)
+AM_INIT_AUTOMAKE(libnewmat, 1.10.2)
+
+AC_CONFIG_SRCDIR([config.h.in])
+AC_CONFIG_HEADER([config.h])
+# AC_CONFIG_FILES([Makefile]) 
+
+AC_LANG_CPLUSPLUS
+# Checks for programs.
+AC_PROG_CXX
+AC_PROG_CC
+AC_PROG_INSTALL
+AC_PROG_LIBTOOL
+
+# Checks for libraries.
+
+# Checks for header files.
+AC_CHECK_HEADER( [ float.h , cstdlib , setjmp.h , limits ] )
+
+# Checks for typedefs, structures, and compiler characteristics.
+AC_HEADER_STDBOOL
+AC_C_CONST
+AC_C_INLINE
+AC_TYPE_SIZE_T
+AC_STRUCT_TM
+
+# Checks for library functions.
+AC_CHECK_FUNCS([floor pow sqrt])
+AC_OUTPUT( [Makefile] )
+
+
+#eof "Id: configure.in -- pcoval $"
--- /dev/null
+++ b/Makefile.am
@@ -0,0 +1,37 @@
+#ident "$Id: Makefile.am -- pcoval"
+lib_LTLIBRARIES = libnewmat.la
+
+libnewmat_la_LDFLAGS = -version-info 10:0:0
+
+libnewmat_la_SOURCES = \
+  newmat1.cpp newmat2.cpp newmat3.cpp newmat4.cpp newmat5.cpp newmat6.cpp \
+  newmat7.cpp newmat8.cpp newmatex.cpp bandmat.cpp submat.cpp myexcept.cpp \
+  cholesky.cpp evalue.cpp fft.cpp hholder.cpp jacobi.cpp newfft.cpp \
+  sort.cpp svd.cpp newmatrm.cpp newmat9.cpp
+ #
+
+pkgincludedir = $(includedir)/newmat
+
+pkginclude_HEADERS = \
+  config.h include.h \
+  boolean.h controlw.h myexcept.h newmat.h newmatnl.h newmatrm.h solution.h \
+  newmatap.h  newmatio.h  newmatrc.h  precisio.h
+ #
+
+bin_PROGRAMS = example test_exc tmt
+
+example_SOURCES = example.cpp
+example_LDADD = libnewmat.la
+
+test_exc_SOURCES = test_exc.cpp
+test_exc_LDADD = libnewmat.la
+
+
+tmt_SOURCES = tmt.cpp \
+  tmt1.cpp tmt2.cpp tmt3.cpp tmt4.cpp tmt5.cpp tmt6.cpp tmt7.cpp tmt8.cpp \
+  tmt9.cpp tmta.cpp tmtb.cpp tmtc.cpp tmtd.cpp tmte.cpp tmtf.cpp tmtg.cpp \
+  tmth.cpp tmti.cpp tmtj.cpp tmtk.cpp tmtl.cpp tmtm.cpp
+ #
+tmt_LDADD = libnewmat.la
+
+#eof "$Id: Makefile.am -- pcoval"
--- a/newmat.h
+++ b/newmat.h
@@ -560,6 +560,8 @@ public:
 
 
 
+class Matrix;
+Real DotProduct(const Matrix& A, const Matrix& B);
 class Matrix : public GeneralMatrix // usual rectangular matrix
 {
GeneralMatrix* Image() const;// copy of matrix
@@ -1207,6 +1209,12 @@ public:
NEW_DELETE(AddedMatrix)
 };
 
+class SPMatrix;
+#ifndef TEMPS_DESTROYED_QUICKLY
+   SPMatrix SP(const BaseMatrix&, const BaseMatrix&);
+#else
+   SPMatrix& SP(const BaseMatrix&, const BaseMatrix&);
+#endif
 class SPMatrix : public AddedMatrix
 {
 protected:
@@ -1230,6 +1238,12 @@ public:
NEW_DELETE(SPMatrix)
 };
 
+class KPMatrix;
+#ifndef TEMPS_DESTROYED_QUICKLY
+   KPMatrix KP(const BaseMatrix&, const BaseMatrix&);
+#else
+   KPMatrix& KP(const BaseMatrix&, const BaseMatrix&);
+#endif
 class KPMatrix : public MultipliedMatrix
 {
 protected:
@@ -1328,6 +1342,12 @@ public:
NEW_DELETE(ShiftedMatrix)
 };
 
+class NegShiftedMatrix;
+#ifndef TEMPS_DESTROYED_QUICKLY
+   NegShiftedMatrix operator-(Real, const BaseMatrix&);
+#else
+   NegShiftedMatrix& operator-(Real, const BaseMatrix&);
+#endif
 class NegShiftedMatrix : public ShiftedMatrix
 {
 protected:
--- a/tmt1.cpp
+++ b/tmt1.cpp
@@ -10,6 +10,7 @@
 #include "tmt.h"
 
 #ifdef use_namespace
+using namespace std; //#~rzr : needed for msvc
 using namespace NEWMAT;
 #endif
 
--- a/tmtm.cpp
+++ b/tmtm.cpp
@@ -8,6 +8,7 @@
 #include "tmt.h"
 
 #ifdef use_namespace
+using namespace std; //#~rzr : needed for msvc
 using namespace NEWMAT;
 #endif
 
--- a/newmatnl.cpp
+++ b/newmatnl.cpp
@@ -10,6 +10,7 @@
 #include "newmatnl.h"
 
 #ifdef use_namespace
+using namespace std; //#~rzr : needed for msvc
 namespace NEWMAT {
 #endif
 
--- a/include.h
+++ b/include.h
@@ -7,7 +7,9 @@
 #ifndef INCLUDE_LIB
 #define INCLUDE_LIB
 
-//#define use_namespace   // define name spaces

Processed: tagging 906678

[Debian Bug Tracking System]

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

> tags 906678 + buster sid
Bug #906678 [src:newmat] newmat: FTBFS in buster/sid (ld: cannot find -lnewmat)
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Bug#906659: keepassxc: FTBFS in buster/sid (invalid use of incomplete type â class QButtonGroupâ )

[Nazar Zhuk]

This is fixed upstream in 2.3.3.
Related upstream bug:
https://github.com/keepassxreboot/keepassxc/issues/2048
Upstream patch:
https://github.com/keepassxreboot/keepassxc/commit/3bbc6ac0e6298d27bfe0c41999460cafda8edf18

Bug#903330: marked as done (glogg: FTBFS in buster/sid (dh_installdocs: Cannot find "README"))

[Debian Bug Tracking System]

Your message dated Sun, 19 Aug 2018 17:34:08 +
with message-id 
and subject line Bug#903330: fixed in glogg 1.1.4-1.1
has caused the Debian Bug report #903330,
regarding glogg: FTBFS in buster/sid (dh_installdocs: Cannot find "README")
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.)


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

Dear maintainer:

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


[...]
 debian/rules build-arch
test -x debian/rules
mkdir -p "."
CDBS WARNING:DEB_DH_MD5SUMS_ARGS is deprecated since 0.4.85
cd . && qmake -qt=5 VERSION=1.1.4-1 'QMAKE_CC = cc' 'QMAKE_CXX = g++' 
'QMAKE_CFLAGS_RELEASE = -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security' 'QMAKE_CXXFLAGS_RELEASE = -Wdate-time 
-D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security' 
'QMAKE_LFLAGS_RELEASE = -Wl,-z,relro'
Info: creating stash file /<>/.qmake.stash
Project MESSAGE: Building using system dynamic Boost libraries
Project MESSAGE: Support for D-BUS will be included
Project MESSAGE: Version checker will NOT be included
Project MESSAGE: File watching using inotify
/usr/bin/make -C . 
make[1]: Entering directory '/<>'
markdown doc/documentation.markdown | sed -f finish.sed >doc/documentation.html
/usr/lib/qt5/bin/uic src/optionsdialog.ui -o 
.ui/release-shared/ui_optionsdialog.h

[... snipped ...]

g++ -c -g -Wextra -std=c++0x -DGLOGG_VERSION=\"1.1.4-1\" -DGLOGG_SUPPORTS_DBUS 
-DGLOGG_SUPPORTS_INOTIFY -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -W -D_REENTRANT -fPIC 
-DFILELOG_MAX_LEVEL="logDEBUG" -DQT_NO_DEBUG -DQT_WIDGETS_LIB -DQT_GUI_LIB 
-DQT_NETWORK_LIB -DQT_DBUS_LIB -DQT_CORE_LIB -I. -Isrc -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/QtNetwork -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtDBus -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtCore -I.moc/release-shared -isystem 
/usr/include/libdrm -I.ui/release-shared 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o 
.obj/release-shared/moc_overviewwidget.o 
.moc/release-shared/moc_overviewwidget.cpp
/usr/lib/qt5/bin/moc -DFILELOG_MAX_LEVEL="logDEBUG" -DQT_NO_DEBUG 
-DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_DBUS_LIB -DQT_CORE_LIB 
--include /<>/.moc/release-shared/moc_predefs.h 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -I/<> 
-I/<>/src -I/usr/include/x86_64-linux-gnu/qt5 
-I/usr/include/x86_64-linux-gnu/qt5/QtWidgets 
-I/usr/include/x86_64-linux-gnu/qt5/QtGui 
-I/usr/include/x86_64-linux-gnu/qt5/QtNetwork 
-I/usr/include/x86_64-linux-gnu/qt5/QtDBus 
-I/usr/include/x86_64-linux-gnu/qt5/QtCore -I/usr/include/c++/7 
-I/usr/include/x86_64-linux-gnu/c++/7 -I/usr/include/c++/7/backward 
-I/usr/lib/gcc/x86_64-linux-gnu/7/include -I/usr/local/include 
-I/usr/lib/gcc/x86_64-linux-gnu/7/include-fixed -I/usr/include/x86_64-linux-gnu 
-I/usr/include src/quickfindmux.h -o .moc/release-shared/moc_quickfindmux.cpp
g++ -c -g -Wextra -std=c++0x -DGLOGG_VERSION=\"1.1.4-1\" -DGLOGG_SUPPORTS_DBUS 
-DGLOGG_SUPPORTS_INOTIFY -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -W -D_REENTRANT -fPIC 
-DFILELOG_MAX_LEVEL="logDEBUG" -DQT_NO_DEBUG -DQT_WIDGETS_LIB -DQT_GUI_LIB 
-DQT_NETWORK_LIB -DQT_DBUS_LIB -DQT_CORE_LIB -I. -Isrc -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/QtNetwork -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtDBus -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtCore -I.moc/release-shared -isystem 
/usr/include/libdrm -I.ui/release-shared 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o 
.obj/release-shared/moc_quickfindmux.o .moc/release-shared/moc_quickfindmux.cpp
/usr/lib/qt5/bin/moc -DFILELOG_MAX_LEVEL="logDEBUG" -DQT_NO_DEBUG 
-DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_DBUS_LIB -DQT_CORE_LIB 
--include /<>/.moc/release-shared/moc_predefs.h 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -I/<> 
-I/<>/src 

Bug#906682: llvmlite: FTBFS when built with dpkg-buildpackage -A

[Santiago Vila]

Package: src:llvmlite
Version: 0.24.0-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package with dpkg-buildpackage -A but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2,python3,sphinxdoc --buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_autoreconf -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild

[... snipped ...]

   dh_link -i -O--buildsystem=pybuild
   dh_strip_nondeterminism -i -O--buildsystem=pybuild
   dh_compress -i -O--buildsystem=pybuild
   dh_fixperms -i -O--buildsystem=pybuild
   dh_missing -i -O--buildsystem=pybuild
   dh_installdeb -i -O--buildsystem=pybuild
   debian/rules override_dh_gencontrol
make[1]: Entering directory '/<>'
dh_gencontrol
dpkg-gencontrol: warning: package llvmlite-doc: unused substitution variable 
${sphinxdoc:Built-Using}
echo "Conflicts: python3-llvmlite-dbgsym" >> 
debian/.debhelper/python-llvmlite/dbgsym-root/DEBIAN/control
/bin/sh: 1: cannot create 
debian/.debhelper/python-llvmlite/dbgsym-root/DEBIAN/control: Directory 
nonexistent
make[1]: *** [debian/rules:27: override_dh_gencontrol] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:8: binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


To reproduce, please try "dpkg-buildpackage -A".

Hint: Try splitting override_dh_gencontrol into override_dh_gencontrol-arch
and override_dh_gencontrol-indep.

Note: Please consider uploading in source-only form (dpkg-buildpackage -S)
so that this kind of bugs never propagate to testing. We would also get
official build logs for the "all" architecture here:

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

Thanks.

Bug#842815: Help needed for change of build system to gradle of package libsis-jhdf5-java

[olivier sallou]

Le dim. 19 août 2018 à 16:17, Bernd Rinn  a écrit :

> On 08/19/2018 04:02 PM, olivier sallou wrote:
> >
> >
> > Le dim. 19 août 2018 à 15:23, Bernd Rinn  > > a écrit :
> >
> > Hi Andreas,
> >
> > I have no idea why the classes are missing for you as they are all
> > present in our ivy-repository which we use for dependency resolution.
> > Maybe there is an issue with your gradle build environment?
> >
> >
> > In debian, all deps must be availlable as debian packages, they are not
> > downloaded from remote repos.
> > So i think 'problem' is those dependencies are not packaged in debian
> >  They should be packaged first, then added as package build dependencies.
>
> The old build procedure involved Ivy with a publicly accessible ivy
> repository, the new build procedure is self-contained. Putting this into
> Debian packages in a form compliant with Debian policies is your task at
> Debian.
>
Agree :-) just explaining what the issue is.

Olivier

>
> Bernd
>
> > Anyway, I have now simplified the build process by removing automatic
> > dependency resolution via ivy altogether. Can you please check
> whether
> > the build works for you now when you use the build procedure on HEAD?
> >
> > All the best,
> > Bernd
> >
> > On 08/16/2018 06:46 AM, Andreas Tille wrote:
> > > Hi Bernd,
> > >
> > > could you give some hints about the missing classes?
> > >
> > > On Tue, Aug 14, 2018 at 12:23:22PM +0200, olivier sallou wrote:
> > >> Le mar. 14 août 2018 à 11:32, Andreas Tille  > > a écrit :
> > >>
> > >>> A problem occurred evaluating root project 'libsis-jhdf5-java'.
> >  Could not resolve all dependencies for configuration ':runtime'.
> > >>>> Could not resolve cisd:cisd-args4j:+.
> > >>>  Required by:
> > >>>  project :
> > >>>   > No cached version listing for cisd:cisd-args4j:+
> > available for
> > >>> offline mode.
> > >>>> Could not resolve cisd:cisd-base:+.
> > >>>  Required by:
> > >>>  project :
> > >>>   > No cached version listing for cisd:cisd-base:+ available
> for
> > >>> offline mode.
> > >>>> Could not resolve rinn:restrictions:+.
> > >>>  Required by:
> > >>>  project :
> > >>>   > No cached version listing for rinn:restrictions:+
> > available for
> > >>> offline mode.
> > >>>
> > >>>
> > >> I do not see in build deps things related to:
> > >>cisd:cisd-args4, cisd:cisd-base, rinn:restrictions
> > >
> > > I have no idea what these are. :-(
> > >
> > > Kind regards
> > >
> > >   Andreas.
> > >
> > >>> [1] https://salsa.debian.org/med-team/libsis-jhdf5-java
>
>

Bug#906679: pam-p11 FTBFS on 32bit: error: comparison between signed and unsigned integer expressions

[Adrian Bunk]

Source: pam-p11
Version: 0.2.0-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=pam-p11=sid

...
pam_p11.c: In function 'randomize':
pam_p11.c:556:36: error: comparison between signed and unsigned integer 
expressions [-Werror=sign-compare]
  if (0 <= fd && read(fd, r, r_len) == r_len) {
^~

Bug#906678: newmat: FTBFS in buster/sid (ld: cannot find -lnewmat)

[Santiago Vila]

Package: src:newmat
Version: 1.10.4-6
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-arch
QUILT_PATCHES=debian/patches \
quilt --quiltrc /dev/null push -a || test $? = 2
Applying patch newmat-1.10.4-msvc.diff
patching file newmat.dsp
patching file example.dsp

[... snipped ...]

touch configure-stamp
dh_testdir
/usr/bin/make
make[1]: Entering directory '/<>'
/usr/bin/make  all-am
make[2]: Entering directory '/<>'
x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I.   -Wdate-time -D_FORTIFY_SOURCE=2  -g 
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -g  -O2 -std=gnu++98 -MT example.o -MD -MP -MF 
.deps/example.Tpo -c -o example.o example.cpp
mv -f .deps/example.Tpo .deps/example.Po
/bin/bash ./libtool  --tag=CXX   --mode=link x86_64-linux-gnu-g++  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -g  -O2 -std=gnu++98 -lnewmat -Wl,-z,relro 
-Wl,-z,now -o example example.o  
libtool: link: x86_64-linux-gnu-g++ -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -g -O2 -std=gnu++98 -Wl,-z -Wl,relro -Wl,-z 
-Wl,now -o example example.o  -lnewmat
/usr/bin/ld: cannot find -lnewmat
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:570: example] Error 1
make[2]: Leaving directory '/<>'
make[1]: *** [Makefile:428: all] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:56: build-stamp] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


The build was made with "dpkg-buildpackage -B" in my autobuilder.
Most probably, it also fails here in reproducible builds:

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

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.

Bug#906513: marked as done (urlview: FTBFS in buster/sid (aclocal-1.15: not found))

[Debian Bug Tracking System]

Your message dated Sun, 19 Aug 2018 16:37:27 +
with message-id 
and subject line Bug#906513: fixed in urlview 0.9-21
has caused the Debian Bug report #906513,
regarding urlview: FTBFS in buster/sid (aclocal-1.15: not found)
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.)


-- 
906513: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906513
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:urlview
Version: 0.9-20
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-arch
test -x debian/rules
mkdir -p "."
set -e;   mv ./config.guess ./config.guess.cdbs-orig; cp --remove-destination 
/usr/share/misc/config.guess ./config.guess;
set -e;   mv ./config.sub ./config.sub.cdbs-orig; cp --remove-destination 
/usr/share/misc/config.sub ./config.sub;
cd . && libtoolize -c -f
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: You should add the contents of the following files to 'aclocal.m4':
libtoolize:   '/usr/share/aclocal/libtool.m4'
libtoolize:   '/usr/share/aclocal/ltoptions.m4'
libtoolize:   '/usr/share/aclocal/ltsugar.m4'
libtoolize:   '/usr/share/aclocal/ltversion.m4'
libtoolize:   '/usr/share/aclocal/lt~obsolete.m4'
libtoolize: Remember to add 'LT_INIT' to configure.in.
libtoolize: Consider adding 'AC_CONFIG_MACRO_DIRS([m4])' to configure.in,
libtoolize: and rerunning libtoolize and aclocal.
libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
cd . &&   aclocal-1.15 
/bin/sh: 1: aclocal-1.15: not found
make: *** [/usr/share/cdbs/1/class/autotools-files.mk:70: 
debian/stamp-autotools-files] Error 127
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


The build was made with "dpkg-buildpackage -B" in my autobuilder.
Most probably, it also fails here in reproducible builds:

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

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: urlview
Source-Version: 0.9-21

We believe that the bug you reported is fixed in the latest version of
urlview, 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.
Emanuele Rocca  (supplier of updated urlview package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 19 Aug 2018 15:00:03 +0200
Source: urlview
Binary: urlview
Architecture: source amd64
Version: 0.9-21
Distribution: unstable
Urgency: medium
Maintainer: Emanuele Rocca 
Changed-By: Emanuele Rocca 
Description:
 urlview- Extracts URLs from text
Closes: 906513
Changes:
 urlview (0.9-21) unstable; urgency=medium
 .
   * Use aclocal-1.16. Closes: #906513
   * url_handler.sh uses sensible-browser, add dependency on sensible-utils.
   * Set debhelper compatibility level to 10.
   * Add Vcs-{Browser,Git} poiting to salsa.
   * Update Standards-Version to 4.2.0.
Checksums-Sha1:
 6623b6f35ba98a906fd85faa3301251fbd92d511 1806 urlview_0.9-21.dsc
 52daadf63ea7525db3d7a210e63b574db704c411 166631 urlview_0.9-21.diff.gz
 5dc794bc70c72a434e61c01aa99b58088f587062 19900 urlview-dbgsym_0.9-21_amd64.deb
 8bf91ee5e56d6ef984f914dfe15ad314271e9943 5902 urlview_0.9-21_amd64.buildinfo
 490f0ff168dc333d23e2bd6a318a912e4910348b 23996 urlview_0.9-21_amd64.deb
Checksums-Sha256:
 2a8e0397a25e3e5ce791cf733cd6793dde09c6a5d388dca9a7f90b81f503e607 1806 
urlview_0.9-21.dsc
 efdf6a279d123952820dd6185ab9399ee1bf081ea3dd613dc96933cd1827a9e9 166631 
urlview_0.9-21.diff.gz
 1f981ddf6f77adca189b53a2f58c027bd569c1b2ee2b7bb8b2d8bea04ad7883e 19900 
urlview-dbgsym_0.9-21_amd64.deb
 b2985a8a8ff4aeb9d56fd3f481784500ce9b8a4e717d5da7eb13822f60c4f215 5902 

Bug#906676: oaklisp: binary-any FTBFS

[Adrian Bunk]

Source: oaklisp
Version: 1.3.7-1
Severity: serious
Tags: ftbfs

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

...
Making all in doc
make[3]: Entering directory '/<>/doc'
cd lang/ && false -pdf lang.tex \
 || cp ../prebuilt/doc/lang/lang.pdf lang/lang.pdf
cd lim/ && false -pdf lim.tex \
 || cp ../prebuilt/doc/lim/lim.pdf lim/lim.pdf
cp: cannot stat '../prebuilt/doc/lang/lang.pdf': No such file or directory
make[3]: *** [Makefile:516: lang/lang.pdf] Error 1


This tries to build the documentation,
whose buid dependencies are only in Build-Depends-Indep.

Bug#906506: marked as done (quesoglc: FTBFS in buster/sid (config.h: No such file or directory))

[Debian Bug Tracking System]

Your message dated Sun, 19 Aug 2018 15:49:18 +
with message-id 
and subject line Bug#906418: fixed in fribidi 1.0.5-2
has caused the Debian Bug report #906418,
regarding quesoglc: FTBFS in buster/sid (config.h: No such file or directory)
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.)


-- 
906418: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906418
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:quesoglc
Version: 0.7.2-5
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-arch
dh build-arch --parallel --with autoreconf
dh: Compatibility levels before 9 are deprecated (level 7 in use)
   dh_update_autotools_config -a -O--parallel
   debian/rules override_dh_autoreconf
make[1]: Entering directory '/<>'
touch NEWS
dh_autoreconf
aclocal: warning: autoconf input should be named 'configure.ac', not 
'configure.in'
configure.in:55: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in 
body
../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from...
../../lib/autoconf/general.m4:2672: _AC_LINK_IFELSE is expanded from...
../../lib/autoconf/general.m4:2689: AC_LINK_IFELSE is expanded from...
build/m4/libtool.m4:1018: _LT_SYS_MODULE_PATH_AIX is expanded from...

[... snipped ...]

   (void (CALLBACK *) (GLdouble[3], void*[4],
   ^~
  GLfloat[4], void**, void*))
  ~~~
   __glcCombineCallback);
   
In file included from /usr/include/GL/glew.h:1202,
 from ../include/internal.h:38,
 from ../src/scalable.c:25:
/usr/include/GL/glu.h:340:87: note: expected '_GLUfuncptr' {aka 'void 
(*)(void)'} but argument is of type 'void (*)(GLdouble *, void **, GLfloat *, 
void **, void *)' {aka 'void (*)(double *, void **, float *, void **, void *)'}
 GLAPI void GLAPIENTRY gluTessCallback (GLUtesselator* tess, GLenum which, 
_GLUfuncptr CallBackFunc);
   
^~~~
../src/scalable.c:608:7: warning: passing argument 3 of 'gluTessCallback' from 
incompatible pointer type [-Wincompatible-pointer-types]
   (void (CALLBACK *) (GLenum, void*))__glcBeginCallback);
   ^
In file included from /usr/include/GL/glew.h:1202,
 from ../include/internal.h:38,
 from ../src/scalable.c:25:
/usr/include/GL/glu.h:340:87: note: expected '_GLUfuncptr' {aka 'void 
(*)(void)'} but argument is of type 'void (*)(GLenum,  void *)' {aka 'void 
(*)(unsigned int,  void *)'}
 GLAPI void GLAPIENTRY gluTessCallback (GLUtesselator* tess, GLenum which, 
_GLUfuncptr CallBackFunc);
   
^~~~
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../include -I../src -D_REENTRANT 
-DGLEW_MX -pthread -I/usr/include/uuid -I/usr/include/freetype2 
-I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/libpng16 
-pthread -pthread -I/usr/include/fribidi -g -O2 -c ../src/scalable.c -o 
libGLC_la-scalable.o >/dev/null 2>&1
/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
-I../include-I../src -D_REENTRANT -DGLEW_MX -pthread -I/usr/include/uuid 
-I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/freetype2 
-I/usr/include/libpng16 -pthread -pthread -I/usr/include/fribidi -g -O2 -c -o 
libGLC_la-transform.lo `test -f '../src/transform.c' || echo 
'./'`../src/transform.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../include -I../src -D_REENTRANT 
-DGLEW_MX -pthread -I/usr/include/uuid -I/usr/include/freetype2 
-I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/libpng16 
-pthread -pthread -I/usr/include/fribidi -g -O2 -c ../src/transform.c  -fPIC 
-DPIC -o .libs/libGLC_la-transform.o
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../include -I../src -D_REENTRANT 
-DGLEW_MX -pthread -I/usr/include/uuid -I/usr/include/freetype2 
-I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/libpng16 
-pthread -pthread -I/usr/include/fribidi -g -O2 -c ../src/transform.c -o 
libGLC_la-transform.o >/dev/null 2>&1
/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
-I../include-I../src -D_REENTRANT -DGLEW_MX -pthread -I/usr/include/uuid 
-I/usr/include/freetype2 -I/usr/include/libpng16 

Bug#906418: marked as done (warmux: FTBFS in buster/sid (config.h: No such file or directory))

[Debian Bug Tracking System]

Your message dated Sun, 19 Aug 2018 15:49:18 +
with message-id 
and subject line Bug#906418: fixed in fribidi 1.0.5-2
has caused the Debian Bug report #906418,
regarding warmux: FTBFS in buster/sid (config.h: No such file or directory)
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.)


-- 
906418: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906418
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:warmux
Version: 1:11.04.1+repack2-3
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
configure.ac:284: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in 
body
../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from...
../../lib/autoconf/general.m4:2740: _AC_RUN_IFELSE is expanded from...
../../lib/m4sugar/m4sh.m4:639: AS_IF is expanded from...
../../lib/autoconf/general.m4:2759: AC_RUN_IFELSE is expanded from...
configure.ac:284: the top level
configure.ac:284: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in 
body
../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from...
../../lib/autoconf/general.m4:2740: _AC_RUN_IFELSE is expanded from...
../../lib/m4sugar/m4sh.m4:639: AS_IF is expanded from...

[... snipped ...]


* [Optional] Bi-directional rendering (fribidi) : yes
* [Optional] Internationalisation (gettext) : yes
* [Optional] Index and game servers : yes
***

Execute make to compile then execute make install to install...
make[1]: Leaving directory '/<>/warmux-11.04.1+repack2'
   dh_auto_build -i
make -j1
make[1]: Entering directory '/<>/warmux-11.04.1+repack2'
find: 'build/android/jni': No such file or directory
find: 'build/android/src': No such file or directory
find: 'build/android/res': No such file or directory
find: 'build/symbian': No such file or directory
Making all in data
make[2]: Entering directory '/<>/warmux-11.04.1+repack2/data'
make[2]: Nothing to be done for 'all'.
make[2]: Leaving directory '/<>/warmux-11.04.1+repack2/data'
Making all in lib
make[2]: Entering directory '/<>/warmux-11.04.1+repack2/lib'
Making all in warmux
make[3]: Entering directory '/<>/warmux-11.04.1+repack2/lib/warmux'
Making all in .
make[4]: Entering directory '/<>/warmux-11.04.1+repack2/lib/warmux'
g++ -DHAVE_CONFIG_H -I. -I../../lib/warmux/include   -Wdate-time 
-D_FORTIFY_SOURCE=2 -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT 
-I../../lib/warmux/include -I../../lib/fixedpoint  -Wall -Wextra -Wall -Wextra 
-g -O2 -fdebug-prefix-map=/<>/warmux-11.04.1+repack2=. 
-fstack-protector-strong -Wformat -Werror=format-security -I/usr/include/SDL 
-D_GNU_SOURCE=1 -D_REENTRANT -I/usr/include/libpng16 -I/usr/include/libxml2 
-I/usr/include/fribidi -fno-rtti -fno-exceptions -c -o action.o `test -f 
'./action/action.cpp' || echo './'`./action/action.cpp
g++ -DHAVE_CONFIG_H -I. -I../../lib/warmux/include   -Wdate-time 
-D_FORTIFY_SOURCE=2 -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT 
-I../../lib/warmux/include -I../../lib/fixedpoint  -Wall -Wextra -Wall -Wextra 
-g -O2 -fdebug-prefix-map=/<>/warmux-11.04.1+repack2=. 
-fstack-protector-strong -Wformat -Werror=format-security -I/usr/include/SDL 
-D_GNU_SOURCE=1 -D_REENTRANT -I/usr/include/libpng16 -I/usr/include/libxml2 
-I/usr/include/fribidi -fno-rtti -fno-exceptions -c -o action_handler.o `test 
-f './action/action_handler.cpp' || echo './'`./action/action_handler.cpp
g++ -DHAVE_CONFIG_H -I. -I../../lib/warmux/include   -Wdate-time 
-D_FORTIFY_SOURCE=2 -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT 
-I../../lib/warmux/include -I../../lib/fixedpoint  -Wall -Wextra -Wall -Wextra 
-g -O2 -fdebug-prefix-map=/<>/warmux-11.04.1+repack2=. 
-fstack-protector-strong -Wformat -Werror=format-security -I/usr/include/SDL 
-D_GNU_SOURCE=1 -D_REENTRANT -I/usr/include/libpng16 -I/usr/include/libxml2 
-I/usr/include/fribidi -fno-rtti -fno-exceptions -c -o error.o `test -f 
'./base/error.cpp' || echo './'`./base/error.cpp
g++ -DHAVE_CONFIG_H -I. -I../../lib/warmux/include   -Wdate-time 
-D_FORTIFY_SOURCE=2 -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT 
-I../../lib/warmux/include -I../../lib/fixedpoint  -Wall -Wextra -Wall -Wextra 
-g -O2 -fdebug-prefix-map=/<>/warmux-11.04.1+repack2=. 
-fstack-protector-strong -Wformat -Werror=format-security -I/usr/include/SDL 
-D_GNU_SOURCE=1 -D_REENTRANT 

Bug#906418: marked as done (warmux: FTBFS in buster/sid (config.h: No such file or directory))

[Debian Bug Tracking System]

Your message dated Sun, 19 Aug 2018 15:49:18 +
with message-id 
and subject line Bug#906506: fixed in fribidi 1.0.5-2
has caused the Debian Bug report #906506,
regarding warmux: FTBFS in buster/sid (config.h: No such file or directory)
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.)


-- 
906506: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906506
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:warmux
Version: 1:11.04.1+repack2-3
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
configure.ac:284: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in 
body
../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from...
../../lib/autoconf/general.m4:2740: _AC_RUN_IFELSE is expanded from...
../../lib/m4sugar/m4sh.m4:639: AS_IF is expanded from...
../../lib/autoconf/general.m4:2759: AC_RUN_IFELSE is expanded from...
configure.ac:284: the top level
configure.ac:284: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in 
body
../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from...
../../lib/autoconf/general.m4:2740: _AC_RUN_IFELSE is expanded from...
../../lib/m4sugar/m4sh.m4:639: AS_IF is expanded from...

[... snipped ...]


* [Optional] Bi-directional rendering (fribidi) : yes
* [Optional] Internationalisation (gettext) : yes
* [Optional] Index and game servers : yes
***

Execute make to compile then execute make install to install...
make[1]: Leaving directory '/<>/warmux-11.04.1+repack2'
   dh_auto_build -i
make -j1
make[1]: Entering directory '/<>/warmux-11.04.1+repack2'
find: 'build/android/jni': No such file or directory
find: 'build/android/src': No such file or directory
find: 'build/android/res': No such file or directory
find: 'build/symbian': No such file or directory
Making all in data
make[2]: Entering directory '/<>/warmux-11.04.1+repack2/data'
make[2]: Nothing to be done for 'all'.
make[2]: Leaving directory '/<>/warmux-11.04.1+repack2/data'
Making all in lib
make[2]: Entering directory '/<>/warmux-11.04.1+repack2/lib'
Making all in warmux
make[3]: Entering directory '/<>/warmux-11.04.1+repack2/lib/warmux'
Making all in .
make[4]: Entering directory '/<>/warmux-11.04.1+repack2/lib/warmux'
g++ -DHAVE_CONFIG_H -I. -I../../lib/warmux/include   -Wdate-time 
-D_FORTIFY_SOURCE=2 -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT 
-I../../lib/warmux/include -I../../lib/fixedpoint  -Wall -Wextra -Wall -Wextra 
-g -O2 -fdebug-prefix-map=/<>/warmux-11.04.1+repack2=. 
-fstack-protector-strong -Wformat -Werror=format-security -I/usr/include/SDL 
-D_GNU_SOURCE=1 -D_REENTRANT -I/usr/include/libpng16 -I/usr/include/libxml2 
-I/usr/include/fribidi -fno-rtti -fno-exceptions -c -o action.o `test -f 
'./action/action.cpp' || echo './'`./action/action.cpp
g++ -DHAVE_CONFIG_H -I. -I../../lib/warmux/include   -Wdate-time 
-D_FORTIFY_SOURCE=2 -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT 
-I../../lib/warmux/include -I../../lib/fixedpoint  -Wall -Wextra -Wall -Wextra 
-g -O2 -fdebug-prefix-map=/<>/warmux-11.04.1+repack2=. 
-fstack-protector-strong -Wformat -Werror=format-security -I/usr/include/SDL 
-D_GNU_SOURCE=1 -D_REENTRANT -I/usr/include/libpng16 -I/usr/include/libxml2 
-I/usr/include/fribidi -fno-rtti -fno-exceptions -c -o action_handler.o `test 
-f './action/action_handler.cpp' || echo './'`./action/action_handler.cpp
g++ -DHAVE_CONFIG_H -I. -I../../lib/warmux/include   -Wdate-time 
-D_FORTIFY_SOURCE=2 -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT 
-I../../lib/warmux/include -I../../lib/fixedpoint  -Wall -Wextra -Wall -Wextra 
-g -O2 -fdebug-prefix-map=/<>/warmux-11.04.1+repack2=. 
-fstack-protector-strong -Wformat -Werror=format-security -I/usr/include/SDL 
-D_GNU_SOURCE=1 -D_REENTRANT -I/usr/include/libpng16 -I/usr/include/libxml2 
-I/usr/include/fribidi -fno-rtti -fno-exceptions -c -o error.o `test -f 
'./base/error.cpp' || echo './'`./base/error.cpp
g++ -DHAVE_CONFIG_H -I. -I../../lib/warmux/include   -Wdate-time 
-D_FORTIFY_SOURCE=2 -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT 
-I../../lib/warmux/include -I../../lib/fixedpoint  -Wall -Wextra -Wall -Wextra 
-g -O2 -fdebug-prefix-map=/<>/warmux-11.04.1+repack2=. 
-fstack-protector-strong -Wformat -Werror=format-security -I/usr/include/SDL 
-D_GNU_SOURCE=1 -D_REENTRANT 

Bug#906506: marked as done (quesoglc: FTBFS in buster/sid (config.h: No such file or directory))

[Debian Bug Tracking System]

Your message dated Sun, 19 Aug 2018 15:49:18 +
with message-id 
and subject line Bug#906506: fixed in fribidi 1.0.5-2
has caused the Debian Bug report #906506,
regarding quesoglc: FTBFS in buster/sid (config.h: No such file or directory)
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.)


-- 
906506: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906506
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:quesoglc
Version: 0.7.2-5
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-arch
dh build-arch --parallel --with autoreconf
dh: Compatibility levels before 9 are deprecated (level 7 in use)
   dh_update_autotools_config -a -O--parallel
   debian/rules override_dh_autoreconf
make[1]: Entering directory '/<>'
touch NEWS
dh_autoreconf
aclocal: warning: autoconf input should be named 'configure.ac', not 
'configure.in'
configure.in:55: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in 
body
../../lib/autoconf/lang.m4:193: AC_LANG_CONFTEST is expanded from...
../../lib/autoconf/general.m4:2672: _AC_LINK_IFELSE is expanded from...
../../lib/autoconf/general.m4:2689: AC_LINK_IFELSE is expanded from...
build/m4/libtool.m4:1018: _LT_SYS_MODULE_PATH_AIX is expanded from...

[... snipped ...]

   (void (CALLBACK *) (GLdouble[3], void*[4],
   ^~
  GLfloat[4], void**, void*))
  ~~~
   __glcCombineCallback);
   
In file included from /usr/include/GL/glew.h:1202,
 from ../include/internal.h:38,
 from ../src/scalable.c:25:
/usr/include/GL/glu.h:340:87: note: expected '_GLUfuncptr' {aka 'void 
(*)(void)'} but argument is of type 'void (*)(GLdouble *, void **, GLfloat *, 
void **, void *)' {aka 'void (*)(double *, void **, float *, void **, void *)'}
 GLAPI void GLAPIENTRY gluTessCallback (GLUtesselator* tess, GLenum which, 
_GLUfuncptr CallBackFunc);
   
^~~~
../src/scalable.c:608:7: warning: passing argument 3 of 'gluTessCallback' from 
incompatible pointer type [-Wincompatible-pointer-types]
   (void (CALLBACK *) (GLenum, void*))__glcBeginCallback);
   ^
In file included from /usr/include/GL/glew.h:1202,
 from ../include/internal.h:38,
 from ../src/scalable.c:25:
/usr/include/GL/glu.h:340:87: note: expected '_GLUfuncptr' {aka 'void 
(*)(void)'} but argument is of type 'void (*)(GLenum,  void *)' {aka 'void 
(*)(unsigned int,  void *)'}
 GLAPI void GLAPIENTRY gluTessCallback (GLUtesselator* tess, GLenum which, 
_GLUfuncptr CallBackFunc);
   
^~~~
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../include -I../src -D_REENTRANT 
-DGLEW_MX -pthread -I/usr/include/uuid -I/usr/include/freetype2 
-I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/libpng16 
-pthread -pthread -I/usr/include/fribidi -g -O2 -c ../src/scalable.c -o 
libGLC_la-scalable.o >/dev/null 2>&1
/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
-I../include-I../src -D_REENTRANT -DGLEW_MX -pthread -I/usr/include/uuid 
-I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/freetype2 
-I/usr/include/libpng16 -pthread -pthread -I/usr/include/fribidi -g -O2 -c -o 
libGLC_la-transform.lo `test -f '../src/transform.c' || echo 
'./'`../src/transform.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../include -I../src -D_REENTRANT 
-DGLEW_MX -pthread -I/usr/include/uuid -I/usr/include/freetype2 
-I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/libpng16 
-pthread -pthread -I/usr/include/fribidi -g -O2 -c ../src/transform.c  -fPIC 
-DPIC -o .libs/libGLC_la-transform.o
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../include -I../src -D_REENTRANT 
-DGLEW_MX -pthread -I/usr/include/uuid -I/usr/include/freetype2 
-I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/libpng16 
-pthread -pthread -I/usr/include/fribidi -g -O2 -c ../src/transform.c -o 
libGLC_la-transform.o >/dev/null 2>&1
/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
-I../include-I../src -D_REENTRANT -DGLEW_MX -pthread -I/usr/include/uuid 
-I/usr/include/freetype2 -I/usr/include/libpng16 

Bug#906502: marked as done (php-apcu-bc: FTBFS in buster/sid (failing tests))

[Debian Bug Tracking System]

Your message dated Sun, 19 Aug 2018 17:00:41 +0200
with message-id 
and subject line Re: Bug#906502: php-apcu-bc: FTBFS in buster/sid (failing 
tests)
has caused the Debian Bug report #906502,
regarding php-apcu-bc: FTBFS in buster/sid (failing tests)
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.)


-- 
906502: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906502
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:php-apcu-bc
Version: 1.0.3-2
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-arch
dh build-arch --with php --sourcedirectory=apcu_bc-1.0.3
   dh_update_autotools_config -a -O--sourcedirectory=apcu_bc-1.0.3
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
cd apcu_bc-1.0.3 && phpize
Configuring for:
PHP Api Version: 20170718
Zend Module Api No:  20170718
Zend Extension Api No:   320170718
dh_auto_configure --sourcedirectory=apcu_bc-1.0.3 -- --enable-apc
cd apcu_bc-1.0.3 && ./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu 
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode 
--disable-dependency-tracking --enable-apc
configure: WARNING: unrecognized options: --disable-silent-rules, 
--disable-maintainer-mode, --disable-dependency-tracking
checking for grep that handles long lines and -e... /bin/grep

[... snipped ...]

TEST 6/7 [tests/iterator_005_bc.phpt]
FAIL APC compat: APCIterator delete [tests/iterator_005_bc.phpt] 
TEST 7/7 [tests/iterator_008_bc.phpt]
FAIL APC compat: APCIterator general [tests/iterator_008_bc.phpt] 
=
TIME END 2018-08-16 19:42:47

=
TEST RESULT SUMMARY
-
Exts skipped:0
Exts tested :   15
-

Number of tests :7 2
Tests skipped   :5 ( 71.4%) 
Tests warned:0 (  0.0%) (  0.0%)
Tests failed:2 ( 28.6%) (100.0%)
Expected fail   :0 (  0.0%) (  0.0%)
Tests passed:0 (  0.0%) (  0.0%)
-
Time taken  :0 seconds
=

=
FAILED TEST SUMMARY
-
APC compat: APCIterator delete [tests/iterator_005_bc.phpt]
APC compat: APCIterator general [tests/iterator_008_bc.phpt]
=

You may have found a problem in PHP.
This report can be automatically sent to the PHP QA team at
http://qa.php.net/reports and http://news.php.net/php.qa.reports
This gives us a better understanding of PHP's behavior.
If you don't want to send the report immediately you can choose
option "s" to save it.  You can then email it to qa-repo...@lists.php.net later.
Do you want to send this report now? [Yns]: 
Please enter your email address.
(Your address will be mangled so that it will not go out on any
mailinglist in plain text): 
Posting to http://qa.php.net/buildtest-process.php
make[1]: *** [Makefile:133: test] Error 1
make[1]: Leaving directory '/<>/apcu_bc-1.0.3'
dh_auto_test: cd apcu_bc-1.0.3 && make -j1 test VERBOSE=1 returned exit code 2
make: *** [debian/rules:8: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


The build was made with "dpkg-buildpackage -B" in my autobuilder.
Most probably, it also fails here in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/php-apcu-bc.html

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Version: 1.0.4-2

The current version builds fine, so closing the bug.

Ondrej
--
Ondřej 

Bug#855533: mate-dock-applet completely unusable

[Rock Storm]

On Sun, Aug 19, 2018 at 12:00:54AM +, Mike Gabriel wrote:
> Does it help, if you additionally install gir1.2-notify-0.7?

Hi, it does help yes. Installing dock-applet 0.86 and gir1.2-notify-0.7
shows the dock in the panel again. However I am not able to make it
look as it did on version 0.75-1. This is how version 0.75-1 looks like
[1] (applet has the same background as the rest of the panel). With
version 0.86-1 and gir1.2-notify-0.7 I am unable to change the
dock-applet's background color to match the rest of the panel [2]. 

 [1] https://imgur.com/a/ePR2wV3 
 [2] https://imgur.com/a/vTCjApt 

Thanks a lot for your time,

-- 
Rock Storm
GPG KeyID: 4096R/C96832FD
GPG Fingerprint:
 C304 34B3 632C 464C 2FAF  C741 0439 CF52 C968 32FD

Bug#906648: marked as done (apt-get update crash)

[Debian Bug Tracking System]

Your message dated Sun, 19 Aug 2018 15:04:27 +
with message-id 
and subject line Bug#906538: fixed in appstream 0.12.2-2
has caused the Debian Bug report #906538,
regarding apt-get update crash
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.)


-- 
906538: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906538
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apt
Version: 1.6.3
Severity: important
File: /usr/bin/apt-get

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi,

sudo agt-get crashed every time:

~$ sudo apt-get update
OK:1 https://josm.openstreetmap.de/apt alldist InRelease
OK:2 https://repo.skype.com/deb stable InRelease
OK:3 https://wire-app.wire.com/linux/debian stable InRelease
OK:4 http://deb.debian.org/debian buster InRelease
OK:5 http://mirror.1und1.de/debian buster InRelease
OK:6 http://linux.teamviewer.com/deb stable InRelease
OK:7 http://security.debian.org buster/updates InRelease
Ign:8 http://dl.google.com/linux/chrome/deb stable InRelease
OK:9 http://linux.teamviewer.com/deb preview InRelease
OK:10 http://mirror.1und1.de/debian buster-updates InRelease
OK:11 http://dl.google.com/linux/chrome/deb stable Release
OK:12 http://mirror.1und1.de/debian unstable InRelease
OK:13 http://mirror.1und1.de/debian experimental InRelease

(appstreamcli:9982): GLib-CRITICAL **: 10:42:58.415: g_variant_builder_end:
assertion '!GVSB(builder)->uniform_item_types || GVSB(builder)->prev_item_type
!= NULL || g_variant_type_is_definite (GVSB(builder)->type)' failed

(appstreamcli:9982): GLib-CRITICAL **: 10:42:58.415: g_variant_new_variant:
assertion 'value != NULL' failed

(appstreamcli:9982): GLib-ERROR **: 10:42:58.415: g_variant_new_parsed:
11-13:invalid GVariant format string
Trace/breakpoint trap
Paketlisten werden gelesen... Fertig
E: Problem executing scripts APT::Update::Post-Invoke-Success 'if /usr/bin/test
- -w /var/cache/app-info -a -e /usr/bin/appstreamcli; then appstreamcli refresh-
cache > /dev/null; fi'
E: Sub-process returned an error code


CU
Jörg



- -- Package-specific info:

- -- apt-config dump --

APT "";
APT::Architecture "amd64";
APT::Build-Essential "";
APT::Build-Essential:: "build-essential";
APT::Install-Recommends "true";
APT::Install-Suggests "0";
APT::Sandbox "";
APT::Sandbox::User "_apt";
APT::Authentication "";
APT::Authentication::TrustCDROM "true";
APT::NeverAutoRemove "";
APT::NeverAutoRemove:: "^firmware-linux.*";
APT::NeverAutoRemove:: "^linux-firmware$";
APT::NeverAutoRemove:: "^linux-image-4\.16\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-image-4\.17\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-headers-4\.16\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-headers-4\.17\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-image-extra-4\.16\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-image-extra-4\.17\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-modules-4\.16\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-modules-4\.17\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-modules-extra-4\.16\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-modules-extra-4\.17\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-signed-image-4\.16\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-signed-image-4\.17\.0-1-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-image-4\.16\.0-2-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-image-4\.17\.0-1-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-headers-4\.16\.0-2-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-headers-4\.17\.0-1-amd64$";
APT::NeverAutoRemove:: "^gnumach-image-4\.16\.0-2-amd64$";
APT::NeverAutoRemove:: "^gnumach-image-4\.17\.0-1-amd64$";
APT::NeverAutoRemove:: "^.*-modules-4\.16\.0-2-amd64$";
APT::NeverAutoRemove:: "^.*-modules-4\.17\.0-1-amd64$";
APT::NeverAutoRemove:: "^.*-kernel-4\.16\.0-2-amd64$";
APT::NeverAutoRemove:: "^.*-kernel-4\.17\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-backports-modules-.*-4\.16\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-backports-modules-.*-4\.17\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-modules-.*-4\.16\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-modules-.*-4\.17\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-tools-4\.16\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-tools-4\.17\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-cloud-tools-4\.16\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-cloud-tools-4\.17\.0-1-amd64$";
APT::VersionedKernelPackages "";
APT::VersionedKernelPackages:: "linux-image";
APT::VersionedKernelPackages:: "linux-headers";
APT::VersionedKernelPackages:: "linux-image-extra";
APT::VersionedKernelPackages:: "linux-modules";
APT::VersionedKernelPackages:: "linux-modules-extra";

Bug#906538: marked as done (appstream: apt-get update fails due to appstream crash)

[Debian Bug Tracking System]

Your message dated Sun, 19 Aug 2018 15:04:27 +
with message-id 
and subject line Bug#906538: fixed in appstream 0.12.2-2
has caused the Debian Bug report #906538,
regarding appstream: apt-get update fails due to appstream crash
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.)


-- 
906538: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906538
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: appstream
Version: 0.12.2-1
Severity: critical
Justification: breaks unrelated software

as of today, apt-get upstream fails because appstreamcli crashes as follows:

sudo appstreamcli refresh-cache

(appstreamcli:7230): GLib-CRITICAL **: 09:35:41.559: g_variant_builder_end: 
assertion '!GVSB(builder)->uniform_item_types || GVSB(builder)->prev_item_type 
!= NULL || g_variant_type_is_definite (GVSB(builder)->type)' failed

(appstreamcli:7230): GLib-CRITICAL **: 09:35:41.559: g_variant_new_variant: 
assertion 'value != NULL' failed

(appstreamcli:7230): GLib-ERROR **: 09:35:41.559: g_variant_new_parsed: 
11-13:invalid GVariant format string
Trace/Breakpoint ausgelöst


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

Kernel: Linux 4.17.0-1-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 appstream depends on:
ii  libappstream4  0.12.2-1
ii  libc6  2.27-5
ii  libglib2.0-0   2.56.1-2

appstream recommends no packages.

Versions of packages appstream suggests:
ii  apt-config-icons  0.12.2-1
ii  curl  7.61.0-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: appstream
Source-Version: 0.12.2-2

We believe that the bug you reported is fixed in the latest version of
appstream, 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.
Matthias Klumpp  (supplier of updated appstream package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 19 Aug 2018 16:32:23 +0200
Source: appstream
Binary: appstream libappstream4 libappstream-dev gir1.2-appstream-1.0 
libappstreamqt2 libappstreamqt-dev appstream-doc apt-config-icons 
apt-config-icons-hidpi apt-config-icons-large apt-config-icons-large-hidpi
Architecture: source amd64 all
Version: 0.12.2-2
Distribution: unstable
Urgency: medium
Maintainer: Matthias Klumpp 
Changed-By: Matthias Klumpp 
Description:
 appstream  - Software component metadata management
 appstream-doc - Developer documentation for AppStream
 apt-config-icons - APT configuration snippet to enable icon downloads
 apt-config-icons-hidpi - APT configuration snippet to enable HiDPI icon 
downloads
 apt-config-icons-large - APT configuration snippet to enable large icon 
downloads
 apt-config-icons-large-hidpi - APT configuration snippet to enable large HiDPI 
icon downloads
 gir1.2-appstream-1.0 - Library to access AppStream services (introspection 
data)
 libappstream-dev - Library to access AppStream services (development files)
 libappstream4 - Library to access AppStream services
 libappstreamqt-dev - Qt5 library to access AppStream services (development 
files)
 libappstreamqt2 - Qt5 library to access AppStream services
Closes: 868018 906538
Changes:
 appstream (0.12.2-2) unstable; urgency=medium
 .
   * Use HTTPS version of homepage URL
   * cache-explicit-variants.patch: Set explicit variant types when
 generating the cache, for cases were we may not be able to
 infer them automatically (Closes: #906538)
   * apt-ignore-exit-status.patch: Don't return failure on metadata issues,
 only print a warning and exit normally (Closes: #868018)
Checksums-Sha1:
 7cbbc7bbbe4d924313efb8de732a3e80682e1b38 2878 appstream_0.12.2-2.dsc
 32ed01139a115ac778fa53876a41ffd83adb5b8a 12416 appstream_0.12.2-2.debian.tar.xz
 7253603b4ac8cd28288577238f25f8f3e7e735f4 57564 

Bug#906544: marked as done (apt: appstreamcli error while run apt)

[Debian Bug Tracking System]

Your message dated Sun, 19 Aug 2018 15:04:27 +
with message-id 
and subject line Bug#906538: fixed in appstream 0.12.2-2
has caused the Debian Bug report #906538,
regarding apt: appstreamcli error while run apt
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.)


-- 
906538: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906538
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apt
Version: 1.6.3
Severity: normal

Dear Maintainer,

I use this comand:aptitude update;aptitude -rf full-upgrade;aptitude -rf 
install;aptitude -rf autoclean;apt-get -f --install-suggests autoremove

Since yesterday i receive this message:

[getting other files...]
Atingiu https://desktop-download.mendeley.com/download/apt stable InRelease 
99% [Trabalhando]   
(appstreamcli:30801): GLib-CRITICAL **: 06:18:44.004: g_variant_builder_end: 
assertion '!GVSB(builder)->uniform_item_types || GVSB(builder)->prev_item_type 
!= NULL || g_variant_type_is_definite (GVSB(builder)->type)' failed

(appstreamcli:30801): GLib-CRITICAL **: 06:18:44.004: g_variant_new_variant: 
assertion 'value != NULL' failed

(appstreamcli:30801): GLib-ERROR **: 06:18:44.004: g_variant_new_parsed: 
11-13:invalid GVariant format string
Trace/breakpoint trap
E: Problem executing scripts APT::Update::Post-Invoke-Success 'if /usr/bin/test 
-w /var/cache/app-info -a -e /usr/bin/appstreamcli; then appstreamcli 
refresh-cache > /dev/null; fi'
E: Sub-process returned an error code

---

It shows if exist updates, but i don't now these are correct.

-- Package-specific info:

-- apt-config dump --

APT "";
APT::Architecture "amd64";
APT::Build-Essential "";
APT::Build-Essential:: "build-essential";
APT::Install-Recommends "1";
APT::Install-Suggests "0";
APT::Sandbox "";
APT::Sandbox::User "_apt";
APT::Authentication "";
APT::Authentication::TrustCDROM "true";
APT::NeverAutoRemove "";
APT::NeverAutoRemove:: "^firmware-linux.*";
APT::NeverAutoRemove:: "^linux-firmware$";
APT::NeverAutoRemove:: "^linux-image-4\.17\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-image-4\.17\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-headers-4\.17\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-headers-4\.17\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-image-extra-4\.17\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-image-extra-4\.17\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-modules-4\.17\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-modules-4\.17\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-modules-extra-4\.17\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-modules-extra-4\.17\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-signed-image-4\.17\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-signed-image-4\.17\.0-2-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-image-4\.17\.0-1-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-image-4\.17\.0-2-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-headers-4\.17\.0-1-amd64$";
APT::NeverAutoRemove:: "^kfreebsd-headers-4\.17\.0-2-amd64$";
APT::NeverAutoRemove:: "^gnumach-image-4\.17\.0-1-amd64$";
APT::NeverAutoRemove:: "^gnumach-image-4\.17\.0-2-amd64$";
APT::NeverAutoRemove:: "^.*-modules-4\.17\.0-1-amd64$";
APT::NeverAutoRemove:: "^.*-modules-4\.17\.0-2-amd64$";
APT::NeverAutoRemove:: "^.*-kernel-4\.17\.0-1-amd64$";
APT::NeverAutoRemove:: "^.*-kernel-4\.17\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-backports-modules-.*-4\.17\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-backports-modules-.*-4\.17\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-modules-.*-4\.17\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-modules-.*-4\.17\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-tools-4\.17\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-tools-4\.17\.0-2-amd64$";
APT::NeverAutoRemove:: "^linux-cloud-tools-4\.17\.0-1-amd64$";
APT::NeverAutoRemove:: "^linux-cloud-tools-4\.17\.0-2-amd64$";
APT::VersionedKernelPackages "";
APT::VersionedKernelPackages:: "linux-image";
APT::VersionedKernelPackages:: "linux-headers";
APT::VersionedKernelPackages:: "linux-image-extra";
APT::VersionedKernelPackages:: "linux-modules";
APT::VersionedKernelPackages:: "linux-modules-extra";
APT::VersionedKernelPackages:: "linux-signed-image";
APT::VersionedKernelPackages:: "kfreebsd-image";
APT::VersionedKernelPackages:: "kfreebsd-headers";
APT::VersionedKernelPackages:: "gnumach-image";
APT::VersionedKernelPackages:: ".*-modules";
APT::VersionedKernelPackages:: ".*-kernel";
APT::VersionedKernelPackages:: "linux-backports-modules-.*";
APT::VersionedKernelPackages:: "linux-modules-.*";
APT::VersionedKernelPackages:: "linux-tools";
APT::VersionedKernelPackages:: "linux-cloud-tools";

Processed: your mail

[Debian Bug Tracking System]

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

> forcemerge 906538 906648
Bug #906538 [appstream] appstream: apt-get update fails due to appstream crash
Bug #906544 [appstream] apt: appstreamcli error while run apt
Bug #906648 [appstream] apt-get update crash
Set Bug forwarded-to-address to 
'https://github.com/ximion/appstream/issues/198'.
Severity set to 'critical' from 'important'
Added indication that 906648 affects apt
Marked as found in versions appstream/0.12.2-1.
Bug #906544 [appstream] apt: appstreamcli error while run apt
Merged 906538 906544 906648
>
End of message, stopping processing here.

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

Bug#842815: Help needed for change of build system to gradle of package libsis-jhdf5-java

[Bernd Rinn]

On 08/19/2018 04:02 PM, olivier sallou wrote:
> 
> 
> Le dim. 19 août 2018 à 15:23, Bernd Rinn  > a écrit :
> 
> Hi Andreas,
> 
> I have no idea why the classes are missing for you as they are all
> present in our ivy-repository which we use for dependency resolution.
> Maybe there is an issue with your gradle build environment?
> 
> 
> In debian, all deps must be availlable as debian packages, they are not
> downloaded from remote repos.
> So i think 'problem' is those dependencies are not packaged in debian
>  They should be packaged first, then added as package build dependencies.

The old build procedure involved Ivy with a publicly accessible ivy
repository, the new build procedure is self-contained. Putting this into
Debian packages in a form compliant with Debian policies is your task at
Debian.

Bernd

> Anyway, I have now simplified the build process by removing automatic
> dependency resolution via ivy altogether. Can you please check whether
> the build works for you now when you use the build procedure on HEAD?
> 
> All the best,
> Bernd
> 
> On 08/16/2018 06:46 AM, Andreas Tille wrote:
> > Hi Bernd,
> >
> > could you give some hints about the missing classes?
> >
> > On Tue, Aug 14, 2018 at 12:23:22PM +0200, olivier sallou wrote:
> >> Le mar. 14 août 2018 à 11:32, Andreas Tille  > a écrit :
> >>
> >>> A problem occurred evaluating root project 'libsis-jhdf5-java'.
>  Could not resolve all dependencies for configuration ':runtime'.
> >>>    > Could not resolve cisd:cisd-args4j:+.
> >>>      Required by:
> >>>          project :
> >>>       > No cached version listing for cisd:cisd-args4j:+
> available for
> >>> offline mode.
> >>>    > Could not resolve cisd:cisd-base:+.
> >>>      Required by:
> >>>          project :
> >>>       > No cached version listing for cisd:cisd-base:+ available for
> >>> offline mode.
> >>>    > Could not resolve rinn:restrictions:+.
> >>>      Required by:
> >>>          project :
> >>>       > No cached version listing for rinn:restrictions:+
> available for
> >>> offline mode.
> >>>
> >>>
> >> I do not see in build deps things related to:
> >>    cisd:cisd-args4, cisd:cisd-base, rinn:restrictions
> >
> > I have no idea what these are. :-(
> >
> > Kind regards
> >
> >       Andreas.
> >
> >>> [1] https://salsa.debian.org/med-team/libsis-jhdf5-java



smime.p7s
Description: S/MIME Cryptographic Signature

Processed: found 906230 in 4.10.1-dfsg1-1

[Debian Bug Tracking System]

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

> found 906230 4.10.1-dfsg1-1
Bug #906230 [insighttoolkit4-python] insighttoolkit4-python: missing python 
dependencies
Marked as found in versions insighttoolkit4/4.10.1-dfsg1-1.
> thanks
Stopping processing here.

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

Processed: forcibly merging 897820 906645

[Debian Bug Tracking System]

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

> forcemerge 897820 906645
Bug #897820 {Done: Gert Wollny } [src:insighttoolkit4] 
nifti2dicom: ftbfs with GCC-8
Bug #897899 {Done: Gert Wollny } [src:insighttoolkit4] FTBFS 
with GCC 8 (error "Dunno about this gcc")
Bug #906645 [src:insighttoolkit4] FTBFS due to "Dunno about this gcc"
897741 was blocked by: 897899 897820
897741 was not blocking any bugs.
Added blocking bug(s) of 897741: 906645
897830 was blocked by: 897820 897756 897899 897775
897830 was not blocking any bugs.
Added blocking bug(s) of 897830: 906645
Marked Bug as done
Added indication that 906645 affects 
src:otb,src:itksnap,src:nifti2dicom,src:fw4spl
Marked as fixed in versions insighttoolkit4/4.12.2-dfsg1-2.
The source insighttoolkit4 and version 4.13.0-dfsg1 do not appear to match any 
binary packages
Marked as found in versions insighttoolkit4/4.12.2-dfsg1-1.
Added tag(s) patch, sid, and buster.
Bug #897820 {Done: Gert Wollny } [src:insighttoolkit4] 
nifti2dicom: ftbfs with GCC-8
The source insighttoolkit4 and version 4.13.0-dfsg1 do not appear to match any 
binary packages
Marked as found in versions insighttoolkit4/4.13.0-dfsg1.
Marked as found in versions insighttoolkit4/4.13.0-dfsg1.
Bug #897899 {Done: Gert Wollny } [src:insighttoolkit4] FTBFS 
with GCC 8 (error "Dunno about this gcc")
Merged 897820 897899 906645
> thanks
Stopping processing here.

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

Bug#842815: Help needed for change of build system to gradle of package libsis-jhdf5-java

[olivier sallou]

Le dim. 19 août 2018 à 15:23, Bernd Rinn  a écrit :

> Hi Andreas,
>
> I have no idea why the classes are missing for you as they are all
> present in our ivy-repository which we use for dependency resolution.
> Maybe there is an issue with your gradle build environment?
>

In debian, all deps must be availlable as debian packages, they are not
downloaded from remote repos.
So i think 'problem' is those dependencies are not packaged in debian
 They should be packaged first, then added as package build dependencies.

Olivier




> Anyway, I have now simplified the build process by removing automatic
> dependency resolution via ivy altogether. Can you please check whether
> the build works for you now when you use the build procedure on HEAD?
>
> All the best,
> Bernd
>
> On 08/16/2018 06:46 AM, Andreas Tille wrote:
> > Hi Bernd,
> >
> > could you give some hints about the missing classes?
> >
> > On Tue, Aug 14, 2018 at 12:23:22PM +0200, olivier sallou wrote:
> >> Le mar. 14 août 2018 à 11:32, Andreas Tille  a écrit
> :
> >>
> >>> A problem occurred evaluating root project 'libsis-jhdf5-java'.
>  Could not resolve all dependencies for configuration ':runtime'.
> >>>> Could not resolve cisd:cisd-args4j:+.
> >>>  Required by:
> >>>  project :
> >>>   > No cached version listing for cisd:cisd-args4j:+ available for
> >>> offline mode.
> >>>> Could not resolve cisd:cisd-base:+.
> >>>  Required by:
> >>>  project :
> >>>   > No cached version listing for cisd:cisd-base:+ available for
> >>> offline mode.
> >>>> Could not resolve rinn:restrictions:+.
> >>>  Required by:
> >>>  project :
> >>>   > No cached version listing for rinn:restrictions:+ available for
> >>> offline mode.
> >>>
> >>>
> >> I do not see in build deps things related to:
> >>cisd:cisd-args4, cisd:cisd-base, rinn:restrictions
> >
> > I have no idea what these are. :-(
> >
> > Kind regards
> >
> >   Andreas.
> >
> >>> [1] https://salsa.debian.org/med-team/libsis-jhdf5-java
>
>

Bug#899652: marked as done (php-solr: Invalid maintainer address pkg-php-p...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Sun, 19 Aug 2018 13:53:10 +
with message-id 
and subject line Bug#899652: fixed in php-solr 2.4.0-6
has caused the Debian Bug report #899652,
regarding php-solr: Invalid maintainer address 
pkg-php-p...@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.)


-- 
899652: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899652
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:php-solr
Version: 2.4.0-5
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of php-solr,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package php-solr since the list address
pkg-php-p...@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-php-p...@lists.alioth.debian.org is 35.

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: php-solr
Source-Version: 2.4.0-6

We believe that the bug you reported is fixed in the latest version of
php-solr, 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.
Ondřej Surý  (supplier of updated php-solr package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 19 Aug 2018 13:31:38 +
Source: php-solr
Binary: php-solr
Architecture: source
Version: 2.4.0-6
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PECL Maintainers 
Changed-By: Ondřej Surý 
Description:
 php-solr   - PHP extension for communicating with Apache Solr server
Closes: 899652
Changes:
 php-solr (2.4.0-6) unstable; urgency=medium
 .
   * Update Vcs-* to salsa.d.o
   * Update maintainer email to team+php-p...@tracker.debian.org
 (Closes: #899652)
Checksums-Sha1:
 dc106251a75d257c05dc50004ce118727419dc16 2132 php-solr_2.4.0-6.dsc
 c0ff96f83924250c66cfc17f2ce858d4c654849b 5740 php-solr_2.4.0-6.debian.tar.xz
 54ad4aa34aa366c498de9bb4b4c7dbaf62990ec7 8550 php-solr_2.4.0-6_amd64.buildinfo
Checksums-Sha256:
 bf89ddeb24ca14ecc4cf5bd67922b122bc4c5bc2accba0877502aa11dff4b43a 2132 
php-solr_2.4.0-6.dsc
 b9d877839b04197e746602c38875fdba02f9ca06b24029ae9e3213b4b39d 5740 
php-solr_2.4.0-6.debian.tar.xz
 c4dcc2695c8cff61ef938a59efe8f90358bd8879b48d8684d2c4d96e14701225 8550 
php-solr_2.4.0-6_amd64.buildinfo
Files:
 fabe223c30ea80a83b49f70f37d79f23 2132 php optional php-solr_2.4.0-6.dsc
 99d63cfa3256b6a85ea2548ef0bde28c 5740 php optional 
php-solr_2.4.0-6.debian.tar.xz
 d7c578796856868a60cc06c77b905d5c 8550 php optional 

Bug#899650: marked as done (php-ssh2: Invalid maintainer address pkg-php-p...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Sun, 19 Aug 2018 13:53:16 +
with message-id 
and subject line Bug#899650: fixed in php-ssh2 1.1.2+0.13-2
has caused the Debian Bug report #899650,
regarding php-ssh2: Invalid maintainer address 
pkg-php-p...@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.)


-- 
899650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899650
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:php-ssh2
Version: 1.1.2+0.13-1
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of php-ssh2,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package php-ssh2 since the list address
pkg-php-p...@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-php-p...@lists.alioth.debian.org is 35.

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: php-ssh2
Source-Version: 1.1.2+0.13-2

We believe that the bug you reported is fixed in the latest version of
php-ssh2, 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.
Ondřej Surý  (supplier of updated php-ssh2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 19 Aug 2018 13:29:51 +
Source: php-ssh2
Binary: php-ssh2
Architecture: source
Version: 1.1.2+0.13-2
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PECL Maintainers 
Changed-By: Ondřej Surý 
Description:
 php-ssh2   - Bindings for the libssh2 library
Closes: 899650
Changes:
 php-ssh2 (1.1.2+0.13-2) unstable; urgency=medium
 .
   * Update Vcs-* to salsa.d.o
   * Update maintainer email to team+php-p...@tracker.debian.org
 (Closes: #899650)
Checksums-Sha1:
 e1297206c4f60b9cb4fa763bffeb96cf82053c07 2183 php-ssh2_1.1.2+0.13-2.dsc
 741509dde71543d80f6c36d761471c7184d97dd2 4772 
php-ssh2_1.1.2+0.13-2.debian.tar.xz
 568334c483920b04646489278012fdd5821e4190 7011 
php-ssh2_1.1.2+0.13-2_amd64.buildinfo
Checksums-Sha256:
 e172a342c99e4da90e70691e6b1c7031b27548997d315aab017bbc28b88972a2 2183 
php-ssh2_1.1.2+0.13-2.dsc
 6f0199f4eaa9f1b00e382ea2d5bb702ea6c43b47f184d17dc8df796129057f67 4772 
php-ssh2_1.1.2+0.13-2.debian.tar.xz
 aaebf9251129bb6d28695ada8bcb98fb8fc9935e5c581345588f3e3fbc9c974a 7011 
php-ssh2_1.1.2+0.13-2_amd64.buildinfo
Files:
 abec9d1e01851ba30e881dd045911c2c 2183 php extra php-ssh2_1.1.2+0.13-2.dsc
 a58c40dc009f3b8e6c68e066d733b4de 4772 php extra 
php-ssh2_1.1.2+0.13-2.debian.tar.xz
 13df7a44d236c969a6eae28415babf34 

Processed: tagging 906514

[Debian Bug Tracking System]

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

> tags 906514 + buster sid
Bug #906514 [src:xfce4-taskmanager] xfce4-taskmanager: FTBFS in buster/sid (cp: 
cannot create regular file 'm4/intltool.m4': No such file or directory)
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Bug#906623: heimdal: FTBFS in buster/sid (hcrypto/engine.h: No such file or directory)

[Santiago Vila]

On Sun, Aug 19, 2018 at 03:51:43PM +0300, Adrian Bunk wrote:

> > Most probably, it also fails here in reproducible builds:
> > 
> > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/heimdal.html
> > 
> > where you can get a full build log if you need it.
> >...
> 
> That is unrelated, the failure in reproducible builds is a frequent test 
> failure - looks like some test is flaky in this environment.

You are right, the failure in reproducible builds is different.
(That's why I usually say "most probably" in the email template).

> I am not able to reproduce your FTBFS.

However, I can reproduce this failure every time, in both buster and sid,
and both with and without eatmydata.

This issue started happening recently, this is my build history:

Status: successful  heimdal_7.5.0+dfsg-2_amd64-20180709T180925Z
Status: successful  heimdal_7.5.0+dfsg-2_amd64-20180723T160612Z
Status: successful  heimdal_7.5.0+dfsg-2_amd64-20180731T163511Z
Status: successful  heimdal_7.5.0+dfsg-2_amd64-20180808T164724Z
Status: failed  heimdal_7.5.0+dfsg-2_amd64-20180818T13Z
Status: failed  heimdal_7.5.0+dfsg-2_amd64-20180819T125609Z
Status: failed  heimdal_7.5.0+dfsg-2_amd64-20180819T125611Z
Status: failed  heimdal_7.5.0+dfsg-2_amd64-20180819T125636Z
Status: failed  heimdal_7.5.0+dfsg-2_amd64-20180819T125810Z
Status: failed  heimdal_7.5.0+dfsg-2_amd64-20180819T131146Z
Status: failed  heimdal_7.5.0+dfsg-2_amd64-20180819T131211Z
Status: failed  heimdal_7.5.0+dfsg-2_amd64-20180819T131544Z
Status: failed  heimdal_7.5.0+dfsg-2_amd64-20180819T131534Z

Apparently something happened in buster between 2018-08-08 and
2018-08-18 for this to happen.

My build environment is described here:

https://people.debian.org/~sanvila/my-building-environment.txt

If you are brave enough, I could setup a virtual machine for you
to reproduce it (contact me privately for details).

Thanks.

Processed: tagging 906644

[Debian Bug Tracking System]

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

> tags 906644 + upstream
Bug #906644 [conkeror] conkeror: not compatible with firefox >= 57
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Bug#906667: fraqtive FTBFS on armel/armhf: error: conflicting declaration 'typedef ptrdiff_t GLsizeiptr'

[Adrian Bunk]

Source: fraqtive
Version: 0.4.8-7
Severity: serious
Tags: ftbfs

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

...
In file included from /usr/include/GL/gl.h:2055,
 from /usr/include/GL/glu.h:38,
 from meshview.cpp:27:
/usr/include/GL/glext.h:468:19: error: conflicting declaration 'typedef 
ptrdiff_t GLsizeiptr'
 typedef ptrdiff_t GLsizeiptr;
   ^~
In file included from /usr/include/arm-linux-gnueabihf/qt5/QtGui/qopengl.h:105,
 from /usr/include/arm-linux-gnueabihf/qt5/QtOpenGL/qgl.h:45,
 from /usr/include/arm-linux-gnueabihf/qt5/QtOpenGL/QGLWidget:1,
 from meshview.h:22,
 from meshview.cpp:19:
/usr/include/GLES3/gl32.h:77:25: note: previous declaration as 'typedef 
khronos_ssize_t GLsizeiptr'
 typedef khronos_ssize_t GLsizeiptr;
 ^~
In file included from /usr/include/GL/gl.h:2055,
 from /usr/include/GL/glu.h:38,
 from meshview.cpp:27:
/usr/include/GL/glext.h:469:19: error: conflicting declaration 'typedef 
ptrdiff_t GLintptr'
 typedef ptrdiff_t GLintptr;
   ^~~~
In file included from /usr/include/arm-linux-gnueabihf/qt5/QtGui/qopengl.h:105,
 from /usr/include/arm-linux-gnueabihf/qt5/QtOpenGL/qgl.h:45,
 from /usr/include/arm-linux-gnueabihf/qt5/QtOpenGL/QGLWidget:1,
 from meshview.h:22,
 from meshview.cpp:19:
/usr/include/GLES3/gl32.h:78:26: note: previous declaration as 'typedef 
khronos_intptr_t GLintptr'
 typedef khronos_intptr_t GLintptr;
  ^~~~
make[2]: *** [Makefile:1381: ../tmp/debug/meshview.o] Error 1


The root cause is that on armel/armhf (and arm64 in Ubuntu)
Qt5 is compiled with OpenGL ES instead of OpenGL.

Ideally it should be fixed to build and work with OpenGL ES,
but if this is not easily possible please
- change the build dependency from libqt5opengl5-dev
  to libqt5opengl5-desktop-dev (which will stop trying
  to build it on armel/armhf), and
- file a removal bug for the old armel+armhf binaries
  against ftp.debian.org

Bug#842815: Help needed for change of build system to gradle of package libsis-jhdf5-java

[Bernd Rinn]

Hi Andreas,

I have no idea why the classes are missing for you as they are all
present in our ivy-repository which we use for dependency resolution.
Maybe there is an issue with your gradle build environment?

Anyway, I have now simplified the build process by removing automatic
dependency resolution via ivy altogether. Can you please check whether
the build works for you now when you use the build procedure on HEAD?

All the best,
Bernd

On 08/16/2018 06:46 AM, Andreas Tille wrote:
> Hi Bernd,
> 
> could you give some hints about the missing classes?
> 
> On Tue, Aug 14, 2018 at 12:23:22PM +0200, olivier sallou wrote:
>> Le mar. 14 août 2018 à 11:32, Andreas Tille  a écrit :
>>
>>> A problem occurred evaluating root project 'libsis-jhdf5-java'.
 Could not resolve all dependencies for configuration ':runtime'.
>>>> Could not resolve cisd:cisd-args4j:+.
>>>  Required by:
>>>  project :
>>>   > No cached version listing for cisd:cisd-args4j:+ available for
>>> offline mode.
>>>> Could not resolve cisd:cisd-base:+.
>>>  Required by:
>>>  project :
>>>   > No cached version listing for cisd:cisd-base:+ available for
>>> offline mode.
>>>> Could not resolve rinn:restrictions:+.
>>>  Required by:
>>>  project :
>>>   > No cached version listing for rinn:restrictions:+ available for
>>> offline mode.
>>>
>>>
>> I do not see in build deps things related to:
>>cisd:cisd-args4, cisd:cisd-base, rinn:restrictions
> 
> I have no idea what these are. :-(
> 
> Kind regards
> 
>   Andreas.
> 
>>> [1] https://salsa.debian.org/med-team/libsis-jhdf5-java



smime.p7s
Description: S/MIME Cryptographic Signature

Bug#899939: marked as done (php-msgpack: Invalid maintainer address pkg-php-p...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Sun, 19 Aug 2018 13:19:55 +
with message-id 
and subject line Bug#899939: fixed in php-msgpack 2.0.2+0.5.7-5
has caused the Debian Bug report #899939,
regarding php-msgpack: Invalid maintainer address 
pkg-php-p...@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.)


-- 
899939: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899939
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:php-msgpack
Version: 2.0.2+0.5.7-2
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of php-msgpack,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package php-msgpack since the list address
pkg-php-p...@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-php-p...@lists.alioth.debian.org is 35.

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: php-msgpack
Source-Version: 2.0.2+0.5.7-5

We believe that the bug you reported is fixed in the latest version of
php-msgpack, 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.
Ondřej Surý  (supplier of updated php-msgpack package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 19 Aug 2018 12:51:57 +
Source: php-msgpack
Binary: php-msgpack
Architecture: source
Version: 2.0.2+0.5.7-5
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PECL Maintainers 
Changed-By: Ondřej Surý 
Description:
 php-msgpack - PHP extension for interfacing with MessagePack
Closes: 899939
Changes:
 php-msgpack (2.0.2+0.5.7-5) unstable; urgency=medium
 .
   * Update maintainer email to team+php-p...@tracker.debian.org
 (Closes: #899939)
Checksums-Sha1:
 976a506ecdbba4ac1707f7c85930c5254b3c55c7 2138 php-msgpack_2.0.2+0.5.7-5.dsc
 a74a187151653f91adfd0506fb1aecb963e805d2 4588 
php-msgpack_2.0.2+0.5.7-5.debian.tar.xz
 ee9e8bd150746ce44e6b336542faf20794d28d38 6949 
php-msgpack_2.0.2+0.5.7-5_amd64.buildinfo
Checksums-Sha256:
 953376d7ffab445015247f75211275dbc45dd235c3378fb4aff4e646d20922a4 2138 
php-msgpack_2.0.2+0.5.7-5.dsc
 8c97ff1ac079cd9497ce9935574054128fb588c2781b43fc32a96f846e9d7510 4588 
php-msgpack_2.0.2+0.5.7-5.debian.tar.xz
 b7c16775c71602ba4b59eb4c7bd989a8131d80f260509377fd606a5202bbe8c1 6949 
php-msgpack_2.0.2+0.5.7-5_amd64.buildinfo
Files:
 15d4a353d9779a6840bf0298ae0011dd 2138 php optional 
php-msgpack_2.0.2+0.5.7-5.dsc
 03f326183e49d9b7336dcc91b20ead37 4588 php optional 

Bug#906666: openms FTBFS on armel/armhf: error: expected class-name before '{' token

[Adrian Bunk]

Source: openms
Version: 2.4.0-1
Severity: serious
Tags: ftbfs
Forwarded: https://github.com/OpenMS/OpenMS/issues/3687

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

...
In file included from 
/<>/src/openms_gui/source/VISUAL/APPLICATIONS/TOPPViewBase.cpp:89:
/<>/src/openms_gui/include/OpenMS/VISUAL/Spectrum3DOpenGLCanvas.h:61:3:
 error: expected class-name before '{' token
   {
   ^
make[4]: *** [src/openms_gui/CMakeFiles/OpenMS_GUI.dir/build.make:108: 
src/openms_gui/CMakeFiles/OpenMS_GUI.dir/source/VISUAL/APPLICATIONS/TOPPViewBase.cpp.o]
 Error 1


The root cause is that on armel/armhf (and arm64 in Ubuntu)
Qt5 is compiled with OpenGL ES instead of OpenGL.

Ideally it should be fixed to build and work with OpenGL ES,
but if this is not easily possible please
- change the build dependency from libqt5opengl5-dev
  to libqt5opengl5-desktop-dev (which will stop trying
  to build mldemos on armel/armhf), and
- file a removal bug for the old armel+armhf binaries
  against ftp.debian.org

Processed: tagging 906655

[Debian Bug Tracking System]

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

> tags 906655 + buster sid
Bug #906655 [src:ruby-minitest-around] ruby-minitest-around: FTBFS in 
buster/sid (failing tests)
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Processed: tagging 906654

[Debian Bug Tracking System]

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

> tags 906654 + buster sid
Bug #906654 [src:ruby-default-value-for] ruby-default-value-for: FTBFS in 
buster/sid (failing tests)
Added tag(s) buster and sid.
> thanks
Stopping processing here.

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

Processed: tagging 906656

[Debian Bug Tracking System]

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

> tags 906656 + buster sid
Bug #906656 [src:ruby-openid-connect] ruby-openid-connect: FTBFS in buster/sid 
(failing tests)
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Processed: giac FTBFS: FAIL: chk_fhan11

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 1.4.9.69+dfsg1-1~exp2
Bug #906665 [src:giac] giac FTBFS: FAIL: chk_fhan11
Marked as fixed in versions giac/1.4.9.69+dfsg1-1~exp2.
> close -1
Bug #906665 [src:giac] giac FTBFS: FAIL: chk_fhan11
Marked Bug as done

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

Bug#906665: giac FTBFS: FAIL: chk_fhan11

[Adrian Bunk]

Source: giac
Version: 1.2.3.57+dfsg1-2
Severity: serious
Tags: ftbfs
Control: fixed -1 1.4.9.69+dfsg1-1~exp2
Control: close -1

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

...
FAIL: chk_fhan11


// Using locale /usr/share/locale/
// C
// /usr/share/locale/
// giac
// UTF-8
// Maximum number of parallel threads 4
// Unable to find keyword file doc/en/keywords
Help file doc/en/aide_cas not found
Added 0 synonyms
Help file aide_cas not found
== restarted ===
// Time 0.01
// Time 0
// Time 0
// Time 0.22
// Time 0.11
// Time 0.12
// Time 0
// Time 0

Evaluation time: 0.64
// Time 0.64
// Time 0
// Time 0
// Time 0.01

Evaluation time: 6.51
// Time 6.51
// Time 0
// Time 0
// Time 0
// Time 0
// Time 0
// Time 0
// Time 0
// Time 0
// Time 0
// Time 0
// Time 0
// Time 0
// Time 0
// Time 0
// Time 0.02
// Time 0
// Time 0
// Time 0.01
ca fait bien p-1
// Time 0.01
// Time 0
// Time 0
// Time 0
// Time 0.01
// Time 0.01
// Time 0
// Time 0
// Time 0.01
// Time 0
// Time 0
// Time 0
// Time 0.01
// Time 0.01
// Time 0.03
// Time 0
// Time 0
// Time 0.08
// Time 0

Evaluation time: 0.57
// Time 0.57

Evaluation time: 0.7
// Time 0.71

Evaluation time: 0.7
// Time 0.7
// Time 0
// Time 0.21
// Time 0.14
// Time 0.14
// Time 0
// Time 0
// Time 0
// Time 0
// Time 0
// Time 0
// Time 0
// Time 0
// Time 0
// Time 0
// Time 0.01
// Time 0
// Time 0
// Time 0
// Total time 10.3
13c13
< 1,
---
> matrix[[2,7,1],[3,2,1],[389,2,1],[733,2,1],[156904374622257604823879982847602392900751802349981470895277241,2,matrix[[2,13,1],[3,3,1],[5,2,1],[7,2,1],[56467,2,1],[6553084925887974620811527,2,matrix[[2,5,1],[19,2,1],[71,2,1],[126823,2,1]],
FAIL chk_fhan11 (exit status: 1)


Testsuite summary for giac 1.2.3

# TOTAL: 30
# PASS:  29
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0


This seems to be already fixed in experimental:
https://tests.reproducible-builds.org/debian/rb-pkg/experimental/amd64/giac.html

Bug#906623: heimdal: FTBFS in buster/sid (hcrypto/engine.h: No such file or directory)

[Adrian Bunk]

On Sat, Aug 18, 2018 at 11:28:06PM +, Santiago Vila wrote:
>...
> make[3]: Entering directory '/<>/heimdal-7.5.0+dfsg/lib/hcrypto'
>   CC   test_rand.o
> In file included from test_rand.c:42:
> rand.h:46:10: fatal error: hcrypto/engine.h: No such file or directory
>  #include 
>   ^~
> compilation terminated.
> make[3]: *** [Makefile:2060: test_rand.o] Error 1
> make[3]: Leaving directory '/<>/heimdal-7.5.0+dfsg/lib/hcrypto'
> make[2]: *** [Makefile:565: all-recursive] Error 1
> make[2]: Leaving directory '/<>/heimdal-7.5.0+dfsg/lib'
> make[1]: *** [Makefile:613: all-recursive] Error 1
> make[1]: Leaving directory '/<>/heimdal-7.5.0+dfsg'
> dh_auto_build: make -j1 returned exit code 2
> make: *** [debian/rules:7: build-indep] Error 2
> dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
> status 2
> 
> 
> The build was made with "dpkg-buildpackage -A" in my autobuilder.
> Most probably, it also fails here in reproducible builds:
> 
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/heimdal.html
> 
> where you can get a full build log if you need it.
>...

That is unrelated, the failure in reproducible builds is a frequent test 
failure - looks like some test is flaky in this environment.

I am not able to reproduce your FTBFS.

cu
Adrian

-- 

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

Bug#899642: marked as done (php-igbinary: Invalid maintainer address pkg-php-p...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Sun, 19 Aug 2018 12:49:54 +
with message-id 
and subject line Bug#899642: fixed in php-igbinary 2.0.7-1
has caused the Debian Bug report #899642,
regarding php-igbinary: Invalid maintainer address 
pkg-php-p...@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.)


-- 
899642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899642
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:php-igbinary
Version: 2.0.5-1
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of php-igbinary,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package php-igbinary since the list address
pkg-php-p...@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-php-p...@lists.alioth.debian.org is 35.

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: php-igbinary
Source-Version: 2.0.7-1

We believe that the bug you reported is fixed in the latest version of
php-igbinary, 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.
Ondřej Surý  (supplier of updated php-igbinary package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 19 Aug 2018 12:22:29 +
Source: php-igbinary
Binary: php-igbinary
Architecture: source
Version: 2.0.7-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PECL Maintainers 
Changed-By: Ondřej Surý 
Description:
 php-igbinary - igbinary PHP serializer
Closes: 899642
Changes:
 php-igbinary (2.0.7-1) unstable; urgency=medium
 .
   * New upstream version 2.0.7
   * Update maintainer email to team+php-p...@tracker.debian.org
 (Closes: #899642)
Checksums-Sha1:
 047f9e01887dc249c7723c288d38f9e579b9246e 2118 php-igbinary_2.0.7-1.dsc
 04e5f317859fd4aec7452d80ec14fc3ba901f13b 73523 php-igbinary_2.0.7.orig.tar.gz
 b3a2df223a56ee0fa6ac239e183c28a5392858e8 4012 
php-igbinary_2.0.7-1.debian.tar.xz
 eff3ebaf69e2aad0eaaef6ff7e54b5ab9fd75b65 6929 
php-igbinary_2.0.7-1_amd64.buildinfo
Checksums-Sha256:
 c7f1d14ca92d039d130b7dca04bbecbce7962b9237b338fa64d03b2fa1532bdd 2118 
php-igbinary_2.0.7-1.dsc
 0cddce91bd0f3a57dfef08f5f99058a5be086878bc28aaa3be047bf10a10f801 73523 
php-igbinary_2.0.7.orig.tar.gz
 adcef6a54d109e27888ad5befd57d86a2c3aeb85a3bf81aa449e5c589604c23a 4012 
php-igbinary_2.0.7-1.debian.tar.xz
 003add0c902d5fc9b7a58bf6265eda8e4c62115cb00878fa03f01036bfb2d9e9 6929 
php-igbinary_2.0.7-1_amd64.buildinfo
Files:
 

Bug#906583: FTBFS: Fails to link testlib in src/plugins/backends/aqhbci/plugin

[Adrian Bunk]

On Sun, Aug 19, 2018 at 08:29:44AM +0200, Micha Lenk wrote:
> Hi Adrian,

Hi Micha,

> thank you for your feedback.
> 
> Am 19.08.2018 um 01:03 schrieb Adrian Bunk:
> > On Sun, Aug 19, 2018 at 12:17:51AM +0200, Micha Lenk wrote:
> >> ...
> >> --- a/src/plugins/backends/aqhbci/plugin/Makefile.am
> >> +++ b/src/plugins/backends/aqhbci/plugin/Makefile.am
> >> @@ -77,6 +77,7 @@ testlib_LDADD = \
> >>$(aqhbci_internal_libs) \
> >>$(aqbanking_internal_libs) \
> >>$(gwenhywfar_libs)
> >> +testlib_DEPENDENCIES = libaqhbci.la
> >> ...
> > 
> > A better fix would be s/$(aqhbci_internal_libs)/libaqhbci.la/
> 
> I would like to learn something. Why would using libaqhbci.la directly
> be better than using the $(aqhbci_internal_libs variable)?

configure.ac:
aqhbci_internal_libs="${abs_top_builddir}/src/plugins/backends/aqhbci/plugin/libaqhbci.la"

For libtool/automake this means "link with an already built library in 
another directory".

Dependencies between directories are handled through the order in SUBDIRS.

But when the library is built in the same directory, there are no 
dependencies "build the library first" created. This was always a
bug waiting to explode with parallel building, but in this case
automake 1.16 seems to trigger a reshuffle of the build order.

libaqhbci.la means "link with the library that has to be built first".

> Maybe there
> are some more places where some cleanup would be appropriate.

libaqhbciplugin_la_LIBADD already uses libaqhbci.la,
so that should be fine.

> Regards,
> Micha

cu
Adrian

-- 

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

Processed: tagging 906644

[Debian Bug Tracking System]

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

> tags 906644 + confirmed
Bug #906644 [conkeror] conkeror: not compatible with firefox >= 57
Added tag(s) confirmed.
> thanks
Stopping processing here.

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

Bug#862373: any update on the libyaml-libyaml-perl bug ?

[shirish शिरीष]

Dear all,

I was trying to install lintian when saw the above -

$ sudo aptitude install lintian -y
The following NEW packages will be installed:
  libyaml-libyaml-perl{a} lintian
0 packages upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/1,161 kB of archives. After unpacking 4,350 kB will be used.
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
grave bugs of libyaml-libyaml-perl (→ 0.72+repack-1) 
 b1 - #862373 - libyaml-libyaml-perl: Unconditionally instantiates
objects from yaml data
Summary:
 libyaml-libyaml-perl(1 bug)
Are you sure you want to install/upgrade the above packages? [Y/n/?/...] n
**
** Exiting with an error in order to stop the installation. **
**
E: Sub-process /usr/sbin/apt-listbugs apt returned an error code (10)
E: Failure running script /usr/sbin/apt-listbugs apt


I tried to see if another version is in experimental or something but
saw nothing -

$ apt-cache policy libyaml-libyaml-perl
libyaml-libyaml-perl:
  Installed: (none)
  Candidate: 0.72+repack-1
  Version table:
 0.72+repack-1 500
500 http://deb.debian.org/debian buster/main amd64 Packages
100 http://deb.debian.org/debian unstable/main amd64 Packages


Then tried to see if a transition slot  has been asked for but
couldn't  find anything at least  in the list -

https://release.debian.org/transitions/

AIUI , we use transitions to add breaks against old versions and
rebuild packages with new package versions etc.

Looking forward to know as and when this is resolved.

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

Bug#906274: marked as done (php-apcu broken. apcu_entry() hangs, crashing the php interpreter.)

[Debian Bug Tracking System]

Your message dated Sun, 19 Aug 2018 12:14:01 +
with message-id 
and subject line Bug#906274: fixed in php-apcu 5.1.12+4.0.11-1
has caused the Debian Bug report #906274,
regarding php-apcu broken. apcu_entry() hangs, crashing the php interpreter.
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.)


-- 
906274: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906274
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php-apcu
Version: 5.1.8+4.0.11-1
Severity: grave
Tags: patch fixed-upstream

I had originally reported this to ubuntu because we first noticed it on a 
machine running ubuntu, however, ubuntu doesnt seem to maintain this pkg so
therefore I am reporting this here.

After upgrading our testing server to bionic, our web application stopped
responding entirely after the second request. We traced this to a problem in 
php-apcu where it would block upon the second call to apcu_entry and completely
lock up the php processes causing the server to become unresponsive to any 
further requests.

This issue was already reported and fixed upstream (release 5.1.11) and I
have attached the diff for the corresponding commit, though I would like to
note that there have been 3 bugfix releases since the packaged version (5.1.9).

Upstream issue: https://github.com/krakjoe/apcu/issues/246

Affected systems: Anything running apcu with either php-fpm or apache with
  mod-php.


diff --git a/apc_cache.c b/apc_cache.c
index 3892c9e..8605525 100644
--- a/apc_cache.c
+++ b/apc_cache.c
@@ -1910,7 +1910,7 @@ PHP_APCU_API void apc_cache_entry(apc_cache_t *cache, zval *key, zend_fcall_info
 }
 			}
 		} else apc_cache_fetch_internal(cache, Z_STR_P(key), entry, now, _value);
-	}, apc_cache_entry_try_begin());
+	}, apc_cache_entry_try_end());
 }/*}}}*/
 #undef apc_cache_entry_try_begin
 #undef apc_cache_entry_try_end
--- End Message ---
--- Begin Message ---
Source: php-apcu
Source-Version: 5.1.12+4.0.11-1

We believe that the bug you reported is fixed in the latest version of
php-apcu, 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.
Ondřej Surý  (supplier of updated php-apcu package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 19 Aug 2018 11:50:51 +
Source: php-apcu
Binary: php-apcu
Architecture: source
Version: 5.1.12+4.0.11-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PECL Maintainers 
Changed-By: Ondřej Surý 
Description:
 php-apcu   - APC User Cache for PHP
Closes: 899947 906274
Changes:
 php-apcu (5.1.12+4.0.11-1) unstable; urgency=medium
 .
   * New upstream version 5.1.12+4.0.11 (Closes: #906274)
   * Update maintainer email to team+php-p...@tracker.debian.org
 (Closes: #899947)
Checksums-Sha1:
 47460aefcaca358b02d47f2039436718cde075e5 2165 php-apcu_5.1.12+4.0.11-1.dsc
 fb8d21c8d5186fa6502d8e73eb0bba269e6d38de 124464 
php-apcu_5.1.12+4.0.11.orig.tar.xz
 193f9460e7cd6eede533c9bab8e75cd1fbe90a0a 5384 
php-apcu_5.1.12+4.0.11-1.debian.tar.xz
 79e90fcf42c0bc6104b039f5b8594037d05b187e 6932 
php-apcu_5.1.12+4.0.11-1_amd64.buildinfo
Checksums-Sha256:
 d4bf598ccb58e4f97f054bc3eb27d4efae454beae3d5a22606fe8d6bd1f31a87 2165 
php-apcu_5.1.12+4.0.11-1.dsc
 1dc70cc5e407f782f5a26bdf570a192a7626f204016f9d194bf8f639cc1b299b 124464 
php-apcu_5.1.12+4.0.11.orig.tar.xz
 f2b880cb9ee4f3c6e80d3a9599b8385531c7d78defdcc3359cf30b0ddf3cf274 5384 
php-apcu_5.1.12+4.0.11-1.debian.tar.xz
 c7175bb9ee0fdd621b17b3368df9cd1b293946d5a96874cd484a4b171ea1fad2 6932 
php-apcu_5.1.12+4.0.11-1_amd64.buildinfo
Files:
 55f0cf4660f14d21d44f0ea39a46610f 2165 php optional php-apcu_5.1.12+4.0.11-1.dsc
 0bbb71ef645768128d50cfd8b7dbef4d 124464 php optional 
php-apcu_5.1.12+4.0.11.orig.tar.xz
 a72ca468d3d22dd0a2ee2b81807d6b91 5384 php optional 
php-apcu_5.1.12+4.0.11-1.debian.tar.xz
 208059200e22a3f920254051b0c41036 6932 php optional 
php-apcu_5.1.12+4.0.11-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEEw2Gx4wKVQ+vGJel9g3Kkd++uWcIFAlt5WztfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEMz

Bug#906660: kphotoalbum: FTBFS in buster/sid ('QString::QString(const char*)' is private within this context)

[Santiago Vila]

Package: src:kphotoalbum
Version: 5.3-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-arch
dh build-arch --parallel --with kf5
   dh_update_autotools_config -a -O--parallel
   dh_auto_configure --buildsystem=kf5 -a -O--parallel
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
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++

[... snipped ...]

   ^~
/<>/RemoteControl/RemoteConnection.cpp:108:52: error: 
'QString::QString(const char*)' is private within this context
<< ": Received " << qPrintable(id);
^~
In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:47,
 from /usr/include/x86_64-linux-gnu/qt5/QtCore/QObject:1,
 from /<>/RemoteControl/RemoteConnection.h:22,
 from /<>/RemoteControl/RemoteConnection.cpp:19:
/usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:829:5: note: declared 
private here
 QString(const char *ch);
 ^~~
In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/qnamespace.h:43,
 from /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs.h:48,
 from /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:46,
 from /usr/include/x86_64-linux-gnu/qt5/QtCore/QObject:1,
 from /<>/RemoteControl/RemoteConnection.h:22,
 from /<>/RemoteControl/RemoteConnection.cpp:19:
/<>/RemoteControl/RemoteConnection.cpp:108:63: error: invalid 
conversion from 'qint32' {aka 'int'} to 'const char*' [-fpermissive]
<< ": Received " << qPrintable(id);
   ^~
In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:47,
 from /usr/include/x86_64-linux-gnu/qt5/QtCore/QObject:1,
 from /<>/RemoteControl/RemoteConnection.h:22,
 from /<>/RemoteControl/RemoteConnection.cpp:19:
/usr/include/x86_64-linux-gnu/qt5/QtCore/qstring.h:829:25: note:   initializing 
argument 1 of 'QString::QString(const char*)'
 QString(const char *ch);
 ^~
In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/qnamespace.h:43,
 from /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs.h:48,
 from /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:46,
 from /usr/include/x86_64-linux-gnu/qt5/QtCore/QObject:1,
 from /<>/RemoteControl/RemoteConnection.h:22,
 from /<>/RemoteControl/RemoteConnection.cpp:19:
/<>/RemoteControl/RemoteConnection.cpp:108:52: error: conversion 
to non-const reference type 'class QString&&' from rvalue of type 'QString' 
[-fpermissive]
<< ": Received " << qPrintable(id);
^~
make[4]: *** [CMakeFiles/kphotoalbum.dir/build.make:2796: 
CMakeFiles/kphotoalbum.dir/RemoteControl/RemoteConnection.cpp.o] Error 1
make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make[3]: *** [CMakeFiles/Makefile2:1183: CMakeFiles/kphotoalbum.dir/all] Error 2
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make[2]: *** [Makefile:144: all] Error 2
make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu'
dh_auto_build: cd obj-x86_64-linux-gnu && make -j1 returned exit code 2
make[1]: *** [debian/rules:11: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:6: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


The build was made with "dpkg-buildpackage -B" in my autobuilder.
Most probably, it also fails here in reproducible builds:

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

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the 

Bug#906661: openrpt: FTBFS in buster/sid (no type named 'Object' in 'struct QtPrivate::FunctionPointer')

[Santiago Vila]

Package: src:openrpt
Version: 3.3.14-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-arch
dh build-arch --builddirectory=. --parallel
   dh_update_autotools_config -a -O--builddirectory=. -O--parallel
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
lrelease */*/*.ts */*.ts
Updating 'OpenRPT/renderapp/renderapp_ar.qm'...
Generated 0 translation(s) (0 finished and 0 unfinished)
Ignored 64 untranslated source text(s)
Updating 'OpenRPT/renderapp/renderapp_es.qm'...
Generated 61 translation(s) (56 finished and 5 unfinished)
Ignored 3 untranslated source text(s)
Updating 'OpenRPT/renderapp/renderapp_fr.qm'...
Generated 63 translation(s) (58 finished and 5 unfinished)

[... snipped ...]

reportparameter.cpp:39:88:   required from here
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:228:43: error: no type named 
'Object' in 'struct QtPrivate::FunctionPointer'
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:260:13: note: candidate: 
'template static typename 
std::enable_if<((int)(QtPrivate::FunctionPointer::ArgumentCount) >= 0), 
QMetaObject::Connection>::type QObject::connect(const typename 
QtPrivate::FunctionPointer::Object*, Func1, Func2)'
 connect(const typename QtPrivate::FunctionPointer::Object 
*sender, Func1 signal, Func2 slot)
 ^~~
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:260:13: note:   template 
argument deduction/substitution failed:
reportparameter.cpp:39:88: note:   candidate expects 3 arguments, 4 provided
 connect(buttonGroup, SIGNAL(buttonClicked(int)), _stack, 
SLOT(setCurrentIndex(int)));

^
In file included from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qwidget.h:45,
 from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qdialog.h:44,
 from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QDialog:1,
 from reportparameter.h:24,
 from reportparameter.cpp:21:
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:269:13: note: candidate: 
'template static typename 
std::enable_if<(((int)(QtPrivate::FunctionPointer::ArgumentCount) >= 0) 
&& (! QtPrivate::FunctionPointer::IsPointerToMemberFunction)), 
QMetaObject::Connection>::type QObject::connect(const typename 
QtPrivate::FunctionPointer::Object*, Func1, const QObject*, Func2, 
Qt::ConnectionType)'
 connect(const typename QtPrivate::FunctionPointer::Object 
*sender, Func1 signal, const QObject *context, Func2 slot,
 ^~~
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:269:13: note:   template 
argument deduction/substitution failed:
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h: In substitution of 
'template static typename 
std::enable_if<(((int)(QtPrivate::FunctionPointer::ArgumentCount) >= 0) 
&& (! QtPrivate::FunctionPointer::IsPointerToMemberFunction)), 
QMetaObject::Connection>::type QObject::connect(const typename 
QtPrivate::FunctionPointer::Object*, Func1, const QObject*, Func2, 
Qt::ConnectionType) [with Func1 = const char*; Func2 = const char*]':
reportparameter.cpp:39:88:   required from here
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:269:13: error: no type named 
'type' in 'struct std::enable_if'
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:300:13: note: candidate: 
'template static typename 
std::enable_if<(QtPrivate::FunctionPointer::ArgumentCount == -1), 
QMetaObject::Connection>::type QObject::connect(const typename 
QtPrivate::FunctionPointer::Object*, Func1, Func2)'
 connect(const typename QtPrivate::FunctionPointer::Object 
*sender, Func1 signal, Func2 slot)
 ^~~
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:300:13: note:   template 
argument deduction/substitution failed:
reportparameter.cpp:39:88: note:   candidate expects 3 arguments, 4 provided
 connect(buttonGroup, SIGNAL(buttonClicked(int)), _stack, 
SLOT(setCurrentIndex(int)));

^
In file included from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qwidget.h:45,
 from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qdialog.h:44,
 from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QDialog:1,
 from reportparameter.h:24,
 from reportparameter.cpp:21:
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:308:13: note: candidate: 
'template static typename 
std::enable_if<(QtPrivate::FunctionPointer::ArgumentCount == -1), 
QMetaObject::Connection>::type QObject::connect(const typename 
QtPrivate::FunctionPointer::Object*, Func1, const QObject*, Func2, 
Qt::ConnectionType)'
 connect(const typename QtPrivate::FunctionPointer::Object 
*sender, 

Bug#906659: keepassxc: FTBFS in buster/sid (invalid use of incomplete type ‘class QButtonGroup’)

[Santiago Vila]

Package: src:keepassxc
Version: 2.3.1+dfsg.1-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-arch
dh build-arch --parallel
   dh_update_autotools_config -a -O--parallel
   dh_autoreconf -a -O--parallel
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>/keepassxc-2.3.1+dfsg.1'
if [ -e src/zxcvbn/ ]; then rm -r src/zxcvbn/ ; fi
dh_auto_configure --  -DWITH_TESTS=ON \
  -DWITH_GUI_TESTS=ON \
  -DWITH_XC_ALL=ON
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" -DWITH_TESTS=ON 
-DWITH_GUI_TESTS=ON -DWITH_XC_ALL=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

[... snipped ...]

[ 39%] Building CXX object 
src/CMakeFiles/keepassx_core.dir/gui/entry/AutoTypeAssociationsModel.cpp.o
cd /<>/keepassxc-2.3.1+dfsg.1/obj-x86_64-linux-gnu/src && 
/usr/bin/c++  -DKEEPASSX_BUILDING_CORE -DQHTTP_EXPORT -DQHTTP_MEMORY_LOG=0 
-DQT_CONCURRENT_LIB -DQT_CORE_LIB -DQT_DBUS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB 
-DQT_NO_CAST_TO_ASCII -DQT_NO_DEBUG -DQT_NO_EXCEPTIONS -DQT_STRICT_ITERATORS 
-DQT_WIDGETS_LIB -DWITH_APP_BUNDLE 
-I/<>/keepassxc-2.3.1+dfsg.1/obj-x86_64-linux-gnu/src/keepassx_core_autogen/include
 -I/usr/include/x86_64-linux-gnu -I/<>/keepassxc-2.3.1+dfsg.1/src 
-I/<>/keepassxc-2.3.1+dfsg.1/obj-x86_64-linux-gnu/src -isystem 
/usr/include/ykpers-1 -isystem /usr/include/x86_64-linux-gnu/qt5 -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/QtWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtConcurrent -isystem 
/usr/include/x86_64-linux-gnu/q
 t5/QtDBus  -g -O2 -fdebug-prefix-map=/<>/keepassxc-2.3.1+dfsg.1=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fno-common -Wall -Wextra -Wundef -Wpointer-arith 
-Wno-long-long -Wformat=2 -Wmissing-format-attribute -fvisibility=hidden 
-fvisibility-inlines-hidden -fstack-protector-strong -fno-exceptions -fno-rtti 
-Wnon-virtual-dtor -Wold-style-cast -Woverloaded-virtual 
-Werror=format-security -Wcast-align -pie -fPIE -std=c++11   -fPIC -std=gnu++11 
-o CMakeFiles/keepassx_core.dir/gui/entry/AutoTypeAssociationsModel.cpp.o -c 
/<>/keepassxc-2.3.1+dfsg.1/src/gui/entry/AutoTypeAssociationsModel.cpp
[ 40%] Building CXX object 
src/CMakeFiles/keepassx_core.dir/gui/entry/AutoTypeMatchModel.cpp.o
cd /<>/keepassxc-2.3.1+dfsg.1/obj-x86_64-linux-gnu/src && 
/usr/bin/c++  -DKEEPASSX_BUILDING_CORE -DQHTTP_EXPORT -DQHTTP_MEMORY_LOG=0 
-DQT_CONCURRENT_LIB -DQT_CORE_LIB -DQT_DBUS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB 
-DQT_NO_CAST_TO_ASCII -DQT_NO_DEBUG -DQT_NO_EXCEPTIONS -DQT_STRICT_ITERATORS 
-DQT_WIDGETS_LIB -DWITH_APP_BUNDLE 
-I/<>/keepassxc-2.3.1+dfsg.1/obj-x86_64-linux-gnu/src/keepassx_core_autogen/include
 -I/usr/include/x86_64-linux-gnu -I/<>/keepassxc-2.3.1+dfsg.1/src 
-I/<>/keepassxc-2.3.1+dfsg.1/obj-x86_64-linux-gnu/src -isystem 
/usr/include/ykpers-1 -isystem /usr/include/x86_64-linux-gnu/qt5 -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/QtWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtConcurrent -isystem 
/usr/include/x86_64-linux-gnu/q
 t5/QtDBus  -g -O2 -fdebug-prefix-map=/<>/keepassxc-2.3.1+dfsg.1=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fno-common -Wall -Wextra -Wundef -Wpointer-arith 
-Wno-long-long -Wformat=2 -Wmissing-format-attribute -fvisibility=hidden 
-fvisibility-inlines-hidden -fstack-protector-strong -fno-exceptions -fno-rtti 
-Wnon-virtual-dtor -Wold-style-cast -Woverloaded-virtual 
-Werror=format-security -Wcast-align -pie -fPIE -std=c++11   -fPIC -std=gnu++11 
-o CMakeFiles/keepassx_core.dir/gui/entry/AutoTypeMatchModel.cpp.o -c 
/<>/keepassxc-2.3.1+dfsg.1/src/gui/entry/AutoTypeMatchModel.cpp
[ 40%] Building CXX object 
src/CMakeFiles/keepassx_core.dir/gui/entry/AutoTypeMatchView.cpp.o
cd /<>/keepassxc-2.3.1+dfsg.1/obj-x86_64-linux-gnu/src && 
/usr/bin/c++  -DKEEPASSX_BUILDING_CORE -DQHTTP_EXPORT -DQHTTP_MEMORY_LOG=0 
-DQT_CONCURRENT_LIB -DQT_CORE_LIB -DQT_DBUS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB 
-DQT_NO_CAST_TO_ASCII -DQT_NO_DEBUG -DQT_NO_EXCEPTIONS -DQT_STRICT_ITERATORS 
-DQT_WIDGETS_LIB 

Bug#906655: ruby-minitest-around: FTBFS in buster/sid (failing tests)

[Santiago Vila]

Package: src:ruby-minitest-around
Version: 0.3.2-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --buildsystem=ruby --with ruby
dh: Compatibility levels before 9 are deprecated (level 7 in use)
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_auto_configure: Compatibility levels before 9 are deprecated (level 7 in use)
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_auto_build: Compatibility levels before 9 are deprecated (level 7 in use)
dh_ruby --build
   dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_auto_test: Compatibility levels before 9 are deprecated (level 7 in use)
dh_ruby --test

[... snipped ...]

install -D -m644 /<>/lib/minitest/around/unit.rb 
/<>/debian/ruby-minitest-around/usr/lib/ruby/vendor_ruby/minitest/around/unit.rb
install -D -m644 /<>/lib/minitest/around/version.rb 
/<>/debian/ruby-minitest-around/usr/lib/ruby/vendor_ruby/minitest/around/version.rb
install -D -m644 /<>/lib/minitest/around.rb 
/<>/debian/ruby-minitest-around/usr/lib/ruby/vendor_ruby/minitest/around.rb

┌──────────────────────────────────────────────────────────────────────────────┐
│ Install Rubygems integration metadata   
 │
└──────────────────────────────────────────────────────────────────────────────┘

generating gemspec at 
/<>/debian/ruby-minitest-around/usr/share/rubygems-integration/all/specifications/minitest-around-0.3.2.gemspec
/usr/bin/ruby2.5 /usr/bin/gem2deb-test-runner

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

RUBYLIB=/<>/debian/ruby-minitest-around/usr/lib/ruby/vendor_ruby:. 
GEM_PATH=debian/ruby-minitest-around/usr/share/rubygems-integration/all:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 -S rake -f debian/ruby-tests.rake
/usr/bin/ruby2.5 -w -I"test"  
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/around_spec.rb" 
"test/around_test.rb" "test/nested_spec.rb" "test/nested_test.rb" -v
/<>/debian/ruby-minitest-around/usr/lib/ruby/vendor_ruby/minitest/around/spec.rb:27:
 warning: method redefined; discarding old before
/usr/lib/ruby/vendor_ruby/minitest/spec.rb:180: warning: previous definition of 
before was here
/<>/debian/ruby-minitest-around/usr/lib/ruby/vendor_ruby/minitest/around/spec.rb:31:
 warning: method redefined; discarding old after
/usr/lib/ruby/vendor_ruby/minitest/spec.rb:194: warning: previous definition of 
after was here
Run options: -v --seed 39915

# Running:

Minitest Around::nested fun::more nesting fun#test_0001_orders = 
/usr/lib/ruby/vendor_ruby/minitest.rb:961:in `run_one_method': Minitest 
Around::nested fun::more nesting fun#run _must_ return a Result (RuntimeError)
from /usr/lib/ruby/vendor_ruby/minitest.rb:334:in `run_one_method'
from /usr/lib/ruby/vendor_ruby/minitest.rb:321:in `block (2 levels) in 
run'
from /usr/lib/ruby/vendor_ruby/minitest.rb:320:in `each'
from /usr/lib/ruby/vendor_ruby/minitest.rb:320:in `block in run'
from /usr/lib/ruby/vendor_ruby/minitest.rb:360:in `on_signal'
from /usr/lib/ruby/vendor_ruby/minitest.rb:347:in `with_info_handler'
from /usr/lib/ruby/vendor_ruby/minitest.rb:319:in `run'
from /usr/lib/ruby/vendor_ruby/minitest.rb:159:in `block in __run'
from /usr/lib/ruby/vendor_ruby/minitest.rb:159:in `map'
from /usr/lib/ruby/vendor_ruby/minitest.rb:159:in `__run'
from /usr/lib/ruby/vendor_ruby/minitest.rb:136:in `run'
from /usr/lib/ruby/vendor_ruby/minitest.rb:63:in `block in autorun'
rake aborted!
Command failed with status (1): [ruby -w -I"test"  
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/around_spec.rb" 
"test/around_test.rb" "test/nested_spec.rb" "test/nested_test.rb" -v]

Tasks: TOP => default
(See full trace by running task with --trace)
ERROR: Test 

Bug#906654: ruby-default-value-for: FTBFS in buster/sid (failing tests)

[Santiago Vila]

Package: src:ruby-default-value-for
Version: 3.0.1-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --buildsystem=ruby --with ruby
dh: Compatibility levels before 9 are deprecated (level 7 in use)
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_auto_configure: Compatibility levels before 9 are deprecated (level 7 in use)
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_auto_build: Compatibility levels before 9 are deprecated (level 7 in use)
dh_ruby --build
   dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_auto_test: Compatibility levels before 9 are deprecated (level 7 in use)
dh_ruby --test

[... snipped ...]


install -d 
/<>/debian/ruby-default-value-for/usr/lib/ruby/vendor_ruby
install -D -m644 /<>/lib/default_value_for/railtie.rb 
/<>/debian/ruby-default-value-for/usr/lib/ruby/vendor_ruby/default_value_for/railtie.rb
install -D -m644 /<>/lib/default_value_for.rb 
/<>/debian/ruby-default-value-for/usr/lib/ruby/vendor_ruby/default_value_for.rb

┌──────────────────────────────────────────────────────────────────────────────┐
│ Install Rubygems integration metadata   
 │
└──────────────────────────────────────────────────────────────────────────────┘

generating gemspec at 
/<>/debian/ruby-default-value-for/usr/share/rubygems-integration/all/specifications/default_value_for-3.0.1.gemspec
/usr/bin/ruby2.5 /usr/bin/gem2deb-test-runner

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

RUBYLIB=/<>/debian/ruby-default-value-for/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-default-value-for/usr/share/rubygems-integration/all:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 -S rake -f debian/ruby-tests.rake
/usr/bin/ruby2.5 test.rb
/usr/lib/ruby/vendor_ruby/minitest.rb:961:in `run_one_method': 
DefaultValuePluginTest#run _must_ return a Result (RuntimeError)
from /usr/lib/ruby/vendor_ruby/minitest.rb:334:in `run_one_method'
from /usr/lib/ruby/vendor_ruby/minitest.rb:321:in `block (2 levels) in 
run'
from /usr/lib/ruby/vendor_ruby/minitest.rb:320:in `each'
from /usr/lib/ruby/vendor_ruby/minitest.rb:320:in `block in run'
from /usr/lib/ruby/vendor_ruby/minitest.rb:360:in `on_signal'
from /usr/lib/ruby/vendor_ruby/minitest.rb:347:in `with_info_handler'
from /usr/lib/ruby/vendor_ruby/minitest.rb:319:in `run'
from /usr/lib/ruby/vendor_ruby/minitest.rb:159:in `block in __run'
from /usr/lib/ruby/vendor_ruby/minitest.rb:159:in `map'
from /usr/lib/ruby/vendor_ruby/minitest.rb:159:in `__run'
from /usr/lib/ruby/vendor_ruby/minitest.rb:136:in `run'
from /usr/lib/ruby/vendor_ruby/minitest.rb:63:in `block in autorun'

Testing with Active Record version 4.2.10

Run options: --seed 61094

# Running:

rake aborted!
Command failed with status (1): [/usr/bin/ruby2.5 test.rb...]
/<>/debian/ruby-tests.rake:5:in `block in '
Tasks: TOP => default => test
(See full trace by running task with --trace)
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install 
/<>/debian/ruby-default-value-for returned exit code 1
make: *** [debian/rules:15: binary-indep] Error 1
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


The build was made with "dpkg-buildpackage -A" in my autobuilder.
Most probably, it also fails here in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-default-value-for.html

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.

Bug#906656: ruby-openid-connect: FTBFS in buster/sid (failing tests)

[Santiago Vila]

Package: src:ruby-openid-connect
Version: 0.12.0-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   dh_auto_build -i -O--buildsystem=ruby
dh_ruby --build
   dh_ruby --build
   dh_auto_test -i -O--buildsystem=ruby
dh_ruby --test
 fakeroot debian/rules binary-indep
dh binary-indep --buildsystem=ruby --with ruby
   dh_testroot -i -O--buildsystem=ruby
   dh_prep -i -O--buildsystem=ruby

[... snipped ...]

 # ./lib/openid_connect/response_object/id_token.rb:51:in 
`left_half_hash_of'
 # ./lib/openid_connect/response_object/id_token.rb:39:in `to_jwt'
 # ./spec/openid_connect/response_object/id_token_spec.rb:155:in `block (5 
levels) in '

  2) OpenIDConnect::ResponseObject::IdToken#to_jwt when access_token is given 
when access_token is a String it should behave like id_token_with_at_hash 
should include at_hash
 Failure/Error: UrlSafeBase64.encode64 digest[0, hash_length / (2 * 8)]

 NameError:
   uninitialized constant 
OpenIDConnect::ResponseObject::IdToken::UrlSafeBase64
 Shared Example Group: :id_token_with_at_hash called from 
./spec/openid_connect/response_object/id_token_spec.rb:172
 # ./lib/openid_connect/response_object/id_token.rb:51:in 
`left_half_hash_of'
 # ./lib/openid_connect/response_object/id_token.rb:39:in `to_jwt'
 # ./spec/openid_connect/response_object/id_token_spec.rb:155:in `block (5 
levels) in '

  3) OpenIDConnect::ResponseObject::IdToken#to_jwt when code is given should 
include at_hash
 Failure/Error: UrlSafeBase64.encode64 digest[0, hash_length / (2 * 8)]

 NameError:
   uninitialized constant 
OpenIDConnect::ResponseObject::IdToken::UrlSafeBase64
 # ./lib/openid_connect/response_object/id_token.rb:51:in 
`left_half_hash_of'
 # ./lib/openid_connect/response_object/id_token.rb:42:in `to_jwt'
 # ./spec/openid_connect/response_object/id_token_spec.rb:179:in `block (4 
levels) in '

  4) OpenIDConnect::ResponseObject::IdToken#to_jwt when both access_token and 
code are given should include at_hash
 Failure/Error: UrlSafeBase64.encode64 digest[0, hash_length / (2 * 8)]

 NameError:
   uninitialized constant 
OpenIDConnect::ResponseObject::IdToken::UrlSafeBase64
 # ./lib/openid_connect/response_object/id_token.rb:51:in 
`left_half_hash_of'
 # ./lib/openid_connect/response_object/id_token.rb:39:in `to_jwt'
 # ./spec/openid_connect/response_object/id_token_spec.rb:195:in `block (4 
levels) in '

Finished in 4.47 seconds (files took 0.93138 seconds to load)
217 examples, 4 failures, 2 pending

Failed examples:

rspec './spec/openid_connect/response_object/id_token_spec.rb[1:3:3:1:1:1]' # 
OpenIDConnect::ResponseObject::IdToken#to_jwt when access_token is given when 
access_token is a Rack::OAuth2::AccessToken it should behave like 
id_token_with_at_hash should include at_hash
rspec './spec/openid_connect/response_object/id_token_spec.rb[1:3:3:2:1:1]' # 
OpenIDConnect::ResponseObject::IdToken#to_jwt when access_token is given when 
access_token is a String it should behave like id_token_with_at_hash should 
include at_hash
rspec ./spec/openid_connect/response_object/id_token_spec.rb:178 # 
OpenIDConnect::ResponseObject::IdToken#to_jwt when code is given should include 
at_hash
rspec ./spec/openid_connect/response_object/id_token_spec.rb:194 # 
OpenIDConnect::ResponseObject::IdToken#to_jwt when both access_token and code 
are given should include at_hash

/usr/bin/ruby2.5 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
documentation failed
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install /<>/debian/ruby-openid-connect 
returned exit code 1
make: *** [debian/rules:7: binary-indep] Error 1
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


The build was made with "dpkg-buildpackage -A" in my autobuilder.
Most probably, it also fails here in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-openid-connect.html

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.

Bug#906657: twinkle: FTBFS in buster/sid (expected type-specifier before 'QRegExpValidator')

[Santiago Vila]

Package: src:twinkle
Version: 1:1.10.1+dfsg-3
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>/twinkle-1.10.1+dfsg'
dh_auto_configure -- -DWITH_QT5=ON -DWITH_ZRTP=OFF -DWITH_SPEEX=ON 
-DWITH_GSM=ON -DWITH_ALSA=ON
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" -DWITH_QT5=ON 
-DWITH_ZRTP=OFF -DWITH_SPEEX=ON -DWITH_GSM=ON -DWITH_ALSA=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 ...]

[ 88%] Building CXX object src/gui/CMakeFiles/twinkle.dir/syssettingsform.cpp.o
cd /<>/twinkle-1.10.1+dfsg/obj-x86_64-linux-gnu/src/gui && 
/usr/bin/c++  -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG 
-DQT_QML_LIB -DQT_QUICK_LIB -DQT_WIDGETS_LIB 
-I/<>/twinkle-1.10.1+dfsg/obj-x86_64-linux-gnu/src/gui/twinkle_autogen/include
 -I/usr/include/libxml2 
-I/<>/twinkle-1.10.1+dfsg/obj-x86_64-linux-gnu 
-I/<>/twinkle-1.10.1+dfsg/src 
-I/<>/twinkle-1.10.1+dfsg/obj-x86_64-linux-gnu/src/gui 
-I/<>/twinkle-1.10.1+dfsg/src/gui -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/QtQuick -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtQml -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtNetwork  -g -O2 
-fdebug-prefix-map=/<>/twinkle-1.10.1+dfsg=. -fstack-protector-strong 
-
 Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11 
-fPIC -std=gnu++11 -o CMakeFiles/twinkle.dir/syssettingsform.cpp.o -c 
/<>/twinkle-1.10.1+dfsg/src/gui/syssettingsform.cpp
[ 88%] Building CXX object src/gui/CMakeFiles/twinkle.dir/historyform.cpp.o
cd /<>/twinkle-1.10.1+dfsg/obj-x86_64-linux-gnu/src/gui && 
/usr/bin/c++  -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG 
-DQT_QML_LIB -DQT_QUICK_LIB -DQT_WIDGETS_LIB 
-I/<>/twinkle-1.10.1+dfsg/obj-x86_64-linux-gnu/src/gui/twinkle_autogen/include
 -I/usr/include/libxml2 
-I/<>/twinkle-1.10.1+dfsg/obj-x86_64-linux-gnu 
-I/<>/twinkle-1.10.1+dfsg/src 
-I/<>/twinkle-1.10.1+dfsg/obj-x86_64-linux-gnu/src/gui 
-I/<>/twinkle-1.10.1+dfsg/src/gui -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/QtQuick -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtQml -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtNetwork  -g -O2 
-fdebug-prefix-map=/<>/twinkle-1.10.1+dfsg=. -fstack-protector-strong 
-
 Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11 
-fPIC -std=gnu++11 -o CMakeFiles/twinkle.dir/historyform.cpp.o -c 
/<>/twinkle-1.10.1+dfsg/src/gui/historyform.cpp
[ 89%] Building CXX object src/gui/CMakeFiles/twinkle.dir/selectuserform.cpp.o
cd /<>/twinkle-1.10.1+dfsg/obj-x86_64-linux-gnu/src/gui && 
/usr/bin/c++  -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG 
-DQT_QML_LIB -DQT_QUICK_LIB -DQT_WIDGETS_LIB 
-I/<>/twinkle-1.10.1+dfsg/obj-x86_64-linux-gnu/src/gui/twinkle_autogen/include
 -I/usr/include/libxml2 
-I/<>/twinkle-1.10.1+dfsg/obj-x86_64-linux-gnu 
-I/<>/twinkle-1.10.1+dfsg/src 
-I/<>/twinkle-1.10.1+dfsg/obj-x86_64-linux-gnu/src/gui 
-I/<>/twinkle-1.10.1+dfsg/src/gui -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/QtQuick -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtQml -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtNetwork  -g -O2 
-fdebug-prefix-map=/<>/twinkle-1.10.1+dfsg=. -fstack-protector-strong 
-
 Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11 
-fPIC -std=gnu++11 -o CMakeFiles/twinkle.dir/selectuserform.cpp.o -c 
/<>/twinkle-1.10.1+dfsg/src/gui/selectuserform.cpp
[ 89%] Building CXX object 
src/gui/CMakeFiles/twinkle.dir/selectprofileform.cpp.o
cd 

Bug#906653: libkf5ksieve: FTBFS in buster/sid ('class QFontMetrics' has no member named 'width')

[Santiago Vila]

Package: src:libkf5ksieve
Version: 4:17.12.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 -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-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 ...]

   ^
/<>/src/ksieveui/vacation/legacy/vacationutils.cpp:72:41: warning: 
'SpamDataExtractor' is deprecated [-Wdeprecated-declarations]
 KSieveUi::Legacy::SpamDataExtractor sdx;
 ^~~
In file included from 
/<>/src/ksieveui/vacation/legacy/vacationutils.cpp:25:
/<>/src/ksieveui/vacation/legacy/vacationscriptextractor.h:83:27: 
note: declared here
 class KSIEVEUI_DEPRECATED SpamDataExtractor : public 
GenericInformationExtractor
   ^
/<>/src/ksieveui/vacation/legacy/vacationutils.cpp:73:54: warning: 
'DomainRestrictionDataExtractor' is deprecated [-Wdeprecated-declarations]
 KSieveUi::Legacy::DomainRestrictionDataExtractor drdx;
  ^~~~
In file included from 
/<>/src/ksieveui/vacation/legacy/vacationutils.cpp:25:
/<>/src/ksieveui/vacation/legacy/vacationscriptextractor.h:145:27: 
note: declared here
 class KSIEVEUI_DEPRECATED DomainRestrictionDataExtractor : public 
GenericInformationExtractor
   ^~
/<>/src/ksieveui/vacation/legacy/vacationutils.cpp:74:37: warning: 
'DateExtractor' is deprecated [-Wdeprecated-declarations]
 KSieveUi::Legacy::DateExtractor dtx;
 ^~~
In file included from 
/<>/src/ksieveui/vacation/legacy/vacationutils.cpp:25:
/<>/src/ksieveui/vacation/legacy/vacationscriptextractor.h:209:27: 
note: declared here
 class KSIEVEUI_DEPRECATED DateExtractor : public GenericInformationExtractor
   ^
[ 16%] Building CXX object 
src/ksieveui/CMakeFiles/KF5KSieveUi.dir/vacation/legacy/vacationscriptextractor.cpp.o
cd /<>/obj-x86_64-linux-gnu/src/ksieveui && /usr/bin/c++  
-DBUILD_TESTING -DKCOREADDONS_LIB -DKF5KSieveUi_EXPORTS -DQT_CONCURRENT_LIB 
-DQT_CORE_LIB -DQT_DBUS_LIB -DQT_DISABLE_DEPRECATED_BEFORE=0x06 
-DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_CAST_FROM_ASCII 
-DQT_NO_CAST_FROM_BYTEARRAY -DQT_NO_CAST_TO_ASCII -DQT_NO_DEBUG 
-DQT_NO_NARROWING_CONVERSIONS_IN_CONNECT -DQT_NO_SIGNALS_SLOTS_KEYWORDS 
-DQT_NO_URL_CAST_FROM_STRING -DQT_POSITIONING_LIB -DQT_PRINTSUPPORT_LIB 
-DQT_QML_LIB -DQT_QUICK_LIB -DQT_USE_FAST_CONCATENATION 
-DQT_USE_FAST_OPERATOR_PLUS -DQT_USE_QSTRINGBUILDER -DQT_WEBCHANNEL_LIB 
-DQT_WEBENGINECORE_LIB -DQT_WEBENGINEWIDGETS_LIB -DQT_WIDGETS_LIB -DQT_XML_LIB 
-DTRANSLATION_DOMAIN=\"libksieve\" -D_GNU_SOURCE -D_LARGEFILE64_SOURCE 
-I/<>/obj-x86_64-linux-gnu/src/ksieveui 
-I/<>/src/ksieveui 
-I/<>/obj-x86_64-linux-gnu/src/ksieveui/KF5KSieveUi_autogen/include
 -I/<>/src/ksieveui/util -I/<>/src/kmanagesieve -I/<
 >/obj-x86_64-linux-gnu/src/kmanagesieve -I/<>/src 
-I/<>/obj-x86_64-linux-gnu/src -I/<>/src/parser 
-isystem /usr/include/KF5/PimCommon -isystem /usr/include/KF5/pimcommon 
-isystem /usr/include/KF5 -isystem /usr/include/x86_64-linux-gnu/qt5 -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 
/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem 
/usr/include/KF5/KIOCore -isystem /usr/include/KF5/KCoreAddons -isystem 
/usr/include/KF5/KService -isystem /usr/include/KF5/KConfigCore -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtConcurrent -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtDBus -isystem 
/usr/include/KF5/KConfigWidgets -isystem /usr/include/KF5/KCodecs -isystem 
/usr/include/KF5/KWidgetsAddons -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem /usr/include/KF5/KConfigGui 
-isystem /usr/include/x86_64-linux-gnu/q
 t5/QtXml -isystem /usr/include/KF5/KAuth -isystem 

Bug#906651: cantor: FTBFS in buster/sid (invalid use of incomplete type 'class QStyle')

[Santiago Vila]

Package: src:cantor
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 ...]

make -f src/assistants/solve/CMakeFiles/cantor_solveassistant.dir/build.make 
src/assistants/solve/CMakeFiles/cantor_solveassistant.dir/depend
make[4]: Entering directory '/<>/obj-x86_64-linux-gnu'
[ 82%] Generating ui_solvedlg.h
cd /<>/obj-x86_64-linux-gnu/src/assistants/solve && /usr/bin/cmake 
-DKDE_UIC_EXECUTABLE:FILEPATH=/usr/lib/qt5/bin/uic 
-DKDE_UIC_FILE:FILEPATH=/<>/src/assistants/solve/solvedlg.ui 
-DKDE_UIC_H_FILE:FILEPATH=/<>/obj-x86_64-linux-gnu/src/assistants/solve/ui_solvedlg.h
 -DKDE_UIC_BASENAME:STRING=solvedlg -P 
/usr/lib/x86_64-linux-gnu/cmake/KF5I18n/kf5i18nuic.cmake
cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends 
"Unix Makefiles" /<> /<>/src/assistants/solve 
/<>/obj-x86_64-linux-gnu 
/<>/obj-x86_64-linux-gnu/src/assistants/solve 
/<>/obj-x86_64-linux-gnu/src/assistants/solve/CMakeFiles/cantor_solveassistant.dir/DependInfo.cmake
 --color=
Scanning dependencies of target cantor_solveassistant
make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make -f src/assistants/solve/CMakeFiles/cantor_solveassistant.dir/build.make 
src/assistants/solve/CMakeFiles/cantor_solveassistant.dir/build
make[4]: Entering directory '/<>/obj-x86_64-linux-gnu'
[ 82%] Building CXX object 
src/assistants/solve/CMakeFiles/cantor_solveassistant.dir/solveassistant.cpp.o
cd /<>/obj-x86_64-linux-gnu/src/assistants/solve && /usr/bin/c++  
-DKCOREADDONS_LIB -DMAKE_CANTORLIBS_LIB -DQT_CONCURRENT_LIB -DQT_CORE_LIB 
-DQT_DBUS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_CAST_FROM_ASCII 
-DQT_NO_CAST_FROM_BYTEARRAY -DQT_NO_CAST_TO_ASCII -DQT_NO_DEBUG 
-DQT_NO_SIGNALS_SLOTS_KEYWORDS -DQT_NO_URL_CAST_FROM_STRING 
-DQT_USE_FAST_CONCATENATION -DQT_USE_FAST_OPERATOR_PLUS -DQT_USE_QSTRINGBUILDER 
-DQT_WIDGETS_LIB -DQT_XML_LIB -D_GNU_SOURCE -D_LARGEFILE64_SOURCE 
-Dcantor_solveassistant_EXPORTS 
-I/<>/obj-x86_64-linux-gnu/src/assistants/solve 
-I/<>/src/assistants/solve 
-I/<>/obj-x86_64-linux-gnu/src/assistants/solve/cantor_solveassistant_autogen/include
 -I/<>/src/lib -I/<>/obj-x86_64-linux-gnu/src/lib 
-I/<>/src/lib/test -I/usr/include/libspectre -isystem 
/usr/include/KF5/KCompletion -isystem /usr/include/KF5 -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/KF5/KIconThemes -isystem /usr/include/KF5/KIOCore -isystem 
/usr/include/KF5/KCoreAddons -isystem /usr/include/KF5/KService -isystem 
/usr/include/KF5/KConfigCore -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtConcurrent -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtDBus -isystem 
/usr/include/KF5/KIOFileWidgets -isystem /usr/include/KF5/KIOWidgets -isystem 
/usr/include/KF5/KJobWidgets -isystem /usr/include/KF5/KWidgetsAddons -isystem 
/usr/include/KF5/KBookmarks -isystem /usr/include/x86_64-linux-gnu/qt5/QtXml 
-isystem /usr/include/KF5/KItemViews -isystem /usr/include/KF5/KXmlGui -isystem 
/usr/include/KF5/KConfigWidgets -isystem /usr/include/KF5/KCodecs -isystem 
/usr/include/KF5/KConfigGui -isystem /usr/include/KF5/KAuth -isystem 
/usr/include/K
 F5/Solid -isystem /usr/include/KF5/KArchive -isystem /usr/include/KF5/KI18n  
-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 -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 
-std=c++0x -fno-operator-names -Wall -Wextra 

Bug#906652: hgsubversion: FTBFS in buster/sid ('module' object has no attribute 'ignore')

[Santiago Vila]

Package: src:hgsubversion
Version: 1.8.7+1517-b3e41b0d50a2-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with python2
   dh_update_autotools_config -i
   dh_auto_configure -i
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>/hgsubversion-1.8.7+1517-b3e41b0d50a2'
#Disable the testsuite.  It's broken in 1.8.3
make[1]: Leaving directory '/<>/hgsubversion-1.8.7+1517-b3e41b0d50a2'
 fakeroot debian/rules binary-indep
dh binary-indep --with python2
   dh_testroot -i
   dh_prep -i
   debian/rules override_dh_auto_install
make[1]: Entering directory '/<>/hgsubversion-1.8.7+1517-b3e41b0d50a2'
python setup.py install --root 
/<>/hgsubversion-1.8.7+1517-b3e41b0d50a2/debian/hgsubversion 
--install-layout=deb
Traceback (most recent call last):
  File "setup.py", line 106, in 
from hgsubversion.svnwrap import svn_swig_wrapper
  File 
"/<>/hgsubversion-1.8.7+1517-b3e41b0d50a2/hgsubversion/__init__.py", 
line 37, in 
demandimport.ignore.extend([
AttributeError: 'module' object has no attribute 'ignore'
make[1]: *** [debian/rules:15: override_dh_auto_install] Error 1
make[1]: Leaving directory '/<>/hgsubversion-1.8.7+1517-b3e41b0d50a2'
make: *** [debian/rules:7: binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


The build was made with "dpkg-buildpackage -A" in my autobuilder.
Most probably, it also fails here in reproducible builds:

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

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.

Bug#906562: marked as done (samba-dsdb-modules not installable)

[Debian Bug Tracking System]

Your message dated Sun, 19 Aug 2018 10:36:16 +
with message-id 
and subject line Bug#906562: fixed in samba 2:4.8.4+dfsg-2
has caused the Debian Bug report #906562,
regarding samba-dsdb-modules not installable
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.)


-- 
906562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906562
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: samba
Version: 2:4.8.4+dfsg-1
Severity: grave
Justification: renders package unusable

# apt install samba-dsdb-modules
Reading package lists... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
samba-dsdb-modules : Depends: libldb1 (< 2:1.3.6~) but 2:1.4.0+really1.3.5-2 is 
to be installed
E: Unable to correct problems, you have held broken packages.

-- Package-specific info:
* /etc/samba/smb.conf present, and attached
* /var/lib/samba/dhcp.conf not present

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

Kernel: Linux 4.14.60-toy-lxtec-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), 
LANGUAGE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages samba depends on:
ii  adduser   3.117
ii  dpkg  1.19.0.5+b1
ii  libattr1  1:2.4.47-2+b2
ii  libbsd0   0.9.1-1
ii  libc6 2.27-5
ii  libldb1   2:1.4.0+really1.3.5-2
ii  libpam-modules1.1.8-3.8
ii  libpam-runtime1.1.8-3.8
ii  libpopt0  1.16-11
ii  libpython2.7  2.7.15-3
ii  libtalloc22.1.14-1
ii  libtdb1   1.3.15-4
ii  libtevent00.9.36-2
ii  lsb-base  9.20170808
ii  procps2:3.3.15-2
ii  python2.7.15-3
ii  python-dnspython  1.15.0-1
ii  python-samba  2:4.8.4+dfsg-1
ii  python2.7 2.7.15-3
ii  samba-common  2:4.8.4+dfsg-1
ii  samba-common-bin  2:4.8.4+dfsg-1
ii  samba-libs2:4.8.4+dfsg-1
ii  tdb-tools 1.3.15-4

Versions of packages samba recommends:
ii  attr1:2.4.47-2+b2
ii  logrotate   3.11.0-0.1
pn  samba-dsdb-modules  
ii  samba-vfs-modules   2:4.8.4+dfsg-1

Versions of packages samba suggests:
ii  bind9  1:9.11.4+dfsg-4
ii  bind9utils 1:9.11.4+dfsg-4
pn  ctdb   
ii  ldb-tools  2:1.4.0+really1.3.5-2
ii  ntp1:4.2.8p12+dfsg-1
ii  smbldap-tools  0.9.9-1
pn  ufw
ii  winbind2:4.8.4+dfsg-1

-- no debconf information
# Global parameters
[global]
workgroup = LXTEC
realm = HOME.LXTEC.NET
netbios name = TOY
server role = active directory domain controller
#server role = standalone server
server services = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, drepl, 
winbind, ntp_signd, kcc, dnsupdate
#server services = s3fs, rpc, nbt, wrepl, kdc, drepl, winbind, 
ntp_signd, kcc, dnsupdate
idmap_ldb:use rfc2307 = yes
interfaces = 192.168.200.1


 Debugging/Accounting 

# This tells Samba to use a separate log file for each machine
# that connects
   log file = /var/log/samba/log.toy
#   log level = 3

# Cap the size of the individual log files (in KiB).
   max log size = 1000

# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
#   syslog only = no

# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
#   syslog = 0

# Do something sensible when Samba crashes: mail the admin a backtrace
   panic action = /usr/share/samba/panic-action %d

# This parameter determines if nmbd(8) advertises itself as a time server to 
Windows clients.
   time server = yes

printing = bsd
printcap name = /dev/null

#nsupdate command = nsupdate


[netlogon]
comment = Logon scripts for Users
#path = /var/lib/samba/sysvol/home.lxtec.de/scripts
path = /samba/logon
read only = No

[sysvol]
path = /var/lib/samba/sysvol
read only = No

[home]
comment = Unix Home
path = /home/users
read only = No
#valid users = %S
 

Bug#906568: marked as done (samba-dsdb-modules not installable)

[Debian Bug Tracking System]

Your message dated Sun, 19 Aug 2018 10:36:16 +
with message-id 
and subject line Bug#906568: fixed in samba 2:4.8.4+dfsg-2
has caused the Debian Bug report #906568,
regarding samba-dsdb-modules not installable
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.)


-- 
906568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906568
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: samba
Version: 2:4.8.4+dfsg-1
Severity: grave
Justification: renders package unusable

# apt install samba-dsdb-modules
Reading package lists... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
samba-dsdb-modules : Depends: libldb1 (< 2:1.3.6~) but 2:1.4.0+really1.3.5-2 is 
to be installed
E: Unable to correct problems, you have held broken packages.

-- Package-specific info:
* /etc/samba/smb.conf not present
* /var/lib/samba/dhcp.conf not present

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

Kernel: Linux 4.14.60-toy-lxtec-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), 
LANGUAGE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages samba depends on:
ii  adduser   3.117
ii  dpkg  1.19.0.5+b1
ii  libattr1  1:2.4.47-2+b2
ii  libbsd0   0.9.1-1
ii  libc6 2.27-5
ii  libldb1   2:1.4.0+really1.3.5-2
ii  libpam-modules1.1.8-3.8
ii  libpam-runtime1.1.8-3.8
ii  libpopt0  1.16-11
ii  libpython2.7  2.7.15-3
ii  libtalloc22.1.14-1
ii  libtdb1   1.3.15-4
ii  libtevent00.9.36-2
ii  lsb-base  9.20170808
ii  procps2:3.3.15-2
ii  python2.7.15-3
ii  python-dnspython  1.15.0-1
ii  python-samba  2:4.8.4+dfsg-1
ii  python2.7 2.7.15-3
ii  samba-common  2:4.8.4+dfsg-1
ii  samba-common-bin  2:4.8.4+dfsg-1
ii  samba-libs2:4.8.4+dfsg-1
ii  tdb-tools 1.3.15-4

Versions of packages samba recommends:
ii  attr1:2.4.47-2+b2
ii  logrotate   3.11.0-0.1
pn  samba-dsdb-modules  
ii  samba-vfs-modules   2:4.8.4+dfsg-1

Versions of packages samba suggests:
ii  bind9  1:9.11.4+dfsg-4
ii  bind9utils 1:9.11.4+dfsg-4
pn  ctdb   
ii  ldb-tools  2:1.4.0+really1.3.5-2
ii  ntp1:4.2.8p12+dfsg-1
ii  smbldap-tools  0.9.9-1
pn  ufw
ii  winbind2:4.8.4+dfsg-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: samba
Source-Version: 2:4.8.4+dfsg-2

We believe that the bug you reported is fixed in the latest version of
samba, 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.
Mathieu Parent  (supplier of updated samba package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 19 Aug 2018 10:08:22 +0200
Source: samba
Binary: samba samba-libs samba-common samba-common-bin smbclient 
samba-testsuite registry-tools libparse-pidl-perl samba-dev python-samba 
samba-dsdb-modules samba-vfs-modules libsmbclient libsmbclient-dev winbind 
libpam-winbind libnss-winbind libwbclient0 libwbclient-dev ctdb
Architecture: source amd64 all
Version: 2:4.8.4+dfsg-2
Distribution: unstable
Urgency: high
Maintainer: Debian Samba Maintainers 
Changed-By: Mathieu Parent 
Description:
 ctdb   - clustered database to store temporary data
 libnss-winbind - Samba nameservice integration plugins
 libpam-winbind - Windows domain authentication integration plugin
 libparse-pidl-perl - IDL compiler written in Perl
 libsmbclient - shared library for communication with SMB/CIFS servers
 libsmbclient-dev - development files for libsmbclient
 libwbclient-dev - Samba winbind client 

Bug#906568: marked as done (samba-dsdb-modules not installable)

[Debian Bug Tracking System]

Your message dated Sun, 19 Aug 2018 10:36:16 +
with message-id 
and subject line Bug#906562: fixed in samba 2:4.8.4+dfsg-2
has caused the Debian Bug report #906562,
regarding samba-dsdb-modules not installable
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.)


-- 
906562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906562
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: samba
Version: 2:4.8.4+dfsg-1
Severity: grave
Justification: renders package unusable

# apt install samba-dsdb-modules
Reading package lists... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
samba-dsdb-modules : Depends: libldb1 (< 2:1.3.6~) but 2:1.4.0+really1.3.5-2 is 
to be installed
E: Unable to correct problems, you have held broken packages.

-- Package-specific info:
* /etc/samba/smb.conf not present
* /var/lib/samba/dhcp.conf not present

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

Kernel: Linux 4.14.60-toy-lxtec-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), 
LANGUAGE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages samba depends on:
ii  adduser   3.117
ii  dpkg  1.19.0.5+b1
ii  libattr1  1:2.4.47-2+b2
ii  libbsd0   0.9.1-1
ii  libc6 2.27-5
ii  libldb1   2:1.4.0+really1.3.5-2
ii  libpam-modules1.1.8-3.8
ii  libpam-runtime1.1.8-3.8
ii  libpopt0  1.16-11
ii  libpython2.7  2.7.15-3
ii  libtalloc22.1.14-1
ii  libtdb1   1.3.15-4
ii  libtevent00.9.36-2
ii  lsb-base  9.20170808
ii  procps2:3.3.15-2
ii  python2.7.15-3
ii  python-dnspython  1.15.0-1
ii  python-samba  2:4.8.4+dfsg-1
ii  python2.7 2.7.15-3
ii  samba-common  2:4.8.4+dfsg-1
ii  samba-common-bin  2:4.8.4+dfsg-1
ii  samba-libs2:4.8.4+dfsg-1
ii  tdb-tools 1.3.15-4

Versions of packages samba recommends:
ii  attr1:2.4.47-2+b2
ii  logrotate   3.11.0-0.1
pn  samba-dsdb-modules  
ii  samba-vfs-modules   2:4.8.4+dfsg-1

Versions of packages samba suggests:
ii  bind9  1:9.11.4+dfsg-4
ii  bind9utils 1:9.11.4+dfsg-4
pn  ctdb   
ii  ldb-tools  2:1.4.0+really1.3.5-2
ii  ntp1:4.2.8p12+dfsg-1
ii  smbldap-tools  0.9.9-1
pn  ufw
ii  winbind2:4.8.4+dfsg-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: samba
Source-Version: 2:4.8.4+dfsg-2

We believe that the bug you reported is fixed in the latest version of
samba, 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.
Mathieu Parent  (supplier of updated samba package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 19 Aug 2018 10:08:22 +0200
Source: samba
Binary: samba samba-libs samba-common samba-common-bin smbclient 
samba-testsuite registry-tools libparse-pidl-perl samba-dev python-samba 
samba-dsdb-modules samba-vfs-modules libsmbclient libsmbclient-dev winbind 
libpam-winbind libnss-winbind libwbclient0 libwbclient-dev ctdb
Architecture: source amd64 all
Version: 2:4.8.4+dfsg-2
Distribution: unstable
Urgency: high
Maintainer: Debian Samba Maintainers 
Changed-By: Mathieu Parent 
Description:
 ctdb   - clustered database to store temporary data
 libnss-winbind - Samba nameservice integration plugins
 libpam-winbind - Windows domain authentication integration plugin
 libparse-pidl-perl - IDL compiler written in Perl
 libsmbclient - shared library for communication with SMB/CIFS servers
 libsmbclient-dev - development files for libsmbclient
 libwbclient-dev - Samba winbind client 

Bug#906562: marked as done (samba-dsdb-modules not installable)

[Debian Bug Tracking System]

Your message dated Sun, 19 Aug 2018 10:36:16 +
with message-id 
and subject line Bug#906568: fixed in samba 2:4.8.4+dfsg-2
has caused the Debian Bug report #906568,
regarding samba-dsdb-modules not installable
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.)


-- 
906568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906568
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: samba
Version: 2:4.8.4+dfsg-1
Severity: grave
Justification: renders package unusable

# apt install samba-dsdb-modules
Reading package lists... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
samba-dsdb-modules : Depends: libldb1 (< 2:1.3.6~) but 2:1.4.0+really1.3.5-2 is 
to be installed
E: Unable to correct problems, you have held broken packages.

-- Package-specific info:
* /etc/samba/smb.conf present, and attached
* /var/lib/samba/dhcp.conf not present

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

Kernel: Linux 4.14.60-toy-lxtec-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), 
LANGUAGE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages samba depends on:
ii  adduser   3.117
ii  dpkg  1.19.0.5+b1
ii  libattr1  1:2.4.47-2+b2
ii  libbsd0   0.9.1-1
ii  libc6 2.27-5
ii  libldb1   2:1.4.0+really1.3.5-2
ii  libpam-modules1.1.8-3.8
ii  libpam-runtime1.1.8-3.8
ii  libpopt0  1.16-11
ii  libpython2.7  2.7.15-3
ii  libtalloc22.1.14-1
ii  libtdb1   1.3.15-4
ii  libtevent00.9.36-2
ii  lsb-base  9.20170808
ii  procps2:3.3.15-2
ii  python2.7.15-3
ii  python-dnspython  1.15.0-1
ii  python-samba  2:4.8.4+dfsg-1
ii  python2.7 2.7.15-3
ii  samba-common  2:4.8.4+dfsg-1
ii  samba-common-bin  2:4.8.4+dfsg-1
ii  samba-libs2:4.8.4+dfsg-1
ii  tdb-tools 1.3.15-4

Versions of packages samba recommends:
ii  attr1:2.4.47-2+b2
ii  logrotate   3.11.0-0.1
pn  samba-dsdb-modules  
ii  samba-vfs-modules   2:4.8.4+dfsg-1

Versions of packages samba suggests:
ii  bind9  1:9.11.4+dfsg-4
ii  bind9utils 1:9.11.4+dfsg-4
pn  ctdb   
ii  ldb-tools  2:1.4.0+really1.3.5-2
ii  ntp1:4.2.8p12+dfsg-1
ii  smbldap-tools  0.9.9-1
pn  ufw
ii  winbind2:4.8.4+dfsg-1

-- no debconf information
# Global parameters
[global]
workgroup = LXTEC
realm = HOME.LXTEC.NET
netbios name = TOY
server role = active directory domain controller
#server role = standalone server
server services = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, drepl, 
winbind, ntp_signd, kcc, dnsupdate
#server services = s3fs, rpc, nbt, wrepl, kdc, drepl, winbind, 
ntp_signd, kcc, dnsupdate
idmap_ldb:use rfc2307 = yes
interfaces = 192.168.200.1


 Debugging/Accounting 

# This tells Samba to use a separate log file for each machine
# that connects
   log file = /var/log/samba/log.toy
#   log level = 3

# Cap the size of the individual log files (in KiB).
   max log size = 1000

# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
#   syslog only = no

# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
#   syslog = 0

# Do something sensible when Samba crashes: mail the admin a backtrace
   panic action = /usr/share/samba/panic-action %d

# This parameter determines if nmbd(8) advertises itself as a time server to 
Windows clients.
   time server = yes

printing = bsd
printcap name = /dev/null

#nsupdate command = nsupdate


[netlogon]
comment = Logon scripts for Users
#path = /var/lib/samba/sysvol/home.lxtec.de/scripts
path = /samba/logon
read only = No

[sysvol]
path = /var/lib/samba/sysvol
read only = No

[home]
comment = Unix Home
path = /home/users
read only = No
#valid users = %S
 

Bug#906491: mediawiki2latex: FTBFS in buster/sid (File name does not match module name)

[Dirk Hünniger]

Hi Georges,

I set up a VM with buster. I did some minor changes to the sourcecode of 
mediawiki2latex and everything compiles now on buster without warnings. 
The only thing is that I can not test it on buster since something seems 
to be wrong with xelatex on buster in general, I get some warning like 
"I can't find the format file xelatex.fmt". I also get errors when I try 
to install xelatex with apt-get, especially about language packs. What 
do you propose? Should I just publish a new release  of mediawiki2latex. 
I think its currently the best thing to do, since this will keep 
mediawiki2latex in debian, an there will be a realistic chance that the 
problems with xelatex will be solved by others.


Yours Dirk


On 18.08.2018 17:38, Georges Khaznadar wrote:

Dear Dirk,

I created a git repository to manage debian packaging at salsa.debian.org,
and then modified slightly one debain patch to take your proposition in
account.

Unfortunately, the package still FTNFS.

Maybe you would like to create an account at https://salsa.debian.org
and either fork and request some pulls or become a direct maintainer of
https://salsa.debian.org/georgesk/mediawiki2latex

Please find attached the build log for my last build attempt, which is
synchronized with the current state of the repository mentioned above.

Best regards,   Georges.

Dirk Hünniger a écrit :

Hi Georges,

Hi Santiago,

to me it looks that the line "Font" in the section "Other-Modules:" in the
file "mediawiki2latex.cabal" needs to be removed to fix the issue. @Georges
is it easy for you to create a patch to fix that, or should I better release
a new version?

Yours Dirk


On 17.08.2018 21:22, Santiago Vila wrote:

Package: src:mediawiki2latex
Version: 7.29-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
   debian/rules build-arch
dh build-arch
 dh_update_autotools_config -a
 debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
ghc /<>/Setup.lhs
[1 of 1] Compiling Main ( /<>/Setup.lhs, 
/<>/Setup.o )
Linking /<>/Setup ...
/<>/Setup configure
Configuring mediawiki2latex-7.29...
make[1]: Leaving directory '/<>'
 debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
/<>/Setup build
Preprocessing executable 'mediawiki2latex' for mediawiki2latex-7.29..
Building executable 'mediawiki2latex' for mediawiki2latex-7.29..

src/Font.hs:1:1: error:
  File name does not match module name:
  Saw: `Main'
  Expected: `Font'
|
1 | import Data.Tuple
| ^
make[1]: *** [debian/rules:9: override_dh_auto_build] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:14: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


The build was made with "dpkg-buildpackage -B" in my autobuilder.
Most probably, it also fails here in reproducible builds:

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

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.

Bug#906427: duplicity: FTBFS: test failure (gpg failed)

[Alexander Zangerl]

tags 906427 upstream
forwarded 906427 https://bugs.launchpad.net/duplicity/+bug/1780617
thanks

On Fri, 17 Aug 2018 13:15:57 +, Damyan Ivanov writes:
>ERROR: test_sigchain_fileobj (testing.unit.test_collections.CollectionTest)
>Test getting signature chain fileobjs from archive_dir

looks like gnupg 2.2.8 has changed its behaviour in a
fairly incompatible fashion, which throws the test suite off.
upstream has a fix but it's not part of a release - yet.

regards
az


-- 
Alexander Zangerl + GPG Key 2FCCF66BB963BD5F + http://snafu.priv.at/
Meddle not in the affairs of sysadmins, for they are subtle and quick to lart.


signature.asc
Description: Digital Signature

Processed: Re: Bug#906427: duplicity: FTBFS: test failure (gpg failed)

[Debian Bug Tracking System]

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

> tags 906427 upstream
Bug #906427 [src:duplicity] duplicity: FTBFS: test failure (gpg failed)
Added tag(s) upstream.
> forwarded 906427 https://bugs.launchpad.net/duplicity/+bug/1780617
Bug #906427 [src:duplicity] duplicity: FTBFS: test failure (gpg failed)
Set Bug forwarded-to-address to 
'https://bugs.launchpad.net/duplicity/+bug/1780617'.
> thanks
Stopping processing here.

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