date:20191114

Your message dated Thu, 14 Nov 2019 08:45:55 +
with message-id 
and subject line Bug#925653: fixed in clamfs 1.1.0-1
has caused the Debian Bug report #925653,
regarding clamfs: ftbfs with GCC-9
to be marked as done.

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

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


-- 
925653: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925653
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:clamfs
Version: 1.0.1-3
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-9

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

The package fails to build in a test rebuild on at least amd64 with
gcc-9/g++-9, but succeeds to build with gcc-8/g++-8. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc9-20190321/clamfs_1.0.1-3_unstable_gcc9.log
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

GCC 9 also passes the linker option --as-needed by default; typical
build issues are passing libraries before object files to the linker,
or underlinking of convenience libraries built from the same source.

[...]
checking for memset... yes
checking for mkdir... yes
checking for mkfifo... yes
checking for rmdir... yes
checking for setxattr... yes
checking for strdup... yes
checking for strerror... yes
checking for utime... yes
checking for boostlib >= 1.33... yes
checking fuse.h usability... yes
checking fuse.h presence... yes
checking for fuse.h... yes
checking for fuse_main in -lfuse... yes
checking rlog/rlog.h usability... yes
checking rlog/rlog.h presence... yes
checking for rlog/rlog.h... yes
checking for main in -lrlog... yes
checking Poco/ExpireLRUCache.h usability... yes
checking Poco/ExpireLRUCache.h presence... yes
checking for Poco/ExpireLRUCache.h... yes
checking Poco/Net/MailMessage.h usability... yes
checking Poco/Net/MailMessage.h presence... yes
checking for Poco/Net/MailMessage.h... yes
checking Poco/Net/MailRecipient.h usability... yes
checking Poco/Net/MailRecipient.h presence... yes
checking for Poco/Net/MailRecipient.h... yes
checking Poco/Net/SMTPClientSession.h usability... yes
checking Poco/Net/SMTPClientSession.h presence... yes
checking for Poco/Net/SMTPClientSession.h... yes
checking Poco/Net/StringPartSource.h usability... yes
checking Poco/Net/StringPartSource.h presence... yes
checking for Poco/Net/StringPartSource.h... yes
checking for main in -lPocoFoundation... yes
checking for main in -lPocoFoundation... (cached) yes
checking for libccgnu2 via ccgnu2-config... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating doc/Makefile
config.status: creating doc/Doxyfile
config.status: creating doc/svg/Makefile
config.status: creating config.h
config.status: executing depfiles commands
dh_testdir
/usr/bin/make
make[1]: Entering directory '/<>'
/usr/bin/make  all-recursive
make[2]: Entering directory '/<>'
Making all in src
make[3]: Entering directory '/<>/src'
x86_64-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I..   -I/usr/include 
-D_FILE_OFFSET_BITS=64 -D_REENTRANT -DFUSE_USE_VERSION=25 
-DRLOG_COMPONENT=clamfs -D_GNU_SOURCE -I/usr/include -Wall -O2 -DNDEBUG  -g -O2 
-MT clamfs.o -MD -MP -MF .deps/clamfs.Tpo -c -o clamfs.o clamfs.cxx
clamfs.cxx:963:16: warning: invalid suffix on literal; C++11 requires a space 
between literal and string macro [-Wliteral-suffix]
  963 | rLog(Info, "ClamFS v"VERSION);
  |^
In file included from /usr/include/cc++/thread.h:50,
 from /usr/include/cc++/file.h:56,
 from rlog.hxx:32,
 from clamfs.hxx:38,
 from clamfs.cxx:53:
/usr/include/cc++/string.h:734:35: error: friend declaration of 'std::istream& 
getline(std::istream&, ost::String&, char, size_t)' specifies default argument

Bug#944714: moonshot-trust-router ftbfs during rebuilds for libevent 2.1.7

Source: moonshot-trust-router
Version: 3.5.0+1
Severity: serious
Tags: ftbfs sid bullseye
Justification: ftbfs

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear Sam,

Your package is part of the libevent transition. I scheduled binNMU's, but your
package FTBFS on all supported archs.

Paul

https://buildd.debian.org/status/package.php?p=moonshot-trust-router

Tail of log for moonshot-trust-router on amd64:

/usr/include/glib-2.0/glib/gtypes.h:551:8: note: declared here
  551 | struct _GTimeVal
  |^
cc1: all warnings being treated as errors
make[2]: *** [Makefile:2847: common/tr_mq.o] Error 1
make[2]: *** Waiting for unfinished jobs
cc1: all warnings being treated as errors
make[2]: *** [Makefile:2847: common/tr_config_comms.o] Error 1
cc1: all warnings being treated as errors
make[2]: *** [Makefile:2847: common/tr_config.o] Error 1
make[2]: Leaving directory '/<>'
make[1]: *** [Makefile:5666: all-recursive] Error 1
make[1]: Leaving directory '/<>'
dh_auto_build: make -j4 returned exit code 2
make: *** [debian/rules:13: build-arch] Error 255


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

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

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl3NFRQACgkQnFyZ6wW9
dQpF9AgAmOsnMDyYZYLvDLfl7FWfqaYYvQXmKmKHNtipkM8JwU9N7cSK5i5sGXgU
xKUUSqUQBlDsEOtKUgA4NkugyUV/Yt0Ji7XWVE/9ybcT1IvkEDOJr68YY2WrrCFl
HyaGWMb54TYEtOsrKjrUCieVsvYwlPqRGi+x8UnBMKLkIWmCSXT+FAwjd77q0jeF
paBmqX7Uwo7R3X1jZoAIO84ILtKilPGfm50qD1gDMYJqeQQ4Puk8NrkyhPhZpQwF
vjTJmgZ/Sc+cWRUYn1qc6ij+7/pt7b23xGzdyNemunVB1UH/4BgUcO6z3TNMY1sX
FQ8AJ9sGwT1q925CPIBK4Z6mrWh3Sg==
=Za/9
-END PGP SIGNATURE-

Bug#944681: marked as done (py-libzfs: FTBFS: libzfs.c:1:2: error: #error Do not use this file, it is the result of a failed Cython compilation.)

Your message dated Thu, 14 Nov 2019 08:49:55 +
with message-id 
and subject line Bug#944681: fixed in py-libzfs 0.0+git20191113.2991805-1
has caused the Debian Bug report #944681,
regarding py-libzfs: FTBFS: libzfs.c:1:2: error: #error Do not use this file, 
it is the result of a failed Cython compilation.
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.)


-- 
944681: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944681
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: py-libzfs
Version: 0.0+git20190717.39ccb15-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source

py-libzfs FTBFS on all architectures:
https://buildd.debian.org/status/package.php?p=py-libzfs&suite=experimental
I can also reproduce it on amd64.

   dh_auto_build -a -O--buildsystem=pybuild
I: pybuild base:217: /usr/bin/python3 setup.py build 
running build
running build_ext
cythoning libzfs.pyx to libzfs.c
building 'libzfs' extension
creating build
creating build/temp.linux-arm64-3.7
aarch64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g 
-fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security 
-g -fwrapv -O2 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.7m -c libzfs.c -o 
build/temp.linux-arm64-3.7/libzfs.o -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -I/usr/include/libzfs/ -I/usr/include/libspl/ 
-D_MACHINE_ENDIAN_H_ -DHAVE_ISSETUGID -Werror=implicit-function-declaration 
-Wdate-time -D_FORTIFY_SOURCE=2
libzfs.c:1:2: error: #error Do not use this file, it is the result of a failed 
Cython compilation.
1 | #error Do not use this file, it is the result of a failed Cython 
compilation.
  |  ^
warning: ./pxd/nvpair.pxd:56:3: 'DATA_TYPE_UINT8_ARRAY' redeclared 
warning: libzfs.pyx:571:24: Non-trivial type declarators in shared declaration 
(e.g. mix of pointers and values). Each pointer declaration should be on its 
own line.
warning: libzfs.pyx:571:31: Non-trivial type declarators in shared declaration 
(e.g. mix of pointers and values). Each pointer declaration should be on its 
own line.
warning: libzfs.pyx:572:29: Non-trivial type declarators in shared declaration 
(e.g. mix of pointers and values). Each pointer declaration should be on its 
own line.
warning: libzfs.pyx:572:35: Non-trivial type declarators in shared declaration 
(e.g. mix of pointers and values). Each pointer declaration should be on its 
own line.

Error compiling Cython file:

...

with nogil:
IF HAVE_ZPOOL_SEARCH_IMPORT_LIBZUTIL and 
HAVE_ZPOOL_SEARCH_IMPORT_PARAMS == 3:
result = libzfs.zpool_search_import(self.handle, &iargs, 
&libzfs.libzfs_config_ops)
ELSE:
result = libzfs.zpool_search_import(self.handle, &iargs)
  ^


libzfs.pyx:814:31: cimported module has no attribute 'zpool_search_import'

Error compiling Cython file:

...
raise OSError(errno.EINVAL, 'Not a character device')

IF HAVE_ZPOOL_READ_LABEL_PARAMS == 3:
ret = libzfs.zpool_read_label(fd, &handle, NULL)
ELSE:
ret = libzfs.zpool_read_label(fd, &handle)
   ^


libzfs.pyx:3390:20: cimported module has no attribute 'zpool_read_label'

Error compiling Cython file:

...

with nogil:
IF HAVE_ZPOOL_SEARCH_IMPORT_LIBZUTIL and 
HAVE_ZPOOL_SEARCH_IMPORT_PARAMS == 3:
result = libzfs.zpool_search_import(self.handle, &iargs, 
&libzfs.libzfs_config_ops)
ELSE:
result = libzfs.zpool_search_import(self.handle, &iargs)
  ^


libzfs.pyx:814:51: Calling gil-requiring function not allowed without gil
error: command 'aarch64-linux-gnu-gcc' failed with exit status 1
E: pybuild pybuild:341: build: plugin distutils failed with: exit code=1: 
/usr/bin/python3 setup.py build 
dh_auto_build: pybuild --build -i python{version} -p 3.7 returned exit code 13
make: *** [debian/rules:8: build-arch] Error 255

Andreas
--- End Message ---
--- Begin Message ---
Source: py-libzfs
Source-V

Bug#943867: marked as done (stressant: non-buildd binaries)

Your message dated Thu, 14 Nov 2019 08:50:17 +
with message-id 
and subject line Bug#943867: fixed in stressant 0.5.0+nmu1
has caused the Debian Bug report #943867,
regarding stressant: non-buildd binaries
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.)


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

Package: stressant
Version: 0.5.0
Severity: serious

The release team have decreed that non-buildd binaries can no longer migrate to 
testing. Please make a source-only upload so your package can migrate.
--- End Message ---
--- Begin Message ---
Source: stressant
Source-Version: 0.5.0+nmu1

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

Debian distribution maintenance software
pp.
Peter Michael Green  (supplier of updated stressant 
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: Sat, 09 Nov 2019 07:50:54 +
Source: stressant
Architecture: source
Version: 0.5.0+nmu1
Distribution: unstable
Urgency: medium
Maintainer: Antoine Beaupré 
Changed-By: Peter Michael Green 
Closes: 943867
Changes:
 stressant (0.5.0+nmu1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Re-upload source-only to allow migration to testing (Closes: 943867).
   * Fix clean target.
Checksums-Sha1:
 0b0e65f3b5b34507dac75f3346b33e66e843177c 1840 stressant_0.5.0+nmu1.dsc
 79d4239c6b177348221cbfd9ae28f8e7d600d639 45252 stressant_0.5.0+nmu1.tar.xz
 b641a75058ed7a8ad3f89b7d190d0bf57a66b17b 6872 
stressant_0.5.0+nmu1_source.buildinfo
Checksums-Sha256:
 18d85fc96e14890181abfe640832818e9ca21742f97e8b3ebd80e92b864acb04 1840 
stressant_0.5.0+nmu1.dsc
 d52695255f8702ac3c56980472b55c35cf9c65a868d58e1f20418fbbb93a38d8 45252 
stressant_0.5.0+nmu1.tar.xz
 c4da5b13d3dcdc936a8f62175e9cb60c2bc8b5afa7df6c4eb4b5e1a9dbe028c6 6872 
stressant_0.5.0+nmu1_source.buildinfo
Files:
 1ffc4ff80b0fd64785174f20e8a01240 1840 admin optional stressant_0.5.0+nmu1.dsc
 2f34870f43086b41a8282c2b7173cd2a 45252 admin optional 
stressant_0.5.0+nmu1.tar.xz
 d010ff0ec6376aa586ab27e15a62caee 6872 admin optional 
stressant_0.5.0+nmu1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAl3Gcu4UHHBsdWd3YXNo
QGRlYmlhbi5vcmcACgkQDEjqKnqP/XvkTQ/8DK/+QqQkaSrH6Vvp2QqusBY3ibrN
U64fJkH8vmVnyNQekNiBoLmKxWbO4YgFhvwlzkViufIr6yp0zSc0i3jeuU+CN+0L
B1tHSuXB4oqncJ4XB4lODJ1w/wltiG33eHWuipTMViK7gpdgUlQ5cTUtZwh1PvoV
t+A9APa4nC5VFshYGst23opLtv18o+/HQHjirLb4P8SATYg2ytQdnNKcHI+kCZnf
b57XD3l+vwVsejhwYeTmlFw+/17mVd0IBvgcZGx+20vOa2sgeorJKYRrEdO2hP+v
J7mpOWYEZ+x2m+oMJQyLvDMU5IVipU55aajfyRDEbyqBcz5Hbj6w/camPs7p4zsD
qURiC/1CXfEQIrPuLGacMJMNwHTFN0Ssoh/Hp9gW2M+yYZg4b8FA80vnwd516Scf
6Nks8OBdUFKuHRNhyIK0DlRbxDxUM6Ly3pn2EG1jh2ON6hKx/ab3BuJeYqFShEPg
jYtrh3skmhcJNAgYzVK13hXmsKMumTOvtSHLsljlO0YFXInrdmQvd7GxPO/Lpa7g
c4niaulvAZrRphXPNIZ4syBtU8tP2avJ6Xr5HSe65yFUWPF7gzNpvL9WutmJq76k
zuyz67rtDet9lTF8ePTCdoB1WkOGUBfd32P5WAQXHSQg4o3jjUC9vIAu7Q8qV8zY
N/HHXFwZQ3zEfc8=
=ATm3
-END PGP SIGNATURE End Message ---

Bug#944715: thunderbird ftbfs on mips64el during rebuild for libevent 2.1.7

Source: thunderbird
Version: 1:68.2.2-1
Severity: serious
Tags: ftbfs sid bullseye
Justification: ftbfs

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear maintainers,

Your package is part of the libevent transition. I binNMU'ed your package but
if fails to build on mips64el. Can you please investigate the situation?

Paul

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

Tail of log for thunderbird on mips64el:

 3:26.57 js/src> checking whether the C++ compiler supports 
-Wno-gnu-zero-variadic-macro-arguments... yes
 3:27.08 js/src> checking whether the C++ compiler supports 
-Wno-noexcept-type... yes
 3:27.60 js/src> checking whether the C++ compiler supports 
-fno-sized-deallocation... yes
 3:27.63 js/src> checking for rustc... /usr/bin/rustc
 3:27.63 js/src> checking for cargo... /usr/bin/cargo
 3:30.11 js/src> checking rustc version... 1.37.0
 3:30.30 js/src> checking cargo version... 1.36.0
 3:30.45 js/src> ERROR: Command `/usr/bin/rustc --print target-list` failed 
with exit status -10.
 3:30.83 *** Fix above errors and then restart with\
 3:30.83"./mach build"
 3:30.83 make[2]: *** [client.mk:115: configure] Error 1
 3:30.83 make[2]: Leaving directory '/<>'
make[1]: *** [debian/rules:112: override_dh_auto_configure] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:83: build-arch] Error 2


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

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

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl3NFsUACgkQnFyZ6wW9
dQqERgf8CToWmH4I9o+2089pjBxzIeMbJbR/GNNb0or5K76g+JGHb9Y10MSEANVu
7fw9qa/V67YH72NWyOTNsQ5NCLpVP0jFEGaTyiDQBFJbZaNse+QtkBvy26LfOwth
wyrRIN9+5RLPbRok8k/gbLa9PCf6/gLW/mLmcPz6u0eSZMzSSd0EH/zwxTjTJID8
FDlnMo1mymjtE9U9QB5BkSLICmdxPPy11vXo7NghHR3m73Tl26nkSGYdycJp/s29
IHvseEo0pwGQo6CUvl6cGgFp0WvT88KX4suFXS5uqkGUnH72ZsR1D0bnvxJ8Thjf
ekFQudmPd5xvoHAHPWJRMmsrqZ+3wQ==
=vRBw
-END PGP SIGNATURE-

Bug#885351: marked as done (mcomix: Depends on unmaintained pygtk)

Your message dated Thu, 14 Nov 2019 16:58:47 +0800
with message-id 

and subject line close this bug
has caused the Debian Bug report #885351,
regarding mcomix: Depends on unmaintained pygtk
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.)


