Processed: 855130 notfound in release 3.0.6-11

[Debian Bug Tracking System]

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

> notfound 855130 3.0.6-11
Bug #855130 [src:med-fichier] med-fichier: MED library is not compatible with 
HDF5 1.10
The source 'med-fichier' and version '3.0.6-11' do not appear to match any 
binary packages
No longer marked as found in versions med-fichier/3.0.6-11.
> thanks
Stopping processing here.

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

Bug#852552: marked as done (ocserv: Build fail on arm patch inc)

[Debian Bug Tracking System]

Your message dated Wed, 15 Feb 2017 15:07:18 +0800
with message-id 

Bug#839100: python-bluez: debian pybluez package version 0.22-1 uses upstream source code version 0.18

[Petter Reinholdtsen]

[Dara Adib]
> I'm marking this bug as serious for now but feel free to change the
> severity.

Can you explain what rationale you have for setting the severity as
serious?  To me it seem like an important bug at most.

And given where we are in the release process, it is unclear to me
what exactly you propose to do with pybluez in Stretch.  Removal along
with blueproximity, bluewho, ganyremote, kanyremote, kodi, kodi-pvr-argustv,
kodi-pvr-dvbviewer, kodi-pvr-hdhomerun, kodi-pvr-hts, kodi-pvr-iptvsimple,
kodi-pvr-mediaportal-tvserver, kodi-pvr-mythtv, kodi-pvr-nextpvr, kodi-pvr-njoy,
kodi-pvr-vdr-vnsi, kodi-pvr-vuplus, kodi-pvr-wmc, kodi-visualization-spectrum,
kodiplatform, nxt-python, python-lightblue, python-whiteboard, series60-remote
and xbmc-pvr-addons seem rather dispropotional.

-- 
Happy hacking
Petter Reinholdtsen

Processed: your mail

[Debian Bug Tracking System]

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

> forwarded 854130 https://jira.mongodb.org/browse/CDRIVER-2053
Bug #854130 [src:libbson] libbson FTBFS on mips/mipsel: test-results.json 
aborted
Set Bug forwarded-to-address to 'https://jira.mongodb.org/browse/CDRIVER-2053'.
>
End of message, stopping processing here.

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

Bug#831541: marked as done (theano: single GradientError and WrongValues in tests on s390x, ppc64 and sparc)

[Debian Bug Tracking System]

Your message dated Tue, 14 Feb 2017 23:34:06 +
with message-id 
and subject line Bug#831541: fixed in theano 0.8.2-6~exp1
has caused the Debian Bug report #831541,
regarding theano: single GradientError and WrongValues in tests on s390x, ppc64 
and sparc
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.)


-- 
831541: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831541
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: theano
Version: 0.8.2-2
Severity: normal

The tests on s390x came up with three single errors (shortened) [1]:


