Bug#873627: udisks2 in sid apparently left me with a borked system in plasma(?)

[Daniel Schaal]

I'm experiencing the same issue. I attached the log output and the 
backtrace of the coredump.


After installing the missing plugins (libblockdev-* packages) it 
complains about, I don't get this issue anymore.


syslog output:
-
Starting Disk Manager...
udisks daemon version 2.7.2 starting
failed to load module mdraid: libbd_mdraid.so.2: cannot open shared 
object file: No such file or directory

Cannot load the part plugin: The 'sgdisk' utility is not available
failed to load module fs: libbd_fs.so.2: cannot open shared object file: 
No such file or directory
Error initializing libblockdev library: Failed to load plugins 
(g-bd-init-error-quark, 0)
traps: udisksd[2390] trap int3 ip:7f77dd711921 sp:7ffce682cbd0 error:0 
in libglib-2.0.so.0.5306.0[7f77dd6c1000+111000]

Started Process Core Dump (PID 2395/UID 0).
udisks2.service: Main process exited, code=dumped, status=5/TRAP
Failed to start Disk Manager.
udisks2.service: Unit entered failed state.
udisks2.service: Failed with result 'core-dump'.
--

Backtrace:
-
#0  _g_log_abort (breakpoint=breakpoint@entry=1) at 
../../../../glib/gmessages.c:554
#1  0x7fd1ff261f41 in g_log_writer_default (log_level=6, 
log_level@entry=G_LOG_LEVEL_ERROR, fields=fields@entry=0x7ffc32a375a0, 
n_fields=n_fields@entry=3, user_data=user_data@entry=0x0)

at ../../../../glib/gmessages.c:2628
#2  0x7fd1ff2604be in g_log_structured_array 
(log_level=G_LOG_LEVEL_ERROR, fields=0x7ffc32a375a0, n_fields=3) at 
../../../../glib/gmessages.c:1941
#3  0x7fd1ff2607b7 in g_log_structured (log_domain=0x55ea532e0c08 
"udisks", log_level=G_LOG_LEVEL_ERROR) at ../../../../glib/gmessages.c:1768

#4  0x55ea532d8e9b in udisks_log ()
#5  0x55ea532ad74f in ?? ()
#6  0x7fd1ff538510 in g_object_new_internal 
(class=class@entry=0x55ea53e38c00, params=params@entry=0x7ffc32a38060, 
n_params=n_params@entry=4) at ../../../../gobject/gobject.c:1821
#7  0x7fd1ff53a4e0 in g_object_new_valist 
(object_type=94464918131104, first_property_name=, 
var_args=var_args@entry=0x7ffc32a381b0) at 
../../../../gobject/gobject.c:2104
#8  0x7fd1ff53a859 in g_object_new (object_type=, 
first_property_name=) at ../../../../gobject/gobject.c:1624

#9  0x55ea532add55 in udisks_daemon_new ()
#10 0x55ea532aceab in ?? ()
#11 0x7fd1ff83de74 in connection_get_cb (source_object=out>, res=0x55ea53e41030, user_data=0x55ea53e34e70) at 
../../../../gio/gdbusnameowning.c:487
#12 0x7fd1ff801fd3 in g_task_return_now (task=0x55ea53e41030) at 
../../../../gio/gtask.c:1145
#13 0x7fd1ff8029f6 in g_task_return (task=0x55ea53e41030, 
type=) at ../../../../gio/gtask.c:1203
#14 0x7fd1ff830b92 in bus_get_async_initable_cb 
(source_object=0x55ea53e42070, res=, 
user_data=0x55ea53e41030) at ../../../../gio/gdbusconnection.c:7302
#15 0x7fd1ff801fd3 in g_task_return_now (task=0x55ea53e41100) at 
../../../../gio/gtask.c:1145
#16 0x7fd1ff802009 in complete_in_idle_cb (task=0x55ea53e41100) at 
../../../../gio/gtask.c:1159
#17 0x7fd1ff259dd5 in g_main_dispatch (context=0x55ea53e34200) at 
../../../../glib/gmain.c:3148
#18 g_main_context_dispatch (context=context@entry=0x55ea53e34200) at 
../../../../glib/gmain.c:3813
#19 0x7fd1ff25a1a0 in g_main_context_iterate 
(context=0x55ea53e34200, block=block@entry=1, dispatch=dispatch@entry=1, 
self=) at ../../../../glib/gmain.c:3886
#20 0x7fd1ff25a4b2 in g_main_loop_run (loop=0x55ea53e341d0) at 
../../../../glib/gmain.c:4082

#21 0x55ea532acc21 in main ()
---

Thanks,
Daniel

Bug#873626: marked as done (pyx3 binary-all FTBFS: rm: cannot remove '/<>/debian/tmp/usr/lib/python*/*-packages/output': No such file or directory)

[Debian Bug Tracking System]

Your message dated Wed, 30 Aug 2017 04:50:02 +
with message-id 
and subject line Bug#873626: fixed in pyx3 0.14.1-7
has caused the Debian Bug report #873626,
regarding pyx3 binary-all FTBFS: rm: cannot remove 
'/<>/debian/tmp/usr/lib/python*/*-packages/output': No such file 
or directory
to be marked as done.

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

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


-- 
873626: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873626
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyx3
Version: 0.14.1-6
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=pyx3=all=0.14.1-6=1504014753=0

...
running install_egg_info
Writing 
/<>/debian/tmp/usr/lib/python3.5/dist-packages/PyX-0.14.1.egg-info
rm 
/<>/debian/tmp/usr/lib/python*/*-packages/pyx/data/lfs/createlfs.*
rm /<>/debian/tmp/usr/lib/python*/*-packages/output
rm: cannot remove 
'/<>/debian/tmp/usr/lib/python*/*-packages/output': No such file 
or directory
debian/rules:32: recipe for target 'override_dh_auto_install' failed
make[1]: *** [override_dh_auto_install] Error 1
--- End Message ---
--- Begin Message ---
Source: pyx3
Source-Version: 0.14.1-7

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 30 Aug 2017 09:16:09 +1000
Source: pyx3
Binary: python3-pyx python3-pyx-doc
Architecture: source
Version: 0.14.1-7
Distribution: unstable
Urgency: medium
Maintainer: Stuart Prescott 
Changed-By: Stuart Prescott 
Closes: 873626
Description: 
 python3-pyx-doc - Python 3 module for generating PostScript graphics 
(documentation
 python3-pyx - Python 3 module for generating PostScript graphics
Changes:
 pyx3 (0.14.1-7) unstable; urgency=medium
 .
   * Fix removal of 'output' file from build output (Closes: #873626).
Checksums-Sha1: 
 b89a5af9a425344af322cf2f38d0011f624eb5d5 2221 pyx3_0.14.1-7.dsc
 562b5c46ccbdb74c505bef9fe376da1ea41b3a7f 16904 pyx3_0.14.1-7.debian.tar.xz
Checksums-Sha256: 
 1fee29240009d6c1d16821917ef5382f6fd7edb18ed93ca7388aec510d56 2221 
pyx3_0.14.1-7.dsc
 8ca802c1cd4a698ee01a933e5c463013c5c2cce249618637ea187b2f2557a673 16904 
pyx3_0.14.1-7.debian.tar.xz
Files: 
 c258233157e8c08da52cff59811d090b 2221 python optional pyx3_0.14.1-7.dsc
 f3d7b7e6d6824a3903ba5013d8ecade2 16904 python optional 
pyx3_0.14.1-7.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkOLSwa0Uaht+u4kdu8F+uxOW8vcFAlml9zQACgkQu8F+uxOW
8vcf1RAArvL3zIfSD3Eg82IaRZtbSYC+b2oIFHTPeNFHGzPaqywyziM5B+YTtAp3
q/Q0Azm4tI5JgiDWlmwu/zBBd3AGQh7O4Dxd76HCL/mPITpyPkKD5UGj/sF/ipkg
Uron9S5E4Uf+P3yN+moVcXITyEiDBq+bMxkSyoRdMUw1Q2QIyGPPqI+4UlwyqdJ/
jfeSubo1aUrbiJOZvjHelt9hy5gBlnaozyEgQeKujxkbbvuHg25uTvAtsDoNcJMo
R2pzoEs/uXZOqRt/gYuasYDex6oFDxzWKnEikwCRyqBR5pdX8qKHzMUBoevNkiG7
q8csoAMIAzTyXa971Ac7gNlnTPRLqJ7bp4RMaquCv7kuPDSefGSK2mit1ZQ6SYH0
D8Iq+KOIJEIDb2bvFw0lJL3bU0DjjrR4hVAD7/0eLCbQonz0EpPek6eHrLEtqkcR
5w8jSzKPja0OoNX0lYlXNGE+SjLiYGe2XVlldgwYKAg2EggW3knROyGc0lRK34lv
eKyRUS5BlfRv+xUJZDbf5iSEEHtvk6W7HN5GWI0MpMzk05fNWBvwVC3+lLWVvL6K
HJ7BHt87ZpCw2TiCjH/pcDV3i/qt5Wk+nKYwiagkSBGoE+Xsuw4wwT6AcjBM5BDw
fAp5AJIrjj0fMi4pGiUslI1P/fG9J8eIeWJWcnIWF7Bir2lhWbQ=
=X0Lz
-END PGP SIGNATURE End Message ---

Bug#873679: dislocker: libdislocker* renamed without transition packages

[Giovani Augusto Ferreira]

Package: src:dislocker
Version: 0.7.1-1
Severity: serious

The libdislocker* packages were renamed without following
the guidelines at https://wiki.debian.org/RenamingPackages
and this will cause failures during upgrade.

This RC bug is to prevent migration to testing until the new
Debian revision exits the NEW queue and resolves this.

Best regards,

Giovani

Bug#873623: sudo: occasionally stalls infinitely instead of running command

[Bob Proulx]

Alban Browaeys wrote:
> This is likely sssd related.
> 
> I upgraded both today (sssd to 1.15.3-1) and "sudo ls" output was empty.
>
> Local workaround was to comment out "sss" on /etc/nsswitch.conf "sudoers:"
> sudoers:files sss
> to
> sudoers:files #sss

While sss might be involved additionally I reproduce the problem on my
system and I do not have sssd installed at all.  The sudo problem is
independent of sssd.  There is no sssd installed on my system which
also exhibits the sudo hang problem.

Bob

Bug#789927: marked as done (libanthyinput0: fails to upgrade from 'sid' - trying to overwrite /usr/lib/x86_64-linux-gnu/libanthyinput.so.0.0.0')

[Debian Bug Tracking System]

Your message dated Wed, 30 Aug 2017 02:51:10 +
with message-id 
and subject line Bug#789927: fixed in anthy 1:0.3-5
has caused the Debian Bug report #789927,
regarding libanthyinput0: fails to upgrade from 'sid' - trying to overwrite 
/usr/lib/x86_64-linux-gnu/libanthyinput.so.0.0.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.)


-- 
789927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789927
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libanthyinput0
Version: 1:0.3-1
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 libanthyinput0:amd64.
  Preparing to unpack .../libanthyinput0_1%3a0.3-1_amd64.deb ...
  Unpacking libanthyinput0:amd64 (1:0.3-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libanthyinput0_1%3a0.3-1_amd64.deb (--unpack):
   trying to overwrite '/usr/lib/x86_64-linux-gnu/libanthyinput.so.0.0.0', 
which is also in package libanthy0:amd64 9100h-25
  Preparing to unpack .../anthy_1%3a0.3-1_amd64.deb ...
  Unpacking anthy (1:0.3-1) over (9100h-25) ...
  dpkg: warning: unable to delete old directory '/var/lib/anthy': Directory not 
empty
  Errors were encountered while processing:
   /var/cache/apt/archives/libanthyinput0_1%3a0.3-1_amd64.deb


cheers,

Andreas


anthy_1:0.3-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: anthy
Source-Version: 1:0.3-5

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

Debian distribution maintenance software
pp.
NIIBE Yutaka  (supplier of updated anthy package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 30 Aug 2017 11:01:41 +0900
Source: anthy
Binary: anthy anthy-common anthy-el libanthy1 libanthy-dev libanthyinput0 
libanthyinput-dev
Architecture: source
Version: 1:0.3-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Anthy Team 
Changed-By: NIIBE Yutaka 
Description:
 anthy  - Japanese kana-kanji conversion - utilities
 anthy-common - Japanese kana-kanji conversion - dictionary
 anthy-el   - Japanese kana-kanji conversion - elisp frontend
 libanthy-dev - Japanese kana-kanji conversion - runtime library
 libanthy1  - Japanese kana-kanji conversion - runtime library
 libanthyinput-dev - Japanese kana-kanji conversion - runtime library for input
 libanthyinput0 - Japanese kana-kanji conversion - runtime library for input
Closes: 789927
Changes:
 anthy (1:0.3-5) unstable; urgency=medium
 .
   * debian/control (Breaks, Replaces): Fix version specification using <<,
 to support +b (Closes: #789927).
Checksums-Sha1:
 8b3f3488aaec95176f49e75ab224a17111a4818b 1996 anthy_0.3-5.dsc
 3da9348077ffbe51b0f7dee0b2e369d79a13a5de 12024 anthy_0.3-5.debian.tar.xz
 a037adf2ae489f6330f15d4969d922ef971da09a 7819 anthy_0.3-5_amd64.buildinfo
Checksums-Sha256:
 60b025be1e2877c0a1225f78f8a26e1b4de315d497214715adef8866d0423fe0 1996 
anthy_0.3-5.dsc
 c89c22c404fb3c6df7b5517b945eedd70c417cb9d441652ba6d4058b23c17765 12024 
anthy_0.3-5.debian.tar.xz
 b89afa66c05b70a8f652f5e6320412bb54fbc35c6d6904443cd2d928f0ec0e2e 7819 
anthy_0.3-5_amd64.buildinfo
Files:
 14c5a7d2d117d08cb07174da9bb280f3 1996 utils optional anthy_0.3-5.dsc
 9f65c088c4883f80f7231e2b2eeb6a7c 12024 utils optional anthy_0.3-5.debian.tar.xz
 029cdb1eeeda6d288cbe49c5dd961df0 7819 utils optional 
anthy_0.3-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEEkEkvTtIYq96CkLxALRevUynur4FAlmmHdUACgkQALRevUyn

Bug#873676: breezy: FTBFS: test_unicode_commit_message_is_filename fails in C locale

[Aaron M. Ucko]

Source: breezy
Version: 3.0.0~bzr6753-1
Severity: serious
Justification: fails to build from source

Builds of breezy under the traditional C locale (as on the
autobuilders, implicitly) have been failing as detailed below.  Please
try arranging for debian/rules to export LC_ALL=C.UTF-8, which should
be available by default (via libc-bin) these days.

Thanks!

==
ERROR: 
breezy.tests.blackbox.test_commit.TestCommit.test_unicode_commit_message_is_filename
--
Traceback (most recent call last):
testtools.testresult.real._StringException: log: {{{
19.942  run brz: ['init']
19.942  breezy version: 3.0.0dev1
19.943  brz arguments: [u'init']
19.960  creating repository in 
file:///tmp/testbzr-qu2rYD.tmp/breezy.tests.blackbox.test_commit.TestCommit.test_unicode_commit_message_is_filename/work/.bzr/.
19.965  creating branch  in 
file:///tmp/testbzr-qu2rYD.tmp/breezy.tests.blackbox.test_commit.TestCommit.test_unicode_commit_message_is_filename/work/
19.983  trying to create missing lock 
'/tmp/testbzr-qu2rYD.tmp/breezy.tests.blackbox.test_commit.TestCommit.test_unicode_commit_message_is_filename/work/.bzr/checkout/dirstate'
19.984  opening working tree 
'/tmp/testbzr-qu2rYD.tmp/breezy.tests.blackbox.test_commit.TestCommit.test_unicode_commit_message_is_filename/work'
20.000  opening working tree 
'/tmp/testbzr-qu2rYD.tmp/breezy.tests.blackbox.test_commit.TestCommit.test_unicode_commit_message_is_filename/work'
20.004  output:
'Created a standalone tree (format: 2a)\n'
20.005  run brz: ['add']
20.005  breezy version: 3.0.0dev1
20.005  brz arguments: [u'add']
20.015  opening working tree 
'/tmp/testbzr-qu2rYD.tmp/breezy.tests.blackbox.test_commit.TestCommit.test_unicode_commit_message_is_filename/work'
20.027  skip control directory '.bzr'
20.027  creating config directory: 
'/tmp/testbzr-qu2rYD.tmp/breezy.tests.blackbox.test_commit.TestCommit.test_unicode_commit_message_is_filename/home/breezy'
20.032  output:
'adding "?"\n'
20.032  run brz: ['commit', '-m', u'\u20ac']
20.032  breezy version: 3.0.0dev1
20.032  brz arguments: [u'commit', u'-m', u'\u20ac']
20.044  opening working tree 
'/tmp/testbzr-qu2rYD.tmp/breezy.tests.blackbox.test_commit.TestCommit.test_unicode_commit_message_is_filename/work'
}}}

Traceback (most recent call last):
  File 
"/<>/build/lib.linux-aarch64-2.7/breezy/tests/blackbox/test_commit.py",
 line 144, in test_unicode_commit_message_is_filename
out, err = self.run_bzr(['commit', '-m', file_name])
  File "/<>/build/lib.linux-aarch64-2.7/breezy/tests/__init__.py", 
line 2021, in run_bzr
working_dir=working_dir,
  File "/<>/build/lib.linux-aarch64-2.7/breezy/tests/__init__.py", 
line 1923, in _run_bzr_autosplit
encoding=encoding, stdin=stdin, working_dir=working_dir,
  File "/<>/build/lib.linux-aarch64-2.7/breezy/tests/__init__.py", 
line 1965, in _run_bzr_core
args)
  File "/<>/build/lib.linux-aarch64-2.7/breezy/tests/__init__.py", 
line 2301, in apply_redirected
return a_callable(*args, **kwargs)
  File "/<>/build/lib.linux-aarch64-2.7/breezy/commands.py", line 
1309, in run_bzr_catch_user_errors
return run_bzr(argv)
  File "/<>/build/lib.linux-aarch64-2.7/breezy/commands.py", line 
1199, in run_bzr
ret = run(*run_argv)
  File "/<>/build/lib.linux-aarch64-2.7/breezy/commands.py", line 
755, in run_argv_aliases
return self.run(**all_cmd_args)
  File "/<>/build/lib.linux-aarch64-2.7/breezy/commands.py", line 
779, in run
return self._operation.run_simple(*args, **kwargs)
  File "/<>/build/lib.linux-aarch64-2.7/breezy/cleanup.py", line 
136, in run_simple
self.cleanups, self.func, *args, **kwargs)
  File "/<>/build/lib.linux-aarch64-2.7/breezy/cleanup.py", line 
165, in _do_with_cleanups
result = func(*args, **kwargs)
  File "/<>/build/lib.linux-aarch64-2.7/breezy/builtins.py", line 
3616, in run
ui.ui_factory.show_warning(warning_msg)
  File "/<>/build/lib.linux-aarch64-2.7/breezy/ui/text.py", line 
343, in show_warning
self.stderr.write("bzr: warning: %s\n" % msg)
  File "/usr/lib/python2.7/codecs.py", line 369, in write
data, consumed = self.encode(object, self.errors)
UnicodeEncodeError: 'ascii' codec can't encode character u'\u20ac' in position 
50: ordinal not in range(128)

--
Ran 27984 tests in 608.241s

FAILED (errors=1, known_failure_count=64)

-- 
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#873675: libexecs: FTBFS w/GCC 7: null where non-null expected

[Aaron M. Ucko]

Source: libexecs
Version: 1.0-1
Severity: serious
Tags: upstream
Justification: fails to build from source

Builds of libexecs with GCC 7 (the default version nowadays) have been
failing:

  libtool: compile:  gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 
-Werror -Wall -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c noshell.c  -fPIC 
-DPIC -o .libs/noshell.o
  noshell.c: In function 'coprocess_common':
  noshell.c:82:7: error: argument 1 null where non-null expected 
[-Werror=nonnull]
 execvpe(path, argv, envp);
 ^
  In file included from noshell.c:5:0:
  /usr/include/unistd.h:593:12: note: in a call to function 'execvpe' declared 
here
   extern int execvpe (const char *__file, char *const __argv[],
  ^~~
  cc1: all warnings being treated as errors
  Makefile:512: recipe for target 'noshell.lo' failed

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#873674: libdazzle: FTBFS: 'ascii' codec can't decode byte 0xe2

[Aaron M. Ucko]

Source: libdazzle
Version: 3.25.5-1
Severity: serious
Justification: fails to build from source

Builds of libdazzle under the traditional C locale (as on the
autobuilders, implicitly) have been failing as detailed below.  Please
try arranging for debian/rules to export LC_ALL=C.UTF-8, which should
be available by default (via libc-bin) these days.

Thanks!

Building documentation for libdazzle
Traceback (most recent call last):
  File "/usr/share/meson/meson", line 37, in 
sys.exit(main())
  File "/usr/share/meson/meson", line 34, in main
return mesonmain.run(sys.argv[1:], launcher)
  File "/usr/share/meson/mesonbuild/mesonmain.py", line 297, in run
sys.exit(run_script_command(args[1:]))
  File "/usr/share/meson/mesonbuild/mesonmain.py", line 264, in 
run_script_command
return cmdfunc(cmdargs)
  File "/usr/share/meson/mesonbuild/scripts/gtkdochelper.py", line 218, in run
options.mode)
  File "/usr/share/meson/mesonbuild/scripts/gtkdochelper.py", line 166, in 
build_gtkdoc
gtkdoc_run_check(fixref_cmd, abs_out)
  File "/usr/share/meson/mesonbuild/scripts/gtkdochelper.py", line 51, in 
gtkdoc_run_check
p, out = Popen_safe(cmd, cwd=cwd, stderr=subprocess.STDOUT)[0:2]
  File "/usr/share/meson/mesonbuild/mesonlib.py", line 522, in Popen_safe
o, e = p.communicate(write)
  File "/usr/lib/python3.5/subprocess.py", line 790, in communicate
stdout = self.stdout.read()
  File "/usr/lib/python3.5/encodings/ascii.py", line 26, in decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 16994: 
ordinal not in range(128)
Warning: You are using 'ANSI_X3.4-1968' which is not a a Unicode-compatible 
locale.
You might see errors if you use UTF-8 strings as filenames, as strings, or as 
file contents.
Please switch to a UTF-8 locale for your platform.

-- 
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#873160: python-pymad: pymad in stretch decodes to noise

[Jamie Wilkinson]

Bug 873673 contains the request to the release team.

On 30 August 2017 at 10:01, Jamie Wilkinson  wrote:

> ... The version you filed the bug against is 0.10-1 but in the body of the
> text you say it's 0.9 yeah.  0.10 fixes a decode-to-noise bug. :)
>
> I'll see if the release team would like to promote 0.10-1 to stretch.
>
> On 25 August 2017 at 15:18, Marc Dahn  wrote:
>
>> Package: python-pymad
>> Version: 0.10-1
>> Severity: grave
>> Justification: renders package unusable
>>
>> Dear Maintainer,
>>
>> When decoding at least several MP3 files (including at 22050 kHz
>> single-channel and 44100 kHz dual-channel, non-VBR), python-pymad in
>> stretch generates fairly horrific sound (chr-chr-chr) at least on i386.
>> If one looks at the decoded bytes, there's a clear overabundance of
>> zeroes, but in the one case I looked at they even included a string .
>> "7/email/encoders.py", so it's probably not just an integer format
>> issue.
>>
>> The good news is:  The version currently in testing, 0.10-1, fixes
>> the problem, so it's probably not worth further investigating this
>> particular issue.  It *would* be good if the fix could somehow slip
>> into stable, though.
>>
>>
>> -- System Information:
>> Debian Release: 9.1
>>   APT prefers proposed-updates
>>   APT policy: (500, 'proposed-updates'), (500, 'stable')
>> Architecture: i386 (x86_64)
>>
>> Kernel: Linux 4.12.2 (SMP w/4 CPU cores)
>> Locale: LANG=C, LC_CTYPE=de_DE.ISO-8859-1 (charmap=ISO-8859-1),
>> LANGUAGE=C (charmap=ISO-8859-1)
>> Shell: /bin/sh linked to /bin/bash
>> Init: sysvinit (via /sbin/init)
>>
>> Versions of packages python-pymad depends on:
>> ii  libc62.24-11+deb9u1
>> ii  libmad0  0.15.1b-8
>> ii  python   2.7.13-2
>>
>> python-pymad recommends no packages.
>>
>> python-pymad suggests no packages.
>>
>> -- no debconf information
>>
>
>

Processed: block 873160 with 873673

[Debian Bug Tracking System]

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

> block 873160 with 873673
Bug #873160 [python-pymad] python-pymad: pymad in stretch decodes to noise
873160 was not blocked by any bugs.
873160 was not blocking any bugs.
Added blocking bug(s) of 873160: 873673
> thanks
Stopping processing here.

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

Processed: notfound 873160 in 0.10-1, found 873160 in 0.9-1

[Debian Bug Tracking System]

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

> notfound 873160 0.10-1
Bug #873160 [python-pymad] python-pymad: pymad in stretch decodes to noise
Ignoring request to alter found versions of bug #873160 to the same values 
previously set
> found 873160 0.9-1
Bug #873160 [python-pymad] python-pymad: pymad in stretch decodes to noise
Ignoring request to alter found versions of bug #873160 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#873576: ruby-rest-client: FTBFS without network access

[Steve Langasek]

Package: ruby-rest-client
Followup-For: Bug #873576

Control: user ubuntu-de...@lists.ubuntu.com
Control: usertags -1 origin-ubuntu artful ubuntu-patch
Control: tags -1 patch

It appears there is already a patch applied to disable network tests, and it
just needs extending with the set of newly-added network-dependent tests. 
Please find attached a debdiff to do this.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru ruby-rest-client-2.0.2/debian/patches/disable-network-tests.patch 
ruby-rest-client-2.0.2/debian/patches/disable-network-tests.patch
--- ruby-rest-client-2.0.2/debian/patches/disable-network-tests.patch   
2017-07-25 23:24:23.0 -0700
+++ ruby-rest-client-2.0.2/debian/patches/disable-network-tests.patch   
2017-08-29 17:14:19.0 -0700
@@ -1,11 +1,15 @@
 From: Matthias Klose 
-Last-Update: 2016-03-16
+From: Steve Langasek 
+Last-Update: 2017-08-29
 Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818459
+Bug-Debian: https://bugs.debian.org/873576
 Forwarded: no
 
 a/spec/integration/request_spec.rb
-+++ b/spec/integration/request_spec.rb
-@@ -10,96 +10,7 @@ describe RestClient::Request do
+Index: ruby-rest-client-2.0.2/spec/integration/request_spec.rb
+===
+--- ruby-rest-client-2.0.2.orig/spec/integration/request_spec.rb
 ruby-rest-client-2.0.2/spec/integration/request_spec.rb
+@@ -10,96 +10,7 @@
end
  
describe "ssl verification" do
@@ -103,3 +107,73 @@
end
  
describe "timeouts" do
+@@ -113,15 +24,6 @@
+ raise_error(RestClient::Exceptions::OpenTimeout))
+ end
+ 
+-it "raises ReadTimeout when it hits a read timeout via :read_timeout" do
+-  request = RestClient::Request.new(
+-:method => :get,
+-:url => 'https://www.mozilla.org',
+-:read_timeout => 1e-10,
+-  )
+-  expect { request.execute }.to(
+-raise_error(RestClient::Exceptions::ReadTimeout))
+-end
+   end
+ 
+ end
+Index: ruby-rest-client-2.0.2/spec/integration/httpbin_spec.rb
+===
+--- ruby-rest-client-2.0.2.orig/spec/integration/httpbin_spec.rb
 ruby-rest-client-2.0.2/spec/integration/httpbin_spec.rb
+@@ -40,48 +40,6 @@
+   end
+ 
+   describe '.execute' do
+-it 'sends a user agent' do
+-  data = execute_httpbin_json('user-agent', method: :get)
+-  expect(data['user-agent']).to match(/rest-client/)
+-end
+-
+-it 'receives cookies on 302' do
+-  expect {
+-execute_httpbin('cookies/set?foo=bar', method: :get, max_redirects: 0)
+-  }.to raise_error(RestClient::Found) { |ex|
+-expect(ex.http_code).to eq 302
+-expect(ex.response.cookies['foo']).to eq 'bar'
+-  }
+-end
+-
+-it 'passes along cookies through 302' do
+-  data = execute_httpbin_json('cookies/set?foo=bar', method: :get)
+-  expect(data).to have_key('cookies')
+-  expect(data['cookies']['foo']).to eq 'bar'
+-end
+-
+-it 'handles quote wrapped cookies' do
+-  expect {
+-execute_httpbin('cookies/set?foo=' + CGI.escape('"bar:baz"'),
+-method: :get, max_redirects: 0)
+-  }.to raise_error(RestClient::Found) { |ex|
+-expect(ex.http_code).to eq 302
+-expect(ex.response.cookies['foo']).to eq '"bar:baz"'
+-  }
+-end
+-
+-it 'sends basic auth' do
+-  user = 'user'
+-  pass = 'pass'
+-
+-  data = execute_httpbin_json("basic-auth/#{user}/#{pass}", method: :get, 
user: user, password: pass)
+-  expect(data).to eq({'authenticated' => true, 'user' => user})
+-
+-  expect {
+-execute_httpbin_json("basic-auth/#{user}/#{pass}", method: :get, 
user: user, password: 'badpass')
+-  }.to raise_error(RestClient::Unauthorized) { |ex|
+-expect(ex.http_code).to eq 401
+-  }
+-end
++# all removed; accessing the network
+   end
+ end

Bug#873160: python-pymad: pymad in stretch decodes to noise

[Jamie Wilkinson]

... The version you filed the bug against is 0.10-1 but in the body of the
text you say it's 0.9 yeah.  0.10 fixes a decode-to-noise bug. :)

I'll see if the release team would like to promote 0.10-1 to stretch.

On 25 August 2017 at 15:18, Marc Dahn  wrote:

> Package: python-pymad
> Version: 0.10-1
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
> When decoding at least several MP3 files (including at 22050 kHz
> single-channel and 44100 kHz dual-channel, non-VBR), python-pymad in
> stretch generates fairly horrific sound (chr-chr-chr) at least on i386.
> If one looks at the decoded bytes, there's a clear overabundance of
> zeroes, but in the one case I looked at they even included a string .
> "7/email/encoders.py", so it's probably not just an integer format
> issue.
>
> The good news is:  The version currently in testing, 0.10-1, fixes
> the problem, so it's probably not worth further investigating this
> particular issue.  It *would* be good if the fix could somehow slip
> into stable, though.
>
>
> -- System Information:
> Debian Release: 9.1
>   APT prefers proposed-updates
>   APT policy: (500, 'proposed-updates'), (500, 'stable')
> Architecture: i386 (x86_64)
>
> Kernel: Linux 4.12.2 (SMP w/4 CPU cores)
> Locale: LANG=C, LC_CTYPE=de_DE.ISO-8859-1 (charmap=ISO-8859-1), LANGUAGE=C
> (charmap=ISO-8859-1)
> Shell: /bin/sh linked to /bin/bash
> Init: sysvinit (via /sbin/init)
>
> Versions of packages python-pymad depends on:
> ii  libc62.24-11+deb9u1
> ii  libmad0  0.15.1b-8
> ii  python   2.7.13-2
>
> python-pymad recommends no packages.
>
> python-pymad suggests no packages.
>
> -- no debconf information
>

Bug#873623: sudo: occasionally stalls infinitely instead of running command

[Alban Browaeys]

Package: sudo
Version: 1.8.21-1
Followup-For: Bug #873623

This is likely sssd related.

I upgraded both today (sssd to 1.15.3-1) and "sudo ls" output was empty.
Local workaround was to comment out "sss" on /etc/nsswitch.conf "sudoers:"
sudoers:files sss
to
sudoers:files #sss

Hinted from "pkexec strace -f sudo ls" output:
connect(4, {sa_family=AF_UNIX, sun_path="/var/lib/sss/pipes/sudo"}, 110) = -1 
ECONNREFUSED (Connection refused)


Best regards,
Alban



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

Kernel: Linux 4.11.0-2-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)

