Processed: patch

2016-11-06 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 patch
Bug #828308 [src:gdcm] missing include for 'X509_STORE_CTX cert_ctx'
Added tag(s) patch.

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



Bug#828308: patch

2016-11-06 Thread Mathieu Malaterre
Control: tags -1 patch

Attached.


828308.patch
Description: Binary data


Bug#843481: asn1c: FTBFS: cannot stat 'asn1c-usage.pdf': No such file or directory

2016-11-06 Thread Eugene Seliverstov
Sure, I’ll take a look today.
It was an attempt to fix a failing MIPS build. Building and installing docs 
only for build-indep would help.

> On 07.11.2016, at 1:52, Aaron M. Ucko  wrote:
> 
> Source: asn1c
> Version: 0.9.27+dfsg-2
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
> 
> Builds of asn1c covering only its main (architecture-dependent) binary
> package have been failing (except, for some reason, on mips):
> 
>  Making install in docsrc
>  make[4]: Entering directory '/«BUILDDIR»/asn1c-0.9.27+dfsg/doc/docsrc'
>  make[5]: Entering directory '/«BUILDDIR»/asn1c-0.9.27+dfsg/doc/docsrc'
>  make[5]: Nothing to be done for 'install-exec-am'.
>  mkdir -p /«BUILDDIR»/asn1c-0.9.27+dfsg/debian/tmp/usr/share/doc/asn1c-doc
>  cp -a asn1c-usage.pdf 
> /«BUILDDIR»/asn1c-0.9.27+dfsg/debian/tmp/usr/share/doc/asn1c-doc
>  cp: cannot stat 'asn1c-usage.pdf': No such file or directory
>  Makefile:458: recipe for target 'install-data-local' failed
>  make[5]: *** [install-data-local] Error 1
> 
> Could you please take a look?
> 
> Thanks!
> 
> -- 
> Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
> http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

---
Best regards,
Eugene Seliverstov



Processed: Re: Bug#843434: terminology: Escape Sequence Command Execution vulnerability

2016-11-06 Thread Debian Bug Tracking System
Processing control commands:

> retitle -1 terminology: CVE-2015-8971: Escape Sequence Command Execution 
> vulnerability
Bug #843434 [src:terminology] terminology: Escape Sequence Command Execution 
vulnerability
Changed Bug title to 'terminology: CVE-2015-8971: Escape Sequence Command 
Execution vulnerability' from 'terminology: Escape Sequence Command Execution 
vulnerability'.

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



Bug#843434: terminology: Escape Sequence Command Execution vulnerability

2016-11-06 Thread Salvatore Bonaccorso
Control: retitle -1 terminology: CVE-2015-8971: Escape Sequence Command 
Execution vulnerability 

On Sun, Nov 06, 2016 at 06:12:31PM +0100, Salvatore Bonaccorso wrote:
> The CVE has not yet been assigned, will update the subject here once
> it's done.

The CVE has been assigned, CVE-2015-8971.

http://www.openwall.com/lists/oss-security/2016/11/07/1

Regards,
Salvatore



Bug#828240: asterisk: FTBFS with openssl 1.1.0

2016-11-06 Thread Stepan Golosunov
06.11.2016 в 23:39:41 +0100 Bernhard Schmidt написал(а):
> On Sun, Nov 06, 2016 at 04:39:03PM +0400, Stepan Golosunov wrote:
> > 06.11.2016 в 16:18:32 +0400 Stepan Golosunov написал:

> > > #if defined(HAVE_OPENSSL) && OPENSSL_VERSION_NUMBER >= 0x1010L
> > > /* No explicit initialization is needed with OpenSSL 1.1.0.
> > >All the functions called or overridden in this file were removed. */
> > > #undef HAVE_OPENSSL
> > > #endif

> Thanks a lot, your suggestion together with 
> https://anonscm.debian.org/cgit/pkg-voip/asterisk.git/commit/?id=ec0143a92f4ced996be419bf49115be8f236e3ea
> 
> leads to something that builds and runs. Yay!
> 
> @Tzafrir: What do you think of this? Your patch is touching
> main/libasteriskssl.c as well, but Stepan suggested to drop even more. 

Note that code in ast_ssl_init would still call functions from
libssl1.0.2, even if compiled with OpenSSL 1.1.0 (but with the wrong
value for CRYPTO_num_locks(), 1 instead of 41). Or return -1 if
libssl.so.1.0.2 is not loaded.

(Though not running that code can be problematic if libssl1.0.2 is
not only loaded but actually used via some third library.)

And I suspect that OPENSSL_API_COMPAT is wrong value for conditional
compilation (it's not defined in OpenSSL 1.0.2 for example).



Bug#825934: marked as done (elkcode: FTBFS: undefined reference to xc_f90_version_)

2016-11-06 Thread Debian Bug Tracking System
Your message dated Mon, 7 Nov 2016 01:02:06 -0500
with message-id 

Bug#832849: docker-swarm: FTBFS: dh_auto_build: src/github.com/docker/swarm/api/handlers.go:17:2: cannot find package "github.com/docker/docker/pkg/parsers/filters"

2016-11-06 Thread Jeremy Bicha
Control: found -1 1.2.5+dfsg-2
Control: reopen -1

Actually, it fails to build on Launchpad's builders too for Ubuntu
17.04 "Zesty" alpha. Do the Debian buildds have internet access?

Thanks,
Jeremy Bicha



Processed: Re: docker-swarm: FTBFS: dh_auto_build: src/github.com/docker/swarm/api/handlers.go:17:2: cannot find package "github.com/docker/docker/pkg/parsers/filters"

2016-11-06 Thread Debian Bug Tracking System
Processing control commands:

> found -1 1.2.5+dfsg-2
Bug #832849 {Done: Jeremy Bicha } [src:docker-swarm] 
docker-swarm: FTBFS: dh_auto_build: 
src/github.com/docker/swarm/api/handlers.go:17:2: cannot find package 
"github.com/docker/docker/pkg/parsers/filters"
Marked as found in versions docker-swarm/1.2.5+dfsg-2 and reopened.
> reopen -1
Bug #832849 [src:docker-swarm] docker-swarm: FTBFS: dh_auto_build: 
src/github.com/docker/swarm/api/handlers.go:17:2: cannot find package 
"github.com/docker/docker/pkg/parsers/filters"
Bug 832849 is not marked as done; doing nothing.

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



Bug#832849: marked as done (docker-swarm: FTBFS: dh_auto_build: src/github.com/docker/swarm/api/handlers.go:17:2: cannot find package "github.com/docker/docker/pkg/parsers/filters")

2016-11-06 Thread Debian Bug Tracking System
Your message dated Mon, 7 Nov 2016 00:39:57 -0500
with message-id 

Bug#843496: libgv-python: Wrong symlink name

2016-11-06 Thread Celelibi
Package: libgv-python
Version: 2.38.0-16
Severity: grave
Justification: renders package unusable

Dear maintainer,

The .so library on i386 is installed at
/usr/lib/python2.7/dist-packages/libgv_python27.i386-linux-gnu.so and
symlinked from /usr/lib/python2.7/dist-packages/_gv.i686-linux-gnu.so.

However, python look for "i386" in the name, not "i686". Here are the
path searched by python.

$ strace -e trace=file python -c 'import gv' 2>&1 | grep 
'/usr/lib/python2.7/dist-packages/_gv.*\.so' | sort -u
open("/usr/lib/python2.7/dist-packages/_gv.i386-linux-gnu.so", 
O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory)
open("/usr/lib/python2.7/dist-packages/_gvmodule.so", O_RDONLY|O_LARGEFILE) = 
-1 ENOENT (No such file or directory)
open("/usr/lib/python2.7/dist-packages/_gv.so", O_RDONLY|O_LARGEFILE) = -1 
ENOENT (No such file or directory)

Best regards,
Celelibi


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

Kernel: Linux 3.10.11 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)

Versions of packages libgv-python depends on:
ii  libc6 2.24-5
ii  libcdt5   2.38.0-16
ii  libcgraph62.38.0-16
ii  libgcc1   1:6.2.0-10
ii  libgvc6   2.38.0-16
ii  libpython2.7  2.7.12-3+b1
ii  libstdc++66.2.0-10
ii  python2.7.11-2
pn  python:any

libgv-python recommends no packages.

libgv-python suggests no packages.

-- no debconf information



Bug#843491: witty: Depends on libmysqlclient18 which is no longer available

2016-11-06 Thread Jeremy Bicha
Source: witty
Version: 3.3.6+dfsg-1.1
Severity: serious

libwtdbomysql40 has a hard-coded dependency on libmysqlclient18 but
that library is no longer built from source in Debian stretch.

I believe the appropriate dependency ( libmariadbclient18 now that the
default MySQL is MariaDB ) is already automatically added during the
build.

Thanks,
Jeremy Bicha



Bug#834624: marked as done (vm-bonus-el: vm-bogofilter.el doesn't byte-compile)

2016-11-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Nov 2016 17:19:59 -0500
with message-id <3246.1478470...@mixed.noname.org>
and subject line Re: Bug#834624: vm-bonus-el: vm-bogofilter.el doesn't 
byte-compile
has caused the Debian Bug report #834624,
regarding vm-bonus-el: vm-bogofilter.el doesn't byte-compile
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.)


-- 
834624: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834624
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: vm-bonus-el
Version: 35.2+nmu1
Severity: serious

Attempting to install, byte-compilation fails.  The compilation log in
/tmp/ contains

emacs24 -q -no-site-file --no-site-file -batch -l path.el -f batch-byte-compile 
vm-bogofilter.el
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion failure: (void-variable vm-supported-sort-keys)
Eager macro-expansion 

Processed: statserial: diff for NMU version 1.1-22.1

2016-11-06 Thread Debian Bug Tracking System
Processing control commands:

> tags 817679 + patch
Bug #817679 [src:statserial] statserial: Removal of debhelper compat 4
Added tag(s) patch.
> tags 817679 + pending
Bug #817679 [src:statserial] statserial: Removal of debhelper compat 4
Added tag(s) pending.

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



Bug#817679: statserial: diff for NMU version 1.1-22.1

2016-11-06 Thread Joao Eriberto Mota Filho
Control: tags 817679 + patch
Control: tags 817679 + pending

Dear maintainer,

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

Regards,

Eriberto

