Processed: One more 1.1 transition blocker

[Debian Bug Tracking System]

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

> block 827061 by 843988
Bug #827061 [release.debian.org] transition: openssl
827061 was blocked by: 828292 828410 828259 828355 828519 828610 828366 828325 
828584 828444 835789 828249 828566 828521 827068 828239 828413 828466 828250 
828283 828533 828564 828339 822380 828506 828419 828353 812166 835793 828618 
828567 828560 828536 828343 828415 828607 828379 828315 828611 828256 828494 
843532 828420 828336 828593 828252 835804 828585 828457 828587 828346 828451 
828496 828303 828383 828510 828308 828377 828590 828515 828449 828363 828561 
828529 828262 828374 828425 828330 828368 828486 828399 828317 828268 828538 
828543 828243 828418 828520 835799 828433 828569 828230 828483 828473 828406 
828549 841635 828578 828142 828289 828541 828582 836419 828604 828617 828302 
828242 828350 828400 828360 828586 828296 828439 828329 828598 828314 828331 
828245 828583 828550 828285 828332 828534 828320 828357 828261 828441 835800 
828436 828267 828257 828278 828370 828280 835798 828266 828557 828485 828232 
828345 828380 828595 828253 828275 828555 828414 828297 828592 828385 828517 
828495 828526 828448 828386 828540 828248 828461 828409 828504 828527 828284 
828619 828589 828551 828412 828240 828327 828333 828351 828518 828575 828334 
835790 828482 828293 828311 828464 828597 828393 828468 828509 828522 828321 
828574 828234 837960 828127 828458 828405 828530 828394 828612 828323 828440 
828546 828460 828492 828539 828498 828340 828572 828348 828349 828507 828287 
829465 828471 828407 828605 828391 828559 835794 828306 828478 828442 828228 
828382 828416 828429 828372 828388 828082 808669 828404 828316 828493 828445 
828417 828579 828450 828430 828615 828516 828573 828422 828338 828277 828523 
829452 809271 828359 828447 828580 828279 828241 828364 828376 828459 828271 
828603 828476 827076 828512 828384 828362 828365 828531 835811 828083 828472 
828255 828369 828260 828294 828499 828469 828337 828514 828426 828537 828335 
828305 828602 828599 814600 828264 828491 828596 828309 828547 828503 828500 
828489 828402 828511 828535 828390 828435 828290 828570 828397 828298 828398 
828463 828465 828562 828591 828581 828237 828571 828307 828594 828524 828358 
828269 828508 828609 828501 828251 828373 835549 828552 828601 828347 828568 
828411 828367 835797 828299 828600 828396 828282 828424 828235 828258 828470 
828454 828545 828462 828361 835785 828276 828446 828246 828318 828453 828354 
828387 828423 828431 828616 828577 828525 828300 828273 828620 828467 828274 
828490 828263 828139 828558 828480 828477 828403 828238 828392 828231 828502 
835786 828487 828310 828301 828437 828513 828322 828488 828479 828326 828553 
828254 828304 835796 828378 828286 828344 828341 828576 828544 828233 828554 
828542 828588 828328 828556 828324 828428 828548 828319 828606 828443 828532 
828288 828421 828528 828395 828272 828427 828474 828295 828313 828375 828312 
828432 828565 828291 835585 828452 828342 828270 828244 828455 828352 828356 
828497 828438 828381 828608 828505 828265 828563 828371 828456 828389 828614 
828434 828281 828484 828401 828229 828481
827061 was not blocking any bugs.
Added blocking bug(s) of 827061: 843988
> thanks
Stopping processing here.

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

Processed: Also affects the version in testing

[Debian Bug Tracking System]

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

> found 843988 3:5.36-1
Bug #843988 [stunnel4] stunnel4 segfaults (client mode)
Marked as found in versions stunnel4/3:5.36-1.
> thanks
Stopping processing here.

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

Bug#830984: marked as done (ball: FTBFS: test suite errors)

[Debian Bug Tracking System]

Your message dated Sun, 13 Nov 2016 09:18:53 +
with message-id 
and subject line Bug#830984: fixed in ball 1.4.3~beta1-2
has caused the Debian Bug report #830984,
regarding ball: FTBFS: test suite errors
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.)


-- 
830984: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830984
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ball
Version: 1.4.3~beta1-1
Severity: serious

Your package failed to build on most architectures with test suite errors.

Build logs at

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

Emilio
--- End Message ---
--- Begin Message ---
Source: ball
Source-Version: 1.4.3~beta1-2

We believe that the bug you reported is fixed in the latest version of
ball, 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.
Danny Edel  (supplier of updated ball 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, 11 Nov 2016 12:07:51 +0100
Source: ball
Binary: libball1.4-data libball1.4 libball1.4-dev libballview1.4 
libballview1.4-dev python-ball python-ballview ballview libball1.4-doc
Architecture: source
Version: 1.4.3~beta1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Danny Edel 
Description:
 ballview   - free molecular modeling and molecular graphics tool
 libball1.4 - Biochemical Algorithms Library
 libball1.4-data - Biochemical Algorithms Library (data files)
 libball1.4-dev - Header files for the Biochemical Algorithms Library
 libball1.4-doc - documentation for the BALL library
 libballview1.4 - Biochemical Algorithms Library, VIEW framework
 libballview1.4-dev - Header files for the VIEW part of the Biochemical 
Algorithms Libr
 python-ball - Python bindings for the Biochemical Algorithms Library
 python-ballview - Python bindings for VIEW-parts of the Biochemical Algorithms 
Libr
Closes: 830984 833004
Changes:
 ball (1.4.3~beta1-2) unstable; urgency=medium
 .
   [ Danny Edel ]
   * Team upload
   * Fix FTBFS with GCC-6 and recent boost
 Closes: #830984, #833004
 * Patches backported from upstream git:
   * 2822068 Modify RTTI function isKindOf to take a pointer argument
 (this fixes a segfault in DefaultProcessors_test)
   * 0604808 Fix PoseClustering_test: replace serialized file comparison
   * 7380918 Fix XDRPersistenceManager_test
 * New patch: disable AmberFF_test, which fails nondeterministically
   * Drop previous PoseClustering_test patches (no longer needed)
   * d/watch: fix uversionmangle expression to correctly detect -BETA
 .
   [ Andreas Tille ]
   * Remove useless Breaks in python-ballview and python-ball
   * lintian override for package-name-doesnt-match-sonames
Checksums-Sha1:
 d8efe82926d88dffedbfde16104ef7ee38781c11 2979 ball_1.4.3~beta1-2.dsc
 db15269e215d262407aaae71da5c9dfbeb3355ce 35980 ball_1.4.3~beta1-2.debian.tar.xz
Checksums-Sha256:
 1bd33e0dff2205e807ea41042bdec7c9e5905a4159cc2cf30d63348094666740 2979 
ball_1.4.3~beta1-2.dsc
 83e7b250a599149b01ba4736585d39eda34a54988b815212bf93fb19d5e19481 35980 
ball_1.4.3~beta1-2.debian.tar.xz
Files:
 a744fe72dd168f6157caa9b128ae7b77 2979 science optional ball_1.4.3~beta1-2.dsc
 a4c9605c13f9b8c0f2dc664261c75cf3 35980 science optional 
ball_1.4.3~beta1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIuBAEBCAAYBQJYKC1/ERx0aWxsZUBkZWJpYW4ub3JnAAoJEFeKBJTRxkbRoagP
/1oUJINBbCp+s9JJukWb4aH7RWQR3ZNAFDaZaaTwMOFkA4Q05lUAPT1Akyrnt+RH
kH7vTXTba8aqsyFgawzU0U9Qe8ovBqtuu5Hbb4dVG0EMZmItYnYjqtSJvez+JoQU
jT9nmV5QuyLVkj4l5d65zpHfBaxDMeSwcvblLrFoEVlkb1PkzA/rl5O9CDbo6Ard
WQYWoEjBB2SQyU7jeyU90n4bs8CAb67XzqiNfKDeNeP2FtI5zRPxroNkoLwjmdVE
XKS0faAib9+3dW61T2F4qTOJo5NPJU+ri1Y0KDJIRWFRert0rJgXNLw27SRPMpZt
ZAsISYl5l3aIOM2WhnBc+DTEAukRx6ZdnOiSWnY+w8Uu65ZSZwuhH/0+nJ6lnkr/
pDzveMXHJEem4W5idJMV6buC8/UGTEcG/S3rQLxTkEMNI44km541gInKaIuGOEdV
UvMYnEiqJAh37thgKE6wfXeNStC43Oc4ZN126XgSbQjKj/WWxn7IY5nqU9a5ShuA
ZCRG8Ao6zP1G/2Ojkfv0+brWYQTEnBrzMkdJLYh1KqndZSKHjVaYfGogmL28Jt9B
HKcFelUQbcMOthFpjykArKHG2xCG+PBWyypQGZBgJgwrOcpQlr3U957NCypfiAKm
GO+g0pOXsuRk0jxpB/43wQAj5o20yUNq0Jr

Bug#833004: marked as done (ball: FTBFS: error: 'isnan' was not declared in this scope)

[Debian Bug Tracking System]

Your message dated Sun, 13 Nov 2016 09:18:53 +
with message-id 
and subject line Bug#833004: fixed in ball 1.4.3~beta1-2
has caused the Debian Bug report #833004,
regarding ball: FTBFS: error: 'isnan' was not declared in this scope
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.)


-- 
833004: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833004
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ball
Version: 1.4.3~beta1-1
Severity: serious

Dear maintainer:

This package currently fails to build from source:


/build/ball-1.4.3~beta1/source/MOLMEC/MINIMIZATION/steepestDescent.C:214:46:
  required from here
/build/ball-1.4.3~beta1/include/BALL/MATHS/common.h:175:18: error:
'isnan' was not declared in this scope, and no declarations were
found
by argument-dependent lookup at the point of instantiation
[-fpermissive]
 return (isnan(t) != 0);


I don't know how to fix this but I know that lots of packages suffered
from this "isnan" problem. If you search for any of them which was
already fixed I'm quite confident that a fix could be found easily.


Build logs here:

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

Thanks.
--- End Message ---
--- Begin Message ---
Source: ball
Source-Version: 1.4.3~beta1-2

