Bug#871129: marked as done (plasma-framework: FTBFS: configcategory_p.cpp:133:10: fatal error: private/moc_configcategory_p.cpp: No such file or directory)

[Debian Bug Tracking System]

Your message dated Mon, 28 Aug 2017 06:00:25 +
with message-id 
and subject line Bug#871129: fixed in plasma-framework 5.37.0-1
has caused the Debian Bug report #871129,
regarding plasma-framework: FTBFS: configcategory_p.cpp:133:10: fatal error: 
private/moc_configcategory_p.cpp: 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.)


-- 
871129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871129
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: plasma-framework
Version: 5.28.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):
> cd /<>/obj-x86_64-linux-gnu/autotests && /usr/bin/c++  
> -DKCOREADDONS_LIB -DQT_CORE_LIB -DQT_DISABLE_DEPRECATED_BEFORE=0 -DQT_GUI_LIB 
> -DQT_NETWORK_LIB -DQT_NO_CAST_TO_ASCII -DQT_NO_DEBUG 
> -DQT_NO_SIGNALS_SLOTS_KEYWORDS -DQT_NO_URL_CAST_FROM_STRING -DQT_QML_LIB 
> -DQT_QUICK_LIB 
> -DQT_TESTCASE_BUILDDIR=\"/<>/obj-x86_64-linux-gnu\" 
> -DQT_TESTLIB_LIB -DQT_USE_FAST_OPERATOR_PLUS -DQT_USE_QSTRINGBUILDER 
> -DQT_WIDGETS_LIB -DQT_XML_LIB -DTRANSLATION_DOMAIN=\"libplasma5\" 
> -D_GNU_SOURCE -D_LARGEFILE64_SOURCE 
> -I/<>/obj-x86_64-linux-gnu/autotests 
> -I/<>/autotests 
> -I/<>/obj-x86_64-linux-gnu/autotests/dialogqmltest_autogen/include
>  -I/<>/obj-x86_64-linux-gnu -I/<>/src/plasma/.. 
> -I/<>/obj-x86_64-linux-gnu/src/plasma 
> -I/<>/obj-x86_64-linux-gnu/src/plasma/Plasma 
> -I/<>/src/plasma 
> -I/<>/obj-x86_64-linux-gnu/src/plasmaquick 
> -I/<>/obj-x86_64-linux-gnu/src/plasmaquick/.. 
> -I/<>/src/plasmaquick -isystem /usr/include/x86_64-linux-gnu/qt5 
> -isystem /usr/include/x86_64-linux-gnu/qt5/QtQml -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 
> /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++-64 -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtTest -isystem /usr/include/KF5/KService 
> -isystem /usr/include/KF5 -isystem /usr/include/KF5/KConfigCore -isystem 
> /usr/include/KF5/KCoreAddons -isystem /usr/include/x86_64-linux-gnu/qt5/QtGui 
> -isystem /usr/include/KF5/KPackage -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtQuick -isystem 
> /usr/include/KF5/KWindowSystem -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
> /usr/include/KF5/KArchive -isystem /usr/include/KF5/KConfigGui -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtXml -isystem /usr/include/KF5/KI18n 
> -isystem /usr/include/KF5/KIOCore -isystem /usr/include/KF5/KIconThemes 
> -isystem /usr/include/KF5/KDeclarative  -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time 
> -D_FORTIFY_SOURCE=2 -std=c++0x -fno-exceptions -Wall -Wextra -Wcast-align 
> -Wchar-subscripts -Wformat-security -Wno-long-long -Wpointer-arith -Wundef 
> -Wnon-virtual-dtor -Woverloaded-virtual -Werror=return-type -std=c++0x 
> -fno-exceptions -Wall -Wextra -Wcast-align -Wchar-subscripts 
> -Wformat-security -Wno-long-long -Wpointer-arith -Wundef -Wnon-virtual-dtor 
> -Woverloaded-virtual -Werror=return-type -pedantic -fvisibility=hidden 
> -fvisibility-inlines-hidden   -Wall -std=c++0x -fPIC -std=gnu++11 -o 
> CMakeFiles/dialogqmltest.dir/dialogqmltest.cpp.o -c 
> /<>/autotests/dialogqmltest.cpp
> In file included from /<>/autotests/configmodeltest.cpp:25:0:
> /<>/src/plasma/../plasmaquick/private/configcategory_p.cpp:133:10:
>  fatal error: private/moc_configcategory_p.cpp: No such file or directory
>  #include "private/moc_configcategory_p.cpp"
>   ^~
> compilation terminated.
> autotests/CMakeFiles/configmodeltest.dir/build.make:65: recipe for target 
> 'autotests/CMakeFiles/configmodeltest.dir/configmodeltest.cpp.o' failed
> make[4]: *** [autotests/CMakeFiles/configmodeltest.dir/configmodeltest.cpp.o] 
> Error 1

The full build log is available from:
   http://aws-logs.debian.net/2017/08/05/plasma-framework_5.28.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: plasma-framework
Source-Version: 5.37.0-1

We beli

Bug#853374: marked as done (dislocker: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Mon, 28 Aug 2017 06:00:15 +
with message-id 
and subject line Bug#853374: fixed in dislocker 0.7.1-1
has caused the Debian Bug report #853374,
regarding dislocker: 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.)


-- 
853374: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853374
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:dislocker
Version: 0.6.1-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/dislocker_0.6.1-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

[...]
cd /<>/src && /usr/bin/cc  -DAUTHOR="\"Romain Coltel\"" 
-DPROGNAME=\"dislocker\" -DVERSION=\"0.6.1\" -D_FILE_OFFSET_BITS=64 
-D_HAVE_RUBY=2.3.0 -D__ARCH=\"x86_64\" -D__ARCH_X86_64 -D__LINUX 
-D__OS=\"Linux\" -Ddislocker_EXPORTS -isystem /usr/local/include 
-I/<>/include -I/usr/include/ruby-2.3.0 
-I/usr/include/ruby-2.3.0/x86_64-linux-gnu 
-I/usr/include/x86_64-linux-gnu/ruby-2.3.0  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -Wall -Werror 
-Wextra -fstack-protector -fstrict-aliasing -D_FORTIFY_SOURCE=2 -O1 
-Wconversion -Wl,-z,now -Wl,-z,relro -fPIC   -o 
CMakeFiles/dislocker.dir/common.c.o   -c /<>/src/common.c
[  7%] Building C object src/CMakeFiles/dislocker.dir/config.c.o
cd /<>/src && /usr/bin/cc  -DAUTHOR="\"Romain Coltel\"" 
-DPROGNAME=\"dislocker\" -DVERSION=\"0.6.1\" -D_FILE_OFFSET_BITS=64 
-D_HAVE_RUBY=2.3.0 -D__ARCH=\"x86_64\" -D__ARCH_X86_64 -D__LINUX 
-D__OS=\"Linux\" -Ddislocker_EXPORTS -isystem /usr/local/include 
-I/<>/include -I/usr/include/ruby-2.3.0 
-I/usr/include/ruby-2.3.0/x86_64-linux-gnu 
-I/usr/include/x86_64-linux-gnu/ruby-2.3.0  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -Wall -Werror 
-Wextra -fstack-protector -fstrict-aliasing -D_FORTIFY_SOURCE=2 -O1 
-Wconversion -Wl,-z,now -Wl,-z,relro -fPIC   -o 
CMakeFiles/dislocker.dir/config.c.o   -c /<>/src/config.c
[ 10%] Building C object src/CMakeFiles/dislocker.dir/xstd/xstdio.c.o
cd /<>/src && /usr/bin/cc  -DAUTHOR="\"Romain Coltel\"" 
-DPROGNAME=\"dislocker\" -DVERSION=\"0.6.1\" -D_FILE_OFFSET_BITS=64 
-D_HAVE_RUBY=2.3.0 -D__ARCH=\"x86_64\" -D__ARCH_X86_64 -D__LINUX 
-D__OS=\"Linux\" -Ddislocker_EXPORTS -isystem /usr/local/include 
-I/<>/include -I/usr/include/ruby-2.3.0 
-I/usr/include/ruby-2.3.0/x86_64-linux-gnu 
-I/usr/include/x86_64-linux-gnu/ruby-2.3.0  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -Wall -Werror 
-Wextra -fstack-protector -fstrict-aliasing -D_FORTIFY_SOURCE=2 -O1 
-Wconversion -Wl,-z,now -Wl,-z,relro -fPIC   -o 
CMakeFiles/dislocker.dir/xstd/xstdio.c.o   -c /<>/src/xstd/xstdio.c
/<>/src/xstd/xstdio.c: In function 'dis_stdio_init':
/<>/src/xstd/xstdio.c:91:20: error: this statement may fall 
through [-Werror=implicit-fallthrough=]
verbosity   = L_DEBUG;
^
/<>/src/xstd/xstdio.c:93:3: note: here
   case L_DEBUG:
   ^~~~
/<>/src/xstd/xstdio.c:94:20: error: this statement may fall 
through [-Werror=implicit-fallthrough=]
fds[L_DEBUG]= log;
^
/<>/src/xstd/xstdio.c:96:3: note: here
   case L_INFO:
   ^~~~
/<>/src/xstd/xstdio.c:97:20: error: this statement may fall 
through [-Werror=implicit-fallthrough=]
fds[L_INFO] = log;
~~

Processed: Re: Bug#873465: apt: wrongly reports failure on 'update' on mips64el, triggers d-i FTBFS

[Debian Bug Tracking System]

Processing control commands:

> tag -1 patch
Bug #873465 [apt] apt: wrongly reports failure on 'update' on mips64el, 
triggers d-i FTBFS
Added tag(s) patch.

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

Bug#871156: pyfits: FTBFS: cc1: error: -Wformat-security ignored without -Wformat [-Werror=format-security]

[Steve Langasek]

Package: pyfits
Version: 1:3.4-4
Followup-For: Bug #871156
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu artful ubuntu-patch

Hi Aurelien,

Attached is a simple fix for this build failure which I've uploaded to
Ubuntu.  There is no reason for this build system to explicitly disable
-Wformat on Debian, the code builds fine as-is.

Cheers,
-- 
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 pyfits-3.4/debian/patches/series pyfits-3.4/debian/patches/series
--- pyfits-3.4/debian/patches/series2016-12-19 15:41:17.0 -0800
+++ pyfits-3.4/debian/patches/series2017-08-27 22:40:43.0 -0700
@@ -2,3 +2,4 @@
 02-numpy-deprecation-warning.diff
 03-fix-for-cfitsio-3380.patch
 04-numpy-1.12.patch
+yes-Wformat.patch
diff -Nru pyfits-3.4/debian/patches/yes-Wformat.patch 
pyfits-3.4/debian/patches/yes-Wformat.patch
--- pyfits-3.4/debian/patches/yes-Wformat.patch 1969-12-31 16:00:00.0 
-0800
+++ pyfits-3.4/debian/patches/yes-Wformat.patch 2017-08-27 22:43:35.0 
-0700
@@ -0,0 +1,21 @@
+Description: don't disable format warnings, which breaks 
-Werror=format-security
+ By default we use hardening flags for package builds to detect certain common
+ security errors, but -Werror=format-security was being silently ignored
+ because of upstream's use of -Wformat.  GCC7 now detects this conflict and
+ requires manual resolution, which we resolve in favor of enforcing the
+ security check.
+Author: Steve Langasek 
+Bug-Debian: https://bugs.debian.org/871156
+
+Index: pyfits-3.4/setup.cfg
+===
+--- pyfits-3.4.orig/setup.cfg
 pyfits-3.4/setup.cfg
+@@ -120,7 +120,6 @@
+   -Wno-unused-variable
+   -Wno-parentheses
+   -Wno-uninitialized
+-  -Wno-format
+   -Wno-strict-prototypes
+   -Wno-unused
+   -Wno-comments

Bug#840516: New upstream version available with the bug fix applied.

[Paul Libert]

Upstream has released 1.0.2 last month and the fix for this bug seems to be
in.
Any chance to update to this version in testing ?

P.

Bug#790222: [boinc_dev] Bug#790222: wxwidgets3.0: depends on libwebkitgtk-1.0-0 which is deprecated

[Olly Betts]

On Sun, Aug 20, 2017 at 08:54:25PM +0300, Adrian Bunk wrote:
> wxwidgets3.0 is a key package, so won't get autoremoved from testing.
> 
> And since a removal from testing would imply a removal of all
> reverse dependencies, wxwidgets3.0 is not at risk of being
> removed from testing anytime soon.

I know, but letting this continue to stall removal of the ancient
webkitgtk seems to be abusing this situation.  I've also previously said
I'm OK to drop the dependency once other blockers are resolved.

Besides, we need to settle on a way forwards soon, or else the feasible
options will start to dwindle.

Cheers,
Olly

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 Mon, 28 Aug 2017 04:49:11 +
with message-id 
and subject line Bug#789927: fixed in anthy 1:0.3-3
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-3

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: Mon, 28 Aug 2017 13:26:04 +0900
Source: anthy
Binary: anthy anthy-common anthy-el libanthy1 libanthy-dev libanthyinput0 
libanthyinput-dev
Architecture: source all amd64
Version: 1:0.3-3
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-3) unstable; urgency=medium
 .
   * debian/control (Breaks, Replaces): Add (Closes: #789927).
Checksums-Sha1:
 5e2a21092a602f9e8a8efc840b8e6bcc902f68d9 2000 anthy_0.3-3.dsc
 7a64108d8176cea8ea77439c74a9a113c8c05cf8 11936 anthy_0.3-3.debian.tar.xz
 f47d4c08655144df000a1d5b27f81aba46750a53 5563414 anthy-common_0.3-3_all.deb
 4760e46e086b7518fa8e3c5bdba5613d4d827481 32616 anthy-dbgsym_0.3-3_amd64.deb
 81f3d79086df95a3f93bea403f61f808ace5d1b2 30500 anthy-el_0.3-3_all.deb
 b454e436ed762bfeac03d108e800fc249479222c 7988 anthy_0.3-3_amd64.buildinfo
 72de6e6bcb0bbbc1f502f59fe78cd92b79b6dd75 25290 anthy_0.3-3_amd64.deb
 43f62a996ff558390157d1466a9c71ed270b09a5 115846 libanthy-dev_0.3-3_amd64.deb
 03bd447e6bbbe75e2fd5b535ae017519f011597f 173122 
libanthy1-dbgsym_0.3-3_amd64.deb
 347e54ee424fd7622458f9187c7d719ffd2d1daa 109068 libanthy1_0.3-3_amd64.deb
 cfa71e462c542d5fe3fa5f0a27b13e854de91ebf 28994 
libanthyinput-dev_0.3-3_amd64.deb
 3bab2772d39e459476061516d538a55dc5b22427 30456 
libanthyinput0-dbgsym_0.3-3_amd64.deb
 6b5ee7fd76a4d6e6e8d7a45c179f70374ed84852 30604 libanthyinput0_0.3-3_amd64.deb
Checksums-Sha256:
 6c5e70f033725fa5797159e79a2151a160aef1a2837cc

Processed: notfound 873467 in 5.3.28-13, found 873467 in 5.3.28-13.1

[Debian Bug Tracking System]

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

> notfound 873467 5.3.28-13
Bug #873467 [src:db5.3] db5.3: FTBFS on mips64el
No longer marked as found in versions db5.3/5.3.28-13.
> found 873467 5.3.28-13.1
Bug #873467 [src:db5.3] db5.3: FTBFS on mips64el
Marked as found in versions db5.3/5.3.28-13.1.
> thanks
Stopping processing here.

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

Bug#873467: db5.3: FTBFS on mips64el

[Salvatore Bonaccorso]

Source: db5.3
Version: 5.3.28-13
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi

db5.3 FTBFS on mips64el (no futher investigation done):

Log:
https://buildd.debian.org/status/fetch.php?pkg=db5.3&arch=mips64el&ver=5.3.28-13.1&stamp=1503890181&raw=0

Regards,
Salvatore

Bug#873465: apt: wrongly reports failure on 'update' on mips64el, triggers d-i FTBFS

[Cyril Brulebois]

Package: apt
Version: 1.5~beta2
Severity: serious
Tags: d-i
Justification: triggers FTBFS

(Please keep debian-boot@ in the loop.)

Hi,

Daily builds of the Debian Installer on mips64el have started erroring
out on 2017-08-19 with what I believed was some kind of network issue;
but we've just hit the very same issue on the buildd when trying to
build the actual debian-installer release:
  
https://buildd.debian.org/status/fetch.php?pkg=debian-installer&arch=mips64el&ver=20170828&stamp=1503891562&raw=0

Excerpt:
| Using generated sources.list.udeb:
|deb [trusted=yes] copy:/<>/build/ localudebs/
|deb http://ftp.at.debian.org/debian buster main/debian-installer
|deb http://ftp.debian.org/debian buster main/debian-installer
| make[7]: 'sources.list.udeb' is up to date.
| Ign:1 copy:/<>/build localudebs/ InRelease
| Ign:2 copy:/<>/build localudebs/ Release
| Get:3 http://ftp.at.debian.org/debian buster InRelease [124 kB]
| Ign:4 copy:/<>/build localudebs/ Packages
| Ign:4 copy:/<>/build localudebs/ Packages
| Ign:4 copy:/<>/build localudebs/ Packages
| Get:4 copy:/<>/build localudebs/ Packages [20 B]
| Get:5 http://ftp.debian.org/debian buster InRelease [124 kB]
| Get:6 http://ftp.at.debian.org/debian buster/main/debian-installer mips64el 
Packages [55.7 kB]
| Get:7 http://ftp.debian.org/debian buster/main/debian-installer mips64el 
Packages [55.7 kB]
| Fetched 358 kB in 1s (280 kB/s)
| Reading package lists...
| E: Some index files failed to download. They have been ignored, or old ones 
used instead.

AFAICT, everything looks good and matches what happens on e.g. amd64:
| Using generated sources.list.udeb:
|deb [trusted=yes] copy:/<>/build/ localudebs/
|deb http://mirror.bm.debian.org/debian buster main/debian-installer
|deb http://ftp.debian.org/debian buster main/debian-installer
| make[9]: 'sources.list.udeb' is up to date.
| Ign:1 copy:/<>/build localudebs/ InRelease
| Ign:2 copy:/<>/build localudebs/ Release
| Ign:3 copy:/<>/build localudebs/ Packages
| Ign:3 copy:/<>/build localudebs/ Packages
| Ign:3 copy:/<>/build localudebs/ Packages
| Get:3 copy:/<>/build localudebs/ Packages [20 B]
| Get:4 http://mirror.bm.debian.org/debian buster InRelease [124 kB]
| Get:5 http://ftp.debian.org/debian buster InRelease [124 kB]
| Get:6 http://mirror.bm.debian.org/debian buster/main/debian-installer amd64 
Packages [50.5 kB]
| Get:7 http://ftp.debian.org/debian buster/main/debian-installer amd64 
Packages [50.5 kB]
| Fetched 348 kB in 0s (563 kB/s)
| Reading package lists...
| Reading package lists...

Given apt 1.5~beta2 was uploaded on the evening of the 17th, it probably
reached the archive on the 18th, and was first used in the build chroot
for the 0030Z build on the 19th. I'm filing this against apt since it
seems clear to me there were no actual download errors, but it also
seems likely that apt might be encountering gcc-7 related
miscompilations, see #871514.

In any case, a speedy fix would be much appreciated, as this is a
blocker for the D-I Buster Alpha 1 release (which has already been
delayed way too much for other reasons).

Thanks for your time.


KiBi.

Processed: found 873439 in 1:2016.4.4+dfsg-3

[Debian Bug Tracking System]

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

> found 873439 1:2016.4.4+dfsg-3
Bug #873439 [src:flightgear] flightgear: CVE-2017-13709: Incorrect access 
control
Marked as found in versions flightgear/1:2016.4.4+dfsg-3.
> thanks
Stopping processing here.

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

Bug#853644: marked as done (ripole: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Mon, 28 Aug 2017 03:49:33 +
with message-id 
and subject line Bug#853644: fixed in ripole 0.2.0+20081101.0215-4
has caused the Debian Bug report #853644,
regarding ripole: 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.)


-- 
853644: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853644
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ripole
Version: 0.2.0+20081101.0215-3
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

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

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

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/ripole_0.2.0+20081101.0215-3_unstable_gcc7.log
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

[...]
-

dpkg-buildpackage: info: source package ripole
dpkg-buildpackage: info: source version 0.2.0+20081101.0215-3
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Chris Lamb 
 dpkg-source --before-build ripole-0.2.0+20081101.0215
dpkg-buildpackage: info: host architecture amd64
 fakeroot debian/rules clean
dh  clean
   dh_testdir
   dh_auto_clean
make -j1 clean
make[1]: Entering directory '/<>/ripole-0.2.0+20081101.0215'
rm -f *.o ripole
make[1]: Leaving directory '/<>/ripole-0.2.0+20081101.0215'
   dh_clean
 dpkg-source -b ripole-0.2.0+20081101.0215
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building ripole using existing 
./ripole_0.2.0+20081101.0215.orig.tar.gz
dpkg-source: info: building ripole in ripole_0.2.0+20081101.0215-3.debian.tar.xz
dpkg-source: info: building ripole in ripole_0.2.0+20081101.0215-3.dsc
 debian/rules build
dh  build
   dh_testdir
   dh_update_autotools_config
   dh_auto_configure
   dh_auto_build
make -j1
make[1]: Entering directory '/<>/ripole-0.2.0+20081101.0215'
cc -Wall -g -O2 -I. -Werror -g -O2 
-fdebug-prefix-map=/<>/ripole-0.2.0+20081101.0215=. 
-fstack-protector-strong -Wformat -Werror=format-security  -c ole.c
cc -Wall -g -O2 -I. -Werror -g -O2 
-fdebug-prefix-map=/<>/ripole-0.2.0+20081101.0215=. 
-fstack-protector-strong -Wformat -Werror=format-security  -c olestream-unwrap.c
cc -Wall -g -O2 -I. -Werror -g -O2 
-fdebug-prefix-map=/<>/ripole-0.2.0+20081101.0215=. 
-fstack-protector-strong -Wformat -Werror=format-security  -c bytedecoders.c
cc -Wall -g -O2 -I. -Werror -g -O2 
-fdebug-prefix-map=/<>/ripole-0.2.0+20081101.0215=. 
-fstack-protector-strong -Wformat -Werror=format-security  -c logger.c
cc -Wall -g -O2 -I. -Werror -g -O2 
-fdebug-prefix-map=/<>/ripole-0.2.0+20081101.0215=. 
-fstack-protector-strong -Wformat -Werror=format-security  -c pldstr.c
pldstr.c: In function 'PLD_strtok':
pldstr.c:300:30: error: comparison between pointer and zero character constant 
[-Werror=pointer-compare]
  if ((st->start)&&(st->start != '\0'))
  ^~
