Bug#941351: peruse: Peruse fails to start

[Settenvini, Matteo]

After the last system updates, I now experience a slightly different
failure:

Model size of -1 is less than 0
qml: Warning: ApplicationHeader is deprecated, remove and use the
automatic internal toolbar instead.
file:///usr/lib/x86_64-linux-
gnu/qt5/qml/org/kde/kirigami.2/templates/private/ForwardButton.qml:33:
ReferenceError: globalToolBar is not defined
file:///usr/lib/x86_64-linux-
gnu/qt5/qml/org/kde/kirigami.2/templates/private/BackButton.qml:33:
ReferenceError: globalToolBar is not defined
kf5.kservice.services: KServiceTypeTrader: serviceType "ThumbCreator"
not found
kf5.kservice.services: KServiceTypeTrader: serviceType "ThumbCreator"
not found
kf5.kservice.services: KServiceTypeTrader: serviceType "ThumbCreator"
not found
kf5.kservice.services: KServiceTypeTrader: serviceType "ThumbCreator"
not found
kf5.kservice.services: KServiceTypeTrader: serviceType "ThumbCreator"
not found
kf5.kservice.services: KServiceTypeTrader: serviceType "ThumbCreator"
not found
kf5.kservice.services: KServiceTypeTrader: serviceType "ThumbCreator"
not found
kf5.kservice.services: KServiceTypeTrader: serviceType "ThumbCreator"
not found
kf5.kservice.services: KServiceTypeTrader: serviceType "ThumbCreator"
not found
kf5.kservice.services: KServiceTypeTrader: serviceType "ThumbCreator"
not found
file:///usr/lib/x86_64-linux-
gnu/qt5/qml/org/kde/kirigami.2/templates/private/BackButton.qml:33:
ReferenceError: globalToolBar is not defined
file:///usr/lib/x86_64-linux-
gnu/qt5/qml/org/kde/kirigami.2/templates/private/ForwardButton.qml:33:
ReferenceError: globalToolBar is not defined
file:///usr/lib/x86_64-linux-
gnu/qt5/qml/org/kde/kirigami.2/templates/private/BackButton.qml:33:
ReferenceError: globalToolBar is not defined
file:///usr/lib/x86_64-linux-
gnu/qt5/qml/org/kde/kirigami.2/templates/private/ForwardButton.qml:33:
ReferenceError: globalToolBar is not defined
file:///usr/lib/x86_64-linux-
gnu/qt5/qml/org/kde/kirigami.2/templates/private/BackButton.qml:33:
ReferenceError: globalToolBar is not defined
file:///usr/lib/x86_64-linux-
gnu/qt5/qml/org/kde/kirigami.2/templates/private/ForwardButton.qml:33:
ReferenceError: globalToolBar is not defined
file:///usr/lib/x86_64-linux-
gnu/qt5/qml/org/kde/kirigami.2/templates/private/BackButton.qml:33:
ReferenceError: globalToolBar is not defined
file:///usr/lib/x86_64-linux-
gnu/qt5/qml/org/kde/kirigami.2/templates/private/ForwardButton.qml:33:
ReferenceError: globalToolBar is not defined
Errore di segmentazione (core dump creato)

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

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

Versions of packages peruse depends on:
ii  kio 5.62.1-2
ii  libc6   2.29-3
ii  libgcc1 1:9.2.1-19
ii  libkf5archive5  5.62.0-1
ii  libkf5baloo55.62.0-2
ii  libkf5configcore5   5.62.0-1
ii  libkf5coreaddons5   5.62.0-1
ii  libkf5declarative5  5.62.0-1
ii  libkf5filemetadata3 5.62.0-1
ii  libkf5i18n5 5.62.0-1
ii  libkf5kiocore5  5.62.1-2
ii  libkf5kiowidgets5   5.62.1-2
ii  libqt5core5a5.12.5+dfsg-2
ii  libqt5gui5  5.12.5+dfsg-2
ii  libqt5qml5  5.12.5-3
ii  libqt5quick55.12.5-3
ii  libqt5sql5  5.12.5+dfsg-2
ii  libqt5widgets5  5.12.5+dfsg-2
ii  libstdc++6  9.2.1-19
ii  peruse-common   1.2+dfsg+20190713-1
ii  qml-module-org-kde-kirigami25.62.0-2
ii  qml-module-org-kde-newstuff 5.62.0-1
ii  qml-module-qt-labs-folderlistmodel  5.12.5-3
ii  qml-module-qt-labs-settings 5.12.5-3
ii  qml-module-qtquick-controls 5.12.5-1
ii  qml-module-qtquick-dialogs  5.12.5-1
ii  qml-module-qtquick-layouts  5.12.5-3

peruse recommends no packages.

peruse suggests no packages.

-- no debconf information

Bug#944652: cmark-gfm: FTBFS on s390x

[Ivo De Decker]

package: src:cmark-gfm
version: 0.29.0.gfm.0-1
severity: serious
tags: ftbfs

Hi,

The latest upload of cmark-gfm to unstable fails on s390x:

https://buildd.debian.org/status/package.php?p=cmark-gfm

Also, if you upload a fix for this, please do a source-only upload to allow it
to migrate to testing.

Cheers,

Ivo

Bug#920147: sagemath FTBFS on mipsel and mips64el

[Tobias Hansen]

It seems like the build failures are related to timeouts of jmol. These 
timeouts started roughly at the time when the default Java version was changed 
in java-common from 10 to 11 in October 2018.

There are also other reports of jmol being broken depending on the jre version, 
see
https://ask.sagemath.org/question/47837/jmol-stuck-at-initializing-3d-display/

While jmol was already replaced by threejs as the default 3d viewer in 
interactive mode, it is still used in the command line mode and hence when 
running the tests.

Maybe we should try to remove jmol completely, or fix it on mipsel and mips64el.

Best,
Tobias

Bug#944657: browserpass: FTBFS on mips64el, mipsel

[Ivo De Decker]

package: src:browserpass
version: 3.4.1-1
severity: serious
tags: ftbfs

Hi,

The latest upload of browserpass to unstable fails on mips64el, mipsel:

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

Cheers,

Ivo

Bug#940224: marked as done (lambda-term: FTBFS with new zed)

[Debian Bug Tracking System]

Your message dated Wed, 13 Nov 2019 09:58:21 +0100
with message-id <7e21c933-c68c-3b23-41be-8623e7a45...@debian.org>
and subject line Re: Bug#940224: lambda-term: FTBFS with new zed
has caused the Debian Bug report #940224,
regarding lambda-term: FTBFS with new zed
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.)


-- 
940224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940224
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lambda-term
Version: 1.10.1-2
Severity: serious

Hello, looks like the new zed made the package FTBFS