We believe that the bug you reported is fixed in the latest version of
ball, 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.
Danny Edel  (supplier of updated ball 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, 11 Nov 2016 12:07:51 +0100
Source: ball
Binary: libball1.4-data libball1.4 libball1.4-dev libballview1.4 
libballview1.4-dev python-ball python-ballview ballview libball1.4-doc
Architecture: source
Version: 1.4.3~beta1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Danny Edel 
Description:
 ballview   - free molecular modeling and molecular graphics tool
 libball1.4 - Biochemical Algorithms Library
 libball1.4-data - Biochemical Algorithms Library (data files)
 libball1.4-dev - Header files for the Biochemical Algorithms Library
 libball1.4-doc - documentation for the BALL library
 libballview1.4 - Biochemical Algorithms Library, VIEW framework
 libballview1.4-dev - Header files for the VIEW part of the Biochemical 
Algorithms Libr
 python-ball - Python bindings for the Biochemical Algorithms Library
 python-ballview - Python bindings for VIEW-parts of the Biochemical Algorithms 
Libr
Closes: 830984 833004
Changes:
 ball (1.4.3~beta1-2) unstable; urgency=medium
 .
   [ Danny Edel ]
   * Team upload
   * Fix FTBFS with GCC-6 and recent boost
 Closes: #830984, #833004
 * Patches backported from upstream git:
   * 2822068 Modify RTTI function isKindOf to take a pointer argument
 (this fixes a segfault in DefaultProcessors_test)
   * 0604808 Fix PoseClustering_test: replace serialized file comparison
   * 7380918 Fix XDRPersistenceManager_test
 * New patch: disable AmberFF_test, which fails nondeterministically
   * Drop previous PoseClustering_test patches (no longer needed)
   * d/watch: fix uversionmangle expression to correctly detect -BETA
 .
   [ Andreas Tille ]
   * Remove useless Breaks in python-ballview and python-ball
   * lintian override for package-name-doesnt-match-sonames
Checksums-Sha1:
 d8efe82926d88dffedbfde16104ef7ee38781c11 2979 ball_1.4.3~beta1-2.dsc
 db15269e215d262407aaae71da5c9dfbeb3355ce 35980 ball_1.4.3~beta1-2.debian.tar.xz
Checksums-Sha256:
 1bd33e0dff2205e807ea41042bdec7c9e5905a4159cc2cf30d63348094666740 2979 
ball_1.4.3~beta1-2.dsc
 83e7b250a599149b01ba4736585d39eda34a54988b815212bf93fb19d5e19481 35980 
ball_1.4.3~beta1-2.debian.tar.xz
Files:
 a744fe72dd168f6157caa9b128ae7b77 2979 science optional ball_1.4.3~beta1-2.dsc
 a4c9605c13f9b8c0f2dc664261c75cf3 35980 science optional 
ball_1.4.3~beta1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIuBAEBCAAYBQJYKC1/ERx0aWxsZUBkZWJpYW4ub3JnAAoJEFeKBJTRxkbRoagP
/1oUJINBbCp+s9JJukWb4aH7RWQR3ZNAFDaZaaTwMOFkA4Q05lUAPT1Akyrnt+RH
kH7vTXTba8

Bug#844199: ros-message-generation: FTBFS: INSTALL cannot find "/home/lamby/temp/cdt.20161113092941.NnUukgDcPF.db.ros-message-generation/ros-message-generation-0.4.0/obj-x86_64-linux-gnu/gtest/libgtes

[Chris Lamb]

Source: ros-message-generation
Version: 0.4.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,

ros-message-generation fails to build from source in unstable/amd64:

  […]

 dh_auto_test -O--parallel
make -j9 test ARGS\+=-j9
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20161113092941.NnUukgDcPF.db.ros-message-generation/ros-message-generation-0.4.0/obj-x86_64-linux-gnu'
  Running tests...
  /usr/bin/ctest --force-new-ctest-process -j9
  Test project 
/home/lamby/temp/cdt.20161113092941.NnUukgDcPF.db.ros-message-generation/ros-message-generation-0.4.0/obj-x86_64-linux-gnu
  No tests were found!!!
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20161113092941.NnUukgDcPF.db.ros-message-generation/ros-message-generation-0.4.0/obj-x86_64-linux-gnu'
   fakeroot debian/rules binary
  dh  binary --parallel
 dh_testroot -O--parallel
 dh_prep -O--parallel
 debian/rules override_dh_auto_install-indep
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20161113092941.NnUukgDcPF.db.ros-message-generation/ros-message-generation-0.4.0'
  dh_auto_install --destdir=debian/tmp
make -j9 install 
DESTDIR=/home/lamby/temp/cdt.20161113092941.NnUukgDcPF.db.ros-message-generation/ros-message-generation-0.4.0/debian/tmp
 AM_UPDATE_INFO_DIR=no
  make[2]: Entering directory 
'/home/lamby/temp/cdt.20161113092941.NnUukgDcPF.db.ros-message-generation/ros-message-generation-0.4.0/obj-x86_64-linux-gnu'
  /usr/bin/cmake 
-H/home/lamby/temp/cdt.20161113092941.NnUukgDcPF.db.ros-message-generation/ros-message-generation-0.4.0
 
-B/home/lamby/temp/cdt.20161113092941.NnUukgDcPF.db.ros-message-generation/ros-message-generation-0.4.0/obj-x86_64-linux-gnu
 --check-build-system CMakeFiles/Makefile.cmake 0
  /usr/bin/cmake -E cmake_progress_start 
/home/lamby/temp/cdt.20161113092941.NnUukgDcPF.db.ros-message-generation/ros-message-generation-0.4.0/obj-x86_64-linux-gnu/CMakeFiles
 
/home/lamby/temp/cdt.20161113092941.NnUukgDcPF.db.ros-message-generation/ros-message-generation-0.4.0/obj-x86_64-linux-gnu/CMakeFiles/progress.marks
  make -f CMakeFiles/Makefile2 all
  make[3]: Entering directory 
'/home/lamby/temp/cdt.20161113092941.NnUukgDcPF.db.ros-message-generation/ros-message-generation-0.4.0/obj-x86_64-linux-gnu'
  make[3]: Nothing to be done for 'all'.
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20161113092941.NnUukgDcPF.db.ros-message-generation/ros-message-generation-0.4.0/obj-x86_64-linux-gnu'
  /usr/bin/cmake -E cmake_progress_start 
/home/lamby/temp/cdt.20161113092941.NnUukgDcPF.db.ros-message-generation/ros-message-generation-0.4.0/obj-x86_64-linux-gnu/CMakeFiles
 0
  make -f CMakeFiles/Makefile2 preinstall
  make[3]: Entering directory 
'/home/lamby/temp/cdt.20161113092941.NnUukgDcPF.db.ros-message-generation/ros-message-generation-0.4.0/obj-x86_64-linux-gnu'
  make[3]: Nothing to be done for 'preinstall'.
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20161113092941.NnUukgDcPF.db.ros-message-generation/ros-message-generation-0.4.0/obj-x86_64-linux-gnu'
  Install the project...
  /usr/bin/cmake -P cmake_install.cmake
  -- Install configuration: "None"
  -- Installing: 
/home/lamby/temp/cdt.20161113092941.NnUukgDcPF.db.ros-message-generation/ros-message-generation-0.4.0/debian/tmp/usr/_setup_util.py
  -- Installing: 
/home/lamby/temp/cdt.20161113092941.NnUukgDcPF.db.ros-message-generation/ros-message-generation-0.4.0/debian/tmp/usr/env.sh
  -- Installing: 
/home/lamby/temp/cdt.20161113092941.NnUukgDcPF.db.ros-message-generation/ros-message-generation-0.4.0/debian/tmp/usr/setup.bash
  -- Installing: 
/home/lamby/temp/cdt.20161113092941.NnUukgDcPF.db.ros-message-generation/ros-message-generation-0.4.0/debian/tmp/usr/setup.sh
  -- Installing: 
/home/lamby/temp/cdt.20161113092941.NnUukgDcPF.db.ros-message-generation/ros-message-generation-0.4.0/debian/tmp/usr/setup.zsh
  -- Installing: 
/home/lamby/temp/cdt.20161113092941.NnUukgDcPF.db.ros-message-generation/ros-message-generation-0.4.0/debian/tmp/usr/.rosinstall
  -- Installing: 
/home/lamby/temp/cdt.20161113092941.NnUukgDcPF.db.ros-message-generation/ros-message-generation-0.4.0/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig/message_generation.pc
  -- Installing: 
/home/lamby/temp/cdt.20161113092941.NnUukgDcPF.db.ros-message-generation/ros-message-generation-0.4.0/debian/tmp/usr/share/message_generation/cmake/message_generationConfig.cmake
  -- Installing: 
/home/lamby/temp/cdt.20161113092941.NnUukgDcPF.db.ros-message-generation/ros-message-generation-0.4.0/debian/tmp/usr/share/message_generation/cmake/message_generationConfig-version.cmake
  -- Installing: 
/home/lamby/temp/cdt.20161113092941.NnUukgDcPF.db.ros-message-generation/ros-message-generation-0.4.0/debian/tmp/usr/share/message_generation/package.xml
  CMake Error at gtest/cmake_install.cmake:42 (file):
file INSTALL canno

Bug#844198: freeciv: FTBFS: configure: error: selected client 'qt' cannot be built: Missing Qt5 development files

[Chris Lamb]

Source: freeciv
Version: 2.5.5-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,

freeciv fails to build from source in unstable/amd64:

  […]

  MODINST_GTK2_FALSE=''
  MODINST_GTK2_TRUE=''
  MODINST_GTK3_FALSE=''
  MODINST_GTK3_TRUE=''
  MODINST_QT_FALSE=''
  MODINST_QT_TRUE=''
  MODINST_TRUE=''
  MSGFMT='/usr/bin/msgfmt'
  MSGFMT_OPTS='-c'
  MYSQL_CONFIG=''
  MYSQL_VERSION=''
  NETWORK_CAPSTRING_MANDATORY='+Freeciv-2.5-network'
  NETWORK_CAPSTRING_OPTIONAL='nationset_change tech_cost split_reports 
extended_move_rate illness_ranges nonnatdef'
  NM='/usr/bin/nm -B'
  NMEDIT=''
  OBJDUMP='objdump'
  OBJEXT='o'
  OTOOL64=''
  OTOOL=''
  PACKAGE='freeciv'
  PACKAGE_BUGREPORT='http://gna.org/projects/freeciv/'
  PACKAGE_NAME='Freeciv'
  PACKAGE_STRING='Freeciv 2.5.5'
  PACKAGE_TARNAME='freeciv'
  PACKAGE_URL=''
  PACKAGE_VERSION='2.5.5'
  PATH_SEPARATOR=':'
  PG_CONFIG=''
  PKG_CONFIG='/usr/bin/pkg-config'
  PKG_CONFIG_LIBDIR=''
  PKG_CONFIG_PATH=''
  PNG_CFLAGS=''
  PNG_LIBS=''
  POFILES=' ar.po bg.po cs.po ca.po da.po de.po el.po en_GB.po eo.po es.po 
et.po fa.po fi.po fr.po ga.po gd.po he.po hu.po id.po it.po ja.po ko.po lt.po 
nl.po nb.po pl.po pt.po pt_BR.po ro.po ru.po sr.po sv.po tr.po uk.po zh_CN.po 
zh_TW.po'
  POSTGRESQL_VERSION=''
  POSUB=''
  PO_IN_DATADIR_FALSE=''
  PO_IN_DATADIR_TRUE=''
  QTPATHS=''
  RANLIB='ranlib'
  REPLACE_CALLOC=''
  REPLACE_CANONICALIZE_FILE_NAME=''
  REPLACE_MALLOC=''
  REPLACE_MBTOWC=''
  REPLACE_MKSTEMP=''
  REPLACE_PTSNAME_R=''
  REPLACE_PUTENV=''
  REPLACE_REALLOC=''
  REPLACE_REALPATH=''
  REPLACE_SETENV=''
  REPLACE_STRTOD=''
  REPLACE_UNSETENV=''
  REPLACE_WCTOMB=''
  SDL2MIXER_CFLAGS=''
  SDL2MIXER_LIBS=''
  SDL2_CFLAGS=''
  SDL2_CONFIG=''
  SDL2_LIBS=''
  SDLMIXER_CFLAGS='-D_GNU_SOURCE=1 -D_REENTRANT -I/usr/include/SDL'
  SDLMIXER_LIBS='-lSDL_mixer -lSDL'
  SDL_CFLAGS='-I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT'
  SDL_CONFIG='/usr/bin/sdl-config'
  SDL_LIBS='-L/usr/lib/x86_64-linux-gnu -lSDL'
  SED='/bin/sed'
  SERVER_FALSE='#'
  SERVER_LIBS=''
  SERVER_TRUE=''
  SET_MAKE=''
  SHELL='/bin/bash'
  SOUND_CFLAGS=' -D_GNU_SOURCE=1 -D_REENTRANT -I/usr/include/SDL'
  SOUND_LIBS=' -lSDL_mixer -lSDL'
  SQLITE3_VERSION='3.15.1'
  SRV_LIB_LIBS=''
  STRIP='strip'
  SVNREV_FALSE=''
  SVNREV_TRUE='#'
  SYS_LUA_FALSE=''
  SYS_LUA_TRUE=''
  TOLUA=''
  TOLUA_CFLAGS=''
  TOLUA_LIBS=''
  UNAME='uname'
  USE_NLS='yes'
  UTILITY_CFLAGS=' '
  UTILITY_LIBS=' -lcurl -lz -lbz2 -llzma'
  VERSION='2.5.5'
  VERSION_LABEL=''
  VERSION_WITHOUT_LABEL='2.5.5'
  WAND_CFLAGS=''
  WAND_LIBS=''
  WIKI_URL='http://www.freeciv.org/'
  WINDRES=''
  XGETTEXT='/usr/bin/xgettext'
  XMKMF=''
  X_CFLAGS=''
  X_EXTRA_LIBS=''
  X_LIBS=''
  X_PRE_LIBS=''
  ac_ct_AR='ar'
  ac_ct_CC='gcc'
  ac_ct_CXX='g++'
  ac_ct_DUMPBIN=''
  aimoduledir='${prefix}/lib/x86_64-linux-gnu/fcai'
  am__EXEEXT_FALSE=''
  am__EXEEXT_TRUE=''
  am__fastdepCC_FALSE=''
  am__fastdepCC_TRUE='#'
  am__fastdepCXX_FALSE=''
  am__fastdepCXX_TRUE='#'
  am__include='include'
  am__isrc=''
  am__leading_dot='.'
  am__nodep=''
  am__quote=''
  am__tar='$${TAR-tar} chof - "$$tardir"'
  am__untar='$${TAR-tar} xf -'
  bindir='${prefix}/games'
  build='x86_64-pc-linux-gnu'
  build_alias='x86_64-linux-gnu'
  build_cpu='x86_64'
  build_os='linux-gnu'
  build_vendor='pc'
  datadir='${prefix}/share/games'
  datarootdir='${prefix}/share'
  docdir='${datarootdir}/doc/${PACKAGE_TARNAME}'
  dvidir='${docdir}'
  exec_prefix='NONE'
  ggz_config=''
  ggz_gtk_includes=''
  ggz_gtk_libraries=''
  ggzdatadir=''
  ggzdconfdir=''
  ggzddatadir=''
  ggzdexecmoddir=''
  ggzdexecmodpath=''
  ggzdmod_includes=''
  ggzdmod_libraries=''
  ggzexecmoddir=''
  ggzmod_includes=''
  ggzmod_libraries=''
  ggzmoduleconfdir=''
  gui_gtk2_cflags='-pthread -I/usr/include/gtk-2.0 
-I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ 
-I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 
-I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libpng16 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/pango-1.0 
-I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/freetype2'
  gui_gtk2_ldflags=''
  gui_gtk2_libs='-lgtk-x11-2.0 -lgdk-x11-2.0 -lpangocairo-1.0 -latk-1.0 -lcairo 
-lgdk_pixbuf-2.0 -lgio-2.0 -lpangoft2-1.0 -lpango-1.0 -lgobject-2.0 -lglib-2.0 
-lfontconfig -lfreetype'
  gui_gtk3_cflags='-pthread -I/usr/include/gtk-3.0 
-I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo 
-I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/free

Bug#823004: gplaycli: sensitive information in config file

[Matlink]

Another solution would be to tell gplaycli to fetch the credentials from
a server. In this case, when the credentials are changed, I just have to
change this file on the server and every instance of gplaycli will fetch
this file and have the new credentials.

Pros:

  * no need to update gplaycli when credentials change
  * transparent for users

Cons:

  * gplaycli is dependent to a server
  * the server is aware of every gplaycli instances (privacy issues)



Le 09/11/2016 à 09:53, matlink a écrit :
> I understand. We're looking for a solution that won't remove them and
> prevent anyone except me to change the password.
>
>
> Le 09/11/2016 à 09:43, Paul Wise a écrit :
>> On Wed, 2016-11-09 at 08:20 +0100, Matlink wrote:
>>
>>> there is a potential big issue with providing default credentials
>> The default shared credentials are the main advantage of this package.
>> I wouldn't have any reason to use it without them.
>>

-- 
Matlink - Sysadmin matlink.fr
Sortez couverts, chiffrez vos mails : https://café-vie-privée.fr/
XMPP/Jabber : matl...@matlink.fr
Clé publique PGP : 0x186BB3CA
Empreinte Off-the-record : 572174BF 6983EA74 91417CA7 705ED899 DE9D05B2

Processed: severity of 828613 is serious, block 827061 with 828613

[Debian Bug Tracking System]

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

> # back to serious since switching back Build-Depends to libssl-dev
> severity 828613 serious
Bug #828613 {Done: Salvatore Bonaccorso } [src:yapet] yapet: 
FTBFS with openssl 1.1.0
Severity set to 'serious' from 'important'
> # add back that 828613 blocks 827061, but solved with 1.0-9
> block 827061 with 828613
Bug #827061 [release.debian.org] transition: openssl
827061 was blocked by: 828233 828275 828446 828614 828314 828245 828509 828351 
828448 828395 828333 828528 828515 828349 828371 828618 828358 828273 828320 
835549 828387 828462 835798 828312 828458 828406 828286 828300 828338 828403 
828252 828608 828304 828361 828328 828548 828552 828268 828364 828502 828527 
828540 828465 828573 828436 828544 827068 828467 835790 828444 828437 828347 
828297 828271 829452 828370 828449 828580 808669 836419 828355 828428 828532 
828353 828263 828596 828352 828230 828432 828536 828276 828576 828570 828517 
828295 828454 828563 828616 828348 828443 828326 828442 828337 828600 828315 
828493 828398 828322 828294 828435 828404 828254 828335 828330 828412 828248 
828283 828357 828139 828336 828391 828256 828464 828228 828423 828394 828584 
828541 828429 828617 828495 828589 828500 828474 809271 828417 828468 828483 
828538 828293 828282 828542 828386 828375 828592 828490 835785 837960 828413 
828484 828583 828365 828345 828453 828597 835585 828579 828572 835800 828481 
828620 828422 828251 828287 828127 828516 828605 828441 828555 828240 828520 
828456 828262 828601 828382 828410 828546 828362 828402 828507 828514 828407 
828588 828258 828419 828253 828260 828478 828284 828612 841635 828609 828492 
828411 828331 835797 828296 828299 828142 828607 828519 827076 828257 828261 
835796 828229 828235 828389 828303 828420 828416 828393 828332 828529 835789 
828342 828504 828359 828575 828530 828318 828264 828494 828427 828434 828566 
828340 828307 828480 828485 828477 828350 828421 828497 828259 828381 828405 
828491 828270 828334 828479 828512 828471 828374 828604 828288 828452 828556 
828553 828313 828390 828250 828533 828611 828310 828488 828619 828489 828380 
828554 843988 828585 828602 828267 828549 828508 828534 828424 828450 828603 
828461 828615 828329 828593 828558 828526 828083 828301 828344 828366 814600 
828292 828401 828265 828327 828414 828232 828269 828409 828356 828373 828319 
828521 828473 828459 828274 828487 828599 828396 828433 828343 829465 828280 
828590 828418 828243 828379 828376 828457 828571 835811 828388 828321 843532 
828586 828367 828237 828564 828242 828438 828255 828506 828562 828496 828463 
828451 828565 828244 828535 828383 828501 828525 828354 828543 828547 828486 
828476 828545 828385 828550 828325 828568 828503 828399 828397 828569 828523 
822380 828378 828482 828581 828598 828560 828363 835786 828346 828439 835804 
828291 828231 828524 828317 828561 828582 812166 828595 828285 828531 828400 
828339 828425 828466 828306 828238 828369 828234 828505 828498 828392 828308 
828577 828469 828455 828316 828377 835799 828567 828499 828606 828591 828309 
828249 828430 828445 828426 828278 828559 828384 828305 828311 828511 828578 
828266 828360 828281 828472 828298 828302 828447 828431 828239 828574 828440 
828513 828277 828246 828372 828241 828290 828272 828324 828341 828415 828610 
828082 828587 828279 828594 828289 828537 828368 828470 828518 828522 828539 
828551 828557 835794 828510 828323 828460 835793
827061 was not blocking any bugs.
Added blocking bug(s) of 827061: 828613
> thanks
Stopping processing here.

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

Bug#828378: closing 828378

[Thijs Kinkhorst]

close 828378 1.1-2
thanks

Processed: closing 828378

[Debian Bug Tracking System]

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

> close 828378 1.1-2
Bug #828378 [src:libapache2-mod-auth-cas] libapache2-mod-auth-cas: FTBFS with 
openssl 1.1.0
Marked as fixed in versions libapache2-mod-auth-cas/1.1-2.
Bug #828378 [src:libapache2-mod-auth-cas] libapache2-mod-auth-cas: FTBFS with 
openssl 1.1.0
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#844201: debsources: updater broken by recent (Sources.gz removal, maybe sha1 removal) dak changes

[Stefano Zacchiroli]

Package: qa.debian.org
Severity: serious
User: qa.debian@packages.debian.org
Usertags: debsources

Context is:

  https://lists.debian.org/debian-devel-announce/2016/11/msg5.html

Here are some relevant entries from debsources.log:

  Use of uninitialized value $sha1 in string eq at /usr/bin/debmirror line 1639.
  Use of uninitialized value $sha1 in string eq at /usr/bin/debmirror line 1639.
  Use of uninitialized value $sha1 in string eq at /usr/bin/debmirror line 1639.
  Use of uninitialized value $sha1 in string eq at /usr/bin/debmirror line 1639.
  Use of uninitialized value $sha1 in string eq at /usr/bin/debmirror line 1639.
  Use of uninitialized value $sha1 in string eq at /usr/bin/debmirror line 1639.
  Use of uninitialized value $sha1 in string eq at /usr/bin/debmirror line 1639.
  Use of uninitialized value $sha1 in string eq at /usr/bin/debmirror line 1639.
  Use of uninitialized value $sha1 in string eq at /usr/bin/debmirror line 1639.
  Use of uninitialized value $sha1 in string eq at /usr/bin/debmirror line 1639.
  Use of uninitialized value $sha1 in string eq at /usr/bin/debmirror line 1639.
  Use of uninitialized value $sha1 in string eq at /usr/bin/debmirror line 1639.
  Use of uninitialized value $sha1 in string eq at /usr/bin/debmirror line 1639.
  Use of uninitialized value $sha1 in string eq at /usr/bin/debmirror line 1639.
  Use of uninitialized value $sha1 in string eq at /usr/bin/debmirror line 1639.
  Use of uninitialized value $sha1 in string eq at /usr/bin/debmirror line 1639.
  Use of uninitialized value $sha1 in string eq at /usr/bin/debmirror line 1639.
  Use of uninitialized value $sha1 in string eq at /usr/bin/debmirror line 1639.
  Use of uninitialized value $sha1 in string eq at /usr/bin/debmirror line 1639.
  Use of uninitialized value $sha1 in string eq at /usr/bin/debmirror line 1639.
  Errors:
   Download of dists/squeeze-lts/Release failed
   Ignoring failed Release files
   Ignoring missing Release file for dists/sid/main/source/Sources.gz
   Ignoring missing Release file for dists/sid/contrib/source/Sources.gz
   Ignoring missing Release file for dists/sid/non-free/source/Sources.gz
   Ignoring missing Release file for dists/squeeze-lts/main/source/Sources.gz
   Ignoring missing Release file for dists/squeeze-lts/contrib/source/Sources.gz
   Ignoring missing Release file for 
dists/squeeze-lts/non-free/source/Sources.gz
   Ignoring missing Release file for dists/experimental/main/source/Sources.gz
   Ignoring missing Release file for 
dists/experimental/contrib/source/Sources.gz
   Ignoring missing Release file for 
dists/experimental/non-free/source/Sources.gz
  /srv/debsources/bin/debsources-main: I: debsources-update...

Cheers.

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

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

Processed: rawtherapee unusable

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #841498 [rawtherapee] rawtherapee: UI elements are displayed too big
Bug #842424 [rawtherapee] rawtherapee: UI is too big. Tone curves are  totally 
unusable.
Severity set to 'grave' from 'normal'
Severity set to 'grave' from 'normal'

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

Bug#844142: norwegian: FTBFS: rm: cannot remove 'munch[123].tmp': No such file or directory

[Lucas Nussbaum]

On 12/11/16 at 22:49 +0100, Petter Reinholdtsen wrote:
> [Lucas Nussbaum]
> > During a rebuild of all packages in sid, your package failed to build on
> > amd64.
> 
> I believe this package can not be built in parallell.  Could this be the
> trigger for this build problem?

Maybe. But it builds in parallel on a machine with less cores. Strange.

Note that there's no obligation to support building in parallel: if it's
broken, you could just remove support for it.
 
Lucas

Processed: Bug#809119 tagged as pending

[Debian Bug Tracking System]

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

> tag 809119 pending
Bug #809119 [src:libvsqlitepp] libvsqlitepp: FTBFS when built with 
dpkg-buildpackage -A (invalid package/library name)
Added tag(s) pending.
> --
Stopping processing here.

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

Bug#809119: tagged as pending

[Dmitry Smirnov]

tag 809119 pending
--

We believe that the bug #809119 you reported has been fixed in the Git
repository. You can see the commit message below and/or inspect the
commit contents at:


http://anonscm.debian.org/cgit/collab-maint/libvsqlitepp.git/diff/?id=4c658ee

(This message was generated automatically by
 'git-post-receive-tag-pending-commitmsg' hook).
---
commit 4c658ee
Author: Dmitry Smirnov 
Date:   Sun Nov 13 10:38:37 2016

rules: override_dh_install --> override_dh_install-arch (Closes: #809119)

Bug#844205: aufs-dkms: I can't load the kernel module after upgrade from Jessie to Stretch.

[Leo]

Package: aufs-dkms
Version: 4.8+20161010-1
Severity: critical
Tags: d-i
Justification: causes serious data loss

Dear Maintainer,

   * What led up to the situation?

I wanted to upgrade from Jessie to Stretch.

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

I run apt-get dist-upgrade. Everything was working (or at least, no
critical error appeared).
After that, docker stop to work because the aufs kernel module was not
found.
I tried to install the aufs packages but the kernel can't find it (maybe
because my kernel is 4.7?).

   * What was the outcome of this action?

The only way to have docker working is to delete all the old
images/containers.
It means that I'm losing all my data inside.

   * What outcome did you expect instead?

To load the module correctly and have docker working again also with
images/containers stored
with aufs.
Or, at least to be able to migrate my old images/containers from aufs to
another storage service.



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

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

Versions of packages aufs-dkms depends on:
ii  dkms  2.3-1

Versions of packages aufs-dkms recommends:
ii  aufs-tools  1:4.1+20161010-1

Versions of packages aufs-dkms suggests:
ii  aufs-dev  4.8+20161010-1

-- no debconf information

Processed: tagging 840786

[Debian Bug Tracking System]

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

> tags 840786 + pending
Bug #840786 [src:mysql-workbench] mysql-workbench: Change libmysqlclient-dev 
build dependency to default-libmysqlclient-dev
Bug #841584 [src:mysql-workbench] mysql-workbench: FTBFS: build-dependency not 
installable: libmysqlclient-dev
Added tag(s) pending.
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: tagging 843887

[Debian Bug Tracking System]

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

> tags 843887 + pending
Bug #843887 [mysql-workbench] mysql-workbench: cannot install it: missing 
dependency gdal-abi-2-1-1
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: tagging 843457

[Debian Bug Tracking System]

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

> tags 843457 + pending
Bug #843457 [src:mysql-workbench] mysql-workbench: Dependency gdal-abi-2-1-1 no 
longer in repo
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: tagging 839356

[Debian Bug Tracking System]

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

> tags 839356 + pending
Bug #839356 [src:mysql-workbench] mysql-workbench: FTBFS: 
lf_popover.cpp:383:13: error: no match for 'operator!=' (operand types are 
'Glib::RefPtr' and 'int')
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#809119: marked as done (libvsqlitepp: FTBFS when built with dpkg-buildpackage -A (invalid package/library name))

[Debian Bug Tracking System]

Your message dated Sun, 13 Nov 2016 11:05:17 +
with message-id 
and subject line Bug#809119: fixed in libvsqlitepp 0.3.13-4
has caused the Debian Bug report #809119,
regarding libvsqlitepp: FTBFS when built with dpkg-buildpackage -A (invalid 
package/library name)
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.)


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

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --parallel --with autoreconf
   dh_testdir -i -O--parallel
   dh_autoreconf -i -O--parallel
libtoolize: putting auxiliary files in `.'.
libtoolize: copying file `./ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'.
libtoolize: copying file `m4/libtool.m4'
libtoolize: copying file `m4/ltoptions.m4'
libtoolize: copying file `m4/ltsugar.m4'
libtoolize: copying file `m4/ltversion.m4'
libtoolize: copying file `m4/lt~obsolete.m4'

[... snipped ...]

   debian/rules override_dh_auto_install
make[1]: Entering directory '/<>'
dh_auto_install --destdir=/<>/debian/tmp
make -j1 install DESTDIR=/<>/debian/tmp 
AM_UPDATE_INFO_DIR=no
make[2]: Entering directory '/<>'
Making install in include
make[3]: Entering directory '/<>/include'
make[4]: Entering directory '/<>/include'
make[4]: Nothing to be done for 'install-exec-am'.
 /bin/mkdir -p '/<>/debian/tmp/usr/include'
 /bin/mkdir -p '/<>/debian/tmp/usr/include/sqlite/ext'
 /usr/bin/install -c -m 644  sqlite/ext/variant.hpp 
'/<>/debian/tmp/usr/include/sqlite/ext'
 /bin/mkdir -p '/<>/debian/tmp/usr/include/sqlite'
 /usr/bin/install -c -m 644  sqlite/command.hpp sqlite/database_exception.hpp 
sqlite/query.hpp sqlite/transaction.hpp sqlite/connection.hpp 
sqlite/execute.hpp sqlite/result.hpp sqlite/view.hpp 
'/<>/debian/tmp/usr/include/sqlite'
make[4]: Leaving directory '/<>/include'
make[3]: Leaving directory '/<>/include'
make[3]: Entering directory '/<>'
make[4]: Entering directory '/<>'
 /bin/mkdir -p '/<>/debian/tmp/usr/lib/x86_64-linux-gnu'
 /bin/bash ./libtool   --mode=install /usr/bin/install -c   libvsqlitepp.la 
'/<>/debian/tmp/usr/lib/x86_64-linux-gnu'
libtool: install: /usr/bin/install -c .libs/libvsqlitepp.so.3.0.0 
/<>/debian/tmp/usr/lib/x86_64-linux-gnu/libvsqlitepp.so.3.0.0
libtool: install: (cd /<>/debian/tmp/usr/lib/x86_64-linux-gnu && { 
ln -s -f libvsqlitepp.so.3.0.0 libvsqlitepp.so.3 || { rm -f libvsqlitepp.so.3 
&& ln -s libvsqlitepp.so.3.0.0 libvsqlitepp.so.3; }; })
libtool: install: (cd /<>/debian/tmp/usr/lib/x86_64-linux-gnu && { 
ln -s -f libvsqlitepp.so.3.0.0 libvsqlitepp.so || { rm -f libvsqlitepp.so && ln 
-s libvsqlitepp.so.3.0.0 libvsqlitepp.so; }; })
libtool: install: /usr/bin/install -c .libs/libvsqlitepp.lai 
/<>/debian/tmp/usr/lib/x86_64-linux-gnu/libvsqlitepp.la
libtool: install: /usr/bin/install -c .libs/libvsqlitepp.a 
/<>/debian/tmp/usr/lib/x86_64-linux-gnu/libvsqlitepp.a
libtool: install: chmod 644 
/<>/debian/tmp/usr/lib/x86_64-linux-gnu/libvsqlitepp.a
libtool: install: ranlib 
/<>/debian/tmp/usr/lib/x86_64-linux-gnu/libvsqlitepp.a
libtool: install: warning: remember to run `libtool --finish 
/usr/lib/x86_64-linux-gnu'
make[4]: Nothing to be done for 'install-data-am'.
make[4]: Leaving directory '/<>'
make[3]: Leaving directory '/<>'
make[2]: Leaving directory '/<>'
make[1]: Leaving directory '/<>'
   debian/rules override_dh_install
make[1]: Entering directory '/<>'
I: library-name=libvsqlitepp3v5
debian/rules:40: *** invalid package/library name...  Stop.
make[1]: Leaving directory '/<>'
debian/rules:25: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep gave error exit 
status 2


Sorry not to have a fix, as I am reporting many bugs similar to
this one. The common hints are:

* If the only architecture-independent packages are dummy transitional
ones and they were released with jessie, the easy fix is to drop them
now.

* When using "dh", it is allowed to use (independently)
optional targets override_dh_foo-arch and override_dh_foo-indep
(for several values of "foo").


Once that both "dpkg-buildpackage -A" and "dpkg-buildpackage 

Processed: tagging 841584

[Debian Bug Tracking System]

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

> tags 841584 + pending
Bug #841584 [src:mysql-workbench] mysql-workbench: FTBFS: build-dependency not 
installable: libmysqlclient-dev
Bug #840786 [src:mysql-workbench] mysql-workbench: Change libmysqlclient-dev 
build dependency to default-libmysqlclient-dev
Ignoring request to alter tags of bug #841584 to the same tags previously set
Ignoring request to alter tags of bug #840786 to the same tags previously set
> thanks
Stopping processing here.

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

Processed: Bug#839356 tagged as pending

[Debian Bug Tracking System]

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

> tag 839356 pending
Bug #839356 [src:mysql-workbench] mysql-workbench: FTBFS: 
lf_popover.cpp:383:13: error: no match for 'operator!=' (operand types are 
'Glib::RefPtr' and 'int')
Ignoring request to alter tags of bug #839356 to the same tags previously set
> --
Stopping processing here.

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

Bug#839356: tagged as pending

[Dmitry Smirnov]

tag 839356 pending
--

We believe that the bug #839356 you reported has been fixed in the Git
repository. You can see the commit message below and/or inspect the
commit contents at:


http://anonscm.debian.org/cgit/collab-maint/mysql-workbench.git/diff/?id=2d345f9

(This message was generated automatically by
 'git-post-receive-tag-pending-commitmsg' hook).
---
commit 2d345f9
Author: Dmitry Smirnov 
Date:   Sun Nov 13 11:08:28 2016

New "gtk.patch" to fix FTBFS (Closes: #839356)

Processed: Re: ros-message-generation: FTBFS: INSTALL cannot find "/home/lamby/temp/cdt.20161113092941.NnUukgDcPF.db.ros-message-generation/ros-message-generation-0.4.0/obj-x86_64-linux-gnu/gtest/libg

[Debian Bug Tracking System]

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

> retitle 844199 ros-message-generation: FTBFS: INSTALL cannot find 
> "ros-message-generation-0.4.0/obj-x86_64-linux-gnu/gtest/libgtest.so
Bug #844199 [src:ros-message-generation] ros-message-generation: FTBFS: INSTALL 
cannot find 
"/home/lamby/temp/cdt.20161113092941.NnUukgDcPF.db.ros-message-generation/ros-message-generation-0.4.0/obj-x86_64-linux-gnu/gtest/libgtest.so
Changed Bug title to 'ros-message-generation: FTBFS: INSTALL cannot find 
"ros-message-generation-0.4.0/obj-x86_64-linux-gnu/gtest/libgtest.so' from 
'ros-message-generation: FTBFS: INSTALL cannot find 
"/home/lamby/temp/cdt.20161113092941.NnUukgDcPF.db.ros-message-generation/ros-message-generation-0.4.0/obj-x86_64-linux-gnu/gtest/libgtest.so'.
> thanks
Stopping processing here.

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

Bug#841050: marked as done (Security fixes from the October 2016 CPU)

[Debian Bug Tracking System]

Your message dated Sun, 13 Nov 2016 11:17:20 +
with message-id 
and subject line Bug#841050: fixed in mysql-5.5 5.5.53-0+deb8u1
has caused the Debian Bug report #841050,
regarding Security fixes from the October 2016 CPU
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.)


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

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

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


The CVE numbers will be available when the CPU is released.

Regards,

Norvald H. Ryeng

