Bug#815868: osmcoastline: FTBFS: protobuf_tags.hpp:36:35: fatal error: protozero/pbf_types.hpp: No such file or directory

[Chris Lamb]

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

Dear Maintainer,

osmcoastline fails to build from source in unstable/amd64:

  [..]

  [ 70%] Building CXX object 
src/CMakeFiles/osmcoastline.dir/output_database.cpp.o
  cd 
/home/lamby/temp/cdt.20160225074733.Dt35P9JqeR/osmcoastline-2.1.2/obj-x86_64-linux-gnu/src
 && /usr/bin/c++   -DOSMCOASTLINE_VERSION=\"2.1.2\" -D_FILE_OFFSET_BITS=64 
-D_LARGEFILE_SOURCE 
-I/home/lamby/temp/cdt.20160225074733.Dt35P9JqeR/osmcoastline-2.1.2/include 
-isystem /usr/include/gdal  -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2-std=c++11 -Wall 
-Wextra -pedantic -Wredundant-decls -Wdisabled-optimization -Wctor-dtor-privacy 
-Wnon-virtual-dtor -Woverloaded-virtual -Wsign-promo -Wold-style-cast -o 
CMakeFiles/osmcoastline.dir/output_database.cpp.o -c 
/home/lamby/temp/cdt.20160225074733.Dt35P9JqeR/osmcoastline-2.1.2/src/output_database.cpp
  In file included from /usr/include/osmium/io/detail/pbf_decoder.hpp:51:0,
   from /usr/include/osmium/io/detail/pbf_input_format.hpp:51,
   from /usr/include/osmium/io/pbf_input.hpp:46,
   from /usr/include/osmium/io/any_input.hpp:48,
   from 
/home/lamby/temp/cdt.20160225074733.Dt35P9JqeR/osmcoastline-2.1.2/src/osmcoastline_filter.cpp:27:
  /usr/include/osmium/io/detail/protobuf_tags.hpp:36:35: fatal error: 
protozero/pbf_types.hpp: No such file or directory
  compilation terminated.
  src/CMakeFiles/osmcoastline_filter.dir/build.make:65: recipe for target 
'src/CMakeFiles/osmcoastline_filter.dir/osmcoastline_filter.cpp.o' failed
  make[3]: *** 
[src/CMakeFiles/osmcoastline_filter.dir/osmcoastline_filter.cpp.o] Error 1
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160225074733.Dt35P9JqeR/osmcoastline-2.1.2/obj-x86_64-linux-gnu'
  CMakeFiles/Makefile2:168: recipe for target 
'src/CMakeFiles/osmcoastline_filter.dir/all' failed
  make[2]: *** [src/CMakeFiles/osmcoastline_filter.dir/all] Error 2
  make[2]: *** Waiting for unfinished jobs
  In file included from /usr/include/osmium/io/detail/pbf_decoder.hpp:51:0,
   from /usr/include/osmium/io/detail/pbf_input_format.hpp:51,
   from /usr/include/osmium/io/pbf_input.hpp:46,
   from /usr/include/osmium/io/any_input.hpp:48,
   from 
/home/lamby/temp/cdt.20160225074733.Dt35P9JqeR/osmcoastline-2.1.2/src/osmcoastline_ways.cpp:31:
  /usr/include/osmium/io/detail/protobuf_tags.hpp:36:35: fatal error: 
protozero/pbf_types.hpp: No such file or directory
  compilation terminated.
  src/CMakeFiles/osmcoastline_ways.dir/build.make:65: recipe for target 
'src/CMakeFiles/osmcoastline_ways.dir/osmcoastline_ways.cpp.o' failed
  make[3]: *** [src/CMakeFiles/osmcoastline_ways.dir/osmcoastline_ways.cpp.o] 
Error 1
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160225074733.Dt35P9JqeR/osmcoastline-2.1.2/obj-x86_64-linux-gnu'
  CMakeFiles/Makefile2:242: recipe for target 
'src/CMakeFiles/osmcoastline_ways.dir/all' failed
  make[2]: *** [src/CMakeFiles/osmcoastline_ways.dir/all] Error 2
  [ 75%] Building CXX object src/CMakeFiles/osmcoastline.dir/srs.cpp.o
  cd 
/home/lamby/temp/cdt.20160225074733.Dt35P9JqeR/osmcoastline-2.1.2/obj-x86_64-linux-gnu/src
 && /usr/bin/c++   -DOSMCOASTLINE_VERSION=\"2.1.2\" -D_FILE_OFFSET_BITS=64 
-D_LARGEFILE_SOURCE 
-I/home/lamby/temp/cdt.20160225074733.Dt35P9JqeR/osmcoastline-2.1.2/include 
-isystem /usr/include/gdal  -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2-std=c++11 -Wall 
-Wextra -pedantic -Wredundant-decls -Wdisabled-optimization -Wctor-dtor-privacy 
-Wnon-virtual-dtor -Woverloaded-virtual -Wsign-promo -Wold-style-cast -o 
CMakeFiles/osmcoastline.dir/srs.cpp.o -c 
/home/lamby/temp/cdt.20160225074733.Dt35P9JqeR/osmcoastline-2.1.2/src/srs.cpp
  [ 80%] Building CXX object src/CMakeFiles/osmcoastline.dir/options.cpp.o
  cd 
/home/lamby/temp/cdt.20160225074733.Dt35P9JqeR/osmcoastline-2.1.2/obj-x86_64-linux-gnu/src
 && /usr/bin/c++   -DOSMCOASTLINE_VERSION=\"2.1.2\" -D_FILE_OFFSET_BITS=64 
-D_LARGEFILE_SOURCE 
-I/home/lamby/temp/cdt.20160225074733.Dt35P9JqeR/osmcoastline-2.1.2/include 
-isystem /usr/include/gdal  -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2-std=c++11 -Wall 
-Wextra -pedantic -Wredundant-decls -Wdisabled-optimization -Wctor-dtor-privacy 
-Wnon-virtual-dtor -Woverloaded-virtual -Wsign-promo -Wold-style-cast -o 
CMakeFiles/osmcoastline.dir/options.cpp.o -c 
/home/lamby/temp/cdt.20160225074733.Dt35P9JqeR/osmcoastline-2.1.2/src/options.cpp
  In file included from /usr/include/osmium/io/detail/pbf_decoder.hpp:51:0,
   from 

Bug#815866: bogofilter: FTBFS: ../../../src/tests/outputs/dump.load-2.out ./checks.14403.20160225T074548/dump.load-2.txt differ: char 87, line 3 FAIL: t.dump.load want: "7.2 6.20030303 10.20030304

[Chris Lamb]

Source: bogofilter
Version: 1.2.4+dfsg1-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,

bogofilter fails to build from source in unstable/amd64:

  [..]

  /usr/bin/make  check-TESTS
  make[6]: Entering directory 
'/home/lamby/temp/cdt.20160225074455.tfh937CMkZ/bogofilter-1.2.4+dfsg1/obj-db/src/tests'
  PASS: t.query.config
  Aborted (core dumped)
  PASS: t.abort
  PASS: t.env
  PASS: t.ctype
  PASS: t.bogodir
  SKIP: t.leakfind
  PASS: t.u_fpe
  PASS: t.longoptions
  PASS: t.ignore_spam_header
  PASS: t.nullstatsprefix
  PASS: t.integrity
  PASS: t.integrity2
  PASS: t.integrity3
  PASS: t.passthrough-hb
  PASS: t.escaped.html
  PASS: t.escaped.url
  PASS: t.base64
  PASS: t.split
  PASS: t.parsing
  PASS: t.lexer
  PASS: t.lexer.mbx
  PASS: t.lexer.qpcr
  PASS: t.lexer.eoh
  PASS: t.spam.header.place
  PASS: t.block.on.subnets
  PASS: t.token.count
  PASS: t.multiple.tokens.head
  PASS: t.multiple.tokens.body
  PASS: t.multiple.tokens.min.mul
  PASS: t.encoding
  PASS: t.rfc2047_broken
  PASS: t.rfc2047_folded
  PASS: t.crash-invalid-base64
  PASS: t.message_addr
  PASS: t.message_id
  PASS: t.queue_id
  ../../../src/tests/outputs/dump.load-2.out 
./checks.14403.20160225T074548/dump.load-2.txt differ: char 87, line 3
  FAIL: t.dump.load
  want: "7.2 6.20030303 10.20030304", have: "1.2 6.20030303 10.20030304"
  FAIL: t.nonascii.replace
  PASS: t.maint
  PASS: t.robx
  PASS: t.regtest
  PASS: t.upgrade.subnet.prefix
  PASS: t.multiple.wordlists
  PASS: t.probe
  PASS: t.bf_compact
  PASS: t.score1
  PASS: t.score2
  PASS: t.systest
  PASS: t.grftest
  PASS: t.wordhist
  ../../../src/tests/outputs/bulkmode.out 
./checks.15335.20160225T074550/bulk-double-2.out differ: char 80, line 3
  FAIL: t.bulkmode
  PASS: t.MH
  PASS: t.maildir
  PASS: t.bogoutil
  PASS: t.lock1
  PASS: t.lock3
  > the following test is skipped, set BF_RUN_VALGRIND=1 to run it
  SKIP: t.valgrind
  ==
  3 of 55 tests failed
  (2 tests were not run)
  ==
  Makefile:536: recipe for target 'check-TESTS' failed
  make[6]: *** [check-TESTS] Error 1
  make[6]: Leaving directory 
'/home/lamby/temp/cdt.20160225074455.tfh937CMkZ/bogofilter-1.2.4+dfsg1/obj-db/src/tests'
  Makefile:659: recipe for target 'check-am' failed
  make[5]: *** [check-am] Error 2
  make[5]: Leaving directory 
'/home/lamby/temp/cdt.20160225074455.tfh937CMkZ/bogofilter-1.2.4+dfsg1/obj-db/src/tests'
  Makefile:662: recipe for target 'check' failed
  make[4]: *** [check] Error 2
  make[4]: Leaving directory 
'/home/lamby/temp/cdt.20160225074455.tfh937CMkZ/bogofilter-1.2.4+dfsg1/obj-db/src/tests'
  Makefile:1486: recipe for target 'check-recursive' failed
  make[3]: *** [check-recursive] Error 1
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160225074455.tfh937CMkZ/bogofilter-1.2.4+dfsg1/obj-db/src'
  Makefile:1757: recipe for target 'check' failed
  make[2]: *** [check] Error 2
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160225074455.tfh937CMkZ/bogofilter-1.2.4+dfsg1/obj-db/src'
  Makefile:511: recipe for target 'check-recursive' failed
  make[1]: *** [check-recursive] Error 1
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160225074455.tfh937CMkZ/bogofilter-1.2.4+dfsg1/obj-db'
  debian/rules:81: recipe for target 'check' failed
  make: *** [check] Error 2

  [..]

The full build log is attached.


Regards,

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


bogofilter.1.2.4+dfsg1-4.unstable.amd64.log.txt.gz
Description: Binary data

Bug#815869: osmium-tool: FTBFS: protobuf_tags.hpp:36:35: fatal error: protozero/pbf_types.hpp: No such file or directory

[Chris Lamb]

Source: osmium-tool
Version: 1.3.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,

osmium-tool fails to build from source in unstable/amd64:

  [..]

  [ 46%] Building CXX object src/CMakeFiles/osmium.dir/command_check_refs.cpp.o
  cd 
/home/lamby/temp/cdt.20160225074829.SvnyKmT6F8/osmium-tool-1.3.0/obj-x86_64-linux-gnu/src
 && /usr/bin/c++   -DOSMIUM_VERSION=\"1.3.0\" -D_FILE_OFFSET_BITS=64 
-D_LARGEFILE_SOURCE 
-I/home/lamby/temp/cdt.20160225074829.SvnyKmT6F8/osmium-tool-1.3.0/include 
-I/home/lamby/temp/cdt.20160225074829.SvnyKmT6F8/osmium-tool-1.3.0/obj-x86_64-linux-gnu/src
  -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2-std=c++11 -o 
CMakeFiles/osmium.dir/command_check_refs.cpp.o -c 
/home/lamby/temp/cdt.20160225074829.SvnyKmT6F8/osmium-tool-1.3.0/src/command_check_refs.cpp
  In file included from /usr/include/osmium/io/detail/pbf_decoder.hpp:51:0,
   from /usr/include/osmium/io/detail/pbf_input_format.hpp:51,
   from /usr/include/osmium/io/pbf_input.hpp:46,
   from /usr/include/osmium/io/any_input.hpp:48,
   from 
/home/lamby/temp/cdt.20160225074829.SvnyKmT6F8/osmium-tool-1.3.0/src/command_cat.cpp:28:
  /usr/include/osmium/io/detail/protobuf_tags.hpp:36:35: fatal error: 
protozero/pbf_types.hpp: No such file or directory
  compilation terminated.
  src/CMakeFiles/osmium.dir/build.make:65: recipe for target 
'src/CMakeFiles/osmium.dir/command_cat.cpp.o' failed
  make[3]: *** [src/CMakeFiles/osmium.dir/command_cat.cpp.o] Error 1
  make[3]: *** Waiting for unfinished jobs
  In file included from /usr/include/osmium/io/detail/pbf_decoder.hpp:51:0,
   from /usr/include/osmium/io/detail/pbf_input_format.hpp:51,
   from /usr/include/osmium/io/pbf_input.hpp:46,
   from /usr/include/osmium/io/any_input.hpp:48,
   from 
/home/lamby/temp/cdt.20160225074829.SvnyKmT6F8/osmium-tool-1.3.0/src/command_changeset_filter.cpp:27:
  /usr/include/osmium/io/detail/protobuf_tags.hpp:36:35: fatal error: 
protozero/pbf_types.hpp: No such file or directory
  compilation terminated.
  [ 48%] Building CXX object 
test/CMakeFiles/unit_tests.dir/__/src/command_apply_changes.cpp.o
  cd 
/home/lamby/temp/cdt.20160225074829.SvnyKmT6F8/osmium-tool-1.3.0/obj-x86_64-linux-gnu/test
 && /usr/bin/c++   -DOSMIUM_VERSION=\"1.3.0\" -D_FILE_OFFSET_BITS=64 
-D_LARGEFILE_SOURCE 
-I/home/lamby/temp/cdt.20160225074829.SvnyKmT6F8/osmium-tool-1.3.0/test/include 
-I/home/lamby/temp/cdt.20160225074829.SvnyKmT6F8/osmium-tool-1.3.0/test/../src 
-I/home/lamby/temp/cdt.20160225074829.SvnyKmT6F8/osmium-tool-1.3.0/test/../include
  -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2-std=c++11 -o 
CMakeFiles/unit_tests.dir/__/src/command_apply_changes.cpp.o -c 
/home/lamby/temp/cdt.20160225074829.SvnyKmT6F8/osmium-tool-1.3.0/src/command_apply_changes.cpp
  src/CMakeFiles/osmium.dir/build.make:161: recipe for target 
'src/CMakeFiles/osmium.dir/command_changeset_filter.cpp.o' failed
  make[3]: *** [src/CMakeFiles/osmium.dir/command_changeset_filter.cpp.o] Error 
1
  [ 51%] Building CXX object 
test/CMakeFiles/unit_tests.dir/__/src/command_help.cpp.o
  cd 
/home/lamby/temp/cdt.20160225074829.SvnyKmT6F8/osmium-tool-1.3.0/obj-x86_64-linux-gnu/test
 && /usr/bin/c++   -DOSMIUM_VERSION=\"1.3.0\" -D_FILE_OFFSET_BITS=64 
-D_LARGEFILE_SOURCE 
-I/home/lamby/temp/cdt.20160225074829.SvnyKmT6F8/osmium-tool-1.3.0/test/include 
-I/home/lamby/temp/cdt.20160225074829.SvnyKmT6F8/osmium-tool-1.3.0/test/../src 
-I/home/lamby/temp/cdt.20160225074829.SvnyKmT6F8/osmium-tool-1.3.0/test/../include
  -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2-std=c++11 -o 
CMakeFiles/unit_tests.dir/__/src/command_help.cpp.o -c 
/home/lamby/temp/cdt.20160225074829.SvnyKmT6F8/osmium-tool-1.3.0/src/command_help.cpp
  In file included from /usr/include/osmium/io/detail/pbf_decoder.hpp:51:0,
   from /usr/include/osmium/io/detail/pbf_input_format.hpp:51,
   from /usr/include/osmium/io/pbf_input.hpp:46,
   from /usr/include/osmium/io/any_input.hpp:48,
   from 
/home/lamby/temp/cdt.20160225074829.SvnyKmT6F8/osmium-tool-1.3.0/src/command_cat.cpp:28:
  /usr/include/osmium/io/detail/protobuf_tags.hpp:36:35: fatal error: 
protozero/pbf_types.hpp: No such file or directory
  In file included from /usr/include/osmium/io/detail/pbf_decoder.hpp:51:0,
   from /usr/include/osmium/io/detail/pbf_input_format.hpp:51,
   from /usr/include/osmium/io/pbf_input.hpp:46,
   from /usr/include/osmium/io/any_input.hpp:48,
   from 

Bug#815867: libxkbcommon: FTBFS: FAIL: test/x11comp

[Chris Lamb]

Source: libxkbcommon
Version: 0.5.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,

libxkbcommon fails to build from source in unstable/amd64:

  [..]

  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160225074617.SVmbtSnzXS/libxkbcommon-0.5.0'
  make  check-TESTS
  make[3]: Entering directory 
'/home/lamby/temp/cdt.20160225074617.SVmbtSnzXS/libxkbcommon-0.5.0'
  make[4]: Entering directory 
'/home/lamby/temp/cdt.20160225074617.SVmbtSnzXS/libxkbcommon-0.5.0'
  PASS: test/context
  PASS: test/utf8
  PASS: test/rules-file
  PASS: test/log
  PASS: test/atom
  PASS: test/keysym
  PASS: test/state
  PASS: test/filecomp
  PASS: test/buffercomp
  PASS: test/stringcomp
  PASS: test/compose
  PASS: test/rulescomp
  PASS: test/keyseq
  SKIP: test/x11
  FAIL: test/x11comp
  
  Testsuite summary for libxkbcommon 0.5.0
  
  # TOTAL: 15
  # PASS:  13
  # SKIP:  1
  # XFAIL: 0
  # FAIL:  1
  # XPASS: 0
  # ERROR: 0
  
  See ./test-suite.log
  Please report to 
https://bugs.freedesktop.org/enter_bug.cgi?product=libxkbcommon
  
  Makefile:1687: recipe for target 'test-suite.log' failed
  make[4]: *** [test-suite.log] Error 1
  make[4]: Leaving directory 
'/home/lamby/temp/cdt.20160225074617.SVmbtSnzXS/libxkbcommon-0.5.0'
  Makefile:1793: recipe for target 'check-TESTS' failed
  make[3]: *** [check-TESTS] Error 2
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160225074617.SVmbtSnzXS/libxkbcommon-0.5.0'
  Makefile:2102: recipe for target 'check-am' failed
  make[2]: *** [check-am] Error 2
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160225074617.SVmbtSnzXS/libxkbcommon-0.5.0'
  Makefile:2105: recipe for target 'check' failed
  make[1]: *** [check] Error 2
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160225074617.SVmbtSnzXS/libxkbcommon-0.5.0'
  dh_auto_test: make -j9 check returned exit code 2
  debian/rules:17: 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
   `-


libxkbcommon.0.5.0-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#815864: python3-venv: unable to create a virtual environment

[Florent Rougon]

Package: python3-venv
Version: 3.5.1-2
Severity: serious
Justification: renders the package unusable

Hello,

It seems current Python 3 packages in Debian unstable don't allow
creating a virtual environment anymore with pyvenv and friends:

~/python-venv % /usr/bin/python3.5 -m venv testdir
The virtual environment was not created successfully because ensurepip is not
available.  On Debian/Ubuntu systems, you need to install the python3-venv
package using the following command.

apt-get install python3-venv

You may need to use sudo with that command.  After installing the python3-venv
package, recreate your virtual environment.

~/python-venv % dpkg -l python3-venv
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---=
ii  python3-venv   3.5.1-2  amd64pyvenv-3 binary for python3 (defa
~/python-venv %

Thanks in advance for looking into this.

Regards

-- 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.4.0-1-amd64 (SMP w/8 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: sysvinit (via /sbin/init)

Versions of packages python3-venv depends on:
ii  python3 3.5.1-2
ii  python3.5-venv  3.5.1-7

python3-venv recommends no packages.

python3-venv suggests no packages.

-- no debconf information

Bug#814311: marked as done (ruby-omniauth-crowd: FTBFS: Failures: OmniAuth::Strategies::Crowd GET /auth/crowd/callback with credentials will fail should fail)

[Debian Bug Tracking System]

Your message dated Thu, 25 Feb 2016 07:35:11 +
with message-id 
and subject line Bug#814311: fixed in ruby-omniauth-crowd 2.2.3-2
has caused the Debian Bug report #814311,
regarding ruby-omniauth-crowd: FTBFS: Failures: OmniAuth::Strategies::Crowd GET 
/auth/crowd/callback with credentials will fail should fail
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.)


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

Dear Maintainer,

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

  [..]
  
  
RUBYLIB=/home/lamby/temp/cdt.20160210085355.S6LhMFrgzI/ruby-omniauth-crowd-2.2.3/debian/ruby-omniauth-crowd/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=/home/lamby/.gem/ruby/2.2.0:/var/lib/gems/2.2.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.2.0:/usr/share/rubygems-integration/2.2.0:/usr/share/rubygems-integration/2.2:/usr/share/rubygems-integration/all:debian/ruby-omniauth-crowd/usr/share/rubygems-integration/all
 ruby2.2 -S rake -f debian/ruby-tests.rake
  /usr/bin/ruby2.2 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
documentation
  
  OmniAuth::Strategies::Crowd
Authentication Request Body
  should send password in session request
  should escape special characters username and password in session request
Session Request Body
  should send username and password in session request
  should escape special characters username and password in session request
GET /auth/crowd
  I, [2016-02-10T08:54:25.660032 #4375]  INFO -- omniauth: (crowd) Request 
phase initiated.
  should show the login form
POST /auth/crowd
  I, [2016-02-10T08:54:25.662068 #4375]  INFO -- omniauth: (crowd) Request 
phase initiated.
  should redirect to callback
GET /auth/crowd/callback without any credentials
  I, [2016-02-10T08:54:25.664514 #4375]  INFO -- omniauth: (crowd) Callback 
phase initiated.
  E, [2016-02-10T08:54:25.664576 #4375] ERROR -- omniauth: (crowd) 
Authentication failure! no_credentials encountered.
  should fail
GET /auth/crowd/callback with credentials can be successful
  when using authentication endpoint
  I, [2016-02-10T08:54:25.668561 #4375]  INFO -- omniauth: (crowd) Callback 
phase initiated.
should call through to the master app
  I, [2016-02-10T08:54:25.676015 #4375]  INFO -- omniauth: (crowd) Callback 
phase initiated.
should have an auth hash
  I, [2016-02-10T08:54:25.681894 #4375]  INFO -- omniauth: (crowd) Callback 
phase initiated.
should have good data
  when using session endpoint
  I, [2016-02-10T08:54:25.687884 #4375]  INFO -- omniauth: (crowd) Callback 
phase initiated.
should call through to the master app
  I, [2016-02-10T08:54:25.694646 #4375]  INFO -- omniauth: (crowd) Callback 
phase initiated.
should have an auth hash
  I, [2016-02-10T08:54:25.701234 #4375]  INFO -- omniauth: (crowd) Callback 
phase initiated.
should have good data
GET /auth/crowd/callback with credentials will fail
  should fail (FAILED - 1)
  
  Failures:
  
1) OmniAuth::Strategies::Crowd GET /auth/crowd/callback with credentials 
will fail should fail
   Failure/Error: to_return(:code=>400)
   ArgumentError:
 Unknown key: "code". Valid keys are: "headers", "status", "body", 
"exception", "should_timeout"
   # ./spec/omniauth/strategies/crowd_spec.rb:153:in `block (3 levels) in 
'
  
  Finished in 0.10463 seconds (files took 0.66 seconds to load)
  14 examples, 1 failure
  
  Failed examples:
  
  rspec ./spec/omniauth/strategies/crowd_spec.rb:156 # 
OmniAuth::Strategies::Crowd GET /auth/crowd/callback with credentials will fail 
should fail
  
  /usr/bin/ruby2.2 /usr/bin/rspec --pattern ./spec/\*\*/\*_spec.rb --format 
documentation failed
  ERROR: Test "ruby2.2" failed. Exiting.
  dh_auto_install: dh_ruby --install 
/home/lamby/temp/cdt.20160210085355.S6LhMFrgzI/ruby-omniauth-crowd-2.2.3/debian/ruby-omniauth-crowd
 returned exit code 1
  debian/rules:6: recipe for target 'binary' failed
  make: *** [binary] Error 1

  [..]

The full build log is attached.


Regards,

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

Bug#814645: not in stable yet

[Pirate Praveen]

ruby-mousetrap-rails is not part of any stable release. So should I
really handle this upgrade case?



signature.asc
Description: OpenPGP digital signature

Bug#808450: marked as done (ruby-sanitize: FTBFS: Config::DEFAULT#test_0009_should clean malicious HTML [/build/ruby-sanitize-2.1.0/test/test_sanitize.rb:213]:)

[Debian Bug Tracking System]

Your message dated Thu, 25 Feb 2016 07:35:17 +
with message-id 
and subject line Bug#808450: fixed in ruby-sanitize 2.1.0-2
has caused the Debian Bug report #808450,
regarding ruby-sanitize: FTBFS: Config::DEFAULT#test_0009_should clean 
malicious HTML [/build/ruby-sanitize-2.1.0/test/test_sanitize.rb:213]:
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.)


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

Dear Maintainer,

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

  [..]

  Finished in 0.222619s, 637.8620 runs/s, 871.4452 assertions/s.
  
1) Failure:
  Config::DEFAULT#test_0009_should clean malicious HTML 
[/build/ruby-sanitize-2.1.0/test/test_sanitize.rb:213]:
  --- expected
  +++ actual
  @@ -1 +1 @@
  -"Lorem ipsum dolor sit amet scriptalert(\"hello world\");"
  +"Lorem ipsum dolor sit amet scriptalert(\"hello world\");"
  
  
  
2) Failure:
  Config::BASIC#test_0006_should clean malicious HTML 
[/build/ruby-sanitize-2.1.0/test/test_sanitize.rb:253]:
  --- expected
  +++ actual
  @@ -1 +1 @@
  -"Lorem ipsum http://foo.com/\; 
rel=\"nofollow\">dolor sitamet scriptalert(\"hello 
world\");"
  +"Lorem ipsum http://foo.com/\; 
rel=\"nofollow\">dolor sitamet 
scriptalert(\"hello world\");"
  
  
  
3) Failure:
  Config::RESTRICTED#test_0004_should clean malicious HTML 
[/build/ruby-sanitize-2.1.0/test/test_sanitize.rb:229]:
  --- expected
  +++ actual
  @@ -1 +1 @@
  -"Lorem ipsum dolor sit amet scriptalert(\"hello 
world\");"
  +"Lorem ipsum dolor sit amet 
scriptalert(\"hello world\");"
  
  
  
4) Failure:
  Full Document parser (using clean_document)#test_0008_should wrap malicious 
