Bug#815787: Fedora bug report of the (assumed) similar issue

[Russel Winder]

cf. https://bugzilla.redhat.com/show_bug.cgi?id=1309658

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

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#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 
/home/lamby/temp/cdt.201602250

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 /usr/include/osmium/io/detail/pbf_input_format.hpp:51,

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#815787: May be a kernel problem not a pulseaudio one?

[Russel Winder]

I have tried rebooting to kernel 4.2, 4.3 as well as 4.4. This is only
a problem for kernel 4.4, things works fine using kernels 4.3 and 4.2.

I also get similar problems when booting to Fedora, there though kernel
4.4 works fine and kernel 4.5 fails.

This may not be a pulseaudio problem per se. Should I raise a new bug
report or can this one be relocated to get to the people that need to
look at it?


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

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#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#815791: RFS: gtranscribe/0.3-1 [ITP] -- simple GTK+ tool focussed on easy transcription of spoken words

[Paul Wise]

On Wed, Feb 24, 2016 at 9:35 PM, Philip Rinn wrote:

>   gTranscribe is a simple GTK+ tool to transcribe audio files and other
>   sources. The playback speed can be adjusted without changing the pitch of 
> the
>   voice. It supports spell checking and resuming at the last transcribed
>   position.

There are apparently a number of other tools for this in Debian, I
wonder if this one is better than the ones we have now. If gTranscribe
reaches Debian, you may want to ensure it is mentioned on the
appropriate pages of the DebConf subtitles team. You may also want to
join that team :)

https://wiki.debconf.org/wiki/Videoteam/Subtitles

As you are upstream, you may want to consider reading our upstream guide:

https://wiki.debian.org/UpstreamGuide

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Bug#814680: RFS: stp/2.1.2+dfsg-1 [ITP] -- Simple theorem prover

[Marko Dimjašević]

Hi Afif,

On Wed, 2016-02-24 at 21:16 -0800, Afif Elghraoui wrote:

> Thanks for working on this package. 

Thank you for taking a look at the package!


> I took a look at it and found some issues. The first is the requirement
> of the additional file stp_2.1.2+dfsg.orig-outputcheck.tar.gz. You
> should not be directly using anything outside the packaging directory.

The archive corresponds to OutputCheck, a build dependency that runs
STP's regression tests. OutputCheck doesn't have a Debian package, and
based on my discussion with upstream developers and a Debian developer
that sponsored the first upload of STP to New, this was the proposed
approach. OutputCheck is, to the best of our knowledge, used only by
STP, and the upstream developers have a plan of re-basing STP tests on a
different testing framework soon. Furthermore, OutputCheck is not
actively developed any more.

I also found examples of other Debian packages being done in the same
way - having a small build dependency shipped as an archive. I don't
have a reference supporting that, but my memory tells me I saw an
example with a Debian Perl package.


> There's at least one other issue--in debian/control, the Vcs URLs should
> be pointing to the packaging repository rather than upstream.

Ok, I didn't know this about the Vcs URL! Recently I added a Git repo
for STP on Alioth. Should I put the repo's URL to d/control?


>  I didn't check further because the package currently doesn't build.

Can you clarify this? It builds in pbuilder with defaults settings.


> Most such problems can be found by running lintian, but we first need
> the package to build in a minimal environment.

I haven't seen the Vcs problem in a report by Lintian. Usually I use the
"-i -I" options. Can you be specific, i.e. which other options should I
use that reveal issues you are talking about?


-- 
Regards,
Marko Dimjašević  .   University of Utah
https://dimjasevic.net/marko . PGP key ID: 1503F0AA
Learn email self-defense!  https://emailselfdefense.fsf.org


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

Bug#815863: Constitution change after 2015/vote_003 'Update Standard Resolution Procedure'

[Didier 'OdyX' Raboud]

Package: doc-debian
Version: 6.3
Severity: important
Tags: patch

Hi,

As result of the 2015/vote_003 GR 'Update Standard Resolution
Procedure' [0], the Constitution has been changed.

Please find hereby attached the patch adding the changes to a new 1.6
revision of the Constitution.

Cheers,
OdyX

[0] https://www.debian.org/vote/2015/vote_003
>From 9afc41b3408dce90077c3abbabb0e950bde600d7 Mon Sep 17 00:00:00 2001
From: Didier Raboud 
Date: Thu, 25 Feb 2016 08:03:50 +0100
Subject: [PATCH] Update the Constitution to version 1.6, as per "General
 Resolution: Update Standard Resolution Procedure",
 https://www.debian.org/vote/2015/vote_003

---
 .../doc-debian.doc-base.debian-constitution-text   |   3 +-
 doc/Makefile   |   2 +-
 doc/constitution.1.5.wml   | 996 +
 doc/constitution.wml   |  10 +-
 4 files changed, 1005 insertions(+), 6 deletions(-)
 create mode 100644 doc/constitution.1.5.wml

diff --git a/debian/doc-debian.doc-base.debian-constitution-text b/debian/doc-debian.doc-base.debian-constitution-text
index 5bbcfbd..d844de8 100644
--- a/debian/doc-debian.doc-base.debian-constitution-text
+++ b/debian/doc-debian.doc-base.debian-constitution-text
@@ -2,7 +2,8 @@ Document: debian-constitution-text
 Title: Debian Constitution
 Author: The Debian Project
 Abstract: This document contains the complete text of Debian Project
- Constitution (v1.5), in text format. Version 1.5, ratified on
+ Constitution (v1.6), in text format. Version 1.6, ratified on
+ Deceber 13th, 2015, supersedes Version 1.5, ratified on
  January 9th, 2015, supersedes Version 1.4, ratified on October 7th,
  2007, Version 1.3 ratified on September 24th, 2006, version 1.2
  ratified on October 29th, 2003, Version 1.1 ratified on June 21st,
diff --git a/doc/Makefile b/doc/Makefile
index 0c4b6a4..91bcb8e 100644
--- a/doc/Makefile
+++ b/doc/Makefile
@@ -13,7 +13,7 @@ bug-log-mailserver.wml  bug-reporting.wml \
 bug-mailserver-refcard.wml  constitution.wml  social-contract.wml\
 bug-maint-info.wml  constitution.1.1.wml  social-contract.1.0.wml \
 constitution.1.2.wmlsocial-contract.wml 	  constitution.1.3.wml \
-constitution.1.4.wml
+constitution.1.4.wmlconstitution.1.5.wml
 
 # These are the automatic files we can generate:
 TXTFILES = $(subst .wml,.txt,$(WMLFILES))
diff --git a/doc/constitution.1.5.wml b/doc/constitution.1.5.wml
new file mode 100644
index 000..9d3410f
--- /dev/null
+++ b/doc/constitution.1.5.wml
@@ -0,0 +1,996 @@
+
+Constitution for the Debian Project (v1.5)
+ 
+
+Version 1.5 ratified on January 9th, 2015. Supersedes
+Version 1.4 ratified on October 7th,
+2007,
+Version 1.3 ratified on September 24th,
+2006,
+Version 1.2 ratified on October 29th,
+2003 and
+Version 1.1 ratified on June 21st,
+2003, which itself supersedes Version 1.0
+ratified on December 2nd, 1998.
+
+
+
+1. Introduction
+
+The Debian Project is an association of individuals who have
+made common cause to create a free operating system.
+
+This document describes the organisational structure for formal
+decision-making in the Project.  It does not describe the goals of the
+Project or how it achieves them, or contain any policies except those
+directly related to the decision-making process.
+
+2. Decision-making bodies and individuals
+
+Each decision in the Project is made by one or more of the
+following:
+
+
+  The Developers, by way of General Resolution or an election;
+
+  The Project Leader;
+
+  The Technical Committee and/or its Chairman;
+
+  The individual Developer working on a particular task;
+
+  Delegates appointed by the Project Leader for specific
+  tasks;
+
+  The Project Secretary.
+
+
+Most of the remainder of this document will outline the powers of
+these bodies, their composition and appointment, and the procedure for
+their decision-making.  The powers of a person or body may be subject to
+review and/or limitation by others; in this case the reviewing body or
+person's entry will state this.  In the list above, a person or
+body is usually listed before any people or bodies whose decisions they
+can overrule or who they (help) appoint - but not everyone listed
+earlier can overrule everyone listed later.
+
+2.1. General rules
+
+
+  
+Nothing in this constitution imposes an obligation on anyone to
+do work for the Project.  A person who does not want to do a task
+which has been delegated or assigned to them does not need to do
+it.  However, they must not actively work against these rules and
+decisions properly made under them.
+  
+
+  
+A person may hold several posts, except that the Project Leader,
+Project Secretary and the Chairman of the Technical Committee must
+be distinct, and that the Leader cannot appoint themselves as their
+own Delegate.
+  
+
+  
+A person may leave the Project or resign from a particular po

Bug#815862: rsyslog re-spawns immediately when stopped

[Brainslug]

Package: rsyslog
Version: 8.16.0-1
Severity: important

Dear Maintainer,

 it appears that I am not able to shut down rsyslog via systemctl or
init script. It auto-respawns immediately.

This is a huge problem b/c everytime I plug in a USB 3.0 device my
system crashes and syslog / kern.log fill up my disks very quickly even
after I remove the device.

Here is what I do:

root@localhost:~# ps faux | grep rsyslogd
...
root  3144  0.0  0.0 258296  3020 ?Ssl  00:41   0:00
/usr/sbin/rsyslogd -n


root@localhost:~# /etc/init.d/rsyslog stop
[] Stopping rsyslog (via systemctl): rsyslog.serviceWarning:
Stopping rsyslog.service, but it can still be activated by:
  syslog.socket
  . ok


root@localhost:~# ps faux | grep rsyslogd
...
root 25326  0.0  0.0 258296  3020 ?Ssl  00:41   0:00
/usr/sbin/rsyslogd -n


The PID of rsyslogd has changed, so the process appears to have gotten
killed originally but my logfiles keep getting flooded thanks to the
auto-spawned process.


The only way for me to "stop" logfile flooding is:

mv /usr/sbin/rsyslog /tmp
/etc/init.d/rsyslog stop
mv /tmp/rsyslog /usr/sbin

This is not good.

My /etc/rsyslog.conf is the original file provided by the .deb package
and there is nothing in /etc/rsyslog.d/

When trying to stop rsyslogd via init script, I see this in /var/log/syslog:

Feb 25 00:51:38 localhost rsyslogd: [origin software="rsyslogd"
swVersion="8.16.0" x-pid="3595" x-info="http://www.rsyslog.com";] exiting
on signal 15.
Feb 25 00:51:38 localhost rsyslogd: [origin software="rsyslogd"
swVersion="8.16.0" x-pid="3681" x-info="http://www.rsyslog.com";] start
Feb 25 00:51:38 localhost systemd[1]: Stopping System Logging Service...
Feb 25 00:51:38 localhost systemd[1]: Stopped System Logging Service.
Feb 25 00:51:38 localhost systemd[1]: Starting System Logging Service...
Feb 25 00:51:38 localhost systemd[1]: Started System Logging Service.

Not sure why I get duplicate entries for stops and starts.


Any help would be much appreciated.



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

Kernel: Linux 4.3.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: systemd (via /run/systemd/system)

Versions of packages rsyslog depends on:
ii  init-system-helpers  1.28
ii  libc62.21-9
ii  libestr0 0.1.10-1
ii  libjson-c2   0.11-4
ii  liblogging-stdlog0   1.0.5-2
ii  liblognorm2  1.1.2-1.1
ii  libsystemd0  228-6
ii  libuuid1 2.27.1-3
ii  lsb-base 9.20160110
ii  zlib1g   1:1.2.8.dfsg-2+b1

Versions of packages rsyslog recommends:
ii  logrotate  3.8.7-2

Versions of packages rsyslog suggests:
pn  rsyslog-doc
pn  rsyslog-gnutls 
pn  rsyslog-gssapi 
pn  rsyslog-mongodb
pn  rsyslog-mysql | rsyslog-pgsql  
pn  rsyslog-relp   

-- no debconf information

Bug#815754: [Pkg-gridengine-devel] Bug#815754: [PATCH] gridengine: proposal to add ppc64el architecture

[Afif Elghraoui]

Hello,

على الأربعاء 24 شباط 2016 ‫01:54، كتب Frederic Bonnard:
>  
> would it be possible to enable build of gridengine on ppc64el architecture ?
> Here is a patch for that, can anybody review it ?
> On my side, it seems to build well.
> 

Many thanks for the patch. Have you tried this on ppc64el with the
latest gridengine package/upstream version in preparation in git [1]? I
see code there that seems to at least intend to handle it.

Many thanks and regards
Afif

1. http://anonscm.debian.org/cgit/pkg-gridengine/pkg-gridengine.git
(master branch)

-- 
Afif Elghraoui | عفيف الغراوي
http://afif.ghraoui.name

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#815843: ocserv: Segfault when loading ocserv

[Nikos Mavrogiannopoulos]

On Thu, Feb 25, 2016 at 1:52 AM, Tony Zhou  wrote:
> Package: ocserv
> Version: 0.10.11-2
> Severity: important
>
> Dear Maintainer,
> I have just upgraded my ocserv from 0.10.11-1 to 0.10.11-2 in order to
> gain RADIUS support. However, when I try to start ocserv it throws a
> segfault and exits, either by systemd or manually executing ocserv. When
> ocserv loads as a service, the journal has the following output:
>
> Feb 25 09:44:48 vpn ocserv[1065]: listening on 2 systemd sockets...
> Feb 25 09:44:48 vpn ocserv[1065]: main: initialized ocserv 0.10.11
> Feb 25 09:44:48 vpn ocserv[1066]: sec-mod: reading supplemental config from 
> files
> Feb 25 09:44:48 vpn ocserv[1066]: sec-mod: sec-mod initialized (socket: 
> /var/run/ocserv-socket.1065)
> Feb 25 09:44:48 vpn systemd[1]: ocserv.service: Main process exited, 
> code=killed, status=6/ABRT
> Feb 25 09:44:48 vpn ocserv[1065]: *** Error in `ocserv-main': free(): invalid 
> pointer: 0xb78e9228 ***

Most likely it is that issue fixed in ocserv 0.10.12 (the underlying
issue is in gnutls):
https://gitlab.com/ocserv/ocserv/commit/874c65f47e83fabd2e21b40bc0953f6f606f006a

regards,
Nikos

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#783711: #783711: redmine: Version number is misleading/wrong

[Reverend Homer]

Hi,
any progress with that? Looks like the version is still wrong.
--
Regards,
R.H.

Bug#186568: bug#22793: grep -E assertion failure with back references

[arnold]

Paul Eggert  wrote:

> With recent 'grep' you can work around the problem by configuring 
> --with-included-regex.

Not so. I did a fresh

./boostrap
./configure --with-included-regex
make

and it still core dumps:

$ echo abc | ./src/grep -E  '(.*)(.*)(.*)\3\2\1'
grep: regexec.c:1413: pop_fail_stack: Assertion `((Idx) (num) < ((Idx) -2))' 
failed.
Aborted (core dumped)

I looked at it in a debugger fs->num before the --fs->num executes looks to
be -1.

Thanks,

Arnold

Bug#815860: libtesseract-dev: conflict with libtesseract4 3.04.01-2+b1

[Arthur Marsh]

Package: libtesseract-dev
Version: 3.04.01-3
Severity: normal

Dear Maintainer,

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

   * What led up to the situation?

Trying to upgrade tesseract-ocr from 3.04.01-2+b1 to 3.04.01-3:

Preparing to unpack .../libtesseract3_3.04.01-3_amd64.deb ...
Unpacking libtesseract3 (3.04.01-3) ...
dpkg: error processing archive 
/var/cache/apt/archives/libtesseract3_3.04.01-3_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/libtesseract.so.3.0.4', which is also in package 
libtesseract4 3.04.01-2+b1
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/libtesseract3_3.04.01-3_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
Failed to perform requested operation on package.  Trying to recover:
Press Return to continue.


   * 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 ***


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