+ /usr/bin/ocamlfind ocamlc -c -g -annot -bin-annot -ccopt -I/usr/lib/ocaml/lwt 
-package lwt -package lwt.react -package lwt.unix -package zed -w -40 -I src -I 
src/widget_impl -o src/lTerm_widget.cmo src/lTerm_widget.ml
File "src/lTerm_widget.ml", line 10, characters 5-32:
Warning 3: deprecated: module CamomileLibraryDyn
Use CamomileLibraryDefault. Configuration using
environment variables is ignored. This module just now aliases
CamomileLibraryDefault
/usr/bin/ocamlfind ocamlc -c -g -annot -bin-annot -ccopt -I/usr/lib/ocaml/lwt 
-package lwt -package lwt.react -package lwt.unix -package zed -w -40 -I src -I 
src/widget_impl -o src/lTerm_widget_callbacks.cmo src/lTerm_widget_callbacks.ml
/usr/bin/ocamlfind ocamlc -c -g -annot -bin-annot -ccopt -I/usr/lib/ocaml/lwt 
-package lwt -package lwt.react -package lwt.unix -package zed -w -40 -I src -I 
src/widget_impl -o src/lTerm_edit.cmo src/lTerm_edit.ml
+ /usr/bin/ocamlfind ocamlc -c -g -annot -bin-annot -ccopt -I/usr/lib/ocaml/lwt 
-package lwt -package lwt.react -package lwt.unix -package zed -w -40 -I src -I 
src/widget_impl -o src/lTerm_edit.cmo src/lTerm_edit.ml
File "src/lTerm_edit.ml", line 10, characters 5-32:
Warning 3: deprecated: module CamomileLibraryDyn
Use CamomileLibraryDefault. Configuration using
environment variables is ignored. This module just now aliases
CamomileLibraryDefault
File "src/lTerm_edit.ml", line 160, characters 2-16:
Error: Unbound value Zed_re.compile
Command exited with code 2.
E: Failure("Command ''/usr/bin/ocamlbuild' src/liblambda-term_stubs.a 
src/dlllambda-term_stubs.so src/lambda-term.cma src/lambda-term.cmxa 
src/lambda-term.a src/lambda-term.cmxs examples/events.native 
examples/colors.native examples/colors_256.native examples/rgb.native 
examples/move.native examples/hello.native examples/clock.native 
examples/buttons.native examples/focus.native examples/checkbuttons.native 
examples/radiobuttons.native examples/shell.native examples/repl.native 
examples/modal.native examples/read_password.native examples/read_yes_no.native 
examples/editor.native tools/lambda_term_actions.native -tag debug' terminated 
with error code 10")
make[1]: *** [debian/rules:25: override_dh_auto_build] Error 1
make[1]: Leaving directory '/build/lambda-term-1.10.1'
make: *** [debian/rules:17: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
I: copying local configuration

can you please have a look?
thanks

Gianfranco
--- End Message ---
--- Begin Message ---
Version: 2.0.2-1

Le 15/09/2019 à 16:06, Stéphane Glondu a écrit :
> There is a new upstream release of lambda-term presumably fixing that.
> Unfortunately, the new lambda-term depends on lwt >= 4 which depends on
> ocaml >= 4.08 (unless some compatibility package is introduced which I'd
> like to avoid).
> 
> This will be fixed during the transition to OCaml >= 4.08.

Done.

-- 
Stéphane--- End Message ---

Bug#941890: marked as done (python-clang-7: missing dependency on libclang-7-dev)

[Debian Bug Tracking System]

Your message dated Wed, 13 Nov 2019 08:44:26 +
with message-id 
and subject line Bug#941890: fixed in llvm-toolchain-8 1:8.0.1-4
has caused the Debian Bug report #941890,
regarding python-clang-7: missing dependency on libclang-7-dev
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.)


-- 
941890: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941890
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-clang-7
Version: 1:7.0.1-8
Severity: serious
Justification: missing dependency

After installing python-clang-7, it is unusable as is:

| $ python
| ...
| >>> import clang.cindex
| >>> clang.cindex.Index.create()
| Traceback (most recent call last):
|   File "", line 1, in 
|   File "/usr/lib/python2.7/dist-packages/clang/cindex.py", line 2672, in 
create
| return Index(conf.lib.clang_createIndex(excludeDecls, 0))
|   File "/usr/lib/python2.7/dist-packages/clang/cindex.py", line 198, in 
__get__
| value = self.wrapped(instance)
|   File "/usr/lib/python2.7/dist-packages/clang/cindex.py", line 4115, in lib
| lib = self.get_cindex_library()
|   File "/usr/lib/python2.7/dist-packages/clang/cindex.py", line 4146, in 
get_cindex_library
| raise LibclangError(msg)
| clang.cindex.LibclangError: libclang-7.so: cannot open shared object file: No 
such file or directory. To provide a path to libclang use 
Config.set_library_path() or Config.set_library_file().
| >>>

It fails to find libclang-7.so, which is shipped in libclang-7-dev.
After installing that package, creating the index works.

Helmut
--- End Message ---
--- Begin Message ---
Source: llvm-toolchain-8
Source-Version: 1:8.0.1-4

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

Debian distribution maintenance software
pp.
Sylvestre Ledru  (supplier of updated llvm-toolchain-8 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 12 Nov 2019 14:12:48 +0100
Source: llvm-toolchain-8
Architecture: source
Version: 1:8.0.1-4
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team 
Changed-By: Sylvestre Ledru 
Closes: 941890 943920
Changes:
 llvm-toolchain-8 (1:8.0.1-4) unstable; urgency=medium
 .
   * Add clangd-X => libclang-common-X-dev dependency
 See https://bugs.llvm.org/show_bug.cgi?id=43152
   * python-clang-8: missing dependency on libclang-8-dev
 (Closes: #941890)
   * Debian moved to gcc-9. This gcc version now refuses -flto="Thin"
 Move from LLVM_ENABLE_LTO="Thin" to BOOTSTRAP_LLVM_ENABLE_LTO="Thin"
 to mitigate the issue (the argument should be passed only at the
 second stage of the build process)
 See https://bugs.llvm.org/show_bug.cgi?id=43193
 (Closes: #943920)
Checksums-Sha1:
 61618033367794c6c2179268528eb50f0cb29b62 8566 llvm-toolchain-8_8.0.1-4.dsc
 6ce8eabc2700da81487c9445da18191aa2237254 113172 
llvm-toolchain-8_8.0.1-4.debian.tar.xz
 5b7a265e866b43fbbf478e1202dae6f554aa042f 11948 
llvm-toolchain-8_8.0.1-4_source.buildinfo
Checksums-Sha256:
 9cb0c275bdb78540412ad6a25cf9150d36a5d5039d33421ff666026ced0beff9 8566 
llvm-toolchain-8_8.0.1-4.dsc
 1467b299b1557b07d5cc1071d4cda0ba43f69fc85400b3e1395169349a40 113172 
llvm-toolchain-8_8.0.1-4.debian.tar.xz
 9b34d9ecc3da03bc066348d741f36c6b7b79288c0be76e4432a44ed98668715f 11948 
llvm-toolchain-8_8.0.1-4_source.buildinfo
Files:
 77bf61d0376809fdfb6f22e2042cc6b4 8566 devel optional 
llvm-toolchain-8_8.0.1-4.dsc
 a4daa33da54848a9daf99764a502182e 113172 devel optional 
llvm-toolchain-8_8.0.1-4.debian.tar.xz
 7d0c3b9fac3956a8963f3e8509a20341 11948 devel optional 
llvm-toolchain-8_8.0.1-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAl3LuSEVHHN5bHZlc3Ry
ZUBkZWJpYW4ub3JnAAoJEH5lKNp1Lxvh2g4QAILNkuEmRsvGhMExWmaIg7S1v8jf
xd3DDHSFTsrHpq4zWCOW/ViG4LOpFSwFpnQ0ZtZrTXDfWEtRbNqigZozxOIbrS+9
KqU1FYv28TeXWUPyvpj3SE/VkNjsqONzVKL49v+4Z854kX/KhNNcaf9Um/OhEydF
ri7CTFY1nsb9M9KbHl2qZRUXZCIkqeIJEYUXn0DskfKIaUIe5baX7OQMbQC5y1Cf
ButA80D7F2BVJ0clZhZpx5Gl9KG0PvTP7cVujwSX76/IckNtlE84bolXDwcFBbrw

Bug#943920: marked as done (llvm-toolchain-8: FTBFS since migration of gcc-defaults to gcc-9)

[Debian Bug Tracking System]

Your message dated Wed, 13 Nov 2019 08:44:26 +
with message-id 
and subject line Bug#943920: fixed in llvm-toolchain-8 1:8.0.1-4
has caused the Debian Bug report #943920,
regarding llvm-toolchain-8: FTBFS since migration of gcc-defaults to 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.)


-- 
943920: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943920
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: llvm-toolchain-8
Version: 1:8.0.1-3
Severity: serious
Justification: FTBFS

Hello,

Since the migration of gcc-defaults to gcc-9, llvm-toolchain-8 FTBFS,
with 



CMake Error at tools/polly/lib/External/CMakeLists.txt:91 (message):
  No ffs implementation found


looking at CMakeError.log, one actually see:


Source file was:

  int main() { (void)__builtin_ffs(0); return 0; }
  
Performing C SOURCE FILE Test HAVE_DECL__BITSCANFORWARD failed with the 
following output:
Change Dir: /build/llvm-toolchain-8-8.0.1/build-llvm/CMakeFiles/CMakeTmp

Run Build Command:"/usr/bin/make" "cmTC_11f2c/fast"
make[2]: Entering directory 
'/build/llvm-toolchain-8-8.0.1/build-llvm/CMakeFiles/CMakeTmp'
/usr/bin/make -f CMakeFiles/cmTC_11f2c.dir/build.make 
CMakeFiles/cmTC_11f2c.dir/build
make[3]: Entering directory 
'/build/llvm-toolchain-8-8.0.1/build-llvm/CMakeFiles/CMakeTmp'
Building C object CMakeFiles/cmTC_11f2c.dir/src.c.o
/usr/bin/gcc-9 -D_GNU_SOURCE  -g -O2 
-fdebug-prefix-map=/build/llvm-toolchain-8-8.0.1=. -fstack-protector-strong 
-Wformat -Werror=format-security -fPIC -Werror=date-time -Wall -Wextra 
-Wno-unused-parameter -Wwrite-strings -Wno-missing-field-initializers -pedantic 
-Wno-long-long -Wimplicit-fallthrough -Wno-comment -ffunction-sections 
-fdata-sections -flto=thin -DHAVE_DECL__BITSCANFORWARD   -o 
CMakeFiles/cmTC_11f2c.dir/src.c.o   -c 
/build/llvm-toolchain-8-8.0.1/build-llvm/CMakeFiles/CMakeTmp/src.c
cc1: error: unrecognized argument to '-flto=' option: 'thin'


i.e. llvm passed -flto=thin to gcc-9, which does not understand it.
gcc-8 used to understand it, but not gcc-9 any more. I had to comment in
debian/rules CMAKE_EXTRA += -DLLVM_ENABLE_LTO="Thin" to get it built.

Samuel

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

Kernel: Linux 5.3.0 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE
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 /bin/dash
Init: systemd (via /run/systemd/system)

-- 
Samuel
 t1 faich
 les programmes ils segfaultent jamais quand on veut
 -+- #ens-mim en plein débogage -+-
--- End Message ---
--- Begin Message ---
Source: llvm-toolchain-8
Source-Version: 1:8.0.1-4

We believe that the bug you reported is fixed in the latest version of
llvm-toolchain-8, 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.
Sylvestre Ledru  (supplier of updated llvm-toolchain-8 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 12 Nov 2019 14:12:48 +0100
Source: llvm-toolchain-8
Architecture: source
Version: 1:8.0.1-4
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team 
Changed-By: Sylvestre Ledru 
Closes: 941890 943920
Changes:
 llvm-toolchain-8 (1:8.0.1-4) unstable; urgency=medium
 .
   * Add clangd-X => libclang-common-X-dev dependency
 See https://bugs.llvm.org/show_bug.cgi?id=43152
   * python-clang-8: missing dependency on libclang-8-dev
 (Closes: #941890)
   * Debian moved to gcc-9. This gcc version now refuses -flto="Thin"
 Move from LLVM_ENABLE_LTO="Thin" to 

Bug#944653: ofono: FTBFS on arm64, armel, armhf, ppc64el, s390x

[Ivo De Decker]

package: src:ofono
version: 1.28-1
severity: serious
tags: ftbfs

Hi,

The latest upload of ofono to unstable fails on arm64, armel, armhf, ppc64el, 
s390x:

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

Cheers,

Ivo

Bug#944651: gcl: FTBFS on ppc64el

[Ivo De Decker]

package: src:gcl
version: 2.6.12-88
severity: serious
tags: ftbfs

Hi,

The latest upload of gcl to unstable fails on ppc64el:

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

I suspect the FTBFS of acl2 is related.

Cheers,

Ivo

Bug#944648: sagemath FTBFS on i386

[Tobias Hansen]

Source: sagemath
Version: 8.9-2
Severity: serious

Since the switch to Python 3 in 8.9~beta9-1, sagemath fails to build from 
source on i386. The reason are segmentation faults in the following three tests:

sage -t --long src/sage/schemes/elliptic_curves/isogeny_small_degree.py  # 
Killed due to segmentation fault
sage -t --long src/sage/schemes/elliptic_curves/ell_number_field.py  # Killed 
due to abort
sage -t --long src/sage/schemes/elliptic_curves/ell_field.py  # Killed due to 
segmentation fault

All three failures give the error message

OverflowError: Python int too large to convert to C long

from

File "sage/rings/polynomial/polynomial_integer_dense_flint.pyx", line 284, in 
sage.rings.polynomial.polynomial_integer_dense_flint.Polynomial_integer_dense_flint.__init__
 
(build/cythonized/sage/rings/polynomial/polynomial_integer_dense_flint.cpp:6548)
fmpz_poly_set_coeff_si(self.__poly, i, a)

Help on finding a fix would be appreciated.

Best,
Tobias

Bug#942538: reducing matplotlib2 build-depends.

[Dmitry Shachnev]

Hi Sandro!

On Tue, Nov 12, 2019 at 09:10:49PM -0500, Sandro Tosi wrote:
> well, i dont think it's a good reason to just stop testing complex
> software tho. some of those dependencies are required so that mpl can
> build extensions (in particular for the GUI backends) so if you remove
> them, the mpl build system is smart enough to disable those
> extensions, resulting in a graphic library without any GUI bindings to
> work with. that doesnt sound ideal.

That is a valid point. But please drop at least the PyQt4 GUI binding.

That one is clearly not needed when PyQt5 binding exists.

> I'm gonna go thru some of the dependencies and will see if i can
> remove some, in particular now that i've remored the -doc package from
> the git repo, but i'm not gonna get rid the whole unittest suite.
>
> thanks for your work on this, and to nudge me into looking deeper at mpl2
> deps

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#944658: mailavenger: FTBFS on i386

[Ivo De Decker]

package: src:mailavenger
version: 0.8.5-2
severity: serious
tags: ftbfs

Hi,

The latest upload of mailavenger to unstable fails on i386:

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

Cheers,

Ivo

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

[Andreas Beckmann]

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=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, , 
_config_ops)
ELSE:
result = libzfs.zpool_search_import(self.handle, )
  ^


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, , NULL)
ELSE:
ret = libzfs.zpool_read_label(fd, )
   ^


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, , 
_config_ops)
ELSE:
result = libzfs.zpool_search_import(self.handle, )
  ^


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

Bug#943447: marked as done (the autopkg test calls python instead of python2)

[Debian Bug Tracking System]

Your message dated Wed, 13 Nov 2019 10:34:34 +
with message-id 
and subject line Bug#943447: fixed in gexiv2 0.12.0-1
has caused the Debian Bug report #943447,
regarding the autopkg test calls python instead of python2
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.)


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

Package: src:gexiv
Version: 0.10.9-1
Severity: serious
Tags: sid bullseye patch

the autopkg test calls python instead of python2. This will make the package 
fail the next binNMU when adding python3.8 support.


http://launchpadlibrarian.net/448276453/gexiv2_0.10.9-1_0.10.9-1ubuntu1.diff.gz
--- End Message ---
--- Begin Message ---
Source: gexiv2
Source-Version: 0.12.0-1

We believe that the bug you reported is fixed in the latest version of
gexiv2, 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.
Jason Crain  (supplier of updated gexiv2 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, 01 Nov 2019 02:59:35 -0600
Source: gexiv2
Architecture: source
Version: 0.12.0-1
Distribution: unstable
Urgency: medium
Maintainer: Jason Crain 
Changed-By: Jason Crain 
Closes: 943447
Changes:
 gexiv2 (0.12.0-1) unstable; urgency=medium
 .
   * New upstream version 0.12.0
   * Update d/copyright
 * Add gexiv2 mailing list to Upstream-Contact.
   * Update d/rules
 * Remove dbgsym migration code since migration is complete.
 * No longer need to specify meson build system since autotools build was
   removed.
 * Renamed enable-gtk-doc option to gtk_doc.
   * Update d/control
 * Bump debhelper level to 12.
 * Switch to the 'debhelper-compat' dependency style. Remove the d/compat
   file.
 * Update Standards-Version to 4.4.1 No changes necessary.
 * Add Rules-Requires-Root: no
   * Update symbols
   * Dynamically generate d/libgexiv2-2.symbols.
 Upstream removed the script which kept C++ symbols from being exported due
 to regressions on OpenBSD 
(https://gitlab.gnome.org/GNOME/gexiv2/issues/27).
 Mark all C++ symbols as optional since these aren't part of the API.
   * Use 'python3' instead of 'python' in autopkgtest.
 Thanks to Matthias Klose (Closes: #943447)
   * Install /usr/share/vala/vapi/gexiv2.deps.
 This file tells vala about dependencies.
   * Add patch Use-exiv2-version-0.25.patch.
 This modifies gexiv2 to use exiv2 version 0.25, the version currently in
 Debian unstable. Upstream is set to use exiv2 version 0.26 or later,
 which is only currently available in Debian experimental.
Checksums-Sha1:
 dce1017980806c4087b60b92c75f2f696533722f 2258 gexiv2_0.12.0-1.dsc
 2d8894d307363726b345d0535d5fe5b7153a7ea9 370816 gexiv2_0.12.0.orig.tar.xz
 2639376d80e39029f5cbcaa99491f21fe233a8f6 9664 gexiv2_0.12.0-1.debian.tar.xz
 d21e89b00930b84c147da75b8593b13d1f4d624c 8190 gexiv2_0.12.0-1_source.buildinfo
Checksums-Sha256:
 a715b9647f9e8425adbc84e3f6ea7fea9d4ea33d6c1388a69b5144327125b3fa 2258 
gexiv2_0.12.0-1.dsc
 58f539b0386f36300b76f3afea3a508de4914b27e78f58ee4d142486a42f926a 370816 
gexiv2_0.12.0.orig.tar.xz
 e66f8a5d13cfab7220664810ae69b580c1cfd3039bcc7b70dcf8c4332f0c9736 9664 
gexiv2_0.12.0-1.debian.tar.xz
 507b59ccac892344cf7980bde5f1f52e186d6dff83ef32f419e00dc7fe7244f2 8190 
gexiv2_0.12.0-1_source.buildinfo
Files:
 a303c49848cbea7ddd4e8994542a16be 2258 libs optional gexiv2_0.12.0-1.dsc
 0a618c5b053106d1801d89cc77385419 370816 libs optional gexiv2_0.12.0.orig.tar.xz
 bfb2ad8bab5b0c85cc8e1fe483201691 9664 libs optional 
gexiv2_0.12.0-1.debian.tar.xz
 9787c57002de273686bbade3007a7572 8190 libs optional 
gexiv2_0.12.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCgAtFiEExyA8CpIGcL+U8AuxsB0acqyNyaEFAl3L12EPHGpjY0BkZWJp
YW4ub3JnAAoJELAdGnKsjcmh+88P/2uDgZx1Dc26tqyVtIN8LJEMCTW6sNk6zyUi
KkQtgpVZ9a/59OqIPaaMMBRUjf+A+/omVyDAZIMQOYBp44sjIl/eeh7WolaLRmJd
DwMImzFg04JN2rnsHka8Ec1c4dVXyRFls7Mnqb25GotuDkc5ARocMrmGgGSR7nEz
36MWYhCsdhcCoa+hnYu5evvOOPgzFNjjLvMI5Y9JB5rYnU+5Ud1X+JfYQRoS3Suo

Bug#944683: FTBFS: missing file /usr/lib/nodejs/axios/dist/axios.min.js

[Gert Wollny]

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.

Bug#906230: marked as done (insighttoolkit4-python: missing python dependencies)

[Debian Bug Tracking System]

Your message dated Wed, 13 Nov 2019 19:03:06 +0100
with message-id <2cb386289a7ef0aa6c11232755432524ecc3a5ff.ca...@collabora.com>
and subject line Fixed bugs
has caused the Debian Bug report #906230,
regarding insighttoolkit4-python: missing python dependencies
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.)


-- 
906230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906230
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: insighttoolkit4-python
Version: 4.10.1-dfsg1-1.1
Severity: serious
Tags: patch

Fix:

--- debian/control.in.old   2018-08-13 12:46:42.486599767 +
+++ debian/control.in   2018-08-14 08:11:49.018243996 +
@@ -21,6 +21,7 @@
 libminc-dev, 
 libnifti-dev, 
 libhdf5-dev, 
+dh-python,
 python-all-dev
 #  libvtk6-dev -- only needed if we enable one of the following modules:
 # VtkGlue, LevelSetsv4Visualization
@@ -90,7 +91,7 @@
 Package: insighttoolkit@VER_MAJOR@-python 
 Section: python 
 Architecture: amd64 i386
-Depends: ${misc:Depends}, ${shlibs:Depends}
+Depends: ${misc:Depends}, ${shlibs:Depends}, ${python:Depends}
 Conflicts: insighttoolkit-python
 Replaces: insighttoolkit-python
 Description: Image processing toolkit for registration and segmentation - 
Python bindings
--- debian/control.old  2018-08-12 22:39:53.179084322 +
+++ debian/control  2018-08-14 08:11:37.626244105 +
@@ -21,6 +21,7 @@
libminc-dev, 
 libnifti-dev, 
libhdf5-dev, 
+   dh-python,
python-all-dev
 #  libvtk6-dev -- only needed if we enable one of the following modules:
 # VtkGlue, LevelSetsv4Visualization
@@ -90,7 +91,7 @@
 Package: insighttoolkit4-python 
 Section: python 
 Architecture: amd64 i386
-Depends: ${misc:Depends}, ${shlibs:Depends}
+Depends: ${misc:Depends}, ${shlibs:Depends}, ${python:Depends}
 Conflicts: insighttoolkit-python
 Replaces: insighttoolkit-python
 Description: Image processing toolkit for registration and segmentation - 
Python bindings
--- debian/rules.old2018-08-12 22:39:54.667084308 +
+++ debian/rules2018-08-13 12:48:11.170598921 +
@@ -81,7 +81,7 @@
 
 
 %:
-   dh $@ --builddir=BUILD --parallel
+   dh $@ --builddir=BUILD --parallel --with python2
 
 override_dh_auto_configure-indep:
 
--- End Message ---
--- Begin Message ---
Version: 4.13.2-dfsg1-1--- End Message ---

Bug#897775: marked as done (itksnap: ftbfs with GCC-8)

[Debian Bug Tracking System]

Your message dated Wed, 13 Nov 2019 19:03:06 +0100
with message-id <2cb386289a7ef0aa6c11232755432524ecc3a5ff.ca...@collabora.com>
and subject line Fixed bugs
has caused the Debian Bug report #897775,
regarding itksnap: ftbfs with GCC-8
to be marked as done.

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

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


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

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-8/g++-8, but succeeds to build with gcc-7/g++-7. The
severity of this report will be raised before the buster release.

The full build log can be found at:
http://aws-logs.debian.net/2018/05/01/gcc8/itksnap_3.6.0-2_unstable_gcc8.log.gz
The last lines of the build log are at the end of this report.

To build with GCC 8, either set CC=gcc-8 CXX=g++-8 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-8/porting_to.html

[...]
cd /<>/obj-x86_64-linux-gnu/Submodules/c3d && /usr/bin/c++  
-DITK_IO_FACTORY_REGISTER_MANAGER 
-DvtkFiltersFlowPaths_AUTOINIT="1(vtkFiltersParallelFlowPaths)" 
-DvtkIOExodus_AUTOINIT="1(vtkIOParallelExodus)" 
-DvtkIOGeometry_AUTOINIT="1(vtkIOMPIParallel)" 
-DvtkIOImage_AUTOINIT="1(vtkIOMPIImage)" 
-DvtkIOParallel_AUTOINIT="1(vtkIOMPIParallel)" 
-DvtkIOSQL_AUTOINIT="2(vtkIOMySQL,vtkIOPostgreSQL)" 
-DvtkRenderingContext2D_AUTOINIT="1(vtkRenderingContextOpenGL)" 
-DvtkRenderingCore_AUTOINIT="3(vtkInteractionStyle,vtkRenderingFreeType,vtkRenderingOpenGL)"
 
-DvtkRenderingFreeType_AUTOINIT="2(vtkRenderingFreeTypeFontConfig,vtkRenderingMatplotlib)"
 -DvtkRenderingLIC_AUTOINIT="1(vtkRenderingParallelLIC)" 
-DvtkRenderingVolume_AUTOINIT="1(vtkRenderingVolumeOpenGL)" 
-I/<>/obj-x86_64-linux-gnu/ITKIOFactoryRegistration 
-I/usr/include/hdf5/serial -I/usr/include/x86_64-linux-gnu -I/usr/include/nifti 
-I/usr/include/gdcm-2.8 -I/usr/include/double-conversion 
-I/usr/include/ITK-4.12 -I
 /usr/include/vtk-6.3 -I/usr/include/freetype2 
-I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi 
-I/usr/lib/x86_64-linux-gnu/openmpi/include -I/usr/include/python2.7 
-I/usr/include/hdf5/openmpi -I/usr/include/libxml2 -I/usr/include/jsoncpp 
-I/usr/include/tcl -I/usr/lib/cmake/ITK-4.12/Utilities/zlib 
-I/<>/Common -I/<>/Common/ITKExtras 
-I/<>/Logic -I/<>/Logic/Common 
-I/<>/Logic/Framework -I/<>/Logic/ImageWrapper 
-I/<>/Logic/LevelSet -I/<>/Logic/Mesh 
-I/<>/Logic/Preprocessing 
-I/<>/Logic/Preprocessing/GMM 
-I/<>/Logic/Preprocessing/Texture 
-I/<>/Logic/RLEImage -I/<>/Logic/Slicing 
-I/<>/Submodules/c3d/itkextras/RandomForest 
-I/<>/Submodules/c3d/api -I/<>/Submodules/greedy/src 
-I/<>/GUI -I/<>/GUI/Model 
-I/<>/GUI/Renderer -I/<>/GUI/R
 enderer/OrientationWidget/Reorient -I/<>/GUI/Qt 
-I/<>/GUI/Qt/Components -I/<>/GUI/Qt/Coupling 
-I/<>/GUI/Qt/External 
-I/<>/GUI/Qt/External/ColorWheel 
-I/<>/GUI/Qt/ModelView -I/<>/GUI/Qt/Testing 
-I/<>/GUI/Qt/View -I/<>/GUI/Qt/Windows 
-I/<>/GUI/Qt/Windows/MeshExportWizard 
-I/<>/GUI/Qt/Windows/Registration -I/<>/Testing/Logic 
-I/<>/Testing/GUI/Qt -I/<>/obj-x86_64-linux-gnu 
-I/usr/include/x86_64-linux-gnu/qt5 
-I/usr/include/x86_64-linux-gnu/qt5/QtWidgets 
-I/usr/include/x86_64-linux-gnu/qt5/QtGui 
-I/usr/include/x86_64-linux-gnu/qt5/QtCore 
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ 
-I/usr/include/x86_64-linux-gnu/qt5/QtOpenGL 
-I/usr/include/x86_64-linux-gnu/qt5/QtConcurrent 
-I/usr/include/x86_64-linux-gnu/qt5/QtQml 
-I/usr/include/x86_64-linux-gnu/qt5/QtNetwork -I/<>/Submodules/c3d 
-I/<>/Submodules/c3d/adapters -I/<>/Submodules/c3d/itkextras 
-I/<>/Submodules/c3d/itkextras/VoxBoIO 
-I/<>/Submodules/c3d/itkextras/PovRayIO 
-I/<>/Submodules/c3d/utilities/doc 
-I/<>/obj-x86_64-linux-gnu/Submodules/c3d  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fPIC -funroll-loops -ftree-vectorize -Wdate-time 
-D_FORTIFY_SOURCE=2 -o 

Bug#897756: marked as done (fw4spl: ftbfs with GCC-8)

[Debian Bug Tracking System]

Your message dated Wed, 13 Nov 2019 19:03:06 +0100
with message-id <2cb386289a7ef0aa6c11232755432524ecc3a5ff.ca...@collabora.com>
and subject line Fixed bugs
has caused the Debian Bug report #897756,
regarding fw4spl: ftbfs with GCC-8
to be marked as done.

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

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


-- 
897756: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897756
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:fw4spl
Version: 14.0.0-1
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-8

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-8/g++-8, but succeeds to build with gcc-7/g++-7. The
severity of this report will be raised before the buster release.

The full build log can be found at:
http://aws-logs.debian.net/2018/05/01/gcc8/fw4spl_14.0.0-1_unstable_gcc8.log.gz
The last lines of the build log are at the end of this report.

To build with GCC 8, either set CC=gcc-8 CXX=g++-8 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-8/porting_to.html

[...]
cd /<>/obj-x86_64-linux-gnu/fwServices && /usr/bin/c++  
-DBOOST_ALL_DYN_LINK -DBOOST_SPIRIT_USE_PHOENIX_V3 
-DBOOST_THREAD_DONT_PROVIDE_DEPRECATED_FEATURES_SINCE_V3_0_0 
-DBOOST_THREAD_PROVIDES_FUTURE -DBOOST_THREAD_VERSION=2 -DFWSERVICES_EXPORTS 
-DFWSERVICES_VER=\"0.1\" -DSPYLOG_LEVEL=2 -DSPYLOG_NO_INCLUDE=1 
-I/<>/SrcLib/core/fwServices/include 
-I/<>/obj-x86_64-linux-gnu/fwServices/include 
-I/<>/SrcLib/core/fwActivities/include 
-I/<>/obj-x86_64-linux-gnu/fwActivities/include 
-I/<>/SrcLib/core/fwCore/include 
-I/<>/obj-x86_64-linux-gnu/fwCore/include 
-I/<>/SrcLib/core/fwData/include 
-I/<>/obj-x86_64-linux-gnu/fwData/include 
-I/<>/SrcLib/core/fwCom/include 
-I/<>/obj-x86_64-linux-gnu/fwCom/include 
-I/<>/SrcLib/core/fwThread/include 
-I/<>/obj-x86_64-linux-gnu/fwThread/include 
-I/<>/SrcLib/core/fwTools/include -
 I/<>/obj-x86_64-linux-gnu/fwTools/include 
-I/<>/SrcLib/core/fwMemory/include 
-I/<>/obj-x86_64-linux-gnu/fwMemory/include 
-I/<>/SrcLib/core/fwCamp/include 
-I/<>/obj-x86_64-linux-gnu/fwCamp/include 
-I/<>/SrcLib/core/fwDataCamp/include 
-I/<>/obj-x86_64-linux-gnu/fwDataCamp/include 
-I/<>/SrcLib/core/fwMath/include 
-I/<>/obj-x86_64-linux-gnu/fwMath/include 
-I/<>/SrcLib/core/fwMedData/include 
-I/<>/obj-x86_64-linux-gnu/fwMedData/include 
-I/<>/SrcLib/core/fwRuntime/include 
-I/<>/obj-x86_64-linux-gnu/fwRuntime/include -isystem 
/usr/include/libxml2  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -Wextra -Wconversion -Wno-unused-parameter 
-Wno-ignored-qualifiers -fvisibility=hidden -O3 -DNDEBUG -fPIC   -std=gnu++11 
-o CMakeFiles/fwSer
 vices.dir/src/fwServices/registry/AppConfigParameters.cpp.o -c 
/<>/SrcLib/core/fwServices/src/fwServices/registry/AppConfigParameters.cpp
/<>/SrcLib/core/fwServices/src/fwServices/registry/AppConfigParameters.cpp:
 In member function 'void 
fwServices::registry::AppConfigParameters::parseBundleInformation()':
/<>/SrcLib/core/fwServices/src/fwServices/registry/AppConfigParameters.cpp:61:34:
 warning: variable 'iter' set but not used [-Wunused-but-set-variable]
 Registry::const_iterator iter = m_reg.find( extensionId );
  ^~~~
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
cd /<>/obj-x86_64-linux-gnu/fwServices && /usr/bin/c++  
-DBOOST_ALL_DYN_LINK -DBOOST_SPIRIT_USE_PHOENIX_V3 
-DBOOST_THREAD_DONT_PROVIDE_DEPRECATED_FEATURES_SINCE_V3_0_0 
-DBOOST_THREAD_PROVIDES_FUTURE -DBOOST_THREAD_VERSION=2 -DFWSERVICES_EXPORTS 
-DFWSERVICES_VER=\"0.1\" -DSPYLOG_LEVEL=2 -DSPYLOG_NO_INCLUDE=1 
-I/<>/SrcLib/core/fwServices/include 
-I/<>/obj-x86_64-linux-gnu/fwServices/include 
-I/<>/SrcLib/core/fwActivities/include 
-I/<>/obj-x86_64-linux-gnu/fwActivities/include 
-I/<>/SrcLib/core/fwCore/include 
-I/<>/obj-x86_64-linux-gnu/fwCore/include 
-I/<>/SrcLib/core/fwData/include 

Bug#944680: python-ftputil: Python2 removal in sid/bullseye

[Stuart Prescott]

Source: python-ftputil
Version: 3.4-1
Severity: serious
Tags: sid bullseye
Justification: Python 2 is going away.
User: debian-pyt...@lists.debian.org
Usertags: py2removal

New Python 2 packages shouldn't be added to bullseye at this stage unless it's
the *only* way of helping some other package transition from Python 2 to
Python 3 *and* there is a clear plan on how and when to remove them in early
2020.

--- boilerplate of the rest of the py2rm bug below ---

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:python-debian

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.

Bug#944680: marked as done (python-ftputil: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 13 Nov 2019 18:35:06 +
with message-id 
and subject line Bug#944680: fixed in python-ftputil 3.4-2
has caused the Debian Bug report #944680,
regarding python-ftputil: 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.)


-- 
944680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944680
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-ftputil
Version: 3.4-1
Severity: serious
Tags: sid bullseye
Justification: Python 2 is going away.
User: debian-pyt...@lists.debian.org
Usertags: py2removal

New Python 2 packages shouldn't be added to bullseye at this stage unless it's
the *only* way of helping some other package transition from Python 2 to
Python 3 *and* there is a clear plan on how and when to remove them in early
2020.

--- boilerplate of the rest of the py2rm bug below ---

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:python-debian

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 ---
Source: python-ftputil
Source-Version: 3.4-2

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 13 Nov 2019 13:18:17 -0500
Source: python-ftputil
Architecture: source
Version: 3.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sandro Tosi 
Closes: 944680
Changes:
 python-ftputil (3.4-2) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Use debhelper-compat instead of debian/compat.
 .
   [ Sandro Tosi ]
   * Drop python2 support (package biomaj for py3k only); Closes: #944680
Checksums-Sha1:
 0c7cab508dd82edc284e85ef1600509d63c511f7 2052 python-ftputil_3.4-2.dsc
 732e64e45904f51f09f0bbff5818054431ec3924 14300 
python-ftputil_3.4-2.debian.tar.xz
 

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

[Pirate Praveen]

On Mon, 11 Nov 2019 22:15:20 +0530 Pirate Praveen
 wrote:
> Control: retitle -1 ssh access fails with gitaly-upload-pack: fatal:
> error: %v
> On Sat, 2 Nov 2019 14:51:42 +0100 Romain Bignon  wrote:
> > Hello,
> > 
> > The problem is still here, and is so not related to compatibility between
> > versions of gitlab/gitlab-shell/gitality…
> > 
> > Is there anything I can do to find the origin of this issue?
> 
> Fortunately or unfortunately the same error hit my instance as well. I'm
> digging deeper into it now.
> 
> As a workaround you can use https access till we fix this (only ssh
> access is affected).

Found the root cause to be ruby-google-protobuf update from 3.7 to 3.10.
But to actually get it work is tricky.

If we downgrade ruby-google-protobuf to 3.7.1, then gitaly fails to build.

Bug#944672: goobook: Fails to query addresses

[Sergio Mendoza]

Package: goobook
Version: 3.4-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,


  goobook in debian sid (and most probably testing and also stable) fails to 
work when
querying a specified regex:


sergio@quetzalli:~$ goobook query sergio
Traceback (most recent call last):
  File "/usr/bin/goobook", line 11, in 
load_entry_point('goobook==3.4', 'console_scripts', 'goobook')()
  File "/usr/share/goobook/goobook/application.py", line 106, in main
args.func(config, args)
  File "/usr/share/goobook/goobook/application.py", line 154, in do_query
goobk = GooBook(config)
  File "/usr/share/goobook/goobook/goobook.py", line 55, in __init__
self.cache.load()
  File "/usr/share/goobook/goobook/goobook.py", line 260, in load
self.update()
  File "/usr/share/goobook/goobook/goobook.py", line 268, in update
self.contacts = list(parse_contacts(gcs.fetch_contacts(), groupname_by_id))
  File "/usr/share/goobook/goobook/goobook.py", line 352, in parse_contacts
parsed = parse_contact(contact, groupname_by_id)
  File "/usr/share/goobook/goobook/goobook.py", line 323, in parse_contact
membership['contactGroupMembership']['contactGroupId']])
KeyError: 'contactGroups/136c5dae0ca94ac9'
>>

  Everything seems to be at the google authentication procedure sin e.g.