-- 
885351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885351
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mcomix
Version: 1.2.1-1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster
X-Debbugs-CC: em...@debian.org

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings (and gtk3).

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

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

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

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
New version with python3 and gtk3 port uploaded.

-- 
Emfox Zhou

GnuPG Public Key: 0x1DEB
--- End Message ---

Bug#936997: marked as done (mcomix: Python2 removal in sid/bullseye)

Your message dated Thu, 14 Nov 2019 17:00:07 +0800
with message-id 

and subject line close this bug
has caused the Debian Bug report #936997,
regarding mcomix: Python2 removal in sid/bullseye
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.)


-- 
936997: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936997
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mcomix
Version: 1.2.1-1.1
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:mcomix

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
  New version with python3 and gtk3 port uploaded.

-- 
Emfox Zhou

GnuPG Public Key: 0x1DEB
--- End Message ---

Processed: tagging 944601

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

> tags 944601 + ftbfs sid bullseye
Bug #944601 [src:ocamlviz] FTBFS with OCaml 4.08.1 (safe strings)
Added tag(s) sid, ftbfs, and bullseye.
> thanks
Stopping processing here.

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

Processed: Bug#927250 marked as pending in golang-github-getlantern-errors

Processing control commands:

> tag -1 pending
Bug #927250 [src:golang-github-getlantern-errors] 
golang-github-getlantern-errors: FTBFS in sid (missing build-depends)
Added tag(s) pending.

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

Bug#927250: marked as pending in golang-github-getlantern-errors

2019-11-14 Thread Andreas Henriksson

Control: tag -1 pending

Hello,

Bug #927250 in golang-github-getlantern-errors reported by you has been fixed 
in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/go-team/packages/golang-github-getlantern-errors/commit/5ab52a2e543d068fe7b7cc501bf0f17ae73007a7


Add missing (build-)dep on getlantern-hex

Closes: #927250


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/927250

Bug#944718: octave-dicom Build-Depends on libgdcm2-dev which isn't build from source anymore

Source: octave-dicom
Version: 0.2.2-3
Severity: serious
Tags: ftbfs sid bullseye

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear maintainers,

Your package Build-Depends on libgdcm2-dev, but the src:gdcm package
transitioned to 3 and dropped that package. Please fix your package to use the
new version of gdcm.

Paul

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

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

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl3NHwkACgkQnFyZ6wW9
dQqEkgf+MhxngdDuUVTIaqVr7jICIwuHHc8cO8K7ZjP1hMV4aY5BS3YSQyqMsI+B
/SbQ6UvhE2yCxhzlpgVbthGtISwmmMBQNNWY/qshN8WUagHVaZw59ndUEvDTNjYP
QQNXkvBq+cMHZJxu84zecjxqlDqBFs1J78c6HdFeTlMfIOhb8RBMY+LfRbQA0xzI
ZbjJ2nmBDq1eMea/PMNsNsiNqTDnATqT/4RVVKIZnxyrhemEfzdsGmZZWmHU6PB4
o1psninSsCQNSrlWHz3V6JDwviQLVdIWBQRWJdjT3C/96bF3N5UBeOD7ZmwLzryM
Ys0hOBp/zBjCvyCQTsfyCdxachlCWA==
=pxx5
-END PGP SIGNATURE-

Bug#927250: marked as done (golang-github-getlantern-errors: FTBFS in sid (missing build-depends))

Your message dated Thu, 14 Nov 2019 09:35:17 +
with message-id 
and subject line Bug#927250: fixed in golang-github-getlantern-errors 
0.0~git20190325.abdb3e3-2
has caused the Debian Bug report #927250,
regarding golang-github-getlantern-errors: FTBFS in sid (missing build-depends)
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.)


-- 
927250: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927250
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:golang-github-getlantern-errors
Version: 0.0~git20190325.abdb3e3-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --buildsystem=golang --with=golang
   dh_update_autotools_config -i -O--buildsystem=golang
   dh_autoreconf -i -O--buildsystem=golang
   dh_auto_configure -i -O--buildsystem=golang
   dh_auto_build -i -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go install 
-gcflags=all=\"-trimpath=/<>/golang-github-getlantern-errors-0.0\~git20190325.abdb3e3/obj-x86_64-linux-gnu/src\"
 
-asmflags=all=\"-trimpath=/<>/golang-github-getlantern-errors-0.0\~git20190325.abdb3e3/obj-x86_64-linux-gnu/src\"
 -v -p 1 github.com/getlantern/errors
src/github.com/getlantern/hidden/hidden.go:11:2: cannot find package 
"github.com/getlantern/hex" in any of:
/usr/lib/go-1.11/src/github.com/getlantern/hex (from $GOROOT)
/<>/obj-x86_64-linux-gnu/src/github.com/getlantern/hex 
(from $GOPATH)
dh_auto_build: cd obj-x86_64-linux-gnu && go install 
-gcflags=all=\"-trimpath=/<>/golang-github-getlantern-errors-0.0\~git20190325.abdb3e3/obj-x86_64-linux-gnu/src\"
 
-asmflags=all=\"-trimpath=/<>/golang-github-getlantern-errors-0.0\~git20190325.abdb3e3/obj-x86_64-linux-gnu/src\"
 -v -p 1 github.com/getlantern/errors returned exit code 1
make: *** [debian/rules:4: build-indep] Error 1
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


Looks like a missing build-depends to me.

Thanks.
--- End Message ---
--- Begin Message ---
Source: golang-github-getlantern-errors
Source-Version: 0.0~git20190325.abdb3e3-2

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

