Bug#974570: ismrmrd: missing libpugi-dev runtime dependency

[Gianfranco Costamagna]

Hello,


I fixed and pushed on git the arch:all/arch:any builds and autopkgtests

commit d2d320434f30ecefc1ed8b88c0dc89c74b92b64d (HEAD -> master, origin/master, 
origin/HEAD)
Author: Gianfranco Costamagna 
Date:   Thu Nov 12 13:22:27 2020 +0100

Update changelog

:100644 100644 b617ae1 824ae5c Mdebian/changelog

commit eb9a0d0fb17104829fb95e96446d180e49a4e916
Author: Gianfranco Costamagna 
Date:   Thu Nov 12 13:21:50 2020 +0100

Really fix arc:all and arch:any builds

:100755 100755 7300b9e 7c27cff Mdebian/rules

commit 662b5b1fdc1b1b098149fed3a227d9d5950c5d4e
Author: Gianfranco Costamagna 
Date:   Thu Nov 12 13:21:17 2020 +0100

Add a runtime dependency on libpugixml-dev to fix autopkgtest failure 
(Closes: #974570)

:100644 100644 f9b2605 cd950bd Mdebian/control


Please have another look and upload if possible :)

G.
On Thu, 12 Nov 2020 12:56:09 +0100 Gianfranco Costamagna 
 wrote:
> Source: ismrmrd
> Version: 1.4.2.1-4
> Severity: serious
> tags: patch
> 
> Hello, autopkgtests fails because of:
> cmake ../../ismrmrd-1.4.2.1/examples/c/
> -- Could NOT find PugiXML (missing: PugiXML_DIR)
> CMake Error at 
> /usr/share/cmake-3.16/Modules/CMakeFindDependencyMacro.cmake:47 
> (find_package):
>   By not providing "FindPugiXML.cmake" in CMAKE_MODULE_PATH this project has
>   asked CMake to find a package configuration file provided by "PugiXML", but
>   CMake did not find one.
> 
>   Could not find a package configuration file provided by "PugiXML" with any
>   of the following names:
> 
> PugiXMLConfig.cmake
> pugixml-config.cmake
> 
>   Add the installation prefix of "PugiXML" to CMAKE_PREFIX_PATH or set
>   "PugiXML_DIR" to a directory containing one of the above files.  If
>   "PugiXML" provides a separate development package or SDK, be sure it has
>   been installed.
> Call Stack (most recent call first):
>   /usr/lib/cmake/ISMRMRD/ISMRMRDConfig.cmake:74 (find_dependency)
>   CMakeLists.txt:6 (find_package)
> 
> 
> -- Configuring incomplete, errors occurred!
> 
> 
> looks like the dev package should also depend on pugixml-dev
> 
> --- control.old   2020-11-12 12:55:48.292055695 +0100
> +++ debian/control2020-11-12 12:55:57.039998908 +0100
> @@ -44,6 +44,7 @@ Multi-Arch: same
>  Section: libdevel
>  Depends: ${misc:Depends},
>   libhdf5-dev,
> + libpugixml-dev,
>   libismrmrd1.4 (= ${binary:Version})
>  Suggests: libismrmrd-doc
>  Description: development files for ISMRMRD
> 
> 
> G.
> 
> 

Bug#973939: fixed in ismrmrd 1.4.2.1-4

[Gianfranco Costamagna]

control: reopen -1
control: notfixed -1 1.4.2.1-4
thanks

On Thu, 12 Nov 2020 09:03:47 + Debian FTP Masters 
 wrote:
> Source: ismrmrd
> Source-Version: 1.4.2.1-4
> Done: Andreas Tille 
> 
> We believe that the bug you reported is fixed in the latest version of
> ismrmrd, 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 973...@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
> 
> Debian distribution maintenance software
> pp.
> Andreas Tille  (supplier of updated ismrmrd 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: Thu, 12 Nov 2020 09:40:14 +0100
> Source: ismrmrd
> Architecture: source
> Version: 1.4.2.1-4
> Distribution: unstable
> Urgency: medium
> Maintainer: Debian Med Packaging Team 
> 
> Changed-By: Andreas Tille 
> Closes: 973939
> Changes:
>  ismrmrd (1.4.2.1-4) unstable; urgency=medium
>  .
>* Team upload.
>* Really fix binary-all FTBFS
>  Closes: #973939
> Checksums-Sha1:
>  1b52e75b889e967c7aae837935b210e09097f173 2401 ismrmrd_1.4.2.1-4.dsc
>  e62634aacd99678adb7790247d814105a202ae28 7324 ismrmrd_1.4.2.1-4.debian.tar.xz
>  3129252f0f350dbeee3d0238a75f1cbe655ea573 9738 
> ismrmrd_1.4.2.1-4_amd64.buildinfo
> Checksums-Sha256:
>  5914ea4e98743d4b9a9556c4e3bb12d2258f12faecf88647d19a97e61865f019 2401 
> ismrmrd_1.4.2.1-4.dsc
>  19e50d753d837a2c3aa44dade0dbe6bf1b507cf0c5f1cfb340664fb05b3891e9 7324 
> ismrmrd_1.4.2.1-4.debian.tar.xz
>  7cba57d1835386f9fbb88f19ce0dd7243d13db8e7ad1dc87f9a6f4c774709804 9738 
> ismrmrd_1.4.2.1-4_amd64.buildinfo
> Files:
>  ee9c8dac51d5bde9cac5bc528352a9d2 2401 science optional ismrmrd_1.4.2.1-4.dsc
>  1d9dfbb1acfb37f134584b9bf4c2b2e0 7324 science optional 
> ismrmrd_1.4.2.1-4.debian.tar.xz
>  7a218b14995d5dc833890e350da450a3 9738 science optional 
> ismrmrd_1.4.2.1-4_amd64.buildinfo
> 
> -BEGIN PGP SIGNATURE-
> 
> iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl+s9pURHHRpbGxlQGRl
> Ymlhbi5vcmcACgkQV4oElNHGRtGJbw//c61G9QHyUFcZjPkxSlg4eWHDUbXxvvFk
> 1VF6i+KKlzXSN4eyGxBWOQr4m4bT60SLbHx+UV6/7dhbGOc+cc2QshVtGcKrEI3i

Bug#974570: marked as pending in ismrmrd

[Gianfranco Costamagna]

Control: tag -1 pending

Hello,

Bug #974570 in ismrmrd 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/med-team/ismrmrd/-/commit/662b5b1fdc1b1b098149fed3a227d9d5950c5d4e


Add a runtime dependency on libpugixml-dev to fix autopkgtest failure (Closes: 
#974570)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/974570

Bug#974570: ismrmrd: missing libpugi-dev runtime dependency

[Gianfranco Costamagna]

Source: ismrmrd
Version: 1.4.2.1-4
Severity: serious
tags: patch

Hello, autopkgtests fails because of:
cmake ../../ismrmrd-1.4.2.1/examples/c/
-- Could NOT find PugiXML (missing: PugiXML_DIR)
CMake Error at /usr/share/cmake-3.16/Modules/CMakeFindDependencyMacro.cmake:47 
(find_package):
  By not providing "FindPugiXML.cmake" in CMAKE_MODULE_PATH this project has
  asked CMake to find a package configuration file provided by "PugiXML", but
  CMake did not find one.

  Could not find a package configuration file provided by "PugiXML" with any
  of the following names:

PugiXMLConfig.cmake
pugixml-config.cmake

  Add the installation prefix of "PugiXML" to CMAKE_PREFIX_PATH or set
  "PugiXML_DIR" to a directory containing one of the above files.  If
  "PugiXML" provides a separate development package or SDK, be sure it has
  been installed.
Call Stack (most recent call first):
  /usr/lib/cmake/ISMRMRD/ISMRMRDConfig.cmake:74 (find_dependency)
  CMakeLists.txt:6 (find_package)


-- Configuring incomplete, errors occurred!


looks like the dev package should also depend on pugixml-dev

--- control.old 2020-11-12 12:55:48.292055695 +0100
+++ debian/control  2020-11-12 12:55:57.039998908 +0100
@@ -44,6 +44,7 @@ Multi-Arch: same
 Section: libdevel
 Depends: ${misc:Depends},
  libhdf5-dev,
+ libpugixml-dev,
  libismrmrd1.4 (= ${binary:Version})
 Suggests: libismrmrd-doc
 Description: development files for ISMRMRD


G.

Bug#973292: blender ftbfs with python3.9

[Gianfranco Costamagna]

control: tags -1 patch fixed-upstream

this commit
https://github.com/blender/blender/commit/56d0df51a36fdce7ec2d1fbb7b47b1d95b591b5f

Might be the fix

G.

On Wed, 28 Oct 2020 09:27:15 +0100 Matthias Klose  wrote:
> Package: src:blender
> Version: 2.83.5+dfsg-3
> Severity: serious
> Tags: sid bullseye ftbfs
> User: debian-pyt...@lists.debian.org
> Usertags: python3.9
> 
> to reproduce, you can use the repositories found at:
> 
> deb [trusted=yes] http://people.debian.org/~doko/tmp/python3.9 ./
> deb [trusted=yes] http://people.debian.org/~ginggs/python3.9-repo ./
> 
> https://people.debian.org/~ginggs/python3.9-default/blender_2.83.5+dfsg-3+build1_amd64-2020-10-26T09:00:19Z.build
> 
> 
> [...]
> /<>/blender-2.83.5+dfsg/source/blender/python/mathutils/mathutils_Matrix.c:1948:33:
> error: ‘PyNoArgsFunction’ undeclared (first use in this function); did you 
> mean
> ‘PyCFunction’?
>  1948 |   return matrix__apply_to_copy((PyNoArgsFunction)Matrix_transpose, 
> self);
>   | ^~~~
>   | PyCFunction
> /<>/blender-2.83.5+dfsg/source/blender/python/mathutils/mathutils_Matrix.c:1948:50:
> error: expected ‘)’ before ‘Matrix_transpose’
>  1948 |   return matrix__apply_to_copy((PyNoArgsFunction)Matrix_transpose, 
> self);
>   |  ^~~~
>   |  )
> /<>/blender-2.83.5+dfsg/source/blender/python/mathutils/mathutils_Matrix.c:1946:50:
> warning: unused parameter ‘self’ [-Wunused-parameter]
>  1946 | static PyObject *Matrix_transposed(MatrixObject *self)
>   |~~^~~~
> /<>/blender-2.83.5+dfsg/source/blender/python/mathutils/mathutils_Matrix.c:
> In function ‘Matrix_normalized’:
> /<>/blender-2.83.5+dfsg/source/blender/python/mathutils/mathutils_Matrix.c:1994:33:
> error: ‘PyNoArgsFunction’ undeclared (first use in this function); did you 
> mean
> ‘PyCFunction’?
>  1994 |   return matrix__apply_to_copy((PyNoArgsFunction)Matrix_normalize, 
> self);
>   | ^~~~
>   | PyCFunction
> /<>/blender-2.83.5+dfsg/source/blender/python/mathutils/mathutils_Matrix.c:1994:50:
> error: expected ‘)’ before ‘Matrix_normalize’
>  1994 |   return matrix__apply_to_copy((PyNoArgsFunction)Matrix_normalize, 
> self);
>   |  ^~~~
>   |  )
> /<>/blender-2.83.5+dfsg/source/blender/python/mathutils/mathutils_Matrix.c:1992:50:
> warning: unused parameter ‘self’ [-Wunused-parameter]
>  1992 | static PyObject *Matrix_normalized(MatrixObject *self)
>   |~~^~~~
> 
> 

Bug#973520: openstack-pkg-tools: uses python2

[Gianfranco Costamagna]

control: tags -1 pending
control: severity -1 important

After having another look, I don't think serious is appropriate as severity, 
and FYI I just committed the changes
on git, will not make an upload just for this bug, but feel free to do it :)

thanks

G.

Bug#973520: marked as pending in openstack-pkg-tools

[Gianfranco Costamagna]

Control: tag -1 pending

Hello,

Bug #973520 in openstack-pkg-tools 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/openstack-team/debian/openstack-pkg-tools/-/commit/9455f8da5c9d1ec2f0e37af1e1eccd195c592d26


