Bug#838888: dh-haskell: "Experimental push on scalar is now forbidden at [..]/Buildsystem/haskell.pm"

[Chris Lamb]

Source: dh-haskell
Version: 0.2
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,

dh-haskell now causes FTBFS in other packages. For example, here is
haskell-pqueue:
  
  
**
  ** Building haskell-pqueue 1.3.1.1-1 on amd64 
  **
  
**
  
   dpkg-buildpackage -rfakeroot -D -us -uc -b
  dpkg-buildpackage: info: source package haskell-pqueue
  dpkg-buildpackage: info: source version 1.3.1.1-1
  dpkg-buildpackage: info: source distribution unstable
  dpkg-buildpackage: info: source changed by Joachim Breitner 

   dpkg-source --before-build haskell-pqueue-1.3.1.1
  dpkg-buildpackage: info: host architecture amd64
   fakeroot debian/rules clean
  dh clean --with haskell --buildsystem=haskell
 dh_testdir -O--buildsystem=haskell
 dh_auto_clean -O--buildsystem=haskell
  dh_auto_clean: unable to load build system class 'haskell': Experimental push 
on scalar is now forbidden at 
/usr/share/perl5/Debian/Debhelper/Buildsystem/haskell.pm line 469, near "$_ }"
  BEGIN not safe after errors--compilation aborted at 
/usr/share/perl5/Debian/Debhelper/Buildsystem/haskell.pm line 472.
  Compilation failed in require at (eval 2) line 2.
  BEGIN failed--compilation aborted at (eval 2) line 2.
  
  debian/rules:4: recipe for target 'clean' failed
  make: *** [clean] Error 255

  [..]

The full build log is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


haskell-pqueue.1.3.1.1-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#835754: marked as done (z3: FTBFS: util/debug.cpp:79:38: error: cannot convert 'std::basic_istream' to 'bool' in initialization)

[Debian Bug Tracking System]

Your message dated Mon, 26 Sep 2016 06:36:50 +
with message-id 
and subject line Bug#835754: fixed in z3 4.4.1-0.3
has caused the Debian Bug report #835754,
regarding z3: FTBFS: util/debug.cpp:79:38: error: cannot convert 
'std::basic_istream' to 'bool' in initialization
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.)


-- 
835754: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835754
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: z3
Version: 4.4.1-0.2
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,

z3 fails to build from source in unstable/amd64:

  [..]

 dh_ocamlinit -O--parallel
 debian/rules override_dh_auto_configure
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20160828113355.M8pdxROBix.db.z3/z3-4.4.1'
  if [ yes = yes ]; then \
sed -i 's/^DOTNET_ENABLED=.*/DOTNET_ENABLED=True/' scripts/mk_util.py; \
  else \
sed -i 's/^DOTNET_ENABLED=.*/DOTNET_ENABLED=False/' scripts/mk_util.py; 
\
  fi
  if [ yes = yes ]; then \
python scripts/mk_make.py --java --ml 
--prefix=/home/lamby/temp/cdt.20160828113355.M8pdxROBix.db.z3/z3-4.4.1/debian/tmp/usr;
 \
  else \
python scripts/mk_make.py --ml 
--prefix=/home/lamby/temp/cdt.20160828113355.M8pdxROBix.db.z3/z3-4.4.1/debian/tmp/usr;
 \
  fi
  opt = --java, arg = 
  opt = --ml, arg = 
  opt = --prefix, arg = 
/home/lamby/temp/cdt.20160828113355.M8pdxROBix.db.z3/z3-4.4.1/debian/tmp/usr
  New component: 'util'
  New component: 'polynomial'
  New component: 'sat'
  New component: 'nlsat'
  New component: 'hilbert'
  New component: 'simplex'
  New component: 'interval'
  New component: 'realclosure'
  New component: 'subpaving'
  New component: 'ast'
  New component: 'rewriter'
  New component: 'normal_forms'
  New component: 'model'
  New component: 'tactic'
  New component: 'substitution'
  New component: 'parser_util'
  New component: 'grobner'
  New component: 'euclid'
  New component: 'core_tactics'
  New component: 'sat_tactic'
  New component: 'arith_tactics'
  New component: 'nlsat_tactic'
  New component: 'subpaving_tactic'
  New component: 'aig_tactic'
  New component: 'solver'
  New component: 'interp'
  New component: 'cmd_context'
  New component: 'extra_cmds'
  New component: 'smt2parser'
  New component: 'proof_checker'
  New component: 'simplifier'
  New component: 'fpa'
  New component: 'macros'
  New component: 'pattern'
  New component: 'bit_blaster'
  New component: 'smt_params'
  New component: 'proto_model'
  New component: 'smt'
  New component: 'user_plugin'
  New component: 'bv_tactics'
  New component: 'fuzzing'
  New component: 'smt_tactic'
  New component: 'sls_tactic'
  New component: 'qe'
  New component: 'duality'
  New component: 'muz'
  New component: 'dataflow'
  New component: 'transforms'
  New component: 'rel'
  New component: 'pdr'
  New component: 'clp'
  New component: 'tab'
  New component: 'bmc'
  New component: 'ddnf'
  New component: 'duality_intf'
  New component: 'fp'
  New component: 'nlsat_smt_tactic'
  New component: 'smtlogic_tactics'
  New component: 'fpa_tactics'
  New component: 'ufbv_tactic'
  New component: 'sat_solver'
  New component: 'portfolio'
  New component: 'smtparser'
  New component: 'opt'
  New component: 'api'
  New component: 'shell'
  New component: 'test'
  New component: 'api_dll'
  New component: 'dotnet'
  New component: 'java'
  New component: 'ml'
  New component: 'cpp'
  Python bindings directory was detected.
  New component: 'cpp_example'
  New component: 'iz3'
  New component: 'z3_tptp'
  New component: 'c_example'
  New component: 'maxsat'
  New component: 'dotnet_example'
  New component: 'java_example'
  New component: 'py_example'
  Generated 'src/util/version.h'
  Updated 'src/api/dotnet/Properties/AssemblyInfo'
  Generated 'src/nlsat/nlsat_params.hpp'
  Generated 'src/tactic/sls/sls_params.hpp'
  Generated 'src/math/realclosure/rcf_params.hpp'
  Generated 'src/math/polynomial/algebraic_params.hpp'
  Generated 'src/muz/base/fixedpoint_params.hpp'
  Generated 'src/ast/pp_params.hpp'
  Generated 'src/ast/fpa/fpa2bv_rewriter_params.hpp'
  Generated 'src/ast/simplifier/bv_simplifier_params_helper.hpp'
  Generated 'src/ast/simplifier/arith_simplifier_params_helper.hpp'
  Generated 'src/ast/simplifier/array_simplifier_params_helper.hpp'
  Generated 'src/ast/normal_forms/nnf_params.hpp'
  Generated 'src/ast/rewriter/rewriter_params.hpp'
  Generated 'src/ast/rewriter/b

Bug#835743: marked as done (z3: FTBFS: ../src/util/mpz.cpp:137:8: error: call of overloaded 'set(mpz&, long unsigned int)' is ambiguous)

[Debian Bug Tracking System]

Your message dated Mon, 26 Sep 2016 06:36:50 +
with message-id 
and subject line Bug#835743: fixed in z3 4.4.1-0.3
has caused the Debian Bug report #835743,
regarding z3: FTBFS: ../src/util/mpz.cpp:137:8: error: call of overloaded 
'set(mpz&, long unsigned int)' is ambiguous
to be marked as done.

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

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


-- 
835743: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835743
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: z3
Version: 4.4.1-0.2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160828 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):
> make[2]: Entering directory '/<>/build'
> src/shell/datalog_frontend.cpp
> src/shell/gparams_register_modules.cpp
> src/shell/z3_log_frontend.cpp
> src/shell/main.cpp
> src/shell/install_tactic.cpp
> src/shell/dimacs_frontend.cpp
> src/shell/mem_initializer.cpp
> src/shell/opt_frontend.cpp
> src/shell/smtlib_frontend.cpp
> src/api/api_params.cpp
> src/api/api_opt.cpp
> src/api/api_algebraic.cpp
> src/api/api_log_macros.cpp
> src/api/api_quant.cpp
> src/api/api_solver_old.cpp
> src/api/api_ast_vector.cpp
> src/api/api_bv.cpp
> src/api/api_context.cpp
> src/api/api_datalog.cpp
> src/api/api_arith.cpp
> src/api/api_ast.cpp
> src/api/api_polynomial.cpp
> src/api/api_ast_map.cpp
> src/api/api_numeral.cpp
> src/api/api_interp.cpp
> src/api/api_stats.cpp
> src/api/api_model.cpp
> src/api/api_config_params.cpp
> src/api/api_solver.cpp
> src/api/z3_replayer.cpp
> src/api/api_array.cpp
> src/api/api_pb.cpp
> src/api/api_goal.cpp
> src/api/api_commands.cpp
> src/api/api_log.cpp
> src/api/api_rcf.cpp
> src/api/api_fpa.cpp
> src/api/api_parsers.cpp
> src/api/api_datatype.cpp
> src/api/api_user_theory.cpp
> src/api/api_tactic.cpp
> src/opt/wmax.cpp
> src/opt/opt_pareto.cpp
> src/opt/opt_cmds.cpp
> src/opt/hitting_sets.cpp
> src/opt/maxsmt.cpp
> src/opt/pb_sls.cpp
> src/opt/opt_context.cpp
> src/opt/mus.cpp
> src/opt/bcd2.cpp
> src/opt/fu_malik.cpp
> src/opt/maxsls.cpp
> src/opt/opt_solver.cpp
> src/opt/maxres.cpp
> src/opt/mss.cpp
> src/opt/maxhs.cpp
> src/opt/optsmt.cpp
> src/parsers/smt/smtparser.cpp
> src/parsers/smt/smtlib.cpp
> src/parsers/smt/smtlib_solver.cpp
> src/tactic/portfolio/default_tactic.cpp
> src/tactic/portfolio/smt_strategic_solver.cpp
> src/sat/sat_solver/inc_sat_solver.cpp
> src/tactic/ufbv/ufbv_tactic.cpp
> src/tactic/ufbv/ufbv_rewriter.cpp
> src/tactic/ufbv/ufbv_rewriter_tactic.cpp
> src/tactic/ufbv/quasi_macros_tactic.cpp
> src/tactic/ufbv/macro_finder_tactic.cpp
> src/tactic/fpa/qffp_tactic.cpp
> src/tactic/fpa/fpa2bv_model_converter.cpp
> src/tactic/fpa/fpa2bv_tactic.cpp
> src/tactic/smtlogics/qfufnra_tactic.cpp
> src/tactic/smtlogics/nra_tactic.cpp
> src/tactic/smtlogics/qfnra_tactic.cpp
> src/tactic/smtlogics/qfufbv_tactic.cpp
> src/tactic/smtlogics/quant_tactics.cpp
> src/tactic/smtlogics/qfbv_tactic.cpp
> src/tactic/smtlogics/qfuf_tactic.cpp
> src/tactic/smtlogics/qflia_tactic.cpp
> src/tactic/smtlogics/qfnia_tactic.cpp
> src/tactic/smtlogics/qfidl_tactic.cpp
> src/tactic/smtlogics/qfaufbv_tactic.cpp
> src/tactic/smtlogics/qflra_tactic.cpp
> src/tactic/smtlogics/qfauflia_tactic.cpp
> src/tactic/nlsat_smt/nl_purify_tactic.cpp
> src/muz/fp/dl_cmds.cpp
> src/muz/fp/datalog_parser.cpp
> src/muz/fp/dl_register_engine.cpp
> src/muz/fp/horn_tactic.cpp
> src/muz/duality/duality_dl_interface.cpp
> src/muz/ddnf/ddnf.cpp
> src/muz/bmc/dl_bmc_engine.cpp
> src/muz/tab/tab_context.cpp
> src/muz/clp/clp_context.cpp
> src/muz/pdr/pdr_generalizers.cpp
> src/muz/pdr/pdr_farkas_learner.cpp
> src/muz/pdr/pdr_closure.cpp
> src/muz/pdr/pdr_manager.cpp
> src/muz/pdr/pdr_smt_context_manager.cpp
> src/muz/pdr/pdr_prop_solver.cpp
> src/muz/pdr/pdr_reachable_cache.cpp
> src/muz/pdr/pdr_dl_interface.cpp
> src/muz/pdr/pdr_context.cpp
> src/muz/pdr/pdr_util.cpp
> src/muz/pdr/pdr_sym_mux.cpp
> src/muz/rel/dl_mk_similarity_compressor.cpp
> src/muz/rel/dl_bound_relation.cpp
> src/muz/rel/dl_interval_relation.cpp
> src/muz/rel/dl_sieve_relation.cpp
> src/muz/rel/udoc_relation.cpp
> src/muz/rel/dl_compiler.cpp
> src/muz/rel/karr_relation.cpp
> src/muz/rel/dl_sparse_table.cpp
> src/muz/rel/dl_finite_product_relation.cpp
> src/muz/rel/dl_base.cpp
> src/muz/rel/dl_mk_partial_equiv.cpp
> src/muz/rel/dl_table.cpp
> src/muz/rel/tbv.cpp
> src/muz/rel/doc.cpp
> src/muz/rel/dl_relation_manager.cpp
> src/muz/rel/dl_mk_explanations.cpp
> src/muz/rel/dl_check_table.cpp
> src/muz/rel/dl_mk_simple_joins.cpp
> 

Bug#835743: z3: FTBFS: ../src/util/mpz.cpp:137:8: error: call of overloaded 'set(mpz&, long unsigned int)' is ambiguous

[Gianfranco Costamagna]

Hi,
> thanks for the patches!
> (feel free to ping directly in case of RC bug fixes if you need a sponsor!)
> 
at the end I'm uploading it with a new couple of casts (and patches forwarded 
upstream).

I hope I did the cast correctly, the build is fine now.