pldstr.c:300:20: note: did you mean to dereference the pointer?
  if ((st->start)&&(st->start != '\0'))
^
cc1: all warnings being treated as errors
Makefile:10: recipe for target 'pldstr.o' failed
make[1]: *** [pldstr.o] Error 1
make[1]: Leaving directory '/<>/ripole-0.2.0+20081101.0215'
dh_auto_build: make -j1 returned exit code 2
debian/rules:6: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
--- End Message ---
--- Begin Message ---
Source: ripole
Source-Version: 0.2.0+20081101.0215-4

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

A summar

Bug#870599: marked as done (ansible: Needs pinned Jinja2 dependency due to upstream bug #20494)

[Debian Bug Tracking System]

Your message dated Mon, 28 Aug 2017 00:19:09 +
with message-id 
and subject line Bug#870599: fixed in ansible 2.3.1.0+dfsg-2
has caused the Debian Bug report #870599,
regarding ansible: Needs pinned Jinja2 dependency due to upstream bug #20494
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.)


-- 
870599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870599
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ansible
Version: 2.2.1.0-2
Severity: important

Dear Maintainer,

Due to upstream bug https://github.com/ansible/ansible/issues/20494 it is
currently not advisable to upgrade python-jinja2 to version 2.9 when using
Ansible. There seem to be other incompabilities with Jinja2 2.9 as well.

Please pin the dependency to python-jinja2 to <2.9 until this bug gets fixed.

Thank you.



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

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

Versions of packages ansible depends on:
ii  python2.7.13-2
ii  python-crypto 2.6.1-7+b1
ii  python-httplib2   0.9.2+dfsg-1
ii  python-jinja2 2.9.6-1
ii  python-netaddr0.7.18-2
ii  python-paramiko   2.0.0-1
ii  python-pkg-resources  36.0.1-1
ii  python-yaml   3.12-1+b1

Versions of packages ansible recommends:
ii  python-kerberos   1.1.5-2+b3
ii  python-selinux2.6-3+b2
pn  python-winrm  
ii  python-xmltodict  0.11.0-1

Versions of packages ansible suggests:
pn  cowsay   
ii  sshpass  1.06-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: ansible
Source-Version: 2.3.1.0+dfsg-2

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

