Bug#875547: animals: can't be played as non root user

[Aaron Howell]

Package: animals
Version: 201207131226-2+b1
Severity: grave
Justification: renders package unusable

The game tries to write its database in /var/games/animals, and segfaults on 
startup when it can't.
it needs to either be setuid/gid to a user that can write to that location (but 
do nothing else),
or it should use a local database in the user's home directory.
At the moment it can only be played as root.


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

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

Versions of packages animals depends on:
ii  libc6   2.24-12ubuntu1
ii  libdb5.3++  5.3.28-13.1
ii  libgcc1 1:7.2.0-3ubuntu1
ii  libstdc++6  7.2.0-3ubuntu1

animals recommends no packages.

animals suggests no packages.

-- no debconf information

Bug#852587: marked as done (wader: Update udevadm path)

[Debian Bug Tracking System]

Your message dated Tue, 12 Sep 2017 04:18:08 +
with message-id 
and subject line Bug#875484: Removed package(s) from unstable
has caused the Debian Bug report #852587,
regarding wader: Update udevadm path
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.)


-- 
852587: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852587
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wader
Version: 0.5.13-1
Severity: normal
User: pkg-systemd-maintain...@lists.alioth.debian.org
Usertags: udevadm

Hi,

since Jessie, the udevadm binary is available as /bin/udevadm.
To not break existing scripts, which use the old /sbin/udevadm path,
the udev package currently ships a compat symlink which we would like
to drop eventually (in buster or buster+1).

According to codesearch [1] your package wader does hard-code the
udevadm path as /sbin/udevadm.

Please change that to /bin/udevadm.

Thanks for considering.

Michael,
on behalf of the pkg-systemd team.

[1] https://codesearch.debian.net/search?q=%2Fsbin%2Fudevadm
--- End Message ---
--- Begin Message ---
Version: 0.5.13-1+rm

Dear submitter,

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

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

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

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

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

Bug#875447: marked as done (emacs25: enriched text remote code execution)

[Debian Bug Tracking System]

Your message dated Tue, 12 Sep 2017 03:49:24 +
with message-id 
and subject line Bug#875447: fixed in emacs25 25.2+1-6
has caused the Debian Bug report #875447,
regarding emacs25: enriched text remote code execution
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.)


-- 
875447: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875447
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: emacs25
Version: 25.1+1-4
Severity: grave
Tags: patch upstream security
Justification: user security hole
Forwarded: https://bugs.gnu.org/28350
Control: clone -1 -2 -3
Control: reassign -2 src:emacs24 24.4+1-4
Control: retitle -2 emacs24: enriched text remote code execution
Control: reassing -3 src:emacs23 23.4+1-4
Control: retitle -3 emacs23: enriched text remote code execution

Hi

See http://www.openwall.com/lists/oss-security/2017/09/11/1 for
details. The bug has been reported upstream at:

https://bugs.gnu.org/28350

Upstream commit:

https://git.savannah.gnu.org/cgit/emacs.git/commit/?h=emacs-25=9ad0fcc54442a9a01d41be19880250783426db70

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: emacs25
Source-Version: 25.2+1-6

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

Debian distribution maintenance software
pp.
Rob Browning  (supplier of updated emacs25 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: Mon, 11 Sep 2017 21:51:49 -0500
Source: emacs25
Binary: emacs25-lucid emacs25-lucid-dbg emacs25-nox emacs25-nox-dbg emacs25 
emacs25-dbg emacs25-bin-common emacs25-common emacs25-el
Architecture: source amd64 all
Version: 25.2+1-6
Distribution: unstable
Urgency: high
Maintainer: Rob Browning 
Changed-By: Rob Browning 
Description:
 emacs25- GNU Emacs editor (with GTK+ GUI support)
 emacs25-bin-common - GNU Emacs editor's shared, architecture dependent files
 emacs25-common - GNU Emacs editor's shared, architecture independent 
infrastructur
 emacs25-dbg - Debugging symbols for emacs25
 emacs25-el - GNU Emacs LISP (.el) files
 emacs25-lucid - GNU Emacs editor (with Lucid GUI support)
 emacs25-lucid-dbg - Debugging symbols for emacs25-lucid
 emacs25-nox - GNU Emacs editor (without GUI support)
 emacs25-nox-dbg - Debugging symbols for emacs25-nox
Closes: 875447
Changes:
 emacs25 (25.2+1-6) unstable; urgency=high
 .
   * Block remote code execution via enriched text.  Add
 0012-A-remote-execution-exploit-via-enriched-text-has-bee.patch to
 fix the problem.  Thanks to David Bremner for the alert and
 Salvatore Bonaccorso for reporting the problem to Debian.
 (Closes: 875447)
Checksums-Sha1:
 4a679c00cb84d32541ff89a1681b0a0e92291379 2827 emacs25_25.2+1-6.dsc
 3ec8f3e6d567aae1e26fab79c3ace01a23f93062 53580 emacs25_25.2+1-6.debian.tar.xz
 8aaeddc33e0d2489c326859c22ae9a330552e094 287520 
emacs25-bin-common-dbgsym_25.2+1-6_amd64.deb
 d5470641b7c22b41417277420798e6e3470c1069 152804 
emacs25-bin-common_25.2+1-6_amd64.deb
 c05cf4bc62c37fb375dfadc6e1d1a687449faf28 13165534 
emacs25-common_25.2+1-6_all.deb
 a2e96c3bfca681afc9ddfd743372511608ef259b 5215368 emacs25-dbg_25.2+1-6_amd64.deb
 72dd52a7b8fbad98cdd09d276e434dc2ce485bee 15662486 emacs25-el_25.2+1-6_all.deb
 b0766c0b66a02bb7448f6ffe6f94a2ac0e630860 5307892 
emacs25-lucid-dbg_25.2+1-6_amd64.deb
 c68a7598e5aeb09c2cfb1dea930ae452cc703b2c 3511184 
emacs25-lucid_25.2+1-6_amd64.deb
 9bd0e34fe90a401e5d73babee3998f4f242178b5 3679566 
emacs25-nox-dbg_25.2+1-6_amd64.deb
 d071c942961d32c1fca357fe8122729a6703748f 3082952 emacs25-nox_25.2+1-6_amd64.deb
 fa98a785afaa790c06c81afb07db0be843131b6f 19498 emacs25_25.2+1-6_amd64.buildinfo
 e9fa60bff8e08f0f5b16ae306cc5b60645812e3f 3504984 emacs25_25.2+1-6_amd64.deb
Checksums-Sha256:
 0fd364f2c708d3790e7acd59dbfb9ede0753cd4a5ae9b571d055d23a690b98fd 2827 
emacs25_25.2+1-6.dsc
 c3e31961fd96cd0eb56b0949a797463208338ac6a76e101f77ed8cad7465b4ef 53580 
emacs25_25.2+1-6.debian.tar.xz
 

Bug#875538: jupyter-nbextension-jupyter-js-widgets: fails to configure: json.decoder.JSONDecodeError

[Norbert Preining]

Package: jupyter-nbextension-jupyter-js-widgets
Version: 6.0.0-2
Severity: serious

Dear maintainer, 

the package consistently fails to configure with the following error:

Setting up jupyter-nbextension-jupyter-js-widgets (6.0.0-2) ...
/usr/lib/python3.5/runpy.py:125: RuntimeWarning: 'notebook.nbextensions' found 
in sys.modules after import of package 'notebook', but prior to execution of 
'notebook.nbextensions'; this may result in unpredictable behaviour
  warn(RuntimeWarning(msg))
Enabling notebook extension jupyter-js-widgets/extension...
Traceback (most recent call last):
  File "/usr/lib/python3.5/runpy.py", line 193, in _run_module_as_main
"__main__", mod_spec)
  File "/usr/lib/python3.5/runpy.py", line 85, in _run_code
exec(code, run_globals)
  File "/usr/lib/python3/dist-packages/notebook/nbextensions.py", line 1176, in 

main()
  File "/usr/lib/python3/dist-packages/jupyter_core/application.py", line 267, 
in launch_instance
return super(JupyterApp, cls).launch_instance(argv=argv, **kwargs)
  File "/usr/lib/python3/dist-packages/traitlets/config/application.py", line 
658, in launch_instance
app.start()
  File "/usr/lib/python3/dist-packages/notebook/nbextensions.py", line 961, in 
start
super(NBExtensionApp, self).start()
  File "/usr/lib/python3/dist-packages/jupyter_core/application.py", line 256, 
in start
self.subapp.start()
  File "/usr/lib/python3/dist-packages/notebook/nbextensions.py", line 871, in 
start
self.toggle_nbextension(self.extra_args[0])
  File "/usr/lib/python3/dist-packages/notebook/nbextensions.py", line 861, in 
toggle_nbextension
logger=self.log)
  File "/usr/lib/python3/dist-packages/notebook/nbextensions.py", line 407, in 
enable_nbextension
logger=logger)
  File "/usr/lib/python3/dist-packages/notebook/nbextensions.py", line 345, in 
_set_nbextension_state
cm.update(section, {"load_extensions": {require: state}})
  File "/usr/lib/python3/dist-packages/traitlets/config/manager.py", line 85, 
in update
data = self.get(section_name)
  File "/usr/lib/python3/dist-packages/traitlets/config/manager.py", line 63, 
in get
return json.load(f)
  File "/usr/lib/python3.5/json/__init__.py", line 268, in load
parse_constant=parse_constant, object_pairs_hook=object_pairs_hook, **kw)
  File "/usr/lib/python3.5/json/__init__.py", line 319, in loads
return _default_decoder.decode(s)
  File "/usr/lib/python3.5/json/decoder.py", line 339, in decode
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/usr/lib/python3.5/json/decoder.py", line 357, in raw_decode
raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
dpkg: error processing package jupyter-nbextension-jupyter-js-widgets 
(--configure):
 subprocess installed post-installation script returned error exit status 1


Thanks

Norbert

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

Kernel: Linux 4.12.0 (SMP w/4 CPU cores)
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)

Versions of packages jupyter-nbextension-jupyter-js-widgets depends on:
ii  python2.7.13-2
ii  python-notebook   4.2.3-4
ii  python3   3.5.3-3
ii  python3-notebook  4.2.3-4

jupyter-nbextension-jupyter-js-widgets recommends no packages.

Versions of packages jupyter-nbextension-jupyter-js-widgets suggests:
iu  python-ipywidgets   6.0.0-2
iu  python3-ipywidgets  6.0.0-2

-- no debconf information

Bug#875535: sambamba: FTBFS: Segmentation fault

[Nobuhiro Iwamatsu]

Package: sambamba
Version: 0.6.6-1
Severity: serious
Tags: buster sid
Justification: FTBFS on amd64

Dear Maintainer,

sambamba FTBFS on sid.

https://buildd.debian.org/status/fetch.php?pkg=sambamba=amd64=0.6.6-1%2Bb1=1504167027=0

--
Build targets in project: 2
   dh_auto_build -a -O--buildsystem=meson
ninja -j4 -v
[1/74] ldc2  -Isambamba@exe -I. -I.. -I/usr/include/d/
-I/usr/include/htslib -enable-color -O3 -g -release  -of
'sambamba@exe/main.d.o' -c ../main.d
../sambamba/utils/common/readstorage.d(22): Deprecation: module
std.c.stdlib is deprecated - Import core.stdc.stdlib or
core.sys.posix.stdlib instead
../sambamba/utils/common/readstorage.d(23): Deprecation: module
std.c.string is deprecated - Import core.stdc.string instead
../sambamba/sort.d(45): Deprecation: module std.c.stdlib is deprecated
- Import core.stdc.stdlib or core.sys.posix.stdlib instead
../sambamba/sort.d(46): Deprecation: module std.c.string is deprecated
- Import core.stdc.string instead
../sambamba/markdup.d(37): Deprecation: module std.c.stdlib is
deprecated - Import core.stdc.stdlib or core.sys.posix.stdlib instead
../sambamba/depth.d(1154): Deprecation: Implicit string concatenation
is deprecated, use "mapping_quality > 0 and " ~ "not duplicate and "
instead
../sambamba/depth.d(1155): Deprecation: Implicit string concatenation
is deprecated, use "not duplicate and " ~ "not failed_quality_control"
instead
[2/74] ldc2  -Isambamba@exe -I. -I.. -I/usr/include/d/
-I/usr/include/htslib -enable-color -O3 -g -release  -of
'sambamba@exe/sambamba_fixbins.d.o' -c ../sambamba/fixbins.d
[3/74] ldc2  -Isambamba@exe -I. -I.. -I/usr/include/d/
-I/usr/include/htslib -enable-color -O3 -g -release  -of
'sambamba@exe/sambamba_depth.d.o' -c ../sambamba/depth.d
FAILED: sambamba@exe/sambamba_depth.d.o
ldc2  -Isambamba@exe -I. -I.. -I/usr/include/d/ -I/usr/include/htslib
-enable-color -O3 -g -release  -of 'sambamba@exe/sambamba_depth.d.o'
-c ../sambamba/depth.d
../sambamba/depth.d(1154): Deprecation: Implicit string concatenation
is deprecated, use "mapping_quality > 0 and " ~ "not duplicate and "
instead
../sambamba/depth.d(1155): Deprecation: Implicit string concatenation
is deprecated, use "not duplicate and " ~ "not failed_quality_control"
instead
0  libLLVM-4.0.so.1 0x7fdf83fb4f45
llvm::sys::PrintStackTrace(llvm::raw_ostream&) + 37
1  libLLVM-4.0.so.1 0x7fdf83fb31a6 llvm::sys::RunSignalHandlers() + 86
2  libLLVM-4.0.so.1 0x7fdf83fb32c3
3  libpthread.so.0  0x7fdf8321b0c0
4  ldc2 0x562179492ee2
5  ldc2 0x562179518017
6  ldc2 0x5621795185dc
7  ldc2 0x5621794dc090
8  ldc2 0x5621794d5be1
9  ldc2 0x5621794e1696
10 ldc2 0x5621794d7041
11 ldc2 0x5621794c4dfd
12 ldc2 0x5621794c3bc4
13 ldc2 0x5621794c1dd4
14 ldc2 0x56217948be81
15 ldc2 0x562179482b00
16 ldc2 0x562179482c9b
17 ldc2 0x562179483564
18 ldc2 0x56217949e915
19 ldc2 0x562179534dc2
20 ldc2 0x56217950ded9
21 ldc2 0x5621793ffa0d
22 ldc2 0x56217951072a
23 ldc2 0x56217955b35f
24 ldc2 0x56217955b324
25 ldc2 0x56217955b250
26 libc.so.60x7fdf825f32e1 __libc_start_main + 241
27 ldc2 0x5621792b57ea
Segmentation fault
[4/74] ldc2  -Isambamba@exe -I. -I.. -I/usr/include/d/
-I/usr/include/htslib -enable-color -O3 -g -release  -of
'sambamba@exe/sambamba_index.d.o' -c ../sambamba/index.d
[5/74] ldc2  -Isambamba@exe -I. -I.. -I/usr/include/d/
-I/usr/include/htslib -enable-color -O3 -g -release  -of
'sambamba@exe/sambamba_flagstat.d.o' -c ../sambamba/flagstat.d
[6/74] ldc2  -Isambamba@exe -I. -I.. -I/usr/include/d/
-I/usr/include/htslib -enable-color -O3 -g -release  -of
'sambamba@exe/sambamba_markdup.d.o' -c ../sambamba/markdup.d
FAILED: sambamba@exe/sambamba_markdup.d.o
ldc2  -Isambamba@exe -I. -I.. -I/usr/include/d/ -I/usr/include/htslib
-enable-color -O3 -g -release  -of 'sambamba@exe/sambamba_markdup.d.o'
-c ../sambamba/markdup.d
../sambamba/markdup.d(37): Deprecation: module std.c.stdlib is
deprecated - Import core.stdc.stdlib or core.sys.posix.stdlib instead
0  libLLVM-4.0.so.1 0x7f56575adf45
llvm::sys::PrintStackTrace(llvm::raw_ostream&) + 37
1  libLLVM-4.0.so.1 0x7f56575ac1a6 llvm::sys::RunSignalHandlers() + 86
2  libLLVM-4.0.so.1 0x7f56575ac2c3
3  libpthread.so.0  0x7f56568140c0
4  ldc2 0x55c9d4f89ee2
5  ldc2 0x55c9d500f017
6  ldc2 0x55c9d500f5dc
7  ldc2 0x55c9d4fd3090
8  ldc2 0x55c9d4fccbe1
9  ldc2 0x55c9d4fd8696
10 ldc2 0x55c9d4fce041
11 ldc2 0x55c9d4fbbdfd
12 ldc2 0x55c9d4fbabc4
13 ldc2 0x55c9d4fb8dd4
14 ldc2 

Processed: tagging 871083

[Debian Bug Tracking System]

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

> tags 871083 + sid
Bug #871083 [src:python-pysam] python-pysam: FTBFS: Test failures
Added tag(s) sid.
> thanks
Stopping processing here.

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

Bug#868955: redmine: buster - broken install, package cannot be removed

[Mark Hedges]

Sorry, I deleted this server and went back to stretch.  I do not have time
to investigate.

Mark

On Sep 11, 2017 11:12 AM, "Marc Dequènes (duck)"  wrote:

> Quack,
>
> Thanks a lot for reporting and taking all this time to investigate.
>
> Antonio is stepping down and we need some time to take over properly.
>
> As for "redmine failed to preconfigure, with exit status 10", I guess this
> is a debconf problem. I'll try to have a look.
>
> As for your second attempt:
>   Bundler will use `/tmp/bundler/home/hedges' as your home directory
> temporarily.
> I wonder how it get that path; are you using sudo without updating the
> HOME environment variable?
> I guess the directory does not exist, which would explain the failure.
> Also it says:
>   `/var/www` is not writable.
> How can this be so if you're root?
>
> It would help if you could answer these questions.
>
> Regards.
> \_o<
>
> --
> Marc Dequènes
>

Bug#784181: [razorqt] Future Qt4 removal from Buster

[Manuel A. Fernandez Montecelo]

2017-09-09 23:09 Lisandro Damián Nicanor Pérez Meyer:


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


This package can be removed when Qt4 is, see:
#784181 -- razorqt: Razor-Qt dead upstream, superseded by LXQt

(copying the bug report, keeping them separate at the moment)

--
Manuel A. Fernandez Montecelo 

Bug#853387: marked as done (elfutils: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Mon, 11 Sep 2017 22:22:51 +
with message-id 
and subject line Bug#853387: fixed in elfutils 0.170-0.1
has caused the Debian Bug report #853387,
regarding elfutils: ftbfs with GCC-7
to be marked as done.

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

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


-- 
853387: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853387
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:elfutils
Version: 0.168-0.2
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

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

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/elfutils_0.168-0.2_unstable_gcc7.log
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

[...]
  CC   asm_getelf.os
  CC   asm_adduint32.os
  CC   asm_scngrp_newsignature.os
  CC   asm_adduint8.os
  CC   asm_adduint64.os
  CC   asm_addint8.os
  CC   disasm_end.os
  CC   asm_addint16.os
  CC   asm_addint64.os
  CC   disasm_begin.os
  CC   asm_newscn.os
  CC   asm_abort.os
  CC   asm_addint32.os
  CC   disasm_str.os
asm_newsym.c: In function 'asm_newsym':
asm_newsym.c:67:41: error: '%07u' directive output may be truncated writing 
between 7 and 10 bytes into a region of size 8 [-Werror=format-truncation=]
   snprintf (tempsym, TEMPSYMLEN, ".L%07u", asmscn->ctx->tempsym_count++);
 ^~~~
asm_newsym.c:67:38: note: using the range [1, 4294967295] for directive argument
   snprintf (tempsym, TEMPSYMLEN, ".L%07u", asmscn->ctx->tempsym_count++);
  ^~~~
In file included from /usr/include/stdio.h:938:0,
 from asm_newsym.c:35:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:64:10: note: format output between 
10 and 13 bytes into a destination of size 10
   return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
  ^~~~
__bos (__s), __fmt, __va_arg_pack ());
~
  CC   asm_adduleb128.os
  CC   asm_addsleb128.os
  CC   asm_newsubscn.os
  CC   asm_newabssym.os
  CC   asm_addstrz.os
  CC   asm_fill.os
  CC   asm_align.os
cc1: all warnings being treated as errors
  CC   asm_newscngrp.os
  CC   asm_newcomsym.os
  CC   disasm_cb.os
Makefile:539: recipe for target 'asm_newsym.o' failed
make[3]: *** [asm_newsym.o] Error 1
make[3]: *** Waiting for unfinished jobs
Makefile:482: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
Makefile:398: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/<>'
debian/rules:51: recipe for target 'build-stamp' failed
make: *** [build-stamp] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
--- End Message ---
--- Begin Message ---
Source: elfutils
Source-Version: 0.170-0.1

We believe that the bug you reported is fixed in the latest version of
elfutils, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 853...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated elfutils package)

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

Bug#848916: marked as done (ocp FTBFS on i386: dwnone_asminc.c:46: Error: junk `(%ebx)' after expression)