changing cache_expiry_hours: 2 in ~/.goobookrc yields the expected
results.

  Nevertheless since the expected result relies on google authentitacion, 
it makes the package fully unusuable.

With best regards,

Sergio.


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

Kernel: Linux 5.2.0-2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: 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

Versions of packages goobook depends on:
ii  python3   3.7.5-1
ii  python3-googleapi 1.7.11-3
ii  python3-oauth2client  4.1.2-4
ii  python3-simplejson3.16.0-2

goobook recommends no packages.

goobook suggests no packages.

-- debconf-show failed

-- 
Sergio Mendoza  
Instituto de Astronomia, UNAM
http://www.mendozza.org/sergio

Processed: closing 943444

[Debian Bug Tracking System]

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

> # this version dropped py2 completely, so no bug anymore
> close 943444 3.4.4+20151206-1.2
Bug #943444 [src:tlsh] the autopkg test calls python instead of python2
Marked as fixed in versions tlsh/3.4.4+20151206-1.2.
Bug #943444 [src:tlsh] the autopkg test calls python instead of python2
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#940688: marked as done (mcomix: Python 3 fork available)

[Debian Bug Tracking System]

Your message dated Wed, 13 Nov 2019 15:21:00 +
with message-id 
and subject line Bug#940688: fixed in mcomix 1.2.1mcomix3+git20190616-1
has caused the Debian Bug report #940688,
regarding mcomix: Python 3 fork available
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.)


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