Debian distribution maintenance software
pp.
Andreas Henriksson  (supplier of updated 
golang-github-getlantern-errors 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, 13 Nov 2019 14:55:41 +0100
Source: golang-github-getlantern-errors
Architecture: source
Version: 0.0~git20190325.abdb3e3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
Changed-By: Andreas Henriksson 
Closes: 927250
Changes:
 golang-github-getlantern-errors (0.0~git20190325.abdb3e3-2) unstable; 
urgency=medium
 .
   * Add missing (build-)dep on getlantern-hex (Closes: #927250)
Checksums-Sha1:
 b8bfe227f74208020d089f36659b3e91a20c7c32 2624 
golang-github-getlantern-errors_0.0~git20190325.abdb3e3-2.dsc
 2db4790ea8f105d56d1fd060c03c3215af1915df 1508 
golang-github-getlantern-errors_0.0~git20190325.abdb3e3-2.debian.tar.xz
 d1a673f51ad51074134279889199d005cf5e110b 6370 
golang-github-getlantern-errors_0.0~git20190325.abdb3e3-2_amd64.buildinfo
Checksums-Sha256:
 afb39014f6fb22af0cdcbe01778c0d61c792a818ca25d067f70fedace6af5630 2624 
golang-github-getlantern-errors_0.0~git20190325.abdb3e3-2.dsc
 18f38f1a57b728f99d4bca3f1f8df964be3aebc9be6f3c3aba1588237f634310 1508 
golang-github-getlantern-errors_0.0~git20190325.abdb3e3-2.debian.tar.xz
 cd4dce311c5f49863bd7e82dd498b2bd3a7dfc1ad08315bdc87f59353aa2061b 6370 
golang-github-getlantern-errors_0.0~git20190325.abdb3e3-2_amd64.buildinfo
Files:
 0f7c844a8f254328f56de1e3e6d011be 2624 devel optional 
golang-github-getlantern-errors_0.0~git20190325.abdb3e3-2.dsc
 e0600a0d7fc21eda11f5974f7b3cc186 1508 devel optional 
golang-github-getlantern-errors_0.0~git20190

Bug#944719: golang-gopkg-stretchr-testify.v1: duplicate of golang-testify

2019-11-14 Thread Andreas Henriksson

Source: golang-gopkg-stretchr-testify.v1
Version: 1.3.0-2
Severity: serious

Dear Maintainer,

It seems to me like this package is a duplicate of the already existing
golang-testify package.

I assume the duplication happened because the same component has
multiple import paths.

I asked about this on #debian-golang and got the following advice on how
it should be implemented to avoid the duplication:

zhsj
ah: same thing, that should be a bug.
make a link ./usr/share/gocode/src/gopkg.in/stretchr/testify.v1/ -> 
./usr/share/gocode/src/github.com/stretchr/testify/ and should request RM 
golang-gopkg-stretchr-testify.v1

Leaving that up to someone else who knows these things better to
implement Given there seems to be no reverse dependencies of this
package I'm marking this bug report as serious so that the package will
eventually fall out of testing if noone actively deals with this
situation, which I think is reasonable

$ ssh mirror.ftp-master.debian.org "dak rm -Rn golang-gopkg-stretchr-testify.v1"
Will remove the following packages from unstable:

golang-gopkg-stretchr-testify.v1 |1.3.0-2 | source
golang-gopkg-stretchr-testify.v1-dev |1.3.0-2 | all

Maintainer: Debian Go Packaging Team 

--- Reason ---

--

Checking reverse dependencies...
No dependency problem found.


Regards,
Andreas Henriksson

Bug#944517: openscenegraph-3.4: FTBFS in sid after latest openscenegraph

2019-11-14 Thread Gianfranco Costamagna

Hello Alberto,

On Mon, 11 Nov 2019 12:13:11 + 
=?utf-8?B?QWxiZXJ0byBMdWFjZXMgRmVybsOhbmRleg==?=  wrote:
> Thank you for the report.
> 
> The plan is to remove this package altogether from the archive and
> replace it with openscenegraph.
> 
> I am going to fill the bug reports for the rdeps, and then ask for the
> removal of 3.4.
> 
> Regards,
> 
> Alberto
> 


I did upload I think all the reverse-dependencies, and now we should be good to 
proceed with its removal
(modulo waiting some hours for builds to complete and publish).

Is it ok for you to open a bug report to get it removed from the archive?

Please do it if you can, so it gets removed once the archive is updated

thanks

Gianfranco

> On 11/11/19 10:32, Gianfranco Costamagna wrote:
> > Source: openscenegraph-3.4
> > Version: 3.4.1+dfsg1-5
> > Severity: serious
> > 
> > Hello, looks like there is some thread link problem in the package after 
> > the latest openscenegraph upload in sid:
> > 
> > [snip]
> > dpkg-shlibdeps: error: cannot find library libOpenThreads.so.20 needed by 
> > debian/libopenscenegraph-3.4-131/usr/lib/x86_64-linux-gnu/libosgText.so.3.4.1
> >  (ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '')
> > dpkg-shlibdeps: error: cannot find library libOpenThreads.so.20 needed by 
> > debian/openscenegraph-3.4/usr/bin/osgtext (ELF format: 'elf64-x86-64' abi: 
> > '0201003e'; RPATH: '')
> > dpkg-shlibdeps: error: cannot find library libOpenThreads.so.20 needed by 
> > debian/libopenscenegraph-3.4-131/usr/lib/x86_64-linux-gnu/libosg.so.3.4.1 
> > (ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '')
> > [snip]
> > 
> > the library seems to be now at SONAME 21, but I have no clue about what 
> > might be wrong...
> > 
> > G.
> > 
>

Processed: tagging 944341

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

> tags 944341 + ftbfs sid bullseye
Bug #944341 [libopencv-imgcodecs-dev] libopencv-imgcodecs-dev depends on cruft 
package.
Added tag(s) sid, bullseye, and ftbfs.
> thanks
Stopping processing here.

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

Bug#944722: orthanc-webviewer Build-Depends on libgdcm2-dev which isn't build from source anymore

Source: orthanc-webviewer
Version: 2.5-1
Severity: serious
Tags: ftbfs sid bullseye
Justification: ftbfs

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear maintainers,

Your package Build-Depends on libgdcm2-dev, but the src:gdcm package
transitioned to 3 and dropped that package. Please fix your package to use the
new version of gdcm.

Paul

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

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

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl3NIeUACgkQnFyZ6wW9
dQol/wf/eboirQBMZxv7rNnGTqNSQNiekFMsAR7c8jEYDz7wZuaUpWKRvmK2GsOR
jAwSIOHliqU7Nikwhr9PJiT33K57LnzGoIO66th1Q9/Ja8CgBxP8bPPinWl6qkxa
C6ZCD2imY8dLKVs3C67H7UeELf3cTN/Dxcc7NS4EUx9WFZOf+QEHu5Ol2/aw5Qbm
kH0ETzBrDe4WeBiA9PoPlngPr3NoUSeL7Vb+zWozA/kprUv995wp6owzMOo2AO2u
5pIP8Wusc1cOV2XaWDFE4gzJOrsFJC9hRssfae2rmMDuvfFy83azrHVF4ABF/UdA
0daqkA2XB5D8bBBPj8awyYrdRgZ2iw==
=p6XM
-END PGP SIGNATURE-

Bug#944721: orthanc-dicomweb Build-Depends on libgdcm2-dev which isn't build from source anymore

Source: orthanc-dicomweb
Version: 1.0+dfsg-1
Severity: serious
Tags: ftbfs sid bullseye
Justification: ftbfs

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear maintainers,

Your package Build-Depends on libgdcm2-dev, but the src:gdcm package
transitioned to 3 and dropped that package. Please fix your package to use the
new version of gdcm.

Paul

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

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

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl3NIXIACgkQnFyZ6wW9
dQp2Qgf6AgL4uckCGVsybsdVPH4ejHv7nIPUlc5IrjeZO62rcmd3TraI01nddTEz
oTv0zSjLe3UDONzwE+h/mCbMvShmCdml+XgLvvcQIP7TbZ9Iz5duXRiQ5uvVK4iV
dfG+plwmppJfHcmQRco8HoJlBGdJWQfuf8x5Me4KUqOTCaIVucZ30IgqnIcu2tQq
xL0oKpBlu6YKp4sSrkcW3qILhl/Ezv385Cm/c9DDKkFKuEykk+DDDFMeEReiIe2M
UdaF9IjYSDbQKBU1EBLYIsm/b7mJ55cNpPS0Ke8eb33VVX9D2SIdo9VfSdpcqqcm
itrIbU/TaCk6acJZGDcIXgDU0qeFdg==
=4X22
-END PGP SIGNATURE-

Bug#943474: marked as done (Doesn't build with Django 2.2)

Your message dated Thu, 14 Nov 2019 10:07:06 +
with message-id 
and subject line Bug#943474: fixed in django-modeltranslation 0.13.3-0.1
has caused the Debian Bug report #943474,
regarding Doesn't build with Django 2.2
to be marked as done.

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

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


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

Hi,

Your package doesn't build with Django 2.2, which is blocking is transition to
Testing. Please fix this ASAP. This also means fixing Py2 removal, as there's
no Py2 support in Django 2.2.

Cheers,

Thomas Goirand (zigo)
--- End Message ---
--- Begin Message ---
Source: django-modeltranslation
Source-Version: 0.13.3-0.1

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

Debian distribution maintenance software
pp.
Michal Arbet  (supplier of updated 
django-modeltranslation package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 14 Nov 2019 10:24:02 +0100
Source: django-modeltranslation
Architecture: source
Version: 0.13.3-0.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Michal Arbet 
Closes: 936416 943474
Changes:
 django-modeltranslation (0.13.3-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Ondřej Nový ]
   * d/changelog: Remove trailing whitespaces
   * Use 'python3 -m sphinx' instead of sphinx-build for building docs
   * Use debhelper-compat instead of debian/compat.
   * Drop Python 2 support (Closes: #936416).
   * Bump debhelper compat level to 12.
   * Bump standards version to 4.4.0 (no changes).
   * Bump Standards-Version to 4.4.1.
 .
   [ Thomas Goirand ]
   * Team upload.
   * New usptream release with Django 2.2 support.
 .
   [ Michal Arbet ]
   * Fix build with Django 2.2 (Closes: #943474).
Checksums-Sha1:
 453d66f34120a6d3eb1ea1841c101585e082f4f5 2371 
django-modeltranslation_0.13.3-0.1.dsc
 56eebe1460baf4fa839a79c77c8d2259092514e6 99645 
django-modeltranslation_0.13.3.orig.tar.gz
 c34a1789cc6874deb6e1c23a0187aa3cec263d74 4792 
django-modeltranslation_0.13.3-0.1.debian.tar.xz
 81415249f4aa563b7672c296808a313137fb6c4d 7961 
django-modeltranslation_0.13.3-0.1_amd64.buildinfo
Checksums-Sha256:
 92edff41fbd6b7eb4955189fb78bc373c51e2c6a6403d9156e8e2224aca252a0 2371 
django-modeltranslation_0.13.3-0.1.dsc
 665c05bd3f1de1f56bdfe69b7fbaab71ec2aebec5224165f2b4d49c1ddfc1f7a 99645 
django-modeltranslation_0.13.3.orig.tar.gz
 7fafb78d3d907136d496ec8f03c082524abdd0ebde143e2ec4e291938a3e6d39 4792 
django-modeltranslation_0.13.3-0.1.debian.tar.xz
 8f406630e2f52c0e492204718a6fb86da111c3c941e7b361525447408aaff499 7961 
django-modeltranslation_0.13.3-0.1_amd64.buildinfo
Files:
 db09788eb54ecd8ba2efb60dec593a8c 2371 python optional 
django-modeltranslation_0.13.3-0.1.dsc
 86693803c1f601350eb30a16261d6e39 99645 python optional 
django-modeltranslation_0.13.3.orig.tar.gz
 e755301c623708ae6d180ed9136735b3 4792 python optional 
django-modeltranslation_0.13.3-0.1.debian.tar.xz
 b130d8eced3cf29ac52c9254e821fa24 7961 python optional 
django-modeltranslation_0.13.3-0.1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE5XQmXq/+PEpA+qGNSgz2OUJ4hOMFAl3NIsQACgkQSgz2OUJ4
hOOl8Q/9EWsRAMmO0RNfBlOfUZq11vW2ELoj58ORPxzJ73RxGIxl+8GD9J1zWGnQ
gzOnpW92ywC3bS38ONzpjB3csiCe4jYd4tOVBIMB8oiLqVEkYc8Jl1K5TsNaWhso
mBo03cTGHaClqjIdQEIqYJSkSvG98/Ws4Q5l0SPJ66yrVtMkkO1DvUccwv0o4Jr4
dHak7zUBIoHyivYsAXDhSSOvkHeYhxf1mP4lJ6fb/77VYkA30rMU6ndX4UcKb8sW
mm3B4Fn/7w5B8L/viagtFRCNYrEHQ1M3rNIUj/yzHPw8dLXzGjCeGtZzHRARUMS/
fr/357JG5WXcyp2MmPrw2UKLeAh11wPAzB7OIen4ik0RQP1jkCSDoxWb8XbCK36s
2sKov+AYYL9Hhnf1go24KtAcE6wgUmsu9fM1unOC+AiSvP/5islKKRQHC1+JsnlG
YYfvuMNvagMXnr4VVHXGVjEiCcRzGIaVPPEXMxeBJxzEJJV/8bAL3rOBW0Hhcj+9
qsMAUzTAVlCYLoRqJS3Hhw6yB4t4uqTnVhuWtyjGKxWvgRvA7QsD8Ji1MgeA1FvA
d5E3dNQzYn2Nu2/6twb0EDG4f47o5smk1+0J6VrLSAL9NmHS3/lVN0AMngURpWSR
ymLhGEMS/fIpWDKuGGNu9lR6WTjAQ/GwDDwhbeP20KtsFFxeh+g=
=GPqq
-END PGP

Processed: tagging 944697

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

> tags 944697 + confirmed
Bug #944697 [ftp.debian.org] security.debian.org: please bring back MD5Sum, at 
least for buster/updates
Added tag(s) confirmed.
> thanks
Stopping processing here.

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

Bug#944697: security.debian.org: please bring back MD5Sum, at least for buster/updates

2019-11-14 Thread Ansgar

On Thu, 2019-11-14 at 01:47 +0100, Cyril Brulebois wrote:
> Assuming the FTP team is responsible for security's dak setup as well,
> we'd like to get MD5Sum back in buster/updates.
> 
> python-apt relies on md5 fields internally, as documented in #944696,
> and a current symptom is live-wrapper's tracebacking accordingly when
> packages are available in security; this has been the case for the
> intel-microcode package, for a few hours.

Okay; I'll look at restoring it in the evening.

> jessie/updates and stretch/updates seem fine (MD5Sum is present there).
> I don't have an opinion regarding bulleyes/updates (MD5Sum is missing
> there) at this point, but given at least some apt bindings don't support
> missing MD5Sum, it would seem premature to remove it from there as well?

I would like to keep MD5sum away for now from bullseye-security to see
if we could keep it that way (I would like to get rid of MD5sum
eventually).  Practically it won't make a difference as the suite is
empty anyway...

Ansgar

Bug#944709: marked as done (autopkgtests failure with OCaml 4.08.1)

Your message dated Thu, 14 Nov 2019 10:49:32 +
with message-id 
and subject line Bug#944709: fixed in diffoscope 130
has caused the Debian Bug report #944709,
regarding autopkgtests failure with OCaml 4.08.1
to be marked as done.

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

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


-- 
944709: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944709
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:diffoscope
Version: 129
Severity: serious
User: debian-ocaml-ma...@lists.debian.org
Usertags: ocaml-4.08-transition

Dear Maintainer,

Diffoscope's autopkgtests fail with OCaml 4.08.1. It looks like they
just need to be updated.

This prevents migration of ocaml to testing.


Cheers,

-- 
Stéphane

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

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

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

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated diffoscope 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, 14 Nov 2019 11:22:20 +0100
Source: diffoscope
Architecture: source
Version: 130
Distribution: unstable
Urgency: medium
Maintainer: Reproducible builds folks 

Changed-By: Mattia Rizzolo 
Closes: 944709
Changes:
 diffoscope (130) unstable; urgency=medium
 .
   [ Chris Lamb ]
   * debian/tests/basic-command-line:
 Move from deprecated ADTTMP to AUTOPKGTEST_TMP.
   * Correct the matching of R .rds files by also detecting newer versions
 of this file format.
   * Drop unused BASE_DIR global in the tests.
   * Try and ensure that new test data files are generated dynamically, ie.
 at least no new ones are added without "good" reasons.
   * Truncate the tcpdump expected diff to 8KB (from ~600KB).
   * Refresh OCaml test fixtures to support OCaml >= 4.08.1.  Closes: #944709
   * Correct reference to the ".rdx" extension in a comment.
   * Update XML test for Python 3.8+.
   * Don't use line-base dbuffering when communucating with subprocesses
 in binary mode. (Closes: reproducible-builds/diffoscope#75)
 .
   [ Jelle van der Waa ]
   * Add support for comparing .zst files are created by zstd.
 (Closes: reproducible-builds/diffoscope!34)
Checksums-Sha1:
 deabf9b7fdacff9b784df1fe6067e756ef5e8ccf 4704 diffoscope_130.dsc
 73a38ec08c3601a962fada3179817c9556f7f54a 974520 diffoscope_130.tar.xz
 559d86e96ef16f5361b9a4ed120d728158caf018 26134 diffoscope_130_amd64.buildinfo
Checksums-Sha256:
 618fcd5c2cd1476b7535301ed66f93eb582c768c77de480d743bc782f3a4b7c5 4704 
diffoscope_130.dsc
 bbaaeedc02eead27ece817914a5f47a73125c939f52b143d01fc406149ffd9e5 974520 
diffoscope_130.tar.xz
 051b51384619e8583c5f0e62031bf0798f07a93675af30a169cf32243aab12ee 26134 
diffoscope_130_amd64.buildinfo
Files:
 60a6535df0989caca1402091cb5b844b 4704 devel optional diffoscope_130.dsc
 727938b0620d1743f1a306fc6c1fd23e 974520 devel optional diffoscope_130.tar.xz
 e5a733760cdcafe72bc9b87ff65ff946 26134 devel optional 
diffoscope_130_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAl3NLacACgkQCBa54Yx2
K63cwA/+Mt4NCbZdEU8h7RL6a7Ac2/lvWJN7GVK8oD4s8tY8tN7jgJcBF/1iKWoz
XnBt4/kQn2EWgjakP5IJEmmCCmyH3dV264AWDzuX5zBqNdXYoI4z06jh3Qletas2
dRP++OtHAQi+DAGxAngnyIfxf+n7JTU0M0LoHSXVLJ09Rlhzwm+KzL5DSB1jmTmZ
61+uaJYVCeNjD3MM2usKpfLG7LfgclbtBxQxFElKqz6UU5HL+YoYbvUzfL2xMU5m
058gU/OMMlgXnlTprSE2t2xkvRkNgss9uOOlTbv1mRcooCdsje0WVhbVYYA/jcyp
Gf1EE6zz/kvjeWikJ9DojvbxYFiyJ8kdCuC5nNLdFrtSJPmnM9enkpSYK1qBXciJ
GR7kgtMcUgwi4WQJOWrb50EU7ZhDs+YgVFqzij2IO93vQ48Q7Dto6J6Vo1cek+/J
N/O3OItsKZMLlyTe9qrRp8ArwDHnMpFkID+ILXx0QjVX2hIeX4cOSXbyuYkqroNC
jszwodnGyHWvnRH

Bug#942633: gitlab: Experimental gitlab requires gitshell 9.3.0 but only 9.1.0 is packaged

2019-11-14 Thread Romain Bignon

On 14/Nov - 07:45, Pirate Praveen wrote:
>  has protobuf 3.7 and grpc 1.19.
> You need to downgrade both and use gitaly 1.59.3+dfsg-1~bpo10+2 (which
> allows these versions).
> 
> And because of 
> you may need to regenrate Gemfile.lock
> 
> # cd /usr/share/gitlab
> # sudo -u gitlab truncate -s0 Gemfile.lock
> # sudo -u gitlab bundle install --local
> # systemctl restart gitlab-sidekiq
> # systemctl restart gitlab gitaly
> 
> I had to use a separate repo with protobuf 3.10 and grpc 1.23 ->
> https://people.debian.org/~praveen/protobuf/ to build gitaly
> 
> I'm keeping this bug open till we can use same version of protobuf for both
> gitaly build and gitlab. I have opened
> https://gitlab.com/gitlab-org/gitaly/issues/2164 to work with upstream on
> this

Great it works, thank you. Please tell us when the issue is fixed in the
experimental repository and that we can upgrade all versions from this
repository, as it is currently somewhat a hot fix.

Romain

Bug#944683: marked as done (FTBFS: missing file /usr/lib/nodejs/axios/dist/axios.min.js)

Your message dated Thu, 14 Nov 2019 11:20:20 +
with message-id 
and subject line Bug#944683: fixed in orthanc-dicomweb 1.0+dfsg-2
has caused the Debian Bug report #944683,
regarding FTBFS: missing file /usr/lib/nodejs/axios/dist/axios.min.js
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.)


-- 
944683: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944683
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: orthanc-dicomweb
Version: orthanc-dicomweb_1.0+dfsg-1
Severity: serious
Justification: 4

Dear Maintainer,

While I was trying to rebuild the package to use libgdcm-dev instead
of 
libgdcm2-dev (change already pushed to the repo) the package failed to
build for another reason with the following error: 

  CMake Error at
debian/ThirdPartyDownloads/JavaScriptLibraries.cmake:10 (file):
file COPY cannot find "/usr/lib/nodejs/axios/dist/axios.min.js".
  Call Stack (most recent call first):
CMakeLists.txt:68 (include)

It seems like the file has changed its location to 

   /usr/share/nodejs/axios/dist/axios.min.js

Best, 
Gert 


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

Kernel: Linux 5.3.9-gentoo (SMP w/6 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: unable to detect

Versions of packages orthanc-dicomweb depends on:
ii  libboost-filesystem1.67.0  1.67.0-13
ii  libboost-locale1.67.0  1.67.0-13
ii  libboost-regex1.67.0   1.67.0-13
ii  libboost-system1.67.0  1.67.0-13
ii  libboost-thread1.67.0  1.67.0-13
ii  libc6  2.29-3
ii  libgcc11:9.2.1-19
ii  libgdcm2.8 2.8.8-9+b1
ii  libjsoncpp11.7.4-3+b1
ii  libpugixml1v5  1.9-3
ii  libstdc++6 9.2.1-19
ii  libuuid1   2.34-0.1
pn  orthanc

orthanc-dicomweb recommends no packages.

orthanc-dicomweb suggests no packages.
--- End Message ---
--- Begin Message ---
Source: orthanc-dicomweb
Source-Version: 1.0+dfsg-2

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

Debian distribution maintenance software
pp.
Sebastien Jodogne  (supplier of updated orthanc-dicomweb 
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, 14 Nov 2019 11:20:16 +0100
Source: orthanc-dicomweb
Architecture: source
Version: 1.0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Sebastien Jodogne 
Closes: 944683 944721
Changes:
 orthanc-dicomweb (1.0+dfsg-2) unstable; urgency=medium
 .
   * Fix FTBFS: linking with gdcm. Closes: #944721
   * Fix FTBFS: use of axios. Closes: #944683
   * Install the "Status.txt" documentation file from upstream.
Checksums-Sha1:
 5435756ed80f9deea385b2e68f30df104498980e 2354 orthanc-dicomweb_1.0+dfsg-2.dsc
 8c9a6639aa923b4aae8a9b4fc64237aac5586159 2244248 
orthanc-dicomweb_1.0+dfsg-2.debian.tar.xz
 de93ec0125be89544b951d15e432fa4f93b60e6f 15559 
orthanc-dicomweb_1.0+dfsg-2_source.buildinfo
Checksums-Sha256:
 134cbb5f621554f9c658eb5ec5927535d71bc8e7d2622dd52ac4c9c8efae48e3 2354 
orthanc-dicomweb_1.0+dfsg-2.dsc
 b651275a3670c4dd910a300ad38a76723b9eca7fe52d4a00e4c1832a7a484fcc 2244248 
orthanc-dicomweb_1.0+dfsg-2.debian.tar.xz
 5a2b353489d4e9bfd4aee43686b04448d4df2123c526f0da18776177dc296476 15559 
orthanc-dicomweb_1.0+dfsg-2_source.buildinfo
Files:
 bc5269a5e8112cb7588b0b0019dbdac7 2354 science optional 
orthanc-dicomweb_1.0+dfsg-2.dsc
 48dcbdfc4c8be3475be1a5e869449ca1 2244248 science optional 
orthanc-dicomweb_1.0+dfsg-2.debian.tar.xz
 75c467308bc247223e657a474bc5af79 15559 science optional 
orthanc-dicomweb_1.0+dfsg-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEk76fGX7V0MMOWT2Lp3ZYKzEqw10FAl3NNW4UHHMuam9kb2du
ZUBnbWFpbC5jb20ACgkQp3ZYKzEqw10CLA/+LDdlB96OzU+KcANDfkqrFzqH759Z
rFpdsmybTd2h5

Bug#944721: marked as done (orthanc-dicomweb Build-Depends on libgdcm2-dev which isn't build from source anymore)

Your message dated Thu, 14 Nov 2019 11:20:20 +
with message-id 
and subject line Bug#944721: fixed in orthanc-dicomweb 1.0+dfsg-2
has caused the Debian Bug report #944721,
regarding orthanc-dicomweb Build-Depends on libgdcm2-dev which isn't build from 
source anymore
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.)


-- 
944721: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944721
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: orthanc-dicomweb
Version: 1.0+dfsg-1
Severity: serious
Tags: ftbfs sid bullseye
Justification: ftbfs

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear maintainers,

Your package Build-Depends on libgdcm2-dev, but the src:gdcm package
transitioned to 3 and dropped that package. Please fix your package to use the
new version of gdcm.

Paul

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

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

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl3NIXIACgkQnFyZ6wW9
dQp2Qgf6AgL4uckCGVsybsdVPH4ejHv7nIPUlc5IrjeZO62rcmd3TraI01nddTEz
oTv0zSjLe3UDONzwE+h/mCbMvShmCdml+XgLvvcQIP7TbZ9Iz5duXRiQ5uvVK4iV
dfG+plwmppJfHcmQRco8HoJlBGdJWQfuf8x5Me4KUqOTCaIVucZ30IgqnIcu2tQq
xL0oKpBlu6YKp4sSrkcW3qILhl/Ezv385Cm/c9DDKkFKuEykk+DDDFMeEReiIe2M
UdaF9IjYSDbQKBU1EBLYIsm/b7mJ55cNpPS0Ke8eb33VVX9D2SIdo9VfSdpcqqcm
itrIbU/TaCk6acJZGDcIXgDU0qeFdg==
=4X22
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: orthanc-dicomweb
Source-Version: 1.0+dfsg-2

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

Debian distribution maintenance software
pp.
Sebastien Jodogne  (supplier of updated orthanc-dicomweb 
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, 14 Nov 2019 11:20:16 +0100
Source: orthanc-dicomweb
Architecture: source
Version: 1.0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Sebastien Jodogne 
Closes: 944683 944721
Changes:
 orthanc-dicomweb (1.0+dfsg-2) unstable; urgency=medium
 .
   * Fix FTBFS: linking with gdcm. Closes: #944721
   * Fix FTBFS: use of axios. Closes: #944683
   * Install the "Status.txt" documentation file from upstream.
Checksums-Sha1:
 5435756ed80f9deea385b2e68f30df104498980e 2354 orthanc-dicomweb_1.0+dfsg-2.dsc
 8c9a6639aa923b4aae8a9b4fc64237aac5586159 2244248 
orthanc-dicomweb_1.0+dfsg-2.debian.tar.xz
 de93ec0125be89544b951d15e432fa4f93b60e6f 15559 
orthanc-dicomweb_1.0+dfsg-2_source.buildinfo
Checksums-Sha256:
 134cbb5f621554f9c658eb5ec5927535d71bc8e7d2622dd52ac4c9c8efae48e3 2354 
orthanc-dicomweb_1.0+dfsg-2.dsc
 b651275a3670c4dd910a300ad38a76723b9eca7fe52d4a00e4c1832a7a484fcc 2244248 
orthanc-dicomweb_1.0+dfsg-2.debian.tar.xz
 5a2b353489d4e9bfd4aee43686b04448d4df2123c526f0da18776177dc296476 15559 
orthanc-dicomweb_1.0+dfsg-2_source.buildinfo
Files:
 bc5269a5e8112cb7588b0b0019dbdac7 2354 science optional 
orthanc-dicomweb_1.0+dfsg-2.dsc
 48dcbdfc4c8be3475be1a5e869449ca1 2244248 science optional 
orthanc-dicomweb_1.0+dfsg-2.debian.tar.xz
 75c467308bc247223e657a474bc5af79 15559 science optional 
orthanc-dicomweb_1.0+dfsg-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEk76fGX7V0MMOWT2Lp3ZYKzEqw10FAl3NNW4UHHMuam9kb2du
ZUBnbWFpbC5jb20ACgkQp3ZYKzEqw10CLA/+LDdlB96OzU+KcANDfkqrFzqH759Z
rFpdsmybTd2h5YKrA8g5ip5p4ngx3uhve2HkSfJRvfcJgOh2c/uLai4l2iqiO+PJ
/+DZfLvyi4MwpxgLtUmwTSI18Y5hWAvGr4RuYuSwq2OS9LsQUAhcQgASiFS2AxAS
aJexUU80HMCNlC2En2sfP6y54kUUPDj2EJon7kb6SUHAvWdg45teImQESEEIPus5
C6Av2l/0s3HCfRFYfBqrG+Rt3kFaHOwspqWeWObv7IONVPZxB1wqT2/F57YLBj95
pgV6rxyRB8Wdm9mhmLuIYBPfgn75j6RnITMeoAz53diIDiO858jVx33zVK+QFIjf
Ydo8UduaZnO8nTXwIHL

Bug#944726: systemd undefined symbol

2019-11-14 Thread Jan Sindelar

Package: systemd
Version: 243-5
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

   * What led up to the situation?
Installing latest systemd package using apt full-upgrade in testing

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
Unbootable system

   * What outcome did you expect instead?
Normal boot



-- Package-specific info:

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

Kernel: Linux 4.9.0-1-grml-amd64 (SMP w/4 CPU cores)
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8), 
LANGUAGE=cs_CZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages systemd depends on:
ii  adduser  3.118
ii  libacl1  2.2.53-5
ii  libapparmor1 2.13.3-6
ii  libaudit11:2.8.5-2
ii  libblkid12.34-0.1
ii  libc62.29-3
ii  libcap2  1:2.27-1
ii  libcryptsetup12  2:2.2.1-1
ii  libgcrypt20  1.8.5-3
ii  libgnutls30  3.6.10-4
ii  libgpg-error01.36-7
ii  libidn2-02.2.0-2
ii  libip4tc21.8.3-2
ii  libkmod2 26-3
ii  liblz4-1 1.9.2-1
ii  liblzma5 5.2.4-1+b1
ii  libmount12.34-0.1
ii  libpam0g 1.3.1-5
ii  libpcre2-8-0 10.32-5+b1
ii  libseccomp2  2.4.1-2
ii  libselinux1  2.9-2+b2
ii  libsystemd0  243-5
ii  mount2.34-0.1
ii  util-linux   2.34-0.1

Versions of packages systemd recommends:
ii  dbus1.12.16-2
iu  libpam-systemd  243-5

Versions of packages systemd suggests:
ii  policykit-10.105-26
iu  systemd-container  243-5

Versions of packages systemd is related to:
pn  dracut   
ii  initramfs-tools  0.135
ii  udev 243-5

-- no debconf information
systemd-delta: symbol lookup error: /lib/systemd/libsystemd-shared-243.so: 
undefined symbol: seccomp_api_get
==> /var/lib/systemd/deb-systemd-helper-enabled/acpi-fakekey.service.dsh-also 
<==
/etc/systemd/system/sockets.target.wants/acpi-fakekey.socket
/etc/systemd/system/multi-user.target.wants/acpi-fakekey.service

==> /var/lib/systemd/deb-systemd-helper-enabled/keyboard-setup.service.dsh-also 
<==
/etc/systemd/system/sysinit.target.wants/keyboard-setup.service

==> /var/lib/systemd/deb-systemd-helper-enabled/avahi-daemon.service.dsh-also 
<==
/etc/systemd/system/multi-user.target.wants/avahi-daemon.service
/etc/systemd/system/sockets.target.wants/avahi-daemon.socket
/etc/systemd/system/dbus-org.freedesktop.Avahi.service

==> /var/lib/systemd/deb-systemd-helper-enabled/unbound.service.dsh-also <==
/etc/systemd/system/multi-user.target.wants/unbound.service

==> 
/var/lib/systemd/deb-systemd-helper-enabled/timers.target.wants/e2scrub_all.timer
 <==

==> 
/var/lib/systemd/deb-systemd-helper-enabled/timers.target.wants/apt-daily.timer 
<==

==> 
/var/lib/systemd/deb-systemd-helper-enabled/timers.target.wants/man-db.timer <==

==> 
/var/lib/systemd/deb-systemd-helper-enabled/timers.target.wants/apt-daily-upgrade.timer
 <==

==> 
/var/lib/systemd/deb-systemd-helper-enabled/timers.target.wants/logrotate.timer 
<==

==> 
/var/lib/systemd/deb-systemd-helper-enabled/timers.target.wants/exim4-base.timer
 <==

==> /var/lib/systemd/deb-systemd-helper-enabled/tlp.service.dsh-also <==
/etc/systemd/system/multi-user.target.wants/tlp.service

==> /var/lib/systemd/deb-systemd-helper-enabled/virtlogd.socket.dsh-also <==
/etc/systemd/system/sockets.target.wants/virtlogd.socket

==> /var/lib/systemd/deb-systemd-helper-enabled/udisks2.service.dsh-also <==
/etc/systemd/system/graphical.target.wants/udisks2.service

==> /var/lib/systemd/deb-systemd-helper-enabled/lvm2-lvmpolld.socket.dsh-also 
<==
/etc/systemd/system/sysinit.target.wants/lvm2-lvmpolld.socket

==> 
/var/lib/systemd/deb-systemd-helper-enabled/graphical.target.wants/udisks2.service
 <==

==> 
/var/lib/systemd/deb-systemd-helper-enabled/graphical.target.wants/rtkit-daemon.service
 <==

==> /var/lib/systemd/deb-systemd-helper-enabled/dm-event.service.dsh-also <==
/etc/systemd/system/sysinit.target.wants/dm-event.service

==> /var/lib/systemd/deb-systemd-helper-enabled/hostapd.service.dsh-also <==
/etc/systemd/system/multi-user.target.wants/hostapd.service

==> 
/var/lib/systemd/deb-systemd-helper-enabled/apt-daily-upgrade.timer.dsh-also <==
/etc/systemd/system/timers.target.wants/apt-daily-upgrade.timer

==> /var/lib/systemd/deb-systemd-helper-enabled/sfacctd.service.dsh-also <==
/etc/systemd/system/multi-user.target.wants/sfacctd.service

==> /var/lib/systemd/deb-systemd-helper-enabled/uuidd.service.dsh-also <==
/etc/systemd/system/sockets.target.wants/uuidd.socket

==> /var/lib/systemd/deb-systemd-helper-enabled/atopacct.service.dsh-also <==
/etc/systemd/system/multi-user.target.wants/atopacct.service

==> /var/lib/systemd/deb-systemd-helper-enabled

Bug#944726: systemd undefined symbol

2019-11-14 Thread Michael Biebl

Control: tags -1 + moreinfo

Am 14.11.19 um 13:22 schrieb Jan Sindelar:
> Package: systemd
> Version: 243-5
> Severity: critical
> Justification: breaks the whole system
> 
> Dear Maintainer,
> 
>* What led up to the situation?
> Installing latest systemd package using apt full-upgrade in testing
> 
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
>* What was the outcome of this action?
> Unbootable system
> 
>* What outcome did you expect instead?
> Normal boot

Please attach an exact error message you are seeing, especially
regarding the undefined symbol.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#944726: systemd undefined symbol

Processing control commands:

> tags -1 + moreinfo
Bug #944726 [systemd] systemd undefined symbol
Added tag(s) moreinfo.

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

Bug#944722: marked as done (orthanc-webviewer Build-Depends on libgdcm2-dev which isn't build from source anymore)

Your message dated Thu, 14 Nov 2019 11:50:25 +
with message-id 
and subject line Bug#944722: fixed in orthanc-webviewer 2.5-2
has caused the Debian Bug report #944722,
regarding orthanc-webviewer Build-Depends on libgdcm2-dev which isn't build 
from source anymore
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.)


-- 
944722: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944722
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: orthanc-webviewer
Version: 2.5-1
Severity: serious
Tags: ftbfs sid bullseye
Justification: ftbfs

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear maintainers,

Your package Build-Depends on libgdcm2-dev, but the src:gdcm package
transitioned to 3 and dropped that package. Please fix your package to use the
new version of gdcm.

Paul

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

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

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl3NIeUACgkQnFyZ6wW9
dQol/wf/eboirQBMZxv7rNnGTqNSQNiekFMsAR7c8jEYDz7wZuaUpWKRvmK2GsOR
jAwSIOHliqU7Nikwhr9PJiT33K57LnzGoIO66th1Q9/Ja8CgBxP8bPPinWl6qkxa
C6ZCD2imY8dLKVs3C67H7UeELf3cTN/Dxcc7NS4EUx9WFZOf+QEHu5Ol2/aw5Qbm
kH0ETzBrDe4WeBiA9PoPlngPr3NoUSeL7Vb+zWozA/kprUv995wp6owzMOo2AO2u
5pIP8Wusc1cOV2XaWDFE4gzJOrsFJC9hRssfae2rmMDuvfFy83azrHVF4ABF/UdA
0daqkA2XB5D8bBBPj8awyYrdRgZ2iw==
=p6XM
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: orthanc-webviewer
Source-Version: 2.5-2

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

Debian distribution maintenance software
pp.
Sebastien Jodogne  (supplier of updated orthanc-webviewer 
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, 14 Nov 2019 12:10:53 +0100
Source: orthanc-webviewer
Architecture: source
Version: 2.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Sebastien Jodogne 
Closes: 944722
Changes:
 orthanc-webviewer (2.5-2) unstable; urgency=medium
 .
   * Fix FTBFS: linking with gdcm. Closes: #944722
Checksums-Sha1:
 0aef92c2aaf656b9a46cc1a9f69cfef70af4bd0a 2269 orthanc-webviewer_2.5-2.dsc
 106f0f73e3bdd386911d7f71c7584ee29ab882af 1768444 
orthanc-webviewer_2.5-2.debian.tar.xz
 2e85dd39f2035a8c4a156d41a1e12632bd4f680d 15226 
orthanc-webviewer_2.5-2_source.buildinfo
Checksums-Sha256:
 e9409469f4793892c4fdd829204e8ef884f3340107636aa6b63f11b6ea951ddd 2269 
orthanc-webviewer_2.5-2.dsc
 1097f05149cf0a8a83465c0608d4b5c7a58a170f499c757409577e6d236eee4d 1768444 
orthanc-webviewer_2.5-2.debian.tar.xz
 41ee0329d94345c193fb6070f9b41c6e266f2644a4a6eeae03964ee01989dfb7 15226 
orthanc-webviewer_2.5-2_source.buildinfo
Files:
 36b53510858008a9aac37b1356fe7734 2269 science optional 
orthanc-webviewer_2.5-2.dsc
 4a454c0865699fd179876876f62960b2 1768444 science optional 
orthanc-webviewer_2.5-2.debian.tar.xz
 674827ac5ba8d555e4f4b101c6b80480 15226 science optional 
orthanc-webviewer_2.5-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEk76fGX7V0MMOWT2Lp3ZYKzEqw10FAl3NOxMUHHMuam9kb2du
ZUBnbWFpbC5jb20ACgkQp3ZYKzEqw11+nRAAsVKrqTGAVnQ+R7YFurxRxw8A7teL
+Vjd5EZ4OmKac3ZDwgADzNEqmgue7J6/WpCnnhUELA7G6pqj95Jfo7xvQnnTu1Ef
0pGV7o8F+6v09jrQFX8LFLumTMDsV7KR0sbT5dGA/Bd3qhPIdUoZy+bS48hB+wWS
fGJmfp/kP4SbyD0YbRLnZoWGRs3+x/Jvdm0zeM+SMouPSQXUx0672TvzrB0CVIG0
Q4VES6iWtj1fsYfOLsA6HhQWKF21btWrQYK7zZL/m+Eg+MO+hAzaB6k886cAjnjd
MgZ0Tt16HCnlOra58bcTpeTnsok8Ko0jRiUlmaMfls1Auf0jwITjb+s5iFMv4rtf
uZWu4BpsgYLK80jC+i2qAJL2DlNNTcRp/NuKtNAm94i6TtUip6Z8hJS8wpwN6OT8
AcKhB1uekPgA5peayRih+v2FTCBxTobn5o5QkZ3hreZSWpEJA3VRG6VIeDK+7XqU
9vCkAYfj2qDy0YqpCOxAlSkkojt5L/cJ1dilZBjQv+v0HSxb8/KbLSTfb0r

Bug#944671: [Debian-med-packaging] Bug#944671: orthanc-dicomweb: missing build on armel

2019-11-14 Thread Sébastien Jodogne


Hello,

Thanks for your feedback. Indeed, "node-axios" is needed to build the 
orthanc-dicomweb package.


Please could you indicate where I can find information about how to 
remove the old armel build?


Regards,
Sébastien-


On 13/11/19 16:45, Ivo De Decker wrote:

package: src:orthanc-dicomweb
version: 1.0+dfsg-1
severity: serious
tags: ftbfs

Hi,

The latest upload of orthanc-dicomweb to unstable fails on armel:

https://buildd.debian.org/status/package.php?p=orthanc-dicomweb

It seems orthanc-dicomweb build-depends on node-axios, which needs nodejs,
which is unavailable on armel. If the build-dependency is optional, it should
be removed on armel. Otherwise, the old binary should be removed there.

Cheers,

Ivo

___
Debian-med-packaging mailing list
debian-med-packag...@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging



--
Sébastien Jodogne
Mail: s.jodo...@orthanc-labs.com
Web: http://www.orthanc-labs.com/
Twitter: https://twitter.com/sjodogne

Be part of OrthancCon 2019! http://conference.orthanc-server.com/

Bug#930869: Please keep pm-utils

2019-11-14 Thread Adam Borowski

On Thu, Nov 14, 2019 at 09:13:51AM +0100, Andras Korn wrote:
> I just stumbled on this bugreport.
> 
> I'm a happy pm-utils user and would like the package to stick around. I use
> it on dozens of computers ranging from servers to desktops to laptops.
> 
> From reading the bugreport, there doesn't appear to be any identifiable,
> specific, actionable reason for removing it, does there?

There's none as far as I can tell, indeed.

After a thought, even cleaning away the quirks would be counterproductive. 
They apply to old i386 machines that need real mode BIOS calls; while I and
most of us have no such hardware to test, it's still used by some users.
But keeping such i386 support is not _my_ itch to scratch, I personally
wouldn't cry if those parts were trimmed away.

Thus:
* on old buggy hardware pm-utils works while new stuff doesn't
* on old non-buggy, and on modern hardware, pm-utils works and is more
  convenient to use (eg. on headless boxes)

Ie, this bug report is outright bogus.  Without even a single identifiable
actionable problem, there's nothing to fix.

Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ A MAP07 (Dead Simple) raspberry tincture recipe: 0.5l 95% alcohol,
⣾⠁⢠⠒⠀⣿⡁ 1kg raspberries, 0.4kg sugar; put into a big jar for 1 month.
⢿⡄⠘⠷⠚⠋⠀ Filter out and throw away the fruits (can dump them into a cake,
⠈⠳⣄ etc), let the drink age at least 3-6 months.

Processed: Help needed to adapt python-skbio to Python3(?) / Pandas

Processing control commands:

> tags -1 help
Bug #944042 [python3-skbio] python3-skbio: FTBFS and autopkgtest fail with 
pandas 0.25
Added tag(s) help.
> tags -1 upstream
Bug #944042 [python3-skbio] python3-skbio: FTBFS and autopkgtest fail with 
pandas 0.25
Added tag(s) upstream.
> forwarded -1 https://github.com/biocore/scikit-bio/issues/1678
Bug #944042 [python3-skbio] python3-skbio: FTBFS and autopkgtest fail with 
pandas 0.25
Set Bug forwarded-to-address to 
'https://github.com/biocore/scikit-bio/issues/1678'.

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

Bug#944042: Help needed to adapt python-skbio to Python3(?) / Pandas

2019-11-14 Thread Andreas Tille

Control: tags -1 help
Control: tags -1 upstream
Control: forwarded -1 https://github.com/biocore/scikit-bio/issues/1678

Hi Rebecca,

thanks a lot for working on the Pandas migration.

On Wed, Nov 13, 2019 at 10:19:56PM +, Rebecca N. Palmer wrote:
> The ones that are blocking pandas [1] are python-skbio,
> 
> [1] https://qa.debian.org/excuses.php?package=pandas (cnvkit since fixed)

I've checked the issue with some patch from upstream[1] but failed.  I
also tried to build HEAD from upstream which also leaves three remaining
errors which I reported in issue #1678[2]:


==
ERROR: test_munging_invalid_type_to_self_type 
(skbio.sequence.tests.test_sequence.TestDistance)
--
Traceback (most recent call last):
  File 
"/build/python-skbio-0.5.5a/.pybuild/cpython3_3.7_skbio/build/skbio/sequence/tests/test_sequence.py",
 line 2369, in test_munging_invalid_type_to_self_type
Sequence("ACGT").distance(42)
  File 
"/build/python-skbio-0.5.5a/.pybuild/cpython3_3.7_skbio/build/skbio/sequence/_sequence.py",
 line 1539, in distance
other = self._munge_to_self_type(other, 'distance')
  File 
"/build/python-skbio-0.5.5a/.pybuild/cpython3_3.7_skbio/build/skbio/sequence/_sequence.py",
 line 2161, in _munge_to_self_type
return self.__class__(other)
  File 
"/build/python-skbio-0.5.5a/.pybuild/cpython3_3.7_skbio/build/skbio/sequence/_sequence.py",
 line 622, in __init__
s = np.frombuffer(sequence, dtype=np.uint8)
TypeError: a bytes-like object is required, not 'int'

==
ERROR: test_init_invalid_sequence 
(skbio.sequence.tests.test_sequence.TestSequence)
--
Traceback (most recent call last):
  File 
"/build/python-skbio-0.5.5a/.pybuild/cpython3_3.7_skbio/build/skbio/sequence/tests/test_sequence.py",
 line 465, in test_init_invalid_sequence
Sequence(('a', 'b', 'c'))
  File 
"/build/python-skbio-0.5.5a/.pybuild/cpython3_3.7_skbio/build/skbio/sequence/_sequence.py",
 line 622, in __init__
s = np.frombuffer(sequence, dtype=np.uint8)
TypeError: a bytes-like object is required, not 'tuple'

==
FAIL: test_no_variation_pearson 
(skbio.stats.distance.tests.test_mantel.MantelTests)
--
Traceback (most recent call last):
  File 
"/build/python-skbio-0.5.5a/.pybuild/cpython3_3.7_skbio/build/skbio/stats/distance/tests/test_mantel.py",
 line 247, in test_no_variation_pearson
npt.assert_equal(obs, (np.nan, np.nan, 3))
  File "/usr/lib/python3/dist-packages/numpy/testing/_private/utils.py", line 
355, in assert_equal
assert_equal(actual[k], desired[k], 'item=%r\n%s' % (k, err_msg), verbose)
  File "/usr/lib/python3/dist-packages/numpy/testing/_private/utils.py", line 
427, in assert_equal
raise AssertionError(msg)
AssertionError:
Items are not equal:
item=0

 ACTUAL: 0.0
 DESIRED: nan

--
Ran 2352 tests in 44.011s

FAILED (SKIP=30, errors=2, failures=1)


I somehow suspect that the two errors above might be caused by a broken
Python3 conversion - any help to fix this would be welcome.

Kind regards

   Andreas.

[1] 
https://github.com/biocore/scikit-bio/commit/9c061da7e2746aee403b41621f71b118ce5c52f8
[2] https://github.com/biocore/scikit-bio/issues/1678

-- 
http://fam-tille.de

Processed: tagging 925797

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

> tags 925797 + ftbfs
Bug #925797 [src:opensurgsim] opensurgsim: ftbfs with GCC-9
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#944671: [Debian-med-packaging] Bug#944671: orthanc-dicomweb: missing build on armel

2019-11-14 Thread Ivo De Decker


Hi,

On 11/14/19 12:44 PM, Sébastien Jodogne wrote:

Hello,

Thanks for your feedback. Indeed, "node-axios" is needed to build the 
orthanc-dicomweb package.


Please could you indicate where I can find information about how to 
remove the old armel build?


some info is here:

https://wiki.debian.org/ftpmaster_Removals

Note that you can close this bug once the removal is done (otherwise 
this bug would prevent migration to testing).


Andreas, I see that you are uploader of this package. I suspect you 
could help Sébastien if more info is needed?


Thanks,

Ivo

Bug#940127: ghostscript makes c2esp autopkgtest timeout

2019-11-14 Thread Jonas Smedegaard

Quoting Didier 'OdyX' Raboud (2019-09-22 15:30:53)
> Le dimanche, 22 septembre 2019, 13.25:19 h CEST Brian Potkin a écrit :
> > On Sat 21 Sep 2019 at 17:39:20 +0200, Didier 'OdyX' Raboud wrote:
> > > Le samedi, 21 septembre 2019, 16.24:30 h CEST Brian Potkin a écrit :
> > > > > There's clearly a regression in ghostscript 9.28 that started
> > > > > segfaulting
> > > > > in the c2esp filter chain. But I can't manage to reproduce it outside
> > > > > of
> > > > > the "cups + c2esp + cups-filters (gstoraster) + ghostscript"
> > > > > environment.
> > > > > 
> > > > > Brian; Till: any idea?
> > > > 
> > > > No ideas from me really. I too get gstoraster stopping when attempting
> > > > to print /usr/share/cups/data/form_russian.pdf; but the same is true for
> > > > form_english.pdf.
> > > 
> > > Ah, sorry; I formulated my inquiry weakly. Let me try again:
> > > 
> > > Do you have a hint on how to reproduce the failing ghostscript call (or
> > > the
> > > gstoraster call) directly, without using CUPS in the middle?
> > 
> > Would this do?
> > 
> > cat /usr/share/cups/data/form_russian.pdf | gs -dQUIET -dPARANOIDSAFER
> > -dNOPAUSE -dBATCH -dNOINTERPOLATE -dNOMEDIAATTRS -dShowAcroForm
> > -sstdout=%stderr -sOutputFile=%stdout -sDEVICE=cups -r600x600
> > -dDEVICEWIDTHPOINTS=595 -dDEVICEHEIGHTPOINTS=842 -dcupsBitsPerColor=8
> > -dcupsColorOrder=0 -dcupsColorSpace=4 -scupsPageSizeName=A4
> > -I/usr/share/cups/fonts -c '< > 3.00] /Margins[00]>>setpagedevice' -f -_ > out.ras
> 
> The problem is… This doesn't segfault. :-(

This bugreport seems to only really describe broken behaviour of c2esp.

Yes, it smells quite strongly of being _caused_ by some bug in 
ghostscript, but when only proven breakable in an environment created 
inside of c2esp, it seems more sensible to me that this bugreport is 
tied to c2esp rather than ghostscript.

@Didier: Since you reassigned this to (only) ghostscript, would you 
please consider re-reassigning to (only) c2esp instead?

Reason I ask is that ghostscript is now security-buggy in testing since 
a month, seemingly blocked only by this issue.  If reassigning does not 
seem sensible, then how about lowering severity (maybe only 
temporarily)?


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#944671: [Debian-med-packaging] Bug#944671: orthanc-dicomweb: missing build on armel

2019-11-14 Thread Sébastien Jodogne


Dear Ivo,

Please could you indicate where I can find information about how to 
remove the old armel build?


some info is here:

https://wiki.debian.org/ftpmaster_Removals

Note that you can close this bug once the removal is done (otherwise 
this bug would prevent migration to testing).


Thanks for your kind explanation!

As instructed on the page you sent, I have just introduced the related 
"RM: orthanc-dicomweb [armel]" bug to ask for the removal:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944732

Regards,
Sébastien-

Bug#838994: Bug#891493: unresolved gtk2-engines-murrine situation (was: numix-gtk-theme: Undocumented and very likely also broken Breaks against murrine-themes since 2.6.7-2)

2019-11-14 Thread Mike Gabriel


Hi Yves-Alexi,

On  Do 14 Nov 2019 08:03:57 CET, Yves-Alexis Perez wrote:


On Wed, 2019-11-13 at 20:58 +, Mike Gabriel wrote:

One last question: For the themes you maintain, is it ok if I provide
the "Provides: any-murrine-theme" patches (as MRs or pushed commits)
and possibly even NMU them for those murrine-like themes that need them?

Like in numix-gtk-theme [1].

Alternative option is me filing wishlist bugs against all related packages.


Go ahead with NMU, and yes I guess you can directly commit/push to the
repository. At that point I think I should just remove myself from
maintainers/uploaders of the theme packages, I'm unlikely to have time for
them in the near future.

Regards,
- --
Yves-Alexis


ok. Will do the NMUs. Let me know, if / when you remove yourself from  
Uploaders: / Maintainer: fields (I will probably miss it if not pinged  
explicitly).


Thanks+Greets,
Mike
--

DAS-NETZWERKTEAM
c\o Technik- und Ökologiezentrum Eckernförde
Mike Gabriel, Marienthaler str. 17, 24340 Eckernförde
mobile: +49 (1520) 1976 148
landline: +49 (4351) 850 8940

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgpWxGRT03qB5.pgp
Description: Digitale PGP-Signatur

Bug#944696: python-apt: relies on MD5 internally to download packages

2019-11-14 Thread AreYouLoco?

I am no expert but on my opinion a temporary fix would be to bring back MD5 for 
the time being and then fixing/extending python-apt functions to check for more 
secure sums like SHA* first and then if not found fallback to MD5.

But just for the backwards-compatibility since MD5 are know to be insecure and 
colissions are possible to find with decent hardware. Security issue as well?

On November 14, 2019 12:36:14 AM UTC, Cyril Brulebois  wrote:
>Package: python-apt
>Version: 1.8.4
>Severity: serious
>Justification: some people want to get rid of MD5Sum in indices
>
>Hi,
>
>While debugging a live-wrapper (lwr) failure that started occurring
>(literally) overnight, I ended up discovering it was triggered by the
>intel-microcode package's getting a security upgrade.
>
>live-wrapper 0.10 isn't affected, but live-wrapper's master branch has
>an extra commit that automatically enables security sources for stable
>releases.
>
>Here's the traceback for a simple build (with a local mirror but anyone
>would do) with that master branch:
>
>$ sudo lwr -d buster -m http://wodi.home/debian -f intel-microcode
>[…]
>DEBUG environment: LWR_MIRROR = 'http://wodi.home/debian'
>DEBUG environment: LWR_EXTRA_PACKAGES = ''
>DEBUG environment: LWR_BASE_DEBS = ''
>DEBUG environment: LWR_DISTRIBUTION = 'buster'
>DEBUG environment: LWR_FIRMWARE_PACKAGES = 'intel-microcode'
>DEBUG environment: LWR_TASK_PACKAGES = ''
>[…]
>Downloading udebs for Debian Installer...
>INFO Downloading udebs for Debian Installer...
>Updating a local cache for amd64 buster ...
>DEBUG Updating local cache...
>CRITICAL Traceback (most recent call last):
>File "/usr/lib/python2.7/dist-packages/cliapp/app.py", line 193, in
>_run
>self.process_args(args)
>File "/usr/lib/python2.7/dist-packages/lwr/run.py", line 143, in
>process_args
>self.start_ops()
>File "/usr/lib/python2.7/dist-packages/lwr/run.py", line 286, in
>start_ops
>apt_udeb.download_udebs(exclude_list)
>File "/usr/lib/python2.7/dist-packages/lwr/apt_udeb.py", line 157, in
>download_udebs
>self.download_apt_file(pkg_name, pool_dir, False)
>File "/usr/lib/python2.7/dist-packages/lwr/apt_udeb.py", line 141, in
>download_apt_file
>version.fetch_binary(destdir=pkg_dir)
>File "/usr/lib/python2.7/dist-packages/apt/package.py", line 867, in
>fetch_binary
>if _file_is_same(destfile, self.size, self._records.md5_hash):
>SystemError: error return without exception set
>
>
>After some debugging, it turned out that merely accessing the
>self._records.md5_hash item is sufficient to reproduce this issue.
>
>Looking at the current (as of 2019-11-14 00:27:00 UTC) indices for
>buster/updates on security.debian.org, one can only see SHA256 entries
>in Release and Packages files, which is likely the reason for
>python-apt's explosion. I've asked #debian-ftp to add MD5Sum entries
>back at least for buster/updates, and will file another bug report for
>that in a moment to make sure it isn't lost.
>
>Looking at even the most recent python-apt code in experimental
>(1.9.0),
>MD5 still seems hardwired, e.g. in apt/packages.py's fetch_binary():
>
>
>def fetch_binary(self, destdir='', progress=None):
># type: (str, AcquireProgress) -> str
>"""Fetch the binary version of the package.
>
> The parameter *destdir* specifies the directory where the package will
>be fetched to.
>
> The parameter *progress* may refer to an apt_pkg.AcquireProgress()
>  object. If not specified or None, apt.progress.text.AcquireProgress()
>is used.
>
>.. versionadded:: 0.7.10
>"""
>base = os.path.basename(self._records.filename)
>destfile = os.path.join(destdir, base)
>if _file_is_same(destfile, self.size, self._records.md5_hash):
> logging.debug('Ignoring already existing file: %s' % destfile)
>return os.path.abspath(destfile)
> acq = apt_pkg.Acquire(progress or apt.progress.text.AcquireProgress())
>acqfile = apt_pkg.AcquireFile(acq, self.uri, self._records.md5_hash,  #
>type: ignore # TODO: Do not use MD5 # nopep8
>self.size, base, destfile=destfile)
>acq.run()
>
>if acqfile.status != acqfile.STAT_DONE:
>raise FetchError("The item %r could not be fetched: %s" %
> (acqfile.destfile, acqfile.error_text))
>
>return os.path.abspath(destfile)
>
>
>Notice the TODO on the apt_pkg.AcquireFile(), but it would probably
>break in the same way as in the live-wrapper case a few lines before,
>on
>the self._records.md5_hash item.
>
>The same goes for fetch_source().
>
>
>Since getting rid of MD5Sum entirely is a topic that comes up on a
>regular fashion (with fingers being pointed at jigdo in particular), it
>looks to me python-apt should get some attention as well; hence filing
>at serious severity. Feel free to adjust as required.
>
>
>Cheers,
>-- 
>Cyril B

Bug#944739: fail2ban must not email start stop actions by default

2019-11-14 Thread sergio

Package: fail2ban
Version: 0.10.2-2.1
Severity: serious

Dear Maintainer,

fail2ban must not email start stop actions by default.

Bug#944726: systemd undefined symbol

2019-11-14 Thread Michael Biebl

Control: severity -1 normal

Am 14.11.19 um 13:22 schrieb Jan Sindelar:
> Package: systemd
> Version: 243-5
> Severity: critical
> Justification: breaks the whole system
> 
> Dear Maintainer,
> 
>* What led up to the situation?
> Installing latest systemd package using apt full-upgrade in testing
> 
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
>* What was the outcome of this action?
> Unbootable system
> 
>* What outcome did you expect instead?
> Normal boot

Downgrading to normal since I'm pretty sure this is not a general issue
but possibly something caused by a locally installed library.
Once we have failure message we can further investigate.

For the failing binary, please run
ldd /path/to/binary

and attach the output to this bug report.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#944726: systemd undefined symbol

Processing control commands:

> severity -1 normal
Bug #944726 [systemd] systemd undefined symbol
Severity set to 'normal' from 'critical'

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

Bug#944742: assimp: testsuite regression

2019-11-14 Thread Gianfranco Costamagna

Source: assimp
Version: 5.0.0~ds2-1
Severity: serious

Hello, looks like the autopkgtest is failing... Can you please have a look?

https://ci.debian.net/packages/a/assimp/
 [3 4 5]
 [3 5 6]]bash: line 1:  1849 Segmentation fault  
/tmp/autopkgtest-lxc.niblnjc6/downtmp/build.0PA/src/debian/tests/quicktest.py 
2> >(tee -a /tmp/autopkgtest-lxc.niblnjc6/downtmp/quicktest.py-stderr >&2) > 
>(tee -a /tmp/autopkgtest-lxc.niblnjc6/downtmp/quicktest.py-stdout)


Looks like it regressed some time ago, and now this should be considered RC 
buggy according to policy

thanks for having a look

G.

Bug#938691: trace-cmd: Python2 removal in sid/bullseye

2019-11-14 Thread Sandro Tosi

On Thu, 14 Nov 2019 07:21:42 + Sudip Mukherjee
 wrote:
> Hi All,
>
> On Fri, Aug 30, 2019 at 07:56:16AM +, Matthias Klose wrote:
> > Package: src:trace-cmd
> > Version: 2.6.1-0.1
> > Severity: normal
> > Tags: sid bullseye
> > User: debian-pyt...@lists.debian.org
> > Usertags: py2removal
>
> trace-cmd/2.8.3-1 is not using python anymore and so I have marked this
> as fixed, but it seems the updated version is not listed for:
> alpha, m68k, powerpcspe, sh4 and so I am not too sure if I should close
> this bug as fixed or leave it open.

please close, it's built on all release-architectures
https://buildd.debian.org/status/package.php?p=trace-cmd

Bug#944748: nftables: no init script

2019-11-14 Thread Thorsten Glaser

Package: nftables
Version: 0.9.0-2
Severity: serious
Justification: Policy 9.11

I’m trying to set up a simple firewall (just filter an exposed
servive so only select source IP addresses can use it) and was
told that nftables should be used for new setups.

While https://wiki.debian.org/nftables is a bit short on actual
helpful information, https://wiki.gentoo.org/wiki/Nftables has
more useful info, but incidentally, while Gentoo ships an init
script with nftables (one that can save and restore rules even)
Debian doesn’t.

This is a problem, as this way the firewall rules are not
reboot-safe (i.e. gone after rebooting) unless I add something
to /etc/rc.local or something.

However, nftables appears to ship a systemd unit, which is a
clear violation of Policy §9.11:
 “However, any package integrating with other init systems
must also be backwards-compatible with sysvinit by providing a SysV-
style init script with the same name as and equivalent functionality
to any init-specific job, as this is the only start-up configuration
method guaranteed to be supported by all init implementations.”

I checked latest version of Policy, and this is still there.
So please make a stable update adding an init script.

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

Kernel: Linux 4.19.0-6-amd64 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages nftables depends on:
ii  dpkg  1.19.7
ii  libc6 2.28-10
ii  libgmp10  2:6.1.2+dfsg-4
ii  libjansson4   2.12-1
ii  libnftables0  0.9.0-2
ii  libreadline7  7.0-5

nftables recommends no packages.

nftables suggests no packages.

-- no debconf information

Bug#944688: deal.ii ftbfs everywhere it build before during binNMU's for assimp 5.0.0

2019-11-14 Thread Adrian Bunk

On Wed, Nov 13, 2019 at 08:32:46PM +0100, Paul Gevers wrote:
>...
> Looking at the reproducible-builds infra, it seems your package started to
> FTBFS before this transition with the same error. Maybe this is related to the
> gcc-9 change?

Relevant part of the log:

...
-- Found TRILINOS_LIBRARY_trilinos_kokkosalgorithms
-- Found TRILINOS_LIBRARY_trilinos_kokkoscontainers
-- Found TRILINOS_LIBRARY_trilinos_kokkoscore
--   TRILINOS_VERSION: 12.14.1
--   TRILINOS_LIBRARIES: *** Required variable 
"TRILINOS_LIBRARY_trilinos_intrepid2" set to NOTFOUND ***
--   TRILINOS_INCLUDE_DIRS: 
/usr/include/trilinos;/usr/include/hdf5/openmpi;/usr/include;/usr/include/scotch
--   TRILINOS_USER_INCLUDE_DIRS: 
/usr/include/trilinos;/usr/include/hdf5/openmpi;/usr/include;/usr/include/scotch
--   TRILINOS_LINKER_FLAGS: 
-- Could NOT find TRILINOS
-- DEAL_II_WITH_TRILINOS has unmet external dependencies.
CMake Error at cmake/macros/macro_configure_feature.cmake:112 (MESSAGE):
...


So that's caused by the new trilinos.


> Paul

Bug#944748: nftables: no init script

2019-11-14 Thread Thorsten Glaser

Package: nftables
Version: 0.9.2-2
Followup-For: Bug #944748

This release-critical bug is also extant in sid.

-- System Information:
Debian Release: bullseye/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'buildd-unstable'), (500, 'unstable'), 
(100, 'experimental')
Architecture: x32 (x86_64)
Foreign Architectures: i386, amd64

Kernel: Linux 5.2.0-3-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages nftables depends on:
ii  dpkg  1.19.7
ii  libc6 2.29-3
ii  libnftables1  0.9.2-2
ii  libreadline8  8.0-3

nftables recommends no packages.

Versions of packages nftables suggests:
pn  firewalld  

-- no debconf information

Bug#944753: libglu FTBFS: src/libutil/error.c:60:10: error: ‘NULL’ undeclared here

2019-11-14 Thread Helmut Grohne

Source: libglu
Version: 9.0.0-2.1
Severity: serious
Tags: ftbfs

libglu fails to build from source:

| /bin/bash ./libtool  --tag=CC   --mode=compile gcc -DPACKAGE_NAME=\"glu\" 
-DPACKAGE_TARNAME=\"glu\" -DPACKAGE_VERSION=\"9.0.0\" -DPACKAGE_STRING=\"glu\ 
9.0.0\" 
-DPACKAGE_BUGREPORT=\"https://bugs.freedesktop.org/enter_bug.cgi\?product=Mesa\&component=GLU\";
 -DPACKAGE_URL=\"\" -DPACKAGE=\"glu\" -DVERSION=\"9.0.0\" -DSTDC_HEADERS=1 
-DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 
-DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 
-DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -I. -I..  
-DLIBRARYBUILD -I../include -I../src/include -I../src/libnurbs/internals 
-I../src/libnurbs/interface -I../src/libnurbs/nurbtess -Wdate-time 
-D_FORTIFY_SOURCE=2 -I/usr/include/libdrm  -Wall -fvisibility=hidden -g -O2 
-ffile-prefix-map=/build/1st/libglu-9.0.0=. -fstack-protector-strong -Wformat 
-Werror=format-security -DNDEBUG -c -o src/libutil/error.lo 
../src/libutil/error.c
| libtool: compile:  gcc -DPACKAGE_NAME=\"glu\" -DPACKAGE_TARNAME=\"glu\" 
-DPACKAGE_VERSION=\"9.0.0\" "-DPACKAGE_STRING=\"glu 9.0.0\"" 
"-DPACKAGE_BUGREPORT=\"https://bugs.freedesktop.org/enter_bug.cgi?product=Mesa&component=GLU\"";
 -DPACKAGE_URL=\"\" -DPACKAGE=\"glu\" -DVERSION=\"9.0.0\" -DSTDC_HEADERS=1 
-DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 
-DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 
-DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -I. -I.. 
-DLIBRARYBUILD -I../include -I../src/include -I../src/libnurbs/internals 
-I../src/libnurbs/interface -I../src/libnurbs/nurbtess -Wdate-time 
-D_FORTIFY_SOURCE=2 -I/usr/include/libdrm -Wall -fvisibility=hidden -g -O2 
-ffile-prefix-map=/build/1st/libglu-9.0.0=. -fstack-protector-strong -Wformat 
-Werror=format-security -DNDEBUG -c ../src/libutil/error.c  -fPIC -DPIC -o 
src/libutil/.libs/error.o
| ../src/libutil/error.c:60:10: error: 'NULL' undeclared here (not in a 
function)
|60 |{ ~0, NULL } /* end of list indicator */
|   |  ^~~~
| ../src/libutil/error.c:34:1: note: 'NULL' is defined in header ''; 
did you forget to '#include '?
|33 | #include 
|   +++ |+#include 
|34 |
| make[1]: *** [Makefile:1274: src/libutil/error.lo] Error 1
| make[1]: Leaving directory '/build/1st/libglu-9.0.0/build'
| dh_auto_build: cd build && make -j1 returned exit code 2
| make: *** [debian/rules:25: build] Error 255
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

This failure is reproduced by reproducible builds and crossqa:
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/libglu_9.0.0-2.1.rbuild.log.gz
http://crossqa.debian.net/build/libglu_9.0.0-2.1_armel_20191011150236.log

Helmut

Bug#944752: libdrm FTBFS on arm* due to dh_missing exynos_fimg2d_*

2019-11-14 Thread Helmut Grohne

Source: libdrm
Version: 2.4.100-3
Severity: serious
Tags: ftbfs

libdrm fails to build from source on buildds:

| dh_install --fail-missing
| dh_install: Please use dh_missing --list-missing/--fail-missing instead
| dh_install: This feature will be removed in compat 12.
| dh_missing: usr/bin/etnaviv_bo_cache_test exists in debian/tmp but is not 
installed to anywhere
| dh_missing: usr/bin/etnaviv_cmd_stream_test exists in debian/tmp but is not 
installed to anywhere
| dh_missing: usr/bin/etnaviv_2d_test exists in debian/tmp but is not installed 
to anywhere
| dh_missing: usr/bin/exynos_fimg2d_event exists in debian/tmp but is not 
installed to anywhere
| dh_missing: usr/bin/exynos_fimg2d_perf exists in debian/tmp but is not 
installed to anywhere
| dh_missing: missing files, aborting
|  The following debhelper tools have reported what they installed (with files 
per package)
|   * dh_install: libdrm-amdgpu1 (2), libdrm-common (1), libdrm-dev (35), 
libdrm-etnaviv1 (2), libdrm-exynos1 (2), libdrm-freedreno1 (2), libdrm-intel1 
(0), libdrm-nouveau2 (2), libdrm-omap1 (2), libdrm-radeon1 (2), libdrm-tegra0 
(2), libdrm-tests (6), libdrm2 (2), libdrm2-udeb (2)
|  If the missing files are installed by another tool, please file a bug 
against it.
|  When filing the report, if the tool is not part of debhelper itself, please 
reference the
|  "Logging helpers and dh_missing" section from the "PROGRAMMING" guide for 
debhelper (10.6.3+).
|(in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz)
|  Be sure to test with dpkg-buildpackage -A/-B as the results may vary when 
only a subset is built
|  For a short-term work-around: Add the files to debian/not-installed
| dh_install: dh_missing --fail-missing returned exit code 255
| make[1]: *** [debian/rules:98: override_dh_install] Error 255
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:125: binary-arch] Error 2
| dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess 
returned exit status 2

Helmut

Bug#944668: marked as done (mupen64plus-core: FTBFS against opencv 4.1: "No OpenCV development libraries found!" during debian/rules clean)

Your message dated Thu, 14 Nov 2019 20:49:33 +
with message-id 
and subject line Bug#944668: fixed in mupen64plus-core 2.5.9-2
has caused the Debian Bug report #944668,
regarding mupen64plus-core: FTBFS against opencv 4.1: "No OpenCV development 
libraries found!" during debian/rules clean
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.)