Kernel: Linux 4.5.0-rc5+ (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: sysvinit (via /sbin/init)

Bug#815015: Acknowledgement (gnome-shell crashes after moving 2048-qt to other screen)

[Reverend Homer]

ping?

17.02.2016 22:18, Debian Bug Tracking System пишет:

Thank you for filing a new Bug report with Debian.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

As you requested using X-Debbugs-CC, your message was also forwarded to
   mk.43.e...@gmail.com
(after having been given a Bug report number, if it did not have one).

Your message has been sent to the package maintainer(s):
  Debian GNOME Maintainers 

If you wish to submit further information on this problem, please
send it to 815...@bugs.debian.org.

Please do not send mail to ow...@bugs.debian.org unless you wish
to report a problem with the Bug-tracking system.



--
Regards,
R.H.

Bug#813696: Acknowledgement (systemd-nspawn failed to move interface to namespace: File exists)

[Reverend Homer]

ping? Can anyone tell me sth about that?
I'm copying this mail to Michael Biebl too. Looking forward to read his 
comment.


04.02.2016 15:39, Debian Bug Tracking System пишет:

Thank you for filing a new Bug report with Debian.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

As you requested using X-Debbugs-CC, your message was also forwarded to
   mk.43.e...@gmail.com
(after having been given a Bug report number, if it did not have one).

Your message has been sent to the package maintainer(s):
  Debian systemd Maintainers 

If you wish to submit further information on this problem, please
send it to 813...@bugs.debian.org.

Please do not send mail to ow...@bugs.debian.org unless you wish
to report a problem with the Bug-tracking system.



--
Regards,
R.H.

Bug#815843: Some findings

[tonytzhou]

After tweaking through each line of the config file, I found the problem turned 
out to be that I used a combined certificate for server, which has the server 
certificate and the intermediate one. Seems that ocserv doesn’t like the server 
cert in this way, so it just failed noisily.

I guess this is probably an upstream issue – should ocserv print a message that 
it does not like the idea of combined certs, rather than throwing a segfault?

Bug#815799: RFS: kateperlcheck/1.7-1 [put in ITP ]

[Dmitry Bogatov]

I am no DD, so I would not be able to sponsor. But here is review:

> Dear mentors,
>
>   I am looking for a sponsor for my package "kateperlcheck"
>
>  * Package name: kateperlcheck
>Version : 1.7-1
>Upstream Author : dirk Lindner  
>  * URL : http://kate.lindnerei.de/
>  * License : gpl
>Section : editors

d/control:

> Section: kde
Maybe devel?

> Build-Depends: debhelper (>= 8.0.0), cmake
debhelper (>= 9), please

> Standards-Version: 3.9.4
3.9.7, please

> #Vcs-Git: git://git.debian.org/collab-maint/kateperlcheck.git
> #Vcs-Browser: 
http://git.debian.org/?p=collab-maint/kateperlcheck.git;a=summary
Why commented out?

> Package: kateperlcheck
> Architecture: i386
Architecture 'any', please

Did you used sbuild or pbuilder? Seems dependencies are incomplete, since
configuration fails on my box, complaining about missing `FindKDE4.cmake`.

> E source-is-missing
> kateperlcheck/CMakeFiles/2.8.12.2/CMakeDetermineCompilerABI_C.bin
> kateperlcheck/CMakeFiles/2.8.12.2/CMakeDetermineCompilerABI_CXX.bin
> kateperlcheck/CMakeFiles/2.8.12.2/CompilerIdC/a.out
> kateperlcheck/CMakeFiles/2.8.12.2/CompilerIdCXX/a.out

CMakeFiles are binary files, and lintian rightfully asks where is
their source.  Correct approach is to NOT have them in tarball in
first place, they are generated by `cmake'. Since you are upstream,
you can easily fix it, otherwise you would be interested in
Files-Excluded.

I do not use KDE, so I can't check the usefulness of your package.

-- 
Accept: text/plain, text/x-diff
Accept-Language: eo,en,ru
X-Keep-In-CC: yes
X-Web-Site: sinsekvu.github.io

Bug#814680: RFS: stp/2.1.2+dfsg-1 [ITP] -- Simple theorem prover

[Afif Elghraoui]

Hi, Marko,

على الأحد 21 شباط 2016 ‫18:27، كتب Marko Dimjašević:
> 
> Let me know if I can do something to get you interested in sponsoring
> this package for the Simple theorem prover. I am desperately looking for
> a sponsor. The package has been in the New queue before. Its details are
> given below. The package is also available on Alioth:
> 
> git.debian.org/git/debian-science/packages/stp.git
> 
> 

Thanks for working on this package. I took a look at it and found some
issues. The first is the requirement of the additional file
stp_2.1.2+dfsg.orig-outputcheck.tar.gz. You should not be directly using
anything outside the packaging directory.

There's at least one other issue--in debian/control, the Vcs URLs should
be pointing to the packaging repository rather than upstream. I didn't
check further because the package currently doesn't build. Most such
problems can be found by running lintian, but we first need the package
to build in a minimal environment.

regards
Afif

-- 
Afif Elghraoui | عفيف الغراوي
http://afif.ghraoui.name

Bug#814451: openmpi: stderr output is an error message

[Gilles Gouaillardet]

Folks,

i was able to reproduce this behaviour.

here is what the openib (e.g. infiniband) btl does :
- if running on Linux, and there is no /sys/class/infiniband, then the
btl disqualifies itself (see ompi_common_verbs_check_basics()(
- if the btl did not previously disqualified itself, and there is no
infiniband port available, then a warning message is issued (we
consider there is likely something wrong)

i am able to reproduce this scenario on a VM with no infiniband
hardware by loading the mlx4_core kernel module.

can you confirm you are running into this very same scenario ?
is the mlx4_core.ko or similar module loaded ?
if yes, is there any reason for it to be loaded ?
is the __linux__ macro defined on debian ?
does the /sys/class/infiniband directory exists ?
is this directory empty ?

from an OpenMPI point of view, it could be possible to disqualify the
openib btl with no warning message if /sys/class/infiniband is empty,
would that be helpful ?

Cheers,

Gilles

Bug#797906: jessie-pu: package dolibarr/3.5.5+dfsg1-2

[Salvatore Bonaccorso]

Hi Laurent,

On Tue, Feb 23, 2016 at 12:48:16PM +, Adam D. Barratt wrote:
> On 2016-02-23 12:29, Laurent Destailleur (aka Eldy) wrote:
> >To fix opened securities hole into dolibarr stable package, i prepared
> >the following 3 patch. This patch is now already included into
> >unstable.
> >It fixes the following CVE:
> >
> >* Fix CVE-2016-1912 (Closes: #812496)
> >* Fix CVE-2015-8685 (Closes: #812449)
> >* Fix CVE-2015-3935 (Closes: #787762)
> >
> >This is the debdiff. Can my mentor (Raphael Hertzog) push the new
> >package with this patch into stable ?
> 
> Are you asking about stable or stable-security? Your changelog doesn't say
> either but you appear to have CCed the Security Team whilst following up to
> a release.debian.org bug.

We do not plan to release a DSA for these dolibarr issues but it still
would be good to have those fixed in Jessie. Those proposing an update
via a upcoming Jessie point release would be great.

Regards,
Salvatore


signature.asc
Description: Digital signature

Bug#815618: ovmf: Please someone create a DFSG-free ovmf variant

[Paul Wise]

On Mon, 22 Feb 2016 23:49:43 +0100 Francesco Poli wrote:

> As far as I know, package ovmf is needed in order to create and
> run a virtual UEFI machine. Unfortunately, ovmf is non-free, since the
> included Intel FAT file system driver has "additional terms" that
> restrict redistribution and use to the implementation of (U)EFI
> specifications.

FYI, I have recently contacted Tony Mangefeste, the new Tianocore
community manager about this issue, didn't get a reply yet.

http://firmwaresecurity.com/2016/02/10/tony-mangefeste-new-tianocore-community-manager/

> Do you know of any such alternative?

There is no such alternative.

> Perhaps the FAT driver in some *BSD kernel could be adapted:

The rumpkernel framework could be one possibility:

http://rumpkernel.org/
https://ftp-master.debian.org/new/rumpkernel_0~20150715-1.html

There is an independently implemented FatFs library available here:

http://elm-chan.org/fsw/ff/00index_e.html

If GPL code is OK, there was a project to create a library out of the
Linux kernel code so that userland programs can use it:

https://www.phoronix.com/scan.php?page=news_item&px=Intel-Kernel-Library-LKL

-- 
bye,
pabs

https://wiki.debian.org/PaulWise




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

Bug#814755: luatex font bug: "checksum mismatch" warnings on 64bit system

[Norbert Preining]

Hi Igor,


> I reported this bug to Debian some days ago, but did not get a
> response, so I'm writing here. Keep the CC please.

You expect quick response.

> luatex gives "checksum mismatch" warnings:

I am not sure, but it might be related to this discussion on
the fontinst mailing list:
http://www.tug.org/pipermail/fontinst/2016/001692.html

Norbert


PREINING, Norbert   http://www.preining.info
JAIST, Japan TeX Live & Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0  ACF0 6CAC A448 860C DC13

Bug#815815: Patool error

[sudheesh shetty]

Hi,
This is the actual error I get.
patool bash: completion: function `_patool' not found

Bug#815630: Aw: Bug#815630: Acknowledgement (2.4.67-1 causes black screen after login on plasma desktop)

[Sten Heinze]

Updating libdrm-intel1 with other packages today lead to a working system with 
version 2.4.67-1. The following packages were updated:

libc-bin:amd64 2.21-8 2.21-9
libc6:amd64 2.21-8 2.21-9
libvlccore8:amd64 2.2.2-3+b1 2.2.2-4
vlc-data:all 2.2.2-3 2.2.2-4
libvlc5:amd64 2.2.2-3+b1 2.2.2-4
libavresample-ffmpeg2:amd64 7:2.8.5-1+b1 7:2.8.6-1+b1
libswresample-ffmpeg1:amd64 7:2.8.5-1+b1 7:2.8.6-1+b1
libpostproc-ffmpeg53:amd64 7:2.8.5-1+b1 7:2.8.6-1+b1
libswscale-ffmpeg3:amd64 7:2.8.5-1+b1 7:2.8.6-1+b1
libavformat-ffmpeg56:amd64 7:2.8.5-1+b1 7:2.8.6-1+b1
libavcodec-ffmpeg56:amd64 7:2.8.5-1+b1 7:2.8.6-1+b1
libavutil-ffmpeg54:amd64 7:2.8.5-1+b1 7:2.8.6-1+b1
libkate1:amd64 0.4.1-5 0.4.1-7
libpng12-0:amd64 1.2.54-1 1.2.54-3
vlc:amd64 2.2.2-3+b1 2.2.2-4
vlc-nox:amd64 2.2.2-3+b1 2.2.2-4
multiarch-support:amd64 2.21-8 2.21-9
iproute2:amd64 4.3.0-1 4.3.0-1+b1
libc-l10n:all 2.21-8 2.21-9
locales:all 2.21-8 2.21-9
libdrm-intel1:amd64 2.4.66-2 2.4.67-1
libutempter0:amd64 1.1.6-1 1.1.6-3
xserver-xorg-video-intel:amd64 2:2.99.917+git20160127-1+b1 
2:2.99.917+git20160218-1

Hope that helps someone.

Sten

> Gesendet: Montag, 22. Februar 2016 um 22:15 Uhr
> Von: "Debian Bug Tracking System" 
> An: "Sten Heinze" 
> Betreff: Bug#815630: Acknowledgement (2.4.67-1 causes black screen after 
> login on plasma desktop)
>
> Thank you for filing a new Bug report with Debian.
> 
> This is an automatically generated reply to let you know your message
> has been received.
> 
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
> 
> As you requested using X-Debbugs-CC, your message was also forwarded to
>   s...@gmx.de
> (after having been given a Bug report number, if it did not have one).
> 
> Your message has been sent to the package maintainer(s):
>  Debian X Strike Force 
> 
> If you wish to submit further information on this problem, please
> send it to 815...@bugs.debian.org.
> 
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
> 
> -- 
> 815630: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815630
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
> 

Bug#815859: ITP: seq-el -- sequence manipulation functions for Emacs Lisp

[Sean Whitton]

Package: wnpp
Severity: wishlist
Owner: Sean Whitton 

* Package name: seq-el
  Version : 1.11
  Upstream Author : Nicolas Petton 
* URL : https://elpa.gnu.org/packages/seq.html
* License : GPL-3
  Programming Lang: Emacs Lisp
  Description : sequence manipulation functions for Emacs Lisp

seq.el provides sequence-manipulation functions for Emacs Lisp that
complement basic functions provided by subr.el.

I am packaging seq.el as a dependency of flycheck, another ITP of mine.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#814566: networkd >= 229-1 starts assigning IPv6 addresses/ routes to lower bridge members

[Stefan Lippers-Hollmann]

Hi

Git bisecting the upstream systemd github repository in a disposable VM 
points at

Revert "networkd: ndisc - revert to letting the kernel handle NDisc"
https://github.com/systemd/systemd/commit/fe30727643a7c53faa29f1caa8dcabcb2b6f6fcb

$ git bisect log
git bisect start
# good: [dd050decb6ad131ebdeabb71c4f9ecb4733269c0] build: bump version numbers
git bisect good dd050decb6ad131ebdeabb71c4f9ecb4733269c0
# bad: [96b08d65a12c304c59febbc52bc871753f0c6f31] Merge pull request #2722 from 
torstehu/fix-typo2
git bisect bad 96b08d65a12c304c59febbc52bc871753f0c6f31
# bad: [c64327b7648f988186a3de55dde264c7c21f7d5f] Merge pull request #2347 from 
aroig/gh/fix-udev-user-wants
git bisect bad c64327b7648f988186a3de55dde264c7c21f7d5f
# bad: [a0361331758dbdb2375d6f871bc959116b699e31] Merge pull request #2143 from 
poettering/dnssec4
git bisect bad a0361331758dbdb2375d6f871bc959116b699e31
# bad: [c7bb28732f0c5d6e964197753d1d8d8a6a591d2f] tests: don't run test on 
incomplete setup
git bisect bad c7bb28732f0c5d6e964197753d1d8d8a6a591d2f
# bad: [58db254ade4fb2ef77de68f28c4f13814819f6a1] resolved: implement 
client-side DNAME resolution
git bisect bad 58db254ade4fb2ef77de68f28c4f13814819f6a1
# bad: [61fea35e14d84144e6e2122f5cd247f9c7e6245e] tests: fix initrd searching 
on Debian/Ubuntu
git bisect bad 61fea35e14d84144e6e2122f5cd247f9c7e6245e
# good: [39609489ca9925f94fdd4ef12a8b3d5ee2e14ddd] update TODO
git bisect good 39609489ca9925f94fdd4ef12a8b3d5ee2e14ddd
# bad: [265fb8052dc3ca334951a5693cdfd6fb968c94c7] Merge pull request #1958 from 
teg/networkd-fixes
git bisect bad 265fb8052dc3ca334951a5693cdfd6fb968c94c7
# bad: [854c1123f5fb6704e900d34c0165360f77ce4ef8] Merge pull request #1944 from 
poettering/randoms-ec
git bisect bad 854c1123f5fb6704e900d34c0165360f77ce4ef8
# good: [3ccd316353532ff60326e91153677c308c032ecb] sd-ndisc: drop RA packets 
from non-link-local addresses
git bisect good 3ccd316353532ff60326e91153677c308c032ecb
# bad: [25422154e8ebda7a9bfd52d7e0cbd7254fed39b3] Merge pull request #1948 from 
teg/networkd-fixes
git bisect bad 25422154e8ebda7a9bfd52d7e0cbd7254fed39b3

Reverting just fe30727643a7c53faa29f1caa8dcabcb2b6f6fcb on top
of systemd 229-1 (after resolving minor merge conflicts, see attached)
fixes this bug for me (networkd's IPv6 handling is still not quite 
perfect, but at least it's back to a networkd <= 228-6 equivalent 
state and results in functional IPv6 connectivity for me again, while
networkd 229-1, and current upstream git HEAD, are totally broken).

Regards
Stefan Lippers-Hollmann
From f1f54ef2f8509100483cb8dc8a9a2f9c3c823700 Mon Sep 17 00:00:00 2001
From: Stefan Lippers-Hollmann 
Date: Thu, 25 Feb 2016 00:29:28 +0100
Subject: [PATCH] Revert "Revert "networkd: ndisc - revert to letting the
 kernel handle NDisc""

networkd v229 introduces many regressions in IPv6 related RA handling,
reverting this at least fixes:
 * https://bugs.debian.org/814566
   networkd >= 229-1 starts assigning IPv6 addresses/ routes to lower bridge
   members
   which may be https://github.com/systemd/systemd/issues/2572
   [networkd] bridged intefaces still get RA ipv6 addresses #2572
and is quite likely to also fix:
 * https://bugs.debian.org/814667
   systemd-networkd overrides default kernel net.ipv6.conf.interface.accept_ra
 * https://bugs.debian.org/815586
   does its own RA handling and is doing it wrong

This reverts commit fe30727643a7c53faa29f1caa8dcabcb2b6f6fcb.

Signed-off-by: Stefan Lippers-Hollmann 
---
 src/network/networkd-link.c  | 20 
 src/network/networkd-ndisc.c | 13 -
 2 files changed, 20 insertions(+), 13 deletions(-)

diff --git a/src/network/networkd-link.c b/src/network/networkd-link.c
index 692c0bf..16c9927 100644
--- a/src/network/networkd-link.c
+++ b/src/network/networkd-link.c
@@ -623,9 +623,6 @@ void link_check_ready(Link *link) {
  !link->dhcp4_configured && !link->dhcp6_configured))
 return;
 