Package: mcomix
Version: 1.2.1-1.1
Severity: serious

There is a Python 3 fork available at
https://github.com/multiSnow/mcomix3

This also fixes #931645


-- System Information:
Debian Release: bullseye/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (200, 'experimental-debug'), (200, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_AU.UTF-8), LANGUAGE=en_GB:en_US (charmap=UTF-8) (ignored: LC_ALL set 
to en_AU.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages mcomix depends on:
ii  python2.7.16-1
ii  python-gtk2   2.24.0-6
ii  python-pil6.1.0-1
ii  python-pkg-resources  41.2.0-1

mcomix recommends no packages.

Versions of packages mcomix suggests:
ii  unrar  1:5.6.6-2

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: mcomix
Source-Version: 1.2.1mcomix3+git20190616-1

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

Debian distribution maintenance software
pp.
Emfox Zhou  (supplier of updated mcomix 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 22:26:02 +0800
Source: mcomix
Binary: mcomix
Architecture: source all
Version: 1.2.1mcomix3+git20190616-1
Distribution: unstable
Urgency: medium
Maintainer: Krzysztof Klimonda 
Changed-By: Emfox Zhou 
Description:
 mcomix - GTK+ image viewer for comic books
Closes: 931645 940688
Changes:
 mcomix (1.2.1mcomix3+git20190616-1) unstable; urgency=medium
 .
   * New upstream release
 - Switching to python3 port(mcomix3,unofficial) (Closes: #940688)
   * Update dependencies accordingly. (Closes: #931645)
   * Bump compat level to 12.
   * Bump debian policy to 4.4.1.
Checksums-Sha1:
 6453d3b06282e3b01d5c9395d8c181c0b24827c7 1928 
mcomix_1.2.1mcomix3+git20190616-1.dsc
 e47b9731c28581ef6c46c29e6578d4e99860d935 3037438 
mcomix_1.2.1mcomix3+git20190616.orig.tar.bz2
 f9481fa436c394f99481de6daaa1faf365d65c4d 3168 
mcomix_1.2.1mcomix3+git20190616-1.debian.tar.xz
 d587a5d689bf43d7fc2b15ae58fc84ac84512175 2637048 
mcomix_1.2.1mcomix3+git20190616-1_all.deb
 d5aac493d0b2eaf6f222bb7c9568a072b24a9c7f 5955 
mcomix_1.2.1mcomix3+git20190616-1_amd64.buildinfo
Checksums-Sha256:
 9563b676ef966b43c43c201b5a469fc2409293879c684ccc794958f615e04f49 1928 
mcomix_1.2.1mcomix3+git20190616-1.dsc
 5fe9ec6f4086045364cfa4b3d464b2af75bfbbd85a4b509141ea24b3435115cd 3037438 
mcomix_1.2.1mcomix3+git20190616.orig.tar.bz2
 f6404382f4129ed0735629b4d3163215527cf4ae379d5090aec24dab427ab6cf 3168 
mcomix_1.2.1mcomix3+git20190616-1.debian.tar.xz
 f662b727ff662e0af5241a80257095823ddc3a30f8c4dfdda3c806cd7ef78eff 2637048 
mcomix_1.2.1mcomix3+git20190616-1_all.deb
 ca16ed278cc02402b91c6ebda80f63885950d017fd3e9105ef899b3ae18e0157 5955 
mcomix_1.2.1mcomix3+git20190616-1_amd64.buildinfo
Files:
 71429d0c60a345eadab8569c14c9b973 1928 x11 optional 
mcomix_1.2.1mcomix3+git20190616-1.dsc
 7113f6706f8f3e6215128afab463a6fa 3037438 x11 optional 
mcomix_1.2.1mcomix3+git20190616.orig.tar.bz2
 054c6d6095df1a150676da3d0b8571ab 3168 x11 optional 
mcomix_1.2.1mcomix3+git20190616-1.debian.tar.xz
 b58006bda006d10f508a2a88cc06c4d3 2637048 x11 optional 
mcomix_1.2.1mcomix3+git20190616-1_all.deb
 729d248d3af7a23f5eba6534db9d0050 5955 x11 optional 

Bug#941890: python-clang-7: missing dependency on libclang-7-dev

[Andreas Beckmann]

On Mon, 7 Oct 2019 09:49:32 +0200 Sylvestre Ledru 
wrote:
> I fixed it from -8 (as -7 will go away soon)

But -7 is in stable, so it might be good to fix it there, too.

Andreas

Bug#943924: marked as done (matplotlib2: please stop build-depending on python-pandas)

[Debian Bug Tracking System]

Your message dated Wed, 13 Nov 2019 14:42:06 +
with message-id 
and subject line Bug#943924: fixed in matplotlib2 2.2.4-3
has caused the Debian Bug report #943924,
regarding matplotlib2: please stop build-depending on python-pandas
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.)


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

Package: python-matplotlib
Version: 2.2.4-2
Control: block 937296 by -1
Control: tags -1 patch

pandas upstream dropped Python 2 support in 0.25 (before adding Python 
3.8 support).  As further discussed in #937296, the Debian package 
python-pandas is currently part of a big tangle of circular 
(build-)dependencies, but can be cut out of that tangle by removing the 
build-dependencies from python-apptools and matplotlib2.


Hence, please drop the build-dependency on python-pandas.  (No other 
changes are required: it builds with the same 5 test failures as the 
existing version, and passes autopkgtests.)
--- End Message ---
--- Begin Message ---
Source: matplotlib2
Source-Version: 2.2.4-3

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 13 Nov 2019 08:59:52 -0500
Source: matplotlib2
Architecture: source
Version: 2.2.4-3
Distribution: unstable
Urgency: medium
Maintainer: Sandro Tosi 
Changed-By: Sandro Tosi 
Closes: 942538 943924
Changes:
 matplotlib2 (2.2.4-3) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Bump Standards-Version to 4.4.1.
 .
   [ Sandro Tosi ]
   * Drop -doc package, nudging people towards py3k matplotlib
   * debian/control
 - remove qt4 from b-d and d; Closes: #942538
 - remove pandas from b-d; Closes: #943924
 - remove some b-d no longer needed, mostly used for doc
Checksums-Sha1:
 5725826e24a63e2066920697c4e8ce1fb9af3cf0 3240 matplotlib2_2.2.4-3.dsc
 4da73db079116142a6f66b74f87aa31b303e5fa3 31360 
matplotlib2_2.2.4-3.debian.tar.xz
 06da0b651bb84f388304995ae31bae4f3340375c 18593 
matplotlib2_2.2.4-3_source.buildinfo
Checksums-Sha256:
 2de56e1be23b36b4b704198e10b51257033beffd6741fd5d79b1c3160451f482 3240 
matplotlib2_2.2.4-3.dsc
 648e06d1f39437eb1a1a7bf459cf81712ead3e3abda366528b61d4d43da8092e 31360 
matplotlib2_2.2.4-3.debian.tar.xz
 1422cf7fb33d34e680acb798bac008f5e608bf3d07dc01da76abd0dbdf64c556 18593 
matplotlib2_2.2.4-3_source.buildinfo
Files:
 67353e8f97f8ceda9dc29d40d16f1d9f 3240 python optional matplotlib2_2.2.4-3.dsc
 a0ab7323246a79f48fef973140f713e3 31360 python optional 
matplotlib2_2.2.4-3.debian.tar.xz
 c70917bae07a948d008458887a610e3b 18593 python optional 
matplotlib2_2.2.4-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAl3MDHoACgkQh588mTgB
qU+wvg//YPVrxI00xAIfPjwYNiaX3uxo/mAwqBJIOMkRWe3KSqbzlrfTNNcC4XQg
8YMwHsgS4CnLxUB3/xfvajkqVR8eudWUfSRNNLo/Ga2jUUVK5i25CUzgOitoq2+n
pMr01kEpQ/zEyGHFjDPKGJa4j7G3SNk5iU2yJWJpCQFBcS9IANBo2+Z90lIg4m4e
OoagfDSkR5qTge9OVyPY5N5gUKJb64n6/GVEIVo8XkmL2S81rcs3eIxuct4eopvq
UyDAMQfW6lmjKQ/9X3E8b7HeUG8rJCykuEzJIUhP44PAXsk2G77FGFjJHgdlIo6j
/gGZYWN085fh19TSPCqhJ61dvdq/CMsnDprr0b05QDR0D1NgGms04CNsvLHTIetU
HqF8ElB4Tr6KHTW+Lmt4oAi88nKJGd2FYK0W9VWsjNND+10rlTqD95yfmfSvMuX9
fNaT6qcPEhn2OBBYU0yJkU06lmaox5gghI22PWvrr7WXaxX0Aec9W6SHT05BU/Mg
jbchltI4LsIqenoKI41dLY549EaoDtH+FXfgDGXrXcyMpd/SPrtSSg1RBIDj+BWN
ISk0htPiExltvaw2WArbQNvd53jPYlA3cVRPSv9nbHjDw556OGemWY+Taqy43L1s
5oH110v/rRvph0kcv8voXi7W0Ze7xiVaQomx4b3OYLieyr49Tt0=
=s8uk
-END PGP SIGNATURE End Message ---

Bug#942538: marked as done (matplotlib2: Qt4 removal from Bullseye)

[Debian Bug Tracking System]

Your message dated Wed, 13 Nov 2019 14:42:06 +
with message-id 
and subject line Bug#942538: fixed in matplotlib2 2.2.4-3
has caused the Debian Bug report #942538,
regarding matplotlib2: Qt4 removal from 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.)


-- 
942538: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942538
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: matplotlib2
Version: 2.2.4-2
Severity: serious
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal

Dear Maintainer,

As you might know, we the Qt/KDE team are going to remove Qt 4 in Bullseye
cycle, as announced in [1].

As one of sub-tasks, we want to remove PyQt4 aka src:python-qt4. Currently
your package build-depends on python-qt4, and is one of few blockers for
its removal from testing.

Please get rid of this build-dependency. You can replace it with python-pyqt5
which will stay there a bit longer (but will eventually be removed as part
of Python 2 removal effort).

[1]: https://lists.debian.org/debian-devel-announce/2017/08/msg6.html

--
Dmitry Shachnev


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: matplotlib2
Source-Version: 2.2.4-3

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

Debian distribution maintenance software
pp.
Sandro Tosi  (supplier of updated matplotlib2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 13 Nov 2019 08:59:52 -0500
Source: matplotlib2
Architecture: source
Version: 2.2.4-3
Distribution: unstable
Urgency: medium
Maintainer: Sandro Tosi 
Changed-By: Sandro Tosi 
Closes: 942538 943924
Changes:
 matplotlib2 (2.2.4-3) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Bump Standards-Version to 4.4.1.
 .
   [ Sandro Tosi ]
   * Drop -doc package, nudging people towards py3k matplotlib
   * debian/control
 - remove qt4 from b-d and d; Closes: #942538
 - remove pandas from b-d; Closes: #943924
 - remove some b-d no longer needed, mostly used for doc
Checksums-Sha1:
 5725826e24a63e2066920697c4e8ce1fb9af3cf0 3240 matplotlib2_2.2.4-3.dsc
 4da73db079116142a6f66b74f87aa31b303e5fa3 31360 
matplotlib2_2.2.4-3.debian.tar.xz
 06da0b651bb84f388304995ae31bae4f3340375c 18593 
matplotlib2_2.2.4-3_source.buildinfo
Checksums-Sha256:
 2de56e1be23b36b4b704198e10b51257033beffd6741fd5d79b1c3160451f482 3240 
matplotlib2_2.2.4-3.dsc
 648e06d1f39437eb1a1a7bf459cf81712ead3e3abda366528b61d4d43da8092e 31360 
matplotlib2_2.2.4-3.debian.tar.xz
 1422cf7fb33d34e680acb798bac008f5e608bf3d07dc01da76abd0dbdf64c556 18593 
matplotlib2_2.2.4-3_source.buildinfo
Files:
 67353e8f97f8ceda9dc29d40d16f1d9f 3240 python optional matplotlib2_2.2.4-3.dsc
 a0ab7323246a79f48fef973140f713e3 31360 python optional 
matplotlib2_2.2.4-3.debian.tar.xz
 c70917bae07a948d008458887a610e3b 18593 python optional 
matplotlib2_2.2.4-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEufrTGSrz5KUwnZ05h588mTgBqU8FAl3MDHoACgkQh588mTgB
qU+wvg//YPVrxI00xAIfPjwYNiaX3uxo/mAwqBJIOMkRWe3KSqbzlrfTNNcC4XQg
8YMwHsgS4CnLxUB3/xfvajkqVR8eudWUfSRNNLo/Ga2jUUVK5i25CUzgOitoq2+n
pMr01kEpQ/zEyGHFjDPKGJa4j7G3SNk5iU2yJWJpCQFBcS9IANBo2+Z90lIg4m4e
OoagfDSkR5qTge9OVyPY5N5gUKJb64n6/GVEIVo8XkmL2S81rcs3eIxuct4eopvq
UyDAMQfW6lmjKQ/9X3E8b7HeUG8rJCykuEzJIUhP44PAXsk2G77FGFjJHgdlIo6j
/gGZYWN085fh19TSPCqhJ61dvdq/CMsnDprr0b05QDR0D1NgGms04CNsvLHTIetU
HqF8ElB4Tr6KHTW+Lmt4oAi88nKJGd2FYK0W9VWsjNND+10rlTqD95yfmfSvMuX9
fNaT6qcPEhn2OBBYU0yJkU06lmaox5gghI22PWvrr7WXaxX0Aec9W6SHT05BU/Mg
jbchltI4LsIqenoKI41dLY549EaoDtH+FXfgDGXrXcyMpd/SPrtSSg1RBIDj+BWN
ISk0htPiExltvaw2WArbQNvd53jPYlA3cVRPSv9nbHjDw556OGemWY+Taqy43L1s
5oH110v/rRvph0kcv8voXi7W0Ze7xiVaQomx4b3OYLieyr49Tt0=
=s8uk
-END PGP SIGNATURE End Message ---

Bug#944426: [Pkg-pascal-devel] Bug#944426: lazarus-src-2.0 fails to upgrade from 2.0.2+dfsg-7 to 2.0.6+dfsg-1: trying to overwrite filefindlaz.lpk

[Abou Al Montacir]

This is the same issue. This means that my changes do not catch all issues.
I'll have a look this WE. For those who want to take a look at the pre-inst
script (a few lines) which is probably the bug cause.
-- 
Cheers,
Abou Al Montacir


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

Processed: found 944628 in 1.1.1-4, tagging 944592, tagging 944593, tagging 944580, tagging 944599 ...

[Debian Bug Tracking System]

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

> found 944628 1.1.1-4
Bug #944628 [bugs-everywhere] Drop build dep on monotone
Marked as found in versions bugs-everywhere/1.1.1-4.
> tags 944592 + sid bullseye
Bug #944592 [src:ocaml-deriving-ocsigen] FTBFS with OCaml 4.08.1 (safe strings)
Added tag(s) bullseye and sid.
> tags 944593 + sid bullseye
Bug #944593 [src:pxp] FTBFS with OCaml 4.08.1 (Unbound module 
Odoc_html.StringSet)
Added tag(s) bullseye and sid.
> tags 944580 + experimental
Bug #944580 {Done: Adrian Bunk } [src:libprelude] libprelude 
FTBFS due to new gawk version
Added tag(s) experimental.
> tags 944599 + sid bullseye
Bug #944599 [src:ocaml-expect] FTBFS with OCaml 4.08.1 (safe strings)
Added tag(s) bullseye and sid.
> tags 944600 + sid bullseye
Bug #944600 [src:ocaml-melt] FTBFS with OCaml 4.08.1 (safe strings)
Added tag(s) sid and bullseye.
> tags 944626 + sid bullseye
Bug #944626 [src:diet-ng] diet-ng FTBFS on armhf: gdc: error: unrecognized 
command line option ‘-main’; did you mean ‘-Wmain’?
Added tag(s) bullseye and sid.
> found 944364 0.5.0-1.1
Bug #944364 [python3-augeas] dpkg: ldconfig is not invoked for Depends or even 
Pre-Depends
Marked as found in versions python-augeas/0.5.0-1.1.
> retitle 944431 berusky2: Segfault on startup
Bug #944431 [berusky2] Segfault on startup
Changed Bug title to 'berusky2: Segfault on startup' from 'Segfault on startup'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
944364: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944364
944431: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944431
944580: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944580
944592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944592
944593: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944593
944599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944599
944600: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944600
944626: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944626
944628: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944628
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

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

[Yves-Alexis Perez]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Tue, 2019-11-12 at 12:09 +0100, Mike Gabriel wrote:
> 
> As I haven't had any reply nor statement nor veto nor anything from any 
> of you on the above, here is what is going to happen, if noone interacts...

Hi Mike,

I'm unfortunately quite busy these days with a lot of stuff, and clearly the
various murrine themes are low priority for me. So I'll let you go ahead with
your plans, don't count on me for anything on this…

Thanks for the work anyway.

Regards,
- -- 
Yves-Alexis
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAl3MIMoACgkQ3rYcyPpX
RFvnjgf+OfjpnOdQXqv1QG0PCGz1ksaDqNG8g6elU1VlkFxP83ueo8xTkSoOSOtj
r3YoRbvLI1WSu62Dhl+szTtmKHwQG9jF4/Yy4WVAYiK9tzQNMt0bxJ40RFFebuNI
r9wOnLWUEISlaROtxRU86LMhgCzNTCUyjTmy+XKP7tZsZ9TOwy7ZymxsUpb6xlii
Nb4T0oRuBsQmcXizONDCe3yWjuy1JRwr9xZ60d+FGVW6sgqVLrkk0aoGZ1lBikKH
ddXNblZ46vtH3Y2f70eDRsxmJHNDE1yCcTtotFVNApPytVw8Tgsr8GvyRqliSFMh
xxSFGjAhXVxz24ReIEnOQ5Kpw5tD3A==
=E08z
-END PGP SIGNATURE-

Bug#944072: marked as done (tlsh: autopkgtest regression: No such file or directory: 'debian/tests/use-python-tlsh')

[Debian Bug Tracking System]

Your message dated Wed, 13 Nov 2019 15:37:56 +
with message-id 
and subject line Bug#944072: fixed in tlsh 3.4.4+20151206-1.3
has caused the Debian Bug report #944072,
regarding tlsh: autopkgtest regression: No such file or directory: 
'debian/tests/use-python-tlsh'
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.)


-- 
944072: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944072
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tlsh
Version: 3.4.4+20151206-1.2
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org, mo...@debian.org
User: debian...@lists.debian.org
Usertags: regression

Dear maintainers,

With a recent upload of tlsh the autopkgtest of tlsh fails in testing
when that autopkgtest is run with the binary packages of tlsh from
unstable. It passes when run with only packages from testing. In tabular
form:
   passfail
tlsh   from testing3.4.4+20151206-1.2
all others from testingfrom testing

I copied some of the output at the bottom of this report. @Sandro, it
seems you removed one file too many in your last NMU. The python3 test
uses the python2 code.

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=tlsh

https://ci.debian.net/data/autopkgtest/testing/amd64/t/tlsh/3323213/log.gz

autopkgtest [05:10:43]: test use-python3-tlsh: [---
Traceback (most recent call last):
  File
"/tmp/autopkgtest-lxc.cwk94dux/downtmp/build.nV3/src/debian/tests/use-python3-tlsh",
line 6, in 
globals = runpy.run_path('debian/tests/use-python-tlsh')
  File "/usr/lib/python3.7/runpy.py", line 261, in run_path
code, fname = _get_code_from_file(run_name, path_name)
  File "/usr/lib/python3.7/runpy.py", line 231, in _get_code_from_file
with open(fname, "rb") as f:
FileNotFoundError: [Errno 2] No such file or directory:
'debian/tests/use-python-tlsh'
autopkgtest [05:10:43]: test use-python3-tlsh: ---]



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: tlsh
Source-Version: 3.4.4+20151206-1.3

We believe that the bug you reported is fixed in the latest version of
tlsh, 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 tlsh 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 16:07:32 +0100
Source: tlsh
Architecture: source
Version: 3.4.4+20151206-1.3
Distribution: unstable
Urgency: medium
Maintainer: Jérémy Bobbio 
Changed-By: Mattia Rizzolo 
Closes: 944072
Changes:
 tlsh (3.4.4+20151206-1.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * d/control:
 + Move the git repository to salsa.debian.org.
 + Drop now unused X-Python-Version field.
   * Run wrap-and-sort.
   * Reinstate the actual python autopkgtests, accidentally removed in
 the previous upload.  Closes: #944072
Checksums-Sha1:
 b45e05389ead4ca70c51cab7e3636cfcaec17cb0 2175 tlsh_3.4.4+20151206-1.3.dsc
 86a65e17be84e108c396197cb00d7742dd500219 9372 
tlsh_3.4.4+20151206-1.3.debian.tar.xz
 315b754eef41c72dd27744b74c045447808167ab 9116 
tlsh_3.4.4+20151206-1.3_amd64.buildinfo
Checksums-Sha256:
 a8f736d1014a4a7e9615b0b91207ba0ad244b3d755754e35b46557e076eba8de 2175 
tlsh_3.4.4+20151206-1.3.dsc
 cbdc711cd550825d47de78da493c3199e8283a5d31e66cb4c7a675a2b2132f58 9372 
tlsh_3.4.4+20151206-1.3.debian.tar.xz
 734e6d3bec0dd399272917b67cc17750116f0ab163dd983c99df3609542622af 9116 
tlsh_3.4.4+20151206-1.3_amd64.buildinfo
Files:
 330b0bbb3d52bf93880c3827f42f2fbf 2175 admin optional 
tlsh_3.4.4+20151206-1.3.dsc
 8a8ca97de06a95a82fa270291d0b9fd4 9372 admin optional 
tlsh_3.4.4+20151206-1.3.debian.tar.xz
 5893e7b6bb34c8db8f05b54da76e8440 9116 admin optional 

Bug#940579: marked as done (ocaml-nox uninstallable: depends on libbinutils (< 2.32.51.20190728))

[Debian Bug Tracking System]

Your message dated Wed, 13 Nov 2019 16:37:16 +0100
with message-id <5b0410d2-a1b9-f2b1-2e5b-0aa6c73f6...@debian.org>
and subject line Re: found 940579 in 4.08.1-1
has caused the Debian Bug report #940579,
regarding ocaml-nox uninstallable: depends on libbinutils (< 2.32.51.20190728)
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.)


-- 
940579: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940579
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ocaml-nox
Version: 4.08.0-3
Severity: serious

Dear Maintainer,

ocaml-nox in experimental is currently uninstallable:

$ sudo apt -t experimental install ocaml-nox
[...]
The following packages have unmet dependencies:
  ocaml-nox : Depends: libbinutils (< 2.32.51.20190728) but 2.32.51.20190821-2 
is to be installed

Thanks
Kyle

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

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

Versions of packages ocaml-nox depends on:
ii  binutils2.32.51.20190909-1
ii  gcc 4:9.2.1-3.1
ii  libc6   2.29-1
ii  libncurses-dev [libncurses5-dev]6.1+20190803-1
ii  libncurses6 6.1+20190803-1
ii  libtinfo6   6.1+20190803-1
ii  ocaml-base-nox [ocaml-base-nox-4.05.0]  4.05.0-12
ii  ocaml-interp4.05.0-12
ii  zlib1g  1:1.2.11.dfsg-1+b1

Versions of packages ocaml-nox recommends:
ii  file  1:5.37-5

Versions of packages ocaml-nox suggests:
pn  ocaml-doc 
pn  tuareg-mode | ocaml-mode  

-- no debconf information
--- End Message ---
--- Begin Message ---
Le 13/11/2019 à 13:52, Andreas Beckmann a écrit :
>>> found 940579 4.08.1-1
>>
>> Why?
> 
> s.t. this does not show up as affecting stable etc. (RC bug with fixed
> but no found version)

OK. I've set the bug as:
- found in 4.08.0-3
- notfound in 4.08.1-1
- fixed in 4.08.1-1

which reflects the reality better.


Cheers,

-- 
Stéphane--- End Message ---

Bug#944671: orthanc-dicomweb: missing build on armel

[Ivo De Decker]

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

Bug#935941: marked as done (golang-github-getlantern: missing dependency on golang-github-getlantern-hex-dev)

[Debian Bug Tracking System]

Your message dated Wed, 13 Nov 2019 14:39:43 +
with message-id 
and subject line Bug#935941: fixed in golang-github-getlantern-hidden 
0.0~git20190325.f02dbb0-2
has caused the Debian Bug report #935941,
regarding golang-github-getlantern: missing dependency on 
golang-github-getlantern-hex-dev
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.)