[1]  
http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881722.html
--- End Message ---
--- Begin Message ---
Source: mysql-5.5
Source-Version: 5.5.53-0+deb8u1

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated mysql-5.5 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, 17 Oct 2016 10:49:23 +0200
Source: mysql-5.5
Binary: libmysqlclient18 libmysqld-pic libmysqld-dev libmysqlclient-dev 
mysql-common mysql-client-5.5 mysql-server-core-5.5 mysql-server-5.5 
mysql-server mysql-client mysql-testsuite mysql-testsuite-5.5 mysql-source-5.5
Architecture: all source
Version: 5.5.53-0+deb8u1
Distribution: jessie-security
Urgency: high
Maintainer: Debian MySQL Maintainers 
Changed-By: Salvatore Bonaccorso 
Closes: 841050
Description: 
 libmysqlclient-dev - MySQL database development files
 libmysqlclient18 - MySQL database client library
 libmysqld-dev - MySQL embedded database development files
 libmysqld-pic - PIC version of MySQL embedded server development files
 mysql-client - MySQL database client (metapackage depending on the latest 
versio
 mysql-client-5.5 - MySQL database client binaries
 mysql-common - MySQL database common files, e.g. /etc/mysql/my.cnf
 mysql-server - MySQL database server (metapackage depending on the latest 
versio
 mysql-server-5.5 - MySQL database server binaries and system database setup
 mysql-server-core-5.5 - MySQL database server binaries
 mysql-source-5.5 - MySQL source
 mysql-testsuite - MySQL testsuite
 mysql-testsuite-5.5 - MySQL testsuite
Changes:
 mysql-5.5 (5.5.53-0+deb8u1) jessie-security; urgency=high
 .
   * Imported upstream version 5.5.53 to fix security issues:
 - 
http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881722.html
 - CVE-2016-7440 CVE-2016-5584
 (Closes: #841050)
   * Packaging will now create /var/lib/mysql-files, as server will now by
 default restrict all import/export operations to this directory. This
 can be changed using the secure-file-priv config option.
Checksums-Sha1: 
 f5751f71c8868b02dc400331cf7da372b5f53185 3233 mysql-5.5_5.5.53-0+deb8u1.dsc
 ecebbb96dd6663eb35278d112cb06a855c3c1537 21035716 mysql-5.5_5.5.53.orig.tar.gz
 877c712e9caa451373a3bbda72e95f702da4d3df 232272 
mysql-5.5_5.5.53-0+deb8u1.debian.tar.xz
 baea185e7c3e93e3085054e7889947fc17abe189 75532 
mysql-common_5.5.53-0+deb8u1_all.deb
 8753cb814803d6da67fb48f3c5ea0ccbbb001c62 73782 
mysql-server_5.5.53-0+deb8u1_all.deb
 e4133739deb21cd764b2c6d0a1676bf066f8a75a 73652 
mysql-client_5.5.53-0+deb8u1_all.deb
 7b8d383370d02fcebc91fbf7a7d6642dc9474411 73616 
mysql-testsuite_5.5.53-0+deb8u1_all.deb
Checksums-Sha256: 
 631ee00029cf7403c5b569ec599f97a6e0378af75441f5b6e16030f2b18d9ca5 3233 
mysql-5.5_5.5.53-0+deb8u1.dsc
 a7a86dd42524e698c9dd8dab2520e6e75377cde077ed71eaf5a3b5a3d1f7d6ea 21035716 
mysql-5.5_5.5.53.orig.tar.gz
 063d2601b47dc24a3e86acadd1797abfbd09c22ecdbebfe8bff6862d3f0702b0 232272 
mysql-5.5_5.5.53-0+deb8u1.debian.tar.xz
 327fc2bcbf53fed05bff4a496c7cf89558bb4ab74a4303c1b03acf9ebd4be78e 75532 
mysql-common_5.5.53-0+deb8u1_all.deb
 aab543be65e89b07a37c52c32d40779c7a5c98ebb453db3a3

Bug#841585: marked as done (mysql-connector-c++: FTBFS: c++: error: unrecognized command line option '-map=/build/mysql-5.7-ClWLeg/mysql-5.7-5.7.15=.')

[Debian Bug Tracking System]

Your message dated Sun, 13 Nov 2016 11:20:57 +
with message-id 
and subject line Bug#841585: fixed in mysql-connector-c++ 1.1.7-3
has caused the Debian Bug report #841585,
regarding mysql-connector-c++: FTBFS: c++: error: unrecognized command line 
option '-map=/build/mysql-5.7-ClWLeg/mysql-5.7-5.7.15=.'
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.)


-- 
841585: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841585
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mysql-connector-c++
Version: 1.1.4+really1.1.3-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161021 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[3]: Entering directory 
> '/build/mysql-connector-c++-XqlzJw/mysql-connector-c++-1.1.4+really1.1.3/builddir'
> [  2%] Building CXX object 
> driver/CMakeFiles/mysqlcppconn.dir/mysql_art_resultset.cpp.o
> cd 
> /build/mysql-connector-c++-XqlzJw/mysql-connector-c++-1.1.4+really1.1.3/builddir/driver
>  && /usr/bin/c++   -DCPPCONN_SO_BUILD=\"\" 
> -DDYNLOAD_MYSQL_LIB=\"MYSQLCPPCONN_DYNLOAD_MYSQL_LIB-NOTFOUND\" 
> -Dmysqlcppconn_EXPORTS -I/usr/include/mysql 
> -I/build/mysql-connector-c++-XqlzJw/mysql-connector-c++-1.1.4+really1.1.3/builddir
>  
> -I/build/mysql-connector-c++-XqlzJw/mysql-connector-c++-1.1.4+really1.1.3/builddir/cppconn
>  
> -I/build/mysql-connector-c++-XqlzJw/mysql-connector-c++-1.1.4+really1.1.3/builddir/driver/nativeapi
>   -DLIBMYSQLCLIENT_SONAME=\"/usr/lib/x86_64-linux-gnu/libmysqlclient_r_r.so\" 
>   -fPIC   -Wall -fPIC -Woverloaded-virtual   
> -DLIBMYSQLCLIENT_SONAME=\"/usr/lib/x86_64-linux-gnu/libmysqlclient_r_r.so\"  
> -I/usr/include/mysql 
> -fdebug-prefix-map=/build/mysql-5.7-ClWLeg/mysql-5.7-5.7.15=. -fabi-version=2 
> -fno-omit-frame-pointer -o 
> CMakeFiles/mysqlcppconn.dir/mysql_art_resultset.cpp.o -c 
> /build/mysql-connector-c++-XqlzJw/mysql-connector-c++-1.1.4+really1.1.3/builddir/driver/mysql_art_resultset.cpp
> [  4%] Building CXX object 
> driver/CMakeFiles/mysqlcppconn.dir/mysql_art_rset_metadata.cpp.o
> cd 
> /build/mysql-connector-c++-XqlzJw/mysql-connector-c++-1.1.4+really1.1.3/builddir/driver
>  && /usr/bin/c++   -DCPPCONN_SO_BUILD=\"\" 
> -DDYNLOAD_MYSQL_LIB=\"MYSQLCPPCONN_DYNLOAD_MYSQL_LIB-NOTFOUND\" 
> -Dmysqlcppconn_EXPORTS -I/usr/include/mysql 
> -I/build/mysql-connector-c++-XqlzJw/mysql-connector-c++-1.1.4+really1.1.3/builddir
>  
> -I/build/mysql-connector-c++-XqlzJw/mysql-connector-c++-1.1.4+really1.1.3/builddir/cppconn
>  
> -I/build/mysql-connector-c++-XqlzJw/mysql-connector-c++-1.1.4+really1.1.3/builddir/driver/nativeapi
>   -DLIBMYSQLCLIENT_SONAME=\"/usr/lib/x86_64-linux-gnu/libmysqlclient_r_r.so\" 
>   -fPIC   -Wall -fPIC -Woverloaded-virtual   
> -DLIBMYSQLCLIENT_SONAME=\"/usr/lib/x86_64-linux-gnu/libmysqlclient_r_r.so\"  
> -I/usr/include/mysql 
> -fdebug-prefix-map=/build/mysql-5.7-ClWLeg/mysql-5.7-5.7.15=. -fabi-version=2 
> -fno-omit-frame-pointer -o 
> CMakeFiles/mysqlcppconn.dir/mysql_art_rset_metadata.cpp.o -c 
> /build/mysql-connector-c++-XqlzJw/mysql-connector-c++-1.1.4+really1.1.3/builddir/driver/mysql_art_rset_metadata.cpp
> [  6%] Building CXX object 
> driver/CMakeFiles/mysqlcppconn.dir/mysql_connection.cpp.o
> cd 
> /build/mysql-connector-c++-XqlzJw/mysql-connector-c++-1.1.4+really1.1.3/builddir/driver
>  && /usr/bin/c++   -DCPPCONN_SO_BUILD=\"\" 
> -DDYNLOAD_MYSQL_LIB=\"MYSQLCPPCONN_DYNLOAD_MYSQL_LIB-NOTFOUND\" 
> -Dmysqlcppconn_EXPORTS -I/usr/include/mysql 
> -I/build/mysql-connector-c++-XqlzJw/mysql-connector-c++-1.1.4+really1.1.3/builddir
>  
> -I/build/mysql-connector-c++-XqlzJw/mysql-connector-c++-1.1.4+really1.1.3/builddir/cppconn
>  
> -I/build/mysql-connector-c++-XqlzJw/mysql-connector-c++-1.1.4+really1.1.3/builddir/driver/nativeapi
>   -DLIBMYSQLCLIENT_SONAME=\"/usr/lib/x86_64-linux-gnu/libmysqlclient_r_r.so\" 
>   -fPIC   -Wall -fPIC -Woverloaded-virtual   
> -DLIBMYSQLCLIENT_SONAME=\"/usr/lib/x86_64-linux-gnu/libmysqlclient_r_r.so\"  
> -I/usr/include/mysql 
> -fdebug-prefix-map=/build/mysql-5.7-ClWLeg/mysql-5.7-5.7.15=. -fabi-version=2 
> -fno-omit-frame-pointer -o CMakeFiles/mysqlcppconn.dir/mysql_connection.cpp.o 
> -c 
> /build/mysql-connector-c++-XqlzJw/mysql-connector-c++-1.1.4+really1.1.3/builddir/driver/mysql_connection.cpp
> In file included from 
> /build/mysql-connector-c++-XqlzJw/mysql-connector-c++-1.1.4+really1.1.3/builddir/driver/mysql_connection.cpp:69:0:
> /build/mysql-connector-c++-XqlzJw/mysql-connector-c++-1.1.4+reall

Bug#842171: marked as done (musl: CVE-2016-8859: Regex integer overflow in buffer size computations)

[Debian Bug Tracking System]

Your message dated Sun, 13 Nov 2016 11:17:19 +
with message-id 
and subject line Bug#842171: fixed in musl 1.1.5-2+deb8u1
has caused the Debian Bug report #842171,
regarding musl: CVE-2016-8859: Regex integer overflow in buffer size 
computations
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.)


-- 
842171: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842171
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: musl
Version: 1.1.15-1
Severity: grave
Tags: security upstream

Hi,

the following vulnerability was published for musl.

CVE-2016-8859[0]:
Regex integer overflow in buffer size computations

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-8859
[1] http://www.openwall.com/lists/oss-security/2016/10/19/1

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: musl
Source-Version: 1.1.5-2+deb8u1

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

Debian distribution maintenance software
pp.
Reiner Herrmann  (supplier of updated musl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 26 Oct 2016 19:39:31 +0200
Source: musl
Binary: musl musl-dev musl-tools
Architecture: source
Version: 1.1.5-2+deb8u1
Distribution: jessie
Urgency: high
Maintainer: Kevin Bortis 
Changed-By: Reiner Herrmann 
Description:
 musl   - standard C library
 musl-dev   - standard C library development files
 musl-tools - standard C library tools
Closes: 842171
Changes:
 musl (1.1.5-2+deb8u1) jessie; urgency=high
 .
   * Cherry-pick upstream fix for regex integer overflow in buffer size
 computations; CVE-2016-8859 (Closes: #842171)
Checksums-Sha1:
 a33cb0f3b8a934a4771e0779e39a4ce894d3f472 2001 musl_1.1.5-2+deb8u1.dsc
 5be2642367c9a47ae752ae6df24263fd00301ab9 872924 musl_1.1.5.orig.tar.gz
 ad796cbdc93d7d349b76996dcac7fee7742eda29 9100 musl_1.1.5-2+deb8u1.debian.tar.xz
Checksums-Sha256:
 eba9601342e611e5525bab3905f7b4426f5140fd6b740df66a1e73e7e3074179 2001 
musl_1.1.5-2+deb8u1.dsc
 352362b1724cc9740f4c3ce0fe02aae45e4de9809ea4ac961f31aedc11b87393 872924 
musl_1.1.5.orig.tar.gz
 8fce12f591a0781c42edbfa5b1262f725db0ed79d64875e645329ef51d31e271 9100 
musl_1.1.5-2+deb8u1.debian.tar.xz
Files:
 838ab4fa9dc027668b4316466440e055 2001 libs extra musl_1.1.5-2+deb8u1.dsc
 94f8aa9dab80229fed68991bb9984cc5 872924 libs extra musl_1.1.5.orig.tar.gz
 19a8b2cb347ba53a755d79098868f39f 9100 libs extra 
musl_1.1.5-2+deb8u1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJYIQPFAAoJEMzwSSjbDuqndwwP/0MNCsuPp8WLwvFxHViBxuNl
yBtTA2VirWg+bLuXq1qMzy8Dr6fQTNIUyaQ3zMBr7WPO4u2RsK2g/qWFqL+LfB8J
fWHGA/4BrdHNX4gzBMjKJDraNfDUTaHSrgQHlepuFFV5Ns2cDI874tDDrFfiAKyu
ulmlpV9cENg7TBqb1OiZ+bfKxc/NGBkBdUtCwIO7kwydr8v+eEMLXk+a4O0ajxO7
7I8+meCGR0slhanoo3D5TSuV4wAC07J0ZL5GXMTeZNZkYt9gw7rpRuL+27nmXwA0
0vNzjJIQAxIxMxVNpLliIOsW6k110986aeqgZs1Ku9N/Jx6P5MSLzR9d9DzNbgxX
FIcdgnJ6xyfwoIg+ZBFWsy14h2lWyZCiEV27IAkf1A7CLklutMTv2nOhgtCfcC2X
bAZd940o1EvOetS76ndfqjKVzjanu5r7azECgx/vYllBUoVNM5QRyCi296h9qZ95
Z7dvCgs5tj6Rz8LGmiq7Occsm084z6FoswuVDT/w+yJN93GBeqBpV2/2vuHn/H3o
WxqpzhcLRN0rxGi8TE16ZDBTjx3nkvxovhpFZCCXKwP/0/0yCKCS0vIX6Iz10sEG
3dx3ya2mW3JqTkdSBp/xRpnz1HDkLeVJTX/7vH64Rz2Y8p+iB8K1kJZQ3J6IsDke
lPxoODv28zkzmJZBWf8J
=zFXX
-END PGP SIGNATURE End Message ---

Processed: tagging 838932, tagging 844160

[Debian Bug Tracking System]

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

> tags 838932 + pending
Bug #838932 [apache2] apache2: multiple apache instances don't start after 
reboot without the default apache enabled
Added tag(s) pending.
> tags 844160 + pending
Bug #844160 [apache2-dev] apache2-dev should depend on libssl1.0-dev
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#834713: marked as done (golang-github-xenolf-lego: accesses the internet during build)

[Debian Bug Tracking System]

Your message dated Sun, 13 Nov 2016 11:20:04 +
with message-id 
and subject line Bug#834713: fixed in golang-github-xenolf-lego 0.3.1-2
has caused the Debian Bug report #834713,
regarding golang-github-xenolf-lego: 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.)


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

Dear Maintainer,

Whilst golang-github-xenolf-lego 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 3448c95ec662.33714 > 169.254.169.254.http: Flags [S], seq 
4145955516, win 29200, options [mss 1460,sackOK,TS val 116894613 ecr 
0,nop,wscale 7], length 0
  00:00:00.002685 IP 3448c95ec662.40891 > 10.0.1.1.domain: 49936+ ? 
metadata.google.internal. (42)
  00:00:00.002796 IP 3448c95ec662.51200 > 10.0.1.1.domain: 17740+ A? 
metadata.google.internal. (42)
  00:00:00.013343 IP 10.0.1.1.domain > 3448c95ec662.51200: 17740 NXDomain* 
0/0/0 (42)
  00:00:00.019853 IP 10.0.1.1.domain > 3448c95ec662.40891: 49936 NXDomain* 
0/0/0 (42)
  00:00:00.020067 IP 3448c95ec662.47514 > 10.0.1.1.domain: 56608+ ? 
metadata.google.internal.chris-lamb.co.uk. (59)
  00:00:00.020171 IP 3448c95ec662.54081 > 10.0.1.1.domain: 4474+ A? 
metadata.google.internal.chris-lamb.co.uk. (59)
  00:00:00.054065 IP 10.0.1.1.domain > 3448c95ec662.47514: 56608 NXDomain* 
0/0/0 (59)
  00:00:00.054319 IP 10.0.1.1.domain > 3448c95ec662.54081: 4474 NXDomain* 0/0/0 
(59)
  00:00:02.999679 IP httpredir.debian.org > 3448c95ec662: ICMP host 
169.254.169.254 unreachable, length 68

  [..]

(Can't quite work out what its accessing here, but I think it's something
to do with a Google cloud service?)

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


Regards,

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


golang-github-xenolf-lego.0.3.1-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: golang-github-xenolf-lego
Source-Version: 0.3.1-2

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

Debian distribution maintenance software
pp.
Dr. Tobias Quathamer  (supplier of updated 
golang-github-xenolf-lego 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, 13 Nov 2016 11:48:33 +0100
Source: golang-github-xenolf-lego
Binary: golang-github-xenolf-lego-dev lego
Architecture: source all amd64
Version: 0.3.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Dr. Tobias Quathamer 
Description:
 golang-github-xenolf-lego-dev - Let's Encrypt ACME library
 lego   - Let's Encrypt client
Closes: 834713
Changes:
 golang-github-xenolf-lego (0.3.1-2) unstable; urgency=medium
 .
   [ Dmitry Smirnov ]
   * Team upload.
   * Remove "googlecloud_test.go" due to network access (Closes: #834713)
 .
   [ Dr. Tobias Quathamer ]
   * Use debhelper v10
Checksums-Sha1:
 13a51985f24d35d2d55cb423606d667a69e52154 2591 
golang-github-xenolf-lego_0.3.1-2.dsc
 848f940f096aa95ffcd01b662b9add4166eb5f5b 2268 
golang-github-xenolf-lego_0.3.1-2.debian.tar.xz
 a8604f2d051ed4f6252eee4da355ed7dbf56a300 26976 
golang-github-xenolf-lego-dev_0.3.1-2_all.deb
 ebd6c165cb8597be49d66d9c291bf29a8d897570 6882 
golang-github-xenolf-lego_0.3.1-2_20161113T105200z-d02deb69.buildinfo
 a8793f5a71184809e18ad3f2ef83025f937a642b 2171980 lego_0.3.1-2_amd64.deb
Checksums-Sha256:
 b576b5bafa4355826d7b0c67f4a61052371645b84ed92035b273798585bfbd31 2591 
golang-github-xenolf-lego_0.3.1-2.dsc
 4bb21aedde0ae31fcfd6629b0def9c12f00d29024f080fb48e0874baf795e192 2268 
golang-github-xenolf-lego_0.3.1-2.debian.tar.xz
 8187771421cf55aa12f77223cc5947eb088331bb11ec8f18736ea52e212ff608 26976 
golang-githu

Bug#842570: marked as done (libxslt: CVE-2016-4738: possible heap overread)

[Debian Bug Tracking System]

Your message dated Sun, 13 Nov 2016 11:17:12 +
with message-id 
and subject line Bug#842570: fixed in libxslt 1.1.28-2+deb8u2
has caused the Debian Bug report #842570,
regarding libxslt: CVE-2016-4738: possible heap overread
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.)


-- 
842570: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842570
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libxslt
Version: 1.1.28-2
Severity: grave
Tags: security upstream patch

Hi,

the following vulnerability was published for libxslt.

CVE-2016-4738[0]:
| libxslt in Apple iOS before 10, OS X before 10.12, tvOS before 10, and
| watchOS before 3 allows remote attackers to execute arbitrary code or
| cause a denial of service (memory corruption) via a crafted web site.

Unfortunately as for many libxml2 issues, the above is not very
specific and there is upstream bug referenced. But the fix is
mentioned as [1].

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-4738
[1] 
https://git.gnome.org/browse/libxslt/commit/?id=eb1030de31165b68487f288308f9d1810fed6880

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: libxslt
Source-Version: 1.1.28-2+deb8u2

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated libxslt package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 06 Nov 2016 21:43:39 +0100
Source: libxslt
Binary: libxslt1.1 libxslt1-dev libxslt1-dbg xsltproc python-libxslt1 
python-libxslt1-dbg
Architecture: source
Version: 1.1.28-2+deb8u2
Distribution: jessie-security
Urgency: high
Maintainer: Debian XML/SGML Group 
Changed-By: Salvatore Bonaccorso 
Closes: 842570
Description: 
 libxslt1-dbg - XSLT 1.0 processing library - debugging symbols
 libxslt1-dev - XSLT 1.0 processing library - development kit
 libxslt1.1 - XSLT 1.0 processing library - runtime library
 python-libxslt1 - Python bindings for libxslt1
 python-libxslt1-dbg - Python bindings for libxslt1 (debug extension)
 xsltproc   - XSLT 1.0 command line processor
Changes:
 libxslt (1.1.28-2+deb8u2) jessie-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * Fix heap overread in xsltFormatNumberConversion (CVE-2016-4738)
 (Closes: #842570)
Checksums-Sha1: 
 6a250431bb43b792352b0d17dcce4e62aee3fc2c 2529 libxslt_1.1.28-2+deb8u2.dsc
 aa8895a781dc554bfe6416843ef25b4cffa054df 37564 
libxslt_1.1.28-2+deb8u2.debian.tar.xz
Checksums-Sha256: 
 e5a1286006f7c9d136f1a2441e4993deb35551ed359d4cb7492d3128835f6f64 2529 
libxslt_1.1.28-2+deb8u2.dsc
 218aa08affb2a5c8b8935a8b44d09e7727cbf453576b4c3e0886fd86a966cca0 37564 
libxslt_1.1.28-2+deb8u2.debian.tar.xz
Files: 
 11e4607da911d652afd3bd9c8ffe4c1f 2529 text optional libxslt_1.1.28-2+deb8u2.dsc
 d875d4c91dd9e2837f92565d6197f97e 37564 text optional 
libxslt_1.1.28-2+deb8u2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKPBAEBCgB5BQJYIWmsXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ0NjQ0NDA5ODA4QzE3MUUwNTUzMURERUUw
NTRDQjhGMzEzNDNDRjQ0EhxjYXJuaWxAZGViaWFuLm9yZwAKCRAFTLjzE0PPRPQy
D/sFdBerxEHHzUTOdjjmgj4i47aWWvSJn9RP/XLgmzQOJosrEyHhZnS+ceTKS/7/
u3XbNNu0uphlKDrDIc3pTkJYLEIngVCgOBgNjLV7up/hC2o7gPhSfagtGS4gN60n
JeR22EWr4KkGvaP52NoLG//EwECMKCj8EkPSOc1rnjQeQVqmu/7+x6YykqJVoIbf
kQL+w4y39yBLVzkirm1VbnrjLWQdQS0pnYJ6xpnheru5sqj44SJ2nEl8ZvJ2CNxv
xKuYSCI8qJ4M+bW0vV9AKoUAPYOo/mqP8dkHlULQpJpO3cCC4WwCrg6b7pm+l7au
z8lqKfNTHZZcjKGrs4l/oKIUMA3LYFT4cRc8sGSJh15yZsmKDEGBw87nGqAOgCgk
7B11xk4g0WJ1VcXW5SWNwdcCw8vkxcfZ6FPQIKTzwsZ2YXCXO8bEqS8/yBEWrgSY
g4zvno+HEhnfsUepPgzy12dWIPpBM5LnUK+OdlYZEwMKzuLDbWsyF6qj6wH8zXFU
cXXwcfAjO7rwS5XKeRpRaBQ4V7nVZD9+H4y8rMEvW4BNBiNcovVr1WemK5OwLln0
ZHI1WuaFdoH5EaEWeoSWVyTykYnhLwIEk+e3vkL/Vq5EQHr/c1PS7QSyquQz0ePb
ySWzLMfl7guDTmrcxGc3AkuzAu

Bug#831554: marked as done (cyrus-nntpd-2.4: nntp not working, regression of #734648?)

[Debian Bug Tracking System]

Your message dated Sun, 13 Nov 2016 11:17:11 +
with message-id 
and subject line Bug#831554: fixed in cyrus-imapd-2.4 2.4.17+nocaldav-0+deb8u2
has caused the Debian Bug report #831554,
regarding cyrus-nntpd-2.4: nntp not working, regression of #734648?
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.)


-- 
831554: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831554
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cyrus-nntpd-2.4
Version: 2.4.17+nocaldav-0~deb8u1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I have upgraded my server to from Debian 7 to Debian 8.
After this upgrade it is not possible anymore to feed news into
my imap spool. In the logs I get the following output from fetchnews:
cyrus/fetchnews[6474]: fetchnews: nntp.aioe.org offered 4; localhost rejected 
0, accepted 0, failed 4

This problem was registered as bugreport on cyrus and fixed in 2.4.18:
https://bugzilla.cyrusimap.org/show_bug.cgi?id=3833 . A detailed description of
the problem can be found there. Also I had a similar problem during
upgrading from debian 6 to debian 7: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734648

I compiled the cyrus nntpd from cyrus 2.4.18. With this nntpd I could 
successfully deliver news into my imap spool.

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

Kernel: Linux 3.2.41-042stab111.12 (SMP w/2 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) (ignored: LC_ALL 
set to de_DE.utf8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages cyrus-nntpd-2.4 depends on:
ii  cyrus-nntpd  2.4.17+nocaldav-0~deb8u1
ii  dpkg 1.17.27

cyrus-nntpd-2.4 recommends no packages.

cyrus-nntpd-2.4 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: cyrus-imapd-2.4
Source-Version: 2.4.17+nocaldav-0+deb8u2

We believe that the bug you reported is fixed in the latest version of
cyrus-imapd-2.4, 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.
Ondřej Surý  (supplier of updated cyrus-imapd-2.4 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, 07 Nov 2016 09:06:21 +0100
Source: cyrus-imapd-2.4
Binary: cyrus-common cyrus-doc cyrus-imapd cyrus-pop3d cyrus-admin cyrus-murder 
cyrus-replication cyrus-nntpd cyrus-clients cyrus-dev libcyrus-imap-perl 
cyrus-common-2.4 cyrus-doc-2.4 cyrus-imapd-2.4 cyrus-pop3d-2.4 cyrus-admin-2.4 
cyrus-murder-2.4 cyrus-replication-2.4 cyrus-nntpd-2.4 cyrus-clients-2.4 
cyrus-dev-2.4 libcyrus-imap-perl24
Architecture: source amd64 all
Version: 2.4.17+nocaldav-0+deb8u2
Distribution: jessie
Urgency: medium
Maintainer: Debian Cyrus Team 

Changed-By: Ondřej Surý 
Description:
 cyrus-admin - Cyrus mail system - administration tools
 cyrus-admin-2.4 - Cyrus mail system - administration tools [dummy package]
 cyrus-clients - Cyrus mail system - test clients
 cyrus-clients-2.4 - Cyrus mail system - test clients [dummy package]
 cyrus-common - Cyrus mail system - common files
 cyrus-common-2.4 - Cyrus mail system - common files [dummy package]
 cyrus-dev  - Cyrus mail system - developer files
 cyrus-dev-2.4 - Cyrus mail system - developer files [dummy package]
 cyrus-doc  - Cyrus mail system - documentation files
 cyrus-doc-2.4 - Cyrus mail system - documentation files [dummy package]
 cyrus-imapd - Cyrus mail system - IMAP support
 cyrus-imapd-2.4 - Cyrus mail system - IMAP support [dummy package]
 cyrus-murder - Cyrus mail system - proxies and aggregator
 cyrus-murder-2.4 - Cyrus mail system - proxies and aggregator [dummy package]
 cyrus-nntpd - Cyrus mail system - NNTP support
 cyrus-nntpd-2.4 - Cyrus mail system - NNTP support [dummy package]
 cyrus-pop3d - Cyrus mail system - POP3 support
 cyrus-pop3d-2.4 - Cyrus mail system - POP3 support [dummy package]
 cyrus-replication - Cyrus mail system - replication
 cyrus-replication-2.4 - Cyrus mail system - replication [dummy package]
 libcyrus-imap-perl

Bug#829494: marked as done (chirpw phones home without informed consent)

[Debian Bug Tracking System]

Your message dated Sun, 13 Nov 2016 11:17:08 +
with message-id 
and subject line Bug#829494: fixed in chirp 0.4.0-1+deb8u1
has caused the Debian Bug report #829494,
regarding chirpw phones home without informed consent
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.)


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

Package: chirp
Version: 0.4.0-1
Severity: serious

A pop-up dialog from the "chirpw" program says that it reports some kind 
of usage information to some external party, and describes how to 
opt-out of this.  There are at least two privacy problems:


1. It appears that some phoning home happens before the user has given 
informed consent.  For example, when I received the pop-up dialogue, I 
immediately disabled reporting, but I found that "chirpw" had already 
contacted some server and informed me that I was not using the latest 
version.  Therefore, the suggestion that one can opt-out of phoning-home 
is misleading, since some phoning-home has already occurred.


2. Also, the text suggests that this is anonymous, but that is 
misleading (due, e.g., to IP address traceability), so any consent would 
not be informed, even were it given prior to phoning-home occurring.


Note that I have not looked at what information is transmitted, so there 
might be a third problem, but I believe these two identified problems 
alone require action.


I recommend and request that this reporting and any other "phoning home" 
either be disabled completely in the Debian "chirp" package, or changed 
to be an express *opt-in* (like opt-in is long used elsewhere in Debian, 
such as for package "popularity contest"). Thank you.
--- End Message ---
--- Begin Message ---
Source: chirp
Source-Version: 0.4.0-1+deb8u1

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

Debian distribution maintenance software
pp.
Iain R. Learmonth  (supplier of updated chirp package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 08 Nov 2016 12:15:26 +
Source: chirp
Binary: chirp
Architecture: source amd64
Version: 0.4.0-1+deb8u1
Distribution: jessie
Urgency: medium
Maintainer: Debian Hamradio Maintainers 
Changed-By: Iain R. Learmonth 
Description:
 chirp  - Configuration tool for amateur radios
Closes: 829494
Changes:
 chirp (0.4.0-1+deb8u1) jessie; urgency=medium
 .
   * Disables reporting of telemetry without informed consent (Closes: #829494)
Checksums-Sha1:
 4e47d21e7e41d0a8a0d118f130586cf54b5cf3ae 1670 chirp_0.4.0-1+deb8u1.dsc
 71e8736860118a64e34a87d660cd209a56bc9fce 3736 
chirp_0.4.0-1+deb8u1.debian.tar.xz
 33ed3b62d835ac8186ffd37f0f561ed9aef0fa21 276154 chirp_0.4.0-1+deb8u1_amd64.deb
Checksums-Sha256:
 f9c9cc186f43a6bfbb9a1a7680d34c018c5d3329e01129393403fb056fa31c3d 1670 
chirp_0.4.0-1+deb8u1.dsc
 0547ad1c6a90021b2487bf9d110db1892e97731dae2aa1a131cb543a329f718f 3736 
chirp_0.4.0-1+deb8u1.debian.tar.xz
 7e14e1213c2abee767b5c3e062b3cb1752d8998ed3bf2df6d07ef782342e6097 276154 
chirp_0.4.0-1+deb8u1_amd64.deb
Files:
 09fa992a2cea6745c17bf3c2478fe904 1670 hamradio optional 
chirp_0.4.0-1+deb8u1.dsc
 ed9cd7aa5a871eb5762755103a0a0114 3736 hamradio optional 
chirp_0.4.0-1+deb8u1.debian.tar.xz
 5ac5c55004b9114d4b4098246325685f 276154 hamradio optional 
chirp_0.4.0-1+deb8u1_amd64.deb

-BEGIN PGP SIGNATURE-

iQEcBAEBCAAGBQJYIcMOAAoJENIXnVuKHtARVC8IAJJoMOZlY4S5TXGgnnO0UOr7
a7HkOJL+4y5XA7HfGKTR8xDrB1wSbvJLjyT1v+PYAE+hSPd0G0KMat534HzyDZcU
FcNp01nfXlqlK4HUmuVDCsynK4Wn1k9lSOQV2H80YcTFg+Sa2F3ZzA/clDKyYOWq
vrUv1NF8Eem15nCfgrD/i8Yu+C7xeRQGKLJifhOhkTyXqCnO65NcxwdPjpr4nuT9
Eygu3gruVKtH936zDaS7L9VCNJIAVkD8ScyFr8m2SXDeo6OF5HeFiXTr+RurPot1
uSF24aD2wEJeUFfzciLavgSliNL5XDInFmUQInRc0EY0vX9wzQsA0bAJvLFgSvk=
=vmJM
-END PGP SIGNATURE End Message ---

Bug#844208: qemu-system-sparc: Needed openbios-sparc not available in jessie-backports

[Pierre Bernhardt]

Package: qemu-system-sparc
Version: 1:2.6+dfsg-3.1~bpo8+1
Severity: grave
Tags: newcomer
Justification: renders package unusable

Dear Maintainer,

if openbios-sparc is not available in jessie-backports. So only the release
from jessie could be used.
But the acutal jessie-backports openbios-sparc needs openbios-sparc >=
1.1+svn1395-1~.

root@host:/etc/apt# apt-get install qemu-system-sparc
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 qemu-system-sparc : Depends: openbios-sparc (>= 1.1+svn1395-1~) but
1.1+svn1306-2 is to be installed
E: Unable to correct problems, you have held broken packages.

root@nihilnihil:/etc/apt# apt-cache policy qemu-system-sparc openbios-sparc
qemu-system-sparc:
  Installed: 1:2.6+dfsg-3.1~bpo8+1
  Candidate: 1:2.7+dfsg-3~bpo8+2
  Version table:
 1:2.7+dfsg-3~bpo8+2 0
600 http://ftp.de.debian.org/debian/ jessie-backports/main amd64
Packages
 *** 1:2.6+dfsg-3.1~bpo8+1 0
100 /var/lib/dpkg/status
 1:2.1+dfsg-12+deb8u6 0
500 http://ftp.de.debian.org/debian/ jessie/main amd64 Packages
500 http://security.debian.org/ jessie/updates/main amd64 Packages
openbios-sparc:
  Installed: 1.1+svn1306-2
  Candidate: 1.1+svn1306-2
  Version table:
 *** 1.1+svn1306-2 0
500 http://ftp.de.debian.org/debian/ jessie/main amd64 Packages
100 /var/lib/dpkg/status
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Pierre Bernhardt 
To: Debian Bug Tracking System 
Subject: qemu-system-sparc: Needed openbios-sparc not available in 
jessie-backports
Bcc: Pierre Bernhardt 

So also the upgrade fails.



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

Kernel: Linux 4.7.0-0.bpo.1-amd64 (SMP w/6 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages qemu-system-sparc depends on:
ii  libaio1 0.3.110-1
ii  libasound2  1.0.28-1
ii  libbluetooth3   5.23-2+b1
ii  libbrlapi0.65.3.1-1~bpo8+1
ii  libc6   2.19-18+deb8u6
ii  libcacard0  1:2.5.0-2~bpo8+1
ii  libfdt1 1.4.0+dfsg-2~bpo8+1
ii  libgcc1 1:4.9.2-10
ii  libglib2.0-02.48.0-1~bpo8+1
ii  libgnutls-deb0-28   3.3.8-6+deb8u3
ii  libjpeg62-turbo 1:1.3.1-12
ii  libncurses5 5.9+20140913-1+b1
ii  libnettle4  2.7.1-5+deb8u1
ii  libpixman-1-0   0.32.6-3
ii  libpng12-0  1.2.50-2+deb8u2
ii  libpulse0   7.1-2~bpo8+1
ii  libsasl2-2  2.1.26.dfsg1-13+deb8u1
ii  libsdl1.2debian 1.2.15-10+b1
ii  libseccomp2 2.2.3-3~bpo8+1
ii  libspice-server10.12.5-1+deb8u3
ii  libtinfo5   5.9+20140913-1+b1
ii  libusb-1.0-02:1.0.19-1
ii  libusbredirparser1  0.7-1
ii  libuuid12.25.2-6
ii  libvdeplug2 2.3.2+r586-1
ii  libx11-62:1.6.2-3
ii  libxen-4.4  4.4.1-9+deb8u7
ii  libxenstore3.0  4.4.1-9+deb8u7
ii  openbios-sparc  1.1+svn1306-2
ii  qemu-system-common  1:2.7+dfsg-3~bpo8+2
ii  zlib1g  1:1.2.8.dfsg-2+b1

Versions of packages qemu-system-sparc recommends:
ii  ipxe-qemu   1.0.0+git-20141004.86285d1-1
ii  qemu-utils  1:2.7+dfsg-3~bpo8+2
ii  seabios 1.7.5-1

Versions of packages qemu-system-sparc suggests:
pn  qemu-block-extra  
ii  samba 2:4.2.10+dfsg-0+deb8u3
pn  vde2  

-- no debconf information

Processed: Debian bugs: #806104, #820964, #821255, #829244

[Debian Bug Tracking System]

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

> tags 806104 + pending
Bug #806104 [src:sane-backends] sane-backends: FTBFS when built with 
dpkg-buildpackage -A (No such file or directory)
Ignoring request to alter tags of bug #806104 to the same tags previously set
> tags 820964 + pending
Bug #820964 [libsane-bin] libsane-bin is wrongly marked Multi-Arch: foreign
Added tag(s) pending.
> tags 821255 + pending
Bug #821255 [src:sane-backends] sane-backends: saned option to report 
network-attached devices
Added tag(s) pending.
> tags 829244 + pending
Bug #829244 [src:sane-backends] sane-backends: initscript stop and restart 
actions should ensure the process has stopped before returning
Ignoring request to alter tags of bug #829244 to the same tags previously set
> --
Stopping processing here.

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

Processed: forcibly merging 832765 841541, severity of 832765 is important

[Debian Bug Tracking System]

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

> forcemerge 832765 841541
Bug #832765 [src:ipxe] ipxe: old version does not support modern network 
adapters.
Bug #832765 [src:ipxe] ipxe: old version does not support modern network 
adapters.
Added tag(s) sid and stretch.
Bug #841541 [src:ipxe] ipxe: FTBFS: cc1MIrHx.s:27: Error: missing or invalid 
displacement expression `private_key_len@GOTOFF'
Severity set to 'wishlist' from 'serious'
Merged 832765 841541
> severity 832765 important
Bug #832765 [src:ipxe] ipxe: old version does not support modern network 
adapters.
Bug #841541 [src:ipxe] ipxe: FTBFS: cc1MIrHx.s:27: Error: missing or invalid 
displacement expression `private_key_len@GOTOFF'
Severity set to 'important' from 'wishlist'
Severity set to 'important' from 'wishlist'
> thanks
Stopping processing here.

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

Bug#841722: marked as done (libpaper: tmp file vulnerability in debian/rules clean target)

[Debian Bug Tracking System]

Your message dated Sun, 13 Nov 2016 12:05:49 +
with message-id 
and subject line Bug#841722: fixed in libpaper 1.1.24+nmu5
has caused the Debian Bug report #841722,
regarding libpaper: tmp file vulnerability in debian/rules clean target
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.)


-- 
841722: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841722
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libpaper
Version: 1.1.21
Severity: serious
Tags: security patch sid stretch

The clean target includes a line "exec > /tmp/libpaper1.new". Since that
is a predictable path in a world writeable location, it can effectively
be used to compromise the build user.

Surprisingly, the counterpart target debian/libpaper1.config get's this
right. So the fix is pretty simple and thus attached.

Note that the ancient version number is correct. The bug was introduced
somewhen between sarge and etch and has persisted since. I'm also
tagging the bug sid stretch as I don't think it makes sense to fix it in
a stable update.

Helmut
diff --minimal -Nru libpaper-1.1.24+nmu4/debian/changelog 
libpaper-1.1.24+nmu5/debian/changelog
--- libpaper-1.1.24+nmu4/debian/changelog   2014-11-01 14:35:21.0 
+0100
+++ libpaper-1.1.24+nmu5/debian/changelog   2016-10-22 17:54:12.0 
+0200
@@ -1,3 +1,10 @@
+libpaper (1.1.24+nmu5) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix /tmp file vulnerability in debian/rules clean target (Closes: #-1)
+
+ -- Helmut Grohne   Sat, 22 Oct 2016 17:53:54 +0200
+
 libpaper (1.1.24+nmu4) unstable; urgency=medium
 
   * Non-maintainer upload.
diff --minimal -Nru libpaper-1.1.24+nmu4/debian/rules 
libpaper-1.1.24+nmu5/debian/rules
--- libpaper-1.1.24+nmu4/debian/rules   2014-11-01 14:26:20.0 +0100
+++ libpaper-1.1.24+nmu5/debian/rules   2016-10-22 17:53:51.0 +0200
@@ -64,10 +64,10 @@
[ ! -f Makefile ] || $(MAKE) distclean
dh_autoreconf_clean
dh_clean
-   exec > /tmp/libpaper1.new \
+   exec > debian/libpaper1.config.new \
&& sed -n '1,/^__BEGIN_PAPERSPECS__/p' debian/libpaper1.config \
&& sed -n '/^__END_PAPERSPECS__/,$$p' debian/libpaper1.config
-   mv /tmp/libpaper1.new debian/libpaper1.config
+   mv debian/libpaper1.config.new debian/libpaper1.config
 
 binary-indep:  DH_OPTIONS=-i
 binary-indep:  checkroot build
--- End Message ---
--- Begin Message ---
Source: libpaper
Source-Version: 1.1.24+nmu5

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

Debian distribution maintenance software
pp.
Jonathan Wiltshire  (supplier of updated libpaper 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, 11 Nov 2016 11:28:37 +
Source: libpaper
Binary: libpaper1 libpaper-utils libpaper-dev
Architecture: source amd64
Version: 1.1.24+nmu5
Distribution: unstable
Urgency: medium
Maintainer: Giuseppe Sacco 
Changed-By: Jonathan Wiltshire 
Description:
 libpaper-dev - library for handling paper characteristics (development files)
 libpaper-utils - library for handling paper characteristics (utilities)
 libpaper1  - library for handling paper characteristics
Closes: 841722
Changes:
 libpaper (1.1.24+nmu5) unstable; urgency=medium
 .
   [ Helmut Grohne ]
   * Non-maintainer upload.
   * Fix /tmp file vulnerability in debian/rules clean target
 (Closes: #841722)
Checksums-Sha1:
 9e7dc0209304e3824a3936f4f644730e93c930ac 1597 libpaper_1.1.24+nmu5.dsc
 fde3c6ce8c8a6ef29242aace0fd6c02543493a8b 49032 libpaper_1.1.24+nmu5.tar.gz
 a6100fda1a4f8fe653db057b6d750721d292b008 16994 
libpaper-dev_1.1.24+nmu5_amd64.deb
 152c35df0d7d64b39ecaa4c19077167d64c2a650 6320 
libpaper-utils-dbgsym_1.1.24+nmu5_amd64.deb
 e893eeb6c6c8dd0eb273ff76940f0ebc1613b7b7 17646 
libpaper-utils_1.1.24+nmu5_amd64.deb
 04e943e61a732cab1e6110e941e553cddc71cfe5 7476 
libpaper1-dbgsym_1.1.24+nmu5_amd64.deb
 275b16b8a8fb82d2a792f24dd2f6f727f3cd311e 21554 libpaper1_1.1.24+nmu5_amd64.deb
 289c3816049e95da07d417e316b4cbeb8e919ac8 5486

Bug#842324: marked as done (console-setup: During apt-get dist-upgrade stage, console-setup did not finish cleanly under ja_JP.UTF-8 locale.)

[Debian Bug Tracking System]

Your message dated Sun, 13 Nov 2016 12:04:58 +
with message-id 
and subject line Bug#842324: fixed in console-setup 1.153
has caused the Debian Bug report #842324,
regarding console-setup: During apt-get dist-upgrade stage, console-setup did 
not finish cleanly under ja_JP.UTF-8 locale.
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.)


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


Package: console-setup
Version: 1.152
Severity: critical
Tags: d-i l10n
Justification: breaks the whole system

Dear Maintainer,

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


   * What led up to the situation?

 I ran "apt-get dist-upgrade" to upgrade to testing repository.
 I ran "apt-get dist-upgrade" after "su" ing to the superuser.
 I am afraid that somehow LANG=ja_JP.UTF-8 setting seeped into the
 environment.
 In that environment, during the execution of
 console-setup, "iconv" failed due to illegal or invalid character
 code or something like that. I am afraid that I failed to log the
 operation successfully and so can't recall the exact message, but
 the failure is due to "iconv", this is for sure.
 I have experienced various "iconv" issues before, and
 thus I changed LANG to LANG=C after seeing the failure and
 ran "apt-get install console-setup" again, and this time
 it succeeded and so the "apt-get dist-upgrade" as a whole 
succeeded!


 On a different PC, I set LANG=C before running apt-get 
dist-upgrade, and found that it ran successfully the first time.



* What exactly did you do (or not do) that was effective (or
 ineffective)?
 Simply ran "apt-get dist-upgrade", and found console-setup failed
 due to the failure of "iconv" that was invoked during its 
execution.

 But setting LANG=C before running apt-get was the cure to solve
 the problem.

   * What was the outcome of this action?

 Failure to run console-setup successfully.

   * What outcome did you expect instead?
 console-setup to run to completion successfully.

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


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

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

Versions of packages console-setup depends on:
ii  console-setup-linux 1.152
ii  debconf 1.5.59
ii  keyboard-configuration  1.152
ii  xkb-data2.18-1

console-setup recommends no packages.

Versions of packages console-setup suggests:
ii  locales   2.24-5
ii  lsb-base  9.20161016

Versions of packages keyboard-configuration depends on:
ii  debconf 1.5.59
ii  liblocale-gettext-perl  1.07-3+b1

Versions of packages console-setup-linux depends on:
ii  init-system-helpers 1.45
ii  initscripts 2.88dsf-59.8
ii  kbd 2.0.3-2
ii  keyboard-configuration  1.152

console-setup-linux suggests no packages.

Versions of packages console-setup is related to:
pn  console-common
pn  console-data  
pn  console-tools 
pn  gnome-control-center  
ii  kbd   2.0.3-2
ii  systemd   231-9

-- debconf information:
* keyboard-configuration/model: A4Tech KB-21
  console-setup/store_defaults_in_debconf_db: true
* keyboard-configuration/store_defaults_in_debconf_db: true
  keyboard-configuration/unsupported_config_options: true
* keyboard-configuration/altgr: The default for the keyboard layout
* keyboard-configuration/variant: Japanese
* keyboard-configuration/switch: No temporary switch
* keyboard-configuration/compose: No compose key
  keyboard-configuration/ctrl_alt_bksp: false
  keyboard-configuration/unsupported_config_layout: true
  console-setup/codesetcode: Lat15
  console-setup/framebuffer_only:
  keyboard-configuration/unsupported_options: true
  console-setup/use_system_font:
  console-setup/codeset47: # Latin1 and Latin5 - western Europe and 
Turkic languages

* keyboard-configuration/xkb-keymap: jp
  console-setup/fontsize: 8x16
* keyboard-configuration/layout:
  console-setup/guess_font:
  console-setup/fontface47: Fixed
* console-setup/charmap47: UTF-8
* keyboard-configuration/variantcode:
* keyboard-configuration/o

Bug#842115: marked as done (partclone: FTBFS: Compiling: fail-mbr.S -> fail-mbr.o -> fail-mbr.image -> /usr/bin/ld: attempted static link of dynamic object `fail-mbr.o')

[Debian Bug Tracking System]

Your message dated Sun, 13 Nov 2016 12:19:45 +
with message-id 
and subject line Bug#842115: fixed in partclone 0.2.89-1
has caused the Debian Bug report #842115,
regarding partclone: FTBFS: Compiling: fail-mbr.S -> fail-mbr.o -> 
fail-mbr.image -> /usr/bin/ld: attempted static link of dynamic object 
`fail-mbr.o'
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.)


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

partclone fails to build from source in unstable/amd64:

  […]

  gcc -DHAVE_CONFIG_H -I. -I..  -DLOCALEDIR=\"/usr/share/locale\" 
-D_FILE_OFFSET_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -DMINIX -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20161025234343.N57us6zz7w.db.partclone/partclone-0.2.88=.
 -fstack-protector-strong -Wformat -Werror=format-security -Wall -c -o 
partclone_minix-partclone.o `test -f 'partclone.c' || echo './'`partclone.c
  gcc -DHAVE_CONFIG_H -I. -I..  -DLOCALEDIR=\"/usr/share/locale\" 
-D_FILE_OFFSET_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -DMINIX -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20161025234343.N57us6zz7w.db.partclone/partclone-0.2.88=.
 -fstack-protector-strong -Wformat -Werror=format-security -Wall -c -o 
partclone_minix-progress.o `test -f 'progress.c' || echo './'`progress.c
  gcc -DHAVE_CONFIG_H -I. -I..  -DLOCALEDIR=\"/usr/share/locale\" 
-D_FILE_OFFSET_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -DMINIX -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20161025234343.N57us6zz7w.db.partclone/partclone-0.2.88=.
 -fstack-protector-strong -Wformat -Werror=format-security -Wall -c -o 
partclone_minix-minixclone.o `test -f 'minixclone.c' || echo './'`minixclone.c
  gcc -DMINIX -g -O2 
-fdebug-prefix-map=/home/lamby/temp/cdt.20161025234343.N57us6zz7w.db.partclone/partclone-0.2.88=.
 -fstack-protector-strong -Wformat -Werror=format-security -Wall  -Wl,-z,relro 
-o partclone.minix partclone_minix-main.o partclone_minix-partclone.o 
partclone_minix-progress.o partclone_minix-minixclone.o  -lncursesw -lpthread  
-ltinfo
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20161025234343.N57us6zz7w.db.partclone/partclone-0.2.88/src'
  Making all in docs
  make[3]: Entering directory 
'/home/lamby/temp/cdt.20161025234343.N57us6zz7w.db.partclone/partclone-0.2.88/docs'
  make[3]: Nothing to be done for 'all'.
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20161025234343.N57us6zz7w.db.partclone/partclone-0.2.88/docs'
  Making all in tests
  make[3]: Entering directory 
'/home/lamby/temp/cdt.20161025234343.N57us6zz7w.db.partclone/partclone-0.2.88/tests'
  make[3]: Nothing to be done for 'all'.
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20161025234343.N57us6zz7w.db.partclone/partclone-0.2.88/tests'
  Making all in fail-mbr
  make[3]: Entering directory 
'/home/lamby/temp/cdt.20161025234343.N57us6zz7w.db.partclone/partclone-0.2.88/fail-mbr'
  sh compile-mbr.sh
  Compiling: fail-mbr.S -> fail-mbr.o -> fail-mbr.image -> /usr/bin/ld: 
attempted static link of dynamic object `fail-mbr.o'
  collect2: error: ld returned 1 exit status
  fail-mbr.bin [Done]. 
  objcopy: 'fail-mbr.image': No such file
  Checking the file:
  objdump: 'fail-mbr.bin': No such file
  files fail-mbr.bin and fail-mbr.bin.orig differ significantly:
  diff: f1.obj: No such file or directory
  diff: f2.obj: No such file or directory
  Makefile:501: recipe for target 'fail-mbr.bin' failed
  make[3]: *** [fail-mbr.bin] Error 1
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20161025234343.N57us6zz7w.db.partclone/partclone-0.2.88/fail-mbr'
  Makefile:400: recipe for target 'all-recursive' failed
  make[2]: *** [all-recursive] Error 1
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20161025234343.N57us6zz7w.db.partclone/partclone-0.2.88'
  Makefile:341: recipe for target 'all' failed
  make[1]: *** [all] Error 2
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20161025234343.N57us6zz7w.db.partclone/partclone-0.2.88'
  dh_auto_build: make -j1 returned exit code 2
  debian/rules:13: recipe for target 'build' failed
  make: *** [build] Error 2

  […]

The full build log is attached.


Regards,

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


partclone.0.2.88-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End

Bug#844205: marked as done (aufs-dkms: I can't load the kernel module after upgrade from Jessie to Stretch.)

[Debian Bug Tracking System]

Your message dated Sun, 13 Nov 2016 13:34:37 +0100
with message-id <9082788e-8afa-8827-8c14-701d8d22f...@fu-berlin.de>
and subject line Re: [Filesystems-devel] Bug#844205: aufs-dkms: I can't load 
the kernel module after upgrade from Jessie to Stretch.
has caused the Debian Bug report #844205,
regarding aufs-dkms: I can't load the kernel module after upgrade from Jessie 
to Stretch.
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.)


-- 
844205: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844205
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: aufs-dkms
Version: 4.8+20161010-1
Severity: critical
Tags: d-i
Justification: causes serious data loss

Dear Maintainer,

   * What led up to the situation?

I wanted to upgrade from Jessie to Stretch.

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

I run apt-get dist-upgrade. Everything was working (or at least, no
critical error appeared).
After that, docker stop to work because the aufs kernel module was not
found.
I tried to install the aufs packages but the kernel can't find it (maybe
because my kernel is 4.7?).

   * What was the outcome of this action?

The only way to have docker working is to delete all the old
images/containers.
It means that I'm losing all my data inside.

   * What outcome did you expect instead?

To load the module correctly and have docker working again also with
images/containers stored
with aufs.
Or, at least to be able to migrate my old images/containers from aufs to
another storage service.



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

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

Versions of packages aufs-dkms depends on:
ii  dkms  2.3-1

Versions of packages aufs-dkms recommends:
ii  aufs-tools  1:4.1+20161010-1

Versions of packages aufs-dkms suggests:
ii  aufs-dev  4.8+20161010-1

-- no debconf information
--- End Message ---
--- Begin Message ---
The current version is packaged for the current unstable kernel, the
problem in this case is that the kernel 4.8 is not migrated to testing
yet. Please wait for the migration (see
https://tracker.debian.org/pkg/linux ) and upgrade then to the kernel
4.8, then the module should be available.

In general it has to be expected that the testing distribution is not
stable/programs breaks in the development phase. If you need a stable
system/stable programs, you should use the stable release (here Jessie).

Best regards,
Jan

Am 13.11.2016 um 11:50 schrieb Leo:
> Package: aufs-dkms Version: 4.8+20161010-1 Severity: critical Tags:
> d-i Justification: causes serious data loss
> 
> Dear Maintainer,
> 
> * What led up to the situation?
> 
> I wanted to upgrade from Jessie to Stretch.
> 
> * What exactly did you do (or not do) that was effective (or 
> ineffective)?
> 
> I run apt-get dist-upgrade. Everything was working (or at least,
> no critical error appeared). After that, docker stop to work
> because the aufs kernel module was not found. I tried to install
> the aufs packages but the kernel can't find it (maybe because my
> kernel is 4.7?).
> 
> * What was the outcome of this action?
> 
> The only way to have docker working is to delete all the old 
> images/containers. It means that I'm losing all my data inside.
> 
> * What outcome did you expect instead?
> 
> To load the module correctly and have docker working again also
> with images/containers stored with aufs. Or, at least to be able to
> migrate my old images/containers from aufs to another storage
> service.
> 
> 
> 
> -- System Information: Debian Release: stretch/sid APT prefers
> testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) 
> Foreign Architectures: i386
> 
> Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores) Locale:
> LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell:
> /bin/sh linked to /bin/dash Init: systemd (via
> /run/systemd/system)
> 
> Versions of packages aufs-dkms depends on: ii  dkms  2.3-1
> 
> Versions of packages aufs-dkms recommends: ii  aufs-tools
> 1:4.1+20161010-1
> 
> Versions of packages aufs-dkms suggests: ii  aufs-dev
> 4.8+20161010-1
> 
> -- no debconf information
> 
> 
> ___ Filesystems-devel
> mailing list filesystems-de...@lists.alioth.debian.org 
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/filesyst

Bug#844160: marked as done (apache2-dev should depend on libssl1.0-dev)

[Debian Bug Tracking System]

Your message dated Sun, 13 Nov 2016 12:34:03 +
with message-id 
and subject line Bug#844160: fixed in apache2 2.4.23-7
has caused the Debian Bug report #844160,
regarding apache2-dev should depend on libssl1.0-dev
to be marked as done.

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

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


-- 
844160: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844160
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apache2-dev
Version: 2.4.23-5
Severity: serious

Looking at mod_ssl_openssl.h and the comment in #828330,
I'd suggest the change below to add a dependency on libssl1.0-dev
to apache2-dev.

This would prevent packages from build-depending (directly or
indirectly) on both apache2-dev and the OpenSSL 1.1 libssl-dev.

--- debian/control.old  2016-11-12 13:18:55.0 +
+++ debian/control  2016-11-12 13:30:56.0 +
@@ -121,7 +121,7 @@
 Package: apache2-dev
 Architecture: any
 Depends: ${misc:Depends}, openssl,
- libapr1-dev, libaprutil1-dev, debhelper (>= 9), ${perl:Depends}
+ libapr1-dev, libaprutil1-dev, debhelper (>= 9), ${perl:Depends}, 
libssl1.0-dev | libssl-dev (<< 1.1)
 Provides: dh-apache2
 Description: Apache HTTP Server (development headers)
  The Apache HTTP Server Project's goal is to build a secure, efficient and
--- End Message ---
--- Begin Message ---
Source: apache2
Source-Version: 2.4.23-7

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

Debian distribution maintenance software
pp.
Stefan Fritsch  (supplier of updated apache2 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, 13 Nov 2016 13:08:28 +0100
Source: apache2
Binary: apache2 apache2-data apache2-bin apache2-utils apache2-suexec-pristine 
apache2-suexec-custom apache2-doc apache2-dev apache2-dbg
Architecture: source amd64 all
Version: 2.4.23-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Apache Maintainers 
Changed-By: Stefan Fritsch 
Description:
 apache2- Apache HTTP Server
 apache2-bin - Apache HTTP Server (modules and other binary files)
 apache2-data - Apache HTTP Server (common files)
 apache2-dbg - Apache debugging symbols
 apache2-dev - Apache HTTP Server (development headers)
 apache2-doc - Apache HTTP Server (on-site documentation)
 apache2-suexec-custom - Apache HTTP Server configurable suexec program for 
mod_suexec
 apache2-suexec-pristine - Apache HTTP Server standard suexec program for 
mod_suexec
 apache2-utils - Apache HTTP Server (utility programs for web servers)
Closes: 838932 844160
Changes:
 apache2 (2.4.23-7) unstable; urgency=medium
 .
   * Make apache2-dev depend on openssl 1.0, too. Closes: #844160
   * Move DefaultRuntimeDir and pid file for multi-instances to
 /var/run/apache2-xxx. Thanks to Horst Platz for the debugging.
 Closes: #838932 LP: #1627339
   * Fix systemd unit naming for multi-instances.
   * Tweak embedded .tar.gz some more to build reproducibly.
Checksums-Sha1:
 44cfb96e3462fb7822afb80c68211649e2846d39 2770 apache2_2.4.23-7.dsc
 9baa1b904fa567a55520298b96d6dc6d70441e8a 352672 apache2_2.4.23-7.debian.tar.xz
 90795d1a9bc7b0c38f1e0666e8e796f8db8af8ac 1150278 apache2-bin_2.4.23-7_amd64.deb
 22d2cf17fbdd0d47222f23b43574d3137dce99c7 162036 apache2-data_2.4.23-7_all.deb
 c61c2629a623e0b92fb2afb511099db0cfa5ed95 2417034 apache2-dbg_2.4.23-7_amd64.deb
 d3387cc2ed5bb6f021861510ce1e1acd363d231c 306124 apache2-dev_2.4.23-7_amd64.deb
 d8d582063f248f5264cc2fe40118e2cf51917876 3753124 apache2-doc_2.4.23-7_all.deb
 7e0533067895e4f5a4a232018c736111bdcd524f 148984 
apache2-suexec-custom_2.4.23-7_amd64.deb
 d10cd12fa1054b22aab0a11d3db0915ab1e9238d 147478 
apache2-suexec-pristine_2.4.23-7_amd64.deb
 47fd62a9833a4364b80daa827ed1291baf52d35c 211042 
apache2-utils_2.4.23-7_amd64.deb
 f444f600cfbc35084f1cddde78c3f1236f775a16 8379 
apache2_2.4.23-7_20161113T121120z-b3d88d78.buildinfo
 3f4fb41f0374f897577290700114512b7708ba79 229126 apache2_2.4.23-7_amd64.deb
Checksums-Sha256:
 ae23a6e056698ac43117f263422a2b815899616af5c14a4b8b76027a7794cad7 2770 
apache2_2.4.23-7.dsc
 f8127a3a07b6e5369a8

Processed (with 1 error): archiving 783051

[Debian Bug Tracking System]

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

> archive 783051
Bug #783051 {Done: Bastian Blank } [ipxe] ipxe: ISO image 
appears to be empty
Bug 783051 cannot be archived
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#837834: marked as done (gtkpod: FTBFS due to undeclared build dependencies)

[Debian Bug Tracking System]

Your message dated Sun, 13 Nov 2016 12:51:16 +
with message-id 
and subject line Bug#837834: fixed in gtkpod 2.1.5-4
has caused the Debian Bug report #837834,
regarding gtkpod: FTBFS due to undeclared build dependencies
to be marked as done.

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

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


-- 
837834: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837834
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gtkpod
Version: 2.1.5-3
Severity: important
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gtk-doc-tools

Hi,

your package gtkpod declares a build dependency on gtk-doc-tools.
gtk-doc-tools in turn depends on gnome-common, which in turn pulls in packages
like gettext, intltool or pkg-config.

The dependency on gnome-common was originally added for the GNOME_GTKDOC_CHECK
macro which has been deprecated and replaced by GTK_DOC_CHECK a long time ago.

As gnome-common has been declared deprecated by GNOME upstream [1], we would
like to drop this dependency from gtk-doc-tools.

We did a test of all reverse build dependencies of gtk-doc-tools and gtkpod
failed to build due to now missing build dependencies which are no longer
pulled in by gtk-doc-tools.

A complete build log is available at
https://people.debian.org/~biebl/gtk-doc-tools/gtkpod.log

We have uploaded that gtk-doc-tools package as 1.25-4 to experimental as well,
so you can test your package against this version.

Common build-failures and their fixes:

a/ configure.ac:32: error: possibly undefined macro: AC_PROG_INTLTOOL

   make[1]: intltoolize: Command not found

   → Build-Depends: intltool

b/ ./configure: line 5461: syntax error near unexpected token `yes'
   ./configure: line 5461: `GNOME_COMPILE_WARNINGS(yes)'

   ./configure: line 14801: GNOME_CODE_COVERAGE: command not found

   → Build-Depends: gnome-common (for GNOME_* macros)

c/ ./configure: line 17439: syntax error near unexpected token 
`$WARN_CFLAGS_EXTRA,'
   ./configure: line 17439: `AX_APPEND_COMPILE_FLAGS($WARN_CFLAGS_EXTRA, 
WARN_CFLAGS)'

   ./configure: line 2629: syntax error near unexpected token `git-directory'
   ./configure: line 2629: `AX_IS_RELEASE(git-directory)'

   → Build-Depends: autoconf-archive (for AX_* macros)

d/ ./configure: line 12518: intltool-update: command not found
   checking for intltool >= 0.40.0...  found
   ./configure: error: Your intltool is too old.  You need intltool 0.40.0 or 
later.

   → Build-Depends: intltool

e/ make[1]: intltoolize: Command not found

   → Build-Depends: intltool

f/ ./autogen.sh calls gnome-autogen.sh

   → Build-Depends: gnome-common


Please add the required build-dependencies to your package so once we upload
gtk-doc-tools_1.25-4 to unstable your package doesn't FTBFS.

Regards,
Michael


[1] https://wiki.gnome.org/Projects/GnomeCommon/Migration
--- End Message ---
--- Begin Message ---
Source: gtkpod
Source-Version: 2.1.5-4

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

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

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

Debian distribution maintenance software
pp.
Matteo F. Vescovi  (supplier of updated gtkpod package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 13 Nov 2016 13:37:44 +0100
Source: gtkpod
Binary: gtkpod gtkpod-data gtkpod-dbg libgtkpod1 libgtkpod-dev 
libatomicparsley0 libatomicparsley-dev
Architecture: source
Version: 2.1.5-4
Distribution: unstable
Urgency: medium
Maintainer: gtkpod Maintainers 
Changed-By: Matteo F. Vescovi 
Description:
 gtkpod - manage songs and playlists on an Apple iPod
 gtkpod-data - architecture-independent files for gtkpod
 gtkpod-dbg - debugging symbols for gtkpod
 libatomicparsley-dev - main library for atomic parsley in gtkpod, development 
kit
 libatomicparsley0 - main library for atomic parsley in gtkpod, shared library
 libgtkpod-dev - main library for the gtkpod package, development kit
 libgtkpod1 - main library for the gtkpod package, shared library
Closes: 837834
Changes:
 gtkpod (2.1.5-4) unstable; urgency=medium
 .
   * debian/control: gnome-common b-dep added (Closes: #837834)
   * debian/gtkp

Bug#844213: pyelliptic: FTBFS: AttributeError: /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1: undefined symbol: ECDH_OpenSSL

[Chris Lamb]

Source: pyelliptic
Version: 1.5.7-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,

pyelliptic fails to build from source in unstable/amd64:

  […]

 dh_auto_test -O--buildsystem=pybuild
  I: pybuild base:184: cd 
/home/lamby/temp/cdt.20161113133613.EaqJ9PdLlW.db.pyelliptic/pyelliptic-1.5.7/.pybuild/pythonX.Y_2.7/build;
 python2.7 -m unittest discover -v 
  
  --
  Ran 0 tests in 0.000s
  
  OK
  I: pybuild base:184: cd 
/home/lamby/temp/cdt.20161113133613.EaqJ9PdLlW.db.pyelliptic/pyelliptic-1.5.7/.pybuild/pythonX.Y_3.5/build;
 python3.5 -m unittest discover -v 
  pyelliptic (unittest.loader._FailedTest) ... ERROR
  
  ==
  ERROR: pyelliptic (unittest.loader._FailedTest)
  --
  ImportError: Failed to import test module: pyelliptic
  Traceback (most recent call last):
File "/usr/lib/python3.5/unittest/loader.py", line 462, in _find_test_path
  package = self._get_module_from_name(name)
File "/usr/lib/python3.5/unittest/loader.py", line 369, in 
_get_module_from_name
  __import__(name)
File 
"/home/lamby/temp/cdt.20161113133613.EaqJ9PdLlW.db.pyelliptic/pyelliptic-1.5.7/.pybuild/pythonX.Y_3.5/build/pyelliptic/__init__.py",
 line 43, in 
  from .openssl import OpenSSL
File 
"/home/lamby/temp/cdt.20161113133613.EaqJ9PdLlW.db.pyelliptic/pyelliptic-1.5.7/.pybuild/pythonX.Y_3.5/build/pyelliptic/openssl.py",
 line 528, in 
  OpenSSL = _OpenSSL(libname)
File 
"/home/lamby/temp/cdt.20161113133613.EaqJ9PdLlW.db.pyelliptic/pyelliptic-1.5.7/.pybuild/pythonX.Y_3.5/build/pyelliptic/openssl.py",
 line 180, in __init__
  self.ECDH_OpenSSL = self._lib.ECDH_OpenSSL
File "/usr/lib/python3.5/ctypes/__init__.py", line 360, in __getattr__
  func = self.__getitem__(name)
File "/usr/lib/python3.5/ctypes/__init__.py", line 365, in __getitem__
  func = self._FuncPtr((name_or_ordinal, self))
  AttributeError: /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1: undefined symbol: 
ECDH_OpenSSL
  
  
  --
  Ran 1 test in 0.000s
  
  FAILED (errors=1)
  E: pybuild pybuild:276: test: plugin distutils failed with: exit code=1: cd 
/home/lamby/temp/cdt.20161113133613.EaqJ9PdLlW.db.pyelliptic/pyelliptic-1.5.7/.pybuild/pythonX.Y_3.5/build;
 python3.5 -m unittest discover -v 
  dh_auto_test: pybuild --test -i python{version} -p 3.5 returned exit code 13
  debian/rules:5: recipe for target 'build' failed
  make: *** [build] Error 25

  […]

The full build log is attached.


Regards,

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


pyelliptic.1.5.7-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#844205: [Filesystems-devel] Bug#844205: aufs-dkms: I can't load the kernel module after upgrade from Jessie to Stretch.

[Jan Luca Naumann]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hey,

1. In the Debian archive there can be only one version of a package at
one time so there will be always only the version compatible to the
current kernel version. The upgrades are needed since there are new
development in the module and changes in the kernel interfaces.
Normally the linux kernel should be already be 4.8. in testing, too,
but it seems that there are problems with the package so the aufs was
unfortunately faster in testing.

2. There is a snapshot of the version 4.7+20160912-2:
http://snapshot.debian.org/package/aufs/4.7%2B20160912-2/

Jan

Am 13.11.2016 um 14:06 schrieb Leo:
> Hi Jan, thanks a lot for your response! :)
> 
> 2016-11-13 13:34 GMT+01:00 Jan Luca Naumann
> mailto:j.naum...@fu-berlin.de>>:
> 
> The current version is packaged for the current unstable kernel,
> the problem in this case is that the kernel 4.8 is not migrated to
> testing yet. Please wait for the migration (see 
> https://tracker.debian.org/pkg/linux 
>  ) and upgrade then to the
> kernel 4.8, then the module should be available.
> 
> 
> I suspected that the problem was this one.. XD
> 
> I don't know exactly how the process "unstable -> testing" works,
> but I'd like to make some question:
> 
> 1. why the aufs was upgraded before the kernel? Was the version
> for kernel 4.7 broken?
> 
> 2. It's possible to be able to find in the repository also the
> previous version (for 4.7)? In order to be able to install the
> correct version for the kernel currently available in repository.
> 
> What do you think? Thanks again for your help.
> 
> Best regards, Leonardo Rossi
> 
> 
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCgAGBQJYKGxHAAoJEH4R1/EZ+XG7YBAQAKnIFCC8vGCuVchZcpYakItu
lKYfDz88L1QxunrSyYXAgxl0GsBWZGsG/QBog56Z730EQyPwqn5KkwUNSyTm2Zv8
O1T4anwXKq2hJR92oBnzLtg3+/fOdacdZpwgTXuMjHHw5d50xcAJdfVGPnDBgiq6
YLV8nRzmNResPIXyX5v4/xS/R+tvqY3wSt4hDryRLVuuHgnpMgAeZI9GB29armQY
akjwtlt5SAbmXaUa3pcXCAUTD8UFGftQVTI5MDrgwZjBL5wjrPYxpP5ZCK1UHTU9
HuqgCWme6eCcLXLLWyDBQBWW0syqg+nzgcA1MFO8Sh3oPK+8+tZGo/j2d958UmZN
UPbH7ga6VscjQom75GdImbDhPXXAYsX7+NaSStbhE2agFAauEVG+vnxKeI5jgWw8
pn8CGcK6yFDy0CR4xFH0iWRxXCDlwj1urf7BLpeokWzoyGhqaa4E9Rc2Fm6cRof3
oxKVpssLeFZmd8XsYOIblXHP4fGDwoxF1vcWKvGq5ymTPXmFNINzJQgvfL3l7R0b
qoTtysp5caOzKVVSpHnhocAleFc1d3T+BP8WaNfo8E8rMw3zDvuWdHYcVslXfNa7
XI3mZCiWmawcRVMaXNzno/MkuXeTHrTQ0K+EYFpO7CaU6mg2W40Q5AKTnaWzxAx/
wzotDax8VH6JshoI5dtH
=pnWF
-END PGP SIGNATURE-

Bug#828601: wpa: FTBFS with openssl 1.1.0

[Julian Wollrath]

Hi,

I cannot do it myself but since the openssl transistion is ongoing now,
maybe the wpa version from experimental, which fixes this bug, should
be uploaded to unstable?

Cheers,
Julian
-- 
 ()  ascii ribbon campaign - against html e-mail 
 /\- against proprietary attachments

Bug#844214: Fails to start: libgif.so.4: cannot open shared object file: No such file or directory

[Kartik Mistry]

Package: fontforge
Version: 1:20161005~dfsg-4
Severity: serious

~/ fontforge
fontforge: error while loading shared libraries: libgif.so.4: cannot open 
shared object file: No such file or directory

I guess fontforge need to rebuild against new libgif.

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

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

Versions of packages fontforge depends on:
ii  fontforge-common  1:20161005~dfsg-4
ii  libc6 2.24-5
ii  libfontforge2 1:20161005~dfsg-4
ii  libgdraw5 1:20161005~dfsg-4
ii  libltdl7  2.4.6-2
ii  libx11-6  2:1.6.3-1

fontforge recommends no packages.

Versions of packages fontforge suggests:
pn  autotrace 
pn  fontforge-doc 
pn  fontforge-extras  
pn  potrace   
ii  python-fontforge  1:20161005~dfsg-4

-- no debconf information

-- 
Kartik Mistry | IRC: kart_
{0x1f1f, kartikm}.wordpress.com


signature.asc
Description: PGP signature

Bug#843988: Processed: Also affects the version in testing

[gregor herrmann]

On Sun, 13 Nov 2016 08:27:03 +, Debian Bug Tracking System wrote:

> > found 843988 3:5.36-1
> Bug #843988 [stunnel4] stunnel4 segfaults (client mode)
> Marked as found in versions stunnel4/3:5.36-1.

Hm? For me stunnel4/3:5.36-1 works fine.

Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature

Bug#843988: Processed: Also affects the version in testing

[Adrian Bunk]

On Sun, Nov 13, 2016 at 02:48:10PM +0100, gregor herrmann wrote:
> On Sun, 13 Nov 2016 08:27:03 +, Debian Bug Tracking System wrote:
> 
> > > found 843988 3:5.36-1
> > Bug #843988 [stunnel4] stunnel4 segfaults (client mode)
> > Marked as found in versions stunnel4/3:5.36-1.
> 
> Hm? For me stunnel4/3:5.36-1 works fine.

Sorry, I failed to explain this properly.

The 3:5.36-1 *binary* package is fine, but the problem is expected
to also be present in the 3:5.36-1 *source* package.

This issue must be fixed before the release of stretch,
shipping 3:5.36-1 as-is in stretch would be a timebomb
waiting to explode in a DSA.

> Cheers,
> gregor

cu
Adrian

-- 

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

Bug#843922: marked as done (stockfish: FTBFS: g++: error: unrecognized command line option '-m32')

[Debian Bug Tracking System]

Your message dated Sun, 13 Nov 2016 15:03:08 +0100
with message-id <87k2c7jx43@turtle.gmx.de>
and subject line Re: Bug#843922: stockfish: FTBFS: g++: error: unrecognized 
command line option '-m32'
has caused the Debian Bug report #843922,
regarding stockfish: FTBFS: g++: error: unrecognized command line option '-m32'
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.)


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

Your package fails to build on most architectures, because it calls g++
with the '-m32' option which is not generally supported.  Besides that,
the Config information looks very wrong on some architectures,
e.g. arm64[1], s390x[2] and mips64el[3] are apparently all wrongly
recognized as 32-bit architectures.

Could you please have a look?


1. 
https://buildd.debian.org/status/fetch.php?pkg=stockfish&arch=arm64&ver=8-1&stamp=1478719816
2. 
https://buildd.debian.org/status/fetch.php?pkg=stockfish&arch=s390x&ver=8-1&stamp=1478721845
3. 
https://buildd.debian.org/status/fetch.php?pkg=stockfish&arch=mips64el&ver=8-1&stamp=1478734250
--- End Message ---
--- Begin Message ---
Source: stockfish
Version: 8-3

On 2016-11-12 20:07 +0100, Milan Zamazal wrote:

>> "SJ" == Sven Joachim  writes:
>
> SJ> I haven't looked at the stockfish source, but I can imagine that
> SJ> this is not going to improve the situation on 32-bit arches.  If
> SJ> the config machinery cannot find out the pointer size by itself,
> SJ> dpkg-architecture provides DEB_HOST_ARCH_BITS for you.
>
> Thanks for the tip, applied.
>
> SJ> Inspecting the build system I found out that there is no config
> SJ> machinery, just a Makefile.  The attached patch fixes the
> SJ> problem for the usual build in Debian, although you might want
> SJ> to fix some other code paths as well (e.g. if someone builds
> SJ> with COMP=clang).
>
> Thanks for the patch, indeed, there's no need to use the option with (at
> least) g++.  Applied.

Thank you.  Since stockfish 8-3 has been built everywhere except on
alpha and sh4 where the buildds are lagging, I'm closing the bug. :-)

Cheers,
   Sven--- End Message ---

Bug#844205: [Filesystems-devel] Bug#844205: aufs-dkms: I can't load the kernel module after upgrade from Jessie to Stretch.

[Leo]

2016-11-13 14:36 GMT+01:00 Jan Luca Naumann :

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Hey,
>
> 1. In the Debian archive there can be only one version of a package at
> one time so there will be always only the version compatible to the
> current kernel version. The upgrades are needed since there are new
> development in the module and changes in the kernel interfaces.
> Normally the linux kernel should be already be 4.8. in testing, too,
> but it seems that there are problems with the package so the aufs was
> unfortunately faster in testing.
>

Other questions from a developer... because now I'm curious.. XD
How the "promotion" works?
Are you using some special software to pass packages from unstable to
testing?
Maybe exists a way to automatize some kind of "dependency check" before the
"promotion" to the testing repository.
Just to avoid this lack of consistency between modules and kernel.
Something that say:
"hey, aufs require kernel 4.8 and you have the 4.7. Please wait the kernel
upgrade"


>
> 2. There is a snapshot of the version 4.7+20160912-2:
> http://snapshot.debian.org/package/aufs/4.7%2B20160912-2/


Do you know if I can use apt-get build-dep to get this package version?


>
>
> Jan
>

Thanks again! :D
Leo






>
> Am 13.11.2016 um 14:06 schrieb Leo:
> > Hi Jan, thanks a lot for your response! :)
> >
> > 2016-11-13 13:34 GMT+01:00 Jan Luca Naumann
> > mailto:j.naum...@fu-berlin.de>>:
> >
> > The current version is packaged for the current unstable kernel,
> > the problem in this case is that the kernel 4.8 is not migrated to
> > testing yet. Please wait for the migration (see
> > https://tracker.debian.org/pkg/linux
> >  ) and upgrade then to the
> > kernel 4.8, then the module should be available.
> >
> >
> > I suspected that the problem was this one.. XD
> >
> > I don't know exactly how the process "unstable -> testing" works,
> > but I'd like to make some question:
> >
> > 1. why the aufs was upgraded before the kernel? Was the version
> > for kernel 4.7 broken?
> >
> > 2. It's possible to be able to find in the repository also the
> > previous version (for 4.7)? In order to be able to install the
> > correct version for the kernel currently available in repository.
> >
> > What do you think? Thanks again for your help.
> >
> > Best regards, Leonardo Rossi
> >
> >
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2
>
> iQIcBAEBCgAGBQJYKGxHAAoJEH4R1/EZ+XG7YBAQAKnIFCC8vGCuVchZcpYakItu
> lKYfDz88L1QxunrSyYXAgxl0GsBWZGsG/QBog56Z730EQyPwqn5KkwUNSyTm2Zv8
> O1T4anwXKq2hJR92oBnzLtg3+/fOdacdZpwgTXuMjHHw5d50xcAJdfVGPnDBgiq6
> YLV8nRzmNResPIXyX5v4/xS/R+tvqY3wSt4hDryRLVuuHgnpMgAeZI9GB29armQY
> akjwtlt5SAbmXaUa3pcXCAUTD8UFGftQVTI5MDrgwZjBL5wjrPYxpP5ZCK1UHTU9
> HuqgCWme6eCcLXLLWyDBQBWW0syqg+nzgcA1MFO8Sh3oPK+8+tZGo/j2d958UmZN
> UPbH7ga6VscjQom75GdImbDhPXXAYsX7+NaSStbhE2agFAauEVG+vnxKeI5jgWw8
> pn8CGcK6yFDy0CR4xFH0iWRxXCDlwj1urf7BLpeokWzoyGhqaa4E9Rc2Fm6cRof3
> oxKVpssLeFZmd8XsYOIblXHP4fGDwoxF1vcWKvGq5ymTPXmFNINzJQgvfL3l7R0b
> qoTtysp5caOzKVVSpHnhocAleFc1d3T+BP8WaNfo8E8rMw3zDvuWdHYcVslXfNa7
> XI3mZCiWmawcRVMaXNzno/MkuXeTHrTQ0K+EYFpO7CaU6mg2W40Q5AKTnaWzxAx/
> wzotDax8VH6JshoI5dtH
> =pnWF
> -END PGP SIGNATURE-
>

Bug#844214: [Pkg-fonts-devel] Bug#844214: Fails to start: libgif.so.4: cannot open shared object file: No such file or directory

[Vasudev Kamath]

Control: tag -1 + unreproducible moreinfo
Control: severity -1 important

Hi Karthik,

Kartik Mistry  writes:

> Package: fontforge
> Version: 1:20161005~dfsg-4
> Severity: serious
>
> ~/ fontforge
> fontforge: error while loading shared libraries: libgif.so.4: cannot open 
> shared object file: No such file or directory
>
> I guess fontforge need to rebuild against new libgif.

This is weird. Fontforge depends on libgif7 and hence it does not need
libgif.so.4 but needs libgif.so.7, below is ldd output of fontforge

> % ldd /usr/bin/fontforge | grep libgif
>libgif.so.7 => /usr/lib/i386-linux-gnu/libgif.so.7 (0xf68f8000)

I can not reproduce this issue and it also seems something is wrong in
your system, for now I've reduced severity to important. Can you please
check your system and provide more information on this?.

Best Regards


signature.asc
Description: PGP signature

Processed: Re: [Pkg-fonts-devel] Bug#844214: Fails to start: libgif.so.4: cannot open shared object file: No such file or directory

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + unreproducible moreinfo
Bug #844214 [fontforge] Fails to start: libgif.so.4: cannot open shared object 
file: No such file or directory
Added tag(s) moreinfo and unreproducible.
> severity -1 important
Bug #844214 [fontforge] Fails to start: libgif.so.4: cannot open shared object 
file: No such file or directory
Severity set to 'important' from 'serious'

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

Bug#840786: tagged as pending

[Dmitry Smirnov]

tag 840786 pending
--

We believe that the bug #840786 you reported has been fixed in the Git
repository. You can see the commit message below and/or inspect the
commit contents at:


http://anonscm.debian.org/cgit/collab-maint/mysql-workbench.git/diff/?id=6886fc0

(This message was generated automatically by
 'git-post-receive-tag-pending-commitmsg' hook).
---
commit 6886fc0
Author: Dmitry Smirnov 
Date:   Sun Nov 13 12:11:15 2016

Switch to "default-libmysqlclient-dev" (Closes: #840786, #841584)

Bug#841584: tagged as pending

[Dmitry Smirnov]

tag 841584 pending
--

We believe that the bug #841584 you reported has been fixed in the Git
repository. You can see the commit message below and/or inspect the
commit contents at:


http://anonscm.debian.org/cgit/collab-maint/mysql-workbench.git/diff/?id=6886fc0

(This message was generated automatically by
 'git-post-receive-tag-pending-commitmsg' hook).
---
commit 6886fc0
Author: Dmitry Smirnov 
Date:   Sun Nov 13 12:11:15 2016

Switch to "default-libmysqlclient-dev" (Closes: #840786, #841584)

Processed: Bug#840786 tagged as pending

[Debian Bug Tracking System]

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

> tag 840786 pending
Bug #840786 [src:mysql-workbench] mysql-workbench: Change libmysqlclient-dev 
build dependency to default-libmysqlclient-dev
Bug #841584 [src:mysql-workbench] mysql-workbench: FTBFS: build-dependency not 
installable: libmysqlclient-dev
Ignoring request to alter tags of bug #840786 to the same tags previously set
Ignoring request to alter tags of bug #841584 to the same tags previously set
> --
Stopping processing here.

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

Processed: Bug#841584 tagged as pending

[Debian Bug Tracking System]

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

> tag 841584 pending
Bug #841584 [src:mysql-workbench] mysql-workbench: FTBFS: build-dependency not 
installable: libmysqlclient-dev
Bug #840786 [src:mysql-workbench] mysql-workbench: Change libmysqlclient-dev 
build dependency to default-libmysqlclient-dev
Ignoring request to alter tags of bug #841584 to the same tags previously set
Ignoring request to alter tags of bug #840786 to the same tags previously set
> --
Stopping processing here.

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

Processed: tagging 828439

[Debian Bug Tracking System]

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

> tags 828439 + fixed-upstream
Bug #828439 {Done: Sergey Kirpichev } [src:monit] monit: 
FTBFS with openssl 1.1.0
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#828439: monit: FTBFS with openssl 1.1.0

[Kurt Roeckx]

This seems to have been fixed upstream.

It also seems like for some reason ssl support is disabled on
other arches than amd64 and i386.


Kurt

Bug#828439: monit: FTBFS with openssl 1.1.0

[Sergey B Kirpichev]

On Sun, Nov 13, 2016 at 03:43:29PM +0100, Kurt Roeckx wrote:
> This seems to have been fixed upstream.

Yes, this bug was closed by upstream.  Thank you for tagging.

BTW, it still FTBFS on i386.

> It also seems like for some reason ssl support is disabled on
> other arches than amd64 and i386.

On which one?

Here is mips:

++
| Monit has been configured with the following options:  |
||
|   Compression:  ENABLED|
|   PAM support:  ENABLED|
|   SSL support:  ENABLED|
|   Large files support:  ENABLED|
|   Optimized:DISABLED   |
|   Profiling:DISABLED   |
++

Same on i386 (look on the previous build for i386, for example).  Libmonit
config options are same too.

Bug#844220: exim4: fails to install: user mail was not found

[Holger Levsen]

Package: exim4
Version: 4.88~RC4-2
Severity: serious
Justification: package fails to install

Hi,

seen in unstable since today, eg found via 
https://jenkins.debian.net/job/chroot-installation_sid_install_education-desktop-mate/734//console
 

Setting up exim4-config (4.88~RC4-2) ...
Adding system-user for exim (v4)
2016-11-13 05:30:11 Exim configuration error in line 682 of 
/var/lib/exim4/config.autogenerated.tmp:
  user mail was not found
Invalid new configfile /var/lib/exim4/config.autogenerated.tmp, not installing 
/var/lib/exim4/config.autogenerated.tmp to /var/lib/exim4/config.autogenerated
dpkg: error processing package exim4-config (--configure):
 subprocess installed post-installation script returned error exit status 1


-- 
cheers,
Holger


signature.asc
Description: Digital signature

Processed: Re: Debian Installer Stretch Alpha 8 release

[Debian Bug Tracking System]

Processing control commands:

> clone 843073 -1
Bug #843073 [dpkg-dev] dpkg-shlibdeps: broken on i386 with merged /usr
Bug 843073 cloned as bug 844221
> reassign -1 debootstrap 1.0.85
Bug #844221 [dpkg-dev] dpkg-shlibdeps: broken on i386 with merged /usr
Bug reassigned from package 'dpkg-dev' to 'debootstrap'.
No longer marked as found in versions dpkg/1.18.10.
Ignoring request to alter fixed versions of bug #844221 to the same values 
previously set
Bug #844221 [debootstrap] dpkg-shlibdeps: broken on i386 with merged /usr
Marked as found in versions debootstrap/1.0.85.
> retitle -1 debootstrap: Please revert merged-/usr by default as it breaks 
> builds
Bug #844221 [debootstrap] dpkg-shlibdeps: broken on i386 with merged /usr
Changed Bug title to 'debootstrap: Please revert merged-/usr by default as it 
breaks builds' from 'dpkg-shlibdeps: broken on i386 with merged /usr'.
> severity -1 serious
Bug #844221 [debootstrap] debootstrap: Please revert merged-/usr by default as 
it breaks builds
Severity set to 'serious' from 'important'
> affects -1 dpkg-dev
Bug #844221 [debootstrap] debootstrap: Please revert merged-/usr by default as 
it breaks builds
Added indication that 844221 affects dpkg-dev
> severity 843073 wishlist
Bug #843073 [dpkg-dev] dpkg-shlibdeps: broken on i386 with merged /usr
Severity set to 'wishlist' from 'important'
> block 810499 by 843073
Bug #810499 [usrmerge] usrmerge: Confuses dpkg-shlibdeps
810499 was not blocked by any bugs.
810499 was not blocking any bugs.
Added blocking bug(s) of 810499: 843073
> severity 810499 serious
Bug #810499 [usrmerge] usrmerge: Confuses dpkg-shlibdeps
Severity set to 'serious' from 'important'
> affects 810499 dpkg-dev
Bug #810499 [usrmerge] usrmerge: Confuses dpkg-shlibdeps
Added indication that 810499 affects dpkg-dev

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

Bug#761853: marked as done (knockd: package 5 years out-of-date with upstream)

[Debian Bug Tracking System]

Your message dated Sun, 13 Nov 2016 15:50:15 +
with message-id 
and subject line Bug#761853: fixed in knockd 0.7-1
has caused the Debian Bug report #761853,
regarding knockd: package 5 years out-of-date with upstream
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.)


-- 
761853: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761853
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: knockd
Version: 0.5-3
Severity: important

Dear Maintainer,

There is a new upstream version dated 2014-06-29.

http://www.zeroflux.org/projects/knock

I'd recommend adding a debian/watch file to prevent this in the future.

The current Debian package doesn't work with systemd, and this is probably why.
In any case, the package should be updated.

X

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

Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages knockd depends on:
ii  libc6   2.19-10
ii  libpcap0.8  1.6.1-1
ii  logrotate   3.8.7-1

knockd recommends no packages.

knockd suggests no packages.

-- Configuration Files:
/etc/default/knockd changed [not included]
/etc/knockd.conf [Errno 13] Permission denied: u'/etc/knockd.conf'

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: knockd
Source-Version: 0.7-1

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

Debian distribution maintenance software
pp.
Leo Antunes  (supplier of updated knockd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 08 Oct 2016 16:05:00 +0200
Source: knockd
Binary: knockd
Architecture: source
Version: 0.7-1
Distribution: unstable
Urgency: medium
Maintainer: Leo Antunes 
Changed-By: Leo Antunes 
Description:
 knockd - small port-knock daemon
Closes: 308078 729663 761853 816388
Changes:
 knockd (0.7-1) unstable; urgency=medium
 .
   * [b2567e28] New upstream version 0.7 (closes: #761853)
 - adds timeout to pcap_open_live (closes: #816388, #308078)
   * [48f78ca5] bump policy to 3.9.8 (no changes)
   * [0b63eacb] update homepage url
   * [86381cd5] migrate to dh short notation
   * [4a38db8d] drop patches/include_limits_h: fixed upstream
   * [42ec7481] drop patches/manpage_cmd_timeout: fixed upstream
   * [733d82a7] switch to source/format 3.0 (quilt)
   * [bfc99c1f] add systemd support (closes: #729663)
   * [197eb24d] init: add dependency on $remote_fs
   * [848daeab] add hardening flags
   * [5c686b87] remove knock client docs from installation
   * [805dec71] debian/control: add VCS URL
   * [14a9bb3f] add watch file
Checksums-Sha1:
 8ac49de424083926283c0cd10296ef786732f4f7 1761 knockd_0.7-1.dsc
 186a687c9db11733cf23a7423884a863873ebb27 110791 knockd_0.7.orig.tar.gz
 6abcba77f783de5dae664a5e0714cd7bb9a70030 4748 knockd_0.7-1.debian.tar.xz
Checksums-Sha256:
 aaa8586237f964f77dfa29b6c1ebd22f54fe35ece771d33f972385123c105525 1761 
knockd_0.7-1.dsc
 9938479c321066424f74c61f6bee46dfd355a828263dc89561a1ece3f56578a4 110791 
knockd_0.7.orig.tar.gz
 aafa55fdbdea8562342c20c247ebe48815b33927926f239fd7fb0daf2bdce9c6 4748 
knockd_0.7-1.debian.tar.xz
Files:
 9681273ad55f451b714e13c5daed8e4b 1761 net optional knockd_0.7-1.dsc
 cb6373fd4ccb42eeca3ff406b7fdb8a7 110791 net optional knockd_0.7.orig.tar.gz
 de33bf9c53b19897180fce306c3b4d22 4748 net optional knockd_0.7-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJYKIO2AAoJEPNPCXROn13Z59wQAJV37zZBh2lgiLfAvEzu4U+F
VqA/80F6hW+1dZP0loMVQ1vp0sR1f/sLNUnkdQ/41XImKNOx2eQbFUNzqD/57RWx
Dt2Gd9wLodOW7k6m/+2C/D8ZBGakQY6Mi5a4RfLCpC8IcdPAE9PbaA8FslCad6jB
dZm4b7Swn3gq6AHZUkEA3HQkiOa17RdPgLXKLj5p+dT1YW41phnrG0nXJxel1fIG
zsgSicezJCwmAXxjDEVHH7SgQXLWejCpYXXuX+m4lgBOqAunmoTviObXtVDVxMp0
+pMyzLDqZgzBLdDZ2Vlm/yxUqyChjGuPxnumBGqGY5s7aW+kOs97EkQrke3icGsA
Xyz3PQJqquc+xin+RoKZF0cMjOjDCgkn7lE1N

Bug#830984: fixed in ball 1.4.3~beta1-2 -- only on amd64

[Danny Edel]

Control: reopen -1

On Sun, 13 Nov 2016 09:18:53 + Danny Edel  wrote:
> We believe that the bug you reported is fixed in the latest version of
> ball, which is due to be installed in the Debian FTP archive.

Hello Andreas, hello Steffen,

it seems like the fixes were indeed only effective on amd64, so I am
reopening the FTBFS/test-suite bug.  Also, I removed the other bugs from
CC, so you don't get each mail 4 times : )

From what I can tell, the testsuite failures fall into two categories:

1.  Most likely completely harmless, -- 0.01 difference in a
floating-point calculation.  The PoseClustering_test seems to be
involved in this on a few arches, where it compares a string rendering
(letter-by-letter) instead of using a fuzzy-compare of the values.

  * arm64
  * ppc64el

2.  Something is really broken and needs debugging on the appropriate
hardware.  Segfaults, integer mismatches (8 != 0), really weird output,
etc...

  * i386
  * s390x
  * kfreebsd-amd64
  * kfreebsd-i386
  * powerpc
  * x32

[at the time of writing, not all arches had finished/failed]

In the case of kfreebsd, the source will likely need patches for the
different kernel, since Sysinfo_test fails with statements like:

TEST_EQUAL(getTotalMemory() > 0, true): got 0, expected 1)

I fear that the tests are likely to keep failing on non-amd64
architectures until someone with access to a corresponding box puts in
the effort to investigate, and adjust the tests for the subtle differences.

Until then, I propose to run, but ignore the return code, of the
testsuite on "anything other than linux-amd64" for now, to have a chance
of re-entry into stretch.

Rationale behind running anyway:  We can load the logfile and grep for
'*Failed' to keep track of the problematic tests.  This string also
works great with the web interface and the ctrl+f feature of most browsers.

Rationale behind ignoring right now:  I assume that the vast majority of
users run amd64 (popcon backs me on this), and those would benefit from
seeing the package in stretch.  Even on the now-FTBFS arches, the
(comprehensive) testsuite suggests that 99% of the library is working as
intended, which should qualify the problem as important, but not
release-critical in my opinion.

If (!) there is a userbase of BALL on Debian-but-non-amd64/non-linux,
there is also the hope one of them will step up and provide assistance
in tracking this down or confirming the actual impact, which is a lot
easier if the package is available as a binary.

What is your opinion?

Danny

-- 

PS:  I submitted a basic travis-ci configuration to upstream for review.
 If it gets accepted, I can work from there to approach the
'will-it-build-on-jessie/stretch/sid/xenial' question.



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#830984: fixed in ball 1.4.3~beta1-2 -- only on amd64

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #830984 {Done: Danny Edel } [src:ball] ball: FTBFS: 
test suite errors
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions ball/1.4.3~beta1-2.

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

Bug#843967: marked as done (asyncpg: FTBFS in some locales)

[Debian Bug Tracking System]

Your message dated Sun, 13 Nov 2016 16:03:44 +
with message-id 
and subject line Bug#843967: fixed in asyncpg 0.6.3-2
has caused the Debian Bug report #843967,
regarding asyncpg: FTBFS in some locales
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.)


-- 
843967: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843967
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: asyncpg
Version: 2.54+dfsg-7
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

Hi,

Due to the way asyncpg parses the output pg_ctl, it will FTBFS in some
locales.

Note the "pg_ctl : le serveur est en cours d'exécution (PID : 9286)".

==
ERROR: test_cancellation_01 (test_cancellation.TestCancellation)
--
Traceback (most recent call last):
  File 
"/build/asyncpg-0.6.3/2nd/.pybuild/pythonX.Y_3.5/build/asyncpg/_testbase.py", 
line 146, in setUp
self.cluster.connect(database='postgres', loop=self.loop, **opts))
  File "/usr/lib/python3.5/asyncio/base_events.py", line 446, in 
run_until_complete
return future.result()
  File "/usr/lib/python3.5/asyncio/futures.py", line 292, in result
raise self._exception
  File "/usr/lib/python3.5/asyncio/tasks.py", line 239, in _step
result = coro.send(None)
  File 
"/build/asyncpg-0.6.3/2nd/.pybuild/pythonX.Y_3.5/build/asyncpg/cluster.py", 
line 125, in connect
conn_info = self.get_connection_spec()
  File 
"/build/asyncpg-0.6.3/2nd/.pybuild/pythonX.Y_3.5/build/asyncpg/cluster.py", 
line 258, in get_connection_spec
status = self.get_status()
  File 
"/build/asyncpg-0.6.3/2nd/.pybuild/pythonX.Y_3.5/build/asyncpg/cluster.py", 
line 116, in get_status
stdout.decode()))
asyncpg.cluster.ClusterError: could not parse pg_ctl status output: pg_ctl : le 
serveur est en cours d'exécution (PID : 9286)
/usr/lib/postgresql/9.6/bin/postgres "-D" "/tmp/tmpyoj88_xx" "--port=55514" 
"-c" "log_connections=on" "-c" "unix_socket_directories=/tmp"

The full build log is available here:

  https://gist.githubusercontent.com/lamby/ed4b17384603a08fdb2b7686887be9d9/raw


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: asyncpg
Source-Version: 0.6.3-2

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

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

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

Debian distribution maintenance software
pp.
Piotr Ożarowski  (supplier of updated asyncpg 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, 13 Nov 2016 16:38:01 +0100
Source: asyncpg
Binary: python3-asyncpg
Architecture: source amd64
Version: 0.6.3-2
Distribution: unstable
Urgency: medium
Maintainer: Piotr Ożarowski 
Changed-By: Piotr Ożarowski 
Description:
 python3-asyncpg - asyncio PosgtreSQL driver
Closes: 843967
Changes:
 asyncpg (0.6.3-2) unstable; urgency=medium
 .
   * Fix parsing pg_ctl output in some locales (closes: 843967, thanks to Chris
 Lamb for the patch)
Checksums-Sha1:
 f39bd9cf0c2ebd0774bb25708d969e174af38073 2037 asyncpg_0.6.3-2.dsc
 b85c0aeaab09aececf16916bd1eec798428f0ccf 6152 asyncpg_0.6.3-2.debian.tar.xz
 0aecfba90a2d82af634e0be156459dc0984a6e16 6558 
asyncpg_0.6.3-2_20161113T154018z-170356a0.buildinfo
 86f2e842813bc1f6830fc9a8c70857e4a92f4cae 655992 
python3-asyncpg-dbgsym_0.6.3-2_amd64.deb
 e5846815df4560671a9258c836096cf5b527c802 237278 
python3-asyncpg_0.6.3-2_amd64.deb
Checksums-Sha256:
 ee78e95ec05c128480cf8a241287af20e8e2463bffb3ca555142027a7026bb82 2037 
asyncpg_0.6.3-2.dsc
 31add51877232a15d6cd69509b05a6f73c7316260ea10627bb5b27e7de206042 6152 
asyncpg_0.6.3-2.debian.tar.xz
 5acc965857498a1f27e0f9f1e3fcc5ecdf6c53ccf5737531409a0e6ef8c03a50 6558 
asyncpg_0.6.3-2_20161113T154018z-170356a0.buildinfo
 557740f1bbe3aed922fcd486ce28e92b37bb1e658ae18e22943bd0ed928a92fb 655992 
python3-asyncpg-db

Processed: Fixed upstream

[Debian Bug Tracking System]

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

> tags 837480 fixed-upstream
Bug #837480 [src:gb] gb: FTBFS with bindnow and PIE enabled
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#844227: FTBFS on mips*, ./.libs/libmutter-cogl.so: undefined reference to `eglQueryString'

[Michael Biebl]

Source: mutter
Version: 3.22.2-1
Severity: serious

The latest build of mutter failed on mips, mipsel and mips64el with

./.libs/libmutter-cogl.so: undefined reference to `eglQueryString'
./.libs/libmutter-cogl.so: undefined reference to `eglTerminate'
collect2: error: ld returned 1 exit status

This looks like a recent regression in either mutter or mesa,
mutter 3.22.1 built fine on those architectures.


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

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

-- no debconf information

Processed: closing 839328

[Debian Bug Tracking System]

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

> close 839328
Bug #839328 [src:ipxe] ipxe: FTBFS: --defsym:2: undefined symbol `obj_82540em' 
referenced in expression
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#844233: python-passlib: FTBFS with probability of 0.22% due to non-deterministic testsuite

[Chris Lamb]

Source: python-passlib
Version: 1.6.5-4
Severity: serious
Tags: ftbfs
User: reproducible-bui...@lists.alioth.debian.org
Usertags: randomess
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi,

Whilst working on the Reproducible Builds effort [0], we noticed
that python-passlib's testsuite will non-determinstically FTBFS:

==
FAIL: test_getrandstr (passlib.tests.test_utils.MiscTest)
--
Traceback (most recent call last):
  File "/build/python-passlib-1.6.5/2nd/passlib/tests/test_utils.py", line 129, 
in test_getrandstr
self.assertEqual(sorted(set(x)), [u('a'),u('b'),u('c')])
AssertionError: Lists differ: [u'a', u'b'] != [u'a', u'b', u'c']

Second list contains 1 additional elements.
First extra element 2:
u'c'

- [u'a', u'b']
+ [u'a', u'b', u'c']
?++

This is because of:

125 x = f(u('abc'), 16)
126 y = f(u('abc'), 16)
127 self.assertIsInstance(x, unicode)
128 self.assertNotEqual(x,y)
129 self.assertEqual(sorted(set(x)), [u('a'),u('b'),u('c')])

If the random string ``x`` doesn't contain a certain character, the
assertion will fail. By my quick calculation this will happen with a
probability of (2/3)^(16-1).

It will also FTBFS if it generates the exact same random string, but
that seems a little more unlikely.

 [0] https://reproducible-builds.org/


Regards,

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

Bug#844234: python-eventlet: FTBFS: AssertionError: Readers: Listener FdListener('read', 19, ,

[Chris Lamb]

Source: python-eventlet
Version: 0.19.0-4
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

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

  […]

  verify_hub_empty()
File 
"/home/lamby/temp/cdt.20161113161222.LQJZGBYT7o.db.python-eventlet/python-eventlet-0.19.0/tests/__init__.py",
 line 244, in verify_hub_empty
  ', '.join(map(format_listener, writers)), num_writers,
  AssertionError: Readers: Listener FdListener('read', 19, , ) for greenlet  with run callback None (1) Writers:  (0)
  
  ==
  ERROR: test_count (tests.zmq_test.TestQueueLock)
  --
  Traceback (most recent call last):
File 
"/home/lamby/temp/cdt.20161113161222.LQJZGBYT7o.db.python-eventlet/python-eventlet-0.19.0/tests/__init__.py",
 line 189, in tearDown
  verify_hub_empty()
File 
"/home/lamby/temp/cdt.20161113161222.LQJZGBYT7o.db.python-eventlet/python-eventlet-0.19.0/tests/__init__.py",
 line 244, in verify_hub_empty
  ', '.join(map(format_listener, writers)), num_writers,
  AssertionError: Readers: Listener FdListener('read', 19, , ) for greenlet  with run callback None (1) Writers:  (0)
  
  ==
  ERROR: test_errors (tests.zmq_test.TestQueueLock)
  --
  Traceback (most recent call last):
File 
"/home/lamby/temp/cdt.20161113161222.LQJZGBYT7o.db.python-eventlet/python-eventlet-0.19.0/tests/__init__.py",
 line 189, in tearDown
  verify_hub_empty()
File 
"/home/lamby/temp/cdt.20161113161222.LQJZGBYT7o.db.python-eventlet/python-eventlet-0.19.0/tests/__init__.py",
 line 244, in verify_hub_empty
  ', '.join(map(format_listener, writers)), num_writers,
  AssertionError: Readers: Listener FdListener('read', 19, , ) for greenlet  with run callback None (1) Writers:  (0)
  
  ==
  ERROR: test_nested_acquire (tests.zmq_test.TestQueueLock)
  --
  Traceback (most recent call last):
File 
"/home/lamby/temp/cdt.20161113161222.LQJZGBYT7o.db.python-eventlet/python-eventlet-0.19.0/tests/__init__.py",
 line 189, in tearDown
  verify_hub_empty()
File 
"/home/lamby/temp/cdt.20161113161222.LQJZGBYT7o.db.python-eventlet/python-eventlet-0.19.0/tests/__init__.py",
 line 244, in verify_hub_empty
  ', '.join(map(format_listener, writers)), num_writers,
  AssertionError: Readers: Listener FdListener('read', 19, , ) for greenlet  with run callback None (1) Writers:  (0)
  
  ==
  ERROR: test_queue_lock_order (tests.zmq_test.TestQueueLock)
  --
  Traceback (most recent call last):
File 
"/home/lamby/temp/cdt.20161113161222.LQJZGBYT7o.db.python-eventlet/python-eventlet-0.19.0/tests/__init__.py",
 line 189, in tearDown
  verify_hub_empty()
File 
"/home/lamby/temp/cdt.20161113161222.LQJZGBYT7o.db.python-eventlet/python-eventlet-0.19.0/tests/__init__.py",
 line 244, in verify_hub_empty
  ', '.join(map(format_listener, writers)), num_writers,
  AssertionError: Readers: Listener FdListener('read', 19, , ) for greenlet  with run callback None (1) Writers:  (0)
  
  ==
  ERROR: test_change_subscription (tests.zmq_test.TestUpstreamDownStream)
  --
  Traceback (most recent call last):
File 
"/home/lamby/temp/cdt.20161113161222.LQJZGBYT7o.db.python-eventlet/python-eventlet-0.19.0/tests/__init__.py",
 line 95, in wrapped
  return func(*a, **kw)
File 
"/home/lamby/temp/cdt.20161113161222.LQJZGBYT7o.db.python-eventlet/python-eventlet-0.19.0/tests/zmq_test.py",
 line 33, in tearDown
  super(TestUpstreamDownStream, self).tearDown()
File 
"/home/lamby/temp/cdt.20161113161222.LQJZGBYT7o.db.python-eventlet/python-eventlet-0.19.0/tests/__init__.py",
 line 189, in tearDown
  verify_hub_empty()
File 
"/home/lamby/temp/cdt.20161113161222.LQJZGBYT7o.db.python-eventlet/python-eventlet-0.19.0/tests/__init__.py",
 line 244, in verify_hub_empty
  ', '.join(map(format_listener, writers)), num_writers,
  AssertionError: Readers: Listener FdListener('read', 19, , ) for greenlet  with run callback None (1) Writers:  (0)
  
  ==
  ERROR: test_close_during_recv (tests.zmq_test.TestUpstreamDownStream)
  --
  Traceback (most recent 

Bug#843627: Give back mercurial for armhf

[Javi Merino]

Hi,

mercurial 4.0-1 failed to build on armhf because
test-largefiles-update.t failed[0].  I've tested it on a porterbox ten
times and I can't reproduce the error.  Can you please give it back
for armhf and see if it was a transient error in the testsuite?

gb mercurial_4.0-1 . armhf

[0] 
https://buildd.debian.org/status/fetch.php?pkg=mercurial&arch=armhf&ver=4.0-1&stamp=1478103982


signature.asc
Description: PGP signature

Bug#828439: monit: FTBFS with openssl 1.1.0

[Kurt Roeckx]

On Sun, Nov 13, 2016 at 06:08:00PM +0300, Sergey B Kirpichev wrote:
> On Sun, Nov 13, 2016 at 03:43:29PM +0100, Kurt Roeckx wrote:
> > This seems to have been fixed upstream.
> 
> Yes, this bug was closed by upstream.  Thank you for tagging.
> 
> BTW, it still FTBFS on i386.

That's because the configure script tries to look for a function
that's been turned into a define. For some reason it's only trying
to look for SSL_library_init() on i386. It doesn't seem to find
the library path on i386, while it does on others?

> > It also seems like for some reason ssl support is disabled on
> > other arches than amd64 and i386.
> 
> On which one?
>
> Here is mips:
> 
> ++
> | Monit has been configured with the following options:  |
> ||
> |   Compression:  ENABLED|
> |   PAM support:  ENABLED|
> |   SSL support:  ENABLED|
> |   Large files support:  ENABLED|
> |   Optimized:DISABLED   |
> |   Profiling:DISABLED   |
> ++

But it also says:
++
| Libmonit is configured as follows: |
||
|   Optimized:DISABLED   |
|   Profiling:DISABLED   |
|   Openssl:  DISABLED   |
|   Compression:  ENABLED|
++

And it seems to link to -lssl anyway.



Kurt

Bug#844227: Acknowledgement (FTBFS on mips*, ./.libs/libmutter-cogl.so: undefined reference to `eglQueryString')

[Michael Biebl]

Looking at the git log for mutter, I don't find any changes between
3.22.1 and 3.22.2 which look like it could be the cause for this build
failure.
So I suspect it's a change in mesa.

3.22.1-2 (from 2016-10-15) successfully built against mesa 12.0.3-1
3.22.2-1 failed to build [1] against 12.0.4-2

@mesa maintainers: any ideas?


[1]
https://buildd.debian.org/status/fetch.php?pkg=mutter&arch=mips&ver=3.22.2-1&stamp=1479018257
-- 
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#844220: exim4: fails to install: user mail was not found

[Marc Haber]

On Sun, Nov 13, 2016 at 03:11:32PM +, Holger Levsen wrote:
> Setting up exim4-config (4.88~RC4-2) ...
> Adding system-user for exim (v4)
> 2016-11-13 05:30:11 Exim configuration error in line 682 of 
> /var/lib/exim4/config.autogenerated.tmp:
>   user mail was not found

Can you please verify that the user mail is present on the system?

If it is present, please note this in this bug.

If it is not present, check the correctness of the essential package
base-passwd, which is responsible to keep the user mail present on all
Debian systems (and which packages can explicitly rely on). If
base-passwd is correct, and mail not present, check why the user is
not there.

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Bug#844235: python-ttystatus: FTBFS: ttystatus/fmt.py:31:1: E305 expected 2 blank lines after class or function definition, found 1

[Chris Lamb]

Source: python-ttystatus
Version: 0.32-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

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

  […]

  dh_auto_test: Compatibility levels before 9 are deprecated (level 7 in use)
make -j1 check
  make[1]: Entering directory 
'/home/lamby/temp/cdt.20161113161402.Z0p6ySqzbu.db.python-ttystatus/python-ttystatus-0.32'
  python -m CoverageTestRunner --ignore-missing-from=without-tests
  
  
  OK
  19 excluded statements
  9 excluded modules
  Time: 0.1 s
  rm -f .coverage
  pep8 ttystatus
  ttystatus/fmt.py:31:1: E305 expected 2 blank lines after class or function 
definition, found 1
  Makefile:5: recipe for target 'check' failed
  make[1]: *** [check] Error 1
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20161113161402.Z0p6ySqzbu.db.python-ttystatus/python-ttystatus-0.32'
  dh_auto_test: make -j1 check returned exit code 2
  debian/rules:3: recipe for target 'build' failed
  make: *** [build] Error 2

  […]

The full build log is attached.


Regards,

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


python-ttystatus.0.32-1.unstable.amd64.log.txt.gz
Description: Binary data

Processed: closing 828600, severity of 828600 is serious

[Debian Bug Tracking System]

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

> close 828600 3.3.6+dfsg-1
Bug #828600 [src:witty] witty: FTBFS with openssl 1.1.0
Marked as fixed in versions witty/3.3.6+dfsg-1.
Bug #828600 [src:witty] witty: FTBFS with openssl 1.1.0
Marked Bug as done
> # It's fixed, it appears to have been very difficult. Wishlist is the wrong 
> severity in any case.
> severity 828600 serious
Bug #828600 {Done: k...@roeckx.be (Kurt Roeckx)} [src:witty] witty: FTBFS with 
openssl 1.1.0
Severity set to 'serious' from 'wishlist'
> thanks
Stopping processing here.

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

Bug#841599: marked as done (xdrawchem: FTBFS: install: cannot create regular file '/usr/bin/xdrawchem': Permission denied)

[Debian Bug Tracking System]

Your message dated Sun, 13 Nov 2016 16:49:06 +
with message-id 
and subject line Bug#841599: fixed in xdrawchem 2.0-6
has caused the Debian Bug report #841599,
regarding xdrawchem: FTBFS: install: cannot create regular file 
'/usr/bin/xdrawchem': Permission denied
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.)


-- 
841599: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841599
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xdrawchem
Version: 2.0-5
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161021 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 '/<>'
> install -m 755 -p "bin/xdrawchem" "/usr/bin/xdrawchem"
> install: cannot create regular file '/usr/bin/xdrawchem': Permission denied
> Makefile:1899: recipe for target 'install_target' failed
> make[2]: [install_target] Error 1 (ignored)
> mkdir: cannot create directory '/usr/share/xdrawchem2/': Permission denied
> Makefile:1908: recipe for target 'install_ringdir' failed
> make[2]: *** [install_ringdir] Error 1

If the failure looks somehow time/timezone related:
Note that this rebuild was performed without the 'tzdata' package
installed in the chroot. tzdata used be (transitively) part of
build-essential, but it no longer is. If this package requires it to
build, it should be added to build-depends. For the release team's
opinion on this, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185

If the failure looks LSB-related:
similarly to tzdata, lsb-base is not installed in the build chroot.

The full build log is available from:
   http://aws-logs.debian.net/2016/10/21/xdrawchem_2.0-5_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Georges Khaznadar  (supplier of updated xdrawchem 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, 13 Nov 2016 17:15:51 +0100
Source: xdrawchem
Binary: xdrawchem
Architecture: source amd64
Version: 2.0-6
Distribution: unstable
Urgency: medium
Maintainer: Georges Khaznadar 
Changed-By: Georges Khaznadar 
Description:
 xdrawchem  - Chemical structures and reactions editor
Closes: 841599
Changes:
 xdrawchem (2.0-6) unstable; urgency=medium
 .
   * modified d/rules and created d/xdrawchem.install; Closes: #841599
Checksums-Sha1:
 33e56253b6d3df326c11868dc8e61a2099ac8ff9 1780 xdrawchem_2.0-6.dsc
 f6c50b44b591d7a7f0dcede0edb6a10860f00e4d 23280 xdrawchem_2.0-6.debian.tar.xz
 4ca27d578800b978711dd94c29ed74a6088dcd47 8303678 
xdrawchem-dbgsym_2.0-6_amd64.deb
 97ce592f8db1d3c0c4a9df3760d48a60e178 10183 
xdrawchem_2.0-6_20161113T162956z-05a91fd4.buildinfo
 92e439056401d9bc4c89852495426f395a621527 562160 xdrawchem_2.0-6_amd64.deb
Checksums-Sha256:
 5f76104fb6c6081a8dfaed3f5442e81d6c7346ec460e5a6e86927016964c23d1 1780 
xdrawchem_2.0-6.dsc
 995e308a3d3871a69ba4a33e1fdc2516e712cf9a3973c5ff1aa435be36ca1b66 23280 
xdrawchem_2.0-6.debian.tar.xz
 bc745fc0bce0f36033c766bc4b95312c604bd6a100f6b97163ca74cae04c37a2 8303678 
xdrawchem-dbgsym_2.0-6_amd64.deb
 0734a107912ec88ceff13c5a9719699ee4ecc6313cf9aaefafff0f81e0cf8fa7 10183 
xdrawchem_2.0-6_20161113T162956z-05a91fd4.buildinfo
 d5871a0a813914e4b2b4b96a660f97928f3357064ef72ccd66a4683105193191 562160 
xdrawchem_2.0-6_amd64.deb
Files:
 67e69b53aa2a98292ed584b1d2b0686a 1780 science optional xdrawchem_2.0-6.dsc
 c50fed87d666d7c50b4dd8017be3ce44 23280 science optional 
xdrawchem_2.0-6.debian.tar.xz
 d42e3e9

Bug#830984: fixed in ball 1.4.3~beta1-2 -- only on amd64

[Andreas Tille]

Hi Danny,

I fully agree that we should ignore test results on other than amd64
architecture.  Please let me know if you intend to implement the needed
change or whether you suggest that I should do so.

Kind regards

  Andreas.

On Sun, Nov 13, 2016 at 04:56:50PM +0100, Danny Edel wrote:
> Control: reopen -1
> 
> On Sun, 13 Nov 2016 09:18:53 + Danny Edel  wrote:
> > We believe that the bug you reported is fixed in the latest version of
> > ball, which is due to be installed in the Debian FTP archive.
> 
> Hello Andreas, hello Steffen,
> 
> it seems like the fixes were indeed only effective on amd64, so I am
> reopening the FTBFS/test-suite bug.  Also, I removed the other bugs from
> CC, so you don't get each mail 4 times : )
> 
> From what I can tell, the testsuite failures fall into two categories:
> 
> 1.  Most likely completely harmless, -- 0.01 difference in a
> floating-point calculation.  The PoseClustering_test seems to be
> involved in this on a few arches, where it compares a string rendering
> (letter-by-letter) instead of using a fuzzy-compare of the values.
> 
>   * arm64
>   * ppc64el
> 
> 2.  Something is really broken and needs debugging on the appropriate
> hardware.  Segfaults, integer mismatches (8 != 0), really weird output,
> etc...
> 
>   * i386
>   * s390x
>   * kfreebsd-amd64
>   * kfreebsd-i386
>   * powerpc
>   * x32
> 
> [at the time of writing, not all arches had finished/failed]
> 
> In the case of kfreebsd, the source will likely need patches for the
> different kernel, since Sysinfo_test fails with statements like:
> 
> TEST_EQUAL(getTotalMemory() > 0, true): got 0, expected 1)
> 
> I fear that the tests are likely to keep failing on non-amd64
> architectures until someone with access to a corresponding box puts in
> the effort to investigate, and adjust the tests for the subtle differences.
> 
> Until then, I propose to run, but ignore the return code, of the
> testsuite on "anything other than linux-amd64" for now, to have a chance
> of re-entry into stretch.
> 
> Rationale behind running anyway:  We can load the logfile and grep for
> '*Failed' to keep track of the problematic tests.  This string also
> works great with the web interface and the ctrl+f feature of most browsers.
> 
> Rationale behind ignoring right now:  I assume that the vast majority of
> users run amd64 (popcon backs me on this), and those would benefit from
> seeing the package in stretch.  Even on the now-FTBFS arches, the
> (comprehensive) testsuite suggests that 99% of the library is working as
> intended, which should qualify the problem as important, but not
> release-critical in my opinion.
> 
> If (!) there is a userbase of BALL on Debian-but-non-amd64/non-linux,
> there is also the hope one of them will step up and provide assistance
> in tracking this down or confirming the actual impact, which is a lot
> easier if the package is available as a binary.
> 
> What is your opinion?
> 
>   Danny
> 
> -- 
> 
> PS:  I submitted a basic travis-ci configuration to upstream for review.
>  If it gets accepted, I can work from there to approach the
> 'will-it-build-on-jessie/stretch/sid/xenial' question.
> 




-- 
http://fam-tille.de

Processed: Re: Bug#844233: python-passlib: FTBFS with probability of 0.22% due to non-deterministic testsuite

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 python-passlib: FTBFS with probability of 0.46% due to 
> non-deterministic testsuite
Bug #844233 [src:python-passlib] python-passlib: FTBFS with probability of 
0.22% due to non-deterministic testsuite
Changed Bug title to 'python-passlib: FTBFS with probability of 0.46% due to 
non-deterministic testsuite' from 'python-passlib: FTBFS with probability of 
0.22% due to non-deterministic testsuite'.

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

Processed: Re: Bug#844233: python-passlib: FTBFS with probability of 0.22% due to non-deterministic testsuite

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 python-passlib: FTBFS with probability of 0.46% due to 
> non-deterministic testsuite
Bug #844233 [src:python-passlib] python-passlib: FTBFS with probability of 
0.46% due to non-deterministic testsuite
Ignoring request to change the title of bug#844233 to the same title

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

Bug#844233: python-passlib: FTBFS with probability of 0.22% due to non-deterministic testsuite

[James Clarke]

Control: retitle -1 python-passlib: FTBFS with probability of 0.46% due to 
non-deterministic testsuite

On Sun, Nov 13, 2016 at 04:25:30PM +, Chris Lamb wrote:
> Whilst working on the Reproducible Builds effort [0], we noticed
> that python-passlib's testsuite will non-determinstically FTBFS:
>
> ==
> FAIL: test_getrandstr (passlib.tests.test_utils.MiscTest)
> --
> Traceback (most recent call last):
>   File "/build/python-passlib-1.6.5/2nd/passlib/tests/test_utils.py", line 
> 129, in test_getrandstr
> self.assertEqual(sorted(set(x)), [u('a'),u('b'),u('c')])
> AssertionError: Lists differ: [u'a', u'b'] != [u'a', u'b', u'c']
>
> Second list contains 1 additional elements.
> First extra element 2:
> u'c'
>
> - [u'a', u'b']
> + [u'a', u'b', u'c']
> ?++
>
> This is because of:
>
> 125 x = f(u('abc'), 16)
> 126 y = f(u('abc'), 16)
> 127 self.assertIsInstance(x, unicode)
> 128 self.assertNotEqual(x,y)
> 129 self.assertEqual(sorted(set(x)), [u('a'),u('b'),u('c')])
>
> If the random string ``x`` doesn't contain a certain character, the
> assertion will fail. By my quick calculation this will happen with a
> probability of (2/3)^(16-1).

I believe it's actually (3C2)*(2/3)^16 - (3C1)*(1/3)^16 ~= 0.46% (the
subtracted value is negligible).

> It will also FTBFS if it generates the exact same random string, but
> that seems a little more unlikely.

P = (1/3)^16 = 2.3e-8 or 0.023%, which isn't quite as absurdly small
as you might think.

Regards,
James

Processed: closing 828260

[Debian Bug Tracking System]

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

> close 828260
Bug #828260 [src:boost1.61] casablanca: FTBFS with openssl 1.1.0
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: closing 835804

[Debian Bug Tracking System]

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

> close 835804
Bug #835804 [src:boost1.61] websocketpp: FTBFS with openssl 1.1.0
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#844239: request-tracker4: FTBFS: t/web/gnupg-select-keys-on-update.t failure

[Niko Tyni]

Package: request-tracker4
Version: 4.2.13-3
Severity: serious

This package failed to build on the 'all' buildd:

  
https://buildd.debian.org/status/fetch.php?pkg=request-tracker4&arch=all&ver=4.2.13-3&stamp=1477439960

  #   Failed test 'problems with passphrase'
  #   at t/web/gnupg-select-keys-on-update.t line 40.
  # searched: "\x{0a}\x{0a}\x{0a}  
\x{0a}

Bug#828439: monit: FTBFS with openssl 1.1.0

[Sergey B Kirpichev]

On Sun, Nov 13, 2016 at 05:29:10PM +0100, Kurt Roeckx wrote:
> That's because the configure script tries to look for a function
> that's been turned into a define. For some reason it's only trying
> to look for SSL_library_init() on i386.

Could you suggest a more portable solution?

> It doesn't seem to find
> the library path on i386, while it does on others?

Yes.  Some non-release archs are failing by same reason.

> But it also says:
> ++
> | Libmonit is configured as follows: |
> ||
> |   Optimized:DISABLED   |
> |   Profiling:DISABLED   |
> |   Openssl:  DISABLED   |
> |   Compression:  ENABLED|
> ++
> 
> And it seems to link to -lssl anyway.

Yeah, but this diagnostic output is new (it appears first in this
release).  I believe, something is wrong with this report, but not with
ssl support itself.

Bug#844240: Intent to not ship squirrelmail with stretch

[Thijs Kinkhorst]

Package: squirrelmail
Severity: serious

SquirrelMail has been missing from Stretch for a while now and I intend
to leave it that way. This bug is to document this explicit choice (and
room for any concerns).

Upstream (of which I'm, at least on paper) part, has not made any new
release of SquirrelMail since 2011. There is some activity in commits
being done, but these do not result in releases.

I've tried to work around this temporarily by packaging a snapshot of
upstream svn, but I'm not happy with that since this is an arbitrary
point in development and not a clear and tested release which we should
ship and support for years. Popcon for squirrelmail is significant but
shows a steady decline since 2010.

Alternatives are availbale. There's the competing product roundcube
which is actively maintained in Debian and shows a steady popcon
increase. Another alternative is to install SquirrelMail from source
which is very easy and makes it easier to e.g. keep up with commits or
newer snapshots. The added value of a Debian package for squirrelmail is
hence not immense in my opinion.

Of course this is not to pass any judgement value or to try to
discourage others from working on this package. I welcome any thoughts
in this bug report, or interest in putting the work into a sustainable
Debian package of squirrelmail.


Cheers,
Thijs

Bug#844227: FTBFS on mips*, ./.libs/libmutter-cogl.so: undefined reference to `eglQueryString'

[Sven Joachim]

On 2016-11-13 17:14 +0100, Michael Biebl wrote:

> Source: mutter
> Version: 3.22.2-1
> Severity: serious
>
> The latest build of mutter failed on mips, mipsel and mips64el with
>
> ./.libs/libmutter-cogl.so: undefined reference to `eglQueryString'
> ./.libs/libmutter-cogl.so: undefined reference to `eglTerminate'
> collect2: error: ld returned 1 exit status
>
> This looks like a recent regression in either mutter or mesa,
> mutter 3.22.1 built fine on those architectures.

I had a look at the build log, and libmutter-cogl.so appears to have
been linked with -lEGL as it's supposed to.  Also, the two mentioned
symbols are still present in libEGL.so, so there's no obvious mesa
problem either.

The toolchain has also changed quite a bit in the past four weeks, with
gcc having pie enabled by default and binutils at a bleeding edge
snapshot.  Maybe one of those has triggered the build failure.

Cheers,
   Sven

Bug#828439: monit: FTBFS with openssl 1.1.0

[Kurt Roeckx]

On Sun, Nov 13, 2016 at 08:26:48PM +0300, Sergey B Kirpichev wrote:
> On Sun, Nov 13, 2016 at 05:29:10PM +0100, Kurt Roeckx wrote:
> > That's because the configure script tries to look for a function
> > that's been turned into a define. For some reason it's only trying
> > to look for SSL_library_init() on i386.
> 
> Could you suggest a more portable solution?

If you really want configure to detect something, write a real
program that includes the proper header file. That way
SSL_library_init() should still work even when we turned it into
a define.

An other solution is that you take an other function, like
SSL_new().


Kurt

Bug#830984: fixed in ball 1.4.3~beta1-2 -- only on amd64

[Danny Edel]

On 11/13/2016 05:55 PM, Andreas Tille wrote:
> Hi Danny,
> 
> I fully agree that we should ignore test results on other than amd64
> architecture.  Please let me know if you intend to implement the needed
> change or whether you suggest that I should do so.
> 
> Kind regards
> 
>   Andreas.
> 

Hello Andreas,

I have created and git-pushed a patch to debian/rules.  I did not update
the changelog, since it didn't look like the one uploaded to unstable
earlier today and I wanted to avoid a merge conflict on your side.

If you could review / edit changelog / upload, that would be nice.

A quick test on an i386 chroot with the build command replaced by
/bin/true suggests it does exactly what it's supposed to.  It ran the
test suite, ignored the inevitable error and issued a diagnostic.  It
even printed my warning multiple times : )  The computer will ignore it
of course, but it might prompt a human reader to get involved.

If the new revision actually builds, I would suggest we keep this bug
open (I wrote the bug number into d/rules) and downgrade its severity to
important.

I don't have the time right now to dig into the i386 issues in detail.
If that changes, I might un-dust my old Celeron-based laptop and let it
compile for a few days.  If it can actually run stretch/sid.  I remember
reading something on d-devel about raising the minimum processor
requirements for the i386 port…

Cheers,

Danny



signature.asc
Description: OpenPGP digital signature

Bug#844245: vym 2.5.0-2 crashes on opening a file

[Miguel Figueiredo]

Package: vym
Version: 2.5.0-2
Severity: grave

On clicking to open a file there's a segmentation fault with the 
following error message:


(vym:15604): Gdk-WARNING **: 
/build/gtk+3.0-3.22.3/./gdk/x11/gdkwindow-x11.c:5573 drawable is not a 
native X11 window

Segmentation fault

Best regards,

Miguel

Bug#828365: marked as done (kismet: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Sun, 13 Nov 2016 18:03:58 +
with message-id 
and subject line Bug#828365: fixed in kismet 2016.07.R1-1
has caused the Debian Bug report #828365,
regarding kismet: FTBFS with openssl 1.1.0
to be marked as done.

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

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


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

Hi,

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

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

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

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


Kurt
--- End Message ---
--- Begin Message ---
Source: kismet
Source-Version: 2016.07.R1-1

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

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

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

Debian distribution maintenance software
pp.
Nick Andrik  (supplier of updated kismet 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 Nov 2016 02:04:15 +0100
Source: kismet
Binary: kismet kismet-plugins
Architecture: source amd64
Version: 2016.07.R1-1
Distribution: sid
Urgency: medium
Maintainer: Nick Andrik 
Changed-By: Nick Andrik 
Description:
 kismet - wireless sniffer and monitor - core
 kismet-plugins - wireless sniffer and monitor - plugins
Closes: 819600 828365 835390
Changes:
 kismet (2016.07.R1-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #835390)
   * Po-debconf translations
 - Update Japanese translation (Closes: #819600)
   * debian/patches
 - Add openssl_1.1.0_port to make buildable with OpenSSL 1.1.0
   (Closes: #828365)
 - Update fix_typos in order to correct additional typos
 - Refresh existing patches
   * debian/control
 - Bump policy to 3.9.8
Checksums-Sha1:
 a7793d0b70c238420641afef7b09ac67cd6b9c07 2099 kismet_2016.07.R1-1.dsc
 ee81412d12c44ce9f951eda3e5442dfc9378ff18 709364 kismet_2016.07.R1.orig.tar.xz
 f4c3d4cb7bc6d2dd3f2e5ab3ca0594921bebad6c 32900 
kismet_2016.07.R1-1.debian.tar.xz
 80a00df0f8b0de63f58693d84e34a28fdfb2d795 17565244 
kismet-dbgsym_2016.07.R1-1_amd64.deb
 2f6c32add470d06cd62683018a39d254357e409c 2479892 
kismet-plugins-dbgsym_2016.07.R1-1_amd64.deb
 db3b355458174a693e8e9825946e3f7f28597a20 144644 
kismet-plugins_2016.07.R1-1_amd64.deb
 d8f3fce9115f8604c69513d5e6fc69b94ced6018 5794 
kismet_2016.07.R1-1_20161113T174937z-fdc6eb38.buildinfo
 dc26f8a7a03ccf5eeb2ef37360afb12ed4667da2 1190136 kismet_2016.07.R1-1_amd64.deb
Checksums-Sha256:
 82823543a731d1c816325bf6b7a3f069a61b2771d4a706b30d2e1f35e1cc4d2a 2099 
kismet_2016.07.R1-1.dsc
 bdb21f153311f1ff3b16621bf0d6740f66369bf0982b0a289c9a12af8847e237 709364 
kismet_2016.07.R1.orig.tar.xz
 f3c268aa09b9bd421e3bc0deb86cb57e02724f0dead740649828f8bf22685f57 32900 
kismet_2016.07.R1-1.debian.tar.xz
 886f93f4b09372b149802f6576bf5ec3f04eba1a266533eaa3af67748d6735cb 17565244 
kismet-dbgsym_2016.07.R1-1_amd64.deb
 c59b3e15e92b3dda1bf7449f6264e05b33cbbde23a6d4190ebfee65365919d71 2479892 
kismet-plugins-dbgsym_2016.07.R1-1_amd64.deb
 476c4d11637683ec4dfc3f229c726aace14ab4f31a54a947ef27107e2670b219 144644 
kismet-plugins_2016.07.R1-1_amd64.deb
 4828c12805abcedf440f06696d8fb7dd8f50140871d827d46f84344216a0d8ff 5794 
kismet_2016.07.R1-1_20161113T174937z-fdc6eb38.buildinfo
 a89221cb022fcb49832783f04ecdb319ceb0e30ba00033f910b15671176b4632 1190136 
kismet_2016.07.R1-1_amd64.deb
Files:
 3b30888f5b16a2252d0c5723f0f6bac7 2099 net optional kismet_2016.07.R1-1.dsc
 7fa6e86c5078a0e7d91fc9bf954c5107 709364 net o

Bug#841592: [debian-mysql] Bug#841592: Bug#841592: mysql-5.7: FTBFS: Tests failures

[Lucas Nussbaum]

On 09/11/16 at 07:27 -0800, Lars Tangvald wrote:
> 
> - lu...@debian.org wrote:
> 
> >  
> > Hi,
> > 
> > I don't think that my test is run as root. So it might be something
> > else...
> > 
> > Lucas
> 
> The error message is access denied for 'root'@'localhost', but the test 
> itself tries to log in as the current system user (it's supposed to be blank, 
> but that's not working right), so it does seem to be running as root. 
> However, if I try a full sbuild as root, there are some other tests that will 
> fail too, so it doesn't seem like the test suite in general is running as 
> root.
> 
> I've made a patch that should fix the test to actually specify a blank user. 
> Are you able to test your build with the head of 
> https://anonscm.debian.org/cgit/pkg-mysql/mysql.git/log/?h=mysql-5.7/ltangvald
>  ?
> It's the same as the 5.7.16 uploaded to unstable, just with that one extra 
> commit.

Hi,

I can confirm that it does not fix the problem; sorry.

Lucas

Bug#844208: marked as done (qemu-system-sparc: Needed openbios-sparc not available in jessie-backports)

[Debian Bug Tracking System]

Your message dated Sun, 13 Nov 2016 21:16:43 +0300
with message-id <263eef6b-ca98-4e71-3727-3e70a2d45...@msgid.tls.msk.ru>
and subject line Re: Bug#844208: qemu-system-sparc: Needed openbios-sparc not 
available in jessie-backports
has caused the Debian Bug report #844208,
regarding qemu-system-sparc: Needed openbios-sparc not available in 
jessie-backports
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.)


-- 
844208: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844208
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qemu-system-sparc
Version: 1:2.6+dfsg-3.1~bpo8+1
Severity: grave
Tags: newcomer
Justification: renders package unusable

Dear Maintainer,

if openbios-sparc is not available in jessie-backports. So only the release
from jessie could be used.
But the acutal jessie-backports openbios-sparc needs openbios-sparc >=
1.1+svn1395-1~.

root@host:/etc/apt# apt-get install qemu-system-sparc
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 qemu-system-sparc : Depends: openbios-sparc (>= 1.1+svn1395-1~) but
1.1+svn1306-2 is to be installed
E: Unable to correct problems, you have held broken packages.

root@nihilnihil:/etc/apt# apt-cache policy qemu-system-sparc openbios-sparc
qemu-system-sparc:
  Installed: 1:2.6+dfsg-3.1~bpo8+1
  Candidate: 1:2.7+dfsg-3~bpo8+2
  Version table:
 1:2.7+dfsg-3~bpo8+2 0
600 http://ftp.de.debian.org/debian/ jessie-backports/main amd64
Packages
 *** 1:2.6+dfsg-3.1~bpo8+1 0
100 /var/lib/dpkg/status
 1:2.1+dfsg-12+deb8u6 0
500 http://ftp.de.debian.org/debian/ jessie/main amd64 Packages
500 http://security.debian.org/ jessie/updates/main amd64 Packages
openbios-sparc:
  Installed: 1.1+svn1306-2
  Candidate: 1.1+svn1306-2
  Version table:
 *** 1.1+svn1306-2 0
500 http://ftp.de.debian.org/debian/ jessie/main amd64 Packages
100 /var/lib/dpkg/status
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Pierre Bernhardt 
To: Debian Bug Tracking System 
Subject: qemu-system-sparc: Needed openbios-sparc not available in 
jessie-backports
Bcc: Pierre Bernhardt 

So also the upgrade fails.



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

Kernel: Linux 4.7.0-0.bpo.1-amd64 (SMP w/6 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages qemu-system-sparc depends on:
ii  libaio1 0.3.110-1
ii  libasound2  1.0.28-1
ii  libbluetooth3   5.23-2+b1
ii  libbrlapi0.65.3.1-1~bpo8+1
ii  libc6   2.19-18+deb8u6
ii  libcacard0  1:2.5.0-2~bpo8+1
ii  libfdt1 1.4.0+dfsg-2~bpo8+1
ii  libgcc1 1:4.9.2-10
ii  libglib2.0-02.48.0-1~bpo8+1
ii  libgnutls-deb0-28   3.3.8-6+deb8u3
ii  libjpeg62-turbo 1:1.3.1-12
ii  libncurses5 5.9+20140913-1+b1
ii  libnettle4  2.7.1-5+deb8u1
ii  libpixman-1-0   0.32.6-3
ii  libpng12-0  1.2.50-2+deb8u2
ii  libpulse0   7.1-2~bpo8+1
ii  libsasl2-2  2.1.26.dfsg1-13+deb8u1
ii  libsdl1.2debian 1.2.15-10+b1
ii  libseccomp2 2.2.3-3~bpo8+1
ii  libspice-server10.12.5-1+deb8u3
ii  libtinfo5   5.9+20140913-1+b1
ii  libusb-1.0-02:1.0.19-1
ii  libusbredirparser1  0.7-1
ii  libuuid12.25.2-6
ii  libvdeplug2 2.3.2+r586-1
ii  libx11-62:1.6.2-3
ii  libxen-4.4  4.4.1-9+deb8u7
ii  libxenstore3.0  4.4.1-9+deb8u7
ii  openbios-sparc  1.1+svn1306-2
ii  qemu-system-common  1:2.7+dfsg-3~bpo8+2
ii  zlib1g  1:1.2.8.dfsg-2+b1

Versions of packages qemu-system-sparc recommends:
ii  ipxe-qemu   1.0.0+git-20141004.86285d1-1
ii  qemu-utils  1:2.7+dfsg-3~bpo8+2
ii  seabios 1.7.5-1

Versions of packages qemu-system-sparc suggests:
pn  qemu-block-extra  
ii  samba 2:4.2.10+dfsg-0+deb8u3
pn  vde2  

-- no debconf information
--- End Message ---
--- Begin Message ---
13.11.2016 14:12, Pierre Bernhardt wrote:
> Package: qemu-system-sparc
> V

Bug#841558: marked as done (node-tap: FTBFS: help2man: can't get `--help' info from bin/tap.js)

[Debian Bug Tracking System]

Your message dated Sun, 13 Nov 2016 18:34:08 +
with message-id 
and subject line Bug#841558: fixed in node-tap 8.0.0-1
has caused the Debian Bug report #841558,
regarding node-tap: FTBFS: help2man: can't get `--help' info from bin/tap.js
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.)


-- 
841558: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841558
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-tap
Version: 0.7.1-1.1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161021 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):
>  debian/rules build
> dh build
>dh_testdir
>dh_update_autotools_config
>dh_auto_configure
>debian/rules override_dh_auto_build
> make[1]: Entering directory '/<>'
> help2man -N -n "Test-Anything-Protocol module for Node.js" bin/tap.js -o 
> "debian/tap.1"
> help2man: can't get `--help' info from bin/tap.js
> Try `--no-discard-stderr' if option outputs to stderr
> debian/rules:20: recipe for target 'debian/tap.1' failed
> make[1]: *** [debian/tap.1] Error 1

If the failure looks somehow time/timezone related:
Note that this rebuild was performed without the 'tzdata' package
installed in the chroot. tzdata used be (transitively) part of
build-essential, but it no longer is. If this package requires it to
build, it should be added to build-depends. For the release team's
opinion on this, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185

If the failure looks LSB-related:
similarly to tzdata, lsb-base is not installed in the build chroot.

The full build log is available from:
   http://aws-logs.debian.net/2016/10/21/node-tap_0.7.1-1.1_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Jérémy Lal  (supplier of updated node-tap 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, 13 Nov 2016 19:13:51 +0100
Source: node-tap
Binary: node-tap
Architecture: source all
Version: 8.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Jérémy Lal 
Description:
 node-tap   - Test-Anything-Protocol module for Node.js
Closes: 841558
Changes:
 node-tap (8.0.0-1) unstable; urgency=medium
 .
   * New upstream version 8.0.0
   * Secure Vcs url
   * Standards-Version 3.9.8
   * Copyright: Expat to ISC
   * Copyright for foreground-child
   * Bundle modules from tapjs as patches:
 + foreground-child
 + tap-mocha-reporter
 + clean-yaml-object
 + stack-utils
 + buffer-to-string
   * Remove the need for unavailable dependencies:
 + only-shallow
 + deeper
 + color-support
 + os-homedir
 + bluebird
   * Postpone the need for unavailable dependencies, and Suggests them:
 + coveralls
 + nyc
 + opener
   * Build-Depends: keep only what's needed to get help2man running
   * Fix help2man call (Closes: #841558)
   * Enable test suite in autopkgtest
   * Patch tests for nodejs rename and disable some tests
Checksums-Sha1:
 80f2b1d44502f7e81835fd89553dd70703af0104 2104 node-tap_8.0.0-1.dsc
 0ccca6b628c933c3407504c06159d7e5f2ef29f6 66244 node-tap_8.0.0.orig.tar.gz
 65232669727792673df0abf3d4f711b67ef60b50 28636 node-tap_8.0.0-1.debian.tar.xz
 7443bb88743ed13d26e4504884b9654eb893123d 5089 
node-tap_8.0.0-1_20161113T181443z-19ea63a5.buildinfo
 c0f0a6e82cd3834551fecd6c44530a864ef2f555 43812 node-tap_8.0.0-1_all.deb
Checksums-Sha256:
 057323e42898e12a57

Bug#844227: FTBFS on mips*, ./.libs/libmutter-cogl.so: undefined reference to `eglQueryString'

[Michael Biebl]

Am 13.11.2016 um 18:37 schrieb Sven Joachim:
> The toolchain has also changed quite a bit in the past four weeks, with
> gcc having pie enabled by default and binutils at a bleeding edge
> snapshot.  Maybe one of those has triggered the build failure.

That might well be it. Currently mutter still builds fine in stretch.
The new binutils should migrate to testing soon.
I can then retry the build on a mips porter machine with
2.27.51.20161108-1

-- 
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#844220: exim4: fails to install: user mail was not found

[Holger Levsen]

On Sun, Nov 13, 2016 at 05:29:16PM +0100, Marc Haber wrote:
> On Sun, Nov 13, 2016 at 03:11:32PM +, Holger Levsen wrote:
> > Setting up exim4-config (4.88~RC4-2) ...
> > Adding system-user for exim (v4)
> > 2016-11-13 05:30:11 Exim configuration error in line 682 of 
> > /var/lib/exim4/config.autogenerated.tmp:
> >   user mail was not found
> Can you please verify that the user mail is present on the system?

It was a normal installation like jenkins has done since years, every
day… so basic debootstrap + apt-get install some packages.

(typing this in an airport and not likely to be able to further debug
this in the next 48h…)
 
> If it is present, please note this in this bug.
> 
> If it is not present, check the correctness of the essential package
> base-passwd, which is responsible to keep the user mail present on all
> Debian systems (and which packages can explicitly rely on). If
> base-passwd is correct, and mail not present, check why the user is
> not there.

cc:ing the base-passwd maintainer.


-- 
cheers,
Holger


signature.asc
Description: Digital signature

Bug#830984: fixed in ball 1.4.3~beta1-2 -- only on amd64

[Andreas Tille]

Hi Danny,

On Sun, Nov 13, 2016 at 07:01:15PM +0100, Danny Edel wrote:
> I have created and git-pushed a patch to debian/rules.  I did not update
> the changelog, since it didn't look like the one uploaded to unstable
> earlier today and I wanted to avoid a merge conflict on your side.

Shame on lazy me - pushed now.
 
> If you could review / edit changelog / upload, that would be nice.
> 
> A quick test on an i386 chroot with the build command replaced by
> /bin/true suggests it does exactly what it's supposed to.  It ran the
> test suite, ignored the inevitable error and issued a diagnostic.  It
> even printed my warning multiple times : )  The computer will ignore it
> of course, but it might prompt a human reader to get involved.

Sounds very sensible.
 
> If the new revision actually builds, I would suggest we keep this bug
> open (I wrote the bug number into d/rules) and downgrade its severity to
> important.

Well, we can do so, yes.
 
> I don't have the time right now to dig into the i386 issues in detail.
> If that changes, I might un-dust my old Celeron-based laptop and let it
> compile for a few days.  If it can actually run stretch/sid.  I remember
> reading something on d-devel about raising the minimum processor
> requirements for the i386 port…

If you want to do so for academic reasons nobody will stop you.
However, for practical cases this might not be very important research.

Kind regards

 Andreas.

-- 
http://fam-tille.de

Bug#838644: marked as pending

[Etienne Millon]

tag 838644 pending
thanks

Hello,

Bug #838644 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/guessit.git;a=commitdiff;h=970cd9b

---
commit 970cd9b25c6704cbaff9b2dbe2e9475234174481
Author: Etienne Millon 
Date:   Mon Nov 7 22:31:55 2016 +0100

Fix failing tests (Closes: #838644)

diff --git a/debian/changelog b/debian/changelog
index d57c2f6..6454317 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,6 +1,6 @@
 guessit (0.11.0-2) UNRELEASED; urgency=medium
 
-  * 
+  * Fix failing tests (Closes: #838644)
 
  -- Etienne Millon   Mon, 07 Nov 2016 22:30:58 +0100
 

Processed: Bug#838644 marked as pending

[Debian Bug Tracking System]

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

> tag 838644 pending
Bug #838644 [src:guessit] guessit: FTBFS (failing tests)
Added tag(s) pending.
> thanks
Stopping processing here.

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