-- 
944668: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944668
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mupen64plus-core
Version: 2.5.9-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + libmupen64plus2

mupen64plus-core/experimental FTBFS against opencv 4.1 which is now in
sid:

 fakeroot debian/rules clean
dh clean --sourcedirectory="projects/unix"
   debian/rules override_dh_auto_clean
make[1]: Entering directory '/build/mupen64plus-core-2.5.9'
dh_auto_clean -- V=1 UNAME='linux' HOST_CPU='x86_64' 
APIDIR=/usr/include/mupen64plus/ DEBUG=1 DEBUGGER=1 PREFIX=/usr/ 
LIBDIR="/usr/lib/x86_64-linux-gnu" PIC=1 OPTFLAGS="-DNDEBUG" 
SHAREDIR="/usr/share/games/mupen64plus/" SDL_CONFIG=sdl2-config OPENCV=1
cd projects/unix && make -j16 distclean V=1 UNAME=linux HOST_CPU=x86_64 
APIDIR=/usr/include/mupen64plus/ DEBUG=1 DEBUGGER=1 PREFIX=/usr/ 
LIBDIR=/usr/lib/x86_64-linux-gnu PIC=1 OPTFLAGS=-DNDEBUG 
SHAREDIR=/usr/share/games/mupen64plus/ SDL_CONFIG=sdl2-config OPENCV=1
make[2]: Entering directory '/build/mupen64plus-core-2.5.9/projects/unix'
Makefile:305: *** No OpenCV development libraries found!.  Stop.
make[2]: Leaving directory '/build/mupen64plus-core-2.5.9/projects/unix'
dh_auto_clean: cd projects/unix && make -j16 distclean V=1 UNAME=linux 
HOST_CPU=x86_64 APIDIR=/usr/include/mupen64plus/ DEBUG=1 DEBUGGER=1 
PREFIX=/usr/ LIBDIR=/usr/lib/x86_64-linux-gnu PIC=1 OPTFLAGS=-DNDEBUG 
SHAREDIR=/usr/share/games/mupen64plus/ SDL_CONFIG=sdl2-config OPENCV=1 returned 
exit code 2
make[1]: *** [debian/rules:30: override_dh_auto_clean] Error 255
make[1]: Leaving directory '/build/mupen64plus-core-2.5.9'
make: *** [debian/rules:24: clean] Error 2
dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit 
status 2


