Bug#895502: libsmithwaterman FTBFS on 32bit: missing symbol

2018-04-11 Thread Adrian Bunk
Source: libsmithwaterman
Version: 0.0+git20160702.2610e25-1
Severity: serious

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

...
   dh_makeshlibs -a -O--no-parallel
dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libsmithwaterman0/DEBIAN/symbols doesn't match 
completely debian/libsmithwaterman0.symbols
--- debian/libsmithwaterman0.symbols 
(libsmithwaterman0_0.0+git20160702.2610e25-1_armel)
+++ dpkg-gensymbolsbf8gA7   2018-04-11 13:29:25.035300351 +
@@ -69,7 +69,7 @@
  _ZNSt7__cxx1115basic_stringbufIcSt11char_traitsIcESaIcEED2Ev@Base 
0.0+git20160702.2610e25
  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_iESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE12_M_erase_auxESt23_Rb_tree_const_iteratorIS8_E@Base
 0.0+git20160702.2610e25
  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_iESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE24_M_get_insert_unique_posERS7_@Base
 0.0+git20160702.2610e25
- 
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_iESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS8_ERS7_@Base
 0.0+git20160702.2610e25
+#MISSING: 0.0+git20160702.2610e25-1# 
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_iESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS8_ERS7_@Base
 0.0+git20160702.2610e25
  
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_iESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE8_M_eraseEPSt13_Rb_tree_nodeIS8_E@Base
 0.0+git20160702.2610e25
  _ZeqRK11IndelAlleleS1_@Base 0.0+git20160702.2610e25
  _ZlsRSoRK11IndelAllele@Base 0.0+git20160702.2610e25
dh_makeshlibs: failing due to earlier errors
debian/rules:8: recipe for target 'binary-arch' failed
make: *** [binary-arch] Error 2



Bug#895500: ruby-slim FTBFS with ruby-tilt 2.0.8-1

2018-04-11 Thread Adrian Bunk
Source: ruby-slim
Version: 3.0.7-1
Severity: serious
Tags: buster sid

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

...
  1) Error:
TestSlimEmbeddedEngines#test_render_with_builder:
NameError: undefined local variable or method `xml' for 
#
(__TEMPLATE__):3:in `block in singleton class'
(__TEMPLATE__):-2:in `instance_eval'
(__TEMPLATE__):-2:in `singleton class'
(__TEMPLATE__):-5:in `__tilt_47056743556540'
/usr/lib/ruby/vendor_ruby/tilt/template.rb:170:in `call'
/usr/lib/ruby/vendor_ruby/tilt/template.rb:170:in `evaluate'
/usr/lib/ruby/vendor_ruby/tilt/template.rb:109:in `render'
/build/1st/ruby-slim-3.0.7/test/core/helper.rb:24:in `render'
/build/1st/ruby-slim-3.0.7/test/core/helper.rb:47:in `assert_html'
/build/1st/ruby-slim-3.0.7/test/core/test_embedded_engines.rb:102:in 
`test_render_with_builder'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:107:in `block (3 levels) in run'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:204:in `capture_exceptions'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:104:in `block (2 levels) in run'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:255:in `time_it'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:103:in `block in run'
/usr/lib/ruby/vendor_ruby/minitest.rb:350:in `on_signal'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:275:in `with_info_handler'
/usr/lib/ruby/vendor_ruby/minitest/test.rb:102:in `run'
/usr/lib/ruby/vendor_ruby/minitest.rb:839:in `run_one_method'
/usr/lib/ruby/vendor_ruby/minitest.rb:324:in `run_one_method'
/usr/lib/ruby/vendor_ruby/minitest.rb:311:in `block (2 levels) in run'
/usr/lib/ruby/vendor_ruby/minitest.rb:310:in `each'
/usr/lib/ruby/vendor_ruby/minitest.rb:310:in `block in run'
/usr/lib/ruby/vendor_ruby/minitest.rb:350:in `on_signal'
/usr/lib/ruby/vendor_ruby/minitest.rb:337:in `with_info_handler'
/usr/lib/ruby/vendor_ruby/minitest.rb:309:in `run'
/usr/lib/ruby/vendor_ruby/minitest.rb:159:in `block in __run'
/usr/lib/ruby/vendor_ruby/minitest.rb:159:in `map'
/usr/lib/ruby/vendor_ruby/minitest.rb:159:in `__run'
/usr/lib/ruby/vendor_ruby/minitest.rb:136:in `run'
/usr/lib/ruby/vendor_ruby/minitest.rb:63:in `block in autorun'