Update pkgos-generate-snapshot, use Python3 instead of deprecated Python2 
(Closes: #973520)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/973520

Bug#973520: openstack-pkg-tools: uses python2

[Gianfranco Costamagna]

Source: openstack-pkg-tools
Version: 114
Severity: serious
tags: patch

Hello,


diff -Nru openstack-pkg-tools-113/build-tools/pkgos-generate-snapshot 
openstack-pkg-tools-113ubuntu1/build-tools/pkgos-generate-snapshot
--- openstack-pkg-tools-113/build-tools/pkgos-generate-snapshot 2019-11-20 
10:25:50.0 +
+++ openstack-pkg-tools-113ubuntu1/build-tools/pkgos-generate-snapshot  
2020-07-30 23:34:17.0 +
@@ -3,7 +3,7 @@
 set -e
 
 rm -f dist/*
-python setup.py sdist
+python3 setup.py sdist
 package=$(cd dist; ls -1 *.tar.gz)
 version=$(echo $package | sed -e "s/\.tar\.gz//" -e "s/.*-//g")
 deb_version=$(echo $version | sed -e "s/\.0a/~a/" -e "s/\.0b/~b/" -e 
"s/\.dev/~dev/")


Please apply to let python2 go away

Patch provided by James Page 

thanks

Gianfranco

Bug#962194: lintian-brush: autopkgtest failure on s390x

[Gianfranco Costamagna]

Hello,


> https://yaml.readthedocs.io/en/latest/basicuse.html#more-examples
> 
> from ruamel.yaml import YAML
> 
> yaml=YAML(typ="safe", pure=True)
> yaml.load(f)
> 
> If that works, then we might be able to make a workaround to default to the
> pure Python version on big endian systems. To be reverted once upstream has
> a proper fix to the cpython code, of course.
> 
> Note: ruamel.yaml is mostly a one person (Anthon van der Neut) project, so
> a fix might take a while. Fans of s390x and other big endian architectures
> are very welcome to develop a patch!
> 
> https://yaml.readthedocs.io/en/latest/contributing.html
> 

not sure if I did it right, but this code:

#!/usr/bin/python3
from io import BytesIO
from ruamel.yaml import YAML
yaml = YAML(typ='safe', pure=True)

f = BytesIO(b"""\
format: multiarch-hints-1.0
hints:
- binary: coinor-libcoinmp-dev
  description: coinor-libcoinmp-dev conflicts on ...
  link: https://wiki.debian.org/MultiArch/Hints#file-conflict
  severity: high
  source: coinmp
  version: 1.8.3-2+b11
""")
yaml.load(f)


works now
thanks!

Gianfranco

Bug#962194: lintian-brush: autopkgtest failure on s390x

[Gianfranco Costamagna]

control: forwarded -1 https://sourceforge.net/p/ruamel-yaml/tickets/360/

G.

Bug#969538: vips/ruby-vips: autopkgtest regression on arm64 and ppc64el

[Gianfranco Costamagna]

According to upstream, this might fix the issue

diff -Nru vips-8.10.1/debian/changelog vips-8.10.1/debian/changelog
--- vips-8.10.1/debian/changelog2020-10-03 18:41:08.0 +0200
+++ vips-8.10.1/debian/changelog2020-10-07 13:20:49.0 +0200
@@ -1,3 +1,12 @@
+vips (8.10.1-2ubuntu1) groovy; urgency=medium
+
+  * debian/patches/143c815a0a85cb187bc6f690dab0555fd617063e.patch:
+- cherry-pick an upstream fix for autopkgtests on arm64 and ppc64el
+  ( See Debian bug: #969538 and
+https://github.com/libvips/libvips/issues/1846 )
+
+ -- Gianfranco Costamagna   Wed, 07 Oct 2020 
13:20:49 +0200
+
 vips (8.10.1-2) unstable; urgency=medium
 
   * Backport upstream fix for docs building with gobject-introspection 1.66+
diff -Nru 
vips-8.10.1/debian/patches/143c815a0a85cb187bc6f690dab0555fd617063e.patch 
vips-8.10.1/debian/patches/143c815a0a85cb187bc6f690dab0555fd617063e.patch
--- vips-8.10.1/debian/patches/143c815a0a85cb187bc6f690dab0555fd617063e.patch   
1970-01-01 01:00:00.0 +0100
+++ vips-8.10.1/debian/patches/143c815a0a85cb187bc6f690dab0555fd617063e.patch   
2020-10-07 13:20:49.0 +0200
@@ -0,0 +1,37 @@
+Origin: 
https://github.com/kleisauke/libvips/commit/143c815a0a85cb187bc6f690dab0555fd617063e
+Bug: https://github.com/libvips/libvips/issues/1846
+From 143c815a0a85cb187bc6f690dab0555fd617063e Mon Sep 17 00:00:00 2001
+From: kleisauke 
+Date: Wed, 7 Oct 2020 15:20:18 +0200
+Subject: [PATCH] Try a patch for libvips/libvips#1846
+
+---
+ libvips/morphology/morph.c | 8 
+ 1 file changed, 4 insertions(+), 4 deletions(-)
+
+diff --git a/libvips/morphology/morph.c b/libvips/morphology/morph.c
+index 7f7ffc485..07a6fc517 100644
+--- a/libvips/morphology/morph.c
 b/libvips/morphology/morph.c
+@@ -449,8 +449,8 @@ vips_dilate_gen( VipsRegion *or,
+   seq->ss = 0;
+   seq->cs = 0;
+   for( y = 0; y < M->Ysize; y++ )
+-  for( x = 0; x < M->Xsize; x++ )
+-  switch( t[x] ) {
++  for( x = 0; x < M->Xsize; x++, t++ )
++  switch( *t ) {
+   case 255:
+   soff[seq->ss++] =
+   VIPS_REGION_ADDR( ir, 
+@@ -560,8 +560,8 @@ vips_erode_gen( VipsRegion *or,
+   seq->ss = 0;
+   seq->cs = 0;
+   for( y = 0; y < M->Ysize; y++ )
+-  for( x = 0; x < M->Xsize; x++ )
+-  switch( t[x] ) {
++  for( x = 0; x < M->Xsize; x++, t++ )
++  switch( *t ) {
+   case 255:
+   soff[seq->ss++] =
+   VIPS_REGION_ADDR( ir, 
diff -Nru vips-8.10.1/debian/patches/series vips-8.10.1/debian/patches/series
--- vips-8.10.1/debian/patches/series   2020-10-03 18:41:08.0 +0200
+++ vips-8.10.1/debian/patches/series   2020-10-07 13:20:49.0 +0200
@@ -1,2 +1,3 @@
 reproducible-build.patch
 fix_build_with_goi_1.66+.patch
+143c815a0a85cb187bc6f690dab0555fd617063e.patch


G.

Bug#969538: vips/ruby-vips: autopkgtest regression on arm64 and ppc64el

[Gianfranco Costamagna]

control: forwarded -1 https://github.com/libvips/libvips/issues/1846

thanks

G.

Bug#969538: vips/ruby-vips: autopkgtest regression on arm64 and ppc64el

[Gianfranco Costamagna]

control: affects -1 ruby-vips

G.
On Fri, 4 Sep 2020 17:14:23 +0200 Gianfranco Costamagna 
 wrote:
> Source: vips
> Version: 8.10.0-1
> Severity: serious
> 
> Hello, your package regressed its testsuite on arm64 in Debian and Ubuntu (in 
> Ubuntu also ppc64el, in Debian I didn't check but the failure is the same)
> 
> https://ci.debian.net/packages/r/ruby-vips/testing/arm64/
> 
> 
> ??? Checking Rubygems dependency resolution on ruby2.7
>???
> 
> 
> GEM_PATH= ruby2.7 -e gem\ \"ruby-vips\"
> 
> 
> ??? Run tests for ruby2.7 from debian/ruby-tests.rake 
>???
> 
> 
> mv lib .gem2deb.lib
> RUBYLIB=. GEM_PATH= ruby2.7 -S rake -f debian/ruby-tests.rake
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib/rspec/core/rake_task.rb:125:
>  warning: deprecated Object#=~ is called on Array; it always returns nil
> /usr/bin/ruby2.7 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.2/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/exe/rspec 
> --pattern ./spec/\*\*/\*_spec.rb --backtrace -r ./spec/spec_helper.rb
> ./usr/lib/ruby/vendor_ruby/vips/object.rb:269: warning: Capturing 
> the given block using Proc.new is deprecated; use `` instead
> /usr/lib/ruby/vendor_ruby/vips/object.rb:269: warning: Capturing the given 
> block using Proc.new is deprecated; use `` instead
> ./usr/lib/ruby/vendor_ruby/vips/object.rb:269: warning: Capturing the given 
> block using Proc.new is deprecated; use `` instead
> ../usr/lib/ruby/vendor_ruby/vips/object.rb:269: warning: Capturing the given 
> block using Proc.new is deprecated; use `` instead
> /usr/lib/ruby/vendor_ruby/vips/object.rb:269: warning: Capturing the given 
> block using Proc.new is deprecated; use `` instead
> ..F
> 
> Failures:
> 
>   1) Vips::Image can dilate
>  Failure/Error: expect(im.getpoint(11, 12)).to eq([255])
> 
>expected: [255]
> got: [0.0]
> 
>(compared using ==)
>  # 
> /usr/share/rubygems-integration/all/gems/rspec-support-3.9.2/lib/rspec/support.rb:97:in
>  `block in '
>  # 
> /usr/share/rubygems-integration/all/gems/rspec-support-3.9.2/lib/rspec/support.rb:106:in
>  `notify_failure'
>  # 
> /usr/share/rubygems-integration/all/gems/rspec-expectations-3.9.0/lib/rspec/expectations/fail_with.rb:35:in
>  `fail_with'
>  # 
> /usr/share/rubygems-integration/all/gems/rspec-expectations-3.9.0/lib/rspec/expectations/handler.rb:38:in
>  `handle_failure'
>  # 
> /usr/share/rubygems-integration/all/gems/rspec-expectations-3.9.0/lib/rspec/expectations/handler.rb:50:in
>  `block in handle_matcher'
>  # 
> /usr/share/rubygems-integration/all/gems/rspec-expectations-3.9.0/lib/rspec/expectations/handler.rb:27:in
>  `with_matcher'
>  # 
> /usr/share/rubygems-integration/all/gems/rspec-expectations-3.9.0/lib/rspec/expectations/handler.rb:48:in
>  `handle_matcher'
>  # 
> /usr/share/rubygems-integration/all/gems/rspec-expectations-3.9.0/lib/rspec/expectations/expectation_target.rb:65:in
>  `to'
>  # ./spec/image_spec.rb:477:in `block (2 levels) in '
>  # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib/rspec/core/example.rb:257:in
>  `instance_exec'
>  # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib/rspec/core/example.rb:257:in
>  `block in run'
>  # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib/rspec/core/example.rb:503:in
>  `block in with_around_and_singleton_context_hooks'
>  # 
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib/rspec/core/exampl

Bug#908681: libsane1: pointless package rename

[Gianfranco Costamagna]

Hello Joerg,

> We are not back.

to be honest, yes we are :)

> 
> Between 1.0.30 and 1.0.31 are the following 7 symbols are not longer 
> available:
> 
> #MISSING: 1.0.31# testing_append_commands_node@Base 1.0.29
> #MISSING: 1.0.31# testing_known_commands_input_failed@Base 1.0.29
> #MISSING: 1.0.31# testing_last_known_seq@Base 1.0.29
> #MISSING: 1.0.31# testing_record_backend@Base 1.0.29
> #MISSING: 1.0.31# testing_xml_doc@Base 1.0.29
> #MISSING: 1.0.31# testing_xml_next_tx_node@Base 1.0.29
> #MISSING: 1.0.31# testing_xml_path@Base 1.0.29
> 
> This ABI changes are not backward-compatible. And so the change are required. 
> 

So, to explain:

If you think they are not backward-compatible, you should rename the package, 
but not provide the old SONAME
as transitional package, otherwise you are doing a mistake

In this case, the symbols were private, and incorrectly exposed outside, so 
removing them is "safe"
as long as nobody uses them.

When I sponsored the package for you, even if I forgot to write that on the RFS 
bug, I had a discussion about this
with some other DDs, and we agreeded that this wasn't worth a SONAME change, 
because the end user applications
were still ABI-safe.

So, this is why I asked you to restore the old package name, and make it 
transitional, to avoid people being forced
to upgrade to a new library SONAME without a real SONAME change.

This way, we made almost "everybody" happy, or at least improved the status quo 
for some bits.

(the real world fix was to ignore lintian, or to not start with a wrong soname, 
but this history now)

So, yes, the ABI changed, but the change was not reflected into a real issue 
for any Debian application, or any custom-built application.

I honestly think we should just move forward, and change the soname again if a 
the library changes in the future.

G.

Bug#971687: Bug#971668: libsane: broke ABI

[Gianfranco Costamagna]

control: severity -1 important
control: reassign -1 src:sane-backends
control: retitle -1 sane-backends: dropped unused symbols without changing 
SONAME 


Hello Vincent and Sebastian

On Mon, 5 Oct 2020 03:48:26 +0200 Vincent Lefevre  wrote:
> Control: clone -1 -2
> Control: reassign -2 libsane1 1.0.31-2
> Control: retitle -2 libsane1: broke ABI
> 
> On 2020-10-04 18:03:30 +0200, Sebastian Ramacher wrote:
> > Package: libsane
> > Version: 1.0.31-2
> > Severity: grave
> > 
> > From 1.0.31-1~experimental1:
> > 
> >* debian/libsane1.symbols:
> > - Remove 7 not longer available symbols.
> > 
> > Hence provinding libsane that depends on libsane1 with a different ABI
> > is wrong.
> 
> Not just libsane is wrong, but libsane1 (which contains the library
> itself) too (at least for programs compiled by users).
> 

Seriously?

this is the list of "dropped symbols"

- testing_append_commands_node@Base 1.0.29
- testing_known_commands_input_failed@Base 1.0.29
- testing_last_known_seq@Base 1.0.29
- testing_record_backend@Base 1.0.29
- testing_xml_doc@Base 1.0.29
- testing_xml_next_tx_node@Base 1.0.29
- testing_xml_path@Base 1.0.29


Please find a single reference of something in the archive, or outside the 
archive, that ever used
part of such (not meant to be exported) API.

The *bug* was to export them in the previous version, not to remove them, 
because meant to be internal symbols.

We had other references in the archive history, where symbols incorrectly 
exposed were dropped without
the need to change the ABI.

We discussed many times already, few people (including I guess the sponsor for 
that particular upload), and at least
3 other DDs agreeded that there was no need to change the SONAME just because 
of something that was not really
used anywhere in the world, included self-compiled stuff.

All the RFS bugs for sane-backends are public, you can find lots of discussion 
about the topic, and help
in better developing the package.

I think this is a non-issue, I would like to have some real bugs before talking 
about the Sex Of Angels... [1]

I also think its better have one single bug, instead of having two of them, for 
the very same source package.


(sorry for the Italian reference :) )
[1] https://www.englishforums.com/English/SexOfAngels/kxpgm/post.htm

just my .02$

Gianfranco

> -- 
> Vincent Lefèvre  - Web: 
> 100% accessible validated (X)HTML - Blog: 
> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
> 
> 

Bug#969141: fixed in doxygen 1.8.20-3

[Gianfranco Costamagna]

control: fixed -1 1.8.20-4
control: close -1

at the end upstream committed a very simple and straightforward additional fix, 
that I just cherry-picked
and uploaded.

G.

On Fri, 2 Oct 2020 12:29:53 +0200 Gianfranco Costamagna 
 wrote:
> Hello,
> 
> I don't want to package a snapshot, so I'll leave this bug open, 1.8.21 will 
> contain the fix anyway.
> 
> G.
> On Fri, 2 Oct 2020 09:34:36 +0200 Gianfranco Costamagna 
>  wrote:
> > control: reopen -1
> > control: notfixed -1 1.8.20-3
> > 
> > Unfortunately for some reasons, commit 
> > d067baf495d0415283ce724ad32cb9a08dc17c83 didn't fix the issue,
> > even if my git bisect resulted in it being the culprit.
> > 
> > I suspect we need some other changes between the 1.8.20 tag and commit 
> > d067baf495d0415283ce724ad32cb9a08dc17c83
> > I'll try to spot them
> > 
> > G.
> > 
> > On Thu, 01 Oct 2020 21:33:47 + Debian FTP Masters 
> >  wrote:
> > > Source: doxygen
> > > Source-Version: 1.8.20-3
> > > Done: Gianfranco Costamagna 
> > > 
> > > We believe that the bug you reported is fixed in the latest version of
> > > doxygen, 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 969...@bugs.debian.org,
> > > and the maintainer will reopen the bug report if appropriate.
> > > 
> > > Debian distribution maintenance software
> > > pp.
> > > Gianfranco Costamagna  (supplier of updated 
> > > doxygen package)
> > > 
> > > (This message was generated automatically at their request; if you
> > > believe that there is a problem with it please contact the archive
> > > administrators by mailing ftpmas...@ftp-master.debian.org)
> > > 
> > > 
> > > -BEGIN PGP SIGNED MESSAGE-
> > > Hash: SHA256
> > > 
> > > Format: 1.8
> > > Date: Thu, 01 Oct 2020 23:23:51 +0200
> > > Source: doxygen
> > > Architecture: source
> > > Version: 1.8.20-3
> > > Distribution: unstable
> > > Urgency: medium
> > > Maintainer: Paolo Greppi 
> > > Changed-By: Gianfranco Costamagna 
> > > Closes: 969141
> > > Changes:
> > >  doxygen (1.8.20-3) unstable; urgency=medium
> > >  .
> > >* Team upload (salsa.d.o namespace)
> > >* debian/patches/d067baf495d0415283ce724ad32cb9a08dc17c83.patch:
> > >  - cherry-pick upstream fix for crash during parse with CLANG helper

Bug#969141: fixed in doxygen 1.8.20-3

[Gianfranco Costamagna]

Hello,

I don't want to package a snapshot, so I'll leave this bug open, 1.8.21 will 
contain the fix anyway.

G.
On Fri, 2 Oct 2020 09:34:36 +0200 Gianfranco Costamagna 
 wrote:
> control: reopen -1
> control: notfixed -1 1.8.20-3
> 
> Unfortunately for some reasons, commit 
> d067baf495d0415283ce724ad32cb9a08dc17c83 didn't fix the issue,
> even if my git bisect resulted in it being the culprit.
> 
> I suspect we need some other changes between the 1.8.20 tag and commit 
> d067baf495d0415283ce724ad32cb9a08dc17c83
> I'll try to spot them
> 
> G.
> 
> On Thu, 01 Oct 2020 21:33:47 + Debian FTP Masters 
>  wrote:
> > Source: doxygen
> > Source-Version: 1.8.20-3
> > Done: Gianfranco Costamagna 
> > 
> > We believe that the bug you reported is fixed in the latest version of
> > doxygen, 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 969...@bugs.debian.org,
> > and the maintainer will reopen the bug report if appropriate.
> > 
> > Debian distribution maintenance software
> > pp.
> > Gianfranco Costamagna  (supplier of updated 
> > doxygen package)
> > 
> > (This message was generated automatically at their request; if you
> > believe that there is a problem with it please contact the archive
> > administrators by mailing ftpmas...@ftp-master.debian.org)
> > 
> > 
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> > 
> > Format: 1.8
> > Date: Thu, 01 Oct 2020 23:23:51 +0200
> > Source: doxygen
> > Architecture: source
> > Version: 1.8.20-3
> > Distribution: unstable
> > Urgency: medium
> > Maintainer: Paolo Greppi 
> > Changed-By: Gianfranco Costamagna 
> > Closes: 969141
> > Changes:
> >  doxygen (1.8.20-3) unstable; urgency=medium
> >  .
> >* Team upload (salsa.d.o namespace)
> >* debian/patches/d067baf495d0415283ce724ad32cb9a08dc17c83.patch:
> >  - cherry-pick upstream fix for crash during parse with CLANG helper
> >(Closes: #969141)
> > Checksums-Sha1:
> >  d79d3d39af78cf8faa8b46eb160e68ec8ee65a57 2728 doxygen_1.8.20-3.dsc
> >  49c0a4f80201e3e9b9d0408b785404e006ad89f8 29688 
> > doxygen_1.8.20-3.debian.tar.xz
> >  ff9be745b7ff6b162dc0f3da07ecdb61e2979e66 12896 
> > doxygen_1.8.20-3_source.buildinfo
> > Checksums-Sha256:

Bug#969141: fixed in doxygen 1.8.20-3

[Gianfranco Costamagna]

control: reopen -1
control: notfixed -1 1.8.20-3

Unfortunately for some reasons, commit d067baf495d0415283ce724ad32cb9a08dc17c83 
didn't fix the issue,
even if my git bisect resulted in it being the culprit.

I suspect we need some other changes between the 1.8.20 tag and commit 
d067baf495d0415283ce724ad32cb9a08dc17c83
I'll try to spot them

G.

On Thu, 01 Oct 2020 21:33:47 + Debian FTP Masters 
 wrote:
> Source: doxygen
> Source-Version: 1.8.20-3
> Done: Gianfranco Costamagna 
> 
> We believe that the bug you reported is fixed in the latest version of
> doxygen, 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 969...@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
> 
> Debian distribution maintenance software
> pp.
> Gianfranco Costamagna  (supplier of updated doxygen 
> package)
> 
> (This message was generated automatically at their request; if you
> believe that there is a problem with it please contact the archive
> administrators by mailing ftpmas...@ftp-master.debian.org)
> 
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
> 
> Format: 1.8
> Date: Thu, 01 Oct 2020 23:23:51 +0200
> Source: doxygen
> Architecture: source
> Version: 1.8.20-3
> Distribution: unstable
> Urgency: medium
> Maintainer: Paolo Greppi 
> Changed-By: Gianfranco Costamagna 
> Closes: 969141
> Changes:
>  doxygen (1.8.20-3) unstable; urgency=medium
>  .
>* Team upload (salsa.d.o namespace)
>* debian/patches/d067baf495d0415283ce724ad32cb9a08dc17c83.patch:
>  - cherry-pick upstream fix for crash during parse with CLANG helper
>(Closes: #969141)
> Checksums-Sha1:
>  d79d3d39af78cf8faa8b46eb160e68ec8ee65a57 2728 doxygen_1.8.20-3.dsc
>  49c0a4f80201e3e9b9d0408b785404e006ad89f8 29688 doxygen_1.8.20-3.debian.tar.xz
>  ff9be745b7ff6b162dc0f3da07ecdb61e2979e66 12896 
> doxygen_1.8.20-3_source.buildinfo
> Checksums-Sha256:
>  9431dd4f438312267ce6a82d36d2f1e7e150586167d9cefe24e1ea6e24143a5f 2728 
> doxygen_1.8.20-3.dsc
>  a5c97fa4e2c7930ed7fd1f3acd2ad7b8d46181fe3e611348681fb1d4b2c0776b 29688 
> doxygen_1.8.20-3.debian.tar.xz
>  0121f8e423a79144f9d3ad1430669f9b428c1e4a495730e1710603634270129a 12896 
> doxygen_1.8.20-3_source.buildinfo
> Files:
>  cccfc97a44f24bc2efdb72c3eb13535f 2728 devel optional doxygen_1.8.20-3.dsc
>  56a5249e498566c753f411fb5b86a23e 29688 devel optional 
> doxygen_1.8.20-3.debian.tar.xz
>  a9014cdf9402e5ce91daf5363708d481 12896 devel optional 
> doxygen_1.8.20-3_source.buildinfo
> 
> -BEGIN PGP SIGNATURE-
> 
> iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAl92ScIACgkQ808JdE6f
> XdnCCw//fhVtRxt4M+JSrsRtezfevwSaW9gMfZKXQXRADNgZzGjxc8OGLn02tahT

Bug#969141: websocketpp: errors while generating documentation & FTBFS with doxygen 1.8.19

[Gianfranco Costamagna]

control: tags -1 pending

Since it is collaborative maintained, I just uploaded and committed the patch 
on git

thanks!

G.

Bug#969141: websocketpp: errors while generating documentation & FTBFS with doxygen 1.8.19

[Gianfranco Costamagna]

control: tags -1 patch

Ciao Paolo,

the issue looks already solved upstream with this commit
https://github.com/doxygen/doxygen/commit/d067baf495d0415283ce724ad32cb9a08dc17c83

G.

On Wed, 30 Sep 2020 11:35:35 +0200 Gianfranco Costamagna 
 wrote:
> control: reassign -1 doxygen
> control: severity -1 serious
> control: forwarded -1 https://github.com/doxygen/doxygen/issues/8066
> control: found -1 1.8.19-1
> 
> 
> Reassigning back after opening an upstream bug.
> 
> G.
> 
> On Fri, 28 Aug 2020 09:18:08 +0200 Paolo Greppi  
> wrote:
> > Source: websocketpp
> > Severity: normal
> > 
> > Dear Maintainer,
> > 
> > while rebuilding the build dependencies of doxygen with the upcoming 
> > doxygen 1.8.19 
> > (https://salsa.debian.org/debian/doxygen/-/wikis/ratt_doxygen_1.8.19-1_amd64-partial)
> >  this package FTBFS.
> > 
> > I attach the buildlogs:
> > - buildlogs/websocketpp_0.8.2-1 (with doxygen 1.8.19)
> > - buildlogs_recheck/websocketpp_0.8.2-1 (with doxygen 1.8.18)
> > 
> > In both buildlogs doxygen reports:
> > 
> > error: fixed-compilation-database: Error while opening fixed database: No 
> > such file or directory
> > json-compilation-database: Error while opening JSON database: No such file 
> > or directory
> >  using clang compilation database path of: "(null)"
> > error: /usr/include/wchar.h:35:10: fatal error: 'stddef.h' file not found 
> > [clang]
> > error: /usr/include/sched.h:29:10: fatal error: 'stddef.h' file not found 
> > [clang]
> > 
> > This then causes a segmentation fault with 1.8.19.
> > 
> > Also doxygen is parsing the files readme.md, changelog.md and roadmap.md 
> > which is incorrect.
> > You should fix the Doxyfile INPUT key and remove them (doxygen should only 
> > parse source code).
> > 
> > The segmentation fault may well be a doxygen issue, but fixing the Doxyfile 
> > of websocketpp is the first step required to pinpoint the root issue.
> > 
> > Paolo
> > 
> > -- System Information:
> > Debian Release: bullseye/sid
> >   APT prefers unstable
> >   APT policy: (500, 'unstable'), (1, 'experimental')
> > Architecture: amd64 (x86_64)
> > 
> > Kernel: Linux 5.7.0-1-amd64 (SMP w/2 CPU threads)
> > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
> > LANGUAGE=en_US:en
> > Shell: /bin/sh linked to /bin/dash
> > Init: systemd (via /run/systemd/system)
> > LSM: AppArmor: enabled
> > 
> > 
> 
> 

Bug#970570: llvm-toolchain-11: autopkgtest failure: Should find 3 warnings

[Gianfranco Costamagna]

control: fixed -1 1:11.0.0~+rc4-1
control: close -1
G.
On Fri, 18 Sep 2020 22:07:28 +0200 Paul Gevers  wrote:
> Source: llvm-toolchain-11
> Version: 1:11.0.0~+rc2-5
> X-Debbugs-CC: debian...@lists.debian.org
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: fails-always
> 
> Dear maintainer(s),
> 
> You recently added a new package with an autopkgtest, great. However,
> the autopkgest fails. Currently this failure is blocking the migration
> to testing [1]. Can you please investigate the situation and fix it?
> 
> I copied some of the output at the bottom of this report.
> 
> More information about this bug and the reason for filing it can be found on
> https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
> 
> Paul
> 
> [1] https://qa.debian.org/excuses.php?package=llvm-toolchain-11
> 
> https://ci.debian.net/data/autopkgtest/testing/amd64/l/llvm-toolchain-11/6878994/log.gz
> 
> clang-$VERSION -cc1  -analyze -analyzer-constraints=range
> -analyzer-checker=core,debug.ExprInspection foo.c &> foo.log
> if ! grep -q "3 warnings generated." foo.log; then
> echo "Should find 3 warnings"
> exit 1
> fi
> Should find 3 warnings
> 

Bug#968681: [Pkg-javascript-devel] Bug#968681: nodejs: regresses in ppc64el ( node-create-hash, node-crypto-browserify, node-sha.js)

[Gianfranco Costamagna]

Hello,

On Wed, 19 Aug 2020 22:39:03 +0200 =?UTF-8?B?SsOpcsOpbXkgTGFs?= 
 wrote:
> Le mer. 19 août 2020 à 21:12, Gianfranco Costamagna <
> locutusofb...@debian.org> a écrit :
> 
> > Source: nodejs
> > Version: 12.18.2~dfsg-1
> > Severity: serious
> >
> > Hello, looks like node-create-hask, node-crypto-browserify, node-sha.js
> > have autopkgtests failures on ppc64el.
> >
> > there might be an upstream patch according to Ubuntu bug [1]  and v8
> > commits
> >
> >
> > https://ci.debian.net/data/autopkgtest/unstable/ppc64el/n/node-crypto-browserify/6740061/log.gz
> >
> >
> > https://ci.debian.net/data/autopkgtest/unstable/ppc64el/n/node-sha.js/6740057/log.gz
> >
> >
> > https://ci.debian.net/data/autopkgtest/unstable/ppc64el/n/node-create-hash/6738537/log.gz
> >
> >
> > the attached diff (based on upstream changes) might help in fixing the
> > failures.
> >
> > [1]
> > https://bugs.launchpad.net/ubuntu/+source/node-create-hash/+bug/1887144
> >
> > I just uploaded in Ubuntu, will see in 24h or so if the problem is fixed
> > or not.
> >
> 
> Thanks, i'll apply the patch later this week, then.
> 
> Jérémy


ping please?

G.

Bug#970910: [Pkg-javascript-devel] Bug#970910: node-rollup-plugin-babel: autopkgtest failures [PATCH]

[Gianfranco Costamagna]

Hello,

On Sat, 26 Sep 2020 08:41:38 + (UTC) Gianfranco Costamagna 
 wrote:
> Hello,
> 
> >debian/tests/autopkgtest-pkg-nodejs.conf contains
> >
> >  "extra_depends=mocha, node-tape, node-rollup-plugin-json (>= 4.1.0)"
> >
> >which should be enough for autodep8 ≥ 0.23. If you use autodep8 ≥ 0.23,
> >this bug should be reassigned to autodep8.
> 
> 
> interesting, I don't see autodep8 installed in both Debian and Ubuntu, but 
> maybe its outside the build log (of course)
> https://autopkgtest.ubuntu.com/packages/n/node-rollup-plugin-babel/groovy/amd64
> 
> Do you have any clue?
> 
> Gianfranco
> 
> 

I confirm it works on my machine after updating autodep8.

Thanks for the help!
I hope Ubuntu folks will update autodep8 soon too.
(for now I workarounded adding the 3 dependencies as build-deps)

G.

Bug#970910: [Pkg-javascript-devel] Bug#970910: node-rollup-plugin-babel: autopkgtest failures [PATCH]

[Gianfranco Costamagna]

Hello,

>debian/tests/autopkgtest-pkg-nodejs.conf contains
>
>  "extra_depends=mocha, node-tape, node-rollup-plugin-json (>= 4.1.0)"
>
>which should be enough for autodep8 ≥ 0.23. If you use autodep8 ≥ 0.23,
>this bug should be reassigned to autodep8.


interesting, I don't see autodep8 installed in both Debian and Ubuntu, but 
maybe its outside the build log (of course)
https://autopkgtest.ubuntu.com/packages/n/node-rollup-plugin-babel/groovy/amd64

Do you have any clue?

Gianfranco

Bug#970910: node-rollup-plugin-babel: autopkgtest failures [PATCH]

[Gianfranco Costamagna]

Hello,

> Adding node-tape to build-dependencies might fix the issue.
> 

please note, it might not fail because node-tape is added by some other rollup 
dependency, so its already installed.

But I think if a dependency is directly used by the tool, it should be declared 
explictly, we shouldn't rely
on something that is already available (specially because non essential)

G.

Bug#970910: node-rollup-plugin-babel: autopkgtest failures [PATCH]

[Gianfranco Costamagna]

Source: node-rollup-plugin-babel
Version: 5.2.1+~4.4.0-2
Severity: serious
tags: patch

Hello, looks like the autopkgtestsuite fails because of 
autopkgtest [08:35:49]: test pkg-js-autopkgtest: 
/usr/share/pkg-js-autopkgtest/runner
autopkgtest [08:35:49]: test pkg-js-autopkgtest: [---
Found debian/nodejs/main, package.json is packages/babel/package.json
Using packages/babel/package.json
Node module name is @rollup/plugin-babel
# Copy test files
Looking at /usr/lib/nodejs/@rollup/plugin-babel
Looking at /usr/lib/*/nodejs/@rollup/plugin-babel
Looking at /usr/share/nodejs/@rollup/plugin-babel
Found /usr/share/nodejs/@rollup/plugin-babel
Linking /usr/share/nodejs/@rollup/plugin-babel/dist
Linking /usr/share/nodejs/@rollup/plugin-babel/package.json
Linking /usr/share/nodejs/@rollup/plugin-babel/types
Launch debian/tests/pkg-js/test with sh -ex
+ cd packages/babel
+ tape test/as-input-plugin.js test/as-output-plugin.js
debian/tests/pkg-js/test: 2: tape: not found
autopkgtest [08:35:49]: test pkg-js-autopkgtest: ---]
autopkgtest [08:35:50]: test pkg-js-autopkgtest:  - - - - - - - - - - results - 
- - - - - - - - -


Adding node-tape to build-dependencies might fix the issue.

thanks for having a look,

G.

Bug#965007: pitivi: ships a copy of gstreamer libraries

[Gianfranco Costamagna]

On Wed, 23 Sep 2020 10:45:41 +0300 Sebastian =?ISO-8859-1?Q?Dr=F6ge?= 
 wrote:
> On Wed, 2020-09-23 at 09:36 +0200, Gianfranco Costamagna wrote:
> > 
> > Hello, I found that pitivi was using the gst-transcoder only if not found 
> > on the system,
> > and upstream commit "51ae6533ee26ffd47e453eb5f5ad8cd46f57d15e" worked in 
> > fixing that.
> > 
> > I prepared a version on Debomatic with that change, and it stopped 
> > installing the binary/pkgconfig/libraries.
> > 
> > http://debomatic-amd64.debian.net/distribution#unstable/pitivi/0.999-3/buildlog
> > 
> > 
> > I would like to upload to sid, but unfortunately gst-plugins-bad1.0 
> > conflicts with pitivi << 0., so it won't fix the uninstallability...
> > 
> > Sebastian, how do you feel about relaxing that one?
> > 
> > I'm attaching a diff here (I'll change also VCS fields, and fix some 
> > lintian sandess here and there)
> 
> Thanks for the diff. Upstream is planning to do a release any day now,
> so I'd prefer waiting for that instead but if you have any other
> changes to the packaging I'd be happy to integrate them :)
> 
> You can also send them as MR to
>   https://salsa.debian.org/gstreamer-team/pitivi
> 
> 
> 

Here we are!
https://salsa.debian.org/gstreamer-team/pitivi/-/merge_requests/3

G.

Bug#965007: pitivi: ships a copy of gstreamer libraries

[Gianfranco Costamagna]

On Mon, 17 Aug 2020 10:21:48 -0300 Antonio Terceiro  wrote:
> Control: reassign -1 pitivi
> Control: retitle -1 pitivi: ships a copy of gstreamer libraries
> Control: found -1 0.999-2
> 
> On Mon, Aug 17, 2020 at 03:27:21PM +0300, Sebastian Dröge wrote:
> > On Mon, 2020-08-17 at 09:10 -0300, Antonio Terceiro wrote:
> > > 
> > > This file is already present in pitivi on stable, and
> > > gstreamer1.0-plugins-bad-apps is only present in experimental.  testing
> > > and unstable are unaffected by this, or testing would be unaffected if
> > > this hadn't caused pitivi to be removed.
> > > 
> > > I'm reassigning to gstreamer1.0-plugins-bad-apps.
> > 
> > It's a bug in pitivi. It should've never shipped these files outside
> > its private library directory.
> > 
> > It will be fixed once there's a new pitivi release, which I'm waiting
> > for currently. Please reassign this back to pitivi, thanks.
> 
> That's a funny way of seeing it, but it's your call.
> 
> Thanks for you work.


Hello, I found that pitivi was using the gst-transcoder only if not found on 
the system,
and upstream commit "51ae6533ee26ffd47e453eb5f5ad8cd46f57d15e" worked in fixing 
that.

I prepared a version on Debomatic with that change, and it stopped installing 
the binary/pkgconfig/libraries.

http://debomatic-amd64.debian.net/distribution#unstable/pitivi/0.999-3/buildlog

I would like to upload to sid, but unfortunately gst-plugins-bad1.0 conflicts 
with pitivi << 0., so it won't fix the uninstallability...

Sebastian, how do you feel about relaxing that one?

I'm attaching a diff here (I'll change also VCS fields, and fix some lintian 
sandess here and there)

G.
diff -Nru pitivi-0.999/debian/changelog pitivi-0.999/debian/changelog
--- pitivi-0.999/debian/changelog   2020-02-21 18:59:53.0 +0100
+++ pitivi-0.999/debian/changelog   2020-09-23 09:00:44.0 +0200
@@ -1,3 +1,12 @@
+pitivi (0.999-3) unstable; urgency=medium
+
+  * No change rebuild against new gstreamer 1.18 (so transcoder embedded
+dependency doesn't get built anymore) Closes: #965007
+- cherry-pick and rebase upstream commit 
51ae6533ee26ffd47e453eb5f5ad8cd46f57d15e
+- add new build and runtime dependency on gstreamer1.0-plugins-bad-apps
+
+ -- Gianfranco Costamagna   Wed, 23 Sep 2020 
09:00:44 +0200
+
 pitivi (0.999-2) unstable; urgency=medium
 
   [ Gianfranco Costamagna ]
diff -Nru pitivi-0.999/debian/control pitivi-0.999/debian/control
--- pitivi-0.999/debian/control 2020-02-07 19:00:40.0 +0100
+++ pitivi-0.999/debian/control 2020-09-23 09:00:44.0 +0200
@@ -17,6 +17,7 @@
 libgtk-3-dev (>= 3.20),
 libgstreamer1.0-dev (>= 1.14.2),
 libgstreamer-plugins-base1.0-dev (>= 1.14.2),
+gstreamer1.0-plugins-bad-apps,
 libgirepository1.0-dev,
 python3-cairo-dev
 X-Python-Version: >= 3.3
@@ -48,6 +49,7 @@
 gstreamer1.0-plugins-base (>= 1.14.2),
 gstreamer1.0-plugins-good (>= 1.14.2),
 gstreamer1.0-plugins-bad (>= 1.14.2),
+gstreamer1.0-plugins-bad-apps,
 gstreamer1.0-pulseaudio | gstreamer1.0-audiosink,
 gstreamer1.0-gtk3,
 gstreamer1.0-x | gstreamer1.0-videosink
diff -Nru 
pitivi-0.999/debian/patches/0a3cc054a2c20b59f5a307de3c9af3c0d270.patch 
pitivi-0.999/debian/patches/0a3cc054a2c20b59f5a307de3c9af3c0d270.patch
--- pitivi-0.999/debian/patches/0a3cc054a2c20b59f5a307de3c9af3c0d270.patch  
2020-02-21 18:59:53.0 +0100
+++ pitivi-0.999/debian/patches/0a3cc054a2c20b59f5a307de3c9af3c0d270.patch  
2020-09-23 09:00:44.0 +0200
@@ -1,6 +1,3 @@
-## Description: add some description
-## Origin/Author: add some origin or author
-## Bug: bug URL
 From 0a3cc054a2c20b59f5a307de3c9af3c0d270 Mon Sep 17 00:00:00 2001
 From: =?UTF-8?q?Alexandru=20B=C4=83lu=C8=9B?= 
 Date: Tue, 28 Jan 2020 22:34:40 +0100
diff -Nru 
pitivi-0.999/debian/patches/51ae6533ee26ffd47e453eb5f5ad8cd46f57d15e.patch 
pitivi-0.999/debian/patches/51ae6533ee26ffd47e453eb5f5ad8cd46f57d15e.patch
--- pitivi-0.999/debian/patches/51ae6533ee26ffd47e453eb5f5ad8cd46f57d15e.patch  
1970-01-01 01:00:00.0 +0100
+++ pitivi-0.999/debian/patches/51ae6533ee26ffd47e453eb5f5ad8cd46f57d15e.patch  
2020-09-23 09:00:44.0 +0200
@@ -0,0 +1,89 @@
+From 51ae6533ee26ffd47e453eb5f5ad8cd46f57d15e Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Alexandru=20B=C4=83lu=C8=9B?= 
+Date: Fri, 4 Oct 2019 02:07:22 +0200
+Subject: [PATCH] Complete switching to gst-transcoder in gst-plugins-bad
+
+---
+ build/flatpak/gst-transcoder-configure | 30 --
+ meson.build|  4 
+ tests/__init__.py  |  6 +-
+ 3 files changed, 1 insertion(+), 39 deletions(-)
+ delete mode 100755 build/flatpak/gst-transcoder-configure
+
+diff --git a

Bug#970726: patch uploaded in deferred/7

[Gianfranco Costamagna]

control: tags -1 patch pending

The following debdiff has been uploaded in deferred/7, feel free to 
reschedule/cancel it

diff -Nru rpi.gpio-0.7.0/debian/changelog rpi.gpio-0.7.0/debian/changelog
--- rpi.gpio-0.7.0/debian/changelog 2020-01-16 17:20:40.0 +0100
+++ rpi.gpio-0.7.0/debian/changelog 2020-09-22 18:16:04.0 +0200
@@ -1,3 +1,13 @@
+rpi.gpio (0.7.0-0.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Grab workaround from meta-raspberrypi to add fcommon and fix gcc-10 build
+failure (Closes: #970726)
+  * Fix README.txt installation, by fixing typo in debian/rpio.gpio-common.docs
+(Closes: #970728) (patch from Ubuntu Dave Jones )
+
+ -- Gianfranco Costamagna   Tue, 22 Sep 2020 
18:16:04 +0200
+
 rpi.gpio (0.7.0-0.1) unstable; urgency=medium

   * Non-maintainer upload.
diff -Nru rpi.gpio-0.7.0/debian/rpi.gpio-common.docs 
rpi.gpio-0.7.0/debian/rpi.gpio-common.docs
--- rpi.gpio-0.7.0/debian/rpi.gpio-common.docs  1970-01-01 01:00:00.0 
+0100
+++ rpi.gpio-0.7.0/debian/rpi.gpio-common.docs  2020-09-22 18:16:02.0 
+0200
@@ -0,0 +1 @@
+README.txt
diff -Nru rpi.gpio-0.7.0/debian/rpio.gpio-common.docs 
rpi.gpio-0.7.0/debian/rpio.gpio-common.docs
--- rpi.gpio-0.7.0/debian/rpio.gpio-common.docs 2018-06-12 14:22:46.0 
+0200
+++ rpi.gpio-0.7.0/debian/rpio.gpio-common.docs 1970-01-01 01:00:00.0 
+0100
@@ -1 +0,0 @@
-README.txt
diff -Nru rpi.gpio-0.7.0/debian/rules rpi.gpio-0.7.0/debian/rules
--- rpi.gpio-0.7.0/debian/rules 2020-01-16 17:20:40.0 +0100
+++ rpi.gpio-0.7.0/debian/rules 2020-09-22 18:16:02.0 +0200
@@ -7,7 +7,7 @@

 export DEB_BUILD_MAINT_OPTIONS = hardening=+all

-DEB_CFLAGS_MAINT_APPEND += $(shell getconf LFS_CFLAGS)
+DEB_CFLAGS_MAINT_APPEND += $(shell getconf LFS_CFLAGS) -fcommon
 DEB_LDFLAGS_MAINT_APPEND += $(shell getconf LFS_LDFLAGS)
 DEB_LDFLAGS_MAINT_APPEND += -Wl,--as-needed
 export DEB_CFLAGS_MAINT_APPEND DEB_LDFLAGS_MAINT_APPEND


diff -Nru rpi.gpio-0.7.0/debian/changelog rpi.gpio-0.7.0/debian/changelog
--- rpi.gpio-0.7.0/debian/changelog 2020-01-16 17:20:40.0 +0100
+++ rpi.gpio-0.7.0/debian/changelog 2020-09-22 18:16:04.0 +0200
@@ -1,3 +1,13 @@
+rpi.gpio (0.7.0-0.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Grab workaround from meta-raspberrypi to add fcommon and fix gcc-10 build
+failure (Closes: #970726)
+  * Fix README.txt installation, by fixing typo in debian/rpio.gpio-common.docs
+(Closes: #970728) (patch from Ubuntu Dave Jones )
+
+ -- Gianfranco Costamagna   Tue, 22 Sep 2020 
18:16:04 +0200
+
 rpi.gpio (0.7.0-0.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru rpi.gpio-0.7.0/debian/rpi.gpio-common.docs 
rpi.gpio-0.7.0/debian/rpi.gpio-common.docs
--- rpi.gpio-0.7.0/debian/rpi.gpio-common.docs  1970-01-01 01:00:00.0 
+0100
+++ rpi.gpio-0.7.0/debian/rpi.gpio-common.docs  2020-09-22 18:16:02.0 
+0200
@@ -0,0 +1 @@
+README.txt
diff -Nru rpi.gpio-0.7.0/debian/rpio.gpio-common.docs 
rpi.gpio-0.7.0/debian/rpio.gpio-common.docs
--- rpi.gpio-0.7.0/debian/rpio.gpio-common.docs 2018-06-12 14:22:46.0 
+0200
+++ rpi.gpio-0.7.0/debian/rpio.gpio-common.docs 1970-01-01 01:00:00.0 
+0100
@@ -1 +0,0 @@
-README.txt
diff -Nru rpi.gpio-0.7.0/debian/rules rpi.gpio-0.7.0/debian/rules
--- rpi.gpio-0.7.0/debian/rules 2020-01-16 17:20:40.0 +0100
+++ rpi.gpio-0.7.0/debian/rules 2020-09-22 18:16:02.0 +0200
@@ -7,7 +7,7 @@
 
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 
-DEB_CFLAGS_MAINT_APPEND += $(shell getconf LFS_CFLAGS)
+DEB_CFLAGS_MAINT_APPEND += $(shell getconf LFS_CFLAGS) -fcommon
 DEB_LDFLAGS_MAINT_APPEND += $(shell getconf LFS_LDFLAGS)
 DEB_LDFLAGS_MAINT_APPEND += -Wl,--as-needed
 export DEB_CFLAGS_MAINT_APPEND DEB_LDFLAGS_MAINT_APPEND

Bug#970726: rpi.gpio: FTBFS in sid (gcc-10)

[Gianfranco Costamagna]

control: tags -1 patch


This works...

--- rpi.gpio-0.7.0/debian/rules 2020-01-16 17:20:40.0 +0100
+++ rpi.gpio-0.7.0/debian/rules 2020-09-22 18:03:46.0 +0200
@@ -7,7 +7,7 @@
 
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all
 
-DEB_CFLAGS_MAINT_APPEND += $(shell getconf LFS_CFLAGS)
+DEB_CFLAGS_MAINT_APPEND += $(shell getconf LFS_CFLAGS) -fcommon
 DEB_LDFLAGS_MAINT_APPEND += $(shell getconf LFS_LDFLAGS)
 DEB_LDFLAGS_MAINT_APPEND += -Wl,--as-needed
 export DEB_CFLAGS_MAINT_APPEND DEB_LDFLAGS_MAINT_APPEND


G.

On Tue, 22 Sep 2020 17:58:36 +0200 Gianfranco Costamagna 
 wrote:
> Source: rpi.gpio
> Version: 0.7.0-0.1
> Severity: serious
> 
> Hello, looks like gcc-10 broke the rpi-gpio build (obviously only on arm*).
> 
> 
> people from meta-raspberrypi workarounded with the fcommon flag...
> # ignore issues with -fno-common from gcc-10 until it's fixed in upstream:
> # https://sourceforge.net/p/raspberry-gpio-python/tickets/187/
> CFLAGS += "-fcommon"
> 
> 
> aarch64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g 
> -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat 
> -Werror=format-security -g -fwrapv -O2 -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
> -I/usr/include/python3.8 -c source/soft_pwm.c -o 
> build/temp.linux-arm64-3.8/source/soft_pwm.o
> aarch64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g 
> -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat 
> -Werror=format-security -g -fwrapv -O2 -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
> -I/usr/include/python3.8 -c source/py_pwm.c -o 
> build/temp.linux-arm64-3.8/source/py_pwm.o
> aarch64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g 
> -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat 
> -Werror=format-security -g -fwrapv -O2 -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
> -I/usr/include/python3.8 -c source/common.c -o 
> build/temp.linux-arm64-3.8/source/common.o
> aarch64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g 
> -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat 
> -Werror=format-security -g -fwrapv -O2 -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
> -I/usr/include/python3.8 -c source/constants.c -o 
> build/temp.linux-arm64-3.8/source/constants.o
> aarch64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions 
> -Wl,-Bsymbolic-functions -Wl,-z,relro -g -fwrapv -O2 -Wl,-Bsymbolic-functions 
> -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
> build/temp.linux-arm64-3.8/source/py_gpio.o 
> build/temp.linux-arm64-3.8/source/c_gpio.o 
> build/temp.linux-arm64-3.8/source/cpuinfo.o 
> build/temp.linux-arm64-3.8/source/event_gpio.o 
> build/temp.linux-arm64-3.8/source/soft_pwm.o 
> build/temp.linux-arm64-3.8/source/py_pwm.o 
> build/temp.linux-arm64-3.8/source/common.o 
> build/temp.linux-arm64-3.8/source/constants.o -o 
> /<>/.pybuild/cpython3_3.8_rpi.gpio/build/RPi/_GPIO.cpython-38-aarch64-linux-gnu.so
> /usr/bin/ld: 
> build/temp.linux-arm64-3.8/source/soft_pwm.o:./source/soft_pwm.c:28: multiple 
> definition of `threads'; 
> build/temp.linux-arm64-3.8/source/event_gpio.o:./source/event_gpio.c:60: 
> first defined here
> /usr/bin/ld: build/temp.linux-arm64-3.8/source/py_pwm.o:./source/common.h:38: 
> multiple definition of `gpio_direction'; 
> build/temp.linux-arm64-3.8/source/py_gpio.o:./source/common.h:38: first 
> defined here
> /usr/bin/ld: build/temp.linux-arm64-3.8/source/py_pwm.o:./source/py_pwm.h:23: 
> multiple definition of `PWMType'; 
> build/temp.linux-arm64-3.8/source/py_gpio.o:./source/py_pwm.h:23: first 
> defined here
> /usr/bin/ld: build/temp.linux-arm64-3.8/source/py_pwm.o:./source/common.h:41: 
> multiple definition of `module_setup'; 
> build/temp.linux-arm64-3.8/source/py_gpio.o:./source/common.h:41: first 
> defined here
> /usr/bin/ld: build/temp.linux-arm64-3.8/source/py_pwm.o:./source/common.h:40: 
> multiple definition of `setup_error'; 
> build/temp.linux-arm64-3.8/source/py_gpio.o:./source/common.h:40: first 
> defined here
> /usr/bin/ld: build/temp.linux-arm64-3.8/source/py_pwm.o:./source/common.h:39: 
> multiple definition of `rpiinfo'; 
> build/temp.linux-arm64-3.8/source/py_gpio.o:./source/common.h:39: first 
> defined here
>

Bug#970726: rpi.gpio: FTBFS in sid (gcc-10)

[Gianfranco Costamagna]

Source: rpi.gpio
Version: 0.7.0-0.1
Severity: serious

Hello, looks like gcc-10 broke the rpi-gpio build (obviously only on arm*).


people from meta-raspberrypi workarounded with the fcommon flag...
# ignore issues with -fno-common from gcc-10 until it's fixed in upstream:
# https://sourceforge.net/p/raspberry-gpio-python/tickets/187/
CFLAGS += "-fcommon"


aarch64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g 
-fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security 
-g -fwrapv -O2 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.8 -c source/soft_pwm.c -o 
build/temp.linux-arm64-3.8/source/soft_pwm.o
aarch64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g 
-fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security 
-g -fwrapv -O2 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.8 -c source/py_pwm.c -o 
build/temp.linux-arm64-3.8/source/py_pwm.o
aarch64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g 
-fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security 
-g -fwrapv -O2 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.8 -c source/common.c -o 
build/temp.linux-arm64-3.8/source/common.o
aarch64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g 
-fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security 
-g -fwrapv -O2 -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.8 -c source/constants.c -o 
build/temp.linux-arm64-3.8/source/constants.o
aarch64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions 
-Wl,-Bsymbolic-functions -Wl,-z,relro -g -fwrapv -O2 -Wl,-Bsymbolic-functions 
-Wl,-z,relro -Wl,-z,now -Wl,--as-needed -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
build/temp.linux-arm64-3.8/source/py_gpio.o 
build/temp.linux-arm64-3.8/source/c_gpio.o 
build/temp.linux-arm64-3.8/source/cpuinfo.o 
build/temp.linux-arm64-3.8/source/event_gpio.o 
build/temp.linux-arm64-3.8/source/soft_pwm.o 
build/temp.linux-arm64-3.8/source/py_pwm.o 
build/temp.linux-arm64-3.8/source/common.o 
build/temp.linux-arm64-3.8/source/constants.o -o 
/<>/.pybuild/cpython3_3.8_rpi.gpio/build/RPi/_GPIO.cpython-38-aarch64-linux-gnu.so
/usr/bin/ld: 
build/temp.linux-arm64-3.8/source/soft_pwm.o:./source/soft_pwm.c:28: multiple 
definition of `threads'; 
build/temp.linux-arm64-3.8/source/event_gpio.o:./source/event_gpio.c:60: first 
defined here
/usr/bin/ld: build/temp.linux-arm64-3.8/source/py_pwm.o:./source/common.h:38: 
multiple definition of `gpio_direction'; 
build/temp.linux-arm64-3.8/source/py_gpio.o:./source/common.h:38: first defined 
here
/usr/bin/ld: build/temp.linux-arm64-3.8/source/py_pwm.o:./source/py_pwm.h:23: 
multiple definition of `PWMType'; 
build/temp.linux-arm64-3.8/source/py_gpio.o:./source/py_pwm.h:23: first defined 
here
/usr/bin/ld: build/temp.linux-arm64-3.8/source/py_pwm.o:./source/common.h:41: 
multiple definition of `module_setup'; 
build/temp.linux-arm64-3.8/source/py_gpio.o:./source/common.h:41: first defined 
here
/usr/bin/ld: build/temp.linux-arm64-3.8/source/py_pwm.o:./source/common.h:40: 
multiple definition of `setup_error'; 
build/temp.linux-arm64-3.8/source/py_gpio.o:./source/common.h:40: first defined 
here
/usr/bin/ld: build/temp.linux-arm64-3.8/source/py_pwm.o:./source/common.h:39: 
multiple definition of `rpiinfo'; 
build/temp.linux-arm64-3.8/source/py_gpio.o:./source/common.h:39: first defined 
here
/usr/bin/ld: build/temp.linux-arm64-3.8/source/py_pwm.o:./source/common.h:37: 
multiple definition of `pin_to_gpio'; 
build/temp.linux-arm64-3.8/source/py_gpio.o:./source/common.h:37: first defined 
here
/usr/bin/ld: build/temp.linux-arm64-3.8/source/py_pwm.o:./source/common.h:36: 
multiple definition of `pin_to_gpio_rev3'; 
build/temp.linux-arm64-3.8/source/py_gpio.o:./source/common.h:36: first defined 
here
/usr/bin/ld: build/temp.linux-arm64-3.8/source/py_pwm.o:./source/common.h:35: 
multiple definition of `pin_to_gpio_rev2'; 
build/temp.linux-arm64-3.8/source/py_gpio.o:./source/common.h:35: first defined 
here
/usr/bin/ld: build/temp.linux-arm64-3.8/source/py_pwm.o:./source/common.h:34: 
multiple definition of `pin_to_gpio_rev1'; 
build/temp.linux-arm64-3.8/source/py_gpio.o:./source/common.h:34: first defined 
here
/usr/bin/ld: build/temp.linux-arm64-3.8/source/py_pwm.o:./source/common.h:33: 
multiple definition of `gpio_mode'; 
build/temp.linux-arm64-3.8/source/py_gpio.o:./source/common.h:33: first defined 
here
/usr/bin/ld: 

