Bug#867404: marked as done (python3-exam: incorrect dependencies)

[Debian Bug Tracking System]

Your message dated Sat, 08 Jul 2017 04:18:44 +
with message-id 
and subject line Bug#867404: fixed in exam 0.10.5-2
has caused the Debian Bug report #867404,
regarding python3-exam: incorrect dependencies
to be marked as done.

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

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


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

Due to a cut'n'paste error the dependencies are incorrect.

Proposed fix:

--- debian/control.old  2017-07-06 13:37:05.0 +
+++ debian/control  2017-07-06 13:37:21.0 +
@@ -59,7 +59,7 @@
 
 Package: python3-exam
 Architecture: all
-Depends: ${misc:Depends}, ${python:Depends}, python-mock
+Depends: ${misc:Depends}, ${python3:Depends}
 Description: Python module to help write better tests
  Exam is a Python toolkit for writing better tests.  It aims to remove
  a lot of the boiler plate testing code one often writes, while still
--- End Message ---
--- Begin Message ---
Source: exam
Source-Version: 0.10.5-2

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

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

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

Debian distribution maintenance software
pp.
Scott Kitterman  (supplier of updated exam 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: Fri, 07 Jul 2017 23:47:09 -0400
Source: exam
Binary: python-exam python3-exam
Architecture: source all
Version: 0.10.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Scott Kitterman 
Description:
 python-exam - Python module to help write better tests
 python3-exam - Python module to help write better tests
Closes: 867404
Changes:
 exam (0.10.5-2) unstable; urgency=medium
 .
   * Team upload.
   * Create DPMT git repository and refresh patches using gbp pq
   * Correct Vcs-* fields in debian/control to point to the correct package
 name
   * Use correct substitution varial for python3-exam so python3 interpreter
 depends are correctly generated (Closes: #867404)
   * Let dh_python determine the mock depends (corrects issue where python-
 exam incorrectly depended on python-mock instead of python3-mock)
Checksums-Sha1:
 28e387342405688097985f8baa2b37fffc23078b 2156 exam_0.10.5-2.dsc
 ce1c3d1f3879c02cd68d294c79e62341773def5c 3512 exam_0.10.5-2.debian.tar.xz
 67508d8923e7b90503f11b25d7162682e09bcf89 7183 exam_0.10.5-2_amd64.buildinfo
 830016876451cdbee59932e5a55a48ed141ce43f 13972 python-exam_0.10.5-2_all.deb
 0017abf5a1de4cc61ffea92adb453b7aeb682674 8170 python3-exam_0.10.5-2_all.deb
Checksums-Sha256:
 d15478b5a58031ea82197cc6fe1440b09d3e66da2325fb07161dfe7f8c060a5e 2156 
exam_0.10.5-2.dsc
 2e5ff2b51ccad7548c08739c81fc30d20a7c4f9bf0cbceb89f53eec3e402f519 3512 
exam_0.10.5-2.debian.tar.xz
 347d9bd35721b76952826eb9d5a1ce66b36a73849c3c10559fa160fc04224ace 7183 
exam_0.10.5-2_amd64.buildinfo
 f45656b1413718f128b3bd4eef467141cdc4d2f6d732d4ef6365c7303dca30fd 13972 
python-exam_0.10.5-2_all.deb
 61b83633e549ec53aa9a77927c3fae13bd62ce83770d8d65819cc9d10a276ae9 8170 
python3-exam_0.10.5-2_all.deb
Files:
 5db1bb3a1a7e9723e640d9489397d21b 2156 python optional exam_0.10.5-2.dsc
 5f5814d463ea2f65fc5e384610260e4e 3512 python optional 
exam_0.10.5-2.debian.tar.xz
 bbee896327fc7e67f3b4abb492bee512 7183 python optional 
exam_0.10.5-2_amd64.buildinfo
 5319f4d699c024b4c680a998a661ed01 13972 python optional 
python-exam_0.10.5-2_all.deb
 5ed51ad53e1cfc080116ceecb89fc603 8170 python optional 
python3-exam_0.10.5-2_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJZYFciAAoJEHjX3vua1ZrxltgP/2Nvs/aalAAbAYSP+xZGpVcM
hDF0f2etOD3vt0rWavylTfEhyHmrUKtUwVYkCwnydyReFxjUR8H8VUnDk7MoMCQb
rKOLk6OadZj2lhC2NQvwOZKCWD/ae1uOxDIH0AGPUeggIAHQd/6NW8S3piVOH8NV
pal5duj0ES78RS6cQTdmd8EnDgMkyJJK8x5aCpUofJF1Xa4U/rYSb8BYngW8A/UP
MQSPrQVTnxYO7RtQD7Ww2ANsct13hl02d7i8wlodYf7LmdOKQLRvjdb8hvzA5Lq3

Bug#866148: marked as done ([general] Do not require POSIX style argument order)

[Debian Bug Tracking System]

Your message dated Fri, 7 Jul 2017 22:02:58 -0400
with message-id <20170708020257.fv5zereteh6cu...@freya.jamessan.com>
and subject line Re: Bug#866148: [general] Do not require POSIX style argument 
order
has caused the Debian Bug report #866148,
regarding [general] Do not require POSIX style argument order
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.)


-- 
866148: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866148
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: devscripts
Version: 2.17.6
Severity: wishlist
Tags: patch
User: devscri...@packages.debian.org

Dear Maintainer,

the scripts "bts", "chdist" and "dpkg-depcheck" currently require the user
to put command-line arguments in POSIX way, i.e., option arguments
should come first and then non-option ones. As Perl's Getopt module
supports the environment variable POSIXLY_CORRECT (if it is enabled
then the POSIX order is required) I suggest we leave out the hard
coding of this order requirement out from the scripts. I
have included a patch.

Thank you,
Joona Kylmälä

-- Package-specific info:

--- /etc/devscripts.conf ---

--- ~/.devscripts ---
Not present

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

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

Versions of packages devscripts depends on:
ii  dpkg-dev  1.18.24
ii  libc6 2.24-12
ii  libfile-homedir-perl  1.00-1
ii  perl  5.24.1-4
ii  python3   3.5.3-1

Versions of packages devscripts recommends:
ii  apt 1.4.6
ii  at  3.1.20-3
ii  dctrl-tools 2.24-2+b1
ii  debian-keyring  2017.05.28
ii  dput0.12.1
ii  equivs  2.0.10
ii  fakeroot1.21-3.1
ii  file1:5.30-1
ii  gnupg   2.1.18-8
ii  libdistro-info-perl 0.15
ii  libdpkg-perl1.18.24
ii  libencode-locale-perl   1.05-1
ii  libgit-wrapper-perl 0.047-1
ii  liblist-compare-perl0.53-1
ii  liblwp-protocol-https-perl  6.06-2
ii  libsoap-lite-perl   1.20-1
ii  liburi-perl 1.71-1
ii  libwww-perl 6.15-1
ii  licensecheck3.0.29-1
ii  lintian 2.5.51
ii  man-db  2.7.6.1-2
ii  patch   2.7.5-1+b2
ii  patchutils  0.3.4-2
ii  python3-debian  0.1.30
ii  python3-magic   1:5.30-1
ii  sensible-utils  0.0.9
ii  strace  4.15-2
ii  unzip   6.0-21
ii  wdiff   1.2.2-2
ii  wget1.19.1-4
ii  xz-utils5.2.2-1.2+b1

Versions of packages devscripts suggests:
pn  adequate 
pn  autopkgtest  
pn  bls-standalone   
ii  build-essential  12.3
pn  check-all-the-things 
pn  cvs-buildpackage 
pn  devscripts-el
pn  diffoscope   
pn  disorderfs   
pn  dose-extra   
pn  duck 
pn  faketime 
pn  gnuplot  
ii  gpgv 2.1.18-8
pn  how-can-i-help   
ii  libauthen-sasl-perl  2.1600-1
pn  libfile-desktopentry-perl
pn  libnet-smtps-perl
pn  libterm-size-perl
ii  libtimedate-perl 2.3000-2
pn  libyaml-syck-perl
ii  mailutils [mailx]1:3.1.1-1
pn  mozilla-devscripts   
ii  mutt 1.8.3+neomutt20170609-2
ii  openssh-client [ssh-client]  1:7.5p1-5
pn  piuparts 
pn  ratt 
pn  reprotest
pn  svn-buildpackage 
pn  w3m  

-- no debconf information
>From dbc7b25c02abcb5669d924adb162cb28a3270c41 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Joonas=20Kylm=C3=A4l=C3=A4?= 
Date: Tue, 27 Jun 2017 18:40:13 +
Subject: [PATCH] Don't require POSIX style argument ordering

---
 scripts/bts.pl   | 2 +-
 scripts/chdist.pl| 2 +-
 scripts/dpkg-depcheck.pl | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git 

Bug#867631: marked as done (python-nanomsg: missing build dependency on python3-all-dev)

[Debian Bug Tracking System]

Your message dated Sat, 08 Jul 2017 01:18:51 +
with message-id 
and subject line Bug#867631: fixed in python-nanomsg 1.0-2
has caused the Debian Bug report #867631,
regarding python-nanomsg: missing build dependency on python3-all-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.)


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

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

...
I: pybuild base:184: python3.6 setup.py test 
running test
running egg_info
writing nanomsg.egg-info/PKG-INFO
writing dependency_links to nanomsg.egg-info/dependency_links.txt
writing top-level names to nanomsg.egg-info/top_level.txt
reading manifest file 'nanomsg.egg-info/SOURCES.txt'
writing manifest file 'nanomsg.egg-info/SOURCES.txt'
running build_ext
building '_nanomsg_cpy' extension
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes 
-g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.6m -c _nanomsg_cpy/wrapper.c 
-o build/temp.linux-amd64-3.6/_nanomsg_cpy/wrapper.o
_nanomsg_cpy/wrapper.c:1:20: fatal error: Python.h: No such file or directory
 #include 
^
compilation terminated.
test_pubsub (unittest.loader._FailedTest) ... ERROR
test_pair (unittest.loader._FailedTest) ... ERROR
test_general_socket_methods (unittest.loader._FailedTest) ... ERROR

==
ERROR: test_pubsub (unittest.loader._FailedTest)
--
ImportError: Failed to import test module: test_pubsub
Traceback (most recent call last):
  File "/usr/lib/python3.6/unittest/loader.py", line 153, in loadTestsFromName
module = __import__(module_name)
  File "/build/1st/python-nanomsg-1.0/tests/test_pubsub.py", line 8, in 
from nanomsg import (
  File "/build/1st/python-nanomsg-1.0/nanomsg/__init__.py", line 7, in 
from . import wrapper
  File "/build/1st/python-nanomsg-1.0/nanomsg/wrapper.py", line 4, in 
_wrapper = _load_wrapper()
  File "/build/1st/python-nanomsg-1.0/nanomsg_wrappers/__init__.py", line 16, 
in load_wrapper
return importlib.import_module('_nanomsg_' + _choice)
  File "/usr/lib/python3.6/importlib/__init__.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
ImportError: /build/1st/python-nanomsg-1.0/_nanomsg_cpy.so: undefined symbol: 
PyString_FromStringAndSize


==
ERROR: test_pair (unittest.loader._FailedTest)
--
ImportError: Failed to import test module: test_pair
Traceback (most recent call last):
  File "/usr/lib/python3.6/unittest/loader.py", line 153, in loadTestsFromName
module = __import__(module_name)
  File "/build/1st/python-nanomsg-1.0/tests/test_pair.py", line 8, in 
from nanomsg import (
  File "/build/1st/python-nanomsg-1.0/nanomsg/__init__.py", line 7, in 
from . import wrapper
  File "/build/1st/python-nanomsg-1.0/nanomsg/wrapper.py", line 4, in 
_wrapper = _load_wrapper()
  File "/build/1st/python-nanomsg-1.0/nanomsg_wrappers/__init__.py", line 16, 
in load_wrapper
return importlib.import_module('_nanomsg_' + _choice)
  File "/usr/lib/python3.6/importlib/__init__.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
ImportError: /build/1st/python-nanomsg-1.0/_nanomsg_cpy.so: undefined symbol: 
PyString_FromStringAndSize


==
ERROR: test_general_socket_methods (unittest.loader._FailedTest)
--
ImportError: Failed to import test module: test_general_socket_methods
Traceback (most recent call last):
  File "/usr/lib/python3.6/unittest/loader.py", line 153, in loadTestsFromName
module = __import__(module_name)
  File "/build/1st/python-nanomsg-1.0/tests/test_general_socket_methods.py", 
line 8, in 
from nanomsg import (
  File "/build/1st/python-nanomsg-1.0/nanomsg/__init__.py", line 7, in 
from . import wrapper
  File "/build/1st/python-nanomsg-1.0/nanomsg/wrapper.py", line 4, in 
_wrapper = _load_wrapper()
  File 

Bug#853805: marked as done (unknown-horizons: Use .png icons instead of .xpm)

[Debian Bug Tracking System]

Your message dated Sat, 08 Jul 2017 00:36:47 +
with message-id 
and subject line Bug#853805: fixed in unknown-horizons 2017.2-1
has caused the Debian Bug report #853805,
regarding unknown-horizons: Use .png icons instead of .xpm
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.)


-- 
853805: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853805
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: unknown-horizons
Version: 2017.1+ds-2
Tags: patch

unknown-horizons does not show up in the GNOME Software app in Ubuntu
but it does show up in Debian. This is because the appstream-generator
used by Ubuntu is a bit older and rejects all .xpm icons.

http://appstream.ubuntu.com/zesty/universe/issues/unknown-horizons.html
https://appstream.debian.org/sid/main/issues/unknown-horizons.html

The fix is pretty simple: use .png icons and do not ship a .xpm icon.
The higher resolution icons look better anyway.

I did see one difference. The .xpm has a banner that says Unknown
Horizons but the .png's don't. I think the clearer icon in an
interface like GNOME Shell's Activities Overview is more important
than that banner.

In my next email I'll attach a patch for this. There's also a patch to
drop the Debian menu because it's obsolete if your package has a
.desktop.
https://www.debian.org/doc/debian-policy/ch-opersys.html#s-menus

Thanks,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: unknown-horizons
Source-Version: 2017.2-1

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

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

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated unknown-horizons 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, 08 Jul 2017 00:59:45 +0200
Source: unknown-horizons
Binary: unknown-horizons
Architecture: source
Version: 2017.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Markus Koschany 
Description:
 unknown-horizons - 2D realtime strategy simulation
Closes: 853805
Changes:
 unknown-horizons (2017.2-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version 2017.2.
   * Declare compliance with Debian Policy 4.0.0.
   * Tighten dependency on python-fife.
   * Drop deprecated menu file and xpm icon. Remove imagemagick from
 Build-Depends.
   * Drop VERSION.patch. Fixed upstream.
   * Link svg icon to hicolor directory. Thanks to Jeremy Bicha for the report
 and Ronny Standtke for the patch. (Closes: #853805)
Checksums-Sha1:
 346fd0dbb090c32192fbb23f672eba47f57da9c5 2236 unknown-horizons_2017.2-1.dsc
 b97e607333de50cc2088ac7dae70b2399e87be24 196271888 
unknown-horizons_2017.2.orig.tar.xz
 3b82b477fd99d8c3f6e1ef501038b901d60dd924 12840 
unknown-horizons_2017.2-1.debian.tar.xz
 ea233ccc100958f728fc05d293c20bf253d52aca 7140 
unknown-horizons_2017.2-1_amd64.buildinfo
Checksums-Sha256:
 e0f1693116e1707f60dd6c838b1bfc5f15c40d8415b2708a1605add27ef3a678 2236 
unknown-horizons_2017.2-1.dsc
 7f5a5f4213a76fe0ce9c03eb542858a676654b398b8da6582706b9515521363c 196271888 
unknown-horizons_2017.2.orig.tar.xz
 c5d95f4f26deb244f8b89072741116d7d36b992c2de9f0eb7d7a727f782fb422 12840 
unknown-horizons_2017.2-1.debian.tar.xz
 efb3777b47e76488ee6ee920fd52d51a4614d236e717b5c6908e20137d43e763 7140 
unknown-horizons_2017.2-1_amd64.buildinfo
Files:
 c79f749f5d4d7945597429d087f40997 2236 games optional 
unknown-horizons_2017.2-1.dsc
 693220e258c6a8120cb006ac311e80ad 196271888 games optional 
unknown-horizons_2017.2.orig.tar.xz
 164ad03bc895d95ef6105da0dbe1bead 12840 games optional 
unknown-horizons_2017.2-1.debian.tar.xz
 a9edb3e693cacd659620392d398ee360 7140 games optional 
unknown-horizons_2017.2-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAllgIzRfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD
RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp

Bug#867324: marked as done (haskell-hgettext FTBFS: Expecting one more argument to `H.Module')

[Debian Bug Tracking System]

Your message dated Sat, 08 Jul 2017 00:19:00 +
with message-id 
and subject line Bug#867324: fixed in haskell-hgettext 0.1.30-15
has caused the Debian Bug report #867324,
regarding haskell-hgettext FTBFS: Expecting one more argument to `H.Module'
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.)


-- 
867324: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867324
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-hgettext
Version: 0.1.30-14
Severity: serious
Tags: buster sid

Some recent change in unstable makes haskell-hgettext FTBFS:

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

...
build_recipe
Running debian/hlibrary.setup build --builddir=dist-ghc
Building hgettext-0.1.30...
Preprocessing library hgettext-0.1.30...
[1 of 2] Compiling Text.I18N.GetText ( src/Text/I18N/GetText.hs, 
dist-ghc/build/Text/I18N/GetText.o )
[2 of 2] Compiling Distribution.Simple.I18N.GetText ( 
src/Distribution/Simple/I18N/GetText.hs, 
dist-ghc/build/Distribution/Simple/I18N/GetText.o )
[1 of 2] Compiling Text.I18N.GetText ( src/Text/I18N/GetText.hs, 
dist-ghc/build/Text/I18N/GetText.p_o )
[2 of 2] Compiling Distribution.Simple.I18N.GetText ( 
src/Distribution/Simple/I18N/GetText.hs, 
dist-ghc/build/Distribution/Simple/I18N/GetText.p_o )
Preprocessing executable 'hgettext' for hgettext-0.1.30...
[1 of 2] Compiling Paths_hgettext   ( dist-ghc/build/autogen/Paths_hgettext.hs, 
dist-ghc/build/hgettext/hgettext-tmp/Paths_hgettext.o )
[2 of 2] Compiling Main ( src/hgettext.hs, 
dist-ghc/build/hgettext/hgettext-tmp/Main.o )

src/hgettext.hs:52:40: error:
* Expecting one more argument to `H.Module'
  Expected a type, but `H.Module' has kind `* -> *'
* In the first argument of `H.ParseResult', namely `H.Module'
  In the type signature:
toTranslate :: String -> H.ParseResult H.Module -> [(Int, String)]
/usr/share/cdbs/1/class/hlibrary.mk:147: recipe for target 'build-ghc-stamp' 
failed
make: *** [build-ghc-stamp] Error 1
--- End Message ---
--- Begin Message ---
Source: haskell-hgettext
Source-Version: 0.1.30-15

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

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

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

Debian distribution maintenance software
pp.
Clint Adams  (supplier of updated haskell-hgettext 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: Fri, 07 Jul 2017 20:03:08 -0400
Source: haskell-hgettext
Binary: libghc-hgettext-dev libghc-hgettext-prof libghc-hgettext-doc
Architecture: source
Version: 0.1.30-15
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group 

Changed-By: Clint Adams 
Description:
 libghc-hgettext-dev - ${haskell:ShortDescription}${haskell:ShortBlurb}
 libghc-hgettext-doc - ${haskell:ShortDescription}${haskell:ShortBlurb}
 libghc-hgettext-prof - ${haskell:ShortDescription}${haskell:ShortBlurb}
Closes: 867324
Changes:
 haskell-hgettext (0.1.30-15) unstable; urgency=medium
 .
   * Patch for haskell-src-exts 1.18.  closes: #867324.
Checksums-Sha1:
 8cb7f1870d1c84c32fc783123effa8204b99839f 2634 haskell-hgettext_0.1.30-15.dsc
 3b52e12041bd518890c80f2f3103dad31e9cb032 6289 
haskell-hgettext_0.1.30.orig.tar.gz
 0b94a195730e9c4d667407dedaeac30c09b2d4a0 4304 
haskell-hgettext_0.1.30-15.debian.tar.xz
 65516b3391c7cd16de158696712e2c1be5f48361 7211 
haskell-hgettext_0.1.30-15_source.buildinfo
Checksums-Sha256:
 7667e7838933a99e031559e89e62baf489094db29a8bf2b8cca923ff0f7b3fd4 2634 
haskell-hgettext_0.1.30-15.dsc
 26453a4d359c99c41d462db9f8c9144d172523b3fa7076117a877e6c43f3ffdd 6289 
haskell-hgettext_0.1.30.orig.tar.gz
 0fd427ad3dda528f59ac90745bfbe2ecea1608c481e8bc85cf2e04378061bfa8 4304 
haskell-hgettext_0.1.30-15.debian.tar.xz
 f41201528455d0f06a758c64a1a0aa53a3d5dddc7f271786c9edb77a62f6b81e 7211 
haskell-hgettext_0.1.30-15_source.buildinfo
Files:
 

Bug#820194: marked as done (nasm: please make the build reproducible (font ordering in documentation))

[Debian Bug Tracking System]

Your message dated Fri, 07 Jul 2017 23:49:47 +
with message-id 
and subject line Bug#820194: fixed in nasm 2.13.01-2
has caused the Debian Bug report #820194,
regarding nasm: please make the build reproducible (font ordering in 
documentation)
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.)


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

Source: nasm
Version: 2.11.08
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps fileordering hostname umask
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi!

While working on the “reproducible builds” effort [1], we have noticed
that nasm could not be built reproducibly.

The attached patch sorts keys from a hash table listing fonts to ensure 
a stable file order when creating the postscript and pdf documentation. 
Once applied, nasm can be built reproducibly in our

current experimental framework.* sort 'keys' for reproducibility.

Author: Raymond Nicholson 

---
The information above should follow the Patch Tagging Guidelines, please
checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here
are templates for supplementary fields that you might want to add:

Origin: , 
Bug: 
Bug-Debian: https://bugs.debian.org/
Bug-Ubuntu: https://launchpad.net/bugs/
Forwarded: 
Reviewed-By: 
Last-Update: 

--- nasm-2.11.08.orig/doc/genps.pl
+++ nasm-2.11.08/doc/genps.pl
@@ -968,18 +968,18 @@ print "%%Pages: $curpage\n";
 print "%%BoundingBox: 0 0 ", $psconf{pagewidth}, ' ', $psconf{pageheight}, "\n";
 print "%%Creator: (NASM psflow.pl)\n";
 print "%%DocumentData: Clean7Bit\n";
-print "%%DocumentFonts: ", join(' ', keys(%ps_all_fonts)), "\n";
-print "%%DocumentNeededFonts: ", join(' ', keys(%ps_all_fonts)), "\n";
+print "%%DocumentFonts: ", join(' ', sort keys(%ps_all_fonts)), "\n";
+print "%%DocumentNeededFonts: ", join(' ', sort keys(%ps_all_fonts)), "\n";
 print "%%Orientation: Portrait\n";
 print "%%PageOrder: Ascend\n";
 print "%%EndComments\n";
 print "%%BeginProlog\n";
 
 # Emit the configurables as PostScript tokens
-foreach $c ( keys(%psconf) ) {
+foreach $c ( sort keys(%psconf) ) {
 print "/$c ", $psconf{$c}, " def\n";
 }
-foreach $c ( keys(%psbool) ) {
+foreach $c ( sort keys(%psbool) ) {
 print "/$c ", ($psbool{$c}?'true':'false'), " def\n";
 }
 
@@ -1007,7 +1007,7 @@ print "  definefont pop\n";
 print "} def\n";
 
 # Emit fontset definitions
-foreach $font ( keys(%ps_all_fonts) ) {
+foreach $font ( sort keys(%ps_all_fonts) ) {
 print '/',$font,'-NASM /',$font," nasmenc\n";
 }
 
--- End Message ---
--- Begin Message ---
Source: nasm
Source-Version: 2.13.01-2

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

Debian distribution maintenance software
pp.
Jordan Justen  (supplier of updated nasm 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, 18 May 2017 23:02:49 -0700
Source: nasm
Binary: nasm
Architecture: source
Version: 2.13.01-2
Distribution: unstable
Urgency: medium
Maintainer: Anibal Monsalve Salazar 
Changed-By: Jordan Justen 
Description:
 nasm   - General-purpose x86 assembler
Closes: 820194
Changes:
 nasm (2.13.01-2) unstable; urgency=medium
 .
   [ Raymond Nicholson ]
   * sort 'keys' for reproducibility (doc/genps.pl), Closes: #820194
 .
   [ Gianfranco Costamagna ]
   * Switch to new dh calls
   * Switch to compat level 10
   * Add font-config to build-dependencies, fixing an error during build.
Checksums-Sha1:
 12a2ef5141ba3d8d75961c8b0140d405b9d8ffe8 1856 nasm_2.13.01-2.dsc
 4904379d80fbec5d3ab9bb8b9016417f25160bf2 16340 nasm_2.13.01-2.debian.tar.xz
 2531e0c97e42bd465c5416087d0dfb597e39b397 7110 nasm_2.13.01-2_source.buildinfo
Checksums-Sha256:
 

Bug#866710: marked as done (golang-golang-x-tools FTBFS with gccgo)

[Debian Bug Tracking System]

Your message dated Fri, 07 Jul 2017 23:03:57 +
with message-id 
and subject line Bug#866710: fixed in golang-golang-x-tools 
1:0.0~git20170707.0.bce9606b+ds-1
has caused the Debian Bug report #866710,
regarding golang-golang-x-tools FTBFS with gccgo
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.)


-- 
866710: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866710
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-golang-x-tools
Version: 1:0.0~git20170629.0.1b3bb8de-1
Severity: serious

https://buildd.debian.org/status/package.php?p=golang-golang-x-tools=sid

...
GOROOT=/<>/build/root GOPATH=/<>/build go install -v \
golang.org/x/tools/cmd/godoc
golang.org/x/tools/cmd/godoc
mv -v /<>/build/root/bin/godoc /<>/build/bin
mv: cannot stat '/<>/build/root/bin/godoc': No such file or 
directory
debian/rules:32: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 1
--- End Message ---
--- Begin Message ---
Source: golang-golang-x-tools
Source-Version: 1:0.0~git20170707.0.bce9606b+ds-1

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

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

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

Debian distribution maintenance software
pp.
Anthony Fok  (supplier of updated golang-golang-x-tools 
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: Fri, 07 Jul 2017 16:18:16 -0600
Source: golang-golang-x-tools
Binary: golang-golang-x-tools golang-go.tools golang-golang-x-tools-dev 
golang-go.tools-dev
Architecture: source all amd64
Version: 1:0.0~git20170707.0.bce9606b+ds-1
Distribution: unstable
Urgency: medium
Maintainer: pkg-go 
Changed-By: Anthony Fok 
Description:
 golang-go.tools - Transitional package for golang-golang-x-tools
 golang-go.tools-dev - Transitional package for golang-golang-x-tools-dev
 golang-golang-x-tools - supplementary Go tools
 golang-golang-x-tools-dev - supplementary Go tools (development files)
Closes: 866710
Changes:
 golang-golang-x-tools (1:0.0~git20170707.0.bce9606b+ds-1) unstable; 
urgency=medium
 .
   * New upstream snapshot.
   * Delete 0010-fix-gorename-tests.patch because "x/tools/cmd/rename:
 tests are failing for Go 1.7 and Go 1.8" has been fixed upstream.
   * Remove GOROOT hack (needed by gccgo-6 but not gccgo-7).
 gccgo-7 no longer installs godoc into $GOROOT/bin like gccgo-6 did,
 and the old GOROOT hack would actually cause FTBFS with gccgo-7.
 (Closes: #866710)
   * Update and re-enable patches which disable or fix/workaround
 issues with certain tests with gccgo-7.
Checksums-Sha1:
 a01fb2ee3d362053c9bd8cf6730ca2bbab5c8e01 2678 
golang-golang-x-tools_0.0~git20170707.0.bce9606b+ds-1.dsc
 eec8e0ab81621843ba4ecf1bed6c8f70f2aa2fbc 928756 
golang-golang-x-tools_0.0~git20170707.0.bce9606b+ds.orig.tar.xz
 10cb4744334331955625c058ecb09b2343b93029 24344 
golang-golang-x-tools_0.0~git20170707.0.bce9606b+ds-1.debian.tar.xz
 bc65c192b81b53cf339eddd9749db28dea12fbd4 11870 
golang-go.tools-dev_0.0~git20170707.0.bce9606b+ds-1_all.deb
 a681d36d1e37c1f457d280b743f4c55027690b2d 11852 
golang-go.tools_0.0~git20170707.0.bce9606b+ds-1_amd64.deb
 73e6e2b13dacacd6faf067544a018919cd393f2c 939844 
golang-golang-x-tools-dev_0.0~git20170707.0.bce9606b+ds-1_all.deb
 a252c002596858ef9a9ef6fa62bf4b289448e20d 7225 
golang-golang-x-tools_0.0~git20170707.0.bce9606b+ds-1_amd64.buildinfo
 f6d6f0506b735f2b8dbc42152c0d037d04608e49 14333292 
golang-golang-x-tools_0.0~git20170707.0.bce9606b+ds-1_amd64.deb
Checksums-Sha256:
 e8c449bac2abb33ba9aa44b0959b3bedd1a367c0650caeed7d94eaf83f50892a 2678 
golang-golang-x-tools_0.0~git20170707.0.bce9606b+ds-1.dsc
 66912ae332407b78425a9a1f755480ec824a3819c27c63545d805ab5298d8df6 928756 
golang-golang-x-tools_0.0~git20170707.0.bce9606b+ds.orig.tar.xz
 f805ed713b347a7042cf29896182981b0cb9bac315ec44084910ab565e6ce93d 24344 
golang-golang-x-tools_0.0~git20170707.0.bce9606b+ds-1.debian.tar.xz
 

Bug#867260: marked as done (FTBFS: not compatible with recent haskell-src-exts)

[Debian Bug Tracking System]

Your message dated Fri, 07 Jul 2017 22:34:02 +
with message-id 
and subject line Bug#867260: fixed in hothasktags 0.3.8-1
has caused the Debian Bug report #867260,
regarding FTBFS: not compatible with recent haskell-src-exts
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.)


-- 
867260: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867260
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: hothasktags
Version: 0.3.7-3
Severity: serious
Tags: upstream buster sid
Justification: fails to build from source (but built successfully in the past)
Control: forwarded -1 https://github.com/luqui/hothasktags/issues/34

hothasktags is not compatible with recent haskell-src-exts:
Language.Haskell.Exts.Annotated is no longer exported, and there have
been other API changes.

Upstream has been mostly inactive for quite some time, and I wonder if
we should keep hothasktags in Debian.  There are other ctags generators
for Haskell.

-- System Information:
Debian Release: 9.0
  APT prefers stable
  APT policy: (900, 'stable')
Architecture: i386 (i686)

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

Versions of packages hothasktags depends on:
ii  libc6 2.24-11+deb9u1
ii  libffi6   3.2.1-6
ii  libgmp10  2:6.1.2+dfsg-1

hothasktags recommends no packages.

hothasktags suggests no packages.

-- no debconf information

-- 
Sean Whitton


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: hothasktags
Source-Version: 0.3.8-1

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

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

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

Debian distribution maintenance software
pp.
Sean Whitton  (supplier of updated hothasktags 
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: Fri, 07 Jul 2017 22:53:56 +0100
Source: hothasktags
Binary: hothasktags
Architecture: source
Version: 0.3.8-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group 

Changed-By: Sean Whitton 
Description:
 hothasktags - Haskell ctags generator
Closes: 867260
Changes:
 hothasktags (0.3.8-1) unstable; urgency=medium
 .
   * New upstream release
   * Add 0001-update-to-haskell-src-exts-1.19.1.patch (Closes: #867260).
 Thanks to Joey Hess for the patch.
Checksums-Sha1:
 adbb89edc6932cde21405208c129f31786472d10 2234 hothasktags_0.3.8-1.dsc
 e1dcc895f1b9f2230303224e2a59dbfd3edb5b6d 6723 hothasktags_0.3.8.orig.tar.gz
 576f1303de0e25579d52c59648a4a0d661af8926 4608 hothasktags_0.3.8-1.debian.tar.xz
 ec4a52b4fadbc3a3252ae3c486f8da4d70529bea 5840 
hothasktags_0.3.8-1_source.buildinfo
Checksums-Sha256:
 518de35d87eceab148bf1584bfc0294560b348d96376312fcd2af72b20c1bd55 2234 
hothasktags_0.3.8-1.dsc
 07b00026a1b8e47719736ae6c64fe2396396c50c8367f82361e6fa4142dcf301 6723 
hothasktags_0.3.8.orig.tar.gz
 4dd1ab42aec57a77901e43f1bac400bcf57e1882e82e183af85005aba505ed63 4608 
hothasktags_0.3.8-1.debian.tar.xz
 0edbdacaac8f3318b821e432c06505c69202e4ce74585779e940ea2ddc9c62e0 5840 
hothasktags_0.3.8-1_source.buildinfo
Files:
 4e3596dd2d3a1e3d2c96c48e17064f3d 2234 devel optional hothasktags_0.3.8-1.dsc
 58c79bcaf4db8cd9aa57d896f37fe572 6723 devel optional 
hothasktags_0.3.8.orig.tar.gz
 928d721d0594dc40c9792bee330cd95b 4608 devel optional 
hothasktags_0.3.8-1.debian.tar.xz
 0e25ff383a53de875c8013cba3c53772 5840 devel optional 
hothasktags_0.3.8-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEm5FwB64DDjbk/CSLaVt65L8GYkAFAllgCOIACgkQaVt65L8G
YkCONg/9EpSrIjfi/9Wb00w8Xx5bzFtZj1GzfRkg4rhceh29ag0MvTZGUdONHoHG
DsqmNnbCyl3Fb3wfbEQQ1T0bShywjqegvsYXAB54bwZ1o4Lmx9fV8DY7zWkg0hHp
OKNpEifWiou7tuLoS7RmTDdjCnU7xMYwzYfWyFZfd6OWR+ZdyBQofd1AMLP2dlxJ
knpCLCU0pVLnikEUpse27VmMTyjm0mcHK+fesmOUt9v4ZJNVLcHPrwCw4Wnty9eY

Bug#720673: marked as done (please use a version control system for packaging)

[Debian Bug Tracking System]

Your message dated Sat, 8 Jul 2017 00:31:26 +0200
with message-id <20170708003126.2f845ff6@localhost>
and subject line Re: please use a version control system for packaging
has caused the Debian Bug report #720673,
regarding please use a version control system for packaging
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.)


-- 
720673: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720673
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gmrun
Version: 0.9.2-2.1
Severity: wishlist

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi,

it would be nice, if you could use a VCS (Git :-) for the packaging of gmrun
so that others can easily contribute.

Thank you, Thomas Koch

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

Kernel: Linux 3.10-0.bpo.2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gmrun depends on:
ii  libatk1.0-0 2.4.0-2
ii  libc6   2.13-38
ii  libcairo2   1.12.2-3
ii  libfontconfig1  2.9.0-7.1
ii  libfreetype62.4.9-1.1
ii  libgcc1 1:4.7.2-5
ii  libglib2.0-02.33.12+really2.32.4-5
ii  libgtk2.0-0 2.24.10-2
ii  libpango1.0-0   1.30.0-1
ii  libpopt01.16-7
ii  libstdc++6  4.7.2-5

gmrun recommends no packages.

gmrun suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJSGLjhAAoJEAf8SJEEK6ZaLV4P/0ks5iJSORqZHSg1gCmPqOwS
7t8claYqDscVy7DglPWMa9AI3KlzEcm13p3KiDbl0P7h13GOGxZ4GbRS3/35vJFT
makvVt9vGds3jGSlHQMlIBg/z8myOLuecJY3uke19dL/AAX4OAv3V4CBrKR2rjMT
NB11pRl3jrR2RjOQH9CU4ERFfto6pix2zfMlwRnq673qB2yL7OTq5NJ/ws4qWrhq
Yj/bQuHyG2+Dv30lMJehN2gt6OYV19fSRxE+c6bQA68UwFm1UWaoVNsOrdpHUyVH
IK48dXFq6qx/AyhMV1cuk+CkThQqwaQfQ1evwiWHyGEiXLdDyQGoI7SnCr2CDaZb
PqRNaYmyhUShh6NnIOfDbjeM11CZuRPR3t2jEdGWf/gJCH6vp6MqBzUWNzHHXpmi
WxoiIQz1cXjo95wtAN7Rt3svMr1X01F2W2CKAEMRFilTitQ9zdbxrqaVpqyfRkIo
efRmTm2cp9vvxN1MHALc7wqeNcpg3R+rXp06A2BMvvx2nDmm658La0FOZiZKTFFi
zxbqnGGQo4YS+XkQPDElxkYr7UVlJXo7XzXyOm9CjQx1ajU8JZ9sxxHZSV7jWTNM
3/zW6wznMNB3W/GLIcde5mOcAc/wJrT5CyQnl/jtTUb1gNtgonwt6D7+lYoqXv3e
PSyfux00r7VO63PYnNeQ
=/AG0
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Hi Thomas,

I've just taken over maintenance of gmrun and I'm happy to report that
I'm using a Git repository as you suggested in 2013 :) .

https://anonscm.debian.org/git/collab-maint/gmrun.git

Regards
Lukas--- End Message ---

Bug#812172: marked as done (gmrun: Incorrect $TERM value in gmrun's children)

[Debian Bug Tracking System]

Your message dated Sat, 8 Jul 2017 00:24:35 +0200
with message-id <20170708002435.1edb20e0@localhost>
and subject line not a bug
has caused the Debian Bug report #812172,
regarding gmrun: Incorrect $TERM value in gmrun's children
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.)


-- 
812172: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812172
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gmrun
Version: 0.9.2-2.1+b1
Severity: normal

Dear Maintainer, child processes of gmrun have incorrect value of TERM variable.
It is set to 'x-terminal-emulator'. This does not seem to be affected by
'Terminal' seting in gmrunrc, some other logic is the cause.

To reproduce: launch mssh or synaptic through gmrun. With mssh it will be
apparent right away, synaptic will have problems with terminal-dependent tools
like whiptail complaining about unknown terminal.


-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (900, 'testing'), (400, 'unstable'), (300, 'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages gmrun depends on:
ii  libatk1.0-0  2.18.0-1
ii  libc62.21-6
ii  libcairo21.14.4-1
ii  libfontconfig1   2.11.0-6.3
ii  libfreetype6 2.6.1-0.1
ii  libgcc1  1:5.3.1-5
ii  libgdk-pixbuf2.0-0   2.32.3-1
ii  libglib2.0-0 2.46.2-3
ii  libgtk2.0-0  2.24.29-1
ii  libpango-1.0-0   1.38.1-1
ii  libpangocairo-1.0-0  1.38.1-1
ii  libpangoft2-1.0-01.38.1-1
ii  libpopt0 1.16-10
ii  libstdc++6   5.3.1-5

gmrun recommends no packages.

gmrun suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Thanks for reporting the cause here, closing as requested.--- End Message ---

Bug#867618: marked as done (sqlite3: CVE-2017-10989)

[Debian Bug Tracking System]

Your message dated Fri, 07 Jul 2017 21:49:52 +
with message-id 
and subject line Bug#867618: fixed in sqlite3 3.19.3-3
has caused the Debian Bug report #867618,
regarding sqlite3: CVE-2017-10989
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.)


-- 
867618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867618
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sqlite3
Version: 3.8.7.1-1
Severity: important
Tags: upstream security patch

Hi,

the following vulnerability was published for sqlite3.

CVE-2017-10989[0]:
| The getNodeSize function in ext/rtree/rtree.c in SQLite before 3.11.0,
| as used in GDAL and other products, mishandles undersized RTree blobs
| in a crafted database, leading to a heap-based buffer over-read or
| possibly unspecified other impact.

Even the above description mentions "before 3.11.0" (and actually would
be 3.17.0) the issue is still present in later versions, it's hidden, as
explained in [1]. There is a patch at [2]. So it might be as well be
applied to newer versions (and it's basically already queued upstream as
well, with the referenced commit).

, [ make test ]
| ...
| ! rtreeA-7.110 expected: [1 {undersize RTree blobs in "t1_node"}]
| ! rtreeA-7.110 got:  [1 {database disk image is malformed}]
| Time: rtreeA.test 56 ms
| ...
`

(unrelated, speaking of testsuite, would be great if #339368 could be
made working in Debian and maybe having autopkgtest smoke-tests running
the upstream testsuite, but not sure how feasible this is).

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-10989
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10989
[1] https://bugs.launchpad.net/ubuntu/+source/sqlite3/+bug/1700937/comments/7
[2] https://sqlite.org/src/info/66de6f4a

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: sqlite3
Source-Version: 3.19.3-3

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

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

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated sqlite3 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: Fri, 07 Jul 2017 20:59:53 +
Source: sqlite3
Binary: lemon sqlite3 sqlite3-doc libsqlite3-0-dbg libsqlite3-0 libsqlite3-dev 
libsqlite3-tcl
Architecture: source amd64 all
Version: 3.19.3-3
Distribution: unstable
Urgency: high
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Description:
 lemon  - LALR(1) Parser Generator for C or C++
 libsqlite3-0 - SQLite 3 shared library
 libsqlite3-0-dbg - SQLite 3 debugging symbols
 libsqlite3-dev - SQLite 3 development files
 libsqlite3-tcl - SQLite 3 Tcl bindings
 sqlite3- Command line interface for SQLite 3
 sqlite3-doc - SQLite 3 documentation
Closes: 867618
Changes:
 sqlite3 (3.19.3-3) unstable; urgency=high
 .
   * Backport fix for CVE-2017-10989, heap-based buffer over-read via
 undersized RTree blobs (closes: #867618).
Checksums-Sha1:
 5d9a53eda54f10e2b0d5ff9ee6e03e30eb68749f 2488 sqlite3_3.19.3-3.dsc
 de57db8c936d4c865cfa420932abeb96db421d06 17564 sqlite3_3.19.3-3.debian.tar.xz
 a5177212cdeb5bab8e648d24f61981d3f3af21b5 144096 lemon_3.19.3-3_amd64.deb
 029348f8ac2cda2a424d9e741f36a0e6fd1fb3d5 4429636 
libsqlite3-0-dbg_3.19.3-3_amd64.deb
 564bc19074391090e9b9fb22c71b521a1b92390d 582376 libsqlite3-0_3.19.3-3_amd64.deb
 82904d25e79fb52b512229b7df33f1ea8c01fd61 714774 
libsqlite3-dev_3.19.3-3_amd64.deb
 02362a05573b2027581109aee5b4f46845ddacb9 111770 
libsqlite3-tcl_3.19.3-3_amd64.deb
 b5cfd95e08064a6c48b9239cc1a8d6525af0a5a6 3596468 sqlite3-doc_3.19.3-3_all.deb
 1fca090e71708a97bf97247b3e4d6ab0bbbefc9c 8083 sqlite3_3.19.3-3_amd64.buildinfo
 866aeb52228bc727d52775027df604a44d4a5ef3 798808 sqlite3_3.19.3-3_amd64.deb
Checksums-Sha256:
 

Bug#867534: marked as done (toolz: missing test dep on python3-all)

[Debian Bug Tracking System]

Your message dated Fri, 07 Jul 2017 21:38:02 +
with message-id 
and subject line Bug#867534: fixed in toolz 0.8.2-3
has caused the Debian Bug report #867534,
regarding toolz: missing test dep on python3-all
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.)


-- 
867534: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867534
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: toolz
Version: 0.8.2-2
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu artful ubuntu-patch

Hi Diane,

As a follow-on to bug #867242, the toolz autopkgtests are still failing in
Ubuntu because pyversions -r now returns python3.6 in addition to python3.5:

autopkgtest [18:27:05]: test command1: [---
Testing with python3.6:
bash: python3.6: command not found
autopkgtest [18:27:05]: test command1: ---]

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/amd64/t/toolz/20170706_182717_02c7b@/log.gz

(This error would also be visible at ci.debian.net now that the python3.6
transition has started in Debian, but the most recent attempt to test toolz
failed for some reason.)

I've uploaded the attached one-liner patch to Ubuntu, which should fix the
issue.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru toolz-0.8.2/debian/tests/control toolz-0.8.2/debian/tests/control
--- toolz-0.8.2/debian/tests/control2016-12-21 20:52:27.0 -0800
+++ toolz-0.8.2/debian/tests/control2017-07-06 22:41:51.0 -0700
@@ -1,2 +1,2 @@
 Test-Command: set -e ; for py in $(py3versions -r 2>/dev/null) ; do cd 
"$ADTTMP" ; echo "Testing with $py:" ; $py -m pytest --pyargs toolz  ; done
-Depends: @, python3-pytest
+Depends: @, python3-pytest, python3-all
--- End Message ---
--- Begin Message ---
Source: toolz
Source-Version: 0.8.2-3

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

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

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

Debian distribution maintenance software
pp.
Diane Trout  (supplier of updated toolz 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: Fri, 07 Jul 2017 11:37:43 -0700
Source: toolz
Binary: python3-toolz python-toolz-doc
Architecture: source
Version: 0.8.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Diane Trout 
Description:
 python-toolz-doc - List processing tools and functional utilities documentation
 python3-toolz - List processing tools and functional utilities
Closes: 867534
Changes:
 toolz (0.8.2-3) unstable; urgency=medium
 .
   * Add python3-all dependency to tests/control to make sure
 we test against all available versions of Python 3.
 Thanks: Steve Langasek (Closes: #867534)
Checksums-Sha1:
 766028b76295d09effc7724e4015c1747ef9364d 2191 toolz_0.8.2-3.dsc
 d0e7b1b2f89f731846930c8f75ef68dd62cb6339 3756 toolz_0.8.2-3.debian.tar.xz
 3e4c90354c12d915a7f1b7dc2d8c3eff66ec225b 6517 toolz_0.8.2-3_source.buildinfo
Checksums-Sha256:
 722b6aacb4f231f52dff0c9046fb84bde77d4795f2ce3a052c172534ba664b9e 2191 
toolz_0.8.2-3.dsc
 345db73c3edf48ce3c7a1d651786577c193c9a6cac6198d34122cc111021d550 3756 
toolz_0.8.2-3.debian.tar.xz
 db39b5e05f1e0d5e1fc3df8edd02a6a9873616cc401816a20cbeaad9ad44bf67 6517 
toolz_0.8.2-3_source.buildinfo
Files:
 9dca1f6993417f102640d659fd75323e 2191 python optional toolz_0.8.2-3.dsc
 bb8ef90a643d5599abef96b350ba30ad 3756 python optional 
toolz_0.8.2-3.debian.tar.xz
 f3f0bb60928c3a4f5c6f5cbd42b1328f 6517 python optional 
toolz_0.8.2-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQVcMeSBIEX5AQ11mQ04NnM013AFAllf+qQACgkQmQ04NnM0

Bug#867532: marked as done (cacti: CVE-2017-10970: XSS vulnerability via link.php)

[Debian Bug Tracking System]

Your message dated Fri, 07 Jul 2017 21:03:55 +
with message-id 
and subject line Bug#867532: fixed in cacti 1.1.12+ds1-1
has caused the Debian Bug report #867532,
regarding cacti: CVE-2017-10970: XSS vulnerability via link.php
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.)


-- 
867532: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867532
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cacti
Version: 1.1.10+ds1-6
Severity: important
Tags: patch security upstream
Forwarded: https://github.com/Cacti/cacti/issues/838

Hi,

the following vulnerability was published for cacti.

CVE-2017-10970[0]:
| Cross-site scripting (XSS) vulnerability in link.php in Cacti 1.1.12
| allows remote anonymous users to inject arbitrary web script or HTML
| via the id parameter, related to the die_html_input_error function in
| lib/html_validate.php.

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-10970
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10970
[1] https://github.com/Cacti/cacti/issues/838

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: cacti
Source-Version: 1.1.12+ds1-1

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

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

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

Debian distribution maintenance software
pp.
Paul Gevers  (supplier of updated cacti 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: Fri, 07 Jul 2017 21:07:43 +0200
Source: cacti
Binary: cacti
Architecture: source
Version: 1.1.12+ds1-1
Distribution: unstable
Urgency: medium
Maintainer: Cacti Maintainer 
Changed-By: Paul Gevers 
Description:
 cacti  - web interface for graphing of monitoring systems
Closes: 867532
Changes:
 cacti (1.1.12+ds1-1) unstable; urgency=medium
 .
   * New upstream release
   * CVE-2017-10970 XSS vulnerability via link.php fixed (Closes: #867532)
   * Add version to jquery-tablesorter
   * Make sure that autopkgtests at least run again
Checksums-Sha1:
 f964455db7167901dbc2fec29430ac9681afa264 2131 cacti_1.1.12+ds1-1.dsc
 f405c3aedec346ae34730c393751258ca2285b5c 77309 
cacti_1.1.12+ds1.orig-docs-source.tar.gz
 bb2be437a4b82218e96e10f5b6daa2ab949f1331 3790582 cacti_1.1.12+ds1.orig.tar.gz
 87f3bf027396511747498f40502ebb0c1691d977 50388 cacti_1.1.12+ds1-1.debian.tar.xz
Checksums-Sha256:
 0d2ef617214f1bab3d5f58da96c3099e3fa943ff290a5a7c91ee7317b22f5971 2131 
cacti_1.1.12+ds1-1.dsc
 83f103e99fe92162830a984daa0a70a5ee7362840e774f157bfdab9cfc8c8a1f 77309 
cacti_1.1.12+ds1.orig-docs-source.tar.gz
 2dbc69066f3cab6e9fa6eb4d6a5d34b7f62ffe0acef7f517a5be95ede7b2c768 3790582 
cacti_1.1.12+ds1.orig.tar.gz
 d0c381eac466fab52161e9a05e1193fcc204193fd27fad7510fdd5afab9c7540 50388 
cacti_1.1.12+ds1-1.debian.tar.xz
Files:
 2924ad3475c19af0a6009a321ccfec31 2131 web extra cacti_1.1.12+ds1-1.dsc
 7ea58851062685a07347e8bd4a3e2e04 77309 web extra 
cacti_1.1.12+ds1.orig-docs-source.tar.gz
 fbf199e8c334d8975f3dc8b044ed43a0 3790582 web extra cacti_1.1.12+ds1.orig.tar.gz
 8593af7176efee3c2fa1b517ac84c2ac 50388 web extra 
cacti_1.1.12+ds1-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAllf9EkACgkQnFyZ6wW9
dQrCOgf9GOeJMlg7oDNsK0mdsF0ric+NbwterZ2/2+we+m3zbSLhCR9gEp25DY/U
JEbDvc4mBoG6Rna2FMNFasX93a9xWpK/Qy7FXRbIHc9UhdaCzwoCD30WLm4nJD/0
2LCZXhq5Ndb546XjF/vIkk9ccsdv1RszEODHPBlpKpHwPIV/PcT3+V4CBdOWfsuR
brC1MIqVyDNwtsYhZv57ljn6SggWThibhM3pCBIKfpp2/t36GOYp1uzA3yvVCxEk
AkCAJofWcsJXLunkOtOKMv8ms0oKexRcsJItjkVs2z6B6M6vz1pbUpa5UP1Gcbyn
lZefQWwU3XZrn8MPgWeolJeSj0EAlA==
=k3Ax
-END PGP SIGNATURE End Message ---

Bug#863969: marked as done (ncurses-term: fails to upgrade from 'sid' - trying to overwrite /usr/share/terminfo/d/dvtm)

[Debian Bug Tracking System]

Your message dated Fri, 07 Jul 2017 20:49:42 +
with message-id 
and subject line Bug#863969: fixed in ncurses 6.0+20170701-1
has caused the Debian Bug report #863969,
regarding ncurses-term: fails to upgrade from 'sid' - trying to overwrite 
/usr/share/terminfo/d/dvtm
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.)


-- 
863969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863969
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ncurses-term
Version: 6.0+20170408-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package ncurses-term.
  Preparing to unpack .../ncurses-term_6.0+20170408-1_all.deb ...
  Unpacking ncurses-term (6.0+20170408-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/ncurses-term_6.0+20170408-1_all.deb (--unpack):
   trying to overwrite '/usr/share/terminfo/d/dvtm', which is also in package 
dvtm 0.15-2
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/ncurses-term_6.0+20170408-1_all.deb


cheers,

Andreas


dvtm=0.15-2_ncurses-term=6.0+20170408-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: ncurses
Source-Version: 6.0+20170701-1

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

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

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

Debian distribution maintenance software
pp.
Sven Joachim  (supplier of updated ncurses 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: Fri, 07 Jul 2017 22:00:14 +0200
Source: ncurses
Binary: libtinfo5 libtinfo5-udeb libncurses5 libtinfo-dev libtinfo5-dbg 
libncurses5-dev libncurses5-dbg libncursesw5 libncursesw5-dev libncursesw5-dbg 
lib64ncurses5 lib64ncurses5-dev lib32ncurses5 lib32ncurses5-dev lib32ncursesw5 
lib32ncursesw5-dev lib64tinfo5 lib32tinfo5 lib32tinfo-dev ncurses-bin 
ncurses-base ncurses-term ncurses-examples ncurses-doc
Architecture: source
Version: 6.0+20170701-1
Distribution: unstable
Urgency: low
Maintainer: Craig Small 
Changed-By: Sven Joachim 
Description:
 lib32ncurses5 - shared libraries for terminal handling (32-bit)
 lib32ncurses5-dev - developer's libraries for ncurses (32-bit)
 lib32ncursesw5 - shared libraries for terminal handling (wide character 
support) (
 lib32ncursesw5-dev - developer's libraries for ncursesw (32-bit)
 lib32tinfo-dev - developer's library for the low-level terminfo library 
(32-bit)
 lib32tinfo5 - shared low-level terminfo library for terminal handling (32-bit)
 lib64ncurses5 - shared libraries for terminal handling (64-bit)
 lib64ncurses5-dev - developer's libraries for ncurses (64-bit)
 lib64tinfo5 - shared low-level terminfo library for terminal handling (64-bit)
 libncurses5 - shared libraries for terminal handling
 libncurses5-dbg - debugging/profiling libraries for ncurses
 libncurses5-dev - developer's libraries for ncurses
 libncursesw5 - shared libraries for terminal handling (wide character support)
 libncursesw5-dbg - debugging/profiling libraries for ncursesw
 libncursesw5-dev - developer's libraries for ncursesw
 libtinfo-dev - developer's library for the low-level terminfo library
 libtinfo5  - shared low-level terminfo library for terminal handling
 libtinfo5-dbg - debugging/profiling library for the low-level terminfo library
 libtinfo5-udeb - shared low-level terminfo library for terminal handling - 
udeb (udeb)
 ncurses-base - basic terminal type definitions
 ncurses-bin - terminal-related programs and man pages
 ncurses-doc - 

Bug#866968: marked as done (dwarfutils: CVE-2017-9998: SEGV libdwarf/dwarf_leb.c:291 in _dwarf_decode_s_leb128_chk)

[Debian Bug Tracking System]

Your message dated Fri, 07 Jul 2017 20:49:00 +
with message-id 
and subject line Bug#866968: fixed in dwarfutils 20170416-3
has caused the Debian Bug report #866968,
regarding dwarfutils: CVE-2017-9998: SEGV libdwarf/dwarf_leb.c:291 in 
_dwarf_decode_s_leb128_chk
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.)


-- 
866968: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866968
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dwarfutils
Version: 20170416-2
Severity: normal
Tags: security upstream

Hi,

the following vulnerability was published for dwarfutils.

CVE-2017-9998[0]:
| The _dwarf_decode_s_leb128_chk function in dwarf_leb.c in libdwarf
| through 2017-06-28 allows remote attackers to cause a denial of service
| (Segmentation fault) via a crafted file.

$~/dwarfutils-20170416# ./dwarfdump/dwarfdump ~/POC1

.debug_info
ASAN:DEADLYSIGNAL
=
==985==ERROR: AddressSanitizer: SEGV on unknown address 0x60462c598e45 (pc 
0x5611cdb92696 bp 0x7ffdcfc1c2a0 sp 0x7ffdcfc1c250 T0)
#0 0x5611cdb92695 in _dwarf_decode_s_leb128_chk libdwarf/dwarf_leb.c:291
#1 0x5611cdbc56a6 in _dwarf_get_size_of_val libdwarf/dwarf_util.c:371
#2 0x5611cdbb941d in _dwarf_get_value_ptr libdwarf/dwarf_query.c:519
#3 0x5611cdbb9e6c in dwarf_attr libdwarf/dwarf_query.c:614
#4 0x5611cdb9acab in dwarf_srcfiles dwarf_line.c:326
#5 0x5611cdb1a770 in print_one_die_section dwarfdump/print_die.c:812
#6 0x5611cdb18326 in print_infos dwarfdump/print_die.c:371
#7 0x5611cdb0599e in process_one_file dwarfdump/dwarfdump.c:1293
#8 0x5611cdb035d7 in main dwarfdump/dwarfdump.c:562
#9 0x7fa2134172b0 in __libc_start_main 
(/lib/x86_64-linux-gnu/libc.so.6+0x202b0)
#10 0x5611cdaffa09 in _start 
(/home/user/dwarfutils-20170416/dwarfdump/dwarfdump+0x4fa09)

AddressSanitizer can not provide additional info.
SUMMARY: AddressSanitizer: SEGV libdwarf/dwarf_leb.c:291 in 
_dwarf_decode_s_leb128_chk
==985==ABORTING

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

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: dwarfutils
Source-Version: 20170416-3

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

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

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

Debian distribution maintenance software
pp.
Fabian Wolff  (supplier of updated dwarfutils 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: Fri, 07 Jul 2017 14:31:46 +0200
Source: dwarfutils
Binary: dwarfdump libdwarf-dev libdwarf1
Architecture: source
Version: 20170416-3
Distribution: unstable
Urgency: medium
Maintainer: Fabian Wolff 
Changed-By: Fabian Wolff 
Closes: 866155 866968
Description: 
 dwarfdump  - utility to dump DWARF debug information from ELF objects
 libdwarf1  - library to consume and produce DWARF debug information (runtime)
 libdwarf-dev - library to consume and produce DWARF debug information
Changes:
 dwarfutils (20170416-3) unstable; urgency=medium
 .
   * Update debian/copyright.
   * Upgrade to Standards-Version 4.0.0 in debian/control (no changes).
   * Add patch 02-fix-CVE-2017-9998.patch to fix CVE-2017-9998
 (Closes: #866968).
   * Add override_dh_compress target in debian/rules to make sure the
 upstream changelog is compressed (Closes: #866155).
Checksums-Sha1: 
 18c4d7c9c6265ddd3b5cfaec14823bde7d94fbe5 2090 dwarfutils_20170416-3.dsc
 2406424f317a16ba586016ff83763a411a096901 1777385 
dwarfutils_20170416.orig.tar.gz
 a406a2f289dc8a9c1dd0ed79699d7bf23518b668 11284 
dwarfutils_20170416-3.debian.tar.xz
Checksums-Sha256: 
 41c25435b95cbbbfc8bc15e9c19a7b54f95b8828f23bc85d7168e6494728244e 2090 

Bug#851305: marked as done (onboard doesn't show any information in mate-session-properties)

[Debian Bug Tracking System]

Your message dated Fri, 07 Jul 2017 20:49:52 +
with message-id 
and subject line Bug#851305: fixed in onboard 1.4.1-1
has caused the Debian Bug report #851305,
regarding onboard doesn't show any information in mate-session-properties
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.)


-- 
851305: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851305
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: onboard
Version: 1.3.0-1
Severity: minor

Dear Maintainer,
Onboard doesn't show/share any description when opened up in
mate-session-properties. Sharing a picture for the same. Look forward
to seeing this fixed.

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

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

Versions of packages onboard depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-2
ii  gir1.2-gdkpixbuf-2.0 2.36.2-1
ii  gir1.2-glib-2.0  1.50.0-1
ii  gir1.2-gtk-3.0   3.22.5-1
ii  gir1.2-pango-1.0 1.40.3-3
ii  iso-codes3.72-1
ii  libc62.24-8
ii  libcairo-gobject21.14.8-1
ii  libcairo21.14.8-1
ii  libcanberra0 0.30-3
ii  libdconf10.26.0-2
ii  libgcc1  1:6.2.1-5
ii  libgdk-pixbuf2.0-0   2.36.2-1
ii  libglib2.0-0 2.50.2-2
ii  libgtk-3-0   3.22.5-1
ii  libhunspell-1.4-01.4.1-2+b1
ii  libpango-1.0-0   1.40.3-3
ii  libpangocairo-1.0-0  1.40.3-3
ii  librsvg2-common  2.40.16-1
ii  libstdc++6   6.2.1-5
ii  libx11-6 2:1.6.4-2
ii  libxi6   2:1.7.8-2
ii  libxkbfile1  1:1.0.9-2
ii  libxtst6 2:1.2.3-1
ii  onboard-common   1.3.0-1
ii  python3  3.5.1-4
ii  python3-cairo1.10.0+dfsg-5+b1
ii  python3-dbus 1.2.4-1
ii  python3-gi-cairo 3.22.0-2
pn  python3:any  

Versions of packages onboard recommends:
ii  gir1.2-appindicator3-0.1  0.4.92-4
ii  gir1.2-atspi-2.0  2.22.0-5
ii  onboard-data  1.3.0-1
ii  xdg-utils 1.1.1-1

Versions of packages onboard suggests:
ii  mousetweaks  3.12.0-1

-- no debconf information


-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8
--- End Message ---
--- Begin Message ---
Source: onboard
Source-Version: 1.4.1-1

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

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated onboard 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: Fri, 07 Jul 2017 21:09:25 +0200
Source: onboard
Binary: onboard onboard-common onboard-data gnome-shell-extension-onboard
Architecture: source
Version: 1.4.1-1
Distribution: unstable
Urgency: medium
Maintainer: MATE Packaging Team 

Bug#858773: marked as done (onboard: new upstream release 1.4.1)

[Debian Bug Tracking System]

Your message dated Fri, 07 Jul 2017 20:49:52 +
with message-id 
and subject line Bug#858773: fixed in onboard 1.4.1-1
has caused the Debian Bug report #858773,
regarding onboard: new upstream release 1.4.1
to be marked as done.

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

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


-- 
858773: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858773
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: onboard
Version: 1.4.1-1.1
Severity: wishlist

Dear Maintainer,

Onboard 1.4.0+ has some real neat features for Hybrid machine, where it
can detect operation mode for the device (tablet or laptop).

I have adopted your pacakging and extended it into gbp workflow. You can
see my changes at: https://github.com/rickysarraf/onboard

Thanks,
Ritesh

-- System Information:
Debian Release: 9.0
  APT prefers unstable-debug
  APT policy: (990, 'unstable-debug'), (990, 'testing-debug'), (990, 
'unstable'), (990, 'testing'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages onboard depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-2+b1
ii  gir1.2-gdkpixbuf-2.0 2.36.5-2
ii  gir1.2-glib-2.0  1.50.0-1+b1
ii  gir1.2-gtk-3.0   3.22.11-1
ii  gir1.2-pango-1.0 1.40.4-1
ii  iso-codes3.74-1
ii  libc62.24-9
ii  libcairo-gobject21.14.8-1
ii  libcairo21.14.8-1
ii  libcanberra0 0.30-3
ii  libdconf10.26.0-2+b1
ii  libgcc1  1:6.3.0-10
ii  libgdk-pixbuf2.0-0   2.36.5-2
ii  libglib2.0-0 2.50.3-2
ii  libgtk-3-0   3.22.11-1
ii  libhunspell-1.4-01.4.1-2+b2
ii  libpango-1.0-0   1.40.4-1
ii  libpangocairo-1.0-0  1.40.4-1
ii  librsvg2-common  2.40.16-1+b1
ii  libstdc++6   6.3.0-10
ii  libudev1 232-21
ii  libx11-6 2:1.6.4-3
ii  libxi6   2:1.7.9-1
ii  libxkbfile1  1:1.0.9-2
ii  libxtst6 2:1.2.3-1
ii  onboard-common   1.4.1-1.1
ii  python3  3.5.3-1
ii  python3-cairo1.10.0+dfsg-5+b1
ii  python3-dbus 1.2.4-1+b1
ii  python3-gi-cairo 3.22.0-2
pn  python3:any  

Versions of packages onboard recommends:
ii  gir1.2-appindicator3-0.1  0.4.92-4
ii  gir1.2-atspi-2.0  2.22.0-5+b1
ii  onboard-data  1.4.1-1.1
ii  xdg-utils 1.1.1-1

Versions of packages onboard suggests:
ii  mousetweaks  3.12.0-1+b1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: onboard
Source-Version: 1.4.1-1

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

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated onboard 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: Fri, 07 Jul 2017 21:09:25 +0200
Source: onboard
Binary: onboard onboard-common onboard-data gnome-shell-extension-onboard
Architecture: source
Version: 1.4.1-1
Distribution: unstable
Urgency: medium
Maintainer: MATE Packaging Team 
Changed-By: Mike Gabriel 
Description:
 

Bug#866155: marked as done (dwarfdump: broken symlink: /usr/share/doc/dwarfdump/changelog.gz -> ChangeLog.gz)

[Debian Bug Tracking System]

Your message dated Fri, 07 Jul 2017 20:49:00 +
with message-id 
and subject line Bug#866155: fixed in dwarfutils 20170416-3
has caused the Debian Bug report #866155,
regarding dwarfdump: broken symlink: /usr/share/doc/dwarfdump/changelog.gz -> 
ChangeLog.gz
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.)


-- 
866155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866155
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dwarfdump
Version: 20170416-2
Severity: normal
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

1m32.2s ERROR: FAIL: Broken symlinks:
  /usr/share/doc/dwarfdump/changelog.gz -> ChangeLog.gz


cheers,

Andreas


dwarfdump_20170416-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: dwarfutils
Source-Version: 20170416-3

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

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

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

Debian distribution maintenance software
pp.
Fabian Wolff  (supplier of updated dwarfutils 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: Fri, 07 Jul 2017 14:31:46 +0200
Source: dwarfutils
Binary: dwarfdump libdwarf-dev libdwarf1
Architecture: source
Version: 20170416-3
Distribution: unstable
Urgency: medium
Maintainer: Fabian Wolff 
Changed-By: Fabian Wolff 
Closes: 866155 866968
Description: 
 dwarfdump  - utility to dump DWARF debug information from ELF objects
 libdwarf1  - library to consume and produce DWARF debug information (runtime)
 libdwarf-dev - library to consume and produce DWARF debug information
Changes:
 dwarfutils (20170416-3) unstable; urgency=medium
 .
   * Update debian/copyright.
   * Upgrade to Standards-Version 4.0.0 in debian/control (no changes).
   * Add patch 02-fix-CVE-2017-9998.patch to fix CVE-2017-9998
 (Closes: #866968).
   * Add override_dh_compress target in debian/rules to make sure the
 upstream changelog is compressed (Closes: #866155).
Checksums-Sha1: 
 18c4d7c9c6265ddd3b5cfaec14823bde7d94fbe5 2090 dwarfutils_20170416-3.dsc
 2406424f317a16ba586016ff83763a411a096901 1777385 
dwarfutils_20170416.orig.tar.gz
 a406a2f289dc8a9c1dd0ed79699d7bf23518b668 11284 
dwarfutils_20170416-3.debian.tar.xz
Checksums-Sha256: 
 41c25435b95cbbbfc8bc15e9c19a7b54f95b8828f23bc85d7168e6494728244e 2090 
dwarfutils_20170416-3.dsc
 d340c395217d78a67bec069f9991130622626a87cdba73131d091cb2f1005d81 1777385 
dwarfutils_20170416.orig.tar.gz
 063cef0f3f4d459f80258d2ef5e9ef6bbd5f59e80fc0ed2f054ff6e807fd1016 11284 
dwarfutils_20170416-3.debian.tar.xz
Files: 
 e3c7f969c70bd3c8a5a885bc152e0d80 2090 libs optional dwarfutils_20170416-3.dsc
 6a53d2b55d3ee2da396d4d0711e5c251 1777385 libs optional 
dwarfutils_20170416.orig.tar.gz
 f961706ff23ed5ed1b672744dd522bf0 11284 libs optional 
dwarfutils_20170416-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEERsscqJ6jt0N2dh25FeCa9N9RgsgFAllf63gACgkQFeCa9N9R
gsiyew/8CrO1KxOn1kam6IF7JXALWpaPiLbajF3UHMvlw//ZTvfrxRp2YfxwjLgI
Ob34FD2W4i4swr+w+TfxOUx9L2B4LlhO3D9qhLXGSkJv5nqaee703KoXiTe8a7nS
TZDzIlXx1zLEbBJmT301x2L8cgd63cZGq/HLkMPG77KT1m4JSd0u/peEdhzCWZMs
W2NdlTjAWFFB8UBverzeLCJ93isjLJNjSUvKCglkTLoDWpcx8SAeTpZA0xa5IC8t
wUs6KKmPZc5jatwhJKn78cDu+bf0QVQEq/i7/CigJQ0A/joNioqjoz9grEUpJDyI
aPdqbsjnU5hnX2GsiO7LKTzSfy6JZeL0dB9jL8nxNPI0xHdNv0xHiBR0S5ASf/t6
MgGDuTLZGQoNVC2PyWcjhMz+t2h75BbCjf44u5CWYHJLa2cKIrnOFefRnS6O8giw
xj5KE6FOIy9xO3hhFxuBWMmf3k4GSJwD4mzyxdxDY+KcbmeSXU4UItscvIAufS9Z
mlvBN7k9CnWRjUist+y/cp+bTEkSd4uo5jFYhvrYiKG7zZwBPdzqhIqW8/QYdFHP
LM5Jl3jaJUQ3YFEq6sgtzqRPuz/ZnnnbcR2BWbooeQq4Qflz+HouTgj/5QrFCCit
YIWKdApnomw8OCkqPUhkTv9bhtTOF4vrWbs+3JaKKLgUpQBMMcg=
=NtyN
-END PGP SIGNATURE End Message ---

Bug#867622: marked as done (tor: after update unable to use/start tor)

[Debian Bug Tracking System]

Your message dated Fri, 7 Jul 2017 20:11:38 +
with message-id <20170707201138.zl7s6oexiyvja...@sarek.noreply.org>
and subject line Re: Bug#867622: tor: after update unable to use/start tor
has caused the Debian Bug report #867622,
regarding tor: after update unable to use/start tor
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.)


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

Dear Maintainer,
I used to start tor from an alias

/home/shirish/.local/share/torbrowser/tbb/x86_64/tor-browser_en-US/Browser/start-tor-browser

I updated tor as it was out of date and nothing happened.

It seems that the path has been changed to -

/home/shirish/.local/share/torbrowser/tbb/x86_64/tor-browser_en-US/start-tor-browser.desktop

Trying to run that either as an alias or via console I get the following -

┌─[shirish@debian] -
[~/.local/share/torbrowser/tbb/x86_64/tor-browser_en-US] - [10018]
└─[$] ./start-tor-browser.desktop
Launching './Browser/start-tor-browser --detach'...
./Browser/execdesktop: line 14: ./Browser/start-tor-browser: No such
file or directory

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

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

Versions of packages tor depends on:
ii  adduser  3.115
ii  init-system-helpers  1.48
ii  libc62.24-12
ii  libevent-2.0-5   2.0.21-stable-3
ii  libseccomp2  2.3.1-2.1
ii  libssl1.11.1.0f-3
ii  libsystemd0  233-9
ii  lsb-base 9.20161125
ii  zlib1g   1:1.2.8.dfsg-5

Versions of packages tor recommends:
ii  logrotate3.11.0-0.1
ii  tor-geoipdb  0.3.0.9-1
ii  torsocks 2.2.0-1

Versions of packages tor suggests:
pn  apparmor-utils   
pn  mixmaster
ii  obfs4proxy   0.0.7-1+b2
ii  obfsproxy0.2.13-2
ii  socat1.7.3.1-2+b1
pn  tor-arm  
ii  torbrowser-launcher  0.2.7-2

-- no debconf information

Looking forward to the fix.

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8
--- End Message ---
--- Begin Message ---
On Sat, 08 Jul 2017, shirish शिरीष wrote:

> Dear Maintainer,
> I used to start tor from an alias
> 
> /home/shirish/.local/share/torbrowser/tbb/x86_64/tor-browser_en-US/Browser/start-tor-browser
> 
> I updated tor as it was out of date and nothing happened.

The tor package and tor browser are two seperate things.

You need to talk to the tor browser people about TBB.

Cheers,
-- 
|  .''`.   ** Debian **
  Peter Palfrader   | : :' :  The  universal
 https://www.palfrader.org/ | `. `'  Operating System
|   `-https://www.debian.org/--- End Message ---

Bug#867499: marked as done (tiptop: Fix parallel bison FTBFS)

[Debian Bug Tracking System]

Your message dated Fri, 07 Jul 2017 19:34:40 +
with message-id 
and subject line Bug#867499: fixed in tiptop 2.3-3
has caused the Debian Bug report #867499,
regarding tiptop: Fix parallel bison FTBFS
to be marked as done.

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

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


-- 
867499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867499
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tiptop
Version: 2.3-2
Severity: important
Tags: patch

tiptop frequently FTBFS due to running bison twice in parallel.

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

...
gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
-I/usr/include/libxml2 -I.. -Wdate-time -D_FORTIFY_SOURCE=2  -c -o spawn.o 
spawn.c
gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
-I/usr/include/libxml2 -I.. -Wdate-time -D_FORTIFY_SOURCE=2  -c -o xml-parser.o 
xml-parser.c
gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
-I/usr/include/libxml2 -I.. -Wdate-time -D_FORTIFY_SOURCE=2  -c -o target.o 
target.c
bison -y -d ./calc.y
gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
-I/usr/include/libxml2 -I.. -Wdate-time -D_FORTIFY_SOURCE=2  -c -o priv.o priv.c
gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
-I/usr/include/libxml2 -I.. -Wdate-time -D_FORTIFY_SOURCE=2  -c -o error.o 
error.c
flex ./calc.lex
bison -y -d ./calc.y
gcc -g -O2 -fstack-protector-strong -Wformat -Werror=format-security 
-I/usr/include/libxml2 -I.. -I. -c y.tab.c
y.tab.c:636:0: error: unterminated #if
 #if YYDEBUG
 
Makefile:65: recipe for target 'y.tab.o' failed
make[2]: *** [y.tab.o] Error 1


The attached patch removes the double-calling of bison.
Description: Fix parallel FTBFS
 Don't run the same bison command twice in parallel.
Author: Adrian Bunk 

--- tiptop-2.3.orig/src/Makefile.in
+++ tiptop-2.3/src/Makefile.in
@@ -57,8 +57,9 @@ lex.yy.c: calc.lex
 lex.yy.o: lex.yy.c
$(CC) $(CFLAGS) -I$(srcdir) -c lex.yy.c
 
+y.tab.c: y.tab.h
 
-y.tab.c y.tab.h: calc.y
+y.tab.h: calc.y
$(YACC) -d $(srcdir)/calc.y
 
 y.tab.o: y.tab.c
--- End Message ---
--- Begin Message ---
Source: tiptop
Source-Version: 2.3-3

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

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

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

Debian distribution maintenance software
pp.
Tomasz Buchert  (supplier of updated tiptop 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: Fri, 07 Jul 2017 21:19:08 +0200
Source: tiptop
Binary: tiptop
Architecture: source
Version: 2.3-3
Distribution: unstable
Urgency: medium
Maintainer: Tomasz Buchert 
Changed-By: Tomasz Buchert 
Description:
 tiptop - performance monitoring tool for Linux
Closes: 867499
Changes:
 tiptop (2.3-3) unstable; urgency=medium
 .
   * d/control: bumped std-ver to 4.0.0 (no changes needed)
   * d/control: use debhelper 10
   * d/watch: use watch version 4
   * d/patches: fix parallel building (Closes: #867499)
Checksums-Sha1:
 a62ade2c118f08fab59c7886280911bb6cc44af9 1510 tiptop_2.3-3.dsc
 42c26bf2f4e10cc29f0682b17fcc15f1f53fc23f 2684 tiptop_2.3-3.debian.tar.xz
 c49c1eee1ef7425d11e79024728c09ed5cf476c8 5529 tiptop_2.3-3_amd64.buildinfo
Checksums-Sha256:
 8e009132fd004189fdebe004bb9f25cb334413437bde1b57ad220104f34acd20 1510 
tiptop_2.3-3.dsc
 2e2d3e590f7312cf4c2a0db546971233d3ed3eeb3f1005d27e4a5bb629429263 2684 
tiptop_2.3-3.debian.tar.xz
 21b25bbfe9972a48663d0ca9692fc8484b82d626058676f613e5e8f76097bfc7 5529 
tiptop_2.3-3_amd64.buildinfo
Files:
 bb054882bda93390dc77e586b5cfcaa4 1510 utils optional tiptop_2.3-3.dsc
 9887bc1cdf130583979fecc6b728cc44 2684 utils optional tiptop_2.3-3.debian.tar.xz
 0bda867a6a7fcf71551c105be3469ebd 5529 utils optional 
tiptop_2.3-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEs7i9UOfOjw7pOBilgsIKSinLv9UFAllf31gACgkQgsIKSinL

Bug#867510: marked as done (klaus: missing build dependency on python3-setuptools)

[Debian Bug Tracking System]

Your message dated Fri, 07 Jul 2017 19:04:23 +
with message-id 
and subject line Bug#867510: fixed in klaus 1.2.1-3
has caused the Debian Bug report #867510,
regarding klaus: missing build dependency on python3-setuptools
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.)


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

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

...
I: pybuild base:184: python3.6 setup.py clean 
Traceback (most recent call last):
  File "setup.py", line 3, in 
from setuptools import setup
ModuleNotFoundError: No module named 'setuptools'
E: pybuild pybuild:283: clean: plugin distutils failed with: exit code=1: 
python3.6 setup.py clean 
dh_auto_clean: pybuild --clean -i python{version} -p 3.6 3.5 returned exit code 
13
debian/rules:19: recipe for target 'override_dh_auto_clean' failed
make[1]: *** [override_dh_auto_clean] Error 25
--- End Message ---
--- Begin Message ---
Source: klaus
Source-Version: 1.2.1-3

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

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

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

Debian distribution maintenance software
pp.
Jelmer Vernooij  (supplier of updated klaus 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: Fri, 07 Jul 2017 17:41:30 +
Source: klaus
Binary: klaus python-klaus python3-klaus
Architecture: source all
Version: 1.2.1-3
Distribution: unstable
Urgency: medium
Maintainer: Jelmer Vernooij 
Changed-By: Jelmer Vernooij 
Description:
 klaus  - simple easy-to-set-up Git web viewer
 python-klaus - simple easy-to-set-up Git web viewer
 python3-klaus - simple easy-to-set-up Git web viewer
Closes: 867510
Changes:
 klaus (1.2.1-3) unstable; urgency=medium
 .
   * Add missing build-dependency on python3-setuptools. Closes: #867510
Checksums-Sha1:
 3c6800d783a055b9e1bfa3c6f3a01dbd920cf69a 2171 klaus_1.2.1-3.dsc
 cef6eccee0a2662a10a0d6fc9f7c5ce964bed8be 13124 klaus_1.2.1-3.debian.tar.xz
 2377a5e61fd64f02694330b9a2e97c6e38de2073 17336 klaus_1.2.1-3_all.deb
 f2af06e5afbe6246af3f11a82e84a6aa917109d1 8176 klaus_1.2.1-3_amd64.buildinfo
 1eb50e40ed75a3c59828e4efe49f94331c130e96 45450 python-klaus_1.2.1-3_all.deb
 c84ebbd9f8a06756c17211d5f886cc98ed16e55b 45492 python3-klaus_1.2.1-3_all.deb
Checksums-Sha256:
 e0fd0d787f7ce1278a7e78fa6976b5762055596ba31b2b37a86138a2a99c8929 2171 
klaus_1.2.1-3.dsc
 08b73c8780f79e05613327861bcee9f0ee6fb13b91691505b3c54bfc8b6af563 13124 
klaus_1.2.1-3.debian.tar.xz
 369e9c79fd832038efeb56c49ead3020a4ac5efb2f71036210ecf4d889dd5b80 17336 
klaus_1.2.1-3_all.deb
 81c5c53c1308d7c5de9ca49954c59e1cddfbd56cfc7347a004add502559188f4 8176 
klaus_1.2.1-3_amd64.buildinfo
 e1340a3d83d8fc71e6be8c5cf1d815884d3239f14bf63041fa2c499a71a4bb20 45450 
python-klaus_1.2.1-3_all.deb
 63c74808ba09699759967f75a9a6d5b4e281aac44e9823cf94f9ea084a023244 45492 
python3-klaus_1.2.1-3_all.deb
Files:
 d043023c90b3f32545bfa9d8696b5bd7 2171 vcs optional klaus_1.2.1-3.dsc
 6ccc85c07ee7f3361050a185926a6a97 13124 vcs optional klaus_1.2.1-3.debian.tar.xz
 2e20b181746fb5c82be0e546573ae54b 17336 vcs optional klaus_1.2.1-3_all.deb
 4a19a1eb1ce33099437dc6a2407aa162 8176 vcs optional 
klaus_1.2.1-3_amd64.buildinfo
 ae91e7e7b02cdc410931d6d326c7b40d 45450 python optional 
python-klaus_1.2.1-3_all.deb
 a4e24ac812d056f321e0b72df878b123 45492 python optional 
python3-klaus_1.2.1-3_all.deb

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEoX1YPWJ8eQgrAMsfmi0kpQTR6fgFAllf14cACgkQmi0kpQTR
6fh7WAf9GttRuJJkSUjMm9Y0fIqxRuW+wihqZhHGTjxLt4uu4iSZEbm4S4Kmb//d
820cSr0v47itG42eZuyj0hHNqmPjqUAbsjiIDBu2uAx4g+9xhbKZjhV/TFXVi8Tn
Dq32qYgmD/tsjc/ibD3cY8TDDxMEu9R2XjgWEETMefrW0ni86APlB4Y371/37p9e
tEjSl7tOZoYCOKZl/leHHv8vt8cm7dPV+KfU/wCSwzJSf2AfhYwrXZAlZpAn76ki
fv9uJe3mp4hZ5X6Xmupp+kmscfaPEZ+wB5sJyJsEYHgL2me64iZwU+vZ5a279Rx7
VUk8NG9mzQtnwlEtHsE7YniOoyk7EQ==
=V/O3
-END PGP SIGNATURE End Message ---

Bug#753454: marked as done ([libjs-jquery-history] "The application state can be stored into a URL hash and restore the state from it." in extended description)

[Debian Bug Tracking System]

Your message dated Fri, 07 Jul 2017 19:04:05 +
with message-id 
and subject line Bug#753454: fixed in jquery-goodies 12-1
has caused the Debian Bug report #753454,
regarding [libjs-jquery-history] "The application state can be stored into a 
URL hash and restore the state from it." in extended description
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.)


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

Package: libjs-jquery-history
Version: 10-1
Severity: minor

The extended description ends with:
The application state can be stored into a URL hash and restore the state from it. 


The end of the sentence made more sense in the previous version of this 
sentence:
You can store the application state into URL hash and restore the state from it. 


I suggest:
The application state can be stored into a URL hash and later restored from the hash. 



By the way, "A jQuery history plugin" reads strange. I'd recommend "The jQuery 
history plugin" over that.

--
Filipus Klutiero
http://www.philippecloutier.com
--- End Message ---
--- Begin Message ---
Source: jquery-goodies
Source-Version: 12-1

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

Debian distribution maintenance software
pp.
Paul Gevers  (supplier of updated jquery-goodies 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: Fri, 07 Jul 2017 20:26:35 +0200
Source: jquery-goodies
Binary: libjs-jquery-event-drag libjs-jquery-event-drop 
libjs-jquery-galleriffic libjs-jquery-jfeed libjs-jquery-jush 
libjs-jquery-meiomask libjs-jquery-mousewheel libjs-jquery-easing 
libjs-jquery-history libjs-jquery-opacityrollover libjs-jquery-form 
libjs-jquery-tipsy libjs-jquery-fancybox libjs-jquery-cookie 
libjs-jquery-metadata libjs-jquery-treetable libjs-jquery-livequery 
libjs-jquery-countdown libjs-jquery-resize libjs-jquery-resize-doc 
libjs-jquery-uploadify libjs-jquery-slides libjs-jquery-fullscreen
Architecture: source
Version: 12-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Paul Gevers 
Description:
 libjs-jquery-cookie - jQuery cookie plugin
 libjs-jquery-countdown - jQuery Countdown
 libjs-jquery-easing - jQuery Easing Plugin
 libjs-jquery-event-drag - jQuery Event Drag
 libjs-jquery-event-drop - jQuery Event Drop
 libjs-jquery-fancybox - fancy lightbox alternative
 libjs-jquery-form - jQuery Form Plugin
 libjs-jquery-fullscreen - jQuery FullScreen Plugin
 libjs-jquery-galleriffic - jQuery Galleriffic plugin
 libjs-jquery-history - jQuery history plugin
 libjs-jquery-jfeed - jQuery RSS/Atom feed parser plugin
 libjs-jquery-jush - jQuery Syntax Highlighter
 libjs-jquery-livequery - jQuery Live Query
 libjs-jquery-meiomask - jQuery mask plugin
 libjs-jquery-metadata - jQuery plugin for parsing metadata from elements
 libjs-jquery-mousewheel - jQuery Mousewheel Plugin
 libjs-jquery-opacityrollover - jQuery Opacity Rollover plugin
 libjs-jquery-resize - jQuery resize
 libjs-jquery-resize-doc - jQuery resize (doc)
 libjs-jquery-slides - Simple slideshow plugin for jQuery
 libjs-jquery-tipsy - jQuery Facebook-style tooltip plugin
 libjs-jquery-treetable - jQuery treeTable Plugin
 libjs-jquery-uploadify - plugin for easy multiple file upload
Closes: 753454
Changes:
 jquery-goodies (12-1) unstable; urgency=medium
 .
   * Team upload
   * Update description of libjs-jquery-history (Closes: #753454)
   * Drop libjs-jquery-tablesorter which is now build by jquery-tablesorter
Checksums-Sha1:
 b730a4f66cc804bb53e9a494eb38515828448431 3270 jquery-goodies_12-1.dsc
 b9965fb21123a75d1c2c0ca0aa973bcf98a64a10 1238604 jquery-goodies_12.orig.tar.xz
 6c72df6423e2e624620f451460040e7a2d113870 12604 
jquery-goodies_12-1.debian.tar.xz
Checksums-Sha256:
 0e1f2f4667a5a615b8d6ba6671554d634ede413e71e3d1ebea272593c6e096d2 3270 

Bug#866768: marked as done (r-base: R does not set the default user directory.)

[Debian Bug Tracking System]

Your message dated Fri, 07 Jul 2017 18:51:41 +
with message-id 
and subject line Bug#866768: fixed in r-base 3.4.1-2
has caused the Debian Bug report #866768,
regarding r-base: R does not set the default user directory.
to be marked as done.

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

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


-- 
866768: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866768
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: r-base
Version: 3.4.1-1
Severity: important

By default, when asked to install or upgrade a package as a non-root user, R
creates a subdirectory in the home directory for such packages, and puts it at
the front of the library path. After the upgrade, I get the following:

$ R

R version 3.4.1 (2017-06-30) -- "Single Candle"
Copyright (C) 2017 The R Foundation for Statistical Computing
Platform: x86_64-pc-linux-gnu (64-bit)

[SNIP]

> update.packages(ask=FALSE)
--- Please select a CRAN mirror for use in this session ---
Warning in install.packages(update[instlib == l, "Package"], l, contriburl =
contriburl,  :
  'lib = "/usr/lib/R/site-library"' is not writable
Would you like to use a personal library instead?  (y/n) y
Would you like to create a personal library
NA
to install packages into?  (y/n) y
Error in install.packages(update[instlib == l, "Package"], l, contriburl =
contriburl,  :
  unable to create ‘NA’


For some reason, rather than creating the usual path (i.e.,
$HOME/R/$architecture/$Rversion), the path it looks for is NA.



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

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

Versions of packages r-base depends on:
ii  r-base-core3.4.1-1
ii  r-recommended  3.4.1-1

Versions of packages r-base recommends:
ii  r-base-html  3.4.1-1
ii  r-doc-html   3.4.1-1

Versions of packages r-base suggests:
ii  ess 16.10-1
pn  r-doc-info | r-doc-pdf  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: r-base
Source-Version: 3.4.1-2

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

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

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

Debian distribution maintenance software
pp.
Dirk Eddelbuettel  (supplier of updated r-base 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: Fri, 07 Jul 2017 13:05:03 -0500
Source: r-base
Binary: r-base r-base-core r-base-dev r-mathlib r-base-html r-doc-pdf 
r-doc-html r-doc-info r-recommended r-base-core-dbg
Architecture: source amd64 all
Version: 3.4.1-2
Distribution: unstable
Urgency: medium
Maintainer: Dirk Eddelbuettel 
Changed-By: Dirk Eddelbuettel 
Description:
 r-base - GNU R statistical computation and graphics system
 r-base-core - GNU R core of statistical computation and graphics system
 r-base-core-dbg - GNU R debug symbols for statistical comp. language and 
environmen
 r-base-dev - GNU R installation of auxiliary GNU R packages
 r-base-html - GNU R html docs for statistical computing system functions
 r-doc-html - GNU R html manuals for statistical computing system
 r-doc-info - GNU R info manuals statistical computing system
 r-doc-pdf  - GNU R pdf manuals for statistical computing system
 r-mathlib  - GNU R standalone mathematics library
 r-recommended - GNU R collection of recommended packages [metapackage]
Closes: 866768
Changes:
 r-base (3.4.1-2) unstable; urgency=medium
 .
   * etc/Renviron.in: No longer unset R_LIBS_USER   (Closes: #866768)
Checksums-Sha1:
 0a19bae3109bc907bfe0a20f1710f57b1b5ee9ac 2832 r-base_3.4.1-2.dsc
 44bb0cef6efd08939f3ec3c19bed0c3633b9d439 86404 r-base_3.4.1-2.debian.tar.xz
 601c508eae046a184838c1e7aa927fe9c4b2d485 3352414 
r-base-core-dbg_3.4.1-2_amd64.deb
 

Bug#867491: marked as done (python-sfml: FTBFS with Sphinx 1.5: more than one target found for cross-reference u'string')

[Debian Bug Tracking System]

Your message dated Fri, 07 Jul 2017 18:04:15 +
with message-id 
and subject line Bug#867491: fixed in python-sfml 2.2~git20150611.196c88+dfsg-4
has caused the Debian Bug report #867491,
regarding python-sfml: FTBFS with Sphinx 1.5: more than one target found for 
cross-reference u'string'
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.)


-- 
867491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867491
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-sfml
Version: 2.2~git20150611.196c88+dfsg-3
Severity: important
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx1.5

Dear maintainer,

I am about to upload Sphinx 1.5 to unstable (it has been available in
experimental for several months now).

Your package fails to build with it:

  Warning, treated as error:
  
/<>/python-sfml-2.2~git20150611.196c88+dfsg/doc/source/api/audio.rst:145:
  WARNING: more than one target found for cross-reference u'string':
  sfml.graphics.Text.string, sfml.network.IpAddress.string

  Makefile:40: recipe for target 'html' failed

The full build log can be found at:
https://launchpad.net/ubuntu/+source/python-sfml/2.2~git20150611.196c88+dfsg-3build2/+build/12578767

The attached patch from Graham Inggs, originally from Ubuntu, fixes this
failure.

--
Dmitry Shachnev
Description: Fix Sphinx rtype
 Fixes FTBFS with recent versions of Sphinx which treat the following
 warning as an error: "more than one target found for cross-reference
 u'string': sfml.graphics.Text.string, sfml.network.IpAddress.string".
Forwarded: no
Author: Graham Inggs 
Last-Update: 2017-05-29
--- a/doc/source/api/audio.rst
+++ b/doc/source/api/audio.rst
@@ -142,7 +142,7 @@
   will be converted internally in an array of **Int16**) and its
   lenght must be an even number.
 
-  :rtype: bytes or string
+  :rtype: bytes or str
 
 SoundBuffer
 ^^^
@@ -872,7 +872,7 @@
   none is available, None is returned.
 
   :return: The name of the default audio capture device
-  :rtype: string (or None)
+  :rtype: str (or None)
 
.. method:: set_device(name)
 
--- a/doc/source/api/graphics.rst
+++ b/doc/source/api/graphics.rst
@@ -2142,7 +2142,7 @@
 
   Set/get the text's string.
 
-  :rtype: bytes or string
+  :rtype: bytes or str
 
.. py:attribute:: font
 
--- a/doc/source/api/window.rst
+++ b/doc/source/api/window.rst
@@ -448,7 +448,7 @@
 
 		Return a copy of the data inside.
 
-		:rtype: bytes or string
+		:rtype: bytes or str
 
 
 Window


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: python-sfml
Source-Version: 2.2~git20150611.196c88+dfsg-4

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

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

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

Debian distribution maintenance software
pp.
James Cowgill  (supplier of updated python-sfml 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: Fri, 07 Jul 2017 18:46:47 +0100
Source: python-sfml
Binary: python-sfml python-sfml-dbg python3-sfml python3-sfml-dbg 
python-sfml-doc
Architecture: source
Version: 2.2~git20150611.196c88+dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: James Cowgill 
Description:
 python-sfml - Simple and Fast Multimedia Library - Python 2 Bindings
 python-sfml-dbg - Simple and Fast Multimedia Library - Python 2 Debug Bindings
 python-sfml-doc - Simple and Fast Multimedia Library - Documentation
 python3-sfml - Simple and Fast Multimedia Library - Python 3 Bindings
 python3-sfml-dbg - Simple and Fast Multimedia Library - Python 3 Debug Bindings
Closes: 867491
Changes:
 python-sfml (2.2~git20150611.196c88+dfsg-4) unstable; urgency=medium
 .
   [ Graham Inggs ]
   * debian/patches/06_fix-sphinx-rtype.patch:
 - Fix FTBFS with Sphinx 1.5. (Closes: #867491)
 .
   [ James Cowgill ]
   * debian/control:
 - Bump standards to 4.0.0 (no changes 

Bug#866662: marked as done (golang-gopkg-mcuadros-go-syslog.v2 FTBFS: FAIL: rfc6587_test.go:48: FormatSuite.TestRFC6587_GetSplitBadSplit)

[Debian Bug Tracking System]

Your message dated Fri, 07 Jul 2017 18:03:49 +
with message-id 
and subject line Bug#82: fixed in golang-gopkg-mcuadros-go-syslog.v2 2.2.1-1
has caused the Debian Bug report #82,
regarding golang-gopkg-mcuadros-go-syslog.v2 FTBFS: FAIL: rfc6587_test.go:48: 
FormatSuite.TestRFC6587_GetSplitBadSplit
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.)


-- 
82: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=82
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-gopkg-mcuadros-go-syslog.v2
Version: 2.1.1-1
Severity: serious

Some recent change in unstable makes golang-gopkg-mcuadros-go-syslog.v2 FTBFS:

https://tests.reproducible-builds.org/debian/history/golang-gopkg-mcuadros-go-syslog.v2.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-gopkg-mcuadros-go-syslog.v2.html

...
   dh_auto_test -O--buildsystem=golang
go test -v -p 1 gopkg.in/mcuadros/go-syslog.v2 
gopkg.in/mcuadros/go-syslog.v2/format
=== RUN   Test
OK: 12 passed
--- PASS: Test (0.41s)
PASS
ok  gopkg.in/mcuadros/go-syslog.v2  0.423s
=== RUN   Test

--
FAIL: rfc6587_test.go:48: FormatSuite.TestRFC6587_GetSplitBadSplit

rfc6587_test.go:64:
c.Assert(err, ErrorMatches, "strconv.ParseInt: parsing \".2\": invalid 
syntax")
... error string = "strconv.Atoi: parsing \".2\": invalid syntax"
... regex string = "strconv.ParseInt: parsing \".2\": invalid syntax"

OOPS: 4 passed, 1 FAILED
--- FAIL: Test (0.00s)
FAIL
exit status 1
FAILgopkg.in/mcuadros/go-syslog.v2/format   0.010s
dh_auto_test: go test -v -p 1 gopkg.in/mcuadros/go-syslog.v2 
gopkg.in/mcuadros/go-syslog.v2/format returned exit code 1
debian/rules:6: recipe for target 'build' failed
make: *** [build] Error 1
--- End Message ---
--- Begin Message ---
Source: golang-gopkg-mcuadros-go-syslog.v2
Source-Version: 2.2.1-1

We believe that the bug you reported is fixed in the latest version of
golang-gopkg-mcuadros-go-syslog.v2, which is due to be installed in the Debian 
FTP archive.

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

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

Debian distribution maintenance software
pp.
Dr. Tobias Quathamer  (supplier of updated 
golang-gopkg-mcuadros-go-syslog.v2 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: Fri, 07 Jul 2017 19:48:16 +0200
Source: golang-gopkg-mcuadros-go-syslog.v2
Binary: golang-gopkg-mcuadros-go-syslog.v2-dev
Architecture: source
Version: 2.2.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Dr. Tobias Quathamer 
Description:
 golang-gopkg-mcuadros-go-syslog.v2-dev - syslog server library for Golang
Closes: 82
Changes:
 golang-gopkg-mcuadros-go-syslog.v2 (2.2.1-1) unstable; urgency=medium
 .
   [ Paul Tagliamonte ]
   * Team upload.
   * Use a secure transport for the Vcs-Git and Vcs-Browser URL
 .
   [ Dr. Tobias Quathamer ]
   * New upstream version 2.2.1
   * Use debhelper v10
   * Update to Standards-Version 4.0.0
 - Use HTTPS URL for d/copyright
   * Use golang-any
   * Update expected error string to fix FTBFS. (Closes: #82)
Checksums-Sha1:
 b66fdb4edbdbb471f97306adeeda4bcc0b85871d 2384 
golang-gopkg-mcuadros-go-syslog.v2_2.2.1-1.dsc
 d37dd8a1eb94f5d9202752144d7ee2a8fe2ddeaa 23368 
golang-gopkg-mcuadros-go-syslog.v2_2.2.1.orig.tar.xz
 7be6894127dd56a06bf83d9698a9c4ea85cb3a34 2488 
golang-gopkg-mcuadros-go-syslog.v2_2.2.1-1.debian.tar.xz
 64ee091ef3990dfec039610fb4d5df3394ba6258 5675 
golang-gopkg-mcuadros-go-syslog.v2_2.2.1-1_amd64.buildinfo
Checksums-Sha256:
 329c4d98b3527665c891b01401174929c4e33d942dd304b1bb34c430d5667085 2384 
golang-gopkg-mcuadros-go-syslog.v2_2.2.1-1.dsc
 b0fbce57cf820fbed645884656dab836f422105d464164f4535d7e6e007271bd 23368 
golang-gopkg-mcuadros-go-syslog.v2_2.2.1.orig.tar.xz
 6540c64a2424443d6332daac27bcdb73ddb5a1aa2caf9d73345e5a0a25c54e1f 2488 
golang-gopkg-mcuadros-go-syslog.v2_2.2.1-1.debian.tar.xz
 30792651fa5d20a71aa699d4c3bfa49845f5cd645ed830672457f1b14920a56f 5675 

Bug#866621: marked as done (sylpheed: 3.6.0 has been released)

[Debian Bug Tracking System]

Your message dated Fri, 07 Jul 2017 17:51:59 +
with message-id 
and subject line Bug#866621: fixed in sylpheed 3.6.0-1
has caused the Debian Bug report #866621,
regarding sylpheed: 3.6.0 has been released
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.)


-- 
866621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866621
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sylpheed
Version: 3.6.0~beta1-1
Severity: wishlist

Dear Maintainer,

sylpheed 3.6.0 has been released.

  http://sylpheed.sraoss.jp/sylpheed/v3.6/sylpheed-3.6.0.tar.gz

So, please update to it. (There is no functionally changes, but it is better to
use official one)

I've uploaded .dsc for it.

  https://mentors.debian.net/debian/pool/main/s/sylpheed/sylpheed_3.6.0-1.dsc

Could you review it?


pgpKIfOr9XG2C.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: sylpheed
Source-Version: 3.6.0-1

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

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

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

Debian distribution maintenance software
pp.
Ricardo Mones  (supplier of updated sylpheed 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: Fri, 07 Jul 2017 19:31:17 +0200
Source: sylpheed
Binary: sylpheed sylpheed-i18n sylpheed-plugins
Architecture: source amd64 all
Version: 3.6.0-1
Distribution: unstable
Urgency: medium
Maintainer: Ricardo Mones 
Changed-By: Ricardo Mones 
Description:
 sylpheed   - Light weight e-mail client with GTK+
 sylpheed-i18n - Locale data for Sylpheed (i18n support)
 sylpheed-plugins - Loadable modules for extending Sylpheed features
Closes: 754353 866621
Changes:
 sylpheed (3.6.0-1) unstable; urgency=medium
 .
   [ Kentaro Hayashi ]
   * New upstream release
 .
   [ Ricardo Mones ]
   * Team upload (Closes: #866621)
   * debian/control
   - Update Kentaro's address to avoid NMU warnings from lintian
   * debian/control, debian/rules
   - Disable JPilot: its library source package has not been updated
 since 2015 and upstream sites have vanished (Closes: #754353)
Checksums-Sha1:
 2599dafdac2bd5b95307f6864acb7f72a8b7c6bb 2300 sylpheed_3.6.0-1.dsc
 71756e77e080871a5e600dea9ca26c676070f3d3 2627112 sylpheed_3.6.0.orig.tar.xz
 7f166013f10d61425d41f36f5eed13413ab0c4b3 29424 sylpheed_3.6.0-1.debian.tar.xz
 29efe8818e14dab222f1fdb21aea5ecfcb5fd7f6 2702850 
sylpheed-dbgsym_3.6.0-1_amd64.deb
 e7575416040478b1a332ba3d1c63fcb50ec78d0e 817888 sylpheed-i18n_3.6.0-1_all.deb
 8e8b7684ef72f3fa76030f3fdd1ea584dd588746 20110 
sylpheed-plugins-dbgsym_3.6.0-1_amd64.deb
 1c79ff5472a4cbe130ee6ed84b62d62a08945f6b 93388 
sylpheed-plugins_3.6.0-1_amd64.deb
 c86e3282be67031338601205f1386c7d7e0cae10 12246 sylpheed_3.6.0-1_amd64.buildinfo
 e9c5248e51f081e0261b52a6b399baa32f317254 832836 sylpheed_3.6.0-1_amd64.deb
Checksums-Sha256:
 c201f9f4e7649fa41e0311ae2588fdf2652b4c2849811420dc20fcbd720b5c6c 2300 
sylpheed_3.6.0-1.dsc
 fa696c19fdcfabc7d95640ef9d1569df083a0e29ae58e3bca0cc0e7425012291 2627112 
sylpheed_3.6.0.orig.tar.xz
 52cade4953993390f8f1f641f3c3e9b99f2f17ca75bdda2fae5482f1fc6790cb 29424 
sylpheed_3.6.0-1.debian.tar.xz
 4e2077299ef0d43d3c1bddf78fd57004191212f44763dafd9f6ff651643973d8 2702850 
sylpheed-dbgsym_3.6.0-1_amd64.deb
 8c321c1062a2b893fd2a8f3b47b9ed29ed6e11bcea83e31c52c4e743dc67c607 817888 
sylpheed-i18n_3.6.0-1_all.deb
 9819a48fd967df002f80dc67dc02260825db2cd9625c4082fa39d1e932a48869 20110 
sylpheed-plugins-dbgsym_3.6.0-1_amd64.deb
 87ba6d324861cbc36f22bf9a0414b0fa8bb66f6a86ebc141296a093872aa36a1 93388 
sylpheed-plugins_3.6.0-1_amd64.deb
 a01141fcd1c7ef3fe1ec80705f770a7d641fe73d338904c014dfc642ed9b0b23 12246 
sylpheed_3.6.0-1_amd64.buildinfo
 61ac11c76728d993b89dd813640bafd3c09f2d631218b95d83fd391b79951758 832836 
sylpheed_3.6.0-1_amd64.deb
Files:
 562911007321473192183abed7470b3a 2300 mail optional sylpheed_3.6.0-1.dsc
 63acd4892a396a3cc24a30cd108053d2 2627112 mail optional 
sylpheed_3.6.0.orig.tar.xz
 3ab6a0a2777e95e773341887f36fe4ce 29424 mail optional 

Bug#754353: marked as done (Sylpheed dependencies)

[Debian Bug Tracking System]

Your message dated Fri, 07 Jul 2017 17:51:59 +
with message-id 
and subject line Bug#754353: fixed in sylpheed 3.6.0-1
has caused the Debian Bug report #754353,
regarding Sylpheed dependencies
to be marked as done.

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

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


-- 
754353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754353
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sylpheed
Version: 3.2.0-1

The package Sylpheed has insane dependencies, such as libpisock9 ->
libbluetooth3.

Sylphed is supposed to be a "Light weight e-mail client". Why does a
lightweight email client need integration with some PalmOS PDA device,
that nobody is using anyway? There are many over-bloated email clients,
such as Evolution. If anybody needs to integrate his own life inside an
email client, he can use such products.

I suggest that Sylpheed package gets rid of irrelevant dependencies, and
returns to being lightweight.

thanks,
Martin
--- End Message ---
--- Begin Message ---
Source: sylpheed
Source-Version: 3.6.0-1

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

Debian distribution maintenance software
pp.
Ricardo Mones  (supplier of updated sylpheed 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: Fri, 07 Jul 2017 19:31:17 +0200
Source: sylpheed
Binary: sylpheed sylpheed-i18n sylpheed-plugins
Architecture: source amd64 all
Version: 3.6.0-1
Distribution: unstable
Urgency: medium
Maintainer: Ricardo Mones 
Changed-By: Ricardo Mones 
Description:
 sylpheed   - Light weight e-mail client with GTK+
 sylpheed-i18n - Locale data for Sylpheed (i18n support)
 sylpheed-plugins - Loadable modules for extending Sylpheed features
Closes: 754353 866621
Changes:
 sylpheed (3.6.0-1) unstable; urgency=medium
 .
   [ Kentaro Hayashi ]
   * New upstream release
 .
   [ Ricardo Mones ]
   * Team upload (Closes: #866621)
   * debian/control
   - Update Kentaro's address to avoid NMU warnings from lintian
   * debian/control, debian/rules
   - Disable JPilot: its library source package has not been updated
 since 2015 and upstream sites have vanished (Closes: #754353)
Checksums-Sha1:
 2599dafdac2bd5b95307f6864acb7f72a8b7c6bb 2300 sylpheed_3.6.0-1.dsc
 71756e77e080871a5e600dea9ca26c676070f3d3 2627112 sylpheed_3.6.0.orig.tar.xz
 7f166013f10d61425d41f36f5eed13413ab0c4b3 29424 sylpheed_3.6.0-1.debian.tar.xz
 29efe8818e14dab222f1fdb21aea5ecfcb5fd7f6 2702850 
sylpheed-dbgsym_3.6.0-1_amd64.deb
 e7575416040478b1a332ba3d1c63fcb50ec78d0e 817888 sylpheed-i18n_3.6.0-1_all.deb
 8e8b7684ef72f3fa76030f3fdd1ea584dd588746 20110 
sylpheed-plugins-dbgsym_3.6.0-1_amd64.deb
 1c79ff5472a4cbe130ee6ed84b62d62a08945f6b 93388 
sylpheed-plugins_3.6.0-1_amd64.deb
 c86e3282be67031338601205f1386c7d7e0cae10 12246 sylpheed_3.6.0-1_amd64.buildinfo
 e9c5248e51f081e0261b52a6b399baa32f317254 832836 sylpheed_3.6.0-1_amd64.deb
Checksums-Sha256:
 c201f9f4e7649fa41e0311ae2588fdf2652b4c2849811420dc20fcbd720b5c6c 2300 
sylpheed_3.6.0-1.dsc
 fa696c19fdcfabc7d95640ef9d1569df083a0e29ae58e3bca0cc0e7425012291 2627112 
sylpheed_3.6.0.orig.tar.xz
 52cade4953993390f8f1f641f3c3e9b99f2f17ca75bdda2fae5482f1fc6790cb 29424 
sylpheed_3.6.0-1.debian.tar.xz
 4e2077299ef0d43d3c1bddf78fd57004191212f44763dafd9f6ff651643973d8 2702850 
sylpheed-dbgsym_3.6.0-1_amd64.deb
 8c321c1062a2b893fd2a8f3b47b9ed29ed6e11bcea83e31c52c4e743dc67c607 817888 
sylpheed-i18n_3.6.0-1_all.deb
 9819a48fd967df002f80dc67dc02260825db2cd9625c4082fa39d1e932a48869 20110 
sylpheed-plugins-dbgsym_3.6.0-1_amd64.deb
 87ba6d324861cbc36f22bf9a0414b0fa8bb66f6a86ebc141296a093872aa36a1 93388 
sylpheed-plugins_3.6.0-1_amd64.deb
 a01141fcd1c7ef3fe1ec80705f770a7d641fe73d338904c014dfc642ed9b0b23 12246 
sylpheed_3.6.0-1_amd64.buildinfo
 61ac11c76728d993b89dd813640bafd3c09f2d631218b95d83fd391b79951758 832836 
sylpheed_3.6.0-1_amd64.deb
Files:
 562911007321473192183abed7470b3a 2300 mail optional sylpheed_3.6.0-1.dsc
 63acd4892a396a3cc24a30cd108053d2 2627112 

Bug#867581: marked as done (libgnutls30: AES256-GCM emits all-zeros ciphertext on aarch64 with hardware acceleration (upstream bug report))

[Debian Bug Tracking System]

Your message dated Fri, 7 Jul 2017 19:22:50 +0200
with message-id <20170707172250.syainpyqkttzh...@argenau.bebt.de>
and subject line Re: Bug#867581: libgnutls30: AES256-GCM emits all-zeros 
ciphertext on aarch64 with hardware acceleration (upstream bug report)
has caused the Debian Bug report #867581,
regarding libgnutls30: AES256-GCM emits all-zeros ciphertext on aarch64 with 
hardware acceleration (upstream bug report)
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.)


-- 
867581: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867581
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgnutls30
Version: 3.5.8-5+deb9u1
Severity: critical
Tags: patch
Justification: breaks unrelated software

Dear Maintainer,

   * What led up to the situation?

Unrelated gnome-terminal or xfce4-terminal crashing when significant output
(e.g. running 'yes'; apparently because of the corruption of the encrypted
scrollback buffer).

Issue noticed on a Cavium ThunderX running Debian Stretch.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Patching libgnutls with
https://gitlab.com/gnutls/gnutls/commit/228b18dfbf934d8924d3305dc24d7b0162352eba
fixes the issue.

This fix is available in gnutls 3.5.13 (and testing+unstable) but not in 3.5.8
(stable). Please back-port the above patch to stable.

Upstream bug report: https://gitlab.com/gnutls/gnutls/issues/204

I marked it as 'critical' because it breaks unrelated packages, though I'm not
sure that's the appropriate severity level.

Thanks.



-- System Information:
Debian Release: 9.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: arm64 (aarch64)

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

Versions of packages libgnutls30 depends on:
ii  libc62.24-11+deb9u1
ii  libgmp10 2:6.1.2+dfsg-1
ii  libhogweed4  3.3-1+b1
ii  libidn11 1.33-1
ii  libnettle6   3.3-1+b1
ii  libp11-kit0  0.23.3-2
ii  libtasn1-6   4.10-1.1
ii  zlib1g   1:1.2.8.dfsg-5

libgnutls30 recommends no packages.

Versions of packages libgnutls30 suggests:
pn  gnutls-bin  
diff --git a/lib/accelerated/aarch64/aes-gcm-aarch64.c 
b/lib/accelerated/aarch64/aes-gcm-aarch64.c
index c571d02..8d2bc1d 100644
--- a/lib/accelerated/aarch64/aes-gcm-aarch64.c
+++ b/lib/accelerated/aarch64/aes-gcm-aarch64.c
@@ -153,6 +153,27 @@ gcm_ghash(struct aes_gcm_ctx *ctx, const uint8_t * src, 
size_t src_size)
 }
 
 static void
+ctr32_encrypt_blocks_inplace(const unsigned char *in, unsigned char *out,
+size_t blocks, const AES_KEY *key,
+const unsigned char ivec[16])
+{
+   unsigned i;
+   uint8_t ctr[16];
+   uint8_t tmp[16];
+
+   memcpy(ctr, ivec, 16);
+
+   for (i=0;i

Bug#867264: marked as done (RM: python-3to2 -- ROM; FTBFS)

[Debian Bug Tracking System]

Your message dated Fri, 07 Jul 2017 17:19:28 +
with message-id 
and subject line Bug#867264: Removed package(s) from unstable
has caused the Debian Bug report #867264,
regarding RM: python-3to2 -- ROM; FTBFS
to be marked as done.

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

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


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


Python 3to2 is broken since too much time, I don't know how to fix it to work
with new Python3 package, and upstream seems mostly dead.

Please let it go

G.
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

python-3to2 |1.1.1-1 | source, all
python3-3to2 |1.1.1-1 | all

--- Reason ---
ROM; FTBFS
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 867...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/867264

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#838974: marked as done (python-3to2: FTBFS: AssertionError: 'print(*args)\n\n' != 'print *args\n\n')

[Debian Bug Tracking System]

Your message dated Fri, 07 Jul 2017 17:19:31 +
with message-id 
and subject line Bug#867264: Removed package(s) from unstable
has caused the Debian Bug report #838974,
regarding python-3to2: FTBFS: AssertionError: 'print(*args)\n\n' != 'print 
*args\n\n'
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.)


-- 
838974: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838974
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-3to2
Version: 1.1.1-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

python-3to2 fails to build from source in unstable/amd64:

  [..]

  test_usage (lib3to2.tests.test_imports.Test_imports) ... ok
  test_various_unchanged (lib3to2.tests.test_imports.Test_imports) ... ok
  test_from_import (lib3to2.tests.test_unittest.Test_unittest) ... ok
  test_imported (lib3to2.tests.test_unittest.Test_unittest) ... ok
  test_imported_from (lib3to2.tests.test_unittest.Test_unittest) ... ok
  test_not_base (lib3to2.tests.test_unittest.Test_unittest) ... ok
  test_used (lib3to2.tests.test_unittest.Test_unittest) ... ok
  test_assignment (lib3to2.tests.test_unpacking.Test_unpacking) ... ok
  test_forloop (lib3to2.tests.test_unpacking.Test_unpacking) ... ok
  test_unchanged (lib3to2.tests.test_unpacking.Test_unpacking) ... ok
  test_comments (lib3to2.tests.test_metaclass.Test_metaclass) ... ok
  test_meta_expression_simple_body_1 
(lib3to2.tests.test_metaclass.Test_metaclass) ... ok
  test_meta_expression_simple_body_2 
(lib3to2.tests.test_metaclass.Test_metaclass) ... ok
  test_meta_multiparent_simple_body_1 
(lib3to2.tests.test_metaclass.Test_metaclass) ... ok
  test_meta_multiparent_simple_body_2 
(lib3to2.tests.test_metaclass.Test_metaclass) ... ok
  test_meta_noparent_odd_body (lib3to2.tests.test_metaclass.Test_metaclass) ... 
ok
  test_meta_noparent_simple_body (lib3to2.tests.test_metaclass.Test_metaclass) 
... ok
  test_meta_oneparent_no_body (lib3to2.tests.test_metaclass.Test_metaclass) ... 
ok
  test_meta_oneparent_simple_body_1 
(lib3to2.tests.test_metaclass.Test_metaclass) ... ok
  test_meta_oneparent_simple_body_2 
(lib3to2.tests.test_metaclass.Test_metaclass) ... ok
  test_meta_oneparent_simple_body_3 
(lib3to2.tests.test_metaclass.Test_metaclass) ... ok
  test_unchanged (lib3to2.tests.test_metaclass.Test_metaclass) ... ok
  test_import (lib3to2.tests.test_fullargspec.Test_fullargspec) ... ok
  test_usage (lib3to2.tests.test_fullargspec.Test_fullargspec) ... ok
  test_doesnt_import (lib3to2.tests.test_open.Test_open) ... ok
  test_imports (lib3to2.tests.test_open.Test_open) ... ok
  test (lib3to2.tests.test_intern.Test_intern) ... ok
  test_multimports (lib3to2.tests.test_intern.Test_intern) ... ok
  test_prefix_preservation (lib3to2.tests.test_intern.Test_intern) ... ok
  test_unchanged (lib3to2.tests.test_intern.Test_intern) ... ok
  test_complex_set_comprehension 
(lib3to2.tests.test_setliteral.Test_setliteral) ... ok
  test_multiple_items (lib3to2.tests.test_setliteral.Test_setliteral) ... ok
  test_simple_literal (lib3to2.tests.test_setliteral.Test_setliteral) ... ok
  test_simple_set_comprehension (lib3to2.tests.test_setliteral.Test_setliteral) 
... ok
  test_unchanged_dict (lib3to2.tests.test_setliteral.Test_setliteral) ... ok
  test_prefix_preservation (lib3to2.tests.test_getcwd.Test_getcwd) ... ok
  test_arbitrary_printing (lib3to2.tests.test_print.Test_print) ... ok
  test_argument_unpacking (lib3to2.tests.test_print.Test_print) ... ok
  test_generic (lib3to2.tests.test_print.Test_print) ... ok
  test_literal (lib3to2.tests.test_print.Test_print) ... ok
  test_long_arglist (lib3to2.tests.test_print.Test_print) ... ok
  test_nones (lib3to2.tests.test_print.Test_print) ... ok
  test_not_builtin_unchanged (lib3to2.tests.test_print.Test_print) ... ok
  test_arbitrary_printing (lib3to2.tests.test_printfunction.Test_printfunction) 
... ok
  test_generic (lib3to2.tests.test_printfunction.Test_printfunction) ... ok
  test_literal (lib3to2.tests.test_printfunction.Test_printfunction) ... ok
  test_long_arglist (lib3to2.tests.test_printfunction.Test_printfunction) ... ok
  test_not_builtin_unchanged 
(lib3to2.tests.test_printfunction.Test_printfunction) ... ok
  test_import (lib3to2.tests.test_absimport.Test_absimport) ... ok
  test_no_imports (lib3to2.tests.test_absimport.Test_absimport) ... ok
  
  --
  

Bug#852393: marked as done (Updating the libplist Uploaders list)

[Debian Bug Tracking System]

Your message dated Fri, 7 Jul 2017 20:10:18 +0300
with message-id <20170707171017.ccmxkb3qe4oyvbbx@localhost>
and subject line libplist has been orphaned
has caused the Debian Bug report #852393,
regarding Updating the libplist Uploaders list
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.)


-- 
852393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852393
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libplist
Version: 1.11-3 1.12-3.1
Severity: minor
User: m...@qa.debian.org
Usertags: mia-teammaint

Julien Lavergne  wishes no longer to be uploader of 
libplist.

We are tracking their status in the MIA team and would like to ask you
to remove them from the Uploaders list of the package so we can close
that part of the file.

(If the person is listed as Maintainer, what we are asking is to please
step in as a new maintainer.)

Thanks.
--- End Message ---
--- Begin Message ---
libplist has been orphaned and the maintainer set to Debian QA Group.

cu
Adrian

-- 

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

Bug#856226: marked as done (libplist: Intent to NMU 1.12+git+1+e37ca00-0.1)

[Debian Bug Tracking System]

Your message dated Fri, 7 Jul 2017 20:11:09 +0300
with message-id <20170707171109.gf4mdrqsb4tjpjc7@localhost>
and subject line Thanks for the NMU
has caused the Debian Bug report #856226,
regarding libplist: Intent to NMU 1.12+git+1+e37ca00-0.1
to be marked as done.

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

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


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

Dear Maintainer,

I have NMU'd 1.12+git+1+e37ca00-0.1 (based upon upstream commit
e37ca0090343e0dae97e967d467bab56d502c37a) to DELAYED/15.

This fixes several security issues:

- CVE-2017-5834, CVE-2017-5835, CVE-2017-5836 (Closes: #854000)
- CVE-2017-5209 (Closes: #851196)
- CVE-2017-5545 (Closes: #852385)

Two symbols are added to libplist3 (but none removed), so this should
not cause any ABI incompatibilities.

Please feel free to reschedule or cancel as you see fit.

Cheers,
-Hilko
--- End Message ---
--- Begin Message ---
Thanks for the NMU, it is included in the latest QA upload
of the now-orphaned package.

cu
Adrian

-- 

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

Bug#865664: marked as done (golang-github-microcosm-cc-bluemonday FTBFS: dh_auto_test fails)

[Debian Bug Tracking System]

Your message dated Fri, 07 Jul 2017 17:04:32 +
with message-id 
and subject line Bug#865664: fixed in golang-github-microcosm-cc-bluemonday 
0.0~git20161202.0.e797637-1
has caused the Debian Bug report #865664,
regarding golang-github-microcosm-cc-bluemonday FTBFS: dh_auto_test fails
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.)


-- 
865664: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865664
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-microcosm-cc-bluemonday
Version: 0.0~git20161012.0.f77f16f-1
Severity: serious
Tags: buster sid

Some recent change in unstable makes golang-github-microcosm-cc-bluemonday 
FTBFS:

https://tests.reproducible-builds.org/debian/history/golang-github-microcosm-cc-bluemonday.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/golang-github-microcosm-cc-bluemonday.html

...
   dh_auto_test -O--buildsystem=golang
go test -v -p 1 github.com/microcosm-cc/bluemonday 
github.com/microcosm-cc/bluemonday/cmd/sanitise_html_email 
github.com/microcosm-cc/bluemonday/cmd/sanitise_ugc
=== RUN   TestRegexpVars
--- PASS: TestRegexpVars (0.00s)
=== RUN   TestAllowDataURIImages
--- PASS: TestAllowDataURIImages (0.00s)
=== RUN   TestStrictPolicy
--- PASS: TestStrictPolicy (0.00s)
=== RUN   TestUGCPolicy
--- PASS: TestUGCPolicy (0.00s)
=== RUN   TestAllowElementsContent
--- PASS: TestAllowElementsContent (0.00s)
=== RUN   TestEmpty
--- PASS: TestEmpty (0.00s)
=== RUN   TestSignatureBehaviour
--- PASS: TestSignatureBehaviour (0.00s)
=== RUN   TestAllowDocType
--- PASS: TestAllowDocType (0.00s)
=== RUN   TestLinks
--- PASS: TestLinks (0.00s)
=== RUN   TestLinkTargets
--- PASS: TestLinkTargets (0.00s)
=== RUN   TestStyling
--- PASS: TestStyling (0.01s)
=== RUN   TestEmptyAttributes
--- PASS: TestEmptyAttributes (0.00s)
=== RUN   TestDataUri
--- PASS: TestDataUri (0.00s)
=== RUN   TestAntiSamy
--- PASS: TestAntiSamy (0.00s)
=== RUN   TestXSS
--- FAIL: TestXSS (0.00s)
sanitize_test.go:1138: test 61 failed;
input   : 
output  : 
expected: 
sanitize_test.go:1138: test 74 failed;
input   : 
output  : 
expected: 
=== RUN   TestIssue3
--- PASS: TestIssue3 (0.00s)
=== RUN   TestIssue9
--- PASS: TestIssue9 (0.00s)
=== RUN   TestIssue18
--- PASS: TestIssue18 (0.00s)
=== RUN   TestIssue23
--- PASS: TestIssue23 (0.00s)
=== RUN   TestAllowNoAttrs
--- PASS: TestAllowNoAttrs (0.00s)
=== RUN   TestSkipElementsContent
--- PASS: TestSkipElementsContent (0.00s)
=== RUN   TestTagSkipClosingTagNested
--- PASS: TestTagSkipClosingTagNested (0.00s)
=== RUN   TestAddSpaces
--- PASS: TestAddSpaces (0.00s)
=== RUN   TestTargetBlankNoOpener
--- PASS: TestTargetBlankNoOpener (0.00s)
=== RUN   ExampleNewPolicy
--- PASS: ExampleNewPolicy (0.00s)
=== RUN   ExampleStrictPolicy
--- PASS: ExampleStrictPolicy (0.00s)
=== RUN   ExampleUGCPolicy
--- PASS: ExampleUGCPolicy (0.00s)
=== RUN   ExamplePolicy_Sanitize
--- PASS: ExamplePolicy_Sanitize (0.00s)
=== RUN   ExamplePolicy_SanitizeBytes
--- PASS: ExamplePolicy_SanitizeBytes (0.00s)
=== RUN   ExamplePolicy_SanitizeReader
--- PASS: ExamplePolicy_SanitizeReader (0.00s)
FAIL
exit status 1
FAILgithub.com/microcosm-cc/bluemonday  0.060s
?   github.com/microcosm-cc/bluemonday/cmd/sanitise_html_email  [no 
test files]
?   github.com/microcosm-cc/bluemonday/cmd/sanitise_ugc [no test files]
dh_auto_test: go test -v -p 1 github.com/microcosm-cc/bluemonday 
github.com/microcosm-cc/bluemonday/cmd/sanitise_html_email 
github.com/microcosm-cc/bluemonday/cmd/sanitise_ugc returned exit code 1
debian/rules:4: recipe for target 'build' failed
make: *** [build] Error 1
--- End Message ---
--- Begin Message ---
Source: golang-github-microcosm-cc-bluemonday
Source-Version: 0.0~git20161202.0.e797637-1

We believe that the bug you reported is fixed in the latest version of
golang-github-microcosm-cc-bluemonday, 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.
Dr. Tobias Quathamer  (supplier of updated 
golang-github-microcosm-cc-bluemonday package)

(This message was generated automatically at their request; if 

Bug#864643: marked as done (openjdk-9: Please update zero-sh.diff patch for sh4)

[Debian Bug Tracking System]

Your message dated Fri, 07 Jul 2017 16:20:39 +
with message-id 
and subject line Bug#864643: fixed in openjdk-9 9~b177-2
has caused the Debian Bug report #864643,
regarding openjdk-9: Please update zero-sh.diff patch for sh4
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.)


-- 
864643: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864643
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openjdk-9
Version: 9~b170-2
Severity: normal
Tags: patch
User: debian-sup...@lists.debian.org
Usertags: sh4

Hi!

openjdk-9 currently fails to build from source on sh4 with:

/<>/src/hotspot/src/os/linux/vm/os_linux.cpp: In static member 
function 'static void* os::dll_load(const char*, char*, int)':
/<>/src/hotspot/src/os/linux/vm/os_linux.cpp:1816:9: error: 
'running_arch_code' was not declared in this scope
 if (running_arch_code == arch_array[i].code) {
 ^
make[4]: *** 
[/<>/build/hotspot/variant-zero/libjvm/objs/os_linux.o] Error 1
lib/CompileJvm.gmk:212: recipe for target 
'/<>/build/hotspot/variant-zero/libjvm/objs/os_linux.o' failed

That's because the included patch zero-sh.diff is broken. I have fixed
the patch to address this issue. Please update the patch.

Thanks,
Adrian

 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
# DP: Add support for sh

Index: b/hotspot/src/os/linux/vm/os_linux.cpp
===
--- a/hotspot/src/os/linux/vm/os_linux.cpp
+++ b/hotspot/src/os/linux/vm/os_linux.cpp
@@ -1766,6 +1766,7 @@ void * os::dll_load(const char *filename
 {EM_PARISC,  EM_PARISC,  ELFCLASS32, ELFDATA2MSB, (char*)"PARISC"},
 {EM_68K, EM_68K, ELFCLASS32, ELFDATA2MSB, (char*)"M68k"},
 {EM_AARCH64, EM_AARCH64, ELFCLASS64, ELFDATA2LSB, (char*)"AARCH64"},
+{EM_SH,  EM_SH,  ELFCLASS32, ELFDATA2LSB, (char*)"Hitachi SH"}
   };
 
 #if  (defined IA32)
@@ -1798,9 +1799,11 @@ void * os::dll_load(const char *filename
   static  Elf32_Half running_arch_code=EM_MIPS;
 #elif  (defined M68K)
   static  Elf32_Half running_arch_code=EM_68K;
+#elif  (defined SH)
+  static  Elf32_Half running_arch_code=EM_SH;
 #else
 #error Method os::dll_load requires that one of following is defined:\
-AARCH64, ALPHA, ARM, AMD64, IA32, IA64, M68K, MIPS, MIPSEL, PARISC, 
__powerpc__, __powerpc64__, S390, __sparc
+AARCH64, ALPHA, ARM, AMD64, IA32, IA64, M68K, MIPS, MIPSEL, PARISC, 
__powerpc__, __powerpc64__, S390, SH, __sparc
 #endif
 
   // Identify compatability class for VM's architecture and library's 
architecture
--- End Message ---
--- Begin Message ---
Source: openjdk-9
Source-Version: 9~b177-2

We believe that the bug you reported is fixed in the latest version of
openjdk-9, 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.
Matthias Klose  (supplier of updated openjdk-9 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: Fri, 07 Jul 2017 12:28:53 +0200
Source: openjdk-9
Binary: openjdk-9-jdk-headless openjdk-9-jre-headless openjdk-9-jdk 
openjdk-9-jre openjdk-9-demo openjdk-9-source openjdk-9-doc openjdk-9-dbg 
openjdk-9-jre-zero
Architecture: source
Version: 9~b177-2
Distribution: unstable
Urgency: medium
Maintainer: OpenJDK Team 
Changed-By: Matthias Klose 
Description:
 openjdk-9-dbg - Java runtime based on OpenJDK (debugging symbols)
 openjdk-9-demo - Java runtime based on OpenJDK (demos and examples)
 openjdk-9-doc - OpenJDK Development Kit (JDK) documentation
 openjdk-9-jdk - OpenJDK Development Kit (JDK)
 openjdk-9-jdk-headless - OpenJDK Development Kit (JDK) (headless)
 openjdk-9-jre - OpenJDK Java runtime, using ${vm:Name}
 openjdk-9-jre-headless - OpenJDK Java runtime, using ${vm:Name} (headless)
 openjdk-9-jre-zero - Alternative JVM for OpenJDK, using 

Bug#864359: marked as done (openjdk-9: Please update and enable patch zero-sparc.diff)

[Debian Bug Tracking System]

Your message dated Fri, 07 Jul 2017 16:20:39 +
with message-id 
and subject line Bug#864359: fixed in openjdk-9 9~b177-2
has caused the Debian Bug report #864359,
regarding openjdk-9: Please update and enable patch zero-sparc.diff
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.)


-- 
864359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864359
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openjdk-9
Version: 9~b170-2
Severity: normal
Tags: patch
User: debian-sp...@lists.debian.org
Usertags: sparc64

Hi!

As promised in #864351 [1], I have updated the currently disabled patch
zero-sparc.diff for openjdk-9. Together with the changes from #864351,
openjdk-9 builds fine for me on sparc64 with the updated zero-sparc.diff
patch.

Thanks for consideration!

Adrian

> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864351

 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
--- a/hotspot/src/share/vm/gc/shared/memset_with_concurrent_readers.hpp 
2017-05-11 15:11:42.0 +0300
+++ b/hotspot/src/share/vm/gc/shared/memset_with_concurrent_readers.hpp 
2017-06-07 14:50:39.835143370 +0300
@@ -37,7 +37,7 @@
 // understanding that there may be concurrent readers of that memory.
 void memset_with_concurrent_readers(void* to, int value, size_t size);
 
-#ifdef SPARC
+#if defined(SPARC) && !defined(ZERO)
 
 // SPARC requires special handling.  See SPARC-specific definition.
 
--- a/hotspot/src/share/vm/compiler/oopMap.cpp~ 2017-05-11 15:11:42.0 
+0300
+++ b/hotspot/src/share/vm/compiler/oopMap.cpp  2017-06-07 15:21:34.723210971 
+0300
@@ -39,7 +39,7 @@
 #ifdef COMPILER2
 #include "opto/optoreg.hpp"
 #endif
-#ifdef SPARC
+#if defined (SPARC) && !defined(ZERO)
 #include "vmreg_sparc.inline.hpp"
 #endif
 
--- a/hotspot/src/os_cpu/linux_zero/vm/os_linux_zero.cpp~   2017-05-11 
15:11:42.0 +0300
+++ b/hotspot/src/os_cpu/linux_zero/vm/os_linux_zero.cpp2017-06-07 
15:41:01.847585726 +0300
@@ -86,7 +86,7 @@
   // Must never look like an address returned by reserve_memory,
   // even in its subfields (as defined by the CPU immediate fields,
   // if the CPU splits constants across multiple instructions).
-#ifdef SPARC
+#if defined(SPARC) && !defined(ZERO)
   // On SPARC, 0 != %hi(any real address), because there is no
   // allocation in the first 1Kb of the virtual address space.
   return (char *) 0;
--- a/hotspot/src/share/vm/opto/output.cpp~ 2017-05-11 15:11:42.0 
+0300
+++ b/hotspot/src/share/vm/opto/output.cpp  2017-06-07 15:42:35.147461407 
+0300
@@ -588,7 +588,7 @@
   array->append(new_loc_value( _regalloc, regnum, Location::lng ));
 }
 #else //_LP64
-#ifdef SPARC
+#if defined (SPARC) && !defined(ZERO)
 if (t->base() == Type::Long && OptoReg::is_reg(regnum)) {
   // For SPARC we have to swap high and low words for
   // long values stored in a single-register (g0-g7).
--- a/hotspot/src/share/vm/opto/chaitin.cpp~2017-06-07 15:43:34.357918591 
+0300
+++ b/hotspot/src/share/vm/opto/chaitin.cpp 2017-06-07 15:45:09.097846755 
+0300
@@ -878,7 +878,7 @@
 case Op_RegD:
   lrg.set_num_regs(2);
   // Define platform specific register pressure
-#if defined(SPARC) || defined(ARM32)
+#if (defined(SPARC) && !defined(ZERO)) || defined(ARM32)
   lrg.set_reg_pressure(2);
 #elif defined(IA32)
   if( ireg == Op_RegL ) {
@@ -905,7 +905,7 @@
 case Op_RegFlags:
 case 0: // not an ideal register
   lrg.set_num_regs(1);
-#ifdef SPARC
+#if defined(SPARC) && !defined(ZERO)
   lrg.set_reg_pressure(2);
 #else
   lrg.set_reg_pressure(1);
@@ -1526,7 +1526,7 @@
 
 // Check if a color is available and if so pick the color
 OptoReg::Name reg = choose_color( *lrg, chunk );
-#ifdef SPARC
+#if defined(SPARC) && !defined(ZERO)
 debug_only(lrg->compute_set_mask_size());
 assert(lrg->num_regs() < 2 || lrg->is_bound() || is_even(reg-1), "allocate 
all doubles aligned");
 #endif
--- a/hotspot/src/share/vm/runtime/deoptimization.cpp~  2017-05-11 
15:11:42.0 +0300
+++ b/hotspot/src/share/vm/runtime/deoptimization.cpp   2017-06-07 
15:47:36.275942531 +0300
@@ -861,7 +861,7 @@
 #ifdef _LP64
   jlong res = (jlong)low->get_int();
 #else
-#ifdef SPARC
+#if defined(SPARC) && !defined(ZERO)
   // For SPARC we have to swap high and low words.

Bug#864595: marked as done (openjdk-9: Please update the patch for m68k support)

[Debian Bug Tracking System]

Your message dated Fri, 07 Jul 2017 16:20:39 +
with message-id 
and subject line Bug#864595: fixed in openjdk-9 9~b177-2
has caused the Debian Bug report #864595,
regarding openjdk-9: Please update the patch for m68k support
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.)


-- 
864595: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864595
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openjdk-9
Version: 9~b170-2
Severity: normal
Tags: patch
User: debian-...@lists.debian.org
Usertags: m68k

Hi!

Like openjdk-8 in #864180 [1], openjdk-9 needs an updated patch to
properly work on m68k. The attached patch comes again from Andreas
Schwab. I had to make two minor modifications to make it work as his
patch was untested.

This patch is the main bit that is necessary to fix openjdk-9 on
m68k. Two additional patches are required which are less related
to m68k and are both workarounds. I will file separate bug reports
for them.

Thanks,
Adrian

 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
Index: jdk9-fe8466adaef8/common/autoconf/generated-configure.sh
===
--- jdk9-fe8466adaef8.orig/common/autoconf/generated-configure.sh
+++ jdk9-fe8466adaef8/common/autoconf/generated-configure.sh
@@ -15595,6 +15595,12 @@ test -n "$target_alias" &&
   VAR_CPU_BITS=64
   VAR_CPU_ENDIAN=big
   ;;
+m68k)
+  VAR_CPU=m68k
+  VAR_CPU_ARCH=m68k
+  VAR_CPU_BITS=32
+  VAR_CPU_ENDIAN=big
+  ;;
 *)
   as_fn_error $? "unsupported cpu $build_cpu" "$LINENO" 5
   ;;
@@ -15734,6 +15740,12 @@ $as_echo "$OPENJDK_BUILD_OS-$OPENJDK_BUI
   VAR_CPU_BITS=64
   VAR_CPU_ENDIAN=big
   ;;
+m68k)
+  VAR_CPU=m68k
+  VAR_CPU_ARCH=m68k
+  VAR_CPU_BITS=32
+  VAR_CPU_ENDIAN=big
+  ;;
 *)
   as_fn_error $? "unsupported cpu $host_cpu" "$LINENO" 5
   ;;
Index: jdk9-fe8466adaef8/common/autoconf/platform.m4
===
--- jdk9-fe8466adaef8.orig/common/autoconf/platform.m4
+++ jdk9-fe8466adaef8/common/autoconf/platform.m4
@@ -96,6 +96,12 @@ AC_DEFUN([PLATFORM_EXTRACT_VARS_FROM_CPU
   VAR_CPU_BITS=64
   VAR_CPU_ENDIAN=big
   ;;
+m68k)
+  VAR_CPU=m68k
+  VAR_CPU_ARCH=m68k
+  VAR_CPU_BITS=32
+  VAR_CPU_ENDIAN=big
+  ;;
 *)
   AC_MSG_ERROR([unsupported cpu $1])
   ;;
Index: jdk9-fe8466adaef8/hotspot/src/os/linux/vm/os_linux.cpp
===
--- jdk9-fe8466adaef8.orig/hotspot/src/os/linux/vm/os_linux.cpp
+++ jdk9-fe8466adaef8/hotspot/src/os/linux/vm/os_linux.cpp
@@ -2214,6 +2214,8 @@ const char* search_string = "cpu";
 const char* search_string = "processor";
 #elif defined(SPARC)
 const char* search_string = "cpu";
+#elif defined(M68K)
+const char* search_string = "CPU";
 #else
 const char* search_string = "Processor";
 #endif
Index: jdk9-fe8466adaef8/hotspot/src/os_cpu/linux_zero/vm/atomic_linux_zero.hpp
===
--- 
jdk9-fe8466adaef8.orig/hotspot/src/os_cpu/linux_zero/vm/atomic_linux_zero.hpp
+++ jdk9-fe8466adaef8/hotspot/src/os_cpu/linux_zero/vm/atomic_linux_zero.hpp
@@ -36,7 +36,7 @@
  * __m68k_cmpxchg
  *
  * Atomically store newval in *ptr if *ptr is equal to oldval for user space.
- * Returns newval on success and oldval if no exchange happened.
+ * Returns oldval on success and *ptr if no exchange happened.
  * This implementation is processor specific and works on
  * 68020 68030 68040 and 68060.
  *
@@ -60,40 +60,48 @@ static inline int __m68k_cmpxchg(int old
 static inline int m68k_compare_and_swap(volatile int *ptr,
 int oldval,
 int newval) {
+  int prev = *ptr;
   for (;;) {
-  int prev = *ptr;
+  int newprev;
   if (prev != oldval)
 return prev;
 
-  if (__m68k_cmpxchg (prev, newval, ptr) == newval)
+  newprev = __m68k_cmpxchg (prev, newval, ptr);
+  if (newprev == prev)
 // Success.
 return prev;
 
   // We failed even though prev == oldval.  Try again.
+  prev = newprev;
 }
 }
 
 /* Atomically add an int to memory.  */
 static inline int m68k_add_and_fetch(volatile int *ptr, int add_value) {
+  int prev = *ptr;
   for 

Bug#866924: marked as done (Crypto classes crash on start: "unlimited" policy)

[Debian Bug Tracking System]

Your message dated Fri, 07 Jul 2017 16:20:39 +
with message-id 
and subject line Bug#866924: fixed in openjdk-9 9~b177-2
has caused the Debian Bug report #866924,
regarding Crypto classes crash on start: "unlimited" policy
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.)


-- 
866924: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866924
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:openjdk-9
Version: 9~b170-2
Severity: important
Justification: Many applications (e.g. maven) crash immediately

A number of crypto classes exception during :

Exception in thread "main" java.lang.ExceptionInInitializerError
at 
java.base/javax.crypto.JceSecurityManager.(JceSecurityManager.java:65)
at 
java.base/javax.crypto.Cipher.getConfiguredPermission(Cipher.java:2610)
[...]
Caused by: java.lang.SecurityException: Can not initialize cryptographic 
mechanism
at java.base/javax.crypto.JceSecurity.(JceSecurity.java:118)
... 4 more
Caused by: java.lang.SecurityException: Can't read cryptographic policy 
directory: unlimited
at 
java.base/javax.crypto.JceSecurity.setupJurisdictionPolicies(JceSecurity.java:324)
at java.base/javax.crypto.JceSecurity.access$000(JceSecurity.java:73)
at java.base/javax.crypto.JceSecurity$1.run(JceSecurity.java:109)
at java.base/javax.crypto.JceSecurity$1.run(JceSecurity.java:106)
at java.base/java.security.AccessController.doPrivileged(Native Method)
at java.base/javax.crypto.JceSecurity.(JceSecurity.java:105)
... 4 more

sources.debian.net has (as usual) failed to index the appropriate source.

This has been noticed by others:
 * https://github.com/docker-library/openjdk/issues/101

They claim that some files in `lib/` should be in `conf/`, or something.
I didn't really look.

Testcase:

% cat A.java
import javax.crypto.Cipher;

public class A {
  public static void main(String... args) throws Exception {
Cipher.getMaxAllowedKeyLength("RC5");
  }
}

% javac A.java && java A



Thanks.
--- End Message ---
--- Begin Message ---
Source: openjdk-9
Source-Version: 9~b177-2

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

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

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated openjdk-9 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: Fri, 07 Jul 2017 12:28:53 +0200
Source: openjdk-9
Binary: openjdk-9-jdk-headless openjdk-9-jre-headless openjdk-9-jdk 
openjdk-9-jre openjdk-9-demo openjdk-9-source openjdk-9-doc openjdk-9-dbg 
openjdk-9-jre-zero
Architecture: source
Version: 9~b177-2
Distribution: unstable
Urgency: medium
Maintainer: OpenJDK Team 
Changed-By: Matthias Klose 
Description:
 openjdk-9-dbg - Java runtime based on OpenJDK (debugging symbols)
 openjdk-9-demo - Java runtime based on OpenJDK (demos and examples)
 openjdk-9-doc - OpenJDK Development Kit (JDK) documentation
 openjdk-9-jdk - OpenJDK Development Kit (JDK)
 openjdk-9-jdk-headless - OpenJDK Development Kit (JDK) (headless)
 openjdk-9-jre - OpenJDK Java runtime, using ${vm:Name}
 openjdk-9-jre-headless - OpenJDK Java runtime, using ${vm:Name} (headless)
 openjdk-9-jre-zero - Alternative JVM for OpenJDK, using Zero/Shark
 openjdk-9-source - OpenJDK Development Kit (JDK) source files
Closes: 841173 850268 863080 864288 864351 864359 864595 864596 864643 865129 
866924
Changes:
 openjdk-9 (9~b177-2) unstable; urgency=medium
 .
   * Try to build zero again on amd64, arm64, ppc64el and s390x.
   * Keep the conf/* symlinks in the JAVA_HOME directory.
 Closes: #866924, #863080.
   * Drop armel from the list of hotspot architectures. See #864464.
   * Stop using deprecated GNOME libraries. Closes: #850268.
   * Apply sparc64 build fixes (Adrian Glaubitz). Closes: #864351.
   * Update the zero-sparc patch (Adrian Glaubitz). Closes: #864359.
   * Update the m68k-support patch (Adrian Glaubitz). Closes: #864595.
 

Bug#865129: marked as done (openjdk-9: Please update jdk-target-arch-define.diff patch)

[Debian Bug Tracking System]

Your message dated Fri, 07 Jul 2017 16:20:39 +
with message-id 
and subject line Bug#865129: fixed in openjdk-9 9~b177-2
has caused the Debian Bug report #865129,
regarding openjdk-9: Please update jdk-target-arch-define.diff patch
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.)


-- 
865129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865129
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openjdk-9
Version: 9~b170-2
Severity: normal
Tags: patch
User: debian-al...@lists.debian.org
Usertags: alpha

Hi!

The patch jdk-target-arch-define.diff is still necessary for openjdk-9 as
otherwise the package fails to build from source on alpha (tested) and
sh4 (testing currently in progress).

I am attaching an updated version of the patch, please consider applying it.

Thanks,
Adrian

  .''`.  John Paul Adrian Glaubitz
 : :' :  Debian Developer - glaub...@debian.org
 `. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
   `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
--- jdk9/common/autoconf/generated-configure.sh~2017-05-16 
14:14:26.0 +0200
+++ jdk9/common/autoconf/generated-configure.sh 2017-06-19 16:00:14.998979413 
+0200
@@ -51229,9 +51229,12 @@
   COMMON_CCXXFLAGS_JDK="$COMMON_CCXXFLAGS_JDK -D$OPENJDK_TARGET_OS_UPPERCASE"
 
   # Setup target CPU
+  case "$OPENJDK_TARGET_CPU_LEGACY" in
+  alpha*|sh*) uscore=_
+  esac
   COMMON_CCXXFLAGS_JDK="$COMMON_CCXXFLAGS_JDK \
   $OPENJDK_TARGET_ADD_LP64 \
-  -DARCH='\"$OPENJDK_TARGET_CPU_LEGACY\"' -D$OPENJDK_TARGET_CPU_LEGACY"
+  -DARCH='\"$OPENJDK_TARGET_CPU_LEGACY\"' 
-D${uscore}$OPENJDK_TARGET_CPU_LEGACY${uscore}"
 
   # Setup debug/release defines
   if test "x$DEBUG_LEVEL" = xrelease; then
--- End Message ---
--- Begin Message ---
Source: openjdk-9
Source-Version: 9~b177-2

We believe that the bug you reported is fixed in the latest version of
openjdk-9, 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.
Matthias Klose  (supplier of updated openjdk-9 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: Fri, 07 Jul 2017 12:28:53 +0200
Source: openjdk-9
Binary: openjdk-9-jdk-headless openjdk-9-jre-headless openjdk-9-jdk 
openjdk-9-jre openjdk-9-demo openjdk-9-source openjdk-9-doc openjdk-9-dbg 
openjdk-9-jre-zero
Architecture: source
Version: 9~b177-2
Distribution: unstable
Urgency: medium
Maintainer: OpenJDK Team 
Changed-By: Matthias Klose 
Description:
 openjdk-9-dbg - Java runtime based on OpenJDK (debugging symbols)
 openjdk-9-demo - Java runtime based on OpenJDK (demos and examples)
 openjdk-9-doc - OpenJDK Development Kit (JDK) documentation
 openjdk-9-jdk - OpenJDK Development Kit (JDK)
 openjdk-9-jdk-headless - OpenJDK Development Kit (JDK) (headless)
 openjdk-9-jre - OpenJDK Java runtime, using ${vm:Name}
 openjdk-9-jre-headless - OpenJDK Java runtime, using ${vm:Name} (headless)
 openjdk-9-jre-zero - Alternative JVM for OpenJDK, using Zero/Shark
 openjdk-9-source - OpenJDK Development Kit (JDK) source files
Closes: 841173 850268 863080 864288 864351 864359 864595 864596 864643 865129 
866924
Changes:
 openjdk-9 (9~b177-2) unstable; urgency=medium
 .
   * Try to build zero again on amd64, arm64, ppc64el and s390x.
   * Keep the conf/* symlinks in the JAVA_HOME directory.
 Closes: #866924, #863080.
   * Drop armel from the list of hotspot architectures. See #864464.
   * Stop using deprecated GNOME libraries. Closes: #850268.
   * Apply sparc64 build fixes (Adrian Glaubitz). Closes: #864351.
   * Update the zero-sparc patch (Adrian Glaubitz). Closes: #864359.
   * Update the m68k-support patch (Adrian Glaubitz). Closes: #864595.
   * Disable generation of jvmti.html on m68k (Adrian Glaubitz).
 Closes: #864596.
   * Update the zero-sh patch (Adrian Glaubitz). Closes: #864643.
   * Update the jdk-target-arch-define patch. Closes: #865129.
   * Provide jvmdir symlink in /usr/lib/debug. Addresses: #867314.
   * Fix pt_BR 

Bug#864351: marked as done (openjdk-9: Please include several sparc64 build fixes)

[Debian Bug Tracking System]

Your message dated Fri, 07 Jul 2017 16:20:39 +
with message-id 
and subject line Bug#864351: fixed in openjdk-9 9~b177-2
has caused the Debian Bug report #864351,
regarding openjdk-9: Please include several sparc64 build fixes
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.)


-- 
864351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864351
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openjdk-9
Version: 9~b170-2
Severity: normal
Tags: patch
User: debian-sp...@lists.debian.org
Usertags: sparc64

Hi!

openjdk-9 currently fails to build from source on sparc64 due to several issues
with the sparc-specific code which arose because OpenJDK currently only 
maintains
the Solaris SPARC port of openjdk-9 but not the Linux SPARC port.

The attached three patches all fix issues with the Linux-SPARC-specific code, 
after
applying them, the build gets much further. It's currently still failing because
the zero-sparc.diff patch needs updating as well. I am already working on an 
updated
patch and I will open a separate bug report for that.

For now, please consider including the three attached patches for sparc64 
(should
also apply to sparc FWIW). They are already in the proper format such that they
can be directly added to the Debian package.

Thanks,
Adrian

 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
--- a/hotspot/src/os_cpu/linux_sparc/vm/vm_version_linux_sparc.cpp~ 
2017-04-28 12:54:05.0 +0300
+++ b/hotspot/src/os_cpu/linux_sparc/vm/vm_version_linux_sparc.cpp  
2017-05-10 21:23:37.067179458 +0300
@@ -22,6 +22,7 @@
  *
  */
 
+#include "logging/log.hpp"
 #include "precompiled.hpp"
 #include "runtime/os.hpp"
 #include "vm_version_sparc.hpp"
--- a/hotspot/src/os_cpu/linux_sparc/vm/os_linux_sparc.cpp~ 2017-04-28 
12:54:05.0 +0300
+++ b/hotspot/src/os_cpu/linux_sparc/vm/os_linux_sparc.cpp  2017-05-10 
20:51:54.373241668 +0300
@@ -387,7 +387,7 @@
   return false;
 }
 
-inline static bool checkByteBuffer(address pc, address npc, address* stub) {
+inline static bool checkByteBuffer(address pc, address npc, JavaThread * 
thread, address* stub) {
   // BugId 4454115: A read from a MappedByteBuffer can fault
   // here if the underlying file has been truncated.
   // Do not crash the VM in such a case.
@@ -579,7 +579,7 @@
   break;
 }
 
-if ((sig == SIGBUS) && checkByteBuffer(pc, npc, )) {
+if ((sig == SIGBUS) && checkByteBuffer(pc, npc, thread, )) {
   break;
 }
 
diff -Nru 
hotspot-jdk-9+168.orig/src/os_cpu/linux_sparc/vm/atomic_linux_sparc.hpp 
hotspot-jdk-9+168/src/os_cpu/linux_sparc/vm/atomic_linux_sparc.hpp
--- a/hotspot/src/os_cpu/linux_sparc/vm/atomic_linux_sparc.hpp  1970-01-01 
03:00:00.0 +0300
+++ b/hotspot/src/os_cpu/linux_sparc/vm/atomic_linux_sparc.hpp  2017-04-28 
12:54:05.0 +0300
@@ -0,0 +1,212 @@
+/*
+ * Copyright (c) 1999, 2016, Oracle and/or its affiliates. All rights reserved.
+ * DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
+ *
+ * This code is free software; you can redistribute it and/or modify it
+ * under the terms of the GNU General Public License version 2 only, as
+ * published by the Free Software Foundation.
+ *
+ * This code is distributed in the hope that it will be useful, but WITHOUT
+ * ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
+ * FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License
+ * version 2 for more details (a copy is included in the LICENSE file that
+ * accompanied this code).
+ *
+ * You should have received a copy of the GNU General Public License version
+ * 2 along with this work; if not, write to the Free Software Foundation,
+ * Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA.
+ *
+ * Please contact Oracle, 500 Oracle Parkway, Redwood Shores, CA 94065 USA
+ * or visit www.oracle.com if you need additional information or have any
+ * questions.
+ *
+ */
+
+#ifndef OS_CPU_LINUX_SPARC_VM_ATOMIC_LINUX_SPARC_INLINE_HPP
+#define OS_CPU_LINUX_SPARC_VM_ATOMIC_LINUX_SPARC_INLINE_HPP
+
+// Implementation of class atomic
+
+inline void Atomic::store(jbytestore_value, jbyte*dest) { *dest = 
store_value; }
+inline void Atomic::store(jshort   store_value, jshort*   dest) { *dest = 
store_value; }
+inline void Atomic::store(jint store_value, jint* dest) { *dest = 

Bug#863080: marked as done (openjdk-9-jre:amd64: No conf directory causes exception from security classes)

[Debian Bug Tracking System]

Your message dated Fri, 07 Jul 2017 16:20:39 +
with message-id 
and subject line Bug#863080: fixed in openjdk-9 9~b177-2
has caused the Debian Bug report #863080,
regarding openjdk-9-jre:amd64: No conf directory causes exception from security 
classes
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.)


-- 
863080: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863080
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openjdk-9-jre
Version: 9~b170-2
Severity: normal

Dear Maintainer,

I was trying to run ./android, from an SDK I downloaded, and I got this 
exception.

Exception in thread "Loading Sources" java.lang.ExceptionInInitializerError 


at 
java.base/javax.crypto.JceSecurityManager.(JceSecurityManager.java:65)  

 
at 
java.base/javax.crypto.Cipher.getConfiguredPermission(Cipher.java:2610) 

 
at 
java.base/javax.crypto.Cipher.getMaxAllowedKeyLength(Cipher.java:2634)  

 
at 
java.base/sun.security.ssl.CipherSuite$BulkCipher.isUnlimited(CipherSuite.java:602)

  
at 
java.base/sun.security.ssl.CipherSuite$BulkCipher.(CipherSuite.java:574)
at 
java.base/sun.security.ssl.CipherSuite$BulkCipher.(CipherSuite.java:460)
at 
java.base/sun.security.ssl.CipherSuite.(CipherSuite.java:1074)
at 
java.base/sun.security.ssl.SSLContextImpl.getApplicableSupportedCipherSuiteList(SSLContextImpl.java:354)
at 
java.base/sun.security.ssl.SSLContextImpl.access$100(SSLContextImpl.java:42)
at 
java.base/sun.security.ssl.SSLContextImpl$AbstractTLSContext.(SSLContextImpl.java:590)
at java.base/java.lang.Class.forName0(Native Method)
at java.base/java.lang.Class.forName(Class.java:291)
at 
java.base/java.security.Provider$Service.getImplClass(Provider.java:1848)
at 
java.base/java.security.Provider$Service.newInstance(Provider.java:1824)
at 
java.base/sun.security.jca.GetInstance.getInstance(GetInstance.java:236)
at 
java.base/sun.security.jca.GetInstance.getInstance(GetInstance.java:164)
at java.base/javax.net.ssl.SSLContext.getInstance(SSLContext.java:168)
at 
org.apache.http.conn.ssl.SSLSocketFactory.createSSLContext(SSLSocketFactory.java:202)
at 
org.apache.http.conn.ssl.SSLSocketFactory.createDefaultSSLContext(SSLSocketFactory.java:209)
at 
org.apache.http.conn.ssl.SSLSocketFactory.(SSLSocketFactory.java:333)
at 
org.apache.http.conn.ssl.SSLSocketFactory.getSocketFactory(SSLSocketFactory.java:165)
at 
org.apache.http.impl.conn.SchemeRegistryFactory.createDefault(SchemeRegistryFactory.java:45)
at 
org.apache.http.impl.client.AbstractHttpClient.createClientConnectionManager(AbstractHttpClient.java:294)
at 
org.apache.http.impl.client.AbstractHttpClient.getConnectionManager(AbstractHttpClient.java:445)
at 
com.android.sdklib.internal.repository.UrlOpener.openWithHttpClient(UrlOpener.java:369)
at 
com.android.sdklib.internal.repository.UrlOpener.openUrl(UrlOpener.java:188)
at 
com.android.sdklib.internal.repository.DownloadCache.openUrl(DownloadCache.java:298)
at 
com.android.sdklib.internal.repository.DownloadCache.downloadAndCache(DownloadCache.java:681)
at 
com.android.sdklib.internal.repository.DownloadCache.openCachedUrl(DownloadCache.java:603)
at 
com.android.sdklib.internal.repository.AddonsListFetcher.fetchXmlUrl(AddonsListFetcher.java:272)
at 
com.android.sdklib.internal.repository.AddonsListFetcher.fetch(AddonsListFetcher.java:137)
at 
com.android.sdklib.internal.repository.updater.PackageLoader.loadRemoteAddonsListInTask(PackageLoader.java:465)
at 
com.android.sdklib.internal.repository.updater.PackageLoader.access$200(PackageLoader.java:52)
at 

Bug#864596: marked as done (openjdk-9: Please disable generation of jvmti.html on m68k)

[Debian Bug Tracking System]

Your message dated Fri, 07 Jul 2017 16:20:39 +
with message-id 
and subject line Bug#864596: fixed in openjdk-9 9~b177-2
has caused the Debian Bug report #864596,
regarding openjdk-9: Please disable generation of jvmti.html on m68k
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.)


-- 
864596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864596
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openjdk-9
Version: 9~b170-2
Severity: normal
Tags: patch
User: debian-...@lists.debian.org
Usertags: m68k

Hi!

Like for openjdk-8 in #864205, the generation of jvmti.html causes
an out-of-memory error on m68k. To avoid this problem, we can just
disable the generation of jvmti.html on m68k which is achieved
by the simple attached patch.

I just added it to debian/rules with:

ifneq (,$(findstring m68k, $(DEB_HOST_ARCH)))
  COMMON_PATCHES += \
hotspot-disable-jvmtihtml.diff
endif

Thanks for consideration.

Adrian

> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864205

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
--- hotspot-jdk-9+170/hotspot/make/gensrc/GensrcJvmti.gmk.orig  2017-05-11 
14:11:42.0 +0200
+++ hotspot-jdk-9+170/hotspot/make/gensrc/GensrcJvmti.gmk   2017-06-06 
16:38:26.990673621 +0200
@@ -103,7 +103,6 @@
 -PARAM interface jvmti -PARAM trace Trace))
 $(eval $(call SetupJvmtiGeneration, jvmtiEnv.hpp, jvmtiHpp.xsl))
 $(eval $(call SetupJvmtiGeneration, jvmti.h, jvmtiH.xsl))
-$(eval $(call SetupJvmtiGeneration, jvmti.html, jvmti.xsl))
 $(eval $(call SetupJvmtiGeneration, jvmtiEnvStub.cpp, jvmtiEnv.xsl))
 
 JVMTI_BC_SRCDIR := $(HOTSPOT_TOPDIR)/src/share/vm/interpreter
--- End Message ---
--- Begin Message ---
Source: openjdk-9
Source-Version: 9~b177-2

We believe that the bug you reported is fixed in the latest version of
openjdk-9, 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.
Matthias Klose  (supplier of updated openjdk-9 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: Fri, 07 Jul 2017 12:28:53 +0200
Source: openjdk-9
Binary: openjdk-9-jdk-headless openjdk-9-jre-headless openjdk-9-jdk 
openjdk-9-jre openjdk-9-demo openjdk-9-source openjdk-9-doc openjdk-9-dbg 
openjdk-9-jre-zero
Architecture: source
Version: 9~b177-2
Distribution: unstable
Urgency: medium
Maintainer: OpenJDK Team 
Changed-By: Matthias Klose 
Description:
 openjdk-9-dbg - Java runtime based on OpenJDK (debugging symbols)
 openjdk-9-demo - Java runtime based on OpenJDK (demos and examples)
 openjdk-9-doc - OpenJDK Development Kit (JDK) documentation
 openjdk-9-jdk - OpenJDK Development Kit (JDK)
 openjdk-9-jdk-headless - OpenJDK Development Kit (JDK) (headless)
 openjdk-9-jre - OpenJDK Java runtime, using ${vm:Name}
 openjdk-9-jre-headless - OpenJDK Java runtime, using ${vm:Name} (headless)
 openjdk-9-jre-zero - Alternative JVM for OpenJDK, using Zero/Shark
 openjdk-9-source - OpenJDK Development Kit (JDK) source files
Closes: 841173 850268 863080 864288 864351 864359 864595 864596 864643 865129 
866924
Changes:
 openjdk-9 (9~b177-2) unstable; urgency=medium
 .
   * Try to build zero again on amd64, arm64, ppc64el and s390x.
   * Keep the conf/* symlinks in the JAVA_HOME directory.
 Closes: #866924, #863080.
   * Drop armel from the list of hotspot architectures. See #864464.
   * Stop using deprecated GNOME libraries. Closes: #850268.
   * Apply sparc64 build fixes (Adrian Glaubitz). Closes: #864351.
   * Update the zero-sparc patch (Adrian Glaubitz). Closes: #864359.
   * Update the m68k-support patch (Adrian Glaubitz). Closes: #864595.
   * Disable generation of jvmti.html on m68k (Adrian Glaubitz).
 Closes: #864596.
   * Update the zero-sh patch (Adrian Glaubitz). Closes: #864643.
   * Update the jdk-target-arch-define patch. Closes: #865129.
   * Provide 

Bug#864288: marked as done (openjdk-9: Please drop obsolete patch 8073754-stack-overflow-9-build.diff)

[Debian Bug Tracking System]

Your message dated Fri, 07 Jul 2017 16:20:39 +
with message-id 
and subject line Bug#864288: fixed in openjdk-9 9~b177-2
has caused the Debian Bug report #864288,
regarding openjdk-9: Please drop obsolete patch 
8073754-stack-overflow-9-build.diff
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.)


-- 
864288: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864288
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openjdk-9
Version: 9~b170-2
Severity: important
User: debian-powe...@lists.debian.org
Usertags: powerpc,powerpcspe,ppc64

Hi!

openjdk-9 currently fails to build from source on the powerpc* and ppc64
targets in Debian Ports because the minimum VM stack size is too small:

/<>/build-zero/jdk/bin/java -Xms64M -Xmx1600M 
-XX:ThreadStackSize=2240 -XX:+UseSerialGC -Xms32M -Xmx512M 
-XX:TieredStopAtLevel=1 -cp 
/<>/build-zero/buildtools/tools_jigsaw_classes --add-exports 
java.base/jdk.internal.module=ALL-UNNAMED 
build.tools.jigsaw.AddPackagesAttribute /<>/build-zero/jdk
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.

The Java thread stack size specified is too small. Specify at least 2432k
ExplodedImageOptimize.gmk:40: recipe for target 
'/<>/build-zero/jdk/_packages_attribute.done' failed
make[4]: *** [/<>/build-zero/jdk/_packages_attribute.done] Error 1

>From the internal builds at SUSE I know that openjdk-9 builds just fine on 
>ppc64
without any modifications to the stack size and increasing the stack size in
the patch 8073754-stack-overflow-9-build.diff didn't help either.

So I just dropped the patch debian/patches/8073754-stack-overflow-9-build.diff
in the Debian package which made the build succeed on ppc64, it still fails
on powerpc for other reasons though. I didn't test powerpcspe but I assume it
should be the same, either way. After removing this patch, the patch
s390x-thread-stack-size.diff didn't apply anymore, so this patch needs to be
rebased.

Thanks for consideration!

Adrian

 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
--- End Message ---
--- Begin Message ---
Source: openjdk-9
Source-Version: 9~b177-2

We believe that the bug you reported is fixed in the latest version of
openjdk-9, 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.
Matthias Klose  (supplier of updated openjdk-9 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: Fri, 07 Jul 2017 12:28:53 +0200
Source: openjdk-9
Binary: openjdk-9-jdk-headless openjdk-9-jre-headless openjdk-9-jdk 
openjdk-9-jre openjdk-9-demo openjdk-9-source openjdk-9-doc openjdk-9-dbg 
openjdk-9-jre-zero
Architecture: source
Version: 9~b177-2
Distribution: unstable
Urgency: medium
Maintainer: OpenJDK Team 
Changed-By: Matthias Klose 
Description:
 openjdk-9-dbg - Java runtime based on OpenJDK (debugging symbols)
 openjdk-9-demo - Java runtime based on OpenJDK (demos and examples)
 openjdk-9-doc - OpenJDK Development Kit (JDK) documentation
 openjdk-9-jdk - OpenJDK Development Kit (JDK)
 openjdk-9-jdk-headless - OpenJDK Development Kit (JDK) (headless)
 openjdk-9-jre - OpenJDK Java runtime, using ${vm:Name}
 openjdk-9-jre-headless - OpenJDK Java runtime, using ${vm:Name} (headless)
 openjdk-9-jre-zero - Alternative JVM for OpenJDK, using Zero/Shark
 openjdk-9-source - OpenJDK Development Kit (JDK) source files
Closes: 841173 850268 863080 864288 864351 864359 864595 864596 864643 865129 
866924
Changes:
 openjdk-9 (9~b177-2) unstable; urgency=medium
 .
   * Try to build zero again on amd64, arm64, ppc64el and s390x.
   * Keep the conf/* symlinks in the JAVA_HOME directory.
 Closes: #866924, #863080.
   * Drop armel from the list of hotspot architectures. See #864464.
   * Stop using deprecated GNOME libraries. Closes: #850268.
   * Apply sparc64 build fixes 

Bug#841173: marked as done (openjdk-9: FTBFS on mips*)

[Debian Bug Tracking System]

Your message dated Fri, 07 Jul 2017 16:20:38 +
with message-id 
and subject line Bug#841173: fixed in openjdk-9 9~b177-2
has caused the Debian Bug report #841173,
regarding openjdk-9: FTBFS on mips*
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.)


-- 
841173: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841173
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openjdk-9
Version: 9~b139-1
Severity: important
Tags: patch

Hi,

openjdk-9 FTBFS on mips* with the error:

/«PKGBUILDDIR»/src/hotspot/src/os/linux/vm/jsig.c:47:2: error: #error
"Not all signals can be encoded in jvmsigs. Adapt its type!"
 #error "Not all signals can be encoded in jvmsigs. Adapt its type!"
  ^

This is because MIPS has 128 signals which the code added to OpenJDK 9
does not take into account. The attached patch fixes this by using
sigset_t to store the list of signals used by the JVM.

The patch was originally written for 9~b139-1, but I'm running another
build now for 9~b140-1 and I will let you know how it goes
(unfortunately it takes ages).

Thanks,
James
Description: Use sigset_t to store the signals used by the JVM
 On mips there are 128 signals so uint64_t is not big enough to store all of
 them. Replace the current method of storing the signals with a sigset_t which
 will work on all architectures.
Author: James Cowgill 

diff -u b/hotspot/src/os/linux/vm/jsig.c b/hotspot/src/os/linux/vm/jsig.c
--- b/hotspot/src/os/linux/vm/jsig.c
+++ b/hotspot/src/os/linux/vm/jsig.c
@@ -41,13 +41,8 @@
 #define true 1
 #define false 0
 
-#define MASK(sig) ((uint64_t)1 << (sig-1))  // 0 is not a signal.
-// Check whether all signals fit into jvmsigs. -1 as MASK shifts by -1.
-#if (64 < NSIG-1)
-#error "Not all signals can be encoded in jvmsigs. Adapt its type!"
-#endif
 static struct sigaction sact[NSIG]; /* saved signal handlers */
-static uint64_t jvmsigs = 0; /* signals used by jvm */
+static sigset_t jvmsigs; /* signals used by jvm */
 
 /* used to synchronize the installation of signal handlers */
 static pthread_mutex_t mutex = PTHREAD_MUTEX_INITIALIZER;
@@ -65,6 +60,11 @@
 static bool jvm_signal_installing = false;
 static bool jvm_signal_installed = false;
 
+static __attribute__((constructor)) void jvmsigs_init(void)
+{
+sigemptyset();
+}
+
 static void signal_lock() {
   pthread_mutex_lock();
   /* When the jvm is installing its set of signal handlers, threads
@@ -110,7 +110,7 @@
 
   signal_lock();
 
-  sigused = (sig < NSIG) && ((MASK(sig) & jvmsigs) != 0);
+  sigused = (sig < NSIG) && sigismember(, sig);
   if (jvm_signal_installed && sigused) {
 /* jvm has installed its signal handler for this signal. */
 /* Save the handler. Don't really install it. */
@@ -127,7 +127,7 @@
 save_signal_handler(sig, oldhandler);
 
 /* Record the signals used by jvm */
-jvmsigs |= MASK(sig);
+sigaddset(, sig);
 
 signal_unlock();
 return oldhandler;
@@ -168,7 +168,7 @@
 
   signal_lock();
 
-  sigused = (sig < NSIG) && ((MASK(sig) & jvmsigs) != 0);
+  sigused = (sig < NSIG) && sigismember(, sig);
   if (jvm_signal_installed && sigused) {
 /* jvm has installed its signal handler for this signal. */
 /* Save the handler. Don't really install it. */
@@ -191,7 +191,7 @@
 }
 
 /* Record the signals used by jvm */
-jvmsigs |= MASK(sig);
+sigaddset(, sig);
 
 signal_unlock();
 return res;
@@ -223,7 +223,7 @@
 
 struct sigaction *JVM_get_signal_action(int sig) {
   /* Does race condition make sense here? */
-  if ((MASK(sig) & jvmsigs) != 0) {
+  if (sigismember(, sig)) {
 return [sig];
   }
   return NULL;
only in patch2:
unchanged:
--- a/hotspot/src/os/linux/vm/os_linux.cpp
+++ b/hotspot/src/os/linux/vm/os_linux.cpp
@@ -4206,14 +4206,16 @@ bool os::Linux::signal_handlers_are_inst
 
 // For signal-chaining
 struct sigaction sigact[NSIG];
-uint64_t sigs = 0;
-#if (64 < NSIG-1)
-#error "Not all signals can be encoded in sigs. Adapt its type!"
-#endif
+sigset_t sigs;
 bool os::Linux::libjsig_is_loaded = false;
 typedef struct sigaction *(*get_signal_t)(int);
 get_signal_t os::Linux::get_signal_action = NULL;
 
+static __attribute__((constructor)) void sigs_init()
+{
+sigemptyset();
+}
+
 struct sigaction* os::Linux::get_chained_signal_action(int sig) {
   struct sigaction *actp = NULL;
 
@@ -4288,7 +4290,7 @@ bool os::Linux::chained_handler(int sig,
 }
 
 struct sigaction* os::Linux::get_preinstalled_handler(int sig) {
-  if uint64_t)1 << (sig-1)) & sigs) != 0) {
+  if (sigismember(, sig)) 

Processed: close 867569

[Debian Bug Tracking System]

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

> close 867569
Bug #867569 [vnc4server] VNC-Server does not start any more after system upgrade
Marked Bug as done
>
End of message, stopping processing here.

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

Bug#854927: marked as done (O: trayer -- lightweight GTK2-based systray for UNIX desktop)

[Debian Bug Tracking System]

Your message dated Fri, 07 Jul 2017 15:51:18 +
with message-id 
and subject line Bug#854927: fixed in trayer 1.1.5-3
has caused the Debian Bug report #854927,
regarding O: trayer -- lightweight GTK2-based systray for UNIX desktop
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.)


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

I've stopped using this software, and in fact had completely forgotten
about it until receiving a request for help from a Ubuntu
user. Clearly I'm not actually maintaining it.
--- End Message ---
--- Begin Message ---
Source: trayer
Source-Version: 1.1.5-3

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

Debian distribution maintenance software
pp.
HIGUCHI Daisuke (VDR dai)  (supplier of updated trayer 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, 08 Jul 2017 00:18:51 +0900
Source: trayer
Binary: trayer
Architecture: source amd64
Version: 1.1.5-3
Distribution: unstable
Urgency: medium
Maintainer: HIGUCHI Daisuke (VDR dai) 
Changed-By: HIGUCHI Daisuke (VDR dai) 
Description:
 trayer - Lightweight GTK2-based systray for UNIX desktop
Closes: 854927
Changes:
 trayer (1.1.5-3) unstable; urgency=medium
 .
   * New maintainer (Closes: #854927).
 thanks to David Bremner  for previous works.
   * debian/control: update VCS-* field uses an encrypted canonical URI.
   * debian/watch: use direct links to the github tags page.
   * debian/copyright: fix spelling error: duplicate word.
   * debian/rules: Enabling hardening build options.
   * debian/control, debian/compat: Migrate to debhelper 10.
   * d/p/0003-fix-spelling-error-in-binary.patch: fix misc.c.
   * Bump standards version (no changes)
Checksums-Sha1:
 7d737419f08f831c59d847b5a8f0a9b2a0592df5 1855 trayer_1.1.5-3.dsc
 a2f41a4f6cf5cf672ef17ec89780d76f31a85920 6244 trayer_1.1.5-3.debian.tar.xz
 82d31d346443801a1dc6ec0c4355b870373c2865 10661 trayer_1.1.5-3_amd64.buildinfo
 99d605fe7dcbfa26f97847457c3fc373a1fc14d1 24072 trayer_1.1.5-3_amd64.deb
Checksums-Sha256:
 2d6e6682793eb4a13528d83037f271b40e4bcd6367d1f18dc430c7787701f88a 1855 
trayer_1.1.5-3.dsc
 aee9e54c29260d73ec7a708c50d2b8bd3104d9b66ca79096836a81dea3151f5f 6244 
trayer_1.1.5-3.debian.tar.xz
 0f11ad7b9ea46cad8a89194ce70f0326d49943036bce5a95257ad3fdb96db2e4 10661 
trayer_1.1.5-3_amd64.buildinfo
 26ba49441795b009a8e8b22e063733f5742e633af87c5f442c7271faa1f925f8 24072 
trayer_1.1.5-3_amd64.deb
Files:
 42851ecb0d9695e394a415f688fe91d2 1855 x11 optional trayer_1.1.5-3.dsc
 55ddcd9fc88bbdb35b99963f785df3b9 6244 x11 optional trayer_1.1.5-3.debian.tar.xz
 cee9896d1a8592d6a449c9fe7a460231 10661 x11 optional 
trayer_1.1.5-3_amd64.buildinfo
 450bf89b7fd34db2b345022f9a01bd25 24072 x11 optional trayer_1.1.5-3_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEECynYjkLmt2W42OpQeDlhndQ5Zo4FAllfp6gACgkQeDlhndQ5
Zo6IahAAv32aklZvNGcyKEtPxSLdOx0zoPGWExcOpkKrMKHNUqqI/1njSZcmG/Ez
M/dMbKEa7gfOD3HugfObo76K3k3D9QRvSn0S9RC+CjivjntznNYX1ZCgUCQqMJQS
uxzm+yvRymdThZG8zQHxO63wI87D9lYI3yBZu2J58pxZWc+74wNhY7qg/V01CYmK
e1EpUZa6v5rHhcenOxwz1+SCQH7RCeX6Voo97vGaYToMf+C6InUcEv/fqLR3uqi1
UbAYBP5yw+cDS+IWDaGNMJ5BqhPTVnk+ctDyR3AcFFAZaO3ylVnS7DSQJ6MtxMeI
Iix3vSJ8php257oPBM+QFohHYNI2pTphURWQDB73IcOa/dyKSrE4gYGPFh2vbdr1
WtUfB7pSygV32FjG/x0Sq/RfIcBZLDCe2gH5A2bwpiTRUnHF/LBGopGZ0saNhHAA
mks8xPbbVEPxf3Igrh1Op7scQKiLP9Gcv/fDGakvNV5N1U5KxMXp173jz9lQApxt
nhQhgj/k1fnW9+lALC/WAq5xgg296xuNTCu6PEqKlbdPxe76Jqa4PWGyMlr8MGo8
f2JCfXXZjfx2FJMsXe9Wd4O1iiMg1je6G+1PrvxkxDBwJv2nxEDY2Be7gazKfvDf
pEL/qP4cvxG7lZFmfD/MEz0zVBs5rFWkvew3iSiQSKn4l11rsiI=
=BTJk
-END PGP SIGNATURE End Message ---

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

[Debian Bug Tracking System]

Your message dated Fri, 07 Jul 2017 15:50:00 +
with message-id 
and subject line Bug#866640: fixed in gtkpod 2.1.5-6
has caused the Debian Bug report #866640,
regarding gtkpod: depends on libwebkitgtk-3.0-0 which is deprecated
to be marked as done.

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

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


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

Hi,

gtkpod depends on libwebkitgtk-3.0-0, which is deprecated in
favor of libwebkit2gtk-4.0-37 (provided in Debian by webkit2gtk).
gtkpod should be ported to the new webkitgtk version so we
can remove the old, unmaintained one.

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

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

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

On behalf of the Debian WebKit Maintainers,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: gtkpod
Source-Version: 2.1.5-6

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

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

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated gtkpod 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: Fri, 07 Jul 2017 18:18:43 +0300
Source: gtkpod
Binary: gtkpod gtkpod-data gtkpod-dbg libgtkpod1 libgtkpod-dev 
libatomicparsley0 libatomicparsley-dev
Architecture: source
Version: 2.1.5-6
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group 
Changed-By: Adrian Bunk 
Description:
 gtkpod - manage songs and playlists on an Apple iPod
 gtkpod-data - architecture-independent files for gtkpod
 gtkpod-dbg - debugging symbols for gtkpod
 libatomicparsley-dev - main library for atomic parsley in gtkpod, development 
kit
 libatomicparsley0 - main library for atomic parsley in gtkpod, shared library
 libgtkpod-dev - main library for the gtkpod package, development kit
 libgtkpod1 - main library for the gtkpod package, shared library
Closes: 866640
Changes:
 gtkpod (2.1.5-6) unstable; urgency=low
 .
   * QA upload.
   * Disable the coverweb plugin, it depends on a deprecated
 WebKitGTK+ version. (Closes: #866640)
Checksums-Sha1:
 6ec214dd930fe84384a72e58e31d0fe59c0dff58 2588 gtkpod_2.1.5-6.dsc
 2d50d6df303449f1ad4d5e91d26c4cce7cbd7280 18220 gtkpod_2.1.5-6.debian.tar.xz
Checksums-Sha256:
 2f2754c0645e1d60fea6cf12be4729258dd5f3287b6886e6e46139c163410cee 2588 
gtkpod_2.1.5-6.dsc
 d63f6169fca87172d728faa01e6af6c4898dead0042513fad6b633b16a58351d 18220 
gtkpod_2.1.5-6.debian.tar.xz
Files:
 5a177d37998fc854c7aeb9e2e87b1825 2588 sound extra gtkpod_2.1.5-6.dsc
 312e70c2445e51e6a4cabb86e016229b 18220 sound extra gtkpod_2.1.5-6.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAllfqcgACgkQiNJCh6LY
mLERgg/7BkU84+20xeEfDU4I3kyZObmzM4KlTq29hDqy7C/pfX62r30qGYVyui3I
IKjJDi8uBCeDIkKswBYs9nasH3roiOIdS/lexMjhy8FSmxLdofQymsHBV5+q4/6r
i4Hv+o5VmGTAPK9ZRuu006QnNJSzz0XLbRgGAUpkDPcPEPvHiq8siUhvKiZTMGmC
umAesQCwclgFjrj+XwjYxNfvmuHYpSJAKUvRUZkOaalZQFfHpoVXzaU+c6PVrECa
bAHtcBW1twrXFbK4h5S71Fl5Bd5dYpGC+yZmG1Qa2P2/EM1ByWUQ8xDV2X3B//i8
4hVatQgXKVkVbb2vxdt1ppu2EcI2atCZIHGRrRJoE2dRnziZrSfWrzY6dF9SlYBc
byiDZa5BfHLvfsA2RDgJ8oc0kBi0wjrsLtTQcJxcICCeDAawiI6t9xaltmz6y5zA
RMwbsZDN3VH8fdCjWDLCPHppXCihXn9yBGjx36e/6Kyq2FWbJp45l9krHzq3Evst
yx+0i/Irhd5/5pwV4mCrUZeBQFwmyWidKDAyuw28BW04NZD5XMS9qvDR2Q+DFGDK
zgfYh/wuO/CKBe+Xa4lbEsD41/kpO7tSjNESEhrhiKyO9ML61/WAHpsaBHxBlsE3
KJ97qPGjxhS53Lt4KjH3gfdPyiET+HiLTJZJVPaB6ANRpy0FZNw=
=Pn50
-END PGP SIGNATURE End Message ---

Processed: Re: Bug#867589: gnome: Text is pasted from clipboard with 30 second delay on GNOME on Wayland

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 mutter 3.22.4-1
Bug #867589 [gnome] gnome: Text is pasted from clipboard with 30 second delay 
on GNOME on Wayland
Bug reassigned from package 'gnome' to 'mutter'.
No longer marked as found in versions meta-gnome3/1:3.22+3.
Ignoring request to alter fixed versions of bug #867589 to the same values 
previously set
Bug #867589 [mutter] gnome: Text is pasted from clipboard with 30 second delay 
on GNOME on Wayland
Marked as found in versions mutter/3.22.4-1.
> forcemerge 865788 -1
Bug #865788 {Done: Laurent Bigonville } [mutter] mutter 
breaks clipboard for firefox/chromium
Bug #865878 {Done: Laurent Bigonville } [mutter] Wayland: 
copy+paste from non-Wayland to Wayland apps is incredibly slow
Bug #867589 [mutter] gnome: Text is pasted from clipboard with 30 second delay 
on GNOME on Wayland
Marked Bug as done
Marked as fixed in versions mutter/3.22.4-2.
Added tag(s) upstream and patch.
Bug #865878 {Done: Laurent Bigonville } [mutter] Wayland: 
copy+paste from non-Wayland to Wayland apps is incredibly slow
Merged 865788 865878 867589

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

Bug#867580: marked as done (d-shlibs FTBFS with shellcheck 0.4.6-1)

[Debian Bug Tracking System]

Your message dated Fri, 07 Jul 2017 15:35:49 +
with message-id 
and subject line Bug#867580: fixed in d-shlibs 0.81
has caused the Debian Bug report #867580,
regarding d-shlibs FTBFS with shellcheck 0.4.6-1
to be marked as done.

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

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


-- 
867580: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867580
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: d-shlibs
Version: 0.80
Severity: serious

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

...
/usr/bin/make -C . CFLAGS="-g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security" CXXFLAGS="-g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security" CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" 
LDFLAGS="-Wl,-z,relro" check
make[1]: Entering directory '/build/1st/d-shlibs-0.80'
bash -n d-shlibmove
bash -n d-devlibdeps
shellcheck d-shlibmove

In d-shlibmove line 86:
execscript=$(tempfile)
 ^-- SC2186: tempfile is deprecated. Use mktemp instead.


In d-shlibmove line 87:
INSTALLFILE_SHLPKG=$(tempfile)
 ^-- SC2186: tempfile is deprecated. Use mktemp instead.


In d-shlibmove line 88:
INSTALLFILE_DEVPKG=$(tempfile)
 ^-- SC2186: tempfile is deprecated. Use mktemp instead.

Makefile:8: recipe for target 'check' failed
make[1]: *** [check] Error 1
ma
--- End Message ---
--- Begin Message ---
Source: d-shlibs
Source-Version: 0.81

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

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

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated d-shlibs 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: Fri, 07 Jul 2017 17:23:24 +0200
Source: d-shlibs
Binary: d-shlibs
Architecture: source all
Version: 0.81
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard 
Changed-By: Jonas Smedegaard 
Description:
 d-shlibs   - Debian shared library package building helper scripts
Closes: 867580
Changes:
 d-shlibs (0.81) unstable; urgency=medium
 .
   * Use mktemp (not tempfile, deperecated according to shellcheck).
 Closes: Bug#867580. Thanks to Adrian Bunk.
Checksums-Sha1:
 c1fc5b696752a9d4828964d0d28ff8140116202e 1661 d-shlibs_0.81.dsc
 d90fa9caadf8277c71c5b0eaa1f59b041948a833 23940 d-shlibs_0.81.tar.xz
 8d13b57ac223f353a5af7e1172d0193a9ab29a9b 18732 d-shlibs_0.81_all.deb
 ae24edde932657c270262654b91443ce5b6291d7 5431 d-shlibs_0.81_amd64.buildinfo
Checksums-Sha256:
 b6bd919d2ed7371bd779695197bc01ce3f071299edfede3b710c61b5c122215c 1661 
d-shlibs_0.81.dsc
 17626ec5e11f86016dc93b71c66a0b4caffa04e632ffb55710e5d0bc20b8b328 23940 
d-shlibs_0.81.tar.xz
 b4c2c3d826cf254519bcb29404f085ce134f5d029211096189e2f556120cc022 18732 
d-shlibs_0.81_all.deb
 2b5407ea2a7843d96565aebcd8833f4fa552008a815f81b23e73c1cf8b6f9efb 5431 
d-shlibs_0.81_amd64.buildinfo
Files:
 ea44b5c948c8151fe840af4ea8f2527f 1661 utils optional d-shlibs_0.81.dsc
 948511c6f0bbfe9962ba3bd26046ada6 23940 utils optional d-shlibs_0.81.tar.xz
 05c0c791c5203215f08b8d57e8df336a 18732 utils optional d-shlibs_0.81_all.deb
 5ae8a945616ac7680af48983094038f6 5431 utils optional 
d-shlibs_0.81_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAllfqIkACgkQLHwxRsGg
ASFKCg//RG5pDdmREOYvJygEcO34w+DkOlr2PF9hi6O5Ghkdh0TsDSYjNe2ZZ2LK
+q7a/E6mMkXDyP5Dn73gOHnc3zms3C4VY56Tknm+7KI3c5Hpu/ExgswfezqB7taF
SMvW6MGoPZY2yhPGFzzvBf2c/cHxZLUxuA/7KSHvY9osGZsH/lg/TFYKpFhYit3q
T28oV1UaK0S7zShhVmM1KKEctRY9MwuK7zfegSUhLyyuVyie1+S9Wkhwvd0gfo31
xlT1WbTZNyI2UhERK9sEtaHTe8pbaOB1DiGm98BO7slqgJTfYEsusLjUDnlVeTD2
Xm3jQuLxxC2aqTZ2iH80U/ICsx52sJJXGhGbD+r/O7JcGSWzx8RdPFQrob1dRbwg
uYXqAkONr/N0dpG72oHR8MaUYd8bphmRdjZiBLS6JgPc7Z1h8ssPMae4WZ532tqq
pM/SW5dWpGP/RDCa03QwcG95j2obIHBK3bEw/fsSQyJYTWg3/Vv6t36x2y2ZGaYS
+8rYIxf3E4nbLCv6xtWmmDoiXwQ67uaAb29rLsK9POhjBu4edW7s2yBUy0AeNxWQ
nmKzkQObiAp45k5uD0VBQl/q8JG3R/V6dQdmAQJ+hycmUuMl+PTCAV84vCCCn+iQ
07lVJobT9MWpPekVFm2uB/706pt8kndb+jYPeORqjF8G6Q3bqUk=
=LeZZ

Bug#867503: marked as done (repsnapper FTBFS: error: no match for 'operator==' (operand types are 'const Cairo::RefPtr' and 'int'))

[Debian Bug Tracking System]

Your message dated Fri, 07 Jul 2017 14:52:19 +
with message-id 
and subject line Bug#867503: fixed in repsnapper 2.5a4-1
has caused the Debian Bug report #867503,
regarding repsnapper FTBFS: error: no match for 'operator==' (operand types are 
'const Cairo::RefPtr' and 'int')
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.)


-- 
867503: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867503
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: repsnapper
Version: 2.4a0-2
Severity: serious

Some recent change in unstable makes repsnapper FTBFS:

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

...
src/slicer/geometry.cpp: In function 'void 
glDrawCairoSurface(Cairo::RefPtr, const Vector2d&, const 
Vector2d&, double)':
src/slicer/geometry.cpp:1367:14: error: no match for 'operator==' (operand 
types are 'const Cairo::RefPtr' and 'int')
   if (surface==0) return;
   ~~~^~~
...
--- End Message ---
--- Begin Message ---
Source: repsnapper
Source-Version: 2.5a4-1

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

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

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

Debian distribution maintenance software
pp.
Ying-Chun Liu (PaulLiu)  (supplier of updated repsnapper 
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: Fri, 07 Jul 2017 13:20:40 +0800
Source: repsnapper
Binary: repsnapper
Architecture: source amd64
Version: 2.5a4-1
Distribution: unstable
Urgency: low
Maintainer: Ying-Chun Liu (PaulLiu) 
Changed-By: Ying-Chun Liu (PaulLiu) 
Description:
 repsnapper - STL to GCode Converter and print software for RepRap machines
Closes: 867503
Changes:
 repsnapper (2.5a4-1) unstable; urgency=low
 .
   * New upstream release
 - Fix FTBFS caused by comparing Cairo::RefPtr to int (Closes: #867503)
   * Bump Standards-Version to 4.0.0: nothing needs to be changed.
   * Remove patches that has been applied in the upstream.
Checksums-Sha1:
 9ce47090db0efe84e2a42ac367e680e4bb103c6c 2008 repsnapper_2.5a4-1.dsc
 5cd6eac1ee7408d0d3de829e6347eaaa3f0777d7 890674 repsnapper_2.5a4.orig.tar.gz
 602b004a3fb6a3f54d357e867700b592657b68c0 8728 repsnapper_2.5a4-1.debian.tar.xz
 b9b853fb13e3eb45df939add7f49dcd6cba20bac 8085508 
repsnapper-dbgsym_2.5a4-1_amd64.deb
 b498fb531672e6f2a15fb75a94b1ab11f4eaf71d 13517 
repsnapper_2.5a4-1_amd64.buildinfo
 491779a01070bfaae6154dc88f49f0131b8a9a7d 730258 repsnapper_2.5a4-1_amd64.deb
Checksums-Sha256:
 15c4d23c527f6b3d11f7edd7a16ba39ab5351507354e1cde3f12da0d866aaf15 2008 
repsnapper_2.5a4-1.dsc
 844f5d0988370b2488dda674983316f89205dabb147ead2f5ec16c0050b5c7fd 890674 
repsnapper_2.5a4.orig.tar.gz
 53e98a82f2f39852f5156d8919812dc9bd2182651c8861f538d8590710f758ec 8728 
repsnapper_2.5a4-1.debian.tar.xz
 baea9edb71d7faa3de16247926a4b35575f94b7fb1f93e139dac85e1a6705b02 8085508 
repsnapper-dbgsym_2.5a4-1_amd64.deb
 c352b02285cafcd1b6cfb5f56112a3762143da5d6a5dc8f0b657ceb9f4750b9d 13517 
repsnapper_2.5a4-1_amd64.buildinfo
 44f4c8160f1930d6dc77525fab181ebe35ebe7f288f38227fd88d5c9ff6ff964 730258 
repsnapper_2.5a4-1_amd64.deb
Files:
 bd7c8732fad5770f1672bca71f8dea59 2008 utils optional repsnapper_2.5a4-1.dsc
 83ac15f1d488d8d99445b8c8acdf9057 890674 utils optional 
repsnapper_2.5a4.orig.tar.gz
 82fbd463b765959757ad8d1570af 8728 utils optional 
repsnapper_2.5a4-1.debian.tar.xz
 74c48cf6f6abe4c6581f5cc674ddaff9 8085508 debug extra 
repsnapper-dbgsym_2.5a4-1_amd64.deb
 947e21078145df9ba0b815a7dd273e4e 13517 utils optional 
repsnapper_2.5a4-1_amd64.buildinfo
 c3b307aff316803400e5c77d04ee299e 730258 utils optional 
repsnapper_2.5a4-1_amd64.deb

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEEo2h49GQQhoFgDLZIRBc/oT0FiIgFAllfmn0THHBhdWxsaXVA
ZGViaWFuLm9yZwAKCRBEFz+hPQWIiOSUEACwN7N9DPPxIJI+acyZ3X5asL3oN6Xa
aNKlqfpDpy72moSBcPeh/smUJcx+eTuOwTLLAh8P15WguMDvy2p9Ke2/gCk5MEJd
VrAxwVXAOgKwMjN2lw00SyywsssEPClb15TMq5hXFVnLRCAwc1DGY3c6OKTxFoDH

Bug#845553: marked as done (kmail: Properties of a folder will only come up once)

[Debian Bug Tracking System]

Your message dated Fri, 07 Jul 2017 14:48:50 +
with message-id 
and subject line Bug#845553: fixed in akonadi 4:16.04.3-5
has caused the Debian Bug report #845553,
regarding kmail: Properties of a folder will only come up once
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.)


-- 
845553: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845553
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kmail
Version: 4:16.04.3-2
Severity: minor

Dear Maintainer,

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

   * What led up to the situation? If I right click on a folder and choose
properties, it will bring up a dialog.  The second time I try this on the same
folder, nothing happens.
   * What exactly did you do (or not do) that was effective (or
 ineffective)? I tried to find he dialog behind something or in the task
bar and could not find it.  Restarting kontact did allow me to get to the
properties dialog again, but again, it was only once.
   * What was the outcome of this action? Properties comes up only once.
   * What outcome did you expect instead? Properties will come up as many times
as I click to ask for it.

*** End of the template - remove these template lines ***



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

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

Versions of packages kmail depends on:
ii  akonadi-server   4:16.04.3-3+b1
ii  kdepim-runtime   4:16.04.2-2
ii  kdepimlibs-data  4:16.04.2-2
ii  kf5-kdepimlibs-kio-plugins   4:16.04.2-2
ii  libc62.24-5
ii  libgcc1  1:6.2.0-13
ii  libkf5akonadiagentbase5  4:16.04.3-3+b1
ii  libkf5akonadicalendar5   16.04.2-2
ii  libkf5akonadicontact54:16.04.2-2
ii  libkf5akonadicore-bin4:16.04.3-3+b1
ii  libkf5akonadicore5   4:16.04.3-3+b1
ii  libkf5akonadimime5   4:16.04.2-2
ii  libkf5akonadisearch-plugins  16.04.3-1
ii  libkf5akonadisearchdebug516.04.3-1
ii  libkf5akonadiwidgets54:16.04.3-3+b1
ii  libkf5alarmcalendar5 16.04.2-2
ii  libkf5archive5   5.27.0-1
ii  libkf5bookmarks5 5.27.0-1
ii  libkf5calendarcore5  4:16.04.2-1
ii  libkf5calendarsupport5   4:16.04.2-2
ii  libkf5calendarutils5 16.04.3-1
ii  libkf5codecs55.27.0-1
ii  libkf5completion55.27.0-1
ii  libkf5configcore55.27.0-1
ii  libkf5configgui5 5.27.0-1
ii  libkf5configwidgets5 5.27.0-1
ii  libkf5contacts5  16.04.2-1
ii  libkf5coreaddons55.27.0-1
ii  libkf5crash5 5.27.0-1
ii  libkf5dbusaddons55.27.0-1
ii  libkf5followupreminder5  4:16.04.2-2
ii  libkf5gpgmepp-pthread5   16.04.3-1
ii  libkf5gravatar5  4:16.04.2-2
ii  libkf5guiaddons5 5.27.0-1
ii  libkf5i18n5  5.27.0-2
ii  libkf5iconthemes55.27.0-1
ii  libkf5identitymanagement516.04.2-1
ii  libkf5incidenceeditor-bin16.04.2-2
ii  libkf5incidenceeditor5   16.04.2-2
ii  libkf5itemmodels55.27.0-1
ii  libkf5itemviews5 5.27.0-1
ii  libkf5jobwidgets55.27.0-1
ii  libkf5kcmutils5  5.27.0-1
ii  libkf5kdelibs4support5   5.27.0-1
ii  libkf5kiocore5   5.27.0-2
ii  libkf5kiofilewidgets55.27.0-2
ii  libkf5kiowidgets55.27.0-2
ii  libkf5kmanagesieve5  4:16.04.3-1
ii  libkf5kontactinterface5  16.04.2-1
ii  libkf5ksieveui5  4:16.04.3-1
ii  libkf5libkdepim-plugins  4:16.04.2-3
ii  libkf5libkdepim5 4:16.04.2-3
ii  libkf5libkleo5   4:16.04.2-1
ii  libkf5mailcommon-plugins 4:16.04.2-2
ii  libkf5mailcommon54:16.04.2-2
ii  libkf5mailimporter5  4:16.04.2-2
ii  libkf5mailtransport5 16.04.2-3
ii  libkf5messagecomposer5   4:16.04.3-2
ii  libkf5messagecore5   4:16.04.3-2
ii  libkf5messagelist5   4:16.04.3-2
ii  libkf5messageviewer5 4:16.04.3-2
ii  libkf5mime5  16.04.2-1
ii  libkf5notifications5 5.27.0-1
ii  libkf5notifyconfig5  5.27.0-1
ii  libkf5parts5 5.27.0-1
ii  libkf5pimcommon-plugins  4:16.04.2-2
ii  

Bug#866717: marked as done (lv FTCBFS: configures for the build architecture)

[Debian Bug Tracking System]

Your message dated Fri, 07 Jul 2017 14:49:34 +
with message-id 
and subject line Bug#866717: fixed in lv 4.51-4
has caused the Debian Bug report #866717,
regarding lv FTCBFS: configures for the build architecture
to be marked as done.

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

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


-- 
866717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866717
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lv
Version: 4.51-3
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

lv fails to cross build from source, because it configures for the build
architecture by not passing the relevant --host flag. Deferring that
task to dh_auto_configure is possible as soon as we use a builddirectory
other than ".". Please consider applying the attached patch.

Helmut
diff --minimal -Nru lv-4.51/debian/changelog lv-4.51/debian/changelog
--- lv-4.51/debian/changelog2016-10-04 12:55:14.0 +0200
+++ lv-4.51/debian/changelog2017-07-01 08:38:02.0 +0200
@@ -1,3 +1,11 @@
+lv (4.51-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
++ Let dh_auto_configure pass --host to ./configure
++ For that to work, use a different builddirectory than .
+
+ -- Helmut Grohne   Sat, 01 Jul 2017 08:38:02 +0200
+
 lv (4.51-3) unstable; urgency=medium
 
   * New maintainer (Closes: #839674)
diff --minimal -Nru lv-4.51/debian/rules lv-4.51/debian/rules
--- lv-4.51/debian/rules2016-10-04 08:46:03.0 +0200
+++ lv-4.51/debian/rules2017-07-01 08:38:02.0 +0200
@@ -10,18 +10,17 @@
 CFLAGS += $(CPPFLAGS)
 
 %:
-   dh $@ --with autoreconf
+   dh $@ --with autoreconf --sourcedirectory=src --builddirectory=builddir
 
 override_dh_auto_configure:
-   src/configure \
-   --prefix=/usr --libdir=/usr/share --enable-fastio
+   dh_auto_configure -- --libdir=/usr/share --enable-fastio
 
 override_dh_auto_install:
install -d -m 755 $(CURDIR)/debian/lv/usr/bin \
  $(CURDIR)/debian/lv/usr/share/lv \
  $(CURDIR)/debian/lv/usr/share/man/man1 \
  $(CURDIR)/debian/lv/usr/share/doc
-   install -m 755 lv $(CURDIR)/debian/lv/usr/bin/lv
+   install -m 755 builddir/lv $(CURDIR)/debian/lv/usr/bin/lv
install -m 644 lv.hlp $(CURDIR)/debian/lv/usr/share/lv/lv.hlp
install -m 644 lv.1 $(CURDIR)/debian/lv/usr/share/man/man1
ln -sf lv debian/lv/usr/bin/lgrep
--- End Message ---
--- Begin Message ---
Source: lv
Source-Version: 4.51-4

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

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

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

Debian distribution maintenance software
pp.
HIGUCHI Daisuke (VDR dai)  (supplier of updated lv 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: Fri, 07 Jul 2017 23:13:08 +0900
Source: lv
Binary: lv
Architecture: source amd64
Version: 4.51-4
Distribution: unstable
Urgency: medium
Maintainer: HIGUCHI Daisuke (VDR dai) 
Changed-By: HIGUCHI Daisuke (VDR dai) 
Description:
 lv - Powerful Multilingual File Viewer
Closes: 866717
Changes:
 lv (4.51-4) unstable; urgency=medium
 .
   * fix FTCBFS: configures for the build architecture (Closes: #866717)
 thanks to Helmut Grohne .
 - debian/rules: Let dh_auto_configure pass --host to ./configure
 - For that to work, use a different builddirectory than .
   * bump up Standards-Version 4.0.0
Checksums-Sha1:
 f861b7b456e153eb4d17272f81a4583095eeaaa1 1769 lv_4.51-4.dsc
 29eac2062cbd48f3460b8f9e08aa496ddc63909b 51964 lv_4.51-4.debian.tar.xz
 312f0a6833600602c52ef475d3bdd0d16b3bb6a4 107946 lv-dbgsym_4.51-4_amd64.deb
 0d301a898d397a7f6a9ec3aaaf7df5dcc55093e3 6213 lv_4.51-4_amd64.buildinfo
 48e0dc29c942aff4d6bef3aae832f691df943940 332330 lv_4.51-4_amd64.deb
Checksums-Sha256:
 5feab56fd26648106acf12632617609d0207906a2d5657b1c89c79c303b4638b 1769 
lv_4.51-4.dsc
 fc5ebddd98400c0706a369cb7c882d215fb68f36e06b36fdd8668aa8d22a4834 51964 

Processed: closing 511287

[Debian Bug Tracking System]

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

> # xfce etc options in d-i tasksel since at least stretch
> close 511287 20170615
Bug #511287 [debian-installer] debian-installer: Should have a task for 
installing KDE or XFCE instead of Gnome
Marked as fixed in versions debian-installer/20170615.
Bug #511287 [debian-installer] debian-installer: Should have a task for 
installing KDE or XFCE instead of Gnome
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#867435: marked as done (python3-hypothesis: missing dependencies)

[Debian Bug Tracking System]

Your message dated Fri, 07 Jul 2017 13:05:28 +
with message-id 
and subject line Bug#867435: fixed in python-hypothesis 3.12.0-1
has caused the Debian Bug report #867435,
regarding python3-hypothesis: missing dependencies
to be marked as done.

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

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


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

Due to missing ${python3:Depends} there are no dependencies.

Fix:

--- debian/control.old  2017-07-06 16:26:50.0 +
+++ debian/control  2017-07-06 16:27:19.0 +
@@ -42,7 +42,7 @@
 
 Package: python3-hypothesis
 Architecture: all
-Depends: ${misc:Depends}, ${sphinxdoc:Depends}
+Depends: ${misc:Depends}, ${sphinxdoc:Depends}, ${python3:Depends}
 Suggests: python-hypothesis-doc
 Description: advanced Quickcheck style testing library for Python 3
  Hypothesis is a library for testing your Python code against a much
--- End Message ---
--- Begin Message ---
Source: python-hypothesis
Source-Version: 3.12.0-1

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

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

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

Debian distribution maintenance software
pp.
Tristan Seligmann  (supplier of updated python-hypothesis 
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: Fri, 07 Jul 2017 14:39:39 +0200
Source: python-hypothesis
Binary: python-hypothesis python3-hypothesis pypy-hypothesis 
python-hypothesis-doc
Architecture: source
Version: 3.12.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Tristan Seligmann 
Description:
 pypy-hypothesis - advanced Quickcheck style testing library for PyPy
 python-hypothesis - advanced Quickcheck style testing library for Python 2
 python-hypothesis-doc - advanced Quickcheck style testing library 
(documentation)
 python3-hypothesis - advanced Quickcheck style testing library for Python 3
Closes: 867435
Changes:
 python-hypothesis (3.12.0-1) unstable; urgency=medium
 .
   * New upstream release.
 - Tweak docs/conf.py to fix building docs when Hypothesis is not
   installed.
   * Fix permuted python3-hypothesis and python-hypothesis-doc Depends
 stanzas (closes: #867435).
   * Bump Standards-Version to 4.0.0 (no changes).
Checksums-Sha1:
 099340836cc7a1d42ec14abc588ec0b94b94664c 2455 python-hypothesis_3.12.0-1.dsc
 5a981ccac589a5ca5e8a44f1b9197a4e43050abd 343036 
python-hypothesis_3.12.0.orig.tar.gz
 c8f9db61cea0d2e20388c9bb6f317b7ab9590e4b 9492 
python-hypothesis_3.12.0-1.debian.tar.xz
 c8875329c28ab9b02d9ea3c402a87cdec326f04c 6536 
python-hypothesis_3.12.0-1_source.buildinfo
Checksums-Sha256:
 0c4576dfc9029c18b9fce11a44b5131a5af3e7dba1d1884a499ea580292cf330 2455 
python-hypothesis_3.12.0-1.dsc
 ae99682cafe1870b6b0bac9d750f38d91786b6b46fd2d2e34b6b3ff197d5d446 343036 
python-hypothesis_3.12.0.orig.tar.gz
 661767c7a1af179331ec1d36be8bf7bced9e3c295eea578e8d140f72bfb628db 9492 
python-hypothesis_3.12.0-1.debian.tar.xz
 e9baa471de5653094632d72ec22dc0ea69d6034a82c89758312931ab03335a1d 6536 
python-hypothesis_3.12.0-1_source.buildinfo
Files:
 f6b96ed403707cc8e11e35712d2f54b8 2455 python optional 
python-hypothesis_3.12.0-1.dsc
 4e83637d3dd8e6bf170f0dac1e377382 343036 python optional 
python-hypothesis_3.12.0.orig.tar.gz
 71af82da188114eda516622b46db7502 9492 python optional 
python-hypothesis_3.12.0-1.debian.tar.xz
 32b3acea104473c32dbf1fa9b616a404 6536 python optional 
python-hypothesis_3.12.0-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQGpBAEBCgCTFiEEXAZWhXVRbQoz/6ejwImQ+x9jeJMFAllfg1xfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDVD
MDY1Njg1NzU1MTZEMEEzM0ZGQTdBM0MwODk5MEZCMUY2Mzc4OTMVHG1pdGhyYW5k
aUBkZWJpYW4ub3JnAAoJEMCJkPsfY3iT4/YH/0vUW36fZBoYFO5MK1nvShp0qmMk
g7KSSFjwV+5qASeMXUuEruZW/jpHzAEvX6OoXxxRj0IQWqo791l+aONsI2Y1o1IM

Bug#628471: marked as done (proftpd fails to enable passive mode if SQLShowInfo directive is used)

[Debian Bug Tracking System]

Your message dated Fri, 7 Jul 2017 13:56:47 +0200
with message-id <20170707115647.zmn67evife3dm...@ba.issia.cnr.it>
and subject line fixed
has caused the Debian Bug report #628471,
regarding proftpd fails to enable passive mode if SQLShowInfo directive is used
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.)


-- 
628471: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=628471
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: proftpd-basic
Version: 1.3.3a-6squeeze1

Having a working proftpd configuration tested on lenny machines, it
seems there are some interaction with SQLShowInfo instruction causing
proftpd to fail to enable passive mode. 

The way to reproduce the problem is to enable passive connection from a
client on localhost (to discard firewall problems).

>> ftp localhost
(after introducing user and password)

ftp> passive on
Passive mode on.

ftp> ls
200 Type set to A
Passive mode address scan failure.Shouldn't happen!

After googling it seems there are other proftpd users that found the
same issue [1]. 

In our case, to solve the issue just comment declaration (SQLShowInfo)
inside proftpd.conf:

 # SQLShowInfo PASS "230" "You've logged on %{getcount} times, %u"

After restarting proftpd everything works fine.
Regards,

[1] http://bugs.proftpd.org/show_bug.cgi?id=3423




--- End Message ---
--- Begin Message ---
Package: proftpd-basic
Version: 1.3.4a-1

This is proftpd#3423

-- 
Francesco P. Lovergine--- End Message ---

Bug#867526: marked as done (linux-headers-amd64: No linux-headers-4.9.0-3-amd64 package in Testing)

[Debian Bug Tracking System]

Your message dated Fri, 07 Jul 2017 13:03:35 +0100
with message-id <1499429015.2707.94.ca...@decadent.org.uk>
and subject line Re: Bug#867526: linux-headers-amd64: No 
linux-headers-4.9.0-3-amd64 package in Testing
has caused the Debian Bug report #867526,
regarding linux-headers-amd64: No linux-headers-4.9.0-3-amd64 package in Testing
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.)


-- 
867526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867526
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-headers-amd64
Version: 4.9+79
Severity: important

Dear Maintainer,

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

   * What led up to the situation?

Needed the Linux-headers-4.9.0-3-amd64 packages to compile Vbox Module

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Apparently the package is not in Testing repos. (apt-cache search
linux-headers)

➜  ~ uname -r
4.9.0-3-amd64


➜  ~ apt-cache search linux-headers
aufs-dkms - DKMS files to build and install aufs
linux-libc-dev-arm64-cross - Linux Kernel Headers for development (for cross-
compiling)
linux-libc-dev-armel-cross - Linux Kernel Headers for development (for cross-
compiling)
linux-libc-dev-armhf-cross - Linux Kernel Headers for development (for cross-
compiling)
linux-libc-dev-mips-cross - Linux Kernel Headers for development (for cross-
compiling)
linux-libc-dev-mips64el-cross - Linux Kernel Headers for development (for
cross-compiling)
linux-libc-dev-mipsel-cross - Linux Kernel Headers for development (for cross-
compiling)
linux-libc-dev-ppc64el-cross - Linux Kernel Headers for development (for cross-
compiling)
linux-libc-dev-s390x-cross - Linux Kernel Headers for development (for cross-
compiling)
linux-libc-dev-alpha-cross - Linux Kernel Headers for development (for cross-
compiling)
linux-libc-dev-hppa-cross - Linux Kernel Headers for development (for cross-
compiling)
linux-libc-dev-m68k-cross - Linux Kernel Headers for development (for cross-
compiling)
linux-libc-dev-mips64-cross - Linux Kernel Headers for development (for cross-
compiling)
linux-libc-dev-powerpc-cross - Linux Kernel Headers for development (for cross-
compiling)
linux-libc-dev-powerpcspe-cross - Linux Kernel Headers for development (for
cross-compiling)
linux-libc-dev-ppc64-cross - Linux Kernel Headers for development (for cross-
compiling)
linux-libc-dev-sh4-cross - Linux Kernel Headers for development (for cross-
compiling)
linux-libc-dev-sparc64-cross - Linux Kernel Headers for development (for cross-
compiling)
linux-headers-4.11.0-1-686 - Header files for Linux 4.11.0-1-686
linux-headers-4.11.0-1-686-pae - Header files for Linux 4.11.0-1-686-pae
linux-headers-4.11.0-1-all - All header files for Linux 4.11 (meta-package)
linux-headers-4.11.0-1-all-amd64 - All header files for Linux 4.11 (meta-
package)
linux-headers-4.11.0-1-all-i386 - All header files for Linux 4.11 (meta-
package)
linux-headers-4.11.0-1-amd64 - Header files for Linux 4.11.0-1-amd64
linux-headers-4.11.0-1-common - Common header files for Linux 4.11.0-1
linux-headers-4.11.0-1-common-rt - Common header files for Linux 4.11.0-1-rt
linux-headers-4.11.0-1-rt-686-pae - Header files for Linux 4.11.0-1-rt-686-pae
linux-headers-4.11.0-1-rt-amd64 - Header files for Linux 4.11.0-1-rt-amd64
linux-headers-586 - Header files for Linux 586 configuration (dummy package)
linux-headers-686 - Header files for Linux 686 configuration (meta-package)
linux-headers-686-pae - Header files for Linux 686-pae configuration (meta-
package)
linux-headers-amd64 - Header files for Linux amd64 configuration (meta-package)
linux-headers-rt-686-pae - Header files for Linux rt-686-pae configuration
(meta-package)
linux-headers-rt-amd64 - Header files for Linux rt-amd64 configuration (meta-
package)
linux-headers-4.9.0-2-common - Common header files for Linux 4.9.0-2
linux-headers-4.9.0-2-amd64 - Header files for Linux 4.9.0-2-amd64
linux-headers-4.4.0-1-common - Common header files for Linux 4.4.0-1
linux-headers-4.4.0-1-amd64 - Header files for Linux 4.4.0-1-amd64


➜  ~ cat /etc/apt/sources.list


# deb cdrom:[Debian GNU/Linux stretch-DI-alpha5 _Stretch_ - Official Snapshot
amd64 DVD Binary-1 20160108-10:55]/ stretch contrib main

#deb cdrom:[Debian GNU/Linux stretch-DI-alpha5 _Stretch_ - Official Snapshot
amd64 DVD Binary-1 20160108-10:55]/ stretch contrib main


deb http://security.debian.org/debian-security testing/updates main contrib
non-free

deb-src http://security.debian.org/debian-security testing/updates 

Bug#867519: marked as done (firmware-realtek: Add support for the rtl8812au/rtl8814au 802.11ac devices (already packaged in Ubuntu, Kali Linux))

[Debian Bug Tracking System]

Your message dated Fri, 07 Jul 2017 13:02:37 +0100
with message-id <1499428957.2707.93.ca...@decadent.org.uk>
and subject line Re: Bug#867519: firmware-realtek: Add support for the 
rtl8812au/rtl8814au 802.11ac devices (already packaged in Ubuntu, Kali Linux)
has caused the Debian Bug report #867519,
regarding firmware-realtek: Add support for the rtl8812au/rtl8814au 802.11ac 
devices (already packaged in Ubuntu, Kali Linux)
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.)


-- 
867519: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867519
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: firmware-realtek
Version: 20161130-3
Severity: wishlist

Dear Maintainer,

Please provide support for the rtl8812au (802.11ac 2x2) and rtl8814au (802.11ac
3x3 MIMO) devices. Drivers for this hardware is provided by:
https://github.com/astsam/rtl8812au. These drivers are already packaged in
Ubuntu since 16.04 LTS (and derivatives) as well as Kali Linux 2017.1 [3],[4].
There are relatively few 802.11ac USB adapters on the market and many of the
available devices appear to use this chipset. You can provide some examples of
hardware using this chipset here [5].  In my case, I am using an Edimax Edimax
EW-7822UAC (Bus 003 Device 023: ID 7392:a822 Edimax Technology Co., Ltd). The
COMFAST CF-917AC is an example of the faster rtl18814au hardware[6].


[1]
http://www.realtek.com.tw/products/productsView.aspx?Langid=1=57=5=4=397
[2]
http://www.realtek.com.tw/products/productsView.aspx?Langid=1=21=57=5=4=392
[3] https://packages.ubuntu.com/search?keywords=rtl8812au-dkms
[4] https://www.kali.org/news/kali-linux-20171-release/ and
https://bugs.kali.org/view.php?id=3260
[5] https://wiki.gentoo.org/wiki/AC1200_Wireless_Adapters
[6] https://www.amazon.com/dp/B01B75MHR0



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

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

firmware-realtek depends on no packages.

firmware-realtek recommends no packages.

Versions of packages firmware-realtek suggests:
ii  initramfs-tools  0.130

-- no debconf information
--- End Message ---
--- Begin Message ---
As you should already have been told by reportbug, this is not a driver
package.

The kernel team won't add drivers from vendor web sites or random
Github repositories.  The drivers needed to be added to the upstream
kernel source first.

Ben.

-- 
Ben Hutchings
All extremists should be taken out and shot.



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

Bug#801751: marked as done (sftp: The host key for this server was not found, but another type of key exists)

[Debian Bug Tracking System]

Your message dated Fri, 7 Jul 2017 13:37:35 +0200
with message-id <20170707113734.ooljxgwnwhbb3...@neoptolemo.gnuservers.com.ar>
and subject line Re: Bug#801751: sftp: The host key for this server was not 
found, but another type of key exists
has caused the Debian Bug report #801751,
regarding sftp: The host key for this server was not found, but another type of 
key exists
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.)


-- 
801751: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801751
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kio
Version: 5.15.0-1
Severity: normal
Tags: upstream

Dear Maintainer,

See upstream bug:
https://bugs.kde.org/show_bug.cgi?id=352709

apparently libssh needs to be updated to 0.7.2

Regards

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

Kernel: Linux 4.2.1a (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages kio depends on:
ii  libacl1   2.2.52-2
ii  libc6 2.19-22
ii  libgcc1   1:5.2.1-22
ii  libgssapi-krb5-2  1.13.2+dfsg-2
ii  libkf5archive55.15.0-1
ii  libkf5codecs5 5.15.0-1
ii  libkf5completion5 5.15.0-1
ii  libkf5configcore5 5.15.0-1
ii  libkf5configwidgets5  5.15.0-1
ii  libkf5coreaddons5 5.15.0-1
ii  libkf5dbusaddons5 5.15.0-1
ii  libkf5i18n5   5.15.0-1
ii  libkf5itemviews5  5.15.0-1
ii  libkf5kiocore55.15.0-1
ii  libkf5kiontlm55.15.0-1
ii  libkf5kiowidgets5 5.15.0-1
ii  libkf5notifications5  5.15.0-1
ii  libkf5service-bin 5.15.0-1
ii  libkf5service55.15.0-1
ii  libkf5solid5  5.15.0-1
ii  libkf5textwidgets55.15.0-1
ii  libkf5wallet-bin  5.15.0-1
ii  libkf5wallet5 5.15.0-1
ii  libkf5widgetsaddons5  5.15.0-1
ii  libkf5windowsystem5   5.15.0-1
ii  libqt5core5a  5.4.2+dfsg-9
ii  libqt5dbus5   5.4.2+dfsg-9
ii  libqt5gui55.4.2+dfsg-9
ii  libqt5network55.4.2+dfsg-9
ii  libqt5script5 5.4.2+dfsg-4
ii  libqt5widgets55.4.2+dfsg-9
ii  libqt5x11extras5  5.4.2-2+b1
ii  libqt5xml55.4.2+dfsg-9
ii  libstdc++65.2.1-22
ii  libxml2   2.9.2+zdfsg1-4
ii  libxslt1.11.1.28-2+b2

kio recommends no packages.

kio suggests no packages.

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

¡Hola!

El 2017-04-04 a las 14:56 +0200, Maximiliano Curia escribió:

apparently libssh needs to be updated to 0.7.2
Thanks for reporting, libssh-4 0.7.3-1 was uploaded to Debian the 
2016-06-09, so I guess this issue is fixed now. Does this version 
fixes the issue for you?


I guess this can be closed now. Please reopen if the issue is still 
reproducible.


Happy hacking,
--
"If you have too many special cases, you are doing it wrong." -- Craig Zarouni
Saludos /\/\ /\ >< `/


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

Bug#867403: marked as done (python3-django-xmlrpc: incorrect dependencies)

[Debian Bug Tracking System]

Your message dated Fri, 07 Jul 2017 11:33:47 +
with message-id 
and subject line Bug#867403: fixed in django-xmlrpc 0.1.7-1
has caused the Debian Bug report #867403,
regarding python3-django-xmlrpc: incorrect dependencies
to be marked as done.

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

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


-- 
867403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867403
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-django-xmlrpc
Version: 0.1.5-4
Severity: serious
Tags: patch

Due to a cut'n'paste error the dependencies are incorrect:

--- debian/control.old  2017-07-06 13:32:59.0 +
+++ debian/control  2017-07-06 13:34:32.0 +
@@ -23,7 +23,7 @@
 
 Package: python3-django-xmlrpc
 Architecture: all
-Depends: ${misc:Depends}, ${python:Depends}, python-django (>= 1.4.5)
+Depends: ${misc:Depends}, ${python3:Depends}, python3-django
 Replaces: django-xmlrpc (<< 0.1.5)
 Breaks: django-xmlrpc (<< 0.1.5)
 Description: XMLRPC library for Django
--- End Message ---
--- Begin Message ---
Source: django-xmlrpc
Source-Version: 0.1.7-1

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

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

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

Debian distribution maintenance software
pp.
Brian May  (supplier of updated django-xmlrpc 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: Fri, 07 Jul 2017 20:57:17 +1000
Source: django-xmlrpc
Binary: python-django-xmlrpc python3-django-xmlrpc django-xmlrpc
Architecture: source all
Version: 0.1.7-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Brian May 
Description:
 django-xmlrpc - XMLRPC library for Django (transitional package)
 python-django-xmlrpc - XMLRPC library for Django
 python3-django-xmlrpc - XMLRPC library for Django
Closes: 867403
Changes:
 django-xmlrpc (0.1.7-1) unstable; urgency=medium
 .
   * Update to new upstream version.
   * Update Standards-Version to 4.0.0.
   * Update debhelper compat level to 9.
   * Fix Python 3 depends. Closes: #867403.
Checksums-Sha1:
 d3ce74e696857c45121d12e4f3db8aedbc0b1af7 2237 django-xmlrpc_0.1.7-1.dsc
 e636cdd8ec51986a5f562c34886c96623d840a42 8045 django-xmlrpc_0.1.7.orig.tar.gz
 56bd7540790e5441e52e39c5775a2ca3cf11c626 2684 
django-xmlrpc_0.1.7-1.debian.tar.xz
 9bea4659aef342e7a7c3b8cf4d923ef30d23539f 2736 django-xmlrpc_0.1.7-1_all.deb
 3b6bc7d6f8d8c800d9f996216fdf863dbf355e74 7054 
django-xmlrpc_0.1.7-1_i386.buildinfo
 8447d8463888e968980d9a8c84bd5e3865a7718a 9534 
python-django-xmlrpc_0.1.7-1_all.deb
 5a8a8955c83054e0bee4a3da655f1c0231e3ab68 9612 
python3-django-xmlrpc_0.1.7-1_all.deb
Checksums-Sha256:
 eb0baa9846b4fcaf3540f09d830540a7c32ed9a457f3bb71cac2b7f8b79e4fb5 2237 
django-xmlrpc_0.1.7-1.dsc
 6d371c27ca3140b9731d3d3b49e4ee9646c6a35439af39f9f387697299b5cc94 8045 
django-xmlrpc_0.1.7.orig.tar.gz
 6a75788cad7a9f50b066d57ca25879b7a56e8dd5a8ee8a261d0990455a32d7ad 2684 
django-xmlrpc_0.1.7-1.debian.tar.xz
 6f940d339e6c9647983893b8e79c6d3c12ae8a7c894d7aef821bdb2d7dd2d0cb 2736 
django-xmlrpc_0.1.7-1_all.deb
 8cb611862d09048cec48676f6a8fea191d9649d67d5d2777fc9b4d0693418f78 7054 
django-xmlrpc_0.1.7-1_i386.buildinfo
 e9d484b3a0bc50e6fa2cd0c577f2f69136e9cf99bd3abf0b7c843f05759a 9534 
python-django-xmlrpc_0.1.7-1_all.deb
 72e3170278a4f72dd46a02b9e90dfc6c0ecbe8923ba020a3d9407b820602c609 9612 
python3-django-xmlrpc_0.1.7-1_all.deb
Files:
 ce8d33cbd00d0cef5c0d6cddcd1e7205 2237 python optional django-xmlrpc_0.1.7-1.dsc
 1300ad43d261cac9bbad0523305cc2d0 8045 python optional 
django-xmlrpc_0.1.7.orig.tar.gz
 5544809c7465602ff863939b622d9f32 2684 python optional 
django-xmlrpc_0.1.7-1.debian.tar.xz
 e9a7be8fa2dbbe63dfc7664bcb014f29 2736 oldlibs extra 
django-xmlrpc_0.1.7-1_all.deb
 34dab73af68426cc4a87ae6c3ccdc177 7054 python optional 
django-xmlrpc_0.1.7-1_i386.buildinfo
 b47a01e5f6c17f41f8e9ef68d67781e5 9534 python optional 
python-django-xmlrpc_0.1.7-1_all.deb
 7ee766726e039b9653b2a239f6deeff0 9612 python optional 

Bug#867559: marked as done (python3.5-minimal: Could not find platform independent libraries )

[Debian Bug Tracking System]

Your message dated Fri, 7 Jul 2017 13:10:44 +0200
with message-id <2a99330a-11fb-be3f-d469-7daf97194...@debian.org>
and subject line Re: Bug#867559: python3.5-minimal: Could not find platform 
independent libraries 
has caused the Debian Bug report #867559,
regarding python3.5-minimal: Could not find platform independent libraries 

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


-- 
867559: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867559
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3.5-minimal
Version: 3.5.3-3
Severity: important

Dear Maintainer,
When I upgraded my sid machine last week I faced this error:

Could not find platform independent libraries 
Consider setting $PYTHONHOME to [:]
Fatal Python error: Py_Initialize: Unable to get the locale encoding
LookupError: no codec search functions registered: can't find encoding

It seems that something broke python3.5-minimal; in fact when I run
/usr/bin/python3.5 I get this:

Could not find platform independent libraries 
Consider setting $PYTHONHOME to [:]
Fatal Python error: Py_Initialize: Unable to get the locale encoding
LookupError: no codec search functions registered: can't find encoding

Current thread 0x7fb8aeb88700 (most recent call first):
Aborted

In order to configure the other packages I installed python3.6 and
symlinked /usr/bin/python3.6 to /usr/bin/python3. That did the trick;
almost: there are a number of packages that depend on python3.5 and don't
configure:

Errors were encountered while processing:
 python3-dbus
 python3-olefile
 hplip-data
 python3-gi
 python3-asn1crypto
 pgcli
 apt-listchanges
 python3-sip
 python3-cairo
 python3-ptyprocess
 python3-dbus.mainloop.pyqt5
 hplip-gui
 python3-cryptography
 hplip
 python3-pil:amd64
 printer-driver-postscript-hp
 python3-pyqt5
 python3-gi-cairo

This is a bit of a nuisance because it involves hplip, so now I can't print
from this computer.
Apparently even the reportbug program runs python, so it wouldn't work
either.

-- 
Fernando Santagata
--- End Message ---
--- Begin Message ---
On 07.07.2017 12:40, Fernando Santagata wrote:
> In order to configure the other packages I installed python3.6 and
> symlinked /usr/bin/python3.6 to /usr/bin/python3. That did the trick;
> almost: there are a number of packages that depend on python3.5 and don't
> configure:

closing as invalid. You are not supposed to mess around with the python3 
symlink.--- End Message ---

Bug#867401: marked as done (python3-django-guardian: missing python3 dependency)

[Debian Bug Tracking System]

Your message dated Fri, 07 Jul 2017 11:03:51 +
with message-id 
and subject line Bug#867401: fixed in django-guardian 1.4.9-1
has caused the Debian Bug report #867401,
regarding python3-django-guardian: missing python3 dependency
to be marked as done.

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

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


-- 
867401: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867401
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-django-guardian
Version: 1.4.8-1
Severity: important
Tags: patch

Due to a cut'n'paste error a direct python3 dependency is missing:

--- debian/control.old  2017-07-06 12:53:48.0 +
+++ debian/control  2017-07-06 12:54:02.0 +
@@ -56,7 +56,7 @@
 Depends: python3-django (>= 1.2),
  python3-six,
  ${misc:Depends},
- ${python:Depends},
+ ${python3:Depends},
 Suggests: python-django-guardian-doc,
 Description: per object permissions of django for Python3
  For Python3.
--- End Message ---
--- Begin Message ---
Source: django-guardian
Source-Version: 1.4.9-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 867...@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: Fri, 07 Jul 2017 20:45:22 +1000
Source: django-guardian
Binary: python-django-guardian python3-django-guardian 
python-django-guardian-doc
Architecture: source all
Version: 1.4.9-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: 867401
Changes:
 django-guardian (1.4.9-1) unstable; urgency=medium
 .
   * New upstream version.
   * Update debian standards version to 4.0.0.
   * Fix Python 3 depends. Closes: #867401.
Checksums-Sha1:
 6f4ea247a6324539245e4674a334b15fac8684c9 2667 django-guardian_1.4.9-1.dsc
 2ddae7532cbb3976fa148ef3a13945bf85d5a2b9 152433 
django-guardian_1.4.9.orig.tar.gz
 37e468b7321ce8bf4837f127ac1e962e53913f0e 34960 
django-guardian_1.4.9-1.debian.tar.xz
 f8ece542489116d9c9655597c01ac403b3422aa9 8713 
django-guardian_1.4.9-1_i386.buildinfo
 09b2bdff7b69d14c18a7af85eb2ec2a4b95d36ad 1396460 
python-django-guardian-doc_1.4.9-1_all.deb
 546a2fd76ea3eb7495049348a7289b73172a8a5d 61842 
python-django-guardian_1.4.9-1_all.deb
 8d59ed47692d5a0ea785f12e4fd394c8e86e5bfc 60480 
python3-django-guardian_1.4.9-1_all.deb
Checksums-Sha256:
 cf96f1f4203a2991e068cf4bb72c56e5b675b51ff57b3db9e3f228977e750a6f 2667 
django-guardian_1.4.9-1.dsc
 c3c0ab257c9d94ce154b9ee32994e3cff8b350c384040705514e14a9fb7c8191 152433 
django-guardian_1.4.9.orig.tar.gz
 5db3db2cec07fce6808c08d99cb15774255f7042f5d46ae42d2c75dbd0fce189 34960 
django-guardian_1.4.9-1.debian.tar.xz
 7f1a5eb0de7cdfa388c4ddbc083aaad0a16a6977873edbc13b2c219bbd071d24 8713 
django-guardian_1.4.9-1_i386.buildinfo
 37d2e2e62678266278e6b92520abd7e141114f20a521969ab4441e9dac5e7b47 1396460 
python-django-guardian-doc_1.4.9-1_all.deb
 1ba123047e17760a05788737095c8579b818e050c37d633a02abb104c7c81398 61842 
python-django-guardian_1.4.9-1_all.deb
 f7543e2331dc84bd2234f4d1a81c9667e32219766b9ffb392fd58b1cf29a74ea 60480 
python3-django-guardian_1.4.9-1_all.deb
Files:
 3480c3d6f97750a75a036e11b8c0cd8c 2667 python optional 
django-guardian_1.4.9-1.dsc
 4341992d30a7793ab3d6f75f2d7f8d35 152433 python optional 
django-guardian_1.4.9.orig.tar.gz
 f73a6f130d7f539edd96e6726a775c92 34960 python optional 
django-guardian_1.4.9-1.debian.tar.xz
 2bdcc44ef50f8c04494b46f86d7a6a8f 8713 python optional 
django-guardian_1.4.9-1_i386.buildinfo
 5da51daf80ab82ead2b02819778c03b0 1396460 doc optional 
python-django-guardian-doc_1.4.9-1_all.deb
 3e73cf4d26636a1ac04b2c2bb84f668d 61842 

Bug#867450: marked as done (python3-pyperclip: missing python3 dependency)

[Debian Bug Tracking System]

Your message dated Fri, 07 Jul 2017 10:50:05 +
with message-id 
and subject line Bug#867450: fixed in python-pyperclip 1.5.27-3
has caused the Debian Bug report #867450,
regarding python3-pyperclip: missing python3 dependency
to be marked as done.

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

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


-- 
867450: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867450
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-pyperclip
Version: 1.5.27-2
Severity: serious
Tags: patch

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

Fix:

--- debian/control.old  2017-07-06 17:10:18.0 +
+++ debian/control  2017-07-06 17:10:29.0 +
@@ -20,7 +20,7 @@
 
 Package: python3-pyperclip
 Architecture: all
-Depends: ${shlibs:Depends}, ${misc:Depends}, ${python:Depends}, xclip | xsel | 
python3-pyqt4
+Depends: ${shlibs:Depends}, ${misc:Depends}, ${python3:Depends}, xclip | xsel 
| python3-pyqt4
 Description: Cross-platform clipboard module for Python3
  This module is a cross-platform Python3 module for copy and paste clipboard
  functions. Currently only handles plaintext.
--- End Message ---
--- Begin Message ---
Source: python-pyperclip
Source-Version: 1.5.27-3

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

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

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

Debian distribution maintenance software
pp.
Sebastien Delafond  (supplier of updated python-pyperclip 
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: Fri, 07 Jul 2017 10:38:02 +0200
Source: python-pyperclip
Binary: python-pyperclip python3-pyperclip
Architecture: source all
Version: 1.5.27-3
Distribution: unstable
Urgency: medium
Maintainer: Sebastien Delafond 
Changed-By: Sebastien Delafond 
Description:
 python-pyperclip - Cross-platform clipboard module for Python
 python3-pyperclip - Cross-platform clipboard module for Python3
Closes: 867450
Changes:
 python-pyperclip (1.5.27-3) unstable; urgency=medium
 .
   * Fix typo in Depends for python3 package (Closes: #867450)
Checksums-Sha1:
 2ee9c9f97c9f8dd56126abc4a2e8c6c511d101c4 1759 python-pyperclip_1.5.27-3.dsc
 c08420fe0b593484a15b77e63e3cab62b0aad5af 2356 
python-pyperclip_1.5.27-3.debian.tar.xz
 8098c6cab0d6cd5428ccfc6cfc5540175a846d7e 7152 python-pyperclip_1.5.27-3_all.deb
 0a641dd47dc6472473b71d7b71dfc594f161ed0a 6981 
python-pyperclip_1.5.27-3_amd64.buildinfo
 24c045045a00918446a5dabbdb2bef3bdebd9aee 7242 
python3-pyperclip_1.5.27-3_all.deb
Checksums-Sha256:
 a26a0d32df91699e76b66e138b1d9e38e4e64512183e2d89ae6fd8ec44ffcfe7 1759 
python-pyperclip_1.5.27-3.dsc
 f34da341034aef80d5e3a492c108dc1ec9d59b115116d15c22a7d05033f72fb0 2356 
python-pyperclip_1.5.27-3.debian.tar.xz
 5b72628a49f5583ed3cd5829b3208aff6becd3931fbe8cc8e6464121dd5586bf 7152 
python-pyperclip_1.5.27-3_all.deb
 abe715c4b4226ed86a8653d1a55ef53ce42cf85c2686a56a7dac37a8bf2c47bc 6981 
python-pyperclip_1.5.27-3_amd64.buildinfo
 6907598a695760eac7dc91e1208bce31967ce9a08fd40efe9b55a96f6dfade34 7242 
python3-pyperclip_1.5.27-3_all.deb
Files:
 affbd435e3d47f8380a9a08dbf41a110 1759 python optional 
python-pyperclip_1.5.27-3.dsc
 f17143b64592708cba5a54dcac1f3d14 2356 python optional 
python-pyperclip_1.5.27-3.debian.tar.xz
 f7c42e6b89cafccd6021b0bd61fb1d59 7152 python optional 
python-pyperclip_1.5.27-3_all.deb
 ab29e98eebe665dff7be97cfa2a9fa80 6981 python optional 
python-pyperclip_1.5.27-3_amd64.buildinfo
 21b91e72c1d8db14c14af59ec1cbaaf2 7242 python optional 
python3-pyperclip_1.5.27-3_all.deb

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEAqSkbVtrXP4xJMh3EL6Jg/PVnWQFAllfYYEACgkQEL6Jg/PV
nWRbxQf/ROSU26j+FDZbYclePMd0H+HwbCuICXatRMQGwSV1Z8STnqag8ZEP3s2r
FiYaXYJEF2CZTRfLKXyJrvT0pXxRRglgOnYBxhZE8r1aTS/tSC8t4MKzQsiY75qD
BXYC72yaIW8ckaQ1RalsUO5qEJjuTJAKah5SuFMnvRds5JtSuJRmRxLb53pfACCa
/yNOrcmcAxjSguX3letZehtutazachEymwqG7lPZ1JM66eOSq/rXGvqM2JszSuli
eTE4+RtI+TwTtXSdWs1sR/m7TIw+YCsw8VsmsGccxd266dYD0hxMIn+artnXn3/m
MEC73gyJevEXZqqx5lDtouHf0xf2Cw==
=VxlO
-END PGP SIGNATURE End 

Bug#838961: marked as done (adwaita-icon-theme: SVG file contains SVN conflict markers)

[Debian Bug Tracking System]

Your message dated Fri, 07 Jul 2017 10:33:56 +
with message-id 
and subject line Bug#838961: fixed in adwaita-icon-theme 3.24.0-1
has caused the Debian Bug report #838961,
regarding adwaita-icon-theme: SVG file contains SVN conflict markers
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.)


-- 
838961: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838961
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: adwaita-icon-theme
Version: 3.22.0-1
Severity: important

The file:
/usr/share/icons/Adwaita/scalable/actions/send-to-symbolic.svg
has merge conflicts still in it, at line 14.
This renders the icon unrenderable (see i.e. the "Open with another 
application" action
on places in gnome-maps).

Thanks!

Regards,
Marcus

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

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

Versions of packages adwaita-icon-theme depends on:
ii  gtk-update-icon-cache  3.21.5-3
ii  hicolor-icon-theme 0.15-1
ii  librsvg2-common2.40.16-1

adwaita-icon-theme recommends no packages.

adwaita-icon-theme suggests no packages.

-- debconf-show failed
--- End Message ---
--- Begin Message ---
Source: adwaita-icon-theme
Source-Version: 3.24.0-1

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

Debian distribution maintenance software
pp.
Laurent Bigonville  (supplier of updated adwaita-icon-theme 
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: Fri, 07 Jul 2017 12:04:33 +0200
Source: adwaita-icon-theme
Binary: adwaita-icon-theme
Architecture: source all
Version: 3.24.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Laurent Bigonville 
Description:
 adwaita-icon-theme - default icon theme of GNOME
Closes: 838961
Changes:
 adwaita-icon-theme (3.24.0-1) unstable; urgency=medium
 .
   * New upstream release.
 - Fix malformed send-to-symbolic icon (Closes: #838961)
   * debian/control.in: Bump Standards-Version to 4.0.0 (no further changes)
Checksums-Sha1:
 577d3127fed5caaa30f5cc8e6b7710f96af0cbf7 1975 adwaita-icon-theme_3.24.0-1.dsc
 333b2d66efbd22e05585a73e4093a769bbee60e0 20717972 
adwaita-icon-theme_3.24.0.orig.tar.xz
 20579fa6af2aa8a804d83cc4b09a99ea21de49ff 27456 
adwaita-icon-theme_3.24.0-1.debian.tar.xz
 bfd652448131eff75d365b8814a0170c5de611f7 12418142 
adwaita-icon-theme_3.24.0-1_all.deb
 9b0e6dfde412dc7e22744b5b09d580a53c13fac8 9259 
adwaita-icon-theme_3.24.0-1_amd64.buildinfo
Checksums-Sha256:
 c048299cee2c95ea6c459802f24c454921b93612ed611651f9ed95122ae4f53d 1975 
adwaita-icon-theme_3.24.0-1.dsc
 ccf79ff3bd340254737ce4d28b87f0ccee4b3358cd3cd5cd11dc7b42f41b272a 20717972 
adwaita-icon-theme_3.24.0.orig.tar.xz
 01709291b3e6043c4da4b87b2bd672ee28d5faa8128f1237eb61c39313ea875b 27456 
adwaita-icon-theme_3.24.0-1.debian.tar.xz
 7e6f6a9e2548dedf719a49947cca4a57f757c0de0c0984dda91f0a08dd0970ea 12418142 
adwaita-icon-theme_3.24.0-1_all.deb
 943edf569ace2173dae97c49a0a0b5c81fd964fdea32d88f440e37e0d03fcde2 9259 
adwaita-icon-theme_3.24.0-1_amd64.buildinfo
Files:
 a699a4c37ae7e19b1a61423dfaa29df3 1975 gnome optional 
adwaita-icon-theme_3.24.0-1.dsc
 3ccac0d600ffc936d2adfb80e9245bc5 20717972 gnome optional 
adwaita-icon-theme_3.24.0.orig.tar.xz
 f7930a526b15d47cf4670325041942cd 27456 gnome optional 
adwaita-icon-theme_3.24.0-1.debian.tar.xz
 5b3ba5a059ee694aaa1c0c3fd856700a 12418142 gnome optional 
adwaita-icon-theme_3.24.0-1_all.deb
 7535b29b95ea4305e38209c2896d19a7 9259 gnome optional 
adwaita-icon-theme_3.24.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQFFBAEBCAAvFiEEmRrdqQAhuF2x31DwH8WJHrqwQ9UFAllfXm8RHGJpZ29uQGRl

Bug#854620: marked as done (python-fife: Change homepage link from http://fifengine.de to http://fifengine.net)

[Debian Bug Tracking System]

Your message dated Fri, 07 Jul 2017 10:34:18 +
with message-id 
and subject line Bug#854620: fixed in fife 0.4.1-1
has caused the Debian Bug report #854620,
regarding python-fife: Change homepage link from http://fifengine.de to 
http://fifengine.net
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.)


-- 
854620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854620
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-fife
Version: 0.4.0-3
Severity: minor

Dear Maintainer,
The homepage http://fifengine.de redirects to http://fifengine.net .
So it would be better to give the latter link anyway.

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

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

Versions of packages python-fife depends on:
ii  libboost-filesystem1.62.0  1.62.0+dfsg-4
ii  libboost-regex1.62.0   1.62.0+dfsg-4
ii  libboost-system1.62.0  1.62.0+dfsg-4
ii  libc6  2.24-9
ii  libfifechan0.1.3   0.1.3-3
ii  libgcc11:6.3.0-5
ii  libgl1-mesa-glx [libgl1]   13.0.3-1
ii  libogg01.3.2-1
ii  libopenal1 1:1.17.2-4
ii  libpng16-161.6.28-1
ii  libpython2.7   2.7.13-2
ii  libsdl2-2.0-0  2.0.5+dfsg1-2
ii  libsdl2-image-2.0-02.0.1+dfsg-2+b2
ii  libsdl2-ttf-2.0-0  2.0.14+dfsg1-1
ii  libstdc++6 6.3.0-5
ii  libtinyxml2.6.2v5  2.6.2-4
ii  libvorbis0a1.3.5-4
ii  libvorbisfile3 1.3.5-4
ii  python 2.7.13-2
pn  python:any 
ii  zlib1g 1:1.2.8.dfsg-5

python-fife recommends no packages.

python-fife suggests no packages.

-- no debconf information

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8
--- End Message ---
--- Begin Message ---
Source: fife
Source-Version: 0.4.1-1

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated fife 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: Fri, 07 Jul 2017 11:26:24 +0200
Source: fife
Binary: python-fife
Architecture: source
Version: 0.4.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Markus Koschany 
Description:
 python-fife - FIFE is a multi-platform isometric game engine
Closes: 854620
Changes:
 fife (0.4.1-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version 0.4.1.
   * Add get-orig-source target.
   * Declare compliance with Debian Policy 4.0.0.
   * Tighten build-dependency on libfifechan-dev to >= 0.1.4.
   * Use https for Format field.
   * Change homepage link to http://www.fifengine.net/. (Closes: #854620)
Checksums-Sha1:
 91bacd6e2e036257d578027aaa8d96f763873c6a 2388 fife_0.4.1-1.dsc
 b6137f1fc3f0b80ec937f3a430cc17b6f3db4094 15972607 fife_0.4.1.orig.tar.gz
 149d1b4c6df4a52cc2083374323009b540a9320d 4964 fife_0.4.1-1.debian.tar.xz
 a87307329433ebd93e83aae54b3fcf5214f7a969 13267 fife_0.4.1-1_amd64.buildinfo
Checksums-Sha256:
 383adc31fece39878dca31b4f79d7bff84ffba8417c7992fb137bf70a452e2b4 2388 
fife_0.4.1-1.dsc
 bae3fc591cc2891f7d1b3a656a5d8ad700ecc2e297ad453bf4f1bcbbf82e8cb2 15972607 
fife_0.4.1.orig.tar.gz
 a1aa0e10b0363ba08d0fbd5871d4be1d64e1907e322004affd2bc814f946e621 4964 
fife_0.4.1-1.debian.tar.xz
 

Bug#866884: marked as done (RFA: gphotofs -- filesystem to mount digital cameras)

[Debian Bug Tracking System]

Your message dated Fri, 07 Jul 2017 10:34:27 +
with message-id 
and subject line Bug#866884: fixed in gphotofs 0.5-3
has caused the Debian Bug report #866884,
regarding RFA: gphotofs -- filesystem to mount digital cameras
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.)


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

I'm the last person in Uploaders, and I'd like to remove myself.  Per
Policy 3.3, at least one human needs to be in the Uploaders field of a
non-orphaned package.

The package description is:
 GPhotoFS is a filesystem client based on libgphoto2 that exposes
 supported cameras as filesystems; while some cameras implement the USB
 Mass Storage class and already appear as filesystems (making this
 program redundant), many use the Picture Transfer Protocol (PTP) or
 some other custom protocol. But as long as the camera is supported
 by libgphoto2, it can be mounted as a filesystem using this program.
 .
 This package is based on the FUSE (filesystem in user space)
 infra-structure of the Linux kernel and, therefore, does not require
 any modifications to the kernel, apart from the fuse module.
--- End Message ---
--- Begin Message ---
Source: gphotofs
Source-Version: 0.5-3

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

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

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

Debian distribution maintenance software
pp.
Herbert Parentes Fortes Neto  (supplier of updated gphotofs 
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: Fri, 07 Jul 2017 05:56:46 -0300
Source: gphotofs
Binary: gphotofs
Architecture: source amd64
Version: 0.5-3
Distribution: unstable
Urgency: medium
Maintainer: Debian PhotoTools Maintainers 

Changed-By: Herbert Parentes Fortes Neto 
Description:
 gphotofs   - filesystem to mount digital cameras
Closes: 866884
Changes:
 gphotofs (0.5-3) unstable; urgency=medium
 .
   * debian/control:
   - (Closes:  #866884)
   - Remove David Bremmer as 'Uploader'.
   - Add myself as 'Uploader'.
   - Fix Vcs-* fields.
   - Bump STD-Version from 3.9.5 to 4.0.0.
   * debian/copyright:
   - Format 1.0
   * debian/rules:
   - Add hardening.
Checksums-Sha1:
 ad543203b9a33b18b4976a2e18b651cf545b4a23 2043 gphotofs_0.5-3.dsc
 050f9091fcbe93775a9aa21096c4f87630ffedcc 343741 gphotofs_0.5.orig.tar.gz
 07268aa8a48fbfaa809a7fa323aff4daced19027 6000 gphotofs_0.5-3.debian.tar.xz
 1e6c0b2a8e57543ae0059df4a61cb87268184a36 21488 gphotofs-dbgsym_0.5-3_amd64.deb
 1181936a1da3326421d8fd4f51df403b9dcfd9e2 7132 gphotofs_0.5-3_amd64.buildinfo
 675546eabe8c8ad63823a1896d632b66708e6897 16600 gphotofs_0.5-3_amd64.deb
Checksums-Sha256:
 9bb560fd8e1fd683a5b4e6f3942b014b3fd9b60b30de07d7277f081916734a5d 2043 
gphotofs_0.5-3.dsc
 826da8222d73e8aa3a05e117ef9f4dc77ad49410135e7e04633d5d6532e45413 343741 
gphotofs_0.5.orig.tar.gz
 bcf65ea988dcec909c930b6e154eba1c193cabc423acc6e6307b570de138dad5 6000 
gphotofs_0.5-3.debian.tar.xz
 fb2ffa344c8beb4e2eed9d6b47a8240a1266ff116aa2df953978e19431d35fe2 21488 
gphotofs-dbgsym_0.5-3_amd64.deb
 83bb87728934da65368d441e31a654436b184af6d06c9953efc5d744629f883d 7132 
gphotofs_0.5-3_amd64.buildinfo
 2eef12d8ff06d8a35c63add459b12547fafff730e449dd76543723a8aac4d964 16600 
gphotofs_0.5-3_amd64.deb
Files:
 0ba68a25f4d0c4367323307a456455b4 2043 utils optional gphotofs_0.5-3.dsc
 87bb49d10ddbbd862d21eae908d785f3 343741 utils optional gphotofs_0.5.orig.tar.gz
 f998dee6dcd5340343a08fcc2e347726 6000 utils optional 
gphotofs_0.5-3.debian.tar.xz
 5ab2d32727fbd9fdfed5eb5d9a96769c 21488 debug extra 
gphotofs-dbgsym_0.5-3_amd64.deb
 6c76675ccbf2620bfb3149c04cbc6855 7132 utils optional 
gphotofs_0.5-3_amd64.buildinfo
 0e0787f9da0749d3017889d13a216158 16600 utils optional gphotofs_0.5-3_amd64.deb

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEEbiJhr5LBUJGFGPlCVSVvKKxgYRoFAllfXIkQHGhwZm5AZGVi

Bug#849229: marked as done (Unneeded dependency on ser2net)

[Debian Bug Tracking System]

Your message dated Fri, 07 Jul 2017 10:19:04 +
with message-id 
and subject line Bug#849229: fixed in lava-dispatcher 2017.7-1
has caused the Debian Bug report #849229,
regarding Unneeded dependency on ser2net
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.)


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

Lava dispatcher has a dependency on ser2net, but this is only needed if usng
ser2net to provide serial for DUTs. Please downgrade ser2net dependency to a
recommends

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

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

Versions of packages lava-dispatcher depends on:
ii  file  1:5.29-2
ii  lava-tool 0.14-2
ii  lsb-base  9.20161125
ii  parted3.2-17
ii  python-configglue 1.0-1
ii  python-configobj  5.0.6-2
ii  python-daemon 2.1.1-1
ii  python-guestfs1:1.34.3-5
ii  python-json-schema-validator  2.3.1-3
ii  python-lzma   0.5.3-3
ii  python-netifaces  0.10.4-0.1+b2
ii  python-nose   1.3.7-2
ii  python-pexpect4.2.1-1
ii  python-pyudev 0.21.0-1
ii  python-requests   2.12.4-1
ii  python-serial 3.2.1-1
ii  python-setuptools 32.0.0-1
ii  python-yaml   3.12-1
ii  python-zmq16.0.2-2
ii  python2.7 2.7.13-1
pn  python:any
pn  ser2net   
ii  sudo  1.8.19-1
ii  tar   1.29b-1.1
ii  telnet0.17-41

Versions of packages lava-dispatcher recommends:
ii  bridge-utils 1.5-10
ii  git  1:2.11.0-1
ii  kpartx   0.6.4-1
ii  libguestfs-tools 1:1.34.3-5
ii  lxc  1:2.0.6-1
ii  nfs-kernel-server1:1.3.4-2
ii  ntp  1:4.2.8p9+dfsg-2
ii  openbsd-inetd0.20140418-2
ii  python-setproctitle  1.1.10-1
ii  qemu-system-x86  1:2.7+dfsg-3+b1
ii  rpcbind  0.2.3-0.5
ii  rsync3.1.2-1
ii  sshfs2.8-1
pn  tftpd-hpa
ii  u-boot-tools 2016.11+dfsg1-3
ii  unzip6.0-21
ii  xz-utils 5.2.2-1.2

Versions of packages lava-dispatcher suggests:
ii  bzr  2.7.0+bzr6619-4

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: lava-dispatcher
Source-Version: 2017.7-1

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

Debian distribution maintenance software
pp.
Neil Williams  (supplier of updated lava-dispatcher 
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, 06 Jul 2017 18:18:03 +0100
Source: lava-dispatcher
Binary: lava-dispatcher
Architecture: source amd64
Version: 2017.7-1
Distribution: unstable
Urgency: medium
Maintainer: Debian LAVA team 
Changed-By: Neil Williams 
Description:
 lava-dispatcher - Linaro Automated Validation Architecture dispatcher
Closes: 849229 849237
Changes:
 lava-dispatcher (2017.7-1) unstable; urgency=medium
 .
   * New production release
 d8dabe63 Switch the print to a test in unit test
 d1e22b67 Revert "Replace invalid characters in test_case_id."
 b3b4f5ac Update the example to a working test job with prompts.
 504ec2bc LAVA-777 last log line should be lava.job result
 ad55acb9 Ensure overlay 

Bug#849237: marked as done (Can't use /srv/tftp in tftpd-hpa)

[Debian Bug Tracking System]

Your message dated Fri, 07 Jul 2017 10:19:04 +
with message-id 
and subject line Bug#849237: fixed in lava-dispatcher 2017.7-1
has caused the Debian Bug report #849237,
regarding Can't use /srv/tftp in tftpd-hpa
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.)


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

According to the installing on debian documentation, when only using V2 one can
leave the default tftp (/srv/tftp) directory as the one configured for
tftpd-hpa, however this doesn't work giving the following error in the log.

- {"dt": "2016-12-23T22:52:11.658332", "lvl": "exception", "msg": "Invalid job
  data: ['tftpd directory is not configured correctly, see
  /etc/default/tftpd-hpa']\n"}

It looks like this broke in upstream commit 18bb6b9895a

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

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

Versions of packages lava-dispatcher depends on:
ii  file  1:5.29-2
ii  lava-tool 0.14-2
ii  lsb-base  9.20161125
ii  parted3.2-17
ii  python-configglue 1.0-1
ii  python-configobj  5.0.6-2
ii  python-daemon 2.1.1-1
ii  python-guestfs1:1.34.3-5
ii  python-json-schema-validator  2.3.1-3
ii  python-lzma   0.5.3-3
ii  python-netifaces  0.10.4-0.1+b2
ii  python-nose   1.3.7-2
ii  python-pexpect4.2.1-1
ii  python-pyudev 0.21.0-1
ii  python-requests   2.12.4-1
ii  python-serial 3.2.1-1
ii  python-setuptools 32.0.0-1
ii  python-yaml   3.12-1
ii  python-zmq16.0.2-2
ii  python2.7 2.7.13-1
pn  python:any
pn  ser2net   
ii  sudo  1.8.19-1
ii  tar   1.29b-1.1
ii  telnet0.17-41

Versions of packages lava-dispatcher recommends:
ii  bridge-utils 1.5-10
ii  git  1:2.11.0-1
ii  kpartx   0.6.4-1
ii  libguestfs-tools 1:1.34.3-5
ii  lxc  1:2.0.6-1
ii  nfs-kernel-server1:1.3.4-2
ii  ntp  1:4.2.8p9+dfsg-2
ii  openbsd-inetd0.20140418-2
ii  python-setproctitle  1.1.10-1
ii  qemu-system-x86  1:2.7+dfsg-3+b1
ii  rpcbind  0.2.3-0.5
ii  rsync3.1.2-1
ii  sshfs2.8-1
pn  tftpd-hpa
ii  u-boot-tools 2016.11+dfsg1-3
ii  unzip6.0-21
ii  xz-utils 5.2.2-1.2

Versions of packages lava-dispatcher suggests:
ii  bzr  2.7.0+bzr6619-4

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: lava-dispatcher
Source-Version: 2017.7-1

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

Debian distribution maintenance software
pp.
Neil Williams  (supplier of updated lava-dispatcher 
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, 06 Jul 2017 18:18:03 +0100
Source: lava-dispatcher
Binary: lava-dispatcher
Architecture: source amd64
Version: 2017.7-1
Distribution: unstable
Urgency: medium
Maintainer: Debian LAVA team 
Changed-By: Neil Williams 
Description:
 lava-dispatcher - Linaro Automated Validation Architecture dispatcher
Closes: 849229 849237
Changes:
 lava-dispatcher (2017.7-1) unstable; urgency=medium
 .
   * New production 

Bug#867549: marked as done (pysal FTBFS with python 3.6 as supported version)

[Debian Bug Tracking System]

Your message dated Fri, 07 Jul 2017 10:04:27 +
with message-id 
and subject line Bug#867549: fixed in pysal 1.13.0-5
has caused the Debian Bug report #867549,
regarding pysal FTBFS with python 3.6 as supported version
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.)


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

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

...
I: pybuild base:184: cd /build/1st/pysal-1.13.0/.pybuild/pythonX.Y_3.6/build; 
python3.6 -m nose --exclude test_DistanceBand_arc  --exclude-dir=pysal/contrib 
--exclude-dir pysal/network
Trying `CDLL(libgeos_c.so.1)`
Library path: 'libgeos_c.so.1'
DLL: 
Trying `CDLL(libc.so.6)`
Library path: 'libc.so.6'
DLL: 
.../build/1st/pysal-1.13.0/.pybuild/pythonX.Y_3.6/build/pysal/cg/segmentLocator.py:117:
 FutureWarning: comparison to `None` will result in an elementwise object 
comparison in the future.
  if self._hashKeys == None:
...S../build/1st/pysal-1.13.0/.pybuild/pythonX.Y_3.6/build/pysal/weights/weights.py:189:
 UserWarning: There are 3 disconnected observations
  warnings.warn("There are %d disconnected observations" % ni)
/build/1st/pysal-1.13.0/.pybuild/pythonX.Y_3.6/build/pysal/weights/weights.py:190:
 UserWarning: Island ids: 6, 8, 11
  warnings.warn("Island ids: %s" % ', '.join(str(island) for island in 
self.islands))
./build/1st/pysal-1.13.0/.pybuild/pythonX.Y_3.6/build/pysal/core/IOHandlers/gwt.py:148:
 RuntimeWarning: DBF relating to GWT was not found, proceeding with unordered 
string ids.
  warn("DBF relating to GWT was not found, proceeding with unordered string 
ids.", RuntimeWarning)
/build/1st/pysal-1.13.0/.pybuild/pythonX.Y_3.6/build/pysal/weights/weights.py:189:
 UserWarning: There are 7 disconnected observations
  warnings.warn("There are %d disconnected observations" % ni)
/build/1st/pysal-1.13.0/.pybuild/pythonX.Y_3.6/build/pysal/weights/weights.py:190:
 UserWarning: Island ids: 5, 9, 10, 11, 12, 14, 15
  warnings.warn("Island ids: %s" % ', '.join(str(island) for island in 
self.islands))
../build/1st/pysal-1.13.0/.pybuild/pythonX.Y_3.6/build/pysal/core/Tables.py:215:
 UserWarning: Encountered the following error in attempting to read the 
shapefile 
/build/1st/pysal-1.13.0/.pybuild/pythonX.Y_3.6/build/pysal/examples/us_income/usjoin.shp.
 Proceeding with read, but the error will be reproduced below:
 [Errno 2] No such file or directory: 
'/build/1st/pysal-1.13.0/.pybuild/pythonX.Y_3.6/build/pysal/examples/us_income/usjoin.shp'
  ' {}'.format(self.dataPath[:-3]+'shp', e))
...FF/build/1st/pysal-1.13.0/.pybuild/pythonX.Y_3.6/build/pysal/esda/moran.py:876:
 RuntimeWarning: invalid value encountered in greater
  zp = self.z > 0
/build/1st/pysal-1.13.0/.pybuild/pythonX.Y_3.6/build/pysal/esda/moran.py:877: 
RuntimeWarning: invalid value encountered in greater
  lp = zl > 0
/build/1st/pysal-1.13.0/.pybuild/pythonX.Y_3.6/build/pysal/esda/moran.py:826: 
RuntimeWarning: invalid value encountered in greater_equal
  above = sim >= self.Is
/usr/lib/python3/dist-packages/scipy/stats/_distn_infrastructure.py:875: 
RuntimeWarning: invalid value encountered in greater
  return (self.a < x) & (x < self.b)
/usr/lib/python3/dist-packages/scipy/stats/_distn_infrastructure.py:875: 
RuntimeWarning: invalid value encountered in less
  return (self.a < x) & (x < self.b)
/usr/lib/python3/dist-packages/scipy/stats/_distn_infrastructure.py:1731: 
RuntimeWarning: invalid value encountered in greater_equal
  cond2 = (x >= self.b) & cond0

==
FAIL: test_Headbanging_Median_Rate (pysal.esda.tests.test_smoothing.TestHB)
--
Traceback (most recent call last):
  File 
"/build/1st/pysal-1.13.0/.pybuild/pythonX.Y_3.6/build/pysal/esda/tests/test_smoothing.py",
 line 301, in test_Headbanging_Median_Rate
np.testing.assert_array_almost_equal(self.sids_hb_rr5, sids_hb_r.r[:5])
  File "/usr/lib/python3/dist-packages/numpy/testing/utils.py", line 979, in 

Bug#864974: marked as done (thunderbird: Missing AtomicOperations for multiple architectures cause FTBFS)

[Debian Bug Tracking System]

Your message dated Fri, 7 Jul 2017 11:48:23 +0200
with message-id <43277f85-2a09-f651-851f-c0e92ca93...@physik.fu-berlin.de>
and subject line Re: Bug#864974: thunderbird: Missing AtomicOperations for 
multiple architectures cause FTBFS
has caused the Debian Bug report #864974,
regarding thunderbird: Missing AtomicOperations for multiple architectures 
cause FTBFS
to be marked as done.

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

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


-- 
864974: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864974
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: icedove
Version: 1:52.2.0-1
Severity: serious
Justification: fails to build from source

Hi!

thunderbird fails to build from source on multiple architectures,
including s390x, because the proper AtomicOperations header
is not included for the affected architectures.

Looking at [1], all architectures that do not have their own
variant of the AtomicOperations header must use the generic
ppc or sparc headers, e.g.

(...)
# elif defined(__alpha__)
#  include "jit/none/AtomicOperations-ppc.h"
# elif defined(__hppa__)
#  include "jit/none/AtomicOperations-ppc.h"
#elif defined(__m68k__)
#  include "jit/none/AtomicOperations-ppc.h"
#elif defined(__s390__)
#  include "jit/none/AtomicOperations-ppc.h"
#elif defined(__sh__)
#  include "jit/none/AtomicOperations-ppc.h"
(...)

From what I can see, you are currently missing:

alpha: __alpha__
hppa: __hppa__
m68k: __m68k__
powerpc and powerpcspe: __ppc__
s390: __s390__

ppc64 and sparc64 should work as they define "__PPC64__" and
"__sparc__" which is actually covered in the current code. I will
check what's wrong on this architectures later.

See also [2] (note: AtomicOperations-ppc.h and AtomicOperations-sparc.h
are identical and have been renamed to AtomicOperations-feeling-lucky.h
by upstream).

All architectures which are not including jit/none/AtomicOperations-ppc.h
or jit/none/AtomicOperations-sparc.h will include 
jit/none/AtomicOperations-none.h
and *will* FTBFS by definition (this is intended behavior in the JavaScript
engine). Please note that __sparc__ is also used for sparc64. So please
do not test for sparc64 with "#if defined(__sparc64__)", testing for
"__sparc__" is fine as it is.

Thus, please add the missing definitions for all architectures where the
build fails with:

Executing /«PKGBUILDDIR»/obj-thunderbird/dist/bin/xpcshell -g 
/«PKGBUILDDIR»/obj-thunderbird/dist/bin/ -a 
/«PKGBUILDDIR»/obj-thunderbird/dist/bin/ -f 
/«PKGBUILDDIR»/mozilla/toolkit/mozapps/installer/precompile_cache.js -e 
precompile_startupcache("resource://gre/");
d: file /«PKGBUILDDIR»/mozilla/xpcom/build/XPCOMInit.cpp, line 709
[23935] ###!!! ABORT: u_init() failed: file 
/«PKGBUILDDIR»/mozilla/xpcom/build/XPCOMInit.cpp, line 709
Traceback (most recent call last):
  File "/«PKGBUILDDIR»/mozilla/toolkit/mozapps/installer/packager.py", line 
415, in 
main()
  File "/«PKGBUILDDIR»/mozilla/toolkit/mozapps/installer/packager.py", line 
409, in main
args.source, gre_path, base)
  File "/«PKGBUILDDIR»/mozilla/toolkit/mozapps/installer/packager.py", line 
166, in precompile_cache
errors.fatal('Error while running startup cache precompilation')
  File "/«PKGBUILDDIR»/mozilla/python/mozbuild/mozpack/errors.py", line 103, in 
fatal
self._handle(self.FATAL, msg)
  File "/«PKGBUILDDIR»/mozilla/python/mozbuild/mozpack/errors.py", line 98, in 
_handle
raise ErrorMessage(msg)
mozpack.errors.ErrorMessage: Error: Error while running startup cache 
precompilation
/«PKGBUILDDIR»/mozilla/toolkit/mozapps/installer/packager.mk:41: recipe for 
target 'stage-package' failed
make[4]: *** [stage-package] Error 1

PS: The build logs for ppc64, sparc64 and x32 are currently missing due to 
issues on the
buildds with sending mail. We're working on fixing this.

Cheers,
Adrian

> [1] 
> https://anonscm.debian.org/cgit/pkg-mozilla/icedove.git/tree/mozilla/js/src/jit/AtomicOperations.h
> [2] 
> https://github.com/glaubitz/gecko-dev/blob/m68k/js/src/jit/AtomicOperations.h#L340

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
--- End Message ---
--- Begin Message ---
Hi Carsten!

I'm closing this bug report now as the AtomicOperations headers are now
properly defined for all architectures.  As we know now, the reason for
mips for the header definition to be missing was that the build was configured
with --disable-ion which disabled the JIT on mips.

Adrian

-- 
 .''`.  John Paul 

Bug#862762: marked as done (Port from libnm-glib to libnm (or GNetworkMonitor))

[Debian Bug Tracking System]

Your message dated Fri, 7 Jul 2017 11:15:55 +0200
with message-id <20170707091555.zatnz2tptkp7c...@bogon.m.sigxcpu.org>
and subject line Re: Bug#862762: Port from libnm-glib to libnm (or 
GNetworkMonitor)
has caused the Debian Bug report #862762,
regarding Port from libnm-glib to libnm (or GNetworkMonitor)
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.)


-- 
862762: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862762
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: krb5-auth-dialog
Version: 3.20.0-2
Severity: normal
User: pkg-utopia-maintain...@lists.alioth.debian.org
Usertags: libnm

Hi,

the libnm-glib/libnm-util libraries have been deprecated upstream in
favour of libnm.

Your package declares a Build-Depends on libnm-glib-dev.

Please consider porting krb5-auth-dialog to libnm. The API of libnm is
very similar to the one provided by libnm-glib/libnm-util.

If you only need to detect the network connectivity status, you can also
use GNetworkMonitor instead, which was introduced in glib 2.32 [2] and
is available since wheezy.

Regards,
Michael

[1] https://developer.gnome.org/libnm/stable/
[2] https://developer.gnome.org/gio/stable/GNetworkMonitor.html

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

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Version: krb5-auth-dialog/3.20.0-3

On Wed, May 17, 2017 at 07:50:44AM +0200, Guido Günther wrote:
> Hi Michael,
> 
> On Tue, May 16, 2017 at 08:49:50PM +0200, Michael Biebl wrote:
> > Source: krb5-auth-dialog
> > Version: 3.20.0-2
> > Severity: normal
> > User: pkg-utopia-maintain...@lists.alioth.debian.org
> > Usertags: libnm
> > 
> > Hi,
> > 
> > the libnm-glib/libnm-util libraries have been deprecated upstream in
> > favour of libnm.
> > 
> > Your package declares a Build-Depends on libnm-glib-dev.
> > 
> > Please consider porting krb5-auth-dialog to libnm. The API of libnm is
> > very similar to the one provided by libnm-glib/libnm-util.
> > 
> > If you only need to detect the network connectivity status, you can also
> > use GNetworkMonitor instead, which was introduced in glib 2.32 [2] and
> > is available since wheezy.
> 
> We've fixed this upstream in January so this will definitely be finxed early
> in the buster cycle.

As a result of gnome-terminal and firefox disagreeing about clipboard
usage I closed the wrong bug in the changelog. This one is fixed in the
recent upload.
Cheers,
 -- Guido--- End Message ---

Bug#867421: marked as done (python3-certifi: missing python3 dependency)

[Debian Bug Tracking System]

Your message dated Fri, 07 Jul 2017 08:51:16 +
with message-id 
and subject line Bug#867421: fixed in python-certifi 2017.4.17-2
has caused the Debian Bug report #867421,
regarding python3-certifi: missing python3 dependency
to be marked as done.

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

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


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

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

Fix:

--- debian/control.old  2017-07-06 15:30:08.0 +
+++ debian/control  2017-07-06 15:30:19.0 +
@@ -26,7 +26,7 @@
 
 Package: python3-certifi
 Architecture: all
-Depends: ${shlibs:Depends}, ${misc:Depends}, ${python:Depends}, ca-certificates
+Depends: ${shlibs:Depends}, ${misc:Depends}, ${python3:Depends}, 
ca-certificates
 Description: root certificates for validating SSL certs and verifying TLS 
hosts (python3)
  Certifi is a carefully curated collection of Root Certificates for
  validating the trustworthiness of SSL certificates while verifying
--- End Message ---
--- Begin Message ---
Source: python-certifi
Source-Version: 2017.4.17-2

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

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

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

Debian distribution maintenance software
pp.
Sebastien Delafond  (supplier of updated python-certifi 
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: Fri, 07 Jul 2017 10:36:41 +0200
Source: python-certifi
Binary: python-certifi python3-certifi
Architecture: source all
Version: 2017.4.17-2
Distribution: unstable
Urgency: medium
Maintainer: Sebastien Delafond 
Changed-By: Sebastien Delafond 
Description:
 python-certifi - root certificates for validating SSL certs and verifying TLS 
host
 python3-certifi - root certificates for validating SSL certs and verifying TLS 
host
Closes: 867421
Changes:
 python-certifi (2017.4.17-2) unstable; urgency=medium
 .
   * Fix typo in Depends for python3 package (Closes: #867421)
Checksums-Sha1:
 9afbd5b0460a16528aeaaf445438c2117287b78e 1726 python-certifi_2017.4.17-2.dsc
 2b6f183aad20169fdc98c00b21fec9d748ae2446 7176 
python-certifi_2017.4.17-2.debian.tar.xz
 fc4d3995a5524d28d4ea9f04e2274cf33d6b777e 177298 
python-certifi_2017.4.17-2_all.deb
 94e58a577e81581cac254df5c98eaa986bcc0070 5849 
python-certifi_2017.4.17-2_amd64.buildinfo
 664ba98227367c47e5a941fac4ecf42f6a353672 177232 
python3-certifi_2017.4.17-2_all.deb
Checksums-Sha256:
 1f44870760e940007ac688c21aad657bcf48d865285f8807260cee3b2cc25a98 1726 
python-certifi_2017.4.17-2.dsc
 f351292d8f32a2deece4397be10fe7738ace2247e8979941e5d86db95ad5f66d 7176 
python-certifi_2017.4.17-2.debian.tar.xz
 f50f4a23392e3bdc5b94a94c8c689505df8fa8307421d3a502ce1f9120153a04 177298 
python-certifi_2017.4.17-2_all.deb
 748e0366b951ef93a21c007c2e17371ac6ff883ad7d56b5b438f1fd481b45cb3 5849 
python-certifi_2017.4.17-2_amd64.buildinfo
 d002256ea900a98dea6bb5e486ac1ad54d0a11b22a03d1aedc26aa0c8d9f40d0 177232 
python3-certifi_2017.4.17-2_all.deb
Files:
 ccfc597b3537231bc9f4e3df9c7b94e4 1726 python optional 
python-certifi_2017.4.17-2.dsc
 659511b087f3e0d0b64108250c6b78cf 7176 python optional 
python-certifi_2017.4.17-2.debian.tar.xz
 8dcffc00af1811d42409955c9d391b29 177298 python optional 
python-certifi_2017.4.17-2_all.deb
 472b975ae7aee79d669296c81df119a2 5849 python optional 
python-certifi_2017.4.17-2_amd64.buildinfo
 a8b4bc9850cf8dc1978721b5ff70cd02 177232 python optional 
python3-certifi_2017.4.17-2_all.deb

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEAqSkbVtrXP4xJMh3EL6Jg/PVnWQFAllfSHUACgkQEL6Jg/PV
nWTcdQf/fBoR8euw+DhdZ2llkR0P9AU26EIcBduvDHfKNqoQNVVa+bznkooognc9
qZ7xfBhbQ0rTm4S16UQiJlYD5SlV6W4Xa1pj5e5x0awb9J2sGtWKr6t8hl7RlkK/
0ne2YQxeisXww0/4vYI1j4Om4nbBPXYuVvTXpgTjxLUDBFdAZ/YbUTcEgK/tmoor
GwHhr1ue/Wtq6juPC9GJVuQfXsrJc9c6o7HRmxT2Mbptzo1J/d+Nbarj4O1SjQrA

Bug#823568: marked as done (krb5-auth-dialog: Don't autostart for non-Kerberos users)

[Debian Bug Tracking System]

Your message dated Fri, 07 Jul 2017 08:50:40 +
with message-id 
and subject line Bug#823568: fixed in krb5-auth-dialog 3.20.0-3
has caused the Debian Bug report #823568,
regarding krb5-auth-dialog: Don't autostart for non-Kerberos 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.)


-- 
823568: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823568
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: krb5-auth-dialog
Version: 3.12.0-2
Severity: wishlist

When krb5-auth-dialog is installed, it drops a .desktop file into
/etc/xdg/autostart/ so that it starts up as part of the normal desktop
session, without requiring further intervention. I am assembling a
system that will mainly handle users authenticated via Kerberos, so
this is great.

However, there will also be some local-only users (via normal Unix
auth), and for them, the "Network credentials expired" notification
will be confusing and unhelpful. I'd like for the program not to
autostart for them.

(If a local-only user somehow wants to authenticate to some Kerberos
principal graphically, they can always start up the program via the
application menu, of course.)

This minor change to the .desktop file gets me the desired effect...

--- /etc/xdg/autostart/krb5-auth-dialog.desktop.orig
+++ /etc/xdg/autostart/krb5-auth-dialog.desktop
@@ -1,7 +1,7 @@
 [Desktop Entry]
 Name=Kerberos Authentication
 Comment=Kerberos Network Authentication Dialog
-Exec=krb5-auth-dialog
+Exec=sh -c 'test -z "$KRB5CCNAME" || exec krb5-auth-dialog'
 Terminal=false
 Type=Application
 Icon=krb-valid-ticket

...but there may be a better way of doing it. I'd like to request
this behavior.
--- End Message ---
--- Begin Message ---
Source: krb5-auth-dialog
Source-Version: 3.20.0-3

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

Debian distribution maintenance software
pp.
Guido Günther  (supplier of updated krb5-auth-dialog 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: Fri, 07 Jul 2017 10:11:16 +0200
Source: krb5-auth-dialog
Binary: krb5-auth-dialog
Architecture: source
Version: 3.20.0-3
Distribution: unstable
Urgency: medium
Maintainer: Guido Günther 
Changed-By: Guido Günther 
Description:
 krb5-auth-dialog - tray applet for reauthenticating kerberos tickets
Closes: 823568
Changes:
 krb5-auth-dialog (3.20.0-3) unstable; urgency=medium
 .
   * [5a7fe1c] Don't depend on unused libnm-glib-dev (Closes: #823568)
   * [1455a30] credentials_expiring_real: check if kcontext is valid
 (LP: #1700468)
   * [2593f51] Bump standards version to 4.0.0
   * [cc2b1c0] Bump standards version to 3.9.8
   * [083647b] Switch to debhelper 10
   * [f92d782] Use https vcs urls.
Checksums-Sha1:
 406db93d298d39c897a604cc2a2ed66393c8ed7a 2217 krb5-auth-dialog_3.20.0-3.dsc
 1ef48d502686866bdd7bd3c9b256915798bc4114 6592 
krb5-auth-dialog_3.20.0-3.debian.tar.xz
 adc8cf67509ae1bf03165795e523477a1d300bcb 14750 
krb5-auth-dialog_3.20.0-3_amd64.buildinfo
Checksums-Sha256:
 c297a00d1294e8a4f2b2ce8857a2d6468335f9f9816fd0ddca7b7470fae6e4d2 2217 
krb5-auth-dialog_3.20.0-3.dsc
 3dfe8cbdc8743f0a2d4f25700584ad1fa5c1ee56aaf76b88090c6ffe719fe5c9 6592 
krb5-auth-dialog_3.20.0-3.debian.tar.xz
 821f26cc0dc99c433f4aaeba6a4bdf3136e647f0fef246c3c7b120a4e78bea83 14750 
krb5-auth-dialog_3.20.0-3_amd64.buildinfo
Files:
 66b367b9b9088a9e76503eb53279f73d 2217 gnome optional 
krb5-auth-dialog_3.20.0-3.dsc
 ef5e1262a81a870b083d614995f7099e 6592 gnome optional 
krb5-auth-dialog_3.20.0-3.debian.tar.xz
 2c4af5fa21db84c422b32a27e1855673 14750 gnome optional 
krb5-auth-dialog_3.20.0-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEvHzQcjh1660F3xzZB7i3sOqYEgsFAllfQrsACgkQB7i3sOqY
EgsyDA/+KDCIz2+dLhXQscE8426yAtGmB35IdOEk9PwyLkbCKwhl1feTrEwGixJK
LqB4uU9gTlwG+lC+ntKrfEYVgXrNTajt0TcnolPR+o059G+PEuk4oMhTA5L0Rp04

Bug#867399: marked as done (python3-django-cors-headers: missing python3 dependency)

[Debian Bug Tracking System]

Your message dated Fri, 07 Jul 2017 08:48:52 +
with message-id 
and subject line Bug#867399: fixed in django-cors-headers 2.1.0+github-2
has caused the Debian Bug report #867399,
regarding python3-django-cors-headers: missing python3 dependency
to be marked as done.

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

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


-- 
867399: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867399
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-django-cors-headers
Version: 2.1.0+github-1
Severity: serious
Tags: patch

Due to a cut'n'paste error the python3 dependency was missing:

--- debian/control.old  2017-07-06 12:49:06.0 +
+++ debian/control  2017-07-06 12:49:24.0 +
@@ -24,7 +24,7 @@
 
 Package: python3-django-cors-headers
 Architecture: all
-Depends: ${misc:Depends}, ${python:Depends}
+Depends: ${misc:Depends}, ${python3:Depends}
 Description: Django application for handling CORS.
  A Django application for handling the server headers required for Cross-Origin
  Resource Sharing (CORS).
--- End Message ---
--- Begin Message ---
Source: django-cors-headers
Source-Version: 2.1.0+github-2

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

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

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

Debian distribution maintenance software
pp.
Brian May  (supplier of updated django-cors-headers 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: Fri, 07 Jul 2017 17:40:00 +1000
Source: django-cors-headers
Binary: python-django-cors-headers python3-django-cors-headers
Architecture: source all
Version: 2.1.0+github-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Brian May 
Description:
 python-django-cors-headers - Django application for handling CORS.
 python3-django-cors-headers - Django application for handling CORS.
Closes: 867399
Changes:
 django-cors-headers (2.1.0+github-2) unstable; urgency=medium
 .
   * Fix Python3 depends. Closes: #867399.
Checksums-Sha1:
 d6a5ab6200b86e98d88380c40bf91e4d3a3fdf41 2507 
django-cors-headers_2.1.0+github-2.dsc
 53b2ce98a427fe799342417198379451dfe03771 14934 
django-cors-headers_2.1.0+github.orig.tar.gz
 4403004d97cd3bc13d139b2387a941d42f77fe4a 2144 
django-cors-headers_2.1.0+github-2.debian.tar.xz
 debd426b72902b288d37e67555fc3008ce5b5514 8006 
django-cors-headers_2.1.0+github-2_i386.buildinfo
 ae931689b8408a95b3bbc142a07f1e15bf5992bd 13388 
python-django-cors-headers_2.1.0+github-2_all.deb
 897880ef921b6b37d9bc60fc8b4de5b40816f459 13452 
python3-django-cors-headers_2.1.0+github-2_all.deb
Checksums-Sha256:
 1c4a8f60d122e0a44af85cacb1dc792aca817e75c97cafd8e24191452343682b 2507 
django-cors-headers_2.1.0+github-2.dsc
 6ba1848a866db3c06829fd798741b569b7494649ca1803b6aba879a7486e064a 14934 
django-cors-headers_2.1.0+github.orig.tar.gz
 377e85912c354986ba44c19c4be4cde747d2596f18a3e01012cb06da8e0bf96a 2144 
django-cors-headers_2.1.0+github-2.debian.tar.xz
 85bfb6404c8d1d6d3eac12b02fd5aaf68f4c759b6f9fb539e90de702b6d611f9 8006 
django-cors-headers_2.1.0+github-2_i386.buildinfo
 846d39219c2227d495216c3010c6275629cb40638c1ef72cbcd2be0b2350c650 13388 
python-django-cors-headers_2.1.0+github-2_all.deb
 631f6f4bddfc3c1d0a9cf133b89ac4bfc55feec53713eb4f47416d219446f224 13452 
python3-django-cors-headers_2.1.0+github-2_all.deb
Files:
 b261354c1562d89d7e5c2469b729fda3 2507 python optional 
django-cors-headers_2.1.0+github-2.dsc
 e5528bf8516c1eac4631da678ccdfcb0 14934 python optional 
django-cors-headers_2.1.0+github.orig.tar.gz
 e04305aeaf0c3dc4bc62c9b48317ab13 2144 python optional 
django-cors-headers_2.1.0+github-2.debian.tar.xz
 f32a741d827e775aaf8ebc212b57f502 8006 python optional 
django-cors-headers_2.1.0+github-2_i386.buildinfo
 564e0a75ecf1a75d00ba96d0a7df62f9 13388 python optional 
python-django-cors-headers_2.1.0+github-2_all.deb
 0cb3c34fd8c94ec461308d9314280373 13452 python optional 
python3-django-cors-headers_2.1.0+github-2_all.deb

-BEGIN PGP 

Processed: closing 867546

[Debian Bug Tracking System]

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

> close 867546
Bug #867546 [libvirt] gbp:error: Pristine-tar couldn't checkout 
"libvirt_3.5.0.orig.tar.xz": fatal: Path 'libvirt_3.5.0.orig.tar.xz.delta' does 
not exist in 'refs/heads/pristine-tar'
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#862949: marked as done (Grisbi Autobackup use wrong date and time)

[Debian Bug Tracking System]

Your message dated Fri, 7 Jul 2017 10:14:41 +0200
with message-id 
and subject line Bug#862949: Acknowledgement (Grisbi Autobackup use wrong date 
and time)
has caused the Debian Bug report #862949,
regarding Grisbi Autobackup use wrong date and time
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.)


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

Package: Grisbi
Version : 1.0.1
Severity: normal

Dear Maintainer,

When I use the autobackup fonction, the file is created with the name " 
Mes comptes_20161013T112518_20170401T122623.gsb".
The first part is the name of grisbi file, but the second part is a 
wrong (always the same) date and time. The third part is the correct 
date and time of backup.



-- System Information:
Debian Release: 9.0
  APT prefers unstable-updates
  APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 
'testing'), (500, 'stable'), (1, 'experimental')

Architecture: amd64
 (x86_64)
Foreign Architectures: i386

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

Versions of packages grisbi depends on:
ii  grisbi-common1.0.1-1
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-10
ii  libcairo21.14.8-1
ii  libfontconfig1   2.11.0-6.7+b1
ii  libfreetype6 2.6.3-3.2
ii  libgdk-pixbuf2.0-0   2.36.5-2
ii  libglib2.0-0 2.50.3-2
ii  libgoffice-0.8-8 0.8.17-7
ii  libgtk2.0-0  2.24.31-2
ii  libofx6  1:0.9.10-2
ii  libpango-1.0-0   1.40.5-1
ii  libpangocairo-1.0-0  1.40.5-1
ii  libpangoft2-1.0-01.40.5-1
ii  libssl1.11.1.0e-2
ii  libxml2  2.9.4+dfsg1-2.2
ii  xdg-utils1.1.1-1
ii  zlib1g   1:1.2.8.dfsg-5

grisbi recommends no packages.

Versions of packages grisbi suggests:
ii  firefox [www-browser]53.0.is.52.0.2-1
ii  konqueror [www-browser]  4:16.08.3-1

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

Oh, i'm very sorry.

I opened a bug for such a stupid thing...



--- End Message ---

Bug#867201: marked as done (postgrey: crashes with "FATAL: Can't call method "network" on an undefined value at /usr/sbin/postgrey line 204.")

[Debian Bug Tracking System]

Your message dated Fri, 7 Jul 2017 07:59:45 +
with message-id <20170707075945.4iu6px537mjg6...@cherubino.dyne.org>
and subject line Re: Bug#867201: postgrey: crashes with "FATAL: Can't call 
method "network" on an undefined value at /usr/sbin/postgrey line 204."
has caused the Debian Bug report #867201,
regarding postgrey: crashes with "FATAL: Can't call method "network" on an 
undefined value at /usr/sbin/postgrey line 204."
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.)


-- 
867201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867201
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: postgrey
Version: 1.36-3
Severity: grave
User: debian-ad...@lists.debian.org
Usertags: needed-by-DSA-Team
X-Debbugs-Cc: debian-ad...@lists.debian.org

After upgrading one of our mail relays to stretch, postgrey regularly
crashes with the error is $subject.

This might or might not be fixed upstream with
https://github.com/schweikert/postgrey/commit/95a2cd8f7f132aae8c62e9706dd9459afca84a5c
which changed the relevant code and among other things added checks for
NetAddr::IP->new returning undef.

Cheers,
Julien

-- System Information:
Debian Release: 9.0
  APT prefers stable-debug
  APT policy: (900, 'stable-debug'), (900, 'stable'), (500, 'unstable-debug'), 
(500, 'oldstable-updates'), (500, 'unstable'), (500, 'oldstable'), (101, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
severity 867201 normal
fixed 867201 1.36-4
thanks


On Fri, Jul 07, 2017 at 09:56:23AM +0200, Julien Cristau wrote:
> On 07/06/2017 11:26 PM, Antonio Radici wrote:
> > Control: tags -1 + moreinfo
> > 
> > On Thu, Jul 06, 2017 at 10:38:37AM +0200, Julien Cristau wrote:
> >> All good, at least the crash prompted me to look at this and update our
> >> exim config.  Might not have noticed otherwise :)
> >>
> > 
> > Hi Julien,
> > this bug will be automatically closed by the 1.36-4 upload in unstable, but
> > obviously it's not solved for stretch so I'll reopen it.
> > 
> I'm not convinced this warrants a stable update.  Initially I was
> worried this might be remote DoS, but as it turned out to just be a MTA
> configuration issue it's not such a big deal.
> 

OK nevermind then, I'll decrease severity and upload the newest postgrey version
to unstable this weekend.

In general this bug can be marked as fixed.--- End Message ---

Bug#867357: marked as done (ratbagd FTBFS: Dependency "python3" not found)

[Debian Bug Tracking System]

Your message dated Fri, 07 Jul 2017 07:48:43 +
with message-id 
and subject line Bug#867357: fixed in ratbagd 0.4-2
has caused the Debian Bug report #867357,
regarding ratbagd FTBFS: Dependency "python3" not found
to be marked as done.

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

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


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

https://buildd.debian.org/status/package.php?p=ratbagd=sid

...
ative dependency libudev found: YES 233
Native dependency libsystemd found: YES 233
Native dependency libratbag found: YES 0.9.0
Library m found: YES
Configuring ratbagd.service using configuration
Configuring org.freedesktop.ratbag1.service using configuration
Dependency python3 found: NO

Meson encountered an error in file meson.build, line 134, column 0:
Dependency "python3" not found
--- End Message ---
--- Begin Message ---
Source: ratbagd
Source-Version: 0.4-2

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

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

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

Debian distribution maintenance software
pp.
Stephen Kitt  (supplier of updated ratbagd 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: Fri, 07 Jul 2017 08:55:06 +0200
Source: ratbagd
Binary: ratbagd
Architecture: source
Version: 0.4-2
Distribution: unstable
Urgency: medium
Maintainer: Stephen Kitt 
Changed-By: Stephen Kitt 
Description:
 ratbagd- D-Bus daemon handling mouse configuration
Closes: 867357
Changes:
 ratbagd (0.4-2) unstable; urgency=medium
 .
   * Build-depend on python3-dev. Closes: #867357.
   * Drop Debian-provided manpages, merged upstream.
   * Use https URLs in debian/copyright.
   * Standards-Version 4.0.0, no further change required.
   * Switch to debhelper compatibility level 10.
Checksums-Sha1:
 c8ee827dba7a0488570005658d726e429cc7d77d 1934 ratbagd_0.4-2.dsc
 2efa409c70a77d7e2ac1c6087c38b696b651941c 2480 ratbagd_0.4-2.debian.tar.xz
 ad53195bc65ec195e135744400d92f40b91333ee 6744 ratbagd_0.4-2_source.buildinfo
Checksums-Sha256:
 cb167ed49b74687e2dbfb69b3b3e2c29b1229ac80e22533531dce039ee3f907d 1934 
ratbagd_0.4-2.dsc
 abda306efe4670e6dce3c75d66b128a0d1330dad2f6a161dd8497256b4d349bc 2480 
ratbagd_0.4-2.debian.tar.xz
 c7a6256e587a5bf4d25e9075984a39fde36600598ac8138e6da12cb9f9c4b508 6744 
ratbagd_0.4-2_source.buildinfo
Files:
 56bfc78b7f27b4644c9b6d70b0e422d4 1934 utils optional ratbagd_0.4-2.dsc
 d272e733dde6e986a4522ccc8e6c7abd 2480 utils optional 
ratbagd_0.4-2.debian.tar.xz
 9b2557a3a35c14eb3bf5eb941aa58182 6744 utils optional 
ratbagd_0.4-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEnPVX/hPLkMoq7x0ggNMC9Yhtg5wFAllfOHgACgkQgNMC9Yht
g5yAFw//dwvbGXM8nLmgVzqhDFJ5DFw+gtcGyAdY5PbDJpVc3iMQaNKG5CoquXDP
qYopN52UFF2SFJMVbLyVUxZ2MCz+Ocw1OGZa875biTH3i9o1jefjN15CXTGa9JCP
r+zx0V+tCUiYepW0//fOfDWWfQ8ZbUjH52NnaVsbgaaUMY6349Vfnslc2tILzB2Q
RkIS1zkQY1F0hddcp/NsaXPYO2X/1eu3C5ezs8x2qb32ZLsYUoJ1dR1hyL7dSFhC
Dknl2f56etHJauGg2KbFP1wMp1bgl/DoOn2huTk/2M4ECXsuVfG+GHrcpB5eTt0A
pO4EabCc15HnRdXdjnwLxvnbl/t25xcLgLWL2S5H9eWY06N/auJnT2LJDp5d4yGC
6avr0wkO1BYu16g0uc5IdIj+K82603c9LFB6JKJnkXBpUiuzU4z6XBt229qODHLX
5rVznBhHzntLELKlMYcbkAHvkh0P+JiJ6gx+n6nqv1Gi4tBOWMQwOUyvYDCZvOh0
FquNPtkzZaKCvDkIWVA84sNQ43ijBG52eLFdMKy7W5BdeERGAve7GLSdwAMmCnIY
Cl4RJzeahFPoWdhaVaqe8xZHlBvoV91wOkxcy13cJs02rFRBIeCSMF7eGAgnQwvd
SPkL+KAc/4Nu7q6J08S3LO/XC+7fmc2chhTEg/Zgn+Ml/eHsmOs=
=NhSC
-END PGP SIGNATURE End Message ---

Bug#855358: marked as done (tor: User run tor connects to Tor network but tor daemon doesn't)

[Debian Bug Tracking System]

Your message dated Fri, 7 Jul 2017 07:44:19 +
with message-id <20170707074419.nns2ekzl6ppzq...@sarek.noreply.org>
and subject line Re: Bug#855358: tor: User run tor connects to Tor network but 
tor daemon doesn't
has caused the Debian Bug report #855358,
regarding tor: User run tor connects to Tor network but tor daemon doesn't
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.)


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

Dear Maintainer,

If I run 'tor' as normal user I can connect to Tor network, i.e. the
output of running the command is:

--
user@host:~/Downloads/tor-browser_en-US$ tor
Feb 17 08:12:15.018 [notice] Tor 0.2.9.9 (git-1d8323c042800718) running on 
Linux with Libevent 2.0.21-stable, OpenSSL 1.1.0d and Zlib 1.2.8.
Feb 17 08:12:15.018 [notice] Tor can't help you if you use it wrong! Learn how 
to be safe at https://www.torproject.org/download/download#warning
Feb 17 08:12:15.018 [notice] Read configuration file "/etc/tor/torrc".
Feb 17 08:12:15.021 [notice] Opening Socks listener on 127.0.0.1:9050
Feb 17 08:12:15.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.
Feb 17 08:12:15.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
Feb 17 08:12:15.000 [notice] Bootstrapped 0%: Starting
Feb 17 08:12:15.000 [notice] Bootstrapped 80%: Connecting to the Tor network
Feb 17 08:12:16.000 [notice] Bootstrapped 85%: Finishing handshake with first 
hop
Feb 17 08:12:19.000 [notice] Bootstrapped 90%: Establishing a Tor circuit
Feb 17 08:12:19.000 [notice] Tor has successfully opened a circuit. Looks like 
client functionality is working.
Feb 17 08:12:19.000 [notice] Bootstrapped 100%: Done
--

But if instead try to use tor daemon, and so after running "sudo
systemctl restart tor" I get:

--
$ sudo tail -f /var/log/tor/log
Feb 17 08:04:27.288 [notice] Read configuration file "/etc/tor/torrc".
Feb 17 08:04:27.291 [notice] Opening Socks listener on 127.0.0.1:9050
Feb 17 08:04:27.000 [notice] Parsing GEOIP IPv4 file /usr/share/tor/geoip.
Feb 17 08:04:27.000 [notice] Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
Feb 17 08:04:27.000 [notice] Bootstrapped 0%: Starting
Feb 17 08:04:27.000 [notice] Bootstrapped 80%: Connecting to the Tor network
Feb 17 08:04:27.000 [notice] Signaled readiness to systemd
Feb 17 08:04:28.000 [notice] Opening Socks listener on /var/run/tor/socks
Feb 17 08:04:28.000 [notice] Opening Control listener on /var/run/tor/control
Feb 17 08:04:28.000 [notice] Bootstrapped 85%: Finishing handshake with first 
hop
Feb 17 08:06:41.000 [notice] Tried for 120 seconds to get a connection to 
[scrubbed]:2000. Giving up. (waiting for rendezvous desc)
Feb 17 08:06:42.000 [notice] No circuits are opened. Relaxed timeout for 
circuit 1 (a General-purpose client 1-hop circuit in state doing handshakes 
with channel state open) to 133150ms. However, it appears the circuit has timed 
out anyway. 2 guards are live.
--

And so it doesn't work. I have had recently problems with my
university censoring Tor connections (e.g. Tor browser needs to have
bridges otherwise it doesn't work), but I don't get why tor run as a
normal user works but not as a daemon. This might not be a bug, but I
will let you decide.

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

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

Versions of packages tor depends on:
ii  adduser  3.115
ii  init-system-helpers  1.47
ii  libc62.24-9
ii  libevent-2.0-5   2.0.21-stable-2.1
ii  libseccomp2  2.3.1-2.1
ii  libssl1.11.1.0d-2
ii  libsystemd0  232-15
ii  lsb-base 9.20161125
ii  zlib1g   1:1.2.8.dfsg-5

Versions of packages tor recommends:
ii  logrotate3.11.0-0.1
ii  tor-geoipdb  0.2.9.9-1
ii  torsocks 2.2.0-1

Versions of packages tor suggests:
pn  apparmor-utils   
pn  mixmaster
pn  obfs4proxy   
pn  obfsproxy
ii  socat1.7.3.1-2
pn  tor-arm  
pn  torbrowser-launcher  

-- Configuration Files:
/etc/tor/torrc changed [not 

Bug#803902: marked as done (tor: Consider adding debconf question to select operating mode)

[Debian Bug Tracking System]

Your message dated Fri, 7 Jul 2017 07:43:02 +
with message-id <20170707074302.zpg74r24h2tke...@sarek.noreply.org>
and subject line Re: Bug#803902: tor: Consider adding debconf question to 
select operating mode
has caused the Debian Bug report #803902,
regarding tor: Consider adding debconf question to select operating mode
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.)


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

For FreedomBox, we are configuring Tor to run as a bridge relay. But I
think it
would be better if Tor can do basic configuration itself, for different
modes of
operation. And make these common configurations easily available to all
Debian
users.

What I propose is a single debconf question like "How should Tor run?" with
multiselect choices of client-only, relay, or bridge relay. Then Tor would
enable options in torrc, with appropriate choices for that selection. This
would be the basic configuration that works for most users running in the
selected mode.

--
James Valleroy



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
On Mon, 02 Nov 2015, James Valleroy wrote:

> For FreedomBox, we are configuring Tor to run as a bridge relay. But I
> think it would be better if Tor can do basic configuration itself, for
> different modes of operation. And make these common configurations
> easily available to all Debian users.
> 
> What I propose is a single debconf question like "How should Tor run?" with
> multiselect choices of client-only, relay, or bridge relay. Then Tor would
> enable options in torrc, with appropriate choices for that selection. This
> would be the basic configuration that works for most users running in the
> selected mode.

I don't think adding the complexity of debconf interaction is a good
idea.

Maybe now with multiple instance support, this has become easier for
FreedomBox to solve in some other way.

-- 
|  .''`.   ** Debian **
  Peter Palfrader   | : :' :  The  universal
 https://www.palfrader.org/ | `. `'  Operating System
|   `-https://www.debian.org/--- End Message ---

Bug#627639: marked as done (Please suggest Tor instead of depending on it)

[Debian Bug Tracking System]

Your message dated Fri, 7 Jul 2017 07:41:18 +
with message-id <20170707074118.qnosnvbgkew5l...@sarek.noreply.org>
and subject line Re: Bug#627639: Please suggest Tor instead of depending on it
has caused the Debian Bug report #627639,
regarding Please suggest Tor instead of depending on it
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.)


-- 
627639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627639
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Package: tor-geoipdb
Version: 0.2.1.30-1

Please consider having tor-geoipdb suggest or recommend tor instead of
depending on it. I would like to depend on this package but not have tor
forcefully pulled in.

Thank you,

- -- 
Kill Your TV
GPG Key 0xDF0A0A1A 
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)

iQEcBAEBAgAGBQJN2YeZAAoJEKvgwxnfCgoatooH/0u2XE1OJebM4EfgWvvlJnaY
TwTvtLql+IxCCHjY8NhFQeQq8fQywFRc18HTpiE/rlwhUeHLeJxnPPGxs96CvLfq
Yu1FReg8fhqm+7hudgDtokpHAYxl5kNLQ8aGdeOQReBHkBBbY/Ddu5mjJE1hRt+J
7bPcasV2e9T5HWDvmReJSzeex9PvprWugzBHO6ZxAkCtRJ8+PpZBot4TNUaGshS5
VyGU//8CQSsfQH5icfNso21tbjl5VlC7wT/F1S9IFGr/rYBigFbuTk3Xt7Ijfxv0
1rE+VJCr/h/gc5On2oLBrYx8vlGy3HQk077rfOOCIYeiY+5Ux4lsvIo/sHR1sAI=
=EgoZ
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
On Tue, 24 May 2011, Kill Your TV wrote:

> > Can you please provide some more rational as to what you are trying to
> > do?
> 
> Certainly. I'm packaging the I2P router (http://www.i2p2.de) and it
> ships a file called geoip.txt which is binary compatible with the file
> in the package tor-geoipdb. 

I'm uneasy about dropping the strict dependency as it might cause
versions to drift out of sync.

So probably not doing this.

Cheers,
-- 
|  .''`.   ** Debian **
  Peter Palfrader   | : :' :  The  universal
 https://www.palfrader.org/ | `. `'  Operating System
|   `-https://www.debian.org/--- End Message ---

Bug#802521: marked as done (tor: Tor service won't start)

[Debian Bug Tracking System]

Your message dated Fri, 7 Jul 2017 07:38:05 +
with message-id <20170707073805.g5fxcyg7hxiqn...@sarek.noreply.org>
and subject line Re: Bug#802521: tor: Tor service won't start
has caused the Debian Bug report #802521,
regarding tor: Tor service won't start
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.)


-- 
802521: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802521
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tor
Version: 0.2.7.3-rc-1
Severity: important

Dear Maintainer,

Tor service won't start at all. Jessie version reported "Something or somebody 
made /var/log/tor disappear." and did not start. So I've upgraded for 
experimental / does not start as well.


-- Logs begin at Út 2015-10-20 14:05:48 CEST, end at Út 2015-10-20 20:48:43 
CEST. --
říj 20 20:48:43 icerock install[12762]: /usr/bin/install: cannot change owner 
and permissions of „02750“: Adresář nebo soubor neexistuje
říj 20 20:48:43 icerock systemd[1]: tor.service: control process exited, 
code=exited status=1
říj 20 20:48:43 icerock systemd[1]: Failed to start Anonymizing overlay network 
for TCP.
-- Subject: Unit tor.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit tor.service has failed.
-- 
-- The result is failed.
říj 20 20:48:43 icerock systemd[1]: Unit tor.service entered failed state.
říj 20 20:48:43 icerock systemd[1]: tor.service holdoff time over, scheduling 
restart.
říj 20 20:48:43 icerock systemd[1]: Stopping Anonymizing overlay network for 
TCP...
-- Subject: Unit tor.service has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit tor.service has begun shutting down.
říj 20 20:48:43 icerock systemd[1]: Starting Anonymizing overlay network for 
TCP...
-- Subject: Unit tor.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit tor.service has begun starting up.
říj 20 20:48:43 icerock systemd[1]: tor.service start request repeated too 
quickly, refusing to start.
říj 20 20:48:43 icerock systemd[1]: Failed to start Anonymizing overlay network 
for TCP.
-- Subject: Unit tor.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit tor.service has failed.
-- 
-- The result is failed.
říj 20 20:48:43 icerock systemd[1]: Unit tor.service entered failed state.




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

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

Versions of packages tor depends on:
ii  adduser  3.113+nmu3
ii  init-system-helpers  1.20
ii  libc62.19-7
ii  libevent-2.0-5   2.0.21-stable-1
ii  libseccomp2  2.2.3-2
ii  libssl1.0.0  1.0.2d-1
ii  libsystemd0  215-5+b1
ii  lsb-base 4.1+Debian13
ii  zlib1g   1:1.2.8.dfsg-1

Versions of packages tor recommends:
ii  logrotate3.8.7-1
ii  tor-geoipdb  0.2.7.3-rc-1
ii  torsocks 2.1.0-1

Versions of packages tor suggests:
pn  apparmor-utils   
pn  mixmaster
pn  obfs4proxy   
pn  obfsproxy
pn  socat
ii  tor-arm  1.4.5.0-1.1
pn  torbrowser-launcher  

-- no debconf information
--- End Message ---
--- Begin Message ---
On Wed, 01 Jun 2016, Peter Palfrader wrote:

> I'd like to try to get to the bottom of this.
> 
> Does tor still refuse to start?

Seems user went away and issue was not reproducible.

Closing for now.  Please file new bugs if similar issues are observed
again.
-- 
|  .''`.   ** Debian **
  Peter Palfrader   | : :' :  The  universal
 https://www.palfrader.org/ | `. `'  Operating System
|   `-https://www.debian.org/--- End Message ---

Bug#808296: marked as done (tor: Latest version doesn't start)

[Debian Bug Tracking System]

Your message dated Fri, 7 Jul 2017 07:36:59 +
with message-id <20170707073659.acjkdhuyi7dmr...@sarek.noreply.org>
and subject line Re: Bug#808296: tor: Latest version doesn't start
has caused the Debian Bug report #808296,
regarding tor: Latest version doesn't start
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.)


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

On a fresh unstable installation tor refuses to do anything. The situation
seems to be different from #802521, hence a new bug report. If it turns out to
be the same bug, feel free to merge.

Dez 18 13:16:08 feivel tor[1349]: Dec 18 13:16:08.001 [notice] Read 
configuration file "/usr/share/tor/tor-service-defaults-torrc".
Dez 18 13:16:08 feivel systemd[1356]: tor@default.service: Failed at step 
APPARMOR spawning /usr/bin/tor: No such file or directory
Dez 18 13:16:08 feivel systemd[1]: tor@default.service: Main process exited, 
code=exited, status=231/APPARMOR
Dez 18 13:16:08 feivel systemd[1]: tor@default.service: Unit entered failed 
state.
Dez 18 13:16:08 feivel systemd[1]: tor@default.service: Failed with result 
'exit-code'.
Dez 18 13:16:08 feivel systemd[1]: tor@default.service: Service hold-off time 
over, scheduling restart.

Manually downgrading to 0.2.5.12-1 solved the problem for now.

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

Kernel: Linux 4.4.0-rc4-next-20151211-1.g34634ae-vanilla (SMP w/4 CPU cores; 
PREEMPT)
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 tor depends on:
ii  adduser 3.113+nmu3
ii  libc6   2.21-4
ii  libevent-2.0-5  2.0.21-stable-2+b1
ii  libseccomp2 2.2.3-2
ii  libssl1.0.0 1.0.2d-1
ii  lsb-base9.20150917
ii  zlib1g  1:1.2.8.dfsg-2+b1

Versions of packages tor recommends:
ii  logrotate3.8.7-2
ii  tor-geoipdb  0.2.5.12-1
ii  torsocks 2.1.0-1

Versions of packages tor suggests:
pn  apparmor-utils 
pn  mixmaster  
pn  obfsproxy  
pn  polipo | privoxy   
pn  socat  
pn  tor-arm
pn  xul-ext-torbutton  

-- no debconf information
--- End Message ---
--- Begin Message ---
On Fri, 18 Dec 2015, Michael Meskes wrote:

> On a fresh unstable installation tor refuses to do anything. The situation
> seems to be different from #802521, hence a new bug report. If it turns out to
> be the same bug, feel free to merge.

I think this might have been due to a bug in the apparmor debhelper not
correctly enabling policies.

If this issue re-appears, please file a new bug.

As it stands, I am not currently able to reproduce this, so this ticket
is not really actionable.

Thanks,
weasel
-- 
|  .''`.   ** Debian **
  Peter Palfrader   | : :' :  The  universal
 https://www.palfrader.org/ | `. `'  Operating System
|   `-https://www.debian.org/--- End Message ---

Bug#849845: marked as done (dirmngr: Can't resolve keyserver hostname anymore)

[Debian Bug Tracking System]

Your message dated Fri, 7 Jul 2017 07:33:20 +
with message-id <20170707073320.e7d73mxcvfkwk...@sarek.noreply.org>
and subject line fixed with Tor 0.3.0.3-alpha
has caused the Debian Bug report #849845,
regarding dirmngr: Can't resolve keyserver hostname anymore
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.)


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

Hi!

since the upgrade to 2.1.17 (not sure if it's in -1 or -2), my dirmngr
is unusable. Any network operation triggers:

  can't connect to 'hkps.pool.sks-keyservers.net': no IP address for host

... almost immediately, i.e. resolver-timeout seems to be ignored.

I've tried multiple combinations of the following settings in
dirmngr.conf:

 * disabling "use-tor"
 * enabling "standard-resolver"
 * pointing "nameserver" to 127.0.0.1 (my Tor DNSPort, that only
   listens on UDP 127.0.0.1:53)
 * pointing "nameserver" to 8.8.8.8 (which should be the default
   given I have "use-tor" enabled, but well)
 * raising the value of "resolver-timeout"

… but none of them helped.

Downgrading to 2.1.16-3 fixes this problem.

The only weird thing about my system that I can think of is that my
/etc/resolv.conf points to 127.0.0.1 (where I have Tor's DNSPort
listening, that only handles A, , and PTR requests). In theory
this should not matter since with use-tor, DNS queries are done over
Tor to 8.8.8.8, if I got the manpage right. However, my limited strace
skills allow me to notice that dirmngr reads /etc/resolv.conf and then
connects to 127.0.0.1 and not to 8.8.8.8 (even if I explicitly set
"nameserver 8.8.8.8" in dirmngr.conf):

  23694 10:51:07.455096 socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 
IPPROTO_IP) = 6 <0.15>
  23694 10:51:07.455145 bind(6, {sa_family=AF_INET, sin_port=htons(53891), 
sin_addr=inet_addr("0.0.0.0")}, 16) = 0 <0.07>
  23694 10:51:07.455196 connect(6, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("127.0.0.1")}, 16) = 0 <0.09>
  23694 10:51:07.455218 sendto(6, 
"\250\302\1\0\0\1\0\0\0\0\0\0\4hkps\4pool\16sks-keyse"..., 46, 0, NULL, 0) = 46 
<0.39>
   | 0  a8 c2 01 00 00 01 00 00  00 00 00 00 04 68 6b 70  .hkp |
   | 00010  73 04 70 6f 6f 6c 0e 73  6b 73 2d 6b 65 79 73 65  s.pool.sks-keyse |
   | 00020  72 76 65 72 73 03 6e 65  74 00 00 01 00 01rvers.net.   |
  23694 10:51:07.455298 recvfrom(6, 0x7fda90009d4c, 768, 0, NULL, NULL) = -1 
EAGAIN (Resource temporarily unavailable) <0.04>
  23694 10:51:07.455318 select(7, [6], [], NULL, {tv_sec=1, tv_usec=0}) = 1 (in 
[6], left {tv_sec=0, tv_usec=922029}) <0.077993>
  23694 10:51:07.533390 recvfrom(6, 
"\250\302\201\200\0\1\0\1\0\0\0\0\4hkps\4pool\16sks-keyse"..., 768, 0, NULL, 
NULL) = 62 <0.32>
   | 0  a8 c2 81 80 00 01 00 01  00 00 00 00 04 68 6b 70  .hkp |
   | 00010  73 04 70 6f 6f 6c 0e 73  6b 73 2d 6b 65 79 73 65  s.pool.sks-keyse |
   | 00020  72 76 65 72 73 03 6e 65  74 00 00 01 00 01 c0 0c  rvers.net... |
   | 00030  00 01 00 01 00 00 00 3c  00 04 d1 87 d3 8d...<..   |
  23694 10:51:07.533551 connect(6, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("127.0.0.1")}, 16) = 0 <0.41>
  23694 10:51:07.533627 sendto(6, 
"\3601\1\0\0\1\0\0\0\0\0\0\4hkps\4pool\16sks-keyse"..., 46, 0, NULL, 0) = 46 
<0.46>
   | 0  f0 31 01 00 00 01 00 00  00 00 00 00 04 68 6b 70  .1...hkp |
   | 00010  73 04 70 6f 6f 6c 0e 73  6b 73 2d 6b 65 79 73 65  s.pool.sks-keyse |
   | 00020  72 76 65 72 73 03 6e 65  74 00 00 1c 00 01rvers.net.   |
  23694 10:51:07.533720 recvfrom(6, 0x7fda9000a10c, 768, 0, NULL, NULL) = -1 
EAGAIN (Resource temporarily unavailable) <0.10>
  23694 10:51:07.533763 select(7, [6], [], NULL, {tv_sec=1, tv_usec=0}) = 1 (in 
[6], left {tv_sec=0, tv_usec=921164}) <0.078863>
  23694 10:51:07.612705 recvfrom(6, 
"\3601\201\203\0\1\0\0\0\0\0\0\4hkps\4pool\16sks-keyse"..., 768, 0, NULL, NULL) 
= 46 <0.22>
   | 0  f0 31 81 83 00 01 00 00  00 00 00 00 04 68 6b 70  .1...hkp |
   | 00010  73 04 70 6f 6f 6c 0e 73  6b 73 2d 6b 65 79 73 65  s.pool.sks-keyse |
   | 00020  72 76 65 72 73 03 6e 65  74 00 00 1c 00 01rvers.net.   |
  23694 10:51:07.612832 connect(6, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("127.0.0.1")}, 16) = 0 <0.14>
  23694 10:51:07.612894 sendto(6, 
"\224J\1\0\0\1\0\0\0\0\0\0\4hkps\4pool\16sks-keyse"..., 47, 0, NULL, 0) = 47 
<0.49>
   | 

Bug#851798: marked as done (tor: IPv6 connections through tor do not appear to work)

[Debian Bug Tracking System]

Your message dated Fri, 7 Jul 2017 07:33:20 +
with message-id <20170707073320.e7d73mxcvfkwk...@sarek.noreply.org>
and subject line fixed with Tor 0.3.0.3-alpha
has caused the Debian Bug report #849845,
regarding tor: IPv6 connections through tor do not appear to work
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.)


-- 
849845: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849845
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tor
Version: 0.3.0.1-alpha-1
Severity: normal
Control: block 849845 with -1
Control: affects -1 dirmgnr

consider the following two commands:

curl --socks5-hostname 127.0.0.1:9050 http://www.google.com

curl --socks5-hostname 127.0.0.1:9050 http://ipv6.google.com


www.google.com has A and  records.

ipv6.google.com has only  records.

the first command shows me the body of the 302 redirection.

the second command sends this line to stderr:

curl: (7) Can't complete SOCKS5 connection to 0.0.0.0:0. (4)

and returns error code 7.

afaict, this is true for every connection to an IPv6 address through
tor.

I'm not sure how to debug, but this appears to be what's causing the
tor+ipv6 failures for dirmngr over on https://bugs.debian.org/849845,
so i'm marking this as blocking that bug.

Any suggestions for debugging?  can you reproduce the problem?  Should
i be trying to do this some other way?

  --dkg


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

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

Versions of packages tor depends on:
ii  adduser  3.115
ii  init-system-helpers  1.46
ii  libc62.24-8
ii  libevent-2.0-5   2.0.21-stable-2.1
ii  libseccomp2  2.3.1-2.1
ii  libssl1.11.1.0c-2
ii  libsystemd0  232-8
ii  lsb-base 9.20161125
ii  zlib1g   1:1.2.8.dfsg-4

Versions of packages tor recommends:
pn  logrotate
ii  tor-geoipdb  0.2.9.8-2
ii  torsocks 2.2.0-1

Versions of packages tor suggests:
pn  apparmor-utils   
pn  mixmaster
pn  obfs4proxy   
pn  obfsproxy
ii  socat1.7.3.1-2
pn  tor-arm  
ii  torbrowser-launcher  0.2.6-3

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.3.0.3-alpha-1

This should have been fixed in February with

| o Minor feature (client):
|   - Enable IPv6 traffic on the SocksPort by default. To disable this,
| a user will have to specify "NoIPv6Traffic". Closes ticket 21269.

Cheers,
-- 
|  .''`.   ** Debian **
  Peter Palfrader   | : :' :  The  universal
 https://www.palfrader.org/ | `. `'  Operating System
|   `-https://www.debian.org/--- End Message ---

Bug#850606: marked as done (dirmngr: can't resolve ipv6 addresses when use-tor is enabled)

[Debian Bug Tracking System]

Your message dated Fri, 7 Jul 2017 07:33:20 +
with message-id <20170707073320.e7d73mxcvfkwk...@sarek.noreply.org>
and subject line fixed with Tor 0.3.0.3-alpha
has caused the Debian Bug report #849845,
regarding dirmngr: can't resolve ipv6 addresses when use-tor is enabled
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.)


-- 
849845: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849845
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dirmngr
Version: 2.1.17-3
Severity: important

Dear Maintainer,

 Failure case:
$ gpg --recv-keys 0x
gpg: keyserver receive failed: Invalid argument

2017-01-08 13:26:07 dirmngr[5394] listening on socket 
'/run/user/1000/gnupg/S.dirmngr'
2017-01-08 13:26:07 dirmngr[5395.0] permanently loaded certificates: 0
2017-01-08 13:26:07 dirmngr[5395.0] runtime cached certificates: 0
2017-01-08 13:26:08 dirmngr[5395.6] handler for fd 6 started
2017-01-08 13:26:08 dirmngr[5395.6] DBG: chan_6 -> # Home: 
/home/infinity0/.gnupg
2017-01-08 13:26:08 dirmngr[5395.6] DBG: chan_6 -> # Config: 
/home/infinity0/.gnupg/dirmngr.conf
2017-01-08 13:26:08 dirmngr[5395.6] DBG: chan_6 -> OK Dirmngr 2.1.17 at your 
service
2017-01-08 13:26:08 dirmngr[5395.6] connection from process 5390 (1000:1000)
2017-01-08 13:26:08 dirmngr[5395.6] DBG: chan_6 <- GETINFO version
2017-01-08 13:26:08 dirmngr[5395.6] DBG: chan_6 -> D 2.1.17
2017-01-08 13:26:08 dirmngr[5395.6] DBG: chan_6 -> OK
2017-01-08 13:26:08 dirmngr[5395.6] DBG: chan_6 <- KS_GET -- 0x
2017-01-08 13:26:08 dirmngr[5395.6] DBG: dns: libdns initialized (tor mode)
2017-01-08 13:26:11 dirmngr[5395.6] DBG: dns: 
getsrv(_hkp._tcp.pool.sks-keyservers.net) -> 0 records
2017-01-08 13:26:11 dirmngr[5395.6] DBG: dns: libdns initialized (tor mode)
2017-01-08 13:26:12 dirmngr[5395.6] DBG: dns: 
resolve_dns_name(pool.sks-keyservers.net): Success
2017-01-08 13:26:12 dirmngr[5395.6] resolve_dns_addr for 
'pool.sks-keyservers.net': ...
2017-01-08 13:26:12 dirmngr[5395.6] resolve_dns_addr for 
'pool.sks-keyservers.net': '[2a01:4f8:161:4283:1000::203]'
2017-01-08 13:26:12 dirmngr[5395.6] resolve_dns_addr for 
'pool.sks-keyservers.net': ...
2017-01-08 13:26:12 dirmngr[5395.6] number of system provided CAs: 173
2017-01-08 13:26:12 dirmngr[5395.6] DBG: dns: 
resolve_dns_name(2a01:4f8:161:4283:1000::203): Success
2017-01-08 13:26:12 dirmngr[5395.6] can't connect to 
'2a01:4f8:161:4283:1000::203': Invalid argument
2017-01-08 13:26:12 dirmngr[5395.6] error connecting to 
'http://[2a01:4f8:161:4283:1000::203]:11371': Invalid argument
2017-01-08 13:26:12 dirmngr[5395.6] command 'KS_GET' failed: Invalid argument
2017-01-08 13:26:12 dirmngr[5395.6] DBG: chan_6 -> ERR 167804976 Invalid 
argument 
2017-01-08 13:26:12 dirmngr[5395.6] DBG: chan_6 <- BYE
2017-01-08 13:26:12 dirmngr[5395.6] DBG: chan_6 -> OK closing connection
2017-01-08 13:26:12 dirmngr[5395.6] handler for fd 6 terminated


 Success case:
$ gpg --recv-keys 0x
gpg: key : 
gpg: Total number processed: 1
gpg:  unchanged: 1

2017-01-08 13:25:53 dirmngr[5312] listening on socket 
'/run/user/1000/gnupg/S.dirmngr'
2017-01-08 13:25:53 dirmngr[5313.0] permanently loaded certificates: 0
2017-01-08 13:25:53 dirmngr[5313.0] runtime cached certificates: 0
2017-01-08 13:25:54 dirmngr[5313.6] handler for fd 6 started
2017-01-08 13:25:54 dirmngr[5313.6] DBG: chan_6 -> # Home: 
/home/infinity0/.gnupg
2017-01-08 13:25:54 dirmngr[5313.6] DBG: chan_6 -> # Config: 
/home/infinity0/.gnupg/dirmngr.conf
2017-01-08 13:25:54 dirmngr[5313.6] DBG: chan_6 -> OK Dirmngr 2.1.17 at your 
service
2017-01-08 13:25:54 dirmngr[5313.6] connection from process 5309 (1000:1000)
2017-01-08 13:25:54 dirmngr[5313.6] DBG: chan_6 <- GETINFO version
2017-01-08 13:25:54 dirmngr[5313.6] DBG: chan_6 -> D 2.1.17
2017-01-08 13:25:54 dirmngr[5313.6] DBG: chan_6 -> OK
2017-01-08 13:25:54 dirmngr[5313.6] DBG: chan_6 <- KS_GET -- 0x
2017-01-08 13:25:54 dirmngr[5313.6] DBG: dns: libdns initialized (tor mode)
2017-01-08 13:25:57 dirmngr[5313.6] DBG: dns: 
getsrv(_hkp._tcp.pool.sks-keyservers.net) -> 0 records
2017-01-08 13:25:57 dirmngr[5313.6] DBG: dns: libdns initialized (tor mode)
2017-01-08 13:25:59 dirmngr[5313.6] DBG: dns: 
resolve_dns_name(pool.sks-keyservers.net): Success
2017-01-08 13:25:59 dirmngr[5313.6] resolve_dns_addr for 
'pool.sks-keyservers.net': ...
2017-01-08 13:25:59 dirmngr[5313.6] resolve_dns_addr for 
'pool.sks-keyservers.net': '212.51.156.78'
2017-01-08 13:25:59 dirmngr[5313.6] resolve_dns_addr for 
'pool.sks-keyservers.net': ...
2017-01-08 13:25:59 

Bug#681123: marked as done (Please document that different torify instances might use the same circuits)

[Debian Bug Tracking System]

Your message dated Fri, 7 Jul 2017 07:30:25 +
with message-id <20170707073025.eczjxqgaobojc...@sarek.noreply.org>
and subject line Re: Bug#681123: torify: Please add a paragraph in the WARNING 
section about identical identities
has caused the Debian Bug report #681123,
regarding Please document that different torify instances might use the same 
circuits
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.)


-- 
681123: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681123
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tor
Version: 0.2.3.19-rc-1
Severity: wishlist

When using multiple instances of torify on the same computer to connect to the
same host, it is possible for the according host to figure out that those two
clients are very likely the same.

While when specifically selecting a certain Tor proxy in an application,
I guess a user will very likely be aware that the same Tor identity is being
used.

However, for torify it is not that obvious that multiple instances are
_not_ necessarily using a new Tor identity. A user might think:

"It's a new torify instance, so it's probably another one of this Tor
thingies, and they say a Tor thingy is pretty anonymous, right?
(Proxies? Ain't heard of that, know idea what that is - but torify works
great. What's torify doing internally? Don't know, I'm not a Tor
developer) I have read 'man torify' and it's not saying anything about
using the same Tor identity, it'd probably have been mentioned there otherwise.
So in conclusion, I guess each torify instance has to have its own,
anonymous identity."

Maybe for now a paragraph about every torify instance sharing the
same Tor identity should be added to the torify manpage in the WARNING
section?

Later, it'd be great if in fact each torify instance were having its own
identity, but don't know how difficult it is to implement that.

Cheers

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

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

Versions of packages tor depends on:
ii  adduser 3.113+nmu3
ii  libc6   2.13-34
ii  libevent-2.0-5  2.0.19-stable-3
ii  libssl1.0.0 1.0.1c-3
ii  lsb-base4.1+Debian7
ii  zlib1g  1:1.2.7.dfsg-13

Versions of packages tor recommends:
ii  logrotate3.8.1-4
ii  tor-geoipdb  0.2.3.19-rc-1
ii  torsocks 1.2-3

Versions of packages tor suggests:
pn  apparmor-utils 
pn  mixmaster  
ii  privoxy3.0.19-2
ii  socat  1.7.1.3-1.4
pn  tor-arm
pn  xul-ext-torbutton  

-- Configuration Files:
/etc/tor/torrc changed [not included]

-- debconf-show failed


--- End Message ---
--- Begin Message ---
Peter Palfrader schrieb am Wednesday, dem 19. September 2012:

> [I have forwarded your request to https://bugs.torproject.org/6892]

The torify manpage not tells you to use torsocks.  The torsocks manpage
does mention the issue of stream isolation.

Cheers,
-- 
|  .''`.   ** Debian **
  Peter Palfrader   | : :' :  The  universal
 https://www.palfrader.org/ | `. `'  Operating System
|   `-https://www.debian.org/--- End Message ---

Bug#705388: marked as done (tordns fails to handle MX lookups)

[Debian Bug Tracking System]

Your message dated Fri, 7 Jul 2017 07:26:32 +
with message-id <20170707072632.i7wav2scnqq65...@sarek.noreply.org>
and subject line Re: Bug#705388: tordns fails to handle MX lookups
has caused the Debian Bug report #705388,
regarding tordns fails to handle MX lookups
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.)


-- 
705388: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705388
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tor
Version: 0.2.3.25-1~~squeeze+1
Severity: wishlist

Tor DNS currently has a crippling limitation of being unable to
resolve MX queries.  This limitation is severe, because there is no
workaround.  Although this report is technically a "wishlist" request,
it probably should be treated as a defect.

The torsocks package cannot compensate for this limitation, because
torsocks depends entirely on tordns.  Old versions of torsocks were
able to disable tordns, so that clients at least had the option
perform MX queries by other* means.

* (other means could be deliberate but acceptible leaks, or by using
   ttdnsd and pdnsd packages -- but these options are essentially
   blocked)

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

Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages tor depends on:
ii  adduser3.112+nmu2add and remove users and groups
ii  libc6  2.11.3-4  Embedded GNU C Library: Shared lib
ii  libevent-1.4-2 1.4.13-stable-1   An asynchronous event notification
ii  libssl0.9.80.9.8o-4squeeze14 SSL shared libraries
ii  lsb-base   3.2-23.2squeeze1  Linux Standard Base 3.2 init scrip
ii  zlib1g 1:1.2.3.4.dfsg-3  compression library - runtime

Versions of packages tor recommends:
ii  logrotate  3.7.8-6   Log rotation utility
ii  tor-geoipdb0.2.3.25-1~~squeeze+1 GeoIP database for Tor
ii  torsocks   1.0~epsilon+dfsg1-1   use socks-friendly applications wi

Versions of packages tor suggests:
pn  apparmor-utils (no description available)
ii  mixmaster  3.0.0-4   Anonymous remailer client and serv
ii  privoxy3.0.16-1  Privacy enhancing HTTP Proxy
ii  socat  1.7.1.3-1 multipurpose relay for bidirection
ii  tor-arm1.4.5.0-1~squeeze terminal status monitor for tor
pn  xul-ext-torbutton  (no description available)
--- End Message ---
--- Begin Message ---
On Fri, 12 Apr 2013, Anonymous wrote:

> Tor DNS currently has a crippling limitation of being unable to
> resolve MX queries.

Tor does not really forward DNS in-protocol.  You can tunnel DNS
requests through tor, but that's not the same.

This limitation is known, and I agree that it's a shortcoming.

Nevertheless, keeping this issue active in the Debian BTS is unlikely to
change the state of things.  Thus, I'm closing this issue here.

-- 
|  .''`.   ** Debian **
  Peter Palfrader   | : :' :  The  universal
 https://www.palfrader.org/ | `. `'  Operating System
|   `-https://www.debian.org/--- End Message ---

Bug#846275: marked as done (provide a directory for hidden service socket files)

[Debian Bug Tracking System]

Your message dated Fri, 7 Jul 2017 07:23:24 +
with message-id <20170707072324.33cbc3gr3thyw...@sarek.noreply.org>
and subject line Re: Bug#846275: provide a directory for hidden service socket 
files
has caused the Debian Bug report #846275,
regarding provide a directory for hidden service socket files
to be marked as done.

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

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


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

When running a tor hidden service, it's desirable to run it as a
different user than debian-tor, and it's safer to use a unix socket than
it is to run the hidden service on a localhost port. However, when a unix
socket file is used for communication between tor and the hidden
service, there is no good location to put it in. I suggest providing
such a location.

It seems that /etc/apparmor.d/system_tor is used by default on systemd
systems -- it appears to be limiting here what tor can read, although I
don't have apparmor packages installed. In that file, tor is locked down
to only be able to access /var/lib/tor/, /var/run/tor/, and /etc/tor/

/var/lib/tor is only readable by debian-tor, so for the hidden service
  socket to be located somewhere in there, the hidden service would have
  to be run as debian-tor (user or group).

/var/run/tor is world readable, so it would be possible to make a
  subdirectory, say /var/run/tor/hidden_service/, allow the hidden service
  user to write to the subdirectory so it can bind the socket, and tor would
  be able to use it. But, /var/run does not persist across reboots, so this
  subdirectory would need to be set up on each boot by root before the
  hidden service starts up.

/etc/tor is the only other option. Indeed, /etc/tor/hidden_service/ can
  be set up to be writable by the hidden service user, it can put its
  socket there, and tor can read it. But putting a socket in /etc/ is
  a FHS violation.

I am using tor hidden services for P2P communication between git-annex
repositories. The user runs a command as root once to set up the hidden
service for their repository. So my current choices to integrate this
with Debian's tor package are:

* Violate the FHS by putting a non-config file in /etc/tor/
* Modify the apparmor config shipped with tor to let it read the socket
  in some other location. Seems this would require restarting the tor
  daemon amoung other complications.
* Add an init script that sets up subdirectories under /var/run/tor
  with appropriate owners on boot. Complicated.

So, the configuration of this package is encouraging me to violate the
FHS. It seems like the most robust and simplest way.

I suggest that the Debian tor package include a world-readable
directory, which tor is allowed to access by its apparmor config and any
other things used to lock it down. Subdirectories can then be
added as needed to contain hidden service unix sockets, etc.

(Another use case for such a world-readable directory could be
onionshare. It currently uses a HiddenServiceDir in /tmp/onionshare/, so
that it can read the onion address from it, which it could not if it
used /var/lib/tor. /etc/apparmor.d/torbrowser.Tor.tor has a special case
for that onionshare directory. This is why the onionshare package depends
on torbrowser-launcher; see #762890.)

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

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

Versions of packages tor depends on:
ii  adduser  3.115
ii  init-system-helpers  1.46
ii  libc62.24-5
ii  libevent-2.0-5   2.0.21-stable-2.1
ii  libseccomp2  2.3.1-2
ii  libssl1.0.2  1.0.2j-4
ii  libsystemd0  232-3
ii  lsb-base 9.20161101
ii  zlib1g   1:1.2.8.dfsg-2+b3

Versions of packages tor recommends:
ii  logrotate3.8.7-2
ii  tor-geoipdb  0.2.8.9-1
ii  torsocks 2.2.0-1

Versions of packages tor suggests:
pn  apparmor-utils   
pn  mixmaster
pn  obfs4proxy   
pn  obfsproxy
ii  socat1.7.3.1-1
pn  tor-arm  
ii  torbrowser-launcher  0.2.6-2

-- Configuration Files:
/etc/tor/torrc changed [not included]

-- no debconf information

-- 
see shy jo


signature.asc

Bug#732943: marked as done (please include example proxy.pac to handle *.onion domains)

[Debian Bug Tracking System]

Your message dated Fri, 7 Jul 2017 07:19:01 +
with message-id <20170707071901.kdteey7s3k5yg...@sarek.noreply.org>
and subject line Re: Bug#732943: please include example proxy.pac to handle 
*.onion domains
has caused the Debian Bug report #732943,
regarding please include example proxy.pac to handle *.onion domains
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.)


-- 
732943: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=732943
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tor
Version: 0.2.3.25-1
Severity: wishlist

This might be useful when one wants to use tor for the only purpose
of accessing *.onion domains.

This could happen because user isn't concerned about his own anonimity
in this particular session, but nevertheless wants to access a service
which has been banned by a totalitarian regime.

A typical example would be http://jntlesnev5o7zysa.onion/ which
doesn't necessarily involve any unlawful activity, but is regardless
often censored by authorities.

If it was provided somewhere in the system (e.g. /usr/share/doc or
/etc), user could enable it right away by pointing his proxy.pac URL
to it using "file://" prefix.

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

Kernel: kFreeBSD 9.0-2-amd64
Locale: LANG=ca_AD.UTF-8, LC_CTYPE=ca_AD.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
function FindProxyForURL (url, host)
{
if (shExpMatch (host,"*.onion"))
{
return "SOCKS 127.0.0.1:9050";
}
return "DIRECT";
}
--- End Message ---
--- Begin Message ---
On Sun, 22 Dec 2013, Robert Millan wrote:

> This might be useful when one wants to use tor for the only purpose
> of accessing *.onion domains.
> 
> This could happen because user isn't concerned about his own anonimity
> in this particular session, but nevertheless wants to access a service
> which has been banned by a totalitarian regime.

I agree that this can be a useful and valid proxy setting, but since we
recommend people not use Tor stand-alone for webbrowsing, I think we
shouldn't do this.

Cheers,
-- 
|  .''`.   ** Debian **
  Peter Palfrader   | : :' :  The  universal
 https://www.palfrader.org/ | `. `'  Operating System
|   `-https://www.debian.org/--- End Message ---

Processed: closing 864517

[Debian Bug Tracking System]

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

> close 864517 3.6.2+dfsg-1
Bug #864517 [src:yara] CVE-2017-9465
Bug #865782 [src:yara] yara: CVE-2017-9465
Marked as fixed in versions yara/3.6.2+dfsg-1.
Marked as fixed in versions yara/3.6.2+dfsg-1.
Bug #864517 [src:yara] CVE-2017-9465
Bug #865782 [src:yara] yara: CVE-2017-9465
Marked Bug as done
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#867492: marked as done (xorg-server: CVE-2017-10971 CVE-2017-10972)

[Debian Bug Tracking System]

Your message dated Fri, 07 Jul 2017 06:04:14 +
with message-id 
and subject line Bug#867492: fixed in xorg-server 2:1.19.3-2
has caused the Debian Bug report #867492,
regarding xorg-server: CVE-2017-10971 CVE-2017-10972
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.)


-- 
867492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867492
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xorg-server
Version: 2:1.16.4-1
Severity: grave
Tags: upstream patch security
Justification: user security hole

Hi,

the following vulnerabilities were published for xorg-server, filling
the bug to track it int the BTS.

CVE-2017-10971[0]:
| In the X.Org X server before 2017-06-19, a user authenticated to an X
| Session could crash or execute code in the context of the X Server by
| exploiting a stack overflow in the endianness conversion of X Events.

CVE-2017-10972[1]:
| Uninitialized data in endianness conversion in the XEvent handling of
| the X.Org X Server before 2017-06-19 allowed authenticated malicious
| users to access potentially privileged data from the X server.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-10971
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10971
[1] https://security-tracker.debian.org/tracker/CVE-2017-10972
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-10972
[2] https://bugzilla.suse.com/show_bug.cgi?id=1035283

Could you please check back with team@s.d.o if those warrant a DSA.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: xorg-server
Source-Version: 2:1.19.3-2

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

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

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

Debian distribution maintenance software
pp.
Julien Cristau  (supplier of updated xorg-server 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: Fri, 07 Jul 2017 07:31:11 +0200
Source: xorg-server
Binary: xserver-xorg-core xserver-xorg-core-udeb xserver-xorg-dev xdmx 
xdmx-tools xnest xvfb xserver-xephyr xserver-common xorg-server-source xwayland 
xserver-xorg-legacy
Architecture: source
Version: 2:1.19.3-2
Distribution: unstable
Urgency: high
Maintainer: Debian X Strike Force 
Changed-By: Julien Cristau 
Description:
 xdmx   - distributed multihead X server
 xdmx-tools - Distributed Multihead X tools
 xnest  - Nested X server
 xorg-server-source - Xorg X server - source files
 xserver-common - common files used by various X servers
 xserver-xephyr - nested X server
 xserver-xorg-core - Xorg X server - core server
 xserver-xorg-core-udeb - Xorg X server - core server (udeb)
 xserver-xorg-dev - Xorg X server - development files
 xserver-xorg-legacy - setuid root Xorg server wrapper
 xvfb   - Virtual Framebuffer 'fake' X server
 xwayland   - Xwayland X server
Closes: 867492
Changes:
 xorg-server (2:1.19.3-2) unstable; urgency=high
 .
   * CVE-2017-10972: information leak out of the X server due to an
 uninitialized stack area when swapping:
 - Xi: Zero target buffer in SProcXSendExtensionEvent
   * CVE-2017-10971: stack overflow due to missing GenericEvent handling in
 XSendEvent:
 - dix: Disallow GenericEvent in SendEvent request
 - Xi: Verify all events in ProcXSendExtensionEvent
 - Xi: Do not try to swap GenericEvent
   * With both those fixes, this closes: #867492
Checksums-Sha1:
 7e66cc3ec78d67e7776e44db1505d7f7d90bbeb8 4815 xorg-server_1.19.3-2.dsc
 bc90bf9b9bef5e1583c53dd72fd39f062c5404f7 139662 xorg-server_1.19.3-2.diff.gz
Checksums-Sha256:
 b12e94496dd2cb00d75170be13276dd29361ef8f9dd5f4b918db636476355e63 4815 
xorg-server_1.19.3-2.dsc
 743dca1680e454b2e166fdd2a5e36ca09145bbbd939503b791c74914eeb4603f 139662 
xorg-server_1.19.3-2.diff.gz
Files:
 9b309c48911de10dab1277c4871e237d 4815 x11 optional