Andreas
--- End Message ---
--- Begin Message ---
Source: mupen64plus-core
Source-Version: 2.5.9-2

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

Debian distribution maintenance software
pp.
Sven Eckelmann  (supplier of updated mupen64plus-core 
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, 14 Nov 2019 21:11:53 +0100
Source: mupen64plus-core
Architecture: source
Version: 2.5.9-2
Distribution: experimental
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Sven Eckelmann 
Closes: 944668
Changes:
 mupen64plus-core (2.5.9-2) experimental; urgency=medium
 .
   * Upgraded to policy 4.4.1, no changes required
   * debian/patches:
 - Add Build-against-libopencv4.patch, Fix FTBFS against libopencv >= 4
   (Closes: #944668)
   * debian/control:
 - Allow build without (fake)root
Checksums-Sha1:
 694a30e60ff8b3d2e2bd3d26965dea71d704a23f 2773 mupen64plus-core_2.5.9-2.dsc
 3725b87183fc1a06d32cc132537e167630ce8e0c 21552 
mupen64plus-core_2.5.9-2.debian.tar.xz
 0a539fe35cf0c2528c565b573d13ab838df2e419 19340 
mupen64plus-core_2.5.9-2_source.buildinfo
Checksums-Sha256:
 509591d5fc1b0cc3039d99cce2c6451f5fd364a8d6f9a6a0bc6ed76cd01e71b3 2773 
mupen64plus-core_2.5.9-2.dsc
 780ac03eabec11607f716029dff92ccc90706fee22c615ba6ebc84c4237b73bb 21552 
mupen64plus-core_2.5.9-2.debian.tar.xz
 89cd3bbbcc9548aec8534e75061bb53c38f10cf83e0afd81fdcc2dcb713cf2e1 19340 
mupen64plus-core_2.5.9-2_source.buildinfo
Files:
 bada9ffd013c357d21efccb8224e8e37 2773 games optional 
mupen64plus-core_2.5.9-2.dsc
 1365bc15e7bb2f4aca9caecae5bc15ff 21552 games optional 
mupen64plus-core_2.5.9-2.debian.tar.xz
 963e62ce702d181512b09133e122c13f 19340 games optional 
mupen64plus-core_2.5.9-2_source.buildinfo

-

Bug#885529: marked as done (trace-cmd: Build-Depends on unmaintained pygtk)

Your message dated Thu, 14 Nov 2019 21:30:36 +
with message-id <20191114213036.wha6us5eqhtm2c4r@debian>
and subject line Re: trace-cmd: Build-Depends on unmaintained pygtk
has caused the Debian Bug report #885529,
regarding trace-cmd: Build-Depends on unmaintained pygtk
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.)


-- 
885529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885529
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: trace-cmd
Version: 2.6.1-0.1
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings (and gtk3).

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

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

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

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Version: trace-cmd/2.8.3-1

This new version of trace-cmd doesnot use pygtk anymore.

--
Regards
Sudip


signature.asc
Description: PGP signature
--- End Message ---

Bug#938691: marked as done (trace-cmd: Python2 removal in sid/bullseye)

Your message dated Thu, 14 Nov 2019 21:33:45 +
with message-id <20191114213345.wgsvbi6zbsso4asq@debian>
and subject line Re: trace-cmd: Python2 removal in sid/bullseye
has caused the Debian Bug report #938691,
regarding trace-cmd: Python2 removal in sid/bullseye
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.)