Versions of packages sudo depends on:
ii  libaudit1   1:2.7.7-1+b2
ii  libc6   2.24-17
ii  libpam-modules  1.1.8-3.6
ii  libpam0g1.1.8-3.6
ii  libselinux1 2.6-3+b2
ii  lsb-base9.20170808

sudo recommends no packages.

sudo suggests no packages.

-- Configuration Files:
/etc/sudoers [Errno 13] Permission non accordée: '/etc/sudoers'
/etc/sudoers.d/README [Errno 13] Permission non accordée: 
'/etc/sudoers.d/README'

-- no debconf information

Bug#873627: udisks2 in sid apparently left me with a borked system in plasma(?)

[Ben Caradoc-Davies]

udisks2 2.7.2-1 also severely impacted the functionality of thunar on 
sid. All filesystems were shown in the sidebar, including things like 
binfmt (about 20-30 or so filsystems). Removable devices were not shown, 
and no eject icon was shown when removable devices were mounted at the 
command line. Workaround was to downgrade to 2.6.5-2. Before filing a 
separate bug report, I will see if the fix for this issue resolves the 
thunar issues.


Downgrade and hold procedure for the benefit of other readers:

I added the following to /etc/apt/source.list:
deb http://snapshot.debian.org/archive/debian/20170827T034402Z/ sid main

Then ran the following to downgrade and hold:

apt-get update
apt-get install udisks2=2.6.5-2 libudisks2-0=2.6.5-2
apt-mark hold udisks2 libudisks2-0

A system restart was required.

Kind regards,

--
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

Bug#873079: marked as done (unattended-upgrades FTBFS: test failures)

[Debian Bug Tracking System]

Your message dated Tue, 29 Aug 2017 23:29:25 +
with message-id 
and subject line Bug#873079: fixed in unattended-upgrades 0.96
has caused the Debian Bug report #873079,
regarding unattended-upgrades FTBFS: test failures
to be marked as done.

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

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


-- 
873079: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873079
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: unattended-upgrades
Version: 0.95
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=unattended-upgrades=all=0.95=1503510785=0

...
Running ./test_remove_unused.py with python3
/<>/test/unattended_upgrade.py:1254: ResourceWarning: unclosed 
file <_io.TextIOWrapper name=7 mode='r' encoding='ANSI_X3.4-1968'>
  res, error = cache_commit(cache, logfile_dpkg, verbose)
/<>/test/unattended_upgrade.py:1254: ResourceWarning: unclosed 
file <_io.TextIOWrapper name=8 mode='w' encoding='ANSI_X3.4-1968'>
  res, error = cache_commit(cache, logfile_dpkg, verbose)
FF
==
FAIL: test_remove_unused_dependencies (__main__.TestRemoveUnused)
--
Traceback (most recent call last):
  File "./test_remove_unused.py", line 105, in test_remove_unused_dependencies
"Can not find '%s' in '%s'" % (needle, haystack))
AssertionError: False is not true : Can not find 'Packages that are auto 
removed: 'old-unused-dependency test-package-dependency'' in '2017-08-23 
17:53:00,093 INFO Initial blacklisted packages: 
2017-08-23 17:53:00,094 INFO Initial whitelisted packages: 
2017-08-23 17:53:00,094 INFO Starting unattended upgrades script
2017-08-23 17:53:00,094 INFO Allowed origins are: ['o=Ubuntu,a=lucid-security']
2017-08-23 17:53:00,149 INFO Packages that will be upgraded: 
2017-08-23 17:53:00,171 INFO Packages that are auto removed: 
'old-unused-dependency'
2017-08-23 17:53:00,470 INFO Packages were successfully auto-removed
'

==
FAIL: test_remove_unused_dependencies_new_unused_only 
(__main__.TestRemoveUnused)
--
Traceback (most recent call last):
  File "./test_remove_unused.py", line 127, in 
test_remove_unused_dependencies_new_unused_only
"Can not find '%s' in '%s'" % (needle, haystack))
AssertionError: False is not true : Can not find 'Packages that are auto 
removed: 'test-package-dependency'' in '2017-08-23 17:53:00,481 INFO Initial 
blacklisted packages: 
2017-08-23 17:53:00,481 INFO Initial whitelisted packages: 
2017-08-23 17:53:00,481 INFO Starting unattended upgrades script
2017-08-23 17:53:00,481 INFO Allowed origins are: ['o=Ubuntu,a=lucid-security']
2017-08-23 17:53:00,504 INFO No packages found that can be upgraded unattended 
and no pending auto-removals
'

--
Ran 2 tests in 0.422s

FAILED (failures=2)
Makefile:6: recipe for target 'check' failed
make[2]: *** [check] Error 1
make[2]: Leaving directory '/<>/test'
debian/rules:15: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 2
--- End Message ---
--- Begin Message ---
Source: unattended-upgrades
Source-Version: 0.96

We believe that the bug you reported is fixed in the latest version of
unattended-upgrades, 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.
Balint Reczey  (supplier of updated unattended-upgrades 
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 18:54:04 +0200
Source: unattended-upgrades
Binary: unattended-upgrades
Architecture: source
Version: 0.96
Distribution: unstable
Urgency: medium
Maintainer: Michael Vogt 
Changed-By: Balint Reczey 
Description:
 unattended-upgrades - automatic installation of security upgrades
Closes: 873079
Changes:
 unattended-upgrades (0.96) unstable; urgency=medium
 .
   

Bug#867414: marked as done (python3-pymongo-ext: missing python3 dependency)

[Debian Bug Tracking System]

Your message dated Tue, 29 Aug 2017 23:27:49 +
with message-id 
and subject line Bug#867414: fixed in pymongo 3.5.1+dfsg1-1
has caused the Debian Bug report #867414,
regarding python3-pymongo-ext: missing python3 dependency
to be marked as done.

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

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


-- 
867414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867414
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-pymongo-ext
Version: 2.7.2-1
Severity: serious
Tags: patch

Due to a cut'n'paste error the python3 dependency is missing.

Fix:

--- debian/control.old  2017-07-06 14:19:30.0 +
+++ debian/control  2017-07-06 14:20:02.0 +
@@ -60,7 +60,7 @@
 Package: python3-pymongo-ext
 Architecture: any-amd64 any-armel any-armhf any-i386 any-ia64 any-mipsel 
any-ppc64el
 Depends: ${misc:Depends}
- , ${python:Depends}
+ , ${python3:Depends}
  , ${shlibs:Depends}
  , python3-bson (= ${binary:Version})
  , python3-pymongo (= ${binary:Version})
--- End Message ---
--- Begin Message ---
Source: pymongo
Source-Version: 3.5.1+dfsg1-1

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

Debian distribution maintenance software
pp.
Federico Ceratto  (supplier of updated pymongo 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 23:32:51 +0100
Source: pymongo
Binary: python-pymongo python3-pymongo python-pymongo-ext python3-pymongo-ext 
python-pymongo-doc python-gridfs python3-gridfs python-bson python3-bson 
python-bson-ext python3-bson-ext
Architecture: source amd64 all
Version: 3.5.1+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Federico Ceratto 
Changed-By: Federico Ceratto 
Description:
 python-bson - Python implementation of BSON for MongoDB
 python-bson-ext - C-coded extension to the python-bson package
 python-gridfs - Python implementation of GridFS for MongoDB
 python-pymongo - Python interface to the MongoDB document-oriented database
 python-pymongo-doc - Python interface to the MongoDB document-oriented 
database (docum
 python-pymongo-ext - C-coded extension to the python-pymongo package
 python3-bson - Python3 implementation of BSON for MongoDB
 python3-bson-ext - C-coded extension to the python3-bson package
 python3-gridfs - Python3 implementation of GridFS for MongoDB
 python3-pymongo - Python3 interface to the MongoDB document-oriented database
 python3-pymongo-ext - C-coded extension to the python3-pymongo package
Closes: 849733 867414
Changes:
 pymongo (3.5.1+dfsg1-1) unstable; urgency=medium
 .
   * New upstream release
   * Removed Janos Guljas from Uploaders (Closes: #849733)
   * Fix python3-pymongo-ext dependency (Closes: #867414)
Checksums-Sha1:
 44f13c37b4ededc9f0f09bae9bbfa09718b685a7 2925 pymongo_3.5.1+dfsg1-1.dsc
 7697a4ff1783423de1d6191a73b22f62cf94d86b 554714 pymongo_3.5.1+dfsg1.orig.tar.gz
 599338c80745082eec882d90751ad751493d12eb 5468 
pymongo_3.5.1+dfsg1-1.debian.tar.xz
 4dd493525223e49820827120c6925d205e54f7e0 11755 
pymongo_3.5.1+dfsg1-1_amd64.buildinfo
 5330f24546173dea95c3986df6cbce6c0715bdb8 53366 
python-bson-ext-dbgsym_3.5.1+dfsg1-1_amd64.deb
 05b1e1f704960d6ddd32dbb876a5c35ac724f1f2 46070 
python-bson-ext_3.5.1+dfsg1-1_amd64.deb
 f3a1aed16df140941c313d27ba0bfd3f1690f43d 56410 
python-bson_3.5.1+dfsg1-1_amd64.deb
 cbcca69fe134399006220b5b4c2b36e4325e0bc5 39344 
python-gridfs_3.5.1+dfsg1-1_all.deb
 c261c4fad3a24a5ca107d39bbeeea62a1d280a61 295160 
python-pymongo-doc_3.5.1+dfsg1-1_all.deb
 2a367016d078c961483cb1f3ce1881463adebbab 25906 
python-pymongo-ext-dbgsym_3.5.1+dfsg1-1_amd64.deb
 3a8b0f350fa7a360dc4f26665f59a766c27f84e4 36568 
python-pymongo-ext_3.5.1+dfsg1-1_amd64.deb
 6a6dd81cae371d34816306d150d48f03b8ef33e0 143712 
python-pymongo_3.5.1+dfsg1-1_amd64.deb
 4efb135f2f105e77c46f5225fa071b86677a85f8 111656 
python3-bson-ext-dbgsym_3.5.1+dfsg1-1_amd64.deb
 b2df3586ff621c93db7fd6dbd6415f3657ebd37a 46298 

Bug#853317: marked as done (apvlv: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Tue, 29 Aug 2017 23:19:47 +
with message-id 
and subject line Bug#853317: fixed in apvlv 0.1.5+dfsg-3
has caused the Debian Bug report #853317,
regarding apvlv: 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.)


-- 
853317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853317
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:apvlv
Version: 0.1.5+dfsg-1
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/apvlv_0.1.5+dfsg-1_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

[...]
  ^~~~
/<>/apvlv-0.1.5+dfsg/src/ApvlvView.cc:75:36: warning: 'gint 
gdk_screen_get_width(GdkScreen*)' is deprecated [-Wdeprecated-declarations]
  mWidth = gdk_screen_get_width (scr);
^
In file included from /usr/include/gtk-3.0/gdk/gdkapplaunchcontext.h:31:0,
 from /usr/include/gtk-3.0/gdk/gdk.h:32,
 from /usr/include/gtk-3.0/gtk/gtk.h:30,
 from /<>/apvlv-0.1.5+dfsg/src/ApvlvUtil.h:32,
 from /<>/apvlv-0.1.5+dfsg/src/ApvlvParams.h:32,
 from /<>/apvlv-0.1.5+dfsg/src/ApvlvView.cc:29:
/usr/include/gtk-3.0/gdk/gdkscreen.h:58:14: note: declared here
 gint gdk_screen_get_width (GdkScreen   *screen);
  ^~~~
/<>/apvlv-0.1.5+dfsg/src/ApvlvView.cc:76:12: warning: 'gint 
gdk_screen_get_height(GdkScreen*)' is deprecated [-Wdeprecated-declarations]
  mHeight = gdk_screen_get_height (scr);
^
In file included from /usr/include/gtk-3.0/gdk/gdkapplaunchcontext.h:31:0,
 from /usr/include/gtk-3.0/gdk/gdk.h:32,
 from /usr/include/gtk-3.0/gtk/gtk.h:30,
 from /<>/apvlv-0.1.5+dfsg/src/ApvlvUtil.h:32,
 from /<>/apvlv-0.1.5+dfsg/src/ApvlvParams.h:32,
 from /<>/apvlv-0.1.5+dfsg/src/ApvlvView.cc:29:
/usr/include/gtk-3.0/gdk/gdkscreen.h:60:14: note: declared here
 gint gdk_screen_get_height(GdkScreen   *screen);
  ^
/<>/apvlv-0.1.5+dfsg/src/ApvlvView.cc:76:38: warning: 'gint 
gdk_screen_get_height(GdkScreen*)' is deprecated [-Wdeprecated-declarations]
  mHeight = gdk_screen_get_height (scr);
  ^
In file included from /usr/include/gtk-3.0/gdk/gdkapplaunchcontext.h:31:0,
 from /usr/include/gtk-3.0/gdk/gdk.h:32,
 from /usr/include/gtk-3.0/gtk/gtk.h:30,
 from /<>/apvlv-0.1.5+dfsg/src/ApvlvUtil.h:32,
 from /<>/apvlv-0.1.5+dfsg/src/ApvlvParams.h:32,
 from /<>/apvlv-0.1.5+dfsg/src/ApvlvView.cc:29:
/usr/include/gtk-3.0/gdk/gdkscreen.h:60:14: note: declared here
 gint gdk_screen_get_height(GdkScreen   *screen);
  ^
src/CMakeFiles/apvlv.dir/build.make:65: recipe for target 
'src/CMakeFiles/apvlv.dir/ApvlvCmds.cc.o' failed
make[3]: *** [src/CMakeFiles/apvlv.dir/ApvlvCmds.cc.o] Error 1
make[3]: Leaving directory '/<>/apvlv-0.1.5+dfsg/obj-x86_64-linux-gnu'
CMakeFiles/Makefile2:88: recipe for target 'src/CMakeFiles/apvlv.dir/all' failed
make[2]: *** [src/CMakeFiles/apvlv.dir/all] Error 2
make[2]: Leaving directory '/<>/apvlv-0.1.5+dfsg/obj-x86_64-linux-gnu'
Makefile:152: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving 

Bug#873505: Acknowledgement (mailman: Runner crashes when processing incoming email)

[Pete Donnell]

Apologies, turns out that this is a duplicate of 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838288


Applying the patch included there fixed it.

Bug#873557: mbedtls: possible authentication bypass

[James Cowgill]

On 29/08/17 00:09, James Cowgill wrote:
> I think this is the commit which fixes this, but I have not checked yet:
> https://github.com/ARMmbed/mbedtls/commit/31458a18788b0cf0b722acda9bb2f2fe13a3fb32

In addition, this commit must be applied before that one:
https://github.com/ARMmbed/mbedtls/commit/d15795acd5074e0b44e71f7ede8bdfe1b48591fc

I created a test certificate chain for this (before I realized upstream
already had one) which I have attached. The bug can be reproduced using
mbedtls's test programs (available from manually built source).

First, start a server:
programs/ssl/ssl_server2 crt_file=test-certs/chain.pem 
key_file=test-certs/child.key

Then run the child like this:
programs/ssl/ssl_client2 server_name=Child server_addr=localhost 
auth_mode=optional

Currently, the client will claim that the certificate validated. This is
quite astounding since I didn't even give the client a list of trusted
CAs!
> . Verifying peer X.509 certificate... ok

After applying the patches the client will correctly fail the
certificate validation.

James


test-certs.tar.gz
Description: application/gzip


signature.asc
Description: OpenPGP digital signature

Processed: This is a regression in the sid version

[Debian Bug Tracking System]

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

> notfound 873627 2.6.5-2
Bug #873627 [udisks2] udisks2 in sid apparently left me with a borked system in 
plasma(?)
Bug #873634 [udisks2] missing module files libbd_*.so
No longer marked as found in versions udisks2/2.6.5-2.
No longer marked as found in versions udisks2/2.6.5-2.
> thanks
Stopping processing here.

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

Bug#871385: marked as done (python-scrapy-djangoitem: FTBFS: build-dependency not installable: python3-scrapy)

[Debian Bug Tracking System]

Your message dated Tue, 29 Aug 2017 22:08:34 +
with message-id 
and subject line Bug#871385: fixed in python-scrapy 1.4.0-1
has caused the Debian Bug report #871385,
regarding python-scrapy-djangoitem: FTBFS: build-dependency not installable: 
python3-scrapy
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.)


-- 
871385: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871385
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-scrapy-djangoitem
Version: 1.1.1-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170807 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):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), dh-python, python-all, python-django, 
> python-scrapy, python-setuptools, python-six, python3-all, python3-django, 
> python3-scrapy, python3-setuptools, python3-six
> Filtered Build-Depends: debhelper (>= 9), dh-python, python-all, 
> python-django, python-scrapy, python-setuptools, python-six, python3-all, 
> python3-django, python3-scrapy, python3-setuptools, python3-six
> dpkg-deb: building package 
> 'sbuild-build-depends-python-scrapy-djangoitem-dummy' in 
> '/<>/resolver-NzGLi2/apt_archive/sbuild-build-depends-python-scrapy-djangoitem-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy 
> sbuild-build-depends-python-scrapy-djangoitem-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-NzGLi2/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-NzGLi2/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-NzGLi2/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-NzGLi2/apt_archive ./ Sources [548 B]
> Get:5 copy:/<>/resolver-NzGLi2/apt_archive ./ Packages [630 B]
> Fetched 2141 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install python-scrapy-djangoitem build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-python-scrapy-djangoitem-dummy : Depends: 
> python3-scrapy but it is not installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   
http://aws-logs.debian.net/2017/08/07/python-scrapy-djangoitem_1.1.1-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: python-scrapy
Source-Version: 1.4.0-1

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

Debian distribution maintenance software
pp.
Michael Fladischer  (supplier of updated python-scrapy 
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: Tue, 29 Aug 2017 22:06:51 

Bug#871160: marked as done (python-biomaj3: FTBFS: UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 1781: ordinal not in range(128))

[Debian Bug Tracking System]

Your message dated Tue, 29 Aug 2017 22:07:57 +
with message-id 
and subject line Bug#871160: fixed in python-biomaj3 3.0.20-2
has caused the Debian Bug report #871160,
regarding python-biomaj3: FTBFS: UnicodeDecodeError: 'ascii' codec can't decode 
byte 0xe2 in position 1781: ordinal not in range(128)
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.)


-- 
871160: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871160
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-biomaj3
Version: 3.0.20-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 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):
>  fakeroot debian/rules clean
> dh clean --with python2,python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:184: python2.7 setup.py clean 
> running clean
> removing '/<>/.pybuild/pythonX.Y_2.7/build' (and everything 
> under it)
> 'build/bdist.linux-amd64' does not exist -- can't clean it
> 'build/scripts-2.7' does not exist -- can't clean it
> I: pybuild base:184: python3.6 setup.py clean 
> Traceback (most recent call last):
>   File "setup.py", line 18, in 
> README = f.read()
>   File "/usr/lib/python3.6/encodings/ascii.py", line 26, in decode
> return codecs.ascii_decode(input, self.errors)[0]
> UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 1781: 
> ordinal not in range(128)
> E: pybuild pybuild:283: clean: plugin distutils failed with: exit code=1: 
> python3.6 setup.py clean 
> dh_auto_clean: pybuild --clean --test-nose -i python{version} -p "3.6 3.5" 
> returned exit code 13
> debian/rules:28: recipe for target 'clean' failed
> make: *** [clean] Error 25