Debian distribution maintenance software
pp.
Harlan Lieberman-Berg  (supplier of updated ansible 
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, 27 Aug 2017 19:57:43 -0400
Source: ansible
Binary: ansible
Architecture: source
Version: 2.3.1.0+dfsg-2
Distribution: unstable
Urgency: high
Maintainer: Harlan Lieberman-Berg 
Changed-By: Harlan Lieberman-Berg 
Closes: 870599 871601
Description: 
 ansible- Configuration management, deployment, and task execution system
Changes:
 ansible (2.3.1.0+dfsg-2) unstable; urgency=high
 .
   * Import patch fixing jinja2 issues (Closes: #870599, #871601)
   * Revert python-jinja2 pin.
Checksums-Sha1: 
 6aee2d94a623cd5d9edca3f55576b7c2f7bc3533 2238 ansible_2.3.1.0+dfsg-2.dsc
 e763542cd351f3adbc7014d67a4c610ec587e59a 17512 
ansible_2.3.1.0+dfsg-2.debian.tar.xz
Checksums-Sha256: 
 a54e8532ec6dbe582479338d9416dc40c36d5964a21225c0c346ed5e00187aa5 2238 
ansible_2.3.1.0+dfsg-2.dsc
 ca33469c772bd9128e2e938526f3ccfcdbe8eb5b11709911bfe19cafe13ca719 17512 
ansible_2.3.1.0+dfsg-2.debian.tar.xz
Files: 
 7b07adf54eacec0c91365ab03352b97a 2238 admin optional ansible_2.3.1.0+dfsg-2.dsc
 e3fd59f7ea346464ea93647f192d9356 17512 admin optional 
ansible_2.3.1.0+dfsg-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKqBAEBCgCUFiEEhiNlIJf/8kpE2Nai6afXk4v2O6UFAlmjXdVfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDg2
MjM2NTIwOTdGRkYyNEE0NEQ4RDZBMkU5QTdENzkzOEJGNjNCQTUWHGhsaWViZXJt
YW5AZGViaWFuLm9yZwAKCRDpp9eTi/Y7pbHXD/9IF6y6lWXc3TPCigEWoC4TcwGx
6Kz1/2SE3ckn0DEfIs+SoZ/N+vMGBWY0m52CrOg5/17CmqUCcFKLWWOHSkG//YJ7
ZPhmVskpHEXllHyhsvn5pr0nP2A6r/z/8Zh29XFdSCl5a6TJDPBfuTDyAoLJAf5S
BHUQRrl1uRx+XX1DXmATGgT/e9//RRA9oCSdLurFSKNU1aEZ+wCjgv1fP/nbzNnU
3nWdb5u3BbHPseDwEfqzZUHBRhpbZJpxCMuQ4YAbIBG0dIfRITT1Sn6WwVl6tpMH
aFGz2ocmIEiAYx2J/EVt73nCX45lTi/D7SLmF3JEmUWF9XEHixhlCwtwHk08UwbC
DfrKkz0WSjOcgDT1xXe3LLEYtd7R7nOjIF8yhpX/KSFZI6jXnGkiRhKzXhe0ON2d
/V+jJxPYZ1OfPHAExmvcFxdA8wcibSLGJTTK5OWzRCtOS0vlXcr

Bug#871601: marked as done (ansible-2.3.1.0+dfsg-1 is uninstallable)

[Debian Bug Tracking System]

Your message dated Mon, 28 Aug 2017 00:19:09 +
with message-id 
and subject line Bug#871601: fixed in ansible 2.3.1.0+dfsg-2
has caused the Debian Bug report #871601,
regarding ansible-2.3.1.0+dfsg-1 is uninstallable
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.)


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

Dear Maintainer,

ansible-2.3.1.0+dfsg-1 depends on python-jinja2 < 2.9.  However, this is not
available in testing/unstable/experimental.  As a result,
ansible-2.3.1.0+dfsg-1 is uninstallable, and its migration from unstable has
been blocked.

Thanks,
--Robbie

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

Kernel: Linux 4.11.0-1-rt-amd64 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages ansible depends on:
ii  python2.7.13-2
ii  python-crypto 2.6.1-7+b1
ii  python-httplib2   0.9.2+dfsg-1
ii  python-jinja2 2.9.6-1
ii  python-netaddr0.7.18-2
ii  python-paramiko   2.0.0-1
ii  python-pkg-resources  36.0.1-1
ii  python-yaml   3.12-1+b1

Versions of packages ansible recommends:
ii  python-kerberos   1.1.5-2+b3
ii  python-selinux2.6-3+b2
pn  python-winrm  
ii  python-xmltodict  0.11.0-1

Versions of packages ansible suggests:
pn  cowsay   
pn  sshpass  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: ansible
Source-Version: 2.3.1.0+dfsg-2

We believe that the bug you reported is fixed in the latest version of
ansible, 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.
Harlan Lieberman-Berg  (supplier of updated ansible 
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, 27 Aug 2017 19:57:43 -0400
Source: ansible
Binary: ansible
Architecture: source
Version: 2.3.1.0+dfsg-2
Distribution: unstable
Urgency: high
Maintainer: Harlan Lieberman-Berg 
Changed-By: Harlan Lieberman-Berg 
Closes: 870599 871601
Description: 
 ansible- Configuration management, deployment, and task execution system
Changes:
 ansible (2.3.1.0+dfsg-2) unstable; urgency=high
 .
   * Import patch fixing jinja2 issues (Closes: #870599, #871601)
   * Revert python-jinja2 pin.
Checksums-Sha1: 
 6aee2d94a623cd5d9edca3f55576b7c2f7bc3533 2238 ansible_2.3.1.0+dfsg-2.dsc
 e763542cd351f3adbc7014d67a4c610ec587e59a 17512 
ansible_2.3.1.0+dfsg-2.debian.tar.xz
Checksums-Sha256: 
 a54e8532ec6dbe582479338d9416dc40c36d5964a21225c0c346ed5e00187aa5 2238 
ansible_2.3.1.0+dfsg-2.dsc
 ca33469c772bd9128e2e938526f3ccfcdbe8eb5b11709911bfe19cafe13ca719 17512 
ansible_2.3.1.0+dfsg-2.debian.tar.xz
Files: 
 7b07adf54eacec0c91365ab03352b97a 2238 admin optional ansible_2.3.1.0+dfsg-2.dsc
 e3fd59f7ea346464ea93647f192d9356 17512 admin optional 
ansible_2.3.1.0+dfsg-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKqBAEBCgCUFiEEhiNlIJf/8kpE2Nai6afXk4v2O6UFAlmjXdVfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDg2
MjM2NTIwOTdGRkYyNEE0NEQ4RDZBMkU5QTdENzkzOEJGNjNCQTUWHGhsaWViZXJt
YW5AZGViaWFuLm9yZwAKCRDpp9eTi/Y7pbHXD/9IF6y6lWXc3TPCigEWoC4TcwGx
6Kz1/2SE3ckn0DEfIs+SoZ/N+vMGBWY0m52CrOg5/17CmqUCcFKLWWOHSkG//YJ7
ZPhmVskpHEXllHyhsvn5pr0nP2A6r/z/8Zh29XFdSCl5a6TJDPBfuTDyAoLJAf5S
BHUQRrl1uRx+XX1DXmATGgT/e9//RRA9oCSdLurFSKNU1aEZ+wCjgv1fP/nbzNnU
3nWdb5u3BbHPseDwEfqzZUHBRhpbZJpxCMuQ4YAbIBG0dIfRITT1Sn6WwVl6tpMH
aFGz2ocmIEiAYx2J/EVt73nCX45lTi/D7SLmF3JEmUWF9XEHixhlCwtwHk08UwbC
DfrKkz0WSjOcgDT1xXe3LLEYtd7R7nOjIF8yhpX/KSFZI6jXnGkiRhKzXhe0ON2d
/V+jJxPYZ1OfPHAExmvcFxdA8wcibSLGJTTK5OWzRCtOS0vlXcrworHBMYyDjkwI
k1OukKFf8qiH+iYneMn/n7rgDte

Bug#871213: marked as pending

[Stuart Prescott]

tag 871213 pending
thanks

Hello,

Bug #871213 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:


http://anonscm.debian.org/git/pkg-multimedia/rosegarden.git/commit/?id=1ebdf65

---
commit 1ebdf65991f1d4fdc97b306e7f1d7ebf2c974c16
Author: Stuart Prescott 
Date:   Mon Aug 28 00:36:48 2017 +1000

Add changelog for upload

diff --git a/debian/changelog b/debian/changelog
index 9e9e957..55c4f0a 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,13 @@
+rosegarden (1:17.04-1) unstable; urgency=medium
+
+  * New upstream release.
+  * Switch to Qt5 build.
+  * Bump standards-version to 4.1.0 (no changes required).
+  * Fix generation of 'src/svnversion.h' to prevent FTBFS with CMake 3.9
+(Closes: #871213).
+
+ -- Stuart Prescott   Mon, 28 Aug 2017 00:36:33 +1000
+
 rosegarden (1:16.06-1) unstable; urgency=medium
 
   * New upstream release.

Processed: Bug#871213 marked as pending

[Debian Bug Tracking System]

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

> tag 871213 pending
Bug #871213 {Done: Stuart Prescott } [src:rosegarden] 
rosegarden: FTBFS: make[3]: *** No rule to make target 'src/svnversion.h', 
needed by 'src/CMakeFiles/rosegardenprivate_autogen'. Stop.
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#871691: marked as done (nss FTBFS on big endian: cpputil/databuffer.h:96:14: error: 'curve' may be used uninitialized in this function)

[Debian Bug Tracking System]

Your message dated Sun, 27 Aug 2017 23:19:41 +
with message-id 
and subject line Bug#871691: fixed in nss 2:3.32-2
has caused the Debian Bug report #871691,
regarding nss FTBFS on big endian: cpputil/databuffer.h:96:14: error: 'curve' 
may be used uninitialized in this function
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.)


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

https://buildd.debian.org/status/package.php?p=nss&suite=sid

...
In file included from test_io.h:17:0,
 from gtest_utils.h:12,
 from ssl_ecdh_unittest.cc:19:
../../cpputil/databuffer.h: In member function 'virtual 
nss_test::PacketFilter::Action 
nss_test::ECCServerKEXFilter::FilterHandshake(const 
nss_test::TlsHandshakeFilter::HandshakeHeader&, const nss_test::DataBuffer&, 
nss_test::DataBuffer*)':
../../cpputil/databuffer.h:96:14: error: 'curve' may be used uninitialized in 
this function [-Werror=maybe-uninitialized]
 uint32_t nvalue = htonl(val);
  ^~
ssl_ecdh_unittest.cc:554:14: note: 'curve' was declared here
 uint32_t curve;
  ^
cc1plus: all warnings being treated as errors
../../coreconf/rules.mk:444: recipe for target 'OBJS/ssl_ecdh_unittest.o' failed
make[4]: *** [OBJS/ssl_ecdh_unittest.o] Error 1
--- End Message ---
--- Begin Message ---
Source: nss
Source-Version: 2:3.32-2

We believe that the bug you reported is fixed in the latest version of
nss, 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.
Mike Hommey  (supplier of updated nss 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 07:39:59 +0900
Source: nss
Binary: libnss3 libnss3-tools libnss3-dev libnss3-dbg
Architecture: source
Version: 2:3.32-2
Distribution: unstable
Urgency: medium
Maintainer: Maintainers of Mozilla-related packages 

Changed-By: Mike Hommey 
Description:
 libnss3- Network Security Service libraries
 libnss3-dbg - Debugging symbols for the Network Security Service libraries
 libnss3-dev - Development files for the Network Security Service libraries
 libnss3-tools - Network Security Service tools
Closes: 871691 871700
Changes:
 nss (2:3.32-2) unstable; urgency=medium
 .
   * nss/gtests/ssl_gtest/ssl_ecdh_unittest.cc: Fix possibly uninitialized
 value 'curve'. bz#1389263. Closes: #871691.
   * lib/freebl/Makefile: Only build gcm.c and rijndael.c with -maes.
 Closes: #871700.
Checksums-Sha1:
 33ab454fdd8c8a6b463c8b98de550e2e340599ea 2223 nss_3.32-2.dsc
 98b6b72397b1e0b66dd3852c8f4a0f81ea8cc3ea 25172 nss_3.32-2.debian.tar.xz
 feff2e8b838f25424852a2a1510f987b6810433b 5681 nss_3.32-2_source.buildinfo
Checksums-Sha256:
 dd485ead7c4517c6f6e0b3dccd92a1708e1da4a534c850a8751abfe3e92e6ead 2223 
nss_3.32-2.dsc
 c4f7f9292288bfa52885a5736a8b3a5a949fed84b98f26f10e4473828d044431 25172 
nss_3.32-2.debian.tar.xz
 77f51541b293b39749f19b25e85793e3dfa5fe6605d0212987eaae3f8641ec9d 5681 
nss_3.32-2_source.buildinfo
Files:
 8dcd0ecf8a6f69e8d4a5cb3ffcff3b99 2223 libs optional nss_3.32-2.dsc
 416b32c635003425f6007f1e8b0898aa 25172 libs optional nss_3.32-2.debian.tar.xz
 3c4934d7c37343c88687f08736daa653 5681 libs optional nss_3.32-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEGC4WHREwufzNfbFn5CqgT6aqjHIFAlmjSo4ACgkQ5CqgT6aq
jHIPkw/7B+0Ilgy5CaQUAGAJ8Rix0aloB7oV5s7fwZ140ext+WqYxjcoNLPml7nq
12MY72BZHaurdDHwTNn2gSKzfEZZUYNVSTjfIhnFe6yLjcqjQ0OkxuGu84jUNXeE
hv0kPNvxLTXAUiiK72ZfLsyOGf4BazeX8bHc3lPTgsg6hAqY9s/CJ5m9A64BhG0i
iMIPvnFaWQGJ2cr7QbDAfVF7DAb3YdY8WClF5gaSGSL7Wex9og1j1zjIoFDLniOi
uYxwnjLlFm2Uf+FqeT7C7tlwTH4ZKGh/cxTYTRqCOlvNOEYzVDMQS8RHKzIwoT5F
6+lSUweqSltm0DCgbKOAi/1bSryquSEJvWTGrD3Ow7E7ytPAOA3do+WRH1OciBQr
zGroLFO08tE3+Q0JyGOP02ovWJknlQ2RRUPZ+6IKAVN53lCJz6aM/OxbFx5Pl1vi
If8rczabifHRvA3TFB+FNgG+yX/v0QX+v/zOVkz6MwaoopP9SJxLvSPNvqEYgBAU
R/tKPiZIj0LimP9Ti6NjB2JXIAyvox/CN6kCvr/TDJNmK6xU8FYAXS3MDTd1Uown
/0tkteUrLwdyLWISQ5Iobwh0BOJU/XesUdWi7NjU21HR+KdkR+W7DuHzLfabiHM9
GQtnDOHE2MW/aYra3m

Bug#860147: marked as done (gnuradio-dev in backports depends on liblog4cpp5-dev which isn't available)

[Debian Bug Tracking System]

Your message dated Sun, 27 Aug 2017 17:54:13 -0400
with message-id <20170827175413.68db3...@216-moncure.alexandria.va.us>
and subject line gnuradio-dev in backports depends on liblog4cpp5-dev which 
isn't available
has caused the Debian Bug report #860147,
regarding gnuradio-dev in backports depends on liblog4cpp5-dev which isn't 
available
to be marked as done.

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

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


-- 
860147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860147
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnuradio-dev
Version: 3.7.10.1-1~bpo8+1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Running jessie and gnuradio 3.7.5.  Configured jessie-backports and installed 
gnuradio 3.7.10.1.  The Sources menu (rtlsdr) was missing. Tried to install 
gnuradio-dev.  Got the following error:

root@raspberrypi:~# dpkg -l | grep '^ii  gnuradio'
ii  gnuradio  3.7.10.1-1~bpo8+1 
armhfGNU Radio Software Radio Toolkit
root@raspberrypi:~# sudo apt-get -t jessie-backports install gnuradio-dev
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 gnuradio-dev : Depends: liblog4cpp5-dev but it is not going to be installed
E: Unable to correct problems, you have held broken packages.



-- System Information:
Distributor ID: Raspbian
Description:Raspbian GNU/Linux 8.0 (jessie)
Release:8.0
Codename:   jessie
Architecture: armv7l

Kernel: Linux 4.4.50-v7+ (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Not a Debian bug

-Maitland--- End Message ---

Bug#866649: marked as done (sugar-read-activity: depends on libwebkitgtk-3.0-0 which is deprecated)

[Debian Bug Tracking System]

Your message dated Sun, 27 Aug 2017 17:56:42 -0400
with message-id 

and subject line Re: sugar-read-activity: depends on libwebkitgtk-3.0-0 which 
is deprecated
has caused the Debian Bug report #866649,
regarding sugar-read-activity: depends on libwebkitgtk-3.0-0 which is deprecated
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.)


-- 
866649: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866649
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sugar-read-activity
Severity: serious
Tags: sid buster
User: pkg-webkit-maintain...@lists.alioth.debian.org
Usertags: oldlibs libwebkitgtk-3.0-0 webkit1

Hi,

sugar-read-activity depends on gir1.2-webkit-3.0, which is deprecated
in favor of gir1.2-webkit2-4.0 (provided in Debian by webkit2gtk). It
should be ported to the new webkitgtk version so we
can remove the old, unmaintained one.

Please try to do soon as we're going to try to remove the old webkitgtk soon.

I am filing this bug as "serious" since the old webkitgtk will not be
available in the next major stable release of Debian (codenamed
"buster").

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

On behalf of the Debian WebKit Maintainers,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Manually closing this bug.

 sugar-read-activity (119-1) unstable; urgency=medium
 .
   [ upstream ]
   * New release.
 + New translations.
 + Remove EPUB support to remove WebKit 3.0 API dependency.
 + Replace BeautifulSoup dependency with ElementTree.
 + Remove unused screenshots.
 + Remove some unnecessary errors from log.
 .
   [ Jonas Smedegaard ]
   * Update copyright info: Use https protocol in file format URL.
   * Declare compliance with Debian Policy 4.1.0.
   * Update package relations:
 + Stop depend on python-beautifulsoup gir1.2-webkit-3.0.
 + Stop recommend fonts-dejavu-core.--- End Message ---

Bug#853664: marked as done (snoopy: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Sun, 27 Aug 2017 21:06:40 +
with message-id 
and subject line Bug#853664: fixed in snoopy 2.4.6-2
has caused the Debian Bug report #853664,
regarding snoopy: 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.)


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

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

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

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

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

  apt-get -t=experimental install g++ 

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

[...]
   dh_auto_build
make -j1
make[1]: Entering directory '/<>'
(CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/bash 
/<>/build/aux/missing autoheader)
rm -f stamp-h1
touch config.h.in
cd . && /bin/bash ./config.status config.h
config.status: creating config.h
make  all-recursive
make[2]: Entering directory '/<>'
Making all in src
make[3]: Entering directory '/<>/src'
make  all-recursive
make[4]: Entering directory '/<>/src'
Making all in datasource
make[5]: Entering directory '/<>/src/datasource'
make  all-am
make[6]: Entering directory '/<>/src/datasource'
/bin/bash ../../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
-I../..   -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Werror -I../../src -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o cmdline.lo cmdline.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../.. -Wdate-time 
-D_FORTIFY_SOURCE=2 -Wall -Werror -I../../src -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c cmdline.c  -fPIC -DPIC -o .libs/cmdline.o
cmdline.c: In function 'snoopy_datasource_cmdline':
cmdline.c:60:78: error: comparison between pointer and zero character constant 
[-Werror=pointer-compare]
 for (cmdLineArgCount=0 ; *(snoopy_inputdatastorage_argv+cmdLineArgCount) 
!= '\0' ; cmdLineArgCount++);
  ^~
cmdline.c:60:30: note: did you mean to dereference the pointer?
 for (cmdLineArgCount=0 ; *(snoopy_inputdatastorage_argv+cmdLineArgCount) 
!= '\0' ; cmdLineArgCount++);
  ^
cc1: all warnings being treated as errors
Makefile:921: recipe for target 'cmdline.lo' failed
make[6]: *** [cmdline.lo] Error 1
make[6]: Leaving directory '/<>/src/datasource'
Makefile:808: recipe for target 'all' failed
make[5]: *** [all] Error 2
make[5]: Leaving directory '/<>/src/datasource'
Makefile:823: recipe for target 'all-recursive' failed
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory '/<>/src'
Makefile:671: recipe for target 'all' failed
make[3]: *** [all] Error 2
make[3]: Leaving directory '/<>/src'
Makefile:697: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory '/<>'
Makefile:614: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/<>'
dh_auto_build: make -j1 returned exit code 2
debian/rules:7: recipe for target 'binary' failed
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
--- End Message ---
--- Begin Message ---
Source: snoopy
Source-Version: 2.4.6-2

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

Bug#870838: marked as done (sugar-write-activity: Please fix depends on abiword gir package)

[Debian Bug Tracking System]

Your message dated Sun, 27 Aug 2017 21:07:14 +
with message-id 
and subject line Bug#870838: fixed in sugar-write-activity 98.2-1
has caused the Debian Bug report #870838,
regarding sugar-write-activity: Please fix depends on abiword gir package
to be marked as done.

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

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


-- 
870838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870838
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sugar-write-activity
Version: 98-1
Severity: serious

Please depend on gir1.2-abi-3.0 instead of gir1.2-abiword-3.0 since
the package was renamed to fix a lintian warning.

Thanks,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: sugar-write-activity
Source-Version: 98.2-1

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated sugar-write-activity 
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, 27 Aug 2017 21:51:37 +0200
Source: sugar-write-activity
Binary: sugar-write-activity
Architecture: source
Version: 98.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Sugar Team 
Changed-By: Jonas Smedegaard 
Description:
 sugar-write-activity - Sugar Learning Platform - writing activity
Closes: 870838
Changes:
 sugar-write-activity (98.2-1) unstable; urgency=medium
 .
   [ upstream ]
   New bugfix release(s):
 + Update POT file
 + Fix Python GI API version warnings
 + Fix for fail to start with Abiword 2.9 on Fedora 18
 .
   [ Jonas Smedegaard ]
   * Modernize cdbs:
 + Drop upstream-tarball hints: Use gbp import-orig --uscan.
 + Do copyright-check in maintainer script (not during build).
   * Drop obsolete lintian override regarding debhelper 9.
   * Tighten lintian overrides regarding License-Reference.
   * Modernize Vcs-* fields:
 + Use anonscm hostname.
 + Use git (not cgit) in path.
   * Declare compliance with Debian Policy 4.1.0.
   * Remove Luke Faraone as uploader.
 Thanks for your past contributions.
   * Update git-buildpackage config:
 + Filter any .gitignore file.
   * Update copyright info: Extend coverage for myself.
   * Update package relations:
 + (Build-)depend on gir1.2-abi-3.0 (not gir1.2-abiword-3.0).
   Closes: Bug#870838. Thanks to Jeremy Bicha.
   * Fix rename locale ibo→ig: ISO 639-1 favored over ISO 639-2.
Checksums-Sha1:
 cfdbb720c6446945f3c7d5cf2024fba5ccaae48e 2071 sugar-write-activity_98.2-1.dsc
 2f061e748a9ae7232e028862cbc1fcec0d2476c7 85757 
sugar-write-activity_98.2.orig.tar.gz
 caec70ca32021848e69256732c436a5d859505cd 6512 
sugar-write-activity_98.2-1.debian.tar.xz
 fa5ae08e40b0fec5ce70d84c9ccf973eb8aee2fe 9916 
sugar-write-activity_98.2-1_amd64.buildinfo
Checksums-Sha256:
 2a5c65f2fb0c8efa0288194df0cd7c2d7aaad5cd38bd05dc75c6646ff411664f 2071 
sugar-write-activity_98.2-1.dsc
 8741cbccdec6921dd9e2f0cf60e0508d61afffef1a69df29f951358303422d41 85757 
sugar-write-activity_98.2.orig.tar.gz
 9a8d285558676dfd56298f8035a04bf352d14ccde20d2b9b826109979008b675 6512 
sugar-write-activity_98.2-1.debian.tar.xz
 c43ff300975749f48280e5641dd954145cb436c4dbdb8537e8d28a0914ad0bf8 9916 
sugar-write-activity_98.2-1_amd64.buildinfo
Files:
 f59b8e21264f7829ee50a8accafc3b7b 2071 x11 optional 
sugar-write-activity_98.2-1.dsc
 63dd6d2fc4c08856d32c4be823ee04b2 85757 x11 optional 
sugar-write-activity_98.2.orig.tar.gz
 a2ee799c35888443184675a65798eda5 6512 x11 optional 
sugar-write-activity_98.2-1.debian.tar.xz
 9c5a948a54a0ab61497e786537c74787 9916 x11 optional 
sugar-write-activity_98.2-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlmjIxAACgkQLHwxRsGg
ASHdBg/+KGt8oVYxFG7UVjxz9AdRsIc5SVH70gZm/RalSMKvrX40rYx+TsJoXhUE
rGv+3lJfnEPznU7qvck9w7pF+47shhuk1hSDYuYDVcoMpSie5TUy5HcuUOrJT3zY
HMpD3MnafLXamnlvNDeZ2laA33VcTUiVI5InzThQs5B73fcjGL6rBrz+xfUXiU7u
BrvA2Q0mCqXuhQwuzaVozqY4N2pkoOUjrEPj7rjAzlOXT67Ah8XOIe8OpfQnlVY7
VnY6tcIvpdHM9DRoRQtkx69i8efjjTqGjJsbN58LhXVrpRyiLG70sr/JNifp2CC1
EUgZXgmyNq

Bug#870797: marked as done (libebml4v5: Please rebuild against GCC 7 to fix bug 853553)

[Debian Bug Tracking System]

Your message dated Sun, 27 Aug 2017 21:05:34 +
with message-id 
and subject line Bug#870797: fixed in libebml 1.3.5-2
has caused the Debian Bug report #870797,
regarding libebml4v5: Please rebuild against GCC 7 to fix bug 853553
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.)


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

Dear Maintainer,

Dear Maintainer,

As explained by upstream author libebml need to be rebuilt against GCC 7
to fix mkvtoolnix build with GCC 7

See https://github.com/mbunkus/mkvtoolnix/issues/2067

Christian

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

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

Versions of packages libebml4v5 depends on:
ii  libc6   2.24-14
ii  libgcc1 1:7.1.0-12
ii  libstdc++6  7.1.0-12

libebml4v5 recommends no packages.

libebml4v5 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: libebml
Source-Version: 1.3.5-2

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

Debian distribution maintenance software
pp.
Matteo F. Vescovi  (supplier of updated libebml 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, 27 Aug 2017 22:25:13 +0200
Source: libebml
Binary: libebml4v5 libebml-dev
Architecture: source
Version: 1.3.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Matteo F. Vescovi 
Description:
 libebml-dev - access library for the EBML format (development files)
 libebml4v5 - access library for the EBML format (shared library)
Closes: 870797
Changes:
 libebml (1.3.5-2) unstable; urgency=medium
 .
   * Re-enable changes made with 1.3.4-2 revision
 and dropped by mistake in 1.3.5-1 (Closes: #870797)
Checksums-Sha1:
 133aa76126ea823eae6aa4970fe7a344ffde809a 2272 libebml_1.3.5-2.dsc
 27af36afab41d1f7a275df56f91c649ec5d0bff1 5088 libebml_1.3.5-2.debian.tar.xz
 ed9318fa8bb3a21164421e34514e3038a3533d23 5526 libebml_1.3.5-2_source.buildinfo
Checksums-Sha256:
 239a8c7a1847973d9a300bce9c15f7cca41c44e0d305a624be7a0edaaa73be50 2272 
libebml_1.3.5-2.dsc
 5f9f84cc845610d331a7ee4cabd5815c97b60107652ce0e7b3028e1ab43f1698 5088 
libebml_1.3.5-2.debian.tar.xz
 0269edcef7c2d73c5f68954e3e1f424a2cda4e4015358ae0e91c60305089355f 5526 
libebml_1.3.5-2_source.buildinfo
Files:
 414802e38156c2eb770fd2d7c5ef383e 2272 devel optional libebml_1.3.5-2.dsc
 9270e14a87b1447cb490b6b462541494 5088 devel optional 
libebml_1.3.5-2.debian.tar.xz
 0f5a3218e71c7d610530ef709bd69ace 5526 devel optional 
libebml_1.3.5-2_source.buildinfo

-BEGIN PGP SIGNATURE-
Comment: Debian powered!

iQKTBAEBCgB9FiEE890J+NqH0d9QRsmbBhL0lE7NzVoFAlmjKwZfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEYz
REQwOUY4REE4N0QxREY1MDQ2Qzk5QjA2MTJGNDk0NEVDRENENUEACgkQBhL0lE7N
zVpIKxAAjOn2RXZASU21lZ/YJXGamohTED4qQYUaC3ZRwwn0JE5hHrSaB6YESwLc
Zatw6/gAyOi1sG8F0Oy5kKHE13jfs4Euqj3gIlIjD2Kj4I/yu/W+w/3D5mm62tLZ
p9qc/xBxhpKqTSPOetx3JzGrN4h79mfHBmnPhDV/jLXZd4CYLd676JtbvFxdYG7V
GFjjNBKTgh+K0uzltfV7JLLCGKLnsYBw3d5S9NQRZOR2KayRfS6w3k4WewZy6DeR
1eS3O/LH6nRO+IEvdJi/r8YezHjJdrrJilL1KKtm7Xf8rCA33VF+mxhPBBy8ffcs
+aBvb/jes0kseAdsXfOBzfVdlaRHQoDaPOFt1QI3d7Rv7bjtR2eqsGmkKSYdnrwU
devoSm3c0c0P3KJfRT29h/EkCrZ3Rbdiu5qG3ho241mxJHuplGSKpF+7dVGet9tb
DrmiqpjQp8Feu5+Fkcc2lTOeUZ1BNQ6iyOe5c4wXaN6sRj8LZ0X9axXKWk4mOzk0
orrN99DScIKeE3s4NIjpvjWNqZbDgMafPicrF7YIxmIfDvCamC6Vf7WueEUl/ws4
gM3X6KB8zB/ZxFChTDrDjEWYtMZtuaZ4LiMJz4FyzXxg0owrN9JThcDU57hBb9bu
Ms8d4vRgMa9tpHyHZGh2JMdXknsSjuqahcQ31oEh2ZYVMUcSR7Y=
=O7fD
-END PGP SIGNATURE End Message ---

Bug#873429: marked as done (flexbar builds with -march=native)

[Debian Bug Tracking System]

Your message dated Sun, 27 Aug 2017 21:04:24 +
with message-id 
and subject line Bug#873429: fixed in flexbar 1:3.0.3-2
has caused the Debian Bug report #873429,
regarding flexbar builds with -march=native
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.)


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

FTBFS on ppc64el, but also wrong everywhere else:

https://buildd.debian.org/status/fetch.php?pkg=flexbar&arch=ppc64el&ver=1%3A3.0.3-1&stamp=1503789051&raw=0

...
cd /<>/obj-powerpc64le-linux-gnu/src && /usr/bin/c++  
-DSEQAN_HAS_BZIP2=1 -DSEQAN_HAS_ZLIB=1 -I/<>/include  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++14 
-march=native   -o CMakeFiles/flexbar.dir/Flexbar.cpp.o -c 
/<>/src/Flexbar.cpp
c++: error: unrecognized command line option '-march=native'; did you mean 
'-mcpu=native'?
src/CMakeFiles/flexbar.dir/build.make:65: recipe for target 
'src/CMakeFiles/flexbar.dir/Flexbar.cpp.o' failed
make[3]: *** [src/CMakeFiles/flexbar.dir/Flexbar.cpp.o] Error 1
--- End Message ---
--- Begin Message ---
Source: flexbar
Source-Version: 1:3.0.3-2

We believe that the bug you reported is fixed in the latest version of
flexbar, 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.
Andreas Tille  (supplier of updated flexbar 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, 27 Aug 2017 22:08:09 +0200
Source: flexbar
Binary: flexbar
Architecture: source
Version: 1:3.0.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 flexbar- flexible barcode and adapter removal for sequencing platforms
Closes: 873429
Changes:
 flexbar (1:3.0.3-2) unstable; urgency=medium
 .
   * Do not build with -march=native
 Closes: #873429
Checksums-Sha1:
 f24bd735a8eafcbc6c95c32606108ad9042dc3a3 2026 flexbar_3.0.3-2.dsc
 8e80685edd33908f15e2ee7f279db9b692da33fa 5268 flexbar_3.0.3-2.debian.tar.xz
 d0822c9102d425fea813d9bee85d12b547acae02 13206 flexbar_3.0.3-2_source.buildinfo
Checksums-Sha256:
 47e146636730227e134f3a6e7d9f5c7fde81dd9d46fa9a7549cc4e3fc2f63255 2026 
flexbar_3.0.3-2.dsc
 a986ebf67377195148e4bd31796400fc6473177fc14795884bc6fb94e966b6d1 5268 
flexbar_3.0.3-2.debian.tar.xz
 bdc24f72df99a6c572dd2a1eac1a74ed68b76b31a43ac0026d863c5ab3ab7511 13206 
flexbar_3.0.3-2_source.buildinfo
Files:
 94cf21554d86c6a2ac0b614c67f367c7 2026 science optional flexbar_3.0.3-2.dsc
 0d5793b7409a8871d5a2de7641adf392 5268 science optional 
flexbar_3.0.3-2.debian.tar.xz
 7274718a3f8a8557955ed6c0eef0e61b 13206 science optional 
flexbar_3.0.3-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJCBAEBCgAsFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlmjLx4OHHRpbGxlYUBy
a2kuZGUACgkQV4oElNHGRtFM8hAAiDzCwQ4cz3CD0/Kpruk7uSV0iegGMj7kO0gI
WqEbGx5sQUd2pyoUmHg6wNFT+au+5fdJsqe1ZwpDXZqGvUzbK6K6ApJ8VT9M+6Cj
EzA3z1MsiEbFeOr0U3eDv9q4YnzEpd/xqXTE63zxJVYaqBphS6ncH++EiPiqZpLW
10V8pL8UjgjX2OZQ2IOr7dIfLVZGu16qqJno/G1vpxI8PQgpK/SgOk71hnPhxPDh
u7dy606zOomOD8FQdzji1dMTckKKbyEgaUR85BwANKARB+bctatDBGBfZiH0O1aN
5Jmd59tBjTcGExK0POas/apvtM5ogJ6ZodumIe7rCpHRboVMFY3Ni5y2QeXzffcO
8BMaiMLk7fbXSXEpRKZGLhWJz/RrFSB8kQmNIQlNkgXvkgPBe0mBco3B+Y0Sznci
rrCAil2scYQF9HNw9QWGkcs+6o41o1MUmHXfv2Phcq53U4pjJrK5spN2tdu2KHJV
o3tCnBZOdBHX3xBty9XANLAQZXvWir2i+pcj4BRjBLbHhcoD84O7HxFcfLSq1ERL
Q37t7oxb3R2MGK0Ku1bbnbnd3lqltn6P4gcb8Q3kRBKAbIma1H25utJ0iADE5N2A
Xg6B6ZglZgC7xJzNXm8Ey3mKpx1bpdplxRyEjymtKIJhkfW8JSf4X746zRQQIHYw
4X/hnXU=
=Cm9I
-END PGP SIGNATURE End Message ---

Processed: Bug#870797 marked as pending

[Debian Bug Tracking System]

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

> tag 870797 pending
Bug #870797 {Done: James Cowgill } [libebml4v5] 
libebml4v5: Please rebuild against GCC 7 to fix bug 853553
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#870797: marked as pending

[Matteo F . Vescovi]

tag 870797 pending
thanks

Hello,

Bug #870797 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:

http://anonscm.debian.org/git/pkg-multimedia/libebml.git/commit/?id=3af8bfe

---
commit 3af8bfe92ab51fb5873ac901ac6c3979d4c2d02f
Author: Matteo F. Vescovi 
Date:   Sun Aug 27 22:24:43 2017 +0200

debian/changelog: new revision entry added

Gbp-Dch:Ignore

diff --git a/debian/changelog b/debian/changelog
index 1ddd37d..dc54e0e 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+libebml (1.3.5-2) UNRELEASED; urgency=medium
+
+  * Re-enable changes made with 1.3.4-2 revision
+and dropped by mistake in 1.3.5-1 (Closes: #870797)
+
+ -- Matteo F. Vescovi   Sun, 27 Aug 2017 22:23:00 +0200
+
 libebml (1.3.5-1) unstable; urgency=medium
 
   * New upstream release (Closes: #872775)

Bug#871114: widelands: FTBFS: game_settings.h:52:8: error: 'newuser.UserSettings::position' may be used uninitialized in this function [-Werror=maybe-uninitialized]

[Hans Joachim Desserud]

Funny. It seems we worked on this bug at the same time. I can confirm
that [2] resolved the FTBFS with GCC 7.


Looks like it. :) Thanks for uploading the patch and the other packaging
changes. (I've already picked it up and integrated it into the packaging
we do upstream for our PPA [1])

I've also added a short description and pointing to the backported patch
in the original GCC7-merge proposal for others who may come across it.


I suggest to add a simple patch to bug reports
next time which tremendously simplifies things for non-regular 
uploaders

of Widelands.


Yes, I considered adding a patch. The main reason I didn't is that I use
quilt too seldom to really remember how it works from time to time. So
I would need to look up the commands, which is not neccessarily hard, 
but

takes time and I knew I would be busy the following days. Since I didn't
know when I'd have the time to prepare a proper patch, I figuered I 
could

at least point to the existing patch, so that no one would need to add
GCC7 support from scratch. If it hadn't been picked up, I would have
prepared a patch when I got the time, but it seemed quicker to add a 
link

and let someone who knew the toolchain integrate it.

If I find the time, there will be a proper patch next time ;)

[1] https://code.launchpad.net/~hjd/widelands/debian-merge/+merge/329686

---
mvh / best regards
Hans Joachim Desserud
http://desserud.org

Bug#784490: marked as done ([kvirc] Qt4's WebKit removal)

[Debian Bug Tracking System]

Your message dated Sun, 27 Aug 2017 19:34:20 +
with message-id 
and subject line Bug#784490: fixed in kvirc 4:4.9.2~git20170827-1
has caused the Debian Bug report #784490,
regarding [kvirc] Qt4's WebKit removal
to be marked as done.

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

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


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

Dear Debian KDE Extras Team ,

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

[announce] 


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

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

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

= Porting =

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

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

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

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

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

Ana,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
Source: kvirc
Source-Version: 4:4.9.2~git20170827-1

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

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

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

Debian distribution maintenance software
pp.
Andrey Rahmatullin  (supplier of updated kvirc 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, 27 Aug 2017 19:34:16 +0500
Source: kvirc
Binary: kvirc libkvilib4 kvirc-modules kvirc-data
Architecture: source
Version: 4:4.9.2~git20170827-1
Distribution: experimental
Urgency: medium
Maintainer: Debian KDE Extras Team 
Changed-By: Andrey Rahmatullin 
Description:
 kvirc  - KDE-based next generation IRC client with module support
 kvirc-data - Data files for KVIrc
 kvirc-modules - KVIrc (IRC client) modules
 libkvilib4 - KVIrc (IRC client) base library
Closes: 784490 872289
Changes:
 kvirc (4:4.9.2~git20170827-1) experimental; urgency=medium
 .
   * Team upload.
   * Upload to experimental.
   * Add myself to Uploaders.
   * Package the current development snapshot, using Qt5 (Closes: #784490,
 #872289).
 + doesn't install /usr/share/kde4/apps/kvirc/kvirc.notifyrc and
   /usr/share/kde4/services/irc*.protocol
   * Update the B-D accordingly.
   * Update the cmake B-D minimum version to 3.1.0.
   * Don't use -Wl,--no-undefined as it doesn't work with the modules.
   * Don't install anything into /usr/share/pixmaps.
   * Install /usr/share/mime/packages/kvirc.xml manually as the upstream
 currently doesn't do that.
   * Update the expression for -DMANUAL_REVISION to work with git snapshot
 versions.
Checksums-Sha1:
 e37f897c910bd54d20909ef2fc94f4786a7d4aa5 2664 kvirc_4.9.2~git20170827-1.dsc
 d928b91c2da49ad15dbca030ac13e8bbdcd29afb 3699460 
kvirc_4.9.2~git20170

Bug#873444: goldencheetah FTBFS with Qt 5.9: error: 'QObject' is an ambiguous base of 'MoxyDevice'

[Adrian Bunk]

Source: goldencheetah
Version: 4.0.0~DEV1607-2
Severity: serious
Tags: buster sid

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

...
In file included from 
/usr/include/x86_64-linux-gnu/qt5/QtCore/qsharedpointer.h:48:0,
 from /usr/include/x86_64-linux-gnu/qt5/QtGui/qpixmap.h:48,
 from /usr/include/x86_64-linux-gnu/qt5/QtGui/qbrush.h:52,
 from /usr/include/x86_64-linux-gnu/qt5/QtGui/qpalette.h:46,
 from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qwidget.h:48,
 from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qmenu.h:44,
 from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QMenu:1,
 from Charts/GoldenCheetah.h:31,
 from FileIO/CommPort.h:21,
 from FileIO/MoxyDevice.h:22,
 from FileIO/MoxyDevice.cpp:19:
/usr/include/x86_64-linux-gnu/qt5/QtCore/qsharedpointer_impl.h: In 
instantiation of 'void QSharedPointer::internalConstruct(X*, Deleter) [with 
X = MoxyDevice; Deleter = QtSharedPointer::NormalDeleter; T = Device]':
/usr/include/x86_64-linux-gnu/qt5/QtCore/qsharedpointer_impl.h:319:24:   
required from 'QSharedPointer::QSharedPointer(X*) [with X = MoxyDevice; T = 
Device]'
FileIO/MoxyDevice.cpp:41:44:   required from here
/usr/include/x86_64-linux-gnu/qt5/QtCore/qsharedpointer_impl.h:494:9: error: 
'QObject' is an ambiguous base of 'MoxyDevice'
 d->setQObjectShared(ptr, true);
 ^
Makefile:161213: recipe for target 'MoxyDevice.o' failed
make[2]: *** [MoxyDevice.o] Error 1

Processed: Fixed in the upstream 6.4 branch

[Debian Bug Tracking System]

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

> tags 768843 fixed-upstream
Bug #768843 [fetchmail] fetchmail: Improved TLS support
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#859294: hunspell-dict-ko: FTBFS: UnicodeDecodeError: 'ascii' codec can't decode byte 0xed in position 38: ordinal not in range(128)

[Changwoo Ryu]

OK, another encoding= parameter is needed.

--- a/make-aff-dic.py
+++ b/make-aff-dic.py
@@ -200,7 +200,7 @@ class Dictionary:
 def output_aff(self, outfile):
 from string import Template
 import aff
-template = Template(open('template.aff').read())
+template = Template(open('template.aff', encoding='utf-8').read())

 # 주의: flag alias를 변경하므로 get_AF() 앞에 와야 한다.
 suffix_str = aff.get_suffix_defines(self.flag_aliases)

Actually I'm the upstream maintainer so it will be applied in the next
upstream revision.


2017-08-28 3:36 GMT+09:00 Adrian Bunk :
> Control: reopen -1
>
> On Wed, Apr 05, 2017 at 12:53:33PM +0900, Changwoo Ryu wrote:
>> OK I found a way of specifying the encoding of the I/O files.
>>
>>
>> diff --git a/make-aff-dic.py b/make-aff-dic.py
>> index 47dff10..98aba41 100644
>> --- a/make-aff-dic.py
>> +++ b/make-aff-dic.py
>> @@ -308,9 +308,9 @@ if __name__ == '__main__':
>>  dic = Dictionary()
>>  for filename in infilenames:
>>  if filename.endswith('.json'):
>> -dic.load_json(open(filename))
>> +dic.load_json(open(filename, encoding='utf-8'))
>>  else:
>>  print('ERROR: unknown file type: ' + filename)
>>  sys.exit(1)
>>  dic.process()
>> -dic.output(open(afffilename, 'w'), open(dicfilename, 'w'))
>> +dic.output(open(afffilename, 'w', encoding='utf-8'),
>> open(dicfilename, 'w', encoding='utf-8'))
>>
>>
>> 2017-04-05 12:44 GMT+09:00 Changwoo Ryu :
>> > It only fails on a legacy non-Unicode locale, such as "C".
>> >
>> > So what is a solution? Specifying a UTF-8 locale and Build-Depending
>> > on locales-all do not seems to be a right way.
>
> Unfortunately it is still failing (this time in a different place?):
>
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/hunspell-dict-ko.html
>
> ...
> make[1]: Entering directory '/build/1st/hunspell-dict-ko-0.6.3'
> python3 make-aff-dic.py ko.aff ko.dic dict-ko-builtins.json
> dict-ko-galkwi-ccby.json dict-ko-galkwi-mplgpllgpl.json
> Progress: \ubcf5\uc218\ud615 \ud655\uc7a5...
> Progress: \ud50c\ub798\uadf8 \uacc4\uc0b0...
> Progress: \ubcf4\uc870\uc6a9\uc5b8 \ud655\uc7a5...
> Progress: dic \ucd9c\ub825...
> Progress: aff \ucd9c\ub825...
> Traceback (most recent call last):
>   File "make-aff-dic.py", line 333, in 
> open(dicfilename, 'w', encoding='utf-8'))
>   File "make-aff-dic.py", line 181, in output
> self.output_aff(afffile)
>   File "make-aff-dic.py", line 203, in output_aff
> template = Template(open('template.aff').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
> 423: ordinal not in range(128)
> Makefile:28: recipe for target 'ko.aff' failed
> make[1]: *** [ko.aff] Error 1
> make[1]: Leaving directory '/build/1st/hunspell-dict-ko-0.6.3'
> dh_auto_build: make -j1 returned exit code 2
> debian/rules:5: recipe for target 'build' failed
> make: *** [build] Error 2
>
>
> cu
> Adrian
>
> --
>
>"Is there not promise of rain?" Ling Tan asked suddenly out
> of the darkness. There had been need of rain for many days.
>"Only a promise," Lao Er said.
>Pearl S. Buck - Dragon Seed
>

Bug#784512: [Python-modules-team] Bug#784512: Is anybody working on PySide2?

[W. Martin Borgert]

On 2017-08-27 16:43, Scott Kitterman wrote:
> If python-ghost can't use PyQt5 instead (some packages are written to work 
> with either), then if you want to keep it in the archive, I would plan on 
> packaging pyside2.

Ghost uses only PySide2 in 2.0.0-dev. Because I have no
knowledge of Qt at all (nor too much time to invest), I cannot
package PySide2. I'll ask Ghost upstream about the issue. Maybe
one can add an alternative API, such as Qt5 or something GIR
based...

Bug#873437: command-execute: Cannot open load file: No such file or directory, go-mode

[Hilko Bengen]

Control: tag -1 moreinfo

* Jameson Graef Rollins:

> I don't understand the new elpa system, but for whatever reason this
> packages is not actually providing go-mode for me.  When I try "M-x
> go-mode" I get the following error:
>
> command-execute: Cannot open load file: No such file or directory, go-mode

Does this problem persist in a freshly-started instance of Emacs?

> This is on emacs 25.2.1.

I can't reproduce the problem on 25.2.2.

Cheers,
-Hilko

Processed: severity of 868558 is normal

[Debian Bug Tracking System]

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

> severity 868558 normal
Bug #868558 [release.debian.org] nmu: multiple r-* packages
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Processed: Re: Bug#873437: command-execute: Cannot open load file: No such file or directory, go-mode

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo
Bug #873437 [elpa-go-mode] command-execute: Cannot open load file: No such file 
or directory, go-mode
Added tag(s) moreinfo.

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

Bug#859294: hunspell-dict-ko: FTBFS: UnicodeDecodeError: 'ascii' codec can't decode byte 0xed in position 38: ordinal not in range(128)

[Adrian Bunk]

Control: reopen -1

On Wed, Apr 05, 2017 at 12:53:33PM +0900, Changwoo Ryu wrote:
> OK I found a way of specifying the encoding of the I/O files.
> 
> 
> diff --git a/make-aff-dic.py b/make-aff-dic.py
> index 47dff10..98aba41 100644
> --- a/make-aff-dic.py
> +++ b/make-aff-dic.py
> @@ -308,9 +308,9 @@ if __name__ == '__main__':
>  dic = Dictionary()
>  for filename in infilenames:
>  if filename.endswith('.json'):
> -dic.load_json(open(filename))
> +dic.load_json(open(filename, encoding='utf-8'))
>  else:
>  print('ERROR: unknown file type: ' + filename)
>  sys.exit(1)
>  dic.process()
> -dic.output(open(afffilename, 'w'), open(dicfilename, 'w'))
> +dic.output(open(afffilename, 'w', encoding='utf-8'),
> open(dicfilename, 'w', encoding='utf-8'))
> 
> 
> 2017-04-05 12:44 GMT+09:00 Changwoo Ryu :
> > It only fails on a legacy non-Unicode locale, such as "C".
> >
> > So what is a solution? Specifying a UTF-8 locale and Build-Depending
> > on locales-all do not seems to be a right way.

Unfortunately it is still failing (this time in a different place?):

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/hunspell-dict-ko.html

...
make[1]: Entering directory '/build/1st/hunspell-dict-ko-0.6.3'
python3 make-aff-dic.py ko.aff ko.dic dict-ko-builtins.json 
dict-ko-galkwi-ccby.json dict-ko-galkwi-mplgpllgpl.json 
Progress: \ubcf5\uc218\ud615 \ud655\uc7a5...
Progress: \ud50c\ub798\uadf8 \uacc4\uc0b0...
Progress: \ubcf4\uc870\uc6a9\uc5b8 \ud655\uc7a5...
Progress: dic \ucd9c\ub825...
Progress: aff \ucd9c\ub825...
Traceback (most recent call last):
  File "make-aff-dic.py", line 333, in 
open(dicfilename, 'w', encoding='utf-8'))
  File "make-aff-dic.py", line 181, in output
self.output_aff(afffile)
  File "make-aff-dic.py", line 203, in output_aff
template = Template(open('template.aff').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 
423: ordinal not in range(128)
Makefile:28: recipe for target 'ko.aff' failed
make[1]: *** [ko.aff] Error 1
make[1]: Leaving directory '/build/1st/hunspell-dict-ko-0.6.3'
dh_auto_build: make -j1 returned exit code 2
debian/rules:5: recipe for target 'build' failed
make: *** [build] Error 2


cu
Adrian

-- 

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

Bug#873362: coinor-libcoinutils3v5: unannounced ABI change without SONAME change?

[Anton Gladky]

Hi Mattia,

thanks for the tip! I have recompiled both libs with the same
current gcc-7.2. And it looks like there are no dropped symbols
(see file old-gcc7_new-gcc7.diff in attachment).

But if I compare new so-file with the one shipped with Stretch
(compiled with gcc6)
the diff contains some missing symbols (see file  old-gcc6_new-gcc7.diff).

What is the best practice for such kind of libs? Provide symbol-files?

Thank you

PS I have generated the symbols with the command:
  readelf -Ws libCoinUtils.so |  awk '{print $8}'

Anton


2017-08-27 18:04 GMT+02:00 Mattia Rizzolo :
> On Sun, Aug 27, 2017 at 03:16:46PM +0200, Anton Gladky wrote:
>> > Still I believe that this should be "correctly" fixed.
>>
>> You mean to increase so-version even if upstream does not do it and
>> to start the normal transition process? I think it is possible.
>
> That's actually your only option.
> Could someone check the symbols of the library before and after the
> upload and check whether some have been dropped?  If there are, not
> bumping SONAME is a bug upstream should deal with by doing another
> release and doing so (and failing so, in Debian you should at the very
> least rename the binary package (doing somethng alike to the v5 thing
> done for libstdc++5)).
>
> --
> 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  `-
diff --git a/symb_old_gcc6 b/symb_new_gcc7
index b2c7fe0..81b10dc 100644
--- a/symb_old_gcc6
+++ b/symb_new_gcc7
@@ -9,7 +9,6 @@ BZ2_bzWrite
 BZ2_bzWriteClose
 BZ2_bzWriteOpen
 calloc@GLIBC_2.2.5
-ceil@GLIBC_2.2.5
 c_ekkbtrn
 c_ekkbtrn_ipivrw
 c_ekketsj
@@ -70,7 +69,6 @@ isalnum@GLIBC_2.2.5
 isalpha@GLIBC_2.2.5
 _ITM_deregisterTMCloneTable
 _ITM_registerTMCloneTable
-_Jv_RegisterClasses
 log10@GLIBC_2.2.5
 log@GLIBC_2.2.5
 malloc@GLIBC_2.2.5
@@ -79,6 +77,7 @@ __memcpy_chk@GLIBC_2.3.4
 memcpy@GLIBC_2.14
 memmove@GLIBC_2.2.5
 memset@GLIBC_2.2.5
+modf@GLIBC_2.2.5
 pow@GLIBC_2.2.5
 __printf_chk@GLIBC_2.3.4
 putchar@GLIBC_2.2.5
@@ -109,7 +108,6 @@ strstr@GLIBC_2.2.5
 strtod@GLIBC_2.2.5
 strtol@GLIBC_2.2.5
 tolower@GLIBC_2.2.5
-trunc@GLIBC_2.2.5
 _Unwind_Resume@GCC_3.0
 _Z10c_ekkputl2PK12_EKKfactinfoPdS2_i
 _Z10clp_doublei
@@ -135,11 +133,13 @@ 
_Z11fileAbsPathRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE
 _Z11log_wrapperd
 _Z11sin_wrapperd
 _Z12atan_wrapperd
+_Z12ceil_wrapperd
 _Z12CoinFromFileIdEiRPT_iP8_IO_FILERi
 _Z12CoinFromFileIiEiRPT_iP8_IO_FILERi
 _Z12fabs_wrapperd
 _Z12remove_fixedP18CoinPresolveMatrixPK18CoinPresolveAction
 _Z12sqrt_wrapperd
+_Z13floor_wrapperd
 _Z13testRedundantP18CoinPresolveMatrixPK18CoinPresolveAction
 _Z13transferCostsP18CoinPresolveMatrix
 _Z16check_tripletonsPK18CoinPresolveAction
@@ -158,7 +158,6 @@ 
_Z22drop_zero_coefficientsP18CoinPresolveMatrixPK18CoinPresolveAction
 _Z22presolve_make_memlistsPiP13presolvehlinki
 _Z24WindowsErrorPopupBlockerv
 _Z26getFunctionValueFromStringPKcS0_d
-_Z26presolve_delete_from_majoriiPKiPiS1_Pd
 _Z27presolve_delete_from_major2iiPiS_S_S_S_
 _Z7clp_inti
 _Z8clp_freePv
@@ -179,10 +178,10 @@ 
_Z9c_ekkrwctPK12_EKKfactinfoPdPiS3_PKiPK8EKKHlinkS8_PKsS2_ii
 _Z9c_ekkshffP12_EKKfactinfoP8EKKHlinkS2_i
 _Z9c_ekkshfvP12_EKKfactinfoP8EKKHlinkS2_i
 _Z9c_ekktriaP12_EKKfactinfoP8EKKHlinkS2_PiS3_S3_S3_i
+_Z9check_rowPiPdS_S_ddii
 _Z9CoinCopyNIdEvPKT_iPS0_
 _Z9CoinCopyNIiEvPKT_iPS0_
 _Z9CoinFillNIiEvPT_iS0_
-_Z9CoinFillNItEvPT_iS0_
 _Z9CoinIsnand
 _Z9CoinZeroNIdEvPT_i
 _Z9CoinZeroNIiEvPT_i
@@ -223,6 +222,7 @@ _ZN12CoinMessagesC2Ei
 _ZN12CoinMessagesC2ERKS_
 _ZN12CoinMessagesD1Ev
 _ZN12CoinMessagesD2Ev
+_ZN12CoinRational16nearestRational_Eddl
 _ZN12CoinRelFltEqD0Ev
 _ZN12CoinRelFltEqD1Ev
 _ZN12CoinRelFltEqD2Ev
@@ -358,6 +358,10 @@ 
_ZN14CoinSearchTreeI26CoinSearchTreeCompareDepthE8realpushEP16CoinTreeSiblings
 _ZN14CoinSearchTreeI26CoinSearchTreeCompareDepthED0Ev
 _ZN14CoinSearchTreeI26CoinSearchTreeCompareDepthED1Ev
 _ZN14CoinSearchTreeI26CoinSearchTreeCompareDepthED2Ev
+_ZN14duprow3_action8presolveEP18CoinPresolveMatrixPK18CoinPresolveAction
+_ZN14duprow3_actionD0Ev
+_ZN14duprow3_actionD1Ev
+_ZN14duprow3_actionD2Ev
 _ZN14FactorPointersC1EiiPiS0_
 _ZN14FactorPointersC2EiiPiS0_
 _ZN14FactorPointersD1Ev
@@ -1142,6 +1146,8 @@ _ZN8CoinLpIO6readLpEP8_IO_FILEd
 _ZN8CoinLpIO6readLpEPKc
 _ZN8CoinLpIO6readLpEPKcd
 _ZN8CoinLpIO7freeAllEv
+_ZN8CoinLpIO7loadSOSEiPK7CoinSet
+_ZN8CoinLpIO7loadSOSEiPPK7CoinSet
 _ZN8CoinLpIO7writeLpEP8_IO_FILEb
 _ZN8CoinLpIO7writeLpEP8_IO_FILEdiib
 _ZN8CoinLpIO7writeLpEPKcb
@@ -1340,6 +1346,8 @@ _ZNK14CoinFileIOBase11getFileNameEv
 _ZNK14CoinModelHash24hashEiiPK15CoinModelTriple
 _ZNK14CoinModelHash29hashValueEii
 _ZNK14CoinSearchTreeI26CoinSearchTreeCompareDepthE8compNameEv
+_ZNK14duprow3_action4nameEv
+_ZNK14duprow3_action9postsolveEP19CoinPostsolve

Processed: Re: Bug#859294: hunspell-dict-ko: FTBFS: UnicodeDecodeError: 'ascii' codec can't decode byte 0xed in position 38: ordinal not in range(128)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #859294 {Done: Changwoo Ryu } [src:hunspell-dict-ko] 
hunspell-dict-ko: FTBFS: UnicodeDecodeError: 'ascii' codec can't decode byte 
0xed in position 38: ordinal not in range(128)
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions hunspell-dict-ko/0.6.2-1.

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

Processed: Re: Bug#870253: clamav-milter: disengaging debconf management destroys config

[Debian Bug Tracking System]

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

> tags 870253 pending
Bug #870253 [clamav-milter] clamav-milter: disengaging debconf management 
destroys config
Added tag(s) pending.
>
End of message, stopping processing here.

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

Bug#873440: ruby-grpc FTBFS: cc1: error: -Wformat-security ignored without -Wformat

[Adrian Bunk]

Source: ruby-grpc
Version: 1.3.2+debian-3
Severity: serious

https://buildd.debian.org/status/package.php?p=ruby-grpc&suite=sid

...
gcc -I. -I/usr/include/aarch64-linux-gnu/ruby-2.3.0 
-I/usr/include/ruby-2.3.0/ruby/backward -I/usr/include/ruby-2.3.0 -I. 
-Wdate-time -D_FORTIFY_SOURCE=2   -fPIC -g -O2 
-fdebug-prefix-map=/build/ruby2.3-gbHtXr/ruby2.3-2.3.3=. 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC 
-I/<>/ruby-grpc-1.3.2+debian/debian/ruby-grpc/usr/lib/aarch64-linux-gnu/rubygems-integration/2.3.0/gems/grpc-1.3.2/include
 -std=c99  -Wall  -Wextra  -pedantic  -Wno-format   -o rb_byte_buffer.o -c 
rb_byte_buffer.c
cc1: error: -Wformat-security ignored without -Wformat [-Werror=format-security]

Bug#853441: marked as done (hexcurse: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Sun, 27 Aug 2017 18:19:41 +
with message-id 
and subject line Bug#853441: fixed in hexcurse 1.58-1.1
has caused the Debian Bug report #853441,
regarding hexcurse: 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.)


-- 
853441: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853441
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:hexcurse
Version: 1.58-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/hexcurse_1.58-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

[...]
configure: WARNING: unrecognized options: --disable-silent-rules, 
--disable-maintainer-mode
   dh_auto_build
make -j1
make[1]: Entering directory '/<>'
make  all-recursive
make[2]: Entering directory '/<>'
Making all in src
make[3]: Entering directory '/<>/src'
gcc -DHAVE_CONFIG_H -I. -I..  -I../include -Wall -Werror -Wextra -Wdate-time 
-D_FORTIFY_SOURCE=2  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c file.c
gcc -DHAVE_CONFIG_H -I. -I..  -I../include -Wall -Werror -Wextra -Wdate-time 
-D_FORTIFY_SOURCE=2  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c llist.c
gcc -DHAVE_CONFIG_H -I. -I..  -I../include -Wall -Werror -Wextra -Wdate-time 
-D_FORTIFY_SOURCE=2  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c screen.c
gcc -DHAVE_CONFIG_H -I. -I..  -I../include -Wall -Werror -Wextra -Wdate-time 
-D_FORTIFY_SOURCE=2  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c hexcurse.c
hexcurse.c: In function 'main':
hexcurse.c:227:54: error: output truncated before the last format character 
[-Werror=format-truncation=]
 min_address_length = snprintf(buffer, 1, "%jd", (intmax_t)len);
   ~~~^
In file included from /usr/include/stdio.h:938:0,
 from ../include/hex.h:23,
 from hexcurse.c:25:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:64:10: note: format output between 
2 and 21 bytes into a destination of size 1
   return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
  ^~~~
__bos (__s), __fmt, __va_arg_pack ());
~
hexcurse.c: In function 'getMinimumAddressLength':
hexcurse.c:227:54: error: output truncated before the last format character 
[-Werror=format-truncation=]
 min_address_length = snprintf(buffer, 1, "%jd", (intmax_t)len);
   ~~~^
In file included from /usr/include/stdio.h:938:0,
 from ../include/hex.h:23,
 from hexcurse.c:25:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:64:10: note: format output between 
2 and 21 bytes into a destination of size 1
   return __builtin___snprintf_chk (__s, __n, __USE_FORTIFY_LEVEL - 1,
  ^~~~
__bos (__s), __fmt, __va_arg_pack ());
~
cc1: all warnings being treated as errors
Makefile:258: recipe for target 'hexcurse.o' failed
make[3]: *** [hexcurse.o] Error 1
make[3]: Leaving directory '/<>/src'
Makefile:266: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory '/<>'
Makefile:206: rec

Bug#873439: flightgear: CVE-2017-13709: Incorrect access control

[Salvatore Bonaccorso]

Source: flightgear
Version: 1:2017.2.1+dfsg-3
Severity: grave
Tags: upstream security

Hi,

the following vulnerability was published for flightgear.

CVE-2017-13709[0]:
| In FlightGear before version 2017.3.1, Main/logger.cxx in the FGLogger
| subsystem allows one to overwrite any file via a resource that affects
| the contents of the global Property Tree.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-13709
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-13709
[1] http://www.openwall.com/lists/oss-security/2017/08/27/1

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#873437: command-execute: Cannot open load file: No such file or directory, go-mode

[Jameson Graef Rollins]

Package: elpa-go-mode
Version: 3:1.5.0-1
Severity: grave
Justification: renders package unusable

I don't understand the new elpa system, but for whatever reason this
packages is not actually providing go-mode for me.  When I try "M-x
go-mode" I get the following error:

command-execute: Cannot open load file: No such file or directory, go-mode

This is on emacs 25.2.1.

Please let me know if there's any more information I can provide.  Thanks.

jamie.


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

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

Versions of packages elpa-go-mode depends on:
ii  emacsen-common  2.0.8

Versions of packages elpa-go-mode recommends:
pn  golang-golang-x-tools  

elpa-go-mode suggests no packages.

-- no debconf information

Bug#784512: [Python-modules-team] Bug#784512: Is anybody working on PySide2?

[Scott Kitterman]

On August 27, 2017 11:13:36 AM EDT, Didier 'OdyX' Raboud  
wrote:
>Le dimanche, 27 août 2017 16.53:30 h CEST, vous avez écrit :
>> Hi,
>> 
>> python-ghost depends on pyside, which will be removed with Qt4.
>> Upstream already ported to pyside2, but I can't find pyside2 in
>> Debian, not even an ITP or RFP. But somewhere I read, that
>> pyside2 will be part of Qt. Is somebody working on this? It
>> would be bad to remove pyside from Debian before pyside2 is in
>> place, right?
>
>For what is worth: I'm not working on pyside, nor pyside2. I removed
>myself 
>from both shiboken and pyside's uploader fields (but should really have
>mailed 
>debian-python about that earlier).

Other than transition related fixes (if you can call disabling tests fixes), I 
don't think anyone has worked on pyside in a long time.

You should consider it orphaned in any practical sense.

If python-ghost can't use PyQt5 instead (some packages are written to work with 
either), then if you want to keep it in the archive, I would plan on packaging 
pyside2.

Qt4 has been unmaintained upstream for many years and it needs to go.

It does look like you're correct that pyside2 is being developed as part of the 
Qt project:

https://wiki.qt.io/PySide2

Given that, we should have it in Debian, but I'm not likely to have time to 
work on it myself.

Scott K

Bug#873341: SBT is uninstallable; depends on nonexistent packages

[tony mancill]

On Sat, Aug 26, 2017 at 06:52:24PM +, David Starner wrote:
> Package: sbt
> Version: 0.13.13-2
> Severity: serious
> 
> sbt is not installable; it depends on various packages like
> sbt-test-interface that only exist in experimental.

Hi David,

Thank you for the bug report.

We're working on one last package in the dependency change,
scala-tools-sbinary, and then we can start the migration from
experimental to unstable.

Regards,
tony


signature.asc
Description: PGP signature

Bug#873429: flexbar builds with -march=native

[Adrian Bunk]

Source: flexbar
Version: 1:3.0.3-1
Severity: serious

FTBFS on ppc64el, but also wrong everywhere else:

https://buildd.debian.org/status/fetch.php?pkg=flexbar&arch=ppc64el&ver=1%3A3.0.3-1&stamp=1503789051&raw=0

...
cd /<>/obj-powerpc64le-linux-gnu/src && /usr/bin/c++  
-DSEQAN_HAS_BZIP2=1 -DSEQAN_HAS_ZLIB=1 -I/<>/include  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++14 
-march=native   -o CMakeFiles/flexbar.dir/Flexbar.cpp.o -c 
/<>/src/Flexbar.cpp
c++: error: unrecognized command line option '-march=native'; did you mean 
'-mcpu=native'?
src/CMakeFiles/flexbar.dir/build.make:65: recipe for target 
'src/CMakeFiles/flexbar.dir/Flexbar.cpp.o' failed
make[3]: *** [src/CMakeFiles/flexbar.dir/Flexbar.cpp.o] Error 1

Bug#873362: coinor-libcoinutils3v5: unannounced ABI change without SONAME change?

[Mattia Rizzolo]

On Sun, Aug 27, 2017 at 03:16:46PM +0200, Anton Gladky wrote:
> > Still I believe that this should be "correctly" fixed.
> 
> You mean to increase so-version even if upstream does not do it and
> to start the normal transition process? I think it is possible.

That's actually your only option.
Could someone check the symbols of the library before and after the
upload and check whether some have been dropped?  If there are, not
bumping SONAME is a bug upstream should deal with by doing another
release and doing so (and failing so, in Debian you should at the very
least rename the binary package (doing somethng alike to the v5 thing
done for libstdc++5)).

-- 
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  `-


signature.asc
Description: PGP signature

Bug#873426: frobby: frequent parallel FTBFS

[Adrian Bunk]

Source: frobby
Version: 0.9.0-4
Severity: serious

Example:

https://buildd.debian.org/status/fetch.php?pkg=frobby&arch=i386&ver=0.9.0-4&stamp=1503827903&raw=0

...
Transcript written on bin/doc//manual.log.
cd bin; dvips doc/manual.dvi
rm -rf bin/doc
mkdir bin/doc
for i in 1 2 3; do pdflatex -output-directory=bin/doc/ doc/manual.tex; done
This is dvips(k) 5.997 Copyright 2017 Radical Eye Software (www.radicaleye.com)
dvips: DVI file can't be opened: doc/manual.dvi: No such file or directory
Makefile:253: recipe for target 'docPs' failed
make[2]: *** [docPs] Error 1
make[2]: *** Waiting for unfinished jobs
...


dh compat 10 defaults to parallel building, if this cannot easily
be fixed then calling dh with --no-parallel brings gives what was
previously the default.

Bug#871213: marked as done (rosegarden: FTBFS: make[3]: *** No rule to make target 'src/svnversion.h', needed by 'src/CMakeFiles/rosegardenprivate_autogen'. Stop.)

[Debian Bug Tracking System]

Your message dated Sun, 27 Aug 2017 15:50:25 +
with message-id 
and subject line Bug#871213: fixed in rosegarden 1:17.04-1
has caused the Debian Bug report #871213,
regarding rosegarden: FTBFS: make[3]: *** No rule to make target 
'src/svnversion.h', needed by 'src/CMakeFiles/rosegardenprivate_autogen'. Stop.
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.)


-- 
871213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871213
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rosegarden
Version: 1:16.06-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):
> make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
> make[3]: *** No rule to make target 'src/svnversion.h', needed by 
> 'src/CMakeFiles/rosegardenprivate_autogen'.  Stop.
> make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
> CMakeFiles/Makefile2:1103: recipe for target 
> 'src/CMakeFiles/rosegardenprivate_autogen.dir/all' failed
> make[2]: *** [src/CMakeFiles/rosegardenprivate_autogen.dir/all] Error 2

The full build log is available from:
   http://aws-logs.debian.net/2017/08/05/rosegarden_16.06-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: rosegarden
Source-Version: 1:17.04-1

We believe that the bug you reported is fixed in the latest version of
rosegarden, 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.
Stuart Prescott  (supplier of updated rosegarden 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 00:36:33 +1000
Source: rosegarden
Binary: rosegarden
Architecture: source
Version: 1:17.04-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Stuart Prescott 
Closes: 871213
Description: 
 rosegarden - music editor and MIDI/audio sequencer
Changes:
 rosegarden (1:17.04-1) unstable; urgency=medium
 .
   * New upstream release.
   * Switch to Qt5 build.
   * Bump standards-version to 4.1.0 (no changes required).
   * Fix generation of 'src/svnversion.h' to prevent FTBFS with CMake 3.9
 (Closes: #871213).
Checksums-Sha1: 
 04239ffc668e9f15158e9b9cd6bf73f4820feb73 2286 rosegarden_17.04-1.dsc
 73271aa7779db4a627fa4060996a879ec0009292 6454603 rosegarden_17.04.orig.tar.bz2
 94848d96ba201aaceb698007bcc2500554c20dae 12536 rosegarden_17.04-1.debian.tar.xz
Checksums-Sha256: 
 9ef93f56cfc2940dd013ea46845fac8036c1aff98f53eb10bb31afcee5abf911 2286 
rosegarden_17.04-1.dsc
 988a6141c5b0a8e85c029f650de78bf57100c4d778c22d0194b0692584640ece 6454603 
rosegarden_17.04.orig.tar.bz2
 f1004eeaa445869c99f5b607e6c45fa58dec27ebc565d0d1cdf76aff951e28ac 12536 
rosegarden_17.04-1.debian.tar.xz
Files: 
 80266e07b664b184b86f1c61745d8fd1 2286 sound optional rosegarden_17.04-1.dsc
 d3d80cc8e6eb3c7764a2905059acacce 6454603 sound optional 
rosegarden_17.04.orig.tar.bz2
 f3d0c0673671629cf4c410f51b00cf33 12536 sound optional 
rosegarden_17.04-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkOLSwa0Uaht+u4kdu8F+uxOW8vcFAlmi3ukACgkQu8F+uxOW
8velaBAAsAEorKO8r6lfYxZmYG1yljx05fs3zSq4m+WwawgxaCW6V32zYbHVyxGe
5JqxnjNic9LycJkSkPyu4bAVSMj25gKa9L2wYMDT/5UnecA2HbXabIF7irP1Mpe+
UXg/dP7C9jvPymkYZOy9qk41Lfpbkkzp5ALvEFTrz8COh6yiNSpPnVvjpKVVgzub
31XiNzNZBoG/Bk83QJTTzkhdS0Iw0wFxtUdJar8kumc01ElBBNkjr3JCk0w5Wygg
Bwf8tfd6giE2SFWcXSq3OfKQtiFM7pASBUuWfem/BA3PVNqsfx6xtPU6pnfKBmhC
YoeQJxq6nSYVLv/bmT+NoLYG0XrgcjMhSDV9h/jHqORv0mjEBmgIDmHL0U9ok8Ep
SdFZJfFm3Yc99NU/yLPiQAzF4c6XV3luseC+VLJ2JvZP9/DSHsPhiEpIsIlCo3FJ
xQcxEaNYVa7wC7JsVRAiGB+0ABAUzOl6BkacD6xFoqdNYsw/EnMKnIRgUub9UqaP
1p035r4odwDNkP3AX9o8B

Bug#853656: Help needed with gcc-7 error

[Bastien Roucaries]

Use  and make signed

Le 27 août 2017 15:58:34 GMT+02:00, James Cowgill  a écrit 
:
>Hi,
>
>On 27/08/17 14:40, Andreas Tille wrote:
>> Hi,
>> 
>> when trying to build sga it results in an error:
>> 
>> ...
>> g++ -DHAVE_CONFIG_H -I. -I..  -I../Bigraph -I../Thirdparty
>-Wdate-time -D_FORTIFY_SOURCE=2 -fopenmp  -I/usr//include
>-I/usr//include/bamtools -Wall -Wextra  -Wno-unknown-pragmas -std=c++98
>-O3 -c -o libutil_a-VariantIndex.o `test -f 'VariantIndex.cpp' || echo
>'./'`VariantIndex.cpp
>> VariantIndex.cpp: In member function 'VariantRecordVector
>VariantIndex::getNearVariants(const string&, int, int) const':
>> VariantIndex.cpp:89:46: error: call of overloaded 'abs(long unsigned
>int)' is ambiguous
>>  if(abs(record.position - position) < distance)
>>   ^
>
>In C++11, you cannot call abs on an unsigned integer (which makes no
>sense anyway). Probably "record.position" needs casting to a signed
>type
>(like long).
>
>Thanks,
>James

-- 
Envoyé de mon appareil Android avec K-9 Mail. Veuillez excuser ma brièveté.

Bug#784512: Is anybody working on PySide2?

[Didier 'OdyX' Raboud]

Le dimanche, 27 août 2017 16.53:30 h CEST, vous avez écrit :
> Hi,
> 
> python-ghost depends on pyside, which will be removed with Qt4.
> Upstream already ported to pyside2, but I can't find pyside2 in
> Debian, not even an ITP or RFP. But somewhere I read, that
> pyside2 will be part of Qt. Is somebody working on this? It
> would be bad to remove pyside from Debian before pyside2 is in
> place, right?

For what is worth: I'm not working on pyside, nor pyside2. I removed myself 
from both shiboken and pyside's uploader fields (but should really have mailed 
debian-python about that earlier).

Cheers,
OdyX

Processed: limit source to rosegarden, tagging 871213

[Debian Bug Tracking System]

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

> limit source rosegarden
Limiting to bugs with field 'source' containing at least one of 'rosegarden'
Limit currently set to 'source':'rosegarden'

> tags 871213 + pending
Bug #871213 [src:rosegarden] rosegarden: FTBFS: make[3]: *** No rule to make 
target 'src/svnversion.h', needed by 
'src/CMakeFiles/rosegardenprivate_autogen'. Stop.
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#873394: marked as done (cython-doc: trying to overwrite '/usr/share/man/man1/cython.1.gz', which is also in package cython 0.26-1)

[Debian Bug Tracking System]

Your message dated Sun, 27 Aug 2017 15:04:58 +
with message-id 
and subject line Bug#873394: fixed in cython 0.26-2
has caused the Debian Bug report #873394,
regarding cython-doc: trying to overwrite '/usr/share/man/man1/cython.1.gz', 
which is also in package cython 0.26-1
to be marked as done.

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

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


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

Package: cython
Version: 0.26-1
Severity: serious

Unpacking cython-doc (0.26-1) over (0.25.2-2) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-atQ9oy/07-cython-doc_0.26-1_all.deb (--unpack):
trying to overwrite '/usr/share/man/man1/cython.1.gz', which is also in package 
cython 0.26-1

--
Jakub Wilk
--- End Message ---
--- Begin Message ---
Source: cython
Source-Version: 0.26-2

We believe that the bug you reported is fixed in the latest version of
cython, 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.
Ximin Luo  (supplier of updated cython 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, 27 Aug 2017 16:32:52 +0200
Source: cython
Binary: cython cython-dbg cython3 cython3-dbg cython-doc
Architecture: source
Version: 0.26-2
Distribution: unstable
Urgency: medium
Maintainer: Python Applications Packaging Team 

Changed-By: Ximin Luo 
Description:
 cython - C-Extensions for Python
 cython-dbg - C-Extensions for Python - debug build
 cython-doc - C-Extensions for Python - documentation
 cython3- C-Extensions for Python 3
 cython3-dbg - C-Extensions for Python 3 - debug build
Closes: 873394
Changes:
 cython (0.26-2) unstable; urgency=medium
 .
   * Install cython.1 manpage only in cython arch-dep package. (Closes: #873394)
Checksums-Sha1:
 c402fe93e8045df2d517425529a7e0a620bf882f 2399 cython_0.26-2.dsc
 4d49dae071a948035d92587615f2f1308c4d4178 24176 cython_0.26-2.debian.tar.xz
 6809a815daa8da06d10dc0a23aec9577eee38a7f 6352 cython_0.26-2_source.buildinfo
Checksums-Sha256:
 6b08f3e7eddb641da8e163753600388fd97334472be450c872eff46e9302dc2b 2399 
cython_0.26-2.dsc
 1c58a691d6d5658eb407ba0ae92c43fbadcbefba5d7ed8afc35b2c3a503df5e7 24176 
cython_0.26-2.debian.tar.xz
 5b70298ef2be2933be16d550e34b6dcef52c624a8396579ba07e3b3a783ac881 6352 
cython_0.26-2_source.buildinfo
Files:
 dff0003a75ad5ed95774b193440a4592 2399 python optional cython_0.26-2.dsc
 4cefd32262c82b825fa296198a4f7b05 24176 python optional 
cython_0.26-2.debian.tar.xz
 ff0f0c53f947b19d796dac5c8ed6b0ba 6352 python optional 
cython_0.26-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEENmdIajJtsnZtJVVGhg3vO49lC3kFAlmi2HIVHGluZmluaXR5
MEBkZWJpYW4ub3JnAAoJEIYN7zuPZQt5+O8P/25/QnlyHtmnqlKm2VkfthA6BBlq
ZNQ8z9MHbpRhGz6usjaV4PTxdbivvCjgnia82MtUat+XMaZoVDhe1hmbjdzBsoZi
1LdAT3BdLYcY87Q9IVmfp9Gln6VICcOty6tB3YNSifu+dYWGSe0cV0+qV/4IvZBa
tw8xSAU8P1FpJfAXOYfK4sc6QDapbYCzO4wkuaPiuQX9m/JIibDkesmtSk4GY2nT
ZrQkxFwUEXFUTsmS5+EP5Q46x1DX6LF8h/RkV1tMXV2zFSlGX9PC8118Ly0hTbBO
G2ltunSwach3irHnBuYRWTNwjHa5q1hl4E1KWcsa2gmQmkjyywhwQ+HdP09cvExc
fPlYvHvC8qdOk1Kfnm6cPpp4aVF9sO6/YCpj6AJsndwSAhgcXuwoAxnL3WHDiCpn
ZfMSqrna6/24XAI5H88zqpkJL/cyaHi+Mkkjf8TbbLuwG9VOsOb73GhoSHveZBOC
SEz/BUZs63W81TBHItxoBBvEug9Gxegaj14g7LXfMo73XNwQtE5XNA3lE0RJBdlU
KzUVz/SiYj+NpNPNBOspoAQVtU4NWZ9LQ/EGoebO8sitN1a5tW7EPDChrgvwMNL1
HhoE3hYmliGdgbAohxqO7VZMHJ6fs6u1NGPvD23jtJDG4k0TImNd3HlSuHRSoAKx
J32r7mJPgY1kbl85
=q0BX
-END PGP SIGNATURE End Message ---

Bug#872436: marked as done (db5.3: CVE-2017-10140: Berkeley DB reads DB_CONFIG from cwd)

[Debian Bug Tracking System]

Your message dated Sun, 27 Aug 2017 15:05:21 +
with message-id 
and subject line Bug#872436: fixed in db5.3 5.3.28-13.1
has caused the Debian Bug report #872436,
regarding db5.3: CVE-2017-10140: Berkeley DB reads DB_CONFIG from cwd
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.)


-- 
872436: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872436
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: db5.3
Version: 5.3.28-9
Severity: grave
Tags: upstream security

Hi,

the following vulnerability was published for db5.3.

CVE-2017-10140[0]:
Berkeley DB reads DB_CONFIG from cwd

Fedora used the patch in [3], and according to [1], comment #9 this
has been acknowledged by upstream to be fine solution.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-10140
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10140
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1464032
[2] https://bugzilla.novell.com/show_bug.cgi?id=1043886
[3] 
https://src.fedoraproject.org/rpms/libdb/raw/8047fa8580659fcae740c25e91b490539b8453eb/f/db-5.3.28-cwd-db_config.patch

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: db5.3
Source-Version: 5.3.28-13.1

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 17 Aug 2017 14:35:22 +0200
Source: db5.3
Binary: db5.3-doc libdb5.3-dev libdb5.3 db5.3-util db5.3-sql-util libdb5.3++ 
libdb5.3++-dev libdb5.3-tcl libdb5.3-dbg libdb5.3-java-jni libdb5.3-java 
libdb5.3-java-dev libdb5.3-sql-dev libdb5.3-sql libdb5.3-stl-dev libdb5.3-stl
Architecture: source
Version: 5.3.28-13.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Berkeley DB Group 
Changed-By: Salvatore Bonaccorso 
Description:
 db5.3-doc  - Berkeley v5.3 Database Documentation [html]
 db5.3-sql-util - Berkeley v5.3 SQL Database Utilities
 db5.3-util - Berkeley v5.3 Database Utilities
 libdb5.3   - Berkeley v5.3 Database Libraries [runtime]
 libdb5.3++ - Berkeley v5.3 Database Libraries for C++ [runtime]
 libdb5.3++-dev - Berkeley v5.3 Database Libraries for C++ [development]
 libdb5.3-dbg - Berkeley v5.3 Database Libraries [debug]
 libdb5.3-dev - Berkeley v5.3 Database Libraries [development]
 libdb5.3-java - Berkeley v5.3 Database Libraries for Java
 libdb5.3-java-dev - Berkeley v5.3 Database Libraries for Java [development]
 libdb5.3-java-jni - Berkeley v5.3 Database Libraries for Java
 libdb5.3-sql - Berkeley v5.3 Database Libraries [SQL runtime]
 libdb5.3-sql-dev - Berkeley v5.3 Database Libraries [SQL development]
 libdb5.3-stl - Berkeley v5.3 Database Libraries [STL runtime]
 libdb5.3-stl-dev - Berkeley v5.3 Database Libraries [STL development]
 libdb5.3-tcl - Berkeley v5.3 Database Libraries for Tcl [module]
Closes: 872436
Changes:
 db5.3 (5.3.28-13.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * CVE-2017-10140: Reads DB_CONFIG from the current working directory.
 Do not access DB_CONFIG when db_home is not set. (Closes: #872436)
Checksums-Sha1:
 055f65f46fbef63f8426fa869e9865dc2b332b7d 3124 db5.3_5.3.28-13.1.dsc
 9ecf25e1b9855ee2401c80e6a71046685438bbbd 28180 db5.3_5.3.28-13.1.debian.tar.xz
 433cf019b6aecceafe58dd2c06b1e6410178a92e 6089 
db5.3_5.3.28-13.1_source.buildinfo
Checksums-Sha256:
 8941edcad8e16fe6bc76ffcbe86dbdaadc654b5ed994654689cf5408602a84f3 3124 
db5.3_5.3.28-13.1.dsc
 9e04b9269be51de4e73536584addc61e19b29e34f769e263c180228064c72ec9 28180 
db5.3_5.3.28-13.1.debian.tar.xz
 ceac7ee4268092db85df99b084eb5ffa8905e7f5fbe1db73d47075c7599f2177 6089 
db5.3_5.3.28-13.1_source.buildinfo
Files:
 0c44e9b0f9d88e1f78185872aed60169 3124 libs standard db5.3_5.3.28-13.1.dsc
 20445d4c813e83a72389138171a7bc0b 28180 libs standard 
db5.3_5.3.28-13.1.debian.tar.xz
 516f65

Bug#784512: Is anybody working on PySide2?

[W. Martin Borgert]

Hi,

python-ghost depends on pyside, which will be removed with Qt4.
Upstream already ported to pyside2, but I can't find pyside2 in
Debian, not even an ITP or RFP. But somewhere I read, that
pyside2 will be part of Qt. Is somebody working on this? It
would be bad to remove pyside from Debian before pyside2 is in
place, right?

TIA for any useful hint!


signature.asc
Description: PGP signature

Processed: Adding fixed version again

[Debian Bug Tracking System]

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

> fixed 871357 0.21
Bug #871357 {Done: Lucas Nussbaum } [src:packaging-tutorial] 
packaging-tutorial: FTBFS: Unescaped left brace in regex is illegal here in 
regex; marked by <-- HERE in m/\\end{ <-- HERE document}/ at 
/usr/share/perl5/Locale/Po4a/TransTractor.pm line 643.
Marked as fixed in versions packaging-tutorial/0.21.
> thanks
Stopping processing here.

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

Bug#873377: tcpdump FTBFS on ppc64el: Failed test: ikev2pI2

[Adrian Bunk]

On Sun, Aug 27, 2017 at 04:21:55PM +0200, Romain Francoise wrote:
> Hmm, I don't think anything has changed wrt. IKEv2 decoding in 4.9.1
> compared to previous version in the archive,

gcc 6 -> 7 would then be my first guess.

> and the only two failing
> archs are ppc64el and powerpc. Puzzling.
>...

Most puzzling is that it didn't also fail on ppc64.

cu
Adrian

-- 

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

Processed: your mail

[Debian Bug Tracking System]

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

> tag 873394 + pending
Bug #873394 [cython] cython-doc: trying to overwrite 
'/usr/share/man/man1/cython.1.gz', which is also in package cython 0.26-1
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#873377: tcpdump FTBFS on ppc64el: Failed test: ikev2pI2

[Romain Francoise]

Hmm, I don't think anything has changed wrt. IKEv2 decoding in 4.9.1
compared to previous version in the archive, and the only two failing
archs are ppc64el and powerpc. Puzzling.

Let me see if I can find a porterbox...

-- 
Romain Francoise 
https://people.debian.org/~rfrancoise/

Bug#853656: Help needed with gcc-7 error

[James Cowgill]

Hi,

On 27/08/17 14:40, Andreas Tille wrote:
> Hi,
> 
> when trying to build sga it results in an error:
> 
> ...
> g++ -DHAVE_CONFIG_H -I. -I..  -I../Bigraph -I../Thirdparty -Wdate-time 
> -D_FORTIFY_SOURCE=2 -fopenmp  -I/usr//include -I/usr//include/bamtools -Wall 
> -Wextra  -Wno-unknown-pragmas -std=c++98 -O3 -c -o libutil_a-VariantIndex.o 
> `test -f 'VariantIndex.cpp' || echo './'`VariantIndex.cpp
> VariantIndex.cpp: In member function 'VariantRecordVector 
> VariantIndex::getNearVariants(const string&, int, int) const':
> VariantIndex.cpp:89:46: error: call of overloaded 'abs(long unsigned int)' is 
> ambiguous
>  if(abs(record.position - position) < distance)
>   ^

In C++11, you cannot call abs on an unsigned integer (which makes no
sense anyway). Probably "record.position" needs casting to a signed type
(like long).

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#853656: Help needed with gcc-7 error

[Andreas Tille]

Hi,

when trying to build sga it results in an error:

...
g++ -DHAVE_CONFIG_H -I. -I..  -I../Bigraph -I../Thirdparty -Wdate-time 
-D_FORTIFY_SOURCE=2 -fopenmp  -I/usr//include -I/usr//include/bamtools -Wall 
-Wextra  -Wno-unknown-pragmas -std=c++98 -O3 -c -o libutil_a-VariantIndex.o 
`test -f 'VariantIndex.cpp' || echo './'`VariantIndex.cpp
VariantIndex.cpp: In member function 'VariantRecordVector 
VariantIndex::getNearVariants(const string&, int, int) const':
VariantIndex.cpp:89:46: error: call of overloaded 'abs(long unsigned int)' is 
ambiguous
 if(abs(record.position - position) < distance)
  ^
In file included from /usr/include/c++/7/cstdlib:75:0,
 from /usr/include/c++/7/bits/stl_algo.h:59,
 from /usr/include/c++/7/algorithm:62,
 from VariantIndex.cpp:11:
/usr/include/stdlib.h:735:12: note: candidate: int abs(int)
 extern int abs (int __x) __THROW __attribute__ ((__const__)) __wur;
^~~
In file included from /usr/include/c++/7/cstdlib:77:0,
 from /usr/include/c++/7/bits/stl_algo.h:59,
 from /usr/include/c++/7/algorithm:62,
 from VariantIndex.cpp:11:
/usr/include/c++/7/bits/std_abs.h:56:3: note: candidate: long int std::abs(long 
int)
   abs(long __i) { return __builtin_labs(__i); }
   ^~~
...


I have no idea in how far abs() is overloaded and how to fix this.

Kind regards

   Andreas.

-- 
http://fam-tille.de

Processed: Bug housekeeping

[Debian Bug Tracking System]

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

> affects 871357
Bug #871357 {Done: Lucas Nussbaum } [po4a] 
packaging-tutorial: FTBFS: Unescaped left brace in regex is illegal here in 
regex; marked by <-- HERE in m/\\end{ <-- HERE document}/ at 
/usr/share/perl5/Locale/Po4a/TransTractor.pm line 643.
Removed indication that 871357 affects src:packaging-tutorial
> reassign 871357 src:packaging-tutorial 0.20
Bug #871357 {Done: Lucas Nussbaum } [po4a] 
packaging-tutorial: FTBFS: Unescaped left brace in regex is illegal here in 
regex; marked by <-- HERE in m/\\end{ <-- HERE document}/ at 
/usr/share/perl5/Locale/Po4a/TransTractor.pm line 643.
Bug reassigned from package 'po4a' to 'src:packaging-tutorial'.
No longer marked as found in versions 0.20.
No longer marked as fixed in versions packaging-tutorial/0.21.
Bug #871357 {Done: Lucas Nussbaum } [src:packaging-tutorial] 
packaging-tutorial: FTBFS: Unescaped left brace in regex is illegal here in 
regex; marked by <-- HERE in m/\\end{ <-- HERE document}/ at 
/usr/share/perl5/Locale/Po4a/TransTractor.pm line 643.
Marked as found in versions packaging-tutorial/0.20.
> thanks
Stopping processing here.

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

Bug#873362: coinor-libcoinutils3v5: unannounced ABI change without SONAME change?

[Anton Gladky]

> Still I believe that this should be "correctly" fixed.

You mean to increase so-version even if upstream does not do it and
to start the normal transition process? I think it is possible.

> P.S.: Is it intended that coinutils contains 
> /usr/lib/x86_64-linux-gnu/pkgconfig/coindatasample.pc or is there a export 
> COIN_SKIP_PROJECTS="Sample" missing?

I do not know, whether it is really needed. This line is in
the .install-package [1] for a long time and  I did not remove
it last year, when overtook the maintenance on this package.

[1] 
https://anonscm.debian.org/cgit/debian-science/packages/coinutils.git/tree/debian/coinor-libcoinutils-dev.install#n4

Cheers

Anton

Processed (with 1 error): Bug housekeeping

[Debian Bug Tracking System]

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

> assign 871357 src:packaging-tutorial
Unknown command or malformed arguments to command.
> found 871357 0.20
Bug #871357 {Done: Lucas Nussbaum } [po4a] 
packaging-tutorial: FTBFS: Unescaped left brace in regex is illegal here in 
regex; marked by <-- HERE in m/\\end{ <-- HERE document}/ at 
/usr/share/perl5/Locale/Po4a/TransTractor.pm line 643.
There is no source info for the package 'po4a' at version '0.20' with 
architecture ''
Unable to make a source version for version '0.20'
Marked as found in versions 0.20.
> thanks
Stopping processing here.

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

Bug#873362: coinor-libcoinutils3v5: unannounced ABI change without SONAME change?

[Rene Engelhard]

On Sun, Aug 27, 2017 at 01:59:04PM +0200, Rene Engelhard wrote:
> for coinmp and libreoffice (5.4.1 release will be next week) if we uploaded
> coinmp 1.8.3 to unstable...

Now uploaded coinmp 1.8.3-2 to unstable.

Let's see.
Test succeeds at least.

Still I believe that this should be "correctly" fixed.
 
Regards,
 
Rene

P.S.: Is it intended that coinutils contains 
/usr/lib/x86_64-linux-gnu/pkgconfig/coindatasample.pc or is there a export 
COIN_SKIP_PROJECTS="Sample" missing?

See 
https://anonscm.debian.org/cgit/debian-science/packages/coinmp.git/commit/?id=fccad9caf4d1698f1c294b73cd64f78c7d4a5727,
 without that I get that file in
coinor-libcoinmp-dev

Bug#873394: cython-doc: trying to overwrite '/usr/share/man/man1/cython.1.gz', which is also in package cython 0.26-1

[Jakub Wilk]

Package: cython
Version: 0.26-1
Severity: serious

Unpacking cython-doc (0.26-1) over (0.25.2-2) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-atQ9oy/07-cython-doc_0.26-1_all.deb (--unpack):
trying to overwrite '/usr/share/man/man1/cython.1.gz', which is also in package 
cython 0.26-1

--
Jakub Wilk

Processed: libebml #870797 should be serious like the other GCC-7 bugs

[Debian Bug Tracking System]

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

> severity 870797 serious
Bug #870797 {Done: James Cowgill } [libebml4v5] 
libebml4v5: Please rebuild against GCC 7 to fix bug 853553
Severity set to 'serious' from 'normal'
> user debian-...@lists.debian.org
Setting user to debian-...@lists.debian.org (was jcowg...@debian.org).
> usertag 870797 gcc-7-op-mangling
There were no usertags set.
Usertags are now: gcc-7-op-mangling.
> thanks
Stopping processing here.

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

Bug#873362: coinor-libcoinutils3v5: unannounced ABI change without SONAME change?

[Rene Engelhard]

Hi,

On Sun, Aug 27, 2017 at 01:26:30PM +0200, Anton Gladky wrote:
> thanks for the bug report and sorry for inconvenience. Upstream did
> not change the SO-version, so I decided not to do it explicitly and
> request transition. Looks like the changes were minimal.
> 
> If the coinmp-recompilation really fixes your problem,

Did, yes, as said.

Though I admit I am a bit confused given coinmp only links
to cbc, not coinutils. (LO does use coinutils, too, though)

> I would ask for binnmus of all rdepends.

That would be better than nothing, though that would "hide" the problem and
would cause problems if the libs for whatever reason get updated independently.
(like right now.)

I uploaded coinmp 1.8.3 to experimental today so I don't think we need bin-NMUs
for coinmp and libreoffice (5.4.1 release will be next week) if we uploaded
coinmp 1.8.3 to unstable...

Regards,

Rene

Processed: found 873383 in 1.8.0-1

[Debian Bug Tracking System]

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

> # fix bts versioning info
> found 873383 1.8.0-1
Bug #873383 {Done: Andreas Metzler } [src:libgcrypt20] 
libgcrypt20: CVE-2017-0379: side-channel attack on Curve25519
Marked as found in versions libgcrypt20/1.8.0-1.
> thanks
Stopping processing here.

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

Bug#863515: marked as done (CVE-2017-0350 CVE-2017-0351 CVE-2017-0352)

[Debian Bug Tracking System]

Your message dated Sun, 27 Aug 2017 12:00:37 +
with message-id 
and subject line Bug#863515: fixed in nvidia-graphics-drivers 381.22-1
has caused the Debian Bug report #863515,
regarding CVE-2017-0350 CVE-2017-0351 CVE-2017-0352
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.)


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

Please see http://nvidia.custhelp.com/app/answers/detail/a_id/4462

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers
Source-Version: 381.22-1

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated nvidia-graphics-drivers 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 13 Aug 2017 08:02:13 +0200
Source: nvidia-graphics-drivers
Binary: nvidia-driver nvidia-driver-bin nvidia-driver-libs 
nvidia-driver-libs-i386 xserver-xorg-video-nvidia nvidia-legacy-check 
libglvnd0-nvidia libopengl0-glvnd-nvidia libglx0-glvnd-nvidia libglx-nvidia0 
libgl1-glvnd-nvidia-glx libgl1-nvidia-glvnd-glx libgl1-nvidia-glx 
libnvidia-glcore libegl1-glvnd-nvidia libegl1-nvidia libegl-nvidia0 
libgles1-glvnd-nvidia libgles1-nvidia libgles-nvidia1 libgles2-glvnd-nvidia 
libgles2-nvidia libgles-nvidia2 libnvidia-eglcore nvidia-egl-common 
nvidia-egl-icd libnvidia-egl-wayland1 nvidia-egl-wayland-common 
nvidia-egl-wayland-icd nvidia-vulkan-common nvidia-vulkan-icd 
nvidia-nonglvnd-vulkan-common nvidia-nonglvnd-vulkan-icd libnvidia-cfg1 
nvidia-alternative nvidia-kernel-support nvidia-kernel-dkms 
nvidia-kernel-source nvidia-vdpau-driver nvidia-smi nvidia-cuda-mps libcuda1 
libcuda1-i386 libnvidia-compiler libnvidia-fatbinaryloader 
libnvidia-ptxjitcompiler libnvcuvid1 libnvidia-encode1 libnvidia-ifr1 
libnvidia-fbc1 libnvidia-ml1
 nvidia-opencl-common nvidia-opencl-icd nvidia-libopencl1
 nvidia-detect
Architecture: source amd64
Version: 381.22-1
Distribution: experimental
Urgency: medium
Maintainer: Debian NVIDIA Maintainers 
Changed-By: Andreas Beckmann 
Description:
 libcuda1   - NVIDIA CUDA Driver Library${nvidia:LegacyDesc}
 libcuda1-i386 - NVIDIA CUDA 32-bit runtime library${nvidia:LegacyDesc}
 libegl-nvidia0 - NVIDIA binary EGL library${nvidia:LegacyDesc}
 libegl1-glvnd-nvidia - Vendor neutral GL dispatch library -- libEGL
 libegl1-nvidia - NVIDIA binary EGL library (non-GLVND 
variant)${nvidia:LegacyDesc}
 libgl1-glvnd-nvidia-glx - Vendor neutral GL dispatch library -- libGL
 libgl1-nvidia-glvnd-glx - NVIDIA binary OpenGL/GLX library (GLVND 
variant)${nvidia:LegacyDe
 libgl1-nvidia-glx - NVIDIA binary OpenGL/GLX library (non-GLVND 
variant)${nvidia:Lega
 libgles-nvidia1 - NVIDIA binary OpenGL|ES 1.x library${nvidia:LegacyDesc}
 libgles-nvidia2 - NVIDIA binary OpenGL|ES 2.x library${nvidia:LegacyDesc}
 libgles1-glvnd-nvidia - NVIDIA binary OpenGL|ES 1.x GLVND stub library
 libgles1-nvidia - NVIDIA binary OpenGL|ES 1.x library 
(transitional)${nvidia:Legacy
 libgles2-glvnd-nvidia - NVIDIA binary OpenGL|ES 2.x GLVND stub library
 libgles2-nvidia - NVIDIA binary OpenGL|ES 2.x library 
(transitional)${nvidia:Legacy
 libglvnd0-nvidia - Vendor neutral GL dispatch library -- libGLdispatch
 libglx-nvidia0 - NVIDIA binary GLX library${nvidia:LegacyDesc}
 libglx0-glvnd-nvidia - Vendor neutral GL dispatch library -- libGLX
 libnvcuvid1 - NVIDIA CUDA Video Decoder runtime library${nvidia:LegacyDesc}
 libnvidia-cfg1 - NVIDIA binary OpenGL/GLX configuration 
library${nvidia:LegacyDesc
 libnvidia-compiler - NVIDIA runtime compiler library${nvidia:LegacyDesc}
 libnvidia-egl-wayland1 - NVIDIA binary Wayland EGL external platform library
 libnvidia-eglcore - NVIDIA binary EGL core libraries${nvidia:LegacyDesc}
 libnvidia-encode1 - NVENC Video Encoding runtime library${nvidia:LegacyDesc}
 libnvidia-fatbinaryloader - NVIDIA FAT binary loader${nvidia:Legacy

Bug#870170: marked as done (wolfssl: CVE-2017-8855)

[Debian Bug Tracking System]

Your message dated Sun, 27 Aug 2017 12:00:45 +
with message-id 
and subject line Bug#870170: fixed in wolfssl 3.12.0+dfsg-1
has caused the Debian Bug report #870170,
regarding wolfssl: CVE-2017-8855
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.)


-- 
870170: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870170
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wolfssl
Version: 3.10.2+dfsg-2
Severity: grave
Tags: upstream security fixed-upstream

Hi,

the following vulnerability was published for wolfssl.

CVE-2017-8855[0]:
| wolfSSL before 3.11.0 does not prevent wc_DhAgree from accepting a
| malformed DH key.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-8855
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-8855
[1] https://github.com/wolfSSL/wolfssl/releases/tag/v3.11.0-stable

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: wolfssl
Source-Version: 3.12.0+dfsg-1

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

Debian distribution maintenance software
pp.
Felix Lechner  (supplier of updated wolfssl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 13 Aug 2017 21:00:54 -0700
Source: wolfssl
Binary: libwolfssl12 libwolfssl-dev
Architecture: source amd64
Version: 3.12.0+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Felix Lechner 
Changed-By: Felix Lechner 
Description:
 libwolfssl-dev - Development files for the wolfSSL encryption library
 libwolfssl12 - wolfSSL encryption library
Closes: 862154 870170
Changes:
 wolfssl (3.12.0+dfsg-1) unstable; urgency=medium
 .
   * New upstream release
   * Shared object version is now 12
   * CVE-2017-2800 was fixed in 3.11.0 (Closes: #862154)
   * CVE-2017-8855 was fixed in 3.11.0 (Closes: #870170)
   * Removed "--with-sha224" from rules; now included in "--enable-distro"
   * Cannot override lintian for missing upstream signature; source was
 repackaged (DFSG)
   * Removed unnecessary Build-Depends: dh-autoreconf
   * Removed unnecessary Build-Depends: autotools-dev
   * Updated to Standards-Version: 4.0.0
Checksums-Sha1:
 6ebd2e06e8b07d868acb8eee4be789745d2a3368 1869 wolfssl_3.12.0+dfsg-1.dsc
 f06cc10c932a2f6e5b6edebd9a2aea800ef85c2d 1839359 
wolfssl_3.12.0+dfsg.orig.tar.gz
 e762c7288be0407899969ddbba0c5ce6283a9a70 16724 
wolfssl_3.12.0+dfsg-1.debian.tar.xz
 447dd5125e315ebd005fbe98d3d61dffec729398 570690 
libwolfssl-dev_3.12.0+dfsg-1_amd64.deb
 ac91f58894b68a73fc01bfad2f8f4fce38c58cfd 1093630 
libwolfssl12-dbgsym_3.12.0+dfsg-1_amd64.deb
 0c86c3f1f038125a88a20844da2871c475d83c31 392310 
libwolfssl12_3.12.0+dfsg-1_amd64.deb
 c8e99e971625cf9594fcc27cdce45d036adc2dfe 5847 
wolfssl_3.12.0+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 a4dc3215fe531ab09b0ea62c1a1efd2302f791283e498a06fae280adae3dea81 1869 
wolfssl_3.12.0+dfsg-1.dsc
 dadb4b4b7924df891dd510cabee427ccad7af84d874536b0a834e94d7b982585 1839359 
wolfssl_3.12.0+dfsg.orig.tar.gz
 9c8e5643d4a8304c8523166639df790d7247146e1f1e4949cd00482f72be8519 16724 
wolfssl_3.12.0+dfsg-1.debian.tar.xz
 9c9ded7d27ae5c50e2af476746789f0eb4c629c55c9ef3442da080512f2c9d25 570690 
libwolfssl-dev_3.12.0+dfsg-1_amd64.deb
 95e2df4110c75aa340382b49f3e447c309efb7ec047bc52e7c1d65e6d799942e 1093630 
libwolfssl12-dbgsym_3.12.0+dfsg-1_amd64.deb
 008b9079d10a8983e945e89b7af656d382d91351d000e270a9511416815a1002 392310 
libwolfssl12_3.12.0+dfsg-1_amd64.deb
 64cb38d74a1732c5b01633cb1cb9aa87a8b3028f5017a31aca84deb962e02fed 5847 
wolfssl_3.12.0+dfsg-1_amd64.buildinfo
Files:
 433adcdc46031490129d695b0bef0010 1869 libs optional wolfssl_3.12.0+dfsg-1.dsc
 338b8a975e2a0dc39d4c5534ae3c5d68 1839359 libs optional 
wolfssl_3.12.0+dfsg.orig.tar.gz
 0f42a952430b5472d98e4a2969cfaac6 16724 libs optional 
wolfssl_3.12.0+dfsg-1.debian.tar.xz
 9b051fc16c5d464f1c6395989ef33ad4 570

Bug#862154: marked as done (wolfssl: CVE-2017-2800 / TALOS-2017-0293)

[Debian Bug Tracking System]

Your message dated Sun, 27 Aug 2017 12:00:45 +
with message-id 
and subject line Bug#862154: fixed in wolfssl 3.12.0+dfsg-1
has caused the Debian Bug report #862154,
regarding wolfssl: CVE-2017-2800 / TALOS-2017-0293
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.)


-- 
862154: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862154
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wolfssl
Version: 3.10.2+dfsg-2
Severity: grave
Tags: upstream security

Hi,

the following vulnerability was published for wolfssl.

CVE-2017-2800[0]:
No description was found (try on a search engine)

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-2800
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-2800
[1] http://www.talosintelligence.com/reports/TALOS-2017-0293/

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: wolfssl
Source-Version: 3.12.0+dfsg-1

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

Debian distribution maintenance software
pp.
Felix Lechner  (supplier of updated wolfssl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 13 Aug 2017 21:00:54 -0700
Source: wolfssl
Binary: libwolfssl12 libwolfssl-dev
Architecture: source amd64
Version: 3.12.0+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Felix Lechner 
Changed-By: Felix Lechner 
Description:
 libwolfssl-dev - Development files for the wolfSSL encryption library
 libwolfssl12 - wolfSSL encryption library
Closes: 862154 870170
Changes:
 wolfssl (3.12.0+dfsg-1) unstable; urgency=medium
 .
   * New upstream release
   * Shared object version is now 12
   * CVE-2017-2800 was fixed in 3.11.0 (Closes: #862154)
   * CVE-2017-8855 was fixed in 3.11.0 (Closes: #870170)
   * Removed "--with-sha224" from rules; now included in "--enable-distro"
   * Cannot override lintian for missing upstream signature; source was
 repackaged (DFSG)
   * Removed unnecessary Build-Depends: dh-autoreconf
   * Removed unnecessary Build-Depends: autotools-dev
   * Updated to Standards-Version: 4.0.0
Checksums-Sha1:
 6ebd2e06e8b07d868acb8eee4be789745d2a3368 1869 wolfssl_3.12.0+dfsg-1.dsc
 f06cc10c932a2f6e5b6edebd9a2aea800ef85c2d 1839359 
wolfssl_3.12.0+dfsg.orig.tar.gz
 e762c7288be0407899969ddbba0c5ce6283a9a70 16724 
wolfssl_3.12.0+dfsg-1.debian.tar.xz
 447dd5125e315ebd005fbe98d3d61dffec729398 570690 
libwolfssl-dev_3.12.0+dfsg-1_amd64.deb
 ac91f58894b68a73fc01bfad2f8f4fce38c58cfd 1093630 
libwolfssl12-dbgsym_3.12.0+dfsg-1_amd64.deb
 0c86c3f1f038125a88a20844da2871c475d83c31 392310 
libwolfssl12_3.12.0+dfsg-1_amd64.deb
 c8e99e971625cf9594fcc27cdce45d036adc2dfe 5847 
wolfssl_3.12.0+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 a4dc3215fe531ab09b0ea62c1a1efd2302f791283e498a06fae280adae3dea81 1869 
wolfssl_3.12.0+dfsg-1.dsc
 dadb4b4b7924df891dd510cabee427ccad7af84d874536b0a834e94d7b982585 1839359 
wolfssl_3.12.0+dfsg.orig.tar.gz
 9c8e5643d4a8304c8523166639df790d7247146e1f1e4949cd00482f72be8519 16724 
wolfssl_3.12.0+dfsg-1.debian.tar.xz
 9c9ded7d27ae5c50e2af476746789f0eb4c629c55c9ef3442da080512f2c9d25 570690 
libwolfssl-dev_3.12.0+dfsg-1_amd64.deb
 95e2df4110c75aa340382b49f3e447c309efb7ec047bc52e7c1d65e6d799942e 1093630 
libwolfssl12-dbgsym_3.12.0+dfsg-1_amd64.deb
 008b9079d10a8983e945e89b7af656d382d91351d000e270a9511416815a1002 392310 
libwolfssl12_3.12.0+dfsg-1_amd64.deb
 64cb38d74a1732c5b01633cb1cb9aa87a8b3028f5017a31aca84deb962e02fed 5847 
wolfssl_3.12.0+dfsg-1_amd64.buildinfo
Files:
 433adcdc46031490129d695b0bef0010 1869 libs optional wolfssl_3.12.0+dfsg-1.dsc
 338b8a975e2a0dc39d4c5534ae3c5d68 1839359 libs optional 
wolfssl_3.12.0+dfsg.orig.tar.gz
 0f42a952430b5472d98e4a2969cfaac6 16724 libs optional 
wolfssl_3.12.0+dfsg-1.debian.tar.xz
 9b051fc16c5d464f1c6395989ef33ad4 570690 libdevel optional 
libwolfssl-dev_3.12.0+dfsg-1_amd64.deb
 d2513459196d3dfa207de1ff120f1e8d 1093

Processed: tagging 872035

[Debian Bug Tracking System]

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

> tags 872035 + patch
Bug #872035 [src:sysdig] sysdig FTBFS with curl 7.55.0-1
Added tag(s) patch.
> thanks
Stopping processing here.

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

Processed: bug 872035 is forwarded to https://github.com/draios/sysdig/issues/895

[Debian Bug Tracking System]

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

> forwarded 872035 https://github.com/draios/sysdig/issues/895
Bug #872035 [src:sysdig] sysdig FTBFS with curl 7.55.0-1
Set Bug forwarded-to-address to 'https://github.com/draios/sysdig/issues/895'.
> thanks
Stopping processing here.

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

Processed: bug 873326 is forwarded to https://github.com/draios/sysdig/pull/921

[Debian Bug Tracking System]

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

> forwarded 873326 https://github.com/draios/sysdig/pull/921
Bug #873326 [src:sysdig] sysdig FTBFS with luajit 2.1
Set Bug forwarded-to-address to 'https://github.com/draios/sysdig/pull/921'.
> thanks
Stopping processing here.

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

Bug#872079: libwine32 will not install

[David Goodenough]

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.

Bug#873383: marked as done (libgcrypt20: CVE-2017-0379: side-channel attack on Curve25519)

[Debian Bug Tracking System]

Your message dated Sun, 27 Aug 2017 11:49:39 +
with message-id 
and subject line Bug#873383: fixed in libgcrypt20 1.8.1-1
has caused the Debian Bug report #873383,
regarding libgcrypt20: CVE-2017-0379: side-channel attack on Curve25519
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.)


-- 
873383: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873383
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgcrypt20
Version: 1.7.1-1
Severity: grave
Tags: upstream patch security fixed-upstream

Hi,

the following vulnerability was published for libgcrypt20.

CVE-2017-0379[0]:
side-channel attack on Curve25519

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-0379
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0379
[1] 
https://git.gnupg.org/cgi-bin/gitweb.cgi?p=libgcrypt.git;a=commit;h=da780c81838f533c8ace8211ac2cb2bdee7b

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: libgcrypt20
Source-Version: 1.8.1-1

We believe that the bug you reported is fixed in the latest version of
libgcrypt20, 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.
Andreas Metzler  (supplier of updated libgcrypt20 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, 27 Aug 2017 13:13:01 +0200
Source: libgcrypt20
Binary: libgcrypt20-doc libgcrypt20-dev libgcrypt20 libgcrypt20-udeb 
libgcrypt11-dev libgcrypt-mingw-w64-dev
Architecture: source
Version: 1.8.1-1
Distribution: experimental
Urgency: medium
Maintainer: Debian GnuTLS Maintainers 
Changed-By: Andreas Metzler 
Closes: 873297 873383
Description: 
 libgcrypt11-dev - transitional libgcrypt11-dev package
 libgcrypt20-dev - LGPL Crypto library - development files
 libgcrypt20-doc - LGPL Crypto library - documentation
 libgcrypt20 - LGPL Crypto library - runtime library
 libgcrypt20-udeb - LGPL Crypto library - runtime library (udeb)
 libgcrypt-mingw-w64-dev - LGPL Crypto library - Windows development
Changes:
 libgcrypt20 (1.8.1-1) experimental; urgency=medium
 .
   * New upstream version.
 + Mitigates a local side-channel attack on Curve25519 dubbed "May the
   Fourth be With You".  [CVE-2017-0379] Closes: #873383
 + Add the OID SHA384WithECDSA from RFC-7427 to SHA-384. Closes: 873297
   * Use @ARCHIVE_EXT@ in watchfile instead of hardcoding bz2.
Checksums-Sha1: 
 a0b7bf430034ee0f69f280db9530b3e8ae51344d 2914 libgcrypt20_1.8.1-1.dsc
 dd35f00da45602afe81e01f4d60c40bbdd826fe6 2967344 libgcrypt20_1.8.1.orig.tar.bz2
 e8af8fc95cab49aeff13e1ef450603785c22f1b1 310 libgcrypt20_1.8.1.orig.tar.bz2.asc
 3618938fe1ec3e398c2b139d72889fde572db2f7 27220 
libgcrypt20_1.8.1-1.debian.tar.xz
Checksums-Sha256: 
 5e4c0be1f9cb7b94476ee6198d8d03d4cc30b0af658af865b9b1ab9bc556234f 2914 
libgcrypt20_1.8.1-1.dsc
 7a2875f8b1ae0301732e878c0cca2c9664ff09ef71408f085c50e332656a78b3 2967344 
libgcrypt20_1.8.1.orig.tar.bz2
 9e08f467824855084594a14c4a0455963dac9a359d543e8c2a91ca3498ad031b 310 
libgcrypt20_1.8.1.orig.tar.bz2.asc
 0b26c83d902a3cc624ea743ae2cd2a08a6cd2b433d6c424497058afef3a49a15 27220 
libgcrypt20_1.8.1-1.debian.tar.xz
Files: 
 c343f9d2a71cc76f24baec1738342680 2914 libs optional libgcrypt20_1.8.1-1.dsc
 b21817f9d850064d2177285f1073ec55 2967344 libs optional 
libgcrypt20_1.8.1.orig.tar.bz2
 7da7be1dae72e715e5b5fd10373d6155 310 libs optional 
libgcrypt20_1.8.1.orig.tar.bz2.asc
 d2224f0e5320131120d0c55e2c844129 27220 libs optional 
libgcrypt20_1.8.1-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE0uCSA5741Jbt9PpepU8BhUOCFIQFAlmirHUACgkQpU8BhUOC
FITnRg//RQRg3fYdwnvjxPtDIRtjXyln7tWvaJljjwOagYCsMTFv8lzNJg3+sZGx
Gg1PyLeNYvB0qeefuu/B8vCufQQz6xDfUrSmD25p7EwXcubzetUlHBBtxlwMrNr4
cg6U03jE64DM238o27kyn56z064tO9Fo1nmF9OXijUZx1ugmYEvMT1gR0G49YKZ3
y3Blth/wJLLddMmsHRRcKGDpWOI4wlJ+77T1Yx5pbrDDygIzBugFT9G9Wr0Dr+C+
XHXTDmHlRDC11Cg9UaS7h7Fur8mZMsWLV+4mv6ySCMXpe1mZYU6GUhmR5D7ngm4g
+qH+nL39IL1xvF8VAPPIflbwGVe9AximGFU/sPOoq

Bug#873362: coinor-libcoinutils3v5: unannounced ABI change without SONAME change?

[Anton Gladky]

Hi Rene,

thanks for the bug report and sorry for inconvenience. Upstream did
not change the SO-version, so I decided not to do it explicitly and
request transition. Looks like the changes were minimal.

If the coinmp-recompilation really fixes your problem, I would ask for
binnmus of all rdepends.

Thanks

Anton


2017-08-27 0:53 GMT+02:00 Rene Engelhard :
> Package: coinor-libcoinutils3v5
> Version: 2.10.14+repack1-1
> Severity: serious

Processed: bug 873386 is forwarded to https://github.com/LuaJIT/LuaJIT/issues/325

[Debian Bug Tracking System]

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

> forwarded 873386 https://github.com/LuaJIT/LuaJIT/issues/325
Bug #873386 [libluajit-5.1-dev] LuaJIT 2.1 breaks Lua 5.1 API
Set Bug forwarded-to-address to 'https://github.com/LuaJIT/LuaJIT/issues/325'.
> thanks
Stopping processing here.

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

Bug#872079: libwine32 will not install

[Antoine]

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?



signature.asc
Description: OpenPGP digital signature

Processed: Re: Attributing the problem to NM after all

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #870171 [network-manager] WPA usage error: Invalid passphrase character
Added tag(s) moreinfo.

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

Bug#873386: LuaJIT 2.1 breaks Lua 5.1 API

[Evgeni Golov]

Package: libluajit-5.1-dev
Version: 2.1.0~beta3+dfsg-2
Severity: serious
Tags: upstream

Hi,

LuaJIT 2.1 introduces symbols from Lua 5.2 [1] and drops a few compat symbols 
[2] that are still present in Lua 5.1 [3].
This breaks software that either not expects these 5.2 symbols, or expects the 
compat stuff to be present. [4]

I don't think the current state is apropriate for testing.

Regards
Evgeni

[1] 
https://github.com/LuaJIT/LuaJIT/commit/de97b9d52bbc42effeaf1180764053a912526873
[2] 
https://github.com/LuaJIT/LuaJIT/commit/dc320ca70f2c5bb3977b82853bcee6dad2523d01
[3] https://www.lua.org/source/5.1/lauxlib.h.html
[4] https://github.com/LuaJIT/LuaJIT/issues/325

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

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

Versions of packages libluajit-5.1-dev:amd64 depends on:
ii  libluajit-5.1-2  2.1.0~beta3+dfsg-2

libluajit-5.1-dev:amd64 recommends no packages.

libluajit-5.1-dev:amd64 suggests no packages.

-- no debconf information

Bug#870171: Attributing the problem to NM after all

[Michael Biebl]

Control: tags -1 + moreinfo

On Sun, 30 Jul 2017 20:22:07 +0200 "Eduard Bloch"
 wrote:
> clone 849875 -1
> reassign -1 network-manager
> retitle -1 WPA usage error: Invalid passphrase character
> thanks
> 
> On Sat, Jul 01, 2017 at 11:32:28PM +0200, Francesco Poli wrote:
> > Dear Debian wpasupplicant Maintainers,
> > I noticed that these 3 RC bugs (#849122, #849077, #849875) are marked
> > as found in wpa/2.6-2, which is now superseded by versions with epoch 2.
> > What seems to have happened (please correct me, if I am wrong) is that
> > the upstream version 2.4 was reintroduced into unstable (with epoch 2)
> > and then migrated to stretch (before the stretch release as stable).
> > 
> > Hence, I would say that those three bugs only affect experimental and
> > are not in stretch, buster or sid.
> > 
> > Could you please confirm that these 3 bugs should be marked as fixed in
> > wpa/2:2.4-1 and found in wpa/2:2.6-4 ?
> 
> Ok, now the problem from the original report has hit me too.
> 
> I could not figure out what is going on. I selected an AP which has been
> working fine for months, and suddenly NM switched me to another AP
> (which works partly since it is far away and reception quality is bad).
> 
> I tried removing wpasupplicant and network-manager. Purging config.
> Nothing helps. Checking the log, and WOW... (see attachment).
> So wpa_supplicant says "Line 0: Invalid passphrase character".
> Line 0 of what? This is most likely the input from NM which means: NM
> feeds wpa_supplicant with CRAP. But which crap? When NM asked me for
> passphrase, I am absolutely sure that I entered the correct one.

Does the password have any special characters?
Can you change the WPA passphrase to something else (say only letters)
and try again?
Please also provide a full debug log from NetworkManager (and
wpasupplicant) when the problem happens.
https://wiki.gnome.org/Projects/NetworkManager/Debugging

which versions of wpasupplicant and network-manager do you have installed?



signature.asc
Description: OpenPGP digital signature

Bug#862472: tack: FTBFS: ./tack.h:78:32: error: dereferencing pointer to incomplete type 'TERMINAL {aka struct term}'

[Thomas Dickey]

On Sat, Aug 26, 2017 at 01:37:20PM +0200, Sven Joachim wrote:
> On 2017-07-27 05:06 -0400, Thomas Dickey wrote:
> 
> > Debian's package hasn't kept up with any of the other changes in tack.
> > Let's see how long it takes for it to be updated to 1.08:
> >
> > http://invisible-island.net/ncurses/tack/CHANGES.html
> 
> Thanks for the new upstream release.  I have prepared a Debian package
> at [1], if the maintainer does not respond I will ask for a sponsor.
> 
> Cheers,
>Sven
> 
> 
> 1. https://anonscm.debian.org/git/users/joachim-guest/tack.git/log/?h=nmu

sounds good (I also considered making the ncurses headers generate
deprecation warnings, but that looked like more clutter than I'd like).

-- 
Thomas E. Dickey 
http://invisible-island.net
ftp://ftp.invisible-island.net


signature.asc
Description: Digital signature

Processed: closing 870232, forcibly merging 870232 870230

[Debian Bug Tracking System]

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

> close 870232
Bug #870232 [debhelper] flex FTBFS: dh_install: Cannot find (any matches for) 
"debian/tmp/include" (tried in ., debian/tmp)
Marked Bug as done
> forcemerge 870232 870230
Bug #870232 {Done: Christian Hofstaedtler } [debhelper] flex 
FTBFS: dh_install: Cannot find (any matches for) "debian/tmp/include" (tried in 
., debian/tmp)
Bug #870230 {Done: Tobias Frost } [debhelper] libpng-dev: 
error when installing together: trying to overwrite shared 
'/usr/bin/libpng16-config'
Severity set to 'serious' from 'important'
Merged 870230 870232
> thanks
Stopping processing here.

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

Bug#873383: marked as done (libgcrypt20: CVE-2017-0379: side-channel attack on Curve25519)

[Debian Bug Tracking System]

Your message dated Sun, 27 Aug 2017 10:55:58 +
with message-id 
and subject line Bug#873383: fixed in libgcrypt20 1.7.9-1
has caused the Debian Bug report #873383,
regarding libgcrypt20: CVE-2017-0379: side-channel attack on Curve25519
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.)


-- 
873383: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873383
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgcrypt20
Version: 1.7.1-1
Severity: grave
Tags: upstream patch security fixed-upstream

Hi,

the following vulnerability was published for libgcrypt20.

CVE-2017-0379[0]:
side-channel attack on Curve25519

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-0379
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0379
[1] 
https://git.gnupg.org/cgi-bin/gitweb.cgi?p=libgcrypt.git;a=commit;h=da780c81838f533c8ace8211ac2cb2bdee7b

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: libgcrypt20
Source-Version: 1.7.9-1

We believe that the bug you reported is fixed in the latest version of
libgcrypt20, 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.
Andreas Metzler  (supplier of updated libgcrypt20 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, 27 Aug 2017 11:56:17 +0200
Source: libgcrypt20
Binary: libgcrypt20-doc libgcrypt20-dev libgcrypt20 libgcrypt20-udeb 
libgcrypt11-dev libgcrypt-mingw-w64-dev
Architecture: source
Version: 1.7.9-1
Distribution: unstable
Urgency: high
Maintainer: Debian GnuTLS Maintainers 
Changed-By: Andreas Metzler 
Closes: 873383
Description: 
 libgcrypt11-dev - transitional libgcrypt11-dev package
 libgcrypt20-dev - LGPL Crypto library - development files
 libgcrypt20-doc - LGPL Crypto library - documentation
 libgcrypt20 - LGPL Crypto library - runtime library
 libgcrypt20-udeb - LGPL Crypto library - runtime library (udeb)
 libgcrypt-mingw-w64-dev - LGPL Crypto library - Windows development
Changes:
 libgcrypt20 (1.7.9-1) unstable; urgency=high
 .
   * New upstream version, mitigates a local side-channel attack on Curve25519
 dubbed "May the Fourth be With You".  [CVE-2017-0379] Closes: #873383
 + Drop 30_mpi-Fix-mpi_set_secure.patch
Checksums-Sha1: 
 a9fb596aa341d031f137ceeb3a6f31e2b582bc4d 2914 libgcrypt20_1.7.9-1.dsc
 04126cdca54074d8768dea4287493a5b338a9a98 2897137 libgcrypt20_1.7.9.orig.tar.bz2
 ec6cd788d04aec601a953b26eb8321aa2d144253 310 libgcrypt20_1.7.9.orig.tar.bz2.asc
 2f26728ba8895647696ac87ad4102c6980f42f76 26020 
libgcrypt20_1.7.9-1.debian.tar.xz
Checksums-Sha256: 
 d922d12b25a64cd25601b34380bed9c9ca3c8fd4c9625951641fcc8766c7796d 2914 
libgcrypt20_1.7.9-1.dsc
 bfe9bb703c1126c3647da2810fd23039c2f09d46969f71612c2065dc3fa9373b 2897137 
libgcrypt20_1.7.9.orig.tar.bz2
 96108d1701cd3c8a6826d7d2a27056de79421fe20bf9ef447e8c12e982f64414 310 
libgcrypt20_1.7.9.orig.tar.bz2.asc
 1a0775f8e8921aa537db92c06cca82780cb24adf04775e2f944a23d867414d55 26020 
libgcrypt20_1.7.9-1.debian.tar.xz
Files: 
 6fb53ee561e080cd20c74e85fd2956aa 2914 libs optional libgcrypt20_1.7.9-1.dsc
 439432d08fa5aa826752589ea1b69efc 2897137 libs optional 
libgcrypt20_1.7.9.orig.tar.bz2
 62b5984d10ce92111cca0bc41cfd6ad3 310 libs optional 
libgcrypt20_1.7.9.orig.tar.bz2.asc
 b69a1c475593a087699f97d2ab437628 26020 libs optional 
libgcrypt20_1.7.9-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE0uCSA5741Jbt9PpepU8BhUOCFIQFAlmioX4ACgkQpU8BhUOC
FIQNyg//YlalRpHjPjCqVjrAvFvzSu0+Mxf+w8Tz2d0sOcUnR696XcugeDAyvaj3
/bcuFuZzGmtyli0wLIxjVVLIWb8WCCTVcI268anAYJlBofNKKDbwvvBRm+gCNNcq
JKNIOVMd595QbIPHnt1mM71QxjLjM1lPMRunvAEafReFpFz3EtLQ9nGwhbeqET38
hkrgmguGAc6pQchaJw26FA/6ZjN4ANI75n6YtX0rCq3gVxOFMiI+aYLgQG44R8TS
paaF3IbLS2lpZCR/o1xMNIrTPA7TuMJ4fo9utmfcSqgxDfrlga8316SugQLEY3sG
MFkwjEdF3yRZ6d7gBG6ec75JJWQENiZVCQurdVWEKmolwmSK1UX71wESdLuSxmij
WwBJLDY20dFWtk+2GIgmDHdJwqbr4DpOpwkSQfifzhjlD3i65XisYCiNWNiizQe/
UWPKRrXq7qIhbtm5uyRZvc+ddMJHFukaSZ

Processed (with 1 error): closing 870232, forcibly merging 870232 870230

[Debian Bug Tracking System]

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

> close 870232
Bug #870232 [src:flex] flex FTBFS: dh_install: Cannot find (any matches for) 
"debian/tmp/include" (tried in ., debian/tmp)
Marked Bug as done
> forcemerge 870232 870230
Bug #870232 {Done: Christian Hofstaedtler } [src:flex] flex 
FTBFS: dh_install: Cannot find (any matches for) "debian/tmp/include" (tried in 
., debian/tmp)
Unable to merge bugs because:
package of #870230 is 'debhelper' not 'src:flex'
Failed to forcibly merge 870232: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Processed: reassign 870232 to debhelper, found 870232 in 10.7, fixed 870232 in 10.7.1

[Debian Bug Tracking System]

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

> reassign 870232 debhelper
Bug #870232 {Done: Christian Hofstaedtler } [src:flex] flex 
FTBFS: dh_install: Cannot find (any matches for) "debian/tmp/include" (tried in 
., debian/tmp)
Bug reassigned from package 'src:flex' to 'debhelper'.
No longer marked as found in versions flex/2.6.1-1.3.
Ignoring request to alter fixed versions of bug #870232 to the same values 
previously set
> found 870232 10.7
Bug #870232 {Done: Christian Hofstaedtler } [debhelper] flex 
FTBFS: dh_install: Cannot find (any matches for) "debian/tmp/include" (tried in 
., debian/tmp)
Marked as found in versions debhelper/10.7 and reopened.
> fixed 870232 10.7.1
Bug #870232 [debhelper] flex FTBFS: dh_install: Cannot find (any matches for) 
"debian/tmp/include" (tried in ., debian/tmp)
Marked as fixed in versions debhelper/10.7.1.
> thanks
Stopping processing here.

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

Processed: Bug#853664 marked as pending

[Debian Bug Tracking System]

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

> tag 853664 pending
Bug #853664 [src:snoopy] snoopy: ftbfs with GCC-7
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#853664: marked as pending

[Lukas Schwaighofer]

tag 853664 pending
thanks

Hello,

Bug #853664 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-security/snoopy.git/commit/?id=4e91817

---
commit 4e918172a06ea2c390c3cc009c20c7793c919b2d
Author: Lukas Schwaighofer 
Date:   Sun Aug 27 12:21:43 2017 +0200

Fix FTBFS with GCC-7

No longer compare pointer with the zero constant character.

Closes: #853664

diff --git a/debian/changelog b/debian/changelog
index 4f3ced3..b08e174 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+snoopy (2.4.6-2) unstable; urgency=medium
+
+  * Team upload.
+  * No longer compare pointer with the zero constant character to fix FTBFS
+with GCC-7 (Closes: #853664).
+
+ -- Lukas Schwaighofer   Sun, 27 Aug 2017 12:18:19 
+0200
+
 snoopy (2.4.6-1) unstable; urgency=medium
 
   [ Marcos Fouces ]

Bug#873163: polib FTBFS: FAIL: test_save_as_mofile

[Jakub Wilk]

* Adrian Bunk , 2017-08-25, 10:02:

==
FAIL: test_save_as_mofile (__main__.TestPoFile)
--
Traceback (most recent call last):
 File "tests/tests.py", line 567, in test_save_as_mofile
   self.assertEqual(s1, s2)
AssertionError: ... (huge string removed by bug submitter)


This is most likely fallout from #792687.

msgfmt now removes the POT-Creation-Date header from MO files, but polib does 
not.


As a quick-and-dirty fix, you could remove this header from 
tests/test_save_as_mofile.po.


--
Jakub Wilk

Bug#873383: libgcrypt20: CVE-2017-0379: side-channel attack on Curve25519

[Salvatore Bonaccorso]

Source: libgcrypt20
Version: 1.7.1-1
Severity: grave
Tags: upstream patch security fixed-upstream

Hi,

the following vulnerability was published for libgcrypt20.

CVE-2017-0379[0]:
side-channel attack on Curve25519

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-0379
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0379
[1] 
https://git.gnupg.org/cgi-bin/gitweb.cgi?p=libgcrypt.git;a=commit;h=da780c81838f533c8ace8211ac2cb2bdee7b

Regards,
Salvatore

Bug#853525: marked as done (llvm-toolchain-snapshot: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Sun, 27 Aug 2017 09:01:03 +
with message-id 
and subject line Bug#853525: fixed in llvm-toolchain-snapshot 1:6.0~svn311834-1
has caused the Debian Bug report #853525,
regarding llvm-toolchain-snapshot: 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.)


-- 
853525: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853525
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:llvm-toolchain-snapshot
Version: 1:4.0~svn291432-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/llvm-toolchain-snapshot_4.0~svn291432-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

[...]
cd "/<>/build-llvm/tools/clang/lib/ARCMigrate" && /usr/bin/cmake 
-E cmake_link_script CMakeFiles/clangARCMigrate.dir/link.txt --verbose=1
/usr/bin/ar qc ../../../../lib/libclangARCMigrate.a  
CMakeFiles/clangARCMigrate.dir/ARCMT.cpp.o 
CMakeFiles/clangARCMigrate.dir/ARCMTActions.cpp.o 
CMakeFiles/clangARCMigrate.dir/FileRemapper.cpp.o 
CMakeFiles/clangARCMigrate.dir/ObjCMT.cpp.o 
CMakeFiles/clangARCMigrate.dir/PlistReporter.cpp.o 
CMakeFiles/clangARCMigrate.dir/TransAPIUses.cpp.o 
CMakeFiles/clangARCMigrate.dir/TransARCAssign.cpp.o 
CMakeFiles/clangARCMigrate.dir/TransAutoreleasePool.cpp.o 
CMakeFiles/clangARCMigrate.dir/TransBlockObjCVariable.cpp.o 
CMakeFiles/clangARCMigrate.dir/TransEmptyStatementsAndDealloc.cpp.o 
CMakeFiles/clangARCMigrate.dir/TransGCAttrs.cpp.o 
CMakeFiles/clangARCMigrate.dir/TransGCCalls.cpp.o 
CMakeFiles/clangARCMigrate.dir/TransProperties.cpp.o 
CMakeFiles/clangARCMigrate.dir/TransProtectedScope.cpp.o 
CMakeFiles/clangARCMigrate.dir/TransRetainReleaseDealloc.cpp.o 
CMakeFiles/clangARCMigrate.dir/TransUnbridgedCasts.cpp.o 
CMakeFiles/clangARCMigrate.dir/TransUnusedInitDelegate.cpp.o 
CMakeFiles/clangARCMigrate.d
 ir/TransZeroOutPropsInDealloc.cpp.o 
CMakeFiles/clangARCMigrate.dir/TransformActions.cpp.o 
CMakeFiles/clangARCMigrate.dir/Transforms.cpp.o
/usr/bin/ranlib ../../../../lib/libclangARCMigrate.a
make[4]: Leaving directory '/<>/build-llvm'
[ 60%] Built target clangARCMigrate
[ 60%] Linking CXX static library 
../../../../../../lib/libclangTidyModernizeModule.a
cd "/<>/build-llvm/tools/clang/tools/extra/clang-tidy/modernize" 
&& /usr/bin/cmake -P 
CMakeFiles/clangTidyModernizeModule.dir/cmake_clean_target.cmake
cd "/<>/build-llvm/tools/clang/tools/extra/clang-tidy/modernize" 
&& /usr/bin/cmake -E cmake_link_script 
CMakeFiles/clangTidyModernizeModule.dir/link.txt --verbose=1
/usr/bin/ar qc ../../../../../../lib/libclangTidyModernizeModule.a  
CMakeFiles/clangTidyModernizeModule.dir/AvoidBindCheck.cpp.o 
CMakeFiles/clangTidyModernizeModule.dir/DeprecatedHeadersCheck.cpp.o 
CMakeFiles/clangTidyModernizeModule.dir/LoopConvertCheck.cpp.o 
CMakeFiles/clangTidyModernizeModule.dir/LoopConvertUtils.cpp.o 
CMakeFiles/clangTidyModernizeModule.dir/MakeSmartPtrCheck.cpp.o 
CMakeFiles/clangTidyModernizeModule.dir/MakeSharedCheck.cpp.o 
CMakeFiles/clangTidyModernizeModule.dir/MakeUniqueCheck.cpp.o 
CMakeFiles/clangTidyModernizeModule.dir/ModernizeTidyModule.cpp.o 
CMakeFiles/clangTidyModernizeModule.dir/PassByValueCheck.cpp.o 
CMakeFiles/clangTidyModernizeModule.dir/RawStringLiteralCheck.cpp.o 
CMakeFiles/clangTidyModernizeModule.dir/RedundantVoidArgCheck.cpp.o 
CMakeFiles/clangTidyModernizeModule.dir/ReplaceAutoPtrCheck.cpp.o 
CMakeFiles/clangTidyModernizeModule.dir/ShrinkToFitCheck.cpp.o 
CMakeFiles/clangTidyModernizeModule.dir/UseAutoCheck.cpp.o 
CMakeFiles

Bug#872020: marked as done (frobby FTBFS: latex: not found)

[Debian Bug Tracking System]

Your message dated Sun, 27 Aug 2017 08:54:22 +
with message-id 
and subject line Bug#872020: fixed in frobby 0.9.0-4
has caused the Debian Bug report #872020,
regarding frobby FTBFS: latex: not found
to be marked as done.

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

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


-- 
872020: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872020
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: frobby
Version: 0.9.0-3
Severity: serious

https://buildd.debian.org/status/package.php?p=frobby&suite=sid

...
for i in 1 2 3; do latex -output-directory=bin/doc/ doc/manual.tex; done
/bin/sh: 1: latex: not found
/bin/sh: 1: latex: not found
/bin/sh: 1: latex: not found
Makefile:253: recipe for target 'docPs' failed
make[2]: *** [docPs] Error 127
--- End Message ---
--- Begin Message ---
Source: frobby
Source-Version: 0.9.0-4

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 13 Aug 2017 19:56:10 -0400
Source: frobby
Binary: frobby libfrobby0 libfrobby-dev libfrobby-doc
Architecture: source amd64 all
Version: 0.9.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Doug Torrance 
Description:
 frobby - Computations with monomial ideals
 libfrobby-dev - Computations with monomial ideals (development tools)
 libfrobby-doc - Computations with monomial ideals (library documentation)
 libfrobby0 - Computations with monomial ideals (shared library)
Closes: 872020
Changes:
 frobby (0.9.0-4) unstable; urgency=medium
 .
   * debian/control
 - Move all dependencies back to Build-Depends. Some documentation
   is shipped with the architecture-dependent package frobby, and
   so we need these dependencies on all architectures
   (Closes: #872020).
Checksums-Sha1:
 31bd9cc49d5ee2603bb3b90ed083723def5254e0 2326 frobby_0.9.0-4.dsc
 ed0364bd13969f5b4be9086deea65c9933bbe3ba 7212 frobby_0.9.0-4.debian.tar.xz
 148c5f1b2f46c0c361eed9e919a35341cc9837f2 9412 frobby_0.9.0-4_amd64.buildinfo
 47c4e01ec61a5b830b10aa2a4bb5fcd350268bb7 731270 frobby_0.9.0-4_amd64.deb
 df64c837c506c59ff7141c36e4c4eba0b1b5375f 10136 libfrobby-dev_0.9.0-4_amd64.deb
 91c8a17109aee4c7b60d4f5b6fff2cccbebcc4ad 6058252 libfrobby-doc_0.9.0-4_all.deb
 643985f2151d98c7901ed8c03788f530254e46c6 7204890 
libfrobby0-dbgsym_0.9.0-4_amd64.deb
 b1fe68ee72eff7df8474aa1844a6e88edac16159 468900 libfrobby0_0.9.0-4_amd64.deb
Checksums-Sha256:
 b014aaa33457006f51e99c9d3a997d56dc9bb83c896daac3d92b6cf15900cdeb 2326 
frobby_0.9.0-4.dsc
 1a918c35f12776d780e11d1319024fa99e9f5c8e52bea19bdb9a06a3027abeb2 7212 
frobby_0.9.0-4.debian.tar.xz
 a3e54da876021b537101ceed82ae8b54a45e1933650ef5725d6c06dfcb563b83 9412 
frobby_0.9.0-4_amd64.buildinfo
 91191c90327202da2b87b65b42666f681e168ecd5446b09368a956ab1148bd5b 731270 
frobby_0.9.0-4_amd64.deb
 77fe1cf11179040eb0f7712d5191cd6d3c2b42eddfe92b90bc956b958e387a2b 10136 
libfrobby-dev_0.9.0-4_amd64.deb
 bcfc54fe28fd300504f27449c931b8ad3c90146702643e4531967973cf91f9f6 6058252 
libfrobby-doc_0.9.0-4_all.deb
 5a511ab4557f4fe0a5b9658d1b6ab71ca26e8911563d7716e67702778407a494 7204890 
libfrobby0-dbgsym_0.9.0-4_amd64.deb
 a1e1c4d8419c478f028a0bcad626b9c95726391448cf03d36a2db840317834de 468900 
libfrobby0_0.9.0-4_amd64.deb
Files:
 f1ad35a7003ac13e1d9c560f345c5e5c 2326 math optional frobby_0.9.0-4.dsc
 d22d69a88edef51521d24bbcd89b17d0 7212 math optional 
frobby_0.9.0-4.debian.tar.xz
 de1fd2aa8bc2b4a52e5648ee75a19bc0 9412 math optional 
frobby_0.9.0-4_amd64.buildinfo
 368a4c34203034e9eae7e87da069db7d 731270 math optional frobby_0.9.0-4_amd64.deb
 193645c27ed5feb8d0b3b504c7e68e8b 10136 libdevel optional 
libfrobby-dev_0.9.0-4_amd64.deb
 629c657b56b06df21114e4056882c1e4 6058252 doc optional 
libfrobby-doc_0.9.0-4_all.deb
 578dd4a27a6964146a012c2b466ed8a1 7204890 debug extra 
libfrobby0-dbgsym_0.9.0-4_amd64.deb
 00562e89a5a45e1df687632569a1bd05 468900 math optional 
libfrobby0_0.9.0-4_amd64

Processed: bug 873163 is forwarded to https://bitbucket.org/izi/polib/issues/86/ftbfs-in-debian-unstable

[Debian Bug Tracking System]

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

> forwarded 873163 
> https://bitbucket.org/izi/polib/issues/86/ftbfs-in-debian-unstable
Bug #873163 [src:polib] polib FTBFS: FAIL: test_save_as_mofile
Set Bug forwarded-to-address to 
'https://bitbucket.org/izi/polib/issues/86/ftbfs-in-debian-unstable'.
> thanks
Stopping processing here.

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

Bug#873377: tcpdump FTBFS on ppc64el: Failed test: ikev2pI2

[Adrian Bunk]

Source: tcpdump
Version: 4.9.1-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=tcpdump&arch=ppc64el&ver=4.9.1-1&stamp=1503778505&raw=0

...
   1 tests failed
 265 tests passed


Failed test: ikev2pI2

41c41
< (v2auth: len=196 method=rsasig 
authdata=()
 ))
---
> (v2auth: len=196 method=rsasig 
> authdata=(9d7686de6fabda36c4b374135ccca0c4596fe7636e19ee71ea7d276b4230948ab529651ba1dbec39e85e506ff90b48a57611be386a5867beccde9c9971587907251df58f0c46b473d9f0abc308eb85482f08383d)
>  ))


Makefile:439: recipe for target 'check' failed
make[1]: *** [check] Error 1

Processed: tagging 873163

[Debian Bug Tracking System]

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

> tags 873163 + upstream
Bug #873163 [src:polib] polib FTBFS: FAIL: test_save_as_mofile
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Processed: found 873201 in 1:7.5p1-5

[Debian Bug Tracking System]

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

> found 873201 1:7.5p1-5
Bug #873201 [openssh-client] openssh-client: command line parsing with -- 
between option and non-option arguments completely broken
Marked as found in versions openssh/1:7.5p1-5.
> thanks
Stopping processing here.

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

Bug#873320: marked as done (ettercap FTBFS with luajit 2.1)

[Debian Bug Tracking System]

Your message dated Sun, 27 Aug 2017 07:19:01 +
with message-id 
and subject line Bug#873320: fixed in ettercap 1:0.8.2-7
has caused the Debian Bug report #873320,
regarding ettercap FTBFS with luajit 2.1
to be marked as done.

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

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


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

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

...
-- Couldn't find a suitable system-provided version of LuaJIT
CMake Error at cmake/Modules/EttercapLuajit.cmake:30 (message):
  Could not find LUAJIT!
Call Stack (most recent call first):
  CMakeLists.txt:138 (include)


-- Configuring incomplete, errors occurred!
--- End Message ---
--- Begin Message ---
Source: ettercap
Source-Version: 1:0.8.2-7

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 27 Aug 2017 08:19:10 +0200
Source: ettercap
Binary: ettercap-common ettercap-text-only ettercap-graphical ettercap-dbg
Architecture: source
Version: 1:0.8.2-7
Distribution: unstable
Urgency: medium
Maintainer: Barak A. Pearlmutter 
Changed-By: Gianfranco Costamagna 
Description:
 ettercap-common - Multipurpose sniffer/interceptor/logger for switched LAN
 ettercap-dbg - Debug symbols for Ettercap
 ettercap-graphical - Ettercap GUI-enabled executable
 ettercap-text-only - Ettercap console-mode executable
Closes: 873320
Changes:
 ettercap (1:0.8.2-7) unstable; urgency=medium
 .
   * Disable lua binding, thanks Adrian Bunk
 for the report! (Closes: #873320)
   * Bump std-version to 4.1.0, no changes required.
   * Switch VCS fields in https mode.
Checksums-Sha1:
 df7b996e577d36278e6c532d9110edc39e93df6a 2277 ettercap_0.8.2-7.dsc
 5d72a066ad416b7334670dcb3cbc56d034b7c409 16700 ettercap_0.8.2-7.debian.tar.xz
Checksums-Sha256:
 9ceaa140d2b7a4da24451231601e3db683565d7e72aaf93f62a72e4846547a74 2277 
ettercap_0.8.2-7.dsc
 1987ac03707a489257e952a182b76e5c6921f315dec3ee6b7bfd3f5294680e69 16700 
ettercap_0.8.2-7.debian.tar.xz
Files:
 0c7fed7fb46390d70902227e2c7935bd 2277 net optional ettercap_0.8.2-7.dsc
 a65ac5bc5f4061961fdc7e8b7785a162 16700 net optional 
ettercap_0.8.2-7.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJZompNAAoJEPNPCXROn13ZSX4QAKhxWW5cRvO8PMoVOYYm/x2Y
oTpJFmx1HcWVW7GPgXsv/b4WkWl8YiMEHpnm0nf5BFSkor9QGta3nhPrE1mXJMck
wNWFN2sxZzQXygGKu/1FEeCiBpQ74IPi07ZpEBqdbLlCazPEefJ7Iz8LujcA+MVW
sCwA8yA+UQ2EUpe9jobxBCD04CYNojVEgI7vWNzHD189WMHBZFiwRet8RD3DLkfP
MUnQsAiypBDBASGz4rc1/pjdP9Wl5Y5f5BRxUPvw4CDe5F8J/bpLze5knbcdmy84
25TGktkoMhdayNM204z+xlyG1oHaBH/GI7aAZfkXOghtrpKa40dbyAtwevvA7USL
Gkiee8iEXthMtKpIbsn9yNDw+J2uDY/sXmJeiRThXnJGyOPIkcpFGwC6wmHGhw1z
0nYvmzsgEtn4//gG6Nft8TCmFnMyESQTyjMPGLFHGf0cY889G3d4JXP65IIZ3EwB
6rlgDx8bD2Y/56ZSLNYFOc+v711RrbmXkgacb2bEfluec2EgphEl3272ZVWA86fj
SaO/NDZk2jT+A8yo/+ZCVDQIXjP0Gfawx9fj2n2WWcsOVSQ7IrocEHfkc/BAxgHx
k+PxI1o+7Nbbtitdnjq8xCQkQf2jsTBIaVAHbdcn+fZk4YvQJ70Eh8X0jGY3IFeL
4E01ggOvfCy6TwDCHzlb
=Z2Ta
-END PGP SIGNATURE End Message ---

Processed: libtsk13 4.4.2-1 crash in the dfvfs test suite

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:dfvfs python-tsk
Bug #873374 [libtsk13] libtsk13 4.4.2-1 crash in the dfvfs test suite
Added indication that 873374 affects src:dfvfs and python-tsk

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

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

[Adrian Bunk]

Package: libtsk13
Version: 4.4.2-1
Severity: serious
Control: affects -1 src:dfvfs python-tsk

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

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/dfvfs-20170723'
python run_tests.py
testIterateVolumes (volume.vshadow_volume_system.VShadowVolumeSystemTest)
Test the iterate volumes functionality. ... ok
testIterateVolumes (volume.tsk_volume_system.TSKVolumeSystemTest)
Test the iterate volumes functionality. ... debian/rules:23: recipe for target 
'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Floating point exception


Program terminated with signal SIGFPE, Arithmetic exception.
#0  0x7fa2ac0f606a in dos_load_prim_table (test=1 '\001', 
vs=0x55c56dcae270) at dos.c:821
821 dos.c: No such file or directory.
(gdb) bt
#0  0x7fa2ac0f606a in dos_load_prim_table (test=1 '\001', 
vs=0x55c56dcae270) at dos.c:821
#1  tsk_vs_dos_open (img_info=0x7fa2a322c070, offset=0, 
test=test@entry=1 '\001') at dos.c:1064
#2  0x7fa2ac0f3161 in tsk_vs_open (img_info=0x7fa2a322c070, offset=0, 
type=) at mm_open.c:56
#3  0x7fa2ac3bf41e in Volume_Info_Con (self=0x55c56dcbe2f0, 
img=, type=, offset=)
at tsk3.c:659
#4  0x7fa2ac3b3ade in pyVolume_Info_init (self=self@entry=0x7fa2a31b4c70, 
args=args@entry=(, _is_open=True, _file_object=) at remote 0x7fa2a31b4550>) at remote 0x7fa2a31b4590>, 
u'type: OS, location: /tmp/dfvfs-20170723/test_data/bdetogo.raw\n': 
) at remote 
0x7fa2a31b4bd0>}) at remote 0x7fa2a3fbad90>, 
_file_system_cache=) at remote 0x7fa2a3fba390>, 
_is_open=True, _file_object=) at remote 
0x7fa2a31b4890>) at remote 0x7fa2a31994b0>,), kwds=kwds@entry=0x0)
at pytsk3.c:20444
#5  0x55c56b688bf4 in type_call.lto_priv () at ../Objects/typeobject.c:765
#6  0x55c56b683163 in PyObject_Call () at ../Objects/abstract.c:2547
...



Works after downgrading libtsk13 to 4.4.0-5