-- 
938691: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938691
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:trace-cmd
Version: 2.6.1-0.1
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:trace-cmd

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Version: trace-cmd/2.8.3-1

This new version of trace-cmd is not using python.

--
Regards
Sudip


signature.asc
Description: PGP signature
--- End Message ---

Bug#939101: marked as done (elogind: elogind 239 in bullseye FTBFS with gcc-9)

Your message dated Thu, 14 Nov 2019 21:00:23 +
with message-id <20191114210022.gb3...@hindley.org.uk>
and subject line Re: elogind: elogind 239 in bullseye FTBFS with gcc-9
has caused the Debian Bug report #939101,
regarding elogind: elogind 239 in bullseye FTBFS with gcc-9
to be marked as done.

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

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


-- 
939101: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939101
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: elogind
Version: 239.3+20190131-1+debian1
Severity: serious
Control: fixed -1 241.3-1+debian1
Control: block -1 by 934132

Reproducible builds of src:elogind 239.3+20190131-1+debian1 in bullseye
have FTBFS for the last few days. This seems to be related to the
migration of gcc-9 to bullseye.

The issue appears to be the STRING_FOREACH macro and was fixed in
systemd in v241:

 https://github.com/systemd/systemd/issues/11394
 https://bugzilla.opensuse.org/show_bug.cgi?id=1121387#c0