with DOCTYPE and HTML tag 
[/build/ruby-sanitize-2.1.0/test/test_sanitize.rb:315]:
  --- expected
  +++ actual
  @@ -1,3 +1,3 @@
   "http://www.w3.org/TR/REC-html40/loose.dtd\;>
  -Lorem ipsum dolor sit amet scriptalert(\"hello world\");
  +Lorem ipsum dolor sit amet scriptalert(\"hello world\");
   "
  
  
  
5) Failure:
  Config::RELAXED#test_0005_should clean malicious HTML 
[/build/ruby-sanitize-2.1.0/test/test_sanitize.rb:275]:
  --- expected
  +++ actual
  @@ -1 +1 @@
  -"Lorem ipsum http://foo.com/\;>dolor sitamet 
scriptalert(\"hello world\");"
  +"Lorem ipsum http://foo.com/\;>dolor sitamet 
scriptalert(\"hello world\");"
  
  
  142 runs, 194 assertions, 5 failures, 0 errors, 0 skips
  ERROR: Test "ruby2.2" failed. Exiting.
  dh_auto_install: dh_ruby --install 
/build/ruby-sanitize-2.1.0/debian/ruby-sanitize returned exit code 1
  debian/rules:15: recipe for target 'binary' failed
  make: *** [binary] Error 1
  dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 
2

  [..]

The full build log is attached or can be viewed here:


https://reproducible.debian.net/logs/unstable/amd64/ruby-sanitize_2.1.0-1.build1.log.gz


Regards,

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


ruby-sanitize.2.1.0-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: ruby-sanitize
Source-Version: 2.1.0-2

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

Debian distribution maintenance software
pp.
Balasankar C  (supplier of updated ruby-sanitize 
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: Thu, 25 Feb 2016 11:34:19 +0530
Source: ruby-sanitize
Binary: ruby-sanitize
Architecture: source all
Version: 2.1.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Balasankar C 
Description:
 

Bug#808738: marked as done (ruby-sinatra: FTBFS: 1034 runs, 2261 assertions, 0 failures, 5 errors, 0 skips)

[Debian Bug Tracking System]

Your message dated Thu, 25 Feb 2016 07:20:08 +
with message-id 
and subject line Bug#808738: fixed in ruby-sinatra 1.4.7-1
has caused the Debian Bug report #808738,
regarding ruby-sinatra: FTBFS: 1034 runs, 2261 assertions, 0 failures, 5 
errors, 0 skips
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.)


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

Dear Maintainer,

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

  [..]

   1034 runs, 2261 assertions, 0 failures, 5 errors, 0 skips
  rake aborted!
  Command failed with status (1): [ruby -I"lib" -rubygems -I.  
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/asciidoctor_test.rb" 
"test/base_test.rb" "test/builder_test.rb" "test/coffee_test.rb" 
"test/compile_test.rb" "test/creole_test.rb" "test/delegator_test.rb" 
"test/encoding_test.rb" "test/erb_test.rb" "test/extensions_test.rb" 
"test/filter_test.rb" "test/haml_test.rb" "test/helpers_test.rb" 
"test/integration_test.rb" "test/less_test.rb" "test/liquid_test.rb" 
"test/mapped_error_test.rb" "test/markaby_test.rb" "test/markdown_test.rb" 
"test/mediawiki_test.rb" "test/middleware_test.rb" "test/nokogiri_test.rb" 
"test/rabl_test.rb" "test/rack_test.rb" "test/radius_test.rb" 
"test/rdoc_test.rb" "test/readme_test.rb" "test/request_test.rb" 
"test/response_test.rb" "test/result_test.rb" "test/route_added_hook_test.rb" 
"test/routing_test.rb" "test/sass_test.rb" "test/scss_test.rb" 
"test/server_test.rb" "test/settings_test.rb" "test/sinatra_test.rb" 
"test/slim_test.rb" "test/static_test.rb" "test/streaming_test.rb" 
"test/stylus_test.rb" "test/templates_test.rb" "test/textile_test.rb" 
"test/wlang_test.rb" "test/yajl_test.rb" ]
  /usr/bin/rake2.2:33:in `'
  Tasks: TOP => default => test
  (See full trace by running task with --trace)
  ERROR: Test "ruby2.2" failed. Exiting.
  dh_auto_install: dh_ruby --install 
/home/lamby/temp/cdt.20151222120731.H1LBqLhjdj/ruby-sinatra-1.4.6/debian/ruby-sinatra
 returned exit code 1
  debian/rules:15: recipe for target 'binary' failed
  make: *** [binary] Error 1

  [..]

The full build log is attached.


Regards,

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


ruby-sinatra.1.4.6-2.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: ruby-sinatra
Source-Version: 1.4.7-1

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

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated ruby-sinatra 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: Thu, 25 Feb 2016 11:01:25 +0530
Source: ruby-sinatra
Binary: ruby-sinatra
Architecture: source all
Version: 1.4.7-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Pirate Praveen 
Description:
 ruby-sinatra - Ruby web-development dressed in a DSL
Closes: 808738
Changes:
 ruby-sinatra (1.4.7-1) experimental; urgency=medium
 .
   [ Pirate Praveen ]
 .
   * New upstream patch release
   * wrap-and-sort dependencies
   * Bump standards version to 3.9.7 (no changes)
   * Make copyright dep5 compliant
 .
   [ Balasankar C ]
   * Add patch i18n-fix.patch
 - Specify available locales during testing (Closes: #808738)
   * Bump debhelper compatibility
   * Fix Vcs-* links to use secure protocol.
Checksums-Sha1:
 05d870286b7ae4019093f621ca982a43a9da95c8 2480 ruby-sinatra_1.4.7-1.dsc
 b347f662c518904079c7d4bcd81ddce0a3d3e8ce 371765 ruby-sinatra_1.4.7.orig.tar.gz
 ce2a3a92efb373e778e4c1953b8cd9d1564b5d26 4560 

Bug#815853: Cannot modprobe due to wrong kernel version string

[Heinrich Schuchardt]

The error was caused by the system not using the kernel installed in
/boot but reading it from /dev/mmcblk0p1.

Please, close the message.

Best regards

Heinrich Schuchardt

Bug#815861: mcstrans: doesn't create /var/run/setrans on startup with systemd

[Russell Coker]

Package: mcstrans
Version: 2.4-4
Severity: grave
Justification: renders package unusable

/var/run/setrans 0755 root root - -

I think we need a /usr/lib/tmpfiles.d file with something like the above to 
create it
when systemd is in use.  Currently mcstrans doesn't start on Unstable.

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

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

Versions of packages mcstrans depends on:
ii  init-system-helpers  1.28+nmu1
ii  libc62.21-9
ii  libcap2  1:2.24-12
ii  libpcre3 2:8.38-1
ii  libselinux1  2.4-3
ii  selinux-utils2.4-3

mcstrans recommends no packages.

mcstrans suggests no packages.

-- no debconf information

Bug#794169: marked as done (FTBFS: EimXML::OpenDSL scope of block is one of outside fails)

[Debian Bug Tracking System]

Your message dated Thu, 25 Feb 2016 14:55:05 +0900
with message-id <1456379705.16665.1.ca...@gfd-dennou.org>
and subject line Re: FTBFS: EimXML::OpenDSL scope of block is one of outside 
fails
has caused the Debian Bug report #794169,
regarding FTBFS: EimXML::OpenDSL scope of block is one of outside fails
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.)


-- 
794169: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794169
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-eim-xml
Version: 0.0.4-3
Severity: serious
Tags: sid stretch
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs

Dear Maintainer,

/usr/bin/ruby2.1 /usr/bin/rspec --pattern spec/\*\*\{,/\*/\*\*\}/\*_spec.rb
..F...F.FFF..FFFFF..

Failures:

  1) EimXML::OpenDSL scope of block is one of outside
 Failure/Error: block_executed.should be_true
   expected true to respond to `true?` or perhaps you meant `be true` or 
`be_truthy`
 # ./spec/dsl_spec.rb:127:in `block (2 levels) in '

  2) EimXML::Element #match
 Failure/Error: e.match(:tag).should be_true
   expected true to respond to `true?` or perhaps you meant `be true` or 
`be_truthy`
 # ./spec/eim_xml_spec.rb:325:in `block (2 levels) in '


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

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

Kernel: Linux 3.19.0-23-generic (SMP w/8 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
This FTBFS is already closed in unstable, ver.0.0.4-5.

I closed this report. Thansk.


On Thu, 30 Jul 2015 22:37:24 + "Chris West \(Faux\)"  wrote:
> Source: ruby-eim-xml
> Version: 0.0.4-3
> Severity: serious
> Tags: sid stretch
> Justification: fails to build from source
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: ftbfs
> 
> Dear Maintainer,
> 
> /usr/bin/ruby2.1 /usr/bin/rspec --pattern
spec/\*\*\{,/\*/\*\*\}/\*_spec.rb
>
..F...F.FFF..FFF...
.FF..
> 
> Failures:
> 
>   1) EimXML::OpenDSL scope of block is one of outside
>  Failure/Error: block_executed.should be_true
>expected true to respond to `true?` or perhaps you meant `be
true` or `be_truthy`
>  # ./spec/dsl_spec.rb:127:in `block (2 levels) in '
> 
>   2) EimXML::Element #match
>  Failure/Error: e.match(:tag).should be_true
>expected true to respond to `true?` or perhaps you meant `be
true` or `be_truthy`
>  # ./spec/eim_xml_spec.rb:325:in `block (2 levels) in '
> 
> 
> Full build log:
> https://reproducible.debian.net/rb-pkg/unstable/amd64/ruby-eim-xml.ht
ml
> 
> -- System Information:
> Debian Release: stretch/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 3.19.0-23-generic (SMP w/8 CPU cores)
> Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
> 
> --- End Message ---

Bug#815853: Cannot modprobe due to wrong kernel version string

[Heinrich Schuchardt]

Package: linux-image-3.16.0-4-armmp-lpae
Version: 3.16.7-ckt20-1+deb8u2
Severity: grave

The package installs modules in /lib/modules/3.16.0-4-armmp-lpae
but uname -r returns
3.16.0-4-armmp

This means that modules cannot be loaded, e.g.

$ sudo modprobe nls_cp437
modprobe: ERROR: ../libkmod/libkmod.c:557 kmod_search_moddep() could not
open moddep file '/lib/modules/3.16.0-4-armmp/modules.dep.bin'

For lpae kernels append -lpae to the kernel version string.

Best regards

Heinrich Schuchardt

Bug#815132: marked as done (tesseract-ocr: link against libept5, libept4 is gone)

[Debian Bug Tracking System]

Your message dated Thu, 25 Feb 2016 01:49:53 +
with message-id 
and subject line Bug#815132: fixed in tesseract 3.04.01-3
has caused the Debian Bug report #815132,
regarding tesseract-ocr: link against libept5, libept4 is gone
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.)


-- 
815132: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815132
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tesseract-ocr
Version: 3.04.01-2
Severity: serious

Dear Maintainer(s),

   since the liblept4 package has been replaced by liblept5,
tesseract-ocr is not installable in testing/sid.

Regards,
Jörg-Volker.
--- End Message ---
--- Begin Message ---
Source: tesseract
Source-Version: 3.04.01-3

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

