Bug#867037: marked as done (python-txaio FTBFS: test_chained_callback[asyncio] failed)

[Debian Bug Tracking System]

Your message dated Wed, 19 Jul 2017 06:49:03 +
with message-id 
and subject line Bug#867037: fixed in python-txaio 2.8.0-0.1
has caused the Debian Bug report #867037,
regarding python-txaio FTBFS: test_chained_callback[asyncio] failed
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.)


-- 
867037: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867037
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-txaio
Version: 2.5.1+2016.10.03.git.623ef68776-1
Severity: serious
Tags: buster sid

Some recent change in unstable makes python-txaio FTBFS:

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

...
test/test_is_future.py .
test/test_legacy_logging.py .
test/test_logging.py ..

=== FAILURES ===
 test_chained_callback[asyncio] 

framework = 

def test_chained_callback(framework):
"""
Chain two callbacks where the first one alters the value.
"""
calls = []

def callback0(arg):
calls.append(arg)
return arg + " pray I do not alter it futher"

def callback1(arg):
calls.append(arg)

f = txaio.create_future()
txaio.add_callbacks(f, callback0, None)
txaio.add_callbacks(f, callback1, None)
txaio.resolve(f, "the deal")

run_once()

assert len(calls) == 2
assert calls[0] == "the deal"
>   assert calls[1] == "the deal pray I do not alter it futher"
E   assert 'the deal' == 'the deal pray I do not alter it futher'
E - the deal
E + the deal pray I do not alter it futher

test/test_callback.py:84: AssertionError
 pytest-warning summary 
WC1 
/build/1st/python-txaio-2.5.1+2016.10.03.git.623ef68776/test/test_logging.py 
cannot collect test class 'TestHandler' because it has a __init__ constructor
== 1 failed, 99 passed, 2 skipped, 1 pytest-warnings in 2.68 seconds ===
debian/rules:14: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
--- End Message ---
--- Begin Message ---
Source: python-txaio
Source-Version: 2.8.0-0.1

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 19 Jul 2017 08:32:33 +0200
Source: python-txaio
Binary: python-txaio python3-txaio python-txaio-doc
Architecture: source
Version: 2.8.0-0.1
Distribution: unstable
Urgency: medium
Maintainer: PKG OpenStack 
Changed-By: Gianfranco Costamagna 
Description:
 python-txaio - compatibility API between asyncio/Twisted/Trollius - Python 2.x
 python-txaio-doc - compatibility API between asyncio/Twisted/Trollius - doc
 python3-txaio - compatibility API between asyncio/Twisted/Trollius - Python 3.x