Bug#970453: coq-float: FTBFS in sid

[Gianfranco Costamagna]

Source: coq-float
Version: 1:8.10.0-1
Severity: serious

Hello, this is the build log (attached)

make[1]: Leaving directory '/<>'
   dh_clean
 dpkg-source -Zxz -b .
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building coq-float using existing 
./coq-float_8.10.0.orig.tar.gz
dpkg-source: info: building coq-float in coq-float_8.10.0-1.debian.tar.xz
dpkg-source: info: building coq-float in coq-float_8.10.0-1.dsc
 debian/rules binary
dh binary
   dh_update_autotools_config
   dh_autoreconf
   dh_auto_configure
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
/usr/bin/make all
make[2]: Entering directory '/<>'
coq_makefile -f Make -o Makefile.coq
make -f Makefile.coq Makefile
make[3]: Entering directory '/<>'
COQDEP VFILES
make[3]: Nothing to be done for 'Makefile'.
make[3]: Leaving directory '/<>'
make -f Makefile.coq all
make[3]: Entering directory '/<>'
COQC sTactic.v
COQC Faux.v
File "./Faux.v", line 640, characters 0-63:
Error: No such goal.

make[4]: *** [Makefile.coq:716: Faux.vo] Error 1
make[3]: *** [Makefile.coq:339: all] Error 2
make[3]: Leaving directory '/<>'
make[2]: *** [Makefile:2: all] Error 2
make[2]: Leaving directory '/<>'
make[1]: *** [debian/rules:17: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:10: binary] Error 2
dpkg-buildpackage-debomatic-original: error: debian/rules binary subprocess 
returned exit status 2



G.

sbuild (Debian sbuild) 0.78.1 (09 February 2019) on misc-debomatic1

+==+
| coq-float 1:8.10.0-1 (amd64) Wed, 16 Sep 2020 09:46:45 + |
+==+

Package: coq-float
Version: 1:8.10.0-1
Source Version: 1:8.10.0-1
Distribution: unstable
Machine Architecture: amd64
Host Architecture: amd64
Build Architecture: amd64
Build Type: full

I: NOTICE: Log filtering will replace 
'var/run/schroot/mount/unstable-amd64-debomatic-0194c9e2-9684-4720-b99d-4f9e1b12cdfe'
 with '<>'

+--+
| Chroot Setup Commands|
+--+


/home/debomatic/debomatic/sbuildcommands/chroot-setup-commands/apt-speedup 
coq-float_8.10.0-1 unstable amd64



I: Finished running 
'/home/debomatic/debomatic/sbuildcommands/chroot-setup-commands/apt-speedup 
coq-float_8.10.0-1 unstable amd64'.

Finished processing commands.

I: NOTICE: Log filtering will replace 'build/coq-float-RLWwzM/resolver-lS5yzA' 
with '<>'

+--+
| Update chroot|
+--+

Get:1 http://ftp.debian.org/debian unstable InRelease [146 kB]
Get:2 http://ftp.debian.org/debian unstable/main amd64 Packages [11.4 MB]
Fetched 11.5 MB in 1s (10.9 MB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
The following packages will be upgraded:
  cpp-10 dmidecode gcc-10-base libelf1 libgcc-s1 libgnutls30 libstdc++6
7 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 10.2 MB of archives.
After this operation, 7168 B of additional disk space will be used.
Get:1 http://ftp.debian.org/debian unstable/main amd64 cpp-10 amd64 10.2.0-8 
[8003 kB]
Get:2 http://ftp.debian.org/debian unstable/main amd64 gcc-10-base amd64 
10.2.0-8 [199 kB]
Get:3 http://ftp.debian.org/debian unstable/main amd64 libstdc++6 amd64 
10.2.0-8 [492 kB]
Get:4 http://ftp.debian.org/debian unstable/main amd64 libgcc-s1 amd64 10.2.0-8 
[41.4 kB]
Get:5 http://ftp.debian.org/debian unstable/main amd64 libgnutls30 amd64 
3.6.15-3 [1189 kB]
Get:6 http://ftp.debian.org/debian unstable/main amd64 dmidecode amd64 3.2-4 
[63.4 kB]
Get:7 http://ftp.debian.org/debian unstable/main amd64 libelf1 amd64 0.181-1 
[164 kB]
Fetched 10.2 MB in 0s (36.3 MB/s)
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 

Bug#970036: libopenmpi-dev fails to install

[Gianfranco Costamagna]

control: tags -1 patch

On Thu, 10 Sep 2020 21:05:09 +0300 Adrian Bunk  wrote:
> Package: libopenmpi-dev
> Version: 4.0.5-2
> Severity: grave
> Tags: ftbfs
> Control: affects -1 src:scotch src:starpu
> 
> ...
> Setting up libopenmpi-dev:amd64 (4.0.5-2) ...
> update-alternatives: error: alternative path 
> /usr/lib/$[DEB_HOST_MULTIARCH}/openmpi/include doesn't exist
> dpkg: error processing package libopenmpi-dev:amd64 (--configure):
> 
> 

grep DEB_HOST_MULTIARCH . -R |grep "\["
./debian/libopenmpi-dev.postinst:   --install 
/usr/include/$[DEB_HOST_MULTIARCH}/mpi mpi-$[DEB_HOST_MULTIARCH} 
/usr/lib/$[DEB_HOST_MULTIARCH}/openmpi/include 50 \
./debian/libopenmpi-dev.postinst:   --slave 
/usr/lib/$[DEB_HOST_MULTIARCH}/libmpi.so libmpi.so-$[DEB_HOST_MULTIARCH} 
/usr/lib/$[DEB_HOST_MULTIARCH}/openmpi/lib/libmpi.so \
./debian/libopenmpi-dev.postinst:   --slave 
/usr/lib/$[DEB_HOST_MULTIARCH}/libmpi++.so libmpi++.so-$[DEB_HOST_MULTIARCH} 
/usr/lib/$[DEB_HOST_MULTIARCH}/openmpi/lib/libmpi_cxx.so \
./debian/libopenmpi-dev.postinst:   --slave 
/usr/lib/$[DEB_HOST_MULTIARCH}/pkgconfig/mpi.pc mpi.pc-$[DEB_HOST_MULTIARCH} 
/usr/lib/$[DEB_HOST_MULTIARCH}/pkgconfig/ompi.pc \
./debian/libopenmpi-dev.postinst:   --slave 
/usr/lib/$[DEB_HOST_MULTIARCH}/pkgconfig/mpi-fort.pc 
mpi-fort.pc-$[DEB_HOST_MULTIARCH} 
/usr/lib/$[DEB_HOST_MULTIARCH}/pkgconfig/ompi-fort.pc \
./debian/libopenmpi-dev.postinst:   --slave 
/usr/lib/$[DEB_HOST_MULTIARCH}/pkgconfig/mpi-c.pc 
mpi-c.pc-$[DEB_HOST_MULTIARCH} 
/usr/lib/$[DEB_HOST_MULTIARCH}/pkgconfig/ompi-c.pc \
./debian/libopenmpi-dev.postinst:   --slave 
/usr/lib/$[DEB_HOST_MULTIARCH}/pkgconfig/mpi-cxx.pc 
mpi-cxx.pc-$[DEB_HOST_MULTIARCH} 
/usr/lib/$[DEB_HOST_MULTIARCH}/pkgconfig/ompi-cxx.pc


sed "s/\$\[DEB_HOST_MULTIARCH}/\${DEB_HOST_MULTIARCH}/g" -i 
./debian/libopenmpi-dev.postinst
*might* do the trick here :)

G.

Bug#963827: [virtualbox] guests limited to 800x600

[Gianfranco Costamagna]

Hello,


On Sat, 27 Jun 2020 23:25:26 +0100 Lyndon Brown  wrote:
> Package: src:virtualbox
> Version: 6.1.10-dfsg-1
> Severity: important
> 
> After installing a handful of updates in a Sid guest and rebooting it,
> it's now stuck with an unusable display area of 800x600.
> 

should be fixed now

G.

Bug#969753: diffoscope: autopkgtest failures

[Gianfranco Costamagna]

Hello,

another additional diff:

--- diffoscope-159ubuntu1/tests/comparators/test_directory.py   2020-09-04 
12:12:52.0 +0200
+++ diffoscope-159ubuntu2/tests/comparators/test_directory.py   2020-09-07 
20:46:23.0 +0200
@@ -33,6 +33,7 @@
 TEST_FILE2_PATH = data("text_ascii2")
 
 
+@skip_unless_tools_exist("pgpdump")
 def test_no_differences():
 difference = compare_directories(
 os.path.dirname(__file__), os.path.dirname(__file__)
@@ -40,6 +41,7 @@
 assert difference is None
 
 
+@skip_unless_tools_exist("pgpdump")
 def test_no_differences_with_extra_slash():
 difference = compare_directories(
 os.path.dirname(__file__) + "/", os.path.dirname(__file__)
diff -Nru diffoscope-159ubuntu1/tests/comparators/test_rlib.py 
diffoscope-159ubuntu2/tests/comparators/test_rlib.py
--- diffoscope-159ubuntu1/tests/comparators/test_rlib.py2020-09-07 
20:46:23.0 +0200
+++ diffoscope-159ubuntu2/tests/comparators/test_rlib.py2020-09-07 
20:46:23.0 +0200
@@ -51,6 +51,7 @@
 assert isinstance(rlib1, ArFile)
 
 
+@skip_unless_tools_exist("pgpdump")
 def test_no_differences(rlib1):
 difference = rlib1.compare(rlib1)
 assert difference is None
@@ -121,6 +122,6 @@
 )
 
 
-@skip_unless_tools_exist("nm")
+@skip_unless_tools_exist("nm", "pgpdump")
 def test_compare_non_existing(monkeypatch, rlib1):
 assert_non_existing(monkeypatch, rlib1)


On Mon, 7 Sep 2020 20:53:13 +0200 Gianfranco Costamagna 
 wrote:
> Source: diffoscope
> Version: 159
> Severity: serious
> 
> Hello, autopkgtests looks sad, pytest-with-recommends works, while pytest 
> doesn't, because of missing pgpdump
> 
> I did add some @skip_unless_tools_exist("pgpdump") around the failing tests 
> (attached the diff), however I don't know
> if this is the right solution, or something better has to be implemented.
> 
> G.

Bug#969753: diffoscope: autopkgtest failures

[Gianfranco Costamagna]

Source: diffoscope
Version: 159
Severity: serious

Hello, autopkgtests looks sad, pytest-with-recommends works, while pytest 
doesn't, because of missing pgpdump

I did add some @skip_unless_tools_exist("pgpdump") around the failing tests 
(attached the diff), however I don't know
if this is the right solution, or something better has to be implemented.

G.
diff -Nru diffoscope-158/debian/changelog diffoscope-158ubuntu1/debian/changelog
--- diffoscope-158/debian/changelog 2020-08-28 12:53:10.0 +0200
+++ diffoscope-158ubuntu1/debian/changelog  2020-09-07 20:46:23.0 
+0200
@@ -1,3 +1,9 @@
+diffoscope (159ubuntu1) groovy; urgency=medium
+
+  * Skip some tests if pgpdump is not installed
+
+ -- Gianfranco Costamagna   Mon, 07 Sep 2020 
20:46:23 +0200
+
 diffoscope (159) unstable; urgency=medium
 
   [ Chris Lamb ]
diff -Nru diffoscope-158/tests/comparators/test_binary.py 
diffoscope-158ubuntu1/tests/comparators/test_binary.py
--- diffoscope-158/tests/comparators/test_binary.py 2020-08-28 
12:53:10.0 +0200
+++ diffoscope-158ubuntu1/tests/comparators/test_binary.py  2020-09-07 
20:01:52.0 +0200
@@ -48,10 +48,12 @@
 binary2 = init_fixture(TEST_FILE2_PATH)
 
 
+@skip_unless_tools_exist("pgpdump")
 def test_same_content(binary1):
 assert binary1.has_same_content_as(binary1) is True
 
 
+@skip_unless_tools_exist("pgpdump")
 def test_not_same_content(binary1, binary2):
 assert binary1.has_same_content_as(binary2) is False
 
@@ -76,18 +78,20 @@
 assert File.guess_encoding(TEST_ISO8859_PATH) == "iso-8859-1"
 
 
-def test_no_differences_with_xxd(binary1):
+@skip_unless_tools_exist("pgpdump")
+def test_no_differences_with_xxd(binary1):
 difference = binary1.compare_bytes(binary1)
 assert difference is None
 
 
-@skip_unless_tools_exist("xxd")
+@skip_unless_tools_exist("xxd", "pgpdump")
 def test_compare_with_xxd(binary1, binary2):
 difference = binary1.compare_bytes(binary2)
 expected_diff = get_data("binary_expected_diff")
 assert normalize_zeros(difference.unified_diff) == expected_diff
 
 
+@skip_unless_tools_exist("pgpdump")
 def test_compare_non_existing_with_xxd(binary1):
 difference = binary1.compare_bytes(MissingFile("/nonexisting", binary1))
 assert difference.source2 == "/nonexisting"
@@ -101,11 +105,13 @@
 monkeypatch.setattr(Xxd, "cmdline", mock_cmdline)
 
 
+@skip_unless_tools_exist("pgpdump")
 def test_no_differences_without_xxd(xxd_not_found, binary1):
 difference = binary1.compare_bytes(binary1)
 assert difference is None
 
 
+@skip_unless_tools_exist("pgpdump")
 def test_compare_without_xxd(xxd_not_found, binary1, binary2):
 difference = binary1.compare(binary2)
 expected_diff = get_data("binary_hexdump_expected_diff")
diff -Nru diffoscope-158/tests/comparators/test_haskell.py 
diffoscope-158ubuntu1/tests/comparators/test_haskell.py
--- diffoscope-158/tests/comparators/test_haskell.py2020-08-28 
12:53:10.0 +0200
+++ diffoscope-158ubuntu1/tests/comparators/test_haskell.py 2020-09-07 
20:03:29.0 +0200
@@ -38,6 +38,7 @@
 assert isinstance(haskell1, HiFile)
 
 
+@skip_unless_tools_exist("pgpdump")
 def test_no_differences(haskell1):
 assert haskell1.compare(haskell1) is None
 
diff -Nru diffoscope-158/tests/comparators/test_pgp.py 
diffoscope-158ubuntu1/tests/comparators/test_pgp.py
--- diffoscope-158/tests/comparators/test_pgp.py2020-08-28 
12:53:10.0 +0200
+++ diffoscope-158ubuntu1/tests/comparators/test_pgp.py 2020-09-07 
20:43:15.0 +0200
@@ -70,6 +70,7 @@
 assert len(difference.details) == 1
 
 
+@skip_unless_tools_exist("pgpdump")
 def test_signed_identification(signed1):
 assert isinstance(signed1, PgpFile)
 
diff -Nru diffoscope-158/tests/comparators/test_ppu.py 
diffoscope-158ubuntu1/tests/comparators/test_ppu.py
--- diffoscope-158/tests/comparators/test_ppu.py2020-08-28 
12:53:10.0 +0200
+++ diffoscope-158ubuntu1/tests/comparators/test_ppu.py 2020-09-07 
20:44:53.0 +0200
@@ -51,6 +51,7 @@
 assert isinstance(file1, PpuFile)
 
 
+@skip_unless_tools_exist("pgpdump")
 def test_no_differences(file1):
 assert file1.compare(file1) is None
 
diff -Nru diffoscope-158/tests/comparators/test_rlib.py 
diffoscope-158ubuntu1/tests/comparators/test_rlib.py
--- diffoscope-158/tests/comparators/test_rlib.py   2020-08-28 
12:53:10.0 +0200
+++ diffoscope-158ubuntu1/tests/comparators/test_rlib.py2020-09-07 
20:46:22.0 +0200
@@ -80,12 +80,12 @@
 return get_data(diff_file)
 
 
-@skip_unless_tools_exist("nm")
+@skip_unless_tools_exist("nm", "pgpdump")
 def test_num_items(differences):
 assert len(differences) == 4
 
 
-@skip_unless_tools_exist("nm"

Bug#969570: ulfius: FTBFS on s390x

[Gianfranco Costamagna]

Source: ulfius
Version: 2.6.9-1
Severity: serious


Hello, your package FTBFS on s390x. Please have a look if possible

gmake[4]: Leaving directory '/<>/build'
gmake[3]: Leaving directory '/<>/build'
Start 1: core
1/4 Test #1: core .   Passed0.08 sec
Start 2: u_map
2/4 Test #2: u_map    Passed0.02 sec
Start 3: framework
3/4 Test #3: framework ***Failed0.65 sec
Running suite(s): Ulfius framework function tests
86%: Checks: 15, Failures: 2, Errors: 0
/<>/test/framework.c:630:P:test_ulfius_framework:test_ulfius_simple_endpoint:0:
 Passed
/<>/test/framework.c:767:P:test_ulfius_framework:test_ulfius_net_type_endpoint:0:
 Passed
/<>/test/framework.c:845:P:test_ulfius_framework:test_ulfius_endpoint_parameters:0:
 Passed
/<>/test/framework.c:896:P:test_ulfius_framework:test_ulfius_endpoint_injection:0:
 Passed
/<>/test/framework.c:971:P:test_ulfius_framework:test_ulfius_endpoint_multiple:0:
 Passed
/<>/test/framework.c:994:P:test_ulfius_framework:test_ulfius_endpoint_stream:0:
 Passed
/<>/test/framework.c:1024:P:test_ulfius_framework:test_ulfius_utf8_not_ignored:0:
 Passed
/<>/test/framework.c:1056:P:test_ulfius_framework:test_ulfius_utf8_ignored:0:
 Passed
/<>/test/framework.c:1083:P:test_ulfius_framework:test_ulfius_endpoint_callback_position:0:
 Passed
/<>/test/framework.c:1115:P:test_ulfius_framework:test_ulfius_MHD_set_response_with_other_free:0:
 Passed
/<>/test/framework.c:1145:F:test_ulfius_framework:test_ulfius_send_smtp:0:
 Assertion 'ulfius_send_smtp_email("localhost", 2525, 0, 0, ((void *)0), ((void 
*)0), "from", "to", "cc", "bcc", "subject", "mail body") == 0' failed: 
ulfius_send_smtp_email("localhost", 2525, 0, 0, ((void *)0), ((void *)0), 
"from", "to", "cc", "bcc", "subject", "mail body") == 5, 0 == 0
/<>/test/framework.c:1169:F:test_ulfius_framework:test_ulfius_send_rich_smtp:0:
 Assertion 'ulfius_send_smtp_rich_email("localhost", 2526, 0, 0, ((void *)0), 
((void *)0), "from", "to", "cc", "bcc", "text/ulfius; charset=utf-42", 
"subject", "mail body") == 0' failed: ulfius_send_smtp_rich_email("localhost", 
2526, 0, 0, ((void *)0), ((void *)0), "from", "to", "cc", "bcc", "text/ulfius; 
charset=utf-42", "subject", "mail body") == 5, 0 == 0
/<>/test/framework.c:1208:P:test_ulfius_framework:test_ulfius_follow_redirect:0:
 Passed
/<>/test/framework.c:1230:P:test_ulfius_framework:test_ulfius_server_ca_trust:0:
 Passed
/<>/test/framework.c:1306:P:test_ulfius_framework:test_ulfius_client_certificate:0:
 Passed

Start 4: websocket
4/4 Test #4: websocket    Passed3.04 sec

75% tests passed, 1 tests failed out of 4

Total Test time (real) =   3.78 sec

The following tests FAILED:
  3 - framework (Failed)
Errors while running CTest
make[2]: *** [Makefile:118: test] Error 8
make[2]: Leaving directory '/<>/build'
make[1]: *** [debian/rules:29: override_dh_auto_test] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:11: binary-arch] Error 2
dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2


thanks

G.

Bug#969561: brotli: breaking reverse-dependencies

[Gianfranco Costamagna]

Source: brotli
Version: 1.0.9-1
Severity: serious
tags: patch


Hello, an upstream change broke pkg-config based detection.

https://ci.debian.net/data/autopkgtest/testing/amd64/f/freetype/6909179/log.gz

please 

wget https://github.com/google/brotli/pull/838.patch && add-patch 838.patch

thanks 

Gianfranco

Bug#969538: vips/ruby-vips: autopkgtest regression on arm64 and ppc64el

[Gianfranco Costamagna]

Source: vips
Version: 8.10.0-1
Severity: serious

Hello, your package regressed its testsuite on arm64 in Debian and Ubuntu (in 
Ubuntu also ppc64el, in Debian I didn't check but the failure is the same)

https://ci.debian.net/packages/r/ruby-vips/testing/arm64/


??? Checking Rubygems dependency resolution on ruby2.7  
 ???


GEM_PATH= ruby2.7 -e gem\ \"ruby-vips\"


??? Run tests for ruby2.7 from debian/ruby-tests.rake   
 ???


mv lib .gem2deb.lib
RUBYLIB=. GEM_PATH= ruby2.7 -S rake -f debian/ruby-tests.rake
/usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib/rspec/core/rake_task.rb:125:
 warning: deprecated Object#=~ is called on Array; it always returns nil
/usr/bin/ruby2.7 
-I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.2/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib
 /usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/exe/rspec --pattern 
./spec/\*\*/\*_spec.rb --backtrace -r ./spec/spec_helper.rb
./usr/lib/ruby/vendor_ruby/vips/object.rb:269: warning: Capturing 
the given block using Proc.new is deprecated; use `` instead
/usr/lib/ruby/vendor_ruby/vips/object.rb:269: warning: Capturing the given 
block using Proc.new is deprecated; use `` instead
./usr/lib/ruby/vendor_ruby/vips/object.rb:269: warning: Capturing the given 
block using Proc.new is deprecated; use `` instead
../usr/lib/ruby/vendor_ruby/vips/object.rb:269: warning: Capturing the given 
block using Proc.new is deprecated; use `` instead
/usr/lib/ruby/vendor_ruby/vips/object.rb:269: warning: Capturing the given 
block using Proc.new is deprecated; use `` instead
..F

Failures:

  1) Vips::Image can dilate
 Failure/Error: expect(im.getpoint(11, 12)).to eq([255])

   expected: [255]
got: [0.0]

   (compared using ==)
 # 
/usr/share/rubygems-integration/all/gems/rspec-support-3.9.2/lib/rspec/support.rb:97:in
 `block in '
 # 
/usr/share/rubygems-integration/all/gems/rspec-support-3.9.2/lib/rspec/support.rb:106:in
 `notify_failure'
 # 
/usr/share/rubygems-integration/all/gems/rspec-expectations-3.9.0/lib/rspec/expectations/fail_with.rb:35:in
 `fail_with'
 # 
/usr/share/rubygems-integration/all/gems/rspec-expectations-3.9.0/lib/rspec/expectations/handler.rb:38:in
 `handle_failure'
 # 
/usr/share/rubygems-integration/all/gems/rspec-expectations-3.9.0/lib/rspec/expectations/handler.rb:50:in
 `block in handle_matcher'
 # 
/usr/share/rubygems-integration/all/gems/rspec-expectations-3.9.0/lib/rspec/expectations/handler.rb:27:in
 `with_matcher'
 # 
/usr/share/rubygems-integration/all/gems/rspec-expectations-3.9.0/lib/rspec/expectations/handler.rb:48:in
 `handle_matcher'
 # 
/usr/share/rubygems-integration/all/gems/rspec-expectations-3.9.0/lib/rspec/expectations/expectation_target.rb:65:in
 `to'
 # ./spec/image_spec.rb:477:in `block (2 levels) in '
 # 
/usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib/rspec/core/example.rb:257:in
 `instance_exec'
 # 
/usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib/rspec/core/example.rb:257:in
 `block in run'
 # 
/usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib/rspec/core/example.rb:503:in
 `block in with_around_and_singleton_context_hooks'
 # 
/usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib/rspec/core/example.rb:460:in
 `block in with_around_example_hooks'
 # 
/usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib/rspec/core/hooks.rb:472:in
 `block in run'
 # 
/usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib/rspec/core/hooks.rb:610:in
 `run_around_example_hooks_for'
 # 
/usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib/rspec/core/hooks.rb:472:in
 `run'
 # 
/usr/share/rubygems-integration/all/gems/rspec-core-3.9.1/lib/rspec/core/example.rb:460:in
 `with_around_example_hooks'
 # 

Bug#963290: re: e-antic: FTBFS: ../e-antic/e-antic.h:24:2: error: #error FLINT 2.5.2 or 2.5.3 required

[Gianfranco Costamagna]

control: tags -1 patch pending

Hello, I changed a little bit the changelog, removed the useless patch and 
uploaded to sid!

G.