The full build log is available from:
   http://aws-logs.debian.net/2017/08/05/python-biomaj3_3.0.20-1_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: python-biomaj3
Source-Version: 3.0.20-2

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated python-biomaj3 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: Tue, 29 Aug 2017 22:49:03 +0200
Source: python-biomaj3
Binary: python-biomaj3 python3-biomaj3 biomaj3-commons
Architecture: source all
Version: 3.0.20-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 biomaj3-commons - biological data-bank updater
 python-biomaj3 - biological data-bank updater (Python 2)
 python3-biomaj3 - biological data-bank updater (Python 3)
Closes: 866547 866548 871160
Changes:
 python-biomaj3 (3.0.20-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Andreas Tille ]
   * Fix python3 encoding
 Closes: #866547, #871160
   * debhelper 10
   * Standards-Version: 4.1.0 (no changes needed)
   * Add missing debhelper token in postrm
   * cme fix dpkg-control (to fix overlong lines in description)
 .
   [ Scott Kitterman ]
   * Prune unneeded -dev build-depends
 Closes: #866548
Checksums-Sha1:
 086b94a9ecbae8255371fd64384136e7558bd096 2530 python-biomaj3_3.0.20-2.dsc
 52142ad702bc68553bd25b3f7602b5ffc2d90cc9 16056 
python-biomaj3_3.0.20-2.debian.tar.xz
 7113df47509a34ec42b23c166ca9050661944533 17466 biomaj3-commons_3.0.20-2_all.deb
 da6f64ac90beeb19a419b9a5ab9573b3b6fc5cef 62386 python-biomaj3_3.0.20-2_all.deb
 55e0cb4d4165d616943377386bd2873b984f85e2 8592 

Bug#871061: marked as done (opengrm-ngram: FTBFS: replace.h:1198:57: error: expected ';' before '::' token)

[Debian Bug Tracking System]

Your message dated Tue, 29 Aug 2017 22:05:21 +
with message-id 
and subject line Bug#871061: fixed in opengrm-ngram 1.3.2-1
has caused the Debian Bug report #871061,
regarding opengrm-ngram: FTBFS: replace.h:1198:57: error: expected ';' before 
'::' token
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.)


-- 
871061: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871061
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: opengrm-ngram
Version: 1.3.0-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 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):
> /bin/bash ../../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H   
> -I./../include -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -std=c++11 -c -o hist-arc.lo hist-arc.cc
> libtool: compile:  g++ -DHAVE_CONFIG_H -I./../include -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -std=c++11 -c 
> ngram-absolute.cc  -fPIC -DPIC -o .libs/ngram-absolute.o
> libtool: compile:  g++ -DHAVE_CONFIG_H -I./../include -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -std=c++11 -c 
> ngram-output.cc  -fPIC -DPIC -o .libs/ngram-output.o
> libtool: compile:  g++ -DHAVE_CONFIG_H -I./../include -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -std=c++11 -c 
> ngram-count-prune.cc  -fPIC -DPIC -o .libs/ngram-count-prune.o
> libtool: compile:  g++ -DHAVE_CONFIG_H -I./../include -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -std=c++11 -c 
> ngram-marginalize.cc  -fPIC -DPIC -o .libs/ngram-marginalize.o
> libtool: compile:  g++ -DHAVE_CONFIG_H -I./../include -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -std=c++11 -c 
> ngram-context.cc  -fPIC -DPIC -o .libs/ngram-context.o
> libtool: compile:  g++ -DHAVE_CONFIG_H -I./../include -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -std=c++11 -c 
> ngram-kneser-ney.cc  -fPIC -DPIC -o .libs/ngram-kneser-ney.o
> libtool: compile:  g++ -DHAVE_CONFIG_H -I./../include -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -std=c++11 -c 
> util.cc  -fPIC -DPIC -o .libs/util.o
> libtool: compile:  g++ -DHAVE_CONFIG_H -I./../include -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -std=c++11 -c 
> hist-arc.cc  -fPIC -DPIC -o .libs/hist-arc.o
> libtool: compile:  g++ -DHAVE_CONFIG_H -I./../include -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -std=c++11 -c 
> util.cc -o util.o >/dev/null 2>&1
> In file included from /usr/include/fst/accumulator.h:18:0,
>  from /usr/include/fst/label-reachable.h:13,
>  from /usr/include/fst/lookahead-matcher.h:13,
>  from /usr/include/fst/lookahead-filter.h:14,
>  from /usr/include/fst/compose.h:16,
>  from ./../include/ngram/ngram-model.h:25,
>  from ./../include/ngram/ngram-context.h:26,
>  from ngram-context.cc:27:
> /usr/include/fst/replace.h: In constructor 
> 'fst::ArcIterator >::ArcIterator(const 
> fst::ReplaceFst&, fst::ArcIterator 
> >::StateId)':
> /usr/include/fst/replace.h:1198:57: error: expected ';' before '::' token
>->template CacheBaseImpl::InitArcIterator(
>  ^~
> In file included from /usr/include/fst/accumulator.h:18:0,
>  from /usr/include/fst/label-reachable.h:13,
>  from /usr/include/fst/lookahead-matcher.h:13,
>  from /usr/include/fst/lookahead-filter.h:14,
>  from /usr/include/fst/compose.h:16,
>  from ./../include/ngram/ngram-model.h:25,
>  from 

Bug#866547: marked as done (python-biomaj3 encoding issue during build)

[Debian Bug Tracking System]

Your message dated Tue, 29 Aug 2017 22:07:57 +
with message-id 
and subject line Bug#866547: fixed in python-biomaj3 3.0.20-2
has caused the Debian Bug report #866547,
regarding python-biomaj3 encoding issue during build
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.)


-- 
866547: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866547
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-biomaj3
Version: 3.0.20-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Now FTBFS.  See attached log.

: pybuild base:184: python3.6 setup.py clean
Traceback (most recent call last):
  File "setup.py", line 18, in 
README = f.read()
  File "/usr/lib/python3.6/encodings/ascii.py", line 26, in decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 1781: 
ordinal not in range(128)
E: pybuild pybuild:283: clean: plugin distutils failed with: exit code=1: 
python3.6 setup.py clean
dh_auto_clean: pybuild --clean --test-nose -i python{version} -p 3.6 3.5 
returned exit code 13
debian/rules:28: recipe for target 'clean' failed

Scott K
I: Logging to 
/home/kitterma/pbuilder/sid_result/python-biomaj3_3.0.20-1_amd64.build
I: using fakeroot in build.
I: Current time: Thu Jun 29 21:25:22 EDT 2017
I: pbuilder-time-stamp: 1498785922
I: Building the build Environment
I: extracting base tarball [/home/kitterma/pbuilder/sid-base.tgz]
I: creating local configuration
I: copying local configuration
W: --override-config is not set; not updating apt.conf Read the manpage for 
details.
I: mounting /proc filesystem
I: mounting /run/shm filesystem
I: mounting /dev/pts filesystem
I: policy-rc.d already exists
I: Obtaining the cached apt archive contents
I: Installing the build-deps
 -> Attempting to satisfy build-dependencies
 -> Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team 
Description: Dummy package to satisfy dependencies with aptitude - created by 
pbuilder
 This package was created automatically by pbuilder to satisfy the
 build-dependencies of the package being currently built.
Depends: debhelper (>= 9), dh-python, python-all, python-setuptools, 
python-mock, python-nose, python-pymongo, python-tabulate, python-ldap3, 
python-bcrypt, python-future, python-elasticsearch, python-pycurl, 
python-drmaa, python3-all, python3-setuptools, python3-mock, python3-nose, 
python3-pymongo, python3-tabulate, python3-ldap3, python3-bcrypt, 
python3-future, python3-elasticsearch, python3-pycurl
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in 
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 14300 files and directories currently installed.)
Preparing to unpack .../pbuilder-satisfydepends-dummy.deb ...
Unpacking pbuilder-satisfydepends-dummy (0.invalid.0) ...
dpkg: pbuilder-satisfydepends-dummy: dependency problems, but configuring 
anyway as you requested:
 pbuilder-satisfydepends-dummy depends on debhelper (>= 9); however:
  Package debhelper is not installed.
 pbuilder-satisfydepends-dummy depends on dh-python; however:
  Package dh-python is not installed.
 pbuilder-satisfydepends-dummy depends on python-all; however:
  Package python-all is not installed.
 pbuilder-satisfydepends-dummy depends on python-setuptools; however:
  Package python-setuptools is not installed.
 pbuilder-satisfydepends-dummy depends on python-mock; however:
  Package python-mock is not installed.
 pbuilder-satisfydepends-dummy depends on python-nose; however:
  Package python-nose is not installed.
 pbuilder-satisfydepends-dummy depends on python-pymongo; however:
  Package python-pymongo is not installed.
 pbuilder-satisfydepends-dummy depends on python-tabulate; however:
  Package python-tabulate is not installed.
 pbuilder-satisfydepends-dummy depends on python-ldap3; however:
  Package python-ldap3 is not installed.
 pbuilder-satisfydepends-dummy depends on python-bcrypt; however:
  Package python-bcrypt is not installed.
 pbuilder-satisfydepends-dummy depends on python-future; however:
  Package python-future is not installed.
 pbuilder-satisfydepends-dummy depends on python-elasticsearch; however:
  Package python-elasticsearch is not installed.
 pbuilder-satisfydepends-dummy depends on 

Bug#871220: marked as done (gcc-doc-defaults: FTBFS with GCC-7)

[Debian Bug Tracking System]

Your message dated Tue, 29 Aug 2017 21:57:06 +
with message-id 
and subject line Bug#871220: fixed in gcc-doc-defaults 5:17
has caused the Debian Bug report #871220,
regarding gcc-doc-defaults: 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.)


-- 
871220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871220
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gcc-doc-defaults
Version: 5:16
Severity: serious
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

gcc-doc-defaults FTBFS since GCC-7 was made the default compiler:

[...]
   debian/rules override_dh_gencontrol-arch
make[1]: Entering directory '/build/gcc-doc-defaults-16'
# call dh_gencontrol one at a time for *-doc packages
dh_gencontrol -p cpp-doc -- -v5:;  dh_gencontrol -p gcc-doc -- -v5:;  
dh_gencontrol -p gfortran-doc -- -v5:;  dh_gencontrol -p gnat-doc -- 
-v5:6.3.0-1;  dh_gencontrol -p gcj-doc -- -v5:6.3.0-1;  dh_gencontrol -p 
gccgo-doc -- -v5:;
dh_gencontrol -a --remaining-packages
dh_gencontrol: No packages to build. Architecture mismatch: amd64, want: all 
alpha amd64 arm64 armel armhf i386 ia64 m68k mips mips64 mips64el mipsel 
powerpc powerpcspe ppc64 ppc64el s390 s390x sparc sparc64 x32 any
make[1]: Leaving directory '/build/gcc-doc-defaults-16'
   debian/rules override_dh_gencontrol-indep
make[1]: Entering directory '/build/gcc-doc-defaults-16'
dh_gencontrol -pgcc-doc-base -- -v6.3.0-1
dh_gencontrol -i --remaining-packages
dh_gencontrol: No packages to build. Architecture mismatch: amd64, want: all 
alpha amd64 arm64 armel armhf i386 ia64 m68k mips mips64 mips64el mipsel 
powerpc powerpcspe ppc64 ppc64el s390 s390x sparc sparc64 x32 any
make[1]: Leaving directory '/build/gcc-doc-defaults-16'
   dh_md5sums
   dh_builddeb
dpkg-deb: error: parsing file 'debian/cpp-doc/DEBIAN/control' near line 3 
package 'cpp-doc':
 error in 'Version' field string '5:': nothing after colon in version number
dh_builddeb: dpkg-deb --build debian/cpp-doc .. returned exit code 2
dpkg-deb: error: parsing file 'debian/gcc-doc/DEBIAN/control' near line 3 
package 'gcc-doc':
 error in 'Version' field string '5:': nothing after colon in version number
dh_builddeb: dpkg-deb --build debian/gcc-doc .. returned exit code 2
dpkg-deb: building package 'gnat-doc' in '../gnat-doc_6.3.0-1_amd64.deb'.
dpkg-deb: error: parsing file 'debian/gfortran-doc/DEBIAN/control' near line 3 
package 'gfortran-doc':
 error in 'Version' field string '5:': nothing after colon in version number
dh_builddeb: dpkg-deb --build debian/gfortran-doc .. returned exit code 2
dpkg-deb: building package 'gcc-doc-base' in '../gcc-doc-base_6.3.0-1_all.deb'.
dpkg-deb: building package 'gcj-doc' in '../gcj-doc_6.3.0-1_amd64.deb'.
dpkg-deb: error: parsing file 'debian/gccgo-doc/DEBIAN/control' near line 3 
package 'gccgo-doc':
 error in 'Version' field string '5:': nothing after colon in version number
dh_builddeb: dpkg-deb --build debian/gccgo-doc .. returned exit code 2
dh_builddeb: Aborting due to earlier error
debian/rules:105: recipe for target 'binary' failed
make: *** [binary] Error 2


The 'dh_gencontrol -- -v5:' looks like some required variable is now unset


Andreas


gcc-doc-defaults_5%16.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: gcc-doc-defaults
Source-Version: 5:17

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

Debian distribution maintenance software
pp.
Guo Yixuan (郭溢譞)  (supplier of updated gcc-doc-defaults 
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: Tue, 22 Aug 2017 22:53:48 -0400
Source: gcc-doc-defaults
Binary: gcc-doc cpp-doc gfortran-doc gnat-doc gcj-doc gccgo-doc gcc-doc-base
Architecture: source amd64 all
Version: 5:17
Distribution: unstable
Urgency: medium
Maintainer: Debian GCC Maintainers 
Changed-By: Guo Yixuan (郭溢譞) 
Description:
 cpp-doc- documentation for 

Bug#853326: marked as done (bind-dyndb-ldap: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Tue, 29 Aug 2017 21:52:11 +
with message-id 
and subject line Bug#853326: fixed in bind-dyndb-ldap 10.1-2
has caused the Debian Bug report #853326,
regarding bind-dyndb-ldap: 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.)


-- 
853326: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853326
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:bind-dyndb-ldap
Version: 10.1-1
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/bind-dyndb-ldap_10.1-1_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

[...]
/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
-I../../src -I..   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra -Werror 
-std=gnu99 -O2 -I/usr/include -D_REENTRANT -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fvisibility=hidden -fno-delete-null-pointer-checks -c 
-o ldap_la-rbt_helper.lo `test -f 'rbt_helper.c' || echo 
'../../src/'`rbt_helper.c
/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
-I../../src -I..   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra -Werror 
-std=gnu99 -O2 -I/usr/include -D_REENTRANT -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fvisibility=hidden -fno-delete-null-pointer-checks -c 
-o ldap_la-semaphore.lo `test -f 'semaphore.c' || echo '../../src/'`semaphore.c
/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
-I../../src -I..   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra -Werror 
-std=gnu99 -O2 -I/usr/include -D_REENTRANT -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fvisibility=hidden -fno-delete-null-pointer-checks -c 
-o ldap_la-settings.lo `test -f 'settings.c' || echo '../../src/'`settings.c
/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
-I../../src -I..   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra -Werror 
-std=gnu99 -O2 -I/usr/include -D_REENTRANT -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fvisibility=hidden -fno-delete-null-pointer-checks -c 
-o ldap_la-syncptr.lo `test -f 'syncptr.c' || echo '../../src/'`syncptr.c
/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
-I../../src -I..   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra -Werror 
-std=gnu99 -O2 -I/usr/include -D_REENTRANT -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fvisibility=hidden -fno-delete-null-pointer-checks -c 
-o ldap_la-syncrepl.lo `test -f 'syncrepl.c' || echo '../../src/'`syncrepl.c
/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
-I../../src -I..   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra -Werror 
-std=gnu99 -O2 -I/usr/include -D_REENTRANT -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fvisibility=hidden -fno-delete-null-pointer-checks -c 
-o ldap_la-str.lo `test -f 'str.c' || echo '../../src/'`str.c
/bin/bash ../libtool  

Bug#873627: udisks2 in sid apparently left me with a borked system in plasma(?)

[Diederik de Haas]

This is essentially a +1 message and downgrading udisks2 + libudisks2-0 to the 
testing version fixed it for me too

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

Processed: block 873661 with 871514

[Debian Bug Tracking System]

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

> block 873661 with 871514
Bug #873661 [src:systemd] Switch back to default GCC
873661 was not blocked by any bugs.
873661 was not blocking any bugs.
Added blocking bug(s) of 873661: 871538, 871514, 872987, and 872438
> thanks
Stopping processing here.

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

Bug#873608: patch

[Paul Tagliamonte]

Whoops, I only just read the comment about this not being standard in
armhf. I misread that and also assumed it was standard (likely because,
as a Coretex-A* user, I always had it), so this patch will likely be
inappropriate (or incomplete). Maybe this patch plus an AND on an
ENABLE_NEON or something, which is disabled by default in the packaging.

  Paul


On Tue, Aug 29, 2017 at 04:10:30PM -0400, Paul Tagliamonte wrote:
> tags 873608 + patch
> thanks
> 
> Attached is a patch that will enable neon if arm_neon.h is present. I
> didn't upstream this or anything, I figure you have a better
> relationship with them, but this ought to fix the ftbfs.
> 
> I'm running a test build now, but it's past the old ftbfs point
> 
>   Paul
> 
> -- 



-- 

Bug#873634: missing module files libbd_*.so

[Amaury Pouly]

> apt install libblockdev-crypto2 libblockdev-mdraid2 libblockdev-part2
> libblockdev-fs2 libblockdev-loop2 libblockdev-swap2
>
I missed the fact that I also needed to install 'gdisk', otherwise it 
fails with

Cannot load the part plugin: The 'sgdisk' utility is not available

This is odd because https://tracker.debian.org/news/866785 mentions 
gdisks is no longer recommended by the package but is still needed?

Bug#873634: missing module files libbd_*.so

[Amaury Pouly]

Same problem here. Tracking down the missing files, I found that 
installing the following packages solves the problem:


apt install libblockdev-crypto2 libblockdev-mdraid2 libblockdev-part2 
libblockdev-fs2 libblockdev-loop2 libblockdev-swap2

Processed: severity of 873634 is grave, forcibly merging 873634 873627

[Debian Bug Tracking System]

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

> severity 873634 grave
Bug #873634 [udisks2] missing module files libbd_*.so
Severity set to 'grave' from 'important'
> forcemerge 873634 873627
Bug #873634 [udisks2] missing module files libbd_*.so
Bug #873627 [udisks2] udisks2 in sid apparently left me with a borked system in 
plasma(?)
Severity set to 'grave' from 'important'
Marked as found in versions udisks2/2.7.2-1.
Bug #873634 [udisks2] missing module files libbd_*.so
Marked as found in versions udisks2/2.6.5-2.
Merged 873627 873634
> thanks
Stopping processing here.

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

Bug#854272: marked as done (CVE-2016-10201 CVE-2016-10202 CVE-2016-10203 CVE-2016-10204 CVE-2016-10205 CVE-2016-10206)

[Debian Bug Tracking System]

Your message dated Tue, 29 Aug 2017 21:56:19 +0100
with message-id 
<1504040179.1241977.1089051400.5a095...@webmail.messagingengine.com>
and subject line Re: zoneminder: CVE-2017-5367 CVE-2017-5368 CVE-2017-5595
has caused the Debian Bug report #854272,
regarding CVE-2016-10201 CVE-2016-10202 CVE-2016-10203 CVE-2016-10204 
CVE-2016-10205 CVE-2016-10206
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.)


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

Please see http://seclists.org/bugtraq/2017/Feb/5

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
forwarded 854272 https://github.com/ZoneMinder/ZoneMinder/pull/1764
tags 854272 + fixed-upstream
thanks

CVE-2017-5595 already addressed, the rest appear to be handled in:

  https://github.com/ZoneMinder/ZoneMinder/pull/1764


Best wishes,

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

Processed: Re: zoneminder: CVE-2017-5367 CVE-2017-5368 CVE-2017-5595

[Debian Bug Tracking System]

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

> forwarded 854733 https://github.com/ZoneMinder/ZoneMinder/pull/1764
Bug #854733 [src:zoneminder] zoneminder: CVE-2017-5367 CVE-2017-5368 
CVE-2017-5595
Set Bug forwarded-to-address to 
'https://github.com/ZoneMinder/ZoneMinder/pull/1764'.
> thanks
Stopping processing here.

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

Processed: Re: zoneminder: CVE-2017-5367 CVE-2017-5368 CVE-2017-5595

[Debian Bug Tracking System]

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

> forwarded 854272 https://github.com/ZoneMinder/ZoneMinder/pull/1764
Bug #854272 [src:zoneminder] CVE-2016-10201 CVE-2016-10202 CVE-2016-10203 
CVE-2016-10204 CVE-2016-10205 CVE-2016-10206
Set Bug forwarded-to-address to 
'https://github.com/ZoneMinder/ZoneMinder/pull/1764'.
> tags 854272 + fixed-upstream
Bug #854272 [src:zoneminder] CVE-2016-10201 CVE-2016-10202 CVE-2016-10203 
CVE-2016-10204 CVE-2016-10205 CVE-2016-10206
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#854733: marked as done (zoneminder: CVE-2017-5367 CVE-2017-5368 CVE-2017-5595)

[Debian Bug Tracking System]

Your message dated Tue, 29 Aug 2017 21:54:02 +0100
with message-id 
<1504040042.855244.1089049736.6e33a...@webmail.messagingengine.com>
and subject line Re: zoneminder: CVE-2017-5367 CVE-2017-5368 CVE-2017-5595
has caused the Debian Bug report #854733,
regarding zoneminder: CVE-2017-5367 CVE-2017-5368 CVE-2017-5595
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.)


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

Please see
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5367
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5368
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5595

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
forwarded 854733 https://github.com/ZoneMinder/ZoneMinder/pull/1764
thanks

Going through this, it looks like the XSS, CSRF, SQL injection and
session fixation issues were indeed reported, addressed and released
upstream.


Best wishes,

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

Bug#862380: Any news?

[Andreas Tille]

Hi Michael,

any news about this?  You said you would like to care for the package.
If it turns out that the real solution takes longer why not applying the
originally suggested patch and continue from a somehow working package?

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#873608: patch

[Paul Tagliamonte]

tags 873608 + patch
thanks

Attached is a patch that will enable neon if arm_neon.h is present. I
didn't upstream this or anything, I figure you have a better
relationship with them, but this ought to fix the ftbfs.

I'm running a test build now, but it's past the old ftbfs point

  Paul

-- 
Description: When building for armhf, enable NEON
 NEON is part of the armhf baseline, so this will always be enabled on
 armhf.
Author: Paul Tagliamonte 
Bug-Debian: https://bugs.debian.org/873608
Origin: vendor
Last-Update: 2017-08-29