281 runs, 425 assertions, 0 failures, 1 errors, 0 skips
/usr/lib/ruby/vendor_ruby/rake/testtask.rb:130:in `block (3 levels) in define': 
Command failed with status (1): [ruby -w -I"lib:lib:test/core"  
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" 
"test/core/test_code_blocks.rb" "test/core/test_code_escaping.rb" 
"test/core/test_code_evaluation.rb" "test/core/test_code_output.rb" 
"test/core/test_code_structure.rb" "test/core/test_commands.rb" 
"test/core/test_embedded_engines.rb" "test/core/test_encoding.rb" 
"test/core/test_erb_converter.rb" "test/core/test_html_attributes.rb" 
"test/core/test_html_escaping.rb" "test/core/test_html_structure.rb" 
"test/core/test_parser_errors.rb" "test/core/test_pretty.rb" 
"test/core/test_ruby_errors.rb" "test/core/test_slim_template.rb" 
"test/core/test_tabs.rb" "test/core/test_text_interpolation.rb" 
"test/core/test_thread_options.rb" "test/core/test_unicode.rb" ] (RuntimeError)
from /usr/lib/ruby/vendor_ruby/rake/file_utils.rb:57:in `sh'
from /usr/lib/ruby/vendor_ruby/rake/file_utils.rb:105:in `ruby'
from /usr/lib/ruby/vendor_ruby/rake/testtask.rb:117:in `block (2 
levels) in define'
from /usr/lib/ruby/vendor_ruby/rake/file_utils_ext.rb:59:in `verbose'
from /usr/lib/ruby/vendor_ruby/rake/testtask.rb:111:in `block in define'
from /usr/lib/ruby/vendor_ruby/rake/task.rb:271:in `block in execute'
from /usr/lib/ruby/vendor_ruby/rake/task.rb:271:in `each'
from /usr/lib/ruby/vendor_ruby/rake/task.rb:271:in `execute'
from /usr/lib/ruby/vendor_ruby/rake/task.rb:213:in `block in 
invoke_with_call_chain'
from /usr/lib/ruby/2.5.0/monitor.rb:226:in `mon_synchronize'
from /usr/lib/ruby/vendor_ruby/rake/task.rb:193:in 
`invoke_with_call_chain'
from /usr/lib/ruby/vendor_ruby/rake/task.rb:237:in `block in 
invoke_prerequisites'
from /usr/lib/ruby/vendor_ruby/rake/task.rb:235:in `each'
from /usr/lib/ruby/vendor_ruby/rake/task.rb:235:in 
`invoke_prerequisites'
from /usr/lib/ruby/vendor_ruby/rake/task.rb:212:in `block in 
invoke_with_call_chain'
from /usr/lib/ruby/2.5.0/monitor.rb:226:in `mon_synchronize'
from /usr/lib/ruby/vendor_ruby/rake/task.rb:193:in 
`invoke_with_call_chain'
from /usr/lib/ruby/vendor_ruby/rake/task.rb:237:in `block in 
invoke_prerequisites'
from /usr/lib/ruby/vendor_ruby/rake/task.rb:235:in `each'
from /usr/lib/ruby/vendor_ruby/rake/task.rb:235:in 
`invoke_prerequisites'
from /usr/lib/ruby/vendor_ruby/rake/task.rb:212:in `block in 
invoke_with_call_chain'
from /usr/lib/ruby/2.5.0/monitor.rb:226:in `mon_synchronize'
from 

Bug#895499: enki-aseba FTBFS on armel/armhf: error: 'glGenLists' was not declared in this scope

2018-04-11 Thread Adrian Bunk
Source: enki-aseba
Version: 1:1.6.0-5
Severity: serious

https://buildd.debian.org/status/package.php?p=enki-aseba=sid

...
cd /<>/obj-arm-linux-gnueabi/viewer && /usr/bin/c++  -DQT_CORE_LIB 
-DQT_NO_DEBUG -DUSE_SDL 
-I/<>/obj-arm-linux-gnueabi/viewer/enkiviewer_autogen/include 
-I/usr/include/SDL2 -I/<> 
-I/<>/obj-arm-linux-gnueabi/viewer -isystem 
/usr/include/arm-linux-gnueabi/qt5 
-I/usr/include/arm-linux-gnueabi/qt5/QtWidgets 
-I/usr/include/arm-linux-gnueabi/qt5/QtGui -isystem 
/usr/include/arm-linux-gnueabi/qt5/QtCore -isystem 
/usr/lib/arm-linux-gnueabi/qt5/mkspecs/linux-g++ 
-I/usr/include/arm-linux-gnueabi/qt5/QtOpenGL  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2   -fPIC -fPIC 
-std=gnu++11 -o CMakeFiles/enkiviewer.dir/objects/EPuckBody.cpp.o -c 
/<>/viewer/objects/EPuckBody.cpp
/<>/viewer/objects/EPuckBody.cpp: In function 'GLint 
Enki::GenEPuckBody()':
/<>/viewer/objects/EPuckBody.cpp:712:12: error: 'glGenLists' was 
not declared in this scope
  GLint lid=glGenLists(1);

^~
/<>/viewer/objects/EPuckBody.cpp:712:12: note: suggested 
alternative: 'glFinish'
  GLint lid=glGenLists(1);

^~
glFinish
/<>/viewer/objects/EPuckBody.cpp:713:17: error: 'GL_COMPILE' was 
not declared in this scope
  glNewList(lid, GL_COMPILE);

 ^~
/<>/viewer/objects/EPuckBody.cpp:713:17: note: suggested 
alternative: 'GL_SAMPLER'
  glNewList(lid, GL_COMPILE);

 ^~
 GL_SAMPLER
/<>/viewer/objects/EPuckBody.cpp:713:2: error: 'glNewList' was not 
declared in this scope
  glNewList(lid, GL_COMPILE);

  ^
/<>/viewer/objects/EPuckBody.cpp:713:2: note: suggested 
alternative: 'glViewport'
  glNewList(lid, GL_COMPILE);

  ^
  glViewport
/<>/viewer/objects/EPuckBody.cpp:715:3: error: 'glBegin' was not 
declared in this scope
   glBegin (GL_TRIANGLES);

   ^~~
/<>/viewer/objects/EPuckBody.cpp:728:4: error: 'glNormal3f' was 
not declared in this scope
glNormal3f (normals[ni][1],-normals[ni][0],normals[ni][2]);

^~
/<>/viewer/objects/EPuckBody.cpp:728:4: note: suggested 
alternative: 'normals'
glNormal3f (normals[ni][1],-normals[ni][0],normals[ni][2]);

^~
normals
/<>/viewer/objects/EPuckBody.cpp:729:4: error: 'glTexCoord2f' was 
not declared in this scope
glTexCoord2f(textures[ti][0],textures[ti][1]);

^~~~
/<>/viewer/objects/EPuckBody.cpp:729:4: note: suggested 
alternative: 'glTexStorage2D'
glTexCoord2f(textures[ti][0],textures[ti][1]);

^~~~
glTexStorage2D
/<>/viewer/objects/EPuckBody.cpp:730:4: error: 'glVertex3f' was 
not declared in this scope
glVertex3f (vertices[vi][1],-vertices[vi][0],vertices[vi][2]);

^~
/<>/viewer/objects/EPuckBody.cpp:730:4: note: suggested 
alternative: 'glVertexAttrib3f'
glVertex3f (vertices[vi][1],-vertices[vi][0],vertices[vi][2]);

^~
glVertexAttrib3f
/<>/viewer/objects/EPuckBody.cpp:733:3: error: 'glEnd' was not 
declared in this scope
   glEnd ();

   ^
/<>/viewer/objects/EPuckBody.cpp:735:2: error: 'glEndList' was not 
declared in this scope
  glEndList();

  ^
viewer/CMakeFiles/enkiviewer.dir/build.make:132: recipe for target 
'viewer/CMakeFiles/enkiviewer.dir/objects/EPuckBody.cpp.o' failed
make[3]: *** [viewer/CMakeFiles/enkiviewer.dir/objects/EPuckBody.cpp.o] Error 1


The root cause is that on armel/armhf (and arm64 in Ubuntu)
Qt5 is compiled with OpenGL ES instead of OpenGL.

enki-aseba should be fixed to build and work with OpenGL ES,
but if this is not easily possible please
- change the build dependency from libqt5opengl5-dev
  to libqt5opengl5-desktop-dev, and
- file a removal bug for the old armel+armhf binaries
  of enki-aseba and aseba against ftp.debian.org



Bug#895497: tryton-server fails to install

2018-04-11 Thread Adrian Bunk
Package: tryton-server
Version: 4.6.3-1
Severity: serious

https://piuparts.debian.org/sid/source/t/tryton-server.html

...
  Preparing to unpack .../tryton-server_4.6.3-1_all.deb ...
  Unpacking tryton-server (4.6.3-1) ...
  Setting up tryton-server (4.6.3-1) ...
  invoke-rc.d: could not determine current runlevel
  invoke-rc.d: policy-rc.d denied execution of start.
  update-rc.d: error: no runlevel symlinks to modify, aborting!
  dpkg: error processing package tryton-server (--configure):
   installed tryton-server package post-installation script subprocess returned 
error exit status 1
  Errors were encountered while processing:
   tryton-server
  E: Sub-process /usr/bin/dpkg returned an error code (1)



Bug#895496: mgba FTBFS with Qt 5.10

2018-04-11 Thread Adrian Bunk
Source: mgba
Version: 0.5.2+dfsg1-3
Severity: serious

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

...
cd /build/1st/mgba-0.5.2+dfsg1/obj-x86_64-linux-gnu/qt && /usr/bin/c++  
-DBUILD_GL -DBUILD_QT_MULTIMEDIA -DBUILD_SDL -DDATADIR=\"share/mgba\" 
-DHAVE_CHMOD -DHAVE_LOCALE -DHAVE_LOCALTIME_R -DHAVE_SETLOCALE -DHAVE_STRDUP 
-DHAVE_STRNDUP -DHAVE_UMASK -DM_CORE_GB -DM_CORE_GBA -DQT_CORE_LIB -DQT_GUI_LIB 
-DQT_MULTIMEDIA_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG -DQT_OPENGL_LIB 
-DQT_WIDGETS_LIB -DUSE_CLI_DEBUGGER -DUSE_FFMPEG -DUSE_GDB_STUB -DUSE_LIBZIP 
-DUSE_LZMA -DUSE_MAGICK -DUSE_PNG -DUSE_PTHREADS -DUSE_ZLIB 
-D_7ZIP_PPMD_SUPPPORT -D_GNU_SOURCE 
-I/build/1st/mgba-0.5.2+dfsg1/obj-x86_64-linux-gnu/qt 
-I/build/1st/mgba-0.5.2+dfsg1/src/platform/qt 
-I/build/1st/mgba-0.5.2+dfsg1/obj-x86_64-linux-gnu/qt/mgba-qt_autogen/include 
-I/build/1st/mgba-0.5.2+dfsg1/src -I/usr/include/editline 
-I/usr/include/x86_64-linux-gnu -I/usr/include/x86_64-linux-gnu/ImageMagick-6 
-I/usr/include/ImageMagick-6 -I/usr/lib/x86_64-linux-gnu/libzip/include 
-I/build/1st/mgba-0.5.2+dfsg1/third-party/lzma -I/usr/include/SDL2 
-I/build/1st/mgba-0.5.2+dfsg1/src/platform/sdl -isystem 
/usr/include/x86_64-linux-gnu/qt5 -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtMultimedia -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtNetwork -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 
/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
/usr/include/x86_64-linux-gnu/qt5/QtOpenGL  -g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11   
-fPIC -std=gnu++11 -o CMakeFiles/mgba-qt.dir/MemoryModel.cpp.o -c 
/build/1st/mgba-0.5.2+dfsg1/src/platform/qt/MemoryModel.cpp
/build/1st/mgba-0.5.2+dfsg1/src/platform/qt/MemoryModel.cpp: In member function 
'void QGBA::MemoryModel::setRegion(uint32_t, uint32_t, const QString&, int)':
/build/1st/mgba-0.5.2+dfsg1/src/platform/qt/MemoryModel.cpp:97:17: error: no 
match for 'operator=' (operand types are 'QStaticText' and 'const QString')
  m_regionName = name;
 ^~~~
In file included from /usr/include/x86_64-linux-gnu/qt5/QtGui/QStaticText:1:0,
 from 
/build/1st/mgba-0.5.2+dfsg1/src/platform/qt/MemoryModel.h:12,
 from 
/build/1st/mgba-0.5.2+dfsg1/src/platform/qt/MemoryModel.cpp:6:
/usr/include/x86_64-linux-gnu/qt5/QtGui/qstatictext.h:68:18: note: candidate: 
QStaticText& QStaticText::operator=(QStaticText&&)
 QStaticText =(QStaticText &) Q_DECL_NOTHROW { swap(other); 
return *this; }
  ^~~~
/usr/include/x86_64-linux-gnu/qt5/QtGui/qstatictext.h:68:18: note:   no known 
conversion for argument 1 from 'const QString' to 'QStaticText&&'
/usr/include/x86_64-linux-gnu/qt5/QtGui/qstatictext.h:70:18: note: candidate: 
QStaticText& QStaticText::operator=(const QStaticText&)
 QStaticText =(const QStaticText &);
  ^~~~
/usr/include/x86_64-linux-gnu/qt5/QtGui/qstatictext.h:70:18: note:   no known 
conversion for argument 1 from 'const QString' to 'const QStaticText&'
make[3]: *** [qt/CMakeFiles/mgba-qt.dir/build.make:717: 
qt/CMakeFiles/mgba-qt.dir/MemoryModel.cpp.o] Error 1



Bug#895494: kimap FTBFS: symbol disappeared

2018-04-11 Thread Adrian Bunk
Source: kimap
Version: 17.12.3-1
Severity: serious

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

...
dh_makeshlibs '-Xusr/lib/libkdeinit5_*'  
dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libkf5imap5/DEBIAN/symbols doesn't match 
completely debian/libkf5imap5.symbols
--- debian/libkf5imap5.symbols (libkf5imap5_17.12.3-1_amd64)
+++ dpkg-gensymbolsrzXBbk   2019-05-14 17:20:45.321348109 -1200
@@ -1,5 +1,5 @@
 libKF5IMAP.so.5 libkf5imap5 #MINVER#
- _ZN10QByteArray7reserveEi@Base 17.08.0
+#MISSING: 17.12.3-1# _ZN10QByteArray7reserveEi@Base 17.08.0
  _ZN5KIMAP10AclJobBase10setMailBoxERK7QString@Base 15.07.90
  _ZN5KIMAP10AclJobBase11qt_metacallEN11QMetaObject4CallEiPPv@Base 15.07.90
  _ZN5KIMAP10AclJobBase11qt_metacastEPKc@Base 15.07.90
dh_makeshlibs: failing due to earlier errors
make[1]: *** [/usr/share/pkg-kde-tools/qt-kde-team/3/dhmk.mk:97: 
pre_binary_dh_makeshlibs] Error 2


Why did kimap export a function from QByteArray()?



Bug#895495: libkf5eventviews FTBFS: symbol disappeared

2018-04-11 Thread Adrian Bunk
Source: libkf5eventviews
Version: 4:17.12.3-1
Severity: serious

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

dh_makeshlibs '-Xusr/lib/libkdeinit5_*'  
dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libkf5eventviews5/DEBIAN/symbols doesn't match 
completely debian/libkf5eventviews5.symbols
--- debian/libkf5eventviews5.symbols (libkf5eventviews5_4:17.12.3-1_amd64)
+++ dpkg-gensymbolshYHHUq   2018-04-11 11:02:48.544501361 -1200
@@ -598,7 +598,7 @@
  _ZN10EventViews9MonthViewD0Ev@Base 4:17.12.2
  _ZN10EventViews9MonthViewD1Ev@Base 4:17.12.2
  _ZN10EventViews9MonthViewD2Ev@Base 4:17.12.2
- _ZN10QByteArray7reserveEi@Base 4:17.12.2
+#MISSING: 4:17.12.3-1# _ZN10QByteArray7reserveEi@Base 4:17.12.2
  
(optional=templinst)_ZN12KConfigGroup10writeEntryI10QByteArrayEEvPKcRKT_6QFlagsIN11KConfigBase15WriteConfigFlagEE@Base
 4:17.12.2
  
(optional=templinst)_ZN12KConfigGroup10writeEntryIiEEvPKcRK5QListIT_E6QFlagsIN11KConfigBase15WriteConfigFlagEE@Base
 4:17.12.2
  
(optional=templinst)_ZN12KConfigGroup10writeEntryIiEEvPKcRKT_6QFlagsIN11KConfigBase15WriteConfigFlagEE@Base
 4:17.12.2
dh_makeshlibs: failing due to earlier errors
make[1]: *** [/usr/share/pkg-kde-tools/qt-kde-team/3/dhmk.mk:97: 
pre_binary_dh_makeshlibs] Error 2


Why did kmime export a function from QByteArray?



Bug#895493: kmime FTBFS: symbol disappeared

2018-04-11 Thread Adrian Bunk
Source: kmime
Version: 17.12.3-1
Severity: serious

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

...
dh_makeshlibs '-Xusr/lib/libkdeinit5_*'  
dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libkf5mime5abi1/DEBIAN/symbols doesn't match 
completely debian/libkf5mime5abi1.symbols
--- debian/libkf5mime5abi1.symbols (libkf5mime5abi1_17.12.3-1_amd64)
+++ dpkg-gensymbolsxA3Agd   2018-04-11 10:56:49.406402045 -1200
@@ -1,6 +1,6 @@
 libKF5Mime.so.5abi1 libkf5mime5abi1 #MINVER#
  ABI_5_1@ABI_5_1 17.12.1
- _ZN10QByteArray7reserveEi@ABI_5_1 17.12.1
+#MISSING: 17.12.3-1# _ZN10QByteArray7reserveEi@ABI_5_1 17.12.1
  _ZN5KMime11NewsArticle10followUpToEb@ABI_5_1 17.12.1
  _ZN5KMime11NewsArticle10newsgroupsEb@ABI_5_1 17.12.1
  _ZN5KMime11NewsArticle10supersedesEb@ABI_5_1 17.12.1
dh_makeshlibs: failing due to earlier errors
make[1]: *** [/usr/share/pkg-kde-tools/qt-kde-team/3/dhmk.mk:97: 
pre_binary_dh_makeshlibs] Error 2


Why did kmime export a function from QByteArray()?



Bug#895446: Error in startup script: bad screen distance "4.5"

2018-04-11 Thread Torbjörn Andersson

Michael Biebl  wrote:

> $ gitk
> Error in startup script: bad screen distance "4.5"

Downgrading fontconfig to 2.12.6-0.1 (from 2.13.0-2) fixes this problem 
for me. I don't know what the implications of that are, though.


Torbjörn Andersson



Bug#895492: tiemu FTBFS: error: macro "abort" passed 1 arguments, but takes just 0

2018-04-11 Thread Adrian Bunk
Source: tiemu
Version: 3.04~git20110801-nogdb+dfsg-1
Severity: serious

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

...
gcc -I.. -I -DPREFIX=\"/usr\" -I. -I./core -I./core/uae -I./core/ti_hw 
-I./core/ti_sw -I./core/dbg -I./sound -I./gui -I./gui/calc -I./gui/debugger 
-I./ipc/dcop -I./ipc/dbus -I./ipc/com -I./kde -I./misc -DHAVE_CONFIG_H 
-DSHARE_DIR=\"/usr/share/tiemu\" -DLOCALEDIR=\"/usr/share/locale\" -c -g -O2 
-fstack-protector-strong -Wformat -Werror=format-security -D__LINUX__ 
-fvisibility=hidden -DGTK_DISABLE_DEPRECATED -DDEBUGGER -DNO_GDB 
-I/usr/include/tilp2 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/tilp2 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/tilp2 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/tilp2 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread 
-I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include 
-I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/pango-1.0 
-I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/fribidi 
-I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 -pthread 
-I/usr/include/libglade-2.0 -I/usr/include/gtk-2.0 
-I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/gio-unix-2.0/ 
-I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 
-I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/libpng16 -I/usr/include/pango-1.0 -I/usr/include/harfbuzz 
-I/usr/include/pango-1.0 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/fribidi 
-I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/libxml2 -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT  
core/state.c -o core/state.o
In file included from /usr/include/glib-2.0/glib/gutils.h:306:0,
 from /usr/include/glib-2.0/glib/gthread.h:34,
 from /usr/include/glib-2.0/glib/gasyncqueue.h:32,
 from /usr/include/glib-2.0/glib.h:32,
 from core/ti68k_def.h:39,
 from core/ti68k_int.h:31,
 from core/state.c:39:
/usr/include/stdlib.h:588:24: error: macro "abort" passed 1 arguments, but 
takes just 0
 extern void abort (void) __THROW __attribute__ ((__noreturn__));
^



Bug#892656: even more tests fail with version 2.0.2

2018-04-11 Thread Pirate Praveen


On April 12, 2018 2:48:32 AM GMT+05:30, Paolo Greppi  
wrote:
>Normally you'd expect to fix bugs with a new version, in this case
>while trying to update node-define-property 1.0.0-1 -> 2.0.2 the
>failing tests actually increased from 1 to 4.
>
>What puzzled me was that no tests fail on upstream's CI (travis), which
>also tests nodejs version 8.
>
>Turns out that we have upgraded node-is-descriptor to version 2.0.0,
>but the npm registry only has 1.0.2.
>
>I have forwarded the issue upstream, and I expect upstream to answer
>that define-property correctly pins the major version of is-descriptor
>with ^1.0.2 (https://docs.npmjs.com/misc/semver), stating that it won't
>work with 2.x.
>
>^1.0.2 should be translated with >= 1.0.2 && < 2.0.0 but we can't
>encode that in debian/control.
>
>So how can we check reverse dependencies for this type of issues in the
>future ?
>
>Paolo

build-and-upload script from ruby-team/meta can help if we have enabled tests. 
If we used that, then is-descriptor 1.0 -> 2.0 update would notify the failure 
before upload. But its likely we added is-descriptor 2.0 directly.

The best choice is upstream updating their dependency. Second choice is we 
update and send merge request.

As a worse case, we can downgrade node-is-descriptor to 1.0 if we have no other 
reverse dependency or embed 1.0 in node-define-property.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.



Bug#893515: digikam: FTBFS with kdepim 17.12.2

2018-04-11 Thread peter green

This was blocking stuff up in Raspbian buster so I decided to take a look.

I decided to base my work on the version currently in Debian experimental.

First of all I reduced the exiv2 dependency in both the Debian packaging and 
the upstream cmake to 0.25.

I then turned my attention to the kdepim problem. After some time messing 
around with upstreams broken git history I was able to locate the relevent 
patches, merge them together and fix-up the filepaths. They then applied 
cleanly.

I then ran into another build failure.

In file included from /usr/include/c++/7/cmath:45:0,
 from /usr/include/c++/7/math.h:36,
 from 
/digikam-5.7.0/core/libs/rawengine/libraw/internal/dcraw_common.cpp:22:
/usr/include/arm-linux-gnueabihf/bits/mathcalls.h:140:1: note: candidate: 
_Float64 powf64(_Float64, _Float64)
 __MATHCALL_VEC (pow,, (_Mdouble_ __x, _Mdouble_ __y));
 ^
/digikam-5.7.0/core/libs/rawengine/libraw/internal/dcraw_common.cpp:5752:14: 
note: candidate: float powf64(float, float)
 static float powf64(float a, float b)

it looks like there is a conflict between a function called "powf64" in the dcraw code in 
digikam and a "powf64" function in the kernel headers upstream fixed this by renaming 
powf64 to libraw_powf64, I did the same. In this case since it was a simple rename I did not bother 
going digging for the original upstream patch.

I am currently doing a final build with the changes, assuming it suceeds I will 
upload it to Raspbian and post a
debdiff to this bug.

No intent to NMU in Debian.



Bug#895482: Fails to upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 4

2018-04-11 Thread Axel Beckert
Hi,

Axel Beckert wrote:
> On other sid installations (including architectures amd64, i386 and
> armhf), the upgrade worked fine, […]

Correction: It failed on one i386 sid machine, too:

Updating certificates in /etc/ssl/certs...
W: /usr/share/ca-certificates/mozilla/GeoTrust_Global_CA_2.crt not found, but 
listed in /etc/ca-certificates.conf.
W: /usr/share/ca-certificates/mozilla/Swisscom_Root_CA_1.crt not found, but 
listed in /etc/ca-certificates.conf.
W: /usr/share/ca-certificates/mozilla/Swisscom_Root_CA_2.crt not found, but 
listed in /etc/ca-certificates.conf.
W: /usr/share/ca-certificates/mozilla/Swisscom_Root_EV_CA_2.crt not found, but 
listed in /etc/ca-certificates.conf.
rehash: skipping Swisscom_Root_CA_1.pem, cannot open file
rehash: skipping Swisscom_Root_CA_2.pem, cannot open file
rehash: skipping GeoTrust_Global_CA_2.pem, cannot open file
rehash: skipping Swisscom_Root_EV_CA_2.pem, cannot open file
dpkg: error processing package ca-certificates (--configure):
 installed ca-certificates package post-installation script subprocess returned 
error exit status 4
Errors were encountered while processing:
 ca-certificates

Still, it worked fine on at least one amd64 and one armhf machine.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE



Bug#895482: Fails to upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 4

2018-04-11 Thread Axel Beckert
Package: ca-certificates
Version: 20180409
Severity: serious

Upgrading ca-certificates from 20170717 to 20180409 fails for me as
follows on one machine:

Before unpacking, I have been shown this dialog, which I acknowledged
by pressing enter:

  ┌┤ ca-certificates configuration 
├─┐
  │ During upgrades, new certificates will be added. Please choose 
those you trust.  │
  │ 
 │
  │ New certificates to activate:   
 │
  │ 
 │
  │[ ] mozilla/GDCA_TrustAUTH_R5_ROOT.crt   
 │
  │[ ] mozilla/SSL.com_EV_Root_Certification_Authority_ECC.crt  
 │
  │[ ] mozilla/SSL.com_EV_Root_Certification_Authority_RSA_R2.crt   
 │
  │[ ] mozilla/SSL.com_Root_Certification_Authority_ECC.crt 
 │
  │[ ] mozilla/SSL.com_Root_Certification_Authority_RSA.crt 
 │
  │[ ] mozilla/TrustCor_ECA-1.crt   
 │
  │[ ] mozilla/TrustCor_RootCert_CA-1.crt   
 │
  │[ ] mozilla/TrustCor_RootCert_CA-2.crt   
 │
  │ 
 │
  │ 
 │
  │ 
 │
  │ 
 │
  
└──┘

Unpacking went fine:

Preparing to unpack .../04-ca-certificates_20180409_all.deb ...
Unpacking ca-certificates (20180409) over (20170717) ...

The first as well as the second try to configure ca-certificates
failed identically:

Setting up ca-certificates (20180409) ...
Updating certificates in /etc/ssl/certs...
W: /usr/share/ca-certificates/mozilla/AddTrust_Public_Services_Root.crt not 
found, but listed in /etc/ca-certificates.conf.
W: /usr/share/ca-certificates/mozilla/AddTrust_Qualified_Certificates_Root.crt 
not found, but listed in /etc/ca-certificates.conf.
W: /usr/share/ca-certificates/mozilla/UTN_USERFirst_Hardware_Root_CA.crt not 
found, but listed in /etc/ca-certificates.conf.
W: /usr/share/ca-certificates/mozilla/DST_ACES_CA_X6.crt not found, but listed 
in /etc/ca-certificates.conf.
rehash: skipping DST_ACES_CA_X6.pem, cannot open file
rehash: skipping AddTrust_Qualified_Certificates_Root.pem, cannot open file
rehash: skipping UTN_USERFirst_Hardware_Root_CA.pem, cannot open file
rehash: skipping AddTrust_Public_Services_Root.pem, cannot open file
dpkg: error processing package ca-certificates (--configure):
 installed ca-certificates package post-installation script subprocess returned 
error exit status 4
[…]
Errors were encountered while processing:
 ca-certificates
[…]
E: Sub-process /usr/bin/dpkg returned an error code (1)
[…]
Setting up ca-certificates (20180409) ...
Updating certificates in /etc/ssl/certs...
W: /usr/share/ca-certificates/mozilla/AddTrust_Public_Services_Root.crt not 
found, but listed in /etc/ca-certificates.conf.
W: /usr/share/ca-certificates/mozilla/AddTrust_Qualified_Certificates_Root.crt 
not found, but listed in /etc/ca-certificates.conf.
W: /usr/share/ca-certificates/mozilla/UTN_USERFirst_Hardware_Root_CA.crt not 
found, but listed in /etc/ca-certificates.conf.
W: /usr/share/ca-certificates/mozilla/DST_ACES_CA_X6.crt not found, but listed 
in /etc/ca-certificates.conf.
rehash: skipping DST_ACES_CA_X6.pem, cannot open file
rehash: skipping AddTrust_Qualified_Certificates_Root.pem, cannot open file
rehash: skipping UTN_USERFirst_Hardware_Root_CA.pem, cannot open file
rehash: skipping AddTrust_Public_Services_Root.pem, cannot open file
dpkg: error processing package ca-certificates (--configure):
 installed ca-certificates package post-installation script subprocess returned 
error exit status 4
Errors were encountered while processing:
 ca-certificates

On other sid installations (including architectures amd64, i386 and
armhf), the upgrade worked fine, despite most (if not all) of my
systems have similar ca-certificates settings, namely
"ca-certificates/trust_new_crts: ask" and just a few CAs
selected. It's though very likely that the actual list of CAs differs
from installation to installation as I enabled further ones per
machine as needed.

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (600, 'testing'), (500, 'unstable-debug'), 
(500, 'buildd-unstable'), (110, 

Bug#895455: marked as done (gradle breaks everytime Groovy is upgraded)

2018-04-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 Apr 2018 23:06:42 +
with message-id 
and subject line Bug#895455: fixed in gradle 3.4.1-7
has caused the Debian Bug report #895455,
regarding gradle breaks everytime Groovy is upgraded
to be marked as done.

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

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


-- 
895455: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895455
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gradle
Version: 3.4.1-6
Severity: serious
Control: affects -1 src:triplea src:zeroc-ice src:gradle-propdeps-plugin 
src:groovy src:gradle-jflex-plugin

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gradle-jflex-plugin.html

...
FAILURE: Build failed with an exception.

* What went wrong:
Could not create service of type ClassLoaderRegistry using 
GlobalScopeServices.createClassLoaderRegistry().

* Try:
Run with --debug option to get more log output.

* Exception is:
org.gradle.internal.service.ServiceCreationException: Could not create service 
of type ClassLoaderRegistry using 
GlobalScopeServices.createClassLoaderRegistry().
at 
org.gradle.internal.service.DefaultServiceRegistry$FactoryMethodService.invokeMethod(DefaultServiceRegistry.java:807)
at 
org.gradle.internal.service.DefaultServiceRegistry$FactoryService.create(DefaultServiceRegistry.java:761)
at 
org.gradle.internal.service.DefaultServiceRegistry$ManagedObjectProvider.getInstance(DefaultServiceRegistry.java:598)
at 
org.gradle.internal.service.DefaultServiceRegistry$SingletonService.get(DefaultServiceRegistry.java:643)
at 
org.gradle.internal.service.DefaultServiceRegistry.applyConfigureMethod(DefaultServiceRegistry.java:253)
at 
org.gradle.internal.service.DefaultServiceRegistry.findProviderMethods(DefaultServiceRegistry.java:214)
at 
org.gradle.internal.service.DefaultServiceRegistry.addProvider(DefaultServiceRegistry.java:352)
at 
org.gradle.internal.service.ServiceRegistryBuilder.build(ServiceRegistryBuilder.java:52)
at 
org.gradle.launcher.cli.BuildActionsFactory.createGlobalClientServices(BuildActionsFactory.java:153)
at 
org.gradle.launcher.cli.BuildActionsFactory.runBuildInSingleUseDaemon(BuildActionsFactory.java:141)
at 
org.gradle.launcher.cli.BuildActionsFactory.createAction(BuildActionsFactory.java:89)
at 
org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.createAction(CommandLineActionFactory.java:249)
at 
org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:239)
at 
org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:217)
at 
org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:33)
at 
org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:24)
at 
org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:33)
at 
org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:22)
at 
org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:210)
at 
org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:174)
at org.gradle.launcher.Main.doAction(Main.java:33)
at org.gradle.launcher.bootstrap.EntryPoint.run(EntryPoint.java:45)
at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:564)
at 
org.gradle.launcher.bootstrap.ProcessBootstrap.runNoExit(ProcessBootstrap.java:60)
at 
org.gradle.launcher.bootstrap.ProcessBootstrap.run(ProcessBootstrap.java:37)
at org.gradle.launcher.GradleMain.main(GradleMain.java:23)
Caused by: java.lang.IllegalArgumentException: Cannot find JAR 
'groovy-all-2.4.14.jar' required by module 'gradle-plugins' using classpath or 
distribution directory '/usr/share/gradle'
at 
org.gradle.api.internal.classpath.DefaultModuleRegistry.findDependencyJar(DefaultModuleRegistry.java:233)
at 
org.gradle.api.internal.classpath.DefaultModuleRegistry.findDependencyJars(DefaultModuleRegistry.java:123)
 

Processed: Pending fixes for bugs in the gradle package

2018-04-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tag 895455 + pending
Bug #895455 [gradle] gradle breaks everytime Groovy is upgraded
Added tag(s) pending.
> thanks
Stopping processing here.

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



Bug#895455: Pending fixes for bugs in the gradle package

2018-04-11 Thread pkg-java-maintainers
tag 895455 + pending
thanks

Some bugs in the gradle package are closed in revision
a787cb7b8b60bbc6928faa90639cead0675833ca in branch 'master' by Markus
Koschany

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/gradle.git/commit/?id=a787cb7

Commit message:

Update groovy-jar.patch and fix runtime errors with new Groovy versions.

Closes: #895455



Bug#895476: fwbuilder FTBFS: Cannot find file: .

2018-04-11 Thread Adrian Bunk
Source: fwbuilder
Version: 5.3.7-1
Severity: serious

Some recent change in unstable (Qt 5.10?) makes fwbuilder FTBFS:

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

...
configure: creating ./config.status
config.status: creating qmake.inc
config.status: creating src/res/objects_init.xml
config.status: creating src/res/templates.xml
config.status: creating src/libfwbuilder/qmake.inc
config.status: creating src/libfwbuilder/etc/fwbuilder.dtd
config.status: creating packaging/fwbuilder.control
config.status: creating packaging/fwbuilder.spec
config.status: creating packaging/fwbuilder-static-qt.spec
config.status: creating packaging/fwbuilder.nsi
config.status: creating config.h
config.status: creating src/libfwbuilder/src/fwbuilder/libfwbuilder-config.h
config.status: executing libtool commands
configure: WARNING: unrecognized options: --disable-maintainer-mode, 
--disable-dependency-tracking, --disable-silent-rules
QTDIR=""
Running qmake: /usr/bin/qmake -recursive
Empty filename passed to function
Cannot find file: .
make: *** [/usr/share/cdbs/1/class/autotools.mk:46: debian/stamp-autotools] 
Error 2



Bug#892656: even more tests fail with version 2.0.2

2018-04-11 Thread Paolo Greppi
Normally you'd expect to fix bugs with a new version, in this case while trying 
to update node-define-property 1.0.0-1 -> 2.0.2 the failing tests actually 
increased from 1 to 4.

What puzzled me was that no tests fail on upstream's CI (travis), which also 
tests nodejs version 8.

Turns out that we have upgraded node-is-descriptor to version 2.0.0, but the 
npm registry only has 1.0.2.

I have forwarded the issue upstream, and I expect upstream to answer that 
define-property correctly pins the major version of is-descriptor with ^1.0.2 
(https://docs.npmjs.com/misc/semver), stating that it won't work with 2.x.

^1.0.2 should be translated with >= 1.0.2 && < 2.0.0 but we can't encode that 
in debian/control.

So how can we check reverse dependencies for this type of issues in the future ?

Paolo



Bug#876582: marked as done (liboobs FTBFS with gtk-doc-tools 1.26: gtkdoc-mktmpl is no longer available)

2018-04-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 Apr 2018 21:20:46 +
with message-id 
and subject line Bug#876582: fixed in liboobs 3.0.0-4
has caused the Debian Bug report #876582,
regarding liboobs FTBFS with gtk-doc-tools 1.26: gtkdoc-mktmpl is no longer 
available
to be marked as done.

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

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


-- 
876582: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876582
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: liboobs
Version: 3.0.0-3
Severity: serious
Tags: buster sid

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

...
Making all in reference
make[4]: Entering directory '/build/1st/liboobs-3.0.0/doc/reference'
gtk-doc: Scanning header files
gtk-doc: Rebuilding template files
/bin/bash: gtkdoc-mktmpl: command not found
Makefile:599: recipe for target 'tmpl-build.stamp' failed
make[4]: *** [tmpl-build.stamp] Error 127
--- End Message ---
--- Begin Message ---
Source: liboobs
Source-Version: 3.0.0-4

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

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

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

Debian distribution maintenance software
pp.
Andriy Grytsenko  (supplier of updated liboobs package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 11 Apr 2018 23:30:04 +0300
Source: liboobs
Binary: liboobs-1-5 liboobs-1-dev liboobs-1-5-dbg
Architecture: source amd64
Version: 3.0.0-4
Distribution: unstable
Urgency: medium
Maintainer: Andriy Grytsenko 
Changed-By: Andriy Grytsenko 
Description:
 liboobs-1-5 - GObject based interface to system-tools-backends - shared library
 liboobs-1-5-dbg - GObject based interface to system-tools-backends - debug 
symbols
 liboobs-1-dev - GObject based interface to system-tools-backends - dev files
Closes: 876582
Changes:
 liboobs (3.0.0-4) unstable; urgency=medium
 .
   * Adding 03-migrate-gtk-doc.patch for gtk-doc-tools 1.26 (Closes: #876582).
   * Bump Standards-Version to 4.1.4: replace Priority: extra with 'optional'.
   * Bump debhelper compat to v10.
   * Converting packages to multiarch.
Checksums-Sha1:
 8e4b5beb5acca91c410697507e5e526e2a9b8aeb 2022 liboobs_3.0.0-4.dsc
 045b87f09110523d801c36a50091ad0e891d39db 10340 liboobs_3.0.0-4.debian.tar.xz
 eb989d8db02c67c02ae767409eee00a40401a4c4 234236 
liboobs-1-5-dbg_3.0.0-4_amd64.deb
 57a4eb8afbabaa981e60d2c71740f77b628e694b 73772 liboobs-1-5_3.0.0-4_amd64.deb
 27a8f2033702559a4240a3602b07e1bc994caaf7 131456 liboobs-1-dev_3.0.0-4_amd64.deb
 adb6efbfbe5b735a646d44b96e33aaa295ab6530 6714 liboobs_3.0.0-4_amd64.buildinfo
Checksums-Sha256:
 4860815db9cb86581caa8872e73799fc9ee9bef3cb8b862c5dc25c9ab7351635 2022 
liboobs_3.0.0-4.dsc
 2ef02afb23f89bf1d297516a7505c61e05aa0c7a96e882d948371385b9bb064d 10340 
liboobs_3.0.0-4.debian.tar.xz
 5601fb2d164bef124fbbc76f153fb83ba5ea7d654e04bf233afbe2f3ddaabef0 234236 
liboobs-1-5-dbg_3.0.0-4_amd64.deb
 89a5367e87f26c8cb3d23284c21d010e62fbb004f32aca4cbbb444a891a81f8c 73772 
liboobs-1-5_3.0.0-4_amd64.deb
 834a81967d799ca1d9f5c04a08578e8d09d96fe6ddcf9d3d6a951240194866fd 131456 
liboobs-1-dev_3.0.0-4_amd64.deb
 6e95ebada75e278fe1cd7fb2514801c2a95b58cce53d56e56c79d9e090629342 6714 
liboobs_3.0.0-4_amd64.buildinfo
Files:
 8434af477b8cf50e9378536131c16d24 2022 libs optional liboobs_3.0.0-4.dsc
 661f74f808b3644a2dbfe167fadf79fc 10340 libs optional 
liboobs_3.0.0-4.debian.tar.xz
 75c1713d0288878f2ec04796c52dd732 234236 debug optional 
liboobs-1-5-dbg_3.0.0-4_amd64.deb
 23361421b558014784720d1a7bc3aa0d 73772 libs optional 
liboobs-1-5_3.0.0-4_amd64.deb
 10b576d95f4c722b049286e3dafd78dd 131456 libdevel optional 
liboobs-1-dev_3.0.0-4_amd64.deb
 ffb9632ece8a1183363b09abcb922efa 6714 libs optional 
liboobs_3.0.0-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJaznUOAAoJEAV2MC/hidTSKDEP/1N7/lMJ9bfZlnKLba8iwJxt
+lT7eKHDRe62CAWjLo/H+UoOnA3MhArtgMg4kTqREEZUfCIvvCT11mOSEDF7sdm8
tCPrGRRMMKdApUUyP4aPm6lQ+2gzbQYur4sgMAC1cSrkhncpjv1HBkChg2BjGGrd

Processed: forwarded upstream

2018-04-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> forwarded 892656 https://github.com/jonschlinkert/define-property/issues/3
Bug #892656 [src:node-define-property] node-define-property: FTBFS and Debci 
failure
Set Bug forwarded-to-address to 
'https://github.com/jonschlinkert/define-property/issues/3'.
>
End of message, stopping processing here.

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



Processed: Bug title fix

2018-04-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> retitle 895471 gnudatalanguage FTBFS on mips/mipsel: cc1plus: out of memory
Bug #895471 [src:gnudatalanguage] gnudatalanguage FTBFSon mips/mipsel:
Changed Bug title to 'gnudatalanguage FTBFS on mips/mipsel: cc1plus: out of 
memory' from 'gnudatalanguage FTBFSon mips/mipsel:'.
> thanks
Stopping processing here.

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



Bug#895471: gnudatalanguage FTBFSon mips/mipsel:

2018-04-11 Thread Adrian Bunk
Source: gnudatalanguage
Version: 0.9.8-2
Severity: serious
Tags: patch

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

...
cd /<>/obj-mips-linux-gnu/src && /usr/bin/c++  -DHAVE_CONFIG_H 
-DWXUSINGDLL -D_FILE_OFFSET_BITS=64 -D__WXGTK__ -Dgnudatalanguage_EXPORTS 
-I/usr/include/GraphicsMagick 
-I/usr/lib/mips-linux-gnu/wx/include/gtk2-unicode-3.0 -I/usr/include/wx-3.0 
-I/usr/include/hdf5/serial -I/usr/include/hdf -I/usr/include/python2.7 
-I/usr/lib/python2.7/dist-packages/numpy/core/include -I/usr/include/eigen3 
-I/<> -I/<>/obj-mips-linux-gnu  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -DBUILD_DATE="\"Apr  3 2018\"" -std=gnu++11 -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC   -fopenmp -o 
CMakeFiles/gnudatalanguage.dir/datatypes.cpp.o -c 
/<>/src/datatypes.cpp
In file included from /usr/include/python2.7/numpy/ndarraytypes.h:1809:0,
 from /usr/include/python2.7/numpy/ndarrayobject.h:18,
 from /usr/include/python2.7/numpy/arrayobject.h:4,
 from /<>/src/datatypes.cpp:21:
/usr/include/python2.7/numpy/npy_1_7_deprecated_api.h:15:2: warning: #warning 
"Using deprecated NumPy API, disable it by " "#defining NPY_NO_DEPRECATED_API 
NPY_1_7_API_VERSION" [-Wcpp]
 #warning "Using deprecated NumPy API, disable it by " \
  ^~~

cc1plus: out of memory allocating 972584 bytes after a total of 51625984 bytes
make[3]: *** [src/CMakeFiles/gnudatalanguage.dir/build.make:282: 
src/CMakeFiles/gnudatalanguage.dir/datatypes.cpp.o] Error 1


Fix:

--- debian/rules.old2018-04-08 14:31:59.814323615 +
+++ debian/rules2018-04-08 14:33:25.220985470 +
@@ -1,9 +1,16 @@
 #!/usr/bin/make -f
 
 include /usr/share/dpkg/pkg-info.mk
+include /usr/share/dpkg/architecture.mk
 
 export DEB_BUILD_MAINT_OPTIONS=hardening=+all
 
+# less debug info to avoid running
+# out of address space
+ifneq (,$(filter $(DEB_HOST_ARCH), mips mipsel))
+  export DEB_CXXFLAGS_MAINT_APPEND += -g1
+endif
+
 CXXFLAGS += -DBUILD_DATE="\"$(shell LC_ALL=C date -u 
--date=@"$(SOURCE_DATE_EPOCH)" +'%b %e %Y')\"" -std=gnu++11
 
 %:



Bug#895469: openjfx FTBFS on armel: invalid instructions

2018-04-11 Thread Adrian Bunk
Source: openjfx
Version: 8u141-b14-3
Severity: serious
Tags: buster sid patch

https://buildd.debian.org/status/fetch.php?pkg=openjfx=armel=8u161-b12-1=1523051663=0

...
/tmp/ccxxsDUf.s: Assembler messages:
/tmp/ccxxsDUf.s:311: Error: selected processor does not support `movw 
r8,#:lower16:.Lllint_op_enter-.LrelativePCBase' in ARM mode
/tmp/ccxxsDUf.s:312: Error: selected processor does not support `movt 
r8,#:upper16:.Lllint_op_enter-.LrelativePCBase' in ARM mode
/tmp/ccxxsDUf.s:316: Error: selected processor does not support `movw 
r8,#:lower16:.Lllint_op_get_scope-.LrelativePCBase' in ARM mode
/tmp/ccxxsDUf.s:317: Error: selected processor does not support `movt 
r8,#:upper16:.Lllint_op_get_scope-.LrelativePCBase' in ARM mode
...


The baseline of the armel port was raised a few months ago,
this can be fixed with:

debian/patches/26-disable-webkit-jit-for-armv4.patch
-+#if CPU(ARM) && WTF_ARM_ARCH_VERSION < 5
++#if CPU(ARM) && WTF_ARM_ARCH_VERSION <= 5



Bug#895467: libsearpc FTBFS on 64bit big endian: test failure

2018-04-11 Thread Adrian Bunk
Source: libsearpc
Version: 3.0.8-2
Severity: serious

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

...
FAIL: test-searpc
=

Loaded 1 suites: 
Started

(process:10121): Searpc-WARNING **: 17:59:21.601: failed to read rpc request: 
Bad address

(process:10121): Searpc-WARNING **: 17:59:21.601: failed to read rpc response: 
Connection reset by peer
F
(process:10121): Searpc-WARNING **: 17:59:21.923: failed to read rpc request: 
Bad address

(process:10121): Searpc-WARNING **: 17:59:21.923: failed to send rpc call: 
Broken pipe
F
(process:10121): Searpc-WARNING **: 17:59:22.122: failed to read rpc request: 
Bad address

(process:10121): Searpc-WARNING **: 17:59:22.125: failed to read rpc response: 
Connection reset by peer
F

  1) Failure:
searpc::pipe_simple_call [searpc.c:427]
  Expression is not true: error == NULL
  Transport Error

  2) Failure:
searpc::pipe_large_request [searpc.c:454]
  Expression is not true: error == NULL
  Transport Error

  3) Failure:
searpc::pipe_concurrent_clients [searpc.c:483]
  Expression is not true: error == NULL
  Transport Error

System error: `fork()` call failed (12) - Cannot allocate memory
FAIL test-searpc (exit status: 255)


Testsuite summary for libsearpc 3.0.8

# TOTAL: 1
# PASS:  0
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See tests/test-suite.log
Please report to i...@seafile.com

make[5]: *** [Makefile:687: test-suite.log] Error 1



Processed (with 2 errors): unblock 787080 with 856192, forcibly merging 787080 894119

2018-04-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> unblock 787080 with 856192
Bug #787080 [wnpp] ITP: libreoffice-online -- LibreOffice on-line
No valid blocking bug(s) given; not doing anything
Failed to set blocking bugs of 787080: Unknown/archived blocking bug(s):856192.

> forcemerge 787080 894119
Bug #787080 [wnpp] ITP: libreoffice-online -- LibreOffice on-line
Bug #894119 [wnpp] RFP: libreoffice-online
894119 was blocked by: 804633 794890
894119 was not blocking any bugs.
Added blocking bug(s) of 894119: 857986
894119 was blocked by: 857986 794890 804633
894119 was not blocking any bugs.
Added blocking bug(s) of 894119: 870460
No valid blocking bug(s) given; not doing anything
Failed to forcibly merge 787080: Failure while trying to adjust bugs, please 
report this as a bug: Unknown/archived blocking bug(s):856192.
 at /usr/local/lib/site_perl/Debbugs/Control.pm line 2133.

> thanks
Stopping processing here.

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



Processed: Re: Bug#895235: sugar-toolkit-gtk3 FTBFS: devlibs error: There is no package matching [libfribidi0-dev] and noone provides it

2018-04-11 Thread Debian Bug Tracking System
Processing control commands:

> reassign -1 libpango1.0-dev 1.42.1-1
Bug #895235 [src:sugar-toolkit-gtk3] sugar-toolkit-gtk3 FTBFS: devlibs error: 
There is no package matching [libfribidi0-dev] and noone provides it
Bug reassigned from package 'src:sugar-toolkit-gtk3' to 'libpango1.0-dev'.
No longer marked as found in versions sugar-toolkit-gtk3/0.112-1.
Ignoring request to alter fixed versions of bug #895235 to the same values 
previously set
Bug #895235 [libpango1.0-dev] sugar-toolkit-gtk3 FTBFS: devlibs error: There is 
no package matching [libfribidi0-dev] and noone provides it
Marked as found in versions pango1.0/1.42.1-1.
> retitle -1 "pkg-config --libs pango" incorrectly contains -lfribidi
Bug #895235 [libpango1.0-dev] sugar-toolkit-gtk3 FTBFS: devlibs error: There is 
no package matching [libfribidi0-dev] and noone provides it
Changed Bug title to '"pkg-config --libs pango" incorrectly contains -lfribidi' 
from 'sugar-toolkit-gtk3 FTBFS: devlibs error: There is no package matching 
[libfribidi0-dev] and noone provides it'.
> affects -1 src:sugar-toolkit-gtk3 src:osm-gps-map src:gtkdataboxmm 
> src:fontforge
Bug #895235 [libpango1.0-dev] "pkg-config --libs pango" incorrectly contains 
-lfribidi
Added indication that 895235 affects src:sugar-toolkit-gtk3, src:osm-gps-map, 
src:gtkdataboxmm, and src:fontforge

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



Bug#895235: sugar-toolkit-gtk3 FTBFS: devlibs error: There is no package matching [libfribidi0-dev] and noone provides it

2018-04-11 Thread Adrian Bunk
Control: reassign -1 libpango1.0-dev 1.42.1-1
Control: retitle -1 "pkg-config --libs pango" incorrectly contains -lfribidi
Control: affects -1 src:sugar-toolkit-gtk3 src:osm-gps-map src:gtkdataboxmm 
src:fontforge

On Sun, Apr 08, 2018 at 08:12:42PM +0300, Adrian Bunk wrote:
> Source: sugar-toolkit-gtk3
> Version: 0.112-1
> Severity: serious
> 
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/sugar-toolkit-gtk3.html
> 
> ...
> d-shlibmove --commit \
>   --multiarch \
>   --exclude-la --exclude-a \
>   --devunversioned --ignorelibdep \
>   --movedev debian/tmp/usr/share/gir-1.0 usr/share/ \
>   --extralib 
> debian/tmp/usr/lib/x86_64-linux-gnu/libsugar-eventcontroller.so \
>   debian/tmp/usr/lib/x86_64-linux-gnu/libsugarext.so
> Library package automatic movement utility
>  --> libasound2-dev package exists.
>  --> libatk1.0-dev package exists.
>  --> libcairo-dev is provided by a package.
>  --> libcairo2-dev package exists.
> devlibs error: There is no package matching [libfribidi0-dev] and noone 
> provides it, please report bug to d-shlibs maintainer
>  --> libglib2.0-dev package exists.
>  --> libgtk-3-dev package exists.
>  --> libgtk2.0-dev package exists.
>  --> libice-dev package exists.
>  --> libpango1.0-dev package exists.
>  --> librsvg2-dev package exists.
>  --> libsm-dev package exists.
>  --> libx11-dev package exists.
>  --> libxfixes-dev package exists.
>  --> libxi-dev package exists.
> make: *** [debian/rules:118: debian/stamp-local-shlibs-libsugarext] Error 1

The root cause is:

$ pkg-config --libs pango
-lpango-1.0 -lgobject-2.0 -lglib-2.0 -lfribidi 
$

See also
  https://bugzilla.gnome.org/show_bug.cgi?id=794570#c2

cu
Adrian

-- 

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



Bug#881595: marked as done (libwoodstox-java: FTBFS junit.framework.AssertionFailedError: Expected token END_ELEMENT; got CHARACTERS.)

2018-04-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 Apr 2018 22:32:46 +0300
with message-id <20180411193246.GA15270@localhost>
and subject line Re: Bug#881595: libwoodstox-java: FTBFS 
junit.framework.AssertionFailedError: Expected token END_ELEMENT; got 
CHARACTERS.
has caused the Debian Bug report #881595,
regarding libwoodstox-java: FTBFS junit.framework.AssertionFailedError: 
Expected token END_ELEMENT; got CHARACTERS.
to be marked as done.

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

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


-- 
881595: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881595
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libwoodstox-java
Version: 1:5.0.3-2
Severity: serious
Justification: fails to build from source

Hi,

libwoodstox-java FTBFS in a clean sid+experimental environment:

[ERROR] Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.007 s 
<<< FAILURE! - in wstxtest.stream.TestStreaming
[ERROR] testCDataStreaming(wstxtest.stream.TestStreaming)  Time elapsed: 0.005 
s  <<< FAILURE!
junit.framework.AssertionFailedError: Expected token END_ELEMENT; got 
CHARACTERS.
at 
wstxtest.stream.TestStreaming.testCDataStreaming(TestStreaming.java:97)

[ERROR] Failures: 
[ERROR]   TestStreaming.testCDataStreaming:97->BaseWstxTest.assertTokenType:351 
Expected token END_ELEMENT; got CHARACTERS.
[INFO] 
[ERROR] Tests run: 824, Failures: 1, Errors: 0, Skipped: 0
[INFO] 
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 17.450 s
[INFO] Finished at: 2017-11-12T04:58:17Z
[INFO] Final Memory: 10M/361M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.20.1:test (default-test) on 
project woodstox-core: There are test failures.
[ERROR] 
[ERROR] Please refer to /build/libwoodstox-java-5.0.3/target/surefire-reports 
for the individual test results.
[ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, 
[date].dumpstream and [date]-jvmRun[N].dumpstream.
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
dh_auto_test: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/build/libwoodstox-java-5.0.3 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Ddebian.dir=/build/libwoodstox-java-5.0.3/debian 
-Dmaven.repo.local=/build/libwoodstox-java-5.0.3/debian/maven-repo --batch-mode 
test returned exit code 1
debian/rules:10: recipe for target 'build' failed
make: *** [build] Error 1


Andreas


libwoodstox-java_1%5.0.3-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
On Mon, Nov 13, 2017 at 11:17:01AM +0100, Andreas Beckmann wrote:
> Source: libwoodstox-java
> Version: 1:5.0.3-2
> Severity: serious
> Justification: fails to build from source
> 
> Hi,
> 
> libwoodstox-java FTBFS in a clean sid+experimental environment:
> 
> [ERROR] Tests run: 3, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.007 
> s <<< FAILURE! - in wstxtest.stream.TestStreaming
> [ERROR] testCDataStreaming(wstxtest.stream.TestStreaming)  Time elapsed: 
> 0.005 s  <<< FAILURE!
> junit.framework.AssertionFailedError: Expected token END_ELEMENT; got 
> CHARACTERS.
> at 
> wstxtest.stream.TestStreaming.testCDataStreaming(TestStreaming.java:97)
> 
> [ERROR] Failures: 
> [ERROR]   
> TestStreaming.testCDataStreaming:97->BaseWstxTest.assertTokenType:351 
> Expected token END_ELEMENT; got CHARACTERS.
> [INFO] 
> [ERROR] Tests run: 824, Failures: 1, Errors: 0, Skipped: 0
> [INFO] 
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 17.450 s
> [INFO] Finished at: 2017-11-12T04:58:17Z
> [INFO] Final Memory: 10M/361M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> 

Bug#895464: dnss FTBFS: FAIL: TestEndToEnd

2018-04-11 Thread Adrian Bunk
Source: dnss
Version: 0.0~git20170810.0.860d2af1-1
Severity: serious

Some recent change in unstable makes dnss FTBFS:

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

...
=== RUN   TestEndToEnd
--- FAIL: TestEndToEnd (0.00s)
dnss_test.go:107: error parsing zone: dns: missing TTL with no previous 
value: "A" at line: 1:13



Bug#895463: keyutils FTBFS: Can't Determine Endianness

2018-04-11 Thread Adrian Bunk
Source: keyutils
Version: 1.5.9-9.2
Severity: serious

Some recent change in unstable makes keyutils FTBFS:

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

...
dh_auto_test -- \
PATH=/build/1st/keyutils-1.5.9:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games 
\
LD_LIBRARY_PATH=/build/1st/keyutils-1.5.9 \
SKIPROOT=yes \
SKIPINSTALLED=yes
make -j1 test 
PATH=/build/1st/keyutils-1.5.9:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games 
LD_LIBRARY_PATH=/build/1st/keyutils-1.5.9 SKIPROOT=yes SKIPINSTALLED=yes
make[2]: Entering directory '/build/1st/keyutils-1.5.9'
grep: /etc/rpm/macros.dist: No such file or directory
make -C tests run
make[3]: Entering directory '/build/1st/keyutils-1.5.9/tests'
sh runtest.sh  keyctl/update/userupdate keyctl/update/noargs 
keyctl/update/bad-args keyctl/unlink/valid keyctl/unlink/noargs 
keyctl/unlink/bad-args keyctl/unlink/all keyctl/timeout/valid 
keyctl/timeout/noargs keyctl/timeout/bad-args keyctl/show/valid 
keyctl/show/noargs keyctl/session/valid keyctl/session/bad-args 
keyctl/search/valid keyctl/search/noargs keyctl/search/bad-args 
keyctl/revoke/valid keyctl/revoke/noargs keyctl/revoke/bad-args 
keyctl/requesting/valid keyctl/requesting/piped keyctl/requesting/noargs 
keyctl/requesting/bad-args keyctl/reading/valid keyctl/reading/noargs 
keyctl/reading/bad-args keyctl/pupdate/userupdate keyctl/pupdate/noargs 
keyctl/pupdate/bad-args keyctl/permitting/valid keyctl/permitting/noargs 
keyctl/permitting/bad-args keyctl/padd/useradd keyctl/padd/noargs 
keyctl/padd/bad-args keyctl/noargs keyctl/newring/valid keyctl/newring/noargs 
keyctl/newring/bad-args keyctl/listing/valid keyctl/listing/noargs 
keyctl/listing/bad-args keyctl/link/valid keyctl/link/recursion 
keyctl/link/noargs keyctl/link/bad-args keyctl/invalidate/valid 
keyctl/invalidate/noargs keyctl/invalidate/bad-args keyctl/instantiating/noargs 
keyctl/instantiating/bad-args keyctl/describing/valid keyctl/describing/noargs 
keyctl/describing/bad-args keyctl/clear/valid keyctl/clear/noargs 
keyctl/clear/bad-args keyctl/add/useradd keyctl/add/noargs keyctl/add/bad-args 
bugzillas/bz1033467
 Some tests require root privileges.
 It is recommended that this be run as root.
Running with session keyring RHTS/keyctl/45279
Joined session keyring: 541509331
=== /build/1st/keyutils-1.5.9/tests/keyctl/update/userupdate/test.out ===
+++ Can't Determine Endianness
make[3]: *** [Makefile:42: run] Error 1



Bug#895455: gradle breaks everytime Groovy is upgraded

2018-04-11 Thread Adrian Bunk
Package: gradle
Version: 3.4.1-6
Severity: serious
Control: affects -1 src:triplea src:zeroc-ice src:gradle-propdeps-plugin 
src:groovy src:gradle-jflex-plugin

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gradle-jflex-plugin.html

...
FAILURE: Build failed with an exception.

* What went wrong:
Could not create service of type ClassLoaderRegistry using 
GlobalScopeServices.createClassLoaderRegistry().

* Try:
Run with --debug option to get more log output.

* Exception is:
org.gradle.internal.service.ServiceCreationException: Could not create service 
of type ClassLoaderRegistry using 
GlobalScopeServices.createClassLoaderRegistry().
at 
org.gradle.internal.service.DefaultServiceRegistry$FactoryMethodService.invokeMethod(DefaultServiceRegistry.java:807)
at 
org.gradle.internal.service.DefaultServiceRegistry$FactoryService.create(DefaultServiceRegistry.java:761)
at 
org.gradle.internal.service.DefaultServiceRegistry$ManagedObjectProvider.getInstance(DefaultServiceRegistry.java:598)
at 
org.gradle.internal.service.DefaultServiceRegistry$SingletonService.get(DefaultServiceRegistry.java:643)
at 
org.gradle.internal.service.DefaultServiceRegistry.applyConfigureMethod(DefaultServiceRegistry.java:253)
at 
org.gradle.internal.service.DefaultServiceRegistry.findProviderMethods(DefaultServiceRegistry.java:214)
at 
org.gradle.internal.service.DefaultServiceRegistry.addProvider(DefaultServiceRegistry.java:352)
at 
org.gradle.internal.service.ServiceRegistryBuilder.build(ServiceRegistryBuilder.java:52)
at 
org.gradle.launcher.cli.BuildActionsFactory.createGlobalClientServices(BuildActionsFactory.java:153)
at 
org.gradle.launcher.cli.BuildActionsFactory.runBuildInSingleUseDaemon(BuildActionsFactory.java:141)
at 
org.gradle.launcher.cli.BuildActionsFactory.createAction(BuildActionsFactory.java:89)
at 
org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.createAction(CommandLineActionFactory.java:249)
at 
org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:239)
at 
org.gradle.launcher.cli.CommandLineActionFactory$ParseAndBuildAction.execute(CommandLineActionFactory.java:217)
at 
org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:33)
at 
org.gradle.launcher.cli.JavaRuntimeValidationAction.execute(JavaRuntimeValidationAction.java:24)
at 
org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:33)
at 
org.gradle.launcher.cli.ExceptionReportingAction.execute(ExceptionReportingAction.java:22)
at 
org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:210)
at 
org.gradle.launcher.cli.CommandLineActionFactory$WithLogging.execute(CommandLineActionFactory.java:174)
at org.gradle.launcher.Main.doAction(Main.java:33)
at org.gradle.launcher.bootstrap.EntryPoint.run(EntryPoint.java:45)
at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:564)
at 
org.gradle.launcher.bootstrap.ProcessBootstrap.runNoExit(ProcessBootstrap.java:60)
at 
org.gradle.launcher.bootstrap.ProcessBootstrap.run(ProcessBootstrap.java:37)
at org.gradle.launcher.GradleMain.main(GradleMain.java:23)
Caused by: java.lang.IllegalArgumentException: Cannot find JAR 
'groovy-all-2.4.14.jar' required by module 'gradle-plugins' using classpath or 
distribution directory '/usr/share/gradle'
at 
org.gradle.api.internal.classpath.DefaultModuleRegistry.findDependencyJar(DefaultModuleRegistry.java:233)
at 
org.gradle.api.internal.classpath.DefaultModuleRegistry.findDependencyJars(DefaultModuleRegistry.java:123)
at 
org.gradle.api.internal.classpath.DefaultModuleRegistry.module(DefaultModuleRegistry.java:113)
at 
org.gradle.api.internal.classpath.DefaultModuleRegistry.loadModule(DefaultModuleRegistry.java:89)
at 
org.gradle.api.internal.classpath.DefaultModuleRegistry.getModule(DefaultModuleRegistry.java:77)
at 
org.gradle.api.internal.classpath.DefaultPluginModuleRegistry.getPluginModules(DefaultPluginModuleRegistry.java:39)
at 
org.gradle.api.internal.DynamicModulesClassPathProvider.findClassPath(DynamicModulesClassPathProvider.java:47)
at 
org.gradle.api.internal.DefaultClassPathRegistry.getClassPath(DefaultClassPathRegistry.java:34)
at 
org.gradle.initialization.DefaultClassLoaderRegistry.(DefaultClassLoaderRegistry.java:31)
at 

Processed: gradle breaks everytime Groovy is upgraded

2018-04-11 Thread Debian Bug Tracking System
Processing control commands:

> affects -1 src:triplea src:zeroc-ice src:gradle-propdeps-plugin src:groovy 
> src:gradle-jflex-plugin
Bug #895455 [gradle] gradle breaks everytime Groovy is upgraded
Added indication that 895455 affects src:triplea, src:zeroc-ice, 
src:gradle-propdeps-plugin, src:groovy, and src:gradle-jflex-plugin

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



Bug#895454: osmo-bts FTBFS with libosmocore 0.10.2

2018-04-11 Thread Adrian Bunk
Source: osmo-bts
Version: 0.4.0-3
Severity: serious

https://buildd.debian.org/status/package.php?p=osmo-bts

...
gcc -DHAVE_CONFIG_H -I. -I../..   -I../../include -I/usr/include/osmocom 
-Wdate-time -D_FORTIFY_SOURCE=2 -Wall -I/usr/include/ -I/usr/include/ -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o oml.o oml.c
oml.c:46:30: error: conflicting type qualifiers for 'abis_nm_att_tlvdef_ipa'
 static struct tlv_definition abis_nm_att_tlvdef_ipa = {
  ^~
In file included from oml.c:33:0:
/usr/include/osmocom/gsm/abis_nm.h:42:36: note: previous declaration of 
'abis_nm_att_tlvdef_ipa' was here
 extern const struct tlv_definition abis_nm_att_tlvdef_ipa;
^~
oml.c:373:6: error: nested redefinition of 'enum abis_nm_t200_idx'
 enum abis_nm_t200_idx {
  ^~~~
oml.c:373:6: error: redeclaration of 'enum abis_nm_t200_idx'
In file included from oml.c:32:0:
/usr/include/osmocom/gsm/protocol/gsm_12_21.h:646:6: note: originally defined 
here
 enum abis_nm_t200_idx {
  ^~~~
oml.c:374:2: error: redeclaration of enumerator 'T200_SDCCH'
  T200_SDCCH  = 0,
  ^~
In file included from oml.c:32:0:
/usr/include/osmocom/gsm/protocol/gsm_12_21.h:647:2: note: previous definition 
of 'T200_SDCCH' was here
  T200_SDCCH  = 0,
  ^~
oml.c:375:2: error: redeclaration of enumerator 'T200_FACCH_F'
  T200_FACCH_F  = 1,
  ^~~~
In file included from oml.c:32:0:
/usr/include/osmocom/gsm/protocol/gsm_12_21.h:648:2: note: previous definition 
of 'T200_FACCH_F' was here
  T200_FACCH_F  = 1,
  ^~~~
oml.c:376:2: error: redeclaration of enumerator 'T200_FACCH_H'
  T200_FACCH_H  = 2,
  ^~~~
In file included from oml.c:32:0:
/usr/include/osmocom/gsm/protocol/gsm_12_21.h:649:2: note: previous definition 
of 'T200_FACCH_H' was here
  T200_FACCH_H  = 2,
  ^~~~
oml.c:377:2: error: redeclaration of enumerator 'T200_SACCH_TCH_SAPI0'
  T200_SACCH_TCH_SAPI0 = 3,
  ^~~~
In file included from oml.c:32:0:
/usr/include/osmocom/gsm/protocol/gsm_12_21.h:650:2: note: previous definition 
of 'T200_SACCH_TCH_SAPI0' was here
  T200_SACCH_TCH_SAPI0 = 3,
  ^~~~
oml.c:378:2: error: redeclaration of enumerator 'T200_SACCH_SDCCH'
  T200_SACCH_SDCCH = 4,
  ^~~~
In file included from oml.c:32:0:
/usr/include/osmocom/gsm/protocol/gsm_12_21.h:651:2: note: previous definition 
of 'T200_SACCH_SDCCH' was here
  T200_SACCH_SDCCH = 4,
  ^~~~
oml.c:379:2: error: redeclaration of enumerator 'T200_SDCCH_SAPI3'
  T200_SDCCH_SAPI3 = 5,
  ^~~~
In file included from oml.c:32:0:
/usr/include/osmocom/gsm/protocol/gsm_12_21.h:652:2: note: previous definition 
of 'T200_SDCCH_SAPI3' was here
  T200_SDCCH_SAPI3 = 5,
  ^~~~
oml.c:380:2: error: redeclaration of enumerator 'T200_SACCH_TCH_SAPI3'
  T200_SACCH_TCH_SAPI3 = 6
  ^~~~
In file included from oml.c:32:0:
/usr/include/osmocom/gsm/protocol/gsm_12_21.h:653:2: note: previous definition 
of 'T200_SACCH_TCH_SAPI3' was here
  T200_SACCH_TCH_SAPI3 = 6
  ^~~~
make[4]: *** [Makefile:371: oml.o] Error 1



Processed: tagging 880233

2018-04-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 880233 + stretch
Bug #880233 [src:openbsc] openbsc: FTBFS: | ./openbsc/conftest.c:22: undefined 
reference to `dlopen'
Added tag(s) stretch.
> thanks
Stopping processing here.

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