-- 
935941: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935941
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-getlantern-hidden
Version: 0.0~git20190325.f02dbb0-1
Severity: serious
Tags: patch


Hello, your package FTBFS without the golang-github-getlantern-hex-dev 
dependency with:
dpkg-source: info: building golang-github-getlantern-hidden using existing 
./golang-github-getlantern-hidden_0.0~git20190325.f02dbb0.orig.tar.xz
dpkg-source: info: building golang-github-getlantern-hidden in 
golang-github-getlantern-hidden_0.0~git20190325.f02dbb0-1.debian.tar.xz
dpkg-source: info: building golang-github-getlantern-hidden in 
golang-github-getlantern-hidden_0.0~git20190325.f02dbb0-1.dsc
 debian/rules build
dh build --buildsystem=golang --with=golang
   dh_update_autotools_config -O--buildsystem=golang
   dh_autoreconf -O--buildsystem=golang
   dh_auto_configure -O--buildsystem=golang
   dh_auto_build -O--buildsystem=golang
cd obj-x86_64-linux-gnu && go install 
-gcflags=all=\"-trimpath=/golang-github-getlantern-hidden-0.0\~git20190325.f02dbb0/obj-x86_64-linux-gnu/src\"
 
-asmflags=all=\"-trimpath=/golang-github-getlantern-hidden-0.0\~git20190325.f02dbb0/obj-x86_64-linux-gnu/src\"
 -v -p 8 github.com/getlantern/hidden