On Thu, 27 Aug 2020 19:46:28 +0100 peter green  wrote:
> tags 963290 +patch
> thanks
> 
> I just took a look at this issue.
> 
> First I did some digging in the upstream git repo. Once I figured out their 
> branch structure (the "master0" branch is
> apparently where current releases are made from) I was able to find two 
> relavent commits.
> 10ed02f429f75a418ee41814af2dffc8cd41101f which added support for flint 2.6.0 
> and cebabe52632013a70be321d590301e06c306a766
> which removed the upper limit on the flint version.
> 
> I applied these to the Debian package, in the process I found that 
> 10ed02f429f75a418ee41814af2dffc8cd41101f conflicted
> with the existing debian patch upstream-fix-sprintf_buffer_overflow.patch, 
> following the upstream issue report link
> for that patch lead to a claim the issue was fixed as part of 
> 10ed02f429f75a418ee41814af2dffc8cd41101f so I removed
> upstream-fix-sprintf_buffer_overflow.patch from the series.
> 
> Next I ran into an issue with a test failing to build because it could not 
> find the newly added
> EANTIC_FIXED_fmpq_poly_add_fmpq symbol. I added the symbol to the version 
> script.
> 
> The final issue I ran into was that some symbols had disappeared.
> 
> +#MISSING: 0.1.5+ds-2+rpi1# 
> EANTIC_FIXED_fmpq_poly_get_str_pretty@LIBEANTIC_0_1_2 0.1.2
> +#MISSING: 0.1.5+ds-2+rpi1# 
> _EANTIC_FIXED_fmpq_poly_get_str_pretty@LIBEANTIC_0_1_2 0.1.2
> +#MISSING: 0.1.5+ds-2+rpi1# _nf_elem_mod_fmpz@LIBEANTIC_0_1_2 0.1.2
> +#MISSING: 0.1.5+ds-2+rpi1# nf_elem_mod_fmpz@LIBEANTIC_0_1_2 0.1.2
> +#MISSING: 0.1.5+ds-2+rpi1# nf_elem_mod_fmpz_den@LIBEANTIC_0_1_2 0.1.2
> 
> I searched for EANTIC_FIXED_fmpq_poly_get_str_pretty and nf_elem_mod_fmpz on 
> the
> codesearch.debian.net website . I also installed all the reverse-dependencies
> listed on the autoremoval list and then grepped in /usr/lib and /usr/bin .
> With the source search the only references I found were in the e-antic
> source package. With the binary search the only references I found were
> in libeantic.so.0.1.5 and libeantic.a. As such I decided it was probably
> ok to remove the symbols from the symbols file and went ahead and updated
> the symbols file.
> 
> With that I was able to get a successful build in Raspbian bullseye-staging
> and I have uploaded the package to Raspbian. A debdiff should appear soon
> at https://debdiffs.raspbian.org/main/e/e-antic
> 
> 
diff -Nru e-antic-0.1.5+ds/debian/changelog e-antic-0.1.5+ds/debian/changelog
--- e-antic-0.1.5+ds/debian/changelog   2020-05-19 14:45:32.00000 +0200
+++ e-antic-0.1.5+ds/debian/changelog   2020-08-27 17:59:03.0 +0200
@@ -1,3 +1,26 @@
+e-antic (0.1.5+ds-2.1) unstable; urgency=medium
+
+  [ Gianfranco Costamagna ]
+  * Non-maintianer upload
+
+  [ Peter Michael Green ]
+  * Fix build with flint 2.6.3 (Closes: 963290 )
++ Apply upstream commit 10ed02f429f75a418ee41814af2dffc8cd41101f
+  as debian/patches/flint-2.6.0.patch to support flint 2.6.0
++ Apply upstream commit cebabe52632013a70be321d590301e06c306a766
+  as debian/patches/remove-flint-upperlimit.patch to allow builds
+  with newer flint versions.
++ Disable debian/patches/upstream-fix-sprintf_buffer_overflow.patch
+  it conflicts with the flint 2.6.0 patch and according to 
+  https://github.com/videlec/e-antic/pull/92 the issue it addresses
+  was fixed as part of that patch.
++ Add EANTIC_FIXED_fmpq_poly_add_fmpq to libeantic.map in
+  upstream-libtool-version_script.patch
++ Update symbols file, removed symbols do not appear to be
+  used by any other packages in Debian.
+
+ -- Peter Michael Green   Thu, 27 Aug 2020 15:59:03 
+
+
 e-antic (0.1.5+ds-2) unstable; urgency=medium
 
   * Serious fix release, revert symbols (Closes: #960614, #960875).
diff -Nru e-antic-0.1.5+ds/debian/libeantic0.symbols 
e-antic-0.1.5+ds/debian/libeantic0.symbols
--- e-antic-0.1.5+ds/debian/libeantic0.symbols  2020-05-19 14:40:01.0 
+0200
+++ e-antic-0.1.5+ds/debian/libeantic0.symbols  2020-08-27 17:59:03.0 
+0200
@@ -1,8 +1,7 @@
 libeantic.so.0 libeantic0 #MINVER#
 * Build-Depends-Package: libeantic-dev
- EANTIC_FIXED_fmpq_poly_get_str_pretty@LIBEANTIC_0_1_2 0.1.2
+ EANTIC_FIXED_fmpq_poly_add_fmpq@LIBEANTIC_0_1_2 0.1.5+ds-2+rpi1
  LIBEANTIC_0_1_2@LIBEANTIC_0_1_2 0.1.2
- _EANTIC_FIXED_fmpq_poly_get_str_pretty@LIBEANTIC_0_1_2 0.1.2
  _fmpq_poly_resultant_div@LIBEANTIC_0_1_2 0.1.2
  _fmpq_vec_fprint@LIBEANTIC_0_1_2 0.1.2
  _fmpq_vec_randtest_uniq_sorted@LIBEANTIC_0_1_2 0.1.2
@@ -33,7 +32,6 @@
  _nf_elem_get_nmod_poly@LIBEANTIC_0_1_2 0.1.2
  _nf_elem_inv@LIBEANTIC_0_1_2 0.1.2
  _nf_elem_invertible_check@LIBEANTIC_0_1_2 0.1.2
- _nf_elem_

Bug#968681: [Pkg-javascript-devel] Bug#968681: nodejs: regresses in ppc64el ( node-create-hash, node-crypto-browserify, node-sha.js)

[Gianfranco Costamagna]

Hello,
On Wed, 19 Aug 2020 22:39:03 +0200 =?UTF-8?B?SsOpcsOpbXkgTGFs?= 
 wrote:
> Le mer. 19 ao??t 2020 ?? 21:12, Gianfranco Costamagna <
> locutusofb...@debian.org> a ??crit :
> 
> > Source: nodejs
> > Version: 12.18.2~dfsg-1
> > Severity: serious
> >
> > Hello, looks like node-create-hask, node-crypto-browserify, node-sha.js
> > have autopkgtests failures on ppc64el.
> >
> > there might be an upstream patch according to Ubuntu bug [1]  and v8
> > commits
> >
> >
> > https://ci.debian.net/data/autopkgtest/unstable/ppc64el/n/node-crypto-browserify/6740061/log.gz
> >
> >
> > https://ci.debian.net/data/autopkgtest/unstable/ppc64el/n/node-sha.js/6740057/log.gz
> >
> >
> > https://ci.debian.net/data/autopkgtest/unstable/ppc64el/n/node-create-hash/6738537/log.gz
> >
> >
> > the attached diff (based on upstream changes) might help in fixing the
> > failures.
> >
> > [1]
> > https://bugs.launchpad.net/ubuntu/+source/node-create-hash/+bug/1887144
> >
> > I just uploaded in Ubuntu, will see in 24h or so if the problem is fixed
> > or not.
> >
> 
> Thanks, i'll apply the patch later this week, then.

I confirm nodejs migrated with ppc64el being green in its autopkgtests!

G.

Bug#969364: ignition-math: FTBFS in sid

[Gianfranco Costamagna]

Source: ignition-math
Version: 6.4.0+ds-9
Severity: serious

Hello, your package failed to build on arm64, ppc64el, s390x, ia64, powerpc, 
ppc64, riscv64
because of a testsuite error:

  Start 22: UNIT_Pose_TEST
22/46 Test #22: UNIT_Pose_TEST ...***Failed0.00 sec
Running main() from /usr/src/gtest/src/gtest_main.cc
[==] Running 3 tests from 1 test suite.
[--] Global test environment set-up.
[--] 3 tests from PoseTest
[ RUN  ] PoseTest.Pose
[   OK ] PoseTest.Pose (0 ms)
[ RUN  ] PoseTest.ConstPose
[   OK ] PoseTest.ConstPose (0 ms)
[ RUN  ] PoseTest.OperatorStreamOut
/<>/src/Pose_TEST.cc:155: Failure
Expected equality of these values:
  stream.str()
Which is: "0.1 1.2 2.3 -0 0.1 1"
  "0.1 1.2 2.3 0 0.1 1"
[  FAILED  ] PoseTest.OperatorStreamOut (0 ms)
[--] 3 tests from PoseTest (0 ms total)

[--] Global test environment tear-down
[==] 3 tests from 1 test suite ran. (0 ms total)
[  PASSED  ] 2 tests.
[  FAILED  ] 1 test, listed below:
[  FAILED  ] PoseTest.OperatorStreamOut

 1 FAILED TEST

  Start 23: UNIT_Quaternion_TEST
23/46 Test #23: UNIT_Quaternion_TEST .   Passed0.00 sec


cheers,

Gianfranco

Bug#969196: zimlib: symbols updates for architectures built with -O3

[Gianfranco Costamagna]

Source: zimlib
Version: 6.2.0-2
Severity: serious
tags: patch

Hello, zimlib symbols file seems to be really difficult to maintain, breaking 
on each icu upload, each new gcc upload,
different gcc optimization levels (such as -O2 and -O3) and so on.

Somebody thinks that symbols files for c++ applications are a waste of time, 
but I'm sending you another patch that fixes the issue for now, by adding some 
symbols, and marking some other as optional
https://wiki.debian.org/UsingSymbolsFiles


diff -Nru zimlib-6.2.0/debian/changelog zimlib-6.2.0/debian/changelog
--- zimlib-6.2.0/debian/changelog   2020-08-28 07:35:20.0 +
+++ zimlib-6.2.0/debian/changelog   2020-08-29 07:43:31.0 +
@@ -1,3 +1,9 @@
+zimlib (6.2.0-2ubuntu1) groovy; urgency=medium
+
+  * Refresh symbols
+
+ -- Gianfranco Costamagna   Sat, 29 Aug 2020 
09:43:31 +0200
+
 zimlib (6.2.0-2) unstable; urgency=medium
 
   * Upload to unstable
diff -Nru zimlib-6.2.0/debian/libzim6.symbols 
zimlib-6.2.0/debian/libzim6.symbols
--- zimlib-6.2.0/debian/libzim6.symbols 2020-08-28 06:40:45.0 +
+++ zimlib-6.2.0/debian/libzim6.symbols 2020-08-29 07:43:30.0 +
@@ -138,7 +138,7 @@
  _ZN3zim14TemplateParser15state_token_endEc@Base 6.0.2
  _ZN3zim14TemplateParser5flushEv@Base 6.0.2
  _ZN3zim14TemplateParser8state_ltEc@Base 6.0.2
- _ZN3zim15search_iterator12InternalData11get_articleEv@Base 6.2.0
+ 
(optional=templinst)_ZN3zim15search_iterator12InternalData11get_articleEv@Base 
6.2.0
  _ZN3zim15search_iteratorC1EOS0_@Base 6.0.2
  _ZN3zim15search_iteratorC1EPNS0_12InternalDataE@Base 6.0.2
  _ZN3zim15search_iteratorC1ERKS0_@Base 6.0.2
@@ -185,9 +185,9 @@
  
_ZN3zim4unix2FS13makeDirectoryERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
 6.0.2
  
_ZN3zim4unix2FS4joinERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES9_@Base
 6.0.2
  
_ZN3zim4unix2FS6removeERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
 6.0.2
- 
_ZN3zim4unix2FS6renameERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES9_@Base
 6.0.2
- 
_ZN3zim4unix2FS8openFileERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
 6.0.2
- 
_ZN3zim4unix2FS9removeDirERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
 6.0.2
+ 
(optional=templinst)_ZN3zim4unix2FS6renameERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES9_@Base
 6.0.2
+ 
(optional=templinst)_ZN3zim4unix2FS8openFileERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
 6.0.2
+ 
(optional=templinst)_ZN3zim4unix2FS9removeDirERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
 6.0.2
 #MISSING: 6.2.0# 
(optional=templinst|arch=!riscv64)_ZN3zim5CacheINS_15article_index_tESt10shared_ptrIKNS_6DirentEEE3putERKS1_RKS5_@Base
 6.0.2
 #MISSING: 6.2.0# 
(optional=templinst|arch=!riscv64)_ZN3zim5CacheINS_15cluster_index_tESt10shared_ptrINS_7ClusterEEE3putERKS1_RKS4_@Base
 6.0.2
  
(optional=templinst)_ZN3zim5findxINS_8FileImplEEESt4pairIbNS_15article_index_tEERT_cRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
 6.2.0
@@ -343,6 +343,8 @@
  
_ZN3zim8FileImplC2ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 
6.0.2
  _ZN3zim8FileImplD1Ev@Base 6.0.2
  _ZN3zim8FileImplD2Ev@Base 6.0.2
+ 
(optional=templinst)_ZN3zim8FilePartINS_4unix2FSEEC1ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
 6.2.0-2
+ 
(optional=templinst)_ZN3zim8FilePartINS_4unix2FSEEC2ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
 6.2.0-2
 #MISSING: 6.1.3# _ZN3zim8ZIP_INFO4nameB5cxx11E@Base 6.0.2
  _ZN3zim8envValueEPKcj@Base 6.0.2
 #MISSING: 6.1.3# _ZN3zim9LZMA_INFO4nameB5cxx11E@Base 6.0.2
@@ -377,6 +379,8 @@
  (optional=templinst)_ZN5QueueIPN3zim6writer7ClusterEED0Ev@Base 6.1.3
  (optional=templinst)_ZN5QueueIPN3zim6writer7ClusterEED1Ev@Base 6.1.3
  (optional=templinst)_ZN5QueueIPN3zim6writer7ClusterEED2Ev@Base 6.1.3
+ (optional=templinst)_ZN6Xapian13LatLongCoordsC1ERKNS_12LatLongCoordE@Base 
6.2.0-2
+ (optional=templinst)_ZN6Xapian13LatLongCoordsC2ERKNS_12LatLongCoordE@Base 
6.2.0-2
  
(optional=templinst)_ZN6Xapian8Internal13intrusive_ptrINS_5Query8InternalEED1Ev@Base
 6.2.0
  
(optional=templinst)_ZN6Xapian8Internal13intrusive_ptrINS_5Query8InternalEED2Ev@Base
 6.2.0
 #MISSING: 6.1.3# 
(optional=templinst|arch=!amd64)_ZN6icu_6314StringByteSinkINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIc6AppendEPKci@Base
 6.0.2
@@ -651,7 +655,7 @@
  (optional=templinst|arch=!armel 
!riscv64)_ZNSt12__shared_ptrIN3zim12MemoryBufferELN9__gnu_cxx12_Lock_policyE2EEC2ISaIS1_EJRNS0_7zsize_tSt20_Sp_alloc_shared_tagIT_EDpOT0_@Base
 6.2.0
  
_ZNSt12system_errorC1ESt10error_codeRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
 6.0.2
  
_ZNSt12system_errorC2ESt10error_codeRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
 6.0.2
- (arch=!amd64 !arm64 !hppa !mipsel !sh4 
!x32)_ZNSt13__future_base13_State_baseV216_M_break_promiseESt10unique_ptrINS_12_Result_baseENS2_8_DeleterEE@Base
 6.2.0
+ (arch=!amd64 !arm64 !hppa !mipsel !ppc64el

Bug#968965: xen: FTBFS in sid

[Gianfranco Costamagna]

Source: xen
Version: 4.11.4+24-gddaaccbbab-1
Severity: serious

Hello, looks like xen is FTBFS because of some bd-uninstallable python package 
and a gcc-10 related build failure. 




gcc  -m64 -DBUILD_ID -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes 
-Wdeclaration-after-statement -Wno-unused-but-set-variable 
-Wno-unused-local-typedefs   -O2 -fomit-frame-pointer 
-D__XEN_INTERFACE_VERSION__=__XEN_LATEST_INTERFACE_VERSION__ -MMD -MF .tdb.o.d 
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE  -g -O2 
-fdebug-prefix-map=/build/xen-4.11.4+24-gddaaccbbab=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Werror -I. 
-include /build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/config.h 
-I./include 
-I/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/libs/evtchn/include
 -I/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/include 
-I/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/libxc/include 
-I/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/libs/toollog/include
 -I/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/include 
-I/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/libs/foreignmemory/include
 -I/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/include 
-I/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/libs/devicemodel/include
 -I/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/include 
-I/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/include 
-D__XEN_TOOLS__ 
-I/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/libs/toolcore/include
 -I/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/include 
-DXEN_LIB_STORED="\"/var/lib/xenstored\"" 
-DXEN_RUN_STORED="\"/var/run/xenstored\""  
-I/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/libs/gnttab/include
 -I/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/include  -c -o 
tdb.o tdb.c 
gcc  -m64 -DBUILD_ID -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes 
-Wdeclaration-after-statement -Wno-unused-but-set-variable 
-Wno-unused-local-typedefs   -O2 -fomit-frame-pointer 
-D__XEN_INTERFACE_VERSION__=__XEN_LATEST_INTERFACE_VERSION__ -MMD -MF 
.talloc.o.d -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE  -g -O2 
-fdebug-prefix-map=/build/xen-4.11.4+24-gddaaccbbab=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Werror -I. 
-include /build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/config.h 
-I./include 
-I/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/libs/evtchn/include
 -I/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/include 
-I/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/libxc/include 
-I/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/libs/toollog/include
 -I/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/include 
-I/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/libs/foreignmemory/include
 -I/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/include 
-I/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/libs/devicemodel/include
 -I/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/include 
-I/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/include 
-D__XEN_TOOLS__ 
-I/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/libs/toolcore/include
 -I/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/include 
-DXEN_LIB_STORED="\"/var/lib/xenstored\"" 
-DXEN_RUN_STORED="\"/var/run/xenstored\""  
-I/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/libs/gnttab/include
 -I/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/include  -c -o 
talloc.o talloc.c 
gcc xs_tdb_dump.o utils.o tdb.o talloc.o-Wl,-z,relro -Wl,-z,now  -o 
xs_tdb_dump 
/usr/bin/ld: utils.o:./tools/xenstore/utils.h:27: multiple definition of 
`xprintf'; xs_tdb_dump.o:./tools/xenstore/utils.h:27: first defined here
collect2: error: ld returned 1 exit status
make[6]: *** [Makefile:97: xs_tdb_dump] Error 1
make[6]: Leaving directory '/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore'
make[5]: *** [/build/xen-4.11.4+24-gddaaccbbab/tools/../tools/Rules.mk:253: 
subdir-install-xenstore] Error 2
make[5]: Leaving directory '/build/xen-4.11.4+24-gddaaccbbab/tools'
make[4]: *** [/build/xen-4.11.4+24-gddaaccbbab/tools/../tools/Rules.mk:248: 
subdirs-install] Error 2
make[4]: Leaving directory '/build/xen-4.11.4+24-gddaaccbbab/tools'
make[3]: *** [Makefile:74: install] Error 2
make[3]: Leaving directory '/build/xen-4.11.4+24-gddaaccbbab/tools'
make[2]: *** [Makefile:127: install-tools] Error 2
make[2]: Leaving directory '/build/xen-4.11.4+24-gddaaccbbab'
make[1]: *** [debian/rules:202: override_dh_auto_build] Error 2
make[1]: Leaving directory '/build/xen-4.11.4+24-gddaaccbbab'
make: *** [debian/rules:150: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
I: 

Bug#968946: coccinelle: FTBFS in sid

[Gianfranco Costamagna]

Source: coccinelle
Version: 1.0.8.deb-3
Severity: serious

Hello, some ocaml changes broke the build of coccinelle

http://debomatic-amd64.debian.net/distribution#unstable/coccinelle/1.0.8.deb-3/buildlog

snip of the failure:
OCAMLCparsing_cocci/command_line.mli
File "parsing_cocci/parser_cocci_menhir.mli", line 234, characters 25-36:
234 |   (Ast_cocci.meta_name * Ast.metavar) option * Ast.mvinit)
   ^^^
Error: Unbound module AstOCAMLCparsing_c/token_annot.mli

OCAMLCparsing_c/flag_parsing_c.mli
make[1]: *** [Makefile:421: parsing_cocci/parser_cocci_menhir.cmi] Error 2

thanks for having a look

Gianfranco

Bug#968940: linux: please add patch to support virtualbox on kernel 5.8

[Gianfranco Costamagna]

Source: linux
Version: 5.8.3-1~exp1
Severity: serious
tags: patch

Hello, as explained on upstream ticket [1], the new kernel broke virtualbox, 
and the only fix that has been found
so far is to export map_kernel_range and __get_vm_area_caller to modules

https://www.virtualbox.org/attachment/ticket/19644/local_patches

This trivial patch does the trick
diff --git a/mm/vmalloc.c b/mm/vmalloc.c
--- a/mm/vmalloc.c
+++ b/mm/vmalloc.c
@@ -325,6 +325,7 @@ int map_kernel_range(unsigned long start, unsigned long 
size, pgprot_t prot,
flush_cache_vmap(start, start + size);
return ret;
 }
+EXPORT_SYMBOL(map_kernel_range);
 
 int is_vmalloc_or_module_addr(const void *x)
 {
@@ -2130,6 +2131,7 @@ struct vm_struct *__get_vm_area_caller(unsigned long 
size, unsigned long flags,
return __get_vm_area_node(size, 1, flags, start, end, NUMA_NO_NODE,
  GFP_KERNEL, caller);
 }
+EXPORT_SYMBOL(__get_vm_area_caller);
 
 /**
  * get_vm_area - reserve a contiguous kernel virtual area


[1] https://www.virtualbox.org/ticket/19644

thanks

Gianfranco

Bug#968245: [Pkg-pascal-devel] Bug#968245: Bug#968245: fpc: autopkgtest failure.

[Gianfranco Costamagna]

Hello,

> Once fpc is otherwise in a good state i'll pop a mail
> to Adam Conrad asking him to bootstrap it for ppc64el Ubuntu.

I'll try to bootstrap it

G.

Bug#968681: nodejs: regresses in ppc64el ( node-create-hash, node-crypto-browserify, node-sha.js)

[Gianfranco Costamagna]

Source: nodejs
Version: 12.18.2~dfsg-1
Severity: serious

Hello, looks like node-create-hask, node-crypto-browserify, node-sha.js have 
autopkgtests failures on ppc64el.

there might be an upstream patch according to Ubuntu bug [1]  and v8 commits

https://ci.debian.net/data/autopkgtest/unstable/ppc64el/n/node-crypto-browserify/6740061/log.gz

https://ci.debian.net/data/autopkgtest/unstable/ppc64el/n/node-sha.js/6740057/log.gz

https://ci.debian.net/data/autopkgtest/unstable/ppc64el/n/node-create-hash/6738537/log.gz


the attached diff (based on upstream changes) might help in fixing the failures.

[1] https://bugs.launchpad.net/ubuntu/+source/node-create-hash/+bug/1887144

I just uploaded in Ubuntu, will see in 24h or so if the problem is fixed or not.

G.
diff -Nru nodejs-12.18.2~dfsg/debian/changelog 
nodejs-12.18.2~dfsg/debian/changelog
--- nodejs-12.18.2~dfsg/debian/changelog2020-07-28 15:12:12.0 
+0200
+++ nodejs-12.18.2~dfsg/debian/changelog2020-08-19 20:47:23.0 
+0200
@@ -1,3 +1,12 @@
+nodejs (12.18.2~dfsg-1ubuntu2) groovy; urgency=medium
+
+  * debian/patches/3f071e3.patch:
+  * debian/patches/1a9c676a141b32483b48884f8cc0330e64c8e17f.patch:
+- cherry-pick two upstream changes in v8 to fix a testsuite failure on
+  ppc64el for some sha1 calculation errors (LP: #1887144)
+
+ -- Gianfranco Costamagna   Wed, 19 Aug 2020 
20:47:23 +0200
+
 nodejs (12.18.2~dfsg-1ubuntu1) groovy; urgency=medium
 
   * Merge from Debian (LP: #1882185). Remaining changes:
diff -Nru 
nodejs-12.18.2~dfsg/debian/patches/1a9c676a141b32483b48884f8cc0330e64c8e17f.patch
 
nodejs-12.18.2~dfsg/debian/patches/1a9c676a141b32483b48884f8cc0330e64c8e17f.patch
--- 
nodejs-12.18.2~dfsg/debian/patches/1a9c676a141b32483b48884f8cc0330e64c8e17f.patch
   1970-01-01 01:00:00.0 +0100
+++ 
nodejs-12.18.2~dfsg/debian/patches/1a9c676a141b32483b48884f8cc0330e64c8e17f.patch
   2020-08-19 20:47:23.0 +0200
@@ -0,0 +1,44 @@
+From 1a9c676a141b32483b48884f8cc0330e64c8e17f Mon Sep 17 00:00:00 2001
+From: Milad Farazmand 
+Date: Mon, 10 Aug 2020 20:19:25 +
+Subject: [PATCH] PPC: clear high 32 bits from the result of mulhw.
+
+The hight 32 bits of the result of mulhw are undefined and need
+to be cleared manually.
+
+Change-Id: I0e746898aa26a7970ab59b89c374afd1377028ea
+Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2347208
+Reviewed-by: Junliang Yan 
+Commit-Queue: Milad Farazmand 
+Cr-Commit-Position: refs/heads/master@{#69318}
+---
+ src/compiler/backend/ppc/code-generator-ppc.cc | 14 ++
+ 1 file changed, 10 insertions(+), 4 deletions(-)
+
+diff --git a/deps/v8/src/compiler/backend/ppc/code-generator-ppc.cc 
b/deps/v8/src/compiler/backend/ppc/code-generator-ppc.cc
+index 337cd795ede..c18500f6e3b 100644
+--- a/deps/v8/src/compiler/backend/ppc/code-generator-ppc.cc
 b/deps/v8/src/compiler/backend/ppc/code-generator-ppc.cc
+@@ -1480,12 +1480,18 @@ CodeGenerator::CodeGenResult 
CodeGenerator::AssembleArchInstruction(
+   }
+   break;
+ case kPPC_MulHigh32:
+-  __ mulhw(i.OutputRegister(), i.InputRegister(0), i.InputRegister(1),
+-   i.OutputRCBit());
++  __ mulhw(ip, i.InputRegister(0), i.InputRegister(1), i.OutputRCBit());
++  // High 32 bits are undefined and need to be cleared.
++  __ li(r0, Operand(-1));
++  __ clrldi(r0, r0, Operand(32));
++  __ and_(i.OutputRegister(), ip, r0);
+   break;
+ case kPPC_MulHighU32:
+-  __ mulhwu(i.OutputRegister(), i.InputRegister(0), i.InputRegister(1),
+-i.OutputRCBit());
++  __ mulhwu(ip, i.InputRegister(0), i.InputRegister(1), i.OutputRCBit());
++  // High 32 bits are undefined and need to be cleared.
++  __ li(r0, Operand(-1));
++  __ clrldi(r0, r0, Operand(32));
++  __ and_(i.OutputRegister(), ip, r0);
+   break;
+ case kPPC_MulDouble:
+   ASSEMBLE_FLOAT_BINOP_RC(fmul, MiscField::decode(instr->opcode()));
diff -Nru nodejs-12.18.2~dfsg/debian/patches/3f071e3.patch 
nodejs-12.18.2~dfsg/debian/patches/3f071e3.patch
--- nodejs-12.18.2~dfsg/debian/patches/3f071e3.patch1970-01-01 
01:00:00.0 +0100
+++ nodejs-12.18.2~dfsg/debian/patches/3f071e3.patch2020-08-19 
20:47:23.0 +0200
@@ -0,0 +1,39 @@
+From 3f071e3e7e15af187267af6c3b369029e27c8cf5 Mon Sep 17 00:00:00 2001
+From: Milad Farazmand 
+Date: Tue, 11 Aug 2020 17:57:09 +
+Subject: [PATCH] PPC: Optimize clearing higher bits of mulhw/mulhwu
+
+Change-Id: Ie3e14a6ef4531349e81a8ae741bc7470c7e547ca
+Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2349468
+Reviewed-by: Junliang Yan 
+Commit-Queue: Milad Farazmand 
+Cr-Commit-Position: refs/heads/master@{#69343}
+---
+
+diff --git a/deps/v8/src/compiler/backend/ppc/code-generator-ppc.cc 
b/deps/v8/src/compiler/backend/ppc/code-generator-ppc.cc
+index c18500f..59cef69 100644
+--- a/deps/v8/src/compiler/backend/ppc/code-generator-ppc.cc
 b/deps/v8/src/compiler/backend/ppc/c

Bug#964854: fixed in npm 6.14.7+ds-1

[Gianfranco Costamagna]

control: reopen -1
control: notfixed -1 6.14.7+ds-1

hello, looks like "ppc64" might also be in that list?

# Subtest: test/tap/legacy-platform-all.js
# Subtest: setup
1..0
ok 1 - setup # time=5.306ms

# Subtest: platform-all
not ok 1 - no error messages
  ---
  found: >
npm ERR! code EBADPLATFORM
  
npm ERR! notsup Unsupported platform for 
npm-test-platform-all@9.9.9-9: wanted

{"os":"darwin,linux,win32,solaris,haiku,sunos,freebsd,openbsd,netbsd","arch":"arm,arm64,mips,ia32,x64,s390x,ppc64el,sparc"}
(current: {"os":"linux","arch":"ppc64"})
  
npm ERR! notsup Valid OS:   
darwin,linux,win32,solaris,haiku,sunos,freebsd,openbsd,netbsd
  
npm ERR! notsup Valid Arch:  
arm,arm64,mips,ia32,x64,s390x,ppc64el,sparc
  
npm ERR! notsup Actual OS:   linux
  
npm ERR! notsup Actual Arch: ppc64
  
  
npm ERR! A complete log of this run can be found in:
  
npm ERR!

/tmp/autopkgtest.JLLdmV/autopkgtest_tmp/smokeAAJn6A/test/npm_cache_legacy-platform-all/_logs/2020-08-15T16_06_49_618Z-debug.log
  wanted: ''
  compare: '==='
  at:
line: 57
column: 7
file: test/tap/legacy-platform-all.js
type: global
function: installCheckAndTest
  stack: |
installCheckAndTest (test/tap/legacy-platform-all.js:57:7)
f (/usr/lib/nodejs/once/once.js:25:25)
ChildProcess. (test/common-tap.js:175:5)
  source: |
t.is(stderr, '', 'no error messages')
  ...

not ok 2 - install went ok
  ---
  found: 1
  wanted: 0
  compare: '==='
  at:
line: 58
column: 7
file: test/tap/legacy-platform-all.js
type: global
function: installCheckAndTest
  stack: |
installCheckAndTest (test/tap/legacy-platform-all.js:58:7)
f (/usr/lib/nodejs/once/once.js:25:25)
ChildProcess. (test/common-tap.js:175:5)
  source: |
t.is(code, 0, 'install went ok')
  ...

1..2
# failed 2 of 2 tests
not ok 2 - platform-all # time=1282.134ms

# Subtest: cleanup
1..0
ok 3 - cleanup # time=3.81ms

1..3
# failed 1 of 3 tests
# time=1309.345ms
not ok 104 - test/tap/legacy-platform-all.js # time=2226.423ms
  ---


see https://autopkgtest.ubuntu.com/packages/n/npm/groovy/ppc64el for the full 
log.

I'm uploading a fix in Ubuntu with sed s/ppc64el/ppc64/g but I'm not sure if it 
will work or not

the version with that change:
--- npm-6.14.7+ds/debian/patches/add-s390x-and-ppc64el.diff 2020-08-14 
12:47:23.0 +0200
+++ npm-6.14.7+ds/debian/patches/add-s390x-and-ppc64el.diff 2020-08-15 
22:22:37.0 +0200
@@ -7,11 +7,12 @@
 
 --- a/test/tap/legacy-platform-all.js
 +++ b/test/tap/legacy-platform-all.js
-@@ -37,6 +37,8 @@
+@@ -37,6 +37,9 @@
  'mips',
  'ia32',
  'x64',
 +'s390x',
++'ppc64',
 +'ppc64el',
  'sparc'
]


is versioned 6.14.7+ds-1ubuntu1

G.
On Fri, 14 Aug 2020 11:51:03 + Debian FTP Masters 
 wrote:
> Source: npm
> Source-Version: 6.14.7+ds-1
> Done: Xavier Guimard 
> 
> We believe that the bug you reported is fixed in the latest version of
> npm, 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 964...@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
> 
> Debian distribution maintenance software
> pp.
> Xavier Guimard  (supplier of updated npm 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: Fri, 14 Aug 2020 13:26:21 +0200
> Source: npm
> Architecture: source
> Version: 6.14.7+ds-1
> Distribution: unstable
> Urgency: medium
> Maintainer: Debian Javascript Maintainers 
> 
> Changed-By: Xavier Guimard 
> Closes: 964854
> Changes:
>  npm (6.14.7+ds-1) unstable; urgency=medium
>  .
>* Team upload
>* Add s390x and ppc64el in supported platforms list (Closes: #964854)
>* New upstream version 6.14.7+ds
>* Update copyright
>* Update lintian overrides
> Checksums-Sha1: 
>  64864237a2da564ab1575716241dc9180bf27769 6736 npm_6.14.7+ds-1.dsc
>  83de3a66bca8d8b5a14b84fa5d8dba4c4fcf3b6c 1435316 npm_6.14.7+ds.orig.tar.xz
>  

Bug#957964: wvstreams: ftbfs with GCC-10

[Gianfranco Costamagna]

control: tags -1 patch pending

uploading patch from meta-oe

G.

On Fri, 17 Apr 2020 11:13:44 + Matthias Klose  wrote:
> Package: src:wvstreams
> Version: 4.6.1-14
> Severity: normal
> Tags: sid bullseye
> User: debian-...@lists.debian.org
> Usertags: ftbfs-gcc-10
> 
> Please keep this issue open in the bug tracker for the package it
> was filed for.  If a fix in another package is required, please
> file a bug for the other package (or clone), and add a block in this
> package. Please keep the issue open until the package can be built in
> a follow-up test rebuild.
> 
> The package fails to build in a test rebuild on at least amd64 with
> gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
> severity of this report will be raised before the bullseye release,
> so nothing has to be done for the buster release.
> 
> The full build log can be found at:
> http://people.debian.org/~doko/logs/gcc10-20200225/wvstreams_4.6.1-14_unstable_gcc10.log
> The last lines of the build log are at the end of this report.
> 
> To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
> or install the gcc, g++, gfortran, ... packages from experimental.
> 
>   apt-get -t=experimental install g++ 
> 
> Common build failures are new warnings resulting in build failures with
> -Werror turned on, or new/dropped symbols in Debian symbols files.
> For other C/C++ related build failures see the porting guide at
> http://gcc.gnu.org/gcc-10/porting_to.html
> 
> [...]
>  from xplc-cxx/uuidtostr.cc:32:
> /usr/include/features.h:185:3: warning: #warning "_BSD_SOURCE and 
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>   185 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
> _DEFAULT_SOURCE"
>   |   ^~~
> ./CXX -c xplc-cxx/xplc   
> x86_64-linux-gnu-g++ -c -o xplc-cxx/xplc.o xplc-cxx/xplc.cc -MMD -MF 
> xplc-cxx/.xplc.d -MP -MQ xplc-cxx/xplc.o -I/usr/include/dbus-1.0 
> -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/tcl8.3 -DDEBUG=0 
> -I./include -D_BSD_SOURCE -D_GNU_SOURCE -D_LARGEFILE_SOURCE 
> -D_FILE_OFFSET_BITS=64 -DUNSTABLE -fPIC -Wall -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fno-tree-dce 
> -fno-optimize-sibling-calls -fPIC -DPIC -fno-tree-dce 
> -fno-optimize-sibling-calls -Wall -Woverloaded-virtual
> In file included from /usr/include/x86_64-linux-gnu/sys/types.h:25,
>  from ./include/xplc/uuid.h:84,
>  from ./include/xplc/IObject.h:36,
>  from ./include/xplc/IMoniker.h:30,
>  from xplc-cxx/xplc.cc:33:
> /usr/include/features.h:185:3: warning: #warning "_BSD_SOURCE and 
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>   185 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
> _DEFAULT_SOURCE"
>   |   ^~~
> ./CXX -c xplc/category   
> x86_64-linux-gnu-g++ -c -o xplc/category.o xplc/category.cc -MMD -MF 
> xplc/.category.d -MP -MQ xplc/category.o -I/usr/include/dbus-1.0 
> -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/tcl8.3 -DDEBUG=0 
> -I./include -D_BSD_SOURCE -D_GNU_SOURCE -D_LARGEFILE_SOURCE 
> -D_FILE_OFFSET_BITS=64 -DUNSTABLE -fPIC -Wall -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fno-tree-dce 
> -fno-optimize-sibling-calls -fPIC -DPIC -fno-tree-dce 
> -fno-optimize-sibling-calls -Wall -Woverloaded-virtual
> In file included from /usr/include/x86_64-linux-gnu/sys/types.h:25,
>  from ./include/xplc/uuid.h:84,
>  from ./include/xplc/IObject.h:36,
>  from ./include/xplc/IServiceManager.h:35,
>  from ./include/xplc/core.h:26,
>  from ./include/xplc/utils.h:47,
>  from xplc/category.cc:22:
> /usr/include/features.h:185:3: warning: #warning "_BSD_SOURCE and 
> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
>   185 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use 
> _DEFAULT_SOURCE"
>   |   ^~~
> ./CXX -c xplc/catiter   


wvstreams_4.6.1-15.debian.tar.xz
Description: application/xz

Bug#968339: kodi: FTBFS in sid (test failures)

[Gianfranco Costamagna]

Source: kodi
Version: 2:18.8+dfsg1-1
Severity: serious

Hello, the package fails its testsuite on amd64 and armhf because of:
99% tests passed, 1 tests failed out of 520

Total Test time (real) =  44.44 sec

The following tests FAILED:
418 - TestSharedSection.TwoCase (Child aborted)


and
99% tests passed, 1 tests failed out of 520

Total Test time (real) =  58.55 sec

The following tests FAILED:
424 - TestEvent.Group (SEGFAULT)
Errors while running CTest


Can you please have a look?

thanks

Gianfranco

Bug#968276: yi: FTBFS in sid (missing deps)

[Gianfranco Costamagna]

Source: yi
Version: 0.18.0-2
Severity: serious

Lots of yi related deps have been removed, yi still depends on them


Installing build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libghc-yi-core-dev : Depends: libghc-listlike-dev-4.6.2-4ca26 but it is not 
installable
  Depends: libghc-array-dev-0.5.3.0-ea273 but it is not 
installable
  Depends: libghc-attoparsec-dev-0.13.2.2-c82a3 but it is 
not installable
  Depends: libghc-base-dev-4.12.0.0-a86a1 but it is not 
installable
  Depends: libghc-binary-dev-0.8.6.0-5ca49 but it is not 
installable
  Depends: libghc-bytestring-dev-0.10.8.2-20f27 but it is 
not installable
  Depends: libghc-containers-dev-0.6.0.1-b7319 but it is 
not installable
  Depends: libghc-data-default-dev-0.7.1.1-96adc but it is 
not installable
  Depends: libghc-directory-dev-1.3.3.0-40647 but it is not 
installable
  Depends: libghc-dlist-dev-0.8.0.6-0ddfa but it is not 
installable
  Depends: libghc-dynamic-state-dev-0.3.1-cf25d but it is 
not installable
  Depends: libghc-exceptions-dev-0.10.2-29311 but it is not 
installable
  Depends: libghc-filepath-dev-1.4.2.1-774a0 but it is not 
installable
  Depends: libghc-hashable-dev-1.2.7.0-4dcfe but it is not 
installable
  Depends: libghc-microlens-platform-dev-0.3.11-33537 but 
it is not installable
  Depends: libghc-mtl-dev-2.2.2-07ff1 but it is not 
installable
  Depends: libghc-old-locale-dev-1.0.0.7-05a9f but it is 
not installable
  Depends: libghc-oo-prototypes-dev-0.1.0.0-0f142 but it is 
not installable
  Depends: libghc-parsec-dev-3.1.13.0-732de but it is not 
installable
  Depends: libghc-pointedlist-dev-0.6.1-cfc04 but it is not 
installable
  Depends: libghc-process-dev-1.6.5.0-e8028 but it is not 
installable
  Depends: libghc-process-extras-dev-0.7.4-f5097 but it is 
not installable
  Depends: libghc-split-dev-0.2.3.3-ec171 but it is not 
installable
  Depends: libghc-text-dev-1.2.3.1-538d8 but it is not 
installable
  Depends: libghc-time-dev-1.8.0.2-76e12 but it is not 
installable
  Depends: libghc-transformers-base-dev-0.4.5.2-b6c26 but 
it is not installable
  Depends: libghc-unix-dev-2.7.2.2-dbe0e but it is not 
installable
  Depends: libghc-unix-compat-dev-0.5.1-e698d but it is not 
installable
  Depends: libghc-unordered-containers-dev-0.2.10.0-31f27 
but it is not installable
  Depends: libghc-xdg-basedir-dev-0.2.2-c4583 but it is not 
installable
  Depends: libghc-yi-language-dev-0.18.0-2efd1
  Depends: libghc-yi-rope-dev-0.11-57f97 but it is not 
installable
 libghc-yi-core-prof : Depends: libghc-listlike-prof-4.6.2-4ca26 but it is not 
installable
   Depends: libghc-array-prof-0.5.3.0-ea273 but it is not 
installable
   Depends: libghc-attoparsec-prof-0.13.2.2-c82a3 but it is 
not installable
   Depends: libghc-base-prof-4.12.0.0-a86a1 but it is not 
installable
   Depends: libghc-binary-prof-0.8.6.0-5ca49 but it is not 
installable
   Depends: libghc-bytestring-prof-0.10.8.2-20f27 but it is 
not installable
   Depends: libghc-containers-prof-0.6.0.1-b7319 but it is 
not installable
   Depends: libghc-data-default-prof-0.7.1.1-96adc but it 
is not installable
   Depends: libghc-directory-prof-1.3.3.0-40647 but it is 
not installable
   Depends: libghc-dlist-prof-0.8.0.6-0ddfa but it is not 
installable
   Depends: libghc-dynamic-state-prof-0.3.1-cf25d but it is 
not installable
   Depends: libghc-exceptions-prof-0.10.2-29311 but it is 
not installable
   Depends: libghc-filepath-prof-1.4.2.1-774a0 but it is 
not installable
   Depends: libghc-hashable-prof-1.2.7.0-4dcfe but it is 
not installable
   Depends: libghc-microlens-platform-prof-0.3.11-33537 but 
it is not installable
   Depends: libghc-mtl-prof-2.2.2-07ff1 but 

Bug#968225: advi: FTBFS in sid

[Gianfranco Costamagna]

Source: advi
Version: 1.10.2-6
Severity: serious

   dh_fixperms
   dh_missing
   dh_dwz
dwz: debian/advi/usr/bin/advi: DWARF version 0 unhandled
dwz: Too few files for multifile optimization
dh_dwz: error: dwz -mdebian/advi/usr/lib/debug/.dwz/x86_64-linux-gnu/advi.debug 
-M/usr/lib/debug/.dwz/x86_64-linux-gnu/advi.debug -- debian/advi/usr/bin/advi 
debian/advi/usr/lib/ocaml/stublibs/dlladvi.so returned exit code 1


Looks like also advi got trapped by this new bug...

G.

Bug#957063: calculix-cgx: ftbfs with GCC-10

[Gianfranco Costamagna]

control: fixed -1 2.17+dfsg-1
control: close -1

We can consider it "fixed" in the new release

G.

On Fri, 17 Apr 2020 10:57:34 + Matthias Klose  wrote:
> Package: src:calculix-cgx
> Version: 2.11+dfsg-1
> Severity: normal
> Tags: sid bullseye
> User: debian-...@lists.debian.org
> Usertags: ftbfs-gcc-10
> 
> Please keep this issue open in the bug tracker for the package it
> was filed for.  If a fix in another package is required, please
> file a bug for the other package (or clone), and add a block in this
> package. Please keep the issue open until the package can be built in
> a follow-up test rebuild.
> 
> The package fails to build in a test rebuild on at least amd64 with
> gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
> severity of this report will be raised before the bullseye release,
> so nothing has to be done for the buster release.
> 
> The full build log can be found at:
> http://people.debian.org/~doko/logs/gcc10-20200225/calculix-cgx_2.11+dfsg-1_unstable_gcc10.log
> The last lines of the build log are at the end of this report.
> 
> To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
> or install the gcc, g++, gfortran, ... packages from experimental.
> 
>   apt-get -t=experimental install g++ 
> 
> Common build failures are new warnings resulting in build failures with
> -Werror turned on, or new/dropped symbols in Debian symbols files.
> For other C/C++ related build failures see the porting guide at
> http://gcc.gnu.org/gcc-10/porting_to.html
> 
> [...]
> generateTet.cpp:402:10: warning: deprecated conversion from string constant 
> to ‘char*’ [-Wwrite-strings]
>   402 |   delSet("+snodSet");
>   |  ^~
> generateTet.cpp:403:10: warning: deprecated conversion from string constant 
> to ‘char*’ [-Wwrite-strings]
>   403 |   delSet("+velemSet");
>   |  ^~~
> generateTet.cpp:404:20: warning: deprecated conversion from string constant 
> to ‘char*’ [-Wwrite-strings]
>   404 |   snodSet=pre_seta("+snodSet","i",0);
>   |^~
> generateTet.cpp:404:31: warning: deprecated conversion from string constant 
> to ‘char*’ [-Wwrite-strings]
>   404 |   snodSet=pre_seta("+snodSet","i",0);
>   |   ^~~
> generateTet.cpp:405:18: warning: deprecated conversion from string constant 
> to ‘char*’ [-Wwrite-strings]
>   405 |   setNr=pre_seta("+velemSet","i",0);
>   |  ^~~
> generateTet.cpp:405:30: warning: deprecated conversion from string constant 
> to ‘char*’ [-Wwrite-strings]
>   405 |   setNr=pre_seta("+velemSet","i",0);
>   |  ^~~
> generateTet.cpp:419:39: warning: deprecated conversion from string constant 
> to ‘char*’ [-Wwrite-strings]
>   419 |   for(k=0; k<3; k++) 
> seta(snodSet,"n",e_enqire[surf[s].elem[i]].nod[k]);
>   |   ^~~
> generateTet.cpp:439:14: warning: deprecated conversion from string constant 
> to ‘char*’ [-Wwrite-strings]
>   439 | { errMsg("ERROR: realloc failure in generateTet\n"); return(0); }
>   |  ^
> generateTet.cpp:500:19: warning: deprecated conversion from string constant 
> to ‘char*’ [-Wwrite-strings]
>   500 |   if ( (  readNG( "test.vol", anz_ng, , _ng, _ng, 
> NULL)) == -1)
>   |   ^~

Bug#968176: gdcm: wrong debian/control file (mono archs missing)

[Gianfranco Costamagna]

Source: gdcm
Version: 3.0.7-2
Severity: serious

Hello, your debian/control file is missing the restrictions for archs (e.g. 
ports, and mips64el),
leading to BD-uninstallabilities where mono is not available.

Please refresh the file to make it build everywhere

thanks

Gianfranco

Bug#966655: orthanc: using tzdata but missing dependency on it?

[Gianfranco Costamagna]

Source: orthanc
Version: 1.7.2+dfsg-1
Severity: serious
tags: patch

Hello, looks like orthanc fails to build from source (testsuite error) when 
tzdata is not installed in the chroot.

I'm not sure if this is an essential package or not, but looks like it can be 
removed, or not be available on some chroots


this is an example of failure

mkdir -p /<>/debian/tmp/locale/
localedef -f UTF-8 -i en_US /<>/debian/tmp/locale/en_US.UTF-8/
( cd Build; LOCPATH=/<>/debian/tmp/locale/ ./UnitTests )
E0731 17:53:29.829350 OrthancException.h:76] Internal error: On UNIX-like 
systems, the file /etc/localtime must be present on the filesystem (install 
"tzdata" package on Debian)
terminate called after throwing an instance of 'Orthanc::OrthancException'
Aborted (core dumped)
make[1]: *** [debian/rules:73: override_dh_auto_test] Error 134


I think adding it as explicit dependency might solve some headaches.

G.

Bug#966654: libgpiod: symbol mismatches with gcc-10/O3 optimization

[Gianfranco Costamagna]

Source: libgpiod
Version: 1.5.1-1
Severity: serious
tags: patch

Hello, looks like some symbols are disappearing when built with -O3 
optimization level, and some other
changed in armhf and ppc64el (probably due to gcc-10)

the following patch seems to be enough to make everybody happy, by making some 
symbols optional.
thanks for considering it

G.


--- libgpiod-1.5.1/debian/changelog 2020-07-01 05:27:41.0 +0200
+++ libgpiod-1.5.1/debian/changelog 2020-07-31 20:08:33.0 +0200
@@ -1,3 +1,9 @@
+libgpiod (1.5.1-1.1) unstable; urgency=medium
+
+  * Refresh symbols (Closes: #-1)
+
+ -- Gianfranco Costamagna   Fri, 31 Jul 2020 
20:08:33 +0200
+
 libgpiod (1.5.1-1) unstable; urgency=medium
 
   * Import new upstream release
diff -Nru libgpiod-1.5.1/debian/libgpiod2.symbols 
libgpiod-1.5.1/debian/libgpiod2.symbols
--- libgpiod-1.5.1/debian/libgpiod2.symbols 2020-07-01 05:27:19.0 
+0200
+++ libgpiod-1.5.1/debian/libgpiod2.symbols 2020-07-31 20:08:33.0 
+0200
@@ -99,6 +99,8 @@
  gpiod_line_update@Base 1.1
  gpiod_version_string@Base 1.1
 libgpiodcxx.so.1 libgpiod2 #MINVER#
+ (c++|optional)"std::_Function_base::~_Function_base()@Base" 1.5.1
+ (c++|optional)"std::_Function_base::~_Function_base()@Base" 1.5.1
  (c++)"gpiod::line_request::FLAG_ACTIVE_LOW@Base" 1.1
  (c++)"gpiod::line_request::FLAG_OPEN_DRAIN@Base" 1.1
  (c++)"gpiod::line_request::FLAG_OPEN_SOURCE@Base" 1.1
@@ -209,7 +211,7 @@
  (c++)"std::system_error::system_error(int, std::_V2::error_category const&, 
std::__cxx11::basic_string, std::allocator > 
const&)@Base" 1.1
  (c++)"std::system_error::system_error(std::error_code, char const*)@Base" 1.1
  (c++)"std::system_error::system_error(int, std::_V2::error_category const&, 
std::__cxx11::basic_string, std::allocator > 
const&)@Base" 1.1
- (c++)"std::_Function_base::_Base_manager, 
std::allocator > const&)>::_M_manager(std::_Any_data&, std::_Any_data 
const&, std::_Manager_operation)@Base" 1.1
+ (c++|optional)"std::_Function_base::_Base_manager, 
std::allocator > const&)>::_M_manager(std::_Any_data&, std::_Any_data 
const&, std::_Manager_operation)@Base" 1.1
  (c++|arch= !armel !riscv64)"std::_Sp_counted_ptr::_M_dispose()@Base" 1.1
  (c++|arch= !armel 
!riscv64)"std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_destroy()@Base" 
1.1
  (c++)"std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release()@Base" 
1.4.1
@@ -219,8 +221,8 @@
  (c++|optional|arch-bits=32)"std::vector 
>::_M_default_append(unsigned int)@Base" 1.5.1
  (c++|optional)"void std::__cxx11::basic_string, 
std::allocator >::_M_construct(char const*, char const*, 
std::forward_iterator_tag)@Base" 1.1
  (c++|optional)"std::_Rb_tree, 
std::_Select1st >, std::less, 
std::allocator > >::_M_get_insert_unique_pos(int 
const&)@Base" 1.1
- (c++|arch=amd64 arm64 ppc64el mips64el riscv64)"std::_Rb_tree, std::_Select1st >, 
std::less, std::allocator > 
>::_M_get_insert_hint_unique_pos(std::_Rb_tree_const_iterator >, int const&)@Base" 1.1
- (c++)"std::_Rb_tree, 
std::_Select1st >, std::less, 
std::allocator > 
>::_M_erase(std::_Rb_tree_node >*)@Base" 1.1
+ (c++|optional|arch=amd64 arm64 ppc64el mips64el riscv64)"std::_Rb_tree, std::_Select1st >, 
std::less, std::allocator > 
>::_M_get_insert_hint_unique_pos(std::_Rb_tree_const_iterator >, int const&)@Base" 1.1
+ (c++|optional)"std::_Rb_tree, 
std::_Select1st >, std::less, 
std::allocator > 
>::_M_erase(std::_Rb_tree_node >*)@Base" 1.1
  (c++|arch= !armel !riscv64)"typeinfo for 
std::_Mutex_base<(__gnu_cxx::_Lock_policy)2>@Base" 1.1
  (c++|arch= !armel !riscv64)"typeinfo for 
std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>@Base" 1.1
  (c++|arch= !armel !riscv64)"typeinfo name for 
std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>@Base" 1.4
@@ -235,6 +237,6 @@
  (c++|arch= armel riscv64)"typeinfo name for __gnu_cxx::__mutex@Base" 1.2
  (c++|arch= armel riscv64)"typeinfo name for 
std::_Mutex_base<(__gnu_cxx::_Lock_policy)1>@Base" 1.2
  (c++|arch= armel riscv64)"typeinfo name for 
std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)1>@Base" 1.2
- (c++|arch= i386 armel mipsel armhf s390x)"std::map, 
std::allocator > 
>::map(std::initializer_list >, std::less 
const&, std::allocator > const&)@Base" 1.3
+ (c++|optional|arch= i386 armel mipsel armhf s390x)"std::map, std::allocator > 
>::map(std::initializer_list >, std::less 
const&, std::allocator > const&)@Base" 1.3
  (c++|arch= !armel 
!riscv64)"std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release()@Base" 
1.4.1
  (c++|arch= !armel !riscv64)"typeinfo name for 
std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>@Base" 1.4.1

Bug#966600: nfstrace: patch for newer json-c/gcc-10

[Gianfranco Costamagna]

control: forwarded -1 https://github.com/epam/nfstrace/pull/42

G.

Bug#966600: nfstrace: patch for newer json-c/gcc-10

[Gianfranco Costamagna]

:)
https://github.com/epam/nfstrace/pull/42 






Il venerdì 31 luglio 2020, 11:41:12 CEST, Andrej Shadura  ha 
scritto: 





Hi,

On Fri, 31 Jul 2020, at 11:23, Gianfranco Costamagna wrote:
> Source: nfstrace
> Version: 0.4.3.2+git20180104+6561cf6-1
> Severity: serious
> tags: patch
>  
> hello, attached a patch that makes it build with newer json-c/gcc-10


Thanks! Could you please also submit it upstream or should I?

-- 
Cheers,
  Andrej

Bug#966597: multipath-tools: patch for newer json-c

[Gianfranco Costamagna]

hello,

I see lots of various people upstream did
sed s/TRUE/1/g
sed s/FALSE/0/g

:)

G.






Il venerdì 31 luglio 2020, 11:29:45 CEST, Chris Hofstaedtler  
ha scritto: 





Hi Gianfranco,

* Gianfranco Costamagna  [200731 10:30]:
> Source: multipath-tools
> Version: 0.8.4-2
> Severity: serious
> tags: patch
>  
> hello, attached a patch that makes it build with newer json-c


Thanks! I'm considering going with a somewhat different patch given 
TRUE is used only once at all.

Should be done soon.

Chris

Bug#957236: frr: ftbfs with GCC-10

[Gianfranco Costamagna]

control: close -1
thanks

G.
On Fri, 17 Apr 2020 11:00:39 + Matthias Klose  wrote:
> Package: src:frr
> Version: 7.2.1-1
> Severity: normal
> Tags: sid bullseye
> User: debian-...@lists.debian.org
> Usertags: ftbfs-gcc-10
> 
> Please keep this issue open in the bug tracker for the package it
> was filed for.  If a fix in another package is required, please
> file a bug for the other package (or clone), and add a block in this
> package. Please keep the issue open until the package can be built in
> a follow-up test rebuild.
> 
> The package fails to build in a test rebuild on at least amd64 with
> gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
> severity of this report will be raised before the bullseye release,
> so nothing has to be done for the buster release.
> 
> The full build log can be found at:
> http://people.debian.org/~doko/logs/gcc10-20200225/frr_7.2.1-1_unstable_gcc10.log
> The last lines of the build log are at the end of this report.
> 
> To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
> or install the gcc, g++, gfortran, ... packages from experimental.
> 
>   apt-get -t=experimental install g++ 
> 
> Common build failures are new warnings resulting in build failures with
> -Werror turned on, or new/dropped symbols in Debian symbols files.
> For other C/C++ related build failures see the porting guide at
> http://gcc.gnu.org/gcc-10/porting_to.html
> 
> [...]
> /bin/bash ./libtool  --tag=CC   --mode=link gcc -std=gnu11   -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -fno-omit-frame-pointer -funwind-tables -Wall -Wextra 
> -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith 
> -Wbad-function-cast -Wwrite-strings -Wno-unused-result -Wno-unused-parameter 
> -Wno-missing-field-initializers -pthread -export-dynamic-Wl,-z,relro 
> -Wl,-z,now -o ospf6d/ospf6d ospf6d/ospf6_main.o ospf6d/libospf6.a 
> lib/libfrr.la -lcap -ldl -lcrypt   -ljson-c -lsystemd -lrt
> libtool: link: gcc -std=gnu11 -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security 
> -fno-omit-frame-pointer -funwind-tables -Wall -Wextra -Wmissing-prototypes 
> -Wmissing-declarations -Wpointer-arith -Wbad-function-cast -Wwrite-strings 
> -Wno-unused-result -Wno-unused-parameter -Wno-missing-field-initializers 
> -pthread -Wl,-z -Wl,relro -Wl,-z -Wl,now -o ospfd/.libs/ospfd 
> ospfd/ospf_main.o -Wl,--export-dynamic  ospfd/libfrrospf.a 
> lib/.libs/libfrr.so -lcap -lm -ldl -lcrypt -ljson-c -lsystemd -lrt -pthread 
> -Wl,-rpath -Wl,/usr/lib/x86_64-linux-gnu/frr
> libtool: link: gcc -std=gnu11 -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security 
> -fno-omit-frame-pointer -funwind-tables -Wall -Wextra -Wmissing-prototypes 
> -Wmissing-declarations -Wpointer-arith -Wbad-function-cast -Wwrite-strings 
> -Wno-unused-result -Wno-unused-parameter -Wno-missing-field-initializers 
> -pthread -Wl,-z -Wl,relro -Wl,-z -Wl,now -o ospf6d/.libs/ospf6d 
> ospf6d/ospf6_main.o -Wl,--export-dynamic  ospf6d/libospf6.a 
> lib/.libs/libfrr.so -lcap -ldl -lcrypt -ljson-c -lsystemd -lrt -pthread 
> -Wl,-rpath -Wl,/usr/lib/x86_64-linux-gnu/frr
> /bin/bash ./libtool  --tag=CC   --mode=link gcc -std=gnu11   -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -fno-omit-frame-pointer -funwind-tables -Wall -Wextra 
> -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith 
> -Wbad-function-cast -Wwrite-strings -Wno-unused-result -Wno-unused-parameter 
> -Wno-missing-field-initializers -pthread -export-dynamic-Wl,-z,relro 
> -Wl,-z,now -o isisd/isisd isisd/isis_bpf.o isisd/isis_dlpi.o 
> isisd/isis_main.o isisd/isis_pfpacket.o yang/frr-isisd.yang.o isisd/libisis.a 
> lib/libfrr.la -lcap -ldl -lcrypt   -ljson-c -lsystemd -lrt
> /bin/bash ./libtool  --tag=CC   --mode=link gcc -std=gnu11   -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -fno-omit-frame-pointer -funwind-tables -Wall -Wextra 
> -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith 
> -Wbad-function-cast -Wwrite-strings -Wno-unused-result -Wno-unused-parameter 
> -Wno-missing-field-initializers -pthread -export-dynamic-Wl,-z,relro 
> -Wl,-z,now -o isisd/fabricd isisd/fabricd-isis_bpf.o 
> isisd/fabricd-isis_dlpi.o isisd/fabricd-isis_main.o 
> isisd/fabricd-isis_pfpacket.o isisd/libfabric.a lib/libfrr.la -lcap -ldl 
> -lcrypt   -ljson-c -lsystemd -lrt
> libtool: link: gcc -std=gnu11 -g -O2 -fdebug-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security 
> -fno-omit-frame-pointer -funwind-tables -Wall -Wextra -Wmissing-prototypes 
> -Wmissing-declarations -Wpointer-arith -Wbad-function-cast -Wwrite-strings 
> -Wno-unused-result -Wno-unused-parameter -Wno-missing-field-initializers 
> -pthread -Wl,-z -Wl,relro -Wl,-z -Wl,now -o isisd/.libs/isisd 
> isisd/isis_bpf.o isisd/isis_dlpi.o 

Bug#958010: yubikey-personalization: ftbfs with GCC-10

[Gianfranco Costamagna]

control: tags -1 patch

On Sun, 26 Jul 2020 14:58:58 +0100 Shayan Doust  wrote:
> Hello,
> 
> Any rough timeframe as to when this FTBFS is fixed?
> 
> Kind regards,
> Shayan Doust

I'm attaching the upstream fix to this bug report.

thanks

G.
## Description: add some description
## Origin/Author: add some origin or author
## Bug: bug URL
>From 09ea16d9e2030e4da6ad00c1e5147e962aa7ff84 Mon Sep 17 00:00:00 2001
From: Klas Lindfors 
Date: Mon, 17 Feb 2020 08:58:33 +0100
Subject: [PATCH] make header declarations extern

fixes #155
---
 ykpers-args.h | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/ykpers-args.h b/ykpers-args.h
index 2a63268..9ff455a 100644
--- a/ykpers-args.h
+++ b/ykpers-args.h
@@ -33,8 +33,8 @@
 
 #include "ykpers.h"
 
-const char *usage;
-const char *optstring;
+extern const char *usage;
+extern const char *optstring;
 
 int args_to_config(int argc, char **argv, YKP_CONFIG *cfg, char *oathid,
 		   size_t oathid_len, const char **infname,

Bug#966606: yubikey-personalization: patch for newer json-c

[Gianfranco Costamagna]

FYI upstream did something like sed s/FALSE/0 and sed s/TRUE/1 on the code, 
instead of defining them.

G.


On Fri, 31 Jul 2020 12:56:16 +0200 Gianfranco Costamagna 
 wrote:
> Source: yubikey-personalization
> Version: 1.20.0-2
> Severity: serious
> tags: patch
>  
> Hello, this is the trivial patch that makes the package build with newer 
> jsonc.
> 
> Description: Patch to make it build with newer json-c deprecated TRUE/FALSE 
> defines
> 
> Author: Gianfranco Costamagna 
> Last-Update: 2020-07-31
> 
> Index: yubikey-personalization-1.20.0/ykpers-json.c
> ===
> --- yubikey-personalization-1.20.0.orig/ykpers-json.c
> +++ yubikey-personalization-1.20.0/ykpers-json.c
> @@ -36,6 +36,14 @@
>  #include 
>  #include 
> 
> +// not exported anymore by new json-c
> +#ifndef TRUE
> +#define TRUE 1
> +#endif
> +#ifndef FALSE
> +#define FALSE 0
> +#endif
> +
>  #ifdef HAVE_JSON_OBJECT_OBJECT_GET_EX
>  #define yk_json_object_object_get(obj, key, value) 
> json_object_object_get_ex(obj, key, )
>  #else
> 
> 
> G. 
> 
> 
> 

Bug#957595: netdata: ftbfs with GCC-10

[Gianfranco Costamagna]

control: tags -1 patch

attached the upstream fix refreshed on top of the current debian version

thanks

Gianfranco

On Fri, 17 Apr 2020 11:07:07 + Matthias Klose  wrote:
> Package: src:netdata
> Version: 1.19.0-2
> Severity: normal
> Tags: sid bullseye
> User: debian-...@lists.debian.org
> Usertags: ftbfs-gcc-10
> 
> Please keep this issue open in the bug tracker for the package it
> was filed for.  If a fix in another package is required, please
> file a bug for the other package (or clone), and add a block in this
> package. Please keep the issue open until the package can be built in
> a follow-up test rebuild.
> 
> The package fails to build in a test rebuild on at least amd64 with
> gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The
> severity of this report will be raised before the bullseye release,
> so nothing has to be done for the buster release.
> 
> The full build log can be found at:
> http://people.debian.org/~doko/logs/gcc10-20200225/netdata_1.19.0-2_unstable_gcc10.log
> The last lines of the build log are at the end of this report.
> 
> To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly,
> or install the gcc, g++, gfortran, ... packages from experimental.
> 
>   apt-get -t=experimental install g++ 
> 
> Common build failures are new warnings resulting in build failures with
> -Werror turned on, or new/dropped symbols in Debian symbols files.
> For other C/C++ related build failures see the porting guide at
> http://gcc.gnu.org/gcc-10/porting_to.html
> 
> [...]
> gcc-I/usr/include/uuid -lcap -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wall -O3 -pthread -flto -I/usr/include/uuid  
>-Wl,-z,relro -Wl,-z,now -Wl,--as-needed -o nfacct.plugin 
> collectors/nfacct.plugin/plugin_nfacct.o 
> libnetdata/adaptive_resortable_list/adaptive_resortable_list.o 
> libnetdata/config/appconfig.o libnetdata/avl/avl.o libnetdata/buffer/buffer.o 
> libnetdata/clocks/clocks.o libnetdata/dictionary/dictionary.o 
> libnetdata/eval/eval.o libnetdata/libnetdata.o libnetdata/locks/locks.o 
> libnetdata/log/log.o libnetdata/popen/popen.o libnetdata/procfile/procfile.o 
> libnetdata/os.o libnetdata/simple_pattern/simple_pattern.o 
> libnetdata/socket/socket.o libnetdata/socket/security.o 
> libnetdata/statistical/statistical.o 
> libnetdata/storage_number/storage_number.o libnetdata/threads/threads.o 
> libnetdata/url/url.o libnetdata/json/json.o libnetdata/json/jsmn.o 
> libnetdata/health/health.o -lm -lz -lcrypto -lssl -luuid -luv -llz4 -lJudy 
> -lcrypto -lssl -ljson-c  -lnetfilter_acct -lmnl  
> /usr/bin/ld: libnetdata/adaptive_resortable_list/adaptive_resortable_list.o 
> (symbol from plugin): in function `arl_callback_str2ull':
> (.text+0x0): multiple definition of `silencers'; 
> collectors/nfacct.plugin/plugin_nfacct.o (symbol from plugin):(.text+0x0): 
> first defined here
> /usr/bin/ld: libnetdata/config/appconfig.o (symbol from plugin): in function 
> `appconfig_section_compare':
> (.text+0x0): multiple definition of `silencers'; 
> collectors/nfacct.plugin/plugin_nfacct.o (symbol from plugin):(.text+0x0): 
> first defined here
> /usr/bin/ld: libnetdata/avl/avl.o (symbol from plugin): in function 
> `avl_search':
> (.text+0x0): multiple definition of `silencers'; 
> collectors/nfacct.plugin/plugin_nfacct.o (symbol from plugin):(.text+0x0): 
> first defined here
> /usr/bin/ld: libnetdata/buffer/buffer.o (symbol from plugin): in function 
> `buffer_reset':
> (.text+0x0): multiple definition of `silencers'; 
> collectors/nfacct.plugin/plugin_nfacct.o (symbol from plugin):(.text+0x0): 
> first defined here
> /usr/bin/ld: libnetdata/clocks/clocks.o (symbol from plugin): in function 
> `test_clock_boottime':
> (.text+0x0): multiple definition of `silencers'; 
> collectors/nfacct.plugin/plugin_nfacct.o (symbol from plugin):(.text+0x0): 
> first defined here
> /usr/bin/ld: libnetdata/dictionary/dictionary.o (symbol from plugin): in 
> function `dictionary_create':
> (.text+0x0): multiple definition of `silencers'; 
> collectors/nfacct.plugin/plugin_nfacct.o (symbol from plugin):(.text+0x0): 
> first defined here
> /usr/bin/ld: libnetdata/eval/eval.o (symbol from plugin): in function 
> `eval_and':
> (.text+0x0): multiple definition of `silencers'; 
> collectors/nfacct.plugin/plugin_nfacct.o (symbol from plugin):(.text+0x0): 
> first defined here
> /usr/bin/ld: libnetdata/libnetdata.o (symbol from plugin): in function 
> `strdupz':
> (.text+0x0): multiple definition of `silencers'; 
> collectors/nfacct.plugin/plugin_nfacct.o (symbol from plugin):(.text+0x0): 
> first defined here
> /usr/bin/ld: libnetdata/locks/locks.o (symbol from plugin): in function 
> `netdata_thread_disable_cancelability':
> (.text+0x0): multiple definition of `silencers'; 
> collectors/nfacct.plugin/plugin_nfacct.o (symbol from plugin):(.text+0x0): 
> first defined here
> /usr/bin/ld: libnetdata/log/log.o (symbol from plugin): in 

Bug#966606: yubikey-personalization: patch for newer json-c

[Gianfranco Costamagna]

Source: yubikey-personalization
Version: 1.20.0-2
Severity: serious
tags: patch
 
Hello, this is the trivial patch that makes the package build with newer jsonc.

Description: Patch to make it build with newer json-c deprecated TRUE/FALSE 
defines

Author: Gianfranco Costamagna 
Last-Update: 2020-07-31

Index: yubikey-personalization-1.20.0/ykpers-json.c
===
--- yubikey-personalization-1.20.0.orig/ykpers-json.c
+++ yubikey-personalization-1.20.0/ykpers-json.c
@@ -36,6 +36,14 @@
 #include 
 #include 

+// not exported anymore by new json-c
+#ifndef TRUE
+#define TRUE 1
+#endif
+#ifndef FALSE
+#define FALSE 0
+#endif
+
 #ifdef HAVE_JSON_OBJECT_OBJECT_GET_EX
 #define yk_json_object_object_get(obj, key, value) 
json_object_object_get_ex(obj, key, )
 #else


G. 

Bug#966604: libu2f-server: patch for newer json-c

[Gianfranco Costamagna]

Source: libu2f-server
Version: 1.1.10-1
Severity: serious
tags: patch

Hello, this is the trivial patch that makes the package build with newer jsonc.


Description: Patch to make it build with newer json-c deprecated TRUE/FALSE 
defines

Author: Gianfranco Costamagna 
Last-Update: 2020-07-31

Index: libu2f-server-1.1.0/u2f-server/core.c
===
--- libu2f-server-1.1.0.orig/u2f-server/core.c
+++ libu2f-server-1.1.0/u2f-server/core.c
@@ -37,6 +37,14 @@
 #include "b64/cdecode.h"
 #include "sha256.h"

+// not exported anymore by new json-c
+#ifndef TRUE
+#define TRUE 1
+#endif
+#ifndef FALSE
+#define FALSE 0
+#endif
+
 #ifdef HAVE_JSON_OBJECT_OBJECT_GET_EX
 #define u2fs_json_object_object_get(obj, key, value) 
json_object_object_get_ex(obj, key, )
 #else


G.

Bug#966602: libu2f-host: patch for newer json-c

[Gianfranco Costamagna]

Source: libu2f-host
Version: 1.1.10-1
Severity: serious
tags: patch

Hello, this is the trivial patch that makes the package build with newer jsonc

Description: Patch to make it build with newer json-c deprecated TRUE/FALSE 
defines

Author: Gianfranco Costamagna 
Last-Update: 2020-07-31

--- libu2f-host-1.1.10.orig/u2f-host/u2fmisc.c
+++ libu2f-host-1.1.10/u2f-host/u2fmisc.c
@@ -26,6 +26,14 @@
 #define HID_TIMEOUT 2
 #define HID_MAX_TIMEOUT 4096

+// not exported anymore by new json-c
+#ifndef TRUE
+#define TRUE 1
+#endif
+#ifndef FALSE
+#define FALSE 0
+#endif
+
 #ifdef HAVE_JSON_OBJECT_OBJECT_GET_EX
 #define u2fh_json_object_object_get(obj, key, value) 
json_object_object_get_ex(obj, key, )
 #else


G.

Bug#957217: forked-daapd: ftbfs with GCC-10

[Gianfranco Costamagna]

control: tags -1 patch


Description: Fix build with gcc-10
Author: Gianfranco Costamagna 
Last-Update: 2020-07-31

--- forked-daapd-26.4+dfsg1.orig/src/input.h
+++ forked-daapd-26.4+dfsg1/src/input.h
@@ -137,7 +137,7 @@ struct input_definition
 /*
  * Input modules should use this to test if playback should end
  */
-int input_loop_break;
+static int input_loop_break;

 /*
  * Transfer stream data to the player's input buffer. The input evbuf will be


I uploaded this patch in Ubuntu, fixing the FTBFS.
(upstream heavily refactored that code, so my suggestion is to move to the new 
upstream release if possible)

G.

Bug#964594: psensor FTBFS with libmicrohttpd 0.9.71

[Gianfranco Costamagna]

control: tags -1 patch pending

NMU ongoing

G.

On Thu, 09 Jul 2020 13:03:10 +0300 Adrian Bunk  wrote:
> Source: psensor
> Version: 1.1.5-1.1
> Severity: serious
> Tags: ftbfs
> 
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/psensor.html
> 
> ...
> server.c: In function 'main':
> server.c:430:21: error: passing argument 5 of 'MHD_start_daemon' from 
> incompatible pointer type [-Werror=incompatible-pointer-types]
>   430 | NULL, NULL, _http_request, server_data.sensors,
>   | ^
>   | |
>   | int (*)(void *, struct MHD_Connection *, const 
> char *, const char *, const char *, const char *, size_t *, void **) {aka int 
> (*)(void *, struct MHD_Connection *, const char *, const char *, const char 
> *, const char *, long unsigned int *, void **)}
> In file included from server.c:39:
> /usr/include/microhttpd.h:2425:1: note: expected 'MHD_AccessHandlerCallback' 
> {aka 'enum MHD_Result (*)(void *, struct MHD_Connection *, const char *, 
> const char *, const char *, const char *, long unsigned int *, void **)'} but 
> argument is of type 'int (*)(void *, struct MHD_Connection *, const char *, 
> const char *, const char *, const char *, size_t *, void **)' {aka 'int 
> (*)(void *, struct MHD_Connection *, const char *, const char *, const char 
> *, const char *, long unsigned int *, void **)'}
>  2425 | MHD_start_daemon (unsigned int flags,
>   | ^~~~
> cc1: all warnings being treated as errors
> make[4]: *** [Makefile:471: server.o] Error 1
> 
> 
diff -Nru psensor-1.1.5/debian/changelog psensor-1.1.5/debian/changelog
--- psensor-1.1.5/debian/changelog  2019-08-12 15:41:22.0 +0200
+++ psensor-1.1.5/debian/changelog  2020-07-31 12:00:39.0 +0200
@@ -1,3 +1,11 @@
+psensor (1.1.5-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/patches/14.patch:
+- adapt to new mhd 0.9.71 with upstream (rebased) patch (Closes: #964594)
+
+ -- Gianfranco Costamagna   Fri, 31 Jul 2020 
12:00:39 +0200
+
 psensor (1.1.5-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru psensor-1.1.5/debian/patches/14.patch 
psensor-1.1.5/debian/patches/14.patch
--- psensor-1.1.5/debian/patches/14.patch   1970-01-01 01:00:00.0 
+0100
+++ psensor-1.1.5/debian/patches/14.patch   2020-07-31 11:56:50.0 
+0200
@@ -0,0 +1,34 @@
+From 3e8dfe6f2a4317c4cab3d5afec42abdefa3cc2df Mon Sep 17 00:00:00 2001
+From: Jean-Philippe Orsini 
+Date: Fri, 17 Jul 2020 00:10:54 +0200
+Subject: [PATCH 1/7] fix compilation with microhttpd since version 0.9.71
+ which changes the return type of the cbk
+
+--- psensor-1.1.5.orig/src/server/server.c
 psensor-1.1.5/src/server/server.c
+@@ -281,13 +281,18 @@ create_response(const char *nurl, const
+  MHD_RESPMEM_MUST_FREE);
+ }
+ 
+-static int cbk_http_request(void *cls,
+-  struct MHD_Connection *connection,
+-  const char *url,
+-  const char *method,
+-  const char *version,
+-  const char *upload_data,
+-  size_t *upload_data_size, void **ptr)
++#if MHD_VERSION < 0x00097002
++static int
++#else
++static enum MHD_Result
++#endif
++cbk_http_request(void *cls,
++   struct MHD_Connection *connection,
++   const char *url,
++   const char *method,
++   const char *version,
++   const char *upload_data,
++   size_t *upload_data_size, void **ptr)
+ {
+   static int dummy;
+   struct MHD_Response *response;
diff -Nru psensor-1.1.5/debian/patches/series 
psensor-1.1.5/debian/patches/series
--- psensor-1.1.5/debian/patches/series 2019-06-30 10:33:04.0 +0200
+++ psensor-1.1.5/debian/patches/series 2020-07-31 11:57:13.0 +0200
@@ -1 +1,2 @@
 0001-Update-rsensor.c-drop-is_error-macro-definition.patch
+14.patch

Bug#966600: nfstrace: patch for newer json-c/gcc-10

[Gianfranco Costamagna]

Source: nfstrace
Version: 0.4.3.2+git20180104+6561cf6-1
Severity: serious
tags: patch
  
hello, attached a patch that makes it build with newer json-c/gcc-10

thanks

Gianfranco
Description: gcc-10 build fixes
Author: Gianfranco Costamagna 
Last-Update: 2020-07-31

--- nfstrace-0.4.3.2+git20180104+6561cf6.orig/analyzers/src/json/json_plugin.cpp
+++ nfstrace-0.4.3.2+git20180104+6561cf6/analyzers/src/json/json_plugin.cpp
@@ -23,6 +23,7 @@
 #include "json_analyzer.h"
 //--
 
+#include 
 static constexpr int DefaultPort = ;
 static constexpr const char* DefaultHost = IpEndpoint::WildcardAddress;
 static constexpr std::size_t DefaultWorkersAmount= 10U;
--- nfstrace-0.4.3.2+git20180104+6561cf6.orig/analyzers/src/watch/nc_windows/statistics_window.cpp
+++ nfstrace-0.4.3.2+git20180104+6561cf6/analyzers/src/watch/nc_windows/statistics_window.cpp
@@ -23,6 +23,7 @@
 #include 
 
 #include 
+#include 
 
 #include "nc_window_const.h"
 #include "statistics_window.h"
--- nfstrace-0.4.3.2+git20180104+6561cf6.orig/analyzers/src/watch/user_gui.cpp
+++ nfstrace-0.4.3.2+git20180104+6561cf6/analyzers/src/watch/user_gui.cpp
@@ -23,6 +23,7 @@
 #include 
 #include 
 #include 
+#include 
 
 #include 
 
--- nfstrace-0.4.3.2+git20180104+6561cf6.orig/src/analysis/analyzers.cpp
+++ nfstrace-0.4.3.2+git20180104+6561cf6/src/analysis/analyzers.cpp
@@ -22,6 +22,7 @@
 #include "analysis/analyzers.h"
 #include "analysis/print_analyzer.h"
 #include "utils/out.h"
+#include 
 //--
 namespace NST
 {
--- nfstrace-0.4.3.2+git20180104+6561cf6.orig/src/controller/controller.h
+++ nfstrace-0.4.3.2+git20180104+6561cf6/src/controller/controller.h
@@ -24,6 +24,7 @@
 #define CONTROLLER_H
 //--
 #include 
+#include 
 
 #include "analysis/analysis_manager.h"
 #include "controller/parameters.h"
--- nfstrace-0.4.3.2+git20180104+6561cf6.orig/src/controller/parameters.cpp
+++ nfstrace-0.4.3.2+git20180104+6561cf6/src/controller/parameters.cpp
@@ -21,6 +21,7 @@
 //--
 #include 
 #include 
+#include 
 
 #include 
 #include 
--- nfstrace-0.4.3.2+git20180104+6561cf6.orig/src/controller/running_status.h
+++ nfstrace-0.4.3.2+git20180104+6561cf6/src/controller/running_status.h
@@ -28,6 +28,7 @@
 #include 
 #include 
 #include 
+#include 
 
 #include "utils/noncopyable.h"
 //--
--- nfstrace-0.4.3.2+git20180104+6561cf6.orig/src/controller/signal_handler.cpp
+++ nfstrace-0.4.3.2+git20180104+6561cf6/src/controller/signal_handler.cpp
@@ -21,6 +21,7 @@
 //--
 #include 
 #include  // std::ref
+#include 
 #include 
 
 #include 
--- nfstrace-0.4.3.2+git20180104+6561cf6.orig/src/filtration/filtration_manager.cpp
+++ nfstrace-0.4.3.2+git20180104+6561cf6/src/filtration/filtration_manager.cpp
@@ -19,6 +19,7 @@
 along with Nfstrace.  If not, see <http://www.gnu.org/licenses/>.
 */
 //--
+#include 
 #include 
 
 #include "filtration/dumping.h"
--- nfstrace-0.4.3.2+git20180104+6561cf6.orig/src/filtration/filtration_processor.h
+++ nfstrace-0.4.3.2+git20180104+6561cf6/src/filtration/filtration_processor.h
@@ -26,6 +26,7 @@
 #include 
 #include 
 #include 
+#include 
 #include 
 #include 
 #include 
--- nfstrace-0.4.3.2+git20180104+6561cf6.orig/src/protocols/xdr/xdr_decoder.h
+++ nfstrace-0.4.3.2+git20180104+6561cf6/src/protocols/xdr/xdr_decoder.h
@@ -23,6 +23,7 @@
 #define XDR_DECODER_H
 //--
 #include 
+#include 
 #include 
 //--
 #include "api/nfs3_types_rpcgen.h"

Bug#966597: rt-app: patch for newer json-c

[Gianfranco Costamagna]

control: retitle -1 multipath-tools: patch for newer json-c

thanks!

G.
On Fri, 31 Jul 2020 10:27:16 +0200 Gianfranco Costamagna 
 wrote:
> Source: multipath-tools
> Version: 0.8.4-2
> Severity: serious
> tags: patch
>  
> hello, attached a patch that makes it build with newer json-c
> 
> Description: Patch to make it build with newer json-c deprecated TRUE/FALSE 
> defines
> 
> Author: Gianfranco Costamagna 
> Last-Update: 2020-07-31
> 
> --- multipath-tools-0.8.4.orig/libdmmp/libdmmp_private.h
> +++ multipath-tools-0.8.4/libdmmp/libdmmp_private.h
> @@ -32,6 +32,14 @@
>  #include 
>  #include 
> 
> +// not exported anymore by new json-c
> +#ifndef TRUE
> +#define TRUE 1
> +#endif
> +#ifndef FALSE
> +#define FALSE 0
> +#endif
> +
>  #include "libdmmp/libdmmp.h"
> 
>  #ifdef __cplusplus
> 
> 
> thanks
> 
> G.
> 
> 
> 

Bug#966597: rt-app: patch for newer json-c

[Gianfranco Costamagna]

Source: multipath-tools
Version: 0.8.4-2
Severity: serious
tags: patch
 
hello, attached a patch that makes it build with newer json-c

Description: Patch to make it build with newer json-c deprecated TRUE/FALSE 
defines

Author: Gianfranco Costamagna 
Last-Update: 2020-07-31

--- multipath-tools-0.8.4.orig/libdmmp/libdmmp_private.h
+++ multipath-tools-0.8.4/libdmmp/libdmmp_private.h
@@ -32,6 +32,14 @@
 #include 
 #include 

+// not exported anymore by new json-c
+#ifndef TRUE
+#define TRUE 1
+#endif
+#ifndef FALSE
+#define FALSE 0
+#endif
+
 #include "libdmmp/libdmmp.h"

 #ifdef __cplusplus


thanks

G.

Bug#966594: rt-app: patch for newer json-c

[Gianfranco Costamagna]

Source: rt-app
Version: 0.3-2
Severity: serious
tags: patch

hello, attached a patch that makes it build with newer json-c

thanks

G.
diff -Nru rt-app-0.3/debian/changelog rt-app-0.3/debian/changelog
--- rt-app-0.3/debian/changelog 2017-03-09 14:44:33.0 +0100
+++ rt-app-0.3/debian/changelog 2020-07-31 10:09:43.0 +0200
@@ -1,3 +1,9 @@
+rt-app (0.3-2.1) unstable; urgency=medium
+
+  * Patch for newer json-c (Closes: #-1)
+
+ -- Gianfranco Costamagna   Fri, 31 Jul 2020 
10:09:43 +0200
+
 rt-app (0.3-2) unstable; urgency=medium
 
   * Fix FTBFS on some arches by defining unsigned long long as __u64
diff -Nru rt-app-0.3/debian/patches/new-jsoncpp.patch 
rt-app-0.3/debian/patches/new-jsoncpp.patch
--- rt-app-0.3/debian/patches/new-jsoncpp.patch 1970-01-01 01:00:00.0 
+0100
+++ rt-app-0.3/debian/patches/new-jsoncpp.patch 2020-07-31 10:09:32.0 
+0200
@@ -0,0 +1,35 @@
+Description: Patch for newer json-c removed is_error
+Author: Gianfranco Costamagna 
+Last-Update: 2020-07-30
+
+Index: rt-app-0.3/src/rt-app_parse_config.c
+===
+--- rt-app-0.3.orig/src/rt-app_parse_config.c
 rt-app-0.3/src/rt-app_parse_config.c
+@@ -18,9 +18,16 @@
+ along with this program; if not, write to the Free Software
+ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301, 
USA.
+ */
+-#include 
+ #include "rt-app_parse_config.h"
+ 
++// not exported anymore by new json-c
++#ifndef TRUE
++#define TRUE 1
++#endif
++#ifndef FALSE
++#define FALSE 0
++#endif
++
+ #define PFX "[json] "
+ #define PFL " "PFX
+ #define PIN PFX""
+@@ -886,7 +893,7 @@
+ {
+   struct json_object *global, *tasks, *resources;
+ 
+-  if (is_error(root)) {
++  if (root == NULL) {
+   log_error(PFX "Error while parsing input JSON");
+   exit(EXIT_INV_CONFIG);
+   }
diff -Nru rt-app-0.3/debian/patches/series rt-app-0.3/debian/patches/series
--- rt-app-0.3/debian/patches/series2017-03-09 14:44:33.0 +0100
+++ rt-app-0.3/debian/patches/series2020-07-31 10:09:39.0 +0200
@@ -1 +1,2 @@
 longlong-u64.diff
+new-jsoncpp.patch

Bug#966131: pylint: Requires old python3-isort (<<5) which won't be available in Debian

[Gianfranco Costamagna]

control: tags -1 patch


Hello, I grabbed the upstream proposed patch and rebased on top of the version 
in Debian.

The result now builds fine and testsuite seems ok


attached!

G.
diff -Nru pylint-2.5.3/debian/changelog pylint-2.5.3/debian/changelog
--- pylint-2.5.3/debian/changelog   2020-07-21 08:18:14.0 +0200
+++ pylint-2.5.3/debian/changelog   2020-07-31 09:34:41.0 +0200
@@ -1,3 +1,10 @@
+pylint (2.5.3-1ubuntu1) groovy; urgency=medium
+
+  * debian/patches/3725.patch:
+- cherry-pick and adapt upstream proposed fix for new isort
+
+ -- Gianfranco Costamagna   Fri, 31 Jul 2020 
09:34:41 +0200
+
 pylint (2.5.3-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru pylint-2.5.3/debian/patches/3725.patch 
pylint-2.5.3/debian/patches/3725.patch
--- pylint-2.5.3/debian/patches/3725.patch  1970-01-01 01:00:00.0 
+0100
+++ pylint-2.5.3/debian/patches/3725.patch  2020-07-31 09:34:41.0 
+0200
@@ -0,0 +1,502 @@
+From db0a6524ac2b1709c1e295cc2377486f32da5bca Mon Sep 17 00:00:00 2001
+From: Damien Baty 
+Date: Sun, 5 Jul 2020 23:06:04 +0200
+Subject: [PATCH 1/3] Support both isort 4 and isort 5
+
+The API of isort 5 (released on 2020-07-04) is completely different.
+We must still support isort 4 because isort 5 dropped the
+compatibility with Python 3.5, which pylint still supports.
+
+Fix #3722.
+---
+ ChangeLog |  4 +++
+ pylint/__pkginfo__.py |  2 +-
+ pylint/checkers/imports.py|  8 +++---
+ pylint/utils/__init__.py  |  2 ++
+ pylint/utils/utils.py | 31 +++
+ tests/functional/w/wrong_import_order.txt |  6 ++---
+ tests/test_functional.py  |  5 
+ tox.ini   |  4 ++-
+ 8 files changed, 52 insertions(+), 10 deletions(-)
+
+Index: pylint/ChangeLog
+===
+--- pylint.orig/ChangeLog
 pylint/ChangeLog
+@@ -40,6 +40,10 @@
+ 
+   Close #3646
+ 
++* Support both isort 4 and isort 5.
++
++  Close #3722
++
+ 
+ What's New in Pylint 2.5.2?
+ ===
+Index: pylint/pylint/__pkginfo__.py
+===
+--- pylint.orig/pylint/__pkginfo__.py
 pylint/pylint/__pkginfo__.py
+@@ -37,7 +37,7 @@
+ 
+ install_requires = [
+ "astroid>=2.4.0,<=2.5",
+-"isort>=4.2.5,<5",
++"isort>=4.2.5,<6",
+ "mccabe>=0.6,<0.7",
+ "toml>=0.7.1",
+ ]
+Index: pylint/pylint/checkers/imports.py
+===
+--- pylint.orig/pylint/checkers/imports.py
 pylint/pylint/checkers/imports.py
+@@ -46,7 +46,6 @@
+ from distutils import sysconfig
+ 
+ import astroid
+-import isort
+ from astroid import modutils
+ from astroid.decorators import cached
+ 
+@@ -60,7 +59,7 @@
+ from pylint.graph import DotBackend, get_cycles
+ from pylint.interfaces import IAstroidChecker
+ from pylint.reporters.ureports.nodes import Paragraph, VerbatimText
+-from pylint.utils import get_global_option
++from pylint.utils import IsortDriver, get_global_option
+ 
+ 
+ def _qualified_names(modname):
+@@ -709,8 +708,7 @@
+ third_party_not_ignored = []
+ first_party_not_ignored = []
+ local_not_ignored = []
+-isort_obj = isort.SortImports(
+-file_contents="",
++isort_driver = IsortDriver(
+ known_third_party=self.config.known_third_party,
+ known_standard_library=self.config.known_standard_library,
+ )
+@@ -723,7 +721,7 @@
+ ignore_for_import_order = not self.linter.is_message_enabled(
+ "wrong-import-order", node.fromlineno
+ )
+-import_category = isort_obj.place_module(package)
++import_category = isort_driver.place_module(package)
+ node_and_package_import = (node, package)
+ if import_category in ("FUTURE", "STDLIB"):
+ std_imports.append(node_and_package_import)
+Index: pylint/pylint/utils/__init__.py
+===
+--- pylint.orig/pylint/utils/__init__.py
 pylint/pylint/utils/__init__.py
+@@ -46,6 +46,8 @@
+ from pylint.utils.ast_walker import ASTWalker
+ from pylint.utils.file_state import FileState
+ from pylint.utils.utils import (
++HAS_ISORT_5,
++IsortDriver,
+ _basename_in_blacklist_re,
+ _check_csv,
+ _format_option_value,
+Index: pylint/pylint/utils/utils.py
+===
+--- pylint.orig/pylint/utils/utils.py
 pylint/pylint/utils/utils.py
+@@ -1,6 +1,15 @@
+ # Licensed under the GPL: 
https://www.gnu.org/licenses/old-licenses/gpl-2.0.html
+ # For details: https://github.com/PyCQA/pylin

Bug#966562: altos: hardcodes runtime json-c dependency

[Gianfranco Costamagna]

Source: altos
Version: 1.9.4-1
Severity: serious
tags: patch

Hello, please update to -c5 or better drop it

in case you want to keep it,

sed s/libjson-c4/libjson-c5/g -i debian/control does the job

G.

Bug#957289: gnss-sdr: ftbfs with GCC-10

[Gianfranco Costamagna]

fstack-protector-strong 
> -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
> -fvisibility=hidden -fvisibility-inlines-hidden   -Wall -Wextra -std=c++2a -o 
> CMakeFiles/acquisition_adapters.dir/beidou_b3i_pcps_acquisition.cc.o -c 
> /<>/src/algorithms/acquisition/adapters/beidou_b3i_pcps_acquisition.cc
> [ 95%] Building CXX object 
> src/algorithms/acquisition/adapters/CMakeFiles/acquisition_adapters.dir/galileo_e1_pcps_8ms_ambiguous_acquisition.cc.o
> cd /<>/obj-x86_64-linux-gnu/src/algorithms/acquisition/adapters 
> && /usr/bin/c++  -DGNSSSDR_INSTALL_DIR=\"/usr\" -D_FILE_OFFSET_BITS=64 
> -D_LARGEFILE_SOURCE -D_LARGE_FILES -I/<>/src/core/interfaces 
> -I/<>/src/algorithms/libs/gsl/include 
> -I/<>/src/algorithms/libs 
> -I/<>/src/algorithms/acquisition/gnuradio_blocks 
> -I/<>/src/algorithms/libs/opencl 
> -I/<>/src/algorithms/acquisition/libs 
> -I/<>/src/core/receiver 
> -I/<>/src/algorithms/channel/libs 
> -I/<>/src/core/system_parameters -isystem /usr/include/glog 
> -isystem 
> /<>/obj-x86_64-linux-gnu/volk_gnsssdr_module/build/include 
> -isystem 
> /<>/src/algorithms/libs/volk_gnsssdr_module/volk_gnsssdr/include 
>  -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
> -fvisibility=hidden -fvisibility-inlines-hidden   -Wall -Wextra -std=c++2a -o 
> CMakeFiles/acquisition_adapters.dir/galileo_e1_pcps_8ms_ambiguous_acquisition.cc.o
>  -c 
> /<>/src/algorithms/acquisition/adapters/galileo_e1_pcps_8ms_ambiguous_acquisition.cc
> [ 95%] Building CXX object 
> src/algorithms/acquisition/adapters/CMakeFiles/acquisition_adapters.dir/galileo_e1_pcps_ambiguous_acquisition.cc.o
> cd /<>/obj-x86_64-linux-gnu/src/algorithms/acquisition/adapters 
> && /usr/bin/c++  -DGNSSSDR_INSTALL_DIR=\"/usr\" -D_FILE_OFFSET_BITS=64 
> -D_LARGEFILE_SOURCE -D_LARGE_FILES -I/<>/src/core/interfaces 
> -I/<>/src/algorithms/libs/gsl/include 
> -I/<>/src/algorithms/libs 
> -I/<>/src/algorithms/acquisition/gnuradio_blocks 
> -I/<>/src/algorithms/libs/opencl 
> -I/<>/src/algorithms/acquisition/libs 
> -I/<>/src/core/receiver 
> -I/<>/src/algorithms/channel/libs 
> -I/<>/src/core/system_parameters -isystem /usr/include/glog 
> -isystem 
> /<>/obj-x86_64-linux-gnu/volk_gnsssdr_module/build/include 
> -isystem 
> /<>/src/algorithms/libs/volk_gnsssdr_module/volk_gnsssdr/include 
>  -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
> -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
> -fvisibility=hidden -fvisibility-inlines-hidden   -Wall -Wextra -std=c++2a -o 
> CMakeFiles/acquisition_adapters.dir/galileo_e1_pcps_ambiguous_acquisition.cc.o
>  -c 
> /<>/src/algorithms/acquisition/adapters/galileo_e1_pcps_ambiguous_acquisition.cc
> make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
diff -Nru gnss-sdr-0.0.12/debian/changelog gnss-sdr-0.0.12/debian/changelog
--- gnss-sdr-0.0.12/debian/changelog2020-03-12 20:10:59.0 +0100
+++ gnss-sdr-0.0.12/debian/changelog2020-07-29 11:11:13.0 +0200
@@ -1,3 +1,11 @@
+gnss-sdr (0.0.12-1.1) unstable; urgency=medium
+
+  * debian/patches/76cce022ac51917242e5af905c2118669bec017e.patch:
+- cherry-pick and rebase upstream fix for gcc-10 build failure (Closes:
+  #957289)
+
+ -- Gianfranco Costamagna   Wed, 29 Jul 2020 
11:11:13 +0200
+
 gnss-sdr (0.0.12-1) unstable; urgency=medium
 
   * First release of upstream version 0.0.12
diff -Nru 
gnss-sdr-0.0.12/debian/patches/76cce022ac51917242e5af905c2118669bec017e.patch 
gnss-sdr-0.0.12/debian/patches/76cce022ac51917242e5af905c2118669bec017e.patch
--- 
gnss-sdr-0.0.12/debian/patches/76cce022ac51917242e5af905c2118669bec017e.patch   
1970-01-01 01:00:00.0 +0100
+++ 
gnss-sdr-0.0.12/debian/patches/76cce022ac51917242e5af905c2118669bec017e.patch   
2020-07-29 11:11:13.0 +0200
@@ -0,0 +1,79 @@
+From 76cce022ac51917242e5af905c2118669bec017e Mon Sep 17 00:00:00 2001
+From: Carles Fernandez 
+Date: Mon, 27 Jul 2020 09:53:01 +0200
+Subject: [PATCH] Fix building in Ubuntu 20.10
+
+---
+ .../adapters/osmosdr_signal_source.cc | 29 +--
+ 1 file changed, 14 insertions(+), 15 deletions(-)
+
+diff --git a/src/algorithms/signal_source/adapters/osmosdr_signal_source.cc 
b/src/algorithms/signal_source/adapters/osmosdr_signal_source.cc
+index b3c32a2bd..b62e8fc3a 100644
+--- a/src/algorithms/signal_source/adapters/osmosdr_signal_source.cc
 b/src/algorithms/signal_source/adapters/osmosdr_signal_source.cc
+@@ -22,7 +22,6 @@
+ #include "GPS_L1_CA.h"
+ #include "configuration_interface.h"
+ #include "gnss_sdr_valve

Bug#966483: iptables-netflow: sourcing of external scripts in dkms file?

[Gianfranco Costamagna]

Source: iptables-netflow
Version: 2.5-2
Severity: serious
tags: patch

Hello, looks like your dkms ship file is sourcing external stuff with 
pushd/popd and so on.
I don't think this is a sane idea, specially because in Debian we don't even 
use version.sh script to fill the dkms.conf file.

Can you please remove the two lines?

this is what we do to test dkms packages:
if ! dkms_conf=$(dpkg -L $pkg | grep '/usr/src' | grep '/dkms.conf$'); then
 echo "I: Package $pkg has no dkms.conf, skipping"
 return
fi
echo "I: Testing binary package $pkg"

dkms_pkg=$(bash -c ". $dkms_conf; echo \$PACKAGE_NAME" 2>/dev/null)
dkms_ver=$(bash -c ". $dkms_conf; echo \$PACKAGE_VERSION" 2>/dev/null)


bash -c ". dkms.conf; echo \$PACKAGE_NAME"
/tmp/iptables-netflow-2.5 /tmp/iptables-netflow-2.5
/tmp/iptables-netflow-2.5
ipt-netflow


I think dkms.conf files are meant to be sourced from outside, and launching 
scripts is a bad idea.

this is the trivial patch:

Description: Don't print useless stuff and change directory in dkms file, it is 
meant to be sourced from outside.

Author: Gianfranco Costamagna 
Bug-Debian: https://bugs.debian.org/-1
Last-Update: 2020-07-29

--- iptables-netflow-2.5.orig/dkms.conf
+++ iptables-netflow-2.5/dkms.conf
@@ -1,7 +1,5 @@
 PACKAGE_NAME="ipt-netflow"
-pushd `dirname $BASH_SOURCE`
 PACKAGE_VERSION=`./version.sh`
-popd
 BUILT_MODULE_NAME[0]=ipt_NETFLOW
 DEST_MODULE_LOCATION[0]=/kernel/extra
 STRIP[0]=no

Bug#966479: sysdig: broken support on 32 bit kernels?

[Gianfranco Costamagna]

Source: sysdig
Version: 0.26.7-2
Severity: serious
Forwarded: https://github.com/draios/sysdig/issues/1669

Hello, I don't know if this happens also in Debian, but there is no reason for 
it not happening there.

I asked upstream for help, this is what happens:
  CC [M]  /var/lib/dkms/sysdig/0.26.7/build/ppm_cputime.o
  LD [M]  /var/lib/dkms/sysdig/0.26.7/build/sysdig-probe.o
  Building modules, stage 2.
  MODPOST 1 modules
ERROR: "__aeabi_uldivmod" [/var/lib/dkms/sysdig/0.26.7/build/sysdig-probe.ko] 
undefined!
make[1]: *** [scripts/Makefile.modpost:94: __modpost] Error 1

thanks for having a look

Gianfranco

Bug#966417: vg: FTBFS in sid, with new elfutils

[Gianfranco Costamagna]

tags: patch
Hello,


I confirm the patch works correctly, the build finished in Ubuntu

https://launchpad.net/ubuntu/+source/vg/1.25.0+ds-2ubuntu1/+build/19650765

G.

Bug#966417: vg: FTBFS in sid, with new elfutils

[Gianfranco Costamagna]

Source: vg
Version: 1.25.0+ds-2
Severity: serious

Hello, looks like elfutils dropped one library used by vg:

# We do not provide a libebl anymore, use libdw instead.
rm -f debian/tmp/usr/include/elfutils/libebl.h


causing now FTBFS in sid:
. ./source_me.sh && g++ -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now 
-I/usr/include/fastahack -I/<>/vg-1.25.0+ds/include -I. 
-I/<>/vg-1.25.0+ds/src -I/<>/vg-1.25.0+ds/src/unittest 
-I/<>/vg-1.25.0+ds/src/subcommand 
-I/<>/vg-1.25.0+ds/include/dynamic -I/usr/include/cairo 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 
-I/usr/include/libpng16 -I/usr/include/smithwaterman -I/usr/include/vcflib 
-I/usr/include/smithwaterman -I/usr/include/fastahack -Wdate-time 
-D_FORTIFY_SOURCE=2 -O3 -Werror=return-type -std=c++14 -ggdb -g -MMD -MP -g -O2 
-fdebug-prefix-map=/<>/vg-1.25.0+ds=. -fstack-protector-strong 
-Wformat -Werror=format-security -DSIMDE_ENABLE_OPENMP -fopenmp-simd -O3 
-msse4.1 -fopenmp -o test/build_graph test/build_graph.cpp -lvg 
-L/<>/vg-1.25.0+ds/lib /<>/vg-1.25.0+ds/lib/libvgio.a -lz 
-lgssw -lssw -lprotobuf -lsublinearLS -ldeflate -lpthread -ljansson -lncurses 
-lgcsa2 -lgbwtgraph -lgbwt -ldivsufsort -ldivsufsort64 -lraptor2 
-lpinchesandcacti -l3edgeconnected -lsonlib -lfml -llz4 -lstructures -lvw 
-lboost_program_options -lallreduce -lbdsg -lxg -lsdsl -lhandlegraph 
-lfastahack -lsmithwaterman -ldisorder -lvcflib -lsmithwaterman -ldisorder 
-lfastahack -lhts -ltabixpp -lcairo -ljansson -latomic -rdynamic -ldw -lelf 
-lebl -ldl -llzma -lrocksdb -lbz2 -ljemalloc 
/usr/bin/ld: cannot find -lebl


I don't know if this patch is enough to make it build correctly, it is still 
building here
diff -Nru vg-1.25.0+ds/debian/changelog vg-1.25.0+ds/debian/changelog
--- vg-1.25.0+ds/debian/changelog   2020-07-14 15:15:28.0 +0200
+++ vg-1.25.0+ds/debian/changelog   2020-07-28 12:11:33.0 +0200
@@ -1,3 +1,9 @@
+vg (1.25.0+ds-2.1) unstable; urgency=medium
+
+  * Fix build by not linking anymore libebl.a (Closes: #-1)
+
+ -- Gianfranco Costamagna   Tue, 28 Jul 2020 
12:11:33 +0200
+
 vg (1.25.0+ds-2) unstable; urgency=medium
 
   * Restrict architectures to build for. Closes: #964039.
diff -Nru vg-1.25.0+ds/debian/patches/use_packaged_elfutils 
vg-1.25.0+ds/debian/patches/use_packaged_elfutils
--- vg-1.25.0+ds/debian/patches/use_packaged_elfutils   2020-02-03 
13:26:00.0 +0100
+++ vg-1.25.0+ds/debian/patches/use_packaged_elfutils   2020-07-28 
12:11:25.0 +0200
@@ -7,7 +7,7 @@
  
  # We want to link against the elfutils libraries
 -LD_LIB_FLAGS += -ldwfl -ldw -ldwelf -lelf -lebl
-+LD_LIB_FLAGS += -ldw -lelf -lebl
++LD_LIB_FLAGS += -ldw -lelf
  
  # We get OpenMP the normal way, using whatever the compiler knows about
  CXXFLAGS += -fopenmp

Bug#966182: virtualbox FTBFS on amd64 with gsoap 2.8.104

[Gianfranco Costamagna]

control: forwarded -1 https://www.virtualbox.org/ticket/19634

On Fri, 24 Jul 2020 14:30:28 +0300 Adrian Bunk  wrote:
> Source: virtualbox
> Version: 6.1.12-dfsg-6
> Severity: serious
> Tags: ftbfs
> 
> https://buildd.debian.org/status/fetch.php?pkg=virtualbox=amd64=6.1.12-dfsg-6%2Bb1=1595581404=0
> 
> ...
> /<>/src/VBox/Main/webservice/vboxweb.cpp: In function ???void 
> doQueuesLoop()???:
> /<>/src/VBox/Main/webservice/vboxweb.cpp:947: error: expression 
> cannot be used as a function
>   947 | if (soap_socket_errno(soap.master) == SOAP_EINTR)
>   |
> kmk: *** [/usr/share/kBuild/footer-pass2-compiling-targets.kmk:277: 
> /<>/out/obj/vboxwebsrv/vboxweb.o] Error 1


will fix thanks

Bug#956822: xpra: FTBFS on armel and armhf

[Gianfranco Costamagna]

Hello,

> xpra failed to build on armel and armhf. See
> https://buildd.debian.org/status/fetch.php?pkg=xpra=armel=3.0.8%2Bdfsg1-1=1586872010=0

based on upstream suggestion, I removed the patch, and let the program do its 
job, by adding the dependencies on xorg and xvfb (this one can probably be 
installed just on arm)

I also added xvfb on debian/tests/control, and the autopkgtest went green also 
on armhf!

--- xpra-3.0.9+dfsg1/debian/changelog   2020-04-20 02:47:55.0 +0200
+++ xpra-3.0.9+dfsg1/debian/changelog   2020-07-21 18:49:46.0 +0200
@@ -1,3 +1,11 @@
+xpra (3.0.9+dfsg1-1.1) unstable; urgency=medium
+
+  * Add xorg and xvfb to build and test deps and comment xorg patch
+- This should help detection of the right backend on arm* and elsewhere.
+  see https://xpra.org/trac/ticket/2737 and Debian bug: #956822
+
+ -- Gianfranco Costamagna   Tue, 21 Jul 2020 
18:49:46 +0200
+
 xpra (3.0.9+dfsg1-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru xpra-3.0.9+dfsg1/debian/control xpra-3.0.9+dfsg1/debian/control
--- xpra-3.0.9+dfsg1/debian/control 2020-04-14 11:52:20.0 +0200
+++ xpra-3.0.9+dfsg1/debian/control 2020-07-21 18:49:46.0 +0200
@@ -28,6 +28,8 @@
 ,python3-all-dev
 ,python3-cairo-dev
 ,python-gi-dev
+,xorg
+,xvfb
 Rules-Requires-Root: no
 Homepage: http://xpra.org/
 Vcs-Git: https://salsa.debian.org/debian/xpra.git
diff -Nru xpra-3.0.9+dfsg1/debian/patches/series 
xpra-3.0.9+dfsg1/debian/patches/series
--- xpra-3.0.9+dfsg1/debian/patches/series  2020-03-26 11:08:09.0 
+0100
+++ xpra-3.0.9+dfsg1/debian/patches/series  2020-07-21 18:49:35.0 
+0200
@@ -1,7 +1,7 @@
 
 ## Fixes
 build-hurd.patch
-fix-xvfb-path.patch
+#fix-xvfb-path.patch
 
 ## Misc.
 buildinfo.patch
diff -Nru xpra-3.0.9+dfsg1/debian/tests/control 
xpra-3.0.9+dfsg1/debian/tests/control
--- xpra-3.0.9+dfsg1/debian/tests/control   2019-04-10 03:39:32.0 
+0200
+++ xpra-3.0.9+dfsg1/debian/tests/control   2020-07-21 18:49:46.0 
+0200
@@ -3,6 +3,6 @@
 #, isolation-container
 # ,isolation-machine
 # ,needs-recommends
-Depends: @ ,coreutils ,procps ,x11-apps ,x11-xserver-utils ,xauth
+Depends: @ ,coreutils ,procps ,x11-apps ,x11-xserver-utils ,xauth, xvfb
 # ,@builddeps@
 # ,x11-common


you can see autopkgtest results here
https://autopkgtest.ubuntu.com/packages/xpra/groovy/

I know adding xorg and xvfb is far from ideal, but I agree that the 
autodetection system that upstream
provides us should work, and eventually be fixed if something is not correct, 
rather than patching it manually
downstream.

I don't plan to NMU this change, because I still feel not too confident on it

G.

Bug#956822: xpra: FTBFS on armel and armhf

[Gianfranco Costamagna]

and this is the correct link
https://autopkgtest.ubuntu.com/packages/xpra

G.

Bug#963347: gst-plugins-ugly1.0: FTBFS: Can't locate Regexp/Assemble.pm in @INC

[Gianfranco Costamagna]

control: fixed -1 1.17.2-1

On Tue, 21 Jul 2020 15:54:47 +0200 Jonas Smedegaard  wrote:
> Package: cdbs
> Followup-For: Bug #963347
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> Control: affects -1 =
> Control: reassign -1 src:gst-plugins-ugly1.0 1.16.2-2
> 
> cdbs provides templates for packages to include.
> gst-plugins-ugly1.0 also build-depends on automake
> even though it is called through a cdbs template.
> 
> cdbs offers an optional mechanism to help resolve build-dependencies,
> but does not itself build-depend on the tools used in its templates.
> If that was the case, then cdbs would depend on openjdk and php-dev
> and cmake and a lot of other tools, which would not be helpful.
> 
> Concretely, src:gst-plugins-ugly1.0 uses the rules/utils.mk template
> and need to either a) declare needed build-dependencies (which indeed has
> changed over time¹), or supress unused parts (notably licensecheck),
> or stop include /usr/share/cdbs/1/rules/utils.mk.
> 
> Hope that helps,
> 

yep, it helped thanks!

in the meanwhile, the package in experimental moved to debhelper, so this bug 
is "fixed" in another way...

G.

Bug#963347: reassigning bug to src:cdbs

[Gianfranco Costamagna]

control: reassign -1 src:cdbs
control: affects -1 src:gst-plugins-ugly1.0
control: found -1 0.4.162

Hello, looks like the new cdbs is using features of libregexp-assemble-perl 
without having a runtime dependency on it.
This makes gst-plugins-ugly1.0 FTBFS with the following error:

>  debian/rules build
> CDBS WARNING:  copyright-check disabled - touch debian/copyright_hints to 
> enable.
> test -x debian/rules
> mkdir -p "."
> CDBS WARNING:DEB_DH_INSTALL_ARGS is deprecated since 0.4.85
> CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85
> CDBS WARNING:DEB_DH_BUILDDEB_ARGS is deprecated since 0.4.85
> 
> Scanning upstream source for new/changed copyright notices...
> 
> set -e; find -- * -type f -regextype posix-extended '!' -regex '^(.+\.(|)|)$' 
> -regex '^.+\.(|)$' -print0 | perl -0 /usr/lib/cdbs/license-miner
> Can't locate Regexp/Assemble.pm in @INC (you may need to install the 
> Regexp::Assemble module) (@INC contains: /etc/perl 
> /usr/local/lib/x86_64-linux-gnu/perl/5.30.3 /usr/local/share/perl/5.30.3 
> /usr/lib/x86_64-linux-gnu/perl5/5.30 /usr/share/perl5 
> /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.30 
> /usr/share/perl/5.30 /usr/local/lib/site_perl) at /usr/lib/cdbs/license-miner 
> line 13.
> BEGIN failed--compilation aborted at /usr/lib/cdbs/license-miner line 13.
> make: *** [/usr/share/cdbs/1/rules/utils.mk:143: debian/copyright_newhints] 
> Error 2

Bug#965926: botch: FTBFS in sid

[Gianfranco Costamagna]

Source: botch
Version: 0.22-4
Severity: serious

Hello, the same that happened to other ocaml packages is now happening to botch 
too.

If the omission is intentional or no other helper can take care of this 
consider adding the
paths to debian/not-installed.
   dh_dwz
dwz: debian/botch/usr/bin/botch-annotate-strong: DWARF version 0 unhandled
dwz: debian/botch/usr/bin/botch-bin2src: DWARF version 0 unhandled
dwz: debian/botch/usr/bin/botch-build-fixpoint: DWARF version 0 unhandled
dwz: debian/botch/usr/bin/botch-buildcheck-more-problems: DWARF version 0 
unhandled
dwz: debian/botch/usr/bin/botch-buildgraph2srcgraph: DWARF version 0 unhandled
dwz: debian/botch/usr/bin/botch-calculate-fas: DWARF version 0 unhandled
dwz: debian/botch/usr/bin/botch-clean-repository: DWARF version 0 unhandled
dwz: debian/botch/usr/bin/botch-collapse-srcgraph: DWARF version 0 unhandled
dwz: debian/botch/usr/bin/botch-create-graph: DWARF version 0 unhandled
dwz: debian/botch/usr/bin/botch-distcheck-more-problems: DWARF version 0 
unhandled
dwz: debian/botch/usr/bin/botch-find-fvs: DWARF version 0 unhandled
dwz: debian/botch/usr/bin/botch-optuniv: DWARF version 0 unhandled
dwz: debian/botch/usr/bin/botch-partial-order: DWARF version 0 unhandled
dwz: debian/botch/usr/bin/botch-print-stats: DWARF version 0 unhandled
dwz: debian/botch/usr/bin/botch-src2bin: DWARF version 0 unhandled
dwz: Too few files for multifile optimization
dh_dwz: error: dwz 
-mdebian/botch/usr/lib/debug/.dwz/x86_64-linux-gnu/botch.debug 
-M/usr/lib/debug/.dwz/x86_64-linux-gnu/botch.debug -- 
debian/botch/usr/bin/botch-annotate-strong debian/botch/usr/bin/botch-bin2src 
debian/botch/usr/bin/botch-build-fixpoint 
debian/botch/usr/bin/botch-buildcheck-more-problems 
debian/botch/usr/bin/botch-buildgraph2srcgraph 
debian/botch/usr/bin/botch-calculate-fas 
debian/botch/usr/bin/botch-clean-repository 
debian/botch/usr/bin/botch-collapse-srcgraph 
debian/botch/usr/bin/botch-create-graph 
debian/botch/usr/bin/botch-distcheck-more-problems 
debian/botch/usr/bin/botch-find-fvs debian/botch/usr/bin/botch-optuniv 
debian/botch/usr/bin/botch-partial-order debian/botch/usr/bin/botch-print-stats 
debian/botch/usr/bin/botch-src2bin returned exit code 1
make: *** [debian/rules:7: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2



I still don't understand if the problem is in binutils or somewhere else

G.

Bug#965372: ocaml-mccs: FTBFS in sid

[Gianfranco Costamagna]

sr/lib/x86_64-linux-gnu/blas/libblas.so to provide 
/usr/lib/x86_64-linux-gnu/libblas.so (libblas.so-x86_64-linux-gnu) in auto mode
Setting up librbio2:amd64 (1:5.7.2+dfsg-1) ...
Setting up libfile-stripnondeterminism-perl (1.9.0-1) ...
Setting up libamd2:amd64 (1:5.7.2+dfsg-1) ...
Setting up liblapack3:amd64 (3.9.0-2) ...
update-alternatives: using /usr/lib/x86_64-linux-gnu/lapack/liblapack.so.3 to 
provide /usr/lib/x86_64-linux-gnu/liblapack.so.3 
(liblapack.so.3-x86_64-linux-gnu) in auto mode
Setting up libncurses-dev:amd64 (6.2-1) ...
Setting up libgmp-dev:amd64 (2:6.2.0+dfsg-6) ...
Setting up libcolamd2:amd64 (1:5.7.2+dfsg-1) ...
Setting up libtool (2.4.6-14) ...
Setting up libfindlib-ocaml (1.8.1-1+b1) ...
Setting up m4 (1.4.18-4) ...
Setting up libcamd2:amd64 (1:5.7.2+dfsg-1) ...
Setting up libmongoose2:amd64 (1:5.7.2+dfsg-1) ...
Setting up libglpk40:amd64 (4.65-2) ...
Setting up ocaml-findlib (1.8.1-1+b1) ...
Setting up liblapack-dev:amd64 (3.9.0-2) ...
update-alternatives: using /usr/lib/x86_64-linux-gnu/lapack/liblapack.so to 
provide /usr/lib/x86_64-linux-gnu/liblapack.so (liblapack.so-x86_64-linux-gnu) 
in auto mode
Setting up libcroco3:amd64 (0.6.13-1) ...
Setting up autoconf (2.69-11.1) ...
Setting up dh-strip-nondeterminism (1.9.0-1) ...
Setting up dwz (0.13-5) ...
Setting up groff-base (1.22.4-5) ...
Setting up libklu1:amd64 (1:5.7.2+dfsg-1) ...
Setting up libccolamd2:amd64 (1:5.7.2+dfsg-1) ...
Setting up libncurses5-dev:amd64 (6.2-1) ...
Setting up libcholmod3:amd64 (1:5.7.2+dfsg-1) ...
Setting up automake (1:1.16.2-3) ...
update-alternatives: using /usr/bin/automake-1.16 to provide /usr/bin/automake 
(automake) in auto mode
Setting up libspqr2:amd64 (1:5.7.2+dfsg-1) ...
Setting up gettext (0.19.8.1-10) ...
Setting up man-db (2.9.3-2) ...
Building database of manual pages ...
Setting up intltool-debian (0.35.0+20060710.5) ...
Setting up libumfpack5:amd64 (1:5.7.2+dfsg-1) ...
Setting up libsuitesparse-dev:amd64 (1:5.7.2+dfsg-1) ...
Setting up po-debconf (1.0.21) ...
Setting up libglpk-dev:amd64 (4.65-2) ...
Setting up dh-autoreconf (19) ...
Setting up ocaml-interp (4.08.1-8) ...
Setting up ocaml-nox (4.08.1-8) ...
Setting up ocaml-compiler-libs (4.08.1-8) ...
Setting up debhelper (13.2) ...
Setting up libextlib-ocaml-dev (1.7.7-1) ...
Setting up libcudf-ocaml-dev (0.7-5+b3) ...
Processing triggers for libc-bin (2.31-1) ...
 -> Finished parsing the build-deps
I: Copying back the cached apt archive contents
I: new cache content 'libcxsparse3_1%3a5.7.2+dfsg-1_amd64.deb' added
I: new cache content 'libcholmod3_1%3a5.7.2+dfsg-1_amd64.deb' added
I: new cache content 'libklu1_1%3a5.7.2+dfsg-1_amd64.deb' added
I: new cache content 'libcudf-ocaml-dev_0.7-5+b3_amd64.deb' added
I: new cache content 'libmongoose2_1%3a5.7.2+dfsg-1_amd64.deb' added
I: new cache content 'libgfortran5_10.1.0-6_amd64.deb' added
I: new cache content 'liblapack-dev_3.9.0-2_amd64.deb' added
I: new cache content 'libextlib-ocaml_1.7.7-1_amd64.deb' added
I: new cache content 'libmetis5_5.1.0.dfsg-7_amd64.deb' added
I: new cache content 'libsuitesparse-dev_1%3a5.7.2+dfsg-1_amd64.deb' 
added
I: new cache content 'libcamd2_1%3a5.7.2+dfsg-1_amd64.deb' added
I: new cache content 'libldl2_1%3a5.7.2+dfsg-1_amd64.deb' added
I: new cache content 'libbtf1_1%3a5.7.2+dfsg-1_amd64.deb' added
I: new cache content 'libccolamd2_1%3a5.7.2+dfsg-1_amd64.deb' added
I: new cache content 'libcolamd2_1%3a5.7.2+dfsg-1_amd64.deb' added
I: new cache content 'libglpk-dev_4.65-2_amd64.deb' added
I: new cache content 'libextlib-ocaml-dev_1.7.7-1_amd64.deb' added
I: new cache content 'libblas3_3.9.0-2_amd64.deb' added
I: new cache content 'librbio2_1%3a5.7.2+dfsg-1_amd64.deb' added
I: new cache content 'libsuitesparseconfig5_1%3a5.7.2+dfsg-1_amd64.deb' 
added
I: new cache content 'ocaml-dune_2.1.3-2_amd64.deb' added
I: new cache content 'libglpk40_4.65-2_amd64.deb' added
I: new cache content 'liblapack3_3.9.0-2_amd64.deb' added
I: new cache content 'libblas-dev_3.9.0-2_amd64.deb' added
I: new cache content 'libspqr2_1%3a5.7.2+dfsg-1_amd64.deb' added
I: new cache content 'libgraphblas3_1%3a5.7.2+dfsg-1_amd64.deb' added
I: new cache content 'libamd2_1%3a5.7.2+dfsg-1_amd64.deb' added
I: new cache content 'libumfpack5_1%3a5.7.2+dfsg-1_amd64.deb' added
I: Building the package
I: Running cd /build/ocaml-mccs-1.1+11/ && env 
PATH="/usr/sbin:/usr/bin:/sbin:/bin" HOME="/nonexistent" dpkg-buildpackage -us 
-uc 
dpkg-buildpackage: info: source package ocaml-mccs
dpkg-buildpackage: info: source version 1.1+11-1build2
dpkg-buildpackage: info: source distribution groovy
dpkg-buildpackage: info: source changed by Gianfranco Costamagna 

 dpkg-source --before-build .
dpkg-buildpackage: info: host arch

Bug#964044: mrpt: FTBFS: test failure

[Gianfranco Costamagna]

On Fri, 17 Jul 2020 08:41:13 +0200 Gianfranco Costamagna 
 wrote:
> Hello again
> 
> I'm deleting the upload, looks like the new ftdi broke configure script.
> 
> see the attached build log
> 
> G.

reuploaded, I gave ftdi a patch, and an upload is coming shortly

G.

Bug#965177: libftdi: ships broken cmake file

[Gianfranco Costamagna]

Hello,

I'm attaching a tested patch that also adds a new autopkgtest that spots this 
kind of failures in the future.

(the diff fixes also #965175)

G.
diff -Nru libftdi1-1.5/debian/changelog libftdi1-1.5/debian/changelog
--- libftdi1-1.5/debian/changelog   2020-07-14 23:32:06.0 +0200
+++ libftdi1-1.5/debian/changelog   2020-07-17 08:57:55.0 +0200
@@ -1,3 +1,11 @@
+libftdi1 (1.5-4) unstable; urgency=medium
+
+  * Mark one symbol as optional, disappearing on ppc64el with -O3 (Closes: 
#965175)
+  * Add again the LIBDIR in rules file to make the cmake script happy (Closes: 
#965177)
+  * Add an autopkgtest to test cmake scripts
+
+ -- Gianfranco Costamagna   Fri, 17 Jul 2020 
08:57:55 +0200
+
 libftdi1 (1.5-3) unstable; urgency=medium
 
   * Redirect autopkgtests stderr output to stdout.
diff -Nru libftdi1-1.5/debian/libftdipp1-3.symbols 
libftdi1-1.5/debian/libftdipp1-3.symbols
--- libftdi1-1.5/debian/libftdipp1-3.symbols2020-06-27 14:53:49.0 
+0200
+++ libftdi1-1.5/debian/libftdipp1-3.symbols2020-07-17 08:57:46.0 
+0200
@@ -105,7 +105,7 @@
  _ZNK4Ftdi4List6rbeginEv@Base 1.5
  _ZNK4Ftdi7Context20get_usb_read_timeoutEv@Base 1.5
  _ZNK4Ftdi7Context21get_usb_write_timeoutEv@Base 1.5
- _ZNSt7__cxx1110_List_baseIN4Ftdi7ContextESaIS2_EE8_M_clearEv@Base 1.5
+ (optional)_ZNSt7__cxx1110_List_baseIN4Ftdi7ContextESaIS2_EE8_M_clearEv@Base 
1.5
  _ZTIN5boost6detail15sp_counted_baseE@Base 1.5
  _ZTIN5boost6detail17sp_counted_impl_pIN4Ftdi4List7PrivateEEE@Base 1.5
  _ZTIN5boost6detail17sp_counted_impl_pIN4Ftdi6Eeprom7PrivateEEE@Base 1.5
diff -Nru libftdi1-1.5/debian/rules libftdi1-1.5/debian/rules
--- libftdi1-1.5/debian/rules   2020-07-13 11:23:42.0 +0200
+++ libftdi1-1.5/debian/rules   2020-07-17 08:57:55.0 +0200
@@ -11,6 +11,7 @@
 override_dh_auto_configure:
dh_auto_configure --builddirectory=build-main -- \
-DBUILD_TESTS=ON \
+   -DCMAKE_INSTALL_LIBDIR="/usr/lib/$(DEB_HOST_MULTIARCH)" \
-DDOCUMENTATION:BOOL=ON \
-DEXAMPLES:BOOL=ON \
-DFTDIPP:BOOL=ON \
@@ -19,6 +20,7 @@
for v in $(PY3VERS) ; do \
dh_auto_configure --builddirectory=build-python$$v -- \
-DBUILD_TESTS=OFF \
+   -DCMAKE_INSTALL_LIBDIR="/usr/lib/$(DEB_HOST_MULTIARCH)" 
\
-DDOCUMENTATION:BOOL=OFF \
-DEXAMPLES:BOOL=OFF \
-DFTDIPP:BOOL=ON \
diff -Nru libftdi1-1.5/debian/tests/control libftdi1-1.5/debian/tests/control
--- libftdi1-1.5/debian/tests/control   2020-07-12 14:45:44.0 +0200
+++ libftdi1-1.5/debian/tests/control   2020-07-17 08:57:55.0 +0200
@@ -1,2 +1,5 @@
 Tests: test-libftdi1
 Depends: build-essential, libftdi1-dev, libboost-test-dev, pkg-config
+
+Tests: test-libftdi1-cmake
+Depends: build-essential, libftdi1-dev, libboost-test-dev, cmake
diff -Nru libftdi1-1.5/debian/tests/test-libftdi1-cmake 
libftdi1-1.5/debian/tests/test-libftdi1-cmake
--- libftdi1-1.5/debian/tests/test-libftdi1-cmake   1970-01-01 
01:00:00.0 +0100
+++ libftdi1-1.5/debian/tests/test-libftdi1-cmake   2020-07-17 
08:57:55.0 +0200
@@ -0,0 +1,38 @@
+#!/bin/sh
+
+set -e
+
+WORKDIR=$(mktemp -d)
+cat << EOF > $WORKDIR/CMakeLists.txt
+cmake_minimum_required(VERSION 3.16)
+project(test)
+find_package(LibFTDI1)
+
+message(STATUS "Include directories: " \${LIBFTDI_INCLUDE_DIRS})
+message(STATUS "Link directories: " \${LIBFTDI_LIBRARY_DIRS})
+message(STATUS "Libraries: " \${LIBFTDI_LIBRARIES})
+
+add_library(imp_ftdi INTERFACE IMPORTED)
+set_target_properties(imp_ftdi
+ PROPERTIES
+ INTERFACE_INCLUDE_DIRECTORIES "\${LIBFTDI_INCLUDE_DIRS}"
+ INTERFACE_LINK_DIRECTORIES "\${LIBFTDI_LIBRARY_DIRS}"
+ INTERFACE_LINK_LIBRARIES "\${LIBFTDI_LIBRARIES}"
+ )
+
+add_executable(test-libftdi1-cmake basic.cpp baudrate.cpp)
+include_directories("\${LIBFTDI_INCLUDE_DIRS}")
+target_link_libraries(test-libftdi1-cmake PRIVATE imp_ftdi 
boost_unit_test_framework)
+EOF
+
+trap "rm -rf $WORKDIR" 0 INT QUIT ABRT PIPE TERM
+
+cp test/basic.cpp test/baudrate.cpp $WORKDIR
+cd $WORKDIR
+cmake .
+make VERBOSE=1
+
+echo "build: OK"
+[ -x $WORKDIR/test-libftdi1-cmake ]
+$WORKDIR/test-libftdi1-cmake 2>&1
+echo "run: OK"

Bug#965177: libftdi: ships broken cmake file

[Gianfranco Costamagna]

Hello again:

This is an example of cmake test file that might help in the future detecting 
such issues:
(stolen and adapted from mrpt)

cat ../CMakeLists.txt 
cmake_minimum_required(VERSION 3.16)
project(test)
find_package(LibFTDI1)

message("Include directories: " ${LIBFTDI_INCLUDE_DIRS})
message("Link directories: " ${LIBFTDI_LIBRARY_DIRS})
message("Libraries: " ${LIBFTDI_LIBRARIES})

add_library(imp_ftdi INTERFACE IMPORTED)
set_target_properties(imp_ftdi
 PROPERTIES
 INTERFACE_INCLUDE_DIRECTORIES "${LIBFTDI_INCLUDE_DIRS}"
 INTERFACE_LINK_DIRECTORIES "${LIBFTDI_LIBRARY_DIRS}"
 INTERFACE_LINK_LIBRARIES "${LIBFTDI_LIBRARIES}"
 )

add_executable(main main.c)
target_link_libraries(main PRIVATE imp_ftdi)


$ cmake ..

Include directories: /usr/include/libftdi1
Link directories: lib/x86_64-linux-gnu
Libraries: ftdi1/usr/lib/x86_64-linux-gnu/libusb-1.0.so
-- Configuring done
CMake Error in CMakeLists.txt:
  Target "imp_ftdi" contains relative path in its INTERFACE_LINK_DIRECTORIES:

"lib/x86_64-linux-gnu"


CMake Error in CMakeLists.txt:
  Target "imp_ftdi" contains relative path in its INTERFACE_LINK_DIRECTORIES:

"lib/x86_64-linux-gnu"


-- Generating done
CMake Generate step failed.  Build files cannot be regenerated correctly.


and this is the patch that fixes the issue:

diff -Nru libftdi1-1.5/debian/changelog libftdi1-1.5/debian/changelog
--- libftdi1-1.5/debian/changelog   2020-07-17 08:57:55.0 +0200
+++ libftdi1-1.5/debian/changelog   2020-07-17 09:19:25.0 +0200
@@ -1,3 +1,9 @@
+libftdi1 (1.5-3.1) unstable; urgency=medium
+
+  * Add again the LIBDIR in rules file to make the cmake script happy (Closes: 
#-1)
+
+ -- Gianfranco Costamagna   Fri, 17 Jul 2020 
09:19:25 +0200
+
 libftdi1 (1.5-3ubuntu1) groovy; urgency=medium

   * Mark one symbol as optional, disappearing on ppc64el with -O3
diff -Nru libftdi1-1.5/debian/rules libftdi1-1.5/debian/rules
--- libftdi1-1.5/debian/rules   2020-07-13 11:23:42.0 +0200
+++ libftdi1-1.5/debian/rules   2020-07-17 09:19:25.0 +0200
@@ -11,6 +11,7 @@
 override_dh_auto_configure:
dh_auto_configure --builddirectory=build-main -- \
-DBUILD_TESTS=ON \
+   -DCMAKE_INSTALL_LIBDIR="/usr/lib/$(DEB_HOST_MULTIARCH)" \
-DDOCUMENTATION:BOOL=ON \
-DEXAMPLES:BOOL=ON \
-DFTDIPP:BOOL=ON \
@@ -19,6 +20,7 @@
for v in $(PY3VERS) ; do \
dh_auto_configure --builddirectory=build-python$$v -- \
-DBUILD_TESTS=OFF \
+   -DCMAKE_INSTALL_LIBDIR="/usr/lib/$(DEB_HOST_MULTIARCH)" 
\
-DDOCUMENTATION:BOOL=OFF \
-DEXAMPLES:BOOL=OFF \
-DFTDIPP:BOOL=ON \

Bug#964044: mrpt: FTBFS: test failure

[Gianfranco Costamagna]

Hello,

> which is not yet released as 2.0.5, and which you can include as a
> patch if you want to go on with the ros-geometry2 transition.
> 

Since you are the maintainer, I'm uploading in deferred/1 your patch, refreshed 
in some parts to apply to 
the current 2.0.4 (and removing the rules part, since we can't patch with quilt 
debian directory)

I'm attaching the diff that will go in unstable in ~24h

I didn't use NMU as notation, but a "team upload" since the patch comes from 
you :)

let me know if this is good, so I can speed it up and let it go in sid today!

G.
diff -Nru mrpt-2.0.4/debian/changelog mrpt-2.0.4/debian/changelog
--- mrpt-2.0.4/debian/changelog 2020-06-20 17:24:00.0 +0200
+++ mrpt-2.0.4/debian/changelog 2020-07-17 08:14:20.0 +0200
@@ -1,3 +1,11 @@
+mrpt (1:2.0.4-2) unstable; urgency=medium
+
+  * Team upload
+  * debian/patches/e84511500276d38d3eeff0b220e8d45e0d74fc93.patch:
+- cherry-pick upstream "fix" for a failing test (Closes: #964044).
+
+ -- Gianfranco Costamagna   Fri, 17 Jul 2020 
08:14:20 +0200
+
 mrpt (1:2.0.4-1) unstable; urgency=medium
 
   * New version of upstream sources.
diff -Nru 
mrpt-2.0.4/debian/patches/e84511500276d38d3eeff0b220e8d45e0d74fc93.patch 
mrpt-2.0.4/debian/patches/e84511500276d38d3eeff0b220e8d45e0d74fc93.patch
--- mrpt-2.0.4/debian/patches/e84511500276d38d3eeff0b220e8d45e0d74fc93.patch
1970-01-01 01:00:00.0 +0100
+++ mrpt-2.0.4/debian/patches/e84511500276d38d3eeff0b220e8d45e0d74fc93.patch
2020-07-17 08:14:20.0 +0200
@@ -0,0 +1,55 @@
+From e84511500276d38d3eeff0b220e8d45e0d74fc93 Mon Sep 17 00:00:00 2001
+From: Jose Luis Blanco Claraco 
+Date: Thu, 2 Jul 2020 23:53:34 +0200
+Subject: [PATCH] give up with the problematic unit test if building a Debian
+ package
+
+---
+ doc/doxygen-pages/changeLog_doc.h   |  4 
+ libs/apps/src/RawlogGrabberApp_unittest.cpp | 10 ++
+ packaging/debian/rules  |  2 ++
+ 3 files changed, 16 insertions(+)
+
+Index: mrpt-2.0.4/doc/doxygen-pages/changeLog_doc.h
+===
+--- mrpt-2.0.4.orig/doc/doxygen-pages/changeLog_doc.h
 mrpt-2.0.4/doc/doxygen-pages/changeLog_doc.h
+@@ -47,6 +47,10 @@
+ - Fix: mrpt::maps::CPointsMapXYZI::setFromPCLPointCloudXYZI() was using a 
non-existing method.
+ - Fix: mrpt::nav::PlannerSimple2D did not honored maximum path length 
correctly.
+ - Fix race condition in CGenericCamera_AVI unit test.
++- Deprecations:
++  - mrpt::system::TParameters is now deprecated.
++- BUG FIXES:
++  - Avoid crash in camera-calib app when clicking "Close" while capturing a 
live video.
+ 
+ --
+ # Version 2.0.3: Released May 13, 2020
+Index: mrpt-2.0.4/libs/apps/src/RawlogGrabberApp_unittest.cpp
+===
+--- mrpt-2.0.4.orig/libs/apps/src/RawlogGrabberApp_unittest.cpp
 mrpt-2.0.4/libs/apps/src/RawlogGrabberApp_unittest.cpp
+@@ -13,6 +13,7 @@
+ #include 
+ #include 
+ #include 
++#include 
+ #include 
+ 
+ #if MRPT_HAS_FFMPEG && MRPT_HAS_OPENCV
+@@ -21,6 +22,15 @@
+ TEST(RawlogGrabberApp, DISABLED_CGenericCamera_AVI)
+ #endif
+ {
++  // This particular unit test is REALLY problematic for some reason on 
build
++  // farms. It's safer to just disable it in this case:
++  if (::getenv("DEB_BUILD_ARCH") || ::getenv("DEB_BUILD_MAINT_OPTIONS"))
++  {
++  std::cerr << "Warning: Disabling test since we are building a 
Debian "
++   "package.\n";
++  return;
++  }
++
+   using namespace std::string_literals;
+ 
+   const std::string ini_fil =
diff -Nru mrpt-2.0.4/debian/patches/series mrpt-2.0.4/debian/patches/series
--- mrpt-2.0.4/debian/patches/series2020-06-20 17:24:00.0 +0200
+++ mrpt-2.0.4/debian/patches/series2020-07-17 08:14:20.0 +0200
@@ -1 +1,2 @@
 fix-inconsistent-appstream-metadata-license.diff
+e84511500276d38d3eeff0b220e8d45e0d74fc93.patch
diff -Nru mrpt-2.0.4/debian/rules mrpt-2.0.4/debian/rules
--- mrpt-2.0.4/debian/rules 2020-06-20 17:24:00.0 +0200
+++ mrpt-2.0.4/debian/rules 2020-07-17 08:14:20.0 +0200
@@ -68,6 +68,8 @@
# Show CPU flags, to help debugging unit test crashes related to
# illegal instructions, etc.
cat /proc/cpuinfo
+   # Show env vars for debugging:
+   env
# Autoconfigure step:
dh_auto_configure -- $(CMAKE_FLAGS)
 

Bug#965033: debdiff

[Gianfranco Costamagna]

and looking at the commit ids, the responsible might be this commit
https://github.com/mesonbuild/meson/commit/57b468c75ae90e09f8bd98da12a5c420ab49cd79

(not sure if only that one)


G.

Bug#965033: debdiff

[Gianfranco Costamagna]

Hello again,

On Wed, 15 Jul 2020 17:02:36 -0700 Kunal Mehta  wrote:
> I'm happy to NMU this since it's affecting some of my packages (zimlib,
> libkiwix, zim-tools, etc.). debdiff is attached.
> 
> It's not clear to me why the dependency was commented out in the first
> place, but it fixes the immediate issue. Let me know if that's OK and if
> you'd like me to go ahead.
> 
this is probably the rationale for it
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909440

G.

Bug#965033: debdiff

[Gianfranco Costamagna]

Hello,
On Wed, 15 Jul 2020 17:02:36 -0700 Kunal Mehta  wrote:
> I'm happy to NMU this since it's affecting some of my packages (zimlib,
> libkiwix, zim-tools, etc.). debdiff is attached.
> 
> It's not clear to me why the dependency was commented out in the first
> place, but it fixes the immediate issue. Let me know if that's OK and if
> you'd like me to go ahead.
> 

I'm not the maintainer, but in case you want to NMU, please add also this patch:
from the other RC bug
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963546#50

diff -Nru meson-0.55.0/debian/tests/control meson-0.55.0/debian/tests/control
--- meson-0.55.0/debian/tests/control   2020-07-12 16:29:07.0 +0200
+++ meson-0.55.0/debian/tests/control   2020-07-14 13:06:32.0 +0200
@@ -12,4 +12,4 @@
 Depends: meson, @builddeps@, valac, rustc, ldc [!s390x !ppc64el]
 
 Tests: crossbuild
-Depends: meson, g++, g++-arm-linux-gnueabihf
+Depends: meson, g++, g++-arm-linux-gnueabihf [!s390x]


thanks!

G.

Bug#964044: mrpt: FTBFS: test failure

[Gianfranco Costamagna]

Hello,

On Mon, 13 Jul 2020 21:20:41 +0200 Sebastian Ramacher  
wrote:
> On 2020-06-30 22:37:57 +0200, Sebastian Ramacher wrote:
> > Source: mrpt
> > Version: 1:2.0.4-1
> > Severity: serious
> > Tags: ftbfs
> > Justification: fails to build from source (but built successfully in the 
> > past)
> > 
> > binNMUs of mrpt failed to build:
> > | [--] 1 test from RawlogGrabberApp
> > | [ RUN  ] RawlogGrabberApp.CGenericCamera_AVI
> > | [CCameraSensor::initialize] Opening camera...
> > | [CCameraSensor::initialize] FFmpeg stream: 
> > /<>/share/mrpt/datasets/dummy_video.avi...
> > | [CCameraSensor::initialize] Done!
> > | Rawlog grabbed objects: 1
> > | /<>/libs/apps/src/RawlogGrabberApp_unittest.cpp:94: Failure
> > | Expected: (app.rawlog_saved_objects) >= (REQUIRED_GRAB_OBS), actual: 1 vs 
> > 3
> > | [  FAILED  ] RawlogGrabberApp.CGenericCamera_AVI (1511 ms)
> > | [--] 1 test from RawlogGrabberApp (1511 ms total)
> > 
> > See
> > https://buildd.debian.org/status/fetch.php?pkg=mrpt=amd64=1%3A2.0.4-1%2Bb1=1593549279=0
> > for example
> 
> This issue has been fixed upstream:
> https://github.com/MRPT/mrpt/commit/15234dc335c2413e3fd41021f7511f1d36fe915b.
> Could you please apply the fix to the Debian package so that
> ros-geometry2 transition can be completed? Thanks


looks like that commit is already part of 2.0.4?

G.

> 
> Cheers
> -- 
> Sebastian Ramacher

Bug#965115: extlib: FTBFS in sid (dh_dwz failure)

[Gianfranco Costamagna]

control: affects -1 ocaml-mccs


for some reasons, the new binutils changed the dwarf version from 2 to 0
(I tested on stretch, upgraded dwz and binutils to bullseye and reproduced the 
issue)

readelf --debug-dump=info src/extLib.cmxs | grep -A 2 'Compilation Unit @'
readelf: Warning: CU at offset 0 contains corrupt or unsupported version 
number: 0.
readelf: Warning: CU at offset 2e contains corrupt or unsupported version 
number: 0.
readelf: Warning: CU at offset 5c contains corrupt or unsupported version 
number: 0.
readelf: Warning: CU at offset 8a contains corrupt or unsupported version 
number: 0.
readelf: Warning: CU at offset b8 contains corrupt or unsupported version 
number: 0.
readelf: Warning: CU at offset e6 contains corrupt or unsupported version 
number: 0.
readelf: Warning: CU at offset 114 contains corrupt or unsupported version 
number: 0.
readelf: Warning: CU at offset 142 contains corrupt or unsupported version 
number: 0.
readelf: Warning: CU at offset 170 contains corrupt or unsupported version 
number: 0.
readelf: Warning: CU at offset 19e contains corrupt or unsupported version 
number: 0.
readelf: Warning: CU at offset 1cc contains corrupt or unsupported version 
number: 0.
readelf: Warning: CU at offset 1fa contains corrupt or unsupported version 
number: 0.
readelf: Warning: CU at offset 228 contains corrupt or unsupported version 
number: 0.
readelf: Warning: CU at offset 256 contains corrupt or unsupported version 
number: 0.
readelf: Warning: CU at offset 284 contains corrupt or unsupported version 
number: 0.
readelf: Warning: CU at offset 2b2 contains corrupt or unsupported version 
number: 0.
readelf: Warning: CU at offset 2e0 contains corrupt or unsupported version 
number: 0.
readelf: Warning: CU at offset 30e contains corrupt or unsupported version 
number: 0.
readelf: Warning: CU at offset 33c contains corrupt or unsupported version 
number: 0.
readelf: Warning: CU at offset 36a contains corrupt or unsupported version 
number: 0.
readelf: Warning: CU at offset 398 contains corrupt or unsupported version 
number: 0.
readelf: Warning: CU at offset 3c6 contains corrupt or unsupported version 
number: 0.
readelf: Warning: CU at offset 0 contains corrupt or unsupported version 
number: 0.
readelf: Warning: CU at offset 2e contains corrupt or unsupported version 
number: 0.
readelf: Warning: CU at offset 5c contains corrupt or unsupported version 
number: 0.
readelf: Warning:   Compilation Unit @ offset 0x0:
CU at offset 8a contains corrupt or unsupported version number: 0.
   Length:0x2a (32-bit)
   Version:   0
readelf: Warning: --
CU at offset b8 contains corrupt or unsupported version number: 0.
  Compilation Unit @ offset 0x2e:
   Length:0x2a (32-bit)
readelf: Warning:Version:   0
CU at offset e6 contains corrupt or unsupported version number: 0.
--
  Compilation Unit @ offset 0x5c:
readelf: Warning:Length:0x2a (32-bit)

Bug#965115: extlib: FTBFS in sid (dh_dwz failure)

[Gianfranco Costamagna]

Source: extlib
Version: 1.7.7-1
Severity: serious

Hello, as you can see in the attached build log, the package now FTBFS.

Honestly I don't know if the error
dwz: debian/libextlib-ocaml/usr/lib/ocaml/extlib/extLib.cmxs: DWARF version 0 
unhandled
dh_dwz: error: dwz -- debian/libextlib-ocaml/usr/lib/ocaml/extlib/extLib.cmxs 
returned exit code 1

is a fault on dwz or extlib, this is why I'm ccing doko, please reassign to 
binutils/dwz or whenever you think its
more appropriate

thanks

G.
D: cmdline: build --distribution sid --buildresult 
/home/locutus/pbuilder/sid_result --basetgz /home/locutus/pbuilder/sid-base.tgz 
--logfile /home/locutus/pbuilder/sid_result/extlib_1.7.7-1_amd64.build --mirror 
http://deb.debian.org/debian --debootstrapopts 
--keyring=/usr/share/keyrings/debian-archive-keyring.gpg --aptcache 
/home/locutus/pbuilder/aptcache/debian --components main contrib non-free 
extlib_1.7.7-1.dsc
W: cgroups are not available on the host, not using them.
I: pbuilder: network access will be disabled during build
I: Current time: Thu Jul 16 12:53:15 CEST 2020
I: pbuilder-time-stamp: 1594896795
I: Building the build Environment
I: extracting base tarball [/home/locutus/pbuilder/sid-base.tgz]
I: copying local configuration
W: No local /etc/mailname to copy, relying on 
/tmp/build/11969/etc/mailname to be correct
W: --override-config is not set; not updating apt.conf Read the manpage 
for details.
I: mounting /proc filesystem
I: mounting /sys filesystem
I: creating /{dev,run}/shm
I: mounting /dev/pts filesystem
I: redirecting /dev/ptmx to /dev/pts/ptmx
I: policy-rc.d already exists
I: Obtaining the cached apt archive contents
I: Copying source file
I: copying [extlib_1.7.7-1.dsc]
I: copying [./extlib_1.7.7.orig.tar.gz]
I: copying [./extlib_1.7.7-1.debian.tar.xz]
I: Extracting source
gpgv: unknown type of key resource 'trustedkeys.kbx'
gpgv: keyblock resource '/tmp/dpkg-verify-sig.TYiqKJZL/trustedkeys.kbx': 
General error
gpgv: Signature made Tue May 19 06:38:02 2020 UTC
gpgv:using RSA key 6DE24E97ECA886CC56E6250E21B8EEF1B1893081
gpgv:issuer "glo...@debian.org"
gpgv: Can't check signature: No public key
dpkg-source: warning: failed to verify signature on ./extlib_1.7.7-1.dsc
dpkg-source: info: extracting extlib in extlib-1.7.7
dpkg-source: info: unpacking extlib_1.7.7.orig.tar.gz
dpkg-source: info: unpacking extlib_1.7.7-1.debian.tar.xz
I: Not using root during the build.
I: Installing the build-deps
 -> Attempting to parse the build-deps
 -> Considering build-depdebhelper-compat (= 12)
   -> Trying to add debhelper-compat=12
   -> Loop detected, last APT error was: ==
Reading package lists...
Building dependency tree...
Reading state information...
E: Version '12' for 'debhelper-compat' was not found
   -> =
   -> (not adding  to debhelper-compat=12)
   -> Cannot install debhelper-compat=12; apt errors follow:
Reading package lists...
Building dependency tree...
Reading state information...
E: Version '12' for 'debhelper-compat' was not found
 -> Considering debhelper to satisfy the dependency 
 -> Considering build-dep ocaml-nox
   -> Trying to add ocaml-nox
 -> Considering build-dep cppo
   -> Trying to add cppo
 -> Considering build-dep ocaml-findlib
   -> Trying to add ocaml-findlib
 -> Considering build-dep libfindlib-ocaml-dev
   -> Trying to add libfindlib-ocaml-dev
 -> Considering build-dep dh-ocaml
   -> Trying to add dh-ocaml
 -> Installing  debhelper ocaml-nox cppo ocaml-findlib libfindlib-ocaml-dev 
dh-ocaml
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
  autoconf automake autopoint autotools-dev bsdextrautils dh-autoreconf
  dh-strip-nondeterminism dwz file gettext gettext-base groff-base
  intltool-debian libarchive-zip-perl libcroco3 libdebhelper-perl libelf1
  libfile-stripnondeterminism-perl libfindlib-ocaml libglib2.0-0 libicu67
  libmagic-mgc libmagic1 libncurses-dev libncurses5-dev libncurses6
  libpipeline1 libsigsegv2 libsub-override-perl libtool libuchardet0 libxml2
  m4 man-db ocaml-base-nox ocaml-compiler-libs ocaml-interp po-debconf
  sensible-utils
Suggested packages:
  autoconf-archive gnu-standards autoconf-doc dh-make git gettext-doc
  libasprintf-dev libgettextpo-dev groff ncurses-doc libtool-doc gfortran
  | fortran95-compiler gcj-jdk m4-doc apparmor less www-browser camlp4
  ocaml-doc tuareg-mode libmail-box-perl
Recommended packages:
  curl | wget | lynx libarchive-cpio-perl libglib2.0-data shared-mime-info
  xdg-user-dirs libgpm2 libltdl-dev ocaml-man ledit | readline-editor
  libmail-sendmail-perl
The following NEW packages will be installed:
  autoconf automake autopoint autotools-dev 

Bug#964680: ibus-pinyin: FTBFS: lmyoslib.c:68:36: error: expected ‘)’ before ‘LUA_QS’

[Gianfranco Costamagna]

control: tags -1 patch pending

Hello, I uploaded in deferred/5 the following debdiff (and submitted upstream)
Feel free to cancel/reschedule as you wish.

diff -Nru ibus-pinyin-1.5.0/debian/changelog ibus-pinyin-1.5.0/debian/changelog
--- ibus-pinyin-1.5.0/debian/changelog  2019-12-07 21:11:35.0 +0100
+++ ibus-pinyin-1.5.0/debian/changelog  2020-07-15 11:26:32.0 +0200
@@ -1,3 +1,11 @@
+ibus-pinyin (1.5.0-6.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix lua compatibility issue due to deprecated LUA_QS macro.
+(Closes: #964680)
+
+ -- Gianfranco Costamagna   Wed, 15 Jul 2020 
11:26:32 +0200
+
 ibus-pinyin (1.5.0-6) unstable; urgency=medium

   * Team upload.
diff -Nru ibus-pinyin-1.5.0/debian/patches/lua-5.4.patch 
ibus-pinyin-1.5.0/debian/patches/lua-5.4.patch
--- ibus-pinyin-1.5.0/debian/patches/lua-5.4.patch  1970-01-01 
01:00:00.0 +0100
+++ ibus-pinyin-1.5.0/debian/patches/lua-5.4.patch  2020-07-15 
11:26:30.0 +0200
@@ -0,0 +1,19 @@
+Description: Fix lua 5.4 compatibility, due to deprecated LUA_QS macro
+See: 
https://polyrex.io/polyrex/dependencies/lua/-/commit/f97c64d7bf4c0f373711795d8faba0e8cd206761
+For reference.
+Author: Gianfranco Costamagna 
+Bug-Debian: https://bugs.debian.org/964680
+Forwarded: https://github.com/phuang/ibus-pinyin/pull/18
+Last-Update: 2020-07-15
+
+--- ibus-pinyin-1.5.0.orig/lua/lmyoslib.c
 ibus-pinyin-1.5.0/lua/lmyoslib.c
+@@ -65,7 +65,7 @@ static int getfield (lua_State *L, const
+ res = (int)lua_tointeger(L, -1);
+   else {
+ if (d < 0)
+-  return luaL_error(L, "field " LUA_QS " missing in date table", key);
++  return luaL_error(L, "field '%s' missing in date table", key);
+ res = d;
+   }
+   lua_pop(L, 1);
diff -Nru ibus-pinyin-1.5.0/debian/patches/series 
ibus-pinyin-1.5.0/debian/patches/series
--- ibus-pinyin-1.5.0/debian/patches/series 2019-12-07 21:11:35.0 
+0100
+++ ibus-pinyin-1.5.0/debian/patches/series 2020-07-15 11:23:29.0 
+0200
@@ -14,3 +14,4 @@

 # python3 support
 python3.patch
+lua-5.4.patch

Bug#965014: bsdmainutils: binaries uploaded

[Gianfranco Costamagna]

Source: bsdmainutils
Version: 12.1.4
Severity: serious
Justification: can't migrate per Britney policy.

Hello, thanks for fixing the bsdmainutils RC bugs, but without a source-only 
upload, the package
won't ever migrate to testing.
In specific, the arch:all packages can't be binNMUed, so please reupload if you 
want the fix to go in testing.

thanks!

Gianfranco

Bug#963546: fixed in meson 0.55.0-1

[Gianfranco Costamagna]

control: reopen -1
control: notfixed -1 0.55.0-1
control: notfixed -1 0.55.0~rc2-1

Hello, looks like there is still one tweak needed?

+meson (0.55.0-2) unstable; urgency=medium
+
+  * Don't require armhf tools on s390x (Closes: #963546)
+
+ -- Gianfranco Costamagna   Tue, 14 Jul 2020 
13:06:33 +0200
+
 meson (0.55.0-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru meson-0.55.0/debian/tests/control meson-0.55.0/debian/tests/control
--- meson-0.55.0/debian/tests/control   2020-07-12 16:29:07.0 +0200
+++ meson-0.55.0/debian/tests/control   2020-07-14 13:06:32.0 +0200
@@ -12,4 +12,4 @@
 Depends: meson, @builddeps@, valac, rustc, ldc [!s390x !ppc64el]
 
 Tests: crossbuild
-Depends: meson, g++, g++-arm-linux-gnueabihf
+Depends: meson, g++, g++-arm-linux-gnueabihf [!s390x]


this is the failure:
Reading package lists...
Building dependency tree...
Reading state information...
Package g++-arm-linux-gnueabihf is not available, but is referred to by another 
package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'g++-arm-linux-gnueabihf' has no installation candidate
crossbuild   FAIL badpkg
blame: meson
badpkg: Test dependencies are unsatisfiable. A common reason is that your 
testbed is out of date with respect to the archive, and you need to use a 
current testbed or run apt-get update or use -U.
autopkgtest [09:26:49]:  summary
basicmeson   PASS
clangmeson   PASS
exhaustive   PASS
crossbuild   FAIL badpkg


thanks for fixing everything else!

(I'm still testing the patch right now, but I presume it should be good)

Gianfranco