This fix is already included in elogind 241.3-1+debian1 which is in
unstable. However, migration of elogind 241.3-1+debian1 to bullseye is
currently blocked (see #934132). When it is unblocked it should resolve
this issue.

Mark
--- End Message ---
--- Begin Message ---
elogind/241.3-1+debian1 is now in bullseye so this is no longer an issue.

Closing.

Mark--- End Message ---

Processed: ghostscript: CVE-2019-14869

Processing control commands:

> found -1 9.26a~dfsg-0+deb9u5
Bug #944760 [src:ghostscript] ghostscript: CVE-2019-14869
Marked as found in versions ghostscript/9.26a~dfsg-0+deb9u5.
> found -1 9.26a~dfsg-0+deb9u1
Bug #944760 [src:ghostscript] ghostscript: CVE-2019-14869
Marked as found in versions ghostscript/9.26a~dfsg-0+deb9u1.
> found -1 9.27~dfsg-2+deb10u2
Bug #944760 [src:ghostscript] ghostscript: CVE-2019-14869
Marked as found in versions ghostscript/9.27~dfsg-2+deb10u2.
> found -1 9.27~dfsg-1
Bug #944760 [src:ghostscript] ghostscript: CVE-2019-14869
Marked as found in versions ghostscript/9.27~dfsg-1.
> found -1 9.27~dfsg-3.1
Bug #944760 [src:ghostscript] ghostscript: CVE-2019-14869
Marked as found in versions ghostscript/9.27~dfsg-3.1.
> fixed -1 9.26a~dfsg-0+deb9u6
Bug #944760 [src:ghostscript] ghostscript: CVE-2019-14869
The source 'ghostscript' and version '9.26a~dfsg-0+deb9u6' do not appear to 
match any binary packages
Marked as fixed in versions ghostscript/9.26a~dfsg-0+deb9u6.
> fixed -1 9.27~dfsg-2+deb10u3
Bug #944760 [src:ghostscript] ghostscript: CVE-2019-14869
The source 'ghostscript' and version '9.27~dfsg-2+deb10u3' do not appear to 
match any binary packages
Marked as fixed in versions ghostscript/9.27~dfsg-2+deb10u3.

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

Bug#944760: ghostscript: CVE-2019-14869

2019-11-14 Thread Salvatore Bonaccorso

Source: ghostscript
Version: 9.50~dfsg-2
Severity: grave
Tags: security upstream
Control: found -1 9.26a~dfsg-0+deb9u5
Control: found -1 9.26a~dfsg-0+deb9u1
Control: found -1 9.27~dfsg-2+deb10u2
Control: found -1 9.27~dfsg-1
Control: found -1 9.27~dfsg-3.1
Control: fixed -1 9.26a~dfsg-0+deb9u6
Control: fixed -1 9.27~dfsg-2+deb10u3

Hi,

The following vulnerability was published for ghostscript. I can agree
the severity is not exaclty matching, as for 9.50 itself, it's not
anymore directly exploitable (unless with -dOLDSAFER). Still it cannot
be considred fixed, only after applying [1].

CVE-2019-14869[0]:
|-dSAFER escape in .charkeys

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2019-14869
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14869
[1] 
https://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=485904772c5f0aa1140032746e5a0abf
[2] https://bugs.ghostscript.com/show_bug.cgi?id=701841

Regards,
Salvatore

Bug#944258: lintian 2.32.0~bpo9+1 in stretch-backports depends on coreutils (>= 8.30), but stretch has only 8.26-3

2019-11-14 Thread Chris Lamb

Chris Lamb wrote:

> > Or, do I need to backport the patch to that specific version?
> 
> If you mean backport it to that particular branch... then no; we just
> need to do a regular backport upload. I do that after its migrated to
> testing to follow the rules, so we are a few days off this landing in
> stretch alas. (As in; I need to do an unstable upload first that
> includes this commit and let that migrate...)

2.35.0~bpo9+1 and 2.35.0~bpo10+1 uploaded to {stretch,buster}-backports
respectfully.


Regards,

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

Bug#885305: marked as done (hijra: Depends on unmaintained pygtk)

Your message dated Thu, 14 Nov 2019 22:00:12 +
with message-id 
and subject line Bug#885305: fixed in hijra 0.4.1-2
has caused the Debian Bug report #885305,
regarding hijra: Depends on unmaintained pygtk
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.)


-- 
885305: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885305
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hijra
Version: 0.4.1-1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

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

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

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

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

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: hijra
Source-Version: 0.4.1-2

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