[Debian Bug Tracking System]

Your message dated Mon, 11 Sep 2017 21:49:36 +
with message-id 
and subject line Bug#848916: fixed in ocp 1:0.1.21-2
has caused the Debian Bug report #848916,
regarding ocp FTBFS on i386: dwnone_asminc.c:46: Error: junk `(%ebx)' after 
expression
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.)


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

https://buildd.debian.org/status/fetch.php?pkg=ocp=i386=1%3A0.1.21-1.3=1482077784

...
make[2]: Entering directory '/«PKGBUILDDIR»/devw'
i686-linux-gnu-gcc -Wall -g -fPIC -O2 -fPIC -Wall -I.././ -O devwnone.c -o 
devwnone.o -c
dwnone_asminc.c: Assembler messages:
dwnone_asminc.c:46: Error: junk `(%ebx)' after expression
dwnone_asminc.c:47: Error: junk `(%ebx)' after expression
dwnone_asminc.c:48: Error: junk `(%ebx)' after expression
dwnone_asminc.c:55: Error: junk `(%ebx)' after expression
dwnone_asminc.c:57: Error: junk `(%ebx)' after expression
dwnone_asminc.c:59: Error: junk `(%ebx)' after expression
dwnone_asminc.c:63: Error: junk `(%ebx)' after expression
dwnone_asminc.c:66: Error: junk `(%ebx)' after expression
dwnone_asminc.c:68: Error: junk `(%ebx)' after expression
dwnone_asminc.c:70: Error: junk `(%ebx)' after expression
dwnone_asminc.c:71: Error: junk `(%ebx)' after expression
dwnone_asminc.c:90: Error: junk `(%ebx)' after expression
dwnone_asminc.c:94: Error: junk `(%ebx)' after expression
dwnone_asminc.c:97: Error: junk `(%ebx)' after expression
dwnone_asminc.c:98: Error: junk `(%ebx)' after expression
dwnone_asminc.c:99: Error: junk `(%ebx)' after expression
dwnone_asminc.c:102: Error: junk `(%ebx)' after expression
dwnone_asminc.c:104: Error: junk `(%ebx)' after expression
dwnone_asminc.c:106: Error: junk `(%ebx)' after expression
dwnone_asminc.c:108: Error: junk `(%ebx)' after expression
dwnone_asminc.c:111: Error: junk `(%ebx)' after expression
dwnone_asminc.c:112: Error: junk `(%ebx)' after expression
dwnone_asminc.c:115: Error: junk `(%ebx)' after expression
dwnone_asminc.c:116: Error: junk `(%ebx)' after expression
dwnone_asminc.c:119: Error: junk `(%ebx)' after expression
dwnone_asminc.c:121: Error: junk `(%ebx)' after expression
dwnone_asminc.c:123: Error: junk `(%ebx)' after expression
dwnone_asminc.c:126: Error: junk `(%ebx)' after expression
dwnone_asminc.c:127: Error: junk `(%ebx)' after expression
dwnone_asminc.c:130: Error: junk `(%ebx)' after expression
dwnone_asminc.c:131: Error: junk `(%ebx)' after expression
dwnone_asminc.c:133: Error: junk `(%ebx)' after expression
Makefile:55: recipe for target 'devwnone.o' failed
make[2]: *** [devwnone.o] Error 1
--- End Message ---
--- Begin Message ---
Source: ocp
Source-Version: 1:0.1.21-2

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

Debian distribution maintenance software
pp.
Adam Borowski  (supplier of updated ocp package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 11 Sep 2017 23:29:00 +0200
Source: ocp
Binary: opencubicplayer opencubicplayer-doc
Architecture: source
Version: 1:0.1.21-2
Distribution: unstable
Urgency: medium
Maintainer: Gürkan Myczko 
Changed-By: Adam Borowski 
Description:
 opencubicplayer - UNIX port of Open Cubic Player
 opencubicplayer-doc - Documentation for UNIX port of Open Cubic Player
Closes: 744480 848916 853581
Changes:
 ocp (1:0.1.21-2) unstable; urgency=medium
 .
   [ Gürkan Myczko ]
   * Really run dh-autoreconf; thanks Logan Rosen. (Closes: #744480)
   * Fix FTBFS on gcc-7; thanks Steve Langasek. (Closes: #853581)
   * Fix FTBFS on i386; thanks Steve Langasek. (Closes: #848916)
   * Bump debhelper version to 10.
   * Bump standards version to 4.1.0.
   * Update my name.
 .
   [ Adam Borowski ]
   * Remove bogus ancient gcc detection completely, fixes FTBFS on gcc-7.
   * Axe redundant/obsolete {Build-,}Depends (dh-autoreconf, autotools-dev,
  

Bug#853581: marked as done (ocp: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Mon, 11 Sep 2017 21:49:36 +
with message-id 
and subject line Bug#853581: fixed in ocp 1:0.1.21-2
has caused the Debian Bug report #853581,
regarding ocp: ftbfs with GCC-7
to be marked as done.

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

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


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

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

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/ocp_0.1.21-1.3_unstable_gcc7.log
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

[...]
dpkg-source: info: building ocp in ocp_0.1.21-1.3.dsc
 debian/rules build
dh_testdir
AUTOMAKE=true LIBTOOLIZE=true AUTOHEADER=true dh_autoreconf
CFLAGS="-Wall -g -fPIC -O2" CXXFLAGS="-fPIC" ./configure 
--host=x86_64-linux-gnu \
--build=x86_64-linux-gnu \
--prefix=/usr \
--exec-prefix=/usr \
--mandir=\${prefix}/share/man \
--sysconfdir=/etc \
--datadir=\${prefix}/share/ocp \
--libdir=\${prefix}/lib \
--bindir=\${prefix}/bin \
--infodir=\${prefix}/share/info \
--with-x11 --with-dir-suffix= \
--with-freepats=\${prefix}/share/midi/freepats
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking for x86_64-linux-gnu-gcc... x86_64-linux-gnu-gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether x86_64-linux-gnu-gcc accepts -g... yes
checking for x86_64-linux-gnu-gcc option to accept ISO C89... none needed
checking for x86_64-linux-gnu-g++... x86_64-linux-gnu-g++
checking whether we are using the GNU C++ compiler... yes
checking whether x86_64-linux-gnu-g++ accepts -g... yes
checking how to run the C preprocessor... x86_64-linux-gnu-gcc -E
checking how to run the C++ preprocessor... x86_64-linux-gnu-g++ -E
checking whether make sets $(MAKE)... yes
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking whether byte ordering is bigendian... no
checking gcc version... configure: error: 7, bad
debian/rules:15: recipe for target 'configure-stamp' failed
make: *** [configure-stamp] Error 1
dpkg-buildpackage: error: debian/rules build gave error exit status 2
--- End Message ---
--- Begin Message ---
Source: ocp
Source-Version: 1:0.1.21-2

We believe that the bug you reported is fixed in the latest version of
ocp, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 853...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Adam Borowski  (supplier of updated ocp package)

(This message was generated automatically at their 

Bug#872491: marked as done (vdr-plugin-streamdev FTBFS with vdr 2.3.8)

[Debian Bug Tracking System]

Your message dated Mon, 11 Sep 2017 21:17:36 +
with message-id 
and subject line Bug#872491: fixed in vdr-plugin-streamdev 0.6.1+git20170911-1
has caused the Debian Bug report #872491,
regarding vdr-plugin-streamdev FTBFS with vdr 2.3.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.)


-- 
872491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872491
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vdr-plugin-streamdev
Version: 0.6.1+git20150213-3
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/vdr-plugin-streamdev.html

...
g++ -g -O2 -fdebug-prefix-map=/build/vdr-2.3.8=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE 
-c -D_GNU_SOURCE -DPLUGIN_NAME_I18N='"streamdev-client"' -I/include -I.. -o 
filter.o filter.c
filter.c: In member function 'int cStreamdevFilters::OpenFilter(u_short, 
u_char, u_char)':
filter.c:222:2: error: reference to 'Lock' is ambiguous
  Lock();
  ^~~~
In file included from /usr/include/vdr/tools.h:29:0,
 from /usr/include/vdr/i18n.h:14,
 from /usr/include/vdr/config.h:19,
 from ../client/filter.h:8,
 from filter.c:5:
/usr/include/vdr/thread.h:94:8: note: candidates are: void cThread::Lock()
   void Lock(void) { mutex.Lock(); }
^~~~
In file included from /usr/include/vdr/i18n.h:14:0,
 from /usr/include/vdr/config.h:19,
 from ../client/filter.h:8,
 from filter.c:5:
/usr/include/vdr/tools.h:531:8: note: bool 
cListBase::Lock(cStateKey&, bool, int) const
   bool Lock(cStateKey , bool Write = false, int TimeoutMs = 0) const;
^~~~
Makefile:34: recipe for target 'filter.o' failed
make[2]: *** [filter.o] Error 1
--- End Message ---
--- Begin Message ---
Source: vdr-plugin-streamdev
Source-Version: 0.6.1+git20170911-1

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

Debian distribution maintenance software
pp.
Tobias Grimm  (supplier of updated vdr-plugin-streamdev 
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: Mon, 11 Sep 2017 21:56:42 +0200
Source: vdr-plugin-streamdev
Binary: vdr-plugin-streamdev-client vdr-plugin-streamdev-server
Architecture: source amd64
Version: 0.6.1+git20170911-1
Distribution: unstable
Urgency: medium
Maintainer: Debian VDR Team 
Changed-By: Tobias Grimm 
Description:
 vdr-plugin-streamdev-client - VDR Plugin to stream Live-TV to other VDR's - 
client part
 vdr-plugin-streamdev-server - VDR Plugin to stream Live-TV to other VDR's - 
server part
Closes: 872491
Changes:
 vdr-plugin-streamdev (0.6.1+git20170911-1) unstable; urgency=medium
 .
   * New Upstream Snapshot (commit b84b7d8) (Closes: #872491)
   * Added fixes for vdr-2.3.7
   * Standards-Version: 3.9.8
Checksums-Sha1:
 c974bafcc1c477008ecc56af1b84a1bc2b95ef8a 2356 
vdr-plugin-streamdev_0.6.1+git20170911-1.dsc
 8b1c13103526882527766caccd58ad85dc12c197 200511 
vdr-plugin-streamdev_0.6.1+git20170911.orig.tar.gz
 e6a2d5785385f51908833b250dbb0cbfa6ca1159 6488 
vdr-plugin-streamdev_0.6.1+git20170911-1.debian.tar.xz
 2eedf737833daaa44459600095b997050f5db951 171590 
vdr-plugin-streamdev-client-dbgsym_0.6.1+git20170911-1_amd64.deb
 6eb73cf01ca3566646043736492aded04ae08a9d 63066 
vdr-plugin-streamdev-client_0.6.1+git20170911-1_amd64.deb
 2f09531906282228c986c60f6199224f763d0e3e 774860 
vdr-plugin-streamdev-server-dbgsym_0.6.1+git20170911-1_amd64.deb
 3497f7acbfa928f8d45a35ad9bd79e78a12e3bfe 201706 
vdr-plugin-streamdev-server_0.6.1+git20170911-1_amd64.deb
Checksums-Sha256:
 3f868cbf584c897449e766d2387c3d057d5a6dc7d4c3148161189c2ddd642c02 2356 
vdr-plugin-streamdev_0.6.1+git20170911-1.dsc
 64de6eb566fed5871c2ffd54d82425166e8a76babb51fb0ec5765d53dd23d182 

Bug#874220: marked as done (openni2 mustn't build with NEON on armel/armhf)

[Debian Bug Tracking System]

Your message dated Mon, 11 Sep 2017 21:15:15 +
with message-id 
and subject line Bug#874220: fixed in openni2 2.2.0.33+dfsg-10
has caused the Debian Bug report #874220,
regarding openni2 mustn't build with NEON on armel/armhf
to be marked as done.

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

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


-- 
874220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874220
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openni2
Version: 2.2.0.33+dfsg-7
Severity: serious
Tags: patch
Control: affects -1 src:mrpt

NEON is not part of the armel and armhf architecture baselines,
it is therefore not permitted to use NEON unless proper runtime
detection is used.

NEON is also not available on the autobuilders.


openni2 trying to build with NEON on armel causes it to FTBFS:

https://buildd.debian.org/status/logs.php?pkg=openni2=armel

...
In file included from Sensor/XnPacked11DepthProcessor.cpp:27:0:
/usr/lib/gcc/arm-linux-gnueabi/7/include/arm_neon.h:31:2: error: #error "NEON 
intrinsics not available with the soft-float ABI.  Please use -mfloat-abi=softp 
or -mfloat-abi=hard"
 #error "NEON intrinsics not available with the soft-float ABI.  Please use 
-mfloat-abi=softp or -mfloat-abi=hard"
  ^



I also strongly suspect that the FTBFS of mrpt on armhf might be
caused by this bug (test_mrpt_hwdrivers is linked with libOpenNI2):

https://buildd.debian.org/status/fetch.php?pkg=mrpt=armhf=1%3A1.5.3-1=1504457093=0

...
cd /<>/obj-arm-linux-gnueabihf/tests && ./test_mrpt_hwdrivers
Illegal instruction



The "uname -m" usage in ThirdParty/PSCommon/BuildSystem/CommonDefs.mak
is wrong and also results in openni2 being built differently for i386
depending on whether a 32bit or 64bit kernel is used, but here I am
only addressing the ARM issues.

The fix contains of 3 parts:

1. In debian/patches/series, comment out
0006-rpi-Added-Armv6l-as-new-target-platform-and-created-missing-OniPlatformLinux-Arm.h-header.patch

This only made the uname bug above worse.


2. In debian/patches/0012-generic-linux.patch, fix a typo in
ThirdParty/PSCommon/BuildSystem/Platform.generic: FLAGS -> CFLAGS


3. Add the attached 0016-armel-armhf-no-neon.patch
Description: Use the generic platform for armel+armhf
 NEON is not part of the armel and armhf baselines.
Author: Adrian Bunk 

--- openni2-2.2.0.33+dfsg.orig/ThirdParty/PSCommon/BuildSystem/CommonDefs.mak
+++ openni2-2.2.0.33+dfsg/ThirdParty/PSCommon/BuildSystem/CommonDefs.mak
@@ -16,8 +16,6 @@ else ifneq (,$(findstring i686,$(MACHINE
HOST_PLATFORM = x86
 else ifneq (,$(findstring i386,$(MACHINE)))
HOST_PLATFORM = x86
-else ifneq (,$(findstring arm,$(MACHINE)))
-   HOST_PLATFORM = Arm
 else
HOST_PLATFORM = generic
 endif
--- End Message ---
--- Begin Message ---
Source: openni2
Source-Version: 2.2.0.33+dfsg-10

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

Debian distribution maintenance software
pp.
Jochen Sprickerhof  (supplier of updated openni2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 09 Sep 2017 16:17:46 +0200
Source: openni2
Binary: libopenni2-0 openni2-utils libopenni2-dev openni2-doc
Architecture: source
Version: 2.2.0.33+dfsg-10
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Jochen Sprickerhof 
Description:
 libopenni2-0 - framework for sensor-based 'Natural Interaction'
 libopenni2-dev - headers for OpenNI 'Natural Interaction' frameworks
 openni2-doc - developer documentation for OpenNI frameworks
 openni2-utils - debug and test utilities OpenNI2 framework
Closes: 874220
Changes:
 openni2 (2.2.0.33+dfsg-10) unstable; urgency=medium
 .
   * Add patch for arm.
 Thanks to Adrian Bunk (Closes: #874220)
   * Remove flags, not needed anymore
Checksums-Sha1:
 644fe0b44e6ba9da1ce099f1a377cb3160da6e1d 2362 openni2_2.2.0.33+dfsg-10.dsc
 

Bug#826356: marked as done (ktp-accounts-kcm: FTBFS libaccounts update need to fix install files.)

[Debian Bug Tracking System]

Your message dated Mon, 11 Sep 2017 21:11:41 +
with message-id 
and subject line Bug#826356: fixed in ktp-accounts-kcm 17.08.1-1
has caused the Debian Bug report #826356,
regarding ktp-accounts-kcm: FTBFS libaccounts update need to fix install files.
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.)


-- 
826356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826356
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ktp-accounts-kcm
Version: 15.08.3-2
Severity: grave
Tags: patch
Justification: renders package unusable

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
https://tests.reproducible-builds.org/rb-pkg/unstable/i386/ktp-accounts-
kcm.html
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
This has been fixed in experimental, needs applied to unstable and testing.
   * What was the outcome of this action?
NA
   * What outcome did you expect instead?
Successful build
*** End of the template - remove these template lines ***



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

Kernel: Linux 4.5.0-2-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff --git a/debian/kde-config-telepathy-accounts.install b/debian/kde-config-telepathy-accounts.install
index 723949f..b036728 100644
--- a/debian/kde-config-telepathy-accounts.install
+++ b/debian/kde-config-telepathy-accounts.install
@@ -1,8 +1,8 @@
 usr/lib/*/libktpaccountskcminternal.so.*
 usr/lib/*/qt5/plugins/kaccounts/ui/ktpaccountskcm_plugin_kaccounts.so
 usr/lib/*/qt5/plugins/ktpaccountskcm_*.so
-usr/share/accounts/providers/*.provider
-usr/share/accounts/services/*.service
+usr/share/accounts/providers/kde/*.provider
+usr/share/accounts/services/kde/*.service
 usr/share/kservices5/*.desktop
 usr/share/kservicetypes5/*.desktop
 usr/share/telepathy/profiles/*.profile 
--- End Message ---
--- Begin Message ---
Source: ktp-accounts-kcm
Source-Version: 17.08.1-1

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

Debian distribution maintenance software
pp.
Maximiliano Curia  (supplier of updated ktp-accounts-kcm 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 11 Sep 2017 19:59:01 +0200
Source: ktp-accounts-kcm
Binary: kde-config-telepathy-accounts
Architecture: source amd64
Version: 17.08.1-1
Distribution: experimental
Urgency: medium
Maintainer: Debian/Kubuntu Qt/KDE Maintainers 
Changed-By: Maximiliano Curia 
Description:
 kde-config-telepathy-accounts - KDE Control Module for managing Telepathy 
Accounts
Closes: 826356
Changes:
 ktp-accounts-kcm (17.08.1-1) experimental; urgency=medium
 .
   * New upstream release (17.08.1). (Closes: 826356)
   * Add breaks/replaces against the kde-l10n packages
   * Release to experimental
Checksums-Sha1:
 66addc71502eead3079d8196124a450d40d62efc 2775 ktp-accounts-kcm_17.08.1-1.dsc
 1f6dcdf0da9cd53c3b1b391b440ff6437509a2e7 262796 
ktp-accounts-kcm_17.08.1.orig.tar.xz
 3c08ae99c308af52a44706e36d316f0ea91d30cb 5352 
ktp-accounts-kcm_17.08.1-1.debian.tar.xz
 4c5021e7d7513be65c97be8e404d8304a130c6d6 11729270 
kde-config-telepathy-accounts-dbgsym_17.08.1-1_amd64.deb
 4d93245da2085212b1875b4ed74d75da89772422 309656 
kde-config-telepathy-accounts_17.08.1-1_amd64.deb
 d12bdcd59cea90ed810dd2cc0f5d3e274bd8da2d 25881 
ktp-accounts-kcm_17.08.1-1_amd64.buildinfo
Checksums-Sha256:
 c9a2e75d43dff3f92243cd4b12918c3408537640fa0e29bf9236bf00e02f19fc 2775 
ktp-accounts-kcm_17.08.1-1.dsc
 29804708b2b80429df210bbe7c677054596db15b6a52ce346b56723f8cfaf0cd 262796 
ktp-accounts-kcm_17.08.1.orig.tar.xz
 5507d034be6e4d1e05023782a22bd87c42a23804605963c3b3eedbb0d438fe6a 5352 

Bug#830404: marked as done (ktp-accounts-kcm: FTBFS: dh_install: missing files, aborting)

[Debian Bug Tracking System]

Your message dated Mon, 11 Sep 2017 21:11:41 +
with message-id 
and subject line Bug#826356: fixed in ktp-accounts-kcm 17.08.1-1
has caused the Debian Bug report #826356,
regarding ktp-accounts-kcm: FTBFS: dh_install: missing files, aborting
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.)


-- 
826356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826356
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ktp-accounts-kcm
Version: 15.08.3-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160707 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory '/«PKGBUILDDIR»'
> dh_install --fail-missing
> dh_install: Cannot find (any matches for) 
> "usr/share/accounts/providers/*.provider" (tried in "." and "debian/tmp")
> dh_install: kde-config-telepathy-accounts missing files: 
> usr/share/accounts/providers/*.provider
> dh_install: Cannot find (any matches for) 
> "usr/share/accounts/services/*.service" (tried in "." and "debian/tmp")
> dh_install: kde-config-telepathy-accounts missing files: 
> usr/share/accounts/services/*.service
> dh_install: usr/share/accounts/services/kde/ktp-haze-yahoo-im.service exists 
> in debian/tmp but is not installed to anywhere
> dh_install: usr/share/accounts/services/kde/ktp-haze-aim-im.service exists in 
> debian/tmp but is not installed to anywhere
> dh_install: usr/share/accounts/services/kde/ktp-sipe-haze-im.service exists 
> in debian/tmp but is not installed to anywhere
> dh_install: usr/share/accounts/services/kde/ktp-sipe-im.service exists in 
> debian/tmp but is not installed to anywhere
> dh_install: usr/share/accounts/services/kde/ktp-generic-im.service exists in 
> debian/tmp but is not installed to anywhere
> dh_install: usr/share/accounts/services/kde/ktp-haze-gadugadu-im.service 
> exists in debian/tmp but is not installed to anywhere
> dh_install: usr/share/accounts/services/kde/ktp-jabber-im.service exists in 
> debian/tmp but is not installed to anywhere
> dh_install: usr/share/accounts/services/kde/ktp-haze-sametime-im.service 
> exists in debian/tmp but is not installed to anywhere
> dh_install: usr/share/accounts/services/kde/ktp-morse-telegram-im.service 
> exists in debian/tmp but is not installed to anywhere
> dh_install: usr/share/accounts/services/kde/ktp-kde-talk-im.service exists in 
> debian/tmp but is not installed to anywhere
> dh_install: usr/share/accounts/services/kde/google-im.service exists in 
> debian/tmp but is not installed to anywhere
> dh_install: usr/share/accounts/services/kde/ktp-haze-icq-im.service exists in 
> debian/tmp but is not installed to anywhere
> dh_install: usr/share/accounts/providers/kde/ktp-sipe.provider exists in 
> debian/tmp but is not installed to anywhere
> dh_install: usr/share/accounts/providers/kde/ktp-haze-icq.provider exists in 
> debian/tmp but is not installed to anywhere
> dh_install: usr/share/accounts/providers/kde/ktp-haze-sametime.provider 
> exists in debian/tmp but is not installed to anywhere
> dh_install: usr/share/accounts/providers/kde/ktp-haze-aim.provider exists in 
> debian/tmp but is not installed to anywhere
> dh_install: usr/share/accounts/providers/kde/ktp-morse-telegram.provider 
> exists in debian/tmp but is not installed to anywhere
> dh_install: usr/share/accounts/providers/kde/ktp-gadugadu.provider exists in 
> debian/tmp but is not installed to anywhere
> dh_install: usr/share/accounts/providers/kde/ktp-jabber.provider exists in 
> debian/tmp but is not installed to anywhere
> dh_install: usr/share/accounts/providers/kde/ktp-haze-yahoo.provider exists 
> in debian/tmp but is not installed to anywhere
> dh_install: usr/share/accounts/providers/kde/ktp-sipe-haze.provider exists in 
> debian/tmp but is not installed to anywhere
> dh_install: usr/share/accounts/providers/kde/ktp-generic.provider exists in 
> debian/tmp but is not installed to anywhere
> dh_install: usr/share/accounts/providers/kde/ktp-kde-talk.provider exists in 
> debian/tmp but is not installed to anywhere
> dh_install: missing files, aborting
> make[2]: *** [override_dh_install] Error 2

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/07/ktp-accounts-kcm_15.08.3-2_unstable_reb.normal.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 

Bug#875510: nanoc: ruby-compass obsolete and now broken

[Jonas Smedegaard]

Source: nanoc
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

I made a mistake today that cause FTBFS of nanoc, but I would prefer to
fix it in nanoc as that would be needed anyway at a later point:

ruby-compass is obsolete and will likely not be released with Buster.
Its replacement is Sass - as already embraced in nanoc, it seems.

Today I accidentally released to unstable (not experimental as intended)
ruby-sass too new for ruby-compass. I can fix that by re-uploading older
ruby-sass with a fake newer version number, but since only 5 packages
(build-)depend on ruby-compass I would much prefer to instead speedup
the removal of ruby-compass.

Nanoc support for Compass is optional, apparently, so the fix seems to
simply remove build-dependency and (runtime) dependency on ruby-compass.

Please consider doing above fix, and accept my apology for rushing things.
Alternatively I can make an NMU.  Or if neither is acceptable I will do
the more substantial work of postponing this change by reverting
ruby-sass to the older version for now.


 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlm29ywACgkQLHwxRsGg
ASEhUw/+PA2n5oUcPr/Gvja9xIUxxG7znEGv6xY9uMSj+AMicMdzM/q8S6TSXE+i
HbOitombO/i8WZe5dw6yuHDobymSLQ9ykUD5gtlsjfzSSc+SOecex7QuradG6Xnt
jjsmBOG6xUicAJkG05HBVQSNIDzlLPU/Pg9unzZxIBb12KWixEjuyzbC9OdunaHl
e83tSu8+rEBhRo8U8c6Rn7c7OB51UBqxhi9Ju9wF5EnaNfLYqgh8wCUOBjq/E3LU
OsT7PYhwBUO5AWct9we114LjRtsqR/q9oQdwG5LsuYhKT/ehikPa2B48s2RLbcMr
0fe260r8VMTTKS5tac/VDjkeX8rQo4UunRigyE7TUdi/dZXTjLcF1NLqHiCqeyWn
FxgDRhaCFjZ7mTkkyM34c6hUHbvcXCSiRVcmRcOpU/3aAVJcx/iOEjCF2UUAo7cD
JwmkoereCg8aGPPXgU9JHA5yKJTRUT6ZIvfUvP2aL6IWSQzhFrz0/PtgMoyD46pE
ZzbJ1RFvuQmT5BrRl13nK3dRlru0TY8R2oyZyOlBd8Q5c5CmZ0IKHvoryTCYHVz8
RKalpryhzfmWn3dzEpuPnYfQE98TgYf57mgMgVGmzOTKdYJPDiGAhHsWcRmvM3C9
fXa/mRuLOCkxxwtry9fZY94KDQ4LXsWAN+BbJHXDW+1bJIHz4LE=
=0Suc
-END PGP SIGNATURE-

Bug#875381: marked as done (boinc-app-seti-graphics: depends on virtualbox-guest-x11 which is in contrib)

[Debian Bug Tracking System]

Your message dated Mon, 11 Sep 2017 20:41:38 + (UTC)
with message-id <96771182.12463401.1505162498...@mail.yahoo.com>
and subject line Re: Bug#875381: boinc-app-seti-graphics: depends on 
virtualbox-guest-x11 which is in contrib
has caused the Debian Bug report #875381,
regarding boinc-app-seti-graphics: depends on virtualbox-guest-x11 which is in 
contrib
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.)


-- 
875381: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875381
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: boinc-app-seti-graphics
Version: 8.00~svn3643-1~exp3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package is no longer
installable in experimental.

The dependency virtualbox-guest-x11 is only available in contrib,
therefore boinc-app-seti-graphics needs to be moved to contrib as well.


Cheers,

Andreas
--- End Message ---
--- Begin Message ---
Hello,
>Package: boinc-app-seti-graphics
>Version: 8.00~svn3643-1~exp3
>Severity: serious
>User: debian...@lists.debian.org
>Usertags: piuparts


this was probably due to a bad build environment on amd64.
Closing now since I uploaded a new version in experimental and unstable.


G.--- End Message ---

Bug#875453: kopanocore: FTBFS (32-bit): symbols not as expected

[Carsten Schoenert]

Control: tags -1 pending

Hello Aaron,

On Mon, Sep 11, 2017 at 09:58:17AM -0400, Aaron M. Ucko wrote:
> Source: kopanocore
> Version: 8.3.3-1
> Severity: serious
> Justification: fails to build from source
> 
> Builds of kopanocore for 32-bit architectures such as i386 have
> started failing, as detailed below (for i386; I haven't cross-checked
> other architectures).  Could you please account for these differences
> in mangled symbol names?

as you already indicated the build is failing due dpkg-gensymbols fails
on 32-bit architectures. I've worked on the kopano-libs.symbols file to
help dpkg-gensymbols selecting the correct symbols related to the used
platform with 32/64 bitness. I will do some more testing and hopefully
start a new upload soon.

Regards
Carsten

Processed: Re: Bug#875453: kopanocore: FTBFS (32-bit): symbols not as expected

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #875453 [src:kopanocore] kopanocore: FTBFS (32-bit): symbols not as expected
Added tag(s) pending.

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

Bug#875492: [exfalso] Package lacks dependencies

[Moi .]

your bug report falls well.
I was embarrassed, despite the installation of the two dependencies that
you mention, it did not work.
so I added the dependency
python-future
and Exfalso and Quodlibet are now working well.

Architecture: x86_64
Kernel: 4.12.0-1
Desktop: Cinnamon 3.4.6
Distribution: Debian Sid

Bug#875425: Unknown symbol init_mm (err 0)

[Luca Boccassi]

Control: tags -1 pending

On Mon, 2017-09-11 at 18:00 +0800, 積丹尼 Dan Jacobson wrote:
> Package: nvidia-legacy-304xx-driver
> Version: 304.135-4
> Severity: grave
> 
> Please install the changes like
> https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304
> /+bug/1711758
> 
> Else 4.12 kernel is unusable.

Hi,

Thanks for the pointer, I've applied the changes from Fedora in SVN, in
branches/304.

Please note that none of the maintainers have hardware supported by
304xx, so we can only check that the module builds correctly.

Kind regards,
Luca Boccassi

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

Processed: Re: Bug#875425: Unknown symbol init_mm (err 0)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #875425 [nvidia-legacy-304xx-driver] Unknown symbol init_mm (err 0)
Added tag(s) pending.

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

Bug#875317: marked as done (python-astropy is no longer installable in unstable)

[Debian Bug Tracking System]

Your message dated Mon, 11 Sep 2017 19:51:42 +
with message-id 
and subject line Bug#875317: fixed in python-astropy 2.0.2-1
has caused the Debian Bug report #875317,
regarding python-astropy is no longer installable in unstable
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.)


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

Source: python-astropy
Version: 2.0.1-2
Severity: grave

Hi,

With the upload of python2.7 2.7.14~rc1-3, libpython2.7-stdlib introduces a 
breaks against python-astropy, as python-astropy uses symbols related to the 
_PyFPE module which was removed in the latest python2.7 version.


That means that python-astropy is currently uninstallable in unstable, thus 
the severity of this bug. (Also, this makes astrometry.net uninstallable and 
thus it makes kstars FTBFS).


Happy hacking,

-- System Information:
Debian Release: 9.1
 APT prefers stable-updates
 APT policy: (600, 'stable-updates'), (600, 'stable-debug'), (600, 
'proposed-updates'), (600, 'stable'), (60, 'testing-debug'), (60, 'testing'), 
(50, 'unstable-debug'), (50, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

--
"If the code and the comments disagree, then both are probable wrong."
-- Norm Schryer
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: python-astropy
Source-Version: 2.0.2-1

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

Debian distribution maintenance software
pp.
Ole Streicher  (supplier of updated python-astropy 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: Mon, 11 Sep 2017 20:39:28 +0200
Source: python-astropy
Binary: python-astropy python3-astropy python-astropy-doc astropy-utils
Architecture: source
Version: 2.0.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Astronomy Maintainers 

Changed-By: Ole Streicher 
Description:
 astropy-utils - Command line tools from astropy
 python-astropy - Core functionality for performing astrophysics with Python
 python-astropy-doc - Core functionality for performing astrophysics with 
Python (doc)
 python3-astropy - Core functionality for performing astrophysics with Python3
Closes: 875317
Changes:
 python-astropy (2.0.2-1) unstable; urgency=medium
 .
   * New upstream version 2.0.2
   * Rediff patches
   * Push Standards-Version to 4.1.0. No changes needed.
   * Shorten message to compare for recent h5py.
   * Rebuiold against current Python versions. Closes: #875317
Checksums-Sha1:
 caa7feec7b170aac4b8608dd5f0102e5ad8fdae5 3115 python-astropy_2.0.2-1.dsc
 29ce40d65c4d43eab91187f2c5c83c28285d5d1d 8225348 
python-astropy_2.0.2.orig.tar.gz
 9a29a48b6d62710ec0ec6592faeb0714f50f0f93 21080 
python-astropy_2.0.2-1.debian.tar.xz
Checksums-Sha256:
 075d3db154d8a56719e74e69d9fc8de6834d5f58f9b4f4c9e0c3f2a7301ba89b 3115 
python-astropy_2.0.2-1.dsc
 4544a422b1173d79b2d65ba74c627f04a5fd8530d97fb604752d657d754e103d 8225348 
python-astropy_2.0.2.orig.tar.gz
 04484fe03704ad3c1ada1a105faa2ad16a316f8d76f22054dfa9fef67cd92a06 21080 
python-astropy_2.0.2-1.debian.tar.xz
Files:
 28361936fec41aaa6d0375a975cf4f51 3115 python optional 
python-astropy_2.0.2-1.dsc
 1b514f83f8475d4a6e3121de6622cec9 8225348 python optional 
python-astropy_2.0.2.orig.tar.gz
 57c20f21572205cddc6452bac5ff021c 21080 python optional 
python-astropy_2.0.2-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAlm25X4ACgkQcRWv0HcQ
3Pe+mA/9HYP9z2ACBNDIloOgWeaxihQON6wfA4X3M8KOv58W3EDhK0ard3DejqJe

Bug#852592: marked as done (bilibop: Update udevadm path)

[Debian Bug Tracking System]

Your message dated Mon, 11 Sep 2017 19:49:17 +
with message-id 
and subject line Bug#852592: fixed in bilibop 0.5.4
has caused the Debian Bug report #852592,
regarding bilibop: Update udevadm path
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.)


-- 
852592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852592
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bilibop
Version: 0.5.2
Severity: normal
User: pkg-systemd-maintain...@lists.alioth.debian.org
Usertags: udevadm

Hi,

since Jessie, the udevadm binary is available as /bin/udevadm.
To not break existing scripts, which use the old /sbin/udevadm path,
the udev package currently ships a compat symlink which we would like
to drop eventually (in buster or buster+1).

According to codesearch [1] your package bilibop does hard-code the
udevadm path as /sbin/udevadm.

Please change that to /bin/udevadm.

Thanks for considering.

Michael,
on behalf of the pkg-systemd team.

[1] https://codesearch.debian.net/search?q=%2Fsbin%2Fudevadm
--- End Message ---
--- Begin Message ---
Source: bilibop
Source-Version: 0.5.4

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

Debian distribution maintenance software
pp.
Yann Amar  (supplier of updated bilibop package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 09 Sep 2017 08:22:54 +
Source: bilibop
Binary: bilibop bilibop-common bilibop-lockfs bilibop-rules bilibop-udev
Architecture: source amd64
Version: 0.5.4
Distribution: unstable
Urgency: high
Maintainer: Yann Amar 
Changed-By: Yann Amar 
Description:
 bilibop- run Debian GNU/Linux from external media - metapackage
 bilibop-common - shell functions for bilibop scripts
 bilibop-lockfs - lock filesystems and write changes into RAM
 bilibop-rules - device management rules for OS running from external media
 bilibop-udev - minimal udev rule for Debian GNU/Linux running from external 
medi
Closes: 852592
Changes:
 bilibop (0.5.4) unstable; urgency=high
 .
   * bilibop-common: remove "udev compatibility stuff" (no more needed).
 Closes: #852592.
   * debian/control:
 - bump Standards-Version to 4.1.0, and modify Format: field in
   debian/copyright accordingly (use https:// URL); also remove
   extra priority (deprecated)
 - add aufs-dkms in the list of packages suggested by bilibop-lockfs
   * debian/*.triggers: replace 'activate' by more explicit 'activate-await'
 variant (caught by lintian).
   * Update copyright dates
Checksums-Sha1:
 a9d1865e720358c061bd67dc8fac863b782ad23e 1789 bilibop_0.5.4.dsc
 a4cffb58f34eb4a4d1520c82c71300f4fa5f5ac6 136744 bilibop_0.5.4.tar.xz
 96a267b6b8f174ceeab2be1e46f7107f8748a680 73412 bilibop-common_0.5.4_amd64.deb
 a0f741bff4c2b503149f46874706e873555fb4c0 49360 bilibop-lockfs_0.5.4_amd64.deb
 2960c2f097f76bd317a4a404c22809ec4e3bad6a 80318 bilibop-rules_0.5.4_amd64.deb
 49116855ba9c6aa8a37cb9b4a12a06be0c8841d5 18326 bilibop-udev_0.5.4_amd64.deb
 7e73230885011a901187ac3c2a2a38fa92067442 6545 bilibop_0.5.4_amd64.buildinfo
 ce0c3e2583e1d8978345399c80df663b4ac4c131 16154 bilibop_0.5.4_amd64.deb
Checksums-Sha256:
 c0ba46cb1ef5a848ee6c7c15f21ad5b9f32bc696bba9d4e3343e161e33018540 1789 
bilibop_0.5.4.dsc
 2af231d15f81a212dfe9d920892844825a6b7e0aaf32c8c5314326e86e0ba811 136744 
bilibop_0.5.4.tar.xz
 af6be7c709e6ef459a66421d16f6ff003dafe4af809473b368f6950107d90d23 73412 
bilibop-common_0.5.4_amd64.deb
 26d61be33e88daa64ee617d4d4f02ea97039a415dd5d44ed88c9ebcfbbc486bc 49360 
bilibop-lockfs_0.5.4_amd64.deb
 534ea65ef4f5fd7602064bb0ca7ebfc53ff43d117b3d2d2459d3f13cc6505c06 80318 
bilibop-rules_0.5.4_amd64.deb
 c51c9eb605867af734f54f7f6519f8421bf033cb6fe07375bf2fdac7980f5ca6 18326 
bilibop-udev_0.5.4_amd64.deb
 aeeea27440477728ccb40d22b2731dca3ff0cd02840d3ec53ec160acb8aac621 6545 
bilibop_0.5.4_amd64.buildinfo
 254dbfaa88d02095d3a6916e8796724fd9edf858ff34eaa44f0a90dd729a5cbb 16154 
bilibop_0.5.4_amd64.deb
Files:
 

Bug#875492: [exfalso] Package lacks dependencies

[Bruno Kleinert]

Package: exfalso
Version: 3.9.1-1
Severity: grave

--- Please enter the report below this line. ---
Hi,

since the upgrade to version 3.9.1-1, exfalso does not start anymore on
my machine. I get the following error:

(0)fuddl@flutschi:~$ exfalso 
Traceback (most recent call last):
  File "/usr/bin/exfalso", line 15, in 
sys.exit(main())
  File "/usr/lib/python2.7/dist-packages/quodlibet/exfalso.py", line
27, in main
quodlibet.init(config_file=config_file)
  File "/usr/lib/python2.7/dist-packages/quodlibet/_init.py", line 56,
in init
_init_gtk()
  File "/usr/lib/python2.7/dist-packages/quodlibet/_init.py", line 274,
in _init_gtk
from quodlibet.qltk import ThemeOverrider, gtk_version
  File "/usr/lib/python2.7/dist-packages/quodlibet/qltk/__init__.py",
line 540, in 
from .msg import Message, ErrorMessage, WarningMessage
  File "/usr/lib/python2.7/dist-packages/quodlibet/qltk/msg.py", line
15, in 
from quodlibet.qltk.window import Dialog
  File "/usr/lib/python2.7/dist-packages/quodlibet/qltk/window.py",
line 16, in 
from quodlibet.qltk.x import Button
  File "/usr/lib/python2.7/dist-packages/quodlibet/qltk/x.py", line 20,
in 
from quodlibet.util.thread import call_async, Cancellable
  File "/usr/lib/python2.7/dist-packages/quodlibet/util/thread.py",
line 14, in 
raise ImportError("python-futures is missing: %r" % e)
ImportError: python-futures is missing: ImportError('No module named
concurrent.futures',)

So I apt install python-concurrent.futures. After that, I see the
following error:

(0)fuddl@flutschi:~$ exfalso 
E: 0.176: errorreport.main.errorhook: update.py:20::
ImportError: No module named feedparser

So I apt install python-feedparser and it runs fine. Please fix the
missing dependencies.

Cheers - Fuddl

--- System information. ---
Architecture: 
Kernel:   Linux 4.12.0-1-amd64

Debian Release: buster/sid
  500 unstableftp.uni-erlangen.de 
1 experimentalftp.uni-erlangen.de 

--- Package information. ---
Depends   (Version) | Installed
===-+-
gir1.2-gtk-3.0  | 3.22.20-1
gir1.2-soup-2.4   (>= 2.44) | 2.59.90.1-1
python  (>= 2.7.3-4+deb7u1) | 2.7.13-2
python-faulthandler | 2.4-1
python-gi   | 3.24.1-3
python-gi-cairo | 3.24.1-3
python-mutagen(>= 1.32) | 1.38-1
python:any (<< 2.8) | 
python:any(>= 2.7.5-5~) | 
libjs-sphinxdoc(>= 1.0) | 1.5.6-2
sphinx-rtd-theme-common | 0.2.4-1


Recommends (Version) | Installed
-+-===
python-musicbrainzngs   (>= 0.5) | 0.6-2


Suggests  (Version) | Installed
===-+-===
brasero | 3.12.2-1
 OR k3b | 
 OR xfburn  | 
gir1.2-gstreamer-1.0| 1.12.2-1
libmodplug1 | 1:0.8.9.0-1






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

Bug#874220: openni2 mustn't build with NEON on armel/armhf

[Adrian Bunk]

On Fri, Sep 08, 2017 at 07:17:59PM +0200, JOSE LUIS BLANCO CLARACO wrote:
> Hi Adrian,
> 
> Thanks for tagging "mrpt" here!
> Is there any expected action on our side? Should we disable linking
> against openni2 in armhf in the meanwhile... or it's better to wait
> for this bug to be solved? It actually blocks mrpt to get into
> testing...

It's best for you to just wait for this bug to get resolved.

> Cheers,

cu
Adrian

-- 

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

Bug#868955: redmine: buster - broken install, package cannot be removed

[duck]

Quack,

Thanks a lot for reporting and taking all this time to investigate.

Antonio is stepping down and we need some time to take over properly.

As for "redmine failed to preconfigure, with exit status 10", I guess 
this is a debconf problem. I'll try to have a look.


As for your second attempt:
  Bundler will use `/tmp/bundler/home/hedges' as your home directory 