src/github.com/getlantern/hidden/hidden.go:11:2: cannot find package 
"github.com/getlantern/hex" in any of:
/usr/lib/go-1.12/src/github.com/getlantern/hex (from $GOROOT)

/golang-github-getlantern-hidden-0.0~git20190325.f02dbb0/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-hidden-0.0\~git20190325.f02dbb0/obj-x86_64-linux-gnu/src\"
 
-asmflags=all=\"-trimpath=/golang-github-getlantern-hidden-0.0\~git20190325.f02dbb0/obj-x86_64-linux-gnu/src\"
 -v -p 8 github.com/getlantern/hidden returned exit code 1
make: *** [debian/rules:4: build] Error 255
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2


This patch fixes the issue: (note: I'm not sure about the runtime dependency)

diff -Nru 
golang-github-getlantern-hidden-0.0~git20190325.f02dbb0/debian/changelog 
golang-github-getlantern-hidden-0.0~git20190325.f02dbb0/debian/changelog
--- golang-github-getlantern-hidden-0.0~git20190325.f02dbb0/debian/changelog
2019-04-04 15:47:37.0 +0200
+++ golang-github-getlantern-hidden-0.0~git20190325.f02dbb0/debian/changelog
2019-08-28 10:11:02.0 +0200
@@ -1,3 +1,9 @@
+golang-github-getlantern-hidden (0.0~git20190325.f02dbb0-2) unstable; 
urgency=medium
+
+  * Add missing dependency on golang-github-getlantern-hex-dev (Closes: #-1)
+
+ -- Gianfranco Costamagna   Wed, 28 Aug 2019 
10:11:02 +0200
+
 golang-github-getlantern-hidden (0.0~git20190325.f02dbb0-1) unstable; 
urgency=medium
 
   * Initial release (Closes: 919946)
diff -Nru 
golang-github-getlantern-hidden-0.0~git20190325.f02dbb0/debian/control 
golang-github-getlantern-hidden-0.0~git20190325.f02dbb0/debian/control
--- golang-github-getlantern-hidden-0.0~git20190325.f02dbb0/debian/control  
2019-04-04 15:47:37.0 +0200
+++ golang-github-getlantern-hidden-0.0~git20190325.f02dbb0/debian/control  
2019-08-28 10:11:02.0 +0200
@@ -6,7 +6,8 @@
 Build-Depends: debhelper (>= 11),
dh-golang,
golang-any,
-   golang-github-stretchr-testify-dev
+   golang-github-stretchr-testify-dev,
+   golang-github-getlantern-hex-dev
 Standards-Version: 4.3.0
 Homepage: https://github.com/getlantern/hidden
 Vcs-Browser: 
https://salsa.debian.org/go-team/packages/golang-github-getlantern-hidden
@@ -17,7 +18,8 @@
 Package: golang-github-getlantern-hidden-dev
 Architecture: all
 Depends: ${misc:Depends},
- golang-github-stretchr-testify-dev
+ golang-github-stretchr-testify-dev,
+ golang-github-getlantern-hex-dev
 Description: Hide text in text
  hidden provides the ability to "hide" binary data in a string using a hex
  encoding with non-printing characters. Hidden data is demarcated with
--- End Message ---
--- Begin Message ---
Source: golang-github-getlantern-hidden
Source-Version: 

Bug#942101: python-msrest build accesses the network during the build

[Luca Boccassi]

Control: tags -1 patch

On Thu, 10 Oct 2019 14:01:46 +0200 Matthias Klose <
d...@debian.org
> wrote:
> Package: src:python-msrest
> Version: 0.6.1-1
> Severity: serious
> Tags: sid bullseye
> 
> according to
> 
https://launchpadlibrarian.net/441507516/buildlog_ubuntu-eoan-amd64.python-msrest_0.6.1-1_BUILDING.txt.gz

> 
> the tests access some infrastructure.  The build must not rely on the
network, 
> the autopkg tests can.  Usually the Debian buildds don't check for
network access.

Dear Maintainers,

I have opened an MR on Salsa to skip those tests at build time:

https://salsa.debian.org/python-team/modules/python-msrest/merge_requests/1

-- 
Kind regards,
Luca Boccassi


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

Processed: Re: python-msrest build accesses the network during the build

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #942101 [src:python-msrest] python-msrest build accesses the network during 
the build
Added tag(s) patch.

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

Processed: fixed 940579 in 4.08.1-1

[Debian Bug Tracking System]

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

> fixed 940579 4.08.1-1
Bug #940579 [ocaml-nox] ocaml-nox uninstallable: depends on libbinutils (< 
2.32.51.20190728)
Marked as fixed in versions ocaml/4.08.1-1.
> thanks
Stopping processing here.

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

Processed: found 940579 in 4.08.0-3

[Debian Bug Tracking System]

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

> found 940579 4.08.0-3
Bug #940579 [ocaml-nox] ocaml-nox uninstallable: depends on libbinutils (< 
2.32.51.20190728)
Marked as found in versions ocaml/4.08.0-3.
> thanks
Stopping processing here.

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

Processed: notfound 940579 in 4.08.1-1

[Debian Bug Tracking System]

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

> notfound 940579 4.08.1-1
Bug #940579 [ocaml-nox] ocaml-nox uninstallable: depends on libbinutils (< 
2.32.51.20190728)
No longer marked as found in versions ocaml/4.08.1-1.
> thanks
Stopping processing here.

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

Bug#937330: Remove pyoptical from Debian, upgrade psychopy to latest upstream to enable Pandas migration

[Andreas Tille]

Hi,

I stumbled upon pyoptical since its the only package that uses psychopy
which in turn is blocking the python-pandas migration to Python3.
Psychopy is extremely lagging behind upstream (which probably - not
checked might have switched to Python3).  From my point of view it
makes sense to

   1. Upgrade psychopy to latest upstream
   2. Remove pyoptical from Debian (dead upstream, low popcon anyway[1])

Any idea to otherwise smoothen the Pandas migration?

Kind regards

   Andreas.


[1] 
https://qa.debian.org/popcon-graph.php?packages=python-pyoptical_vote=on_legend=on_ticks=on_date=_date=_date=_fmt=%25Y-%25m=1

-- 
http://fam-tille.de

Processed: Bug#935941 marked as pending in golang-github-getlantern-hidden

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #935941 [src:golang-github-getlantern-hidden] golang-github-getlantern: 
missing dependency on golang-github-getlantern-hex-dev
Added tag(s) pending.

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

Bug#935941: marked as pending in golang-github-getlantern-hidden

[Andreas Henriksson]

Control: tag -1 pending

Hello,

Bug #935941 in golang-github-getlantern-hidden 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-hidden/commit/dcbbfca9c9d37d893a0e261744f429937cac9789


Add missing dependency on golang-github-getlantern-hex-dev

Closes: #935941


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/935941

Processed: mupen64plus-core: FTBFS against opencv 4.1: "No OpenCV development libraries found!" during debian/rules clean

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + libmupen64plus2
Bug #944668 [src:mupen64plus-core] mupen64plus-core: FTBFS against opencv 4.1: 
"No OpenCV development libraries found!" during debian/rules clean
Added indication that 944668 affects libmupen64plus2

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

Bug#943654: anbox: GUI crashes after "starting"

[Shengjing Zhu]

Control: tags -1 + moreinfo unreproducible
Control: severity -1 normal

On Sun, Oct 27, 2019 at 10:52 PM Shengjing Zhu  wrote:
>
> On Sun, Oct 27, 2019 at 10:48 PM Matheus Mello  
> wrote:
> >
> > Package: anbox
> > Version: 0.0~git20190124-1
> > Severity: grave
> > Justification: renders package unusable
> >
> > Dear Maintainer,
> >
> > Anbox does not start the Graphical Application after correctly installing 
> > the
> > Debian package. The application shows a boot image with "Starting", but it
> > crashes after a few seconds and the program turns unusable.
> >
>
> Have you ever followed the instructions in /usr/share/doc/anbox/README.Debian?
>
> Notably, is the Android image downloaded, and the status of two
> systemd services.
>
> Please run following commands and give back your results.
>
> ls /var/lib/anbox/android.img
> systemctl status anbox-container-manager.service
> systemctl --user status anbox-session-manager.service
>

Since I haven't received further reply, I'm going to downgrade the severity.

-- 
Shengjing Zhu

Processed: Re: Bug#943654: anbox: GUI crashes after "starting"

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo unreproducible
Bug #943654 [anbox] anbox: GUI crashes after "starting"
Added tag(s) moreinfo and unreproducible.
> severity -1 normal
Bug #943654 [anbox] anbox: GUI crashes after "starting"
Severity set to 'normal' from 'grave'

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

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

[Andreas Beckmann]

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

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

[Paul Gevers]

Source: deal.ii
Version: 9.1.1-6
Severity: serious
Tags: ftbfs sid bullseye
Justification: ftbfs

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear maintainer,

Your package is part of the assimp transition. I scheduled binNMU's but you
package fails to build everywhere it build in the past.

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?

Paul

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

Tail of log for deal.ii on amd64:

Source file was:

#include 

int main()
{
  int *i = new int;
  std::auto_ptr x(i);
  return 0;
}

dh_auto_configure: cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu 
"-DDEAL_II_CXX_FLAGS=-Wno-nonnull-compare -Wno-address" 
-DCMAKE_PREFIX_PATH=/usr/lib/x86_64-linux-gnu/hdf5/openmpi\;/usr/include/hdf5/openmpi
 -DCMAKE_BUILD_TYPE=DebugRelease -DDEAL_II_ALLOW_AUTODETECTION=OFF 
