Bug#865822: mutt: Enter key disabled with latest upgrade

[Jamie Heilman]

> It behaves like all the sane compile time defaults were replaced
> with something unusable.

I was able to restore most functionality by running mutt -D with
1.8.0, and then again with 1.8.3 and then sourcing a file that
restores all the settings I lost.  Hopefully that helps somebody else
who's trying to figure out all the regressions this version
introduced.

-- 
Jamie Heilman http://audible.transient.net/~jamie/

Bug#865796: marked as done (ginkgocadx FTBFS with libdcmtk-dev 3.6.1~20170228-2)

[Debian Bug Tracking System]

Your message dated Sun, 25 Jun 2017 06:33:49 +
with message-id 
and subject line Bug#865796: fixed in ginkgocadx 3.8.5-1
has caused the Debian Bug report #865796,
regarding ginkgocadx FTBFS with libdcmtk-dev 3.6.1~20170228-2
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.)


-- 
865796: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865796
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ginkgocadx
Version: 3.8.4-1
Severity: serious
Tags: buster sid

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

...
cd /<>/obj-x86_64-linux-gnu/cadxcore && /usr/bin/c++   -DAPIEXPORT 
-DCURL_STATICLIB -DGINKGO_ARCH_x86_64 -DGINKGO_CODENAME=\"\" 
-DGINKGO_VERSION=\"3.8.4\" -DHAVE_CONFIG_H -DINTERNET_DIST 
-DITK_IO_FACTORY_REGISTER_MANAGER -DLINUX -DMONOLITIC -DUSE_SYSTEM_SQLITE 
-DUSING_EXTENSIONS -DWXUSINGDLL -D_FILE_OFFSET_BITS=64 -D__WXGTK__ 
-DvtkFiltersFlowPaths_AUTOINIT="1(vtkFiltersParallelFlowPaths)" 
-DvtkIOExodus_AUTOINIT="1(vtkIOParallelExodus)" 
-DvtkIOGeometry_AUTOINIT="1(vtkIOMPIParallel)" 
-DvtkIOImage_AUTOINIT="1(vtkIOMPIImage)" 
-DvtkIOParallel_AUTOINIT="1(vtkIOMPIParallel)" 
-DvtkIOSQL_AUTOINIT="2(vtkIOMySQL,vtkIOPostgreSQL)" 
-DvtkRenderingContext2D_AUTOINIT="1(vtkRenderingContextOpenGL)" 
-DvtkRenderingCore_AUTOINIT="3(vtkInteractionStyle,vtkRenderingFreeType,vtkRenderingOpenGL)"
 
-DvtkRenderingFreeType_AUTOINIT="2(vtkRenderingFreeTypeFontConfig,vtkRenderingMatplotlib)"
 -DvtkRenderingLIC_AUTOINIT="1(vtkRenderingParallelLIC)" 
-DvtkRenderingVolume_AUTOINIT="1(vtkRenderingVolumeOpe
 nGL)" 
-I/<>/obj-x86_64-linux-gnu/cadxcore/ITKIOFactoryRegistration 
-I/usr/include/gdcm-2.6 -isystem /usr/include/ITK-4.10 -I/usr/include/cairo 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include 
-I/usr/include/gio-unix-2.0 -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/harfbuzz 
-I/usr/include/x86_64-linux-gnu -I/<>/cadxcore/CADxCore 
-I/<>/cadxcore -I/<>/cadxcore/vtk 
-I/<>/cadxcore/itk -I/<>/cadxcore/wx 
-I/<>/cadxcore/wx/VTK -I/<>/cadxcore/VTKInria3D 
-I/<>/cadxcore/VTKInria3D/wxVTK -I/usr/include/jsoncpp 
-I/<>/../lib/Linux-x86_64/libcurl-7.28.1/include 
-I/usr/lib/x86_64-linux-gnu/wx/include/gtk2-unicode-3.0 -I/usr/include/wx-3.0 
-I/usr/include/vtk-6.3 -I/us
 r/lib/x86_64-linux-gnu/openmpi/include/openmpi 
-I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi/opal/mca/event/libevent2022/libevent
 
-I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi/opal/mca/event/libevent2022/libevent/include
 -I/usr/lib/x86_64-linux-gnu/openmpi/include -I/usr/include/python2.7 
-I/usr/include/hdf5/openmpi -I/usr/include/libxml2 -I/usr/include/tcl 
-I/usr/lib/i386-linux-gnu/glib-2.0/include -I/usr/include/libpng12 
-I/usr/lib/gtk-2.0/include  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -DNDEBUG -fPIC  -std=c++11 -o 
CMakeFiles/CADxCore.dir/api/dicom/icustomassociation.cpp.o -c 
/<>/cadxcore/api/dicom/icustomassociation.cpp
[ 11%] Building CXX object 
cadxcore/CMakeFiles/CADxCore.dir/api/dicom/idicom.cpp.o
cd /<>/obj-x86_64-linux-gnu/cadxcore && /usr/bin/c++   -DAPIEXPORT 
-DCURL_STATICLIB -DGINKGO_ARCH_x86_64 -DGINKGO_CODENAME=\"\" 
-DGINKGO_VERSION=\"3.8.4\" -DHAVE_CONFIG_H -DINTERNET_DIST 
-DITK_IO_FACTORY_REGISTER_MANAGER -DLINUX -DMONOLITIC -DUSE_SYSTEM_SQLITE 
-DUSING_EXTENSIONS -DWXUSINGDLL -D_FILE_OFFSET_BITS=64 -D__WXGTK__ 
-DvtkFiltersFlowPaths_AUTOINIT="1(vtkFiltersParallelFlowPaths)" 
-DvtkIOExodus_AUTOINIT="1(vtkIOParallelExodus)" 
-DvtkIOGeometry_AUTOINIT="1(vtkIOMPIParallel)" 
-DvtkIOImage_AUTOINIT="1(vtkIOMPIImage)" 
-DvtkIOParallel_AUTOINIT="1(vtkIOMPIParallel)" 
-DvtkIOSQL_AUTOINIT="2(vtkIOMySQL,vtkIOPostgreSQL)" 
-DvtkRenderingContext2D_AUTOINIT="1(vtkRenderingContextOpenGL)" 
-DvtkRenderingCore_AUTOINIT="3(vtkInteractionStyle,vtkRenderingFreeType,vtkRenderingOpenGL)"
 
-DvtkRenderingFreeType_AUTOINIT="2(vtkRenderingFreeTypeFontConfig,vtkRenderingMatplotlib)"
 -DvtkRenderingLIC_AUTOINIT="1(vtkRenderingParallelLIC)" 
-DvtkRenderingVolume_AUTOINIT="1(vtkRenderingVolumeOpe
 nGL)" 
-I/<>/obj-x86_64-linux-gnu/cadxcore/ITKIOFactoryRegistration 
-I/usr/include/gdcm-2.6 -isystem /usr/include/ITK-4.10 -I/usr/include/cairo 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/gtk-2.0 -I/usr/

Bug#830902: openBVE doesn't start

[Petter Reinholdtsen]

I also see the same behavior.  I tried to debug it, but have no idea how to
debug mono applications.

-- 
Happy hacking
Petter Reinholdtsen

Bug#865822: mutt: Enter key disabled with latest upgrade

[Jamie Heilman]

It goes beyond just the tmpdir setting; for those of us who start our
mutt configs with "reset all" we wind up with a more or less unusable
mail client.  In my case it screwed up decoding my aliases with
"Warning: Bad IDN" for every single alias I had, ment that I didn't
start in my inbox as defined by my $MAIL environment variable, and
couldn't decode html email despite having set a tmpdir ... and so
forth.  It behaves like all the sane compile time defaults were
replaced with something unusable.

-- 
Jamie Heilman http://audible.transient.net/~jamie/

Bug#865577: cloud-init FTBFS: recipe for target 'pep8' failed

[Joonas Kylmälä]

Hey.

As there has not been yet a new release of the upstream package (current
one is 0.7.9) to which we could upgrade, I decided to create a patch
specifically for Debian. See it attached. The patch is pretty much the
same as Joshua Powers' upstream one. The only difference is the usage of
httplib instead of hclient.

Thanks,
Joonas Kylmälä
>From 8afb8941e696b74ca03a7c80e15eed320e1b8e72 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Joonas=20Kylm=C3=A4l=C3=A4?= 
Date: Sun, 25 Jun 2017 07:42:13 +0200
Subject: [PATCH] Fix Python code style errors (Closes #865577)

This commit is based on Joshua Powers' upstream commit
with hash 5f14a0b1ca3079e4ab43d615840866a4b7d8df6a
(code-style: make master pass pycodestyle (2.3.1) cleanly).
---
 tools/make-mime.py | 2 +-
 tools/mock-meta.py | 5 -
 2 files changed, 5 insertions(+), 2 deletions(-)

diff --git a/tools/make-mime.py b/tools/make-mime.py
index 12727126..f6a72044 100755
--- a/tools/make-mime.py
+++ b/tools/make-mime.py
@@ -22,7 +22,7 @@ def file_content_type(text):
 try:
 filename, content_type = text.split(":", 1)
 return (open(filename, 'r'), filename, content_type.strip())
-except:
+except ValueError:
 raise argparse.ArgumentError("Invalid value for %r" % (text))
 
 
diff --git a/tools/mock-meta.py b/tools/mock-meta.py
index d74f9e31..2165d623 100755
--- a/tools/mock-meta.py
+++ b/tools/mock-meta.py
@@ -249,7 +249,10 @@ class MetaDataHandler(object):
 try:
 key_id = int(mybe_key)
 key_name = key_ids[key_id]
-except:
+except ValueError:
+raise WebException(httplib.BAD_REQUEST,
+   "%s: not an integer" % mybe_key)
+except KeyError:
 raise WebException(httplib.BAD_REQUEST,
"Unknown key id %r" % mybe_key)
 # Extract the possible sub-params
-- 
2.11.0

Bug#865556: marked as done (django-guardian FTBFS with Django 1.11)

[Debian Bug Tracking System]

Your message dated Sun, 25 Jun 2017 03:49:19 +
with message-id 
and subject line Bug#865556: fixed in django-guardian 1.4.8-1
has caused the Debian Bug report #865556,
regarding django-guardian FTBFS with Django 1.11
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.)


-- 
865556: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865556
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: django-guardian
Version: 1.4.4-1
Severity: serious
Tags: buster sid

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

...
# Build the HTML documentation.
cd /build/1st/django-guardian-1.4.4/docs/ && make html 
make[2]: Entering directory '/build/1st/django-guardian-1.4.4/docs'
sphinx-build -b html -d build/doctrees   . build/html
Running Sphinx v1.4.9
making output directory...

Exception occurred:
  File "/usr/lib/python3/dist-packages/django/contrib/auth/__init__.py", line 
198, in get_user_model
"AUTH_USER_MODEL refers to model '%s' that has not been installed" % 
settings.AUTH_USER_MODEL
django.core.exceptions.ImproperlyConfigured: AUTH_USER_MODEL refers to model 
'testapp.CustomUser' that has not been installed
The full traceback has been saved in /tmp/sphinx-err-11l3ttgc.log, if you want 
to report the issue to the developers.
Please also report this if it was a user error, so that a better error message 
can be provided next time.
A bug report can be filed in the tracker at 
. Thanks!
Makefile:35: recipe for target 'html' failed
make[2]: *** [html] Error 1
make[2]: Leaving directory '/build/1st/django-guardian-1.4.4/docs'
debian/rules:10: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
--- End Message ---
--- Begin Message ---
Source: django-guardian
Source-Version: 1.4.8-1

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