Debian distribution maintenance software
pp.
أحمد المحمودي (Ahmed El-Mahmoudy)  (supplier 
of updated hijra 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, 03 Nov 2019 05:08:36 +0100
Source: hijra
Binary: gnome-shell-extension-hijra hijra-applet python3-hijra
Architecture: source all
Version: 0.4.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Islamic Maintainers 

Changed-By: أحمد المحمودي (Ahmed El-Mahmoudy) 

Description:
 gnome-shell-extension-hijra - Hijri Islamic Calendar GNOME shell extension
 hijra-applet - Hijri Islamic Calendar tray applet
 python3-hijra - Hijri Islamic Calendar converting functions for Python
Closes: 802512 885305 936703
Changes:
 hijra (0.4.1-2) unstable; urgency=medium
 .
   * Split GNOME shell extension into a separate package (Closes: #802512)
   * Migrate to Python 3 (Closes: #936703)
 + Added py3.diff patch to migrate to Python 3
   * Bumped to compat level 12
   * d/control:
 + Update Vcs-* fields
 + Add dh-python to build-deps
 + Use Breaks instead of Conflicts
 + Update to standards version 4.4.0
 + Replaced python-gtk dependency with python3-gi (Closes: #885305)
 + Update standards version to 4.4.1
 + Add Rules-Requires-Root: no
 + Add XS-Autobuild: yes
   * d/copyright:
 + Switch to secure copyright format URI
 + Add explanation for non-free package
 + Update copyright years
 + Switch to WPL-2 license
   * Add upstream metadata
   * Update homepage URL
Checksums-Sha1:
 c308541279a38a2a7bddaa13d3e4e103932ccf0c 2239 hijra_0.4.1-2.dsc
 aed7734987b8683e5888209579b3292150444c25 13820 hijra_0.4.1-2.debian.tar.xz
 b841299e20124e4d28c21808520b723beb392706 1920 
gnome-shell-extension-hijra_0.4.1-2_all.deb
 7e3203f041b23cdbf50aa6b307b5f432201c3e39 12780 hijra-applet_0.4.1-2_all.deb
 c71dbafe182f422fd3359fd1daf16cf860792eb1 6781 hijra_0.4.1-2_amd64.buildinfo
 b687b71cd50bb3b423d560b06450455275ef9ace 20736 python3-hijra_0.4.1-2_all.deb
Checksums-Sha256:
 b4e2b0356b4ab4fdcf254f604fd50a13b0ec07b09f0268874f458c692cfc5403 2239 
hijra_0.4.1-2.dsc
 a257916c9b5e166ba0ce78c5c9c1a17e6cc94907253dd2c6d03471c1f3aaecf6 13820 
hijra_0.4.1-2.debian.tar.xz
 885498b03b2bd2e08548c82d76a1dfbdaebb51828bffbb55dc780d12da9cd495 1920 
gnome-shell-extension-hijra_0.4.1-2_all.deb
 cb29729cea3714dab5e198b424ab6f56b6d64d9d997db1b587cb246b6bd5c7fd 12780 
hijra-applet_0.4.1-2_all.deb
 e3eceff710a833786175a67a3d71bc6f9b232718322e37c276938f576c0921af 6781 
hijra_0.4.1-2_amd64.buildinfo
 89dd225db3031f9f068e287afcc498b24ed7c67613cc0e62aa86d29a58f4362c 20736 
python3-hijra_0.4.1-2_all.deb
Files:
 debe11b3701989ba52b1f3ed4275f4e1 2239 non-free/misc optional hijra_0.4.1-2.dsc
 b706092f8c2713fadfc629b9c6d47c8d 13820 non-free/misc optional 
hijra_0.4.1-2.debian.tar.xz
 65d9d6fda290eea3c6aed1e6

Bug#906578: [makehuman] Future Qt4 removal

2019-11-14 Thread Moritz Mühlenhoff

On Sun, Oct 13, 2019 at 02:56:00PM -0400, Boyuan Yang wrote:
> Looks like makehuman upstream is working on the Qt5 version but it hasn't
> finished yet. There's only alpha versions at 
> https://github.com/makehumancommunity/makehuman . I guess we should move on
> and have it removed if upstream is acting that slowly.
> 
> Muammar: if you have any other thoughts, please let us know now.

No reply in a month, I've filed a removal bug now. If it gets ported to Qt5
it can still be re-introduced for Bullseye.

Cheers,
Moritz

Bug#942235: dask: autopkgtest needs update for new version of pytest

2019-11-14 Thread Rebecca N. Palmer

Ubuntu have dask 2.6.0 and fsspec, but still have a few autopkgtest 
failures:


https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html

dask itself - looks like trying to use a nonexistent temporary directory
pyfftw - looks like a test treating a new (unexpected) warning as a failure
satpy - looks like a missing dependency on fsspec

Bug#943972: marked as done (akonadi-backend-sqlite: expermental version impossible to install due to old qt dependency)

Your message dated Thu, 14 Nov 2019 23:19:38 +
with message-id 
and subject line Bug#943972: fixed in akonadi 4:18.08.3-11
has caused the Debian Bug report #943972,
regarding akonadi-backend-sqlite: expermental version impossible to install due 
to old qt dependency
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.)


-- 
943972: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943972
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: akonadi-backend-sqlite
Version: 4:18.08.3-10
Severity: grave
Justification: renders package unusable

apt-get -t experimental install akonadi-backend-sqlite
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances   
Lecture des informations d'état... Fait
Certains paquets ne peuvent être installés. Ceci peut signifier
que vous avez demandé l'impossible, ou bien, si vous utilisez
la distribution unstable, que certains paquets n'ont pas encore
été créés ou ne sont pas sortis d'Incoming.
L'information suivante devrait vous aider à résoudre la situation : 

Les paquets suivants contiennent des dépendances non satisfaites :
 akonadi-backend-sqlite : Dépend: qtbase-abi-5-11-3 mais il n'est pas 
installable



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

Kernel: Linux 4.19.81 (SMP w/2 CPU cores; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE= 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages akonadi-backend-sqlite depends on:
ii  libc6 2.29-3
ii  libgcc1   1:9.2.1-16
ii  libqt5core5a [qtbase-abi-5-12-5]  5.12.5+dfsg-2
ii  libqt5sql55.12.5+dfsg-2
ii  libqt5sql5-sqlite 5.12.5+dfsg-2
ii  libsqlite3-0  3.30.1-1
ii  libstdc++69.2.1-16

Versions of packages akonadi-backend-sqlite recommends:
ii  akonadi-server  4:18.08.3-7+b1

akonadi-backend-sqlite suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: akonadi
Source-Version: 4:18.08.3-11

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

Debian distribution maintenance software
pp.
Sandro Knauß  (supplier of updated akonadi 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, 14 Nov 2019 23:48:16 +0100
Source: akonadi
Architecture: source
Version: 4:18.08.3-11
Distribution: unstable
Urgency: medium
Maintainer: Debian/Kubuntu Qt/KDE Maintainers 
Changed-By: Sandro Knauß 
Closes: 943972
Changes:
 akonadi (4:18.08.3-11) unstable; urgency=medium
 .
   [ Sandro Knauß ]
   * Fix "expermental version impossible to install due to old qt
 dependency" (Closes: #943972)
Checksums-Sha1:
 6152304ee46c7f94187c5945fd77acd704170b37 4057 akonadi_18.08.3-11.dsc
 b0a73e1193ca03046a2d263eb315a9ea76b4229f 43928 akonadi_18.08.3-11.debian.tar.xz
 293d23b3022c47ddb6f8079a5c3887c68830fbf9 19293 
akonadi_18.08.3-11_source.buildinfo
Checksums-Sha256:
 9cb5c6208274ce77fac952eb9ec53993981c102dbfee4a84f196321a0ef3b4ff 4057 
akonadi_18.08.3-11.dsc
 ddcdf450efb7aaad0bfac441a92e4965678285943357f26ebea8dd66a4e162a7 43928 
akonadi_18.08.3-11.debian.tar.xz
 7ab5d29c6a641ff6afa212ddb7f4543a6a88ab8f693ef9c73fd7c644409d5b00 19293 
akonadi_18.08.3-11_source.buildinfo
Files:
 7f467e3374b89f8d0d7f1d956b8d4fab 4057 libs optional akonadi_18.08.3-11.dsc
 9c88bb665e724b82d7444820048db0f2 43928 libs optional 
akonadi_18.08.3-11.debian.tar.xz
 02df9ced5dd14b6f72e16468c265c972 19293 libs optional 
akonadi_18.08.3-11_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEOewRoCAWtykmSRoG462wCFBgVjYFAl3N2/gRHGhlZmVlQGRl
Ymlhbi5vcmcACgkQ462wCFBgVjZECA//WEoJR67E5wQZOchxgnlx+7O5B9voK6E8
P/VfNozg0ystKwhQGH0Jk6w66F4BLSRoH3MhuU2SDETEOR3mYktfldsZpj99A52A
w2kk859qMqCYyrQv64yS3QPkmATwPehNiaUtE/nl8xjNthjJ1hI4me

Bug#934843: parsedatetime: FTBFS in stretch

2019-11-14 Thread Harlan Lieberman-Berg

tag 934843 +unreproducible
thanks

On Thu, 15 Aug 2019 19:12:49 + Santiago Vila  wrote:
> I tried to build this package in stretch but it failed:

Hello!

This is quite strange.  I've tried rebuilding it several times in my
stretch sbuild, and it worked every time without error.  I also
re-triggered the build on reproducible-builds, and it's now clean
there as well.

One possibility that comes to mind is locales -- what locales are you
compiling under? It's possible there's a bug in one of the
locale-specific parsers that's not getting exercised on my sbuild,
through, I admit to not being sure how reproducible-builds could have
been affected by the same thing.  Otherwise, maybe a difference in one
of the deps that was fixed in the last... day?

Sincerely,
-- 
Harlan Lieberman-Berg
~hlieberman

Processed: Re: parsedatetime: FTBFS in stretch

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

> tag 934843 +unreproducible
Bug #934843 [src:parsedatetime] parsedatetime: FTBFS in stretch
Added tag(s) unreproducible.
> thanks
Stopping processing here.

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

Bug#885529: bumping severity of pygtk bugs

On Wed, Nov 13, 2019 at 3:08 PM Sudip Mukherjee
 wrote:
> trace-cmd/2.8.3-1 is fixing this as it now uses qt and not pygtk. But
> I am not sure if I should close this bug now or wait for you to verify
> and close it.

Yes, it was fine that you closed this bug.

It looks like trace-cmd still uses Python2 which is (or soon will be)
a Release Critical bug for Bullseye also.

Thanks,
Jeremy Bicha

Bug#944766: design-desktop: Stop depending on volti

Package: design-desktop
Version: 3.0.15
Severity: serious
Tags: bullseye sid

design-desktop depends on volti. Because volti is unmaintained with
low popcorn and depends on pygtk and Python2, volti will likely be
removed from Debian soon. Please remove the dependency so that volti
can be removed smoothly.

Thanks,
Jeremy Bicha

Bug#944767: python3-hijra: uninstallable

Source: hijra
Version: 0.4.1-2
X-Debbugs-CC: aelmahmo...@users.sourceforge.net
Severity: grave


python3-hijra is uninstallable:

Setting up python3-hijra (0.4.1-2) ...
Sorry: TabError: inconsistent use of tabs and spaces in indentation
(HijriCal.py, line 83)
dpkg: error processing package python3-hijra (--configure):
 installed python3-hijra package post-installation script subprocess
returned error exit status 1
dpkg: dependency problems prevent configuration of hijra-applet:
 hijra-applet depends on python3-hijra (= 0.4.1-2); however:
  Package python3-hijra is not configured yet.


See the mention of line 83 in the log excerpt I posted.

Thanks,
Jeremy Bicha

Bug#944768: gnome-shell-extension-hijra: Uninstallable

Source: hijra
Version: 0.4.1-2
X-Debugs-CC: aelmahmo...@users.sourceforge.net
Severity: serious

gnome-shell-extension-hijra depends on gnome-shell (<< 3.31) but
Debian Testing has gnome-shell 3.34.

The extension looks simple enough that I think you could probably drop
the upper dependency limit to avoid this issue every 6 months when we
package a new gnome-shell version. I was unable to test this extension
because of https://bugs.debian.org/944767

Thanks,
Jeremy Bicha

Bug#944769: python3-h5py fails to import if offline due to apparent MPI failure

2019-11-14 Thread Jameson Graef Rollins

Package: python3-h5py
Version: 2.10.0-2
Severity: serious

The latest version of h5py compiled against MPI completely fails to
import if there is no network connection:

servo:~ 0$ python3 -c 'import h5py; print("foo")'
--
No network interfaces were found for out-of-band communications. We require
at least one available network for out-of-band messaging.
--
[servo:32114] [[INVALID],INVALID] ORTE_ERROR_LOG: Unable to start a daemon on 
the local node in file ess_singleton_module.c at line 532
[servo:32114] [[INVALID],INVALID] ORTE_ERROR_LOG: Unable to start a daemon on 
the local node in file ess_singleton_module.c at line 166
--
It looks like orte_init failed for some reason; your parallel process is
likely to abort.  There are many reasons that a parallel process can
fail during orte_init; some of which are due to configuration or
environment problems.  This failure appears to be an internal failure;
here's some additional information (which may only be relevant to an
Open MPI developer):

  orte_ess_init failed
--> Returned value Unable to start a daemon on the local node (-127) 
instead of ORTE_SUCCESS
--
--
It looks like MPI_INIT failed for some reason; your parallel process is
likely to abort.  There are many reasons that a parallel process can
fail during MPI_INIT; some of which are due to configuration or environment
problems.  This failure appears to be an internal failure; here's some
additional information (which may only be relevant to an Open MPI
developer):

  ompi_mpi_init: ompi_rte_init failed
--> Returned "Unable to start a daemon on the local node" (-127) instead of 
"Success" (0)
--
*** An error occurred in MPI_Init_thread
*** on a NULL communicator
*** MPI_ERRORS_ARE_FATAL (processes in this communicator will now abort,
***and potentially your MPI job)
[servo:32114] Local abort before MPI_INIT completed completed successfully, but 
am not able to aggregate error messages, and not able to guarantee that all 
other processes were killed!
servo:~ 1$

Note the return code and that the print command was not executed.  The
import actually caused python to crash without throwing an exception.
This is obviously unacceptable and very major usability issue.

As mention in other similar reports, please drop the MPI support in
the default build!

jamie.


-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (600, 'testing'), (500, 'stable'), (200, 'unstable'), (101, 
'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages python3-h5py depends on:
ii  libc6   2.29-3
ii  libhdf5-openmpi-103 1.10.4+repack-10
ii  python3 3.7.5-1
ii  python3-mpi4py  3.0.2-13
ii  python3-numpy [python3-numpy-abi9]  1:1.16.5-1
ii  python3-six 1.12.0-2

python3-h5py recommends no packages.

Versions of packages python3-h5py suggests:
pn  python-h5py-doc  

-- no debconf information

Bug#944753: marked as done (libglu FTBFS: src/libutil/error.c:60:10: error: ‘NULL’ undeclared here)

Your message dated Fri, 15 Nov 2019 06:05:59 +
with message-id 
and subject line Bug#944753: fixed in libglu 9.0.1-1
has caused the Debian Bug report #944753,
regarding libglu FTBFS: src/libutil/error.c:60:10: error: ‘NULL’ undeclared here
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.)


-- 
944753: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944753
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libglu
Version: 9.0.0-2.1
Severity: serious
Tags: ftbfs

libglu fails to build from source:

| /bin/bash ./libtool  --tag=CC   --mode=compile gcc -DPACKAGE_NAME=\"glu\" 
-DPACKAGE_TARNAME=\"glu\" -DPACKAGE_VERSION=\"9.0.0\" -DPACKAGE_STRING=\"glu\ 
9.0.0\" 
-DPACKAGE_BUGREPORT=\"https://bugs.freedesktop.org/enter_bug.cgi\?product=Mesa\&component=GLU\";
 -DPACKAGE_URL=\"\" -DPACKAGE=\"glu\" -DVERSION=\"9.0.0\" -DSTDC_HEADERS=1 
-DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 
-DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 
-DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -I. -I..  
-DLIBRARYBUILD -I../include -I../src/include -I../src/libnurbs/internals 
-I../src/libnurbs/interface -I../src/libnurbs/nurbtess -Wdate-time 
-D_FORTIFY_SOURCE=2 -I/usr/include/libdrm  -Wall -fvisibility=hidden -g -O2 
-ffile-prefix-map=/build/1st/libglu-9.0.0=. -fstack-protector-strong -Wformat 
-Werror=format-security -DNDEBUG -c -o src/libutil/error.lo 
../src/libutil/error.c
| libtool: compile:  gcc -DPACKAGE_NAME=\"glu\" -DPACKAGE_TARNAME=\"glu\" 
-DPACKAGE_VERSION=\"9.0.0\" "-DPACKAGE_STRING=\"glu 9.0.0\"" 
"-DPACKAGE_BUGREPORT=\"https://bugs.freedesktop.org/enter_bug.cgi?product=Mesa&component=GLU\"";
 -DPACKAGE_URL=\"\" -DPACKAGE=\"glu\" -DVERSION=\"9.0.0\" -DSTDC_HEADERS=1 
-DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 
-DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 
-DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -I. -I.. 
-DLIBRARYBUILD -I../include -I../src/include -I../src/libnurbs/internals 
-I../src/libnurbs/interface -I../src/libnurbs/nurbtess -Wdate-time 
-D_FORTIFY_SOURCE=2 -I/usr/include/libdrm -Wall -fvisibility=hidden -g -O2 
-ffile-prefix-map=/build/1st/libglu-9.0.0=. -fstack-protector-strong -Wformat 
-Werror=format-security -DNDEBUG -c ../src/libutil/error.c  -fPIC -DPIC -o 
src/libutil/.libs/error.o
| ../src/libutil/error.c:60:10: error: 'NULL' undeclared here (not in a 
function)
|60 |{ ~0, NULL } /* end of list indicator */
|   |  ^~~~
| ../src/libutil/error.c:34:1: note: 'NULL' is defined in header ''; 
did you forget to '#include '?
|33 | #include 
|   +++ |+#include 
|34 |
| make[1]: *** [Makefile:1274: src/libutil/error.lo] Error 1
| make[1]: Leaving directory '/build/1st/libglu-9.0.0/build'
| dh_auto_build: cd build && make -j1 returned exit code 2
| make: *** [debian/rules:25: build] Error 255
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

This failure is reproduced by reproducible builds and crossqa:
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/libglu_9.0.0-2.1.rbuild.log.gz
http://crossqa.debian.net/build/libglu_9.0.0-2.1_armel_20191011150236.log

Helmut
--- End Message ---
--- Begin Message ---
Source: libglu
Source-Version: 9.0.1-1

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

Debian distribution maintenance software
pp.
Timo Aaltonen  (supplier of updated libglu 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: Fri, 15 Nov 2019 07:45:36 +0200
Source: libglu
Architecture: source
Version: 9.0.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian X Strike Force 
Changed-By: Timo Aaltonen 
Closes: 944753
Changes:
 libglu (9.0.1-1) unstable; urgency=medium
 .
   * New upstream release. (Closes: #944753)
   * Use dh 12, drop dh_autoreconf from build-deps, override dh_missing.
   * control: Update VCS urls.
   * control: Bump policy to 4.4.1.
   * control: Drop Cyril f

Bug#885529: bumping severity of pygtk bugs

2019-11-14 Thread Sudip Mukherjee

Hi Jeremy,

On Thu, Nov 14, 2019 at 07:40:41PM -0500, Jeremy Bicha wrote:
> On Wed, Nov 13, 2019 at 3:08 PM Sudip Mukherjee
>  wrote:
> > trace-cmd/2.8.3-1 is fixing this as it now uses qt and not pygtk. But
> > I am not sure if I should close this bug now or wait for you to verify
> > and close it.
> 
> Yes, it was fine that you closed this bug.

Thanks for your reply. I closed it based on reply from "Sandro Tosi" in
#938691.

> 
> It looks like trace-cmd still uses Python2 which is (or soon will be)
> a Release Critical bug for Bullseye also.

I am confused by that. If you see https://packages.debian.org/sid/trace-cmd
it shows that it depends of python only for alpha, m68k, powerpcspe, sh4
and if you see the download table on that same page, it shows that those
arch (unofficial port) are still using the old version - 2.6.1-0.1 and
not this new version.
So, I guess, the implication of python2 removal will be that the old
version of trace-cmd will be removed from these arch.
Am I correct in my understanding? Please correct me if I am wrong.

--
Regards
Sudip

Bug#885379: marked as done (liblarch: Depends on unmaintained pygtk)

Your message dated Fri, 15 Nov 2019 07:34:56 +
with message-id 
and subject line Bug#944568: Removed package(s) from unstable
has caused the Debian Bug report #885379,
regarding liblarch: Depends on unmaintained pygtk
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.)


-- 
885379: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885379
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: liblarch
Version: 2.1.0-4
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings (and gtk3).

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

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

It looks like all you need to do here is upload liblarch 3.0 from
experimental to unstable.

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

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Version: 2.1.0-4+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#944769: python3-h5py fails to import if offline due to apparent MPI failure

2019-11-14 Thread Drew Parsons

Package: python3-h5py
Version: 2.10.0-2
Followup-For: Bug #944769
Control: severity -1 important

I don't think this issue warrants severity Serious.

The failure is not triggered simply by having no network connection.
It is only triggered if there is no network interface at all. The only
way there can be no network interface is if the localhost loopback
interface lo has been taken down.  This is a very artificial situation
I think.

Ensure that the loopback interface is active with
  ifup lo


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

Kernel: Linux 5.3.0-2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_AU:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python3-h5py depends on:
ii  libc6   2.29-3
ii  libhdf5-openmpi-103 1.10.4+repack-10
ii  python3 3.7.5-3
ii  python3-mpi4py  3.0.3-1
ii  python3-numpy [python3-numpy-abi9]  1:1.17.4-1
ii  python3-six 1.13.0-1

python3-h5py recommends no packages.

Versions of packages python3-h5py suggests:
ii  python-h5py-doc  2.10.0-2

-- no debconf information

Processed: Re: python3-h5py fails to import if offline due to apparent MPI failure

Processing control commands:

> severity -1 important
Bug #944769 [python3-h5py] python3-h5py fails to import if offline due to 
apparent MPI failure
Severity set to 'important' from 'serious'

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

Bug#864012: marked as done (lepton: Upstream requires sse4.1 in Intel platform which is not available in all build machines)

Your message dated Fri, 15 Nov 2019 07:34:03 +
with message-id
and subject line Bug#941799: Removed package(s) from unstable
has caused the Debian Bug report #864012,
regarding lepton: Upstream requires sse4.1 in Intel platform which is not
available in all build machines
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.)

--
864012: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864012
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lepton
Version: 1.2.1+20170405-3
Severity: normal

lepton requires sse4.1 to build with vectorization. However, not all
build machines (ex: binet) support sse4.1. If lepton is built in these
build machines, test cases will fail due to "Illegal instruction" [0].

[0]
https://buildd.debian.org/status/fetch.php?pkg=lepton&arch=amd64&ver=1.2.1%2B20170405-3&stamp=1496420251&raw=0

--
ChangZhuo Chen (陳昌倬) czchen@{czchen,debian}.org
http://czchen.info/
Key fingerprint = BA04 346D C2E1 FE63 C790 8793 CC65 B0CD EC27 5D5B

signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 1.2.1+20170405-3+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#885302: marked as done (gtklick: Depends on unmaintained pygtk)

Your message dated Fri, 15 Nov 2019 07:35:53 +
with message-id 
and subject line Bug#944570: Removed package(s) from unstable
has caused the Debian Bug report #885302,
regarding gtklick: Depends on unmaintained pygtk
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.)


-- 
885302: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885302
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gtklick
Version: 0.6.4-5
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

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

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

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

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

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Version: 0.6.4-5+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#936887: marked as done (liblarch: Python2 removal in sid/bullseye)

Your message dated Fri, 15 Nov 2019 07:34:56 +
with message-id 
and subject line Bug#944568: Removed package(s) from unstable
has caused the Debian Bug report #936887,
regarding liblarch: Python2 removal in sid/bullseye
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.)


-- 
936887: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936887
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:liblarch
Version: 2.1.0-4
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:liblarch

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Version: 2.1.0-4+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#943899: marked as done (Should ndisgtk be removed?)

Your message dated Fri, 15 Nov 2019 07:35:29 +
with message-id 
and subject line Bug#944569: Removed package(s) from unstable
has caused the Debian Bug report #943899,
regarding Should ndisgtk be removed?
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.)


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

Should ndisgtk be removed?

It's dead upstream (no release for 10 years) and depends on outdated stacks 
scheduled for removal
(python 2, pygtk).

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Version: 0.8.5-1+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#936672: marked as done (gtklick: Python2 removal in sid/bullseye)

Your message dated Fri, 15 Nov 2019 07:35:53 +
with message-id 
and subject line Bug#944570: Removed package(s) from unstable
has caused the Debian Bug report #936672,
regarding gtklick: Python2 removal in sid/bullseye
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.)


-- 
936672: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936672
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gtklick
Version: 0.6.4-5
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:gtklick

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Version: 0.6.4-5+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#885356: marked as done (ndisgtk: Depends on unmaintained pygtk)

Your message dated Fri, 15 Nov 2019 07:35:29 +
with message-id 
and subject line Bug#944569: Removed package(s) from unstable
has caused the Debian Bug report #885356,
regarding ndisgtk: Depends on unmaintained pygtk
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.)


-- 
885356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885356
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ndisgtk
Version: 0.8.5-1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: oldlibs pygtk
Tags: sid buster

pygtk is unmaintained upstream. It has not had a release since GNOME 3
was released in 2011.

The way forward is to port your app to use GObject Introspection
bindings (and gtk3).

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

Please try to do this before the Buster release as we're going to
try to remove pygtk this cycle.

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

[1] https://wiki.gnome.org/Projects/GObjectIntrospection
[2] https://wiki.gnome.org/Projects/PyGObject

On behalf of the Debian GNOME team,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Version: 0.8.5-1+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#906578: marked as done ([makehuman] Future Qt4 removal)

Your message dated Fri, 15 Nov 2019 07:39:24 +
with message-id 
and subject line Bug#944761: Removed package(s) from unstable
has caused the Debian Bug report #906578,
regarding [makehuman] Future Qt4 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.)


-- 
906578: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906578
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: makehuman
Version: 1.1.1-1
Severity: normal
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal

TL;DR: Your package, makehuman, is using pyqt4 which depends on Qt4. 
However, it is planned that Qt4 shall be removed from Debian in the 
future. Please check upstream status for Qt5 migration and package 
the new (py)Qt5-based version when available.

* Python3 + Qt5 development git repository:

https://github.com/makehumancommunity/makehuman

== Begin mail template ==

Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:

[announced] 

Currently Qt4 has been dead upstream and we are starting to have 
problems
maintaining it.

In order to make this move, all packages directly or indirectly 
depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a 
Qt5
port of your application
- if there are no activities regarding porting, investigate whether 
there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging 
it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version


For any questions and issues, do not hesitate to contact the Debian 
Qt/KDE
team at debian-qt-...@lists.debian.org

The removal is being tracked in 

== End mail template ==

Regards,
Boyuan Yang


signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---
Version: 1.1.1-1.2+rm

Dear submitter,

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

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

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

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#937123: marked as done (ndisgtk: Python2 removal in sid/bullseye)