-DDEAL_II_ALLOW_BUNDLED=OFF -DDEAL_II_ALLOW_PLATFORM_INTROSPECTION=OFF 
-DDEAL_II_HAVE_FP_EXCEPTIONS=FALSE -DDEAL_II_COMPONENT_DOCUMENTATION=ON 
-DDEAL_II_WITH_ARPACK=ON -DDEAL_II_WITH_ASSIMP=ON -DDEAL_II_WITH_BOOST=ON 
-DDEAL_II_WITH_BZIP2=ON -DDEAL_II_WITH_GMSH=ON -DDEAL_II_WITH_GSL=ON 
-DDEAL_II_WITH_HDF5=ON -DDEAL_II_WITH_LAPACK=ON -DDEAL_II_WITH_MPI=ON 
-DDEAL_II_WITH_MUPARSER=ON -DDEAL_II_WITH_NETCDF=ON 
-DDEAL_II_WITH_OPENCASCADE=ON -DDEAL_II_WITH_P4EST=ON -DDEAL_II_WITH_PETSC=ON 
-DDEAL_II_WITH_SCALAPACK=ON -DDEAL_II_WITH_SLEPC=ON -DDEAL_II_WITH_SUNDIALS=ON 
-DDEAL_II_WITH_THREADS=ON -DDEAL_II_WITH_TRILINOS=ON -DDEAL_II_WITH_UMFPACK=ON 
-DDEAL_II_WITH_ZLIB=ON -DCMAKE_INSTALL_RPATH_USE_LINK_PATH=OFF 
-DDEAL_II_BASE_NAME=deal.ii 
-DDEAL_II_DOCHTML_RELDIR=share/doc/libdeal.ii-doc/html 
-DDEAL_II_DOCREADME_RELDIR=share/doc/libdeal.ii-doc 
-DDEAL_II_EXAMPLES_RELDIR=share/doc/libdeal.ii-doc/examples 
-DDEAL_II_LIBRARY_RELDIR=lib/x86_64-linux-gnu 
-DDEAL_II_PROJECT_CONFIG_RELDIR=share/cmake/deal.II 
-DDEAL_II_SHARE_RELDIR=share/deal.ii/ .. returned exit code 1
make[1]: *** [debian/rules:10: override_dh_auto_configure] Error 255
make[1]: Leaving directory '/<>'
make: *** [debian/rules:7: binary-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

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl3MWl4ACgkQnFyZ6wW9
dQrxEAf8CG69Mbfvso8sU1HZrRrDy4Qq7RB+vWDaWYd3MPuXGgsAS+B+h7oyqvJL
G6aCdWz9Z1YOXw5KLDi31R72O24GtBW5wqb9KKDWC049H3ACMXXIf6NU6+13Fsd+
iJZNOWn0C2MJ3KyJL5yrpTze+JAMOYHZXUqaT38EWcI1JoLqf7EchKKdTVPuNJLt
f9reZDe7/25D6e47BHOq5r1/PAkG5HhRe48v72adRW3LPIFY3l2NEv86nxzdfCoA
B4oQS+bDQTSHsct2y96ORkOpGfTBiwr9rq5uLU1dF66YXQQ+V7a09ZhOboUa48+x
+QeCc/XcN+/LADOH8dFWb0RnNhsECw==
=RTT1
-END PGP SIGNATURE-

Bug#885529: bumping severity of pygtk bugs

[Sudip Mukherjee]

Hi,

On Sun, Oct 06, 2019 at 05:09:30PM -0400, Jeremy Bicha wrote:
> Control: severity -1 serious
> Control: tags -1 -buster
> 
> 
> As part of the Python2 removal, it is our intent that pygtk will be removed 
> from Testing before the release of Debian 11
> "Bullseye". Therefore, I am bumping the severity of this bug to Serious to 
> ensure that there is plenty of warning before
> the Debian 11 release and to make the eventual removal of pygtk as smooth as 
> possible.

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.

--
Regards
Sudip

Bug#925799: marked as done (oss-preserve: ftbfs with GCC-9)

[Debian Bug Tracking System]

Your message dated Wed, 13 Nov 2019 21:29:21 +
with message-id 
and subject line Bug#925799: fixed in oss-preserve 1.1-6.1
has caused the Debian Bug report #925799,
regarding oss-preserve: 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.)


-- 
925799: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925799
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:oss-preserve
Version: 1.1-6
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/oss-preserve_1.1-6_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.

[...]
touch debian/stamp-autotools-files
chmod a+x /<>/./configure
mkdir -p .
cd . && CFLAGS="-g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security" CXXFLAGS="-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security" CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" 
LDFLAGS="-Wl,-z,relro" /<>/./configure --build=x86_64-linux-gnu 
--prefix=/usr --includedir="\${prefix}/include" --mandir="\${prefix}/share/man" 
--infodir="\${prefix}/share/info" --sysconfdir=/etc --localstatedir=/var 
--libexecdir="\${prefix}/lib/oss-preserve" --srcdir=. --disable-maintainer-mode 
--disable-dependency-tracking --disable-silent-rules
creating cache ./config.cache
checking for a BSD compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... yes
checking for working aclocal... found
checking for working autoconf... found
checking for working automake... found
checking for working autoheader... found
checking for working makeinfo... missing
checking whether to enable maintainer-specific portions of Makefiles... no
checking for gcc... gcc
checking whether the C compiler (gcc -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wl,-z,relro) works... yes
checking whether the C compiler (gcc -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wl,-z,relro) is a cross-compiler... no
checking whether we are using GNU C... yes
checking whether gcc accepts -g... yes
checking how to run the C preprocessor... gcc -E
checking whether gcc needs -traditional... no
checking for a BSD compatible install... /usr/bin/install -c
checking whether make sets ${MAKE}... (cached) yes
checking for pkg-config... yes
updating cache ./config.cache
creating ./config.status
creating Makefile
touch debian/stamp-autotools
/usr/bin/make -C . 
make[1]: Entering directory '/<>'
gcc -DPACKAGE=\"ossctl\" -DVERSION=\"1.1\"  -I. -I.-Wdate-time 
-D_FORTIFY_SOURCE=2 `pkg-config glib-2.0 --cflags` -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -c ossctl.c
ossctl.c: In function 'read_from_device':
ossctl.c:210:2: warning: comparison of constant '0' with boolean expression is 
always false [-Wbool-compare]
  210 |  < 0)
  |  ^
gcc `pkg-config glib-2.0 --cflags` -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -Wl,-z,relro -o 
ossctl `pkg-config glib-2.0 --libs` ossctl.o  
/usr/bin/ld: ossctl.o: in function `read_configuration':
./ossctl.c:108: undefined reference to `g_array_new'
/usr/bin/ld: ./ossctl.c:127: 

Bug#937330: Remove pyoptical from Debian, [or?] upgrade psychopy to latest upstream to enable Pandas migration

[Rebecca N. Palmer]

psychopy isn't blocking pandas' testing migration because psychopy 
already isn't in testing (for reasons unrelated to py2removal). 
Upstream say it's now Python 3 compatible [0], but I haven't tried to 
fix its other problems.


The ones that are blocking pandas [1] are python-skbio, 
python-feather-format and dask.


[0] https://github.com/psychopy/psychopy/blob/master/setup.cfg#22
[1] https://qa.debian.org/excuses.php?package=pandas (cnvkit since fixed)

Bug#944693: mailavenger: license incompatibility between 4-clause BSD and GPL

[Francesco Poli (wintermute)]

Package: mailavenger
Version: 0.8.5-2
Severity: serious
Justification: Policy 2.2.1

Hello,
I [noticed] that package mailavenger includes some files which are
derived from code originally released under the terms of the
4-clause BSD license, but their modifications are released under
the terms of the GNU GPL v2 or later, or anyway the files are part
of a whole released under the terms of the GNU GPL v3 or later.

[noticed]: 


The third clause in the 4-clause BSD license (the so-called "obnoxious
advertising clause") is incompatible with both the GNU GPL v2 and the
GNU GPL v3, as [stated] on the FSF license list.

[stated]: 

I believe this makes the package undistributable as is, hence
the "serious" severity of the bug report.


Luckily, the issue could be relatively easy to address.

As far as [libasync/convertint.C] and [libasync/suio_vuprintf.C]
are concerned, the parts covered by the 4-clause BSD license
are copyrighted by the The Regents of the University of California.
I think their general [re-licensing] applies, so the advertising
clause may be dropped: the code is effectively re-licensed under
the terms of the 3-clause BSD license (which is GPL-compatible!).

[libasync/convertint.C]: 

[libasync/suio_vuprintf.C]: 

[re-licensing]: 

As far as [libasync/getopt_long.c] and [util/getopt_long.c]
are concerned, the parts covered by the 4-clause BSD license
are copyrighted by the The NetBSD Foundation, Inc.
As far as I can tell, [NetBSD switched] to the 2-clause BSD license.
I am not 100 % sure this implies that any file copyrighted by
NetBSD Foundation under the 4-clause BSD license may now be effectively
considered as under the 2-clause BSD license (and thus
GPL-compatible!), but it may be worth getting in touch with
the Foundation and asking... I recommend doing so, in order to
get confirmation.

[libasync/getopt_long.c]: 

[util/getopt_long.c]: 

[NetBSD switched]: 


Please fix these issues.
Thanks for your time.

Bye!

Processed: reassign 934958 to osmalchemy

[Debian Bug Tracking System]

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

> reassign 934958 osmalchemy 0.1.+3-1
Bug #934958 [src:sqlalchemy, src:osmalchemy] sqlalchemy breaks osmalchemy 
(autopkgtest)
Bug reassigned from package 'src:sqlalchemy, src:osmalchemy' to 'osmalchemy'.
No longer marked as found in versions osmalchemy/0.1.+3-1 and 
sqlalchemy/1.3.5+ds1-2.
Ignoring request to alter fixed versions of bug #934958 to the same values 
previously set
Bug #934958 [osmalchemy] sqlalchemy breaks osmalchemy (autopkgtest)
There is no source info for the package 'osmalchemy' at version '0.1.+3-1' with 
architecture ''
Unable to make a source version for version '0.1.+3-1'
Marked as found in versions 0.1.+3-1.
> thanks
Stopping processing here.

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

Bug#917698: marked as done (libg15render: FTBFS: build-dependency not installable: libg15-dev)

[Debian Bug Tracking System]

Your message dated Wed, 13 Nov 2019 22:24:45 +0300
with message-id 

and subject line Fixed by reintroducing libg15
has caused the Debian Bug report #917698,
regarding libg15render: FTBFS: build-dependency not installable: libg15-dev
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.)


-- 
917698: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917698
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libg15render
Version: 1.3.0~svn316-2.4
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: cdbs, debhelper (>= 5), autotools-dev, libtool, 
> automake1.11, libg15-dev, libusb-dev, libfreetype6-dev, pkg-config, quilt
> Filtered Build-Depends: cdbs, debhelper (>= 5), autotools-dev, libtool, 
> automake1.11, libg15-dev, libusb-dev, libfreetype6-dev, pkg-config, quilt
> dpkg-deb: building package 'sbuild-build-depends-libg15render-dummy' in 
> '/<>/resolver-VTfJtN/apt_archive/sbuild-build-depends-libg15render-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy 
> sbuild-build-depends-libg15render-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-VTfJtN/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-VTfJtN/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-VTfJtN/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-VTfJtN/apt_archive ./ Sources [542 B]
> Get:5 copy:/<>/resolver-VTfJtN/apt_archive ./ Packages [626 B]
> Fetched 2131 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install libg15render build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-libg15render-dummy : Depends: libg15-dev but it is not 
> installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   
http://aws-logs.debian.net/2018/12/29/libg15render_1.3.0~svn316-2.4_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
The package builds now, after the libg15 package was reintroduced.--- End Message ---

Processed: Re: trace-cmd in debian

[Debian Bug Tracking System]

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

> fixed 885529 trace-cmd/2.8.3-1
Bug #885529 [src:trace-cmd] trace-cmd: Build-Depends on unmaintained pygtk
Marked as fixed in versions trace-cmd/2.8.3-1.
>
End of message, stopping processing here.

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

Processed: severity of 942514 is grave

[Debian Bug Tracking System]

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

> severity 942514 grave
Bug #942514 [src:pam-python] pam-python: CVE-2019-16729: local root escalation
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Processed: fixed 942514 in 1.0.6-1.1+deb10u1, fixed 942514 in 1.0.6-1.1+deb9u1

[Debian Bug Tracking System]

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

> fixed 942514 1.0.6-1.1+deb10u1
Bug #942514 [src:pam-python] pam-python: CVE-2019-16729: local root escalation
Marked as fixed in versions pam-python/1.0.6-1.1+deb10u1.
> fixed 942514 1.0.6-1.1+deb9u1
Bug #942514 [src:pam-python] pam-python: CVE-2019-16729: local root escalation
Marked as fixed in versions pam-python/1.0.6-1.1+deb9u1.
> thanks
Stopping processing here.

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

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)

[Mike Gabriel]

Hi Yves-Alexis,

thanks for your reply.

On  Mi 13 Nov 2019 16:27:06 CET, Yves-Alexis Perez wrote:


On Tue, 2019-11-12 at 12:09 +0100, Mike Gabriel wrote:


As I haven't had any reply nor statement nor veto nor anything from any
of you on the above, here is what is going to happen, if noone interacts...


Hi Mike,

I'm unfortunately quite busy these days with a lot of stuff, and clearly the
various murrine themes are low priority for me. So I'll let you go ahead with
your plans, don't count on me for anything on this…


Ok. Thanks.


Thanks for the work anyway.


Thanks for the appreciation.

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.

Thanks + Greets,
Mike

[1]  
https://salsa.debian.org/desktop-themes-team/numix-gtk-theme/commit/765624c473612866ab9227a41d0592816154e00e

--

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



pgp0nhHxjdfc8.pgp
Description: Digitale PGP-Signatur

Bug#944692: thin-provisioning-tools version 0.7.6-2.1 FTBFS

[Lucas Kanashiro]

I submitted a merge request on salsa which fixes this issue (and some 
others): 
https://salsa.debian.org/lvm-team/thin-provisioning-tools/merge_requests/2


Thanks for considering this!

--
Lucas Kanashiro

Bug#944431: marked as done (berusky2: Segfault on startup)

[Debian Bug Tracking System]

Your message dated Thu, 14 Nov 2019 00:05:23 +
with message-id 
and subject line Bug#944431: fixed in berusky2 0.10-8
has caused the Debian Bug report #944431,
regarding berusky2: Segfault on startup
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.)


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

Hello,

thank you for packaging berusky2.

I wanted to try the game but it segfaults on startup, after showing the cinemax
logo. The stack trace is sadly not really helpful:

  Thread 1 "berusky2" received signal SIGSEGV, Segmentation fault.
  0x555d892e in ?? ()
  (gdb) where
  #0  0x555d892e in ?? ()
  #1  0x556305e4 in ?? ()
  #2  0x556306a9 in ?? ()
  #3  0x5557d374 in ?? ()
  #4  0x555bd1b7 in ?? ()
  #5  0x55561293 in main ()

The stdout/stderr output when launching the game is this:

Checking /home/enrico/.berusky2/...ok
Checking /home/enrico/.berusky2/Save/...ok
Checking /home/enrico/.berusky2/Save/profiles/...ok
Checking ~/.berusky2/berusky3d.ini...OK
Trying to open ini file at /home/enrico/.berusky2//berusky3d.ini...OK
SDL Init...
Init video surface...

Screen resolution 1024x768
Color depth 32 bits
Fullscreen = 0
OpenGL = 0

Creating screen...
Loading extensions...
OpenGL Vendor: Intel Open Source Technology Center
OpenGL Renderer: Mesa DRI Intel(R) HD Graphics 620 (Kaby Lake GT2) 
OpenGL Version: 3.0 Mesa 18.3.6