temporarily.
I wonder how it get that path; are you using sudo without updating the 
HOME environment variable?

I guess the directory does not exist, which would explain the failure.
Also it says:
  `/var/www` is not writable.
How can this be so if you're root?

It would help if you could answer these questions.

Regards.
\_o<

--
Marc Dequènes

Bug#875465: sagemath: FTBFS on arm64: partitions doctests fail

[Ximin Luo]

Control: severity -1 important

The previous build success was an accident, I raised the ignore-test-failures 
threshold too high. These combinat tests that you mention, also failed in the 
"successful build". Further, that build did not get a chance to migrate to 
Debian testing, so it can effectively be disregarded for Debian release 
purposes.

Upstream are spending a minor amount of effort on fixing these issues but until 
this is complete, I think it's best to avoid shipping arm64 sagemath on Debian. 
Downgrading the severity for now.

(FWIW ppc64el seems to be fine and has the same number of test failures as 
amd64.)

X

On Mon, 11 Sep 2017 11:08:41 -0400 "Aaron M. Ucko"  wrote:
> Source: sagemath
> Version: 8.0-7
> Severity: serious
> Tags: upstream
> Justification: fails to build from source (but built successfully in the past)
> 
> The latest arm64 build of sagemath encountered errors in two
> sage.combinat.partitions.* doctests, as detailed at
> https://buildd.debian.org/status/fetch.php?pkg=sagemath=arm64=8.0-7=1505101830=0
> 
>   2 items had failures:
> 10 of  26 in sage.combinat.partitions.number_of_partitions
>  1 of   3 in sage.combinat.partitions.run_tests
>   [35 tests, 11 failures, 8.05 s]
> 
> Could you please take a look?
> 
> Thanks!
> 
> -- 
> Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
> http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
> 
> 