--- uhd-3.10.2.0.orig/host/lib/convert/CMakeLists.txt
+++ uhd-3.10.2.0/host/lib/convert/CMakeLists.txt
@@ -67,6 +67,8 @@ IF(HAVE_ARM_NEON_H AND (${CMAKE_SIZEOF_V
 ${CMAKE_CURRENT_SOURCE_DIR}/convert_with_neon.cpp
 ${CMAKE_CURRENT_SOURCE_DIR}/convert_neon.S
 )
+
+SET ( CMAKE_CXX_FLAGS "-mfpu=neon" )
 ENDIF()
 
 

Processed: patch

[Debian Bug Tracking System]

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

> tags 873608 + patch
Bug #873608 [src:uhd] uhd: NEON-related FTBFS on armhf
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#873654: python-py-zipkin: Incomplete debian/copyright?

[Chris Lamb]

Source: python-py-zipkin
Version: 0.9.0-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Olivier Sallou 

Hi,

I just ACCEPTed python-py-zipkin from NEW but noticed it was missing 
attribution in debian/copyright for at least Twitter, Inc.

(This is not exhaustive so please check over the entire package 
carefully and address these on your next upload.)


Best wishes,

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

Processed: bug 863886 is forwarded to https://bugs.ghostscript.com/show_bug.cgi?id=698438

[Debian Bug Tracking System]

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

> forwarded 863886 https://bugs.ghostscript.com/show_bug.cgi?id=698438
Bug #863886 [jbig2dec] jbig2dec: CVE-2016-8729
Set Bug forwarded-to-address to 
'https://bugs.ghostscript.com/show_bug.cgi?id=698438'.
> thanks
Stopping processing here.

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

Bug#873642: weboob-qt: misses dependency on python-pyqt5.qtmultimedia

[ydirson]

Package: weboob-qt
Version: 1.2-1
Severity: serious

without it, qvideoob fails with:

$ qvideoob
Traceback (most recent call last):
  File "/usr/bin/qvideoob", line 24, in 
from weboob.applications.qvideoob import QVideoob
  File 
"/usr/lib/python2.7/dist-packages/weboob/applications/qvideoob/__init__.py", 
line 1, in 
from .qvideoob import QVideoob
  File 
"/usr/lib/python2.7/dist-packages/weboob/applications/qvideoob/qvideoob.py", 
line 24, in 
from .main_window import MainWindow
  File 
"/usr/lib/python2.7/dist-packages/weboob/applications/qvideoob/main_window.py", 
line 30, in 
from .video import Video
  File 
"/usr/lib/python2.7/dist-packages/weboob/applications/qvideoob/video.py", line 
23, in 
from PyQt5.QtMultimedia import QMediaContent, QMediaPlayer
ImportError: No module named QtMultimedia

Processed: Proper bug title

[Debian Bug Tracking System]

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

> retitle 873639 python-scipy FTBFS on ppc64el: python3.5-dbg segfaults
Bug #873639 [src:python-scipy] python-scipy FTBFS on ppc64el:
Changed Bug title to 'python-scipy FTBFS on ppc64el: python3.5-dbg segfaults' 
from 'python-scipy FTBFS on ppc64el:'.
> thanks
Stopping processing here.

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

Bug#873639: python-scipy FTBFS on ppc64el:

[Adrian Bunk]

Source: python-scipy
Version: 0.18.1-2
Severity: serious
Tags: buster sid

https://buildd.debian.org/status/logs.php?pkg=python-scipy=ppc64el

...
scipy/sparse/linalg/dsolve/SuperLU/SRC/sgsrfs.c: In function 'sgsrfs':
scipy/sparse/linalg/dsolve/SuperLU/SRC/sgsrfs.c:416:3: warning: 'transt' may be 
used uninitialized in this function [-Wmaybe-uninitialized]
   sgstrs (transt, L, U, perm_c, perm_r, , stat, info);
   ^
scipy/sparse/linalg/dsolve/SuperLU/SRC/zlacon2.c: In function 'zlacon2_':
scipy/sparse/linalg/dsolve/SuperLU/SRC/zlacon2.c:165:5: warning: implicit 
declaration of function 'zcopy_'; did you mean 'zlacon2_'? 
[-Wimplicit-function-declaration]
 zcopy_(n, x, __1, v, __1);
 ^~
 zlacon2_
scipy/sparse/linalg/dsolve/SuperLU/SRC/zlacon2.c:171:1: warning: label 'L90' 
defined but not used [-Wunused-label]
 L90:
 ^~~
powerpc64le-linux-gnu-gcc: scipy/sparse/linalg/dsolve/SuperLU/SRC/sgssvx.c
In file included from scipy/sparse/linalg/dsolve/SuperLU/SRC/slu_cdefs.h:87:0,
 from scipy/sparse/linalg/dsolve/SuperLU/SRC/ccopy_to_ucol.c:23:
scipy/sparse/linalg/dsolve/SuperLU/SRC/slu_util.h:373:1: warning: function 
declaration isn't a prototype [-Wstrict-prototypes]
 extern double  SuperLU_timer_ ();
 ^~
powerpc64le-linux-gnu-gcc: scipy/sparse/linalg/dsolve/SuperLU/SRC/dpruneL.c
scipy/sparse/linalg/dsolve/SuperLU/SRC/ccopy_to_ucol.c: In function 
'ccopy_to_ucol':
scipy/sparse/linalg/dsolve/SuperLU/SRC/ccopy_to_ucol.c:77:11: warning: suggest 
parentheses around assignment used as truth value [-Wparentheses]
   if (mem_error = cLUMemXpand(jcol, nextu, UCOL, , Glu))
   ^
In file included from scipy/sparse/linalg/dsolve/SuperLU/SRC/slu_zdefs.h:87:0,
 from scipy/sparse/linalg/dsolve/SuperLU/SRC/zpanel_dfs.c:25:
scipy/sparse/linalg/dsolve/SuperLU/SRC/slu_util.h:373:1: warning: function 
declaration isn't a prototype [-Wstrict-prototypes]
 extern double  SuperLU_timer_ ();
 ^~
scipy/sparse/linalg/dsolve/SuperLU/SRC/ccopy_to_ucol.c:80:11: warning: suggest 
parentheses around assignment used as truth value [-Wparentheses]
   if (mem_error = cLUMemXpand(jcol, nextu, USUB, , Glu))
   ^
In file included from scipy/sparse/linalg/dsolve/SuperLU/SRC/slu_zdefs.h:87:0,
 from scipy/sparse/linalg/dsolve/SuperLU/SRC/zgsisx.c:12:
scipy/sparse/linalg/dsolve/SuperLU/SRC/slu_util.h:373:1: warning: function 
declaration isn't a prototype [-Wstrict-prototypes]
 extern double  SuperLU_timer_ ();
 ^~
scipy/sparse/linalg/dsolve/SuperLU/SRC/zgsisx.c: In function 'zgsisx':
scipy/sparse/linalg/dsolve/SuperLU/SRC/zgsisx.c:578:7: warning: suggest 
parentheses around operand of '!' or change '&' to '&&' or '!' to '~' 
[-Wparentheses]
  if ( !mc64 & equil ) { /* Only perform equilibration, no row perm */
   ^
powerpc64le-linux-gnu-gcc: scipy/sparse/linalg/dsolve/SuperLU/SRC/qselect.c
scipy/sparse/linalg/dsolve/SuperLU/SRC/zgsisx.c:667:24: warning: unused 
variable 'rhs_work' [-Wunused-variable]
 doublecomplex *rhs_work;
^~~~
scipy/sparse/linalg/dsolve/SuperLU/SRC/zgsisx.c:413:15: warning: variable 
'diag_pivot_thresh' set but not used [-Wunused-but-set-variable]
 doublediag_pivot_thresh;
   ^
Segmentation fault
debian/rules:36: recipe for target 'build-python3.5' failed
make[1]: *** [build-python3.5] Error 139
make[1]: Leaving directory '/<>'
debian/rules:43: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2



Reproduced on plummer, top part of the backtrace:

#0  PyTuple_GetItem (op=0x0, i=0) at ../Objects/tupleobject.c:138
#1  0x33ea184c in PyEval_EvalFrameEx (
f=Frame 0x3fff38000bc8, for file 
/usr/lib/python3/dist-packages/numpy/distutils/exec_command.py, line 279, in 
_exec_command_posix (command=['powerpc64le-linux-gnu-gcc', '-pthread', '-g', 
'-Og', '-Wall', '-Wstrict-prototypes', '-g', '-ggdb', '-Wdate-time', 
'-D_FORTIFY_SOURCE=2', '-fPIC', '-DUSE_VENDOR_BLAS=1', 
'-Iscipy/sparse/linalg/dsolve/SuperLU/SRC', 
'-I/usr/lib/python3/dist-packages/numpy/core/include', '-c', 
'scipy/sparse/linalg/dsolve/SuperLU/SRC/zpanel_dfs.c', '-o', 
'build/temp.linux-ppc64le-3.5-pydebug/scipy/sparse/linalg/dsolve/SuperLU/SRC/zpanel_dfs.o'],
 use_shell=True, use_tee=True, env={}, command_str='powerpc64le-linux-gnu-gcc 
-pthread -g -Og -Wall -Wstrict-prototypes -g -ggdb -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -DUSE_VENDOR_BLAS=1 
-Iscipy/sparse/linalg/dsolve/SuperLU/SRC 
-I/usr/lib/python3/dist-packages/numpy/core/include -c 
scipy/sparse/linalg/dsolve/SuperLU/SRC/zpanel_dfs.c -o 
build/temp.linux-ppc64le-3.5-pydebug/scipy/sparse/linalg/dsolve/SuperLU/SRC/zpanel_dfs.
 o', tmpfile='/tmp/tmpesxa6x6k/6b...(truncated), throwflag=0) at 
../Python/ceval.c:1381
#2  0x33eafcb4 in _PyEval_EvalCodeWithName (_co=, globals=, locals=, 
args=, argcount=, kws=0x3fff9aaede80, 

Bug#872298: marked as done (poppler: Incomplete debian/copyright?)

[Debian Bug Tracking System]

Your message dated Tue, 29 Aug 2017 17:13:10 +
with message-id 
and subject line Bug#872298: fixed in poppler 0.57.0-2
has caused the Debian Bug report #872298,
regarding poppler: Incomplete debian/copyright?
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.)


-- 
872298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872298
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: poppler
Version: 0.57.0-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Emilio Pozuelo Monfort 

Hi,

I just ACCEPTed poppler from NEW but noticed it was missing 
attribution in debian/copyright for at least a lot of references
in utils/pdftotext.cc.

(This is not exhaustive so please check over the entire package 
carefully and address these on your next upload.)


Best wishes,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: poppler
Source-Version: 0.57.0-2

We believe that the bug you reported is fixed in the latest version of
poppler, 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.
Emilio Pozuelo Monfort  (supplier of updated poppler 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 18:42:54 +0200
Source: poppler
Binary: libpoppler68 libpoppler-dev libpoppler-private-dev libpoppler-glib8 
libpoppler-glib-dev libpoppler-glib-doc gir1.2-poppler-0.18 libpoppler-qt4-4 
libpoppler-qt4-dev libpoppler-qt5-1 libpoppler-qt5-dev libpoppler-cpp0v5 
libpoppler-cpp-dev poppler-utils
Architecture: source
Version: 0.57.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian freedesktop.org maintainers 

Changed-By: Emilio Pozuelo Monfort 
Description:
 gir1.2-poppler-0.18 - GObject introspection data for poppler-glib
 libpoppler-cpp-dev - PDF rendering library -- development files (CPP interface)
 libpoppler-cpp0v5 - PDF rendering library (CPP shared library)
 libpoppler-dev - PDF rendering library -- development files
 libpoppler-glib-dev - PDF rendering library -- development files (GLib 
interface)
 libpoppler-glib-doc - PDF rendering library -- documentation for the GLib 
interface
 libpoppler-glib8 - PDF rendering library (GLib-based shared library)
 libpoppler-private-dev - PDF rendering library -- private development files
 libpoppler-qt4-4 - PDF rendering library (Qt 4 based shared library)
 libpoppler-qt4-dev - PDF rendering library -- development files (Qt 4 
interface)
 libpoppler-qt5-1 - PDF rendering library (Qt 5 based shared library)
 libpoppler-qt5-dev - PDF rendering library -- development files (Qt 5 
interface)
 libpoppler68 - PDF rendering library
 poppler-utils - PDF utilities (based on Poppler)
Closes: 872298
Changes:
 poppler (0.57.0-2) unstable; urgency=medium
 .
   * debian/copyright: Add missing copyright holders. Closes: #872298.
   * Upload to unstable.
Checksums-Sha1:
 8cf5475b3b50252eb965ac21c42902878caccfd1 3437 poppler_0.57.0-2.dsc
 128f175a81a7c25c4c67b353391b8cae506db2ae 1703300 poppler_0.57.0.orig.tar.xz
 57dfa29a1e1afe5f80c88e8f4cc54b7ae0b8c291 31360 poppler_0.57.0-2.debian.tar.xz
 430bc940395d1360152d32770fa5f65166900401 12037 
poppler_0.57.0-2_source.buildinfo
Checksums-Sha256:
 fa0a279a9f77c0086cfc6f50e4721c9befb2f5abb87df3616041a4bfe47a3e42 3437 
poppler_0.57.0-2.dsc
 0ea37de71b7db78212ebc79df59f99b66409a29c2eac4d882dae9f2397fe44d8 1703300 
poppler_0.57.0.orig.tar.xz
 f6fa75230f7fa05c32ccd6d660eca87cf8120b848a43f5d0921b5b16a4c7b819 31360 
poppler_0.57.0-2.debian.tar.xz
 5a75d7089de860b721a16bbe49c9045aa3e2a7be1f3b3e6c1c70b874d95ad99d 12037 
poppler_0.57.0-2_source.buildinfo
Files:
 ded1cfc66ec41f603d985f223413a5c2 3437 devel optional poppler_0.57.0-2.dsc
 bc5a191741604552c90d484103229374 1703300 devel optional 
poppler_0.57.0.orig.tar.xz
 2fd731b477ad715fb1f7c412dd27ed6a 31360 devel optional 
poppler_0.57.0-2.debian.tar.xz
 

Bug#853319: [Aspectc-developers] Fwd: Bug#853319: aspectc++: ftbfs with GCC-7

[Reinhard Tartler]

I've uploaded a new package that simply ignores failures from tests. Not 
exactly an ideal situation because it renders the test ineffective.

From what I understand I could instead dialer disable these the tests instead. 
But before doing that, I wanted to check with you if these failures also 
occurred on your akut Test infrastructure. If yes, how do you deal with them, 
maybe you could disable the test in svn. If they do not appear in akut, I 
wonder why.

I agree that it's not super critical or urgent to me, but I think you are in a 
much per position to assess the criticality and urgency.

Thanks
Reinhard

On August 29, 2017 12:19:21 PM EDT, Olaf Spinczyk 
 wrote:
>Hi Reinhard!
>
>We should definitely look into these three problems within the next few
>weeks, but I don't regard them as very critical, because they affect
>only special use cases: Advice for user-defined "operator new"
>implementations and the code generation for get/set advice, which is a
>feature that is only enabled with --data_joinpoints and still a bit
>experimental.
>
>How to proceed? Can we/you live with these problems for now and update
>later or is there no update option and we have to fix it sooner?
>
>Cheers,
>
>Olaf
>
>On 08/24/2017 00:16, Reinhard Tartler wrote:
>> 
>> 
>> On 08/23/2017 12:07 PM, Olaf Spinczyk wrote:
>>> Hi!
>>>
>>> You can generate the config file easily with ag++ --gen_config.
>Sorry
>>> for the inconvenience. The background is that when I wrote the first
>>> ac++ tests, I did not want the makefile to depend on ag++.
>>>
>>> We should change that sooner or later, because it is obviously
>confusing.
>> 
>> Not a problem.
>> 
>> Progress! With a "correct" PUMA CONFIG, I now get further, but there
>seem to be
>> genuine test failures. Are they concerning or shall I ignore them for
>the debian
>> package?
>> 
>> They look like this:
>> 
>> /usr/bin/make -C tests -s  all
>> make[2]: Entering directory
>> '/build/aspectc++-rCVJRW/aspectc++-2.2+git20170823/AspectC++/tests'
>>
>...[C:ExecAdviceNewDelete].[D:Bug574]...[C:Bug598]
>> 
>> 
>> +-+
>> |ERRORS:  |
>> +-+
>> 
>>
>-
>> TEST: ExecAdviceNewDelete
>>
>-
>> STDOUT:
>> 
>> make[3]: Entering directory
>>
>'/build/aspectc++-rCVJRW/aspectc++-2.2+git20170823/AspectC++/tests/ExecAdviceNewDelete'
>> Weaving main.cc
>> * Running ac++ 2.2
>> * Handling Translation Unit `main.cc'.
>>   - Path "main.cc"
>>   - Parsing ...
>>   - Weaving Aspects Forward Declarations ...
>>   - Inserting namespace AC
>>   - Committing
>>   - Preparing introductions ...
>>   - Parsing again ...
>>   - Weaving access control bypass classes ...
>>   - Weaving Join Points ...
>> Advicecode manipulation
>> Collecting Advice
>>   Setting up thisJoinPoint for aspectof
>> Create pointcut expression tree
>> Matching joinpoints
>> Aspect ordering ...
>> Creating project repository 'repo.acp'
>> Type Check Functions
>> Access Join Points
>> Execution Join Points
>>   void *operator new(unsigned long int)
>>   void *operator new[](unsigned long int)
>>   void operator delete(void *)
>>   void operator delete[](void *)
>>   void A::operator delete(void *)
>>   void *C::operator new(unsigned long int)
>>   void C::operator delete(void *)
>> Construction Join Points
>> Destruction Join Points
>>   - Aspect Includes ...
>>   - Final cleanup
>>   - Committing
>> * Inserting unit pro- and epilogues
>>   - Manipulating translation unit file main.cc
>> * Updating #line directives of generated code fragments
>> * Saving
>>   - Expanding project includes
>>   - Fixing #line directives
>>   - Path "main.acc"
>> * Done
>> Compiling main.acc
>> ../Makefile.generic:80: recipe for target 'Junk/main.o' failed
>> make[3]: Leaving directory
>>
>'/build/aspectc++-rCVJRW/aspectc++-2.2+git20170823/AspectC++/tests/ExecAdviceNewDelete'
>> 
>> STDERR:
>> 
>> main.cc:5:30: warning: dynamic exception specifications are
>deprecated in C++11
>> [-Wdeprecated]
>>  void *operator new (size_t ) throw(std::bad_alloc);
>>   ^
>> main.cc:7:31: warning: dynamic exception specifications are
>deprecated in C++11
>> [-Wdeprecated]
>>  void *operator new (size_t s) throw(std::bad_alloc) {
>>^
>> main.cc: In function 'void* operator new(size_t)':
>> main.cc:7:7: error: declaration of 'void* operator new(size_t) throw
>> (std::bad_alloc)' has a different exception specifier
>>  void *operator new (size_t s) throw(std::bad_alloc) {
>>^~~~
>> main.cc:5:7: note: from previous declaration 'void* operator
>new(std::size_t)'
>>  void *operator new 

Bug#873557: marked as done (mbedtls: possible authentication bypass)

[Debian Bug Tracking System]

Your message dated Tue, 29 Aug 2017 17:11:34 +
with message-id 
and subject line Bug#873557: fixed in mbedtls 2.6.0-1
has caused the Debian Bug report #873557,
regarding mbedtls: possible authentication bypass
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.)


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

Hi,

The following security advisory was published for mbedtls:
https://tls.mbed.org/tech-updates/security-advisories/mbedtls-security-advisory-2017-02

[Vulnerability]
If a malicious peer supplies an X.509 certificate chain that has more
than MBEDTLS_X509_MAX_INTERMEDIATE_CA intermediates (which by default is
8), it could bypass authentication of the certificates, when the
authentication mode was set to 'optional' eg.
MBEDTLS_SSL_VERIFY_OPTIONAL. The issue could be triggered remotely by
both the client and server sides.

If the authentication mode, which can be set by the function
mbedtls_ssl_conf_authmode(), was set to 'required' eg.
MBEDTLS_SSL_VERIFY_REQUIRED which is the default, authentication would
occur normally as intended.

[Impact]
Depending on the platform, an attack exploiting this vulnerability could
allow successful impersonation of the intended peer and permit
man-in-the-middle attacks.

The advisory states that only mbedtls >= 1.3.10 is affected, which means
that jessie's version of polarssl is not affected.

I think this is the commit which fixes this, but I have not checked yet:
https://github.com/ARMmbed/mbedtls/commit/31458a18788b0cf0b722acda9bb2f2fe13a3fb32

James



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: mbedtls
Source-Version: 2.6.0-1

We believe that the bug you reported is fixed in the latest version of
mbedtls, 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.
James Cowgill  (supplier of updated mbedtls 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: Tue, 29 Aug 2017 16:09:30 +0100
Source: mbedtls
Binary: libmbedtls-dev libmbedcrypto0 libmbedtls10 libmbedx509-0 libmbedtls-doc
Architecture: source
Version: 2.6.0-1
Distribution: unstable
Urgency: high
Maintainer: James Cowgill 
Changed-By: James Cowgill 
Description:
 libmbedcrypto0 - lightweight crypto and SSL/TLS library - crypto library
 libmbedtls-dev - lightweight crypto and SSL/TLS library - development files
 libmbedtls-doc - lightweight crypto and SSL/TLS library - documentation
 libmbedtls10 - lightweight crypto and SSL/TLS library - tls library
 libmbedx509-0 - lightweight crypto and SSL/TLS library - x509 certificate 
library
Closes: 873557
Changes:
 mbedtls (2.6.0-1) unstable; urgency=high
 .
   * New upstream version.
 - Fixes possible authentication bypass if a peer supplies a certificate
   chain with more than 8 intermediates. (Closes: #873557)
 .
   * debian/copyright:
 - Update copyright dates.
 - Use https Format URL.
   * debian/control:
 - Bump standards to 4.1.0 (no changes required).
 - Use debhelper compat 10.
   * debian/libmbedcrypto0.symbols:
 - Add new symbols from 2.6.0.
   * debian/patches:
 - Refresh config patch.
 - Drop all stubs patches - upstream reverted the ABI breakage.
Checksums-Sha1:
 29442316b62139fa2be3aa5036ad8ad38bba4bb1 2221 mbedtls_2.6.0-1.dsc
 e914288da50977f541773f9d36e26f14926594a5 1973397 mbedtls_2.6.0.orig.tar.gz
 8929984bf729d0fbe0afb09191c62d2878b0033c 11048 mbedtls_2.6.0-1.debian.tar.xz
 b9c8e2304d2610ffc2a320ed3b1e5202f2bc5b4e 6203 mbedtls_2.6.0-1_source.buildinfo
Checksums-Sha256:
 681980e13390160cecd0f3e69834106bde148c007333b39869f4a9f79e3f34cb 2221 
mbedtls_2.6.0-1.dsc
 99bc9d4212d3d885eeb96273bcde8ecc649a481404b8d7ea7bb26397c9909687 1973397 
mbedtls_2.6.0.orig.tar.gz
 54462b68263620ba138e4db0382b4ac519d2720a8e076045429f5124ac2633c9 11048 
mbedtls_2.6.0-1.debian.tar.xz
 

Bug#873539: marked as done (monit 1:5.23.0-3 won't install - "epoch in version is empty")

[Debian Bug Tracking System]

Your message dated Tue, 29 Aug 2017 17:11:45 +
with message-id 
and subject line Bug#873539: fixed in monit 1:5.23.0-4
has caused the Debian Bug report #873539,
regarding monit 1:5.23.0-3 won't install - "epoch in version is empty"
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.)


-- 
873539: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873539
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: monit
Version: 1:5.23.0-2
Severity: normal

Dear Maintainer,

Tried to upgrade monit (via aptitude and apt-get) on amd64 unstable from 
version 
1:5.23.0-2 to 1:5.23.0-3. Here's the installation text:

Preparing to unpack .../monit_1%3a5.23.0-3_amd64.deb ...
dpkg-maintscript-helper: error: dpkg: error: version '"1:5.15-1~"' has bad 
syntax: epoch in version is empty
dpkg: error processing archive 
/var/cache/apt/archives/monit_1%3a5.23.0-3_amd64.deb (--unpack):
 subprocess new pre-installation script returned error exit status 1
dpkg-maintscript-helper: error: dpkg: error: version '"1:5.15-1~"' has bad 
syntax: epoch in version is empty
dpkg: error while cleaning up:
 subprocess new post-removal script returned error exit status 1
Errors were encountered while processing:
 /var/cache/apt/archives/monit_1%3a5.23.0-3_amd64.deb
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)

I tried to find where epoch information resides, but I am not familiar enough
with Debian packaging. Tried to build it from source (apt-get source), but got
the same error. Downloaded version 1:5.23.0-2 source and have reinstalled that
instead.

Hope this is helpful. Thanks for your time now and for maintaining monit!


-- Package-specific info:

Monit config file /etc/monit/monitrc is *NOT* readable by reportbug.
Please, consider to rerun reportbug as root and *carefully* examine
reportbug's output (e.g., monitrc content), before sending it out.

Contents of /etc/monit/ directory:
/etc/monit:
total 36
drwxr-xr-x 2 root root  4096 Aug 28 12:27 conf-available
drwxr-xr-x 2 root root  4096 Mar  7  2016 conf-enabled
drwxr-xr-x 2 root root  4096 Mar  7  2016 conf.d
-rw--- 1 root root 13099 Jul  8 03:11 monitrc
drwxr-xr-x 2 root root  4096 Aug  4 09:55 monitrc.d
drwxr-xr-x 2 root root  4096 Aug 28 12:27 templates

/etc/monit/conf-available:
total 60
-rw-r--r-- 1 root root  481 Mar  7  2016 acpid
-rw-r--r-- 1 root root  640 Mar  7  2016 apache2
-rw-r--r-- 1 root root  455 Mar  7  2016 at
-rw-r--r-- 1 root root  691 Mar  7  2016 cron
-rw-r--r-- 1 root root  602 Mar  7  2016 mdadm
-rw-r--r-- 1 root root  669 Mar  7  2016 memcached
-rw-r--r-- 1 root root  703 Mar  7  2016 mysql
-rw-r--r-- 1 root root  521 Mar  7  2016 nginx
-rw-r--r-- 1 root root  471 Mar  7  2016 openntpd
-rw-r--r-- 1 root root  950 Mar  7  2016 openssh-server
-rw-r--r-- 1 root root  683 Mar  7  2016 pdns-recursor
-rw-r--r-- 1 root root 1421 Mar  7  2016 postfix
-rw-r--r-- 1 root root  869 Mar 22  2016 rsyslog
-rw-r--r-- 1 root root  501 Mar  7  2016 smartmontools
-rw-r--r-- 1 root root  306 Mar  7  2016 snmpd

/etc/monit/conf-enabled:
total 0

/etc/monit/conf.d:
total 0

/etc/monit/monitrc.d:
total 4
-rw-r--r-- 1 root root 403 Dec  9  2016 fail2ban

/etc/monit/templates:
total 12
-rw-r--r-- 1 root root 164 Mar  7  2016 rootbin
-rw-r--r-- 1 root root 160 Mar  7  2016 rootrc
-rw-r--r-- 1 root root 164 Mar  7  2016 rootstrict


-- 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_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
LANGUAGE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages monit depends on:
ii  libc6  2.24-17
ii  libpam0g   1.1.8-3.6
ii  libssl1.1  1.1.0f-5
ii  lsb-base   9.20170808
ii  zlib1g 1:1.2.8.dfsg-5

monit recommends no packages.

Versions of packages monit suggests:
ii  postfix [mail-transport-agent]  3.2.2-1
pn  sysvinit-core   

-- Configuration Files:
/etc/monit/monitrc [Errno 13] Permission denied: '/etc/monit/monitrc'

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: monit
Source-Version: 1:5.23.0-4

We believe that the bug you reported is fixed in the latest version of
monit, 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, 

Bug#872880: marked as done (libemf: FTBFS: #error Unknown CPU architecture!)

[Debian Bug Tracking System]

Your message dated Tue, 29 Aug 2017 17:09:23 +
with message-id 
and subject line Bug#872880: fixed in libemf 1.0.9+git.10.3231442-1
has caused the Debian Bug report #872880,
regarding libemf: FTBFS: #error Unknown CPU architecture!
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.)


-- 
872880: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872880
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libemf
Version: 1.0.9+git.9.e2f97d9-1
Severity: important
Tags: upstream
Justification: fails to build from source

Builds of libemf have been failing on arm64, mips*, and the
non-release architectures hppa, m68k, and sh4:

  In file included from ../include/libEMF/wine/windef.h:16:0,
   from ../include/libEMF/emf.h:27,
   from libemf.h:32,
   from libemf.cpp:24:
  ../include/libEMF/wine/winnt.h:61:3: error: #error Unknown CPU architecture!
   # error Unknown CPU architecture!
 ^
  In file included from ../include/libEMF/wine/windef.h:16:0,
   from ../include/libEMF/emf.h:27,
   from libemf.h:32,
   from libemf.cpp:24:
  ../include/libEMF/wine/winnt.h:1429:2: error: #error You need to define a 
CONTEXT for your CPU
   #error You need to define a CONTEXT for your CPU
^
  ../include/libEMF/wine/winnt.h:1432:9: error: 'CONTEXT' does not name a type; 
did you mean 'CONTEXT86'?
   typedef CONTEXT *PCONTEXT;
   ^~~
   CONTEXT86

Could you please take a look?  It would be best if you could cut out
the CPU-dependent code altogether.  However, if that's infeasible,
please restrict libemf's official Architecture accordingly so that
incompatible autobuilders don't bother trying to cover it.

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
--- End Message ---
--- Begin Message ---
Source: libemf
Source-Version: 1.0.9+git.10.3231442-1

We believe that the bug you reported is fixed in the latest version of
libemf, 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.
Barak A. Pearlmutter  (supplier of updated libemf 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 14:58:58 +0100
Source: libemf
Binary: libemf-dev libemf1 libemf-doc printemf
Architecture: source amd64 all
Version: 1.0.9+git.10.3231442-1
Distribution: unstable
Urgency: medium
Maintainer: Barak A. Pearlmutter 
Changed-By: Barak A. Pearlmutter 
Description:
 libemf-dev - Enhanced Metafile library (development)
 libemf-doc - Enhanced Metafile library (documentation)
 libemf1- Enhanced Metafile library (run-time)
 printemf   - Enhanced Metafile library (executable)
Closes: 872880
Changes:
 libemf (1.0.9+git.10.3231442-1) unstable; urgency=medium
 .
   * Incorporate Fedora aarch64 patch
   * Restrict architecture list (closes: #872880)
Checksums-Sha1:
 a516b861edf7c264863fb35ddedea2648379770c 2589 libemf_1.0.9+git.10.3231442-1.dsc
 94bc0275269a60e53f1cf5b5dd0e3b3e8569c229 224124 
libemf_1.0.9+git.10.3231442.orig.tar.gz
 192dec225d678d6510d3b78f1c5d2483700eec46 2856 
libemf_1.0.9+git.10.3231442-1.debian.tar.xz
 1a018dcc309233b8748023de387846b5611f4de8 157704 
libemf-dev_1.0.9+git.10.3231442-1_amd64.deb
 ee3a9c13a9f9318998272b700b6fcf2e99bb3838 1083416 
libemf-doc_1.0.9+git.10.3231442-1_all.deb
 b8f2bea08dffba3b18493f195118b304d311bb73 261892 
libemf1-dbgsym_1.0.9+git.10.3231442-1_amd64.deb
 48638edb1c36afdcb1cb2fdbf8a4732b7bb0c2f6 55856 
libemf1_1.0.9+git.10.3231442-1_amd64.deb
 a72659d2ceb9491a8c25932bee6235ce173d76c8 10247 
libemf_1.0.9+git.10.3231442-1_amd64.buildinfo
 7248c1549005c4d257f0500c2fb94dc48e425796 4290 
printemf-dbgsym_1.0.9+git.10.3231442-1_amd64.deb
 2b8e370a63d8a271a516b1b15f7d1b0508e5f4d5 5182 
printemf_1.0.9+git.10.3231442-1_amd64.deb
Checksums-Sha256:
 c589416cc7d7304dbc67cd020b6d9338c54ee7fa13ac41c95e95ea9ff750ac6e 2589 

Bug#873616: marked as done (libdazzle: Incomplete debian/copyright?)

[Debian Bug Tracking System]

Your message dated Tue, 29 Aug 2017 17:09:08 +
with message-id 
and subject line Bug#873616: fixed in libdazzle 3.25.91-1
has caused the Debian Bug report #873616,
regarding libdazzle: Incomplete debian/copyright?
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.)


-- 
873616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873616
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libdazzle
Version: 3.25.5-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Jeremy Bicha 

Hi,

I just ACCEPTed libdazzle from NEW but noticed it was missing 
attribution in debian/copyright for at least Garrett Regier,
Async Open Source, James Henstridge etc etc.

(This is not exhaustive so please check over the entire package 
carefully and address these on your next upload.)


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: libdazzle
Source-Version: 3.25.91-1

We believe that the bug you reported is fixed in the latest version of
libdazzle, 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.
Jeremy Bicha  (supplier of updated libdazzle 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: Tue, 29 Aug 2017 10:43:08 -0400
Source: libdazzle
Binary: libdazzle-1.0-0 libdazzle-1.0-dev libdazzle-doc libdazzle-tools 
gir1.2-dazzle-1.0
Architecture: source
Version: 3.25.91-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bicha 
Description:
 gir1.2-dazzle-1.0 - GObject introspection data for libdazzle
 libdazzle-1.0-0 - feature-filled library for GTK+ and GObject
 libdazzle-1.0-dev - feature-filled library for GTK+ and GObject - development 
files
 libdazzle-doc - feature-filled library for GTK+ and GObject - documentation
 libdazzle-tools - feature-filled library for GTK+ and GObject - tools
Closes: 873616
Changes:
 libdazzle (3.25.91-1) unstable; urgency=medium
 .
   * New upstream release
   * debian/libdazzle-1.0-0.symbols: Add new symbols
   * debian/control.in: trivial tweaks
   * debian/copyright: Add missing copyright attributions, thanks
 Chris Lamb for the report (Closes: #873616)
Checksums-Sha1:
 739620a8e598e4b29a579140c5adc657d9fbcdee 2369 libdazzle_3.25.91-1.dsc
 dc4316d413f95402251316ba933569dcefed18c7 397328 libdazzle_3.25.91.orig.tar.xz
 f7061cd42f7f6c45a5b59ab853fb7d3bacfac41b 7816 libdazzle_3.25.91-1.debian.tar.xz
 d8147c9bfda6a81bf0f501d30ae8c33fd5f6f42d 17205 
libdazzle_3.25.91-1_source.buildinfo
Checksums-Sha256:
 98b0f26b8a731728ebef152bdcc84ca108b39b817adcf396a169d6e60b663dab 2369 
libdazzle_3.25.91-1.dsc
 1a7eb8cb1b030b93f6652db81ca4a2cfac1133a60b768b28affcbe836e6ae649 397328 
libdazzle_3.25.91.orig.tar.xz
 2a30c2eb5fb78e9cc23e4985abe38da927c3827c5d447dcd1280e74fe76df205 7816 
libdazzle_3.25.91-1.debian.tar.xz
 a50c74ed569c36f8c2822c01fd2cafe0b16aed45c64e14909323f05149ca365f 17205 
libdazzle_3.25.91-1_source.buildinfo
Files:
 2318118f0bf7bda63279cbba0ec1e741 2369 libs optional libdazzle_3.25.91-1.dsc
 673e6bc4f5b169161e3c06fe931f79db 397328 libs optional 
libdazzle_3.25.91.orig.tar.xz
 6004f86656c83fc5a36fe21eb45f4d11 7816 libs optional 
libdazzle_3.25.91-1.debian.tar.xz
 3bcf52f5da3b9f617612598c7b99d758 17205 libs optional 
libdazzle_3.25.91-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJZpYGxAAoJEOZsd1rr/mx9ffsP/1lQp6I4sdtrNX6BOcSeROqC
OtFUu71mTj6LEY6w+uxU9kpvevf3kekSn47vQLV7/tuzPOHdsZ9UBeOs/B5KNCo6
04XwOozQPX3/bKBMgMuMSNJPLMlEM/RQAGw4Y3eQDLYU+SBLbck/JmPu2RHfULkU
ywsI0so9FyGcNsbH2NQqjMIJjbpwCcWnvnrsTMr//UmcxiFJ4fBlZBqmWdMhm0h3
0Zkv05LuPX3AfMT45cHX4Ug1JmxPJrxJRxuShW49D6ZrwKDNk6+x2xBpT44palwW
bgrw5KEoRKpl6/0STJ1BemVaNBHaHVPnuOViI4XV3yopmkismyxRGVqUEeBxuErM
9Mp6e5jlUJws812R5JFY0sSjyFlyZGhFy3leTFso8A3Oid8246L8/N4nkzREnalX
6YJUniswyF8YZ1Je823Cq90ZL7D9f00VtYIXMfmUjwd6nJuMSeVrpsBOfXyENlKM

Bug#873632: ruby-css-parser FTBFS: CssParser::RemoteFileError: https://dialect.ca:443/inc/screen.css

[Adrian Bunk]

Source: ruby-css-parser
Version: 1.5.0.pre2-1
Severity: serious

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

...
Finished in 0.128064s, 765.2416 runs/s, 3755.9306 assertions/s.

  1) Error:
CssParserOffsetCaptureTests#test_capturing_offsets_from_remote_file:
CssParser::RemoteFileError: https://dialect.ca:443/inc/screen.css

/build/1st/ruby-css-parser-1.5.0.pre2/debian/ruby-css-parser/usr/lib/ruby/vendor_ruby/css_parser/parser.rb:625:in
 `rescue in read_remote_file'

/build/1st/ruby-css-parser-1.5.0.pre2/debian/ruby-css-parser/usr/lib/ruby/vendor_ruby/css_parser/parser.rb:569:in
 `read_remote_file'

/build/1st/ruby-css-parser-1.5.0.pre2/debian/ruby-css-parser/usr/lib/ruby/vendor_ruby/css_parser/parser.rb:454:in
 `load_uri!'

/build/1st/ruby-css-parser-1.5.0.pre2/test/test_css_parser_offset_capture.rb:34:in
 `test_capturing_offsets_from_remote_file'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:107:in `block (3 levels) in run'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:204:in `capture_exceptions'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:104:in `block (2 levels) in run'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:255:in `time_it'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:103:in `block in run'
/usr/lib/ruby/vendor_ruby/minitest.rb:350:in `on_signal'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:275:in `with_info_handler'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:102:in `run'
/usr/lib/ruby/vendor_ruby/minitest.rb:839:in `run_one_method'
/usr/lib/ruby/vendor_ruby/minitest.rb:324:in `run_one_method'
/usr/lib/ruby/vendor_ruby/minitest.rb:311:in `block (2 levels) in run'
/usr/lib/ruby/vendor_ruby/minitest.rb:310:in `each'
/usr/lib/ruby/vendor_ruby/minitest.rb:310:in `block in run'
/usr/lib/ruby/vendor_ruby/minitest.rb:350:in `on_signal'
/usr/lib/ruby/vendor_ruby/minitest.rb:337:in `with_info_handler'
/usr/lib/ruby/vendor_ruby/minitest.rb:309:in `run'
/usr/lib/ruby/vendor_ruby/minitest.rb:159:in `block in __run'
/usr/lib/ruby/vendor_ruby/minitest.rb:159:in `map'
/usr/lib/ruby/vendor_ruby/minitest.rb:159:in `__run'
/usr/lib/ruby/vendor_ruby/minitest.rb:136:in `run'
/usr/lib/ruby/vendor_ruby/minitest.rb:63:in `block in autorun'

98 runs, 481 assertions, 0 failures, 1 errors, 0 skips
rake aborted!
Command failed with status (1): [ruby -w -I"test"  
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" 
"test/test_css_parser_basic.rb" "test/test_css_parser_loading.rb" 
"test/test_css_parser_media_types.rb" "test/test_css_parser_misc.rb" 
"test/test_css_parser_offset_capture.rb" "test/test_css_parser_regexps.rb" 
"test/test_helper.rb" "test/test_merging.rb" "test/test_rule_set.rb" 
"test/test_rule_set_creating_shorthand.rb" 
"test/test_rule_set_expanding_shorthand.rb" -v]

Tasks: TOP => default
(See full trace by running task with --trace)
ERROR: Test "ruby2.3" failed. Exiting.
dh_auto_install: dh_ruby --install 
/build/1st/ruby-css-parser-1.5.0.pre2/debian/ruby-css-parser returned exit code 
1
debian/rules:6: recipe for target 'binary' failed
make: *** [binary] Error 1

Bug#872298: marked as pending

[Emilio Pozuelo Monfort]

tag 872298 pending
thanks

Hello,

Bug #872298 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:


https://anonscm.debian.org/cgit/pkg-freedesktop/poppler.git/commit/?id=d15de18

---
commit d15de18af31ae3804a2bf4b51cc4002e44cdd00b
Author: Emilio Pozuelo Monfort 
Date:   Tue Aug 29 18:42:38 2017 +0200

debian/copyright: Add missing copyright holders

diff --git a/debian/changelog b/debian/changelog
index 2c25ce5..3088642 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+poppler (0.57.0-2) UNRELEASED; urgency=medium
+
+  * debian/copyright: Add missing copyright holders. Closes: #872298.
+
+ -- Emilio Pozuelo Monfort   Tue, 29 Aug 2017 18:38:26 +0200
+
 poppler (0.57.0-1) experimental; urgency=medium
 
   [ Pino Toscano ]

Processed: Bug#872298 marked as pending

[Debian Bug Tracking System]

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

> tag 872298 pending
Bug #872298 [src:poppler] poppler: Incomplete debian/copyright?
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#853319: [Aspectc-developers] Fwd: Bug#853319: aspectc++: ftbfs with GCC-7

[Olaf Spinczyk]

Hi Reinhard!

We should definitely look into these three problems within the next few
weeks, but I don't regard them as very critical, because they affect
only special use cases: Advice for user-defined "operator new"
implementations and the code generation for get/set advice, which is a
feature that is only enabled with --data_joinpoints and still a bit
experimental.

How to proceed? Can we/you live with these problems for now and update
later or is there no update option and we have to fix it sooner?

Cheers,

Olaf

On 08/24/2017 00:16, Reinhard Tartler wrote:
> 
> 
> On 08/23/2017 12:07 PM, Olaf Spinczyk wrote:
>> Hi!
>>
>> You can generate the config file easily with ag++ --gen_config. Sorry
>> for the inconvenience. The background is that when I wrote the first
>> ac++ tests, I did not want the makefile to depend on ag++.
>>
>> We should change that sooner or later, because it is obviously confusing.
> 
> Not a problem.
> 
> Progress! With a "correct" PUMA CONFIG, I now get further, but there seem to 
> be
> genuine test failures. Are they concerning or shall I ignore them for the 
> debian
> package?
> 
> They look like this:
> 
> /usr/bin/make -C tests -s  all
> make[2]: Entering directory
> '/build/aspectc++-rCVJRW/aspectc++-2.2+git20170823/AspectC++/tests'
> ...[C:ExecAdviceNewDelete].[D:Bug574]...[C:Bug598]
> 
> 
> +-+
> |ERRORS:  |
> +-+
> 
> -
> TEST: ExecAdviceNewDelete
> -
> STDOUT:
> 
> make[3]: Entering directory
> '/build/aspectc++-rCVJRW/aspectc++-2.2+git20170823/AspectC++/tests/ExecAdviceNewDelete'
> Weaving main.cc
> * Running ac++ 2.2
> * Handling Translation Unit `main.cc'.
>   - Path "main.cc"
>   - Parsing ...
>   - Weaving Aspects Forward Declarations ...
>   - Inserting namespace AC
>   - Committing
>   - Preparing introductions ...
>   - Parsing again ...
>   - Weaving access control bypass classes ...
>   - Weaving Join Points ...
> Advicecode manipulation
> Collecting Advice
>   Setting up thisJoinPoint for aspectof
> Create pointcut expression tree
> Matching joinpoints
> Aspect ordering ...
> Creating project repository 'repo.acp'
> Type Check Functions
> Access Join Points
> Execution Join Points
>   void *operator new(unsigned long int)
>   void *operator new[](unsigned long int)
>   void operator delete(void *)
>   void operator delete[](void *)
>   void A::operator delete(void *)
>   void *C::operator new(unsigned long int)
>   void C::operator delete(void *)
> Construction Join Points
> Destruction Join Points
>   - Aspect Includes ...
>   - Final cleanup
>   - Committing
> * Inserting unit pro- and epilogues
>   - Manipulating translation unit file main.cc
> * Updating #line directives of generated code fragments
> * Saving
>   - Expanding project includes
>   - Fixing #line directives
>   - Path "main.acc"
> * Done
> Compiling main.acc
> ../Makefile.generic:80: recipe for target 'Junk/main.o' failed
> make[3]: Leaving directory
> '/build/aspectc++-rCVJRW/aspectc++-2.2+git20170823/AspectC++/tests/ExecAdviceNewDelete'
> 
> STDERR:
> 
> main.cc:5:30: warning: dynamic exception specifications are deprecated in 
> C++11
> [-Wdeprecated]
>  void *operator new (size_t ) throw(std::bad_alloc);
>   ^
> main.cc:7:31: warning: dynamic exception specifications are deprecated in 
> C++11
> [-Wdeprecated]
>  void *operator new (size_t s) throw(std::bad_alloc) {
>^
> main.cc: In function 'void* operator new(size_t)':
> main.cc:7:7: error: declaration of 'void* operator new(size_t) throw
> (std::bad_alloc)' has a different exception specifier
>  void *operator new (size_t s) throw(std::bad_alloc) {
>^~~~
> main.cc:5:7: note: from previous declaration 'void* operator new(std::size_t)'
>  void *operator new (size_t ) throw(std::bad_alloc);
>^~~~
> main.acc: In function 'void* operator new(std::size_t)':
> main.acc:147:61: warning: dynamic exception specifications are deprecated in
> C++11 [-Wdeprecated]
>typedef TJP__Znwm_0< void *, void, void, void *(::size_t)
> throw(std::bad_alloc),  AC::TL< ::size_t, AC::TLE > > __TJP;
>  ^
> main.cc: At global scope:
> main.cc:11:33: warning: dynamic exception specifications are deprecated in 
> C++11
> [-Wdeprecated]
>  void *operator new[] (size_t s) throw(std::bad_alloc) {
>  ^
> main.acc: In function 'void* operator new [](std::size_t)':
> main.acc:198:61: warning: dynamic exception specifications are deprecated in
> C++11 [-Wdeprecated]
>typedef TJP__Znam_0< 

Bug#873626: pyx3 binary-all FTBFS: rm: cannot remove '/<>/debian/tmp/usr/lib/python*/*-packages/output': No such file or directory

[Adrian Bunk]

Source: pyx3
Version: 0.14.1-6
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=pyx3=all=0.14.1-6=1504014753=0

...
running install_egg_info
Writing 
/<>/debian/tmp/usr/lib/python3.5/dist-packages/PyX-0.14.1.egg-info
rm 
/<>/debian/tmp/usr/lib/python*/*-packages/pyx/data/lfs/createlfs.*
rm /<>/debian/tmp/usr/lib/python*/*-packages/output
rm: cannot remove 
'/<>/debian/tmp/usr/lib/python*/*-packages/output': No such file 
or directory
debian/rules:32: recipe for target 'override_dh_auto_install' failed
make[1]: *** [override_dh_auto_install] Error 1

Bug#870312: marked as done (flatpak FTBFS on amd64/arm64: ERROR: testlibrary - missing test plan)

[Debian Bug Tracking System]

Your message dated Tue, 29 Aug 2017 18:53:23 +0300
with message-id <20170829155323.zumev64sfxnoetzw@localhost>
and subject line Re: Bug#870312: flatpak FTBFS on amd64/arm64: ERROR: 
testlibrary - missing test plan
has caused the Debian Bug report #870312,
regarding flatpak FTBFS on amd64/arm64: ERROR: testlibrary - missing test plan
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.)


-- 
870312: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870312
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: flatpak
Version: 0.8.7-4
Severity: serious

Some recent change in unstable makes flatpak FTBFS on amd64/arm64:

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

...
ERROR: testlibrary - missing test plan
ERROR: testlibrary - exited with status 134 (terminated by signal 6?)
=
   Flatpak 0.8.7: ./test-suite.log
=

# TOTAL: 20
# PASS:  6
# SKIP:  12
# XFAIL: 0
# FAIL:  0
# XPASS: 0
# ERROR: 2

.. contents:: :depth: 2

SKIP: test-doc-portal
=

# random seed: R02S2d187e435d4aa4fb68938109e0122c30
1..2
# Start of db tests
ok 1 /db/create_doc # SKIP this test requires FUSE
SKIP: test-doc-portal 1 /db/create_doc # SKIP this test requires FUSE
ok 2 /db/recursive_doc # SKIP this test requires FUSE
SKIP: test-doc-portal 2 /db/recursive_doc # SKIP this test requires FUSE
# End of db tests

ERROR: testlibrary
==

**
flatpak:ERROR:tests/testlibrary.c:668:add_remote: assertion failed (status == 
0): (256 == 0)
./buildutil/tap-test: line 23: 59830 Aborted ${srcd}/${bn} -k 
--tap
# random seed: R02Sbf4ab0218f9346d8617da03c0d7234c9
# flatpak:ERROR:tests/testlibrary.c:668:add_remote: assertion failed (status == 
0): (256 == 0)
ERROR: testlibrary - missing test plan
ERROR: testlibrary - exited with status 134 (terminated by signal 6?)
...
--- End Message ---
--- Begin Message ---
Version: 0.9.7-1

On Tue, Aug 29, 2017 at 03:05:34PM +0100, Simon McVittie wrote:
> On Tue, 01 Aug 2017 at 00:38:58 +0300, Adrian Bunk wrote:
> > Some recent change in unstable makes flatpak FTBFS on amd64/arm64:
> > 
> > https://tests.reproducible-builds.org/debian/history/flatpak.html
> > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/flatpak.html
> 
> I can't reproduce this in my local sbuild, but it's still happening on
> the reproducible-builds infrastructure. It might be related to the use
> of pbuilder on reproducible-builds?
> 
> Have you reproduced this yourself, or are you reporting it purely based on
> what you see on reproducible-builds.org?

I actually tried a rebuild in a chroot before reporting in this case, 
but that failed even earlier:
 flatpak:ERROR:tests/testlibrary.c:550:make_test_runtime: assertion failed 
(status == 0): (256 == 0)

> > # random seed: R02Sbf4ab0218f9346d8617da03c0d7234c9
> > # flatpak:ERROR:tests/testlibrary.c:668:add_remote: assertion failed 
> > (status == 0): (256 == 0)
> 
> This is status from:
> 
>   g_spawn_sync (NULL, (char **)argv, NULL, flags, NULL, NULL, NULL, NULL, 
> , );
> 
> where argv is { "flatpak", "remote-add", ... } and error indicates that
> g_spawn_sync() did not immediately fail (therefore status is a waitpid()
> result). Applying WIFEXITED() and WEXISTATUS() indicates that
> "flatpak remote-add ..." exited 1.
> 
> The next step is to make this fail in an environment where g_test_verbose()
> would return true (or patch out that check), so that we see flatpak's stderr.
> I'm not entirely sure why upstream suppressed its stderr here.

The version in experimental is fine, so there's not much point in 
spending time debugging here.

I actually wonder why I didn't close it with that version when reporting,
doing it now.

Technically this will still be an RC bug in flatpak in unstable,
but since flatpak is a key package it won't trigger autoremoval
and everything will be fine once flatpak 0.9/1.0 enters unstable.

> S

cu
Adrian


-- 

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

Processed: Re: virtualbox-dkms: Installation hangs running depmod...

[Debian Bug Tracking System]

Processing control commands:

> tag -1 unreproducible
Bug #873142 [src:linux] virtualbox-dkms: Installation hangs running depmod...
Added tag(s) unreproducible.
> severity -1 important
Bug #873142 [src:linux] virtualbox-dkms: Installation hangs running depmod...
Severity set to 'important' from 'critical'

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

Bug#873142: virtualbox-dkms: Installation hangs running depmod...

[Ben Hutchings]

Control: tag -1 unreproducible
Control: severity -1 important

On Thu, 24 Aug 2017 13:00:34 -0700 Ivan Kohler  wrote:
> Package: virtualbox-dkms
> Version: 5.1.24-dfsg-2
> Severity: critical
> Justification: breaks the whole system
> 
> Installation hangs running "depmod..." and printing a period every few 
> seconds.
> 
> ps shows the command being run is:
>   depmod -a 4.11.0-1-amd64 -F /boot/System.map-4.11.0-1-amd64
> 
> It has been running for over 25 minutes now, but does not appear to be using
> any CPU or resources.
> 
> Ctrl-C does not stop the installation process.  Sending a kill signal to the
> depmod process does not have any effect.

I can't reproduce this.  I tried with both:

- linux-image-4.12.0-1-amd64 installed and running,
  linux-headers-4.12.0-1-amd64 installed
- linux-image-4.11.0-2-amd64 installed and running (as in your report),
  linux-headers-4.11.0-1-amd64 installed (as in your report)

Ben.

-- 
Ben Hutchings
Teamwork is essential - it allows you to blame someone else.



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

Bug#873623: sudo: occasionally stalls infinitely instead of running command

[Thorsten Glaser]

Package: sudo
Version: 1.8.21-1
Severity: grave
Justification: renders package unusable

After an upgrade from 1.8.20p2-1 sudo became somewhat unusable:

[…]
Processing triggers for menu (2.1.47) ...
[master 2a7cfae] committing changes in /etc after apt run
 9 files changed, 20 insertions(+), 8 deletions(-)
 rename rc0.d/{K01avahi-daemon => K02avahi-daemon} (100%)
 rename rc1.d/{K01avahi-daemon => K02avahi-daemon} (100%)
 rename rc6.d/{K01avahi-daemon => K02avahi-daemon} (100%)
sudo: obsolete-conffile /etc/sudoers.dist
N: Download is performed unsandboxed as root as file 
'/home/tglase/Projekte/DebTarent/dists/sid/wtf/Pkgs/mksh/mksh_56b+wtf1_x32.deb' 
couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)
tglase@tglase:~ $ sudo rm /etc/sudoers.dist
[sudo] password for tglase:
^Ctglase@tglase:~ $ sudo -K
tglase@tglase:~ $ sudo rm /etc/sudoers.dist
[sudo] password for tglase:
rm: cannot remove '/etc/sudoers.dist': No such file or directory
1|tglase@tglase:~ $ sudo true
tglase@tglase:~ $ sudo ls
Bilder  Lesen Ulibxml2_2.7.8.dfsg-2+squeeze16.diff.gz  licenses  
sirc.log  uw-imap  y
GPX Projekte  UU   libxml2_2.7.8.dfsg-2+squeeze16.dsc  mail  stuff  
   x
KanaTODO  UUU  libxml2_2.7.8.dfsg.orig.tar.gz  mbsd  tmp
   x-git
tglase@tglase:~ $ sudo true
tglase@tglase:~ $ sudo true
tglase@tglase:~ $ sudo true
tglase@tglase:~ $ sudo true
tglase@tglase:~ $ sudo true
^[[A
^Ctglase@tglase:~ $ 

Basically, sometimes, it doesn’t come back from the command
(confirmed by running “sudo ls” a couple of times in succession)
making it unreliable and impossible to use from a script.

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

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

Versions of packages sudo depends on:
ii  libaudit1   1:2.7.7-1+b2
ii  libc6   2.24-17
ii  libpam-modules  1.1.8-3.6
ii  libpam0g1.1.8-3.6
ii  libselinux1 2.6-3+b2
ii  lsb-base9.20170808

sudo recommends no packages.

sudo suggests no packages.

-- Configuration Files:
/etc/sudoers [Errno 13] Permission denied: '/etc/sudoers'
/etc/sudoers.d/README [Errno 13] Permission denied: '/etc/sudoers.d/README'
/etc/sudoers.dist [Errno 2] No such file or directory: '/etc/sudoers.dist'

-- no debconf information

Bug#872079: marked as done (libwine32 will not install)

[Debian Bug Tracking System]

Your message dated Tue, 29 Aug 2017 17:36:34 +0200
with message-id 
and subject line Re: Bug#872079: libwine32 will not install
has caused the Debian Bug report #872079,
regarding libwine32 will not install
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.)


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

Dear Maintainer,

When I try to install wine32:i386 on an amd64 system it fails saying that
libwine32:i386 is not going to be installed.  The same applies to
wine32-development.

I think the problem is actually at a much lower level and may be to do with
gcc-7 becoming the default, as lower down the dependency list it complains
about libstdc++6:i386 not being installable.  Either gcc-7 is missing
something, or wine32 needs rebuilding.

David



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

Kernel: Linux 4.11.0-2-amd64 (SMP w/8 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: sysvinit (via /sbin/init)
--- End Message ---
--- Begin Message ---
On 08/27/2017 01:36 PM, David Goodenough wrote:
> On Sunday, 27 August 2017 13:16:25 BST Antoine wrote:
>> libc6:i386 and libc6:amd64 are now installable in the same 
> version on
>> Debian Sid.
>>
>> Can you please try again to install libwine32 and tell us if you 
> still
>> get issues?
> It now installs, thank you.

Closing.  Thanks everyone.--- End Message ---

Bug#871065: marked as done (likwid: FTBFS: cc1: error: -Wformat-security ignored without -Wformat [-Werror=format-security])

[Debian Bug Tracking System]

Your message dated Tue, 29 Aug 2017 15:18:15 +
with message-id 
and subject line Bug#871065: fixed in likwid 4.2.1+dfsg1-1
has caused the Debian Bug report #871065,
regarding likwid: FTBFS: cc1: error: -Wformat-security ignored without -Wformat 
[-Werror=format-security]
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.)


-- 
871065: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871065
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: likwid
Version: 4.2.0-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 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):
> gcc -c  -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -O2 -std=c99 -Wno-format -fPIC -fPIC 
> -fvisibility=hidden  -Wdate-time -D_FORTIFY_SOURCE=2 -DPAGE_ALIGNMENT=4096 
> -DLIKWID_MONITOR_LOCK -DDEBUGLEV=0 -DVERSION=4 -DRELEASE=2 
> -DCFGFILE=/etc/likwid.cfg -DTOPOFILE=/etc/likwid_topo.cfg 
> -DINSTALL_PREFIX=/usr -DMAX_NUM_THREADS=263 -DMAX_NUM_NODES=64 
> -DACCESSDAEMON=/usr/sbin/likwid-accessD 
> -DGROUPPATH=/usr/share/likwid/perfgroups -DLIKWIDLOCK=/var/run/likwid.lock 
> -DLIKWIDSOCKETBASE=/tmp/likwid   -D_GNU_SOURCE -DCOLOR=BLUE -DHAS_MEMPOLICY 
> -DHAS_SCHEDAFFINITY -DLIKWID_USE_HWLOC -DACCESSMODE=1  -I./src/includes 
> -I/usr/include/lua5.2 -Iext/hwloc/include -I./GCC ./src/calculator.c -o 
> GCC/calculator.o
> cc1: error: -Wformat-security ignored without -Wformat 
> [-Werror=format-security]
> cc1: some warnings being treated as errors
> Makefile:189: recipe for target 'GCC/calculator.o' failed
> make[2]: *** [GCC/calculator.o] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2017/08/05/likwid_4.2.0-2_unstable.log

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

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: likwid
Source-Version: 4.2.1+dfsg1-1

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

Debian distribution maintenance software
pp.
Christoph Martin  (supplier of updated likwid 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: Tue, 29 Aug 2017 16:04:55 +0200
Source: likwid
Binary: likwid
Architecture: source amd64
Version: 4.2.1+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Christoph Martin 
Changed-By: Christoph Martin 
Description:
 likwid - toolsuite for performance oriented programmers
Closes: 871065
Changes:
 likwid (4.2.1+dfsg1-1) unstable; urgency=medium
 .
   * New upstream version 4.2.1+dfsg1
   * remove -Wno-format (closes: #871065)
Checksums-Sha1:
 ca78d2303f79a6e2b9fccd0691465c5672ab05d0 1935 likwid_4.2.1+dfsg1-1.dsc
 8d440721e5beff5013efa893f18a3834db8642ea 1280159 likwid_4.2.1+dfsg1.orig.tar.gz
 93de5404058621e46d8628df3daea7e10d230da6 53936 
likwid_4.2.1+dfsg1-1.debian.tar.xz
 b47ee8c5157a882db5512c9cd030a0b7315db50d 698778 
likwid-dbgsym_4.2.1+dfsg1-1_amd64.deb
 12320f60e9f533aa7859a0de348295ce9f79844a 6678 
likwid_4.2.1+dfsg1-1_amd64.buildinfo
 74ba101b7dad5f7be07c675514ba53277ad8dea4 654914 likwid_4.2.1+dfsg1-1_amd64.deb
Checksums-Sha256:
 09f9c477d4a766414522838c9b6e9209730e6e0c700cd022abcaaa3b4b36fdb2 1935 
likwid_4.2.1+dfsg1-1.dsc
 b1a796fc48140903edf7a5be23a1a31ba8ebde85bf5824126ad992d9085cdd01 1280159 
likwid_4.2.1+dfsg1.orig.tar.gz
 19f468228fd2954b5e5d6453915e56c9ff3fde27d49fa88ba5789b66aa807a31 53936 
likwid_4.2.1+dfsg1-1.debian.tar.xz
 278d35ee97c35d2168b13d165875acb6988721b311c5333775e95f41b3f47643 698778 
likwid-dbgsym_4.2.1+dfsg1-1_amd64.deb
 

Processed: found 872378 in 1.05-1

[Debian Bug Tracking System]

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

> found 872378 1.05-1
Bug #872378 [fenrir] fenrir.deb: No speech after enabling fenrir to start in 
concial.
Marked as found in versions fenrir/1.05-1.
> thanks
Stopping processing here.

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

Bug#871185: marked as done (ibus-kkc: FTBFS with vala 0.36)

[Debian Bug Tracking System]

Your message dated Tue, 29 Aug 2017 15:09:43 +
with message-id 
and subject line Bug#871185: fixed in ibus-kkc 1.5.22-1
has caused the Debian Bug report #871185,
regarding ibus-kkc: FTBFS with vala 0.36
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.)


-- 
871185: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871185
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ibus-kkc
Version: 1.5.21-1
Severity: important
User: pkg-vala-maintain...@lists.alioth.debian.org
Usertags: vala-0.36
Tags: buster sid patch

ibus-kkc fails to build from source with vala 0.36 which is currently
in experimental and will be uploaded to unstable soon.

I am attaching a patch to fix this issue (in my next email).

On behalf of the Debian Vala maintainers,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: ibus-kkc
Source-Version: 1.5.22-1

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

Debian distribution maintenance software
pp.
Mitsuya Shibata  (supplier of updated ibus-kkc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 13 Aug 2017 19:45:11 +0900
Source: ibus-kkc
Binary: ibus-kkc ibus-kkc-dbg
Architecture: source
Version: 1.5.22-1
Distribution: unstable
Urgency: medium
Maintainer: IME Packaging Team 
Changed-By: Mitsuya Shibata 
Description:
 ibus-kkc   - Japanese Kana Kanji input engine for IBus
 ibus-kkc-dbg - Japanese Kana Kanji input engine for IBus - debugging symbols
Closes: 871185
Changes:
 ibus-kkc (1.5.22-1) unstable; urgency=medium
 .
   [ Mitsuya Shibata ]
   * debian/control,watch: switch to new upstream site
   * New upstream version 1.5.22
 * Migrated to Gtk widget template (thus, it requires gtk+-3.0 >= 3.12)
 * IBus 1.4 is no longer supported
   * Refresh debian/patches
   * debian/control: Require gtk+-3.0 >= 3.10 for widget template
   * debian/control: exec autogen.sh instead of autoreconf
   * debian/copyright: update copyright information for new release
   * Bump Standards-Version to 4.0.0
   * debian/control: fix lintian vcs-field-uses-insecure-uri
 .
   [ Jeremy Bicha ]
   * Fix build with vala 0.36 (Closes: #871185)
Checksums-Sha1:
 1c24a91a89ee6ec2246a9d0c04ce5d7a79b7a7f1 2095 ibus-kkc_1.5.22-1.dsc
 fef5505f25564ca802669e832c096f7fefc8d12e 54584 ibus-kkc_1.5.22.orig.tar.gz
 ea41a2dc0f34b7226795d85a7a9049f9b57245ea 4368 ibus-kkc_1.5.22-1.debian.tar.xz
 61c1971ede62900ef5ea189e06f96177cc870f2d 15659 
ibus-kkc_1.5.22-1_source.buildinfo
Checksums-Sha256:
 e4ae39b8ce15269715344362f6ed7d7b5d00f28e76fbf27d78dc3919794184b4 2095 
ibus-kkc_1.5.22-1.dsc
 f60bd7741509c0393eff552f0c933db163b70bbc3624a331014f4c50e2f33de6 54584 
ibus-kkc_1.5.22.orig.tar.gz
 68b93408eb5b4da8036a5874ee4a933934ab09b3c440fefa34ab68af0a16100f 4368 
ibus-kkc_1.5.22-1.debian.tar.xz
 f898baeb21988a41a05ff8f8ffc0de474b5f8b6aa6c5a4e96ae0c0928ba804e0 15659 
ibus-kkc_1.5.22-1_source.buildinfo
Files:
 abb7a0de682e69572f28f6002b109d98 2095 utils extra ibus-kkc_1.5.22-1.dsc
 9a6917e404aa6212678e554445e734c6 54584 utils extra ibus-kkc_1.5.22.orig.tar.gz
 d195f0f7f0f32677b06097e482941ed2 4368 utils extra 
ibus-kkc_1.5.22-1.debian.tar.xz
 6fbc2963eb5ea8468b18cbc850bf1b8f 15659 utils extra 
ibus-kkc_1.5.22-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJZpXTaAAoJEOZsd1rr/mx9auwP/0nnbJ2JlJcOratg2Sil4JIt
2EXAyV+AEn5urobooSOLnZcHMfeWKXZBXHNPIxd+JgXyFGQ+zhQsSm/QufVBsGBh
t491ZEVjpFTPjc8Xe1ApD7SdCeTslD6C3aV977m5oEa+PnQuyMFr23u3zxy0VFgB
4t6SEcFVp9TYZaejurdJ2CfLHbCu1Ztkuyly6zAkFIJ/6CHDA/38RAb23W/Mo6mS
TB5c47p3fYj1r298IPmjno+syA5D1L6p7Q+uwvZaWFn7LYg7UccIZSG1DFX2V+Kn
ZtVLpUqYHTpLAEiO1Sw91zYRcqja6PAqwyLyBvxqzeMQcKPqknTfkR/dX/R/vsxj
OrOCS9KCkUVpIzO4ES2MI55jZXR1WvAuaFR1ZRn2JRL1GCAYoTaqahv9ltXbvJm/
qu9jP8F2bN9m8q8iwlcDsCaF6rG1wQZpjl5cBsULy94X7aW6EIhfdVRoF6ymPo6/
6SBNAIapg2iaGALD3nLsKiPtNCJVWQRL/j3+jLZsFGR8tJ+qWG2sOjAqP05HelC8
PWSh3Q+kYilu/tCjTGT3Ew6I/fDM4Zv2lmSIXve5HeNGt9BE/G/LKj01i8+HcZRa

Bug#872378: fenrir.deb: No speech after enabling fenrir to start inconcial.

[Matthew Dyer]

Hi,


Downgrading still gives me no speech.  I have speech with orca how 
ever.  Espeakup also works though not at the same time.  I have espeakup 
disabled at the moment.



Matthew




On 08/28/2017 02:38 PM, Paul Gevers wrote:

Hi Matthew

On 28-08-17 15:06, Matthew Dyer wrote:

Could you try to downgrade to version 1.05-1 so as to check whether it's
only version 1.06-1 which has the issue?

Anyhow,  went trying to downgrade, I got the
package not found erroor.  Am I doing something wrong?  I did sudo
apt-get install fenrir 1.05.

Yes, the invocation is (at least I am pretty sure):
sudo apt-get install fenrir=1.05-1
or
sudo apt-get install -t testing fenrir

Both commands require that you have both unstable (sid) and testing
(buster) in your apt/source.list. If you don't have that and don't want
to change it, you could download¹ the fenrir deb package and install it with
dpkg -i path/to/fenrir.deb

Paul
¹ https://packages.debian.org/buster/all/fenrir/download



___
Pkg-a11y-devel mailing list
pkg-a11y-de...@lists.alioth.debian.org
https://lists.alioth.debian.org/mailman/listinfo/pkg-a11y-devel

Bug#873619: template-glib: debian/copyright references online source without quote

[Jeremy Bicha]

Control: severity -1 important

On Tue, Aug 29, 2017 at 10:15 AM, Chris Lamb  wrote:
> Source: template-glib
> Version: 3.25.3-1
> Severity: serious
> Justication: Policy 12.5
> X-Debbugs-CC: Jeremy Bicha 
>
> Hi,
>
> I just ACCEPTed template-glib from NEW but noticed it uses an URL
> as a source:
>
> Comment: A few files were incorrectly marked as GPL-3+
>  but those have been relicensed to LGPL-2.1+ by their author here:
>  https://git.gnome.org/browse/template-glib/commit/?id=6f6bd5
>
> It's great its been licensed correctly but referring to a URL requires
> that our users must be online to check the copyright (think of the
> Desert Island Test!), the site never changes, the URL does not go stale,
> etc. etc.
>
> Please additionally quote the relevant section of the page you are
> link.

The commit message on the linked URL is "use LGPLv2.1+ consistently"
and the author is "Christian Hergert " . I think
debian/copyright already effectively includes that information.

I am lowering the importance of this bug since I don't feel 12.5 is
quite so precise as you're presenting it. This will be fixed by
September with 3.26.0 any way.

Thanks,
Jeremy Bicha

Bug#784468: goldendict: Qt4 WebKit removal: raising severity to serious

[Boyuan Yang]

Hi,

I am more than willing to package new snapshots with Qt5 for goldendict 
package so that the problem of Qt4 removal can be resolved.

Please let me know if it is okay to "hijack" your package and push a new 
snapshot, or if an NMU is preferred.

Thanks,
Boyuan Yang

Processed: Re: Bug#873619: template-glib: debian/copyright references online source without quote

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #873619 [src:template-glib] template-glib: debian/copyright references 
online source without quote
Warning: Unknown package 'src:template-glib'
Severity set to 'important' from 'serious'
Warning: Unknown package 'src:template-glib'

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

Bug#873619: template-glib: debian/copyright references online source without quote

[Chris Lamb]

Source: template-glib
Version: 3.25.3-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Jeremy Bicha 

Hi,

I just ACCEPTed template-glib from NEW but noticed it uses an URL
as a source:

Comment: A few files were incorrectly marked as GPL-3+
 but those have been relicensed to LGPL-2.1+ by their author here:
 https://git.gnome.org/browse/template-glib/commit/?id=6f6bd5

It's great its been licensed correctly but referring to a URL requires
that our users must be online to check the copyright (think of the
Desert Island Test!), the site never changes, the URL does not go stale,
etc. etc.

Please additionally quote the relevant section of the page you are
link.


Regards,

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

Bug#873616: libdazzle: Incomplete debian/copyright?

[Chris Lamb]

Source: libdazzle
Version: 3.25.5-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Jeremy Bicha 

Hi,

I just ACCEPTed libdazzle from NEW but noticed it was missing 
attribution in debian/copyright for at least Garrett Regier,
Async Open Source, James Henstridge etc etc.

(This is not exhaustive so please check over the entire package 
carefully and address these on your next upload.)


Regards,

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

Bug#870312: flatpak FTBFS on amd64/arm64: ERROR: testlibrary - missing test plan

[Simon McVittie]

On Tue, 01 Aug 2017 at 00:38:58 +0300, Adrian Bunk wrote:
> Some recent change in unstable makes flatpak FTBFS on amd64/arm64:
> 
> https://tests.reproducible-builds.org/debian/history/flatpak.html
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/flatpak.html

I can't reproduce this in my local sbuild, but it's still happening on
the reproducible-builds infrastructure. It might be related to the use
of pbuilder on reproducible-builds?

Have you reproduced this yourself, or are you reporting it purely based on
what you see on reproducible-builds.org?

> # random seed: R02Sbf4ab0218f9346d8617da03c0d7234c9
> # flatpak:ERROR:tests/testlibrary.c:668:add_remote: assertion failed (status 
> == 0): (256 == 0)

This is status from:

  g_spawn_sync (NULL, (char **)argv, NULL, flags, NULL, NULL, NULL, NULL, 
, );

where argv is { "flatpak", "remote-add", ... } and error indicates that
g_spawn_sync() did not immediately fail (therefore status is a waitpid()
result). Applying WIFEXITED() and WEXISTATUS() indicates that
"flatpak remote-add ..." exited 1.

The next step is to make this fail in an environment where g_test_verbose()
would return true (or patch out that check), so that we see flatpak's stderr.
I'm not entirely sure why upstream suppressed its stderr here.

S

Processed: Raising severity of FTBFS bugs since vala 0.36 is in unstable

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #871187 [libkkc] libkkc: FTBFS with vala 0.36
Severity set to 'serious' from 'important'

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

Processed: Raising severity of FTBFS bugs since vala 0.36 is in unstable

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #871186 [src:ibus-skk] ibus-skk: FTBFS with vala 0.36
Severity set to 'serious' from 'important'

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

Bug#873088: Wheezy update of git-annex?

[Raphael Hertzog]

Hello Richard,

First I want to point out that git-annex 6.20170818-1 failed to build on
arm64, you might want to ask for a give-back to retry with a newer
compiler (gcc 7.2 landed in unstable since the failed build on arm64).

Apart from that, the Debian LTS team would like to fix the security issues
which are currently open in the Wheezy version of git-annex:
https://security-tracker.debian.org/tracker/CVE-2017-12976

Would you like to take care of this yourself?

If yes, please follow the workflow we have defined here:
https://wiki.debian.org/LTS/Development

If that workflow is a burden to you, feel free to just prepare an
updated source package and send it to debian-...@lists.debian.org
(via a debdiff, or with an URL pointing to the source package,
or even with a pointer to your packaging repository), and the members
of the LTS team will take care of the rest. Indicate clearly whether you
have tested the updated package or not.

If you don't want to take care of this update, it's not a problem, we
will do our best with your package. Just let us know whether you would
like to review and/or test the updated package before it gets released.

You can also opt-out from receiving future similar emails in your
answer and then the LTS Team will take care of git-annex updates
for the LTS releases.

Thank you very much.

Raphaël Hertzog,
  on behalf of the Debian LTS team.

PS: A member of the LTS team might start working on this update at
any point in time. You can verify whether someone is registered
on this update in this file:
https://anonscm.debian.org/viewvc/secure-testing/data/dla-needed.txt?view=markup
-- 
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/

Processed: Raising severity of FTBFS bugs since vala 0.36 is in unstable

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #871058 [fso-deviced] fso-deviced: FTBFS with vala 0.36
Severity set to 'serious' from 'important'

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

Processed: Raising severity of FTBFS bugs since vala 0.36 is in unstable

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #871185 [src:ibus-kkc] ibus-kkc: FTBFS with vala 0.36
Severity set to 'serious' from 'important'

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

Processed: Raising severity of FTBFS bugs since vala 0.36 is in unstable

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #871119 [fso-gsmd] fso-gsmd: FTBFS with vala 0.36
Severity set to 'serious' from 'important'

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

Bug#873063: marked as done (fcitx-frontend-qt5: Not working with Qt 5.9)

[Debian Bug Tracking System]

Your message dated Tue, 29 Aug 2017 13:35:53 +
with message-id 
and subject line Bug#873063: fixed in fcitx-qt5 1.1.0-1
has caused the Debian Bug report #873063,
regarding fcitx-frontend-qt5: Not working with Qt 5.9
to be marked as done.

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

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


-- 
873063: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873063
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fcitx-frontend-qt5
Version: 1.0.5-1+b1
Severity: serious

Dear Maintainer,

Please rebuild it with Qt 5.9.
Or package the new version 1.1.0.

Thanks

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

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

Versions of packages fcitx-frontend-qt5 depends on:
ii  fcitx-module-dbus  1:4.2.9.1-6
ii  libc6  2.24-15
ii  libfcitx-qt5-1 1.0.5-1+b1
ii  libgcc11:7.2.0-1
ii  libqt5core5a   5.9.1+dfsg-9
ii  libqt5dbus55.9.1+dfsg-9
ii  libqt5gui5 5.9.1+dfsg-9
ii  libstdc++6 7.2.0-1
ii  libxkbcommon0  0.7.1-1

fcitx-frontend-qt5 recommends no packages.

fcitx-frontend-qt5 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: fcitx-qt5
Source-Version: 1.1.0-1

We believe that the bug you reported is fixed in the latest version of
fcitx-qt5, 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.
Shengjing Zhu  (supplier of updated fcitx-qt5 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, 28 Aug 2017 18:15:36 +0800
Source: fcitx-qt5
Binary: fcitx-frontend-qt5 fcitx-libs-qt5 libfcitx-qt5-1 libfcitx-qt5-dev
Architecture: source amd64 all
Version: 1.1.0-1
Distribution: unstable
Urgency: medium
Maintainer: IME Packaging Team 
Changed-By: Shengjing Zhu 
Description:
 fcitx-frontend-qt5 - Free Chinese Input Toy of X - Qt5 IM Module frontend
 fcitx-libs-qt5 - transitional dummy package
 libfcitx-qt5-1 - Free Chinese Input Toy of X - D-Bus client libraries for Qt5
 libfcitx-qt5-dev - Free Chinese Input Toy of X - Devel files for libfcitx-qt5
Closes: 851953 873063
Changes:
 fcitx-qt5 (1.1.0-1) unstable; urgency=medium
 .
   * Team upload
   * Imported Upstream version 1.1.0 (Closes: #873063, #851953)
   * d/watch: change upstream url to github
   * Remove libfcitx-qt5-dbg
   * Update compat, debhelper to 10
   * Change various insecure url to https
   * Use dh_missing --fail-missing instead
   * Install fcitx-qt5-gui-wrapper
   * Bump Standards-Version to 4.1.0
   * Update symbols
Checksums-Sha1:
 7c12901fc33ccd18e7903465c096845c748e7f17 1910 fcitx-qt5_1.1.0-1.dsc
 ad1d443bca4d798dbe968ccc9f165753712bdb8c 55944 fcitx-qt5_1.1.0.orig.tar.xz
 eb12d1d3c7785731063c388c4ae81dcabf90d6aa 4776 fcitx-qt5_1.1.0-1.debian.tar.xz
 73b549ddfc596bd65b15acb581413209713e3433 631408 
fcitx-frontend-qt5-dbgsym_1.1.0-1_amd64.deb
 cbfb165408171c8acd47a50d796dd1c37f66eb69 34038 
fcitx-frontend-qt5_1.1.0-1_amd64.deb
 ed3b9603bf93dd05d06b2245865c52c7cee1efaa 2612 fcitx-libs-qt5_1.1.0-1_all.deb
 f64d2544025db3bb4cd520ed2e8174d015a70a3b 12675 
fcitx-qt5_1.1.0-1_amd64.buildinfo
 654db34db2055fcdb5149e5c6530760f42289d90 1975850 
libfcitx-qt5-1-dbgsym_1.1.0-1_amd64.deb
 17cd35cde9d0141ab7f86117df6828fc29a9c3a3 67982 libfcitx-qt5-1_1.1.0-1_amd64.deb
 b5a379d8aa8243950ce013bde4975d376a517e48 12320 
libfcitx-qt5-dev_1.1.0-1_amd64.deb
Checksums-Sha256:
 c14e39ef44dc0afd7a6b23b0a236a157bad7a30a826d2938ee28260d823f6149 1910 
fcitx-qt5_1.1.0-1.dsc
 9be3205e9bb730a23f28bf742d8c41a5035fcd8d91b51aaef875d888c12c0c65 55944 
fcitx-qt5_1.1.0.orig.tar.xz
 f0d89a9338493436949dbbffb9aeb13f68a788d63b3f17a56f4d947f35c25df6 4776 
fcitx-qt5_1.1.0-1.debian.tar.xz
 

Processed: Better bug title

[Debian Bug Tracking System]

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

> retitle 873608 uhd: NEON-related FTBFS on armhf
Bug #873608 [src:uhd] uhd FTBFS on armhf dues to NEON
Changed Bug title to 'uhd: NEON-related FTBFS on armhf' from 'uhd FTBFS on 
armhf dues to NEON'.
> thanks
Stopping processing here.

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

Bug#873608: uhd FTBFS on armhf dues to NEON

[Adrian Bunk]

Source: uhd
Version: 3.10.2.0-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=uhd=armhf=3.10.2.0-1=1503874671=0

...
In file included from 
/«PKGBUILDDIR»/host/lib/convert/convert_with_neon.cpp:20:0:
/usr/lib/gcc/arm-linux-gnueabihf/7/include/arm_neon.h: In member function 
'virtual void __convert_fc32_1_sc16_item32_le_1_PRIORITY_SIMD::operator()(const 
input_type&, const output_type&, size_t)':
/usr/lib/gcc/arm-linux-gnueabihf/7/include/arm_neon.h:6740:1: error: inlining 
failed in call to always_inline 'float32x4_t vdupq_n_f32(float32_t)': target 
specific option mismatch
 vdupq_n_f32 (float32_t __a)
 ^~~
/«PKGBUILDDIR»/host/lib/convert/convert_with_neon.cpp:36:53: note: called from 
here
 float32x4_t Q0 = vdupq_n_f32(float(scale_factor));
 ^
In file included from 
/«PKGBUILDDIR»/host/lib/convert/convert_with_neon.cpp:20:0:
/usr/lib/gcc/arm-linux-gnueabihf/7/include/arm_neon.h:10844:1: error: inlining 
failed in call to always_inline 'void vst1_s16(int16_t*, int16x4_t)': target 
specific option mismatch
 vst1_s16 (int16_t * __a, int16x4_t __b)
 ^~~~
/«PKGBUILDDIR»/host/lib/convert/convert_with_neon.cpp:65:17: note: called from 
here
 vst1_s16((reinterpret_cast([i+6])), D15);
 ^~
In file included from 
/«PKGBUILDDIR»/host/lib/convert/convert_with_neon.cpp:20:0:
/usr/lib/gcc/arm-linux-gnueabihf/7/include/arm_neon.h:9027:1: error: inlining 
failed in call to always_inline 'int16x4_t vrev32_s16(int16x4_t)': target 
specific option mismatch
 vrev32_s16 (int16x4_t __a)
 ^~
/«PKGBUILDDIR»/host/lib/convert/convert_with_neon.cpp:64:39: note: called from 
here
 int16x4_t D15 = vrev32_s16(D14);
   ^
In file included from 
/«PKGBUILDDIR»/host/lib/convert/convert_with_neon.cpp:20:0:
/usr/lib/gcc/arm-linux-gnueabihf/7/include/arm_neon.h:7552:1: error: inlining 
failed in call to always_inline 'int16x4_t vmovn_s32(int32x4_t)': target 
specific option mismatch
 vmovn_s32 (int32x4_t __a)
 ^
/«PKGBUILDDIR»/host/lib/convert/convert_with_neon.cpp:63:38: note: called from 
here
 int16x4_t D14 = vmovn_s32(Q13);
  ^
...



NEON is not part of the armhf port baseline.

Processed: pd-xsample was never built on ppc64el

[Debian Bug Tracking System]

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

> severity 873602 important
Bug #873602 [pd-xsample] pd-xsample FTBFS on ppc64el: UInt32 does not name a 
type
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Processed: yabause: diff for NMU version 0.9.14-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 870304 + patch
Bug #870304 [src:yabause] yabause FTBFS with buster libgtkglext1-dev
Added tag(s) patch.
> tags 870304 + pending
Bug #870304 [src:yabause] yabause FTBFS with buster libgtkglext1-dev
Added tag(s) pending.

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

Bug#870304: yabause: diff for NMU version 0.9.14-2.1

[Adrian Bunk]

Control: tags 870304 + patch
Control: tags 870304 + pending

Dear maintainer,

I've prepared an NMU for yabause (versioned as 0.9.14-2.1) and uploaded 
it to DELAYED/10. Please feel free to tell me if I should cancel it.

cu
Adrian

-- 

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

diff -Nru yabause-0.9.14/debian/changelog yabause-0.9.14/debian/changelog
--- yabause-0.9.14/debian/changelog	2016-10-29 10:53:24.0 +0300
+++ yabause-0.9.14/debian/changelog	2017-08-29 15:49:16.0 +0300
@@ -1,3 +1,11 @@
+yabause (0.9.14-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Search for gdkglext-config.h in the new location.
+(Closes: #870304)
+
+ -- Adrian Bunk   Tue, 29 Aug 2017 15:49:16 +0300
+
 yabause (0.9.14-2) unstable; urgency=medium
 
   * Build without dynarec, as this fails with PIE.
diff -Nru yabause-0.9.14/debian/patches/gtkglext-patch.patch yabause-0.9.14/debian/patches/gtkglext-patch.patch
--- yabause-0.9.14/debian/patches/gtkglext-patch.patch	1970-01-01 02:00:00.0 +0200
+++ yabause-0.9.14/debian/patches/gtkglext-patch.patch	2017-08-29 15:49:10.0 +0300
@@ -0,0 +1,15 @@
+Description: Search for gdkglext-config.h in the new location
+Author: Adrian Bunk 
+Bug-Debian: https://bugs.debian.org/870304
+
+--- yabause-0.9.14.orig/src/gtk/CMakeLists.txt
 yabause-0.9.14/src/gtk/CMakeLists.txt
+@@ -12,7 +12,7 @@ set(PORT_INCLUDE_DIRS ${GTK2_INCLUDE_DIR
+ set(PORT_LIBRARIES ${GTK2_LIBRARIES})
+ 
+ if (OPENGL_FOUND)
+-	find_path(GDKGLEXT_CONFIG_INCLUDE_DIR gdkglext-config.h PATHS ${CMAKE_SYSTEM_PREFIX_PATH} PATH_SUFFIXES lib/gtkglext-1.0/include)
++	find_path(GDKGLEXT_CONFIG_INCLUDE_DIR gdkglext-config.h PATHS ${CMAKE_SYSTEM_PREFIX_PATH} PATH_SUFFIXES include/gtkglext-1.0)
+ 	find_path(GTKGLEXT_INCLUDE_DIR gtk/gtkgl.h PATH_SUFFIXES gtkglext-1.0)
+ 	find_library(GDKGLEXT_LIBRARY gdkglext-x11-1.0)
+ 	find_library(GTKGLEXT_LIBRARY gtkglext-x11-1.0)
diff -Nru yabause-0.9.14/debian/patches/series yabause-0.9.14/debian/patches/series
--- yabause-0.9.14/debian/patches/series	1970-01-01 02:00:00.0 +0200
+++ yabause-0.9.14/debian/patches/series	2017-08-29 15:48:23.0 +0300
@@ -0,0 +1 @@
+gtkglext-patch.patch

Bug#873602: pd-xsample FTBFS on ppc64el: UInt32 does not name a type

[Roberto Oliveira]

Package: pd-xsample
Version: 0.3.2~git20161105.1.d16761a1-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=pd-xsample=ppc64el=0.3.2%7Egit20161105.1.d16761a1-1=1486228622=0

...
make[2]: Entering directory '/«PKGBUILDDIR»'
 info: using Makefile.pdlibbuilder version 0.4.4
 info: using Pd API /usr/include/pd/m_pd.h
 info: making target all in lib xsample
 info: making source/main.o in lib xsample
g++ -DPD -I "/usr/include/pd" -DUNIX -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-fcheck-new   -DPD -DFLEXT_SYS=2 -DFLEXT_SHARED -DFLEXT_USE_CMEM 
-I/usr/include/flext -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/«PKGBUILDDIR»=. -fstack-protector-strong -Wformat 
-Werror=format-security -o source/main.o -c source/main.cpp
In file included from source/main.cpp:13:0:
source/main.h:82:9: error: 'UInt32' does not name a type
  inline UInt32 GetPrefetchConstant( int blockSizeInVectors,int blockCount,int 
blockStride )
 ^~
/usr/share/pd-lib-builder//Makefile.pdlibbuilder:867: recipe for target 
'source/main.o' failed
make[2]: *** [source/main.o] Error 1
make[2]: Leaving directory '/«PKGBUILDDIR»'
debian/rules:9: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory '/«PKGBUILDDIR»'
debian/rules:6: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2



-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: ppc64el (ppc64le)

Kernel: Linux 4.11.0-2-powerpc64le (SMP w/16 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#873598: spice-gtk: gir package missing dependencies

[Laurent Bigonville]

Package: src:spice-gtk
Followup-For: Bug #873598

Hi,

While we are at it, the gir package can be marked as multi-arch same

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

Kernel: Linux 4.13.0-rc5-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru spice-gtk-0.34/debian/changelog spice-gtk-0.34/debian/changelog
--- spice-gtk-0.34/debian/changelog 2017-08-06 11:02:13.0 +0200
+++ spice-gtk-0.34/debian/changelog 2017-08-29 14:30:00.0 +0200
@@ -1,3 +1,11 @@
+spice-gtk (0.34-2) UNRELEASED; urgency=medium
+
+  * debian/rules: Call the gir sequence so the gir1.2-* packages have the
+correct dependencies defined.
+  * Make the gir1.2-* packages Multi-Arch: same
+
+ -- Laurent Bigonville   Tue, 29 Aug 2017 14:30:00 +0200
+
 spice-gtk (0.34-1) unstable; urgency=medium
 
   * New upstream release
@@ -7,7 +15,7 @@
 - Rename gir1.2* to fix lintian warning
 - Install gir*.typelib to multiarch directory
 - Remove build-depends on gstreamer1.0-plugins-*(Closes: #863978)
-- Chnage Depends on gstreamer1.0-plugins-* to Suggests(Closes: #849047)
+- Change Depends on gstreamer1.0-plugins-* to Suggests(Closes: #849047)
   * debian/patches:
 - debian/patches/ssl-Rework-our-custom-BIO-type.patch, removed, applied 
   upstream
diff -Nru spice-gtk-0.34/debian/control spice-gtk-0.34/debian/control
--- spice-gtk-0.34/debian/control   2017-08-06 11:02:13.0 +0200
+++ spice-gtk-0.34/debian/control   2017-08-29 14:29:52.0 +0200
@@ -88,6 +88,7 @@
 Package: gir1.2-spiceclientglib-2.0
 Section: introspection
 Architecture: any
+Multi-Arch: same
 Pre-Depends: ${misc:Pre-Depends}
 Depends: ${misc:Depends}, ${gir:Depends}
 Description: GObject for communicating with Spice servers 
(GObject-Introspection)
@@ -126,6 +127,7 @@
 Package: gir1.2-spiceclientgtk-3.0
 Section: introspection
 Architecture: any
+Multi-Arch: same
 Depends: ${misc:Depends}, ${gir:Depends}
 Description: GTK3 widget for SPICE clients (GObject-Introspection)
  libspice-gtk3 provides gtk3 widget to show spice display 
diff -Nru spice-gtk-0.34/debian/rules spice-gtk-0.34/debian/rules
--- spice-gtk-0.34/debian/rules 2017-08-06 11:02:13.0 +0200
+++ spice-gtk-0.34/debian/rules 2017-08-29 14:17:01.0 +0200
@@ -1,7 +1,7 @@
 #!/usr/bin/make -f
 
 %:
-   dh $@ --parallel --with autoreconf
+   dh $@ --parallel --with autoreconf,gir
 
 override_dh_auto_configure:
dh_auto_configure -- \

Bug#853448: marked as done (hylafax: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Tue, 29 Aug 2017 15:33:51 +0300
with message-id <20170829123351.masam3m7ektncebi@localhost>
and subject line Fixed in 3:6.0.6-8
has caused the Debian Bug report #853448,
regarding hylafax: 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.)


-- 
853448: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853448
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:hylafax
Version: 3:6.0.6-7
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/hylafax_6.0.6-7_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

[...]
/usr/bin/g++-D__ANSI_CPP__ -I. -I.. -I.././libhylafax -I.././libhylafax 
   -g -fpic -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -c Dictionary.c++
/usr/bin/g++-D__ANSI_CPP__ -I. -I.. -I.././libhylafax -I.././libhylafax 
   -g -fpic -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -c Obj.c++
/usr/bin/g++-D__ANSI_CPP__ -I. -I.. -I.././libhylafax -I.././libhylafax 
   -g -fpic -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -c PageSize.c++
/usr/bin/g++-D__ANSI_CPP__ -I. -I.. -I.././libhylafax -I.././libhylafax 
   -g -fpic -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -c Range.c++
/usr/bin/g++-D__ANSI_CPP__ -I. -I.. -I.././libhylafax -I.././libhylafax 
   -g -fpic -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -c RE.c++
/usr/bin/g++-D__ANSI_CPP__ -I. -I.. -I.././libhylafax -I.././libhylafax 
   -g -fpic -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -c REArray.c++
/usr/bin/g++-D__ANSI_CPP__ -I. -I.. -I.././libhylafax -I.././libhylafax 
   -g -fpic -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -c REDict.c++
/usr/bin/g++-D__ANSI_CPP__ -I. -I.. -I.././libhylafax -I.././libhylafax 
   -g -fpic -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -c StackBuffer.c++
/usr/bin/g++-D__ANSI_CPP__ -I. -I.. -I.././libhylafax -I.././libhylafax 
   -g -fpic -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -c Str.c++
/usr/bin/g++-D__ANSI_CPP__ -I. -I.. -I.././libhylafax -I.././libhylafax 
   -g -fpic -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -c StrArray.c++
/usr/bin/g++-D__ANSI_CPP__ -I. -I.. -I.././libhylafax -I.././libhylafax 
   -g -fpic -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -c StrDict.c++
/usr/bin/g++-D__ANSI_CPP__ -I. -I.. -I.././libhylafax -I.././libhylafax 
   -g -fpic -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -c Dispatcher.c++
/usr/bin/g++-D__ANSI_CPP__ -I. -I.. -I.././libhylafax -I.././libhylafax 
   -g -fpic -g -O2 

Bug#873599: lxqt-panel FTBFS: error: ‘_explicit’ does not name a type; did you mean ‘explicit’?

[Adrian Bunk]

Source: lxqt-panel
Version: 0.11.1-3
Severity: serious

Some recent change in unstable makes lxqt-panel FTBFS:

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

...
/build/1st/lxqt-panel-0.11.1/plugin-kbindicator/src/x11/kbdlayout.cpp:36:18: 
error: ‘_explicit’ does not name a type; did you mean ‘explicit’?
 #define explicit _explicit
  ^
/build/1st/lxqt-panel-0.11.1/plugin-kbindicator/src/x11/kbdlayout.cpp:36:18: 
error: ‘_explicit’ does not name a type; did you mean ‘explicit’?
 #define explicit _explicit
  ^
/build/1st/lxqt-panel-0.11.1/plugin-kbindicator/src/x11/kbdlayout.cpp:36:18: 
error: ‘_explicit’ does not name a type; did you mean ‘explicit’?
 #define explicit _explicit
  ^
/build/1st/lxqt-panel-0.11.1/plugin-kbindicator/src/x11/kbdlayout.cpp:36:18: 
error: ‘_explicit’ does not name a type; did you mean ‘explicit’?
 #define explicit _explicit
  ^
/build/1st/lxqt-panel-0.11.1/plugin-kbindicator/src/x11/kbdlayout.cpp:36:18: 
error: ‘_explicit’ does not name a type; did you mean ‘explicit’?
 #define explicit _explicit
  ^
/build/1st/lxqt-panel-0.11.1/plugin-kbindicator/src/x11/kbdlayout.cpp:36:18: 
error: ‘_explicit’ does not name a type; did you mean ‘explicit’?
 #define explicit _explicit
  ^
In file included from /usr/include/x86_64-linux-gnu/qt5/QtGui/qevent.h:56:0,
 from /usr/include/x86_64-linux-gnu/qt5/QtGui/QList:1,
 from 
/build/1st/lxqt-panel-0.11.1/plugin-kbindicator/src/x11/../kbdinfo.h:31,
 from 
/build/1st/lxqt-panel-0.11.1/plugin-kbindicator/src/x11/kbdlayout.cpp:38:
/usr/include/x86_64-linux-gnu/qt5/QtGui/qvector2d.h:138:25: error: prototype 
for ‘constexpr QVector2D::QVector2D(const QPoint&)’ does not match any in class 
‘QVector2D’
 Q_DECL_CONSTEXPR inline QVector2D::QVector2D(const QPoint& point) : 
xp(point.x()), yp(point.y()) {}
 ^
/usr/include/x86_64-linux-gnu/qt5/QtGui/qvector2d.h:56:20: error: candidates 
are: constexpr QVector2D::QVector2D(QVector2D&&)
 class Q_GUI_EXPORT QVector2D
^
/usr/include/x86_64-linux-gnu/qt5/QtGui/qvector2d.h:56:20: error:   
  constexpr QVector2D::QVector2D(const QVector2D&)
/usr/include/x86_64-linux-gnu/qt5/QtGui/qvector2d.h:136:25: error:  
   constexpr QVector2D::QVector2D(float, float)
 Q_DECL_CONSTEXPR inline QVector2D::QVector2D(float xpos, float ypos) : 
xp(xpos), yp(ypos) {}
 ^
/usr/include/x86_64-linux-gnu/qt5/QtGui/qvector2d.h:134:25: error:  
   constexpr QVector2D::QVector2D()
 Q_DECL_CONSTEXPR inline QVector2D::QVector2D() : xp(0.0f), yp(0.0f) {}
 ^
/usr/include/x86_64-linux-gnu/qt5/QtGui/qvector2d.h:140:25: error: prototype 
for ‘constexpr QVector2D::QVector2D(const QPointF&)’ does not match any in 
class ‘QVector2D’
 Q_DECL_CONSTEXPR inline QVector2D::QVector2D(const QPointF& point) : 
xp(point.x()), yp(point.y()) {}
 ^
/usr/include/x86_64-linux-gnu/qt5/QtGui/qvector2d.h:56:20: error: candidates 
are: constexpr QVector2D::QVector2D(QVector2D&&)
 class Q_GUI_EXPORT QVector2D
^
/usr/include/x86_64-linux-gnu/qt5/QtGui/qvector2d.h:56:20: error:   
  constexpr QVector2D::QVector2D(const QVector2D&)
/usr/include/x86_64-linux-gnu/qt5/QtGui/qvector2d.h:136:25: error:  
   constexpr QVector2D::QVector2D(float, float)
 Q_DECL_CONSTEXPR inline QVector2D::QVector2D(float xpos, float ypos) : 
xp(xpos), yp(ypos) {}
 ^
/usr/include/x86_64-linux-gnu/qt5/QtGui/qvector2d.h:134:25: error:  
   constexpr QVector2D::QVector2D()
 Q_DECL_CONSTEXPR inline QVector2D::QVector2D() : xp(0.0f), yp(0.0f) {}
 ^
/build/1st/lxqt-panel-0.11.1/plugin-kbindicator/src/x11/kbdlayout.cpp:36:18: 
error: ‘_explicit’ does not name a type; did you mean ‘explicit’?
 #define explicit _explicit
  ^
/build/1st/lxqt-panel-0.11.1/plugin-kbindicator/src/x11/kbdlayout.cpp:36:18: 
error: ‘_explicit’ does not name a type; did you mean ‘explicit’?
 #define explicit _explicit
  ^
/build/1st/lxqt-panel-0.11.1/plugin-kbindicator/src/x11/kbdlayout.cpp:36:18: 
error: ‘_explicit’ does not name a type; did you mean ‘explicit’?
 #define explicit _explicit
  ^
/build/1st/lxqt-panel-0.11.1/plugin-kbindicator/src/x11/kbdlayout.cpp:36:18: 
error: ‘_explicit’ does not name a type; did you mean ‘explicit’?
 #define explicit _explicit
  ^
/build/1st/lxqt-panel-0.11.1/plugin-kbindicator/src/x11/kbdlayout.cpp:36:18: 
error: ‘_explicit’ does not name a type; did you mean ‘explicit’?
 #define explicit _explicit
  ^

Bug#867507: marked as done (automat FTBFS: TypeError: unhashable type: 'MethodicalState')

[Debian Bug Tracking System]

Your message dated Tue, 29 Aug 2017 15:21:07 +0300
with message-id <20170829122107.g3fsrgjzzgbwmpyu@localhost>
and subject line automat 0.6.0-1 builds in unstable
has caused the Debian Bug report #867507,
regarding automat FTBFS: TypeError: unhashable type: 'MethodicalState'
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.)


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

Some recent change in unstable makes automat FTBFS:

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

...
==
ERROR: test_badTransitionForCurrentState 
(automat._test.test_methodical.MethodicalTests)
--
Traceback (most recent call last):
  File "automat/_test/test_methodical.py", line 262, in 
test_badTransitionForCurrentState
class OnlyOnePath(object):
  File "automat/_test/test_methodical.py", line 276, in OnlyOnePath
start.upon(advance, end, [])
  File "automat/_methodical.py", line 62, in upon
self.machine._oneTransition(self, input, enter, outputs, collector)
  File "automat/_methodical.py", line 255, in _oneTransition
tuple(outputTokens))
  File "automat/_core.py", line 74, in addTransition
(inState, inputSymbol, outState, tuple(outputSymbols))
TypeError: unhashable type: 'MethodicalState'

==
ERROR: test_collectOutputs (automat._test.test_methodical.MethodicalTests)
--
Traceback (most recent call last):
  File "automat/_test/test_methodical.py", line 151, in test_collectOutputs
class Machine(object):
  File "automat/_test/test_methodical.py", line 166, in Machine
collector=lambda x: reduce(operator.add, x))
  File "automat/_methodical.py", line 62, in upon
self.machine._oneTransition(self, input, enter, outputs, collector)
  File "automat/_methodical.py", line 255, in _oneTransition
tuple(outputTokens))
  File "automat/_core.py", line 74, in addTransition
(inState, inputSymbol, outState, tuple(outputSymbols))
TypeError: unhashable type: 'MethodicalState'

==
ERROR: test_inputWithArguments (automat._test.test_methodical.MethodicalTests)
--
Traceback (most recent call last):
  File "automat/_test/test_methodical.py", line 193, in test_inputWithArguments
class Mechanism(object):
  File "automat/_test/test_methodical.py", line 205, in Mechanism
state.upon(input, state, [output])
  File "automat/_methodical.py", line 62, in upon
self.machine._oneTransition(self, input, enter, outputs, collector)
  File "automat/_methodical.py", line 255, in _oneTransition
tuple(outputTokens))
  File "automat/_core.py", line 74, in addTransition
(inState, inputSymbol, outState, tuple(outputSymbols))
TypeError: unhashable type: 'MethodicalState'

==
ERROR: test_multipleMachines (automat._test.test_methodical.MethodicalTests)
--
Traceback (most recent call last):
  File "automat/_test/test_methodical.py", line 116, in test_multipleMachines
class MultiMach(object):
  File "automat/_test/test_methodical.py", line 138, in MultiMach
initialA.upon(inputA, initialA, [outputA])
  File "automat/_methodical.py", line 62, in upon
self.machine._oneTransition(self, input, enter, outputs, collector)
  File "automat/_methodical.py", line 255, in _oneTransition
tuple(outputTokens))
  File "automat/_core.py", line 74, in addTransition
(inState, inputSymbol, outState, tuple(outputSymbols))
TypeError: unhashable type: 'MethodicalState'

==
ERROR: test_oneTransition (automat._test.test_methodical.MethodicalTests)
--
Traceback (most recent call last):
  File "automat/_test/test_methodical.py", line 24, in test_oneTransition
class Machination(object):
  File "automat/_test/test_methodical.py", line 48, in Machination
anState.upon(anInput, enter=anotherState, outputs=[anOutput])
  File 

Bug#799454: marked as done (golang-git2go: FTBFS: could not determine kind of name for C.GIT_CHECKOUT_SAFE_CREATE)

[Debian Bug Tracking System]

Your message dated Tue, 29 Aug 2017 15:22:55 +0300
with message-id <20170829122255.dmjkpspvshozwg7y@localhost>
and subject line golang-git2go 0.24+git20161003.0.2209188-1 builds in unstable
has caused the Debian Bug report #799454,
regarding golang-git2go: FTBFS: could not determine kind of name for 
C.GIT_CHECKOUT_SAFE_CREATE
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.)


-- 
799454: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799454
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-git2go
Version: 0.0~git20150731.0.ed62fda-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

golang-git2go fails to build from source in unstable/amd64 as libgit2
has been updated. You can read more here:

  https://github.com/libgit2/git2go/issues/181

TL;DR this GIT_CHECKOUT_SAFE_CREATE was removed in src:libgit2 0.23.1-1
(or earlier).


  [..]

  dh build --buildsystem=golang --with=golang
 dh_testdir -O--buildsystem=golang
 dh_auto_configure -O--buildsystem=golang
mkdir -p obj-x86_64-linux-gnu
 dh_auto_build -O--buildsystem=golang
cd obj-x86_64-linux-gnu
go install -v github.com/libgit2/git2go
  github.com/libgit2/git2go
  # github.com/libgit2/git2go
  could not determine kind of name for C.GIT_CHECKOUT_SAFE_CREATE
  dh_auto_build: go install -v github.com/libgit2/git2go returned exit
  code 2
  debian/rules:13: recipe for target 'build' failed
  make: *** [build] Error 2
  dpkg-buildpackage: error: debian/rules build gave error exit status 2

  [..]

The full build log is attached or can be viewed here:


https://reproducible.debian.net/logs/unstable/amd64/golang-git2go_0.0~git20150731.0.ed62fda-1.build1.log.gz


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
I: using fakeroot in build.
I: pbuilder: network access will be disabled during build
I: Current time: Fri Sep 18 11:58:35 GMT+12 2015
I: pbuilder-time-stamp: 1442620715
I: Building the build Environment
I: extracting base tarball [/var/cache/pbuilder/unstable-reproducible-base.tgz]
I: creating local configuration
I: copying local configuration
I: mounting /proc filesystem
I: mounting /run/shm filesystem
I: mounting /dev/pts filesystem
I: Mounting /dev/shm
I: Mounting /sys
I: policy-rc.d already exists
I: Installing the build-deps
 -> Attempting to satisfy build-dependencies
 -> Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team 
Description: Dummy package to satisfy dependencies with aptitude - created by 
pbuilder
 This package was created automatically by pbuilder to satisfy the
 build-dependencies of the package being currently built.
Depends: debhelper (>= 9), golang-go, dh-golang, pkg-config, libgit2-dev
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in 
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 20254 files and directories currently installed.)
Preparing to unpack .../pbuilder-satisfydepends-dummy.deb ...
Unpacking pbuilder-satisfydepends-dummy (0.invalid.0) ...
dpkg: pbuilder-satisfydepends-dummy: dependency problems, but configuring 
anyway as you requested:
 pbuilder-satisfydepends-dummy depends on golang-go; however:
  Package golang-go is not installed.
 pbuilder-satisfydepends-dummy depends on dh-golang; however:
  Package dh-golang is not installed.
 pbuilder-satisfydepends-dummy depends on pkg-config; however:
  Package pkg-config is not installed.
 pbuilder-satisfydepends-dummy depends on libgit2-dev; however:
  Package libgit2-dev is not installed.

Setting up pbuilder-satisfydepends-dummy (0.invalid.0) ...
Reading package lists...
Building dependency tree...
Reading state information...
Initializing package states...
Writing extended state information...
Building tag database...
pbuilder-satisfydepends-dummy is already installed at the requested version 
(0.invalid.0)
pbuilder-satisfydepends-dummy is already installed at the requested version 
(0.invalid.0)
The following NEW packages will be installed:
  dh-golang{a} golang-go{a} golang-go-linux-amd64{a} golang-src{a} 
  libcurl3{a} libcurl4-openssl-dev{a} libgcrypt20-dev{a} libgit2-23{a} 
  libgit2-dev{a} libgnutls-deb0-28{a} 

Bug#873598: spice-gtk: gir package missing dependencies

[Laurent Bigonville]

Source: spice-gtk
Version: 0.34-1
Severity: serious
Tags: patch

Hi,

gir1.2-spiceclientgtk-3.0 and gir1.2-spiceclientglib-2.0 have not any
dependencies defined.

It seems that the build is not calling dh_girepository

See the attached patch.

Cheers,

Laurent Bigonville

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

Kernel: Linux 4.13.0-rc5-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru spice-gtk-0.34/debian/changelog spice-gtk-0.34/debian/changelog
--- spice-gtk-0.34/debian/changelog 2017-08-06 11:02:13.0 +0200
+++ spice-gtk-0.34/debian/changelog 2017-08-29 14:22:47.0 +0200
@@ -1,3 +1,10 @@
+spice-gtk (0.34-2) UNRELEASED; urgency=medium
+
+  * debian/rules: Call the gir sequence so the gir1.2-* packages have the
+correct dependencies defined.
+
+ -- Laurent Bigonville   Tue, 29 Aug 2017 14:22:47 +0200
+
 spice-gtk (0.34-1) unstable; urgency=medium
 
   * New upstream release
@@ -7,7 +14,7 @@
 - Rename gir1.2* to fix lintian warning
 - Install gir*.typelib to multiarch directory
 - Remove build-depends on gstreamer1.0-plugins-*(Closes: #863978)
-- Chnage Depends on gstreamer1.0-plugins-* to Suggests(Closes: #849047)
+- Change Depends on gstreamer1.0-plugins-* to Suggests(Closes: #849047)
   * debian/patches:
 - debian/patches/ssl-Rework-our-custom-BIO-type.patch, removed, applied 
   upstream
diff -Nru spice-gtk-0.34/debian/rules spice-gtk-0.34/debian/rules
--- spice-gtk-0.34/debian/rules 2017-08-06 11:02:13.0 +0200
+++ spice-gtk-0.34/debian/rules 2017-08-29 14:17:01.0 +0200
@@ -1,7 +1,7 @@
 #!/usr/bin/make -f
 
 %:
-   dh $@ --parallel --with autoreconf
+   dh $@ --parallel --with autoreconf,gir
 
 override_dh_auto_configure:
dh_auto_configure -- \

Processed: libprelude: diff for NMU version 3.1.0-0.5

[Debian Bug Tracking System]

Processing control commands:

> tags 871289 + patch
Bug #871289 [libpreludecpp8] libpreludecpp8: requires rebuild against GCC 7 and 
symbols/shlibs bump
Added tag(s) patch.
> tags 871289 + pending
Bug #871289 [libpreludecpp8] libpreludecpp8: requires rebuild against GCC 7 and 
symbols/shlibs bump
Added tag(s) pending.

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

Bug#871289: libprelude: diff for NMU version 3.1.0-0.5

[Mattia Rizzolo]

Control: tags 871289 + patch
Control: tags 871289 + pending

Dear maintainer,

I've prepared an NMU for libprelude (versioned as 3.1.0-0.5) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.

-- 
regards,
Mattia Rizzolo

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

 changelog |9 +
 control   |1 +
 rules |5 +
 3 files changed, 15 insertions(+)

diff -Nru libprelude-3.1.0/debian/changelog libprelude-3.1.0/debian/changelog
--- libprelude-3.1.0/debian/changelog	2017-07-17 12:07:24.0 +0200
+++ libprelude-3.1.0/debian/changelog	2017-08-28 00:30:12.0 +0200
@@ -1,3 +1,12 @@
+libprelude (3.1.0-0.5) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Rebuild with GCC 7. (Closes: #871289)
+- Build-depend on gcc >= 7.
+- Update shlibs to ensure rdeps pull in the new version.
+
+ -- Thomas Andrejak   Mon, 28 Aug 2017 00:30:12 +0200
+
 libprelude (3.1.0-0.4) unstable; urgency=medium
 
   * Upload to unstable.
diff -Nru libprelude-3.1.0/debian/control libprelude-3.1.0/debian/control
--- libprelude-3.1.0/debian/control	2017-06-27 21:18:39.0 +0200
+++ libprelude-3.1.0/debian/control	2017-08-28 00:30:12.0 +0200
@@ -4,6 +4,7 @@
 Maintainer: Pierre Chifflier 
 Build-Depends: debhelper (>= 10),
 dh-python ,
+g++ (>= 4:7),
 gawk,
 gem2deb ,
 libgcrypt20-dev,
diff -Nru libprelude-3.1.0/debian/rules libprelude-3.1.0/debian/rules
--- libprelude-3.1.0/debian/rules	2017-06-27 21:56:05.0 +0200
+++ libprelude-3.1.0/debian/rules	2017-08-28 00:30:12.0 +0200
@@ -52,5 +52,10 @@
 override_dh_python3:
 	dh_python3 -ppython3-prelude
 
+override_dh_makeshlibs:
+	# For new symbols when compiled with GCC 7
+	dh_makeshlibs -plibpreludecpp8 -V'libpreludecpp8 (>= 3.1.0-0.5~)'
+	dh_makeshlibs --remaining-packages
+
 %:
 	dh $@ $(DH_ADDONS)


signature.asc
Description: PGP signature

Bug#872742: marked as done (qtmultimedia5-dev: QMAKE_PRL_LIBS comtains libraries without package dependencies)

[Debian Bug Tracking System]

Your message dated Tue, 29 Aug 2017 11:38:05 +
with message-id 
and subject line Bug#872742: fixed in qtmultimedia-opensource-src 5.9.1-3
has caused the Debian Bug report #872742,
regarding qtmultimedia5-dev: QMAKE_PRL_LIBS comtains libraries without package 
dependencies
to be marked as done.

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

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


-- 
872742: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872742
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qtmultimedia5-dev
Version: 5.9.1-2
Severity: serious
Control: affects -1 src:actiona

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

...
g++ -m64 -Wl,-z,relro -Wl,-rpath-link,/usr/lib/x86_64-linux-gnu -shared -o 
libActionPackSystem.so generated/killprocessinstance.o 
generated/notifyinstance.o generated/systeminstance.o 
generated/pixelcolorinstance.o generated/playsoundinstance.o 
generated/findimageinstance.o generated/findimagedefinition.o 
generated/system.o generated/mediaplaylist.o generated/notify.o 
generated/process.o generated/qdeviceinfo.o generated/qstorageinfo.o 
generated/qscreensaver.o generated/qbatteryinfo.o generated/qnetworkinfo.o 
generated/qdeviceinfo_linux.o generated/qstorageinfo_linux.o 
generated/qnetworkinfo_linux.o generated/qscreensaver_linux.o 
generated/qbatteryinfo_linux.o generated/systemsession.o 
generated/qrc_actionpacksystem.o generated/moc_commanddefinition.o 
generated/moc_commandinstance.o generated/moc_killprocessdefinition.o 
generated/moc_killprocessinstance.o generated/moc_notifydefinition.o 
generated/moc_notifyinstance.o generated/moc_pixelcolordefinition.o 
generated/moc_pixelcolorinsta
 nce.o generated/moc_systeminstance.o generated/moc_systemdefinition.o 
generated/moc_openurlinstance.o generated/moc_openurldefinition.o 
generated/moc_detachedcommanddefinition.o 
generated/moc_detachedcommandinstance.o generated/moc_playsounddefinition.o 
generated/moc_playsoundinstance.o generated/moc_findimagedefinition.o 
generated/moc_findimageinstance.o generated/moc_system.o 
generated/moc_mediaplaylist.o generated/moc_notify.o generated/moc_process.o 
generated/moc_qbatteryinfo_linux_p.o generated/moc_qdeviceinfo.o 
generated/moc_qstorageinfo.o generated/moc_qscreensaver.o 
generated/moc_qbatteryinfo.o generated/moc_qnetworkinfo.o 
generated/moc_qdeviceinfo_linux_p.o generated/moc_qstorageinfo_linux_p.o 
generated/moc_qnetworkinfo_linux_p.o generated/moc_actionpacksystem.o  
-L/usr/X11R6/lib64 -L../.. -ltools -lactiontools -lnotify -lgdk_pixbuf-2.0 
-lgio-2.0 -lgobject-2.0 -lQt5MultimediaWidgets -lpulse-mainloop-glib -lpulse 
-lglib-2.0 -lQt5Widgets -lQt5Multimedia -lQt5Gui -lQt5Script -
 lQt5Network -lQt5DBus -lQt5Core -lGL -lpthread  
/usr/bin/ld: cannot find -lpulse-mainloop-glib
/usr/bin/ld: cannot find -lpulse
collect2: error: ld returned 1 exit status
Makefile:320: recipe for target '../../actions/libActionPackSystem.so' failed
make[3]: *** [../../actions/libActionPackSystem.so] Error 1


The root cause is:

$ grep QMAKE_PRL_LIBS /usr/lib/x86_64-linux-gnu/libQt5MultimediaWidgets.prl
QMAKE_PRL_LIBS = -L/usr/X11R6/lib64  -lQt5Multimedia -lQt5Widgets -lQt5Gui 
-lQt5Network -lQt5Core -lpthread -lpulse-mainloop-glib -lpulse -lglib-2.0
$

Either the libraries have to be removed from QMAKE_PRL_LIBS,
or the corresponding -dev packages added to the dependencies
of qtmultimedia5-dev.

This is a regression compared to 5.7.1 (QMAKE_PRL_LIBS is shorter there).
--- End Message ---
--- Begin Message ---
Source: qtmultimedia-opensource-src
Source-Version: 5.9.1-3

We believe that the bug you reported is fixed in the latest version of
qtmultimedia-opensource-src, 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.
Dmitry Shachnev  (supplier of updated 
qtmultimedia-opensource-src 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 14:08:13 +0300
Source: qtmultimedia-opensource-src
Binary: libqt5multimedia5 libqt5multimedia5-plugins libqt5multimediaquick-p5 

Processed: Not a problem in stretch

[Debian Bug Tracking System]

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

> tags 873583 buster sid
Bug #873583 [src:tortoisehg] tortoisehg: needs update for mercurial 4.3
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Processed: Security tracker says bug is in stretch

[Debian Bug Tracking System]

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

> found 868300 1.06-1
Bug #868300 {Done: ChangZhuo Chen (陳昌倬) } [yadm] yadm: 
CVE-2017-11353: race condition allows access to SSH and PGP keys
Marked as found in versions yadm/1.06-1.
> thanks
Stopping processing here.

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

Bug#873589: clearsilver: FTBFS on arm64, mips*, ppc64el during clean - unable to guess system type

[James Cowgill]

Source: clearsilver
Version: 0.10.5-2
Severity: serious
Tags: sid buster

Hi,

clearsilver FTBFS on arm64, mips* and ppc64el with this error:
> checking build system type... ./config.guess: unable to guess system type
> 
> This script, last modified 2001-09-04, has failed to recognize
> the operating system you are using. It is advised that you
> download the most up to date version of the config scripts from
> 
> ftp://ftp.gnu.org/pub/gnu/config/
> 
> If the version you run (./config.guess) is already up to date, please
> send the following data and any information you think might be
> pertinent to  in order to provide the needed
> information to handle your system.
> 
> config.guess timestamp = 2001-09-04

This happens during the "clean" phase of the build:
>  fakeroot debian/rules clean
> dh clean --with python2
>dh_auto_clean
>   make -j6 distclean
> make[1]: Entering directory '/<>'
> Makefile:10: rules.mk: No such file or directory
> ./configure
> checking for gcc... gcc

Calling "make distclean" should probably be skipped if rules.mk does not
exist so that the configure script isn't run.

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#873319: marked as pending

[Christos Trochalakis]

tag 873319 pending
thanks

Hello,

Bug #873319 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:

https://anonscm.debian.org/cgit/pkg-nginx/nginx.git/commit/?id=ee4f08f

---
commit ee4f08f8b48651eb584373af0bb71afd5a4d3c1d
Author: Christos Trochalakis 
Date:   Tue Aug 29 10:50:48 2017 +0300

Release 1.13.4-1

diff --git a/debian/changelog b/debian/changelog
index 7d350cf..3e671b0 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,20 @@
+nginx (1.13.4-1) unstable; urgency=medium
+
+  * New upstream version 1.13.4
+  * nginx-lua:
++ Add a simple lua autopkgtest
++ Discover LuaJIT 2.1 (FTBFS) (Closes: #873319)
++ Update to v0.10.10
++ Update OpenSSL 1.1 patch
++ Drop patch to build against Nginx 1.11.11, now included upstream
+  * tests: Fix race between reload and curl's http request
+  * Explicitly disable autoreconf (debhelper 10)
+  * Drop Upstart configuration
+  * Bump Standards to 4.1.0
++ Switch all packages to Priority optional, extra is considered deprecated
+
+ -- Christos Trochalakis   Tue, 29 Aug 2017 10:49:03 
+0300
+
 nginx (1.13.3-1) unstable; urgency=high
 
   * New upstream version 1.13.3.

Processed: Bug#873319 marked as pending

[Debian Bug Tracking System]

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

> tag 873319 pending
Bug #873319 {Done: Christos Trochalakis } [src:nginx] 
nginx FTBFS with luajit 2.1
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#871170: marked as done (openfst: FTBFS: ./../include/fst/replace.h:1198:57: error: expected ';' before '::' token)

[Debian Bug Tracking System]

Your message dated Tue, 29 Aug 2017 12:47:14 +0300
with message-id <20170829094714.xit2qfusobcpcobg@localhost>
and subject line openfst 1.6.3-1 builds
has caused the Debian Bug report #871170,
regarding openfst: FTBFS: ./../include/fst/replace.h:1198:57: error: expected 
';' before '::' token
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.)


-- 
871170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871170
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openfst
Version: 1.5.3+r3-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 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):
> /bin/bash ../../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H   
> -I./../include  -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
> -fdebug-prefix-map=/<>/openfst-1.5.3+r3=. -fstack-protector-strong 
> -Wformat -Werror=format-security -std=c++11 -c -o mapped-file.lo 
> mapped-file.cc
> libtool: compile:  g++ -DHAVE_CONFIG_H -I./../include -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -O2 
> -fdebug-prefix-map=/<>/openfst-1.5.3+r3=. -fstack-protector-strong 
> -Wformat -Werror=format-security -std=c++11 -c util.cc  -fPIC -DPIC -o 
> .libs/util.o
> libtool: compile:  g++ -DHAVE_CONFIG_H -I./../include -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -O2 
> -fdebug-prefix-map=/<>/openfst-1.5.3+r3=. -fstack-protector-strong 
> -Wformat -Werror=format-security -std=c++11 -c symbol-table.cc  -fPIC -DPIC 
> -o .libs/symbol-table.o
> libtool: compile:  g++ -DHAVE_CONFIG_H -I./../include -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -O2 
> -fdebug-prefix-map=/<>/openfst-1.5.3+r3=. -fstack-protector-strong 
> -Wformat -Werror=format-security -std=c++11 -c mapped-file.cc  -fPIC -DPIC -o 
> .libs/mapped-file.o
> libtool: compile:  g++ -DHAVE_CONFIG_H -I./../include -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -O2 
> -fdebug-prefix-map=/<>/openfst-1.5.3+r3=. -fstack-protector-strong 
> -Wformat -Werror=format-security -std=c++11 -c compat.cc  -fPIC -DPIC -o 
> .libs/compat.o
> libtool: compile:  g++ -DHAVE_CONFIG_H -I./../include -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -O2 
> -fdebug-prefix-map=/<>/openfst-1.5.3+r3=. -fstack-protector-strong 
> -Wformat -Werror=format-security -std=c++11 -c flags.cc  -fPIC -DPIC -o 
> .libs/flags.o
> libtool: compile:  g++ -DHAVE_CONFIG_H -I./../include -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -O2 
> -fdebug-prefix-map=/<>/openfst-1.5.3+r3=. -fstack-protector-strong 
> -Wformat -Werror=format-security -std=c++11 -c symbol-table-ops.cc  -fPIC 
> -DPIC -o .libs/symbol-table-ops.o
> libtool: compile:  g++ -DHAVE_CONFIG_H -I./../include -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -O2 
> -fdebug-prefix-map=/<>/openfst-1.5.3+r3=. -fstack-protector-strong 
> -Wformat -Werror=format-security -std=c++11 -c fst.cc  -fPIC -DPIC -o 
> .libs/fst.o
> libtool: compile:  g++ -DHAVE_CONFIG_H -I./../include -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -O2 
> -fdebug-prefix-map=/<>/openfst-1.5.3+r3=. -fstack-protector-strong 
> -Wformat -Werror=format-security -std=c++11 -c properties.cc  -fPIC -DPIC -o 
> .libs/properties.o
> libtool: compile:  g++ -DHAVE_CONFIG_H -I./../include -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -O2 
> -fdebug-prefix-map=/<>/openfst-1.5.3+r3=. -fstack-protector-strong 
> -Wformat -Werror=format-security -std=c++11 -c compat.cc -o compat.o 
> >/dev/null 2>&1
> libtool: compile:  g++ -DHAVE_CONFIG_H -I./../include -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -O2 
> -fdebug-prefix-map=/<>/openfst-1.5.3+r3=. -fstack-protector-strong 
> -Wformat -Werror=format-security -std=c++11 -c properties.cc -o properties.o 
> >/dev/null 2>&1
> libtool: compile:  g++ -DHAVE_CONFIG_H -I./../include -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -O2 
> -fdebug-prefix-map=/<>/openfst-1.5.3+r3=. -fstack-protector-strong 
> -Wformat -Werror=format-security -std=c++11 -c mapped-file.cc -o 
> mapped-file.o >/dev/null 2>&1
> In file included from ./../include/fst/accumulator.h:18:0,
>  from ./../include/fst/label-reachable.h:13,
>  from ./../include/fst/lookahead-matcher.h:13,
>  from ./../include/fst/matcher-fst.h:13,
>  from fst.cc:14:
> ./../include/fst/replace.h: In constructor 
> 'fst::ArcIterator >::ArcIterator(const 
> fst::ReplaceFst&, fst::ArcIterator 
> >::StateId)':
> ./../include/fst/replace.h:1198:57: error: expected ';' before '::' token
>->template 

Bug#859510: marked as done (Generated header file without means to regenerate)

[Debian Bug Tracking System]

Your message dated Tue, 29 Aug 2017 18:29:55 +0900
with message-id <87k21m4t7w.wl-uwab...@gfd-dennou.org>
and subject line Bug#859510 marked as done
has caused the Debian Bug report #859510,
regarding Generated header file without means to regenerate
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.)


-- 
859510: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859510
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-unf-ext
Version: 0.0.7.2-2
Severity: serious

Hi,
While investigating #859463 with Niels, we noticed that the file in
question, ext/unf_ext/unf/table.hh, is pre-generated, but the original
sources[1] (and script used to process the sources[2]) are not present
in main.

Regards,
James

[1] https://github.com/sile/unf/tree/master/data
[2] https://github.com/sile/unf/blob/master/lisp/gen-table.lisp
--- End Message ---
--- Begin Message ---
Source: ruby-unf-ext
Source-Version: 0.0.7.4-1--- End Message ---