Bug#895451: firetray FTBFS: No rule to make target 'chrome/skin/icons/linux/hicolor/22x22/apps/firefox.png'

2018-04-11 Thread Adrian Bunk
Source: firetray
Version: 0.6.1+dfsg-1
Severity: serious

Some recent change in unstable makes firetray FTBFS:

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

...
   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/1st/firetray-0.6.1+dfsg'
/usr/bin/make -C src build
make[2]: Entering directory '/build/1st/firetray-0.6.1+dfsg/src'
/bin/dash: 1: git: not found
checking version consistency
checking loglevel
/bin/dash: 1: git: not found
Stripping debug calls from JS file chrome/content/overlay.js
Stripping debug calls from JS file chrome/content/options.js
make[2]: *** No rule to make target 
'chrome/skin/icons/linux/hicolor/22x22/apps/firefox.png', needed by 
'../build-/chrome/skin/icons/linux/hicolor/22x22/apps/firefox.png'.  Stop.
make[2]: Leaving directory '/build/1st/firetray-0.6.1+dfsg/src'
make[1]: *** [debian/rules:6: override_dh_auto_build] Error 2



Bug#895406: marked as done (libopenmpt: CVE-2018-10017)

2018-04-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 Apr 2018 15:51:50 +
with message-id 
and subject line Bug#895406: fixed in libopenmpt 0.3.8-1
has caused the Debian Bug report #895406,
regarding libopenmpt: CVE-2018-10017
to be marked as done.

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

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