-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git

Processed: Re: sagemath: FTBFS on arm64: partitions doctests fail

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #875465 [src:sagemath] sagemath: FTBFS on arm64: partitions doctests fail
Severity set to 'important' from 'serious'

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

Bug#875478: cjk does not trap command errors in Makefile

[韓達耐]

Thanks Helmut!
I'll update the SVN shortly.

Regards

Danai

On 12 Sep 2017 01:44, "Helmut Grohne"  wrote:

> Source: cjk
> Version: 4.8.4+git20150701-2
> Severity: serious
> Justification: policy 4.6
>
> The toplevel cjk Makefile runs configure and make chained with ";". In
> the presence of errors from configure, it still attempts to run make.
> This behaviour can result in errors going undetected and thus violates
> Debian policy section 4.6. It's not an upstream bug, because the
> offending code was introduced in a Debian-specific patch.
>
> Helmut
>
>

Bug#875478: cjk does not trap command errors in Makefile

[Helmut Grohne]

Source: cjk
Version: 4.8.4+git20150701-2
Severity: serious
Justification: policy 4.6

The toplevel cjk Makefile runs configure and make chained with ";". In
the presence of errors from configure, it still attempts to run make.
This behaviour can result in errors going undetected and thus violates
Debian policy section 4.6. It's not an upstream bug, because the
offending code was introduced in a Debian-specific patch.

Helmut

Processed: [bts-link] source package src:openjpeg2

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:openjpeg2
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #874430 (http://bugs.debian.org/874430)
> # Bug title: openjpeg2: CVE-2017-14151: heap-based buffer overflow in 
> opj_mqc_flush
> #  * https://github.com/uclouvain/openjpeg/issues/982
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 874430 + fixed-upstream
Bug #874430 [src:openjpeg2] openjpeg2: CVE-2017-14151: heap-based buffer 
overflow in opj_mqc_flush
Added tag(s) fixed-upstream.
> usertags 874430 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> # remote status report for #874431 (http://bugs.debian.org/874431)
> # Bug title: openjpeg2: CVE-2017-14152: heap-based buffer overflow in 
> opj_write_bytes_LE
> #  * https://github.com/uclouvain/openjpeg/issues/985
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 874431 + fixed-upstream
Bug #874431 [src:openjpeg2] openjpeg2: CVE-2017-14152: heap-based buffer 
overflow in opj_write_bytes_LE
Added tag(s) fixed-upstream.
> usertags 874431 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:gdk-pixbuf

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:gdk-pixbuf
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #874552 (http://bugs.debian.org/874552)
> # Bug title: gdk-pixbuf: CVE-2017-2862: JPEG 
> gdk_pixbuf__jpeg_image_load_increment Code Execution Vulnerability
> #  * http://bugzilla.gnome.org/show_bug.cgi?id=784866
> #  * remote status changed: (?) -> RESOLVED
> #  * remote resolution changed: (?) -> FIXED
> #  * closed upstream
> tags 874552 + fixed-upstream
Bug #874552 [src:gdk-pixbuf] gdk-pixbuf: CVE-2017-2862: JPEG 
gdk_pixbuf__jpeg_image_load_increment Code Execution Vulnerability
Added tag(s) fixed-upstream.
> usertags 874552 + status-RESOLVED resolution-FIXED
There were no usertags set.
Usertags are now: resolution-FIXED status-RESOLVED.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:haskell-test-framework-th-prime

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package 
> src:haskell-test-framework-th-prime
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #867475 (http://bugs.debian.org/867475)
> # Bug title: haskell-test-framework-th-prime FTBFS: Expecting one more 
> argument to `Module'
> #  * https://github.com/kazu-yamamoto/test-framework-th-prime/issues/7
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 867475 + fixed-upstream
Bug #867475 [src:haskell-test-framework-th-prime] 
haskell-test-framework-th-prime FTBFS: Expecting one more argument to `Module'
Added tag(s) fixed-upstream.
> usertags 867475 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 867475 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#790207: Upstream luakit based on webkit2gtk

[Grégory DAVID]

I confirm that, as the new maintainer, the last tag in luakit Git repo in 
Alioth is based on Webkit2gtk.


The correct commit to use is the one tagged with "debian/2017.08.10-2": 
8ddd96fadd6bfc41291a487235c388ebbc92d03b


Unfortunatly, I'm not sure that everything was done correctly to let the 
luakit package become available inside the Debian archive.


Someone can verify that, just to assure that I'm in the right way.

Thanks.

--
DAVID Grégory
Libre Software Developer
d...@groolot.net

https://framagit.org/groolot
https://github.com/groolot

smime.p7s
Description: S/MIME Cryptographic Signature

Processed: Re: Bug#875387: efl: FTBFS in experimental: lib/elua/elua.c:358:7: error: unknown type name 'luaL_reg'

[Debian Bug Tracking System]

Processing control commands:

> tags -1 fixed-upstream
Bug #875387 [src:efl] efl: FTBFS in experimental: lib/elua/elua.c:358:7: error: 
unknown type name 'luaL_reg'
Added tag(s) fixed-upstream.

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

Bug#875387: efl: FTBFS in experimental: lib/elua/elua.c:358:7: error: unknown type name 'luaL_reg'

[Andreas Metzler]

Control: tags -1 fixed-upstream

On 2017-09-11 Andreas Beckmann  wrote:
> Source: efl
> Version: 1.18.4-1
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
> User: debian...@lists.debian.org
> Usertags: piuparts
> Control: affects -1 + libevas-loaders

> Hi,

> efl FTBFS in experimental:

> lib/elua/elua.c:358:7: error: unknown type name 'luaL_reg'
>  const luaL_reg gettextlib[] =
[...]

Ross is already in the process of upgrading to efl 1.20.3, which builds
successfully.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#875471: fitspng segfaults with glibc-2.26, undefined strtok behaviour

[Matthias Klose]

Package: src:fitspng
Version: 0.3.5-1
Severity: serious
Tags: sid buster

the autopkg test segfaults when run with glibc-2.26, in fitspng.c line 683

  fw = strtok(fval[3])

exposed by
https://sourceware.org/bugzilla/show_bug.cgi?id=16640

the first call to strtok with a NULL pointer is undefined.

Bug#873374: libtsk13 4.4.2-1 crash in the dfvfs test suite

[Eriberto Mota]

2017-08-27 4:08 GMT-03:00 Adrian Bunk :
> Package: libtsk13
> Version: 4.4.2-1
> Severity: serious
> Control: affects -1 src:dfvfs python-tsk
>
> https://tests.reproducible-builds.org/debian/history/dfvfs.html
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/dfvfs.html
>
> ...
>debian/rules override_dh_auto_test
> make[1]: Entering directory '/build/1st/dfvfs-20170723'
> python run_tests.py
> testIterateVolumes (volume.vshadow_volume_system.VShadowVolumeSystemTest)
> Test the iterate volumes functionality. ... ok
> testIterateVolumes (volume.tsk_volume_system.TSKVolumeSystemTest)
> Test the iterate volumes functionality. ... debian/rules:23: recipe for 
> target 'override_dh_auto_test' failed
> make[1]: *** [override_dh_auto_test] Floating point exception
>
>
> Program terminated with signal SIGFPE, Arithmetic exception.
> #0  0x7fa2ac0f606a in dos_load_prim_table (test=1 '\001',
> vs=0x55c56dcae270) at dos.c:821
> 821 dos.c: No such file or directory.
> (gdb) bt
> #0  0x7fa2ac0f606a in dos_load_prim_table (test=1 '\001',
> vs=0x55c56dcae270) at dos.c:821
> #1  tsk_vs_dos_open (img_info=0x7fa2a322c070, offset=0,
> test=test@entry=1 '\001') at dos.c:1064
> #2  0x7fa2ac0f3161 in tsk_vs_open (img_info=0x7fa2a322c070, offset=0,
> type=) at mm_open.c:56
> #3  0x7fa2ac3bf41e in Volume_Info_Con (self=0x55c56dcbe2f0,
> img=, type=, offset=)
> at tsk3.c:659
> #4  0x7fa2ac3b3ade in pyVolume_Info_init (self=self@entry=0x7fa2a31b4c70,
> args=args@entry=( _is_cached=True, 
> _resolver_context=  _values={u'type: OS, location: 
> /tmp/dfvfs-20170723/test_data/vsstest.qcow2\n': 
>  _is_cached=True, _resolver_context=<...>, _is_open=True, _file_object= at remote 0x7fa2a3174d20>) at remote 0x7fa2a31b4550>) at remote 
> 0x7fa2a31b4590>, u'type: OS, location: 
> /tmp/dfvfs-20170723/test_data/bdetogo.raw\n': 
> ) at remote 
> 0x7fa2a31b4bd0>}) at remote 0x7fa2a3fbad90>, 
> _file_system_cache= _values={}) at remote 0x7fa2a3fbad50>) at remote 0x7fa2a3fba390>, 
> _is_open=True, _file_object=) at remote 
> 0x7fa2a31b4890>) at remote 0x7fa2a31994b0>,), kwds=kwds@entry=0x0)
> at pytsk3.c:20444
> #5  0x55c56b688bf4 in type_call.lto_priv () at ../Objects/typeobject.c:765
> #6  0x55c56b683163 in PyObject_Call () at ../Objects/abstract.c:2547
> ...
>
> Works after downgrading libtsk13 to 4.4.0-5



Hi Adrian and all,

I think that it is an upstream problem and I will report it soon (today).

There is any workaround to mitigate this issue for now?

Regards,

Eriberto

Bug#875465: sagemath: FTBFS on arm64: partitions doctests fail

[Aaron M. Ucko]

Source: sagemath
Version: 8.0-7
Severity: serious
Tags: upstream
Justification: fails to build from source (but built successfully in the past)

The latest arm64 build of sagemath encountered errors in two
sage.combinat.partitions.* doctests, as detailed at
https://buildd.debian.org/status/fetch.php?pkg=sagemath=arm64=8.0-7=1505101830=0

  2 items had failures:
10 of  26 in sage.combinat.partitions.number_of_partitions
 1 of   3 in sage.combinat.partitions.run_tests
  [35 tests, 11 failures, 8.05 s]

Could you please take a look?

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#868280: even after purging and installing fresh torbrowser-launcher doesn't work.

[Roger Shimizu]

latest version 0.2.8 is already available in jessie-backports-sloppy,
stretch-backports, buster and sid.
So please kindly help to confirm your problem is solved.

Thank you!

-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1

Bug#853672: marked as done (svxlink: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Mon, 11 Sep 2017 15:18:36 +
with message-id 
and subject line Bug#853672: fixed in svxlink 15.11-2.1
has caused the Debian Bug report #853672,
regarding svxlink: ftbfs with GCC-7
to be marked as done.

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

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


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

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

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/svxlink_15.11-2_unstable_gcc7.log
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

[...]
[ 62%] Built target asynccpp_static
cd /<>/build/async/cpp && /usr/bin/cmake -E cmake_symlink_library 
../../lib/libasynccpp.so.1.4.0 ../../lib/libasynccpp.so.1.4 
../../lib/libasynccpp.so
make[4]: Leaving directory '/<>/build'
[ 62%] Built target asynccpp
[ 62%] Linking CXX shared library ../../lib/libasyncqt.so
cd /<>/build/async/qt && /usr/bin/cmake -E cmake_link_script 
CMakeFiles/asyncqt.dir/link.txt --verbose=1
/usr/bin/c++  -fPIC -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 --std=c++11 -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -shared 
-Wl,-soname,libasyncqt.so.1.4 -o ../../lib/libasyncqt.so.1.4.0 
CMakeFiles/asyncqt.dir/AsyncQtApplication.cpp.o 
CMakeFiles/asyncqt.dir/AsyncQtDnsLookupWorker.cpp.o 
CMakeFiles/asyncqt.dir/moc_AsyncQtApplication.cpp.o 
CMakeFiles/asyncqt.dir/moc_AsyncQtTimer.cpp.o 
CMakeFiles/asyncqt.dir/moc_AsyncQtDnsLookupWorker.cpp.o 
-Wl,-rpath,/<>/build/lib: -lsigc-2.0 
../../lib/libasynccore.so.1.4.0 
/usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.7.1 
/usr/lib/x86_64-linux-gnu/libQt5Network.so.5.7.1 -lsigc-2.0 -lpthread 
/usr/lib/x86_64-linux-gnu/libQt5Gui.so.5.7.1 
/usr/lib/x86_64-linux-gnu/libQt5Core.so.5.7.1 
make[4]: Leaving directory '/<>/build'
CMakeFiles/Makefile2:308: recipe for target 
'async/audio/CMakeFiles/asyncaudio.dir/all' failed
make[3]: *** [async/audio/CMakeFiles/asyncaudio.dir/all] Error 2
[ 62%] Linking CXX static library libasyncqt.a
cd /<>/build/async/qt && /usr/bin/cmake -P 
CMakeFiles/asyncqt_static.dir/cmake_clean_target.cmake
cd /<>/build/async/qt && /usr/bin/cmake -E cmake_link_script 
CMakeFiles/asyncqt_static.dir/link.txt --verbose=1
/usr/bin/ar qc libasyncqt.a  
CMakeFiles/asyncqt_static.dir/AsyncQtApplication.cpp.o 
CMakeFiles/asyncqt_static.dir/AsyncQtDnsLookupWorker.cpp.o
/usr/bin/ranlib libasyncqt.a
make[4]: Leaving directory '/<>/build'
[ 62%] Built target asyncqt_static
cd /<>/build/async/qt && /usr/bin/cmake -E cmake_symlink_library 
../../lib/libasyncqt.so.1.4.0 ../../lib/libasyncqt.so.1.4 
../../lib/libasyncqt.so
make[4]: Leaving directory '/<>/build'
[ 62%] Built target asyncqt
[ 63%] Linking CXX static library liblocationinfo.a
cd /<>/build/locationinfo && /usr/bin/cmake -P 
CMakeFiles/locationinfo.dir/cmake_clean_target.cmake
cd /<>/build/locationinfo && /usr/bin/cmake -E cmake_link_script 
CMakeFiles/locationinfo.dir/link.txt --verbose=1
/usr/bin/ar qc liblocationinfo.a  
CMakeFiles/locationinfo.dir/LocationInfo.cpp.o 
CMakeFiles/locationinfo.dir/AprsTcpClient.cpp.o 
CMakeFiles/locationinfo.dir/AprsUdpClient.cpp.o
/usr/bin/ranlib liblocationinfo.a
[ 64%] Linking CXX shared module ../../../lib/ModuleMetarInfo.so
cd /<>/build/svxlink/modules/metarinfo && /usr/bin/cmake -E 
cmake_link_script CMakeFiles/ModuleMetarInfo.dir/link.txt --verbose=1
/usr/bin/c++  -fPIC -g -O2 

Bug#853368: marked as done (dbf2mysql: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Mon, 11 Sep 2017 15:06:48 +
with message-id 
and subject line Bug#853368: fixed in dbf2mysql 1.14a-5.1
has caused the Debian Bug report #853368,
regarding dbf2mysql: ftbfs with GCC-7
to be marked as done.

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

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


-- 
853368: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853368
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:dbf2mysql
Version: 1.14a-5
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

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