G.
diff -Nru z3-4.4.1/debian/changelog z3-4.4.1/debian/changelog
--- z3-4.4.1/debian/changelog   2016-07-20 13:07:58.0 +0200
+++ z3-4.4.1/debian/changelog   2016-09-26 07:28:12.0 +0200
@@ -1,3 +1,19 @@
+z3 (4.4.1-0.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Fabian Wolff ]
+  * debian/patches/f02d273ee39ae047222e362c37213d29135dc661.patch:
+Fix build failure with new gnu++14 standard. (Closes: #835754)
+  * debian/patches/27399309009314f56cdfbd8333f287b1a9b7a3a6.patch:
+Fix build failure with new compiler and clang. (Closes: #835743)
+
+  [ Gianfranco Costamagna ]
+  * debian/patches/fix-build.patch: tweak the casts a little bit
+more to really fix 835743.
+
+ -- Gianfranco Costamagna   Sun, 25 Sep 2016 
23:06:24 +0200
+
 z3 (4.4.1-0.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru 
z3-4.4.1/debian/patches/27399309009314f56cdfbd8333f287b1a9b7a3a6.patch 
z3-4.4.1/debian/patches/27399309009314f56cdfbd8333f287b1a9b7a3a6.patch
--- z3-4.4.1/debian/patches/27399309009314f56cdfbd8333f287b1a9b7a3a6.patch  
1970-01-01 01:00:00.0 +0100
+++ z3-4.4.1/debian/patches/27399309009314f56cdfbd8333f287b1a9b7a3a6.patch  
2016-09-25 23:46:37.0 +0200
@@ -0,0 +1,23 @@
+From 27399309009314f56cdfbd8333f287b1a9b7a3a6 Mon Sep 17 00:00:00 2001
+From: Nuno Lopes 
+Date: Fri, 27 Nov 2015 12:13:44 +
+Subject: [PATCH] fix build with clang
+
+Signed-off-by: Nuno Lopes 
+---
+ src/util/mpz.cpp | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/src/util/mpz.cpp b/src/util/mpz.cpp
+index 8559279..7dca14b 100644
+--- a/src/util/mpz.cpp
 b/src/util/mpz.cpp
+@@ -134,7 +134,7 @@ mpz_manager::mpz_manager():
+ #endif
+ 
+ mpz one(1);
+-set(m_two64, UINT64_MAX);
++set(m_two64, (uint64)UINT64_MAX);
+ add(m_two64, one, m_two64);
+ }
+ 
diff -Nru 
z3-4.4.1/debian/patches/f02d273ee39ae047222e362c37213d29135dc661.patch 
z3-4.4.1/debian/patches/f02d273ee39ae047222e362c37213d29135dc661.patch
--- z3-4.4.1/debian/patches/f02d273ee39ae047222e362c37213d29135dc661.patch  
1970-01-01 01:00:00.0 +0100
+++ z3-4.4.1/debian/patches/f02d273ee39ae047222e362c37213d29135dc661.patch  
2016-09-25 23:46:37.0 +0200
@@ -0,0 +1,23 @@
+From f02d273ee39ae047222e362c37213d29135dc661 Mon Sep 17 00:00:00 2001
+From: Jonathan Wakely 
+Date: Tue, 2 Feb 2016 23:39:11 +
+Subject: [PATCH] Convert stream to bool explicitly
+
+In C++11 there is no implicit conversion from iostream classes to `void*`, 
just an explicit conversion to bool.
+---
+ src/util/debug.cpp | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/src/util/debug.cpp b/src/util/debug.cpp
+index 54c67fe..66676c6 100644
+--- a/src/util/debug.cpp
 b/src/util/debug.cpp
+@@ -76,7 +76,7 @@ void invoke_gdb() {
+ for (;;) {
+ std::cerr << "(C)ontinue, (A)bort, (S)top, (T)hrow exception, Invoke 
(G)DB\n";
+ char result;
+-bool ok = (std::cin >> result);
++bool ok = bool(std::cin >> result);
+ if (!ok) exit(ERR_INTERNAL_FATAL); // happens if std::cin is eof or 
unattached.
+ switch(result) {
+ case 'C':
diff -Nru z3-4.4.1/debian/patches/fix-build.patch 
z3-4.4.1/debian/patches/fix-build.patch
--- z3-4.4.1/debian/patches/fix-build.patch 1970-01-01 01:00:00.0 
+0100
+++ z3-4.4.1/debian/patches/fix-build.patch 2016-09-26 08:08:19.0 
+0200
@@ -0,0 +1,53 @@
+Author: Gianfranco Costamagna 
+Description: Add some more casts to fix the build (Bug: #835743)
+Forwarded: https://github.com/Z3Prover/z3/pull/746
+   https://github.com/Z3Prover/z3/pull/747
+--- z3-4.4.1.orig/src/test/mpff.cpp
 z3-4.4.1/src/test/mpff.cpp
+@@ -207,7 +207,7 @@ static void tst_set64(unsigned N, unsign
+ mpff_manager fm(prec);
+ scoped_mpff a(fm);
+ 
+-fm.set(a, INT64_MAX);
++fm.set(a, static_cast(INT64_MAX));
+ SASSERT(fm.is_int64(a));
+ SASSERT(fm.is_uint64(a));
+ fm.inc(a);
+@@ -221,7 +221,7 @@ static void tst_set64(unsigned N, unsign
+ SASSERT(fm.is_int64(a));
+ SASSERT(fm.is_uint64(a));
+ 
+-fm.set(a, INT64_MIN);
++fm.set(a, static_cast(INT64_MIN));
+ SASSERT(fm.is_int64(a));
+ SASSERT(!fm.is_uint64(a));
+ fm.dec(a);
+@@ -235,7 +235,7 @@ static void tst_set64(unsigned N, unsign
+ SASSERT(fm.is_int64(a));
+ SASSERT(!fm.is_uint64(a));
+ 
+-fm.set(a, UINT64_MAX);
++fm.set(a, static_cast(UINT64_MAX));
+ SASSERT(fm.is_uint64(a));
+ SASSERT(!fm.is_int64(a));
+ fm.inc(a);
+@@ -600,7 +600,7 @@ static void tst_div(unsigned prec) {
+ scoped_mpff a(m), b(m), c(m);
+ m.round_to_plus_inf();
+ m.set(a, 1);
+-m.set(b, UINT64_MAX);
++m.se

Processed: retitle 834504 to imagemagick: CVE-2016-6823: Buffer overflow in bmp file reader

[Debian Bug Tracking System]

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

> retitle 834504 imagemagick: CVE-2016-6823: Buffer overflow in bmp file reader
Bug #834504 {Done: Bastien Roucariès } 
[src:imagemagick] Buffer overflow in bmp file reader
Changed Bug title to 'imagemagick: CVE-2016-6823: Buffer overflow in bmp file 
reader' from 'Buffer overflow in bmp file reader'.
> thanks
Stopping processing here.

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

Processed: retitle 838832 to asterisk: CVE-2016-7551: AST-2016-007 ...

[Debian Bug Tracking System]

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

> retitle 838832 asterisk: CVE-2016-7551: AST-2016-007
Bug #838832 [src:asterisk] asterisk: AST-2016-007
Changed Bug title to 'asterisk: CVE-2016-7551: AST-2016-007' from 'asterisk: 
AST-2016-007'.
> retitle 838833 asterisk: CVE-2016-7550: AST-2016-006
Bug #838833 [src:asterisk] asterisk: AST-2016-006
Changed Bug title to 'asterisk: CVE-2016-7550: AST-2016-006' from 'asterisk: 
AST-2016-006'.
> thanks
Stopping processing here.

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

Bug#838544: marked as done (ext4: ext4_iget:4476: inode #8: comm mount: checksum invalid)

[Debian Bug Tracking System]

Your message dated Mon, 26 Sep 2016 04:23:26 +
with message-id 
and subject line Bug#838544: fixed in linux 4.7.5-1
has caused the Debian Bug report #838544,
regarding ext4: ext4_iget:4476: inode #8: comm mount: checksum invalid
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.)


-- 
838544: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838544
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:linux
Version: 4.7.4-2
Severity: grave
Justification: renders package unusable

When booting with linux-image-4.7.0-1-amd64 4.7.4-2, one of my
filesystems fails to mount with:

ext4_iget:4476: inode #8: comm mount: checksum invalid

A fsck does not find any errors, though, and the mount problem persists.
After rebooting with 4.6, it works.

It seems this is a known problem:

http://www.spinics.net/lists/linux-fsdevel/msg101888.html


Not sure about the severity, but I thought I should prevent it from
migrating to testing until you have looked at it.
--- End Message ---
--- Begin Message ---
Source: linux
Source-Version: 4.7.5-1

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

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

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

Debian distribution maintenance software
pp.
Ben Hutchings  (supplier of updated linux 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: Mon, 26 Sep 2016 01:48:21 +0100
Source: linux
Binary: linux-source-4.7 linux-support-4.7.0-1 linux-doc-4.7 linux-manual-4.7 
linux-kbuild-4.7 linux-cpupower libcpupower1 libcpupower-dev linux-perf-4.7 
libusbip-dev usbip hyperv-daemons lockdep liblockdep4.7 liblockdep-dev 
linux-libc-dev linux-headers-4.7.0-1-all linux-headers-4.7.0-1-all-alpha 
kernel-image-4.7.0-1-alpha-generic-di nic-modules-4.7.0-1-alpha-generic-di 
nic-wireless-modules-4.7.0-1-alpha-generic-di 
nic-shared-modules-4.7.0-1-alpha-generic-di 
serial-modules-4.7.0-1-alpha-generic-di 
usb-serial-modules-4.7.0-1-alpha-generic-di 
ppp-modules-4.7.0-1-alpha-generic-di pata-modules-4.7.0-1-alpha-generic-di 
cdrom-core-modules-4.7.0-1-alpha-generic-di 
scsi-core-modules-4.7.0-1-alpha-generic-di 
scsi-modules-4.7.0-1-alpha-generic-di loop-modules-4.7.0-1-alpha-generic-di 
btrfs-modules-4.7.0-1-alpha-generic-di ext4-modules-4.7.0-1-alpha-generic-di 
isofs-modules-4.7.0-1-alpha-generic-di jfs-modules-4.7.0-1-alpha-generic-di 
xfs-modules-4.7.0-1-alpha-generic-di
 fat-modules-4.7.0-1-alpha-generic-di md-modules-4.7.0-1-alpha-generic-di 
multipath-modules-4.7.0-1-alpha-generic-di usb-modules-4.7.0-1-alpha-generic-di 
usb-storage-modules-4.7.0-1-alpha-generic-di 
fb-modules-4.7.0-1-alpha-generic-di input-modules-4.7.0-1-alpha-generic-di 
event-modules-4.7.0-1-alpha-generic-di mouse-modules-4.7.0-1-alpha-generic-di 
nic-pcmcia-modules-4.7.0-1-alpha-generic-di 
pcmcia-modules-4.7.0-1-alpha-generic-di 
nic-usb-modules-4.7.0-1-alpha-generic-di sata-modules-4.7.0-1-alpha-generic-di 
core-modules-4.7.0-1-alpha-generic-di crc-modules-4.7.0-1-alpha-generic-di 
crypto-modules-4.7.0-1-alpha-generic-di 
crypto-dm-modules-4.7.0-1-alpha-generic-di ata-modules-4.7.0-1-alpha-generic-di 
nbd-modules-4.7.0-1-alpha-generic-di squashfs-modules-4.7.0-1-alpha-generic-di 
virtio-modules-4.7.0-1-alpha-generic-di zlib-modules-4.7.0-1-alpha-generic-di 
fuse-modules-4.7.0-1-alpha-generic-di srm-modules-4.7.0-1-alpha-generic-di 
linux-headers-4.7.0-1-common
 linux-image-4.7.0-1-alpha-generic linux-headers-4.7.0-1-alpha-generic 
linux-image-4.7.0-1-alpha-generic-dbgsym linux-image-4.7.0-1-alpha-smp 
linux-headers-4.7.0-1-alpha-smp linux-image-4.7.0-1-alpha-smp-dbgsym 
linux-headers-4.7.0-1-all-amd64 linux-image-4.7.0-1-amd64-unsigned 
linux-headers-4.7.0-1-amd64 linux-image-4.7.0-1-amd64-dbgsym 
xen-linux-system-4.7.0-1-amd64 linux-headers-4.7.0-1-all-arm64 
linux-image-4.7.0-1-arm64-unsigned linux-headers-4.7.0-1-arm64 
linux-image-4.7.0-1-arm64-dbgsym linux-headers-4.7.0-1-all-armel 
kernel-image-4.7.0-1-marvell-di nic-modules-4.7.0-1-marvell-di 
nic-shared-modules-4.7.0-1-marvell-di usb-serial-modules-4.7.0-1-marvell-di 
ppp-modules-4.7.0-1-marvell-di cdrom-core-modules-4.7

Bug#838334: fixed in valadoc 0.30.0~git20160518-1

[Sebastian Reichel]

Hi,

On Mon, Sep 26, 2016 at 01:44:32AM +0200, Michael Biebl wrote:
> Am 26.09.2016 um 01:28 schrieb Sebastian Reichel:
> > I wonder if libvala-XY-dev should be named libvala-dev with the
> > next version increase, though. This should make binnmu based
> > transitions possible for valabind.
> 
> Would a Provides: libvala-dev be sufficient?

As long as it's guaranteed, that there is only one package providing
libvala-dev it might work. It would be a problem if libvala-0.34-dev
and libvala-0.36-dev (numbers are just examples) are both available
and providing libvala-dev. Then it's unclear which build-dependency
should be pulled.

That could be worked around by creating a transition-style
libvala-dev package, that depends on libvala-xy-dev.

> I think it makes some sense to include the API version in
> libvala-XY-dev. After all, the version is encoded in
> libvala-XY.pc and /usr/include/vala-XY.
> 
> Would we need to provide an unversioned libvala.pc as well?

No.

valabind checks which libvala-xy it has to build against
based on the valac version:

https://sources.debian.net/src/valabind/0.10.0-1/getvv/

valadoc has a list of supported libvala versions, that
it can build against:

https://sources.debian.net/src/valadoc/0.30.0~git20160518-1/configure.ac/#L83

-- Sebastian


signature.asc
Description: PGP signature

Processed: Also mark as found in 1:1.7.10.4-1 for complete version tree

[Debian Bug Tracking System]

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

> found 801046 1:1.7.10.4-1
Bug #801046 [git] fatal: Out of memory, malloc failed (tried to allocate 
524288000 bytes)
Marked as found in versions git/1:1.7.10.4-1.
> thanks
Stopping processing here.

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

Bug#788513: aufs-tools: FTBFS: linux/aufs_type.h: No such file or directory

[Christoph Anton Mitterer]

Hey.

Is it really necessary that the userland tools binary package depends
on the kernel driver package?

That seems to be rather uncommon among similar packages...

Cheers,
Chris.

smime.p7s
Description: S/MIME cryptographic signature

Bug#838881: Actual python module files missing

[debbug]

Package: python-parsedatetime
Version: 2.1-1
Severity: critical

Upgrade from 1.4-1 to 2.1-1 made certbot fail. Short investigation reveals the 
package contains only files in /usr/share/doc/python-parsedatetime/* but is 
missing any file in /usr/lib/.

-- System Information:
Debian Release: stretch/sid
Architecture: i386 (i686)

Bug#838880: chromium Unable to open X display

[user]

Package: chromium
Version: 53.0.2785.113-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

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

   * What led up to the situation?
Running chromium
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Install weston/wayland from experimental branch.  It was not effective
   * What was the outcome of this action?
ERROR:browser_main_loop.cc Unable to open X display
   * What outcome did you expect instead?
For chromium browser to open

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


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

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

Versions of packages chromium depends on:
ii  libasound2   1.1.2-1
ii  libatk1.0-0  2.22.0-1
ii  libavcodec57 7:3.1.3-1+b3
ii  libavformat577:3.1.3-1+b3
ii  libavutil55  7:3.1.3-1+b3
ii  libc62.24-3
ii  libcairo21.14.6-1+b1
ii  libcups2 2.2.0-2
ii  libdbus-1-3  1.10.10-1
ii  libexpat12.2.0-1
ii  libfontconfig1   2.11.0-6.7
ii  libfreetype6 2.6.3-3+b1
ii  libgcc1  1:6.2.0-4
ii  libgdk-pixbuf2.0-0   2.36.0-1
ii  libglib2.0-0 2.50.0-1
ii  libgnome-keyring03.12.0-1+b1
ii  libgtk-3-0   3.22.0-1
ii  libharfbuzz0b1.2.7-1+b1
ii  libjpeg62-turbo  1:1.5.1-1
ii  libnettle6   3.2-1
ii  libnspr4 2:4.12-6
ii  libnss3  2:3.26-2
ii  libpango-1.0-0   1.40.3-2
ii  libpangocairo-1.0-0  1.40.3-2
ii  libpci3  1:3.3.1-1.1
ii  libpulse09.0-3
ii  libspeechd2  0.8.5-1
ii  libstdc++6   6.2.0-4
ii  libx11-6 2:1.6.3-1
ii  libxcomposite1   1:0.4.4-1
ii  libxcursor1  1:1.1.14-1+b1
ii  libxdamage1  1:1.1.4-2+b1
ii  libxext6 2:1.3.3-1
ii  libxfixes3   1:5.0.2-1
ii  libxi6   2:1.7.6-1
ii  libxml2  2.9.4+dfsg1-2
ii  libxrandr2   2:1.5.0-1
ii  libxrender1  1:0.9.9-2
ii  libxslt1.1   1.1.29-1
ii  libxss1  1:1.2.2-1
ii  libxtst6 2:1.2.2-1+b1
ii  x11-utils7.7+3
ii  xdg-utils1.1.1-1

Versions of packages chromium recommends:
ii  fonts-liberation  1:1.07.4-2

Versions of packages chromium suggests:
pn  chromium-l10n  

-- no debconf information

Bug#811826: enigma: FTBFS with GCC 6: no match for

[Erich Schubert]

Thank you.
I did not get around to update engima yet, unfortunately. I was hoping
to do this this weekend, but I don't have a lot of time anymore.
There is also a newer upstream, 1.21, that should eventually be used.

Feel free to move the upload to non-delayed.

Best regards,
Erich

On Mon, Sep 26, 2016 at 12:30 AM, Markus Koschany  wrote:
> Control: tags -1 pending
>
> On Tue, 19 Jan 2016 18:21:45 -0800 Martin Michlmayr  wrote:
>> Package: enigma
>> Version: 1.20-dfsg.1-2
>> Severity: important
>> User: debian-...@lists.debian.org
>> Usertags: ftbfs-gcc-6 gcc-6-no-match
>>
>> This package fails to build with GCC 6.  GCC 6 has not been released
>> yet, but it's expected that GCC 6 will become the default compiler for
>> stretch.
>
> [...]
>
> Dear maintainer,
>
> I've prepared an NMU for enigma (versioned as 1.20-dfsg.1-2.1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer.
>
> Please find attached the debdiff.
>
> Regards,
>
> Markus

Bug#838334: fixed in valadoc 0.30.0~git20160518-1

[Michael Biebl]

Am 26.09.2016 um 01:28 schrieb Sebastian Reichel:
> Hi,
> 
> On Mon, Sep 26, 2016 at 12:34:55AM +0200, Michael Biebl wrote:
>> Thank you for fixing valadoc and valabind so quickly
> 
> You are welcome.
> 
>> and sorry for the short advance notice.
> 
> No harm done. I wonder if libvala-XY-dev should be named libvala-dev
> with the next version increase, though. This should make binnmu
> based transitions possible for valabind.

Would a Provides: libvala-dev be sufficient?

I think it makes some sense to include the API version in
libvala-XY-dev. After all, the version is encoded in
libvala-XY.pc and /usr/include/vala-XY.

Would we need to provide an unversioned libvala.pc as well?


-- 
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#838334: fixed in valadoc 0.30.0~git20160518-1

[Sebastian Reichel]

Hi,

On Mon, Sep 26, 2016 at 12:34:55AM +0200, Michael Biebl wrote:
> Thank you for fixing valadoc and valabind so quickly

You are welcome.

> and sorry for the short advance notice.

No harm done. I wonder if libvala-XY-dev should be named libvala-dev
with the next version increase, though. This should make binnmu
based transitions possible for valabind.

valadoc needs code adjustments for each vala release, but I can
specify Build-Depends: libvala-dev (< max-version-supported+1~).
So if I upload a valadoc release with 0.36 support before valac
is in the archive valadoc could also be binnmu'd once vala 0.36
arrives.

> I didn't expect to get a green light on the libvala transition so
> quickly. So kudos to the release team here as well.

-- Sebastian


signature.asc
Description: PGP signature

Processed: Upstream Bug Report

[Debian Bug Tracking System]

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

> forwarded 838829 https://bugzilla.gnome.org/771964
Bug #838829 [valac] valac: Feature Regression in vala 0.34
Set Bug forwarded-to-address to 'https://bugzilla.gnome.org/771964'.
> thanks
Stopping processing here.

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

Bug#838334: fixed in valadoc 0.30.0~git20160518-1

[Michael Biebl]

Thank you for fixing valadoc and valabind so quickly and sorry for the
short advance notice. I didn't expect to get a green light on the
libvala transition so quickly. So kudos to the release team here as well.

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



signature.asc
Description: OpenPGP digital signature

Processed: Re: enigma: FTBFS with GCC 6: no match for

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #811826 [enigma] enigma: FTBFS with GCC 6: no match for
Added tag(s) pending.

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

Bug#838855: marked as done (perl: no longer provides perl-modules, ~35 reverse dependencies still in the archive)

[Debian Bug Tracking System]

Your message dated Sun, 25 Sep 2016 22:29:23 +
with message-id 
and subject line Bug#838855: fixed in perl 5.24.1~rc3-3
has caused the Debian Bug report #838855,
regarding perl: no longer provides perl-modules, ~35 reverse dependencies still 
in the archive
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.)


-- 
838855: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838855
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: perl-modules-5.24
Version: 5.24.1~rc3-2
Severity: serious

It looks like we stopped Providing perl-modules in 5.24 but missed
transitioning its reverse dependencies.

As stated in the commit message of
 
https://anonscm.debian.org/cgit/perl/perl.git/commit/?id=eae8645a080c81093fd4a5479c9889cbb9a8a13f
"This will need changing ~35 packages in unstable to drop build and
runtime dependencies on perl-modules." Unfortunately we seem to have
forgotten to actually push that through.

According to the same commit message, the reason for dropping
the Provides entry was coinstallability between perl-modules-5.22
and perl-modules-5.24. At the time perl-modules-5.22 conflicted
unconditionally with perl-modules, but this was later changed to a
versioned conflict (see #821161).

I think we should be able to simply reinstate the Provides without
other changes, but will to do some testing to confirm.

Currently affected packages:

 apt-mirror
 cd-circleprint
 chronicle
 conmux
 debian-builder
 dhelp
 dirvish
 dl10n
 ecaccess
 fig2ps
 git
 iwatch
 kanla
 libfinance-yahooquote-perl
 libmime-lite-html-perl
 libtk-tablematrix-perl
 libyaml-shell-perl
 nuxwdog
 oar-restful-api
 ogamesim-www
 parallel
 po4a
 pod2pdf
 ps-watcher
 qdbm
 rcconf
 rt-extension-calendar
 rt-extension-spawnlinkedticketinqueue
 sitesummary
 sitesummary-client
 tightvnc
 wakeonlan
 yample

Related to this, these have a preferred alternative build dependency
on perl-modules-5.22 which is broken too:

 libgraphics-colornames-perl
 libgraphics-colorobject-perl
-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: perl
Source-Version: 5.24.1~rc3-3

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

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

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

Debian distribution maintenance software
pp.
Niko Tyni  (supplier of updated perl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 25 Sep 2016 23:22:41 +0300
Source: perl
Binary: perl-base perl-doc perl-debug libperl5.24 libperl-dev perl-modules-5.24 
perl
Architecture: source
Version: 5.24.1~rc3-3
Distribution: unstable
Urgency: medium
Maintainer: Niko Tyni 
Changed-By: Niko Tyni 
Description:
 libperl-dev - Perl library: development files
 libperl5.24 - shared Perl library
 perl   - Larry Wall's Practical Extraction and Report Language
 perl-base  - minimal Perl system
 perl-debug - debug-enabled Perl interpreter
 perl-doc   - Perl documentation
 perl-modules-5.24 - Core Perl modules
Closes: 838855
Changes:
 perl (5.24.1~rc3-3) unstable; urgency=medium
 .
   * Reinstate perl-modules virtual package (Closes: #838855)
Checksums-Sha1:
 09353c57335fe3bd8944508edfb06e62fb61467c 2347 perl_5.24.1~rc3-3.dsc
 3ab2eaf924f44627c63c42a267616b480aa0a226 162980 perl_5.24.1~rc3-3.debian.tar.xz
Checksums-Sha256:
 9328c6e667267ed5a20618b06dffc9f96180d0ea519f2422e8964d0d173c66d4 2347 
perl_5.24.1~rc3-3.dsc
 c52663a4148af33561e3c8db88fa4b07e8fe62ffc3670f7a78f521ebb1ec7759 162980 
perl_5.24.1~rc3-3.debian.tar.xz
Files:
 1234110d4d9d75a86386a624a5fd5d0a 2347 perl standard perl_5.24.1~rc3-3.dsc
 b748c1e969274b2126f4b000e1ae188c 162980 perl standard 
perl_5.24.1~rc3-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJX6D2CAAoJEC7A/7O3MBsfNDEP/1PxYVDcNPnwF5XGtYgQexHU
M+/eS3+I4p2Fhp86HcKTatH8+XHMiR0lEVcgYdUjC6nu3kXFH5ccWekBhIh/WP0B
zESvYQJYoJa4FYWffcrvj2bR7NJi3RMOdoiD6jawPvrvNKufBINTsUfeLWjRjwaw
dVvgnEy86Kg7klpE9EGoncorPSu7D1y2ur8vdGeo8QWxc6yX+vikPFDI83bHn1ZR
lc3y+CgwpAj2eOhiJDnk7mPPcmIdvUGvT9DXoQr5gvQU4lIwCyRHkFLHjyQeQ8Vh
N4oP+3A9FpHfgPSgos9jJKC3mDFh8P5/k6YK5y6a4XGt0H8cOVZfdx9IRzoaPeq6
rLqSVNnG4q+bLRRUNa0hl3sVMcHhH1F0ic

Bug#811826: enigma: FTBFS with GCC 6: no match for

[Markus Koschany]

Control: tags -1 pending

On Tue, 19 Jan 2016 18:21:45 -0800 Martin Michlmayr  wrote:
> Package: enigma
> Version: 1.20-dfsg.1-2
> Severity: important
> User: debian-...@lists.debian.org
> Usertags: ftbfs-gcc-6 gcc-6-no-match
> 
> This package fails to build with GCC 6.  GCC 6 has not been released
> yet, but it's expected that GCC 6 will become the default compiler for
> stretch.

[...]

Dear maintainer,

I've prepared an NMU for enigma (versioned as 1.20-dfsg.1-2.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Please find attached the debdiff.

Regards,

Markus
diff -Nru enigma-1.20-dfsg.1/debian/changelog 
enigma-1.20-dfsg.1/debian/changelog
--- enigma-1.20-dfsg.1/debian/changelog 2014-01-23 19:02:55.0 +0100
+++ enigma-1.20-dfsg.1/debian/changelog 2016-09-26 00:21:41.0 +0200
@@ -1,3 +1,16 @@
+enigma (1.20-dfsg.1-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add gcc6.patch and fix FTBFS with GCC-6. (Closes: #811826)
+  * Add desktop-file.patch and create a valid desktop file. Add keywords and a
+comment in German. Thanks to Ronny Standtke for the report.
+(Closes: #667656)
+  * enigma-doc.links:
+Symlink index.html to /usr/share/doc/enigma-doc/manual/enigma.html.
+Thanks to Ronny Standtke for the report. (Closes: #791690)
+
+ -- Markus Koschany   Mon, 26 Sep 2016 00:21:41 +0200
+
 enigma (1.20-dfsg.1-2) unstable; urgency=low
 
   * Fixes uninitialized floors (patch r2382, Closes: #652983)
diff -Nru enigma-1.20-dfsg.1/debian/enigma-doc.links 
enigma-1.20-dfsg.1/debian/enigma-doc.links
--- enigma-1.20-dfsg.1/debian/enigma-doc.links  1970-01-01 01:00:00.0 
+0100
+++ enigma-1.20-dfsg.1/debian/enigma-doc.links  2016-09-26 00:21:41.0 
+0200
@@ -0,0 +1 @@
+usr/share/doc/enigma-doc/manual/enigma.html usr/share/doc/enigma-doc/index.html
diff -Nru enigma-1.20-dfsg.1/debian/patches/desktop-file.patch 
enigma-1.20-dfsg.1/debian/patches/desktop-file.patch
--- enigma-1.20-dfsg.1/debian/patches/desktop-file.patch1970-01-01 
01:00:00.0 +0100
+++ enigma-1.20-dfsg.1/debian/patches/desktop-file.patch2016-09-26 
00:21:41.0 +0200
@@ -0,0 +1,31 @@
+From: Markus Koschany 
+Date: Sun, 25 Sep 2016 23:32:43 +0200
+Subject: desktop file
+
+Create a valid desktop file. Add keywords and a comment in German.
+
+Debian-Bug: https://bugs.debian.org/667656
+Forwarded: no
+---
+ etc/enigma.desktop | 4 +++-
+ 1 file changed, 3 insertions(+), 1 deletion(-)
+
+diff --git a/etc/enigma.desktop b/etc/enigma.desktop
+index c33613c..95942fd 100644
+--- a/etc/enigma.desktop
 b/etc/enigma.desktop
+@@ -4,6 +4,7 @@ Version=1.0
+ Name=Enigma
+ 
+ Comment=Uncover pairs of stones while navigating obstacles using a marble
++Comment[de]=Decke Steinpaare mit einer Kugel in einer Welt voller Hindernisse 
auf
+ 
+ TryExec=enigma
+ Exec=enigma
+@@ -13,4 +14,5 @@ Icon=enigma
+ StartupNotify=false
+ 
+ Type=Application
+-Categories=Application;Game;LogicGame;
++Categories=Game;LogicGame;
++Keywords=marble;puzzle;logic;level;
diff -Nru enigma-1.20-dfsg.1/debian/patches/gcc6.patch 
enigma-1.20-dfsg.1/debian/patches/gcc6.patch
--- enigma-1.20-dfsg.1/debian/patches/gcc6.patch1970-01-01 
01:00:00.0 +0100
+++ enigma-1.20-dfsg.1/debian/patches/gcc6.patch2016-09-26 
00:21:41.0 +0200
@@ -0,0 +1,25 @@
+From: Markus Koschany 
+Date: Sun, 25 Sep 2016 23:21:20 +0200
+Subject: gcc6
+
+Fix FTBFS with GCC-6.
+
+Debian-Bug: https://bugs.debian.org/811826
+Forwarded: no
+---
+ src/lev/Proxy.cc | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/src/lev/Proxy.cc b/src/lev/Proxy.cc
+index 0003820..c069247 100644
+--- a/src/lev/Proxy.cc
 b/src/lev/Proxy.cc
+@@ -933,7 +933,7 @@ namespace enigma { namespace lev {
+ } else if (haveLocalCopy) {
+ // plain file
+ basic_ifstream ifs(absExtPath.c_str(), 
ios::binary | ios::in);
+-if (ifs != NULL)
++if (ifs)
+ Readfile(ifs, extCode);
+ else
+ haveLocalCopy = false;
diff -Nru enigma-1.20-dfsg.1/debian/patches/series 
enigma-1.20-dfsg.1/debian/patches/series
--- enigma-1.20-dfsg.1/debian/patches/series2014-01-22 21:34:32.0 
+0100
+++ enigma-1.20-dfsg.1/debian/patches/series2016-09-26 00:21:41.0 
+0200
@@ -3,3 +3,5 @@
 enigma.desktop.patch
 bugfix-oldapi-r2382.patch
 localedir.patch
+gcc6.patch
+desktop-file.patch


signature.asc
Description: OpenPGP digital signature

Bug#838851: marked as done (libcoro-perl: FTBFS with Perl 5.24: panic: corrupt saved stack index -144185424)

[Debian Bug Tracking System]

Your message dated Sun, 25 Sep 2016 22:24:29 +
with message-id 
and subject line Bug#838851: fixed in libcoro-perl 6.511-1
has caused the Debian Bug report #838851,
regarding libcoro-perl: FTBFS with Perl 5.24: panic: corrupt saved stack index 
-144185424
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.)


-- 
838851: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838851
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcoro-perl
Version: 6.490-1
Severity: serious
User: debian-p...@lists.debian.org
Usertags: perl-5.24-transition
Control: block 830200 with -1

This package failed to build against Perl 5.24 on armel, armhf and i386,
with t/12_exit.t test 5 dying:

  panic: corrupt saved stack index -144185424.

Upstream 6.5 changelog has this:

  - adjust to PL_savestack changes in perl 5.24 (adapted from
the debian patch, which unfortunately gets it wrong).

so it's probably time to try the upstream code which should work on
5.24 nowadays.
-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: libcoro-perl
Source-Version: 6.511-1

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

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

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated libcoro-perl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 25 Sep 2016 23:17:12 +0200
Source: libcoro-perl
Binary: libcoro-perl
Architecture: source
Version: 6.511-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 838851
Description: 
 libcoro-perl - Perl framework implementing coroutines
Changes:
 libcoro-perl (6.511-1) unstable; urgency=medium
 .
   * New upstream release.
   * Remove Jonathan Yu from Uploaders. Thanks for your work!
   * Refresh spelling.patch.
   * Drop coro-5.22.patch, issues are fixed upstream.
   * Add back a hunk of the removed patch as coro-5.24.patch.
 (Closes: #838851)
Checksums-Sha1: 
 8f5a06092b7a93d79907a27997e1c0fdcc23c02f 2350 libcoro-perl_6.511-1.dsc
 c3700e11b1e421fa7d2e577b4ab2ef9d85411da3 195173 libcoro-perl_6.511.orig.tar.gz
 3ebb4c97ccd40c203cb38a225056df14b0de8f50 9784 
libcoro-perl_6.511-1.debian.tar.xz
Checksums-Sha256: 
 c39db040b2b61f3816d449026396e98152015010b36da3ca12ae75908d72f6f2 2350 
libcoro-perl_6.511-1.dsc
 7e3ed48cdb3f3742d94ae3ab3d088c3ab818c521f8681da6c5f656bd49ac53ea 195173 
libcoro-perl_6.511.orig.tar.gz
 aae6f557b0601705f5a9cf7dbbd54f4e5c8f8b42182156ad74ba19f74a2d72ad 9784 
libcoro-perl_6.511-1.debian.tar.xz
Files: 
 20594e947226cbaaf13a13c764400ece 2350 perl optional libcoro-perl_6.511-1.dsc
 bcad7051f573fed680eaf72e64e2140e 195173 perl optional 
libcoro-perl_6.511.orig.tar.gz
 897a9721074645bb9cf79ef03027dc2e 9784 perl optional 
libcoro-perl_6.511-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJ8BAEBCgBmBQJX6D9QXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC
QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoGAFwQAKwOBR4c5rxgYk7GolY/2sbz
hN809AXqtRGWdmsnPSAf2W8yxnPm1wIO9OfdZWsvOZTWVoIoCEIU85KLJbuJL3Sv
WfPlEb9zTfmNsq7D8LUFAGU5m59dNjHEQUhZbwqR+pmZuCTGuQEdeDWfPchGpZJc
LjVDEqstB8VO/tsQKJ+5PBofBuKb4SEsxy4f+UyfAZDhuvdUw3BMxKIdQJyoE7u2
6EYZOBdiytNYebmoZmQvUMnMZHnxfl6/7hmgr13i9FXp/MhpP8nD2qAOpCNRpT/x
IYS1fXqje77iBbbvtGbg11rQ+OjJ5P/VvjhBKkYkh7ee2/mLTz0wVI4LMXsMxX6l
N4vqyliyIbJQ+VMnHmrZCYrQ9dW+qv9F7IZivfLVc86SuZJ+2s3G0sM+W44HaxnX
Y/6/IswrT2V7LxOSlQTKmwQQ9o4Jroj5xIUUVfyWzgrrmCA/G4PzxYjMoeaxLyEO
RNSRSfpBiBn/K7QZ9jo5P5VXkBcfHxQmVFxh6rMkOjbZVyI8a7FvqnHvf0lsHYn7
b713yvKxg3W93BIcDlnSFAtQsfF0fSoKpsjtBqttWjbgdSginonCWrkqb0njIUqr
MGCe1fLk6FI8cUmm4ju819vFoDfLn9yxxLsHM2UhiklIGRzrdrKQB8XtXxPufHQG
FTCihpOCxIlVmg8zK5eP
=rjE7
-END PGP SIGNATURE End Message ---

Processed: Fix for the litecoin FTBFS

[Debian Bug Tracking System]

Processing control commands:

> tags 811917 -help
Bug #811917 [litecoin] litecoin: FTBFS with GCC 6: ambiguous overload
Removed tag(s) help.
> tags 811917 +fixed-upstream
Bug #811917 [litecoin] litecoin: FTBFS with GCC 6: ambiguous overload
Added tag(s) fixed-upstream.
> tags 811917 +patch
Bug #811917 [litecoin] litecoin: FTBFS with GCC 6: ambiguous overload
Added tag(s) patch.

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

Bug#811917: Fix for the litecoin FTBFS

[Adrian Bunk]

Control: tags 811917 -help
Control: tags 811917 +fixed-upstream
Control: tags 811917 +patch
thanks

The upstream fix for the litecoin FTBFS is attached.

cu
Adrian

-- 

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

Description: build: fix newer boost build with c++11
 Upstream commit b513bc41337c9c983acdc199ce9b42382c23b658
Origin: upstream, https://github.com/litecoin-project/litecoin/commit/b513bc41337c9c983acdc199ce9b42382c23b658
Bug-Debian: https://bugs.debian.org/811917

--- litecoin-0.10.4.0.orig/src/chainparams.cpp
+++ litecoin-0.10.4.0/src/chainparams.cpp
@@ -106,7 +106,7 @@ public:
 CMainParams() {
 networkID = CBaseChainParams::MAIN;
 strNetworkID = "main";
-/** 
+/**
  * The message start string is designed to be unlikely to occur in normal data.
  * The characters are rarely used upper ASCII, not valid as UTF-8, and produce
  * a large 4-byte int at any alignment.
@@ -130,7 +130,7 @@ public:
 /**
  * Build the genesis block. Note that the output of the genesis coinbase cannot
  * be spent as it did not originally exist in the database.
- * 
+ *
  * CBlock(hash=0019d6, ver=1, hashPrevBlock=00, hashMerkleRoot=4a5e1e, nTime=1231006505, nBits=1d00, nNonce=2083236893, vtx=1)
  *   CTransaction(hash=4a5e1e, ver=1, vin.size=1, vout.size=1, nLockTime=0)
  * CTxIn(COutPoint(00, -1), coinbase 04001d0104455468652054696d65732030332f4a616e2f32303039204368616e63656c6c6f72206f6e206272696e6b206f66207365636f6e64206261696c6f757420666f722062616e6b73)
@@ -162,11 +162,11 @@ public:
 vSeeds.push_back(CDNSSeedData("koin-project.com", "dnsseed.koin-project.com"));
 vSeeds.push_back(CDNSSeedData("weminemnc.com", "dnsseed.weminemnc.com"));
 
-base58Prefixes[PUBKEY_ADDRESS] = list_of(48);
-base58Prefixes[SCRIPT_ADDRESS] = list_of(5);
-base58Prefixes[SECRET_KEY] = list_of(176);
-base58Prefixes[EXT_PUBLIC_KEY] = list_of(0x04)(0x88)(0xB2)(0x1E);
-base58Prefixes[EXT_SECRET_KEY] = list_of(0x04)(0x88)(0xAD)(0xE4);
+base58Prefixes[PUBKEY_ADDRESS] = {48};
+base58Prefixes[SCRIPT_ADDRESS] = {5};
+base58Prefixes[SECRET_KEY] = {176};
+base58Prefixes[EXT_PUBLIC_KEY] = {0x04, 0x88, 0xb2, 0x1e};
+base58Prefixes[EXT_SECRET_KEY] = {0x04, 0x88, 0xad, 0xe4};
 
 convertSeed6(vFixedSeeds, pnSeed6_main, ARRAYLEN(pnSeed6_main));
 
@@ -183,7 +183,7 @@ public:
 nEnforceV2AfterHeight = 71;
 }
 
-const Checkpoints::CCheckpointData& Checkpoints() const 
+const Checkpoints::CCheckpointData& Checkpoints() const
 {
 return data;
 }
@@ -224,11 +224,11 @@ public:
 vSeeds.push_back(CDNSSeedData("xurious.com", "testnet-seed.ltc.xurious.com"));
 vSeeds.push_back(CDNSSeedData("wemine-testnet.com", "dnsseed.wemine-testnet.com"));
 
-base58Prefixes[PUBKEY_ADDRESS] = list_of(111);
-base58Prefixes[SCRIPT_ADDRESS] = list_of(196);
-base58Prefixes[SECRET_KEY] = list_of(239);
-base58Prefixes[EXT_PUBLIC_KEY] = list_of(0x04)(0x35)(0x87)(0xCF);
-base58Prefixes[EXT_SECRET_KEY] = list_of(0x04)(0x35)(0x83)(0x94);
+base58Prefixes[PUBKEY_ADDRESS] = {111};
+base58Prefixes[SCRIPT_ADDRESS] = {196};
+base58Prefixes[SECRET_KEY] = {239};
+base58Prefixes[EXT_PUBLIC_KEY] = {0x04, 0x35, 0x87, 0xcf};
+base58Prefixes[EXT_SECRET_KEY] = {0x04, 0x35, 0x83, 0x94};
 
 convertSeed6(vFixedSeeds, pnSeed6_test, ARRAYLEN(pnSeed6_test));
 
@@ -243,7 +243,7 @@ public:
 // Litecoin: Testnet v2 enforced as of block 400k
 nEnforceV2AfterHeight = 40;
 }
-const Checkpoints::CCheckpointData& Checkpoints() const 
+const Checkpoints::CCheckpointData& Checkpoints() const
 {
 return dataTestnet;
 }
@@ -292,7 +292,7 @@ public:
 // Litecoin: v2 enforced using Bitcoin's supermajority rule
 nEnforceV2AfterHeight = -1;
 }
-const Checkpoints::CCheckpointData& Checkpoints() const 
+const Checkpoints::CCheckpointData& Checkpoints() const
 {
 return dataRegtest;
 }
@@ -321,7 +321,7 @@ public:
 nEnforceV2AfterHeight = -1;
 }
 
-const Checkpoints::CCheckpointData& Checkpoints() const 
+const Checkpoints::CCheckpointData& Checkpoints() const
 {
 // UnitTest share the same checkpoints as MAIN
 return data;

Processed: Re: xl2tpd makes kernel soft lockup

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #822801 [src:linux] xl2tpd makes kernel soft lockup
Severity set to 'important' from 'critical'
> found -1 4.5.1-1
Bug #822801 [src:linux] xl2tpd makes kernel soft lockup
Marked as found in versions linux/4.5.1-1.
> tag -1 moreinfo
Bug #822801 [src:linux] xl2tpd makes kernel soft lockup
Added tag(s) moreinfo.

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

Bug#822801: xl2tpd makes kernel soft lockup

[Ben Hutchings]

Control: severity -1 important
Control: found -1 4.5.1-1
Control: tag -1 moreinfo

On Thu, 28 Apr 2016 01:17:46 +0800 Lu Wang  wrote:
> Package: xl2tpd
> Version: 1.3.6+dfsg-4
> Severity: critical
> Justification: breaks the whole system
> 
> Dear Maintainer,
> 
> I want to set a client of the l2tp vpn for my campus using this technique to 
> connect to the internet.
> I have set the client for Debian 7. But now, when I try to do the same thing 
> for a computer with Debian 9, I failed.
> I set use the configuration for the Debian 7 mechine, including 
> /etc/xl2tpd/xl2tpd /etc/ppp/chap-secrets and /etc/ppp/options.xl2tpd.zju.
> The first one is the configuration for xl2tp, and the last two are for the 
> ppp.
> 
> 
> Following is what I do.
> I find the xl2tpd is running after the initialization through lots of 
> init-scripts. Then I use "echo 'c ZJU_VPN' > /var/run/xl2tpd/l2tp-control" to 
> connect the vpn server in my campus. At the beginning everything is fine, I 
> use "ip link" and I find that there is ppp0. But few time later, about 20-30 
> seconds I am not sure, the keybroad is useless. I can type nothing. And I 
> find there are some words on the screen.
> NMI watchdog: BUG: soft lockup CPU#0 stuck for 23s ... And the mechine begins 
> to beep.

Does this problem still occur when using Linux 4.7 (currently in
unstable)?

Ben.

-- 
Ben Hutchings
No political challenge can be met by shopping. - George Monbiot


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

Bug#838867: chromium: Chromium Way comp d/n sup xdg shell unable to init server cannot open display

[user]

Package: chromium
Version: 53.0.2785.113-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

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

   * What led up to the situation?
Running chromium from weston-terminal in unstable/sid
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
Gdk-WARNING Wayland compositor does not support xdg_shell interface, not using 
wayland
display
Unable to init server: Could not connect: Connection refused
Gtk-WARNING cannot open display
   * What outcome did you expect instead?

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


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

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

Versions of packages chromium depends on:
ii  libasound2   1.1.2-1
ii  libatk1.0-0  2.22.0-1
ii  libavcodec57 7:3.1.3-1+b3
ii  libavformat577:3.1.3-1+b3
ii  libavutil55  7:3.1.3-1+b3
ii  libc62.24-3
ii  libcairo21.14.6-1+b1
ii  libcups2 2.2.0-2
ii  libdbus-1-3  1.10.10-1
ii  libexpat12.2.0-1
ii  libfontconfig1   2.11.0-6.7
ii  libfreetype6 2.6.3-3+b1
ii  libgcc1  1:6.2.0-4
ii  libgdk-pixbuf2.0-0   2.36.0-1
ii  libglib2.0-0 2.50.0-1
ii  libgnome-keyring03.12.0-1+b1
ii  libgtk-3-0   3.22.0-1
ii  libharfbuzz0b1.2.7-1+b1
ii  libjpeg62-turbo  1:1.5.1-1
ii  libnettle6   3.2-1
ii  libnspr4 2:4.12-6
ii  libnss3  2:3.26-2
ii  libpango-1.0-0   1.40.3-2
ii  libpangocairo-1.0-0  1.40.3-2
ii  libpci3  1:3.3.1-1.1
ii  libpulse09.0-3
ii  libspeechd2  0.8.5-1
ii  libstdc++6   6.2.0-4
ii  libx11-6 2:1.6.3-1
ii  libxcomposite1   1:0.4.4-1
ii  libxcursor1  1:1.1.14-1+b1
ii  libxdamage1  1:1.1.4-2+b1
ii  libxext6 2:1.3.3-1
ii  libxfixes3   1:5.0.2-1
ii  libxi6   2:1.7.6-1
ii  libxml2  2.9.4+dfsg1-2
ii  libxrandr2   2:1.5.0-1
ii  libxrender1  1:0.9.9-2
ii  libxslt1.1   1.1.29-1
ii  libxss1  1:1.2.2-1
ii  libxtst6 2:1.2.2-1+b1
ii  x11-utils7.7+3
ii  xdg-utils1.1.1-1

Versions of packages chromium recommends:
ii  fonts-liberation  1:1.07.4-2

Versions of packages chromium suggests:
pn  chromium-l10n  

-- no debconf information

Bug#835743: z3: FTBFS: ../src/util/mpz.cpp:137:8: error: call of overloaded 'set(mpz&, long unsigned int)' is ambiguous

[Gianfranco Costamagna]

Control: tags -1 +pending
On Wed, 14 Sep 2016 18:20:38 +0200 Fabian Wolff  wrote:
> Control: tags -1 + upstream patch fixed-upstream
> 

Hi,

the following debdiff is being build-tested and uploaded on deferred/2

thanks for the patches!
(feel free to ping directly in case of RC bug fixes if you need a sponsor!)

Gianfranco
diff -Nru z3-4.4.1/debian/changelog z3-4.4.1/debian/changelog
--- z3-4.4.1/debian/changelog   2016-07-20 13:07:58.0 +0200
+++ z3-4.4.1/debian/changelog   2016-09-25 23:09:40.0 +0200
@@ -1,3 +1,15 @@
+z3 (4.4.1-0.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Fabian Wolff ]
+  * debian/patches/f02d273ee39ae047222e362c37213d29135dc661.patch:
+Fix build failure with new gnu++14 standard. (Closes: #835754)
+  * debian/patches/27399309009314f56cdfbd8333f287b1a9b7a3a6.patch:
+Fix build failure with new compiler and clang. (Closes: #835743)
+
+ -- Gianfranco Costamagna   Sun, 25 Sep 2016 
23:06:24 +0200
+
 z3 (4.4.1-0.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru 
z3-4.4.1/debian/patches/27399309009314f56cdfbd8333f287b1a9b7a3a6.patch 
z3-4.4.1/debian/patches/27399309009314f56cdfbd8333f287b1a9b7a3a6.patch
--- z3-4.4.1/debian/patches/27399309009314f56cdfbd8333f287b1a9b7a3a6.patch  
1970-01-01 01:00:00.0 +0100
+++ z3-4.4.1/debian/patches/27399309009314f56cdfbd8333f287b1a9b7a3a6.patch  
2016-09-25 23:10:20.0 +0200
@@ -0,0 +1,23 @@
+From 27399309009314f56cdfbd8333f287b1a9b7a3a6 Mon Sep 17 00:00:00 2001
+From: Nuno Lopes 
+Date: Fri, 27 Nov 2015 12:13:44 +
+Subject: [PATCH] fix build with clang
+
+Signed-off-by: Nuno Lopes 
+---
+ src/util/mpz.cpp | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/src/util/mpz.cpp b/src/util/mpz.cpp
+index 8559279..7dca14b 100644
+--- a/src/util/mpz.cpp
 b/src/util/mpz.cpp
+@@ -134,7 +134,7 @@ mpz_manager::mpz_manager():
+ #endif
+ 
+ mpz one(1);
+-set(m_two64, UINT64_MAX);
++set(m_two64, (uint64)UINT64_MAX);
+ add(m_two64, one, m_two64);
+ }
+ 
diff -Nru 
z3-4.4.1/debian/patches/f02d273ee39ae047222e362c37213d29135dc661.patch 
z3-4.4.1/debian/patches/f02d273ee39ae047222e362c37213d29135dc661.patch
--- z3-4.4.1/debian/patches/f02d273ee39ae047222e362c37213d29135dc661.patch  
1970-01-01 01:00:00.0 +0100
+++ z3-4.4.1/debian/patches/f02d273ee39ae047222e362c37213d29135dc661.patch  
2016-09-25 23:10:14.0 +0200
@@ -0,0 +1,23 @@
+From f02d273ee39ae047222e362c37213d29135dc661 Mon Sep 17 00:00:00 2001
+From: Jonathan Wakely 
+Date: Tue, 2 Feb 2016 23:39:11 +
+Subject: [PATCH] Convert stream to bool explicitly
+
+In C++11 there is no implicit conversion from iostream classes to `void*`, 
just an explicit conversion to bool.
+---
+ src/util/debug.cpp | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/src/util/debug.cpp b/src/util/debug.cpp
+index 54c67fe..66676c6 100644
+--- a/src/util/debug.cpp
 b/src/util/debug.cpp
+@@ -76,7 +76,7 @@ void invoke_gdb() {
+ for (;;) {
+ std::cerr << "(C)ontinue, (A)bort, (S)top, (T)hrow exception, Invoke 
(G)DB\n";
+ char result;
+-bool ok = (std::cin >> result);
++bool ok = bool(std::cin >> result);
+ if (!ok) exit(ERR_INTERNAL_FATAL); // happens if std::cin is eof or 
unattached.
+ switch(result) {
+ case 'C':
diff -Nru z3-4.4.1/debian/patches/series z3-4.4.1/debian/patches/series
--- z3-4.4.1/debian/patches/series  2016-07-20 13:07:58.0 +0200
+++ z3-4.4.1/debian/patches/series  2016-09-25 23:08:44.0 +0200
@@ -6,3 +6,5 @@
 typos.patch
 hardening.patch
 kfreebsd.patch
+f02d273ee39ae047222e362c37213d29135dc661.patch
+27399309009314f56cdfbd8333f287b1a9b7a3a6.patch


signature.asc
Description: OpenPGP digital signature

Processed: Re: z3: FTBFS: ../src/util/mpz.cpp:137:8: error: call of overloaded 'set(mpz&, long unsigned int)' is ambiguous

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +pending
Bug #835743 [src:z3] z3: FTBFS: ../src/util/mpz.cpp:137:8: error: call of 
overloaded 'set(mpz&, long unsigned int)' is ambiguous
Added tag(s) pending.

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

Processed: Re: z3: FTBFS: ../src/util/mpz.cpp:137:8: error: call of overloaded 'set(mpz&, long unsigned int)' is ambiguous

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +pending
Bug #835754 [src:z3] z3: FTBFS: util/debug.cpp:79:38: error: cannot convert 
'std::basic_istream' to 'bool' in initialization
Added tag(s) pending.

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

Processed: Pending fixes for bugs in the libcoro-perl package

[Debian Bug Tracking System]

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

> tag 838851 + pending
Bug #838851 [libcoro-perl] libcoro-perl: FTBFS with Perl 5.24: panic: corrupt 
saved stack index -144185424
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Re: Processed (with 2 errors): The actual bug is in liblognorm-dev

[Debian Bug Tracking System]

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

> reassign 835763 liblognorm-dev
Bug #835763 [src:sagan] sagan: FTBFS: configure: error: Package requirements 
(lognorm >= 1.0.0) were not met
Bug #834081 [src:sagan] Missing dependency on libfastjson-dev
Bug reassigned from package 'src:sagan' to 'liblognorm-dev'.
Bug reassigned from package 'src:sagan' to 'liblognorm-dev'.
Ignoring request to alter found versions of bug #835763 to the same values 
previously set
Ignoring request to alter found versions of bug #834081 to the same values 
previously set
Ignoring request to alter fixed versions of bug #835763 to the same values 
previously set
Ignoring request to alter fixed versions of bug #834081 to the same values 
previously set
> found 835763 2.0.1-1
Bug #835763 [liblognorm-dev] sagan: FTBFS: configure: error: Package 
requirements (lognorm >= 1.0.0) were not met
Bug #834081 [liblognorm-dev] Missing dependency on libfastjson-dev
Marked as found in versions liblognorm/2.0.1-1.
Marked as found in versions liblognorm/2.0.1-1.
> thanks
Stopping processing here.

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

Bug#838865: haskell-hmatrix-gsl: FTBFS: hlibrary.setup: The program 'pkg-config' version >=0.9.0 is required but it could not be found.

[Chris Lamb]

Source: haskell-hmatrix-gsl
Version: 0.17.0.0-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

haskell-hmatrix-gsl fails to build from source in unstable/amd64:

  [..]

  Get:2 http://httpredir.debian.org/debian sid/main amd64 dh-buildinfo all 
0.11+nmu1 [18.1 kB]
  Get:3 http://httpredir.debian.org/debian sid/main amd64 libgmpxx4ldbl amd64 
2:6.1.1+dfsg-1 [22.3 kB]
  Get:4 http://httpredir.debian.org/debian sid/main amd64 libgmp-dev amd64 
2:6.1.1+dfsg-1 [629 kB]
  Get:5 http://httpredir.debian.org/debian sid/main amd64 libffi-dev amd64 
3.2.1-6 [161 kB]
  Get:6 http://httpredir.debian.org/debian sid/main amd64 libbsd-dev amd64 
0.8.3-1 [178 kB]
  Get:7 http://httpredir.debian.org/debian sid/main amd64 libtinfo-dev amd64 
6.0+20160917-1 [77.3 kB]
  Get:8 http://httpredir.debian.org/debian sid/main amd64 libncurses5-dev amd64 
6.0+20160917-1 [173 kB]
  Get:9 http://httpredir.debian.org/debian sid/main amd64 ghc amd64 7.10.3-9 
[37.5 MB]
  Get:10 http://httpredir.debian.org/debian sid/main amd64 cdbs all 0.4.148 
[82.3 kB]
  Get:11 http://httpredir.debian.org/debian sid/main amd64 html-xml-utils amd64 
6.9-1 [244 kB]
  Get:12 http://httpredir.debian.org/debian sid/main amd64 
haskell-devscripts-minimal all 0.12 [38.3 kB]
  Get:13 http://httpredir.debian.org/debian sid/main amd64 hscolour amd64 
1.24.1-1 [309 kB]
  Get:14 http://httpredir.debian.org/debian sid/main amd64 haskell-devscripts 
all 0.12 [15.4 kB]
  Get:15 http://httpredir.debian.org/debian sid/main amd64 ghc-prof amd64 
7.10.3-9 [32.1 MB]
  Get:16 http://httpredir.debian.org/debian sid/main amd64 libghc-random-dev 
amd64 1.1-3 [108 kB]
  Get:17 http://httpredir.debian.org/debian sid/main amd64 libghc-split-dev 
amd64 0.2.3.1-1 [42.5 kB]
  Get:18 http://httpredir.debian.org/debian sid/main amd64 
libghc-storable-complex-dev amd64 0.2.2-4 [8660 B]
  Get:19 http://httpredir.debian.org/debian sid/main amd64 libghc-primitive-dev 
amd64 0.6.1.0-2 [85.6 kB]
  Get:20 http://httpredir.debian.org/debian sid/main amd64 libghc-vector-dev 
amd64 0.11.0.0-5 [1116 kB]
  Get:21 http://httpredir.debian.org/debian sid/main amd64 libgfortran3 amd64 
6.2.0-4 [265 kB]
  Get:22 http://httpredir.debian.org/debian sid/main amd64 libblas-common amd64 
3.6.1-2 [13.9 kB]
  Get:23 http://httpredir.debian.org/debian sid/main amd64 libblas3 amd64 
3.6.1-2 [157 kB]
  Get:24 http://httpredir.debian.org/debian sid/main amd64 liblapack3 amd64 
3.6.1-2 [1963 kB]
  Get:25 http://httpredir.debian.org/debian sid/main amd64 libgfortran-6-dev 
amd64 6.2.0-4 [295 kB]
  Get:26 http://httpredir.debian.org/debian sid/main amd64 gfortran-6 amd64 
6.2.0-4 [31.8 MB]
  Get:27 http://httpredir.debian.org/debian sid/main amd64 gfortran amd64 
4:6.1.1-1 [1352 B]
  Get:28 http://httpredir.debian.org/debian sid/main amd64 libblas-dev amd64 
3.6.1-2 [18.9 kB]
  Get:29 http://httpredir.debian.org/debian sid/main amd64 liblapack-dev amd64 
3.6.1-2 [1977 kB]
  Get:30 http://httpredir.debian.org/debian sid/main amd64 libghc-hmatrix-dev 
amd64 0.17.0.2-1+b1 [1456 kB]
  Get:31 http://httpredir.debian.org/debian sid/main amd64 libghc-random-prof 
amd64 1.1-3 [92.8 kB]
  Get:32 http://httpredir.debian.org/debian sid/main amd64 libghc-split-prof 
amd64 0.2.3.1-1 [35.5 kB]
  Get:33 http://httpredir.debian.org/debian sid/main amd64 
libghc-storable-complex-prof amd64 0.2.2-4 [6960 B]
  Get:34 http://httpredir.debian.org/debian sid/main amd64 
libghc-primitive-prof amd64 0.6.1.0-2 [74.1 kB]
  Get:35 http://httpredir.debian.org/debian sid/main amd64 libghc-vector-prof 
amd64 0.11.0.0-5 [1010 kB]
  Get:36 http://httpredir.debian.org/debian sid/main amd64 libghc-hmatrix-prof 
amd64 0.17.0.2-1+b1 [1865 kB]
  Get:37 http://httpredir.debian.org/debian sid/main amd64 libgsl2 amd64 
2.2.1+dfsg-1 [888 kB]
  Get:38 http://httpredir.debian.org/debian sid/main amd64 libgsl-dev amd64 
2.2.1+dfsg-1 [987 kB]
  Get:39 http://httpredir.debian.org/debian sid/main amd64 ghc-doc all 7.10.3-9 
[8920 kB]
  Get:40 http://httpredir.debian.org/debian sid/main amd64 libghc-hmatrix-doc 
all 0.17.0.2-1 [222 kB]
  Get:41 http://httpredir.debian.org/debian sid/main amd64 libghc-random-doc 
all 1.1-3 [44.9 kB]
  Get:42 http://httpredir.debian.org/debian sid/main amd64 libghc-vector-doc 
all 0.11.0.0-5 [253 kB]
  Fetched 125 MB in 3s (38.4 MB/s)
  Selecting previously unselected package dctrl-tools.
  (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%
(Read

Bug#838851: Pending fixes for bugs in the libcoro-perl package

[pkg-perl-maintainers]

tag 838851 + pending
thanks

Some bugs in the libcoro-perl package are closed in revision
d6a751c45999b4f79f3d85290c2a46eaccdc37f2 in branch 'master' by gregor
herrmann

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

Commit message:

Add back a hunk of the removed patch as coro-5.24.patch.

Closes: #838851

Bug#817569: lpr: Removal of debhelper compat 4

[Chris Lamb]

> Thanks. The debdiff is actually 0 bytes in size, but I can compare
> that later.

Sorry about that; not sure what happened...


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

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

[Debian Bug Tracking System]

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

> forwarded 838851 https://rt.cpan.org/Public/Bug/Display.html?id=114708
Bug #838851 [libcoro-perl] libcoro-perl: FTBFS with Perl 5.24: panic: corrupt 
saved stack index -144185424
Set Bug forwarded-to-address to 
'https://rt.cpan.org/Public/Bug/Display.html?id=114708'.
> thanks
Stopping processing here.

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

Bug#817672: solarwolf: Removal of debhelper compat 4

[Markus Koschany]

Control: tags -1 pending

On Wed, 09 Mar 2016 22:00:57 +0100 ni...@thykier.net wrote:
> Source: solarwolf
> Severity: important
> Usertags: compat-4-removal
> 
> Hi,
> 
> The package solarwolf uses debhelper with a compat level of 4,
> which is deprecated and scheduled for removal.

[...]

Dear maintainer,

I've prepared an NMU for solarwolf (versioned as 1.5-2.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Please find attached the debdiff.

Regards,

Markus

diff -u solarwolf-1.5/debian/changelog solarwolf-1.5/debian/changelog
--- solarwolf-1.5/debian/changelog
+++ solarwolf-1.5/debian/changelog
@@ -1,3 +1,17 @@
+solarwolf (1.5-2.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Switch to compat level 10. (Closes: #817672)
+  * Declare use of source format 1.0 explicitly.
+  * Create a valid desktop file. (Closes: #686765)
+  * Change menu section to Games/Action because Games/Arcade does not exist
+anymore.
+  * debian/rules: Call dh_prep instead of deprecated dh_clean -k.
+  * debian/control: Add ${misc:Depends} substvar.
+  * Remove duplicate "is" word in package description.
+
+ -- Markus Koschany   Sun, 25 Sep 2016 21:53:45 +0200
+
 solarwolf (1.5-2.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -u solarwolf-1.5/debian/compat solarwolf-1.5/debian/compat
--- solarwolf-1.5/debian/compat
+++ solarwolf-1.5/debian/compat
@@ -1 +1 @@
-4
+10
diff -u solarwolf-1.5/debian/control solarwolf-1.5/debian/control
--- solarwolf-1.5/debian/control
+++ solarwolf-1.5/debian/control
@@ -3,16 +3,16 @@
 Priority: optional
 Maintainer: Josselin Mouette 
 Build-Depends-Indep: python-all, dh-python
-Build-Depends: debhelper (>= 4.1.25)
+Build-Depends: debhelper (>= 10)
 Standards-Version: 3.7.2
 
 Package: solarwolf
 Architecture: all
-Depends: python-pygame (>= 1.5.6), ${python:Depends}
+Depends: python-pygame (>= 1.5.6), ${misc:Depends}, ${python:Depends}
 Description: Collect the boxes and don't become mad
  Solarwolf is an action/arcade game written entirely in Python,
  featuring amazing graphics and cool music.
- It is is originally based on the SolarFox game on the Atari 2600.
+ It is originally based on the SolarFox game on the Atari 2600.
  .
  All this, yet the best feature of all is; it is a hecka lotta fun!
  The point of the game is to scramble through 48 levels of patterns,
diff -u solarwolf-1.5/debian/menu solarwolf-1.5/debian/menu
--- solarwolf-1.5/debian/menu
+++ solarwolf-1.5/debian/menu
@@ -1,5 +1,5 @@
 ?package(solarwolf): needs="X11"\
-section="Games/Arcade" \
+section="Games/Action" \
 title="SolarWolf" \
 command="/usr/games/solarwolf" \
 icon="/usr/share/pixmaps/solarwolf.xpm"
diff -u solarwolf-1.5/debian/rules solarwolf-1.5/debian/rules
--- solarwolf-1.5/debian/rules
+++ solarwolf-1.5/debian/rules
@@ -21,7 +21,7 @@
 install: build
dh_testdir
dh_testroot
-   dh_clean -k
+   dh_prep
dh_installdirs
dh_install
(cd debian/solarwolf/usr/games && mv solarwolf.py solarwolf)
diff -u solarwolf-1.5/dist/solarwolf.desktop 
solarwolf-1.5/dist/solarwolf.desktop
--- solarwolf-1.5/dist/solarwolf.desktop
+++ solarwolf-1.5/dist/solarwolf.desktop
@@ -4,5 +4,5 @@
-Encoding=UTF-8
 Name=SolarWolf
-Icon=solarwolf.png
-Exec=/usr/games/solarwolf
-Categories=Application;Game;ArcadeGame
+Icon=solarwolf
+Exec=solarwolf
+Categories=Game;ArcadeGame;
+Keywords=pygame;boxes;space;ship;
only in patch2:
unchanged:
--- solarwolf-1.5.orig/debian/source/format
+++ solarwolf-1.5/debian/source/format
@@ -0,0 +1 @@
+1.0


signature.asc
Description: OpenPGP digital signature

Processed: Re: solarwolf: Removal of debhelper compat 4

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #817672 [src:solarwolf] solarwolf: Removal of debhelper compat 4
Added tag(s) pending.

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

Bug#838734: [plasma-discover] plasma-discover uninstalls packages during upgrades without asking for confirmation

[Scott Kitterman]

Thanks.

Another scenario to consider is a user that doesn't know any better enables a 
poorly maintained third party repository that contains conflicting packages 
that cause large numbers of removals.

This can happen post-release and is a scenario the user base you're targeting 
is particularly vulnerable to.

Scott K

On September 25, 2016 2:28:37 PM EDT, Matthias Klumpp  
wrote:
>Discover is for end-users with no technical knowledge. Showing extra
>dialog boxes with crazy text won't help and just be visual clitter,
>since people will press "Yes" anyway. Also, Discover isn't really to
>blame for the underlying problem, which is a busted archive, something
>that never happens in any stable distribution.
>However, it would be nice if Discover handled this situation better on
>unstable development versions of a distro.
>
>I see the following possible solutions:
>
>1) Have Discover detect an unstable distribution, and if it finds one,
>show an extra confirmation box if changes that cause the removal of a
>package are detected.
>
>2) Just display removals as seperate items in the updates list
>unconditionally - people on unstable distros would just need to read
>the information then.
>
>3) Show a "This update is potentially disruptive if you are using an
>unstable distribution" or any other meaningful message when big
>changes are detected (e.g. > 10 packages being removed)
>
>Since even on stable distros sometimes transitions happen and stuff
>gets removed, adding an unconditional dialog seems like a bad idea,
>simply because it's meaningless for average users.
>
>I'll talk to the usability people about the different options, and
>hopefully we can land one of them before Plasma 5.8 is released.
>
>Cheers,
>Matthias

Bug#817569: lpr: Removal of debhelper compat 4

[Adam Majer]

On Sun, Sep 25, 2016 at 02:19:21PM +0100, Chris Lamb wrote:
> I've uploaded lpr 2008.05.17.2 to DELAYED/5:
>   
>   lpr (1:2008.05.17.2) unstable; urgency=medium
>   
> * Non-maintainer upload.
> * Move to debhelper compat level 9. (Closes: #817569)
> 
> The full debdiff is attached.


Thanks. The debdiff is actually 0 bytes in size, but I can compare
that later.

- Adam

Bug#831101: it's torch3 what's the culprit

[Adam Borowski]

I've taken a brief look at this FTBFS, and it appears that it's not a
problem in imms but in torch3 (a build-dependency) which #defines min() and
max() which breaks functions mandated by C++11 and higher, and with new gcc's
focus being on C++14 compliancy, --std=c++98 doesn't appear to be enough to
workaround the issue.

As torch3 has other RC bugs, and popcons of these packages (7 and 14 vote,
respectively) are so low, I'll put my QA tuits elsewhere for now.


Meow!
-- 
An imaginary friend squared is a real enemy.

Bug#838544: ext4: ext4_iget:4476: inode #8: comm mount: checksum invalid

[Michael Biebl]

Am 25.09.2016 um 18:58 schrieb Julien Cristau:
> On Sun, Sep 25, 2016 at 17:06:56 +0200, Michael Biebl wrote:
>> Does this affect 4.7.2-1 as well, i.e. the current version in testing?
> 
> The current version in testing is 4.6.4-1.

Indeed. Somehow I was fooled by
https://packages.qa.debian.org/l/linux.html which lists 4.7.2-1 as the
version in testing. Sorry for the confusion.

Michael

-- 
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#833693: marked as done (python3-popcon: missing Depends on python3-xdg)

[Debian Bug Tracking System]

Your message dated Sun, 25 Sep 2016 19:29:52 +
with message-id 
and subject line Bug#833693: fixed in python-popcon 1.3+nmu1
has caused the Debian Bug report #833693,
regarding python3-popcon: missing Depends on python3-xdg
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.)


-- 
833693: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833693
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-popcon
Version: 1.3
Tags: patch
Severity: serious

Hi,

python3-popcon has a Depends for python-xdg. This should, of course,
be python3-xdg:

$ sudo apt-get install python3-popcon
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following NEW packages will be installed:
  python3-popcon
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 4920 B of archives.
After this operation, 22.5 kB of additional disk space will be used.
Get:1 http://httpredir.debian.org/debian sid/main amd64 python3-popcon all 1.3 
[4920 B]
Fetched 4920 B in 0s (0 B/s) 
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously unselected package python3-popcon.
(Reading database ... 23217 files and directories currently installed.)
Preparing to unpack .../python3-popcon_1.3_all.deb ...
Unpacking python3-popcon (1.3) ...
Setting up python3-popcon (1.3) ...

$ python3
Python 3.5.2+ (default, Aug  5 2016, 08:07:14) 
[GCC 6.1.1 20160724] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import popcon
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/popcon.py", line 80, in 
import xdg.BaseDirectory
ImportError: No module named 'xdg.BaseDirectory'


Patch attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff --git a/debian/control b/debian/control
index 74e977a..2f6d28e 100644
--- a/debian/control
+++ b/debian/control
@@ -18,7 +18,7 @@ Description: Python interface to Debian's Popularity Contest 
(popcon)
 
 Package: python3-popcon
 Architecture: all
-Depends: ${misc:Depends}, ${python3:Depends}, python-xdg
+Depends: ${misc:Depends}, ${python3:Depends}, python3-xdg
 Description: Python interface to Debian's Popularity Contest (popcon)
  This package provides the popcon module, which allows to query Debian's
  Popularity Contest data.
--- End Message ---
--- Begin Message ---
Source: python-popcon
Source-Version: 1.3+nmu1

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

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

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

Debian distribution maintenance software
pp.
Ximin Luo  (supplier of updated python-popcon package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 13 Sep 2016 19:58:28 +0200
Source: python-popcon
Binary: python-popcon python3-popcon
Architecture: source
Version: 1.3+nmu1
Distribution: unstable
Urgency: medium
Maintainer: Bastian Venthur 
Changed-By: Ximin Luo 
Description:
 python-popcon - Python interface to Debian's Popularity Contest (popcon)
 python3-popcon - Python interface to Debian's Popularity Contest (popcon)
Closes: 833693 833738
Changes:
 python-popcon (1.3+nmu1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add support for querying sourcemax statistics.
   * Don't mix up pickle formats; this causes bad lookups when py2/py3 both
 use the same file.
   * Update to latest Standards-Version; no changes required.
 .
   [ Chris Lamb ]
   * Fix missing Depends on python3-xdg. (Closes: #833693)
   * Don't assume all-popcon-results.txt.gz is UTF-8. (Closes: #833738)
Checksums-Sha1:
 3a0d7f454135a6fb312b2325f5eda062790987b2 1609 python-popcon_1.3+nmu1.dsc
 7422b45030ae5ae7581e4992ddd8d4e8974e50e6 4904 python-popcon_1.3+nmu1.tar.xz
Checksums-Sha256:
 62fdf5347aac80e0eac702e418eb78fbc4706cac3f89cbd65fc5ab30dc3ffaae 1609 
python-popcon_1.3+nmu1.dsc
 3229a3550292b7fa79bea8043053d0066a0031355d7ee6d93a29202e004271f0 4904 
python-popcon_1.3+nmu1.tar.xz
Files:
 24924ef52cd1094

Bug#833738: marked as done (python-popcon: assumes all-popcon-results.txt.gz is UTF-8)

[Debian Bug Tracking System]

Your message dated Sun, 25 Sep 2016 19:29:52 +
with message-id 
and subject line Bug#833738: fixed in python-popcon 1.3+nmu1
has caused the Debian Bug report #833738,
regarding python-popcon: assumes all-popcon-results.txt.gz is UTF-8
to be marked as done.

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

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


-- 
833738: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833738
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-popcon
Version: 1.3
Severity: serious
Tags: patch
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi,

Since (at least) 07-Aug-2016 14:04, the all-popcon-results.txt.gz file
contains an invalid line:

Package: libfyba0-dbg   0 2 0 0
--> Package: libf erdp-ommon0 0 0 1
Package: libg++2.8.1.3-dbg  0 0 0 1

That's (currently) line 54869. The "space" on the second line is actually
a 0xa0 character. This is making the package unusable.

$ python3
Python 3.5.2+ (default, Aug  5 2016, 08:07:14) 
[GCC 6.1.1 20160724] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import popcon
>>> popcon.package("foo")
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/popcon.py", line 145, in package
raw = package_raw(*packages)
  File "/usr/lib/python3/dist-packages/popcon.py", line 189, in package_raw
data = _fetch()
  File "/usr/lib/python3/dist-packages/popcon.py", line 108, in _fetch
txt = _decompress(txt)
  File "/usr/lib/python3/dist-packages/popcon.py", line 134, in _decompress
data = data.decode()
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xa0 in position 3574857: 
invalid start byte

You can see this happening here:

  
https://jenkins.debian.net/view/reproducible/view/problems/job/reproducible_html_notes/


Patch attached. NB. the comment in the lookup section.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff --git a/src/popcon.py b/src/popcon.py
index 4f089f0..670c514 100644
--- a/src/popcon.py
+++ b/src/popcon.py
@@ -115,7 +115,7 @@ def _parse(results):
 results = results.splitlines()
 for line in results:
 elems = line.split()
-if elems[0] != "Package:":
+if elems[0] != b"Package:":
 continue
 ans[elems[1]] = Package(*(int(i) for i in elems[2:]))
 return ans
@@ -131,7 +131,6 @@ def _decompress(compressed):
 gzippedstream = io.BytesIO(compressed)
 gzipper = gzip.GzipFile(fileobj=gzippedstream)
 data = gzipper.read()
-data = data.decode()
 return data
 
 
@@ -206,8 +205,11 @@ def package_raw(*packages):
 cached_timestamp = time.time()
 ans = dict()
 for pkg in packages:
-if pkg in data:
-ans[pkg] = data[pkg]
+# Lookup using bytestrings, but always index results by the original so
+# that callsites can look it up.
+lookup = pkg if isinstance(pkg, bytes) else pkg.encode('utf-8')
+if lookup in data:
+ans[pkg] = data[lookup]
 if KEEP_DATA:
 cached_data = data
 return ans
--- End Message ---
--- Begin Message ---
Source: python-popcon
Source-Version: 1.3+nmu1

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

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

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

Debian distribution maintenance software
pp.
Ximin Luo  (supplier of updated python-popcon package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 13 Sep 2016 19:58:28 +0200
Source: python-popcon
Binary: python-popcon python3-popcon
Architecture: source
Version: 1.3+nmu1
Distribution: unstable
Urgency: medium
Maintainer: Bastian Venthur 
Changed-By: Ximin Luo 
Description:
 python-popcon - Python interface to Debian's Popularity Contest (popcon)
 python3-popcon - Python interface to Debian's Popularity Contest (popcon)
Closes: 833693 833738
Changes:
 python-popcon (1.3+nmu1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add support 

Bug#838855: perl: no longer provides perl-modules, ~35 reverse dependencies still in the archive

[Niko Tyni]

Package: perl-modules-5.24
Version: 5.24.1~rc3-2
Severity: serious

It looks like we stopped Providing perl-modules in 5.24 but missed
transitioning its reverse dependencies.

As stated in the commit message of
 
https://anonscm.debian.org/cgit/perl/perl.git/commit/?id=eae8645a080c81093fd4a5479c9889cbb9a8a13f
"This will need changing ~35 packages in unstable to drop build and
runtime dependencies on perl-modules." Unfortunately we seem to have
forgotten to actually push that through.

According to the same commit message, the reason for dropping
the Provides entry was coinstallability between perl-modules-5.22
and perl-modules-5.24. At the time perl-modules-5.22 conflicted
unconditionally with perl-modules, but this was later changed to a
versioned conflict (see #821161).

I think we should be able to simply reinstate the Provides without
other changes, but will to do some testing to confirm.

Currently affected packages:

 apt-mirror
 cd-circleprint
 chronicle
 conmux
 debian-builder
 dhelp
 dirvish
 dl10n
 ecaccess
 fig2ps
 git
 iwatch
 kanla
 libfinance-yahooquote-perl
 libmime-lite-html-perl
 libtk-tablematrix-perl
 libyaml-shell-perl
 nuxwdog
 oar-restful-api
 ogamesim-www
 parallel
 po4a
 pod2pdf
 ps-watcher
 qdbm
 rcconf
 rt-extension-calendar
 rt-extension-spawnlinkedticketinqueue
 sitesummary
 sitesummary-client
 tightvnc
 wakeonlan
 yample

Related to this, these have a preferred alternative build dependency
on perl-modules-5.22 which is broken too:

 libgraphics-colornames-perl
 libgraphics-colorobject-perl
-- 
Niko Tyni   nt...@debian.org

Bug#825629: marked as done (libgd-perl: FTBFS: Could not find gdlib-config in the search path. )

[Debian Bug Tracking System]

Your message dated Sun, 25 Sep 2016 19:25:08 +
with message-id 
and subject line Bug#825629: fixed in libgd-perl 2.53-3
has caused the Debian Bug report #825629,
regarding libgd-perl: FTBFS: Could not find gdlib-config in the search path. 
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.)


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

Dear Maintainer,

libgd-perl fails to build from source in unstable/amd64:

  [..]

  Get:41 http://httpredir.debian.org/debian sid/main amd64 libsm-dev amd64 
2:1.2.2-1+b1 [35.8 kB]
  Get:42 http://httpredir.debian.org/debian sid/main amd64 libxt-dev amd64 
1:1.1.5-1 [423 kB]
  Get:43 http://httpredir.debian.org/debian sid/main amd64 libexpat1-dev amd64 
2.1.1-2 [127 kB]
  Get:44 http://httpredir.debian.org/debian sid/main amd64 pkg-config amd64 
0.29-4 [62.5 kB]
  Get:45 http://httpredir.debian.org/debian sid/main amd64 libfontconfig1-dev 
amd64 2.11.0-6.4 [893 kB]
  Get:46 http://httpredir.debian.org/debian sid/main amd64 libvpx3 amd64 
1.5.0-3 [743 kB]
  Get:47 http://httpredir.debian.org/debian sid/main amd64 libvpx-dev amd64 
1.5.0-3 [836 kB]
  Get:48 http://httpredir.debian.org/debian sid/main amd64 libjbig-dev amd64 
2.1-3.1 [29.9 kB]
  Get:49 http://httpredir.debian.org/debian sid/main amd64 liblzma-dev amd64 
5.1.1alpha+20120614-2.1 [255 kB]
  Get:50 http://httpredir.debian.org/debian sid/main amd64 libtiffxx5 amd64 
4.0.6-1 [83.9 kB]
  Get:51 http://httpredir.debian.org/debian sid/main amd64 libtiff5-dev amd64 
4.0.6-1 [344 kB]
  Get:52 http://httpredir.debian.org/debian sid/main amd64 libgd-dev amd64 
2.2.1-1 [275 kB]
  Get:53 http://httpredir.debian.org/debian sid/main amd64 
libregexp-assemble-perl all 0.36-1 [86.6 kB]
  Get:54 http://httpredir.debian.org/debian sid/main amd64 
libimage-exiftool-perl all 10.15-1 [2354 kB]
  Get:55 http://httpredir.debian.org/debian sid/main amd64 libfont-ttf-perl all 
1.05-1 [358 kB]
  Fetched 20.9 MB in 0s (73.7 MB/s)
  Selecting previously unselected package cdbs.
  (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 ... 23096 files and directories currently installed.)
  Preparing to unpack .../archives/cdbs_0.4.137_all.deb ...
  Unpacking cdbs (0.4.137) ...
  Selecting previously unselected package dh-buildinfo.
  Preparing to unpack .../dh-buildinfo_0.11+nmu1_all.deb ...
  Unpacking dh-buildinfo (0.11+nmu1) ...
  Selecting previously unselected package libpng16-16:amd64.
  Preparing to unpack .../libpng16-16_1.6.21-5_amd64.deb ...
  Unpacking libpng16-16:amd64 (1.6.21-5) ...
  Selecting previously unselected package libfreetype6:amd64.
  Preparing to unpack .../libfreetype6_2.6.3-3+b1_amd64.deb ...
  Unpacking libfreetype6:amd64 (2.6.3-3+b1) ...
  Selecting previously unselected package ucf.
  Preparing to unpack .../archives/ucf_3.0036_all.deb ...
  Moving old data out of the way
  Unpacking ucf (3.0036) ...
  Selecting previously unselected package fonts-dejavu-core.
  Preparing to unpack .../fonts-dejavu-core_2.35-1_all.deb ...
  Unpacking fonts-dejavu-core (2.35-1) ...
  Selecting previously unselected package fontconfig-config.
  Preparing to unpack .../fontconfig-config_2.11.0-6.4_all.deb ...
  Unpacking fontconfig-config (2.11.0-6.4) ...
  Selecting previously unselected package libfontconfig1:amd64.
  Preparing to unpack .../libfontconfig1_2.11.0-6.4_amd64.deb ...
  Unpacking libfontconfig1:amd64 (2.11.0-6.4) ...
  Selecting previously unselected package libjpeg62-turbo:amd64.
  Preparing to unpack .../libjpeg62-turbo_1%3a1.4.2-2_amd64.deb ...
  Unpacking libjpeg62-turbo:amd64 (1:1.4.2-2) ...
  Selecting previously unselected package libjbig0:amd64.
  Preparing to unpack .../libjbig0_2.1-3.1_amd64.deb ...
  Unpacking libjbig0:amd64 (2.1-3.1) ...
  Selecting previously unselected package libtiff5:amd64.
  Preparin

Bug#831174: marked as done (gcc-avr: FTBFS with GCC 6: cfns.gperf:101:1: error: 'const char* libc_name_p(const char*, unsigned int)' redeclared inline with 'gnu_inline' attribute)

[Debian Bug Tracking System]

Your message dated Sun, 25 Sep 2016 19:22:47 +
with message-id 
and subject line Bug#831174: fixed in gcc-avr 1:4.9.2+Atmel3.5.3-1
has caused the Debian Bug report #831174,
regarding gcc-avr: FTBFS with GCC 6: cfns.gperf:101:1: error: 'const char* 
libc_name_p(const char*, unsigned int)' redeclared inline with 'gnu_inline' 
attribute
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.)


-- 
831174: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831174
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gcc-avr
Version: 1:4.9.2+Atmel3.5.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160713 qa-ftbfs
Justification: FTBFS with GCC 6 on amd64

Hi,

During a rebuild of all packages in sid using the gcc-defaults package
available in experimental to make GCC default to version 6, your package failed
to build on amd64. For more information about GCC 6 and Stretch, see:
- https://wiki.debian.org/GCC6
- https://lists.debian.org/debian-devel-announce/2016/06/msg7.html

Relevant part (hopefully):
> x86_64-linux-gnu-g++ -c  -DIN_GCC_FRONTEND -g -O2 -fstack-protector-strong 
> -Wformat  -DIN_GCC  -DCROSS_DIRECTORY_STRUCTURE  -fno-exceptions -fno-rtti 
> -fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings 
> -Wcast-qual -Wmissing-format-attribute -pedantic -Wno-long-long 
> -Wno-variadic-macros -Wno-overlength-strings   -DHAVE_CONFIG_H -I. -Icp 
> -I../../src/gcc -I../../src/gcc/cp -I../../src/gcc/../include 
> -I../../src/gcc/../libcpp/include  -I../../src/gcc/../libdecnumber 
> -I../../src/gcc/../libdecnumber/dpd -I../libdecnumber 
> -I../../src/gcc/../libbacktrace-o cp/except.o -MT cp/except.o -MMD -MP 
> -MF cp/.deps/except.TPo ../../src/gcc/cp/except.c
> In file included from ./tm.h:18:0,
>  from ../../src/gcc/cp/except.c:27:
> ../../src/gcc/config/elfos.h:102:21: warning: invalid suffix on literal; 
> C++11 requires a space between literal and string macro [-Wliteral-suffix]
> fprintf ((FILE), "%s"HOST_WIDE_INT_PRINT_UNSIGNED"\n",\
>  ^
> ../../src/gcc/config/elfos.h:170:24: warning: invalid suffix on literal; 
> C++11 requires a space between literal and string macro [-Wliteral-suffix]
>fprintf ((FILE), ","HOST_WIDE_INT_PRINT_UNSIGNED",%u\n",  \
> ^
> In file included from ../../src/gcc/cp/except.c:1013:0:
> cfns.gperf: In function 'const char* libc_name_p(const char*, unsigned int)':
> cfns.gperf:101:1: error: 'const char* libc_name_p(const char*, unsigned int)' 
> redeclared inline with 'gnu_inline' attribute
> cfns.gperf:26:14: note: 'const char* libc_name_p(const char*, unsigned int)' 
> previously declared here
> cfns.gperf: At global scope:
> cfns.gperf:26:14: warning: inline function 'const char* libc_name_p(const 
> char*, unsigned int)' used but never defined
> make[3]: *** [cp/except.o] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/13/gcc-avr_4.9.2+Atmel3.5.0-1_unstable_gcc6.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 ---
Source: gcc-avr
Source-Version: 1:4.9.2+Atmel3.5.3-1

We believe that the bug you reported is fixed in the latest version of
gcc-avr, 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.
Hakan Ardo  (supplier of updated gcc-avr 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: SHA1

Format: 1.8
Date: Sun, 28 Aug 2016 19:45:37 +0200
Source: gcc-avr
Binary: gcc-avr
Architecture: source amd64
Version: 1:4.9.2+Atmel3.5.3-1
Distribution: unstable
Urgency: medium
Maintainer: Hakan Ardo 
Changed-By: Hakan Ardo 
Description:
 gcc-avr- GNU C compiler (cross compiler for avr)
Closes: 831174
Changes:
 gcc-avr (1:4.9.2+Atm

Bug#798296: marked as done (bats own testsuite fails with TERM set to unknown)

[Debian Bug Tracking System]

Your message dated Sun, 25 Sep 2016 19:20:57 +
with message-id 
and subject line Bug#798296: fixed in bats 0.4.0-1.1
has caused the Debian Bug report #798296,
regarding bats own testsuite fails with TERM set to unknown
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.)


-- 
798296: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798296
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:bats
Version: 0.4.0-1
Severity: important
Tags: patch

bats own testsuite fails when TERM is set to unknown. The following patch fixes
it.  It also prints the $output for failed tests (taken from an upstream pull
request).

patch attached

  * Set TERM for running the tests when not set or set to unknown.
  * Apply upstream pull requests #101 to print the output of failed tests.
 
diff -Nru bats-0.4.0/debian/patches/fix-101.diff 
bats-0.4.0/debian/patches/fix-101.diff
--- bats-0.4.0/debian/patches/fix-101.diff  1970-01-01 01:00:00.0 
+0100
+++ bats-0.4.0/debian/patches/fix-101.diff  2015-09-07 21:11:23.0 
+0200
@@ -0,0 +1,14 @@
+Index: b/libexec/bats-exec-test
+===
+--- a/libexec/bats-exec-test
 b/libexec/bats-exec-test
+@@ -161,6 +161,9 @@ bats_print_failed_command() {
+   else
+ echo "failed with status $status"
+   fi
++  if [ -n "$output" ]; then
++  echo "#   $output"
++  fi
+ }
+ 
+ bats_frame_lineno() {
diff -Nru bats-0.4.0/debian/patches/series bats-0.4.0/debian/patches/series
--- bats-0.4.0/debian/patches/series2014-12-07 06:53:16.0 +0100
+++ bats-0.4.0/debian/patches/series2015-09-07 21:42:36.0 +0200
@@ -1 +1,2 @@
 deb_libexec_to_lib
+fix-101.diff
diff -Nru bats-0.4.0/debian/rules bats-0.4.0/debian/rules
--- bats-0.4.0/debian/rules 2014-12-07 06:53:16.0 +0100
+++ bats-0.4.0/debian/rules 2015-09-07 21:37:37.0 +0200
@@ -11,5 +11,9 @@
./install.sh debian/bats/usr
 
 override_dh_auto_test:
+   set -e; \
+   if [ x$$TERM = x ] || [ x$$TERM = xunknown ]; then \
+ export TERM=dumb; \
+   fi; \
bin/bats --tap test
 
--- End Message ---
--- Begin Message ---
Source: bats
Source-Version: 0.4.0-1.1

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

Debian distribution maintenance software
pp.
Tobias Frost  (supplier of updated bats package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 25 Sep 2016 11:40:12 +0200
Source: bats
Binary: bats
Architecture: source
Version: 0.4.0-1.1
Distribution: unstable
Urgency: medium
Maintainer: Yaroslav Halchenko 
Changed-By: Tobias Frost 
Description:
 bats   - bash automated testing system
Closes: 798296
Changes:
 bats (0.4.0-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Set TERM=dumb for tests to avoid FTBFS (Closes: #798296) and
 Using dumb to keep the build reproducible.
Checksums-Sha1:
 17fe8648a17c17d44fcb59fa48426e3260d6f9e3 1757 bats_0.4.0-1.1.dsc
 4dc8e7e9ea11b81cee259c568c3b9a4a8932f427 2444 bats_0.4.0-1.1.debian.tar.xz
Checksums-Sha256:
 d62a2b805feb1625e5fbb03d3f70411f04a1da9c579fbce9d8063b148d910cd2 1757 
bats_0.4.0-1.1.dsc
 bc46d883bdac4149544d736a17ed375d999d62fd4065f85fa48f3937ab475724 2444 
bats_0.4.0-1.1.debian.tar.xz
Files:
 5e8b9333487de4462e41423447b7be75 1757 shells optional bats_0.4.0-1.1.dsc
 dad52f96fd216dddf5cde00cbc0fb27b 2444 shells optional 
bats_0.4.0-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJX55xOAAoJEJFk+h0XvV02N+QQAJ+wgeZAiv/Zv0x8j4mghnTU
EG6RHx5/wkU54nV8zfwdm9VPKBtVPdzCJ/lrm9vPEQ+40WZyOE65v0Gr/c8fopDI
sJ2pRUw0s+3msjrNYaMGU5T5zsLKbwQWw0iDaGL6FA/QMBmsk5V7KQx5xbjPIIui
fT2QqkinCZzexTFMZ1bsZ4oeLSdVV26ZKmi8Iv2gdmoZR2p8lyNoU14REbUOgTlQ
xRhad828bg8Oxj2bnwoy6aQtPuIB+M4OAaU7YfJmvsUJeNzkQEZd8EVRPGoV5DEx
d6kX9jTVIL67IOQDC8hcIqJe03DyfcOdDHKgsIE+IEq1gP/GED3Fmbrjdt7M+9nj
2TvLek3K6coYRFAHAvOV3onXsC+c3FxmMDBAsMwqpsPyIqiKcFvPZa908s58sQGM
ZIvOMqHC6gPFkdyBpU3pfQBh/2h7VWYPL8xu0fHwpCKVdbwLU23sUBrDNFnzcMNM
fhjpTVrLDtW8xW0TAwbvezb5xlk5q+XQyOx6DMkJglN

Bug#802191: marked as done (bats: FTBFS: not ok 7 summary passing tests)

[Debian Bug Tracking System]

Your message dated Sun, 25 Sep 2016 19:20:57 +
with message-id 
and subject line Bug#798296: fixed in bats 0.4.0-1.1
has caused the Debian Bug report #798296,
regarding bats: FTBFS: not ok 7 summary passing 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.)


-- 
798296: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798296
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bats
Version: 0.4.0-1
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

The package fails to build:

make[1]: Entering directory '/bats-0.4.0'
bin/bats --tap test
1..43
ok 1 no arguments prints usage instructions
ok 2 -v and --version print version number
ok 3 -h and --help print help
ok 4 invalid filename prints an error
ok 5 empty test file runs zero tests
ok 6 one passing test
not ok 7 summary passing tests
# (in test file test/bats.bats, line 46)
#   `[ "${lines[1]}" = "1 test, 0 failures" ]' failed
not ok 8 summary passing and skipping tests
# (in test file test/bats.bats, line 52)
#   `[ "${lines[2]}" = "2 tests, 0 failures, 1 skipped" ]' failed
not ok 9 summary passing and failing tests
# (in test file test/bats.bats, line 58)
#   `[ "${lines[4]}" = "2 tests, 1 failure" ]' failed
not ok 10 summary passing, failing and skipping tests
# (in test file test/bats.bats, line 64)
#   `[ "${lines[5]}" = "3 tests, 1 failure, 1 skipped" ]' failed
ok 11 one failing test
ok 12 one failing and one passing test



debian/rules:14: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/bats-0.4.0'

Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/bats.html

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Source: bats
Source-Version: 0.4.0-1.1

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

Debian distribution maintenance software
pp.
Tobias Frost  (supplier of updated bats package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 25 Sep 2016 11:40:12 +0200
Source: bats
Binary: bats
Architecture: source
Version: 0.4.0-1.1
Distribution: unstable
Urgency: medium
Maintainer: Yaroslav Halchenko 
Changed-By: Tobias Frost 
Description:
 bats   - bash automated testing system
Closes: 798296
Changes:
 bats (0.4.0-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Set TERM=dumb for tests to avoid FTBFS (Closes: #798296) and
 Using dumb to keep the build reproducible.
Checksums-Sha1:
 17fe8648a17c17d44fcb59fa48426e3260d6f9e3 1757 bats_0.4.0-1.1.dsc
 4dc8e7e9ea11b81cee259c568c3b9a4a8932f427 2444 bats_0.4.0-1.1.debian.tar.xz
Checksums-Sha256:
 d62a2b805feb1625e5fbb03d3f70411f04a1da9c579fbce9d8063b148d910cd2 1757 
bats_0.4.0-1.1.dsc
 bc46d883bdac4149544d736a17ed375d999d62fd4065f85fa48f3937ab475724 2444 
bats_0.4.0-1.1.debian.tar.xz
Files:
 5e8b9333487de4462e41423447b7be75 1757 shells optional bats_0.4.0-1.1.dsc
 dad52f96fd216dddf5cde00cbc0fb27b 2444 shells optional 
bats_0.4.0-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJX55xOAAoJEJFk+h0XvV02N+QQAJ+wgeZAiv/Zv0x8j4mghnTU
EG6RHx5/wkU54nV8zfwdm9VPKBtVPdzCJ/lrm9vPEQ+40WZyOE65v0Gr/c8fopDI
sJ2pRUw0s+3msjrNYaMGU5T5zsLKbwQWw0iDaGL6FA/QMBmsk5V7KQx5xbjPIIui
fT2QqkinCZzexTFMZ1bsZ4oeLSdVV26ZKmi8Iv2gdmoZR2p8lyNoU14REbUOgTlQ
xRhad828bg8Oxj2bnwoy6aQtPuIB+M4OAaU7YfJmvsUJeNzkQEZd8EVRPGoV5DEx
d6kX9jTVIL67IOQDC8hcIqJe03DyfcOdDHKgsIE+IEq1gP/GED3Fmbrjdt7M+9nj
2TvLek3K6coYRFAHAvOV3onXsC+c3FxmMDBAsMwqpsPyIqiKcFvPZa908s58sQGM
ZIvOMqHC6gPFkdyBpU3pfQBh/2h7VWYPL8xu0fHwpCKVdbwLU23sUBrDNFnzcMNM
fhjpTVrLDtW8xW0TAwbvezb5xlk5q+XQyOx6DMkJglNRWMX5t2KIHriFnWlKVgqb
8jUltt+NFtKn+BpZMoYr9CEyhW6hPlLJQ5YDViaAAlV1FPWfApMh+c95HIaLvhBA
RjCJ+dWSGgtncqSBIwb+0KT5QVa/5c+P1Rl3Jwt2ad7zVa+yoW/T/U1TXvc6t37g
2f+kI0Hs4lKL7K6PqvFN
=OE

Bug#838851: libcoro-perl: FTBFS with Perl 5.24: panic: corrupt saved stack index -144185424

[gregor herrmann]

On Sun, 25 Sep 2016 21:33:10 +0300, Niko Tyni wrote:

> so it's probably time to try the upstream code which should work on
> 5.24 nowadays.

6.511 in git fails to build (cowbuilder sid amd64) with:

Running Mkbootstrap for Coro::State ()
chmod 644 "State.bs"
"/usr/bin/perl" "/usr/share/perl/5.24.1/ExtUtils/xsubpp"  -typemap 
"/usr/share/perl/5.24/ExtUtils/typemap" -typemap "typemap"  State.xs > 
State.xsc && mv State.xsc State.c
Warning: Aliases 'is_zombie' and 'is_destroyed' have identical values in 
State.xs, line 3852
x86_64-linux-gnu-gcc -c   -D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fwrapv 
-fno-strict-aliasing -pipe -I/usr/local/include -D_LARGEFILE_SOURCE 
-D_FILE_OFFSET_BITS=64 -g -O2 -fdebug-prefix-map=/build/libcoro-perl-6.511=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2   -DVERSION=\"6.511\" -DXS_VERSION=\"6.511\" -fPIC 
"-I/usr/lib/x86_64-linux-gnu/perl/5.24/CORE"  -DCORO_ASM -DCORO_STACKSIZE=16384 
-DCORO_GUARDPAGES=4 -DCORO_JIT=1 State.c
State.xs: In function 'runops_trace':
State.xs:1415:168: error: 'struct block_sub' has no member named 'argarray'; 
did you mean 'savearray'?
   PUSHs (CxHASARGS (cx) ? sv_2mortal (newRV_inc ((SV 
*)cx->blk_sub.argarray)) : &PL_sv_undef);


^
Makefile:406: recipe for target 'State.o' failed
make[2]: *** [State.o] Error 1
make[2]: Leaving directory '/build/libcoro-perl-6.511/Coro'
Makefile:613: recipe for target 'subdirs' failed
make[1]: *** [subdirs] Error 2
make[1]: Leaving directory '/build/libcoro-perl-6.511'
dh_auto_build: make -j1 returned exit code 2
debian/rules:6: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2


Cheers,
gregor

-- 
 .''`.  Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Tracy Chapman: Broken


signature.asc
Description: Digital Signature

Bug#836635: libpam-mount: please drop the build dependency on hardening-wrapper

[Christian Meyer]

Hello there,

since the build dep on hardening-wrapper isn't neccessary for pam_mount,
I'm wondering why #836635 is "serious" and marked for autoremoval.

BTW: pam_mount 1.16 has just been released to "support building with
OpenSSL 1.1.0 and test libressl 2.4.2", which could be good for the
auto-openssl transition (#828404).
Since pam_mount 1.15 it supports the helper= option so that various
debian bugs for pam_mount, even crypto or unmounting related bugs,
should be resolved.

So by updating to the latest upstream version and removing the build dep
pam_mount should be able to stay in Debian.

Christian Meyer

Processed: libcoro-perl: FTBFS with Perl 5.24: panic: corrupt saved stack index -144185424

[Debian Bug Tracking System]

Processing control commands:

> block 830200 with -1
Bug #830200 [release.debian.org] transition: perl
830200 was blocked by: 825629 825524 825231 834800 838394 834795 825609 825014 
825762 834798 834799 834797 836636 825012 837719 834249 834796
830200 was not blocking any bugs.
Added blocking bug(s) of 830200: 838851

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

Bug#838851: libcoro-perl: FTBFS with Perl 5.24: panic: corrupt saved stack index -144185424

[Niko Tyni]

Package: libcoro-perl
Version: 6.490-1
Severity: serious
User: debian-p...@lists.debian.org
Usertags: perl-5.24-transition
Control: block 830200 with -1

This package failed to build against Perl 5.24 on armel, armhf and i386,
with t/12_exit.t test 5 dying:

  panic: corrupt saved stack index -144185424.

Upstream 6.5 changelog has this:

  - adjust to PL_savestack changes in perl 5.24 (adapted from
the debian patch, which unfortunately gets it wrong).

so it's probably time to try the upstream code which should work on
5.24 nowadays.
-- 
Niko Tyni   nt...@debian.org

Bug#838734: [plasma-discover] plasma-discover uninstalls packages during upgrades without asking for confirmation

[Matthias Klumpp]

Discover is for end-users with no technical knowledge. Showing extra
dialog boxes with crazy text won't help and just be visual clitter,
since people will press "Yes" anyway. Also, Discover isn't really to
blame for the underlying problem, which is a busted archive, something
that never happens in any stable distribution.
However, it would be nice if Discover handled this situation better on
unstable development versions of a distro.

I see the following possible solutions:

1) Have Discover detect an unstable distribution, and if it finds one,
show an extra confirmation box if changes that cause the removal of a
package are detected.

2) Just display removals as seperate items in the updates list
unconditionally - people on unstable distros would just need to read
the information then.

3) Show a "This update is potentially disruptive if you are using an
unstable distribution" or any other meaningful message when big
changes are detected (e.g. > 10 packages being removed)

Since even on stable distros sometimes transitions happen and stuff
gets removed, adding an unconditional dialog seems like a bad idea,
simply because it's meaningless for average users.

I'll talk to the usability people about the different options, and
hopefully we can land one of them before Plasma 5.8 is released.

Cheers,
Matthias

Processed: found 836320 in 0.3.4-1, fixed 836320 in 0.3.4-1+deb7u1

[Debian Bug Tracking System]

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

> found 836320 0.3.4-1
Bug #836320 [src:mactelnet] mactelnet: CVE-2016-7115
Marked as found in versions mactelnet/0.3.4-1.
> # fixed in Wheezy LTS
> fixed 836320 0.3.4-1+deb7u1
Bug #836320 [src:mactelnet] mactelnet: CVE-2016-7115
The source 'mactelnet' and version '0.3.4-1+deb7u1' do not appear to match any 
binary packages
Marked as fixed in versions mactelnet/0.3.4-1+deb7u1.
> thanks
Stopping processing here.

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

Bug#831174: gcc-avr: diff for NMU version 1:4.9.2+Atmel3.5.0-1.1

[Hakan Ardo]

I'm releaseing my version now, which I suppose cancels the NMU?

On Sun, Sep 25, 2016 at 12:36 PM, Sebastian Ramacher 
wrote:

> On 2016-09-25 10:40:34, Hakan Ardo wrote:
> > Thanx. I've got a version on the way that instead applies this upstream
> fix
> > for gcc 6 compatibility:
> >
> > https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=
> ec1cc0263f156f70693a62cf17b254a0029f4852
> >
> > I would prefer to go with thatone unless you have strong reasons for your
> > approach?
>
> No, not all. Just let me know if you prefer if I'd delay it longer or
> cancel it
> altogether.
>
> Cheers
>
> >
> > On Sat, Sep 24, 2016 at 11:43 PM, Sebastian Ramacher <
> sramac...@debian.org>
> > wrote:
> >
> > > Control: tags 831174 + patch
> > > Control: tags 831174 + pending
> > >
> > > Dear maintainer,
> > >
> > > I've prepared an NMU for gcc-avr (versioned as 1:4.9.2+Atmel3.5.0-1.1)
> and
> > > uploaded it to DELAYED/2. Please feel free to tell me if I
> > > should delay it longer.
> > >
> > > Regards.
> > >
> > > --
> > > Sebastian Ramacher
> > >
> >
> >
> >
> > --
> > Håkan Ardö
>
> --
> Sebastian Ramacher
>



-- 
Håkan Ardö

Processed: Re: wordpress really needs apache2's mod_rewrite enabled - either as a default, or well documented

[Debian Bug Tracking System]

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

> severity 838819 normal
Bug #838819 [wordpress] wordpress really needs apache2's mod_rewrite enabled - 
either as a default, or well documented
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#838819: wordpress really needs apache2's mod_rewrite enabled - either as a default, or well documented

[Santiago Vila]

severity 838819 normal
thanks

On Sun, 25 Sep 2016, Josh Stern wrote:

> I'm a newbie to apache & wordpress, working with testing out wordpress
> in a virtual hosts configuration on my own box.  After getting
> wordpress up and running, I found that a lot of basic functionality
> was not working correctly & it took me a while to track down the
> problem.  It turns out that many wordpress packages require a
> permalinks setup other than the default to function.  However,
> wordpress's ability to find it's own pages with permalinks other than
> the default seems to depend on apache2 having mod_rewrite enabled,
> which was not true of the default installation, & seemingly not well
> documented by wordpress, either online or on the debian system.
> Ideally this info should appear as part of a prominent README and
> perhaps be configured by the wordpress package installation.   I
> understand that mod_rewrite may be considered a minor security risk,
> but seemingly one accepts that with the decision to use the wordpress
> package.

Hi.

I'm not the maintainer, but WordPress works fine with nginx, which has
nothing to do with Apache, so there is not really a "dependency" on
Apache's mod_rewrite.

I'm downgrading this to normal because it's a documentation bug at most.
(Documentation bugs are usually minor or normal, unless the bug is that
we tell the user to "rm -rf /" as root or things like that).

Maybe the documentation you ask is in

/usr/share/doc/wordpress/examples/apache.conf.

(examples are also considered to be "documentation")

Thanks.

Bug#811846: marked as done (xbase64: FTBFS with GCC 6: no match for)

[Debian Bug Tracking System]

Your message dated Sun, 25 Sep 2016 17:09:58 +
with message-id 
and subject line Bug#811846: fixed in xbase64 3.1.2-7
has caused the Debian Bug report #811846,
regarding xbase64: FTBFS with GCC 6: no match for
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.)


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

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

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

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

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> /bin/bash ../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. 
> -I/<>  -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 -fPIE 
> -fstack-protector-strong -Wformat -Werror=format-security -MT xblock.lo -MD 
> -MP -MF .deps/xblock.Tpo -c -o xblock.lo xblock.cpp
> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I/<> -Wdate-time 
> -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -MT xblock.lo -MD -MP -MF .deps/xblock.Tpo -c 
> xblock.cpp  -fPIC -DPIC -o .libs/xblock.o
> xblock.cpp: In constructor 'xbLock::xbLock(xbDbf*)':
> xblock.cpp:87:37: error: no match for 'operator<<' (operand types are 
> 'std::basic_ostream' and 'std::ostream {aka std::basic_ostream}')
>std::cout << "xbLock constructor" << std::cout;
>~~^~
> 
> In file included from /usr/include/c++/6/iostream:39:0,
>  from /<>/xbase64/xbstring.h:55,
>  from /<>/xbase64/xbdate.h:58,
>  from /<>/xbase64/xbase64.h:123,
>  from xblock.cpp:55:
> /usr/include/c++/6/ostream:628:5: note: candidate: std::basic_ostream<_CharT, 
> _Traits>& std::operator<<(std::basic_ostream<_CharT, _Traits>&&, const _Tp&) 
> [with _CharT = char; _Traits = std::char_traits; _Tp = 
> std::basic_ostream] 
>  operator<<(basic_ostream<_CharT, _Traits>&& __os, const _Tp& __x)
>  ^~~~
> 
> /usr/include/c++/6/ostream:628:5: note:   conversion of argument 1 would be 
> ill-formed:
> xblock.cpp:87:13: error: cannot bind 'std::basic_ostream' lvalue to 
> 'std::basic_ostream&&'
>std::cout << "xbLock constructor" << std::cout;
>~~^~~
> 
> xblock.cpp:87:37: note: candidate: operator<<(int, int) 
>std::cout << "xbLock constructor" << std::cout;
>~~^~
> 
> xblock.cpp:87:37: note:   no known conversion for argument 2 from 
> 'std::ostream {aka std::basic_ostream}' to 'int'
> In file included from /usr/include/c++/6/iostream:39:0,
>  from /<>/xbase64/xbstring.h:55,
>  from /<>/xbase64/xbdate.h:58,
>  from /<>/xbase64/xbase64.h:123,
>  from xblock.cpp:55:
> /usr/include/c++/6/ostream:108:7: note: candidate: std::basic_ostream<_CharT, 
> _Traits>::__ostream_type& std::basic_ostream<_CharT, 
> _Traits>::operator<<(std::basic_ostream<_CharT, _Traits>::__ostream_type& 
> (*)(std::basic_ostream<_CharT, _Traits>::__ostream_type&)) [with _CharT = 
> char; _Traits = std::char_traits; std::basic_ostream<_CharT, 
> _Traits>::__ostream_type = std::basic_ostream]
>operator<<(__ostream_type& (*__pf)(__ostream_type&))
>^~~~
> 
> /usr/include/c++/6/ostream:108:7: note:   no known conversion for argument 1 
> from 'std::ostream {aka std::basic_ostream}' to 
> 'std::basic_ostream::__ostream_type& 
> (*)(std::basic_ostream::__ostream_type&) {aka std::basic_ostream& 
> (*)(std::basic_ostream&)}'
> /usr/include/c++/6/ostream:117:7: note: candidate: std::basic_ostream<_CharT, 
> _Traits>::__ostream_type& std::basic_ostream<_CharT, 
> _Traits>::operator<<(std::basic_ostream<_CharT, _Traits>::__ios_type& 
> (*)(std::basic_ostream<_CharT, _Traits>::__ios_type&)) [with _CharT = char; 
> _Traits = std::char_traits; std::basic_ostream<_CharT, 
> _Traits>::__ostream_type = std::basic_ostream; 
> std::basic_ostream<_CharT, _Traits>::__ios_type = std::basic_ios]
>operator<<(__ios_type& (*__pf)(__ios_type&))
>^~~~
--- End Message ---
--- Begin Message ---
Source: xbase64
Source-Version: 3.

Bug#837226: marked as done (zeroinstall-injector: FTBFS: Tests failures)

[Debian Bug Tracking System]

Your message dated Sun, 25 Sep 2016 17:10:15 +
with message-id 
and subject line Bug#837226: fixed in zeroinstall-injector 2.12-1
has caused the Debian Bug report #837226,
regarding zeroinstall-injector: FTBFS: Tests failures
to be marked as done.

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

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


-- 
837226: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837226
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zeroinstall-injector
Version: 2.10-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160910 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):
> 
> Can't find all required implementations:
> - http://foo/Binary.xml -> (problem)
> Main feed 'http://foo/Binary.xml' not available
> No known implementations at all
> 
> --
> ==
> Failure: 0install:17:download:20:distro
> 
> got None!
> --
> Ran: 273 tests in: 0.63 seconds.
> FAILED: Cases: 273 Tried: 273 Errors: 26 Failures: 1 Skip:  4 Todo: 0 
> Timeouts: 0.
> 
> Makefile:22: recipe for target 'test' failed

The full build log is available from:
   
http://aws-logs.debian.net/2016/09/10/zeroinstall-injector_2.10-2_unstable.log
(That DNS record was just updated. Use
http://ec2-52-58-237-241.eu-central-1.compute.amazonaws.com if it
doesn't work)

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 ---
Source: zeroinstall-injector
Source-Version: 2.12-1

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

Debian distribution maintenance software
pp.
Thomas Leonard  (supplier of updated zeroinstall-injector 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 25 Sep 2016 07:55:43 +
Source: zeroinstall-injector
Binary: 0install 0install-core zeroinstall-injector
Architecture: source amd64 all
Version: 2.12-1
Distribution: unstable
Urgency: medium
Maintainer: Thomas Leonard 
Changed-By: Thomas Leonard 
Description:
 0install   - cross-distribution packaging system
 0install-core - cross-distribution packaging system (non-GUI parts)
 zeroinstall-injector - transitional package for 0install
Closes: 837226
Changes:
 zeroinstall-injector (2.12-1) unstable; urgency=medium
 .
   * New upstream release.
   * Add missing build dep. Closes: #837226.
Checksums-Sha1:
 7eecaa3eec90691c52b43520ff3f3d317a309ae8 2269 zeroinstall-injector_2.12-1.dsc
 9359a9744e5a3c25f63cfcab575805a1bcebe578 441288 
zeroinstall-injector_2.12.orig.tar.bz2
 a022b2f0a3edf158a945abd9f9c9199f1b5ed7f8 13832 
zeroinstall-injector_2.12-1.debian.tar.xz
 65855cbd6659d4603bf95a9656223db320b05ebe 336586 
0install-core-dbgsym_2.12-1_amd64.deb
 665f5968b80c87c668595e84cf8a29e6e6862762 1344350 0install-core_2.12-1_amd64.deb
 060f0d660a6f5f3536012134f712321857c576d4 129646 
0install-dbgsym_2.12-1_amd64.deb
 fe0d1871df3fb31c51939943bee8c163ec3ca75f 584196 0install_2.12-1_amd64.deb
 4030892c5913174ee556fb1f809947d8d70573ba 1086 
zeroinstall-injector_2.12-1_all.deb
Checksums-Sha256:
 cd0f4122b007156e1db4849cf2477ad06776a0aa61269c40f25b4d024c5fa189 2269 
zeroinstall-injector_2.12-1.dsc
 facbe6970888926ea4be34c8e9a8f19e3b96d0f161fdc4871fd4f5be347e51c6 441288 
zeroinstall-injector_2.12.orig.tar.bz2
 4a418c2502273aff46ce0455b91cd12fcd661541a830cfc8ff0abddf1dd9c138 13832 
zeroinstall-injector_2.12-1.debian.tar.xz
 370bb635db26331229f7ce8fdbaabd3224f5869831436654a2d9ae4e5c99045e 336586 
0install-core-dbgsym_2.1

Bug#836762: marked as done (tor: please drop the build dependency on hardening-wrapper)

[Debian Bug Tracking System]

Your message dated Sun, 25 Sep 2016 17:08:44 +
with message-id 
and subject line Bug#836762: fixed in tor 0.2.9.3-alpha-1
has caused the Debian Bug report #836762,
regarding tor: please drop the build dependency on hardening-wrapper
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.)


-- 
836762: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836762
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tor
Version: 0.2.8.7-1
Severity: important
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: hardening-wrapper

This package builds using the hardening-includes package, which
is now replaced by dpkg-dev's DEB_BUILD_MAINT_OPTIONS settings.

Please consider dropping the build dependency of hardening-includes
and use the DEB_BUILD_MAINT_OPTIONS settings.

The goal is to remove hardening-wrapper for the stretch release.
Discussion about the removal is tracked in https://bugs.debian.org/836162

The severity of this report is likely to be raised before the release,
so that the hardening-wrapper package can be removed for the release.
--- End Message ---
--- Begin Message ---
Source: tor
Source-Version: 0.2.9.3-alpha-1

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

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

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

Debian distribution maintenance software
pp.
Peter Palfrader  (supplier of updated tor package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 25 Sep 2016 18:07:54 CEST
Source: tor
Binary: tor tor-dbg tor-geoipdb
Architecture: source all
Version: 0.2.9.3-alpha-1
Distribution: experimental
Urgency: medium
Maintainer: Peter Palfrader 
Changed-By: Peter Palfrader 
Description: 
 tor - anonymizing overlay network for TCP
 tor-dbg - debugging symbols for Tor
 tor-geoipdb - GeoIP database for Tor
Closes: 836762
Changes:
 tor (0.2.9.3-alpha-1) experimental; urgency=medium
 .
   [ Peter Palfrader ]
   * New upstream version.
 .
   [ Iain R. Learmonth ]
   * Removes dependency on hardening-wrapper, and
 build-depend on version >= 9 of debhelper instead
 so we can enable harding via DEB_BUILD_MAINT_OPTIONS
 (closes: #836762).
Checksums-Sha256: 
 e02bb2bf2f6c1a9fbf9cacab7c193bdc3b39096ed4c7a2328046b0a8fc5d6078 1862 
tor_0.2.9.3-alpha-1.dsc
 ee51f62191a33b2b3f50a2cf691dd6250fd0c110f97b8360785a1b56be5eee15 5240054 
tor_0.2.9.3-alpha.orig.tar.gz
 a7b34b0ddf9084f6c0953c9fa315192da4a761f14cfdc383b19c0748a9507656 40067 
tor_0.2.9.3-alpha-1.diff.gz
 819dbf05544a7a928719665e83c7414a88ec0bb9ae902ff4ec86372a517a492c 909680 
tor-geoipdb_0.2.9.3-alpha-1_all.deb
Checksums-Sha1: 
 a0273d66944571f4092aca1f6e5079981ac88f03 1862 tor_0.2.9.3-alpha-1.dsc
 bdfa1a83a175226453228c735b74059055447354 5240054 tor_0.2.9.3-alpha.orig.tar.gz
 6f27bb11589fd2db04f29bdfa370d2e515625d23 40067 tor_0.2.9.3-alpha-1.diff.gz
 beb8e042edce69e360a41d2aa9c7064a23633935 909680 
tor-geoipdb_0.2.9.3-alpha-1_all.deb
Files: 
 3c4f841b66609363768b03e94d62fbea 1862 net optional tor_0.2.9.3-alpha-1.dsc
 0356164a3e66e4d8cf2ac3413fe54cbe 5240054 net optional 
tor_0.2.9.3-alpha.orig.tar.gz
 3e7d4d863892b12221a4df93591cbe56 40067 net optional tor_0.2.9.3-alpha-1.diff.gz
 7c9d3b3cc5ebdda32b719572bc9bfb7c 909680 net extra 
tor-geoipdb_0.2.9.3-alpha-1_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBCAAGBQJX5/ZpAAoJEIYCyCA4cjMf8T4H/R9Ph2zqrDqEqdnWvY0eAXEA
nyFzQdsgr60CwJz7XXxhtaQ6dVkOai/fObUgEGG9XPRnLprOG7pfqRi2HaZZ4t3x
R4eYb5Rqru6kt1tdWJoF4jiswsAw+wWFQD7x09IAAVz6M59c5s/nneQgmyMGgXBa
p+jSQtvrhKrLPr5ed/UobT03IMjJMputZuWZjrV3QZZqSW8jAKvsDOXWcaXVKrvo
5UYK8MLZVZAWOpRuGdwu/ewpLEfSPuxysdFAQGAg7v09GN4D273MUaKzVEW/hshN
pwlgenqqB9MyWae+wDgCcwdLwft8/JOEE98ME+mSEUa3fu8yjsM6dnOyV+ZDg3g=
=B55N
-END PGP SIGNATURE End Message ---

Bug#833780: marked as done (undertaker: FTBFS with boost1.61)

[Debian Bug Tracking System]

Your message dated Sun, 25 Sep 2016 17:08:59 +
with message-id 
and subject line Bug#833780: fixed in undertaker 1.6.1-3
has caused the Debian Bug report #833780,
regarding undertaker: FTBFS with boost1.61
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.)


-- 
833780: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833780
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
source: undertaker
version: 1.6.1-2
severity: serious

Dear maintainer,

your package failed to build during the rebuilds for the boost1.61
transition, using gcc-6 as a compiler.
you can see the failed build logs at:
https://buildd.debian.org/status/logs.php?pkg=undertaker&ver=1.6.1-2%2Bb1

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: undertaker
Source-Version: 1.6.1-3

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

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

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

Debian distribution maintenance software
pp.
Reinhard Tartler  (supplier of updated undertaker package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 05 Mar 2016 18:52:29 -0500
Source: undertaker
Binary: undertaker
Architecture: source amd64
Version: 1.6.1-3
Distribution: unstable
Urgency: medium
Maintainer: Reinhard Tartler 
Changed-By: Reinhard Tartler 
Description:
 undertaker - variability-aware tool for static code analysis
Closes: 833780
Changes:
 undertaker (1.6.1-3) unstable; urgency=medium
 .
   * Rebuild against aspectc++/libpuma 2.0
   * Rebuild against flex 2.6.1 (Closes: #833780), run flex at build-time.
Checksums-Sha1:
 18035a0a1994cb3ad42ebd10d1b358b79f9dee4c 2197 undertaker_1.6.1-3.dsc
 5b7e151d2dc4961e621ffc82f4601d3ad2af2cf0 18100 undertaker_1.6.1-3.debian.tar.xz
 46c3e3f9a440ef3a40e6c2d24648354b6d0e3852 1330152 
undertaker-dbgsym_1.6.1-3_amd64.deb
 2f0116f434a8e3f22e278cbe356a11fa4afaf846 1146592 undertaker_1.6.1-3_amd64.deb
Checksums-Sha256:
 c255cb28ba8477c9e0fc62841646eb624b6f790f8a97b4b31e53d27aa55f2476 2197 
undertaker_1.6.1-3.dsc
 349baf8d22ea50519c14da7305097033d21647351b9f590275458de15cc54b90 18100 
undertaker_1.6.1-3.debian.tar.xz
 2269b8532c4020fb0ac0587efcc7eabb5b76061fd774a362e39ae0d916fbb698 1330152 
undertaker-dbgsym_1.6.1-3_amd64.deb
 f46bcd109fcc2c10a847ec73021ce993729952982f5dac1aca80a3b9fe5c8a47 1146592 
undertaker_1.6.1-3_amd64.deb
Files:
 009ca6c1ef1e0a9328ef6de138cf96d3 2197 devel optional undertaker_1.6.1-3.dsc
 9cd441dad7f59b528fd7a2afdaf7d64b 18100 devel optional 
undertaker_1.6.1-3.debian.tar.xz
 174a9028264fb6d9aa0a4f94f49b6817 1330152 debug extra 
undertaker-dbgsym_1.6.1-3_amd64.deb
 c0e9e7195eecc45f4df193a562fa659d 1146592 devel optional 
undertaker_1.6.1-3_amd64.deb

-BEGIN PGP SIGNATURE-

iQIxBAEBCAAbBQJX5/emFBxzaXJldGFydEB0YXV3YXJlLmRlAAoJEGEJKruXQZ3z
eC0P/AovFtxYZ9x8ZoFzwI0L1mkHLpde+9yErXDjirUN8OmPT/1kj2NKOPQ3GAAi
Q5HqTkqxs5VsFkxnUrnbxSjKgWNs8ktMPMG2gD5Q7TiaE++FV8InFUK7Zeyab0HT
zjVuae5BxRNBv6+mLmLFzwd9QTBc5QQYY2jY9EpfrcNAF3p6pt1eh3lvtFdpDCzH
Tk8BR5Y7bDFPJ9jr0s25RCTYBw2lHnbMt0fRTpaV1+h/dwM9Wog8GuFz+yANrkE9
PVBoy2i+hxVJw6apP5LqXY2xPeCHLs43ZSfHE29MZMZ/9fWN7/qKlpHItFuhevjb
dYB674BUtNs8xJEnCM3BatSvmZGb6AzE8b9usfdM7Vx10ljZAAfw/RlDbRDPsxnv
0y1JqGFNh1/7Qq2MlliJ4S584FiF0xmgMenk0gcyfN1HR+hf/Mkxs9A5dODFw5d9
ZZEP3GR1FAIEt0Hizsub8xR3Ik8sk2goh44XztqXeFxAEe2eg5HCeh6LmRYK9MIj
1++g0z6PfbATFeTFhhUAO3N3MWXqOPkAyVFkbD6zvyhClyIr7mw8i+8OwT/h6amt
HUW4vqasS28b/xC83hSItMY6hN1Q8M4Jd10k824hgRBvtcWlPRcs53gQdrScYlof
12GAr5bPDPYTuQtyhXUBJK+YxybsHWI7wzwr4xk7V/KnChNb
=nOE1
-END PGP SIGNATURE End Message ---

Bug#838828: marked as done (pyeapi: FTBFS 286019 times out of 41990400 (approx 1 every 147 times))

[Debian Bug Tracking System]

Your message dated Sun, 25 Sep 2016 17:06:39 +
with message-id 
and subject line Bug#838828: fixed in pyeapi 0.7.0-1
has caused the Debian Bug report #838828,
regarding pyeapi: FTBFS 286019 times out of 41990400 (approx 1 every 147 times)
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.)


-- 
838828: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838828
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pyeapi
Version: 0.6.1-2
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with python3,python2,sphinxdoc --buildsystem=pybuild
   dh_testdir -i -O--buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:184: python2.7 setup.py config 
running config
I: pybuild base:184: python3.5 setup.py config 
running config
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build
I: pybuild base:184: /usr/bin/python setup.py build 

[... snipped ...]

test_make_connection_raises_typeerror (test_client.TestClient) ... ok
test_missing_connection_raises_attribute_error (test_client.TestClient) ... ok
test_node_hasattr_connection (test_client.TestClient) ... ok
test_node_repr_returns (test_client.TestClient) ... ok
test_node_returns_cached_startup_confgi (test_client.TestClient) ... ok
test_node_returns_running_config (test_client.TestClient) ... ok
test_node_returns_startup_config (test_client.TestClient) ... ok
test_node_str_returns (test_client.TestClient) ... ok
test_api_autoloader (test_client.TestNode) ... ok
test_config_with_multiple_commands (test_client.TestNode) ... ok
test_config_with_multiple_multilines (test_client.TestNode) ... ok
test_config_with_single_command (test_client.TestNode) ... ok
test_config_with_single_multiline (test_client.TestNode) ... ok
test_enable_authentication (test_client.TestNode) ... ok
test_enable_with_config_statement (test_client.TestNode) ... ok
test_enable_with_multiple_commands (test_client.TestNode) ... ok
test_enable_with_single_command (test_client.TestNode) ... ok
test_get_config (test_client.TestNode) ... ok
test_get_config_as_string (test_client.TestNode) ... ok
test_get_config_raises_type_error (test_client.TestNode) ... ok
test_collapse_mixed (test_utils.TestUtils) ... ok
test_collapse_range (test_utils.TestUtils) ... ok
test_collapse_singles (test_utils.TestUtils) ... ok
test_debug (test_utils.TestUtils) ... ok
test_expand_mixed (test_utils.TestUtils) ... ok
test_expand_range (test_utils.TestUtils) ... ok
test_expand_singles (test_utils.TestUtils) ... ok
test_import_module (test_utils.TestUtils) ... ok
test_import_module_raises_import_error (test_utils.TestUtils) ... ok
test_load_module (test_utils.TestUtils) ... ok
test_load_module_raises_import_error (test_utils.TestUtils) ... ok
test_make_iterable_from_iterable (test_utils.TestUtils) ... ok
test_make_iterable_from_string (test_utils.TestUtils) ... ok
test_make_iterable_raises_type_error (test_utils.TestUtils) ... ok

==
FAIL: test_isvlan_with_string (test_api_vlans.TestApiVlans)
--
Traceback (most recent call last):
  File 
"/<>/.pybuild/pythonX.Y_2.7/build/test/unit/test_api_vlans.py", 
line 52, in test_isvlan_with_string
self.assertFalse(pyeapi.api.vlans.isvlan(random_string()))
AssertionError: True is not false

--
Ran 333 tests in 0.233s

FAILED (failures=1)
E: pybuild pybuild:276: test: plugin distutils failed with: exit code=1: cd 
/<>/.pybuild/pythonX.Y_2.7/build; python2.7 -m unittest discover 
-v test/unit
dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
debian/rules:6: recipe for target 'build-indep' failed
make: *** [build-indep] Error 25
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The failing test creates a random string and then ensures that it's
not a valid vlan value (a number between 1 and 4094).

So this is what happens:

1 out of 50 times the string will have length 1.
Of those, 9 out of 10+26 times the string will be a valid vlan.
(from 1 to 9)

1 out 

Bug#811846: #811846: status?

[John Paul Adrian Glaubitz]

Hi Pino!

On 09/25/2016 02:07 PM, Pino Toscano wrote:
> Note that, if nothing happens within few days (say, friday 30th), then
> I'll NMU/2 the patch I sent earlier; it has been already 3 months since
> the switch to GCC 6, and this bug was reported months earlier.
> xbase64 is not a leaf package, so leaving it unfixed means blocking
> other packages (calligra, at least in my case).

I uploaded xbase64 earlier today but I'm still waiting for the ACCEPT mail.

If that doesn't happen within the next two hours, I will try to reupload
the package. Please do therefore not NMU this package.

Thanks,
Adrian

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



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#838353: gstreamermm-1.0: FTBFS: check.cc:57:69: error: cannot convert 'Glib::RefPtr

[Debian Bug Tracking System]

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

> tags 838353 upstream fixed-upstream pending
Bug #838353 [src:gstreamermm-1.0] gstreamermm-1.0: FTBFS: check.cc:57:69: 
error: cannot convert 'Glib::RefPtr' to 'bool' for argument '1' 
to 'void ThrowIf(bool, const Glib::ustring&)'
Added tag(s) upstream, pending, and fixed-upstream.
> thanks
Stopping processing here.

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

Bug#838677: python-jellyfish: FTBFS: dh: unable to load addon sphinxdoc

[Diego M. Rodriguez]

Hello Aaron,

thanks a lot for reporting the bug and for the hint on how to solve the
issue, it's much appreciated! It seems my pbuilder-based setup was not
properly tuned to detect the issue during my first round of packaging,
but I have switched to sbuild (--no-arch-all) and have been able to
replicate the problem.

As mentioned on the auto-generated mail, I'm preparing a new release
with hopefully includes a fix for this bug [1].

Best regards,

[1] 
https://anonscm.debian.org/cgit/python-modules/packages/python-jellyfish.git/commit/?id=a5915aabd07f8fe8ce396c59298c791942ff625c

-- 
Diego M. Rodriguez
36B3 42A9 9F2F 2CFB F79B  FF9B B6C4 B901 06BC E232



signature.asc
Description: Digital signature

Bug#838353: gstreamermm-1.0: FTBFS: check.cc:57:69: error: cannot convert 'Glib::RefPtr

[Philip Rinn]

tags 838353 upstream fixed-upstream pending
thanks

Hi Chris,

thanks for the report. I fixed[1] the bug and asked my sponsor to upload the 
fixed
package.

Best,
Philip

[1]
https://anonscm.debian.org/cgit/collab-maint/gstreamermm-1.0.git/commit/?id=9180dc0219a99b0519219bb4abefaeb9792c74b5



signature.asc
Description: OpenPGP digital signature

Bug#838544: ext4: ext4_iget:4476: inode #8: comm mount: checksum invalid

[Julien Cristau]

On Sun, Sep 25, 2016 at 17:06:56 +0200, Michael Biebl wrote:

> On Thu, 22 Sep 2016 07:51:36 +0200 Stefan Fritsch  wrote:
> > Package: src:linux
> > Version: 4.7.4-2
> > Severity: grave
> > Justification: renders package unusable
> > 
> > When booting with linux-image-4.7.0-1-amd64 4.7.4-2, one of my
> > filesystems fails to mount with:
> > 
> > ext4_iget:4476: inode #8: comm mount: checksum invalid
> > 
> > A fsck does not find any errors, though, and the mount problem persists.
> > After rebooting with 4.6, it works.
> > 
> > It seems this is a known problem:
> > 
> > http://www.spinics.net/lists/linux-fsdevel/msg101888.html
> > 
> > 
> > Not sure about the severity, but I thought I should prevent it from
> > migrating to testing until you have looked at it.
> > 
> > 
> 
> Does this affect 4.7.2-1 as well, i.e. the current version in testing?

The current version in testing is 4.6.4-1.

Cheers,
Julien

Bug#830672: marked as done (golang-github-azure-go-autorest: accesses the internet during build)

[Debian Bug Tracking System]

Your message dated Sun, 25 Sep 2016 16:56:27 +
with message-id 
and subject line Bug#830672: fixed in golang-github-azure-go-autorest 7.0.4-3
has caused the Debian Bug report #830672,
regarding golang-github-azure-go-autorest: accesses the internet during build
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.)


-- 
830672: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830672
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-azure-go-autorest
Version: 7.0.4-1
Severity: serious
Justification: Policy 4.9
User: la...@debian.org
Usertags: network-access

Dear Maintainer,

Whilst golang-github-azure-go-autorest builds successfully on unstable/amd64, 
according to
Debian Policy 4.9 packages may not attempt network access during
a build.

  00:00:00.00 IP 17e100504765.35716 > dnscache.uct.ac.za.domain: 33685+ 
? microsoft.com. (31)
  00:00:00.48 IP 17e100504765.33860 > dnscache.uct.ac.za.domain: 20870+ A? 
microsoft.com. (31)
  00:00:00.017802 IP dnscache.uct.ac.za.domain > 17e100504765.33860: 20870 
5/4/8 A 104.40.211.35, A 104.43.195.251, A 23.100.122.175, A 23.96.52.53, A 
191.239.213.197 (367)
  00:00:00.208338 IP dnscache.uct.ac.za.domain > 17e100504765.35716: 33685 
0/1/0 (86)
  00:00:00.208773 IP 17e100504765.35524 > 104.40.211.35.https: Flags [S], seq 
480852211, win 29200, options [mss 1460,sackOK,TS val 120877368 ecr 
0,nop,wscale 7], length 0
  00:00:00.422695 IP 104.40.211.35.https > 17e100504765.35524: Flags [S.], seq 
4072704715, ack 480852212, win 8192, options [mss 1440,nop,wscale 8,sackOK,TS 
val 216103281 ecr 120877368], length 0

  [..]

The full build log (including tcpdump output) is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


golang-github-azure-go-autorest.7.0.4-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: golang-github-azure-go-autorest
Source-Version: 7.0.4-3

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

Debian distribution maintenance software
pp.
Martín Ferrari  (supplier of updated 
golang-github-azure-go-autorest package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 25 Sep 2016 15:03:48 +
Source: golang-github-azure-go-autorest
Binary: golang-github-azure-go-autorest-dev
Architecture: source all
Version: 7.0.4-3
Distribution: unstable
Urgency: medium
Maintainer: pkg-go 
Changed-By: Martín Ferrari 
Description:
 golang-github-azure-go-autorest-dev - HTTP request pipeline suitable for use 
across multiple go-routine
Closes: 830672
Changes:
 golang-github-azure-go-autorest (7.0.4-3) unstable; urgency=medium
 .
   * Patch more tests that were accessing the network, hopefully this time it
 closes: #830672.
   * Add myself to Uploaders.
Checksums-Sha1:
 ea2adcbf0174c7ced4b6357a3c4a6e0582994d45 2317 
golang-github-azure-go-autorest_7.0.4-3.dsc
 45fe39c803f57ee8a32458464a9a5fdb46f20fe3 3568 
golang-github-azure-go-autorest_7.0.4-3.debian.tar.xz
 f9820309b6e37db16525e96b0145829ae0104927 51476 
golang-github-azure-go-autorest-dev_7.0.4-3_all.deb
Checksums-Sha256:
 6ae6633a174822f3dc931c1a31e167b98d3d335cf4ba2dd5bb140d61046168ab 2317 
golang-github-azure-go-autorest_7.0.4-3.dsc
 d8dc817fb5ce7e3098b0d9fea549b589953118f88852cc8136a843d56f5d8245 3568 
golang-github-azure-go-autorest_7.0.4-3.debian.tar.xz
 a096d2be85642853ebef08fc6eaa61fe8adf283488b68139475cbc8c0c1429c0 51476 
golang-github-azure-go-autorest-dev_7.0.4-3_all.deb
Files:
 d8e9328ff76fada5a859d11b52dd9aa8 2317 devel extra 
golang-github-azure-go-autorest_7.0.4-3.dsc
 8e2fac0c1101387ac93ee1bd77ee5d1d 3568 devel extra 
golang-github-azure-go-autorest_7.0.4-3.debian.tar.xz
 30a4455e301116c7ed970bb75ebec21d 51476 devel extra 
golang-github-azure-go-autorest-dev_7.0.4-3_all.deb

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJX5+tKAAoJEF3Y4L+Ro9PaF0IP/RQKREGQ7J7TtAxMVWt26/Ap
XfKy9yi5rv6hvCcScOMUTvnl7YbxnusiZGoO5b/GNq0y41ul7ksZKItXDhfK

Bug#830311: marked as done (ipython: FTBFS: ImportError: No module named Crypto)

[Debian Bug Tracking System]

Your message dated Sun, 25 Sep 2016 16:55:06 +
with message-id 
and subject line Bug#830311: fixed in fabric 1.10.2-1.1
has caused the Debian Bug report #830311,
regarding ipython: FTBFS: ImportError: No module named Crypto
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.)


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

>From my pbuilder build log:

...
running build_scripts
creating build/scripts-3.5
Writing script to build/scripts-3.5/ipython
Writing script to build/scripts-3.5/ipcontroller
Writing script to build/scripts-3.5/ipengine
Writing script to build/scripts-3.5/ipcluster
Writing script to build/scripts-3.5/iptest
Writing script to build/scripts-3.5/ipython3
Writing script to build/scripts-3.5/ipcontroller3
Writing script to build/scripts-3.5/ipengine3
Writing script to build/scripts-3.5/ipcluster3
Writing script to build/scripts-3.5/iptest3
cd IPython/html && fab css
Traceback (most recent call last):
  File "/usr/bin/fab", line 9, in 
load_entry_point('Fabric==1.10.2', 'console_scripts', 'fab')()
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py",
line 542, in load_entry_point
return get_distribution(dist).load_entry_point(group, name)
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py",
line 2569, in load_entry_point
return ep.load()
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py",
line 2229, in load
return self.resolve()
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py",
line 2235, in resolve
module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/usr/lib/python2.7/dist-packages/fabric/main.py", line 19, in 
from fabric import api, state, colors
  File "/usr/lib/python2.7/dist-packages/fabric/api.py", line 11, in 
from fabric.decorators import (hosts, roles, runs_once, with_settings, task,
  File "/usr/lib/python2.7/dist-packages/fabric/decorators.py", line
9, in 
from Crypto import Random
ImportError: No module named Crypto
debian/rules:23: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 1
make[1]: Leaving directory '/build/ipython-2.4.1'
debian/rules:8: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
-- 
Daniel Schepler
--- End Message ---
--- Begin Message ---
Source: fabric
Source-Version: 1.10.2-1.1

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

Debian distribution maintenance software
pp.
Johannes Brandstätter  (supplier of updated fabric package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 25 Sep 2016 14:12:00 +0200
Source: fabric
Binary: fabric
Architecture: source
Version: 1.10.2-1.1
Distribution: unstable
Urgency: medium
Maintainer: Andrew Starr-Bochicchio 
Changed-By: Johannes Brandstätter 
Description:
 fabric - Simple Pythonic remote deployment tool
Closes: 830311
Changes:
 fabric (1.10.2-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add python-crypto to Depends and Build-Depends. (Closes: #830311)
Checksums-Sha1:
 674839ae5a8dded16df093bb46257f2a4dc5e357 1907 fabric_1.10.2-1.1.dsc
 126546b4cd8df6100502dfc2eff56d3d0d34a1ea 10624 fabric_1.10.2-1.1.debian.tar.xz
Checksums-Sha256:
 64eb9f9c8ba1c759cbac078da292186843d94ae50f8d49ece6da9d25e92b1ce0 1907 
fabric_1.10.2-1.1.dsc
 064efafead275facddad060931e1c63e182f4fbdbc2dff76bba6185b2c750284 10624 
fabric_1.10.2-1.1.debian.tar.xz
Files:
 7356e446bbc2c67a0aa4d31aceb42bdf 1907 net optional fabric_1.10.2-1.1.dsc
 617a63172b2a606114b6d4454e1c4d4b 10624 net optional 
fabric_1.10.2-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJX57/1AAoJEGny/FFupxmT3yIP/1S/TPUCqSM4ihf9B5q4CpUN
ujfASAlFSQtswDspG0yPmETWIE2e0TRDI0FcQrhU6LKXojFkRuEi9W7K9hs8Kf/h
HxidpS/7FCqa3390iU9Kqe/kQ57Sud3Kxjqi5qp6Ro84YS5VtKTL8vkI30Adx3z7
6LUQhF8UpxjETfdHfaLFDIHTgXmjkD

Bug#838667: marked as done (aufs-dkms: unconditionally tries to build a module for the running kernel)

[Debian Bug Tracking System]

Your message dated Sun, 25 Sep 2016 16:53:12 +
with message-id 
and subject line Bug#838667: fixed in aufs 4.7+20160912-2
has caused the Debian Bug report #838667,
regarding aufs-dkms: unconditionally tries to build a module for the running 
kernel
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.)


-- 
838667: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838667
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: aufs-dkms
Version: 4.7+20160912-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Looks like it tries to build the module for the running kernel,
not the one that has been requested.

Selecting previously unselected package aufs-dkms.
(Reading database ... 27590 files and directories currently installed.)
Preparing to unpack .../aufs-dkms_4.7+20160912-1_amd64.deb ...
Unpacking aufs-dkms (4.7+20160912-1) ...
Setting up aufs-dkms (4.7+20160912-1) ...
Loading new aufs-4.7+20160912 DKMS files...
dpkg: warning: version '*-*' has bad syntax: version number does not start with 
digit
It is likely that 4.6.0-1-amd64 belongs to a chroot's host
Building for 4.7.0-1-amd64
Building initial module for 4.7.0-1-amd64
Error! Bad return status for module build on kernel: 4.7.0-1-amd64 (x86_64)
Consult /var/lib/dkms/aufs/4.7+20160912/build/make.log for more information.

DKMS make.log for aufs-4.7+20160912 for kernel 4.7.0-1-amd64 (x86_64)
Fri Sep 23 13:02:13 UTC 2016
make: Entering directory '/var/lib/dkms/aufs/4.7+20160912/build'
Makefile:10: could not find kernel config file. internal auto-config may fail
config.mk:55: CONFIG_AUFS_SBILIST is enabled but CONFIG_AUFS_MAGIC_SYSRQ nor 
CONFIG_PROC_FS
-I/var/lib/dkms/aufs/4.7+20160912/build/include -DCONFIG_AUFS_FS_MODULE 
-UCONFIG_AUFS -DCONFIG_AUFS_BRANCH_MAX_127 -DCONFIG_AUFS_SBILIST 
-DCONFIG_AUFS_DEBUG
make -C /lib/modules/4.6.0-1-amd64/build 
M=/var/lib/dkms/aufs/4.7+20160912/build/fs/aufs 
EXTRA_CFLAGS="-I/var/lib/dkms/aufs/4.7+20160912/build/include 
-DCONFIG_AUFS_FS_MODULE -UCONFIG_AUFS -DCONFIG_AUFS_BRANCH_MAX_127 
-DCONFIG_AUFS_SBILIST -DCONFIG_AUFS_DEBUG" modules
make[1]: Entering directory '/var/lib/dkms/aufs/4.7+20160912/build'
make[1]: *** /lib/modules/4.6.0-1-amd64/build: No such file or directory.  Stop.
make[1]: Leaving directory '/var/lib/dkms/aufs/4.7+20160912/build'
Makefile:45: recipe for target 'fs/aufs/aufs.ko' failed
make: *** [fs/aufs/aufs.ko] Error 2
make: Leaving directory '/var/lib/dkms/aufs/4.7+20160912/build'


Andreas
--- End Message ---
--- Begin Message ---
Source: aufs
Source-Version: 4.7+20160912-2

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

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

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

Debian distribution maintenance software
pp.
Jan Luca Naumann  (supplier of updated aufs package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 23 Sep 2016 23:33:21 +0200
Source: aufs
Binary: aufs-dkms aufs-dev
Architecture: source amd64
Version: 4.7+20160912-2
Distribution: sid
Urgency: medium
Maintainer: Filesystems Group 
Changed-By: Jan Luca Naumann 
Description:
 aufs-dev   - Development files for aufs
 aufs-dkms  - DKMS files to build and install aufs
Closes: 838626 838667
Changes:
 aufs (4.7+20160912-2) unstable; urgency=medium
 .
   * debian/aufs-dkms.dkms:
 - KDIR to correct value for DKMS builds. (Closes: #838667)
 - Add BUILD_EXCLUSIVE_KERNEL directive.
   * debian/control:
 - Add Breaks/Replaces: linux-libc-dev (<< 3.18-1~exp1)
   relation for aufs-dev binary package (Closes: #838626).
Checksums-Sha1:
 14b507fd1e26a1a1f7733ae42acfb90b2daa6178 1969 aufs_4.7+20160912-2.dsc
 44faece78a2a6b9e5b7355a888410dc1e13a2fe3 3180 aufs_4.7+20160912-2.debian.tar.xz
 25812e7d4ae46dafb2e0633c3a4c2dd63d6e813c 5208 aufs-dev_4.7+20160912-2_amd64.deb
 3a1bb3f539ade3cf1d37990db0c68eb9a442f8e1 167650 
aufs-dkms_4.7+20160912-2_amd64.deb
Checksums-Sha256:
 3f78fe104663e958bae71c0324d70163c91fa5e692a911f2e672106f2561073e 1969 
aufs_4.7+20160912-2.dsc
 07de2c3d1e3bdbf43f46948a81b13e3eeeab260bd18ced31580cc13c9e549ba3 3180 
aufs_4.7+20160912-2.debian.tar.xz
 512d10f

Processed: block 830200 with 825629

[Debian Bug Tracking System]

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

> # we missed this earlier for some reason
> block 830200 with 825629
Bug #830200 [release.debian.org] transition: perl
830200 was blocked by: 837719 825231 834795 834799 825014 834798 834796 834249 
825524 825012 836636 825609 834800 834797 825762 838394
830200 was not blocking any bugs.
Added blocking bug(s) of 830200: 825629
> thanks
Stopping processing here.

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

Bug#838626: marked as done (aufs-dev: fails to upgrade from 'jessie' - trying to overwrite /usr/include/linux/aufs_type.h)

[Debian Bug Tracking System]

Your message dated Sun, 25 Sep 2016 16:53:12 +
with message-id 
and subject line Bug#838626: fixed in aufs 4.7+20160912-2
has caused the Debian Bug report #838626,
regarding aufs-dev: fails to upgrade from 'jessie' - trying to overwrite 
/usr/include/linux/aufs_type.h
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.)


-- 
838626: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838626
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: aufs-dev
Version: 4.7+20160912-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package aufs-dev.
  Preparing to unpack .../aufs-dev_4.7+20160912-1_amd64.deb ...
  Unpacking aufs-dev (4.7+20160912-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/aufs-dev_4.7+20160912-1_amd64.deb (--unpack):
   trying to overwrite '/usr/include/linux/aufs_type.h', which is also in 
package linux-libc-dev:amd64 3.16.36-1+deb8u1
  Errors were encountered while processing:
   /var/cache/apt/archives/aufs-dev_4.7+20160912-1_amd64.deb


cheers,

Andreas


linux-libc-dev=3.16.36-1+deb8u1_aufs-dev=4.7+20160912-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: aufs
Source-Version: 4.7+20160912-2

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

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

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

Debian distribution maintenance software
pp.
Jan Luca Naumann  (supplier of updated aufs package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 23 Sep 2016 23:33:21 +0200
Source: aufs
Binary: aufs-dkms aufs-dev
Architecture: source amd64
Version: 4.7+20160912-2
Distribution: sid
Urgency: medium
Maintainer: Filesystems Group 
Changed-By: Jan Luca Naumann 
Description:
 aufs-dev   - Development files for aufs
 aufs-dkms  - DKMS files to build and install aufs
Closes: 838626 838667
Changes:
 aufs (4.7+20160912-2) unstable; urgency=medium
 .
   * debian/aufs-dkms.dkms:
 - KDIR to correct value for DKMS builds. (Closes: #838667)
 - Add BUILD_EXCLUSIVE_KERNEL directive.
   * debian/control:
 - Add Breaks/Replaces: linux-libc-dev (<< 3.18-1~exp1)
   relation for aufs-dev binary package (Closes: #838626).
Checksums-Sha1:
 14b507fd1e26a1a1f7733ae42acfb90b2daa6178 1969 aufs_4.7+20160912-2.dsc
 44faece78a2a6b9e5b7355a888410dc1e13a2fe3 3180 aufs_4.7+20160912-2.debian.tar.xz
 25812e7d4ae46dafb2e0633c3a4c2dd63d6e813c 5208 aufs-dev_4.7+20160912-2_amd64.deb
 3a1bb3f539ade3cf1d37990db0c68eb9a442f8e1 167650 
aufs-dkms_4.7+20160912-2_amd64.deb
Checksums-Sha256:
 3f78fe104663e958bae71c0324d70163c91fa5e692a911f2e672106f2561073e 1969 
aufs_4.7+20160912-2.dsc
 07de2c3d1e3bdbf43f46948a81b13e3eeeab260bd18ced31580cc13c9e549ba3 3180 
aufs_4.7+20160912-2.debian.tar.xz
 512d10f9ed29c33c42a2f2c1253a949890178f87ce81cd25ffb81c0e2a8fd9cc 5208 
aufs-dev_4.7+20160912-2_amd64.deb
 5206464936e72f4f1c50010014091ab7718f352ce250e7aa57cee7317861cd63 167650 
aufs-dkms_4.7+20160912-2_amd64.deb
Files:
 d529e47a2b7631e94dbb23cdd120dd8b 1969 kernel optional aufs_4.7+20160912-2.dsc
 9160e8a279c0e19c0cda3db5737a6f69 3180 kernel optional 
aufs_4.7+20160912-2.debian.tar.xz
 8420ab6cec873a3643052a1060f473b9 5208 kernel optional 
aufs-dev_4.7+20160912-2_amd64.deb
 422dcf9dd5b9b2ec501a987c2893cfcb 167650 kernel optional 
aufs-dkms_4.7+20160912-2_amd64.deb

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJX5+KPAAoJEHQmOzf1tfkTYwgP/RkiItqd+2S9j/artZUxBf60
KQ5iIV6XYFHYReZxQA70aIoak/o8a0reY3/KOF8fIO0/7JndoysYYrYxOsknbPoN
uIv47aPPiiodkbqh5Q/1BNr9ECGQeCduenA5ccLraF3DJAo982aUIr5xlbNiH9Qw
TEHxlmJttU1Wi6y1CAfN9MhuOgaCFeW5lDcoPqmGHHiVt/q9oAtO8w0FbWsykbSy
Alj8h/V3akOKoYpH0ZfaijxUxnjVMJhGePsGWdLv7UVLAmF4uoJvlHBFY7ggZ

Bug#779154: closing 779154

[Salvatore Bonaccorso]

close 779154 2.3.3-1
thanks

Processed: closing 779154

[Debian Bug Tracking System]

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

> close 779154 2.3.3-1
Bug #779154 [jabberd2] CVE-2015-2058
Ignoring request to alter fixed versions of bug #779154 to the same values 
previously set
Bug #779154 [jabberd2] CVE-2015-2058
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#800291: jade: Please migrate a supported debhelper compat level

[Neil Roeth]

Hi, Tobi,

The removal of jade, sp and openjade1.3 is coming along.   Openjade1.3
is done, it was actually removed from testing but there were no more
dependencies on it.  I was focusing recently on the sp binary package,
and most of those dependencies have been switched to opensp.  Jade is next.

There are tracking bugs already, 811310 and 811312.

Aboot and iputils have bugs with patches open to change sp to opensp.

Can you explain the output below?  I guess "dak rm jade" means remove
jade, while the -n means not to actually do it (no act).  What does -R
mean?  Does the command apply to the jade source package or the binary
package?  I'm guessing source since sp appears in the list and it is a
binary package built from the jade source package.

Thanks.

On 09/25/2016 07:04 AM, Tobias Frost wrote:
> Hi Neil,
>
> how is the removal going?
> I was wondering if there should be a dedicated bug to track the status
> of the progess? What do you think? 
>
>
> A "dak rm -Rn jade" yields to:
>
>
> # Broken Depends:
> xmldiff: xmldiff-xmlrev
>
> # Broken Build-Depends:
> aboot: sp
> alex: jade
> datapacker: jade
> dejagnu: jade
> gnome-packagekit: sp
> gstreamer1.0: jade (>= 1.2.1)
> iputils: sp
> kannel: jade
> libetpan: jade
> lprng-doc: jade
> mozart: sp
> pyepl: jade
> scons-doc: jade
>
>
> --
> tobi 
>
> On Thu, 29 Oct 2015 21:00:50 -0400 Neil Roeth  wrote:
>> I intend to remove this package from Debian rather than update
> it.  The
>> Debian packages openjade/opensp can be used instead. I will file bugs
>> against any packages that depend on jade and give them some time to
> be
>> updated before I file the actual removal bug for jade.
>>  
>> -- 
>> Neil Roeth
>>  
>>  
>>  


-- 
Neil Roeth

Bug#838677: marked as pending

[Diego M . Rodriguez]

tag 838677 pending
thanks

Hello,

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


http://git.debian.org/?p=python-modules/packages/python-jellyfish.git;a=commitdiff;h=767b5b8

---
commit 767b5b80bd3cc087d40e03cabb53b6981307b98a
Author: Diego M. Rodriguez 
Date:   Sun Sep 25 17:55:58 2016 +0200

Update changelog

diff --git a/debian/changelog b/debian/changelog
index afc01c9..03e8721 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+python-jellyfish (0.5.6-2) unstable; urgency=medium
+
+  * Move python-sphinx to Build-Depends. (Closes: #838677)
+  * Add Vcs-Git and Vcs-Browser fields.
+
+ -- Diego M. Rodriguez   Sun, 25 Sep 2016 17:55:05 +0200
+
 python-jellyfish (0.5.6-1) unstable; urgency=medium
 
   * Initial release. (Closes: #806716)

Processed: Bug#838677 marked as pending

[Debian Bug Tracking System]

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

> tag 838677 pending
Bug #838677 [src:python-jellyfish] python-jellyfish: FTBFS: dh: unable to load 
addon sphinxdoc
Warning: Unknown package 'src:python-jellyfish'
Added tag(s) pending.
Warning: Unknown package 'src:python-jellyfish'
> thanks
Stopping processing here.

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

Bug#830311: fabric: diff for NMU version 1.10.2-1.1

[Sebastian Ramacher]

On 2016-09-25 10:48:30, Andrew Starr-Bochicchio wrote:
> On Sun, Sep 25, 2016 at 8:15 AM, Sebastian Ramacher
>  wrote:
> > I've prepared an NMU for fabric (versioned as 1.10.2-1.1) and
> > uploaded it to DELAYED/2. Please feel free to tell me if I
> > should delay it longer.
> 
> Thanks! Feel free to upload directly to unstable.

Thanks, rescheduled to DELAYED/0.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Processed: severity of 838812 is grave

[Debian Bug Tracking System]

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

> severity 838812 grave
Bug #838812 [postgresql-common] pg_upgradecluster skips databases owned by a 
role who is not a user
Severity set to 'grave' from 'critical'
> thanks
Stopping processing here.

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

Bug#838838: postgresql-9.5_9.5.4-1+b1_mipsel.changes REJECTED

[Aurelien Jarno]

Package: postgresql-9.5
Version: 9.5.4-1
Severity: serious

The package has been binNMUed and the resulting package has been
rejected by dak:

On 2016-09-25 11:49, Debian FTP Masters wrote:
> Version check failed:
> Your upload included the binary package libpq5, version 9.5.4-1+b1, for 
> mipsel,
> however testing already has version 9.6~rc1-1.
> Uploads to unstable must have a higher version than present in testing.
> 
> ===
> 
> Please feel free to respond to this email if you don't understand why
> your files were rejected, or if you upload new files which address our
> concerns.

It seems that libpq5 is now provided by postgresql-9.6. Therefore
postgresql-9.5 should stop building it.

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

Processed: Pending fixes for bugs in the libgd-perl package

[Debian Bug Tracking System]

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

> tag 825629 + pending
Bug #825629 [src:libgd-perl] libgd-perl: FTBFS: Could not find gdlib-config in 
the search path. 
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#825629: Pending fixes for bugs in the libgd-perl package

[pkg-perl-maintainers]

tag 825629 + pending
thanks

Some bugs in the libgd-perl package are closed in revision
0da69d968b3715b74223898581c2d184d626befa in branch 'master' by gregor
herrmann

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

Commit message:

Add patch to use pkg-config instead of the removed gdlib-config.

Closes: #825629

Bug#817592: myspell: Removal of debhelper compat 4

[Chris Lamb]

tags 817592 + pending patch
thanks

I've uploaded myspell 3.0+pre3.1-24.2 to DELAYED/5:
  
  myspell (1:3.0+pre3.1-24.2) unstable; urgency=medium
  
* Non-maintainer upload.
* Move to debhelper compat level 9. (Closes: #817592)

The full debdiff is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff -u myspell-3.0+pre3.1/debian/changelog myspell-3.0+pre3.1/debian/changelog
--- myspell-3.0+pre3.1/debian/changelog
+++ myspell-3.0+pre3.1/debian/changelog
@@ -1,3 +1,10 @@
+myspell (1:3.0+pre3.1-24.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Move to debhelper compat level 9. (Closes: #817592)
+
+ -- Chris Lamb   Sun, 25 Sep 2016 17:11:41 +0200
+
 myspell (1:3.0+pre3.1-24.1) unstable; urgency=medium
 
   * Non-maintainer upload to fix FTBFS.
diff -u myspell-3.0+pre3.1/debian/compat myspell-3.0+pre3.1/debian/compat
--- myspell-3.0+pre3.1/debian/compat
+++ myspell-3.0+pre3.1/debian/compat
@@ -1 +1 @@
-4
+9
diff -u myspell-3.0+pre3.1/debian/control myspell-3.0+pre3.1/debian/control
--- myspell-3.0+pre3.1/debian/control
+++ myspell-3.0+pre3.1/debian/control
@@ -3,7 +3,7 @@
 Priority: extra
 Maintainer: Debian OpenOffice Team 
 Uploaders: Rene Engelhard , Chris Halls 
-Build-Depends: debhelper (>= 4.0.0), dpatch
+Build-Depends: debhelper (>= 9), dpatch
 Standards-Version: 3.6.1
 
 Package: myspell-tools

Processed: Re: myspell: Removal of debhelper compat 4

[Debian Bug Tracking System]

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

> tags 817592 + pending patch
Bug #817592 [src:myspell] myspell: Removal of debhelper compat 4
Added tag(s) pending and patch.
> thanks
Stopping processing here.

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

Processed: Pending fixes for bugs in the golang-github-azure-go-autorest package

[Debian Bug Tracking System]

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

> tag 830672 + pending
Bug #830672 [src:golang-github-azure-go-autorest] 
golang-github-azure-go-autorest: accesses the internet during build
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#830672: Pending fixes for bugs in the golang-github-azure-go-autorest package

[pkg-go-maintainers]

tag 830672 + pending
thanks

Some bugs in the golang-github-azure-go-autorest package are closed
in revision 945920e5daff89a5713f4d135fd92e3f822f246e in branch
'master' by Martín Ferrari

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-azure-go-autorest.git/commit/?id=945920e

Commit message:

Patch more tests that were accessing the network, hopefully this time it 
closes: #830672.

Bug#837226: zeroinstall-injector: FTBFS: Tests failures

[Chris Lamb]

Hi,

> zeroinstall-injector: FTBFS: Tests failures

I've just uploaded this from mentors.debian.net. Enjoy :)



Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Processed: found 838832 in 1:11.13.0~dfsg-1

[Debian Bug Tracking System]

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

> found 838832 1:11.13.0~dfsg-1
Bug #838832 [src:asterisk] asterisk: AST-2016-007
Marked as found in versions asterisk/1:11.13.0~dfsg-1.
> thanks
Stopping processing here.

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

Bug#838544: ext4: ext4_iget:4476: inode #8: comm mount: checksum invalid

[Michael Biebl]

On Thu, 22 Sep 2016 07:51:36 +0200 Stefan Fritsch  wrote:
> Package: src:linux
> Version: 4.7.4-2
> Severity: grave
> Justification: renders package unusable
> 
> When booting with linux-image-4.7.0-1-amd64 4.7.4-2, one of my
> filesystems fails to mount with:
> 
> ext4_iget:4476: inode #8: comm mount: checksum invalid
> 
> A fsck does not find any errors, though, and the mount problem persists.
> After rebooting with 4.6, it works.
> 
> It seems this is a known problem:
> 
> http://www.spinics.net/lists/linux-fsdevel/msg101888.html
> 
> 
> Not sure about the severity, but I thought I should prevent it from
> migrating to testing until you have looked at it.
> 
> 

Does this affect 4.7.2-1 as well, i.e. the current version in testing?
-- 
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#838833: asterisk: AST-2016-006

[Salvatore Bonaccorso]

Source: asterisk
Version: 1:13.10.0~dfsg-1
Severity: grave
Tags: security upstream

Hi

See the upstream advisory at
http://downloads.asterisk.org/pub/security/AST-2016-006.html . AFAICS,
still no CVE was assigned for this issue.

Regards,
Salvatore

Bug#838832: asterisk: AST-2016-007

[Salvatore Bonaccorso]

Source: asterisk
Version: 1:11.13.1~dfsg-2
Severity: grave
Tags: security upstream
Forwarded: https://issues.asterisk.org/jira/browse/ASTERISK-26272

Hi

See http://downloads.asterisk.org/pub/security/AST-2016-007.html and
https://issues.asterisk.org/jira/browse/ASTERISK-26272 for patches.

Regards,
Salvatore

Bug#830311: fabric: diff for NMU version 1.10.2-1.1

[Andrew Starr-Bochicchio]

On Sun, Sep 25, 2016 at 8:15 AM, Sebastian Ramacher
 wrote:
> I've prepared an NMU for fabric (versioned as 1.10.2-1.1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer.

Thanks! Feel free to upload directly to unstable.

-- Andrew Starr-Bochicchio

   Debian Developer 
   Ubuntu Developer 
   PGP/GPG Key ID: 3B56E2BBD53FDCB1

Bug#798296: bats: diff for NMU version 0.4.0-1.1

[Yaroslav Halchenko]

On September 25, 2016 5:48:15 AM EDT, Tobias Frost  wrote:
>
>
>Dear maintainer,
>
>With Santiago's suggestion considered, replacing the previous
>NMU with this one...
>
>I've prepared an NMU for bats (versioned as 0.4.0-1.1) and
>uploaded it to DELAYED/2. Please feel free to tell me if I
>should delay it longer.
>
>Regards.

Looks good to me. If need it faster, feel free to reupload without delay
-- 
Sent from a phone which beats iPhone.

Bug#838826: [Pkg-utopia-maintainers] Bug#838826: network-manager kills network on upgrade

[Michael Biebl]

Am 25.09.2016 um 14:59 schrieb Juha Jäykkä:
> Versions of packages network-manager depends on:
> pn  libndp0
> pn  libnm0 
> pn  libteamdctl0   

Do you have an idea why these packages are listed as not available?
If they are really not installed, then it would not be surprising that
network-manager is no longer functional.
Could you please check the state of those packages.

Michael

-- 
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#830672: [pkg-go] Bug#830672: Bug#830672: golang-github-azure-go-autorest: accesses the internet during build

[Martín Ferrari]

Chris,

On 29/08/16 11:29, Chris Lamb wrote:

> I bit of manual bisecting later, this is the test:
> 
>  
> http://sources.debian.net/src/golang-github-azure-go-autorest/7.0.4-2/autorest/azure/token_test.go/#L375

Thanks a lot, I should definitely improve my tooling for this kind of
test. I am uploading a (hopefully) fixed version now.


-- 
Martín Ferrari (Tincho)

Processed: 838829 blocks 838705

[Debian Bug Tracking System]

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

> block 838705 by 838829
Bug #838705 [libfsoframework] fso-datad: FTBFS: 
fsoframework-2.0.vapi:257.48-257.48: error: internal error: comparing type 
parameters with different parents
838705 was not blocked by any bugs.
838705 was not blocking any bugs.
Added blocking bug(s) of 838705: 838829
> thanks
Stopping processing here.

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

Bug#838829: valac: Feature Regression in vala 0.34

[Sebastian Reichel]

Package: valac
Version: 0.34.0-1
Severity: serious
Tags: upstream
Justification: upstream regression causes FTBFS in other package(s)

Hi,

valac no longer supports abstract functions with generics. This
construct is used by the freesmartphone.org stack, which is
packaged for Debian and FTBFS with valac > 0.34.0-1. This has
been reported in Debian Bug #838705.

The below standalone testcase, which compiles warning free
in vala 0.32, no longer works in vala 0.34 and demonstrates the
problem.

As far as I can see the regression has been introduced by the
following change:
https://mail.gnome.org/archives/commits-list/2016-July/msg02876.html

-
public abstract class basecl : Object {
public abstract void test(T parameter);
}

public class inheritcl : basecl {
public override void test(T parameter) {
stdout.printf("Just a test!\n");
}
}

int main(string[] args) {
var obj = new inheritcl();
obj.test("test");
return 0;
}
-

-- Sebastian

Bug#812261: marked as done (cppformat: FTBFS with GCC 6: Exception: SegFault in test suite)

[Debian Bug Tracking System]

Your message dated Sun, 25 Sep 2016 14:00:09 +
with message-id 
and subject line Bug#812261: fixed in cppformat 3.0.0+ds-1
has caused the Debian Bug report #812261,
regarding cppformat: FTBFS with GCC 6: Exception: SegFault in test suite
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.)


-- 
812261: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812261
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cppformat
Version: 1.1.0+ds-3
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-unknown

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

Unfortunately, it's not clear from the log why the build failed.
It's possible there's a bug in this package or in GCC.  It's also
possible I reported a non-issue, although I tried to avoid that.
I apologize in advance if this is the case.

If you have some time to look into this issue, that'd be great.  If
not, I can re-test the package with GCC 6 in a few weeks time.

You can find a snapshot of GCC 6 in experimental.  To build with
GCC 6, you can set CC=gcc-6 CXX=g++-6 explicitly.

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

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> 
> Start 3: format-impl-test
> 3/7 Test #3: format-impl-test .   Passed0.00 sec
> Start 4: printf-test
> 4/7 Test #4: printf-test ..   Passed0.01 sec
> Start 5: util-test
> 5/7 Test #5: util-test ***Exception: SegFault  0.53 
> sec
> [==] Running 30 tests from 6 test cases.
> [--] Global test environment set-up.
> [--] 1 test from AllocatorTest
> [ RUN  ] AllocatorTest.AllocatorRef
> 
> Start 6: posix-test
> 6/7 Test #6: posix-test ...   Passed0.01 sec
> Start 7: compile-test
> 7/7 Test #7: compile-test .   Passed   11.60 sec
> 
> 71% tests passed, 2 tests failed out of 7
> 
> Total Test time (real) =  13.33 sec
> 
> The following tests FAILED:
> 2 - format-test (SEGFAULT)
> 5 - util-test (SEGFAULT)
> Errors while running CTest
> Makefile:130: recipe for target 'test' failed
> make[1]: *** [test] Error 8

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: cppformat
Source-Version: 3.0.0+ds-1

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

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

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

Debian distribution maintenance software
pp.
Eugene V. Lyubimkin  (supplier of updated cppformat package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 24 Sep 2016 17:16:59 +0200
Source: cppformat
Binary: libfmt3-dev libfmt3-doc
Architecture: source amd64 all
Version: 3.0.0+ds-1
Distribution: experimental
Urgency: low
Maintainer: Eugene V. Lyubimkin 
Changed-By: Eugene V. Lyubimkin 
Description:
 libfmt3-dev - fast type-safe C++ formatting library -- development files
 libfmt3-doc - fast type-safe C++ formatting library -- documentation
Closes: 812261
Changes:
 cppformat (3.0.0+ds-1) experimental; urgency=low
 .
   * New upstream release.
 - Unit tests now pass when compiled with GCC6. (Closes: #812261)
   * debian/control:
 - Updated home page (new is http://fmtlib.net/).
 - Updated binary package names to use libfmt prefix (following
   the upstream name change).
 - Updated Standards-Version to 3.9.8, no changes needed.
   * debian/strip-orig-tar.sh:
 - Strip also GTest/GMock from new locations inside 3.0.0 tarball.
   * debian/patches:
 - Rebased.
 - 0010-test-cmakelists-don-t-guess-C-11-support.patch: added.
 - 0011-fmt-cmakelists-don-t-bother-with-exporting-CMake-con.patch: added.
 - 0012-test-format-test-FormatIntLocale-disabled.patch: added.
 - 0013-test-cmakelists-posix-mock-test-link-to-already-comp.patch: added.
 - 0014-fmt-cmakelists-really-separate-sources-

Bug#838828: pyeapi: FTBFS 286019 times out of 41990400 (approx 1 every 147 times)

[Santiago Vila]

Package: src:pyeapi
Version: 0.6.1-2
Severity: serious

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with python3,python2,sphinxdoc --buildsystem=pybuild
   dh_testdir -i -O--buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:184: python2.7 setup.py config 
running config
I: pybuild base:184: python3.5 setup.py config 
running config
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build
I: pybuild base:184: /usr/bin/python setup.py build 

[... snipped ...]

test_make_connection_raises_typeerror (test_client.TestClient) ... ok
test_missing_connection_raises_attribute_error (test_client.TestClient) ... ok
test_node_hasattr_connection (test_client.TestClient) ... ok
test_node_repr_returns (test_client.TestClient) ... ok
test_node_returns_cached_startup_confgi (test_client.TestClient) ... ok
test_node_returns_running_config (test_client.TestClient) ... ok
test_node_returns_startup_config (test_client.TestClient) ... ok
test_node_str_returns (test_client.TestClient) ... ok
test_api_autoloader (test_client.TestNode) ... ok
test_config_with_multiple_commands (test_client.TestNode) ... ok
test_config_with_multiple_multilines (test_client.TestNode) ... ok
test_config_with_single_command (test_client.TestNode) ... ok
test_config_with_single_multiline (test_client.TestNode) ... ok
test_enable_authentication (test_client.TestNode) ... ok
test_enable_with_config_statement (test_client.TestNode) ... ok
test_enable_with_multiple_commands (test_client.TestNode) ... ok
test_enable_with_single_command (test_client.TestNode) ... ok
test_get_config (test_client.TestNode) ... ok
test_get_config_as_string (test_client.TestNode) ... ok
test_get_config_raises_type_error (test_client.TestNode) ... ok
test_collapse_mixed (test_utils.TestUtils) ... ok
test_collapse_range (test_utils.TestUtils) ... ok
test_collapse_singles (test_utils.TestUtils) ... ok
test_debug (test_utils.TestUtils) ... ok
test_expand_mixed (test_utils.TestUtils) ... ok
test_expand_range (test_utils.TestUtils) ... ok
test_expand_singles (test_utils.TestUtils) ... ok
test_import_module (test_utils.TestUtils) ... ok
test_import_module_raises_import_error (test_utils.TestUtils) ... ok
test_load_module (test_utils.TestUtils) ... ok
test_load_module_raises_import_error (test_utils.TestUtils) ... ok
test_make_iterable_from_iterable (test_utils.TestUtils) ... ok
test_make_iterable_from_string (test_utils.TestUtils) ... ok
test_make_iterable_raises_type_error (test_utils.TestUtils) ... ok

==
FAIL: test_isvlan_with_string (test_api_vlans.TestApiVlans)
--
Traceback (most recent call last):
  File 
"/<>/.pybuild/pythonX.Y_2.7/build/test/unit/test_api_vlans.py", 
line 52, in test_isvlan_with_string
self.assertFalse(pyeapi.api.vlans.isvlan(random_string()))
AssertionError: True is not false

--
Ran 333 tests in 0.233s

FAILED (failures=1)
E: pybuild pybuild:276: test: plugin distutils failed with: exit code=1: cd 
/<>/.pybuild/pythonX.Y_2.7/build; python2.7 -m unittest discover 
-v test/unit
dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
debian/rules:6: recipe for target 'build-indep' failed
make: *** [build-indep] Error 25
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The failing test creates a random string and then ensures that it's
not a valid vlan value (a number between 1 and 4094).

So this is what happens:

1 out of 50 times the string will have length 1.
Of those, 9 out of 10+26 times the string will be a valid vlan.
(from 1 to 9)

1 out of 50 times the string will have length 2.
Of those, 90 out of (10+26)**2 times the string will be a valid vlan.
(from 10 to 99)

1 out of 50 times the string will have length 3.
Of those, 900 out of (10+26)**3 times the string will be a valid vlan.
(from 100 to 999)

1 out of 50 times the string will have length 4.
Of those, 3094 out of (10+26)**4 times the string will be a valid vlan.
(from 1000 to 4094)

So I estimate that the probability that this fails is:

1/50*(9/b+90/b**2+900/b**3+3094/b**4) = 286019/41990400,
where b=10+26, i.e. approximately once every 147 times,
which of course is > 0 and not good enough.

To see how easy this is to happen, just try the program below.

TLDR: Please disable such test, we want tests to always succeed,
not just "most of the time".

Thanks.

#!/usr/bin/python
import random
import 

Processed: Re: [Pkg-utopia-maintainers] Bug#838826: network-manager kills network on upgrade

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo unreproducible
Bug #838826 [network-manager] network-manager kills network on upgrade
Added tag(s) moreinfo and unreproducible.

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