diff -u statserial-1.1/debian/changelog statserial-1.1/debian/changelog
--- statserial-1.1/debian/changelog
+++ statserial-1.1/debian/changelog
@@ -1,3 +1,16 @@
+statserial (1.1-22.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Bumped DH level to 10. (Closes: #817679)
+  * debian/compat: created.
+  * debian/control:
+  - Added a ${misc:Depends} variable to Depends field.
+  - Added a Homepage field.
+  - Bumped Standards-Version to 3.9.8.
+  * debian/watch: created.
+
+ -- Joao Eriberto Mota Filho   Mon, 07 Nov 2016 00:01:02 
-0200
+
 statserial (1.1-22) unstable; urgency=low
 
   * Policy compliant up to 3.6.2.0 
diff -u statserial-1.1/debian/control statserial-1.1/debian/control
--- statserial-1.1/debian/control
+++ statserial-1.1/debian/control
@@ -1,13 +1,14 @@
 Source: statserial
-Build-Depends: debhelper, libncurses5-dev
+Build-Depends: debhelper (>= 10), libncurses5-dev
 Section: utils
 Priority: extra
 Maintainer: Vince Mulhollon 
-Standards-Version: 3.6.2.0
+Standards-Version: 3.9.8
+Homepage: http://www.oocities.org/jefftran...@rogers.com/
 
 Package: statserial
 Architecture: any
-Depends: ${shlibs:Depends}
+Depends: ${misc:Depends}, ${shlibs:Depends}
 Description: Displays serial port modem status lines
  Statserial displays a table of the signals on a standard 9-pin or
  25-pin serial port, and indicates the status of the handshaking lines.
diff -u statserial-1.1/debian/rules statserial-1.1/debian/rules
--- statserial-1.1/debian/rules
+++ statserial-1.1/debian/rules
@@ -4,7 +4,7 @@
 # Uncomment this to turn on verbose mode.
 #export DH_VERBOSE=1
 
-export DH_COMPAT=4
+#export DH_COMPAT=4
 
 build: build-stamp
 build-stamp:
only in patch2:
unchanged:
--- statserial-1.1.orig/debian/compat
+++ statserial-1.1/debian/compat
@@ -0,0 +1 @@
+10
only in patch2:
unchanged:
--- statserial-1.1.orig/debian/watch
+++ statserial-1.1/debian/watch
@@ -0,0 +1,2 @@
+version=4
+http://www.oocities.org/jefftran...@rogers.com/ 
.*/pub/Linux/system/serial/statserial-(\d\S+)\.tar\.(?:bz2|gz|xz)



Processed: Re: Bug#843482: aubio: FTBFS on PowerPC variants: test_zeros fails

2016-11-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 843482 patch pending
Bug #843482 [src:aubio] aubio: FTBFS on PowerPC variants: test_zeros fails
Added tag(s) patch and pending.
> thanks
Stopping processing here.

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



Bug#843482: aubio: FTBFS on PowerPC variants: test_zeros fails

2016-11-06 Thread Paul Brossier
Hi Aaron,

Yes. Attached is a patch that just skip the two tests.

The issue here is that when running fftw_execute on an input vector full
of 0, the output vector contains some -0 on powerpc, instead of all 0
other architectures.

When computing the phase using atan2(im, re), the result is no more all
0, but can also be -0, pi, or -pi, as described in atan2f(3).

If I remember correctly, this is due to a powerpc specific optimization
in fftw3, (not a bug, a feature).

Attached is a patch that fixes the build by checking the phases are one
of those 4 values, and marking the unit test as skipped.

I will upload 0.4.3-2 tomorrow evening, with a few other minor changes.

Thanks,
Paul

On 11/06/2016 11:57 PM, Aaron M. Ucko wrote:
> Source: aubio
> Version: 0.4.1-2.2
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
> 
> Builds of aubio for ppc64el and the non-release architectures powerpc
> and ppc64 all failed; see below for an excerpt from the ppc64el log at
> https://buildd.debian.org/status/fetch.php?pkg=aubio=ppc64el=0.4.3-1=1478460825
> Could you please take a look?
> 
> Thanks!
> 
>   ==
>   FAIL: test_zeros (test_phasevoc.aubio_pvoc_test_case)
>   check the resynthesis of zeros gives zeros
>   --
>   Traceback (most recent call last):
> File "/«PKGBUILDDIR»/python/tests/test_phasevoc.py", line 49, in 
> test_zeros
>   assert_equal ( s.phas, 0.)
> File "/usr/lib/python2.7/dist-packages/numpy/testing/utils.py", line 322, 
> in assert_equal
>   return assert_array_equal(actual, desired, err_msg, verbose)
> File "/usr/lib/python2.7/dist-packages/numpy/testing/utils.py", line 813, 
> in assert_array_equal
>   verbose=verbose, header='Arrays are not equal')
> File "/usr/lib/python2.7/dist-packages/numpy/testing/utils.py", line 739, 
> in assert_array_compare
>   raise AssertionError(msg)
>   AssertionError: 
>   Arrays are not equal
>   
>   (mismatch 34.6978557505%)
>x: array([ 0.  ,  0.  ,  0.  ,  0.  ,  0.  ,  0.  ,
>   0.  ,  0.  ,  0.  ,  0.  ,  0.  ,  0.  ,
>   0.  ,  0.  ,  0.  ,  0.  , -0.  ,  0.  ,...
>y: array(0.0)
>   
>   ==
>   FAIL: test_zeros (test_fft.aubio_fft_test_case)
>   check the transform of zeros is all zeros
>   --
>   Traceback (most recent call last):
> File "/«PKGBUILDDIR»/python/tests/test_fft.py", line 36, in test_zeros
>   assert_equal ( fftgrain.phas, 0 )
> File "/usr/lib/python2.7/dist-packages/numpy/testing/utils.py", line 322, 
> in assert_equal
>   return assert_array_equal(actual, desired, err_msg, verbose)
> File "/usr/lib/python2.7/dist-packages/numpy/testing/utils.py", line 813, 
> in assert_array_equal
>   verbose=verbose, header='Arrays are not equal')
> File "/usr/lib/python2.7/dist-packages/numpy/testing/utils.py", line 739, 
> in assert_array_compare
>   raise AssertionError(msg)
>   AssertionError: 
>   Arrays are not equal
>   
>   (mismatch 31.5175097276%)
>x: array([ 0.  ,  0.  ,  0.  ,  0.  ,  0.  ,  0.  ,
>   0.  ,  0.  ,  0.  ,  0.  ,  0.  ,  0.  ,
>   0.  ,  0.  ,  0.  ,  0.  , -0.  ,  0.  ,...
>y: array(0)
>   
>   --
>   Ran 745 tests in 12.995s
>   
>   FAILED (failures=2, skipped=4)
> 
diff --git a/python/tests/test_fft.py b/python/tests/test_fft.py
index fa349e5..a8f82b9 100755
--- a/python/tests/test_fft.py
+++ b/python/tests/test_fft.py
@@ -33,7 +33,14 @@ class aubio_fft_test_case(TestCase):
 f = fft (win_s)
 fftgrain = f (timegrain)
 assert_equal ( fftgrain.norm, 0 )
-assert_equal ( fftgrain.phas, 0 )
+try:
+assert_equal ( fftgrain.phas, 0 )
+except AssertionError:
+assert_equal (fftgrain.phas[fftgrain.phas > 0], +pi)
+assert_equal (fftgrain.phas[fftgrain.phas < 0], -pi)
+assert_equal (np.abs(fftgrain.phas[np.abs(fftgrain.phas) != pi]), 0)
+self.skipTest('fft(fvec(%d)).phas != +0, ' % win_s \
++ 'This is expected when using fftw3 on powerpc.')
 
 def test_impulse(self):
 """ check the transform of one impulse at a random place """
diff --git a/python/tests/test_phasevoc.py b/python/tests/test_phasevoc.py
index 23cbad5..957d3b1 100755
--- a/python/tests/test_phasevoc.py
+++ b/python/tests/test_phasevoc.py
@@ -46,7 +46,14 @@ class aubio_pvoc_test_case(TestCase):
 r = f.rdo(s)
 assert_equal ( t, 0.)
 assert_equal ( s.norm, 0.)
-

Processed: Re: Bug#843482: aubio: FTBFS on PowerPC variants: test_zeros fails

2016-11-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> found 843482 0.4.3-1
Bug #843482 [src:aubio] aubio: FTBFS on PowerPC variants: test_zeros fails
Marked as found in versions aubio/0.4.3-1.
> thanks
Stopping processing here.

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



Bug#833198: marked as done (libtcd: Uses obsolete Source-Version substvar)

2016-11-06 Thread Debian Bug Tracking System
Your message dated Mon, 07 Nov 2016 01:04:07 +
with message-id 
and subject line Bug#833198: fixed in libtcd 2.2.2-2
has caused the Debian Bug report #833198,
regarding libtcd: Uses obsolete Source-Version substvar
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.)


-- 
833198: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833198
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libtcd
Source-Version: 2.2.2-1
Severity: important
User: debian-d...@lists.debian.org
Usertags: dpkg-obsolete-source-version-substvar

Hi!

This source package uses the ${Source-Version} substvar variable
deprecated since dpkg 1.13.19 in 2006-05-04. That upload also introduced
the substvars binary:Version and source:Version which can be used
instead.

Using this deprecated substvar will become an error in the near
future. Please update the package.

See also .

Thanks,
Guillem
--- End Message ---
--- Begin Message ---
Source: libtcd
Source-Version: 2.2.2-2

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

Debian distribution maintenance software
pp.
Peter S Galbraith  (supplier of updated libtcd 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, 06 Nov 2016 19:36:57 -0500
Source: libtcd
Binary: libtcd-dev libtcd0
Architecture: source amd64
Version: 2.2.2-2
Distribution: unstable
Urgency: medium
Maintainer: Peter S Galbraith 
Changed-By: Peter S Galbraith 
Description:
 libtcd-dev - Tide Constituent Database (TCD) library (header file)
 libtcd0- Tide Constituent Database (TCD) library
Closes: 734221 833198
Changes:
 libtcd (2.2.2-2) unstable; urgency=medium
 .
   * debian/compat from 5 to 9
   * Standards-Version: 3.9.8
   * Bug fix: "Uses obsolete Source-Version substvar", thanks to Guillem
 Jover (Closes: #833198).
   * Bug fix: "use dh-autoreconf instead of autotools-dev to fix FTBFS on
 ppc64el", thanks to Logan Rosen (Closes: #734221).
Checksums-Sha1:
 2f14d24326d39511d787afe1fb05bcfd19297671 1670 libtcd_2.2.2-2.dsc
 2f9a64e962aab9a095df49468150ef4f10c270e2 7733 libtcd_2.2.2-2.diff.gz
 88ff6ca7d0858edc6c3f311db8d2aca9a5c300c2 51966 libtcd-dev_2.2.2-2_amd64.deb
 b12431e099f71d708fc633b7ce5f89bb60e0d258 34732 libtcd0_2.2.2-2_amd64.deb
Checksums-Sha256:
 0ff43b127c1d9e328cabda993ef06cbf08ffe2a1ef69102611a1a814e43cb0f0 1670 
libtcd_2.2.2-2.dsc
 29c0ae307d24d6f68206a75e4b4bbac43a1b86d11a0009859c66ea570b18f41a 7733 
libtcd_2.2.2-2.diff.gz
 0d025d75d13e88f34b2d4ccf6355856cf8e4717c94cdf3566fed37b81047eeb3 51966 
libtcd-dev_2.2.2-2_amd64.deb
 79baebe404bc7eaab0ef621ab6e6263c6976e61bd046fdf0f03a4073c958f7dc 34732 
libtcd0_2.2.2-2_amd64.deb
Files:
 1888d7197601704073ff9ce2154205d2 1670 libs extra libtcd_2.2.2-2.dsc
 5a153e4be4a588695fbc3667256ecd66 7733 libs extra libtcd_2.2.2-2.diff.gz
 f6fa62e25c5cfe2bee63877e7e174361 51966 libdevel extra 
libtcd-dev_2.2.2-2_amd64.deb
 bb624a28238111a02be5ee16090aeac9 34732 libs extra libtcd0_2.2.2-2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJYH81AAAoJEBfcPMRw1Kl5FQQP/3E5N0Bd2LrHJULj+1I1oJ69
Ed5uyJb9Y951L5/kS47Z1M7Ic08lYD7+iP+bT5ZT82SFz6gQIg2D8bj5TPSlFxbA
2cT01JCsFT8g8FjaIvWdZPGfXWXCoG4YtL0bNiBcjyzM93ukmF1gQRmx9W+k2iCW
bsT0fvsArIC4TqJrsEXKjnCAZWPHvEeEqOj+IUcBgOBZB3hbM2kzVvD8dyPlbT55
PC1g1ruLEMBzV9TEAqrE2sQ2x8rDXKJHk+RLPcfyNzU0X1Ro6bb9pwov3X+PMslj
tckYl2lgFpadZ8s9iOSs6rAoiyfo8+1jyBzQB9NaNu0OSSiGqBCQf1Q1rJXbsVK8
6K8buk4OvuGTIuboH4+4x7uc84NvxGfpEaBFvs5GWclUEbu4AbN2EIE27ZLfN7/o
f0M4+XFGXZsVY9eZrx/bIrjOh+lQlrggY9kQ6nyd8INcU1aP2H2TAME5q4L7q5KN
jr5WYPZsA5A9ghXSvJv6z5J/rXAF+Avq53oS1b5Duz7KN0jNobh0KeVbU1S+xoQw
zIQfWCh7hEpDnGOrQ2WvKnQLx60hRb/TTOBH/dBs0MZX1SbF+vmKothUHesyC3/C
+HP9XFgzL6JnX1LS9Nj5qL2COGbb6cittlzYYouMKrZrZOBjSM0FirYradRR98wH
QiqNwc6XAI8xeIOC1F94
=HA9h
-END PGP SIGNATURE End Message ---


Bug#812652: marked as done (horae: FTBFS - Can't locate Module/Build.pm)

2016-11-06 Thread Debian Bug Tracking System
Your message dated Mon, 07 Nov 2016 00:34:09 +
with message-id 
and subject line Bug#812652: fixed in horae 071~svn537-2.1
has caused the Debian Bug report #812652,
regarding horae: FTBFS - Can't locate Module/Build.pm
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.)


-- 
812652: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812652
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: horae
Version: 071~svn537-2
Severity: serious
Usertags: goto-cc

During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.

[...]
 debian/rules build
dh_testdir
/usr/bin/perl Build.PL 
destdir=/srv/jenkins-slave/workspace/sid-goto-cc-horae/horae-071~svn537/debian/horae
Can't locate Module/Build.pm in @INC (you may need to install the Module::Build 
module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.22.1 
/usr/local/share/perl/5.22.1 /usr/lib/x86_64-linux-gnu/perl5/5.22 
/usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.22 /usr/share/perl/5.22 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .) at Build.PL 
line 3.
BEGIN failed--compilation aborted at Build.PL line 3.
debian/rules:16: recipe for target 'configure-stamp' failed
make: *** [configure-stamp] Error 2


The full build log is attached; please do let me know if the problem is
unreproducible, in which case I shall try to investigate further.

Best,
Michael


horae-build-log.txt.gz
Description: application/gunzip


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: horae
Source-Version: 071~svn537-2.1

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

Debian distribution maintenance software
pp.
Stuart Prescott  (supplier of updated horae package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 07 Nov 2016 11:04:20 +1100
Source: horae
Binary: horae
Architecture: source all
Version: 071~svn537-2.1
Distribution: unstable
Urgency: medium
Maintainer: Carlo Segre 
Changed-By: Stuart Prescott 
Description:
 horae  - interactive graphical processing and analysis of EXAFS data
Closes: 812652
Changes:
 horae (071~svn537-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix "FTBFS - Can't locate Module/Build.pm" by adding a build-dependency on
 libmodule-build-perl, with thanks to Logan Rosen (Closes: #812652).
Checksums-Sha1:
 3a1af829895b40cb3b6f462688a7c201e2216cc0 1886 horae_071~svn537-2.1.dsc
 351c97838bce432829bcc13a151aab74929f91c6 16984 
horae_071~svn537-2.1.debian.tar.xz
 c2ffdc79123c64e6ea7fa0d99e57a52789eb70b2 5057 
horae_071~svn537-2.1_20161107T000513z-67cba6d9.buildinfo
 850a8f4faa0fa99e697e7fcf3e9ee66c5c1ac70b 4864572 horae_071~svn537-2.1_all.deb
Checksums-Sha256:
 65bc821abaa2b7cd7c93a16605b3f6449e544bf89e31215b6fb5ed9264a29cdc 1886 
horae_071~svn537-2.1.dsc
 6674802c41aceb1dc3d9fa837ece417ac1962de9a8f0ebbe1a1e786eb2210c10 16984 
horae_071~svn537-2.1.debian.tar.xz
 d0f46d6516af010fe99aa0dca5d960f835dca6c83f7048ee48625fd10af28f8d 5057 
horae_071~svn537-2.1_20161107T000513z-67cba6d9.buildinfo
 6fbbf69d9b848aad50dc12b92da42ca2fffebc8bb6a564a4c36adcdd3eaa7526 4864572 
horae_071~svn537-2.1_all.deb
Files:
 bc917d6e54bf31c8f86a3e41cd21c957 1886 contrib/science optional 
horae_071~svn537-2.1.dsc
 03233748a06ca40005e724718bcd2f9c 16984 contrib/science optional 
horae_071~svn537-2.1.debian.tar.xz
 67cba6d91534f06bd7b5997450bd8806 5057 contrib/science optional 
horae_071~svn537-2.1_20161107T000513z-67cba6d9.buildinfo
 0f4a51113eca0748eada75947221c8f1 4864572 contrib/science optional 
horae_071~svn537-2.1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJYH8ZNAAoJELvBfrsTlvL3S2EP+gNs/W/YMP2n0hola++leLHh
xw4GKLRhcrDPLYZ86UpfQSlzAdO0eD2TOMjlf1kGoFQJUuqE2di80RUSyCdYUjnQ
f/2eMJotjDSLszx7nQWVpxNNcuKOSMvkF65+KjbVqy+QSLCVvVO+vK2Syw+76ouQ

Bug#812652: horae: FTBFS - Can't locate Module/Build.pm

2016-11-06 Thread Stuart Prescott
Hi!

I've uploaded an NMU to add the missing build-dependency along with the 
appropriate binary package.

diff attached!

cheers
Stuart

-- 
Stuart Prescotthttp://www.nanonanonano.net/   stu...@nanonanonano.net
Debian Developer   http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7diff -Nru horae-071~svn537/debian/changelog horae-071~svn537/debian/changelog
--- horae-071~svn537/debian/changelog	2015-01-11 07:54:01.0 +1100
+++ horae-071~svn537/debian/changelog	2016-11-07 11:04:20.0 +1100
@@ -1,3 +1,11 @@
+horae (071~svn537-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "FTBFS - Can't locate Module/Build.pm" by adding a build-dependency on
+libmodule-build-perl, with thanks to Logan Rosen (Closes: #812652).
+
+ -- Stuart Prescott   Mon, 07 Nov 2016 11:04:20 +1100
+
 horae (071~svn537-2) unstable; urgency=medium
 
   * Add Build-Depends on libpod-latex-perl (Closes: #772611)
diff -Nru horae-071~svn537/debian/control horae-071~svn537/debian/control
--- horae-071~svn537/debian/control	2015-01-11 07:53:03.0 +1100
+++ horae-071~svn537/debian/control	2016-11-06 21:39:31.0 +1100
@@ -4,7 +4,8 @@
 Maintainer: Carlo Segre 
 Build-Depends: debhelper (>= 7)
 Build-Depends-Indep: perl (>= 5.6.0-16), libchemistry-elements-perl, 
- perl-tk (>= 804), libifeffit-perl, libpod-latex-perl
+ perl-tk (>= 804), libifeffit-perl, libpod-latex-perl,
+ libmodule-build-perl
 Homepage: http://cars9.uchicago.edu/~ravel/software/Welcome.html
 Standards-Version: 3.9.6
 


Bug#828616: [Pkg-auth-maintainers] Bug#828616: question about versions

2016-11-06 Thread Luke Faraone
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 6 November 2016 at 22:30, Robert Lange  wrote:
> I'm a concerned package user looking at this. According to tracker,
> yubico-piv-tool is slated for auto-removal because it fails to build
> with OpenSSL 1.1. However, the report shows that the version that fails
> to build is 1.0.3-1, whereas the current version in Sid and Stretch is
> 1.4.2-1. What's up with that?

Probably because it hasn't been fixed yet. I'm not intimately involved
in this project, but a quick review of the upstream changelog doesn't
indicate that compatibility has been added.

- --
Luke Faraone;; Debian & Ubuntu Developer; Sugar Labs; MIT SIPB
lfaraone on irc.[freenode,oftc].net -- https://luke.wf/ohhello
PGP fprint: 8C82 3DED 10AA 8041 639E  1210 5ACE 8D6E 0C14 A470
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJYH8IeAAoJENjr+MERubUggyMP/0eJPDotS+zfqYX0Kk2bZoVw
Uoq1MMWDWFTojuTMtzk+HXQPo4hAeKrT3SCX2oU/kjHipaJU0qfsyV11F4xFggzn
S88kC1xQruyVqEkAudPKbW2VXt1gob79x3TTmLBYoY64iKBSz3N7uOwp8N5U7DZ4
k1V5NU/3FmkTFP8ienNpV+U3y1Vqhguwf8yi1Zd4C6/SSYHUJet1pwmQ4XGSnu0N
cKNxdqF0rxBqlOwu3Gp/mB5S/DRCvxMQataE22RA5LInJMdOT5mNYBCJQON4ADHJ
ckLiKPD0QF8PDqD+z7XGCVWYI4ULZGPaQM6dfAps40YJdhtns5DFciznoXTDMV62
7KBXkCI5dphJ+kBfdBrQDTpBivOHwMHG5nU3amVk7PQFyixD1N19H0SgsAdrbJmz
7tCFRh3anusnClQOkHFNoPouufLH97/uQfF4M7AZ3ZAOCWJf+Ua2+mGnSq+WYiuo
2tb/SpuglNnF1+dB8WH73YU3DF4OdIm9nX60nokS+L6gjl3KmfW8eLdsLGsWoDd7
wAFxw63dyF8eW4UlH3Vl8JZlo15dLbnrJS0w3oSXRghPbTN8eBh54MWpLPrkaImk
UVz98yJB0+NsSKuo4CtCxfJETRLggCbFiHeSDupdli/Uy6pwJX4QfPypO5nOZoB1
jnhpLA/w0KNjnWv1As9L
=pcBZ
-END PGP SIGNATURE-



Bug#811800: marked as done (fityk: FTBFS with GCC 6: error: reference is ambiguous)

2016-11-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Nov 2016 23:48:54 +
with message-id 
and subject line Bug#811800: fixed in fityk 1.3.0-1
has caused the Debian Bug report #811800,
regarding fityk: FTBFS with GCC 6: error: reference is ambiguous
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.)


-- 
811800: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811800
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fityk
Version: 1.2.1-0.1
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-reference-ambiguous

This package fails to build with GCC 6.  GCC 6 has not been released
yet, but it's expected that GCC 6 will become the default compiler for
stretch.

Note that only the first error is reported; there might be more.  You
can find a snapshot of GCC 6 in experimental.  To build with GCC 6,
you can set CC=gcc-6 CXX=g++-6 explicitly.

You may be able to find out more about this issue at
https://gcc.gnu.org/gcc-6/changes.html

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> 
> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. -Wdate-time 
> -D_FORTIFY_SOURCE=2 -I/usr/include/lua5.1 -g -O2 -fstack-protector-strong 
> -Wformat -Werror=format-security -c swig/fityk_lua.cpp -o 
> swig/libfityk_la-fityk_lua.o
> /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I..  
>  -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/lua5.1  -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -c -o 
> cmpfit/libfityk_la-mpfit.lo `test -f 'cmpfit/mpfit.c' || echo 
> './'`cmpfit/mpfit.c
> mgr.cpp: In member function 'int 
> fityk::VariableManager::add_variable(fityk::Variable*)':
> mgr.cpp:251:5: warning: 'template class std::auto_ptr' is deprecated 
> [-Wdeprecated-declarations]
>  auto_ptr var(new_var);
>  ^~~~
> 
> In file included from /usr/include/c++/6/memory:81:0,
>  from /usr/include/boost/config/no_tr1/memory.hpp:21,
>  from /usr/include/boost/smart_ptr/shared_ptr.hpp:23,
>  from /usr/include/boost/shared_ptr.hpp:17,
>  from tplate.h:9,
>  from mgr.h:9,
>  from mgr.cpp:5:
> /usr/include/c++/6/bits/unique_ptr.h:49:28: note: declared here
>template class auto_ptr;
> ^~~~
> 
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time 
> -D_FORTIFY_SOURCE=2 -I/usr/include/lua5.1 -g -O2 -fstack-protector-strong 
> -Wformat -Werror=format-security -c cmpfit/mpfit.c -o 
> cmpfit/libfityk_la-mpfit.o
> logic.cpp: In member function 'void fityk::Ftk::import_dataset(int, const 
> string&, const string&, const string&)':
> logic.cpp:234:13: warning: 'template class std::auto_ptr' is 
> deprecated [-Wdeprecated-declarations]
>  auto_ptr data(new Data(this));
>  ^~~~
> 
> In file included from /usr/include/c++/6/memory:81:0,
>  from /usr/include/boost/smart_ptr/scoped_ptr.hpp:21,
>  from /usr/include/boost/scoped_ptr.hpp:14,
>  from logic.h:8,
>  from logic.cpp:5:
> /usr/include/c++/6/bits/unique_ptr.h:49:28: note: declared here
>template class auto_ptr;
> ^~~~
> 
> guess.cpp:23:7: error: reference to 'array' is ambiguous
>  const array Guess::linear_traits =
>^
> 
> In file included from guess.h:9:0,
>  from guess.cpp:5:
> /usr/include/boost/array.hpp:60:11: note: candidates are: template long unsigned int N> class boost::array
>  class array {
>^
> 
> In file included from /usr/include/c++/6/tuple:39:0,
>  from /usr/include/c++/6/functional:55,
>  from /usr/include/c++/6/memory:79,
>  from model.h:9,
>  from guess.cpp:12:
> /usr/include/c++/6/array:90:12: note: template long unsigned int _Nm> struct std::array
>  struct array
> ^
> 
> guess.cpp:25:7: error: reference to 'array' is ambiguous
>  const array Guess::peak_traits =
>^
> 
> In file included from guess.h:9:0,
>  from guess.cpp:5:
> /usr/include/boost/array.hpp:60:11: note: candidates are: template long unsigned int N> class boost::array
>  class array {
>^
> 
> In file included from /usr/include/c++/6/tuple:39:0,
>  from /usr/include/c++/6/functional:55,
>  from /usr/include/c++/6/memory:79,
>  from model.h:9,
>   

Bug#828616: question about versions

2016-11-06 Thread Robert Lange
I'm a concerned package user looking at this. According to tracker,
yubico-piv-tool is slated for auto-removal because it fails to build
with OpenSSL 1.1. However, the report shows that the version that fails
to build is 1.0.3-1, whereas the current version in Sid and Stretch is
1.4.2-1. What's up with that?



Bug#842878: Asterisk crashes with pjproject 2.5.5

2016-11-06 Thread Gedalya
On 11/06/2016 05:50 PM, Bernhard Schmidt wrote:
> Nothing productive on the upstream mailinglist (or rather disturbing,
> they say that ABI can change in backward incompatible way even in minor
> versions and you're always expected to recompile),
Yea, I followed the conversation there. Looks rather grim.

>  BUT thanks to Stepan
> Golosunov and Tzafrir in Bug#828240 there now seems to be a way to build
> Asterisk 13.12.1 against OpenSSL 1.1.0. 
>
> I have tested that build (built against pjproject 2.5.5~dfsg-2 in sid)
> and it does not crash for me.
OK, a little confused here: the resulting asterisk will link against both 
libssl1.1 and libssl1.0.2 (via pjsip) during runtime?
Does that kind of thing work?


> It will probably take a few more days to fully test this (and import a
> few other crash fixes for pjproject as well for good measure),
Agreed, basically all the revisions in SVN related to DNS resolution since 
2.5.5 look important.

Anyhow, I'll try this on my end soon and let you know how it went.



Bug#840806: marked as done (libgd2: CVE-2016-6911: invalid read in gdImageCreateFromTiffPtr())

2016-11-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Nov 2016 23:04:10 +
with message-id 
and subject line Bug#840806: fixed in libgd2 2.2.3-87-gd0fec80-2
has caused the Debian Bug report #840806,
regarding libgd2: CVE-2016-6911: invalid read in gdImageCreateFromTiffPtr()
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.)


-- 
840806: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840806
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgd2
Version: 2.1.0-5
Severity: grave
Tags: security upstream patch
Control: fixed -1 2.1.0-5+deb8u7

For tracking the isssue.

DSA-3693-1 included the patch
0020-Fix-invalid-read-in-gdImageCreateFromTiffPtr.patch to fix:

> Subject: Fix invalid read in gdImageCreateFromTiffPtr()

with patch included in the 2.1.0-5+deb8u7 upload.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: libgd2
Source-Version: 2.2.3-87-gd0fec80-2

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

Debian distribution maintenance software
pp.
Ondřej Surý  (supplier of updated libgd2 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, 06 Nov 2016 23:38:28 +0100
Source: libgd2
Binary: libgd-tools libgd-dev libgd3
Architecture: source
Version: 2.2.3-87-gd0fec80-2
Distribution: unstable
Urgency: medium
Maintainer: GD team 
Changed-By: Ondřej Surý 
Description:
 libgd-dev  - GD Graphics Library (development version)
 libgd-tools - GD command line tools and example code
 libgd3 - GD Graphics Library
Closes: 840806
Changes:
 libgd2 (2.2.3-87-gd0fec80-2) unstable; urgency=medium
 .
   * [CVE-2016-6911]: Fix invalid read in gdImageCreateFromTiffPtr()
 (Closes: #840806)
Checksums-Sha1:
 9123a601d3138d9432c2ff3ce068dc498751d53a 2363 libgd2_2.2.3-87-gd0fec80-2.dsc
 c6249f343cd0471ca5e1a8bfd62cac7572e1ebbb 26940 
libgd2_2.2.3-87-gd0fec80-2.debian.tar.xz
Checksums-Sha256:
 fb07d6d50e132696c4133949c317c24b430f52748d1b39b4904e900cb83c6d98 2363 
libgd2_2.2.3-87-gd0fec80-2.dsc
 e3d5fdcd9b05ba919650e2ef79bebb0f3e310cc0d080d79461a2a3c405869c90 26940 
libgd2_2.2.3-87-gd0fec80-2.debian.tar.xz
Files:
 e5a5e3b76a1d0d44cf255f00a59eb399 2363 graphics optional 
libgd2_2.2.3-87-gd0fec80-2.dsc
 76880184a6a1f838a7388d0d0a441390 26940 graphics optional 
libgd2_2.2.3-87-gd0fec80-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQJ8BAEBCgBmBQJYH7KiXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHp+0P/RFnlksPwhEXQMUazTbjA4h2
bs81mmY2PLf2Wuf27lw+5anAxef6sqUADeOwKRbgB2rsY/0FbeSKBmXQN6bwrFl2
AyXgNhaQelLv/R8lW+9I75A3mUofWaBnVQkzJ70AnOHVlcx72uBYpqAjjFCCNOeZ
ppzSIeNtU3WVAsplrHyzawaPheSLmOGqkPczNny/pvQlLnS6vFXM/o1tAMRIwyyV
7QbEIVZkl5mKoH8XDsctCmGJ75I+fAzwOV7wYFPBtPlh3fANkHZe9naox4SkXXBO
FUoChJyLoFB0KsZyyD8m+qgxMifRPJjInLo47Jx2XEub9i5gza+4RM4UDKsz8s49
urwNRvzsJavMN/bOQ5tItftQeUmFAFo1mG5SaUqeBb64S+JCz8egdcDZi2WI+lex
BQum5mq9stn84Mtyu+TotPWqXaNqzKDmRlmdpP7q1VIeezcY2zxq76wFmFJxEIWn
NkuT9B1g2XaEBFLNxCvteE9TXr97S5zdMVTRLVAv2qMqN1GVABac9oUxct84rOON
6lWfTsYgsHvpzTZG4TbouUm+y01CqPnLlxXbvo8gTltRnCA5Ti3lE+hR0I9Rgbs6
nCrw20wdcUZmS0iYKfIbHZMiCv4TFgyTFhQ8x2kt2JZz+uFGJ39zuJcDeuwIkAoe
ucgwPf3EKZDQW1Yj31Kd
=YBLG
-END PGP SIGNATURE End Message ---


Bug#843482: aubio: FTBFS on PowerPC variants: test_zeros fails

2016-11-06 Thread Aaron M. Ucko
Source: aubio
Version: 0.4.1-2.2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Builds of aubio for ppc64el and the non-release architectures powerpc
and ppc64 all failed; see below for an excerpt from the ppc64el log at
https://buildd.debian.org/status/fetch.php?pkg=aubio=ppc64el=0.4.3-1=1478460825
Could you please take a look?

Thanks!

  ==
  FAIL: test_zeros (test_phasevoc.aubio_pvoc_test_case)
  check the resynthesis of zeros gives zeros
  --
  Traceback (most recent call last):
File "/«PKGBUILDDIR»/python/tests/test_phasevoc.py", line 49, in test_zeros
  assert_equal ( s.phas, 0.)
File "/usr/lib/python2.7/dist-packages/numpy/testing/utils.py", line 322, 
in assert_equal
  return assert_array_equal(actual, desired, err_msg, verbose)
File "/usr/lib/python2.7/dist-packages/numpy/testing/utils.py", line 813, 
in assert_array_equal
  verbose=verbose, header='Arrays are not equal')
File "/usr/lib/python2.7/dist-packages/numpy/testing/utils.py", line 739, 
in assert_array_compare
  raise AssertionError(msg)
  AssertionError: 
  Arrays are not equal
  
  (mismatch 34.6978557505%)
   x: array([ 0.  ,  0.  ,  0.  ,  0.  ,  0.  ,  0.  ,
  0.  ,  0.  ,  0.  ,  0.  ,  0.  ,  0.  ,
  0.  ,  0.  ,  0.  ,  0.  , -0.  ,  0.  ,...
   y: array(0.0)
  
  ==
  FAIL: test_zeros (test_fft.aubio_fft_test_case)
  check the transform of zeros is all zeros
  --
  Traceback (most recent call last):
File "/«PKGBUILDDIR»/python/tests/test_fft.py", line 36, in test_zeros
  assert_equal ( fftgrain.phas, 0 )
File "/usr/lib/python2.7/dist-packages/numpy/testing/utils.py", line 322, 
in assert_equal
  return assert_array_equal(actual, desired, err_msg, verbose)
File "/usr/lib/python2.7/dist-packages/numpy/testing/utils.py", line 813, 
in assert_array_equal
  verbose=verbose, header='Arrays are not equal')
File "/usr/lib/python2.7/dist-packages/numpy/testing/utils.py", line 739, 
in assert_array_compare
  raise AssertionError(msg)
  AssertionError: 
  Arrays are not equal
  
  (mismatch 31.5175097276%)
   x: array([ 0.  ,  0.  ,  0.  ,  0.  ,  0.  ,  0.  ,
  0.  ,  0.  ,  0.  ,  0.  ,  0.  ,  0.  ,
  0.  ,  0.  ,  0.  ,  0.  , -0.  ,  0.  ,...
   y: array(0)
  
  --
  Ran 745 tests in 12.995s
  
  FAILED (failures=2, skipped=4)

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu



Bug#843481: asn1c: FTBFS: cannot stat 'asn1c-usage.pdf': No such file or directory

2016-11-06 Thread Aaron M. Ucko
Source: asn1c
Version: 0.9.27+dfsg-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Builds of asn1c covering only its main (architecture-dependent) binary
package have been failing (except, for some reason, on mips):

  Making install in docsrc
  make[4]: Entering directory '/«BUILDDIR»/asn1c-0.9.27+dfsg/doc/docsrc'
  make[5]: Entering directory '/«BUILDDIR»/asn1c-0.9.27+dfsg/doc/docsrc'
  make[5]: Nothing to be done for 'install-exec-am'.
  mkdir -p /«BUILDDIR»/asn1c-0.9.27+dfsg/debian/tmp/usr/share/doc/asn1c-doc
  cp -a asn1c-usage.pdf 
/«BUILDDIR»/asn1c-0.9.27+dfsg/debian/tmp/usr/share/doc/asn1c-doc
  cp: cannot stat 'asn1c-usage.pdf': No such file or directory
  Makefile:458: recipe for target 'install-data-local' failed
  make[5]: *** [install-data-local] Error 1

Could you please take a look?

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu



Bug#842878: Asterisk crashes with pjproject 2.5.5

2016-11-06 Thread Bernhard Schmidt
On Fri, Nov 04, 2016 at 11:02:03AM +0100, Bernhard Schmidt wrote:

Hi,

> > I decided to try this: I made a sid chroot, manually downgraded to
> > libssl-dev 1.0.2j-1 from stretch, and built asterisk from the
> > current packaging git head (ec0143a).  I actually enabled
> > OpenSSL-1.1.0-support.patch while I was at it.
> > 
> > Ultimately, running this with pjproject 2.5.5~dfsg-2 failed at the same 
> > stage, but with a different assert:
> > 
> > asterisk: ../src/pjsip/sip_auth_client.c:507: pjsip_auth_clt_deinit: 
> > Assertion `sess && sess->endpt' failed.
> > Aborted
> 
> Thanks. I have also tested that a fresh rebuild of 2.5.1 does not exhibit
> the problem, so it is not caused by updated build-deps.
> 
> Upstream recommends to disable assertions in production builds, see
> 
> https://trac.pjsip.org/repos/wiki/FAQ#assert
> 
> When I do this I get a full-blown segfault (and we lose a symbol, so
> although we only have one rdep it would technically involve a library
> transition). I've reported the segfault to the upstream mailinglist

Nothing productive on the upstream mailinglist (or rather disturbing,
they say that ABI can change in backward incompatible way even in minor
versions and you're always expected to recompile), BUT thanks to Stepan
Golosunov and Tzafrir in Bug#828240 there now seems to be a way to build
Asterisk 13.12.1 against OpenSSL 1.1.0. 

I have tested that build (built against pjproject 2.5.5~dfsg-2 in sid)
and it does not crash for me.

It will probably take a few more days to fully test this (and import a
few other crash fixes for pjproject as well for good measure), but now
the future looks a bit less dark than before. I will probably disable
the pjsip asserts as well, following upstream recommendation.

Bernhard


signature.asc
Description: Digital signature


Bug#833218: marked as done (markupsafe: Uses obsolete compressor for .deb data.tar member)

2016-11-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Nov 2016 22:50:59 +
with message-id 
and subject line Bug#833218: fixed in markupsafe 0.23-3
has caused the Debian Bug report #833218,
regarding markupsafe: Uses obsolete compressor for .deb data.tar member
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.)


-- 
833218: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833218
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: markupsafe
Source-Version: 0.23-2
Severity: important
User: debian-d...@lists.debian.org
Usertags: dpkg-obsolete-deb-data-tar-compressor

Hi!

This source package builds one or more binary packages using the
deprecated compressor bzip2. The default has been xz for a while now
which should usually compress better than bzip2. If instead you'd like
speed then switch to use gzip.

Using a deprecated compressor when building binary packages will
become an error in the near future. Please update the packages.

See also .

Thanks,
Guillem
--- End Message ---
--- Begin Message ---
Source: markupsafe
Source-Version: 0.23-3

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

Debian distribution maintenance software
pp.
Piotr Ożarowski  (supplier of updated markupsafe 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, 06 Nov 2016 23:19:04 +0100
Source: markupsafe
Binary: python-markupsafe python-markupsafe-dbg python3-markupsafe 
python3-markupsafe-dbg
Architecture: source amd64
Version: 0.23-3
Distribution: unstable
Urgency: medium
Maintainer: Piotr Ożarowski 
Changed-By: Piotr Ożarowski 
Description:
 python-markupsafe - HTML/XHTML/XML string library for Python
 python-markupsafe-dbg - HTML/XHTML/XML string library for Python - debug 
version
 python3-markupsafe - HTML/XHTML/XML string library for Python 3
 python3-markupsafe-dbg - HTML/XHTML/XML string library for Python 3 - debug 
version
Closes: 833218
Changes:
 markupsafe (0.23-3) unstable; urgency=medium
 .
   [ Piotr Ożarowski ]
   * Add dh-python to Build-Depends
   * dh_builddeb now uses the default compression (xz) instead of bzip2
 (closes: #833218)
   * Standards-Version bumped to 3.9.8 (no changes needed)
 .
   [ Ondřej Nový ]
   * Fixed homepage (https)
   * Fixed VCS URL (https)
Checksums-Sha1:
 733539aecf37a4ebbcb5cd1459031c71e94e283d 2331 markupsafe_0.23-3.dsc
 c355bf92f06031f901ae8efa91db823c10f05c5d 3708 markupsafe_0.23-3.debian.tar.xz
 a0ded8393bd195651b7133c03b1225ae4828c228 7035 
markupsafe_0.23-3_20161106T21z-df3e937d.buildinfo
 62b5d91410b2899b6827f4afdba8a4898daad338 24688 
python-markupsafe-dbg_0.23-3_amd64.deb
 8fa8d1e8132a99a77790d8d289f6ec6caec98ea1 14394 
python-markupsafe_0.23-3_amd64.deb
 21c44b48610b708e3d35599c518163af79f7745a 29284 
python3-markupsafe-dbg_0.23-3_amd64.deb
 3029a4a2d20f801add4fba97e713bd22ec16d7e1 14836 
python3-markupsafe_0.23-3_amd64.deb
Checksums-Sha256:
 278f78205e2c2c6dd93345b67854c35c07f752e073fdd6506c7c8f141f381db0 2331 
markupsafe_0.23-3.dsc
 9ed07a691d404cf2bcf405aee611098f9d37dddbdc967c271c413029b65d21a5 3708 
markupsafe_0.23-3.debian.tar.xz
 dde158fbd7fa03cd3b7989298fbfce3d6b8ab0237ad71b7afc0ffd7623338968 7035 
markupsafe_0.23-3_20161106T21z-df3e937d.buildinfo
 2d230c14f936fd8af0704fc2e62d16908862b3617e7e36371a01b7829d7c5a67 24688 
python-markupsafe-dbg_0.23-3_amd64.deb
 b56abb3ac9798e9facf05b6083bc9bf030282635806d58fcc0c01a379465c213 14394 
python-markupsafe_0.23-3_amd64.deb
 97c669e256e45f8753141ca0663fb3a16f0aa13f9ed11f873c1ee5ffc4c5f19a 29284 
python3-markupsafe-dbg_0.23-3_amd64.deb
 eff50f7f39aea1d34c134d16149f5b572152083c1a0f89d2d64b2d84859d00e7 14836 
python3-markupsafe_0.23-3_amd64.deb
Files:
 3c2e04aeae7765d7baab88c93d9db678 2331 python optional markupsafe_0.23-3.dsc
 2248e693606da87580a2061f0d908a5d 3708 python optional 
markupsafe_0.23-3.debian.tar.xz
 df3e937df65241b89fef0902168f2fa3 7035 python optional 

Bug#840806: [pkg-GD-devel] Bug#840806: closed by Ondřej Surý <ond...@debian.org> (Bug#840806: fixed in libgd2 2.2.3-87-gd0fec80-1)

2016-11-06 Thread Ondřej Surý
Hi Salvatore,

you are right. I thought this patch has been already merged into
upstream git,
but it looks like it hasn't. I will upload fixed version to unstable
shortly.

Cheers,
-- 
Ondřej Surý 
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
Knot Resolver (https://www.knot-resolver.cz/) – secure, privacy-aware,
fast DNS(SEC) resolver

On Mon, Oct 31, 2016, at 14:16, Salvatore Bonaccorso wrote:
> Control: reopen -1 
> 
> Hi Ondřej,
> 
> While updating the security-tracker information I noticed:
> 
> On Mon, Oct 31, 2016 at 10:21:15AM +, Debian Bug Tracking System
> wrote:
> [...]
> > + [CVE-2016-6911]: invalid read in gdImageCreateFromTiffPtr()
> [...]
> 
> For the recently uploaded Version 2.2.3-87-gd0fec80-1. But comparing
> this with the patch applied in jessie-security, named
> 0020-Fix-invalid-read-in-gdImageCreateFromTiffPtr.patch
> 
> Is this patch missing for the unstable upload?
> 
> I'm reopening the bug just to be on the safe side, but happy to be
> corrected if I'm wrong!
> 
> Regards,
> Salvatore
> 
> -- 
> pkg-GD-devel mailing list
> pkg-gd-de...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-gd-devel



Bug#828240: asterisk: FTBFS with openssl 1.1.0

2016-11-06 Thread Bernhard Schmidt
On Sun, Nov 06, 2016 at 04:39:03PM +0400, Stepan Golosunov wrote:

Hi,

> 06.11.2016 в 16:18:32 +0400 Stepan Golosunov написал:
> > 03.11.2016 в 09:24:19 +0100 Bernhard Schmidt написал(а):
> > > - Asterisk is doing some weird stuff with macros in
> > >   
> > > https://sources.debian.net/src/asterisk/1:13.11.2~dfsg-1/main/libasteriskssl.c/
> > >   that causes the build against 1.1.0 to fail. This is beyond my C
> > >   knowledge. I will gladly test and accept any patch for that.
> > 
> > I think that
> > 
> > #if defined(HAVE_OPENSSL) && OPENSSL_VERSION_NUMBER >= 0x1010L
> > /* No explicit initialization is needed with OpenSSL 1.1.0.
> >All the functions called or overridden in this file were removed. */
> > #undef HAVE_OPENSSL
> > #endif
> > 
> > should be added after ASTERISK_FILE_VERSION in libasteriskssl.c.
> 
> After or inside
> 
> #ifdef HAVE_OPENSSL
> #include 
> #include 
> #endif
> 
> seems more apropriate as #include is still needed to get
> OPENSSL_VERSION_NUMBER.

Thanks a lot, your suggestion together with 
https://anonscm.debian.org/cgit/pkg-voip/asterisk.git/commit/?id=ec0143a92f4ced996be419bf49115be8f236e3ea

leads to something that builds and runs. Yay!

@Tzafrir: What do you think of this? Your patch is touching
main/libasteriskssl.c as well, but Stepan suggested to drop even more. 

Bernhard


signature.asc
Description: Digital signature


Processed: Bug#833218 marked as pending

2016-11-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tag 833218 pending
Bug #833218 [src:markupsafe] markupsafe: Uses obsolete compressor for .deb 
data.tar member
Added tag(s) pending.
> thanks
Stopping processing here.

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



Bug#833218: marked as pending

2016-11-06 Thread Piotr Ożarowski
tag 833218 pending
thanks

Hello,

Bug #833218 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://git.debian.org/?p=python-modules/packages/markupsafe.git;a=commitdiff;h=eddfa5d

---
commit eddfa5d77583e76ddbb47dca44d313eb22038a09
Author: Piotr Ożarowski 
Date:   Sun Nov 6 23:19:07 2016 +0100

close #833218 in changelog

diff --git a/debian/changelog b/debian/changelog
index 420d276..2610ab6 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,14 +1,15 @@
-markupsafe (0.23-3) UNRELEASED; urgency=medium
+markupsafe (0.23-3) unstable; urgency=medium
 
   [ Piotr Ożarowski ]
   * Add dh-python to Build-Depends
   * dh_builddeb now uses the default compression (xz) instead of bzip2
+(closes: #833218)
 
   [ Ondřej Nový ]
   * Fixed homepage (https)
   * Fixed VCS URL (https)
 
- -- Piotr Ożarowski   Thu, 20 Aug 2015 00:54:39 +0200
+ -- Piotr Ożarowski   Sun, 06 Nov 2016 23:19:04 +0100
 
 markupsafe (0.23-2) unstable; urgency=medium
 



Bug#828467: marked as done (opendnssec: FTBFS with openssl 1.1.0)

2016-11-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Nov 2016 22:21:11 +
with message-id 
and subject line Bug#828467: fixed in opendnssec 1:2.0.3-1
has caused the Debian Bug report #828467,
regarding opendnssec: FTBFS with openssl 1.1.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.)


-- 
828467: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828467
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: opendnssec
Version: 1.4.10-1
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/opendnssec_1.4.10-1_amd64-20160530-2113

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt
--- End Message ---
--- Begin Message ---
Source: opendnssec
Source-Version: 1:2.0.3-1

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

Debian distribution maintenance software
pp.
Ondřej Surý  (supplier of updated opendnssec 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, 06 Nov 2016 22:34:27 +0100
Source: opendnssec
Binary: opendnssec-common opendnssec opendnssec-doc opendnssec-enforcer 
opendnssec-enforcer-mysql opendnssec-enforcer-sqlite3 opendnssec-signer 
libhsm-bin
Architecture: source amd64 all
Version: 1:2.0.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian DNS Packaging 
Changed-By: Ondřej Surý 
Description:
 libhsm-bin - library for interfacing PKCS#11 Hardware Security Modules
 opendnssec - dependency package to install full OpenDNSSEC suite
 opendnssec-common - common configuration files for OpenDNSSEC suite
 opendnssec-doc - documentation for OpenDNSSEC suite
 opendnssec-enforcer - tool to prepare DNSSEC keys (common package)
 opendnssec-enforcer-mysql - tool to prepare DNSSEC keys (mysql backend)
 opendnssec-enforcer-sqlite3 - tool to prepare DNSSEC keys (sqlite3 backend)
 opendnssec-signer - daemon to sign DNS zone files periodically
Closes: 828467
Changes:
 opendnssec (1:2.0.3-1) unstable; urgency=medium
 .
   * Fix OpenSSL 1.1.0 Support (Closes: #828467)
   * Imported Upstream version 2.0.3
   * Add default-jdk to Build-Depends as "java is required for converting
 RelaxNG Compact to RelaxNG"
Checksums-Sha1:
 c466cfce608512a04b337548189230ce7878825c 2784 opendnssec_2.0.3-1.dsc
 22337cfac9a16b47d4f570e370317cb5412e3023 1539390 opendnssec_2.0.3.orig.tar.gz
 d47a45c9a1074a519789b2171d802bfdaddad8a1 20520 opendnssec_2.0.3-1.debian.tar.xz
 0d74ea9fa8d3248f67a35bd35d210354af0373e8 190300 
libhsm-bin-dbgsym_2.0.3-1_amd64.deb
 1271cdcdb12c6f65436823976f042d397b0d3967 70760 libhsm-bin_2.0.3-1_amd64.deb
 a681515f8649f625754eaca1236a9b1300b95df5 58024 
opendnssec-common_2.0.3-1_all.deb
 dd9f0e0b6112cae8b3a8f8f5c3f3fc420e74b53c 1573354 opendnssec-doc_2.0.3-1_all.deb
 84e9561bb921c935c016eb43c7e1b76e7fc336ef 1021864 
opendnssec-enforcer-mysql-dbgsym_2.0.3-1_amd64.deb
 acaa17d6dd0168826a78ffa6a654f11e8e30e474 228578 
opendnssec-enforcer-mysql_2.0.3-1_amd64.deb
 372fb0c65709f15c0a9d391dadfbab81a1c7f535 1000244 
opendnssec-enforcer-sqlite3-dbgsym_2.0.3-1_amd64.deb
 76b0449823ec8053a98c43b4cfd7cf8c40349520 224180 
opendnssec-enforcer-sqlite3_2.0.3-1_amd64.deb
 1b7ae65d2c6f309cd08d97c72a836c69fe79d2d1 31806 
opendnssec-enforcer_2.0.3-1_all.deb
 caa036b10c09dfd268f9b445b30d8e70ceebc2c7 620760 
opendnssec-signer-dbgsym_2.0.3-1_amd64.deb
 8660d249307d3999163e98dd6252cf4224e23e28 182370 

Processed: block 843376 with 843476, block 843377 with 843476

2016-11-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> block 843376 with 843476
Bug #843376 [src:gcc-mingw-w64] gcc-mingw-w64: FTBFS (uudecode: Command not 
found)
843376 was not blocked by any bugs.
843376 was not blocking any bugs.
Added blocking bug(s) of 843376: 843476
> block 843377 with 843476
Bug #843377 [src:gnat-mingw-w64] gnat-mingw-w64: FTBFS (uudecode: Command not 
found)
843377 was not blocked by any bugs.
843377 was not blocking any bugs.
Added blocking bug(s) of 843377: 843476
> thanks
Stopping processing here.

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



Bug#843477: src:kamailio: stop using libval-dev for DNSSEC validation

2016-11-06 Thread Ondřej Surý
Package: src:kamailio
Version: 4.4.3-2
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear maintainer,

please stop using libdnsval-dev for DNSSEC validation.  src:dnsval
is very poorly upstream maintained (SVN repository, issue tracker,
mailing list are non-functional) and I am going to schedule it for
removal for stretch.

In a long term you should migrated to better and maintained library
(preferrably getdns or just libunbound), but now please just drop
it.

Cheers,
Ondrej

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

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

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQJ8BAEBCgBmBQJYH6ugXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHKTEP+gJ+XH9lI2j1G1YQlp479mrT
QyD8IZKnJfqm/w08+q834MF/3jtBi+YR+7mElbMP4NpHELMgCxg5Pt9PqcO6D0dh
IowNEegvaqVLfYPwMfhDbNGVgRN4QqPTVwZ4jwsWhcPDRdGMhsWxnhf9lAiwhkNX
4oom93kEpA/LrNoP+Be/5z1VL8m/NpFTE/ORXTQ6fmVSf+QgHS2rWLBrdvVeI5Sn
rn34N+K8PQhhrruuoQyXyDInUKa1wQSWZ1zy6apPHkrGnD0f1YjR84k5MY+rg8St
MYewM1rdEU6fMphQccCDuAtXJ7E58c4zFGeZlli6uTPXDrlOAIAThmEyGupn//2Q
izuVK7Jhr6guSJpl8jWNOg2IsSriQSc0mMJyUf4O5a1ZTBg31IyhZDnLk44SdPhK
/zIjPuTNMjlERmah9dQkx2J9ORe75hTT9L0QA3fRWHsHBoHnIP4aMuyjpqgJcREH
HJ9bQwD7/B3bv8IKsSy7M9v0aKbBjA/P/+8OPIqqbWk3dOVFG0+PAVNvWQrVJ6Ge
7wl0zVYAD6YqiKZNFTRpf6NYJ7SN64lJhg8OvkXbl5Vyy6XLvY5aNhk/ukCW2ap3
r0UQcb3dEVx+5sncXtdB5FlYgNJ2rdAEtAAeDwHO1toPxWYqFiOAZbF0N0N/1WN9
t5LdwPupjo9F0UQQTKmU
=GkaB
-END PGP SIGNATURE-



Bug#843474: ruby-ethon: FTBFS: [BUG] Segmentation fault at 0x007f2767e0d800

2016-11-06 Thread Chris Lamb
Source: ruby-ethon
Version: 0.9.0-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

ruby-ethon fails to build from source in unstable/amd64:

  []

when mime type
  sets mime type to text
when no mime type
  sets mime type to default application/octet-stream
  when no MIME
    sets mime type to default application/octet-stream
  when params contains file
    transforms
  when params key contains a null byte
    preserves
  when params value contains a null byte
    preserves
#empty?
  when params empty
    returns true
  when params not empty
    returns false
  
  Ethon::Easy::ResponseCallbacks
#on_complete
  responds
  when no block given
    returns @on_complete
  when block given
    stores
  when multiple blocks given
    stores
#on_headers
  responds
  when no block given
    returns @on_headers
  when block given
    stores
  when multiple blocks given
    stores
#on_body
  responds
  when no block given
    returns @on_body
  when block given
    stores
  when multiple blocks given
    stores
#complete
  executes blocks and passes self
  when @on_complete nil
    doesn't raise
#headers
  executes blocks and passes self
  when @on_headers nil
    doesn't raise
#body
  executes blocks and passes self
  executes blocks and passes chunk
  when @on_body nil
    doesn't raise
  
  Ethon::Easy::Util
escape_zero_byte
  when value has no zero byte
    returns same value
  when value has zero byte
    returns escaped
  
  Ethon::Easy
.new
  inits curl
  when options are empty
    sets only callbacks
  when options not empty
when followlocation is set
  sets followlocation
#set_attributes
  when options are empty
    sets only callbacks
  when options aren't empty
when valid key
  sets
when invalid key
  raises invalid option error
#reset
  resets url
  resets escape?
  resets hash
  resets easy handle
  resets on_complete
  resets on_headers
  resets on_body
#dup
  sets a new handle
  preserves url
  preserves on_complete callback
  preserves on_headers callback
  D, [2016-11-06T22:07:14.550828 #4814] DEBUG -- : ETHON: performed EASY 
effective_url=http://localhost:3001/ response_code=200 return_code=ok 
total_time=0.007464
  D, [2016-11-06T22:07:14.592603 #4814] DEBUG -- : ETHON: performed EASY 
effective_url=http://localhost:3001/ response_code=200 return_code=ok 
total_time=0.007464
  preserves body_write_callback of original handle
  D, [2016-11-06T22:07:14.602889 #4814] DEBUG -- : ETHON: performed EASY 
effective_url=http://localhost:3001/ response_code=200 return_code=ok 
total_time=0.008938
  D, [2016-11-06T22:07:14.644777 #4814] DEBUG -- : ETHON: performed EASY 
effective_url=http://localhost:3001/ response_code=200 return_code=ok 
total_time=0.008938
  sets new body_write_callback of duplicated handle
  D, [2016-11-06T22:07:14.655129 #4814] DEBUG -- : ETHON: performed EASY 
effective_url=http://localhost:3001/ response_code=200 return_code=ok 
total_time=0.008426
  D, [2016-11-06T22:07:14.696761 #4814] DEBUG -- : ETHON: performed EASY 
effective_url=http://localhost:3001/ response_code=200 return_code=ok 
total_time=0.008426
  preserves headers_write_callback of original handle
  D, [2016-11-06T22:07:14.706802 #4814] DEBUG -- : ETHON: performed EASY 
effective_url=http://localhost:3001/ response_code=200 return_code=ok 
total_time=0.008366
  D, [2016-11-06T22:07:14.748684 #4814] DEBUG -- : ETHON: performed EASY 
effective_url=http://localhost:3001/ response_code=200 return_code=ok 
total_time=0.008366
  sets new headers_write_callback of duplicated handle
  resets response_body
  resets response_headers
  D, [2016-11-06T22:07:14.759694 #4814] DEBUG -- : ETHON: performed EASY 
effective_url=http://localhost:3001/ response_code=200 return_code=ok 
total_time=0.008385
  sets response_body for duplicated Easy
  D, [2016-11-06T22:07:14.768601 #4814] DEBUG -- : ETHON: performed EASY 
effective_url=http://localhost:3001/ response_code=200 return_code=ok 

Bug#842576: (caja:1599): Gtk-ERROR

2016-11-06 Thread Steve Cotton
On Sun, Oct 30, 2016 at 04:04:57PM +0200, Vangelis Mouhtsis wrote:
> Package: caja
> Version: 1.16.1-1
> ...
> debsums: changed file /usr/bin/caja (from caja package)

Hi Vangelis,

That debsums error suggests that this is just local file corruption.
Please would you try reinstalling the package?

Thanks,
Steve



Bug#843077: marked as done (php-memcached must build-depend on zlib1g-dev)

2016-11-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Nov 2016 22:06:03 +
with message-id 
and subject line Bug#843077: fixed in php-memcached 
3.0.0a1-61-g583ecd6+2.2.0++-1
has caused the Debian Bug report #843077,
regarding php-memcached must build-depend on zlib1g-dev
to be marked as done.

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

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


-- 
843077: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843077
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php-memcached
Version: 3.0.0a1-13-g6ee96ca+2.2.0-3
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

php-memcached fails to build from source in unstable/amd64:

  […]

  configure:2866: result: o
  configure:2870: checking whether we are using the GNU C compiler
  configure:2889: cc -c -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20161103173002.ca87pUni3i.db.php-memcached/php-memcached-3.0.0a1-13-g6ee96ca+2.2.0=.
 -fPIE -fstack-protector-strong -Wformat -Werror=format-security -Wall 
-pedantic -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c >&5
  configure:2889: $? = 0
  configure:2898: result: yes
  configure:2907: checking whether cc accepts -g
  configure:2927: cc -c -g -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c >&5
  configure:2927: $? = 0
  configure:2968: result: yes
  configure:2985: checking for cc option to accept ISO C89
  configure:3048: cc  -c -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20161103173002.ca87pUni3i.db.php-memcached/php-memcached-3.0.0a1-13-g6ee96ca+2.2.0=.
 -fPIE -fstack-protector-strong -Wformat -Werror=format-security -Wall 
-pedantic -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c >&5
  configure:3048: $? = 0
  configure:3061: result: none needed
  configure:3087: checking how to run the C preprocessor
  configure:3118: cc -E -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c
  configure:3118: $? = 0
  configure:3132: cc -E -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c
  conftest.c:9:28: fatal error: ac_nonexistent.h: No such file or directory
   #include 
  ^
  compilation terminated.
  configure:3132: $? = 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 ""
  | /* end confdefs.h.  */
  | #include 
  configure:3157: result: cc -E
  configure:3177: cc -E -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c
  configure:3177: $? = 0
  configure:3191: cc -E -Wdate-time -D_FORTIFY_SOURCE=2 conftest.c
  conftest.c:9:28: fatal error: ac_nonexistent.h: No such file or directory
   #include 
  ^
  compilation terminated.
  configure:3191: $? = 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 ""
  | /* end confdefs.h.  */
  | #include 
  configure:3222: checking for icc
  configure:3231: result: no
  configure:3245: checking for suncc
  configure:3254: result: no
  configure:3272: checking whether cc understands -c and -o together
  configure:3300: cc -c conftest.c -o conftest2.o >&5
  configure:3304: $? = 0
  configure:3310: cc -c conftest.c -o conftest2.o >&5
  configure:3314: $? = 0
  configure:3369: result: yes
  configure:3383: checking for system library directory
  configure:3398: result: lib
  configure:3405: checking if compiler supports -R
  configure:3424: cc -o conftest -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20161103173002.ca87pUni3i.db.php-memcached/php-memcached-3.0.0a1-13-g6ee96ca+2.2.0=.
 -fPIE -fstack-protector-strong -Wformat -Werror=format-security -Wall 
-pedantic -Wdate-time -D_FORTIFY_SOURCE=2 -fPIE -pie -Wl,-z,relro -Wl,-z,now 
-Wl,--as-needed conftest.c -R /usr/lib  >&5
  cc: error: unrecognized command line option '-R'; did you mean '-R'?
  configure:3424: $? = 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 ""
  | /* end confdefs.h.  */
  | 
  | int
  | main ()
  | {
  | 
  |   ;
  |   return 0;
  | }
  configure:3434: result: no
  configure:3439: checking if compiler supports -Wl,-rpath,
  configure:3458: cc -o conftest -g -O2 

Bug#828278: marked as done (datovka: FTBFS with openssl 1.1.0)

2016-11-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Nov 2016 23:06:31 +0100
with message-id 
<1478469991.1052191.779205785.0056f...@webmail.messagingengine.com>
and subject line Fixed in 4.7.0-1
has caused the Debian Bug report #828278,
regarding datovka: FTBFS with openssl 1.1.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.)


-- 
828278: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828278
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: datovka
Version: 4.6.0-1
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/datovka_4.6.0-1_amd64-20160529-1413

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt
--- End Message ---
--- Begin Message ---
Version: 4.7.0-1

-- 
Ondřej Surý 
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
Knot Resolver (https://www.knot-resolver.cz/) – secure, privacy-aware,
fast DNS(SEC) resolver
Vše pro chleba (https://vseprochleba.cz) – Mouky ze mlýna a potřeby pro
pečení chleba všeho druhu--- End Message ---


Processed: your mail

2016-11-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 843413 qtdeclarative-opensource-src
Bug #843413 [plasma-workspace] plasma-workspace: plasmashell fail to start
Bug reassigned from package 'plasma-workspace' to 
'qtdeclarative-opensource-src'.
No longer marked as found in versions plasma-workspace/4:5.8.2-1.
Ignoring request to alter fixed versions of bug #843413 to the same values 
previously set
> forcemerge 843208 843413
Bug #843208 {Done: Dmitry Shachnev } 
[qtdeclarative-opensource-src] plasma-workspace: Does not start plasmashell on 
the KDE.
Bug #843250 {Done: Dmitry Shachnev } 
[qtdeclarative-opensource-src] qml-module-qtquick-controls is broken and breaks 
software using it
Bug #843332 {Done: Dmitry Shachnev } 
[qtdeclarative-opensource-src] /usr/bin/plasmashell: segmentation fault when 
attempting to start plasmashell after upgrade
Bug #843342 {Done: Dmitry Shachnev } 
[qtdeclarative-opensource-src] plasma-workspace: plasmashell crashes after 
startup
Bug #843363 {Done: Dmitry Shachnev } 
[qtdeclarative-opensource-src] plasmashell: segfault in libQt5Core.so.5.7.1
Bug #843413 [qtdeclarative-opensource-src] plasma-workspace: plasmashell fail 
to start
Set Bug forwarded-to-address to 'https://bugreports.qt.io/browse/QTBUG-56932'.
Severity set to 'grave' from 'important'
Marked Bug as done
Added indication that 843413 affects sddm,plasma-workspace
Marked as fixed in versions qtdeclarative-opensource-src/5.7.1~20161021-5.
There is no source info for the package 'qtdeclarative-opensource-src' at 
version '5.7.1~20161021-4' with architecture ''
Unable to make a source version for version '5.7.1~20161021-4'
Marked as found in versions 5.7.1~20161021-4.
Bug #843250 {Done: Dmitry Shachnev } 
[qtdeclarative-opensource-src] qml-module-qtquick-controls is broken and breaks 
software using it
Bug #843332 {Done: Dmitry Shachnev } 
[qtdeclarative-opensource-src] /usr/bin/plasmashell: segmentation fault when 
attempting to start plasmashell after upgrade
Bug #843342 {Done: Dmitry Shachnev } 
[qtdeclarative-opensource-src] plasma-workspace: plasmashell crashes after 
startup
Bug #843363 {Done: Dmitry Shachnev } 
[qtdeclarative-opensource-src] plasmashell: segfault in libQt5Core.so.5.7.1
Merged 843208 843250 843332 843342 843363 843413
> thanks
Stopping processing here.

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



Bug#828551: marked as done (softhsm2: FTBFS with openssl 1.1.0)

2016-11-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Nov 2016 21:53:30 +
with message-id 
and subject line Bug#828551: fixed in softhsm2 2.2.0~rc1-1
has caused the Debian Bug report #828551,
regarding softhsm2: FTBFS with openssl 1.1.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.)


-- 
828551: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828551
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: softhsm2
Version: 2.1.0-3
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/softhsm2_2.1.0-3_amd64-20160529-1538

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt
--- End Message ---
--- Begin Message ---
Source: softhsm2
Source-Version: 2.2.0~rc1-1

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

Debian distribution maintenance software
pp.
Ondřej Surý  (supplier of updated softhsm2 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, 06 Nov 2016 22:17:08 +0100
Source: softhsm2
Binary: softhsm2-common softhsm2 libsofthsm2-dev libsofthsm2 softhsm2-dbg
Architecture: source
Version: 2.2.0~rc1-1
Distribution: unstable
Urgency: medium
Maintainer: Ondřej Surý 
Changed-By: Ondřej Surý 
Description:
 libsofthsm2 - cryptographic store accessible through a PKCS #11
 libsofthsm2-dev - cryptographic store accessible through a PKCS #11
 softhsm2   - cryptographic store accessible through a PKCS #11
 softhsm2-common - cryptographic store accessible through a PKCS #11
 softhsm2-dbg - Debug symbols for SoftHSM 2
Closes: 828551
Changes:
 softhsm2 (2.2.0~rc1-1) unstable; urgency=medium
 .
   * Imported Upstream version 2.2.0~rc1
+ OpenSSL 1.1.0 support (Closes: #828551)
   * Disable GOST support due OpenSSL 1.1.0
Checksums-Sha1:
 4b66684324a2b9927df3170502fccc6c2ad2514a 2317 softhsm2_2.2.0~rc1-1.dsc
 71e457e1fb35cee89804618f18b94a7483da1bb1 303516 softhsm2_2.2.0~rc1.orig.tar.xz
 d2c612bb048dc12a29e5a2d4d543f72e95106561 7424 
softhsm2_2.2.0~rc1-1.debian.tar.xz
Checksums-Sha256:
 61dea7fa4b0ba7891f2c260b042fb05702b5a96684abd61161bb6b021b3fae57 2317 
softhsm2_2.2.0~rc1-1.dsc
 9f8c2d1cc911fc8f07f89839db1df2f752b9a1b2eff0d6f530de2ad24ebfdca7 303516 
softhsm2_2.2.0~rc1.orig.tar.xz
 e6a24c9a85ad1a6798b1738c8b83f74d983d91d2b5d5cbfaae40d64f5728af67 7424 
softhsm2_2.2.0~rc1-1.debian.tar.xz
Files:
 6965d767cd3da270cdde6a3ae1ddaeb8 2317 admin extra softhsm2_2.2.0~rc1-1.dsc
 f382846c941524dd95f23deef711e9b8 303516 admin extra 
softhsm2_2.2.0~rc1.orig.tar.xz
 7eb382b21e9b07f2c8c2c6fc87e0d9d8 7424 admin extra 
softhsm2_2.2.0~rc1-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQJ8BAEBCgBmBQJYH5/oXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHwysQALGkEgiVvOEU5vYRsVkHnYDh
CW5wEu2Xjop9YTq7Tj4Fd+QkbkokBsc3nQyE2DnlE51NVD4pPWn1qRnsgFmHl1BU
ZscheHTs2Nr1r6gEFFDBhGYk6SYjgQ5hqpyaM83Q7nzkVHdAI6buvdrdtOJspShm
1ubt9r/+KkDBOMeGt6oHTomt64ZudmwDvZrh41dVV2Rm1rfgIMmm0io/x2WCZYHB
y4aYCiiKkl8upjCQdlTJBt/RxEchkPpwFRIr630P2AXkjXWzrl03Yf7xkW/h2iv9
YrChqBjQ2vdl7vtnM0TFgCKxHDPzZ6cVI2C4pz9ykRdCdHnbE4nHdB1l4i2muBIx
Aao80nrxA1dZboZ5EkDjfLfHHvZdSqVCWkmjW+7XwxriN9S5eZ/20SpIKy7k724r
+jZWu86hlSgYin9Kp215DjmcheNY6Dg8PA1nKIMDn9/+l/QOl5UeSrH9A9J4gBVo
9fEjdDX6stKyj3zOkdHvv92YeZU2X7DXspP5gPYdZXJowHDihk43dLA9zDo+uJmx

Bug#828386: marked as done (libcrypt-openssl-pkcs12-perl: FTBFS with openssl 1.1.0)

2016-11-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Nov 2016 21:49:51 +
with message-id 
and subject line Bug#828386: fixed in libcrypt-openssl-pkcs12-perl 0.7-2
has caused the Debian Bug report #828386,
regarding libcrypt-openssl-pkcs12-perl: FTBFS with openssl 1.1.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.)


-- 
828386: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828386
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libcrypt-openssl-pkcs12-perl
Version: 0.7-1
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/libcrypt-openssl-pkcs12-perl_0.7-1_amd64-20160529-1439

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt
--- End Message ---
--- Begin Message ---
Source: libcrypt-openssl-pkcs12-perl
Source-Version: 0.7-2

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

Debian distribution maintenance software
pp.
Christopher Hoskin  (supplier of updated 
libcrypt-openssl-pkcs12-perl 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, 06 Nov 2016 21:00:31 +
Source: libcrypt-openssl-pkcs12-perl
Binary: libcrypt-openssl-pkcs12-perl
Architecture: source
Version: 0.7-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: Christopher Hoskin 
Closes: 828386
Description: 
 libcrypt-openssl-pkcs12-perl - Perl extension to OpenSSL's PKCS12 API
Changes:
 libcrypt-openssl-pkcs12-perl (0.7-2) unstable; urgency=medium
 .
   [ Salvatore Bonaccorso ]
   * debian/control: Use HTTPS transport protocol for Vcs-Git URI
 .
   [ gregor herrmann ]
   * debian/copyright: change Copyright-Format 1.0 URL to HTTPS.
 .
   [ Christopher Hoskin ]
   * Fix "FTBFS with openssl 1.1.0" - patch for new API (Closes: #828386)
   * Enable hardening
   * Update Standards Version from 3.9.6 to 3.9.8 (no change required)
   * Use the simplified form of BTS URL in openssl-1.1.patch
Checksums-Sha1: 
 54291db34bcecc61bfedca7c6e8b32d37e7f2a7f 2412 
libcrypt-openssl-pkcs12-perl_0.7-2.dsc
 b854417d305dd06a0ac4b136370c5a6ac7561760 2660 
libcrypt-openssl-pkcs12-perl_0.7-2.debian.tar.xz
Checksums-Sha256: 
 b748596262b06483d97bc1ac96bbb073087838843e221e124c9d4a9d2adcbb74 2412 
libcrypt-openssl-pkcs12-perl_0.7-2.dsc
 0ea966b44f608e0c9174e6e1f350d82441db03dbc1962988bb03c4a1de83ace2 2660 
libcrypt-openssl-pkcs12-perl_0.7-2.debian.tar.xz
Files: 
 2ebae183c315742ef8109c254919fcae 2412 perl optional 
libcrypt-openssl-pkcs12-perl_0.7-2.dsc
 4a264131dd0a45751dab2014fa2b56cf 2660 perl optional 
libcrypt-openssl-pkcs12-perl_0.7-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJ8BAEBCgBmBQJYH5/jXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC
QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoGlU4P/RmQUMr1ZCXC9mHN5nWKyWqz
Iq48vW8F/uUnHGuzAvaInj26zkZ6aQSfw5iXc20W+R7Btvunbp6yVPgMrHwBOriE
XU9HQikbLYAhqr2Utm+xAR9QAVNjQ3cXP95UBjJ1APtEp5eAZkrbsUOCGeTVygLQ
ZOsM4CDvSPnzMYNIOz84v0Cz9K/5zfaub4Q/0krEdyNQdNlN0P0LuERcWkgrJT4Y
bbTR8cmowT04qNWbW6nGUYYSfdP4ciDQKW7qQbsjQ93CYLlVxv10Jjkr4R2Hz4S8
ODkoGjPyKhKjmlYXFgYAUz66dud9d0JANuSnCxDOkiXttPPfMM8W9OgDqj9JnMfz
384QmvLhza3XqrxHUPlHuc5CevDC2GXVh78RWduXuxqWtxXYJeqaVhaUBCYUdSpa
d6v2YV3v5pBryFu92Yng763neNGMX6zpXrQTMeBmXnnhrbVxqzhrgKMAfNNxOz6d

Processed (with 1 error): your mail

2016-11-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 843250 qtdeclarative-opensource-src
Bug #843250 {Done: Dmitry Shachnev } 
[qtdeclarative-opensource-src] qml-module-qtquick-controls is broken and breaks 
software using it
Bug #843208 {Done: Dmitry Shachnev } 
[qtdeclarative-opensource-src] plasma-workspace: Does not start plasmashell on 
the KDE.
Bug #843332 {Done: Dmitry Shachnev } 
[qtdeclarative-opensource-src] /usr/bin/plasmashell: segmentation fault when 
attempting to start plasmashell after upgrade
Bug #843342 {Done: Dmitry Shachnev } 
[qtdeclarative-opensource-src] plasma-workspace: plasmashell crashes after 
startup
Bug #843363 {Done: Dmitry Shachnev } 
[qtdeclarative-opensource-src] plasmashell: segfault in libQt5Core.so.5.7.1
Ignoring request to reassign bug #843250 to the same package
Ignoring request to reassign bug #843208 to the same package
Ignoring request to reassign bug #843332 to the same package
Ignoring request to reassign bug #843342 to the same package
Ignoring request to reassign bug #843363 to the same package
> forcemerge 843208 843413
Bug #843208 {Done: Dmitry Shachnev } 
[qtdeclarative-opensource-src] plasma-workspace: Does not start plasmashell on 
the KDE.
Bug #843250 {Done: Dmitry Shachnev } 
[qtdeclarative-opensource-src] qml-module-qtquick-controls is broken and breaks 
software using it
Bug #843332 {Done: Dmitry Shachnev } 
[qtdeclarative-opensource-src] /usr/bin/plasmashell: segmentation fault when 
attempting to start plasmashell after upgrade
Bug #843342 {Done: Dmitry Shachnev } 
[qtdeclarative-opensource-src] plasma-workspace: plasmashell crashes after 
startup
Bug #843363 {Done: Dmitry Shachnev } 
[qtdeclarative-opensource-src] plasmashell: segfault in libQt5Core.so.5.7.1
Unable to merge bugs because:
package of #843413 is 'plasma-workspace' not 'qtdeclarative-opensource-src'
Failed to forcibly merge 843208: Did not alter merged bugs.

> thanks
Stopping processing here.

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



Bug#825012: Half-working patch

2016-11-06 Thread Martin Petricek

I needed libalgorithm-permute-perl as dependency of one of my scripts.

The perlapi changed between 5.22 and 5.24, so just recompilation won't 
do the trick.


I've tried to fix it (PUSHBLOCK was replaced by new cx_pushblock, etc 
...), but as it is first times I've done something with the xs / 
perlguts / perl internals, my fix was not perfect.
The code compiles and installs cleanly, some of my scripts using 
Algorithm::Permute run properly, but some of them fail with segfault or 
some "panic: pp_iter, type=0" message.


Well, in worst case anybody can use my patch until someone else fixes 
this properly... or use this patch as base of a proper patch.


Martin Petricek
Author: Martin Petricek 
Date:   Sun Nov 6 22:21:11 2016 +0100

Partial fix for perlapi 5.24

diff --git Permute.xs Permute.xs
index 4b47499..116a92c 100644
--- Permute.xs
+++ Permute.xs
@@ -472,6 +472,8 @@ SV* array_sv;
 struct afp_cache *c;
 I32 hasargs = 0;
 SV** newsp;
+OP *retop = PL_op->op_next;
+I32 old_ss_ix = PL_savestack_ix;
   PPCODE:
 {
 if (!SvROK(callback_sv) || SvTYPE(SvRV(callback_sv)) != SVt_PVCV)
@@ -533,8 +535,8 @@ SV* array_sv;
 SAVETMPS;
 SAVESPTR(PL_op);
 
-PUSHBLOCK(cx, CXt_NULL, SP);  /* make a pseudo block */
-PUSHSUB(cx);
+cx = cx_pushblock(CXt_NULL, gimme, MARK, old_ss_ix);  /* make a pseudo 
block */
+cx_pushsub(cx, callback, retop, hasargs);
 
 old_catch = CATCH_GET;
 CATCH_SET(TRUE);
@@ -543,6 +545,6 @@ SV* array_sv;
 permute_engine(c->array, AvARRAY(c->array), 0, c->len, 
 c->tmparea, CvSTART(callback));
 
-POPBLOCK(cx,PL_curpm);
+cx_popblock(cx);
 CATCH_SET(old_catch);
 }



Bug#828499: marked as done (php7.0: FTBFS with openssl 1.1.0)

2016-11-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Nov 2016 21:28:03 +
with message-id 
and subject line Bug#828499: fixed in php7.0 7.0.12-2
has caused the Debian Bug report #828499,
regarding php7.0: FTBFS with openssl 1.1.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.)


-- 
828499: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828499
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php7.0
Version: 7.0.7-3
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/php7.0_7.0.7-3_amd64-20160529-1506

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt
--- End Message ---
--- Begin Message ---
Source: php7.0
Source-Version: 7.0.12-2

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

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

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

Debian distribution maintenance software
pp.
Ondřej Surý  (supplier of updated php7.0 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 01 Nov 2016 12:55:45 +0100
Source: php7.0
Binary: libapache2-mod-php7.0 libphp7.0-embed php7.0 php7.0-cgi php7.0-cli 
php7.0-dev php7.0-fpm php7.0-phpdbg php7.0-xsl php7.0-odbc php7.0-readline 
php7.0-recode php7.0-sqlite3 php7.0-xml php7.0-zip php7.0-sybase php7.0-gd 
php7.0-gmp php7.0-ldap php7.0-common php7.0-intl php7.0-mysql php7.0-mcrypt 
php7.0-snmp php7.0-curl php7.0-json php7.0-pgsql php7.0-mbstring php7.0-enchant 
php7.0-opcache php7.0-imap php7.0-bcmath php7.0-tidy php7.0-soap php7.0-dba 
php7.0-interbase php7.0-xmlrpc php7.0-pspell php7.0-bz2
Architecture: source
Version: 7.0.12-2
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP Maintainers 
Changed-By: Ondřej Surý 
Description:
 libapache2-mod-php7.0 - server-side, HTML-embedded scripting language (Apache 
2 module)
 libphp7.0-embed - HTML-embedded scripting language (Embedded SAPI library)
 php7.0 - server-side, HTML-embedded scripting language (metapackage)
 php7.0-bcmath - Bcmath module for PHP
 php7.0-bz2 - bzip2 module for PHP
 php7.0-cgi - server-side, HTML-embedded scripting language (CGI binary)
 php7.0-cli - command-line interpreter for the PHP scripting language
 php7.0-common - documentation, examples and common module for PHP
 php7.0-curl - CURL module for PHP
 php7.0-dba - DBA module for PHP
 php7.0-dev - Files for PHP7.0 module development
 php7.0-enchant - Enchant module for PHP
 php7.0-fpm - server-side, HTML-embedded scripting language (FPM-CGI binary)
 php7.0-gd  - GD module for PHP
 php7.0-gmp - GMP module for PHP
 php7.0-imap - IMAP module for PHP
 php7.0-interbase - Interbase module for PHP
 php7.0-intl - Internationalisation module for PHP
 php7.0-json - JSON module for PHP
 php7.0-ldap - LDAP module for PHP
 php7.0-mbstring - MBSTRING module for PHP
 php7.0-mcrypt - libmcrypt module for PHP
 php7.0-mysql - MySQL module for PHP
 php7.0-odbc - ODBC module for PHP
 php7.0-opcache - Zend OpCache module for PHP
 php7.0-pgsql - PostgreSQL module for PHP
 php7.0-phpdbg - server-side, HTML-embedded scripting language (PHPDBG binary)
 php7.0-pspell - pspell module for PHP
 php7.0-readline - readline module for PHP
 php7.0-recode - recode module for PHP
 php7.0-snmp - SNMP module for PHP
 php7.0-soap - SOAP module for PHP
 php7.0-sqlite3 - SQLite3 module for PHP
 php7.0-sybase - Sybase module for PHP
 php7.0-tidy - tidy module for PHP
 php7.0-xml - DOM, SimpleXML, WDDX, XML, and XSL module for PHP
 

Processed (with 1 error): Done

2016-11-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 843250 qtdeclarative-opensource-src 5.7.1~20161021-4
Bug #843250 {Done: Dmitry Shachnev } 
[qtdeclarative-opensource-src] qml-module-qtquick-controls is broken and breaks 
software using it
Bug #843208 {Done: Dmitry Shachnev } 
[qtdeclarative-opensource-src] plasma-workspace: Does not start plasmashell on 
the KDE.
Bug #843332 {Done: Dmitry Shachnev } 
[qtdeclarative-opensource-src] /usr/bin/plasmashell: segmentation fault when 
attempting to start plasmashell after upgrade
Bug #843342 {Done: Dmitry Shachnev } 
[qtdeclarative-opensource-src] plasma-workspace: plasmashell crashes after 
startup
Bug #843363 {Done: Dmitry Shachnev } 
[qtdeclarative-opensource-src] plasmashell: segfault in libQt5Core.so.5.7.1
Ignoring request to reassign bug #843250 to the same package
Ignoring request to reassign bug #843208 to the same package
Ignoring request to reassign bug #843332 to the same package
Ignoring request to reassign bug #843342 to the same package
Ignoring request to reassign bug #843363 to the same package
Bug #843250 {Done: Dmitry Shachnev } 
[qtdeclarative-opensource-src] qml-module-qtquick-controls is broken and breaks 
software using it
Bug #843208 {Done: Dmitry Shachnev } 
[qtdeclarative-opensource-src] plasma-workspace: Does not start plasmashell on 
the KDE.
Bug #843332 {Done: Dmitry Shachnev } 
[qtdeclarative-opensource-src] /usr/bin/plasmashell: segmentation fault when 
attempting to start plasmashell after upgrade
Bug #843342 {Done: Dmitry Shachnev } 
[qtdeclarative-opensource-src] plasma-workspace: plasmashell crashes after 
startup
Bug #843363 {Done: Dmitry Shachnev } 
[qtdeclarative-opensource-src] plasmashell: segfault in libQt5Core.so.5.7.1
There is no source info for the package 'qtdeclarative-opensource-src' at 
version '5.7.1~20161021-4' with architecture ''
Unable to make a source version for version '5.7.1~20161021-4'
Ignoring request to alter found versions of bug #843250 to the same values 
previously set
Ignoring request to alter found versions of bug #843208 to the same values 
previously set
Ignoring request to alter found versions of bug #843332 to the same values 
previously set
Ignoring request to alter found versions of bug #843342 to the same values 
previously set
Ignoring request to alter found versions of bug #843363 to the same values 
previously set
> forcemerge 843208 843413
Bug #843208 {Done: Dmitry Shachnev } 
[qtdeclarative-opensource-src] plasma-workspace: Does not start plasmashell on 
the KDE.
Bug #843250 {Done: Dmitry Shachnev } 
[qtdeclarative-opensource-src] qml-module-qtquick-controls is broken and breaks 
software using it
Bug #843332 {Done: Dmitry Shachnev } 
[qtdeclarative-opensource-src] /usr/bin/plasmashell: segmentation fault when 
attempting to start plasmashell after upgrade
Bug #843342 {Done: Dmitry Shachnev } 
[qtdeclarative-opensource-src] plasma-workspace: plasmashell crashes after 
startup
Bug #843363 {Done: Dmitry Shachnev } 
[qtdeclarative-opensource-src] plasmashell: segfault in libQt5Core.so.5.7.1
Unable to merge bugs because:
package of #843413 is 'plasma-workspace' not 'qtdeclarative-opensource-src'
Failed to forcibly merge 843208: Did not alter merged bugs.

> thanks
Stopping processing here.

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



Bug#828275: marked as done (cyrus-imapd-2.4: FTBFS with openssl 1.1.0)

2016-11-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Nov 2016 21:22:42 +
with message-id 
and subject line Bug#828276: fixed in cyrus-imapd 2.5.10-2
has caused the Debian Bug report #828276,
regarding cyrus-imapd-2.4: FTBFS with openssl 1.1.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.)


-- 
828276: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828276
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cyrus-imapd-2.4
Version: 2.4.18-5
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/cyrus-imapd-2.4_2.4.18-5_amd64-20160529-1412

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt
--- End Message ---
--- Begin Message ---
Source: cyrus-imapd
Source-Version: 2.5.10-2

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

Debian distribution maintenance software
pp.
Ondřej Surý  (supplier of updated cyrus-imapd 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, 06 Nov 2016 21:05:26 +0100
Source: cyrus-imapd
Binary: cyrus-common cyrus-doc cyrus-imapd cyrus-pop3d cyrus-admin cyrus-murder 
cyrus-replication cyrus-nntpd cyrus-caldav cyrus-clients cyrus-dev 
libcyrus-imap-perl
Architecture: source
Version: 2.5.10-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Cyrus Team 

Changed-By: Ondřej Surý 
Description:
 cyrus-admin - Cyrus mail system - administration tools
 cyrus-caldav - Cyrus mail system - CalDAV and CardDAV support
 cyrus-clients - Cyrus mail system - test clients
 cyrus-common - Cyrus mail system - common files
 cyrus-dev  - Cyrus mail system - developer files
 cyrus-doc  - Cyrus mail system - documentation files
 cyrus-imapd - Cyrus mail system - IMAP support
 cyrus-murder - Cyrus mail system - proxies and aggregator
 cyrus-nntpd - Cyrus mail system - NNTP support
 cyrus-pop3d - Cyrus mail system - POP3 support
 cyrus-replication - Cyrus mail system - replication
 libcyrus-imap-perl - Interface to Cyrus imap client imclient library
Closes: 828275 828276
Changes:
 cyrus-imapd (2.5.10-2) unstable; urgency=medium
 .
   * Replace 'struct sched_param' with 'struct caldav_sched_param'
 (Closes: #828276, #828275)
Checksums-Sha1:
 7e6446483ca6515a753a215a84f3df34535c68f3 3225 cyrus-imapd_2.5.10-2.dsc
 876b4a06cc0e2ca6726aa4578a34001b2157625d 86048 
cyrus-imapd_2.5.10-2.debian.tar.xz
Checksums-Sha256:
 c7b747ef5407df5f946211b8e5ff5711ecdfac7b2efa47f4b766be2b64039471 3225 
cyrus-imapd_2.5.10-2.dsc
 83def7090f75b9635004b72275b4d728c200062fa97af2fe25655e77cbdd58d5 86048 
cyrus-imapd_2.5.10-2.debian.tar.xz
Files:
 a7ccf72b666f6225107a9edbda5bcf9c 3225 mail extra cyrus-imapd_2.5.10-2.dsc
 0f9a39aa377d2b691fb30d5213df0ccf 86048 mail extra 
cyrus-imapd_2.5.10-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQJ8BAEBCgBmBQJYH5HvXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHtgAP/1f05X3u4nWNntm9RHq0YDqi
GX8BwGHqOZnGvOhG2mKgOXBFQjosPbeHiVol5xqT+sBtgGflTg+atD7wyl4IpOlB
Tg3I8OHDPjwhVX8RTnmxqwZeojUAPVMimZSf77BbSvBjIM6vuuw/mFknhypLW9QA
cd/GGm8UnX2phMq+d7MBVt+/yQSbTLPwxU13yxwn20dLFGtw7D9cL+mxUPvnsrHc
3zLv3TLg7I/Teyi4lfZEpZezpWPFQlk2Kzs41Fr9siEWvGjVmis45Zh4Ix6xZflR
L9AN1GrJ5VQF+xhR3c42KPO8wyFBnG3UjFC8+9hFa269g5cRWXycfIWX5Eqo26LZ

Bug#828276: marked as done (cyrus-imapd: FTBFS with openssl 1.1.0)

2016-11-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Nov 2016 21:22:42 +
with message-id 
and subject line Bug#828275: fixed in cyrus-imapd 2.5.10-2
has caused the Debian Bug report #828275,
regarding cyrus-imapd: FTBFS with openssl 1.1.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.)


-- 
828275: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828275
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cyrus-imapd
Version: 2.5.8-1
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/cyrus-imapd_2.5.8-1_amd64-20160529-1412

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt
--- End Message ---
--- Begin Message ---
Source: cyrus-imapd
Source-Version: 2.5.10-2

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

Debian distribution maintenance software
pp.
Ondřej Surý  (supplier of updated cyrus-imapd 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, 06 Nov 2016 21:05:26 +0100
Source: cyrus-imapd
Binary: cyrus-common cyrus-doc cyrus-imapd cyrus-pop3d cyrus-admin cyrus-murder 
cyrus-replication cyrus-nntpd cyrus-caldav cyrus-clients cyrus-dev 
libcyrus-imap-perl
Architecture: source
Version: 2.5.10-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Cyrus Team 

Changed-By: Ondřej Surý 
Description:
 cyrus-admin - Cyrus mail system - administration tools
 cyrus-caldav - Cyrus mail system - CalDAV and CardDAV support
 cyrus-clients - Cyrus mail system - test clients
 cyrus-common - Cyrus mail system - common files
 cyrus-dev  - Cyrus mail system - developer files
 cyrus-doc  - Cyrus mail system - documentation files
 cyrus-imapd - Cyrus mail system - IMAP support
 cyrus-murder - Cyrus mail system - proxies and aggregator
 cyrus-nntpd - Cyrus mail system - NNTP support
 cyrus-pop3d - Cyrus mail system - POP3 support
 cyrus-replication - Cyrus mail system - replication
 libcyrus-imap-perl - Interface to Cyrus imap client imclient library
Closes: 828275 828276
Changes:
 cyrus-imapd (2.5.10-2) unstable; urgency=medium
 .
   * Replace 'struct sched_param' with 'struct caldav_sched_param'
 (Closes: #828276, #828275)
Checksums-Sha1:
 7e6446483ca6515a753a215a84f3df34535c68f3 3225 cyrus-imapd_2.5.10-2.dsc
 876b4a06cc0e2ca6726aa4578a34001b2157625d 86048 
cyrus-imapd_2.5.10-2.debian.tar.xz
Checksums-Sha256:
 c7b747ef5407df5f946211b8e5ff5711ecdfac7b2efa47f4b766be2b64039471 3225 
cyrus-imapd_2.5.10-2.dsc
 83def7090f75b9635004b72275b4d728c200062fa97af2fe25655e77cbdd58d5 86048 
cyrus-imapd_2.5.10-2.debian.tar.xz
Files:
 a7ccf72b666f6225107a9edbda5bcf9c 3225 mail extra cyrus-imapd_2.5.10-2.dsc
 0f9a39aa377d2b691fb30d5213df0ccf 86048 mail extra 
cyrus-imapd_2.5.10-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQJ8BAEBCgBmBQJYH5HvXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHtgAP/1f05X3u4nWNntm9RHq0YDqi
GX8BwGHqOZnGvOhG2mKgOXBFQjosPbeHiVol5xqT+sBtgGflTg+atD7wyl4IpOlB
Tg3I8OHDPjwhVX8RTnmxqwZeojUAPVMimZSf77BbSvBjIM6vuuw/mFknhypLW9QA
cd/GGm8UnX2phMq+d7MBVt+/yQSbTLPwxU13yxwn20dLFGtw7D9cL+mxUPvnsrHc
3zLv3TLg7I/Teyi4lfZEpZezpWPFQlk2Kzs41Fr9siEWvGjVmis45Zh4Ix6xZflR
L9AN1GrJ5VQF+xhR3c42KPO8wyFBnG3UjFC8+9hFa269g5cRWXycfIWX5Eqo26LZ

Bug#828276: marked as done (cyrus-imapd: FTBFS with openssl 1.1.0)

2016-11-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Nov 2016 21:22:42 +
with message-id 
and subject line Bug#828276: fixed in cyrus-imapd 2.5.10-2
has caused the Debian Bug report #828276,
regarding cyrus-imapd: FTBFS with openssl 1.1.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.)


-- 
828276: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828276
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cyrus-imapd
Version: 2.5.8-1
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/cyrus-imapd_2.5.8-1_amd64-20160529-1412

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt
--- End Message ---
--- Begin Message ---
Source: cyrus-imapd
Source-Version: 2.5.10-2

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

Debian distribution maintenance software
pp.
Ondřej Surý  (supplier of updated cyrus-imapd 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, 06 Nov 2016 21:05:26 +0100
Source: cyrus-imapd
Binary: cyrus-common cyrus-doc cyrus-imapd cyrus-pop3d cyrus-admin cyrus-murder 
cyrus-replication cyrus-nntpd cyrus-caldav cyrus-clients cyrus-dev 
libcyrus-imap-perl
Architecture: source
Version: 2.5.10-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Cyrus Team 

Changed-By: Ondřej Surý 
Description:
 cyrus-admin - Cyrus mail system - administration tools
 cyrus-caldav - Cyrus mail system - CalDAV and CardDAV support
 cyrus-clients - Cyrus mail system - test clients
 cyrus-common - Cyrus mail system - common files
 cyrus-dev  - Cyrus mail system - developer files
 cyrus-doc  - Cyrus mail system - documentation files
 cyrus-imapd - Cyrus mail system - IMAP support
 cyrus-murder - Cyrus mail system - proxies and aggregator
 cyrus-nntpd - Cyrus mail system - NNTP support
 cyrus-pop3d - Cyrus mail system - POP3 support
 cyrus-replication - Cyrus mail system - replication
 libcyrus-imap-perl - Interface to Cyrus imap client imclient library
Closes: 828275 828276
Changes:
 cyrus-imapd (2.5.10-2) unstable; urgency=medium
 .
   * Replace 'struct sched_param' with 'struct caldav_sched_param'
 (Closes: #828276, #828275)
Checksums-Sha1:
 7e6446483ca6515a753a215a84f3df34535c68f3 3225 cyrus-imapd_2.5.10-2.dsc
 876b4a06cc0e2ca6726aa4578a34001b2157625d 86048 
cyrus-imapd_2.5.10-2.debian.tar.xz
Checksums-Sha256:
 c7b747ef5407df5f946211b8e5ff5711ecdfac7b2efa47f4b766be2b64039471 3225 
cyrus-imapd_2.5.10-2.dsc
 83def7090f75b9635004b72275b4d728c200062fa97af2fe25655e77cbdd58d5 86048 
cyrus-imapd_2.5.10-2.debian.tar.xz
Files:
 a7ccf72b666f6225107a9edbda5bcf9c 3225 mail extra cyrus-imapd_2.5.10-2.dsc
 0f9a39aa377d2b691fb30d5213df0ccf 86048 mail extra 
cyrus-imapd_2.5.10-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQJ8BAEBCgBmBQJYH5HvXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHtgAP/1f05X3u4nWNntm9RHq0YDqi
GX8BwGHqOZnGvOhG2mKgOXBFQjosPbeHiVol5xqT+sBtgGflTg+atD7wyl4IpOlB
Tg3I8OHDPjwhVX8RTnmxqwZeojUAPVMimZSf77BbSvBjIM6vuuw/mFknhypLW9QA
cd/GGm8UnX2phMq+d7MBVt+/yQSbTLPwxU13yxwn20dLFGtw7D9cL+mxUPvnsrHc
3zLv3TLg7I/Teyi4lfZEpZezpWPFQlk2Kzs41Fr9siEWvGjVmis45Zh4Ix6xZflR
L9AN1GrJ5VQF+xhR3c42KPO8wyFBnG3UjFC8+9hFa269g5cRWXycfIWX5Eqo26LZ

Bug#828275: marked as done (cyrus-imapd-2.4: FTBFS with openssl 1.1.0)

2016-11-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Nov 2016 21:22:42 +
with message-id 
and subject line Bug#828275: fixed in cyrus-imapd 2.5.10-2
has caused the Debian Bug report #828275,
regarding cyrus-imapd-2.4: FTBFS with openssl 1.1.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.)


-- 
828275: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828275
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cyrus-imapd-2.4
Version: 2.4.18-5
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/cyrus-imapd-2.4_2.4.18-5_amd64-20160529-1412

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt
--- End Message ---
--- Begin Message ---
Source: cyrus-imapd
Source-Version: 2.5.10-2

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

Debian distribution maintenance software
pp.
Ondřej Surý  (supplier of updated cyrus-imapd 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, 06 Nov 2016 21:05:26 +0100
Source: cyrus-imapd
Binary: cyrus-common cyrus-doc cyrus-imapd cyrus-pop3d cyrus-admin cyrus-murder 
cyrus-replication cyrus-nntpd cyrus-caldav cyrus-clients cyrus-dev 
libcyrus-imap-perl
Architecture: source
Version: 2.5.10-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Cyrus Team 

Changed-By: Ondřej Surý 
Description:
 cyrus-admin - Cyrus mail system - administration tools
 cyrus-caldav - Cyrus mail system - CalDAV and CardDAV support
 cyrus-clients - Cyrus mail system - test clients
 cyrus-common - Cyrus mail system - common files
 cyrus-dev  - Cyrus mail system - developer files
 cyrus-doc  - Cyrus mail system - documentation files
 cyrus-imapd - Cyrus mail system - IMAP support
 cyrus-murder - Cyrus mail system - proxies and aggregator
 cyrus-nntpd - Cyrus mail system - NNTP support
 cyrus-pop3d - Cyrus mail system - POP3 support
 cyrus-replication - Cyrus mail system - replication
 libcyrus-imap-perl - Interface to Cyrus imap client imclient library
Closes: 828275 828276
Changes:
 cyrus-imapd (2.5.10-2) unstable; urgency=medium
 .
   * Replace 'struct sched_param' with 'struct caldav_sched_param'
 (Closes: #828276, #828275)
Checksums-Sha1:
 7e6446483ca6515a753a215a84f3df34535c68f3 3225 cyrus-imapd_2.5.10-2.dsc
 876b4a06cc0e2ca6726aa4578a34001b2157625d 86048 
cyrus-imapd_2.5.10-2.debian.tar.xz
Checksums-Sha256:
 c7b747ef5407df5f946211b8e5ff5711ecdfac7b2efa47f4b766be2b64039471 3225 
cyrus-imapd_2.5.10-2.dsc
 83def7090f75b9635004b72275b4d728c200062fa97af2fe25655e77cbdd58d5 86048 
cyrus-imapd_2.5.10-2.debian.tar.xz
Files:
 a7ccf72b666f6225107a9edbda5bcf9c 3225 mail extra cyrus-imapd_2.5.10-2.dsc
 0f9a39aa377d2b691fb30d5213df0ccf 86048 mail extra 
cyrus-imapd_2.5.10-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQJ8BAEBCgBmBQJYH5HvXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHtgAP/1f05X3u4nWNntm9RHq0YDqi
GX8BwGHqOZnGvOhG2mKgOXBFQjosPbeHiVol5xqT+sBtgGflTg+atD7wyl4IpOlB
Tg3I8OHDPjwhVX8RTnmxqwZeojUAPVMimZSf77BbSvBjIM6vuuw/mFknhypLW9QA
cd/GGm8UnX2phMq+d7MBVt+/yQSbTLPwxU13yxwn20dLFGtw7D9cL+mxUPvnsrHc
3zLv3TLg7I/Teyi4lfZEpZezpWPFQlk2Kzs41Fr9siEWvGjVmis45Zh4Ix6xZflR
L9AN1GrJ5VQF+xhR3c42KPO8wyFBnG3UjFC8+9hFa269g5cRWXycfIWX5Eqo26LZ

Bug#828252: marked as done (botan1.10: FTBFS with openssl 1.1.0)

2016-11-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Nov 2016 21:20:25 +
with message-id 
and subject line Bug#828252: fixed in botan1.10 1.10.13-1
has caused the Debian Bug report #828252,
regarding botan1.10: FTBFS with openssl 1.1.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.)


-- 
828252: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828252
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: botan1.10
Version: 1.10.12-1.1
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/botan1.10_1.10.12-1.1_amd64-20160529-1408

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt
--- End Message ---
--- Begin Message ---
Source: botan1.10
Source-Version: 1.10.13-1

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

Debian distribution maintenance software
pp.
Ondřej Surý  (supplier of updated botan1.10 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, 06 Nov 2016 21:00:24 +0100
Source: botan1.10
Binary: botan1.10-dbg libbotan-1.10-1 libbotan1.10-dev
Architecture: source
Version: 1.10.13-1
Distribution: unstable
Urgency: medium
Maintainer: Ondřej Surý 
Changed-By: Ondřej Surý 
Description:
 botan1.10-dbg - multiplatform crypto library (debug)
 libbotan-1.10-1 - multiplatform crypto library
 libbotan1.10-dev - multiplatform crypto library (development)
Closes: 828252
Changes:
 botan1.10 (1.10.13-1) unstable; urgency=medium
 .
   * Imported Upstream version 1.10.13
   * Disable OpenSSL module to mitigate OpenSSL 1.1.0 transition
 (Closes: #828252)
Checksums-Sha1:
 bfb795bc077f27cf6dc59270a96d70de4e784bb4 2155 botan1.10_1.10.13-1.dsc
 e6771fb063a286c5dcbf6b3f040f4f6be19d00bd 2710181 botan1.10_1.10.13.orig.tar.gz
 12960295b64be50509ef21d894a5332d401e01f6 40304 
botan1.10_1.10.13-1.debian.tar.xz
Checksums-Sha256:
 65a323a66527c8dbf8c70abab9aa6223bc8fea7fee7e35bbe741f80308712e49 2155 
botan1.10_1.10.13-1.dsc
 23ec973d4b4a4fe04f490d409e08ac5638afe3aa09acd7f520daaff38ba19b90 2710181 
botan1.10_1.10.13.orig.tar.gz
 c7f4a919fdb709f5f43e85d7537ff616c125b51076574cd223b45d00b858acec 40304 
botan1.10_1.10.13-1.debian.tar.xz
Files:
 9d115984489e137bc2e67c8efd9f3d1e 2155 libs optional botan1.10_1.10.13-1.dsc
 dd961df109f3b0cc3306f56218fdc700 2710181 libs optional 
botan1.10_1.10.13.orig.tar.gz
 70b288e6fec1d7bf6368dbcafeacb3b0 40304 libs optional 
botan1.10_1.10.13-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQJ8BAEBCgBmBQJYH415XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHjF0P/04byvSHIjGsJ6rTV23aJiyj
6Gmvsk2IulctJNM6MhgoCDVrNDEUey3Cem9xHL7v86qGzH8M0fzmKFgl6jBR+nAa
Z611unXrxIpW8smRSIGhasroawCZ4n8pHO5kjr4/PfudDFT3vWECg3Tqb8OwGoWy
Cy9A/5o4T7lZr2/1WT7CaAnnMC0fbmsApzSaY1EsV9Mgn4n3Zfecd/cKaOG5tn4z
5Yfn3Fdm9tG+nMopcRoH+lllg1qG3o0j8/j80XFC16DRSbAL0L89gQljf3mjfPAA
bqZO3DhIcePtghdfTq4DDHJ+eQ7wVbO3RfjL8opFcoWKiHd4yW/nobcqpQfrqkBr
HUADeRvVsHzb5UpRmLFn1g5p/iGBR9NXUl/aDdvr2wv3UfIZ14CRS5oUlXRa9LPk
KhPgE22gut0ls8Awaao9dLm2pF47yilyW9Zobek9ezc7be3fI/v5KBLnoRXSg56m
TYFsLvlEpgEFG78WwKKYJ30MDVlreu2n5kFKaphnQeISteMREOogQeI7jHNh3+t9
aUrwBWrG3gRePgqDfwOjyBj2BwdHBdS7SppCWOmMhB3vrssQE5IVBsBHuPqzGUM4
lEF8hzkTDBK/GaTRTcM4pz55H/QzQz+LLYfhHEG+mJwiZ6y8rUWZfGHobDiuDpgg
YVOZgQKJc0LTVQ8mPgRc
=2B0M
-END PGP SIGNATURE End Message ---


Processed: bug 809252 is forwarded to https://github.com/node-js-libs/cli/issues/81

2016-11-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> forwarded 809252 https://github.com/node-js-libs/cli/issues/81
Bug #809252 [node-cli] node-cli: insecure use of temporary files
Set Bug forwarded-to-address to 'https://github.com/node-js-libs/cli/issues/81'.
> thanks
Stopping processing here.

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



Bug#837485: [pkg-golang-devel] Bug#837485: Bug#837485: Bug#837485: golang-1.6: FTBFS with bindnow and PIE enabled

2016-11-06 Thread Michael Hudson-Doyle
On 6 November 2016 at 05:00, Niels Thykier  wrote:

> Tianon Gravi:
> > On 31 October 2016 at 17:50, Tianon Gravi  wrote:
> >> Checking reverse dependencies...
> >> # Broken Build-Depends:
> >> golang-github-docker-go: golang-1.6-go
> >>  golang-1.6-src
> >>
> >> Dependency problem found.
> >
> > After that last golang-github-docker-go upload, we're in better shape
> now:
> >
> > $ ssh mirror.ftp-master.debian.org dak rm -Rn golang-1.6
> > [...]
> >
> > Checking reverse dependencies...
> > No dependency problem found.
> >
> >
> > ♥,
> > - Tianon
> >   4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4
> >
>
> Cool! :)
>
> Should I file a bug against ftp.d.o, asking them to remove golang-1.6
> from unstable? :)
>

Somehow I thought Tianon had already done that, but if not, sure!

Cheers,
mwh


Bug#828386: Pending fixes for bugs in the libcrypt-openssl-pkcs12-perl package

2016-11-06 Thread pkg-perl-maintainers
tag 828386 + pending
thanks

Some bugs in the libcrypt-openssl-pkcs12-perl package are closed in
revision 74352d867c315dcf5c45157049fcb6554263d97e in branch 'master'
by Christopher Hoskin

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libcrypt-openssl-pkcs12-perl.git/commit/?id=74352d8

Commit message:

Fix "FTBFS with openssl 1.1.0" - patch for new API (Closes: #828386)



Processed: Pending fixes for bugs in the libcrypt-openssl-pkcs12-perl package

2016-11-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tag 828386 + pending
Bug #828386 [src:libcrypt-openssl-pkcs12-perl] libcrypt-openssl-pkcs12-perl: 
FTBFS with openssl 1.1.0
Added tag(s) pending.
> thanks
Stopping processing here.

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



Bug#843040: c-blosc: diff for NMU version 1.11.1+ds1-2.1

2016-11-06 Thread Daniel Stender
Hi Gilles,

that's o.k. with me. Thx for taking care of this.

Best,
DS

On 06.11.2016 12:10, Gilles Filippini wrote:
> Control: tags 8430040 + patch
> Control: tags 8430040 + pending
> 
> Dear maintainer,
> 
> I've prepared an NMU for c-blosc (versioned as 1.11.1+ds1-2.1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer.
> 
> Regards,
> 
> _g.

-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
LPIC-1 (LPI000329859 64mz6f7kt4)
http://www.danielstender.com/



Bug#809252: Bug solved since v1.0.0

2016-11-06 Thread Jens Krefeldt
Hi,

pls note that this bug is solved since v1.0.0, see 
https://github.com/node-js-libs/cli/issues/81 
 . Pls could you update this? It 
is still marked at https://nodesecurity.io/advisories/cli_arbitrary-file-write 
 and blames all 
modules referencing it even in version 1.0.0, e.g 
https://david-dm.org/deadratfink/jy-transform/development 
.

Thx and best,
Jens

Processed: Re: Bug#843379: blender: FTBFS (internal compiler error)

2016-11-06 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 important
Bug #843379 [gcc-6] blender: FTBFS (internal compiler error)
Severity set to 'important' from 'serious'

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



Bug#843379: blender: FTBFS (internal compiler error)

2016-11-06 Thread Matthias Klose
Control: severity -1 important

For now you can work around it by building with -O1. I also filed a bug for
using non-default compiler flags.



Processed: user debian...@lists.debian.org, usertagging 843247, usertagging 841615, found 841615 in 0.9.5+dfsg-4

2016-11-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 843247 piuparts
There were no usertags set.
Usertags are now: piuparts.
> usertags 841615 piuparts
Usertags were: qa-ftbfs-20161021 qa-ftbfs.
Usertags are now: qa-ftbfs-20161021 piuparts qa-ftbfs.
> found 841615 0.9.5+dfsg-4
Bug #841615 [libmono-cecil-cil] libmono-cecil-cil is not installable in unstable
Marked as found in versions cecil/0.9.5+dfsg-4.
> thanks
Stopping processing here.

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



Bug#843467: libxbase64-1: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

2016-11-06 Thread Andreas Beckmann
Package: libxbase64-1
Version: 3.1.2-9
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  jessie -> stretch

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/ch-docs.html#s-copyrightfile

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


>From the attached log (usually somewhere in the middle...):

2m18.1s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/libxbase64-1/changelog.Debian.gz (libxbase64-1:i386) != 
/usr/share/doc/libxbase64-doc/changelog.Debian.gz (libxbase64-doc)
/usr/share/doc/libxbase64-1 -> libxbase64-doc
  /usr/share/doc/libxbase64-1/changelog.gz (libxbase64-1:i386) != 
/usr/share/doc/libxbase64-doc/changelog.gz (libxbase64-doc)
/usr/share/doc/libxbase64-1 -> libxbase64-doc
  /usr/share/doc/libxbase64-1/copyright (libxbase64-1:i386) != 
/usr/share/doc/libxbase64-doc/copyright (libxbase64-doc)
/usr/share/doc/libxbase64-1 -> libxbase64-doc


cheers,

Andreas


libxbase64-1_3.1.2-9.log.gz
Description: application/gzip


Bug#828252: qtcreator is marked for autoremoval from testing

2016-11-06 Thread Ondřej Surý
In the end it was very easy (hopefully) - the OpenSSL module is optional
and hopefully this won't break anything :). Ccing other botan1.10 users.

Please test with botan1.10 - 1.10.13-1 that just got uploaded to
unstable.

Cheers,
-- 
Ondřej Surý 
Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server
Knot Resolver (https://www.knot-resolver.cz/) – secure, privacy-aware,
fast DNS(SEC) resolver
Vše pro chleba (https://vseprochleba.cz) – Mouky ze mlýna a potřeby pro
pečení chleba všeho druhu

On Thu, Oct 27, 2016, at 21:20, Adam Majer wrote:
> On 27/10/16 09:59 AM, Ondřej Surý wrote:
> > I can probably generate two sets of packages with versioned symbols
> > if I have some help with that.
> >
> > Cheers,
> >
> 
> Yes, but this will not help and I'm not sure it is required since 
> OpenSSL is versioned already.
> 
> The problem is that Qt5 is using dlopen for OpenSSL. Versioned symbols 
> are not used with dlopen as is so we are SOL. Either Qt5 needs to be 
> linked directly against OpenSSL, or Qt5 needs to use symbols from old 
> OpenSSL library.
> 
> And now I'm looking at Qt source, and it looks like for Qt5 it is 
> possible to specify SHLIB version number for OpenSSL. see
> 
> qtbase/src/network/ssl/qsslsocket_openssl_symbols.cpp line 653
> 
> which means it *may be* possible to have multiple OpenSSL versions 
> installed and have Qt use only the old version. But this needs to be 
> tested with some test application to make sure correct functions are 
> actually called.
> 
> SHLIB_VERSION_NUMBER = 1.0.2
> 
> during compilation of Qt maybe all that is required to keep Qt crypto 
> support working in a mixed environment.
> 
> - Adam



Bug#843465: cloud-init: FTBFS (dictionary key repeated with different values)

2016-11-06 Thread Santiago Vila
Package: src:cloud-init
Version: 0.7.8-1
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python3,systemd --buildsystem pybuild
   dh_testdir -i -O--buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:184: python3.5 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:184: /usr/bin/python3 setup.py build 
running build
running build_py
creating /<>/.pybuild/pythonX.Y_3.5/build/cloudinit
copying cloudinit/ssh_util.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/cloudinit

[... snipped ...]

copying cloudinit/distros/parsers/hostname.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/cloudinit/distros/parsers
copying cloudinit/distros/parsers/resolv_conf.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/cloudinit/distros/parsers
copying cloudinit/distros/parsers/hosts.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/cloudinit/distros/parsers
copying cloudinit/distros/parsers/__init__.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/cloudinit/distros/parsers
copying cloudinit/distros/parsers/sys_conf.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/cloudinit/distros/parsers
creating /<>/.pybuild/pythonX.Y_3.5/build/cloudinit/sources/helpers
copying cloudinit/sources/helpers/azure.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/cloudinit/sources/helpers
copying cloudinit/sources/helpers/__init__.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/cloudinit/sources/helpers
copying cloudinit/sources/helpers/openstack.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/cloudinit/sources/helpers
creating 
/<>/.pybuild/pythonX.Y_3.5/build/cloudinit/sources/helpers/vmware
copying cloudinit/sources/helpers/vmware/__init__.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/cloudinit/sources/helpers/vmware
creating 
/<>/.pybuild/pythonX.Y_3.5/build/cloudinit/sources/helpers/vmware/imc
copying cloudinit/sources/helpers/vmware/imc/ipv4_mode.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/cloudinit/sources/helpers/vmware/imc
copying cloudinit/sources/helpers/vmware/imc/nic.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/cloudinit/sources/helpers/vmware/imc
copying cloudinit/sources/helpers/vmware/imc/config_namespace.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/cloudinit/sources/helpers/vmware/imc
copying cloudinit/sources/helpers/vmware/imc/config_nic.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/cloudinit/sources/helpers/vmware/imc
copying cloudinit/sources/helpers/vmware/imc/guestcust_state.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/cloudinit/sources/helpers/vmware/imc
copying cloudinit/sources/helpers/vmware/imc/config_source.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/cloudinit/sources/helpers/vmware/imc
copying cloudinit/sources/helpers/vmware/imc/__init__.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/cloudinit/sources/helpers/vmware/imc
copying cloudinit/sources/helpers/vmware/imc/guestcust_util.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/cloudinit/sources/helpers/vmware/imc
copying cloudinit/sources/helpers/vmware/imc/guestcust_error.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/cloudinit/sources/helpers/vmware/imc
copying cloudinit/sources/helpers/vmware/imc/guestcust_event.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/cloudinit/sources/helpers/vmware/imc
copying cloudinit/sources/helpers/vmware/imc/config.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/cloudinit/sources/helpers/vmware/imc
copying cloudinit/sources/helpers/vmware/imc/config_file.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/cloudinit/sources/helpers/vmware/imc
copying cloudinit/sources/helpers/vmware/imc/nic_base.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/cloudinit/sources/helpers/vmware/imc
copying cloudinit/sources/helpers/vmware/imc/boot_proto.py -> 
/<>/.pybuild/pythonX.Y_3.5/build/cloudinit/sources/helpers/vmware/imc
running build_scripts
creating build
creating build/scripts-3.5
copying tools/cloud-init-per -> build/scripts-3.5
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
make PYVER=python3 check
make[2]: Entering directory '/<>'
Running:  pep8 cloudinit/ tests/ tools/
Running:  python3 -m pyflakes cloudinit/ tests/ tools/
tests/unittests/test_datasource/test_openstack.py:70: dictionary key 
'openstack/latest/meta_data.json' repeated with different values
tests/unittests/test_datasource/test_openstack.py:74: dictionary key 
'openstack/latest/meta_data.json' repeated with different values
Makefile:45: recipe for target 'pyflakes3' failed
make[2]: *** [pyflakes3] Error 1
make[2]: Leaving directory '/<>'
debian/rules:13: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 2
make[1]: Leaving directory '/<>'
debian/rules:6: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error 

Bug#843464: jmol: FTBFS (RawPacketWriter() has private access in RawPacketWriter)

2016-11-06 Thread Santiago Vila
Package: src:jmol
Version: 12.2.32+dfsg2-1
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with=javahelper --buildsystem=ant --parallel
dh: Compatibility levels before 9 are deprecated (level 8 in use)
   dh_testdir -i -O--buildsystem=ant -O--parallel
   dh_update_autotools_config -i -O--buildsystem=ant -O--parallel
   dh_auto_configure -i -O--buildsystem=ant -O--parallel
dh_auto_configure: Compatibility levels before 9 are deprecated (level 8 in use)
   jh_linkjars -i -O--buildsystem=ant -O--parallel
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>/jmol-12.2.32+dfsg2'
(cd jars && for i in /usr/share/java/*.jar /usr/share/icedtea-web/*.jar; \
 do ln -s $i; done)
dh_auto_build -- -Dvecmath.jar=vecmath.jar -Ditext.jar=itext1.jar \

[... snipped ...]

[javac]^
[javac]   (use of '_' as an identifier might not be supported in releases 
after Java SE 8)
[javac] /<>/jmol-12.2.32+dfsg2/src/org/jmol/i18n/GT.java:146: 
warning: '_' used as an identifier
[javac]   new Language("el",GT._("Greek"),
"", false),
[javac]^
[javac]   (use of '_' as an identifier might not be supported in releases 
after Java SE 8)
[javac] /<>/jmol-12.2.32+dfsg2/src/org/jmol/i18n/GT.java:147: 
warning: '_' used as an identifier
[javac]   new Language("en_AU", GT._("Australian English"),   
"Australian English",   false),
[javac]^
[javac]   (use of '_' as an identifier might not be supported in releases 
after Java SE 8)
[javac] /<>/jmol-12.2.32+dfsg2/src/org/jmol/i18n/GT.java:148: 
warning: '_' used as an identifier
[javac]   new Language("en_GB", GT._("British English"),  "British 
English",  true),
[javac]^
[javac]   (use of '_' as an identifier might not be supported in releases 
after Java SE 8)
[javac] 
/<>/jmol-12.2.32+dfsg2/src/org/openscience/jmol/app/jmolpanel/JsonNioService.java:243:
 error: RawPacketWriter() has private access in RawPacketWriter
[javac] inSocket.setPacketWriter(new RawPacketWriter());
[javac]  ^
[javac] 
/<>/jmol-12.2.32+dfsg2/src/org/openscience/jmol/app/jmolpanel/JsonNioService.java:244:
 error:  is not 
abstract and does not override abstract method packetSent(NIOSocket,Object) in 
SocketObserver
[javac] inSocket.listen(new SocketObserver() {
[javac]  ^
[javac] 
/<>/jmol-12.2.32+dfsg2/src/org/openscience/jmol/app/jmolpanel/JsonNioService.java:265:
 error: RawPacketWriter() has private access in RawPacketWriter
[javac] outSocket.setPacketWriter(new RawPacketWriter());
[javac]   ^
[javac] 
/<>/jmol-12.2.32+dfsg2/src/org/openscience/jmol/app/jmolpanel/JsonNioService.java:266:
 error:  is not 
abstract and does not override abstract method packetSent(NIOSocket,Object) in 
SocketObserver
[javac] outSocket.listen(new SocketObserver() {
[javac]   ^
[javac] 
/<>/jmol-12.2.32+dfsg2/src/org/openscience/jmol/app/jmolpanel/JsonNioService.java:350:
 error: RawPacketWriter() has private access in RawPacketWriter
[javac]   nioSocket.setPacketWriter(new RawPacketWriter());
[javac] ^
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
[javac] 5 errors
[javac] 100 warnings

BUILD FAILED
/<>/jmol-12.2.32+dfsg2/build.xml:198: Compile failed; see the 
compiler error output for details.

Total time: 20 seconds
dh_auto_build: ant -Duser.name debian -Dvecmath.jar=vecmath.jar 
-Ditext.jar=itext1.jar -Dcommons-cli.jar=commons-cli.jar jar applet-jar doc 
returned exit code 1
debian/rules:12: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>/jmol-12.2.32+dfsg2'
debian/rules:9: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The relevant part of the build log is included above.

There are full build logs here:

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

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is 

Bug#843463: opendkim: fails to install: /lib/opendkim/opendkim.service.generate: systemctl: not found

2016-11-06 Thread Andreas Beckmann
Package: opendkim
Version: 2.11.0~alpha-7
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Selecting previously unselected package opendkim.
  (Reading database ... 
(Reading database ... 4633 files and directories currently installed.)
  Preparing to unpack .../opendkim_2.11.0~alpha-7_amd64.deb ...
  Unpacking opendkim (2.11.0~alpha-7) ...
  Setting up opendkim (2.11.0~alpha-7) ...
  /lib/opendkim/opendkim.service.generate: 83: 
/lib/opendkim/opendkim.service.generate: systemctl: not found
  /lib/opendkim/opendkim.service.generate: 84: 
/lib/opendkim/opendkim.service.generate: systemctl: not found
  dpkg: error processing package opendkim (--configure):
   subprocess installed post-installation script returned error exit status 127
  Errors were encountered while processing:
   opendkim


cheers,

Andreas


opendkim_2.11.0~alpha-7.log.gz
Description: application/gzip


Bug#843040: c-blosc: diff for NMU version 1.11.1+ds1-2.1

2016-11-06 Thread Gilles Filippini
Control: tags 8430040 + patch
Control: tags 8430040 + pending

Dear maintainer,

I've prepared an NMU for c-blosc (versioned as 1.11.1+ds1-2.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards,

_g.

diff -Nru c-blosc-1.11.1+ds1/debian/changelog
c-blosc-1.11.1+ds1/debian/changelog
--- c-blosc-1.11.1+ds1/debian/changelog 2016-09-04 13:08:55.0 +0200
+++ c-blosc-1.11.1+ds1/debian/changelog 2016-11-04 11:19:43.0 +0100
@@ -1,3 +1,11 @@
+c-blosc (1.11.1+ds1-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * New patch bigendian.patch: fix endianness issue in the bitshuffle
+filter (closes: #8430040)
+
+ -- Gilles Filippini   Fri, 04 Nov 2016 11:19:43 +0100
+
 c-blosc (1.11.1+ds1-2) unstable; urgency=medium
* add preserve-cflags-from-environment.patch.
diff -Nru c-blosc-1.11.1+ds1/debian/patches/bigendian.patch
c-blosc-1.11.1+ds1/debian/patches/bigendian.patch
--- c-blosc-1.11.1+ds1/debian/patches/bigendian.patch   1970-01-01
01:00:00.0 +0100
+++ c-blosc-1.11.1+ds1/debian/patches/bigendian.patch   2016-11-04
02:57:31.0 +0100
@@ -0,0 +1,38 @@
+Index: c-blosc-1.11.1+ds1/blosc/bitshuffle-generic.h
+===
+--- c-blosc-1.11.1+ds1.orig/blosc/bitshuffle-generic.h
 c-blosc-1.11.1+ds1/blosc/bitshuffle-generic.h
+@@ -39,7 +39,14 @@ extern "C" {
+ + /* Transpose 8x8 bit array packed into a single quadword *x*.
+  * *t* is workspace. */
++#ifdef BSHUF_BIGENDIAN
++# include 
++# define BSWAP_64(x) x = bswap_64(x)
++#else
++# define BSWAP_64(x)
++#endif
+ #define TRANS_BIT_8X8(x, t) {
 \
++BSWAP_64(x)
 \
+ t = (x ^ (x >> 7)) & 0x00AA00AA00AA00AALL;
 \
+ x = x ^ t ^ (t << 7);
 \
+ t = (x ^ (x >> 14)) & 0xLL;
 \
+Index: c-blosc-1.11.1+ds1/blosc/CMakeLists.txt
+===
+--- c-blosc-1.11.1+ds1.orig/blosc/CMakeLists.txt
 c-blosc-1.11.1+ds1/blosc/CMakeLists.txt
+@@ -161,6 +161,14 @@ if(COMPILER_SUPPORT_AVX2)
+ APPEND PROPERTY COMPILE_DEFINITIONS SHUFFLE_AVX2_ENABLED)
+ endif(COMPILER_SUPPORT_AVX2)
+ ++INCLUDE(TestBigEndian)
++TEST_BIG_ENDIAN(BIGENDIAN)
++IF(BIGENDIAN)
++set_property(
++SOURCE bitshuffle-generic.c
++APPEND PROPERTY COMPILE_DEFINITIONS BSHUF_BIGENDIAN)
++ENDIF(BIGENDIAN)
++
+ # When the option has been selected to compile the test suite,
+ # compile an additional version of blosc_shared which exports
+ # some normally-hidden symbols (to facilitate unit testing).
diff -Nru c-blosc-1.11.1+ds1/debian/patches/series
c-blosc-1.11.1+ds1/debian/patches/series
--- c-blosc-1.11.1+ds1/debian/patches/series2016-09-04
12:56:02.0 +0200
+++ c-blosc-1.11.1+ds1/debian/patches/series2016-11-04
02:29:44.0 +0100
@@ -1 +1,2 @@
 preserve-cflags-from-environment.patch
+bigendian.patch



signature.asc
Description: OpenPGP digital signature


Processed: bug 843324 is forwarded to http://bugs.ghostscript.com/show_bug.cgi?id=695862

2016-11-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> forwarded 843324 http://bugs.ghostscript.com/show_bug.cgi?id=695862
Bug #843324 [ghostscript] ghostscript crashes on some machines, much of the time
Set Bug forwarded-to-address to 
'http://bugs.ghostscript.com/show_bug.cgi?id=695862'.
> thanks
Stopping processing here.

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



Processed: found 843324 in 9.06~dfsg-2

2016-11-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> # for the version graph in BTS
> found 843324 9.06~dfsg-2
Bug #843324 [ghostscript] ghostscript crashes on some machines, much of the time
Marked as found in versions ghostscript/9.06~dfsg-2.
> thanks
Stopping processing here.

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



Bug#843433: Wrong paths for /bin/mount when compiled on merged-usr system

2016-11-06 Thread Felipe Sateler
On 6 November 2016 at 14:07, Michael Biebl  wrote:
> Source: systemd
> Version: 232-2
> Severity: serious
> User: m...@linux.it
> Usertags: usrmerge
>
> As reported on IRC
>
>  mbiebl:
> https://buildd.debian.org/status/fetch.php?pkg=systemd=sparc64=232-2=1478397115
> has split-usr enabled, but because it finds /usr/bin/mount at configure
> time, it uses that rather than /bin/mount
>  (chroots are created with debootstrap from unstable, which does
> usr-merge since 21st Oct)
>  then, on systems without usr-merge, boom
>
>
> We should probably update
> debian/patches/debian/Use-different-default-paths-for-various-binaries.patch
> and use a different search path which prefers /bin and /sbin, like
>
> -AC_PATH_PROG([MOUNT_PATH], [mount], [/usr/bin/mount], 
> [$PATH:/usr/sbin:/sbin])
> -AC_PATH_PROG([UMOUNT_PATH], [umount], [/usr/bin/umount], 
> [$PATH:/usr/sbin:/sbin])
> +AC_PATH_PROG([MOUNT_PATH], [mount], [/usr/bin/mount], [/sbin:/bin:$PATH])
> +AC_PATH_PROG([UMOUNT_PATH], [umount], [/usr/bin/umount], [/sbin:/bin:$PATH])
>
>
> (we should do that for all occurences of AC_PATH_PROG)
>
>
> Thoughts? Does anyone have a nicer solution?

The following patch appears to fix the issue:

diff --git a/debian/rules b/debian/rules
index 306c5f9..62ad96e 100755
--- a/debian/rules
+++ b/debian/rules
@@ -15,6 +15,18 @@ else
 SUPPORT_URL = https://www.debian.org/support
 endif

+SPLIT_USR_PATHS = \
+ QUOTAON=/sbin/quotaon \
+ QUOTACHECK=/sbin/quotacheck \
+ SETCAP=/sbin/setcap \
+ KILL=/bin/kill \
+ KMOD=/bin/kmod \
+ KEXEC=/sbin/kexec \
+ SULOGIN=/sbin/sulogin \
+ MOUNT_PATH=/bin/mount \
+ UMOUNT_PATH=/bin/umount \
+
+
 # Drop these after stretch
 BREAKS_RCS_COMPAT = \
  ifupdown (<< 0.8), \
@@ -86,6 +98,7 @@ export DEB_BUILD_PROFILES += noudeb
 endif

 CONFFLAGS = \
+ $(SPLIT_USR_PATHS) \
  --with-rootprefix= \
  --with-rootlibdir=/lib/$(DEB_HOST_MULTIARCH) \
  --with-zshcompletiondir=/usr/share/zsh/vendor-completions \

%  egrep '^(QUOTAON|QUOTACHECK|KMOD|KEXEC|U?MOUNT_PATH|SETCAP|SULOGIN|KILL)'
build-deb/Makefile
KEXEC = /sbin/kexec
KILL = /bin/kill
KILL_USER_PROCESSES = no
KMOD = /bin/kmod
KMOD_CFLAGS =
KMOD_LIBS = -lkmod
MOUNT_PATH = /bin/mount
QUOTACHECK = /sbin/quotacheck
QUOTAON = /sbin/quotaon
SETCAP = /sbin/setcap
SULOGIN = /sbin/sulogin
UMOUNT_PATH = /bin/umount


This would make
debian/patches/debian/Use-different-default-paths-for-various-binaries.patch
obsolete.

-- 

Saludos,
Felipe Sateler



Bug#843457: mysql-workbench: Dependency gdal-abi-2-1-1 no longer in repo

2016-11-06 Thread Facundo Gaich
Source: mysql-workbench
Severity: grave
Justification: renders package unusable

Dear Maintainer,

mysql-workbench depends on virtual package gdal-abi-2-1-1, which isn't provided
by any other package since libgdal20 is now providing gdal-abi-2-1-2, rendering
this package uninstallable. 

Thanks
Facundo

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

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



Bug#843432: libwww-curl-perl: FTBFS: error: 'CURL_STRICTER' undeclared

2016-11-06 Thread Daniel Stenberg

On Sun, 6 Nov 2016, gregor herrmann wrote:


There's an upstream bug at
https://rt.cpan.org/Public/Bug/Display.html?id=117793
which also contains a patch.

Confirmation from the curl maintainers that the patch makes sense would be 
welcome.


Seems sensible. CURL_STRICTER is just a define an application can define to 
change some typedefs in the header files to make the type checking stricter.


--

 / daniel.haxx.se



Processed: yapps2: diff for NMU version 2.1.1-17.4

2016-11-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tag 817771 patch pending
Bug #817771 {Done: Colin Watson } [src:yapps2] yapps2: 
Removal of debhelper compat 4
Added tag(s) pending and patch.
> tag 833233 patch pending
Bug #833233 {Done: Colin Watson } [src:yapps2] yapps2: 
Uses obsolete Source-Version substvar
Added tag(s) pending and patch.
> thanks
Stopping processing here.

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



Bug#817771: yapps2: diff for NMU version 2.1.1-17.4

2016-11-06 Thread Colin Watson
tag 817771 patch pending
tag 833233 patch pending
thanks

Dear maintainer,

I've prepared an NMU for yapps2 (versioned as 2.1.1-17.4) and uploaded
it to DELAYED/0.  Please feel free to tell me if I should delay it
longer.

Regards,

-- 
Colin Watson   [cjwat...@debian.org]
diff -u yapps2-2.1.1/debian/changelog yapps2-2.1.1/debian/changelog
--- yapps2-2.1.1/debian/changelog
+++ yapps2-2.1.1/debian/changelog
@@ -1,3 +1,11 @@
+yapps2 (2.1.1-17.4) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Bump to debhelper compat level 9 (closes: #817771).
+  * Use ${binary:Version} rather than ${Source-Version} (closes: #833233).
+
+ -- Colin Watson   Sun, 06 Nov 2016 17:11:44 +
+
 yapps2 (2.1.1-17.3) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u yapps2-2.1.1/debian/compat yapps2-2.1.1/debian/compat
--- yapps2-2.1.1/debian/compat
+++ yapps2-2.1.1/debian/compat
@@ -1 +1 @@
-4
+9
diff -u yapps2-2.1.1/debian/control yapps2-2.1.1/debian/control
--- yapps2-2.1.1/debian/control
+++ yapps2-2.1.1/debian/control
@@ -2,13 +2,13 @@
 Section: python
 Priority: optional
 Maintainer: Matthias Urlichs 
-Build-Depends: debhelper (>= 4.1)
+Build-Depends: debhelper (>= 9~)
 Build-Depends-Indep: python-dev (>= 2.5.4-1~), hevea, dh-python
 Standards-Version: 3.7.2
 
 Package: yapps2
 Architecture: all
-Depends: ${python:Depends}, yapps2-runtime (= ${Source-Version})
+Depends: ${python:Depends}, yapps2-runtime (= ${binary:Version})
 Description: Yet Another Python Parser System
  YAPPS is an easy to use parser generator that is written in Python and
  generates Python code.  There are several parser generator systems


Bug#841429: marked as done (homesick: FTBFS under some locales (eg. fr_CH.UTF-8))

2016-11-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Nov 2016 17:49:20 +
with message-id 
and subject line Bug#841429: fixed in homesick 1.1.3-2
has caused the Debian Bug report #841429,
regarding homesick: FTBFS under some locales (eg. fr_CH.UTF-8)
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.)


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

Dear Maintainer,

homesick fails to build from source in unstable/amd64 under some locales (eg. 
LANG="fr_CH.UTF-8") as the testsuite — which is curiously run in the install
target — uses local-sensitive strings to determine success.

  […]

  
┌──┐
  │ Run tests for ruby2.3 from debian/ruby-tests.rake   
 │
  
└──┘
  
  
RUBYLIB=/home/lamby/temp/cdt.20161020163846.S0SIG1t1l1.db.homesick/homesick-1.1.3/debian/homesick/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/homesick/usr/share/rubygems-integration/all:/home/lamby/.gem/ruby/2.3.0:/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 -S rake -f debian/ruby-tests.rake
  /usr/bin/ruby2.3 /usr/bin/rspec --pattern ./spec/\*_spec.rb
  [Coveralls] Set up the SimpleCov formatter.
  [Coveralls] Using SimpleCov's default settings.
  ..WARNING: Using the `raise_error` matcher without providing a 
specific error or message risks false positives, since `raise_error` will match 
when Ruby raises a `NoMethodError`, `NameError` or `ArgumentError`, potentially 
allowing the expectation to pass without even executing the method you are 
intending to call. Actual error raised was #. Instead consider providing a specific error class or message. This 
message can be suppressed by setting: 
`RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. 
Called from 
/home/lamby/temp/cdt.20161020163846.S0SIG1t1l1.db.homesick/homesick-1.1.3/spec/homesick_cli_spec.rb:149:in
 `block (3 levels) in '.
  FF.F.
  
  Failures:
  
1) Homesick::CLI status says "nothing to commit" when there are no changes
   Failure/Error: expect(text).to match(%r{nothing to commit \(create/copy 
files and use "git add" to track\)$})
  
 expected "Sur la branche master\n\nValidation initiale\n\nrien à 
valider (créez/copiez des fichiers et utilisez \"git add\" pour les suivre)\n" 
to match /nothing to commit \(create\/copy files and use "git add" to track\)$/
 Diff:
 @@ -1,2 +1,6 @@
 -/nothing to commit \(create\/copy files and use "git add" to track\)$/
 +Sur la branche master
 +
 +Validation initiale
 +
 +rien à valider (créez/copiez des fichiers et utilisez "git add" pour 
les suivre)
   # ./spec/homesick_cli_spec.rb:441:in `block (3 levels) in '
  
2) Homesick::CLI status says "Changes to be committed" when there are 
changes
   Failure/Error: expect(text).to match(%r{Changes to be committed:.*new 
file:\s*home\/.some_rc_file}m)
  
 expected "Sur la branche master\n\nValidation 
initiale\n\nModifications qui seront validées :\n  (utilisez \"git rm --cached 
...\" pour désindexer)\n\n\tnouveau fichier : home/.some_rc_file\n\n" 
to match /Changes to be committed:.*new file:\s*home\/.some_rc_file/m
 Diff:
 @@ -1,2 +1,9 @@
 -/Changes to be committed:.*new file:\s*home\/.some_rc_file/m
 +Sur la branche master
 +
 +Validation initiale
 +
 +Modifications qui seront validées :
 +  (utilisez "git rm --cached ..." pour désindexer)
 +
 +  nouveau fichier : home/.some_rc_file
   # ./spec/homesick_cli_spec.rb:449:in `block (3 levels) in '
  
3) Homesick::CLI track commit has a commit message when the commit succeeds
   Failure/Error: expect(text).to match(/^\[master \(root-commit\) \w+\] 
Test message/)
  
 expected "[master (commit racine) 9bf3bd7] Test message\n 1 file 
changed, 0 insertions(+), 0 deletions(-)\n create mode 100644 
home/.a_random_rc_file\n" to match 

Bug#833233: marked as done (yapps2: Uses obsolete Source-Version substvar)

2016-11-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Nov 2016 17:36:15 +
with message-id 
and subject line Bug#833233: fixed in yapps2 2.1.1-17.4
has caused the Debian Bug report #833233,
regarding yapps2: Uses obsolete Source-Version substvar
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.)


-- 
833233: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833233
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: yapps2
Source-Version: 2.1.1-17.3
Severity: important
User: debian-d...@lists.debian.org
Usertags: dpkg-obsolete-source-version-substvar

Hi!

This source package uses the ${Source-Version} substvar variable
deprecated since dpkg 1.13.19 in 2006-05-04. That upload also introduced
the substvars binary:Version and source:Version which can be used
instead.

Using this deprecated substvar will become an error in the near
future. Please update the package.

See also .

Thanks,
Guillem
--- End Message ---
--- Begin Message ---
Source: yapps2
Source-Version: 2.1.1-17.4

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

Debian distribution maintenance software
pp.
Colin Watson  (supplier of updated yapps2 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, 06 Nov 2016 17:11:44 +
Source: yapps2
Binary: yapps2 yapps2-runtime
Architecture: source
Version: 2.1.1-17.4
Distribution: unstable
Urgency: medium
Maintainer: Matthias Urlichs 
Changed-By: Colin Watson 
Description:
 yapps2 - Yet Another Python Parser System
 yapps2-runtime - Yet Another Python Parser System
Closes: 817771 833233
Changes:
 yapps2 (2.1.1-17.4) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Bump to debhelper compat level 9 (closes: #817771).
   * Use ${binary:Version} rather than ${Source-Version} (closes: #833233).
Checksums-Sha1:
 c3879ee7575957f40be65ee28638e525e410f295 1791 yapps2_2.1.1-17.4.dsc
 3052826b52a023a20270fc6d68aa9e16f5fb5bdd 40317 yapps2_2.1.1-17.4.diff.gz
Checksums-Sha256:
 d2b1ffb04109d7f651c9ff0eb7c3b254e148d725a7ec388c1ee349796a377d79 1791 
yapps2_2.1.1-17.4.dsc
 f1f8fb16eb8f5c4f4ae7e77cf62c4d10b5a16d6398438cf20adbd521622e1ad0 40317 
yapps2_2.1.1-17.4.diff.gz
Files:
 55fe5f9d7ac32e6224eedaa57dcfb153 1791 python optional yapps2_2.1.1-17.4.dsc
 dbe8934e23ce75142b482f5a9226ce42 40317 python optional 
yapps2_2.1.1-17.4.diff.gz

-BEGIN PGP SIGNATURE-
Comment: Colin Watson  -- Debian developer

iQIcBAEBCAAGBQJYH2SFAAoJEDk1h9l9hlALSvwP+gIKgzCBI3PZYy+n8Fzvt0nP
fcOdej9CYeAqw5nnRoVWIbtp7j3Q5Jmpx9ij+7FssIn2anb7vGEzObQcIJHA6x9V
bbxvV1S+iD2in0oyaeOpFZuup7lzQbxEL6sZyWTtnvsUirLnYq/sff49mELqdjr8
7m4ZEKfqS6hImnNNs4k+6UNb4jPo3qYT2CiaVSM+fvaTP22pMb/rUl9X0UeP72JL
G4wXzYqUXVdgJm0lSJpCW5u9n+mahgLyfN1Bjwu/YlwslQOd5Oz0w7M3x80UIrgl
TIVMZYhFKUZR8fbISe6ngvNHZknfh51oDUOr2HZk1Aau+wQ97n3iCJ+nR78MSJgt
mOaR4QH61kULbSfXg74Hul+BLQXqP3UE0M4YouhhrxMZLRziI/FbOWsofn3JJIde
J/5HxhgHYoEGuJ+mueqQcDOLNEB+uzkPyvmF7zEqlJUZ6KdfK4jrAjswVNchudKZ
2UQDb4PHLsKETBT0h43N/G3fhADzmJ1OM1TbPDEyfEr+K8ERCy10OJ3movFXDvQu
RqD8KaSNub3A86O+wRc4MVPzhN7cA6/3rxtLEu8WF3YGe7siEkok4PkDtOYygbA/
eeUYDcPMCP1UO15HrqtfMwIIES3yIhw4ejAOvUPwrKwP13RsThWLOjUcqux/yLhS
nzFJk5q8tpzsRghzg4WR
=xP9/
-END PGP SIGNATURE End Message ---


Bug#811862: marked as done (libqalculate: FTBFS with GCC 6: no matching function for call to)

2016-11-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Nov 2016 17:35:01 +
with message-id 
and subject line Bug#811862: fixed in libqalculate 0.9.7-9.2
has caused the Debian Bug report #811862,
regarding libqalculate: FTBFS with GCC 6: no matching function for call to
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.)


-- 
811862: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811862
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libqalculate
Version: 0.9.7-9.1
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-no-match

This package fails to build with GCC 6.  GCC 6 has not been released
yet, but it's expected that GCC 6 will become the default compiler for
stretch.

Note that only the first error is reported; there might be more.  You
can find a snapshot of GCC 6 in experimental.  To build with GCC 6,
you can set CC=gcc-6 CXX=g++-6 explicitly.

You may be able to find out more about this issue at
https://gcc.gnu.org/gcc-6/changes.html

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> /bin/bash ../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. -I.. 
> -I../ -DPACKAGE_DATA_DIR=\""/usr/share"\" 
> -DPACKAGE_LOCALE_DIR=\""/usr/share/locale"\" -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libxml2  
> -Wdate-time -D_FORTIFY_SOURCE=2   -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -c -o MathStructure.lo MathStructure.cc
> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. -I../ 
> -DPACKAGE_DATA_DIR=\"/usr/share\" -DPACKAGE_LOCALE_DIR=\"/usr/share/locale\" 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
> -I/usr/include/libxml2 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -c MathStructure.cc 
>  -fPIC -DPIC -o .libs/MathStructure.o
> In file included from /usr/include/c++/6/ext/hash_map:60:0,
>  from ../libqalculate/includes.h:40,
>  from MathStructure.h:15,
>  from MathStructure.cc:14:
> /usr/include/c++/6/backward/backward_warning.h:32:2: warning: #warning This 
> file includes at least one deprecated or antiquated header which may be 
> removed without further notice at a future date. Please use a non-deprecated 
> interface with equivalent functionality instead. For a listing of replacement 
> headers and interfaces, consult the file backward_warning.h. To disable this 
> warning use -Wno-deprecated. [-Wcpp]
>  #warning \
>   ^~~
> 
> MathStructure.cc: In function 'bool sr_gcd(const MathStructure&, const 
> MathStructure&, MathStructure&, std::vector::const_iterator, const 
> EvaluationOptions&)':
> MathStructure.cc:7166:53: error: no matching function for call to 
> 'MathStructure::gcd(MathStructure&, MathStructure&, MathStructure&, const 
> EvaluationOptions&, bool)'
>   MathStructure::gcd(cont_c, cont_d, gamma, eo, false);
>  ^
> 
> In file included from MathStructure.cc:14:0:
> MathStructure.h:827:15: note: candidate: static bool MathStructure::gcd(const 
> MathStructure&, const MathStructure&, MathStructure&, const 
> EvaluationOptions&, MathStructure*, MathStructure*, bool)
>static bool gcd(const MathStructure , const MathStructure , 
> MathStructure , const EvaluationOptions , MathStructure *ca = 
> NULL, MathStructure *cb = NULL, bool check_args = true);
>^~~
> 
> MathStructure.h:827:15: note:   no known conversion for argument 5 from 
> 'bool' to 'MathStructure*'

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: libqalculate
Source-Version: 0.9.7-9.2

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated libqalculate 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, 06 Nov 2016 

Bug#817771: marked as done (yapps2: Removal of debhelper compat 4)

2016-11-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Nov 2016 17:36:15 +
with message-id 
and subject line Bug#817771: fixed in yapps2 2.1.1-17.4
has caused the Debian Bug report #817771,
regarding yapps2: Removal of debhelper compat 4
to be marked as done.

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

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


-- 
817771: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817771
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: yapps2
Severity: important
Usertags: compat-4-removal

Hi,

The package yapps2 uses debhelper with a compat level of 4,
which is deprecated and scheduled for removal.

 * Please bump the debhelper compat at your earliest convenience.
   on the 15th of June.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum
   - If the package has been relying on dh_install being lenient about
 missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * Compat level 4 will be removed on the first debhelper upload after
   the 15th of June.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: yapps2
Source-Version: 2.1.1-17.4

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

Debian distribution maintenance software
pp.
Colin Watson  (supplier of updated yapps2 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, 06 Nov 2016 17:11:44 +
Source: yapps2
Binary: yapps2 yapps2-runtime
Architecture: source
Version: 2.1.1-17.4
Distribution: unstable
Urgency: medium
Maintainer: Matthias Urlichs 
Changed-By: Colin Watson 
Description:
 yapps2 - Yet Another Python Parser System
 yapps2-runtime - Yet Another Python Parser System
Closes: 817771 833233
Changes:
 yapps2 (2.1.1-17.4) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Bump to debhelper compat level 9 (closes: #817771).
   * Use ${binary:Version} rather than ${Source-Version} (closes: #833233).
Checksums-Sha1:
 c3879ee7575957f40be65ee28638e525e410f295 1791 yapps2_2.1.1-17.4.dsc
 3052826b52a023a20270fc6d68aa9e16f5fb5bdd 40317 yapps2_2.1.1-17.4.diff.gz
Checksums-Sha256:
 d2b1ffb04109d7f651c9ff0eb7c3b254e148d725a7ec388c1ee349796a377d79 1791 
yapps2_2.1.1-17.4.dsc
 f1f8fb16eb8f5c4f4ae7e77cf62c4d10b5a16d6398438cf20adbd521622e1ad0 40317 
yapps2_2.1.1-17.4.diff.gz
Files:
 55fe5f9d7ac32e6224eedaa57dcfb153 1791 python optional yapps2_2.1.1-17.4.dsc
 dbe8934e23ce75142b482f5a9226ce42 40317 python optional 
yapps2_2.1.1-17.4.diff.gz

-BEGIN PGP SIGNATURE-
Comment: Colin Watson  -- Debian developer

iQIcBAEBCAAGBQJYH2SFAAoJEDk1h9l9hlALSvwP+gIKgzCBI3PZYy+n8Fzvt0nP
fcOdej9CYeAqw5nnRoVWIbtp7j3Q5Jmpx9ij+7FssIn2anb7vGEzObQcIJHA6x9V
bbxvV1S+iD2in0oyaeOpFZuup7lzQbxEL6sZyWTtnvsUirLnYq/sff49mELqdjr8
7m4ZEKfqS6hImnNNs4k+6UNb4jPo3qYT2CiaVSM+fvaTP22pMb/rUl9X0UeP72JL
G4wXzYqUXVdgJm0lSJpCW5u9n+mahgLyfN1Bjwu/YlwslQOd5Oz0w7M3x80UIrgl
TIVMZYhFKUZR8fbISe6ngvNHZknfh51oDUOr2HZk1Aau+wQ97n3iCJ+nR78MSJgt
mOaR4QH61kULbSfXg74Hul+BLQXqP3UE0M4YouhhrxMZLRziI/FbOWsofn3JJIde
J/5HxhgHYoEGuJ+mueqQcDOLNEB+uzkPyvmF7zEqlJUZ6KdfK4jrAjswVNchudKZ
2UQDb4PHLsKETBT0h43N/G3fhADzmJ1OM1TbPDEyfEr+K8ERCy10OJ3movFXDvQu
RqD8KaSNub3A86O+wRc4MVPzhN7cA6/3rxtLEu8WF3YGe7siEkok4PkDtOYygbA/
eeUYDcPMCP1UO15HrqtfMwIIES3yIhw4ejAOvUPwrKwP13RsThWLOjUcqux/yLhS
nzFJk5q8tpzsRghzg4WR
=xP9/
-END PGP SIGNATURE End Message ---


Bug#712102: marked as done (Plugin no longer functions with Twitter or Identica)

2016-11-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Nov 2016 17:31:10 +
with message-id 
and subject line Bug#724983: Removed package(s) from unstable
has caused the Debian Bug report #712102,
regarding Plugin no longer functions with Twitter or Identica
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.)


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

Package: pidgin-microblog
Version: 0.3.0-3
Severity: important

Dear Maintainer,

   * What led up to the situation?
 
 The Twitter API 1 drop dead date apparently arrived and the previously 
available access to Twitter was gone.

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

 I attempted to login as normal to Twitter using Pidgin.

   * What was the outcome of this action?

 Authentication error.  This was similar to what was reported by Wil 
Wheaton as to his particular client no longer accessing Twitter: 
https://plus.google.com/108176814619778619437/posts/Bb2biiyguzj

   * What outcome did you expect instead?

 Being able to access Twitter.

Bug is additionally reported upstream at: 
http://code.google.com/p/microblog-purple/issues/detail?id=269

-- System Information:
Debian Release: 7.0
Architecture: armhf (armv6l)

Kernel: Linux 3.6.11+ (PREEMPT)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash

Versions of packages pidgin-microblog depends on:
ii  libatk1.0-0 2.4.0-2
ii  libc6   2.13-38+rpi2
ii  libcairo2   1.12.2-3
ii  libfontconfig1  2.9.0-7.1
ii  libfreetype62.4.9-1.1
ii  libgdk-pixbuf2.0-0  2.26.1-1
ii  libglib2.0-02.33.12+really2.32.4-5
ii  libgtk2.0-0 2.24.10-2
ii  libpango1.0-0   1.30.0-1
ii  libpurple0  2.10.6-3

pidgin-microblog recommends no packages.

pidgin-microblog suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.3.0-3+rm

Dear submitter,

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

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

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

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

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


Bug#818537: marked as done (maildrop: FTBFS: ./../../depcomp: No such file or directory)

2016-11-06 Thread Debian Bug Tracking System
Your message dated Sun, 6 Nov 2016 17:59:35 +0100
with message-id <20161106165935.ga22...@entuzijast.net>
and subject line Re: Bug#818537: maildrop: FTBFS: ./../../depcomp: No such file 
or directory
has caused the Debian Bug report #818537,
regarding maildrop: FTBFS: ./../../depcomp: 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.)


-- 
818537: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818537
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: maildrop
Version: 2.7.1-3
Severity: serious

This package fails to build in unstable:

> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...
> make[3]: Entering directory '/<>/libs/numlib'
> source='atotimet.c' object='atotimet.lo' libtool=yes \
> DEPDIR=.deps depmode=none /bin/bash ./../../depcomp \
> /bin/bash ./libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I.   
> -Wdate-time -D_FORTIFY_SOURCE=2  -I.. -I./.. -g -O2 -fstack-protector-strong 
> -Wformat -Werror=format-security -Wall -pedantic -Wall -c -o atotimet.lo 
> atotimet.c
> /bin/bash: ./../../depcomp: No such file or directory
> Makefile:452: recipe for target 'atotimet.lo' failed
> make[3]: *** [atotimet.lo] Error 127
> make[3]: Leaving directory '/<>/libs/numlib'
> Makefile:345: recipe for target 'all' failed
> make[2]: *** [all] Error 2
> make[2]: Leaving directory '/<>/libs/numlib'
> Makefile:829: recipe for target 'all-recursive' failed
> make[1]: *** [all-recursive] Error 1

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Hi,

The recent uploads of versions 2.8.3 and 2.8.4 seemed to have no trouble
building on the buildd network.

I'm going to assume this was something about the combination of 2.7.1 and
unstable, which doesn't appear to be relevant any more.

If you can still reproduce a problem, please reopen the bug.

Thanks for reporting.

On Thu, Mar 17, 2016 at 01:20:34PM -0700, Martin Michlmayr wrote:
> Package: maildrop
> Version: 2.7.1-3
> Severity: serious
> 
> This package fails to build in unstable:
> 
> > sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
> ...
> > make[3]: Entering directory '/<>/libs/numlib'
> > source='atotimet.c' object='atotimet.lo' libtool=yes \
> > DEPDIR=.deps depmode=none /bin/bash ./../../depcomp \
> > /bin/bash ./libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I.   
> > -Wdate-time -D_FORTIFY_SOURCE=2  -I.. -I./.. -g -O2 
> > -fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic 
> > -Wall -c -o atotimet.lo atotimet.c
> > /bin/bash: ./../../depcomp: No such file or directory
> > Makefile:452: recipe for target 'atotimet.lo' failed
> > make[3]: *** [atotimet.lo] Error 127
> > make[3]: Leaving directory '/<>/libs/numlib'
> > Makefile:345: recipe for target 'all' failed
> > make[2]: *** [all] Error 2
> > make[2]: Leaving directory '/<>/libs/numlib'
> > Makefile:829: recipe for target 'all-recursive' failed
> > make[1]: *** [all-recursive] Error 1
> 
> -- 
> Martin Michlmayr
> Linux for HPE Helion, Hewlett Packard Enterprise

-- 
 2. That which causes joy or happiness.--- End Message ---


Bug#843432: libwww-curl-perl: FTBFS: error: 'CURL_STRICTER' undeclared

2016-11-06 Thread gregor herrmann
On Sun, 06 Nov 2016 19:06:43 +0200, Niko Tyni wrote:

> As noticed by the reproducible-builds.org CI system, this package fails
> to build on current sid. It looks like this broke with the recent curl
> 7.51.0-1 upload, so cc'ing the curl maintainers too.

There's an upstream bug at
https://rt.cpan.org/Public/Bug/Display.html?id=117793
which also contains a patch.

Confirmation from the curl maintainers that the patch makes sense
would be welcome.


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: Dire Straits: Money For Nothing


signature.asc
Description: Digital Signature


Processed: bug 843432 is forwarded to https://rt.cpan.org/Public/Bug/Display.html?id=117793

2016-11-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> # also contains a patch
> forwarded 843432 https://rt.cpan.org/Public/Bug/Display.html?id=117793
Bug #843432 [libwww-curl-perl] libwww-curl-perl: FTBFS: error: 'CURL_STRICTER' 
undeclared
Set Bug forwarded-to-address to 
'https://rt.cpan.org/Public/Bug/Display.html?id=117793'.
> thanks
Stopping processing here.

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



Processed: tagging 843432

2016-11-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 843432 + confirmed patch
Bug #843432 [libwww-curl-perl] libwww-curl-perl: FTBFS: error: 'CURL_STRICTER' 
undeclared
Added tag(s) confirmed and patch.
> thanks
Stopping processing here.

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



Processed: tagging 825608

2016-11-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 825608 - pending
Bug #825608 [libnet-jifty-perl] libnet-jifty-perl: FTBFS: t/006-uploads.t 
failure
Removed tag(s) pending.
> thanks
Stopping processing here.

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



Bug#843086: marked as done (mdk3: FTBFS: No rule to make target 'osdep/libosdep.a')

2016-11-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Nov 2016 17:19:28 +
with message-id 
and subject line Bug#843086: fixed in mdk3 6.0-3
has caused the Debian Bug report #843086,
regarding mdk3: FTBFS: No rule to make target 'osdep/libosdep.a'
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.)


-- 
843086: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843086
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mdk3
Version: 6.0-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

[Filing as a regression due to the likelihood of affecting any binNMUs.]

Builds of mdk3 that use parallel make have been failing:

  make -C osdep
  make[1]: *** No rule to make target 'osdep/libosdep.a', needed by 'mdk3'.  
Stop.
  make[1]: *** Waiting for unfinished jobs
  make[2]: Entering directory '/«PKGBUILDDIR»/osdep'

The issue appears to be a typo in the top-level Makefile, which only
supplies a rule for osdep/libosdep.so even though libosdep is always
static.

Could you please take a look?

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
--- End Message ---
--- Begin Message ---
Source: mdk3
Source-Version: 6.0-3

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

Debian distribution maintenance software
pp.
Samuel Henrique  (supplier of updated mdk3 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, 06 Nov 2016 13:50:23 -0200
Source: mdk3
Binary: mdk3
Architecture: source
Version: 6.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools Packaging Team 

Changed-By: Samuel Henrique 
Description:
 mdk3   - Wireless attack tool for IEEE 802.11 networks
Closes: 843086 843089 843092 843093
Changes:
 mdk3 (6.0-3) unstable; urgency=medium
 .
   * debian/control: Change Architecture from any to linux-any
 (closes: #843092, #843093).
   * debian/mdk3.1: Update to point to example files correct location.
   * debian/patches:
 - example_file.patch: Update to point to correct location.
 - makefile_flags.patch: Update to fix FTBFS with parallel builds
   (closes: #843086).
 - linux_macro.patch: New patch, check for "__linux__" macro instead of
   "linux", this fix FTBFS when running GCC with GNU extensions disabled
   (closes: #843089).
 - radiotap_needs_types_h.patch: New patch from OpenWRT, fix FTBFS on mips.
Checksums-Sha1:
 8aa1a7f603c137014312f1c09b2b4fd96c1332cc 1894 mdk3_6.0-3.dsc
 ebfb4e65f2c5ca7cd40d5ed86ed395dc0f3fa973 9988 mdk3_6.0-3.debian.tar.xz
Checksums-Sha256:
 22a15b28979672bdb2344e30d216ced3edb9ccd62a3f94b561096840709669a7 1894 
mdk3_6.0-3.dsc
 2bd885d7322dc448e02dab7b0d5c4f0ba941620edf15b9dee1b216deb143be19 9988 
mdk3_6.0-3.debian.tar.xz
Files:
 d0b95ecb3d1c05bc6eea98e4c45f54ad 1894 net extra mdk3_6.0-3.dsc
 f2b594a84cb731c3e0153275212321ca 9988 net extra mdk3_6.0-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIxBAEBCAAbBQJYH2CJFBxzYW11ZWxvcGhAZ21haWwuY29tAAoJEFmJXkSxaWJt
+REQAMLTkwdkYLWN9fFxJmrmeJBggZgqpTw0ocpt3n8HzPC/OseHMvturGq/gZbA
LVnlIhNqSOXOfkh6eqd3OGiZZxI+tw3KQl5qW/eF96If5JghTFj2sofN2W3WNnpx
LjgGZ4ln6WW5gKfxM3Qlycy0G43wxEpeRjdTXfTNAArNjDELlFViRkJRg95EbibY
3vUTSY36qYCqnQc11nlMDCUrOV4wKNBIYXNIqBEXrOJax6RJ2fQjHwOpJf0tMRgs
+nFnuE5Ksn4gga1wmj7GcjmFdDztgrk9mJpV3Zm1EDzZMIdFaCv3dvE4FZbMjVsb
sQHssiHcIVIHZhy2MiSWrFYnb/kkGs/4VrKSFa7tQ05UnLgx/HajSZ9vzBlCB50C
LaazctX6dy/JiClAiXxQzCvZagRx6jLPx9la5fpSieDN0G/vN2bb15Wfz+VZuB9F
EJyUIE6tzu7H3sMIVq7FobulGec5PhL59SG1INGhNQCgZ3mhM8d5S/nYGCfvQ8bH
TIBD/XiyTahGAcoWfFP8fztwkSxfoui74TUeC+NKwQZ58Yz5eVQYmqkP3tDPUTm4
R4OrdwHoLjjpGnmwpVhkqOr9sFVKuaSKdOnvFx/GXHDjE9FAgFT0+hNR8k50DHfP
tYSFuvPmfRTlUNg10wkt2L2rGpk/aM9FUNwNbAZAcmiVaQcl
=dZj0
-END PGP SIGNATURE End Message ---


Bug#841543: help needed to fix ruby-carrierware FTBFS

2016-11-06 Thread Pirate Praveen
With the recent upload of mysql-server 5.7, mysql_install_db is
deprecated, we are supposed to use mysqld --initialize.

I tried replacing mysql_init_db with /usr/sbin/mysqld --initialize, but
the options are not a one to one map. Can anyone help with this?



signature.asc
Description: OpenPGP digital signature


Bug#843434: terminology: Escape Sequence Command Execution vulnerability

2016-11-06 Thread Salvatore Bonaccorso
Source: terminology
Version: 0.7.0-1
Severity: grave
Tags: security upstream patch
Justification: user security hole

Hi

terminology is suspectible to an escape sequence command execution
vulnerability, as described in
http://www.openwall.com/lists/oss-security/2016/11/04/12

The CVE has not yet been assigned, will update the subject here once
it's done.

Regards,
Salvatore



Bug#843432: libwww-curl-perl: FTBFS: error: 'CURL_STRICTER' undeclared

2016-11-06 Thread Niko Tyni
Package: libwww-curl-perl
Version: 4.17-2
Severity: serious
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org, 
c...@packages.debian.org

As noticed by the reproducible-builds.org CI system, this package fails
to build on current sid. It looks like this broke with the recent curl
7.51.0-1 upload, so cc'ing the curl maintainers too.

  
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/i386/libwww-curl-perl.html

Excerpt from a local amd64 build log:

  x86_64-linux-gnu-gcc -c  -I/usr/include -D_REENTRANT -D_GNU_SOURCE -DDEBIAN 
-fwrapv -fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2   -DVERSION=\"4.17\" -DXS_VERSION=\"4.17\" -fPIC 
"-I/usr/lib/x86_64-linux-gnu/perl/5.24/CORE"   Curl.c
  In file included from Curl.xs:574:0:
  curlopt-constants.c: In function 'constant':
  curlopt-constants.c:19:58: warning: 'return' with no value, in function 
returning non-void
   if (strEQ(name, "DID_MEMORY_FUNC_TYPEDEFS")) return 
CURL_DID_MEMORY_FUNC_TYPEDEFS;
^~
  curlopt-constants.c:2:1: note: declared here
   constant(const char *name)
   ^~~~
  curlopt-constants.c:128:49: error: 'CURL_STRICTER' undeclared (first use in 
this function)
   if (strEQ(name, "STRICTER")) return CURL_STRICTER;
   ^
  curlopt-constants.c:128:49: note: each undeclared identifier is reported only 
once for each function it appears in
  curlopt-constants.c:2051:44: warning: overflow in implicit constant 
conversion [-Woverflow]
   if (strEQ(name, "ANY")) return CURLAUTH_ANY;
  ^~~~
  curlopt-constants.c:2052:48: warning: overflow in implicit constant 
conversion [-Woverflow]
   if (strEQ(name, "ANYSAFE")) return CURLAUTH_ANYSAFE;
  ^~~~
  Makefile:357: recipe for target 'Curl.o' failed
  make[1]: *** [Curl.o] Error 1
 
-- 
Niko Tyni   nt...@debian.org



Bug#843433: Wrong paths for /bin/mount when compiled on merged-usr system

2016-11-06 Thread Michael Biebl
Source: systemd
Version: 232-2
Severity: serious
User: m...@linux.it
Usertags: usrmerge

As reported on IRC

 mbiebl:
https://buildd.debian.org/status/fetch.php?pkg=systemd=sparc64=232-2=1478397115
has split-usr enabled, but because it finds /usr/bin/mount at configure
time, it uses that rather than /bin/mount
 (chroots are created with debootstrap from unstable, which does
usr-merge since 21st Oct)
 then, on systems without usr-merge, boom


We should probably update
debian/patches/debian/Use-different-default-paths-for-various-binaries.patch
and use a different search path which prefers /bin and /sbin, like

-AC_PATH_PROG([MOUNT_PATH], [mount], [/usr/bin/mount], [$PATH:/usr/sbin:/sbin])
-AC_PATH_PROG([UMOUNT_PATH], [umount], [/usr/bin/umount], 
[$PATH:/usr/sbin:/sbin])
+AC_PATH_PROG([MOUNT_PATH], [mount], [/usr/bin/mount], [/sbin:/bin:$PATH])
+AC_PATH_PROG([UMOUNT_PATH], [umount], [/usr/bin/umount], [/sbin:/bin:$PATH])


(we should do that for all occurences of AC_PATH_PROG)


Thoughts? Does anyone have a nicer solution?




-- Package-specific info:

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

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

Versions of packages systemd is related to:
pn  dracut   
ii  initramfs-tools  0.125
ii  udev 232-2

-- no debconf information



Bug#821522: marked as done (libmarkdown-php: PHP 7.0 Transition)

2016-11-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Nov 2016 17:04:18 +
with message-id 
and subject line Bug#821522: fixed in libmarkdown-php 1.0.2-2
has caused the Debian Bug report #821522,
regarding libmarkdown-php: PHP 7.0 Transition
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.)


-- 
821522: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821522
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libmarkdown-php
Version: 1.0.2-1
Severity: important
User: pkg-php-ma...@lists.alioth.debian.org
Usertags: php7.0-transition

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear maintainer(s),

this bug is a part of ongoing php7.0 transition.  It is filled as
important, but the severity will be bumped to serious within quite short
(~month) timeframe as the transition was announced almost 3 months ago.

The libmarkdown-php package currently depends on php5 php5-cli .

PHP 7.0 has landed in unstable with substantial changes to the packaging:

  1. Every package built from src:phpMAJOR.MINOR now include
 phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm.

  2. Accompanying src:php-defaults builds 1:1 mapping to a default
 MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm.  When you
 specify a dependency, please use the generic name, unless you
 absolutely know that won't work for you.

  3. Every path in the system has been changed to a versioned, e.g.
 /etc/php5/cli is now /etc/php/7.0/cli

  4. dh_php5 is now dh_php

  5. php-pear is not built from independent source package.

  6. master-7.0 branches of several extensions (php-apcu, xdebug,
 php-apcu-bc) can be used as a template how to change the PHP
 extension packaging.  It's mostly cut since the d/rules tries
 to figure-out most of the variables from debian/ directory.

  7. pkg-php-tools package now supports PHP 7.0 packaging and if your
 package uses pkg-php-tools a simple binNMU is all it might need

  8. PHP 7.0 has changed extension API, so most-if-not-all extensions
 need work from upstream to be compatible with PHP 7.0.

  9. We expect to ship next Debian release (stretch) only with PHP
 7.0, that means that all packages needs to be made compatible with
 PHP 7.0.  Fortunately the PHP 7.0 is mostly compatible with properly
 maintained software.  However some extensions has been deprecated
 (f.e. mysql) and thus old unmaintained software will stop working
 and it will have to be either patched or removed from stable Debian.

So what you need to do:

Replace every occurence of php5 with just php, e.g. if you depend on
'php5' then you just need to depend on 'php'.  Also if you package a web
application and depend on specific SAPI, I would recommend depending just
on 'php' package and let the user decide whether he will install php-fpm,
libapache2-mod-php or php-cgi.

The script that was used to get the list of packages for MBF was not a
particular smart one (so it doesn't detect alternatives, etc.), so if
there's a false positive, please excuse me and just close the bug with
short explanation.

The other options that might be used with packages that don't and won't
support PHP 7.0 is to remove the software from Debian by changing the
title of this bugreport to:

RM: libmarkdown-php -- ROM; doesn't support PHP 7.0

reassigning it to ftp.debian.org pseudo-package and changing severity to
'normal'.

Also feel free to contact the maintainers at one of the lists:

pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages
pkg-php-p...@lists.alioth.debian.org -- for PHP extensions
pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all

Cheers, Ondrej

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

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

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQJ8BAEBCgBmBQJXFUp7XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHFJsQALri8baRQSKpGEbfZM083kUZ
gjzHxScj6SslgpORO6jqTy3SdjNijmWfX01uDjDW+lVWUTkdEL2QfnzuYruX+L1o
eVFyN1KbIRXigTlXzGJ03CwBw4F2QHd8RqJyTEhNb4lqFGaLwpx7YwrsDZQgKgFe
A0h6yiEFKjBaviQ9Ltc1iy88GtVSqnAs22o4h2Py5jhlDD371+G+l+VR4iDo6J1+

Processed: Pending fixes for bugs in the libnet-jifty-perl package

2016-11-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tag 825608 + pending
Bug #825608 [libnet-jifty-perl] libnet-jifty-perl: FTBFS: t/006-uploads.t 
failure
Added tag(s) pending.
> thanks
Stopping processing here.

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



Bug#825608: Pending fixes for bugs in the libnet-jifty-perl package

2016-11-06 Thread pkg-perl-maintainers
tag 825608 + pending
thanks

Some bugs in the libnet-jifty-perl package are closed in revision
a5853d89d7640cf25692ddb8c15404b13d534c1b in branch 'master' by gregor
herrmann

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libnet-jifty-perl.git/commit/?id=a5853d8

Commit message:

Add test patch for compatibility with newer Encode.

Closes: #825608



Bug#843086: marked as pending

2016-11-06 Thread Samuel Henrique
tag 843086 pending
thanks

Hello,

Bug #843086 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://git.debian.org/?p=pkg-security/mdk3.git;a=commitdiff;h=a2d2247

---
commit a2d22471628c588aec65f178516cfaa389978f51
Author: Samuel Henrique 
Date:   Sun Nov 6 13:29:38 2016 -0200

d/patches/makefile_flags: Fix parallel build

diff --git a/debian/changelog b/debian/changelog
index cea43ef..370300f 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+mdk3 (6.0-3) unstable; urgency=medium
+
+  * debian/patches/makefile_flags.patch: Update to fix FTBFS with parallel
+builds (closes: #843086).
+
+ -- Samuel Henrique   Sun, 06 Nov 2016 13:31:34 -0200
+
 mdk3 (6.0-2) unstable; urgency=medium
 
   * Implement suggestions from lumin:



Processed: Bug#843086 marked as pending

2016-11-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tag 843086 pending
Bug #843086 [src:mdk3] mdk3: FTBFS: No rule to make target 'osdep/libosdep.a'
Added tag(s) pending.
> thanks
Stopping processing here.

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



Bug#843425: blender doesn't optimize for amd64 defaults

2016-11-06 Thread Matthias Klose
Package: src:blender
Version: 2.77.a+dfsg0-9
Severity: serious
Tags: sid stretch

as seen with #843379, blender optimizes on amd64 with
-msse -msse2 -msse3 -mssse3 -msse4.1 -mavx -mavx2 -mfma -mlzcnt -mbmi -mbmi2
-mf16c -mfpmath=sse

per policy, compiler defaults should be used.



Processed: severity of 833251 is serious, severity of 833252 is serious

2016-11-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 833251 serious
Bug #833251 [src:libx86] libx86: Uses obsolete compressor for .deb data.tar 
member
Severity set to 'serious' from 'important'
> severity 833252 serious
Bug #833252 [src:lbzip2] lbzip2: Uses obsolete compressor for .deb data.tar 
member
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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



Bug#843208: marked as done (plasma-workspace: Does not start plasmashell on the KDE.)

2016-11-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Nov 2016 15:39:06 +
with message-id 
and subject line Bug#843250: fixed in qtdeclarative-opensource-src 
5.7.1~20161021-5
has caused the Debian Bug report #843250,
regarding plasma-workspace: Does not start plasmashell on the KDE.
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.)


-- 
843250: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843250
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: plasma-workspace
Version: 4:5.8.2-1
Severity: important

Dear Maintainer,

The screen is BLACK vision and the process plasmashell is missing and
closing in one minute. Not executing new programs and not working on the 
versions packages in this moment.

Problem on the akonadi? Any ideas?

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

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

Versions of packages plasma-workspace depends on:
ii  dbus-x11 1.10.12-1
ii  frameworkintegration 5.27.0-1
ii  gdb  7.11.1-2
ii  iso-codes3.70-1
ii  kactivitymanagerd5.8.2-1
ii  kde-cli-tools4:5.8.2-1
ii  kded55.27.0-1
ii  kinit5.27.0-1
ii  kio  5.27.0-2
ii  kpackagetool55.27.0-1
ii  libc62.24-5
ii  libcln6  1.3.4-2
ii  libdbusmenu-qt5-20.9.3+16.04.20160218-1
ii  libgcc1  1:6.2.0-11
ii  libgps22 3.16-3
ii  libice6  2:1.0.9-1+b1
ii  libkf5activities55.27.0-1
ii  libkf5auth5  5.27.0-1
ii  libkf5baloo5 5.27.0-1
ii  libkf5bookmarks5 5.27.0-1
ii  libkf5calendarevents55.27.0-1+b1
ii  libkf5completion55.27.0-1
ii  libkf5configcore55.27.0-1
ii  libkf5configgui5 5.27.0-1
ii  libkf5configwidgets5 5.27.0-1
ii  libkf5coreaddons55.27.0-1
ii  libkf5crash5 5.27.0-1
ii  libkf5dbusaddons55.27.0-1
ii  libkf5declarative5   5.27.0-1+b1
ii  libkf5globalaccel-bin5.27.0-1
ii  libkf5globalaccel5   5.27.0-1
ii  libkf5guiaddons5 5.27.0-1
ii  libkf5holidays5  16.04.2-1
ii  libkf5i18n5  5.27.0-2
ii  libkf5iconthemes55.27.0-1
ii  libkf5idletime5  5.27.0-1
ii  libkf5itemviews5 5.27.0-1
ii  libkf5jobwidgets55.27.0-1
ii  libkf5js55.27.0-1
ii  libkf5jsembed5   5.27.0-1
ii  libkf5kdelibs4support5   5.27.0-1
ii  libkf5kiocore5   5.27.0-2
ii  libkf5kiofilewidgets55.27.0-2
ii  libkf5kiowidgets55.27.0-2
ii  libkf5networkmanagerqt6  5.27.0-1
ii  libkf5newstuff5  5.27.0-1
ii  libkf5notifications5 5.27.0-1
ii  libkf5notifyconfig5  5.27.0-1
ii  libkf5package5   5.27.0-1
ii  libkf5plasma55.27.0-1
ii  libkf5plasmaquick5   5.27.0-1
ii  libkf5quickaddons5   5.27.0-1+b1
ii  libkf5runner55.27.0-1
ii  libkf5service-bin5.27.0-1
ii  libkf5service5   5.27.0-1
ii  libkf5solid5 5.27.0-1
ii  libkf5texteditor55.27.0-1
ii  libkf5textwidgets5   5.27.0-1
ii  libkf5wallet-bin 5.27.0-1
ii  libkf5wallet55.27.0-1
ii  libkf5waylandclient5 4:5.27.0-1
ii  libkf5widgetsaddons5 5.27.0-1
ii  libkf5windowsystem5  

Processed: forcibly merging 842906 842982

2016-11-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> forcemerge 842906 842982
Bug #842906 [lua-sec] lua-sec: Prosody is now unable to use STARTTLS
Bug #842982 [lua-sec] lua-sec update prevents ssl connections with prosody
Severity set to 'important' from 'serious'
Added tag(s) patch.
Merged 842906 842982
> thanks
Stopping processing here.

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



Bug#843250: marked as done (qml-module-qtquick-controls is broken and breaks software using it)

2016-11-06 Thread Debian Bug Tracking System
Your message dated Sun, 06 Nov 2016 15:39:06 +
with message-id 
and subject line Bug#843250: fixed in qtdeclarative-opensource-src 
5.7.1~20161021-5
has caused the Debian Bug report #843250,
regarding qml-module-qtquick-controls is broken and breaks software using it
to be marked as done.

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

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


-- 
843250: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843250
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qml-module-qtquick-controls
Version: 5.7.1~20161021-2
Severity: important

Since the last upload (5.7.1~20161021-2) it seems something is broken.
plasmashell is giving me errors of type:
file:///usr/lib/x86_64-linux-
gnu/qt5/qml/QtQuick/Controls/Styles/Plasma/TextFieldStyle.qml:76: TypeError:
Property 'hasOwnProperty' of object TextField_QMLTYPE_151(0x3aeed10) is not a
function

I have a software build locally (I rebuilt it agains current Qt) that is giving
me the same type of errors:
file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/ScrollView.qml:198:
TypeError: Property 'hasOwnProperty' of object
QQuickListView_QML_56(0x561fa9169fe0) is not a function
file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/ScrollView.qml:198:
TypeError: Property 'hasOwnProperty' of object
QQuickListView_QML_56(0x561fa9321770) is not a function

I believe bug #843208 is a symptom of this.

Best regards (and by the way thanks for your work that is really appreciated).



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

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

Versions of packages qml-module-qtquick-controls depends on:
ii  dpkg  1.18.10
ii  libc6 2.24-5
ii  libqt5core5a [qtbase-abi-5-7-1]   5.7.1~20161021+dfsg-5
ii  libqt5gui55.7.1~20161021+dfsg-5
ii  libqt5qml5 [qtdeclarative-abi-5-7-0]  5.7.1~20161021-4
ii  libqt5quick5  5.7.1~20161021-4
ii  libqt5widgets55.7.1~20161021+dfsg-5
ii  libstdc++66.2.0-11
ii  qml-module-qtgraphicaleffects 5.7.1~20161021-3
ii  qml-module-qtquick-layouts5.7.1~20161021-4
ii  qml-module-qtquick-window25.7.1~20161021-4
ii  qml-module-qtquick2   5.7.1~20161021-4

qml-module-qtquick-controls recommends no packages.

qml-module-qtquick-controls suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: qtdeclarative-opensource-src
Source-Version: 5.7.1~20161021-5

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

Debian distribution maintenance software
pp.
Dmitry Shachnev  (supplier of updated 
qtdeclarative-opensource-src 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, 06 Nov 2016 17:01:42 +0300
Source: qtdeclarative-opensource-src
Binary: libqt5qml5 libqt5quick5 libqt5quickparticles5 libqt5quicktest5 
libqt5quickwidgets5 qml-module-qtquick-layouts qt5-qmltooling-plugins 
qml-module-qt-labs-folderlistmodel qml-module-qtquick-localstorage 
qml-module-qtqml-models2 qml-module-qtqml-statemachine 
qml-module-qtquick-particles2 qml-module-qtquick2 qml-module-qt-labs-settings 
qml-module-qttest qml-module-qtquick-window2 qml-module-qtquick-xmllistmodel 
qtdeclarative5-dev qtdeclarative5-private-dev qtdeclarative5-dev-tools qmlscene 
qml qtdeclarative5-examples qtdeclarative5-doc qtdeclarative5-doc-html
Architecture: source
Version: 5.7.1~20161021-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 

  1   2   >