-- 
895406: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895406
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libopenmpt
Version: 0.2.7025~beta20.1-1
Severity: grave
Tags: security upstream fixed-upstream

Hi,

libopenmpt 0.3.8 was released with a security update. I requested a CVE
and got CVE-2018-10017 assigned for it (the "[Sec]" line in the changelog).

https://lib.openmpt.org/libopenmpt/2018/04/08/security-updates-0.3.8-0.2-beta31-0.2.7561-beta20.5-p8-0.2.7386-beta20.3-p11/

> libopenmpt 0.3.8 (2018-04-08)
> [Sec] Possible out-of-bounds memory read with IT and MO3 files containing 
> many nested pattern loops (r10028).
> 
> Keep track of active SFx macro during seeking.
> The “note cut” duplicate note action did not volume-ramp the previously 
> playing sample.
> A song starting with non-existing patterns could not be played.
> DSM: Support restart position and 16-bit samples.
> DTM: Import global volume.

Thanks,
James



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: libopenmpt
Source-Version: 0.3.8-1

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

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

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

Debian distribution maintenance software
pp.
James Cowgill  (supplier of updated libopenmpt package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 11 Apr 2018 12:19:51 +0100
Source: libopenmpt
Binary: openmpt123 libopenmpt0 libopenmpt-dev libopenmpt-doc 
libopenmpt-modplug1 libopenmpt-modplug-dev
Architecture: source
Version: 0.3.8-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: James Cowgill 
Description:
 libopenmpt-dev - module music library based on OpenMPT -- development files
 libopenmpt-doc - module music library based on OpenMPT -- documentation
 libopenmpt-modplug-dev - module music library based on OpenMPT -- modplug 
compat developme
 libopenmpt-modplug1 - module music library based on OpenMPT -- modplug compat 
library
 libopenmpt0 - module music library based on OpenMPT -- shared library
 openmpt123 - module music library based on OpenMPT -- music player
Closes: 895406
Changes:
 libopenmpt (0.3.8-1) unstable; urgency=medium
 .
   * New upstream release.
 - Fixes CVE-2018-10017 (Closes: #895406).
 .
   * debian/control:
 - Bump standards version to 4.1.4.
Checksums-Sha1:
 066c5ace56532741c9293309c90330476ca65ccb 2589 libopenmpt_0.3.8-1.dsc
 ec12c7e1552cd29862c9a301d8580657804118df 1410880 libopenmpt_0.3.8.orig.tar.gz
 5b51590321fa7b9e3e0072af5b1d62263f1407d0 12356 libopenmpt_0.3.8-1.debian.tar.xz
 c625f86c287a3ea9ee5bcea86246cd2ff8b60e01 7898 
libopenmpt_0.3.8-1_source.buildinfo
Checksums-Sha256:
 eb4d00af8245d82d46fd01ed550dd42e456896b53ceef292517b02e28a3cc29a 2589 
libopenmpt_0.3.8-1.dsc
 3d46dd0cc217b93976df755f2f633de06a8c30c5c69d74e5f65a136b1c82e905 1410880 
libopenmpt_0.3.8.orig.tar.gz
 37dec7f8fb483b474eb243dab68c8119c323d8b59720733ba30ad072b4304978 12356 
libopenmpt_0.3.8-1.debian.tar.xz
 f315035c4602fb14c968537e963eb3f1af0cb9800bfee3a54cedbe89a8151dda 7898 
libopenmpt_0.3.8-1_source.buildinfo
Files:
 adb16603f114c8f963e429589d9d3d47 2589 libs optional libopenmpt_0.3.8-1.dsc
 423a187791b0409564ac46e17206fd09 1410880 libs optional 
libopenmpt_0.3.8.orig.tar.gz
 957af30f0746d44393464fc1224bd843 12356 libs optional 
libopenmpt_0.3.8-1.debian.tar.xz
 05c9ce793ea44c378bf6ec1d72ffc069 7898 libs optional 
libopenmpt_0.3.8-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEE+Ixt5DaZ6POztUwQx/FnbeotAe8FAlrOKd4UHGpjb3dnaWxs
QGRlYmlhbi5vcmcACgkQx/FnbeotAe/fAw/9EjJRijlPbap3h9j453R9W5MEFyaU

Bug#895448: needs update for dehydrated 0.6

2018-04-11 Thread Daniel Baumann
Package: dehydrated-hook-ddns-tsig
Version: 0.1.2-2
Severity: serious

Hi,

thanks for maintaining dehydrated-hook-ddns-tsig in debian.
unfortunately, since dehydrated 0.6 changed the way hooks are handled,
it doesn't work and needs the following patch (tested, works for me):

  https://github.com/eferdman/dehydrated-hook-ddns-tsig/pull/20

It would be nice if you could cherry-pick that into the debian package.

Regards,
Daniel



Bug#895446: Error in startup script: bad screen distance "4.5"

2018-04-11 Thread Michael Biebl
Package: gitk
Version: 1:2.17.0-1
Severity: grave

gitk no longer successfully starts here. When I run it from a terminal,
I get

$ gitk
Error in startup script: bad screen distance "4.5"
while executing
"$canv conf -scrollregion [list 0 0 $canvxmax $ymax]"
(procedure "setcanvscroll" line 6)
invoked from within
"setcanvscroll"
(procedure "initlayout" line 17)
invoked from within
"initlayout"
(procedure "getcommits" line 4)
invoked from within
"getcommits {}"
(file "/usr/bin/gitk" line 12613)
$ echo $?
1



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

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

Versions of packages gitk depends on:
ii  git  1:2.17.0-1
ii  tk   8.6.0+9

gitk recommends no packages.

Versions of packages gitk suggests:
pn  git-doc  

-- no debconf information



Processed: Re: Bug#894365: fixed in virtualbox 5.2.8-dfsg-6

2018-04-11 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 important
Bug #894365 {Done: Gianfranco Costamagna } 
[src:virtualbox] virtualbox build depends on openjdk-8-jdk-headless
Severity set to 'important' from 'serious'

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



Bug#894365: fixed in virtualbox 5.2.8-dfsg-6

2018-04-11 Thread Gianfranco Costamagna
control: severity -1 important

The bug is fixed, but the new version is entangled with qt transition.
I don't think it makes sense to autoremove it just because of this reason, 
because it is clear that this bug is not happening anymore
and testing will be fine in a matter of days

G.



Bug#894874: A patch is available

2018-04-11 Thread Sunil Mohan Adapa
tag 894874 + patch
thanks

Thanks to Thomas Klute, a patch to fix the problem is now available[1].
I am also attaching a slightly modified patch that I used for testing.
This applies cleanly on the latest version of mod-gnutls in Debian 0.8.2-3.

Please consider making a release with this patch (probably adding
Depends: apache>=2.4.33-1). There is the danger of newer apache2 getting
into testing and breaking all FreedomBox machines.

Links:

1) https://lists.gnupg.org/pipermail/mod_gnutls-devel/2018-April/000206.html

Thank you,

-- 
Sunil
--- a/include/mod_gnutls.h.in
+++ b/include/mod_gnutls.h.in
@@ -293,6 +293,9 @@
  * connections. */
 APR_DECLARE_OPTIONAL_FN(int, ssl_proxy_enable, (conn_rec *));
 APR_DECLARE_OPTIONAL_FN(int, ssl_engine_disable, (conn_rec *));
+APR_DECLARE_OPTIONAL_FN(int, ssl_engine_set, (conn_rec *,
+  ap_conf_vector_t *,
+  int proxy, int enable));
 int ssl_is_https(conn_rec *c);
 int ssl_proxy_enable(conn_rec *c);
 int ssl_engine_disable(conn_rec *c);
--- a/src/gnutls_hooks.c
+++ b/src/gnutls_hooks.c
@@ -21,6 +21,7 @@
 #include "mod_gnutls.h"
 #include "gnutls_cache.h"
 #include "gnutls_ocsp.h"
+#include "gnutls_util.h"
 #include "http_vhost.h"
 #include "ap_mpm.h"
 #include "mod_status.h"
@@ -788,23 +789,11 @@
 
 static void create_gnutls_handle(conn_rec * c)
 {
-/* Get mod_gnutls server configuration */
-mgs_srvconf_rec *sc = (mgs_srvconf_rec *)
-ap_get_module_config(c->base_server->module_config, _module);
-
 _gnutls_log(debug_log_fp, "%s: %d\n", __func__, __LINE__);
 
 /* Get connection specific configuration */
-mgs_handle_t *ctxt = (mgs_handle_t *) ap_get_module_config(c->conn_config, _module);
-if (ctxt == NULL)
-{
-ctxt = apr_pcalloc(c->pool, sizeof (*ctxt));
-ap_set_module_config(c->conn_config, _module, ctxt);
-ctxt->is_proxy = GNUTLS_ENABLED_FALSE;
-}
+mgs_handle_t *ctxt = init_gnutls_ctxt(c);
 ctxt->enabled = GNUTLS_ENABLED_TRUE;
-ctxt->c = c;
-ctxt->sc = sc;
 ctxt->status = 0;
 ctxt->input_rc = APR_SUCCESS;
 ctxt->input_bb = apr_brigade_create(c->pool, c->bucket_alloc);
--- a/src/gnutls_util.c
+++ b/src/gnutls_util.c
@@ -125,3 +125,28 @@
 
 return rv;
 }
+
+
+
+mgs_handle_t *init_gnutls_ctxt(conn_rec *c)
+{
+mgs_handle_t *ctxt = (mgs_handle_t *)
+ap_get_module_config(c->conn_config, _module);
+if (ctxt == NULL)
+{
+ctxt = apr_pcalloc(c->pool, sizeof (*ctxt));
+ap_set_module_config(c->conn_config, _module, ctxt);
+
+/* Get mod_gnutls server configuration */
+mgs_srvconf_rec *sc = (mgs_srvconf_rec *)
+ap_get_module_config(c->base_server->module_config,
+ _module);
+
+/* Set up connection and server references */
+ctxt->c = c;
+ctxt->sc = sc;
+/* Default, unconditionally changed in proxy setup functions */
+ctxt->is_proxy = GNUTLS_ENABLED_FALSE;
+}
+return ctxt;
+}
--- a/src/gnutls_util.h
+++ b/src/gnutls_util.h
@@ -20,6 +20,7 @@
 #include 
 #include 
 #include 
+#include "mod_gnutls.h"
 
 #ifndef __MOD_GNUTLS_UTIL_H__
 #define __MOD_GNUTLS_UTIL_H__
@@ -66,4 +67,10 @@
  gnutls_datum_t *datum)
 __attribute__((nonnull));
 