Closes: 867037
Changes:
 python-txaio (2.8.0-0.1) unstable; urgency=medium
 .
   [ Gianfranco Costamagna ]
   * Non-maintainer upload.
   * Drop useless, conflicting usr/LICENSE file in both binary packages.
   * Update copyright year and author
   * Update watch file.
 .
   [ Michael Hudson-Doyle ]
   * New upstream release (Closes: #867037).
   * d/control: drop build-dependency/dependency on python3-trollius.
   * d/patches/remove-privacy-breach-in-docs.patch: regenerate.
Checksums-Sha1:
 bed96707ca2f9e027482fac52366cef7c9b03487 2485 python-txaio_2.8.0-0.1.dsc
 a3ff00bae6d154cdf07ae2c009a9ffa8fddbb72e 43521 python-txaio_2.8.0.orig.tar.gz
 0f9758382e2af05d8aea0921ea165e9e2e2fe26c 4212 
python-txaio_2.8.0-0.1.debian.tar.xz
Checksums-Sha256:
 61af55109d63011c30cc897acfcea694a1c705fcb585d9859a622b71b8522391 2485 
python-txaio_2.8.0-0.1.dsc
 8029d956591107ff9a2221d2a28

Bug#860739: libghc-xcb-types-dev: cannot parse xcb-proto 1.12

[Iain R. Learmonth]

Hi,

On 07/19/2017 04:49 AM, Clint Adams wrote:

On Sun, Apr 23, 2017 at 01:22:33PM +0100, James Cowgill wrote:

It looks like the xcffib dependency from cairocffi is optional, so this
would be a much easier solution. Otherwise we have to backport tons of
stuff or use upstream 0.5.1.


So does this mean this is no longer a bug?


xcffib is now building the latest upstream in unstable successfully and 
the test suite is passing, the test suite for qtile (which uses xcffib) 
is also passing.


It would look that this is no longer a bug.

Thanks,
Iain.

Bug#867037: python-txaio FTBFS: test_chained_callback[asyncio] failed

[Gianfranco Costamagna]

control: tags -1 patch pending
> Some recent change in unstable makes python-txaio FTBFS:
> 

NMU and diffs from Ubuntu attached.
This new release fixed the Ubuntu build issues and should be ready also for 
Python 3.6

G.

diff -Nru python-txaio-2.5.1+2016.10.03.git.623ef68776/debian/changelog 
python-txaio-2.8.0/debian/changelog
--- python-txaio-2.5.1+2016.10.03.git.623ef68776/debian/changelog   
2016-10-13 19:51:07.0 +0200
+++ python-txaio-2.8.0/debian/changelog 2017-07-19 08:32:33.0 +0200
@@ -1,3 +1,18 @@
+python-txaio (2.8.0-0.1) unstable; urgency=medium
+
+  [ Gianfranco Costamagna ]
+  * Non-maintainer upload.
+  * Drop useless, conflicting usr/LICENSE file in both binary packages.
+  * Update copyright year and author
+  * Update watch file.
+
+  [ Michael Hudson-Doyle ]
+  * New upstream release (Closes: #867037).
+  * d/control: drop build-dependency/dependency on python3-trollius.
+  * d/patches/remove-privacy-breach-in-docs.patch: regenerate.
+
+ -- Gianfranco Costamagna   Wed, 19 Jul 2017 
08:32:33 +0200
+
 python-txaio (2.5.1+2016.10.03.git.623ef68776-1) unstable; urgency=medium
 
   * New upstream release based on commit 623ef68776:
diff -Nru python-txaio-2.5.1+2016.10.03.git.623ef68776/debian/control 
python-txaio-2.8.0/debian/control
--- python-txaio-2.5.1+2016.10.03.git.623ef68776/debian/control 2016-10-13 
19:51:07.0 +0200
+++ python-txaio-2.8.0/debian/control   2017-07-19 08:32:33.0 +0200
@@ -24,7 +24,6 @@
  python3-mock (>= 1.3),
  python3-pytest,
  python3-six,
- python3-trollius,
  python3-twisted,
  python3-zope.interface,
 Standards-Version: 3.9.8
@@ -55,7 +54,6 @@
 Package: python3-txaio
 Architecture: all
 Depends: python3-six,
- python3-trollius,
  python3-twisted,
  python3-zope.interface,
  ${misc:Depends},
diff -Nru python-txaio-2.5.1+2016.10.03.git.623ef68776/debian/copyright 
python-txaio-2.8.0/debian/copyright
--- python-txaio-2.5.1+2016.10.03.git.623ef68776/debian/copyright   
2016-10-13 19:51:07.0 +0200
+++ python-txaio-2.8.0/debian/copyright 2017-07-19 08:28:26.0 +0200
@@ -3,7 +3,7 @@
 Source: https://github.com/tavendo/txaio
 
 Files: *
-Copyright: (c) 2015, Tavendo GmbH 
+Copyright: (c) 2015 Crossbar.io Technologies GmbH
 License: Expat
 
 Files: debian/*
diff -Nru 
python-txaio-2.5.1+2016.10.03.git.623ef68776/debian/patches/remove-privacy-breach-in-docs.patch
 python-txaio-2.8.0/debian/patches/remove-privacy-breach-in-docs.patch
--- 
python-txaio-2.5.1+2016.10.03.git.623ef68776/debian/patches/remove-privacy-breach-in-docs.patch
 2016-10-13 19:51:07.0 +0200
+++ python-txaio-2.8.0/debian/patches/remove-privacy-breach-in-docs.patch   
2017-06-30 01:18:36.0 +0200
@@ -3,31 +3,22 @@
 Forwarded: no
 Last-Update: 2016-07-13
 
 python-txaio-2.5.1.orig/README.rst
-+++ python-txaio-2.5.1/README.rst
-@@ -58,25 +58,3 @@ Code like the following can then run on
- # ...
- txaio.resolve(f0, "value")
+--- a/README.rst
 b/README.rst
+@@ -60,16 +60,3 @@
  txaio.reject(f1, RuntimeError("it failed"))
+ 
+ Please refer to the `documentation 
`_ for description and usage of the 
library features.
 -
 -
 -.. |Version| image:: https://img.shields.io/pypi/v/txaio.svg
 -   :target: https://pypi.python.org/pypi/txaio
 -
--.. |Downloads| image:: https://img.shields.io/pypi/dm/txaio.svg
--   :target: https://pypi.python.org/pypi/txaio
--
--.. |GitHub Stars| image:: 
https://img.shields.io/github/stars/crossbario/txaio.svg?style=social&label=Star
--   :target: https://github.com/crossbario/txaio
--
--.. |Master Branch| image:: 
https://img.shields.io/badge/branch-master-orange.svg
--   :target: https://travis-ci.org/crossbario/txaio.svg?branch=master
--
 -.. |Build Status| image:: 
https://travis-ci.org/crossbario/txaio.svg?branch=master
 -   :target: https://travis-ci.org/crossbario/txaio
 -
--.. |Coverage| image:: 
https://img.shields.io/codecov/c/github/crossbario/txaio/master.svg
+-.. |Coverage| image:: 
https://codecov.io/github/crossbario/txaio/coverage.svg?branch=master
 -   :target: https://codecov.io/github/crossbario/txaio
 -
--.. |Docs| image:: 
https://img.shields.io/badge/docs-latest-brightgreen.svg?style=flat
--   :target: http://txaio.readthedocs.org/en/latest/
+-.. |Docs| image:: https://readthedocs.org/projects/txaio/badge/?version=latest
+-   :target: https://txaio.readthedocs.io/en/latest/
diff -Nru python-txaio-2.5.1+2016.10.03.git.623ef68776/debian/rules 
python-txaio-2.8.0/debian/rules
--- python-txaio-2.5.1+2016.10.03.git.623ef68776/debian/rules   2016-10-13 
19:51:07.0 +0200
+++ python-txaio-2.8.0/debian/rules 2017-07-14 11:18:18.0 +0200
@@ -8,6 +8,8 @@
 
 override_dh_auto_install:
pkgos-dh_auto_install
+   # they are useless and conflicting files
+   f

Processed: Re: python-txaio FTBFS: test_chained_callback[asyncio] failed

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch pending
Bug #867037 [src:python-txaio] python-txaio FTBFS: 
test_chained_callback[asyncio] failed
Added tag(s) pending and patch.

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

Processed: ruby-mustermann,ruby-mustermann19: error when trying to install together

[Debian Bug Tracking System]

Processing control commands:

> found -1 1.0.0-2
Bug #868839 [ruby-mustermann,ruby-mustermann19] 
ruby-mustermann,ruby-mustermann19: error when trying to install together
There is no source info for the package 'ruby-mustermann19' at version 
'1.0.0-2' with architecture ''
Marked as found in versions ruby-mustermann/1.0.0-2.
> found -1 0.4.3+git20160621-1
Bug #868839 [ruby-mustermann,ruby-mustermann19] 
ruby-mustermann,ruby-mustermann19: error when trying to install together
There is no source info for the package 'ruby-mustermann' at version 
'0.4.3+git20160621-1' with architecture ''
Marked as found in versions ruby-mustermann19/0.4.3+git20160621-1.

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

Processed: bug 868787 is forwarded to https://github.com/processone/cache_tab/issues/12

[Debian Bug Tracking System]

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

> forwarded 868787 https://github.com/processone/cache_tab/issues/12
Bug #868787 [src:erlang-p1-cache-tab] erlang-p1-cache-tab: FTBFS on mips, 
mipsel and powerpc: undefined symbol: __sync_add_and_fetch_8'
Set Bug forwarded-to-address to 
'https://github.com/processone/cache_tab/issues/12'.
> thanks
Stopping processing here.

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

Bug#868839: ruby-mustermann,ruby-mustermann19: error when trying to install together

[Andreas Beckmann]

Package: ruby-mustermann,ruby-mustermann19
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite
Control: found -1 1.0.0-2
Control: found -1 0.4.3+git20160621-1

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:

  Selecting previously unselected package ruby-mustermann19.
  Preparing to unpack .../ruby-mustermann19_0.4.3+git20160621-1_all.deb ...
  Unpacking ruby-mustermann19 (0.4.3+git20160621-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/ruby-mustermann19_0.4.3+git20160621-1_all.deb 
(--unpack):
   trying to overwrite 
'/usr/lib/ruby/vendor_ruby/mustermann/ast/boundaries.rb', which is also in 
package ruby-mustermann 1.0.0-2
  Errors were encountered while processing:
   /var/cache/apt/archives/ruby-mustermann19_0.4.3+git20160621-1_all.deb

This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

usr/lib/ruby/vendor_ruby/mustermann.rb
usr/lib/ruby/vendor_ruby/mustermann/ast/boundaries.rb
usr/lib/ruby/vendor_ruby/mustermann/ast/compiler.rb
usr/lib/ruby/vendor_ruby/mustermann/ast/expander.rb
usr/lib/ruby/vendor_ruby/mustermann/ast/node.rb
usr/lib/ruby/vendor_ruby/mustermann/ast/param_scanner.rb
usr/lib/ruby/vendor_ruby/mustermann/ast/parser.rb
usr/lib/ruby/vendor_ruby/mustermann/ast/pattern.rb
usr/lib/ruby/vendor_ruby/mustermann/ast/template_generator.rb
usr/lib/ruby/vendor_ruby/mustermann/ast/transformer.rb
usr/lib/ruby/vendor_ruby/mustermann/ast/translator.rb
usr/lib/ruby/vendor_ruby/mustermann/ast/validation.rb
usr/lib/ruby/vendor_ruby/mustermann/caster.rb
usr/lib/ruby/vendor_ruby/mustermann/composite.rb
usr/lib/ruby/vendor_ruby/mustermann/equality_map.rb
usr/lib/ruby/vendor_ruby/mustermann/error.rb
usr/lib/ruby/vendor_ruby/mustermann/expander.rb
usr/lib/ruby/vendor_ruby/mustermann/extension.rb
usr/lib/ruby/vendor_ruby/mustermann/identity.rb
usr/lib/ruby/vendor_ruby/mustermann/mapper.rb
usr/lib/ruby/vendor_ruby/mustermann/pattern.rb
usr/lib/ruby/vendor_ruby/mustermann/pattern_cache.rb
usr/lib/ruby/vendor_ruby/mustermann/regexp.rb
usr/lib/ruby/vendor_ruby/mustermann/regexp_based.rb
usr/lib/ruby/vendor_ruby/mustermann/regular.rb
usr/lib/ruby/vendor_ruby/mustermann/simple_match.rb
usr/lib/ruby/vendor_ruby/mustermann/sinatra.rb
usr/lib/ruby/vendor_ruby/mustermann/to_pattern.rb
usr/lib/ruby/vendor_ruby/mustermann/version.rb


This bug is assigned to both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may
also register in the BTS that the other package is affected by the bug.

Cheers,

Andreas

PS: for more information about the detection of file overwrite errors
of this kind see https://qa.debian.org/dose/file-overwrites.html


ruby-mustermann=1.0.0-2_ruby-mustermann19=0.4.3+git20160621-1.log.gz
Description: application/gzip

Bug#868787: erlang-p1-cache-tab: FTBFS on mips, mipsel and powerpc: undefined symbol: __sync_add_and_fetch_8'

[Philipp Huebner]

Hi,

> erlang-p1-cache-tab FTBFS on mips, mipsel and powerpc with this error
> while running the testsuite:
>> Failed to load NIF /<>/priv/lib/ets_cache: Failed to load NIF 
>> library: '/<>/priv/lib/ets_cache.so: undefined symbol: 
>> __sync_add_and_fetch_8' (load_failed)
> 
> This happens because these architectures do not implement 64-bit atomics
> natively. The fix is to use libatomic (part of GCC) which provides
> helper routines for these missing atomics, implemented using locks.
> 
> The attached patch does this by:
> - Linking against libatomic
> - Switching from __sync_add_and_fetch to __atomic_add_fetch
> 
> One side effect of this is that libatomic is pulled in on every
> architecture. If you don't like this, you can use -Wl,--as-needed.

awesome, will test this ASAP, thx!

Best wishes,
-- 
 .''`.   Philipp Huebner 
: :'  :  pgp fp: 6719 25C5 B8CD E74A 5225  3DF9 E5CA 8C49 25E4 205F
`. `'`
  `-



signature.asc
Description: OpenPGP digital signature

Bug#868831: apport: CVE-2017-10708

[Salvatore Bonaccorso]

Source: apport
Version: 2.16.2-1
Severity: grave
Tags: security upstream
Justification: user security hole
Forwarded: https://launchpad.net/bugs/1700573

Hi,

the following vulnerability was published for apport.

CVE-2017-10708[0]:
| An issue was discovered in Apport through 2.20.x. In apport/report.py,
| Apport sets the ExecutablePath field and it then uses the path to run
| package specific hooks without protecting against path traversal. This
| allows remote attackers to execute arbitrary code via a crafted .crash
| file.

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

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Processed: severity of 868508 is grave

[Debian Bug Tracking System]

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

> severity 868508 grave
Bug #868508 [src:fedmsg] fedmsg: CVE-2017-101
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Bug#860739: libghc-xcb-types-dev: cannot parse xcb-proto 1.12

[Clint Adams]

On Sun, Apr 23, 2017 at 01:22:33PM +0100, James Cowgill wrote:
> It looks like the xcffib dependency from cairocffi is optional, so this
> would be a much easier solution. Otherwise we have to backport tons of
> stuff or use upstream 0.5.1.

So does this mean this is no longer a bug?

Bug#868633: marked as done (haskell-blogliterately build-depends on libghc-lens-dev (< 4.15) but 4.15.1-1 is to be installed)

[Debian Bug Tracking System]

Your message dated Wed, 19 Jul 2017 03:45:03 +
with message-id <20170719034503.lv6fcfgr2cmjv...@scru.org>
and subject line newer BlogLiterately
has caused the Debian Bug report #868633,
regarding haskell-blogliterately build-depends on libghc-lens-dev (< 4.15) but 
4.15.1-1 is to be installed
to be marked as done.

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

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


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

The following packages have unmet dependencies:
  Depends: libghc-lens-dev (< 4.15) but 4.15.1-1 is to be installed
--- End Message ---
--- Begin Message ---
Version: 0.8.4.3-1

.--- End Message ---

Bug#867830: marked as done (glirc: << build dependencies on packages with a more recent version)

[Debian Bug Tracking System]

Your message dated Wed, 19 Jul 2017 03:43:19 +
with message-id <20170719034319.nkmctlaakpe7x...@scru.org>
and subject line new glirc
has caused the Debian Bug report #867830,
regarding glirc: << build dependencies on packages with a more recent 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.)


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

The following packages have unmet dependencies:
   Depends: libghc-vty-dev (< 5.12) but 5.15.1-1+b1 is to be 
installed
   Depends: libghc-vty-prof (< 5.12) but 5.15.1-1+b1 is to be 
installed
   Depends: libghc-hunit-dev (< 1.4) but 1.5.0.0-1 is to be 
installed
E
--- End Message ---
--- Begin Message ---
Version: 2.22-1

.--- End Message ---

Bug#868632: marked as done (gitit: << build dependencies on packages with a more recent version)

[Debian Bug Tracking System]

Your message dated Wed, 19 Jul 2017 03:44:06 +
with message-id <20170719034406.dedw34prqsw4i...@scru.org>
and subject line newer gitit
has caused the Debian Bug report #868632,
regarding gitit: << build dependencies on packages with a more recent 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.)


-- 
868632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868632
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gitit
Version: 0.12.1.1+dfsg-6
Severity: serious
Tags: buster sid


The following packages have unmet dependencies:
 builddeps:gitit : Depends: libghc-aeson-dev (< 0.12) but 1.0.2.1-3 is to be 
installed
   Depends: libghc-http-client-tls-dev (< 0.3) but 0.3.5.1-1+b2 
is to be installed
--- End Message ---
--- Begin Message ---
Version: 0.12.2.1-1

.--- End Message ---

Bug#867522:

[Michael Hudson-Doyle]

Attaching a patch to fix this.
diff -Nru pytest-pylint-0.6.0/debian/changelog 
pytest-pylint-0.6.0/debian/changelog
--- pytest-pylint-0.6.0/debian/changelog2016-08-02 17:56:04.0 
+1200
+++ pytest-pylint-0.6.0/debian/changelog2017-07-19 15:25:40.0 
+1200
@@ -1,3 +1,10 @@
+pytest-pylint (0.6.0-2) UNRELEASED; urgency=medium
+
+  * Prevent tests in the debian/$pkg directories from being collected when
+running the tests.
+
+ -- Michael Hudson-Doyle   Wed, 19 Jul 2017 
15:25:09 +1200
+
 pytest-pylint (0.6.0-1) unstable; urgency=medium
 
   [ Ondřej Nový ]
diff -Nru pytest-pylint-0.6.0/debian/rules pytest-pylint-0.6.0/debian/rules
--- pytest-pylint-0.6.0/debian/rules2016-08-02 17:56:04.0 +1200
+++ pytest-pylint-0.6.0/debian/rules2017-07-19 15:25:52.0 +1200
@@ -10,7 +10,7 @@
 
 override_dh_auto_install:
dh_auto_install
-   PYBUILD_SYSTEM=custom PYBUILD_TEST_ARGS="{interpreter} -m pytest -v -x" 
dh_auto_test
+   PYBUILD_SYSTEM=custom PYBUILD_TEST_ARGS="{interpreter} -m pytest -v -x 
--ignore debian" dh_auto_test
# run tests after install: plugin needs to get registered by 
setup.py/entry_points
 
 override_dh_installchangelogs:

Processed: tagging 867522

[Debian Bug Tracking System]

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

> tags 867522 + patch
Bug #867522 [src:pytest-pylint] pytest-pylint FTBFS with python 3.6 as 
supported version
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#834204: libsdl1.2: Nonfree file: src/video/fbcon/riva_mmio.h

[Manuel A. Fernandez Montecelo]

Hi Jonas,

2017-07-18 14:14 Jonas Smedegaard:

Package: src:libsdl1.2
Followup-For: Bug #834204

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

I have prepared an NMU and queued for release in 5 days.

Attached is the diff.


Thanks.  I am in the midst of a snowstorm, metaphorically speaking, so I
didn't have time (and neither I will have in the next few days) to
review this in depth, but in principle I trust your good judgement so
all fine by me, including the NMU.



I made the changes in git locally, and can push that to Alioth if
granted write access to the repository (my account is js).
Alternatively I can put my git public somewhere for you to clone if you
prefer.


If you want to become a somewhat-regular contributor / maintainer the
first option is preferrable, otherwise I think that the output of
format-path is intended for this kind of situations, and preserves
authorship and all that (?).  Whatever you prefer, really.


... and big thanks for caring and fixing this bug.


PS: (Would be super if you contact upstream about it, but it's fine if
   you don't want to get so involved.  I'll try to remember in the next
   revision of the package).


--
Manuel A. Fernandez Montecelo 

Bug#868816: python-click FTBFS: test_legacy_callbacks fails

[Adrian Bunk]

Source: python-click
Version: 6.6-1
Severity: serious
Tags: buster sid

Some recent change in usntable makes python-click FTBFS:

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

...
   dh_auto_test -O--buildsystem=pybuild
I: pybuild base:184: cd 
/build/1st/python-click-6.6/.pybuild/pythonX.Y_2.7/build; python2.7 -m pytest 
/build/1st/python-click-6.6/tests/
= test session starts ==
platform linux2 -- Python 2.7.13, pytest-3.1.3, py-1.4.34, pluggy-0.4.0
rootdir: /build/1st/python-click-6.6, inifile:
collected 117 items

../../../tests/test_arguments.py .
../../../tests/test_bashcomplete.py .
../../../tests/test_basic.py ...
../../../tests/test_chain.py ...x
../../../tests/test_commands.py ..
../../../tests/test_compat.py F.
../../../tests/test_context.py ..
../../../tests/test_defaults.py ...
../../../tests/test_formatting.py 
../../../tests/test_imports.py .
../../../tests/test_normalization.py ...
../../../tests/test_options.py 
../../../tests/test_termui.py .
../../../tests/test_testing.py 
../../../tests/test_utils.py ..

=== FAILURES ===
 test_legacy_callbacks _

runner = 

def test_legacy_callbacks(runner):
def legacy_callback(ctx, value):
return value.upper()

@click.command()
@click.option('--foo', callback=legacy_callback)
def cli(foo):
click.echo(foo)

result = runner.invoke(cli, ['--foo', 'wat'])
assert result.exit_code == 0
assert 'WAT' in result.output
>   assert 'Invoked legacy parameter callback' in result.output
E   AssertionError: assert 'Invoked legacy parameter callback' in 'WAT\n'
E+  where 'WAT\n' = .output

../../../tests/test_compat.py:17: AssertionError
=== warnings summary ===
tests/test_basic.py::test_evaluation_order
  click/core.py:874: Warning: Invoked legacy parameter callback "".  The new signature for such callbacks starting with click 
2.0 is (ctx, param, value).
value, args = param.handle_parse_result(ctx, opts, args)

tests/test_compat.py::test_legacy_callbacks
  click/core.py:874: Warning: Invoked legacy parameter callback "".  The new signature for such callbacks 
starting with click 2.0 is (ctx, param, value).
value, args = param.handle_parse_result(ctx, opts, args)

tests/test_options.py::test_custom_validation
  click/core.py:874: Warning: Invoked legacy parameter callback "".  The new signature for such callbacks 
starting with click 2.0 is (ctx, param, value).
value, args = param.handle_parse_result(ctx, opts, args)

-- Docs: http://doc.pytest.org/en/latest/warnings.html
= 1 failed, 115 passed, 1 xfailed, 3 warnings in 1.05 seconds ==
E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: cd 
/build/1st/python-click-6.6/.pybuild/pythonX.Y_2.7/build; python2.7 -m pytest 
{dir}/tests/
dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
debian/rules:13: recipe for target 'build' failed
make: *** [build] Error 25

Bug#868738: git FTBFS on several architectures: not ok 134 - --dump-aliases must be used alone

[Jonathan Nieder]

Hi,

Adrian Bunk wrote:

> https://buildd.debian.org/status/package.php?p=git&suite=sid
>
> expecting success: 
>   test_must_fail git send-email --dump-aliases --to=jan...@example.com -1 
> refs/heads/accounting
>
> --dump-aliases incompatible with other options
> test_must_fail: command not found: git send-email --dump-aliases 
> --to=jan...@example.com -1 refs/heads/accounting
> not ok 134 - --dump-aliases must be used alone

Thanks for reporting.  The relevant code is

die __("--dump-aliases incompatible with other options\n")
if !$help and $dump_aliases and @ARGV;

test_must_fail prints the "command not found" message if and only if
the status code was 127.  I would have expected it to be 1 or 128
here.

"man perlfunc" says

If the exception is outside of all enclosing "eval"s, then
the uncaught exception prints LIST to "STDERR" and exits with a
non-zero value.  If you need to exit the process with a specific
exit code, see "exit".

That doesn't tell me what the status code will be.  Peeking at the source,
I find

int exitstatus;
if (errno & 255)
STATUS_UNIX_SET(errno);
else {
exitstatus = STATUS_UNIX >> 8;
if (exitstatus & 255)
STATUS_UNIX_SET(exitstatus);
else
STATUS_UNIX_SET(255);
}

which seems risky (there are many functions that could set errno, so
this is prone to spooky action at a distance if any caller forgets to
set it explicitly).  Looking for errno values that could be 127 in
glibc and linux using "git grep --cached -e '#.*define.*E.*127'", I
find

 linux:arch/alpha/include/uapi/asm/errno.h:#define ERESTART127
 linux:arch/mips/include/uapi/asm/errno.h:#define ENETDOWN 127
 linux:arch/sparc/include/uapi/asm/errno.h:#define ECANCELED   127
 linux:include/uapi/asm-generic/errno.h:#defineEKEYEXPIRED 127

so that doesn't look likely to be the cause.

Next step is to ssh into porterboxes and get the output of

perl -e 'die "testing"'; echo $?"

Bug#868074: libfelix-bundlerepository-java: missing requirement osgi.wiring.package; (&(osgi.wiring.package=org.osgi.service.repository)(version>=1.0.0)(!(version>=1.1.0))))

[Markus Koschany]

Am 17.07.2017 um 23:45 schrieb Mykola Nikishov:
> Markus Koschany  writes:
> 
>> I tried to update the whole felix-* stack in Debian but I quickly ran
>> into more issues. Thus I have decided to replace the newly added
>> Import-Package requirement
>>
>> org.osgi.service.repository;resolution:=mandatory;version="[1.0,1.1)"
>>
>> with its old value in 2.0.8
>>
>> org.osgi.service.repository;resolution:=mandatory
> 
> As I understand, libfelix-bundlerepository-java should depend on some
> Debian package that
> a) provides the package org.osgi.service.repository
> b) is a valid OSGi bundle
> 
> libosgi-compendium-java satisfies a) but fails b) - it's MANIFEST.MF has
> no OSGi headers at all.
> 
> Is adding Depends:libosgi-compendium-java and fixing
> libosgi-compendium-java's manifest the right way to go?

The pom.xml does not list osgi-compendium as a dependency hence I'm not
so sure about that. I expect that after an upgrade of felix-main and
felix-framework things will look differently. Updating OSGi dependencies
is usually not the difficult part but reverse-dependencies like Netbeans
rely on a specific version and will certainly break if we use something
newer.

Markus



signature.asc
Description: OpenPGP digital signature

Bug#866564: marked as done (bind9: CVE-2017-3142 CVE-2017-3143)

[Debian Bug Tracking System]

Your message dated Tue, 18 Jul 2017 20:54:26 +
with message-id 
and subject line Bug#866564: fixed in bind9 1:9.10.3.dfsg.P4-12.4
has caused the Debian Bug report #866564,
regarding bind9: CVE-2017-3142 CVE-2017-3143
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.)


-- 
866564: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866564
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bind9
Version: 1:9.9.5.dfsg-9
Severity: grave
Tags: patch security upstream

Hi,

the following vulnerabilities were published for bind9.

CVE-2017-3142[0]:
|An error in TSIG authentication can permit unauthorized zone transfers

CVE-2017-3143[1]:
|An error in TSIG authentication can permit unauthorized dynamic
|updates

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-3142
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3142
[1] https://security-tracker.debian.org/tracker/CVE-2017-3143
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3143
[2] https://kb.isc.org/article/AA-01504
[3] https://kb.isc.org/article/AA-01503

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: bind9
Source-Version: 1:9.10.3.dfsg.P4-12.4

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 16 Jul 2017 22:13:21 +0200
Source: bind9
Binary: bind9 bind9utils bind9-doc host bind9-host libbind-dev libbind9-140 
libdns162 libirs141 libisc160 liblwres141 libisccc140 libisccfg140 dnsutils 
lwresd libbind-export-dev libdns-export162 libdns-export162-udeb 
libisc-export160 libisc-export160-udeb libisccfg-export140 libisccc-export140 
libisccc-export140-udeb libisccfg-export140-udeb libirs-export141 
libirs-export141-udeb
Architecture: source
Version: 1:9.10.3.dfsg.P4-12.4
Distribution: unstable
Urgency: high
Maintainer: LaMont Jones 
Changed-By: Salvatore Bonaccorso 
Closes: 866564
Description: 
 bind9  - Internet Domain Name Server
 bind9-doc  - Documentation for BIND
 bind9-host - Version of 'host' bundled with BIND 9.X
 bind9utils - Utilities for BIND
 dnsutils   - Clients provided with BIND
 host   - Transitional package
 libbind-dev - Static Libraries and Headers used by BIND
 libbind-export-dev - Development files for the exported BIND libraries
 libbind9-140 - BIND9 Shared Library used by BIND
 libdns-export162 - Exported DNS Shared Library
 libdns-export162-udeb - Exported DNS library for debian-installer (udeb)
 libdns162  - DNS Shared Library used by BIND
 libirs-export141 - Exported IRS Shared Library
 libirs-export141-udeb - Exported IRS library for debian-installer (udeb)
 libirs141  - DNS Shared Library used by BIND
 libisc-export160 - Exported ISC Shared Library
 libisc-export160-udeb - Exported ISC library for debian-installer (udeb)
 libisc160  - ISC Shared Library used by BIND
 libisccc-export140 - Command Channel Library used by BIND
 libisccc-export140-udeb - Command Channel Library used by BIND (udeb)
 libisccc140 - Command Channel Library used by BIND
 libisccfg-export140 - Exported ISC CFG Shared Library
 libisccfg-export140-udeb - Exported ISC CFG library for debian-installer (udeb)
 libisccfg140 - Config File Handling Library used by BIND
 liblwres141 - Lightweight Resolver Library used by BIND
 lwresd - Lightweight Resolver Daemon
Changes:
 bind9 (1:9.10.3.dfsg.P4-12.4) unstable; urgency=high
 .
   * Non-maintainer upload.
 .
   [ Yves-Alexis Perez ]
   * debian/patches:
 - debian/patches/CVE-2017-3142+CVE-2017-3143 added, fix TSIG bypasses
   CVE-2017-3142: error in TSIG authentication can permit unauthorized zone
   transfers. An attacker may be able to circumvent TSIG authentication of
   AXFR and Notify requests.
   CVE-2017-3143: error in TSIG 

Bug#865224: uwsgi: ftbfs with multiple supported python3 versions

[gregor herrmann]

Control: tag -1 + patch pending

On Tue, 18 Jul 2017 11:27:56 +0200, gregor herrmann wrote:

> What also seems to work is the following workaround in debian/rules:
> 
> diff -Nru uwsgi-2.0.15/debian/rules uwsgi-2.0.15/debian/rules
> --- uwsgi-2.0.15/debian/rules   2017-02-20 11:40:46.0 +0100
> +++ uwsgi-2.0.15/debian/rules   2017-07-18 08:55:03.0 +0200
> @@ -259,9 +259,11 @@
>  plugin_lang_kind = $(strip \
> $(if $(filter java python,$(plugin_lang)),\
> $(lastword $(subst -, ,$(plugin_kind)
> -plugin_flavors = $(strip \
> -   $(if $(filter python,$(plugin_lang)),\
> -   $(cdbs_$(plugin_lang_kind:python=python2)_allflavors)))
> +#workaround, cf. #865224
> +#plugin_flavors = $(strip \
> +#  $(if $(filter python,$(plugin_lang)),\
> +#  $(cdbs_$(plugin_lang_kind:python=python2)_allflavors)))
> +plugin_flavors = $(plugin_defaultflavor)
>  plugin_defaultflavor = $(strip \
> $(if $(filter python,$(plugin_lang)),\
> $(cdbs_$(plugin_lang_kind:python=python2)_defaultflavor)))
> 
[..] 
> Maybe that's a bit less invasive and a bit more binNMU friendly than
> hardcoding 'X-Python3-Version: 3.5'?

I've now uploaded this option; to DELAYED/1 in case there are some
more comments.

debdiff as uploaded attached.


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Wir sind Helden: Kaputt
diff -Nru uwsgi-2.0.15/debian/changelog uwsgi-2.0.15/debian/changelog
--- uwsgi-2.0.15/debian/changelog	2017-06-20 12:00:19.0 +0200
+++ uwsgi-2.0.15/debian/changelog	2017-07-18 22:27:56.0 +0200
@@ -1,3 +1,14 @@
+uwsgi (2.0.15-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload with maintainer's permission.
+  * Fix "ftbfs with multiple supported python3 versions":
+debian/rules: workaround cdbs issue #868752 by using only the default
+python flavors.
+Thanks to Niko Tyni and Scott Kitterman for their analyses.
+(Closes: #865224)
+
+ -- gregor herrmann   Tue, 18 Jul 2017 22:27:56 +0200
+
 uwsgi (2.0.15-2) unstable; urgency=medium
 
   * Add patches cherry-picked upstream:
diff -Nru uwsgi-2.0.15/debian/rules uwsgi-2.0.15/debian/rules
--- uwsgi-2.0.15/debian/rules	2017-02-20 11:40:46.0 +0100
+++ uwsgi-2.0.15/debian/rules	2017-07-18 17:27:48.0 +0200
@@ -259,9 +259,12 @@
 plugin_lang_kind = $(strip \
 	$(if $(filter java python,$(plugin_lang)),\
 		$(lastword $(subst -, ,$(plugin_kind)
-plugin_flavors = $(strip \
-	$(if $(filter python,$(plugin_lang)),\
-		$(cdbs_$(plugin_lang_kind:python=python2)_allflavors)))
+# workaround for #868752
+#plugin_flavors = $(strip \
+#	$(if $(filter python,$(plugin_lang)),\
+#		$(cdbs_$(plugin_lang_kind:python=python2)_allflavors)))
+plugin_flavors = $(plugin_defaultflavor)
+# workaround end
 plugin_defaultflavor = $(strip \
 	$(if $(filter python,$(plugin_lang)),\
 		$(cdbs_$(plugin_lang_kind:python=python2)_defaultflavor)))


signature.asc
Description: Digital Signature

Processed: Re: Bug#865224: uwsgi: ftbfs with multiple supported python3 versions

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + patch pending
Bug #865224 [src:uwsgi] uwsgi: ftbfs with multiple supported python3 versions
Added tag(s) pending and patch.

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

Processed: tagging 868695

[Debian Bug Tracking System]

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

> tags 868695 + moreinfo
Bug #868695 [systemd] systemd: leaves empty LC_CTYPE what breaks X11 ssh 
password prompt
Added tag(s) moreinfo.
> thanks
Stopping processing here.

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

Bug#865060: bcftools: Fix for the test-regidx FTBFS

[Adrian Bunk]

Control: tags -1 patch

The attached patch fixes test-regidx on architectures where char
is unsigned.

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

Description: Fix test-regidx argument parsing on archs with unsigned char
 On architectures where char is unsigned "c >= 0" was always true.
Author: Adrian Bunk 
Bug-Debian: https://bugs.debian.org/865060

--- bcftools-1.4.1.orig/test/test-regidx.c
+++ bcftools-1.4.1/test/test-regidx.c
@@ -336,7 +336,7 @@ int main(int argc, char **argv)
 {"seed",1,0,'s'},
 {0,0,0,0}
 };
-char c;
+int c;
 int seed = (int)time(NULL);
 while ((c = getopt_long(argc, argv, "hvs:",loptions,NULL)) >= 0) 
 {

Processed: bcftools: Fix for the test-regidx FTBFS

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #865060 [src:bcftools] bcftools FTBFS: Usage: test-regidx [OPTIONS]
Added tag(s) patch.

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

Bug#868256: marked as done (sendxmpp: does not sending any message)

[Debian Bug Tracking System]

Your message dated Tue, 18 Jul 2017 17:03:31 -0300
with message-id 

and subject line Re: sendxmpp: does not sending any message
has caused the Debian Bug report #868256,
regarding sendxmpp: does not sending any message
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.)


-- 
868256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868256
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sendxmpp
Version: 1.23-1.1
Severity: grave
Tags: upstream
Justification: renders package unusable

sendxmpp is unusable now. It was tested over Debian Stretch/Sid.

root@crazy:~# echo ok | sendxmpp --tls-ca-path=/etc/ssl/certs/ -t 
eribe...@xyz.abc
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 1829.
Use of uninitialized value $sid in concatenation (.) or string at 
/usr/share/perl5/XML/Stream.pm line 2740.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 2742.
Use of uninitialized value $sid in concatenation (.) or string at 
/usr/share/perl5/XML/Stream.pm line 1668.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 1669.
Use of uninitialized value in concatenation (.) or string at 
/usr/share/perl5/XML/Stream.pm line 1669.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 1671.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 1673.
Use of uninitialized value in numeric eq (==) at /usr/share/perl5/XML/Stream.pm 
line 1673.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 1675.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 1678.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 2620.
Use of uninitialized value $sid in concatenation (.) or string at 
/usr/share/perl5/XML/Stream.pm line 2740.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 2742.
Use of uninitialized value in concatenation (.) or string at 
/usr/share/perl5/XML/Stream.pm line 1440.
Use of uninitialized value in numeric eq (==) at /usr/share/perl5/XML/Stream.pm 
line 1443.
Use of uninitialized value within %status in numeric eq (==) at 
/usr/share/perl5/XML/Stream.pm line 1506.
Use of uninitialized value in subtraction (-) at /usr/share/perl5/XML/Stream.pm 
line 1507.
Use of uninitialized value in concatenation (.) or string at 
/usr/share/perl5/XML/Stream.pm line 1669.
Use of uninitialized value in numeric eq (==) at /usr/share/perl5/XML/Stream.pm 
line 1673.
Use of uninitialized value in hash element at 
/usr/share/perl5/Net/XMPP/Connection.pm line 433.
Use of uninitialized value in hash element at 
/usr/share/perl5/Net/XMPP/Connection.pm line 440.
Use of uninitialized value in hash element at 
/usr/share/perl5/Net/XMPP/Connection.pm line 433.
Use of uninitialized value in string eq at /usr/bin/sendxmpp line 496.
Error 'AuthSend': [?]
Use of uninitialized value $sid in concatenation (.) or string at 
/usr/share/perl5/XML/Stream.pm line 1668.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 1669.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 1671.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 1673.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 1266.
Use of uninitialized value in string eq at /usr/share/perl5/XML/Stream.pm line 
1266.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 1266.
Use of uninitialized value in string eq at /usr/share/perl5/XML/Stream.pm line 
1266.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 1267.
Use of uninitialized value in delete at /usr/share/perl5/XML/Stream.pm line 
1267.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 1268.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 1270.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 1270.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 1270.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 1270.
Use of uninitialized value $sid in hash element at 
/usr/share/perl5/XML/Stream.pm line 1270.
Use of uninitialized value $sid in delete at /usr/share/perl5/XML/Stream.pm 
line 1272.

Regard

Bug#868705: marked as done (gnome-exe-thumbnailer: CVE-2017-11421: Thumbnail generation for MSI files executes arbitrary VBScript)

[Debian Bug Tracking System]

Your message dated Tue, 18 Jul 2017 19:51:04 +
with message-id 
and subject line Bug#868705: fixed in gnome-exe-thumbnailer 0.9.5-1
has caused the Debian Bug report #868705,
regarding gnome-exe-thumbnailer: CVE-2017-11421: Thumbnail generation for MSI 
files executes arbitrary VBScript
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.)


-- 
868705: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868705
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-exe-thumbnailer
Version: 0.9.4-2
Severity: grave
Tags: security
Justification: user security hole

Dear Maintainer,

the following PoC is copied verbatim from my post about the parsing issue:
http://news.dieweltistgarnichtso.net/posts/gnome-thumbnailer-msi-fail.html

Proof of Concept

Install Dependencies

On Debian GNU/Linux, install the packages gnome-exe-thumbnailer, nautilus and 
wixl. The wixl package is only needed to create MSI files that trigger the 
thumbnailer.

If the proof of concept does not work, install winetricks and run winetricks 
wsh56 to upgrade the Windows Script Host.

Create MSI Files

Create a file named poc.xml with the following content:


http://schemas.microsoft.com/wix/2006/wi";>



Execute the following Bourne Shell code:

wixl -o poc.msi poc.xml
cp poc.msi "poc.msi\",0):Set 
fso=CreateObject(\"Scripting.FileSystemObject\"):Set 
poc=fso.CreateTextFile(\"badtaste.txt\")'.msi"

Trigger Execution

Start GNOME Files and navigate to the folder with the MSI files. An empty file 
with the name badtaste.txt should appear.

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


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

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

Versions of packages gnome-exe-thumbnailer depends on:
ii  icoutils 0.31.2-1.1
ii  imagemagick  8:6.9.7.4+dfsg-11
ii  imagemagick-6.q16 [imagemagick]  8:6.9.7.4+dfsg-11
ii  libglib2.0-bin   2.50.3-2

Versions of packages gnome-exe-thumbnailer recommends:
pn  wine 
pn  wine64-tools | wine32-tools | wine64-development-tools | wine32-dev  

gnome-exe-thumbnailer suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: gnome-exe-thumbnailer
Source-Version: 0.9.5-1

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

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

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

Debian distribution maintenance software
pp.
James Lu  (supplier of updated gnome-exe-thumbnailer 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 18 Jul 2017 08:18:48 +0800
Source: gnome-exe-thumbnailer
Binary: gnome-exe-thumbnailer
Architecture: source
Version: 0.9.5-1
Distribution: unstable
Urgency: high
Maintainer: Debian Wine Party 
Changed-By: James Lu 
Description:
 gnome-exe-thumbnailer - Wine .exe and other executable thumbnailer for GNOME
Closes: 868705
Changes:
 gnome-exe-thumbnailer (0.9.5-1) unstable; urgency=high
 .
   [ Stephen Kitt ]
   * Fix the filename mangling in debian/watch.
 .
   [ James Lu ]
   * New upstream release.
 - Switch to msitools' msiinfo for ProductVersion fetching, replacing the
   insecure VBScript-based parsing as described at
   
http://news.dieweltistgarnichtso.net/posts/gnome-thumbnailer-msi-fail.html
   (Closes: #868705; LP: #651610; CVE-2017-11421).
   * Add Enhances: caja, tumbler (>= 0.1.92~), nautilus, nemo
 These are some of the many file managers/thumbnailer programs that support
 desktop thumbnailers like exe-thumbnailer, and I have verified (at some
 point) that all of these work.
   * fallback-thumbnail-limit.patch: drop, applied upstream.
   * Bump Standards-Version to 4.0.0; no changes needed.
   * Add msitools to recommends; it is used to fetch .msi version info.
Checksums-Sha1:
 4355e

Bug#868765: marked as done (freeradius: New upstream version 3.0.15 fixing security critical bugs)

[Debian Bug Tracking System]

Your message dated Tue, 18 Jul 2017 19:50:28 +
with message-id 
and subject line Bug#868765: fixed in freeradius 3.0.15+dfsg-1
has caused the Debian Bug report #868765,
regarding freeradius: New upstream version 3.0.15 fixing security critical bugs
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.)


-- 
868765: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868765
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: freeradius
Version: 3.0.12+dfsg-5
Severity: grave
Tags: upstream security
Justification: user security hole

Dear Maintainer,

the freeradius team released version 3.0.15 fixing several important
security issues found by a fuzzing analysis.

See:
http://freeradius.org/press/index.html#3.0.15
http://freeradius.org/security/fuzzer-2017.html

The following issues were found for v3 of freeradius up to 3.0.14:
- CVE-2017-10978. No remote code execution is possible. A denial of
service is possible.
- CVE-2017-10984. Remote code execution is possible. A denial of 
service is possible.
- CVE-2017-10985. No remote code execution is possible. A denial of
service is possible.

The following affect only the DHCP part of freeradius, which is seldomly used:
- CVE-2017-10983. No remote code execution is possible. A denial of
service is possible.
- CVE-2017-10986. No remote code execution is possible. A denial of
service is possible.
- CVE-2017-10987. No remote code execution is possible. A denial of
service is possible.

Please update the package accordingly.

-- 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/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 freeradius depends on:
ii  freeradius-common  3.0.12+dfsg-5
ii  freeradius-config  3.0.12+dfsg-5
ii  libc6  2.24-11+deb9u1
ii  libcap21:2.25-1
ii  libfreeradius3 3.0.12+dfsg-5
ii  libgdbm3   1.8.3-14
ii  libpam0g   1.1.8-3.6
ii  libpcre3   2:8.39-3
ii  libperl5.245.24.1-3
ii  libpython2.7   2.7.13-2
ii  libreadline7   7.0-3
ii  libsqlite3-0   3.16.2-5
ii  libssl1.1  1.1.0f-3
ii  libtalloc2 2.1.8-1
ii  libwbclient0   2:4.5.8+dfsg-2+deb9u1+b1
ii  lsb-base   9.20161125

Versions of packages freeradius recommends:
pn  freeradius-utils  

Versions of packages freeradius suggests:
pn  freeradius-krb5
pn  freeradius-ldap
pn  freeradius-mysql   
pn  freeradius-postgresql  
pn  snmp   

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: freeradius
Source-Version: 3.0.15+dfsg-1

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

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

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

Debian distribution maintenance software
pp.
Michael Stapelberg  (supplier of updated freeradius 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 18 Jul 2017 20:49:31 +0200
Source: freeradius
Binary: freeradius freeradius-common freeradius-config freeradius-utils 
libfreeradius3 libfreeradius-dev freeradius-dhcp freeradius-krb5 
freeradius-ldap freeradius-rest freeradius-postgresql freeradius-mysql 
freeradius-iodbc freeradius-redis freeradius-memcached freeradius-yubikey
Architecture: source
Version: 3.0.15+dfsg-1
Distribution: unstable
Urgency: high
Maintainer: Debian FreeRADIUS Packaging Team 

Changed-By: Michael Stapelberg 
Description:
 freeradius - high-performance and highly configurable RADIUS server
 freeradius-common - FreeRADIUS common files
 freeradius-config - FreeRADIUS default config files
 freeradius-dhcp - DHCP module for FreeRADIUS server
 freeradius-iodbc - iODBC module for FreeRADIUS server
 freeradius-krb5 - kerberos module for FreeRADIUS server
 freeradius-ldap - LDAP module for FreeRADIUS server
 freeradius-memcached - Memcached module for FreeRADIUS server
 freeradius-mysql - MySQL 

Bug#868705: gnome-exe-thumbnailer: Thumbnail generation for MSI files executes arbitrary VBScript

[Nils Dagsson Moskopp]

Quote :

> gnome-exe-thumbnailer before 0.9.5 is prone to a VBScript Injection
> when generating thumbnails for MSI files, aka the "Bad Taste"
> issue. There is a local attack if the victim uses the GNOME Files file
> manager, and navigates to a directory containing a .msi file with
> VBScript code in its filename.

Note that thumbnailer issues could be exploited via drive-by downloads
with any web browser that does not ask users if files should be saved.

Salvatore Bonaccorso  writes:

> Control: retitle -1 gnome-exe-thumbnailer: CVE-2017-11421: Thumbnail 
> generation for MSI files executes arbitrary VBScript
>  
> Hi
>
> CVE-2017-11421 has been assigned for this issue.
>
> Regards,
> Salvatore

-- 
Nils Dagsson Moskopp // erlehmann



signature.asc
Description: PGP signature

Bug#868705: [pkg-wine-party] Bug#868705: gnome-exe-thumbnailer: Thumbnail generation for MSI files executes arbitrary VBScript

[Stephen Kitt]

Hi Salvatore,

On Tue, 18 Jul 2017 20:53:17 +0200, Salvatore Bonaccorso 
wrote:
> CVE-2017-11421 has been assigned for this issue.

Thanks, I’ve added that to the changelog and uploaded the package.

Regards,

Stephen


pgpb4FwW7Pkgi.pgp
Description: OpenPGP digital signature

Processed: found 868788 in 5.5.42-1

[Debian Bug Tracking System]

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

> # for the BTS graph
> found 868788 5.5.42-1
Bug #868788 [src:mysql-5.5] Security fixes from the July 2017 CPU
Warning: Unknown package 'src:mysql-5.5'
Marked as found in versions mysql-5.5/5.5.42-1.
Warning: Unknown package 'src:mysql-5.5'
> thanks
Stopping processing here.

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

Bug#868751: marked as done (git-cola FTBFS: rm: cannot remove '/build/1st/git-cola-2.10/debian/git-cola/usr/share/doc/git-cola/html/sources/relnotes.txt': No such file or directory)

[Debian Bug Tracking System]

Your message dated Tue, 18 Jul 2017 19:03:56 +
with message-id 
and subject line Bug#868751: fixed in git-cola 2.11-2
has caused the Debian Bug report #868751,
regarding git-cola FTBFS: rm: cannot remove 
'/build/1st/git-cola-2.10/debian/git-cola/usr/share/doc/git-cola/html/sources/relnotes.txt':
 No such file or directory
to be marked as done.

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

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


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

Some recent change in unstable makes git-cola FTBFS:

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

...
dh_installchangelogs 
rm /build/1st/git-cola-2.10/debian/git-cola/usr/share/doc/git-cola/changelog \

/build/1st/git-cola-2.10/debian/git-cola/usr/share/doc/git-cola/html/sources/relnotes.txt
rm: cannot remove 
'/build/1st/git-cola-2.10/debian/git-cola/usr/share/doc/git-cola/html/sources/relnotes.txt':
 No such file or directory
debian/rules:47: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 1
--- End Message ---
--- Begin Message ---
Source: git-cola
Source-Version: 2.11-2

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

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

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated git-cola 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 18 Jul 2017 18:00:04 +
Source: git-cola
Binary: git-cola
Architecture: source all
Version: 2.11-2
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Description:
 git-cola   - highly caffeinated git GUI
Closes: 868751
Changes:
 git-cola (2.11-2) unstable; urgency=medium
 .
   * Upload to Sid.
   * Correct duplicate documentation removal (closes: #868751).
   * Update Standards-Version to 4.0.0 and debhelper level to 10 .
Checksums-Sha1:
 5f91961b88e103cf854aa17ca3dd8758c6c0ddf2 1963 git-cola_2.11-2.dsc
 16f381279d11f7bc80a4789fc9f823285b09b355 7900 git-cola_2.11-2.debian.tar.xz
 88f1714ac49f09d1b8c99520977e18e310d71e71 626410 git-cola_2.11-2_all.deb
 69768d10aa09c7c618a3aaf30cbd22c32c9173fd 11791 git-cola_2.11-2_amd64.buildinfo
Checksums-Sha256:
 a3b3d259db8e06615da8ac3eba5c0e3475b14d71c863c7620f61b90eaf0f1e45 1963 
git-cola_2.11-2.dsc
 c3cfebff145618132e7803b4758496f4850eb580032f1b4a621a390db9822ffa 7900 
git-cola_2.11-2.debian.tar.xz
 c2a4472f6da22adef742a7edde8c644ccfceabf995d84c5f13a14b7681b1cfb2 626410 
git-cola_2.11-2_all.deb
 103c7a587cb02d6e2b274a494ef58a966fb582d7b18aa7f476d8ec2afb7d0430 11791 
git-cola_2.11-2_amd64.buildinfo
Files:
 9ab5f8f9b67e65ead8067a6368647e02 1963 vcs optional git-cola_2.11-2.dsc
 94f86c60aab80639e20d78e09dfd0371 7900 vcs optional 
git-cola_2.11-2.debian.tar.xz
 0280823c1d1280ede9e11e106e8d2517 626410 vcs optional git-cola_2.11-2_all.deb
 da8ed26e261c588532cf7563ce78a1c7 11791 vcs optional 
git-cola_2.11-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAlluVdcACgkQ3OMQ54ZM
yL/pThAAnpwAvTdJBcfnPgz7QRgv3aIBqt56YZtP+2BMkXWiWfpEnhEtwxKgwcno
+/glsFm/eQ6l6n9quxIyzROHnZ1SQtcO/lEWJS8jT1FogJz7h/3mAKwWD3hFGmqT
KtxghpHgIw3EjsD/QC4xB6rnjXdV3+ebfLk7Mk/kwyahR66mZfMuxa7yX4xWPpnb
WyfPCBrpQFT9cArxqi3l8Q35YGASJIO7TNqq6mRKecuzFOhMbCVNti4QIZywJycy
wCsjZsojAc6N0bZVet4IPIyk8cTFT4ybD/rf/f6770z4qcQQ5/2vjdZoJDXX/bV2
p4WClVxTVA4tLnRfSrYU2fFd0HE3ovR2frZ48ajLp9BRg+rYqNiC9Tnv7iOtiURF
FRtI1aJyqLUspcgRojNXAIWx0/dAqmWPOcF9C1xxJdR8JbDX+M1IU5RG2hD/86PM
XaIv5k5SfgemgqT5N8L4L8qT8ZwmDac4wucZt+Rsaghk2Y+eyMTQL/qaCr9Rfp96
pFwjuazIwpPM/DOX4SXzJZAgXfMBlltA0obgA9Qo59SOU3ZRCuOeW032h1J+w7+L
gc7jxz7kee5wXl1CrJeIiXDINpp9eWCJYKjsDtdvvHeIjfSOXvoHY1E9O9E/r/cz
8zasic4MdvaNWLvCstRZa0bKQ/2KVjTNMv/q/wcW5CdceAGXDh4=
=Vm/g
-END PGP SIGNATURE End Message ---

Processed: your mail

[Debian Bug Tracking System]

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

> severity 868018 important
Bug #868018 [appstream] appstream: AppStream system cache was updated, but 
problems were found: Metadata files have errors:
Severity set to 'important' from 'serious'
>
End of message, stopping processing here.

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

Bug#868018: appstream: AppStream system cache was updated, but problems were found: Metadata files have errors:

[Matthias Klumpp]

2017-07-11 10:46 GMT+02:00 Andreas Beckmann :
> [...]
> during a test with piuparts I noticed your package fails to upgrade from
> 'stretch' via 'buster' to 'sid'.
> It installed fine in 'stretch' and upgraded successfully to 'buster',
> then the upgrade to 'sid' fails.
>
> >From the attached log (scroll to the bottom...):
>
> 0m17.2s DEBUG: Starting command: ['chroot', '/srv/piuparts/tmp/tmphZCQmo', 
> 'apt-get', 'update']
> 0m22.4s DUMP:
>   Get:1 http://ftp.de.debian.org/debian sid InRelease [255 kB]
>   Get:2 http://ftp.de.debian.org/debian sid/main amd64 Packages [7550 kB]
>   Get:3 http://ftp.de.debian.org/debian sid/main Translation-en [5731 kB]
>   Get:4 http://ftp.de.debian.org/debian sid/main amd64 DEP-11 Metadata [3147 
> kB]
>   AppStream system cache was updated, but problems were found: Metadata files 
> have errors: 
> /var/lib/app-info/yaml/ftp.de.debian.org_debian_dists_sid_main_dep11_Components-amd64.yml.gz
>   Fetched 16.7 MB in 4s (4071 kB/s)
>   Reading package lists...
>   E: Problem executing scripts APT::Update::Post-Invoke-Success 'if 
> /usr/bin/test -w /var/cache/app-info -a -e /usr/bin/appstreamcli; then 
> appstreamcli refresh-cache > /dev/null; fi'
>   E: Sub-process returned an error code
> 0m22.4s ERROR: Command failed (status=100): ['chroot', 
> '/srv/piuparts/tmp/tmphZCQmo', 'apt-get', 'update']

This is not a bug in the package, but in the metadata - the package
itself updates properly (it has to, these errors are ignored in
postinst).

I wonder whether it makes sense to make this not a hard failure, but
just print something on stderr in case of and error and have the apt
update command succeed.

I will look into that.

Cheers,
Matthias

Processed: Re: Bug#868705: gnome-exe-thumbnailer: Thumbnail generation for MSI files executes arbitrary VBScript

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 gnome-exe-thumbnailer: CVE-2017-11421: Thumbnail generation for 
> MSI files executes arbitrary VBScript
Bug #868705 [gnome-exe-thumbnailer] gnome-exe-thumbnailer: Thumbnail generation 
for MSI files executes arbitrary VBScript
Changed Bug title to 'gnome-exe-thumbnailer: CVE-2017-11421: Thumbnail 
generation for MSI files executes arbitrary VBScript' from 
'gnome-exe-thumbnailer: Thumbnail generation for MSI files executes arbitrary 
VBScript'.

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

Bug#868705: gnome-exe-thumbnailer: Thumbnail generation for MSI files executes arbitrary VBScript

[Salvatore Bonaccorso]

Control: retitle -1 gnome-exe-thumbnailer: CVE-2017-11421: Thumbnail generation 
for MSI files executes arbitrary VBScript
 
Hi

CVE-2017-11421 has been assigned for this issue.

Regards,
Salvatore

Bug#868599: marked as done (ocaml-curses FTBFS with recent ncurses)

[Debian Bug Tracking System]

Your message dated Tue, 18 Jul 2017 18:49:58 +
with message-id 
and subject line Bug#868599: fixed in ocaml-curses 1.0.3-3
has caused the Debian Bug report #868599,
regarding ocaml-curses FTBFS with recent ncurses
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.)


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

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

...
checking for sys/ioctl.h... yes
checking windows.h usability... no
checking windows.h presence... no
checking for windows.h... no
checking for working ncurses library... found in -lncursesw
checking for term.h... configure: error: not found
debian/rules:21: recipe for target 'build-stamp' failed
make: *** [build-stamp] Error 1



config.log says:

...
configure:3644: checking for term.h
configure:3657: gcc -c -g -O2   conftest.c >&5
conftest.c: In function 'main':
conftest.c:26:10: error: storage size of '__dummy' isn't known
 TERMINAL __dummy
  ^~~
configure:3657: $? = 1
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME ""
| #define PACKAGE_TARNAME ""
| #define PACKAGE_VERSION ""
| #define PACKAGE_STRING ""
| #define PACKAGE_BUGREPORT ""
| #define PACKAGE_URL ""
| #define STDC_HEADERS 1
| #define HAVE_SYS_TYPES_H 1
| #define HAVE_SYS_STAT_H 1
| #define HAVE_STDLIB_H 1
| #define HAVE_STRING_H 1
| #define HAVE_MEMORY_H 1
| #define HAVE_STRINGS_H 1
| #define HAVE_INTTYPES_H 1
| #define HAVE_STDINT_H 1
| #define HAVE_UNISTD_H 1
| #define HAVE_TERMIOS_H 1
| #define HAVE_SYS_IOCTL_H 1
| #define CURSES_HEADER 
| /* end confdefs.h.  */
| #include 
| int
| main ()
| {
| TERMINAL __dummy
|   ;
|   return 0;
| }
...
--- End Message ---
--- Begin Message ---
Source: ocaml-curses
Source-Version: 1.0.3-3

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

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

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

Debian distribution maintenance software
pp.
Stéphane Glondu  (supplier of updated ocaml-curses package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 18 Jul 2017 20:29:29 +0200
Source: ocaml-curses
Binary: libcurses-ocaml libcurses-ocaml-dev
Architecture: source amd64
Version: 1.0.3-3
Distribution: unstable
Urgency: low
Maintainer: Debian OCaml Maintainers 
Changed-By: Stéphane Glondu 
Description:
 libcurses-ocaml - OCaml bindings for the ncurses library (runtime)
 libcurses-ocaml-dev - OCaml bindings for the ncurses library
Closes: 868599
Changes:
 ocaml-curses (1.0.3-3) unstable; urgency=low
 .
   [ Stéphane Glondu ]
   * Team upload
   * Bump debhelper compat to 10
   * Update Vcs-*
 .
   [ Sylvain Le Gall ]
   * Remove Sylvain Le Gall from uploaders
 .
   [ Sven Joachim ]
   * Use TERMTYPE rather than TERMINAL in configure check, the latter is
 opaque in recent ncurses versions (Closes: #868599).
Checksums-Sha1:
 2b399b00336fa3907bcc6e615900e4a9f9f2 2170 ocaml-curses_1.0.3-3.dsc
 b67880a3b58b4d46bcbe6f1883c82cae1c10060d 33560 
ocaml-curses_1.0.3-3.debian.tar.xz
 522b62b5959d277fdd11eac7c9a08672769b78a4 49498 
libcurses-ocaml-dbgsym_1.0.3-3_amd64.deb
 74e13129a6d4d9507bae865526f386ebf69b8d09 66178 
libcurses-ocaml-dev_1.0.3-3_amd64.deb
 1cc8474dd32ff56d8fcff57e9b28d11e7ea69e83 21790 
libcurses-ocaml_1.0.3-3_amd64.deb
 83cd8af14b566bb002b55d71f2d6dec493331a65 6483 
ocaml-curses_1.0.3-3_amd64.buildinfo
Checksums-Sha256:
 70d698bb9955addc14b14f93b866d6d769c9a1adf5c5895cada55f3d195d598e 2170 
ocaml-curses_1.0.3-3.dsc
 d6d20a464ed2747b9bde4cc929325be877729067ac15bce9ee4b8c939948ae5d 33560 
ocaml-curses_1.0.3-3.debian.tar.xz
 2865f4257cb45cc917e51be7bf82c2b51121e6935d130f5d8fde5407ae4ebe33 49498 
libcurses-ocaml-dbgsym_1.0.3-3_amd64.deb
 5565f9f5253ec8c4e8f15128ccf73ea2a55572c3fb347d93a268f98adee87bfb 66178 
libcurses-ocaml-dev_1.0.3-3_amd64.deb
 8b79e2b4961e633939c9b3d287eda75cd94eda890be618c811f5e754462127b0 21790 
libcurses-ocaml_1.0.3-3_amd64.deb
 6901c354688016a74a0f19d898868ae88b25b8753

Bug#868150: imapproxy: fails to start

[Richard Laager]

Agreed on stable-proposed-updates. I plan to prepare an upload in the next few 
days.

-- 
Richard

Bug#868798: Security fixes from the July 2017 CPU

[Lars Tangvald]

Source: mysql-5.7
Version: 5.7.18-1
Severity: grave
Tags: security upstream fixed-upstream

The Oracle Critical Patch Update for July 2017 will be released on
Tuesday, July 18. According to the pre-release announcement [1], it
will contain information about CVEs fixed in MySQL 5.7.19.

We will update the bug with CVE numbers when they become available, and
test the update to ensure there are no packaging issues that need
addressing.

Regards,

Lars Tangvald

[1]
http://www.oracle.com/technetwork/security-advisory/cpujul2017-3236622.html

Bug#858283: marked as pending

[Joël Krähemann]

tag 858283 pending
thanks

Hello,

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


http://anonscm.debian.org/git/pkg-multimedia/gsequencer.git/commit/?id=9c24b55

---
commit 9c24b55bd326f7dbebbc3f011f31c0339aad5370
Author: Joël Krähemann 
Date:   Tue Jul 18 17:42:48 2017 +0200

changelog

diff --git a/debian/changelog b/debian/changelog
index 2c1406e..09a1a83 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+gsequencer (0.8.10-1) UNRELEASED; urgency=medium
+
+  * New upstream version 0.8.10
+  * Verified no soundcard works
+(Closes: #858283)
+
+ -- Joël Krähemann   Tue, 18 Jul 
2017 17:03:13 +0200
+
 gsequencer (0.8.7-1) unstable; urgency=medium
 
   * New upstream version 0.8.7

Processed: Bug#858283 marked as pending

[Debian Bug Tracking System]

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

> tag 858283 pending
Bug #858283 [src:gsequencer] gsequencer: GSequencer crashes as no soundcard 
configured
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Re: [Pkg-ipsec-tools-devel] Bug#867986: CVE-2016-10396

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending patch
Bug #867986 [racoon] CVE-2016-10396
Added tag(s) pending and patch.

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

Bug#867986: [Pkg-ipsec-tools-devel] Bug#867986: CVE-2016-10396

[Noah Meyerhans]

Control: tags -1 + pending patch

On Mon, Jul 10, 2017 at 11:18:35PM +0200, Moritz Muehlenhoff wrote:
> 
> Please see http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-10396   
> 

I believe that the attached debdiff, derived from NetBSD's fix, should
address this problem. It should apply with only metadata modifications
as far back as oldstable.

I'll upload to unstable as soon as I've satisfied myself that the update
doesn't introduce any regressions. I don't believe there's a PoC for the
attack, so I don't know that we'll be able to confirm definitively that
the issue is resolved. If anybody has PoC code or is interested in
putting some together, I'd be interested in testing the fix more
thoroughly...

Uploads targeting (old)stable will follow shortly after unstable,
assuming no issues.

noah

diff -Nru ipsec-tools-0.8.2+20140711/debian/changelog 
ipsec-tools-0.8.2+20140711/debian/changelog
--- ipsec-tools-0.8.2+20140711/debian/changelog 2016-12-01 09:49:16.0 
+
+++ ipsec-tools-0.8.2+20140711/debian/changelog 2017-07-18 17:22:32.0 
+
@@ -1,3 +1,9 @@
+ipsec-tools (1:0.8.2+20140711-9) UNRELEASED; urgency=medium
+
+  * Import NetBSD's patch to address CVE-2016-10396 (Closes: #867986)
+
+ -- Noah Meyerhans   Tue, 18 Jul 2017 17:22:32 +
+
 ipsec-tools (1:0.8.2+20140711-8) unstable; urgency=medium
 
   * Depend on libfl-dev to follow flex changes (Closes: #846430)
diff -Nru ipsec-tools-0.8.2+20140711/debian/patches/CVE-2016-10396.patch 
ipsec-tools-0.8.2+20140711/debian/patches/CVE-2016-10396.patch
--- ipsec-tools-0.8.2+20140711/debian/patches/CVE-2016-10396.patch  
1970-01-01 00:00:00.0 +
+++ ipsec-tools-0.8.2+20140711/debian/patches/CVE-2016-10396.patch  
2017-07-18 17:22:32.0 +
@@ -0,0 +1,194 @@
+Description: Fix remotely exploitable DoS. 
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-10396
+Source: vendor; 
https://gnats.netbsd.org/cgi-bin/query-pr-single.pl?number=51682
+Bug-debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867986
+
+--- pkg-ipsec-tools.orig/src/racoon/isakmp_frag.c
 pkg-ipsec-tools/src/racoon/isakmp_frag.c
+@@ -1,4 +1,4 @@
+-/*$NetBSD: isakmp_frag.c,v 1.5 2009/04/22 11:24:20 tteras Exp $   */
++/*$NetBSD: isakmp_frag.c,v 1.5.36.1 2017/04/21 16:50:42 bouyer Exp $  
*/
+ 
+ /* Id: isakmp_frag.c,v 1.4 2004/11/13 17:31:36 manubsd Exp */
+ 
+@@ -173,6 +173,38 @@ vendorid_frag_cap(gen)
+   return ntohl(hp[MD5_DIGEST_LENGTH / sizeof(*hp)]);
+ }
+ 
++static int 
++isakmp_frag_insert(struct ph1handle *iph1, struct isakmp_frag_item *item)
++{
++  struct isakmp_frag_item *pitem = NULL;
++  struct isakmp_frag_item *citem = iph1->frag_chain;
++
++  if (iph1->frag_chain == NULL) {
++  iph1->frag_chain = item;
++  return 0;
++  }
++
++  do {
++  if (citem->frag_num == item->frag_num)
++  return -1;
++
++  if (citem->frag_num > item->frag_num) {
++  if (pitem)
++  pitem->frag_next = item;
++  item->frag_next = citem;
++  break;
++  }
++
++  pitem = citem;
++  citem = citem->frag_next;
++  } while (citem != NULL);
++
++  /* we reached the end of the list, insert */
++  if (citem == NULL)
++pitem->frag_next = item;
++  return 0;
++}
++
+ int 
+ isakmp_frag_extract(iph1, msg)
+   struct ph1handle *iph1;
+@@ -224,39 +256,43 @@ isakmp_frag_extract(iph1, msg)
+   item->frag_next = NULL;
+   item->frag_packet = buf;
+ 
+-  /* Look for the last frag while inserting the new item in the chain */
+-  if (item->frag_last)
+-  last_frag = item->frag_num;
++  /* Check for the last frag before inserting the new item in the chain */
++  if (item->frag_last) {
++  /* if we have the last fragment, indices must match */
++  if (iph1->frag_last_index != 0 &&
++  item->frag_last != iph1->frag_last_index) {
++  plog(LLV_ERROR, LOCATION, NULL,
++   "Repeated last fragment index mismatch\n");
++  racoon_free(item);
++  vfree(buf);
++  return -1;
++  }
+ 
+-  if (iph1->frag_chain == NULL) {
+-  iph1->frag_chain = item;
+-  } else {
+-  struct isakmp_frag_item *current;
++  last_frag = iph1->frag_last_index = item->frag_num;
++  }
+ 
+-  current = iph1->frag_chain;
+-  while (current->frag_next) {
+-  if (current->frag_last)
+-  last_frag = item->frag_num;
+-  current = current->frag_next;
+-  }
+-  current->frag_next = item;
++  /* insert fragment into chain */
++  if (isakmp_frag_insert(iph1, item) == -1) {
++  plog(L

Bug#868150: imapproxy: fails to start

[duck]

Quack,

On 2017-07-16 16:00, Richard Laager wrote:


From my first testing, it worked fine without PIDFile. Unfortunately,
upon further testing, it seems to fail most of the time. Given that
those errors seem harmless, I think setting PIDFile is the lesser of 
the

two evils right now, so I'm sticking with that. I've sent the update to
my sponsor. (I'm not a DD.)


I've never configured a Type=forking service, so I guess I lack some 
knowledge. Looks like a race condition but I'm not sure.



I should probably explore the idea of adding a command-line option to
imapproxy that sets foreground_mode. Then, I can use that in the 
systemd

unit, making this Type=simple instead of Type=forking.


That could be useful anyway for debugging, so I think it's a good idea.

Thanks for your upload :-). Nevertheless it doe not solve my problem yet 
because my service is on stable. I think it's important enough to ask 
for an upload to stable-proposed-updates. Please look at the procedure 
before uploading.


\_o<

--
Marc Dequènes

Bug#868695: systemd: leaves empty LC_CTYPE what breaks X11 ssh password prompt

[Michael Biebl]

Am 17.07.2017 um 20:54 schrieb Robert Luberda:
> Package: systemd
> Version: 234-1
> Severity: critical
> Justification: breaks unrelated software
> 
> I usually login on tty1 via getty and then switch to X via startx.
> After recent upgrade of systemd  I can no longer ssh to any 
> host in  X11, because gpg-agent (which is used instead of ssh-agent) 
> fails to prompt for password, and the following error is shown instead:
> 
>  sign_and_send_pubkey: signing failed: agent refused operation
>  Permission denied (publickey).
> 
> strace -f on gpg-agent process showed me this:
> 
> [pid  1794] <... read resumed> "OPTION lc-ctype=", 1002) = 16
> [pid  1792] write(12, "\n", 1 
> [pid  1794] read(6,  
> [pid  1792] <... write resumed> )   = 1
> [pid  1794] <... read resumed> "\n", 986) = 1
> [pid  1792] read(9,  
> [pid  1794] write(10, "ERR 536871188 IPC syntax error <"..., 81) = 81
> [pid  1792] <... read resumed> "ERR 536871188 IPC syntax error <"..., 1002) = 
> 81
> 
> 
> Yes, LC_CTYPE and other LC_ variables are empty, because they are set
> like this in /lib/systemd/system/getty@.service.
> Downgrading systemd to 233-10 solves the bug for me (even though
> getty@.service still contains the empty LC_ variables, but fortunatelly they 
> are not propagated to my terminals).

I'm not sure how the LC_*/LANG setting in getty@.service are relevant.
Can you please elaborate?

From what I understand, gpg-agent is started as a user service nowadays.

What does
systemctl --user show-environment
systemctl --user status gpg-agent.service
say?


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#868794: libbpp-qt-dev: postinst removal makes bppphyview FTBFS

[Adrian Bunk]

Package: libbpp-qt-dev
Version: 2.3.1-3
Severity: serious
Control: affects -1 src:bppphyview

https://buildd.debian.org/status/fetch.php?pkg=bppphyview&arch=armhf&ver=0.3.0-1.1%2Bb2&stamp=1500397457&raw=0

...
make[3]: Entering directory '/«PKGBUILDDIR»'
[ 37%] Building CXX object bppPhyView/CMakeFiles/phyview.dir/PhyView.cpp.o
In file included from /«PKGBUILDDIR»/bppPhyView/TreeSubWindow.h:43:0,
 from /«PKGBUILDDIR»/bppPhyView/PhyView.h:40,
 from /«PKGBUILDDIR»/bppPhyView/PhyView.cpp:40:
/«PKGBUILDDIR»/bppPhyView/TreeDocument.h:47:27: fatal error: Bpp/Phyl/Io.all: 
No such file or directory
 #include 
   ^
compilation terminated.
bppPhyView/CMakeFiles/phyview.dir/build.make:72: recipe for target 
'bppPhyView/CMakeFiles/phyview.dir/PhyView.cpp.o' failed
make[3]: *** [bppPhyView/CMakeFiles/phyview.dir/PhyView.cpp.o] Error 1


/usr/include/Bpp/Phyl/Io.all was created by createGeneric() in the
postinst of libbpp-qt-dev.

Processed: libbpp-qt-dev: postinst removal makes bppphyview FTBFS

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:bppphyview
Bug #868794 [libbpp-qt-dev] libbpp-qt-dev: postinst removal makes bppphyview 
FTBFS
Added indication that 868794 affects src:bppphyview

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

Bug#868695: systemd: leaves empty LC_CTYPE what breaks X11 ssh password prompt

[Michael Biebl]

Am 17.07.2017 um 20:54 schrieb Robert Luberda:
> Package: systemd
> Version: 234-1
> Severity: critical
> Justification: breaks unrelated software
> 
> I usually login on tty1 via getty and then switch to X via startx.
> After recent upgrade of systemd  I can no longer ssh to any 
> host in  X11, because gpg-agent (which is used instead of ssh-agent) 
> fails to prompt for password, and the following error is shown instead:
> 

Can you share the exact configuration you are using so we can reproduce
the problem?

I just started a pristine sid VM, logged in on tty2, ran startx
/usr/bin/openbox, then ssh some.remote.server.
This prompted me for the password withouth problems.

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#868700: claws-mail: Segfaults when selected from application menu or command line

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo
Bug #868700 [claws-mail] claws-mail: Segfaults when selected from application 
menu or command line
Added tag(s) moreinfo.

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

Bug#868700: claws-mail: Segfaults when selected from application menu or command line

[Ricardo Mones]

Control: tags -1 moreinfo

Hi Joe,

On Mon, Jul 17, 2017 at 08:54:20PM +0100, Joe wrote:
> Package: claws-mail
> Version: 3.15.0-2+b1
> Severity: grave
> Justification: renders package unusable
> 
> Since upgrade to 3.15.0-2, claws-mail segfaults when I try to run it:
> 
> joe@jrenet:~$ claws-mail
> 
> (claws-mail:3276): Claws-Mail-CRITICAL **: imap_item_get_path: assertion 
> 'folder_path != NULL' failed
> folder.c:3967 Condition path != NULL failed
> traceback:
> 0:claws-mail() [0x80cf2f8]
> 1:claws-mail() [0x80d275f]
> 2:claws-mail(folder_item_get_msg_list+0x7f) [0x80d311f]
> 3:claws-mail() [0x80dc881]
> 4:claws-mail() [0x80dd017]
> 5:claws-mail(gtk_sctree_insert_gnode+0x136) [0x828f386]
> 6:claws-mail(gtk_sctree_insert_gnode+0x1f7) [0x828f447]
> 7:claws-mail(gtk_sctree_insert_gnode+0x1f7) [0x828f447]
> 8:claws-mail(folderview_set+0x25c) [0x80df4bc]
> 9:claws-mail() [0x80df701]
> 10:   claws-mail() [0x822de41]
> 11:   /lib/i386-linux-gnu/libglib-2.0.so.0(g_hook_list_marshal+0x67) 
> [0xb6a7f847]
> 12:   claws-mail(hooks_invoke+0x64) [0x822e554]
> 13:   claws-mail(folder_add+0xc1) [0x80cc151]
> 14:   claws-mail(folder_read_list+0x79) [0x80d0959]
> 15:   claws-mail(main+0xc65) [0x80839d5]
> 16:   /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf6) [0xb6191276]
> 17:   claws-mail() [0x80857ea]
> 
> 
> (claws-mail:3276): Claws-Mail-CRITICAL **: imap_item_get_path: assertion 
> 'folder_path != NULL' failed
> folder.c:3991 Condition path != NULL failed
> traceback:
> 0:claws-mail() [0x80cf608]
> 1:claws-mail() [0x80d276c]
> 2:claws-mail(folder_item_get_msg_list+0x7f) [0x80d311f]
> 3:claws-mail() [0x80dc881]
> 4:claws-mail() [0x80dd017]
> 5:claws-mail(gtk_sctree_insert_gnode+0x136) [0x828f386]
> 6:claws-mail(gtk_sctree_insert_gnode+0x1f7) [0x828f447]
> 7:claws-mail(gtk_sctree_insert_gnode+0x1f7) [0x828f447]
> 8:claws-mail(folderview_set+0x25c) [0x80df4bc]
> 9:claws-mail() [0x80df701]
> 10:   claws-mail() [0x822de41]
> 11:   /lib/i386-linux-gnu/libglib-2.0.so.0(g_hook_list_marshal+0x67) 
> [0xb6a7f847]
> 12:   claws-mail(hooks_invoke+0x64) [0x822e554]
> 13:   claws-mail(folder_add+0xc1) [0x80cc151]
> 14:   claws-mail(folder_read_list+0x79) [0x80d0959]
> 15:   claws-mail(main+0xc65) [0x80839d5]
> 16:   /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf6) [0xb6191276]
> 17:   claws-mail() [0x80857ea]
> 
> msgcache.c:586 Condition cache_file != NULL failed
> traceback:
> 0:claws-mail(msgcache_read_cache+0xd7b) [0x812e3cb]
> 1:claws-mail() [0x80d2783]
> 2:claws-mail(folder_item_get_msg_list+0x7f) [0x80d311f]
> 3:claws-mail() [0x80dc881]
> 4:claws-mail() [0x80dd017]
> 5:claws-mail(gtk_sctree_insert_gnode+0x136) [0x828f386]
> 6:claws-mail(gtk_sctree_insert_gnode+0x1f7) [0x828f447]
> 7:claws-mail(gtk_sctree_insert_gnode+0x1f7) [0x828f447]
> 8:claws-mail(folderview_set+0x25c) [0x80df4bc]
> 9:claws-mail() [0x80df701]
> 10:   claws-mail() [0x822de41]
> 11:   /lib/i386-linux-gnu/libglib-2.0.so.0(g_hook_list_marshal+0x67) 
> [0xb6a7f847]
> 12:   claws-mail(hooks_invoke+0x64) [0x822e554]
> 13:   claws-mail(folder_add+0xc1) [0x80cc151]
> 14:   claws-mail(folder_read_list+0x79) [0x80d0959]
> 15:   claws-mail(main+0xc65) [0x80839d5]
> 16:   /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf6) [0xb6191276]
> 17:   claws-mail() [0x80857ea]
> 
> 
> (claws-mail:3276): Claws-Mail-CRITICAL **: imap_item_get_path: assertion 
> 'folder_path != NULL' failed
> Segmentation fault
> joe@jrenet:~$ 

Does this crash happen when you start claws-mail from command line?

If it does, can you install debug packages¹ and get the backtrace when
running inside gdb²?

Thanks in advance,

¹ https://wiki.debian.org/AutomaticDebugPackages
² http://www.claws-mail.org/faq/index.php/Debugging_Claws
-- 
  Ricardo Mones 
  ~
  RTFM - "Read The Manual" (The 'F' is silent). Usually a very good 
  idea. Bjarne Stroustrup



signature.asc
Description: PGP signature

Bug#865614: [Filesystems-devel] Bug#865614: aufs-dkms: aufs-dkms does not support Linux 4.11

[David R. Hedges]

Hi!

Jan Luca Naumann:

I will try to package a new version as soon as 4.11.7+ is uploaded.


I'm sorry to be a bother, but 4.11.11 is in unstable, and 4.12.2 is in the
NEW queue awaiting FTP master review. Could you please push the new version
to unstable when you have a chance (and/or NEW, to catch 4.12 when that
makes its way in)?

Thanks!
-David

Processed: python-pymzml: diff for NMU version 0.7.6-dfsg-4.1

[Debian Bug Tracking System]

Processing control commands:

> tags 865237 + patch
Bug #865237 [src:python-pymzml] Please update dependencies from latex-xcolor to 
tl-latex-recommended
Added tag(s) patch.
> tags 865237 + pending
Bug #865237 [src:python-pymzml] Please update dependencies from latex-xcolor to 
tl-latex-recommended
Added tag(s) pending.

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

Bug#865237: python-pymzml: diff for NMU version 0.7.6-dfsg-4.1

[Adrian Bunk]

Control: tags 865237 + patch
Control: tags 865237 + pending

Dear maintainer,

I've prepared an NMU for python-pymzml (versioned as 0.7.6-dfsg-4.1) and 
uploaded it to DELAYED/10. Please feel free to tell me if I delay or 
cancel it.

cu
Adrian

-- 

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

diff -Nru python-pymzml-0.7.6-dfsg/debian/changelog python-pymzml-0.7.6-dfsg/debian/changelog
--- python-pymzml-0.7.6-dfsg/debian/changelog	2016-09-01 11:43:36.0 +0300
+++ python-pymzml-0.7.6-dfsg/debian/changelog	2017-07-18 19:50:54.0 +0300
@@ -1,3 +1,11 @@
+python-pymzml (0.7.6-dfsg-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Update the build dependency from latex-xcolor to
+tl-latex-recommended. (Closes: #865237)
+
+ -- Adrian Bunk   Tue, 18 Jul 2017 19:50:54 +0300
+
 python-pymzml (0.7.6-dfsg-4) unstable; urgency=low
 
   * debian/control: update the name of the git repository to match the new
diff -Nru python-pymzml-0.7.6-dfsg/debian/control python-pymzml-0.7.6-dfsg/debian/control
--- python-pymzml-0.7.6-dfsg/debian/control	2016-09-01 11:43:36.0 +0300
+++ python-pymzml-0.7.6-dfsg/debian/control	2017-07-18 19:50:54.0 +0300
@@ -14,7 +14,7 @@
  texlive-generic-extra, 
  texlive-extra-utils, 
  texlive-latex-extra, 
- latex-xcolor, 
+ texlive-latex-recommended, 
  texlive-font-utils, 
  ghostscript, 
  texlive-fonts-recommended,

Bug#867518: marked as done (pytest-localserver FTBFS with python 3.6 as supported version)

[Debian Bug Tracking System]

Your message dated Tue, 18 Jul 2017 16:51:47 +
with message-id 
and subject line Bug#867518: fixed in pytest-localserver 0.3.7-1
has caused the Debian Bug report #867518,
regarding pytest-localserver 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.)


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

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

...
I: pybuild base:184: python3.6 -m pytest -v -x
= test session starts ==
platform linux -- Python 3.6.2rc1, pytest-3.0.6, py-1.4.34, pluggy-0.4.0 -- 
/usr/bin/python3.6
cachedir: .cache
rootdir: /build/1st/pytest-localserver-0.3.6, inifile: 
plugins: localserver-0.3.6
collecting ... collected 15 items

tests/test_http.py::test_httpserver_funcarg PASSED
tests/test_http.py::test_server_does_not_serve_file_at_startup PASSED
tests/test_http.py::test_some_content_retrieval PASSED
tests/test_http.py::test_GET_request PASSED
tests/test_http.py::test_HEAD_request PASSED
tests/test_https.py::test_httpsserver_funcarg PASSED
tests/test_https.py::test_server_does_not_serve_file_at_startup PASSED
tests/test_https.py::test_some_content_retrieval PASSED
tests/test_https.py::test_GET_request PASSED
tests/test_https.py::test_HEAD_request PASSED
tests/test_smtp.py::test_smtpserver_funcarg PASSED
tests/test_smtp.py::test_server_is_killed PASSED
tests/test_smtp.py::test_server_is_deleted PASSED
tests/test_smtp.py::test_smtpserver_has_empty_outbox_at_startup PASSED
tests/test_smtp.py::test_send_email FAILED

=== FAILURES ===
___ test_send_email 

smtpserver = <[TypeError("not all arguments converted during string 
formatting") raised in repr()] Server object at 0x7fb46cac3e10>

def test_send_email(smtpserver):
# send one e-mail
send_plain_email(
'al...@example.com', 'webmas...@example.com',
'Your e-mail is getting there', 'Seems like this test actually 
works!',
>   smtpserver.addr)

tests/test_smtp.py:63: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
tests/test_smtp.py:27: in send_plain_email
server.sendmail(from_, to, msg.as_string())
/usr/lib/python3.6/smtplib.py:882: in sendmail
(code, resp) = self.data(msg)
/usr/lib/python3.6/smtplib.py:569: in data
(code, msg) = self.getreply()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = 

def getreply(self):
"""Get a reply from the server.

Returns a tuple consisting of:

  - server response code (e.g. '250', or such, if all goes well)
Note: returns -1 if it can't read response code.

  - server response string corresponding to response code (multiline
responses are converted to a single, multiline string).

Raises SMTPServerDisconnected if end-of-file is reached.
"""
resp = []
if self.file is None:
self.file = self.sock.makefile('rb')
while 1:
try:
line = self.file.readline(_MAXLINE + 1)
except OSError as e:
self.close()
raise SMTPServerDisconnected("Connection unexpectedly closed: "
 + str(e))
if not line:
self.close()
>   raise SMTPServerDisconnected("Connection unexpectedly closed")
E   smtplib.SMTPServerDisconnected: Connection unexpectedly closed

/usr/lib/python3.6/smtplib.py:394: SMTPServerDisconnected
- Captured stdout call -
error: uncaptured python exception, closing channel  (:process_message() got an unexpected keyword argument 
'mail_options' [/usr/lib/python3.6/asyncore.py|read|83] 
[/usr/lib/python3.6/asyncore.py|handle_read_event|423] 
[/usr/lib/python3.6/asynchat.py|handle_read|171] 
[/usr/lib/python3.6/smtpd.py|found_terminator|386])
- Captured stderr call -
send: 'ehlo [127.0.1.1]\r\n'
reply: b'250-profitbricks-build5-amd64\r\n'
reply: b'250-SIZE 33554432\r\n'
reply: b'250-8BITMIME\r\n'
reply: b'250 HELP\r\n'
reply: retcode (250

Bug#868787: erlang-p1-cache-tab: FTBFS on mips, mipsel and powerpc: undefined symbol: __sync_add_and_fetch_8'

[James Cowgill]

Source: erlang-p1-cache-tab
Version: 1.0.9-1
Severity: serious
Tags: sid buster patch

Hi,

erlang-p1-cache-tab FTBFS on mips, mipsel and powerpc with this error
while running the testsuite:
> Failed to load NIF /<>/priv/lib/ets_cache: Failed to load NIF 
> library: '/<>/priv/lib/ets_cache.so: undefined symbol: 
> __sync_add_and_fetch_8' (load_failed)

This happens because these architectures do not implement 64-bit atomics
natively. The fix is to use libatomic (part of GCC) which provides
helper routines for these missing atomics, implemented using locks.

The attached patch does this by:
- Linking against libatomic
- Switching from __sync_add_and_fetch to __atomic_add_fetch

One side effect of this is that libatomic is pulled in on every
architecture. If you don't like this, you can use -Wl,--as-needed.

Thanks,
James
--- a/c_src/ets_cache.c
+++ b/c_src/ets_cache.c
@@ -100,7 +100,7 @@ static ERL_NIF_TERM incr_counter(ErlNifE
   if (enif_get_uint(env, argv[0], &counter))
 if (counter < max_counters) {
   if (counters[counter] != MAX_UINT64)
-	return enif_make_uint64(env, __sync_add_and_fetch(counters + counter, 1));
+	return enif_make_uint64(env, __atomic_add_fetch(counters + counter, 1, __ATOMIC_SEQ_CST));
 }
 
   return enif_make_badarg(env);
--- a/rebar.config
+++ b/rebar.config
@@ -24,7 +24,7 @@
 
 
 {port_specs, [{"priv/lib/ets_cache.so", ["c_src/ets_cache.c"]}]}.
-{port_env, [{"CFLAGS", "$CFLAGS -g -O2 -Wall"}]}.
+{port_env, [{"CFLAGS", "$CFLAGS -g -O2 -Wall"}, {"LDFLAGS", "$LDFLAGS -latomic"}]}.
 
 {cover_enabled, true}.
 {cover_export_enabled, true}.


signature.asc
Description: OpenPGP digital signature

Bug#867080: marked as done (dune-pdelab: Build-dependency pgf no longer available)

[Debian Bug Tracking System]

Your message dated Tue, 18 Jul 2017 16:49:44 +
with message-id 
and subject line Bug#867080: fixed in dune-pdelab 2.5.0~rc1-2
has caused the Debian Bug report #867080,
regarding dune-pdelab: Build-dependency pgf no longer available
to be marked as done.

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

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


-- 
867080: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867080
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dune-pdelab
Version: 2.5.0~20170124g7cf9f47a-1
Severity: serious
Tags: buster sid

The texlive-pictures package ships still ships pgf but no longer
provides it in the dependencies.
--- End Message ---
--- Begin Message ---
Source: dune-pdelab
Source-Version: 2.5.0~rc1-2

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 18 Jul 2017 12:33:14 +0200
Source: dune-pdelab
Binary: libdune-pdelab-dev libdune-pdelab-doc
Architecture: source
Version: 2.5.0~rc1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Ansgar Burchardt 
Description:
 libdune-pdelab-dev - toolbox for solving PDEs -- discretization module 
(development fi
 libdune-pdelab-doc - toolbox for solving PDEs -- discretization module 
(documentation)
Closes: 867080
Changes:
 dune-pdelab (2.5.0~rc1-2) unstable; urgency=medium
 .
   * Upload to unstable.
   * Build-Depend on texlive-pictures instead of pgf. (Closes: #867080)
   * debian/copyright: Update URLs.
   * Bumped Standards-Version to 4.0.0 (no changes).
Checksums-Sha1:
 3e404dcb22da25d04e24ccf2aa2de48a8ceaf163 2585 dune-pdelab_2.5.0~rc1-2.dsc
 b90288fd6d4497c1d4c90dbf17fd17330a10039b 5128 
dune-pdelab_2.5.0~rc1-2.debian.tar.xz
Checksums-Sha256:
 975a0b5b21e478010093d51d37be68228e54a7b5c3831b90bad8f048c66c5308 2585 
dune-pdelab_2.5.0~rc1-2.dsc
 5b62a5add563be4711928272dd47ca0bd97e506cf014a454b6d6c5e28365522c 5128 
dune-pdelab_2.5.0~rc1-2.debian.tar.xz
Files:
 6e1675ac4c6ad43d0c22f4c07753d244 2585 libs optional dune-pdelab_2.5.0~rc1-2.dsc
 d24f69114c69063a15676ea4d7147c42 5128 libs optional 
dune-pdelab_2.5.0~rc1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEE6XYjQ9o8g2p4zSVKamMCj1p06JMFAlluOQESHGFuc2dhckBk
ZWJpYW4ub3JnAAoJEGpjAo9adOiT8p8QAIS1+lRGqBwE81ssimcODvs8m40psaH9
BIXbBqr7GQk+GVF1rtoN2p53JKUaDBNnfo4+bSuQLDBpxdZpd37jhpm96QMVKX70
oTpPRwpuXbk3cSo17Nc/BxYrv7NB/MF3YNYkwlnkgjJ64lugS1AbcZlwTV2BDNvw
bneBvbW20nNbABn3EjeiNBSQiVexKWFp6D9dvSdUPzR+HAecApMKv07uKdNbfL/4
ekgymljxSlCdQ2Hievi5FXKx43cg01x+f69ydHNU7GqcSq5Hqr+f/jVF0q0+SwBQ
h7/3pxctSSL8wHagcfYY1cBej5deeY1icSgZr9dwPvBaBNyTVh70N0TwL57ydErt
glrc84v80+pNyMjS46wkxgioBiHItNzXBPd/un6i7ELsNTGi4Q58ghKzHzHZAZeO
swReDbk0o/yjKWJRYeLXcXinSlWRCnkCAyqJ3rCXa//sVWpaH611ABhjhBy1tXSG
WcpBiCxqPrZVEyvUkZSUgqoQPSCPkOA44oL9Btwsmq4mRTgWu12/KCSjz+phbp5+
Vad+hVt5H/p7GHFL07M8mHcLvi+zjbFbCbnzF+D8tcIwELE20MiUDZISmCUsrFBi
qQAYGVZ9NhWSlM2SrZzjJlS4NCRbYskl+bMiPc8wTa+X+S6r9SDAaIXS+WzVArHN
fIoiaQZL2Db9
=MwD9
-END PGP SIGNATURE End Message ---

Bug#868788: Security fixes from the July 2017 CPU

[Lars Tangvald]

Source: mysql-5.5
Version: 5.5.55-0+deb8u1
Severity: grave
Tags: security upstream fixed-upstream

The Oracle Critical Patch Update for July 2017 will be released on
Tuesday, July 18. According to the pre-release announcement [1], it
will contain information about CVEs fixed in MySQL 5.5.57.

We will update the bug with CVE numbers when they become available, and 
test the update to ensure there are no packaging issues that need 
addressing.


Regards,

Lars Tangvald

[1] 
http://www.oracle.com/technetwork/security-advisory/cpujul2017-3236622.html

Bug#868786: shogun FTBFS on arm64 with libeigen3-dev 3.3.4-2

[Adrian Bunk]

Source: shogun
Version: 3.2.0-7.4
Severity: serious
Tags: buster sid

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

...
/build/1st/shogun-3.2.0/src/shogun/mathematics/linalg/linsolver/DirectLinearSolverComplex.cpp:82:50:
   required from here
/usr/include/eigen3/Eigen/src/Core/util/BlasUtil.h:63:74: error: no type named 
'ReturnType' in 'struct Eigen::ScalarBinaryOpTraits<__vector(2) double, 
Eigen::internal::Packet1cd, Eigen::internal::scalar_product_op<__vector(2) 
double, Eigen::internal::Packet1cd> >'
   typedef typename ScalarBinaryOpTraits::ReturnType 
Scalar;
  ^~
In file included from /usr/include/eigen3/Eigen/Jacobi:27:0,
 from /usr/include/eigen3/Eigen/QR:16,
 from /usr/include/eigen3/Eigen/Dense:4,
 from /usr/include/eigen3/Eigen/Eigen:1,
 from 
/build/1st/shogun-3.2.0/src/shogun/mathematics/eigen3.h:17,
 from 
/build/1st/shogun-3.2.0/src/shogun/mathematics/linalg/linsolver/DirectLinearSolverComplex.cpp:15:
/usr/include/eigen3/Eigen/src/Jacobi/Jacobi.h: In instantiation of 'void 
Eigen::internal::apply_rotation_in_the_plane(Eigen::DenseBase&, 
Eigen::DenseBase&, const Eigen::JacobiRotation&) [with 
VectorX = Eigen::Block, -1, -1>, 1, -1, 
false>; VectorY = Eigen::Block, -1, -1>, 1, 
-1, false>; OtherScalar = double]':
/usr/include/eigen3/Eigen/src/Jacobi/Jacobi.h:282:40:   required from 'void 
Eigen::MatrixBase::applyOnTheLeft(Eigen::Index, Eigen::Index, const 
Eigen::JacobiRotation&) [with OtherScalar = double; Derived = 
Eigen::Matrix, -1, -1>; Eigen::Index = long int]'
/usr/include/eigen3/Eigen/src/SVD/JacobiSVD.h:725:13:   required from 
'Eigen::JacobiSVD& Eigen::JacobiSVD::compute(const MatrixType&, unsigned int) [with _MatrixType = 
Eigen::Matrix, -1, -1>; int QRPreconditioner = 2; 
Eigen::JacobiSVD::MatrixType = 
Eigen::Matrix, -1, -1>]'
/usr/include/eigen3/Eigen/src/SVD/JacobiSVD.h:548:14:   required from 
'Eigen::JacobiSVD::JacobiSVD(const MatrixType&, 
unsigned int) [with _MatrixType = Eigen::Matrix, -1, -1>; 
int QRPreconditioner = 2; Eigen::JacobiSVD::MatrixType = Eigen::Matrix, -1, -1>]'
/usr/include/eigen3/Eigen/src/SVD/JacobiSVD.h:799:10:   required from 
'Eigen::JacobiSVD::PlainObject> 
Eigen::MatrixBase::jacobiSvd(unsigned int) const [with Derived = 
Eigen::Map, -1, -1> >; typename 
Eigen::DenseBase::PlainObject = Eigen::Matrix, 
-1, -1>]'
/build/1st/shogun-3.2.0/src/shogun/mathematics/linalg/linsolver/DirectLinearSolverComplex.cpp:82:50:
   required from here
/usr/include/eigen3/Eigen/src/Jacobi/Jacobi.h:359:28: error: 'struct 
Eigen::internal::conj_helper<__vector(2) double, Eigen::internal::Packet1cd, 
false, false>' has no member named 'pmul'
 pstore(px, padd(pm.pmul(pc,xi),pcj.pmul(ps,yi)));
 ~~~^~~~
/usr/include/eigen3/Eigen/src/Jacobi/Jacobi.h:359:44: error: 'struct 
Eigen::internal::conj_helper<__vector(2) double, Eigen::internal::Packet1cd, 
false, false>' has no member named 'pmul'
 pstore(px, padd(pm.pmul(pc,xi),pcj.pmul(ps,yi)));
^~~~
/usr/include/eigen3/Eigen/src/Jacobi/Jacobi.h:360:29: error: 'struct 
Eigen::internal::conj_helper<__vector(2) double, Eigen::internal::Packet1cd, 
false, false>' has no member named 'pmul'
 pstore(py, psub(pcj.pmul(pc,yi),pm.pmul(ps,xi)));
 ^~~~
/usr/include/eigen3/Eigen/src/Jacobi/Jacobi.h:360:44: error: 'struct 
Eigen::internal::conj_helper<__vector(2) double, Eigen::internal::Packet1cd, 
false, false>' has no member named 'pmul'
 pstore(py, psub(pcj.pmul(pc,yi),pm.pmul(ps,xi)));
 ~~~^~~~
/usr/include/eigen3/Eigen/src/Jacobi/Jacobi.h:374:29: error: 'struct 
Eigen::internal::conj_helper<__vector(2) double, Eigen::internal::Packet1cd, 
false, false>' has no member named 'pmul'
 pstoreu(px, padd(pm.pmul(pc,xi),pcj.pmul(ps,yi)));
  ~~~^~~~
/usr/include/eigen3/Eigen/src/Jacobi/Jacobi.h:374:45: error: 'struct 
Eigen::internal::conj_helper<__vector(2) double, Eigen::internal::Packet1cd, 
false, false>' has no member named 'pmul'
 pstoreu(px, padd(pm.pmul(pc,xi),pcj.pmul(ps,yi)));
 ^~~~
/usr/include/eigen3/Eigen/src/Jacobi/Jacobi.h:375:40: error: 'struct 
Eigen::internal::conj_helper<__vector(2) double, Eigen::internal::Packet1cd, 
false, false>' has no member named 'pmul'
 pstoreu(px+PacketSize, padd(pm.pmul(pc,xi1),pcj.pmul(ps,yi1)));
 ~~~^~~~
/usr/include/eigen3/Eigen/src/Jacobi/Jacobi.h:375:57: error: 'struct 
Eigen::internal::conj_helper<__vector(2) double, Eigen::internal::Packet1cd, 
false, false>' has no member named 'pmul'
 pstoreu(px+PacketSize, padd(pm.pmul(pc,xi1),pcj.pmul(ps,yi1)));
 ^~~~

Bug#868652: marked as done (ros-vcstools FTBFS: CalledProcessError: Command 'git commit -m initial' returned non-zero exit status 128)

[Debian Bug Tracking System]

Your message dated Tue, 18 Jul 2017 16:19:48 +
with message-id 
and subject line Bug#868652: fixed in ros-vcstools 0.1.39-4
has caused the Debian Bug report #868652,
regarding ros-vcstools FTBFS: CalledProcessError: Command 'git commit -m 
initial' returned non-zero exit status 128
to be marked as done.

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

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


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

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

...
Checked out revision 1.
..
==
ERROR: test suite for 
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/suite.py", line 209, in run
self.setUp()
  File "/usr/lib/python2.7/dist-packages/nose/suite.py", line 292, in setUp
self.setupContext(ancestor)
  File "/usr/lib/python2.7/dist-packages/nose/suite.py", line 315, in 
setupContext
try_run(context, names)
  File "/usr/lib/python2.7/dist-packages/nose/util.py", line 471, in try_run
return func()
  File 
"/build/1st/ros-vcstools-0.1.39/.pybuild/pythonX.Y_2.7/build/test/test_git.py", 
line 71, in setUpClass
subprocess.check_call("git commit -m initial", shell=True, 
cwd=self.remote_path)
  File "/usr/lib/python2.7/subprocess.py", line 186, in check_call
raise CalledProcessError(retcode, cmd)
CalledProcessError: Command 'git commit -m initial' returned non-zero exit 
status 128

==
ERROR: test suite for 
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/suite.py", line 209, in run
self.setUp()
  File "/usr/lib/python2.7/dist-packages/nose/suite.py", line 292, in setUp
self.setupContext(ancestor)
  File "/usr/lib/python2.7/dist-packages/nose/suite.py", line 315, in 
setupContext
try_run(context, names)
  File "/usr/lib/python2.7/dist-packages/nose/util.py", line 471, in try_run
return func()
  File 
"/build/1st/ros-vcstools-0.1.39/.pybuild/pythonX.Y_2.7/build/test/test_git.py", 
line 71, in setUpClass
subprocess.check_call("git commit -m initial", shell=True, 
cwd=self.remote_path)
  File "/usr/lib/python2.7/subprocess.py", line 186, in check_call
raise CalledProcessError(retcode, cmd)
CalledProcessError: Command 'git commit -m initial' returned non-zero exit 
status 128

==
ERROR: test suite for 
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/suite.py", line 209, in run
self.setUp()
  File "/usr/lib/python2.7/dist-packages/nose/suite.py", line 292, in setUp
self.setupContext(ancestor)
  File "/usr/lib/python2.7/dist-packages/nose/suite.py", line 315, in 
setupContext
try_run(context, names)
  File "/usr/lib/python2.7/dist-packages/nose/util.py", line 471, in try_run
return func()
  File 
"/build/1st/ros-vcstools-0.1.39/.pybuild/pythonX.Y_2.7/build/test/test_git.py", 
line 71, in setUpClass
subprocess.check_call("git commit -m initial", shell=True, 
cwd=self.remote_path)
  File "/usr/lib/python2.7/subprocess.py", line 186, in check_call
raise CalledProcessError(retcode, cmd)
CalledProcessError: Command 'git commit -m initial' returned non-zero exit 
status 128

==
ERROR: test suite for 
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/suite.py", line 209, in run
self.setUp()
  File "/usr/lib/python2.7/dist-packages/nose/suite.py", line 292, in setUp
self.setupContext(ancestor)
  File "/usr/lib/python2.7/dist-packages/nose/suite.py", line 315, in 
setupContext
try_run(context, names)
  File "/usr/lib/python2.7/dist-packages/nose/util.py", line 471, in try_run
return func()
  File 
"/build/1st/ros-vcstools-0.1.39/.pybuild/pythonX.Y_2.7/build/test/test_git.py", 
line 71, in setUpClass
subprocess.check_call("git commit -m initial", shell=True, 
cwd=self.remote_path)
  File "/usr/lib/python2.7/subprocess.py", line 186, in check_call
raise CalledProcessError(retcode, cmd)
CalledProcessEr

Bug#868639: marked as done (cmake: error while loading shared libraries: libcrypto.so.1.0.0)

[Debian Bug Tracking System]

Your message dated Tue, 18 Jul 2017 17:57:42 +0200
with message-id 
and subject line Re: [Pkg-cmake-team] Bug#868639: cmake: error while loading 
shared libraries: libcrypto.so.1.0.0
has caused the Debian Bug report #868639,
regarding cmake: error while loading shared libraries: libcrypto.so.1.0.0
to be marked as done.

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

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


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

Dear Maintainer,

I've recently migrated my server from Debian 8 to Debian 9 and installed the 
last version of cmake available to Debian Stretch.

Every time I invoke cmake a get as result:
cmake: error while loading shared libraries: libcrypto.so.1.0.0: cannot open 
shared object file: No such file or directory 

And it imediately closes.

It seems that this package has been compiled with an older version of libssl 
than what is available in the Debian Stretch repository (libssl1.0.2 and 
libssl1.1).

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

Versions of packages cmake depends on:
ii  cmake-data3.7.2-1
ii  dpkg  1.18.24
ii  libarchive13  3.2.2-2
ii  libc6 2.24-11+deb9u1
ii  libcurl3  7.52.1-5
ii  libexpat1 2.2.0-2+deb9u1
ii  libgcc1   1:6.3.0-18
ii  libjsoncpp1   1.7.4-3
ii  libstdc++66.3.0-18
ii  libuv11.9.1-3
ii  procps2:3.3.12-3
ii  zlib1g1:1.2.8.dfsg-5

Versions of packages cmake recommends:
ii  gcc   4:6.3.0-4
ii  make  4.1-9.1

Versions of packages cmake suggests:
pn  codeblocks   
pn  eclipse  
pn  ninja-build  

-- no debconf information
--- End Message ---
--- Begin Message ---
On 18.07.2017 02:44, Augusto Fraga Giachero wrote:
> Hi Felix,
> 
> I've figure out the problem, it was my fault... I didn't realized that the 
> .bashrc of my user
> modified the PATH variable and I was executing a locally installed cmake 
> binary...
> 
> Sorry for the noise :(

Thanks for following up, closing accordingly.

Felix--- End Message ---

Processed: Re: Bug#868602: bats FTBFS: test failures

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #868602 [src:bats] bats FTBFS: test failures
Severity set to 'important' from 'serious'

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

Bug#868602: bats FTBFS: test failures

[Adrian Bunk]

Control: severity -1 important

On Tue, Jul 18, 2017 at 10:07:32AM -0400, Yaroslav Halchenko wrote:
> 
> On Mon, 17 Jul 2017, Adrian Bunk wrote:
> 
> > Source: bats
> > Version: 0.4.0-1.1
> > Severity: serious
> > Tags: buster sid
> 
> > Some recent change in unstable makes bats FTBFS:
> 
> > https://tests.reproducible-builds.org/debian/history/bats.html
> > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/bats.html
> 
> failed to reproduce FTBFS on the laptop and clean sid env (cowbuilder).
> not sure how to proceed -- may be was a fluke which would go away on its
> own

I just retried once more and it still fails.

11/11 failures in buster+unstable
4/4 passes in stretch
That's a pretty strong pattern.

But like you I cannot reproduce it locally, reducing the severity.

cu
Adrian

-- 

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

Bug#868739: marked as done (courier-authlib FTBFS on armel/armhf/s390x: symbol differences)

[Debian Bug Tracking System]

Your message dated Tue, 18 Jul 2017 15:48:46 +
with message-id 
and subject line Bug#868739: fixed in courier-authlib 0.68.0-3
has caused the Debian Bug report #868739,
regarding courier-authlib FTBFS on armel/armhf/s390x: symbol differences
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.)


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

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

armel/armhf:

...
   dh_makeshlibs -a
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: warning: debian/courier-authlib/DEBIAN/symbols doesn't match 
completely debian/courier-authlib.symbols
--- debian/courier-authlib.symbols (courier-authlib_0.68.0-2_armel)
+++ dpkg-gensymbolsNkSMCQ   2017-07-17 23:23:54.337428029 +
@@ -101,6 +101,7 @@
  strdupdefdomain@Base 0.63.0
 libcourierauthcommon.so.0 courier-authlib #MINVER#
 * Build-Depends-Package: courier-authlib-dev
+ 
_ZSt9__find_ifIN9__gnu_cxx17__normal_iteratorIPcNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcENS0_5__ops10_Iter_predIN7courier4auth11config_file7isspaceT_SH_SH_T0_St26random_access_iterator_tag@Base
 0.68.0-2
  (c++)"__gnu_cxx::__normal_iterator, std::allocator > 
> std::__find_if<__gnu_cxx::__normal_iterator, std::allocator > 
>, __gnu_cxx::__ops::_Iter_equals_val 
>(__gnu_cxx::__normal_iterator, std::allocator > >, 
__gnu_cxx::__normal_iterator, std::allocator > >, 
__gnu_cxx::__ops::_Iter_equals_val, 
std::random_access_iterator_tag)@Base" 0.67.0
  (c++|arch-bits=64)"__gnu_cxx::__normal_iterator, std::allocator > 
> std::__find_if<__gnu_cxx::__normal_iterator, std::allocator > 
>, __gnu_cxx::__ops::_Iter_pred 
>(__gnu_cxx::__normal_iterator, std::allocator > >, 
__gnu_cxx::__normal_iterator, std::allocator > >, 
__gnu_cxx::__ops::_Iter_pred, 
std::random_access_iterator_tag)@Base" 0.67.0
  (c++)"__gnu_cxx::__normal_iterator, std::allocator > > 
std::__find_if<__gnu_cxx::__normal_iterator, std::allocator > 
>, __gnu_cxx::__ops::_Iter_pred 
>(__gnu_cxx::__normal_iterator, std::allocator > >, 
__gnu_cxx::__normal_iterator, std::allocator > >, 
__gnu_cxx::__ops::_Iter_pred, 
std::random_access_iterator_tag)@Base" 0.67.0
dh_makeshlibs: failing due to earlier errors
debian/rules:27: recipe for target 'binary-arch' failed
make: *** [binary-arch] Error 2


s390x:

...
   dh_makeshlibs -a
dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/courier-authlib/DEBIAN/symbols doesn't match 
completely debian/courier-authlib.symbols
--- debian/courier-authlib.symbols (courier-authlib_0.68.0-2_s390x)
+++ dpkg-gensymbolsUL_Ajc   2017-07-17 22:19:06.506275075 +
@@ -102,7 +102,7 @@
 libcourierauthcommon.so.0 courier-authlib #MINVER#
 * Build-Depends-Package: courier-authlib-dev
  (c++)"__gnu_cxx::__normal_iterator, std::allocator > 
> std::__find_if<__gnu_cxx::__normal_iterator, std::allocator > 
>, __gnu_cxx::__ops::_Iter_equals_val 
>(__gnu_cxx::__normal_iterator, std::allocator > >, 
__gnu_cxx::__normal_iterator, std::allocator > >, 
__gnu_cxx::__ops::_Iter_equals_val, 
std::random_access_iterator_tag)@Base" 0.67.0
- (c++|arch-bits=64)"__gnu_cxx::__normal_iterator, std::allocator > 
> std::__find_if<__gnu_cxx::__normal_iterator, std::allocator > 
>, __gnu_cxx::__ops::_Iter_pred 
>(__gnu_cxx::__normal_iterator, std::allocator > >, 
__gnu_cxx::__normal_iterator, std::allocator > >, 
__gnu_cxx::__ops::_Iter_pred, 
std::random_access_iterator_tag)@Base" 0.67.0
+#MISSING: 0.68.0-2# (c++|arch-bits=64)"__gnu_cxx::__normal_iterator, std::allocator > 
> std::__find_if<__gnu_cxx::__normal_iterator, std::allocator > 
>, __gnu_cxx::__ops::_Iter_pred 
>(__gnu_cxx::__normal_iterator, std::allocator > >, 
__gnu_cxx::__normal_iterator, std::allocator > >, 
__gnu_cxx::__ops::_Iter_pred, 
std::random_access_iterator_tag)@Base" 0.67.0
  (c++)"__gnu_cxx::__normal_iterator, std::allocator > > 
std::__find_if<__gnu_cxx::__normal_iterator, std::allocator > 
>, __gnu_cxx::__ops::_Iter_pred 
>(__gnu_cxx::__normal_iterator, std::allocator > >, 
__gnu_cxx::__normal_iterator, std::allocator > >, 
__gnu_cxx::__ops::_Iter_pred, 
std::random_access_iterator_tag)@Base" 0.67.0
  auth_cram_callback@Base 0.63.0
  auth_get_cram@Base 0.63.0
@@ -127,7 +127,7 @@
  (c++)"courier::auth::config_file::open_and_load_file(bool)@Base" 0.67.0
  
(c++)"courier::auth::config_fil

Bug#861333: r-base: R packages uploaded to Debian before 14 April 2017 that use .C or .Fortran fail to find objects

[Dirk Eddelbuettel]

On 18 July 2017 at 11:55, Johannes Ranke wrote:
| Nice. Amazing work. So buster should be covered then.

Thanks!

I also pushed the code to CRAN as RcppAPT 0.0.4 just to mark a snapshot.
 
| Now (correct me if I am wrong) if we could adapt your scripts to create 
| versioned Breaks: relationships with these packages, this would open the 
| possibility to create backports for stretch-backports and jessie-backports-
| sloppy, taking advantage of the Debian infrastructure for builds on all 
| architectures.

Yes. RcppAPT just reads whatever cached data apt has -- will work on stable
too (unless you get unlucky and libapt-pkg-dev is slightly different which we
could probably address).

Dirk

-- 
http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#868720: sympa FTBFS: configure: error: invalid value /usr/sbin/newaliases for newaliases command

[Stefan Hornburg (Racke)]

On 07/18/2017 01:02 AM, Adrian Bunk wrote:
> Source: sympa
> Version: 6.2.16~dfsg-4
> Severity: serious
> 
> https://buildd.debian.org/status/package.php?p=sympa&suite=sid
> 
> ...
> checking for pod2man... /usr/bin/pod2man
> checking for makemap... /usr/bin/makemap
> checking user-supplied newaliases command... non-existing
> configure: error: invalid value /usr/sbin/newaliases for newaliases command
> 
> 

Apparently sympa checks for the presence of this binary on the build system.

Regards
 Racke

-- 
Ecommerce and Linux consulting + Perl and web application programming.
Debian and Sympa administration.

Bug#867074: marked as done (dune-functions: Build-dependency pgf no longer available)

[Debian Bug Tracking System]

Your message dated Tue, 18 Jul 2017 15:04:44 +
with message-id 
and subject line Bug#867074: fixed in dune-functions 2.5.1-1
has caused the Debian Bug report #867074,
regarding dune-functions: Build-dependency pgf no longer available
to be marked as done.

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

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


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

The texlive-pictures package ships still ships pgf but no longer
provides it in the dependencies.
--- End Message ---
--- Begin Message ---
Source: dune-functions
Source-Version: 2.5.1-1

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 18 Jul 2017 12:13:03 +0200
Source: dune-functions
Binary: libdune-functions-dev libdune-functions-doc
Architecture: source
Version: 2.5.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Ansgar Burchardt 
Description:
 libdune-functions-dev - toolbox for solving PDEs -- interface for functions 
(development
 libdune-functions-doc - toolbox for solving PDEs -- interface for functions 
(documentatio
Closes: 867074
Changes:
 dune-functions (2.5.1-1) unstable; urgency=medium
 .
   * New upstream release.
   * Build-Depend on texlive-pictures instead of pgf. (Closes: #867074)
   * debian/copyright: Upgrade copyright format URL to https://.
   * Bumped Standards-Version to 4.0.0.
Checksums-Sha1:
 19ef81ddec087ba22f469f0a181fdee58b520a02 2775 dune-functions_2.5.1-1.dsc
 1d30597cd3e7fbecb1c30c66ad48210baab08adc 252708 
dune-functions_2.5.1.orig.tar.gz
 d91aa2b6f46478c36ffbe997e02436d34071112e 1061 
dune-functions_2.5.1.orig.tar.gz.asc
 0994450bbf5fe8239994695fbc45456fb90a33e3 2732 
dune-functions_2.5.1-1.debian.tar.xz
Checksums-Sha256:
 b9b2f85eae5b1cf558afe54669104486e1221dcf9d08065529269652746f2470 2775 
dune-functions_2.5.1-1.dsc
 18bc5969d42601d758f42cfb532bf1cbbcff7960de916dc0222638449b24aa88 252708 
dune-functions_2.5.1.orig.tar.gz
 d0f6d7efac81562a22d0709cf51fc91ec6753da30a2867c28e794cc4d4263e44 1061 
dune-functions_2.5.1.orig.tar.gz.asc
 ba7fc0370a8a194d7bd889b46ef68b76be6cbdf101cbefd3fe071119331e0507 2732 
dune-functions_2.5.1-1.debian.tar.xz
Files:
 860941bd15d11701e664eb7f26f146be 2775 libs optional dune-functions_2.5.1-1.dsc
 b8eb9a1d2151fa6b0684ca3f838b6963 252708 libs optional 
dune-functions_2.5.1.orig.tar.gz
 da830d42d0fa235118b0f24d0e9afdce 1061 libs optional 
dune-functions_2.5.1.orig.tar.gz.asc
 89c6b28041475462cc8f4a39f785ae2b 2732 libs optional 
dune-functions_2.5.1-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEE6XYjQ9o8g2p4zSVKamMCj1p06JMFAlluFMsSHGFuc2dhckBk
ZWJpYW4ub3JnAAoJEGpjAo9adOiT22oP/jom4ThswOpgTEmQ8GuvKKTzCsoHs9cq
MqbFNBy6pOLv3ICy3h4Hsz8a0pFvczwkpiBQzNByal7H0RIFVkZotFm6eBWDZyrx
uFgXUdzXts9FJ6azLEvWZR7qhOPI2ktq2WUQ+mOKBoUWunqcpHNkXJE44FWSwVHL
GbmmBMsqtpzmLERF7GW9OlYeiyLvCmdMfFtr+kAgiUnpHYcsUUHuSMTcxG7AMbmC
yFHxTVAdUjbhbp6TWa3JPB/UGaZTd+fnPi9RC0NL8wiPB2YpzsqMu0Th7WLZfrfp
ZhTRYRIpzp+D+13DBvyzuS4qHV00pvfF1fJLdW8EdJnFAqkWA459AmiEranWQEaQ
IIvmeWdJslPRFC5OZfIMmbWPJHG2hDevCBPmYxjEII/MmFY/PVCFArHF3IAtcM1V
Vc3+Zmj5fuw23eqJSS5i2ystfnB4+TcUQE3ozj+uBc3KkYjxfist5LfGszhiQ7YX
+LbI+ZgwFFBSIaw6SbEVo4nmMPb9MaCwyT/zu+NV0b/0VXOM5+Adsb3klO71eaCF
EbIZ04zm5dL4yQMxCDKdcSUxQH17hgD8qADFDE3gQlrZAyrDppf1ugS5idhClFk5
k+M9jjiijOs9beM1Q1zeTlN1wK4Z/qpirfF0tH0lizCVXXkxLefISHWuAtsgFh31
WFpj9HjfQfom
=GxMv
-END PGP SIGNATURE End Message ---

Processed: Re: Bug#863110: openvpn: VPN remains connected, but network is unreachable after 30-45 min and requires reconnect

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://community.openvpn.net/openvpn/ticket/812
Bug #863110 [openvpn] openvpn: VPN remains connected, but network is 
unreachable after 30-45 min and requires reconnect
Set Bug forwarded-to-address to 
'https://community.openvpn.net/openvpn/ticket/812'.

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

Bug#863110: openvpn: VPN remains connected, but network is unreachable after 30-45 min and requires reconnect

[Bernhard Schmidt]

Control: forwarded -1 https://community.openvpn.net/openvpn/ticket/812

> I have tested it three times, it is definitly
> https://community.openvpn.net/openvpn/ticket/812 which fixes this issue

Thanks, I'll fix it ASAP.

Bernhard

Bug#868780: pytest-catchlog: latest pytest breaks test_compat_camel_case_aliases

[Daniel Stender]

Source: pytest-catchlog
Version: 1.2.2-1
Severity: serious
Justification: fails to build from source
Control: forwarded -1 https://github.com/eisensheng/pytest-catchlog/issues/68

Latest Pytest in Debian (3.1.3) breaks the tests of this package:


test_pytest_catchlog.py::test_record_tuples PASSED
test_pytest_catchlog.py::test_compat_camel_case_aliases FAILED

=== FAILURES ===
 test_compat_camel_case_aliases 

testdir = 

def test_compat_camel_case_aliases(testdir):
testdir.makepyfile('''
import logging

def test_foo(caplog):
caplog.setLevel(logging.INFO)
logging.getLogger().debug('boo!')

with caplog.atLevel(logging.WARNING):
logging.getLogger().info('catch me if you can')
''')
result = testdir.runpytest()
assert result.ret == 0

py.test.raises(Exception, result.stdout.fnmatch_lines,
   ['*- Captured *log call -*'])

result = testdir.runpytest('-rw')
assert result.ret == 0
result.stdout.fnmatch_lines('''
=*warning summary*=
*WL1*test_compat_camel_case_aliases*caplog.setLevel()*deprecated*
*WL1*test_compat_camel_case_aliases*caplog.atLevel()*deprecated*
>   ''')
E   Failed: nomatch: '=*warning summary*='
E   and: u'= test session starts 
=='
E   and: u'platform linux2 -- Python 2.7.13, pytest-3.1.3, py-1.4.34, 
pluggy-0.4.0'
E   and: u'rootdir: 
/tmp/pytest-of-aham/pytest-0/testdir/test_compat_camel_case_aliases0, inifile:'
E   and: u'plugins: catchlog-1.2.2'
E   and: u'collected 1 item'
E   and: u''
E   and: u'test_compat_camel_case_aliases.py .'
E   and: u''
E   and: u'=== warnings summary 
==='
E   and: u'test_compat_camel_case_aliases.py::test_foo'
E   and: u"  'caplog.setLevel()' is deprecated, use 
'caplog.set_level()' instead"
E   and: u"  'caplog.atLevel()' is deprecated, use 'caplog.at_level()' 
instead"
E   and: u''
E   and: u'-- Docs: http://doc.pytest.org/en/latest/warnings.html'
E   and: u'= 1 passed, 2 warnings in 0.00 seconds 
='
E   and: u''
E   remains unmatched: '=*warning summary*='

/<>/test_pytest_catchlog.py:230: Failed
- Captured stdout call -
= test session starts ==
platform linux2 -- Python 2.7.13, pytest-3.1.3, py-1.4.34, pluggy-0.4.0
rootdir: /tmp/pytest-of-aham/pytest-0/testdir/test_compat_camel_case_aliases0, 
inifile:
plugins: catchlog-1.2.2
collected 1 item

test_compat_camel_case_aliases.py .

=== warnings summary ===
test_compat_camel_case_aliases.py::test_foo
  'caplog.setLevel()' is deprecated, use 'caplog.set_level()' instead
  'caplog.atLevel()' is deprecated, use 'caplog.at_level()' instead

-- Docs: http://doc.pytest.org/en/latest/warnings.html
= 1 passed, 2 warnings in 0.01 seconds =
= test session starts ==
platform linux2 -- Python 2.7.13, pytest-3.1.3, py-1.4.34, pluggy-0.4.0
rootdir: /tmp/pytest-of-aham/pytest-0/testdir/test_compat_camel_case_aliases0, 
inifile:
plugins: catchlog-1.2.2
collected 1 item

test_compat_camel_case_aliases.py .

=== warnings summary ===
test_compat_camel_case_aliases.py::test_foo
  'caplog.setLevel()' is deprecated, use 'caplog.set_level()' instead
  'caplog.atLevel()' is deprecated, use 'caplog.at_level()' instead

-- Docs: http://doc.pytest.org/en/latest/warnings.html
= 1 passed, 2 warnings in 0.00 seconds =
-- Captured log call ---
test_compat_camel_case_aliases.py5 DEBUGboo!
test_compat_camel_case_aliases.py8 INFO catch me if you can
test_compat_camel_case_aliases.py5 DEBUGboo!
test_compat_camel_case_aliases.py8 INFO catch me if you can
 Interrupted: stopping after 1 failures 
= 1 failed, 10 passed in 0.45 seconds ==
E: pybuild pybuild:283: test: plugin custom failed with: exit code=2: python2.7 
-m pytest -v -x


Thanks,
DS

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

Kernel: Linux 4.5.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), 
LANGUAGE=de_DE.utf8 

Processed: pytest-catchlog: latest pytest breaks test_compat_camel_case_aliases

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/eisensheng/pytest-catchlog/issues/68
Bug #868780 [src:pytest-catchlog] pytest-catchlog: latest pytest breaks 
test_compat_camel_case_aliases
Set Bug forwarded-to-address to 
'https://github.com/eisensheng/pytest-catchlog/issues/68'.

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

Bug#868602: bats FTBFS: test failures

[Yaroslav Halchenko]

On Mon, 17 Jul 2017, Adrian Bunk wrote:

> Source: bats
> Version: 0.4.0-1.1
> Severity: serious
> Tags: buster sid

> Some recent change in unstable makes bats FTBFS:

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

failed to reproduce FTBFS on the laptop and clean sid env (cowbuilder).
not sure how to proceed -- may be was a fluke which would go away on its
own

-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik

Bug#867410: marked as done (python3-nagiosplugin; missing dependencies)

[Debian Bug Tracking System]

Your message dated Tue, 18 Jul 2017 13:50:46 +
with message-id 
and subject line Bug#867410: fixed in nagiosplugin 1.2.4-1
has caused the Debian Bug report #867410,
regarding python3-nagiosplugin; 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.)


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

Due to a cut'n'paste error there are no package dependencies.

Fix:

--- debian/control.old  2017-07-06 14:00:47.0 +
+++ debian/control  2017-07-06 14:00:56.0 +
@@ -42,7 +42,7 @@
 
 Package: python3-nagiosplugin
 Architecture: all
-Depends: ${misc:Depends}, ${python:Depends}
+Depends: ${misc:Depends}, ${python3:Depends}
 Description: Python class library for writing Nagios (Icinga) plugins (Python 
3)
  nagiosplugin is a Python class library which helps writing Nagios
  (or Icinga) compatible plugins easily in Python. It cares for much of
--- End Message ---
--- Begin Message ---
Source: nagiosplugin
Source-Version: 1.2.4-1

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 18 Jul 2017 15:25:45 +0200
Source: nagiosplugin
Binary: python-nagiosplugin python3-nagiosplugin
Architecture: source all
Version: 1.2.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Jan Dittberner 
Description:
 python-nagiosplugin - Python class library for writing Nagios (Icinga) plugins 
(Python
 python3-nagiosplugin - Python class library for writing Nagios (Icinga) 
plugins (Python
Closes: 867410
Changes:
 nagiosplugin (1.2.4-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Fixed VCS URL (https)
 .
   [ Jan Dittberner ]
   * Fix "python3-nagiosplugin; missing dependencies" by fixing a typo in
 debian/control stanza (Closes: #867410)
   * Fix spelling in debian/control long descriptions
   * Add myself to Uploaders field in debian/control
   * Update debian/copyright
   * Bump Standards-Version to 4.0.0
 - change copyright format URL to https
   * New upstream release
Checksums-Sha1:
 f4271fa9887d3305d5f64b4e959ba38213efa4ed 1959 nagiosplugin_1.2.4-1.dsc
 d76df86ec7902f2e5cbf37e5aa49e5a4b41ecfa8 38290 nagiosplugin_1.2.4.orig.tar.gz
 1c7dc3f62e932d5ba3e356fd9f3a3a4cd5c1d74a 3680 
nagiosplugin_1.2.4-1.debian.tar.xz
 e09b1e63bd3912e74795f18eecc4c336a269869d 6489 
nagiosplugin_1.2.4-1_amd64.buildinfo
 b83ade9d7f4673e35943162f1ea0e4279830560a 34260 
python-nagiosplugin_1.2.4-1_all.deb
 ed44cf93fad0d8877465d73448aff7c82e664951 34336 
python3-nagiosplugin_1.2.4-1_all.deb
Checksums-Sha256:
 fca2a3f8d3d87c066b4abe7503e0d4423713c3ccfb4d8aba854d244cd402b6b2 1959 
nagiosplugin_1.2.4-1.dsc
 6b020aca516f3643ad02378866d382f0296bf378fa3874d9b2e1d3cc6135f8bb 38290 
nagiosplugin_1.2.4.orig.tar.gz
 ba7d9b19c2858566fe511a3f02162c4ddda64b1428fc319b42c4d1144ceabc70 3680 
nagiosplugin_1.2.4-1.debian.tar.xz
 e8636a8b08504c42c30587beed38e8903c868151d01c4f6c79c7ed54227ab81d 6489 
nagiosplugin_1.2.4-1_amd64.buildinfo
 5714ea9357c8104a8941b787355ddc7d768ae67386c2d934f132fd9c89ecca00 34260 
python-nagiosplugin_1.2.4-1_all.deb
 4f5ccc9ce48cc9b61a06fb0966c09e72593608afccc58b2546b9d8248b714a6c 34336 
python3-nagiosplugin_1.2.4-1_all.deb
Files:
 f58268bb6500d883224fded83780e6f6 1959 python optional nagiosplugin_1.2.4-1.dsc
 f22ee91fc89d0c442803bdf27fab8c99 38290 python optional 
nagiosplugin_1.2.4.orig.tar.gz
 914549cb998c028b7a53d91298d434ef 3680 python optional 
nagiosplugin_1.2.4-1.debian.tar.xz
 d449c96301b07fbd246beb9886a7ce81 6489 python optional 
nagiosplugin_1.2.4-1_amd64.buildinfo
 e08f002332e6b903e8ecf49cf0cdbad5 34260 python optional 
python-nagiosplugin_1.2.4-1_all.deb
 37a361a8990acb88360d84d626943da5 34336 python optional 
python3-nagiosplugin_1.2.4-1_all.deb

Bug#867899:

[Neil Muller]

This specific failure has been fixed in SQLObject 3.3.0 .

However, 3.3.0 fails sporadically with python 3.6 and python 3.5 due
to a different error. This is still being investigated (See
https://github.com/sqlobject/sqlobject/issues/135 ). Once that issue
has been solved, I'll look at uploading an updated package.

Processed: Bug#867410 marked as pending

[Debian Bug Tracking System]

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

> tag 867410 pending
Bug #867410 [python3-nagiosplugin] python3-nagiosplugin; missing dependencies
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#867410: marked as pending

[Jan Dittberner]

tag 867410 pending
thanks

Hello,

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


https://anonscm.debian.org/cgit/python-modules/packages/nagiosplugin.git/commit/?id=fee36bc

---
commit fee36bc5e05c7bec144c742d78b223db8f46cac5
Author: Jan Dittberner 
Date:   Tue Jul 18 14:04:42 2017 +0200

Fix "python3-nagiosplugin; missing dependencies" by fixing a typo in 
debian/control stanza (Closes: #867410)

diff --git a/debian/changelog b/debian/changelog
index 7dee86e..89ba1e9 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,7 +1,12 @@
 nagiosplugin (1.2.2-2) UNRELEASED; urgency=medium
 
+  [ Ondřej Nový ]
   * Fixed VCS URL (https)
 
+  [ Jan Dittberner ]
+  * Fix "python3-nagiosplugin; missing dependencies" by fixing a typo in
+debian/control stanza (Closes: #867410)
+
  -- Ondřej Nový   Tue, 29 Mar 2016 21:44:22 +0200
 
 nagiosplugin (1.2.2-1) unstable; urgency=medium

Bug#868500: atril: CVE-2017-1000083

[Santiago Ruano Rincón]

Control: tags -1 + patch

On Sun, 16 Jul 2017 08:19:43 +0200 Salvatore Bonaccorso  
wrote:
...
> the following vulnerability was published for atril.
> 
> CVE-2017-183[0]:
> Evince command injection vulnerability in CBT handler
...

Please, find attached the patch backported from evince's fix.

Cheers,

  -- Santiago
Origin: https://bugzilla.gnome.org/show_bug.cgi?id=784630
Reviewed-by: Santiago R.R. 
Bug-Debian: http://bugs.debian.org/868500

From 717df38fd8509bf883b70d680c9b1b3cf36732ee Mon Sep 17 00:00:00 2001
From: Bastien Nocera 
Date: Thu, 6 Jul 2017 20:02:00 +0200
Subject: [PATCH] comics: Remove support for tar and tar-like commands

When handling tar files, or using a command with tar-compatible syntax,
to open comic-book archives, both the archive name (the name of the
comics file) and the filename (the name of a page within the archive)
are quoted to not be interpreted by the shell.

But the filename is completely with the attacker's control and can start
with "--" which leads to tar interpreting it as a command line flag.

This can be exploited by creating a CBT file (a tar archive with the
.cbt suffix) with an embedded file named something like this:
"--checkpoint-action=exec=bash -c 'touch ~/hacked;'.jpg"

CBT files are infinitely rare (CBZ is usually used for DRM-free
commercial releases, CBR for those from more dubious provenance), so
removing support is the easiest way to avoid the bug triggering. All
this code was rewritten in the development release for GNOME 3.26 to not
shell out to any command, closing off this particular attack vector.

This also removes the ability to use libarchive's bsdtar-compatible
binary for CBZ (ZIP), CB7 (7zip), and CBR (RAR) formats. The first two
are already supported by unzip and 7zip respectively. libarchive's RAR
support is limited, so unrar is a requirement anyway.

Discovered by Felix Wilhelm from the Google Security Team.

https://bugzilla.gnome.org/show_bug.cgi?id=784630

-Index: atril-1.16.1/backend/comics/comics-document.c
===
--- atril-1.16.1.orig/backend/comics/comics-document.c
+++ atril-1.16.1/backend/comics/comics-document.c
@@ -44,8 +44,7 @@ typedef enum
 	RARLABS,
 	GNAUNRAR,
 	UNZIP,
-	P7ZIP,
-	TAR
+	P7ZIP
 } ComicBookDecompressType;
 
 typedef struct _ComicsDocumentClass ComicsDocumentClass;
@@ -105,9 +104,6 @@ static const ComicBookDecompressCommand
 
 /* 7zip */
 	{NULL   , "%s l -- %s" , "%s x -y %s -o%s", FALSE, OFFSET_7Z},
-
-/* tar */
-	{"%s -xOf"  , "%s -tf %s"  , NULL , FALSE, NO_OFFSET}
 };
 
 static void   comics_document_document_thumbnails_iface_init (EvDocumentThumbnailsInterface *iface);
@@ -355,13 +351,6 @@ comics_check_decompress_command	(gchar
 			comics_document->command_usage = GNAUNRAR;
 			return TRUE;
 		}
-		comics_document->selected_command =
-g_find_program_in_path ("bsdtar");
-		if (comics_document->selected_command) {
-			comics_document->command_usage = TAR;
-			return TRUE;
-		}
-
 	} else if (g_content_type_is_a (mime_type, "application/x-cbz") ||
 		   g_content_type_is_a (mime_type, "application/zip")) {
 		/* InfoZIP's unzip program */
@@ -374,12 +363,6 @@ comics_check_decompress_command	(gchar
 			comics_document->command_usage = UNZIP;
 			return TRUE;
 		}
-		comics_document->selected_command =
-g_find_program_in_path ("bsdtar");
-		if (comics_document->selected_command) {
-			comics_document->command_usage = TAR;
-			return TRUE;
-		}
 
 	} else if (g_content_type_is_a (mime_type, "application/x-cb7") ||
 		   g_content_type_is_a (mime_type, "application/x-7z-compressed")) {
@@ -403,27 +386,6 @@ comics_check_decompress_command	(gchar
 			comics_document->command_usage = P7ZIP;
 			return TRUE;
 		}
-		comics_document->selected_command =
-g_find_program_in_path ("bsdtar");
-		if (comics_document->selected_command) {
-			comics_document->command_usage = TAR;
-			return TRUE;
-		}
-	} else if (g_content_type_is_a (mime_type, "application/x-cbt") ||
-		   g_content_type_is_a (mime_type, "application/x-tar")) {
-		/* tar utility (Tape ARchive) */
-		comics_document->selected_command =
-g_find_program_in_path ("tar");
-		if (comics_document->selected_command) {
-			comics_document->command_usage = TAR;
-			return TRUE;
-		}
-		comics_document->selected_command =
-g_find_program_in_path ("bsdtar");
-		if (comics_document->selected_command) {
-			comics_document->command_usage = TAR;
-			return TRUE;
-		}
 	} else {
 		g_set_error (error,
 			 EV_DOCUMENT_ERROR,
Index: atril-1.16.1/configure.ac
===
--- atril-1.16.1.orig/configure.ac
+++ atril-1.16.1/configure.ac
@@ -625,7 +625,7 @@ if test "x$enable_tiff" = "xyes"; then
 ATRIL_MIME_TYPES="${ATRIL_MIME_TYPES}image/tiff;"
 fi
 if test "x$enable_comics" = "xyes"; then
-ATRIL_MIME_TYPES="${ATRIL_MIME_TYPES}application/x-cbr;application/x-cbz;appli

Processed: Re: atril: CVE-2017-1000083

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #868500 [src:atril] atril: CVE-2017-183
Added tag(s) patch.

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

Bug#867076: marked as done (dune-grid: Build-dependency pgf no longer available)

[Debian Bug Tracking System]

Your message dated Tue, 18 Jul 2017 13:04:15 +
with message-id 
and subject line Bug#867076: fixed in dune-grid 2.5.1-1
has caused the Debian Bug report #867076,
regarding dune-grid: Build-dependency pgf no longer available
to be marked as done.

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

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


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

The texlive-pictures package ships still ships pgf but no longer
provides it in the dependencies.
--- End Message ---
--- Begin Message ---
Source: dune-grid
Source-Version: 2.5.1-1

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 18 Jul 2017 12:10:59 +0200
Source: dune-grid
Binary: libdune-grid-dev libdune-grid-doc
Architecture: source
Version: 2.5.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Ansgar Burchardt 
Description:
 libdune-grid-dev - toolbox for solving PDEs -- grid interface (development 
files)
 libdune-grid-doc - toolbox for solving PDEs -- grid interface (documentation)
Closes: 867076
Changes:
 dune-grid (2.5.1-1) unstable; urgency=medium
 .
   * New upstream release.
   * Build-Depend on texlive-pictures instead of pgf. (Closes: #867076)
   * debian/copyright: Update URLs.
   * Bumped Standards-Version to 4.0.0 (no changes).
Checksums-Sha1:
 7459225ae055dbeacbddf2c1e73387fe7c5c22e9 2434 dune-grid_2.5.1-1.dsc
 0342a542c94d816aaa16185eb01ea874bd5accc3 2644096 dune-grid_2.5.1.orig.tar.xz
 0245663c6d5618923576bb1d5cd4669940b120c4 5828 dune-grid_2.5.1-1.debian.tar.xz
Checksums-Sha256:
 1ace4a0bb9e5aad9221f822e3a8a2822a30d03998346984942a49468d24a610b 2434 
dune-grid_2.5.1-1.dsc
 ccfad69f1719dbf0ff10928afb7f7ff3ca7476101633dd12a6c863954502c81a 2644096 
dune-grid_2.5.1.orig.tar.xz
 b51bf16f50a9b2ee04378a57af9520fa7254021bba5e0cbd63ab9a9089bee0ce 5828 
dune-grid_2.5.1-1.debian.tar.xz
Files:
 942dd6045288d0a07a187be9dcf9ff1f 2434 libs optional dune-grid_2.5.1-1.dsc
 51e6f02cbfb3a416091b4acac95709bd 2644096 libs optional 
dune-grid_2.5.1.orig.tar.xz
 88e4e85e79deed1fefefa5baf7ef7252 5828 libs optional 
dune-grid_2.5.1-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEE6XYjQ9o8g2p4zSVKamMCj1p06JMFAlluBZwSHGFuc2dhckBk
ZWJpYW4ub3JnAAoJEGpjAo9adOiTUuIQAK/pFgVvnGnjVAsxPs3hUsJ5nzx4yHaT
Z2CHwoyAUD96hFJ8RH7i83w+gws7JFvJv4vq42LM2/6nHVWCWaqB1fb+FGFSlp4W
WPTOuqhFF1MQdinImb16eC09VLr0R0tsGDt5Y7hEWQ1IRQl8tLF8G7TIAYQQkYvd
EU75ag9jdqDaqaSWSWavBD/lULhVZGMw3WAbPoo24fKj6vy5mPPn9OcOolNOSxAc
xr60qCFqLBr6NBkKE0o6X/6HI5dOjrgoju6+wNf/cJ9Mnn2AE729fHDw6r5araXa
I/fdnIfsLmThhNMU3LEvrWOcFDBxZh+OIziLeWnr2poccBCeBjHp3o+LjP3I/ZBP
vWnjSt7EQGoC/xpxadekfIhFWg50yRKV8BQ3mJn0T3NKvqUCo1o5entvC3ZyR3oF
2klUbKQWt8uMuZGpTW9QU3pZgwEa5vH57ITYY+OHYOHvtdoULno7EQWoT2QsNgB6
lhgvb+QJEAreg7DRu/qjrrQ6EgRSWLHcok6TSlr2VD/ogz7W8b6QKKyKwE239Gp/
uuVIj4h5YWfvdWNtT7ko6MREn8hLL/mlTpfIPjAkOqyEXpDwLYEpSeNFY1YENmwc
7szrY30/sPoD3K8a2pndFx2zh6ozmorygs02jdrXzPCtQZ4oyhf18BOc92YSV7yU
2YwSsk3NQtvq
=Rka/
-END PGP SIGNATURE End Message ---

Bug#867079: marked as done (dune-localfunctions: Build-dependency pgf no longer available)

[Debian Bug Tracking System]

Your message dated Tue, 18 Jul 2017 13:04:23 +
with message-id 
and subject line Bug#867079: fixed in dune-localfunctions 2.5.1-1
has caused the Debian Bug report #867079,
regarding dune-localfunctions: Build-dependency pgf no longer available
to be marked as done.

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

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


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

The texlive-pictures package ships still ships pgf but no longer
provides it in the dependencies.
--- End Message ---
--- Begin Message ---
Source: dune-localfunctions
Source-Version: 2.5.1-1

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 18 Jul 2017 12:08:08 +0200
Source: dune-localfunctions
Binary: libdune-localfunctions-dev libdune-localfunctions-doc
Architecture: source
Version: 2.5.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Ansgar Burchardt 
Description:
 libdune-localfunctions-dev - toolbox for solving PDEs -- local basis 
(development files)
 libdune-localfunctions-doc - toolbox for solving PDEs -- local basis 
(documentation)
Closes: 867079
Changes:
 dune-localfunctions (2.5.1-1) unstable; urgency=medium
 .
   * New upstream release.
   * Build-Depend on texlive-pictures instead of pgf. (Closes: #867079)
   * debian/copyright: Update URLs.
   * Bumped Standards-Version to 4.0.0 (no changes).
Checksums-Sha1:
 4e0c20d917fc97eac1d72ee1477dc99a2f69408a 2789 dune-localfunctions_2.5.1-1.dsc
 a8225ef3ba19d8226e41a1c5e587f7650499eeca 179554 
dune-localfunctions_2.5.1.orig.tar.gz
 95ae74586a3f1ae42f58dfe54c2a673e5ee9102f 1061 
dune-localfunctions_2.5.1.orig.tar.gz.asc
 a6a38504e0a34971416b29271db67fd5c64c4beb 3316 
dune-localfunctions_2.5.1-1.debian.tar.xz
Checksums-Sha256:
 969d4e7760a4934fa467690fddeb412cc2229216484548452eaf1c94ac2c8af6 2789 
dune-localfunctions_2.5.1-1.dsc
 4308d45132f463ca6c37cf59f0ef52b30b13dc01afba782c467e7ed6511dd0c0 179554 
dune-localfunctions_2.5.1.orig.tar.gz
 954f746d0407a26ba87154ca5c58c8dc34b2f3103c445eac1d8b855faf5c283d 1061 
dune-localfunctions_2.5.1.orig.tar.gz.asc
 9a0dc3adc8b7af1d21653c90736ff937fa4c7f3abd921966e23f7abe6ea691ec 3316 
dune-localfunctions_2.5.1-1.debian.tar.xz
Files:
 ea3cc7ecb5dcb15af356de0c86430159 2789 libs optional 
dune-localfunctions_2.5.1-1.dsc
 a4a6d31714d9a46ac8be2ad8303e4531 179554 libs optional 
dune-localfunctions_2.5.1.orig.tar.gz
 b9003be000d6960de4fea7a186941f50 1061 libs optional 
dune-localfunctions_2.5.1.orig.tar.gz.asc
 103c7a03f4b3cfff2912e3e38d3f5aee 3316 libs optional 
dune-localfunctions_2.5.1-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEE6XYjQ9o8g2p4zSVKamMCj1p06JMFAlluBacSHGFuc2dhckBk
ZWJpYW4ub3JnAAoJEGpjAo9adOiTN1UP/03KW9cX+WpIauZjj02X1C3VydKw8XxU
OLn9kGxBZmt9ghdWodHVN2TOqstabQlNUJypkSfwj7c5K0UXrA5GbQKgOl7Dl1PA
bagrtS5CxOCUFQDgOsQi/eA8fQXBm/GDYDLkz5M2ymXbDZZc7kUPUOmo9rJjRAKo
Nsh0WaGIj3dzXoTQ24/lKswXL9wJN06wWMKm3TrPYcBqiFv/XWHffoVtmeQjcS9h
cf2Ld/oOP2WkKmd+ZqAffjufGIWVAfADJAkjnr0JQz2gE8JaLh8P/Ye4tdCZQser
eFtBoXW+iS+8EhfOQ/pTmOTo4jKSoRJ9/xxp5m+V1fjcBiPfM0HfGvZRlmGwJ1Gd
GljOXvmWmTrHwpsHBGL+mhXwtDGjOojnoVJ0GDzKDsi2rQmzNU8q8OatNmWjC/ml
mwgo8Y1RvhwXp/VPlJRoEBeNLWKZlGLIfFxs+9DbmHjj7CjKs/t5BDgoRkUpT1Cb
Dzl3gJh43bRIvRNBX3LKdAPNt6sMp3evKrPZMdOk4s6s1sYMVKwiEpwuwGV/5IQn
Qbci1nZerBJUw9IzRDTzlQS/x5Wu/j2DppXce55UIWH/hTcnLm/oDwqyNxfse0+s
P6KNb+qKD8mMs1KZ0QXsxhENzLtxxwuRC99/VrxHRs7l/nYgO+frfQdaQLzSaSit
hpUfMLOrQRJ/
=/djY
-END PGP SIGNATURE End Message ---

Bug#868774: rabbit FTBFS: test failures

[Adrian Bunk]

Source: rabbit
Version: 2.1.9-2
Severity: serious
Tags: buster sid

Some recent change in unstable makes rabbit FTBFS:

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

...
┌──┐
│ Run tests for ruby2.3 from debian/ruby-tests.rb  │
└──┘

RUBYLIB=/build/1st/rabbit-2.1.9/debian/rabbit/usr/lib/ruby/vendor_ruby:. 
GEM_PATH=debian/rabbit/usr/share/rubygems-integration/all:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
 ruby2.3 debian/ruby-tests.rb
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: already initialized constant 
Pango::LOG_DOMAIN
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: previous definition of 
LOG_DOMAIN was here
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: already initialized constant 
Pango::LOG_DOMAIN
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: previous definition of 
LOG_DOMAIN was here
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: already initialized constant 
Pango::LOG_DOMAIN
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: previous definition of 
LOG_DOMAIN was here
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: already initialized constant 
Pango::LOG_DOMAIN
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: previous definition of 
LOG_DOMAIN was here
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: already initialized constant 
Pango::LOG_DOMAIN
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: previous definition of 
LOG_DOMAIN was here
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: already initialized constant 
Pango::LOG_DOMAIN
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: previous definition of 
LOG_DOMAIN was here
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: already initialized constant 
Pango::LOG_DOMAIN
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: previous definition of 
LOG_DOMAIN was here
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: already initialized constant 
Pango::LOG_DOMAIN
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: previous definition of 
LOG_DOMAIN was here
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: already initialized constant 
Pango::LOG_DOMAIN
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: previous definition of 
LOG_DOMAIN was here
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: already initialized constant 
Pango::LOG_DOMAIN
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: previous definition of 
LOG_DOMAIN was here
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: already initialized constant 
Pango::LOG_DOMAIN
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: previous definition of 
LOG_DOMAIN was here
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: already initialized constant 
Pango::LOG_DOMAIN
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: previous definition of 
LOG_DOMAIN was here
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: already initialized constant 
Pango::LOG_DOMAIN
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: previous definition of 
LOG_DOMAIN was here
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: already initialized constant 
Pango::LOG_DOMAIN
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: previous definition of 
LOG_DOMAIN was here
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: already initialized constant 
Pango::LOG_DOMAIN
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: previous definition of 
LOG_DOMAIN was here
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: already initialized constant 
Pango::LOG_DOMAIN
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: previous definition of 
LOG_DOMAIN was here
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: already initialized constant 
Pango::LOG_DOMAIN
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: previous definition of 
LOG_DOMAIN was here
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: already initialized constant 
Pango::LOG_DOMAIN
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: previous definition of 
LOG_DOMAIN was here
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: already initialized constant 
Pango::LOG_DOMAIN
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: previous definition of 
LOG_DOMAIN was here
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: already initialized constant 
Pango::LOG_DOMAIN
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: previous definition of 
LOG_DOMAIN was here
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: already initialized constant 
Pango::LOG_DOMAIN
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: previous definition of 
LOG_DOMAIN was here
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: already initialized constant 
Pango::LOG_DOMAIN
/usr/lib/ruby/vendor_ruby/pango.rb:32: warning: previous definition of 
LOG_DOMAIN was here
/usr/lib/ruby/vendor_ruby/pango.rb:32: wa

Bug#863110: openvpn: VPN remains connected, but network is unreachable after 30-45 min and requires reconnect

[Patrick Matthäi]

Am 18.07.2017 um 13:29 schrieb Bernhard Schmidt:
 I've browsed through the git commits between 2.4.0 and 2.4.3, these
 might be relevant here

 https://community.openvpn.net/openvpn/ticket/812
 https://community.openvpn.net/openvpn/ticket/887

 Are you able to build a version with these patches applied yourself?
>>> I will build it for one of the notworking nodes and see what happens and
>>> give a feedback
>> Yeah very nice! With both patches applied it is working :D Like the
>> version 2.4.3-4 I get now a "NOTE: Pulled options changed on restart,
>> will need to close and reopen TUN/TAP device", all routes are removed
>> and readded and the connection works again. Two hosts, which are not
>> working after a restart of the server, do not have got this and refuse
>> to work.
> Can you try to test which of those it is? I need a specific patch to get
> into stable.

I have tested it three times, it is definitly
https://community.openvpn.net/openvpn/ticket/812 which fixes this issue

>
>> Would love to see these patches in 9.1 :)
> 9.1 is already frozen, but I will submit it into 9.2 as soon as I know
> which patch it is.

Urgs right.. ;)

-- 
/*
Mit freundlichem Gruß / With kind regards,
 Patrick Matthäi
 GNU/Linux Debian Developer

  Blog: http://www.linux-dev.org/
E-Mail: pmatth...@debian.org
patr...@linux-dev.org
*/

Bug#868773: khal FTBFS: AssertionError: assert not OSError(6, 'No such device or address')

[Adrian Bunk]

Source: khal
Version: 1:0.9.6-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=khal&arch=all&ver=1:0.9.6-1&stamp=1500381224&raw=0

...
=== FAILURES ===
 test_import_from_stdin 

runner = 

def test_import_from_stdin(runner):
ics_data = 'This is some really fake icalendar data'

with mock.patch('khal.controllers.import_ics') as mocked_import:
runner = runner()
result = runner.invoke(main_khal, ['import'], input=ics_data)

>   assert not result.exception
E   AssertionError: assert not OSError(6, 'No such device or address')
E+  where OSError(6, 'No such device or address') = .exception

tests/cli_test.py:505: AssertionError
 test_printics_read_from_stdin _

runner = 

def test_printics_read_from_stdin(runner):
runner = runner(command='printics')
result = runner.invoke(main_khal, ['printics'], 
input=_get_text('cal_d'))
>   assert not result.exception
E   AssertionError: assert not OSError(6, 'No such device or address')
E+  where OSError(6, 'No such device or address') = .exception

tests/cli_test.py:683: AssertionError
== 2 failed, 261 passed, 7 skipped, 3 xfailed in 9.52 seconds ==
E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: cd 
/<>/.pybuild/pythonX.Y_3.6/build; python3.6 -m pytest tests
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.6 3.5 
returned exit code 13
debian/rules:26: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 25

Bug#868053: marked as done (sunpy: FTBFS with python-astropy >= 2)

[Debian Bug Tracking System]

Your message dated Tue, 18 Jul 2017 12:52:03 +
with message-id 
and subject line Bug#868053: fixed in sunpy 0.7.9-1
has caused the Debian Bug report #868053,
regarding sunpy: FTBFS with python-astropy >= 2
to be marked as done.

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

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


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

sunpy FTBFS with testsuite when built using python-astropy from unstable:

> python -m pytest sunpy -k "not figure and not online"
> = test session starts 
> ==
> platform linux2 -- Python 2.7.13, pytest-3.0.6, py-1.4.34, pluggy-0.4.0
> rootdir: /<>, inifile: setup.cfg
> collected 618 items / 36 errors
> 
>  ERRORS 
> 
> ___ ERROR collecting sunpy/coordinates/tests/test_frameattributes.py 
> ___
> ImportError while importing test module 
> '/<>/sunpy/coordinates/tests/test_frameattributes.py'.
> Hint: make sure your test modules/packages have valid Python names.
> Traceback:
> sunpy/coordinates/__init__.py:3: in 
> from .frames import *
> sunpy/coordinates/frames.py:17: in 
> from astropy.coordinates import FrameAttribute
> E   ImportError: cannot import name FrameAttribute

James



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: sunpy
Source-Version: 0.7.9-1

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

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

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

Debian distribution maintenance software
pp.
Ole Streicher  (supplier of updated sunpy package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 18 Jul 2017 13:38:04 +0200
Source: sunpy
Binary: python-sunpy python3-sunpy
Architecture: source
Version: 0.7.9-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Astronomy Team 

Changed-By: Ole Streicher 
Description:
 python-sunpy - Software library for solar physics based on Python
 python3-sunpy - Software library for solar physics based on Python 3
Closes: 868053
Changes:
 sunpy (0.7.9-1) unstable; urgency=medium
 .
   * New upstream version 0.7.9. Closes: #868053
   * Rediff patches
Checksums-Sha1:
 8e6323e07338056bce04690ca4b2d2d6c154 2743 sunpy_0.7.9-1.dsc
 fd5433d70592ac3590c4fb3ed15151f7e8c4d42f 5690849 sunpy_0.7.9.orig.tar.gz
 577af607e1dc422cbe1d5c925e9f8d2d00a8d3bc 8116 sunpy_0.7.9-1.debian.tar.xz
Checksums-Sha256:
 b160aca62bc4b73a3905ce4cb2022baa59b1de61e847566b9d1e8549fb334c43 2743 
sunpy_0.7.9-1.dsc
 359961f62a32df69b2df2cd5390040fa27b7522066fb546469fc9f485d2d0a57 5690849 
sunpy_0.7.9.orig.tar.gz
 c0f499cbba2ef19ea43f9d4fd6317f3cdfa29b630972947a282f9f5dd13fc5b0 8116 
sunpy_0.7.9-1.debian.tar.xz
Files:
 65e59f0ae2dee2c603f5ff792f9b8891 2743 python optional sunpy_0.7.9-1.dsc
 a1c6cec0d4606527075b5717dbf2108b 5690849 python optional 
sunpy_0.7.9.orig.tar.gz
 c168977d8a8723d32932306e62499fea 8116 python optional 
sunpy_0.7.9-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAllt9nEACgkQcRWv0HcQ
3Pef2Q//aFZoOQ1es79SAP6tDR+AXIe9AArO5qIOYpsxtU5BBYBwaMKKCUzgwJz9
l20jdQERHSQl3rlnWYharFP+a3pkLmFP/FTd3Uf16O29u+Ofm1TuABBa3+OBvCCO
nPle/yBv7QPmf1io8yTGJY/TW4KezzZP670fRUhhZzFRtym3ap5lE/fnLolGBQUl
ObSv1ECn5YhC02/X4B5IPbidmejIzn3iWNNY9W/Pf8wBLerCJkLiWGymtUb8ccrF
Cz6FV8BFDDKUY2KQ1qJyfhEMz5d2ZtTtASRVYJspBa9w/3YlKdvBpSxDWVvi6Uzc
5LPUJDuVPsSmF9347wWShgRK4uM9KvkHOHvK+Yy7MfwApZ9Xw6qmJ4siqDTC5Xr5
L2URVv6ntYzvwRmFwt77HlmBk+S1kwtiB94gqedFItxFjw8A2AYOw9rXMd8fa13s
MteFMbJP191kqEOAs5EaKIeYrLgJueXhmNflF9wZNk1EJhXzkMN6Zd+tdDMbS+nD
KUalHdoku59+ansIuFxAXHFaQ8o0sUKfjM8P34qkFCVRsuWQmMo9VxwdpLNlXA/w
YIEjcXtx7SPSwcXAUXhFWb5gX5eojP7ndAqEhJV8drJi1AncqsUS74A81KIUB1MV
46Ea7DdhY9anJhl+c3arxLhCIWfq6bQkXP+fTjRTZctVzkA46SQ=
=dS7Y
-END PGP SIGNATURE End Message ---

Bug#868587: marked as done (gnuastro FTBFS on big endian: test failures)

[Debian Bug Tracking System]

Your message dated Tue, 18 Jul 2017 12:19:25 +
with message-id 
and subject line Bug#868587: fixed in gnuastro 0.3.33-1
has caused the Debian Bug report #868587,
regarding gnuastro FTBFS on big endian: test failures
to be marked as done.

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

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


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

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

...
SKIP: lib/multithread.sh


psf.fits does not exist.
SKIP lib/multithread.sh (exit status: 77)

SKIP: arithmetic/snimage.sh
===

convolve_spatial_noised_labeled.fits does not exist.
SKIP arithmetic/snimage.sh (exit status: 77)

SKIP: arithmetic/where.sh
=

convolve_spatial_noised_labeled.fits does not exist.
SKIP arithmetic/where.sh (exit status: 77)

SKIP: arithmetic/or.sh
==

convolve_spatial_noised_labeled.fits does not exist.
SKIP arithmetic/or.sh (exit status: 77)

SKIP: buildprog/simpleio.sh
===

psf.fits does not exist.
SKIP buildprog/simpleio.sh (exit status: 77)

SKIP: convertt/fitstotxt.sh
===

psf.fits does not exist.
SKIP convertt/fitstotxt.sh (exit status: 77)

SKIP: convertt/fitstojpeg.sh


psf.fits does not exist.
SKIP convertt/fitstojpeg.sh (exit status: 77)

SKIP: convertt/blankch.sh
=

psf.fits does not exist.
SKIP convertt/blankch.sh (exit status: 77)

SKIP: convertt/jpegtotxt.sh
===

psf.jpg does not exist.
SKIP convertt/jpegtotxt.sh (exit status: 77)

SKIP: convertt/fitstojpegcmyk.sh


psf.fits does not exist.
SKIP convertt/fitstojpegcmyk.sh (exit status: 77)

SKIP: convertt/jpegtofits.sh


blankch.jpg does not exist.
SKIP convertt/jpegtofits.sh (exit status: 77)

SKIP: convertt/fitstopdf.sh
===

crop_section.fits does not exist.
SKIP convertt/fitstopdf.sh (exit status: 77)

SKIP: convolve/spatial.sh
=

mkprofcat1.fits does not exist.
SKIP convolve/spatial.sh (exit status: 77)

SKIP: convolve/frequency.sh
===

mkprofcat1.fits does not exist.
SKIP convolve/frequency.sh (exit status: 77)

SKIP: crop/imgcat.sh


mkprofcat1.fits does not exist.
SKIP crop/imgcat.sh (exit status: 77)

SKIP: crop/wcscat.sh


mkprofcat*.fits doesn't exist.
SKIP crop/wcscat.sh (exit status: 77)

SKIP: crop/imgcenter.sh
===

mkprofcat1.fits does not exist.
SKIP crop/imgcenter.sh (exit status: 77)

SKIP: crop/imgcenternoblank.sh
==

mkprofcat1.fits does not exist.
SKIP crop/imgcenternoblank.sh (exit status: 77)

SKIP: crop/section.sh
=

mkprofcat1.fits does not exist.
SKIP crop/section.sh (exit status: 77)

SKIP: crop/wcscenter.sh
===

mkprofcat*.fits does not exist.
SKIP crop/wcscenter.sh (exit status: 77)

SKIP: crop/imgpolygon.sh


mkprofcat1.fits does not exist.
SKIP crop/imgpolygon.sh (exit status: 77)

SKIP: crop/imgoutpolygon.sh
===

mkprofcat1.fits does not exist.
SKIP crop/imgoutpolygon.sh (exit status: 77)

SKIP: crop/wcspolygon.sh


mkprofcat*.fits doesn't exist.
SKIP crop/wcspolygon.sh (exit status: 77)

SKIP: fits/write.sh
===

mkprofcat1.fits does not exist.
SKIP fits/write.sh (exit status: 77)

SKIP: fits/print.sh
===

fitstest.fits does not exist.
SKIP fits/print.sh (exit status: 77)

SKIP: fits/update.sh


fitstest.fits does not exist.
SKIP fits/update.sh (exit status: 77)

SKIP: fits/delete.sh


fitstest.fits does not exist.
SKIP fits/delete.sh (exit status: 77)

SKIP: fits/copyhdu.sh
=

fitstest.fits does not exist.
SKIP fits/copyhdu.sh (exit status: 77)

SKIP: mkcatalog/simple.sh
=

convolve_spatial_noised_labeled.fits does not exist.
SKIP mkcatalog/simple.sh (exit status: 77)

SKIP: mkcatalog/aperturephot.sh
===

convolve_spatial_noised_labeled.fits does not exist.
SKIP mkcatalog/aperturephot.sh (exit status: 77)

SKIP: mknoise/addnoise.sh
=

convolve_spatial.fits does not exist.
SKIP mknoise/addnoise.sh (exit status: 77)

FAIL: mkprof/mosaic1.sh
===

/<>/bin/mkpro

Bug#868586: marked as done (gnuastro FTBFS on 32bit: FAIL: mkprof/radeccat.sh)

[Debian Bug Tracking System]

Your message dated Tue, 18 Jul 2017 12:19:25 +
with message-id 
and subject line Bug#868586: fixed in gnuastro 0.3.33-1
has caused the Debian Bug report #868586,
regarding gnuastro FTBFS on 32bit: FAIL: mkprof/radeccat.sh
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.)


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

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

...
FAIL: mkprof/radeccat.sh


./mkprof/radeccat.sh: line 51: 31464 Segmentation fault  $execname $cat 
--ccol=RA --ccol=Dec --mode=wcs --naxis=100,100
FAIL mkprof/radeccat.sh (exit status: 139)


Testsuite summary for GNU Astronomy Utilities 0.3.31-8415

# TOTAL: 51
# PASS:  50
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See tests/test-suite.log
Please report to bug-gnuas...@gnu.org

Makefile:1974: recipe for target 'test-suite.log' failed
make[5]: *** [test-suite.log] Error 1
--- End Message ---
--- Begin Message ---
Source: gnuastro
Source-Version: 0.3.33-1

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

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

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

Debian distribution maintenance software
pp.
Mohammad Akhlaghi  (supplier of updated gnuastro package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 16 Jul 2017 00:08:12 +0200
Source: gnuastro
Binary: libgnuastro2 libgnuastro-dev gnuastro
Architecture: source
Version: 0.3.33-1
Distribution: unstable
Urgency: low
Maintainer: Debian Astro Team 
Changed-By: Mohammad Akhlaghi 
Description:
 gnuastro   - GNU Astronomy Utilities programs
 libgnuastro-dev - GNU Astronomy Utilities development files
 libgnuastro2 - GNU Astronomy Utilities shared libraries
Closes: 868586 868587
Changes:
 gnuastro (0.3.33-1) unstable; urgency=low
 .
   * Crashes on 32-bit and big-endian systems corrected. (Closes: #868586)
 (Closes: #868587)
Checksums-Sha1:
 c2020b5846641f197cf7297919387e69b11f848b 2178 gnuastro_0.3.33-1.dsc
 817caed36ecbc7de9c59c4edc67393652b6ad186 4544314 gnuastro_0.3.33.orig.tar.gz
 2ef8e7df86f05c740275a919e40a44d6886e8f4f 5968 gnuastro_0.3.33-1.debian.tar.xz
Checksums-Sha256:
 5463bf3ce4991a06b99d36d785924b6daf3e5a1ead907aec1bafb8842b3ae280 2178 
gnuastro_0.3.33-1.dsc
 69f7f8286db8cbb53b057985b06a344fc7e674ed539d08318fd76d228d26ba38 4544314 
gnuastro_0.3.33.orig.tar.gz
 87b809a2428ade986e7ddd763a3b00f60877879c20036053e2bd45a7ab9add47 5968 
gnuastro_0.3.33-1.debian.tar.xz
Files:
 8066f9e17378755b6561f8051f06abb9 2178 science optional gnuastro_0.3.33-1.dsc
 ee1b44cde353c17be674af225c9a9019 4544314 science optional 
gnuastro_0.3.33.orig.tar.gz
 9da7e362f2e7c323a5f60be76cd2c0ab 5968 science optional 
gnuastro_0.3.33-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAllt+aYACgkQcRWv0HcQ
3Pc60BAA3h9LL19ws6Z/x/Q7ReyOdOWYPAlWqq4Yd1Je+gayxfnoDyD5YCc4tZbu
Uor3wkK/gppA6C1RuMNE2MZEAH4dnm/Hj8QQ0fhLgPm2GjoH5WIbAn33Jv1Li+/v
gYbkHvE22Ea9lDd4zQ4F9Bam8HiXuCvNDWzEiA0zfpOn+UoBvHiY5AbzcoTpaouM
m2ZxuwkgjuR61kpAlrGh+Ptc3jA+MINxgAGHkt6bBLnYID8qii1QOu4HzOgpauHZ
X7l4M1jepEQ1wz1rKbTOeiMEqEJNZ87LWbEyQijtSw39P1y9xPcBUSKPjE43S8IE
OFgIF58vw3T2jhvHfn0pn2bhsZzYE5db0HsSoG0FGrStzeaTKetqseX0UkheySid
5Mkok7L4INczXvap2We6KNWF/hbiM/j8rF9Ft+RdBDxSd4jDSbg+cNdUXqpb3fgJ
yzslIXQ9atZdWVytP/vvvDTkjhJJYAiH8aZBPvIx72I1zqD62E6pehTOvO5C/qgL
4s1H/PR/Y18TxlU7wylQBJZIN4P9VBC9eXnHv/CPQ0h5ExUs73upZnEI8q3CxFyd
l5bupiITlyoI59uf9iiJQC4okooPteQ46UlvHaUjBDKh5sRr0mjOulFLlMbr6A5D
+AFkOJhfzdPpGlFWLK014/pvbrm4oEFAIA5L+xCugM40d/TjMLs=
=52f7
-END PGP SIGNATURE End Message ---

Bug#867797: marked as done (khal FTBFS with python 3.6 as supported version)

[Debian Bug Tracking System]

Your message dated Tue, 18 Jul 2017 12:19:36 +
with message-id 
and subject line Bug#867797: fixed in khal 1:0.9.6-1
has caused the Debian Bug report #867797,
regarding khal 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.)


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

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

...
I: pybuild base:184: cd /build/1st/khal-0.8.4/.pybuild/pythonX.Y_3.6/build; 
python3.6 -m pytest tests
= test session starts ==
platform linux -- Python 3.6.2rc2, pytest-3.0.6, py-1.4.34, pluggy-0.4.0
rootdir: /build/1st/khal-0.8.4, inifile: 
collected 133 items / 3 errors

 ERRORS 
___ ERROR collecting .pybuild/pythonX.Y_3.6/build/tests/cli_test.py 
ImportError while importing test module 
'/build/1st/khal-0.8.4/.pybuild/pythonX.Y_3.6/build/tests/cli_test.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
:942: in _find_and_load_unlocked
???
E   AttributeError: module 'vdirsyncer.utils' has no attribute '__path__'

During handling of the above exception, another exception occurred:
tests/cli_test.py:9: in 
from khal.cli import main_khal, main_ikhal
khal/cli.py:36: in 
from . import aux, controllers, khalendar, __version__
khal/controllers.py:25: in 
from vdirsyncer.utils.vobject import Item
E   ModuleNotFoundError: No module named 'vdirsyncer.utils.vobject'; 
'vdirsyncer.utils' is not a package
 ERROR collecting .pybuild/pythonX.Y_3.6/build/tests/controller_test.py 
ImportError while importing test module 
'/build/1st/khal-0.8.4/.pybuild/pythonX.Y_3.6/build/tests/controller_test.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
tests/controller_test.py:4: in 
from vdirsyncer.storage.base import Item
E   ImportError: cannot import name 'Item'
 ERROR collecting .pybuild/pythonX.Y_3.6/build/tests/khalendar_test.py _
ImportError while importing test module 
'/build/1st/khal-0.8.4/.pybuild/pythonX.Y_3.6/build/tests/khalendar_test.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
tests/khalendar_test.py:8: in 
from vdirsyncer.storage.base import Item
E   ImportError: cannot import name 'Item'
!!! Interrupted: 3 errors during collection 
=== 3 error in 1.86 seconds 
E: pybuild pybuild:283: test: plugin distutils failed with: exit code=2: cd 
/build/1st/khal-0.8.4/.pybuild/pythonX.Y_3.6/build; python3.6 -m pytest tests
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.6 3.5 
returned exit code 13
debian/rules:26: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 25
--- End Message ---
--- Begin Message ---
Source: khal
Source-Version: 1:0.9.6-1

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 18 Jul 2017 11:49:34 +0200
Source: khal
Binary: khal khal-doc
Architecture: source
Version: 1:0.9.6-1
Distribution: unstable
Urgency: medium
Maintainer: Python Applications Packaging Team 

Changed-By: Filip Pytloun 
Description:
 khal   - Standards based CLI and terminal calendar program
 khal-doc   - Standards based CLI and terminal calendar program - documentation
Closes: 867797
Changes:
 khal (1:0.9.6-1) unstable; urgency=medium
 .
   * New upstream version (Closes: #867797)
   * d/patches: rebase for new release
Checksums-Sha1:
 53a2af1a485415883594479409375ff469fdfcd8 2404 khal_0.9.6-1.dsc
 871e7a2ad8d04d93fd8de914a534a94e43c1d730 169539 

Bug#834204: libsdl1.2: Nonfree file: src/video/fbcon/riva_mmio.h

[Jonas Smedegaard]

Package: src:libsdl1.2
Followup-For: Bug #834204

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Whoops - forgot to acutally attach the diff.

 - Jonas

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

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

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAllt+/EACgkQLHwxRsGg
ASGtXg//fTrFEtoLczPWhkKQ3A2YuiGqjkpgJhIvdFRcJsLa29ixrh9hraWGeN1j
FMfaYABS7aoeAd1Efpn6HqE+leT9SslCSgeromLBtmyX/blusRvLMYFipOJmhCOE
LzZHsDAUo7nE6wKH9xPbHOxwFL4ZzKBoqWFZ+SKumpVkTRijld0D0+4Z4LE5kiUZ
raerilDHCLqQrWZr9Vof/p4HyYgapYHYXZ+h9foRm48kzZuUIHQs75KtXO2PCdQn
pz28AwpAIaOMukZ9eq462Z4agDoarasHJMjDXHLxxxz2gti76iCMbKEKOJGcVj9t
TKVqMD0x2rqKJ0S3eiXfMv0Cf00yGj1y4PCA3aFfS2QdIw6OV9eBsPRDA1Gglzcu
stxB73dYYKibqLHgUgU01RsSXd8aIZcb42Y3mW1lKRImJm3XqTpMgu1Ye4jUgYVE
NHydJNt+1rZq8RyXhuUzFRFM+ow/t+ukPaRBGcJ1uHuKOHEjvMOX0xuT4W+BUA0W
FUDNUgVsPTndXDZ12VODlxCEMBpp3/vsbInMjOof1LUK0vTdQ6WrbA9eFKz33cwh
sc8++C5hJZ90emkQfMe2/0VtXpQ3uasv8WgVGmFUX1PsVOzV4Q+VHCJi3y2/02br
XE0ZqLDCV7Ei1a7PGjTchHnZsLENqivZXzhPm4G8F6sEDwMSWO0=
=tCu0
-END PGP SIGNATURE-


nmu.diff
Description: Binary data

Bug#834204: libsdl1.2: Nonfree file: src/video/fbcon/riva_mmio.h

[Jonas Smedegaard]

Package: src:libsdl1.2
Followup-For: Bug #834204

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

I have prepared an NMU and queued for release in 5 days.

Attached is the diff.

I made the changes in git locally, and can push that to Alioth if
granted write access to the repository (my account is js).
Alternatively I can put my git public somewhere for you to clone if you
prefer.

 - Jonas

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

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

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAllt+50ACgkQLHwxRsGg
ASHhCxAAj1GSl6n3oAmymMiX9CI1uFPZAefNs/+8chmlX0pbZKYAjvw9W2Lu35eS
eWLE9BBPOXjKsSqRnW6uM9xnaySu4zOlyYeEv/h/GZm8u4tunmr6OtCZpDQSI+Cy
DxHmt4fw6WhZ+/e3EmehKUni8QIX+h5GqZ/OCt7/MsqNMIuyvd1rhpbqGRXXtqVe
uEg/l1uHKzNdjNjUIpGCPJCumCnQRLPNDva/2A90Xam5twEV4NnnTuEn4P1m0kCm
NvkhhAVIN18xvkqQHyJRBgeuBEWaxT8OU+doSyQFvW/YVu8wFiJh39/MMcy4jnJ3
+/JzPWwa59KD7SiIoQO24P1KFXrRfekemiLqYUPHdK9WiGtd6oF02LQSVfp02Di8
TWvXS9KClIk/AverR1aTPuBXzK8cApWQ4pCcpFWrlrAGHlyfS1pe9tv0PP8nayhi
y+el3volYY2Z90m2GXWL3GDdjo76MrM1XbB2GdS37TDWXPwekC7I0W8LSuw2xPZu
N8l2MsxpRS6Zr4ybxxjTOAq/qiTp5N3f6SiiRDu5ZM1RkK6ASzLqS9VQ5tMcJOgx
S9IDenznNqsooVKpmQGUG6DYs/N4p+5Es2Ee7Ggk2UQ03iSGFhDyghXsDzb9mgIC
ozTIWQXfVNFiEWUdoqYimIVj5iGfG3QiaAS3LQaqmaPxHiq8tr8=
=Wl8e
-END PGP SIGNATURE-

Bug#865303: LibreOffice Writer works normally, Base still crashes on Sid with latest updates

[Nrbrtx]

With latest updates (libreoffice 1:5.3.4-4 and kernel
linux-image-4.11.0-2-686-pae 4.11.11-1) LibreOffice Writer starts normally
on 32bit Debian Sid.

But LibreOffice Base still crashes (in Database Wizard selected 'Create a
new database', 'Embedded database:' -> 'HSQLDB Embedded', click 'Next',
click 'Finish', save database file in /tmp/db.odb.).

Bug#868770: subvertpy FTBFS on big endian: FAIL: test_client_cert_pw/test_server_trust

[Adrian Bunk]

Source: subvertpy
Version: 0.10.0-1
Severity: serious

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

...
==
FAIL: test_client_cert_pw (subvertpy.tests.test_ra.AuthTests)
--
Traceback (most recent call last):
  File 
"/<>/.pybuild/pythonX.Y_2.7/build/subvertpy/tests/test_ra.py", 
line 462, in test_client_cert_pw
self.assertEqual(("supergeheim", False), next(creds))
AssertionError: Tuples differ: ('supergeheim', False) != ('supergeheim', 1)

First differing element 1:
False
1

- ('supergeheim', False)
? ^

+ ('supergeheim', 1)
? ^


==
FAIL: test_server_trust (subvertpy.tests.test_ra.AuthTests)
--
Traceback (most recent call last):
  File 
"/<>/.pybuild/pythonX.Y_2.7/build/subvertpy/tests/test_ra.py", 
line 470, in test_server_trust
self.assertEqual((42, 0), next(creds))
AssertionError: Tuples differ: (42, 0) != (42, 1)

First differing element 1:
0
1

- (42, 0)
?  ^

+ (42, 1)
?  ^


--
Ran 174 tests in 0.682s

FAILED (failures=2, skipped=21)
E: pybuild pybuild:283: test: plugin distutils failed with: exit code=1: 
python2.7 setup.py test 
dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
debian/rules:21: recipe for target 'build-arch' failed
make: *** [build-arch] Error 25

Bug#867082: marked as done (dune-typetree: Build-dependency pgf no longer available)

[Debian Bug Tracking System]

Your message dated Tue, 18 Jul 2017 11:34:19 +
with message-id 
and subject line Bug#867082: fixed in dune-typetree 2.5.0-2
has caused the Debian Bug report #867082,
regarding dune-typetree: Build-dependency pgf no longer available
to be marked as done.

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

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


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

The texlive-pictures package ships still ships pgf but no longer
provides it in the dependencies.
--- End Message ---
--- Begin Message ---
Source: dune-typetree
Source-Version: 2.5.0-2

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 18 Jul 2017 12:29:28 +0200
Source: dune-typetree
Binary: libdune-typetree-dev libdune-typetree-doc
Architecture: source
Version: 2.5.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Ansgar Burchardt 
Description:
 libdune-typetree-dev - toolbox for solving PDEs -- typed tree template library 
(developm
 libdune-typetree-doc - toolbox for solving PDEs -- typed tree template library 
(document
Closes: 867082
Changes:
 dune-typetree (2.5.0-2) unstable; urgency=medium
 .
   * Build-Depend on texlive-pictures instead of pgf. (Closes: #867082)
   * debian/copyright: Update URLs.
   * Bumped Standards-Version to 4.0.0 (no changes).
Checksums-Sha1:
 85e69a0b8c5611e2d29ff856962fd9246679ece3 2636 dune-typetree_2.5.0-2.dsc
 592aeb29b81db822267afe32b4d480d0d64531bb 3300 
dune-typetree_2.5.0-2.debian.tar.xz
Checksums-Sha256:
 8ac297061de71fdf9253d4ffae787b08a147c1a220143c31e539fdda57dd2dab 2636 
dune-typetree_2.5.0-2.dsc
 c65496e7d78c70dea5426bbb77c3590281620c0075ccc2d910da90faf2563e29 3300 
dune-typetree_2.5.0-2.debian.tar.xz
Files:
 6633f387b088474dbe9e7aa7d4f22e0b 2636 libs optional dune-typetree_2.5.0-2.dsc
 92419ff1e6611c4a6248a51b52d35199 3300 libs optional 
dune-typetree_2.5.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEE6XYjQ9o8g2p4zSVKamMCj1p06JMFAllt75sSHGFuc2dhckBk
ZWJpYW4ub3JnAAoJEGpjAo9adOiTW3cP+wewSsbtyMMc4KiyoIWNfTYn+xQL15h2
dnemNpzy+N6lHeLCSnu3nBTmj7X8B2Yh4/NmX6MbU7p4ceDXCMgdIvAK+v1nGbbc
vgizZH8xeEzc3VM79sHfWcveNYglECkJez1kIeyhUOKAdXe68sXdNNwvInjmdu+F
FWU4yJQ6tuPIs9xqNaPDAwCnREE31Ag+gS1w/B7ZlxhgS8e6fbWjEhRE8BZBUv0u
Z0F/zYW0ceS8XNBocdtjD5Kc9zzeaZLKbhv6Sd0wrQKhR7bGju/86/+cwmzp6T2Y
811g6R2724QB9+hsAB5NidfzVS/+F6v1SQ9B3f1xRrojM5jb//34orxvSN1pzknT
Oju+zjVCa3k1EcsEP4/zidSRHvbmx3p06MuDiN8nWX1gcxExZUodfcjVW7zYOUzg
sk2vMf6qqNQai5XJ8SRf6AEQuZ7HHEkV2+t4uUdrP+DmUpygY1l3yXXbflddVkuo
EpMAxn/wHhga2YBmXI1lR4Vt2sYzervb6VhKn5a7M9jsVvpBsG0LPLzdPg94BRLq
2nNH2BqBZW7K+yNvcM2DhkWJ2jpcXMrLIv4hm0Mbv9aFmDjIG4uY2aMo+9KwquTz
FlcCMuX0RhaDlBGj/v3nwFcG2e0GBDKee2pjP2/kw1URmNMSkJnPsUJnbUQ+3p6O
lsgDmI/D09dY
=8qb7
-END PGP SIGNATURE End Message ---

Bug#867075: marked as done (dune-geometry: Build-dependency pgf no longer available)

[Debian Bug Tracking System]

Your message dated Tue, 18 Jul 2017 11:34:05 +
with message-id 
and subject line Bug#867075: fixed in dune-geometry 2.5.1-1
has caused the Debian Bug report #867075,
regarding dune-geometry: Build-dependency pgf no longer available
to be marked as done.

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

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


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

The texlive-pictures package ships still ships pgf but no longer
provides it in the dependencies.
--- End Message ---
--- Begin Message ---
Source: dune-geometry
Source-Version: 2.5.1-1

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 18 Jul 2017 11:55:38 +0200
Source: dune-geometry
Binary: libdune-geometry-dev libdune-geometry-doc
Architecture: source
Version: 2.5.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Ansgar Burchardt 
Description:
 libdune-geometry-dev - toolbox for solving PDEs -- geometry classes 
(development files)
 libdune-geometry-doc - toolbox for solving PDEs -- geometry classes 
(documentation)
Closes: 867075
Changes:
 dune-geometry (2.5.1-1) unstable; urgency=medium
 .
   * New upstream release.
   * Build-Depend on texlive-pictures instead of pgf. (Closes: #867075)
   * debian/copyright: Update URLs.
   * Bumped Standards-Version to 4.0.0 (no changes).
Checksums-Sha1:
 6d63afd85364c4b1787cc387eeaca2aa797f4f4c 2643 dune-geometry_2.5.1-1.dsc
 33ec4c1acba24564f4183f0214f1ba0de40ac0ad 704515 dune-geometry_2.5.1.orig.tar.gz
 d34bd35b3288f74bdc589a51fabdade0c3e030fc 1061 
dune-geometry_2.5.1.orig.tar.gz.asc
 286fb50323d41c28b964dd8e8c1e88d7b3f36085 3672 
dune-geometry_2.5.1-1.debian.tar.xz
Checksums-Sha256:
 2d03387a953baf6ecaca2415dd178359ac38b1b15a3ca69eb018723fdc6f7b69 2643 
dune-geometry_2.5.1-1.dsc
 f3782b27a4622bd7b7bc52fa7561d5bcf4f0dc39d6c161c082047c7b92140076 704515 
dune-geometry_2.5.1.orig.tar.gz
 b458efa9d1edf43935296851680377b62d0f303e61d22e57417f97a08599b45d 1061 
dune-geometry_2.5.1.orig.tar.gz.asc
 bfb0b8b03b44849647c861ed2a5173350591949222a2bac8119476887dcc8f66 3672 
dune-geometry_2.5.1-1.debian.tar.xz
Files:
 072a65438982c5dd4c37bda257bd3c0e 2643 libs optional dune-geometry_2.5.1-1.dsc
 3d0ea46cad71c5087f304f462ccc5068 704515 libs optional 
dune-geometry_2.5.1.orig.tar.gz
 7a5f9bc64f365c688edab6df2699f9d8 1061 libs optional 
dune-geometry_2.5.1.orig.tar.gz.asc
 4e1c363945318ff826cb5d8756217d49 3672 libs optional 
dune-geometry_2.5.1-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEE6XYjQ9o8g2p4zSVKamMCj1p06JMFAllt8DESHGFuc2dhckBk
ZWJpYW4ub3JnAAoJEGpjAo9adOiTUmIP/2XOpl/vF2zlP2C685pgJxiFwC1Ak8fS
xg88A/6XCXsAyRu1MieW0CL4kzjDk8IMJjnY5ki3+4xTcTu88OavRP9IoC4G9AvP
DM8csy3PtulncA+gEiOtVRbxBIBD+Cde+R2MzjRiOJ1CGE+rL+6tRqv7I4/YDdb+
nmrUCs4TQwskm46SlvhTwwaJwc0jzNIVeDV16ZYL0wRjctbGGYpd0R19M735wDoX
Z1RXbvJbtw7H28k5iNNomBCxHMuhzSJA9VOxmilVtA4Ha4+zUd5kBJgjJvgQi4Lr
HTy7ntzjsbo2edk2q6VbYZ6BnITDP+W3Tw74Ssao1x/jw6uk8yaIO/D2MfK7kc/G
MSxDedKIbEJzdiWHq7pzROOW9f8tArkh29J784qWdn9Poug7UXw3YNE6VORK8j5/
upUN59t3e0xnkT8ycmdqH+wWwiqpz5HHPAjZfXlXe9BWcuqGjdNQxVcylZO2nzTU
NEQdQqbcgL+Gwz+6V6Z5d4TY/whKMweAet0BhlWZQnx1HK8n89o2fZjiirIoeoU3
gbvl3flW18DnQV81LB3Qp3Ims1Ddffdomvd/2SpVP0WtsyBNIrYTpift+Z8hFGun
ezOvOcmHzL9LKDswYtuzLHvVBW+5P1st8WUUh8yjGvSPRJMhQ008V7rRm1xY0T6m
QErvUifiOm2E
=jaSU
-END PGP SIGNATURE End Message ---

Bug#867078: marked as done (dune-istl: Build-dependency pgf no longer available)

[Debian Bug Tracking System]

Your message dated Tue, 18 Jul 2017 11:34:13 +
with message-id 
and subject line Bug#867078: fixed in dune-istl 2.5.1-1
has caused the Debian Bug report #867078,
regarding dune-istl: Build-dependency pgf no longer available
to be marked as done.

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

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


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

The texlive-pictures package ships still ships pgf but no longer
provides it in the dependencies.
--- End Message ---
--- Begin Message ---
Source: dune-istl
Source-Version: 2.5.1-1

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 18 Jul 2017 12:01:32 +0200
Source: dune-istl
Binary: libdune-istl-dev libdune-istl-doc
Architecture: source
Version: 2.5.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Ansgar Burchardt 
Description:
 libdune-istl-dev - toolbox for solving PDEs -- iterative solvers (development 
files)
 libdune-istl-doc - toolbox for solving PDEs -- iterative solvers 
(documentation)
Closes: 867078
Changes:
 dune-istl (2.5.1-1) unstable; urgency=medium
 .
   * New upstream release.
   * Build-Depend on texlive-pictures instead of pgf. (Closes: #867078)
   * debian/copyright: Update URLs.
   * Bumped Standards-Version to 4.0.0 (no changes).
Checksums-Sha1:
 cdc943417e19151dcb53322fe99c83f3e87f9ee3 2616 dune-istl_2.5.1-1.dsc
 4bb4d0100afd1b715e4dd669fcee66271b2e15f3 326892 dune-istl_2.5.1.orig.tar.gz
 fe8694a60b59bd8cdb9937d18b85c8d9595d748a 1061 dune-istl_2.5.1.orig.tar.gz.asc
 b71abc2d2e144e204495c1dbf0f488a0689c6f4a 3456 dune-istl_2.5.1-1.debian.tar.xz
Checksums-Sha256:
 4079bb7e42f061a945e5af3ed36a9f634e27d9ad26114ab0cac12db7c5fc22f4 2616 
dune-istl_2.5.1-1.dsc
 7e183b1361419620e3df7287d962bcbc1860fa8233588f5b25507ef7a20649dc 326892 
dune-istl_2.5.1.orig.tar.gz
 996d327c7cd471de32c590e020b42bf37284fc6de360d36920ba15bb9942 1061 
dune-istl_2.5.1.orig.tar.gz.asc
 b52de20f14c34806cc12bf8c91fff801600633241e669379b7e012cedc9a418f 3456 
dune-istl_2.5.1-1.debian.tar.xz
Files:
 3d0a0074b1d1ee9f9bb5973cacb98632 2616 libs optional dune-istl_2.5.1-1.dsc
 b16be825d8f0c2acdfdebde91894c6ef 326892 libs optional 
dune-istl_2.5.1.orig.tar.gz
 bb88dce96db3715ec86f54b78a00af77 1061 libs optional 
dune-istl_2.5.1.orig.tar.gz.asc
 b734b4332f497ac62ff4e3912a5d87c2 3456 libs optional 
dune-istl_2.5.1-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEE6XYjQ9o8g2p4zSVKamMCj1p06JMFAllt7/ESHGFuc2dhckBk
ZWJpYW4ub3JnAAoJEGpjAo9adOiTdK0P/iteBmjUJBV3bJD6JQNYLgPujIice1Vk
YgWGictLKl4ydkx4khsfVm9uz7OW8PIZNDkhUwb/gBxM6X46dlxci1CCSTD64YA8
6u15idrjbSRuzPIkPCPJLAfdhwaEMhcDFDsu2QFEWS0SgzkLJGADFVgrRwk1br8d
QJsqSAATqYIbONo1jaG71a/HD0SdPegqRJ7S3fJ2mwEE201s/fAb+33fmL86cUHg
37HMElOw3VW1ila/N4/MW59mdFI/vasYYApFRnARfIMbqB40upLH7YihEPq8T27N
OWPf6cwYJifKS7egbWU5CZjGe1q7KVFJyO35K4OShmTJGBe/j/aaAr/8llLhCRr0
vib+S/yjrl2hnJzjPHW/a2YlEx/4TEZSPujVnMs3Ft7epDcj5kw1+X5ZFu2gB2cU
lhN6OYArXFeBDS32BeAndRJd85vR+KgHiQGJL5TnwX3oxuW0iA2ZrEiuCnWUNb8l
ssolHqdLgizIdeaeTVqDpOB1M+HwlBr8Zu5buYRmYJZfoXw18RZg0Ws9xQsAPLi9
RB/AkRfOCZuqmfw3cua4Ou0cZLwSV9XAHdomvygOXxFNSB3mquOTKm1HOcKZ1hlK
R+Tgv+jIF37e3YhiXz/ZWBMxtmG8KNOfK1tOhfcV1jl8Fvg+o40TFRT37Evbiefn
89fnwJ0hrbef
=i0TF
-END PGP SIGNATURE End Message ---

Bug#863110: openvpn: VPN remains connected, but network is unreachable after 30-45 min and requires reconnect

[Patrick Matthäi]

Am 18.07.2017 um 13:05 schrieb Patrick Matthäi:
>> I've browsed through the git commits between 2.4.0 and 2.4.3, these
>> might be relevant here
>>
>> https://community.openvpn.net/openvpn/ticket/812
>> https://community.openvpn.net/openvpn/ticket/887
>>
>> Are you able to build a version with these patches applied yourself?
> I will build it for one of the notworking nodes and see what happens and
> give a feedback

Yeah very nice! With both patches applied it is working :D Like the
version 2.4.3-4 I get now a "NOTE: Pulled options changed on restart,
will need to close and reopen TUN/TAP device", all routes are removed
and readded and the connection works again. Two hosts, which are not
working after a restart of the server, do not have got this and refuse
to work.
Would love to see these patches in 9.1 :)

-- 
/*
Mit freundlichem Gruß / With kind regards,
 Patrick Matthäi
 GNU/Linux Debian Developer

  Blog: http://www.linux-dev.org/
E-Mail: pmatth...@debian.org
patr...@linux-dev.org
*/

Bug#863110: openvpn: VPN remains connected, but network is unreachable after 30-45 min and requires reconnect

[Bernhard Schmidt]

Am 18.07.2017 um 13:26 schrieb Patrick Matthäi:

Hi,

> Am 18.07.2017 um 13:05 schrieb Patrick Matthäi:
>>> I've browsed through the git commits between 2.4.0 and 2.4.3, these
>>> might be relevant here
>>>
>>> https://community.openvpn.net/openvpn/ticket/812
>>> https://community.openvpn.net/openvpn/ticket/887
>>>
>>> Are you able to build a version with these patches applied yourself?
>> I will build it for one of the notworking nodes and see what happens and
>> give a feedback
> 
> Yeah very nice! With both patches applied it is working :D Like the
> version 2.4.3-4 I get now a "NOTE: Pulled options changed on restart,
> will need to close and reopen TUN/TAP device", all routes are removed
> and readded and the connection works again. Two hosts, which are not
> working after a restart of the server, do not have got this and refuse
> to work.

Can you try to test which of those it is? I need a specific patch to get
into stable.

> Would love to see these patches in 9.1 :)

9.1 is already frozen, but I will submit it into 9.2 as soon as I know
which patch it is.

Bernhard

Bug#868765: [Pkg-freeradius-maintainers] Bug#868765: freeradius: New upstream version 3.0.15 fixing security critical bugs

[Michael Stapelberg]

Thanks for the heads-up. I’ll work on packaging the new upstream release
later today.

On Tue, Jul 18, 2017 at 4:06 AM, Karsten Heymann 
wrote:

> Package: freeradius
> Version: 3.0.12+dfsg-5
> Severity: grave
> Tags: upstream security
> Justification: user security hole
>
> Dear Maintainer,
>
> the freeradius team released version 3.0.15 fixing several important
> security issues found by a fuzzing analysis.
>
> See:
> http://freeradius.org/press/index.html#3.0.15
> http://freeradius.org/security/fuzzer-2017.html
>
> The following issues were found for v3 of freeradius up to 3.0.14:
> - CVE-2017-10978. No remote code execution is possible. A denial of
> service is possible.
> - CVE-2017-10984. Remote code execution is possible. A denial of
> service is possible.
> - CVE-2017-10985. No remote code execution is possible. A denial of
> service is possible.
>
> The following affect only the DHCP part of freeradius, which is seldomly
> used:
> - CVE-2017-10983. No remote code execution is possible. A denial of
> service is possible.
> - CVE-2017-10986. No remote code execution is possible. A denial of
> service is possible.
> - CVE-2017-10987. No remote code execution is possible. A denial of
> service is possible.
>
> Please update the package accordingly.
>
> -- 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/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 freeradius depends on:
> ii  freeradius-common  3.0.12+dfsg-5
> ii  freeradius-config  3.0.12+dfsg-5
> ii  libc6  2.24-11+deb9u1
> ii  libcap21:2.25-1
> ii  libfreeradius3 3.0.12+dfsg-5
> ii  libgdbm3   1.8.3-14
> ii  libpam0g   1.1.8-3.6
> ii  libpcre3   2:8.39-3
> ii  libperl5.245.24.1-3
> ii  libpython2.7   2.7.13-2
> ii  libreadline7   7.0-3
> ii  libsqlite3-0   3.16.2-5
> ii  libssl1.1  1.1.0f-3
> ii  libtalloc2 2.1.8-1
> ii  libwbclient0   2:4.5.8+dfsg-2+deb9u1+b1
> ii  lsb-base   9.20161125
>
> Versions of packages freeradius recommends:
> pn  freeradius-utils  
>
> Versions of packages freeradius suggests:
> pn  freeradius-krb5
> pn  freeradius-ldap
> pn  freeradius-mysql   
> pn  freeradius-postgresql  
> pn  snmp   
>
> -- no debconf information
>
> ___
> Pkg-freeradius-maintainers mailing list
> pkg-freeradius-maintain...@lists.alioth.debian.org
> https://lists.alioth.debian.org/mailman/listinfo/pkg-
> freeradius-maintainers
>



-- 
Best regards,
Michael

Bug#868761: [Pkg-freeradius-maintainers] Bug#868761: freeradius: New upstream version 2.2.10 fixing security critical bugs

[Michael Stapelberg]

Help with this would be appreciated. I’m not sure about the appropriate
processes, so if you could clarify that with the security/release team,
that’d be helpful.

On Tue, Jul 18, 2017 at 3:51 AM, Karsten Heymann 
wrote:

> Subject: freeradius: New upstream version 2.2.10 fixing security critical
> bugs
> Package: freeradius
> Version: 2.2.5+dfsg-0.2
> Justification: user security hole
> Severity: grave
> Tags: security upstream
>
> The freeradius team released version 2.2.10 fixing several important
> security issues found by a fuzzing analysis.
>
> See:
> http://freeradius.org/press/index.html#2.2.10
> http://freeradius.org/security/fuzzer-2017.html
>
> The following issues were found for v2 of freeradius up to 2.2.9:
> - CVE-2017-10978. No remote code execution is possible. A denial of
> service is possible.
> - CVE-2017-10979. Remote code execution is possible. A denial of
> service is possible.
>
> The following affect only the DHCP part of freeradius, which is seldomly
> used:
> - CVE-2017-10980. No remote code execution is possible. A denial of
> service is possible.
> - CVE-2017-10981. No remote code execution is possible. A denial of
> service is possible.
> - CVE-2017-10982. No remote code execution is possible. A denial of
> service is possible.
> - CVE-2017-10983. No remote code execution is possible. A denial of
> service is possible.
>
> I'm not sure what's the best way to proceed. As I assume updating the
> package in oldstable to 2.2.10 is not a realistic option, my guess
> would be that at least CVE-2017-10978 and CVE-2017-10979 should be
> fixed in the code via backporting the relevant fixes. This is even
> more critical as there is no backport of freeradius 3 in jessie, and
> it is not possible to create or update backports for oldstable.
>
> -- System Information:
> Debian Release: 8.8
>   APT prefers oldstable-updates
>   APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
> 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 freeradius depends on:
> ii  adduser3.113+nmu3
> ii  ca-certificates20141019+deb8u3
> ii  freeradius-common  2.2.5+dfsg-0.2
> ii  libc6  2.19-18+deb8u10
> ii  libfreeradius2 2.2.5+dfsg-0.2
> ii  libgdbm3   1.8.3-13.1
> ii  libltdl7   2.4.2-1.11+b1
> ii  libpam0g   1.1.8-3.1+deb8u2
> ii  libperl5.205.20.2-3+deb8u7
> ii  libpython2.7   2.7.9-2+deb8u1
> ii  libssl1.0.01.0.1t-1+deb8u6
> ii  lsb-base   4.1+Debian13+nmu1
> ii  ssl-cert   1.0.35
>
> Versions of packages freeradius recommends:
> ii  freeradius-utils  2.2.5+dfsg-0.2
>
> Versions of packages freeradius suggests:
> pn  freeradius-krb5
> ii  freeradius-ldap2.2.5+dfsg-0.2
> ii  freeradius-mysql   2.2.5+dfsg-0.2
> pn  freeradius-postgresql  
>
> -- Configuration Files:
> /etc/freeradius/clients.conf changed [not included]
> /etc/freeradius/eap.conf changed [not included]
> /etc/freeradius/ldap.attrmap changed [not included]
> /etc/freeradius/modules/ldap changed [not included]
> /etc/freeradius/modules/pap changed [not included]
> /etc/freeradius/sites-available/control-socket changed [not included]
> /etc/freeradius/sites-available/default changed [not included]
> /etc/freeradius/sites-available/inner-tunnel changed [not included]
> /etc/freeradius/sql.conf changed [not included]
> /etc/freeradius/users changed [not included]
>
> -- no debconf information
>
> ___
> Pkg-freeradius-maintainers mailing list
> pkg-freeradius-maintain...@lists.alioth.debian.org
> https://lists.alioth.debian.org/mailman/listinfo/pkg-
> freeradius-maintainers
>



-- 
Best regards,
Michael

Bug#868765: freeradius: New upstream version 3.0.15 fixing security critical bugs

[Karsten Heymann]

Package: freeradius
Version: 3.0.12+dfsg-5
Severity: grave
Tags: upstream security
Justification: user security hole

Dear Maintainer,

the freeradius team released version 3.0.15 fixing several important
security issues found by a fuzzing analysis.

See:
http://freeradius.org/press/index.html#3.0.15
http://freeradius.org/security/fuzzer-2017.html

The following issues were found for v3 of freeradius up to 3.0.14:
- CVE-2017-10978. No remote code execution is possible. A denial of
service is possible.
- CVE-2017-10984. Remote code execution is possible. A denial of 
service is possible.
- CVE-2017-10985. No remote code execution is possible. A denial of
service is possible.

The following affect only the DHCP part of freeradius, which is seldomly used:
- CVE-2017-10983. No remote code execution is possible. A denial of
service is possible.
- CVE-2017-10986. No remote code execution is possible. A denial of
service is possible.
- CVE-2017-10987. No remote code execution is possible. A denial of
service is possible.

Please update the package accordingly.

-- 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/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 freeradius depends on:
ii  freeradius-common  3.0.12+dfsg-5
ii  freeradius-config  3.0.12+dfsg-5
ii  libc6  2.24-11+deb9u1
ii  libcap21:2.25-1
ii  libfreeradius3 3.0.12+dfsg-5
ii  libgdbm3   1.8.3-14
ii  libpam0g   1.1.8-3.6
ii  libpcre3   2:8.39-3
ii  libperl5.245.24.1-3
ii  libpython2.7   2.7.13-2
ii  libreadline7   7.0-3
ii  libsqlite3-0   3.16.2-5
ii  libssl1.1  1.1.0f-3
ii  libtalloc2 2.1.8-1
ii  libwbclient0   2:4.5.8+dfsg-2+deb9u1+b1
ii  lsb-base   9.20161125

Versions of packages freeradius recommends:
pn  freeradius-utils  

Versions of packages freeradius suggests:
pn  freeradius-krb5
pn  freeradius-ldap
pn  freeradius-mysql   
pn  freeradius-postgresql  
pn  snmp   

-- no debconf information

Bug#863110: openvpn: VPN remains connected, but network is unreachable after 30-45 min and requires reconnect

[Patrick Matthäi]

Am 18.07.2017 um 12:58 schrieb Bernhard Schmidt:
> The notworking version does nothing like this. This smells like a bug.
>
> What I don't understand is that you claim the VPN endpoint is not
> reachable on the dead nodes (the outer IP I presume). Both nodes still
> have a hostroute towards the VPN gateway in their routing table
>
I mean not the external VPN endpoint address, but the VPN internal
server address (10.200.13.1 here).
>
> I've browsed through the git commits between 2.4.0 and 2.4.3, these
> might be relevant here
>
> https://community.openvpn.net/openvpn/ticket/812
> https://community.openvpn.net/openvpn/ticket/887
>
> Are you able to build a version with these patches applied yourself?

I will build it for one of the notworking nodes and see what happens and
give a feedback

-- 
/*
Mit freundlichem Gruß / With kind regards,
 Patrick Matthäi
 GNU/Linux Debian Developer

  Blog: http://www.linux-dev.org/
E-Mail: pmatth...@debian.org
patr...@linux-dev.org
*/