Availabile extensions:
GL_ARB_multisample
GL_EXT_abgr
GL_EXT_bgra
GL_EXT_blend_color
GL_EXT_blend_minmax
GL_EXT_blend_subtract
GL_EXT_copy_texture
GL_EXT_subtexture
GL_EXT_texture_object
GL_EXT_vertex_array
GL_EXT_compiled_vertex_array
GL_EXT_texture
GL_EXT_texture3D
GL_IBM_rasterpos_clip
GL_ARB_point_parameters
GL_EXT_draw_range_elements
GL_EXT_packed_pixels
GL_EXT_point_parameters
GL_EXT_rescale_normal
GL_EXT_separate_specular_color
GL_EXT_texture_edge_clamp
GL_SGIS_generate_mipmap
GL_SGIS_texture_border_clamp
GL_SGIS_texture_edge_clamp
GL_SGIS_texture_lod
GL_ARB_framebuffer_sRGB
GL_ARB_multitexture
GL_EXT_framebuffer_sRGB
GL_IBM_multimode_draw_arrays
GL_IBM_texture_mirrored_repeat
GL_3DFX_texture_compression_FXT1
GL_ARB_texture_cube_map
GL_ARB_texture_env_add
GL_ARB_transpose_matrix
GL_EXT_blend_func_separate
GL_EXT_fog_coord
GL_EXT_multi_draw_arrays
GL_EXT_secondary_color
GL_EXT_texture_env_add
GL_EXT_texture_filter_anisotropic
GL_EXT_texture_lod_bias
GL_INGR_blend_func_separate
GL_NV_blend_square
GL_NV_light_max_exponent
GL_NV_texgen_reflection
GL_NV_texture_env_combine4
GL_S3_s3tc
GL_SUN_multi_draw_arrays
GL_ARB_texture_border_clamp
GL_ARB_texture_compression
GL_EXT_framebuffer_object
GL_EXT_texture_compression_s3tc
GL_EXT_texture_env_combine
GL_EXT_texture_env_dot3
GL_MESA_window_pos
GL_NV_packed_depth_stencil
GL_NV_texture_rectangle
GL_ARB_depth_texture
GL_ARB_occlusion_query
GL_ARB_shadow
GL_ARB_texture_env_combine
GL_ARB_texture_env_crossbar
GL_ARB_texture_env_dot3
GL_ARB_texture_mirrored_repeat
GL_ARB_window_pos
GL_EXT_stencil_two_side
GL_EXT_texture_cube_map
GL_NV_depth_clamp
GL_NV_fog_distance
GL_APPLE_packed_pixels
GL_ARB_draw_buffers
GL_ARB_fragment_program
GL_ARB_fragment_shader
GL_ARB_shader_objects
GL_ARB_vertex_program
GL_ARB_vertex_shader
GL_ATI_draw_buffers
GL_ATI_texture_env_combine3
GL_ATI_texture_float
GL_EXT_shadow_funcs
GL_EXT_stencil_wrap
GL_MESA_pack_invert
GL_NV_primitive_restart
GL_ARB_depth_clamp
GL_ARB_fragment_program_shadow
GL_ARB_half_float_pixel
GL_ARB_occlusion_query2
GL_ARB_point_sprite
GL_ARB_shading_language_100
GL_ARB_sync
GL_ARB_texture_non_power_of_two
GL_ARB_vertex_buffer_object
GL_ATI_blend_equation_separate
GL_EXT_blend_equation_separate
GL_OES_read_format
GL_ARB_color_buffer_float
GL_ARB_pixel_buffer_object
GL_ARB_texture_compression_rgtc
GL_ARB_texture_float
GL_ARB_texture_rectangle
GL_EXT_packed_float
GL_EXT_pixel_buffer_object
GL_EXT_texture_compression_dxt1
GL_EXT_texture_compression_rgtc
GL_EXT_texture_rectangle
GL_EXT_texture_sRGB
GL_EXT_texture_shared_exponent
GL_ARB_framebuffer_object
GL_EXT_framebuffer_blit
GL_EXT_framebuffer_multisample
GL_EXT_packed_depth_stencil
GL_APPLE_object_purgeable
GL_ARB_vertex_array_object
GL_ATI_separate_stencil
GL_EXT_draw_buffers2
GL_EXT_draw_instanced
GL_EXT_gpu_program_parameters
GL_EXT_texture_array
GL_EXT_texture_integer
GL_EXT_texture_sRGB_decode
GL_EXT_timer_query
GL_OES_EGL_image
GL_ARB_copy_buffer
GL_ARB_depth_buffer_float
GL_ARB_draw_instanced
GL_ARB_half_float_vertex
GL_ARB_instanced_arrays

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

[Cyril Brulebois]

Package: ftp.debian.org
Severity: serious
Justification: breaks image generation tools

Hi,

I've mentioned this on #debian-ftp already, but filing a bug report in
addition to make sure it's not lost.

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.

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?


Cheers,
-- 
Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/

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

[Cyril Brulebois]

Cyril Brulebois  (2019-11-14):
> 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.

For completeness, this is tracked in #944697.


Cheers,
-- 
Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/


signature.asc
Description: PGP signature

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

[Cyril Brulebois]

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 Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/

Bug#944651: gcl: FTBFS on ppc64el

[Camm Maguire]

Greetings, and thanks!  I'm on it...

Take care,

Ivo De Decker  writes:

> package: src:gcl
> version: 2.6.12-88
> severity: serious
> tags: ftbfs
>
> Hi,
>
> The latest upload of gcl to unstable fails on ppc64el:
>
> https://buildd.debian.org/status/package.php?p=gcl
>
> I suspect the FTBFS of acl2 is related.
>
> Cheers,
>
> Ivo
>
>
>

-- 
Camm Maguirec...@maguirefamily.org
==
"The earth is but one country, and mankind its citizens."  --  Baha'u'llah

Bug#944431: marked as pending in berusky2

[Markus Koschany]

Control: tag -1 pending

Hello,

Bug #944431 in berusky2 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/games-team/berusky2/commit/d253ecdf60c7bbe6a431faced3198f503c1d8929


Build with no optimization to avoid a segfault with GCC 9.

Closes: #944431
Thanks: Enrico Zini for the report.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/944431

Processed: Bug#944431 marked as pending in berusky2

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #944431 [berusky2] berusky2: Segfault on startup
Added tag(s) pending.

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

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

[Pirate Praveen]

Control: retitle -1 gitlab ssh access broken with protobuf 3.10
Control: severity -1 serious

On ബു, Nov 13, 2019 at 23:44, Pirate Praveen 
 wrote:

On Mon, 11 Nov 2019 22:15:20 +0530 Pirate Praveen
mailto:prav...@onenetbeyond.org>> wrote:

 Control: retitle -1 ssh access fails with gitaly-upload-pack: fatal:
 error: %v
 On Sat, 2 Nov 2019 14:51:42 +0100 Romain Bignon > wrote:

 > Hello,
 >
 > The problem is still here, and is so not related to compatibility 
between

 > versions of gitlab/gitlab-shell/gitality…
 >
 > Is there anything I can do to find the origin of this issue?

 Fortunately or unfortunately the same error hit my instance as 
well. I'm

 digging deeper into it now.

 As a workaround you can use https access till we fix this (only ssh
 access is affected).


Found the root cause to be ruby-google-protobuf update from 3.7 to 
3.10.

But to actually get it work is tricky.

If we downgrade ruby-google-protobuf to 3.7.1, then gitaly fails to 
build.


 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

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

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 gitlab ssh access broken with protobuf 3.10
Bug #942633 [gitlab] ssh access fails with gitaly-upload-pack: fatal:
Changed Bug title to 'gitlab ssh access broken with protobuf 3.10' from 'ssh 
access fails with gitaly-upload-pack: fatal:'.
> severity -1 serious
Bug #942633 [gitlab] gitlab ssh access broken with protobuf 3.10
Severity set to 'serious' from 'grave'

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

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)

[Yves-Alexis Perez]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

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
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAl3M/F0ACgkQ3rYcyPpX
RFvtLggAtPb/BMDo5FtGG1Z51pEqRbrfijD0ad16ymSR5PUoxReL5aVL5Ygt3zFX
b1Pgn3fH9FFAsE6guzo59WfK51+erWSGI52t3AEWOCdenAU4GKfBUSs6HyU9WmAk
Bii5Hre2Cu/hsyOWcm28pXhtvK3SwLqA7GKxK2r1xIOV1rhIFcziLFF7KohcO66i
/EV/xkK+pVv1JYY/hMx+wvGIaKVIhurHyusj0AaUx5b5QgQ6aWYcWw7PsBRcv+Fr
FHjyxLLM6WePaFBjdBCoKy3bXpVJG54r8Shtj3L4d+zK42r8GcUf2qt8pGH9dYk0
6KbO+P+VHKoALQLyNRlxdvglnmsZBg==
=ZlSB
-END PGP SIGNATURE-

Processed: Re: broken with pandas 0.25

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #944042 [python3-skbio] python3-skbio: FTBFS and autopkgtest fail with 
pandas 0.25
Severity set to 'serious' from 'important'

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

Processed: Re: broken with pandas 0.25

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #944043 [src:q2-types] q2-types: autopkgtest fail with pandas 0.25
Severity set to 'serious' from 'important'

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

Processed: Re: trace-cmd: Python2 removal in sid/bullseye

[Debian Bug Tracking System]

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

> fixed 938691 trace-cmd/2.8.3-1
Bug #938691 [src:trace-cmd] trace-cmd: Python2 removal in sid/bullseye
Marked as fixed in versions trace-cmd/2.8.3-1.
>
End of message, stopping processing here.

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

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

[Sudip Mukherjee]

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.

--
Regards
Sudip

Bug#944706: firefox-esr: Tab crashes immediately after start up and Firefox ESR was unusable.

[ISHIKAWA,chiaki]

Package: firefox-esr
Version: 68.2.0esr-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I don't know where to report, but I want to share an experience and
possible workaround.

I hav filed a mozilla bugzilla entry:
https://bugzilla.mozilla.org/show_bug.cgi?id=1596338
Bug 1596338
firefox-esr 68.2.0.ESR startup error under Debian GNU/Linux

My debian kernel version is:
$ uname -a
Linux ip030 5.2.0-3-amd64 #1 SMP Debian 5.2.17-1 (2019-09-26) x86_64 
GNU/Linux


I am using a testing package of Debian. So, that may be one of the
reasons of ill-behavior.

SYMPTOM of the problem:

(1) I upgraded my Debian GNU/Linux packages, and firefox seemed to
updated itself some days ago or yesterday, I am not sure when.

When I tried to run Firefox for the first time after these events by
invoking it from the application menu maybe for the first time in a
few days, Firefox was not usable because any tab including the startup
tab(s) that I wanted to create crashed, and firefox displayed the
error message and offered to close the tab or restore the tab.

Since the tab(s) crashed immediately after startup, if I closed the
tab, Firefox terminated.
If I tried to restore the tabs, this again resulted in the same tab
crashing dialog screen page.  There was no way out.

(2) Another bug I noticed is incorrect link in the help dialog.

I get Page not found error when I clicked on the "What's New" link:

HELP -> About Firefox -> What's New link

I get Page not Found error.

The page shown with BIG "Whoops1" message has URL:
https://www.mozilla.org/en-US/und/firefox/68.2.0/releasenotes/?utm_campaign=whatsnew_medium=firefox-browser_source=firefox-browser

If I delete the "/und" part manually and hit return in the URL bar,
I think the correct page s being accessed.
(I am not sure if the incorrect URL is Debian-specific or originated
in the mozilla binary.)

In then accessed page I see clearly the following message. So it *IS*
the release note.

--- begin quote

Firefox ESR
Release Notes

Release Notes tell you what’s new in Firefox. As always, we welcome
your feedback. You can also file a bug in Bugzilla or see the system
requirements of this release.

    Desktop
    Android
    iOS
    Pre-releases

68.2.0
Firefox ESR

October 22, 2019
Version 68.2.0, first offered to ESR channel users on October 22, 2019

--- end quote



ERROR messages:
While the error in (1) was observed, I saw something like the
following (quoted/pasted at the end of this memo.)
in the startup console where I typed /usr/bin/firefox-esr

Possible Workaround ??? :

I found a solution by accident. I have no idea if this works for everybody.

I tried to restart Firefox after disabling plugin, i.e., safe-mode
from the menu.
This operation failed again and no window was created.
Usually Firefox restart after disabling plugins. But I saw no such
window and there does not seem to be any live firefox process anymore.

ps axg | grep firefox

does not show firefox process.

So, after this, I ran firefox-esr again by typing the command line
this time.  To my relief, this time no tab crashed error screen
appeared, and I can access google search, for example eventually.
Something, maybe some profile or whatever, was changed for the better
(?) is my best guess.

Just thought to share my experience.

---
Note; Some error messages that appeared on the command tty window where I
typed
firefox-esr to start Firefox.

Error messages uring the error (1) above:

$ firefox-esr
IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: 
PLayerTransaction::Msg_ReleaseLayer Processing error: message was 
deserialized, but the handler returned false (indicating failure)


IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: 
PLayerTransaction::Msg_ReleaseLayer Processing error: message was 
deserialized, but the handler returned false (indicating failure)


IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: 
PLayerTransaction::Msg_ReleaseLayer Processing error: message was 
deserialized, but the handler returned false (indicating failure)


IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: 
PLayerTransaction::Msg_ReleaseLayer Processing error: message was 
deserialized, but the handler returned false (indicating failure)


IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: 
PLayerTransaction::Msg_ReleaseLayer Processing error: message was 
deserialized, but the handler returned false (indicating failure)


IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: 
PLayerTransaction::Msg_ReleaseLayer Processing error: message was 
deserialized, but the handler returned false (indicating failure)


IPDL protocol error: Handler returned error code!

###!!! [Parent][DispatchAsyncMessage] Error: 

Processed: tagging 925708

[Debian Bug Tracking System]

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

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

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