Bug#873888: marked as pending

[Youhei SASAKI]

tag 873888 pending
thanks

Hello,

Bug #873888 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/git/users/uwabami-guest/dcl-f77.git/diff/?id=855ac8442f3cb563b5017c92bcbc1a5c5e382d60

---
From 855ac8442f3cb563b5017c92bcbc1a5c5e382d60 Mon Sep 17 00:00:00 2001
From: Youhei SASAKI 
Date: Sat, 2 Sep 2017 05:24:54 +0900
Subject: [PATCH 1/4] Separate arch|indep (Closes: #873888)

Signed-off-by: Youhei SASAKI 
---
 debian/dcl-f77-docs.install   |  2 ++
 debian/fonts-dclfonts.install |  5 -
 debian/rules  | 23 ++-
 3 files changed, 20 insertions(+), 10 deletions(-)
 create mode 100644 debian/dcl-f77-docs.install

diff --git a/debian/dcl-f77-docs.install b/debian/dcl-f77-docs.install
new file mode 100644
index 000..3c71747
--- /dev/null
+++ b/debian/dcl-f77-docs.install
@@ -0,0 +1,2 @@
+demo  usr/share/doc/dcl-f77-docs/
+doc  usr/share/doc/dcl-f77-docs/
diff --git a/debian/fonts-dclfonts.install b/debian/fonts-dclfonts.install
index 666d028..05d2c00 100644
--- a/debian/fonts-dclfonts.install
+++ b/debian/fonts-dclfonts.install
@@ -1 +1,4 @@
-usr/share/fonts/truetype/dclfonts/
+src/env1/sysfont/DCLMarker-Black.ttf   usr/share/fonts/truetype/dclfonts/
+src/env1/sysfont/DCLMarker-Bold.ttfusr/share/fonts/truetype/dclfonts/
+src/env1/sysfont/DCLMarker-Light.ttf   usr/share/fonts/truetype/dclfonts/
+src/env1/sysfont/DCLMarker-Regular.ttf usr/share/fonts/truetype/dclfonts/
diff --git a/debian/rules b/debian/rules
index fcc9238..8fce060 100755
--- a/debian/rules
+++ b/debian/rules
@@ -12,16 +12,19 @@ DCLVER=723
 %:
dh $@

-override_dh_auto_configure:
+override_dh_auto_configure-arch:
$(shell ! grep -q jessie /etc/os-release || \
  echo "activate-noawait ldconfig" > 
$(CURDIR)/debian/libf77dcl7.triggers )
CC=gcc FC=gfortran \
   dh_auto_configure -- $(dpkg-buildflags --export=configure) 
--with-gtk3

+override_dh_auto_configure-indep:
+#  do nothing
+
 override_dh_auto_test:
+#  do nothing

-override_dh_auto_install:
-   mkdir -p $(CURDIR)/debian/tmp/usr/share/fonts/truetype/dclfonts/
+override_dh_auto_install-arch:
dh_auto_install -- prefix=$(CURDIR)/debian/tmp/usr
rm $(CURDIR)/debian/tmp/usr/bin/dclconfig
mv $(CURDIR)/debian/tmp/usr/bin/dclconfig$(DCLVER) \
@@ -34,14 +37,16 @@ override_dh_auto_install:
( cd $(CURDIR)/debian/tmp/usr/lib/$(DEB_HOST_MULTIARCH) ; \
  ln -s libf77dcl.so.$(DCLVERNUM) libf77dcl.so )

-override_dh_install:
-   install -m644 $(CURDIR)/src/env1/sysfont/*.ttf \
- $(CURDIR)/debian/tmp/usr/share/fonts/truetype/dclfonts/
-   dh_install --sourcedir=debian/tmp
+override_dh_auto_install-indep:
+#  do nothing
+
+override_dh_install-arch:
+   dh_install -a --sourcedir=debian/tmp
sed -i -e 's%-fdebug-prefix-map.*\.%%g ' \
  $(CURDIR)/debian/libf77dcl-dev/usr/bin/dclconfig
-   cp -ar demo $(CURDIR)/debian/dcl-f77-docs/usr/share/doc/dcl-f77-docs/
-   cp -ar doc $(CURDIR)/debian/dcl-f77-docs/usr/share/doc/dcl-f77-docs/
+
+override_dh_install-indep:
+   dh_install -i --sourcedir=$(CURDIR)
find $(CURDIR)/debian/dcl-f77-docs/ -name Makefile.win | xargs rm -f

 override_dh_auto_clean:
--
2.14.1

Bug#864162: opendkim: systemd ExecStart ignore configuration options

[K. de Jong]

This bug affects also Debian stable (Stretch), is there any chance Debian
will fix this? Or are these one of those things that won't be touched now
Stretch is already released?


--
Kind regards,
Kees de Jong  |  OpenPGP fingerprint: 0x0E45C98AB51428E6

Processed: closing 753235

[Debian Bug Tracking System]

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

> close 753235
Bug #753235 [src:lldpad] lldpad: FTBFS: dpkg-source: error: expected ^--- in 
line 2 of diff `lldpad-0.9.46/debian/patches/fix-typo-in-lldptool-ets-8.patch'
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#753235: closing 753235

[Valentin Vidic]

close 753235 
thanks

Bug#871079: marked as done (pydenticon: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13)

[Debian Bug Tracking System]

Your message dated Sun, 03 Sep 2017 08:56:32 +
with message-id 
and subject line Bug#871079: fixed in pydenticon 0.3-2
has caused the Debian Bug report #871079,
regarding pydenticon: FTBFS: dh_auto_test: pybuild --test -i python{version} -p 
2.7 returned exit code 13
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.)


-- 
871079: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871079
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pydenticon
Version: 0.3-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):
>  debian/rules build
> dh build --with python2,python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:184: python2.7 setup.py config 
> running config
> I: pybuild base:184: python3.6 setup.py config 
> running config
> I: pybuild base:184: python3.5 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:184: /usr/bin/python setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/pythonX.Y_2.7/build/pydenticon
> copying pydenticon/__init__.py -> 
> /<>/.pybuild/pythonX.Y_2.7/build/pydenticon
> running egg_info
> writing requirements to pydenticon.egg-info/requires.txt
> writing pydenticon.egg-info/PKG-INFO
> writing top-level names to pydenticon.egg-info/top_level.txt
> writing dependency_links to pydenticon.egg-info/dependency_links.txt
> writing manifest file 'pydenticon.egg-info/SOURCES.txt'
> reading manifest file 'pydenticon.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> no previously-included directories found matching 'docs/_build'
> warning: no previously-included files found matching 'tmp/'
> writing manifest file 'pydenticon.egg-info/SOURCES.txt'
> I: pybuild base:184: /usr/bin/python3.6 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/pythonX.Y_3.6/build/pydenticon
> copying pydenticon/__init__.py -> 
> /<>/.pybuild/pythonX.Y_3.6/build/pydenticon
> running egg_info
> writing pydenticon.egg-info/PKG-INFO
> writing dependency_links to pydenticon.egg-info/dependency_links.txt
> writing requirements to pydenticon.egg-info/requires.txt
> writing top-level names to pydenticon.egg-info/top_level.txt
> reading manifest file 'pydenticon.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> no previously-included directories found matching 'docs/_build'
> warning: no previously-included files found matching 'tmp/'
> writing manifest file 'pydenticon.egg-info/SOURCES.txt'
> I: pybuild base:184: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/pythonX.Y_3.5/build/pydenticon
> copying pydenticon/__init__.py -> 
> /<>/.pybuild/pythonX.Y_3.5/build/pydenticon
> running egg_info
> writing top-level names to pydenticon.egg-info/top_level.txt
> writing pydenticon.egg-info/PKG-INFO
> writing dependency_links to pydenticon.egg-info/dependency_links.txt
> writing requirements to pydenticon.egg-info/requires.txt
> reading manifest file 'pydenticon.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> no previously-included directories found matching 'docs/_build'
> warning: no previously-included files found matching 'tmp/'
> writing manifest file 'pydenticon.egg-info/SOURCES.txt'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:184: python2.7 setup.py test 
> running test
> running egg_info
> writing requirements to pydenticon.egg-info/requires.txt
> writing pydenticon.egg-info/PKG-INFO
> writing top-level names to pydenticon.egg-info/top_level.txt
> writing dependency_links to pydenticon.egg-info/dependency_links.txt
> reading manifest file 'pydenticon.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> no previously-included directories found matching 'docs/_build'
> warning: no previously-included files found matching 'tmp/'
> writing manifest file 'pydenticon.egg-info/SOURCES.txt'
> running build_ext
> test_data_to_digest_byte_list_hex (tests.test_pydenticon.GeneratorTest) ... ok
> test_data_to_digest_byte_list_hex_lookalike 
> (tests.test_pydenticon.GeneratorTest) ... ok
> test_data_to_digest_byte_list_raw (tests.test_pydenticon.GeneratorTest) ... ok
> test_generate_ascii (tests.test_pydenticon.GeneratorTest) ... ok
> test_generate_foreground (tests.test_pydenticon.GeneratorTest) ... ok
> test_generate

Bug#874105: virtualbox: Virtualbox seems to conflict with BTRFS when trying to install ReactOS 0.4.6

[Svein Engelsgjerd]

Package: virtualbox
Version: 5.1.26-dfsg-2
Severity: grave
Justification: causes non-serious data loss

Dear Maintainer,

   * What led up to the situation?
I wanted to try to install ReactOS 0.4.6. My rootfs is btrfs with 
metadata=raid10 and data=raid1
While VirtualBox was running dmesg showed a constant stream of csum failed root 
5 ino XXX off XXX csum XXX expected csum XXX mirror 1 messages.
Note that the mirror was always 1.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
I stopped the VM that was running the ReactOS installer. All the errors stopped
I ran a scrub on my btrfs filesystem afterwards. No errors detected.
I checked smart data for my SSD's No errors detected, no sign of wear.
I tried various file operations (md5sum, sha1sum, cp, hexeditor etc...) on the 
.vdi file - no corruption messages

   * What was the outcome of this action?
While this could just as easily be a btrfs bug I suspect that  VirtualBox's 
vboxdrv is the cause here.
I may be wrong about this, so my apologies if that is the case.
Btrfs fixes the corruptions and appear to be in a good state as long as the 
VirutalBox VM is not running.
qemu/kvm works fine. Using that instead.

   * What outcome did you expect instead?
I expected no errors while running VirtualBox on top of my BTRFS rootfilessytem.

   * Other information:
While I did not experience any dataloss I fear that this is fragile and *might* 
cause dataloss for some.
this is the reason I classify this bug as grave. This is also causing me to 
avoid testing for a while
until I get some feedback on this one.

I am aware that BTRFS have it's share of bugs, but I run with a minimal 
configuration that have not caused
any issues for years (it has actually fixed a few silent data corruptions here 
and there).

So since my hardware and data checked out fine and the data is instact I think 
this could be a conflict
between the btrfs and/or vboxdrv module. I am not skilled enoguh to find that 
out for myself.

BTW: The VirtualBox vdi file contains a VFAT filesystem (reactos uses that). 
This does NOT appear to be
the issues as I have tested other stuff with VFAT without any issues.

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

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

Versions of packages virtualbox depends on:
ii  adduser   3.116
ii  init-system-helpers   1.49
ii  iproute2  4.9.0-1
ii  libc6 2.24-14
ii  libcurl3-gnutls   7.55.0-1
ii  libdevmapper1.02.12:1.02.137-2+b1
ii  libgcc1   1:7.2.0-1
ii  libgsoap-2.8.49   2.8.49-1
ii  libpng16-16   1.6.31-1
ii  libpython3.5  3.5.4-2
ii  libsdl1.2debian   1.2.15+dfsg2-0.1
ii  libssl1.1 1.1.0f-4
ii  libstdc++67.2.0-1
ii  libvncserver1 0.9.11+dfsg-1
ii  libvpx4   1.6.1-3
ii  libx11-6  2:1.6.4-3
ii  libxcursor1   1:1.1.14-1+b4
ii  libxext6  2:1.3.3-1+b2
ii  libxml2   2.9.4+dfsg1-3.1
ii  libxmu6   2:1.1.2-2
ii  libxt61:1.1.5-1
ii  procps2:3.3.12-3
ii  python3   3.5.3-3
ii  python3.5 3.5.4-2
ii  virtualbox-dkms [virtualbox-modules]  5.1.26-dfsg-2
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages virtualbox recommends:
ii  libgl1-mesa-glx [libgl1]  13.0.6-1+b2
ii  libqt5core5a  5.9.1+dfsg-9
ii  libqt5opengl5 5.9.1+dfsg-9
ii  libqt5widgets55.9.1+dfsg-9
ii  virtualbox-qt 5.1.26-dfsg-2

Versions of packages virtualbox suggests:
ii  vde22.3.2+r586-2.1
pn  virtualbox-guest-additions-iso  

-- no debconf information

Processed: Mark fixed-upstream

[Debian Bug Tracking System]

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

> tags 853715 fixed-upstream
Bug #853715 [src:yrmcds] yrmcds: ftbfs with GCC-7
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#873841: opengrm-ngram: Fix mips/mipsel FTBFS by reducing g++ memory usage

[Giulio Paci]

Hi Adrian,
thank you very much for this bug report and for the patch.

Do you think the same approach will work on sh4 as well?

Cheers,
Giulio


On Thu, 31 Aug 2017 17:52:40 +0300 Adrian Bunk  wrote:
> Source: opengrm-ngram
> Version: 1.3.2-2
> Severity: serious
> Tags: patch
> 
> https://buildd.debian.org/status/package.php?p=opengrm-ngram&suite=sid
> 
> ...
> libtool: compile:  g++ -DHAVE_CONFIG_H -I./../include -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -std=c++11 -c 
> hist-arc.cc  -fPIC -DPIC -o .libs/hist-arc.o
> ...
> virtual memory exhausted: Cannot allocate memory
> Makefile:481: recipe for target 'hist-arc.lo' failed
> make[4]: *** [hist-arc.lo] Error 1
> 
> 
> Fix:
> 
> --- debian/rules.old  2017-08-30 11:17:38.431222040 +
> +++ debian/rules  2017-08-30 11:19:57.964547509 +
> @@ -1,5 +1,12 @@
>  #!/usr/bin/make -f
>  
> +DEB_HOST_ARCH ?= $(shell dpkg-architecture -qDEB_HOST_ARCH)
> +
> +# reduce g++ memory usage to fix FTBFS
> +ifneq (,$(filter $(DEB_HOST_ARCH), mips mipsel))
> +export DEB_CXXFLAGS_MAINT_APPEND = --param ggc-min-expand=10
> +endif
> +
>  export DEB_BUILD_MAINT_OPTIONS = hardening=+all
>  export DEB_CFLAGS_MAINT_APPEND = -Wall
>  include /usr/share/dpkg/buildflags.mk
> 
> 
> 
> The mips64el FTBFS is unrelated, this is likely caused by the
> known gcc-7 breakage on mips64el (#871514).
> 
> 

Processed: retitle

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 An incomplete active theme can cause post-inst to fail on
Bug #858643 {Done: Aurélien COUDERC } [desktop-base] 
stretch-pu: package desktop-base/9.0.2+deb9u1
Changed Bug title to 'An incomplete active theme can cause post-inst to fail 
on' from 'stretch-pu: package desktop-base/9.0.2+deb9u1'.

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

Bug#858643: retitle

[Aurélien COUDERC]

control: retitle -1 An incomplete active theme can cause post-inst to fail on
upgrade/reinstall

Bug#858643: retitle for real

[Aurélien COUDERC]

control: retitle -1 An incomplete active theme can cause post-inst to fail on 
upgrade/reinstall

Processed: Re: retitle for real

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 An incomplete active theme can cause post-inst to fail on 
> upgrade/reinstall
Bug #858643 {Done: Aurélien COUDERC } [desktop-base] An 
incomplete active theme can cause post-inst to fail on
Changed Bug title to 'An incomplete active theme can cause post-inst to fail on 
upgrade/reinstall' from 'An incomplete active theme can cause post-inst to fail 
on'.

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

Processed: your mail

[Debian Bug Tracking System]

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

> notfound 873320 1:0.8.2-6
Bug #873320 {Done: Gianfranco Costamagna } 
[src:ettercap] ettercap FTBFS with luajit 2.1
No longer marked as found in versions ettercap/1:0.8.2-6.
> #testing is fine
> thanks
Stopping processing here.

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

Bug#873443: closed by Rene Engelhard (Bug#873443: fixed in libreoffice 1:5.4.1-1)

[Linus Lüssing]

On Thu, Aug 31, 2017 at 11:39:17AM +, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the libreoffice-core package:
> 
> #873443: terminate called after throwing an instance of 
> com::sun::star::uno::DeploymentException on architectures not using 
> libmergedlo.so
> 
> It has been closed by Rene Engelhard .

Hi Rene,

The buildbot finally finished for armhf and it works like charm
\o/.

And, wow, quite a changelog, thanks for the great work, Rene :-).

Cheers, Linus

Bug#853693: undertaker: diff for NMU version 1.6.1-4.1

[Adrian Bunk]

Control: tags 853693 + patch
Control: tags 853693 + pending

Dear maintainer,

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

cu
Adrian

-- 

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

diff -Nru undertaker-1.6.1/debian/changelog undertaker-1.6.1/debian/changelog
--- undertaker-1.6.1/debian/changelog	2016-12-21 23:08:23.0 +0200
+++ undertaker-1.6.1/debian/changelog	2017-09-03 14:54:27.0 +0300
@@ -1,3 +1,10 @@
+undertaker (1.6.1-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS with gcc 7. (Closes: #853693)
+
+ -- Adrian Bunk   Sun, 03 Sep 2017 14:54:27 +0300
+
 undertaker (1.6.1-4) unstable; urgency=medium
 
   * Bug fix: "FTBFS in parallel builds", thanks to Lucas Nussbaum
diff -Nru undertaker-1.6.1/debian/patches/gcc7-ftbfs.patch undertaker-1.6.1/debian/patches/gcc7-ftbfs.patch
--- undertaker-1.6.1/debian/patches/gcc7-ftbfs.patch	1970-01-01 02:00:00.0 +0200
+++ undertaker-1.6.1/debian/patches/gcc7-ftbfs.patch	2017-09-03 14:54:27.0 +0300
@@ -0,0 +1,204 @@
+Description: Fix FTBFS with gcc 7
+ Make some functions static.
+ .
+ "inline" without "extern" was not correct,
+ and there is  anyway no reason for them to be global.
+Author: Adrian Bunk 
+Bug-Debian: https://bugs.debian.org/853693
+
+--- undertaker-1.6.1.orig/tailor/src/traceutil-boost.cc
 undertaker-1.6.1/tailor/src/traceutil-boost.cc
+@@ -43,7 +43,7 @@ int ignoreFileReopenCounter = 0;
+  * inside a certain module's address range.
+  */
+ 
+-void readModules() {
++static void readModules() {
+ string moduleLine;
+ ifstream moduleFile;
+ loadedModules.clear();
+@@ -69,7 +69,7 @@ void readModules() {
+  * currently present.
+  */
+ 
+-bool addModuleAddr(unsigned long long addr) {
++static bool addModuleAddr(unsigned long long addr) {
+ for (map::iterator it=loadedModules.begin() ;
+  it != loadedModules.end(); it++ ) {
+ unsigned long long lowAddr = (*it).first;
+@@ -89,7 +89,7 @@ bool addModuleAddr(unsigned long long ad
+  * didn't scan the module table yet, a call to addModuleAddr(addr) is triggered.
+  */
+ 
+-bool addAddr(unsigned long long addr) {
++static bool addAddr(unsigned long long addr) {
+ // address new?
+ if (calledAddr.insert(addr).second) {
+ // module address (if modules enabled)?
+@@ -119,7 +119,7 @@ bool addAddr(unsigned long long addr) {
+  * functions are being encountered.
+  */
+ 
+-void ignoreFunc(string name) {
++static void ignoreFunc(string name) {
+ // Otherwise, we add the function's name to the ignore list.
+ if (ignoreFile == NULL
+ || ++ignoreFileReopenCounter >= ignoreFileReopenUpperBound) {
+--- undertaker-1.6.1.orig/tailor/src/traceutil-native.c
 undertaker-1.6.1/tailor/src/traceutil-native.c
+@@ -56,7 +56,7 @@ int numberSize=0;
+  * later test whether a given address is inside a certain module's address range
+  */
+ 
+-void readModules() {
++static void readModules() {
+ int size = 0;
+ int parsingMode = 0;
+ // Open module file
+@@ -168,7 +168,7 @@ void readModules() {
+  * currently present.
+  */
+ 
+-inline bool addModuleAddr(unsigned long long addr) {
++static inline bool addModuleAddr(unsigned long long addr) {
+ for (j=0; j= moduleBaseAddr) {
+@@ -264,7 +264,7 @@ inline bool addAddr(unsigned long long a
+  * functions are being encountered.
+  */
+ 
+-inline void ignoreFunc(char * callerBuffer, int callerSize) {
++static inline void ignoreFunc(char * callerBuffer, int callerSize) {
+ // Flushing does not work on debugfs, so we close and reopen the ignore file
+ if (ignoreFile == -1
+ || ++ignorePathReopenCounter >= ignorePathReopenUpperBound) {
+--- undertaker-1.6.1.orig/tailor/src/traceutil-native.h
 undertaker-1.6.1/tailor/src/traceutil-native.h
+@@ -74,10 +74,4 @@ typedef struct module {
+ int hexCharToDec[256];
+ char decToHexChar[16];
+ 
+-//function declarations
+-void readModules();
+-inline bool addModuleAddr(unsigned long long addr);
+-inline bool addAddr(unsigned long long addr);
+-inline void ignoreFunc(char * funcbuf, int funcbufp);
+-
+ #endif
+--- undertaker-1.6.1.orig/tailor/src/traceutil-stdio.c
 undertaker-1.6.1/tailor/src/traceutil-stdio.c
+@@ -41,7 +41,7 @@ int ignoreFileReopenCounter = 0;
+  * later test whether a given address is inside a certain module's address range
+  */
+ 
+-inline void readModules() {
++static inline void readModules() {
+ FILE * moduleFile;
+ moduleFile = fopen (modulePath,"r");
+ // On error, use old version of procmodules
+@@ -65,13 +65,39 @@ inline void readModules() {
+ fclose(moduleFile);
+ }
+ 
++/* This function adds an address from an LKM to the output. Therefore we iterate
++ * the

Processed: undertaker: diff for NMU version 1.6.1-4.1

[Debian Bug Tracking System]

Processing control commands:

> tags 853693 + patch
Bug #853693 [src:undertaker] undertaker: ftbfs with GCC-7
Added tag(s) patch.
> tags 853693 + pending
Bug #853693 [src:undertaker] undertaker: ftbfs with GCC-7
Added tag(s) pending.

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

Bug#874112: scm FTBFS on 32bit: ERROR: "r4rstest.scm": round-quotient: Wrong type in arg1 (0 . 0)

[Adrian Bunk]

Source: scm
Version: 5f2-1
Severity: serious

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

...
(float-print-test #t)  ==> #t
(mult-float-print-test #t)  ==> #t
(mult-float-print-test #t)  ==> #t
(mult-float-print-test #t)  ==> #t
(mult-float-print-test #t)  ==> #t
(mult-float-print-test #t)  ==> #t
(# cnt 308) success) (let* ((estr (string-append "1.e" 
(number->string cnt))) (num (string->number estr)) (str (number->string num))) 
(cond ((or (>= (string-length str) 10) (not (equal? (string->number str) num))) 
(set! success #f) (for-each write (list estr num str (string->number 
str>)  ==> 
;ERROR: "r4rstest.scm": round-quotient: Wrong type in arg1 (0 . 0)
; in expression: (#@number->string #@num)
; in scope:
;   num
;   estr
;   (cnt . #@do)
;   (success . #@define)
;   ()  procedure float-rw-range-test
;   (log2 slow-frexp float-precision float-print-test mult-float-print-test 
float-rw-range-test . #@define)
;   (f0.0 f0.5 f1.0 f2.0 . #@let)
;   ()  procedure test-inexact-printing
; defined by load: "r4rstest.scm"

;STACK TRACE
1; (#@let* ((estr (#@string-append "1.e" (#@number->string #@cnt) ...
2; (#@do ((cnt -323 (#@+ 1 #@cnt))) ((#@> #@cnt 308) success)  (# ...
3; (#@let ((res (#@if (#@procedure? #@0+1) (#@apply #@0+1 #@0-2)  ...
4; (#@let ((have-inexacts? (#@and (#@string->number "0.0") (#@ine ...
...

; program args: ("./scm" "-fr4rstest.scm" 
"-e(test-sc4)(test-cont)(test-delay)(gc)" "-e" "(or (null? errs) (quit 1))")
Makefile:555: recipe for target 'check' failed
make[1]: *** [check] Error 1

Bug#874115: openjpeg2: CVE-2017-14041: Stack-based buffer over-write in pgxtoimage function in bin/jp2/convert.c

[Salvatore Bonaccorso]

Source: openjpeg2
Version: 2.1.0-2
Severity: grave
Tags: upstream patch security
Forwarded: https://github.com/uclouvain/openjpeg/issues/997

Hi,

the following vulnerability was published for openjpeg2.

CVE-2017-14041[0]:
| A stack-based buffer overflow was discovered in the pgxtoimage function
| in bin/jp2/convert.c in OpenJPEG 2.2.0. The vulnerability causes an
| out-of-bounds write, which may lead to remote denial of service or
| possibly remote code execution.

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-14041
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-14041
[1] https://github.com/uclouvain/openjpeg/issues/997
[2] 
https://github.com/uclouvain/openjpeg/commit/e5285319229a5d77bf316bb0d3a6cbd3cb8666d9

Regards,
Salvatore

Bug#872155: marked as done (strongswan: CVE-2017-11185: Insufficient Input Validation in gmp Plugin)

[Debian Bug Tracking System]

Your message dated Sun, 03 Sep 2017 13:22:52 +
with message-id 
and subject line Bug#872155: fixed in strongswan 5.6.0-1
has caused the Debian Bug report #872155,
regarding strongswan: CVE-2017-11185: Insufficient Input Validation in gmp 
Plugin
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.)


-- 
872155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872155
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: strongswan
Version: 5.2.1-1
Severity: grave
Tags: upstream security patch
Control: fixed -1 5.2.1-6+deb8u5
Control: fixed -1 5.5.1-4+deb9u1

Hi,

the following vulnerability was published for strongswan, just filling
the corresponding tracking bug in the BTS.

CVE-2017-11185[0]:
denial of service in the gmp plugin

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-11185
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-11185
[1] 
https://www.strongswan.org/blog/2017/08/14/strongswan-vulnerability-(cve-2017-11185).html

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: strongswan
Source-Version: 5.6.0-1

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 03 Sep 2017 14:38:09 +0200
Source: strongswan
Binary: strongswan libstrongswan libstrongswan-standard-plugins 
libstrongswan-extra-plugins libcharon-extra-plugins strongswan-starter 
strongswan-libcharon strongswan-charon strongswan-ike strongswan-nm 
strongswan-ikev1 strongswan-ikev2 charon-cmd strongswan-pki 
strongswan-scepclient strongswan-swanctl charon-systemd
Architecture: source
Version: 5.6.0-1
Distribution: unstable
Urgency: medium
Maintainer: strongSwan Maintainers 
Changed-By: Yves-Alexis Perez 
Description:
 charon-cmd - standalone IPsec client
 charon-systemd - strongSwan IPsec client, systemd support
 libcharon-extra-plugins - strongSwan charon library (extra plugins)
 libstrongswan - strongSwan utility and crypto library
 libstrongswan-extra-plugins - strongSwan utility and crypto library (extra 
plugins)
 libstrongswan-standard-plugins - strongSwan utility and crypto library 
(standard plugins)
 strongswan - IPsec VPN solution metapackage
 strongswan-charon - strongSwan Internet Key Exchange daemon
 strongswan-ike - strongSwan Internet Key Exchange daemon (transitional package)
 strongswan-ikev1 - strongSwan IKEv1 daemon, transitional package
 strongswan-ikev2 - strongSwan IKEv2 daemon, transitional package
 strongswan-libcharon - strongSwan charon library
 strongswan-nm - strongSwan plugin to interact with NetworkManager
 strongswan-pki - strongSwan IPsec client, pki command
 strongswan-scepclient - strongSwan IPsec client, SCEP client
 strongswan-starter - strongSwan daemon starter and configuration file parser
 strongswan-swanctl - strongSwan IPsec client, swanctl command
Closes: 866324 866325 866327 89 872155
Changes:
 strongswan (5.6.0-1) unstable; urgency=medium
 .
   * New upstream release.
 - fix insufficient input validation in gmp plugin, which can cause a
 denial of service vulnerability (CVE-2017-11185)closes: #872155
   * debian/rules:
 - remove .la files before install
 - don't call dh_install with --fail-missing
 - override dh_missing with --fail-missing to catch uninstalled files
 - apply patch from Gerald Turner to restrict permissions on swanctl folder
   containing private material.
 - replace DEB_BUILD_* by DEB_HOST_* when needed, fix FTCBFS, for example
   when building for ppc64el on x86. Thanks Helmut Grohne.   closes: #89
   * debian/strongswan-swanctl.install:
 - install the whole /etc/swanctl folder, including (empty) subfolders.
 close

Processed: libclang-perl is waiting for the llvm-defaults transition

[Debian Bug Tracking System]

Processing control commands:

> block 869602 by 869752
Bug #869602 [libclang-perl] libclang-perl: FTBFS on armel: clang-c/Index.h: No 
such file or directory
869602 was blocked by: 866354 873200
869602 was blocking: 866389
Added blocking bug(s) of 869602: 869752

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

Bug#869602: libclang-perl is waiting for the llvm-defaults transition

[Adrian Bunk]

Control: block 869602 by 869752

A give-back of libclang-perl requires either
- a #853523 FTBFS fix (might not to happen, see #873331), or
- the llvm-defaults transition (#869752).

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#864162: opendkim: systemd ExecStart ignore configuration options

[Scott Kitterman]

Once I have it fixed in unstable/testing, I plan to fix Stretch too.

Scott K

On September 3, 2017 3:31:25 AM EDT, "K. de Jong" 
 wrote:
>This bug affects also Debian stable (Stretch), is there any chance
>Debian
>will fix this? Or are these one of those things that won't be touched
>now
>Stretch is already released?
>
>
>--
>Kind regards,
>Kees de Jong  |  OpenPGP fingerprint: 0x0E45C98AB51428E6

Processed: Re: Bug#528058: patch

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #528058 [xfrisk] xfrisk: does not start: Can't find the font
Severity set to 'serious' from 'normal'
> tag -1 + pending
Bug #528058 [xfrisk] xfrisk: does not start: Can't find the font
Added tag(s) pending.

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

Bug#874125: octave-image FTBFS with octave-pkg-dev 1.5.0

[Adrian Bunk]

Source: octave-image
Version: 2.6.1-2
Severity: serious

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

...
Summary: 1169 tests, 1132 passed, 21 known failures, 0 skipped
/usr/share/cdbs/1/class/octave-pkg.mk:108: recipe for target 'check-pkg' failed
make: *** [check-pkg] Error 1

Bug#789927: Anthy library breakage

[Osamu Aoki]

Hi,

https://bugs.debian.org/873860#10

If what NOKUBI Takatsugu's comment is correct, I wonder why anthy is
upgraded without coordinating with key users:
 ibus
 uim
 fcitx

(Please note these have many dependence packages so the testing
migration is slow if package version dependency is correctly recorded.)

I agree moving to utf8 is right thing to do but this breakage is
something we should avoid.

If -dev package version is bumped, we can have slow migration without
breaking packages depending on old anthy.  But if we share the same -dev
package name, all related package needs to be uploaded together
(otherwise we suffer long broken sid system).

I know we tend to forget about it.  (I did this for ibus killing
ibus-mozc for few months alienating many uses).

But if library change its API spec from non-utf8 to utf8, this needs to
be coordinated carefully.

I haven't checked all the facts but it seems we should have bumped
package version and set conflict with -dev etc.

Just uploading new package may fix it in sid but this kind of api change
can't be detected by symbol file and probable break testing.  

It's not simple. What does people think is the right way to fix.

Osamu

Bug#874126: octave-financial FTBFS with octave-pkg-dev 1.5.0

[Adrian Bunk]

Source: octave-financial
Version: 0.5.0-1
Severity: serious
Tags: buster sid

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

...
Summary: 292 tests, 291 passed, 0 known failures, 0 skipped
/usr/share/cdbs/1/class/octave-pkg.mk:108: recipe for target 'check-pkg' failed
make: *** [check-pkg] Error 1

Processed: affects 873791

[Debian Bug Tracking System]

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

> affects 873791 + python-scipy
Bug #873791 {Done: Matthias Klose } [python2.7] python2.7: 
fpectl extension removal broke the ABI for C extensions
Added indication that 873791 affects python-scipy
> thanks
Stopping processing here.

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

Bug#873791: [python-numpy] Undefined symbols on several architectures

[Sébastien Villemot]

On Thu, 31 Aug 2017 12:48:53 +0200 Matthias Klose  wrote:

> yes, that's intended. I'll add a break.  Are there other known packages 
> besides
> python-numpy?

Looks like python-scipy is also affected:

$ python -c "from scipy import linalg"
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.7/dist-packages/scipy/linalg/__init__.py", line 175, 
in 
from .basic import *
  File "/usr/lib/python2.7/dist-packages/scipy/linalg/basic.py", line 21, in 

from ._solve_toeplitz import levinson
ImportError: 
/usr/lib/python2.7/dist-packages/scipy/linalg/_solve_toeplitz.x86_64-linux-gnu.so:
 undefined symbol: PyFPE_jbuf

(tested with python-scipy 0.18.1-2+b2)


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


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

Bug#874133: xfrisk: Always crashes due to "stack smashing" on pressing "Start game"

[Axel Beckert]

Package: xfrisk
Version: 1.2-4
Severity: grave

xfrisk (initially started via "risk") always crashes as follows for me
if I click the "Start game" button or if I later call "xfrisk localhost"
with the server already running. The following crash is from the latter
case:

~ → xfrisk localhost
CLIENT: Connected to server.
CLIENT: Waiting for server to send client ID...Done.
*** stack smashing detected ***: xfrisk terminated
=== Backtrace: =
/lib/x86_64-linux-gnu/libc.so.6(+0x70bfb)[0x7f35b3a6abfb]
/lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x37)[0x7f35b3af31e7]
/lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x0)[0x7f35b3af31b0]
xfrisk(+0x8652)[0x55ac99edc652]
xfrisk(+0x8aea)[0x55ac99edcaea]
xfrisk(+0x8dc6)[0x55ac99edcdc6]
/usr/lib/x86_64-linux-gnu/libXt.so.6(XtAppProcessEvent+0x17a)[0x7f35b452a58a]
/usr/lib/x86_64-linux-gnu/libXt.so.6(XtAppMainLoop+0x2d)[0x7f35b451edcd]
xfrisk(+0x5f4d)[0x55ac99ed9f4d]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7f35b3a1a2e1]
xfrisk(+0x5faa)[0x55ac99ed9faa]
=== Memory map: 
55ac99ed4000-55ac99ef6000 r-xp  fd:01 537517 
/usr/games/xfrisk
55ac9a0f6000-55ac9a0f8000 r--p 00022000 fd:01 537517 
/usr/games/xfrisk
55ac9a0f8000-55ac9a0fb000 rw-p 00024000 fd:01 537517 
/usr/games/xfrisk
55ac9a0fb000-55ac9a0fe000 rw-p  00:00 0 
55ac9bacf000-55ac9bb75000 rw-p  00:00 0  [heap]
7f35b1d2f000-7f35b1d45000 r-xp  fd:01 288120 
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f35b1d45000-7f35b1f44000 ---p 00016000 fd:01 288120 
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f35b1f44000-7f35b1f45000 r--p 00015000 fd:01 288120 
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f35b1f45000-7f35b1f46000 rw-p 00016000 fd:01 288120 
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f35b1f46000-7f35b1f4b000 r-xp  fd:01 529359 
/usr/lib/x86_64-linux-gnu/libXfixes.so.3.1.0
7f35b1f4b000-7f35b214a000 ---p 5000 fd:01 529359 
/usr/lib/x86_64-linux-gnu/libXfixes.so.3.1.0
7f35b214a000-7f35b214b000 r--p 4000 fd:01 529359 
/usr/lib/x86_64-linux-gnu/libXfixes.so.3.1.0
7f35b214b000-7f35b214c000 rw-p 5000 fd:01 529359 
/usr/lib/x86_64-linux-gnu/libXfixes.so.3.1.0
7f35b214c000-7f35b2155000 r-xp  fd:01 561244 
/usr/lib/x86_64-linux-gnu/libXrender.so.1.3.0
7f35b2155000-7f35b2354000 ---p 9000 fd:01 561244 
/usr/lib/x86_64-linux-gnu/libXrender.so.1.3.0
7f35b2354000-7f35b2355000 r--p 8000 fd:01 561244 
/usr/lib/x86_64-linux-gnu/libXrender.so.1.3.0
7f35b2355000-7f35b2356000 rw-p 9000 fd:01 561244 
/usr/lib/x86_64-linux-gnu/libXrender.so.1.3.0
7f35b2356000-7f35b235f000 r-xp  fd:01 524345 
/usr/lib/x86_64-linux-gnu/libXcursor.so.1.0.2
7f35b235f000-7f35b255f000 ---p 9000 fd:01 524345 
/usr/lib/x86_64-linux-gnu/libXcursor.so.1.0.2
7f35b255f000-7f35b256 r--p 9000 fd:01 524345 
/usr/lib/x86_64-linux-gnu/libXcursor.so.1.0.2
7f35b256-7f35b2561000 rw-p a000 fd:01 524345 
/usr/lib/x86_64-linux-gnu/libXcursor.so.1.0.2
7f35b2561000-7f35b256b000 r-xp  fd:01 264439 
/lib/x86_64-linux-gnu/libnss_files-2.24.so
7f35b256b000-7f35b276b000 ---p a000 fd:01 264439 
/lib/x86_64-linux-gnu/libnss_files-2.24.so
7f35b276b000-7f35b276c000 r--p a000 fd:01 264439 
/lib/x86_64-linux-gnu/libnss_files-2.24.so
7f35b276c000-7f35b276d000 rw-p b000 fd:01 264439 
/lib/x86_64-linux-gnu/libnss_files-2.24.so
7f35b276d000-7f35b2773000 rw-p  00:00 0 
7f35b2773000-7f35b2778000 r-xp  fd:01 529447 
/usr/lib/x86_64-linux-gnu/libXdmcp.so.6.0.0
7f35b2778000-7f35b2977000 ---p 5000 fd:01 529447 
/usr/lib/x86_64-linux-gnu/libXdmcp.so.6.0.0
7f35b2977000-7f35b2978000 r--p 4000 fd:01 529447 
/usr/lib/x86_64-linux-gnu/libXdmcp.so.6.0.0
7f35b2978000-7f35b2979000 rw-p 5000 fd:01 529447 
/usr/lib/x86_64-linux-gnu/libXdmcp.so.6.0.0
7f35b2979000-7f35b297b000 r-xp  fd:01 570496 
/usr/lib/x86_64-linux-gnu/libXau.so.6.0.0
7f35b297b000-7f35b2b7b000 ---p 2000 fd:01 570496 
/usr/lib/x86_64-linux-gnu/libXau.so.6.0.0
7f35b2b7b000-7f35b2b7c000 r--p 2000 fd:01 570496 
/usr/lib/x86_64-linux-gnu/libXau.so.6.0.0
7f35b2b7c000-7f35b2b7d000 rw-p 3000 fd:01 570496 
/usr/lib/x86_64-linux-gnu/libXau.so.6.0.0
7f35b2b7d000-7f35b2b84000 r-xp  fd:01 265865 
/lib/x86_64-linux-gnu/librt-2.24.so
7f35b2b84000-7f35b2d83000 ---p 7000 fd:01 265865 
/lib/x86_64-linux-gn

Bug#853353: conky: diff for NMU version 1.10.6-1.1

[Adrian Bunk]

Control: tags 853353 + pending

Dear maintainer,

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

cu
Adrian

-- 

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

diff -Nru conky-1.10.6/debian/changelog conky-1.10.6/debian/changelog
--- conky-1.10.6/debian/changelog	2016-12-09 09:46:09.0 +0200
+++ conky-1.10.6/debian/changelog	2017-09-03 18:12:29.0 +0300
@@ -1,3 +1,10 @@
+conky (1.10.6-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS with gcc 7. (Closes: #853353)
+
+ -- Adrian Bunk   Sun, 03 Sep 2017 18:12:29 +0300
+
 conky (1.10.6-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru conky-1.10.6/debian/patches/gcc-7.patch conky-1.10.6/debian/patches/gcc-7.patch
--- conky-1.10.6/debian/patches/gcc-7.patch	1970-01-01 02:00:00.0 +0200
+++ conky-1.10.6/debian/patches/gcc-7.patch	2017-08-19 20:59:53.0 +0300
@@ -0,0 +1,15 @@
+Description: src/luamm.hh: #include 
+ Required for building with gcc 7.
+Author: Adrian Bunk 
+Bug-Debian: https://bugs.debian.org/853353
+
+--- conky-1.10.6.orig/src/luamm.hh
 conky-1.10.6/src/luamm.hh
+@@ -26,6 +26,7 @@
+ #include 
+ #include 
+ #include 
++#include 
+ #include 
+ #include 
+ 
diff -Nru conky-1.10.6/debian/patches/series conky-1.10.6/debian/patches/series
--- conky-1.10.6/debian/patches/series	1970-01-01 02:00:00.0 +0200
+++ conky-1.10.6/debian/patches/series	2017-08-19 20:01:25.0 +0300
@@ -0,0 +1 @@
+gcc-7.patch

Bug#853571: marked as done (nfstrace: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Sun, 03 Sep 2017 15:26:02 +
with message-id 
and subject line Bug#853571: fixed in nfstrace 0.4.3.1-3
has caused the Debian Bug report #853571,
regarding nfstrace: 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.)


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

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

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

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

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

  apt-get -t=experimental install g++ 

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

[...]
make -j1
make[1]: Entering directory '/<>/obj-x86_64-linux-gnu'
/usr/bin/cmake -H/<> -B/<>/obj-x86_64-linux-gnu 
--check-build-system CMakeFiles/Makefile.cmake 0
/usr/bin/cmake -E cmake_progress_start 
/<>/obj-x86_64-linux-gnu/CMakeFiles 
/<>/obj-x86_64-linux-gnu/CMakeFiles/progress.marks
make -f CMakeFiles/Makefile2 all
make[2]: Entering directory '/<>/obj-x86_64-linux-gnu'
make -f CMakeFiles/nfstrace.dir/build.make CMakeFiles/nfstrace.dir/depend
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends 
"Unix Makefiles" /<> /<> 
/<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu 
/<>/obj-x86_64-linux-gnu/CMakeFiles/nfstrace.dir/DependInfo.cmake 
--color=
Scanning dependencies of target nfstrace
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make -f CMakeFiles/nfstrace.dir/build.make CMakeFiles/nfstrace.dir/build
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
[  1%] Building CXX object 
CMakeFiles/nfstrace.dir/src/analysis/analysis_manager.cpp.o
/usr/bin/c++-I/<>/src  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++14 -pedantic 
-Wall -Werror -Wextra -Wno-invalid-offsetof -Wno-braced-scalar-init -fPIC 
-fvisibility=hidden   -o 
CMakeFiles/nfstrace.dir/src/analysis/analysis_manager.cpp.o -c 
/<>/src/analysis/analysis_manager.cpp
[  2%] Building CXX object CMakeFiles/nfstrace.dir/src/analysis/analyzers.cpp.o
/usr/bin/c++-I/<>/src  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++14 -pedantic 
-Wall -Werror -Wextra -Wno-invalid-offsetof -Wno-braced-scalar-init -fPIC 
-fvisibility=hidden   -o CMakeFiles/nfstrace.dir/src/analysis/analyzers.cpp.o 
-c /<>/src/analysis/analyzers.cpp
[  4%] Building CXX object 
CMakeFiles/nfstrace.dir/src/analysis/cifs_parser.cpp.o
/usr/bin/c++-I/<>/src  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++14 -pedantic 
-Wall -Werror -Wextra -Wno-invalid-offsetof -Wno-braced-scalar-init -fPIC 
-fvisibility=hidden   -o CMakeFiles/nfstrace.dir/src/analysis/cifs_parser.cpp.o 
-c /<>/src/analysis/cifs_parser.cpp
[  5%] Building CXX object CMakeFiles/nfstrace.dir/src/analysis/nfs_parser.cpp.o
/usr/bin/c++-I/<>/src  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++14 -pedantic 
-Wall -Werror -Wextra -Wno-invalid-offsetof -Wno-braced-scalar-init -fPIC 
-fvisibility=hidden   -o CMakeFiles/nfstrace.dir/src/analysis/nfs_parser.cpp.o 
-c /<>/src/analysis/nfs_parser.cpp
/<>/src/analysis/nfs_parser.cpp: In function 'void 
NST::analysis::nfs4_ops_switch(NST::analysis::Analyzers&, const RPCProcedure*, 
const nfs_argop4*, const 

Processed: conky: diff for NMU version 1.10.6-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 853353 + pending
Bug #853353 [src:conky] conky: ftbfs with GCC-7
Added tag(s) pending.

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

Bug#853619: proposed fix

[Adrian Bunk]

ping

Thanks
Adrian


On Thu, Feb 09, 2017 at 08:20:06AM +0100, Ola Lundqvist wrote:
> Hi Kir
> 
> Thank you. I will test this.
> 
> // Ola
> 
> On 8 February 2017 at 23:38, Kir Kolyshkin  wrote:
> 
> > A fix has been committed to ploop repo:
> >
> > https://src.openvz.org/projects/OVZL/repos/ploop/commits/d42
> > 98fb98245be22ebe9f576e455c7bf9b26
> >
> > As gcc-7 is still experimental/unreleased, no new ploop release
> > is currently planned.

Bug#874135: octave-interval FTBFS on i386 with octave-pkg-dev 1.5.0

[Adrian Bunk]

Source: octave-interval
Version: 2.1.0-2
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/octave-interval.html

...
Summary: 1343 tests, 1341 passed, 0 known failures, 0 skipped
/usr/share/cdbs/1/class/octave-pkg.mk:108: recipe for target 'check-pkg' failed
make: *** [check-pkg] Error 1

Bug#874139: octave-signal FTBFS with octave-pkg-dev 1.5.0

[Adrian Bunk]

Source: octave-signal
Version: 1.3.2-1
Severity: serious
Tags: buster sid

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

...
Summary: 514 tests, 489 passed, 1 known failures, 0 skipped
/usr/share/cdbs/1/class/octave-pkg.mk:108: recipe for target 'check-pkg' failed
make: *** [check-pkg] Error 1

Bug#874141: octave-statistics FTBFS with octave-pkg-dev 1.5.0

[Adrian Bunk]

Source: octave-statistics
Version: 1.3.0-1
Severity: serious
Tags: buster sid

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

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

Bug#870171: Attributing the problem to NM after all

[Eduard Bloch]

Hallo,
* Michael Biebl [Sun, Aug 27 2017, 01:04:53PM]:
> > 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?

No. Actually, I have two APs here with different SSIDs but the same
password. One of them works fine, the other has the metioned problem.

> Can you change the WPA passphrase to something else (say only letters)
> and try again?

I did that and it worked. I reverted the change and then it works.

So the idea is then that something has corrupted the credentials store?
If so, why does it not drop the password from the store in case of
errors like this?

> Please also provide a full debug log from NetworkManager (and
> wpasupplicant) when the problem happens.
> https://wiki.gnome.org/Projects/NetworkManager/Debugging

Cannot do that right now. Luckily, I have a system backup and spare
hardware where it could be installed on... so I could try to reproduce
it if you want.

If you don't want, I think there should be some upstream fix which
deletes the credentials. The same way it does when the PSK has changed.

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

All Sid.

Best regards,
Eduard.

Bug#874138: octave-msh FTBFS with octave-pkg-dev 1.5.0

[Adrian Bunk]

Source: octave-msh
Version: 1.0.10-2
Severity: serious
Tags: buster sid

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

...
Summary: 32 tests, 29 passed, 0 known failures, 0 skipped
/usr/share/cdbs/1/class/octave-pkg.mk:108: recipe for target 'check-pkg' failed
make: *** [check-pkg] Error 1

Bug#874143: octave-odepkg FTBFS with octave-pkg-dev 1.5.0

[Adrian Bunk]

Source: octave-odepkg
Version: 0.8.5-2
Severity: serious

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

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

Bug#874136: Upgrading to libtorrent 1.1.0 or 1.1.1 can corrupt torrent filenames

[Etienne Dechamps]

Package: libtorrent-rasterbar9
Version: 1.1.1-1+b2
Severity: serious

Due to a bug in libtorrent 1.1.0 and 1.1.1, renaming a torrent (or, more
worryingly, loading a torrent that was renamed in the past) can result
in filename corruption, where subdirectories appear out of nowhere.

See: http://dev.deluge-torrent.org/ticket/2898

Because this bug also affects torrents that were added *before* the
upgrade, it can create a complete mess where pieces of torrents get
scattered everywhere. Recovering from such a "disaster" can be tricky
and time-consuming.

Please upload a fixed version of the package, either by cherry-picking
the fix (https://github.com/arvidn/libtorrent/pull/1524) or by upgrading
to libtorrent >=1.1.2.

Bug#874144: octave-control FTBFS on arm64/i386 with octave-pkg-dev 1.5.0

[Adrian Bunk]

Source: octave-control
Version: 3.0.0-2
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/arm64/octave-control.html

...
Summary: 328 tests, 313 passed, 0 known failures, 0 skipped
/usr/share/cdbs/1/class/octave-pkg.mk:108: recipe for target 'check-pkg' failed
make: *** [check-pkg] Error 1

Bug#874152: strongswan binary-all FTBFS: dh_missing: missing files, aborting

[Adrian Bunk]

Source: strongswan
Version: 5.6.0-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=strongswan&arch=all&ver=5.6.0-1&stamp=1504446045&raw=0

...
make[1]: Entering directory '/<>'
dh_missing --fail-missing
dh_missing: lib/systemd/system/strongswan.service exists in debian/tmp but is 
not installed to anywhere
dh_missing: etc/strongswan.d/charon/dhcp.conf exists in debian/tmp but is not 
installed to anywhere
dh_missing: etc/strongswan.d/charon/farp.conf exists in debian/tmp but is not 
installed to anywhere
dh_missing: etc/strongswan.d/charon/connmark.conf exists in debian/tmp but is 
not installed to anywhere
dh_missing: etc/strongswan.d/charon/kernel-netlink.conf exists in debian/tmp 
but is not installed to anywhere
dh_missing: etc/strongswan.d/charon/af-alg.conf exists in debian/tmp but is not 
installed to anywhere
dh_missing: etc/strongswan.d/charon/rdrand.conf exists in debian/tmp but is not 
installed to anywhere
dh_missing: etc/strongswan.d/charon/aesni.conf exists in debian/tmp but is not 
installed to anywhere
dh_missing: usr/share/strongswan/templates/config/plugins/dhcp.conf exists in 
debian/tmp but is not installed to anywhere
dh_missing: usr/share/strongswan/templates/config/plugins/farp.conf exists in 
debian/tmp but is not installed to anywhere
dh_missing: usr/share/strongswan/templates/config/plugins/connmark.conf exists 
in debian/tmp but is not installed to anywhere
dh_missing: usr/share/strongswan/templates/config/plugins/kernel-netlink.conf 
exists in debian/tmp but is not installed to anywhere
dh_missing: usr/share/strongswan/templates/config/plugins/af-alg.conf exists in 
debian/tmp but is not installed to anywhere
dh_missing: usr/share/strongswan/templates/config/plugins/rdrand.conf exists in 
debian/tmp but is not installed to anywhere
dh_missing: usr/share/strongswan/templates/config/plugins/aesni.conf exists in 
debian/tmp but is not installed to anywhere
dh_missing: usr/lib/ipsec/libvici.la exists in debian/tmp but is not installed 
to anywhere
dh_missing: usr/lib/ipsec/libtpmtss.la exists in debian/tmp but is not 
installed to anywhere
dh_missing: usr/lib/ipsec/libpttls.la exists in debian/tmp but is not installed 
to anywhere
dh_missing: usr/lib/ipsec/libtnccs.la exists in debian/tmp but is not installed 
to anywhere
dh_missing: usr/lib/ipsec/libradius.la exists in debian/tmp but is not 
installed to anywhere
dh_missing: usr/lib/ipsec/libtls.la exists in debian/tmp but is not installed 
to anywhere
dh_missing: usr/lib/ipsec/libsimaka.la exists in debian/tmp but is not 
installed to anywhere
dh_missing: usr/lib/ipsec/libstrongswan.la exists in debian/tmp but is not 
installed to anywhere
dh_missing: usr/lib/ipsec/plugins/libstrongswan-attr.la exists in debian/tmp 
but is not installed to anywhere
dh_missing: usr/lib/ipsec/plugins/libstrongswan-resolve.la exists in debian/tmp 
but is not installed to anywhere
dh_missing: usr/lib/ipsec/plugins/libstrongswan-xauth-pam.la exists in 
debian/tmp but is not installed to anywhere
dh_missing: usr/lib/ipsec/plugins/libstrongswan-xauth-eap.la exists in 
debian/tmp but is not installed to anywhere
dh_missing: usr/lib/ipsec/plugins/libstrongswan-xauth-generic.la exists in 
debian/tmp but is not installed to anywhere
dh_missing: usr/lib/ipsec/plugins/libstrongswan-unity.la exists in debian/tmp 
but is not installed to anywhere
dh_missing: usr/lib/ipsec/plugins/libstrongswan-addrblock.la exists in 
debian/tmp but is not installed to anywhere
dh_missing: usr/lib/ipsec/plugins/libstrongswan-led.la exists in debian/tmp but 
is not installed to anywhere
dh_missing: usr/lib/ipsec/plugins/libstrongswan-certexpire.la exists in 
debian/tmp but is not installed to anywhere
dh_missing: usr/lib/ipsec/plugins/libstrongswan-error-notify.la exists in 
debian/tmp but is not installed to anywhere
dh_missing: usr/lib/ipsec/plugins/libstrongswan-lookip.la exists in debian/tmp 
but is not installed to anywhere
dh_missing: usr/lib/ipsec/plugins/libstrongswan-kernel-netlink.la exists in 
debian/tmp but is not installed to anywhere
dh_missing: usr/lib/ipsec/plugins/libstrongswan-kernel-netlink.so exists in 
debian/tmp but is not installed to anywhere
dh_missing: usr/lib/ipsec/plugins/libstrongswan-ha.la exists in debian/tmp but 
is not installed to anywhere
dh_missing: usr/lib/ipsec/plugins/libstrongswan-dhcp.la exists in debian/tmp 
but is not installed to anywhere
dh_missing: usr/lib/ipsec/plugins/libstrongswan-dhcp.so exists in debian/tmp 
but is not installed to anywhere
dh_missing: usr/lib/ipsec/plugins/libstrongswan-eap-tnc.la exists in debian/tmp 
but is not installed to anywhere
dh_missing: usr/lib/ipsec/plugins/libstrongswan-eap-ttls.la exists in 
debian/tmp but is not installed to anywhere
dh_missing: usr/lib/ipsec/plugins/libstrongswan-eap-tls.la exists in debian/tmp 
but is not installed to anywhere
dh_missing: usr/lib/ipsec/plugins/libstrongswan-eap-radius.la exists in 
debian/tmp but is not installed to anywhere
dh_missing: usr/lib/

Processed: limit source to debian-archive-keyring, tagging 872525, tagging 870780

[Debian Bug Tracking System]

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

> limit source debian-archive-keyring
Limiting to bugs with field 'source' containing at least one of 
'debian-archive-keyring'
Limit currently set to 'source':'debian-archive-keyring'

> tags 872525 + pending
Bug #872525 [src:debian-archive-keyring] debian-archive-keyring FTBFS with 
gnupg 2.1.23
Added tag(s) pending.
> tags 870780 + pending
Bug #870780 [debian-archive-keyring] debian-archive-keyring: please remove 
trust packets from keyrings
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#874133: xfrisk: Always crashes due to "stack smashing" on pressing "Start game"

[Axel Beckert]

Hi,

Axel Beckert wrote:
> Package: xfrisk
> Version: 1.2-4
> Severity: grave
> 
> xfrisk (initially started via "risk") always crashes as follows for me
> if I click the "Start game" button or if I later call "xfrisk localhost"
> with the server already running.

Since upstream has a release candidate of a future release available,
I imported that one into the packaging and pushed the according
package changes to a git branch named "experimental", see
https://anonscm.debian.org/cgit/collab-maint/xfrisk.git/log/?h=experimental

Unfortunately that release candidate didn't fix this issue, so we very
likely need to find the cause for this crash and make up a patch to
fix it.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#872525: marked as done (debian-archive-keyring FTBFS with gnupg 2.1.23)

[Debian Bug Tracking System]

Your message dated Sun, 03 Sep 2017 17:34:52 +
with message-id 
and subject line Bug#872525: fixed in debian-archive-keyring 2017.6
has caused the Debian Bug report #872525,
regarding debian-archive-keyring FTBFS with gnupg 2.1.23
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.)


-- 
872525: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872525
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: debian-archive-keyring
Version: 2017.5
Severity: serious
Tags: buster sid

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

...
gpg --no-options --no-default-keyring --no-auto-check-trustdb --trustdb-name 
./trustdb.gpg \
--keyring keyrings/team-members.gpg --verify \
keyrings/debian-archive-keyring.gpg.asc \
keyrings/debian-archive-keyring.gpg
gpg: Signature made Thu May 25 06:30:03 2017 -12
gpg:using RSA key C5CE5DC2C542CD59
gpg: BAD signature from "Adam D. Barratt " [unknown]
Makefile:17: recipe for target 'verify-results' failed
make[1]: *** [verify-results] Error 1
make[1]: Leaving directory '/build/1st/debian-archive-keyring-2017.5'
dh_auto_build: make -j1 returned exit code 2
debian/rules:3: recipe for target 'build' failed
make: *** [build] Error 2


Works after downgrading gnupg to the buster version.

The Debian GnuPG Maintainers are Cc'ed, please reassign
if the bug turns out to be there.
--- End Message ---
--- Begin Message ---
Source: debian-archive-keyring
Source-Version: 2017.6

We believe that the bug you reported is fixed in the latest version of
debian-archive-keyring, 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.
Adam D. Barratt  (supplier of updated 
debian-archive-keyring package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 03 Sep 2017 17:52:14 +0100
Source: debian-archive-keyring
Binary: debian-archive-keyring debian-archive-keyring-udeb
Architecture: source
Version: 2017.6
Distribution: unstable
Urgency: medium
Maintainer: Debian Release Team 
Changed-By: Adam D. Barratt 
Description:
 debian-archive-keyring - GnuPG archive keys of the Debian archive
 debian-archive-keyring-udeb - GnuPG keys of the Debian archive (udeb)
Closes: 801381 870780 872525
Changes:
 debian-archive-keyring (2017.6) unstable; urgency=medium
 .
   * Remove dependencies between the .deb package and gnupg / gpgv.  apt has
 had relevant relationships of its own for some time now, so there's no
 need for us to do so.  (Closes: #801381)
   * Add Vcs-{Browser,Git} headers.
   * Remove trust packets from generated keyrings.  They're not required for
 the purpose of archive keyrings and may change between GnuPG versions,
 rendering the resulting keyrings unreproducible.
 (Closes: #872525, #870780)
Checksums-Sha1:
 0b9b55f0356460b7a6c829b6527ef46fdd347595 1788 debian-archive-keyring_2017.6.dsc
 a7a2e8ddf7016e04bfcd4ba856994960f9cb42cc 79560 
debian-archive-keyring_2017.6.tar.xz
 1629793715e6e62a2ceece2c7ee8adb622b41f5d 7111 
debian-archive-keyring_2017.6_amd64.buildinfo
Checksums-Sha256:
 366f7e854cc3686755e1988977fb276790beb581dd4bb2a0faac87a59ebef5b0 1788 
debian-archive-keyring_2017.6.dsc
 d5b3a7ad4030324489fa783235d3c5cd98e47ecb24e23533cb419cc696d6f7be 79560 
debian-archive-keyring_2017.6.tar.xz
 012cbfc4fb41ffa8722e8edeb4aabc03f0cc66b5846afd19e35c21648b9dcf07 7111 
debian-archive-keyring_2017.6_amd64.buildinfo
Files:
 14a473eb6d51ad87046f837248c48949 1788 misc important 
debian-archive-keyring_2017.6.dsc
 cc0c6f7cd7c9e879e7956f3c177faa4d 79560 misc important 
debian-archive-keyring_2017.6.tar.xz
 7b67dc83242a88bb877175b7a4cd1828 7111 misc important 
debian-archive-keyring_2017.6_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJMBAEBCAA3FiEEcgNjDiyOcnJRaE/rxc5dwsVCzVkFAlmsOikZHGFkYW1AYWRh
bS1iYXJyYXR0Lm9yZy51awAKCRDFzl3CxULNWYhPD/do4oluQtpOZv9ePk5fXFUP
WeLe5vHdWltRKiqf3WGfC2n4K2xQecgQxAhLYveTfFYvd43ORIK8AiYRO2ZRk7Py
BhY0sUJ0NJCF1NTs0Thq2MkELfdjarpscFuJNvKJm8VHgZaHTqpJD6KFhhE0Bs5K
HtIJvC3CvB8rEaQX0tkLYuUPWsKPMP5A01+y6xK0KtkrrIh4J0vLGRloygvhrPc

Bug#874133: xfrisk: Always crashes due to "stack smashing" on pressing "Start game"

[Adrian Bunk]

On Sun, Sep 03, 2017 at 07:11:23PM +0200, Axel Beckert wrote:
> Hi,
> 
> Axel Beckert wrote:
> > Package: xfrisk
> > Version: 1.2-4
> > Severity: grave
> > 
> > xfrisk (initially started via "risk") always crashes as follows for me
> > if I click the "Start game" button or if I later call "xfrisk localhost"
> > with the server already running.
> 
> Since upstream has a release candidate of a future release available,
> I imported that one into the packaging and pushed the according
> package changes to a git branch named "experimental", see
> https://anonscm.debian.org/cgit/collab-maint/xfrisk.git/log/?h=experimental
> 
> Unfortunately that release candidate didn't fix this issue, so we very
> likely need to find the cause for this crash and make up a patch to
> fix it.

Crashes for me with 1.2-4
Works for me with 1.2-3+b2

Looking at the build logs, the hardening flags
(especially -fstack-protector-strong) are new
in -4 and likely trigger the issue.

>   Regards, Axel

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#874152: marked as done (strongswan binary-all FTBFS: dh_missing: missing files, aborting)

[Debian Bug Tracking System]

Your message dated Sun, 03 Sep 2017 18:07:04 +
with message-id 
and subject line Bug#874152: fixed in strongswan 5.6.0-2
has caused the Debian Bug report #874152,
regarding strongswan binary-all FTBFS: dh_missing: missing files, aborting
to be marked as done.

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

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


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

https://buildd.debian.org/status/fetch.php?pkg=strongswan&arch=all&ver=5.6.0-1&stamp=1504446045&raw=0

...
make[1]: Entering directory '/<>'
dh_missing --fail-missing
dh_missing: lib/systemd/system/strongswan.service exists in debian/tmp but is 
not installed to anywhere
dh_missing: etc/strongswan.d/charon/dhcp.conf exists in debian/tmp but is not 
installed to anywhere
dh_missing: etc/strongswan.d/charon/farp.conf exists in debian/tmp but is not 
installed to anywhere
dh_missing: etc/strongswan.d/charon/connmark.conf exists in debian/tmp but is 
not installed to anywhere
dh_missing: etc/strongswan.d/charon/kernel-netlink.conf exists in debian/tmp 
but is not installed to anywhere
dh_missing: etc/strongswan.d/charon/af-alg.conf exists in debian/tmp but is not 
installed to anywhere
dh_missing: etc/strongswan.d/charon/rdrand.conf exists in debian/tmp but is not 
installed to anywhere
dh_missing: etc/strongswan.d/charon/aesni.conf exists in debian/tmp but is not 
installed to anywhere
dh_missing: usr/share/strongswan/templates/config/plugins/dhcp.conf exists in 
debian/tmp but is not installed to anywhere
dh_missing: usr/share/strongswan/templates/config/plugins/farp.conf exists in 
debian/tmp but is not installed to anywhere
dh_missing: usr/share/strongswan/templates/config/plugins/connmark.conf exists 
in debian/tmp but is not installed to anywhere
dh_missing: usr/share/strongswan/templates/config/plugins/kernel-netlink.conf 
exists in debian/tmp but is not installed to anywhere
dh_missing: usr/share/strongswan/templates/config/plugins/af-alg.conf exists in 
debian/tmp but is not installed to anywhere
dh_missing: usr/share/strongswan/templates/config/plugins/rdrand.conf exists in 
debian/tmp but is not installed to anywhere
dh_missing: usr/share/strongswan/templates/config/plugins/aesni.conf exists in 
debian/tmp but is not installed to anywhere
dh_missing: usr/lib/ipsec/libvici.la exists in debian/tmp but is not installed 
to anywhere
dh_missing: usr/lib/ipsec/libtpmtss.la exists in debian/tmp but is not 
installed to anywhere
dh_missing: usr/lib/ipsec/libpttls.la exists in debian/tmp but is not installed 
to anywhere
dh_missing: usr/lib/ipsec/libtnccs.la exists in debian/tmp but is not installed 
to anywhere
dh_missing: usr/lib/ipsec/libradius.la exists in debian/tmp but is not 
installed to anywhere
dh_missing: usr/lib/ipsec/libtls.la exists in debian/tmp but is not installed 
to anywhere
dh_missing: usr/lib/ipsec/libsimaka.la exists in debian/tmp but is not 
installed to anywhere
dh_missing: usr/lib/ipsec/libstrongswan.la exists in debian/tmp but is not 
installed to anywhere
dh_missing: usr/lib/ipsec/plugins/libstrongswan-attr.la exists in debian/tmp 
but is not installed to anywhere
dh_missing: usr/lib/ipsec/plugins/libstrongswan-resolve.la exists in debian/tmp 
but is not installed to anywhere
dh_missing: usr/lib/ipsec/plugins/libstrongswan-xauth-pam.la exists in 
debian/tmp but is not installed to anywhere
dh_missing: usr/lib/ipsec/plugins/libstrongswan-xauth-eap.la exists in 
debian/tmp but is not installed to anywhere
dh_missing: usr/lib/ipsec/plugins/libstrongswan-xauth-generic.la exists in 
debian/tmp but is not installed to anywhere
dh_missing: usr/lib/ipsec/plugins/libstrongswan-unity.la exists in debian/tmp 
but is not installed to anywhere
dh_missing: usr/lib/ipsec/plugins/libstrongswan-addrblock.la exists in 
debian/tmp but is not installed to anywhere
dh_missing: usr/lib/ipsec/plugins/libstrongswan-led.la exists in debian/tmp but 
is not installed to anywhere
dh_missing: usr/lib/ipsec/plugins/libstrongswan-certexpire.la exists in 
debian/tmp but is not installed to anywhere
dh_missing: usr/lib/ipsec/plugins/libstrongswan-error-notify.la exists in 
debian/tmp but is not installed to anywhere
dh_missing: usr/lib/ipsec/plugins/libstrongswan-lookip.la exists in debian/tmp 
but is not installed to anywhere
dh_missing: usr/lib/ipsec/plugins/libstrongswan-kernel-netlink.la exists in 
debian/tmp but is not installed to anywhere
dh_missing: usr/lib/ipsec/plugins/libstrongswan-kernel-netlink.so exists in 
debian/tmp but is not i

Bug#874133: xfrisk: Always crashes due to "stack smashing" on pressing "Start game"

[Axel Beckert]

Hi Adrian,

Adrian Bunk wrote:
> Crashes for me with 1.2-4
> Works for me with 1.2-3+b2
> 
> Looking at the build logs, the hardening flags
> (especially -fstack-protector-strong) are new
> in -4 and likely trigger the issue.

Thanks for that hint! Didn't notice it when uploading 1.2-4. Probably
didn't test far enough.

Will likely upload a 1.2-5 with the fix soon.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#874165: libvdpau FTBFS: configure: error: Documentation enabled but doxygen was not found in your path

[Adrian Bunk]

Source: libvdpau
Version: 1.1.1-7
Severity: serious

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

...
checking for library containing pthread_once... -lpthread
checking for doxygen... no
checking for dot... no
configure: error: Documentation enabled but doxygen was not found in your path

Bug#874136: marked as done (Upgrading to libtorrent 1.1.0 or 1.1.1 can corrupt torrent filenames)

[Debian Bug Tracking System]

Your message dated Sun, 03 Sep 2017 18:39:01 +
with message-id 
and subject line Bug#874136: fixed in libtorrent-rasterbar 1.1.4-1
has caused the Debian Bug report #874136,
regarding Upgrading to libtorrent 1.1.0 or 1.1.1 can corrupt torrent filenames
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.)


-- 
874136: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874136
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libtorrent-rasterbar9
Version: 1.1.1-1+b2
Severity: serious

Due to a bug in libtorrent 1.1.0 and 1.1.1, renaming a torrent (or, more
worryingly, loading a torrent that was renamed in the past) can result
in filename corruption, where subdirectories appear out of nowhere.

See: http://dev.deluge-torrent.org/ticket/2898

Because this bug also affects torrents that were added *before* the
upgrade, it can create a complete mess where pieces of torrents get
scattered everywhere. Recovering from such a "disaster" can be tricky
and time-consuming.

Please upload a fixed version of the package, either by cherry-picking
the fix (https://github.com/arvidn/libtorrent/pull/1524) or by upgrading
to libtorrent >=1.1.2.
--- End Message ---
--- Begin Message ---
Source: libtorrent-rasterbar
Source-Version: 1.1.4-1

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

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

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

Debian distribution maintenance software
pp.
Andrew Starr-Bochicchio  (supplier of updated 
libtorrent-rasterbar package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 03 Sep 2017 13:28:04 -0400
Source: libtorrent-rasterbar
Binary: libtorrent-rasterbar9 libtorrent-rasterbar-dev libtorrent-rasterbar-dbg 
libtorrent-rasterbar-doc python-libtorrent python-libtorrent-dbg 
python3-libtorrent python3-libtorrent-dbg
Architecture: source amd64 all
Version: 1.1.4-1
Distribution: unstable
Urgency: medium
Maintainer: Cristian Greco 
Changed-By: Andrew Starr-Bochicchio 
Description:
 libtorrent-rasterbar-dbg - Debug symbols for libtorrent-rasterbar
 libtorrent-rasterbar-dev - Development files for libtorrent-rasterbar
 libtorrent-rasterbar-doc - Documentation for libtorrent-rasterbar
 libtorrent-rasterbar9 - C++ bittorrent library by Rasterbar Software
 python-libtorrent - Python bindings for libtorrent-rasterbar
 python-libtorrent-dbg - Python bindings for libtorrent-rasterbar (debug 
symbols)
 python3-libtorrent - Python bindings for libtorrent-rasterbar (Python 3)
 python3-libtorrent-dbg - Python bindings for libtorrent-rasterbar (debug 
symbols) (Python
Closes: 842538 857239 874136
Changes:
 libtorrent-rasterbar (1.1.4-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #857239).
- Fix file rename issue with name prefix matching
  torrent name (Closes: #874136).
- Fix ABI compatibility issue introduced with
  preformatted entry type (Closes: #842538).
   * debian/libtorrent-rasterbar-doc.install:
- Adjust for new release.
   * debian/control:
- All priority 'extra' packages are now 'optional.'
- Bump Standards-Version to 4.1.0.
- Drop un-needed build dep on dh-autoreconf.
Checksums-Sha1:
 30eb0ea506286ee13ea86326db41a0fc0d50751a 2817 libtorrent-rasterbar_1.1.4-1.dsc
 7bda02cd0dd936afd798d35bf2d3ab83c0d094dc 3917557 
libtorrent-rasterbar_1.1.4.orig.tar.gz
 b4b5891214b83954a567ab29fb133bc6f86448f5 16092 
libtorrent-rasterbar_1.1.4-1.debian.tar.xz
 b2e6c714571ef2c783a3bb223067b99ae1450aeb 63466548 
libtorrent-rasterbar-dbg_1.1.4-1_amd64.deb
 ce713126ca47fb783f5c413b95c41b7b0f4108d0 2135922 
libtorrent-rasterbar-dev_1.1.4-1_amd64.deb
 4ba2c8ba7aaa26ad543870b6132e24cc9e5f5ece 1546748 
libtorrent-rasterbar-doc_1.1.4-1_all.deb
 f48fa84e1b11f3b5bb352c9564ce04416c3a7306 1250900 
libtorrent-rasterbar9_1.1.4-1_amd64.deb
 928d0183d86393cc23d7880bd54a1dadc37e61d2 9411 
libtorrent-rasterbar_1.1.4-1_amd64.buildinfo
 6d7d4f3829fbf967a2c3a1d94b97f33369525b15 346252 
python-libtorrent-dbg_1.1.4-1_amd64.deb
 cb0f03b2c9a3aed1e8ccbc2415793ff88e174242 323044 
python-libtorrent_1.1.4-1_amd64.deb
 ef80272f8b5f388b2e892

Bug#874165: libvdpau FTBFS: configure: error: Documentation enabled but doxygen was not found in your path

[Luca Boccassi]

On September 3, 2017 7:15:04 PM GMT+01:00, Adrian Bunk  wrote:
>Source: libvdpau
>Version: 1.1.1-7
>Severity: serious
>
>https://buildd.debian.org/status/package.php?p=libvdpau&suite=sid
>
>...
>checking for library containing pthread_once... -lpthread
>checking for doxygen... no
>checking for dot... no
>configure: error: Documentation enabled but doxygen was not found in
>your path

Hi,

Yes, I did a boo-boo :-P
I failed to see the problem when testing with pbuilder, but I've already pushed 
a fix some minutes ago, hopefully it's good this time.

Kind regards,
Luca Boccassi


signature.asc
Description: PGP signature

Bug#871338: marked as done (xfdesktop4: FTBFS: unsatisfiable build-dependency: libgarcon-1-0-dev (>= 0.2.0) (versioned dep on a virtual pkg?))

[Debian Bug Tracking System]

Your message dated Sun, 03 Sep 2017 18:49:32 +
with message-id 
and subject line Bug#868626: fixed in garcon 0.6.1-2
has caused the Debian Bug report #868626,
regarding xfdesktop4: FTBFS: unsatisfiable build-dependency: libgarcon-1-0-dev 
(>= 0.2.0) (versioned dep on a virtual pkg?)
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.)


-- 
868626: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868626
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xfdesktop4
Version: 4.12.3-4
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170807 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), libglib2.0-dev, libgtk2.0-dev, 
> libxfce4util-dev (>= 4.10.0), libxfce4ui-1-dev (>= 4.11.1), libwnck-dev, 
> libxfconf-0-dev (>= 4.10.0), intltool, libdbus-glib-1-dev (>= 0.84), 
> libthunarx-2-dev (>= 1.4.0), libexo-1-dev (>= 0.7.0), libgarcon-1-0-dev (>= 
> 0.2.0), libnotify-dev (>= 0.4.0), dpkg-dev (>= 1.16.1)
> Filtered Build-Depends: debhelper (>= 9), libglib2.0-dev, libgtk2.0-dev, 
> libxfce4util-dev (>= 4.10.0), libxfce4ui-1-dev (>= 4.11.1), libwnck-dev, 
> libxfconf-0-dev (>= 4.10.0), intltool, libdbus-glib-1-dev (>= 0.84), 
> libthunarx-2-dev (>= 1.4.0), libexo-1-dev (>= 0.7.0), libgarcon-1-0-dev (>= 
> 0.2.0), libnotify-dev (>= 0.4.0), dpkg-dev (>= 1.16.1)
> dpkg-deb: building package 'sbuild-build-depends-xfdesktop4-dummy' in 
> '/<>/resolver-AM8rqF/apt_archive/sbuild-build-depends-xfdesktop4-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy 
> sbuild-build-depends-xfdesktop4-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-AM8rqF/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-AM8rqF/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-AM8rqF/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-AM8rqF/apt_archive ./ Sources [607 B]
> Get:5 copy:/<>/resolver-AM8rqF/apt_archive ./ Packages [691 B]
> Fetched 2261 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install xfdesktop4 build dependencies (apt-based resolver)
> --
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-xfdesktop4-dummy : Depends: libgarcon-1-0-dev (>= 0.2.0)
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2017/08/07/xfdesktop4_4.12.3-4_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Yves-Alexis Perez  (supplier of updated garcon 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-m

Bug#871368: marked as done (xfce4-xkb-plugin: FTBFS: unsatisfiable build-dependency: libgarcon-1-0-dev (>= 0.1.5) (versioned dep on a virtual pkg?))

[Debian Bug Tracking System]

Your message dated Sun, 03 Sep 2017 18:49:32 +
with message-id 
and subject line Bug#868626: fixed in garcon 0.6.1-2
has caused the Debian Bug report #868626,
regarding xfce4-xkb-plugin: FTBFS: unsatisfiable build-dependency: 
libgarcon-1-0-dev (>= 0.1.5) (versioned dep on a virtual pkg?)
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.)


-- 
868626: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868626
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xfce4-xkb-plugin
Version: 1:0.7.1-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170807 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), libgtk2.0-dev, dpkg-dev (>= 1.16.1), 
> libxfce4ui-1-dev (>= 4.8.0), xfce4-panel-dev (>= 4.8.0), libxml-parser-perl, 
> libxklavier-dev (>= 5.0), librsvg2-dev, libwnck-dev, intltool, 
> libgarcon-1-0-dev (>= 0.1.5)
> Filtered Build-Depends: debhelper (>= 9), libgtk2.0-dev, dpkg-dev (>= 
> 1.16.1), libxfce4ui-1-dev (>= 4.8.0), xfce4-panel-dev (>= 4.8.0), 
> libxml-parser-perl, libxklavier-dev (>= 5.0), librsvg2-dev, libwnck-dev, 
> intltool, libgarcon-1-0-dev (>= 0.1.5)
> dpkg-deb: building package 'sbuild-build-depends-xfce4-xkb-plugin-dummy' in 
> '/<>/resolver-NBnVvj/apt_archive/sbuild-build-depends-xfce4-xkb-plugin-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy 
> sbuild-build-depends-xfce4-xkb-plugin-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-NBnVvj/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-NBnVvj/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-NBnVvj/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-NBnVvj/apt_archive ./ Sources [594 B]
> Get:5 copy:/<>/resolver-NBnVvj/apt_archive ./ Packages [675 B]
> Fetched 2232 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install xfce4-xkb-plugin build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-xfce4-xkb-plugin-dummy : Depends: libgarcon-1-0-dev (>= 
> 0.1.5)
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2017/08/07/xfce4-xkb-plugin_0.7.1-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: garcon
Source-Version: 0.6.1-2

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

Debian distribution maintenance software
pp.
Yves-Alexis Perez  (supplier of updated garcon package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 03 Sep 2017 19:14:03 +0200
Source: garcon
Binary: lib

Bug#868626: marked as done (libgarcon-1-0-dev is not installable)

[Debian Bug Tracking System]

Your message dated Sun, 03 Sep 2017 18:49:32 +
with message-id 
and subject line Bug#868626: fixed in garcon 0.6.1-2
has caused the Debian Bug report #868626,
regarding libgarcon-1-0-dev is not installable
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.)


-- 
868626: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868626
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgarcon-1-0-dev
Version: 0.6.1-1
Severity: serious

Package: libgarcon-1-0-dev
Version: 0.6.1-1
Depends: libgarcon-1-dev

Package: libgarcon-1-dev
Version: 0.6.1-1
Breaks: libgarcon-1-0-dev
--- End Message ---
--- Begin Message ---
Source: garcon
Source-Version: 0.6.1-2

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

Debian distribution maintenance software
pp.
Yves-Alexis Perez  (supplier of updated garcon package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 03 Sep 2017 19:14:03 +0200
Source: garcon
Binary: libgarcon-1-dev libgarcon-1-0-dev libgarcon-gtk3-1-dev libgarcon-1-0 
libgarcon-gtk3-1-0 libgarcon-common
Architecture: source
Version: 0.6.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Yves-Alexis Perez 
Description:
 libgarcon-1-0 - freedesktop.org compliant menu implementation for Xfce
 libgarcon-1-0-dev - transitional package for libgarcon-1-dev
 libgarcon-1-dev - Development files for garcon-1
 libgarcon-common - common files for libgarcon menu implementation
 libgarcon-gtk3-1-0 - menu library for Xfce (GTK3 library)
 libgarcon-gtk3-1-dev - Development files for garcon-gtk3
Closes: 868626
Changes:
 garcon (0.6.1-2) unstable; urgency=medium
 .
   [ Unit 193 ]
   * d/control:
 - Add versioned breaks/replaces on libgarcon-1-0-dev.   closes: #868626
Checksums-Sha1:
 239f4da543733a6095acbc3200e524510ac451e2 2148 garcon_0.6.1-2.dsc
 2e74df4774913c14acbc12e02e8ba8a30f7853f1 4688 garcon_0.6.1-2.debian.tar.xz
 429c7ff615103de169be2976709b9100621f2a34 15859 garcon_0.6.1-2_amd64.buildinfo
Checksums-Sha256:
 4892723d8ea90fa4917f102fb2f735689658487155bba516ed3b72c826e82f30 2148 
garcon_0.6.1-2.dsc
 72fe767d95d709f6c7728ae12789bb28c98559567bd1594489a8d8c999a2b846 4688 
garcon_0.6.1-2.debian.tar.xz
 8b012750ebc423141e0574b2205d7aa9bcb5b44c81266305cf2acb7532b63332 15859 
garcon_0.6.1-2_amd64.buildinfo
Files:
 6fcdb711c2452b76970c6084f54b5efb 2148 xfce optional garcon_0.6.1-2.dsc
 c7cd447af5ef29879eec81c55d995aa1 4688 xfce optional 
garcon_0.6.1-2.debian.tar.xz
 dca66597c987e9138950ea5dc87caa51 15859 xfce optional 
garcon_0.6.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEl0WwInMjgf6efq/1bdtT8qZ1wKUFAlmsSpsACgkQbdtT8qZ1
wKUNfQf+Kv4E6InGhyHKbpMFOlxw/3RT0cnrHhkT/O4dHnKvWeQBpJxDQSY+uum3
CYL5yEsx5I/nvNlaLXCqpGxdPFOXiRZQEhwleFH3xIyidOv2CEeSV9dzw1qAAIAX
94+xk5UxjqKhSIWMQj1tGcDse/VKCnyR35b0g/DM/hM6v1oiiWd/Pbahlibpb5iU
chmSfqgLOxjr7kwl0oofrXqwGrskDc13zPIQizNOM3p9icrFFAuP6NFv380Qc7vg
y4OO+Xn9ltdwoVCIFMnMEXQItQRroKfdwXvwLiy/y7e4gyQ+ZQn9f5tH4bmuJ3XO
UQZe0P/qNM+mp/d4pcCgYkK3qCBNLQ==
=0lCm
-END PGP SIGNATURE End Message ---

Bug#871329: marked as done (xfce4-settings: FTBFS: unsatisfiable build-dependency: libgarcon-1-0-dev (>= 0.2.0) (versioned dep on a virtual pkg?))

[Debian Bug Tracking System]

Your message dated Sun, 03 Sep 2017 18:49:32 +
with message-id 
and subject line Bug#868626: fixed in garcon 0.6.1-2
has caused the Debian Bug report #868626,
regarding xfce4-settings: FTBFS: unsatisfiable build-dependency: 
libgarcon-1-0-dev (>= 0.2.0) (versioned dep on a virtual pkg?)
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.)


-- 
868626: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868626
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xfce4-settings
Version: 4.12.1-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170807 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), dpkg-dev (>= 1.16.1), 
> libxfce4util-dev (>= 4.10.0), libxfce4ui-1-dev (>= 4.11.0), libexo-1-dev (>= 
> 0.8.0), libxfconf-0-dev (>= 4.10.0), libwnck-dev, libxklavier-dev (>= 5.0), 
> libnotify-dev, intltool (>= 0.31), libgarcon-1-0-dev (>= 0.2.0), 
> libupower-glib-dev (>= 0.99)
> Merged Build-Conflicts: libxfcegui4-dev (<< 4.7.0)
> Filtered Build-Depends: debhelper (>= 9), dpkg-dev (>= 1.16.1), 
> libxfce4util-dev (>= 4.10.0), libxfce4ui-1-dev (>= 4.11.0), libexo-1-dev (>= 
> 0.8.0), libxfconf-0-dev (>= 4.10.0), libwnck-dev, libxklavier-dev (>= 5.0), 
> libnotify-dev, intltool (>= 0.31), libgarcon-1-0-dev (>= 0.2.0), 
> libupower-glib-dev (>= 0.99)
> Filtered Build-Conflicts: libxfcegui4-dev (<< 4.7.0)
> dpkg-deb: building package 'sbuild-build-depends-xfce4-settings-dummy' in 
> '/<>/resolver-tYzxzU/apt_archive/sbuild-build-depends-xfce4-settings-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy 
> sbuild-build-depends-xfce4-settings-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-tYzxzU/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-tYzxzU/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-tYzxzU/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-tYzxzU/apt_archive ./ Sources [619 B]
> Get:5 copy:/<>/resolver-tYzxzU/apt_archive ./ Packages [704 B]
> Fetched 2286 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install xfce4-settings build dependencies (apt-based resolver)
> --
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-xfce4-settings-dummy : Depends: libgarcon-1-0-dev (>= 
> 0.2.0)
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2017/08/07/xfce4-settings_4.12.1-1_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Yves-Alexis Perez  (supplier of updated garcon package)

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

Bug#871356: marked as done (xfce4-panel: FTBFS: unsatisfiable build-dependency: libgarcon-1-0-dev (>= 0.3.0) (versioned dep on a virtual pkg?))

[Debian Bug Tracking System]

Your message dated Sun, 03 Sep 2017 18:49:32 +
with message-id 
and subject line Bug#868626: fixed in garcon 0.6.1-2
has caused the Debian Bug report #868626,
regarding xfce4-panel: FTBFS: unsatisfiable build-dependency: libgarcon-1-0-dev 
(>= 0.3.0) (versioned dep on a virtual pkg?)
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.)


-- 
868626: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868626
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xfce4-panel
Version: 4.12.1-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170807 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), libxfce4util-dev (>= 4.10.0), 
> libgarcon-1-0-dev (>= 0.3.0), libxfce4ui-1-dev (>= 4.11.0), libxfconf-0-dev 
> (>= 4.10.0), libexo-1-dev (>= 0.8.0), libgtk2.0-dev (>= 2.14.0), 
> libglib2.0-dev (>= 2.18.0), libdbus-glib-1-dev (>= 0.73), libcairo2-dev (>= 
> 1.0.0), libwnck-dev (>= 2.22), libxml-parser-perl, intltool, libgtk-3-dev
> Filtered Build-Depends: debhelper (>= 9), libxfce4util-dev (>= 4.10.0), 
> libgarcon-1-0-dev (>= 0.3.0), libxfce4ui-1-dev (>= 4.11.0), libxfconf-0-dev 
> (>= 4.10.0), libexo-1-dev (>= 0.8.0), libgtk2.0-dev (>= 2.14.0), 
> libglib2.0-dev (>= 2.18.0), libdbus-glib-1-dev (>= 0.73), libcairo2-dev (>= 
> 1.0.0), libwnck-dev (>= 2.22), libxml-parser-perl, intltool, libgtk-3-dev
> dpkg-deb: building package 'sbuild-build-depends-xfce4-panel-dummy' in 
> '/<>/resolver-U7QUon/apt_archive/sbuild-build-depends-xfce4-panel-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy 
> sbuild-build-depends-xfce4-panel-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-U7QUon/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-U7QUon/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-U7QUon/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-U7QUon/apt_archive ./ Sources [608 B]
> Get:5 copy:/<>/resolver-U7QUon/apt_archive ./ Packages [691 B]
> Fetched 2262 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install xfce4-panel build dependencies (apt-based resolver)
> ---
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-xfce4-panel-dummy : Depends: libgarcon-1-0-dev (>= 
> 0.3.0)
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2017/08/07/xfce4-panel_4.12.1-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: garcon
Source-Version: 0.6.1-2

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

Debian distribution maintenance software
pp.
Yves-Alexis Perez  (supplier of updated garcon package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the arc

Bug#871374: marked as done (xfce4-appfinder: FTBFS: unsatisfiable build-dependency: libgarcon-1-0-dev (>= 0.3.0) (versioned dep on a virtual pkg?))

[Debian Bug Tracking System]

Your message dated Sun, 03 Sep 2017 18:49:32 +
with message-id 
and subject line Bug#868626: fixed in garcon 0.6.1-2
has caused the Debian Bug report #868626,
regarding xfce4-appfinder: FTBFS: unsatisfiable build-dependency: 
libgarcon-1-0-dev (>= 0.3.0) (versioned dep on a virtual pkg?)
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.)


-- 
868626: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868626
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xfce4-appfinder
Version: 4.12.0-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170807 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), libxfce4util-dev (>= 4.10.0), 
> libxfce4ui-1-dev (>= 4.10.0), libxft-dev, libxml-parser-perl, libgtk2.0-dev, 
> libxfconf-0-dev (>= 4.10.0), libgarcon-1-0-dev (>= 0.3.0), intltool, dpkg-dev 
> (>= 1.16.1), libglib2.0-dev
> Filtered Build-Depends: debhelper (>= 9), libxfce4util-dev (>= 4.10.0), 
> libxfce4ui-1-dev (>= 4.10.0), libxft-dev, libxml-parser-perl, libgtk2.0-dev, 
> libxfconf-0-dev (>= 4.10.0), libgarcon-1-0-dev (>= 0.3.0), intltool, dpkg-dev 
> (>= 1.16.1), libglib2.0-dev
> dpkg-deb: building package 'sbuild-build-depends-xfce4-appfinder-dummy' in 
> '/<>/resolver-zKCFNp/apt_archive/sbuild-build-depends-xfce4-appfinder-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy 
> sbuild-build-depends-xfce4-appfinder-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-zKCFNp/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-zKCFNp/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-zKCFNp/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-zKCFNp/apt_archive ./ Sources [579 B]
> Get:5 copy:/<>/resolver-zKCFNp/apt_archive ./ Packages [659 B]
> Fetched 2201 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install xfce4-appfinder build dependencies (apt-based resolver)
> ---
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-xfce4-appfinder-dummy : Depends: libgarcon-1-0-dev (>= 
> 0.3.0)
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2017/08/07/xfce4-appfinder_4.12.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: garcon
Source-Version: 0.6.1-2

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

Debian distribution maintenance software
pp.
Yves-Alexis Perez  (supplier of updated garcon package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 03 Sep 2017 19:14:03 +0200
Source: garcon
Binary

Bug#874167: gcc-6-doc: source uploaded without binaries, caused package removal

[Mattia Rizzolo]

Source: gcc-6-doc
Severity: serious
Version: 6.4.0-1
X-Debbugs-Cc: culu@gmail.com, kilob...@angband.pl, dktrkr...@debian.org

Hi!

gcc-6-doc is a non-free package, therefore wanna-build doesn't attempt
its build automatically.  Also, it is not manually whitelisted (it's
also missing the XS-Autobuild header).
Nonetheless you uploaded it source-only, without binaries; due to it,
dak considered the binaries as not built anymore, and ended up in the
cruft report.  From there an overzealous ftp-master removed it :)

Date: Wed, 30 Aug 2017 12:29:23 +
Ftpmaster: Luca Falavigna
Suite: unstable
Binaries:
 gcc-6-doc_6.3.0-1 [all]
Reason: [auto-cruft] no longer built from source

Date: Wed, 30 Aug 2017 12:27:15 +
Ftpmaster: Luca Falavigna
Suite: unstable
Sources:
 gcc-6-doc_6.4.0-1
Reason: [auto-cruft] obsolete source package


Please upload the package again (which will end up in NEW), and remember
to either always upload the binaries, or to ask to enable autobuilding.


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

Processed: closing 856600

[Debian Bug Tracking System]

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

> close 856599 1.1.4-1
Bug #856599 {Done: Andreas Beckmann } [libktpcommoninternals9] 
libktpcommoninternals9: please add Breaks: libktpcommoninternalsprivate7
There is no source info for the package 'libktpcommoninternals9' at version 
'1.1.4-1' with architecture ''
Unable to make a source version for version '1.1.4-1'
Marked as fixed in versions 1.1.4-1.
Bug #856599 {Done: Andreas Beckmann } [libktpcommoninternals9] 
libktpcommoninternals9: please add Breaks: libktpcommoninternalsprivate7
Bug 856599 is already marked as done; not doing anything.
> thanks
Stopping processing here.

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

Processed: libappstreamqt-dev: AppStreamQtConfig.cmake hardcodes a 64bit behaviour

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:frameworkintegration
Bug #874170 [libappstreamqt-dev] libappstreamqt-dev: AppStreamQtConfig.cmake 
hardcodes a 64bit behaviour
Added indication that 874170 affects src:frameworkintegration
> affects -1 src:plasma-discover
Bug #874170 [libappstreamqt-dev] libappstreamqt-dev: AppStreamQtConfig.cmake 
hardcodes a 64bit behaviour
Added indication that 874170 affects src:plasma-discover

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

Bug#874170: libappstreamqt-dev: AppStreamQtConfig.cmake hardcodes a 64bit behaviour

[Pino Toscano]

Package: libappstreamqt-dev
Version: 0.11.4-1
Severity: grave
Justification: renders package unusable
Control: affects -1 src:frameworkintegration
Control: affects -1 src:plasma-discover

Hi,

in the new version 0.11.4, I guess because of the switch from cmake to
meson, the source got a template for the AppStreamQtConfig.cmake file.
This template was created from an existing file on a 64bit system, so
the final AppStreamQtConfig.cmake file is rejected by cmake when found
by packages via cmake on 32bit architectures.

Two examples are frameworkintergration, and plasma-discover:
https://buildd.debian.org/status/logs.php?pkg=frameworkintegration&ver=5.37.0-2
https://buildd.debian.org/status/logs.php?pkg=plasma-discover&ver=5.10.5-1
In particular:

<
CMake Warning at CMakeLists.txt:44 (find_package):
  Could not find a configuration file for package "AppStreamQt" that is
  compatible with requested version "0.10.4".

  The following configuration files were considered but not accepted:

/usr/lib/i386-linux-gnu/cmake/AppStreamQt/AppStreamQtConfig.cmake, version: 
0.11.4 (64bit)
<

The severity is grave because this is an issue in the upstream sources,
and because it's a regression compared to the previous version (and thus
ought to not migrate to testing).

-- 
Pino

Bug#874169: AppStreamQtConfig.cmake no longer usable in i386

[Maximiliano Curia]

Source: appstream
Version: 0.11.4-1
Severity: critical

The latest appstream release migrates the build system to meson, but builds a 
cmake file for compatibility, so far so good. Sadly, the logic to 
detect if the build was for 32 bits or for 64 bits seems to be incorrect, 
which makes software that build depends on libappstreamqt-dev to ftbfs [1].


I looked at the code but couldn't find the root of the issue. The end of the generated 
file (/usr/lib/i386-linux-gnu/cmake/AppStreamQt/AppStreamQtConfigVersion.cmake) says:


# check that the installed version has the same 32/64bit-ness as the one which 
is currently searching:
if(NOT CMAKE_SIZEOF_VOID_P STREQUAL "8")
  math(EXPR installedBits "8 * 8")
  set(PACKAGE_VERSION "${PACKAGE_VERSION} (${installedBits}bit)")
  set(PACKAGE_VERSION_UNSUITABLE TRUE)
endif()

This last part `NOT CMAKE_SIZEOF_VOID_P STREQUAL "8"', seems to indicate that it 
would never work on a 32 bit system. Is the "8" here meant to be replaced at 
build time?


Happy hacking,

[1]
https://buildd.debian.org/status/fetch.php?pkg=frameworkintegration&arch=i386&ver=5.37.0-2&stamp=1504461982&raw=0

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

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

--
"C makes it easy to shoot yourself in the foot; C++ makes it harder,
but when you do it blows your whole leg off."
-- Bjarne Stroustrup
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#874167: gcc-6-doc: source uploaded without binaries, caused package removal

[Adam Borowski]

On Sun, Sep 03, 2017 at 08:52:19PM +0200, Mattia Rizzolo wrote:
> Source: gcc-6-doc
> Severity: serious
> Version: 6.4.0-1
> X-Debbugs-Cc: culu@gmail.com, kilob...@angband.pl, dktrkr...@debian.org
> 
> Hi!
> 
> gcc-6-doc is a non-free package, therefore wanna-build doesn't attempt
> its build automatically.  Also, it is not manually whitelisted (it's
> also missing the XS-Autobuild header).
> Nonetheless you uploaded it source-only, without binaries; due to it,
> dak considered the binaries as not built anymore, and ended up in the
> cruft report.  From there an overzealous ftp-master removed it :)

Oif.

> Please upload the package again (which will end up in NEW), and remember
> to either always upload the binaries, or to ask to enable autobuilding.

I've uploaded source+binary identical as before (as it has been in the
archive, any modifications would be a bad idea).  If this won't work, the
maintainer (Guo Yixuan) is a better person to bump the version and make
adjustments.

XS-Autobuild can be added -2 no matter if we need it tonight or months
later.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢰⠒⠀⣿⡁ Vat kind uf sufficiently advanced technology iz dis!?
⢿⡄⠘⠷⠚⠋⠀ -- Genghis Ht'rok'din
⠈⠳⣄ 

Processed (with 1 error): forcibly merging 874170 874169

[Debian Bug Tracking System]

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

> forcemerge 874170 874169
Bug #874170 [libappstreamqt-dev] libappstreamqt-dev: AppStreamQtConfig.cmake 
hardcodes a 64bit behaviour
Unable to merge bugs because:
package of #874169 is 'src:appstream' not 'libappstreamqt-dev'
Failed to forcibly merge 874170: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Processed: reassign 874169 to libappstreamqt-dev, forcibly merging 874170 874169

[Debian Bug Tracking System]

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

> reassign 874169 libappstreamqt-dev appstream/0.11.4-1
Bug #874169 [src:appstream] AppStreamQtConfig.cmake no longer usable in i386
Bug reassigned from package 'src:appstream' to 'libappstreamqt-dev'.
No longer marked as found in versions appstream/0.11.4-1.
Ignoring request to alter fixed versions of bug #874169 to the same values 
previously set
Bug #874169 [libappstreamqt-dev] AppStreamQtConfig.cmake no longer usable in 
i386
Marked as found in versions appstream/0.11.4-1.
> forcemerge 874170 874169
Bug #874170 [libappstreamqt-dev] libappstreamqt-dev: AppStreamQtConfig.cmake 
hardcodes a 64bit behaviour
Bug #874169 [libappstreamqt-dev] AppStreamQtConfig.cmake no longer usable in 
i386
Severity set to 'grave' from 'critical'
Added indication that 874169 affects 
src:frameworkintegration,src:plasma-discover
Merged 874169 874170
> thanks
Stopping processing here.

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

Bug#874167: gcc-6-doc: source uploaded without binaries, caused package removal

[Mattia Rizzolo]

On Sun, Sep 03, 2017 at 09:30:08PM +0200, Adam Borowski wrote:
> I've uploaded source+binary identical as before (as it has been in the
> archive, any modifications would be a bad idea).  If this won't work, the
> maintainer (Guo Yixuan) is a better person to bump the version and make
> adjustments.

I fear that it's going to be rejected…  but let's see :)

> XS-Autobuild can be added -2 no matter if we need it tonight or months
> later.

Right.  But please consider adding it, as it makes only sense to have
that stuff built on the buildds.  Also remember that XS-Autobuild is
only the first step, you need to ask it to be whitelisted on the buildds
https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#non-free-buildd

-- 
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#874170: libappstreamqt-dev: AppStreamQtConfig.cmake hardcodes a 64bit behaviour

[Matthias Klumpp]

2017-09-03 21:22 GMT+02:00 Pino Toscano :
> Package: libappstreamqt-dev
> Version: 0.11.4-1
> Severity: grave
> Justification: renders package unusable
> Control: affects -1 src:frameworkintegration
> Control: affects -1 src:plasma-discover
>
> Hi,
>
> in the new version 0.11.4, I guess because of the switch from cmake to
> meson, the source got a template for the AppStreamQtConfig.cmake file.
> This template was created from an existing file on a 64bit system, so
> the final AppStreamQtConfig.cmake file is rejected by cmake when found
> by packages via cmake on 32bit architectures.
>
> Two examples are frameworkintergration, and plasma-discover:
> https://buildd.debian.org/status/logs.php?pkg=frameworkintegration&ver=5.37.0-2
> https://buildd.debian.org/status/logs.php?pkg=plasma-discover&ver=5.10.5-1
> In particular:
>
> <
> CMake Warning at CMakeLists.txt:44 (find_package):
>   Could not find a configuration file for package "AppStreamQt" that is
>   compatible with requested version "0.10.4".
>
>   The following configuration files were considered but not accepted:
>
> /usr/lib/i386-linux-gnu/cmake/AppStreamQt/AppStreamQtConfig.cmake, 
> version: 0.11.4 (64bit)
> <
>
> The severity is grave because this is an issue in the upstream sources,
> and because it's a regression compared to the previous version (and thus
> ought to not migrate to testing).

Bah... I'll see to fix this as soon as possible, first I need to read
up on how CMake determines which files are appropriate.

Cheers,
Matthias

Bug#874169: AppStreamQtConfig.cmake no longer usable in i386

[Matthias Klumpp]

2017-09-03 21:15 GMT+02:00 Maximiliano Curia :
> [...]
> # check that the installed version has the same 32/64bit-ness as the one
> which is currently searching:
> if(NOT CMAKE_SIZEOF_VOID_P STREQUAL "8")
>   math(EXPR installedBits "8 * 8")
>   set(PACKAGE_VERSION "${PACKAGE_VERSION} (${installedBits}bit)")
>   set(PACKAGE_VERSION_UNSUITABLE TRUE)
> endif()
>
> This last part `NOT CMAKE_SIZEOF_VOID_P STREQUAL "8"', seems to indicate
> that it would never work on a 32 bit system. Is the "8" here meant to be
> replaced at build time?

Can you try removing that entire section and see if that fixes it?
It serves no real purpose in how AppStreamQt is used anyway.

Cheers,
Matthias

Bug#853578: marked as done (ntopng: ftbfs with GCC-7)

[Debian Bug Tracking System]

Your message dated Sun, 03 Sep 2017 19:59:21 +
with message-id 
and subject line Bug#853578: fixed in ntopng 2.4+dfsg1-4
has caused the Debian Bug report #853578,
regarding ntopng: 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.)


-- 
853578: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853578
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ntopng
Version: 2.4+dfsg1-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/ntopng_2.4+dfsg1-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

[...]
src/Lua.cpp:4196:12: warning: '%f' directive output may be truncated writing 
between 8 and 317 bytes into a region of size 64 [-Wformat-truncation=]
 static int ntop_lua_http_print(lua_State* vm) {
^~~
In file included from /usr/include/stdio.h:938:0,
 from /<>/ntopng-2.4+dfsg1/include/ntop_includes.h:31,
 from src/Lua.cpp:22:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:65:44: note: format output between 
9 and 318 bytes into a destination of size 64
__bos (__s), __fmt, __va_arg_pack ());
^
src/Lua.cpp: In function 'int ntop_list_reports(lua_State*)':
src/Lua.cpp:3730:12: warning: '%s' directive output truncated while writing 7 
bytes into a region of size 0 [-Wformat-truncation=]
 static int ntop_list_reports(lua_State* vm) {
^
In file included from /usr/include/stdio.h:938:0,
 from /<>/ntopng-2.4+dfsg1/include/ntop_includes.h:31,
 from src/Lua.cpp:22:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:65:44: note: format output between 
9 and 264 bytes into a destination of size 256
__bos (__s), __fmt, __va_arg_pack ());
^
In file included from src/Lua.cpp:38:0:
src/../third-party/snmp/snmp.c: In function 'SNMPMessage* 
snmp_parse_message(void*, int)':
src/../third-party/snmp/snmp.c:250:33: warning: 'type' may be used 
uninitialized in this function [-Wmaybe-uninitialized]
snmp_add_varbind_integer_type(message, oid, type, value.int_value);
~^
g++ -g -Wall -I/<>/ntopng-2.4+dfsg1 
-I/<>/ntopng-2.4+dfsg1/include -I/usr/local/include 
-D_FILE_OFFSET_BITS=64 -I/usr/include/hiredis -I/usr/include/hiredis 
-I/<>/ntopng-2.4+dfsg1/third-party/mongoose -I/usr/include/json-c 
-I/usr/include/libndpi-1.8.0/libndpi -I/usr/include/luajit-2.0   
-I/usr/include/mysql -Wdate-time -D_FORTIFY_SOURCE=2 
-I/<>/ntopng-2.4+dfsg1 -I/<>/ntopng-2.4+dfsg1/include 
-I/usr/local/include 
-I/<>/ntopng-2.4+dfsg1/third-party/http-client-c/src/  
-DDATA_DIR='"/usr/share"' 
-I/<>/ntopng-2.4+dfsg1/third-party/libgeohash 
-I/<>/ntopng-2.4+dfsg1/third-party/patricia  -g -O2 
-fdebug-prefix-map=/<>/ntopng-2.4+dfsg1=. -fstack-protector-strong 
-Wformat -Werror=format-security -c src/main.cpp -o src/main.o
src/main.cpp: In function 'int main(int, char**)':
src/main.cpp:79:5: warning: output may be truncated at or before format 
character '.' at offset 3 [-Wformat-truncation=]
 int main(int argc, char *argv[])
 ^~~~
In file included from /usr/include/stdio.h:938:0,
 from /<>/ntopng-2.4+dfsg1/include/ntop_includes.h:31,
 from src/main.cpp:22:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:65:44: note: format output between 
7 and 262 bytes into a destination of size 256
__bo

Bug#874176: wrk: Fails to run with 'PANIC: unprotected error in call to Lua API'

[Federico Ceratto]

Package: wrk
Version: 4.0.2-2
Severity: grave

The error makes wrk unusable:

wrk -d 3 http://localhost:8080/
PANIC: unprotected error in call to Lua API (attempt to index a nil value)


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

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

Versions of packages wrk depends on:
ii  libc62.24-17
ii  libluajit-5.1-2  2.1.0~beta3+dfsg-2
ii  libssl1.11.1.0f-5

wrk recommends no packages.

wrk suggests no packages.

-- no debconf information

Bug#874177: expat/lib/nametab.h source missing

[Helmut Grohne]

Source: expat
Version: 2.2.3-1
Severity: serious
Justification: missing source
User: helm...@debian.org
Usertags: rebootstrap

The source code for generating expat/lib/nametab.h is missing from the
debian source package. It can be found at
https://github.com/libexpat/libexpat/blob/97c6bd01990090d4015364ae37dd141f3c39a30f/expat/gennmtab/gennmtab.c.

Helmut

Bug#874165: libvdpau FTBFS: configure: error: Documentation enabled but doxygen was not found in your path

[Luca Boccassi]

Control: close -1 1.1.1-8

On Sun, 2017-09-03 at 19:41 +0100, Luca Boccassi wrote:
> On September 3, 2017 7:15:04 PM GMT+01:00, Adrian Bunk  rg> wrote:
> > Source: libvdpau
> > Version: 1.1.1-7
> > Severity: serious
> > 
> > https://buildd.debian.org/status/package.php?p=libvdpau&suite=sid
> > 
> > ...
> > checking for library containing pthread_once... -lpthread
> > checking for doxygen... no
> > checking for dot... no
> > configure: error: Documentation enabled but doxygen was not found
> > in
> > your path
> 
> Hi,
> 
> Yes, I did a boo-boo :-P
> I failed to see the problem when testing with pbuilder, but I've
> already pushed a fix some minutes ago, hopefully it's good this time.

Yep it's fixed now, thanks.

-- 
Kind regards,
Luca Boccassi

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

Processed: Re: Bug#874165: libvdpau FTBFS: configure: error: Documentation enabled but doxygen was not found in your path

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.1.1-8
Bug #874165 [src:libvdpau] libvdpau FTBFS: configure: error: Documentation 
enabled but doxygen was not found in your path
Marked as fixed in versions libvdpau/1.1.1-8.
Bug #874165 [src:libvdpau] libvdpau FTBFS: configure: error: Documentation 
enabled but doxygen was not found in your path
Marked Bug as done

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

Bug#874180: python3-tk: undefined symbol in _tkinter.cpython-35m-x86_64-linux-gnu.so

[Philippe Daouadi]

Package: python3-tk
Version: 3.5.3-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

After updating my system, python3-tk stopped functionning:

>>> import _tkinter
Traceback (most recent call last):
  File "", line 1, in 
ImportError: 
/usr/lib/python3.5/lib-dynload/_tkinter.cpython-35m-x86_64-linux-gnu.so: 
undefined symbol: PyFPE_jbuf

Here is the output of ldd:

$ LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libpython3.5m.so ldd -r 
/usr/lib/python3.5/lib-dynload/_tkinter.cpython-35m-x86_64-linux-gnu.so 
linux-vdso.so.1 (0x7ffd1fdfe000)
/usr/lib/x86_64-linux-gnu/libpython3.5m.so (0x7fca1211f000)
libBLT.2.5.so.8.6 => /usr/lib/libBLT.2.5.so.8.6 (0x7fca11db)
libtk8.6.so => /usr/lib/x86_64-linux-gnu/libtk8.6.so (0x7fca11a52000)
libtcl8.6.so => /usr/lib/x86_64-linux-gnu/libtcl8.6.so (0x7fca1169b000)
libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 (0x7fca1135b000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7fca1113e000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fca10da1000)
libexpat.so.1 => /lib/x86_64-linux-gnu/libexpat.so.1 (0x7fca10b76000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7fca1095c000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fca10758000)
libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1 (0x7fca10555000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fca10251000)
libnsl.so.1 => /lib/x86_64-linux-gnu/libnsl.so.1 (0x7fca1003a000)
libXft.so.2 => /usr/lib/x86_64-linux-gnu/libXft.so.2 (0x7fca0fe24000)
libfontconfig.so.1 => /usr/lib/x86_64-linux-gnu/libfontconfig.so.1 
(0x7fca0fbe)
libfreetype.so.6 => /usr/lib/x86_64-linux-gnu/libfreetype.so.6 
(0x7fca0f92b000)
libXss.so.1 => /usr/lib/x86_64-linux-gnu/libXss.so.1 (0x7fca0f728000)
libXext.so.6 => /usr/lib/x86_64-linux-gnu/libXext.so.6 (0x7fca0f516000)
libxcb.so.1 => /usr/lib/x86_64-linux-gnu/libxcb.so.1 (0x7fca0f2ee000)
/lib64/ld-linux-x86-64.so.2 (0x7fca129b)
libXrender.so.1 => /usr/lib/x86_64-linux-gnu/libXrender.so.1 
(0x7fca0f0e4000)
libpng16.so.16 => /usr/lib/x86_64-linux-gnu/libpng16.so.16 
(0x7fca0eeb1000)
libXau.so.6 => /usr/lib/x86_64-linux-gnu/libXau.so.6 (0x7fca0ecad000)
libXdmcp.so.6 => /usr/lib/x86_64-linux-gnu/libXdmcp.so.6 
(0x7fca0eaa7000)
libbsd.so.0 => /lib/x86_64-linux-gnu/libbsd.so.0 (0x7fca0e892000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7fca0e68a000)
  undefined symbol: 
PyFPE_jbuf(/usr/lib/python3.5/lib-dynload/_tkinter.cpython-35m-x86_64-linux-gnu.so)
  undefined symbol: 
PyFPE_counter(/usr/lib/python3.5/lib-dynload/_tkinter.cpython-35m-x86_64-linux-gnu.so)

Philippe

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

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

Versions of packages python3-tk depends on:
ii  blt   2.5.3+dfsg-3
ii  libc6 2.24-17
ii  libtcl8.6 8.6.7+dfsg-1
ii  libtk8.6  8.6.7-1
ii  libx11-6  2:1.6.4-3
ii  python3   3.5.3-3
ii  tk8.6-blt2.5  2.5.3+dfsg-3

python3-tk recommends no packages.

Versions of packages python3-tk suggests:
pn  python3-tk-dbg  
pn  tix 

-- no debconf information

Bug#874042: marked as done (hmmer2: please Build-Depend on rename)

[Debian Bug Tracking System]

Your message dated Sun, 03 Sep 2017 21:06:57 +
with message-id 
and subject line Bug#874042: fixed in hmmer2 2.3.2+dfsg-5
has caused the Debian Bug report #874042,
regarding hmmer2: please Build-Depend on rename
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.)


-- 
874042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874042
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hmmer2
Version: 2.3.2+dfsg-4
Severity: serious
Justification: FTBFS with impending change
User: debian-p...@lists.debian.org
Usertags: rename-deprecation

As announced last year[1] and as advised by deprecation messages,
rename(1) will be removed from the perl package after the stretch
release, and this is now imminent.

Your package FTBFS with perl from experimental as a result. Please
add a Build-Depends: rename to your package, and all will be well
again:

# lkajan: rename binaries and man pages like this: s/hmm/hmm2/ - except 
hmmer.1, rename that to hmmer2.1:
rename 's/^hmm/hmm2/;' /<>/hmmer2-2.3.2+dfsg/debian/tmp/bin/*
/bin/sh: 1: rename: not found
debian/rules:31: recipe for target 'override_dh_auto_install' failed

Cheers,
Dominic.

[1] 
--- End Message ---
--- Begin Message ---
Source: hmmer2
Source-Version: 2.3.2+dfsg-5

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

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

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated hmmer2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 03 Sep 2017 21:50:24 +0200
Source: hmmer2
Binary: hmmer2 hmmer2-pvm hmmer2-doc libhmmer2-dev
Architecture: source amd64 all
Version: 2.3.2+dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 hmmer2 - profile hidden Markov models for protein sequence analysis
 hmmer2-doc - profile hidden Markov models for protein sequence analysis (docs)
 hmmer2-pvm - HMMER programs with PVM (Parallel Virtual Machine) support
 libhmmer2-dev - profile hidden Markov models for protein sequence analysis 
(devel
Closes: 874042
Changes:
 hmmer2 (2.3.2+dfsg-5) unstable; urgency=medium
 .
   [ Steffen Moeller ]
   * debian/upstream/metadata: Added refs to OMICtoos,
 bio.tools, RRID
 .
   [ Andreas Tille ]
   * Build-Depends: rename
 Closes: #874042
   * Standards-Version: 4.1.0 (no chaanges needed)
   * Drop autotools-dev
Checksums-Sha1:
 a3fae70d2330228aed3f68e40728ac46dce01638 2302 hmmer2_2.3.2+dfsg-5.dsc
 7363d8b9efd280ca1b9e5dcc58726ee587dd166a 12752 
hmmer2_2.3.2+dfsg-5.debian.tar.xz
 25933f74fc2c8a876f631fc837453f5097c78844 1316530 
hmmer2-dbgsym_2.3.2+dfsg-5_amd64.deb
 b92035fc992031dd19a3b4453343cc8e979faa2d 79264 hmmer2-doc_2.3.2+dfsg-5_all.deb
 37bd65e9a365fcce12bd92bfc247b414a6acbebf 425022 
hmmer2-pvm-dbgsym_2.3.2+dfsg-5_amd64.deb
 91a55800aa8fa8c8d8c24f8045c6555c0f2a3cd6 99802 
hmmer2-pvm_2.3.2+dfsg-5_amd64.deb
 97c8ff00a71bd6b0ce315d630054c7d8bbc235c4 7510 
hmmer2_2.3.2+dfsg-5_amd64.buildinfo
 7677c324bb99ad24c189da1a0179fef189962951 1519004 hmmer2_2.3.2+dfsg-5_amd64.deb
 dce3fde38476d5a46ce4c58fad424d56d997b753 101422 
libhmmer2-dev_2.3.2+dfsg-5_amd64.deb
Checksums-Sha256:
 84713b364659289398eea87b6e85191541a9865e24d3c26f8d6968550a45728d 2302 
hmmer2_2.3.2+dfsg-5.dsc
 17d1625f3f26a10caeb37ec47d7104be3d048118344b200703e3b28ddba592fb 12752 
hmmer2_2.3.2+dfsg-5.debian.tar.xz
 bb78ad9f3ca4ec75990c662e748ce75cb5dfbc1197c54b35590b8102c4598999 1316530 
hmmer2-dbgsym_2.3.2+dfsg-5_amd64.deb
 08a573e11819677569a9462068afef31340903d57fe672a5b5f49d41be3e5b70 79264 
hmmer2-doc_2.3.2+dfsg-5_all.deb
 d52a9d2885ae3758108d86198f44f41c1e01e5ff81b76feaea85e1ccf2da3ae2 425022 
hmmer2-pvm-dbgsym_2.3.2+dfsg-5_amd64.deb
 69b1501b0abb3bd44d357fcff8026cd3fdbcf2bde3cebe98f153f4bb740d2c40 99802 
hmmer2-pvm_2.3.2+dfsg-5_amd64.deb
 aa11e2af0de72c040166f0935b4acbbfcad795afc945be656d71d47670ff82ec 7510 
hmmer2_2.3.2+dfsg-5_amd64.buildinfo
 2c4f64a70ffd35f6d296e4106a794d8e48f75fcfac1e6c8a13efaaeb8995c25b 1519004

Bug#873508: sparse test failures on ppc32le (and other not so common archs)

[Luc Van Oostenryck]

On Fri, Sep 1, 2017 at 9:02 AM, Josh Triplett  wrote:
> On Thu, Aug 31, 2017 at 08:47:55PM -0400, Christopher Li wrote:
>> On Thu, Aug 31, 2017 at 4:55 PM, Uwe Kleine-König  Yes
>> that works. So to address the Debian bug I can do:
>> >
>> >  - move sparse to /usr/lib
>> >  - teach cgcc about the move of sparse
>> >  - make /usr/bin/sparse call cgcc -no-compile "$@"
>>
>> I don't like that. It means the user can't invoke sparse directly.
>>
>> >
>> > or is it easier to teach sparse about the architecture stuff?
>>
>> First of all. It is not very trivial to teach sparse about the architecture
>> stuff. To my mind, we need to move all the cgcc logic into sparse.
>
> Related to that: while it would mean we couldn't necessarily just rely
> entirely on GCC's definitions for a target platform, I think in an ideal
> world we could have a sparse binary that understood *all* target
> platforms at once, such that you could ask Sparse on x86_64 to "compile"
> as though targeting any arbitrary architecture. That would also have the
> major advantage of making it easy to run the Sparse testsuite for
> *every* target architecture without needing compilers for every such
> architecture.

I really think that the testsuite should not depend on system or library
header.

Otherwise, I'm not at all opposed to sparse being universal but I would like
to note that things can become very quickly very very messy.
For example, for the current problem here I understood that it was
at least partially based on the lack of a definition of _CALL_ELF
but do we need to define it to 1 or to 2, in other words, do we need
to support the ELFv1 ABI or the ELFv2? GCC has some flags for this
(-mabi=elfv[12]) but what default value do we want? ELFv1 is the default
for big-endian platform and ELFv2 for little-endian platform, so yes,
we need a flag for the endianness but which endianness we want as default?
And so on.

Things become even more fun when taking in account the difference
between GCC version. Do we want to be universal there too (and thus
have some flags for to specify which gcc's version we want to mimick)?
What about other compilers?


I think that part of the needed info can be auto-extracted from GCC
when doing a native build. Using some sort of spec file or a .sparserc
can help too.

I also note that currently, sparse is already largely universal *because*
it *doesn't* need those platform details (or only the very minimal: word size).

-- Luc Van Oostenryck

Bug#874185: _solve_toeplitz.x86_64-linux-gnu.so: undefinedsymbol: PyFPE_jbuf

[Sébastien Villemot]

Package: python-scipy
Version: 0.18.1-2+b2
Severity: serious

The linalg submodule currently cannot be loaded in sid:

$ python -c "from scipy import linalg"
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.7/dist-packages/scipy/linalg/__init__.py", line 175, 
in 
from .basic import *
  File "/usr/lib/python2.7/dist-packages/scipy/linalg/basic.py", line 21, in 

from ._solve_toeplitz import levinson
ImportError: 
/usr/lib/python2.7/dist-packages/scipy/linalg/_solve_toeplitz.x86_64-linux-gnu.so:
 undefined symbol: PyFPE_jbuf

This issue seems related to #873791.

Cheers,

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


signature.asc
Description: PGP signature

Processed: Missing dependencies are RC

[Debian Bug Tracking System]

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

> severity 695584 serious
Bug #695584 [libxsettings-client-dev] Missing dependency on libxsettings-dev
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#874187: qtermwidget FTBFS with Qt 5.9: symbol differences

[Adrian Bunk]

Source: qtermwidget
Version: 0.7.1-4
Severity: serious

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

...
   dh_makeshlibs -O--buildsystem=cmake -O--fail-missing
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libqtermwidget5-0/DEBIAN/symbols doesn't match 
completely debian/libqtermwidget5-0.symbols
--- debian/libqtermwidget5-0.symbols (libqtermwidget5-0_0.7.1-4_amd64)
+++ dpkg-gensymbolsY7a7UW   2018-10-06 15:07:51.983955567 -1200
@@ -115,18 +115,18 @@
  (c++)"Konsole::AutoScrollHandler::~AutoScrollHandler()@Base" 0.6.0
  (c++)"Konsole::BlockArray::BlockArray()@Base" 0.6.0
  (c++)"Konsole::BlockArray::append(Konsole::Block*)@Base" 0.6.0
- (optional|c++)"Konsole::BlockArray::at(unsigned int)@Base" 0.6.0
+#MISSING: 0.7.1-4# (optional|c++)"Konsole::BlockArray::at(unsigned int)@Base" 
0.6.0
  (optional|c++)"Konsole::BlockArray::at(unsigned long)@Base" 0.6.0
- (optional|c++)"Konsole::BlockArray::decreaseBuffer(unsigned int)@Base" 0.6.0
+#MISSING: 0.7.1-4# (optional|c++)"Konsole::BlockArray::decreaseBuffer(unsigned 
int)@Base" 0.6.0
  (optional|c++)"Konsole::BlockArray::decreaseBuffer(unsigned long)@Base" 0.6.0
- (optional|c++)"Konsole::BlockArray::has(unsigned int) const@Base" 0.6.0
+#MISSING: 0.7.1-4# (optional|c++)"Konsole::BlockArray::has(unsigned int) 
const@Base" 0.6.0
  (optional|c++)"Konsole::BlockArray::has(unsigned long) const@Base" 0.6.0
  (c++)"Konsole::BlockArray::increaseBuffer()@Base" 0.6.0
  (c++)"Konsole::BlockArray::lastBlock() const@Base" 0.6.0
  (c++)"Konsole::BlockArray::newBlock()@Base" 0.6.0
- (optional|c++)"Konsole::BlockArray::setHistorySize(unsigned int)@Base" 0.6.0
+#MISSING: 0.7.1-4# (optional|c++)"Konsole::BlockArray::setHistorySize(unsigned 
int)@Base" 0.6.0
  (optional|c++)"Konsole::BlockArray::setHistorySize(unsigned long)@Base" 0.6.0
- (optional|c++)"Konsole::BlockArray::setSize(unsigned int)@Base" 0.6.0
+#MISSING: 0.7.1-4# (optional|c++)"Konsole::BlockArray::setSize(unsigned 
int)@Base" 0.6.0
  (optional|c++)"Konsole::BlockArray::setSize(unsigned long)@Base" 0.6.0
  (c++)"Konsole::BlockArray::unmap()@Base" 0.6.0
  (c++)"Konsole::BlockArray::~BlockArray()@Base" 0.6.0
@@ -172,7 +172,7 @@
  (c++)"Konsole::ColorSchemeManager::loadCustomColorScheme(QString 
const&)@Base" 0.6.0
  (c++)"Konsole::ColorSchemeManager::loadKDE3ColorScheme(QString const&)@Base" 
0.6.0
  (c++)"Konsole::ColorSchemeManager::~ColorSchemeManager()@Base" 0.6.0
- (optional|c++)"Konsole::CompactHistoryBlock::allocate(unsigned int)@Base" 
0.6.0
+#MISSING: 0.7.1-4# 
(optional|c++)"Konsole::CompactHistoryBlock::allocate(unsigned int)@Base" 0.6.0
  (optional|c++)"Konsole::CompactHistoryBlock::allocate(unsigned long)@Base" 
0.6.0
  (c++)"Konsole::CompactHistoryBlock::contains(void*)@Base" 0.6.0
  (c++)"Konsole::CompactHistoryBlock::deallocate()@Base" 0.6.0
@@ -180,7 +180,7 @@
  (c++)"Konsole::CompactHistoryBlock::length()@Base" 0.6.0
  (c++)"Konsole::CompactHistoryBlock::remaining()@Base" 0.6.0
  (c++)"Konsole::CompactHistoryBlock::~CompactHistoryBlock()@Base" 0.6.0
- (optional|c++)"Konsole::CompactHistoryBlockList::allocate(unsigned int)@Base" 
0.6.0
+#MISSING: 0.7.1-4# 
(optional|c++)"Konsole::CompactHistoryBlockList::allocate(unsigned int)@Base" 
0.6.0
  (optional|c++)"Konsole::CompactHistoryBlockList::allocate(unsigned 
long)@Base" 0.6.0
  (c++)"Konsole::CompactHistoryBlockList::deallocate(void*)@Base" 0.6.0
  (c++)"Konsole::CompactHistoryBlockList::~CompactHistoryBlockList()@Base" 0.6.0
@@ -189,7 +189,7 @@
  (c++)"Konsole::CompactHistoryLine::getCharacters(Konsole::Character*, int, 
int)@Base" 0.6.0
  (c++)"Konsole::CompactHistoryLine::getLength() const@Base" 0.6.0
  (c++)"Konsole::CompactHistoryLine::isWrapped() const@Base" 0.6.0
- (optional|c++)"Konsole::CompactHistoryLine::operator new(unsigned int, 
Konsole::CompactHistoryBlockList&)@Base" 0.6.0
+#MISSING: 0.7.1-4# (optional|c++)"Konsole::CompactHistoryLine::operator 
new(unsigned int, Konsole::CompactHistoryBlockList&)@Base" 0.6.0
  (optional|c++)"Konsole::CompactHistoryLine::operator new(unsigned long, 
Konsole::CompactHistoryBlockList&)@Base" 0.6.0
  (c++)"Konsole::CompactHistoryLine::setWrapped(bool)@Base" 0.6.0
  (c++)"Konsole::CompactHistoryLine::~CompactHistoryLine()@Base" 0.6.0
@@ -318,7 +318,7 @@
  (c++)"Konsole::HistoryScroll::addCellsVector(QVector 
const&)@Base" 0.6.0
  (c++)"Konsole::HistoryScroll::hasScroll()@Base" 0.6.0
  (c++)"Konsole::HistoryScroll::~HistoryScroll()@Base" 0.6.0
- 
(optional|c++)"Konsole::HistoryScrollBlockArray::HistoryScrollBlockArray(unsigned
 int)@Base" 0.6.0
+#MISSING: 0.7.1-4# 
(optional|c++)"Konsole::HistoryScrollBlockArray::HistoryScrollBlockArray(unsigned
 int)@Base" 0.6.0
  
(optional|c++)"Konsole::HistoryScrollBlockArray::HistoryScrollBlockArray(unsigned
 long)@Base" 0.6.0
  (c++)"Konsole:

Bug#874169: AppStreamQtConfig.cmake no longer usable in i386

[Maximiliano Curia]

¡Hola Matthias!

El 2017-09-03 a las 21:45 +0200, Matthias Klumpp escribió:

2017-09-03 21:15 GMT+02:00 Maximiliano Curia :

[...]
# check that the installed version has the same 32/64bit-ness as the one 
which is currently searching:
if(NOT CMAKE_SIZEOF_VOID_P STREQUAL "8") 
  math(EXPR installedBits "8 * 8") 
  set(PACKAGE_VERSION "${PACKAGE_VERSION} (${installedBits}bit)") 
  set(PACKAGE_VERSION_UNSUITABLE TRUE) 
endif()


This last part `NOT CMAKE_SIZEOF_VOID_P STREQUAL "8"', seems to indicate 
that it would never work on a 32 bit system. Is the "8" here meant to be 
replaced at build time?


Can you try removing that entire section and see if that fixes it? 
It serves no real purpose in how AppStreamQt is used anyway.


Commenting out that block allowed frameworkintegration to build.

Happy hacking,
--
"Any change looks terrible at first." -- Principle of Design Inertia
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Bug#695584: marked as done (Missing dependency on libxsettings-dev)

[Debian Bug Tracking System]

Your message dated Sun, 03 Sep 2017 21:50:28 +
with message-id 
and subject line Bug#695584: fixed in libxsettings-client 0.17-9
has caused the Debian Bug report #695584,
regarding Missing dependency on libxsettings-dev
to be marked as done.

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

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


-- 
695584: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695584
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libxsettings-client-dev
Version: 0.17-6
Severity: normal

libxsettings-client-dev should depend on libxsettings-dev:

/usr/include/xsettings-client.h:27:30: fatal error: xsettings-common.h: No such 
file or directory

xsettings-common.h is packaged in libxsettings.dev.


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

Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages libxsettings-client-dev depends on:
ii  libx11-dev2:1.5.0-1
ii  libxsettings-client0  0.17-6

libxsettings-client-dev recommends no packages.

libxsettings-client-dev suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: libxsettings-client
Source-Version: 0.17-9

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated libxsettings-client package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 03 Sep 2017 23:36:18 +0300
Source: libxsettings-client
Binary: libxsettings-client0 libxsettings-client-dev libxsettings-client0-dbg 
libxsettings-client-doc
Architecture: source
Version: 0.17-9
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Adrian Bunk 
Description:
 libxsettings-client-dev - utility functions for the Xsettings protocol 
(Development files)
 libxsettings-client-doc - utility functions for the Xsettings protocol 
(Documentation)
 libxsettings-client0 - utility functions for the Xsettings protocol (GPE)
 libxsettings-client0-dbg - utility functions for the Xsettings protocol (Debug 
symbols)
Closes: 695584
Changes:
 libxsettings-client (0.17-9) unstable; urgency=medium
 .
   * QA upload.
   * Add the missing libxsettings-client-dev -> libxsettings-dev
 dependency. (Closes: #695584)
Checksums-Sha1:
 deeabc72978c787e911c6d2392e9cdc6301df09b 2123 libxsettings-client_0.17-9.dsc
 053b8fb78d321570f08f9019924b8ae24fe14ea2 4556 
libxsettings-client_0.17-9.debian.tar.xz
Checksums-Sha256:
 47ece19b67d66d12f9b22790825244935173b1c6beadba573a013b58923e7b06 2123 
libxsettings-client_0.17-9.dsc
 9c846ef936df26ffd018ec7579c3c33d175e3036c1350466920f16e1e94f623f 4556 
libxsettings-client_0.17-9.debian.tar.xz
Files:
 b0d1facbe194e86dc8ae601653cf90bd 2123 libs optional 
libxsettings-client_0.17-9.dsc
 495fafef754fb2ed71aa857818361886 4556 libs optional 
libxsettings-client_0.17-9.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlmscpsACgkQiNJCh6LY
mLFNwQ/9HGZeHoyl4luj2WxV+IXu9BViEQu+XFucYvUTGLX2XRRzL4MnT5+VuB+z
IX8qetOazZzhPPy5nTNLTNqKw+yUiJB3e83ebggUvbAdFGs6NBxe0N01GVG6kjVy
FIi2gXKWpL6xkDYMscnyhmgJNMR3R5R4WE6JvFFn21aAgCRaCl6/J5JiTi81tj45
xZzu8qApKLIJs8TrJGBlEAsP4KscV7QzABaJbAewWvejyIAFDTbt6jsezBxUtOA4
skho7Rcrh7KVVyR5+JAlxMMqQawH0Ri7O8/XhPmyzd3m103+5RJLXLv2EPCZm0b8
uPh4kD544Aamj6vO2L79TElVN77nXZYB+7uTaZZNCKxmDjPl+XUhOjsImv1txnB6
oH1hUO0DOa5mP1roajS6FELI1nwIJxRMMgJVZuCmhhksFWwWoEgGYUzC9o1nsNVI
vC6c7c3b2yyEynMmFrOubGvZ515iK7a/oYKYj9bEh+bDACMxP/6gNqxxSnuQ8GO2
R06LYMZgRHJObYEGzZiDhuJUpu8WbOfqAdqJnUjxCKQVOGUwEz1C6dAAy+A2e9cv
uXoC16OLBUsHpUVCdXCQeUC3E9Zs8PbTLMdVlaQX9HTsZbvAFmP2Q7pZ3GctSIJh
UjBnAE2Sdnc8Hfbdrr5S+mUH7dNOXEIyJhKiCajN1ax1xItHFAQ=
=EPNG
-END PGP SIGNATURE End Message ---

Bug#873791: [python-numpy] Undefined symbols on several architectures

[Adrian Bunk]

Control: reopen -1

On Thu, Aug 31, 2017 at 12:48:53PM +0200, Matthias Klose wrote:
> On 31.08.2017 12:35, Adrian Bunk wrote:
> > Control: reassign -1 python2.7 2.7.14~rc1-1
> > Control: retitle -1 python2.7: fpectl extension removal broke the ABI for C 
> > extensions
> > Control: affects -1 python-numpy
> > 
> > On Thu, Aug 31, 2017 at 11:34:55AM +0200, Michał Klichowicz wrote:
> >> Got that error on amd64, too.
> >>
> >> This started today, after the upgrading python2.7 packages to 2.7.14~rc1
> >> in sid. Downgrading back to buster's 2.7.13-2 solves the problem.
> > 
> > I got the same error with Cython:
> > 
> > ImportError: 
> > /usr/lib/python2.7/dist-packages/Cython/Compiler/Code.x86_64-linux-gnu.so: 
> > undefined symbol: PyFPE_jbuf.  You should look at http://www.cython.org"; 
> > 
> > It seems the following change in 2.7.14~rc1-1 broke the ABI:
> >   * Stop building the fpectl extension.
> 
> yes, that's intended. I'll add a break.  Are there other known packages 
> besides
> python-numpy?

A complete list of all packages in unstable on amd64 that need rebuild
and Breaks is attached.

Additionally, Breaks are required for the following packages
that were already fixed in sid:
- cython
- cython3
- python-lxml
- python3-lxml

To avoid breaking testing, please keep these bugs open and RC until
all Breaks are in place.

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

PyFPE ./pool/main/a/adios/python-adios_1.12.0-3_amd64.deb
PyFPE ./pool/main/a/adios/python3-adios_1.12.0-3_amd64.deb
PyFPE ./pool/main/a/astroml-addons/python-astroml-addons_0.2.2-4_amd64.deb
PyFPE ./pool/main/a/astroml-addons/python3-astroml-addons_0.2.2-4_amd64.deb
PyFPE ./pool/main/a/astroscrappy/python-astroscrappy_1.0.5-1+b1_amd64.deb
PyFPE ./pool/main/a/astroscrappy/python3-astroscrappy_1.0.5-1+b1_amd64.deb
PyFPE ./pool/main/a/asyncpg/python3-asyncpg_0.12.0-1_amd64.deb
PyFPE ./pool/main/b/bcolz/python-bcolz_1.1.0+ds1-4+b1_amd64.deb
PyFPE ./pool/main/b/bcolz/python3-bcolz_1.1.0+ds1-4+b1_amd64.deb
PyFPE ./pool/main/b/borgbackup/borgbackup_1.0.11-3_amd64.deb
PyFPE ./pool/main/b/breezy/python-breezy_3.0.0~bzr6772-1_amd64.deb
PyFPE ./pool/main/b/bzr/python-bzrlib_2.7.0+bzr6622-7_amd64.deb
PyFPE ./pool/main/c/cypari2/python-cypari2_1.0.0-3_amd64.deb
PyFPE ./pool/main/d/dipy/python-dipy-lib_0.12.0-1_amd64.deb
PyFPE ./pool/main/e/epigrass/epigrass_2.4.7-1_amd64.deb
PyFPE ./pool/main/f/fiona/python-fiona_1.7.9-1_amd64.deb
PyFPE ./pool/main/f/fiona/python3-fiona_1.7.9-1_amd64.deb
PyFPE ./pool/main/f/fpylll/python-fpylll_0.2.4+ds-3_amd64.deb
PyFPE ./pool/main/h/h5py/python-h5py_2.7.0-1+b1_amd64.deb
PyFPE ./pool/main/h/h5py/python3-h5py_2.7.0-1+b1_amd64.deb
PyFPE ./pool/main/h/healpy/python-healpy_1.10.3-2+b1_amd64.deb
PyFPE ./pool/main/h/healpy/python3-healpy_1.10.3-2+b1_amd64.deb
PyFPE ./pool/main/h/htseq/python-htseq_0.6.1p1-4_amd64.deb
PyFPE ./pool/main/i/invesalius/invesalius-bin_3.1.1-1_amd64.deb
PyFPE ./pool/main/k/kivy/python-kivy_1.9.1-1+b1_amd64.deb
PyFPE ./pool/main/k/kivy/python3-kivy_1.9.1-1+b1_amd64.deb
PyFPE ./pool/main/libg/libgpuarray/python-pygpu_0.6.9-2_amd64.deb
PyFPE ./pool/main/libg/libgpuarray/python3-pygpu_0.6.9-2_amd64.deb
PyFPE 
./pool/main/libi/libimobiledevice/python-imobiledevice_1.2.0+dfsg-3.1_amd64.deb
PyFPE ./pool/main/m/macs/macs_2.1.1.20160309-1_amd64.deb
PyFPE ./pool/main/m/meliae/python-meliae_0.4.0+bzr199-3_amd64.deb
PyFPE ./pool/main/n/netcdf4-python/python-netcdf4_1.2.9-1+b1_amd64.deb
PyFPE ./pool/main/n/netcdf4-python/python3-netcdf4_1.2.9-1+b1_amd64.deb
PyFPE ./pool/main/n/nipy/python-nipy-lib_0.4.1-1_amd64.deb
PyFPE ./pool/main/p/pandas/python-pandas-lib_0.20.3-1_amd64.deb
PyFPE ./pool/main/p/pandas/python3-pandas-lib_0.20.3-1_amd64.deb
PyFPE ./pool/main/p/petsc4py/python-petsc4py_3.7.0-3+b1_amd64.deb
PyFPE ./pool/main/p/petsc4py/python3-petsc4py_3.7.0-3+b1_amd64.deb
PyFPE ./pool/main/p/printrun/printrun_0~20150310-5_amd64.deb
PyFPE 
./pool/main/p/pybloomfiltermmap/python-pybloomfiltermmap_0.3.15-0.1+b1_amd64.deb
PyFPE ./pool/main/p/pycorrfit/pycorrfit_1.0.0+dfsg-1_amd64.deb
PyFPE ./pool/main/p/pyfai/python-pyfai_0.13.0+dfsg-1+b1_amd64.deb
PyFPE ./pool/main/p/pyfai/python3-pyfai_0.13.0+dfsg-1+b1_amd64.deb
PyFPE ./pool/main/p/pygame-sdl2/python-pygame-sdl2_6.99.12.4-1_amd64.deb
PyFPE ./pool/main/p/pygrib/python-grib_2.0.2-2_amd64.deb
PyFPE ./pool/main/p/pygrib/python3-grib_2.0.2-2_amd64.deb
PyFPE ./pool/main/p/pyliblo/python-liblo_0.10.0-3+b1_amd64.deb
PyFPE ./pool/main/p/pyliblo/python3-liblo_0.10.0-3+b1_amd64.deb
PyFPE ./pool/main/p/pymca/python-pymca5_5.1.3+dfsg-1+b1_amd64.deb
PyFPE ./pool/main/p/pymca/python3-pymca5_5.1.3+dfsg-1+b1_amd64.deb
PyFPE ./pool/main/p/pymssql/python-pymssql_2.1.3+dfsg-1+b1_amd64.deb
PyFPE ./pool/main/p/pymssql/python3-pymssql_2.1.3+dfsg-1+b1_amd64.deb
PyFPE ./pool/mai

Processed: Re: Bug#873791: [python-numpy] Undefined symbols on several architectures

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #873791 {Done: Matthias Klose } [python2.7] python2.7: 
fpectl extension removal broke the ABI for C extensions
'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 python2.7/2.7.14~rc1-2.

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

Processed: Re: Bug#873791: [python-numpy] Undefined symbols on several architectures

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #873921 [src:python3.5] python3.5_3.5.4-3 breaks borgbackup: undefined 
symbol: PyFPE_jbuf
Bug #874081 [src:python3.5] borgbackup: Won't start: ImportError: 
/usr/lib/python3/dist-packages/borg/crypto.cpython-35m-x86_64-linux-gnu.so: 
undefined symbol: PyFPE_jbuf
Bug 873921 is not marked as done; doing nothing.

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

Bug#874191: gdm3 started users start in wrong context

[Harlan Lieberman-Berg]

Package: selinux-policy-default
Version: 2:2.20161023.1-9
Severity: serious

Hello maintainers,

It seems that shells started via Gnome start with the wrong context.
Logging in from a console shell gives me an id of
unconfined_u:unconfined_r:unconfined_t:s0-s0, whereas terminals opened
inside Gnome give me a context of system_u:system_r:initrc_t:s0.

Sincerely,

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

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

Versions of packages selinux-policy-default depends on:
ii  libselinux1  2.6-3+b2
ii  libsemanage1 2.6-2+b1
ii  libsepol12.6-2
ii  policycoreutils  2.6-3
ii  selinux-utils2.6-3+b2

Versions of packages selinux-policy-default recommends:
ii  checkpolicy  2.6-2
ii  setools  4.0.1-6+b1

Versions of packages selinux-policy-default suggests:
pn  logcheck
pn  syslog-summary  

-- no debconf information

Bug#871112: Pending fixes for bugs in the surefire package

[pkg-java-maintainers]

tag 871112 + pending
thanks

Some bugs in the surefire package are closed in revision
d5a13a9afc56e91711bca95b747e1f153e6c6d99 in branch 'master' by
Emmanuel Bourg

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/surefire.git/commit/?id=d5a13a9

Commit message:

Fixed the build failure caused by the Doxia upgrade (Closes: #871112)

Processed: Pending fixes for bugs in the surefire package

[Debian Bug Tracking System]

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

> tag 871112 + pending
Bug #871112 [src:surefire] surefire: FTBFS: [ERROR] 
/<>/maven-surefire-report-plugin/src/main/java/org/apache/maven/plugins/surefire/report/SurefireReportGenerator.java:[601,50]
 cannot find symbol
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#871112: marked as done (surefire: FTBFS: [ERROR] /<>/maven-surefire-report-plugin/src/main/java/org/apache/maven/plugins/surefire/report/SurefireReportGenerator.java:[601,50

[Debian Bug Tracking System]

Your message dated Sun, 03 Sep 2017 22:26:46 +
with message-id 
and subject line Bug#871112: fixed in surefire 2.19.1-2
has caused the Debian Bug report #871112,
regarding surefire: FTBFS: [ERROR] 
/<>/maven-surefire-report-plugin/src/main/java/org/apache/maven/plugins/surefire/report/SurefireReportGenerator.java:[601,50]
 cannot find symbol
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.)


-- 
871112: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871112
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: surefire
Version: 2.19.1-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[1]: Entering directory '/<>'
> # two passes build to work around a circular dependency between 
> maven-surefire-common and maven-surefire-plugin
> dh_auto_build -- install -DskipTests
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
>  -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> -Dproperties.file.manual=/<>/debian/maven.properties 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo install -DskipTests 
> -DskipTests -Dnotimestamp=true -Dlocale=en_US
> [INFO] Scanning for projects...
> [WARNING] 
> [WARNING] Some problems were encountered while building the 
> effective model for org.apache.maven.surefire:surefire-junit47:jar:2.19.1
> [WARNING] 'build.plugins.plugin.version' for 
> org.apache.maven.plugins:maven-compiler-plugin is missing. @ line 120, column 
> 12
> [WARNING] 
> [WARNING] It is highly recommended to fix these problems because 
> they threaten the stability of your build.
> [WARNING] 
> [WARNING] For this reason, future Maven versions might no longer 
> support building such malformed projects.
> [WARNING] 
> [WARNING] The project 
> org.apache.maven.surefire:surefire-grouper:jar:2.19.1 uses prerequisites 
> which is only intended for maven-plugin projects but not for non maven-plugin 
> projects. For such purposes you should use the maven-enforcer-plugin. See 
> https://maven.apache.org/enforcer/enforcer-rules/requireMavenVersion.html
> [WARNING] The project 
> org.apache.maven.surefire:maven-surefire-common:jar:2.19.1 uses prerequisites 
> which is only intended for maven-plugin projects but not for non maven-plugin 
> projects. For such purposes you should use the maven-enforcer-plugin. See 
> https://maven.apache.org/enforcer/enforcer-rules/requireMavenVersion.html
> [WARNING] The project 
> org.apache.maven.surefire:surefire-report-parser:jar:2.19.1 uses 
> prerequisites which is only intended for maven-plugin projects but not for 
> non maven-plugin projects. For such purposes you should use the 
> maven-enforcer-plugin. See 
> https://maven.apache.org/enforcer/enforcer-rules/requireMavenVersion.html
> [INFO] 
> 
> [INFO] Reactor Build Order:
> [INFO] 
> [INFO] Apache Maven Surefire
> [INFO] SureFire API
> [INFO] SureFire Booter
> [INFO] Maven Surefire Test-Grouping Support
> [INFO] SureFire Providers
> [INFO] Shared JUnit3 Provider Code
> [INFO] Shared Java 5 Provider Base
> [INFO] Shared JUnit4 Provider Code
> [INFO] Shared JUnit48 Provider Code
> [INFO] SureFire JUnit Runner
> [INFO] SureFire JUnit4 Runner
> [INFO] Maven Surefire Common
> [INFO] SureFire JUnitCore Runner
> [INFO] SureFire TestNG Utils
> [INFO] SureFire TestNG Runner
> [INFO] Surefire Report Parser
> [INFO] Maven Surefire Report Plugin
> [INFO] 
> [INFO] 
> 
> [INFO] Building Apache Maven Surefire 2.19.1
> [INFO] 
> 
> [INFO] 
> [INFO] --- maven-install-plugin:2.5.2:install 
> (default

Bug#874133: xfrisk: Always crashes due to "stack smashing" on pressing "Start game"

[Axel Beckert]

Hi again,

Axel Beckert wrote:
> Adrian Bunk wrote:
> > Crashes for me with 1.2-4
> > Works for me with 1.2-3+b2
> > 
> > Looking at the build logs, the hardening flags
> > (especially -fstack-protector-strong) are new
> > in -4 and likely trigger the issue.
> 
> Thanks for that hint! Didn't notice it when uploading 1.2-4. Probably
> didn't test far enough.

Hrm, The crashes are less verbose with "export
DEB_BUILD_MAINT_OPTIONS=hardening=-all", "export
DEB_BUILD_MAINT_OPTIONS=hardening=-stackprotectorstrong" or "export
DEB_BUILD_MAINT_OPTIONS=hardening=-stackprotector,-relro,-pie", but
still there:

~ → xfrisk localhost
CLIENT: Connected to server.
CLIENT: Waiting for server to send client ID...Done.
[1]11208 segmentation fault (core dumped)  xfrisk localhost

The backtrace now looks as follows:

(gdb) bt
#0  CBK_IncomingMessage (iMessType=, pvMess=0x) at 
callbacks.c:327
#1  0xcfc6 in CBK_XIncomingMessage (pClientData=, 
iSource=, 
id=) at callbacks.c:97
#2  0x772fc58a in XtAppProcessEvent () from 
/usr/lib/x86_64-linux-gnu/libXt.so.6
#3  0x772f0dcd in XtAppMainLoop () from 
/usr/lib/x86_64-linux-gnu/libXt.so.6
#4  0xa28d in main (argc=2, argv=0x7fffdf38) at clientMain.c:103

Nevertheless it must be something which is part of the 1.2-4 packaging
as just recompiling xfrisk 1.2-3 under the same current environment
results in a working binary.

Will continue to dig deeper. Hints welcome, though.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#874133: xfrisk: Always crashes due to "stack smashing" on pressing "Start game"

[Adrian Bunk]

On Mon, Sep 04, 2017 at 12:59:59AM +0200, Axel Beckert wrote:
>...
> Nevertheless it must be something which is part of the 1.2-4 packaging
> as just recompiling xfrisk 1.2-3 under the same current environment
> results in a working binary.
> 
> Will continue to dig deeper. Hints welcome, though.

I'm not seeing any -O2 in the 1.2-3 build log,
so my next guess would be buggy code breaking
when compiled with optimization.

>   Regards, Axel

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#874133: xfrisk: Always crashes due to "stack smashing" on pressing "Start game"

[Axel Beckert]

Hi Adrian,

Adrian Bunk wrote:
> On Mon, Sep 04, 2017 at 12:59:59AM +0200, Axel Beckert wrote:
> > Nevertheless it must be something which is part of the 1.2-4 packaging
> > as just recompiling xfrisk 1.2-3 under the same current environment
> > results in a working binary.
> > 
> > Will continue to dig deeper. Hints welcome, though.
> 
> I'm not seeing any -O2 in the 1.2-3 build log,
> so my next guess would be buggy code breaking
> when compiled with optimization.

Hrm, the old debian/rules contained this:

CFLAGS = -Wall -g
ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS)))
CFLAGS += -O0
else
CFLAGS += -O2
endif
export CFLAGS

… so I thought that optimization shouldn't make a difference.

But since the old package didn't pass through CFLAGS properly anyway
(had to fix that in 1.2-4), that's indeed a good point. Will check,
thanks!

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#874133: xfrisk: Always crashes due to "stack smashing" on pressing "Start game"

[Axel Beckert]

Hi again,

Axel Beckert wrote:
> > I'm not seeing any -O2 in the 1.2-3 build log,
> > so my next guess would be buggy code breaking
> > when compiled with optimization.
> 
> Hrm, the old debian/rules contained this:
> 
> CFLAGS = -Wall -g
> ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS)))
> CFLAGS += -O0
> else
> CFLAGS += -O2
> endif
> export CFLAGS
> 
> … so I thought that optimization shouldn't make a difference.
> 
> But since the old package didn't pass through CFLAGS properly anyway
> (had to fix that in 1.2-4), that's indeed a good point. Will check,
> thanks!

Indeed, this line in debian/rules helps:

export DEB_CFLAGS_MAINT_APPEND=-O0

*sigh*

Thanks for the help!

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

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

[Debian Bug Tracking System]

Your message dated Sun, 03 Sep 2017 23:52:01 +
with message-id 
and subject line Bug#873599: fixed in lxqt-panel 0.11.1-4
has caused the Debian Bug report #873599,
regarding lxqt-panel FTBFS: error: ‘_explicit’ does not name a type; did you 
mean ‘explicit’?
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.)


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

Some recent change in unstable makes lxqt-panel FTBFS:

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

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

Processed: tagging 874133

[Debian Bug Tracking System]

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

> tags 874133 + pending
Bug #874133 [xfrisk] xfrisk: Always crashes due to "stack smashing" on pressing 
"Start game"
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#871136: marked as done (mousetweaks: FTBFS: UnicodeEncodeError: 'ascii' codec can't encode character '\xa9' in position 16: ordinal not in range(128))

[Debian Bug Tracking System]

Your message dated Sun, 3 Sep 2017 20:20:29 -0400
with message-id 

and subject line Re: mousetweaks: FTBFS: UnicodeEncodeError: 'ascii' codec 
can't encode
has caused the Debian Bug report #871136,
regarding mousetweaks: FTBFS: UnicodeEncodeError: 'ascii' codec can't encode 
character '\xa9' in position 16: ordinal not in range(128)
to be marked as done.

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

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


-- 
871136: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871136
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mousetweaks
Version: 3.12.0-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170805 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[3]: Entering directory '/<>/src'
> glib-mkenums --template mt-enum-types.h.template mt-common.h > xgen-gtbh \
> && (cmp -s xgen-gtbh mt-enum-types.h || cp xgen-gtbh mt-enum-types.h) \
> && rm -f xgen-gtbh \
> && echo timestamp > stamp-mt-enum-types.h
> Traceback (most recent call last):
>   File "/usr/bin/glib-mkenums", line 394, in 
> write_output(prod)
>   File "/usr/bin/glib-mkenums", line 73, in write_output
> print(output, file=output_stream)
> UnicodeEncodeError: 'ascii' codec can't encode character '\xa9' in position 
> 16: ordinal not in range(128)
> Makefile:841: recipe for target 'stamp-mt-enum-types.h' failed
> make[3]: *** [stamp-mt-enum-types.h] Error 1

The full build log is available from:
   http://aws-logs.debian.net/2017/08/05/mousetweaks_3.12.0-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 ---
mousetweaks builds fine for me now in unstable.

I assume this issue was fixed by a newer glib2.0 upload.

Thanks,
Jeremy Bicha--- End Message ---

Bug#864162: marked as done (opendkim: systemd ExecStart ignore configuration options)

[Debian Bug Tracking System]

Your message dated Mon, 04 Sep 2017 00:49:50 +
with message-id 
and subject line Bug#864162: fixed in opendkim 2.11.0~alpha-11
has caused the Debian Bug report #864162,
regarding opendkim: systemd ExecStart ignore configuration options
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.)


-- 
864162: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864162
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: opendkim
Version: 2.11.0~alpha-10
Severity: important

Dear Maintainer,

I was unable to make opendkim listening on the 12301 port.

It appears that the ExecStart in
/etc/systemd/system/multi-user.target.wants/opendkim.service
ignore configuration options.

I fixed it locally by defining
ExecStart=/usr/sbin/opendkim -P /var/run/opendkim/opendkim.pid -p $(awk '$1 == 
"Socket" { print $2 }' /etc/opendkim.conf)
(inspired by init script).

François

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

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

Versions of packages opendkim depends on:
ii  adduser  3.115
ii  dns-root-data2017041101
ii  init-system-helpers  1.48
ii  libbsd0  0.8.3-1
ii  libc62.24-10
ii  libdb5.3 5.3.28-12+b1
ii  libldap-2.4-22.4.44+dfsg-5
ii  liblua5.1-0  5.1.5-8.1+b2
ii  libmemcached11   1.0.18-4.1
ii  libmemcachedutil21.0.18-4.1
ii  libmilter1.0.1   8.15.2-8
ii  libopendbx1  1.4.6-11+b1
ii  libopendkim112.11.0~alpha-10
ii  librbl1  2.11.0~alpha-10
ii  libssl1.11.1.0e-2
ii  libunbound2  1.6.0-3
ii  libvbr2  2.11.0~alpha-10
ii  lsb-base 9.20161125

opendkim recommends no packages.

Versions of packages opendkim suggests:
ii  opendkim-tools  2.11.0~alpha-10
pn  unbound 

-- Configuration Files:
/etc/default/opendkim changed:
RUNDIR=/var/run/opendkim
SOCKET=inet:12301@localhost
USER=opendkim
GROUP=opendkim
PIDFILE=$RUNDIR/$NAME.pid
EXTRAAFTER=

/etc/opendkim.conf changed:
Syslog  yes
UMask   007
Modesv
OversignHeaders From
TrustAnchorFile   /usr/share/dns/root.key
AutoRestart Yes
AutoRestartRate 10/1h
UMask   002
Syslog  yes
SyslogSuccess   Yes
LogWhy  Yes
Canonicalizationrelaxed/simple
KeyTable/etc/postfix/dkim/keytable
SigningTable/etc/postfix/dkim/signingtable 
ExternalIgnoreList  /etc/postfix/dkim/TrustedHosts
InternalHosts   /etc/postfix/dkim/TrustedHosts
Modesv
PidFile /var/run/opendkim/opendkim.pid
SignatureAlgorithm  rsa-sha256
UserID  opendkim:opendkim
Socket  inet:12301@localhost


-- no debconf information
--- End Message ---
--- Begin Message ---
Source: opendkim
Source-Version: 2.11.0~alpha-11

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

Debian distribution maintenance software
pp.
Scott Kitterman  (supplier of updated opendkim package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 03 Sep 2017 20:22:45 -0400
Source: opendkim
Binary: opendkim opendkim-tools libopendkim11 libopendkim-dev libvbr2 
libvbr-dev librbl1 librbl-dev
Architecture: source amd64
Version: 2.11.0~alpha-11
Distribution: unstable
Urgency: medium
Maintainer: Scott Kitterman 
Changed-By: Scott Kitterman 
Description:
 libopendkim-dev - Headers and development libraries for the OpenDKIM library
 libopendkim11 - Library for signing and verifying DomainKeys Identified Mail 
sign
 librbl-dev - Headers/development libraries for the OpenDKIM RBL library
 librbl1- Library to support a DKIM based RBL system
 libvbr-dev - Headers and development libraries for the OpenDKIM VBR library

Bug#866654: marked as done (typecatcher: depends on libwebkitgtk-3.0-0 which is deprecated)

[Debian Bug Tracking System]

Your message dated Mon, 04 Sep 2017 01:19:27 +
with message-id 
and subject line Bug#866654: fixed in typecatcher 0.3-1
has caused the Debian Bug report #866654,
regarding typecatcher: 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.)


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

Hi,

typecatcher 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 ---
Source: typecatcher
Source-Version: 0.3-1

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

Debian distribution maintenance software
pp.
Andrew Starr-Bochicchio  (supplier of updated typecatcher 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 03 Sep 2017 20:48:32 -0400
Source: typecatcher
Binary: typecatcher
Architecture: source all
Version: 0.3-1
Distribution: unstable
Urgency: medium
Maintainer: Andrew Starr-Bochicchio 
Changed-By: Andrew Starr-Bochicchio 
Description:
 typecatcher - Download Google webfonts for off-line use
Closes: 820386 866654
Changes:
 typecatcher (0.3-1) unstable; urgency=medium
 .
   * New upstream release.
- Port to gir1.2-webkit2-4.0 (Closes: #866654).
   * Add debian/watch file.
   * debian/control:
- Depend on gir1.2-webkit2-4.0 and drop gir1.2-webkit-3.0.
- "Extra" priority has been deprecated; now "optional."
- Move to "fonts" section (Closes: #820386).
- Bump Standards-Version to 4.1.0.
   * Bump debian/compat to 10.
Checksums-Sha1:
 00cd6ee90b19f58f92a41036ec2b9f23114dcf1d 1940 typecatcher_0.3-1.dsc
 45b4e656be871afcb7a764f99722b94059412c88 122424 typecatcher_0.3.orig.tar.gz
 2394f348735ba9f834de3890c783431a0851fa88 9156 typecatcher_0.3-1.debian.tar.xz
 ca208626eae785387f5063f9e96d4306b3dda6e9 94504 typecatcher_0.3-1_all.deb
 c362ee81f1c8bd8d802091e8e5133d3bff1427e5 9930 typecatcher_0.3-1_amd64.buildinfo
Checksums-Sha256:
 259c426102b4ccab995f26c937337327517b9a444b13bb36cd88b2cbcd27a1d4 1940 
typecatcher_0.3-1.dsc
 1328a54021d0c575f7e4c4f7331c33cfff361861b065278998f0a186aa92c7b3 122424 
typecatcher_0.3.orig.tar.gz
 fd672133e4f050d774b8f0f1c8121f65cb79db4094c868aa4165d5fbc5e58b41 9156 
typecatcher_0.3-1.debian.tar.xz
 c1c001a109f3070ffaae80e4db870991510a2179cca049c3004f4e98fa776b9c 94504 
typecatcher_0.3-1_all.deb
 078c8e4f317d1b4ac77d05718fad7c546a13ce27d14ed1046e2386f189c9e5f0 9930 
typecatcher_0.3-1_amd64.buildinfo
Files:
 6e18cf9d55352c8684125c4a144966ca 1940 fonts optional typecatcher_0.3-1.dsc
 756172605eec2231bebb93b3fc385cca 122424 fonts optional 
typecatcher_0.3.orig.tar.gz
 90283d4fc43ab049a1121f6fc9e891a7 9156 fonts optional 
typecatcher_0.3-1.debian.tar.xz
 aa257130da76da462fa2a745efd9bc03 94504 fonts optional typecatcher_0.3-1_all.deb
 d92032c7a8e86d0b8dec86c07cc403e8 9930 fonts optional 
typecatcher_0.3-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJZrKQFAAoJEDtW4rvVP9yxK8AP/jAMdLPjLCzeSaqHR8buT+S9
EwNOgLZ0VdLgJ1YXcRha+aQ/MoOmvKPVGv9EYPQb5XQdu2GwmyPLn5bQDvblTU+w
mq1mJx9tjmZUVOA2iZDIpnNTxPV5DCDZscFF2IGSzKNcvkK+ntLyv+9qBQce5iCS
1mBnOtdIXFLGi/BbMHwn33D4QuGE2gdxTX3XuKIBKjf2JqSqbR4UrPbZz7Xln0uO
LGx1duQsnbciIlMmZGrz41cVfYzt4sCBFDiSRgZOAxIotWDbxAMIvppFXqS7fU2z
HGecTVBhuefrkHaBDelChGQdWxQ2OUvbnizQIrr9vx2wOhh6PQTkFfGRk2q60wWU
tyVa6iXbHZcmBViJupfCcfFbGR+i5jwzE6w+uE0iE1WG0e3rPYUYnF02dB6WrdWa

Bug#870742: marked as done (libgnome FTBFS with glib 2.53.4)

[Debian Bug Tracking System]

Your message dated Mon, 04 Sep 2017 01:49:39 +
with message-id 
and subject line Bug#870742: fixed in libgnome 2.32.1-6
has caused the Debian Bug report #870742,
regarding libgnome FTBFS with glib 2.53.4
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.)


-- 
870742: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870742
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgnome
Version: 2.32.1-5
Severity: serious
Tags: patch buster sid

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

...
Making all in libgnome
make[3]: Entering directory '/build/1st/libgnome-2.32.1/libgnome'
(cd . \
&& glib-mkenums \
--fhead "#ifndef __LIBGNOMETYPEBUILTINS_H__\n" \
--fhead "#define __LIBGNOMETYPEBUILTINS_H__ 1\n\n" \
--fhead "#include \n\n" \
--fhead "G_BEGIN_DECLS\n\n" \
--ftail "G_END_DECLS\n\n" \
--ftail "#endif /* __LIBGNOMETYPEBUILTINS_H__ */\n" \
--fprod "\n/* --- @filename@ --- */" \
--eprod "#define GNOME_TYPE_@ENUMSHORT@ 
@enum_name@_get_type()\n" \
--eprod "GType @enum_name@_get_type (void);\n" \
gnome-config.h gnome-sound.h gnome-triggers.h gnome-program.h 
gnome-help.h gnome-i18n.h gnome-exec.h gnome-gconf.h gnome-url.h gnome-util.h 
gnome-macros.h gnome-score.h gnome-init.h libgnome.h ) > xgen-gth \
&& (cmp -s xgen-gth libgnometypebuiltins.h || cp xgen-gth 
libgnometypebuiltins.h) \
&& rm -f xgen-gth \
&& echo timestamp > stamp-libgnometypebuiltins.h
Traceback (most recent call last):
  File "/usr/bin/glib-mkenums", line 675, in 
process_file(fname)
  File "/usr/bin/glib-mkenums", line 407, in process_file
line = curfile.readline()
  File "/usr/lib/python3.5/codecs.py", line 321, in decode
(result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xa0 in position 3214: 
invalid start byte
Makefile:936: recipe for target 'stamp-libgnometypebuiltins.h' failed
make[3]: *** [stamp-libgnometypebuiltins.h] Error 1


A fix is attached.
Description: Fix FTBFS with glib 2.54
 glib-mkenums now expects input files to be UTF-8,
 fix the encoding of libgnome/gnome-config.h
Author: Adrian Bunk 

--- libgnome-2.32.1.orig/libgnome/gnome-config.h
+++ libgnome-2.32.1/libgnome/gnome-config.h
@@ -270,7 +270,7 @@ void gnome_config_clean_key_ (const char
 #define gnome_config_private_clean_key(path) \
 	(gnome_config_clean_key_((path),TRUE))
 
-/* returns the true filename of the config file */
+/* returns the true filename of the config file */
 #define gnome_config_get_real_path(path) \
 	(g_build_filename (gnome_user_dir_get(),(path),NULL))
 #define gnome_config_private_get_real_path(path) \
--- End Message ---
--- Begin Message ---
Source: libgnome
Source-Version: 2.32.1-6

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 03 Sep 2017 21:28:35 -0400
Source: libgnome
Binary: libgnome2-0 libgnome2-bin libgnome-2-0 libgnome2-dev libgnome2-common 
libgnome2-doc
Architecture: source
Version: 2.32.1-6
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bicha 
Description:
 libgnome-2-0 - Deprecated GNOME 2 library - runtime files
 libgnome2-0 - Deprecated GNOME 2 library - transition package
 libgnome2-bin - Deprecated GNOME 2 library - binary files
 libgnome2-common - Deprecated GNOME 2 library - common files
 libgnome2-dev - Deprecated GNOME 2 library - development files
 libgnome2-doc - Deprecated GNOME 2 library - documentation files
Closes: 870742
Changes:
 libgnome (2.32.1-6) unstable; urgency=medium
 .
   * Cherry-pick 05_fix_invalid_utf8.patch to fix build with latest glib2.0
 (Closes: #870742)
   * Modernize packaging:
 - Convert to dh
 - Bump debhelper compat to 10
   

Bug#870749: marked as done (glade FTBFS with glib 2.53.4)

[Debian Bug Tracking System]

Your message dated Mon, 04 Sep 2017 03:05:27 +
with message-id 
and subject line Bug#870749: fixed in glade 3.20.0-3
has caused the Debian Bug report #870749,
regarding glade FTBFS with glib 2.53.4
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.)


-- 
870749: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870749
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glade
Version: 3.20.0-2
Severity: serious
Tags: patch buster sid

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

...
glade-signal-model.c:68:1: error: conflicting types for 'g_ptr_array_find'
 g_ptr_array_find (GPtrArray *array, gpointer data)
 ^~~~
In file included from /usr/include/glib-2.0/glib.h:31:0,
 from /usr/include/glib-2.0/gobject/gbinding.h:28,
 from /usr/include/glib-2.0/glib-object.h:23,
 from glade-signal-model.h:23,
 from glade-signal-model.c:23:
/usr/include/glib-2.0/glib/garray.h:186:12: note: previous declaration of 
'g_ptr_array_find' was here
 gboolean   g_ptr_array_find   (GPtrArray*haystack,
^~~~
Makefile:1210: recipe for target 'libgladeui_2_la-glade-signal-model.lo' failed
make[4]: *** [libgladeui_2_la-glade-signal-model.lo] Error 1


The upstream fix is attached.
>From 8a73d114ca5b4d37a770d0b6b69dd17a366dbcf4 Mon Sep 17 00:00:00 2001
From: Jonh Wendell 
Date: Thu, 4 May 2017 11:05:48 -0300
Subject: Use g_ptr_array_find() from GLib

https://bugzilla.gnome.org/show_bug.cgi?id=782161
---
 configure.ac |  2 ++
 gladeui/glade-signal-model.c | 30 ++
 2 files changed, 12 insertions(+), 20 deletions(-)

diff --git a/configure.ac b/configure.ac
index ac59f096..db7487ef 100644
--- a/configure.ac
+++ b/configure.ac
@@ -146,8 +146,10 @@ dnl 

 dnl Check for gtk+
 dnl 
 GTK_REQUIRED=3.20.0
+GLIB_REQUIRED=2.53.2
 PKG_CHECK_MODULES([GTK],[
   gtk+-3.0 >= $GTK_REQUIRED
+  glib-2.0 >= $GLIB_REQUIRED
   gmodule-2.0
   libxml-2.0 >= 2.4.0
 ])
diff --git a/gladeui/glade-signal-model.c b/gladeui/glade-signal-model.c
index 2b383e51..4d1a8a40 100644
--- a/gladeui/glade-signal-model.c
+++ b/gladeui/glade-signal-model.c
@@ -64,18 +64,6 @@ G_DEFINE_TYPE_WITH_CODE (GladeSignalModel, 
glade_signal_model, G_TYPE_OBJECT,
  G_IMPLEMENT_INTERFACE (GTK_TYPE_TREE_DRAG_SOURCE,
 
gtk_tree_drag_source_iface_init))
 
-static gint
-g_ptr_array_find (GPtrArray *array, gpointer data)
-{
-  gint i;
-  for (i = 0; i < array->len; i++)
-{
-  if (array->pdata[i] == data)
-   return i;
-}
-  return -1;
-}
-
 static void
 glade_signal_model_init (GladeSignalModel *object)
 {
@@ -524,13 +512,11 @@ glade_signal_model_get_path (GtkTreeModel *model, 
GtkTreeIter *iter)
{
  if (handlers)
{
- gint handler_index = g_ptr_array_find (handlers, handler);
- if (handler_index == -1) /* dummy handler */
-   {
- index1 += handlers->len;
-   }
- else
+ guint handler_index;
+ if (g_ptr_array_find (handlers, handler, &handler_index))
index1 += handler_index;
+ else
+   index1 += handlers->len;
}
  break;
}
@@ -582,7 +568,8 @@ glade_signal_model_get_value (GtkTreeModel *model,
 {
   GPtrArray *handlers = g_hash_table_lookup (sig_model->priv->signals,
  glade_signal_get_name 
(signal));
-  if (!handlers || !handlers->len || g_ptr_array_find (handlers, 
signal) == 0)
+  guint index;
+  if (!handlers || !handlers->len || (g_ptr_array_find (handlers, 
signal, &index) && index == 0))
 g_value_set_boolean (value, TRUE);
   else
 g_value_set_boolean (value, FALSE);
@@ -718,7 +705,10 @@ glade_signal_model_iter_next (GtkTreeModel *model, 
GtkTreeIter *iter)
}
   else if (handlers)
{
- gint new_index = g_ptr_array_find (handlers, handler) + 1;
+ guint new_index = 0;
+ if (g_ptr_array_find (handlers, handler, &new_index))
+   new_index++;
+
  if (new_index < handlers->len)
{
  glade_signal_model_create_si

Bug#874133: marked as done (xfrisk: Always crashes due to "stack smashing" on pressing "Start game")

[Debian Bug Tracking System]

Your message dated Mon, 04 Sep 2017 03:13:38 +
with message-id 
and subject line Bug#874133: fixed in xfrisk 1.2-5
has caused the Debian Bug report #874133,
regarding xfrisk: Always crashes due to "stack smashing" on pressing "Start 
game"
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.)


-- 
874133: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874133
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xfrisk
Version: 1.2-4
Severity: grave

xfrisk (initially started via "risk") always crashes as follows for me
if I click the "Start game" button or if I later call "xfrisk localhost"
with the server already running. The following crash is from the latter
case:

~ → xfrisk localhost
CLIENT: Connected to server.
CLIENT: Waiting for server to send client ID...Done.
*** stack smashing detected ***: xfrisk terminated
=== Backtrace: =
/lib/x86_64-linux-gnu/libc.so.6(+0x70bfb)[0x7f35b3a6abfb]
/lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x37)[0x7f35b3af31e7]
/lib/x86_64-linux-gnu/libc.so.6(__fortify_fail+0x0)[0x7f35b3af31b0]
xfrisk(+0x8652)[0x55ac99edc652]
xfrisk(+0x8aea)[0x55ac99edcaea]
xfrisk(+0x8dc6)[0x55ac99edcdc6]
/usr/lib/x86_64-linux-gnu/libXt.so.6(XtAppProcessEvent+0x17a)[0x7f35b452a58a]
/usr/lib/x86_64-linux-gnu/libXt.so.6(XtAppMainLoop+0x2d)[0x7f35b451edcd]
xfrisk(+0x5f4d)[0x55ac99ed9f4d]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)[0x7f35b3a1a2e1]
xfrisk(+0x5faa)[0x55ac99ed9faa]
=== Memory map: 
55ac99ed4000-55ac99ef6000 r-xp  fd:01 537517 
/usr/games/xfrisk
55ac9a0f6000-55ac9a0f8000 r--p 00022000 fd:01 537517 
/usr/games/xfrisk
55ac9a0f8000-55ac9a0fb000 rw-p 00024000 fd:01 537517 
/usr/games/xfrisk
55ac9a0fb000-55ac9a0fe000 rw-p  00:00 0 
55ac9bacf000-55ac9bb75000 rw-p  00:00 0  [heap]
7f35b1d2f000-7f35b1d45000 r-xp  fd:01 288120 
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f35b1d45000-7f35b1f44000 ---p 00016000 fd:01 288120 
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f35b1f44000-7f35b1f45000 r--p 00015000 fd:01 288120 
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f35b1f45000-7f35b1f46000 rw-p 00016000 fd:01 288120 
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f35b1f46000-7f35b1f4b000 r-xp  fd:01 529359 
/usr/lib/x86_64-linux-gnu/libXfixes.so.3.1.0
7f35b1f4b000-7f35b214a000 ---p 5000 fd:01 529359 
/usr/lib/x86_64-linux-gnu/libXfixes.so.3.1.0
7f35b214a000-7f35b214b000 r--p 4000 fd:01 529359 
/usr/lib/x86_64-linux-gnu/libXfixes.so.3.1.0
7f35b214b000-7f35b214c000 rw-p 5000 fd:01 529359 
/usr/lib/x86_64-linux-gnu/libXfixes.so.3.1.0
7f35b214c000-7f35b2155000 r-xp  fd:01 561244 
/usr/lib/x86_64-linux-gnu/libXrender.so.1.3.0
7f35b2155000-7f35b2354000 ---p 9000 fd:01 561244 
/usr/lib/x86_64-linux-gnu/libXrender.so.1.3.0
7f35b2354000-7f35b2355000 r--p 8000 fd:01 561244 
/usr/lib/x86_64-linux-gnu/libXrender.so.1.3.0
7f35b2355000-7f35b2356000 rw-p 9000 fd:01 561244 
/usr/lib/x86_64-linux-gnu/libXrender.so.1.3.0
7f35b2356000-7f35b235f000 r-xp  fd:01 524345 
/usr/lib/x86_64-linux-gnu/libXcursor.so.1.0.2
7f35b235f000-7f35b255f000 ---p 9000 fd:01 524345 
/usr/lib/x86_64-linux-gnu/libXcursor.so.1.0.2
7f35b255f000-7f35b256 r--p 9000 fd:01 524345 
/usr/lib/x86_64-linux-gnu/libXcursor.so.1.0.2
7f35b256-7f35b2561000 rw-p a000 fd:01 524345 
/usr/lib/x86_64-linux-gnu/libXcursor.so.1.0.2
7f35b2561000-7f35b256b000 r-xp  fd:01 264439 
/lib/x86_64-linux-gnu/libnss_files-2.24.so
7f35b256b000-7f35b276b000 ---p a000 fd:01 264439 
/lib/x86_64-linux-gnu/libnss_files-2.24.so
7f35b276b000-7f35b276c000 r--p a000 fd:01 264439 
/lib/x86_64-linux-gnu/libnss_files-2.24.so
7f35b276c000-7f35b276d000 rw-p b000 fd:01 264439 
/lib/x86_64-linux-gnu/libnss_files-2.24.so
7f35b276d000-7f35b2773000 rw-p  00:00 0 
7f35b2773000-7f35b2778000 r-xp  fd:01 529447 
/usr/lib/x86_64-linux-gnu/libXdmcp.so.6.0.0
7f35b2778000-7f35b2977000 ---p 5000 fd:01 529447 
/usr/lib/x86_64-linux-gnu/libXdmcp.so.6.0.0
7f35b2977000-7f35b2978000 r--p 4000 fd:01 529447