+/**
+ * Allocate the connection configuration structure if necessary, set
+ * some defaults.
+ */
+mgs_handle_t *init_gnutls_ctxt(conn_rec *c);
+
 #endif /* __MOD_GNUTLS_UTIL_H__ */
--- a/src/mod_gnutls.c
+++ b/src/mod_gnutls.c
@@ -19,11 +19,16 @@
 
 #include "mod_gnutls.h"
 #include "gnutls_ocsp.h"
+#include "gnutls_util.h"
 
 #ifdef APLOG_USE_MODULE
 APLOG_USE_MODULE(gnutls);
 #endif
 
+int ssl_engine_set(conn_rec *c,
+   ap_conf_vector_t *dir_conf __attribute__((unused)),
+   int proxy, int enable);
+
 static void gnutls_hooks(apr_pool_t * p __attribute__((unused)))
 {
 /* Try Run Post-Config Hook After mod_proxy */
@@ -64,6 +69,7 @@
 /* mod_proxy calls these functions */
 APR_REGISTER_OPTIONAL_FN(ssl_proxy_enable);
 APR_REGISTER_OPTIONAL_FN(ssl_engine_disable);
+APR_REGISTER_OPTIONAL_FN(ssl_engine_set);
 
 /* mod_rewrite calls this function to detect HTTPS */
 APR_REGISTER_OPTIONAL_FN(ssl_is_https);
@@ -95,59 +101,55 @@
 return 1;
 }
 
-
-
-int ssl_engine_disable(conn_rec *c)
+/**
+ * In Apache versions from 2.4.33 mod_proxy uses this function to set
+ * up its client connections. Note that mod_gnutls does not (yet)
+ * implement per directory configuration for such connections.
+ *
+ * @param c the connection
+ * @param dir_conf per directory configuration, unused for now
+ * @param proxy Is this a proxy connection?
+ * @param enable Should TLS be enabled on this connection?
+ *
+ * @param `true` (1) if successful, `false` (0) otherwise
+ */
+int ssl_engine_set(conn_rec *c,
+   ap_conf_vector_t *dir_conf 

Processed: A patch is available

2018-04-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tag 894874 + patch
Bug #894874 [src:mod-gnutls] mod-gnutls: FTBFS with Apache 2.4.33-1, reverse 
proxying seems fully broken
Added tag(s) patch.
> thanks
Stopping processing here.

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



Processed: Re: Should be ported from libnm-glib/libnm-gtk to libnm/libnma

2018-04-11 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 serious
Bug #857227 [src:qreator] Should be ported from libnm-glib/libnm-gtk to 
libnm/libnma
Severity set to 'serious' from 'important'

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



Processed: Re: Build-Depends on deprecated libnm-glib/libnm-gtk libraries

2018-04-11 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 serious
Bug #887951 [src:network-manager-strongswan] Build-Depends on deprecated 
libnm-glib/libnm-gtk libraries
Severity set to 'serious' from 'important'

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



Processed: Re: Should be ported from libnm-glib/libnm-gtk to libnm/libnma

2018-04-11 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 serious
Bug #857230 [src:sugar] Should be ported from libnm-glib/libnm-gtk to 
libnm/libnma
Severity set to 'serious' from 'important'

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



Processed: Re: Processed: Re: Processed (with 1 error): Re: libfontconfig1-dev: missing dependency on uuid-dev

2018-04-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> fixed 895391 fontconfig/2.13.0-2
Bug #895391 {Done: Emilio Pozuelo Monfort } 
[libfontconfig1-dev] libfontconfig1-dev: Missing dependency on uuid-dev
Bug #895400 {Done: Emilio Pozuelo Monfort } 
[libfontconfig1-dev] libfontconfig1-dev: missing dependency on uuid-dev
The source fontconfig and version 2.13.0-2 do not appear to match any binary 
packages
Marked as fixed in versions fontconfig/2.13.0-2.
Marked as fixed in versions fontconfig/2.13.0-2.
> thanks
Stopping processing here.

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



Bug#895388: marked as done (Symbol removal prevents upgrade of postgres 9.6 cluster with postgis columns)

2018-04-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 Apr 2018 11:15:34 +
with message-id 
and subject line Bug#895388: fixed in sfcgal 1.3.4-2
has caused the Debian Bug report #895388,
regarding Symbol removal prevents upgrade of postgres 9.6 cluster with postgis 
columns
to be marked as done.

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

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


-- 
895388: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895388
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libsfcgal1
Version: 1.3.3-1
Severity: serious

I have postgresql-9.6-postgis-2.3 installed (no longer in Debian
buster, but was in stretch, current stable). After upgrading libsfcgal1
and trying to use postgis on my existing Postgres 9.6 server, I get an
error when trying to access a table with a geography column:

ari@ari:~ % psql
ari=# \d+
location_order_providers

ERROR:  could not load library
"/usr/lib/postgresql/9.6/lib/postgis-2.3.so":
/usr/lib/x86_64-linux-gnu/libSFCGAL.so.1: undefined symbol:
_ZN4CGAL11NULL_VECTORE


That would be fine if I could upgrade the database to Postgres 10, since
the new postgresql-10-postgis-2.4 package doesn't depend on libsfcgal1,
but I can't do that with the missing symbol:

ari@ari:~ % sudo pg_upgradecluster 9.6 main
Stopping old
cluster...

Disabling connections to the old cluster during
upgrade...

Restarting old cluster with restricted
connections...

Creating new PostgreSQL cluster 10/main .
...
Disabling connections to the new cluster during upgrade...
Roles, databases, schemas, ACLs...
pg_dump: [archiver (db)] query failed: ERROR:  could not load library
"/usr/lib/postgresql/9.6/lib/postgis-2.3.so":
/usr/lib/x86_64-linux-gnu/libSFCGAL.so.1: undefined symbol:
_ZN4CGAL11NULL_VECTORE


If I downgrade libsfcgal1, all of that works fine.


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

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

Versions of packages libsfcgal1 depends on:
ii  libboost-atomic1.62.0   1.62.0+dfsg-5
ii  libboost-chrono1.62.0   1.62.0+dfsg-5
ii  libboost-date-time1.62.01.62.0+dfsg-5
ii  libboost-filesystem1.62.0   1.62.0+dfsg-5
ii  libboost-program-options1.62.0  1.62.0+dfsg-5
ii  libboost-serialization1.62.01.62.0+dfsg-5
ii  libboost-system1.62.0   1.62.0+dfsg-5
ii  libboost-test1.62.0 1.62.0+dfsg-5
ii  libboost-thread1.62.0   1.62.0+dfsg-5
ii  libboost-timer1.62.01.62.0+dfsg-5
ii  libc6   2.27-3
ii  libgcc1 1:8-20180402-1
ii  libgmp102:6.1.2+dfsg-3
ii  libmpfr64.0.1-1
ii  libstdc++6  8-20180402-1

libsfcgal1 recommends no packages.

libsfcgal1 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: sfcgal
Source-Version: 1.3.4-2

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

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

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

Debian distribution maintenance software
pp.
Bas Couwenberg  (supplier of updated sfcgal package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 11 Apr 2018 12:04:16 +0200
Source: sfcgal
Binary: libsfcgal1 libsfcgal-osg1 libsfcgal-dev
Architecture: source amd64
Version: 1.3.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GIS Project 
Changed-By: Bas Couwenberg 
Description:
 libsfcgal-dev - Library for ISO 19107:2013 and OGC SFA 1.2 for 3D operations 
(dev
 libsfcgal-osg1 - Library for ISO 19107:2013 and OGC SFA 1.2 for 3D operations 
(Ope
 libsfcgal1 - Library for ISO 19107:2013 and OGC SFA 1.2 for 3D 

Processed: Re: Processed (with 1 error): Re: libfontconfig1-dev: missing dependency on uuid-dev

2018-04-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 895391 libfontconfig1-dev 2.13.0-1
Bug #895391 {Done: Emilio Pozuelo Monfort } 
[libfontconfig-1-dev] libfontconfig1-dev: Missing dependency on uuid-dev
Warning: Unknown package 'libfontconfig-1-dev'
Bug reassigned from package 'libfontconfig-1-dev' to 'libfontconfig1-dev'.
No longer marked as found in versions 2.13.0-1.
No longer marked as fixed in versions fontconfig/2.13.0-2.
Bug #895391 {Done: Emilio Pozuelo Monfort } 
[libfontconfig1-dev] libfontconfig1-dev: Missing dependency on uuid-dev
Marked as found in versions fontconfig/2.13.0-1.
> forcemerge 895391 895400
Bug #895391 {Done: Emilio Pozuelo Monfort } 
[libfontconfig1-dev] libfontconfig1-dev: Missing dependency on uuid-dev
Bug #895400 [libfontconfig1-dev] libfontconfig1-dev: missing dependency on 
uuid-dev
Severity set to 'grave' from 'serious'
Marked Bug as done
Removed indication that 895400 affects src:zenity, src:evolution, and 
src:libdazzle
Merged 895391 895400
> thanks
Stopping processing here.

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



Bug#895400: libfontconfig1-dev: missing dependency on uuid-dev

2018-04-11 Thread James Cowgill
Control: forcemerge 895391 -1

Hi,

On Wed, 11 Apr 2018 10:22:48 +0300 Adrian Bunk  wrote:
> Package: libfontconfig1-dev
> Version: 2.13.0-1
> Severity: serious
> Control: affects -1 src:libdazzle src:zenity src:evolution
> 
> $ pkg-config --cflags fontconfig
> Package uuid was not found in the pkg-config search path.
> Perhaps you should add the directory containing `uuid.pc'
> to the PKG_CONFIG_PATH environment variable
> Package 'uuid', required by 'fontconfig', not found

Duplicate of #895391 (which was fixed a few hours ago).

James



signature.asc
Description: OpenPGP digital signature


Processed (with 1 error): Re: libfontconfig1-dev: missing dependency on uuid-dev

2018-04-11 Thread Debian Bug Tracking System
Processing control commands:

> forcemerge 895391 -1
Bug #895391 {Done: Emilio Pozuelo Monfort } 
[libfontconfig-1-dev] libfontconfig1-dev: Missing dependency on uuid-dev
Warning: Unknown package 'libfontconfig-1-dev'
Unable to merge bugs because:
package of #895400 is 'libfontconfig1-dev' not 'libfontconfig-1-dev'
Warning: Unknown package 'libfontconfig-1-dev'
Failed to forcibly merge 895391: Did not alter merged bugs.


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



Bug#894560: marked as done (pygame: Don't drop python2 package)

2018-04-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 Apr 2018 10:13:27 +
with message-id 
and subject line Bug#894560: fixed in pygame 1.9.3+dfsg2-2
has caused the Debian Bug report #894560,
regarding pygame: Don't drop python2 package
to be marked as done.

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

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


-- 
894560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894560
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pygame
Version: 1.9.3+dfsg2-1
Severity: serious
X-Debbugs-CC:naturesha...@debian.org

Your latest upload drops the python-pygame pacakge but I count 35
packages in Debian Testing that depend on it. Please restore the
python-pygame package until all those packages no longer depend on it.

Even without a bug being filed, I believe the broken dependency issue
would have prevented this package from migrating to Testing.

Thanks,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: pygame
Source-Version: 1.9.3+dfsg2-2

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

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

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

Debian distribution maintenance software
pp.
Dominik George  (supplier of updated pygame package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 11 Apr 2018 11:02:05 +0200
Source: pygame
Binary: python-pygame python3-pygame python-pygame-doc
Architecture: source amd64 all
Version: 1.9.3+dfsg2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Dominik George 
Description:
 python-pygame - SDL bindings for games development (Python 2)
 python-pygame-doc - SDL bindings for games development in Python 
(documentation)
 python3-pygame - SDL bindings for games development (Python 3)
Closes: 861254 892436 894560
Changes:
 pygame (1.9.3+dfsg2-2) unstable; urgency=medium
 .
   * Bring back Python 2 version for now. (Closes: #894560)
   * Amend last changelog with missing bug number.
   * Refresh a patch to fix clean step.
   * Use pkg-config to find freetype. (Closes: #892436)
   * Fix installation of documentation into correct directory.
   * Bump Standards-Version (no changes needed).
   * Fix tests on FreeBSD (and probably others). (Closes: #861254)
Checksums-Sha1:
 0c4018018f9ebf3497c96f9f6118d2d224aafae7 2808 pygame_1.9.3+dfsg2-2.dsc
 5e4c032e09bfc9226b05f20a77f8866583dd2d1b 26064 
pygame_1.9.3+dfsg2-2.debian.tar.xz
 bfb7947dde0cb63d049537f0d8d88b13f6de45b9 15124 
pygame_1.9.3+dfsg2-2_amd64.buildinfo
 607adeb352edc1fdeb23cd727bd85e6c2b0de202 1072164 
python-pygame-dbgsym_1.9.3+dfsg2-2_amd64.deb
 c48309d5813b3707e458beb5ade0bbb3a712d683 1576628 
python-pygame-doc_1.9.3+dfsg2-2_all.deb
 7779e93ff9f34a70e741b89c2f37025b70a87f90 579356 
python-pygame_1.9.3+dfsg2-2_amd64.deb
 88b6a2904bfa6c0d78525a9497010862ad6d0679 1154996 
python3-pygame-dbgsym_1.9.3+dfsg2-2_amd64.deb
 dd16ecde3cb86eb0e02af66e280cb70df1d5816e 580564 
python3-pygame_1.9.3+dfsg2-2_amd64.deb
Checksums-Sha256:
 46f5dc2806d7b7dcf81d068f3d289c65ee37fbb9f890a61d46514e248be993d1 2808 
pygame_1.9.3+dfsg2-2.dsc
 f1d9f583746e5d9432a877db694167cd3f5515fce8a42999e012c9311439c057 26064 
pygame_1.9.3+dfsg2-2.debian.tar.xz
 0e6b4a3c3d5a2540f6cc1fd08db82dd6ea457474ee5fc9364d364e6fec3884fc 15124 
pygame_1.9.3+dfsg2-2_amd64.buildinfo
 9e508c8725dd97904fca0de5c0bd4702992cfa229ab0269c0ca4709c52894c9d 1072164 
python-pygame-dbgsym_1.9.3+dfsg2-2_amd64.deb
 9cf17db3a07b01fbee4ea354957d50fab0fad68d244be65db5c98be52ffc328f 1576628 
python-pygame-doc_1.9.3+dfsg2-2_all.deb
 af819f12e479ed9a18232ed0b773f085bb8144da15192f3f574ed2dbb17a3c25 579356 
python-pygame_1.9.3+dfsg2-2_amd64.deb
 b82fa51731536d87fe88f1d39991c48bcd53afda71269c1345b4aa83bdc59559 1154996 
python3-pygame-dbgsym_1.9.3+dfsg2-2_amd64.deb
 93bffebf27a972c3fbe1b5b146315d38e91fbf3fa1cde3a4e3094df7394c686e 580564 
python3-pygame_1.9.3+dfsg2-2_amd64.deb
Files:
 aee29dcb35df332cc547804bef134779 2808 python optional pygame_1.9.3+dfsg2-2.dsc
 f15445268065b016bbd962c09d7ffa48 26064 python optional 

Bug#894313: marked as done (etherape: Crashes on startup)

2018-04-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 Apr 2018 10:07:04 +
with message-id 
and subject line Bug#894313: fixed in etherape 0.9.17-1
has caused the Debian Bug report #894313,
regarding etherape: Crashes on startup
to be marked as done.

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

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


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

Dear Maintainer,

I'm trying to start etherape, but it crashes with this error:

% etherape

(etherape:32196): libglade-WARNING **: Could not load support for `gnome': 
libgnome.so: cannot open shared object file: No such file or directory

(etherape:32196): libglade-WARNING **: unknown widget class 'GnomeCanvas'

(etherape:32196): Gtk-WARNING **: gtk_scrolled_window_add(): cannot add non 
scrollable widget use gtk_scrolled_window_add_with_viewport() instead
EtherApe-INFO: sctp protocol not supported
EtherApe-INFO: ddp protocol not supported
EtherApe-INFO: ddp protocol not supported
EtherApe-INFO: ddp protocol not supported
EtherApe-INFO: ddp protocol not supported

(etherape:32196): GLib-GObject-WARNING **: invalid cast from 'GtkLabel' to 
'GnomeCanvas'

(etherape:32196): GnomeCanvas-CRITICAL **: gnome_canvas_root: assertion 
'GNOME_IS_CANVAS (canvas)' failed

(etherape:32196): GnomeCanvas-CRITICAL **: gnome_canvas_item_new: assertion 
'GNOME_IS_CANVAS_GROUP (parent)' failed
**
ERROR:diagram.c:250:addref_canvas_obj: assertion failed: (obj)
zsh: abort  etherape
% unexpected EOF in read_all()
critical: read_all() failed on control socket

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

Kernel: Linux 4.15.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages etherape depends on:
ii  etherape-data0.9.16-1
ii  libart-2.0-2 2.3.21-3
ii  libatk1.0-0  2.26.1-3
ii  libc-ares2   1.14.0-1
ii  libc62.27-1
ii  libcairo21.15.10-2
ii  libfontconfig1   2.12.6-0.1
ii  libfreetype6 2.8.1-2
ii  libgdk-pixbuf2.0-0   2.36.11-1
ii  libglade2-0  1:2.6.4-2+b1
ii  libglib2.0-0 2.54.3-2
ii  libgnomecanvas2-02.30.3-3
ii  libgtk2.0-0  2.24.32-1
ii  libpango-1.0-0   1.40.14-1
ii  libpangocairo-1.0-0  1.40.14-1
ii  libpangoft2-1.0-01.40.14-1
ii  libpcap0.8   1.8.1-6
ii  libpopt0 1.16-10+b2
ii  libxml2  2.9.4+dfsg1-6.1

etherape recommends no packages.

etherape suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: etherape
Source-Version: 0.9.17-1

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

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

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

Debian distribution maintenance software
pp.
Patrick Matthäi  (supplier of updated etherape package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 11 Apr 2018 11:13:48 +0200
Source: etherape
Binary: etherape etherape-data
Architecture: source all amd64
Version: 0.9.17-1
Distribution: unstable
Urgency: high
Maintainer: Patrick Matthäi 
Changed-By: Patrick Matthäi 
Description:
 etherape   - graphical network monitor
 etherape-data - graphical network monitor (data files)
Closes: 894313
Changes:
 etherape (0.9.17-1) unstable; urgency=high
 .
   * New upstream release.
 - Fixes loading of gnomecanvas on startup.
   Closes: #894313
   * Bump Standards-Version to 4.1.4.
   * Move source.lintian-overrides file to the source subfolder.
   * Fix renamed lintian tag.
Checksums-Sha1:
 113243d05a633bd9c302d8d5c2f071346d161db7 1891 etherape_0.9.17-1.dsc
 fe18ad889788e1105c9966b4eb18e3ec85e748a5 1436276 etherape_0.9.17.orig.tar.gz
 

Bug#895411: anki: Anki raises exception instead of starting (Exception: Qt 5.10 is known to be buggy.)

2018-04-11 Thread Matthias Wimmer
Package: anki
Version: 2.1.0+dfsg~b37-1
Severity: grave
Justification: renders package unusable

I cannot start anki anymore. When starting it from the command line, I get the
following message:

Traceback (most recent call last):
  File "/usr/bin/anki", line 6, in 
import aqt
  File "/usr/share/anki/aqt/__init__.py", line 14, in 
from aqt.qt import *
  File "/usr/share/anki/aqt/qt.py", line 44, in 
raise Exception("Qt 5.10 is known to be buggy.")
Exception: Qt 5.10 is known to be buggy.


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

Kernel: Linux 4.15.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=zh_TW.UTF-8, LC_CTYPE=zh_TW.UTF-8 (charmap=UTF-8), 
LANGUAGE=zh_TW.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages anki depends on:
ii  libjs-jquery3.2.1-1
ii  libjs-jquery-flot   0.8.3+dfsg-1
ii  libjs-jquery-ui 1.12.1+dfsg-5
ii  libjs-mathjax   2.7.3+dfsg-1
ii  python3 3.6.5-2
ii  python3-bs4 4.6.0-1
ii  python3-decorator   4.1.2-1
ii  python3-markdown2.6.9-1
ii  python3-pyaudio 0.2.11-1+b1
ii  python3-pyqt5   5.9.2+dfsg-1+b1
ii  python3-pyqt5.qtwebchannel  5.9.2+dfsg-1+b1
ii  python3-pyqt5.qtwebengine   5.9.2+dfsg-1+b1
ii  python3-requests2.18.4-2
ii  python3-send2trash  1.4.2-2

Versions of packages anki recommends:
ii  python3-matplotlib  2.1.1-2

Versions of packages anki suggests:
pn  dvipng   
pn  lame 
ii  mplayer  2:1.3.0-7+b3

-- no debconf information



Bug#889704: marked as done (runc FTBFS: kill.go:44:12: undefined: unix.SIGUNUSED)

2018-04-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 Apr 2018 09:34:20 +
with message-id 
and subject line Bug#889704: fixed in runc 1.0.0~rc4+dfsg1-6
has caused the Debian Bug report #889704,
regarding runc FTBFS: kill.go:44:12: undefined: unix.SIGUNUSED
to be marked as done.

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

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


-- 
889704: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889704
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: runc
Version: 1.0.0~rc4+dfsg1-5
Severity: serious

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

...
github.com/urfave/cli
github.com/opencontainers/runc
# github.com/opencontainers/runc
src/github.com/opencontainers/runc/kill.go:44:12: undefined: unix.SIGUNUSED
github.com/opencontainers/runc/contrib/cmd/recvtty
github.com/opencontainers/runc/libcontainer/devices
github.com/opencontainers/runc/libcontainer/integration
github.com/opencontainers/runc/libcontainer/xattr
dh_auto_build: cd _build && go install 
-gcflags=\"-trimpath=/<>/runc-1.0.0\~rc4\+dfsg1/_build/src\" 
-asmflags=\"-trimpath=/<>/runc-1.0.0\~rc4\+dfsg1/_build/src\" -v -p 1 
-tags "apparmor seccomp" github.com/opencontainers/runc 
github.com/opencontainers/runc/contrib/cmd/recvtty 
github.com/opencontainers/runc/libcontainer 
github.com/opencontainers/runc/libcontainer/apparmor 
github.com/opencontainers/runc/libcontainer/cgroups 
github.com/opencontainers/runc/libcontainer/cgroups/fs 
github.com/opencontainers/runc/libcontainer/cgroups/rootless 
github.com/opencontainers/runc/libcontainer/cgroups/systemd 
github.com/opencontainers/runc/libcontainer/configs 
github.com/opencontainers/runc/libcontainer/configs/validate 
github.com/opencontainers/runc/libcontainer/criurpc 
github.com/opencontainers/runc/libcontainer/devices 
github.com/opencontainers/runc/libcontainer/integration 
github.com/opencontainers/runc/libcontainer/keys 
github.com/opencontainers/runc/libcontainer/nsenter gi
 thub.com/opencontainers/runc/libcontainer/seccomp 
github.com/opencontainers/runc/libcontainer/specconv 
github.com/opencontainers/runc/libcontainer/stacktrace 
github.com/opencontainers/runc/libcontainer/system 
github.com/opencontainers/runc/libcontainer/user 
github.com/opencontainers/runc/libcontainer/utils 
github.com/opencontainers/runc/libcontainer/xattr returned exit code 2
debian/rules:36: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
--- End Message ---
--- Begin Message ---
Source: runc
Source-Version: 1.0.0~rc4+dfsg1-6

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

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

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

Debian distribution maintenance software
pp.
Balint Reczey  (supplier of updated runc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 10 Apr 2018 18:40:56 +0200
Source: runc
Binary: runc golang-github-opencontainers-runc-dev
Architecture: source
Version: 1.0.0~rc4+dfsg1-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 

Changed-By: Balint Reczey 
Description:
 golang-github-opencontainers-runc-dev - Open Container Project - development 
files
 runc   - Open Container Project - runtime
Closes: 889704
Changes:
 runc (1.0.0~rc4+dfsg1-6) unstable; urgency=medium
 .
   [ Michael Stapelberg ]
   * update debian/gitlab-ci.yml (using salsa.debian.org/go-team/ci/cmd/ci)
 .
   [ Dmitry Smirnov ]
   * Removed myself from uploaders.
 .
   [ Balint Reczey ]
   * Team upload
   * Stop using unix.SIGUNUSED which has been removed from golang.org/x/sys
 (Closes: #889704)
Checksums-Sha1:
 70949e1fdecfb2ce6403176440ac75c296802b19 2735 runc_1.0.0~rc4+dfsg1-6.dsc
 eeabb7ff6761830892efa8c6f981b892225f1201 6096 
runc_1.0.0~rc4+dfsg1-6.debian.tar.xz
 b7b5bdc0aa022ebf8c96a0e9b0756c12a586fc7f 7156 
runc_1.0.0~rc4+dfsg1-6_source.buildinfo
Checksums-Sha256:
 f7383194d84ffc27404f497e3fb2d7e5fba6ab982c079260aa75cf9d68fad6f4 2735 
runc_1.0.0~rc4+dfsg1-6.dsc
 

Bug#895391: marked as done (libfontconfig1-dev: Missing dependency on uuid-dev)

2018-04-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 Apr 2018 09:22:45 +
with message-id 
and subject line Bug#895391: fixed in fontconfig 2.13.0-2
has caused the Debian Bug report #895391,
regarding libfontconfig1-dev: Missing dependency on uuid-dev
to be marked as done.

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

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


-- 
895391: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895391
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libfontconfig-1dev
Version: 2.13.0-1
Severity: grave
X-Debbugs-CC: po...@debian.org

According to its pkgconfig file, libfontconfig1-dev needs to depend on
uuid-dev. This is causing other packages to FTBFS. First seen on arm64
with evolution, libdazzle, webkit2gtk, zenity, etc.

Thanks,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: fontconfig
Source-Version: 2.13.0-2

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

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

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

Debian distribution maintenance software
pp.
Emilio Pozuelo Monfort  (supplier of updated fontconfig 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 11 Apr 2018 09:12:46 +0200
Source: fontconfig
Binary: fontconfig fontconfig-config fontconfig-udeb libfontconfig1-dev 
libfontconfig1
Architecture: source
Version: 2.13.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian freedesktop.org maintainers 

Changed-By: Emilio Pozuelo Monfort 
Description:
 fontconfig - generic font configuration library - support binaries
 fontconfig-config - generic font configuration library - configuration
 fontconfig-udeb - generic font configuration library - minimal runtime (udeb)
 libfontconfig1 - generic font configuration library - runtime
 libfontconfig1-dev - generic font configuration library - development
Closes: 895391
Changes:
 fontconfig (2.13.0-2) unstable; urgency=medium
 .
   * debian/control: let libfontconfig1-dev depend on uuid-dev.
 Closes: #895391.
   * Add myself to Uploaders.
Checksums-Sha1:
 c105d40653bc1329467f09c06fedd028145101f3 2520 fontconfig_2.13.0-2.dsc
 b7bcc5d47211b7bbac35bb221860407db3601f5b 1700500 fontconfig_2.13.0.orig.tar.bz2
 7e19a54fa7d0db4298820e2e67fc557a9c32079b 49820 
fontconfig_2.13.0-2.debian.tar.xz
 5de22559a719dc6ad13485f28c0d7368324db557 5603 
fontconfig_2.13.0-2_source.buildinfo
Checksums-Sha256:
 eea35db2d4dfd126935e16c127cd7ce7ff3977b82b67842ca08e936d5ee8ef04 2520 
fontconfig_2.13.0-2.dsc
 91dde8492155b7f34bb95079e79be92f1df353fcc682c19be90762fd3e12eeb9 1700500 
fontconfig_2.13.0.orig.tar.bz2
 9c9440cb4ec28263f5a351ccf91820debd2c7b9ece3df257caeab4eff5863c6f 49820 
fontconfig_2.13.0-2.debian.tar.xz
 2f24c8cd143051703f60de04a6df2e10acc3183f43ae34fe28713faceb59ea95 5603 
fontconfig_2.13.0-2_source.buildinfo
Files:
 fc900489651365ad7c5726b2bad3e0c9 2520 fonts optional fontconfig_2.13.0-2.dsc
 60d2394a79d3b2e5db2daea55193fa47 1700500 fonts optional 
fontconfig_2.13.0.orig.tar.bz2
 5d5c5d6424bf4d841fe22e2de63d91e0 49820 fonts optional 
fontconfig_2.13.0-2.debian.tar.xz
 2ebba3ad00ab74adfc20deecf39b703a 5603 fonts optional 
fontconfig_2.13.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEcJymx+vmJZxd92Q+nUbEiOQ2gwIFAlrNtYIACgkQnUbEiOQ2
gwIkqw/+KDzbL9wF4Aw8+y0R0ZwsIKukbiorEe0758kD/4M4QZPHjaM/Br+p+gNQ
PRVoKq7EHEisHdu3NRFs8WezjPdxvmudPHi7w2DgUVno+Mytlv5a8VkHNyzB4j5z
U+4yeNSf+XhN3AEObvRX4ICrqUTseWAxFK7AGCVtljlUJ6C0SFwJZTyAYA2C4AXa
k+bXfCjyW7IU7Cul6RUMyBUReiZvP0I3J9TEeXiFBH44sOqBSHNxhMiFju60qmFH
OtZYrDFqa70bBCcWw9uvpt7cLS7IOETESxDorBaMMDLznYMch5KoDUnfeGc5pbzP
k0O1x6fnisu30qx0ZNGetK06YYcVSJ/C6XjWv0M1k56YfR9v5iTHSsgkvKQL4wTn
W3W60q587ELggVyAQmPwk6x0sgLe4E+b9fJGrilXYEoU1cvxfWvalaGTNAUxx+wT
z0TG8rZuKolKDIPxbsXqX8iM442eLNdxar6InLeVZms6HC70qfD78uekJ7jgxndE
TcQo//Q3iJca1xa/+VT4JFSItQT4uphcFnWM8pfaEUIOf/KtaVJDDuVkzpXSjx2U
cDz2NEi20FGDfPWyc92C+w6qsMDSnoljm6CTQgUgF6pVnFHoTBj159U3gs+Lbe7f
dmI2RPKtgsRfaCmVPJZ0fbZ9feSWAMST2XhnCVYy0s5SfvR72gg=
=YPXI
-END PGP SIGNATURE End Message ---


Bug#895406: libopenmpt: CVE-2018-10017

2018-04-11 Thread James Cowgill
Source: libopenmpt
Version: 0.2.7025~beta20.1-1
Severity: grave
Tags: security upstream fixed-upstream

Hi,

libopenmpt 0.3.8 was released with a security update. I requested a CVE
and got CVE-2018-10017 assigned for it (the "[Sec]" line in the changelog).

https://lib.openmpt.org/libopenmpt/2018/04/08/security-updates-0.3.8-0.2-beta31-0.2.7561-beta20.5-p8-0.2.7386-beta20.3-p11/

> libopenmpt 0.3.8 (2018-04-08)
> [Sec] Possible out-of-bounds memory read with IT and MO3 files containing 
> many nested pattern loops (r10028).
> 
> Keep track of active SFx macro during seeking.
> The “note cut” duplicate note action did not volume-ramp the previously 
> playing sample.
> A song starting with non-existing patterns could not be played.
> DSM: Support restart position and 16-bit samples.
> DTM: Import global volume.

Thanks,
James



signature.asc
Description: OpenPGP digital signature


Bug#895404: nfs-kernel-server: NFS server stops accepting mount request / mounted NFS directories became inaccecible on client

2018-04-11 Thread superuser
Package: nfs-kernel-server
Version: 1:1.3.4-2.1
Severity: critical
Justification: causes serious data loss

Dear Maintainer,

NFS directory exported for local network host, and mounted by client.
After few days normal workload that share on client side became
inaccessible.
syslog on client side shows:  nfs: server  not responding,
still trying
Tried to mount that share from NFS-server itself but it hangs for
timeout value(5 min) and report about that:
$ mount.nfs: Connection timed out

Tried to restart nfs-kernel-server.service but it is not gives any
positive result. Tried to kill nfsd processed by -9 and PID but it does
not kills any of them. journalctl show nothing suspicious.
Problem get resolved only after reboot of the server each time.

Changing kernel to one from backport repository did not helped.


-- Package-specific info:
-- rpcinfo --
   program vers proto   port  service
104   tcp111  portmapper
103   tcp111  portmapper
102   tcp111  portmapper
104   udp111  portmapper
103   udp111  portmapper
102   udp111  portmapper
151   udp  42805  mountd
151   tcp  42241  mountd
152   udp  44844  mountd
152   tcp  51819  mountd
153   udp  52308  mountd
153   tcp  54731  mountd
133   tcp   2049  nfs
1002273   tcp   2049
133   udp   2049  nfs
1002273   udp   2049
1000211   udp  46342  nlockmgr
1000213   udp  46342  nlockmgr
1000214   udp  46342  nlockmgr
1000211   tcp  41403  nlockmgr
1000213   tcp  41403  nlockmgr
1000214   tcp  41403  nlockmgr
-- /etc/default/nfs-kernel-server --
RPCNFSDCOUNT=8
RPCNFSDPRIORITY=0
RPCMOUNTDOPTS="--manage-gids --no-nfs-version 4"
RPCNFSDOPTS="--no-nfs-version 4"
NEED_SVCGSSD=""
RPCSVCGSSDOPTS=""
-- /etc/exports --
/srv/backups   10.196.1.224/27(rw,sync,no_subtree_check)
-- /proc/fs/nfs/exports --
# Version 1.1
# Path Client(Flags) # IPs

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

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

Versions of packages nfs-kernel-server depends on:
ii  init-system-helpers  1.48
ii  keyutils 1.5.9-9
ii  libblkid12.29.2-1+deb9u1
ii  libc62.24-11+deb9u3
ii  libcap2  1:2.25-1
ii  libsqlite3-0 3.16.2-5+deb9u1
ii  libtirpc10.2.5-1.2
ii  libwrap0 7.6.q-26
ii  lsb-base 9.20161125
ii  netbase  5.4
ii  nfs-common   1:1.3.4-2.1
ii  ucf  3.0036

nfs-kernel-server recommends no packages.

nfs-kernel-server suggests no packages.

-- no debconf information



Bug#895400: libfontconfig1-dev: missing dependency on uuid-dev

2018-04-11 Thread Adrian Bunk
Package: libfontconfig1-dev
Version: 2.13.0-1
Severity: serious
Control: affects -1 src:libdazzle src:zenity src:evolution

$ pkg-config --cflags fontconfig
Package uuid was not found in the pkg-config search path.
Perhaps you should add the directory containing `uuid.pc'
to the PKG_CONFIG_PATH environment variable
Package 'uuid', required by 'fontconfig', not found

$



Processed: libfontconfig1-dev: missing dependency on uuid-dev

2018-04-11 Thread Debian Bug Tracking System
Processing control commands:

> affects -1 src:libdazzle src:zenity src:evolution
Bug #895400 [libfontconfig1-dev] libfontconfig1-dev: missing dependency on 
uuid-dev
Added indication that 895400 affects src:libdazzle, src:zenity, and 
src:evolution

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



Bug#895388: Symbol removal prevents upgrade of postgres 9.6 cluster with postgis columns

2018-04-11 Thread Adrian Bunk
On Wed, Apr 11, 2018 at 09:43:59AM +0300, Adrian Bunk wrote:
> Control: reopen -1
> Control: severity -1 serious
> 
> On Wed, Apr 11, 2018 at 07:04:40AM +0200, Sebastiaan Couwenberg wrote:
> > severity 895388 normal
> > tags 895388 wontfix
> > thanks
> > 
> > On 04/10/2018 11:30 PM, Ari Pollak wrote:
> > > I have postgresql-9.6-postgis-2.3 installed (no longer in Debian
> > > buster, but was in stretch, current stable). After upgrading libsfcgal1
> > > and trying to use postgis on my existing Postgres 9.6 server, I get an
> > > error when trying to access a table with a geography column:
> > > 
> > > [...]
> > > 
> > > That would be fine if I could upgrade the database to Postgres 10, since
> > > the new postgresql-10-postgis-2.4 package doesn't depend on libsfcgal1,
> > > but I can't do that with the missing symbol:
> > > 
> > > [...]
> > > 
> > > If I downgrade libsfcgal1, all of that works fine.
> > 
> > Upgrading postgis databases is not supported by the Debian package. You
> > need to recreate the postgis databases, or use the symlink hacks.
> 
> This bug is not about postgis databases, it is about a broken library.
> 
> > The postgis package in unstable will be rebuilt with the new sfcgal once
> > that migrates to testing.
> 
> Does that work for you?
> 
> I would expect linking to fail due to this bug.

I think I'm wrong on the latter:
As a plugin it would link but fail with the same error when trying to 
use it.

Either way, SFCGAL no longer linked with CGAL is a pretty fatal bug.

cu
Adrian

-- 

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



Processed: Re: Bug#895397: josm: fails to start

2018-04-11 Thread Debian Bug Tracking System
Processing control commands:

> severity -1 important
Bug #895397 [josm] josm: fails to start
Severity set to 'important' from 'grave'
> tags -1 moreinfo unreproducible
Bug #895397 [josm] josm: fails to start
Added tag(s) unreproducible and moreinfo.

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



Bug#895397: josm: fails to start

2018-04-11 Thread Bas Couwenberg

Control: severity -1 important
Control: tags -1 moreinfo unreproducible

On 2018-04-11 08:09, patrick noll wrote:

JOSM fails when trying to launch from menu or cli and returns pop up
with following info:


I cannot reproduce this issue, josm works as expected on my system.

Ensure that you have configured openjdk-9 as the default:

 update-java-alternatives -s java-1.9.0-openjdk-amd64

If the issue persists try starting josm with a clean profile:

 JAVA_OPTS="-Djosm.home=${HOME}/.josm-new-home" josm

If that works, there is probably a plugin, setting or other file in your 
JOSM directory that breaks the new version.


Kind Regards,

Bas



Processed: Re: Bug#895388: Symbol removal prevents upgrade of postgres 9.6 cluster with postgis columns

2018-04-11 Thread Debian Bug Tracking System
Processing control commands:

> reopen -1
Bug #895388 {Done: Sebastiaan Couwenberg } [libsfcgal1] 
Symbol removal prevents upgrade of postgres 9.6 cluster with postgis columns
Bug reopened
Ignoring request to alter fixed versions of bug #895388 to the same values 
previously set
> severity -1 serious
Bug #895388 [libsfcgal1] Symbol removal prevents upgrade of postgres 9.6 
cluster with postgis columns
Severity set to 'serious' from 'normal'

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



Bug#855157: mugshot: diff for NMU version 0.3.1-1.2

2018-04-11 Thread Adrian Bunk
Dear maintainer,

I've uploaded the attached NMU to fix the FTBFS caused by recent change 
in the python packaging.

cu
Adrian

-- 

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

diff -Nru mugshot-0.3.1/debian/changelog mugshot-0.3.1/debian/changelog
--- mugshot-0.3.1/debian/changelog	2018-04-08 15:46:42.0 +0300
+++ mugshot-0.3.1/debian/changelog	2018-04-11 08:58:48.0 +0300
@@ -1,3 +1,11 @@
+mugshot (0.3.1-1.2) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Build-depend on dh-python and python3-distutils,
+required after recent python3 packaging changes.
+
+ -- Adrian Bunk   Wed, 11 Apr 2018 08:58:48 +0300
+
 mugshot (0.3.1-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru mugshot-0.3.1/debian/control mugshot-0.3.1/debian/control
--- mugshot-0.3.1/debian/control	2018-04-08 15:46:42.0 +0300
+++ mugshot-0.3.1/debian/control	2018-04-11 08:58:48.0 +0300
@@ -5,7 +5,8 @@
 Uploaders:
  Jackson Doak ,
  Sean Davis 
-Build-Depends: debhelper (>= 9), python3, python3-distutils-extra,
+Build-Depends: debhelper (>= 9), dh-python, python3,
+ python3-distutils, python3-distutils-extra,
  python3-pexpect, python3-dbus, python3-gi, gir1.2-gtk-3.0
 Standards-Version: 3.9.8
 Homepage: https://launchpad.net/mugshot


Bug#895397: josm: fails to start

2018-04-11 Thread patrick noll
Package: josm
Version: 0.0.svn13576+dfsg-3
Severity: grave
Justification: renders package unusable

Dear Maintainer,

JOSM fails when trying to launch from menu or cli and returns pop up with 
following info:

{{{
Revision:13576
Is-Local-Build:false
Build-Date:2018-04-03 18:33:05
Debian-Release:0.0.svn13576+dfsg-3
Build-Name:Debian

Identification: JOSM/1.5 (13576 Debian en) Linux Debian GNU/Linux testing 
(buster)
Memory Usage: 250 MB / 3984 MB (215 MB allocated, but free)
Java version: 9.0.4+12-Debian-4, Oracle Corporation, OpenJDK 64-Bit Server VM
Screen: :0.0 1600x900, :0.1 1920x1080, :0.2 1920x1080
Maximum Screen Size: 1920x1080
Java package: openjdk-9-jre:amd64-9.0.4+12-4
Java ATK Wrapper package: libatk-wrapper-java:all-0.33.3-20
VM arguments: [-Djosm.restart=true, -Djava.net.useSystemProxies=true]

Plugins:
+ Mapillary
+ apache-commons
+ apache-http
+ buildings_tools
+ ejml
+ ext_tools
+ geotools
+ jogl
+ jts
+ kendzi3d
+ kendzi3d-resources
+ log4j
+ opendata
+ utilsplugin2

Map paint styles:
- 
https://josm.openstreetmap.de/josmfile?page=Styles/Lane_and_Road_Attributes=1
- https://josm.openstreetmap.de/josmfile?page=Styles/PublicTransportV2=1
+ https://josm.openstreetmap.de/josmfile?page=Styles/HiDPISupport=1
- 
https://github.com/bastik/mapcss-tools/raw/osm/mapnik2mapcss/osm-results/mapnik.zip

Last errors/warnings:
- E: java.util.concurrent.ExecutionException: 
java.lang.IllegalArgumentException: Window must not be zero. Cause: 
java.lang.IllegalArgumentException: Window must not be zero
- E: Handled by bug report queue: java.lang.NullPointerException


=== REPORTED CRASH DATA ===
BugReportExceptionHandler#handleException:
No data collected.

Warning issued by: BugReportExceptionHandler#handleException

=== STACK TRACE ===
Thread: main (1)
java.lang.NullPointerException
at 
org.openstreetmap.josm.gui.MainApplication.mainJOSM(MainApplication.java:989)
at 
org.openstreetmap.josm.gui.MainApplication$2.processArguments(MainApplication.java:279)
at 
org.openstreetmap.josm.gui.MainApplication.main(MainApplication.java:851)
}}}


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

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

Versions of packages josm depends on:
ii  default-jre [java9-runtime]2:1.9-63
ii  fonts-noto 20171026-2
ii  jmapviewer 2.7+dfsg-1
ii  libcommons-compress-java   1.13-1
ii  libcommons-logging-java1.2-2
ii  libgettext-commons-java0.9.6-6
ii  liboauth-signpost-java 1.2.1.2-1.5
ii  libsvgsalamander-java  1.1.1+dfsg-2
ii  openjdk-9-jre [java9-runtime]  9.0.4+12-4
ii  proj-data  5.0.1-1

Versions of packages josm recommends:
ii  josm-l10n  0.0.svn13576+dfsg-3

josm suggests no packages.

-- no debconf information