Debian distribution maintenance software
pp.
Brian May  (supplier of updated django-guardian 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, 25 Jun 2017 13:28:33 +1000
Source: django-guardian
Binary: python-django-guardian python3-django-guardian 
python-django-guardian-doc
Architecture: source all
Version: 1.4.8-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Brian May 
Description:
 python-django-guardian - per object permissions of django
 python-django-guardian-doc - per object permissions of django (documentation)
 python3-django-guardian - per object permissions of django for Python3
Closes: 865556
Changes:
 django-guardian (1.4.8-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Depend on newer dh-python which sets SETUPTOOLS_SCM_PRETEND_VERSION
   * wrap-and-sort -t -a
   * Bumped debhelper compat version to 9
   * Standards-Version is 3.9.8 now (no changes needed)
   * d/copyright: Removed licence for absent files
 .
   [ Brian May ]
   * New upstream version. Closes: #865556.
   * Refresh patches after git-dpm to gbp pq conversion
Checksums-Sha1:
 ed18a6ce912db1393c0fc842fe179b2ec47bb9dc 2667 django-guardian_1.4.8-1.dsc
 b89dadd9df4923fff2667094f04cd6da38553951 151805 
django-guardian_1.4.8.orig.tar.gz
 4e6f137a6ab08259ada2d8dca8427c540768a97f 34888 
django-guardian_1.4.8-1.debian.tar.xz
 733366193cec5ac92ae7ccadf10b380da085c6f6 8573 
django-guardian_1.4.8-1_i386.buildinfo
 9485d7623eec25478a267e48cbd31b08c3d7ce44 1374194 
python-django-guardian-doc_1.4.8-1_all.deb
 0a1d708d6efa01e4d40d141a72131c60584964e7 61564 
python-django-guardian_1.4.8-1_all.deb
 cf90d667f603d56216ac7782e2366a4b27d506c2 60202 
python3-django-guardian_1.4.8-1_all.deb
Checksums-Sha256:
 bc176d2aa5075dab48b436cd78127c04f2d1e753ed606756f64b8a474da22c59 2667 
django-guardian_1.4.8-1.dsc
 353794b2f685c588e44583e18dcc2bf5fc33b0870a344ab7a1bb00764877350d 151805 
django-guardian_1.4.8.orig.tar.gz
 04befbd7d13fdf51d4d7edc0c16d179480da86b6d110ef0610455dfe2c3f13bb 34888 
django-guardian_1.4.8-1.debian.tar.xz
 62857c59111f820e3de1b

Bug#865711: haskell-yaml: FTBFS everywhere (except all)

[Gianfranco Costamagna]

Hello,

>I don't know what we should do here.  The behavior of the embedded
>libyaml differs from our libyaml and I'm not sure why, but it appears

>to be on purpose.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865675
because the embedded yaml is more up-to-date wrt the Debian one, and for
this reason I opened a bug report.

Patching yaml in Ubuntu made the whole stuff migrate, however seems that
some unintended side-effects are possible, according to pyyaml regressions
on i386.

https://github.com/snoyberg/yaml/issues/110

G.

Processed: tagging 864719

[Debian Bug Tracking System]

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

> tags 864719 + pending
Bug #864719 [slapd] slapd: fails to configure when olcSuffix contains a 
backslash-escaped umlaut
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#865556: marked as pending

[Brian May]

tag 865556 pending
thanks

Hello,

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


https://anonscm.debian.org/cgit/python-modules/packages/django-guardian.git/commit/?id=3d3c4a8

---
commit 3d3c4a83f34747c3ca14dba4f1d71329f40ad24e
Author: Brian May 
Date:   Sun Jun 25 13:14:22 2017 +1000

Update changelog for 1.4.8-1

diff --git a/debian/changelog b/debian/changelog
index f947d8e..fed99d6 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,13 +1,17 @@
-django-guardian (1.4.4-2) UNRELEASED; urgency=medium
+django-guardian (1.4.8-1) UNRELEASED; urgency=medium
 
+  [ Ondřej Nový ]
   * Depend on newer dh-python which sets SETUPTOOLS_SCM_PRETEND_VERSION
   * wrap-and-sort -t -a
   * Bumped debhelper compat version to 9
   * Standards-Version is 3.9.8 now (no changes needed)
   * d/copyright: Removed licence for absent files
+
+  [ Brian May ]
+  * New upstream version. Closes: #865556.
   * Refresh patches after git-dpm to gbp pq conversion
 
- -- Ondřej Nový   Fri, 17 Jun 2016 21:05:30 +0200
+ -- Brian May   Sun, 25 Jun 2017 13:13:07 +1000
 
 django-guardian (1.4.4-1) unstable; urgency=medium
 

Processed: Bug#865556 marked as pending

[Debian Bug Tracking System]

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

> tag 865556 pending
Bug #865556 [src:django-guardian] django-guardian FTBFS with Django 1.11
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#865819: marked as done (haskell-hackage-security FTBFS due to build-dependency on libghc-cabal-dev)

[Debian Bug Tracking System]

Your message dated Sun, 25 Jun 2017 03:06:23 +
with message-id 
and subject line Bug#865819: fixed in haskell-hackage-security 0.5.2.2-8
has caused the Debian Bug report #865819,
regarding haskell-hackage-security FTBFS due to build-dependency on 
libghc-cabal-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.)


-- 
865819: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865819
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-hackage-security
Version: 0.5.2.2-7
Severity: serious

>From #865399:
haskell-cabal should be kept out of testing for the foreseeable future,
and any packages build-depending on it should be switched to use ghc's
Cabal for the foreseeable future.
--- End Message ---
--- Begin Message ---
Source: haskell-hackage-security
Source-Version: 0.5.2.2-8

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

Debian distribution maintenance software
pp.
Clint Adams  (supplier of updated haskell-hackage-security 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 24 Jun 2017 22:11:27 -0400
Source: haskell-hackage-security
Binary: libghc-hackage-security-dev libghc-hackage-security-prof 
libghc-hackage-security-doc
Architecture: source
Version: 0.5.2.2-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group 

Changed-By: Clint Adams 
Description:
 libghc-hackage-security-dev - ${haskell:ShortDescription}${haskell:ShortBlurb}
 libghc-hackage-security-doc - ${haskell:ShortDescription}${haskell:ShortBlurb}
 libghc-hackage-security-prof - ${haskell:ShortDescription}${haskell:ShortBlurb}
Closes: 865819
Changes:
 haskell-hackage-security (0.5.2.2-8) unstable; urgency=medium
 .
   * Switch back to ghc-bundled Cabal.  closes: #865819.
Checksums-Sha1:
 48a64632970d34c5e46aed7535c41c3ab8900c99 3784 
haskell-hackage-security_0.5.2.2-8.dsc
 a1bcc102a1473f14db086ce5c9938c7bf961c16f 83131 
haskell-hackage-security_0.5.2.2.orig.tar.gz
 83cadb59ef5ad52134ae35ac706ef08bdd43ad15 3220 
haskell-hackage-security_0.5.2.2-8.debian.tar.xz
 6d106721e9ba3f83822d203c5521de20ba0b7ddf 8680 
haskell-hackage-security_0.5.2.2-8_source.buildinfo
Checksums-Sha256:
 908fbf7d9b4db33d6c089d8ea93a1b084520a6a15a49bd31a0510fe346001c93 3784 
haskell-hackage-security_0.5.2.2-8.dsc
 507a837851264a774c8f4d400f798c3dac5be11dc428fe72d33ef594ca533c41 83131 
haskell-hackage-security_0.5.2.2.orig.tar.gz
 429969cc837a41889e4845f00991a81ef732f67c5fd089e6f0a6d5011a8ffaa1 3220 
haskell-hackage-security_0.5.2.2-8.debian.tar.xz
 1af7c3980fe124ed2e15b5a95be0451ee9769cf8e788bb4caa0f5044a2073751 8680 
haskell-hackage-security_0.5.2.2-8_source.buildinfo
Files:
 7a627c48e4fdc807938619040c89f138 3784 haskell extra 
haskell-hackage-security_0.5.2.2-8.dsc
 7bbcd32f60b445d7246f67a37cac6f46 83131 haskell extra 
haskell-hackage-security_0.5.2.2.orig.tar.gz
 9b47e8c14362722202aaa2f8e5a1dd6b 3220 haskell extra 
haskell-hackage-security_0.5.2.2-8.debian.tar.xz
 b37aabba21ae9a4d44c6f40464cd7d5c 8680 haskell extra 
haskell-hackage-security_0.5.2.2-8_source.buildinfo

-BEGIN PGP SIGNATURE-
Comment: Debian!

iQKlBAEBCgCPFiEEdYHsh0BT5sgHeRubVZIzHhmdOKgFAllPHCRfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDc1
ODFFQzg3NDA1M0U2QzgwNzc5MUI5QjU1OTIzMzFFMTk5RDM4QTgRHGNsaW50QGRl
Ymlhbi5vcmcACgkQVZIzHhmdOKi+6Q/9EoTzasuwKpSNlaD2Z1GPFE6kBLEbjxOw
fCvs6HhZ155JdF1XhrCfomnxIsyCHF5jERSzbhxTRXrIYdqtv0YIicvcVF31aG2r
YW6+VtkFtVdwf/JhnxDZeXTylzyesy2xQxAS8cKeROuj8EvigXHC5WeYad/VrfRs
joDAlpzMge1PPeZRbIitFf7IFzfd+uxWpkS37Gfsj69VMpp7dTNDCLMvQ9RnRYIF
PJCMYZGfINx5PqIQQuzEcOyxaqQZJIvfnmp83bp5WC9Q12LMO+T+M6L/TrPu33s7
+9px8XjFhu0fG4YsW1Bg8MIz62JXPaos9CBCy1m92wvoJhGFFPmHYEVdCruXpYAL
jgOl+WIBZxOSUUNxhn9rNQkVo7y7OcWdNKn6TtCrtFFeEGy//0bI57/7RzUkQzGD
mvJdX9UX7W+ku64qrtO+VKEJwYNnDEu7S3BUmUjp31ugqEfXX0hQTRigqfq37RGk
ZE4JfZ2V8VlRVldrXS4BFyafU4K7ovNaUTnVMAZXsPoE34j3DcdAWc75TTtAAWin
VRx+P2kjHqHoTG/ZASUGwVRvv9nCN/8NvqMPzfGS99q4Cd0DoN62vkiZtr/+asRt
6AvU0eoZPqjx/VdDuB5sjtq0L/lSr9U/hgzGgQmjqf2Id3G8gT410DUAqyrVB+Wg
V+HB+tcOzqs

Processed: Re: Bug#865822: mutt: Enter key disabled with latest upgrade

[Debian Bug Tracking System]

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

> retitle 865822 no compile time tmp dir
Bug #865822 [mutt] mutt: Enter key disabled with latest upgrade
Changed Bug title to 'no compile time tmp dir' from 'mutt: Enter key disabled 
with latest upgrade'.
> thanks
Stopping processing here.

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

Bug#865822: mutt: Enter key disabled with latest upgrade

[Norbert Preining]

retitle 865822 no compile time tmp dir
thanks

> today's mutt update to 1.8.3... rendered the Enter key unusable.

The reason was
reset tmpdir
in the config file, which uses the compiled in tmpdir, which seems to be
set to
/
because a trace reveils that mutt tries to create a tmp file in
mkdir("/.mutts9pGoo", 0700) = -1 EACCES (Permission denied)
root.

Please compile in a decent tmpdir like /tmp or /var/tmp

Thanks

Norbert

--
PREINING Norbert   http://www.preining.info
Accelia Inc. +JAIST +TeX Live +Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#865822: mutt: Enter key disabled with latest upgrade

[Norbert Preining]

Package: mutt
Version: 1.8.3+neomutt20170609-1
Severity: serious
Justification: renders unusable

Dear maintainers,

today's mutt update to 1.8.3... rendered the Enter key unusable.
I can navigate my inbox, but it is impossible to open any
mail, which was definitely possible till till morning when
I was reading email.

Removing my whole local configuration activates the Enter key again,
but that is not really optimal.

Thanks

Norbert

-- Package-specific info:
NeoMutt 20170609 (1.8.3)
Copyright (C) 1996-2016 Michael R. Elkins and others.
Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'.
Mutt is free software, and you are welcome to redistribute it
under certain conditions; type `mutt -vv' for details.

System: Linux 4.12.0-rc6 (x86_64)
libidn: 1.33 (compiled with 1.33)
hcache backends: tokyocabinet

Compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/6/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 6.3.0-19' 
--with-bugurl=file:///usr/share/doc/gcc-6/README.Bugs 
--enable-languages=c,ada,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr 
--program-suffix=-6 --program-prefix=x86_64-linux-gnu- --enable-shared 
--enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext 
--enable-threads=posix --libdir=/usr/lib --enable-nls --with-sysroot=/ 
--enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes 
--with-default-libstdcxx-abi=new --enable-gnu-unique-object 
--disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie 
--with-system-zlib --disable-browser-plugin --enable-java-awt=gtk 
--enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-6-amd64/jre 
--enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-6-amd64 
--with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-6-amd64 
--with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar 
--with-target-s
 ystem-zlib --enable-objc-gc=auto --enable-multiarch --with-arch-32=i686 
--with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib 
--with-tune=generic --enable-checking=release --build=x86_64-linux-gnu 
--host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 6.3.0 20170618 (Debian 6.3.0-19) 

Configure options: '--build=x86_64-linux-gnu' '--prefix=/usr' 
'--includedir=\${prefix}/include' '--mandir=\${prefix}/share/man' 
'--infodir=\${prefix}/share/info' '--sysconfdir=/etc' '--localstatedir=/var' 
'--disable-silent-rules' '--libdir=\${prefix}/lib/x86_64-linux-gnu' 
'--libexecdir=\${prefix}/lib/x86_64-linux-gnu' '--disable-maintainer-mode' 
'--disable-dependency-tracking' '--with-mailpath=/var/mail' 
'--enable-compressed' '--enable-debug' '--enable-fcntl' '--enable-hcache' 
'--enable-gpgme' '--enable-lua' '--enable-imap' '--enable-smtp' '--enable-pop' 
'--enable-sidebar' '--enable-nntp' '--enable-dotlock' '--enable-notmuch' 
'--disable-fmemopen' '--with-curses' '--with-gnutls' '--with-gss' '--with-idn' 
'--with-mixmaster' '--with-sasl' '--without-gdbm' '--without-bdb' 
'--without-qdbm' '--with-tokyocabinet' 'build_alias=x86_64-linux-gnu' 
'CFLAGS=-g -O2 
-fdebug-prefix-map=/build/mutt-fz46Ej/mutt-1.8.3+neomutt20170609=. 
-fstack-protector-strong -Wformat -Werror=format-security' 'LDFLAGS
 =-Wl,-z,relro -Wl,-z,now' 'CPPFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2'

Compilation CFLAGS: -Wall -pedantic -Wno-long-long -g -O2 
-fdebug-prefix-map=/build/mutt-fz46Ej/mutt-1.8.3+neomutt20170609=. 
-fstack-protector-strong -Wformat -Werror=format-security 
-fno-delete-null-pointer-checks

Compile options:
  +attach_headers_color +bkgdset +color +compose_to_sender +compress +cond_date 
  +curs_set +debug +dotlock +encrypt_to_self -exact_address +fcntl -flock 
  -fmemopen +forgotten_attachments +forwref +futimens +getaddrinfo +getsid 
  +gnutls +gpgme +gss +hcache -homespool -iconv_nontrans +ifdef +imap 
  +index_color +initials +keywords +libidn +limit_current_thread +lmdb 
  -locales_hack +lua +meta +mixmaster +multiple_fcc +nested_if +new_mail +nls 
  +nntp +notmuch -openssl +pgp +pop +progress +quasi_delete +regcomp 
  +reply_with_xorig +resizeterm +sasl +sensible_browser -setgid +sidebar 
  +skip_quoted +smime +smtp +start_color +status_color +sun_attachment +timeout 
  +tls_sni +trash +typeahead +wc_funcs 
EXECSHELL="/bin/sh"
MAILPATH="/var/mail"
MIXMASTER="mixmaster"
PKGDATADIR="/usr/share/mutt"
SENDMAIL="/usr/sbin/sendmail"
SYSCONFDIR="/etc"

To learn more about NeoMutt, visit: http://www.neomutt.org/
If you find a bug in NeoMutt, please raise an issue at:
https://github.com/neomutt/neomutt/issues
or send an email to: 


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

Kernel: Linux 4.12.0-rc6 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)

Bug#865653: xrdp: X server timeout

[Stanislav Sinyagin]

Found a solution: after changing to "allowed_users=anybody" in
/etc/X11/Xwrapper.config , XRDP works as expected. So, the default
value ("console") supplied by xserver-xorg-legacy is not compatible
with XRDP, and needs to be adapted.

Bug#865819: haskell-hackage-security FTBFS due to build-dependency on libghc-cabal-dev

[Adrian Bunk]

Source: haskell-hackage-security
Version: 0.5.2.2-7
Severity: serious

>From #865399:
haskell-cabal should be kept out of testing for the foreseeable future,
and any packages build-depending on it should be switched to use ghc's
Cabal for the foreseeable future.

Bug#865818: ganeti FTBFS due to build-dependency on libghc-cabal-dev

[Adrian Bunk]

Source: ganeti
Version: 2.15.2-3
Severity: serious
Tags: buster sid

>From #865399:
haskell-cabal should be kept out of testing for the foreseeable future,
and any packages build-depending on it should be switched to use ghc's
Cabal for the foreseeable future.

Bug#865817: curry-frontend FTBFS due to build-dependency on libghc-cabal-dev

[Adrian Bunk]

Source: curry-frontend
Version: 0.4.2-5
Severity: serious

>From #865399:
haskell-cabal should be kept out of testing for the foreseeable future,
and any packages build-depending on it should be switched to use ghc's
Cabal for the foreseeable future.

Processed: your mail

[Debian Bug Tracking System]

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

> tags 865577 + patch
Bug #865577 [src:cloud-init] cloud-init FTBFS: recipe for target 'pep8' failed
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#865577: cloud-init FTBFS: recipe for target 'pep8' failed

[Joonas Kylmälä]

This bug has been fixed in the upstream commit
.

Processed: affects stable now that firefox-esr is 52 there

[Debian Bug Tracking System]

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

> reopen 863947
Bug #863947 {Done: Michael Schutte } [xul-ext-pentadactyl] 
Does not work with FF 5x
'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 dactyl/1.2~r20170308-1.
> severity 863947 serious
Bug #863947 [xul-ext-pentadactyl] Does not work with FF 5x
Severity set to 'serious' from 'normal'
> close 863947 1.2~r20170308-1
Bug #863947 [xul-ext-pentadactyl] Does not work with FF 5x
Marked as fixed in versions dactyl/1.2~r20170308-1.
Bug #863947 [xul-ext-pentadactyl] Does not work with FF 5x
Marked Bug as done
> quit
Stopping processing here.

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

Processed: oops

[Debian Bug Tracking System]

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

> reopen 865305
Bug #865305 {Done: Clint Adams } [xul-ext-pentadactyl] Does 
not work with firefox 54
'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 dactyl/1.2~r20170308-1.
> quit
Stopping processing here.

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

Bug#865814: django-tables FTBFS with Django 1.11

[Adrian Bunk]

Source: django-tables
Version: 1.2.0-1
Severity: serious
Tags: buster sid

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

...
dh_auto_test -- --system=custom --test-args="{interpreter} /usr/bin/py.test"
dh_auto_test: Compatibility levels before 9 are deprecated (level 7 in use)
I: pybuild base:184: python2.7 /usr/bin/py.test
= test session starts ==
platform linux2 -- Python 2.7.13, pytest-3.0.6, py-1.4.34, pluggy-0.4.0
django settings: tests.app.settings (from ini file)
rootdir: /build/1st/django-tables-1.2.0, inifile: tox.ini
plugins: django-2.9.1
collected 178 items

tests/test_config.py ..
tests/test_core.py .
tests/test_models.py 
tests/test_rows.py ..
tests/test_templates.py 
tests/test_templatetags.py .
tests/test_utils.py 
tests/test_views.py ...
tests/columns/test_booleancolumn.py ...
tests/columns/test_checkboxcolumn.py .
tests/columns/test_datecolumn.py 
tests/columns/test_datetimecolumn.py 
tests/columns/test_emailcolumn.py 
tests/columns/test_filecolumn.py 
tests/columns/test_general.py ..
tests/columns/test_linkcolumn.py 
tests/columns/test_templatecolumn.py F
tests/columns/test_timecolumn.py ..
tests/columns/test_urlcolumn.py 

=== FAILURES ===
_ test_should_handle_context_on_table __

def test_should_handle_context_on_table():
class TestTable(tables.Table):
col_code = tables.TemplateColumn(template_code='code:{{ record.col 
}}{{ STATIC_URL }}')
col_name = 
tables.TemplateColumn(template_name='test_template_column.html')

table = TestTable([{'col': 'brad'}])
assert table.rows[0].get_cell('col_code') == 'code:brad'
>   assert table.rows[0].get_cell('col_name') == 'name:brad'

tests/columns/test_templatecolumn.py:17: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
django_tables2/rows.py:150: in get_cell
return self._call_render(bound_column, value)
django_tables2/rows.py:170: in _call_render
return bound_column.render(**kwargs)
django_tables2/columns/templatecolumn.py:71: in render
return template.render(context)
/usr/lib/python2.7/dist-packages/django/template/backends/django.py:64: in 
render
context = make_context(context, request, 
autoescape=self.backend.engine.autoescape)
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

context = [{'False': False, 'None': None, 'True': True}], request = None
kwargs = {'autoescape': True}

def make_context(context, request=None, **kwargs):
"""
Create a suitable Context from a plain dict and optionally an 
HttpRequest.
"""
if context is not None and not isinstance(context, dict):
>   raise TypeError('context must be a dict rather than %s.' % 
> context.__class__.__name__)
E   TypeError: context must be a dict rather than Context.

/usr/lib/python2.7/dist-packages/django/template/context.py:287: TypeError
= 1 failed, 177 passed in 2.44 seconds =
E: pybuild pybuild:283: test: plugin custom failed with: exit code=1: python2.7 
/usr/bin/py.test
dh_auto_test: pybuild --test -i python{version} -p 2.7 --system=custom 
--test-args={interpreter} /usr/bin/py.test returned exit code 13
debian/rules:21: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 25

Bug#823508: Useless in Debian

[Michael Crusoe]

The khmer package latest upstream version now uses this theme. I would be
happy to take over maintenance.

On Thu, 5 May 2016 09:29:14 -0400 David =?iso-8859-1?Q?Pr=E9vot?= <
taf...@debian.org> wrote:
> Package: python-guzzle-sphinx-theme
> Version: 0.7.10-1
> Severity: serious
>
> [ Filled as an RC-bug by the maintainer to see the package auto-removed
>   from testing. ]
>
> I packaged python-guzzle-sphinx-theme in order to build php-guzzle-doc,
> but php-guzzle is going away, see #821698. There is a priori little
> point in shipping python-guzzle-sphinx-theme in any Debian stable
> release anymore.
>
> I intend to follow up with an RM request once php-guzzle is gone, unless
> anyone objects (but feel free to beat me to it).
>
> Regards
>
> David

Bug#865813: jumpnbump: Fix occasional parallel FTBFS

[Adrian Bunk]

Source: jumpnbump
Version: 1.60-1
Severity: serious
Tags: patch

debhelper compat 10 defaults to parallel building,
which exposed the bug fixed in the attached patch
that resulted in "cd modify && make" running up to
three times in prallel.

Depending on the timing this does sometimes FTBFS:

https://buildd.debian.org/status/fetch.php?pkg=jumpnbump&arch=mips&ver=1.60-1&stamp=1498322671&raw=0

...
make -C modify
...
make -C modify
...
cc -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. -fstack-protector-strong -Wformat 
-Werror=format-security -Dstricmp=strcasecmp -Dstrnicmp=strncasecmp -DNDEBUG 
-DUSE_SDL -DUSE_NET -DZLIB_SUPPORT -DBZLIB_SUPPORT `sdl2-config --cflags` -I. 
-Dstricmp=strcasecmp -Dstrnicmp=strncasecmp -DNDEBUG -DUSE_SDL -DUSE_NET 
-DZLIB_SUPPORT -DBZLIB_SUPPORT -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2  -c -o 
jnbunpack.o jnbunpack.c
cc -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. -fstack-protector-strong -Wformat 
-Werror=format-security -Dstricmp=strcasecmp -Dstrnicmp=strncasecmp -DNDEBUG 
-DUSE_SDL -DUSE_NET -DZLIB_SUPPORT -DBZLIB_SUPPORT `sdl2-config --cflags` -I. 
-Dstricmp=strcasecmp -Dstrnicmp=strncasecmp -DNDEBUG -DUSE_SDL -DUSE_NET 
-DZLIB_SUPPORT -DBZLIB_SUPPORT -I. -I.. -o ../gobpack gobpack.o -Wl,-z,relro 
cc -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. -fstack-protector-strong -Wformat 
-Werror=format-security -Dstricmp=strcasecmp -Dstrnicmp=strncasecmp -DNDEBUG 
-DUSE_SDL -DUSE_NET -DZLIB_SUPPORT -DBZLIB_SUPPORT `sdl2-config --cflags` -I. 
-Dstricmp=strcasecmp -Dstrnicmp=strncasecmp -DNDEBUG -DUSE_SDL -DUSE_NET 
-DZLIB_SUPPORT -DBZLIB_SUPPORT -I. -I.. -o ../jnbpack jnbpack.o -Wl,-z,relro 
jnbunpack.c: In function 'main':
jnbunpack.c:65:5: warning: ignoring return value of 'read', declared with 
attribute warn_unused_result [-Wunused-result]
 read(fd, &num_entries, 4);
 ^
jnbunpack.c:70:5: warning: ignoring return value of 'read', declared with 
attribute warn_unused_result [-Wunused-result]
 read(fd, datafile, num_entries * sizeof(DirEntry));
 ^~
jnbunpack.c:100:2: warning: ignoring return value of 'read', declared with 
attribute warn_unused_result [-Wunused-result]
  read(fd, buf, datafile[i].size);
  ^~~
jnbunpack.c:101:2: warning: ignoring return value of 'write', declared with 
attribute warn_unused_result [-Wunused-result]
  write(outfd, buf, datafile[i].size);
  ^~~
cc -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. -fstack-protector-strong -Wformat 
-Werror=format-security -Dstricmp=strcasecmp -Dstrnicmp=strncasecmp -DNDEBUG 
-DUSE_SDL -DUSE_NET -DZLIB_SUPPORT -DBZLIB_SUPPORT `sdl2-config --cflags` -I. 
-Dstricmp=strcasecmp -Dstrnicmp=strncasecmp -DNDEBUG -DUSE_SDL -DUSE_NET 
-DZLIB_SUPPORT -DBZLIB_SUPPORT -I. -I.. -o ../jnbunpack jnbunpack.o 
-Wl,-z,relro 
make[3]: Leaving directory '/«PKGBUILDDIR»/modify'
make -C modify
make[3]: Entering directory '/«PKGBUILDDIR»/modify'
cc -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. -fstack-protector-strong -Wformat 
-Werror=format-security -Dstricmp=strcasecmp -Dstrnicmp=strncasecmp -DNDEBUG 
-DUSE_SDL -DUSE_NET -DZLIB_SUPPORT -DBZLIB_SUPPORT `sdl2-config --cflags` -I. 
-Dstricmp=strcasecmp -Dstrnicmp=strncasecmp -DNDEBUG -DUSE_SDL -DUSE_NET 
-DZLIB_SUPPORT -DBZLIB_SUPPORT -I. -I.. -o ../jnbunpack jnbunpack.o 
-Wl,-z,relro 
jnbunpack.o: file not recognized: File truncated
collect2: error: ld returned 1 exit status
Makefile:21: recipe for target '../jnbunpack' failed
make[3]: *** [../jnbunpack] Error 1
make[3]: Leaving directory '/«PKGBUILDDIR»/modify'
Makefile:36: recipe for target 'jnbunpack' failed
make[2]: *** [jnbunpack] Error 2
make[2]: *** Waiting for unfinished jobs
cc -g -O2 -fdebug-prefix-map=/«PKGBUILDDIR»=. -fstack-protector-strong -Wformat 
-Werror=format-security -Dstricmp=strcasecmp -Dstrnicmp=strncasecmp -DNDEBUG 
-DUSE_SDL -DUSE_NET -DZLIB_SUPPORT -DBZLIB_SUPPORT `sdl2-config --cflags` -I. 
-Dstricmp=strcasecmp -Dstrnicmp=strncasecmp -DNDEBUG -DUSE_SDL -DUSE_NET 
-DZLIB_SUPPORT -DBZLIB_SUPPORT -I. -I.. -o ../jnbunpack jnbunpack.o 
-Wl,-z,relro 
make[3]: Leaving directory '/«PKGBUILDDIR»/modify'
make[2]: Leaving directory '/«PKGBUILDDIR»'
dh_auto_build: make -j2 PREFIX=/usr BINDIR=/usr/games 
GAMEDATADIR=/usr/share/games returned exit code 2
debian/rules:7: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
Description: Fix occasional parallel FTBFS
 "cd modify && make" was running up to three times in parallel.
Author: Adrian Bunk 

--- jumpnbump-1.51+dfsg1.orig/Makefile
+++ jumpnbump-1.51+dfsg1/Makefile
@@ -12,14 +12,16 @@ BINARIES = $(TARGET) jumpnbump.svgalib j
jnbmenu.tcl
 PREFIX ?= /usr/local
 
-.PHONY: data
+.PHONY: data modify
 
 all: $(BINARIES)
 
 $(SDL_TARGET): globals.h
cd sdl && make
 
-$(MODIFY_TARGET): globals.h
+$(MODIFY_TARGET): modify
+
+modify: globals.h
cd modify && make
 
 $(TARGET): $(OBJS) $(SDL

Processed: reassign 865810 to libmodule-build-perl, forcibly merging 865563 865810, affects 865563 ...

[Debian Bug Tracking System]

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

> reassign 865810 libmodule-build-perl
Bug #865810 [src:libjson-webtoken-perl] libjson-webtoken-perl FTBFS: test 
failures
Bug reassigned from package 'src:libjson-webtoken-perl' to 
'libmodule-build-perl'.
No longer marked as found in versions libjson-webtoken-perl/0.10-2.
Ignoring request to alter fixed versions of bug #865810 to the same values 
previously set
> forcemerge 865563 865810
Bug #865563 [libmodule-build-perl] libcatmandu-sru-perl FTBFS: test failures
Bug #865810 [libmodule-build-perl] libjson-webtoken-perl FTBFS: test failures
Set Bug forwarded-to-address to 
'https://github.com/Perl-Toolchain-Gang/Module-Build/issues/77'.
Added indication that 865810 affects src:libcatmandu-sru-perl
Marked as found in versions libmodule-build-perl/0.422400-1.
Merged 865563 865810
> affects 865563 + libjson-webtoken-perl
Bug #865563 [libmodule-build-perl] libcatmandu-sru-perl FTBFS: test failures
Bug #865810 [libmodule-build-perl] libjson-webtoken-perl FTBFS: test failures
Added indication that 865563 affects libjson-webtoken-perl
Added indication that 865810 affects libjson-webtoken-perl
> retitle 865563 libmodule-build-perl: Issue with missing dot-in-inc; causes 
> multiple build failures
Bug #865563 [libmodule-build-perl] libcatmandu-sru-perl FTBFS: test failures
Bug #865810 [libmodule-build-perl] libjson-webtoken-perl FTBFS: test failures
Changed Bug title to 'libmodule-build-perl: Issue with missing dot-in-inc; 
causes multiple build failures' from 'libcatmandu-sru-perl FTBFS: test 
failures'.
Changed Bug title to 'libmodule-build-perl: Issue with missing dot-in-inc; 
causes multiple build failures' from 'libjson-webtoken-perl FTBFS: test 
failures'.
> thanks
Stopping processing here.

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

Processed (with 3 errors): Re: Bug#865810: libjson-webtoken-perl FTBFS: test failures

[Debian Bug Tracking System]

Processing control commands:

> forcemerge 865563 -1
Bug #865563 [libmodule-build-perl] libcatmandu-sru-perl FTBFS: test failures
Unable to merge bugs because:
package of #865810 is 'src:libjson-webtoken-perl' not 'libmodule-build-perl'
Failed to forcibly merge 865563: Did not alter merged bugs.

> affects 865563 + libjson-webtoken-perl
Failed to mark 865563 as affecting package(s): failed to get lock on 
/org/bugs.debian.org/spool/lock/865563 -- Unable to lock 
/org/bugs.debian.org/spool/lock/865563 Resource temporarily unavailable.
Unable to lock /org/bugs.debian.org/spool/lock/865563 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/865563 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/865563 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/865563 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/865563 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/865563 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/865563 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/865563 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/865563 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
 at /usr/local/lib/site_perl/Debbugs/Common.pm line 587.

> retitle 865563 libmodule-build-perl: Issue with missing dot-in-inc; causes 
> multiple build failures
Failed to set the title of 865563: failed to get lock on 
/org/bugs.debian.org/spool/lock/865563 -- Unable to lock 
/org/bugs.debian.org/spool/lock/865563 Resource temporarily unavailable.
Unable to lock /org/bugs.debian.org/spool/lock/865563 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/865563 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/865563 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/865563 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/865563 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/865563 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/865563 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/865563 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/865563 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
 at /usr/local/lib/site_perl/Debbugs/Common.pm line 587.


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

Bug#865810: libjson-webtoken-perl FTBFS: test failures

[gregor herrmann]

Control: forcemerge 865563 -1
Control: affects 865563 + libjson-webtoken-perl
Control: retitle 865563 libmodule-build-perl: Issue with missing dot-in-inc; 
causes multiple build failures

On Sun, 25 Jun 2017 01:43:37 +0300, Adrian Bunk wrote:

> Source: libjson-webtoken-perl
> Version: 0.10-2
> Severity: serious
> Tags: buster sid
> 
> Some recent change in unstable makes libjson-webtoken-perl FTBFS:

Yeah, that's #865563 again; which is a problem in Module::Build and
affects dozens (or hundreds) of packages.
 

Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: STS: Continental


signature.asc
Description: Digital Signature

Bug#865810: libjson-webtoken-perl FTBFS: test failures

[Adrian Bunk]

Source: libjson-webtoken-perl
Version: 0.10-2
Severity: serious
Tags: buster sid

Some recent change in unstable makes libjson-webtoken-perl FTBFS:

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

...
Can't locate t/Util.pm in @INC (you may need to install the t::Util module) 
(@INC contains: /build/1st/libjson-webtoken-perl-0.10/blib/lib 
/build/1st/libjson-webtoken-perl-0.10/blib/arch 
/build/1st/libjson-webtoken-perl-0.10/_build/lib /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.24.1 /usr/local/share/perl/5.24.1 
/usr/lib/x86_64-linux-gnu/perl5/5.24 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at t/01_basic.t 
line 3.
BEGIN failed--compilation aborted at t/01_basic.t line 3.
t/01_basic.t ... 
Dubious, test returned 2 (wstat 512, 0x200)
No subtests run 
Can't locate t/Util.pm in @INC (you may need to install the t::Util module) 
(@INC contains: /build/1st/libjson-webtoken-perl-0.10/blib/lib 
/build/1st/libjson-webtoken-perl-0.10/blib/arch 
/build/1st/libjson-webtoken-perl-0.10/_build/lib /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.24.1 /usr/local/share/perl/5.24.1 
/usr/lib/x86_64-linux-gnu/perl5/5.24 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at t/02_rsa.t 
line 3.
BEGIN failed--compilation aborted at t/02_rsa.t line 3.
t/02_rsa.t . 
Dubious, test returned 2 (wstat 512, 0x200)
No subtests run 
Can't locate t/Util.pm in @INC (you may need to install the t::Util module) 
(@INC contains: /build/1st/libjson-webtoken-perl-0.10/blib/lib 
/build/1st/libjson-webtoken-perl-0.10/blib/arch 
/build/1st/libjson-webtoken-perl-0.10/_build/lib /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.24.1 /usr/local/share/perl/5.24.1 
/usr/lib/x86_64-linux-gnu/perl5/5.24 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at 
t/03_add_signing_algorithm.t line 30.
BEGIN failed--compilation aborted at t/03_add_signing_algorithm.t line 30.
t/03_add_signing_algorithm.t ... 
Dubious, test returned 2 (wstat 512, 0x200)
No subtests run 
...
Can't locate t/Util.pm in @INC (you may need to install the t::Util module) 
(@INC contains: /build/1st/libjson-webtoken-perl-0.10/blib/lib 
/build/1st/libjson-webtoken-perl-0.10/blib/arch 
/build/1st/libjson-webtoken-perl-0.10/_build/lib /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.24.1 /usr/local/share/perl/5.24.1 
/usr/lib/x86_64-linux-gnu/perl5/5.24 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at 
t/spec/draft-ietf-oauth-json-web-token-06-3.1.example.t line 3.
BEGIN failed--compilation aborted at 
t/spec/draft-ietf-oauth-json-web-token-06-3.1.example.t line 3.
t/spec/draft-ietf-oauth-json-web-token-06-3.1.example.t  
Dubious, test returned 2 (wstat 512, 0x200)
No subtests run 

Test Summary Report
---
t/01_basic.t (Wstat: 512 Tests: 
0 Failed: 0)
  Non-zero exit status: 2
  Parse errors: No plan found in TAP output
t/02_rsa.t   (Wstat: 512 Tests: 
0 Failed: 0)
  Non-zero exit status: 2
  Parse errors: No plan found in TAP output
t/03_add_signing_algorithm.t (Wstat: 512 Tests: 
0 Failed: 0)
  Non-zero exit status: 2
  Parse errors: No plan found in TAP output
t/spec/draft-ietf-oauth-json-web-token-06-3.1.example.t  (Wstat: 512 Tests: 
0 Failed: 0)
  Non-zero exit status: 2
  Parse errors: No plan found in TAP output
Files=9, Tests=24,  1 wallclock secs ( 0.06 usr  0.02 sys +  0.42 cusr  0.09 
csys =  0.59 CPU)
Result: FAIL
Failed 4/9 test programs. 0/24 subtests failed.
/usr/share/cdbs/1/class/perl-build.mk:84: recipe for target 
'debian/stamp-perl-check' failed
make: *** [debian/stamp-perl-check] Error 2

Bug#865808: golang-github-urfave-cli FTBFS: FAIL: TestFlagsFromEnv

[Adrian Bunk]

Source: golang-github-urfave-cli
Version: 1.19.1-1
Severity: serious
Tags: buster sid

Some recent change in unstable makes golang-github-urfave-cli FTBFS:

https://tests.reproducible-builds.org/debian/history/golang-github-urfave-cli.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-urfave-cli.html

...
=== RUN   TestFlagsFromEnv
--- FAIL: TestFlagsFromEnv (0.00s)
flag_test.go:102: expected error could not parse 1.2,2 as int slice 
value for flag seconds: strconv.ParseInt: parsing "1.2": invalid syntax, got 
error could not parse 1.2,2 as int slice value for flag seconds: strconv.Atoi: 
parsing "1.2": invalid syntax
flag_test.go:102: expected error could not parse foobar as int slice 
value for flag seconds: strconv.ParseInt: parsing "foobar": invalid syntax, got 
error could not parse foobar as int slice value for flag seconds: strconv.Atoi: 
parsing "foobar": invalid syntax
...

Bug#865807: golang-github-coreos-go-oidc FTBFS: FAIL github.com/coreos/go-oidc/http

[Adrian Bunk]

Source: golang-github-coreos-go-oidc
Version: 0.0~git20160926.0.16c5ecc-1
Severity: serious
Tags: buster sid

Some recent change in unstable makes golang-github-coreos-go-oidc FTBFS:

https://tests.reproducible-builds.org/debian/history/golang-github-coreos-go-oidc.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-coreos-go-oidc.html

...
url_test.go:26: err: url is empty
url_test.go:26: err: url host is empty
url_test.go:26: err: url scheme is empty
url_test.go:26: err: url scheme is empty
FAIL
exit status 1
FAILgithub.com/coreos/go-oidc/http  0.013s
...

Bug#865806: gnome-dictionary FTBFS: gdict-client-context.h:84:1: error: unknown type name 'GdictContext'

[Adrian Bunk]

Source: gnome-dictionary
Version: 3.20.0-3
Severity: serious
Tags: buster sid

Some recent change in unstable makes gnome-dictionary FTBFS:

https://tests.reproducible-builds.org/debian/history/gnome-dictionary.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/gnome-dictionary.html

...
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I../libgdict -I../libgdict 
-DG_LOG_DOMAIN=\"Gdict\" -DDATADIR=\"/usr/share\" 
-DLIBDIR=\"/usr/lib/i386-linux-gnu\" -DSYSCONFDIR=\"/etc\" -DPREFIX=\"/usr\" 
-DGNOMELOCALEDIR=\"/usr/share/locale\" 
-DGDICTSOURCESDIR=\"/usr/share/gdict-1.0/sources\" -DGDICT_ENABLE_INTERNALS=1 
-DG_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED -UGTK_DISABLE_DEPRECATED 
-DPANGO_DISABLE_DEPRECATED -DG_DISABLE_SINGLE_INCLUDES 
-DGTK_DISABLE_SINGLE_INCLUDES -Wdate-time -D_FORTIFY_SOURCE=2 -pthread 
-I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/i386-linux-gnu/dbus-1.0/include 
-I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo 
-I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/libpng16 -I/usr/include
 /glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -DG_DISABLE_CAST_CHECKS 
-g -O2 -fstack-protector-strong -Wformat -Werror=format-security -c 
gdict-enum-types.c  -fPIC -DPIC -o .libs/libgdict_1_0_la-gdict-enum-types.o
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I../libgdict -I../libgdict 
-DG_LOG_DOMAIN=\"Gdict\" -DDATADIR=\"/usr/share\" 
-DLIBDIR=\"/usr/lib/i386-linux-gnu\" -DSYSCONFDIR=\"/etc\" -DPREFIX=\"/usr\" 
-DGNOMELOCALEDIR=\"/usr/share/locale\" 
-DGDICTSOURCESDIR=\"/usr/share/gdict-1.0/sources\" -DGDICT_ENABLE_INTERNALS=1 
-DG_DISABLE_DEPRECATED -DGDK_DISABLE_DEPRECATED -UGTK_DISABLE_DEPRECATED 
-DPANGO_DISABLE_DEPRECATED -DG_DISABLE_SINGLE_INCLUDES 
-DGTK_DISABLE_SINGLE_INCLUDES -Wdate-time -D_FORTIFY_SOURCE=2 -pthread 
-I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/i386-linux-gnu/dbus-1.0/include 
-I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo 
-I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/libpng16 -I/usr/include
 /glib-2.0 -I/usr/lib/i386-linux-gnu/glib-2.0/include -DG_DISABLE_CAST_CHECKS 
-g -O2 -fstack-protector-strong -Wformat -Werror=format-security -c 
gdict-utils.c  -fPIC -DPIC -o .libs/libgdict_1_0_la-gdict-utils.o
In file included from gdict-enum-types.c:6:0:
./gdict-client-context.h:84:1: error: unknown type name 'GdictContext'
 GdictContext *gdict_client_context_new  (const gchar
*hostname,
 ^~~~
Makefile:662: recipe for target 'libgdict_1_0_la-gdict-enum-types.lo' failed
make[4]: *** [libgdict_1_0_la-gdict-enum-types.lo] Error 1

Bug#865805: aiohttp-cors FTBFS: test failures

[Adrian Bunk]

Source: aiohttp-cors
Version: 0.5.0-1
Severity: serious
Tags: buster sid

Some recent change in unstable makes aiohttp-cors FTBFS:

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

...
== 4 tests deselected ==
= 13 failed, 14 passed, 4 deselected, 4 error in 2.42 seconds ==
E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: cd 
/build/1st/aiohttp-cors-0.5.0/.pybuild/pythonX.Y_3.5/build; python3.5 -m pytest 
-k-tests/integration/test_real_browser.py
dh_auto_test: pybuild --test -i python{version} -p 3.5 returned exit code 13
debian/rules:8: recipe for target 'build' failed
make: *** [build] Error 25

Processed: Add the tags I forgot

[Debian Bug Tracking System]

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

> tags 865804 buster sid
Bug #865804 [src:golang-github-ngaut-go-zookeeper] 
golang-github-ngaut-go-zookeeper FTBFS: local import "../zk" in non-local 
package
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Processed: Fix the bug title

[Debian Bug Tracking System]

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

> retitle 865803 libsoup2.4 FTBFS: test failures
Bug #865803 [src:libsoup2.4] libsoup2.4 FTBFS:
Changed Bug title to 'libsoup2.4 FTBFS: test failures' from 'libsoup2.4 FTBFS:'.
> thanks
Stopping processing here.

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

Bug#865804: golang-github-ngaut-go-zookeeper FTBFS: local import "../zk" in non-local package

[Adrian Bunk]

Source: golang-github-ngaut-go-zookeeper
Version: 0.0~git20150813.0.9c3719e-1
Severity: serious

Some recent change in unstable makes golang-github-ngaut-go-zookeeper FTBFS:

https://tests.reproducible-builds.org/debian/history/golang-github-ngaut-go-zookeeper.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-ngaut-go-zookeeper.html

...
dh build --buildsystem=golang --with=golang
   dh_testdir -O--buildsystem=golang
   dh_update_autotools_config -O--buildsystem=golang
   dh_autoreconf -O--buildsystem=golang
   dh_auto_configure -O--buildsystem=golang
   dh_auto_build -O--buildsystem=golang
go install -v -p 15 github.com/ngaut/go-zookeeper/examples 
github.com/ngaut/go-zookeeper/tracer github.com/ngaut/go-zookeeper/zk
src/github.com/ngaut/go-zookeeper/tracer/main.go:4:2: local import "../zk" in 
non-local package
dh_auto_build: go install -v -p 15 github.com/ngaut/go-zookeeper/examples 
github.com/ngaut/go-zookeeper/tracer github.com/ngaut/go-zookeeper/zk returned 
exit code 1
debian/rules:4: recipe for target 'build' failed
make: *** [build] Error 1

Bug#865552: libbpp-phyl FTBFS with test failures

[Julien Yann Dutheil]

Dear Andreas,

Please find attached a patch that sets the timeout to 1s (default was
1500). Hope this improves things...

Best,

Julien.

On Fri, Jun 23, 2017 at 9:43 PM, Andreas Tille  wrote:

> Hi Julien,
>
> On Fri, Jun 23, 2017 at 09:02:30PM +0200, Julien Yann Dutheil wrote:
> > This is most strange indeed. The errors are all "time out" errors on unit
> > tests which take the longest time (several min or so). Looks like some
> > issues with the default value for the timeout setting in CTest... I would
> > suggest to simply skip the unit tests by running "cmake
> > -DBUILD_TESTING=FALSE ." .  Does this solve the problem?
>
> Hmmm, this would most probably lead to successfully built packages but I
> would prefer spending some additional thoughts on this.  It would
> explain the issue why the package has built before but does not any more
> without any visible change on "weak" architectures.  I could imagine
> that after stretch release the run on the build servers increased and
> that possibly parallel builds are happening which lead to performance
> loss for single packages.
>
> Do you see any chance to increase the timeout settings by one order of
> magnitude to test this hypothesis?
>
> Kind regards
>
>   Andreas.
>
> --
> http://fam-tille.de
>



-- 
Julien Y. Dutheil, Ph-D
0 (+49) 6421 178 986

§ Max Planck Institute for Evolutionary Biology
Molecular Systems Evolution
Department of Evolutionary Genetics
Plön -- GERMANY

§ Institute of Evolutionary Sciences - Montpellier
University of Montpellier 2 -- FRANCE
commit 1d8fb92514f7cacfcf158de80b99cc13483437e7
Author: Julien Y. Dutheil 
Date:   Sat Jun 24 23:41:39 2017 +0200

Added longer timeout for tests.

diff --git a/test/CMakeLists.txt b/test/CMakeLists.txt
index 206cef39..5e8cf244 100644
--- a/test/CMakeLists.txt
+++ b/test/CMakeLists.txt
@@ -21,4 +21,6 @@ foreach (test_cpp_file ${test_cpp_files})
 WORKING_DIRECTORY ${CMAKE_CURRENT_SOURCE_DIR}
 COMMAND ${test_name}
 )
+  set_tests_properties (${test_name} PROPERTIES TIMEOUT 1)
 endforeach (test_cpp_file)
+

Bug#865803: libsoup2.4 FTBFS:

[Adrian Bunk]

Source: libsoup2.4
Version: 2.56.0-2
Severity: serious
Tags: buster sid

Some recent change in unstable makes libsoup2.4 FTBFS:

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

...
PASS: misc-test 1 /misc/host
PASS: misc-test 2 /misc/msg-reuse
PASS: misc-test 3 /misc/accept-language
FAIL: misc-test 4 /misc/aliases
PASS: misc-test 5 /misc/idle-on-dispose
PASS: misc-test 6 /misc/pause-abort
PASS: misc-test 7 /misc/pause-cancel
PASS: misc-test 8 /misc/callback-unref/msg
PASS: misc-test 9 /misc/callback-unref/req
PASS: misc-test 10 /misc/early-abort/msg
PASS: misc-test 11 /misc/early-abort/req
PASS: misc-test 12 /misc/cancel-while-reading/msg
PASS: misc-test 13 /misc/cancel-while-reading/req/immediate
PASS: misc-test 14 /misc/cancel-while-reading/req/delayed
PASS: misc-test 15 /misc/cancel-while-reading/req/preemptive
PASS: misc-test 16 /misc/stealing/async
PASS: misc-test 17 /misc/stealing/sync
ERROR: misc-test - exited with status 1
...
PASS: server-test 1 /server/OPTIONS *
PASS: server-test 2 /server/aliases
PASS: server-test 3 /server/..-in-path
PASS: server-test 4 /server/ipv6
PASS: server-test 5 /server/multi/port
FAIL: server-test 6 /server/multi/scheme
PASS: server-test 7 /server/multi/family
PASS: server-test 8 /server/import/gsocket
PASS: server-test 9 /server/import/fd
PASS: server-test 10 /server/accept/iostream
PASS: server-test 11 /server/fail/404
PASS: server-test 12 /server/fail/500
PASS: server-test 13 /server/fail/500-pause
PASS: server-test 14 /server/early/stream
PASS: server-test 15 /server/early/respond
PASS: server-test 16 /server/early/multi
FAIL: server-test 17 /server/steal/CONNECT
ERROR: server-test - exited with status 1
...
PASS: ssl-test 1 /ssl/session-properties
FAIL: ssl-test 2 /ssl/tls-interaction
FAIL: ssl-test 3 /ssl/message-properties/async
FAIL: ssl-test 4 /ssl/message-properties/sync
FAIL: ssl-test 5 /ssl/strictness/async/strict/with-ca
PASS: ssl-test 6 /ssl/strictness/async/strict/without-ca
FAIL: ssl-test 7 /ssl/strictness/async/non-strict/with-ca
PASS: ssl-test 8 /ssl/strictness/async/non-strict/without-ca
FAIL: ssl-test 9 /ssl/strictness/sync/strict/with-ca
PASS: ssl-test 10 /ssl/strictness/sync/strict/without-ca
FAIL: ssl-test 11 /ssl/strictness/sync/non-strict/with-ca
PASS: ssl-test 12 /ssl/strictness/sync/non-strict/without-ca
ERROR: ssl-test - exited with status 1
...
==
   libsoup 2.56.0: tests/test-suite.log
==

# TOTAL: 526
# PASS:  461
# SKIP:  50
# XFAIL: 0
# FAIL:  10
# XPASS: 0
# ERROR: 5
...

Bug#865802: django-filter FTBFS with Django 1.11

[Adrian Bunk]

Source: django-filter
Version: 0.13.0-1
Severity: serious

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

...
dh_auto_test -- --system=custom --test-args="{interpreter} ./runtests.py"
dh_auto_test: Compatibility levels before 9 are deprecated (level 7 in use)
I: pybuild base:184: python2.7 ./runtests.py
Traceback (most recent call last):
  File "./runtests.py", line 14, in 
runtests()
  File "./runtests.py", line 10, in runtests
execute_from_command_line(argv)
  File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", 
line 363, in execute_from_command_line
utility.execute()
  File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", 
line 337, in execute
django.setup()
  File "/usr/lib/python2.7/dist-packages/django/__init__.py", line 27, in setup
apps.populate(settings.INSTALLED_APPS)
  File "/usr/lib/python2.7/dist-packages/django/apps/registry.py", line 85, in 
populate
app_config = AppConfig.create(entry)
  File "/usr/lib/python2.7/dist-packages/django/apps/config.py", line 94, in 
create
module = import_module(entry)
  File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module
__import__(name)
  File "/build/1st/django-filter-0.13.0/django_filters/__init__.py", line 3, in 

from .filterset import FilterSet
  File "/build/1st/django-filter-0.13.0/django_filters/filterset.py", line 19, 
in 
from .filters import (Filter, CharFilter, BooleanFilter, BaseInFilter, 
BaseRangeFilter,
  File "/build/1st/django-filter-0.13.0/django_filters/filters.py", line 16, in 

from .fields import (
  File "/build/1st/django-filter-0.13.0/django_filters/fields.py", line 14, in 

from .widgets import RangeWidget, LookupTypeWidget, CSVWidget
  File "/build/1st/django-filter-0.13.0/django_filters/widgets.py", line 13, in 

from django.forms.widgets import flatatt
ImportError: cannot import name flatatt
E: pybuild pybuild:283: test: plugin custom failed with: exit code=1: python2.7 
./runtests.py
dh_auto_test: pybuild --test -i python{version} -p 2.7 --system=custom 
--test-args={interpreter} ./runtests.py returned exit code 13
debian/rules:16: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 25

Bug#865801: ovirt-guest-agent FTBFS: recipe for target 'check-local' failed

[Adrian Bunk]

Source: ovirt-guest-agent
Version: 1.0.12.2.dfsg-2
Severity: serious
Tags: buster sid

Some recent change in unstable makes ovirt-guest-agent FTBFS:

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

...
/usr/bin/pep8 --exclude="ovirt-guest-agent/setup.py" --filename '*.py,*.py.in' \
ovirt-guest-agent/CredServer.py ovirt-guest-agent/GuestAgentLinux2.py 
ovirt-guest-agent/GuestAgentWin32.py ovirt-guest-agent/LockActiveSession.py 
ovirt-guest-agent/OVirtAgentLogic.py ovirt-guest-agent/OVirtGuestService.py 
ovirt-guest-agent/VirtIoChannel.py ovirt-guest-agent/WinFile.py 
ovirt-guest-agent/ovirt-guest-agent.py ovirt-guest-agent/version.py 
ovirt-guest-agent/hooks.py tests/*.py
ovirt-guest-agent/GuestAgentLinux2.py:218:9: E722 do not use bare except'
ovirt-guest-agent/GuestAgentLinux2.py:349:9: E722 do not use bare except'
ovirt-guest-agent/GuestAgentLinux2.py:359:9: E722 do not use bare except'
ovirt-guest-agent/GuestAgentLinux2.py:382:17: E722 do not use bare except'
ovirt-guest-agent/GuestAgentLinux2.py:409:9: E722 do not use bare except'
ovirt-guest-agent/GuestAgentWin32.py:136:5: E722 do not use bare except'
ovirt-guest-agent/GuestAgentWin32.py:308:17: E722 do not use bare except'
ovirt-guest-agent/GuestAgentWin32.py:313:9: E722 do not use bare except'
ovirt-guest-agent/GuestAgentWin32.py:415:9: E722 do not use bare except'
ovirt-guest-agent/GuestAgentWin32.py:491:17: E722 do not use bare except'
ovirt-guest-agent/GuestAgentWin32.py:550:17: E722 do not use bare except'
ovirt-guest-agent/GuestAgentWin32.py:556:9: E722 do not use bare except'
ovirt-guest-agent/GuestAgentWin32.py:579:21: E722 do not use bare except'
ovirt-guest-agent/GuestAgentWin32.py:583:9: E722 do not use bare except'
ovirt-guest-agent/GuestAgentWin32.py:682:9: E722 do not use bare except'
ovirt-guest-agent/GuestAgentWin32.py:705:9: E722 do not use bare except'
ovirt-guest-agent/OVirtAgentLogic.py:269:9: E722 do not use bare except'
ovirt-guest-agent/OVirtAgentLogic.py:285:13: E722 do not use bare except'
ovirt-guest-agent/OVirtAgentLogic.py:317:13: E722 do not use bare except'
ovirt-guest-agent/OVirtAgentLogic.py:321:13: E722 do not use bare except'
ovirt-guest-agent/OVirtAgentLogic.py:325:13: E722 do not use bare except'
ovirt-guest-agent/OVirtGuestService.py:127:9: E722 do not use bare except'
ovirt-guest-agent/VirtIoChannel.py:184:9: E722 do not use bare except'
ovirt-guest-agent/WinFile.py:60:9: E722 do not use bare except'
ovirt-guest-agent/WinFile.py:72:9: E722 do not use bare except'
ovirt-guest-agent/ovirt-guest-agent.py:140:9: E722 do not use bare except'
ovirt-guest-agent/ovirt-guest-agent.py:146:9: E722 do not use bare except'
Makefile:904: recipe for target 'check-local' failed
make[3]: *** [check-local] Error 1
make[3]: Leaving directory '/build/1st/ovirt-guest-agent-1.0.12.2.dfsg'
Makefile:770: recipe for target 'check-am' failed
make[2]: *** [check-am] Error 2
make[2]: Leaving directory '/build/1st/ovirt-guest-agent-1.0.12.2.dfsg'
Makefile:482: recipe for target 'check-recursive' failed
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory '/build/1st/ovirt-guest-agent-1.0.12.2.dfsg'
dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2
debian/rules:24: recipe for target 'build' failed
make: *** [build] Error 2

Bug#865800: golang-github-smartystreets-go-aws-auth FTBFS: test failure

[Adrian Bunk]

Source: golang-github-smartystreets-go-aws-auth
Version: 0.0~git20160722.0.2043e6d-1
Severity: serious
Tags: buster sid

Some recent change in unstable makes golang-github-smartystreets-go-aws-auth 
FTBFS:

https://tests.reproducible-builds.org/debian/history/golang-github-smartystreets-go-aws-auth.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-smartystreets-go-aws-auth.html

...

   dh_auto_test -O--buildsystem=golang
go test -v -p 16 github.com/smartystreets/go-aws-auth
=== RUN   TestIntegration

  Given real credentials from environment variables 
A request (with out-of-order query string) with to IAM should succeed 
(assuming Administrator Access policy) ⚠
A request to S3 should succeed ⚠
A request to EC2 should succeed ⚠
A request to SQS should succeed ⚠
A request to SES should succeed ⚠
A request to Route 53 should succeed ⚠
A request to SimpleDB should succeed ⚠
If S3Resource env variable is set 
  A URL-signed request to that S3 resource should succeed ⚠


0 total assertions (one or more sections skipped)

--- PASS: TestIntegration (0.01s)
=== RUN   TestSign

  Requests to services using Version 2 should be signed accordingly ✔✔


2 total assertions (one or more sections skipped)


  Requests to services using Version 3 should be signed accordingly ✔✔


4 total assertions (one or more sections skipped)


  Requests to services using Version 4 should be signed accordingly ✔✔✔


7 total assertions (one or more sections skipped)


  Requests to services using existing credentials Version 2 should be signed 
accordingly ✔✔


9 total assertions (one or more sections skipped)


  Requests to services using existing credentials Version 3 should be signed 
accordingly ✔✔


11 total assertions (one or more sections skipped)


  Requests to services using existing credentials Version 4 should be signed 
accordingly ✔✔✔


14 total assertions (one or more sections skipped)

--- PASS: TestSign (0.00s)
=== RUN   TestExpiration

  Credentials without an expiration can't expire ✔


15 total assertions (one or more sections skipped)


  Credentials that expire in 5 minutes aren't expired ✔


16 total assertions (one or more sections skipped)


  Credentials that expire in 1 minute are expired ✔


17 total assertions (one or more sections skipped)


  Credentials that expired 2 hours ago are expired ✔


18 total assertions (one or more sections skipped)

--- PASS: TestExpiration (0.00s)
=== RUN   TestCommonFunctions

  Service and region should be properly extracted from host strings 
✔✔


32 total assertions (one or more sections skipped)


  MD5 hashes should be properly computed and base-64 encoded ✔


33 total assertions (one or more sections skipped)


  SHA-256 hashes should be properly hex-encoded (base 16) ✔


34 total assertions (one or more sections skipped)


  Given a key and contents 
HMAC-SHA256 should be properly computed ✔
HMAC-SHA1 should be properly computed ✔


36 total assertions (one or more sections skipped)


  Strings should be properly concatenated with a delimiter ✔✔✔


39 total assertions (one or more sections skipped)


  URI components should be properly encoded ✔✔✔


42 total assertions (one or more sections skipped)


  URI query strings should be properly encoded ✔


43 total assertions (one or more sections skipped)

--- PASS: TestCommonFunctions (0.00s)
=== RUN   TestSignatureS3

  Given a GET request to Amazon S3 
The request should be prepared with a Date header ✔
The CanonicalizedAmzHeaders should be built properly ✔
The CanonicalizedResource should be built properly ✔
The string to sign should be correct ✔
The final signature string should be exactly correct ✔


48 total assertions (one or more sections skipped)


  Given a GET request for a resource on S3 for query string authentication 
The string to sign should be correct ✔
The signature of string to sign should be correct ✔
The finished signed URL should be correct ✔


51 total assertions (one or more sections skipped)

--- PASS: TestSignatureS3 (0.00s)
=== RUN   TestS3STSRequestPreparer

  Given a plain request with no custom headers 
And a set of credentials with an STS token 
  It should include an X-Amz-Security-Token when the request is signed ✔✔


53 total assertions (one or more sections skipped)

--- PASS: TestS3STSRequestPreparer (0.00s)
=== RUN   TestCanonical
--- PASS: TestCanonical (0.00s)
=== RUN   TestSignature2

  Given bogus credentials 
Given a plain request that is unprepared 
  The request should be prepared to be signed ✔
Given a prepared, but unsigned, request 
  The canonical query string should be correct ✔
  The absolute path should be extracted correctly ✔
  The string to sign should be well-formed ✔
  The resulting signature should be correct ✔
  The final signed request should be correctly formed ✔


59 total assertions (one o

Bug#865026: marked as done (libusb.h: __linux usage makes ippusbxd FTBFS on ppc)

[Debian Bug Tracking System]

Your message dated Sat, 24 Jun 2017 21:34:55 +
with message-id 
and subject line Bug#865026: fixed in libusb-1.0 2:1.0.21-2
has caused the Debian Bug report #865026,
regarding libusb.h: __linux usage makes ippusbxd FTBFS on ppc
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.)


-- 
865026: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865026
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libusb-1.0-0-dev
Version: 2:1.0.21-1
Severity: serious
Tags: patch buster sid
Control: affects -1 src:ippusbxd

https://buildd.debian.org/status/fetch.php?pkg=ippusbxd&arch=ppc64el&ver=1.30-2&stamp=1497806137&raw=0

...
[ 50%] Building C object CMakeFiles/ippusbxd.dir/usb.c.o
/usr/bin/cc   -I/usr/include/libusb-1.0  -g -O2 
-fdebug-prefix-map=/«PKGBUILDDIR»=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -o2 -g -std=c99 -Wall 
-Wextra -pedantic -pedantic-errors   -o CMakeFiles/ippusbxd.dir/usb.c.o   -c 
/«PKGBUILDDIR»/src/usb.c
In file included from /«PKGBUILDDIR»/src/usb.c:23:0:
/usr/include/libusb-1.0/libusb.h:1815:67: warning: 'struct timeval' declared 
inside parameter list will not be visible outside of this definition or 
declaration
 int LIBUSB_CALL libusb_wait_for_event(libusb_context *ctx, struct timeval *tv);
   ^~~
/usr/include/libusb-1.0/libusb.h:1818:9: warning: 'struct timeval' declared 
inside parameter list will not be visible outside of this definition or 
declaration
  struct timeval *tv);
 ^~~
/usr/include/libusb-1.0/libusb.h:1820:9: warning: 'struct timeval' declared 
inside parameter list will not be visible outside of this definition or 
declaration
  struct timeval *tv, int *completed);
 ^~~
/usr/include/libusb-1.0/libusb.h:1824:9: warning: 'struct timeval' declared 
inside parameter list will not be visible outside of this definition or 
declaration
  struct timeval *tv);
 ^~~
/usr/include/libusb-1.0/libusb.h:1827:9: warning: 'struct timeval' declared 
inside parameter list will not be visible outside of this definition or 
declaration
  struct timeval *tv);
 ^~~
/«PKGBUILDDIR»/src/usb.c: In function 'usb_pump_events':
/«PKGBUILDDIR»/src/usb.c:519:50: error: passing argument 2 of 
'libusb_handle_events_timeout_completed' from incompatible pointer type 
[-Wincompatible-pointer-types]
 libusb_handle_events_timeout_completed(NULL, &tv, NULL);
  ^
In file included from /«PKGBUILDDIR»/src/usb.c:23:0:
/usr/include/libusb-1.0/libusb.h:1819:17: note: expected 'struct timeval *' but 
argument is of type 'struct timeval *'
 int LIBUSB_CALL libusb_handle_events_timeout_completed(libusb_context *ctx,
 ^~
CMakeFiles/ippusbxd.dir/build.make:134: recipe for target 
'CMakeFiles/ippusbxd.dir/usb.c.o' failed
make[4]: *** [CMakeFiles/ippusbxd.dir/usb.c.o] Error 1


__linux is not defined on ppc with -std=c99, the attached patch uses
__linux__ instead for the required #include 
Description: libusb.h: use __linux__ instead of __linux
 The check was added since sys/time.h is not available on windows,
 but breaks on ppc where __linux is not defined by gcc in strict
 standards modes.
Author: Adrian Bunk 

--- libusb-1.0-1.0.21.orig/libusb/libusb.h
+++ libusb-1.0-1.0.21/libusb/libusb.h
@@ -54,7 +54,7 @@ typedef unsigned __int32  uint32_t;
 #include 
 #endif
 
-#if defined(__linux) || defined(__APPLE__) || defined(__CYGWIN__) || 
defined(__HAIKU__)
+#if defined(__linux__) || defined(__APPLE__) || defined(__CYGWIN__) || 
defined(__HAIKU__)
 #include 
 #endif
 
--- End Message ---
--- Begin Message ---
Source: libusb-1.0
Source-Version: 2:1.0.21-2

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

Debian distribution maintenance software
pp.
Aurelien Jarno  (supplier of updated libusb-1.0 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 24 Jun 2017 2

Bug#865799: python-django-openstack-auth FTBFS with Django 1.11

[Adrian Bunk]

Source: python-django-openstack-auth
Version: 2.4.1-2
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-django-openstack-auth.html

...
set -e ; for pyversion in 2.7 3.5 ; do \
NOSE_WITH_OPENSTACK=1 \
NOSE_OPENSTACK_COLOR=1 \
NOSE_OPENSTACK_RED=0.05 \
NOSE_OPENSTACK_YELLOW=0.025 \
NOSE_OPENSTACK_SHOW_ELAPSED=1 \
PYTHONPATH=. python$pyversion openstack_auth/tests/run_tests.py ; \
done
No handlers could be found for logger "openstack_auth.utils"
.EE.
==
ERROR: test_websso_redirect_by_idp (tests.OpenStackAuthTestsWebSSO)
--
Traceback (most recent call last):
  File 
"/build/1st/python-django-openstack-auth-2.4.1/openstack_auth/tests/tests.py", 
line 916, in test_websso_redirect_by_idp
target_status_code=404)
  File "/usr/lib/python2.7/dist-packages/django/test/testcases.py", line 315, 
in assertRedirects
% (url, domain)
ValueError: The test client is unable to fetch remote URLs (got 
http://localhost:5000/v3/auth/OS-FEDERATION/identity_providers/158fb42243b744d1acc3300c5ab0ecc6/protocols/oidc/websso?origin=http://testserver/auth/websso/).
 If the host is served by Django, add 'localhost' to ALLOWED_HOSTS. Otherwise, 
use assertRedirects(..., fetch_redirect_response=False).

==
ERROR: test_websso_redirect_by_protocol (tests.OpenStackAuthTestsWebSSO)
--
Traceback (most recent call last):
  File 
"/build/1st/python-django-openstack-auth-2.4.1/openstack_auth/tests/tests.py", 
line 899, in test_websso_redirect_by_protocol
target_status_code=404)
  File "/usr/lib/python2.7/dist-packages/django/test/testcases.py", line 315, 
in assertRedirects
% (url, domain)
ValueError: The test client is unable to fetch remote URLs (got 
http://localhost:5000/v3/auth/OS-FEDERATION/websso/oidc?origin=http://testserver/auth/websso/).
 If the host is served by Django, add 'localhost' to ALLOWED_HOSTS. Otherwise, 
use assertRedirects(..., fetch_redirect_response=False).

--
Ran 52 tests in 12.500s

FAILED (errors=2)
Creating test database for alias 'default'...
System check identified no issues (0 silenced).
Destroying test database for alias 'default'...
debian/rules:14: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 2

Bug#865798: golang-github-shopify-sarama FTBFS: test failures

[Adrian Bunk]

Source: golang-github-shopify-sarama
Version: 1.9.0-2
Severity: serious
Tags: buster sid

Some recent change in unstable makes golang-github-shopify-sarama FTBFS:

https://tests.reproducible-builds.org/debian/history/golang-github-shopify-sarama.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-shopify-sarama.html

...
--- FAIL: TestMessageEncoding (0.00s)
request_test.go:32: Encoding empty gzip failed
got  [132 99 80 148 0 1 255 255 255 255 0 0 0 23 31 139 8 0 0 0 
0 0 0 255 1 0 0 255 255 0 0 0 0 0 0 0 0] 
want [97 79 149 90 0 1 255 255 255 255 0 0 0 23 31 139 8 0 0 9 
110 136 0 255 1 0 0 255 255 0 0 0 0 0 0 0 0]
...
FAIL
exit status 1
FAILgithub.com/Shopify/sarama   4.201s
...

Bug#864302: marked as done (request-tracker4: FTBFS due to base.pm changes in July 2016)

[Debian Bug Tracking System]

Your message dated Sat, 24 Jun 2017 21:18:52 +
with message-id 
and subject line Bug#864302: fixed in request-tracker4 4.2.8-3+deb8u2
has caused the Debian Bug report #864302,
regarding request-tracker4: FTBFS due to base.pm changes in July 2016
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.)


-- 
864302: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864302
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: request-tracker4
Version: 4.2.8-3+deb8u1
Severity: serious
Justification: ftbfs
Tags: jessie patch

As per

http://perl.debian.net/rebuild-logs/jessie/request-tracker4_4.2.8-3+deb8u1/request-tracker4_4.2.8-3+deb8u1_amd64-2017-06-05T20:11:50Z.build

building this package was broken by the changes in perl to fix the '.'
in @INC vulnerability.

The breakage doesn't appear in the version in unstable, though it's
not immediately obvious why. There is a proposed fix in

https://anonscm.debian.org/cgit/pkg-request-tracker/request-tracker4.git/log/?h=ntyni/jessie-base-pm

Dominic.
--- End Message ---
--- Begin Message ---
Source: request-tracker4
Source-Version: 4.2.8-3+deb8u2

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 10 Jun 2017 23:25:11 +0100
Source: request-tracker4
Binary: request-tracker4 rt4-clients rt4-standalone rt4-fcgi rt4-apache2 
rt4-db-postgresql rt4-db-mysql rt4-db-sqlite rt4-doc-html
Architecture: all source
Version: 4.2.8-3+deb8u2
Distribution: jessie-security
Urgency: high
Maintainer: Debian Request Tracker Group 

Changed-By: Dominic Hargreaves 
Closes: 864302
Description: 
 request-tracker4 - extensible trouble-ticket tracking system
 rt4-apache2 - Apache 2 specific files for request-tracker4
 rt4-clients - mail gateway and command-line interface to request-tracker4
 rt4-db-mysql - MySQL database backend for request-tracker4
 rt4-db-postgresql - PostgreSQL database backend for request-tracker4
 rt4-db-sqlite - SQLite database backend for request-tracker4
 rt4-doc-html - HTML documentation for request-tracker4
 rt4-fcgi   - External FastCGI support for request-tracker4
 rt4-standalone - Standalone web server support for request-tracker4
Changes:
 request-tracker4 (4.2.8-3+deb8u2) jessie-security; urgency=high
 .
   * Fix FTBFS due to base.pm changes (Closes: #864302)
   * Fix multiple security issues:
 - [CVE-2017-5943] CSRF verification token information leak
 - [CVE-2016-6127] XSS in file uploads
 - [CVE-2017-5361] Timing side-channel vulnerability in password
   verification
 - [CVE-2017-5944] Remote code execution in dashboard interface
 - Add check for incorrect RestrictLoginReferrer configuration setting
   * Work around a DoS vulnerability in Email::Address (CVE-2015-7686)
Checksums-Sha1: 
 253920f51e42317d0da074bcc88861b74f6f8cb2 5629 
request-tracker4_4.2.8-3+deb8u2.dsc
 000a7de7337b4f0ab60fb5dbed451e610b4183f3 78564 
request-tracker4_4.2.8-3+deb8u2.debian.tar.xz
 8f366bd8c54808ce4d468efc5b31d7edec5a779e 3073664 
request-tracker4_4.2.8-3+deb8u2_all.deb
 be38b9ffad749fe29b843b8baa4a58b41d32b144 51986 
rt4-clients_4.2.8-3+deb8u2_all.deb
 64e98c4fc9af467c918f163f0732bf121f40f1a8 16706 
rt4-standalone_4.2.8-3+deb8u2_all.deb
 745bf82d49eec132db122ab495b10d3f4c0f67ba 19066 rt4-fcgi_4.2.8-3+deb8u2_all.deb
 ec485cc6c5ad1138b321783bc243b0ba40617926 18016 
rt4-apache2_4.2.8-3+deb8u2_all.deb
 4241bf057937a41fb6825cb6c91b6493439c7da2 17326 
rt4-db-postgresql_4.2.8-3+deb8u2_all.deb
 fc27f3be4eadf0764a24a63475a684479dd572bc 17338 
rt4-db-mysql_4.2.8-3+deb8u2_all.deb
 9e67bc8d03f246f4d0673aa4ef1ae8c3ff246c5f 17438 
rt4-db-sqlite_4.2.8-3+deb8u2_all.deb
 05c7773b3494cea4655980956d1948e48916223f 982314 
rt4-doc-html_4.2.8-3+deb8u2_all.deb
Checksums-Sha256: 
 6f759c001d865196694323cd77c9e227a95904224bda0c84f057ebb873f5a5bd 5629 
request-tracker4_4.2.8-3+deb8u2.dsc
 7686f9ec7bea98d4c9fdecb76b6a846f55e2

Bug#862816: marked as done (wordpress: Six security bugs in wordpress 4.7.4 and earlier)

[Debian Bug Tracking System]

Your message dated Sat, 24 Jun 2017 21:19:24 +
with message-id 
and subject line Bug#862816: fixed in wordpress 4.1+dfsg-1+deb8u14
has caused the Debian Bug report #862816,
regarding wordpress: Six security bugs in wordpress 4.7.4 and earlier
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.)


-- 
862816: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862816
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wordpress
Version: 4.7.4+dfsg-1
Severity: grave
Tags: upstream security
Justification: user security hole

Wordpress 4.7.4 and earlier has 6 security holes that are fixed in
4.7.5[1]

 * 2.7.0 - 4.7.4
   Insufficient redirect validation in the HTTP class.
 * 2.5.0 - 4.7.4
   Improper handling of post meta data values in the XML-RPC API.
 * 3.4.0 - 4.7.4
   Lack of capability checks for post meta data in the XML-RPC API.
 * 2.5.0 - 4.7.4
   A Cross Site Request Forgery (CRSF) vulnerability was discovered in the
   filesystem credentials dialog.
 * 3.3 - 4.7.4
   A cross-site scripting (XSS) vulnerability was discovered when
   attempting to upload very large files.
 * 3.4.0 - 4.6.4
   A cross-site scripting (XSS) vulnerability was discovered related to the
   Customizer.

Looking at the versions, all distributions are vulnerable to all bugs,
yay me!

I'll request the CVEs and update when I get them.

1: https://wordpress.org/news/2017/05/wordpress-4-7-5/


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

Kernel: Linux 4.9.0-2-amd64 (SMP w/6 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: wordpress
Source-Version: 4.1+dfsg-1+deb8u14

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

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

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

Debian distribution maintenance software
pp.
Craig Small  (supplier of updated wordpress package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 24 May 2017 22:24:48 +1000
Source: wordpress
Binary: wordpress wordpress-l10n wordpress-theme-twentyfifteen 
wordpress-theme-twentyfourteen wordpress-theme-twentythirteen
Architecture: source all
Version: 4.1+dfsg-1+deb8u14
Distribution: stable
Urgency: medium
Maintainer: Craig Small 
Changed-By: Craig Small 
Description:
 wordpress  - weblog manager
 wordpress-l10n - weblog manager - language files
 wordpress-theme-twentyfifteen - weblog manager - twentytfifteen theme files
 wordpress-theme-twentyfourteen - weblog manager - twentyfourteen theme files
 wordpress-theme-twentythirteen - weblog manager - twentythirteen theme files
Closes: 862053 862816
Changes:
 wordpress (4.1+dfsg-1+deb8u14) jessie-security; urgency=medium
 .
   * Backport patches from 4.7.5 Closes: #862816
- CVE-2017-9062
  Improper handling of post meta data values in the XML-RPC API.
  Changeset 40699
- CVE-2017-9065
  Lack of capability checks for post meta data in the XML-RPC API.
  Changeset 40684
- CVE-2017-9064
  A Cross Site Request Forgery (CRSF) vulnerability was discovered
  in the filesystem credentials dialog.
  Changeset 40730
- CVE-2017-9061
  A cross-site scripting (XSS) vulnerability was discovered when
  attempting to upload very large files.
  Changeset 40743
- CVE-2017-9063
  A cross-site scripting (XSS) vulnerability was discovered related
  to the Customizer.
  Changeset 40711
   * CVE-2017-9066 not fixed as the relevant code has changed dramatically
 and there is no upstream patch for it.
 Insufficient redirect validation in the HTTP class.
   * CVE-2017-8295 Don't use client-provided data to form password reset
 from email address, from WordPress ticket #23239 Closes: #862053
Checksums-Sha1:
 6992e217144edb572b91420cf4668a316d2f6cce 2206 wordpress_4.1+dfsg-1+deb8u14.dsc
 aecf3343a5b0b3b5e559a7e1eb41b32f2259414e 6129728 
wordpress_4.1+dfsg-1+deb8u14.debian.

Bug#864424: marked as done (tor onion services: remote assertion failure)

[Debian Bug Tracking System]

Your message dated Sat, 24 Jun 2017 21:19:19 +
with message-id 
and subject line Bug#864424: fixed in tor 0.2.5.14-1
has caused the Debian Bug report #864424,
regarding tor onion services: remote assertion failure
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.)


-- 
864424: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864424
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tor
Version: 0.2.2.1-alpha-1
Severity: serious
Tags: security

There is a remotely triggerable assertion failure in Tor onion services.

This is a DoS issue for any tor instance providing an onion service.
Tor in all of Debian's suites is affected.

It's tracked as TROVE-2017-005, https://bugs.torproject.org/22494, 
CVE-2017-0376.


[Additionally, Tor in experimental is affected by TROVE-2017-004,
 https://bugs.torproject.org/22493 CVE-2017-0375.]
-- 
|  .''`.   ** Debian **
  Peter Palfrader   | : :' :  The  universal
 https://www.palfrader.org/ | `. `'  Operating System
|   `-https://www.debian.org/
--- End Message ---
--- Begin Message ---
Source: tor
Source-Version: 0.2.5.14-1

We believe that the bug you reported is fixed in the latest version of
tor, 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.
Peter Palfrader  (supplier of updated tor 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: Thu, 08 Jun 2017 20:19:22 +0200
Source: tor
Binary: tor tor-dbg tor-geoipdb
Architecture: source all
Version: 0.2.5.14-1
Distribution: jessie-security
Urgency: medium
Maintainer: Peter Palfrader 
Changed-By: Peter Palfrader 
Description:
 tor- anonymizing overlay network for TCP
 tor-dbg- debugging symbols for Tor
 tor-geoipdb - GeoIP database for Tor
Closes: 864424
Changes:
 tor (0.2.5.14-1) jessie-security; urgency=medium
 .
   * New upstream version, fixing a hidden service related Denial of
 Service bug:
 - Fix a remotely triggerable assertion failure caused by receiving a
   BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
   22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
   on 0.2.2.1-alpha.  (closes: #864424)
   * The previous release, 0.2.5.13, already incorporates the changes made in
 Debian's updates of the 0.2.5.12 version.  Therefore, drop
 - debian/patches/tor-bug-20384-TROVE-2016-10-001
 - debian/patches/tor-bug-21018-TROVE-2016-12-002-CVE-2016-1254
 - debian/patches/update-authority-set
Checksums-Sha1:
 12a3d1b7f9d69bce58271ecda9fd1f12b51f5520 1761 tor_0.2.5.14-1.dsc
 f623ab0866a7a9ab881c81f9cbdbea59f821a88d 3685957 tor_0.2.5.14.orig.tar.gz
 be3484574c906b7cacf00362a4271c66980e70b0 35155 tor_0.2.5.14-1.diff.gz
 e7b34125211ff9e268b18cb85753208254f9df95 1015592 tor-geoipdb_0.2.5.14-1_all.deb
Checksums-Sha256:
 e6b7f0a197d95764917de7e55d10715ef57f1ffb014df99e04b9a56f8c8324a3 1761 
tor_0.2.5.14-1.dsc
 114f6925add7ab88ea36aea0229f9b9b7c05971d2316b040b3811350f7f3ff34 3685957 
tor_0.2.5.14.orig.tar.gz
 47acb67c827a5b6d31441155337b16f25938758d953c863c1a2cf2d654f1d79e 35155 
tor_0.2.5.14-1.diff.gz
 ac4a50ed2d72f144f66a287cc21e8134b6f5e7c8b7cf4ce965d190d7d8f63693 1015592 
tor-geoipdb_0.2.5.14-1_all.deb
Files:
 58bc512b55a7be961fea1722c94214b9 1761 net optional tor_0.2.5.14-1.dsc
 388484043ded7963c24d8e71bf07 3685957 net optional tor_0.2.5.14.orig.tar.gz
 4c7457ad31fff946bc41d9fe20d6dfeb 35155 net optional tor_0.2.5.14-1.diff.gz
 cd5b6da1102d9d9366a73e6d0d173323 1015592 net extra 
tor-geoipdb_0.2.5.14-1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBCAAGBQJZOZ6lAAoJEIYCyCA4cjMft90IAJ4rOtT+39m+KeVoyBTx2A9z
xan24457x0P5Jr6zdlpFLyNj9vtC5e4igtPrt/nAqJGRIskMEm3eRUozLkLZuaoL
U29SX2BMkqfcvOyRK3CIzS4oQ5IYWMMsfXBlDA6K2o3cU6s+vIuIrjSC55M3lfoE
lZxJCOpwzAT86ldX8GsDnkf0jnegpGTNmgONCdLNKHk8FSq9/15WCS8Xdkt6eSOy
v2Nxq7sE7WKpBEcFoqNCTIDt2/l/owg8QnCq3PJzeWt0kv6blhbF5y8GBXNHXndo
YIDBzjbdcHT3MPLb0MPzJ8/km7ChGJzUnUUE+A+uhxZf/0uNPD+WUc5YW/AxVPk=
=FBqb
-END PGP SIGNATURE End Message ---

Bug#864859: marked as done (jython: CVE-2016-4000: Unsafe deserialization leads to code execution)

[Debian Bug Tracking System]

Your message dated Sat, 24 Jun 2017 21:18:27 +
with message-id 
and subject line Bug#864859: fixed in jython 2.5.3-3+deb8u1
has caused the Debian Bug report #864859,
regarding jython: CVE-2016-4000: Unsafe deserialization leads to code execution
to be marked as done.

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

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


-- 
864859: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864859
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jython
Version: 2.5.3-1
Severity: grave
Tags: security upstream patch
Justification: user security hole
Forwarded: http://bugs.jython.org/issue2454

Hi,

the following vulnerability was published for jython.

CVE-2016-4000[0]:
Unsafe deserialization leads to 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-2016-4000
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-4000
[1] http://bugs.jython.org/issue2454
[2] https://hg.python.org/jython/rev/d06e29d100c0

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: jython
Source-Version: 2.5.3-3+deb8u1

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 21 Jun 2017 20:00:46 +0200
Source: jython
Binary: jython jython-doc
Architecture: source all
Version: 2.5.3-3+deb8u1
Distribution: jessie-security
Urgency: high
Maintainer: Debian Java Maintainers 

Changed-By: Markus Koschany 
Description:
 jython - Python seamlessly integrated with Java
 jython-doc - Jython documentation including API docs
Closes: 864859
Changes:
 jython (2.5.3-3+deb8u1) jessie-security; urgency=high
 .
   * Team upload.
   * Fix CVE-2016-4000: (Closes: #864859)
 Unsafe deserialization may lead to arbitrary code execution.
Checksums-Sha1:
 4005e55e8d99f71940f14f0c51dc8df2efc8d0dd 2446 jython_2.5.3-3+deb8u1.dsc
 fb2329935da29375f6c58e80c361a22fef1ce694 5731140 jython_2.5.3.orig.tar.bz2
 a6106611a19d6f324757fb976c41bc41337fade2 17596 
jython_2.5.3-3+deb8u1.debian.tar.xz
 18ce5190589356499a998adf875a8587a2414620 6907190 jython_2.5.3-3+deb8u1_all.deb
 fa7c89c99e7b94b958c91bab5b09a50beafab9cc 562942 
jython-doc_2.5.3-3+deb8u1_all.deb
Checksums-Sha256:
 5191fd859007cd558a4b600918cd40440c5b5ae259ddf21ae21b65f58446e362 2446 
jython_2.5.3-3+deb8u1.dsc
 f65ba40098f9312ed487219e64c4ea01fecad927411b1a72dc1d8cadf0ddc947 5731140 
jython_2.5.3.orig.tar.bz2
 68c7122d199e3a519af4fc9f3b1c8e29dac6bd3273811aa4e77a6136f3ca46eb 17596 
jython_2.5.3-3+deb8u1.debian.tar.xz
 076576f62ae93a87023ad6747e4b64a51493cbd83c32e17198786f255643e1b0 6907190 
jython_2.5.3-3+deb8u1_all.deb
 67cae1441b8920d64b8fd367574fe158e77c9bc7b6d8978da97640cbcb6d77d0 562942 
jython-doc_2.5.3-3+deb8u1_all.deb
Files:
 49d2d2a7471f5885a28bc4b65b5651aa 2446 python optional jython_2.5.3-3+deb8u1.dsc
 2e4210614f20aa3cbcef9031601679b7 5731140 python optional 
jython_2.5.3.orig.tar.bz2
 73652c76868ae57b1c2dc6c5c6b916df 17596 python optional 
jython_2.5.3-3+deb8u1.debian.tar.xz
 5fd2131a593cd812db4eb8b8e4708c8a 6907190 python optional 
jython_2.5.3-3+deb8u1_all.deb
 39b58e3821690eeccb2fd7cc308265ed 562942 doc optional 
jython-doc_2.5.3-3+deb8u1_all.deb

-BEGIN PGP SIGNATURE-

iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAllKtnRfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD
RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp
YW4ub3JnAAoJENmtFLlRO1Hk6iUP/jmih+vt+iwtlC3rlonw8flekw8++Ek3dpGL
Gq50Kpw7hFs4IRGCuV7cTXrgYXfmNtJ0ZxvlC5ILCV4qgxVCfZ7QVttsi6GnKsCg
QueDIaTmKikj+1qz5zke6B84mTVnVJCMQiP0jh2rB/KLl4UAB2DoILR4UTm5JmVb
4TcMq0unACkcvSxhmgIPpSw2azMGbVYon62h6ptmyZ6E19bLqVXDecGpo+DvKSdi
igXQp9sBusfwp4Dv8kPdnnQ4MIipTRc48yNI+eP5H4AaRBpmLoC36TFJjQ9+vCRa
28X9v6nv3So3Ilwgqx4Sl7FdE4vCePss9aemkMlq0GcZFyzn45u4S757ztGOgSl8
3bj5HVFIFGdHeyJ0jsOS1lyLg8C6FlaSDnG

Bug#865498: marked as done (drupal7: CVE-2017-6922: Files uploaded by anonymous users into a private file system can be accessed by other anonymous users)

[Debian Bug Tracking System]

Your message dated Sat, 24 Jun 2017 21:17:43 +
with message-id 
and subject line Bug#865498: fixed in drupal7 7.32-1+deb8u9
has caused the Debian Bug report #865498,
regarding drupal7: CVE-2017-6922: Files uploaded by anonymous users into a 
private file system can be accessed by other anonymous users
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.)


-- 
865498: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865498
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: drupal7
Version: 7.52-2
Severity: normal
Tags: security patch upstream fixed-upstream

Hi,

the following vulnerability was published for drupal7.

CVE-2017-6922[0]:
|Files uploaded by anonymous users into a private file system can be
|accessed by other anonymous users

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-6922
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-6922

Please adjust the affected versions in the BTS as needed. Is jessie as
well affected with based version 7.32?

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: drupal7
Source-Version: 7.32-1+deb8u9

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

Debian distribution maintenance software
pp.
Gunnar Wolf  (supplier of updated drupal7 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: Thu, 22 Jun 2017 11:31:48 -0500
Source: drupal7
Binary: drupal7
Architecture: source all
Version: 7.32-1+deb8u9
Distribution: jessie-security
Urgency: high
Maintainer: Luigi Gangitano 
Changed-By: Gunnar Wolf 
Description:
 drupal7- fully-featured content management framework
Closes: 865498
Changes:
 drupal7 (7.32-1+deb8u9) jessie-security; urgency=high
 .
   * Backported from 7.41: SA-CORE-2015-004: Open redirect (CVE-2015-
 7943)
   * Backported from 7.56: SA-CORE-2017-003: Files uploaded by anonymous
 users into a private file system can be accessed by other anonymous
 users. (CVE-2017-6922) (Closes: #865498)
   * Updated patches noting the CVE IDs they address (many were sent out
 before a CVE was assigned)
Checksums-Sha1:
 edadb618485953aec6c5526633b97f52fd9f20bb 1911 drupal7_7.32-1+deb8u9.dsc
 c673dfec976d86ec6079d503dc9d81f2cb73d262 3207974 drupal7_7.32.orig.tar.gz
 b1490cb8887870c8ea6c46faf71a53554cea6d6d 201136 
drupal7_7.32-1+deb8u9.debian.tar.xz
 1b2d7e19d889390a43906a08e6e48264cbfd5ac6 2473314 drupal7_7.32-1+deb8u9_all.deb
 a95fdc3819dd137a8d1992dab1462a1b3872a577 8437 
drupal7_7.32-1+deb8u9_amd64.buildinfo
Checksums-Sha256:
 95bddc9e16b97c7ca8ee069e1e2bb40d53b3f212c2baa587e6dcb7fe105306cf 1911 
drupal7_7.32-1+deb8u9.dsc
 f5e6efc7269d1a6e35788ed84022da7da3edd9f7d5c7e5cfa04302de366cf206 3207974 
drupal7_7.32.orig.tar.gz
 59478479510c19ec36fae37afc93d1aa0798c616f4f5e7683b1dab4d1d4f857a 201136 
drupal7_7.32-1+deb8u9.debian.tar.xz
 3b3f8838d0382bf17efebcf65d5d7b0f57448c574c344b8d50c76bf5b3268805 2473314 
drupal7_7.32-1+deb8u9_all.deb
 eb8c74569835e463292ca9ac4659fe96e421573a1cd51daf494b9a2a384d36e9 8437 
drupal7_7.32-1+deb8u9_amd64.buildinfo
Files:
 21347d6fa7b1740cefa6b4339b81cdbc 1911 web extra drupal7_7.32-1+deb8u9.dsc
 54754efc64474e8b9e0f8507a9f0ddca 3207974 web extra drupal7_7.32.orig.tar.gz
 38e63f9bff96eab90d2993f8d6219db6 201136 web extra 
drupal7_7.32-1+deb8u9.debian.tar.xz
 9feab23334d72808f7d858a1012ea28c 2473314 web extra 
drupal7_7.32-1+deb8u9_all.deb
 91c202f56f2ede36e053d70b17951503 8437 web extra 
drupal7_7.32-1+deb8u9_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEq0HBxor9ZoygRev4ZzoD5MHbkh8FAllL9I0ACgkQZzoD5MHb
kh+l1A/9Fmr3x8kcuXI2D5X2WLd+ZodIdAL3wyR6lZw/TyfdOAqmGBCbgXth+uWa
hPw+B9V09GwvEr27aah6r0SJ+suIBrZNheITkPD4osTIq5TkqaEUooV7uzja7hsT
KHWuLYn17qC7bQQebe9RsA+qKlvdpJ47onx4R0t/GjC00uoiKaqyJ9FHhaTNyHYD
GpIHI+cY0gv0KE8jPOtBYc/3gFSFJzdaSk5baaNLGqs5gRochnHO+HMo8PGQjmNv
5MG/lRToJIM4HO44e6HEm/PZQKNf0vMx0GNG7pD3brC21WuYdvdHgGEkgu+ACm

Bug#862053: marked as done (wordpress: CVE-2017-8295)

[Debian Bug Tracking System]

Your message dated Sat, 24 Jun 2017 21:19:24 +
with message-id 
and subject line Bug#862053: fixed in wordpress 4.1+dfsg-1+deb8u14
has caused the Debian Bug report #862053,
regarding wordpress: CVE-2017-8295
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.)


-- 
862053: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862053
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wordpress
X-Debbugs-CC: t...@security.debian.org 
secure-testing-t...@lists.alioth.debian.org
Severity: important
Tags: security

Hi,

the following vulnerability was published for wordpress.

CVE-2017-8295[0]:
| WordPress through 4.7.4 relies on the Host HTTP header for a
| password-reset e-mail message, which makes it easier for remote
| attackers to reset arbitrary passwords by making a crafted
| wp-login.php?action=lostpassword request and then arranging for this
| message to bounce or be resent, leading to transmission of the reset
| key to a mailbox on an attacker-controlled SMTP server. This is
| related to problematic use of the SERVER_NAME variable in
| wp-includes/pluggable.php in conjunction with the PHP mail function.
| Exploitation is not achievable in all cases because it requires at
| least one of the following: (1) the attacker can prevent the victim
| from receiving any e-mail messages for an extended period of time
| (such as 5 days), (2) the victim's e-mail system sends an autoresponse
| containing the original message, or (3) the victim manually composes a
| reply containing the original message.

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

No official patch has been published yet but there is an interesting assessment
at 
http://blog.dewhurstsecurity.com/2017/05/04/exploitbox-wordpress-security-advisories.html

I think it makes sense to wait for an official Wordpress response but we could 
also
try to avoid the SERVER_NAME variable in this case.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-8295
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-8295

Please adjust the affected versions in the BTS as needed.



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: wordpress
Source-Version: 4.1+dfsg-1+deb8u14

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

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

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

Debian distribution maintenance software
pp.
Craig Small  (supplier of updated wordpress package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 24 May 2017 22:24:48 +1000
Source: wordpress
Binary: wordpress wordpress-l10n wordpress-theme-twentyfifteen 
wordpress-theme-twentyfourteen wordpress-theme-twentythirteen
Architecture: source all
Version: 4.1+dfsg-1+deb8u14
Distribution: stable
Urgency: medium
Maintainer: Craig Small 
Changed-By: Craig Small 
Description:
 wordpress  - weblog manager
 wordpress-l10n - weblog manager - language files
 wordpress-theme-twentyfifteen - weblog manager - twentytfifteen theme files
 wordpress-theme-twentyfourteen - weblog manager - twentyfourteen theme files
 wordpress-theme-twentythirteen - weblog manager - twentythirteen theme files
Closes: 862053 862816
Changes:
 wordpress (4.1+dfsg-1+deb8u14) jessie-security; urgency=medium
 .
   * Backport patches from 4.7.5 Closes: #862816
- CVE-2017-9062
  Improper handling of post meta data values in the XML-RPC API.
  Changeset 40699
- CVE-2017-9065
  Lack of capability checks for post meta data in the XML-RPC API.
  Changeset 40684
- CVE-2017-9064
  A Cross Site Request Forgery (CRSF) vulnerability was discovered
  in the filesystem credentials dialog.
  Changeset 40730
- CVE-2017-9061
  A cross-site scripting (XSS) vulnerability was discovered when
  attempting to upload very large files.
  Changeset 40743
- CVE-2017-9063
  A cross-site scripting (XSS) vulnerability was discovered related
  to the Customizer.
  Changeset

Bug#865797: signond FTBFS: symbol changes

[Adrian Bunk]

Source: signond
Version: 8.59-1
Severity: serious
Tags: buster sid

Some recent change in unstable makes signond FTBFS:

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

...
   dh_makeshlibs -O-Bbuild/qt5 -O--parallel
dpkg-gensymbols: warning: debian/libsignon-qt5-1/DEBIAN/symbols doesn't match 
completely debian/libsignon-qt5-1.symbols
--- debian/libsignon-qt5-1.symbols (libsignon-qt5-1_8.59-1_amd64)
+++ dpkg-gensymbolsMvafsq   2018-07-26 21:09:03.368772123 -1200
@@ -56,8 +56,8 @@
  _ZN6SignOn12IdentityInfoD1Ev@Base 8.57+20150423
  _ZN6SignOn12IdentityInfoD2Ev@Base 8.57+20150423
  _ZN6SignOn12IdentityInfoaSERKS0_@Base 8.57+20150423
- (optional=inline)_ZN6SignOn5ErrorC1EiRK7QString@Base 8.57+20150423
- (optional=inline)_ZN6SignOn5ErrorC2EiRK7QString@Base 8.57+20150423
+#MISSING: 8.59-1# (optional=inline)_ZN6SignOn5ErrorC1EiRK7QString@Base 
8.57+20150423
+#MISSING: 8.59-1# (optional=inline)_ZN6SignOn5ErrorC2EiRK7QString@Base 
8.57+20150423
  _ZN6SignOn5ErrorD0Ev@Base 8.57+20150423
  _ZN6SignOn5ErrorD1Ev@Base 8.57+20150423
  _ZN6SignOn5ErrorD2Ev@Base 8.57+20150423
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: warning: debian/libsignon-plugins-common1/DEBIAN/symbols 
doesn't match completely debian/libsignon-plugins-common1.symbols
--- debian/libsignon-plugins-common1.symbols 
(libsignon-plugins-common1_8.59-1_amd64)
+++ dpkg-gensymbolsVmmzQ3   2018-07-26 21:09:03.756772123 -1200
@@ -1,9 +1,9 @@
 libsignon-plugins-common.so.1 libsignon-plugins-common1 #MINVER#
  (optional=templinst|arch=mips64el 
mipsel)_Z17qRegisterMetaTypeI13QDBusArgumentEiPKcPT_N9QtPrivate21MetaTypeDefinedHelperIS3_Xaasr12QMetaTypeId2IS3_E7DefinedntsrS8_9IsBuiltInEE11DefinedTypeE@Base
 8.57+20150423
  _Z23expandDBusArgumentValueRK8QVariantPb@Base 8.57+20150423
- 
(optional=templinst|arch=amd64)_Z27qRegisterNormalizedMetaTypeI13QDBusArgumentEiRK10QByteArrayPT_N9QtPrivate21MetaTypeDefinedHelperIS4_Xaasr12QMetaTypeId2IS4_E7DefinedntsrS9_9IsBuiltInEE11DefinedTypeE@Base
 8.57+20150423
- 
(optional=templinst)_ZN17QtMetaTypePrivate23QMetaTypeFunctionHelperI13QDBusArgumentLb1EE6CreateEPKv@Base
 8.57+20150423
- 
(optional=templinst)_ZN17QtMetaTypePrivate23QMetaTypeFunctionHelperI13QDBusArgumentLb1EE6DeleteEPv@Base
 8.57+20150423
+#MISSING: 8.59-1# 
(optional=templinst|arch=amd64)_Z27qRegisterNormalizedMetaTypeI13QDBusArgumentEiRK10QByteArrayPT_N9QtPrivate21MetaTypeDefinedHelperIS4_Xaasr12QMetaTypeId2IS4_E7DefinedntsrS9_9IsBuiltInEE11DefinedTypeE@Base
 8.57+20150423
+#MISSING: 8.59-1# 
(optional=templinst)_ZN17QtMetaTypePrivate23QMetaTypeFunctionHelperI13QDBusArgumentLb1EE6CreateEPKv@Base
 8.57+20150423
+#MISSING: 8.59-1# 
(optional=templinst)_ZN17QtMetaTypePrivate23QMetaTypeFunctionHelperI13QDBusArgumentLb1EE6DeleteEPv@Base
 8.57+20150423
  
(optional=templinst)_ZN17QtMetaTypePrivate23QMetaTypeFunctionHelperI13QDBusArgumentLb1EE8DestructEPv@Base
 8.57+20150423
  
(optional=templinst)_ZN17QtMetaTypePrivate23QMetaTypeFunctionHelperI13QDBusArgumentLb1EE9ConstructEPvPKv@Base
 8.57+20150423
  (optional=templinst)_ZN4QMapI7QString8QVariantE13detach_helperEv@Base 
8.57+20150423
@@ -30,6 +30,8 @@
  
(optional=templinst)_ZN7QVectorI10QByteArrayE11reallocDataEii6QFlagsIN10QArrayData16AllocationOptionEE@Base
 8.57+20150423
  (optional=templinst)_ZN7QVectorI10QByteArrayE6appendERKS0_@Base 8.57+20150423
  (optional=templinst)_ZN8QMapNodeI7QString8QVariantE14destroySubTreeEv@Base 
8.57+20150423
+ _ZN9QtPrivate16StreamStateSaverD1Ev@Base 8.59-1
+ _ZN9QtPrivate16StreamStateSaverD2Ev@Base 8.59-1
  _ZNK6SignOn13BlobIOHandler10metaObjectEv@Base 8.57+20150423
  
(optional=templinst)_ZNK8QMapNodeI7QString8QVariantE4copyEP8QMapDataIS0_S1_E@Base
 8.57+20150423
  _ZTVN6SignOn13BlobIOHandlerE@Base 8.57+20150423
@@ -37,16 +39,16 @@
  
(optional=templinst)_ZrsI7QString8QVariantER11QDataStreamS3_R4QMapIT_T0_E@Base 
8.57+20150423
 libsignon-plugins.so.1 libsignon-plugins-common1 #MINVER#
  
(optional=templinst)_Z17qRegisterMetaTypeIN6SignOn5ErrorEEiPKcPT_N9QtPrivate21MetaTypeDefinedHelperIS4_Xaasr12QMetaTypeId2IS4_E7DefinedntsrS9_9IsBuiltInEE11DefinedTypeE@Base
 8.57+20150423
- 
(optional=templinst)_ZN17QtMetaTypePrivate23QMetaTypeFunctionHelperIN6SignOn11SessionDataELb1EE6CreateEPKv@Base
 8.57+20150423
- 
(optional=templinst)_ZN17QtMetaTypePrivate23QMetaTypeFunctionHelperIN6SignOn11SessionDataELb1EE6DeleteEPv@Base
 8.57+20150423
+#MISSING: 8.59-1# 
(optional=templinst)_ZN17QtMetaTypePrivate23QMetaTypeFunctionHelperIN6SignOn11SessionDataELb1EE6CreateEPKv@Base
 8.57+20150423
+#MISSING: 8.59-1# 
(optional=templinst)_ZN17QtMetaTypePrivate23QMetaTypeFunctionHelperIN6SignOn11SessionDataELb1EE6DeleteEPv@Base
 8.57+20150423
  
(optional=templinst)_ZN17QtMetaTypePrivate23QMetaTypeFunctionHelperIN6SignOn11SessionDataELb1EE8DestructEPv@Base
 8.57+20150423
  
(optional=templinst)_ZN17QtMetaTypePrivate23QMetaTypeFuncti

Bug#865796: ginkgocadx FTBFS with libdcmtk-dev 3.6.1~20170228-2

[Adrian Bunk]

Source: ginkgocadx
Version: 3.8.4-1
Severity: serious
Tags: buster sid

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

...
cd /<>/obj-x86_64-linux-gnu/cadxcore && /usr/bin/c++   -DAPIEXPORT 
-DCURL_STATICLIB -DGINKGO_ARCH_x86_64 -DGINKGO_CODENAME=\"\" 
-DGINKGO_VERSION=\"3.8.4\" -DHAVE_CONFIG_H -DINTERNET_DIST 
-DITK_IO_FACTORY_REGISTER_MANAGER -DLINUX -DMONOLITIC -DUSE_SYSTEM_SQLITE 
-DUSING_EXTENSIONS -DWXUSINGDLL -D_FILE_OFFSET_BITS=64 -D__WXGTK__ 
-DvtkFiltersFlowPaths_AUTOINIT="1(vtkFiltersParallelFlowPaths)" 
-DvtkIOExodus_AUTOINIT="1(vtkIOParallelExodus)" 
-DvtkIOGeometry_AUTOINIT="1(vtkIOMPIParallel)" 
-DvtkIOImage_AUTOINIT="1(vtkIOMPIImage)" 
-DvtkIOParallel_AUTOINIT="1(vtkIOMPIParallel)" 
-DvtkIOSQL_AUTOINIT="2(vtkIOMySQL,vtkIOPostgreSQL)" 
-DvtkRenderingContext2D_AUTOINIT="1(vtkRenderingContextOpenGL)" 
-DvtkRenderingCore_AUTOINIT="3(vtkInteractionStyle,vtkRenderingFreeType,vtkRenderingOpenGL)"
 
-DvtkRenderingFreeType_AUTOINIT="2(vtkRenderingFreeTypeFontConfig,vtkRenderingMatplotlib)"
 -DvtkRenderingLIC_AUTOINIT="1(vtkRenderingParallelLIC)" 
-DvtkRenderingVolume_AUTOINIT="1(vtkRenderingVolumeOpe
 nGL)" 
-I/<>/obj-x86_64-linux-gnu/cadxcore/ITKIOFactoryRegistration 
-I/usr/include/gdcm-2.6 -isystem /usr/include/ITK-4.10 -I/usr/include/cairo 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include 
-I/usr/include/gio-unix-2.0 -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/harfbuzz 
-I/usr/include/x86_64-linux-gnu -I/<>/cadxcore/CADxCore 
-I/<>/cadxcore -I/<>/cadxcore/vtk 
-I/<>/cadxcore/itk -I/<>/cadxcore/wx 
-I/<>/cadxcore/wx/VTK -I/<>/cadxcore/VTKInria3D 
-I/<>/cadxcore/VTKInria3D/wxVTK -I/usr/include/jsoncpp 
-I/<>/../lib/Linux-x86_64/libcurl-7.28.1/include 
-I/usr/lib/x86_64-linux-gnu/wx/include/gtk2-unicode-3.0 -I/usr/include/wx-3.0 
-I/usr/include/vtk-6.3 -I/us
 r/lib/x86_64-linux-gnu/openmpi/include/openmpi 
-I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi/opal/mca/event/libevent2022/libevent
 
-I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi/opal/mca/event/libevent2022/libevent/include
 -I/usr/lib/x86_64-linux-gnu/openmpi/include -I/usr/include/python2.7 
-I/usr/include/hdf5/openmpi -I/usr/include/libxml2 -I/usr/include/tcl 
-I/usr/lib/i386-linux-gnu/glib-2.0/include -I/usr/include/libpng12 
-I/usr/lib/gtk-2.0/include  -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -DNDEBUG -fPIC  -std=c++11 -o 
CMakeFiles/CADxCore.dir/api/dicom/icustomassociation.cpp.o -c 
/<>/cadxcore/api/dicom/icustomassociation.cpp
[ 11%] Building CXX object 
cadxcore/CMakeFiles/CADxCore.dir/api/dicom/idicom.cpp.o
cd /<>/obj-x86_64-linux-gnu/cadxcore && /usr/bin/c++   -DAPIEXPORT 
-DCURL_STATICLIB -DGINKGO_ARCH_x86_64 -DGINKGO_CODENAME=\"\" 
-DGINKGO_VERSION=\"3.8.4\" -DHAVE_CONFIG_H -DINTERNET_DIST 
-DITK_IO_FACTORY_REGISTER_MANAGER -DLINUX -DMONOLITIC -DUSE_SYSTEM_SQLITE 
-DUSING_EXTENSIONS -DWXUSINGDLL -D_FILE_OFFSET_BITS=64 -D__WXGTK__ 
-DvtkFiltersFlowPaths_AUTOINIT="1(vtkFiltersParallelFlowPaths)" 
-DvtkIOExodus_AUTOINIT="1(vtkIOParallelExodus)" 
-DvtkIOGeometry_AUTOINIT="1(vtkIOMPIParallel)" 
-DvtkIOImage_AUTOINIT="1(vtkIOMPIImage)" 
-DvtkIOParallel_AUTOINIT="1(vtkIOMPIParallel)" 
-DvtkIOSQL_AUTOINIT="2(vtkIOMySQL,vtkIOPostgreSQL)" 
-DvtkRenderingContext2D_AUTOINIT="1(vtkRenderingContextOpenGL)" 
-DvtkRenderingCore_AUTOINIT="3(vtkInteractionStyle,vtkRenderingFreeType,vtkRenderingOpenGL)"
 
-DvtkRenderingFreeType_AUTOINIT="2(vtkRenderingFreeTypeFontConfig,vtkRenderingMatplotlib)"
 -DvtkRenderingLIC_AUTOINIT="1(vtkRenderingParallelLIC)" 
-DvtkRenderingVolume_AUTOINIT="1(vtkRenderingVolumeOpe
 nGL)" 
-I/<>/obj-x86_64-linux-gnu/cadxcore/ITKIOFactoryRegistration 
-I/usr/include/gdcm-2.6 -isystem /usr/include/ITK-4.10 -I/usr/include/cairo 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include 
-I/usr/include/gio-unix-2.0 -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/harfbuzz 
-I/usr/include/x86_64-linux-gnu -I/<>/cadxcore/CADxCore 
-I/<>/cadxcore -I/<>/cadxcore/vtk 
-I/<>/cadxcore/itk -I/<>/cadxcore/wx 
-I/<>/cadxcore/wx/VTK -I/<>/cadxcore/VTKInria3D 
-I/<>/cadxcore/VTKInria3D/wxVTK -I/usr/include/jsoncpp 
-I/<>/../lib/Linux-x86_64/libcurl-7.28.1/include 
-I/usr/lib/x86_64-linux-gnu/wx/include/gtk2-unicode-3.0 -I/usr/include/wx-3.0 
-I/usr/include/vtk-6.3 -I/us
 r/lib/x86_64-linux-gnu/openmpi/include/openmpi 
-I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi/opal/mca/event/libevent2022/libevent
 
-I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi/opal/mca/event/libevent2022/libevent/include
 -I/usr/lib/x86_64

Bug#865552: libbpp-phyl FTBFS with test failures

[Adrian Bunk]

On Sat, Jun 24, 2017 at 10:39:15PM +0200, Andreas Tille wrote:
>...
> Thanks for the explanation.  Do you have a better idea what might lead
> to the test failures of the d/rules file is changing only things that
> are happening after the tests are runned?
> 
> I admit I'm quite clueless and just ignoring test errors on the
> affected architectures would be really the last resort.

Looking closer through the build history, it seems my 2.3.1-1/2.3.1-2
comparison in the bug report was wrong and misleading, sorry for that.

I was looking only at some architectures, looking through all 
architectures the situation based on all 3 2.3.1-* builds is:

2.3.1-* always FTBFS on armel with tests 5,6,11 failing
2.3.1-* always FTBFS on armhf with tests 5,6 and sometimes 11 failing
2.3.1-* always FTBFS on mips with tests 4,5,6 failing
2.3.1-* always FTBFS on mipsel with tests 4,5,6 and sometimes 11 failing
2.3.1-* always FTBFS on mips64el with tests 5,6 and sometimes 11 failing
2.3.1-* sometimes FTBFS on ppc64el with test 6 failing
2.3.1-* sometimes FTBFS on sometimes with test 5,6,11 failing

So the problems sterted with 2.2.0-1 -> 2.3.1-1,
which actually makes sense.

All test failures are timeouts except the test 4 failures on
mips/mipsel, which are "Failed" and likely a separate issue.

> Kind regards
> 
>   Andreas.

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#865552: libbpp-phyl FTBFS with test failures

[Andreas Tille]

Hi Adrian,

On Sat, Jun 24, 2017 at 11:30:05PM +0300, Adrian Bunk wrote:
> > 
> > Hmmm, this would most probably lead to successfully built packages but I
> > would prefer spending some additional thoughts on this.  It would
> > explain the issue why the package has built before but does not any more
> > without any visible change on "weak" architectures.  I could imagine
> > that after stretch release the run on the build servers increased and
> > that possibly parallel builds are happening which lead to performance
> > loss for single packages.
> >...
> 
> No, a buildd never builds more than 1 package at a time.
> 
> Some of the weaker architectures currently have 100 packages
> queued to be built and it can take a few days until a package
> gets built, but during the build the situation stays the same.

Thanks for the explanation.  Do you have a better idea what might lead
to the test failures of the d/rules file is changing only things that
are happening after the tests are runned?

I admit I'm quite clueless and just ignoring test errors on the
affected architectures would be really the last resort.

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#865552: libbpp-phyl FTBFS with test failures

[Adrian Bunk]

On Fri, Jun 23, 2017 at 09:43:11PM +0200, Andreas Tille wrote:
>...
> On Fri, Jun 23, 2017 at 09:02:30PM +0200, Julien Yann Dutheil wrote:
> > This is most strange indeed. The errors are all "time out" errors on unit
> > tests which take the longest time (several min or so). Looks like some
> > issues with the default value for the timeout setting in CTest... I would
> > suggest to simply skip the unit tests by running "cmake
> > -DBUILD_TESTING=FALSE ." .  Does this solve the problem?
> 
> Hmmm, this would most probably lead to successfully built packages but I
> would prefer spending some additional thoughts on this.  It would
> explain the issue why the package has built before but does not any more
> without any visible change on "weak" architectures.  I could imagine
> that after stretch release the run on the build servers increased and
> that possibly parallel builds are happening which lead to performance
> loss for single packages.
>...

No, a buildd never builds more than 1 package at a time.

Some of the weaker architectures currently have 100 packages
queued to be built and it can take a few days until a package
gets built, but during the build the situation stays the same.

> Kind regards
> 
>   Andreas.

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#865790: django-countries FTBFS with Django 1.11

[Adrian Bunk]

Source: django-countries
Version: 3.4.1-2.1
Severity: serious
Tags: buster sid

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

...
   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/1st/django-countries-3.4.1'
set -e; \
for python in python2.7 python3.5; do \
  PYTHONPATH="." DJANGO_SETTINGS_MODULE=django_countries.tests.settings $python 
/usr/bin/django-admin test django_countries.tests;\
done
Traceback (most recent call last):
  File "/usr/bin/django-admin", line 21, in 
management.execute_from_command_line()
  File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", 
line 363, in execute_from_command_line
utility.execute()
  File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", 
line 307, in execute
settings.INSTALLED_APPS
  File "/usr/lib/python2.7/dist-packages/django/conf/__init__.py", line 56, in 
__getattr__
self._setup(name)
  File "/usr/lib/python2.7/dist-packages/django/conf/__init__.py", line 41, in 
_setup
self._wrapped = Settings(settings_module)
  File "/usr/lib/python2.7/dist-packages/django/conf/__init__.py", line 110, in 
__init__
mod = importlib.import_module(self.SETTINGS_MODULE)
  File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module
__import__(name)
  File "/build/1st/django-countries-3.4.1/django_countries/__init__.py", line 
5, in 
from django_countries.conf import settings
  File "/build/1st/django-countries-3.4.1/django_countries/conf.py", line 4, in 

class AppSettings(django.conf.BaseSettings):
AttributeError: 'module' object has no attribute 'BaseSettings'
debian/rules:14: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1

Bug#865789: git FTBFS on armhf/ppc64el: not ok 3 - git svn branch tests

[Adrian Bunk]

Source: git
Version: 1:2.13.1-1
Severity: serious

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

...
expecting success: 
git svn branch a &&
base=$(git rev-parse HEAD:) &&
test $base = $(git rev-parse remotes/origin/a:) &&
git svn branch -m "created branch b blah" b &&
test $base = $(git rev-parse remotes/origin/b:) &&
test_must_fail git branch -m "no branchname" &&
git svn branch -n c &&
test_must_fail git rev-parse remotes/origin/c &&
test_must_fail git svn branch a &&
git svn branch -t tag1 &&
test $base = $(git rev-parse remotes/origin/tags/tag1:) &&
git svn branch --tag tag2 &&
test $base = $(git rev-parse remotes/origin/tags/tag2:) &&
git svn tag tag3 &&
test $base = $(git rev-parse remotes/origin/tags/tag3:) &&
git svn tag -m "created tag4 foo" tag4 &&
test $base = $(git rev-parse remotes/origin/tags/tag4:) &&
test_must_fail git svn tag -m "no tagname" &&
git svn tag -n tag5 &&
test_must_fail git rev-parse remotes/origin/tags/tag5 &&
test_must_fail git svn tag tag1

Copying 
file:///«PKGBUILDDIR»/t/trash%20directory.t9128-git-svn-cmd-branch/svnrepo/trunk
 at r2 to 
file:///«PKGBUILDDIR»/t/trash%20directory.t9128-git-svn-cmd-branch/svnrepo/branches/a...
Found possible branch point: 
file:///«PKGBUILDDIR»/t/trash%20directory.t9128-git-svn-cmd-branch/svnrepo/trunk
 => 
file:///«PKGBUILDDIR»/t/trash%20directory.t9128-git-svn-cmd-branch/svnrepo/branches/a,
 2
Found branch parent: (refs/remotes/origin/a) 
eed7341cd656e2fdb2fb9b36fbe4b039ba13e348
Following parent with do_switch
Successfully followed parent
r3 = 66a689f823e1002a376e324cce35d8c131f72bdc (refs/remotes/origin/a)
Copying 
file:///«PKGBUILDDIR»/t/trash%20directory.t9128-git-svn-cmd-branch/svnrepo/trunk
 at r2 to 
file:///«PKGBUILDDIR»/t/trash%20directory.t9128-git-svn-cmd-branch/svnrepo/branches/b...
Found possible branch point: 
file:///«PKGBUILDDIR»/t/trash%20directory.t9128-git-svn-cmd-branch/svnrepo/trunk
 => 
file:///«PKGBUILDDIR»/t/trash%20directory.t9128-git-svn-cmd-branch/svnrepo/branches/b,
 2
Found branch parent: (refs/remotes/origin/b) 
eed7341cd656e2fdb2fb9b36fbe4b039ba13e348
Following parent with do_switch
Successfully followed parent
r4 = 3f86a479bd31164c206172f5ef7b1fcb7d43e4e1 (refs/remotes/origin/b)
error: git-svn died of signal 11
not ok 3 - git svn branch tests
#   
#   git svn branch a &&
#   base=$(git rev-parse HEAD:) &&
#   test $base = $(git rev-parse remotes/origin/a:) &&
#   git svn branch -m "created branch b blah" b &&
#   test $base = $(git rev-parse remotes/origin/b:) &&
#   test_must_fail git branch -m "no branchname" &&
#   git svn branch -n c &&
#   test_must_fail git rev-parse remotes/origin/c &&
#   test_must_fail git svn branch a &&
#   git svn branch -t tag1 &&
#   test $base = $(git rev-parse remotes/origin/tags/tag1:) &&
#   git svn branch --tag tag2 &&
#   test $base = $(git rev-parse remotes/origin/tags/tag2:) &&
#   git svn tag tag3 &&
#   test $base = $(git rev-parse remotes/origin/tags/tag3:) &&
#   git svn tag -m "created tag4 foo" tag4 &&
#   test $base = $(git rev-parse remotes/origin/tags/tag4:) &&
#   test_must_fail git svn tag -m "no tagname" &&
#   git svn tag -n tag5 &&
#   test_must_fail git rev-parse remotes/origin/tags/tag5 &&
#   test_must_fail git svn tag tag1
#   
...

Bug#865786: prometheus FTBFS on 32bit: FAIL: TestSampleDelivery

[Adrian Bunk]

Source: prometheus
Version: 1.6.2+ds-2
Severity: serious

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

...
=== RUN   TestSampleDelivery
--- FAIL: TestSampleDelivery (0.56s)
panic: runtime error: invalid memory address or nil pointer dereference 
[recovered]
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x8049a8c]

goroutine 33 [running]:
testing.tRunner.func1(0x18766680)
/usr/lib/go-1.8/src/testing/testing.go:622 +0x226
panic(0x82bb580, 0x8448800)
/usr/lib/go-1.8/src/runtime/panic.go:489 +0x22a
sync/atomic.AddUint64(0x187b0074, 0x1, 0x0, 0x8093740, 0x809b1b7)
/usr/lib/go-1.8/src/sync/atomic/asm_386.s:112 +0xc
github.com/prometheus/prometheus/storage/remote.(*ewmaRate).incr(0x187b0074, 
0x1, 0x0)

/<>/prometheus-1.6.2+ds/build/src/github.com/prometheus/prometheus/storage/remote/ewma.go:65
 +0x33
github.com/prometheus/prometheus/storage/remote.(*shards).enqueue(0x1876c0c0, 
0x1beac080, 0x0)

/<>/prometheus-1.6.2+ds/build/src/github.com/prometheus/prometheus/storage/remote/queue_manager.go:427
 +0x3c
github.com/prometheus/prometheus/storage/remote.(*QueueManager).Append(0x187b,
 0x187efea0, 0x64, 0x2a05f200)

/<>/prometheus-1.6.2+ds/build/src/github.com/prometheus/prometheus/storage/remote/queue_manager.go:239
 +0x191
github.com/prometheus/prometheus/storage/remote.TestSampleDelivery(0x18766680)

/<>/prometheus-1.6.2+ds/build/src/github.com/prometheus/prometheus/storage/remote/queue_manager_test.go:106
 +0x448
testing.tRunner(0x18766680, 0x830d894)
/usr/lib/go-1.8/src/testing/testing.go:657 +0x7e
created by testing.(*T).Run
/usr/lib/go-1.8/src/testing/testing.go:697 +0x242
exit status 2
FAILgithub.com/prometheus/prometheus/storage/remote 0.604s
...

Bug#865785: t50 FTBFS on i386: randomizer.c:99:7: error: expected string literal before ':' token

[Adrian Bunk]

Source: t50
Version: 5.6.13-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=t50&arch=i386&ver=5.6.13-1&stamp=1498263356&raw=0

...
Making all in src
make[2]: Entering directory '/<>/src'
gcc -DHAVE_CONFIG_H -I. -I../src/include   -Wdate-time -D_FORTIFY_SOURCE=2  -g 
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -std=gnu11  -DNDEBUG -c -o main.o main.c
gcc -DHAVE_CONFIG_H -I. -I../src/include   -Wdate-time -D_FORTIFY_SOURCE=2  -g 
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -std=gnu11  -DNDEBUG -c -o config.o config.c
gcc -DHAVE_CONFIG_H -I. -I../src/include   -Wdate-time -D_FORTIFY_SOURCE=2  -g 
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -std=gnu11  -DNDEBUG -c -o randomizer.o randomizer.c
gcc -DHAVE_CONFIG_H -I. -I../src/include   -Wdate-time -D_FORTIFY_SOURCE=2  -g 
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -std=gnu11  -DNDEBUG -c -o usage.o usage.c
gcc -DHAVE_CONFIG_H -I. -I../src/include   -Wdate-time -D_FORTIFY_SOURCE=2  -g 
-O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -std=gnu11  -DNDEBUG -c -o modules.o modules.c
randomizer.c: In function 'SRANDOM':
randomizer.c:99:7: error: expected string literal before ':' token
   : : "cc"
   ^
Makefile:527: recipe for target 'randomizer.o' failed
make[2]: *** [randomizer.o] Error 1

Bug#854210: libnet-xmpp-perl: sendxmpp can't send message to hangouts (work fine for 1.02-5)

[Eriberto Mota]

2017-06-24 15:23 GMT-03:00 gregor herrmann :
>> The both options work fine. Thanks a lot for your help.
>
> Thanks for testing!
>
> Now I'm a bit confused: Which "both" of the 3 options mentioned above
> work?
> [ ] call sendxmpp with --tls-ca-path="/etc/ssl/certs"
> [ ] change line 223 in /usr/share/perl5/XML/Stream.pm
> [ ] change line 287 in /usr/bin/sendxmpp
>
>> Please, when uploading, fix Stretch too!
>
> First we need to decide where we want the fix ...


Wow, sorry...

Worked fine:

[ x ] call sendxmpp with --tls-ca-path="/etc/ssl/certs"
[ x ] change line 223 in /usr/share/perl5/XML/Stream.pm

I didn't test the following option in my last email. I did it now and works too.

[ x ] change line 287 in /usr/bin/sendxmpp

However, for me in Stretch the right line is 290. See below:

   290 'tls-ca-path' => ($tls_ca_path or '/etc/ssl/certs'),

Thanks!

Cheers,

Eriberto

Bug#838320: installation-reports: debian stretch (testing) installer freezes on the laptop with Intel Celeron N2840 CPU

[Cyril Brulebois]

Control: tag -1 moreinfo - d-i
Control: severity -1 normal

Geert Stappers  (2016-09-19):
> Control: -1 moreinfo
> Stop
> 
> On Mon, Sep 19, 2016 at 11:03:26PM +0300, Oksana Andrusiv wrote:
> > 
> > The installation of the base system hangs.
> > The very last message in log console is "installed discover".
> > The issue was reproduced in 100% of attempts with and without network 
> > mirror.
> > 
> > The debian 8 is currently in use on the same laptop thus I suppose it is a 
> > new
> > problem.
> 
> Good that the new problem is being reported.
> 
> Please boot with 'priority=low' to get more messages
> and report back..
> 
> See https://www.debian.org/releases/stretch/arm64/ch05s03.html.en for 
> additional
> information.

Hi Oksana,

It's been a few months already and we didn't hear back from you. We
can't do anything if we don't get any feedback…


KiBi.


signature.asc
Description: Digital signature

Processed: Re: Bug#838320: installation-reports: debian stretch (testing) installer freezes on the laptop with Intel Celeron N2840 CPU

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo - d-i
Bug #838320 [installation-reports] installation-reports: debian stretch 
(testing) installer freezes on the laptop with Intel Celeron N2840 CPU
Added tag(s) moreinfo.
Bug #838320 [installation-reports] installation-reports: debian stretch 
(testing) installer freezes on the laptop with Intel Celeron N2840 CPU
Removed tag(s) d-i.
> severity -1 normal
Bug #838320 [installation-reports] installation-reports: debian stretch 
(testing) installer freezes on the laptop with Intel Celeron N2840 CPU
Severity set to 'normal' from 'critical'

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

Bug#865783: dicomscope FTBFS with libdcmtk-dev 3.6.1~20170228-2

[Adrian Bunk]

Source: dicomscope
Version: 3.6.0-15
Severity: serious
Tags: buster sid

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

...
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found JNI: /usr/lib/jvm/default-java/jre/lib/amd64/libjawt.so  
-- Trying to find DCMTK expecting DCMTKConfig.cmake
-- Trying to find DCMTK expecting DCMTKConfig.cmake - ok
-- Found Java: /usr/lib/jvm/default-java/bin/java (found version "1.8.0.131") 
CMake Error: The following variables are used in this project, but they are set 
to NOTFOUND.
Please set them or make sure they are set and tested correctly in the CMake 
files:
DCMTK_dcmjpeg_INCLUDE_DIR
   used as include directory in directory /<>/interface/libsrc
   used as include directory in directory /<>/interface/libsrc
   used as include directory in directory /<>/interface/libsrc
   used as include directory in directory /<>/interface/libsrc
   used as include directory in directory /<>/interface/libsrc
   used as include directory in directory /<>/interface/libsrc
   used as include directory in directory /<>/interface/libsrc
DCMTK_dcmpstat_INCLUDE_DIR
   used as include directory in directory /<>/interface/libsrc
   used as include directory in directory /<>/interface/libsrc
   used as include directory in directory /<>/interface/libsrc
   used as include directory in directory /<>/interface/libsrc
   used as include directory in directory /<>/interface/libsrc
   used as include directory in directory /<>/interface/libsrc
   used as include directory in directory /<>/interface/libsrc
DCMTK_dcmsr_INCLUDE_DIR
   used as include directory in directory /<>/interface/libsrc
   used as include directory in directory /<>/interface/libsrc
   used as include directory in directory /<>/interface/libsrc
   used as include directory in directory /<>/interface/libsrc
   used as include directory in directory /<>/interface/libsrc
   used as include directory in directory /<>/interface/libsrc
   used as include directory in directory /<>/interface/libsrc

-- Configuring incomplete, errors occurred!
...

Bug#865781: orthanc-wsi FTBFS with libdcmtk-dev 3.6.1~20170228-2

[Adrian Bunk]

Source: orthanc-wsi
Version: 0.4+dfsg-1
Severity: serious

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

...
-- Found PythonInterp: /usr/bin/python (found version "2.7.13") 
-- Could NOT find PkgConfig (missing:  PKG_CONFIG_EXECUTABLE) 
-- Looking for include file uuid/uuid.h
-- Looking for include file uuid/uuid.h - found
-- Trying to find DCMTK expecting DCMTKConfig.cmake
-- Trying to find DCMTK expecting DCMTKConfig.cmake - ok
CMake Error at 
/<>/orthanc-wsi-0.4+dfsg/Resources/Orthanc/Resources/CMake/DcmtkConfiguration.cmake:274
 (message):
  Please install libdcmtk*-dev
Call Stack (most recent call first):
  CMakeLists.txt:67 (include)


-- Configuring incomplete, errors occurred!
...

Bug#865780: gnuastro FTBFS on 32bit: test failures

[Adrian Bunk]

Source: gnuastro
Version: 0.3.7-1
Severity: serious

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

mkcatalog/simple.sh is failing on all 32bit architectures,
on some 32bit architectures (including i386) more tests
are failing.

Bug#865776: hardinfo FTBFS on ppc64el: Unsupported architecture: ppc64le

[Adrian Bunk]

Source: hardinfo
Version: 0.5.1+git20170620-1
Severity: serious


https://buildd.debian.org/status/fetch.php?pkg=hardinfo&arch=ppc64el&ver=0.5.1%2Bgit20170620-1&stamp=1498211950&raw=0

...
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
CMake Error at CMakeLists.txt:47 (message):
  Unsupported architecture: ppc64le


-- Configuring incomplete, errors occurred!
...

Bug#854210: libnet-xmpp-perl: sendxmpp can't send message to hangouts (work fine for 1.02-5)

[gregor herrmann]

On Sat, 24 Jun 2017 15:13:49 -0300, Eriberto Mota wrote:

> > Looks like the path to the SSL cert(s) is empty.
> > I gues either sendxmpp should set it, or XML::Stream should use a
> > sane default.
> >
> > For the latter see /usr/share/perl5/XML/Stream.pm:
> > 223$self->{SIDS}->{default}->{ssl_ca_path} = '';
> >
> > Changing this value to '/etc/ssl/certs' might help.
> >
> >
> > Ah, sendxmpp has an option tls-ca-path which is set to an empty
> > string if not passed on the command line. [0] In that case probably the
> > empty string somehow propagates down ...
> >
> >
> > Could one of the sendxmpp please try to call it with something like
> > --tls-ca-path="/etc/ssl/certs"
> > and see if this helps?
> > And/or change the above mentioned line in
> > /usr/share/perl5/XML/Stream.pm?
> > And/or change the line in sendxmpp mentioned in [0]?
> >
> >
> > [0]
> > 287'tls-ca-path' => ($tls_ca_path or ''),
> 
> 
> 
> The both options work fine. Thanks a lot for your help.

Thanks for testing!

Now I'm a bit confused: Which "both" of the 3 options mentioned above
work?
[ ] call sendxmpp with --tls-ca-path="/etc/ssl/certs"
[ ] change line 223 in /usr/share/perl5/XML/Stream.pm
[ ] change line 287 in /usr/bin/sendxmpp
 
> Please, when uploading, fix Stretch too!

First we need to decide where we want the fix ...
 

Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Eric Clapton: Wonderful Tonight


signature.asc
Description: Digital Signature

Processed: your mail

[Debian Bug Tracking System]

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

> affects 854210 sendxmpp ejabberd
Bug #854210 [libnet-xmpp-perl] libnet-xmpp-perl: sendxmpp can't send message to 
hangouts (work fine for 1.02-5)
Added indication that 854210 affects sendxmpp and ejabberd
> tags 854210 stretch buster sid
Bug #854210 [libnet-xmpp-perl] libnet-xmpp-perl: sendxmpp can't send message to 
hangouts (work fine for 1.02-5)
Added tag(s) stretch, sid, and buster.
>
End of message, stopping processing here.

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

Bug#854210: libnet-xmpp-perl: sendxmpp can't send message to hangouts (work fine for 1.02-5)

[Eriberto Mota]

2017-06-23 21:14 GMT-03:00 gregor herrmann :
> On Sun, 05 Feb 2017 10:24:24 +0800, Tommy Wu wrote:
>
>> After upgrade to 1.05-1, sendxmpp program can't send message to googole 
>> hangouts.
>>
>> XML::Stream: SetCallBacks: tag(node) func(CODE(0x5567d6c2aa20))
>> XMPP::Conn: xmppCallbackInit: start
>> XMPP::Conn: SetCallBacks: tag(message) func(CODE(0x5567d6c2aaf8))
>> XMPP::Conn: SetCallBacks: tag(presence) func(CODE(0x5567d6b19538))
>> XMPP::Conn: SetCallBacks: tag(iq) func(CODE(0x5567d5bc4b68))
>> XMPP::Conn: SetPresenceCallBacks: type(subscribe) func(CODE(0x5567d6c2a798))
>> XMPP::Conn: SetPresenceCallBacks: type(unsubscribe) 
>> func(CODE(0x5567d6c2a720))
>> XMPP::Conn: SetPresenceCallBacks: type(unsubscribed) 
>> func(CODE(0x5567d6c2b068))
>> XMPP::Conn: SetPresenceCallBacks: type(subscribed) func(CODE(0x5567d6c2b1d0))
>> XMPP::Conn: SetDirectXPathCallBacks: 
>> xpath(/[@xmlns="urn:ietf:params:xml:ns:xmpp-tls"]) func(CODE(0x5567d6bd6a48))
>> XMPP::Conn: SetDirectXPathCallBacks: 
>> xpath(/[@xmlns="urn:ietf:params:xml:ns:xmpp-sasl"]) 
>> func(CODE(0x5567d6c2aea0))
>> XMPP::Conn: xmppCallbackInit: stop
>> sendxmpp: ssl_verify: 1
>> sendxmpp: tls_ca_path:
>
> ^^
>
>> XMPP::Conn: Connect: host(talk.google.com:5222) namespace(jabber:client)
>> XMPP::Conn: Connect: timeout(10)
>> XML::Stream: Connect: srv requested
>> XML::Stream: Connect: srv query failed
>> XML::Stream: Connect: type(tcpip)
>> Invalid or unreadable path specified for ssl_ca_path. at 
>> /usr/share/perl5/XML/Stream.pm line 641.
>
> ^^
>
> Looks like the path to the SSL cert(s) is empty.
> I gues either sendxmpp should set it, or XML::Stream should use a
> sane default.
>
> For the latter see /usr/share/perl5/XML/Stream.pm:
> 223$self->{SIDS}->{default}->{ssl_ca_path} = '';
>
> Changing this value to '/etc/ssl/certs' might help.
>
>
> I doubt that libnet-xmpp-perl is the problem here; the change between
> 1.02 and 1.05 is that it passes a defined ssl_ca_path on to
> XML::Stream.
>
>
> Ah, sendxmpp has an option tls-ca-path which is set to an empty
> string if not passed on the command line. [0] In that case probably the
> empty string somehow propagates down ...
>
>
> Could one of the sendxmpp please try to call it with something like
> --tls-ca-path="/etc/ssl/certs"
> and see if this helps?
> And/or change the above mentioned line in
> /usr/share/perl5/XML/Stream.pm?
> And/or change the line in sendxmpp mentioned in [0]?
>
>
> If this is successful we still have to think where we should make
> changes.
>
>
> Cheers,
> gregor
>
>
> [0]
> 287'tls-ca-path' => ($tls_ca_path or ''),



Hi gregor,

The both options work fine. Thanks a lot for your help.

Please, when uploading, fix Stretch too!

Have a nice weekend.

Cheers,

Eriberto

Bug#865772: webkit2gtk: Select element regression introduced in 2.16.4

[Jeremy Bicha]

Source: webkit2gtk
Version: 2.16.4-1
Severity: serious

The webkit2gtk developers recommend not updating to 2.16.4 because of
a regression and wait for the next version (2.16.5?). Therefore, I'm
filing this bug to stop automatic migration to testing.

https://mail.gnome.org/archives/distributor-list/2017-June/msg1.html

Thanks,
Jeremy Bicha

Processed: notfound 865684 in josm-plugins/0.0.svn33112+ds-1

[Debian Bug Tracking System]

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

> notfound 865684 josm-plugins/0.0.svn33112+ds-1
Bug #865684 {Done: Debian FTP Masters } 
[src:josm-plugins] josm-plugins: Obsolete, causes issues with user installed 
plugins
No longer marked as found in versions josm-plugins/0.0.svn33112+ds-1.
> thanks
Stopping processing here.

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

Bug#864276: [request-tracker-maintainers] Bug#864276: Bug#864276: rt4-extension-sla: not installable in sid

[Dominic Hargreaves]

On Tue, Jun 06, 2017 at 02:58:36PM +0100, Dominic Hargreaves wrote:
> On Tue, Jun 06, 2017 at 08:41:39AM +0200, Ralf Treinen wrote:
> > Package: rt4-extension-sla
> > Version: 1.04-2
> > Severity: serious
> > User: trei...@debian.org
> > Usertags: edos-uninstallable
> > 
> > Hi,
> > 
> > rt4-extension-sla is not installable in sid on any architecture. This is
> > the case since at least 2017-01-21. The reason is that it depends on
> > request-tracker4 (< 4.4.0), however the version of that package in sid
> > is 4.4.1-3.
> 
> Thanks. As per #851986 this was left in to aid backporting(?) but the
> reasoning in that bug is not too clear. Joost, any objections to just
> removing this?

I've now filed an RM bug (#865767) for this.

Dominic.

Bug#865090: marked as done (libbsd FTBFS on arm*: FAIL: progname)

[Debian Bug Tracking System]

Your message dated Sat, 24 Jun 2017 15:37:40 +
with message-id 
and subject line Bug#865090: fixed in libbsd 0.8.5-1
has caused the Debian Bug report #865090,
regarding libbsd FTBFS on arm*: FAIL: progname
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.)


-- 
865090: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865090
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libbsd
Version: 0.8.4-1
Severity: serious

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

...
PASS: nlist
PASS: proctitle-init
../build-aux/test-driver: line 107: 16338 Aborted "$@" > 
$log_file 2>&1
FAIL: progname
PASS: setmode
PASS: strl
PASS: strmode
PASS: strnstr
PASS: proctitle
===
   libbsd 0.8.4: test/test-suite.log
===

# TOTAL: 20
# PASS:  19
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: progname
==

lt-progname: progname.c:34: main: Assertion `strcmp(getprogname(), "progname") 
== 0' failed.
FAIL progname (exit status: 134)


Testsuite summary for libbsd 0.8.4

# TOTAL: 20
# PASS:  19
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See test/test-suite.log
Please report to lib...@lists.freedesktop.org

Makefile:924: recipe for target 'test-suite.log' failed
make[4]: *** [test-suite.log] Error 1
make[4]: Leaving directory '/<>/test'
Makefile:1030: recipe for target 'check-TESTS' failed
make[3]: *** [check-TESTS] Error 2
make[3]: Leaving directory '/<>/test'
Makefile:1243: recipe for target 'check-am' failed
make[2]: *** [check-am] Error 2
make[2]: Leaving directory '/<>/test'
Makefile:409: recipe for target 'check-recursive' failed
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory '/<>'
debian/rules:48: recipe for target 'check-arch' failed
make: *** [check-arch] Error 2
--- End Message ---
--- Begin Message ---
Source: libbsd
Source-Version: 0.8.5-1

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

Debian distribution maintenance software
pp.
Guillem Jover  (supplier of updated libbsd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 24 Jun 2017 17:01:03 +0200
Source: libbsd
Binary: libbsd-dev libbsd0 libbsd0-udeb
Architecture: source
Version: 0.8.5-1
Distribution: unstable
Urgency: medium
Maintainer: Guillem Jover 
Changed-By: Guillem Jover 
Description:
 libbsd-dev - utility functions from BSD systems - development files
 libbsd0- utility functions from BSD systems - shared library
 libbsd0-udeb - utility functions from BSD systems - shared library (udeb)
Closes: 865090 865091
Changes:
 libbsd (0.8.5-1) unstable; urgency=medium
 .
   * New upstream release.
 - Handle libtool executable names in getprogname() unit test.
   Closes: #865090
 - Fix ELF definitions for PowerPC and MIPS in local-elf.h.
   Thanks to James Cowgill . Closes: #865091
 - Ship and install libbsd(7).
Checksums-Sha1:
 cc30681083038aa639c1382164c17593cb953550 2218 libbsd_0.8.5-1.dsc
 8ca40694bddf17a81cc6b0d49725311ab766d709 370680 libbsd_0.8.5.orig.tar.xz
 b1ed15f48e79a25412011df8c4347708520c98ab 833 libbsd_0.8.5.orig.tar.xz.asc
 40a4ed5faff0ce36c5eaef43fb695089ed25e7c0 15536 libbsd_0.8.5-1.debian.tar.xz
 281320854ab9f8c0fae15f394004e700337f45be 6112 libbsd_0.8.5-1_amd64.buildinfo
Checksums-Sha256:
 64f6ecaa50af866829c8f0b0663c3a1cbb77162c5b92a75bb24a265e4477b6ae 2218 
libbsd_0.8.5-1.dsc
 7647d024f41389305272c263da933a6f2a978213c1801592f47e68d83ac05b28 370680 
libbsd_0.8.5.orig.tar.xz
 53a316531f50ad43551aac1b744c86422d7b890deed3169411947c0656f6bd6a 833 
libbsd_0.8.5.orig.tar.xz.asc
 680f1826a38d7d48284196a0db6d1d601639bd6af17a26850bab2bba4c4de646 1553

Bug#865091: marked as done (libbsd FTBFS on mips64el/ppc64el: FAIL: nlist)

[Debian Bug Tracking System]

Your message dated Sat, 24 Jun 2017 15:37:40 +
with message-id 
and subject line Bug#865091: fixed in libbsd 0.8.5-1
has caused the Debian Bug report #865091,
regarding libbsd FTBFS on mips64el/ppc64el: FAIL: nlist
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.)


-- 
865091: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865091
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libbsd
Version: 0.8.4-1
Severity: serious

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

...
PASS: fpurge
PASS: md5
../build-aux/test-driver: line 107: 14657 Aborted "$@" > 
$log_file 2>&1
FAIL: nlist
PASS: proctitle-init
PASS: progname
PASS: setmode
PASS: strl
PASS: strmode
PASS: strnstr
PASS: proctitle
===
   libbsd 0.8.4: test/test-suite.log
===

# TOTAL: 20
# PASS:  19
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: nlist
===

nlist: nlist.c:70: main: Assertion `rc == 0' failed.
FAIL nlist (exit status: 134)


Testsuite summary for libbsd 0.8.4

# TOTAL: 20
# PASS:  19
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See test/test-suite.log
Please report to lib...@lists.freedesktop.org

Makefile:924: recipe for target 'test-suite.log' failed
make[4]: *** [test-suite.log] Error 1
make[4]: Leaving directory '/<>/test'
Makefile:1030: recipe for target 'check-TESTS' failed
make[3]: *** [check-TESTS] Error 2
make[3]: Leaving directory '/<>/test'
Makefile:1243: recipe for target 'check-am' failed
make[2]: *** [check-am] Error 2
make[2]: Leaving directory '/<>/test'
Makefile:409: recipe for target 'check-recursive' failed
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory '/<>'
debian/rules:48: recipe for target 'check-arch' failed
make: *** [check-arch] Error 2
--- End Message ---
--- Begin Message ---
Source: libbsd
Source-Version: 0.8.5-1

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

Debian distribution maintenance software
pp.
Guillem Jover  (supplier of updated libbsd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 24 Jun 2017 17:01:03 +0200
Source: libbsd
Binary: libbsd-dev libbsd0 libbsd0-udeb
Architecture: source
Version: 0.8.5-1
Distribution: unstable
Urgency: medium
Maintainer: Guillem Jover 
Changed-By: Guillem Jover 
Description:
 libbsd-dev - utility functions from BSD systems - development files
 libbsd0- utility functions from BSD systems - shared library
 libbsd0-udeb - utility functions from BSD systems - shared library (udeb)
Closes: 865090 865091
Changes:
 libbsd (0.8.5-1) unstable; urgency=medium
 .
   * New upstream release.
 - Handle libtool executable names in getprogname() unit test.
   Closes: #865090
 - Fix ELF definitions for PowerPC and MIPS in local-elf.h.
   Thanks to James Cowgill . Closes: #865091
 - Ship and install libbsd(7).
Checksums-Sha1:
 cc30681083038aa639c1382164c17593cb953550 2218 libbsd_0.8.5-1.dsc
 8ca40694bddf17a81cc6b0d49725311ab766d709 370680 libbsd_0.8.5.orig.tar.xz
 b1ed15f48e79a25412011df8c4347708520c98ab 833 libbsd_0.8.5.orig.tar.xz.asc
 40a4ed5faff0ce36c5eaef43fb695089ed25e7c0 15536 libbsd_0.8.5-1.debian.tar.xz
 281320854ab9f8c0fae15f394004e700337f45be 6112 libbsd_0.8.5-1_amd64.buildinfo
Checksums-Sha256:
 64f6ecaa50af866829c8f0b0663c3a1cbb77162c5b92a75bb24a265e4477b6ae 2218 
libbsd_0.8.5-1.dsc
 7647d024f41389305272c263da933a6f2a978213c1801592f47e68d83ac05b28 370680 
libbsd_0.8.5.orig.tar.xz
 53a316531f50ad43551aac1b744c86422d7b890deed3169411947c0656f6bd6a 833 
libbsd_0.8.5.orig.tar.xz.asc
 680f1826a38d7d48284196a0db6d1d601639bd6af17a26850bab2bba4c4de646 15536 
libbsd_0.8.5-1.

Processed: Re: Bug#836770: efi-readvar: Claims 'No efivarfs filesystem is mounted', no idea why

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #836770 [efitools] efi-readvar: Claims 'No efivarfs filesystem is mounted', 
no idea why
Severity set to 'important' from 'grave'

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

Bug#836770: efi-readvar: Claims 'No efivarfs filesystem is mounted', no idea why

[Julian Andres Klode]

Control: severity -1 important

On Mon, Sep 05, 2016 at 05:06:21PM +0200, Julian Andres Klode wrote:
> Package: efitools
> Version: 1.4.2-2
> Severity: grave
> File: /usr/bin/efi-readvar
> 
> The efivarfs part of the package is unusable:
> 
> root@jak-x230:~# mount | grep efi
> efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,relatime)
> systemd-1 on /boot/efi type autofs 
> (rw,relatime,fd=32,pgrp=1,timeout=10,minproto=5,maxproto=5,direct,pipe_ino=11388)
> root@jak-x230:~# ls /sys/firmware/efi/efivars | grep PK
> PK-8be4df61-93ca-11d2-aa0d-00e098032b8c
> root@jak-x230:~# efi-readvar -v PK
> No efivarfs filesystem is mounted
> 

The rest of the package works OK (especially the EFI binaries), so
it seems wrong for this bug to be RC.

-- 
Debian Developer - deb.li/jak | jak-linux.org - free software dev
  |  Ubuntu Core Developer |
When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to ('inline').  Thank you.

Bug#830897: marked as done (Please drop dependency on sysvinit)

[Debian Bug Tracking System]

Your message dated Sat, 24 Jun 2017 15:14:16 +
with message-id 
and subject line Bug#865752: Removed package(s) from unstable
has caused the Debian Bug report #830897,
regarding Please drop dependency on sysvinit
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.)


-- 
830897: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830897
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: init-select
Version: 1.20140921
Severity: important

Hi,

the init-select package has a dependency on "sysvinit".
In Jesse, the "sysvinit" package has been turned into a transitional
package to pull in the new "init" meta-package.
Now that Jessie has been released, the sysvinit package has served its
purpose and we want to remove it.
I would therefor ask you to remove the dependency on sysvinit.

If you are looking for the package shipping the actual /sbin/init
binary, you need "sysvinit-core" instead.

Regards,
Michael

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

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

Versions of packages init-select depends on:
ii  debconf [debconf-2.0]  1.5.59

Versions of packages init-select recommends:
ii  grub-pc  2.02~beta2-36

Versions of packages init-select suggests:
ii  systemd  230-7
--- End Message ---
--- Begin Message ---
Version: 1.20140921+rm

Dear submitter,

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

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

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

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

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

Bug#858528: marked as done (grub-coreboot: fails to upgrade from jessie to stretch if init-select was installed)

[Debian Bug Tracking System]

Your message dated Sat, 24 Jun 2017 15:14:16 +
with message-id 
and subject line Bug#865752: Removed package(s) from unstable
has caused the Debian Bug report #858528,
regarding grub-coreboot: fails to upgrade from jessie to stretch if init-select 
was installed
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.)


-- 
858528: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858528
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: grub-coreboot
Version: 2.02~beta3-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + init-select

Hi,

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

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

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

  Setting up grub-coreboot (2.02~beta3-5) ...
  Installing new version of config file /etc/kernel/postinst.d/zz-update-grub 
...
  Installing new version of config file /etc/kernel/postrm.d/zz-update-grub ...
  /var/lib/dpkg/info/grub-coreboot.config: 1: 
/etc/default/grub.d/init-select.cfg: /usr/lib/init-select/get-init: not found
  dpkg: error processing package grub-coreboot (--configure):
   subprocess installed post-installation script returned error exit status 127

This was observed in the following configuration:

* --arch i386
* --install-recommends
* package to be tested: init-select/jessie
* distupgrade from jessie to stretch (stretch does not have init-select,
  init-select was removed before grub-coreboot was configured)


cheers,

Andreas


init-select_None.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 1.20140921+rm

Dear submitter,

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

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

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

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

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

Bug#865711: haskell-yaml: FTBFS everywhere (except all)

[Clint Adams]

On Sat, Jun 24, 2017 at 03:34:35AM +0100, James Clarke wrote:
> Hi,
> haskell-yaml FTBFS on every architecture (except all) due to testsuite
> failures:
> 
> > Failures:
> >
> >   test/Data/YamlSpec.hs:440:
> >   1) Data.Yaml.Data.Yaml encode invalid numbers
> >expected: ".\n"
> > but got: ".\n...\n"
> >
> >   test/Data/YamlSpec.hs:458:
> >   2) Data.Yaml.numbers integers have no decimals
> >expected: "1\n"
> > but got: "1\n...\n"
> >
> > Randomized with seed 1628861893

I don't know what we should do here.  The behavior of the embedded
libyaml differs from our libyaml and I'm not sure why, but it appears
to be on purpose.

Bug#865684: marked as done (josm-plugins: Obsolete, causes issues with user installed plugins)

[Debian Bug Tracking System]

Your message dated Sat, 24 Jun 2017 15:05:03 +
with message-id 
and subject line Bug#864976: Removed package(s) from unstable
has caused the Debian Bug report #865684,
regarding josm-plugins: Obsolete, causes issues with user installed plugins
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.)


-- 
865684: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865684
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: josm-plugins
Version: 0.0.svn33112+ds-1
Severity: serious
Tags: upstream
Justification: makes the package unsuitable for release

josm-plugins will be removed from Debian because it doesn't play well
with user installed plugins. See:

 https://josm.openstreetmap.de/ticket/7483

RM bugs have been filed to remove the package from unstable &
experimental:

 https://bugs.debian.org/864976 (unstable)
 https://bugs.debian.org/864975 (experimental)

This RC bugs serves to get josm-plugins removed from testing to allow
josm (>= 0.0.svn12275+dfsg-1) to migrate to testing.
--- End Message ---
--- Begin Message ---
Version: 0.0.svn33112+ds-1+rm

Dear submitter,

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

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

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

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

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

Bug#865581: czmq frequently FTBFS: czmq_selftest killed with signal TERM after 150 minutes of inactivity

[Luca Boccassi]

On Fri, 2017-06-23 at 00:04 +0300, Adrian Bunk wrote:
> Source: czmq
> Version: 4.0.2-8
> Severity: serious
> 
> 4.0.2-8 FTBFS twice on ppc64el, and there is also an older
> similar FTBFS on ppc64el:
> https://buildd.debian.org/status/logs.php?pkg=czmq&arch=ppc64el
> 
> The same FTBFS has in the past also been seen on mips and i386:
> https://buildd.debian.org/status/fetch.php?pkg=czmq&arch=mips&ver=4.0
> .2-4&stamp=1485124953&raw=0
> https://buildd.debian.org/status/fetch.php?pkg=czmq&arch=i386&ver=3.0
> .2-6&stamp=1461609319&raw=0
> 
> 
> ...
> make  check-TESTS check-local
> make[4]: Entering directory '/<>'
> make[5]: Entering directory '/<>'
> =
> ===
> Testsuite summary for czmq 4.0.2
> =
> ===
> # TOTAL: 0
> # PASS:  0
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  0
> # XPASS: 0
> # ERROR: 0
> =
> ===
> make[5]: Leaving directory '/<>'
> /bin/bash ./libtool --mode=execute ./src/czmq_selftest
> E: Build killed with signal TERM after 150 minutes of inactivity

Hi, thanks for the report.

We've noticed there's one of the unit tests that very occasionally
hangs in some environment, especially when overbooked or with slower
architectures.

Unfortunately I haven't been able to reproduce it locally yet, will
keep investigating.

Kind regards,
Luca Boccassi

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

Bug#864921: marked as done (spip: CVE-2017-9736: remote code execution)

[Debian Bug Tracking System]

Your message dated Sat, 24 Jun 2017 14:51:39 +
with message-id 
and subject line Bug#864921: fixed in spip 3.1.4-3~deb9u1
has caused the Debian Bug report #864921,
regarding spip: CVE-2017-9736: remote code execution
to be marked as done.

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

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


-- 
864921: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864921
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: spip
Version: 3.1.4-2
Severity: grave
Tags: security upstream
Justification: user security hole
Control: fixed -1 3.1.4-2

As per

https://contrib.spip.net/CRITICAL-security-update-SPIP-3-1-6-and-SPIP-3-2-Beta?var_zapl=non
> A CRITICAL flaw was discovered recently in SPIP, allowing the
> execution of arbitrary code.
>
> It affects SPIP 3.1.x and 3.2 versions (alpha & beta), and impacts all
> websites using these versions.
> SPIP 3.0.x and earlier versions are not affected by this issue.
>
> It is imperative to update your SPIP website as soon as possible.
>
> In the meantime, the security screen version 1.3.2 will block possible
> exploitations of the vulnerability. Updating the security screen
> remains a transitional measure that should not prevent you from
> updating SPIP as soon as possible.
>
> The team thanks Emeric Boit and ANSSI for identifying and reporting
> the issue.

and since there is no CVE to track the issue, filling the bug in the
BTS even though already fixed in unstable.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: spip
Source-Version: 3.1.4-3~deb9u1

We believe that the bug you reported is fixed in the latest version of
spip, 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.
David Prévot  (supplier of updated spip package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 19 Jun 2017 09:36:46 -1000
Source: spip
Binary: spip
Architecture: source
Version: 3.1.4-3~deb9u1
Distribution: stretch-security
Urgency: high
Maintainer: SPIP packaging team 
Changed-By: David Prévot 
Description:
 spip   - website engine for publishing
Closes: 864921
Changes:
 spip (3.1.4-3~deb9u1) stretch-security; urgency=high
 .
   * Upload previous fixes to Stretch
   * Update previous changelog entry with CVE and bug report
 .
 spip (3.1.4-3) unstable; urgency=high
 .
   * Track Stretch
   * Backport security fix from 3.1.6
 - Execution of arbitrary code [CVE-2017-9736] (Closes: #864921)
   * Update security screen to 1.3.2
Checksums-Sha1:
 7ebd6794431e14d5c53b98849c7f76f16aad130c 1604 spip_3.1.4-3~deb9u1.dsc
 5c11a4ba509364298fda7e5e6838c7caead8d091 5848656 spip_3.1.4.orig.tar.xz
 ddf928c5a754559697b78fd2bbe4d17d83c509d9 81588 
spip_3.1.4-3~deb9u1.debian.tar.xz
Checksums-Sha256:
 f183335113efe985153400406b73d054f13e2107845ad97f726c786b8202afb9 1604 
spip_3.1.4-3~deb9u1.dsc
 884778eca338242da714641727b9acaa8ec10a5aefeefc1dbe1d38ad379d8318 5848656 
spip_3.1.4.orig.tar.xz
 005526c5806b00dd524d5d437ccc318ede3c989687f7a29b2db0b5cbc57be6ef 81588 
spip_3.1.4-3~deb9u1.debian.tar.xz
Files:
 5e38b7a4eda96a6d3962acedbfbd12d3 1604 web extra spip_3.1.4-3~deb9u1.dsc
 773ba92d20896200e8301361cbc814f6 5848656 web extra spip_3.1.4.orig.tar.xz
 177ecfbf57bb01da37084c392952cc3f 81588 web extra 
spip_3.1.4-3~deb9u1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEeHVNB7wJXHRI941mBYwc+UT2vTwFAllKA5AACgkQBYwc+UT2
vTxR7ggAn7ij0FPeor1NJLpQvJoLUaaQU/8GrxE5wmPXfdYJzqs3ltfWO1+DlA+P
4teGPAMQBZiK84uCN91xm3EvS5Xfo/BiS7ATTxX1nB4Br//ZPAHoDLNCxQMD4aRw
uWUDKyPURA9Qm5efK1R3tSPYnwYO+7/rtB6pWKZYXvIe0bHKEGP1M1D5A3SRiV3R
0I1enXSb0lO22UGudlUpAR4hbqAYggl7/DegVOf2StumJnzXHt0Ef6AGnscYeblY
NFdhiYbUbMP1AR/JMoyHWzlwynBw+WaoJ70q5/r11tA1yStL9dUai+eK5BlJEsK6
JDWnZzCneAe1HLq/N8ls5cTHtHK8ag==
=+4mB
-END PGP SIGNATURE End Message ---

Bug#865498: marked as done (drupal7: CVE-2017-6922: Files uploaded by anonymous users into a private file system can be accessed by other anonymous users)

[Debian Bug Tracking System]

Your message dated Sat, 24 Jun 2017 14:47:19 +
with message-id 
and subject line Bug#865498: fixed in drupal7 7.52-2+deb9u1
has caused the Debian Bug report #865498,
regarding drupal7: CVE-2017-6922: Files uploaded by anonymous users into a 
private file system can be accessed by other anonymous users
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.)


-- 
865498: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865498
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: drupal7
Version: 7.52-2
Severity: normal
Tags: security patch upstream fixed-upstream

Hi,

the following vulnerability was published for drupal7.

CVE-2017-6922[0]:
|Files uploaded by anonymous users into a private file system can be
|accessed by other anonymous users

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-6922
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-6922

Please adjust the affected versions in the BTS as needed. Is jessie as
well affected with based version 7.32?

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: drupal7
Source-Version: 7.52-2+deb9u1

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

Debian distribution maintenance software
pp.
Gunnar Wolf  (supplier of updated drupal7 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: Thu, 22 Jun 2017 11:04:29 -0500
Source: drupal7
Binary: drupal7
Architecture: source all
Version: 7.52-2+deb9u1
Distribution: stretch-security
Urgency: high
Maintainer: Gunnar Wolf 
Changed-By: Gunnar Wolf 
Description:
 drupal7- fully-featured content management framework
Closes: 865498
Changes:
 drupal7 (7.52-2+deb9u1) stretch-security; urgency=high
 .
   * Backported from 7.56: SA-CORE-2017-003: Files uploaded by anonymous
 users into a private file system can be accessed by other anonymous
 users. (CVE-2017-6922) (Closes: #865498)
Checksums-Sha1:
 17e9a81379a3c147f0755d64b0148515be99fb19 1904 drupal7_7.52-2+deb9u1.dsc
 fceb7a2891e870eae1a027d7f06028aa24dc58b2 3289714 drupal7_7.52.orig.tar.gz
 210c2fbd81a7bdf760ac952e745ac354b91abf74 190024 
drupal7_7.52-2+deb9u1.debian.tar.xz
 147da0dcfeadccd822810b092d874587acfd31fb 2520630 drupal7_7.52-2+deb9u1_all.deb
 72b3706fb7acb046b154b3be09a24ac6e192600c 8437 
drupal7_7.52-2+deb9u1_amd64.buildinfo
Checksums-Sha256:
 f2de423c55d5962c02418ee4045c4914904ddd03565373399f4b37bf8d435499 1904 
drupal7_7.52-2+deb9u1.dsc
 ea09ec7c3555856591b7ac739dafbe7dbfba47d1ffe2a9a1f17fda490a91b8e8 3289714 
drupal7_7.52.orig.tar.gz
 fa84a5d85193b5f0df911ac085502ba5e4ca911407438dd65979b9270742c17e 190024 
drupal7_7.52-2+deb9u1.debian.tar.xz
 eb868eb50b0f9b731807e15131f99f092b8b3c30d8525a76fc8c55e4856274eb 2520630 
drupal7_7.52-2+deb9u1_all.deb
 47edf3422f8cb61f50c35bbe969eb1b6c852e420378fb7f4eeb640e6e3f3bbe8 8437 
drupal7_7.52-2+deb9u1_amd64.buildinfo
Files:
 cac5e6a5e21ad446b5b8558a5eed5356 1904 web extra drupal7_7.52-2+deb9u1.dsc
 4963e68ca12918d3a3eae56054214191 3289714 web extra drupal7_7.52.orig.tar.gz
 c78326fda2eb194bbc2c66468124e1f8 190024 web extra 
drupal7_7.52-2+deb9u1.debian.tar.xz
 f9ec98b99d04a0f500a96ac45c94a0ba 2520630 web extra 
drupal7_7.52-2+deb9u1_all.deb
 90f53414baf2a2dc174524a8902d71c8 8437 web extra 
drupal7_7.52-2+deb9u1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEq0HBxor9ZoygRev4ZzoD5MHbkh8FAllL7i0ACgkQZzoD5MHb
kh8/LRAAoK0F/u0vVbhVMM8f/UJ2qrKURkt5nQkvEaMe/X48Zz8f3UkJrkMc/MV6
ho9fNkG+Yq0+y9UR9CrCh5La/XbsnIvM6plREPkTziv8mGkyYUbtw2nJ2rjsGFGC
U5zDDYlUvf4xx/zHY+V9bJauBW46sPy9I4pluKKGHd6brGgD71gDYy8VCfqDImgL
WhMTsjA9siGyU3YY18ZTkpeJyAcS4ahELiw9qLA7Y+7+Rtg/Yti2X+998QztJGjg
ZILKIJbRUhg+AIOVPpoZI2Lejd907wxJT5ojn3CUyyjFsEX9g3hxvoESwLKsXBFy
TNClbKm2XSUkAV3ZHfl7FLtp30S5rF5DE3JDjhco931yWyi7F1i2YodjMoM4rT6f
KJh/eUW4FN4T9CcYnZFq66XSooRh4MRrL/1c90FllawpB3YlYRN9NNe+IYGqeaWP
cdd9qHjsv0OkwqgoYQdQccSKHU08RRxKaJNixi/FZ4Wec/yWQKu/4lL

Bug#865413: marked as done (flatpak: CVE-2017-9780: Flatpak security issue)

[Debian Bug Tracking System]

Your message dated Sat, 24 Jun 2017 14:47:31 +
with message-id 
and subject line Bug#865413: fixed in flatpak 0.8.5-2+deb9u1
has caused the Debian Bug report #865413,
regarding flatpak: CVE-2017-9780: Flatpak security issue
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.)


-- 
865413: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865413
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: flatpak
Version: 0.8.5-2
Severity: critical
Tags: security fixed-upstream
Forwarded: https://github.com/flatpak/flatpak/issues/845
Justification: potentially (in worst case) root security hole

The Flatpak developers recently released version 0.8.7 fixing a security
issue. A third-party app repository could include malicious apps that
contain files with inappropriate permissions, for example setuid or
world-writable. Older Flatpak versions would deploy the files with those
permissions, which would let a local attacker run the setuid executable
or write to the world-writable location.

In the case of the "system helper", files deployed as part of the app
are owned by root, so in the worst case they could be setuid root.

Mitigations:
* If you are running apps from a third party already, then there is
  already a trust relationship (the app is sandboxed, but the sandbox
  is not very strict in practice, and the third-party vendor chooses
  what permissions the app will have)
* The default polkit policies will not allow apps to be installed
  system-wide unless a privileged (root-equivalent) user has added
  the third-party app repository, which indicates that the privileged
  user trusts the operator of that repository
* The attacker exploiting the wrong permissions needs to be local

It seems that upstream consider this to be a minor security issue due
to those mitigations.

For the buster and sid suites, this will be fixed in 0.8.7-1 shortly.

For the experimental suite, this will be fixed in 0.9.6-1. That will
take a bit longer because it needs a newer version of libostree.

Security team: do you want a backport/DSA for stretch-security, or do
you consider the mitigations to be sufficient to fix this through
a stable update instead? I am hoping to get 0.8.7 into stretch r1 as a
stable update, but 0.8.6 contains unrelated bug fixes that I realise
you won't necessarily want in stretch-security (proposed-update tracked
at ).

For a stretch-security backport with just this fix, I could optionally
also include these security-hardening-related commits from 0.8.6:
https://github.com/flatpak/flatpak/commit/6265200c83f23acceb3c9b192ebc1ffa9db140de
https://github.com/flatpak/flatpak/commit/414d699621664913dadebcf5db39732b99268c37
Please let me know whether you would prefer those included or excluded.

S
--- End Message ---
--- Begin Message ---
Source: flatpak
Source-Version: 0.8.5-2+deb9u1

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated flatpak package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 21 Jun 2017 12:05:49 +0100
Source: flatpak
Binary: flatpak flatpak-builder flatpak-tests gir1.2-flatpak-1.0 libflatpak-dev 
libflatpak-doc libflatpak0
Architecture: source
Version: 0.8.5-2+deb9u1
Distribution: stretch-security
Urgency: high
Maintainer: Utopia Maintenance Team 

Changed-By: Simon McVittie 
Closes: 865413
Description: 
 flatpak- Application deployment framework for desktop apps
 flatpak-builder - Flatpak application building helper
 flatpak-tests - Application deployment framework for desktop apps (tests)
 gir1.2-flatpak-1.0 - Application deployment framework for desktop apps 
(introspection)
 libflatpak0 - Application deployment framework for desktop apps (library)
 libflatpak-dev - Application deployment framework for desktop apps 
(development)
 libflatpak-doc - Application deployment framework for desktop apps 
(documentation)
Changes:
 flatpak (0.8.5-2+deb9u1) stre

Bug#865549: linux-image-3.16.0-4: stackguard fix incorrect

[Ben Hutchings]

On Fri, 2017-06-23 at 09:45 +0200, Moritz Bechler wrote:
> Hi,
> 
> Fyi, the original patch also breaks openjdk (SEGV from JNI_CreateJavaVM)
> when the VM is launched on the main thread (which is not the case for
> the normal java launcher, but embedded uses - e.g. browser plugin <
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1699772>;,
> commons-daemon, ...).

Yes, that's what I worked out from bug #865303 and those merged with
it.

Ben.

> Can confirm that the updated patch fixes the problem (amd64).

-- 
Ben Hutchings
Sturgeon's Law: Ninety percent of everything is crap.


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

Processed: Re: Bug#807648: zyne: Requested version of wxPython not found

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #807648 [zyne] zyne: Fails to start (missing dep for wx?)
Severity set to 'grave' from 'normal'

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

Bug#865058: (no subject)

[J Mo]

Spectator here chiming in. Just upgraded and the module built okay for 
me. Likely a local system issue. Good luck getting it figured out OP.


-->modinfo /lib/modules/4.9.0-3-amd64/updates/dkms/nvidia-current-drm.ko
filename: /lib/modules/4.9.0-3-amd64/updates/dkms/nvidia-current-drm.ko
version:375.66
supported:  external
license:MIT
srcversion: C4CEF74C8A748A2437DB582
alias:  pci:v10DEd0E00sv*sd*bc04sc80i00*
alias:  pci:v10DEd*sv*sd*bc03sc02i00*
alias:  pci:v10DEd*sv*sd*bc03sc00i00*
depends:drm,drm_kms_helper,nvidia-modeset
vermagic:   4.9.0-3-amd64 SMP mod_unload modversions
parm:   modeset:Enable atomic kernel modesetting (1 = enable, 0 
= disable (default)) (bool)