-if (link_ipv6_accept_ra_enabled(link) && !link->ndisc_configured)
-return;
-
 SET_FOREACH(a, link->addresses, i)
 if (!address_is_ready(a))
 return;
@@ -1923,6 +1920,7 @@ static int link_set_ipv6_privacy_extensions(Link *link) {
 
 static int link_set_ipv6_accept_ra(Link *link) {
 const char *p = NULL;
+const char *v;
 int r;
 
 /* Make this a NOP if IPv6 is not available */
@@ -1935,12 +1933,16 @@ static int link_set_ipv6_accept_ra(Link *link) {
 if (!link->network)
 return 0;
 
+if (link_ipv6_accept_ra_enabled(link))
+v = "1";
+else
+v = "0";
+
 p = strjoina("/proc/sys/net/ipv6/conf/", link->ifname, "/accept_ra");
 
-/* We handle router advertisments ourselves, tell the kernel to GTFO */
-r = write_string_file(p, "0", WRITE_STRING_FILE_VERIFY_ON_FAILURE);
+r = write_string_file(p, v, WRITE_STRING_FILE_VERIFY_ON_FAILURE);

Bug#815858: glibc: [INTL:ja] Japanese debconf templates translation update

[Takuma Yamada]

Source: glibc
Severity: wishlist
Tags: l10n patch

Dear Maintainer,

Here's Japanese po-debconf templates translation (ja.po) file that 
reviewed by several Japanese Debian developers and users.

Please copy the attachment into debian/po/ja.po.

Kind regards.
--
Takuma Yamada


-- 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/2 CPU cores)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
# Kenshi Muto , 2007
# GOTO Masanori , -2007
# Nobuhiro Iwamatsu , 2010
#
#Translators, if you are not familiar with the PO format, gettext
#documentation is worth reading, especially sections dedicated to
#this format, e.g. by running:
# info -n '(gettext)PO Files'
# info -n '(gettext)Header Entry'
#
#Some information specific to po-debconf are available at
#/usr/share/doc/po-debconf/README-trans
# or http://www.debian.org/intl/l10n/po-debconf/README-trans
#
#Developers do not need to manually edit POT or PO files.
# Takuma Yamada , 2016.
#
msgid ""
msgstr ""
"Project-Id-Version: eglibc_2.13-38\n"
"Report-Msgid-Bugs-To: gl...@packages.debian.org\n"
"POT-Creation-Date: 2015-12-07 14:56+0100\n"
"PO-Revision-Date: 2016-02-25 13:03+0900\n"
"Last-Translator: Takuma Yamada \n"
"Language-Team: Japanese \n"
"Language: ja\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=1; plural=0;\n"
"X-Generator: Gtranslator 2.91.6\n"

#. Type: multiselect
#. Choices
#: ../debhelper.in/locales.templates:1001
msgid "All locales"
msgstr "すべてのロケール"

#. Type: multiselect
#. Description
#: ../debhelper.in/locales.templates:1002
msgid "Locales to be generated:"
msgstr "生成するロケールの選択:"

#. Type: multiselect
#. Description
#: ../debhelper.in/locales.templates:1002
msgid ""
"Locales are a framework to switch between multiple languages and allow users "
"to use their language, country, characters, collation order, etc."
msgstr ""
"ロケールとは、複数の言語を切り替え、ユーザが自身の言語・国・文字・並べ替え順"
"序などを使えるようにするための仕組みです。"

#. Type: multiselect
#. Description
#: ../debhelper.in/locales.templates:1002
msgid ""
"Please choose which locales to generate. UTF-8 locales should be chosen by "
"default, particularly for new installations. Other character sets may be "
"useful for backwards compatibility with older systems and software."
msgstr ""
"生成したいロケールを選択してください。UTF-8 ロケールは、特に新規にインストー"
"ルしたものであれば、デフォルトで選択されているはずです。その他の文字セット"
"は、より古いシステムおよびソフトウェアとの後方互換性のために役立つでしょう。"

#. Type: select
#. Choices
#: ../debhelper.in/locales.templates:2001
msgid "None"
msgstr "なし"

#. Type: select
#. Description
#: ../debhelper.in/locales.templates:2002
msgid "Default locale for the system environment:"
msgstr "システムの環境変数として設定するデフォルトロケール:"

#. Type: select
#. Description
#: ../debhelper.in/locales.templates:2002
msgid ""
"Many packages in Debian use locales to display text in the correct language "
"for the user. You can choose a default locale for the system from the "
"generated locales."
msgstr ""
"ユーザに合った言語でテキストを表示するため、Debian では多くのパッケージがロ"
"ケールを使用します。生成したロケールの中からシステムでのデフォルトロケールを"
"選択できます。"

#. Type: select
#. Description
#: ../debhelper.in/locales.templates:2002
msgid ""
"This will select the default language for the entire system. If this system "
"is a multi-user system where not all users are able to speak the default "
"language, they will experience difficulties."
msgstr ""
"これはシステム全体のデフォルトの言語を選ぶことになります。このシステムがマル"
"チユーザシステムで、すべてのユーザがデフォルトの言語を話すことができるという"
"わけではない場合は、そういった人々は困難を感じることになってしまいます。"

#. Type: boolean
#. Description
#: ../debhelper.in/libc.templates:1001
msgid "Do you want to upgrade glibc now?"
msgstr "glibc を今更新しますか?"

#. Type: boolean
#. Description
#: ../debhelper.in/libc.templates:1001
msgid ""
"Running services and programs that are using NSS need to be restarted, "
"otherwise they might not be able to do lookup or authentication any more. "
"The installation process is able to restart some services (such as ssh or "
"telnetd), but other programs cannot be restarted automatically. One such "
"program that needs manual stopping and restart after the glibc upgrade by "
"yourself is xdm - because automatic restart might disconnect your active X11 "
"sessions."
msgstr ""
"NSS を利用している実行中のサービスおよびプログラムは、再起動する必要がありま"
"す。さもないと、ルックアップおよび認証がもう利用できないことになります。イン"
"ストール手続きではいくつかのサービス (ssh や telnetd など) を再起動することが"
"できますが、その他のプログラムは自動では再起動されません。手動での停止および "
"glibc の更新のあとにあなた自身で再起動する必要のあるそのようなプログラムの 1 "
"つとしては、xdm があります。というのも、自動再起動はあなたのアクティブな X11 "
"のセッションを閉じてしまうことになるからです。"

#. Type: boolean
#. Description
#: ../debhelper.in/libc.templates:1001
msgid ""
"This script detected the following installed services which must be stopped "
"before the upgrade: ${services}"
msgstr ""
"スクリプトは、更新前に停止されなければならない以下のサービスがインストールさ"
"れているのを検出しました: ${services}"

#. T

Bug#815857: watchdog: [INTL:ja] Japanese debconf templates translation update

[Takuma Yamada]

Package: watchdog
Severity: wishlist
Tags: l10n patch

Here's Japanese po-debconf templates translation (ja.po) file that 
reviewed by several Japanese Debian developers and users.

Please copy the attachment into debian/po/ja.po.

Kind regards.
--
Takuma Yamada

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


-- 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/2 CPU cores)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
# Japanese debconf templates translation for watchdog.
# Copyright (C) 2007-2009 Michael Meskes 
# This file is distributed under the same license as the watchdog package.
# Noritada Kobayashi , 2007.
# Hideki Yamane (Debian-JP) , 2009.
# 
# Takuma Yamada , 2016.
#
msgid ""
msgstr ""
"Project-Id-Version: watchdog 5.4-10\n"
"Report-Msgid-Bugs-To: watch...@packages.debian.org\n"
"POT-Creation-Date: 2014-11-10 03:23+0100\n"
"PO-Revision-Date: 2016-02-25 13:03+0900\n"
"Last-Translator: Takuma Yamada \n"
"Language-Team: Japanese \n"
"Language: ja\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=1; plural=0;\n"
"X-Generator: Gtranslator 2.91.6\n"

#. Type: boolean
#. Description
#: ../templates:2001
msgid "Start watchdog at boot time?"
msgstr "システム起動時に watchdog を開始しますか?"

#. Type: boolean
#. Description
#: ../templates:2001
msgid ""
"Please specify whether watchdog should be started as part of the boot "
"process. This can be changed later by editing /etc/default/watchdog."
msgstr ""
"起動プロセスの一部として watchdog を起動させるかどうか指定してください。この"
"指定は、/etc/default/watchdog を編集して後から変更することも可能です。"

#. Type: boolean
#. Description
#: ../templates:3001
msgid "Start wd_keepalive after stopping watchdog?"
msgstr "watchdog が終了した後に wd_keepalive を開始しますか?"

#. Type: boolean
#. Description
#: ../templates:3001
msgid ""
"Please specify whether stopping watchdog should start wd_keepalive to keep "
"on triggering the watchdog device. This can be changed later by editing /etc/"
"default/watchdog."
msgstr ""
"ウォッチドッグが終了するとき、ウォッチドッグデバイスのトリガーを保つために"
"wd_keepalive を開始するかどうかを指定してください。この指定は、/etc/default/"
"watchdog を編集して後から変更することも可能です。"

#. Type: boolean
#. Description
#: ../templates:4001
msgid "Restart watchdog on upgrades?"
msgstr "アップグレード時に watchdog を再起動しますか?"

#. Type: boolean
#. Description
#: ../templates:4001
msgid ""
"If the kernel is configured with the CONFIG_WATCHDOG_NOWAYOUT option (which "
"is not the default setting), restarting watchdog will cause a spurious "
"reboot (the kernel will assume that the watchdog daemon crashed)."
msgstr ""
"カーネルが CONFIG_WATCHDOG_NOWAYOUT オプションを有効にして設定されている場合 "
"(デフォルトでは設定されていません)、watchdog を再起動するとシステムが誤って再"
"起動してしまいます (watchdog デーモンがクラッシュしたとカーネルが考えるためで"
"す)。"

#. Type: string
#. Description
#: ../templates:5001
msgid "Watchdog module to preload:"
msgstr "先にロードしておく watchdog モジュール:"

#. Type: string
#. Description
#: ../templates:5001
msgid ""
"Please choose which watchdog module should be preloaded before starting "
"watchdog. The 'softdog' module should be suited for all installations. Enter "
"'none' if you don't want the script to load a module."
msgstr ""
"どの watchdog モジュールを watchdog の起動前に先にロードしておく必要があるか"
"を選択してください。「softdog」モジュールはどのようなインストール状況でも問題"
"はありません。モジュールをロードするスクリプトが必要で無い場合は「none」と入"
"力してください。"

Bug#815753: fwupdmgr: thinks my internal camera is external

[Paul Wise]

On Wed, 2016-02-24 at 21:37 -0600, Mario Limonciello wrote:

> Unfortunately this is not indicative of an internally located device. 
> 
> The USB video spec [1] indicates iFunction is only an index to a string
> descriptor.
...
> Upstream is not going to track a full list of strings just to indicate a
> device is internally wired or externally wired via the USB bus, and I
> won't carry a patch doing that in Debian either.

Thanks for the info.

I wonder if the solution is to use a phrase other than "Internal" that
actually indicates what this field is used for. You mentioned "the
Internal flag is only used to relax authentication checks on removable
devices" but I'm not clear on what exactly this means. Does it mean
that "Internal: True" devices need root/sudo access to update and
"Internal: False" any be updated by any locally present user?

-- 
bye,
pabs

https://wiki.debian.org/PaulWise




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

Bug#814928: [Pkg-samba-maint] Bug#814928: updated patch

[Jelmer Vernooij]

Thanks for the patch; I've committed it to git, will upload later. Two
small further comments:

On Fri, Feb 19, 2016 at 11:03:05AM +0100, Matthias Klose wrote:
> updated patch, the .install files need the x bit set.

>   * Build python3 packages.
>   * Bump debhelper and standards version.
>   * Do not generate symbols for the extension module
Was there a specific reason you removed this? The extension module
should only export the init function anyway (so it'll never change),
Verifying that that is the only function exported doesn't seem bad
either, though it's also not super useful.

>   * Do not encode the SOABI and the multiarch string into the pytalloc-util
> library, just append a '-py3'.
>   * Make the build log a bit more verbose.
Making waf more verbose can be done by setting the "V" environment
variable; I've committed a change to simplify this.

Cheers,

Jelmer

> 
> diff -Nru talloc-2.1.5/debian/compat talloc-2.1.5/debian/compat
> --- talloc-2.1.5/debian/compat2015-11-07 15:36:10.0 +
> +++ talloc-2.1.5/debian/compat2016-02-16 14:10:26.0 +
> @@ -1 +1 @@
> -8
> +9
> diff -Nru talloc-2.1.5/debian/control talloc-2.1.5/debian/control
> --- talloc-2.1.5/debian/control   2015-11-08 21:08:04.0 +
> +++ talloc-2.1.5/debian/control   2016-02-18 14:59:18.0 +
> @@ -4,7 +4,13 @@
>  Maintainer: Debian Samba Maintainers 
> 
>  Uploaders: Jelmer Vernooij , Christian Perrier 
> 
>  Homepage: http://talloc.samba.org/
> -Build-Depends: debhelper (>= 8.1.3), docbook-xml, docbook-xsl, xsltproc, 
> libpopt-dev, python-all (>= 2.6.6-3), python-all-dev (>= 2.6.6-3)
> +Build-Depends: debhelper (>= 9),
> +  docbook-xml, docbook-xsl, xsltproc,
> +  dh-exec,
> +  dh-python,
> +  libpopt-dev,
> +  python-dev (>= 2.6.6-3),
> +  python3-dev,
>  Standards-Version: 3.9.6
>  Vcs-Git: git://anonscm.debian.org/pkg-samba/talloc.git -b unstable
>  XS-Testsuite: autopkgtest
> @@ -77,3 +83,38 @@
>   reference counting to determine when memory should be freed.
>   .
>   This package contains the development files for the Python bindings.
> +
> +Package: python3-talloc
> +Pre-Depends: ${misc:Pre-Depends}
> +Architecture: any
> +Section: python
> +Provides: ${python3:Provides}
> +Depends: ${shlibs:Depends}, ${misc:Depends}, ${python3:Depends}
> +Description: hierarchical pool based memory allocator - Python3 bindings
> + A hierarchical pool based memory allocator with destructors. It uses
> + reference counting to determine when memory should be freed.
> + .
> + This package contains the Python3 bindings.
> +
> +Package: python3-talloc-dbg
> +Architecture: any
> +Pre-Depends: ${misc:Pre-Depends}
> +Section: debug
> +Depends: ${shlibs:Depends}, ${misc:Depends}, ${python3:Depends}, 
> python3-talloc (= ${binary:Version})
> +Recommends: python3-dbg, libtalloc2-dbg
> +Priority: extra
> +Description: hierarchical pool based memory allocator - Python3 debug 
> extension
> + A hierarchical pool based memory allocator with destructors. It uses
> + reference counting to determine when memory should be freed.
> + .
> + This package contains the Python3 debug extension.
> +
> +Package: python3-talloc-dev
> +Architecture: any
> +Section: libdevel
> +Depends: python3-talloc (= ${binary:Version}), ${misc:Depends}, pkg-config
> +Description: talloc Python3 bindings - development files
> + A hierarchical pool based memory allocator with destructors. It uses
> + reference counting to determine when memory should be freed.
> + .
> + This package contains the development files for the Python3 bindings.
> diff -Nru talloc-2.1.5/debian/patches/pass-waf-flags.diff 
> talloc-2.1.5/debian/patches/pass-waf-flags.diff
> --- talloc-2.1.5/debian/patches/pass-waf-flags.diff   1970-01-01 
> 00:00:00.0 +
> +++ talloc-2.1.5/debian/patches/pass-waf-flags.diff   2016-02-16 
> 16:17:56.0 +
> @@ -0,0 +1,17 @@
> +# Allow to pass flags to waf
> +
> +--- talloc-2.1.5.orig/Makefile
>  talloc-2.1.5/Makefile
> +@@ -3,10 +3,10 @@
> + WAF=WAF_MAKE=1 PATH=buildtools/bin:../../buildtools/bin:$$PATH waf
> + 
> + all:
> +-$(WAF) build
> ++$(WAF) build $(WAFFLAGS)
> + 
> + install:
> +-$(WAF) install
> ++$(WAF) install $(WAFFLAGS)
> + 
> + uninstall:
> + $(WAF) uninstall
> diff -Nru talloc-2.1.5/debian/patches/pytalloc-util-name.diff 
> talloc-2.1.5/debian/patches/pytalloc-util-name.diff
> --- talloc-2.1.5/debian/patches/pytalloc-util-name.diff   1970-01-01 
> 00:00:00.0 +
> +++ talloc-2.1.5/debian/patches/pytalloc-util-name.diff   2016-02-18 
> 14:55:52.0 +
> @@ -0,0 +1,21 @@
> +# Don't encode the multiarch name into the pytalloc-util library name
> +
> +Index: b/buildtools/wafsamba/samba_python.py
> +===
> +--- a/buildtools/wafsamba/samba_python.py
>  b/buildtools/wafsamba/samba_python.py
> +@@ -122,7 +122,13 @@ Build.BuildContext.SAMBA_PYTHON = SAMBA_
> + 
> + 
>

Bug#815856: ITP: apertium-fra -- Apertium single language data for French

[Kartik Mistry]

Package: wnpp
Severity: wishlist
Owner: Kartik Mistry 

* Package name: apertium-fra
  Version : 1.0.0~r65786
  Upstream Author : Francis M. Tyers ,
Kevin Brubeck Unhammer ,
sabertooth-...@users.sourceforge.net
* URL : http://apertium.org/
* License : GPL-3+
  Programming Lang:
  Description : Apertium single language data for French

Data package providing Apertium language resources for French

 - why is this package useful/relevant? is it a dependency for
   another package? do you use it? if there are other packages
   providing similar functionality, how does it compare?

 A: Dependency for new apertium-fra-cat (formerly apertium-fr-ca)

 - how do you plan to maintain it? inside a packaging team
   (check list at https://wiki.debian.org/Teams)? are you
   looking for co-maintainers? do you need a sponsor?

 A: Under debian-science.

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


signature.asc
Description: PGP signature

Bug#815854: xsp: [INTL:ja] Japanese debconf templates translation update

[Takuma Yamada]

Source: xsp
Severity: wishlist
Tags: l10n patch

Dear Maintainer,

Here's Japanese po-debconf templates translation (ja.po) file that 
reviewed by several Japanese Debian developers and users.

Please copy the attachment into debian/po/ja.po.

Kind regards.
--
Takuma Yamada

-- 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/2 CPU cores)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
# Copyright (C) 2009 Debian Mono Group 
# This file is distributed under the same license as xsp package.
# Hideki Yamane , 2009-2011.
# Takuma Yamada , 2016.
#
msgid ""
msgstr ""
"Project-Id-Version: xsp 2.10-1\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2015-12-12 14:32+\n"
"PO-Revision-Date: 2016-02-25 12:23+0900\n"
"Last-Translator: Takuma Yamada \n"
"Language-Team: Japanese \n"
"Language: ja\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=1; plural=0;\n"
"X-Generator: Gtranslator 2.91.6\n"

#. Type: boolean
#. Description
#: ../mono-apache-server4.templates:1001
msgid "Let mono-apache-server4 restart Apache?"
msgstr "mono-apache-server4 に Apache を再起動させますか?"

#. Type: boolean
#. Description
#: ../mono-apache-server4.templates:1001
msgid ""
"The Debian version of mono-apache-server4 includes a mono-server4-update "
"script that creates a configuration file for Apache to start the ASP.NET "
"applications, and mono-server4-update can restart Apache if there's a new "
"configuration file (/etc/mono-server4/mono-server-hosts.conf). If this is "
"true, then Apache will be restarted when there is a new mono-server4-hosts."
"conf file."
msgstr ""
"Debian 版の mono-apache-server4 は、Apache で ASP.NET アプリケーションを起動"
"させるための設定ファイルを作成する mono-server4-update スクリプトを含んでお"
"り、新しい設定ファイル (/etc/mono-server4/mono-server-hosts.conf) がある場合"
"には mono-server4-update は Apache を再起動できます。これを有効にすると、新し"
"い mono-server4-hosts.conf ファイルがある場合に Apache が再起動されます。"

#. Type: note
#. Description
#: ../mono-apache-server4.templates:2001 ../mono-xsp4.templates:4001
msgid "ASP.NET 1.0 support removed"
msgstr "ASP.NET 1.0 のサポートが削除されました"

#. Type: note
#. Description
#: ../mono-apache-server4.templates:2001
msgid ""
"You appear to have some ASP.NET 1.0 sites configured in /etc/mono-server. "
"Support for the 1.0 profile has been removed from Mono 2.8 and above, and "
"you are no longer able to serve ASP.NET 1.0 sites. You must reconfigure XSP "
"to serve these sites using the 4.0 profile, assuming your application is "
"compatible. Please see mono-server4-admin(8) to see how to regenerate a "
"configuration for use with the 4.0 profile."
msgstr ""
"/etc/mono-server に ASP.NET 1.0 のサイトが設定されているようです。1.0 のプロ"
"ファイルへのサポートは Mono 2.8 以上で削除されているので、ASP.NET 1.0 のサイ"
"トを提供することはもうできなくなります。アプリケーションに互換性がある場合に"
"は、XSP を再設定してサイトが 4.0 のプロファイルを使うようにする必要がありま"
"す。4.0 のプロファイルで利用するように設定を再生成する方法は、mono-server4-"
"admin(8) を参照してください。"

#. Type: note
#. Description
#: ../mono-apache-server4.templates:3001 ../mono-xsp4.templates:5001
msgid "ASP.NET 2.0 support removed"
msgstr "ASP.NET 2.0 のサポートが削除されました"

#. Type: note
#. Description
#: ../mono-apache-server4.templates:3001
msgid ""
"You appear to have some ASP.NET 2.0 sites configured in /etc/mono-server. "
"Support for the 1.0 profile has been removed from Mono 4.0 and above, and "
"you are no longer able to serve ASP.NET 2.0 sites. You must reconfigure XSP "
"to serve these sites using the 4.0 profile, assuming your application is "
"compatible. Please see mono-server4-admin(8) to see how to regenerate a "
"configuration for use with the 4.0 profile."
msgstr ""
"/etc/mono-server に ASP.NET 2.0 のサイトが設定されているようです。1.0 のプロ"
"ファイルへのサポートは Mono 4.0 以上で削除されているので、ASP.NET 2.0 のサイ"
"トを提供することはもうできなくなります。アプリケーションに互換性がある場合に"
"は、XSP を再設定してサイトが 4.0 のプロファイルを使うようにする必要がありま"
"す。4.0 のプロファイルで利用するように設定を再生成する方法は、mono-server4-"
"admin(8) を参照してください。"

#. Type: boolean
#. Description
#: ../mono-xsp4.templates:1001
msgid "Start on boot?"
msgstr "起動時に開始しますか?"

#. Type: boolean
#. Description
#: ../mono-xsp4.templates:1001
msgid ""
"If this is true, then XSP4 will automatically start when the computer is "
"turned on."
msgstr ""
"これを有効にすると、XSP4 はコンピュータの電源が入れられた際に自動的に起動しま"
"す。"

#. Type: string
#. Description
#: ../mono-xsp4.templates:2001
msgid "Bind to address:"
msgstr "バインドするアドレス:"

#. Type: string
#. Description
#: ../mono-xsp4.templates:2001
msgid ""
"To function properly, XSP4 needs to be bound to an IP address. The default "
"(\"0.0.0.0\") binds to all addresses of the server, but a specific port can "
"be selected. To use XSP4 only locally, use \"127.0.0.1\" for the address."
msgstr ""
"正しく動作させるには、XSP4 は IP アドレスにバインドする必要があります。デフォ"
"ルト値 (\"0.0.0.0\") ではサーバの全てのアドレスにバインドしますが、特定のポー"
"トを選ぶこともできます。XSP4 をローカルだけで使うには、アドレスに "
"\"127.0.0.1\" を使います。"

#. Type: stri

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#815855: ITP: apertium-cat -- Apertium single language data for Catalan

[Kartik Mistry]

Package: wnpp
Severity: wishlist
Owner: Kartik Mistry 

* Package name: apertium-cat
  Version : 1.0.0~r65787
  Upstream Author : Francis M. Tyers ,
Kevin Brubeck Unhammer ,
Juan Pablo Martínez Cortés ,
Xavivars 
* URL : http://apertium.org/
* License : GPL-3+
  Programming Lang:
  Description : Apertium single language data for Catalan

Data package providing Apertium language resources for Catalan

 - why is this package useful/relevant? is it a dependency for
   another package? do you use it? if there are other packages
   providing similar functionality, how does it compare?

 A: Dependency for new apertium-fra-cat (formerly apertium-fr-ca)

 - how do you plan to maintain it? inside a packaging team
   (check list at https://wiki.debian.org/Teams)? are you
   looking for co-maintainers? do you need a sponsor?

 A: Under debian-science.

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


signature.asc
Description: PGP signature

Bug#815753: fwupdmgr: thinks my internal camera is external

[Mario Limonciello]

On 02/24/2016 07:55 PM, Paul Wise wrote:
> On Wed, 2016-02-24 at 16:41 -0600, Mario Limonciello wrote:
>
>> Although technically this is an internal device, I don't believe that
>> any of those USB attributes can identify this information about the
>> physical location of the bus. Please correct me if I'm wrong.
> This info from the lsusb output would appear to indicate this:
>
>   iFunction   4 Integrated Camera
>
Unfortunately this is not indicative of an internally located device. 

The USB video spec [1] indicates iFunction is only an index to a string
descriptor.

This is the relevant snippet from the spec:

Index of a string descriptor that describes this interface. This must be
used for the device (function) name and be implemented in US English
(LANGID = 0x0409) at the minimum.

Analysing a string to guess if a device is internal is not a reliable
method.  What if I had a USB device that filled in that string
descriptor with "Wireless keyboard with integrated touchpad"?  Looking
for the word integrated is obviously going to falsely trigger this
item.  Looking for the full phrase integrated camera will match the
source of the camera in your machine, but that's all that is guaranteed. 

Upstream is not going to track a full list of strings just to indicate a
device is internally wired or externally wired via the USB bus, and I
won't carry a patch doing that in Debian either.

[1]
http://www.usb.org/developers/docs/devclass_docs/USB_Video_Class_1_1_090711.zip

Bug#815852: apache2: Obsolete IE configuration cruft should be removed from default-ssl.conf

[Paul Fisher]

Package: apache2
Version: 2.4.12-2ubuntu2
Severity: normal

The default-ssl.conf configuration for apache2 contains these lines:

> BrowserMatch "MSIE [2-6]" \
>   nokeepalive ssl-unclean-shutdown \
>   downgrade-1.0 force-response-1.0
> BrowserMatch "MSIE [17-9]" ssl-unclean-shutdown

They don't serve any purpose and should be removed.


For IE 2-6:

Upstream uses 

> BrowserMatch "MSIE [2-5]" \
>   nokeepalive ssl-unclean-shutdown \
>   downgrade-1.0 force-response-1.0

in httpd-ssl.conf.in, which excludes IE6.

IE5 and below are rare enough that seems not worth including them
in the default configuration for a new secure web server today.
(I would argue the same is true for IE6.)


For IE 7 and up:

I used an IE7 VM from https://modern.ie/ to connect to a vhost
which didn't enable ssl-unclean-shutdown. 
IE7 had no problem with standard connection closes, and nothing
appeared in a debug-level SSL log.

This directive does not appear to be necessary for any more modern
versions of IE.


-- Package-specific info:

-- System Information:
Debian Release: jessie/sid
  APT prefers wily-updates
  APT policy: (500, 'wily-updates'), (500, 'wily-security'), (500, 'wily')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages apache2 depends on:
ii  apache2-bin2.4.12-2ubuntu2
ii  apache2-data   2.4.12-2ubuntu2
ii  apache2-utils  2.4.12-2ubuntu2
ii  dpkg   1.18.2ubuntu5.1
ii  lsb-base   4.1+Debian11ubuntu8
ii  mime-support   3.58ubuntu1
ii  perl   5.20.2-6ubuntu0.1
ii  procps 1:3.3.9-1ubuntu8

Versions of packages apache2 recommends:
ii  ssl-cert  1.0.37

Versions of packages apache2 suggests:
pn  apache2-doc  
pn  apache2-suexec-pristine | apache2-suexec-custom  
ii  ufw  0.34-2
pn  www-browser  

Versions of packages apache2-bin depends on:
ii  libapr1  1.5.2-3
ii  libaprutil1  1.5.4-1
ii  libaprutil1-dbd-sqlite3  1.5.4-1
ii  libaprutil1-ldap 1.5.4-1
ii  libc62.21-0ubuntu4.1
ii  libldap-2.4-22.4.41+dfsg-1ubuntu2
ii  liblua5.1-0  5.1.5-8
ii  libpcre3 2:8.35-7.1ubuntu1
ii  libssl1.0.0  1.0.2d-0ubuntu1.3
ii  libxml2  2.9.2+zdfsg1-4ubuntu0.3
ii  perl 5.20.2-6ubuntu0.1
ii  zlib1g   1:1.2.8.dfsg-2ubuntu4

Versions of packages apache2-bin suggests:
pn  apache2-doc  
pn  apache2-suexec-pristine | apache2-suexec-custom  
pn  www-browser  

Versions of packages apache2 is related to:
ii  apache2  2.4.12-2ubuntu2
ii  apache2-bin  2.4.12-2ubuntu2

-- Configuration Files:
/etc/apache2/apache2.conf changed [not included]
/etc/apache2/conf-available/charset.conf changed [not included]
/etc/apache2/conf-available/security.conf changed [not included]

-- no debconf information

Bug#815851: much freshier version is finally provided by upstram (0.8.14)

[Yaroslav Halchenko]

Package: python-httpretty
Version: 0.8.6-2
Severity: wishlist

There is now finally 0.8.14 which carries many bugfixes, in particular
for python3 compatibility.  Since build-time testing errors are ignored
ATM I can only speculate that 0.8.6 has a few outstanding ones new release
should have addressed.

Please let me know if you need a hand updating this package

Cheers,

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

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

Versions of packages python-httpretty depends on:
ii  python-urllib3  1.12-1
pn  python:any  

python-httpretty recommends no packages.

python-httpretty suggests no packages.

-- no debconf information

Bug#782243: Failed to get unit file state for snmpd.service: No such file or directory

[Sam Tannous]

I've been using this simple snmpd.service file (placed in
/lib/systemd/system/snmpd.service):

###
[Unit]
Description=Simple Network Management Protocol (SNMP) Daemon.
After=networking.service syslog.service

[Service]
EnvironmentFile=-/etc/default/snmpd
Type=simple
# Restart can be no (the default), on-success, on-failure, on-abnormal,
on-watchdog,
# on-abort, or always
#Restart=no
# Here, we start snmpd with -f to prevent from forking for better systemd
control
ExecStart=/usr/sbin/snmpd $SNMPDOPTS -f
ExecReload=/bin/kill -HUP $MAINPID

[Install]
WantedBy=multi-user.target


0. After saving the snmpd.service file in the right place, do a systemctl
daemon-reload.
1. Remove "export" from /etc/default/snmpd since this causes a warning.
2. Move /etc/init.d/snmpd to someplace else (e.g. snmpd.orig) or you'll get
some
warnings about 'insserv'.   Best not to mix init.d with systemd.
3. Comment out "defaultMonitors" and "linkUpDownNotifications" or you'll
see some warnings about
unknown tokens.


And I think that's all.

I've been trying to get this patch correct for the maintainers but I can't
figure out how
to get the snmpd.service file into the deb package.


On Wed, 3 Feb 2016 17:20:52 +0100 Tom Laermans 
wrote:
> Hi,
>
> Any updates here? We're also running into this, using Puppet. snmpd will
> never be restarted as it thinks it's not currently running.
>
> Tom
>
>

-- 
*Sam Tannous*

Bug#787663: aptitude forgets/clears manually set auto-installed-flags in several situations

[Christoph Anton Mitterer]

Control: reopen -1

Hey.

I just tried that with:
# aptitude --version
aptitude 0.7.6
Compiler: g++ 5.3.1 20160220
Compiled against:
  apt version 5.0.0
  NCurses version 6.0
  libsigc++ version: 2.6.2
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 6.0.20160213
  cwidget version: 0.5.17
  Apt version: 5.0.0

... and it still seems to happen.

I.e. I've upgraded kerberos, of which I've had e.g. krb5-k5tls marked
auto, though nothing depended/recommended/etc. it.

I've aborted at apt-listchanges, and then the auto flag was cleared.


Cheers,
Chris.

smime.p7s
Description: S/MIME cryptographic signature

Bug#814755: luatex font bug: "checksum mismatch" warnings on 64bit system

[Igor Liferenko]

Hi all,

I reported this bug to Debian some days ago, but did not get a
response, so I'm writing here. Keep the CC please.

luatex gives "checksum mismatch" warnings:

This is LuaTeX, Version beta-0.80.0 (TeX Live 2015/Debian) (rev 5238)
checksum mismatch in local font cmb10 (-770990554 != -770990554)
in virtual font
 myfont.vf ignored.
No pages of output.
Transcript written on texput.log.

Run the following commands in a clean directory to create OFM/OVF font
and load it in luatex:

echo "(MAPFONT D 0 (FONTNAME cmb10))" > myfont.vpl
tftopl cmb10 >> myfont.vpl
vptovf myfont.vpl
rm myfont.vpl
vftovp -charcode-format=octal myfont.vf > myfont.ovp
rm myfont.tfm myfont.vf
ovp2ovf myfont.ovp
luatex '\font\f=myfont\end'


On i386 system the same versions of texlive packages do not give such warnings.

If we change cmb10 to, e.g., cmr10, no warning is printed.
The problem is that for fonts with values of FONTCHECKSUM above octal
177, the value is interpreted as negative.

Octal 177 is binary 0111
Octal 200 is binary 1000
This is possibly some issue with types of variables on 32bit vs 64bit systems.

Also, "man ofm2opl" says about "-charcode-format" option, which does not exist:
$ ofm2opl -charcode-format=ascii myfont
ofm2opl: unrecognized option '-charcode-format=ascii'
Try `ofm2opl --help' for more information.

Best regards,
Igor

Bug#815850: missing symbolic link /boot/vmlinux

[Heinrich Schuchardt]

Package: linux-image-armmp
Version: 3.16.0-4
Severity: normal

When first removing the current kernel and then installing a new kernel
a symbolic link /boot/vmlinux is created.

sudo apt-get remove linux-image-3.16.0-4-armmp
sudo apt-get install linux-image-armmp-lpae

When first installing an additional kernel and then removing the current
kernel the symbolic link /boot/vmlinux is removed instead of replacing it.

sudo apt-get install linux-image-armmp-lpae
sudo apt-get remove linux-image-3.16.0-4-armmp

My expectation is that irrespective of the sequence of operations the
symbolic link /boot/vmlinux should be created for the current kernel.

Same for /boot/initrd.img.

The problem occurs in
linux-image-3.16.0-4-armmp.postrm

Best regards

Heinrich Schuchardt


0 aktualisiert, 0 neu installiert, 2 zu entfernen und 0 nicht aktualisiert.
Nach dieser Operation werden 102 MB Plattenplatz freigegeben.
Möchten Sie fortfahren? [J/n] j
(Lese Datenbank ... 177337 Dateien und Verzeichnisse sind derzeit
installiert.)
Entfernen von linux-image-armmp (3.16+63) ...
Entfernen von linux-image-3.16.0-4-armmp (3.16.7-ckt20-1+deb8u3) ...
Ok, proceeding with removing running kernel image.
/etc/kernel/postrm.d/initramfs-tools:
update-initramfs: Deleting /boot/initrd.img-3.16.0-4-armmp
/etc/kernel/postrm.d/zz-flash-kernel:
DTB: sun7i-a20-bananapi.dtb
flash-kernel: Kernel 3.16.0-4-armmp has been removed.
flash-kernel: A higher version (3.16.0-4-armmp-lpae) is still installed,
no reflashing required.
The link /boot/vmlinuz is a damaged link
Removing symbolic link vmlinuz
You may need to re-run your boot loader
The link /boot/initrd.img is a damaged link
Removing symbolic link initrd.img
You may need to re-run your boot loader

Bug#815849: ITP: tpm2-tools -- TPM (Trusted Platform Module) 2.0 tools

[Mathieu Trudel-Lapierre]

Package: wnpp
Severity: wishlist
Owner: "Mathieu Trudel-Lapierre" 

* Package name: tpm2-tools
  Version : 1.0
  Upstream Author : Gang Wei 
* URL : https://github.com/01org/tpm2.0-tools
* License : BSD
  Programming Lang: C, C++
  Description : TPM (Trusted Platform Module) 2.0 tools

This package includes tools to use for interacting with TPM chips for
various purposes, such as for attestation, key management, encryption
or signing.

Since there seems to be a growing number of TPM-related packages in
Debian it may be useful to combine efforts in a team.

Bug#815847: Fdisk Shows 'Reversed' Head/Sector Data Fields via ExpertMode;Print

[groups, freeman]

Package: util-linux
Version: 2.25.2-6
Severity: normal

I have an 8GB USB flash drive containing the attached Master Boot Record 
(MBR).


On this freshly-setup Debian 8.3 system I manually constructed the 
partition layout and believe it to have the following attributes:

Partition #4 in MBR
~7900Cylinders
   64Heads, or Tracks
   32Sectors

having created the partition layout using fdisk (possibly an older 
version tho).


(The fob's actual use is as a full Deb server, with sda1 being an 
extended partition containing 2 logical ext3 partitions and it boots up 
and runs all fine - the attached MBR that lacks sda1 is a 'simplest 
case' example of the problem.)


So now when I examine the attached MBR in fdisk via the cmds:
{ printf "u \n x \n p \n r \n q \n" | fdisk Sample64h32sMBR.mbr; } 
| grep -E "^(Geometry|Device|Sample64h)"


the 3 lines output are:
Geometry: 64 heads, 32 sectors/track, 0 cylinders
Device   Boot Start   End Cylinders Id Type Start-C/H/S 
End-C/H/S Attrs
Sample64h32sMBR.mbr4 *1   412   412  6 FAT16 1/1/0 
411/32/6380


The first and second lines are as expected, however the 3rd line SHOULD 
have the End geometry as:

411/63/32
instead of the indicated:
411/32/63

(The problem also manifests when I don't invoke the 'u'nits command - I 
only invoked the 'u' command to cause fdisk to output the "Geometry" 
line, making the problem readily illustrated.)


Of note: I believe the problem also affects the Start-geometry 
fields as well.


I'd plead that the problem be corrected by way of reversing the 
fields of numerals that are output as the Hd & Sec fields, and not by 
way of simply reversing the columnar headers, since Cyl/Sec/Hd display 
would be both a minor mind bend to do calculations and verifications of 
data upon, and also in conflict with what it seems to be the widespread 
convention of ordering the fields in a 
MostSignificant-to-LeastSignificant, Left-to-Right arrangement. (At 
least for English-speakers :)


In any case thanks for considering the bug, and your work on open 
source code!




Below, the 'reportbug' output:
-- System Information:
Debian Release: 8.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 3.16.0-4-586
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages util-linux depends on:
ii  initscripts2.88dsf-59
ii  libblkid1  2.25.2-6
ii  libc6  2.19-18+deb8u3
ii  libmount1  2.25.2-6
ii  libncurses55.9+20140913-1+b1
ii  libpam0g   1.1.8-3.1+deb8u1
ii  libselinux12.3-2
ii  libslang2  2.3.0-2
ii  libsmartcols1  2.25.2-6
ii  libtinfo5  5.9+20140913-1+b1
ii  libuuid1   2.25.2-6
ii  lsb-base   4.1+Debian13+nmu1
ii  tzdata 2015g-0+deb8u1
ii  zlib1g 1:1.2.8.dfsg-2+b1

util-linux recommends no packages.

Versions of packages util-linux suggests:
ii  dosfstools  3.0.27-1
ii  kbd 1.15.5-2
ii  util-linux-locales  2.25.2-6

-- no debconf information





Sample64h32sMBR.mbr
Description: Binary data

Bug#815846: ITP: tpm2-tss -- TPM (Trusted Platform Module) 2.0 Software Stack

[Mathieu Trudel-Lapierre]

Package: wnpp
Severity: wishlist
Owner: "Mathieu Trudel-Lapierre" 

* Package name: tpm2-tss
  Version : 0.9.8
  Upstream Author : Will Arthur 
* URL : https://github.com/01org/TPM2.0-TSS
* License : MIT/BSD
  Programming Lang: C, C++
  Description : TPM (Trusted Platform Module) 2.0 Software Stack

TPM2.0-TSS is a software stack comprising a few layers:
 - Feature API (FAPI)
 - Enhanced System API (ESAPI)
 - System API (SAPI)
 - TPM Command Transmission Interface (TCTI)
 - Trusted Access Broker/Resource Manager (TAB/RM)

These are used to interface with TPM chips to provide specific cryptographic
services to the system in a secure manner.

TPM2.0-TSS is a requirement (for tss2 and tcti) for tpm2-tools (TPM2.0-tools),
for which I will file another ITP.

It may be relevant here to merge efforts for maintaining TPM tools in a team,
there has been lots of work by pollux in maintaining the trousers stack for
which this project seeks to be an improvement / evolution.

Bug#815848: linux: [armhf] udeb: Include modules needed on BeagleBoard-X15

[Vagrant Cascadian]

Source: linux
Version: 4.4.2-3
Severity: normal
Tags: patch

The following modules are needed to support USB disk installs on
BeagleBoard-X15.

diff --git a/debian/installer/armhf/modules/armhf-armmp/usb-modules 
b/debian/installer/armhf/modules/armhf-armmp/usb-modules
index 7861c82..f82d68b 100644
--- a/debian/installer/armhf/modules/armhf-armmp/usb-modules
+++ b/debian/installer/armhf/modules/armhf-armmp/usb-modules
@@ -9,3 +9,6 @@ ehci-orion
 ehci-tegra
 ci_hdrc_imx
 dwc2
+dwc3
+omap-ocp2scp
+extcon-usb-gpio

Tested with the patch applied from #815476.

In theory, omap-ocp2scp (and maybe extcon-usb-gpio) is needed to support
eSATA as well, although at the moment sata support doesn't work on the
BeagleBoard-X15. So maybe there's a more appropriate place for some of
these modules... not sure where exactly.


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#770161: [e68e1da] Fix for Bug#770161 committed to git

[Manoj Srivastava]

tags 770161 + pending
thanks
Hi,

 The following change has been committed for this bug by
 Manoj Srivastava  on the branch 
 master at Wed, 24 Feb 2016 17:44:01 -0800.

 The fix will be in the next upload. 
=
[master]: Cleanup generated files based on changes to flex.skl.

 The variable yy_n_chars had been of type yy_size_t which is incorrect
 given its use in read(). While it might be adviseable to look at
 defining a yy_ssize_t, there might be some issues doing this and so, for
 now, at least, we'll punt back to int.

 Bug fix: "Type of yy_n_chars changed to yy_size_t by authors cause bug
 in YY_INPUT macro where result argument is tested if < 0; thanks to
 gcc's -Werror=type-limits", thanks to Michal Fita
 (Closes: #770161).

Signed-off-by: Manoj Srivastava 
=

Bug#793809: please build packages for python3

[Dato Simó]

> Please build packages for python3, using the upstream 1.1b1 release, maybe
> uploading to experimental only.

Please consider using at least 1.1rc4, to avoid running against this
issue with Python 3.5:

https://github.com/gevent/gevent/issues/653

Bug#815753: fwupdmgr: thinks my internal camera is external

[Paul Wise]

On Wed, 2016-02-24 at 16:41 -0600, Mario Limonciello wrote:

> Although technically this is an internal device, I don't believe that
> any of those USB attributes can identify this information about the
> physical location of the bus. Please correct me if I'm wrong.

This info from the lsusb output would appear to indicate this:

      iFunction   4 Integrated Camera

> Furthermore, this is a moot point since the Internal flag is only
> used to relax authentication checks on removable devices so this has
> no value other than cosmetic since you can't do anything to this
> device's firmware from fwupd.

I see, I guess that is why I chose minor severity.

FYI a couple of tips on using email around the Debian project:

Please use interleaved style posting instead of top posting:

https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

Please also trim your replies as I have done.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise




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

Bug#815036: transition: msgpack-c

[James McCoy]

On Mon, Feb 22, 2016 at 07:39:44PM +0100, Emilio Pozuelo Monfort wrote:
> Tracker at https://release.debian.org/transitions/html/msgpack-c.html

Thanks!

> On 21/02/16 16:54, James McCoy wrote:
> > On Wed, Feb 17, 2016 at 11:46:53PM -0500, James McCoy wrote:
> >> FTBFS:
> >>
> >> * webdis:
> >>   + #811343 filed with patch
> >> * tmate:
> >>   + New upstream version is needed
> >>   + Will file a bug for this
> > 
> > Filed #815381.
> > 
> >> * kumofs:
> >>   + configure script expects the C++ library (libmsgpack) and therefore
> >> fails
> >>   + Trivial patch to remove that expectation leads to a compile failure
> >> due to mixing code with C and C++ linkage
> >>   + No upstream activity in 5+ years
> >>   + Debian maintainer MIA
> > 
> > Given the above and a popcon of 5, should an RM bug be filed?
> 
> Yeah I'd say so.

#815845 filed.

Cheers,
-- 
James
GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy 

Bug#761250: [3207b11] Fix for Bug#761250 committed to git

[Manoj Srivastava]

tags 761250 + pending
thanks
Hi,

 The following change has been committed for this bug by
 Manoj Srivastava  on the branch 
 master at Wed, 24 Feb 2016 17:15:45 -0800.

 The fix will be in the next upload. 
=
Fixed size of buffer allocation

 The value of n_alloc was a count, not a size. Multiplying the value
 by the element size was incorrect. That multiplication was already
 being done and having it done twice was incorrect.

 Bug fix: "n_alloc has wrong value in buf_append function", thanks to
 Howard Gong (Closes: #761250).

Signed-off-by: Manoj Srivastava 
=

Bug#815845: RM: kumofs -- RoQA; Unmaintained both upstream and in Debian, RC buggy

[James McCoy]

Package: ftp.debian.org
Severity: normal

kumofs FTBFS with the new version of libmsgpack-dev, which is currently
in planning to be moved out of experimental (#815036).

There hasn't been upstream activity in 5+ years, and the last MU was 2.5
years ago, which was subsequently removed from testing.  The followup
NMU, to fix FTBFS, has also since been removed from testing.

While not definitive, popcon has also never been above 13.

Cheers,
James

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#498061: Some commands like "show" needn't lock /var/lib/dpkg/lock

[Manuel A. Fernandez Montecelo]

Control: tags -1 + pending


2013-01-06 18:54 Axel Beckert:

Control: severity -1 minor
Control: tag -1 + confirmed

Hi,

jida...@jidanni.org wrote:

Severity: wishlist

Some commands like "show" and "why", "why-not", needn't try to lock 
/var/lib/dpkg/lock
# aptitude show scim-gtk2-immodule
E: Could not get lock /var/lib/dpkg/lock - open (11 Resource temporarily 
unavailable)
E: Unable to lock the administration directory (/var/lib/dpkg/), is another 
process using it?


As the merged http://bugs.debian.org/650179 shows, this happens only
as root, so a workaround is to call this command as user instead.

Since I used the word "workaround", the issue only appears when
running the command as root but not as normal user, and since I felt
the urge to tag it as "confirmed", this is definitely more severe than
just "wishlist".

I'm hence raising the severity to "minor" (only, since there is a
workaround).


Fixed now, marking as + pending.


--
Manuel A. Fernandez Montecelo 

Bug#815843: ocserv: Segfault when loading ocserv

[Tony Zhou]

Package: ocserv
Version: 0.10.11-2
Severity: important

Dear Maintainer,

I have just upgraded my ocserv from 0.10.11-1 to 0.10.11-2 in order to
gain RADIUS support. However, when I try to start ocserv it throws a
segfault and exits, either by systemd or manually executing ocserv. When
ocserv loads as a service, the journal has the following output:

Feb 25 09:44:48 vpn ocserv[1065]: listening on 2 systemd sockets...
Feb 25 09:44:48 vpn ocserv[1065]: main: initialized ocserv 0.10.11
Feb 25 09:44:48 vpn ocserv[1066]: sec-mod: reading supplemental config from 
files
Feb 25 09:44:48 vpn ocserv[1066]: sec-mod: sec-mod initialized (socket: 
/var/run/ocserv-socket.1065)
Feb 25 09:44:48 vpn systemd[1]: ocserv.service: Main process exited, 
code=killed, status=6/ABRT
Feb 25 09:44:48 vpn ocserv[1065]: *** Error in `ocserv-main': free(): invalid 
pointer: 0xb78e9228 ***
Feb 25 09:44:48 vpn ocserv[1066]: sec-mod: error receiving msg head: No such 
file or directory
Feb 25 09:44:48 vpn ocserv[1066]: sec-mod: error processing sync command from 
main
Feb 25 09:44:48 vpn systemd[1]: ocserv.service: Unit entered failed state.
Feb 25 09:44:48 vpn systemd[1]: ocserv.service: Failed with result 'signal'.

and when executing ocserv directly:

tony@vpn:~$ sudo /usr/sbin/ocserv -f -c /etc/ocserv/ocserv.conf -d 10

Setting 'radius' as primary authentication method
Setting 'radius' as accounting method
listening (TCP) on server.ip.address:443...
listening (UDP) on server.ip.address:443...
ocserv[983]: sec-mod: reading supplemental config from files
ocserv[982]: main: initializing control unix socket: /var/run/occtl.socket
ocserv[982]: main: initialized ocserv 0.10.11
ocserv[983]: sec-mod: sec-mod initialized (socket: /var/run/ocserv-socket.982)
ocserv[982]: TLS[<3>]: ASSERT: common.c:1110
Segmentation fault
tony@vpn:~$ ocserv[983]: sec-mod: error receiving msg head: No such file or 
directory
ocserv[983]: sec-mod: error processing sync command from main

Not sure if it's just me or everybody.

Thanks,
TZ


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

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

Versions of packages ocserv depends on:
ii  dbus 1.10.6-1
ii  init-system-helpers  1.28
ii  libc62.21-9
ii  libgnutls30  3.4.9-2
ii  libgssapi-krb5-2 1.13.2+dfsg-4
ii  libhttp-parser2.12.1-2
ii  liblz4-1 0.0~r131-1
ii  libnl-3-200  3.2.27-1
ii  libnl-route-3-2003.2.27-1
ii  liboath0 2.6.1-1
ii  libopts251:5.18.7-3
ii  libpam0g 1.1.8-3.2
ii  libpcl1  1.6-1
ii  libprotobuf-c1   1.2.1-1
ii  libradcli4   1.2.4-2.1
ii  libreadline6 6.3-8+b4
ii  libseccomp2  2.2.3-3
ii  libsystemd0  228-6
ii  libtalloc2   2.1.5-1
ii  libtasn1-6   4.7-3
ii  libwrap0 7.6.q-25
ii  ssl-cert 1.0.37

Versions of packages ocserv recommends:
ii  ca-certificates  20160104

ocserv suggests no packages.

-- Configuration Files:
/etc/ocserv/ocserv.conf changed [not included]

-- no debconf information

Bug#815844: diffoscope won't build without python-magic from PyPi

[Leo Famulari]

Source: diffoscope

Dear Maintainer,

I am maintaining the diffoscope package in GNU Guix [0].

I recently updated from version 34 to 49, and found that I could not
build diffoscope from source without the python-magic package from PyPi
[1].

However, diffoscope's README [2] says that:

``Magic-file-extension`` can be used instead of
``python-magic``. It is built from `file
`_.
Available on Debian and Fedora as ``python3-magic``.

I removed the requirement of python-magic from setup.py and built
against the Python bindings distributed with `file`, as packaged in Guix
[3]. Diffoscope seems to work just fine this way.

I even confirmed, with strace, that diffoscope was using libmagic from
`file`.

Will you consider making python-magic an optional dependency of
diffoscope, so that downstream packagers don't have to package
python-magic from PyPi or work around this issue by patching setup.py?

[0]
https://www.gnu.org/software/guix/package-list.html#diffoscope

[1]
https://pypi.python.org/pypi/python-magic/

[2]
https://anonscm.debian.org/cgit/reproducible/diffoscope.git/tree/README.rst#n58

[3]
https://www.gnu.org/software/guix/package-list.html#python-file

Bug#815841: linux-headers-4.5.0-rc4-common: missing scripts/Makefile.ubsan causing dkms builds failures

[Luca Boccassi]

Package: linux-headers-4.5.0-rc4-common
Version: 4.5~rc4-1~exp1
Severity: normal

Dear Maintainer,

4.5-rc1 started shipping a new file, scripts/Makefile.ubsan [1]. This is 
included by scripts/Makefile,
which is shipped by debian's linux-headers-4.5.0-rc4-common package, but the 
same does not ship
Makefile.ubsan, which is causing DKMS build failures.

Please consider either shipping this new makefile too or patching away the 
include in scripts/Makefile.

Thank you!

Kind regards,
Luca Boccassi

[1] 
https://github.com/torvalds/linux/commit/c6d308534aef6c99904bf5862066360ae067abc4

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#678921: Info received (Bug#678921: Info received (STILL broken in 3.5-2+b2 in Jessie))

[Athanasius]

  Actually, use this patch instead.  It will also fire the first time it
sees a new title, even if the previous saved one was empty.  The
previous patch would need *two* changes of title before it would fire
the script, one to fill in the previous, and then another to be
different to that.

  I'd definitely push this upstream if possible.  I really don't know
why this has remained unfixed for so long, I guess no audacious dev
cared about this bit of code.

diff -ur audacious-plugins-3.5/src/song_change/song_change.c 
new-audacious-plugins-3.5/src/song_change/song_change.c
--- audacious-plugins-3.5/src/song_change/song_change.c 2014-04-23 
03:37:46.0 +0100
+++ new-audacious-plugins-3.5/src/song_change/song_change.c 2016-02-25 
00:18:01.691451152 +
@@ -32,7 +32,7 @@
 static void songchange_playback_begin(gpointer unused, gpointer unused2);
 static void songchange_playback_end(gpointer unused, gpointer unused2);
 static void songchange_playlist_eof(gpointer unused, gpointer unused2);
-//static void songchange_playback_ttc(gpointer, gpointer);
+static void songchange_playback_ttc(gpointer, gpointer);
 
 typedef struct
 {
@@ -252,7 +252,7 @@
 hook_dissociate("playback begin", songchange_playback_begin);
 hook_dissociate("playback end", songchange_playback_end);
 hook_dissociate("playlist end reached", songchange_playlist_eof);
-// hook_dissociate( "playlist set info" , songchange_playback_ttc);
+hook_dissociate("title change" , songchange_playback_ttc);
 
 if ( ttc_prevs != NULL )
 {
@@ -320,7 +320,7 @@
 ttc_prevs = g_malloc0(sizeof(songchange_playback_ttc_prevs_t));
 ttc_prevs->title = NULL;
 ttc_prevs->filename = NULL;
-// hook_associate( "playlist set info" , songchange_playback_ttc , 
ttc_prevs );
+hook_associate("title change" , songchange_playback_ttc , ttc_prevs );
 
 return TRUE;
 }
@@ -335,53 +335,58 @@
 do_command (cmd_line_after);
 }
 
-#if 0
 static void
 songchange_playback_ttc(gpointer plentry_gp, gpointer prevs_gp)
 {
-if ( ( aud_ip_state->playing ) && ( strcmp(cmd_line_ttc,"") ) )
+if ( aud_drct_get_playing() && ( strcmp(cmd_line_ttc,"") ) )
 {
 songchange_playback_ttc_prevs_t *prevs = prevs_gp;
-PlaylistEntry *pl_entry = plentry_gp;
+   int playlist = aud_playlist_get_playing ();
+   int pl_entry = aud_playlist_get_position(playlist);
+   gchar *pl_entry_filename = aud_playlist_entry_get_filename(playlist, 
pl_entry);
+   gchar *pl_entry_title = aud_playlist_entry_get_title(playlist, 
pl_entry, FALSE);
 
 /* same filename but title changed, useful to detect http stream song 
changes */
 
 if ( ( prevs->title != NULL ) && ( prevs->filename != NULL ) )
 {
-if ( ( pl_entry->filename != NULL ) && ( 
!strcmp(pl_entry->filename,prevs->filename) ) )
+if ( ( pl_entry_filename != NULL ) && ( 
!strcmp(pl_entry_filename,prevs->filename) ) )
 {
-if ( ( pl_entry->title != NULL ) && ( 
strcmp(pl_entry->title,prevs->title) ) )
+if ( ( pl_entry_title != NULL ) && ( 
strcmp(pl_entry_title,prevs->title) ) )
 {
-int pos = aud_drct_pl_get_pos();
-char *current_file = aud_drct_pl_get_file(pos);
-do_command(cmd_line_ttc, current_file, pos);
-g_free(current_file);
+do_command(cmd_line_ttc);
 g_free(prevs->title);
-prevs->title = g_strdup(pl_entry->title);
+prevs->title = g_strdup(pl_entry_title);
 }
 }
 else
 {
 g_free(prevs->filename);
-prevs->filename = g_strdup(pl_entry->filename);
+prevs->filename = g_strdup(pl_entry_filename);
 /* if filename changes, reset title as well */
 if ( prevs->title != NULL )
 g_free(prevs->title);
-prevs->title = g_strdup(pl_entry->title);
+prevs->title = g_strdup(pl_entry_title);
 }
 }
 else
 {
-if ( prevs->title != NULL )
-g_free(prevs->title);
-prevs->title = g_strdup(pl_entry->title);
-if ( prevs->filename != NULL )
-g_free(prevs->filename);
-prevs->filename = g_strdup(pl_entry->filename);
+if ( pl_entry_filename != NULL &&  pl_entry_title != NULL )
+{
+   do_command(cmd_line_ttc);
+   if ( prevs->title != NULL )
+g_free(prevs->title);
+   prevs->title = g_strdup(pl_entry_title);
+   if ( prevs->filename != NULL )
+g_free(prevs->filename);
+   prevs->filename = g_strdup(pl_entry_filename);
+   }
 }
+
+   str_unref (pl_entry_filename);
+   str_unref (pl_entry_ti

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#815543: [g++] errors in parsing templates

[Matthias Klose]

On 22.02.2016 11:15, Matthias Klose wrote:

Control: tags -1 + moreinfo
Control: reassign -1 g++-5

please provide the preprocessed source (from one of these platforms).

On 22.02.2016 10:39, Giulio Paci wrote:

Package: g++
Version: 4:5.3.1-8
Severity: important

--- Please enter the report below this line. ---

Recently I updated phonetisaurus package and it failed to compile on a few
architectures, where it used to compile (See
https://buildd.debian.org/status/package.php?p=phonetisaurus&suite=experimental).

On hppa, x32 and sparc64 I obtain the following error:

"/usr/include/fst/interval-set.h: In member function 'bool
fst::IntervalSet::Contains(const fst::IntervalSet&) const':
/usr/include/fst/interval-set.h:351:54: error: expected ')' before 'it1'
  } else if (it2->begin < it1->begin || it2->end > it1->end) {  // no C"

that seems a bug in g++.

According to https://gcc.gnu.org/bugzilla/show_bug.cgi?id=10200 it also seems
to be a recurrent bug, apparently solved upstream.


this works for me at least on x32.

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

Bug#815840: libfcgi-perl: bundles libfcgi, vulnerable to CVE-2012-6687

[Tianon Gravi]

Package: libfcgi-perl
Version: 0.77-1+b2
Severity: important
Tags: security upstream

It would appear that the version of libfcgi that upstream has bundled is 
vulnerable to CVE-2012-6687.

I had hoped that unbundling would be our easiest solution here (adding 
"libfcgi-dev" to "Build-Depends" and adding "override_dh_auto_configure" to 
include "--use-installed"), but it runs into issues with "FCGX_Detach" missing:

|dh_auto_test -O--buildsystem=perl_makemaker
|   make -j1 test TEST_VERBOSE=1
| make[1]: Entering directory '/usr/src/pkg'
| Running Mkbootstrap for FCGI ()
| chmod 644 "FCGI.bs"
| PERL_DL_NONLAZY=1 "/usr/bin/perl" "-Iblib/lib" "-Iblib/arch" test.pl
| 1..1
| # Running under perl version 5.022001 for linux
| # Current time local: Wed Feb 24 23:47:47 2016
| # Current time GMT:   Wed Feb 24 23:47:47 2016
| # Using Test.pm version 1.26
| Can't load 'blib/arch/auto/FCGI/FCGI.so' for module FCGI: 
blib/arch/auto/FCGI/FCGI.so: undefined symbol: FCGX_Detach at 
/usr/share/perl/5.22/XSLoader.pm line 70.
|  at blib/arch/FCGI.pm line 8.
| BEGIN failed--compilation aborted at blib/arch/FCGI.pm line 9.
| Compilation failed in require at test.pl line 3.
| BEGIN failed--compilation aborted at test.pl line 3.
| Makefile:1017: recipe for target 'test_dynamic' failed
| make[1]: Leaving directory '/usr/src/pkg'
| make[1]: *** [test_dynamic] Error 2
| dh_auto_test: make -j1 test TEST_VERBOSE=1 returned exit code 2


I'm in a bit over my head, but hopefully something sane can be done here (since 
upstream doesn't seem to be especially active based on the date of the most 
recent release and the activity on the issue tracker).

Thanks!

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

Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages libfcgi-perl depends on:
ii  libc6   2.21-9
ii  perl5.22.1-7
ii  perl-base [perlapi-5.22.1]  5.22.1-7

libfcgi-perl recommends no packages.

libfcgi-perl suggests no packages.

-- no debconf information

Bug#678921: Info received (STILL broken in 3.5-2+b2 in Jessie)

[Athanasius]

  Here, have a patch that gets this working again.  As soon as I'd
nailed semantics of a the function calls versus g_free() and str_unref()
it's been working 100% here.

--- audacious-plugins-3.5/src/song_change/song_change.c 2014-04-23 
03:37:46.0 +0100
+++ new-audacious-plugins-3.5/src/song_change/song_change.c 2016-02-25 
00:05:31.937064865 +
@@ -32,7 +32,7 @@
 static void songchange_playback_begin(gpointer unused, gpointer unused2);
 static void songchange_playback_end(gpointer unused, gpointer unused2);
 static void songchange_playlist_eof(gpointer unused, gpointer unused2);
-//static void songchange_playback_ttc(gpointer, gpointer);
+static void songchange_playback_ttc(gpointer, gpointer);
 
 typedef struct
 {
@@ -252,7 +252,7 @@
 hook_dissociate("playback begin", songchange_playback_begin);
 hook_dissociate("playback end", songchange_playback_end);
 hook_dissociate("playlist end reached", songchange_playlist_eof);
-// hook_dissociate( "playlist set info" , songchange_playback_ttc);
+hook_dissociate("title change" , songchange_playback_ttc);
 
 if ( ttc_prevs != NULL )
 {
@@ -320,7 +320,7 @@
 ttc_prevs = g_malloc0(sizeof(songchange_playback_ttc_prevs_t));
 ttc_prevs->title = NULL;
 ttc_prevs->filename = NULL;
-// hook_associate( "playlist set info" , songchange_playback_ttc , 
ttc_prevs );
+hook_associate("title change" , songchange_playback_ttc , ttc_prevs );
 
 return TRUE;
 }
@@ -335,53 +335,54 @@
 do_command (cmd_line_after);
 }
 
-#if 0
 static void
 songchange_playback_ttc(gpointer plentry_gp, gpointer prevs_gp)
 {
-if ( ( aud_ip_state->playing ) && ( strcmp(cmd_line_ttc,"") ) )
+if ( aud_drct_get_playing() && ( strcmp(cmd_line_ttc,"") ) )
 {
 songchange_playback_ttc_prevs_t *prevs = prevs_gp;
-PlaylistEntry *pl_entry = plentry_gp;
+   int playlist = aud_playlist_get_playing ();
+   int pl_entry = aud_playlist_get_position(playlist);
+   gchar *pl_entry_filename = aud_playlist_entry_get_filename(playlist, 
pl_entry);
+   gchar *pl_entry_title = aud_playlist_entry_get_title(playlist, 
pl_entry, FALSE);
 
 /* same filename but title changed, useful to detect http stream song 
changes */
 
 if ( ( prevs->title != NULL ) && ( prevs->filename != NULL ) )
 {
-if ( ( pl_entry->filename != NULL ) && ( 
!strcmp(pl_entry->filename,prevs->filename) ) )
+if ( ( pl_entry_filename != NULL ) && ( 
!strcmp(pl_entry_filename,prevs->filename) ) )
 {
-if ( ( pl_entry->title != NULL ) && ( 
strcmp(pl_entry->title,prevs->title) ) )
+if ( ( pl_entry_title != NULL ) && ( 
strcmp(pl_entry_title,prevs->title) ) )
 {
-int pos = aud_drct_pl_get_pos();
-char *current_file = aud_drct_pl_get_file(pos);
-do_command(cmd_line_ttc, current_file, pos);
-g_free(current_file);
+do_command(cmd_line_ttc);
 g_free(prevs->title);
-prevs->title = g_strdup(pl_entry->title);
+prevs->title = g_strdup(pl_entry_title);
 }
 }
 else
 {
 g_free(prevs->filename);
-prevs->filename = g_strdup(pl_entry->filename);
+prevs->filename = g_strdup(pl_entry_filename);
 /* if filename changes, reset title as well */
 if ( prevs->title != NULL )
 g_free(prevs->title);
-prevs->title = g_strdup(pl_entry->title);
+prevs->title = g_strdup(pl_entry_title);
 }
 }
 else
 {
 if ( prevs->title != NULL )
 g_free(prevs->title);
-prevs->title = g_strdup(pl_entry->title);
+prevs->title = g_strdup(pl_entry_title);
 if ( prevs->filename != NULL )
 g_free(prevs->filename);
-prevs->filename = g_strdup(pl_entry->filename);
+prevs->filename = g_strdup(pl_entry_filename);
 }
+
+   str_unref (pl_entry_filename);
+   str_unref (pl_entry_title);
 }
 }
-#endif
 
 static void songchange_playlist_eof(gpointer unused, gpointer unused2)
 {

Bug#813143: openjdk-7-jre-headless: Please re-disable atk bridge

[Samuel Thibault]

JOSM team, on Fri 29 Jan 2016 20:43:52 +0100, wrote:
> Basically the UI breaks at many places, EDT violations occur often, nasty
> display bugs are encountered.

Yes, more generally OpenJDK has threading issues, and thus we have to
make java-atk-wrapper extra cautious with it...

> These problems have been reported upstream by several users,

Where have they been reported?

> but GNOME ATK bridge seems unmaintained (no commit in the past 6
> months).

No commit in past 6 months doesn't mean it's unmaintained. It just does
the job. The development is rather in orca.

Anyway, I have now uploaded a fix.

Samuel

Bug#815675: ITP: ftpbackup -- Script to backups your data from a Debian system to a ftp space

[Nikolaus Rath]

[ forwarded from debian-devel to have this included in the ITP ]

From: Jakub Wilk 
Subject: Re: Bug#815675: ITP: ftpbackup -- Script to backups your data from a 
Debian system to a ftp space
Newsgroups: gmane.linux.debian.devel.general
To: debian-de...@lists.debian.org
Date: Wed, 24 Feb 2016 23:26:11 +0100

* Brian May , 2016-02-25, 08:14:
>I haven't seen the code myself, however one of the comments was:
>
>  "just having whitespace in the destination directory will lead to a
>  crash, set -e is not used, and errors are redirected to /dev/null"
>
>This sounds to me like a recipe for security problems.

I wouldn't worry about whitespace in destination directory. If the
attacker can control were backups go, we have a bigger problem...

But the bug density of this code is astounding:

>ARCHIVE=$BACKUPHOME/$SERVER-backup-`date +%d-%m-%Y`.tar.gz

Eww, little-endian dates.
https://xkcd.com/1179/

># create BACKUPHOME if not exists
>mkdir -p $BACKUPHOME

No umask set anywhere in this script, so in default setup the
directory (and later, the backup files) will be created readable to
anyone.

>dpkg --get-selections| awk -F' ' '{print $1}' > $PKGLIST
>RETVAL=$?
>if [[ $RETVAL != 0 ]]; then
>echo "Issue while performing dpkg --get-selections of
> $SERVER" | mail -s "Issue while performing dpkg get selections of
> $SERVER" $ADMINEMAIL

Contrary to what the error message suggests, this catches only errors
from awk, not from dpkg.

>tar --preserve-permissions -z -c -f $ARCHIVE  \
>--exclude=/var/lib/mysql/data \
>--exclude=$BACKUPHOME/$SERVER-backup* \
>--exclude=/var/log \
>--exclude=/var/cache/apt/archives \
>$EXCLUDES \
>/etc /var /home /opt /usr/local/bin  > /dev/null 2>&1

What about /srv? Errors are hidden and ignored.

># remove old archive on the FTP
> lftp -e "set ftp:ssl-allow no; 

Not only this program lets the backups be sent over unencrypted
channel, but it even disables opportunistic TLS.

>rm -f $SERVER-backup-`date -d "-$RETENTION day" +%d-%m-%Y`.tar.bz2;exit" -u 
>$FTPUSER,$FTPPASS $FTPSERVER > /dev/null 2>&1

This removal feature seems to work correctly only if you run backups
every day, and never close to midnight.

Wait, no, it doesn't work at all: the script creates .tar.gz, but then
it tries to delete .tar.bz2.

[Gratitude for the review would be best expressed by requesting
removal of this package from the archive.]

-- 
Jakub Wilk

Bug#814780: transition: papi

[Emilio Pozuelo Monfort]

Control: tags -1 confirmed

On 18/02/16 19:11, Emilio Pozuelo Monfort wrote:
> On 15/02/16 12:08, Andreas Beckmann wrote:
>> Package: release.debian.org
>> Severity: normal
>> User: release.debian@packages.debian.org
>> Usertags: transition
>>
>> Hi,
>>
>> papi 5.4.3 comes with a mini-transition libpapi5.4.1 -> libpapi5.4.3
>> No auto tracker was generated so far, although the new package is in
>> experimental for some time already.
> 
> Thanks to Adam you have a tracker now.
> 
> Unfortunately this would collide and get blocked by the openmpi transition, so
> let's wait for that.

Let's do this, as papi could migrate. eztrace will need to wait for openmpi but
that's not a huge deal.

Emilio

Bug#780253: Re Bug #780253 - libreoffice-writer: LibreOffice has no support for Google Drive

[Stéphane Aulery]

Hi Rene,

Le 24/02/2016 23:41, Rene Engelhard a écrit :

On Wed, Feb 24, 2016 at 07:12:17PM +0100, Stéphane Aulery wrote:

This bug has been fixed in Ubuntu.

Maybe the patch is transferable?


No. (Well, maybe.)

Looking at what they did:

   # Set up Google API keys, see 
http://www.chromium.org/developers/how-tos/api-keys .
   # Note: these are for Ubuntu use ONLY. For your own distribution,
   # please get your own set of keys.
   # Permission to add API keys, from Paweł Hajdan, To chad.mil...@canonical.com
   # msgid: caadnaofsfoch68nm1sgpctrxqmspykqguputsf7sgrsrxih...@mail.gmail.com
   # reused from chromium-browser 48.0.2564.82-0ubuntu1.1222
   GOOGLEAPI_APIKEY_UBUNTU := 
   GOOGLEAPI_CLIENTID_UBUNTU := 
   GOOGLEAPI_CLIENTSECRET_UBUNTU := 
   CONFIGURE_FLAGS += --with-gdrive-client-id=$(GOOGLEAPI_CLIENTID_UBUNTU) 
--with-gdrive-client-secret=$(GOOGLEAPI_CLIENTSECRET_UBUNTU)

so no, we can't take that. Of course, we could get ours via the same way
- but then we also could post it somewhere on a public site, it's then no
secret anymore. It's as if we would put passwords publically visible.

Or I misunderstand the concept of a "secret" here, but I doubt that.

That said, I see that chromium-browser in Debian also has a debian/apikeys...


Ok, forget that. No way to spread this kind of thing!

Thanks Rene.

Regards,

--
Stéphane Aulery

Bug#463510: aptitude: Remove option to run reportbug

[Manuel A. Fernandez Montecelo]

Control: reopen -1
Control: tags -1 + pending


Hi,

2014-06-02 08:17 Matijs van Zuijlen:

Package: aptitude
Version: 0.6.10-1+b1
Followup-For: Bug #463510

Well, this is surprising. For quite a while it seemed the consensus was
to indeed remove reportbug, and now I suddenly get a message that this
bug report has been closed. Why this sudden change of heart?


This will be removed in the next version, marking as +pending.


Cheers.
--
Manuel A. Fernandez Montecelo 

Bug#815775: #815775: zeroc-ice: FTBFS against ruby2.3

[Christian Hofstaedtler]

Control: severity -1 serious
Control: retitle -1 Build-Depends on unavailable packages mono-gmcs 
libmono2.0-cil

Dear Maintainer,

A followup rebuild of your package zeroc-ice in an unmodified sid
chroot using sbuild failed in the same way as originally indicated.

The root cause appears to be a build dependency on the following
packages that are not available in sid or testing:

  libmono2.0-cil
  mono-gmcs

Therefore I'm raising the severity of this bug.

Thank you,
-- 
 ,''`.  Christian Hofstaedtler 
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  `-

Bug#815765: #815765: remctl: FTBFS against ruby2.3

[Christian Hofstaedtler]

Control: severity -1 serious

Dear Maintainer,

During a follow-up rebuild of remctl in an unmodified sid chroot
using sbuild, your package FTBFS in the very same way - phpize not
finding libtool.

Therefore I'm raising the bug's severity as it's likely the package
will FTBFS for anyone building it.

Thank you,
-- 
 ,''`.  Christian Hofstaedtler 
: :' :  Debian Developer
`. `'   7D1A CFFA D9E0 806C 9C4C  D392 5C13 D6DB 9305 2E03
  `-

Bug#772681: kernel-package bug preventing build NVidia proprietary module

[Manoj Srivastava]

Hi,

Thanks for the report. This should be relatively easy to fix,
 and I’ll try getting to a new release perhaps this weekend.

manoj
-- 
I'll say it again for the logic impaired. Larry Wall
Manoj Srivastava    
4096R/C5779A1C E37E 5EC5 2A01 DA25 AD20  05B6 CF48 9438 C577 9A1C


smime.p7s
Description: S/MIME cryptographic signature

Bug#729927: [6f23a1c] Fix for Bug#729927 committed to git

[Manoj Srivastava]

tags 729927 + pending
thanks
Hi,

 The following change has been committed for this bug by
 Manoj Srivastava  on the branch 
 master at Wed, 24 Feb 2016 14:57:22 -0800.

 The fix will be in the next upload. 
=
Emit no #line directives if gen_line_dirs is false

There are two instances in the code which will print a #line directive
to the resulting lexer, regardless of the value of gen_line_dirs. Fix
them, so they also respect gen_line_dirs.

Bug fix: "flex --noline outputs a #line directive", thanks to Arthur
Schwarz (Closes: #729927).

Signed-off-by: Manoj Srivastava 
=

Bug#729693: [36e2e59] Fix for Bug#729693 committed to git

[Manoj Srivastava]

tags 729693 + pending
thanks
Hi,

 The following change has been committed for this bug by
 Manoj Srivastava  on the branch 
 master at Wed, 24 Feb 2016 14:49:24 -0800.

 The fix will be in the next upload. 
=
Allow '%option noline' in flex input file

 Allow specifying '%option noline' in the input file, leading to the
 same effect as calling flex with the command line option --noline.

 Bug fix: "%option noline generates and error message", thanks to
 Arthur Schwarz (Closes: #729693).

Signed-off-by: Manoj Srivastava 
=

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#762634: initramfs-tools: [armhf] mounting rootfs on USB disk fails / some USB host controller drivers missing in initramfs

[Vagrant Cascadian]

On 2016-02-24, Vagrant Cascadian wrote:
> On 2016-02-04, Ben Hutchings wrote:
>> Oh, so the MODULES=most case is bust and we need to list more host
>> controller drivers (or include all modules under drivers/usb/host/).
>> How about MODULES=dep; does that work now?
>
> MODULES=dep appears to pull in the necessary drivers on a recent stretch
> install on a wandboard solo, using initramfs-tools 0.123, but
> MODULES=most still requires manually including them in
> /etc/initramfs-tools/modules.

And, FWIW, MODULES=dep appears to also workaround the issue on the wandboard 
dual
with initramfs-tools 0.120.


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#807720: Information about Wandboard Quad out-of-date

[Vagrant Cascadian]

On 2016-02-06, Vagrant Cascadian wrote:
> On 2015-12-11, Martin Michlmayr wrote:
>> en/hardware/supported/arm.xml says:
>>
>> [..] Support for
>> the onboard audio options (analog, S/PDIF, HDMI-Audio) and for
>> the onboard WLAN/Bluetooth module is not available in &debian;
>> 8.
>
> I can test some of the audio support on a wandboard solo (don't have a
> working S/PDIF setup) I have, but my wandboard dual and quad are tied up
> for a while at least, so I can't test the wifi or bluetooth either.

I was able to test analog audio headphones and microphone jack using the
4.4.2-3 kernel from unstable.

Didn't have luck with HDMI audio, but I need to verify the HDMI audio
input works before being confident about that.

Don't have S/PDIF to test.


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#815753: fwupdmgr: thinks my internal camera is external

[Mario_Limonciello]

Although technically this is an internal device, I don't believe that any of 
those USB attributes can identify this information about the physical location 
of the bus.
Please correct me if I'm wrong.

Furthermore, this is a moot point since the Internal flag is only used to relax 
authentication checks on removable devices so this has no value other than 
cosmetic since you can't do anything to this device's firmware from fwupd.

-Original Message-
From: Paul Wise [mailto:p...@debian.org]
Sent: Wednesday, February 24, 2016 3:51 AM
To: Debian Bug Tracking System 
Subject: Bug#815753: fwupdmgr: thinks my internal camera is external

Package: fwupd
Version: 0.6.2-1
Severity: minor

fwupdmgr thinks my internal camera is external (Internal: False):

pabs@chianamo ~ $ fwupdmgr get-devices
...
Device: usb:00:01:06
  DisplayName: Integrated Camera
  Provider:USB
  Created: 2016-02-24
  Guid:3015b96c-e897-55cb-a658-1b161524e3e4
  Version: 35.69
  Internal:False
  AllowOnline: False
  AllowOffline:False
...
pabs@chianamo ~ $ lsusb | grep -i cam
Bus 001 Device 006: ID 17ef:4816 Lenovo Integrated Webcam pabs@chianamo ~ $ 
sudo lsusb -vvd 17ef:4816 [sudo] password for pabs:

Bus 001 Device 006: ID 17ef:4816 Lenovo Integrated Webcam Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   2.00
  bDeviceClass  239 Miscellaneous Device
  bDeviceSubClass 2 ?
  bDeviceProtocol 1 Interface Association
  bMaxPacketSize064
  idVendor   0x17ef Lenovo
  idProduct  0x4816 Integrated Webcam
  bcdDevice   23.45
  iManufacturer   1 Chicony Electronics Co., Ltd.
  iProduct2 Integrated Camera
  iSerial 0
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength  722
bNumInterfaces  2
bConfigurationValue 1
iConfiguration  0
bmAttributes 0x80
  (Bus Powered)
MaxPower  200mA
Interface Association:
  bLength 8
  bDescriptorType11
  bFirstInterface 0
  bInterfaceCount 2
  bFunctionClass 14 Video
  bFunctionSubClass   3 Video Interface Collection
  bFunctionProtocol   0
  iFunction   4 Integrated Camera
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   1
  bInterfaceClass14 Video
  bInterfaceSubClass  1 Video Control
  bInterfaceProtocol  0
  iInterface  4 Integrated Camera
  VideoControl Interface Descriptor:
bLength13
bDescriptorType36
bDescriptorSubtype  1 (HEADER)
bcdUVC   1.00
wTotalLength   78
dwClockFrequency   30.00MHz
bInCollection   1
baInterfaceNr( 0)   1
  VideoControl Interface Descriptor:
bLength18
bDescriptorType36
bDescriptorSubtype  2 (INPUT_TERMINAL)
bTerminalID 1
wTerminalType  0x0201 Camera Sensor
bAssocTerminal  4
iTerminal   0
wObjectiveFocalLengthMin  0
wObjectiveFocalLengthMax  0
wOcularFocalLength0
bControlSize  3
bmControls   0x00040a04
  Auto-Exposure Priority
  Zoom (Absolute)
  PanTilt (Absolute)
  Privacy
  VideoControl Interface Descriptor:
bLength11
bDescriptorType36
bDescriptorSubtype  5 (PROCESSING_UNIT)
  Warning: Descriptor too short
bUnitID 2
bSourceID   1
wMaxMultiplier  0
bControlSize2
bmControls 0x013f
  Brightness
  Contrast
  Hue
  Saturation
  Sharpness
  Gamma
  Backlight Compensation
iProcessing 0
bmVideoStandards 0x1b
  None
  NTSC - 525/60
  SECAM - 625/50
  NTSC - 625/50
  VideoControl Interface Descriptor:
bLength27
bDescriptorType36
bDescriptorSubtype  6 (EXTENSION_UNIT)
bUnitID 3
guidExtensionCode {0a3e1874-8254-1a48-b402-48b8b8c49cc8}
bNumControl10
bNrPins 1
baSourceID( 0)  2
bControlSize2
bmControls( 0)   0xff
bmControls( 1)   0x03
iExtension  0
  VideoControl Interface Descriptor:
bLength 

Bug#780253: Re Bug #780253 - libreoffice-writer: LibreOffice has no support for Google Drive

[Rene Engelhard]

Hi,

On Wed, Feb 24, 2016 at 07:12:17PM +0100, Stéphane Aulery wrote:
> This bug has been fixed in Ubuntu.
> 
> Maybe the patch is transferable?

No. (Well, maybe.)

Looking at what they did:

  # Set up Google API keys, see 
http://www.chromium.org/developers/how-tos/api-keys .
  # Note: these are for Ubuntu use ONLY. For your own distribution,
  # please get your own set of keys.
  # Permission to add API keys, from Paweł Hajdan, To chad.mil...@canonical.com
  # msgid: caadnaofsfoch68nm1sgpctrxqmspykqguputsf7sgrsrxih...@mail.gmail.com
  # reused from chromium-browser 48.0.2564.82-0ubuntu1.1222
  GOOGLEAPI_APIKEY_UBUNTU := 
  GOOGLEAPI_CLIENTID_UBUNTU := 
  GOOGLEAPI_CLIENTSECRET_UBUNTU := 
  CONFIGURE_FLAGS += --with-gdrive-client-id=$(GOOGLEAPI_CLIENTID_UBUNTU) 
--with-gdrive-client-secret=$(GOOGLEAPI_CLIENTSECRET_UBUNTU)

so no, we can't take that. Of course, we could get ours via the same way
- but then we also could post it somewhere on a public site, it's then no
secret anymore. It's as if we would put passwords publically visible.

Or I misunderstand the concept of a "secret" here, but I doubt that.

That said, I see that chromium-browser in Debian also has a debian/apikeys...

Regards,

Rene

Bug#678921: STILL broken in 3.5-2+b2 in Jessie

[Athanasius]

  This is still broken.  Looking at
 where I saw someone
had posted this bug it may well be that a section of code that is #if
0'd out due to not being updated for some other changes.

  It would be great to get this updated.  All I wanted to do was log
song titles on a stream so as to track down the artist and title of a
song I've been loving.  It just started playing though so my immediate
need is now moot ;) .

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, Wi

Bug#814269: jessie-pu: package nettle/2.7.1-5

[Adam D. Barratt]

Control: tags -1 + pending

On Sun, 2016-02-21 at 12:18 +, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
> 
> On Tue, 2016-02-09 at 20:59 +0100, Magnus Holmgren wrote:
> > OK to upload fix for https://bugs.debian.org/813679 (CVE-2015-8803
> > CVE-2015-8804 CVE-2015-8805), as suggested by (a member of) the
> > security team? (Security-related bugs but unlikely to be exploitable.)
> 
> Assuming that the resulting package has been tested on Jessie, please go
> ahead.

Uploaded and flagged for acceptance.

Regards,

Adam

Bug#762634: initramfs-tools: [armhf] mounting rootfs on USB disk fails / some USB host controller drivers missing in initramfs

[Vagrant Cascadian]

On 2016-02-04, Ben Hutchings wrote:
> On Wed, 2016-02-03 at 15:43 -0800, Vagrant Cascadian wrote:
>> On 2016-01-25, Ben Hutchings wrote:
>> > On Thu, 12 Nov 2015 09:49:33 + Ian Campbell  
>> > wrote:
>> > > On Wed, 2015-11-11 at 18:46 -0600, Vagrant Cascadian wrote:
>> > > > Would definitely like to see this, with a recent install on a Wandboard
>> > > > Dual with a USB2 sata disk for the rootfs. It installed fine with
>> > > > jessie's debian-installer, but failed on initial boot.
>> > > >  
>> > > > I worked around it by adding to /etc/initramfs-tools/modules:
>> > > >  
>> > > >   ci_hdrc_imx
>> > > >   phy_mxs_usb
>> > > >  
>> > > > I haven't yet verified if only adding "phy_mxs_usb" instead of both 
>> > > > will
>> > > > work.
>> ...
>> > > I think Ben essentially did this in #762042[0], which ends up adding any
>> > > phy-* which are currently loaded to the initramfs. That change appears to
>> > > be in v0.119 while Jessie has v0.120 so perhaps something else is going 
>> > > on.
>> > >  
>> > > ci-* isn't covered by this logic, so that might be it in the first case.
>> > > What is ci-*?
>> > 
>> > Thaose are the chipidea USB controller drivers, which should get found
>> > through sysfs.
>> > 
>> > Please can you clear out /etc/initramfs-tools/modules (temporarily) and
>> > run:
>> > 
>> >     sh -x /usr/sbin/mkinitramfs -o /dev/null 3.16.0-4-armmp 
>> > >mkinitramfs.log 2>&1
>> > 
>> > Then send the log so we can see how this is going wrong.
>> 
>> Attached is a log of the above command with /etc/initramfs-tools/modules
>> cleared out.
>
> Oh, so the MODULES=most case is bust and we need to list more host
> controller drivers (or include all modules under drivers/usb/host/).
> How about MODULES=dep; does that work now?

MODULES=dep appears to pull in the necessary drivers on a recent stretch
install on a wandboard solo, using initramfs-tools 0.123, but
MODULES=most still requires manually including them in
/etc/initramfs-tools/modules.


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#784391: Logs flooded with "irq ### affinity_hint subset empty"

[higuita]

Hi

I still have this on jessie, any change of backporting this to
jessie? i have 1 million irqbalance messages in the daemon log.

If no backport, any problem of using the "--hintpolicy=ignore"
workaround?

Thanks
higuita

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#815837: armci-mpi -- ARMCI-compatible implemntation using MPI RMA

[Michael Banck]

Package: wnpp
Severity: wishlist
Owner: Debian Science Team 

* Package name: armci-mpi
  Version : 0.0
  Upstream Author : The ARMCI-MPI Team at Argonne National Laboratory
* URL : https://wiki.mpich.org/armci-mpi/index.php/Main_Page
* License : OpenMPI license
  Programming Lang: C
  Description : ARMCI-compatible implementation using MPI RMA

ARMCI-MPI is a completely rewritten implementation of the (Global
Arrays) ARMCI one-sided communication interface that uses MPI RMA
(remote memory access) for one-sided communication.
.
ARMCI-MPI is nearly feature-complete with respect to ARMCI as provided
in Global Arrays.  As of Global Arrays 5.2, ARMCI-MPI can be easily
configured to work with Global Arrays and all the valid tests pass. 
.
This package includes the MPI-3 branch of ARMCI-MPI (mpi3rma branch).

Bug#815836: latex-make: lualatex support

[Andreas Beckmann]

Package: latex-make
Version: 2.2.2-1
Severity: normal

Hi Vincent,

for using lualatex with LaTeX.mk a small fix is needed in LaTeX.mk:

-   sed -e 's,\\openout[0-9]* = `\(.*\)'"'.,TD_$(1)$(4)_OUTPUTS += \1,p;d" \
+   sed -e 's,\\openout[0-9]* = \([^`].*\),TD_$(1)$(4)_OUTPUTS += 
\1,p;s,\\openout[0-9]* = `\(.*\)'"'.,TD_$(1)$(4)_OUTPUTS += \1,p;d" \

Compared with pdflatex, lualatex writes the \openout lines in the logfile
without quotes around the filename.
This needs lualatex from texlive in stretch/sid (beta-0.80.0), because
the lualatex in jessie (beta-0.79.1) does not emit \openout in the logfile
at all.

Thereafter I can use

PDFLATEX = lualatex
include LaTeX.mk


Andreas

Bug#186568: bug#22793: grep -E assertion failure with back references

[santiagorr]

Control: reassign -1 glibc
Control: retitle -1 "ERE '0|()0|\1|0' causes regexec undefined behavior"
Control: forwarded -1 https://sourceware.org/bugzilla/show_bug.cgi?id=18986
Control: tags -1 + patch

El 24/02/16 a las 11:46, Paul Eggert escribió:
> With recent 'grep' you can work around the problem by configuring
> --with-included-regex. That has some other undesirable properties, though.
> 
> This is really a glibc bug
>  and the glibc patch
> could be applied to the Debian copy of glibc. Here's the patch:
> 
> http://git.savannah.gnu.org/cgit/gnulib.git/commit/?id=5513b40999149090987a0341c018d05d3eea1272
> 
> In other words, Debian bug #186568 is really a glibc bug, not a grep bug.
> Can you please fix the Debian bug report accordingly? I'll CC: this message
> there.

Paul, thanks for the info. I am answering to the mail, including the
control commands to reassign the bug to glibc.

Cheers,

Santiago


signature.asc
Description: Digital signature

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#749979: forwarded 749979 https://bugs.documentfoundation.org

[Stéphane Aulery]

forwarded 749979 https://bugs.documentfoundation.org/show_bug.cgi?id=98164
tags 749979 + upstream
tags 749979 + moreinfo
stop
-

He request a list on mandatory fonts to upstream.

--
Stéphane Aulery

Bug#815835: repsnapper: glib runtime error on loading model

[lkcl]

Package: repsnapper
Version: 2.4a0-1+b1
Severity: normal

when loading a model i get the following error:

(repsnapper:28175): glibmm-CRITICAL **: 
unhandled exception (type Glib::Error) in signal handler:
domain: g-key-file-error-quark
code  : 4
what  : Key file does not have group 'Extruder'

the system that i am using is a continuously-upgraded one (on-demand)
so what this means is that somewhere there is an incorrectly
(insufficiently) specified dependency, such that the right dependencies
haven't been properly pulled in.

this is with LIBGL_ALWAYS_SOFTWARE *not* defined.


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

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

Versions of packages repsnapper depends on:
ii  libatk1.0-02.18.0-1
ii  libatkmm-1.6-1v5   2.24.2-1
ii  libc6  2.21-6
ii  libcairo2  1.14.0-2.1
ii  libcairomm-1.0-1v5 1.12.0-1
ii  libfontconfig1 2.11.0-6.1
ii  libfreetype6   2.5.2-2
ii  libgcc11:5.2.1-17
ii  libgdk-pixbuf2.0-0 2.31.1-2+b1
ii  libgl1-mesa-glx [libgl1]   10.3.2-1
ii  libglib2.0-0   2.46.0-2
ii  libglibmm-2.4-1v5  2.46.3-1
ii  libglu1-mesa [libglu1] 9.0.0-2
ii  libgtk2.0-02.24.25-1
ii  libgtkglext1   1.2.0-3.2
ii  libgtkglextmm-x11-1.2-0v5  1.2.0-7
ii  libgtkmm-2.4-1v5   1:2.24.4-2+b1
ii  libice62:1.0.9-1
ii  libpango-1.0-0 1.38.0-3
ii  libpangocairo-1.0-01.38.0-3
ii  libpangoft2-1.0-0  1.38.0-3
ii  libpangomm-1.4-1v5 2.38.1-1
ii  libpangox-1.0-00.0.2-4
ii  libsigc++-2.0-0v5  2.6.2-1
ii  libsm6 2:1.2.2-1
ii  libstdc++6 5.2.1-17
ii  libx11-6   2:1.6.2-3
ii  libxml++2.6-2v52.40.1-1
ii  libxml22.9.1+dfsg1-4
ii  libxmu62:1.1.2-1
ii  libxt6 1:1.1.4-1
ii  libzip41.0.1-1.1
ii  zlib1g 1:1.2.8.dfsg-2+b1

repsnapper recommends no packages.

repsnapper suggests no packages.

-- no debconf information

Bug#813933: RFS: sawfish/1:1.11-1 [ITA] -- window manager for X11

[Jose M Calhariz]

Hi, sorry for the long time.  But I went to my home country.

In the usual palce there is my lastest interaction. 

On 23/02/16 11:09, Mattia Rizzolo wrote:
> On Wed, Feb 17, 2016 at 11:43:14AM +, Mattia Rizzolo wrote:
>> On Wed, Feb 10, 2016 at 09:44:09PM +, Jose M Calhariz wrote:
>>> One more interation.
>> uops!
>>
>> This slipped off my sight, sorry for the delay! :|
>>
>>> On 08/02/16 21:57, Mattia Rizzolo wrote:
 On Mon, Feb 08, 2016 at 09:29:55PM +, Jose M Calhariz wrote:
> Today I didn't review all yours remarks.  But in the spirit of release
> early and release often here goes my today effort.
 yay, I definitely approve this ;)
 I hadn't gone deeper, just commented on your last changes here.

> On 07/02/16 22:01, Mattia Rizzolo wrote:
>> On Sun, Feb 07, 2016 at 08:40:10PM +, Jose M Calhariz wrote:
>>> On 06/02/16 23:41, Mattia Rizzolo wrote:
 Umh, couldn't you turn d/rules to use the dh sequencer?
>>> I don't know enough and lintian show many problems with upstream 
>>> d/rules.
>> well, let's fix them, then :)
>> Attached there is a d/rules using short dh, may you try it and bend it
>> better to the needs of this package?
> I managed to make it compile, but for a reason I don't know I needed to
> add the following lines:
>
> override_dh_auto_configure:
> cp /usr/share/misc/config.guess .
> cp /usr/share/misc/config.sub .
> dh_auto_configure --parallel
 that's so weird.

 even more in light of the new dh_update_autotools_config which is run
 automatically by dh >= 9.20160114 and do exactly that.
 Are you testing your package in an update sid chroot?

> I have tried many ideas but was only this way that it build
 also, it did build here without them.
>>> As you may see in d/rules, I found another workaround.  This time I
>>> believe that is correct.
>> umh, that is so tautological and useless :)
>> So, you are telling dh_clean to remove those files in debian/clean, just
>> to leter tell it telling to *not* remove those 2 in debian/rules!
>>
>> Just remove those config.{sub,guess} from debian/clean, and it should be
>> just fine.
>> And while on it also remove 'configure' and 'libtool' from d/clean, no
>> need to remove them.
>> d/clean is to remove files created a build time and not cleaned up by
>> the build system, this is not the case here.  And I have the impression
>> there are several other useless entries there.
>>
>> And while you are cleaning useless files up, now the
>> override_dh_auto_configure is useless too.
>>
>>
>> Then sawfish-lisp-source.dirs is empty, remove it;
>> and please check whether all the entries on sawfish.dirs are needed or
>> not; I can count on a single hand the occasions where a debian/*.dirs
>> file was really needed, remember that files copied by dh tools don't
>> need it.
>>
>>> I have reviewed all the bugs, so I am closing what I more certain that
>>> is fixed by 1.11.
>> cool!
>>
>>
>> In nearly 10 days of pause I forgot almose everything I wrote here…
>> I hope later today to be able to review everything again and provide you
>> with a list of stuff.
> actually, scratch these last lines.
> For me, just another thing (other than the above) and them I'm happy:
> please rename debian/manpages to debian/sawfish.manpages, for clarity.
>
>> I also saw you tried to do the symlink_to_dir thinghy, I'll check if
>> more is needed.
> the symlink_to_dir versions lack the epoch (the leading '1:' of the
> version).
>
> It seems otherwise fine to me.
>




signature.asc
Description: OpenPGP digital signature

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&id=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&id=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&id=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

Bug#814855: Audigy 2 ZS not working

[Stefan Potyra]

Hi Ben,

my soundcard also doesn't work any longer:

03:07.0 Multimedia audio controller: Creative Labs SB Audigy (rev 04)
Subsystem: Creative Labs SB Audigy 2 ZS (SB0350)
Flags: bus master, medium devsel, latency 64
I/O ports at ec00 [size=64]
Capabilities: 

I believe it it also covered by emu10k1.

Correct and intended by your change?

Anything I can do to help?

Cheers,
  Stefan.

Bug#815834: mdadm: with systemd as PID 1, no clean way to restart the mdadm monitor

[Francesco Poli (wintermute)]

Package: mdadm
Version: 3.3.4-1.1+b1
Severity: normal

Hello!

The issue I am reporting may be related to bug #796624, but it's not
the same.

After upgrading packages (especially libraries), I routinely use
"checkrestart" (from package debian-goodies) to see which processes
need to be restarted.

I noticed that, whenever the mdadm monitor process needs to be restarted
(for instance, after a libc6 upgrade), there seems to be no clean way to
actually restart it, if using systemd as PID 1.

Suppose we have to restart the mdadm monitor process:

  # checkrestart
  [...]
  service mdadm-raid restart
  service mdadm-waitidle restart
  service mdadm restart
  [...]
  # ps aux | grep mdadm | head -n 1
  root   359  0.0  0.0  13620  2508 ?Ss   23:18   0:00 /sbin/mdadm 
--monitor --scan

Which service command should I use?

  # service mdadm restart
  Failed to restart mdadm.service: Unit mdadm.service is masked.
  # service mdadm-waitidle restart
  Failed to restart mdadm-waitidle.service: Unit mdadm-waitidle.service is 
masked.
  # service mdadm-raid restart

The first two do nothing, since they are masked.
The last one seems to be successful, but:

  # checkrestart
  [...]
  service mdadm-raid restart
  service mdadm-waitidle restart
  service mdadm restart
  [...]
  # ps aux | grep mdadm | head -n 1
  root   359  0.0  0.0  13620  2556 ?Ss   23:18   0:00 /sbin/mdadm 
--monitor --scan

Nothing has changed! Please note that the mdadm monitor process PID is
the same as before: it has not been restarted.

It seems that, with systemd as PID 1, the available services are
unable to restart the running mdadm monitor...
Please note that, with sysvinit as PID 1, it's possible to restart
the mdadm monitor via the appropriate service.


Please provide a clean way to restart the mdadm monitor process:
I could kill it and then start it again by hand, but it doesn't feel
especially safe to do that...

It seems to me that the init script which is able to restart the
mdadm monitor process is /etc/init.d/mdadm .
I wonder why there's no corresponding service file for systemd and
why the service is masked instead.
Wait, there's /lib/systemd/system/mdmonitor.service : is

  # systemctl restart mdmonitor.service

or

  # service mdmonitor restart

the clean way I am looking for?

Unfortunately, checkrestart does not suggest it.

Please clarify, thanks for your time!
Bye.


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

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

Versions of packages mdadm depends on:
ii  debconf [debconf-2.0]  1.5.58
ii  initscripts2.88dsf-59.3
ii  libc6  2.21-9
ii  lsb-base   9.20160110
ii  udev   228-6

Versions of packages mdadm recommends:
ii  exim4-daemon-light [mail-transport-agent]  4.86-7+b2
ii  kmod   22-1

mdadm suggests no packages.

-- debconf information:
  mdadm/initrdstart_msg_errblock:
  mdadm/initrdstart_msg_errmd:
  mdadm/mail_to: root
* mdadm/initrdstart: all
  mdadm/initrdstart_notinconf: false
  mdadm/initrdstart_msg_errconf:
  mdadm/initrdstart_msg_intro:
  mdadm/autocheck: true
  mdadm/start_daemon: true
  mdadm/initrdstart_msg_errexist: