Bug#921697: libcxx-serial-dev: /usr/include/v8stdint.h is already provided by libv8-dev

2019-02-09 Thread Alec Leamas
On 08/02/19 02:01, Andreas Beckmann wrote:
> Package: libcxx-serial-dev
> Version: 1.2.1-1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> 
> Hi,
> 
> during a test with piuparts I noticed your package failed to install
> because it tries to overwrite other packages files.

>   
>   trying to overwrite '/usr/include/v8stdint.h', which is 
> also in package
libv8-dev



Thanks, good catch! Will look into it.

Cheers!
--alec



Bug#921823: chromium: FTBFS of vaapi_wrapper.cc in i386/armhf (pointer casting)

2019-02-09 Thread Charlemagne Lasse
Source: chromium
Version: 72.0.3626.81-1
Severity: grave
X-Debbugs-CC: 856...@bugs.debian.org

FAILED: obj/media/gpu/vaapi/vaapi/vaapi_wrapper.o
g++ -MMD -MF obj/media/gpu/vaapi/vaapi/vaapi_wrapper.o.d
-DMEDIA_GPU_IMPLEMENTATION -DV8_DEPRECATION_WARNINGS -DUSE_UDEV
-DUSE_AURA=1 -DUSE_GLIB=1 -DUSE_NSS_CERTS=1 -DUSE_X11=1 -DNO_TCMALLOC
-DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL
-DCHROMIUM_BUILD -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
-D_LARGEFILE64_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS
-D_FORTIFY_SOURCE=2 -DNDEBUG -DNVALGRIND
-DDYNAMIC_ANNOTATIONS_ENABLED=0
-DGLIB_VERSION_MAX_ALLOWED=GLIB_VERSION_2_32
-DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_26 -DVK_NO_PROTOTYPES
-DGL_GLEXT_PROTOTYPES -DUSE_GLX -DUSE_EGL -DSK_HAS_PNG_LIBRARY
-DSK_HAS_WEBP_LIBRARY -DSK_HAS_JPEG_LIBRARY
-DSK_VULKAN_HEADER=\"../../skia/config/SkVulkanConfig.h\"
-DSK_VULKAN=1 -DSK_SUPPORT_GPU=1
-DSK_GPU_WORKAROUNDS_HEADER=\"gpu/config/gpu_driver_bug_workaround_autogen.h\"
-DVK_NO_PROTOTYPES -DUSING_SYSTEM_ICU=1
-DICU_UTIL_DATA_IMPL=ICU_UTIL_DATA_STATIC -DUCHAR_TYPE=uint16_t
-DU_IMPORT=U_EXPORT -DGOOGLE_PROTOBUF_NO_RTTI
-DGOOGLE_PROTOBUF_NO_STATIC_INITIALIZER -DHAVE_PTHREAD
-DLEVELDB_PLATFORM_CHROMIUM=1 -DLEVELDB_PLATFORM_CHROMIUM=1 -I../..
-Igen -I../../third_party/libyuv/include
-Igen/shim_headers/libevent_shim -Igen/shim_headers/libpng_shim
-Igen/shim_headers/libwebp_shim -Igen/shim_headers/icuuc_shim
-Igen/shim_headers/zlib_shim -I../../third_party/khronos -I../../gpu
-Igen/shim_headers/libdrm_shim -I../../third_party/vulkan/include
-Igen/shim_headers/icui18n_shim -Igen/shim_headers/re2_shim
-Igen/shim_headers/ffmpeg_shim -Igen/shim_headers/libvpx_shim
-Igen/shim_headers/snappy_shim -Igen/shim_headers/opus_shim
-I../../skia/config -I../../skia/ext
-I../../third_party/skia/include/c
-I../../third_party/skia/include/config
-I../../third_party/skia/include/core
-I../../third_party/skia/include/docs
-I../../third_party/skia/include/effects
-I../../third_party/skia/include/encode
-I../../third_party/skia/include/gpu
-I../../third_party/skia/include/pathops
-I../../third_party/skia/include/ports
-I../../third_party/skia/include/utils
-I../../third_party/vulkan/include
-I../../third_party/skia/third_party/vulkanmemoryallocator
-I../../third_party/skia/include/codec
-I../../third_party/skia/src/gpu -I../../third_party/skia/src/sksl
-I../../third_party/skia/modules/skottie/include
-I../../third_party/vulkan/include -I../../third_party/ced/src
-I../../third_party/protobuf/src -I../../third_party/mesa_headers
-I../../third_party/libwebm/source -I../../third_party/protobuf/src
-Igen/protoc_out -I../../third_party/leveldatabase
-I../../third_party/leveldatabase/src
-I../../third_party/leveldatabase/src/include -fno-strict-aliasing
--param=ssp-buffer-size=4 -fstack-protector
-Wno-builtin-macro-redefined -D__DATE__= -D__TIME__= -D__TIMESTAMP__=
-funwind-tables -fPIC -pipe -pthread -march=armv7-a -mfloat-abi=hard
-mtune=generic-armv7-a -mfpu=vfpv3-d16 -mthumb -Wall -Wno-psabi
-Wno-unused-local-typedefs -Wno-maybe-uninitialized
-Wno-deprecated-declarations -Wno-comments
-Wno-missing-field-initializers -Wno-unused-parameter -O2 -fno-ident
-fdata-sections -ffunction-sections -fno-omit-frame-pointer -g0
-fvisibility=hidden -I/usr/include/glib-2.0
-I/usr/lib/arm-linux-gnueabihf/glib-2.0/include -std=gnu++14
-Wno-narrowing -fno-exceptions -fno-rtti -fvisibility-inlines-hidden
-Wdate-time -D_FORTIFY_SOURCE=2 -Wno-pedantic -Wno-unused-function
-Wno-unused-variable -Wno-unused-but-set-variable
-Wno-deprecated-declarations  -Wno-return-type
-Wno-misleading-indentation  -Wno-attributes -Wno-subobject-linkage
-Wno-ignored-attributes -Wno-address -Wno-dangling-else
-Wno-class-memaccess -Wno-invalid-offsetof -Wno-packed-not-aligned
-Wno-pedantic -Wno-unused-function -Wno-unused-variable
-Wno-unused-but-set-variable -Wno-deprecated-declarations
-Wno-return-type -Wno-misleading-indentation  -Wno-attributes
-Wno-subobject-linkage  -Wno-ignored-attributes -Wno-address
-Wno-dangling-else -Wno-class-memaccess -Wno-invalid-offsetof
-Wno-packed-not-aligned  -c ../../media/gpu/vaapi/vaapi_wrapper.cc -o
obj/media/gpu/vaapi/vaapi/vaapi_wrapper.o
../../media/gpu/vaapi/vaapi_wrapper.cc: In member function
'scoped_refptr
media::VaapiWrapper::CreateVASurfaceForPixmap(const
scoped_refptr&)':
../../media/gpu/vaapi/vaapi_wrapper.cc:1012:38: error: invalid
conversion from 'long unsigned int*' to 'uintptr_t*' {aka 'unsigned
int*'} [-fpermissive]
   va_attrib_extbuf.buffers = fds.data();
  ^~

https://buildd.debian.org/status/fetch.php?pkg=chromium&arch=armhf&ver=72.0.3626.81-1&stamp=1549182249&raw=0
https://buildd.debian.org/status/fetch.php?pkg=chromium&arch=i386&ver=72.0.3626.81-1&stamp=1549136121&raw=0



Bug#905697: Info received (Bug#905697: kdepimlibs: don't depend on libical)

2019-02-09 Thread Scott Kitterman
I think the only API change that's relevant might be:

is_utc to icaltime_is_utc() in icaltimetype

For anyonne with a non-trivial C++ knowledge (i.e. not me), I suspect this 
wouldn't be too hard.

Scott K



Processed: Re: Bug#921781: fis-gtm: FTBFS (dh_auto_configure fails)

2019-02-09 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 help
Bug #921781 [src:fis-gtm] fis-gtm: FTBFS (dh_auto_configure fails)
Added tag(s) help.

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



Bug#921781: fis-gtm: FTBFS (dh_auto_configure fails)

2019-02-09 Thread Andreas Tille
Control: tags -1 help

[CCing some contributors to the bugs mentioned below]

Hi,

I've now read logs of #920900 and #898820.  The latter even is
mentioning that fis-gtm depends icu-config.  I wonder if someone
who has experience with cmake could lend a helping hand how to
replace icu-config by pkg-config.

I'm afraid I will end up with some hackish patches which are
not really nice to submit upstream and I'd prefer to do it the
right.  The naive approach to simply remove the icu-config
check from CMakeLists.txt ended up in 

...
-- Installing: 
/build/fis-gtm-6.3-005/debian/fis-gtm-6.3-005-stage1/usr/lib/x86_64-linux-gnu/fis-gtm/V6.3-005_x86_64/GDETEMPL.o
CMake Error at cmake_install.cmake:763 (file):
  file INSTALL cannot find
  "/build/fis-gtm-6.3-005/obj-x86_64-linux-gnu/utf8/GDEGET.o".

I've pushed my poor attempt to


https://salsa.debian.org/med-team/fis-gtm/blob/master/debian/patches/no_icu-config.patch

but this does not help. :-(

Any hints?

Kind regards

   Andreas.


On Sat, Feb 09, 2019 at 07:15:00AM +0100, Andreas Tille wrote:
> Hi,
> 
> that's caused by missing icu-config (#920900)
> 
> 
> On Sat, Feb 09, 2019 at 12:15:16AM +, Santiago Vila wrote:
> > [... snipped ...]
> 
> -- Detecting C compiler ABI info - done
> -- Detecting C compile features
> -- Detecting C compile features - done
> --> OS = Linux / ARCH = x86_64
> -- Bootstraping from pre-generated sources.
> CMake Error at CMakeLists.txt:756 (message):
>   Unable to find 'icu-config'.  Set ICUCONFIG in CMake cache.
> 
> 
> I need to check how to work around this.  Its a bit ugly to
> drop something with "wontfix" in this release state ...
> 
> Kind regards
> 
>  Andreas.
> 
> -- 
> http://fam-tille.de
> 
> ___
> Debian-med-packaging mailing list
> debian-med-packag...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging

-- 
http://fam-tille.de



Bug#921763: weston: FTBFS (dh_install: missing files)

2019-02-09 Thread Sven Joachim
On 2019-02-08 21:19 +, Santiago Vila wrote:

> Package: src:weston
> Version: 5.0.0-1
> Severity: serious
> Tags: ftbfs
>
> Dear maintainer:
>
> I tried to build this package in buster but it failed:
> [...]
> dh_install: Cannot find (any matches for) "usr/lib/*/weston/cms-colord.so" 
> (tried in ., debian/tmp)
>
> dh_install: weston missing files: usr/lib/*/weston/cms-colord.so
> dh_install: Cannot find (any matches for) "usr/lib/*/weston/cms-static.so" 
> (tried in ., debian/tmp)
>
> dh_install: weston missing files: usr/lib/*/weston/cms-static.so
> dh_install: missing files, aborting
> make[1]: *** [debian/rules:13: override_dh_install] Error 25

Thanks for the report.  This is a consequence of the latest colord
upload where libcolord-dev dropped its dependency on liblcms2-dev.
Adding the latter to Build-Depends, which I have just done in git, fixes
the problem.

Cheers,
   Sven



Bug#921301: starpu: FTBFS with upcoming doxygen 1.8.15

2019-02-09 Thread Samuel Thibault
Hello,

Samuel Thibault, le mar. 05 févr. 2019 20:21:56 +0200, a ecrit:
> Andreas Beckmann, le mar. 05 févr. 2019 10:54:49 +0100, a ecrit:
> > Control: retitle -1 starpu: FTBFS while building documentation
> 
> Ok, I give up with building the pdf version, doxygen+latex is too much
> of a hassle.

For information, I had to do it not only in starpu, but also in
gtg-trace, hwloc, and litl, i.e. essentially almost all of my packages
which build pdf out of doxygen.

We had already had LaTeX dependency issues in the past, and now it seems
to be a bug in the .tex file itself, I'm sorry I just can't spend time
on fixing issues between doxygen and LaTeX, Debian will just only ship
the html version for these packages.

If anybody wants to try to fix the actual issue, just disable the
doc-nopdf patch in those packages.

Samuel



Bug#835508: marked as done (ruby-leaflet-rails: should depend on libjs-leaflet (not ship convenience code copy))

2019-02-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Feb 2019 08:40:35 +
with message-id 
and subject line Bug#835508: fixed in ruby-leaflet-rails 1.3.1+dfsg-1
has caused the Debian Bug report #835508,
regarding ruby-leaflet-rails: should depend on libjs-leaflet (not ship 
convenience code copy)
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.)


-- 
835508: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835508
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-leaflet-rails
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

This package ships a convenience code copy of Leaflet.

It should instead ship only a symlink to separately packaged Leaflet in
package libjs-leaflet, and depend on that package.

See Debian Policy § 4.13 for further info.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJXwDKVAAoJECx8MUbBoAEhy9kP/1GsvtURm2Nkbm0oaYkj1FW1
xjLx71FSJRB+NriEe5H1leGwMeBHakksYlLkeJcTQEr45bUANTgl7xlSBnM/nC2h
ryEeVEk8ZO84arc0DN2bkMTiRZCKJ+VaTV8ZTmn3cS8I9lgakdTPYq/RR6zU1Qwe
e8vf4uHao+S/WZB5Mt2+yKoqZp89+7q1DrnrItbbT0QpoDB94wely5XrBqR7aLvV
Kzh7cacZn3dBlVwCKFK5H7L2NwmbaiR6XsLKMmmlaG9MmbXIMySB51vUSV/6FdVp
4Y8tS5HOyFoRtoaCCZeSMMltP1Zh4f+wwptRBJJB1iMsUfsrkxHEBBfOJRPYm7PV
F5uaEFA9VAl6l3mEoK+LiK9FHs/NVw2ENWeFIAxZJ3JdOTph0ObBIODLRAmAFDkf
udDKbzi+1Utzuud65/TVU8YI4Y6whz3ACAXTKT7B6TjE0QwffcOfWidtNtnLYlmI
6sADU5SM4raKuTbZFkyFjZT5lJXsxSSIFlNUjDVr6e9qsZnwFryDFgB+iIa+YtoU
TcctJyqaYLlvpuwzKR08cq+kBRwz879w1TjrO0EnWBuRyopjkuZgvBT7+NH3BTnI
6ZEt3rQcWetOWaXk5bKqx8NfcyB7TRvf+t10WG0lvaM3EnpI+8GFTHuu03bkTkAw
0BWeUeLv/iD7T3uLcqxj
=JOYP
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: ruby-leaflet-rails
Source-Version: 1.3.1+dfsg-1

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

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated ruby-leaflet-rails 
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: Sat, 09 Feb 2019 12:59:43 +0530
Source: ruby-leaflet-rails
Binary: ruby-leaflet-rails
Architecture: source all
Version: 1.3.1+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Pirate Praveen 
Description:
 ruby-leaflet-rails - Use leaflet.js with Rails 4
Closes: 835508
Changes:
 ruby-leaflet-rails (1.3.1+dfsg-1) unstable; urgency=medium
 .
   * Team upload
   * New upstream version 1.3.1+dfsg
   * Add smoke test as autopkgtest
   * Use libjs-leaflet instead of embedded copy
   * Remove embedded copy from source tarball (Closes: #835508)
Checksums-Sha1:
 b6c155be8573c2c15b14f316e27d5e0bb54b449a 2218 
ruby-leaflet-rails_1.3.1+dfsg-1.dsc
 d90571534d3cae4fbf49786d9f3fe3925b811e70 142232 
ruby-leaflet-rails_1.3.1+dfsg.orig.tar.xz
 b1f8b75712d405791458f45b11427bf55856f184 3384 
ruby-leaflet-rails_1.3.1+dfsg-1.debian.tar.xz
 525850b0b694da21740e5d8f0338e493704f406e 142232 
ruby-leaflet-rails_1.3.1+dfsg-1_all.deb
 17a9aa783883910d0cbe9951ad94e02df7d1f21e 10602 
ruby-leaflet-rails_1.3.1+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 ec0fbf091d10be880bf7d6bc294e8583bfb97c294f92148a9c1428676e5ba4f5 2218 
ruby-leaflet-rails_1.3.1+dfsg-1.dsc
 e29068c97f41deb53ccf01dfa1d8ae5abbdb425be76db87500e9661f4f9b5dcb 142232 
ruby-leaflet-rails_1.3.1+dfsg.orig.tar.xz
 4701c8b5b50370cce980e1a21af7e33a3e27c64772aa6eca2a8a64855c23bbfa 3384 
ruby-leaflet-rails_1.3.1+dfsg-1.debian.tar.xz
 f62c1ab9947292cc6a5d7af4c4c9caf1c8fb7009cf3c4dfbb8b2813617de0df4 142232 
ruby-leaflet-rails_1.3.1+dfsg-1_all.deb
 e69ca4f4b8a252d6cba60e507ccdd5426fb7d8ddc293a11fc091523248eca103 10602 
ruby-leaflet-rails_1.3.1+dfsg-1_amd64.buildinfo
Files:
 11b0452a952ee43500a88583ab01461c 2218 ruby optional 
ruby-leaflet-rails_1.3.1+dfsg-1.dsc
 1e7bf216a567bf4c0ec2bddc5180d207 142232 ruby optional 
ruby-leaflet-rails_1.3.1+dfsg.orig.tar.xz
 801d4de680bf21f9d72f2377cdb0ec71 3384 ruby optional 
ruby-leaflet-rails_1.3.1+dfsg-1.debian.tar.xz
 088a9cf9e12268e936a894cd19803594 142232 ruby optional 
ruby-leaflet-rails_1.3.1+dfsg-1_all.deb
 7413760bae1c4220207cbb24bd743cd9 10602 ruby 

Bug#741464: Bug #741464 in grub2 marked as pending

2019-02-09 Thread Colin Watson
Control: tag -1 pending

Hello,

Bug #741464 in grub2 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/grub-team/grub/commit/26f3349694ee739cc3711a7fd8a61be49b8d0ec5


Initialize keyboard in at_keyboard module init if keyboard is ready

Closes: #741464


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/741464



Processed: Re: photocollage: ValueError: Namespace Gtk not available

2019-02-09 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #914440 {Done: Adrian Bunk } [photocollage] photocollage: 
ValueError: Namespace Gtk not available
Added tag(s) pending.

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



Bug#914440: photocollage: ValueError: Namespace Gtk not available

2019-02-09 Thread Andreas Beckmann
Followup-For: Bug #914440
Control: tag -1 pending

Hi,

I've rebuilt the package from sid and opened a stretch-pu request:
https://bugs.debian.org/921825


Andreas



Bug#921781: fis-gtm: FTBFS (dh_auto_configure fails)

2019-02-09 Thread GCS
Control: tags -1 +patch

On Sat, Feb 9, 2019 at 9:13 AM Andreas Tille  wrote:
> I've now read logs of #920900 and #898820.  The latter even is
> mentioning that fis-gtm depends icu-config.  I wonder if someone
> who has experience with cmake could lend a helping hand how to
> replace icu-config by pkg-config.
 Proper patch is attached.

> The naive approach to simply remove the icu-config
> check from CMakeLists.txt ended up in
>
> ...
> -- Installing: 
> /build/fis-gtm-6.3-005/debian/fis-gtm-6.3-005-stage1/usr/lib/x86_64-linux-gnu/fis-gtm/V6.3-005_x86_64/GDETEMPL.o
> CMake Error at cmake_install.cmake:763 (file):
>   file INSTALL cannot find
>   "/build/fis-gtm-6.3-005/obj-x86_64-linux-gnu/utf8/GDEGET.o".
 This might be a different issue. Going to check it as well.

Laszlo/GCS
--- fis-gtm-6.3-005.orig/CMakeLists.txt
+++ fis-gtm-6.3-005/CMakeLists.txt
@@ -737,24 +737,9 @@ install(FILES ${scripts}
   PERMISSIONS ${install_permissions_script}
   )
 
-find_program(ICUCONFIG NAMES icu-config)
-if(ICUCONFIG)
-  execute_process(
-COMMAND ${ICUCONFIG} --version
-OUTPUT_VARIABLE icu_version
-RESULT_VARIABLE icu_failed
-OUTPUT_STRIP_TRAILING_WHITESPACE
-)
-  if(icu_failed)
-message(FATAL_ERROR "Command\n ${ICUCONFIG} --version\nfailed (${icu_failed}).")
-  elseif("x${icu_version}" MATCHES "^x([0-9]+\\.[0-9]+)")
-set(gtm_icu_version "${CMAKE_MATCH_1}")
-  else()
-message(FATAL_ERROR "Command\n ${ICUCONFIG} --version\nproduced unrecognized output:\n ${icu_version}")
-  endif()
-else()
-  message(FATAL_ERROR "Unable to find 'icu-config'.  Set ICUCONFIG in CMake cache.")
-endif()
+find_package(PkgConfig REQUIRED)
+PKG_CHECK_MODULES(ICU REQUIRED icu-io)
+set(gtm_icu_version "${ICU_VERSION}")
 
 find_program(LOCALECFG NAMES locale)
 if(LOCALECFG)
--- fis-gtm-6.3-005.orig/sr_unix/gtmprofile.gtc
+++ fis-gtm-6.3-005/sr_unix/gtmprofile.gtc
@@ -75,11 +75,11 @@ if [ $gtm_dist != "$old_gtm_dist" ] ; th
 else gtmroutines=$gtm_dist ; fi
 export gtmroutines
 # Set $gtm_icu_version if icu-config is available - should be set before checking for UTF-8 mode
-if [ -z "$gtm_icu_version" -a -n "`which icu-config`" ] ; then
-	gtm_icu_version=`icu-config --version | gtm_chset=M $gtm_dist/mumps -run %XCMD 'Read x Write $FNumber(x*$Select(+x>5:.1,1:1),"",1)'`
+if [ -z "$gtm_icu_version" -a -n "`which pkg-config`" ] ; then
+	gtm_icu_version=`pkg-config --modversion icu-io | gtm_chset=M $gtm_dist/mumps -run %XCMD 'Read x Write $FNumber(x*$Select(+x>5:.1,1:1),"",1)'`
 export gtm_icu_version
 	# Add library path to LD_LIBRARY_PATH
-	extendlibpath=`icu-config --libdir`
+	extendlibpath=`pkg-config --libs-only-L icu-io`
 	if [ "" = "$LD_LIBRARY_PATH" ]; then LD_LIBRARY_PATH="$extendlibpath"; else LD_LIBRARY_PATH="$LD_LIBRARY_PATH:$extendlibpath";fi; export LD_LIBRARY_PATH
 	if [ "ibm" = "$arch" ]; then
 		if [ "" = "$LIBPATH" ]; then LIBPATH="$extendlibpath"; else LIBPATH="$LIBPATH:$extendlibpath";fi; export LIBPATH;


Processed: Re: Bug#921781: fis-gtm: FTBFS (dh_auto_configure fails)

2019-02-09 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 +patch
Bug #921781 [src:fis-gtm] fis-gtm: FTBFS (dh_auto_configure fails)
Added tag(s) patch.

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



Processed: and graphite2? (was: Processed: doxygen: cascade of FTBFS)

2019-02-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 921783 doxygen
Bug #921783 [src:graphite2] graphite2: FTBFS (LaTeX error)
Bug reassigned from package 'src:graphite2' to 'doxygen'.
No longer marked as found in versions graphite2/1.3.13-7.
Ignoring request to alter fixed versions of bug #921783 to the same values 
previously set
> affects 921783 graphite2
Bug #921783 [doxygen] graphite2: FTBFS (LaTeX error)
Added indication that 921783 affects graphite2
> thanks
Stopping processing here.

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



Bug#921832: [firefox-esr] FTBFS of security/certverifier/Buffer.cpp

2019-02-09 Thread Charlemagne Lasse
Source: firefox-esr
Version: 60.5.0esr-1
Severity: grave
Tags: patch
Forwarded: https://bugzilla.mozilla.org/show_bug.cgi?id=1526648

Noticed while trying to prepare the mini fix for https://bugs.debian.org/921381

/usr/bin/g++ -o Unified_cpp_certverifier0.o -c -Ibuster/stl_wrappers
-Ibuster/system_wrappers -include
/build/firefox-esr-60.5.0esr/config/gcc_hidden.h -DNDEBUG=1
-DTRIMMED=1 '-DDLL_PREFIX="lib"' '-DDLL_SUFFIX=".so"'
-DSTATIC_EXPORTABLE_JS_API -DMOZ_HAS_MOZGLUE -DMOZILLA_INTERNAL_API
-DIMPL_LIBXUL -I/build/firefox-esr-60.5.0esr/security/certverifier
-I/build/firefox-esr-60.5.0esr/build-browser/security/certverifier
-I/build/firefox-esr-60.5.0esr/security/manager/ssl
-I/build/firefox-esr-60.5.0esr/security/pkix/include
-I/build/firefox-esr-60.5.0esr/security/pkix/lib
-I/build/firefox-esr-60.5.0esr/build-browser/dist/include
-I/usr/include/nspr -I/usr/include/nss -fPIC -DMOZILLA_CLIENT -include
/build/firefox-esr-60.5.0esr/build-browser/mozilla-config.h
-Wdate-time -D_FORTIFY_SOURCE=2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2
-Wall -Wempty-body -Wignored-qualifiers -Woverloaded-virtual
-Wpointer-arith -Wsign-compare -Wtype-limits -Wunreachable-code
-Wwrite-strings -Wno-invalid-offsetof -Wc++1z-compat -Wduplicated-cond
-Wimplicit-fallthrough -Wno-error=maybe-uninitialized
-Wno-error=deprecated-declarations -Wno-error=array-bounds
-Wno-error=free-nonheap-object -Wformat -Wformat-overflow=2
-fno-sized-deallocation -fstack-protector-strong -Wformat
-Werror=format-security -fno-schedule-insns2 -fno-lifetime-dse
-fno-delete-null-pointer-checks -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2
-fno-exceptions -fno-strict-aliasing -fno-rtti -ffunction-sections
-fdata-sections -fno-exceptions -fno-math-errno -pthread -pipe -g
-freorder-blocks -O2 -fomit-frame-pointer -Wall -Wextra
-Wunreachable-code -Wno-unused-parameter  -MD -MP -MF
.deps/Unified_cpp_certverifier0.o.pp
/build/firefox-esr-60.5.0esr/build-browser/security/certverifier/Unified_cpp_certverifier0.cpp
In file included from
/build/firefox-esr-60.5.0esr/build-browser/security/certverifier/Unified_cpp_certverifier0.cpp:20:
/build/firefox-esr-60.5.0esr/security/certverifier/Buffer.cpp: In
function 'bool mozilla::operator==(const Buffer&, const Buffer&)':
/build/firefox-esr-60.5.0esr/security/certverifier/Buffer.cpp:14:11:
error: 'memcmp' was not declared in this scope
   memcmp(a.begin(), b.begin(), a.length()) == 0);
   ^~
/build/firefox-esr-60.5.0esr/security/certverifier/Buffer.cpp:14:11:
note: 'memcmp' is defined in header ''; did you forget to
'#include '?
/build/firefox-esr-60.5.0esr/security/certverifier/Buffer.cpp:1:1:
+#include 
 /* -*- Mode: C++; tab-width: 8; indent-tabs-mode: nil; c-basic-offset: 2 -*- */
/build/firefox-esr-60.5.0esr/security/certverifier/Buffer.cpp:14:11:
   memcmp(a.begin(), b.begin(), a.length()) == 0);
   ^~
make[6]: *** [/build/firefox-esr-60.5.0esr/config/rules.mk:1056:
Unified_cpp_certverifier0.o] Error 1
make[6]: Leaving directory
'/build/firefox-esr-60.5.0esr/build-browser/security/certverifier'
make[5]: *** [/build/firefox-esr-60.5.0esr/config/recurse.mk:73:
security/certverifier/target] Error 2
make[5]: Leaving directory '/build/firefox-esr-60.5.0esr/build-browser'
make[4]: *** [/build/firefox-esr-60.5.0esr/config/recurse.mk:33:
compile] Error 2
make[4]: Leaving directory '/build/firefox-esr-60.5.0esr/build-browser'
make[3]: *** [/build/firefox-esr-60.5.0esr/config/rules.mk:442: default] Error 2
make[3]: Leaving directory '/build/firefox-esr-60.5.0esr/build-browser'
dh_auto_build: cd build-browser && make -j1
LD_LIBS=-Wl,--no-gc-sections _LEAKTEST_FILES=leaktest.py returned exit
code 2
make[2]: *** [debian/rules:227: stamps/build-browser] Error 2
make[2]: Leaving directory '/build/firefox-esr-60.5.0esr'
make[1]: *** [debian/rules:336: build-arch] Error 2
make[1]: Leaving directory '/build/firefox-esr-60.5.0esr'
make: *** [debian/rules:336: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
From: Charlemange Lasse 
Date: Sat, 9 Feb 2019 10:08:10 +0100
Subject: [PATCH] Fix FTBFS of security/certverifier/Buffer.cpp
---
 debian/changelog |  1 +
 .../Bug-1526648-Include-cstring-for-memcmp.patch | 12 
 debian/patches/series|  1 +
 3 files changed, 14 insertions(+)
 create mode 100644 debian/patches/fixes/Bug-1526648-Include-cstring-for-memcmp.patch

--- a/debian/changelog
+++ b/debian/changelog
@@ -4,6 +4,7 @@ firefox-esr (60.5.0esr-2) UNRELEASED; urgency=medium
 
   * Fix download of esr compatible Gecko Media Plugins (widevine, openh264) by
 switching to "esr" update channel (Closes: #921381, #921121, #921654)
+  * Fix FTBFS of security/certverifier/Buffer.cpp (Closes: #-TODO)
 
  -- Charlemange Lasse   Sat, 09 Feb 2019 08:47:47 +0100
 
--- /dev/null
+++ b/debian/patches/fixes/Bug-1526648-Include-cstring-for-memcmp.patch
@@ -0,0 +1,12 @@
+diff --git a/secur

Processed: Re: snapd: FTBFS: too many arguments in call to activation.Listeners

2019-02-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 917797 + unreproducible
Bug #917797 [src:snapd] snapd: FTBFS: too many arguments in call to 
activation.Listeners
Added tag(s) unreproducible.
> user debian-rele...@lists.debian.org
Setting user to debian-rele...@lists.debian.org (was sa...@debian.org).
> usertag 917797 + bsp-2019-02-de-berlin
There were no usertags set.
Usertags are now: bsp-2019-02-de-berlin.
> thanks
Stopping processing here.

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



Processed: found 910757 in 20140202+stable-3

2019-02-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> found 910757 20140202+stable-3
Bug #910757 [gnulib] gnulib: CVE-2018-17942 heap-based buffer overflow
Marked as found in versions gnulib/20140202+stable-3.
> thanks
Stopping processing here.

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



Bug#917797: snapd: FTBFS: too many arguments in call to activation.Listeners

2019-02-09 Thread Sascha Steinbiss
tags 917797 + unreproducible
user debian-rele...@lists.debian.org
usertag 917797 + bsp-2019-02-de-berlin
thanks

Hi,

a warm hello from the BSP in Berlin.

> I found problems with am armel-on-arm64 build, but I can reproduce the
> same problem on a straight amd64 build too.

I've tried to look into this issue but was not able to reproduce theis
FTBFS with the current unstable version snapd_2.37.2-1 (tested on amd64
and armel). Builds complete fine and show no fatal errors.

I think this bug can be closed.

Cheers
Sascha



Processed: Re: Code compiles just fine with current commit in Salsa

2019-02-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 897865 + unreproducible
Bug #897865 [src:snapd] snapd: ftbfs with GCC-8
Bug #906408 [src:snapd] snapd: FTBFS in buster/sid
Added tag(s) unreproducible.
Added tag(s) unreproducible.
> user debian-rele...@lists.debian.org
Setting user to debian-rele...@lists.debian.org (was sa...@debian.org).
> usertag 897865 + bsp-2019-02-de-berlin
Usertags were: bsp-2018-10-de-karlsruhe.
Usertags are now: bsp-2018-10-de-karlsruhe bsp-2019-02-de-berlin.
> thanks
Stopping processing here.

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



Bug#897865: Code compiles just fine with current commit in Salsa

2019-02-09 Thread Sascha Steinbiss
tags 897865 + unreproducible
user debian-rele...@lists.debian.org
usertag 897865 + bsp-2019-02-de-berlin
thanks

Hi,

a warm hello from the BSP in Berlin (and from across the table fro you,
Hilko ;).

> The current commit in Salsa -- 00b7e79dd144ebfc5d187c331353b50239b032db,
> marked "snapd (2.35.5-1) UNRELEASED" -- builds the test code including
> locking-test.c just fine, but various tests then fail.

I've tried to look into this issue but was not able to reproduce theis
FTBFS with the current unstable version snapd_2.37.2-1 (tested on amd64
and armel). Builds complete fine and show no fatal errors.

I think this bug can be closed.

Cheers
Sascha



Processed: found 910757 in 20180621~6979c25-1

2019-02-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> found 910757 20180621~6979c25-1
Bug #910757 [gnulib] gnulib: CVE-2018-17942 heap-based buffer overflow
Marked as found in versions gnulib/20180621~6979c25-1.
> thanks
Stopping processing here.

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



Bug#921725: libu2f-host: CVE-2018-20340

2019-02-09 Thread Sébastien Delafond
On Feb/08, Nicolas Braud-Santoni wrote:
> I backported the fix and prepared an upload.
> The debdiff is attached, and the commands used to produced it are documented 
> below.
> 
> May I proceed with an upload to security-master?

It looks OK to me, so if it passes testing on your end please upload to
security-master (don't forget to use -sa as it will be new there).

Cheers,

-- 
Seb



Processed: closing 884693

2019-02-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> close 884693 0.16.1-1
Bug #884693 {Done: Salvatore Bonaccorso } 
[src:ruby-net-ldap] ruby-net-ldap: CVE-2017-17718: missing certificate 
validation
Ignoring request to alter fixed versions of bug #884693 to the same values 
previously set
Bug #884693 {Done: Salvatore Bonaccorso } 
[src:ruby-net-ldap] ruby-net-ldap: CVE-2017-17718: missing certificate 
validation
Bug 884693 is already marked as done; not doing anything.
> thanks
Stopping processing here.

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



Bug#884693: closing 884693

2019-02-09 Thread Salvatore Bonaccorso
close 884693 0.16.1-1
thanks



Processed: closing 884693

2019-02-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> close 884693 0.16.1-1
Bug #884693 [src:ruby-net-ldap] ruby-net-ldap: CVE-2017-17718: missing 
certificate validation
Marked as fixed in versions ruby-net-ldap/0.16.1-1.
Bug #884693 [src:ruby-net-ldap] ruby-net-ldap: CVE-2017-17718: missing 
certificate validation
Marked Bug as done
> thanks
Stopping processing here.

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



Bug#918171: Broken with Thunderbird 60

2019-02-09 Thread Daniel Baumann
tag 918171 + fixed-upstream
thanks

Hi,

upstream version is at 0.9 and works nicely with thunderbird 60 from
sid/buster. It would be nice if you could update package in time to make
it into buster.

Regards,
Daniel



Processed: Re: Broken with Thunderbird 60

2019-02-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tag 918171 + fixed-upstream
Bug #918171 [xul-ext-colorediffs] Broken with Thunderbird 60
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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



Bug#921352: reassign 921352 to octave-msh, closing 921352

2019-02-09 Thread Sébastien Villemot
reassign 921352 octave-msh 1.0.10-6
close 921352 1.0.10-7
thanks

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄⠀⠀⠀⠀  http://www.debian.org



Processed: reassign 921352 to octave-msh, closing 921352

2019-02-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 921352 octave-msh 1.0.10-6
Bug #921352 [src:gmsh] gmsh: breaks octave-msh autopkgtest
Bug reassigned from package 'src:gmsh' to 'octave-msh'.
No longer marked as found in versions gmsh/4.1.3+ds1-1.
Ignoring request to alter fixed versions of bug #921352 to the same values 
previously set
Bug #921352 [octave-msh] gmsh: breaks octave-msh autopkgtest
Marked as found in versions octave-msh/1.0.10-6.
> close 921352 1.0.10-7
Bug #921352 [octave-msh] gmsh: breaks octave-msh autopkgtest
There is no source info for the package 'octave-msh' at version '1.0.10-7' with 
architecture ''
Unable to make a source version for version '1.0.10-7'
Marked as fixed in versions 1.0.10-7.
Bug #921352 [octave-msh] gmsh: breaks octave-msh autopkgtest
Marked Bug as done
> thanks
Stopping processing here.

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



Bug#921836: ipywidgets: FTBFS (error TS2688: Cannot find type definition file for 'sizzle')

2019-02-09 Thread Santiago Vila
Package: src:ipywidgets
Version: 6.0.0-3
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2,python3,sphinxdoc --buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_autoreconf -i -O--buildsystem=pybuild
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure
I: pybuild base:217: python2.7 setup.py config 
running config
I: pybuild base:217: python3.7 setup.py config 
running config
dh_auto_configure -- -d ./widgetsnbextension
I: pybuild base:217: python2.7 setup.py config 
INFO:root:setup.py entered
INFO:root:$PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
running config
I: pybuild base:217: python3.7 setup.py config 
INFO:root:setup.py entered
INFO:root:$PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
running config
make[1]: Leaving directory '/<>'
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
/usr/bin/make -C debian -f fakewebpack.mk all
make[2]: Entering directory '/<>/debian'
/usr/bin/make -f "fakewebpack-prep-unpacked.mk" all
make[3]: Entering directory '/<>/debian'
cd "fakewebpack-unpacked/phosphor/" && tsc --moduleResolution Classic --project 
src
mkdir -p "fakewebpack-unpacked/phosphor/styles/" && NODE_PATH=../.. 
fakewebpack-helpers/css-loader-pack.py < 
"fakewebpack-unpacked/phosphor/styles/base.css.real" > 
"fakewebpack-unpacked/phosphor/styles/base.css"
mkdir -p "fakewebpack-unpacked/phosphor/styles/" && m4 -DNODE_PATH=../.. 
-DCSS_INPUT=./base.css "fakewebpack-helpers/style-loader.js.m4" > 
"fakewebpack-unpacked/phosphor/styles/base.css?f74d"
printf "module.exports = $(cat 
"fakewebpack-unpacked/jupyter-js-widgets/package.json.real");" > 
"fakewebpack-unpacked/jupyter-js-widgets/package.json"
cd "fakewebpack-unpacked/jupyter-js-widgets/" && tsc --moduleResolution Classic 
--project src
../../../../../../usr/lib/nodejs/@types/jquery/index.d.ts(28,23): error TS2688: 
Cannot find type definition file for 'sizzle'.
../../../../../../usr/lib/nodejs/@types/jquery/misc.d.ts(27,33): error TS2503: 
Cannot find namespace 'Sizzle'.
../../../../../../usr/lib/nodejs/@types/jquery/misc.d.ts(35,14): error TS2503: 
Cannot find namespace 'Sizzle'.
../../../../../../usr/lib/nodejs/@types/jquery/misc.d.ts(43,17): error TS2503: 
Cannot find namespace 'Sizzle'.
make[3]: *** [fakewebpack-prep-unpacked.mk:33: 
fakewebpack-unpacked/jupyter-js-widgets/lib.stamp] Error 1
make[3]: Leaving directory '/<>/debian'
make[2]: *** [fakewebpack.mk:73: fakewebpack/widgetsnbextension-unpacked.stamp] 
Error 2
make[2]: Leaving directory '/<>/debian'
make[1]: *** [debian/rules:15: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:7: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

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

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.



Bug#921839: wcslib: FTBFS (LaTeX error)

2019-02-09 Thread Santiago Vila
Package: src:wcslib
Version: 6.2-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh  build-indep --no-parallel --with autoreconf
   dh_update_autotools_config -i
   debian/rules override_dh_autoreconf
make[1]: Entering directory '/<>'
AUTOHEADER=true dh_autoreconf
make[1]: Leaving directory '/<>'
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- --docdir=$\{prefix\}/share/doc/wcslib-doc
./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu 
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run 
--disable-maintainer-mode --disable-dependency-tracking 
--docdir=\${prefix}/share/doc/wcslib-doc
configure: WARNING: unrecognized options: --disable-silent-rules, 
--disable-maintainer-mode, --disable-dependency-tracking
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu

[... snipped ...]



LaTeX Warning: Reference `wcsunits_8h' on page 20 undefined on input line 22.


LaTeX Warning: Reference `wcsutil_8h' on page 20 undefined on input line 23.


LaTeX Warning: Reference `wtbarr_8h' on page 20 undefined on input line 24.

) (./structcelprm.tex [20] [21] [22]) (./structdisprm.tex [23] [24] [25]
[26]) (./structdpkey.tex [27] [28]) (./structfitskey.tex [29] [30] [31]
[32]) (./structfitskeyid.tex [33]) (./structlinprm.tex [34] [35] [36] [37]
[38]) (./structprjprm.tex [39] [40] [41] [42] [43]) (./structpscard.tex
[44]) (./structpvcard.tex [45]) (./structspcprm.tex [46]
(/usr/share/texlive/texmf-dist/tex/latex/psnfss/ts1pcr.fd) [47] [48])
(./structspxprm.tex [49] [50] [51] [52] [53] [54]) (./structtabprm.tex [55]
[56] [57] [58] [59]) (./structwcserr.tex [60]) (./structwcsprm.tex [61]
[62] [63] [64] [65] [66] [67] [68] [69] [70] [71] [72] [73] [74] [75] [76]
[77] [78] [79] [80]) (./structwtbarr.tex [81] [82]) [83] (./cel_8h.tex
Underfull \hbox (badness 1) in paragraph at lines 3--4

[84] [85]
! Missing } inserted.
 
}
l.168 \end{DoxyEnumFields}
  
? 
! Emergency stop.
 
}
l.168 \end{DoxyEnumFields}
  
!  ==> Fatal error occurred, no output PDF file produced!
Transcript written on refman.log.
make[3]: *** [GNUmakefile:66: ../wcslib.pdf] Error 1
rm doxextr.c
make[3]: Leaving directory '/<>/doxygen'
make[2]: *** [../makedefs:185: all] Error 2
make[2]: Leaving directory '/<>/doxygen'
make[1]: *** [debian/rules:20: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:7: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

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

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.



Bug#921837: mopidy: FTBFS (dh_installman: Could not determine section for ./docs/_build/man/_static)

2019-02-09 Thread Santiago Vila
Package: src:mopidy
Version: 2.2.1-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2,sphinxdoc,systemd --buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_autoreconf -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python2.7 setup.py config 
running config
   dh_auto_test -i -O--buildsystem=pybuild
   create-stamp debian/debhelper-build-stamp
 fakeroot debian/rules binary-indep
dh binary-indep --with python2,sphinxdoc,systemd --buildsystem=pybuild
   dh_testroot -i -O--buildsystem=pybuild
   dh_prep -i -O--buildsystem=pybuild
   dh_installdirs -i -O--buildsystem=pybuild

[... snipped ...]

WARNING: autodoc: failed to import attribute 
u'core.PlaybackController.current_track' from module u'mopidy'; the following 
exception was raised:
No module named pykka
WARNING: autodoc: failed to import attribute u'core.PlaybackController.state' 
from module u'mopidy'; the following exception was raised:
No module named pykka
WARNING: autodoc: failed to import attribute 
u'core.PlaybackController.time_position' from module u'mopidy'; the following 
exception was raised:
No module named pykka
WARNING: autodoc: failed to import attribute u'core.PlaybackController.mute' 
from module u'mopidy'; the following exception was raised:
No module named pykka
WARNING: autodoc: failed to import attribute u'core.PlaybackController.volume' 
from module u'mopidy'; the following exception was raised:
No module named pykka
WARNING: autodoc: failed to import method u'core.LibraryController.find_exact' 
from module u'mopidy'; the following exception was raised:
No module named pykka
WARNING: autodoc: failed to import method u'core.PlaylistsController.filter' 
from module u'mopidy'; the following exception was raised:
No module named pykka
WARNING: autodoc: failed to import method 
u'core.PlaylistsController.get_playlists' from module u'mopidy'; the following 
exception was raised:
No module named pykka
WARNING: autodoc: failed to import attribute 
u'core.PlaylistsController.playlists' from module u'mopidy'; the following 
exception was raised:
No module named pykka
WARNING: autodoc: failed to import class u'mixer.Mixer' from module u'mopidy'; 
the following exception was raised:
No module named pykka
WARNING: autodoc: failed to import class u'mixer.MixerListener' from module 
u'mopidy'; the following exception was raised:
No module named pykka
WARNING: autodoc: failed to import module u'dispatcher' from module 
u'mopidy.mpd'; the following exception was raised:
No module named pykka
WARNING: autodoc: failed to import module u'playback' from module 
u'mopidy.mpd.protocol'; the following exception was raised:
No module named pykka
WARNING: autodoc: failed to import module u'status' from module 
u'mopidy.mpd.protocol'; the following exception was raised:
No module named pykka
looking for now-outdated files... none found
pickling environment... done
checking consistency... done
writing... mopidy.1 { } 
build succeeded, 100 warnings.

The manual pages are in _build/man.

Build finished. The manual pages are in _build/man.
make[2]: Leaving directory '/<>/docs'
dh_installman
dh_installman: Could not determine section for ./docs/_build/man/_static
dh_installman: Aborting due to earlier error
make[1]: *** [debian/rules:40: override_dh_installman] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:9: binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

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

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.



Bug#921838: ppl: FTBFS (LaTeX error)

2019-02-09 Thread Santiago Vila
Package: src:ppl
Version: 1:1.2-7
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules binary-indep
dh binary-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
libtoolize: putting auxiliary files in '.'.
libtoolize: copying file './ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:152: installing './compile'
configure.ac:43: installing './missing'

[... snipped ...]

d on input line 40.

) (./group__PPL__C__interface.tex)
Underfull \vbox (badness 7740) has occurred while \output is active [17]
[18] (./group__Init.tex
Underfull \hbox (badness 1) detected at line 35
[][][]

Underfull \hbox (badness 1) detected at line 48
[][][]
[19]) [20] (./group__Version.tex [21]) [22] (./group__Error.tex
(/usr/share/texlive/texmf-dist/tex/latex/psnfss/omsptm.fd)
Overfull \hbox (1.62299pt too wide) in paragraph at lines 6--20
[][]\OT1/ptm/m/n/10 P[]P[]L[][][][]E[]R[]R[]O[]R[][][][]O[]U[]T[][][][]O[]F[][]
[][]M[]E[]M[]O[]RY[][], [][]P[]P[]L[][][][]E[]R[]R[]O[]R[][][][]I[]N[]V[]A[]L[]
I[]D[][][][]A[]R[]G[]U[]M[]E[]NT[][], [][]P[]P[]L[][][][]E[]R[]R[]O[]R[][][][]D
[]O[]M[]

Overfull \hbox (1.35289pt too wide) in paragraph at lines 6--20
[][]\OT1/ptm/m/n/10 P[]P[]L[][][][]A[]R[]I[]T[]H[]M[]E[]T[]I[]C[][][][]O[]V[]E[
]R[]F[]L[]OW[][], [][]P[]P[]L[][][][]S[]T[]D[]I[]O[][][][]E[]R[]R[]OR[][], [][]
P[]P[]L[][][][]E[]R[]R[]O[]R[][][][]I[]N[]T[]E[]R[]N[]A[]L[][][][]E[]R[]R[]OR[]
[], [][]P[]
! Missing } inserted.
 
}
l.88 \end{DoxyEnumFields}
 
? 
! Emergency stop.
 
}
l.88 \end{DoxyEnumFields}
 
!  ==> Fatal error occurred, no output PDF file produced!
Transcript written on refman.log.
make[3]: *** [Makefile:6: refman.pdf] Error 1
make[3]: Leaving directory 
'/<>/doc/user-configured-c-interface.latex-dir'
make[2]: *** [Makefile:2064: ppl-user-configured-c-interface-1.2.pdf] Error 2
make[2]: Leaving directory '/<>/doc'
dh_auto_build: cd doc && make -j1 user-configured returned exit code 2
make[1]: *** [debian/rules:75: override_dh_auto_build-indep] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:52: binary-indep] Error 2
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

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

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.



Processed: Still FTBFS, different

2019-02-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> user debian-rele...@lists.debian.org
Setting user to debian-rele...@lists.debian.org (was ben...@debian.org).
> usertag 906365 + bsp-2019-02-de-berlin
Usertags were: bsp-2018-12-ch-bern.
Usertags are now: bsp-2018-12-ch-bern bsp-2019-02-de-berlin.
> tag 906365 fixed-upstream
Bug #906365 [src:ipxe] ipxe: FTBFS in buster/sid (Error: can't resolve 
`__table_entries.2701')
Added tag(s) fixed-upstream.
> thank you
Stopping processing here.

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



Bug#906365: Still FTBFS, different

2019-02-09 Thread Hilko Bengen
user debian-rele...@lists.debian.org
usertag 906365 + bsp-2019-02-de-berlin   
tag 906365 fixed-upstream
thank you

Hi!

Greetings from the BSP at the DCSO office in Berlin.

I find that building from source still fails, only with "interesting"
different symptoms, see below.

However, I am happy to report that building a new version (based on
upstream commit 36a4c85f911c85f5ab183331ff74d125f9a9ed32 from
2019-01-25) builds just fine.

Cheers,
-Hilko

,
| ar: creating bin-x86_64-efi/blib.a
| ranlib bin-x86_64-efi/blib.a
| ld  -m elf_x86_64 -q -S   --gc-sections -static -T scripts/efi.lds  -u 
_efidrv_start --defsym check__efidrv_start=_efidrv_start   -u obj_intel 
--defsym check_obj_intel=obj_intel   -u pci_devlist_8086100e --defsym 
check_pci_devlist_8086100e=pci_devlist_8086100e   -u obj_config --defsym 
check_obj_config=obj_config   -u obj_config_efi --defsym 
check_obj_config_efi=obj_config_efi  --defsym pci_vendor_id=0x8086 --defsym 
pci_device_id=0x100e -e _efidrv_start bin-x86_64-efi/version.82540em.efidrv.o 
bin-x86_64-efi/blib.a -o bin-x86_64-efi/82540em.efidrv.tmp \
|   --defsym _build_id=`perl -e 'printf "0x%08x", int ( rand ( 0x ) 
);'` \
|   --defsym _build_timestamp=1549708978 \
|   -Map bin-x86_64-efi/82540em.efidrv.tmp.map
| objdump -ht bin-x86_64-efi/82540em.efidrv.tmp | perl ./util/sortobjdump.pl >> 
bin-x86_64-efi/82540em.efidrv.tmp.map
| ./util/elf2efi64 --subsystem=11 bin-x86_64-efi/82540em.efidrv.tmp 
bin-x86_64-efi/82540em.efidrv
| Unrecognised relocation type 4
| make[2]: *** [Makefile.efi:30: bin-x86_64-efi/82540em.efidrv] Error 1
| rm bin-x86_64-efi/version.82540em.efidrv.o
| make[2]: Leaving directory '/<>/ipxe-1.0.0+git-20161027.b991c67/src'
| dh_auto_build: cd src && make -j8 V=1 NO_WERROR=1 
VERSION=1.0.0\+git-20161027.b991c67-1 bin-x86_64-efi/82540em.efirom returned 
exit code 2
| make[1]: *** [debian/rules:18: src/bin-x86_64-efi/82540em.efirom] Error 2
| make[1]: Leaving directory '/<>/ipxe-1.0.0+git-20161027.b991c67'
| make: *** [debian/rules:12: build] Error 2
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
`



Processed: Re: Bug#921832: [firefox-esr] FTBFS of security/certverifier/Buffer.cpp

2019-02-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 921832 normal
Bug #921832 [src:firefox-esr] [firefox-esr] FTBFS of 
security/certverifier/Buffer.cpp
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.

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



Bug#921832: [firefox-esr] FTBFS of security/certverifier/Buffer.cpp

2019-02-09 Thread Mike Hommey
severity 921832 normal
thanks

I don't know how you built this, but in a pbuilder with a fresh
unstable, it doesn't FTBFS.

Mike

On Sat, Feb 09, 2019 at 10:56:57AM +0100, Charlemagne Lasse wrote:
> Source: firefox-esr
> Version: 60.5.0esr-1
> Severity: grave
> Tags: patch
> Forwarded: https://bugzilla.mozilla.org/show_bug.cgi?id=1526648
> 
> Noticed while trying to prepare the mini fix for 
> https://bugs.debian.org/921381
> 
> /usr/bin/g++ -o Unified_cpp_certverifier0.o -c -Ibuster/stl_wrappers
> -Ibuster/system_wrappers -include
> /build/firefox-esr-60.5.0esr/config/gcc_hidden.h -DNDEBUG=1
> -DTRIMMED=1 '-DDLL_PREFIX="lib"' '-DDLL_SUFFIX=".so"'
> -DSTATIC_EXPORTABLE_JS_API -DMOZ_HAS_MOZGLUE -DMOZILLA_INTERNAL_API
> -DIMPL_LIBXUL -I/build/firefox-esr-60.5.0esr/security/certverifier
> -I/build/firefox-esr-60.5.0esr/build-browser/security/certverifier
> -I/build/firefox-esr-60.5.0esr/security/manager/ssl
> -I/build/firefox-esr-60.5.0esr/security/pkix/include
> -I/build/firefox-esr-60.5.0esr/security/pkix/lib
> -I/build/firefox-esr-60.5.0esr/build-browser/dist/include
> -I/usr/include/nspr -I/usr/include/nss -fPIC -DMOZILLA_CLIENT -include
> /build/firefox-esr-60.5.0esr/build-browser/mozilla-config.h
> -Wdate-time -D_FORTIFY_SOURCE=2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2
> -Wall -Wempty-body -Wignored-qualifiers -Woverloaded-virtual
> -Wpointer-arith -Wsign-compare -Wtype-limits -Wunreachable-code
> -Wwrite-strings -Wno-invalid-offsetof -Wc++1z-compat -Wduplicated-cond
> -Wimplicit-fallthrough -Wno-error=maybe-uninitialized
> -Wno-error=deprecated-declarations -Wno-error=array-bounds
> -Wno-error=free-nonheap-object -Wformat -Wformat-overflow=2
> -fno-sized-deallocation -fstack-protector-strong -Wformat
> -Werror=format-security -fno-schedule-insns2 -fno-lifetime-dse
> -fno-delete-null-pointer-checks -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2
> -fno-exceptions -fno-strict-aliasing -fno-rtti -ffunction-sections
> -fdata-sections -fno-exceptions -fno-math-errno -pthread -pipe -g
> -freorder-blocks -O2 -fomit-frame-pointer -Wall -Wextra
> -Wunreachable-code -Wno-unused-parameter  -MD -MP -MF
> .deps/Unified_cpp_certverifier0.o.pp
> /build/firefox-esr-60.5.0esr/build-browser/security/certverifier/Unified_cpp_certverifier0.cpp
> In file included from
> /build/firefox-esr-60.5.0esr/build-browser/security/certverifier/Unified_cpp_certverifier0.cpp:20:
> /build/firefox-esr-60.5.0esr/security/certverifier/Buffer.cpp: In
> function 'bool mozilla::operator==(const Buffer&, const Buffer&)':
> /build/firefox-esr-60.5.0esr/security/certverifier/Buffer.cpp:14:11:
> error: 'memcmp' was not declared in this scope
>memcmp(a.begin(), b.begin(), a.length()) == 0);
>^~
> /build/firefox-esr-60.5.0esr/security/certverifier/Buffer.cpp:14:11:
> note: 'memcmp' is defined in header ''; did you forget to
> '#include '?
> /build/firefox-esr-60.5.0esr/security/certverifier/Buffer.cpp:1:1:
> +#include 
>  /* -*- Mode: C++; tab-width: 8; indent-tabs-mode: nil; c-basic-offset: 2 -*- 
> */
> /build/firefox-esr-60.5.0esr/security/certverifier/Buffer.cpp:14:11:
>memcmp(a.begin(), b.begin(), a.length()) == 0);
>^~
> make[6]: *** [/build/firefox-esr-60.5.0esr/config/rules.mk:1056:
> Unified_cpp_certverifier0.o] Error 1
> make[6]: Leaving directory
> '/build/firefox-esr-60.5.0esr/build-browser/security/certverifier'
> make[5]: *** [/build/firefox-esr-60.5.0esr/config/recurse.mk:73:
> security/certverifier/target] Error 2
> make[5]: Leaving directory '/build/firefox-esr-60.5.0esr/build-browser'
> make[4]: *** [/build/firefox-esr-60.5.0esr/config/recurse.mk:33:
> compile] Error 2
> make[4]: Leaving directory '/build/firefox-esr-60.5.0esr/build-browser'
> make[3]: *** [/build/firefox-esr-60.5.0esr/config/rules.mk:442: default] 
> Error 2
> make[3]: Leaving directory '/build/firefox-esr-60.5.0esr/build-browser'
> dh_auto_build: cd build-browser && make -j1
> LD_LIBS=-Wl,--no-gc-sections _LEAKTEST_FILES=leaktest.py returned exit
> code 2
> make[2]: *** [debian/rules:227: stamps/build-browser] Error 2
> make[2]: Leaving directory '/build/firefox-esr-60.5.0esr'
> make[1]: *** [debian/rules:336: build-arch] Error 2
> make[1]: Leaving directory '/build/firefox-esr-60.5.0esr'
> make: *** [debian/rules:336: build] Error 2
> dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2



Bug#867671: closed by Stephen Kitt (Bug#867671: fixed in libratbag 0.9.904-3)

2019-02-09 Thread Stephen Kitt
On Fri, 8 Feb 2019 23:46:42 +0100, Andreas Beckmann  wrote:
> On 2019-02-08 21:27, Stephen Kitt wrote:
> > It was staring me in the face: you tested with 0.9.904-2 and marked the
> > bug  
> 
> Damned race conditions ...
> I didn't realize that there were two uploads in a short timeframe. I
> first saw your closing message, then I found the bug showing up again in
> my latest test run (but your -3 upload hadn't reached my mirror, yet,
> even at the time I reopened the bug), so it was only -2 getting tested
> 
> Running tests again, but the package itself looks good now in -3 :-)

Cool, thanks for checking!

> > as found in 0.9.904-3 (which is where the bug was fixed).  
> 
> copy+paste from the subject, since that obviously must have been the
> failing version :-(
> 
> > There’s a few hours I won’t be getting back :-(.  
> 
> Sorry for that.

I wasn’t annoyed at you, I was annoyed at myself — if I’d ported the fix to
both branches when you first filed the bug, I wouldn’t have wasted your time
or mine!

Thanks for all your QA work, I certainly appreciate it.

Regards,

Stephen


pgpG6He52Z2ed.pgp
Description: OpenPGP digital signature


Bug#921843: discosnp has unsatisfiable dependencies

2019-02-09 Thread Matthias Klose
Package: src:discosnp
Version: 2.3.0-1
Severity: serious
Tags: sid buster

Impossible Depends: discosnp -> gatb-core/amd64
Impossible Depends: discosnp -> gatb-core/arm64
Impossible Depends: discosnp -> gatb-core/i386
Impossible Depends: discosnp -> gatb-core/mips64el
Impossible Depends: discosnp -> gatb-core/ppc64el
Impossible Depends: discosnp -> gatb-core/s390x



Processed: Re: pyzo: missing dependancy to python3-pkg-resources

2019-02-09 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #917085 {Done: Adrian Bunk } [src:pyzo] pyzo: missing 
dependancy to python3-pkg-resources
Added tag(s) pending.

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



Bug#917085: pyzo: missing dependancy to python3-pkg-resources

2019-02-09 Thread Andreas Beckmann
Followup-For: Bug #917085
Control: tag -1 pending

Hi,

I've backported the fix to stretch and file a stretch-pu-request:
https://bugs.debian.org/921844


Andreas



Processed: tagging 909497, reassign 869815 to libvdpau1, found 858693 in 4.0.0+dfsg1-1, tagging 858693 ...

2019-02-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 909497 - moreinfo
Bug #909497 {Done: Andreas Beckmann } [nvidia-cuda-toolkit] 
CUDA 10 available now
Removed tag(s) moreinfo.
> reassign 869815 libvdpau1
Bug #869815 [vdpauinfo] libvdpau_i965.so: cannot open shared object file: No 
such file or directory
Bug reassigned from package 'vdpauinfo' to 'libvdpau1'.
No longer marked as found in versions vdpauinfo/1.0-1.
Ignoring request to alter fixed versions of bug #869815 to the same values 
previously set
> found 858693 4.0.0+dfsg1-1
Bug #858693 {Done: Thomas Goirand } [congress-server] 
congress-server: Missing dependency net-tools
Marked as found in versions congress/4.0.0+dfsg1-1.
> tags 858693 - stretch
Bug #858693 {Done: Thomas Goirand } [congress-server] 
congress-server: Missing dependency net-tools
Removed tag(s) stretch.
> tags 908947 - stretch
Bug #908947 [youtube-dl] youtube-dl: backport youtube-dl to recent version for 
stretch
Removed tag(s) stretch.
> fixed 908947 2019.01.17-1
Bug #908947 [youtube-dl] youtube-dl: backport youtube-dl to recent version for 
stretch
Marked as fixed in versions youtube-dl/2019.01.17-1.
> fixed 908947 2019.01.17-1~bpo9+1
Bug #908947 [youtube-dl] youtube-dl: backport youtube-dl to recent version for 
stretch
Marked as fixed in versions youtube-dl/2019.01.17-1~bpo9+1.
> tags 918163 - stretch
Bug #918163 [xul-ext-sieve] Broken in Stretch
Removed tag(s) stretch.
> fixed 918163 0.3.0+dfsg-1
Bug #918163 [xul-ext-sieve] Broken in Stretch
Marked as fixed in versions sieve-extension/0.3.0+dfsg-1.
> tags 884632 - stretch
Bug #884632 [rtv] rtv crashes when viewing submission
Removed tag(s) stretch.
> tags 921712 + sid
Bug #921712 {Done: Julien Cristau } [libxinerama1] 
libgtk2.0-0-udeb: wrong dependency while building on buster based system
Bug #921715 {Done: Julien Cristau } [libxinerama1] 
libgtk2.0-0-udeb: wrong dependency while building on buster based system
Added tag(s) sid.
Added tag(s) sid.
> reassign 878772 src:mpqc 2.3.1-16
Bug #878772 {Done: Andreas Tille } [mpqc-openmpi] please drop 
transitional package mpqc-openmpi
Bug reassigned from package 'mpqc-openmpi' to 'src:mpqc'.
No longer marked as found in versions mpqc/2.3.1-16.
No longer marked as fixed in versions mpqc/2.3.1-19.
Bug #878772 {Done: Andreas Tille } [src:mpqc] please drop 
transitional package mpqc-openmpi
Marked as found in versions mpqc/2.3.1-16.
> fixed 878772 2.3.1-19
Bug #878772 {Done: Andreas Tille } [src:mpqc] please drop 
transitional package mpqc-openmpi
Marked as fixed in versions mpqc/2.3.1-19.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
858693: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858693
869815: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=869815
878772: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878772
884632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884632
908947: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908947
909497: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909497
918163: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918163
921712: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921712
921715: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921715
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#921850: unnecessary b-d's libisl-0.18-dev and libcloog-isl-dev, to be removed for buster

2019-02-09 Thread Matthias Klose
Package: src:binutils-arm-none-eabi
Version: 10
Severity: serious
Tags: sid buster

unnecessary b-d's libisl-0.18-dev and libcloog-isl-dev, to be removed for buster

Both b-d's are not needed. Just remove them.



Bug#921848: please remove unnecessary b-d cloog-ppl

2019-02-09 Thread Matthias Klose
Package: src:fact++
Version: 1.6.5~dfsg-1
Severity: serious
Tags: sid buster

I'd like to remove cloog-ppl from the sid/buster, therefore the severity of this
report.  I can't see yet any use of cloog-ppl during the package build.  So
please check if this package is working without it.  If not, then please
downgrade the severity, and think about using libisl. cloog-ppl isn't maintained
anymore upstream.



Bug#921851: unnecessary b-d's libisl-0.18-dev and libcloog-isl-dev, to be removed for buster

2019-02-09 Thread Matthias Klose
Package: src:binutils-xtensa-lx106
Version: 1
Severity: serious
Tags: sid buster

unnecessary b-d's libisl-0.18-dev and libcloog-isl-dev, to be removed for buster

Both b-d's are not needed. Just remove them.



Bug#921852: unnecessary b-d on libcloog-isl-dev, to be removed in buster

2019-02-09 Thread Matthias Klose
Package: src:newlib
Version: 3.0.0.20180831-1
Severity: serious
Tags: sid buster

unnecessary b-d on libcloog-isl-dev, to be removed in buster. Please just 
remove.



Bug#921853: unnecessary b-d on libcloog-isl-dev, to be removed in buster

2019-02-09 Thread Matthias Klose
Package: src:gdb-mingw-w64
Version: 10.7
Severity: serious
Tags: sid buster

unnecessary b-d on libcloog-isl-dev, to be removed in buster.  This is not used
in gdb.



Bug#921854: outdated b-d's on libisl-0.18-dev and libcloog-isl-dev, to be removed for buster

2019-02-09 Thread Matthias Klose
Package: src:gcc-arm-none-eabi
Version: 15:7-2018-q2-5
Severity: serious
Tags: sid buster

Looks like the packaging didn't see any update since GCC 5. outdated b-d's on
libisl-0.18-dev and libcloog-isl-dev. Use libisl-dev.

I didn't check what else wasn't updated for GCC 8 ...



Bug#921855: outdated b-d's on libisl-0.18-dev and libcloog-isl-dev, to be removed in buster

2019-02-09 Thread Matthias Klose
Package: src:gcc-xtensa-lx106
Version: 1
Severity: serious
Tags: sid buster

Looks like the packaging didn't see any update since GCC 5. outdated b-d's on
libisl-0.18-dev and libcloog-isl-dev. Use libisl-dev.

I didn't check what else wasn't updated for GCC 8 ...



Bug#921856: outdated b-d's on,libisl-0.18-dev and libcloog-isl-dev, to be removed in buster

2019-02-09 Thread Matthias Klose
Package: src:libstdc++-arm-none-eabi
Version: 11
Severity: serious
Tags: sid buster

Looks like the packaging didn't see any update since GCC 5. outdated b-d's on
libisl-0.18-dev and libcloog-isl-dev. Use libisl-dev.

I didn't check what else wasn't updated for GCC 8 ...



Bug#921725: libu2f-host: CVE-2018-20340

2019-02-09 Thread Nicolas Braud-Santoni
On Sat, Feb 09, 2019 at 11:19:47AM +0100, Sébastien Delafond wrote:
> On Feb/08, Nicolas Braud-Santoni wrote:
> > I backported the fix and prepared an upload.
> > The debdiff is attached, and the commands used to produced it are 
> > documented below.
> > 
> > May I proceed with an upload to security-master?
> 
> It looks OK to me, so if it passes testing on your end please upload to
> security-master (don't forget to use -sa as it will be new there).

OK.  My first dput didn't seem to include the orig tarball, even though I
built with --force-orig-source and the .dsc mentionned the orig tarball.

I will reupload as soon as I figure it out  :)


Best,

  nicoo


signature.asc
Description: PGP signature


Processed: affects 921718

2019-02-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> affects 921718 ruby-rails
Bug #921718 [ruby-spring] spring is broken 
/usr/lib/ruby/vendor_ruby/spring/client/run.rb:76:in `spawn': No such file or 
directory - /usr/lib/ruby/bin/spring (Errno::ENOENT)
Added indication that 921718 affects ruby-rails
> thanks
Stopping processing here.

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



Bug#921725: libu2f-host: CVE-2018-20340

2019-02-09 Thread Nicolas Braud-Santoni
On Sat, Feb 09, 2019 at 01:54:19PM +0100, Nicolas Braud-Santoni wrote:
> On Sat, Feb 09, 2019 at 11:19:47AM +0100, Sébastien Delafond wrote:
> > don't forget to use -sa as it will be new there
> 
> OK.  My first dput didn't seem to include the orig tarball, even though I
> built with --force-orig-source and the .dsc mentionned the orig tarball.
> 
> I will reupload as soon as I figure it out  :)

Ah, I was bitten in the arse by #884428 again.
The upload to security-master should now be fine  :)

Sorry for accidentally duplicating your work, I didn't realise you had prepared
a backported fix for stable before the issue went public  :)


Best,

  nicoo


signature.asc
Description: PGP signature


Bug#918850: libmypaint: FTBFS with Sphinx 1.8: No module named 'sphinx.ext.pngmath'

2019-02-09 Thread Sascha Steinbiss
user debian-rele...@lists.debian.org
usertag 918850 + bsp-2019-02-de-berlin
thank you

Hi all,

Greetings from the BSP at the DCSO office in Berlin.

> libmypaint fails to build with Sphinx 1.8, currently available in
> experimental:
[...]
> The pngmath extension was deprecated in Sphinx 1.4 and has been removed [1]
> in Sphinx 1.8. The recommended alternative is sphinx.ext.imgmath [2] which
> also has SVG support in addition to PNG.
> 
> To me it looks like this extension is unused anyway: there are no “.. math::”
> directives or “:math:” roles, and libmypaint-doc does not have any generated
> PNG images. So this extension can be simply removed from extensions in
> conf.py.

I have incorporated this fix and will upload a non-maintainer upload
(libmypaint_1.3.0-2.1) to DELAYED with a 5 day delay. See attached patch
for an overview.

Cheers
Sascha

diff --git a/debian/changelog b/debian/changelog
index 3bc3051..6a01797 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,15 @@
+libmypaint (1.3.0-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Remove unused Sphinx extension. Thanks to Dmitry Shachnev for the hint.
+Closes: #918850
+  * Make build reproducible. Thanks to Chris Lamb for the patch.
+Closes: #895401
+  * Reference correct homepage. Thanks to Chris Lamb for the patch.
+Closes: #895402
+
+ -- Sascha Steinbiss   Sat, 09 Feb 2019 12:22:40 +0100
+
 libmypaint (1.3.0-2) unstable; urgency=medium
 
   * Add Conflicts: mypaint-data to libmypaint-common. See bug 894757
diff --git a/debian/control b/debian/control
index ed96ddf..afe2bd0 100644
--- a/debian/control
+++ b/debian/control
@@ -19,7 +19,7 @@ Build-Depends: autoconf-archive,
 Standards-Version: 4.1.3
 Vcs-Browser: https://salsa.debian.org/multimedia-team/libmypaint
 Vcs-Git: https://salsa.debian.org/multimedia-team/libmypaint.git
-Homepage: https://github.com/Jehan/mypaint-brushes
+Homepage: https://github.com/Jehan/mypaint
 
 Package: libmypaint-1.3-0
 Architecture: any
diff --git a/debian/patches/disable-sphinx-math-extension.patch b/debian/patches/disable-sphinx-math-extension.patch
new file mode 100644
index 000..19286b3
--- /dev/null
+++ b/debian/patches/disable-sphinx-math-extension.patch
@@ -0,0 +1,17 @@
+Description: remove unused Sphinx extension
+ This package uses a deprecated and later removed Sphinx extension
+ that led to a FTBFS with recent Sphinx versions.
+ Since it wasn't used in the documentation anyway, it should be safe to remove.
+Author: Sascha Steinbiss 
+Last-Update: 2019-02-09
+--- a/doc/source/conf.py
 b/doc/source/conf.py
+@@ -27,7 +27,7 @@
+ 
+ # Add any Sphinx extension module names here, as strings. They can be extensions
+ # coming with Sphinx (named 'sphinx.ext.*') or your custom ones.
+-extensions = ['sphinx.ext.autodoc', 'sphinx.ext.doctest', 'sphinx.ext.intersphinx', 'sphinx.ext.todo', 'sphinx.ext.coverage', 'sphinx.ext.pngmath', 'sphinx.ext.ifconfig', 'sphinx.ext.viewcode']
++extensions = ['sphinx.ext.autodoc', 'sphinx.ext.doctest', 'sphinx.ext.intersphinx', 'sphinx.ext.todo', 'sphinx.ext.coverage', 'sphinx.ext.ifconfig', 'sphinx.ext.viewcode']
+ 
+ # Breathe setup, for integrating doxygen content
+ extensions.append('breathe')
diff --git a/debian/patches/reproducible-build.patch b/debian/patches/reproducible-build.patch
new file mode 100644
index 000..8a0b6a5
--- /dev/null
+++ b/debian/patches/reproducible-build.patch
@@ -0,0 +1,15 @@
+Description: Make the build reproducible
+Author: Chris Lamb 
+Last-Update: 2018-04-11
+
+--- libmypaint-1.3.0.orig/doc/Doxyfile
 libmypaint-1.3.0/doc/Doxyfile
+@@ -119,7 +119,7 @@ INLINE_INHERITED_MEMB  = NO
+ # path before files name in the file list and in the header files. If set
+ # to NO the shortest path that makes the file name unique will be used.
+ 
+-FULL_PATH_NAMES= YES
++FULL_PATH_NAMES= NO
+ 
+ # If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag
+ # can be used to strip a user-defined part of the path. Stripping is
diff --git a/debian/patches/series b/debian/patches/series
index 1e8becf..e298399 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1 +1,3 @@
 dont-require-m4macros.patch
+reproducible-build.patch
+disable-sphinx-math-extension.patch


Processed: fixed 847642 in 2.7.5-2+deb9u1

2019-02-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> fixed 847642 2.7.5-2+deb9u1
Bug #847642 {Done: Jonas Smedegaard } [node-uglify] node-uglify: 
neither manpage nor --help output useful
Bug #847643 {Done: Jonas Smedegaard } [node-uglify] node-uglify: 
neither manpage nor --help output useful
Marked as fixed in versions uglifyjs/2.7.5-2+deb9u1.
Marked as fixed in versions uglifyjs/2.7.5-2+deb9u1.
> thanks
Stopping processing here.

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



Bug#916151: Fix, NMU

2019-02-09 Thread Hilko Bengen
user debian-rele...@lists.debian.org
usertag 916151 + bsp-2019-02-de-berlin
usertag 920358 + bsp-2019-02-de-berlin
thank you

Dear maintainers,

Greetings from the BSP at the DCSO office in Berlin.

I have fixed this bug and NMU'd kopete/17.08.3-2.1 to DELAYED/2. Please
feel free to reschedule or cancel my upload as you see fit. I have
attached the diff.

Cheers,
-Hilko
>From 0f24a751b7acc0952152739a5398c8140f02c098 Mon Sep 17 00:00:00 2001
From: Hilko Bengen 
Date: Sat, 9 Feb 2019 14:43:38 +0100
Subject: [PATCH] Add missing include, fixing FTBFS with glibc 2.28 (Closes:
 #916151, #920358)

---
 debian/changelog |  8 
 debian/patches/fix-glibc2.28-ftbfs.patch | 12 
 debian/patches/series|  1 +
 3 files changed, 21 insertions(+)
 create mode 100644 debian/patches/fix-glibc2.28-ftbfs.patch

diff --git a/debian/changelog b/debian/changelog
index 8419975..af578c8 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,11 @@
+kopete (4:17.08.3-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add missing include, fixing FTBFS with glibc 2.28 (Closes: #916151,
+#920358)
+
+ -- Hilko Bengen   Sat, 09 Feb 2019 12:53:00 +0100
+
 kopete (4:17.08.3-2) unstable; urgency=medium
 
   * Team upload.
diff --git a/debian/patches/fix-glibc2.28-ftbfs.patch b/debian/patches/fix-glibc2.28-ftbfs.patch
new file mode 100644
index 000..9287177
--- /dev/null
+++ b/debian/patches/fix-glibc2.28-ftbfs.patch
@@ -0,0 +1,12 @@
+Index: kopete/protocols/jabber/libjingle/talk/session/phone/v4llookup.cc
+===
+--- kopete.orig/protocols/jabber/libjingle/talk/session/phone/v4llookup.cc
 kopete/protocols/jabber/libjingle/talk/session/phone/v4llookup.cc
+@@ -15,6 +15,7 @@
+ #include 
+ #include 
+ #include 
++#include 
+ #include 
+ 
+ #include 
diff --git a/debian/patches/series b/debian/patches/series
index 03598d1..41cc671 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,3 +1,4 @@
 kopete-17.08.3-openssl-1.1.patch
 fix-mediastreamer-ftbfs.patch
 kopete-srtp2.patch
+fix-glibc2.28-ftbfs.patch
-- 
2.19.1



Bug#921781: fis-gtm: FTBFS (dh_auto_configure fails)

2019-02-09 Thread GCS
On Sat, Feb 9, 2019 at 9:13 AM Andreas Tille  wrote:
> The naive approach to simply remove the icu-config
> check from CMakeLists.txt ended up in
>
> ...
> -- Installing: 
> /build/fis-gtm-6.3-005/debian/fis-gtm-6.3-005-stage1/usr/lib/x86_64-linux-gnu/fis-gtm/V6.3-005_x86_64/GDETEMPL.o
> CMake Error at cmake_install.cmake:763 (file):
>   file INSTALL cannot find
>   "/build/fis-gtm-6.3-005/obj-x86_64-linux-gnu/utf8/GDEGET.o".
 This happens with and without icu-config (rebuilt the last ICU one
which had icu-config) as well.
Reason that you didn't recognize:
%GTM-E-GTMDISTUNVERIF, Environment variable $gtm_dist
([builddir]/fis-gtm-6.3-005/obj-x86_64-linux-gnu) could not be
verified against the executables path
([builddir]/fis-gtm-6.3-005/obj-x86_64-linux-gnu/mumps).
But it only happens in my dirty chroot. Normal pbuilder build with my
ICU patch can build your package. Consult the gtm_dist issue with your
upstream if you want.

Laszlo/GCS



Processed: Re: /usr/bin/sc-libtool: Command not found

2019-02-09 Thread Debian Bug Tracking System
Processing control commands:

> tag -1 pending
Bug #873719 {Done: Andreas Tille } [libsc-dev] 
/usr/bin/sc-libtool: Command not found
Added tag(s) pending.

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



Bug#873719: /usr/bin/sc-libtool: Command not found

2019-02-09 Thread Andreas Beckmann
Followup-For: Bug #873719
Control: tag -1 pending

Hi,

I just backported the fix to stretch, prepared a stretch-pu request and
uploaded the package: https://bugs.debian.org/921864


Andreas



Bug#858693: Triaging: closing this bug

2019-02-09 Thread Andreas Beckmann
On Tue, 8 Jan 2019 09:12:34 +0100 Thomas Goirand  wrote:
> I attempted to get this fixed, but after a year, I'm still waiting for
> the release team approval. I'm now giving up... Anyone who wants  to see

You seem to have missed the approval in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883897#24

Today would be a good day to upload to get this fixed in the next point
release.


Andreas



Bug#884721: rsyncrypto: Segmentation fault with --delete

2019-02-09 Thread Sascha Steinbiss
user debian-rele...@lists.debian.org

usertag 884721 + bsp-2019-02-de-berlin
usertag 912051 + bsp-2019-02-de-berlin
thank you

Dear maintainers,

Greetings from the BSP at the DCSO office in Berlin.

I have fixed this bug and NMU'd rsyncrypto_1.14-1.1 to DELAYED/5. Please
feel free to reschedule or cancel my upload as you see fit. I have
attached the diff.

Cheers
Sascha
diff -Nru rsyncrypto-1.14/debian/changelog rsyncrypto-1.14/debian/changelog
--- rsyncrypto-1.14/debian/changelog	2017-09-06 19:30:22.0 +0200
+++ rsyncrypto-1.14/debian/changelog	2019-02-09 15:11:50.0 +0100
@@ -1,3 +1,13 @@
+rsyncrypto (1.14-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add explicit build dependency on automake-1.15.
+Closes: #912051   
+  * Fix segfault with --delete. Thanks to Chris Boot for the patch.
+Closes: #884721
+
+ -- Sascha Steinbiss   Sat, 09 Feb 2019 15:11:50 +0100
+
 rsyncrypto (1.14-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru rsyncrypto-1.14/debian/control rsyncrypto-1.14/debian/control
--- rsyncrypto-1.14/debian/control	2017-09-06 19:30:22.0 +0200
+++ rsyncrypto-1.14/debian/control	2019-02-09 15:11:50.0 +0100
@@ -2,7 +2,7 @@
 Section: utils
 Priority: optional
 Maintainer: Shachar Shemesh 
-Build-Depends: debhelper (>= 9), libssl-dev (>= 1.1.0), libargtable2-dev, autotools-dev
+Build-Depends: debhelper (>= 9), libssl-dev (>= 1.1.0), libargtable2-dev, autotools-dev, automake-1.15
 Standards-Version: 4.1.0
 Homepage: https://rsyncrypto.lingnu.com
 
diff -Nru rsyncrypto-1.14/debian/patches/fix_segfault_in_unlink rsyncrypto-1.14/debian/patches/fix_segfault_in_unlink
--- rsyncrypto-1.14/debian/patches/fix_segfault_in_unlink	1970-01-01 01:00:00.0 +0100
+++ rsyncrypto-1.14/debian/patches/fix_segfault_in_unlink	2019-02-09 15:11:50.0 +0100
@@ -0,0 +1,17 @@
+Description: fix segfault
+ This fixes a crash when using rsyncrypto to refresh an
+ encrypted directory tree with --delete enabled.
+ This happens because of an infinite recursion in autofd::unlink()
+Author: Chris Boot 
+Last-Update: 2019-02-09
+--- a/autofd.h
 b/autofd.h
+@@ -216,7 +216,7 @@
+ // unless it failed with ENOENT - the file already doesn't exist
+ static int unlink(const char *pathname)
+ {
+-bool success=unlink( pathname )==0;
++bool success=::unlink( pathname )==0;
+ if( !success && errno!=ENOENT )
+ throw rscerror("Erasing file", errno, pathname );
+ 
diff -Nru rsyncrypto-1.14/debian/patches/series rsyncrypto-1.14/debian/patches/series
--- rsyncrypto-1.14/debian/patches/series	2017-09-06 19:30:22.0 +0200
+++ rsyncrypto-1.14/debian/patches/series	2019-02-09 15:11:50.0 +0100
@@ -1 +1,2 @@
 remove_precompiled_headers
+fix_segfault_in_unlink


Bug#910757: gnulib: diff for NMU version 20140202+stable-3.1

2019-02-09 Thread Salvatore Bonaccorso
Control: tags 910757 + patch
Control: tags 910757 + pending


Dear maintainer,

I've prepared an NMU for gnulib (versioned as 20140202+stable-3.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Tested 

CC='gcc -fsanitize=address -g -O0' gnulib-tool --test vasnprintf 
vasnprintf-posix

before and after patching.

Regards,
Salvatore
diff -Nru gnulib-20140202+stable/debian/changelog gnulib-20140202+stable/debian/changelog
--- gnulib-20140202+stable/debian/changelog	2018-06-23 09:23:11.0 +0200
+++ gnulib-20140202+stable/debian/changelog	2019-02-09 11:11:06.0 +0100
@@ -1,3 +1,10 @@
+gnulib (20140202+stable-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * vasnprintf: Fix heap memory overrun bug (CVE-2018-17942) (Closes: #910757)
+
+ -- Salvatore Bonaccorso   Sat, 09 Feb 2019 11:11:06 +0100
+
 gnulib (20140202+stable-3) unstable; urgency=medium
 
   * Update copyright info:
diff -Nru gnulib-20140202+stable/debian/patches/03-vasnprintf-Fix-heap-memory-overrun-bug.patch gnulib-20140202+stable/debian/patches/03-vasnprintf-Fix-heap-memory-overrun-bug.patch
--- gnulib-20140202+stable/debian/patches/03-vasnprintf-Fix-heap-memory-overrun-bug.patch	1970-01-01 01:00:00.0 +0100
+++ gnulib-20140202+stable/debian/patches/03-vasnprintf-Fix-heap-memory-overrun-bug.patch	2019-02-09 11:11:06.0 +0100
@@ -0,0 +1,70 @@
+From: Bruno Haible 
+Date: Sun, 23 Sep 2018 14:13:52 +0200
+Subject: vasnprintf: Fix heap memory overrun bug.
+Origin: https://github.com/coreutils/gnulib/commit/278b4175c9d7dd47c1a3071554aac02add3b3c35
+Bug-Debian-Security: https://security-tracker.debian.org/tracker/CVE-2018-17942
+Bug-Debian: https://bugs.debian.org/910757
+Bug: https://lists.gnu.org/archive/html/bug-gnulib/2018-09/msg00107.html
+
+Reported by Ben Pfaff  in
+.
+
+* lib/vasnprintf.c (convert_to_decimal): Allocate one more byte of
+memory.
+* tests/test-vasnprintf.c (test_function): Add another test.
+---
+ ChangeLog   |  9 +
+ lib/vasnprintf.c|  4 +++-
+ tests/test-vasnprintf.c | 21 -
+ 3 files changed, 32 insertions(+), 2 deletions(-)
+
+diff --git a/lib/vasnprintf.c b/lib/vasnprintf.c
+index 56ffbe308a6a..30d021b2847d 100644
+--- a/lib/vasnprintf.c
 b/lib/vasnprintf.c
+@@ -860,7 +860,9 @@ convert_to_decimal (mpn_t a, size_t extra_zeroes)
+   size_t a_len = a.nlimbs;
+   /* 0.03345 is slightly larger than log(2)/(9*log(10)).  */
+   size_t c_len = 9 * ((size_t)(a_len * (GMP_LIMB_BITS * 0.03345f)) + 1);
+-  char *c_ptr = (char *) malloc (xsum (c_len, extra_zeroes));
++  /* We need extra_zeroes bytes for zeroes, followed by c_len bytes for the
++ digits of a, followed by 1 byte for the terminating NUL.  */
++  char *c_ptr = (char *) malloc (xsum (xsum (extra_zeroes, c_len), 1));
+   if (c_ptr != NULL)
+ {
+   char *d_ptr = c_ptr;
+diff --git a/tests/test-vasnprintf.c b/tests/test-vasnprintf.c
+index 19731bc93378..93d81d7041c5 100644
+--- a/tests/test-vasnprintf.c
 b/tests/test-vasnprintf.c
+@@ -53,7 +53,26 @@ test_function (char * (*my_asnprintf) (char *, size_t *, const char *, ...))
+   ASSERT (result != NULL);
+   ASSERT (strcmp (result, "12345") == 0);
+   ASSERT (length == 5);
+-  if (size < 6)
++  if (size < 5 + 1)
++ASSERT (result != buf);
++  ASSERT (memcmp (buf + size, &"DEADBEEF"[size], 8 - size) == 0);
++  if (result != buf)
++free (result);
++}
++
++  /* Note: This test assumes IEEE 754 representation of 'double' floats.  */
++  for (size = 0; size <= 8; size++)
++{
++  size_t length;
++  char *result;
++
++  memcpy (buf, "DEADBEEF", 8);
++  length = size;
++  result = my_asnprintf (buf, &length, "%2.0f", 1.6314159265358979e+125);
++  ASSERT (result != NULL);
++  ASSERT (strcmp (result, "16314159265358979021572935093952849305752959889973415177246818626842325068536614838678161083520756952076273094236944990208") == 0);
++  ASSERT (length == 126);
++  if (size < 126 + 1)
+ ASSERT (result != buf);
+   ASSERT (memcmp (buf + size, &"DEADBEEF"[size], 8 - size) == 0);
+   if (result != buf)
+-- 
+2.20.1
+
diff -Nru gnulib-20140202+stable/debian/patches/series gnulib-20140202+stable/debian/patches/series
--- gnulib-20140202+stable/debian/patches/series	2018-06-22 10:26:47.0 +0200
+++ gnulib-20140202+stable/debian/patches/series	2019-02-09 11:11:06.0 +0100
@@ -1,2 +1,3 @@
 01-gnulib-directory.patch
 02-shebang.patch
+03-vasnprintf-Fix-heap-memory-overrun-bug.patch


Processed: gnulib: diff for NMU version 20140202+stable-3.1

2019-02-09 Thread Debian Bug Tracking System
Processing control commands:

> tags 910757 + patch
Bug #910757 [gnulib] gnulib: CVE-2018-17942 heap-based buffer overflow
Added tag(s) patch.
> tags 910757 + pending
Bug #910757 [gnulib] gnulib: CVE-2018-17942 heap-based buffer overflow
Added tag(s) pending.

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



Bug#921777: bugwarrior: FTBFS (failing tests)

2019-02-09 Thread Nicolas Schier
tag 921777 + patch
usertag 921777 + bsp-2019-02-de-berlin
thank you

Hei,

> I tried to build this package in buster but it failed:
> [...]
> pkg_resources.VersionConflict: (future 0.16.0 
> (/usr/lib/python3/dist-packages), Requirement.parse('future!=0.16.0'))

the build dependency ('future!=0.16.0') is explicitly given in
setup.py, originating from the latest upstream import.

When removing the problematic line (cp. attached patch), it seems to 
build and run the tests again.  Is this line really still required?

Kind regards,
Nicolas


From 8425df9da9b02151e31b8ea1bf5da5df73b907a2 Mon Sep 17 00:00:00 2001
From: Nicolas Schier 
Date: Sat, 9 Feb 2019 12:32:38 +0100
Subject: [PATCH] setup.py: Remove future!=0.16.0 dependency (Closes: #921777)

The 'future!=0.16.0' dependency prevents building the package on buster.
There seems to be no reason for this dependency (anymore)?
---
 setup.py | 1 -
 1 file changed, 1 deletion(-)

diff --git a/setup.py b/setup.py
index c2ad788..5246ff1 100644
--- a/setup.py
+++ b/setup.py
@@ -38,7 +38,6 @@ setup(name='bugwarrior',
   "dogpile.cache>=0.5.3",
   "lockfile>=0.9.1",
   "click",
-  "future!=0.16.0",
   ],
   extras_require=dict(
   keyring=["keyring"],
-- 
2.20.1



signature.asc
Description: PGP signature


Bug#915995: NMU, patch

2019-02-09 Thread Hilko Bengen
user debian-rele...@lists.debian.org
usertag 915995 + bsp-2019-02-de-berlin
thank you

Dear maintainers,

Greetings from the BSP at the DCSO office in Berlin.

I have NMU'd nfs-utils/1:1.3.4-2.4 to DELAYED/5, fixing this bug. Please
feel free to reschedule or cancel my upload as you see fit. I have
attached the diffs based upon the last Git commit in Salsa.

Cheers,
-Hilko

>From fe2dd58a3bbee3369a2d44da6e997f5a5e0ff88f Mon Sep 17 00:00:00 2001
From: Hilko Bengen 
Date: Sat, 9 Feb 2019 15:25:20 +0100
Subject: [PATCH 1/2] Add missing include, fixing FTBFS with glibc 2.28
 (Closes: #915995)

---
 debian/patches/fix-glibc2.28-ftbfs.patch | 12 
 debian/patches/series|  1 +
 2 files changed, 13 insertions(+)
 create mode 100644 debian/patches/fix-glibc2.28-ftbfs.patch

diff --git a/debian/patches/fix-glibc2.28-ftbfs.patch b/debian/patches/fix-glibc2.28-ftbfs.patch
new file mode 100644
index 000..a0bfdf5
--- /dev/null
+++ b/debian/patches/fix-glibc2.28-ftbfs.patch
@@ -0,0 +1,12 @@
+Index: nfs-utils/utils/blkmapd/device-discovery.c
+===
+--- nfs-utils.orig/utils/blkmapd/device-discovery.c
 nfs-utils/utils/blkmapd/device-discovery.c
+@@ -49,6 +49,7 @@
+ #include 
+ #include 
+ #include 
++#include 
+ 
+ #include "device-discovery.h"
+ #include "xcommon.h"
diff --git a/debian/patches/series b/debian/patches/series
index 9733125..b1be644 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -12,3 +12,4 @@ unbreak-gssd-rpc_pipefs-run.patch
 29-start-statd-fd-9.patch
 0001-rpc.c-added-include-file-so-UINT16_MAX-is-defined.patch
 30-remove-whitespace-service.patch
+fix-glibc2.28-ftbfs.patch
-- 
2.19.1

>From cf204d95a678fb945def91a9aaae16382b228e47 Mon Sep 17 00:00:00 2001
From: Hilko Bengen 
Date: Sat, 9 Feb 2019 15:31:22 +0100
Subject: [PATCH 2/2] Debian release 1:1.3.4-2.4

---
 debian/changelog | 8 ++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index f9757ba..bd57693 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,9 +1,13 @@
-nfs-utils (1:1.3.4-3) UNRELEASED; urgency=medium
+nfs-utils (1:1.3.4-2.4) unstable; urgency=medium
 
+  [ Laurent Bigonville ]
   * debian/control: Downgrade the priority to optional to match the override
 file
 
- -- Laurent Bigonville   Sat, 20 Oct 2018 15:53:29 +0200
+  [ Hilko Bengen ]
+  * Add missing include, fixing FTBFS with glibc 2.28 (Closes: #915995)
+
+ -- Hilko Bengen   Sat, 09 Feb 2019 15:26:27 +0100
 
 nfs-utils (1:1.3.4-2.3) unstable; urgency=medium
 
-- 
2.19.1



Processed: Re: Bug#921843: discosnp has unsatisfiable dependencies

2019-02-09 Thread Debian Bug Tracking System
Processing control commands:

> tags -1 help moreinfo
Bug #921843 [src:discosnp] discosnp has unsatisfiable dependencies
Added tag(s) help and moreinfo.

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



Bug#921843: discosnp has unsatisfiable dependencies

2019-02-09 Thread Andreas Tille
Control: tags -1 help moreinfo

Hi,

I really wonder why gatb-core should be missing.  According to
tracker[1] gatb-core is in testing and the build logs[2] are specifying
exactly those architectures as successfully installed that you claim
missing (in agreement with discosnp tracker page[3] admittedly but
not more enlightening to me).

Any idea what might be wrong here and how to fix this?

Kind regards

   Andreas.


[1] https://tracker.debian.org/pkg/gatb-core
[2] https://buildd.debian.org/status/package.php?p=gatb-core
[3] https://tracker.debian.org/pkg/discosnp

On Sat, Feb 09, 2019 at 12:48:07PM +0100, Matthias Klose wrote:
> Package: src:discosnp
> Version: 2.3.0-1
> Severity: serious
> Tags: sid buster
> 
> Impossible Depends: discosnp -> gatb-core/amd64
> Impossible Depends: discosnp -> gatb-core/arm64
> Impossible Depends: discosnp -> gatb-core/i386
> Impossible Depends: discosnp -> gatb-core/mips64el
> Impossible Depends: discosnp -> gatb-core/ppc64el
> Impossible Depends: discosnp -> gatb-core/s390x
> 
> ___
> Debian-med-packaging mailing list
> debian-med-packag...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging

-- 
http://fam-tille.de



Bug#916858: tagging 916858

2019-02-09 Thread Andreas Beckmann
On Thu, 07 Feb 2019 14:57:19 +0200 Adrian Bunk  wrote:
> tags 916858 + pending
> thanks

#916858 supercollider-emacs: fails to install with xemacs21

You are working on a stretch-pu? Or why is this tagged pending?


Andreas



Bug#916858: tagging 916858

2019-02-09 Thread Adrian Bunk
On Sat, Feb 09, 2019 at 03:58:12PM +0100, Andreas Beckmann wrote:
> On Thu, 07 Feb 2019 14:57:19 +0200 Adrian Bunk  wrote:
> > tags 916858 + pending
> > thanks
> 
> #916858 supercollider-emacs: fails to install with xemacs21
> 
> You are working on a stretch-pu? Or why is this tagged pending?

testing migration was pending on other supercollider changes,
no stretch-pu planned by me.

> Andreas

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#913159: task-kannada-desktop: uninstallable on mips and mipsel

2019-02-09 Thread Debian Bug Tracking System
Processing control commands:

> notfound -1 3.50
Bug #913159 [task-kannada-desktop] task-kannada-desktop: uninstallable on mips 
and mipsel
Ignoring request to alter found versions of bug #913159 to the same values 
previously set

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



Bug#913159: task-kannada-desktop: uninstallable on mips and mipsel

2019-02-09 Thread Holger Wansing
Control: notfound -1 3.50

Holger Wansing  wrote:
> Hi,
> 
> Ivo De Decker  wrote:
> > Control: found -1 3.39
> > 
> > Hi
> > 
> > On Wed, Nov 07, 2018 at 07:19:21PM +0100, Ivo De Decker wrote:
> > > version: 3.47
> > 
> > As kibi noted on IRC, this also affects the version in stretch.
> > 
> > Ivo
> 
> 
> "task-kannada-desktop depends on 'firefox-esr-l10n-kn | firefox-l10n-kn', 
> which
> is not installable on mips and mipsel, because the latest firefox doesn't
> build there (yet)."
> 
> I committed that for Buster now.
> Does this deserve a stable upload for Stretch?

With yesterday's upload of tasksel, this has been fixed for Buster.
Tagging accordingly.

Should we leave this bug open for Stretch?


Holger

-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076



Bug#921839: marked as done (wcslib: FTBFS (LaTeX error))

2019-02-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Feb 2019 15:15:23 +
with message-id 
and subject line Bug#921839: fixed in wcslib 6.2-2
has caused the Debian Bug report #921839,
regarding wcslib: FTBFS (LaTeX error)
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.)


-- 
921839: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921839
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:wcslib
Version: 6.2-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh  build-indep --no-parallel --with autoreconf
   dh_update_autotools_config -i
   debian/rules override_dh_autoreconf
make[1]: Entering directory '/<>'
AUTOHEADER=true dh_autoreconf
make[1]: Leaving directory '/<>'
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- --docdir=$\{prefix\}/share/doc/wcslib-doc
./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu 
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run 
--disable-maintainer-mode --disable-dependency-tracking 
--docdir=\${prefix}/share/doc/wcslib-doc
configure: WARNING: unrecognized options: --disable-silent-rules, 
--disable-maintainer-mode, --disable-dependency-tracking
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu

[... snipped ...]



LaTeX Warning: Reference `wcsunits_8h' on page 20 undefined on input line 22.


LaTeX Warning: Reference `wcsutil_8h' on page 20 undefined on input line 23.


LaTeX Warning: Reference `wtbarr_8h' on page 20 undefined on input line 24.

) (./structcelprm.tex [20] [21] [22]) (./structdisprm.tex [23] [24] [25]
[26]) (./structdpkey.tex [27] [28]) (./structfitskey.tex [29] [30] [31]
[32]) (./structfitskeyid.tex [33]) (./structlinprm.tex [34] [35] [36] [37]
[38]) (./structprjprm.tex [39] [40] [41] [42] [43]) (./structpscard.tex
[44]) (./structpvcard.tex [45]) (./structspcprm.tex [46]
(/usr/share/texlive/texmf-dist/tex/latex/psnfss/ts1pcr.fd) [47] [48])
(./structspxprm.tex [49] [50] [51] [52] [53] [54]) (./structtabprm.tex [55]
[56] [57] [58] [59]) (./structwcserr.tex [60]) (./structwcsprm.tex [61]
[62] [63] [64] [65] [66] [67] [68] [69] [70] [71] [72] [73] [74] [75] [76]
[77] [78] [79] [80]) (./structwtbarr.tex [81] [82]) [83] (./cel_8h.tex
Underfull \hbox (badness 1) in paragraph at lines 3--4

[84] [85]
! Missing } inserted.
 
}
l.168 \end{DoxyEnumFields}
  
? 
! Emergency stop.
 
}
l.168 \end{DoxyEnumFields}
  
!  ==> Fatal error occurred, no output PDF file produced!
Transcript written on refman.log.
make[3]: *** [GNUmakefile:66: ../wcslib.pdf] Error 1
rm doxextr.c
make[3]: Leaving directory '/<>/doxygen'
make[2]: *** [../makedefs:185: all] Error 2
make[2]: Leaving directory '/<>/doxygen'
make[1]: *** [debian/rules:20: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:7: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


(The above is just how the build ends and not necessarily the most relevant 
part)

The build was made in my autobuilder with "dpkg-buildpackage -A"
and it also fails here:

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

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the BTS web page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: wcslib
Source-Version: 6.2-2

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

Debian distribution maintenance software
pp.
Ole Streicher  (supplier of updated wcslib package)

(This message was generated automatically at their request; if

Bug#921786: marked as done (kim-api: FTBFS (F90-F-0000-Internal compiler error. process_formal_arguments: Function argument with mismatched size that is neither integer nor floating-point))

2019-02-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Feb 2019 15:37:36 +
with message-id 
and subject line Bug#921786: fixed in kim-api 2.0~beta2.gita734d1-2
has caused the Debian Bug report #921786,
regarding kim-api: FTBFS (F90-F--Internal compiler error. 
process_formal_arguments: Function argument with mismatched size that is 
neither integer nor floating-point)
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.)


-- 
921786: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921786
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:kim-api
Version: 2.0~beta2.gita734d1-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
mkdir -p /<>/debian/home
dh_auto_configure -- -DKIM_API_BUILD_MODELS_AND_DRIVERS=ON
cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON "-GUnix Makefiles" 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu 
-DKIM_API_BUILD_MODELS_AND_DRIVERS=ON ..
-- The CXX compiler identification is GNU 8.2.0
-- The C compiler identification is GNU 8.2.0
-- The Fortran compiler identification is Flang 99.99.1
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works

[... snipped ...]

/usr/bin/cmake -E touch 
CMakeFiles/kim-api.dir/fortran/src/kim_length_unit_f.f90.o.provides.build
[ 24%] Building Fortran object 
CMakeFiles/kim-api.dir/fortran/src/kim_log_f.f90.o
/usr/bin/f95 -Dkim_api_EXPORTS 
-I"/<>/obj-x86_64-linux-gnu/Fortran_MODULES" 
-I"/<>/obj-x86_64-linux-gnu" -I"/<>/cpp/include" 
-I"/<>/c/include" -I"/<>/cpp/src" 
-I"/<>/fortran/include"  -std=f2003 -Wall -Wextra -pedantic 
-ffree-line-length-none -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -JFortran_MODULES -fPIC   -c 
"/<>/fortran/src/kim_log_f.f90" -o 
CMakeFiles/kim-api.dir/fortran/src/kim_log_f.f90.o
flang: warning: argument unused during compilation: '-ffree-line-length-none' 
[-Wunused-command-line-argument]
/usr/bin/cmake -E cmake_copy_f90_mod Fortran_MODULES/kim_log_f_module.mod 
CMakeFiles/kim-api.dir/kim_log_f_module.mod.stamp Flang
/usr/bin/cmake -E touch 
CMakeFiles/kim-api.dir/fortran/src/kim_log_f.f90.o.provides.build
[ 25%] Building Fortran object 
CMakeFiles/kim-api.dir/fortran/src/kim_log_verbosity_f.f90.o
/usr/bin/f95 -Dkim_api_EXPORTS 
-I"/<>/obj-x86_64-linux-gnu/Fortran_MODULES" 
-I"/<>/obj-x86_64-linux-gnu" -I"/<>/cpp/include" 
-I"/<>/c/include" -I"/<>/cpp/src" 
-I"/<>/fortran/include"  -std=f2003 -Wall -Wextra -pedantic 
-ffree-line-length-none -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -JFortran_MODULES -fPIC   -c 
"/<>/fortran/src/kim_log_verbosity_f.f90" -o 
CMakeFiles/kim-api.dir/fortran/src/kim_log_verbosity_f.f90.o
flang: warning: argument unused during compilation: '-ffree-line-length-none' 
[-Wunused-command-line-argument]
/usr/bin/cmake -E cmake_copy_f90_mod 
Fortran_MODULES/kim_log_verbosity_f_module.mod 
CMakeFiles/kim-api.dir/kim_log_verbosity_f_module.mod.stamp Flang
/usr/bin/cmake -E touch 
CMakeFiles/kim-api.dir/fortran/src/kim_log_verbosity_f.f90.o.provides.build
[ 25%] Building Fortran object 
CMakeFiles/kim-api.dir/fortran/src/kim_model_compute_arguments_create_f.f90.o
/usr/bin/f95 -Dkim_api_EXPORTS 
-I"/<>/obj-x86_64-linux-gnu/Fortran_MODULES" 
-I"/<>/obj-x86_64-linux-gnu" -I"/<>/cpp/include" 
-I"/<>/c/include" -I"/<>/cpp/src" 
-I"/<>/fortran/include"  -std=f2003 -Wall -Wextra -pedantic 
-ffree-line-length-none -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -JFortran_MODULES -fPIC   -c 
"/<>/fortran/src/kim_model_compute_arguments_create_f.f90" -o 
CMakeFiles/kim-api.dir/fortran/src/kim_model_compute_arguments_create_f.f90.o
flang: warning: argument unused during compilation: '-ffree-line-length-none' 
[-Wunused-command-line-argument]
/usr/bin/cmake -E cmake_copy_f90_mod 
Fortran_MODULES/kim_model_compute_arguments_create_f_module.mod 
CMakeFiles/kim-api.dir/kim_model_compute_arguments_create_f_module.mod.stamp 
Flang
/usr/bin/cmake -E touch 
CMakeFiles/kim-api.dir/fortran/src/kim_model_compute_arguments_create_f.f90.o.provides.build
[ 26%] Building Fortran object 
CMakeFiles/kim-api.dir/fortra

Bug#921781: marked as done (fis-gtm: FTBFS (dh_auto_configure fails))

2019-02-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Feb 2019 15:35:59 +
with message-id 
and subject line Bug#921781: fixed in fis-gtm 6.3-005-2
has caused the Debian Bug report #921781,
regarding fis-gtm: FTBFS (dh_auto_configure fails)
to be marked as done.

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

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


-- 
921781: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921781
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:fis-gtm
Version: 6.3-005-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- -DCMAKE_INSTALL_PREFIX:PATH=/usr 
-DGTM_INSTALL_DIR=lib/x86_64-linux-gnu/fis-gtm/V6.3-005_x86_64 
-DCMAKE_BUILD_TYPE=Release
cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu -DCMAKE_INSTALL_PREFIX:PATH=/usr 
-DGTM_INSTALL_DIR=lib/x86_64-linux-gnu/fis-gtm/V6.3-005_x86_64 
-DCMAKE_BUILD_TYPE=Release ..
-- The C compiler identification is GNU 8.2.0
-- The ASM compiler identification is GNU
-- Found assembler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info

[... snipped ...]


Run Build Command:"/usr/bin/make" "cmTC_76390/fast"
make[2]: Entering directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
/usr/bin/make -f CMakeFiles/cmTC_76390.dir/build.make 
CMakeFiles/cmTC_76390.dir/build
make[3]: Entering directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
Building C object CMakeFiles/cmTC_76390.dir/feature_tests.c.o
/usr/bin/cc   -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2-std=c99 -o CMakeFiles/cmTC_76390.dir/feature_tests.c.o  
 -c /<>/obj-x86_64-linux-gnu/CMakeFiles/feature_tests.c
Linking C executable cmTC_76390
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_76390.dir/link.txt 
--verbose=1
/usr/bin/cc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2   -Wl,-z,relro -Wl,-z,now  -rdynamic 
CMakeFiles/cmTC_76390.dir/feature_tests.c.o  -o cmTC_76390 
make[3]: Leaving directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
make[2]: Leaving directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'


Feature record: C_FEATURE:1c_function_prototypes
Feature record: C_FEATURE:1c_restrict
Feature record: C_FEATURE:0c_static_assert
Feature record: C_FEATURE:1c_variadic_macros


Detecting C [-std=c90] compiler features compiled with the following output:
Change Dir: /<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp

Run Build Command:"/usr/bin/make" "cmTC_da08a/fast"
make[2]: Entering directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
/usr/bin/make -f CMakeFiles/cmTC_da08a.dir/build.make 
CMakeFiles/cmTC_da08a.dir/build
make[3]: Entering directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
Building C object CMakeFiles/cmTC_da08a.dir/feature_tests.c.o
/usr/bin/cc   -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2-std=c90 -o CMakeFiles/cmTC_da08a.dir/feature_tests.c.o  
 -c /<>/obj-x86_64-linux-gnu/CMakeFiles/feature_tests.c
Linking C executable cmTC_da08a
/usr/bin/cmake -E cmake_link_script CMakeFiles/cmTC_da08a.dir/link.txt 
--verbose=1
/usr/bin/cc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2   -Wl,-z,relro -Wl,-z,now  -rdynamic 
CMakeFiles/cmTC_da08a.dir/feature_tests.c.o  -o cmTC_da08a 
make[3]: Leaving directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
make[2]: Leaving directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'


Feature record: C_FEATURE:1c_function_prototypes
Feature record: C_FEATURE:0c_restrict
Feature record: C_FEATURE:0c_static_assert
Feature record: C_FEATURE:0c_variadic_macros
dh_auto_configure: cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=

Bug#921851: [Pkg-electronics-devel] Bug#921851: unnecessary b-d's libisl-0.18-dev and libcloog-isl-dev, to be removed for buster

2019-02-09 Thread Jonathan McDowell
On Sat, Feb 09, 2019 at 01:39:34PM +0100, Matthias Klose wrote:
> Package: src:binutils-xtensa-lx106
> Version: 1
> Severity: serious
> Tags: sid buster

> unnecessary b-d's libisl-0.18-dev and libcloog-isl-dev, to be removed
> for buster

Where should I have been paying attention to find this out? It seems
prudent to do the removal well enough in advance of the freeze rather
than the packages in question still being present less than a week
before soft freeze.

J.

-- 
Web [Why are we here?  Because we're here.  Roll the bones.]
site: https:// [  ]  Made by
www.earth.li/~noodles/  [  ] HuggieTag 0.0.24



Bug#915175: oath-toolkit FTBFS with glibc 2.28

2019-02-09 Thread Sascha Steinbiss
user debian-rele...@lists.debian.org

usertag 915175 + bsp-2019-02-de-berlin
thank you

Dear maintainers,

Greetings from the BSP at the DCSO office in Berlin.

> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time 
> -D_FORTIFY_SOURCE=2 -fvisibility=hidden -g -O2 
> -ffile-prefix-map=/build/1st/oath-toolkit-2.6.1=. -fstack-protector-strong 
> -Wformat -Werror=format-security -c fseeko.c  -fPIC -DPIC -o .libs/fseeko.o
> fseeko.c: In function 'rpl_fseeko':
> fseeko.c:110:4: error: #error "Please port gnulib fseeko.c to your platform! 
> Look at the code in fseeko.c, then report this to bug-gnulib."
>#error "Please port gnulib fseeko.c to your platform! Look at the code in 
> fseeko.c, then report this to bug-gnulib."
> ^
> make[7]: *** [Makefile:1402: fseeko.lo] Error 1

I have fixed this bug and NMU'd oath-toolkit_2.6.1-1.3 to DELAYED/5.
Please feel free to reschedule or cancel my upload as you see fit. I
have attached the diff.

Cheers
Sascha
diff -Nru oath-toolkit-2.6.1/debian/changelog oath-toolkit-2.6.1/debian/changelog
--- oath-toolkit-2.6.1/debian/changelog	2018-06-22 19:48:53.0 +0200
+++ oath-toolkit-2.6.1/debian/changelog	2019-02-09 16:39:41.0 +0100
@@ -1,3 +1,11 @@
+oath-toolkit (2.6.1-1.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Use _IO_EOF_SEEN as GNU libc indicator.
+Closes: #915175
+
+ -- Sascha Steinbiss   Sat, 09 Feb 2019 16:39:41 +0100
+
 oath-toolkit (2.6.1-1.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru oath-toolkit-2.6.1/debian/patches/new-glibc-check.patch oath-toolkit-2.6.1/debian/patches/new-glibc-check.patch
--- oath-toolkit-2.6.1/debian/patches/new-glibc-check.patch	1970-01-01 01:00:00.0 +0100
+++ oath-toolkit-2.6.1/debian/patches/new-glibc-check.patch	2019-02-09 16:39:41.0 +0100
@@ -0,0 +1,25 @@
+Description: Check _IO_EOF_SEEN instead of _IO_ftrylockfile
+ Needed to get fseeko.c to build with glibc 2.28.
+ Inspired by https://git.savannah.gnu.org/cgit/gnulib.git/commit/?id=4af4a4a71827c0bc5e0ec67af23edef4f15cee8e.
+Author: Sascha Steinbiss 
+Last-Update: 2019-02-09
+--- a/liboath/gl/fseeko.c
 b/liboath/gl/fseeko.c
+@@ -47,7 +47,7 @@
+ #endif
+ 
+   /* These tests are based on fpurge.c.  */
+-#if defined _IO_ftrylockfile || __GNU_LIBRARY__ == 1 /* GNU libc, BeOS, Haiku, Linux libc5 */
++#if defined _IO_EOF_SEEN || __GNU_LIBRARY__ == 1 /* GNU libc, BeOS, Haiku, Linux libc5 */
+   if (fp->_IO_read_end == fp->_IO_read_ptr
+   && fp->_IO_write_ptr == fp->_IO_write_base
+   && fp->_IO_save_base == NULL)
+@@ -123,7 +123,7 @@
+   return -1;
+ }
+ 
+-#if defined _IO_ftrylockfile || __GNU_LIBRARY__ == 1 /* GNU libc, BeOS, Haiku, Linux libc5 */
++#if defined _IO_EOF_SEEN || __GNU_LIBRARY__ == 1 /* GNU libc, BeOS, Haiku, Linux libc5 */
+   fp->_flags &= ~_IO_EOF_SEEN;
+   fp->_offset = pos;
+ #elif defined __sferror || defined __DragonFly__ || defined __ANDROID__
diff -Nru oath-toolkit-2.6.1/debian/patches/series oath-toolkit-2.6.1/debian/patches/series
--- oath-toolkit-2.6.1/debian/patches/series	2018-04-15 20:19:41.0 +0200
+++ oath-toolkit-2.6.1/debian/patches/series	2019-02-09 16:39:41.0 +0100
@@ -1 +1,2 @@
 gtkdocize.patch
+new-glibc-check.patch


Bug#909383: Patch, NMU

2019-02-09 Thread Hilko Bengen
user debian-rele...@lists.debian.org
usertag 909383 + bsp-2019-02-de-berlin
usertag 680578 + bsp-2019-02-de-berlin
usertag 837991 + bsp-2019-02-de-berlin
thank you

Dear maintainer,

Greetings from the BSP at the DCSO office in Berlin.

I have NMU'd python-mode/6.2.3-1.1 which removes XEmacs21 support and
fixes three bugs to DELAYED/2. Please feel free to reschedule or cancel
my upload as you see fit. Patches based on 6.2.3-1 are attached.

Cheers,
-Hilko
>From 191d5f737c5b59b93777633d1363b753d1a622d7 Mon Sep 17 00:00:00 2001
From: Hilko Bengen 
Date: Sat, 9 Feb 2019 16:50:20 +0100
Subject: [PATCH 1/2] Drop xemacs21 support (Closes: #909383, #680578, #837991)

---
 debian/emacsen-install | 5 +
 1 file changed, 5 insertions(+)

diff --git a/debian/emacsen-install b/debian/emacsen-install
index e2a2ed9..90d5814 100755
--- a/debian/emacsen-install
+++ b/debian/emacsen-install
@@ -20,6 +20,11 @@ if [ ${FLAVOR} = emacs21 ]; then
 exit 0
 fi
 
+if [ ${FLAVOR} = xemacs21 ]; then
+echo "$PACKAGE requires string-to-syntax, rx.el, which is not available in xemacs21"
+exit 0
+fi
+
 echo install/${PACKAGE}: Handling install for emacsen flavor ${FLAVOR}
 
 FLAVORTEST=`echo $FLAVOR | cut -c-6`
-- 
2.19.1

>From 8095cbde8d09f96e4f1c6591fd5247f3900d01ec Mon Sep 17 00:00:00 2001
From: Hilko Bengen 
Date: Sat, 9 Feb 2019 16:58:38 +0100
Subject: [PATCH 2/2] Debian release 1:6.2.3-1.1

---
 debian/changelog | 7 +++
 1 file changed, 7 insertions(+)

diff --git a/debian/changelog b/debian/changelog
index f0c1b24..b0df38d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+python-mode (1:6.2.3-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * Drop xemacs21 support (Closes: #909383, #680578, #837991)
+
+ -- Hilko Bengen   Sat, 09 Feb 2019 16:56:13 +0100
+
 python-mode (1:6.2.3-1) unstable; urgency=medium
 
   * New upstream release.
-- 
2.19.1



Bug#919103: marked as done (libreoffice-kde5: failure to upgrade from stretch: soffice.odg also in libreoffice-kde)

2019-02-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Feb 2019 16:20:21 +
with message-id 
and subject line Bug#919103: fixed in libreoffice 1:6.2.0-1
has caused the Debian Bug report #919103,
regarding libreoffice-kde5: failure to upgrade from stretch: soffice.odg also 
in libreoffice-kde
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.)


-- 
919103: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919103
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libreoffice-kde5
Version: 1:6.1.4-3
Severity: serious
Justification: failure to install/upgrade

Hi,

Testing the upgrade path from stretch to buster for various desktop
tasks, I've noticed the following issue:

Unpacking libreoffice-kde5 (1:6.1.4-3+b1) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-q3iqce/43-libreoffice-kde5_1%3a6.1.4-3+b1_amd64.deb 
(--unpack):
 trying to overwrite '/usr/share/templates/.source/soffice.odg', which is 
also in package libreoffice-kde 1:5.2.7-1+deb9u4

which breaks the dist-upgrade.


Cheers,
-- 
Cyril Brulebois (k...@debian.org)
D-I release manager -- Release team member -- Freelance Consultant
--- End Message ---
--- Begin Message ---
Source: libreoffice
Source-Version: 1:6.2.0-1

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

Debian distribution maintenance software
pp.
Rene Engelhard  (supplier of updated libreoffice 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: Sat, 09 Feb 2019 16:10:13 +0100
Source: libreoffice
Architecture: source
Version: 1:6.2.0-1
Distribution: experimental
Urgency: medium
Maintainer: Debian LibreOffice Maintainers 
Changed-By: Rene Engelhard 
Closes: 919103 919298 920331 920859 920960
Changes:
 libreoffice (1:6.2.0-1) experimental; urgency=medium
 .
   * New upstream release
 .
   * debian/patches/jdk-11.0.2-javadoc.diff: backport from master
 (closes: #920331)
   * debian/patches/tdf123077.diff: add from libreoffice-6-1 branch
 (closes: #920859)
 .
   * debian/patches/aarch64-temporarily-disable-testgetCaughtException.diff:
 remove again ...
   * debian/patches/aarch64-call-__cxa_current_exception_type.diff: ... and
 replace with this (from master)
 .
   * debian/control.transitionals.in: revert making libreoffice-mysql-connector
 'all'
   * debian/libreoffice-mysql-connector.maintscript: remove
 $DPKG_MAINTSCRIPT_PACKAGE and use -core instead of -common.
   (closes: #919298)
   * debian/control.kde*.in: Replaces: libreoffice-kde (<< 1:6.1.0~alpha1-1)
 (closes: #919103)
   * debian/rules:
 - add mesa-opencl-icd | beignet-opencl-icd as alternatives to
   ocl-icd-libopencl1
   * debian/control.in: recommend fonts-noto-{,ui}-core instead of transitional
 fonts-noto-hinted (closes: #920960)
   * debian/rules, debian/scripts/locale-gen: revert removal, still needed e.g.
 for sw_odfexports testSpellOutNumberingTypes::Import which hangs otherwise
 .
   [ Vincas Dargis ]
   * debian/patches/apparmor-opencl.diff: Include OpenCL abstractions to fix
 OpenCL usage in Calc
Checksums-Sha1:
 ac052859aee0b3fdd2412914dd07d4990fa62555 26742 libreoffice_6.2.0-1.dsc
 5131ef43c856d55377b8097e6154f1f501b20d4e 15598112 
libreoffice_6.2.0.orig-helpcontent2.tar.xz
 f8f66adff03eb7fb4d0af569f5a89e0ef8c008ce 142163900 
libreoffice_6.2.0.orig-translations.tar.xz
 860fa65972c83c03c26f3bbd64491bb0bd4e163a 213476336 
libreoffice_6.2.0.orig.tar.xz
 82a9d8e8ad31b09ae892515261eebf83ca46dced 833 libreoffice_6.2.0.orig.tar.xz.asc
 3ab3a3bcdc9b1c402d6974b26dfac822f32660f7 10527216 
libreoffice_6.2.0-1.debian.tar.xz
 cb9dfc9a41056a72e3b7dd0d51e078cd4243ea36 42123 
libreoffice_6.2.0-1_source.buildinfo
Checksums-Sha256:
 79767c5bd0ab8f0eb90bfedfb5662ea0ac149b396a75eb870aff40b0d950e1d7 26742 
libreoffice_6.2.0-1.dsc
 9a19655e3d2dde6750b997cf53a49ec579a0029551b1233119fce975258a4c46 15598112 
libreoffice_6.2.0.orig-helpcontent2.tar.xz
 9dc665a3966fda91a6bfe0fc8e5662c69eb75fcbc9cd0d2a0ad776b49ba9efc1 142163900 
libreoffice_6.2.0.orig-translations.t

Bug#920331: marked as done (uninstallable - arch-indep parts missing)

2019-02-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Feb 2019 16:20:21 +
with message-id 
and subject line Bug#920331: fixed in libreoffice 1:6.2.0-1
has caused the Debian Bug report #920331,
regarding uninstallable - arch-indep parts missing
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.)


-- 
920331: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920331
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libreoffice-common
Version: 1:6.1.4-4
Severity: minor
Tags: a11y

libreoffice-common is at 1:6.1.4-4 in Sid, while all the other libreoffice
packages like libreoffice and libreoffice are at 1:6.1.5~rc1-1, which depend on
libreoffice-common 1:6.1.5~rc1-1. This makes it impossible to upgrade
libreoffice from 1:6.1.4-4 tp 1:6.1.5~rc1-1.



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

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

Versions of packages libreoffice-common depends on:
ii  libnumbertext-data 1.0.5-1
ii  libreoffice-style-colibre  1:6.1.4-4
ii  libreoffice-style-tango1:6.1.4-4
ii  ure6.1.5~rc1-1

Versions of packages libreoffice-common recommends:
ii  apparmor2.13.2-3
ii  fonts-liberation2   2.00.4-1
ii  libexttextcat-data  3.4.5-1
ii  python3-uno 1:6.1.4-4
ii  xdg-utils   1.1.3-1

Versions of packages libreoffice-common suggests:
ii  libreoffice-style-colibre [libreoffice-style]  1:6.1.4-4
ii  libreoffice-style-tango [libreoffice-style]1:6.1.4-4

Versions of packages python3-uno depends on:
ii  libc6 2.28-5
ii  libgcc1   1:8.2.0-14
ii  libpython3.7  3.7.2-1
ii  libreoffice-core  1:6.1.4-4
ii  libstdc++68.2.0-14
ii  python3   3.7.2-1
ii  python3.7 3.7.2-1
ii  uno-libs3 6.1.5~rc1-1
ii  ure   6.1.5~rc1-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: libreoffice
Source-Version: 1:6.2.0-1

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

Debian distribution maintenance software
pp.
Rene Engelhard  (supplier of updated libreoffice 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: Sat, 09 Feb 2019 16:10:13 +0100
Source: libreoffice
Architecture: source
Version: 1:6.2.0-1
Distribution: experimental
Urgency: medium
Maintainer: Debian LibreOffice Maintainers 
Changed-By: Rene Engelhard 
Closes: 919103 919298 920331 920859 920960
Changes:
 libreoffice (1:6.2.0-1) experimental; urgency=medium
 .
   * New upstream release
 .
   * debian/patches/jdk-11.0.2-javadoc.diff: backport from master
 (closes: #920331)
   * debian/patches/tdf123077.diff: add from libreoffice-6-1 branch
 (closes: #920859)
 .
   * debian/patches/aarch64-temporarily-disable-testgetCaughtException.diff:
 remove again ...
   * debian/patches/aarch64-call-__cxa_current_exception_type.diff: ... and
 replace with this (from master)
 .
   * debian/control.transitionals.in: revert making libreoffice-mysql-connector
 'all'
   * debian/libreoffice-mysql-connector.maintscript: remove
 $DPKG_MAINTSCRIPT_PACKAGE and use -core instead of -common.
   (closes: #919298)
   * debian/control.kde*.in: Replaces: libreoffice-kde (<< 1:6.1.0~alpha1-1)
 (closes: #919103)
   * debian/rules:
 - add mesa-opencl-icd | beignet-opencl-icd as alternatives to
   ocl-icd-libopencl1
   * debian/control.in: recommend fonts-noto-{,ui}-core instead of transitional
 fonts-noto-hinted (closes: #920960)
   * debian/rules, debian/scripts/locale-gen: revert removal, still needed e.g.
 for sw_odfexports testSpellOutNumberingTypes::Import which hangs otherwise
 .
   [ Vincas Dargis ]
   * debian/patches/apparmor-opencl.diff: Include OpenCL abstractions to fix
 OpenCL usage in Calc
Checksums-Sha1:

Bug#921851: [Pkg-electronics-devel] Bug#921851: unnecessary b-d's libisl-0.18-dev and libcloog-isl-dev, to be removed for buster

2019-02-09 Thread Matthias Klose
On 09.02.19 16:42, Jonathan McDowell wrote:
> On Sat, Feb 09, 2019 at 01:39:34PM +0100, Matthias Klose wrote:
>> Package: src:binutils-xtensa-lx106
>> Version: 1
>> Severity: serious
>> Tags: sid buster
> 
>> unnecessary b-d's libisl-0.18-dev and libcloog-isl-dev, to be removed
>> for buster
> 
> Where should I have been paying attention to find this out? It seems
> prudent to do the removal well enough in advance of the freeze rather
> than the packages in question still being present less than a week
> before soft freeze.

well, don't use badly maintained packages as templates for your own package. I
only saw these after gcc-5* was removed from unstable earlier this year.



Bug#919298: marked as done (libreoffice-mysql-connector: fails to upgrade from sid: dpkg-maintscript-helper errors out)

2019-02-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Feb 2019 16:20:21 +
with message-id 
and subject line Bug#919298: fixed in libreoffice 1:6.2.0-1
has caused the Debian Bug report #919298,
regarding libreoffice-mysql-connector: fails to upgrade from sid: 
dpkg-maintscript-helper errors out
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.)


-- 
919298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919298
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libreoffice-mysql-connector
Version: 1:6.2.0~rc2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.

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

  Preparing to unpack .../7-libreoffice-mysql-connector_1%3a6.2.0~rc2-1_all.deb 
...
  dpkg-query: no packages found matching $DPKG_MAINTSCRIPT_PACKAGE
  dpkg-query: error: --listfiles needs a valid package name but 
'$DPKG_MAINTSCRIPT_PACKAGE' is not: illegal package name in specifier 
'$DPKG_MAINTSCRIPT_PACKAGE': must start with an alphanumeric character
  
  Use --help for help about querying packages.
  dpkg-maintscript-helper: error: file 
'/usr/share/doc/libreoffice-mysql-connector' not owned by package 
'$DPKG_MAINTSCRIPT_PACKAGE'
  dpkg-query: error: --listfiles needs a valid package name but 
'$DPKG_MAINTSCRIPT_PACKAGE' is not: illegal package name in specifier 
'$DPKG_MAINTSCRIPT_PACKAGE': must start with an alphanumeric character
  
  Use --help for help about querying packages.
  dpkg-maintscript-helper: error: file 
'/usr/share/doc/libreoffice-mysql-connector/copyright' not owned by package 
'$DPKG_MAINTSCRIPT_PACKAGE'
  dpkg-query: error: --listfiles needs a valid package name but 
'$DPKG_MAINTSCRIPT_PACKAGE' is not: illegal package name in specifier 
'$DPKG_MAINTSCRIPT_PACKAGE': must start with an alphanumeric character
  
  Use --help for help about querying packages.
  dpkg-maintscript-helper: error: file 
'/usr/share/doc/libreoffice-mysql-connector/changelog.Debian.gz' not owned by 
package '$DPKG_MAINTSCRIPT_PACKAGE'
  dpkg-query: error: --listfiles needs a valid package name but 
'$DPKG_MAINTSCRIPT_PACKAGE' is not: illegal package name in specifier 
'$DPKG_MAINTSCRIPT_PACKAGE': must start with an alphanumeric character
  
  Use --help for help about querying packages.
  dpkg-maintscript-helper: error: file 
'/usr/share/doc/libreoffice-mysql-connector/changelog.Debian.amd64.gz' not 
owned by package '$DPKG_MAINTSCRIPT_PACKAGE'
  dpkg-maintscript-helper: error: directory 
'/usr/share/doc/libreoffice-mysql-connector' contains files not owned by 
package $DPKG_MAINTSCRIPT_PACKAGE, cannot switch to symlink
  dpkg: error processing archive 
/tmp/apt-dpkg-install-w3OdOs/7-libreoffice-mysql-connector_1%3a6.2.0~rc2-1_all.deb
 (--unpack):
   new libreoffice-mysql-connector package pre-installation script subprocess 
returned error exit status 1
  Errors were encountered while processing:
   
/tmp/apt-dpkg-install-w3OdOs/7-libreoffice-mysql-connector_1%3a6.2.0~rc2-1_all.deb


Without looking at the code I'd suspect you have a redundant
  $DPKG_MAINTSCRIPT_PACKAGE
in libreoffice-mysql-connector.maintscript. Current debhelper compat
levels properly escape the '$' character.


cheers,

Andreas


libreoffice-mysql-connector_1:6.2.0~rc2-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libreoffice
Source-Version: 1:6.2.0-1

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

Debian distribution maintenance software
pp.
Rene Engelhard  (supplier of updated libreoffice 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: Sat, 09 Feb 2019 16:10:13 +0100
Source: libreoffice
Architecture: source
Version: 1:6.2.0-1
Distribution: experimental
Urgency: medium
Maintainer: Debian LibreOffice Maintainers 
Changed-By: Rene Engelhard 
Closes: 919103 919298 920331 920859 920960
Changes:
 libreoffice (1:6.2.0-1) experimental; urgency=medium
 .
   * New upstream release
 .
   *

Bug#921769: marked as done (moarvm: FTBFS (error: 'MP_GEN_RANDOM_MAX' undeclared))

2019-02-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Feb 2019 16:20:39 +
with message-id 
and subject line Bug#921769: fixed in moarvm 2018.12+dfsg-3
has caused the Debian Bug report #921769,
regarding moarvm: FTBFS (error: 'MP_GEN_RANDOM_MAX' undeclared)
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.)


-- 
921769: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921769
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:moarvm
Version: 2018.12+dfsg-2
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-arch
dh build-arch
   dh_update_autotools_config -a
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>/moarvm-2018.12+dfsg'
perl Configure.pl  \
--prefix=/usr \
--libdir=/usr/lib/moar \
--debug \
--has-libtommath \
--has-libuv \
--has-libatomic_ops \
--has-libffi
Welcome to MoarVM!

[... snipped ...]

 two_complement_bitop(ia, ib, ic, mp_##opname); \
  ^~~
src/math/bigintops.c:512:1: note: in expansion of macro 'MVM_BIGINT_BINARY_OP_2'
 MVM_BIGINT_BINARY_OP_2(or , { sc = sa | sb; })
 ^~
src/math/bigintops.c:264:40: note: expected 'int (*)(mp_int *, mp_int *, mp_int 
*)' {aka 'int (*)(struct  *, struct  *, struct 
 *)'} but argument is of type 'int (*)(const mp_int *, const mp_int 
*, mp_int *)' {aka 'int (*)(const struct  *, const struct 
 *, struct  *)'}
  int (*mp_bitop)(mp_int *, mp_int *, mp_int 
*)) {
  ~~^~~
src/math/bigintops.c: In function 'MVM_bigint_xor':
src/math/bigintops.c:447:42: warning: passing argument 4 of 
'two_complement_bitop' from incompatible pointer type 
[-Wincompatible-pointer-types]
 two_complement_bitop(ia, ib, ic, mp_##opname); \
  ^~~
src/math/bigintops.c:513:1: note: in expansion of macro 'MVM_BIGINT_BINARY_OP_2'
 MVM_BIGINT_BINARY_OP_2(xor, { sc = sa ^ sb; })
 ^~
src/math/bigintops.c:264:40: note: expected 'int (*)(mp_int *, mp_int *, mp_int 
*)' {aka 'int (*)(struct  *, struct  *, struct 
 *)'} but argument is of type 'int (*)(const mp_int *, const mp_int 
*, mp_int *)' {aka 'int (*)(const struct  *, const struct 
 *, struct  *)'}
  int (*mp_bitop)(mp_int *, mp_int *, mp_int 
*)) {
  ~~^~~
src/math/bigintops.c: In function 'MVM_bigint_and':
src/math/bigintops.c:447:42: warning: passing argument 4 of 
'two_complement_bitop' from incompatible pointer type 
[-Wincompatible-pointer-types]
 two_complement_bitop(ia, ib, ic, mp_##opname); \
  ^~~
src/math/bigintops.c:514:1: note: in expansion of macro 'MVM_BIGINT_BINARY_OP_2'
 MVM_BIGINT_BINARY_OP_2(and, { sc = sa & sb; })
 ^~
src/math/bigintops.c:264:40: note: expected 'int (*)(mp_int *, mp_int *, mp_int 
*)' {aka 'int (*)(struct  *, struct  *, struct 
 *)'} but argument is of type 'int (*)(const mp_int *, const mp_int 
*, mp_int *)' {aka 'int (*)(const struct  *, const struct 
 *, struct  *)'}
  int (*mp_bitop)(mp_int *, mp_int *, mp_int 
*)) {
  ~~^~~
src/math/bigintops.c: In function 'MVM_bigint_rand':
src/math/bigintops.c:1166:13: error: 'MP_GEN_RANDOM_MAX' undeclared (first use 
in this function); did you mean 'UV_ERRNO_MAX'?
 if (MP_GEN_RANDOM_MAX >= abs(smallint_max)) {
 ^
 UV_ERRNO_MAX
src/math/bigintops.c:1166:13: note: each undeclared identifier is reported only 
once for each function it appears in
src/math/bigintops.c:1167:35: warning: implicit declaration of function 
'MP_GEN_RANDOM'; did you mean 'UV_FS_O_RANDOM'? 
[-Wimplicit-function-declaration]
 mp_digit result_int = MP_GEN_RANDOM();
   ^
   UV_FS_O_RANDOM
make[2]: *** [Makefile:621: src/math/bigintops.o] Error 1
make[2]: Leaving directory '/<>/moarvm-2018.12+dfsg'
dh_auto_build: make -j1 NOISY=1 returned exit code 2
make[1]: *** [debian/rules:51: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>/moarvm-2018.12+dfsg'
make: *** [debian/rules:37: build-arch] Error 2
dpkg-b

Bug#919850: python3-link-grammar: broken symlink: /usr/lib/python3.7/site-packages/linkgrammar/_clinkgrammar.so -> _clinkgrammar.so.5.5.1

2019-02-09 Thread Eriberto Mota
Hi,

After dh_install:

python3-link-grammar
└── usr
└── lib
└── python3.7
└── site-packages
├── linkgrammar
│   ├── clinkgrammar.py
│   ├── _clinkgrammar.so -> _clinkgrammar.so.5.5.1
│   ├── _clinkgrammar.so.5 -> _clinkgrammar.so.5.5.1
│   ├── _clinkgrammar.so.5.5.1
│   ├── __init__.py
│   ├── linkgrammar.py
│   └── __pycache__
│   ├── clinkgrammar.cpython-37.opt-1.pyc
│   ├── clinkgrammar.cpython-37.pyc
│   ├── __init__.cpython-37.opt-1.pyc
│   ├── __init__.cpython-37.pyc
│   ├── linkgrammar.cpython-37.opt-1.pyc
│   └── linkgrammar.cpython-37.pyc
└── linkgrammar.pth

After dh_python3:

python3-link-grammar
└── usr
├── lib
│   ├── python3
│   │   └── dist-packages
│   │   ├── linkgrammar
│   │   │   ├── clinkgrammar.py
│   │   │   ├── _clinkgrammar.so.5.5.1
│   │   │   ├── __init__.py
│   │   │   └── linkgrammar.py
│   │   └── linkgrammar.pth
│   └── python3.7
│   └── site-packages
│   └── linkgrammar
│   └── _clinkgrammar.so -> _clinkgrammar.so.5.5.1

So, the link was not moved or recreated by dh_python3.

Eriberto


Bug#921848: marked as done (please remove unnecessary b-d cloog-ppl)

2019-02-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Feb 2019 16:44:41 +
with message-id 
and subject line Bug#921848: fixed in fact++ 1.6.5~dfsg-2
has caused the Debian Bug report #921848,
regarding please remove unnecessary b-d cloog-ppl
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.)


-- 
921848: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921848
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:fact++
Version: 1.6.5~dfsg-1
Severity: serious
Tags: sid buster

I'd like to remove cloog-ppl from the sid/buster, therefore the severity of this
report.  I can't see yet any use of cloog-ppl during the package build.  So
please check if this package is working without it.  If not, then please
downgrade the severity, and think about using libisl. cloog-ppl isn't maintained
anymore upstream.
--- End Message ---
--- Begin Message ---
Source: fact++
Source-Version: 1.6.5~dfsg-2

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated fact++ 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: Sat, 09 Feb 2019 17:03:32 +0100
Source: fact++
Architecture: source
Version: 1.6.5~dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard 
Changed-By: Jonas Smedegaard 
Closes: 836091 921848
Changes:
 fact++ (1.6.5~dfsg-2) unstable; urgency=medium
 .
   * Update copyright info:
 + Fix syntax of Copyright field for main author.
 + Use https protocol in file format URL.
 + Extend coverage of packaging.
   * Fix stop bogusly depend on dbus-x11.
 Closes: Bug#836091. Thanks to Simon McVittie.
   * Simplify rules.
 Stop build-depend on dh-buildinfo licensecheck cdbs.
   * Update Vcs-* fields: Packaging moved to Salsa.
   * Stop build-depend on cloog-ppl.
 + Closes: Bug#921848. Thanks to Matthias Klose.
   * Declare compliance with Debian Policy 4.3.0.
   * Enable parallel build.
   * Set Rules-Requires-Root: no.
   * Update watch file:
 + Rewrite usage comment.
 + Generalize dversionmangle option.
   * Drop obsolete lintian override about debhelper 9.
   * Tighten lintian overrides regarding License-Reference.
   * Enable autopkgtest.
Checksums-Sha1:
 dccd301f1c1b6d984120d381b19e018c71db75da 1912 fact++_1.6.5~dfsg-2.dsc
 98e0c4fc74e88e3d4636ea09d70c972683513eda 7120 fact++_1.6.5~dfsg-2.debian.tar.xz
 16b8f9e8d24c3d2db22a877ce3fb47e9c5471f68 5273 
fact++_1.6.5~dfsg-2_amd64.buildinfo
Checksums-Sha256:
 f5731154804377724f9eee5101058b875eb017ac708ed9b0832d43aba4141cb4 1912 
fact++_1.6.5~dfsg-2.dsc
 24e7ac8a2b006ed42f3f6c984b95d61a20218b3d5beeaafea72e74572df80ba9 7120 
fact++_1.6.5~dfsg-2.debian.tar.xz
 4bc56acb00b755feac7fc863d6d92ad99f6db8acfc416e8f98740d43b6de3135 5273 
fact++_1.6.5~dfsg-2_amd64.buildinfo
Files:
 8ab1ecf940f5729029592de0a118138e 1912 science optional fact++_1.6.5~dfsg-2.dsc
 316bd897d5f12bfe97ab32ec3d0b8850 7120 science optional 
fact++_1.6.5~dfsg-2.debian.tar.xz
 35b89dd44f6e32d4b8192836b3137f9e 5273 science optional 
fact++_1.6.5~dfsg-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAlxe+5EACgkQLHwxRsGg
ASFbchAAmJ9WneNPEMkhNpyuPvOGw8n6nGJWz3AsWiK2YOoID6cFlT3KMVlbRmUi
E/esKkpj7CegfY+gAnvWjzE1/KY7Xkh21WwLGJwo6Efc7S0PWPeLw77dSlKloVO9
U0YPk+UiPPTn0y08t3Uvswu8cb0rp4yBkFoY2LGLoJcZEKdk8mINQGtDczLM3fMm
nCSKBmRVnkte3naOjRP8i60ZuGLmCR3s7JZsBBEVoi0MyyUoMW1ttuJ8dFlEmulV
5y2d5VIIO2YwwyJHV0eco4LXzTI2ILX6f7ZJa13YtHTZQTQWKmt+IaJIads/KSiq
oZ2KMLeQ7NTt41R07rNkp6FRS2KewPJIEVNXssJGScpdp8yAcHiBzck0wlFpYtX7
5wixelA1YGCFiSW3WuphoCEgRdaaT+uVXfMGKH77Y2oPOfvCCEkF3V8llEsyBwDi
GxXuk4MKARCQMlOiT9S9kWFivxqE6tieEzlIw98RMSsTn0yu0YGH3PSP3X11KJvw
sq3MK80M56dRKTIcR3ewOoQ2f24ppTeNZkUaXmEpq9cjJYk/I3TjmNec98hu32G5
kBhopEpblUnaXw85WfF+/5LdCAQWEUiVn2UaY7jfzEpMUVZ6oVU0Z2rgh5F3byjM
/b8Jgxf3R8aBWq+27PvhO2IyBovajE9/llaVolotyLi722G92sw=
=IhJv
-END PGP SIGNATURE End Message ---


Bug#921871: grr: Prevent entering testing

2019-02-09 Thread Hilko Bengen
Source: grr
Version: 3.1.0.2+dfsg-6
Severity: grave

The Buster release should not contain GRR.

The version in unstable (3.1.0.2) is outdated and effectively unsuppoted
by upstream. Current upstream versions require many thus far unpackaged
build-dependencies for building the web-based UI, including two dozen
NodeJS modules and a newer version of the Java/Maven-based
clojure-compiler. We won't be able to get this situation fixed in time.

Cheers,
-Hilko



Bug#906365: marked as done (ipxe: FTBFS in buster/sid (Error: can't resolve `__table_entries.2701'))

2019-02-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Feb 2019 17:05:08 +
with message-id 
and subject line Bug#906365: fixed in ipxe 1.0.0+git-20190125.36a4c85-1
has caused the Debian Bug report #906365,
regarding ipxe: FTBFS in buster/sid (Error: can't resolve 
`__table_entries.2701')
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.)


-- 
906365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906365
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ipxe
Version: 1.0.0+git-20161027.b991c67-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in buster but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>/ipxe-1.0.0+git-20161027.b991c67'
cp debian/config/* src/config/local
make[1]: Leaving directory '/<>/ipxe-1.0.0+git-20161027.b991c67'
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>/ipxe-1.0.0+git-20161027.b991c67'
dh_auto_build --sourcedirectory=src -- V=1 NO_WERROR=1 
VERSION="1.0.0+git-20161027.b991c67-1" bin/82540em.rom
cd src && make -j1 V=1 NO_WERROR=1 
VERSION=1.0.0\+git-20161027.b991c67-1 bin/82540em.rom
make[2]: Entering directory '/<>/ipxe-1.0.0+git-20161027.b991c67/src'
rm -f  bin/*.*  bin/.certificate.* bin/.certificates.* bin/.private_key.* 
bin/errors bin/NIC ./util/zbin ./util/elf2efi32 ./util/elf2efi64 
./util/efirom ./util/efifatbin ./util/iccfix ./util/einfo TAGS bin/symtab

[... snipped ...]

gcc  -DARCH=i386 -DPLATFORM=pcbios -march=i386 -fomit-frame-pointer 
-fstrength-reduce -falign-jumps=1 -falign-loops=1 -falign-functions=1 
-mpreferred-stack-boundary=2 -mregparm=3 -mrtd -freg-struct-return -m32 
-fshort-wchar -Ui386 -Ulinux -DNVALGRIND -Iinclude -I. -Iarch/x86/include 
-Iarch/i386/include -Iarch/i386/include/pcbios -Os -g -ffreestanding -Wall -W 
-Wformat-nonliteral  -fno-stack-protector -fno-dwarf2-cfi-asm -fno-exceptions  
-fno-unwind-tables -fno-asynchronous-unwind-tables -Wno-address   
-ffunction-sections -fdata-sections -include include/compiler.h -DASM_TCHAR='@' 
-DASM_TCHAR_OPS='@'   -DOBJECT=ping -c net/ping.c -o bin/ping.o 
gcc  -DARCH=i386 -DPLATFORM=pcbios -march=i386 -fomit-frame-pointer 
-fstrength-reduce -falign-jumps=1 -falign-loops=1 -falign-functions=1 
-mpreferred-stack-boundary=2 -mregparm=3 -mrtd -freg-struct-return -m32 
-fshort-wchar -Ui386 -Ulinux -DNVALGRIND -Iinclude -I. -Iarch/x86/include 
-Iarch/i386/include -Iarch/i386/include/pcbios -Os -g -ffreestanding -Wall -W 
-Wformat-nonliteral  -fno-stack-protector -fno-dwarf2-cfi-asm -fno-exceptions  
-fno-unwind-tables -fno-asynchronous-unwind-tables -Wno-address   
-ffunction-sections -fdata-sections -include include/compiler.h -DASM_TCHAR='@' 
-DASM_TCHAR_OPS='@'   -DOBJECT=fragment -c net/fragment.c -o bin/fragment.o 
gcc  -DARCH=i386 -DPLATFORM=pcbios -march=i386 -fomit-frame-pointer 
-fstrength-reduce -falign-jumps=1 -falign-loops=1 -falign-functions=1 
-mpreferred-stack-boundary=2 -mregparm=3 -mrtd -freg-struct-return -m32 
-fshort-wchar -Ui386 -Ulinux -DNVALGRIND -Iinclude -I. -Iarch/x86/include 
-Iarch/i386/include -Iarch/i386/include/pcbios -Os -g -ffreestanding -Wall -W 
-Wformat-nonliteral  -fno-stack-protector -fno-dwarf2-cfi-asm -fno-exceptions  
-fno-unwind-tables -fno-asynchronous-unwind-tables -Wno-address   
-ffunction-sections -fdata-sections -include include/compiler.h -DASM_TCHAR='@' 
-DASM_TCHAR_OPS='@'   -DOBJECT=pccrc -c net/pccrc.c -o bin/pccrc.o 
gcc  -DARCH=i386 -DPLATFORM=pcbios -march=i386 -fomit-frame-pointer 
-fstrength-reduce -falign-jumps=1 -falign-loops=1 -falign-functions=1 
-mpreferred-stack-boundary=2 -mregparm=3 -mrtd -freg-struct-return -m32 
-fshort-wchar -Ui386 -Ulinux -DNVALGRIND -Iinclude -I. -Iarch/x86/include 
-Iarch/i386/include -Iarch/i386/include/pcbios -Os -g -ffreestanding -Wall -W 
-Wformat-nonliteral  -fno-stack-protector -fno-dwarf2-cfi-asm -fno-exceptions  
-fno-unwind-tables -fno-asynchronous-unwind-tables -Wno-address   
-ffunction-sections -fdata-sections -include include/compiler.h -DASM_TCHAR='@' 
-DASM_TCHAR_OPS='@'   -DOBJECT=arp -c net/arp.c -o bin/arp.o 
gcc  -DARCH=i386 -DPLATFORM=pcbios -march=i386 -fomit-frame-pointer 
-fstrength-reduce -falign-jumps=1 -falign-loops=1 -falign-functions=1 
-mpreferred-stack-boundary=2 -mregparm=3 -mrtd -freg-struct-return -m32 
-fshort-wchar -Ui386 -Ulinux -DNVALGRIND -Iinclude -I. -Iarch/x86/include 
-Iarch/i386/include -

Bug#919974: NMU, patch

2019-02-09 Thread Hilko Bengen
user debian-rele...@lists.debian.org
usertag 919974 + bsp-2019-02-de-berlin
thank you

Dear maintainers,

Greetings from the BSP at the DCSO office in Berlin.

I have NMU'd yapf/0.25.0-2.1 to unstable, re-adding the yapf,
python-yapf packages. I have chosen not to place it into a DELAYED
slot:

- The upload needs to go through the NEW queue again and we are pretty
  close to the freeze.

- The solution to this bug seems obvious as migrating all the reverse
  dependencies to Python3-only in time for the freeze is not feasible.

- The last uploader did not act on this bug within the last 15 days.

My patches are attached.

Cheers,
-Hilko
>From 4fcac9c97186da7904f397ca84dc6cb21b89930c Mon Sep 17 00:00:00 2001
From: Hilko Bengen 
Date: Sat, 9 Feb 2019 18:11:48 +0100
Subject: [PATCH 1/3] Revert removal of Python2 support (Closes: #919974)

---
 debian/control | 32 +++-
 debian/rules   |  5 -
 2 files changed, 35 insertions(+), 2 deletions(-)

diff --git a/debian/control b/debian/control
index 6ebc357..e86d9f4 100644
--- a/debian/control
+++ b/debian/control
@@ -3,12 +3,42 @@ Section: python
 Priority: optional
 Maintainer: Ana Custura 
 Uploaders: Debian Python Modules Team 
-Build-Depends: debhelper (>=12),dh-python,python3-all,python3-setuptools,python3-nose,python3-pkg-resources
+Build-Depends: debhelper (>=12),dh-python,python-all,python-setuptools,python3-all,python3-setuptools,python-nose,python3-nose,python-pkg-resources,python3-pkg-resources
 Standards-Version: 4.3.0
 Homepage: https://github.com/google/yapf
 Vcs-Git: https://salsa.debian.org/python-team/modules/yapf.git
 Vcs-Browser: https://salsa.debian.org/python-team/modules/yapf
 
+Package: python-yapf
+Architecture: all
+Depends: ${misc:Depends},
+ ${python:Depends},
+ python-pkg-resources
+Breaks: yapf (<< 0.19.0-1~)
+Replaces: yapf (<< 0.19.0-1~)
+Description: public modules for yapf (Python 2)
+ Yapf is a tool that reformats code to the best formatting that conforms to the
+ style guide. It is not only concerned with lint errors, but also with the
+ styilistic appearance of Python code. The idea is also similar to the 'gofmt'
+ tool for the Go programming language. This package installs the tool for Python
+ 2.
+ .
+ This package provides the modules for Python 2.
+
+Package: yapf
+Architecture: all
+Depends: ${misc:Depends},
+ ${python:Depends},
+ python-yapf (= ${binary:Version})
+Description: Python code formatter for different styles (Python 2)
+ Yapf is a tool that reformats code to the best formatting that conforms to the
+ style guide. It is not only concerned with lint errors, but also with the
+ styilistic appearance of Python code. The idea is also similar to the 'gofmt'
+ tool for the Go programming language. This package installs the tool for Python
+ 2.
+ .
+ This package provides the command-line interface for Python 2.
+
 Package: python3-yapf
 Architecture: all
 Depends: ${misc:Depends},
diff --git a/debian/rules b/debian/rules
index 15ff663..b63c75a 100755
--- a/debian/rules
+++ b/debian/rules
@@ -2,13 +2,16 @@
 #export DH_VERBOSE = 1
 
 export PYBUILD_NAME=yapf
+export PYBUILD_DESTDIR_python2=debian/python-${PYBUILD_NAME}
 export PYBUILD_DESTDIR_python3=debian/python3-${PYBUILD_NAME}
 export PYBUILD_TEST_NOSE=1
+export PYBUILD_TEST_ARGS_python2=--exclude "yapftests.pytree_unwrapper_test.MatchBracketsTest"
 export PYBUILD_TEST_ARGS_python3=-e "testStronglyConnected" -e "testAsyncAsNonKeyword" -e "testListComprehensionPreferThreeLinesForLineWrap"
 %:
-	dh $@  --with python3 --buildsystem=pybuild --verbose
+	dh $@  --with python2,python3 --buildsystem=pybuild --verbose
 
 override_dh_auto_install:
 	dh_auto_install
+	dh_movefiles --package=yapf --sourcedir=$(PYBUILD_DESTDIR_python2) usr/bin
 	dh_movefiles --package=yapf3 --sourcedir=$(PYBUILD_DESTDIR_python3) usr/bin
 	(cd $(CURDIR)/debian/yapf3 && mv ./usr/bin/yapf ./usr/bin/yapf3)
-- 
2.19.1

>From 13a56289167c9a0a21ff1a67b66cf5384b386655 Mon Sep 17 00:00:00 2001
From: Hilko Bengen 
Date: Sat, 9 Feb 2019 18:17:58 +0100
Subject: [PATCH 2/3] Re-add yapf documentation files

---
 debian/yapf.docs | 1 +
 debian/yapf.manpages | 1 +
 2 files changed, 2 insertions(+)
 create mode 100644 debian/yapf.docs
 create mode 100644 debian/yapf.manpages

diff --git a/debian/yapf.docs b/debian/yapf.docs
new file mode 100644
index 000..30d8556
--- /dev/null
+++ b/debian/yapf.docs
@@ -0,0 +1 @@
+*.rst
diff --git a/debian/yapf.manpages b/debian/yapf.manpages
new file mode 100644
index 000..fafe023
--- /dev/null
+++ b/debian/yapf.manpages
@@ -0,0 +1 @@
+debian/yapf.1
-- 
2.19.1

>From 8d666fa2b61627d2689b6cd3bddf4f23ea062cb7 Mon Sep 17 00:00:00 2001
From: Hilko Bengen 
Date: Sat, 9 Feb 2019 18:18:38 +0100
Subject: [PATCH 3/3] Debian release 0.25.0-2.1

---
 debian/changelog | 8 
 1 file changed, 8 insertions(+)

diff --git a/debian/changelog b/debian/changelog
index 07510a1

Bug#921305: zfs-dkms: fails to upgrade from stretch

2019-02-09 Thread Andrew G. Dunn
Similarly fails on fresh buster install from Debian Alpha5 install media.

On Mon, 04 Feb 2019 03:47:36 +0100 Andreas Beckmann  wrote:
> Package: zfs-dkms
> Version: 0.7.12-2
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
> 
> Hi,
> 
> during a test with piuparts I noticed your package fails to upgrade from
> 'stretch'.
> It installed fine in 'stretch', then the upgrade to 'buster' fails.
> 
> The problem is the order chosen by apt to process the packages.
> 
> * the new spl-dkms gets configured and builds modules for the stretch kernel
> * the new zfs-dkms gets unpacked
> * the buster kernel headers get unpacked
> * the new zfs-dkms gets configured and attempts to build a module for the
>   buster kernel
> * this fails due to a missing spl-dkms build for the buster kernel
> * the buster kernel headers get configured
> 
> From the attached log (scroll to the bottom...):
> 
> [...]
>  Setting up spl-dkms (0.7.12-1) ...
>   Loading new spl-0.7.12 DKMS files...
>   It is likely that 4.13.2 belongs to a chroot's host
>   Building for 4.9.0-8-amd64
>   Building initial module for 4.9.0-8-amd64
>   Done.
> [...]
>   DKMS: install completed.
> [...]
>   Preparing to unpack .../zfs-dkms_0.7.12-2_all.deb ...
>   
>    Uninstall Beginning 
>   Module:  zfs
>   Version: 0.6.5.9
>   Kernel:  4.9.0-8-amd64 (x86_64)
>   -
>   
>   Status: Before uninstall, this module version was ACTIVE on this kernel.
> [...]
>   DKMS: uninstall completed.
>   
>   --
>   Deleting module version: 0.6.5.9
>   completely from the DKMS tree.
>   --
>   Done.
>   Unpacking zfs-dkms (0.7.12-2) over (0.6.5.9-5) ...
> [...]
>   Selecting previously unselected package linux-compiler-gcc-8-x86.
>   Preparing to unpack .../4-linux-compiler-gcc-8-x86_4.19.12-1_amd64.deb ...
>   Unpacking linux-compiler-gcc-8-x86 (4.19.12-1) ...
>   Selecting previously unselected package linux-headers-4.19.0-1-common.
>   Preparing to unpack .../5-linux-headers-4.19.0-1-common_4.19.12-1_all.deb
...
>   Unpacking linux-headers-4.19.0-1-common (4.19.12-1) ...
>   Selecting previously unselected package linux-kbuild-4.19.



Bug#921772: CVE-2018-1000652

2019-02-09 Thread tony mancill
On Sat, Feb 09, 2019 at 01:11:52AM +0100, gregor herrmann wrote:
> On Fri, 08 Feb 2019 23:37:20 +0100, Moritz Muehlenhoff wrote:
> 
> > This was assigned CVE-2018-1000652:
> > https://github.com/JabRef/jabref/issues/4229
> > https://github.com/JabRef/jabref/commit/89f855d76713b4cd25ac0830c719cd61c511851e

<--snip-->

> private static final Logger LOGGER = 
> LoggerFactory.getLogger(MsBibImporter.class);
>  ^
>   symbol:   class Logger
>   location: class MsBibImporter
> 
> 
> Seems like we either need a new build dependency, or remove the
> logging part, or rewrite it … I'd be grateful for help from Java
> experts :)

Hi Gregor,

Thank you for doing this.  I guess upstream switched out the logging
implementation in their patch.  I'll push an updated patch this weekend.

Cheers,
tony


signature.asc
Description: PGP signature


Bug#921305: zfs-dkms: fails to upgrade from stretch

2019-02-09 Thread Hilko Bengen
Andreas,

I seem to have no way to test this in a chroot, but I'm pretty sure that
this issue could be fixed by adding a versioned Pre-Depends: spl-dkms to
zfs-dkms.

Am I missing something?

Cheers,
-Hilko



Processed: Re: Leafpad over ssh erases file content upon saving

2019-02-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 890416 +moreinfo
Bug #890416 [leafpad] Leafpad over ssh erases file content upon saving
Added tag(s) moreinfo.
> user debian-rele...@lists.debian.org
Setting user to debian-rele...@lists.debian.org (was fgr...@freenet.de).
> usertag 890416 + bsp-2019-02-de-berlin
There were no usertags set.
Usertags are now: bsp-2019-02-de-berlin.
> thanks
Stopping processing here.

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



Bug#890416: Leafpad over ssh erases file content upon saving

2019-02-09 Thread Judit Foglszinger
tags 890416 +moreinfo
user debian-rele...@lists.debian.org
usertag 890416 + bsp-2019-02-de-berlin  
thanks

Behaves differently to me.
When connecting with caja over ssh to localhost and opening a file,
an empty file with title 'Untitled' is opened.
When klicking on the save button, the location where to save to is asked for.

versions:
caja - 1.20.3-1+b1
leafpad - 0.8.18.1-5



Bug#921772: CVE-2018-1000652

2019-02-09 Thread gregor herrmann
On Sat, 09 Feb 2019 09:47:08 -0800, tony mancill wrote:

> > Seems like we either need a new build dependency, or remove the
> > logging part, or rewrite it … I'd be grateful for help from Java
> > experts :)
> Thank you for doing this.  I guess upstream switched out the logging
> implementation in their patch.  I'll push an updated patch this weekend.

Great, thanks Tony!


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Leonard Cohen: I Can't Forget


signature.asc
Description: Digital Signature


Bug#921778: deap: FTBFS (Could not import extension sphinx.ext.pngmath)

2019-02-09 Thread Sascha Steinbiss
user debian-rele...@lists.debian.org
usertag 921778 + bsp-2019-02-de-berlin
thank you

Dear maintainers,

Greetings from the BSP at the DCSO office in Berlin.

I have fixed this bug and attached a patch for the issue.

Cheers
Sascha
diff --git a/debian/changelog b/debian/changelog
index b1133ac..d799f8c 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,10 +1,15 @@
-deap (1.0.2.post2-6) UNRELEASED; urgency=medium
+deap (1.0.2.post2-6.1) UNRELEASED; urgency=medium
 
+  [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * d/watch: Use https protocol
   * d/tests: Use AUTOPKGTEST_TMP instead of ADTTMP
 
- -- Ondřej Nový   Tue, 13 Feb 2018 10:18:20 +0100
+  [ Sascha Steinbiss ]
+  * Use imgmath Sphinx extension instead of deprecated pngmath.
+Closes: #921778
+
+ -- Sascha Steinbiss   Sat, 09 Feb 2019 19:28:44 +0100
 
 deap (1.0.2.post2-5) unstable; urgency=medium
 
diff --git a/debian/patches/0003-remove-pngmath.patch b/debian/patches/0003-remove-pngmath.patch
new file mode 100644
index 000..ec000fb
--- /dev/null
+++ b/debian/patches/0003-remove-pngmath.patch
@@ -0,0 +1,17 @@
+Description: replace pngmath with imgmath
+ The pngmath Sphinx extension has been deprecated in Sphinx 1.4 and
+ was removed for good in Sphinx 1.8. It can be replaced safely by the
+ imgmath extension, which is also available in 1.4 (so also in stretch).
+Author: Sascha Steinbiss 
+Last-Update: 2019-02-09
+--- a/doc/conf.py
 b/doc/conf.py
+@@ -27,7 +27,7 @@
+ # coming with Sphinx (named 'sphinx.ext.*') or your custom ones
+ 
+ extensions = ['sphinx.ext.autodoc', 'sphinx.ext.doctest', 'sphinx.ext.todo',
+-  'sphinx.ext.pngmath', 'sphinx.ext.intersphinx', 'sphinx.ext.extlinks'] 
++  'sphinx.ext.imgmath', 'sphinx.ext.intersphinx', 'sphinx.ext.extlinks']
+ 
+ try:
+ import matplotlib
diff --git a/debian/patches/series b/debian/patches/series
index 233d16a..393233d 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,2 +1,3 @@
 0001-fix-docs.patch
 0002-fix-tests.patch
+0003-remove-pngmath.patch


Processed (with 2 errors): Downgrading severity while packages are still present

2019-02-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity important 921851
Unknown command or malformed arguments to command.
> tags 921851 + pending
Bug #921851 [src:binutils-xtensa-lx106] unnecessary b-d's libisl-0.18-dev and 
libcloog-isl-dev, to be removed for buster
Added tag(s) pending.
> severity important 921855
Unknown command or malformed arguments to command.
> tags 921855 + pending
Bug #921855 [src:gcc-xtensa-lx106] outdated b-d's on libisl-0.18-dev and 
libcloog-isl-dev, to be removed in buster
Added tag(s) pending.
> thanks
Stopping processing here.

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



Processed: Downgrading severity while packages are still present

2019-02-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> severity 921851 important
Bug #921851 [src:binutils-xtensa-lx106] unnecessary b-d's libisl-0.18-dev and 
libcloog-isl-dev, to be removed for buster
Severity set to 'important' from 'serious'
> severity 921855 important
Bug #921855 [src:gcc-xtensa-lx106] outdated b-d's on libisl-0.18-dev and 
libcloog-isl-dev, to be removed in buster
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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



Bug#919001: emacs-gtk: fails to upgrade to 1.26.1+1-3

2019-02-09 Thread Pavel Kreuzt
This bug (or a very similar one) seems to trigger again when upgrading to
emacs-gtk-1:26.1+1-3.2 with emacspeak-49.0+dfsg-2 :

0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
WARNING: Unknown distro but dpkg found, assuming Debian
Setting up emacs-gtk (1:26.1+1-3.2) ...
Install emacsen-common for emacs
emacsen-common: Handling install of emacsen flavor emacs
Install emacspeak for emacs
/usr/lib/emacsen-common/packages/install/emacspeak running in /
Latest installed version: 49.0+dfsg-2
install/emacspeak: Handling install for emacsen flavor emacs
  Temporary log file is /tmp/filedHvWsk
  Byte-compiling  (~0.7 min) ...ERROR: install script from emacspeak
package failed
dpkg: error processing package emacs-gtk (--configure):
 installed emacs-gtk package post-installation script subprocess returned
error exit status 1
dpkg: dependency problems prevent configuration of emacs:
 emacs depends on emacs-gtk (>= 1:26.1) | emacs-lucid (>= 1:26.1) |
emacs-nox (>= 1:26.1); however:
  Package emacs-gtk is not configured yet.
  Package emacs-lucid is not installed.
  Package emacs-nox is not installed.

dpkg: error processing package emacs (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 emacs-gtk
 emacs
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)


On Mon, Jan 14, 2019 at 6:45 PM Paul Gevers  wrote:

> HI,
>
> On 13-01-2019 22:49, Pavel Kreuzt wrote:
> > It's emacspeak-47.0+dfsg-6
>
> I think I understand the issue. Will upload shortly.
>
> Paul
>
>


Bug#919001: emacs-gtk: fails to upgrade to 1.26.1+1-3

2019-02-09 Thread Paul Gevers
Hi Pavel,

Can you please attach the /tmp/filedHvWsk file?

Paul



signature.asc
Description: OpenPGP digital signature


Processed: your mail

2019-02-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 921778 + patch
Bug #921778 [src:deap] deap: FTBFS (Could not import extension 
sphinx.ext.pngmath)
Added tag(s) patch.
> thanks
Stopping processing here.

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



Bug#915426: marked as done (git breaks git-remote-hg autopkgtest)

2019-02-09 Thread Debian Bug Tracking System
Your message dated Sat, 09 Feb 2019 19:29:12 +
with message-id 
and subject line Bug#915426: fixed in git-remote-hg 1.0.0~ds-1
has caused the Debian Bug report #915426,
regarding git breaks git-remote-hg autopkgtest
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.)


-- 
915426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915426
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: git, git-remote-hg
Control: found -1 git/1:2.20.0~rc2-1
Control: found -1 git-remote-hg/0.4-0.1
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainers,

With a recent upload of git the autopkgtest of git-remote-hg fails in
testing when that autopkgtest is run with the binary packages of git
from unstable. It passes when run with only packages from testing. In
tabular form:
   passfail
gitfrom testing1:2.20.0~rc2-1
git-remote-hg  from testing0.4-0.1
versioned deps [0] from testingfrom unstable
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is contributing to the delay of the migration
of git to testing [1]. Due to the nature of this issue, I filed this bug
report against both packages. Can you please investigate the situation
and reassign the bug to the right package? If needed, please change the
bug's severity.

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[0] You can see what packages were added from the second line of the log
file quoted below. The migration software adds source package from
unstable to the list if they are needed to install packages from
git/1:2.20.0~rc2-1. I.e. due to versioned dependencies or breaks/conflicts.
[1] https://qa.debian.org/excuses.php?package=git

https://ci.debian.net/data/autopkgtest/testing/amd64/g/git-remote-hg/1428119/log.gz

not ok 32 - pull tags
#   
#   test_when_finished "rm -rf hgrepo gitrepo" &&
#   
#   (
#   hg init hgrepo &&
#   cd hgrepo &&
#   echo one > content &&
#   hg add content &&
#   hg commit -m one
#   ) &&
#   
#   git clone "hg::hgrepo" gitrepo &&
#   
#   (cd hgrepo && hg tag v1.0) &&
#   (cd gitrepo && git pull) &&
#   
#   echo "v1.0" > expected &&
#   git --git-dir=gitrepo/.git tag > actual &&
#   test_cmp expected actual
#   
ok 33 - push merged named branch
ok 34 - light tag sets author
ok 35 - push tag different branch
ok 36 - cloning a removed file works
ok 37 - cloning a file replaced with a directory
ok 38 - clone replace directory with a file
ok 39 - clone can ignore invalid refnames
# 1 known breakage(s) vanished; please update test(s)
# still have 2 known breakage(s)
# failed 1 among remaining 36 test(s)
1..39
make: *** [Makefile:14: main.t] Error 1



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: git-remote-hg
Source-Version: 1.0.0~ds-1

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated git-remote-hg 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: Sat, 09 Feb 2019 19:42:14 +0100
Source: git-remote-hg
Architecture: source
Version: 1.0.0~ds-1
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard 
Changed-By: Jonas Smedegaard 
Closes: 915426
Changes:
 git-remote-hg (1.0.0~ds-1) unstable; urgency=medium
 .
   [ upstream ]
   * New release.
 + Fixes to support Mercurial 4.7.
   Closes: Bug#915426. Thanks to Paul Gevers.
 .
   [ Ondřej Nový ]
   * Update copyright info: Use https protocol in Format field
   * Use package section optional (not obsolete extra).
   

  1   2   >