The package fails to build in a test rebuild on at least amd64 with
gcc-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/dbf2mysql_1.14a-5_unstable_gcc7.log
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

[...]
dbf.c:666:37: warning: pointer targets in passing argument 2 of 
'__builtin_strncpy' differ in signedness [-Wpointer-sign]
  strncpy(fields[t].db_contents, end, i);
 ^
dbf.c:666:37: note: expected 'const char *' but argument is of type 'u_char * 
{aka unsigned char *}'
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -O2 -Wall -c -o endian.o endian.c
ar rcs libdbf.a dbf.o endian.o
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -O2 -Wall  -L.  -o dbf2mysql dbf2mysql.o -ldbf 
\
-lmysqlclient -lm -Wl,-z,relro
dbf2mysql.o: In function `do_inserts':
./dbf2mysql.c:403: warning: the use of `tempnam' is dangerous, better use 
`mkstemp'
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -O2 -Wall -DVERSION=\"1.14\" 
-I/usr/include/mysql -c -o mysql2dbf.o mysql2dbf.c
mysql2dbf.c: In function 'main':
mysql2dbf.c:211:45: warning: format '%d' expects argument of type 'int', but 
argument 3 has type 'long unsigned int' [-Wformat=]
printf("Adding field: %s, INT_TYPE, %d\n", qfield->name,
~^
%ld
qfield->length);
~~
mysql2dbf.c:223:45: warning: format '%d' expects argument of type 'int', but 
argument 3 has type 'long unsigned int' [-Wformat=]
printf("Adding field: %s, INT_REAL, %d\n", qfield->name,
~^
%ld
qfield->length);
~~
mysql2dbf.c:235:45: warning: format '%d' expects argument of type 'int', but 
argument 3 has type 'long unsigned int' [-Wformat=]
printf("Adding field: %s, INT_CHAR, %d\n", qfield->name,
~^
%ld
qfield->length);
~~
mysql2dbf.c:243:55: warning: format '%d' expects argument of type 'int', but 
argument 3 has type 'long unsigned int' [-Wformat=]
   printf("Adding field: %s, FIELD_TYPE_DATETIME, %d\n", qfield->name,
  ~^
  %ld
  qfield->length);
  ~~
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -O2 -Wall  -L.  -o mysql2dbf mysql2dbf.o -ldbf 
\
-lmysqlclient -lm -Wl,-z,relro
mysql2dbf.o: In function `main':
./mysql2dbf.c:202: undefined reference to `strtoupper'
./mysql2dbf.c:286: undefined reference to `strtoupper'
./mysql2dbf.c:289: undefined reference to `strtolower'
collect2: error: 

Bug#858905: marked as done (kde-telepathy-text-ui: Fails to show text entry widget)

[Debian Bug Tracking System]

Your message dated Mon, 11 Sep 2017 16:58:13 +0200
with message-id <1505141754-1843-bts-m...@debian.org>
and subject line Issue fixed upstream 858905
has caused the Debian Bug report #858905,
regarding kde-telepathy-text-ui: Fails to show text entry widget
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.)


-- 
858905: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858905
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kde-telepathy-text-ui
Version: 15.08.3-1+b2
Severity: serious
Justification: breaks entire package

Dear Maintainer,

The text-ui package is supposed to present a textbox in which the user can
type to be able to chat on IM. At present, the text box is not displayed
(instead and empty window with nothing below the toolbar is shown). Any
attempt to use functions within that window results in either nothing
happening or the application crashing.

This looks rather similar to

  https://bugs.kde.org/show_bug.cgi?id=361459

cheers
Stuart


-- System Information:
Debian Release: 9.0
  APT prefers testing-proposed-updates
  APT policy: (550, 'testing-proposed-updates'), (500, 'testing-debug'), (500, 
'testing'), (60, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages kde-telepathy-text-ui depends on:
ii  kde-telepathy-data  15.08.3-1
ii  kio 5.28.0-1
ii  libc6   2.24-9
ii  libgcc1 1:6.3.0-10
ii  libjs-jquery3.1.1-2
ii  libkf5archive5  5.28.0-1+b2
ii  libkf5configcore5   5.28.0-1+b2
ii  libkf5configgui55.28.0-1+b2
ii  libkf5configwidgets55.28.0-1
ii  libkf5coreaddons5   5.28.0-1+b2
ii  libkf5dbusaddons5   5.28.0-1
ii  libkf5emoticons-bin 5.28.0-1
ii  libkf5emoticons55.28.0-1
ii  libkf5i18n5 5.28.0-1+b2
ii  libkf5iconthemes5   5.28.0-1
ii  libkf5itemviews55.28.0-1
ii  libkf5kcmutils5 5.28.0-1
ii  libkf5kiocore5  5.28.0-1
ii  libkf5kiowidgets5   5.28.0-1
ii  libkf5notifications55.28.0-1
ii  libkf5notifyconfig5 5.28.0-1
ii  libkf5people5   5.28.0-1
ii  libkf5peoplewidgets55.28.0-1
ii  libkf5service-bin   5.28.0-1
ii  libkf5service5  5.28.0-1
ii  libkf5sonnetcore5   5.28.0-1
ii  libkf5sonnetui5 5.28.0-1
ii  libkf5textwidgets5  5.28.0-1
ii  libkf5webkit5   5.28.0-1
ii  libkf5widgetsaddons55.28.0-1
ii  libkf5windowsystem5 5.28.0-1
ii  libkf5xmlgui5   5.28.0-1
ii  libktpcommoninternals9  15.08.3-1+b4
ii  libktplogger9   15.08.3-1+b4
ii  libktpmodels9   15.08.3-1+b4
ii  libktpotr9  15.08.3-1+b4
ii  libktpwidgets9  15.08.3-1+b4
ii  libqt5core5a5.7.1+dfsg-3+b1
ii  libqt5dbus5 5.7.1+dfsg-3+b1
ii  libqt5gui5  5.7.1+dfsg-3+b1
ii  libqt5webkit5   5.7.1+dfsg-1
ii  libqt5widgets5  5.7.1+dfsg-3+b1
ii  libqt5xml5  5.7.1+dfsg-3+b1
ii  libstdc++6  6.3.0-10
ii  libtelepathy-qt5-0  0.9.6.1-6.1~themill9+1

Versions of packages kde-telepathy-text-ui recommends:
ii  kde-telepathy  15.08.3

kde-telepathy-text-ui suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---

Version: 16.04.1-1

Hi,

Upstream fixed this issue in 16.03.90, I' tagging the issue as fixed in the 
next Debian upload.


Happy hacking,
--
"There are two major products that come out of Berkeley: LSD and BSD.
We don't believe this to be a coincidence."
-- Jeremy S. Anderson
Saludos /\/\ /\ >< `/


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

Bug#875423: openssl: Please re-enable TLS 1.0 and TLS 1.1 (at least in testing)

[Philip Hands]

Raphaël Hertzog  writes:

...
> Or at least I would like a system-wide flag (in a configuration file?) to
> let me re-enable old protocols easily.

Just because I haven't seen anyone else suggest it:

Would it be practical to have the normal packages drop TLS 1.0/1.1
support as currently planned, but have an alternative set of packages
(called openssl-obsolescent, or openssl-tls-flawed, or whatever) with
the TLS 1.0/1.1 support re-enabled, so that one could do the migration
away from TLS 1.0/1.1, but still allow people who notice problems to
deal with them by choosing to install this other set of packages?