ERROR: test_grad (theano.sparse.tests.test_basic.SamplingDotTester)
--
GradientError: GradientError: numeric gradient and analytic gradient exceed 
tolerance:
At position 0 of argument 0,
abs. error = 4.801748,  abs. tolerance = 0.000100
rel. error = 1.00,  rel. tolerance = 0.000100
Exception args: 
The error happened with the following inputs:, [array([[ 4.,  2.,  2.],
   [ 0.,  1.,  3.],
   [ 1.,  0.,  0.],



ERROR: test_op (theano.sparse.tests.test_basic.SamplingDotTester)
--
WrongValue: WrongValue
   : shape, dtype, strides, min, max, n_inf, n_nan:
  Expected : (4, 5) float64 (40, 8) 0.0 28.0 0 0 
  Value: (4, 5) float64 (40, 8) 0.0 0.0 0 0 
  expected: [[ 28.   0.   0.   0.   0.]
 [ 12.   9.  11.   0.   0.]
 [  4.   1.   0.   2.   0.]
 [  0.   8.   0.   0.   0.]]



ERROR: test (theano.sparse.tests.test_basic.UsmmTests)
--
Traceback (most recent call last):
  File "/«PKGBUILDDIR»/theano/sparse/tests/test_basic.py", line 1458, in test
utt.assert_allclose(f_a_out, f_b_out, rtol=rtol, atol=atol)
  File "/«PKGBUILDDIR»/theano/tests/unittest_tools.py", line 339, in 
assert_allclose
raise WrongValue(val1, val2, rtol, atol)
WrongValue: WrongValue
   : shape, dtype, strides, min, max, n_inf, n_nan:
  Expected : (10, 200) float32 (800, 4) -0.999263 0.999721 0 0 
  Value: (10, 200) float32 (800, 4) -20.3578 20.3085 0 0 
  expected: [[ 0.43297213 -0.99617213 -0.94651264 ...,  0.90926737  
0.87269104
   0.18024164]


The same errors occurs on ppc64 [2].

This is a regression from 0.8.2-2 (0.8.2-1 was build with `FAST_COMPILE` and 
this didn't
came up then). dh_auto_test is temporarily failsafed, this is going to be 
removed when
this problem is solved.

Thanks,
DS

[1] 
https://buildd.debian.org/status/fetch.php?pkg=theano=s390x=0.8.2-2=1468619676

[2] 
https://buildd.debian.org/status/fetch.php?pkg=theano=ppc64=0.8.2-3=1468725341

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

Kernel: Linux 4.5.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: theano
Source-Version: 0.8.2-6~exp1

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

Debian distribution maintenance software
pp.
Daniel Stender  (supplier of updated theano package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 15 Feb 2017 00:08:13 +0100
Source: theano
Binary: python-theano python3-theano theano-doc
Architecture: source amd64 all
Version: 0.8.2-6~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Daniel Stender 
Description:
 python-theano - CPU/GPU math expression compiler for Python
 python3-theano - CPU/GPU math expression compiler for Python 3
 theano-doc - CPU/GPU math expression compiler for Python (docs)
Closes: 831541 835531 855102
Changes:
 theano (0.8.2-6~exp1) experimental; 

Bug#855175: add option to bypass security checks

[積丹尼 Dan Jacobson]

Package: flashplugin-nonfree
Version: 1:3.7
Severity: grave
File: /usr/sbin/update-flashplugin-nonfree

Please add an option to bypass


 downloadfile=fp.$upstream.sha512.i386.pgp.asc
[ `dpkg --print-architecture` != "amd64" ] || 
downloadfile=fp.$upstream.sha512.amd64.pg
p.asc

downloadurl=http://people.debian.org/~bartm/flashplugin-nonfree/D5C0FC14/$downloadfile

etc. security checks.

As the non-availability of that file might be worse that being stuck
with an outdated version of flash plugin. Thanks.

Processed: severity 835531

[Debian Bug Tracking System]

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

> severity 835531 important
Bug #835531 [src:theano] theano: fail of 
test_csr_correct_output_faster_than_scipy at times (FTBFS)
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Processed: Re: Processed (with 1 error):

[Debian Bug Tracking System]

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

> tags 855102 patch
Bug #855102 [theano] theano: SamplingDot broken on negative-stride arrays
Added tag(s) patch.
> tags 831541 patch
Bug #831541 [src:theano] theano: single GradientError and WrongValues in tests 
on s390x, ppc64 and sparc
Added tag(s) patch.
> tags 835531 patch
Bug #835531 [src:theano] theano: fail of 
test_csr_correct_output_faster_than_scipy at times (FTBFS)
Added tag(s) patch.
>
End of message, stopping processing here.

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

Bug#835531: theano: fail of test_csr_correct_output_faster_than_scipy at times (FTBFS)

[Rebecca N. Palmer]

I agree that failing a build for a timing test such as this is 
inherently unreliable...so let's turn it off.


(Tested only in sparse/tests/test_basic.py, not a full build.)

It may be that theano is slower because it's using a 
lowest-common-denominator BLAS while numpy does runtime processor 
detection, as recently discussed at
https://lists.debian.org/debian-science/2017/02/msg00043.html , but now 
is not the time to be fixing that.
Description: Disable overly environment-dependent test

Testing speed by wall-clock time is inherently unreliable on a
shared machine such as Debian's buildds:
don't let it fail the whole build.

Author: Rebecca N. Palmer 
Bug-Debian: https://bugs.debian.org/835531
Forwarded: not-needed

diff --git a/theano/sparse/tests/test_basic.py b/theano/sparse/tests/test_basic.py
index 8c183b9..03d79f1 100644
--- a/theano/sparse/tests/test_basic.py
+++ b/theano/sparse/tests/test_basic.py
@@ -1209,8 +1209,8 @@ class test_structureddot(unittest.TestCase):
 overhead_tol = 0.002  # seconds
 overhead_rtol = 1.1  # times as long
 utt.assert_allclose(scipy_result, theano_result)
-if (not theano.config.mode in ["DebugMode", "DEBUG_MODE"] and
-theano.config.cxx):
+
+if 0:#(not theano.config.mode in ["DebugMode", "DEBUG_MODE"] and theano.config.cxx):
 self.assertFalse(
 theano_time > overhead_rtol * scipy_time + overhead_tol,
 (theano_time,

Bug#853916: marked as done (encfs '-S' vulnerability)

[Debian Bug Tracking System]

Your message dated Tue, 14 Feb 2017 22:34:14 +
with message-id 
and subject line Bug#853916: fixed in encfs 1.9.1-4
has caused the Debian Bug report #853916,
regarding encfs '-S' vulnerability
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.)


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


Recently, a change in Encfs was found to have broken cryptkeeper, causing it
to use the password 'p' for all operations, regardless of user input 
(#852751)[3].
The bug was closed by removing cryptkeeper from Debian.

The issue, however, remains. Sirikali, which manages multiple userspace
filesystems including Encfs, suffers from the same failure (#853874).
An upstream Encfs representative has indicated that the problem will be fixed
there [1], though no change has been pushed to date [2].

The overall issue should be RC critical for Stretch. I've marked this as 
'serious',
indicating that the problem will be fixed in Encfs for the Stretch release. If 
this
is not the case, close or demote, and I'll elevate in Sirikali.

[1] https://github.com/tomm/cryptkeeper/issues/23#issuecomment-276304206
[2] https://github.com/vgough/encfs
[3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852751

-- 
AE0D BF5A 92A5 ADE4 9481  BA6F 8A31 71EF 3661 50CE


signature.asc
Description: GooPG digital signature
--- End Message ---
--- Begin Message ---
Source: encfs
Source-Version: 1.9.1-4

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

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

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

Debian distribution maintenance software
pp.
Eduard Bloch  (supplier of updated encfs package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 14 Feb 2017 23:03:28 +0100
Source: encfs
Binary: encfs
Architecture: source amd64
Version: 1.9.1-4
Distribution: unstable
Urgency: high
Maintainer: Eduard Bloch 
Changed-By: Eduard Bloch 
Description:
 encfs  - encrypted virtual filesystem
Closes: 853916
Changes:
 encfs (1.9.1-4) unstable; urgency=high
 .
   * Cherry-picked from upstream:
 + Replaced zero_pwd_segfault patch with another fix from upstream branch
   which forces a clean exit instead of a behavior that confused some encfs
   frontends (closes: #853916)
   (source: 5994b28542e7f551b71ac471ff9aacf6dcd5a3b0 / Jakob Unterwurzacher)
 + improve_example: safer command execution example with quotes ("$*")
   (source: ecc364df0d7269c65d2858039aaeaf27ea0e4da6 / Charles Duffy)
Checksums-Sha1:
 809ceab99b04273553c774e03bd0bb20cefa51f2 1947 encfs_1.9.1-4.dsc
 bb06917cb3461305dbb795c9ba15d0afa9164772 27260 encfs_1.9.1-4.debian.tar.xz
 036469491f6a1c31eaf84c28ba911cd2b9e47704 1571526 encfs-dbgsym_1.9.1-4_amd64.deb
 b6a67a4bd72e46d349456f9c212b4819c6120d98 7537 encfs_1.9.1-4_amd64.buildinfo
 5f624903608d327d98f75582418d8604da7126c4 380302 encfs_1.9.1-4_amd64.deb
Checksums-Sha256:
 5dac60af502409054f7a3ff2182901b27bc1b0af118e10b78a93335a0a622042 1947 
encfs_1.9.1-4.dsc
 06f85640e4e3745fbdf2cdd6f893c68eab790f03b97592b1442f51a04540cf53 27260 
encfs_1.9.1-4.debian.tar.xz
 2238efc928e9696832c77d67243b10631e15d47536a59bb6246a61ede4f948ce 1571526 
encfs-dbgsym_1.9.1-4_amd64.deb
 5e6a54061ba45a6d445c8a058a17f317e7bebbe44f62152f188427273b6412d3 7537 
encfs_1.9.1-4_amd64.buildinfo
 1f3621a5fa6d11fb95dc741850845628f8ab2b2aa9c010c251632650bd63c8e4 380302 
encfs_1.9.1-4_amd64.deb
Files:
 ad981af60537b9b27d4cef5c30d59c92 1947 utils optional encfs_1.9.1-4.dsc
 5c8127b4fcf56fdd9c68b6ed172e729a 27260 utils optional 
encfs_1.9.1-4.debian.tar.xz
 2b39d21a8abff78478140e4538c79b71 1571526 debug extra 
encfs-dbgsym_1.9.1-4_amd64.deb
 338d41bc6f6dffb738308ffcb003a603 7537 utils optional 
encfs_1.9.1-4_amd64.buildinfo
 55bf39352b20411f7506cd75adbaa8b7 380302 utils optional encfs_1.9.1-4_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEZI3Zj0vEgpAXyw40aXQOXLNf7DwFAlijgJgACgkQaXQOXLNf

Processed: Re: pybluez: Compile for Python 3.x

[Debian Bug Tracking System]

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

> tags 787850 patch
Bug #787850 [src:pybluez] pybluez: Compile for Python 3.x
Added tag(s) patch.
> block 787850 by 839100
Bug #787850 [src:pybluez] pybluez: Compile for Python 3.x
787850 was not blocked by any bugs.
787850 was not blocking any bugs.
Added blocking bug(s) of 787850: 839100
>
End of message, stopping processing here.

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

Bug#855163: [debian-mysql] Bug#855163: Missing mariadb-plugin-tokudb binary package on amd64

[James Clarke]

Control: reassign -1 release.debian.org
Control: user release.debian@packages.debian.org
Control: usertags -1 binnmu
Control: severity -1 normal
Control: retitle -1 nmu: mariadb-10.1_10.1.21-5

On 14 Feb 2017, at 22:00, Otto Kekäläinen  wrote:
>> 2017-02-14 23:58 GMT+02:00 James Clarke :
>>> On 14 Feb 2017, at 21:54, Otto Kekäläinen  wrote:
>>> 
>>> So you suggest I upload 10.1.21-6 and go though all the hassle of
>>> filing unblocks etc? Is there no possibility to trigger a rebuild on
>>> amd64 with the current source package?
>> 
>> I don't know which is preferred, just that both solve the problem.
> 
> I would prefer somebody would just trigger the rebuild on amd64. There
> is no need to fill the archives with an indentical upload.

I thought the NEW-ness might introduce issues, but apparently not.

nmu mariadb-10.1_10.1.21-5 . amd64 . -m "Rebuild to build missing 
mariadb-plugin-tokudb."

Regards,
James

Bug#831541: (no subject)

[Rebecca N. Palmer]

Control: tags -1 patch
(Combined patch for both bugs as the changes are so close together, but 
you *can* do the obvious split if you only want to fix one.)


This has been tested only by running sparse/test_basic.py and #855102's 
example from the source tree, *not* a full build.  This confirms that it 
does fix #855102, but I can't test for #831541 (due to several qemu 
bugs).  The syntax for running a single test is nosetests3 -v 
'/path/to/theano/theano/sparse/tests/test_basic.py':SamplingDotTester.test_op


I intend to send this upstream tomorrow.
Description: Fix invalid casts and negative stride handling

Cast values, not pointers, from int64 to int32.

Remember that first-in-index order (numpy) and
first-in-memory-order (BLAS) are not always the same thing.

Bump c_code_cache_version to make sure existing installs use the fixes.

Author: Rebecca N. Palmer 
Bug-Debian: https://bugs.debian.org/855102 https://bugs.debian.org/831541
Forwarded: not yet

diff --git a/theano/sparse/opt.py b/theano/sparse/opt.py
index 6100405..d1c2b54 100644
--- a/theano/sparse/opt.py
+++ b/theano/sparse/opt.py
@@ -829,7 +829,11 @@ class UsmmCscDense(gof.Op):
 npy_intp Sind = PyArray_STRIDES(%(x_ind)s)[0] / PyArray_DESCR(%(x_ind)s)->elsize;
 npy_intp Sptr = PyArray_STRIDES(%(x_ptr)s)[0] / PyArray_DESCR(%(x_ptr)s)->elsize;
 npy_intp Sy = PyArray_STRIDES(%(y)s)[1] / PyArray_DESCR(%(y)s)->elsize;
-
+
+// blas expects ints; convert here (rather than just making N etc ints) to avoid potential overflow in the negative-stride correction
+int N32 = N;
+int Sy32 = Sy;
+int Szn32 = Szn;
 
 if (!(%(inplace)s))
 {
@@ -859,7 +863,7 @@ class UsmmCscDense(gof.Op):
 if (Szn < 0)
 z_row += (N - 1) * Szn;
 
-%(axpy)s((int*), (%(conv_type)s*), (%(conv_type)s*)y_row, (int*), (%(conv_type)s*)z_row, (int*));
+%(axpy)s(, (%(conv_type)s*), (%(conv_type)s*)y_row, , (%(conv_type)s*)z_row, );
 }
 }
 }
@@ -868,7 +872,7 @@ class UsmmCscDense(gof.Op):
 return rval
 
 def c_code_cache_version(self):
-return (1, blas.blas_header_version())
+return (1, blas.blas_header_version(), 0xdeb1a)
 usmm_csc_dense = UsmmCscDense(inplace=False)
 usmm_csc_dense_inplace = UsmmCscDense(inplace=True)
 
@@ -1748,7 +1752,7 @@ class SamplingDotCSR(gof.Op):
 ])
 
 def c_code_cache_version(self):
-return (2, blas.blas_header_version())
+return (2, blas.blas_header_version(), 0xdeb1a)
 
 def c_support_code(self):
 return blas.blas_header_text()
@@ -1891,6 +1895,11 @@ PyErr_SetString(PyExc_NotImplementedError, "rank(y) != 2"); %(fail)s;}
 memcpy(Dzi, Dpi, PyArray_DIMS(%(p_ind)s)[0]*sizeof(dtype_%(p_ind)s));
 memcpy(Dzp, Dpp, PyArray_DIMS(%(p_ptr)s)[0]*sizeof(dtype_%(p_ptr)s));
 
+// blas expects ints; convert here (rather than just making K etc ints) to avoid potential overflow in the negative-stride correction
+int K32 = K;
+int Sdx32 = Sdx;
+int Sdy32 = Sdy;
+
 for (npy_int32 m = 0; m < M; ++m) {
 for (npy_int32 n_idx = Dpp[m * Sdpp]; n_idx < Dpp[(m+1)*Sdpp]; ++n_idx) {
 const npy_int32 n = Dpi[n_idx * Sdpi]; // row index of non-null value for column K
@@ -1898,8 +1907,15 @@ PyErr_SetString(PyExc_NotImplementedError, "rank(y) != 2"); %(fail)s;}
 const dtype_%(x)s* x_row = (dtype_%(x)s*)(PyArray_BYTES(%(x)s) + PyArray_STRIDES(%(x)s)[0] * m);
 
 const dtype_%(y)s* y_col = (dtype_%(y)s*)(PyArray_BYTES(%(y)s) + PyArray_STRIDES(%(y)s)[0] * n);
+// dot expects pointer to the beginning of memory arrays,
+// so when the stride is negative, we need to get the
+// last element
+if (Sdx < 0)
+x_row += (K - 1) * Sdx;
+if (Sdy < 0)
+y_col += (K - 1) * Sdy;
 
-Dzd[n_idx * Sdzd] = Dpd[n_idx * Sdpd] * %(cdot)s((int*), (const %(conv_type)s*)x_row, (int*), (const %(conv_type)s*)y_col, (int*));
+Dzd[n_idx * Sdzd] = Dpd[n_idx * Sdpd] * %(cdot)s(, (const %(conv_type)s*)x_row, , (const %(conv_type)s*)y_col, );
 }
 }
 }
diff --git a/theano/sparse/tests/test_basic.py b/theano/sparse/tests/test_basic.py
index 8c183b9..03d79f1 100644
--- a/theano/sparse/tests/test_basic.py
+++ b/theano/sparse/tests/test_basic.py
@@ -3085,6 +3085,20 @@ class SamplingDotTester(utt.InferShapeTester):
 assert tested.format == 'csr'
 assert tested.dtype == expected.dtype
 
+def test_negative_stride(self):
+f = theano.function(
+self.x,
+sampling_dot(*self.x))
+
+

Processed (with 2 errors): Re: [debian-mysql] Bug#855163: Missing mariadb-plugin-tokudb binary package on amd64

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 release.debian.org
Bug #855163 [src:mariadb-10.1] Missing mariadb-plugin-tokudb binary package on 
amd64
Bug reassigned from package 'src:mariadb-10.1' to 'release.debian.org'.
No longer marked as found in versions mariadb-10.1/10.1.21-5.
Ignoring request to alter fixed versions of bug #855163 to the same values 
previously set
> user release.debian@packages.debian.org
Unknown command or malformed arguments to command.

> usertags -1 binnmu
Unknown command or malformed arguments to command.

> severity -1 normal
Bug #855163 [release.debian.org] Missing mariadb-plugin-tokudb binary package 
on amd64
Severity set to 'normal' from 'serious'
> retitle -1 nmu: mariadb-10.1_10.1.21-5
Bug #855163 [release.debian.org] Missing mariadb-plugin-tokudb binary package 
on amd64
Changed Bug title to 'nmu: mariadb-10.1_10.1.21-5' from 'Missing 
mariadb-plugin-tokudb binary package on amd64'.

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

Processed: Re: python-bluez: debian pybluez package version 0.22-1 uses upstream source code version 0.18

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #839100 [python-bluez] python-bluez: debian pybluez package version 0.22-1 
uses upstream source code version 0.18
Severity set to 'serious' from 'normal'
> found -1 0.20-1
Bug #839100 [python-bluez] python-bluez: debian pybluez package version 0.22-1 
uses upstream source code version 0.18
Marked as found in versions pybluez/0.20-1.

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

Bug#855163: [debian-mysql] Bug#855163: Missing mariadb-plugin-tokudb binary package on amd64

[Otto Kekäläinen]

2017-02-14 23:58 GMT+02:00 James Clarke :
>> On 14 Feb 2017, at 21:54, Otto Kekäläinen  wrote:
>>
>> So you suggest I upload 10.1.21-6 and go though all the hassle of
>> filing unblocks etc? Is there no possibility to trigger a rebuild on
>> amd64 with the current source package?
>
> I don't know which is preferred, just that both solve the problem.

I would prefer somebody would just trigger the rebuild on amd64. There
is no need to fill the archives with an indentical upload.

Bug#855163: [debian-mysql] Bug#855163: Missing mariadb-plugin-tokudb binary package on amd64

[James Clarke]

> On 14 Feb 2017, at 21:54, Otto Kekäläinen  wrote:
> 
> So you suggest I upload 10.1.21-6 and go though all the hassle of
> filing unblocks etc? Is there no possibility to trigger a rebuild on
> amd64 with the current source package?

I don't know which is preferred, just that both solve the problem.

James

Bug#855163: [debian-mysql] Bug#855163: Missing mariadb-plugin-tokudb binary package on amd64

[Otto Kekäläinen]

So you suggest I upload 10.1.21-6 and go though all the hassle of
filing unblocks etc? Is there no possibility to trigger a rebuild on
amd64 with the current source package?

Bug#855168: olvwm crashes traying to log in X

[Awtul]

Package: olvwm
Version: 4.4.3.2p1.4-28.2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Olvwm crashes trying to log in X, using startx or wdm. No trace of it in 
xsession-errors/Xorg logs.

I only found the following in /var/log/syslog and journalctl:

- syslog: kernel: [  151.441615] olvwm[1112]: segfault at 44c51dd0 ip 
55634411d3ed sp 7ffc19538b50 error 6 in olvwm[556344107000+62000]

- journalctl: kernel: olvwm[1112]: segfault at 44c51dd0 ip 55634411d3ed sp 
7ffc19538b50 error 6 in olvwm[556344107000+62000]

Note that I'm not an olwm user; no clue on how to debug it.

Cheers,

Awtul

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

Kernel: Linux 4.9.0-1-amd64 (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 olvwm depends on:
ii  libc6 2.24-9
ii  libx11-6  2:1.6.4-3
ii  libxext6  2:1.3.3-1
ii  libxpm4   1:3.5.12-1

olvwm recommends no packages.

Versions of packages olvwm suggests:
ii  menu   2.1.47
ii  olwm   3.2p1.4-28.2
pn  xview-clients  

-- no debconf information

Bug#855167: olwm crashes trying to log in X

[Awtul]

Package: olwm
Version: 3.2p1.4-28.2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

Olwm crashes trying to log in X, using startx or wdm. No trace of it in 
xsession-errors/Xorg logs.

I only found the following in /var/log/syslog and journalctl:

- syslog: kernel: [ 1548.393919] olwm[7906]: segfault at 1fe16138 ip 
7f1e6f4234c7 sp 7fff3bf47f10 error 4 in 
libX11.so.6.3.0[7f1e6f394000+13a000]

- journalctl: kernel: olwm[983]: segfault at 82233138 ip 7f64327a84c7 sp 
7ffe9cd18a80 error 4 in libX11.so.6.3.0[7f6432719000+13a000]

Note that I'm not an olwm user; no clue on how to debug it.

Cheers,

Awtul



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

Kernel: Linux 4.9.0-1-amd64 (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 olwm depends on:
ii  libc6 2.24-9
ii  libx11-6  2:1.6.4-3
ii  libxext6  2:1.3.3-1
ii  xviewg3.2p1.4-28.2

olwm recommends no packages.

Versions of packages olwm suggests:
ii  menu   2.1.47
pn  xview-clients  

-- no debconf information

Bug#848729: It is grave

[Nis Martensen]

Hi Ondřej,

Ondřej Surý wrote:
> As this bug is preventing me from filling any bugs at all and it fails
> only after I press "Y", so the content of the lengthy unblock bug is
> gone...  and this puts my laptop in danger of my rage :).
> 
> Traceback (most recent call last):
>   File "/usr/bin/reportbug", line 2234, in 
> main()
>   File "/usr/bin/reportbug", line 1107, in main
> return iface.user_interface()
>   File "/usr/bin/reportbug", line 2225, in user_interface
> self.options.envelopefrom)
>   File "/usr/lib/python3/dist-packages/reportbug/submit.py", line 209,
>   in send_report
> (message, failed) = mime_attach(body, attachments, charset,
> body_charset)
>   File "/usr/lib/python3/dist-packages/reportbug/submit.py", line 157,
>   in mime_attach
> part = MIMEText(fp.read())
>   File "/usr/lib/python3.5/codecs.py", line 321, in decode
> (result, consumed) = self._buffer_decode(data, self.errors, final)
> UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe5 in position
> 296505: invalid continuation byte
> 
> and my locale is:
> 
> $ locale
> LANG=en_DK.UTF-8

Your Traceback is different from the others. This bug is not fixed yet.

Did you try to attach a text(plain/html/etc) file in a different
encoding than UTF-8? As a workaround, you could gzip that file.

Attached a patch that should fix the problem.
>From 0566a9cec6c9bd561db0128a58c84b9db0a5d1c4 Mon Sep 17 00:00:00 2001
From: Nis Martensen 
Date: Tue, 14 Feb 2017 22:21:29 +0100
Subject: [PATCH] Handle text attachments in different encodings

---
 reportbug/submit.py | 12 +---
 1 file changed, 9 insertions(+), 3 deletions(-)

diff --git a/reportbug/submit.py b/reportbug/submit.py
index 5cc1231..b3025b3 100644
--- a/reportbug/submit.py
+++ b/reportbug/submit.py
@@ -153,9 +153,15 @@ def mime_attach(body, attachments, charset, body_charset=None):
 
 maintype, subtype = ctype.split('/', 1)
 if maintype == 'text':
-fp = open(attachment, 'rU')
-part = MIMEText(fp.read())
-fp.close()
+try:
+with open(attachment, 'rU') as fp:
+part = MIMEText(fp.read())
+except UnicodeDecodeError:
+fp = open(attachment, 'rb')
+part = MIMEBase(maintype, subtype)
+part.set_payload(fp.read())
+fp.close()
+email.encoders.encode_base64(part)
 elif maintype == 'message':
 fp = open(attachment, 'rb')
 part = MIMEMessage(email.message_from_file(fp),
-- 
2.1.4

Bug#855166: pyrit FTBFS on i386: testAttackBatch memory corruption

[Adrian Bunk]

Source: pyrit
Version: 0.4.0-7.1
Severity: serious

https://buildd.debian.org/status/logs.php?pkg=pyrit=i386

...
make[1]: Entering directory '/«PKGBUILDDIR»'
PYBUILD_SYSTEM=custom \
PYBUILD_TEST_ARGS="cd /«PKGBUILDDIR»/test/ && {interpreter} test_pyrit.py" \
PYRIT_CONFIG_FILE="/«PKGBUILDDIR»/debian/config.build" \
dh_auto_test
I: pybuild base:184: cd /«PKGBUILDDIR»/test/ && python2.7 test_pyrit.py
testAnalyze (__main__.FilesystemTestCase) ... ok
testAttackBatch (__main__.FilesystemTestCase) ... *** Error in `python2.7': 
malloc(): memory corruption: 0xf80a6cb0 ***
=== Backtrace: =
/lib/i386-linux-gnu/libc.so.6(+0x6737a)[0xf71bc37a]
/lib/i386-linux-gnu/libc.so.6(+0x6dfb7)[0xf71c2fb7]
/lib/i386-linux-gnu/libc.so.6(+0x6fe52)[0xf71c4e52]
/lib/i386-linux-gnu/libc.so.6(__libc_malloc+0xc5)[0xf71c6a25]
python2.7(+0x1aa9e3)[0xf757b9e3]
python2.7(PyEval_EvalFrameEx+0x591)[0xf74a77e1]
python2.7(PyEval_EvalFrameEx+0x58dd)[0xf74acb2d]
python2.7(PyEval_EvalCodeEx+0x1fb)[0xf74a5acb]
python2.7(+0xf0b62)[0xf74c1b62]
python2.7(PyObject_Call+0x49)[0xf7494d69]
python2.7(+0x1073f5)[0xf74d83f5]
python2.7(PyObject_Call+0x49)[0xf7494d69]
python2.7(+0x106bbe)[0xf74d7bbe]
python2.7(+0xc9287)[0xf749a287]
python2.7(PyObject_Call+0x49)[0xf7494d69]
python2.7(PyEval_EvalFrameEx+0x5bc1)[0xf74ace11]
python2.7(PyEval_EvalCodeEx+0x1fb)[0xf74a5acb]
python2.7(+0xf0b62)[0xf74c1b62]
python2.7(PyObject_Call+0x49)[0xf7494d69]
python2.7(+0x1073f5)[0xf74d83f5]
python2.7(PyObject_Call+0x49)[0xf7494d69]
python2.7(+0x106bbe)[0xf74d7bbe]
python2.7(+0xc9287)[0xf749a287]
python2.7(PyObject_Call+0x49)[0xf7494d69]
python2.7(PyEval_EvalFrameEx+0x5bc1)[0xf74ace11]
python2.7(PyEval_EvalCodeEx+0x1fb)[0xf74a5acb]
python2.7(+0xf0d4e)[0xf74c1d4e]
python2.7(PyObject_Call+0x49)[0xf7494d69]
python2.7(PyEval_EvalFrameEx+0x3122)[0xf74aa372]
python2.7(PyEval_EvalCodeEx+0x1fb)[0xf74a5acb]
python2.7(PyEval_EvalFrameEx+0x62cf)[0xf74ad51f]
python2.7(PyEval_EvalCodeEx+0x1fb)[0xf74a5acb]
python2.7(+0xf0d4e)[0xf74c1d4e]
python2.7(PyObject_Call+0x49)[0xf7494d69]
python2.7(PyEval_EvalFrameEx+0x3122)[0xf74aa372]
python2.7(PyEval_EvalCodeEx+0x1fb)[0xf74a5acb]
python2.7(PyEval_EvalFrameEx+0x62cf)[0xf74ad51f]
python2.7(PyEval_EvalCodeEx+0x1fb)[0xf74a5acb]
python2.7(+0xf0d4e)[0xf74c1d4e]
python2.7(PyObject_Call+0x49)[0xf7494d69]
python2.7(PyEval_EvalFrameEx+0x3122)[0xf74aa372]
python2.7(PyEval_EvalCodeEx+0x1fb)[0xf74a5acb]
python2.7(+0xf0b62)[0xf74c1b62]
python2.7(PyObject_Call+0x49)[0xf7494d69]
python2.7(+0x1073f5)[0xf74d83f5]
python2.7(PyObject_Call+0x49)[0xf7494d69]
python2.7(+0x1672be)[0xf75382be]
python2.7(PyObject_Call+0x49)[0xf7494d69]
python2.7(PyEval_EvalFrameEx+0x5bc1)[0xf74ace11]
python2.7(PyEval_EvalCodeEx+0x1fb)[0xf74a5acb]
python2.7(+0xf0d4e)[0xf74c1d4e]
python2.7(PyObject_Call+0x49)[0xf7494d69]
python2.7(PyEval_EvalFrameEx+0x3122)[0xf74aa372]
python2.7(PyEval_EvalCodeEx+0x1fb)[0xf74a5acb]
python2.7(+0xf0b62)[0xf74c1b62]
python2.7(PyObject_Call+0x49)[0xf7494d69]
python2.7(+0x1073f5)[0xf74d83f5]
python2.7(PyObject_Call+0x49)[0xf7494d69]
python2.7(+0x1672be)[0xf75382be]
python2.7(PyObject_Call+0x49)[0xf7494d69]
python2.7(PyEval_EvalFrameEx+0x5bc1)[0xf74ace11]
python2.7(PyEval_EvalFrameEx+0x58dd)[0xf74acb2d]
python2.7(PyEval_EvalCodeEx+0x1fb)[0xf74a5acb]
=== Memory map: 
f5a0-f5a21000 rw-p  00:00 0 
f5a21000-f5b0 ---p  00:00 0 
f5b6f000-f5b8b000 r-xp  00:1f 127408775  
/lib/i386-linux-gnu/libgcc_s.so.1
f5b8b000-f5b8c000 r--p 0001b000 00:1f 127408775  
/lib/i386-linux-gnu/libgcc_s.so.1
f5b8c000-f5b8d000 rw-p 0001c000 00:1f 127408775  
/lib/i386-linux-gnu/libgcc_s.so.1
f5b8d000-f5b8e000 ---p  00:00 0 
f5b8e000-f658e000 rw-p  00:00 0 
f658e000-f660e000 rw-p  00:00 0 
f660e000-f6651000 r-xp  00:1f 127432055  
/usr/lib/i386-linux-gnu/libpcap.so.1.8.1
f6651000-f6652000 ---p 00043000 00:1f 127432055  
/usr/lib/i386-linux-gnu/libpcap.so.1.8.1
f6652000-f6653000 r--p 00043000 00:1f 127432055  
/usr/lib/i386-linux-gnu/libpcap.so.1.8.1
f6653000-f6654000 rw-p 00044000 00:1f 127432055  
/usr/lib/i386-linux-gnu/libpcap.so.1.8.1
f6654000-f69d4000 rw-p  00:00 0 
f69d8000-f69fa000 r-xp  00:1f 127428819  
/usr/lib/python2.7/lib-dynload/_ctypes.i386-linux-gnu.so
f69fa000-f69fb000 r--p 00021000 00:1f 127428819  
/usr/lib/python2.7/lib-dynload/_ctypes.i386-linux-gnu.so
f69fb000-f69fe000 rw-p 00022000 00:1f 127428819  
/usr/lib/python2.7/lib-dynload/_ctypes.i386-linux-gnu.so
f69fe000-f6a7e000 rw-p  00:00 0 
f6a93000-f6a97000 r-xp  00:1f 127408697  
/lib/i386-linux-gnu/libuuid.so.1.3.0
f6a97000-f6a98000 r--p 3000 00:1f 127408697  
/lib/i386-linux-gnu/libuuid.so.1.3.0
f6a98000-f6a99000 rw-p 

Bug#855163: Missing mariadb-plugin-tokudb binary package on amd64

[James Clarke]

Source: mariadb-10.1
Version: 10.1.21-5
Severity: serious

As can be seen in the discussion for #852709, the source+amd64 upload
for 10.1.21-5 did not include mariadb-plugin-tokudb, despite the
package's architecture being base-any-any-amd64. Either a binNMU or a
new source upload is needed (a test rebuild on barriere worked).

Regards,
James

Processed: transgui: diff for NMU version 5.0.1-4.1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch pending
Bug #839863 [transgui] transgui: Bad libssl dependency
Added tag(s) pending.

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

Processed: transgui: diff for NMU version 5.0.1-4.1

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch pending
Bug #855007 [transgui] transgui: build and use libssl 1.0.2
Added tag(s) pending and patch.

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

Bug#839863: transgui: diff for NMU version 5.0.1-4.1

[Sebastian Andrzej Siewior]

Control: tags -1 patch pending

Dear maintainer,

I've prepared an NMU for transgui (versioned as 5.0.1-4.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer. I will reschedule on my own until the release
teams unblocks this version for testing.

Regards.
Sebastian
diff -Nru transgui-5.0.1/debian/changelog transgui-5.0.1/debian/changelog
--- transgui-5.0.1/debian/changelog	2016-03-25 19:30:44.0 +0100
+++ transgui-5.0.1/debian/changelog	2017-02-14 21:12:57.0 +0100
@@ -1,3 +1,11 @@
+transgui (5.0.1-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Build-depend on libssl1.0-dev and load the 1.0.2 library
+(Closes: #855007, #839863).
+
+ -- Sebastian Andrzej Siewior   Tue, 14 Feb 2017 21:12:57 +0100
+
 transgui (5.0.1-4) unstable; urgency=medium
 
   * Remove error message when opening containing folder (Closes: #811289)
diff -Nru transgui-5.0.1/debian/control transgui-5.0.1/debian/control
--- transgui-5.0.1/debian/control	2016-03-25 19:30:44.0 +0100
+++ transgui-5.0.1/debian/control	2017-02-13 08:15:56.0 +0100
@@ -14,7 +14,7 @@
libgdk-pixbuf2.0-dev,
libgtk2.0-dev,
libpango1.0-dev,
-   libssl-dev,
+   libssl1.0-dev,
libx11-dev
 Standards-Version: 3.9.6
 Homepage: http://code.google.com/p/transmisson-remote-gui/
diff -Nru transgui-5.0.1/debian/files transgui-5.0.1/debian/files
--- transgui-5.0.1/debian/files	1970-01-01 01:00:00.0 +0100
+++ transgui-5.0.1/debian/files	2017-02-14 21:12:57.0 +0100
@@ -0,0 +1 @@
+transgui_5.0.1-4.1_source.buildinfo net optional
diff -Nru transgui-5.0.1/debian/patches/force_ssl1.0.2.patch transgui-5.0.1/debian/patches/force_ssl1.0.2.patch
--- transgui-5.0.1/debian/patches/force_ssl1.0.2.patch	1970-01-01 01:00:00.0 +0100
+++ transgui-5.0.1/debian/patches/force_ssl1.0.2.patch	2017-02-14 21:12:57.0 +0100
@@ -0,0 +1,17 @@
+---
+ rpc.pas |4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+--- a/rpc.pas
 b/rpc.pas
+@@ -585,8 +585,8 @@ procedure TRpc.InitSSL;
+ {$ifndef darwin}
+   procedure CheckOpenSSL;
+   const
+-OpenSSLVersions: array[1..2] of string =
+-  ('0.9.8', '1.0.0');
++OpenSSLVersions: array[1..3] of string =
++  ('1.0.2', '0.9.8', '1.0.0');
+   var
+ hLib1, hLib2: TLibHandle;
+ i: integer;
diff -Nru transgui-5.0.1/debian/patches/series transgui-5.0.1/debian/patches/series
--- transgui-5.0.1/debian/patches/series	2016-03-25 19:30:44.0 +0100
+++ transgui-5.0.1/debian/patches/series	2017-02-13 08:13:22.0 +0100
@@ -1 +1,2 @@
 fix.open.patch
+force_ssl1.0.2.patch

Bug#844943: python-bleach: FTBFS: Tests failures

[Scott Kitterman]

On Mon, 19 Dec 2016 20:54:02 +0530 Pirate Praveen  wrote:
...
> Seems python-html5lib was updated without checking reverse dependency
> compatibility  https://github.com/mozilla/bleach/issues/212
> 

Based on recent discussions in the upstream bugs, it looks like they are 
making some progress on this.  If they don't, I think the only option is to 
embed a copy of the older html5lib in bleach (not ideal, I know).

Scott K

Bug#854341: libchado-perl: FTBFS: The following enviroment variables not detected: CHADO_DB_USERNAME

[gregor herrmann]

On Tue, 14 Feb 2017 09:46:23 +, olivier sallou wrote:

> > I admit I have no idea how to fix this.  Help from people with
> > Perl background would be really appreciated.
> I just made a build attempt (1-31-3) with pbuilder, updated right before
> build, based on latest svn source and it built fine
> Onyl difference is make -j4 for you and make -j1 for me (automatic update
> by debhelper?)

Builds for me as well (both from svn and from the archive, both with
-j1 and -j4). cowbuilder sid amd64.

(BZW: svn seems to miss the tag for 1.31-3. Or my svn foo has
deteriorated too much.)
 
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: Leon Redbone: So Relax


signature.asc
Description: Digital Signature

Bug#824442: and conflict needs to be resolved

[Aurelien Jarno]

On 2017-02-11 05:44, Niels Thykier wrote:
> On Mon, 16 May 2016 03:12:51 +0100 Ben Hutchings 
> wrote:
> > Source: glibc
> > Version: 2.22-7
> > Severity: serious
> > 
> > (Continued from bug #822393.)
> > 
> > glibc's  should check whether  has already been
> > included and, if so, avoid making conflicting definitions.
> > 
> > Including the headers in the opposite order works since this change in
> > Linux 4.6:
> > https://git.kernel.org/linus/4a91cb61bb995e5571098188092e296192309c77
> > 
> > Ben.
> > 
> > -- 
> > Ben Hutchings
> > 73.46% of all statistics are made up.
> 
> Hi,
> 
> Any news on this bug?

Now that the change have been done on the kernel side, the bug is not
really visible anymore, so nobody really cared about this bug.

I'll see if I can come with a patch in the next days.

Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Bug#854647: marked as done (doc-linux-hr: Too outdated for being useful)

[Debian Bug Tracking System]

Your message dated Tue, 14 Feb 2017 19:27:25 +
with message-id 
and subject line Bug#855000: Removed package(s) from unstable
has caused the Debian Bug report #854647,
regarding doc-linux-hr: Too outdated for being useful
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.)


-- 
854647: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854647
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: doc-linux-hr
Version: 2416.1+nmu1
Severity: serious

I do not speak Croatian, but both from looking the contents
of the package and reading debian/copyright it is clear that
these are HOWTOs (several of them translations from English ones)
that date from 1995-2000.
--- End Message ---
--- Begin Message ---
Version: 2416.1+nmu1+rm

Dear submitter,

as the package doc-linux-hr 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/855000

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#817449: marked as done (epwutil: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Tue, 14 Feb 2017 19:22:33 +
with message-id 
and subject line Bug#854768: Removed package(s) from unstable
has caused the Debian Bug report #817449,
regarding epwutil: 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.)


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

Hi,

The package epwutil 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 ---
Version: 1.1-8.1+rm

Dear submitter,

as the package epwutil 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/854768

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#846696: marked as done (xserver-xorg-input-acecad: FTBFS: ../../src/acecad.c:494:9: error: implicit declaration of function 'RemoveEnabledDevice' [-Werror=implicit-function-declaration])

[Debian Bug Tracking System]

Your message dated Tue, 14 Feb 2017 19:23:03 +
with message-id 
and subject line Bug#854775: Removed package(s) from unstable
has caused the Debian Bug report #846696,
regarding xserver-xorg-input-acecad: FTBFS: ../../src/acecad.c:494:9: error: 
implicit declaration of function 'RemoveEnabledDevice' 
[-Werror=implicit-function-declaration]
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.)


-- 
846696: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846696
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xserver-xorg-input-acecad
Version: 1:1.5.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161202 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
> -I../../src -I..-fvisibility=hidden -I/usr/include/pixman-1 
> -I/usr/include/libdrm -I/usr/include/xorg -I/usr/include/X11/dri -Wall 
> -Wpointer-arith -Wmissing-declarations -Wformat=2 -Wstrict-prototypes 
> -Wmissing-prototypes -Wnested-externs -Wbad-function-cast 
> -Wold-style-definition -Wdeclaration-after-statement -Wunused -Wuninitialized 
> -Wshadow -Wmissing-noreturn -Wmissing-format-attribute -Wredundant-decls 
> -Wlogical-op -Werror=implicit -Werror=nonnull -Werror=init-self -Werror=main 
> -Werror=missing-braces -Werror=sequence-point -Werror=return-type 
> -Werror=trigraphs -Werror=array-bounds -Werror=write-strings -Werror=address 
> -Werror=int-to-pointer-cast -Werror=pointer-to-int-cast -fno-strict-aliasing 
> -g -O2 -c -o acecad.lo ../../src/acecad.c
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../src -I.. 
> -fvisibility=hidden -I/usr/include/pixman-1 -I/usr/include/libdrm 
> -I/usr/include/xorg -I/usr/include/X11/dri -Wall -Wpointer-arith 
> -Wmissing-declarations -Wformat=2 -Wstrict-prototypes -Wmissing-prototypes 
> -Wnested-externs -Wbad-function-cast -Wold-style-definition 
> -Wdeclaration-after-statement -Wunused -Wuninitialized -Wshadow 
> -Wmissing-noreturn -Wmissing-format-attribute -Wredundant-decls -Wlogical-op 
> -Werror=implicit -Werror=nonnull -Werror=init-self -Werror=main 
> -Werror=missing-braces -Werror=sequence-point -Werror=return-type 
> -Werror=trigraphs -Werror=array-bounds -Werror=write-strings -Werror=address 
> -Werror=int-to-pointer-cast -Werror=pointer-to-int-cast -fno-strict-aliasing 
> -g -O2 -c ../../src/acecad.c  -fPIC -DPIC -o .libs/acecad.o
> ../../src/acecad.c: In function 'AceCadAutoDevProbe':
> ../../src/acecad.c:228:22: warning: initialization discards 'const' qualifier 
> from pointer target type [-Wdiscarded-qualifiers]
>  char *ace_name = xf86FindOptionValue(local->options, "Name");
>   ^~~
> ../../src/acecad.c: In function 'AceCadPreInit':
> ../../src/acecad.c:394:7: warning: assignment discards 'const' qualifier from 
> pointer target type [-Wdiscarded-qualifiers]
>  s = xf86FindOptionValue(local->options, "Device");
>^
> ../../src/acecad.c:476:7: warning: assignment discards 'const' qualifier from 
> pointer target type [-Wdiscarded-qualifiers]
>  s = xf86FindOptionValue(local->options, "Mode");
>^
> ../../src/acecad.c:494:9: error: implicit declaration of function 
> 'RemoveEnabledDevice' [-Werror=implicit-function-declaration]
>  RemoveEnabledDevice (local->fd);
>  ^~~
> ../../src/acecad.c:494:9: warning: nested extern declaration of 
> 'RemoveEnabledDevice' [-Wnested-externs]
> At top level:
> ../../src/acecad.c:1075:1: warning: 'ReverseConvertProc' defined but not used 
> [-Wunused-function]
>  ReverseConvertProc (InputInfoPtr local,
>  ^~
> ../../src/acecad.c: In function 'USBReadInput':
> ../../src/acecad.c:1037:21: warning: 'report_y' may be used uninitialized in 
> this function [-Wmaybe-uninitialized]
>  xf86PostProximityEvent(local->dev, 0, 0, 3, report_x, 
> report_y, z);
>  
> ^~
> ../../src/acecad.c:1037:21: warning: 'report_x' may be used uninitialized in 
> this function [-Wmaybe-uninitialized]
> cc1: some warnings being treated as errors
> Makefile:458: recipe for target 'acecad.lo' failed
> make[3]: *** [acecad.lo] Error 1

The full build log is available from:
   
http://aws-logs.debian.net/2016/12/02/xserver-xorg-input-acecad_1.5.0-1_unstable.log

A list of current common 

Bug#842723: marked as done (python-pytils: FTBFS (failing tests))

[Debian Bug Tracking System]

Your message dated Tue, 14 Feb 2017 19:22:01 +
with message-id 
and subject line Bug#854767: Removed package(s) from unstable
has caused the Debian Bug report #842723,
regarding python-pytils: FTBFS (failing tests)
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.)


-- 
842723: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842723
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-pytils
Version: 0.3-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 --with python2,python3 build-indep --buildsystem=pybuild
dh: Compatibility levels before 9 are deprecated (level 7 in use)
   dh_testdir -i -O--buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
dh_auto_configure: Compatibility levels before 9 are deprecated (level 7 in use)
I: pybuild base:184: python2.7 setup.py config 
running config
I: pybuild base:184: python3.5 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
dh_auto_build: Compatibility levels before 9 are deprecated (level 7 in use)

[... snipped ...]

  File "/<>/pytils/test/test_dt.py", line 182, in 
testDOTIWDefaultToTimeAcc1
self.ckDefaultToTime("2day_ago", 1, u"позавчера")
  File "/<>/pytils/test/test_dt.py", line 95, in ckDefaultToTime
self.assertEquals(res, estimated)
AssertionError: u'\u0432\u0447\u0435\u0440\u0430' != 
u'\u043f\u043e\u0437\u0430\u0432\u0447\u0435\u0440\u0430'
- \u0432\u0447\u0435\u0440\u0430
+ \u043f\u043e\u0437\u0430\u0432\u0447\u0435\u0440\u0430
? 


==
FAIL: testDOTIWDefaultToTimeAcc2 
(pytils.test.test_dt.DistanceOfTimeInWordsTestCase)
--
Traceback (most recent call last):
  File "/<>/pytils/test/test_dt.py", line 211, in 
testDOTIWDefaultToTimeAcc2
self.ckDefaultToTime("2day_ago", 2, u"позавчера")
  File "/<>/pytils/test/test_dt.py", line 95, in ckDefaultToTime
self.assertEquals(res, estimated)
AssertionError: u'1 \u0434\u0435\u043d\u044c 23 \u0447\u0430\u0441\u0430 
\u043d\u0430\u0437\u043 [truncated]... != 
u'\u043f\u043e\u0437\u0430\u0432\u0447\u0435\u0440\u0430'
- 1 \u0434\u0435\u043d\u044c 23 \u0447\u0430\u0441\u0430 
\u043d\u0430\u0437\u0430\u0434
+ \u043f\u043e\u0437\u0430\u0432\u0447\u0435\u0440\u0430


==
FAIL: testDOTIWDefaultToTimeAcc3 
(pytils.test.test_dt.DistanceOfTimeInWordsTestCase)
--
Traceback (most recent call last):
  File "/<>/pytils/test/test_dt.py", line 243, in 
testDOTIWDefaultToTimeAcc3
u"2 дня 0 часов 40 минут назад")
  File "/<>/pytils/test/test_dt.py", line 95, in ckDefaultToTime
self.assertEquals(res, estimated)
AssertionError: u'1 \u0434\u0435\u043d\u044c 23 \u0447\u0430\u0441\u0430 40 
\u043c\u0438\u043d\u [truncated]... != u'2 \u0434\u043d\u044f 0 
\u0447\u0430\u0441\u043e\u0432 40 \u043c\u0438\u043d\u0 [truncated]...
- 1 \u0434\u0435\u043d\u044c 23 \u0447\u0430\u0441\u0430 40 
\u043c\u0438\u043d\u0443\u0442 \u043d\u0430\u0437\u0430\u0434
? ^  - ^
+ 2 \u0434\u043d\u044f 0 \u0447\u0430\u0441\u043e\u0432 40 
\u043c\u0438\u043d\u0443\u0442 \u043d\u0430\u0437\u0430\u0434
? ^   ^^^^^


--
Ran 71 tests in 0.039s

FAILED (failures=5)
E: pybuild pybuild:276: test: plugin distutils failed with: exit code=1: 
python2.7 setup.py test 
dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
debian/rules:4: recipe for target 'build-indep' failed
make: *** [build-indep] Error 25
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The relevant part of the build log is included above.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

If you could not reproduce this using sbuild on a single CPU virtual machine 
(as I did),
please do not downgrade or mark as unreproducible, I would then consider giving 
you 

Bug#817732: marked as done (xipmsg: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Tue, 14 Feb 2017 19:20:51 +
with message-id 
and subject line Bug#854765: Removed package(s) from unstable
has caused the Debian Bug report #817732,
regarding xipmsg: 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.)


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

Hi,

The package xipmsg 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 ---
Version: 0.8088-2.1+rm

Dear submitter,

as the package xipmsg 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/854765

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#836979: marked as done (episoder: non-DFSG files found)

[Debian Bug Tracking System]

Your message dated Tue, 14 Feb 2017 19:21:26 +
with message-id 
and subject line Bug#854766: Removed package(s) from unstable
has caused the Debian Bug report #836979,
regarding episoder: non-DFSG files found
to be marked as done.

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

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


-- 
836979: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836979
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: episoder
Version: 0.7.1
Severity: serious
Tags: upstream
Justification: Policy 2.2.1

Dear Maintainer,

Several files in episoder have the following text:

---
This guide may be distributed and copied freely, in its entirety, for personal
use. All original author and copyright information must remain intact. Any
sales or other uses of this document are expressly forbidden, without the
specific consent of the author(s).
---

Up to 0.7.2 version, the text can be found in files inside test/testdata/
directory.

In 0.7.3 version (not in Debian)[1], the text can be found in files inside
test/fixtures/ directory.

[1] https://github.com/cockroach/episoder

Regards,

Eriberto
--- End Message ---
--- Begin Message ---
Version: 0.7.1-2+rm

Dear submitter,

as the package episoder 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/854766

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#817381: marked as done (bookview: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Tue, 14 Feb 2017 19:20:08 +
with message-id 
and subject line Bug#854764: Removed package(s) from unstable
has caused the Debian Bug report #817381,
regarding bookview: 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.)


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

Hi,

The package bookview 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 ---
Version: 3.2.1-1.1+rm

Dear submitter,

as the package bookview 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/854764

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#817633: marked as done (ptex-buildsupport: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Tue, 14 Feb 2017 19:19:14 +
with message-id 
and subject line Bug#854761: Removed package(s) from unstable
has caused the Debian Bug report #817633,
regarding ptex-buildsupport: 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.)


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

Hi,

The package ptex-buildsupport 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 ---
Version: 3.0-3+rm

Dear submitter,

as the package ptex-buildsupport 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/854761

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#713183: marked as done (pyg: FTBFS: make[4]: *** No rule to make target `/usr/lib/python2.7/config/Makefile', needed by `sedscript'. Stop.)

[Debian Bug Tracking System]

Your message dated Tue, 14 Feb 2017 19:18:14 +
with message-id 
and subject line Bug#854760: Removed package(s) from unstable
has caused the Debian Bug report #713183,
regarding pyg: FTBFS: make[4]: *** No rule to make target 
`/usr/lib/python2.7/config/Makefile', needed by `sedscript'.  Stop.
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.)


-- 
713183: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713183
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyg
Version: 0.9.8
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130620 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part:
> make[3]: Entering directory `/«PKGBUILDDIR»/wlp/module'
> rm -f *.o *~
> rm -f *.a tags TAGS config.c Makefile.pre python sedscript
> rm -f *.so *.sl so_locations
> VERSION=`python -c "import sys; print sys.version[:3]"`; \
>   installdir=`python -c "import sys; print sys.prefix"`; \
>   exec_installdir=`python -c "import sys; print sys.exec_prefix"`; \
>   /usr/bin/make -f ./Makefile.pre.in VPATH=. srcdir=. \
>   VERSION=$VERSION \
>   installdir=$installdir \
>   exec_installdir=$exec_installdir \
>   Makefile
> make[4]: Entering directory `/«PKGBUILDDIR»/wlp/module'
> make[4]: *** No rule to make target `/usr/lib/python2.7/config/Makefile', 
> needed by `sedscript'.  Stop.
> make[4]: Leaving directory `/«PKGBUILDDIR»/wlp/module'
> make[3]: *** [boot] Error 2

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/06/20/pyg_0.9.8_unstable.log

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

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

Dear submitter,

as the package pyg 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/854760

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#817579: marked as done (mendexk: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Tue, 14 Feb 2017 19:17:12 +
with message-id 
and subject line Bug#854759: Removed package(s) from unstable
has caused the Debian Bug report #817579,
regarding mendexk: 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.)


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

Hi,

The package mendexk 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 ---
Version: 2.6e-3.2+rm

Dear submitter,

as the package mendexk 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/854759

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#830449: marked as done (golang-rrd: FTBFS: ld: cannot find -lrrd_th)

[Debian Bug Tracking System]

Your message dated Tue, 14 Feb 2017 19:16:12 +
with message-id 
and subject line Bug#854756: Removed package(s) from unstable
has caused the Debian Bug report #830449,
regarding golang-rrd: FTBFS: ld: cannot find -lrrd_th
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.)


-- 
830449: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830449
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-rrd
Version: 0.0~git20131112-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160707 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> DC-Build-Header: golang-rrd 0.0~git20131112-1 / 2016-07-06 21:17:16 +
> DC-Task: source:golang-rrd version:0.0~git20131112-1 architecture:all 
> chroot:unstable esttime:80 
> logfile:/tmp/golang-rrd_0.0~git20131112-1_unstable_reb2.log modes:
> DC-Sbuild-call: su user -c 'sbuild -n -A -s --force-orig-source --apt-update 
> -d unstable -v  golang-rrd_0.0~git20131112-1'
> sbuild (Debian sbuild) 0.65.2 (24 Mar 2015) on 
> ip-172-31-7-140.eu-central-1.compute.internal
> 
> ╔══╗
> ║ golang-rrd 0.0~git20131112-1 (amd64)   06 Jul 2016 
> 21:17 ║
> ╚══╝
> 
> Package: golang-rrd
> Version: 0.0~git20131112-1
> Source Version: 0.0~git20131112-1
> Distribution: unstable
> Machine Architecture: amd64
> Host Architecture: amd64
> Build Architecture: amd64
> 
> I: NOTICE: Log filtering will replace 
> 'build/golang-rrd-v82_qv/golang-rrd-0.0~git20131112' with '«PKGBUILDDIR»'
> I: NOTICE: Log filtering will replace 'build/golang-rrd-v82_qv' with 
> '«BUILDDIR»'
> I: NOTICE: Log filtering will replace 
> 'var/lib/schroot/mount/unstable-amd64-sbuild-9b32addd-b680-4c47-8105-e7381eb380f1'
>  with '«CHROOT»'
> 
> ┌──┐
> │ Update chroot   
>  │
> └──┘
> 
> Get:1 http://127.0.0.1:/debian unstable InRelease [209 kB]
> Get:2 http://127.0.0.1:/debian unstable/main Sources.diff/Index [27.9 kB]
> Get:3 http://127.0.0.1:/debian unstable/main amd64 Packages.diff/Index 
> [27.9 kB]
> Get:4 http://127.0.0.1:/debian unstable/main Translation-en.diff/Index 
> [27.9 kB]
> Get:5 http://127.0.0.1:/debian unstable/main Sources 
> 2016-07-06-1505.17.pdiff [7201 B]
> Get:6 http://127.0.0.1:/debian unstable/main amd64 Packages 
> 2016-07-06-1505.17.pdiff [9176 B]
> Get:5 http://127.0.0.1:/debian unstable/main Sources 
> 2016-07-06-1505.17.pdiff [7201 B]
> Get:6 http://127.0.0.1:/debian unstable/main amd64 Packages 
> 2016-07-06-1505.17.pdiff [9176 B]
> Get:7 http://127.0.0.1:/debian unstable/main Translation-en 
> 2016-07-06-1505.17.pdiff [866 B]
> Get:7 http://127.0.0.1:/debian unstable/main Translation-en 
> 2016-07-06-1505.17.pdiff [866 B]
> Fetched 310 kB in 1s (276 kB/s)
> Reading package lists...
> W: No sandbox user '_apt' on the system, can not drop privileges
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Calculating upgrade...
> The following packages will be upgraded:
>   dash linux-libc-dev
> 2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> Need to get 1252 kB of archives.
> After this operation, 2048 B of additional disk space will be used.
> Get:1 http://127.0.0.1:/debian unstable/main amd64 dash amd64 0.5.8-2.3 
> [108 kB]
> Get:2 http://127.0.0.1:/debian unstable/main amd64 linux-libc-dev amd64 
> 4.6.3-1 [1144 kB]
> debconf: delaying package configuration, since apt-utils is not installed
> Fetched 1252 kB in 0s (27.4 MB/s)
> (Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 11521 files and directories currently 

Bug#789834: marked as done (golang-doozer: FTBFS: cannot find package [..] goprotobuf/proto)

[Debian Bug Tracking System]

Your message dated Tue, 14 Feb 2017 19:16:42 +
with message-id 
and subject line Bug#854757: Removed package(s) from unstable
has caused the Debian Bug report #789834,
regarding golang-doozer: FTBFS: cannot find package [..] goprotobuf/proto
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.)


-- 
789834: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789834
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-doozer
Version: 0.0~git20130909-1
Severity: serious
Tags: sid stretch
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

 debian/rules build
src/github.com/4ad/doozer/conn.go:4:2: cannot find package 
"code.google.com/p/goprotobuf/proto" in any of:
/usr/lib/go/src/code.google.com/p/goprotobuf/proto (from $GOROOT)

/golang-doozer-0.0~git20130909/obj-x86_64-linux-gnu/src/code.google.com/p/goprotobuf/proto
 (from $GOPATH)
dh_auto_build: go install -v github.com/4ad/doozer 
github.com/4ad/doozer/cmd/doozer returned exit code 1
make: *** [build] Error 1


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

Kernel: Linux 3.19.0-21-generic (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Version: 0.0~git20130909-1+rm

Dear submitter,

as the package golang-doozer 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/854757

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#822044: marked as done (libsyncml: Build arch:all+arch:any but is missing build-{arch,indep} targets)

[Debian Bug Tracking System]

Your message dated Tue, 14 Feb 2017 19:15:21 +
with message-id 
and subject line Bug#854755: Removed package(s) from unstable
has caused the Debian Bug report #822044,
regarding libsyncml: Build arch:all+arch:any but is missing build-{arch,indep} 
targets
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.)


-- 
822044: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822044
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libsyncml
Severity: normal
Usertags: arch-all-and-any-missing-targets

Hi,

The package libsyncml builds an architecture independent *and* an
architecture dependent package, but does not have the (now mandatory)
"build-arch" and "build-indep" targets in debian/rules.

We would like to phase out the hacks in dpkg, which are currently
needed to ensure that libsyncml builds despite its lack of these
targets.

 * Please add build-arch and build-indep targets to libsyncml at
   your earliest convenience.
   - This can also be solved by using e.g. the "dh"-style rules.

 * The work around will be removed in the first dpkg upload after
   the 1st of June.  After that upload, libsyncml will FTBFS if
   this bug has not been fixed before then.

Thanks,

See also: https://lists.debian.org/debian-devel/2016/04/msg00023.html
--- End Message ---
--- Begin Message ---
Version: 0.5.4-2.3+rm

Dear submitter,

as the package libsyncml 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/854755

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#811300: marked as done (FTBFS: error: 'OBEX_TRANS_CUST' undeclared)

[Debian Bug Tracking System]

Your message dated Tue, 14 Feb 2017 19:15:21 +
with message-id 
and subject line Bug#854755: Removed package(s) from unstable
has caused the Debian Bug report #811300,
regarding FTBFS: error: 'OBEX_TRANS_CUST' undeclared
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.)


-- 
811300: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811300
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libsyncml
Version: 0.5.4-2.2
Severity: serious

libsyncml fails to build:

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> [ 34%] Building C object 
> libsyncml/CMakeFiles/syncml.dir/transports/obex_client.o
> cd /<>/build/libsyncml && /usr/bin/cc  -Dsyncml_EXPORTS 
> -I/<> -I/<>/build -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/libxml2 
> -I/usr/include/libsoup-2.4  -Wall -g -O2 -fPIC   -o 
> CMakeFiles/syncml.dir/transports/obex_client.o   -c 
> /<>/libsyncml/transports/obex_client.c
> /<>/libsyncml/transports/obex_client.c: In function 
> 'smlTransportObexClientSetConnectionType':
> /<>/libsyncml/transports/obex_client.c:719:32: error: 
> 'OBEX_TRANS_CUST' undeclared (first use in this function)
> env->obexhandle = OBEX_Init(OBEX_TRANS_CUST, smlTransportObexClientEvent, 
> 0); 
> ^
> /<>/libsyncml/transports/obex_client.c:719:32: note: each 
> undeclared identifier is reported only once for each function it appears in
> /<>/libsyncml/transports/obex_client.c:743:6: warning: 
> initialization from incompatible pointer type [-Wincompatible-pointer-types]
>   obex_cable_handleinput,
>   ^
> /<>/libsyncml/transports/obex_client.c:743:6: note: (near 
> initialization for 'cabletrans.write')
> /<>/libsyncml/transports/obex_client.c:744:6: warning: 
> initialization from incompatible pointer type [-Wincompatible-pointer-types]
>   env};
>   ^
> /<>/libsyncml/transports/obex_client.c:744:6: note: (near 
> initialization for 'cabletrans.handleinput')
> /<>/libsyncml/transports/obex_client.c: In function 
> 'smlTransportObexClientConnect':
> /<>/libsyncml/transports/obex_client.c:885:19: warning: implicit 
> declaration of function 'OBEX_FindInterfaces' 
> [-Wimplicit-function-declaration]
>obex_intf_cnt = OBEX_FindInterfaces(env->obexhandle, _intf);
>^
> libsyncml/CMakeFiles/syncml.dir/build.make:785: recipe for target 
> 'libsyncml/CMakeFiles/syncml.dir/transports/obex_client.o' failed
> make[3]: *** [libsyncml/CMakeFiles/syncml.dir/transports/obex_client.o] Error 
> 1

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Version: 0.5.4-2.3+rm

Dear submitter,

as the package libsyncml 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/854755

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#805948: marked as done (libsyncml: FTBFS when built with dpkg-buildpackage -A (no binary artifacts))

[Debian Bug Tracking System]

Your message dated Tue, 14 Feb 2017 19:15:21 +
with message-id 
and subject line Bug#854755: Removed package(s) from unstable
has caused the Debian Bug report #805948,
regarding libsyncml: FTBFS when built with dpkg-buildpackage -A (no binary 
artifacts)
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.)


-- 
805948: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805948
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libsyncml
Version: 0.5.4-2.2
User: sanv...@debian.org
Usertags: binary-indep
Severity: important

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(i.e. only architecture-independent packages), and it failed:


[...]
 fakeroot debian/rules binary-indep
dh_testdir
dh_testroot
dh_prep
dh_installdirs
/usr/bin/make -C /<>/build install 
DESTDIR=/<>/debian/tmp

[ ... snipped ... ]

-- Installing: /<>/debian/tmp/usr/bin/syncml-ds-tool
make[1]: Leaving directory '/<>/build'
dh_install --sourcedir=/<>/debian/tmp
 dpkg-genchanges -A >../libsyncml_0.5.4-2.2_all.changes
dpkg-genchanges: error: binary build with no binary artifacts found; cannot 
distribute
dpkg-buildpackage: error: dpkg-genchanges gave error exit status 2


This usually happens because there is a binary-indep target in debian/rules
which is either empty or does not do anything useful.

If all the arch-independent packages are dummy transitional packages released 
with jessie,
the easy fix is to drop them now. If not, debian/rules should be modified so 
that the
binary-indep target generates the architecture independent packages (and only 
those).

After checking that both "dpkg-buildpackage -A" and "dpkg-buildpackage -B" work
properly, this package will be suitable to be uploaded in source-only form if 
you wish
(I recommend that you try it).

Thanks.
--- End Message ---
--- Begin Message ---
Version: 0.5.4-2.3+rm

Dear submitter,

as the package libsyncml 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/854755

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#854289: marked as done (newbiedoc: Too outdated for being useful)

[Debian Bug Tracking System]

Your message dated Tue, 14 Feb 2017 19:09:16 +
with message-id 
and subject line Bug#854726: Removed package(s) from unstable
has caused the Debian Bug report #854289,
regarding newbiedoc: Too outdated for being useful
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.)


-- 
854289: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854289
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: newbiedoc
Version: 0.8.0-2.1
Severity: serious

"I'm writing this in January of 2001 as it applies to my
 Debian "potato" release." (Runlevels_introduction.html)

The included files are ~ 15 years old and have last been
revised ~ 10 years ago in etch/squeeze times.

Reading some of the files brings back memories from the
good old days when men were real men, winters were real winters,
and systemd did not exist. :-)

But as documentation for newbies (or anyone else) it is
no longer suitable.
--- End Message ---
--- Begin Message ---
Version: 0.8.0-2.1+rm

Dear submitter,

as the package newbiedoc 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/854726

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#817744: marked as done (zeroc-icee-java: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Tue, 14 Feb 2017 19:12:34 +
with message-id 
and subject line Bug#854752: Removed package(s) from unstable
has caused the Debian Bug report #817744,
regarding zeroc-icee-java: 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.)


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

Hi,

The package zeroc-icee-java 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 ---
Version: 1.2.0-3+rm

Dear submitter,

as the package zeroc-icee-java 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/854752

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#814767: marked as done (zeroc-icee-java: FTBFS: config/common.xml:34: java.lang.ClassFormatError: proguard.ant.ProGuardTask (unrecognized class file version))

[Debian Bug Tracking System]

Your message dated Tue, 14 Feb 2017 19:12:34 +
with message-id 
and subject line Bug#854752: Removed package(s) from unstable
has caused the Debian Bug report #814767,
regarding zeroc-icee-java: FTBFS: config/common.xml:34: 
java.lang.ClassFormatError: proguard.ant.ProGuardTask (unrecognized class file 
version)
to be marked as done.

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

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


-- 
814767: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814767
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zeroc-icee-java
Version: 1.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,

zeroc-icee-java fails to build from source in unstable/amd64:

  [..]

  dh_clean 
  dh_clean: Compatibility levels before 5 are deprecated (level 4 in use)
  /usr/lib/jvm/java-gcj/bin/java -classpath /usr/share/ant/lib/ant-launcher.jar 
-Dant.home=/usr/share/ant org.apache.tools.ant.launch.Launcher -cp 
/usr/share/java/proguard.jar -Djdk.version=1.4  clean
  Buildfile: 
/home/lamby/temp/cdt.20160215091322.4umRwGdLUi/zeroc-icee-java-1.2.0/build.xml
  
  BUILD FAILED
  
/home/lamby/temp/cdt.20160215091322.4umRwGdLUi/zeroc-icee-java-1.2.0/build.xml:16:
 The following error occurred while executing this line:
  
/home/lamby/temp/cdt.20160215091322.4umRwGdLUi/zeroc-icee-java-1.2.0/config/common.xml:34:
 java.lang.ClassFormatError: proguard.ant.ProGuardTask (unrecognized class file 
version)
 at java.lang.VMClassLoader.defineClass(libgcj.so.16)
 at java.lang.ClassLoader.defineClass(libgcj.so.16)
 at java.security.SecureClassLoader.defineClass(libgcj.so.16)
 at java.net.URLClassLoader.findClass(libgcj.so.16)
 at java.lang.ClassLoader.loadClass(libgcj.so.16)
 at java.lang.ClassLoader.loadClass(libgcj.so.16)
 at 
org.apache.tools.ant.AntClassLoader.findBaseClass(AntClassLoader.java:1407)
 at org.apache.tools.ant.AntClassLoader.loadClass(AntClassLoader.java:1085)
 at java.lang.ClassLoader.loadClass(libgcj.so.16)
 at org.apache.tools.ant.taskdefs.Available.checkClass(Available.java:455)
 at org.apache.tools.ant.taskdefs.Available.eval(Available.java:286)
 at 
org.apache.tools.ant.taskdefs.ConditionTask.execute(ConditionTask.java:120)
 at java.lang.reflect.Method.invoke(libgcj.so.16)
 at 
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
 at org.apache.tools.ant.TaskAdapter.execute(TaskAdapter.java:155)
 at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:293)
 at java.lang.reflect.Method.invoke(libgcj.so.16)
 at 
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
 at org.apache.tools.ant.Task.perform(Task.java:348)
 at org.apache.tools.ant.Target.execute(Target.java:435)
 at 
org.apache.tools.ant.helper.ProjectHelper2.parse(ProjectHelper2.java:169)
 at 
org.apache.tools.ant.taskdefs.ImportTask.importResource(ImportTask.java:222)
 at org.apache.tools.ant.taskdefs.ImportTask.execute(ImportTask.java:163)
 at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:293)
 at java.lang.reflect.Method.invoke(libgcj.so.16)
 at 
org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
 at org.apache.tools.ant.Task.perform(Task.java:348)
 at org.apache.tools.ant.Target.execute(Target.java:435)
 at 
org.apache.tools.ant.helper.ProjectHelper2.parse(ProjectHelper2.java:180)
 at 
org.apache.tools.ant.ProjectHelper.configureProject(ProjectHelper.java:93)
 at org.apache.tools.ant.Main.runBuild(Main.java:828)
 at org.apache.tools.ant.Main.startAnt(Main.java:235)
 at org.apache.tools.ant.launch.Launcher.run(Launcher.java:285)
 at org.apache.tools.ant.launch.Launcher.main(Launcher.java:112)
  
  Total time: 0 seconds
  /usr/share/cdbs/1/class/ant.mk:44: recipe for target 'clean' failed
  make: [clean] Error 1 (ignored)
  rm -f debian/stamp-ant-build
   debian/rules build
  /usr/share/cdbs/1/rules/simple-patchsys.mk:31: CDBS WARNING:
simple-patchsys.mk is deprecated since 0.4.85 - please use source format 3.0 
(quilt) instead
  test -x debian/rules
  mkdir -p "."
  /usr/share/cdbs/1/rules/buildcore.mk:110: CDBS WARNING:
DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85
  /usr/bin/make -f debian/rules reverse-config
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20160215091322.4umRwGdLUi/zeroc-icee-java-1.2.0'
  

Bug#817743: marked as done (zeroc-icee: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Tue, 14 Feb 2017 19:13:23 +
with message-id 
and subject line Bug#854753: Removed package(s) from unstable
has caused the Debian Bug report #817743,
regarding zeroc-icee: 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.)


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

Hi,

The package zeroc-icee 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 ---
Version: 1.2.0-6.2+rm

Dear submitter,

as the package zeroc-icee 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/854753

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#842387: marked as done (zeroc-icee: FTBFS in amd64 clean jail)

[Debian Bug Tracking System]

Your message dated Tue, 14 Feb 2017 19:13:23 +
with message-id 
and subject line Bug#854753: Removed package(s) from unstable
has caused the Debian Bug report #842387,
regarding zeroc-icee: FTBFS in amd64 clean jail
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.)


-- 
842387: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842387
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zeroc-icee
Version: 1.2.0-6.2
Severity: grave
Justification: renders package unusable

The package FTBFS in a chroot jail and in cowbuilder. The error message is:

dh_install -plibicee-dev --sourcedir=debian/tmp
dh_install: Cannot find (any matches for) "usr/lib/*.a" (tried in "debian/tmp" 
and "debian/tmp")
dh_install: libicee-dev missing files: usr/lib/*.a
dh_install: missing files, aborting
/usr/share/cdbs/1/rules/debhelper.mk:233: recipe for target 
'binary-install/libicee-dev' failed
make: *** [binary-install/libicee-dev] Error 255

Regards,

Eriberto
--- End Message ---
--- Begin Message ---
Version: 1.2.0-6.2+rm

Dear submitter,

as the package zeroc-icee 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/854753

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#817745: marked as done (zeroc-icee-translators: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Tue, 14 Feb 2017 19:11:54 +
with message-id 
and subject line Bug#854751: Removed package(s) from unstable
has caused the Debian Bug report #817745,
regarding zeroc-icee-translators: 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.)


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

Hi,

The package zeroc-icee-translators 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 ---
Version: 1.2.0-6.1+rm

Dear submitter,

as the package zeroc-icee-translators 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/854751

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#817419: marked as done (cvs-autoreleasedeb: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Tue, 14 Feb 2017 19:10:27 +
with message-id 
and subject line Bug#854748: Removed package(s) from unstable
has caused the Debian Bug report #817419,
regarding cvs-autoreleasedeb: 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.)


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

Hi,

The package cvs-autoreleasedeb 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 ---
Version: 0.12-1+rm

Dear submitter,

as the package cvs-autoreleasedeb 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/854748

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#817718: marked as done (wayv: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Tue, 14 Feb 2017 19:11:08 +
with message-id 
and subject line Bug#854750: Removed package(s) from unstable
has caused the Debian Bug report #817718,
regarding wayv: 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.)


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

Hi,

The package wayv 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 ---
Version: 0.3-5+rm

Dear submitter,

as the package wayv 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/854750

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#817420: marked as done (cvschangelogbuilder: Removal of debhelper compat 4)

[Debian Bug Tracking System]

Your message dated Tue, 14 Feb 2017 19:09:48 +
with message-id 
and subject line Bug#854747: Removed package(s) from unstable
has caused the Debian Bug report #817420,
regarding cvschangelogbuilder: 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.)


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

Hi,

The package cvschangelogbuilder 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 ---
Version: 2.4-1+rm

Dear submitter,

as the package cvschangelogbuilder 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/854747

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#817325: marked as done (cvs-autoreleasedeb: Mandatory debian/compat for debhelper)

[Debian Bug Tracking System]

Your message dated Tue, 14 Feb 2017 19:10:27 +
with message-id 
and subject line Bug#854748: Removed package(s) from unstable
has caused the Debian Bug report #817325,
regarding cvs-autoreleasedeb: Mandatory debian/compat for debhelper
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.)


-- 
817325: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817325
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cvs-autoreleasedeb
Severity: important
Usertags: mandatory-debian-compat

Hi,

The package cvs-autoreleasedeb uses debhelper but does not have a debian/compat
file.

 * Please add a debian/compat file at your earliest convenience.

 * This will become mandatory in the first debhelper upload after
   15th of April.

If your package is *also* affected by any of the following debhelper
related deprecations, please consider fixing them at the same time:

 * debhelper compat 4 is deprecated and is expected to be removed
   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].

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Version: 0.12-1+rm

Dear submitter,

as the package cvs-autoreleasedeb 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/854748

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#806969: marked as done (auto_start option crashes with current tornado)

[Debian Bug Tracking System]

Your message dated Tue, 14 Feb 2017 19:05:27 +
with message-id 
and subject line Bug#836499: Removed package(s) from unstable
has caused the Debian Bug report #806969,
regarding auto_start option crashes with current tornado
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.)


-- 
806969: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806969
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-tornadio2
Version: 0.0.4-1
Severity: important

Hello,

thank you for maintaining tornadio2.

In one of our sites we rely on the auto_start feature, but with the new tornado
it causes an exception to be raised:

   $ python
   Python 2.7.10+ (default, Oct 10 2015, 09:11:24) 
   [GCC 5.2.1 20151028] on linux2
   Type "help", "copyright", "credits" or "license" for more information.
   >>> import tornadio2
   >>> import tornado
   >>> server = tornadio2.SocketServer(tornado.web.Application([]), 
auto_start=False)
   Traceback (most recent call last):
 File "", line 1, in 
 File "/usr/lib/python2.7/dist-packages/tornado/util.py", line 222, in 
__new__
   instance.initialize(*args, **init_kwargs)
   TypeError: initialize() got an unexpected keyword argument 'auto_start'
   >>> 

I will now try to redesign my code to work around this.


Thank you,

Enrico

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

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

Versions of packages python-tornadio2 depends on:
ii  python 2.7.9-1
ii  python-simplejson  3.7.3-1+b1
ii  python-tornado 4.2.1-1+b1

python-tornadio2 recommends no packages.

python-tornadio2 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.0.4-1+rm

Dear submitter,

as the package tornadio2 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/836499

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#807029: marked as done (tornadio2.gen.sync_engine does not work with recent versions of Tornado)

[Debian Bug Tracking System]

Your message dated Tue, 14 Feb 2017 19:05:27 +
with message-id 
and subject line Bug#836499: Removed package(s) from unstable
has caused the Debian Bug report #807029,
regarding tornadio2.gen.sync_engine does not work with recent versions of 
Tornado
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.)


-- 
807029: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=807029
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-tornadio2
Version: 0.0.4-1
Severity: important

Hello,

in tornadio2/gen.py:45, the tornado.gen.Runner constructor is invoked
with only one argument besides self, although in recent versions of
tornado it requires 3: 
http://tornadokevinlee.readthedocs.org/en/latest/_modules/tornado/gen.html

This results in a traceback, and in tornadio2.gen.sync_engine not being usable:

[E 151204 10:28:13 root session:433] __init__() takes exactly 4 arguments (2 
given)
Traceback (most recent call last):
  File "/home/enrico/lavori/truelite/reach/reach/tornadio2/session.py", 
line 381, in raw_message
conn.on_message(msg_data)
  File "/home/enrico/lavori/truelite/reach/reach/tornadio2/gen.py", line 
113, in wrapper
run(args, kwargs)
  File "/home/enrico/lavori/truelite/reach/reach/tornadio2/gen.py", line 
84, in run
data.runner = SyncRunner(gen, finished)
  File "/home/enrico/lavori/truelite/reach/reach/tornadio2/gen.py", line 
45, in __init__
super(SyncRunner, self).__init__(gen)
TypeError: __init__() takes exactly 4 arguments (2 given)
[E 151204 10:28:13 root persistent:148] Failed to handle message: Traceback 
(most recent call last):
  File "/home/enrico/lavori/truelite/reach/reach/tornadio2/persistent.py", 
line 146, in on_message
self.session.raw_message(message)
  File "/home/enrico/lavori/truelite/reach/reach/tornadio2/session.py", 
line 381, in raw_message
conn.on_message(msg_data)
  File "/home/enrico/lavori/truelite/reach/reach/tornadio2/gen.py", line 
113, in wrapper
run(args, kwargs)
  File "/home/enrico/lavori/truelite/reach/reach/tornadio2/gen.py", line 
84, in run
data.runner = SyncRunner(gen, finished)
  File "/home/enrico/lavori/truelite/reach/reach/tornadio2/gen.py", line 
45, in __init__
super(SyncRunner, self).__init__(gen)
TypeError: __init__() takes exactly 4 arguments (2 given)


Thanks,

Enrico


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

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

Versions of packages python-tornadio2 depends on:
ii  python 2.7.9-1
ii  python-simplejson  3.7.3-1+b1
ii  python-tornado 4.2.1-1+b1

python-tornadio2 recommends no packages.

python-tornadio2 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.0.4-1+rm

Dear submitter,

as the package tornadio2 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/836499

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#818926: marked as done (perl6-panda: panda doesn't start up / find needed libraries)

[Debian Bug Tracking System]

Your message dated Tue, 14 Feb 2017 19:07:33 +
with message-id 
and subject line Bug#854339: Removed package(s) from unstable
has caused the Debian Bug report #818926,
regarding perl6-panda: panda doesn't start up / find needed libraries
to be marked as done.

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

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


-- 
818926: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818926
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: perl6-panda
Version: 2016.02-1
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

panda simply doesn't work:

% panda --help
===SORRY!===
Could not find Shell::Command in:
/home/gregoa/.perl6/2016.02
/usr/share/perl6/site
/usr/share/perl6/vendor
/usr/share/perl6
CompUnit::Repository::AbsolutePath<139839414999752>
CompUnit::Repository::NQP<139839414997224>
CompUnit::Repository::Perl5<139839414994856>


% PERL6LIB=/usr/share/perl6/lib panda --help
===SORRY!=== 
Failed to create directory '/usr/share/perl6/lib/.precomp' with mode '0o777': 
Failed to mkdir: 13



No material for testing yet :)


Cheers,
gregor

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQJ8BAEBCgBmBQJW8EnAXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC
QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoG9HsP+wamdKSxAsHP/GUcjIQ8rCtX
E+1HF5rxgZ82BDmSHhD4TIY9KbQ45Tv8957+vjsyzJpBKqUspQBTqMJCbdWRtnE9
VhCKMgwoiF4A982fdXQ0kEr5xvIDN5Um05zKTz2g/w61AzS/aEke0+HqdLbmlU+5
NyVQGEMok5E248+UREi3ZJzwsXdra0+Kmf+avKBv6VjQ0WhtsmIbukOpjNpbuWff
sKfMPkvfIcmMsm/K9qP9KvhgAoVOUrHKaR0NLVwA80+yEXbreIMtIISHUgYtSnbf
PXZdWA11d+QxDJuoPIlYzK2OOhE4OtOr8+DLD0r4abwhvQm5DleahJ7AxRZalLim
uJe2YRjxy0CWu+3KMWYUj5HPIdqaBRJjWhYot5JX6tqpezoM94r8tX1rt4eIxG0t
AvxhWraZmQxmRCkTCrW3Djrt93mB3G3s80agT7g5ZU3olHf5oa71RepPtjBwz6+x
y2dvJYMn+6oDUce5H/CCSKdXDR7lKZV0H5bU0O9btOANexjxhFV509De3QTgs/+a
0r7bRn1hFJb1qL7+dUO799RpmmCb9idw9Rv+zTUPvlteo3qm1SoK9wwC4hDhx4EN
QNGtNnIrWv8gMwj6AoJwTvxJ7rj1BUfPfxEt47ZX8wd1zAZ4MQRSiaV/lVW4p55k
piLYoF0RcxSWp3RIxb0u
=uQUt
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Version: 2016.02-1+rm

Dear submitter,

as the package perl6-panda 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/854339

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#850149: marked as done (shotwell: Freezes when trying to open an image in fullscreen mode)

[Debian Bug Tracking System]

Your message dated Tue, 14 Feb 2017 18:34:27 +
with message-id 
and subject line Bug#850149: fixed in shotwell 0.25.4+really0.24.5-0.1
has caused the Debian Bug report #850149,
regarding shotwell: Freezes when trying to open an image in fullscreen mode
to be marked as done.

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

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


-- 
850149: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850149
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: shotwell
Version: 0.25.1-1
Severity: normal

Hello,

when I open Shotwell and I double click on one of the images from the
"Photos" library (I have tens of thousands) in order to display it in
fullscreen mode then the app freezes more often than not.

After a while I get the "Shotwell is not responding" dialog, with
the "Force Quit" and "Wait" options. If I wait then I finally get
the image in fullscreen mode after ~30 seconds and the app behaves
normally again. After that I can double click on any other image from
the library and Shotwell responds normally.

If instead of opening an image from the main "Photos" library I choose
one event and double click on a photo from there then app also behaves
normally.

I believe this started to happen recently (maybe after Shotwell
0.24.0).

I'm attaching the backtrace of the moment when Shotwell is frozen.

Regards,

Berto

-- Package-specific info:

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

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

Versions of packages shotwell depends on:
ii  dbus-user-session [default-dbus-session-bus]  1.10.14-1
ii  dbus-x11 [dbus-session-bus]   1.10.14-1
ii  dconf-cli 0.26.0-2
ii  libatk1.0-0   2.22.0-1
ii  libc6 2.24-7
ii  libcairo-gobject2 1.14.6-1.1
ii  libcairo2 1.14.6-1.1
ii  libexif12 0.6.21-2
ii  libgck-1-03.20.0-3
ii  libgcr-base-3-1   3.20.0-3
ii  libgcr-ui-3-1 3.20.0-3
ii  libgdk-pixbuf2.0-02.36.2-1
ii  libgee-0.8-2  0.18.1-1
ii  libgexiv2-2   0.10.4-1
ii  libglib2.0-0  2.50.2-2
ii  libgomp1  6.2.1-5
ii  libgphoto2-6  2.5.11-1
ii  libgphoto2-port12 2.5.11-1
ii  libgstreamer-plugins-base1.0-01.10.2-1
ii  libgstreamer1.0-0 1.10.2-1
ii  libgtk-3-03.22.4-1
ii  libgudev-1.0-0230-3
ii  libjavascriptcoregtk-4.0-18   2.14.2-1
ii  libjson-glib-1.0-01.2.2-1
ii  liblcms2-22.7-1
ii  libp11-kit0   0.23.2-5
ii  libpango-1.0-01.40.3-3
ii  libpangocairo-1.0-0   1.40.3-3
ii  libraw15  0.17.2-6
ii  librsvg2-common   2.40.16-1
ii  libsoup2.4-1  2.56.0-1
ii  libsqlite3-0  3.15.2-1
ii  libstdc++66.2.1-5
ii  libwebkit2gtk-4.0-37  2.14.2-1
ii  libxml2   2.9.4+dfsg1-2.1
ii  shotwell-common   0.25.1-1

shotwell recommends no packages.

shotwell suggests no packages.

-- no debconf information
Thread 29 (Thread 0x7fff93fff700 (LWP 20434)):
#0  0x7fffef17f119 in syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x7fffef91326a in g_cond_wait_until (cond=cond@entry=0x55bce698, 
mutex=mutex@entry=0x55bce690, end_time=end_time@entry=146184007185)
at ././glib/gthread-posix.c:1442
#2  0x7fffef8a1e89 in g_async_queue_pop_intern_unlocked 
(queue=queue@entry=0x55bce690, wait=wait@entry=1, 
end_time=end_time@entry=146184007185)
at ././glib/gasyncqueue.c:422
#3  0x7fffef8a24ac in 

Processed: 855130 found in release 3.0.6-10.1

[Debian Bug Tracking System]

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

> found 855130 3.0.6-10.1
Bug #855130 [src:med-fichier] med-fichier: MED library is not compatible with 
HDF5 1.10
Marked as found in versions med-fichier/3.0.6-10.1.
> thanks
Stopping processing here.

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

Bug#849504: Data corruption with copy-on-write and multiple threads

[Niels Thykier]

Wouter Verhelst:
> Hi Niels,
> 
> On Sun, Feb 12, 2017 at 08:52:00AM +, Niels Thykier wrote:
>> Any news on this bug?
> 
> I'm going to release (upstream) nbd 3.15.2 later this week (probably on
> thursday), which contains the fix:
> 
> https://github.com/NetworkBlockDevice/nbd/compare/nbd-3.15.1...master
> 
> This patch series includes:
> 
> - The fix for this bug, commit a43a2d8;
> - Several minor documentation fixes (e.g., fixed the sorting of a listing in a
>   man page);
> - A better fix for the issue of nbd-client-udeb being compiled against GnuTLS
>   that does not break the build on kFreeBSD etc;
> - The ability to change the GnuTLS priority string, to follow TLS best
>   practices and allow people to lock down the TLS configuration
> 
> I would like to update nbd to that version; but if the release team
> prefers, I can cherry-pick a43a2d8 onto 3.15.1 and upload that instead.
> 

Thanks for getting back to me on this.

On the note of the actual changes, could you please provide a (source)
debdiff, so I know what we are looking at?

Thanks,
~Niels

Bug#855142: tmpfile are not random

[Bastien ROUCARIES]

Package: src:pdfsandwich
version: 0.1.6-1
Severity: grave
Tags: security
X-Debbugs-CC: secure-testing-t...@lists.alioth.debian.org

Hi,

pdfsandwish use totally previsible file name like
/tmp/pdfsandwich_inputfileea1150.pdf[11]

Security team could you open a CVE ?

Upsteam should use for instance a tmpname subdirectory

Bastien

Bug#855096: unison: segfaults after connection has been established

[Soramichi Akiyama]

Hi,

> Growing page table to 262144 entries

This means that unison uses up to 262144 pages * 4KB/page == 1GB of memory,
which must be a memory leak.

In the upstream repository there are several memory leak issues reported,
like this: https://github.com/bcpierce00/unison/pull/55
or this: https://github.com/bcpierce00/unison/issues/33 (not yet closed 
unfortunately).

If your situation is reproducible, I think trying the latest release (2.48.15)
and see if there's any difference will help a lot.
https://github.com/bcpierce00/unison/releases/tag/2.48.15

-- 
Soramichi Akiyama 

Bug#854343: network-manager: The search domain string in resolv.conf is being duplicated leading to problems with DNS

[Michael Biebl]

Thanks for testing

Am 14.02.2017 um 10:50 schrieb Tilo Villwock:

> I only installed the newly created network-manager_1.6.0 package
> though. When this is fixed and a new version gets into the
> repositories. Will my own package be removed automatically in favor of
> the new one?

If you didn't change the version number and kept 1.6.0-1 it will be
upgraded automatically.


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



signature.asc
Description: OpenPGP digital signature

Bug#854336: spice: diff for NMU version 0.12.8-2.1

[Liang Guo]

please upload it to unstable now.

Thank you !

On Tue, Feb 14, 2017 at 5:00 AM, Markus Koschany  wrote:
> Control: tags 854336 + pending
>
> Dear maintainer,
>
> I've prepared an NMU for spice (versioned as 0.12.8-2.1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer.
>
> I am attaching the debdiff to this bug report.
>
> Regards,
>
> Markus



-- 
Liang Guo
http://guoliang.me/

Processed: bug 855129 is forwarded to https://github.com/flatpak/flatpak/issues/557

[Debian Bug Tracking System]

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

> forwarded 855129 https://github.com/flatpak/flatpak/issues/557
Bug #855129 [flatpak] flatpak: Portals can't read /proc/$pid/root in Debian
Set Bug forwarded-to-address to 'https://github.com/flatpak/flatpak/issues/557'.
> thanks
Stopping processing here.

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

Bug#855130: med-fichier: MED library is not compatible with HDF5 1.10

[Gilles Filippini]

Source: med-fichier
Version: 3.0.6-11
Severity: grave
Justification: renders package unusable

Hi,

From the Salome Platform support forum [1]:

> Problems with Salome and Code Saturne in Debian
> Posted by Elektrix at January 03. 2017
> 
> Hello all,
> 
> I'm trying to set up a CFD case with Salome, export the mesh in a MED file 
> and then process it with Code Saturne. CS doesn't read the MED file and gives 
> the error in the preprocessing stage:
> 
> _MEDdatasetRd.c [139] : Erreur à la lecture du dataset
> _MEDdatasetRd.c [139] : COO
> HDF5-DIAG: Error detected in HDF5 (1.10.0-patch1) thread 0:
>   #000: ../../../src/H5Dio.c line 170 in H5Dread(): can't read data
> major: Dataset
> minor: Read failed
>   #001: ../../../src/H5Dio.c line 418 in H5D__read(): unable to set up type 
> info
> major: Dataset
> minor: Unable to initialize object
>   #002: ../../../src/H5Dio.c line 953 in H5D__typeinfo_init(): not a datatype
> major: Invalid arguments to routine
> minor: Inappropriate type
> _MEDdatasetRd.c [142] : _dataset = 2
> _MEDdatasetRd.c [143] : _i = 0
> _MEDdatasetRd.c [144] : (*filter).memspace[_i] = 2
> _MEDdatasetRd.c [145] : (*filter).diskspace[_i] = 3
> _MEDmeshAdvancedRd30.c [462] : Erreur à la lecture du dataset
> _MEDmeshAdvancedRd30.c [462] :
> _MEDmeshAdvancedRd30.c [463] : meshname = "Mesh_water"
> _MEDmeshAdvancedRd30.c [463] : numit = -1
> _MEDmeshAdvancedRd30.c [463] : numdt = -1
> _MEDmeshAdvancedRd30.c [463] : _datagroupname2 = "NOE"
> _MEDmeshAdvancedRd30.c [464] : _datagroupname3 = ""
> _MEDmeshAdvancedRd30.c [464] : _profilename = "MED_NO_PROFILE_INTERNAL"
> 
> The problem can be because I installed Salome from the SALOME-7.6.0-DB07.tgz 
> archive whilst Code Saturne is a Debian package and is installed via the 
> Debian package system which is much easier than installing the original 
> package. So the med and hdf5 libraries of CS come from the Debian 
> repositories. I can't use newer versions of Salome (7.7.1 or 7.8.0) as they 
> produce MED3.1 files but my CS reads only MED3.0 files.
> 
> The details of my machine:
> 
> Debian stretch (testing) on AMD64
> 
> Salome 7.6.0 from SALOME-7.6.0-DB07.tgz
> 
> Code Saturne 4.3 Debian package
> 
> libmed 3.0.6-10.1 Debian package
> 
> hdf5 1.10.0 Debian package
> 
> Not knowing if this problem comes from how I create the mesh I tried to run 
> one of the test cases from the Code Saturne tutorials but ran into other 
> problems.
> 
> If you need any other information pleas let me know. Any hint on how to go 
> further is very welcome.
> 
> Best regards
> 
> Elektrix



> Re: Problems with Salome and Code Saturne in Debian
> Posted by Yvan Fournier at Monday 16:21
> 
> Hello,
> 
> I was contacted by the Debian maintainer relative to this, so it seems the 
> bug was reported.
> 
> The root problem is that the MED library is not compatible with HDF5 1.10 
> yet. So reverting to HDF5 1.8 as indicated is the solution for now, but the 
> better solution would be for MED to handle compatibility with both HDF5 1.8 
> and HDF5 1.10 (or at least 1.10 for future versions).
> 
> Best regards,
> 
> Yvan

[1] http://www.salome-platform.org/forum/forum_9/122041955

Thanks,

_g.

Bug#853755: Bug#852811: fixed in systemd 232-16

[Martin Pitt]

Hello Breno,

Breno Leitao [2017-02-14 11:14 -0200]:
> Are you going to move systemd to 232-16 or backport the patch to stretch 
> 232-15?

Yes, we'll give -18 a few days to settle in unstable, then I'll ask the release
team for letting it in.

Martin

Bug#855129: flatpak: Portals can't read /proc/$pid/root in Debian

[Simon McVittie]

Package: flatpak
Version: 0.8.2-1
Severity: serious
Justification: maintainer says so
Tags: fixed-upstream pending

Portals like the ones in xdg-desktop-portal{,-gtk} need to know the
identity of the confined Flatpak app. They discover this by reading
the special file /proc/$pid/root/flatpak-info.

Unfortunately, when a setuid bwrap is told to use user namespaces even
though they are not strictly necessary (in our case because Debian's
kernels do not allow unprivileged processes to create their own user
namespaces by default), the resulting user namespace is owned by
root. This means user processes outside the container are not allowed
to ptrace it, and the ptrace capability is also what controls the
ability to read and traverse /proc/$pid/root.

Flatpak 0.8.3 fixes this by not explicitly requesting the creation of a
user namespace. If bwrap is not setuid (as in Ubuntu) it will create
a user namespace anyway, because that's a prerequisite for being able to
create its mount namespace. If bwrap is setuid (as in Debian) it will
skip creation of the user namespace, so we can traverse through
/proc/$pid/root as intended.

Not being able to identify confined processes is pretty bad for the
ability to make informed decisions about access control in portals,
which are a key part of what makes Flatpak containers usable, so I'm
considering this to be release-critical.

S

Bug#854837: Package dicompyler does not work

[Vojtech Kulvait]

Whoewer will be solving this issue. Quick fix should be to edit
/usr/share/dicompyler/dicompyler/dicomgui.py such that after the line 46
there will be edit adding these two lines


class DicomImporterDialog(wx.Dialog):
"""Import DICOM RT files and return a dictionary of data."""

def __init__(self):
pre = wx.PreDialog()
# the Create step is done by XRC.
self.PostCreate(pre)



*path = "/tmp"import_location_setting = "Remember Last Used"*

def Init(self, res):


After doing that program seems to be able to read RT data and even seem to
be importing them. However the program is unable to show these data,
without warnings or errors in the console.

Vojtech.



2017-02-12 22:51 GMT+01:00 Andreas Tille :

> tags 854837 help
> severity 854837 grave
> thanks
>
> I can confirm Vojtech's observation that "Open patient" button throws
> this exception.  I've tagged this bug "help", raised its severity to
> grave and added upstream developer in CC.  As I said there are no
> commits on Github for quite some time and there are several open issues
> which report about disfunctionality.  I have some slight hope that
> somebody from the Debian team might pick up this issue since it seems to
> be reproducible.  If it turns out that it can not be fixed until the
> next release we will not distribute this package inside the next stable
> release.
>
> Thanks for the bug report and sorry for not beeing more helpful
>
> Andreas.
>
> On Sun, Feb 12, 2017 at 10:30:20PM +0100, Vojtech Kulvait wrote:
> > Hi,
> > the package you provided to me does not work either. It shows main
> > application dialog but when I click on Open patient button it does not
> open
> > dialog but in console there is
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > *ERROR: Unhandled exception: Traceback (most recent call last):  File
> > "/usr/share/dicompyler/dicompyler/main.py", line 314, in OnOpenPatient
> > dicomgui.ImportDicom(self)  File
> > "/usr/share/dicompyler/dicompyler/dicomgui.py", line 31, in ImportDicom
> > dlgDicomImporter.Init(res)  File
> > "/usr/share/dicompyler/dicompyler/dicomgui.py", line 129, in Init
> > self.OnDirectorySearch()  File
> > "/usr/share/dicompyler/dicompyler/dicomgui.py", line 188, in
> > OnDirectorySearchargs=(self, self.path,
> > self.import_search_subfolders,AttributeError: 'DicomImporterDialog'
> object
> > has no attribute 'path'*
> > Which is the same behavior as when I solved that matplotlib problem by
> > editing that file.
> >
> > I was lucky enough to run windows version today. I was able to view ct
> data
> > and radiotherapy data and doses data. It seems in the package you
> provided
> > to me there is even no button for importing these data and import dialog
> is
> > gray.
> > Vojtech.
> >
> >
> > 2017-02-12 15:46 GMT+01:00 Andreas Tille :
> >
> > > Hi Vojtech,
> > >
> > > please make sure you send your mails to 854...@bugs.debian.org and not
> > > my private e-mail address.  Thanks.
> > >
> > > On Sun, Feb 12, 2017 at 08:50:05AM +, Vojtech Kulvait wrote:
> > > > Andreas,
> > > > I am using Debian Jessie and you are using some development version.
> > >
> > > I admit that is true and I assumed that the egg-info files would have
> > > been cleaned up also by previous python helper versions.  Sorry for
> > > the confusion.
> > >
> > > > In the
> > > > package http://http.debian.net/debian/pool/main/d/dicompyler/
> > > > dicompyler_0.4.2.orig.tar.gz there is file
> > > > dicompyler/dicompyler-0.4.2.egg-info/requires.txt
> > >
> > > To be clear about this:  Inside the .orig.tar.gz tarball you will find
> > > the orginal source as the authors of dicompyler.  As I said its
> > > unmaintained and orphaned code which will probably never change.
> > > However, at least in *recent* build tools the egg-info files are
> cleaned
> > > up.
> > >
> > > > in the format I have described with those dependencieds. To
> replicate the
> > > > problem I downloaded live CD with debian Jessie (XFCE).
> > > >
> > > > Using vanilla Debian Live CD:
> > > > apt-get install dicompyler
> > > > dicompyler
> > > > The result is:
> > > >
> > > > *Traceback (most recent call last):  File "/usr/bin/dicompyler",
> line 5,
> > > in
> > > > from pkg_resources import load_entry_point  File
> > > > "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 2876, in
> > > > working_set = WorkingSet._build_master()  File
> > > > "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 451, in
> > > > _build_masterreturn cls._build_from_requirements(__requires__)
> File
> > > > "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 464, in
> > > > _build_from_requirementsdists = ws.resolve(reqs, Environment())
> File
> > > > "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 639, in
> > > > resolveraise
> > > > DistributionNotFound(req)pkg_resources.DistributionNotFound:
> > > > matplotlib>=0.99,<=1.3.1*
> > > >
> > > >
> > > 

Bug#853755: Bug#852811: fixed in systemd 232-16

[Breno Leitao]

Hi Martin,

On Thu, 09 Feb 2017 17:34:33 + Martin Pitt  wrote:
> Source: systemd
> Source-Version: 232-16

How will it show up in Stretch?

Are you going to move systemd to 232-16 or backport the patch to stretch 232-15?

Thank you,
Breno

Processed: found 854742 in 3.0-2

[Debian Bug Tracking System]

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

> found 854742 3.0-2
Bug #854742 {Done: Christoph Martin } [postfixadmin] 
CVE-2017-5930
Marked as found in versions postfixadmin/3.0-2.
> thanks
Stopping processing here.

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

Bug#854517: marked as done (vagrant-sshfs: Makes vagrant crash with “cannot load translations”)

[Debian Bug Tracking System]

Your message dated Tue, 14 Feb 2017 12:19:55 +
with message-id 
and subject line Bug#854517: fixed in vagrant-sshfs 1.3.0-2
has caused the Debian Bug report #854517,
regarding vagrant-sshfs: Makes vagrant crash with “cannot load translations”
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.)


-- 
854517: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854517
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: vagrant-sshfs
Version: 1.3.0-1
Severity: grave

Dear Maintainer,

After installing vagrant-sshfs, I cannot run vagrant anymore.

> % vagrant init debian/jessie64; vagrant up --provider libvirt
> /usr/lib/ruby/vendor_ruby/i18n/backend/base.rb:184:in `rescue in load_yml': 
> can not load translations from /usr/lib/ruby/locales/synced_folder_sshfs.yml: 
> # /usr/lib/ruby/locales/synced_folder_sshfs.yml> (I18n::InvalidLocaleData)
>   from /usr/lib/ruby/vendor_ruby/i18n/backend/base.rb:181:in `load_yml'
>   from /usr/lib/ruby/vendor_ruby/i18n/backend/base.rb:165:in `load_file'
>   from /usr/lib/ruby/vendor_ruby/i18n/backend/base.rb:15:in `block in 
> load_translations'
>   from /usr/lib/ruby/vendor_ruby/i18n/backend/base.rb:15:in `each'
>   from /usr/lib/ruby/vendor_ruby/i18n/backend/base.rb:15:in 
> `load_translations'
>   from /usr/lib/ruby/vendor_ruby/i18n/backend/simple.rb:57:in 
> `init_translations'
>   from /usr/lib/ruby/vendor_ruby/i18n/backend/simple.rb:40:in 
> `available_locales'
>   from /usr/lib/ruby/vendor_ruby/i18n/config.rb:43:in `available_locales'
>   from /usr/lib/ruby/vendor_ruby/i18n/config.rb:49:in 
> `available_locales_set'
>   from /usr/lib/ruby/vendor_ruby/i18n.rb:278:in `locale_available?'
>   from /usr/lib/ruby/vendor_ruby/i18n.rb:284:in 
> `enforce_available_locales!'
>   from /usr/lib/ruby/vendor_ruby/i18n.rb:151:in `translate'
>   from 
> /usr/share/rubygems-integration/all/gems/vagrant-1.9.1/lib/vagrant/errors.rb:103:in
>  `translate_error'
>   from 
> /usr/share/rubygems-integration/all/gems/vagrant-1.9.1/lib/vagrant/errors.rb:72:in
>  `initialize'
>   from 
> /usr/share/rubygems-integration/all/gems/vagrant-1.9.1/plugins/commands/init/command.rb:51:in
>  `exception'
>   from 
> /usr/share/rubygems-integration/all/gems/vagrant-1.9.1/plugins/commands/init/command.rb:51:in
>  `raise'
>   from 
> /usr/share/rubygems-integration/all/gems/vagrant-1.9.1/plugins/commands/init/command.rb:51:in
>  `execute'
>   from 
> /usr/share/rubygems-integration/all/gems/vagrant-1.9.1/lib/vagrant/cli.rb:42:in
>  `execute'
>   from 
> /usr/share/rubygems-integration/all/gems/vagrant-1.9.1/lib/vagrant/environment.rb:274:in
>  `cli'
>   from 
> /usr/share/rubygems-integration/all/gems/vagrant-1.9.1/bin/vagrant:122:in 
> `'
>   from /usr/bin/vagrant:22:in `load'
>   from /usr/bin/vagrant:22:in `'
> /usr/lib/ruby/vendor_ruby/i18n/backend/base.rb:184:in `rescue in load_yml': 
> can not load translations from /usr/lib/ruby/locales/synced_folder_sshfs.yml: 
> # /usr/lib/ruby/locales/synced_folder_sshfs.yml> (I18n::InvalidLocaleData)
>   from /usr/lib/ruby/vendor_ruby/i18n/backend/base.rb:181:in `load_yml'
>   from /usr/lib/ruby/vendor_ruby/i18n/backend/base.rb:165:in `load_file'
>   from /usr/lib/ruby/vendor_ruby/i18n/backend/base.rb:15:in `block in 
> load_translations'
>   from /usr/lib/ruby/vendor_ruby/i18n/backend/base.rb:15:in `each'
>   from /usr/lib/ruby/vendor_ruby/i18n/backend/base.rb:15:in 
> `load_translations'
>   from /usr/lib/ruby/vendor_ruby/i18n/backend/simple.rb:57:in 
> `init_translations'
>   from /usr/lib/ruby/vendor_ruby/i18n/backend/simple.rb:40:in 
> `available_locales'
>   from /usr/lib/ruby/vendor_ruby/i18n/config.rb:43:in `available_locales'
>   from /usr/lib/ruby/vendor_ruby/i18n/config.rb:49:in 
> `available_locales_set'
>   from /usr/lib/ruby/vendor_ruby/i18n.rb:278:in `locale_available?'
>   from /usr/lib/ruby/vendor_ruby/i18n.rb:284:in 
> `enforce_available_locales!'
>   from /usr/lib/ruby/vendor_ruby/i18n.rb:151:in `translate'
>   from 
> /usr/share/rubygems-integration/all/gems/vagrant-1.9.1/plugins/providers/virtualbox/provider.rb:102:in
>  `state'
>   from 
> /usr/share/rubygems-integration/all/gems/vagrant-1.9.1/lib/vagrant/machine.rb:506:in
>  `state'
>   from 
> /usr/share/rubygems-integration/all/gems/vagrant-1.9.1/lib/vagrant/machine.rb:145:in
>  `initialize'
>   from 
> 

Bug#831541: theano: single GradientError and WrongValues in tests on s390x, ppc64 and sparc

[Daniel Stender]

On 14.02.2017 08:43, Rebecca N. Palmer wrote:
> Found the problem: the affected functions ( 
> https://sources.debian.net/src/theano/0.8.2-4/theano/sparse/opt.py/#L862 , 
> https://sources.debian.net/src/theano/0.8.2-4/theano/sparse/opt.py/#L1902 ) 
> cast a pointer-to-intptr_t (64 bit) to a pointer-to-int (32-bit).
> 
> Which isn't just broken on big-endian systems, it's a strict aliasing 
> violation *everywhere* (i.e. technically undefined behaviour with 
> optimization on, which it is by default, though it appears to work in 
> practice).
> 
> (I expect to post a patch tonight: the obvious has a potential overflow 
> issue, and it also needs a c_code_cache_version change to make the fix be 
> used in existing installs).

That would be sensational. #835531 doesn't keep up being RC, that would mean 
that we're through
to Stretch if this bug could be closed. Much thx in advance!

Daniel

-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
http://www.danielstender.com/

Processed: tagging 854734

[Debian Bug Tracking System]

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

> tags 854734 + upstream
Bug #854734 [src:mupdf] CVE-2017-5896
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Processed: bug 854734 is forwarded to https://bugs.ghostscript.com/show_bug.cgi?id=69751

[Debian Bug Tracking System]

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

> forwarded 854734 https://bugs.ghostscript.com/show_bug.cgi?id=69751
Bug #854734 [src:mupdf] CVE-2017-5896
Set Bug forwarded-to-address to 
'https://bugs.ghostscript.com/show_bug.cgi?id=69751'.
> thanks
Stopping processing here.

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

Bug#850692: marked as done (pyrit: failed with 'BitEnumField' object has no attribute 'names')

[Debian Bug Tracking System]

Your message dated Tue, 14 Feb 2017 09:48:31 +
with message-id 
and subject line Bug#850692: fixed in pyrit 0.4.0-7.1
has caused the Debian Bug report #850692,
regarding pyrit: failed with 'BitEnumField' object has no attribute 'names'
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.)


-- 
850692: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850692
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pyrit
Version: 0.4.0-7
Severity: normal
Tags: patch

Hello,

Trying to run the command "pyrit -r file.cap analyze" failed:
Traceback (most recent call last):
  File "/usr/bin/pyrit", line 6, in 
pyrit_cli.Pyrit_CLI().initFromArgv()
  File "/usr/lib/python2.7/dist-packages/pyrit_cli.py", line 115, in 
initFromArgv
func(self, **options)
  File "/usr/lib/python2.7/dist-packages/pyrit_cli.py", line 163, in new_f
f(*args, **kwds)
  File "/usr/lib/python2.7/dist-packages/pyrit_cli.py", line 447, in analyze
parser = self._getParser(capturefile)
  File "/usr/lib/python2.7/dist-packages/pyrit_cli.py", line 179, in _getParser
parser.parse_pcapdevice(dev)
  File "/usr/lib/python2.7/dist-packages/cpyrit/pckttools.py", line 601, in 
parse_pcapdevice
self.parse_packet(pckt)
  File "/usr/lib/python2.7/dist-packages/cpyrit/pckttools.py", line 614, in 
parse_packet
if dot11_pckt.isFlagSet('type', 'Control'):
  File "/usr/lib/python2.7/dist-packages/cpyrit/pckttools.py", line 66, in 
isFlagSet
return (1 << field.names.index([value])) & self.__getattr__(name) != 0
AttributeError: 'BitEnumField' object has no attribute 'names'

It's caused by the new version of python-scapy (2.3.3).

Here is a patch to fix it.
The patch is from the https://github.com/JPaulMora/Pyrit repo (dev branch):
https://github.com/JPaulMora/Pyrit/commit/14ec997174b8e8fd20d22b6a97c57e19633f12a0

John Mora seems to have taken maintenance of pyrit and should consider tracking 
new release from this repository.

Consider joining the pkg-security team, we could co-maintain pyrit there:
https://wiki.debian.org/Teams/pkg-security

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

Kernel: Linux 4.8.0-2-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 pyrit depends on:
ii  libc62.24-8
ii  libpcap0.8   1.8.1-3
ii  libssl1.0.2  1.0.2j-4
ii  python   2.7.13-1
pn  python:any   

Versions of packages pyrit recommends:
ii  python-scapy   2.3.3-1
ii  python-sqlalchemy  1.0.15+ds1-1

Versions of packages pyrit suggests:
ii  python-mysqldb   1.3.7-1+b1
ii  python-psycopg2  2.6.2-1

-- no debconf information
Subject: Update isinstance(EnumField) for scapy 2.3.3+
 scapy 2.3.2- requires that scapy.fields.EnumField is passed to
 isinstance, while scapy 2.3.3+ needs scapy.fields._EnumField.
 This patch accomodates pyrit for both versions.
Author: Ilya Terentyev 
Origin: 
https://github.com/JPaulMora/Pyrit/commit/14ec997174b8e8fd20d22b6a97c57e19633f12a0
Bug: https://github.com/JPaulMora/Pyrit/issues/500
Bug-Kali: https://bugs.kali.org/view.php?id=3801
Date: Tue, 1 Nov 2016 20:40:15 +0300
Forwarded: not-needed
Last-Update: 2017-01-06

---
 cpyrit/pckttools.py | 13 -
 1 file changed, 12 insertions(+), 1 deletion(-)

diff --git a/cpyrit/pckttools.py b/cpyrit/pckttools.py
index 326829d..d58fff1 100644
--- a/cpyrit/pckttools.py
+++ b/cpyrit/pckttools.py
@@ -54,12 +54,23 @@
 scapy.layers.dot11.PrismHeader)
 
 
+def isEnumField(f):
+"""Return True if f is an instance of EnumField.  This function tries to be
+   portable: scapy versions 2.3.2 and earlier need isinstance(EnumField),
+   while scapy 2.3.3+ requires isinstance(_EnumField).
+"""
+try:
+return isinstance(f, scapy.fields._EnumField)
+except AttributeError:
+return isinstance(f, scapy.fields.EnumField)
+
+
 def isFlagSet(self, name, value):
 """Return True if the given field 'includes' the given value.
Exact behaviour of this function is specific to the field-type.
 """
 field, val = self.getfield_and_val(name)
-if isinstance(field, scapy.fields.EnumField):
+if isEnumField(field):
 if val not in field.i2s:
 return False
 return field.i2s[val] == value
--- End 

Bug#854343: network-manager: The search domain string in resolv.conf is being duplicated leading to problems with DNS

[Tilo Villwock]

> Would be great if you can test with this patch applied and report
> back.

So this fixed the problem for me. I patched the source tarball I got
from apt source and created a new package with:

dpkg-buildpackage -rfakeroot -uc -b

I only installed the newly created network-manager_1.6.0 package
though. When this is fixed and a new version gets into the
repositories. Will my own package be removed automatically in favor of
the new one?

Thanks

--Tilo

Bug#854341: libchado-perl: FTBFS: The following enviroment variables not detected: CHADO_DB_USERNAME

[olivier sallou]

Le mar. 14 févr. 2017 à 08:36, Andreas Tille  a écrit :

> tags 854341 help
> thanks
>
> Hi,
>
> I admit I have no idea how to fix this.  Help from people with
> Perl background would be really appreciated.
>

I just made a build attempt (1-31-3) with pbuilder, updated right before
build, based on latest svn source and it built fine
Onyl difference is make -j4 for you and make -j1 for me (automatic update
by debhelper?)

Olivier

>
> On Mon, Feb 06, 2017 at 03:40:09PM +0100, Andreas Tille wrote:
> > ...
> >
> > I'm running later into
> >
> > ...
> >dh_auto_install -O--buildsystem=perl_makemaker
> > make -j4 install DESTDIR=/build/libchado-perl-1.31/debian/tmp
> AM_UPDATE_INFO_DIR=no PREFIX=/usr
> > make[1]: Entering directory '/build/libchado-perl-1.31'
> > "/usr/bin/perl" "/build/libchado-perl-1.31/install_util/conf_install.pl"
> 'GMOD_ROOT=/build/libchado-perl-1.31/debian/libchado-perl/usr/share/gmod/chado'
> 'VERSION=1.31'
> > "/usr/bin/perl" "/build/libchado-perl-1.31/install_util/src_install.pl"
> 'GMOD_ROOT=/build/libchado-perl-1.31/debian/libchado-perl/usr/share/gmod/chado'
> > couldn't open
> /build/libchado-perl-1.31/debian/libchado-perl/usr/share/gmod/chado/conf
> directory for reading:No such file or directory
> > Makefile:1222: recipe for target 'src_install' failed
> >
> >
> > which is pretty strange since
> >
> > # ls -l
> /build/libchado-perl-1.31/debian/libchado-perl/usr/share/gmod/chado/conf
> > total 8
> > -rw-r--r-- 1 pbuilder pbuilder 221 Feb  6 11:06 gmod-chado.conf
> > -rw-r--r-- 1 pbuilder pbuilder 167 Feb  6 11:06 gmod.conf
> >
> >
> >
> > > Glancing quickly at Makefile.PL and debian/rules it looks like the
> > > variable names have changed (eg. was DBUSER, etc.).
> >
> > The variable names have not changed in any recent upload and as you can
> > see DBUSER etc are used.
> >
> > Does anybody else have some idea?
>
> Kind regards
>
>Andreas.
>
> --
> http://fam-tille.de
>

Processed: pyrit: diff for NMU version 0.4.0-7.1

[Debian Bug Tracking System]

Processing control commands:

> tags 850692 + patch
Bug #850692 [pyrit] pyrit: failed with 'BitEnumField' object has no attribute 
'names'
Ignoring request to alter tags of bug #850692 to the same tags previously set
> tags 850692 + pending
Bug #850692 [pyrit] pyrit: failed with 'BitEnumField' object has no attribute 
'names'
Added tag(s) pending.

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

Bug#850692: pyrit: diff for NMU version 0.4.0-7.1

[Gianfranco Costamagna]

Control: tags 850692 + patch
Control: tags 850692 + pending

Dear maintainer,

I've prepared an NMU for pyrit (versioned as 0.4.0-7.1) and
uploaded it to DELAYED/0.
Regards.

G.
diff -Nru pyrit-0.4.0/debian/changelog pyrit-0.4.0/debian/changelog
--- pyrit-0.4.0/debian/changelog	2016-04-17 16:31:10.0 +0200
+++ pyrit-0.4.0/debian/changelog	2017-02-14 10:28:20.0 +0100
@@ -1,3 +1,12 @@
+pyrit (0.4.0-7.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  [ Sophie Brun ]
+  * debian/patches/update-for-scapy-2.3.3.patch:
+- fix build failure with new python-scapy (Closes: #850692)
+
+ -- Gianfranco Costamagna   Tue, 14 Feb 2017 10:27:30 +0100
+
 pyrit (0.4.0-7) unstable; urgency=medium
 
   * d/control:
diff -Nru pyrit-0.4.0/debian/patches/series pyrit-0.4.0/debian/patches/series
--- pyrit-0.4.0/debian/patches/series	2016-03-21 22:33:10.0 +0100
+++ pyrit-0.4.0/debian/patches/series	2017-02-14 10:27:30.0 +0100
@@ -1,3 +1,4 @@
 0006-custom-config-file.patch
 0014-performancecounter-handle-empty-result-gracefully.patch
 0015-increase-timeout-in-unittests.patch
+update-for-scapy-2.3.3.patch
diff -Nru pyrit-0.4.0/debian/patches/update-for-scapy-2.3.3.patch pyrit-0.4.0/debian/patches/update-for-scapy-2.3.3.patch
--- pyrit-0.4.0/debian/patches/update-for-scapy-2.3.3.patch	1970-01-01 01:00:00.0 +0100
+++ pyrit-0.4.0/debian/patches/update-for-scapy-2.3.3.patch	2017-02-14 10:35:17.0 +0100
@@ -0,0 +1,45 @@
+Subject: Update isinstance(EnumField) for scapy 2.3.3+
+ scapy 2.3.2- requires that scapy.fields.EnumField is passed to
+ isinstance, while scapy 2.3.3+ needs scapy.fields._EnumField.
+ This patch accomodates pyrit for both versions.
+Author: Ilya Terentyev 
+Origin: https://github.com/JPaulMora/Pyrit/commit/14ec997174b8e8fd20d22b6a97c57e19633f12a0
+Bug: https://github.com/JPaulMora/Pyrit/issues/500
+Bug-Kali: https://bugs.kali.org/view.php?id=3801
+Date: Tue, 1 Nov 2016 20:40:15 +0300
+Forwarded: not-needed
+Last-Update: 2017-01-06
+
+---
+ cpyrit/pckttools.py | 13 -
+ 1 file changed, 12 insertions(+), 1 deletion(-)
+
+diff --git a/cpyrit/pckttools.py b/cpyrit/pckttools.py
+index 326829d..d58fff1 100644
+--- a/cpyrit/pckttools.py
 b/cpyrit/pckttools.py
+@@ -54,12 +54,23 @@
+ scapy.layers.dot11.PrismHeader)
+ 
+ 
++def isEnumField(f):
++"""Return True if f is an instance of EnumField.  This function tries to be
++   portable: scapy versions 2.3.2 and earlier need isinstance(EnumField),
++   while scapy 2.3.3+ requires isinstance(_EnumField).
++"""
++try:
++return isinstance(f, scapy.fields._EnumField)
++except AttributeError:
++return isinstance(f, scapy.fields.EnumField)
++
++
+ def isFlagSet(self, name, value):
+ """Return True if the given field 'includes' the given value.
+Exact behaviour of this function is specific to the field-type.
+ """
+ field, val = self.getfield_and_val(name)
+-if isinstance(field, scapy.fields.EnumField):
++if isEnumField(field):
+ if val not in field.i2s:
+ return False
+ return field.i2s[val] == value

Processed: found 853232 in 5.1-1.1

[Debian Bug Tracking System]

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

> found 853232 5.1-1.1
Bug #853232 [libphp-phpmailer] libphp-phpmailer: CVE-2017-5223
Marked as found in versions libphp-phpmailer/5.1-1.1.
> thanks
Stopping processing here.

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

Processed: found 854336 in 0.12.8-2

[Debian Bug Tracking System]

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

> found 854336 0.12.8-2
Bug #854336 [src:spice] CVE-2016-9577 CVE-2016-9578
Marked as found in versions spice/0.12.8-2.
> thanks
Stopping processing here.

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

Processed: found 854278 in 2.6.2-0.1

[Debian Bug Tracking System]

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

> found 854278 2.6.2-0.1
Bug #854278 [mp3splt] CVE-2017-5666
Marked as found in versions mp3splt/2.6.2-0.1.
> thanks
Stopping processing here.

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

Processed: tagging 854278

[Debian Bug Tracking System]

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

> tags 854278 + upstream
Bug #854278 [mp3splt] CVE-2017-5666
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Processed: found 854733 in 1.30.0+dfsg-1

[Debian Bug Tracking System]

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

> found 854733 1.30.0+dfsg-1
Bug #854733 [src:zoneminder] CVE-2017-5367 / CVE-2017-5367 / CVE-2017-5368
Marked as found in versions zoneminder/1.30.0+dfsg-1.
> thanks
Stopping processing here.

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

Bug#854343: network-manager: The search domain string in resolv.conf is being duplicated leading to problems with DNS

[Martin Haaß]

The patch you mention fixed the behavior for me.
Thx,
 Martin
On 02/13/2017 10:28 PM, Michael Biebl wrote:

Am 10.02.2017 um 09:49 schrieb Tilo Villwock:


Bug report filed:

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


Upstream provided a patch at
https://bugzilla.gnome.org/show_bug.cgi?id=778430#c10

Would be great if you can test with this patch applied and report back.

Regards,
Michael

Bug#835531: fail of test_csr_correct_output_faster_than_scipy at times (FTBFS)

[Daniel Stender]

On 14.02.2017 08:59, Ole Streicher wrote:
> Hi Daniel,
> 
> I don't really see why you declare this failure as "serious". From the
> source (and the bug name), it basically means that theano took a bit
> longer to calculate than scipy for the same calculation. This may depend
> on the scipy version and optimization, and also on the timing (load)
> during the test -- it is calendar time what is taken here.
> 
> IMO, the failure is severity "normal", maybe you could consider
> resetting the severity to this value?
> 
> Best regards
> 
> Ole

Yes, in the meanwhile, I've thought into the same direction. The latest build 
(0.8.2-5~exp1)
succeeded again without this appeared anywhere. I'll do that.

Daniel

-- 
4096R/DF5182C8
Debian Developer (sten...@debian.org)
http://www.danielstender.com/

Bug#850692: pyrit: failed with 'BitEnumField' object has no attribute 'names'

[Raphael Hertzog]

On Mon, 09 Jan 2017, Sophie Brun wrote:
> AttributeError: 'BitEnumField' object has no attribute 'names'
[...]
> Consider joining the pkg-security team, we could co-maintain pyrit there:
> https://wiki.debian.org/Teams/pkg-security

Hello Christian,

you haven't replied to this bug in more than a month. Someone upgraded it
to RC severity because the package FTBFS actually.

So we should handle it promptly now. In the pkg-security team, we're
willing to help you on this package... please reply and let us know how to
proceed.

If I don't hear back from you, I'll assume that it's ok to move the
package to pkg-security.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/

Bug#835949: linux-grsec: non-standard gcc/g++ used for build (gcc-5)

[Yves-Alexis Perez]

On Tue, 2017-02-14 at 15:32 +0900, Hideki Yamane wrote:
> > On Mon, 29 Aug 2016 16:15:34 +0200 Yves-Alexis Perez  
> > wrote:
> > I follow src:linux package on this, so I'll do the switch when they do it 
> > (and
> > will close this bug at that point).
> 
>  It seems that src:linux was fixed
>  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835957

Yes I know. I'm waiting for the src:linux 4.9.9 upload to upload linux-grsec.
-- 
Yves-Alexis

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

Processed: Re: Bug#855103: Rendering fails on wayland/hidpi

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://bugs.webkit.org/show_bug.cgi?id=168128
Bug #855103 [libwebkit2gtk-4.0-37] Rendering fails on wayland/hidpi
Set Bug forwarded-to-address to 
'https://bugs.webkit.org/show_bug.cgi?id=168128'.
> tags -1 upstream fixed-upstream
Bug #855103 [libwebkit2gtk-4.0-37] Rendering fails on wayland/hidpi
Added tag(s) fixed-upstream and upstream.

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

Bug#855103: Rendering fails on wayland/hidpi

[Alberto Garcia]

Control: forwarded -1 https://bugs.webkit.org/show_bug.cgi?id=168128
Control: tags -1 upstream fixed-upstream

On Tue, Feb 14, 2017 at 08:54:16AM +0100, Sjoerd Simons wrote:

> Both epiphany and evolution show blank output when trying to render
> website/e-mails. Downgrading libwebkit2gtk-4.0-37 to 2.14.3 seems to
> solve the issue.

webkitgtk 2.14.5 is about to be published with the fix for this.

Berto

Processed: found 854272 in 1.30.0+dfsg-1

[Debian Bug Tracking System]

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

> found 854272 1.30.0+dfsg-1
Bug #854272 [src:zoneminder] CVE-2016-10201 CVE-2016-10202 CVE-2016-10203 
CVE-2016-10204 CVE-2016-10205 CVE-2016-10206
Marked as found in versions zoneminder/1.30.0+dfsg-1.
> thanks
Stopping processing here.

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

Bug#835531: fail of test_csr_correct_output_faster_than_scipy at times (FTBFS)

[Ole Streicher]

Hi Daniel,

I don't really see why you declare this failure as "serious". From the
source (and the bug name), it basically means that theano took a bit
longer to calculate than scipy for the same calculation. This may depend
on the scipy version and optimization, and also on the timing (load)
during the test -- it is calendar time what is taken here.

IMO, the failure is severity "normal", maybe you could consider
resetting the severity to this value?

Best regards

Ole

Bug#847311: amavisd-new: After the last Debian update Amavis does not read data type float from Mysql DB correctly. All fields are "0".

[LOC]

desc spamfilter_users
 
Field Type Null Key Default Extra  idint(11) 
unsignedNOPRINULLauto_incrementsys_useridint(11) unsignedNO 0 
sys_groupidint(11) unsignedNO 0 sys_perm_uservarchar(5)NO   
sys_perm_groupvarchar(5)NO   sys_perm_othervarchar(5)NO   server_idint(11) 
unsignedNO 0 prioritytinyint(3) unsignedNO 7 policy_idint(11) unsignedNO 1 
emailvarchar(255)NOUNI  fullnamevarchar(64)YES NULL localvarchar(1)YES NULL  
#
 
desc spamfilter_policy
 
Field Type Null Key Default Extra  idint(11) 
unsignedNOPRINULLauto_incrementsys_useridint(11) unsignedNO 0 
sys_groupidint(11) unsignedNO 0 sys_perm_uservarchar(5)NO   
sys_perm_groupvarchar(5)NO   sys_perm_othervarchar(5)NO   
policy_namevarchar(64)YES NULL virus_loverenum('N','Y')YES NULL 
spam_loverenum('N','Y')YES NULL banned_files_loverenum('N','Y')YES NULL 
bad_header_loverenum('N','Y')YES NULL bypass_virus_checksenum('N','Y')YES NULL 
bypass_spam_checksenum('N','Y')YES NULL bypass_banned_checksenum('N','Y')YES 
NULL bypass_header_checksenum('N','Y')YES NULL 
spam_modifies_subjenum('N','Y')YES NULL virus_quarantine_tovarchar(255)YES NULL 
spam_quarantine_tovarchar(255)YES NULL banned_quarantine_tovarchar(255)YES NULL 
bad_header_quarantine_tovarchar(255)YES NULL clean_quarantine_tovarchar(255)YES 
NULL other_quarantine_tovarchar(255)YES NULL spam_tag_levelfloatYES NULL 
spam_tag2_levelfloatYES NULL spam_kill_levelfloatYES NULL spa
m_dsn_cutoff_levelfloatYES NULL spam_quarantine_cutoff_levelfloatYES NULL 
addr_extension_virusvarchar(64)YES NULL addr_extension_spamvarchar(64)YES NULL 
addr_extension_bannedvarchar(64)YES NULL 
addr_extension_bad_headervarchar(64)YES NULL warnvirusrecipenum('N','Y')YES 
NULL warnbannedrecipenum('N','Y')YES NULL warnbadhrecipenum('N','Y')YES NULL 
newvirus_adminvarchar(64)YES NULL virus_adminvarchar(64)YES NULL 
banned_adminvarchar(64)YES NULL bad_header_adminvarchar(64)YES NULL 
spam_adminvarchar(64)YES NULL spam_subject_tagvarchar(64)YES NULL 
spam_subject_tag2varchar(64)YES NULL message_size_limitint(11) unsignedYES NULL 
banned_rulenamesvarchar(64)YES NULL policyd_quota_inint(11)NO -1 
policyd_quota_in_periodint(11)NO 24 policyd_quota_outint(11)NO -1 
policyd_quota_out_periodint(11)NO 24 policyd_greylistenum('Y','N')NO N  
#
 
SELECT *,spamfilter_users.id FROM spamfilter_users LEFT JOIN spamfilter_policy 
ON
spamfilter_users.policy_id=spamfilter_policy.id WHERE spamfilter_users.email IN 
('recei...@domain2.com','@domain2.com','@.domain2.com','@.com','@.') ORDER BY 
spamfilter_users.priority DESC;
 
id sys_userid sys_groupid sys_perm_user sys_perm_group sys_perm_other server_id 
priority policy_id email fullname local id sys_userid sys_groupid sys_perm_user 
sys_perm_group sys_perm_other policy_name virus_lover spam_lover 
banned_files_lover bad_header_lover bypass_virus_checks bypass_spam_checks 
bypass_banned_checks bypass_header_checks spam_modifies_subj 
virus_quarantine_to spam_quarantine_to banned_quarantine_to 
bad_header_quarantine_to clean_quarantine_to other_quarantine_to spam_tag_level 
spam_tag2_level spam_kill_level spam_dsn_cutoff_level 
spam_quarantine_cutoff_level addr_extension_virus addr_extension_spam 
addr_extension_banned addr_extension_bad_header warnvirusrecip warnbannedrecip 
warnbadhrecip newvirus_admin virus_admin banned_admin bad_header_admin 
spam_admin spam_subject_tag spam_subject_tag2 message_size_limit 
banned_rulenames policyd_quota_in policyd_quota_in_period policyd_quota_out 
policyd_quota_out_period policyd_greylist id  411riudriud 151receiver@do
main2.comreceiver@domain2.comY110riudriudrNormalniN  -504.5154.515  
  NNN   0 -124-124N4 
#
 
Content of these 2 tables are still the same, nothing is changing them. Data 
types of all the affected fields and it's field names are consistent with 
amavisd-new docs and confirmed to be working before the mentioned update of my 
debian system in the late november.
 
Jakub.
__

Od: Brian May 
Komu: Henrique de Moraes Holschuh , 847...@bugs.debian.org, LOC 
, 847...@bugs.debian.org, 847311-submit...@bugs.debian.org
Datum: 13.02.2017 22:19
Předmět: Bug#847311: amavisd-new: After the last Debian update Amavis does not read data 
type float from Mysql DB correctly. All fields are "0".


Henrique de Moraes Holschuh  writes:

> LOC, could you send (to this bug report) a dump of the *schema* for the
> relevant tables (the ones returning 0 instead of the correct float) ?

LOC, please connect to the database using the mysql client, and type in
the following commands. Send back the results.

desc spamfilter_users;
desc spamfilter_policy;