Debian distribution maintenance software
pp.
Jeff Breidenbach  (supplier of updated tesseract 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: Thu, 25 Feb 2016 00:22:26 +
Source: tesseract
Binary: tesseract-ocr-dev libtesseract-dev libtesseract3 tesseract-ocr 
tesseract-ocr-all
Architecture: source amd64 all
Version: 3.04.01-3
Distribution: unstable
Urgency: medium
Maintainer: Jeffrey Ratcliffe 
Changed-By: Jeff Breidenbach 
Description:
 libtesseract-dev - Development files for the tesseract command line OCR tool
 libtesseract3 - Tesseract OCR library
 tesseract-ocr - Tesseract command line OCR tool
 tesseract-ocr-all - Tesseract OCR with all language packages
 tesseract-ocr-dev - transitional dummy package
Closes: 815056 815132
Changes:
 tesseract (3.04.01-3) unstable; urgency=medium
 .
   * Fix leptonica dependency (closes: #815132)
   * Drop back to libtesseract3, restore old ABI (closes: #815056)
Checksums-Sha1:
 777b18755579334acfdf6639d72209d5232ff2e8 2128 tesseract_3.04.01-3.dsc
 cee11296df09687c8d1acc99c6301522e87ee465 7798 tesseract_3.04.01-3.diff.gz
 26c949007604fe051dec01d79d3d06fe1c2abb5f 1385742 
libtesseract-dev_3.04.01-3_amd64.deb
 f921c0153956e51ddd7e63d56d4981ed4d8c83f0 1134792 
libtesseract3_3.04.01-3_amd64.deb
 122c9da8eae891bf5b977c0ff963ee4b600f9e21 9614 
tesseract-ocr-all_3.04.01-3_all.deb
 ce58249897a99934e8ad7545c3ced14b499fff8e 11082 
tesseract-ocr-dev_3.04.01-3_all.deb
 3747b299e228ab56a5022f2cf556e8648052750e 142344 
tesseract-ocr_3.04.01-3_amd64.deb
Checksums-Sha256:
 f0f7ba1763ebefa6aa215d5f8a3b7a67295d8a7e28dca8f8659cf2ef8151e311 2128 
tesseract_3.04.01-3.dsc
 851feaf87c35b9b1f57257cd8c776e279596afd34d7ca2fca74c064ec43f352d 7798 
tesseract_3.04.01-3.diff.gz
 a51261331c64939eae02a35558a5b1e4fbb5f9a13a4ed98df2b00d3a92ffa829 1385742 
libtesseract-dev_3.04.01-3_amd64.deb
 0b1e0257f1f40b4120219b57a502e04154671c012bd711cf63bbc3008a795f50 1134792 
libtesseract3_3.04.01-3_amd64.deb
 cad276acb32663dd0ca287a7d53bbc0fd3ae4e75308aecdb7ab586d96017ee91 9614 
tesseract-ocr-all_3.04.01-3_all.deb
 46d66d14573acefca57611f4300684c302f167af31932bdb05518248611094f7 11082 
tesseract-ocr-dev_3.04.01-3_all.deb
 b782049581eb617e943a0eb0abd4f33c6b257cd66395d4f82e49cfdbff1c58e8 142344 
tesseract-ocr_3.04.01-3_amd64.deb
Files:
 375fa787bc1daf7f127f8d008b92ab86 2128 graphics optional tesseract_3.04.01-3.dsc
 0bb1292dee8ed9c6caf8d183716af2a1 7798 graphics optional 
tesseract_3.04.01-3.diff.gz
 7dbc1556a6046bfb2c089a9a232f534f 1385742 libdevel optional 
libtesseract-dev_3.04.01-3_amd64.deb
 809aecb34787e21fcfac64836b3ce514 1134792 graphics optional 
libtesseract3_3.04.01-3_amd64.deb
 8f9aef40020ab6437d18e4dd44195bec 9614 graphics optional 
tesseract-ocr-all_3.04.01-3_all.deb
 2b19529aa04b356eb55c257ca85e6348 11082 oldlibs optional 
tesseract-ocr-dev_3.04.01-3_all.deb
 535815d9a22cc3ace3fd28d93fa2e657 142344 graphics optional 
tesseract-ocr_3.04.01-3_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWzlzLAAoJEKh2roMKSazToSwQANQujnMX2RmETfTljuWu/str
36u9sebtpgkl+Aue6AIMUlefGAEQMG0fTN+rWItL8Lf8siZmv3t/xJ67QtNmVWau

Bug#815056: marked as done (libtesseract4: fails to upgrade from libtesseract3)

[Debian Bug Tracking System]

Your message dated Thu, 25 Feb 2016 01:49:53 +
with message-id 
and subject line Bug#815056: fixed in tesseract 3.04.01-3
has caused the Debian Bug report #815056,
regarding libtesseract4: fails to upgrade from libtesseract3
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.)


-- 
815056: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815056
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libtesseract4
Version: 3.04.01-1
Severity: serious
Justification: Policy 7.4

Dear Maintainer,

libtesseract4 provides at least one identical file as libtesseract3 without
declaring a "Conflicts" relationshipt, does breaking any upgrade:

> Preparing to unpack .../libtesseract4_3.04.01-1_amd64.deb ...
> Unpacking libtesseract4 (3.04.01-1) ...
> dpkg: error processing archive 
> /var/cache/apt/archives/libtesseract4_3.04.01-1_amd64.deb (--unpack):
>  trying to overwrite '/usr/lib/libtesseract.so.3.0.4', which is also in 
> package libtesseract3 3.04.00-5+b2
> dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
> Errors were encountered while processing:
>  /var/cache/apt/archives/libtesseract4_3.04.01-1_amd64.deb


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

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

Versions of packages libtesseract4 depends on:
ii  libc6   2.21-9
ii  libgcc1 1:5.3.1-8
ii  liblept41.71-2.1+b2
ii  libstdc++6  5.3.1-8

libtesseract4 recommends no packages.

libtesseract4 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: tesseract
Source-Version: 3.04.01-3

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

Debian distribution maintenance software
pp.
Jeff Breidenbach  (supplier of updated tesseract 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: Thu, 25 Feb 2016 00:22:26 +
Source: tesseract
Binary: tesseract-ocr-dev libtesseract-dev libtesseract3 tesseract-ocr 
tesseract-ocr-all
Architecture: source amd64 all
Version: 3.04.01-3
Distribution: unstable
Urgency: medium
Maintainer: Jeffrey Ratcliffe 
Changed-By: Jeff Breidenbach 
Description:
 libtesseract-dev - Development files for the tesseract command line OCR tool
 libtesseract3 - Tesseract OCR library
 tesseract-ocr - Tesseract command line OCR tool
 tesseract-ocr-all - Tesseract OCR with all language packages
 tesseract-ocr-dev - transitional dummy package
Closes: 815056 815132
Changes:
 tesseract (3.04.01-3) unstable; urgency=medium
 .
   * Fix leptonica dependency (closes: #815132)
   * Drop back to libtesseract3, restore old ABI (closes: #815056)
Checksums-Sha1:
 777b18755579334acfdf6639d72209d5232ff2e8 2128 tesseract_3.04.01-3.dsc
 cee11296df09687c8d1acc99c6301522e87ee465 7798 tesseract_3.04.01-3.diff.gz
 26c949007604fe051dec01d79d3d06fe1c2abb5f 1385742 
libtesseract-dev_3.04.01-3_amd64.deb
 f921c0153956e51ddd7e63d56d4981ed4d8c83f0 1134792 
libtesseract3_3.04.01-3_amd64.deb
 122c9da8eae891bf5b977c0ff963ee4b600f9e21 9614 
tesseract-ocr-all_3.04.01-3_all.deb
 ce58249897a99934e8ad7545c3ced14b499fff8e 11082 
tesseract-ocr-dev_3.04.01-3_all.deb
 3747b299e228ab56a5022f2cf556e8648052750e 142344 
tesseract-ocr_3.04.01-3_amd64.deb
Checksums-Sha256:
 f0f7ba1763ebefa6aa215d5f8a3b7a67295d8a7e28dca8f8659cf2ef8151e311 2128 
tesseract_3.04.01-3.dsc
 851feaf87c35b9b1f57257cd8c776e279596afd34d7ca2fca74c064ec43f352d 7798 
tesseract_3.04.01-3.diff.gz
 a51261331c64939eae02a35558a5b1e4fbb5f9a13a4ed98df2b00d3a92ffa829 1385742 
libtesseract-dev_3.04.01-3_amd64.deb
 0b1e0257f1f40b4120219b57a502e04154671c012bd711cf63bbc3008a795f50 1134792 
libtesseract3_3.04.01-3_amd64.deb
 

Bug#814744: marked as done (xapian-core: "Multi-Arch: no" gets rejected by dak)

[Debian Bug Tracking System]

Your message dated Thu, 25 Feb 2016 01:38:03 +
with message-id 
and subject line Bug#814744: fixed in xapian-core 1.2.22-3
has caused the Debian Bug report #814744,
regarding xapian-core: "Multi-Arch: no" gets rejected by dak
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.)


-- 
814744: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814744
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xapian-core
Version: 1.2.22-2
Severity: serious

This package has been built successfully on the autobuilders, but it
has then be rejected by dak with the following message:

  libxapian-dev_1.2.22-2_ppc64el.deb: Multi-Arch: no support in Debian is 
broken (#768353)

I think the default value being "no", the best is to actually drop this 
entry from debian/control.

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

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: xapian-core
Source-Version: 1.2.22-3

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

Debian distribution maintenance software
pp.
Olly Betts  (supplier of updated xapian-core package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Thu, 25 Feb 2016 12:59:19 +1300
Source: xapian-core
Binary: libxapian22v5 libxapian22v5-dbg libxapian-dev xapian-tools xapian-doc 
xapian-examples
Architecture: source
Version: 1.2.22-3
Distribution: unstable
Urgency: medium
Maintainer: Olly Betts 
Changed-By: Olly Betts 
Description:
 libxapian-dev - Development files for Xapian search engine library
 libxapian22v5 - Search engine library
 libxapian22v5-dbg - Debugging symbols for the Xapian Search engine library
 xapian-doc - Core Xapian documentation
 xapian-examples - Xapian simple example programs
 xapian-tools - Basic tools for Xapian search engine library
Closes: 814744
Changes:
 xapian-core (1.2.22-3) unstable; urgency=medium
 .
   * Remove "Multi-Arch: no" as dak rejects it.  (Closes: #814744)
Checksums-Sha1:
 bcbc54e8f00f62573e711961e9bae7438cd7a2be 2207 xapian-core_1.2.22-3.dsc
 a45a95e7fd5f7a8483153b47a76455a1448b4fb8 17216 
xapian-core_1.2.22-3.debian.tar.xz
Checksums-Sha256:
 7146e4ae707dc735ac3b15378a9d484625f1abc8c899ea681e001c4ab46f0c9b 2207 
xapian-core_1.2.22-3.dsc
 0a3ad580ea6e70742865f22675ed7a14d25afbb133cc5580a5f6a0e2d8d365e0 17216 
xapian-core_1.2.22-3.debian.tar.xz
Files:
 2b14f5f9dd5d82cbe1fdfe0d5a2eb786 2207 libs important xapian-core_1.2.22-3.dsc
 b57db2ae3ff354ddc5e10b63af075dc7 17216 libs important 
xapian-core_1.2.22-3.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJWzlf4AAoJEBgUewc7rSsHNXsQAMFwQ60oTdnKA9id/HVeeihs
3ySB4duK3D0tx0BS3oUcJZYp5k2Sn0E9GLz7G8XXMba1JK+vS1vzbReBTeCh1f3b
fzgpPEYl+JdEynlhiVLMb0YUK/rmm5kmUGCGC0srNy3bb9km4m2lmUdq8pOxJlyS
nPexYwz2F9b67kRJgYhdi0gxQ4JZtRmZRKJGlaciW18GpeX5dfMSFon88ah9DeMJ
JbNeo6lYEgQkD5i5GeEvotOESSYMwJNHPfbS9YQ7wvSdpO7n3d0FHSlhorOdz4xe
hpcPq8DxuCxDOyJEMTUihCox+PSdvtkN3Glc7QxfVVCxptCZcGS0iMpgkb2OXKtH
CUCkJyjjKltJI/NbczxK0l5rtabI3BnDCcDOw4PwArPbMrSBbCAo1o4DUpegZu7g
KzRtdOGvgIAxaR2ANMomWnzspeuw5evRn9o1hVGAf0Z0LloNi1B1MGgAkuQc7wN9
tUdQ3lPgkygHt/l0jBLdXft5lq0wlyymJ9fDgI+ttyrm7rsWyxQjrOC3Yu9WXY7S
FIJ5p2gAoWN0hCIU/HPEBPsH04lfGXuvPt0rr35UqtSQPO/oqFmqDAd/DD/mYETl
LOXwVgDsa/GA/vdvJDcRDnJT0Tj8URFSrS2qZCpEcKZpnWV9Laj3dyvtWstoZRrt
659ou4x1pv2wumttXk1c
=KlzI
-END PGP SIGNATURE End Message ---

Bug#815056: libtesseract4: fails to upgrade from libtesseract3

[Jeff Breidenbach]

> There was an accidental ABI breakage a while ago
> And I thought that bumping to libtesseract4 was the right thing to do

...

 The important question is: How did this ABI break happen?
Upstream change or only an effect of the C++ transition?
> I had been assuming upstream change
> But actually I'm not sure how to tell
 well, the symbol demangles to
tesseract::TessBaseAPI::AnalyseLayout() so look and see if there's anything
changed there between the versions

...

 jbreiden: Wait a mo. The problem is far easier to solve
 Just move the body from  "PageIterator* AnalyseLayout() {
  +return AnalyseLayout(false);
  +  }" from the header into the .cpp
 this function was accidentally inlined in the refactoring
 then you should have the old ABI again
 but incompatible with upstream
 Well, it is a change that can be done upstream
 All old code continues working
 even code built against the broken version, as those have that
function inlined

...

> Okay, I'll try it. I'll call the resulting package libtesseract3.
 Yes, then you could just rename it back entirely and all trouble
is gone
> Do I need to do something special to get rid of libtesseract4?
 that's certainly the cleanest solution you could hope for
 jbreiden: You could break/replace that. not sure if worth the
trouble

Bug#815132: marked as done (tesseract-ocr: link against libept5, libept4 is gone)

[Debian Bug Tracking System]

Your message dated Thu, 25 Feb 2016 01:47:04 +0100
with message-id <56ce4f08.5060...@debian.org>
and subject line Re: tesseract-ocr: link against libept5, libept4 is gone
has caused the Debian Bug report #815132,
regarding tesseract-ocr: link against libept5, libept4 is gone
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.)


-- 
815132: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815132
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tesseract-ocr
Version: 3.04.01-2
Severity: serious

Dear Maintainer(s),

   since the liblept4 package has been replaced by liblept5,
tesseract-ocr is not installable in testing/sid.

Regards,
Jörg-Volker.
--- End Message ---
--- Begin Message ---
On Fri, 19 Feb 2016 09:15:01 +0100 =?UTF-8?Q?J=c3=b6rg-Volker_Peetz?=
 wrote:
>since the liblept4 package has been replaced by liblept5,
> tesseract-ocr is not installable in testing/sid.

Fixed by a binNMU in a clean environment.

Andreas--- End Message ---

Bug#815842: php-rrd source incorrectly references imagick-*

[Nishanth Aravamudan]

Source: php-rrd
Version: 2.0.0+1.1.3-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

debian/tests/control lists:

Test-Command: cd imagick-* && phpunit --verbose tests
Depends: php-cli, php-imagick, phpunit

which I believe has been copied unaltered from php-imagick. This
obviously fails with php-rrd.

-Nish

Bug#762133: marked as done (ruby-kakasi-ffi: FTBFS: can't load libkakasi.so (DL::DLError))

[Debian Bug Tracking System]

Your message dated Thu, 25 Feb 2016 00:38:28 +
with message-id 
and subject line Bug#762133: fixed in ruby-kakasi-ffi 1.0.2-1
has caused the Debian Bug report #762133,
regarding ruby-kakasi-ffi: FTBFS: can't load libkakasi.so (DL::DLError)
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.)


-- 
762133: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762133
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-kakasi-ffi
Version: 1.0.1-1
Severity: serious
Justification: fails to build from source

Builds of ruby-kakasi-ffi in minimal environments (notably, the
autobuilders) have been failing:

  /usr/lib/ruby/2.1.0/dl/import.rb:68:in `rescue in block in dlload': can't 
load libkakasi.so (DL::DLError)
from /usr/lib/ruby/2.1.0/dl/import.rb:65:in `block in dlload'
from /usr/lib/ruby/2.1.0/dl/import.rb:56:in `collect'
from /usr/lib/ruby/2.1.0/dl/import.rb:56:in `dlload'
from extconf.rb:49:in `block in '
from /«PKGBUILDDIR»/lib/kakasi/platform.rb:55:in `try_load'
from extconf.rb:46:in `'
from extconf.rb:8:in `'

Could you please declare a build dependency on libkakasi2-dev and
confirm with pbuilder or the like that you haven't missed any others?

Thanks!
--- End Message ---
--- Begin Message ---
Source: ruby-kakasi-ffi
Source-Version: 1.0.2-1

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

Debian distribution maintenance software
pp.
Christian Hofstaedtler  (supplier of updated ruby-kakasi-ffi 
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: Thu, 25 Feb 2016 00:11:50 +
Source: ruby-kakasi-ffi
Binary: ruby-kakasi-ffi
Architecture: source
Version: 1.0.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Christian Hofstaedtler 
Description:
 ruby-kakasi-ffi - KAKASI interface for Ruby with Fiddle/DL/FFI
Closes: 762133
Changes:
 ruby-kakasi-ffi (1.0.2-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version
   * Update Debian packaging using dh-make-ruby -w
   * Update Standards-Version to 3.9.7 (no source level changes)
   * Fix missing build dependency libkakasi2-dev (Closes: #762133)
   * Run tests without bundler
Checksums-Sha1:
 d640f421e27fa09c335294b138ece7b1668e903d 2101 ruby-kakasi-ffi_1.0.2-1.dsc
 c6a77238de9ecf858501de77f121b26f497bb182 6021 ruby-kakasi-ffi_1.0.2.orig.tar.gz
 598d3f47f116569e2c185ac3291a4c4f4f57c537 2688 
ruby-kakasi-ffi_1.0.2-1.debian.tar.xz
Checksums-Sha256:
 85192f6a75ee2c20400bcf191635eca080c7c9c97177dcd4445c3acab8788668 2101 
ruby-kakasi-ffi_1.0.2-1.dsc
 d93890018f7ed3785cf890e817fc2285bb97e2c0681cc8a7ec5eba940169d42f 6021 
ruby-kakasi-ffi_1.0.2.orig.tar.gz
 9524920a8de871be5ee6e8921a5e5a2aa6e17f916ebcfaa37cd8dc999f5cf689 2688 
ruby-kakasi-ffi_1.0.2-1.debian.tar.xz
Files:
 4f1290ce2cc1527b26d54f04c5fd39f5 2101 ruby optional ruby-kakasi-ffi_1.0.2-1.dsc
 09770706f93aba40982216bb754afdbb 6021 ruby optional 
ruby-kakasi-ffi_1.0.2.orig.tar.gz
 4e13fcfff2d6b55889a9b2e15007c250 2688 ruby optional 
ruby-kakasi-ffi_1.0.2-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWzkd/AAoJEFwT1tuTBS4DdAkP/3fe3dGvmSBEocRAoVe3Ie5s
QB4Li7Tr3FSmcQxrdIRfuE9i+d00EV0PhTxpME1RZp1jeDC/7HGOCb6IGSLCnEDj
Vhzn8egMS8ii5tzwRt96IwkvTFSDOxO5b6BWBtNqLkH5BXh5nCmPDq602iguQncR
Gh0Kd+nL8WliUzrKwrqcAe+E+2v2sOG7+5F5bi9FXJsRVMOu5YKAcrTPbD+CzsuH
eaJLa+j5bihMUNFSOEIpfF/bNF0ckBgoixlXzfvL4QLgbuz1QoSib+7SU7j91Jwm
bJXEcA31EAx9e0Ih/BiJWMeFpMgodcFhLgQAfgQzY9nZlfQ5XUTHGHaxaydRYrSe
MjAEyuTJTyrnLp0px43r68tn6tggEco80IgzfTBH7KPlINfUlGralV98NCpd34qw
bRg9AlSIvwLBqXUONVTcBzHxCOndV7Osz7EURpGMP0vjh93hruCZ7d1zVMrH6O4C
sPj0ukOUyBNlsJzg1tN9ssD+aZqUWEM81euzImIn1m7BIWYCUCIxdYYTgnn6YB/C
kOHrmQCWjWHP9mmnVQH7VL0rPkiamp7RIbx1y3QxZfaDdsAcB8OhRQ16FTLT5uM/
lbPAmNegc4PUwN73EeihEB0L38pp0o2CmIPbvVsHMet1P2OiOi1axG2LeXKBcKUW
QjTxK0fDxwZHzDLaQLOc
=qeV7
-END PGP 

Bug#815769: marked as done (ruby-kakasi-ffi: FTBFS against ruby2.3)

[Debian Bug Tracking System]

Your message dated Thu, 25 Feb 2016 00:38:28 +
with message-id 
and subject line Bug#762133: fixed in ruby-kakasi-ffi 1.0.2-1
has caused the Debian Bug report #762133,
regarding ruby-kakasi-ffi: FTBFS against ruby2.3
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.)


-- 
762133: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762133
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-kakasi-ffi
Version: 1.0.1-1
Severity: important

During a rebuild with ruby2.3 enabled, ruby-kakasi-ffi fails to build. Please 
make
sure it builds against ruby2.3, which will be the Ruby version in stretch.

The full build log can be found at
https://pkg-ruby-extras.alioth.debian.org/rebuilds/ruby2.3-build-logs/ruby-kakasi-ffi_1.0.1-1_amd64.txt
--- End Message ---
--- Begin Message ---
Source: ruby-kakasi-ffi
Source-Version: 1.0.2-1

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

Debian distribution maintenance software
pp.
Christian Hofstaedtler  (supplier of updated ruby-kakasi-ffi 
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: Thu, 25 Feb 2016 00:11:50 +
Source: ruby-kakasi-ffi
Binary: ruby-kakasi-ffi
Architecture: source
Version: 1.0.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Christian Hofstaedtler 
Description:
 ruby-kakasi-ffi - KAKASI interface for Ruby with Fiddle/DL/FFI
Closes: 762133
Changes:
 ruby-kakasi-ffi (1.0.2-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version
   * Update Debian packaging using dh-make-ruby -w
   * Update Standards-Version to 3.9.7 (no source level changes)
   * Fix missing build dependency libkakasi2-dev (Closes: #762133)
   * Run tests without bundler
Checksums-Sha1:
 d640f421e27fa09c335294b138ece7b1668e903d 2101 ruby-kakasi-ffi_1.0.2-1.dsc
 c6a77238de9ecf858501de77f121b26f497bb182 6021 ruby-kakasi-ffi_1.0.2.orig.tar.gz
 598d3f47f116569e2c185ac3291a4c4f4f57c537 2688 
ruby-kakasi-ffi_1.0.2-1.debian.tar.xz
Checksums-Sha256:
 85192f6a75ee2c20400bcf191635eca080c7c9c97177dcd4445c3acab8788668 2101 
ruby-kakasi-ffi_1.0.2-1.dsc
 d93890018f7ed3785cf890e817fc2285bb97e2c0681cc8a7ec5eba940169d42f 6021 
ruby-kakasi-ffi_1.0.2.orig.tar.gz
 9524920a8de871be5ee6e8921a5e5a2aa6e17f916ebcfaa37cd8dc999f5cf689 2688 
ruby-kakasi-ffi_1.0.2-1.debian.tar.xz
Files:
 4f1290ce2cc1527b26d54f04c5fd39f5 2101 ruby optional ruby-kakasi-ffi_1.0.2-1.dsc
 09770706f93aba40982216bb754afdbb 6021 ruby optional 
ruby-kakasi-ffi_1.0.2.orig.tar.gz
 4e13fcfff2d6b55889a9b2e15007c250 2688 ruby optional 
ruby-kakasi-ffi_1.0.2-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWzkd/AAoJEFwT1tuTBS4DdAkP/3fe3dGvmSBEocRAoVe3Ie5s
QB4Li7Tr3FSmcQxrdIRfuE9i+d00EV0PhTxpME1RZp1jeDC/7HGOCb6IGSLCnEDj
Vhzn8egMS8ii5tzwRt96IwkvTFSDOxO5b6BWBtNqLkH5BXh5nCmPDq602iguQncR
Gh0Kd+nL8WliUzrKwrqcAe+E+2v2sOG7+5F5bi9FXJsRVMOu5YKAcrTPbD+CzsuH
eaJLa+j5bihMUNFSOEIpfF/bNF0ckBgoixlXzfvL4QLgbuz1QoSib+7SU7j91Jwm
bJXEcA31EAx9e0Ih/BiJWMeFpMgodcFhLgQAfgQzY9nZlfQ5XUTHGHaxaydRYrSe
MjAEyuTJTyrnLp0px43r68tn6tggEco80IgzfTBH7KPlINfUlGralV98NCpd34qw
bRg9AlSIvwLBqXUONVTcBzHxCOndV7Osz7EURpGMP0vjh93hruCZ7d1zVMrH6O4C
sPj0ukOUyBNlsJzg1tN9ssD+aZqUWEM81euzImIn1m7BIWYCUCIxdYYTgnn6YB/C
kOHrmQCWjWHP9mmnVQH7VL0rPkiamp7RIbx1y3QxZfaDdsAcB8OhRQ16FTLT5uM/
lbPAmNegc4PUwN73EeihEB0L38pp0o2CmIPbvVsHMet1P2OiOi1axG2LeXKBcKUW
QjTxK0fDxwZHzDLaQLOc
=qeV7
-END PGP SIGNATURE End Message ---

Bug#815056: libtesseract4: fails to upgrade from libtesseract3

[Jeff Breidenbach]

Why? I was asked strongly by a Debian Developer in 794489 to
bump the libtesseract version. I suspect 742027 was related.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794489
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742027

I historically have a lot of trouble with transitions, and this one
sadly seems to be no exception.  Advice is appreciated.

Bug#814744: xapian-core: "Multi-Arch: no" gets rejected by dak

[Olly Betts]

Control: tag -1 +pending

On Sun, Feb 14, 2016 at 11:13:39PM +0100, Aurelien Jarno wrote:
> This package has been built successfully on the autobuilders, but it
> has then be rejected by dak with the following message:
> 
>   libxapian-dev_1.2.22-2_ppc64el.deb: Multi-Arch: no support in Debian is 
> broken (#768353)

#765353 was closed in November *2014*, so that no longer seems
relevant (at least for uploading to unstable as here).

> I think the default value being "no", the best is to actually drop this 
> entry from debian/control.

OK, I'll do that.

However it was lintian that directed me to mark the package as
"Multi-Arch: no" - I feel either dak or lintian needs changing.

Cheers,
Olly

Processed: Re: Bug#814744: xapian-core: "Multi-Arch: no" gets rejected by dak

[Debian Bug Tracking System]

Processing control commands:

> tag -1 +pending
Bug #814744 [src:xapian-core] xapian-core: "Multi-Arch: no" gets rejected by dak
Added tag(s) pending.

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

Bug#815649: marked as done (netty-tcnative fails to build on the buildds)

[Debian Bug Tracking System]

Your message dated Thu, 25 Feb 2016 00:06:59 +
with message-id 
and subject line Bug#815649: fixed in netty-tcnative 1.1.33.Fork14-1
has caused the Debian Bug report #815649,
regarding netty-tcnative fails to build on the buildds
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.)


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

Package: src:netty-tcnative
Version: 1.1.33.Fork12-1
Severity: serious
Tags: sid stretch

[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR]   The project io.netty:${artifactIdToUse}:1.1.33.Fork12 
(/«PKGBUILDDIR»/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM for 
io.netty:${artifactIdToUse}:1.1.33.Fork12: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
io.netty:netty-parent:pom:4.0.18.Final has not been downloaded from it before. 
and 'parent.relativePath' points at wrong local POM @ line 19, column 11 -> [Help 2]

[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
[ERROR] [Help 2] 
http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
dh_auto_test: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar 
-Dmaven.home=/usr/share/maven -Dmaven.multiModuleProjectDirectory=/«PKGBUILDDIR» 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/«PKGBUILDDIR»/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/«PKGBUILDDIR»/debian 
-Dmaven.repo.local=/«PKGBUILDDIR»/debian/maven-repo test returned exit code 1

debian/rules:6: recipe for target 'build-arch' failed
--- End Message ---
--- Begin Message ---
Source: netty-tcnative
Source-Version: 1.1.33.Fork14-1

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated netty-tcnative 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: Thu, 25 Feb 2016 00:35:21 +0100
Source: netty-tcnative
Binary: libnetty-tcnative-java libnetty-tcnative-jni
Architecture: source all amd64
Version: 1.1.33.Fork14-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 libnetty-tcnative-java - Tomcat native fork for Netty
 libnetty-tcnative-jni - Tomcat native fork for Netty (JNI library)
Closes: 815649
Changes:
 netty-tcnative (1.1.33.Fork14-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream release
 - Ignore the new *-static modules and build only openssl-dynamic
 - Updated the paths in debian/rules according to the code reorganization
   * Fixed the build failure when building the architecture dependent package
 only (Closes: #815649)
   * Use a secure Vcs-Git URL
Checksums-Sha1:
 fabe17519391c0a6b6703c7a46a28e2e0d7a6a37 2270 
netty-tcnative_1.1.33.Fork14-1.dsc
 943e3cd216f58279afc68d358a0c30fc3040002f 144428 
netty-tcnative_1.1.33.Fork14.orig.tar.xz
 64cb1f5334695c389087fdf21835683184792c83 5632 
netty-tcnative_1.1.33.Fork14-1.debian.tar.xz
 cfb3888567bdca9265b0695346ca70693d9d4abd 66124 
libnetty-tcnative-java_1.1.33.Fork14-1_all.deb
 4d49b5064a284af4e0f8d9cb799b299c0f14a3b8 328426 
libnetty-tcnative-jni-dbgsym_1.1.33.Fork14-1_amd64.deb
 262da36a92665adb308bfc4f3ef08b0ffd99bf05 52644 
libnetty-tcnative-jni_1.1.33.Fork14-1_amd64.deb
Checksums-Sha256:
 b7c604b5b5b89cd630020e4d1f2c7808d1c1bded39be655612fcd8da69fa8690 2270 

Processed: reassign 813143 to libatk-wrapper-java, forcibly merging 809087 813143 808860

[Debian Bug Tracking System]

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

> reassign 813143 libatk-wrapper-java
Bug #813143 [openjdk-7-jre-headless] openjdk-7-jre-headless: Please re-disable 
atk bridge
Bug #808860 [openjdk-7-jre-headless] netbeans: Periodic freezing with GTK+ 
look-and-feel
Bug reassigned from package 'openjdk-7-jre-headless' to 'libatk-wrapper-java'.
Bug reassigned from package 'openjdk-7-jre-headless' to 'libatk-wrapper-java'.
No longer marked as found in versions 7u91-2.6.3-0ubuntu0.14.04.1 and 
openjdk-7/7u91-2.6.3-1.
No longer marked as found in versions openjdk-7/7u91-2.6.3-1 and 
7u91-2.6.3-0ubuntu0.14.04.1.
Ignoring request to alter fixed versions of bug #813143 to the same values 
previously set
Ignoring request to alter fixed versions of bug #808860 to the same values 
previously set
> forcemerge 809087 813143 808860
Bug #809087 [libatk-wrapper-java] libatk-wrapper-java: Regression hangs 
Intellij Idea
Bug #808860 [libatk-wrapper-java] netbeans: Periodic freezing with GTK+ 
look-and-feel
Severity set to 'important' from 'grave'
Severity set to 'important' from 'grave'
Removed indication that 808860 affects netbeans
Removed indication that 813143 affects netbeans
Marked as found in versions java-atk-wrapper/0.33.3-5.
Marked as found in versions java-atk-wrapper/0.33.3-5.
Added tag(s) pending.
Added tag(s) pending.
Bug #813143 [libatk-wrapper-java] openjdk-7-jre-headless: Please re-disable atk 
bridge
Merged 808860 809087 813143
> thanks
Stopping processing here.

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

Processed (with 1 error): forcibly merging 809087 813143 808860

[Debian Bug Tracking System]

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

> forcemerge 809087 813143 808860
Bug #809087 [libatk-wrapper-java] libatk-wrapper-java: Regression hangs 
Intellij Idea
Unable to merge bugs because:
package of #808860 is 'openjdk-7-jre-headless' not 'libatk-wrapper-java'
package of #813143 is 'openjdk-7-jre-headless' not 'libatk-wrapper-java'
Failed to forcibly merge 809087: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Processed: reassign 815769 to src:ruby-kakasi-ffi, forcibly merging 762133 815769, tagging 762133

[Debian Bug Tracking System]

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

> reassign 815769 src:ruby-kakasi-ffi
Bug #815769 [ruby-kakasi-ffi] ruby-kakasi-ffi: FTBFS against ruby2.3
Bug reassigned from package 'ruby-kakasi-ffi' to 'src:ruby-kakasi-ffi'.
No longer marked as found in versions ruby-kakasi-ffi/1.0.1-1.
Ignoring request to alter fixed versions of bug #815769 to the same values 
previously set
> forcemerge 762133 815769
Bug #762133 [src:ruby-kakasi-ffi] ruby-kakasi-ffi: FTBFS: can't load 
libkakasi.so (DL::DLError)
Bug #815769 [src:ruby-kakasi-ffi] ruby-kakasi-ffi: FTBFS against ruby2.3
Severity set to 'serious' from 'important'
Marked as found in versions ruby-kakasi-ffi/1.0.1-1.
Merged 762133 815769
> tags 762133 + confirmed
Bug #762133 [src:ruby-kakasi-ffi] ruby-kakasi-ffi: FTBFS: can't load 
libkakasi.so (DL::DLError)
Bug #815769 [src:ruby-kakasi-ffi] ruby-kakasi-ffi: FTBFS against ruby2.3
Added tag(s) confirmed.
Added tag(s) confirmed.
> thanks
Stopping processing here.

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

Processed: reassign 815767 to src:ruby-fssm, forcibly merging 795041 815767

[Debian Bug Tracking System]

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

> reassign 815767 src:ruby-fssm
Bug #815767 [ruby-fssm] ruby-fssm: FTBFS against ruby2.3
Bug reassigned from package 'ruby-fssm' to 'src:ruby-fssm'.
No longer marked as found in versions ruby-fssm/0.2.10-2.
Ignoring request to alter fixed versions of bug #815767 to the same values 
previously set
> forcemerge 795041 815767
Bug #795041 [src:ruby-fssm] ruby-fssm: FTBFS: "monitor with default options" 
test fails: File.exists?
Bug #815767 [src:ruby-fssm] ruby-fssm: FTBFS against ruby2.3
Severity set to 'serious' from 'important'
Marked as found in versions ruby-fssm/0.2.10-2.
Added tag(s) stretch and sid.
Merged 795041 815767
> thanks
Stopping processing here.

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

Processed (with 1 error): forcibly merging 795041 815767

[Debian Bug Tracking System]

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

> forcemerge 795041 815767
Bug #795041 [src:ruby-fssm] ruby-fssm: FTBFS: "monitor with default options" 
test fails: File.exists?
Unable to merge bugs because:
package of #815767 is 'ruby-fssm' not 'src:ruby-fssm'
Failed to forcibly merge 795041: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Processed (with 1 error): forcibly merging 804499 815768

[Debian Bug Tracking System]

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

> forcemerge 804499 815768
Bug #804499 [src:ruby-gsl] ruby-gsl: GSL transition requires rebuild
Bug #805842 [src:ruby-gsl] ruby-gsl: Fails to build with GSL 2
Unable to merge bugs because:
package of #815768 is 'ruby-gsl' not 'src:ruby-gsl'
Failed to forcibly merge 804499: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Processed (with 2 errors): forcibly merging 762133 815769, tagging 762133

[Debian Bug Tracking System]

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

> forcemerge 762133 815769
Bug #762133 [src:ruby-kakasi-ffi] ruby-kakasi-ffi: FTBFS: can't load 
libkakasi.so (DL::DLError)
Unable to merge bugs because:
package of #815769 is 'ruby-kakasi-ffi' not 'src:ruby-kakasi-ffi'
Failed to forcibly merge 762133: Did not alter merged bugs.

> tags 762133 + confirmed
Failed to alter tags of Bug 762133: failed to get lock on 
/org/bugs.debian.org/spool/lock/762133 -- Unable to lock 
/org/bugs.debian.org/spool/lock/762133 Resource temporarily unavailable.
Unable to lock /org/bugs.debian.org/spool/lock/762133 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/762133 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/762133 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/762133 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/762133 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/762133 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/762133 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/762133 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
Unable to lock /org/bugs.debian.org/spool/lock/762133 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 629.
 at /usr/local/lib/site_perl/Debbugs/Common.pm line 587.

> thanks
Stopping processing here.

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

Processed: Re: #815775: zeroc-ice: FTBFS against ruby2.3

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #815775 [zeroc-ice] zeroc-ice: FTBFS against ruby2.3
Severity set to 'serious' from 'important'
> retitle -1 Build-Depends on unavailable packages mono-gmcs libmono2.0-cil
Bug #815775 [zeroc-ice] zeroc-ice: FTBFS against ruby2.3
Changed Bug title to 'Build-Depends on unavailable packages mono-gmcs 
libmono2.0-cil' from 'zeroc-ice: FTBFS against ruby2.3'

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

Processed: Re: #815765: remctl: FTBFS against ruby2.3

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #815765 [remctl] remctl: FTBFS against ruby2.3
Severity set to 'serious' from 'important'

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

Bug#815663: marked as done (libssh: CVE-2016-0739: Weak Diffie-Hellman secret generation)

[Debian Bug Tracking System]

Your message dated Wed, 24 Feb 2016 23:17:08 +
with message-id 
and subject line Bug#815663: fixed in libssh 0.6.3-4+deb8u2
has caused the Debian Bug report #815663,
regarding libssh: CVE-2016-0739: Weak Diffie-Hellman secret generation
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.)


-- 
815663: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815663
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libssh
Version: 0.4.5-3
Severity: grave
Tags: security upstream patch fixed-upstream

Hi,

the following vulnerability was published for libssh.

CVE-2016-0739[0]:
Weak Diffie-Hellman secret generation in libssh

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-0739
[1] https://www.libssh.org/2016/02/23/libssh-0-7-3-security-and-bugfix-release/

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: libssh
Source-Version: 0.6.3-4+deb8u2

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 23 Feb 2016 16:00:29 +0100
Source: libssh
Binary: libssh-4 libssh-gcrypt-4 libssh-dev libssh-gcrypt-dev libssh-dbg 
libssh-doc
Architecture: all source
Version: 0.6.3-4+deb8u2
Distribution: jessie-security
Urgency: high
Maintainer: Laurent Bigonville 
Changed-By: Salvatore Bonaccorso 
Closes: 815663
Description: 
 libssh-4   - tiny C SSH library (OpenSSL flavor)
 libssh-dbg - tiny C SSH library. Debug symbols
 libssh-dev - tiny C SSH library. Development files (OpenSSL flavor)
 libssh-doc - tiny C SSH library. Documentation files
 libssh-gcrypt-4 - tiny C SSH library (gcrypt flavor)
 libssh-gcrypt-dev - tiny C SSH library. Development files (gcrypt flavor)
Changes:
 libssh (0.6.3-4+deb8u2) jessie-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * CVE-2016-0739: Truncated Diffie-Hellman secret length (Closes: #815663)
Checksums-Sha1: 
 a830844974a7e6763d40f653b75fdadfcd962d73 2320 libssh_0.6.3-4+deb8u2.dsc
 8189255e0f684d36b7ca62739fa0cd5f1030a467 279492 libssh_0.6.3.orig.tar.xz
 304013847f4921fa0735386cf9df44e9fe366e1b 18684 
libssh_0.6.3-4+deb8u2.debian.tar.xz
 4713c90e3c6a923f9d54b5c0e211d948d6a806ea 199414 
libssh-doc_0.6.3-4+deb8u2_all.deb
Checksums-Sha256: 
 56093ce89933c72a571a2b74a43f1287a034109042958c01cb9718bdb8e409e0 2320 
libssh_0.6.3-4+deb8u2.dsc
 2bb5d7c595059f990a8915c190169257328ffa828ced0c05b09bbe186092cacb 279492 
libssh_0.6.3.orig.tar.xz
 2eb01665f2773e87110346001b0f28e72594b02de7aead185b0470da76c1e3cd 18684 
libssh_0.6.3-4+deb8u2.debian.tar.xz
 d4a6cb9fbdbd7ad1da46876dee32c5e8a626db7254b3ee1817f70be71d3dd648 199414 
libssh-doc_0.6.3-4+deb8u2_all.deb
Files: 
 b2eea797e389eee1cbb09f45dcd8ad38 2320 libs optional libssh_0.6.3-4+deb8u2.dsc
 66cf16e77f60913b4d54f18c92cdbf71 279492 libs optional libssh_0.6.3.orig.tar.xz
 4b441a2812976158e8ed609e0bb31686 18684 libs optional 
libssh_0.6.3-4+deb8u2.debian.tar.xz
 15fbc91840ac5d0c996678b22dca65e7 199414 doc optional 
libssh-doc_0.6.3-4+deb8u2_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJWzHc0AAoJEAVMuPMTQ89EV4kQAJiWvUtkaW+vynpJalWC2dPJ
RuqpPJgZqRh6Puq0ZMmaP0HTdXRvlamJKKDoA8qU9uNUH2sn/PjGlq90jKjO7Rog
0MWfbQauozQ5bZkcQPLb4BvF+MH/lu0xoLI6pzpJRhB/3ZkiT38UIbdlhiJ+7lc9
YXgSfhm0fxANzJe8jHIwx/apRdX1XAzetx6MT/QIMHECPH9nDoytSeLwz0KUCfEa
KJBhAUb3qcR3321tHeqFyGJSVlUoRXREzpgRBYwIXka8sLnpw/Vl95vkwCelK/Qt
rJMlj6Z0axky4WJbsFuS9odBPycUULx6oKctSLCc2jK4ZoGGc+7PMINchLC1j5Vx
mBBTRFY6bXb+QHhT8EWQ2Hp3PZ9FSDqSmjHsyptKVD5usFB1nIWKCTY6+AF1uQk8
OpO1xCW61uXnOlM/Q9yCGCwX+UBJwl8Eyibw6i65wZDCNB5Pxq8wSdWFeoa17BmF
KQge8JAkPeCGrgtMZyiee93XGxLri7QGV1G/8Ud42yjOhWK/qALmiImO4qCjdeAI

Bug#815663: marked as done (libssh: CVE-2016-0739: Weak Diffie-Hellman secret generation)

[Debian Bug Tracking System]

Your message dated Wed, 24 Feb 2016 23:18:25 +
with message-id 
and subject line Bug#815663: fixed in libssh 0.5.4-1+deb7u3
has caused the Debian Bug report #815663,
regarding libssh: CVE-2016-0739: Weak Diffie-Hellman secret generation
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.)


-- 
815663: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815663
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libssh
Version: 0.4.5-3
Severity: grave
Tags: security upstream patch fixed-upstream

Hi,

the following vulnerability was published for libssh.

CVE-2016-0739[0]:
Weak Diffie-Hellman secret generation in libssh

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-0739
[1] https://www.libssh.org/2016/02/23/libssh-0-7-3-security-and-bugfix-release/

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: libssh
Source-Version: 0.5.4-1+deb7u3

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 23 Feb 2016 16:23:48 +0100
Source: libssh
Binary: libssh-4 libssh-dev libssh-dbg libssh-doc
Architecture: source all amd64
Version: 0.5.4-1+deb7u3
Distribution: wheezy-security
Urgency: high
Maintainer: Laurent Bigonville 
Changed-By: Salvatore Bonaccorso 
Description: 
 libssh-4   - tiny C SSH library
 libssh-dbg - tiny C SSH library. Debug symbols
 libssh-dev - tiny C SSH library. Development files
 libssh-doc - tiny C SSH library. Documentation files
Closes: 815663
Changes: 
 libssh (0.5.4-1+deb7u3) wheezy-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * CVE-2016-0739: Truncated Diffie-Hellman secret length (Closes: #815663)
Checksums-Sha1: 
 17a5e233212ea15d9c520cd6d5324f30face2d12 2038 libssh_0.5.4-1+deb7u3.dsc
 429a29615657d14515af7a5df049558a19c82f93 12022 
libssh_0.5.4-1+deb7u3.debian.tar.gz
 7a129b0e41ab9578ad6efda8754d627d3990430f 273820 
libssh-doc_0.5.4-1+deb7u3_all.deb
 f5bab7cd6b075effc4981bae7c9fff916de98358 131162 
libssh-4_0.5.4-1+deb7u3_amd64.deb
 31b245b2817087a132465ff26518058be9cc59b7 184446 
libssh-dev_0.5.4-1+deb7u3_amd64.deb
 258483b50aa9ad3b6a96acecb705fef53f37934f 360890 
libssh-dbg_0.5.4-1+deb7u3_amd64.deb
Checksums-Sha256: 
 fbbdd26b19f1d0d5a5bdb38b20a7a91952364a6541d08eee54dd4f95f9ca83d4 2038 
libssh_0.5.4-1+deb7u3.dsc
 066588214af8f0047e4f74b15773c17c515ffe4b4b4831fd5b5c6db34a0d02fb 12022 
libssh_0.5.4-1+deb7u3.debian.tar.gz
 205ff7b037570b1298f9bbc8d9a4842ec299fb48a2f99c168a9de05250456577 273820 
libssh-doc_0.5.4-1+deb7u3_all.deb
 73e73397e067b8412c7e6e999b96ccbf95263b94df4859dd251b4082c1ec4912 131162 
libssh-4_0.5.4-1+deb7u3_amd64.deb
 96de663ccd5d124e4b8787f759572720dde61de8b6486de5926069bfeeac5bf1 184446 
libssh-dev_0.5.4-1+deb7u3_amd64.deb
 a7d69f7d2cf38c4b0e2bc889f8ed3c60d4fa0800bc8c7c370beef92c0e4ae59e 360890 
libssh-dbg_0.5.4-1+deb7u3_amd64.deb
Files: 
 183575b77dc43940ceb3f2aa16563b5a 2038 libs optional libssh_0.5.4-1+deb7u3.dsc
 5e812e589c3e7ebd415b2d8062869e86 12022 libs optional 
libssh_0.5.4-1+deb7u3.debian.tar.gz
 4704811d8cb09b4328b996da13da0ec3 273820 doc optional 
libssh-doc_0.5.4-1+deb7u3_all.deb
 4a459305ab870c7ec057c2bbf59f4e6a 131162 libs optional 
libssh-4_0.5.4-1+deb7u3_amd64.deb
 6b883bc75ea4cae05c6c103307fe54f1 184446 libdevel optional 
libssh-dev_0.5.4-1+deb7u3_amd64.deb
 6b5ec67b8eac17cc8c6f840d23c1dce5 360890 debug extra 
libssh-dbg_0.5.4-1+deb7u3_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJWzHo4AAoJEAVMuPMTQ89EguoQAJX3faWXbUZ174fvxj/N/Oa/
7SwNLQyhVN+RovU0nw1gvyqmdwarjL43R8IvQBo22aildNDdzyQ/QG+duz8Ybv5U
bF25ged0FtisVFNphA0Hrn0eprJtnOsHvnc8Dp/5evglCrCoDoWBoEmpM/A7QHg7

Bug#808860: netbeans: Periodic freezing with GTK+ look-and-feel

[Samuel Thibault]

Markus Koschany, on Wed 24 Feb 2016 23:31:01 +0100, wrote:
> Since you are still waiting for upstream's opinion and the packages are
> not tested yet, I suggest the following steps.

They are tested already, in various cases.  I'd just like to know
whether that fixes all known issues.

> 1. Revert this change as soon as possible
> 2. Ask on debian-java, or people who reported this issue to test the
>packages. I would suggest to write down what exactly should be
>installed and tested.

I don't believe 2. will happen properly.  It's only when using a package
everyday that bug reports show up.  That's why the default parameter was
set.

I was however simply not aware that this was posing so many problems: I
wasn't made aware of all the mentioned in #813143.

Really, I'll just upload the fixed java-atk-wrapper, it has been tested
quite well already.

Samuel

Bug#815838: linux-image-3.16.0-4-amd64: Boot randomly fails with "Initramfs unpacking failed", probably due to kaslr bug upstream

[Blake Miner]

Package: src:linux
Version: 3.16.7-ckt11-1+deb8u6
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

The operating system will boot up fine in most cases, but randomly, the kernel 
will panic on boot-up and display
"Initramfs unpacking failed: uncompression error"

I am running this kernel (I know that it's not quite up-to-date):
3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u6 (2015-11-09) x86_64 GNU/Linux

I believe that this problem is caused by a bug already fixed upstream by the 
Linux Kernel team but not yet
fixed in the Debian 3.16 kernel.

Please check out commit 664653016626d15d3e898aabd0785f1b785f6400
https://github.com/torvalds/linux/commit/664653016626d15d3e898aabd0785f1b785f6400

An excerpt of the commit message is as follows:

---
x86, kaslr: Prevent .bss from overlaping initrd"

When choosing a random address, the current implementation does not take into
account the reversed space for .bss and .brk sections. Thus the relocated kernel
may overlap other components in memory. 

The initrd image will then be overwritten by the memset during early
initialization:

[1.655204] Unpacking initramfs...
[1.662831] Initramfs unpacking failed: junk in compressed archive
---

This commit has not landed in 3.16, but it landed in 3.17.4 upstream AFAIK.

I will try to run the Linux 3.18 kernel on Debian jessie to see if the problem 
gets resolved, but since it is
difficult to reproduce, it may take some time...

Ideally, someone should patch the current 3.16 kernel for Debian jessie (maybe 
pull in the above-referenced commit).

-- Package-specific info:
** Version:
Linux version 3.16.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 
4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt11-1+deb8u6 (2015-11-09)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64 
root=UUID=d2f282d7-653f-4171-ba43-7f8880a54742 ro i915.modeset=0 fbcon=rotate:1 
8250.nr_uarts=6 quiet splash

** Tainted: PO (4097)
 * Proprietary module has been loaded.
 * Out-of-tree module has been loaded.

** Kernel log:
[13734.196472] [UFW BLOCK] IN=eth0 OUT= 
MAC=01:00:5e:00:00:01:04:a1:51:93:d7:30:08:00 SRC=192.168.1.1 DST=224.0.0.1 
LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=18447 PROTO=2 
[13759.464703] [UFW BLOCK] IN=eth0 OUT= 
MAC=01:00:5e:00:00:01:04:a1:51:93:d7:30:08:00 SRC=192.168.1.1 DST=224.0.0.1 
LEN=36 TOS=0x00 PREC=0xC0 TTL=1 ID=18448 PROTO=2 

** Model information
sys_vendor: NA
product_name: NA
product_version: NA
chassis_vendor: NA
chassis_version: NA
bios_vendor: American Megatrends Inc.
bios_version: B209S002
board_vendor: NA
board_name: NA
board_version: NA

** Loaded modules:
ip6t_REJECT
xt_hl
ip6t_rt
nf_conntrack_ipv6
nf_defrag_ipv6
ipt_REJECT
xt_LOG
xt_limit
xt_tcpudp
xt_addrtype
nf_conntrack_ipv4
nf_defrag_ipv4
xt_conntrack
ip6table_filter
ip6_tables
nf_conntrack_netbios_ns
nf_conntrack_broadcast
nf_nat_ftp
nf_nat
nf_conntrack_ftp
nf_conntrack
iptable_filter
ip_tables
x_tables
nvidia(PO)
rtsx_usb_ms
memstick
nls_utf8
nls_cp437
vfat
fat
snd_hda_codec_hdmi
arc4
snd_hda_codec_realtek
snd_hda_codec_generic
iwlmvm
mac80211
snd_hda_intel
ecb
iwlwifi
btusb
snd_hda_controller
cfg80211
bluetooth
iTCO_wdt
iTCO_vendor_support
snd_hda_codec
snd_hwdep
snd_pcm
snd_timer
snd
6lowpan_iphc
rfkill
soundcore
cp210x(O)
joydev
usbserial
coretemp
efi_pstore
drm
psmouse
shpchp
serio_raw
pcspkr
efivars
lpc_ich
ac
evdev
battery
i2c_i801
i2c_core
processor
parport_pc
ppdev
lp
parport
autofs4
ext4
crc16
mbcache
jbd2
sg
hid_generic
sd_mod
usbhid
hid
crc_t10dif
crct10dif_generic
crct10dif_common
usb_storage
rtsx_usb_sdmmc
mmc_core
rtsx_usb
mfd_core
ata_generic
ata_piix
ehci_pci
libata
uhci_hcd
xhci_hcd
ehci_hcd
scsi_mod
r8169
mii
usbcore
usb_common
fan
thermal
video
thermal_sys
button

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Atom Processor D2xxx/N2xxx DRAM 
Controller [8086:0bf3] (rev 04)
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: [40] Express (v1) Root Port (Slot+), MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- 
Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ 
TransPend-
LnkCap: Port #1, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit 
Latency L0s <256ns, L1 <4us
ClockPM- Surprise- LLActRep+ BwNot-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, 

Bug#808860: netbeans: Periodic freezing with GTK+ look-and-feel

[Markus Koschany]

Hello,

Am 24.02.2016 um 23:01 schrieb Samuel Thibault:
> Hello,
> 
> Markus Koschany, on Wed 24 Feb 2016 20:53:37 +0100, wrote:
>> I am also in favor of reverting the change that enabled the atk bridge
>> by default.
> 
> I'm in favor of fixing bugs instead of working around them.
> 
> I have been waiting for upstream's opinion on my proposed fix, but I
> guess at some point I'll just upload it to Debian, I can do it now if
> people feel it's about time.

I am also in favor of fixing bugs but we should also take the severity
of this issue and the priorities into account. I would definitely like
to see this issue fixed by having non-freezing GTK themed Java
applications and supporting the ATK bridge. But it is apparent that this
change was a regression and badly affects a lot of people.


> In the meantime, could people try the packages I have uploaded to
> 
> deb http://people.debian.org/~sthibault/tmp ./
> 
> to make sure that this fixes the issue?
> 
> Samuel


Since you are still waiting for upstream's opinion and the packages are
not tested yet, I suggest the following steps.

1. Revert this change as soon as possible
2. Ask on debian-java, or people who reported this issue to test the
   packages. I would suggest to write down what exactly should be
   installed and tested.
3. Wait for upstream's opinion / ping them again.
4. Upload when everything is well tested.

Regards,

Markus







signature.asc
Description: OpenPGP digital signature

Bug#815538: marked as done (postfix: Does not start after upgrading to 3.0.3-1 - instance conflicts)

[Debian Bug Tracking System]

Your message dated Wed, 24 Feb 2016 22:05:54 +
with message-id 
and subject line Bug#815047: fixed in postfix 3.0.4-3
has caused the Debian Bug report #815047,
regarding postfix: Does not start after upgrading to 3.0.3-1 - instance 
conflicts
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.)


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

After upgrading to 3.0.3 postfix fails to start with the following
error:

Starting Postfix Mail Transport Agent: postfixpostmulti: fatal: instance
/etc/postfix, shlib_directory=/usr/lib/postfix conflicts with instance
/etc/postfix, daemon_directory=/usr/lib/postfix

Downgrading to 2.11.3-1+b1 fixes this issue (and the reportbug tool
generated its information from that version; I've manually corrected
the above Version: header).


-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (200, 'testing')
Architecture: i386 (i686)

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

Versions of packages postfix depends on:
ii  adduser3.113+nmu3
ii  cpio   2.11+dfsg-5
ii  debconf [debconf-2.0]  1.5.58
ii  dpkg   1.18.4
ii  libc6  2.21-9
ii  libdb5.3   5.3.28-11
ii  libsasl2-2 2.1.26.dfsg1-14+b1
ii  libsqlite3-0   3.11.0-1
ii  libssl1.0.21.0.2f-2
ii  lsb-base   9.20160110
ii  netbase5.3
ii  ssl-cert   1.0.37

Versions of packages postfix recommends:
ii  python  2.7.11-1

Versions of packages postfix suggests:
ii  bsd-mailx [mail-reader]  8.1.2-0.20160123cvs-2
pn  dovecot-common   
ii  icedove [mail-reader]38.6.0-1
ii  libsasl2-modules 2.1.26.dfsg1-14+b1
ii  mailutils [mail-reader]  1:2.99.99-1
ii  mutt [mail-reader]   1.5.24-1+b1
pn  postfix-cdb  
ii  postfix-doc  3.0.3-1
pn  postfix-ldap 
pn  postfix-mysql
pn  postfix-pcre 
pn  postfix-pgsql
ii  procmail 3.22-25
ii  resolvconf   1.78
ii  s-nail [mail-reader] 14.8.6-1
pn  sasl2-bin
pn  ufw  

-- debconf information:
[ Note: I've manually stripped some information in the following
lines, even though I'm pretty sure this does not hide anything]
  postfix/rfc1035_violation: false
* postfix/sqlite_warning: true
* postfix/procmail: true
  postfix/master_upgrade_warning:
* postfix/protocols: ipv4
  postfix/transport_map_warning:
  postfix/bad_recipient_delimiter:
* postfix/chattr: true
* postfix/mynetworks: 127.0.0.0/8, 192.[stripped]
  postfix/nqmgr_upgrade_warning:
* postfix/mailbox_limit: 0
* postfix/root_address: robert
  postfix/not_configured:
* postfix/mydomain_warning: true
* postfix/retry_upgrade_warning: true
  postfix/tlsmgr_upgrade_warning:
  postfix/dynamicmaps_upgrade_warning:
* postfix/destinations: vox.[stripped], localhost.[stripped], localhost, vox
* postfix/recipient_delim: +
  postfix/relay_restrictions_warning:
* postfix/mailname: vox.[stripped]
  postfix/db_upgrade_warning: true
  postfix/kernel_version_warning:
* postfix/relayhost:
* postfix/main_mailer_type: Internet with smarthost
--- End Message ---
--- Begin Message ---
Source: postfix
Source-Version: 3.0.4-3

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

Debian distribution maintenance software
pp.
LaMont Jones  (supplier of updated postfix package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 24 Feb 2016 12:47:38 -0700
Source: postfix
Binary: postfix postfix-ldap postfix-cdb postfix-pcre postfix-mysql 
postfix-pgsql postfix-dev postfix-doc
Architecture: all amd64 source
Version: 3.0.4-3

Bug#815047: marked as done (postfix: Postfix fails to start after upgrade)

[Debian Bug Tracking System]

Your message dated Wed, 24 Feb 2016 22:05:54 +
with message-id 
and subject line Bug#815047: fixed in postfix 3.0.4-3
has caused the Debian Bug report #815047,
regarding postfix: Postfix fails to start after upgrade
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.)


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

Dear Maintainer,


After this morning's upgrade of Postfix from 2.11.3-1+b1 to 3.0.3-1, postfix 
refuses to start saying:

fatal: instance /etc/postfix, shlib_directory=/usr/lib/postfix conflicts with 
instance /etc/postfix, daemon_directory=/usr/lib/postfix

It seems from email threads on the archives that haveing shlib_directory and 
daemon_directory refer to the
same directory is now considered unacceptable. I have not set these variables 
explicitly in /etc/postfix/main.cf or/etc/postfix/
master.cf.

postconf -d indicates daemon_directory is set to /usr/lib/postfix from 
somewhere.


Copying /usr/lib/postfix to /usr/libexec/postifx and setting:

daemon_directory = /usr/libexec/postfix

in /etc/postfix/main.cf

allows the postfix server to run.


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

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

Versions of packages postfix depends on:
ii  adduser3.113+nmu3
ii  cpio   2.11+dfsg-5
ii  debconf [debconf-2.0]  1.5.58
ii  dpkg   1.18.4
ii  libc6  2.21-9
ii  libdb5.3   5.3.28-11
ii  libicu55   55.1-7
ii  libsasl2-2 2.1.26.dfsg1-14+b1
ii  libsqlite3-0   3.11.0-1
ii  libssl1.0.21.0.2f-2
ii  lsb-base   9.20160110
ii  netbase5.3
ii  ssl-cert   1.0.37

Versions of packages postfix recommends:
ii  python3  3.5.1-1

Versions of packages postfix suggests:
ii  bsd-mailx [mail-reader]8.1.2-0.20160123cvs-2
ii  dovecot-core [dovecot-common]  1:2.2.18-2+b1
ii  emacs24 [mail-reader]  24.5+1-6+b1
ii  libsasl2-modules   2.1.26.dfsg1-14+b1
ii  mutt [mail-reader] 1.5.24-1+b1
pn  postfix-cdb
pn  postfix-doc
pn  postfix-ldap   
pn  postfix-mysql  
pn  postfix-pcre   
pn  postfix-pgsql  
ii  procmail   3.22-25
pn  resolvconf 
ii  sasl2-bin  2.1.26.dfsg1-14+b1
pn  ufw

-- debconf information:
  postfix/destinations:
  postfix/mydomain_warning:
  postfix/procmail:
* postfix/main_mailer_type: No configuration
  postfix/mynetworks: 127.0.0.0/8 [:::127.0.0.0]/104 [::1]/128
  postfix/sqlite_warning:
  postfix/mailname: /etc/mailname
  postfix/mailbox_limit: 0
  postfix/relay_restrictions_warning:
  postfix/relayhost:
  postfix/retry_upgrade_warning:
  postfix/root_address:
  postfix/recipient_delim: +
  postfix/kernel_version_warning:
  postfix/tlsmgr_upgrade_warning:
  postfix/bad_recipient_delimiter:
  postfix/protocols:
  postfix/chattr: false
  postfix/not_configured:
  postfix/rfc1035_violation: false
--- End Message ---
--- Begin Message ---
Source: postfix
Source-Version: 3.0.4-3

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

Debian distribution maintenance software
pp.
LaMont Jones  (supplier of updated postfix package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 24 Feb 2016 12:47:38 -0700
Source: postfix
Binary: postfix postfix-ldap postfix-cdb postfix-pcre postfix-mysql 
postfix-pgsql postfix-dev postfix-doc
Architecture: all amd64 source
Version: 3.0.4-3
Distribution: unstable

Bug#815622: marked as done (Postfix fails to start after apt-get upgrade)

[Debian Bug Tracking System]

Your message dated Wed, 24 Feb 2016 22:05:54 +
with message-id 
and subject line Bug#815047: fixed in postfix 3.0.4-3
has caused the Debian Bug report #815047,
regarding Postfix fails to start after apt-get upgrade
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.)


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

After running apt-get upgrade, postfix fails to start due to this:

postmulti: fatal: instance /etc/postfix, shlib_directory=/usr/lib/postfix 
conflicts with instance /etc/postfix, daemon_directory=/usr/lib/postfix

Neither shlib_directory nor daemon_directory are mentioned in my /etc/postfix,
and I had not been using multi at all on this box.

If the new init script cannot handle having shlib_directory and daemon_directory
be identical, the defaults should not have them identical.

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

Kernel: Linux 3.2.0-4-amd64 (SMP w/8 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: sysvinit (via /sbin/init)

Versions of packages postfix depends on:
ii  adduser3.113+nmu3
ii  cpio   2.11+dfsg-5
ii  debconf [debconf-2.0]  1.5.58
ii  dpkg   1.18.4
ii  libc6  2.21-9
ii  libdb5.3   5.3.28-11
ii  libicu55   55.1-7
ii  libsasl2-2 2.1.26.dfsg1-14+b1
ii  libsqlite3-0   3.11.0-1
ii  libssl1.0.21.0.2f-2
ii  lsb-base   9.20160110
ii  netbase5.3
ii  ssl-cert   1.0.37

Versions of packages postfix recommends:
ii  python3  3.5.1-1

Versions of packages postfix suggests:
ii  bsd-mailx [mail-reader]8.1.2-0.20160123cvs-2
pn  dovecot-common 
ii  emacs24-nox [mail-reader]  24.5+1-6+b1
ii  libsasl2-modules   2.1.26.dfsg1-14+b1
ii  mutt [mail-reader] 1.5.24-1+b1
ii  postfix-cdb3.0.3-1
ii  postfix-doc3.0.3-1
pn  postfix-ldap   
pn  postfix-mysql  
ii  postfix-pcre   3.0.3-1
ii  postfix-pgsql  3.0.3-1
ii  procmail   3.22-25
pn  resolvconf 
ii  s-nail [mail-reader]   14.8.6-1
pn  sasl2-bin  
pn  ufw

-- debconf information:
  postfix/sqlite_warning:
  postfix/protocols: all
  postfix/relayhost:
  postfix/procmail: true
  postfix/mynetworks: 127.0.0.0/8 [::1]/128
  postfix/root_address:
  postfix/tlsmgr_upgrade_warning:
  postfix/mailbox_limit: 0
  postfix/recipient_delim: +
* postfix/main_mailer_type: Internet Site
  postfix/mydomain_warning:
  postfix/bad_recipient_delimiter:
  postfix/destinations: globe.jhcloos.com, localhost.jhcloos.com, localhost
  postfix/not_configured:
  postfix/kernel_version_warning:
  postfix/retry_upgrade_warning:
* postfix/mailname: globe.jhcloos.com
  postfix/rfc1035_violation: false
  postfix/chattr: false
  postfix/relay_restrictions_warning:
--- End Message ---
--- Begin Message ---
Source: postfix
Source-Version: 3.0.4-3

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

Debian distribution maintenance software
pp.
LaMont Jones  (supplier of updated postfix package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 24 Feb 2016 12:47:38 -0700
Source: postfix
Binary: postfix postfix-ldap postfix-cdb postfix-pcre postfix-mysql 
postfix-pgsql postfix-dev postfix-doc
Architecture: all amd64 source
Version: 3.0.4-3
Distribution: unstable
Urgency: medium
Maintainer: LaMont Jones 
Changed-By: LaMont Jones 
Closes: 815047
Description: 
 postfix- High-performance mail transport agent
 postfix-cdb - CDB map support for Postfix
 postfix-dev - 

Bug#815070: marked as done (postfix: does not start)

[Debian Bug Tracking System]

Your message dated Wed, 24 Feb 2016 22:05:54 +
with message-id 
and subject line Bug#815047: fixed in postfix 3.0.4-3
has caused the Debian Bug report #815047,
regarding postfix: does not start
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.)


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

After a dist-upgrade:

tglase@tglase-nb:~ $ fgrep postmulti /var/log/syslog.1
Feb 18 09:10:42 tglase-nb postmulti[7295]: fatal: instance /etc/postfix, 
shlib_directory=/usr/lib/postfix conflicts with instance /etc/postfix, 
daemon_directory=/usr/lib/postfix
tglase@tglase-nb:~ $ sudo /etc/init.d/postfix stop
Stopping Postfix Mail Transport Agent: postfixpostmulti: fatal: instance 
/etc/postfix, shlib_directory=/usr/lib/postfix conflicts with instance 
/etc/postfix, daemon_directory=/usr/lib/postfix
--- End Message ---
--- Begin Message ---
Source: postfix
Source-Version: 3.0.4-3

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

Debian distribution maintenance software
pp.
LaMont Jones  (supplier of updated postfix package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 24 Feb 2016 12:47:38 -0700
Source: postfix
Binary: postfix postfix-ldap postfix-cdb postfix-pcre postfix-mysql 
postfix-pgsql postfix-dev postfix-doc
Architecture: all amd64 source
Version: 3.0.4-3
Distribution: unstable
Urgency: medium
Maintainer: LaMont Jones 
Changed-By: LaMont Jones 
Closes: 815047
Description: 
 postfix- High-performance mail transport agent
 postfix-cdb - CDB map support for Postfix
 postfix-dev - Loadable modules development environment for Postfix
 postfix-doc - Documentation for Postfix
 postfix-ldap - LDAP map support for Postfix
 postfix-mysql - MySQL map support for Postfix
 postfix-pcre - PCRE map support for Postfix
 postfix-pgsql - PostgreSQL map support for Postfix
Changes:
 postfix (3.0.4-3) unstable; urgency=medium
 .
   [Scott Kitterman]
 .
   * Move libpostfix-*.so.1* to /usr/lib/postfix to match the specified value
 of shlib_directory
   * Set daemon_directory to usr/lib/postfix/sbin to match install location and
 to fix failure to start due to shlib_directory and daemon_directory
 pointing to the same location (Closes: #815047)
Checksums-Sha1: 
 4dc87a78922af3ac259dd8efbf9530c60ef838e4 2441 postfix_3.0.4-3.dsc
 ab4c3ff6c4cb79f275b0ca22b2097b6dea28acd0 177480 postfix_3.0.4-3.debian.tar.xz
 67e705bc6ae7d33d56bd4292bba04db92e08abef 2396 
postfix-cdb-dbgsym_3.0.4-3_amd64.deb
 679e91a3667998147b928001df2e7a0838366f67 301182 postfix-cdb_3.0.4-3_amd64.deb
 2d34f3f29a6f6ea9345b0310d2396d127898578c 97424 postfix-dbgsym_3.0.4-3_amd64.deb
 0e75a74264f29c5a06093601e111de6b7d79f3f4 404828 postfix-dev_3.0.4-3_all.deb
 077d067e2cd5574a8f98e81429ebfc6e8051bfb6 1143920 postfix-doc_3.0.4-3_all.deb
 4bc5f103e3c07471dd34c174abf117c7089900b2 3106 
postfix-ldap-dbgsym_3.0.4-3_amd64.deb
 b33651c00c628df46146f95b31e145ed9b1f1033 308892 postfix-ldap_3.0.4-3_amd64.deb
 e014ac6adc38b6ee0a5f90626523b80e04f0c5c2 2652 
postfix-mysql-dbgsym_3.0.4-3_amd64.deb
 ed3246ceda2cb82b9234fde85eb43a5c057ef443 302924 postfix-mysql_3.0.4-3_amd64.deb
 89fe2deb454869d504f40e6ac7283f13ae06bab1 2474 
postfix-pcre-dbgsym_3.0.4-3_amd64.deb
 3eab77cf8d660eff1ca002d6b1dd992898541d35 303114 postfix-pcre_3.0.4-3_amd64.deb
 f203712b0033e4c0f9f0af0477a289e10c3afa1b 2622 
postfix-pgsql-dbgsym_3.0.4-3_amd64.deb
 0804d716e85c0c8c40df8756483f424bbff64c23 302732 postfix-pgsql_3.0.4-3_amd64.deb
 8d92066982430052cbe836e09549d222337fa9bd 1408998 postfix_3.0.4-3_amd64.deb
Checksums-Sha256: 
 8b7e36389ba8906b65f3754f38bc12b18634dc334327c1e2f7e07923fdfda02e 2441 
postfix_3.0.4-3.dsc
 cf297b500b62a08766b8ef9fd52d85c8ae309abed3eae06450cd2924b20febb8 177480 
postfix_3.0.4-3.debian.tar.xz
 

Bug#815073: marked as done (netbeans: FTBFS with ClassNotFoundException svnclientadapter)

[Debian Bug Tracking System]

Your message dated Wed, 24 Feb 2016 22:01:46 +
with message-id 
and subject line Bug#815073: fixed in netbeans 8.1+dfsg2-1
has caused the Debian Bug report #815073,
regarding netbeans: FTBFS with ClassNotFoundException svnclientadapter
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.)


-- 
815073: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815073
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: netbeans
Version: 8.1+dfsg1-1
Severity: serious

Netbeans currently FTBFS in Sid with cannot access SVNClientInterface

There also two runtime errors with the slf4j.dummy module and jgit
which are probably not related.


/build/netbeans-8.1+dfsg2/libs.svnClientAdapter.svnkit/build/classes
[nb-javac] Compiling 1 source file to
/build/netbeans-8.1+dfsg2/libs.svnClientAdapter.svnkit/build/classes
[repeat] warning: [options] bootstrap class path not set in
conjunction with -source 1.6 [repeat]
/build/netbeans-8.1+dfsg2/libs.svnClientAdapter.svnkit/src/org/netbeans/libs/svnclientadapter/svnkit/SvnKitClientAdapterFactory.java:88:
error: cannot access SVNClientInterface [repeat]
SVNClientImpl.setRuntimeCredentialsStorage(null); [repeat]
^ [repeat]   class file for
org.tigris.subversion.javahl.SVNClientInterface not found [repeat]
/build/netbeans-8.1+dfsg2/libs.svnClientAdapter.svnkit/src/org/netbeans/libs/svnclientadapter/svnkit/SvnKitClientAdapterFactory.java:89:
error: cannot access ISVNClient [repeat]
org.tmatesoft.svn.core.javahl17.SVNClientImpl.setRuntimeCredentialsStorage(null);
[repeat] ^ [repeat]   class file for
org.apache.subversion.javahl.ISVNClient not found [repeat] 2 errors
[nbmerge] Failed to build target: all-libs.svnClientAdapter.svnkit



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

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

Versions of packages netbeans depends on:
ii  libnb-apisupport3-java 8.1+dfsg2-1
ii  libnb-ide14-java   8.1+dfsg2-1
ii  libnb-java5-java   8.1+dfsg2-1
ii  libnb-platform18-java  8.1+dfsg1-2
ii  openjdk-8-jdk [java8-sdk]  8u72-b05-6

netbeans recommends no packages.

netbeans suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: netbeans
Source-Version: 8.1+dfsg2-1

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated netbeans 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, 24 Feb 2016 19:24:16 +0100
Source: netbeans
Binary: libnb-absolutelayout-java libnb-apisupport3-java libnb-ide14-java 
libnb-java5-java netbeans
Architecture: source all
Version: 8.1+dfsg2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Markus Koschany 
Description:
 libnb-absolutelayout-java - Java LayoutManager to allow placement in absolute 
positions
 libnb-apisupport3-java - Common NetBeans Platform Development Related 
Libraries for NetBea
 libnb-ide14-java - Common Integrated Development Environment Libraries for 
NetBeans
 libnb-java5-java - Common Java Related Libraries for NetBeans
 netbeans   - Extensible Java IDE
Closes: 809256 815073
Changes:
 netbeans (8.1+dfsg2-1) unstable; urgency=medium
 .
   * Imported Upstream version 8.1+dfsg2.
 - Include html5doc.zip because it is free documentation.
   * Build-Depend on libhtml5parser-java. This fixes HTML parser exceptions and
 makes it possible to edit and work with HTML files. Thanks to Michael
 Cordingley for the report. (Closes: #809256)
   * Switch to libicu4j-4.4-java.
 This prevents a NoClassFound exception when parsing HTML5 documents.
   * Delete 

Bug#808860: netbeans: Periodic freezing with GTK+ look-and-feel

[Samuel Thibault]

Hello,

Markus Koschany, on Wed 24 Feb 2016 20:53:37 +0100, wrote:
> I am also in favor of reverting the change that enabled the atk bridge
> by default.

I'm in favor of fixing bugs instead of working around them.

I have been waiting for upstream's opinion on my proposed fix, but I
guess at some point I'll just upload it to Debian, I can do it now if
people feel it's about time.

In the meantime, could people try the packages I have uploaded to

deb http://people.debian.org/~sthibault/tmp ./

to make sure that this fixes the issue?

Samuel

Bug#789101: marked as done (FTBFS: gdk_pixbuf_new_from_inline is deprecated + -Werror)

[Debian Bug Tracking System]

Your message dated Wed, 24 Feb 2016 21:52:35 +
with message-id 
and subject line Bug#789101: fixed in gtkimageview 1.6.4+dfsg-1
has caused the Debian Bug report #789101,
regarding FTBFS: gdk_pixbuf_new_from_inline is deprecated + -Werror
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.)


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

Dear Maintainer,

The package fails to build due to specifying -Werror=deprecated-declarations,
and using something that has become deprecated in libgdk-pixbuf:

gtkimagescrollwin.c: In function ‘gtk_image_scroll_win_init’:
gtkimagescrollwin.c:297:9: error: ‘gdk_pixbuf_new_from_inline’ is deprecated 
(declared at /usr/include/gdk-pixbuf-2.0/gdk-pixbuf/gdk-pixbuf-core.h:314) 
[-Werror=deprecated-declarations]
 gdk_pixbuf_new_from_inline (-1, nav_button, FALSE, NULL);

The full build log can be seen on the Reproducible Builds builder:
https://reproducible.debian.net/rb-pkg/unstable/amd64/gtkimageview.html

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

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

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

Debian distribution maintenance software
pp.
Jeffrey Ratcliffe  (supplier of updated gtkimageview package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 24 Feb 2016 21:21:33 +0100
Source: gtkimageview
Binary: libgtkimageview0 libgtkimageview-dev
Architecture: source amd64
Version: 1.6.4+dfsg-1
Distribution: unstable
Urgency: low
Maintainer: Jeffrey Ratcliffe 
Changed-By: Jeffrey Ratcliffe 
Description:
 libgtkimageview-dev - image viewer widget for GTK+ (development files)
 libgtkimageview0 - image viewer widget for GTK+
Closes: 789101
Changes:
 gtkimageview (1.6.4+dfsg-1) unstable; urgency=low
 .
   * Replace gdk_pixbuf_new_from_inline() with gdk_pixbuf_new_from_resource()
 (Closes: #789101)
   * Corrected maintainer email address
   * Removed DM-Upload-Allowed flag
   * Bumped compat and depends debhelper to 9
   * + source/format 3.0 (quilt)
   * Bumped standards to 3.9.6 (no changes needed)
Checksums-Sha1:
 5a2db5d5818fc8481fff08acf4e03a0196593e75 1925 gtkimageview_1.6.4+dfsg-1.dsc
 5bbc2f1687a64f7e1cde1bf889feaa519ea825ea 4500 
gtkimageview_1.6.4+dfsg-1.debian.tar.xz
 5c4b4b4c5b850463a5aace77b9097c9130c83d27 325042 
libgtkimageview-dev_1.6.4+dfsg-1_amd64.deb
 32a986f094d1df56c7e21c5061d1163f05459776 111758 
libgtkimageview0-dbgsym_1.6.4+dfsg-1_amd64.deb
 bd897f7727ae7632aa6183922fd09bffa5521d15 27676 
libgtkimageview0_1.6.4+dfsg-1_amd64.deb
Checksums-Sha256:
 cad9a078b8703a7ea034960c78937c77a9812ce426d9acfff3b83a7cd077963b 1925 
gtkimageview_1.6.4+dfsg-1.dsc
 634e872aec59dc33e372d03d48f7f4f0e6e1b26389ef8aa8f82251f8012985a9 4500 
gtkimageview_1.6.4+dfsg-1.debian.tar.xz
 bfca453599ab1db38cbc460cc3b6e560e90e44aa7f540ae4ba8364d4fad2264c 325042 
libgtkimageview-dev_1.6.4+dfsg-1_amd64.deb
 9fb1b43db39df8474f52359f3d3386cc050a45aa7eb54e9a4313f06a1f648598 111758 
libgtkimageview0-dbgsym_1.6.4+dfsg-1_amd64.deb
 85fdc9a45d1398c29c13481ab098d0857efe4e2cbb25c08398b534a1407006db 27676 
libgtkimageview0_1.6.4+dfsg-1_amd64.deb
Files:
 72a15d6ea88b2d46bba8201314dd026d 1925 libs optional 
gtkimageview_1.6.4+dfsg-1.dsc
 677b5308675a6420e8aa93f752c4f7ed 4500 libs optional 
gtkimageview_1.6.4+dfsg-1.debian.tar.xz
 073bc5ed09d57560e276c1db2ea523af 325042 libdevel optional 

Bug#814331: repsnapper: nothing displayed in 3d window

[Luke Kenneth Casson Leighton]

> Hi Luke,
>
> Can you try "env LIBGL_ALWAYS_SOFTWARE=1 repsnapper" to see if it fixes?

 ok i can confirm that the latest version is working.  also the
(just-reported) bug with glib also goes away.  so that one can be
closed.

 l.

Bug#813406: WIP (was: Fwd: Proposed changes to jessie)

[Mathieu Parent]

Hello,

I've proposed the changes to -security, without response yet.

See below.

-- Forwarded message --
From: Mathieu Parent 
Date: 2016-02-24 22:24 GMT+01:00
Subject: Re: Proposed changes to jessie
To: t...@security.debian.org


2016-02-04 15:04 GMT+01:00 Mathieu Parent :
> Hello,

Pinging again.

> I have prepared security fixes for two Horde packages:
> - php-horde: https://bugs.debian.org/813573#26 XSS vulnerability in menu bar
Debdiff at: 
http://anonscm.debian.org/cgit/pkg-horde/PEAR/php-horde.git/diff/?id2=47c6d6e6ad0836d657eee75e36ef8dbd19c843d2=112b45b0403df87828e6cd620eb0e3d4fc3c7fa9

> - php-horde-core: https://bugs.debian.org/813590#23 XSS in
> Horde_Core_VarRenderer_Html
Debdiff at: 
http://anonscm.debian.org/cgit/pkg-horde/PEAR/php-horde-core.git/diff/?id2=d79e0d5424ba76351cde56701e061f91d241ec09=a98c8cb02edaaa0378771a7f21855aaafc883785

>
> Can I upload the two packages (this is already fixed in sid)?

Waiting for your answer.

> I have also prepared a ctdb regression update, which fix CTDB behavior
> under Linux after the fix for CVE-2015-8543:
> - https://bugs.debian.org/813406#25 ctdb, raw sockets and CVE-2015-8543

See 
http://anonscm.debian.org/cgit/pkg-samba/ctdb.git/commit/?h=debian-jessie=ec4e506686578cdf13b36ce18ec98cc5307b4e64

> Can I upload it?

Same.

> Can I make the same to wheezy once jessie is uploaded?

Same.

I think keeping those issues in place is not good.

Regards
--
Mathieu Parent

Processed: tagging 815171

[Debian Bug Tracking System]

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

> tags 815171 + pending
Bug #815171 [src:diffoscope] diffoscope: tests for directory are brittle
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: tagging 815592

[Debian Bug Tracking System]

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

> tags 815592 + confirmed pending
Bug #815592 [src:gpicview] gpicview: maintainer address bounces
Added tag(s) confirmed and pending.
> thanks
Stopping processing here.

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

Bug#782332: Please re-test

[Andreas Beckmann]

On 2016-02-21 16:08, Neil Williams wrote:
> I've just tried to reproduce this manually in a fresh Wheezy i386 VM,
> installing libgpod-nogtk-dev and upgrading to jessie. The upgrade
> proceeded normally.

I can still reproduce this issue in piuparts wheezy -> jessie i386
upgrades with --install-recommends. Without --install-recommends the
test passes (and always had).
On amd64 it passes regardless of the --install-recommends option.

Andreas

Bug#813143: netbeans: Periodic freezing with GTK+ look-and-feel

[Markus Koschany]

Control: reassign 808860 openjdk-7-jre-headless
Control: forcemerge 813143 808860
Control: affects 808860 netbeans

I am also in favor of reverting the change that enabled the atk bridge
by default. Bug #808860 is clearly a symptom of this change and all
users using Netbeans with GTK look theme are negatively affected
and the application becomes unusable.


Commenting out:

# assistive_technologies=org.GNOME.Accessibility.AtkWrapper

in /etc/java-7-openjdk/accessibility.properties

solved this issue.

Regards,

Markus



signature.asc
Description: OpenPGP digital signature

Processed: Re: netbeans: Periodic freezing with GTK+ look-and-feel

[Debian Bug Tracking System]

Processing control commands:

> reassign 808860 openjdk-7-jre-headless
Bug #808860 [netbeans] netbeans: Periodic freezing with GTK+ look-and-feel
Bug reassigned from package 'netbeans' to 'openjdk-7-jre-headless'.
No longer marked as found in versions netbeans/8.0.2+dfsg1-5.
Ignoring request to alter fixed versions of bug #808860 to the same values 
previously set
> forcemerge 813143 808860
Bug #813143 [openjdk-7-jre-headless] openjdk-7-jre-headless: Please re-disable 
atk bridge
Bug #813143 [openjdk-7-jre-headless] openjdk-7-jre-headless: Please re-disable 
atk bridge
Added tag(s) moreinfo.
Bug #808860 [openjdk-7-jre-headless] netbeans: Periodic freezing with GTK+ 
look-and-feel
Severity set to 'grave' from 'normal'
There is no source info for the package 'openjdk-7-jre-headless' at version 
'7u91-2.6.3-0ubuntu0.14.04.1' with architecture ''
Unable to make a source version for version '7u91-2.6.3-0ubuntu0.14.04.1'
Marked as found in versions 7u91-2.6.3-0ubuntu0.14.04.1 and 
openjdk-7/7u91-2.6.3-1.
Merged 808860 813143
> affects 808860 netbeans
Bug #808860 [openjdk-7-jre-headless] netbeans: Periodic freezing with GTK+ 
look-and-feel
Bug #813143 [openjdk-7-jre-headless] openjdk-7-jre-headless: Please re-disable 
atk bridge
Added indication that 808860 affects netbeans
Added indication that 813143 affects netbeans

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

Processed: Re: netbeans: Periodic freezing with GTK+ look-and-feel

[Debian Bug Tracking System]

Processing control commands:

> reassign 808860 openjdk-7-jre-headless
Bug #808860 [openjdk-7-jre-headless] netbeans: Periodic freezing with GTK+ 
look-and-feel
Bug #813143 [openjdk-7-jre-headless] openjdk-7-jre-headless: Please re-disable 
atk bridge
Ignoring request to reassign bug #808860 to the same package
Ignoring request to reassign bug #813143 to the same package
> forcemerge 813143 808860
Bug #813143 [openjdk-7-jre-headless] openjdk-7-jre-headless: Please re-disable 
atk bridge
Bug #808860 [openjdk-7-jre-headless] netbeans: Periodic freezing with GTK+ 
look-and-feel
Bug #808860 [openjdk-7-jre-headless] netbeans: Periodic freezing with GTK+ 
look-and-feel
Merged 808860 813143
> affects 808860 netbeans
Bug #808860 [openjdk-7-jre-headless] netbeans: Periodic freezing with GTK+ 
look-and-feel
Bug #813143 [openjdk-7-jre-headless] openjdk-7-jre-headless: Please re-disable 
atk bridge
Ignoring request to set affects of bug 808860 to the same value previously set
Ignoring request to set affects of bug 813143 to the same value previously set

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

Bug#787924: marked as done (node-crc: test failure Error: Use CoffeeScript.register())

[Debian Bug Tracking System]

Your message dated Wed, 24 Feb 2016 19:23:37 +
with message-id 
and subject line Bug#787924: fixed in node-crc 3.0.0-3
has caused the Debian Bug report #787924,
regarding node-crc: test failure Error: Use CoffeeScript.register()
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.)


-- 
787924: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787924
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-crc
Version: 3.0.0-2
Severity: important

Hello,

while rebuilding node-crc in a clean sid sbuild chroot, this error happens:

dh build
   dh_testdir
   dh_auto_configure
   debian/rules override_dh_auto_build
make[1]: Entering directory '/«PKGBUILDDIR»'
if [ ! -d lib.org ]; then mv lib lib.orig; fi
coffee --bare --output ./lib --compile ./src/*.coffee
make[1]: Leaving directory '/«PKGBUILDDIR»'
   debian/rules override_dh_auto_test
make[1]: Entering directory '/«PKGBUILDDIR»'
mocha -C test/*.spec.coffee

/usr/lib/coffee-script/lib/coffee-script/coffee-script.js:213
  throw new Error("Use CoffeeScript.register() or require the coffee-s
^
Error: Use CoffeeScript.register() or require the coffee-script/register module 
to require .coffee.md files.
  at Object.base.(anonymous function) [as .coffee] 
(/usr/lib/coffee-script/lib/coffee-script/coffee-script.js:213:17)
  at Module.load (module.js:356:32)
  at Function.Module._load (module.js:312:12)
  at Module.require (module.js:364:17)
  at require (module.js:380:17)
  at /usr/lib/nodejs/mocha/lib/mocha.js:172:27
  at Array.forEach (native)
  at Mocha.loadFiles (/usr/lib/nodejs/mocha/lib/mocha.js:169:14)
  at Mocha.run (/usr/lib/nodejs/mocha/lib/mocha.js:356:31)
  at Object. (/usr/lib/nodejs/mocha/bin/_mocha:366:16)
  at Module._compile (module.js:456:26)
  at Object.Module._extensions..js (module.js:474:10)
  at Module.load (module.js:356:32)
  at Function.Module._load (module.js:312:12)
  at Function.Module.runMain (module.js:497:10)
  at startup (node.js:119:16)
  at node.js:906:3

make[1]: *** [override_dh_auto_test] Error 8
debian/rules:19: recipe for target 'override_dh_auto_test' failed

Is mocha the problem ? node-crc ? coffeescript ?

Jérémy

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

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

Versions of packages node-crc depends on:
ii  nodejs  0.10.38~dfsg-1

node-crc recommends no packages.

node-crc suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: node-crc
Source-Version: 3.0.0-3

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

Debian distribution maintenance software
pp.
Thorsten Alteholz  (supplier of updated node-crc 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, 24 Feb   2016 18:04:02 +0100
Source: node-crc
Binary: node-crc
Architecture: source all
Version: 3.0.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Thorsten Alteholz 
Description:
 node-crc   - module for calculating Cyclic Redundancy Check (CRC)
Closes: 787924
Changes:
 node-crc (3.0.0-3) unstable; urgency=medium
 .
   * debian/control: add myself to uploaders
   * debian/control: use secure VCS-URLs
   * adapt patch -fix-tests.patch for coffeescript > 1.7
 (Closes: #787924)
Checksums-Sha1:
 1f9856e1bccef055213097c7c54a515c2fed2ea4 2175 node-crc_3.0.0-3.dsc
 dd796bfe449c4c38fe5d85da3f8b981c5f7eae2c 2744 node-crc_3.0.0-3.debian.tar.xz
 d1d43f5da0de454167978dbe426eeabd9c16ea96 8350 node-crc_3.0.0-3_all.deb
Checksums-Sha256:
 700ea1334df1f3ae1d5f79fe97324062da4c0eb92472ac1e90e3fc64f16f5ce8 2175 
node-crc_3.0.0-3.dsc
 

Bug#784614: marked as done ([openlp] Qt4's WebKit removal)

[Debian Bug Tracking System]

Your message dated Wed, 24 Feb 2016 19:23:51 +
with message-id 
and subject line Bug#784614: fixed in openlp 2.4-1
has caused the Debian Bug report #784614,
regarding [openlp] Qt4's WebKit removal
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.)


-- 
784614: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784614
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openlp
Severity: wishlist
User: debian-qt-...@lists.debian.org
Usertags: qt4webkit-removal
Control: block 784513 by -1

Hi! As you might know we the Qt/KDE team are preparing to remove Qt4's WebKit
as announced in [announce]. Your package seems to be using it via PyQt4's
QtWebKit module.

[announce] 


Basically we are about to get the last Qt4 point release and upstream is
migrating from WebKit to Blink in the Qt5 series, so we won't have much upstream
support for maintaining Qt4's WebKit (Qt5's WebKit is expected to stay supported
until Qt6).

In order to make this move, all packages directly or indirectly depending on
the Qt4's WebKit library have to either get ported to Qt5 or eventually get
removed from the Debian repositories.

Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5 
  port of your application
- if there are no activities regarding porting, investigate whether there are 
  suitable alternatives for your users
- if there is a Qt5/PyQt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian 
  archives, consider removing the Qt4 version

= Porting =

Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.

We also understand that there is still a lot of software still using Qt4. In
order to ease the transition time we have provided Wheezy backports for Qt5.

Don't forget to take a look at the C++ API changes page [apichanges] and the
PyQt4 vs PyQt5 differences page [pyqtchanges] whenever you start porting
your application.

[migration] http://pkg-kde.alioth.debian.org/packagingqtstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html
[pyqtchanges] http://pyqt.sourceforge.net/Docs/PyQt5/pyqt4_differences.html

For any questions and issues, do not hesitate to contact the Debian Qt/KDE 
team at debian-qt-...@lists.debian.org.

--
Dmitry Shachnev,
on behalf of the Qt4 and PyQt4 maintainers
--- End Message ---
--- Begin Message ---
Source: openlp
Source-Version: 2.4-1

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

Debian distribution maintenance software
pp.
Raoul Snyman  (supplier of updated openlp package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 23 Feb 2016 23:04:54 +0200
Source: openlp
Binary: openlp
Architecture: source
Version: 2.4-1
Distribution: unstable
Urgency: low
Maintainer: Raoul Snyman 
Changed-By: Raoul Snyman 
Description:
 openlp - Church lyrics projection application
Closes: 784614
Changes:
 openlp (2.4-1) unstable; urgency=low
 .
   * New upstream release
   * Migrate to PyQt5. Closes: #784614
   * Update copyright file
   * Fix patches for new upstream version
   * Fixed up insecure URLs to source and website
   * Disable running tests when packaging for now
Checksums-Sha1:
 68141366c67f89ce63c65dfaaa5fdf60bc5a92a2 1486 openlp_2.4-1.dsc
 b4f7492a9bb1a4f12b95a942e9448b3e65fb906e 7421504 openlp_2.4.orig.tar.gz
 84a25fa2f1ef0ec74cea46d5e18714be6eb97998 5696 openlp_2.4-1.debian.tar.xz
Checksums-Sha256:
 800fd804cd187e05289a49ebd7293a33a40a403b25c4b4dfdef09fe1cc717d65 1486 
openlp_2.4-1.dsc
 7af0d36b134deae68b13658e7be67596aeb5367c9cc9652315f2719429e80a7b 7421504 
openlp_2.4.orig.tar.gz
 ee31446b20a74a42d26c37eab540848b2c75467dfc061bb04d4827787f8eeb52 5696 
openlp_2.4-1.debian.tar.xz

Bug#815824: gerris: build_function uses wrong compiler

[Stephane Popinet]

Package: gerris
Version: 20131206+dfsg-5
Severity: grave
Tags: patch
Justification: renders package unusable

Dear Maintainer,

Gerris uses compilation in the background to evaluate user-defined functions in
parameter files. This is done through the /usr/share/gerris/build_function
script. Currently, the "serial" gerris package includes a build_function script
which uses 'mpicc' to compile, but mpicc is not a dependency of the package
(because the gerris executable itself is serial, not parallel). This causes all
user-defined functions to fail and thus very seriously limits the usability of
the package.

To reproduce the bug you can do

% wget
http://gerris.dalembert.upmc.fr/gerris/examples/examples/boussinesq/boussinesq.gfs
% gerris2D boussinesq.gfs

which will give

gerris: file `boussinesq.gfs' is not a valid simulation file
boussinesq.gfs:61:74: error compiling expression
/usr/share/gerris/build_function: 28: /usr/share/gerris/build_function: mpicc:
not found

The fix is simple, just replace 'mpicc' with 'gcc' on lines 7 and 8 of
/usr/share/gerris/build_function.

thanks for packaging Gerris!

Stephane



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

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

Versions of packages gerris depends on:
ii  libav-tools   6:11.4-1~deb8u1
ii  libc6 2.19-18+deb8u3
ii  libgcc1   1:4.9.2-10
ii  libgfortran3  4.9.2-10
ii  libgfs-1.3-2  20131206+dfsg-5
ii  libgfs-dev20131206+dfsg-5
ii  libglib2.0-0  2.42.1-1
ii  libgts-0.7-5  0.7.6+darcs121130-1.2
ii  libgts-dev0.7.6+darcs121130-1.2
ii  libquadmath0  4.9.2-10

Versions of packages gerris recommends:
ii  gfsview  20121130+dfsg-1

Versions of packages gerris suggests:
ii  python  2.7.9-1

-- no debconf information

Bug#812643: marked as done (jgit: FTBFS - 2 tests fail)

[Debian Bug Tracking System]

Your message dated Wed, 24 Feb 2016 18:59:15 +
with message-id 
and subject line Bug#812643: fixed in jgit 3.7.1-2
has caused the Debian Bug report #812643,
regarding jgit: FTBFS - 2 tests fail
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.)


-- 
812643: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812643
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: jgit
Version: 3.7.1-1
Severity: serious
Usertags: goto-cc

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

[...]
---
 T E S T S
---
Running org.eclipse.jgit.pgm.LsRemoteTest
Running org.eclipse.jgit.pgm.MergeTest
Running org.eclipse.jgit.pgm.CloneTest
Running org.eclipse.jgit.pgm.AddTest
Running org.eclipse.jgit.pgm.ConfigTest
Running org.eclipse.jgit.pgm.TagTest
Running org.eclipse.jgit.pgm.DescribeTest
Running org.eclipse.jgit.pgm.ArchiveTest
Running org.eclipse.jgit.pgm.FetchTest
Running org.eclipse.jgit.pgm.CLIGitCommandTest
Running org.eclipse.jgit.pgm.BranchTest
Running org.eclipse.jgit.pgm.CommitAndLogTest
Running org.eclipse.jgit.pgm.ReflogTest
Running org.eclipse.jgit.pgm.RepoTest
Running org.eclipse.jgit.pgm.CheckoutTest
Running org.eclipse.jgit.pgm.StatusTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.274 sec - in 
org.eclipse.jgit.pgm.CLIGitCommandTest
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further 
details.
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further 
details.
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further 
details.
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further 
details.
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further 
details.
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further 
details.
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further 
details.
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further 
details.
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further 
details.
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further 
details.
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further 
details.
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further 
details.
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further 
details.
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further 
details.
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger 

Processed: bug 815738 is forwarded to https://bugs.freedesktop.org/show_bug.cgi?id=92637

[Debian Bug Tracking System]

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

> forwarded 815738 https://bugs.freedesktop.org/show_bug.cgi?id=92637
Bug #815738 [src:libspectre] libspectre: FTBFS: spectre-gs.c:46:9: error: 
'e_Fatal' undeclared (first use in this function)
Set Bug forwarded-to-address to 
'https://bugs.freedesktop.org/show_bug.cgi?id=92637'.
> thanks
Stopping processing here.

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

Bug#815731: arandr: Doesn't work with the current version of xrandr

[Julien Cristau]

On Wed, Feb 24, 2016 at 09:57:13 +0100, chrysn wrote:

> hi kristof,
> 
> On Wed, Feb 24, 2016 at 09:05:16AM +0100, Kristof Csillag wrote:
> > Lately, xrandr has been updated to v1.5:
> > 
> > user@host:~$ xrandr --version
> > xrandr program version   1.5.0
> > Server reports RandR version 1.5
> > 
> > arandr doesn't like that at all:
> 
> thanks for spotting this, i'm working on getting out the fix.
> 
> > If this can't be fixed easily, then at a versioned dependency
> > should be added to the package. (It still won't be usable for sid,
> > but at least ppl will know.)
> 
> unfortunately, xrandr isn't released with its own version, and i missed
> the news about 1.5 being out.
> 
> julien, do you see any way from packaging side how i could declare a
> dependency on "xrandr << 1.5"? splitting out xrandr into its own
> versioned package would be quite some work for just one versioned
> dependency. would a "Provides: xrandr-1.5" be an option?
> 
ewww.  I don't think xrandr's output is really suitable for machine
consumption.  Can't you use the libXrandr API directly?

As for your question, the right thing at this point is probably to add
Breaks against current versions of arandr to x11-xserver-utils.  What
version of arandr is likely to have that issue fixed?

Cheers,
Julien

Bug#793607: FTBFS against QT5

[Gianfranco Costamagna]

Hi Daniele, I would like to sponsor and fix the package.
Something that comes to my mind:
Drop all at build dependencies, drop insighttoolkit and so the package from non 
intel anche (please don't restrict to and and 8386 only, in case itk4 starts to 
build everywhere e.g. Like it does on Ubuntu)Fix the qt5 build
Drop cdbs (nice to have I really don't understand it)
I would like to sponsor the package in the next few days if possible, to see it 
in testing soon and in the next Ubuntu LTD
Cheers
G.

On Tue, 12 Jan 2016 14:38:51 +0100 "Daniele E. Domenichelli" 
 wrote:
> pending 793607
> thanks
> 
> Hello Gert,
> 
> Thanks for the patch. Actually, I fixed this some time ago and I have
> the package ready for the upload, but it fails to build on testing
> because libinsighttoolkit-dev disappeared from testing.
> If you want to try, the package from git should be building now (you
> will have to use libinsighttoolkit-dev from unstable).
> 
> 
> Cheers,
>  Daniele
> 
> 
> 

Sent from Yahoo Mail on Android

Bug#815736: marked as done (graphicsmagick: FTBFS: debian/rules:138: recipe for target 'check-stamp' failed)

[Debian Bug Tracking System]

Your message dated Wed, 24 Feb 2016 18:22:43 +
with message-id 
and subject line Bug#815736: fixed in graphicsmagick 1.3.23-2
has caused the Debian Bug report #815736,
regarding graphicsmagick: FTBFS: debian/rules:138: recipe for target 
'check-stamp' failed
to be marked as done.

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

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


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

graphicsmagick fails to build from source in unstable/amd64:

  [..]

  PASS: utilities/tests/list.tap 14 - gm mogrify -list type
  
/home/lamby/temp/cdt.20160224080703.Sm74YzPPeX/graphicsmagick-1.3.23/utilities/.libs/lt-gm
 convert: Unrecognized list type (module).
  EXEC: 
/home/lamby/temp/cdt.20160224080703.Sm74YzPPeX/graphicsmagick-1.3.23/utilities/gm
 convert -list module
  ok 15 - gm convert -list module # SKIP requires MODULES support
  SKIP: utilities/tests/list.tap 15 - gm convert -list module # SKIP requires 
MODULES support
  
/home/lamby/temp/cdt.20160224080703.Sm74YzPPeX/graphicsmagick-1.3.23/utilities/.libs/lt-gm
 mogrify: Unrecognized list type (module).
  EXEC: 
/home/lamby/temp/cdt.20160224080703.Sm74YzPPeX/graphicsmagick-1.3.23/utilities/gm
 mogrify -list module
  ok 16 - gm mogrify -list module # SKIP requires MODULES support
  SKIP: utilities/tests/list.tap 16 - gm mogrify -list module # SKIP requires 
MODULES support
  
   end of test-suite.log 
  debian/rules:138: recipe for target 'check-stamp' failed
  make: *** [check-stamp] Error 1

  [..]

The full build log is attached.


Regards,

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


graphicsmagick.1.3.23-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: graphicsmagick
Source-Version: 1.3.23-2

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated graphicsmagick 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 24 Feb 2016 18:36:00 +0100
Source: graphicsmagick
Binary: graphicsmagick libgraphicsmagick-q16-3 libgraphicsmagick1-dev 
libgraphicsmagick++-q16-12 libgraphicsmagick++1-dev libgraphics-magick-perl 
graphicsmagick-imagemagick-compat graphicsmagick-libmagick-dev-compat 
graphicsmagick-dbg
Architecture: source amd64 all
Version: 1.3.23-2
Distribution: unstable
Urgency: low
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Description:
 graphicsmagick - collection of image processing tools
 graphicsmagick-dbg - format-independent image processing - debugging symbols
 graphicsmagick-imagemagick-compat - image processing tools providing 
ImageMagick interface
 graphicsmagick-libmagick-dev-compat - image processing libraries providing 
ImageMagick interface
 libgraphics-magick-perl - format-independent image processing - perl interface
 libgraphicsmagick++-q16-12 - format-independent image processing - C++ shared 
library
 libgraphicsmagick++1-dev - format-independent image processing - C++ 
development files
 libgraphicsmagick-q16-3 - format-independent image processing - C shared 
library
 libgraphicsmagick1-dev - format-independent image processing - C development 
files
Closes: 815736
Changes:
 graphicsmagick (1.3.23-2) unstable; urgency=low
 .
   * Add previously transient gsfonts build dependency (closes: #815736).
Checksums-Sha1:
 7f234a225c4203decf4fa5121eb3db46a362f24f 2804 graphicsmagick_1.3.23-2.dsc
 833b2a7be731039a453223cc371b22280677bf9b 136536 
graphicsmagick_1.3.23-2.debian.tar.xz
 0c6da17569227d27e9c01c660fc40e838051e772 3021548 

Bug#815736: graphicsmagick: FTBFS: debian/rules:138: recipe for target 'check-stamp' failed

[GCS]

Hi Chris,

On Wed, Feb 24, 2016 at 9:49 AM, Chris Lamb  wrote:
> graphicsmagick fails to build from source in unstable/amd64:
 Previously something automatically pulled in gsfonts, maybe
ghostscript itself. If you have time, you may check building all
packages that have ghostscript as build dependency.
Anyway, uploading the updated graphicsmagick package soon.

Thanks for the heads-up,
Laszlo/GCS

Bug#815157: marked as done (hfst-ospell: FTBFS on most architectures)

[Debian Bug Tracking System]

Your message dated Wed, 24 Feb 2016 17:43:51 +
with message-id 
and subject line Bug#815157: fixed in hfst-ospell 0.4.0~r4643-2
has caused the Debian Bug report #815157,
regarding hfst-ospell: FTBFS on most architectures
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.)


-- 
815157: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815157
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: hfst-ospell
Version: hfst-ospell-dev
Severity: serious
Justification: fails to build from source

Dear Maintainer,

hfst-ospell has failed to build for most architectures in experimental.

You can find the build logs at:

https://buildd.debian.org/status/package.php?p=hfst-ospell=experimental

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (450, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 4.3.0-1-686-pae (SMP w/1 CPU core)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: hfst-ospell
Source-Version: 0.4.0~r4643-2

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

Debian distribution maintenance software
pp.
Kartik Mistry  (supplier of updated hfst-ospell package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 24 Feb 2016 22:20:53 +0530
Source: hfst-ospell
Binary: hfst-ospell libhfstospell5 hfst-ospell-dev
Architecture: source amd64
Version: 0.4.0~r4643-2
Distribution: experimental
Urgency: low
Maintainer: Debian Science Team 

Changed-By: Kartik Mistry 
Description:
 hfst-ospell - Spell checker library and tool based on HFST
 hfst-ospell-dev - HFST spell checker development files
 libhfstospell5 - HFST spell checker runtime libraries
Closes: 815157
Changes:
 hfst-ospell (0.4.0~r4643-2) experimental; urgency=low
 .
   [ Tino Didriksen ]
   * Disable broken tests (closes: #815157)
 .
   [ Kartik Mistry ]
   * Update Standards-Version to 3.9.7
Checksums-Sha1:
 1cff812205d21a2d0a0b59318cd301d78e19eba4 2326 hfst-ospell_0.4.0~r4643-2.dsc
 e0c98f3dc763e2d9ec4e96fda3338a527cfb27dc 2968 
hfst-ospell_0.4.0~r4643-2.debian.tar.xz
 1294deac75c3fcf9ccd002f9cb757bad30889433 289942 
hfst-ospell-dbgsym_0.4.0~r4643-2_amd64.deb
 1764ed111d4ea4683463ad4c962203aa40aff426 24582 
hfst-ospell-dev_0.4.0~r4643-2_amd64.deb
 0abf0e92e4838b28a2c809981b3f52e783fb1b61 37000 
hfst-ospell_0.4.0~r4643-2_amd64.deb
 569df1e9fd9e21f86903a0769961e087de138369 706636 
libhfstospell5-dbgsym_0.4.0~r4643-2_amd64.deb
 9e0eb85956626d52eedb6ec081e17d41afa30dda 79624 
libhfstospell5_0.4.0~r4643-2_amd64.deb
Checksums-Sha256:
 dcca61946f9757ed70b259cf7de19e35a32fd1bfc19426e8d64760c1443a7f3f 2326 
hfst-ospell_0.4.0~r4643-2.dsc
 c0ea69c1b2c99d2caf05e59b6d607e0f15db4b2a08e11c684548d7b530b87700 2968 
hfst-ospell_0.4.0~r4643-2.debian.tar.xz
 686262b05218e3868a20df45feedc49387925fb34402d4b2009af6be8c91a9c8 289942 
hfst-ospell-dbgsym_0.4.0~r4643-2_amd64.deb
 8505ebacf7cff616f3bdbe0289700819f3cba5ba4680553ac0a44e34a7dd3dc1 24582 
hfst-ospell-dev_0.4.0~r4643-2_amd64.deb
 b8ffd987f5e3cc53db9af1d3ef3939cc196ff3de526cbfebd2691cca51c85b3a 37000 
hfst-ospell_0.4.0~r4643-2_amd64.deb
 274c4006b646d7cdcf281d5e571908543b69793abcbcaf8689138a00496d63d9 706636 
libhfstospell5-dbgsym_0.4.0~r4643-2_amd64.deb
 b222710f82805dcbf18e80423cb49c5ad542569dbecc444d8990f3a7eef7cabd 79624 
libhfstospell5_0.4.0~r4643-2_amd64.deb
Files:
 059b345c74c0bdb33f807176afb5a4fd 2326 science optional 
hfst-ospell_0.4.0~r4643-2.dsc
 d4eec92640e054ec899bf7ce434dfa73 2968 science optional 
hfst-ospell_0.4.0~r4643-2.debian.tar.xz
 ca1b5976b367b10ee33eeceef764d566 289942 debug extra 
hfst-ospell-dbgsym_0.4.0~r4643-2_amd64.deb
 8b75f19ae8d385a1f6d059ad1f843fcc 24582 devel optional 
hfst-ospell-dev_0.4.0~r4643-2_amd64.deb
 7f440af042f3a9ce72c0f0ab324e1e25 37000 science optional 

Bug#815814: urdfdom: FTBFS on several architectures

[Emilio Pozuelo Monfort]

Source: urdfdom
Version: 0.4.1-1
Severity: serious

Your package failed to build on several architectures with:

CMake Error at CMakeLists.txt:41 (find_package):
  Could not find a configuration file for package "urdfdom_headers" that is
  compatible with requested version "0.4".

  The following configuration files were considered but not accepted:

/usr/share/urdfdom_headers/cmake/urdfdom_headers-config.cmake, version: 
0.4.0 (64bit)

Logs at:

https://buildd.debian.org/status/logs.php?pkg=urdfdom=0.4.1-1

Emilio

Bug#814411: marked as done (all ruby-rjb tests fail on i386)

[Debian Bug Tracking System]

Your message dated Wed, 24 Feb 2016 16:55:10 +
with message-id 
and subject line Bug#814411: fixed in ruby-rjb 1.5.3-2
has caused the Debian Bug report #814411,
regarding all ruby-rjb tests fail on i386
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.)


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

Package: src:ruby-rjb
Version: 1.5.3-1
Severity: serious
Tags: sid stretch

===
Error: test_unbind(TestRjb): RuntimeError: Constants DL and Fiddle is not 
defined.
/scratch/packages/tmp/ruby-rjb-1.5.3/debian/ruby-rjb/usr/lib/ruby/vendor_ruby/rjb.rb:76:in 
`load'
/scratch/packages/tmp/ruby-rjb-1.5.3/debian/ruby-rjb/usr/lib/ruby/vendor_ruby/rjb.rb:76:in 
`load'

/scratch/packages/tmp/ruby-rjb-1.5.3/test/test.rb:21:in `setup'
===
E
===
Error: test_underscored_constant(TestRjb): RuntimeError: Constants DL and Fiddle 
is not defined.
/scratch/packages/tmp/ruby-rjb-1.5.3/debian/ruby-rjb/usr/lib/ruby/vendor_ruby/rjb.rb:76:in 
`load'
/scratch/packages/tmp/ruby-rjb-1.5.3/debian/ruby-rjb/usr/lib/ruby/vendor_ruby/rjb.rb:76:in 
`load'

/scratch/packages/tmp/ruby-rjb-1.5.3/test/test.rb:21:in `setup'
===


Finished in 0.042415471 seconds.
--
65 tests, 0 assertions, 0 failures, 65 errors, 0 pendings, 0 omissions, 0 
notifications

0% passed
--
1532.46 tests/s, 0.00 assertions/s
ERROR: Test "ruby2.2" failed. Exiting.
dh_auto_install: dh_ruby --install 
/scratch/packages/tmp/ruby-rjb-1.5.3/debian/ruby-rjb returned exit code 1

debian/rules:43: recipe for target 'override_dh_auto_install' failed
make[1]: *** [override_dh_auto_install] Error 1
--- End Message ---
--- Begin Message ---
Source: ruby-rjb
Source-Version: 1.5.3-2

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

Debian distribution maintenance software
pp.
Jérémy Bobbio  (supplier of updated ruby-rjb package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Wed, 24 Feb 2016 15:13:12 +0100
Source: ruby-rjb
Binary: ruby-rjb
Architecture: source amd64
Version: 1.5.3-2
Distribution: unstable
Urgency: high
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Jérémy Bobbio 
Description:
 ruby-rjb   - Ruby-Java bridge using Java Native Interface
Closes: 814411
Changes:
 ruby-rjb (1.5.3-2) unstable; urgency=high
 .
   * Add a patch to provide the right libjvm.so location on i386.
 (Closes: #814411)
Checksums-Sha1:
 5690ea4578468e87c4317af06ac6ffec401764a2 2024 ruby-rjb_1.5.3-2.dsc
 cd41cef4e94ed68a9760e0dc4319bf614e1f775f 5952 ruby-rjb_1.5.3-2.debian.tar.xz
 ded59b24c3295b0cdd9f9a34bb4fcfe4cd02cb61 80446 
ruby-rjb-dbgsym_1.5.3-2_amd64.deb
 74d7a3e703b49acc056da71f756b2a6fc525802f 38660 ruby-rjb_1.5.3-2_amd64.deb
Checksums-Sha256:
 d3e3d829dff4c997a4baccbb030c1081bfd3c58b7bdde4b78b235381ab2c90d0 2024 
ruby-rjb_1.5.3-2.dsc
 d6d3976cdd39e3ba0853134025fcf286efb4ab92f15c37d99202c56a3580e522 5952 
ruby-rjb_1.5.3-2.debian.tar.xz
 dc771aa2e7d73b046e2a45a1efaa39b314af1e066a4ebbca0f0c14085eaf1440 80446 
ruby-rjb-dbgsym_1.5.3-2_amd64.deb
 8bf085e1c8c9656c24f84b7462cd52fcc055a041816dbe1293c4dcf20cb557d9 38660 
ruby-rjb_1.5.3-2_amd64.deb
Files:
 e3c145b8b5688c0d4183fa2b2945cc67 2024 ruby optional ruby-rjb_1.5.3-2.dsc
 8bab9d6118c238b8e5b6bcce27c264aa 5952 ruby optional 
ruby-rjb_1.5.3-2.debian.tar.xz
 e46c51ed04b9776b5c137e2157bfaaad 80446 debug extra 
ruby-rjb-dbgsym_1.5.3-2_amd64.deb
 3d47aba3e31db54a24de95dfdde53c9c 38660 ruby optional ruby-rjb_1.5.3-2_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJWzbtAAAoJEEAsIlA9Nuk2jxAP/389Ld9oAl/tmK51uztASHjR

Processed: Re: [Aptitude-devel] Bug#815581: Bug#815581: aptitude crashes when trying to show information about packages that are not installed

[Debian Bug Tracking System]

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

> severity 815581 serious
Bug #815581 [aptitude] aptitude crashes when trying to show information about 
packages that are not installed
Bug #815810 [aptitude] "aptitude show pkgname" does not display information 
about non-installed packages
Severity set to 'serious' from 'important'
Severity set to 'serious' from 'important'
> kthxbye
Stopping processing here.

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

Bug#815359: marked as done (cups: build-depends on libslp-dev)

[Debian Bug Tracking System]

Your message dated Wed, 24 Feb 2016 16:34:54 +
with message-id 
and subject line Bug#815359: fixed in cups 2.1.3-2
has caused the Debian Bug report #815359,
regarding cups: build-depends on libslp-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.)


-- 
815359: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815359
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openslp-dfsg
Severity: serious

The last maintainer upload of openslp happened in 2007
and it's orphaned for 5.5 years now. The 1.2 branch is
completely abandoned upstream.

At the minimum the package should be upgraded to 2.0,
but the comment at
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2015-5177
suggests it's completely abandoned upstream.

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: cups
Source-Version: 2.1.3-2

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

Debian distribution maintenance software
pp.
Didier Raboud  (supplier of updated cups 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, 24 Feb 2016 13:55:29 +0100
Source: cups
Binary: libcups2 libcupsimage2 libcupscgi1 libcupsmime1 libcupsppdc1 cups 
cups-core-drivers cups-daemon cups-client cups-ipp-utils libcups2-dev 
libcupsimage2-dev libcupscgi1-dev libcupsmime1-dev libcupsppdc1-dev cups-bsd 
cups-common cups-server-common cups-ppdc cups-dbg
Architecture: source
Version: 2.1.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Printing Team 
Changed-By: Didier Raboud 
Description:
 cups   - Common UNIX Printing System(tm) - PPD/driver support, web interfa
 cups-bsd   - Common UNIX Printing System(tm) - BSD commands
 cups-client - Common UNIX Printing System(tm) - client programs (SysV)
 cups-common - Common UNIX Printing System(tm) - common files
 cups-core-drivers - Common UNIX Printing System(tm) - PPD-less printing
 cups-daemon - Common UNIX Printing System(tm) - daemon
 cups-dbg   - Common UNIX Printing System(tm) - debugging symbols
 cups-ipp-utils - Common UNIX Printing System(tm) - IPP developer/admin 
utilities
 cups-ppdc  - Common UNIX Printing System(tm) - PPD manipulation utilities
 cups-server-common - Common UNIX Printing System(tm) - server common files
 libcups2   - Common UNIX Printing System(tm) - Core library
 libcups2-dev - Common UNIX Printing System(tm) - Development files CUPS library
 libcupscgi1 - Common UNIX Printing System(tm) - CGI library
 libcupscgi1-dev - Common UNIX Printing System(tm) - Development files for CGI 
libra
 libcupsimage2 - Common UNIX Printing System(tm) - Raster image library
 libcupsimage2-dev - Common UNIX Printing System(tm) - Development files CUPS 
image li
 libcupsmime1 - Common UNIX Printing System(tm) - MIME library
 libcupsmime1-dev - Common UNIX Printing System(tm) - Development files MIME 
library
 libcupsppdc1 - Common UNIX Printing System(tm) - PPD manipulation library
 libcupsppdc1-dev - Common UNIX Printing System(tm) - Development files PPD 
library
Closes: 815359
Changes:
 cups (2.1.3-2) unstable; urgency=medium
 .
   * Drop unused libslp-dev Build-Dependency (Closes: #815359)
   * Bump Standards-Version to 3.9.7 without changes needed
Checksums-Sha1:
 aa568a45f5752392b8063c6349f19e6ffee21bff 3433 cups_2.1.3-2.dsc
 98009de34f8b93c168d1baf51b9c80835eb82707 348680 cups_2.1.3-2.debian.tar.xz
Checksums-Sha256:
 43ce814e24c7c24cecafd0d50b5d9e677a5904f3e9234f7f4221a30baae929c4 3433 
cups_2.1.3-2.dsc
 ba4e8a5f849be62f4823332d8cb4b7b5477dfdbf52ab48a1f7da9c61ed5ebdcb 348680 
cups_2.1.3-2.debian.tar.xz
Files:
 a88483279acee89ef29954969d349e35 3433 net optional cups_2.1.3-2.dsc
 f5d59d67155424901a8a268eb426bd17 348680 net optional cups_2.1.3-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQGcBAEBCgAGBQJWzbqiAAoJEIvPpx7KFjRVTxgL/3ubZSa/6ZUbMrBY1tnrLnl/
u48ed2BYk1vAMls1BuyLwaskfgfBVqA0T61kISsK+0a3xgcIGKW5yMYM7xSkzt4S

Bug#815735: marked as done (fio: FTBFS: libmtd.h:288:8: error: unknown type name 'uint8_t')

[Debian Bug Tracking System]

Your message dated Wed, 24 Feb 2016 16:35:05 +
with message-id 
and subject line Bug#815735: fixed in fio 2.6-1
has caused the Debian Bug report #815735,
regarding fio: FTBFS: libmtd.h:288:8: error: unknown type name 'uint8_t'
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.)


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

fio fails to build from source in unstable/amd64:

  [..]

  CC engines/e4defrag.o
  CC engines/splice.o
  CC engines/rbd.o
  CC engines/mtd.o
  CC lib/libmtd.o
  CC lib/libmtd_legacy.o
  In file included from lib/libmtd_legacy.c:38:0:
  lib/libmtd.h:288:8: error: unknown type name 'uint8_t'
  uint8_t mode);
  ^
  lib/libmtd.h:305:4: error: unknown type name 'uint64_t'
  uint64_t start, uint64_t length, void *data);
  ^
  lib/libmtd.h:305:20: error: unknown type name 'uint64_t'
  uint64_t start, uint64_t length, void *data);
  ^
  lib/libmtd.h:322:5: error: unknown type name 'uint64_t'
   uint64_t start, uint64_t length, void *data);
   ^
  lib/libmtd.h:322:21: error: unknown type name 'uint64_t'
   uint64_t start, uint64_t length, void *data);
   ^
  Makefile:287: recipe for target 'lib/libmtd_legacy.o' failed
  make[1]: *** [lib/libmtd_legacy.o] Error 1
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160224080541.mSFrnTpDmm/fio-2.2.10'
  dh_auto_build: make -j1 returned exit code 2
  debian/rules:15: 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
   `-


fio.2.2.10-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: fio
Source-Version: 2.6-1

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

Debian distribution maintenance software
pp.
Martin Steigerwald  (supplier of updated fio 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 24 Feb 2016 10:47:40 +0100
Source: fio
Binary: fio gfio
Architecture: source amd64
Version: 2.6-1
Distribution: unstable
Urgency: medium
Maintainer: Martin Steigerwald 
Changed-By: Martin Steigerwald 
Description:
 fio- flexible I/O tester
 gfio   - flexible I/O tester - gui frontend
Closes: 815735
Changes:
 fio (2.6-1) unstable; urgency=medium
 .
   * Imported Upstream version 2.6.
   * patches/fix-ftbfs-with-libmtd.h: Fix FTBFS: libmtd.h:288:8: error:
 unknown type name 'uint8_t'. Thanks Chris. (Closes: #815735)
   * control:
 - Updated to standards version 3.9.7. No changes needed.
 - Made Vcs-Browser and Vcs-Git URLs secure
   - copyright:
 - Adapted path for library files that are now in oslib.
 - fio.1: Fixed license to GPL-2. Don´t know how I came to the
   conclusion that it would be GPL-2+, if the rest without any
   license specified is GPL-2.
 - rate_submit.c: Added copyright.
Checksums-Sha1:
 a9ed3d91f1e62552b1171f899e12e8c4ac2b9b12 1975 fio_2.6-1.dsc
 a57520f1e861244710c7a7b36052d789fa741f37 605277 fio_2.6.orig.tar.gz
 a0c6159d40e0746c604264cea50280ae86aae36e 8496 fio_2.6-1.debian.tar.xz
 64379932204813f93f88f36ecd367e881110d4f6 1204774 fio-dbgsym_2.6-1_amd64.deb
 67b03e6eff119641f081a3836c89490c5ef8b4bb 378448 fio_2.6-1_amd64.deb
 823dcf4a2d456f2ad73a9308854eaea57a27b13c 1262746 gfio-dbgsym_2.6-1_amd64.deb
 1beacd2555a1e6c69761354314684460adde9e35 308652 gfio_2.6-1_amd64.deb
Checksums-Sha256:
 fa89434c56b2f4411a6787e35a65fc7b9a4c4e007115ea5f3747b1ac38125bad 1975 

Bug#815809: lldb-3.8: lldb binary not included in the package any more

[Vadim Zeitlin]

Package: lldb-3.8
Version: 1:3.8~+rc2-1~exp1
Severity: grave
Justification: renders package unusable

The latest version of the package contains symlinks /usr/bin/lldb-3.8 and
/usr/lib/llvm-3.8/bin/lldb but not the actual lldb binary
/usr/lib/llvm-3.8/bin/lldb-3.8.0, so it basically doesn't provide the
debugger at all.

I don't know if this is a regression or not because I had been previously
using the packages from http://llvm.org/apt/unstable/ which did include
lldb (but didn't include ASAN libraries which are available in Debian
packages, see https://llvm.org/bugs/show_bug.cgi?id=22757)

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

Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)
Shell: /bin/sh linked to /bin/dash
Init: unable to detect

Versions of packages lldb-3.8 depends on:
ii  libllvm3.8   1:3.8~+rc2-1~exp1
ii  llvm-3.8-dev 1:3.8~svn254193-1
ii  python   2.7.11-1
ii  python-lldb-3.8  1:3.8~svn254193-1

lldb-3.8 recommends no packages.

lldb-3.8 suggests no packages.

-- no debconf information

Bug#815734: ess: FTBFS: doc/newfeat.texi:29: Argument of @gobblespaces has an extra }.

[Kurt Hornik]

> Dirk Eddelbuettel writes:

> On 24 February 2016 at 09:48, Chris Lamb wrote:
> | Source: ess
> | Version: 15.09.2-1
> | Severity: serious
> | Justification: fails to build from source
> | User: reproducible-bui...@lists.alioth.debian.org
> | Usertags: ftbfs
> | X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
> | 
> | Dear Maintainer,
> | 
> | ess fails to build from source in unstable/amd64:
> | 
> |   [..]
> | 
> |   LC_ALL=C LANG=en makeinfo --html --no-split 
> --css-include=atouchofstyle.css -o html/news.html allnews.texi
> |   LANG=C texi2dvi --pdf ess.texi
> |   This is pdfTeX, Version 3.14159265-2.6-1.40.16 (TeX Live 2015/Debian) 
> (preloaded format=pdfetex)
> |restricted \write18 enabled.
> |   entering extended mode
> |   (./ess.texi (/usr/share/texmf/tex/texinfo/texinfo.tex
> |   Loading texinfo [version 2016-02-05.07.deb1]: pdf, fonts, markup, glyphs,
> |   page headings, tables, conditionals, indexing, sectioning, toc, 
> environments,
> |   defuns, macros, cross references, insertions,
> |   (/usr/share/texlive/texmf-dist/tex/generic/epsf/epsf.tex
> |   This is `epsf.tex' v2.7.4 <14 February 2011>
> |   ) localization, formatting, and turning on texinfo input format.)
> |   
> (/home/lamby/temp/cdt.20160224075206.p19g7Umwps/ess-15.09.2/doc/ess-defs.texi)
> |   (../VERSION) [1{/var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map}] [-1]
> |   Chapter 1
> |   
> (/home/lamby/temp/cdt.20160224075206.p19g7Umwps/ess-15.09.2/doc/currfeat.texi
> |   [1]) Cross reference values unknown; you must run TeX again. [2]
> |   
> (/home/lamby/temp/cdt.20160224075206.p19g7Umwps/ess-15.09.2/doc/newfeat.texi
> |   [3]
> |   
> /home/lamby/temp/cdt.20160224075206.p19g7Umwps/ess-15.09.2/doc/newfeat.texi:29:
> |Argument of @gobblespaces has an extra }.
> |
> |   @par 
> |
> |  }
> |   @doacronym ...#3@finish ->{@selectfonts @lsize #1}
> | @def @temp {#2}@ifx 
> @temp ...
> |   l.1 @acronym{ESS@gobblespaces }
> |  @texinfoc
> |   @scanmacro ...atspaces }@scantokens {#1@texinfoc }
> | @aftermacro 
> |   l.29 @item @ESS{}
> |: A test framework has been set up.
> |   ? Runaway argument?
> |   
> /home/lamby/temp/cdt.20160224075206.p19g7Umwps/ess-15.09.2/doc/newfeat.texi:29:
> |Paragraph ended before @gobblespaces was complete.
> |
> |  @par 
> |
> |  }
> |   @doacronym ...#3@finish ->{@selectfonts @lsize #1}
> | @def @temp {#2}@ifx 
> @temp ...
> |   l.1 @acronym{ESS@gobblespaces }
> |  @texinfoc
> |   @scanmacro ...atspaces }@scantokens {#1@texinfoc }
> | @aftermacro 
> |   l.29 @item @ESS{}
> |: A test framework has been set up.
> |   ? 
> /home/lamby/temp/cdt.20160224075206.p19g7Umwps/ess-15.09.2/doc/newfeat.texi:72:
> |Argument of @gobblespaces has an extra }.
> |
> |   @par 
> |
> |  }
> |   @doacronym ...#3@finish ->{@selectfonts @lsize #1}
> | @def @temp {#2}@ifx 
> @temp ...
> |   l.1 @acronym{ESS@gobblespaces @gobblespaces }
> |@texinfoc
> |   @scanmacro ...atspaces }@scantokens {#1@texinfoc }
> | @aftermacro 
> |   @w #1->@leavevmode @hbox {#1
> |   }
> |   ...
> |   l.72 @item @iESS{}
> | : For naming inferior processes, ESS can use 
> @code{project...
> |   
> |   ? 
> |   
> /home/lamby/temp/cdt.20160224075206.p19g7Umwps/ess-15.09.2/doc/newfeat.texi:72:
> |Emergency stop.
> |
> |   @par 
> |
> |  }
> |   @doacronym ...#3@finish ->{@selectfonts @lsize #1}
> | @def @temp {#2}@ifx 
> @temp ...
> |   l.1 @acronym{ESS@gobblespaces @gobblespaces }
> |@texinfoc
> |   @scanmacro ...atspaces }@scantokens {#1@texinfoc }
> | @aftermacro 
> |   @w #1->@leavevmode @hbox {#1
> |   }
> |   ...
> |   l.72 @item @iESS{}
> | : For naming inferior processes, ESS can use 
> @code{project...
> |   
> |   
> /home/lamby/temp/cdt.20160224075206.p19g7Umwps/ess-15.09.2/doc/newfeat.texi:72:
> | ==> Fatal error occurred, no output PDF file produced!
> |   Transcript written on ess.log.
> |   /usr/bin/texi2dvi: pdfetex exited with bad status, quitting.

> Might be the same texinfo 6.1 issue that also bit us in R.

Another Texinfo 6.1 issue.  The one breaking R is a change to texi2dvi,
which for the purpose of building R 

Bug#815804: linux-image-4.4.0-1-amd64: kernel-image-4.4.0-1-amd64 does not boot on X751L asus laptop

[maderios]

Package: src:linux
Version: 4.4.2-3
Severity: grave
Tags: newcomer
Justification: renders package unusable

Dear Maintainer,

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

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

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



-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: ASUSTeK COMPUTER INC.
product_name: X751LB
product_version: 1.0   
chassis_vendor: ASUSTeK COMPUTER INC.
chassis_version: 1.0   
bios_vendor: American Megatrends Inc.
bios_version: X751LB.604
board_vendor: ASUSTeK COMPUTER INC.
board_name: X751LB
board_version: 1.0   

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Broadwell-U Host Bridge -OPI 
[8086:1604] (rev 09)
Subsystem: ASUSTeK Computer Inc. Broadwell-U Host Bridge -OPI 
[1043:241a]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: bdw_uncore

00:02.0 VGA compatible controller [0300]: Intel Corporation Broadwell-U 
Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Broadwell-U Integrated Graphics 
[1043:241a]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR-  [disabled]
Capabilities: 
Kernel driver in use: i915
Kernel modules: i915

00:03.0 Audio device [0403]: Intel Corporation Broadwell-U Audio Controller 
[8086:160c] (rev 09)
Subsystem: ASUSTeK Computer Inc. Broadwell-U Audio Controller 
[1043:241a]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

00:04.0 Signal processing controller [1180]: Intel Corporation Broadwell-U 
Camarillo Device [8086:1603] (rev 09)
Subsystem: ASUSTeK Computer Inc. Broadwell-U Processor Thermal 
Subsystem [1043:241a]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device

00:14.0 USB controller [0c03]: Intel Corporation Wildcat Point-LP USB xHCI 
Controller [8086:9cb1] (rev 03) (prog-if 30 [XHCI])
Subsystem: ASUSTeK Computer Inc. Wildcat Point-LP USB xHCI Controller 
[1043:201f]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci

00:16.0 Communication controller [0780]: Intel Corporation Wildcat Point-LP MEI 
Controller #1 [8086:9cba] (rev 03)
Subsystem: ASUSTeK Computer Inc. Wildcat Point-LP MEI Controller 
[1043:241a]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: mei_me
Kernel modules: mei_me

00:1b.0 Audio device [0403]: Intel Corporation Wildcat Point-LP High Definition 
Audio Controller [8086:9ca0] (rev 03)
Subsystem: ASUSTeK Computer Inc. Wildcat Point-LP High Definition Audio 
Controller [1043:138f]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

00:1c.0 PCI bridge [0604]: Intel Corporation Wildcat Point-LP PCI Express Root 
Port #1 [8086:9c90] (rev e3) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport
Kernel modules: shpchp

00:1c.2 PCI bridge [0604]: Intel Corporation Wildcat Point-LP PCI Express Root 
Port #3 [8086:9c94] (rev e3) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- 

Bug#814338: marked as done (armhf-20150422: Format partitions error for ext4/fat/jfs : Unknown symbol __getblk_gfp)

[Debian Bug Tracking System]

Your message dated Wed, 24 Feb 2016 15:13:33 +
with message-id <1456326813.6225.158.ca...@debian.org>
and subject line Re: Bug#814338: armhf-20150422: Format partitions error for 
ext4/fat/jfs : Unknown symbol __getblk_gfp
has caused the Debian Bug report #814338,
regarding armhf-20150422: Format partitions error for ext4/fat/jfs : Unknown 
symbol __getblk_gfp
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.)


-- 
814338: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814338
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports
Severity: grave
Tags: d-i
Justification: renders package unusable

I'm trying to run Debian Jessie on ARMv7 using Qemu. I used the initrd.gz and
vmlinuz available at ftp://ftp.debian.org/debian/dists/jessie/main/installer-
armhf/20150422/images/netboot/. I also tried with the up-to-date version at
ftp://ftp.debian.org/debian/dists/jessie/main/installer-
armhf/20150422+deb8u3/images/netboot/ without success.

I also used the vexpress-v2p-ca9.dtb file to pass to Qemu like this:

$ qemu-system-arm -machine vexpress-a9 -m 256 -kernel vmlinuz -initrd initrd.gz
-dtb vexpress-v2p-ca9.dtb   -append "console=ttyAMA0 root=/dev/vda2" -drive
id=vda,file=vda.img,if=none,format=raw,index=1 -device virtio-blk-
device,drive=vda -serial stdio


The installation goes fine until partitionning and fails right after when
trying to mount the newly created partitions. Dmesg give us an idea about the
error that seems related to filesystem module:

[  643.769787] ext4: Unknown symbol __bread_gfp (err 0)
[  643.785817] ext4: Unknown symbol __getblk_gfp (err 0)
[  643.980183] fat: Unknown symbol __bread_gfp (err 0)
[  643.980811] fat: Unknown symbol __getblk_gfp (err 0)
[  644.660754] raid6: int32x1225 MB/s
[  644.729194] raid6: int32x2 65 MB/s
[  644.796728] raid6: int32x4198 MB/s
[  644.864700] raid6: int32x8153 MB/s
[  644.864774] raid6: using algorithm int32x1 (225 MB/s)
[  644.864877] raid6: using intx1 recovery algorithm
[  644.891890] xor: measuring software checksum speed
[  644.928760]arm4regs  :   126.000 MB/sec
[  644.968613]8regs :   444.000 MB/sec
[  645.008637]32regs:   323.000 MB/sec
[  645.008762] xor: using function: 8regs (444.000 MB/sec)
[  645.237009] Btrfs loaded
[  645.799760] ext4: Unknown symbol __bread_gfp (err 0)
[  645.807260] ext4: Unknown symbol __getblk_gfp (err 0)
[  645.926729] ext4: Unknown symbol __bread_gfp (err 0)
[  645.931377] ext4: Unknown symbol __getblk_gfp (err 0)
[  646.358278] jfs: Unknown symbol __bread_gfp (err 0)
[  646.359270] jfs: Unknown symbol __getblk_gfp (err 0)

Also, during the partitionning, the default ext4 filesystem is selected. When
trying to modify it, there's no proposed ext4/ext3/ext2 filesystem nor fat32,
only btrfs, raid, lvm and encrypted.

After some research, could be related to difference of version between the
running kernel and the kernel used to compile the module, so modinfo give us
the following information:

~ # modinfo ext4
filename:   /lib/modules/3.16.0-4-armmp/kernel/fs/ext4/ext4.ko
license:GPL
description:Fourth Extended Filesystem
author: Remy Card, Stephen Tweedie, Andrew Morton, Andreas Dilger,
Theodore Ts'o and others
alias:  fs-ext4
alias:  ext3
alias:  fs-ext3
alias:  ext2
alias:  fs-ext2
depends:mbcache,jbd2,crc16
intree: Y
vermagic:   3.16.0-4-armmp SMP mod_unload modversions ARMv7 p2v8
~ # uname -a
Linux debian 3.16.0-4-armmp #1 SMP Debian 3.16.7-ckt9-2 (2015-04-13) armv7l
GNU/Linux


Any idea what is the problem?




-- Package-specific info:

Boot method: network
Image version: ftp://ftp.debian.org/debian/dists/jessie/main/installer-
armhf/20150422/images/netboot/
Date: 

Machine: QEMU vexpress-v2p-ca9.dtb
Partitions: 


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [ ]
Detect network card:[ ]
Configure network:  [ ]
Detect CD:  [ ]
Load installer modules: [ ]
Clock/timezone setup:   [ ]
User/password setup:[ ]
Detect hard drives: [ ]
Partition hard drives:  [ ]
Install base system:[ ]
Install tasks:  [ ]
Install boot loader:[ ]
Overall install:[ ]

Comments/Problems:





-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to 

Bug#815798: (no subject)

[Sven Geggus]

Subject: gitlab uninstallabe on plain Debian "stretch"
Package: gitlab
Version: 8.4.3+dfsg-9
Severity: serious

Hi,

trying to install gitlab package on a palin stretch-system where postgis and
nginx have already been installed will currently not work.

In case it is of relevance, the system uses sysv-init.

Here is what I get (irrelevant parts have been skipped).

The "gitlab_production database is not empty" message can not be true.  I
did check it manually and it is empty.

..

gitlab_production database is not empty, skipping gitlab setup
Precompiling assets...
fatal: Not a git repository (or any of the parent directories): .git
I, [2016-02-24T13:50:04.590534 #18160]  INFO -- : 


...


Starting GitLab Unicorn
Starting GitLab Sidekiq
Starting gitlab-workhorse
.
The GitLab Unicorn web server with pid 20641 is running.
The GitLab Sidekiq job dispatcher with pid 20706 is running.
The gitlab-workhorse with pid 20683 is running.
GitLab and all its components are up and running.
fatal: Not a git repository (or any of the parent directories): .git
Checking GitLab Shell ...

GitLab Shell version >= 2.6.10 ? ... OK (2.6.10)
Repo base directory exists? ... yes
Repo base directory is a symlink? ... no
Repo base owned by gitlab:gitlab? ... yes
Repo base access is drwxrws---? ... yes
hooks directories in repos are links: ... rake aborted!
ActiveRecord::StatementInvalid: PG::UndefinedTable: ERROR:  relation "projects" 
does not exist
LINE 5:WHERE a.attrelid = '"projects"'::regclass
  ^
:   SELECT a.attname, format_type(a.atttypid, a.atttypmod),
 pg_get_expr(d.adbin, d.adrelid), a.attnotnull,
a.atttypid, a.atttypmod
FROM pg_attribute a LEFT JOIN pg_attrdef d
  ON a.attrelid = d.adrelid AND a.attnum = d.adnum
   WHERE a.attrelid = '"projects"'::regclass
 AND a.attnum > 0 AND NOT a.attisdropped
   ORDER BY a.attnum
/usr/share/gitlab/lib/tasks/gitlab/check.rake:476:in 
`check_repos_hooks_directory_is_link'
/usr/share/gitlab/lib/tasks/gitlab/check.rake:366:in `block (3 levels) in '
PG::UndefinedTable: ERROR:  relation "projects" does not exist
LINE 5:WHERE a.attrelid = '"projects"'::regclass
  ^
/usr/share/gitlab/lib/tasks/gitlab/check.rake:476:in 
`check_repos_hooks_directory_is_link'
/usr/share/gitlab/lib/tasks/gitlab/check.rake:366:in `block (3 levels) in '
Tasks: TOP => gitlab:check => gitlab:gitlab_shell:check
(See full trace by running task with --trace)

Bug#815797: Transition to src:php7.0

[Ondřej Surý]

Package: src:php5
Version: 5.6.17+dfsg-3
Severity: serious

This is a just a maintainer blocker bug, so we can start transitioning
stretch to src:php7.0 and slowly get rid of src:php5 in testing and
unstable.

O.

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

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

Bug#814338: armhf-20150422: Format partitions error for ext4/fat/jfs : Unknown symbol __getblk_gfp

[Gagou Lou]

Just tried today with a fresh Debian install and got the same problem with
20150422 but, against all expectations, the 20150422+deb8u3 as well as the
current symlink worked fine this time.

I'm thinking maybe I made a stupid error using wget to download both
version and not doing any remove before... Not sure, but seems like all my
qemu test was always using the 20150422 instead of the +deb8u3 one.

Anyway, it's working now and sorry for the disturbance.

Regards,
Gaël


2016-02-10 16:18 GMT+01:00 Ian Campbell :

> On Wed, 2016-02-10 at 15:31 +0100, Gaël Jobin wrote:
> > Package: installation-reports
> > Severity: grave
> > Tags: d-i
> > Justification: renders package unusable
> >
> > I'm trying to run Debian Jessie on ARMv7 using Qemu. I used the initrd.gz
> > and
> > vmlinuz available at
> ftp://ftp.debian.org/debian/dists/jessie/main/instal
> > ler-
> > armhf/20150422/images/netboot/. I also tried with the up-to-date version
> > at
> > ftp://ftp.debian.org/debian/dists/jessie/main/installer-
> > armhf/20150422+deb8u3/images/netboot/ without success.
>
> You need to use 20150422+deb8u3, or more specificall whatever the "current"
> symlink currently points to, otherwise you will find a mismatch between the
> installer kernel and what is in the network archive, which results in
> things like what you are seeing.
>
> It looks like all of your logs are with the 20150422 version, please repeat
> using 20150422+deb8u3 and supply those logs instead.
>
> You mention you didn't have success with +deb8u3, but was it the same
> issue?
>
> > ~ # uname -a
> > Linux debian 3.16.0-4-armmp #1 SMP Debian 3.16.7-ckt9-2 (2015-04-13)
> armv7l
>
> This 3.16.7-ckt9-2 is what lead me to conclude these logs were from
> 20150422 and not +deb8u3, the latter would be ...-clk20+deb8u.
>
> Ian.
>

Processed: found 815567 in 2.8.0-4, found 815746 in 4:4.14.0-3, notfound 815684 in 2.24-3 ..., tagging 815685 ...

[Debian Bug Tracking System]

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

> found 815567 2.8.0-4
Bug #815567 [amarok] Amarok should depend on virtual-mysql-server-core to 
support MariaDB
Marked as found in versions amarok/2.8.0-4.
> found 815746 4:4.14.0-3
Bug #815746 [digikam] Digikam should depend on virtual-mysql-server-core to 
support MariaDB
Marked as found in versions digikam/4:4.14.0-3.
> notfound 815684 2.24-3
Bug #815684 [src:why] why can't be built from source
The source 'why' and version '2.24-3' do not appear to match any binary packages
No longer marked as found in versions why/2.24-3.
> found 815684 2.34-3
Bug #815684 [src:why] why can't be built from source
The source 'why' and version '2.34-3' do not appear to match any binary packages
Marked as found in versions why/2.34-3.
> tags 815685 + sid stretch
Bug #815685 [src:libxs] libxs: update for libpgm 5.2 transition
Added tag(s) sid and stretch.
> found 815686 1.1-2.1
Bug #815686 [imageindex] imageindex: Does not work with Perl 5.22
Marked as found in versions imageindex/1.1-2.1.
> tags 815686 + sid stretch
Bug #815686 [imageindex] imageindex: Does not work with Perl 5.22
Added tag(s) sid and stretch.
> tags 815738 + sid stretch
Bug #815738 [src:libspectre] libspectre: FTBFS: spectre-gs.c:46:9: error: 
'e_Fatal' undeclared (first use in this function)
Added tag(s) stretch and sid.
> tags 815781 + sid stretch
Bug #815781 [src:hypre] hypre: FTBFS in sid
Added tag(s) sid and stretch.
> tags 815684 + sid stretch
Bug #815684 [src:why] why can't be built from source
Added tag(s) sid and stretch.
> tags 806615 + sid stretch
Bug #806615 [src:espresso] espresso: FTBFS when built with dpkg-buildpackage -A 
(different version of GNU Fortran)
Added tag(s) stretch and sid.
> retitle 806615 espresso: FTBFS with elpa 2015.05.001
Bug #806615 [src:espresso] espresso: FTBFS when built with dpkg-buildpackage -A 
(different version of GNU Fortran)
Changed Bug title to 'espresso: FTBFS with elpa 2015.05.001' from 'espresso: 
FTBFS when built with dpkg-buildpackage -A (different version of GNU Fortran)'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
806615: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806615
815567: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815567
815684: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815684
815685: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815685
815686: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815686
815738: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815738
815746: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815746
815781: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815781
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#815795: libvigraimpex6: misses Breaks: libvigraimpex5v5 (>= 1.10.0+git20160120.803d5d4-1)

[Daniel Stender]

On 24.02.2016 15:32, Andreas Beckmann wrote:
> Package: libvigraimpex6
> Version: 1.10.0+git20160120.803d5d4-3
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> 
> Hi,
> 
> The Replaces should have a matching Breaks, otherwise it is possible to
> take over files from $oldpkg by $newpkg, remove $newpkg and dpkg still
> thinks $oldpkg is correctly installed, and can satisfy dependencies.
> 
> In your case, libvigraimpex6 is co-installable with libvigraimpex5v5 from
> stretch, but not with the incorrect libvigraimpex5v5 from sid.
> 
> cheers,
> 
> Andreas

Yes, o.k. Thx for the pointer.

DS

-- 
4096R/DF5182C8
46CB 1CA8 9EA3 B743 7676 1DB9 15E0 9AF4 DF51 82C8
http://www.danielstender.com/blog/

Bug#815625: marked as done (redmine: fails to install: /usr/lib/ruby/vendor_ruby/molinillo/dependency_graph.rb:109:in `add_vertex': wrong number of arguments (3 for 2) (ArgumentError))

[Debian Bug Tracking System]

Your message dated Wed, 24 Feb 2016 11:26:15 -0300
with message-id <20160224142615.ga4...@debian.org>
and subject line Re: Bug#815625: redmine: fails to install: 
/usr/lib/ruby/vendor_ruby/molinillo/dependency_graph.rb:109:in `add_vertex': 
wrong number of arguments (3 for 2) (ArgumentError)
has caused the Debian Bug report #815625,
regarding redmine: fails to install: 
/usr/lib/ruby/vendor_ruby/molinillo/dependency_graph.rb:109:in `add_vertex': 
wrong number of arguments (3 for 2) (ArgumentError)
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.)


-- 
815625: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815625
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: redmine
Version: 3.2.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + redmine-plugin-custom-css

Hi,

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

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

  Setting up redmine (3.2.0-2) ...
  Please configure your config/database.yml first
  dbconfig-common: writing config to 
/etc/dbconfig-common/redmine/instances/default.conf
  
  Creating config file /etc/dbconfig-common/redmine/instances/default.conf with 
new version
  
  Creating config file /etc/redmine/default/database.yml with new version
  creating database redmine_default: success.
  verifying database redmine_default exists: success.
  /usr/lib/ruby/vendor_ruby/molinillo/dependency_graph.rb:109:in `add_vertex': 
wrong number of arguments (3 for 2) (ArgumentError)
from /usr/lib/ruby/vendor_ruby/bundler/resolver.rb:194:in `block in 
initialize'
from /usr/lib/ruby/vendor_ruby/bundler/resolver.rb:194:in `initialize'
from /usr/lib/ruby/vendor_ruby/bundler/resolver.rb:182:in `new'
from /usr/lib/ruby/vendor_ruby/bundler/resolver.rb:182:in `resolve'
from /usr/lib/ruby/vendor_ruby/bundler/definition.rb:198:in `resolve'
from /usr/lib/ruby/vendor_ruby/bundler/definition.rb:137:in `specs'
from /usr/lib/ruby/vendor_ruby/bundler/definition.rb:182:in `specs_for'
from /usr/lib/ruby/vendor_ruby/bundler/definition.rb:171:in 
`requested_specs'
from /usr/lib/ruby/vendor_ruby/bundler/environment.rb:18:in 
`requested_specs'
from /usr/lib/ruby/vendor_ruby/bundler/runtime.rb:13:in `setup'
from /usr/lib/ruby/vendor_ruby/bundler.rb:92:in `setup'
from /usr/lib/ruby/vendor_ruby/bundler/setup.rb:8:in `'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in 
`require'
  dpkg: error processing package redmine (--configure):
   subprocess installed post-installation script returned error exit status 1


This was observed while installing the dependencies of package
redmine-plugin-custom-css in preparation of a piuparts test on that
package.


cheers,

Andreas


redmine-plugin-custom-css_0.1.6+dfsg-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
On Tue, Feb 23, 2016 at 01:32:58AM +0100, Andreas Beckmann wrote:
> Package: redmine
> Version: 3.2.0-2
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> Control: affects -1 + redmine-plugin-custom-css
> 
> Hi,
> 
> during a test with piuparts I noticed your package failed to install. As
> per definition of the release team this makes the package too buggy for
> a release, thus the severity.
> 
> >From the attached log (scroll to the bottom...):
> 
>   Setting up redmine (3.2.0-2) ...
>   Please configure your config/database.yml first
>   dbconfig-common: writing config to 
> /etc/dbconfig-common/redmine/instances/default.conf
>   
>   Creating config file /etc/dbconfig-common/redmine/instances/default.conf 
> with new version
>   
>   Creating config file /etc/redmine/default/database.yml with new version
>   creating database redmine_default: success.
>   verifying database redmine_default exists: success.
>   /usr/lib/ruby/vendor_ruby/molinillo/dependency_graph.rb:109:in 
> `add_vertex': wrong number of arguments (3 for 2) (ArgumentError)

This was caused by bundler and ruby-molinillo, but has been fixed since.


signature.asc
Description: PGP signature
--- End Message ---

Bug#815795: libvigraimpex6: misses Breaks: libvigraimpex5v5 (>= 1.10.0+git20160120.803d5d4-1)

[Andreas Beckmann]

Package: libvigraimpex6
Version: 1.10.0+git20160120.803d5d4-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

The Replaces should have a matching Breaks, otherwise it is possible to
take over files from $oldpkg by $newpkg, remove $newpkg and dpkg still
thinks $oldpkg is correctly installed, and can satisfy dependencies.

In your case, libvigraimpex6 is co-installable with libvigraimpex5v5 from
stretch, but not with the incorrect libvigraimpex5v5 from sid.


cheers,

Andreas

Bug#815785: marked as done (comix: FTBFS - Could not find all required dependencies)

[Debian Bug Tracking System]

Your message dated Wed, 24 Feb 2016 13:50:33 +
with message-id 
and subject line Bug#815785: fixed in comix 4.0.4-3
has caused the Debian Bug report #815785,
regarding comix: FTBFS - Could not find all required 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.)


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

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

[...]
# Add here commands to install the package into debian/comix.
mkdir -p 
/srv/jenkins-slave/workspace/sid-goto-cc-comix/comix-4.0.4/debian/comix/usr
python install.py install --dir 
/srv/jenkins-slave/workspace/sid-goto-cc-comix/comix-4.0.4/debian/comix/usr 
--no-mime
Checking dependencies ...

Required dependencies:
!!! PyGTK  Not found
!!! Python Imaging Library ... Not found

Recommended dependencies:
!!! rar/unrar  Not found

Could not find all required dependencies!
Please install them and try again.
debian/rules:32: recipe for target 'install' failed
make: *** [install] Error 1


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

Best,
Michael


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


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: comix
Source-Version: 4.0.4-3

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

Debian distribution maintenance software
pp.
Emfox Zhou  (supplier of updated comix package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 24 Feb 2016 20:37:51 +0800
Source: comix
Binary: comix
Architecture: source all
Version: 4.0.4-3
Distribution: unstable
Urgency: low
Maintainer: Emfox Zhou 
Changed-By: Emfox Zhou 
Description:
 comix  - GTK Comic Book Viewer
Closes: 815785
Changes:
 comix (4.0.4-3) unstable; urgency=low
 .
   * Didn't really add unar support, remove suggestion.
   * Disable runtime dependency check at build time again, was enabled
 accidentally on changing source format. (Closes: #815785)
Checksums-Sha1:
 319aadce8d311840a9376040bfcbcd969ca5f0af 1658 comix_4.0.4-3.dsc
 8b9541a45347943d19162afa9c6a15a2db3f3be5 4404 comix_4.0.4-3.debian.tar.xz
 58135d1686412321985a2e8057e7bd1fe21e3540 166148 comix_4.0.4-3_all.deb
Checksums-Sha256:
 d8326c51094cf585b4820d327609f73e5f846307567200d8fd52fffad7536c65 1658 
comix_4.0.4-3.dsc
 c79d07236a5a96443926f30959c04ab14e1941b55146fd7dac1ce7140bdd98be 4404 
comix_4.0.4-3.debian.tar.xz
 2d9bda210751d8844b3727f7310e16b64f1e2ffc0f7724f23f45a356f49af3dd 166148 
comix_4.0.4-3_all.deb
Files:
 f2df945dbdf7fd91a0aa6fe3b586fde2 1658 x11 optional comix_4.0.4-3.dsc
 9cb008ad3ef31fa7521e5dc09e7a0a8e 4404 x11 optional comix_4.0.4-3.debian.tar.xz
 9c37e4c6ddd7968d25704415c26ff754 166148 x11 optional comix_4.0.4-3_all.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWza19AAoJEICJm7/be72UEkAP/1q2A6cFlXw45FQXeBSdy8My
zFz5w+Dxba23PkEyaDJ3TqLWvQFPitI04FudO5IX2YkJBp/5D47WUOfHc4bzPWXd
9dW4sIk5orITPfTXf4BkXahxMIavRTGYU9D7zpYTWWzEoprdGg5aRG5gU5WX4QAy
arDgVY1wKrnjQd+gt6CpZO6vE5R9HoRJlWIvtwfScUEvHKQLXMou+5hThvoWl1Ew
L8bP8i4cIGMHgDWnZWD+wrZxPw5mmhBICih3GcU3PzAZfHYjB5Q58TG3oYqJ2+Hh
2IRS9g+OCeOy4VLiSkE9okEaD8rIQ/O+S8V0CPc9KMDN+cuzY2iqnP2GuuB0/I97
/r4GJMkaK+P0zd4YQ+YDcQ/SNVIzal6Qnx0WMKeFjGpWc1OJ15HHnV/g4+9jqFY8
wiADQz45sol+5fWdnYpakPWdTMOZFjhf8w1o+dK41Z2tkSBJ60fiyCS5eaS/Ttsh
ZqJfMNDXcy2kVxVGResGnCZblQ55Af4gYH4xlYDUBDBHA15441VLXtHDqnAPVXpL
8Q/f3iVlIg0sAAo7/5Slv80K7umUe8+6ucm+k7iVBb343SgGO6YF5MhD2IBuzak/
ufSzeoYgmOemm8IXsn/bYhhawbBgE54Qw6pncw8ZVH3B3kJ4Zi47Aws9pfHsDAZP
ju62dK2s09E/S7St/wG3
=PQVx
-END PGP SIGNATURE End Message ---

Bug#815047: Still there with 3.0.4-1

[Scott Kitterman]

On Wednesday, February 24, 2016 07:56:33 AM you wrote:
> On Wed, 24 Feb 2016 12:49:29 +0100 Michael Meskes  wrote:
> > reopen 815047
> > thanks
> 
> > The latest uploaded does not seem to fix the problem:
> ...
> 
> > Feb 24 12:44:33 feivel postmulti[24558]: fatal: instance /etc/postfix,
> 
> shlib_directory=/usr/lib/postfix conflicts with instance /etc/postfix,
> daemon_directory=/usr/lib/postfix
> ...
> 
> Looks like the change in [1] got lost somewhere.  Given the current layout:
> 
> /usr/lib/
> ...
> /usr/lib/libpostfix-dns.so.1 -> libpostfix-dns.so.1.0.1
> /usr/lib/libpostfix-dns.so.1.0.1
> (which is the start of a list of file that amount to usr/lib/libpostfix-
> *.so.1{.0.1})
> ...
> /usr/lib/postfix/
> ...
> /usr/lib/postfix/sbin/
> /usr/lib/postfix/sbin/anvil
> etc
> 
> I think what lamont was going for was:
> shlib_directory=/usr/lib/postfix
> daemon_directory=/usr/lib/postfix/sbin
> 
> So the install location for the libpostfix files needs updating and the
> daemon_directory value needs to be corrected.  I'll take a stab at it.

OK.  I've pushed the fix to git, but I'm not 100% sure I know what lamont was 
after, so I'll leave it to him to review/upload once he's awake.

Scott K

Bug#814972: marked as done (openimageio: FTBFS: CMakeFiles/Makefile2:1517: recipe for target 'src/libOpenImageIO/CMakeFiles/OpenImageIO.dir/all' failed)

[Debian Bug Tracking System]

Your message dated Wed, 24 Feb 2016 14:40:11 +0100
with message-id <20160224134011.GA13950@localhost>
and subject line Re: Bug#814972: openimageio: FTBFS:  
CMakeFiles/Makefile2:1517: recipe for target 
'src/libOpenImageIO/CMakeFiles/OpenImageIO.dir/all' failed
has caused the Debian Bug report #814972,
regarding openimageio: FTBFS:  CMakeFiles/Makefile2:1517: recipe for target 
'src/libOpenImageIO/CMakeFiles/OpenImageIO.dir/all' failed
to be marked as done.

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

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


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

Dear Maintainer,

openimageio fails to build from source in unstable/amd64:

  [..]


  cd 
"/home/lamby/temp/cdt.20160217092835.sTeDIzmZc8/openimageio-1.6.10~dfsg0/build/src/libOpenImageIO"
 && /usr/bin/c++   -DBOOST_TEST_DYN_LINK -DEMBED_PLUGINS=1 
-DOpenImageIO_EXPORTS -DPTEX_EXPORTS -DUSE_BOOST_ASIO=1 -DUSE_FREETYPE 
-DUSE_GIF -DUSE_LIBRAW=1 -DUSE_OCIO=1 -DUSE_OPENCV -DUSE_OPENEXR_VERSION2=1 
-DUSE_OPENJPEG -DUSE_PTEX -DUSE_WEBP=1 -D__STDC_CONSTANT_MACROS 
-D__STDC_LIMIT_MACROS -I/usr/include/OpenEXR -I/usr/include/libraw 
-I"/home/lamby/temp/cdt.20160217092835.sTeDIzmZc8/openimageio-1.6.10~dfsg0/src/include"
 
-I"/home/lamby/temp/cdt.20160217092835.sTeDIzmZc8/openimageio-1.6.10~dfsg0/build/include/OpenImageIO"
 
-I"/home/lamby/temp/cdt.20160217092835.sTeDIzmZc8/openimageio-1.6.10~dfsg0/build/src/libOpenImageIO"
 -I/usr/include/x86_64-linux-gnu -I/usr/include/openjpeg-1.5 
-I/usr/include/freetype2 -I/usr/include/freetype2/freetype2 
-I/usr/include/freetype2/freetype2/freetype  -g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2  -fPIC   -Wall 
-fno-math-errno -Wno-error=unused-local-typedefs -Wno-unused-local-typedefs 
-Wno-unused-result -UUSE_FIELD3D -o 
CMakeFiles/OpenImageIO.dir/__/ptex.imageio/ptex/PtexWriter.cpp.o -c 
"/home/lamby/temp/cdt.20160217092835.sTeDIzmZc8/openimageio-1.6.10~dfsg0/src/ptex.imageio/ptex/PtexWriter.cpp"
  make[4]: Leaving directory 
'/home/lamby/temp/cdt.20160217092835.sTeDIzmZc8/openimageio-1.6.10~dfsg0/build'
  CMakeFiles/Makefile2:1517: recipe for target 
'src/libOpenImageIO/CMakeFiles/OpenImageIO.dir/all' failed
  make[3]: *** [src/libOpenImageIO/CMakeFiles/OpenImageIO.dir/all] Error 2
  make[3]: Leaving directory 
'/home/lamby/temp/cdt.20160217092835.sTeDIzmZc8/openimageio-1.6.10~dfsg0/build'
  Makefile:163: recipe for target 'all' failed
  make[2]: *** [all] Error 2
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160217092835.sTeDIzmZc8/openimageio-1.6.10~dfsg0/build'
  dh_auto_build: make -j9 returned exit code 2
  debian/rules:23: recipe for target 'override_dh_auto_build' failed
  make[1]: *** [override_dh_auto_build] Error 2
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160217092835.sTeDIzmZc8/openimageio-1.6.10~dfsg0'
  debian/rules:10: 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
   `-


openimageio.1.6.10~dfsg0-2.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Version: 1.6.10~dfsg0-2

Hi Chris!

On 2016-02-24 at 13:38 (CET), Chris Lamb wrote:
> Dear Maintainer,
> 
> openimageio fails to build from source in unstable/amd64:

There was a known issue with libpng that prevented the package on amd64
to build.

I asked for a g-b and the package builds fine again.

So, closing.

Cheers.


-- 
Matteo F. Vescovi || Debian Developer
GnuPG KeyID: 4096R/0x8062398983B2CF7A


signature.asc
Description: PGP signature
--- End Message ---

Bug#815218: marked as done (ros-image-common: FTBFS: dh_install: libcamera-calibration-parsers0d missing files: usr/lib/*/camera_calibration_parsers)

[Debian Bug Tracking System]

Your message dated Wed, 24 Feb 2016 13:32:54 +
with message-id 
and subject line Bug#815218: fixed in ros-image-common 1.11.10-2
has caused the Debian Bug report #815218,
regarding ros-image-common: FTBFS: dh_install: libcamera-calibration-parsers0d 
missing files: usr/lib/*/camera_calibration_parsers
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.)


-- 
815218: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815218
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ros-image-common
Version: 1.11.10-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-image-common fails to build from source in unstable/amd64:

  [..]

  -- Installing: 
/home/lamby/temp/cdt.20160220082234.5FYPMuebWg/ros-image-common-1.11.10/debian/tmp/usr/lib/x86_64-linux-gnu/libpolled_camera.so.0d
  -- Installing: 
/home/lamby/temp/cdt.20160220082234.5FYPMuebWg/ros-image-common-1.11.10/debian/tmp/usr/lib/x86_64-linux-gnu/libpolled_camera.so
  -- Removed runtime path from 
"/home/lamby/temp/cdt.20160220082234.5FYPMuebWg/ros-image-common-1.11.10/debian/tmp/usr/lib/x86_64-linux-gnu/libpolled_camera.so.1.11.10"
  -- Up-to-date: 
/home/lamby/temp/cdt.20160220082234.5FYPMuebWg/ros-image-common-1.11.10/debian/tmp/usr/include/polled_camera
  -- Installing: 
/home/lamby/temp/cdt.20160220082234.5FYPMuebWg/ros-image-common-1.11.10/debian/tmp/usr/include/polled_camera/publication_server.h
  -- Installing: 
/home/lamby/temp/cdt.20160220082234.5FYPMuebWg/ros-image-common-1.11.10/debian/tmp/usr/lib/polled_camera/poller
  -- Removed runtime path from 
"/home/lamby/temp/cdt.20160220082234.5FYPMuebWg/ros-image-common-1.11.10/debian/tmp/usr/lib/polled_camera/poller"
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160220082234.5FYPMuebWg/ros-image-common-1.11.10/obj-x86_64-linux-gnu'
 dh_install -O--parallel -O--buildsystem=cmake
  dh_install: libcamera-calibration-parsers0d missing files: 
usr/lib/*/camera_calibration_parsers
  dh_install: image-transport-tools missing files: usr/lib/*/image_transport
  dh_install: libpolled-camera0d missing files: usr/lib/*/polled_camera
  dh_install: missing files, aborting
  debian/rules:6: recipe for target 'binary' failed
  make: *** [binary] Error 2

  [..]

The full build log is attached.


Regards,

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


ros-image-common.1.11.10-1.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: ros-image-common
Source-Version: 1.11.10-2

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

Debian distribution maintenance software
pp.
Jochen Sprickerhof  (supplier of updated 
ros-image-common 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, 21 Feb 2016 12:41:07 +0100
Source: ros-image-common
Binary: libcamera-calibration-parsers-dev libcamera-calibration-parsers0d 
python-camera-calibration-parsers libcamera-info-manager-dev 
libcamera-info-manager0d libimage-transport-dev libimage-transport0d 
image-transport-tools libpolled-camera-dev libpolled-camera0d 
python-polled-camera cl-polled-camera
Architecture: source all amd64
Version: 1.11.10-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Jochen Sprickerhof 
Description:
 cl-polled-camera - Robot OS polled_camera package - LISP
 image-transport-tools - Robot OS image_transport package
 libcamera-calibration-parsers-dev - Robot OS camera_calibration_parsers 
package - development
 libcamera-calibration-parsers0d - Robot OS camera_calibration_parsers package
 libcamera-info-manager-dev - Robot OS camera_info_manager package - development
 libcamera-info-manager0d - 

Processed: tagging 684499

[Debian Bug Tracking System]

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

> tags 684499 + pending
Bug #684499 [dovecot-core] dovecot-core: Expunged messages continue to reappear
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#815743: marked as done (ros-geometry-experimental: FTBFS: dh_install: tf2-tools missing files: usr/lib/*/tf2_ros/*)

[Debian Bug Tracking System]

Your message dated Wed, 24 Feb 2016 14:24:49 +0100
with message-id <20160224132449.gh18...@vis.informatik.uni-osnabrueck.de>
and subject line ros-geometry-experimental: FTBFS: dh_install: tf2-tools 
missing files: usr/lib/*/tf2_ros/*
has caused the Debian Bug report #815743,
regarding ros-geometry-experimental: FTBFS: dh_install: tf2-tools missing 
files: usr/lib/*/tf2_ros/*
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.)


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

Dear Maintainer,

ros-geometry-experimental fails to build from source in unstable/amd64:

  [..]

  running install
  running install_lib
  creating 
/home/lamby/temp/cdt.20160224081500.26FVwmhnKk/ros-geometry-experimental-0.5.12/debian/tmp/usr/lib/python2.7/dist-packages/tf2_sensor_msgs
  copying 
/home/lamby/temp/cdt.20160224081500.26FVwmhnKk/ros-geometry-experimental-0.5.12/obj-x86_64-linux-gnu/tf2_sensor_msgs/lib.linux-x86_64-2.7/tf2_sensor_msgs/__init__.py
 -> 
/home/lamby/temp/cdt.20160224081500.26FVwmhnKk/ros-geometry-experimental-0.5.12/debian/tmp/usr/lib/python2.7/dist-packages/tf2_sensor_msgs
  copying 
/home/lamby/temp/cdt.20160224081500.26FVwmhnKk/ros-geometry-experimental-0.5.12/obj-x86_64-linux-gnu/tf2_sensor_msgs/lib.linux-x86_64-2.7/tf2_sensor_msgs/tf2_sensor_msgs.py
 -> 
/home/lamby/temp/cdt.20160224081500.26FVwmhnKk/ros-geometry-experimental-0.5.12/debian/tmp/usr/lib/python2.7/dist-packages/tf2_sensor_msgs
  byte-compiling 
/home/lamby/temp/cdt.20160224081500.26FVwmhnKk/ros-geometry-experimental-0.5.12/debian/tmp/usr/lib/python2.7/dist-packages/tf2_sensor_msgs/__init__.py
 to __init__.pyc
  byte-compiling 
/home/lamby/temp/cdt.20160224081500.26FVwmhnKk/ros-geometry-experimental-0.5.12/debian/tmp/usr/lib/python2.7/dist-packages/tf2_sensor_msgs/tf2_sensor_msgs.py
 to tf2_sensor_msgs.pyc
  running install_egg_info
  Writing 
/home/lamby/temp/cdt.20160224081500.26FVwmhnKk/ros-geometry-experimental-0.5.12/debian/tmp/usr/lib/python2.7/dist-packages/tf2_sensor_msgs-0.5.12.egg-info
  -- Installing: 
/home/lamby/temp/cdt.20160224081500.26FVwmhnKk/ros-geometry-experimental-0.5.12/debian/tmp/usr/_setup_util.py
  -- Up-to-date: 
/home/lamby/temp/cdt.20160224081500.26FVwmhnKk/ros-geometry-experimental-0.5.12/debian/tmp/usr/env.sh
  -- Up-to-date: 
/home/lamby/temp/cdt.20160224081500.26FVwmhnKk/ros-geometry-experimental-0.5.12/debian/tmp/usr/setup.bash
  -- Up-to-date: 
/home/lamby/temp/cdt.20160224081500.26FVwmhnKk/ros-geometry-experimental-0.5.12/debian/tmp/usr/setup.sh
  -- Up-to-date: 
/home/lamby/temp/cdt.20160224081500.26FVwmhnKk/ros-geometry-experimental-0.5.12/debian/tmp/usr/setup.zsh
  -- Up-to-date: 
/home/lamby/temp/cdt.20160224081500.26FVwmhnKk/ros-geometry-experimental-0.5.12/debian/tmp/usr/.rosinstall
  -- Installing: 
/home/lamby/temp/cdt.20160224081500.26FVwmhnKk/ros-geometry-experimental-0.5.12/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig/tf2_tools.pc
  -- Installing: 
/home/lamby/temp/cdt.20160224081500.26FVwmhnKk/ros-geometry-experimental-0.5.12/debian/tmp/usr/share/tf2_tools/cmake/tf2_toolsConfig.cmake
  -- Installing: 
/home/lamby/temp/cdt.20160224081500.26FVwmhnKk/ros-geometry-experimental-0.5.12/debian/tmp/usr/share/tf2_tools/cmake/tf2_toolsConfig-version.cmake
  -- Installing: 
/home/lamby/temp/cdt.20160224081500.26FVwmhnKk/ros-geometry-experimental-0.5.12/debian/tmp/usr/share/tf2_tools/package.xml
  -- Installing: 
/home/lamby/temp/cdt.20160224081500.26FVwmhnKk/ros-geometry-experimental-0.5.12/debian/tmp/usr/lib/tf2_tools/view_frames.py
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160224081500.26FVwmhnKk/ros-geometry-experimental-0.5.12/obj-x86_64-linux-gnu'
 dh_install -O--parallel -O--buildsystem=cmake
  dh_install: tf2-tools missing files: usr/lib/*/tf2_ros/*
  dh_install: missing files, aborting
  debian/rules:6: recipe for target 'binary' failed
  make: *** [binary] Error 2

  [..]

The full build log is attached.


Regards,

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


ros-geometry-experimental.0.5.12-2.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Version: 0.5.12-3


signature.asc
Description: PGP signature
--- End Message ---

Bug#815744: marked as done (ros-pluginlib: FTBFS: dh_install: pluginlib-dev missing files: usr/lib/*/pluginlib)

[Debian Bug Tracking System]

Your message dated Wed, 24 Feb 2016 14:24:20 +0100
with message-id <20160224132420.gg18...@vis.informatik.uni-osnabrueck.de>
and subject line ros-pluginlib: FTBFS: dh_install: pluginlib-dev missing files: 
usr/lib/*/pluginlib
has caused the Debian Bug report #815744,
regarding ros-pluginlib: FTBFS: dh_install: pluginlib-dev missing files: 
usr/lib/*/pluginlib
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.)


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

Dear Maintainer,

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

  [..]

  running install
  running install_egg_info
  Creating 
/home/lamby/temp/cdt.20160224081630.7zpa0JrVPD/ros-pluginlib-1.10.1/debian/tmp/usr/lib/python2.7/dist-packages/
  Writing 
/home/lamby/temp/cdt.20160224081630.7zpa0JrVPD/ros-pluginlib-1.10.1/debian/tmp/usr/lib/python2.7/dist-packages/pluginlib-1.10.1.egg-info
  -- Installing: 
/home/lamby/temp/cdt.20160224081630.7zpa0JrVPD/ros-pluginlib-1.10.1/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig/pluginlib.pc
  -- Installing: 
/home/lamby/temp/cdt.20160224081630.7zpa0JrVPD/ros-pluginlib-1.10.1/debian/tmp/usr/share/pluginlib/cmake/pluginlibConfig.cmake
  -- Installing: 
/home/lamby/temp/cdt.20160224081630.7zpa0JrVPD/ros-pluginlib-1.10.1/debian/tmp/usr/share/pluginlib/cmake/pluginlibConfig-version.cmake
  -- Installing: 
/home/lamby/temp/cdt.20160224081630.7zpa0JrVPD/ros-pluginlib-1.10.1/debian/tmp/usr/share/pluginlib/package.xml
  -- Installing: 
/home/lamby/temp/cdt.20160224081630.7zpa0JrVPD/ros-pluginlib-1.10.1/debian/tmp/usr/lib/pluginlib/plugin_tool
  -- Installing: 
/home/lamby/temp/cdt.20160224081630.7zpa0JrVPD/ros-pluginlib-1.10.1/debian/tmp/usr/include/pluginlib
  -- Installing: 
/home/lamby/temp/cdt.20160224081630.7zpa0JrVPD/ros-pluginlib-1.10.1/debian/tmp/usr/include/pluginlib/class_desc.h
  -- Installing: 
/home/lamby/temp/cdt.20160224081630.7zpa0JrVPD/ros-pluginlib-1.10.1/debian/tmp/usr/include/pluginlib/class_list_macros.h
  -- Installing: 
/home/lamby/temp/cdt.20160224081630.7zpa0JrVPD/ros-pluginlib-1.10.1/debian/tmp/usr/include/pluginlib/class_loader_base.h
  -- Installing: 
/home/lamby/temp/cdt.20160224081630.7zpa0JrVPD/ros-pluginlib-1.10.1/debian/tmp/usr/include/pluginlib/class_loader_imp.h
  -- Installing: 
/home/lamby/temp/cdt.20160224081630.7zpa0JrVPD/ros-pluginlib-1.10.1/debian/tmp/usr/include/pluginlib/class_loader.h
  -- Installing: 
/home/lamby/temp/cdt.20160224081630.7zpa0JrVPD/ros-pluginlib-1.10.1/debian/tmp/usr/include/pluginlib/pluginlib_exceptions.h
  -- Installing: 
/home/lamby/temp/cdt.20160224081630.7zpa0JrVPD/ros-pluginlib-1.10.1/debian/tmp/usr/share/pluginlib/typed_class_loader_template.cpp
  -- Installing: 
/home/lamby/temp/cdt.20160224081630.7zpa0JrVPD/ros-pluginlib-1.10.1/debian/tmp/usr/lib/pluginlib/plugin_macro_update
  make[2]: Leaving directory 
'/home/lamby/temp/cdt.20160224081630.7zpa0JrVPD/ros-pluginlib-1.10.1/build'
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160224081630.7zpa0JrVPD/ros-pluginlib-1.10.1'
 dh_install -O--buildsystem=cmake -O--builddirectory=build
  dh_install: pluginlib-dev missing files: usr/lib/*/pluginlib
  dh_install: missing files, aborting
  debian/rules:6: recipe for target 'binary' failed
  make: *** [binary] Error 2

  [..]

The full build log is attached.


Regards,

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


ros-pluginlib.1.10.1-2.unstable.amd64.log.txt.gz
Description: Binary data
--- End Message ---
--- Begin Message ---
Version: 1.10.1-3


signature.asc
Description: PGP signature
--- End Message ---

Bug#815785: comix: FTBFS - Could not find all required dependencies

[Michael Tautschnig]

Package: comix
Version: 4.0.4-2
Severity: serious
Usertags: goto-cc

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

[...]
# Add here commands to install the package into debian/comix.
mkdir -p 
/srv/jenkins-slave/workspace/sid-goto-cc-comix/comix-4.0.4/debian/comix/usr
python install.py install --dir 
/srv/jenkins-slave/workspace/sid-goto-cc-comix/comix-4.0.4/debian/comix/usr 
--no-mime
Checking dependencies ...

Required dependencies:
!!! PyGTK  Not found
!!! Python Imaging Library ... Not found

Recommended dependencies:
!!! rar/unrar  Not found

Could not find all required dependencies!
Please install them and try again.
debian/rules:32: recipe for target 'install' failed
make: *** [install] Error 1


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

Best,
Michael


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


signature.asc
Description: PGP signature

Bug#815047: Still there with 3.0.4-1

[Scott Kitterman]

On Wed, 24 Feb 2016 12:49:29 +0100 Michael Meskes  wrote:
> reopen 815047
> thanks
> 
> The latest uploaded does not seem to fix the problem:
...
> Feb 24 12:44:33 feivel postmulti[24558]: fatal: instance /etc/postfix, 
shlib_directory=/usr/lib/postfix conflicts with instance /etc/postfix, 
daemon_directory=/usr/lib/postfix
...

Looks like the change in [1] got lost somewhere.  Given the current layout:

/usr/lib/
...
/usr/lib/libpostfix-dns.so.1 -> libpostfix-dns.so.1.0.1
/usr/lib/libpostfix-dns.so.1.0.1
(which is the start of a list of file that amount to usr/lib/libpostfix-
*.so.1{.0.1})
...
/usr/lib/postfix/
...
/usr/lib/postfix/sbin/
/usr/lib/postfix/sbin/anvil
etc

I think what lamont was going for was:
shlib_directory=/usr/lib/postfix
daemon_directory=/usr/lib/postfix/sbin

So the install location for the libpostfix files needs updating and the 
daemon_directory value needs to be corrected.  I'll take a stab at it.

Scott K


[1] 
https://git.launchpad.net/postfix/commit/?h=stable/v3.0=87d0c5193c06854ca6f212d14b0fa76c17ffde46

Bug#815783: r-cran-arm: FTBFS - dependencies are not available for package 'arm'

[Michael Tautschnig]

Package: r-cran-arm
Version: 1.8-6-1
Severity: serious
Usertags: goto-cc

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

[...]
dh_installdirs  usr/lib/R/site-library
echo "R:Depends=r-base-core (>= 3.2.3-6), r-api-3" >> 
debian/r-cran-arm.substvars
if test -f /usr/bin/xvfb-run; then  \
 xvfb-run -a\
R CMD INSTALL -l 
/srv/jenkins-slave/workspace/sid-goto-cc-r-cran-arm/r-cran-arm-1.8-6/debian/r-cran-arm/usr/lib/R/site-library
 --clean \
 .  \
"--built-timestamp=\"Thu, 18 Feb 2016 21:43:55 
+0100\"" \
;   \
else\
 R CMD INSTALL -l 
/srv/jenkins-slave/workspace/sid-goto-cc-r-cran-arm/r-cran-arm-1.8-6/debian/r-cran-arm/usr/lib/R/site-library
 \
--clean  .  \
"--built-timestamp=\"Thu, 18 Feb 2016 21:43:55 
+0100\"" \
;   \
fi
ERROR: dependencies 'MASS', 'Matrix', 'lme4', 'abind', 'coda', 'nlme' are not 
available for package 'arm'
* removing 
'/srv/jenkins-slave/workspace/sid-goto-cc-r-cran-arm/r-cran-arm-1.8-6/debian/r-cran-arm/usr/lib/R/site-library/arm'
/usr/share/R/debian/r-cran.mk:98: recipe for target 'R_any_arch' failed
make: *** [R_any_arch] Error 1


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

Best,
Michael


r-cran-arm-build-log.txt.gz
Description: application/gunzip


signature.asc
Description: PGP signature

Processed: add patch

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #814198 [csmith] csmith: FTBFS: platform.cpp:78:10: error: impossible 
constraint in 'asm'
Added tag(s) patch.

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

Bug#814198: add patch

[Matthias Klose]

Control: tags -1 + patch

patch at
http://launchpadlibrarian.net/242472711/csmith_2.2.0-1_2.2.0-1ubuntu1.diff.gz

Bug#815735: fio: FTBFS: libmtd.h:288:8: error: unknown type name 'uint8_t'

[Martin Steigerwald]

Hello Chris.

Thanks Chris.

Upstream git master already contains the same fix I came up with
(#include ).

I updated the packaging to fio-2.6 and asked Sven to review and sponsor
the package.

http://people.teamix.net/~ms/debian/sid/fio/fio_2.6-1.dsc

http://people.teamix.net/~ms/debian/sid/fio/

Or any of the git repos like:

https://anonscm.debian.org/cgit/collab-maint/fio.git

Sven may take a while for the review, cause he is quite busy.

Thanks,
Martin


Am Mittwoch, 24. Februar 2016, 09:49:03 CET schrieben Sie:
> Source: fio
> Version: 2.2.10-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,
> 
> fio fails to build from source in unstable/amd64:
> 
>   [..]
> 
>   CC engines/e4defrag.o
>   CC engines/splice.o
>   CC engines/rbd.o
>   CC engines/mtd.o
>   CC lib/libmtd.o
>   CC lib/libmtd_legacy.o
>   In file included from lib/libmtd_legacy.c:38:0:
>   lib/libmtd.h:288:8: error: unknown type name 'uint8_t'
>   uint8_t mode);
>   ^
>   lib/libmtd.h:305:4: error: unknown type name 'uint64_t'
>   uint64_t start, uint64_t length, void *data);
>   ^
>   lib/libmtd.h:305:20: error: unknown type name 'uint64_t'
>   uint64_t start, uint64_t length, void *data);
>   ^
>   lib/libmtd.h:322:5: error: unknown type name 'uint64_t'
>uint64_t start, uint64_t length, void *data);
>^
>   lib/libmtd.h:322:21: error: unknown type name 'uint64_t'
>uint64_t start, uint64_t length, void *data);
>^
>   Makefile:287: recipe for target 'lib/libmtd_legacy.o' failed
>   make[1]: *** [lib/libmtd_legacy.o] Error 1
>   make[1]: Leaving directory 
> '/home/lamby/temp/cdt.20160224080541.mSFrnTpDmm/fio-2.2.10'
>   dh_auto_build: make -j1 returned exit code 2
>   debian/rules:15: recipe for target 'build' failed
>   make: *** [build] Error 2
> 
>   [..]
> 
> The full build log is attached.
> 
> 
> Regards,
> 
> 



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

Bug#815734: ess: FTBFS: doc/newfeat.texi:29: Argument of @gobblespaces has an extra }.

[Dirk Eddelbuettel]

On 24 February 2016 at 09:48, Chris Lamb wrote:
| Source: ess
| Version: 15.09.2-1
| Severity: serious
| Justification: fails to build from source
| User: reproducible-bui...@lists.alioth.debian.org
| Usertags: ftbfs
| X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
| 
| Dear Maintainer,
| 
| ess fails to build from source in unstable/amd64:
| 
|   [..]
| 
|   LC_ALL=C LANG=en makeinfo --html --no-split --css-include=atouchofstyle.css 
-o html/news.html allnews.texi
|   LANG=C texi2dvi --pdf ess.texi
|   This is pdfTeX, Version 3.14159265-2.6-1.40.16 (TeX Live 2015/Debian) 
(preloaded format=pdfetex)
|restricted \write18 enabled.
|   entering extended mode
|   (./ess.texi (/usr/share/texmf/tex/texinfo/texinfo.tex
|   Loading texinfo [version 2016-02-05.07.deb1]: pdf, fonts, markup, glyphs,
|   page headings, tables, conditionals, indexing, sectioning, toc, 
environments,
|   defuns, macros, cross references, insertions,
|   (/usr/share/texlive/texmf-dist/tex/generic/epsf/epsf.tex
|   This is `epsf.tex' v2.7.4 <14 February 2011>
|   ) localization, formatting, and turning on texinfo input format.)
|   
(/home/lamby/temp/cdt.20160224075206.p19g7Umwps/ess-15.09.2/doc/ess-defs.texi)
|   (../VERSION) [1{/var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map}] [-1]
|   Chapter 1
|   
(/home/lamby/temp/cdt.20160224075206.p19g7Umwps/ess-15.09.2/doc/currfeat.texi
|   [1]) Cross reference values unknown; you must run TeX again. [2]
|   (/home/lamby/temp/cdt.20160224075206.p19g7Umwps/ess-15.09.2/doc/newfeat.texi
|   [3]
|   
/home/lamby/temp/cdt.20160224075206.p19g7Umwps/ess-15.09.2/doc/newfeat.texi:29:
|Argument of @gobblespaces has an extra }.
|
|   @par 
|
|  }
|   @doacronym ...#3@finish ->{@selectfonts @lsize #1}
| @def @temp {#2}@ifx @temp 
...
|   l.1 @acronym{ESS@gobblespaces }
|  @texinfoc
|   @scanmacro ...atspaces }@scantokens {#1@texinfoc }
| @aftermacro 
|   l.29 @item @ESS{}
|: A test framework has been set up.
|   ? Runaway argument?
|   
/home/lamby/temp/cdt.20160224075206.p19g7Umwps/ess-15.09.2/doc/newfeat.texi:29:
|Paragraph ended before @gobblespaces was complete.
|
|  @par 
|
|  }
|   @doacronym ...#3@finish ->{@selectfonts @lsize #1}
| @def @temp {#2}@ifx @temp 
...
|   l.1 @acronym{ESS@gobblespaces }
|  @texinfoc
|   @scanmacro ...atspaces }@scantokens {#1@texinfoc }
| @aftermacro 
|   l.29 @item @ESS{}
|: A test framework has been set up.
|   ? 
/home/lamby/temp/cdt.20160224075206.p19g7Umwps/ess-15.09.2/doc/newfeat.texi:72:
|Argument of @gobblespaces has an extra }.
|
|   @par 
|
|  }
|   @doacronym ...#3@finish ->{@selectfonts @lsize #1}
| @def @temp {#2}@ifx @temp 
...
|   l.1 @acronym{ESS@gobblespaces @gobblespaces }
|@texinfoc
|   @scanmacro ...atspaces }@scantokens {#1@texinfoc }
| @aftermacro 
|   @w #1->@leavevmode @hbox {#1
|   }
|   ...
|   l.72 @item @iESS{}
| : For naming inferior processes, ESS can use 
@code{project...
|   
|   ? 
|   
/home/lamby/temp/cdt.20160224075206.p19g7Umwps/ess-15.09.2/doc/newfeat.texi:72:
|Emergency stop.
|
|   @par 
|
|  }
|   @doacronym ...#3@finish ->{@selectfonts @lsize #1}
| @def @temp {#2}@ifx @temp 
...
|   l.1 @acronym{ESS@gobblespaces @gobblespaces }
|@texinfoc
|   @scanmacro ...atspaces }@scantokens {#1@texinfoc }
| @aftermacro 
|   @w #1->@leavevmode @hbox {#1
|   }
|   ...
|   l.72 @item @iESS{}
| : For naming inferior processes, ESS can use 
@code{project...
|   
|   
/home/lamby/temp/cdt.20160224075206.p19g7Umwps/ess-15.09.2/doc/newfeat.texi:72:
| ==> Fatal error occurred, no output PDF file produced!
|   Transcript written on ess.log.
|   /usr/bin/texi2dvi: pdfetex exited with bad status, quitting.

Might be the same texinfo 6.1 issue that also bit us in R.

The recommendation was to try

R_TEXI2DVICMD=emulation 

Otherwise it is not clear why this would break now when it a) didn't when the
package came out or b) we don't hear about it otherwise.

Dirk

|   Makefile:43: recipe for target 'ess.pdf' failed
|   make[1]: *** [ess.pdf] Error 1
|   make[1]: Leaving directory 

Bug#815624: marked as done (mate-dock-applet: fails to install: mate-dock-applet.postinst: glib-compile-schemas: not found)

[Debian Bug Tracking System]

Your message dated Wed, 24 Feb 2016 12:26:24 +
with message-id 
and subject line Bug#815624: fixed in mate-dock-applet 0.67-3
has caused the Debian Bug report #815624,
regarding mate-dock-applet: fails to install: mate-dock-applet.postinst: 
glib-compile-schemas: not found
to be marked as done.

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

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


-- 
815624: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815624
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mate-dock-applet
Version: 0.67-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

  Selecting previously unselected package mate-dock-applet.
  (Reading database ... 
(Reading database ... 27152 files and directories currently installed.)
  Preparing to unpack .../mate-dock-applet_0.67-2_amd64.deb ...
  Unpacking mate-dock-applet (0.67-2) ...
  Processing triggers for libglib2.0-0:amd64 (2.46.2-3) ...
  Setting up mate-dock-applet (0.67-2) ...
  /var/lib/dpkg/info/mate-dock-applet.postinst: 8: 
/var/lib/dpkg/info/mate-dock-applet.postinst: glib-compile-schemas: not found
  dpkg: error processing package mate-dock-applet (--configure):
   subprocess installed post-installation script returned error exit status 127
  Errors were encountered while processing:
   mate-dock-applet


cheers,

Andreas


mate-dock-applet_0.67-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: mate-dock-applet
Source-Version: 0.67-3

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

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated mate-dock-applet 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 24 Feb 2016 12:51:31 +0100
Source: mate-dock-applet
Binary: mate-dock-applet
Architecture: source amd64
Version: 0.67-3
Distribution: unstable
Urgency: medium
Maintainer: Debian MATE Packaging Team 
Changed-By: Mike Gabriel 
Description:
 mate-dock-applet - MATE Panel dock applet
Closes: 815624
Changes:
 mate-dock-applet (0.67-3) unstable; urgency=medium
 .
   * debian/control:
 + Add D (mate-dock-applet): libglib2.0-bin. (Closes: #815624).
Checksums-Sha1:
 f9b69c6c26c254a750483d8b5dc3adea2069977f 2101 mate-dock-applet_0.67-3.dsc
 685e2f8b0e71f05f43ec3a1dc90f3f1ec802c5f8 3820 
mate-dock-applet_0.67-3.debian.tar.xz
 1ad2dc1a30ee2af47fff487953ef8d88c153f0fd 45856 
mate-dock-applet_0.67-3_amd64.deb
Checksums-Sha256:
 5126cdc33994fc594e88997867328da058d30f8ab53dd13921c2267f9c47ebfe 2101 
mate-dock-applet_0.67-3.dsc
 a0774f49988f8387c2be90e0d2e1932c4df0ecbdf9cd8510aade960eb4991bbc 3820 
mate-dock-applet_0.67-3.debian.tar.xz
 ca05d8b0f4d8a76281d2062c8c1403f5f7e9a572a1e74d0f7a908d4f358bf1b7 45856 
mate-dock-applet_0.67-3_amd64.deb
Files:
 8eb9b0657e26cd0ea6012b5f834b0d54 2101 utils extra mate-dock-applet_0.67-3.dsc
 455c962e6415b7d19aa04635e75a7c6f 3820 utils extra 
mate-dock-applet_0.67-3.debian.tar.xz
 d814e3d6015d4ca25d0c79414215c7bc 45856 utils extra 
mate-dock-applet_0.67-3_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWzZmkAAoJEJr0azAldxsxRjgP/1xj3HYJqSH3GXr7UXh+60KD
BCpsodx6PHgV4RI9CRoLEgi+nJd9TiZ3gOdYUlitkFJirZ6auutyBN7QeHqQQiRe
hSX4szPtzwnHCgfOI1Z+mbcV8cQIKEevxoIZCHGBn92ThvwZqAF9qgiiV+O6zdE2
YNM3WvZANdRN2MmqOr7rgleeC/EHakTn+0w5TqGgOXGteuvukLq9O9M/c/IgTJZ1
wUdshbS1TF/Z/dD1zjgJCiOOyDqMq2hI3g1dRdW9zEf4XUWIJPFJIv/ige7LczfJ
G0OqvbyDZQQ/yhVRVBzDVY9W6gyWDX52BiBSwHdP5BaGGfWZnN4tDgDdoRaTeS2Y
QsdiRYXy92BsNMfVbt7y9m4M+QFxQauOxxh06qRhq3ri8elSsLZQii26IuAI5rc9
KVClpiVnQc/0Q+gVDaC2H6P+HXb3Wdi1CQZtBJhsUfRgTvEqiRUVvcZMjI9/pBvw
MEDv9zgRd3fqS/kjeCL/IlXuG7QX0kEKI4Da6Ai95jiPaV4n8jwFfYdb3tRMz3AD

Bug#798059: marked as done (turbojson: FTBFS: ImportError: from peak.rules import abstract, around, when)

[Debian Bug Tracking System]

Your message dated Wed, 24 Feb 2016 14:11:24 +0200
with message-id <56cd9dec.5070...@uct.ac.za>
and subject line turbojson: FTBFS: ImportError: from peak.rules import 
abstract, around, when
has caused the Debian Bug report #798059,
regarding turbojson: FTBFS: ImportError: from peak.rules import abstract, 
around, when
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.)


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

Dear Maintainer,

The package fails to build:

...

Get:34 http://urika:3142/ftp.debian.org/debian/ sid/main python-nose all 
1.3.6-1 [132 kB]
Get:35 http://urika:3142/ftp.debian.org/debian/ sid/main 
python-peak.util.decorators all 1.8-3 [22.9 kB]
Get:36 http://urika:3142/ftp.debian.org/debian/ sid/main python-peak.util all 
20110909-1 [69.1 kB]
Get:37 http://urika:3142/ftp.debian.org/debian/ sid/main python-peak.rules all 
0.5a1+r2707-1 [116 kB]
Get:38 http://urika:3142/ftp.debian.org/debian/ sid/main python-pysqlite2 amd64 
2.7.0-1 [35.0 kB]

...

==
ERROR: Failure: ImportError (No module named rules)
--
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/nose/loader.py", line 420, in 
loadTestsFromName
addr.filename, addr.module)
  File "/usr/lib/python2.7/dist-packages/nose/importer.py", line 47, in 
importFromPath
return self.importFromDir(dir_path, fqname)
  File "/usr/lib/python2.7/dist-packages/nose/importer.py", line 94, in 
importFromDir
mod = load_module(part_fqname, fh, filename, desc)
  File "/turbojson-1.3.2/turbojson/__init__.py", line 3, in 
from turbojson.jsonsupport import JsonSupport
  File "/turbojson-1.3.2/turbojson/jsonsupport.py", line 3, in 
from turbojson.jsonify import GenericJSON
  File "/turbojson-1.3.2/turbojson/jsonify.py", line 6, in 
from peak.rules import abstract, around, when
ImportError: No module named rules

--
Ran 1 test in 0.006s

FAILED (errors=1)
debian/rules:8: recipe for target 'override_dh_auto_test' failed

-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
--- End Message ---
--- Begin Message ---
Rebuilding turbojson does cause files to be installed in 
/usr/lib/python2.7/dist-packages instead of /usr/share/pyshared, but I 
cannot see anywhere that this is required.--- End Message ---

Processed: Still there with 3.0.4-1

[Debian Bug Tracking System]

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

> reopen 815047
Bug #815047 {Done: LaMont Jones } [postfix] postfix: Postfix 
fails to start after upgrade
Bug #815070 {Done: LaMont Jones } [postfix] postfix: does 
not start
Bug #815538 {Done: LaMont Jones } [postfix] postfix: Does 
not start after upgrading to 3.0.3-1 - instance conflicts
Bug #815622 {Done: LaMont Jones } [postfix] Postfix fails to 
start after apt-get upgrade
'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 postfix/3.0.4-1.
No longer marked as fixed in versions postfix/3.0.4-1.
No longer marked as fixed in versions postfix/3.0.4-1.
No longer marked as fixed in versions postfix/3.0.4-1.
> thanks
Stopping processing here.

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

Bug#815047: Still there with 3.0.4-1

[Michael Meskes]

reopen 815047
thanks

The latest uploaded does not seem to fix the problem:

dpkg -l postfix

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version  Architecture Description
+++-==---=
ii  postfix3.0.4-1  amd64High-performance mail transport 
agent

systemctl start postfix.service; systemctl status postfix.service

● postfix.service - LSB: Postfix Mail Transport Agent
   Loaded: loaded (/etc/init.d/postfix; bad; vendor preset: enabled)
  Drop-In: /run/systemd/generator/postfix.service.d
   └─50-postfix-$mail-transport-agent.conf
   Active: active (exited) since Mi 2016-02-24 12:44:34 CET; 1min 39s ago
 Docs: man:systemd-sysv-generator(8)
  Process: 24148 ExecStop=/etc/init.d/postfix stop (code=exited, 
status=0/SUCCESS)
  Process: 24552 ExecStart=/etc/init.d/postfix start (code=exited, 
status=0/SUCCESS)

Feb 24 12:44:33 feivel systemd[1]: Starting LSB: Postfix Mail Transport Agent...
Feb 24 12:44:33 feivel postmulti[24558]: fatal: instance /etc/postfix, 
shlib_directory=/usr/lib/postfix conflicts with instance /etc/postfix, 
daemon_directory=/usr/lib/postfix
Feb 24 12:44:34 feivel postfix[24552]: Starting Postfix Mail Transport Agent: 
postfix.
Feb 24 12:44:34 feivel systemd[1]: Started LSB: Postfix Mail Transport Agent.
Feb 24 12:45:37 feivel systemd[1]: Started LSB: Postfix Mail Transport Agent.
Feb 24 12:45:56 feivel systemd[1]: Started LSB: Postfix Mail Transport Agent.
Feb 24 12:46:13 feivel systemd[1]: Started LSB: Postfix Mail Transport Agent.

It does claim success despite the fatal message. Needless to say the system is 
down afterwards.

Michael
-- 
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org
Jabber: michael at xmpp dot meskes dot org
VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL

Bug#815781: hypre: FTBFS in sid

[Samuel Thibault]

Source: hypre
Version: 2.8.0b-2
Severity: serious
Justification: FTBFS

Hello,

hypre currently FTBFS in sid:

(cd src/babel-runtime && libtoolize)
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'config'.
libtoolize: linking file 'config/compile'
libtoolize: linking file 'config/config.guess'
libtoolize: linking file 'config/config.sub'
libtoolize:   error: 'config/depcomp' exists: use '--force' to overwrite
libtoolize: linking file 'config/install-sh'
libtoolize:   error: 'config/missing' exists: use '--force' to overwrite

Samuel

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

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

-- 
Samuel
 Les roots ne sont plus ce qu'ils étaient...Maintenant il sont dioxinés,
 c'est de la m... ! Avant on les élevaient avec du bon unix mais ça été
 remplacé par des farines industrielles nouvelles technologies (NT).
 -+- JdK in NPC : Exigez un root élevé sous la mère ! -+-

Processed: Bug#815624 marked as pending

[Debian Bug Tracking System]

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

> tag 815624 pending
Bug #815624 [mate-dock-applet] mate-dock-applet: fails to install: 
mate-dock-applet.postinst: glib-compile-schemas: not found
Added tag(s) pending.
> thanks
Stopping processing here.

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