Cheers, Phil.
-- 
|)|  Philip Hands  [+44 (0)20 8530 9560]  HANDS.COM Ltd.
|-|  http://www.hands.com/http://ftp.uk.debian.org/
|(|  Hugo-Klemm-Strasse 34,   21075 Hamburg,GERMANY


signature.asc
Description: PGP signature

Bug#875453: kopanocore: FTBFS (32-bit): symbols not as expected

[Aaron M. Ucko]

Source: kopanocore
Version: 8.3.3-1
Severity: serious
Justification: fails to build from source

Builds of kopanocore for 32-bit architectures such as i386 have
started failing, as detailed below (for i386; I haven't cross-checked
other architectures).  Could you please account for these differences
in mangled symbol names?

Thanks!

--- debian/kopano-libs.symbols (kopano-libs_8.3.3-1_i386)
+++ dpkg-gensymbolszTPcxZ  2017-09-11 07:37:24.163161144 +
@@ -48,9 +48,12 @@
  
_Z16conv_out_defaultIN2KC7ECGROUPEjXadL_ZNS1_12ulIsABHiddenvPT_P7_objectPKcPvj@Base
 8.3.2
  
_Z16conv_out_defaultIN2KC7ECQUOTAEbXadL_ZNS1_16bUseDefaultQuotavPT_P7_objectPKcPvj@Base
 8.3.2
  
_Z16conv_out_defaultIN2KC7ECQUOTAEbXadL_ZNS1_19bIsUserDefaultQuotavPT_P7_objectPKcPvj@Base
 8.3.2
- 
_Z16conv_out_defaultIN2KC7ECQUOTAElXadL_ZNS1_10llHardSizevPT_P7_objectPKcPvj@Base
 8.3.2
- 
_Z16conv_out_defaultIN2KC7ECQUOTAElXadL_ZNS1_10llSoftSizevPT_P7_objectPKcPvj@Base
 8.3.2
- 
_Z16conv_out_defaultIN2KC7ECQUOTAElXadL_ZNS1_10llWarnSizevPT_P7_objectPKcPvj@Base
 8.3.2
+#MISSING: 8.3.3-1# 
_Z16conv_out_defaultIN2KC7ECQUOTAElXadL_ZNS1_10llHardSizevPT_P7_objectPKcPvj@Base
 8.3.2
+#MISSING: 8.3.3-1# 
_Z16conv_out_defaultIN2KC7ECQUOTAElXadL_ZNS1_10llSoftSizevPT_P7_objectPKcPvj@Base
 8.3.2
+#MISSING: 8.3.3-1# 
_Z16conv_out_defaultIN2KC7ECQUOTAElXadL_ZNS1_10llWarnSizevPT_P7_objectPKcPvj@Base
 8.3.2
+ 
_Z16conv_out_defaultIN2KC7ECQUOTAExXadL_ZNS1_10llHardSizevPT_P7_objectPKcPvj@Base
 8.3.3-1
+ 
_Z16conv_out_defaultIN2KC7ECQUOTAExXadL_ZNS1_10llSoftSizevPT_P7_objectPKcPvj@Base
 8.3.3-1
+ 
_Z16conv_out_defaultIN2KC7ECQUOTAExXadL_ZNS1_10llWarnSizevPT_P7_objectPKcPvj@Base
 8.3.3-1
  
_Z16conv_out_defaultIN2KC9ECCOMPANYENS0_9ECENTRYIDEXadL_ZNS1_10sCompanyIdvPT_P7_objectPKcPvj@Base
 8.3.2
  
_Z16conv_out_defaultIN2KC9ECCOMPANYENS0_9ECENTRYIDEXadL_ZNS1_14sAdministratorvPT_P7_objectPKcPvj@Base
 8.3.2
  
_Z16conv_out_defaultIN2KC9ECCOMPANYEPwXadL_ZNS1_14lpszServernamevPT_P7_objectPKcPvj@Base
 8.3.2
@@ -69,8 +72,9 @@
  _ZN4priv8conv_outIPwEEvP7_objectPvjPT_@Base 8.3.2
  _ZN4priv8conv_outIbEEvP7_objectPvjPT_@Base 8.3.2
  _ZN4priv8conv_outIjEEvP7_objectPvjPT_@Base 8.3.2
- _ZN4priv8conv_outIlEEvP7_objectPvjPT_@Base 8.3.2
+#MISSING: 8.3.3-1# _ZN4priv8conv_outIlEEvP7_objectPvjPT_@Base 8.3.2
  _ZN4priv8conv_outItEEvP7_objectPvjPT_@Base 8.3.2
+ _ZN4priv8conv_outIxEEvP7_objectPvjPT_@Base 8.3.3-1
 libkcpydirector.so.0 kopano-libs #MINVER#
 #MISSING: 8.3.3-1# (symver|optional)EC_8.1.0 8.0.1
  (symver|optional)KC_8.3 8.3.2

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Processed: reassign 875449 to src:emacs23

[Debian Bug Tracking System]

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

> reassign 875449 src:emacs23 23.4+1-4
Bug #875449 [src:emacs25] emacs23: enriched text remote code execution
Bug reassigned from package 'src:emacs25' to 'src:emacs23'.
No longer marked as found in versions emacs25/25.1+1-4.
Ignoring request to alter fixed versions of bug #875449 to the same values 
previously set
Bug #875449 [src:emacs23] emacs23: enriched text remote code execution
Marked as found in versions emacs23/23.4+1-4.
> thanks
Stopping processing here.

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

Processed (with 1 error): emacs25: enriched text remote code execution

[Debian Bug Tracking System]

Processing control commands:

> clone -1 -2 -3
Bug #875447 [src:emacs25] emacs25: enriched text remote code execution
Bug 875447 cloned as bugs 875448-875449
> reassign -2 src:emacs24 24.4+1-4
Bug #875448 [src:emacs25] emacs25: enriched text remote code execution
Bug reassigned from package 'src:emacs25' to 'src:emacs24'.
No longer marked as found in versions emacs25/25.1+1-4.
Ignoring request to alter fixed versions of bug #875448 to the same values 
previously set
Bug #875448 [src:emacs24] emacs25: enriched text remote code execution
Marked as found in versions emacs24/24.4+1-4.
> retitle -2 emacs24: enriched text remote code execution
Bug #875448 [src:emacs24] emacs25: enriched text remote code execution
Changed Bug title to 'emacs24: enriched text remote code execution' from 
'emacs25: enriched text remote code execution'.
> reassing -3 src:emacs23 23.4+1-4
Unknown command or malformed arguments to command.

> retitle -3 emacs23: enriched text remote code execution
Bug #875449 [src:emacs25] emacs25: enriched text remote code execution
Changed Bug title to 'emacs23: enriched text remote code execution' from 
'emacs25: enriched text remote code execution'.

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

Bug#875447: emacs25: enriched text remote code execution

[Salvatore Bonaccorso]

Source: emacs25
Version: 25.1+1-4
Severity: grave
Tags: patch upstream security
Justification: user security hole
Forwarded: https://bugs.gnu.org/28350
Control: clone -1 -2 -3
Control: reassign -2 src:emacs24 24.4+1-4
Control: retitle -2 emacs24: enriched text remote code execution
Control: reassing -3 src:emacs23 23.4+1-4
Control: retitle -3 emacs23: enriched text remote code execution

Hi

See http://www.openwall.com/lists/oss-security/2017/09/11/1 for
details. The bug has been reported upstream at:

https://bugs.gnu.org/28350

Upstream commit:

https://git.savannah.gnu.org/cgit/emacs.git/commit/?h=emacs-25=9ad0fcc54442a9a01d41be19880250783426db70

Regards,
Salvatore

Bug#875446: libglvnd-dev: overwrites files in old libegl1-mesa-dev

[James Cowgill]

Package: libglvnd-dev
Version: 0.2.999+git20170802-3
Severity: serious

Hi,

On upgrading today I got this error:
> Unpacking libglvnd-dev (0.2.999+git20170802-3) ...
> dpkg: error processing archive 
> /tmp/apt-dpkg-install-Go1Tzy/19-libglvnd-dev_0.2.999+git20170802-3_amd64.deb 
> (--unpack):
>  trying to overwrite '/usr/lib/x86_64-linux-gnu/libEGL.so', which is also in 
> package libegl1-mesa-dev:amd64 17.1.5-1

I am guessing that libglvnd-dev needs to Breaks/Replaces the old mesa
dev packages.

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#873325: marked as done (fastnetmon FTBFS with luajit 2.1)

[Debian Bug Tracking System]

Your message dated Mon, 11 Sep 2017 12:49:36 +
with message-id 
and subject line Bug#873325: fixed in fastnetmon 1.1.3+dfsg-4
has caused the Debian Bug report #873325,
regarding fastnetmon FTBFS with luajit 2.1
to be marked as done.

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

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


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

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

...
In file included from /build/1st/fastnetmon-1.1.3+dfsg/src/fast_library.cpp:3:0:
/build/1st/fastnetmon-1.1.3+dfsg/src/fast_library.h:28:10: fatal error: 
luajit-2.0/lua.hpp: No such file or directory
 #include 
  ^~~~
compilation terminated.
CMakeFiles/fast_library.dir/build.make:65: recipe for target 
'CMakeFiles/fast_library.dir/fast_library.cpp.o' failed
--- End Message ---
--- Begin Message ---
Source: fastnetmon
Source-Version: 1.1.3+dfsg-4

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

Debian distribution maintenance software
pp.
Benjamin Drung  (supplier of updated 
fastnetmon 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: Mon, 11 Sep 2017 14:27:56 +0200
Source: fastnetmon
Binary: fastnetmon
Architecture: source
Version: 1.1.3+dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: Benjamin Drung 
Changed-By: Benjamin Drung 
Description:
 fastnetmon - fast DDoS analyzer with sflow/netflow/mirror support (community e
Closes: 873325
Changes:
 fastnetmon (1.1.3+dfsg-4) unstable; urgency=medium
 .
   * Use pkg-config for finding luajit (Closes: #873325)
   * Enable luajit support on arm64, kfreebsd-amd64, mips64el, ppc64*
Checksums-Sha1:
 5d91f3b5b480ae48ce5df4eccbfc25f6b271a592 2290 fastnetmon_1.1.3+dfsg-4.dsc
 15dedcdf060703e57a5f19d883617630a026fc4b 20288 
fastnetmon_1.1.3+dfsg-4.debian.tar.xz
Checksums-Sha256:
 6d0facf4e1ffeb099e0d7b89cf28604fb0fd9a73649a879823f9f097d4af38a6 2290 
fastnetmon_1.1.3+dfsg-4.dsc
 61330c7622e3db57358d4ef4a7f7ff4e1fd80e77323c36ed4b2ddb7df34c857e 20288 
fastnetmon_1.1.3+dfsg-4.debian.tar.xz
Files:
 7c7a62442156d9b42640232d5d7d045d 2290 net optional fastnetmon_1.1.3+dfsg-4.dsc
 4589d1c93cb909ebe5e9f85150b4debb 20288 net optional 
fastnetmon_1.1.3+dfsg-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJZtoH8AAoJEN2M1aXejH56iY4QAJusAM8habLYlFTAdXGj40vq
72RyY1OXOmQrS/sdWW425ZMyt0c8kCDVVw0bolz+TR+sAgWPN+xXoye85w6AurGp
8lDbvORBbJa1YfTFMj3H/nyxHn57va48PmW7RI+Z+Uy85W7ssfbgYAYkgWLT+MwZ
S+B+Ykn9mbJ8EOpBU2BrrNmP/Wi7s4TGk4mNDo3q/Gm4brylwD8HMNF3TGY5MzqR
aBsjcwX5U2llSNxd/q46HmMXFPFvOYwTWxSR1WNmV98BCLN1nF22XkaDptUUs5Ng
gb1WbtOVPUCYuaJIHLpS4YiyLp511Ke+CPLM0aMd4rGu2xAWlriLV7SD6mLpGcBY
idiqx3PJlV8CCzJw6h3LPN4J3ZeLZDegjhAoKAL8nkA3vRkX5OZwcTvWHfm4976B
A1OPVirLGxB14aVgwqLz5FNPXBegd2KwbnJOjdpdpLWfeNWdehKKgaBoaOLF+kmG
wOdAqrR/SmWlZ9dCSb2cpUP1OFiIA3KPhKMuip+V9rdWY6Snb4KgH1VdeklusS9P
aMdcfrR5cBUFqRl6E7GcITt7TqA2eKXAaSLc2BGNu5jnFjSNeD0S/yHNw2Qk69Mk
vWzXoGjXCUeIv5C79RRsOAIBd5CHl0vJTkuBy3K/DsTXABnakphRCrc1F3cz5BZg
Flz99jC/MYXbbehTEFLk
=Qy5Z
-END PGP SIGNATURE End Message ---

Processed: severity of 875434 is serious

[Debian Bug Tracking System]

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

> severity 875434 serious
Bug #875434 [libqbscore1.8] libqbscore1.8: The package should depend on 
qbs-common
Severity set to 'serious' from 'grave'
> thanks
Stopping processing here.

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

Bug#875434: libqbscore1.8: The package should depend on qbs-common

[Orgad Shaneh]

Package: libqbscore1.8
Version: 1.8.1+dfsg-3
Severity: grave
Justification: renders package unusable

Dear Maintainer,

libqbs is useless without its data files.

Opening a qbs project in Qt Creator when qbs-common is not installed fails on 
parsing.

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

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

Versions of packages libqbscore1.8 depends on:
ii  libc62.24-17
ii  libgcc1  1:7.2.0-4
ii  libgl1   0.2.999+git20170802-3
ii  libgl1-mesa-glx  17.2.0-2
ii  libqt5core5a 5.9.1+dfsg-9
ii  libqt5gui5   5.9.1+dfsg-9
ii  libqt5network5   5.9.1+dfsg-9
ii  libqt5script55.9.1+dfsg-2
ii  libqt5test5  5.9.1+dfsg-9
ii  libqt5xml5   5.9.1+dfsg-9
ii  libstdc++6   7.2.0-4

libqbscore1.8 recommends no packages.

libqbscore1.8 suggests no packages.

-- no debconf information

Bug#874143: marked as done (octave-odepkg FTBFS with octave-pkg-dev 1.5.0)

[Debian Bug Tracking System]

Your message dated Mon, 11 Sep 2017 11:12:46 +
with message-id 
and subject line Bug#874143: fixed in octave-odepkg 0.8.5-3
has caused the Debian Bug report #874143,
regarding octave-odepkg FTBFS with octave-pkg-dev 1.5.0
to be marked as done.

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

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


-- 
874143: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874143
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: octave-odepkg
Version: 0.8.5-2
Severity: serious

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

...
Summary: 619 tests, 618 passed, 0 known failures, 0 skipped
/usr/share/cdbs/1/class/octave-pkg.mk:108: recipe for target 'check-pkg' failed
make: *** [check-pkg] Error 1
--- End Message ---
--- Begin Message ---
Source: octave-odepkg
Source-Version: 0.8.5-3

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

Debian distribution maintenance software
pp.
Rafael Laboissiere  (supplier of updated octave-odepkg 
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: Mon, 11 Sep 2017 06:33:04 -0300
Source: octave-odepkg
Binary: octave-odepkg
Architecture: source amd64
Version: 0.8.5-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Octave Group 
Changed-By: Rafael Laboissiere 
Description:
 octave-odepkg - solve differential equations and initial value problems in 
Octave
Closes: 874143
Changes:
 octave-odepkg (0.8.5-3) unstable; urgency=medium
 .
   * d/p/nan-unit-test-calcmescd.patch: New patch.
 Fix failing unit test, avoing the package to FTBFS with
 octave-pkg-dev 1.5.0. (Closes: #874143)
   * d/control: Bump Standards-Version to 4.1.0 (no changes needed)
Checksums-Sha1:
 0772df6b2420041940440374ada79ce43f4df106 2016 octave-odepkg_0.8.5-3.dsc
 b675606d1fb72fc4900c9828ee8bf7a087aef728 9464 
octave-odepkg_0.8.5-3.debian.tar.xz
 bd02c12e23abd00e586a4c99350db6ebc295e05f 2609684 
octave-odepkg-dbgsym_0.8.5-3_amd64.deb
 c3361c64d92bbba122cdbb47135a949db171fe01 13561 
octave-odepkg_0.8.5-3_amd64.buildinfo
 b9d27aa4a6093c3a941eca558dd356bcaeffecaf 680744 octave-odepkg_0.8.5-3_amd64.deb
Checksums-Sha256:
 f5d2601a6c156a558c3000598db3d682746581b8d1424091816ab41b02b9c181 2016 
octave-odepkg_0.8.5-3.dsc
 8103b5062e397aa1cb0c94b53fc117cc8a193aee080e9d81b7b7ccc84ebac8a0 9464 
octave-odepkg_0.8.5-3.debian.tar.xz
 4342fefd957ea5888fa46c35e6668a34056f7ae1f0f35ee53ec42608f9de5f55 2609684 
octave-odepkg-dbgsym_0.8.5-3_amd64.deb
 047a2a99726aad6e2661fb7622b16526477b76a14d37cd861390a579f042fe07 13561 
octave-odepkg_0.8.5-3_amd64.buildinfo
 603ac19943e9a78d636af2c414fecf1637afd647aff598f808359a3bd0ddb181 680744 
octave-odepkg_0.8.5-3_amd64.deb
Files:
 fce1c65f2936c59ea2ad970d1f73ed39 2016 math optional octave-odepkg_0.8.5-3.dsc
 0d55306c744df2d9ecc2ee4c2ef4a261 9464 math optional 
octave-odepkg_0.8.5-3.debian.tar.xz
 3adfa098d9b9a2d837f19dabe3e58360 2609684 debug optional 
octave-odepkg-dbgsym_0.8.5-3_amd64.deb
 68ffbb0d5bed5635e6a9534e48f0b269 13561 math optional 
octave-odepkg_0.8.5-3_amd64.buildinfo
 c4998b8459a48eafc617e44ac6f5d3d5 680744 math optional 
octave-odepkg_0.8.5-3_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEP0ZDkUmP6HS9tdmPISSqGYN4XJAFAlm2YTsACgkQISSqGYN4
XJA00g/+JIfrt9F7xSMwlRKjE13wS6ADTEaO0LXvJTHUEqgECF89fkzKIjShHvjg
GgslvVK1w85gjUj5Dggds/t/bfFPyUCR/I1lJm68m/XHimj9cq8K3nu9IYWHPXeg
tlxvMr6K8W2idmO8GFCtZLcHSXIyQHvTJ4Dt4pXuxbignuLTaXNc88vATIA7nWIX
/b+4s+aBopuvY3icG7Fvo5s5Ma5o2Cn6K/sMmOEptqZeMdOSW1U44e7afIupsbmQ
ifsL0xeNDFH7QjvGtgu/Fb8xSYC+640pdgU0w3RJa/cytnWGR4jh2CKKtMi8slAt
j6a+APtINV4FCoxTwoSu3MRqtVM6lIVUmmzuWpJw+40UXgbK3T1Hjn6R9GFaSuIn
TWeQt2sgI9lxR9rCLcV7Qb2x/7KIosQGcozhPNezU/eD9MHOab/uGGIiEiX4tQQC
qMmz0004HJRpF70t3J5Em0R9J26qDXrGXbntr4ElIIjf/FGFfhzVswgd8UOJFF1y
dptDhYOmvx8sYGwtEvnEjbZiaQofuEGJTpRQhABiFH9B1ZHma74MxNGLAA427FeQ
5xOZqfR43TrFP6VBdn3HBTWpUrlD6wEP8S4iNBSVb9aT+qnxw1gvJiCrmoksp7ae

Bug#874712: marked as done (python-h5py: all arches FTBFS)

[Debian Bug Tracking System]

Your message dated Mon, 11 Sep 2017 11:08:55 +
with message-id 
and subject line Bug#874712: fixed in h5py 2.7.1-2
has caused the Debian Bug report #874712,
regarding python-h5py: all arches FTBFS
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.)


-- 
874712: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874712
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-h5py
Version: 2.7.0-1+b1
Severity: serious
Justification: FTBFS

Your new version of h5py fails to build from source.  All arches.

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

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

Versions of packages python-h5py depends on:
ii  libc6 2.24-17
ii  libhdf5-100   1.10.0-patch1+docs-4
ii  python2.7.13-2
ii  python-numpy [python-numpy-abi9]  1:1.13.1-1
ii  python-six1.10.0-4

python-h5py recommends no packages.

Versions of packages python-h5py suggests:
ii  python-h5py-doc  2.7.0-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: h5py
Source-Version: 2.7.1-2

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

Debian distribution maintenance software
pp.
Ghislain Antony Vaillant  (supplier of updated h5py package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 11 Sep 2017 10:15:49 +0100
Source: h5py
Binary: python-h5py python-h5py-dbg python3-h5py python3-h5py-dbg 
python-h5py-doc
Architecture: source
Version: 2.7.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Ghislain Antony Vaillant 
Description:
 python-h5py - general-purpose Python interface to hdf5 (Python 2)
 python-h5py-dbg - debug extensions for h5py (Python 2)
 python-h5py-doc - documentation for h5py
 python3-h5py - general-purpose Python interface to hdf5 (Python 3)
 python3-h5py-dbg - debug extensions for h5py (Python 3)
Closes: 874712
Changes:
 h5py (2.7.1-2) unstable; urgency=medium
 .
   * Fixup the debug package description for Python 2.
 Thanks to James Clarke
   * Replace occurrences of findstring with filter.
 Thanks to James Clarke
   * Build and install the low-level API documentation
 - Move Sphinx to Build-Depends
 - Build and install the API documentation
 - New patch Fix-build-of-API-docs-with-Python-3.patch
 Thanks to Drew Parsons for reporting (Closes: #874712)
   * Filter egg-info directory with extend-diff-ignore
   * Add recommended get-orig-source target
Checksums-Sha1:
 c50866d1950447cadf8d401d47f5a4b89589e771 2668 h5py_2.7.1-2.dsc
 96248be13ce3af35b54579ca93ffaf8a5d47d28d 7756 h5py_2.7.1-2.debian.tar.xz
 84920306e3510a20cde5d56899ff77b4318312ce 7750 h5py_2.7.1-2_source.buildinfo
Checksums-Sha256:
 0151d60e96df29a96de0c34509ac1ea003e2fb1c1b03ab3d9e92fbd145603ca2 2668 
h5py_2.7.1-2.dsc
 8ab897a33987642600416065297ba8c67ae73aed9fc11c6e0254b8359616104c 7756 
h5py_2.7.1-2.debian.tar.xz
 693a913e634812c5765f145c720d95147f3a79be93a91819d6d8c27efc11642c 7750 
h5py_2.7.1-2_source.buildinfo
Files:
 4003fa4b3a2ef47f36a4cacb7dd5ed2e 2668 python optional h5py_2.7.1-2.dsc
 108d8691a89107d1ef418daa18687639 7756 python optional 
h5py_2.7.1-2.debian.tar.xz
 b1e645288a3e4b9423be2cf9aefc1ff1 7750 python optional 
h5py_2.7.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEj1g0K+q+HvQ3lVH7sZN3DBhqHH0FAlm2YhsACgkQsZN3DBhq
HH24dA//TG5+7R2f2Zs5f/jQpnwb59LUtv/eq6SIxKZyOBq/9vVqGvfYF2Jx69NM
AkJFmPZZU9usJkXcOgTITv9zZf8V/5/pD8r1Nfvtwng+1f0wZhMFzo9IWo/k/Peh

Bug#784468: marked as done ([goldendict] Qt4's WebKit removal)

[Debian Bug Tracking System]

Your message dated Mon, 11 Sep 2017 11:08:37 +
with message-id 
and subject line Bug#784468: fixed in goldendict 1.5.0~git20160508.g92b5485-3
has caused the Debian Bug report #784468,
regarding [goldendict] Qt4's WebKit removal
to be marked as done.

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

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


-- 
784468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784468
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: goldendict
Version: 1.5.0~git20131003-1
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4webkit-removal

Dear Dmitry E. Oboukhov ,

As you might know we the Qt/KDE team are preparing to remove Qt4's WebKit
as announced in [announce].

[announce] 


Basically we are about to get the latest Qt4 point release and upstream is
migrating from WebKit to Bing in the Qt5 series, so we won't have much upstream
support for maintaining Qt4's WebKit.

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

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

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4. In
order to ease the transition time we have provided Wheezy backports for Qt5.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

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

Ana,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Source: goldendict
Source-Version: 1.5.0~git20160508.g92b5485-3

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

Debian distribution maintenance software
pp.
Dmitry E. Oboukhov  (supplier of updated goldendict package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 11 Sep 2017 11:49:42 +0300
Source: goldendict
Binary: goldendict
Architecture: source amd64
Version: 1.5.0~git20160508.g92b5485-3
Distribution: unstable
Urgency: medium
Maintainer: Dmitry E. Oboukhov 
Changed-By: Dmitry E. Oboukhov 
Description:
 goldendict - feature-rich dictionary lookup program
Closes: 784468 793039 837677 864667
Changes:
 goldendict (1.5.0~git20160508.g92b5485-3) unstable; urgency=medium
 .
   [Dmitry E. Oboukhov]
   * Apply Boyuan Yang changes, sorry for too long timeout.
 .
   [Boyuan Yang <073p...@gmail.com>]
   * Non-maintainer upload.
   * Ack previous upload. Thank you Gianfranco!
   * Add myself into uploaders list. (Hijacking package)
   * Add watch file. (Closes: #793039)
   * Update Vcs-* field. (Closes: #864667)
   * Drop .install file. (Closes: #837677)
   * Drop .menu file as per ctte's decision.
   * Build against Qt5. (Closes: #784468)
Checksums-Sha1:
 9ec9b2ef1f78b9d5e3c759acc7b5dc90911d8d6e 2380 
goldendict_1.5.0~git20160508.g92b5485-3.dsc
 dbae5a0ed89d4d06314e6af3538f7d04f3b44a26 10424 
goldendict_1.5.0~git20160508.g92b5485-3.debian.tar.xz
 19f57674e56d4077975fad1ca7d22294c78033e7 12134 
goldendict_1.5.0~git20160508.g92b5485-3_amd64.buildinfo
 f4f0feadc240f5a84a583b5b70b72cbe714bd07e 

Bug#874141: marked as done (octave-statistics FTBFS with octave-pkg-dev 1.5.0)

[Debian Bug Tracking System]

Your message dated Mon, 11 Sep 2017 10:30:23 +
with message-id 
and subject line Bug#874141: fixed in octave-statistics 1.3.0-2
has caused the Debian Bug report #874141,
regarding octave-statistics FTBFS with octave-pkg-dev 1.5.0
to be marked as done.

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

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


-- 
874141: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874141
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: octave-statistics
Version: 1.3.0-1
Severity: serious
Tags: buster sid

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

...
Summary: 948 tests, 938 passed, 0 known failures, 0 skipped
/usr/share/cdbs/1/class/octave-pkg.mk:108: recipe for target 'check-pkg' failed
make: *** [check-pkg] Error 1
--- End Message ---
--- Begin Message ---
Source: octave-statistics
Source-Version: 1.3.0-2

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

Debian distribution maintenance software
pp.
Rafael Laboissiere  (supplier of updated octave-statistics 
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: Mon, 11 Sep 2017 01:03:46 -0300
Source: octave-statistics
Binary: octave-statistics
Architecture: source all
Version: 1.3.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Octave Group 
Changed-By: Rafael Laboissiere 
Description:
 octave-statistics - additional statistical functions for Octave
Closes: 874141
Changes:
 octave-statistics (1.3.0-2) unstable; urgency=medium
 .
   [ Sébastien Villemot ]
   * d/copyright: use secure URL for format.
   * d/watch: bump to format version 4.
 .
   [ Rafael Laboissiere ]
   * d/control:
 + Use cgit instead of gitweb in Vcs-Browser URL
 + Build-conflict with octave-nan (colision with function 'mad')
 + Bump Standards-Version to 4.1.0 (no changes needed)
 + Build-depends on octave-common > 4.2.1-3. This is necessary
   because this version of the octave-common package
   contains the function corrcoef, necessary for the unit tests.
   * New patches (avoid FTBFS with octave-pkg-dev 1.5.0, closes: #874141):
 + d/p/pval-in-ttest-unit-test.patch
 + d/p/xtests-in-grp2idx.patch
 + d/p/tsquare-in-princomp-unit-tests.patch
Checksums-Sha1:
 cd57c8b282f33fa1624630b19c5b69457e5e46a1 2181 octave-statistics_1.3.0-2.dsc
 bec9e98bd62409782e6862e9e46a4e2f2c4a13a7 6576 
octave-statistics_1.3.0-2.debian.tar.xz
 7881e506a60b4e8516bd907d78d9e6b214d31feb 133750 
octave-statistics_1.3.0-2_all.deb
 98d90854271821dfa9c8e7b7de2ce9dd57edc19c 12181 
octave-statistics_1.3.0-2_amd64.buildinfo
Checksums-Sha256:
 5cf9df99a0d45cbc1d85cec99c6c53163ee71d7be4c7dad2fce02206bfb666c8 2181 
octave-statistics_1.3.0-2.dsc
 5a52dcfcf01e3593b78f36f5bedb6d0c5f271de231eac0b6060a6a0e4fd1c948 6576 
octave-statistics_1.3.0-2.debian.tar.xz
 b8241d9ee8c906974355c1acef15f8be90876c156d516c285281472f0d64d20b 133750 
octave-statistics_1.3.0-2_all.deb
 970daa246a4faf382d95b260606f369dd37e846e201a6f11a3556d9d8f4e8354 12181 
octave-statistics_1.3.0-2_amd64.buildinfo
Files:
 d8709085a3b2d36ae20507a40705f0d8 2181 math optional 
octave-statistics_1.3.0-2.dsc
 61eb1f61228378b0ce59bcd4c2374607 6576 math optional 
octave-statistics_1.3.0-2.debian.tar.xz
 8d95d2df7ac153a1b51d7ec3d430c378 133750 math optional 
octave-statistics_1.3.0-2_all.deb
 3ef30870071f2ba58087639e5544e7a4 12181 math optional 
octave-statistics_1.3.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEP0ZDkUmP6HS9tdmPISSqGYN4XJAFAlm2WjMACgkQISSqGYN4
XJBFZRAAmrjGj1HkluNAmPUA9zJf2VVx/xZq1KKCUXfRnF7VyBINABs49NilzLB8
bbFunFfrtDgUanW1sqxCBmA3K/EGkAh5D3xEVTvdqiAWVcdVg17B+8/O/7d7WuXl
fMEh2TC1Yd0kopcBtXn1+frPDn8wtW8UbY6HdvuVI9OC4wS0BBXC4LPncNt8Qiue
XmukhFi6pwZhjOOH5BJBYLdpWBvzxLFhWuEbIbyupyra3wiSKYZrSja730/CUUae
MYZ/8N/w2SwySeUznueoe7+3t1YyUiTrvlgDp9va5j5oPJg8HZLjV7ojOOAv+3tO
sDzp1sQ6vexWjzIJBcU7NKlEi+SMpl4bcYRrrXcrUzw+6vrVmVL+Do9aL3BrmGIo

Bug#875423: openssl: Please re-enable TLS 1.0 and TLS 1.1 (at least in testing)

[Raphael Hertzog]

On Mon, 11 Sep 2017, Philipp Kern wrote:
> https://packages.qa.debian.org/o/openssl/news/20170824T211015Z.html seems to
> have pushed this onto client applications? I.e. it's no longer hard disabled
> but client applications need to explicitly enable them?

Yes, I'm aware of that but Kurt never said that he would be willing to
back off from completely disabling it before the buster release and
I don't see any benefit in modifying all server applications to re-enable
the protocols that we want to support out-of-the box because there 
are (outside of Debian) old applications that will have to connect to
those servers.

I understand we need to fix the client applications that we ship in Debian
so that they work with TLS 1.2-only servers and for this it might be
useful to disable TLS 1.0 and TLS 1.1 by default in unstable for a while.

But in Debian testing, we have real end-users (direct and through
"rolling" derivatives) and they should not have to be impacted by this
experiment IMO.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/

Bug#875430: emacs25: please add Breaks: edb (<< 1.32)

[Andreas Beckmann]

Package: emacs25
Version: 25.2+1-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

emacs25 fails to install if edb 1.31 is installed, see #840748 for the
edb bug, which suggests that this is fixed in the next upstream release
of edb.

To ensure smooth upgrades to emacs25, we need a Breaks against the
problematic version, s.t. edb either gets upgraded or removed.


Andreas

Processed: not serious

[Debian Bug Tracking System]

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

> severity 874191 normal
Bug #874191 [selinux-policy-default] gdm3 started users start in wrong context
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#874191: not serious

[Russell Coker]

severity 874191 normal
thanks

Daemon in the wrong domain is not a reason to have the package removed from 
testing.

-- 
My Main Blog http://etbe.coker.com.au/
My Documents Bloghttp://doc.coker.com.au/

Bug#874143: [pkg-octave/master] d/p/nan-unit-test-calcmescd.patch: New patch

[Rafael Laboissiere]

tag 874143 pending
thanks

Date: Mon Sep 11 06:24:22 2017 -0300
Author: Rafael Laboissiere 
Commit ID: e009cf318c5d7f02f0d104ef3ebc105cbf4251db
Commit URL: 
https://anonscm.debian.org/cgit/pkg-octave/octave-odepkg.git;a=commitdiff;h=e009cf318c5d7f02f0d104ef3ebc105cbf4251db
Patch URL: 
https://anonscm.debian.org/cgit/pkg-octave/octave-odepkg.git;a=commitdiff_plain;h=e009cf318c5d7f02f0d104ef3ebc105cbf4251db

d/p/nan-unit-test-calcmescd.patch: New patch

Fix failing unit test, avoing the package to FTBFS with
octave-pkg-dev 1.5.0.

Gbp-Dch: Full
Closes: #874143
  

Bug#875423: openssl: Please re-enable TLS 1.0 and TLS 1.1 (at least in testing)

[Philipp Kern]

On 2017-09-11 11:33, Raphaël Hertzog wrote:

I looked back at the debian-devel discussion and it seems to me that
the majority of persons who expressed themselves (including Moritz 
Mühlenhoff
of the Debian security team) believe that buster should ship with TLS 
1.0

and TLS 1.1 enabled.

Given this, I would like to request you to make sure that Debian 
testing

has a version of openssl with TLS 1.0 and TLS 1.1 enabled.

The rough consensus seems to be that it's ok for you to use Debian
unstable as a test-bed for your experiment to disable TLS 1.0 and TLS 
1.1.


While that might not be practical to manage when you have to push an
update to testing, it's a burden that you should accept since you
believe that Debian experimental will not give enough exposure.

Please do listen to your fellow developers. Thank you.

Cheers,

PS: I'm filing this because I would like to not have to fork OpenSSL
for Kali. It's counter-productive to go too fast in deprecating old
protocols. You will only get less users using the official Debian
package with all the risks it involves.

Or at least I would like a system-wide flag (in a configuration file?) 
to

let me re-enable old protocols easily.


https://packages.qa.debian.org/o/openssl/news/20170824T211015Z.html 
seems to have pushed this onto client applications? I.e. it's no longer 
hard disabled but client applications need to explicitly enable them?


Kind regards
Philipp Kern

Processed: [pkg-octave/master] d/p/nan-unit-test-calcmescd.patch: New patch

[Debian Bug Tracking System]

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

> tag 874143 pending
Bug #874143 [src:octave-odepkg] octave-odepkg FTBFS with octave-pkg-dev 1.5.0
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#875425: Unknown symbol init_mm (err 0)

[積丹尼 Dan Jacobson]

Package: nvidia-legacy-304xx-driver
Version: 304.135-4
Severity: grave

Please install the changes like
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1711758

Else 4.12 kernel is unusable.

Processed: user debian...@lists.debian.org, usertagging 870831, affects 870831, tagging 871083 ...

[Debian Bug Tracking System]

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

> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 870831 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 870831 + brotli
Bug #870831 [libbrotli0.6.0] Broken symbols file creates broken dependencies
Added indication that 870831 affects brotli
> tags 871083 - sid
Bug #871083 [src:python-pysam] python-pysam: FTBFS: Test failures
Removed tag(s) sid.
> unarchive 810694
Bug #810694 {Done: Ying-Chun Liu (PaulLiu) } 
[west-chamber-dkms] west-chamber-dkms: does not clean after module build
Unarchived Bug 810694
> reopen 810694
Bug #810694 {Done: Ying-Chun Liu (PaulLiu) } 
[west-chamber-dkms] west-chamber-dkms: does not clean after module build
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions west-chamber/20100405+svn2007.r124-6.
> found 810694 20100405+svn2007.r124-7
Bug #810694 [west-chamber-dkms] west-chamber-dkms: does not clean after module 
build
Marked as found in versions west-chamber/20100405+svn2007.r124-7.
> found 857529 libgpgmepp-dev
Bug #857529 [libgpgmepp-dev] libgpgmepp-dev: broken symlink: 
/usr/share/doc/libgpgmepp-dev/README.qgpgme -> ../libqgpgme/README
There is no source info for the package 'libgpgmepp-dev' at version 
'libgpgmepp-dev' with architecture ''
Unable to make a source version for version 'libgpgmepp-dev'
Marked as found in versions libgpgmepp-dev.
> found 857522 1:9.10.3.dfsg.P4-12.6
Bug #857522 [libbind-export-dev] libbind-export-dev: broken symlinks: 
/usr/lib/x86_64-linux-gnu/liblwres-export.so -> 
/lib/x86_64-linux-gnu/liblwres-export.so.141, 
/usr/lib/x86_64-linux-gnu/libbind9.so -> libbind9.so.140.0.10
Marked as found in versions bind9/1:9.10.3.dfsg.P4-12.6.
> affects 857680 + llvm-6.0-examples
Bug #857680 [llvm-3.8-examples] llvm-3.8-examples: broken symlinks: 
/usr/share/doc/llvm-3.8-examples/Makefile.* -> 
../../../lib/llvm-3.8/build/Makefile.*
Added indication that 857680 affects llvm-6.0-examples
> found 857680 llvm-6.0-examples/1:6.0~svn311834-1
Bug #857680 [llvm-3.8-examples] llvm-3.8-examples: broken symlinks: 
/usr/share/doc/llvm-3.8-examples/Makefile.* -> 
../../../lib/llvm-3.8/build/Makefile.*
The source llvm-6.0-examples and version 1:6.0~svn311834-1 do not appear to 
match any binary packages
Marked as found in versions llvm-6.0-examples/1:6.0~svn311834-1.
> thanks
Stopping processing here.

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

Bug#875423: openssl: Please re-enable TLS 1.0 and TLS 1.1 (at least in testing)

[Raphaël Hertzog]

Source: openssl
Version: 1.1.0f-5
Severity: serious

Hello Kurt,

I looked back at the debian-devel discussion and it seems to me that
the majority of persons who expressed themselves (including Moritz Mühlenhoff
of the Debian security team) believe that buster should ship with TLS 1.0
and TLS 1.1 enabled.

Given this, I would like to request you to make sure that Debian testing
has a version of openssl with TLS 1.0 and TLS 1.1 enabled.

The rough consensus seems to be that it's ok for you to use Debian
unstable as a test-bed for your experiment to disable TLS 1.0 and TLS 1.1.

While that might not be practical to manage when you have to push an
update to testing, it's a burden that you should accept since you
believe that Debian experimental will not give enough exposure.

Please do listen to your fellow developers. Thank you.

Cheers,

PS: I'm filing this because I would like to not have to fork OpenSSL
for Kali. It's counter-productive to go too fast in deprecating old
protocols. You will only get less users using the official Debian
package with all the risks it involves.

Or at least I would like a system-wide flag (in a configuration file?) to
let me re-enable old protocols easily.

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

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

-- no debconf information

Bug#875422: libgrok-dev: missing Depends: libgrok1 (= ${binary:Version})

[Andreas Beckmann]

Package: libgrok-dev
Version: 1.20110708.1-4.2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

0m20.8s ERROR: FAIL: Broken symlinks:
  /usr/lib/x86_64-linux-gnu/libgrok.so -> libgrok.so.1


cheers,

Andreas


libgrok-dev_1.20110708.1-4.2+b1.log.gz
Description: application/gzip

Bug#875421: libexecs-dev: missing Depends: libexecs-embedded0 (= ${binary:Version})

[Andreas Beckmann]

Package: libexecs-dev
Version: 1.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

0m23.0s ERROR: FAIL: Broken symlinks:
  /usr/lib/x86_64-linux-gnu/libexecs-embedded.so -> libexecs-embedded.so.0.9.0


cheers,

Andreas


libexecs-dev_1.0-1.log.gz
Description: application/gzip

Bug#875417: gitlab: fails to install: could not find compatible versions for gem "rack-test"

[Andreas Beckmann]

Package: gitlab
Version: 8.13.11+dfsg1-11
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Selecting previously unselected package gitlab.
  (Reading database ... 
(Reading database ... 33745 files and directories currently installed.)
  Preparing to unpack .../gitlab_8.13.11+dfsg1-11_all.deb ...
  Unpacking gitlab (8.13.11+dfsg1-11) ...
  Setting up gitlab (8.13.11+dfsg1-11) ...
  Creating/updating gitlab user account...
  adduser: Warning: The home directory `/var/lib/gitlab' does not belong to the 
user you are currently creating.
  Making gitlab owner of /var/lib/gitlab...
  [ESC][31mBundler could not find compatible versions for gem "rack-test":
In Gemfile:
  rails (>= 4.2.7.1, ~> 4.2) was resolved to 4.2.9, which depends on
actionpack (= 4.2.9) was resolved to 4.2.9, which depends on
  rack-test (~> 0.6.2)
  
  Could not find gem 'rack-test (~> 0.6.2)', which is required by gem 
'actionpack
  (= 4.2.9)', in any of the sources.[ESC][0m
  dpkg: error processing package gitlab (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   gitlab


cheers,

Andreas


gitlab_8.13.11+dfsg1-11.log.gz
Description: application/gzip

Bug#875413: open-infrastructure-package-tracker: fails to reinstall: ln: failed to create symbolic link '/var/lib/package-tracker//etc/apt/trusted.gpg': File exists

[Andreas Beckmann]

Package: open-infrastructure-package-tracker
Version: 20170515-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to reinstall
the same version that was already installed.

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

0m27.0s DEBUG: Starting command: ['chroot', '/tmp/piupartss/tmpaJIkZj', 
'apt-get', '-y', 'install', '--reinstall', 
'open-infrastructure-package-tracker=20170515-1']
0m27.7s DUMP: 
  Reading package lists...
  Building dependency tree...
  Reading state information...
  debconf: delaying package configuration, since apt-utils is not installed
  0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
  Need to get 0 B/15.3 kB of archives.
  After this operation, 0 B of additional disk space will be used.
  (Reading database ... 
(Reading database ... 5983 files and directories currently installed.)
  Preparing to unpack 
.../open-infrastructure-package-tracker_20170515-1_all.deb ...
  Unpacking open-infrastructure-package-tracker (20170515-1) over (20170515-1) 
...
  Setting up open-infrastructure-package-tracker (20170515-1) ...
  ln: failed to create symbolic link 
'/var/lib/package-tracker//etc/apt/trusted.gpg': File exists
  dpkg: error processing package open-infrastructure-package-tracker 
(--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   open-infrastructure-package-tracker
  E: Sub-process /usr/bin/dpkg returned an error code (1)
0m27.7s ERROR: Command failed (status=100): ['chroot', 
'/tmp/piupartss/tmpaJIkZj', 'apt-get', '-y', 'install', '--reinstall', 
'open-infrastructure-package-tracker=20170515-1']


cheers,

Andreas


open-infrastructure-package-tracker_20170515-1.log.gz
Description: application/gzip

Bug#875400: gammaray: B-D on qt3d-assimpsceneio-plugin which was removed

[Andreas Beckmann]

Source: gammaray
Version: 2.7.0-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
User: debian...@lists.debian.org
Usertags: piuparts

gammaray can no longer be built in sid since qt3d-assimpsceneio-plugin
is gone from the archive.


Andreas

Bug#875399: AttributeError: type object 'Theme' has no attribute 'themes'

[Ondřej Nový]

Source: sphinx-testing
Severity: grave
Justification: renders package unusable

Hi,

after upgrade to Sphinx 1.6, this package is not working:

Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/sphinx_testing/util.py", line 151, in 
decorator
app.cleanup()
  File "/usr/lib/python2.7/dist-packages/sphinx_testing/util.py", line 96, in 
cleanup
Theme.themes.clear()
AttributeError: type object 'Theme' has no attribute 'themes'

Version 0.7.2 should fix this, see 
https://github.com/sphinx-doc/sphinx-testing/commit/5e09ddb5989e77ddf84f2be919ce5ece7413c0ce

Thanks for fixing.

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

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

Bug#875396: haskell-vector: FTBFS on any-i386

[Samuel Thibault]

Source: haskell-vector
Version: 0.12.0.1-1
Severity: serious
Justification: FTBFS

Hello,

In case you have not noticed, the haskell-vector fails the tests on i386
ports (at least i386 and hurd-i386 failed, kfreebsd-i386 hasn't tried
yet).

Samuel


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-debug'), (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 4.13.0 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-- 
Samuel
 Ça peut être une madeleine à sous munitions (avec des composants,
par exemple)
 -+- #runtime -+-

Bug#875387: efl: FTBFS in experimental: lib/elua/elua.c:358:7: error: unknown type name 'luaL_reg'

[Andreas Beckmann]

Source: efl
Version: 1.18.4-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + libevas-loaders

Hi,

efl FTBFS in experimental:

lib/elua/elua.c:358:7: error: unknown type name 'luaL_reg'
 const luaL_reg gettextlib[] =
   ^~~~
lib/elua/elua.c:360:4: warning: braces around scalar initializer
{ "bind_textdomain", _elua_gettext_bind_textdomain },
^
lib/elua/elua.c:360:4: note: (near initialization for 'gettextlib[0]')
lib/elua/elua.c:360:6: warning: initialization makes integer from pointer 
without a cast [-Wint-conversion]
{ "bind_textdomain", _elua_gettext_bind_textdomain },
  ^
lib/elua/elua.c:360:6: note: (near initialization for 'gettextlib[0]')
lib/elua/elua.c:360:6: error: initializer element is not computable at load time
lib/elua/elua.c:360:6: note: (near initialization for 'gettextlib[0]')
lib/elua/elua.c:360:25: warning: excess elements in scalar initializer
{ "bind_textdomain", _elua_gettext_bind_textdomain },
 ^
lib/elua/elua.c:360:25: note: (near initialization for 'gettextlib[0]')
lib/elua/elua.c:361:4: warning: braces around scalar initializer
{ "get_message_language", _elua_get_message_language },
^
lib/elua/elua.c:361:4: note: (near initialization for 'gettextlib[1]')
lib/elua/elua.c:361:6: warning: initialization makes integer from pointer 
without a cast [-Wint-conversion]
{ "get_message_language", _elua_get_message_language },
  ^~
lib/elua/elua.c:361:6: note: (near initialization for 'gettextlib[1]')
lib/elua/elua.c:361:6: error: initializer element is not computable at load time
lib/elua/elua.c:361:6: note: (near initialization for 'gettextlib[1]')
lib/elua/elua.c:361:30: warning: excess elements in scalar initializer
{ "get_message_language", _elua_get_message_language },
  ^~
[...]


Andreas


efl.experimental.build.gz
Description: application/gzip

Processed: found 874802 in 3.10.3-4, found 874802 in 3.2.1+dfsg-1, found 874803 in 3.10.3-4 ...

[Debian Bug Tracking System]

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

> found 874802 3.10.3-4
Bug #874802 [libatlas3-base,libcblas3] libcblas3 and libatlas3-base: error when 
trying to install together
There is no source info for the package 'libcblas3' at version '3.10.3-4' with 
architecture ''
Marked as found in versions atlas/3.10.3-4.
> found 874802 3.2.1+dfsg-1
Bug #874802 [libatlas3-base,libcblas3] libcblas3 and libatlas3-base: error when 
trying to install together
There is no source info for the package 'libatlas3-base' at version 
'3.2.1+dfsg-1' with architecture ''
Marked as found in versions clapack/3.2.1+dfsg-1.
> found 874803 3.10.3-4
Bug #874803 [libatlas-base-dev,libcblas-dev] libcblas-dev and 
libatlas-base-dev: error when trying to install together
There is no source info for the package 'libcblas-dev' at version '3.10.3-4' 
with architecture ''
Marked as found in versions atlas/3.10.3-4.
> found 874803 3.2.1+dfsg-1
Bug #874803 [libatlas-base-dev,libcblas-dev] libcblas-dev and 
libatlas-base-dev: error when trying to install together
There is no source info for the package 'libatlas-base-dev' at version 
'3.2.1+dfsg-1' with architecture ''
Marked as found in versions clapack/3.2.1+dfsg-1.
> thanks
Stopping processing here.

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

Processed: efl: FTBFS in experimental: lib/elua/elua.c:358:7: error: unknown type name 'luaL_reg'

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + libevas-loaders
Bug #875387 [src:efl] efl: FTBFS in experimental: lib/elua/elua.c:358:7: error: 
unknown type name 'luaL_reg'
Added indication that 875387 affects libevas-loaders

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

Bug#875386: phonetisaurus: FTBFS: error: 'EncodeTable' does not name a type

[Andreas Beckmann]

Source: phonetisaurus
Version: 0.7.8-6
Severity: serious
Justification: fails to build from source (but built successfully in the past)
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

phonetisaurus FTBFS in experimental:

[..]
g++ -g -O2 -fdebug-prefix-map=/build/phonetisaurus-0.7.8=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall 
-I3rdparty/utfcpp -g -O2 -fdebug-prefix-map=/build/phonetisaurus-0.7.8=. 
-fstack-protector-
strong -Wformat -Werror=format-security -std=c++11 -Wdate-time 
-D_FORTIFY_SOURCE=2  -c PhonetisaurusE2F.cpp -o PhonetisaurusE2F.o
In file included from PhonetisaurusE2F.cpp:32:0:
PhonetisaurusE2F.hpp:62:27: error: 'EncodeTable' does not name a type
   PhonetisaurusE2F( const EncodeTable& table, int _verbose, bool 
_allow_ins,
   ^~~
PhonetisaurusE2F.hpp:62:38: error: expected ',' or '...' before '<' token
   PhonetisaurusE2F( const EncodeTable& table, int _verbose, bool 
_allow_ins,
  ^
PhonetisaurusE2F.hpp:86:36: error: 'EncodeTable' does not name a type
   void _make_loop_and_iomap( const EncodeTable& table );
^~~
PhonetisaurusE2F.hpp:86:47: error: expected ',' or '...' before '<' token
   void _make_loop_and_iomap( const EncodeTable& table );
   ^
PhonetisaurusE2F.cpp:62:43: error: 'EncodeTable' does not name a type
 PhonetisaurusE2F::PhonetisaurusE2F( const EncodeTable& table, int 
_verbose, bool _allow_ins,
   ^~~
PhonetisaurusE2F.cpp:62:54: error: expected ',' or '...' before '<' token
 PhonetisaurusE2F::PhonetisaurusE2F( const EncodeTable& table, int 
_verbose, bool _allow_ins,
  ^
PhonetisaurusE2F.cpp: In constructor 'PhonetisaurusE2F::PhonetisaurusE2F(int)':
PhonetisaurusE2F.cpp:72:15: error: '_verbose' was not declared in this scope
   verbose   = _verbose;
   ^~~~
PhonetisaurusE2F.cpp:72:15: note: suggested alternative: 'verbose'
   verbose   = _verbose;
   ^~~~
   verbose
PhonetisaurusE2F.cpp:73:15: error: '_allow_ins' was not declared in this scope
   allow_ins = _allow_ins;
   ^~
PhonetisaurusE2F.cpp:73:15: note: suggested alternative: 'allow_ins'
   allow_ins = _allow_ins;
   ^~
   allow_ins
PhonetisaurusE2F.cpp:76:11: error: '_isyms' was not declared in this scope
   isyms = _isyms;
   ^~
PhonetisaurusE2F.cpp:76:11: note: suggested alternative: 'isyms'
   isyms = _isyms;
   ^~
   isyms
[..]


Cheers,

Andreas


phonetisaurus.build.gz
Description: application/gzip

Bug#873271: marked as done (pam-krb5-migrate: install paths are wrong)

[Debian Bug Tracking System]

Your message dated Mon, 11 Sep 2017 07:00:40 +
with message-id 
and subject line Bug#873271: fixed in pam-krb5-migrate 0.0.11-5
has caused the Debian Bug report #873271,
regarding pam-krb5-migrate: install paths are wrong
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.)


-- 
873271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873271
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pam-krb5-migrate
Version: 0.0.11-4
Severity: grave
Justification: renders package unusable

Both the PAM modules and the pam config are installed into
sub-directories instead of their correct places. This makes the package
unusable without moving files in system locations around beforehand.

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

Kernel: Linux 4.9.0-3-amd64 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: pam-krb5-migrate
Source-Version: 0.0.11-5

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

Debian distribution maintenance software
pp.
Dominik George  (supplier of updated pam-krb5-migrate 
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, 29 Aug 2017 00:47:53 +0200
Source: pam-krb5-migrate
Binary: libpam-krb5-migrate-heimdal libpam-krb5-migrate-mit
Architecture: source amd64
Version: 0.0.11-5
Distribution: unstable
Urgency: medium
Maintainer: Dominik George 
Changed-By: Dominik George 
Description:
 libpam-krb5-migrate-heimdal - PAM module for migrating to Heimdal Kerberos
 libpam-krb5-migrate-mit - PAM module for migrating to MIT Kerberos
Closes: 724346 873147 873271
Changes:
 pam-krb5-migrate (0.0.11-5) unstable; urgency=medium
 .
   * Adopt package. (Closes: #724346)
 + Move packaging repo to collab-maint.
 + Update maintainer.
 + Update standards version to 4.1.0.
 + Update compat level.
   * Re-introduce Heimdal support. (Closes: #873147)
 + Debian has avoided dropping Heimdal.
   * Fix install paths of modules and pam-config. (Closes: #873271)
   * Make package multi-arch compliant.
   * Add homepage field.
Checksums-Sha1:
 74e281c33c270f91248d366d7e753f76badfdf53 2124 pam-krb5-migrate_0.0.11-5.dsc
 66054fe454dc6405f2c274eff33bb813befbea5a 4544 
pam-krb5-migrate_0.0.11-5.debian.tar.xz
 d4c510947b53a242b1cd91b63fac1063d402c20b 14226 
libpam-krb5-migrate-heimdal-dbgsym_0.0.11-5_amd64.deb
 308334242c010e793e9592b7a30c920bf99192d5 11832 
libpam-krb5-migrate-heimdal_0.0.11-5_amd64.deb
 c25d7b01e2f63efce9af6511cb7e49c40ac7fa4e 13238 
libpam-krb5-migrate-mit-dbgsym_0.0.11-5_amd64.deb
 e1bfe2ffc15b56a22595779e3024cc758426b38c 10482 
libpam-krb5-migrate-mit_0.0.11-5_amd64.deb
 ebf5e7bf5a86ecc1842959b78a7c354f6f551e6b 7819 
pam-krb5-migrate_0.0.11-5_amd64.buildinfo
Checksums-Sha256:
 c44a099d064455eda5a1fc6baf7aa37a9b7f7bd5e2a13ff8e92dfb525abdf379 2124 
pam-krb5-migrate_0.0.11-5.dsc
 dedd4bb6e94faa6ffabc4e604edb671846671edda32da0c8128cf8dcc0a83531 4544 
pam-krb5-migrate_0.0.11-5.debian.tar.xz
 7a0bca59a0945aee03310e04d15c2662f318604c87e1871bbff05e6e4c56ab29 14226 
libpam-krb5-migrate-heimdal-dbgsym_0.0.11-5_amd64.deb
 87e247acb61325acd4555c5889975dd945e6cb0872e3c2addfb1ae6c9bcb4a03 11832 
libpam-krb5-migrate-heimdal_0.0.11-5_amd64.deb
 cefeec65895c2692ca0418a76d39b3d3b891bc30df30103e62425bfc7a1dd10d 13238 
libpam-krb5-migrate-mit-dbgsym_0.0.11-5_amd64.deb
 89c142dd6a50d1b0e13243ba73523c504f1fb4bb3a62e757d37cad0542f4b4ce 10482 
libpam-krb5-migrate-mit_0.0.11-5_amd64.deb
 6891593eb39d4f29d401b1fec8d887460ce9f852c8a66aaa7af088c5bd608c7f 7819 
pam-krb5-migrate_0.0.11-5_amd64.buildinfo
Files:
 9b403b94be46283d3783b133d7612d55 2124 admin optional 
pam-krb5-migrate_0.0.11-5.dsc
 291a274986d54ef085f7c6aa457a1346 4544 admin 

Bug#874423: marked as done (libpinyin-data: fails to upgrade from 'sid' - trying to overwrite /usr/lib/x86_64-linux-gnu/libpinyin/data/addon_phrase_index.bin)

[Debian Bug Tracking System]

Your message dated Mon, 11 Sep 2017 07:00:38 +
with message-id 
and subject line Bug#874423: fixed in libpinyin 2.1.0-1~exp1
has caused the Debian Bug report #874423,
regarding libpinyin-data: fails to upgrade from 'sid' - trying to overwrite 
/usr/lib/x86_64-linux-gnu/libpinyin/data/addon_phrase_index.bin
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.)


-- 
874423: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874423
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libpinyin-data
Version: 2.0.92-1~exp1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

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

  Selecting previously unselected package libpinyin-data:amd64.
  Preparing to unpack .../libpinyin-data_2.0.92-1~exp1_amd64.deb ...
  Unpacking libpinyin-data:amd64 (2.0.92-1~exp1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libpinyin-data_2.0.92-1~exp1_amd64.deb (--unpack):
   trying to overwrite 
'/usr/lib/x86_64-linux-gnu/libpinyin/data/addon_phrase_index.bin', which is 
also in package libpinyin7:amd64 1.3.0-3
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libpinyin-data_2.0.92-1~exp1_amd64.deb


cheers,

Andreas


libpinyin7=1.3.0-3_libpinyin-data=2.0.92-1~exp1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libpinyin
Source-Version: 2.1.0-1~exp1

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

Debian distribution maintenance software
pp.
ChangZhuo Chen (陳昌倬)  (supplier of updated libpinyin 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, 06 Sep 2017 18:41:11 +0800
Source: libpinyin
Binary: libpinyin-common-dev libpinyin13-dev libpinyin13 libpinyin-data 
libpinyin-utils libzhuyin13 libzhuyin-dev
Architecture: source amd64
Version: 2.1.0-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: IME Packaging Team 
Changed-By: ChangZhuo Chen (陳昌倬) 
Description:
 libpinyin-common-dev - library to deal with PinYin / zhuyin - common 
development files
 libpinyin-data - Data for PinYin / zhuyin input method library
 libpinyin-utils - library to deal with PinYin - utilities
 libpinyin13 - library to deal with PinYin
 libpinyin13-dev - library to deal with PinYin - development files
 libzhuyin-dev - Development files for zhuyin input method library
 libzhuyin13 - Zhuyin input method library
Closes: 874423
Changes:
 libpinyin (2.1.0-1~exp1) experimental; urgency=medium
 .
   * New upstream release.
   * Bump SO version to 13.
   * Add Breaks/Replaces in libpinyin-data for data transferred from libpinyin7
 to libpinyin-data (Closes: #874423).
Checksums-Sha1:
 52605f60d64c5fd67ac208faefc315bff8728f5f 2541 libpinyin_2.1.0-1~exp1.dsc
 ced534294469442a8371bdd15df6a24504b4f8b7 19593494 libpinyin_2.1.0.orig.tar.gz
 2d2fc298c29c105995e86324136af5d95371c31f 5308 
libpinyin_2.1.0-1~exp1.debian.tar.xz
 65e60471c3aada6c02f7dc764a5853da27c91464 5792 
libpinyin-common-dev_2.1.0-1~exp1_amd64.deb
 946488a39653c4c3d8f1846c01368735a5cbbb86 11014156 
libpinyin-data_2.1.0-1~exp1_amd64.deb
 bbe6c81031343e73fbfb728242b0e1e936839be1 1072348 
libpinyin-utils-dbgsym_2.1.0-1~exp1_amd64.deb
 6cc9b7461d6ddc2fccb694ab357e8aaae4b69b3b 232090 
libpinyin-utils_2.1.0-1~exp1_amd64.deb
 d8c2ef42a77bf02083ce97d06815f1af97c8d186 1066712 
libpinyin13-dbgsym_2.1.0-1~exp1_amd64.deb
 b49ae113c2b82c7cf62c28f847580273521e7998 216720 
libpinyin13-dev_2.1.0-1~exp1_amd64.deb
 

Bug#874068: marked as done (ABI breakage without shared library renaming)

[Debian Bug Tracking System]

Your message dated Mon, 11 Sep 2017 07:00:11 +
with message-id 
and subject line Bug#874068: fixed in ffcall 1.13-0.2
has caused the Debian Bug report #874068,
regarding ABI breakage without shared library renaming
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.)


-- 
874068: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874068
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libffcall1
Version: 1.13-0.1
Severity: serious
Control: affects -1 clisp libmlpcap-ocaml

Symbol __vacall_r has been dropped from libffcall1 in version 1.13-0.1 and,
contrary to my expectations, this symbol is used by reverse-dependencies
(clisp, libmlpcap-ocaml).

Upstream does not track ABI, so the right fix is to rename the shared library
package (and make it conflict with the old one).

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄  http://www.debian.org


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ffcall
Source-Version: 1.13-0.2

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

Debian distribution maintenance software
pp.
Sébastien Villemot  (supplier of updated ffcall package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 02 Sep 2017 23:43:43 +0200
Source: ffcall
Binary: libffcall1-dev libffcall1a
Architecture: source amd64
Version: 1.13-0.2
Distribution: unstable
Urgency: low
Maintainer: Christoph Egger 
Changed-By: Sébastien Villemot 
Description:
 libffcall1-dev - Foreign Function Call Libraries (development files)
 libffcall1a - Foreign Function Call Libraries
Closes: 874068
Changes:
 ffcall (1.13-0.2) unstable; urgency=low
 .
   * Non-maintainer upload.
   * Rename libffcall1 to libffcall1a because ABI was broken in 1.13-0.1.
 (Closes: #874068)
   * Update symbols file. This should fix FTBFS on hurd-i386, powerpcspe and
 sparc64.
Checksums-Sha1:
 0f5252854cedfdb32f2b4d2dd36c7290e4a963a0 1944 ffcall_1.13-0.2.dsc
 8e15744c7d0388dbddc3fb19fa87a8334a0cafd3 10668 ffcall_1.13-0.2.debian.tar.xz
 15be241c0dcdf9e1d1153bf9e6e2b118a17e90c5 5837 ffcall_1.13-0.2_amd64.buildinfo
 7c8c19fff212ce73c3c0e2a91446ab5306d2dfe0 70808 
libffcall1-dev_1.13-0.2_amd64.deb
 58b2f2dbc5aad2327718a4e1a37fc44f1fd9a9d0 11284 
libffcall1a-dbgsym_1.13-0.2_amd64.deb
 2d4feba14bb70aed3f0b5c4f2594451d45c6f2f3 40086 libffcall1a_1.13-0.2_amd64.deb
Checksums-Sha256:
 3ecfc85a26feaf0bd895a0946f931e95e21128c5f6f887e97bb2d58609fbfee2 1944 
ffcall_1.13-0.2.dsc
 edca3d2436a7b73def43eb6b2151bc8adef819298547ee39b9d4d47ba239c115 10668 
ffcall_1.13-0.2.debian.tar.xz
 dfd7ba90b8ebdea749f41568a6defc4b56512c33c3fd6823f2dd0ffb09dee431 5837 
ffcall_1.13-0.2_amd64.buildinfo
 db586a8ba046b134550be0b78b702dfaf08cb4b560c3e29242d7fc9805dda9cf 70808 
libffcall1-dev_1.13-0.2_amd64.deb
 7c604f772a02a83767c59a6c0faa8d9f608d70cf0caf920359156594b15f8b90 11284 
libffcall1a-dbgsym_1.13-0.2_amd64.deb
 56ba630d3820cb8cb20d2b05b5064938ca80d0dcc221d2b972fd970e56f3af05 40086 
libffcall1a_1.13-0.2_amd64.deb
Files:
 a9658542b31fc74e42a8277054aad3fb 1944 libdevel optional ffcall_1.13-0.2.dsc
 6e836c594cc377e8ae91c2ae3d9493bd 10668 libdevel optional 
ffcall_1.13-0.2.debian.tar.xz
 25a57b139d1d2b5dcb59ec10d1071370 5837 libdevel optional 
ffcall_1.13-0.2_amd64.buildinfo
 d25b79756b66546e0443176315de0114 70808 libdevel optional 
libffcall1-dev_1.13-0.2_amd64.deb
 0c7e576c7ba0a685afd848a890372d62 11284 debug extra 
libffcall1a-dbgsym_1.13-0.2_amd64.deb
 993d26802bc13a4afde017ddef50723c 40086 libs optional 
libffcall1a_1.13-0.2_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEU5UdlScuDFuCvoxKLOzpNQ7OvkoFAlmrof8ACgkQLOzpNQ7O
vkpcYxAAmlPcU+BKBMxkbLrwXn8zbQUjPBPMfXsN0WNrguLTdGF0qXW8/1oWOuyn
UhUZVB3QnGsFw7d+dj6y7H1Mz+com1z8xGGahdfqiXYlirLPlYGIZSR/POHww5wg
Q4YReIhJ7/IXKeWpBKKLlVZO2FNhHvL7QgxhdBTNDtFhPRk7Lfw1xsWgB+5g8u51

Bug#873874: marked as done (uim FTBFS with libanthy-dev 1:0.3-5)

[Debian Bug Tracking System]

Your message dated Mon, 11 Sep 2017 07:00:44 +
with message-id 
and subject line Bug#873874: fixed in uim 1:1.8.6+gh20161003.0.d63dadd-5~exp1
has caused the Debian Bug report #873874,
regarding uim FTBFS with libanthy-dev 1:0.3-5
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.)


-- 
873874: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873874
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: uim
Version: 1:1.8.6+gh20161003.0.d63dadd-4
Severity: serious
Tags: buster sid

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

...
checking anthy/anthy.h usability... yes
checking anthy/anthy.h presence... yes
checking for anthy/anthy.h... yes
checking for anthy_init in -lanthy... yes
checking for ANTHY_UTF8... no
...
   debian/rules override_dh_install
make[1]: Entering directory '/build/1st/uim-1.8.6+gh20161003.0.d63dadd'
install -d 
/build/1st/uim-1.8.6+gh20161003.0.d63dadd/debian/libuim-data/var/lib/uim
dh_install --sourcedir=debian/tmp
dh_install: Cannot find (any matches for) 
"usr/lib/*/uim/plugin/libuim-anthy-utf8.so" (tried in debian/tmp, debian/tmp)

dh_install: uim-anthy missing files: usr/lib/*/uim/plugin/libuim-anthy-utf8.so
dh_install: Cannot find (any matches for) 
"usr/share/uim/pixmaps/anthy-utf8.png" (tried in debian/tmp, debian/tmp)

dh_install: uim-anthy missing files: usr/share/uim/pixmaps/anthy-utf8.png
dh_install: missing files, aborting
debian/rules:68: recipe for target 'override_dh_install' failed
make[1]: *** [override_dh_install] Error 25
m
--- End Message ---
--- Begin Message ---
Source: uim
Source-Version: 1:1.8.6+gh20161003.0.d63dadd-5~exp1

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

Debian distribution maintenance software
pp.
HIGUCHI Daisuke (VDR dai)  (supplier of updated uim package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 03 Sep 2017 09:58:05 +0900
Source: uim
Binary: uim uim-plugins uim-data libuim8 libuim-scm0 libuim-custom2 libuim-dev 
uim-gtk2.0 uim-gtk2.0-immodule uim-gtk3 uim-gtk3-immodule uim-qt 
uim-qt-immodule uim-qt5 uim-qt5-immodule uim-xim uim-fep uim-anthy uim-skk 
uim-el uim-tcode
Architecture: source amd64 all
Version: 1:1.8.6+gh20161003.0.d63dadd-5~exp1
Distribution: experimental
Urgency: medium
Maintainer: HIGUCHI Daisuke (VDR dai) 
Changed-By: HIGUCHI Daisuke (VDR dai) 
Description:
 libuim-custom2 - Universal Input Method - uim-custom API library
 libuim-dev - Universal Input Method - development files
 libuim-scm0 - Universal Input Method - uim-scm API library
 libuim8- Universal Input Method - uim library
 uim- Universal Input Method - main binary package
 uim-anthy  - Universal Input Method - Anthy support metapackage
 uim-data   - Universal Input Method - data files
 uim-el - Universal Input Method - Emacs front end
 uim-fep- Universal Input Method - front end processor
 uim-gtk2.0 - Universal Input Method - GTK+2.x front end
 uim-gtk2.0-immodule - Universal Input Method - GTK+2.x IM-module
 uim-gtk3   - Universal Input Method - GTK+3.x front end
 uim-gtk3-immodule - Universal Input Method - GTK+3.x IM module
 uim-plugins - Universal Input Method - plugin files
 uim-qt - Universal Input Method - Qt 4.x front end
 uim-qt-immodule - Universal Input Method - Qt 4.x IM module
 uim-qt5- Universal Input Method - Qt 5.x front end
 uim-qt5-immodule - Universal Input Method - Qt 5.x IM module
 uim-skk- Universal Input Method - SKK support metapackage
 uim-tcode  - Universal Input Method - T-Code support metapackage
 uim-xim- Universal Input Method - XIM compatibility interface
Closes: 731672 863664 873123 873155 873739 873874
Changes:
 uim (1:1.8.6+gh20161003.0.d63dadd-5~exp1) experimental; urgency=medium
 .
   * upload to experimental due to drastic package arrangement.
 .
   [ HIGUCHI Daisuke (VDR dai) ]
 .
   * d/uim.{postinst,prerm}: register/unregister all supported modules.
 suggested by 

Bug#784475: marked as done ([kbibtex] Qt4's WebKit removal)

[Debian Bug Tracking System]

Your message dated Mon, 11 Sep 2017 07:00:21 +
with message-id 
and subject line Bug#784475: fixed in kbibtex 0.8~20170819git31a77b27e8e83836e-1
has caused the Debian Bug report #784475,
regarding [kbibtex] Qt4's WebKit removal
to be marked as done.

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

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


-- 
784475: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784475
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kbibtex
Version: 0.4-4
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4webkit-removal

Dear Debian Science Maintainers 
,

As you might know we the Qt/KDE team are preparing to remove Qt4's WebKit
as announced in [announce].

[announce] 


Basically we are about to get the latest Qt4 point release and upstream is
migrating from WebKit to Bing in the Qt5 series, so we won't have much upstream
support for maintaining Qt4's WebKit.

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

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

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4. In
order to ease the transition time we have provided Wheezy backports for Qt5.

Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html

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

Ana,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Source: kbibtex
Source-Version: 0.8~20170819git31a77b27e8e83836e-1

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

Debian distribution maintenance software
pp.
Bastien Roucariès  (supplier of updated kbibtex package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 28 Aug 2017 16:12:42 +0200
Source: kbibtex
Binary: kbibtex kbibtex-data
Architecture: source all amd64
Version: 0.8~20170819git31a77b27e8e83836e-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Bastien Roucariès 
Description:
 kbibtex- BibTeX editor for KDE
 kbibtex-data - BibTeX editor for KDE -- common data
Closes: 742974 784475
Changes:
 kbibtex (0.8~20170819git31a77b27e8e83836e-1) unstable; urgency=medium
 .
   * New upstream release
   * Bug fix: "new upstream release available", thanks to Gerrit Kruse
 (Closes: #742974).
   * Bug fix: "[kbibtex] Qt4s WebKit removal", thanks to Ana Guerrero
 Lopez (Closes: #784475).
Checksums-Sha1:
 8bc42442f139f88eb56049b1fc943b49ec15d7db 2739 
kbibtex_0.8~20170819git31a77b27e8e83836e-1.dsc
 666071a8351c653eea3440be355b213734345ace 7635908 
kbibtex_0.8~20170819git31a77b27e8e83836e.orig.tar.xz
 032d3ec37bdd9cfe0ad38a3c3d4013f25ee6e70c 16648 
kbibtex_0.8~20170819git31a77b27e8e83836e-1.debian.tar.xz
 a8a2135ca437690305aa40ef98bf58bf631d58b3 2579620 
kbibtex-data_0.8~20170819git31a77b27e8e83836e-1_all.deb
 32e368652e10cb00f46ca65f5ce27d2c9572832e 20930792 

Bug#875381: boinc-app-seti-graphics: depends on virtualbox-guest-x11 which is in contrib

[Andreas Beckmann]

Package: boinc-app-seti-graphics
Version: 8.00~svn3643-1~exp3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package is no longer
installable in experimental.

The dependency virtualbox-guest-x11 is only available in contrib,
therefore boinc-app-seti-graphics needs to be moved to contrib as well.


Cheers,

Andreas