Processed: fixed 935669 in 1.2.0.2.1-1

[Debian Bug Tracking System]

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

> fixed 935669 1.2.0.2.1-1
Bug #935669 [assaultcube-data] assaultcube-data: Outdated version makes 
assaultcube uninstallable
There is no source info for the package 'assaultcube-data' at version 
'1.2.0.2.1-1' with architecture ''
Unable to make a source version for version '1.2.0.2.1-1'
Marked as fixed in versions 1.2.0.2.1-1.
> thanks
Stopping processing here.

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

Bug#951921: vdr-plugin-xineliboutput: diff for NMU version 2.1.0+git20191101-1.1

[Adrian Bunk]

Control: tags 951921 + patch
Control: tags 951921 + pending

Dear maintainer,

I've prepared an NMU for vdr-plugin-xineliboutput (versioned as 
2.1.0+git20191101-1.1) and uploaded it to DELAYED/1. Please feel
free to tell me if I should cancel it.

cu
Adrian
diff -Nru vdr-plugin-xineliboutput-2.1.0+git20191101/debian/changelog vdr-plugin-xineliboutput-2.1.0+git20191101/debian/changelog
--- vdr-plugin-xineliboutput-2.1.0+git20191101/debian/changelog	2019-11-01 16:36:57.0 +0200
+++ vdr-plugin-xineliboutput-2.1.0+git20191101/debian/changelog	2021-02-05 09:21:31.0 +0200
@@ -1,3 +1,10 @@
+vdr-plugin-xineliboutput (2.1.0+git20191101-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Backport upstream fix for GLX FTBFS. (Closes: #951921)
+
+ -- Adrian Bunk   Fri, 05 Feb 2021 09:21:31 +0200
+
 vdr-plugin-xineliboutput (2.1.0+git20191101-1) unstable; urgency=medium
 
   * New Upstream Snapshot (commit 32a5ffc)
diff -Nru vdr-plugin-xineliboutput-2.1.0+git20191101/debian/patches/0001-configure-fix-GLX-check-when-using-pkg-config.patch vdr-plugin-xineliboutput-2.1.0+git20191101/debian/patches/0001-configure-fix-GLX-check-when-using-pkg-config.patch
--- vdr-plugin-xineliboutput-2.1.0+git20191101/debian/patches/0001-configure-fix-GLX-check-when-using-pkg-config.patch	1970-01-01 02:00:00.0 +0200
+++ vdr-plugin-xineliboutput-2.1.0+git20191101/debian/patches/0001-configure-fix-GLX-check-when-using-pkg-config.patch	2021-02-05 09:17:14.0 +0200
@@ -0,0 +1,42 @@
+From 21df3eed9745333c19f175b707df7da0963391c5 Mon Sep 17 00:00:00 2001
+From: Petri Hintukainen 
+Date: Thu, 2 Jul 2020 21:48:36 +0300
+Subject: configure: fix GLX check (when using pkg-config)
+
+---
+ configure | 5 -
+ 1 file changed, 4 insertions(+), 1 deletion(-)
+
+diff --git a/configure b/configure
+index b1138bb..1a443fd 100755
+--- a/configure
 b/configure
+@@ -238,6 +238,7 @@ FEATURES="
+   xrender
+   xshape
+   opengl
++  glx
+   pthread
+   dlfcn
+   vdpau
+@@ -345,6 +346,7 @@ check_deps(){
+   disabled vdr && disable libextractor libcap libbluray avahi-client
+   disabled dlfcn   && disable opengl
+   disabled pthread && disable opengl
++  disabled glx && disable opengl
+   disabled xrender && disable xshape xshm
+ }
+ 
+@@ -401,7 +403,8 @@ if enabled libxine; then
+ test_library X11  xshape   "X11/extensions/shape.h""-lXext"  "XShapeQueryExtension(0,0,0)"
+ test_library X11  xdpms"X11/extensions/dpms.h" "-lXext"  "DPMSDisable(0)"
+ test_library X11  xinerama "X11/extensions/Xinerama.h" "-lXinerama"  "XineramaQueryScreens(0,0)"
+-test_library X11  opengl   "GL/glx.h"  "-lGL -lGLU"  "glXQueryVersion(0,0,0)"
++test_library X11  opengl   "GL/gl.h"   "-lGL -lGLU"  "glTexCoord2f(0.0,0.0)"
++test_library X11  glx  "GL/glx.h"  "-lGLX"   "glXQueryVersion(0,0,0)"
+ test_library none vdpau"vdpau/vdpau_x11.h" "-lvdpau" "vdp_device_create_x11(0,0,0,0)"
+ test_library X11  dbus-glib-1  \
+   "dbus/dbus-glib.h" \
+-- 
+2.20.1
+
diff -Nru vdr-plugin-xineliboutput-2.1.0+git20191101/debian/patches/series vdr-plugin-xineliboutput-2.1.0+git20191101/debian/patches/series
--- vdr-plugin-xineliboutput-2.1.0+git20191101/debian/patches/series	2019-11-01 16:36:57.0 +0200
+++ vdr-plugin-xineliboutput-2.1.0+git20191101/debian/patches/series	2021-02-05 09:21:30.0 +0200
@@ -1 +1,2 @@
 disable-po-update.patch
+0001-configure-fix-GLX-check-when-using-pkg-config.patch

Processed: vdr-plugin-xineliboutput: diff for NMU version 2.1.0+git20191101-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 951921 + patch
Bug #951921 [src:vdr-plugin-xineliboutput] vdr-plugin-xineliboutput: FTBFS: 
xine_sxfe_frontend.c:1873: undefined reference to `glXQueryExtensionsString'
Added tag(s) patch.
> tags 951921 + pending
Bug #951921 [src:vdr-plugin-xineliboutput] vdr-plugin-xineliboutput: FTBFS: 
xine_sxfe_frontend.c:1873: undefined reference to `glXQueryExtensionsString'
Added tag(s) pending.

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

Bug#981835: ugly workaround

[Petko Angelov]

I was in the same situation this morning but this help me to install the
libelf1:i386

/sudo mv /usr/share/locale/en@quot/LC_MESSAGES/elfutils.mo
/usr/share/locale/en@quot/LC_MESSAGES/elfutils.mo-back //
/

Bug#981889: marked as done (nomad: CVE-2021-3283)

[Debian Bug Tracking System]

Your message dated Fri, 05 Feb 2021 05:48:55 +
with message-id 
and subject line Bug#981889: fixed in nomad 0.12.10+dfsg1-1
has caused the Debian Bug report #981889,
regarding nomad: CVE-2021-3283
to be marked as done.

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

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


-- 
981889: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981889
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nomad
Version: 0.12.9+dfsg1-3
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for nomad.

CVE-2021-3283[0]:
| HashiCorp Nomad and Nomad Enterprise up to 0.12.9 exec and java task
| drivers can access processes associated with other tasks on the same
| node. Fixed in 0.12.10, and 1.0.3.

Some details are in [1] and said to be fixed in 0.12.10 for nomad.


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2021-3283
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3283
[1] 
https://discuss.hashicorp.com/t/hcsec-2021-01-nomad-s-exec-and-java-task-drivers-did-not-isolate-processes/20332

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: nomad
Source-Version: 0.12.10+dfsg1-1
Done: Dmitry Smirnov 

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

Debian distribution maintenance software
pp.
Dmitry Smirnov  (supplier of updated nomad 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: Fri, 05 Feb 2021 16:14:14 +1100
Source: nomad
Architecture: source
Version: 0.12.10+dfsg1-1
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Smirnov 
Changed-By: Dmitry Smirnov 
Closes: 981889
Changes:
 nomad (0.12.10+dfsg1-1) unstable; urgency=medium
 .
   * New upstream release.
 + CVE-2021-3283: exec-based drivers to run tasks in private PID/IPC
   namespaces (Closes: #981889).
Checksums-Sha1:
 7aa24488f91e36811ccd787092e771b593bff335 7712 nomad_0.12.10+dfsg1-1.dsc
 dcbf39a7f15c68a3d74b26170f385ee22f68d9f9 25456156 
nomad_0.12.10+dfsg1.orig.tar.xz
 d09244f0bcbbeade921b517b9f54cc0fde790149 25328 
nomad_0.12.10+dfsg1-1.debian.tar.xz
 356cf1c7586ea1b0fdb28792c87c1bea48677330 23781 
nomad_0.12.10+dfsg1-1_amd64.buildinfo
Checksums-Sha256:
 0698d8833277fcde5cfa635cd7b1465d496607d26a755b75f6929ab4ad6cbc05 7712 
nomad_0.12.10+dfsg1-1.dsc
 9805476e6d8296f507a51cf9d0f6dc761811838f95ea2e792a14ac1be28cf4a1 25456156 
nomad_0.12.10+dfsg1.orig.tar.xz
 ae485acf6ca79d8c80a24da4ee0d049cab3067eb48bf5dc2fbc77d89ffb6b584 25328 
nomad_0.12.10+dfsg1-1.debian.tar.xz
 43393a5962b1b69c907b223c3fa9ca383994fb75e7707910d167eca68f55aeae 23781 
nomad_0.12.10+dfsg1-1_amd64.buildinfo
Files:
 c2f13b60e5d2355647d01bab632989a7 7712 admin optional nomad_0.12.10+dfsg1-1.dsc
 77a0cc8d8b27908f24d716cf0225cca0 25456156 admin optional 
nomad_0.12.10+dfsg1.orig.tar.xz
 fc356a3b7a10252c4624cbd564688b69 25328 admin optional 
nomad_0.12.10+dfsg1-1.debian.tar.xz
 a6d573d95f370b074eca178187db629a 23781 admin optional 
nomad_0.12.10+dfsg1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEULx8+TnSDCcqawZWUra72VOWjRsFAmAc2cQACgkQUra72VOW
jRtgfhAAwAFvwfS/0/2kkk6cS93MoiV4veAxK/AbFtdwulBFhEVR9fbi/Q/53wiP
t9LzmK2RPCLDsIgBo8hfaGp0MQ7mUcB1kqwxRlYujYVfeptV06ZRwMxNHozP6L98
NBrqP5W4YpwPvlU4U4yC1Aefng71qoJE83yEM8FZhwvHH/CIrkl+ZlUHIlQbatv1
b1yOQ9khw0HWaYfIHErEbtBluXn/saj8BEKej1XC6M1RctfVDbtCGq4/LieDZGQX
15QOlbqtNd56trI7hwQkLrTxouiPtd8nmVX8ovJLYQxJmE6oo16M5JE5NSwYLFig
afKZG9zRiPifk2ZNXNCWFhiSU8apABZqxCxMrKm98jIsTqPnuAYUbkDIQdo5sPaZ
W7BmJvFgQOy8lSTp150oYKLxQ+NgJoWn9jhVRdBE5wPehh4k2SjlOWfORXbw4P5M
udjms10gLYqQYZBjZpmmQlw9zd2+Tvb2h/4NIlPUrJ92/twEk49qQTtsFiBwwURM
kjY2FO8BSNAKde8Njmr8fKeLB/xBWbsYZNZ1eL9iTchrt/nmD/JeXoVNJP3/pVml
r+RwgAvW0ir6HsqULLjgkPNzdeTS0Ww2KHpCPRPFPUKnwO2Y2fLbJNFEDBVm8HGJ
OdVeNyqORyaHXWuRIkRwxl9Z34qcKqswH2+wda8TBJLjQ4pq/EU=
=OR3A
-END PGP SIGNATURE End Me

Processed: found 981889 in 0.12.9+dfsg1-2

[Debian Bug Tracking System]

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

> found 981889 0.12.9+dfsg1-2
Bug #981889 [src:nomad] nomad: CVE-2021-3283
Marked as found in versions nomad/0.12.9+dfsg1-2.
> thanks
Stopping processing here.

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

Processed: severity of 981835 is serious

[Debian Bug Tracking System]

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

> # Fails to configure due to file conflict -> release-critical
> severity 981835 serious
Bug #981835 [libelf1] libelf1 violates Multi-Arch: same / unreproducible
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#981804: yubioath-desktop: fails to read yubikey

[Norbert Preining]

Hi Nicoo,

> > — 
> > https://github.com/Yubico/yubioath-desktop/issues/693#issuecomment-773096570

Thanks for the info, that helps a lot. I will downgrade for the time
being.

Thanks for all you work on that!

Best

Norbert

--
PREINING Norbert  https://www.preining.info
Fujitsu Research Labs  +  IFMGA Guide + TU Wien + TeX Live + Debian Dev
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13

Bug#976860: marked as done (python3-plaso: log2timeline.py + image_export.py always bail out with "ERROR: Unable to determine location of data files.")

[Debian Bug Tracking System]

Your message dated Fri, 05 Feb 2021 00:04:06 +
with message-id 
and subject line Bug#976860: fixed in plaso 20201007-2
has caused the Debian Bug report #976860,
regarding python3-plaso: log2timeline.py + image_export.py always bail out with 
"ERROR: Unable to determine location of data files."
to be marked as done.

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

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


-- 
976860: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976860
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-plaso
Version: 20190131-3
Severity: grave
Justification: tools fail to start

image_export.py and log2timeline.py always exits with the error message

  ERROR: Unable to determine location of data files.

even with just passing --info (to log2timeline.py) as option.

Full output from Debian Testing and Kali Linux before the switch from
Python 3.8 to 3.9 (which throws a lot of Python warnings which I will
report separately):

$ log2timeline.py --info
ERROR: Unable to determine location of data files.

usage: log2timeline.py [-h] [-V] [--artifact_definitions PATH]
   [--custom_artifact_definitions PATH] [--data PATH]
   [--artifact_filters ARTIFACT_FILTERS]
   [--artifact_filters_file PATH] [--preferred_year YEAR]
   [--process_archives] [--skip_compressed_streams]
   [-f FILE_FILTER] [--hasher_file_size_limit SIZE]
   [--hashers HASHER_LIST] [--parsers PARSER_LIST]
   [--yara_rules PATH] [--partitions PARTITIONS]
   [--volumes VOLUMES] [-z TIMEZONE] [--no_vss]
   [--vss_only] [--vss_stores VSS_STORES]
   [--credential TYPE:DATA] [-d] [-q] [--info]
   [--use_markdown] [--no_dependencies_check]
   [--logfile FILENAME] [--status_view TYPE] [-t TEXT]
   [--buffer_size BUFFER_SIZE] [--queue_size QUEUE_SIZE]
   [--single_process] [--process_memory_limit SIZE]
   [--temporary_directory DIRECTORY]
   [--worker_memory_limit SIZE] [--workers WORKERS]
   [--disable_zeromq] [--sigsegv_handler]
   [--profilers PROFILERS_LIST]
   [--profiling_directory DIRECTORY]
   [--profiling_sample_rate SAMPLE_RATE]
   [--storage_format FORMAT]
   [STORAGE_FILE] [SOURCE]
$ image_export.py foo
ERROR: Unable to determine location of data files.
usage: image_export.py [-h] [-V] [-d] [-q] [--artifact_definitions PATH]
   [--custom_artifact_definitions PATH] [--data PATH] 
[--process_memory_limit SIZE]
   [--logfile FILENAME] [--partitions PARTITIONS] 
[--volumes VOLUMES] [--no_vss]
   [--vss_only] [--vss_stores VSS_STORES] 
[--artifact_filters ARTIFACT_FILTERS]
   [--artifact_filters_file PATH] [--date-filter 
TYPE_START_END] [-f FILE_FILTER]
   [-x EXTENSIONS] [--names NAMES] [--signatures 
IDENTIFIERS] [-w PATH]
   [--include_duplicates]
   [IMAGE]
$

According to strace it looks in these directories which are all
non-existing on my system:

stat("/usr/lib/python3/dist-packages/share/plaso", 0x7ffc932a7200) = -1 ENOENT 
(No such file or directory)
stat("/usr/lib/python3/dist-packages/data", 0x7ffc932a7200) = -1 ENOENT (No 
such file or directory)
stat("/usr/share/plaso", 0x7ffc932a7200) = -1 ENOENT (No such file or directory)
stat("/usr/local/share/plaso", 0x7ffc932a7200) = -1 ENOENT (No such file or 
directory)
ERROR: Unable to determine location of data files.

Seems as if either …

* the correct directory is not searched for,
* the files are missing from the package, or
* a package dependency is missing.

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

Kernel: Linux 5.9.0-4-amd64 (SMP w/4 CPU threads)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages python3-plaso depends on:
ii  python33.9.0-4
ii  python3-artifacts  20190320-3
ii  python3-biplist1.0.3-2

Bug#977109: marked as done (ruby-licensee, autopkgtest failure with ruby-rugged 1.1.0)

[Debian Bug Tracking System]

Your message dated Thu, 04 Feb 2021 23:50:43 +
with message-id 
and subject line Bug#977109: fixed in ruby-licensee 8.9.2-2
has caused the Debian Bug report #977109,
regarding ruby-licensee, autopkgtest failure with ruby-rugged 1.1.0
to be marked as done.

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

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


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

package: ruby-licensee
Version: 8.9.2-1
Severity: serious
Tags: bullseye, sid

The autopkgtest for ruby-licensee is failing with ruby-rugged 1.1.0.


GEM_PATH= ruby2.7 -e gem\ \"licensee\"
/usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1398:in `rescue in block in 
activate_dependencies': Could not find 'rugged' (~> 0.24) among 92 total gem(s) 
(Gem::MissingSpecError)
Checked in 
'GEM_PATH=/home/debci/.local/share/gem/ruby/2.7.0:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0'
 at: /usr/share/rubygems-integration/all/specifications/licensee-8.9.2.gemspec, 
execute `gem env` for more information
from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1395:in `block 
in activate_dependencies'
from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1384:in `each'
from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1384:in 
`activate_dependencies'
from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1366:in 
`activate'
from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
`block in gem'
from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
`synchronize'
from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
`gem'
from -e:1:in `'
/usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:309:in `to_specs': Could not find 
'rugged' (~> 0.24) - did find: [rugged-1.1.0] (Gem::MissingSpecVersionError)
Checked in 
'GEM_PATH=/home/debci/.local/share/gem/ruby/2.7.0:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0'
 , execute `gem env` for more information
from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1396:in `block 
in activate_dependencies'
from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1384:in `each'
from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1384:in 
`activate_dependencies'
from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1366:in 
`activate'
from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
`block in gem'
from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
`synchronize'
from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in 
`gem'
from -e:1:in `'



This is blocking ruby-rugged 1.1.0 (which is needed for the libgit2 transition) 
from migrating to
testing.
--- End Message ---
--- Begin Message ---
Source: ruby-licensee
Source-Version: 8.9.2-2
Done: Cédric Boutillier 

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

Debian distribution maintenance software
pp.
Cédric Boutillier  (supplier of updated ruby-licensee 
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, 05 Feb 2021 00:18:05 +0100
Source: ruby-licensee
Architecture: source
Version: 8.9.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Cédric Boutillier 
Closes: 977109
Changes:
 ruby-licensee (8.9.2-2) unstable; urgency=medium
 .
   * Team upload
   * Add gbp.conf for branch configurations
   * Add patch to relax dependency on rugged gem in gemspecs (Closes: #977109)
   * Move debian/watch to gemwatch.debian.net
   * Use salsa.debian.org in Vcs-* field

Processed: Bug#977109 marked as pending in ruby-licensee

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #977109 [ruby-licensee] ruby-licensee, autopkgtest failure with ruby-rugged 
1.1.0
Added tag(s) pending.

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

Bug#977109: marked as pending in ruby-licensee

[Cédric Boutillier]

Control: tag -1 pending

Hello,

Bug #977109 in ruby-licensee 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/ruby-team/ruby-licensee/-/commit/ccd51e26d2d41df5a4efdb9036b0b540ab0f548a


Add patch to relax dependency on rugged gem in gemspecs (Closes: #977109)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/977109

Processed: owner 981850

[Debian Bug Tracking System]

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

> owner 981850 terce...@debian.org
Bug #981850 [ruby-rspec] Failed: rspec-core, rspec-support
Owner recorded as terce...@debian.org.
> thanks
Stopping processing here.

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

Bug#981850: [DRE-maint] Bug#981850: Failed: rspec-core, rspec-support

[Antonio Terceiro]

On Thu, Feb 04, 2021 at 09:02:37PM +0530, Ritesh Raj Sarraf wrote:
> Package: ruby-rspec
> Version: 3.9.0c2e2m1s3-1
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source
> 
> Dear Maintainer,
> 
> During a rebuild of the package for Bullseye, it is seen that the
> package fails to build. The build failure snippet is below. It is also
> noticed that the same build failure is seen on the Reproducible Builds.
> 
> ```
> [  294s] Finished in 2.23 seconds (files took 0.50425 seconds to load)
> [  294s] 538 examples, 3 failures, 1 pending
> [  294s]
> [  294s] Failed examples:
> [  294s]
> [  294s] rspec ./spec/rspec/support/differ_spec.rb:315 # 
> RSpec::Support::Differ#diff outputs unified diff message of two hashes with 
> differing encoding
> [  294s] rspec ./spec/rspec/support/differ_spec.rb:328 # 
> RSpec::Support::Differ#diff outputs unified diff message of two hashes with 
> encoding different to key encoding
> [  294s] rspec ./spec/rspec/support/differ_spec.rb:158 # 
> RSpec::Support::Differ#diff uses the default external encoding when the two 
> strings have incompatible encodings
> [  294s]
> [  294s] Randomized with seed 8873
> [  294s]
> [  295s] cd -
> [  295s] Failed: rspec-core, rspec-support
> [  295s] ERROR: Test "ruby2.7" failed. Exiting.
> [  295s] dh_auto_install: error: dh_ruby --install 
> /usr/src/packages/BUILD/debian/tmp returned exit code 1
> [  295s] make: *** [debian/rules:99: binary] Error 25
> [  295s] dpkg-buildpackage: error: debian/rules binary subprocess returned 
> exit status 2
> ```

Can you please share more information about the environment where you
did this build?

I can reproduce a test failure with a non-UTF-8 locale, is that the
case?


signature.asc
Description: PGP signature

Processed: confirm

[Debian Bug Tracking System]

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

> tags 981662 confirmed
Bug #981662 [src:xfsprogs] xfsprogs-udeb depends on libinih1, not libinih1-udeb
Added tag(s) confirmed.
> tags 539723 upstream wontfix
Bug #539723 [xfsprogs] xfsprogs: {mkfs.xfs] Please provide GNU --long options
Added tag(s) upstream and wontfix.
>
End of message, stopping processing here.

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

Bug#975855: closing 975855

[Antonio Terceiro]

close 975855 
thanks

Hi.

I cannot reproduce this on my main system, under sbuild, or on a porterbox.
Maybe it was a transient failure, or something else got fixed in the meantime.
So I'm closing this bug.

Bug#845733: marked as done (nant: FTBFS (SDK path could not be resolved))

[Debian Bug Tracking System]

Your message dated Fri, 5 Feb 2021 00:42:07 +0200
with message-id <20210204224207.GA23742@localhost>
and subject line Fixed in 0.92~rc1+dfsg-7
has caused the Debian Bug report #845733,
regarding nant: FTBFS (SDK path could not be resolved)
to be marked as done.

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

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


-- 
845733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845733
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:nant
Version: 0.92~rc1+dfsg-6
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with cli
dh: Compatibility levels before 9 are deprecated (level 7 in use)
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
dh_auto_configure: Compatibility levels before 9 are deprecated (level 7 in use)
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>/nant-0.92~rc1+dfsg'
/usr/bin/make MONO=/usr/bin/cli MCS=/usr/bin/mono-csc
make[2]: Entering directory '/<>/nant-0.92~rc1+dfsg'
mkdir -p bootstrap
# Mono loads log4net before privatebinpath is set-up, so we need this in the 
same directory

[... snipped ...]


build:

[mkdir] Creating directory 
'/<>/nant-0.92~rc1+dfsg/build/mono-4.5.unix/nant-debug/bin/extensions/neutral/debian'.
  [csc] Compiling 22 files to 
'/<>/nant-0.92~rc1+dfsg/build/mono-4.5.unix/nant-debug/bin/extensions/neutral/debian/NAnt.MSBuild.dll'.
  [csc] warning CS8001: SDK path could not be resolved
  [csc] Compilation succeeded - 1 warning(s)

BUILD SUCCEEDED - 0 non-fatal error(s), 1 warning(s)

Total time: 0.3 seconds.

 [nant] /<>/nant-0.92~rc1+dfsg/tests/NAnt.Core/NAnt.Core.build 
build
Buildfile: 
file:///<>/nant-0.92~rc1+dfsg/tests/NAnt.Core/NAnt.Core.build
Target framework: Mono 4.5 Profile
Target(s) specified: build 


build:

  [csc] Compiling 67 files to 
'/<>/nant-0.92~rc1+dfsg/build/mono-4.5.unix/nant-debug/bin/NAnt.Core.Tests.dll'.
  [csc] error CS8001: Warning as Error: SDK path could not be 
resolved
  [csc] Compilation failed: 1 error(s), 0 warnings

BUILD FAILED - 0 non-fatal error(s), 1 warning(s)


/<>/nant-0.92~rc1+dfsg/tests/NAnt.Core/NAnt.Core.build(11,10):
External Program Failed: /usr/lib/mono/4.5/mcs.exe (return code was 
1)

Total time: 0.3 seconds.


BUILD FAILED

Nested build failed.  Refer to build log for exact reason.

Total time: 5.2 seconds.

Makefile:81: recipe for target 'build-nant' failed
make[2]: *** [build-nant] Error 1
make[2]: Leaving directory '/<>/nant-0.92~rc1+dfsg'
debian/rules:7: recipe for target 'override_dh_auto_build' failed
make[1]: *** [override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>/nant-0.92~rc1+dfsg'
debian/rules:14: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


It also fails here:

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

Even if this package is Arch:all, please consider uploading in source-only form,
so that we get official build logs here:

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

and also avoid bugs like this to propagate to testing.

Thanks.
--- End Message ---
--- Begin Message ---
Version: 0.92~rc1+dfsg-7

nant (0.92~rc1+dfsg-7) unstable; urgency=medium

  * [48d668e] Fix build on newer Mono w/ -api facades. Thanks to Sean Champ.

 -- Jo Shields   Tue, 25 Feb 2020 10:05:43 -0500--- End Message ---

Processed: closing 975855

[Debian Bug Tracking System]

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

> close 975855
Bug #975855 [src:ruby-fakefs] ruby-fakefs: FTBFS: ERROR: Test "ruby2.7" failed.
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#974994: marked as done (Please build-depend on libidn2-dev instead of obsolete transition package libidn2-0-dev)

[Debian Bug Tracking System]

Your message dated Thu, 04 Feb 2021 22:04:59 +
with message-id 
and subject line Bug#974994: fixed in libpsl 0.21.0-1.2
has caused the Debian Bug report #974994,
regarding Please build-depend on libidn2-dev instead of obsolete transition 
package libidn2-0-dev
to be marked as done.

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

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


-- 
974994: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974994
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libpsl
Version: 0.21.0-1.1
Tags: patch

The package libidn2-0-dev was obsoleted back in 2017, and replacing it
with libidn2-dev should work fine.

It would be great if this would be fixed before the next Debian
release, so we can finally remove the libidn2-0-dev package from the
archive.

/Simon

From 709812a3b9494dd9b0b4243e648e7fea7cbe546a Mon Sep 17 00:00:00 2001
From: Simon Josefsson 
Date: Tue, 17 Nov 2020 19:29:32 +0100
Subject: [PATCH] B-D on libidn2-dev instead of obsolete libidn2-0-dev.

---
 debian/control | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/control b/debian/control
index 12343db..e29579e 100644
--- a/debian/control
+++ b/debian/control
@@ -8,7 +8,7 @@ Build-Depends:
  autoconf-archive,
  automake,
  gtk-doc-tools,
- libidn2-0-dev (>=0.16),
+ libidn2-dev,
  libunistring-dev,
  pkg-config,
  publicsuffix (>= 20150507),
-- 
2.20.1



signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: libpsl
Source-Version: 0.21.0-1.2
Done: Sebastian Ramacher 

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated libpsl 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, 04 Feb 2021 22:56:22 +0100
Source: libpsl
Architecture: source
Version: 0.21.0-1.2
Distribution: unstable
Urgency: medium
Maintainer: Tim Rühsen 
Changed-By: Sebastian Ramacher 
Closes: 966941 974994
Changes:
 libpsl (0.21.0-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Simon Josefsson ]
   * B-D on libidn2-dev instead of obsolete libidn2-0-dev. (Closes: #974994)
 .
   [ Sebastian Ramacher ]
   * debian/patches: Update Platform.sh example in test data (Closes: #966941)
Checksums-Sha1:
 3f3502f14fef1e71ee9f118c83f36827b7145dae 2216 libpsl_0.21.0-1.2.dsc
 311be7d09c34ee8be8fffc49df93570493e143cc 12724 libpsl_0.21.0-1.2.debian.tar.xz
Checksums-Sha256:
 d46b69dd1cb43dc48375d70c4895d0a0d5964131196a7de4e0ad1ea2912d6df4 2216 
libpsl_0.21.0-1.2.dsc
 012d3b6ec5634c59e6a4aa9f854d756ef23f08edf21d70ae5a888c55e95abd5d 12724 
libpsl_0.21.0-1.2.debian.tar.xz
Files:
 4b0837e3bf4be0e84b1b7af1109dac70 2216 libs optional libpsl_0.21.0-1.2.dsc
 7b08b0807e6f8298cd701824d36bfe04 12724 libs optional 
libpsl_0.21.0-1.2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAmAcbmoACgkQafL8UW6n
GZPieA//YX7Z6O/9CFxORjxBA7Sv2oKIQTlCIM9Y1hScTg6OEIoJpFexcQgaJg/F
wqEEFW1d0mB6r1lxzTD50fDTVc1TtPQgxh2ok1Rk96oY8HnxUb6UefarKAxZWMsc
jsnmIZ4QdFi1EXJs8iB3norG36svJwTiZpYDbvy/ahL089O6kTzEQzeaUfXYOYnd
hhELnCS4t7PxxRreve4eS0AhHv/7Fh89dP8ex+DAgSNjJQRXuhK7uX+VPWZiQhTD
ZTL/dcjTgvauQUCwRacAp6/DsUkGqN+V4AOtefYe1eGL2HOkZj0jdUrJHLofYfWJ
f37sjpBYNWn7X7OMZYWyAB3P77HQkke71fHZDXhpHIIQoe3PF2tWUq8mlw2HS2NG
4mRAqhG2ZFwACOJrVL2V3zjwziEyr/hZzKVykIWfluIk/SSoLOSLYsrfQUWDjYXQ
pciEukCJCKHB71cXMmTrBfpMUcs1iFxki9UNr/sNkYhYp9HrbU/XKPlcwrZbAMxl
O6VNc3le0/QPF0XOzcQQl5zMHcSwFTzV7FIkAK2sg90Crh9cfRugkedKRHTvu/kH
qPFDkoQCGHYw1eZbQG05RqXKch9TvyGtn3TUhA1BhtPbtJThb7O8N2zBzRb7dkkE
rvUeFVTC+563vNjITKBU4/3buWlxwAG/rfaJAtqOQW8P8egUlp4=
=iJnM
-END PGP SIGNATURE End Message ---

Bug#966941: marked as done (libpsl: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2)

[Debian Bug Tracking System]

Your message dated Thu, 04 Feb 2021 22:04:59 +
with message-id 
and subject line Bug#966941: fixed in libpsl 0.21.0-1.2
has caused the Debian Bug report #966941,
regarding libpsl: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned 
exit code 2
to be marked as done.

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

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


-- 
966941: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966941
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libpsl
Version: 0.21.0-1.1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200802 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> make[5]: Entering directory '/<>/tests'
> FAIL: test-is-public-builtin
> PASS: test-is-cookie-domain-acceptable
> PASS: test-is-public
> PASS: test-registrable-domain
> PASS: test-is-public-all
> =
>libpsl 0.21.0: tests/test-suite.log
> =
> 
> # TOTAL: 5
> # PASS:  4
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> .. contents:: :depth: 2
> 
> FAIL: test-is-public-builtin
> 
> 
> have 8934 suffixes and 8 exceptions
> psl_is_public_suffix(whatever.platform.sh)=0 (expected 1)
> psl_is_public_suffix(.platform.sh)=0 (expected 1)
> psl_is_public_suffix2(whatever.platform.sh, NO_STAR_RULE)=0 (expected 1)
> psl_is_public_suffix2(.platform.sh, NO_STAR_RULE)=0 (expected 1)
> psl_builtin_file_time()=1596043500
> psl_builtin_sha1sum()=5db9beb156c226fd98a7e1d18c04eb5b2d6b4a87
> Summary: 4 out of 68 tests failed
> FAIL test-is-public-builtin (exit status: 1)
> 
> 
> Testsuite summary for libpsl 0.21.0
> 
> # TOTAL: 5
> # PASS:  4
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> See tests/test-suite.log
> Please report to tim.rueh...@gmx.de
> 
> make[5]: *** [Makefile:799: test-suite.log] Error 1
> make[5]: Leaving directory '/<>/tests'
> make[4]: *** [Makefile:907: check-TESTS] Error 2
> make[4]: Leaving directory '/<>/tests'
> make[3]: *** [Makefile:1009: check-am] Error 2
> make[3]: Leaving directory '/<>/tests'
> make[2]: *** [Makefile:1011: check] Error 2
> make[2]: Leaving directory '/<>/tests'
> make[1]: *** [Makefile:535: check-recursive] Error 1
> make[1]: Leaving directory '/<>'
> dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2

The full build log is available from:
   http://qa-logs.debian.net/2020/08/02/libpsl_0.21.0-1.1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: libpsl
Source-Version: 0.21.0-1.2
Done: Sebastian Ramacher 

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated libpsl 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, 04 Feb 2021 22:56:22 +0100
Source: libpsl
Architecture: source
Version: 0.21.0-1.2
Distribution: unstable
Urgency: medium
Maintainer: Tim Rühsen 
Changed-By: Sebastian Ramacher 
Closes: 966941 974994
Changes:
 libpsl (0.21.0-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Simon Josefsson ]
   * B-D on libidn2-dev instead of obsolete libidn2-0-dev. (Closes: #974994)
 .
   [ Sebastian Ramacher ]
   * debian/patches: Update Platform.sh example in test data (Closes: #966941)

Bug#963687: marked as done (FTBFS: Does not build with ghc 8.8)

[Debian Bug Tracking System]

Your message dated Fri, 5 Feb 2021 00:03:56 +0200
with message-id <20210204220356.GA20755@localhost>
and subject line Fixed in 5.3.1-2
has caused the Debian Bug report #963687,
regarding FTBFS: Does not build with ghc 8.8
to be marked as done.

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

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


-- 
963687: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963687
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-hindent
Version: 5.3.1-1
Severity: grave
Justification: renders package unusable
Forwarded: https://github.com/chrisdone/hindent/issues/563

This package FTBFS with ghc 8.8. It also appears to be unmaintained:

  https://github.com/chrisdone/hindent/issues/557

-- 
Ilias
--- End Message ---
--- Begin Message ---
Version: 5.3.1-2

haskell-hindent (5.3.1-2) unstable; urgency=medium

  * Patch for newer haskell-src-exts.

 -- Clint Adams   Thu, 25 Jun 2020 10:39:58 -0400--- End Message ---

Bug#963640: marked as done (jansson: FTBFS with Sphinx 3.1: TypeError: add_directive() takes from 3 to 4 positional arguments but 5 were given)

[Debian Bug Tracking System]

Your message dated Thu, 04 Feb 2021 22:04:48 +
with message-id 
and subject line Bug#963640: fixed in jansson 2.13.1-1.1
has caused the Debian Bug report #963640,
regarding jansson: FTBFS with Sphinx 3.1: TypeError: add_directive() takes from 
3 to 4 positional arguments but 5 were given
to be marked as done.

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

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


-- 
963640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963640
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jansson
Version: 2.12-1
Severity: important
Tags: ftbfs
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx3.1

Hi,

jansson fails to build with Sphinx 3.1, currently available in
experimental.

Relevant part (hopefully):
> make[3]: Entering directory '/<>/doc'
> sphinx-build -b html -D today="December 15, 2018" . _build/html
> Running Sphinx v3.1.1
> 
> Exception occurred:
>   File "/<>/doc/ext/refcounting.py", line 60, in setup
> app.add_directive('refcounting', refcounting_directive, 0, (1, 0, 0))
> TypeError: add_directive() takes from 3 to 4 positional arguments but 5 were 
> given
> The full traceback has been saved in /tmp/sphinx-err-8hra1hv3.log, if you 
> want to report the issue to the developers.
> Please also report this if it was a user error, so that a better error 
> message can be provided next time.
> A bug report can be filed in the tracker at 
> . Thanks!
> make[3]: *** [Makefile:448: html-local] Error 2

The full build log is available from:
   http://qa-logs.debian.net/2020/06/23/jansson_2.12-1_unstable_sphinx-exp.log

Please see [1] for Sphinx changelog, which may give a hint of what changes in
Sphinx caused this error.

Also see [2] for the list of deprecated/removed APIs and possible alternatives
to them.

Sphinx 3.1 is going to be uploaded to unstable in a couple of weeks. When that
happens, the severity of this bug will be bumped to serious.

In case you have questions, please Cc sph...@packages.debian.org on reply.

[1]: https://www.sphinx-doc.org/en/3.x/changes.html
[2]: https://www.sphinx-doc.org/en/3.x/extdev/deprecated.html

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: jansson
Source-Version: 2.13.1-1.1
Done: Sebastian Ramacher 

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated jansson 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, 04 Feb 2021 22:47:01 +0100
Source: jansson
Architecture: source
Version: 2.13.1-1.1
Distribution: unstable
Urgency: medium
Maintainer: Alessandro Ghedini 
Changed-By: Sebastian Ramacher 
Closes: 963640
Changes:
 jansson (2.13.1-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload
 .
   [ Sebastien Bacher ]
   * debian/patches/git_new_sphinx.patch:
 - backport an upstream change to fix the build with sphinx3
   (Closes: #963640)
Checksums-Sha1:
 8adab920534191783f2528c0bf64b94ddc70cce3 2002 jansson_2.13.1-1.1.dsc
 444b52dd1adb10faeb1154070f35d1a366956623 5364 jansson_2.13.1-1.1.debian.tar.xz
Checksums-Sha256:
 800bac1bd7231e41ac5fba8fa632d80894b2961d4d7d41037655b224c1f73d4e 2002 
jansson_2.13.1-1.1.dsc
 e4f72193800b35acf40c6db2dc4404980a56ee8e1244666ea20e81a04dd69d15 5364 
jansson_2.13.1-1.1.debian.tar.xz
Files:
 a75c8189ff00719ffb39f629de6fdc6c 2002 libs optional jansson_2.13.1-1.1.dsc
 1ab3d65f7458bde7c85443fea17df3da 5364 libs optional 
jansson_2.13.1-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAmAca+wACgkQafL8UW6n
GZNp/g//aQhxG1LtkUodJHk4U+8ZaCKH20C7VLW08ESR6E6AAnkgpEqA2tKJ6/MP
DptphhR4J6cmiDbpJxsy6J2tiq4uWTuPVfV95aW6Vgnk

Bug#978364: marked as done (apertium-ukr: FTBFS: Error: Invalid dictionary (hint: the left side of an entry is empty))

[Debian Bug Tracking System]

Your message dated Thu, 04 Feb 2021 22:00:09 +
with message-id 
and subject line Bug#978364: fixed in apertium-rus-ukr 0.2.1-1
has caused the Debian Bug report #978364,
regarding apertium-ukr: FTBFS: Error: Invalid dictionary (hint: the left side 
of an entry is empty)
to be marked as done.

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

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


-- 
978364: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978364
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: apertium-ukr
Version: 0.1.0~r82563-2
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> apertium-validate-dictionary apertium-ukr.ukr.dix
> /bin/mkdir -p .deps
> lt-comp lr apertium-ukr.post-ukr.dix ukr.autopgen.bin
> /usr/bin/cg-comp apertium-ukr.ukr.rlx ukr.rlx.bin
> touch .deps/.d
> apertium-validate-modes modes.xml
> main@standard 6 14
> apertium-validate-dictionary apertium-ukr.ukr.dix
> Sections: 1, Rules: 29, Sets: 67, Tags: 138
> 10 rules cannot be skipped by index.
> apertium-gen-modes modes.xml
> lt-comp lr apertium-ukr.ukr.dix ukr.automorf.bin apertium-ukr.ukr.acx
> lt-comp rl apertium-ukr.ukr.dix ukr.autogen.bin apertium-ukr.ukr.acx
> final@inconditional 34 301
> gci@standard 583 789
> main@standard 16515 38654
> lt-print ukr.autogen.bin | gzip -9 -c -n > ukr.autogen.att.gz
> Error: Invalid dictionary (hint: the left side of an entry is empty)
> make[1]: *** [Makefile:729: ukr.automorf.bin] Error 1

The full build log is available from:
   http://qa-logs.debian.net/2020/12/26/apertium-ukr_0.1.0~r82563-2_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: apertium-rus-ukr
Source-Version: 0.2.1-1
Done: Kartik Mistry 

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

Debian distribution maintenance software
pp.
Kartik Mistry  (supplier of updated apertium-rus-ukr 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: Mon, 01 Feb 2021 08:49:22 +0530
Source: apertium-rus-ukr
Binary: apertium-rus-ukr
Architecture: source all
Version: 0.2.1-1
Distribution: experimental
Urgency: low
Maintainer: Debian Science Team 

Changed-By: Kartik Mistry 
Description:
 apertium-rus-ukr - Apertium translation data for the Russian-Ukrainian pair
Closes: 978364 981530
Changes:
 apertium-rus-ukr (0.2.1-1) experimental; urgency=low
 .
   [ Tino Didriksen ]
   * Initial release (Closes: #981530)
   * Bundles apertium-rus 0.2.1 and apertium-ukr 0.1.1 (Closes: #978364)
Checksums-Sha1:
 59ace0afa8c64989798b65983c1beb279575aba4 2131 apertium-rus-ukr_0.2.1-1.dsc
 ab5405725f7bd54a2268dd93c712cde5c69fb901 2436980 
apertium-rus-ukr_0.2.1.orig.tar.bz2
 5f63cbb5aaf8ce865bcb726fdf5f32ec16d54301 2768 
apertium-rus-ukr_0.2.1-1.debian.tar.xz
 7f998d683bca680beea56cfff0a72ea652d4c8b1 1383248 
apertium-rus-ukr_0.2.1-1_all.deb
 94e41a5b784aecc1295ea7fd610912aa41c06ca9 6775 
apertium-rus-ukr_0.2.1-1_amd64.buildinfo
Checksums-Sha256:
 4d3e07b4e68dccf3645f3ee4f126a5d63475070175476378678912519f143b85 2131 
apertium-rus-ukr_0.2.1-1.dsc
 915640c6bfea580a46b073b8c1b9abb0391e6036eae7360d096c359779868b35 2436980 
apertium-rus-ukr_0.2.1.orig.tar.bz2
 4c46cdcb162efdfea63b12eea6c4e8715a20a5736e0816ad2e2b2e96a7697220 2768 
apertium-rus-ukr_0.2.1-1.d

Bug#966941: libpsl: diff for NMU version 0.21.0-1.2

[Sebastian Ramacher]

Dear maintainer,

I've prepared an NMU for libpsl (versioned as 0.21.0-1.2). The diff is
attached to this message.

Cheers
-- 
Sebastian Ramacher
diff -Nru libpsl-0.21.0/debian/changelog libpsl-0.21.0/debian/changelog
--- libpsl-0.21.0/debian/changelog	2020-05-16 16:24:03.0 +0200
+++ libpsl-0.21.0/debian/changelog	2021-02-04 22:56:22.0 +0100
@@ -1,3 +1,15 @@
+libpsl (0.21.0-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Simon Josefsson ]
+  * B-D on libidn2-dev instead of obsolete libidn2-0-dev. (Closes: #974994)
+
+  [ Sebastian Ramacher ]
+  * debian/patches: Update Platform.sh example in test data (Closes: #966941)
+
+ -- Sebastian Ramacher   Thu, 04 Feb 2021 22:56:22 +0100
+
 libpsl (0.21.0-1.1) unstable; urgency=low
 
   * Non-maintainer upload.
diff -Nru libpsl-0.21.0/debian/control libpsl-0.21.0/debian/control
--- libpsl-0.21.0/debian/control	2020-05-16 16:24:03.0 +0200
+++ libpsl-0.21.0/debian/control	2021-02-04 22:54:10.0 +0100
@@ -8,7 +8,7 @@
  autoconf-archive,
  automake,
  gtk-doc-tools,
- libidn2-0-dev (>=0.16),
+ libidn2-dev,
  libunistring-dev,
  pkg-config,
  publicsuffix (>= 20150507),
diff -Nru libpsl-0.21.0/debian/patches/0008-Update-Platform.sh-example-in-test-data.patch libpsl-0.21.0/debian/patches/0008-Update-Platform.sh-example-in-test-data.patch
--- libpsl-0.21.0/debian/patches/0008-Update-Platform.sh-example-in-test-data.patch	1970-01-01 01:00:00.0 +0100
+++ libpsl-0.21.0/debian/patches/0008-Update-Platform.sh-example-in-test-data.patch	2021-02-04 22:55:25.0 +0100
@@ -0,0 +1,23 @@
+From: Nikola Kotur 
+Date: Thu, 2 Jul 2020 16:41:58 +0200
+Subject: Update Platform.sh example in test data
+
+---
+ tests/test-is-public-builtin.c | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/tests/test-is-public-builtin.c b/tests/test-is-public-builtin.c
+index e9963b5..ea3a434 100644
+--- a/tests/test-is-public-builtin.c
 b/tests/test-is-public-builtin.c
+@@ -82,8 +82,8 @@ static void test_psl(void)
+ 		{ ".forgot.his.name", 1, 1 },
+ 		{ "whoever.his.name", 0, 0 },
+ 		{ "whoever.forgot.his.name", 0, 0 },
+-		{ "whatever.platform.sh", 1, 1 },
+-		{ ".platform.sh", 1, 1 },
++		{ "whatever.platformsh.site", 1, 1 },
++		{ ".platformsh.site", 1, 1 },
+ 		{ "whatever.yokohama.jp", 1, 1 },
+ 		{ ".yokohama.jp", 1, 1 },
+ 		{ ".", 1, 0 }, /* special case */
diff -Nru libpsl-0.21.0/debian/patches/series libpsl-0.21.0/debian/patches/series
--- libpsl-0.21.0/debian/patches/series	2020-03-04 18:39:16.0 +0100
+++ libpsl-0.21.0/debian/patches/series	2021-02-04 22:55:25.0 +0100
@@ -5,3 +5,4 @@
 0005-Add-missing-api-indeces-for-gtk-doc.patch
 0006-Use-NULL-and-FILE-overall-in-gtk-docs.patch
 0007-gtk-doc-do-not-include-tree_index.sgml.patch
+0008-Update-Platform.sh-example-in-test-data.patch


signature.asc
Description: PGP signature

Bug#957074: cdrkit: diff for NMU version 9:1.1.11-3.2

[John Paul Adrian Glaubitz]

Please don’t. I am planning to work on this in the following days. I was stuck 
with hfsprogs.

Thanks,
Adrian

> On Feb 4, 2021, at 10:41 PM, Sebastian Ramacher  wrote:
> 
> Control: tags 957074 + patch
> 
> Dear maintainer,
> 
> the ITA bug has been filed, but nothing happended since then. So I've
> prepared an NMU for cdrkit (versioned as 9:1.1.11-3.2). The diff is
> attached to this message.
> 
> Cheers
> -- 
> Sebastian Ramacher
> 

Bug#981894: marked as done (go-dlib FTBFS: test failure)

[Debian Bug Tracking System]

Your message dated Thu, 04 Feb 2021 21:49:18 +
with message-id 
and subject line Bug#981894: fixed in go-dlib 5.6.0.9+dfsg-2
has caused the Debian Bug report #981894,
regarding go-dlib FTBFS: test failure
to be marked as done.

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

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


-- 
981894: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981894
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: go-dlib
Version: 5.6.0.9+dfsg-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=go-dlib&arch=all&ver=5.6.0.9%2Bdfsg-1&stamp=1612409395&raw=0

...
FAIL: group_test.go:57: testWrapper.TestGetGroupEntry

group_test.go:60:
c.Check(groups[0].Name, C.Equals, "root")
... obtained string = "porter-any"
... expected string = "root"

OOPS: 2 passed, 1 FAILED
--- FAIL: Test (0.00s)
FAIL
FAILpkg.deepin.io/lib/users/group   0.019s
...
--- End Message ---
--- Begin Message ---
Source: go-dlib
Source-Version: 5.6.0.9+dfsg-2
Done: Boyuan Yang 

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated go-dlib 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, 04 Feb 2021 16:21:00 -0500
Source: go-dlib
Architecture: source
Version: 5.6.0.9+dfsg-2
Distribution: unstable
Urgency: high
Maintainer: Debian Deepin Packaging Team 

Changed-By: Boyuan Yang 
Closes: 981894
Changes:
 go-dlib (5.6.0.9+dfsg-2) unstable; urgency=high
 .
   * Team upload.
   * Disable broken /etc/group test in group_test.go. (Closes: #981894)
Checksums-Sha1:
 1c85717310435345d872f215eecf4708271783c4 2695 go-dlib_5.6.0.9+dfsg-2.dsc
 eb6fac82c0e4a5aeb7cd11217c39bb1c7e8c1cf1 555038 
go-dlib_5.6.0.9+dfsg.orig.tar.gz
 938fe3fbf85a4aa54784ff76172b9cf6c7c431f1 4440 
go-dlib_5.6.0.9+dfsg-2.debian.tar.xz
 711ceb736b1443fe32803f595c4f50a882ce0664 15873 
go-dlib_5.6.0.9+dfsg-2_amd64.buildinfo
Checksums-Sha256:
 0a2f616dbbf6de3b8ea2f20f764fa85b4e3cc3dc9e53ff31cc72408373741b97 2695 
go-dlib_5.6.0.9+dfsg-2.dsc
 56f36e15033beae8750a3af400108d4594bc49d211c9e72462c5d36a3102f23a 555038 
go-dlib_5.6.0.9+dfsg.orig.tar.gz
 a7afe4f4ddc158c11726ae343f610363ad717a69d42b6726b2b8a6aabb2a16d6 4440 
go-dlib_5.6.0.9+dfsg-2.debian.tar.xz
 868c7acc4a495c64d115815690e5a183cdac9669007a8eff5b8aab9db47460ea 15873 
go-dlib_5.6.0.9+dfsg-2_amd64.buildinfo
Files:
 b7088efdb65e16b7e05560e751326c41 2695 devel optional go-dlib_5.6.0.9+dfsg-2.dsc
 d809e77a4f7bfd6bc228eb30067827a6 555038 devel optional 
go-dlib_5.6.0.9+dfsg.orig.tar.gz
 0558870f7fee621c9eb6698393183a23 4440 devel optional 
go-dlib_5.6.0.9+dfsg-2.debian.tar.xz
 b80ccbbf5931fef92eab2d2b7a683ac7 15873 devel optional 
go-dlib_5.6.0.9+dfsg-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmAcZrMACgkQwpPntGGC
Ws49qBAAqeOc070EPaS/0Mx7OokR2AzNTFlLw9HdYg9yuroocQ5/li3XMxfiPCJV
/bCU2Ic+lg/U71hqb+vVj88lvsDQbZ/8LR6BXA6X1k6RTOCTViLrs+iX1XrWkWqJ
DZVkytZl/+N/hMwHe8L86jlFNcGTWwjLFrTxm/U4lEOb5VXBDLHkc43MBt9ZbmpU
+JR44btkuYR/54gXcNrseiO3iEb+3FQTNCYkb/+F78qmgTMjzYLKmig+PWNMCgzq
VUS3vqgW+TdMXiZ7WvTnukxqhV6/3ffpNu4J/ejk5+xepygkdFWLHayjXYjsUu2/
2luwTnM7dCGo/ZqZvp1Bqf9qM1ZeVFVrrHAPh0Mm8HqkgkZU8tz5m8Z0YDQbOKQB
iIH0jlftDcSrUruHL9HYzEjBKoUsxY5RtF377+pTw5t0rGQ8d+9Ng3wquthmoUSY
pwtGol7oUdnMNDAf81xCvi6/6zMfoUptsTnbuWvYMQ0DQo/j4GvXoAtd4KZ6WJJI
ap0F0MBwfheN/Nz6x4feL0bDZsEtZUaRo1we6FB5KZjSEWaMy1rF/r6IT2ReZYFU
NXfNQUd4lC9e7Bat7zA4QRyyCbSVBDwL+NZWRJt+J8xfp0aur9IehnrZKeAPo6bu
puUKhNI0YgULEx77D5A70pR3rgdVKcNnEpU7bczPt8KfJJE9okA=
=9224
-END PGP SIGNATURE End Message ---

Bug#957074: marked as done (cdrkit: ftbfs with GCC-10)

[Debian Bug Tracking System]

Your message dated Thu, 04 Feb 2021 21:48:30 +
with message-id 
and subject line Bug#957074: fixed in cdrkit 9:1.1.11-3.2
has caused the Debian Bug report #957074,
regarding cdrkit: ftbfs with GCC-10
to be marked as done.

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

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


-- 
957074: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957074
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:cdrkit
Version: 9:1.1.11-3.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/cdrkit_1.1.11-3.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

[...]
  313 | strncpy((char *)vh.vh_vd[i].vd_name, filename, MIN(VDNAMESIZE, 
strlen(filename)));
  | 
^
In file included from /<>/genisoimage/../include/dirdefs.h:80,
 from /<>/genisoimage/genisoimage.h:48,
 from /<>/genisoimage/boot-mips.c:191:
/<>/genisoimage/boot-mips.c:313:72: note: length computed here
  313 | strncpy((char *)vh.vh_vd[i].vd_name, filename, MIN(VDNAMESIZE, 
strlen(filename)));
  |^
[ 72%] Building C object genisoimage/CMakeFiles/genisoimage.dir/md5.o
[ 72%] Building C object genisoimage/CMakeFiles/genisoimage.dir/jte.o
/<>/genisoimage/jte.c: In function ‘list_file_in_jigdo’:
/<>/genisoimage/jte.c:281:26: warning: ‘sizeof’ on array function 
parameter ‘md5’ will return size of ‘unsigned char *’ [-Wsizeof-array-argument]
  281 | memset(md5, 0, sizeof(md5));
  |  ^
/<>/genisoimage/jte.c:272:90: note: declared here
  272 | extern int list_file_in_jigdo(char *filename, off_t size, char 
**realname, unsigned char md5[16])
  | 
   ~~^~~
/<>/genisoimage/jte.c:317:21: warning: implicit declaration of 
function ‘calculate_md5sum’ [-Wimplicit-function-declaration]
  317 | calculate_md5sum(filename, size, md5);
  | ^~~~
/<>/genisoimage/jte.c: In function ‘parse_md5_list’:
/<>/genisoimage/jte.c:528:13: warning: implicit declaration of 
function ‘mk_MD5Parse’ [-Wimplicit-function-declaration]
  528 | if (mk_MD5Parse(buf, md5))
  | ^~~
[ 73%] Building C object genisoimage/CMakeFiles/genisoimage.dir/rsync.o
[ 73%] Building C object genisoimage/CMakeFiles/genisoimage.dir/boot-mipsel.o
[ 74%] Building C object genisoimage/CMakeFiles/genisoimage.dir/endian.o
[ 74%] Building C object genisoimage/CMakeFiles/genisoimage.dir/sha1.o
[ 74%] Building C object genisoimage/CMakeFiles/genisoimage.dir/sha256.o
[ 75%] Building C object genisoimage/CMakeFiles/genisoimage.dir/sha512.o
[ 75%] Building C object genisoimage/CMakeFiles/genisoimage.dir/checksum.o
[ 76%] Linking C executable genisoimage
/usr/bin/ld: 
CMakeFiles/genisoimage.dir/apple.o:/<>/genisoimage/genisoimage.h:380:
 multiple definition of `outfile'; 
CMakeFiles/genisoimage.dir/genisoimage.o:/<>/genisoimage/genisoimage.h:380:
 first defined here
/usr/bin/ld: 
CMakeFiles/genisoimage.dir/boot.o:/<>/genisoimage/genisoimage.h:380:
 multiple definition of `outfile'; 
CMakeFiles/genisoimage.dir/genisoimage.o:/<>/genisoimage/genisoimage.h:380:
 first defined here
/usr/bin/ld: 
CMakeFiles/genisoimage.dir/desktop.o:/<>/genisoimage/genisoimage.h:380:
 multiple definition of `outfile'; 
CMakeFiles/genisoi

Processed: closing 871692

[Debian Bug Tracking System]

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

> close 871692 2.11.0-1
Bug #871692 [src:gobgp] gobgp FTBFS on arm64: Test killed with quit: ran too 
long (10m0s).
Marked as fixed in versions gobgp/2.11.0-1.
Bug #871692 [src:gobgp] gobgp FTBFS on arm64: Test killed with quit: ran too 
long (10m0s).
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: retitle 968381 to bashtop: seems superceded by Python-based bpytop

[Debian Bug Tracking System]

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

> retitle 968381 bashtop: seems superceded by Python-based bpytop
Bug #968381 [bashtop] bashtop: seems superceded by Python-based pbytop
Changed Bug title to 'bashtop: seems superceded by Python-based bpytop' from 
'bashtop: seems superceded by Python-based pbytop'.
> thanks
Stopping processing here.

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

Bug#963640: jansson: diff for NMU version 2.13.1-1.1

[Sebastian Ramacher]

Dear maintainer,

I've prepared an NMU for jansson (versioned as 2.13.1-1.1). The diff is
attached to this message.

Cheers
-- 
Sebastian Ramacher
diff -Nru jansson-2.13.1/debian/changelog jansson-2.13.1/debian/changelog
--- jansson-2.13.1/debian/changelog	2020-06-28 14:46:50.0 +0200
+++ jansson-2.13.1/debian/changelog	2021-02-04 22:47:01.0 +0100
@@ -1,3 +1,14 @@
+jansson (2.13.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+
+  [ Sebastien Bacher ]
+  * debian/patches/git_new_sphinx.patch:
+- backport an upstream change to fix the build with sphinx3
+  (Closes: #963640)
+
+ -- Sebastian Ramacher   Thu, 04 Feb 2021 22:47:01 +0100
+
 jansson (2.13.1-1) unstable; urgency=medium
 
   * New upstream release (Closes: #963842)
diff -Nru jansson-2.13.1/debian/patches/git_new_sphinx.patch jansson-2.13.1/debian/patches/git_new_sphinx.patch
--- jansson-2.13.1/debian/patches/git_new_sphinx.patch	1970-01-01 01:00:00.0 +0100
+++ jansson-2.13.1/debian/patches/git_new_sphinx.patch	2021-02-04 22:45:41.0 +0100
@@ -0,0 +1,66 @@
+From 798d40c3f3e0700501de1588274b69e2b128ad7c Mon Sep 17 00:00:00 2001
+From: Pierce Lopez 
+Date: Fri, 7 Aug 2020 01:54:45 -0400
+Subject: [PATCH] doc: convert refcounting directive to a class
+
+Directive functions are no longer supported in Sphinx-3.0
+but directive classes have been supported since early 1.x
+---
+ doc/ext/refcounting.py | 31 ---
+ 1 file changed, 20 insertions(+), 11 deletions(-)
+
+diff --git a/doc/ext/refcounting.py b/doc/ext/refcounting.py
+index bba26849..e72c481c 100644
+--- a/doc/ext/refcounting.py
 b/doc/ext/refcounting.py
+@@ -24,8 +24,8 @@
+ """
+ 
+ from docutils import nodes
++from docutils.parsers.rst import Directive
+ 
+-class refcounting(nodes.emphasis): pass
+ 
+ def visit(self, node):
+ self.visit_emphasis(node)
+@@ -40,16 +40,25 @@ def html_depart(self, node):
+ self.body.append('')
+ 
+ 
+-def refcounting_directive(name, arguments, options, content, lineno,
+-   content_offset, block_text, state, state_machine):
+-if arguments[0] == 'borrow':
+-text = 'Return value: Borrowed reference.'
+-elif arguments[0] == 'new':
+-text = 'Return value: New reference.'
+-else:
+-raise Error('Valid arguments: new, borrow')
++class refcounting(nodes.emphasis):
++pass
++
++class refcounting_directive(Directive):
++has_content = False
++required_arguments = 1
++optional_arguments = 0
++final_argument_whitespace = False
++
++def run(self):
++if self.arguments[0] == 'borrow':
++text = 'Return value: Borrowed reference.'
++elif self.arguments[0] == 'new':
++text = 'Return value: New reference.'
++else:
++raise Error('Valid arguments: new, borrow')
++
++return [refcounting(text, text)]
+ 
+-return [refcounting(text, text)]
+ 
+ def setup(app):
+ app.add_node(refcounting,
+@@ -57,4 +66,4 @@ def setup(app):
+  latex=(visit, depart),
+  text=(visit, depart),
+  man=(visit, depart))
+-app.add_directive('refcounting', refcounting_directive, 0, (1, 0, 0))
++app.add_directive('refcounting', refcounting_directive)
diff -Nru jansson-2.13.1/debian/patches/series jansson-2.13.1/debian/patches/series
--- jansson-2.13.1/debian/patches/series	1970-01-01 01:00:00.0 +0100
+++ jansson-2.13.1/debian/patches/series	2021-02-04 22:45:41.0 +0100
@@ -0,0 +1 @@
+git_new_sphinx.patch


signature.asc
Description: PGP signature

Bug#980655: lbzip2: diff for NMU version 2.5-2.1

[Boyuan Yang]

Control: tags 980655 + patch
Control: tags 980655 + pending

Dear maintainer,

I've prepared an NMU for lbzip2 (versioned as 2.5-2.1) and
uploaded it to DELAYED/3. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru lbzip2-2.5/debian/changelog lbzip2-2.5/debian/changelog
--- lbzip2-2.5/debian/changelog 2016-11-09 06:08:17.0 -0500
+++ lbzip2-2.5/debian/changelog 2021-02-04 16:37:24.0 -0500
@@ -1,3 +1,13 @@
+lbzip2 (2.5-2.1) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * debian/control: Replace obsolete Priority: extra with
+Priority: optional.
+  * debian/patches/0001-configure-ac: Bump AC_PREREQ to 2.64.
+This fixes FTBFS with newer gnulib. (Closes: #980655)
+
+ -- Boyuan Yang   Thu, 04 Feb 2021 16:37:24 -0500
+
 lbzip2 (2.5-2) unstable; urgency=low
 
   * debian/rules: Switch to default dpkg-deb compression
diff -Nru lbzip2-2.5/debian/control lbzip2-2.5/debian/control
--- lbzip2-2.5/debian/control   2016-11-09 06:08:17.0 -0500
+++ lbzip2-2.5/debian/control   2021-02-04 16:35:48.0 -0500
@@ -1,6 +1,6 @@
 Source: lbzip2
 Section: utils
-Priority: extra
+Priority: optional
 Maintainer: Mikolaj Izdebski 
 Build-Depends: debhelper (>= 9), gnulib (>= 20130805), autoconf,
automake (>= 1.14)
 Standards-Version: 3.9.8
diff -Nru lbzip2-2.5/debian/patches/0001-configure.ac-Bump-AC_PREREQ-
to-2.64.patch lbzip2-2.5/debian/patches/0001-configure.ac-Bump-
AC_PREREQ-to-2.64.patch
--- lbzip2-2.5/debian/patches/0001-configure.ac-Bump-AC_PREREQ-to-
2.64.patch  1969-12-31 19:00:00.0 -0500
+++ lbzip2-2.5/debian/patches/0001-configure.ac-Bump-AC_PREREQ-to-
2.64.patch  2021-02-04 16:37:18.0 -0500
@@ -0,0 +1,24 @@
+From: Boyuan Yang 
+Date: Thu, 4 Feb 2021 16:36:47 -0500
+Subject: configure.ac: Bump AC_PREREQ to 2.64
+
+Required by new gnulib.
+
+Bug-Debian: https://bugs.debian.org/980655
+---
+ configure.ac | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/configure.ac b/configure.ac
+index a20abe0..9c198f1 100644
+--- a/configure.ac
 b/configure.ac
+@@ -16,7 +16,7 @@
+ 
+ dnl TODO: check for GCC builtins: expect, prefetch, ctz, ctzl, ctzll
+ 
+-AC_PREREQ([2.63])
++AC_PREREQ([2.64])
+ AC_INIT([lbzip2], [2.5])
+ 
+ AC_CONFIG_SRCDIR([src/main.c])
diff -Nru lbzip2-2.5/debian/patches/series lbzip2-
2.5/debian/patches/series
--- lbzip2-2.5/debian/patches/series1969-12-31 19:00:00.0
-0500
+++ lbzip2-2.5/debian/patches/series2021-02-04 16:36:49.0
-0500
@@ -0,0 +1 @@
+0001-configure.ac-Bump-AC_PREREQ-to-2.64.patch


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

Processed: lbzip2: diff for NMU version 2.5-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 980655 + patch
Bug #980655 [src:lbzip2] lbzip2: FTBFS: /usr/bin/gnulib-tool: *** minimum 
supported autoconf version is 2.64. Try adding AC_PREREQ([2.64]) to your 
configure.ac.
Added tag(s) patch.
> tags 980655 + pending
Bug #980655 [src:lbzip2] lbzip2: FTBFS: /usr/bin/gnulib-tool: *** minimum 
supported autoconf version is 2.64. Try adding AC_PREREQ([2.64]) to your 
configure.ac.
Added tag(s) pending.

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

Processed: cdrkit: diff for NMU version 9:1.1.11-3.2

[Debian Bug Tracking System]

Processing control commands:

> tags 957074 + patch
Bug #957074 [src:cdrkit] cdrkit: ftbfs with GCC-10
Added tag(s) patch.

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

Bug#957074: cdrkit: diff for NMU version 9:1.1.11-3.2

[Sebastian Ramacher]

Control: tags 957074 + patch

Dear maintainer,

the ITA bug has been filed, but nothing happended since then. So I've
prepared an NMU for cdrkit (versioned as 9:1.1.11-3.2). The diff is
attached to this message.

Cheers
-- 
Sebastian Ramacher
diff -Nru cdrkit-1.1.11/debian/changelog cdrkit-1.1.11/debian/changelog
--- cdrkit-1.1.11/debian/changelog	2020-01-09 20:22:43.0 +0100
+++ cdrkit-1.1.11/debian/changelog	2021-02-04 22:36:29.0 +0100
@@ -1,3 +1,11 @@
+cdrkit (9:1.1.11-3.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/patches: Apply patch from Fedora to fix build with GCC 10 (Closes:
+#957074)
+
+ -- Sebastian Ramacher   Thu, 04 Feb 2021 22:36:29 +0100
+
 cdrkit (9:1.1.11-3.1) unstable; urgency=medium
 
   * Non-maintainer upload (With Steve approval).
diff -Nru cdrkit-1.1.11/debian/patches/gcc10.patch cdrkit-1.1.11/debian/patches/gcc10.patch
--- cdrkit-1.1.11/debian/patches/gcc10.patch	1970-01-01 01:00:00.0 +0100
+++ cdrkit-1.1.11/debian/patches/gcc10.patch	2021-02-04 22:35:26.0 +0100
@@ -0,0 +1,12 @@
+diff -up cdrkit-1.1.11/genisoimage/genisoimage.h.me cdrkit-1.1.11/genisoimage/genisoimage.h
+--- cdrkit-1.1.11/genisoimage/genisoimage.h.me	2020-02-24 15:10:35.542998992 +0100
 cdrkit-1.1.11/genisoimage/genisoimage.h	2020-02-24 15:10:50.011130450 +0100
+@@ -377,7 +377,7 @@ extern int	use_fileversion;
+ extern int	split_SL_component;
+ extern int	split_SL_field;
+ extern char	*trans_tbl;
+-char		*outfile;
++extern char	*outfile;
+ 
+ #define	JMAX		64	/* maximum Joliet file name length (spec) */
+ #define	JLONGMAX	103	/* out of spec Joliet file name length */
diff -Nru cdrkit-1.1.11/debian/patches/series cdrkit-1.1.11/debian/patches/series
--- cdrkit-1.1.11/debian/patches/series	2020-01-09 18:36:13.0 +0100
+++ cdrkit-1.1.11/debian/patches/series	2021-02-04 22:35:33.0 +0100
@@ -2,3 +2,4 @@
 fix_typo.patch
 fix_libcap_detection.patch
 add-efi-boot.patch
+gcc10.patch


signature.asc
Description: PGP signature

Bug#981905: mysql-8.0: missing runtime dependency on -dev package

[Gianfranco Costamagna]

Source: mysql-8.0
Version: 8.0.23-1
Severity: serious
tags: patch

Hello, the dev package exposes zstd build flags, but doesn't depend on it.
e.g. you can see boinc build log failing

checking mysql libraries... -L/usr/lib/x86_64-linux-gnu -lmysqlclient -lpthread 
-lz -lzstd -lm -lrt -lssl -lcrypto -ldl -lresolv
checking mysql includes... -I/usr/include/mysql 
[...]
libtool: link: /usr/bin/g++ -Wall -Wextra -Wshadow -Wredundant-decls 
-Wdisabled-optimization -Wpointer-arith -Wstrict-aliasing -Wcast-align -g -O2 
-ffile-prefix-map=/<>/boinc-7.16.16+dfsg=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -O3 -funroll-loops -fforce-addr 
-ffast-math -flto -Wall -Wl,-Bsymbolic-functions -Wl,-z -Wl,relro -Wl,-z 
-Wl,now -Wl,--as-needed -flto -g -O2 
-ffile-prefix-map=/<>/boinc-7.16.16+dfsg=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -O3 -funroll-loops -fforce-addr 
-ffast-math -flto -o .libs/adjust_user_priority adjust_user_priority.o  
../sched/.libs/libsched.so ../lib/.libs/libboinc_crypt.so 
../lib/.libs/libboinc.so -L/usr/lib/x86_64-linux-gnu -lmysqlclient -lpthread 
-lz -lzstd -lm -lrt -ldl -lresolv -lssl -lcrypto -pthread
/usr/bin/ld: cannot find -lzstd
collect2: error: ld returned 1 exit status


this patch should do the trick
diff -Nru mysql-8.0-8.0.23/debian/control mysql-8.0-8.0.23/debian/control
--- mysql-8.0-8.0.23/debian/control 2021-01-19 15:07:46.0 +0100
+++ mysql-8.0-8.0.23/debian/control 2021-02-04 22:30:12.0 +0100
@@ -62,6 +62,7 @@
 Section: libdevel
 Depends: libmysqlclient21 (= ${binary:Version}),
  libssl-dev,
+ libzstd-dev,
  zlib1g-dev,
  ${misc:Depends},
  ${shlibs:Depends}


Gianfranco

Processed: Re: Bug#978667: libv4l-dev: ioctl(rfd, VIDIOC_QBUF, &rbuf) fails

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #978667 [libv4l-dev] libv4l-dev: ioctl(rfd, VIDIOC_QBUF, &rbuf) fails
Severity set to 'normal' from 'serious'
> tags -1 moreinfo
Bug #978667 [libv4l-dev] libv4l-dev: ioctl(rfd, VIDIOC_QBUF, &rbuf) fails
Added tag(s) moreinfo.

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

Bug#978667: libv4l-dev: ioctl(rfd, VIDIOC_QBUF, &rbuf) fails

[Sebastian Ramacher]

Control: severity -1 normal
Control: tags -1 moreinfo

On 2020-12-29 15:55:11 -0500, william wrote:
> Package: libv4l-dev
> Version: 1.16.3-3
> Severity: serious
> Justification: Policy 2.5 - important - Unix is a multi-port operating system
> 
> Dear Maintainer,
> 
> 
>* What led up to the situation?
>  Attempted to open access to a second device (camera)
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
>  wrote the attached program which minimally opens the stream from the second 
> camera
>* What was the outcome of this action?
>  The program reportes that although the first camera was accessible, 
> identical code opening a stream for a second camera was not successful
>* What outcome did you expect instead?
>  Expected ioctl to return r==0, indicating successful system call

I'm afraid that this bug reports lacks a lot of information and does not
qualify as release critical. Does the second camera work if you switch
ports? Also this package does not implement handling of the ioctl, so
this bug would need to be assigned elsewhere.

Cheers

> 
> 
> -- System Information:
> Debian Release: 10.7
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'stable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.19.0-13-amd64 (SMP w/8 CPU cores)
> Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
> TAINT_UNSIGNED_MODULE
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE= 
> (charmap=UTF-8)
> Shell: /bin/sh linked to /usr/bin/dash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 
> Versions of packages libv4l-dev depends on:
> ii  libv4l-01.16.3-3
> ii  libv4l2rds0 1.16.3-3
> ii  libv4lconvert0  1.16.3-3
> 
> libv4l-dev recommends no packages.
> 
> Versions of packages libv4l-dev suggests:
> ii  pkg-config  0.29-6
> 
> -- no debconf information

-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#981903: puppetdb: autopkgtest failure

[Adrian Bunk]

Source: puppetdb
Version: 6.2.0-5
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/p/puppetdb/10223214/log.gz

...
autopkgtest [03:52:37]: test puppet: [---
Adding user `puppetdb' to group `puppet' ...
Adding user puppetdb to group puppet
Done.
Waiting for PuppetDB to start
Timed out
cp: cannot stat '/var/log/puppetdb/puppetdb.log': No such file or directory
autopkgtest [03:54:46]: test puppet: ---]
autopkgtest [03:54:46]: test puppet:  - - - - - - - - - - results - - - - - - - 
- - -
puppet   FAIL non-zero exit status 1
autopkgtest [03:54:47]: test puppet:  - - - - - - - - - - stderr - - - - - - - 
- - -
cp: cannot stat '/var/log/puppetdb/puppetdb.log': No such file or directory
autopkgtest [03:54:47]:  summary
standalone   FAIL non-zero exit status 1
puppet   FAIL non-zero exit status 1

Bug#981902: facterdb: autopkgtest failure

[Adrian Bunk]

Source: facterdb
Version: 1.6.0-2
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/f/facterdb/10218718/log.gz

...
Failures:

  1) FacterDB.facterdb_fact_files returns the deduplicated combination of 
.default_fact_files and .external_fact_files
 Failure/Error: expect(facterdb_fact_files.count).to 
eq(described_class.default_fact_files.count)

   expected: 1577
got: 1702

   (compared using ==)
 # ./spec/facterdb_spec.rb:153:in `block (3 levels) in '

  2) Default Facts 
../../../../../usr/share/rubygems-integration/all/gems/facterdb-1.6.0/facts/2.2/archlinux-x86_64.facts
 contains an ipaddress fact
 Failure/Error: expect(content['ipaddress']).to not_be_nil.and not_be_empty

  expected: not nil
   got: nil

   ...and:

  expected nil to respond to `empty?`
 # ./spec/facts_spec.rb:105:in `block (4 levels) in '

  3) Default Facts 
../../../../../usr/share/rubygems-integration/all/gems/facterdb-1.6.0/facts/3.2/aix-53-powerpc.facts
 contains an ipaddress fact
 Failure/Error: expect(content['ipaddress']).to not_be_nil.and not_be_empty

  expected: not nil
   got: nil

   ...and:

  expected nil to respond to `empty?`
 # ./spec/facts_spec.rb:105:in `block (4 levels) in '

  4) Default Facts 
../../../../../usr/share/rubygems-integration/all/gems/facterdb-1.6.0/facts/3.2/aix-61-powerpc.facts
 contains an ipaddress fact
 Failure/Error: expect(content['ipaddress']).to not_be_nil.and not_be_empty

  expected: not nil
   got: nil

   ...and:

  expected nil to respond to `empty?`
 # ./spec/facts_spec.rb:105:in `block (4 levels) in '

  5) Default Facts 
../../../../../usr/share/rubygems-integration/all/gems/facterdb-1.6.0/facts/3.2/aix-71-powerpc.facts
 contains an ipaddress fact
 Failure/Error: expect(content['ipaddress']).to not_be_nil.and not_be_empty

  expected: not nil
   got: nil

   ...and:

  expected nil to respond to `empty?`
 # ./spec/facts_spec.rb:105:in `block (4 levels) in '

  6) Default Facts 
../../../../../usr/share/rubygems-integration/all/gems/facterdb-1.6.0/facts/1.7/archlinux-x86_64.facts
 contains an ipaddress fact
 Failure/Error: expect(content['ipaddress']).to not_be_nil.and not_be_empty

  expected: not nil
   got: nil

   ...and:

  expected nil to respond to `empty?`
 # ./spec/facts_spec.rb:105:in `block (4 levels) in '

  7) Default Facts 
../../../../../usr/share/rubygems-integration/all/gems/facterdb-1.6.0/facts/2.1/archlinux-x86_64.facts
 contains an ipaddress fact
 Failure/Error: expect(content['ipaddress']).to not_be_nil.and not_be_empty

  expected: not nil
   got: nil

   ...and:

  expected nil to respond to `empty?`
 # ./spec/facts_spec.rb:105:in `block (4 levels) in '

  8) Default Facts 
../../../../../usr/share/rubygems-integration/all/gems/facterdb-1.6.0/facts/2.3/archlinux-x86_64.facts
 contains an ipaddress fact
 Failure/Error: expect(content['ipaddress']).to not_be_nil.and not_be_empty

  expected: not nil
   got: nil

   ...and:

  expected nil to respond to `empty?`
 # ./spec/facts_spec.rb:105:in `block (4 levels) in '

  9) Default Facts 
../../../../../usr/share/rubygems-integration/all/gems/facterdb-1.6.0/facts/3.0/ubuntu-15.10-x86_64.facts
 contains an ipaddress fact
 Failure/Error: expect(content['ipaddress']).to not_be_nil.and not_be_empty

  expected: not nil
   got: nil

   ...and:

  expected nil to respond to `empty?`
 # ./spec/facts_spec.rb:105:in `block (4 levels) in '

  10) Default Facts 
../../../../../usr/share/rubygems-integration/all/gems/facterdb-1.6.0/facts/3.0/ubuntu-15.10-i386.facts
 contains an ipaddress fact
  Failure/Error: expect(content['ipaddress']).to not_be_nil.and not_be_empty

   expected: not nil
got: nil

...and:

   expected nil to respond to `empty?`
  # ./spec/facts_spec.rb:105:in `block (4 levels) in '

  11) Default Facts 
../../../../../usr/share/rubygems-integration/all/gems/facterdb-1.6.0/facts/2.4/archlinux-x86_64.facts
 contains an ipaddress fact
  Failure/Error: expect(content['ipaddress']).to not_be_nil.and not_be_empty

   expected: not nil
got: nil

...and:

   expected nil to respond to `empty?`
  # ./spec/facts_spec.rb:105:in `block (4 levels) in '

  12) Default Facts 
../../../../../usr/share/rubygems-integration/all/gems/facterdb-1.6.0/facts/3.6/pcs-6-x86_64.facts
 contains an ipaddress fact
  Failure/Error: expect(content['ipaddress']).to not_be_nil.and not_be_empty

   expected: not nil
got: nil

...and:

   expected nil to respond to `empty?`
  # ./spec/facts_spec.rb:105:in `block (4 levels) in '

  13) Defau

Bug#949638: marked as done (tesseract: uses -march=native)

[Debian Bug Tracking System]

Your message dated Thu, 04 Feb 2021 21:19:17 +
with message-id 
and subject line Bug#949638: fixed in tesseract 4.1.1-2.1
has caused the Debian Bug report #949638,
regarding tesseract: uses -march=native
to be marked as done.

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

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


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

Package: tesseract
Version: 4.1.0-1
Severity: serious
Tags: patch

I recently discovered that tesseract 4.1.1-1 failed the armv7 contamination 
check we run in raspbian.

Investigating shows that since version 4.1.0-1 tesseract started using 
-march=native. This compiler option is totally inappropriate for a binary 
distribution like Debian or Raspbian, because it means that the minimum CPU 
requirements of the resulting binaries will depend on what CPU the buildbox 
happens to have.

4.1.0-1 was never built in raspbian, I am not sure why 4.1.0-2 passed the 
contamination check in raspbian. My best guess is that -march=native on arm is 
poorly implemented and does not recognise the CPUs on some of our buildboxes.

Anyway I whipped up a fix and uploaded it to raspbian. A debdiff should appear 
soon at https://debdiffs.raspbian.org/main/t/tessarect/
--- End Message ---
--- Begin Message ---
Source: tesseract
Source-Version: 4.1.1-2.1
Done: Paul Gevers 

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

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

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

Debian distribution maintenance software
pp.
Paul Gevers  (supplier of updated tesseract package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 04 Feb 2021 21:49:33 +0100
Source: tesseract
Architecture: source
Version: 4.1.1-2.1
Distribution: unstable
Urgency: medium
Maintainer: Alexander Pozdnyakov 
Changed-By: Paul Gevers 
Closes: 949638
Changes:
 tesseract (4.1.1-2.1) unstable; urgency=medium
 .
   [ Peter Green ]
   * Edit configure.ac to disable -march=native (Closes: #949638)
   * Edit control/rules to enable autoreconf.
Checksums-Sha1:
 7553d8980e226c710116b96ac8532dec2725e2e6 2109 tesseract_4.1.1-2.1.dsc
 4e4a019a2eaa76c7cc2c5320025d131530fdb473 53876 
tesseract_4.1.1-2.1.debian.tar.xz
Checksums-Sha256:
 f61830e0f2503859f3f496a2708cbc2616b77645c0d628e0df504b07ec39da70 2109 
tesseract_4.1.1-2.1.dsc
 4db7966c045c6bf015de3d506b973bb7d986abfda652fbf0bc25537daf1d8ec1 53876 
tesseract_4.1.1-2.1.debian.tar.xz
Files:
 a9d2aff381b35f432c84c225302ca929 2109 graphics optional tesseract_4.1.1-2.1.dsc
 68d89e8a4bbb4670e5d72e3d39905ea4 53876 graphics optional 
tesseract_4.1.1-2.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmAcYfsACgkQnFyZ6wW9
dQqp2gf/RCYora1ZlmHjunlhooLndBbCdapm+yP+nhatZdz/o2S7ShIjicPMg6vl
ADOf8xi3XhZd+nmoshIUlT0TCC2ePgU6VyjaeME2sKScXXKr9ItCAxp8V+UWF3p9
xVW5DbK7767MDkQUF3UIXoukIShZS4yqsmhnOZk+LDvkaBLt3G7W5oEmq2+rscrh
2FzKRoZitPT8sifY/ANQ3lAvv8j9upJpyBIqecfaHnKnHLIXel1VFSLOnXwTrW0S
Jfchzt1PgSI+tN9dftpl9JYTXEkSh6e3fi1ZbxWuECLjk/r1MfC4g+jUWl8CFXzs
fJIthS+WlMJVH96wgzznKS1aoiURxQ==
=tqnl
-END PGP SIGNATURE End Message ---

Bug#949638: debdiff for 949638 "tesseract: uses -march=native"

[Paul Gevers]

Dear maintainer,

I have just uploaded tesseract to the archive to fix this bug. debdiff
based on the work of plugwash attached.

Paul
diff -Nru tesseract-4.1.1/debian/changelog tesseract-4.1.1/debian/changelog
--- tesseract-4.1.1/debian/changelog2020-01-19 06:48:59.0 +0100
+++ tesseract-4.1.1/debian/changelog2021-02-04 21:49:33.0 +0100
@@ -1,3 +1,11 @@
+tesseract (4.1.1-2.1) unstable; urgency=medium
+
+  [ Peter Green ]
+  * Edit configure.ac to disable -march=native (Closes: #949638)
+  * Edit control/rules to enable autoreconf.
+
+ -- Paul Gevers   Thu, 04 Feb 2021 21:49:33 +0100
+
 tesseract (4.1.1-2) unstable; urgency=medium
 
   * Update debian/control:
diff -Nru tesseract-4.1.1/debian/control tesseract-4.1.1/debian/control
--- tesseract-4.1.1/debian/control  2020-01-19 06:47:02.0 +0100
+++ tesseract-4.1.1/debian/control  2021-02-04 21:49:33.0 +0100
@@ -5,7 +5,7 @@
 Build-Depends: debhelper (>= 9), libleptonica-dev (>= 1.75.3),
automake, libtool, libarchive-dev, libpango1.0-dev, 
libcairo2-dev, libicu-dev,
libpng-dev, libjpeg-dev, libtiff-dev, zlib1g-dev, git, 
autoconf-archive, asciidoc,
-   xsltproc, docbook-xsl, docbook-xml, tesseract-ocr-eng (>= 4.00~)
+   xsltproc, docbook-xsl, docbook-xml, tesseract-ocr-eng (>= 
4.00~), dh-autoreconf
 Standards-Version: 4.4.1
 Homepage: https://github.com/tesseract-ocr/
 Vcs-Git: https://github.com/AlexanderP/tesseract-debian.git
diff -Nru tesseract-4.1.1/debian/patches/no-march-native 
tesseract-4.1.1/debian/patches/no-march-native
--- tesseract-4.1.1/debian/patches/no-march-native  1970-01-01 
01:00:00.0 +0100
+++ tesseract-4.1.1/debian/patches/no-march-native  2021-02-04 
21:49:33.0 +0100
@@ -0,0 +1,28 @@
+Description:  Edit configure.ac to disable -march=native
+ -march=native is inappropriate for a binary distribution like Debian.
+Author: Peter Michael Green 
+
+---
+The information above should follow the Patch Tagging Guidelines, please
+checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here
+are templates for supplementary fields that you might want to add:
+
+Origin: , 
+Bug: 
+Bug-Debian: https://bugs.debian.org/
+Bug-Ubuntu: https://launchpad.net/bugs/
+Forwarded: 
+Reviewed-By: 
+Last-Update: 2020-01-23
+
+--- tesseract-4.1.1.orig/configure.ac
 tesseract-4.1.1/configure.ac
+@@ -136,7 +136,7 @@ AM_CONDITIONAL([FMA_OPT], $fma)
+ AX_CHECK_COMPILE_FLAG([-msse4.1], [sse41=true], [sse41=false], [$WERROR])
+ AM_CONDITIONAL([SSE41_OPT], $sse41)
+ 
+-AX_CHECK_COMPILE_FLAG([-march=native], [arch_native=true], 
[arch_native=false], [$WERROR])
++AX_CHECK_COMPILE_FLAG([-march=native], [arch_native=false], 
[arch_native=false], [$WERROR])
+ AM_CONDITIONAL([MARCH_NATIVE_OPT], $arch_native)
+ 
+ AC_ARG_WITH([extra-includes],
diff -Nru tesseract-4.1.1/debian/patches/series 
tesseract-4.1.1/debian/patches/series
--- tesseract-4.1.1/debian/patches/series   2019-12-26 21:46:07.0 
+0100
+++ tesseract-4.1.1/debian/patches/series   2021-02-04 21:49:33.0 
+0100
@@ -2,3 +2,4 @@
 #fix-up-headers
 helptext
 #shebang.diff
+no-march-native
diff -Nru tesseract-4.1.1/debian/rules tesseract-4.1.1/debian/rules
--- tesseract-4.1.1/debian/rules2019-12-26 21:46:07.0 +0100
+++ tesseract-4.1.1/debian/rules2021-02-04 21:49:33.0 +0100
@@ -16,7 +16,7 @@
 endif
 
 %:
-   dh $@ --parallel
+   dh $@ --parallel --with autoreconf
 
 override_dh_auto_build:
make -j$(NUMJOBS)


OpenPGP_signature
Description: OpenPGP digital signature

Bug#981900: s3ql: autopkgtest failure: No module named 'pytest_trio'

[Adrian Bunk]

Source: s3ql
Version: 3.7.0+dfsg-1
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/s/s3ql/10265797/log.gz

...
autopkgtest [16:12:24]: test upstream-standard: [---
ImportError while loading conftest 
'/tmp/autopkgtest-lxc.weivh3tb/downtmp/build.pvb/src/tests/conftest.py'.
tests/conftest.py:22: in 
import pytest_trio
E   ModuleNotFoundError: No module named 'pytest_trio'
autopkgtest [16:12:25]: test upstream-standard: ---]
autopkgtest [16:12:26]: test upstream-standard:  - - - - - - - - - - results - 
- - - - - - - - -
upstream-standardFAIL non-zero exit status 4
autopkgtest [16:12:26]: test upstream-standard:  - - - - - - - - - - stderr - - 
- - - - - - - -
ImportError while loading conftest 
'/tmp/autopkgtest-lxc.weivh3tb/downtmp/build.pvb/src/tests/conftest.py'.
tests/conftest.py:22: in 
import pytest_trio
E   ModuleNotFoundError: No module named 'pytest_trio'
autopkgtest [16:12:26]: test upstream-with-fuse: preparing testbed
Reading package lists...
Building dependency tree...
Reading state information...
Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up autopkgtest-satdep (0) ...
(Reading database ... 15096 files and directories currently installed.)
Removing autopkgtest-satdep (0) ...
autopkgtest [16:12:30]: test upstream-with-fuse: [---
ImportError while loading conftest 
'/tmp/autopkgtest-lxc.weivh3tb/downtmp/build.pvb/src/tests/conftest.py'.
tests/conftest.py:22: in 
import pytest_trio
E   ModuleNotFoundError: No module named 'pytest_trio'
autopkgtest [16:12:31]: test upstream-with-fuse: ---]
autopkgtest [16:12:31]: test upstream-with-fuse:  - - - - - - - - - - results - 
- - - - - - - - -
upstream-with-fuse   FAIL non-zero exit status 4
autopkgtest [16:12:31]: test upstream-with-fuse:  - - - - - - - - - - stderr - 
- - - - - - - - -
ImportError while loading conftest 
'/tmp/autopkgtest-lxc.weivh3tb/downtmp/build.pvb/src/tests/conftest.py'.
tests/conftest.py:22: in 
import pytest_trio
E   ModuleNotFoundError: No module named 'pytest_trio'
autopkgtest [16:12:32]:  summary
upstream-standardFAIL non-zero exit status 4
upstream-with-fuse   FAIL non-zero exit status 4

Bug#981899: adequate: autopkgtest failure

[Adrian Bunk]

Source: adequate
Version: 0.15.4
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/a/adequate/10235236/log.gz

...
./run-tests adequate-testpkg_1_amd64.changes
install adequate-testpkg-bin-or-sbin-binary-requires-usr-lib-library ... ok
check adequate-testpkg-bin-or-sbin-binary-requires-usr-lib-library ... FAIL
-adequate-testpkg-bin-or-sbin-binary-requires-usr-lib-library: 
bin-or-sbin-binary-requires-usr-lib-library /bin/adequate-usrlib1 => 
/usr/lib/libadequate-usrlib.so.0
-adequate-testpkg-bin-or-sbin-binary-requires-usr-lib-library: 
bin-or-sbin-binary-requires-usr-lib-library /sbin/adequate-usrlib2 => 
/usr/lib/libadequate-usrlib.so.0
remove adequate-testpkg-bin-or-sbin-binary-requires-usr-lib-library ... ok
install adequate-testpkg-broken-symlink ... ok
check adequate-testpkg-broken-symlink ... ok
remove adequate-testpkg-broken-symlink ... ok
install adequate-testpkg-incompatible-licenses ... ok
check adequate-testpkg-incompatible-licenses ... ok
remove adequate-testpkg-incompatible-licenses ... ok
install adequate-testpkg-incompatible-licenses-dep5 ... ok
check adequate-testpkg-incompatible-licenses-dep5 ... ok
remove adequate-testpkg-incompatible-licenses-dep5 ... ok
install adequate-testpkg-library-not-found ... ok
check adequate-testpkg-library-not-found ... ok
remove adequate-testpkg-library-not-found ... ok
install adequate-testpkg-missing-alternative ... ok
check adequate-testpkg-missing-alternative ... ok
remove adequate-testpkg-missing-alternative ... ok
install adequate-testpkg-missing-copyright-file ... ok
check adequate-testpkg-missing-copyright-file ... ok
remove adequate-testpkg-missing-copyright-file ... ok
install adequate-testpkg-missing-pkgconfig-dependency ... ok
check adequate-testpkg-missing-pkgconfig-dependency ... ok
remove adequate-testpkg-missing-pkgconfig-dependency ... ok
install adequate-testpkg-missing-symbol-version-information ... ok
check adequate-testpkg-missing-symbol-version-information ... ERROR (non-empty 
stderr)
! adequate: ldd -r /usr/bin/adequate-test-msvi: Inconsistency detected by 
ld.so: dl-lookup.c: 111: check_match: Assertion `version->filename == NULL || ! 
_dl_name_match_p (version->filename, map)' failed!
remove adequate-testpkg-missing-symbol-version-information ... ok
install adequate-testpkg-obsolete-conffile (1) ... ok
check adequate-testpkg-obsolete-conffile ... ok
upgrade adequate-testpkg-obsolete-conffile (1 => 2) ... ok
check adequate-testpkg-obsolete-conffile ... ok
remove adequate-testpkg-obsolete-conffile ... ok
install adequate-testpkg-program-name-collision ... ok
check adequate-testpkg-program-name-collision ... FAIL
 adequate-testpkg-program-name-collision: program-name-collision 
/usr/games/true (bash builtin command)
 adequate-testpkg-program-name-collision: program-name-collision 
/usr/games/true /bin/true
+adequate-testpkg-program-name-collision: program-name-collision 
/usr/games/true /usr/bin/true
remove adequate-testpkg-program-name-collision ... ok
install adequate-testpkg-py-file-not-bytecompiled ... ok
check adequate-testpkg-py-file-not-bytecompiled ... ok
remove adequate-testpkg-py-file-not-bytecompiled ... ok
install adequate-testpkg-symbol-size-mismatch ... ok
check adequate-testpkg-symbol-size-mismatch ... ok
remove adequate-testpkg-symbol-size-mismatch ... ok
install adequate-testpkg-undefined-symbol ... ok
check adequate-testpkg-undefined-symbol ... FAIL
-adequate-testpkg-undefined-symbol: undefined-symbol /usr/bin/adequate-test-us1 
=> this_symbol_might_be_undefined
-adequate-testpkg-undefined-symbol: undefined-symbol /usr/bin/adequate-test-us2 
=> this_symbol_might_be_undefined@ADEQUATE_TEST 
(libadequate-test-versioning.so.0)
+adequate-testpkg-undefined-symbol: undefined-symbol /usr/bin/adequate-test-us2 
=> this_symbol_might_be_undefined@ADEQUATE_TEST
remove adequate-testpkg-undefined-symbol ... ok
make: *** [Makefile:15: run] Error 1
autopkgtest [11:55:28]: test full-test: ---]
autopkgtest [11:55:28]: test full-test:  - - - - - - - - - - results - - - - - 
- - - - -
full-testFAIL non-zero exit status 2
autopkgtest [11:55:28]: test full-test:  - - - - - - - - - - stderr - - - - - - 
- - - -
make: *** [Makefile:15: run] Error 1
autopkgtest [11:55:29]:  summary
smoke-test   PASS
full-testFAIL non-zero exit status 2

Bug#979244: 關於 Debian 中 moblin 的老套件.

[Ying-Chun Liu (PaulLiu)]

Hi Baptiste,

Yes. True.

We should submit a bug for  that.


Yours,

Paul

Baptiste Beauplat 於 2021/2/3 上午3:16 寫道:
> Hi PaulLiu,
>
>
> If I'm not mistaken, I think you forgot to open the RM bug for
> moblin-sound-theme.
>



OpenPGP_signature
Description: OpenPGP digital signature

Bug#981898: python-fsquota: autopkgtest failure: No module named 'fsquota'

[Adrian Bunk]

Source: python-fsquota
Version: 0.1.0+dfsg1-1
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-fsquota/10254027/log.gz

...
autopkgtest [05:38:58]: test autodep8-python3: set -e ; for py in $(py3versions 
-d 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing with $py:" ; $py -c 
"import fsquota; print(fsquota)" ; done
autopkgtest [05:38:58]: test autodep8-python3: [---
Testing with python3.9:
Traceback (most recent call last):
  File "", line 1, in 
ModuleNotFoundError: No module named 'fsquota'
autopkgtest [05:39:01]: test autodep8-python3: ---]
autopkgtest [05:39:01]: test autodep8-python3:  - - - - - - - - - - results - - 
- - - - - - - -
autodep8-python3 FAIL non-zero exit status 1
autopkgtest [05:39:01]:  summary
autodep8-python3 FAIL non-zero exit status 1

Processed: Re: doesn't run: 'xml.etree.ElementTree.Element' object has no attribute 'getchildren'

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #977324 [ocrfeeder] doesn't run: 'xml.etree.ElementTree.Element' object has 
no attribute 'getchildren'
Severity set to 'grave' from 'important'
> tag -1 + patch
Bug #977324 [ocrfeeder] doesn't run: 'xml.etree.ElementTree.Element' object has 
no attribute 'getchildren'
Added tag(s) patch.

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

Bug#981897: put-dns: Removing package fails

[Adrian Bunk]

Package: put-dns
Version: 0.0.2-1
Severity: serious

https://piuparts.debian.org/sid/fail/put-dns_0.0.2-1.log

...
  Removing put-dns (0.0.2-1) ...
  rmdir: failed to remove '/var/lib/put-dns': No such file or directory
  dpkg: error processing package put-dns (--remove):
   installed put-dns package post-removal script subprocess returned error exit 
status 1
  dpkg: too many errors, stopping
  Errors were encountered while processing:
   put-dns
  Processing was halted because there were too many errors.
  E: Sub-process /usr/bin/dpkg returned an error code (1)

Bug#981894: go-dlib FTBFS: test failure

[Adrian Bunk]

Source: go-dlib
Version: 5.6.0.9+dfsg-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=go-dlib&arch=all&ver=5.6.0.9%2Bdfsg-1&stamp=1612409395&raw=0

...
FAIL: group_test.go:57: testWrapper.TestGetGroupEntry

group_test.go:60:
c.Check(groups[0].Name, C.Equals, "root")
... obtained string = "porter-any"
... expected string = "root"

OOPS: 2 passed, 1 FAILED
--- FAIL: Test (0.00s)
FAIL
FAILpkg.deepin.io/lib/users/group   0.019s
...

Bug#958597: marked as done (pmacct: Build-Depends on deprecated dh-systemd which is going away)

[Debian Bug Tracking System]

Your message dated Thu, 04 Feb 2021 20:26:05 +
with message-id 
and subject line Bug#958597: fixed in pmacct 1.7.5-2
has caused the Debian Bug report #958597,
regarding pmacct: Build-Depends on deprecated dh-systemd which is going away
to be marked as done.

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

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


-- 
958597: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958597
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pmacct
Severity: normal
User: pkg-systemd-maintain...@lists.alioth.debian.org
Usertags: dh-systemd-removal

Hi,

your package pmacct declares a build dependency on dh-systemd.
dh-systemd was merged into debhelper in version 9.20160709 [1] and since
stretch, dh-systemd is an empty transitional package.

For bullseye we intend to drop this empty transitional package.

Once we drop dh-systemd, this bug report will become RC.

Please update your package accordingly. The change should be as simple as
replacing the build dependency on dh-systemd with a build dependency on
debhelper (>= 9.20160709).

Regards,
Michael

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822670
--- End Message ---
--- Begin Message ---
Source: pmacct
Source-Version: 1.7.5-2
Done: Adrian Bunk 

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated pmacct 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, 04 Feb 2021 22:02:20 +0200
Source: pmacct
Architecture: source
Version: 1.7.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Adrian Bunk 
Closes: 958597
Changes:
 pmacct (1.7.5-2) unstable; urgency=medium
 .
   * QA upload.
   * Removed build dependency on obsolete dh-systemd. (Closes: #958597)
Checksums-Sha1:
 3c68bdf059f8e74234728ab309c07e32c53eddfb 2057 pmacct_1.7.5-2.dsc
 cf0bfc0c348c1375399fa26e5bb90cb1e9152f6e 12808 pmacct_1.7.5-2.debian.tar.xz
Checksums-Sha256:
 80a91c6e34b09f0de911c9155ef56102de2271d72e17ac3aeb4f055bb16a94bf 2057 
pmacct_1.7.5-2.dsc
 2e28dcaa1b29638fc38ea8666384f2f7f296034d2d9a6335686f6cce2417ce89 12808 
pmacct_1.7.5-2.debian.tar.xz
Files:
 399b6a83f7fe997f5c773004292a03ed 2057 net optional pmacct_1.7.5-2.dsc
 3f6447d64eff3afeb5e6025e477f2a4b 12808 net optional 
pmacct_1.7.5-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmAcU+AACgkQiNJCh6LY
mLFDLRAAkdlLJaJbMD4IBLXaMI3U1SnCkIBu4TZeVr7my/bTaKkUH1NDj1xY5W8E
XRdk1LoOs219JgkVm3sYsk8Lk6XDIhdCWocmN9I7xNhLALzT0D29WWwoviXpQttK
7ssUCYj+KrqQOOTP6YqHsoo/Y8pCzkv9IV7B+bP5rKc1TtbPawIKQhJSOXFAvPQb
bI78mCKp99pXQ5REkyZ2x61ToeTH+yFI5OYN9ey7JM873JOarc0qYQxCinMBcXhh
qW6oJ8NdKCMi9/sH2e2F+wpoe/jk7QKRxkPB6G+jMUjzJb26rh1l1xs8fqIwbgJw
nwjtZt2Gh/3wqWsVz1jcIffcpbPqOQlij+H6uV634icvt97eknB1f0G5GiKbuko3
CbvZR9dq/qBS62pSyjIVDZIsDypOUdcOvdykuaiE9YSOoTX0xaN1wrfw68tsDQw3
FsJ9SHxsBDyf1VyiyuVxPYGLRPk+CXVEK5KcoFvyvJFHfTt5rLWYXALzlyQww3C3
rc9baUJPKAuoqdw4MvbsOMorFgbPpQyN3Ilsf17g6KULaIUj+fmBy+OXfSOucNL7
TF5ExzffeFMsXTPUN/b83qSe5W2wnj80szqDCyFXPakZ3hSEEXRckOilR//tOEbI
dOLr0bfY9OQgQPQYTHP0LIA5f5qMJiKEXXQmhZHNEpD0004nxQk=
=7/HS
-END PGP SIGNATURE End Message ---

Bug#981891: paraview: autopkgtest failure: TypeError: Initialize argument 3: method requires a VTK object

[Adrian Bunk]

Source: paraview
Version: 5.9.0-1
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/p/paraview/10117274/log.gz

...
autopkgtest [03:43:55]: test paraviewtest.py: [---
Traceback (most recent call last):
  File 
"/tmp/autopkgtest-lxc.91pw_4ca/downtmp/build.hgG/src/debian/tests/paraviewtest.py",
 line 5, in 
from paraview.simple import *
  File "/usr/lib/python3/dist-packages/paraview/simple.py", line 41, in 
from paraview import servermanager
  File "/usr/lib/python3/dist-packages/paraview/servermanager.py", line 3290, 
in 
vtkInitializationHelper.Initialize(sys.executable,
TypeError: Initialize argument 3: method requires a VTK object
autopkgtest [03:44:06]: test paraviewtest.py: ---]
autopkgtest [03:44:06]: test paraviewtest.py:  - - - - - - - - - - results - - 
- - - - - - - -
paraviewtest.py  FAIL non-zero exit status 1
autopkgtest [03:44:06]: test paraviewtest.py:  - - - - - - - - - - stderr - - - 
- - - - - - -
Traceback (most recent call last):
  File 
"/tmp/autopkgtest-lxc.91pw_4ca/downtmp/build.hgG/src/debian/tests/paraviewtest.py",
 line 5, in 
from paraview.simple import *
  File "/usr/lib/python3/dist-packages/paraview/simple.py", line 41, in 
from paraview import servermanager
  File "/usr/lib/python3/dist-packages/paraview/servermanager.py", line 3290, 
in 
vtkInitializationHelper.Initialize(sys.executable,
TypeError: Initialize argument 3: method requires a VTK object
autopkgtest [03:44:07]:  summary
paraviewtest.py  FAIL non-zero exit status 1

Processed: affects 963737

[Debian Bug Tracking System]

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

> affects 963737 src:haskell-blogliterately
Bug #963737 [src:highlighting-kate] highlighting-kate: Removal notice: 
Deprecated
Added indication that 963737 affects src:haskell-blogliterately
> thanks
Stopping processing here.

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

Bug#981889: nomad: CVE-2021-3283

[Salvatore Bonaccorso]

Source: nomad
Version: 0.12.9+dfsg1-3
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for nomad.

CVE-2021-3283[0]:
| HashiCorp Nomad and Nomad Enterprise up to 0.12.9 exec and java task
| drivers can access processes associated with other tasks on the same
| node. Fixed in 0.12.10, and 1.0.3.

Some details are in [1] and said to be fixed in 0.12.10 for nomad.


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2021-3283
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3283
[1] 
https://discuss.hashicorp.com/t/hcsec-2021-01-nomad-s-exec-and-java-task-drivers-did-not-isolate-processes/20332

Regards,
Salvatore

Bug#981888: iwyu FTBFS on mipsel: Linking CXX executable bin/include-what-you-use fails

[Paul Gevers]

Source: iwyu
Version: 8.15-2
Severity: serious
Tags: ftbfs

Hi,

iwyu FTBFS on mispel.

https://buildd.debian.org/status/fetch.php?pkg=iwyu&arch=mipsel&ver=8.15-2&stamp=1612343226&raw=0

Maybe the relevant part is this:

[100%] Linking CXX executable bin/include-what-you-use
/usr/bin/cmake -E cmake_link_script
CMakeFiles/include-what-you-use.dir/link.txt --verbose=1
/usr/bin/c++  -fPIC -fno-shrink-wrap -fvisibility-inlines-hidden
-Werror=date-time -w -ffunction-sections -fdata-sections -Wl,-z,relro
-Wl,-rpath-link,  -Wl,-O3 -Wl,--gc-sections
CMakeFiles/include-what-you-use.dir/iwyu.cc.o
CMakeFiles/include-what-you-use.dir/iwyu_ast_util.cc.o
CMakeFiles/include-what-you-use.dir/iwyu_cache.cc.o
CMakeFiles/include-what-you-use.dir/iwyu_driver.cc.o
CMakeFiles/include-what-you-use.dir/iwyu_getopt.cc.o
CMakeFiles/include-what-you-use.dir/iwyu_globals.cc.o
CMakeFiles/include-what-you-use.dir/iwyu_include_picker.cc.o
CMakeFiles/include-what-you-use.dir/iwyu_lexer_utils.cc.o
CMakeFiles/include-what-you-use.dir/iwyu_location_util.cc.o
CMakeFiles/include-what-you-use.dir/iwyu_output.cc.o
CMakeFiles/include-what-you-use.dir/iwyu_path_util.cc.o
CMakeFiles/include-what-you-use.dir/iwyu_preprocessor.cc.o
CMakeFiles/include-what-you-use.dir/iwyu_verrs.cc.o -o
bin/include-what-you-use
-Wl,-rpath,"\$ORIGIN/../lib:/usr/lib/llvm-11/lib" -lpthread
/usr/lib/llvm-11/lib/libclang-cpp.so.11
/usr/lib/llvm-11/lib/libLLVM-11.so.1
CMakeFiles/include-what-you-use.dir/iwyu.cc.o: in function
`std::char_traits::compare(char const*, char const*, unsigned int)':
iwyu.cc:(.text._ZNSt11char_traitsIcE7compareEPKcS2_j[_ZNSt11char_traitsIcE7compareEPKcS2_j]+0x50):
relocation truncated to fit: R_MIPS_CALL16 against `memcmp@@GLIBC_2.0'
CMakeFiles/include-what-you-use.dir/iwyu.cc.o: in function
`std::__cxx11::to_string(int)':
iwyu.cc:(.text._ZNSt7__cxx119to_stringEi[_ZNSt7__cxx119to_stringEi]+0x90):
relocation truncated to fit: R_MIPS_CALL16 against
`std::allocator::allocator()@@GLIBCXX_3.4'
iwyu.cc:(.text._ZNSt7__cxx119to_stringEi[_ZNSt7__cxx119to_stringEi]+0xb8):
relocation truncated to fit: R_MIPS_CALL16 against
`std::__cxx11::basic_string,
std::allocator >::basic_string(unsigned int, char,
std::allocator const&)@@GLIBCXX_3.4.21'
iwyu.cc:(.text._ZNSt7__cxx119to_stringEi[_ZNSt7__cxx119to_stringEi]+0xd4):
relocation truncated to fit: R_MIPS_CALL16 against
`std::allocator::~allocator()@@GLIBCXX_3.4'
iwyu.cc:(.text._ZNSt7__cxx119to_stringEi[_ZNSt7__cxx119to_stringEi]+0xf4):
relocation truncated to fit: R_MIPS_CALL16 against
`std::__cxx11::basic_string,
std::allocator >::operator[](unsigned int)@@GLIBCXX_3.4.21'
CMakeFiles/include-what-you-use.dir/iwyu.cc.o: in function
`llvm::alignTo(unsigned long long, unsigned long long, unsigned long long)':
iwyu.cc:(.text._ZN4llvm7alignToEyyy[_ZN4llvm7alignToEyyy]+0x60):
relocation truncated to fit: R_MIPS_CALL16 against
`__assert_fail@@GLIBC_2.0'
iwyu.cc:(.text._ZN4llvm7alignToEyyy[_ZN4llvm7alignToEyyy]+0x78):
relocation truncated to fit: R_MIPS_CALL16 against `__umoddi3@@GLIBC_2.0'
iwyu.cc:(.text._ZN4llvm7alignToEyyy[_ZN4llvm7alignToEyyy]+0x118):
relocation truncated to fit: R_MIPS_CALL16 against `__udivdi3@@GLIBC_2.0'
CMakeFiles/include-what-you-use.dir/iwyu.cc.o: in function
`llvm::StringRef::strLen(char const*)':
iwyu.cc:(.text._ZN4llvm9StringRef6strLenEPKc[_ZN4llvm9StringRef6strLenEPKc]+0x28):
relocation truncated to fit: R_MIPS_CALL16 against `strlen@@GLIBC_2.0'
CMakeFiles/include-what-you-use.dir/iwyu.cc.o: in function
`llvm::StringRef::str[abi:cxx11]() const':
iwyu.cc:(.text._ZNK4llvm9StringRef3strB5cxx11Ev[_ZNK4llvm9StringRef3strB5cxx11Ev]+0x44):
relocation truncated to fit: R_MIPS_CALL16 against
`std::__cxx11::basic_string,
std::allocator >::basic_string()@@GLIBCXX_3.4.21'
iwyu.cc:(.text._ZNK4llvm9StringRef3strB5cxx11Ev[_ZNK4llvm9StringRef3strB5cxx11Ev]+0x78):
additional relocation overflows omitted from the output
collect2: error: ld returned 1 exit status
make[4]: *** [CMakeFiles/include-what-you-use.dir/build.make:288:
bin/include-what-you-use] Error 1
make[4]: Leaving directory '/<>/iwyu-build'
make[3]: *** [CMakeFiles/Makefile2:131:
CMakeFiles/include-what-you-use.dir/all] Error 2
make[3]: Leaving directory '/<>/iwyu-build'
make[2]: *** [Makefile:163: all] Error 2
make[2]: Leaving directory '/<>/iwyu-build'
dh_auto_build: error: cd iwyu-build && make -j4 "INSTALL=install
--strip-program=true" VERBOSE=1 returned exit code 2
make[1]: *** [debian/rules:29: override_dh_auto_build] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:21: build-arch] Error 2

Paul



OpenPGP_signature
Description: OpenPGP digital signature

Processed: Bug#976860 marked as pending in plaso

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #976860 [python3-plaso] python3-plaso: log2timeline.py + image_export.py 
always bail out with "ERROR: Unable to determine location of data files."
Ignoring request to alter tags of bug #976860 to the same tags previously set

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

Bug#976860: marked as pending in plaso

[Axel Beckert]

Control: tag -1 pending

Hello,

Bug #976860 in plaso 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/pkg-security-team/plaso/-/commit/a60908322089d8e3a5f6e78d7ebe3e87952aba3f


python3-plaso: Also install /usr/share/plaso/. (Closes: #976860)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/976860

Processed: tagging 976860

[Debian Bug Tracking System]

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

> tags 976860 + pending
Bug #976860 [python3-plaso] python3-plaso: log2timeline.py + image_export.py 
always bail out with "ERROR: Unable to determine location of data files."
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#981886: intellij-community-idea build depends on openjdk-8-jdk-headless that will not be in bullseye

[Adrian Bunk]

Source: intellij-community-idea
Version: 183.5153.4-2
Severity: serious
Tags: ftbfs

Migration status: Blocked. Can't migrate due to a non-migratable dependency. 
Check status below.
Build-Depends(-Arch): intellij-community-idea openjdk-8 (not considered)
Invalidated by build-dependency

Bug#981495: marked as done (screenkey: FTBFS: E: pybuild pybuild:353: clean: plugin distutils failed with: exit code=1: python3.9 setup.py clean)

[Debian Bug Tracking System]

Your message dated Thu, 04 Feb 2021 19:35:51 +
with message-id 
and subject line Bug#981495: fixed in screenkey 1:1.4-2
has caused the Debian Bug report #981495,
regarding screenkey: FTBFS: E: pybuild pybuild:353: clean: plugin distutils 
failed with: exit code=1: python3.9 setup.py clean
to be marked as done.

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

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


-- 
981495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981495
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: screenkey
Version: 1:1.4-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
X-Debbugs-Cc: sramac...@debian.org

| I: pybuild base:232: python3.9 setup.py clean 
| WARNING: The pip package is not available, falling back to EasyInstall for 
handling setup_requires/test_requires; this is deprecated and will be removed 
in a future version.
| Download error on https://pypi.org/simple/babel/: [Errno 111] Connection 
refused -- Some packages may not be found!
| Couldn't find index page for 'babel' (maybe misspelled?)
| Download error on https://pypi.org/simple/: [Errno 111] Connection refused -- 
Some packages may not be found!
| No local packages or working download links found for babel
| Traceback (most recent call last):
|   File "/usr/lib/python3/dist-packages/setuptools/installer.py", line 60, in 
fetch_build_egg
| pkg_resources.get_distribution('pip')
|   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 466, 
in get_distribution
| dist = get_provider(dist)
|   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 342, 
in get_provider
| return working_set.find(moduleOrReq) or require(str(moduleOrReq))[0]
|   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 886, 
in require
| needed = self.resolve(parse_requirements(requirements))
|   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 772, 
in resolve
| raise DistributionNotFound(req, requirers)
| pkg_resources.DistributionNotFound: The 'pip' distribution was not found and 
is required by the application
|
| During handling of the above exception, another exception occurred:
|
| Traceback (most recent call last):
|   File "/<>/setup.py", line 8, in 
| setup(name='screenkey', version='1.4',
|   File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 152, in 
setup
| _install_setup_requires(attrs)
|   File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 147, in 
_install_setup_requires
| dist.fetch_build_eggs(dist.setup_requires)
|   File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 686, in 
fetch_build_eggs
| resolved_dists = pkg_resources.working_set.resolve(
|   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 766, 
in resolve
| dist = best[req.key] = env.best_match(
|   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 1051, 
in best_match
| return self.obtain(req, installer)
|   File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 1063, 
in obtain
| return installer(requirement)
|   File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 745, in 
fetch_build_egg
| return fetch_build_egg(self, req)
|   File "/usr/lib/python3/dist-packages/setuptools/installer.py", line 68, in 
fetch_build_egg
| return _legacy_fetch_build_egg(dist, req)
|   File "/usr/lib/python3/dist-packages/setuptools/installer.py", line 51, in 
_legacy_fetch_build_egg
| return cmd.easy_install(req)
|   File "/usr/lib/python3/dist-packages/setuptools/command/easy_install.py", 
line 688, in easy_install
| raise DistutilsError(msg)
| distutils.errors.DistutilsError: Could not find suitable distribution for 
Requirement.parse('babel')
| E: pybuild pybuild:353: clean: plugin distutils failed with: exit code=1: 
python3.9 setup.py clean 
| dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit 
code 13
| make: *** [debian/rules:13: clean] Error 25
| dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned 
exit status 2

See
https://buildd.debian.org/status/fetch.php?pkg=screenkey&arch=all&ver=1%3A1.4-1&stamp=1611862712&raw=0

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: screenkey
Source-Version: 1:1.4-2
Done: Georges Khaznadar 

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

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

Processed: found 976860 in 20201007-1

[Debian Bug Tracking System]

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

> found 976860 20201007-1
Bug #976860 [python3-plaso] python3-plaso: log2timeline.py + image_export.py 
always bail out with "ERROR: Unable to determine location of data files."
Marked as found in versions plaso/20201007-1.
> thanks
Stopping processing here.

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

Processed: Re: Bug#981725: libdap-dev no longer provides dap-config

[Debian Bug Tracking System]

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

> reopen 981725
Bug #981725 {Done: Alastair McKinstry } [src:libdap] 
libdap-dev no longer provides dap-config
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions libdap/3.20.7-5.
> notfixed 981725 libdap/3.20.7-5
Bug #981725 [src:libdap] libdap-dev no longer provides dap-config
Ignoring request to alter fixed versions of bug #981725 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#981725: libdap-dev no longer provides dap-config

[Sebastiaan Couwenberg]

reopen 981725
notfixed 981725 libdap/3.20.7-5
thanks

On 2/4/21 5:39 AM, Sebastiaan Couwenberg wrote:
> On 2/3/21 12:37 PM, Sebastiaan Couwenberg wrote:
>> On 2/3/21 12:03 PM, Sebastiaan Couwenberg wrote:
>>> On 2/3/21 10:48 AM, Gianfranco Costamagna wrote:
 Hello, the new libdap broke in some way the gdal configure script, and now 
 the configure step fails with:

 checking for libqhull/libqhull.h... yes
 checking for qh_new_qhull in -lqhull... no
 configure: error: --with-qhull requested, but library not found!


 I don't really understand what is going on here, looks like qhull is not 
 found anymore.

 libdap might be the library to blame here, feel free to reassign if needed
>>>
>>> libdap-dev no longer provides /usr/bin/dap-config, gdal configure then
>>> adds dap++ to LIBS which breaks the compile test for qhull.
>>>
>>> dap-config should really be provided by libdap-dev instead of
>>> libdap-bin. Or libdap-bin needs to be a dependency of libdap-dev.
>>
>> This is also the cause of the autopkgtest failure which prevents testing
>> migration:
>>
>>  Test-Command: set -e
>>; dap-config --help 2> /dev/null
>>  Depends: libdap-dev
>>
>> The attached patch should fix the issue.
> 
> The patch has been updated with the changed from -4.
> 
> To clarify the issue:
> 
> Moving dap-config* from libdap-dev to libdap-bin is wrong,
> from the Debian Library Packaging guide:
> 
> "
> -DEV package (e.g. libfooX-dev) should contain the development symlink
> used when linking, static libraries, and header files, and if they
> exist, package configuration scripts.
> 
> Table 4.1. Annotated list of files that usually reside in -DEV package
> 
> +--+
> |files |meaning|
> |--+---|
> |usr/lib/*.so  |development linkage file, used when other  |
> |  |programs are linked with -lxxx |
> |--+---|
> |usr/lib/*.a   |static link files  |
> |--+---|
> |usr/lib/*.la  |libtool linkage information file   |
> |--+---|
> |usr/include/* |Development include files  |
> |--+---|
> |usr/bin/*-config  |Some configuration script used in obtaining|
> |  |the library paths, like gtk-config |
> |--+-- |
> |usr/lib/pkgconfig/*.pc|Some information required for pkgconfig|
> +--+
> "
> 
> https://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.html#id249952
> 
> Alastair, if you won't move dap-config* back to the -dev package (e.g.
> by applying the attached patch), you must add Depends: libdap-bin to
> libdap-dev to have dap-config available when installing libdap-dev.

Alastair, you should have applied the patch, the changes in -5 are not
sufficient:

 * debian/control

 ** libdap-dev lacks:

Breaks: libdap-bin (<< 3.20.7-5~)
Replaces: libdap-bin (<< 3.20.7-5~)

These need to be added.

 ** libdap-doc still has erroneous Breaks/Replaces:

Breaks: libdap-dev (<< 3.20.7)
Replaces: libdap-dev (<< 3.20.7)

These need to be removed.

 * debian/libdap-bin.install

   Still includes:

   usr/bin/dap-config-pkgconfig
   usr/share/man/man1/dap-config.1

   These should move to libdap-dev.install too.

 * debian/rules

   Installs debian/dap-config.pkg in libdap-bin via
   override_dh_installdocs.

   It should be installed in override_dh_auto_install.

   Now the upstream dap-config is included in libdap-dev and the debian
   one in libdap-bin creating a conflict.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Processed: closing 950065

[Debian Bug Tracking System]

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

> close 950065
Bug #950065 [src:python-static3] python-static3 FTBFS with Python 3.8 as 
supported version
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#919348: many new releases since -- still "too buggy"?

[Yves-Alexis Perez]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Thu, 2021-02-04 at 14:43 +0200, Adrian Bunk wrote:
> Yves-Alexis, do you have any objections to closing this bug now?

Yes. I have xfce4-screensaver (4.16) running on a Debian sid install and it
still happens every once in a while that the desktop of the locked box appears
(for example at resume). I'm still not confident it should actually be used on
a production install it's just not robust enough, but I don't have the time or
motivation to investigate and fix it myself.

Regards,
- -- 
Yves-Alexis
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAmAcRBUACgkQ3rYcyPpX
RFugAAgA3B0u6cT682/Ks+TPVPy4eW7z9YsrtNz0MS2aMhxsDNbgu4iI2IKviGd2
4z4Pai+0MxlwDA0r5/jFAmyqrsqJ/ze7B0SdoizaDG976/62qQ1+KH8pPeP/h+zJ
1qYxr/8tRubTOaUBEdPoTkPNuzWWpQzKtggsV/J/HpRa7Lr94rsiie+Buig474hS
Wl7oqw1CkCHnBFf8n+ZA9Y9DByqdXS0tNHu3fMeDWDdzl7/pL5J6amJY+sXkYuVo
f0FoFth7GmbKKZKBNhPhjtgyo8Q8kG6A3kSlq8WDqlUeIFbYP/ScmfsjiLhCw4fb
8TjW7HaWaprxaJlAJlrSEmwQHpEqKA==
=JzSz
-END PGP SIGNATURE-

Processed: affects 980801

[Debian Bug Tracking System]

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

> affects 980801 + pgcharts
Bug #980801 [cl-postgres] pgcharts: FTBFS with sbcl 2.1
Bug #980689 [cl-postgres] cl-postgres: fails to load with SBCL 2.1.0
Added indication that 980801 affects pgcharts
Added indication that 980689 affects pgcharts
> thanks
Stopping processing here.

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

Processed: forcibly merging 980689 980801

[Debian Bug Tracking System]

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

> forcemerge 980689 980801
Bug #980689 [cl-postgres] cl-postgres: fails to load with SBCL 2.1.0
Bug #980801 [cl-postgres] pgcharts: FTBFS with sbcl 2.1
Added indication that 980801 affects pgloader
Marked as found in versions cl-postmodern/20180430-1 and 
cl-postmodern/20180430-1.1.
Added tag(s) patch and upstream.
Merged 980689 980801
> thanks
Stopping processing here.

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

Bug#981878: ruby-gitlab-pg-query downloads from the internet during the build

[Adrian Bunk]

Source: ruby-gitlab-pg-query
Version: 1.3.1-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=ruby-gitlab-pg-query&arch=amd64&ver=1.3.1-2&stamp=1612462914&raw=0

...
Building native extensions. This could take a while...
current directory: 
/<>/debian/ruby-gitlab-pg-query/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0/gems/gitlab-pg_query-1.3.1/ext/pg_query
["/usr/bin/ruby2.7", "-I", "/usr/lib/ruby/vendor_ruby", "-r", 
"./siteconf20210204-26550-1qve3p5.rb", "extconf.rb"]
ERROR:  Error installing /tmp/d20210204-26547-bcny2z/gitlab-pg_query-1.3.1.gem:
ERROR: Failed to build gem native extension.

current directory: 
/<>/debian/ruby-gitlab-pg-query/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0/gems/gitlab-pg_query-1.3.1/ext/pg_query
/usr/bin/ruby2.7 -I /usr/lib/ruby/vendor_ruby -r 
./siteconf20210204-26550-1qve3p5.rb extconf.rb
Building has failed. See above output for more information on the failure.
extconf failed, exit code 1

Gem files will remain installed in 
/<>/debian/ruby-gitlab-pg-query/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0/gems/gitlab-pg_query-1.3.1
 for inspection.
Results logged to 
/<>/debian/ruby-gitlab-pg-query/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0/extensions/x86_64-linux/2.7.0/gitlab-pg_query-1.3.1/gem_make.out
*** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of necessary
libraries and/or headers.  Check the mkmf.log file for more details.  You may
need configuration options.

Provided configuration options:
--with-opt-dir
--without-opt-dir
--with-opt-include
--without-opt-include=${opt-dir}/include
--with-opt-lib
--without-opt-lib=${opt-dir}/lib
--with-make-prog
--without-make-prog
--srcdir=.
--curdir
--ruby=/usr/bin/$(RUBY_BASE_NAME)2.7
/usr/lib/ruby/2.7.0/net/http.rb:960:in `initialize': Failed to open TCP 
connection to codeload.github.com:443 (Network is unreachable - connect(2) for 
"codeload.github.com" port 443) (Errno::ENETUNREACH)
from /usr/lib/ruby/2.7.0/net/http.rb:960:in `open'
from /usr/lib/ruby/2.7.0/net/http.rb:960:in `block in connect'
from /usr/lib/ruby/2.7.0/timeout.rb:95:in `block in timeout'
from /usr/lib/ruby/2.7.0/timeout.rb:105:in `timeout'
from /usr/lib/ruby/2.7.0/net/http.rb:958:in `connect'
from /usr/lib/ruby/2.7.0/net/http.rb:943:in `do_start'
from /usr/lib/ruby/2.7.0/net/http.rb:932:in `start'
from /usr/lib/ruby/2.7.0/open-uri.rb:346:in `open_http'
from /usr/lib/ruby/2.7.0/open-uri.rb:764:in `buffer_open'
from /usr/lib/ruby/2.7.0/open-uri.rb:235:in `block in open_loop'
from /usr/lib/ruby/2.7.0/open-uri.rb:233:in `catch'
from /usr/lib/ruby/2.7.0/open-uri.rb:233:in `open_loop'
from /usr/lib/ruby/2.7.0/open-uri.rb:174:in `open_uri'
from /usr/lib/ruby/2.7.0/open-uri.rb:744:in `open'
from /usr/lib/ruby/2.7.0/open-uri.rb:50:in `open'
from extconf.rb:19:in `block in '
from extconf.rb:18:in `open'
from extconf.rb:18:in `'
/usr/lib/ruby/2.7.0/net/http.rb:960:in `initialize': Network is unreachable - 
connect(2) for "codeload.github.com" port 443 (Errno::ENETUNREACH)
from /usr/lib/ruby/2.7.0/net/http.rb:960:in `open'
from /usr/lib/ruby/2.7.0/net/http.rb:960:in `block in connect'
from /usr/lib/ruby/2.7.0/timeout.rb:95:in `block in timeout'
from /usr/lib/ruby/2.7.0/timeout.rb:105:in `timeout'
from /usr/lib/ruby/2.7.0/net/http.rb:958:in `connect'
from /usr/lib/ruby/2.7.0/net/http.rb:943:in `do_start'
from /usr/lib/ruby/2.7.0/net/http.rb:932:in `start'
from /usr/lib/ruby/2.7.0/open-uri.rb:346:in `open_http'
from /usr/lib/ruby/2.7.0/open-uri.rb:764:in `buffer_open'
from /usr/lib/ruby/2.7.0/open-uri.rb:235:in `block in open_loop'
from /usr/lib/ruby/2.7.0/open-uri.rb:233:in `catch'
from /usr/lib/ruby/2.7.0/open-uri.rb:233:in `open_loop'
from /usr/lib/ruby/2.7.0/open-uri.rb:174:in `open_uri'
from /usr/lib/ruby/2.7.0/open-uri.rb:744:in `open'
from /usr/lib/ruby/2.7.0/open-uri.rb:50:in `open'
from extconf.rb:19:in `block in '
from extconf.rb:18:in `open'
from extconf.rb:18:in `'
/usr/lib/ruby/vendor_ruby/gem2deb.rb:54:in `run': /usr/bin/ruby2.7 -S gem 
install --config-file /dev/null --verbose --local --verbose --no-document 
--ignore-dependencies --install-dir 
debian/ruby-gitlab-pg-query/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0 
/tmp/d20210204-26547-bcny2z/gitlab-pg_query-1.3.1.gem (Gem2Deb::CommandFailed)
from /usr/lib/ruby/vendor_ruby/gem2deb/gem_installer.rb:195:in `run_gem'
from /usr/lib/ruby/vendor_ruby/gem2deb/gem_installer.rb:113:in `block 
in install_files_and_build_extensions'
from /usr/lib/ruby/vendor_ruby/gem2deb/gem_installer.rb:61:in `each'
f

Bug#972425: marked as done (mlpack: FTBFS: warning: the dot tool could not be found at dot-Gbgcolor=black)

[Debian Bug Tracking System]

Your message dated Thu, 4 Feb 2021 20:44:43 +0200
with message-id <20210204184443.GA29703@localhost>
and subject line Re: Bug#972425: mlpack FTBFS fixed in version 3.4.2-1 ?
has caused the Debian Bug report #972425,
regarding mlpack: FTBFS: warning: the dot tool could not be found at 
dot-Gbgcolor=black
to be marked as done.

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

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


-- 
972425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972425
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mlpack
Version: 3.4.1-2
Severity: serious
Tags: ftbfs sid bullseye
Justification: fails to build from source (but built successfully in the past)

mlpack fails to build on all architectures:
| cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends 
"Unix Makefiles" /<> /<>/src/mlpack 
/<>/obj-x86_64-linux-gnu 
/<>/obj-x86_64-linux-gnu/src/mlpack 
/<>/obj-x86_64-linux-gnu/src/mlpack/CMakeFiles/mlpack_headers.dir/DependInfo.cmake
 --color=
| warning: Tag 'USE_WINDOWS_ENCODING' at line 11 of file 
'/<>/obj-x86_64-linux-gnu/Doxyfile' has become obsolete.
|  To avoid this warning please remove this line from your 
configuration file or upgrade it using "doxygen -u"
| warning: Tag 'DETAILS_AT_TOP' at line 33 of file 
'/<>/obj-x86_64-linux-gnu/Doxyfile' has become obsolete.
|  To avoid this warning please remove this line from your 
configuration file or upgrade it using "doxygen -u"
| warning: Tag 'SHOW_DIRECTORIES' at line 71 of file 
'/<>/obj-x86_64-linux-gnu/Doxyfile' has become obsolete.
|  To avoid this warning please remove this line from your 
configuration file or upgrade it using "doxygen -u"
| warning: Tag 'HTML_ALIGN_MEMBERS' at line 150 of file 
'/<>/obj-x86_64-linux-gnu/Doxyfile' has become obsolete.
|  To avoid this warning please remove this line from your 
configuration file or upgrade it using "doxygen -u"
| warning: Tag 'XML_SCHEMA' at line 201 of file 
'/<>/obj-x86_64-linux-gnu/Doxyfile' has become obsolete.
|  To avoid this warning please remove this line from your 
configuration file or upgrade it using "doxygen -u"
| warning: Tag 'XML_DTD' at line 202 of file 
'/<>/obj-x86_64-linux-gnu/Doxyfile' has become obsolete.
|  To avoid this warning please remove this line from your 
configuration file or upgrade it using "doxygen -u"
| warning: Tag 'PERL_PATH' at line 234 of file 
'/<>/obj-x86_64-linux-gnu/Doxyfile' has become obsolete.
|  To avoid this warning please remove this line from your 
configuration file or upgrade it using "doxygen -u"
| warning: Tag 'MAX_DOT_GRAPH_WIDTH' at line 256 of file 
'/<>/obj-x86_64-linux-gnu/Doxyfile' has become obsolete.
|  To avoid this warning please remove this line from your 
configuration file or upgrade it using "doxygen -u"
| warning: Tag 'MAX_DOT_GRAPH_HEIGHT' at line 257 of file 
'/<>/obj-x86_64-linux-gnu/Doxyfile' has become obsolete.
|  To avoid this warning please remove this line from your 
configuration file or upgrade it using "doxygen -u"
| warning: the dot tool could not be found at dot-Gbgcolor=black
|  (warning treated as error, aborting now)
| make[3]: *** [CMakeFiles/doc.dir/build.make:80: CMakeFiles/doc] Error 1
| make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
| make[2]: *** [CMakeFiles/Makefile2:2504: CMakeFiles/doc.dir/all] Error 2

See
https://buildd.debian.org/status/fetch.php?pkg=mlpack&arch=amd64&ver=3.4.1-2&stamp=1602517529&raw=0
for example

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 3.4.2-1

On Wed, Jan 06, 2021 at 02:54:38PM +0100, Étienne Mollier wrote:
> Good day,
> 
> I tried to reproduce the FTBFS of mlpack on my end, and the
> build went through.  Then, I spotted the following entry in the
> mlpack changelog:
> 
>   * Do not allow doxygen warnings to break the build
> 
> By chance, isn't it time to close #972425, as fixed in version
> 3.4.2-1 ?

Looks correct to me.

> Best wishes,

cu
Adrian--- End Message ---

Processed: Alter tags for #980689 (cl-postgres)

[Debian Bug Tracking System]

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

> tag 980689 + patch upstream
Bug #980689 [cl-postgres] cl-postgres: fails to load with SBCL 2.1.0
Added tag(s) patch and upstream.
> thanks
Stopping processing here.

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

Bug#951806: marked as done (ruby-serverengine: FTBFS with ruby-rspec 3.9.0c1e0m1s2-1, not 3.8.0c0e1m0s0-1)

[Debian Bug Tracking System]

Your message dated Thu, 4 Feb 2021 20:30:41 +0200
with message-id <20210204183041.GA29102@localhost>
and subject line Re: Bug#951806: ruby-serverengine: FTBFS aginst Ruby2.5 and 
Ruby2.7
has caused the Debian Bug report #951806,
regarding ruby-serverengine: FTBFS with ruby-rspec 3.9.0c1e0m1s2-1, not 
3.8.0c0e1m0s0-1
to be marked as done.

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

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


-- 
951806: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951806
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-serverengine
Version: 2.2.0-1
Severity: critical
User pkg-ruby-extras-maintain...@lists.alioth.debian.org
Usertags: ruby2.7-transition

Dear Maintainer,

Whilst building ruby-serverengine against Ruby2.5 and Ruby2.7, I
noticed that all the tests are failing and at one point, the tests
freeze.

I've forwarded this upstream:
https://github.com/treasure-data/serverengine/issues/104

Just FTR, this package has no reverse-dependencies or
reverse-build-dependencies. Is it a good sign for it to be filed for
removal?


Best,
Utkarsh

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

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

Versions of packages ruby-serverengine depends on:
ii  ruby  1:2.5.2
ii  ruby-sigdump  0.2.4-4

ruby-serverengine recommends no packages.

ruby-serverengine suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 2.2.1-1

On Sat, Feb 22, 2020 at 03:47:01AM +0530, Utkarsh Gupta wrote:
> Package: ruby-serverengine
> Version: 2.2.0-1
> Severity: critical
> User pkg-ruby-extras-maintain...@lists.alioth.debian.org
> Usertags: ruby2.7-transition
> 
> Dear Maintainer,
> 
> Whilst building ruby-serverengine against Ruby2.5 and Ruby2.7, I
> noticed that all the tests are failing and at one point, the tests
> freeze.

Seems this was fixed in 2.2.1:
https://tests.reproducible-builds.org/debian/history/ruby-serverengine.html

> I've forwarded this upstream:
> https://github.com/treasure-data/serverengine/issues/104
>...
> Best,
> Utkarsh

cu
Adrian--- End Message ---

Bug#981876: gdpc: flaky autopkgtest on i386

[Paul Gevers]

Source: gdpc
Version: 2.2.5-10
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

Your package has an autopkgtest, great. However, I looked into
the history of your autopkgtest [1] on i386 (because it is blocking
glib2.0) and I noticed it fails regularly, while a rerun passes. I
copied some of the output at the bottom of this report.

Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.

Please do get in touch if we need to dive into this together. Or if you
want to discuss this issue. I noticed that all the failed runs I checked
were done on the same worker. Could the problem be a timing issue? (The
worker has a spinning disk and is slower than our other workers).

Paul

https://ci.debian.net/data/autopkgtest/testing/i386/g/gdpc/10255341/log.gz

autopkgtest [04:19:42]: test run-unit-test: [---
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ...
or kill -l [sigspec]
autopkgtest [04:19:52]: test run-unit-test: ---]



OpenPGP_signature
Description: OpenPGP digital signature

Bug#976354: git - tests fail with dash

[Nicolas Boulenguez]

Package: git
Followup-For: Bug #976354

The test scripts include test-lib.sh, which deliberately assumes bash.
# checkbashisms test-lib.sh

possible bashism in test-lib.sh line 381 ($BASH_SOMETHING):
 if test -n "$BASH_VERSION" && eval '
This part happens to work for other shells, but the comments around it
suggest that the intent is only to check the bash version.

possible bashism in test-lib.sh line 1491 (builtin):
 builtin pwd -W
The 'builtin' builtin only exists in bash.

So I suggest to apply Bastian’s suggestion:
# sed -i '1 s_^#!/bin/sh$_#!/bin/bash_' t/t*.sh

Bug#981725: marked as done (libdap-dev no longer provides dap-config)

[Debian Bug Tracking System]

Your message dated Thu, 04 Feb 2021 18:04:52 +
with message-id 
and subject line Bug#981725: fixed in libdap 3.20.7-5
has caused the Debian Bug report #981725,
regarding libdap-dev no longer provides dap-config
to be marked as done.

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

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


-- 
981725: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981725
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gdal
Version: 3.2.1+dfsg-1
Severity: serious

Hello, the new libdap broke in some way the gdal configure script, and now the 
configure step fails with:

checking for libqhull/libqhull.h... yes
checking for qh_new_qhull in -lqhull... no
configure: error: --with-qhull requested, but library not found!


I don't really understand what is going on here, looks like qhull is not found 
anymore.

libdap might be the library to blame here, feel free to reassign if needed

Gianfranco
--- End Message ---
--- Begin Message ---
Source: libdap
Source-Version: 3.20.7-5
Done: Alastair McKinstry 

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated libdap 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, 04 Feb 2021 13:13:25 +
Source: libdap
Architecture: source
Version: 3.20.7-5
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Closes: 981725
Changes:
 libdap (3.20.7-5) unstable; urgency=medium
 .
   * Revert dap-config to libdap-dev. Closes: #981725
Checksums-Sha1:
 0816c6308363d91c5b3256b0d42f2722be64a54b 2405 libdap_3.20.7-5.dsc
 3872bc8940a70a30739d5479d85a3d2ccc0fc902 13880 libdap_3.20.7-5.debian.tar.xz
Checksums-Sha256:
 e8443aef6d9943696cae3fae0d1d6631ed5a5144596f70f8326327e1fa62e617 2405 
libdap_3.20.7-5.dsc
 9ca942e144ee1be458eec57f4bc3d1cacd23b7bc25043ea78e3c52bbbddd1534 13880 
libdap_3.20.7-5.debian.tar.xz
Files:
 749f8aaffb33e9de78ef5710913642ac 2405 utils optional libdap_3.20.7-5.dsc
 dd939b16f81db9432f60e39c4781469e 13880 utils optional 
libdap_3.20.7-5.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAmAcM8QACgkQy+a7Tl2a
06Wt4BAAoge6NTKUB9UNTcuaYRJx+0551/yfPFQ36uYPg7YULPo1KCO6YBJOcuDI
7nYQr3M3okn5i0vslnWga6CGzbdarF8xMsZT4UxvI+/ZgSLYaKDxzfPe5eLXgol8
0BYDtjAcE1SgHZ+/rQAeoUP4RPkoArPYJ3m26QuVEudR7ScysER3/EUcH/V2HMvr
URT8aK8aInGeRy2UP1ipKTVIMdZ7etzb6WEv/lVCT7wJcC6VjRPqFJBTMV0lJ0nb
K72LlelwQ+FBq1uMU2sM2g2yy3kuAbWPHiwxnx6xiCWVoI7PjQ4AWtA6mQuQX8DL
kqDQTZWoZaMJ86WvntawBtC6ZcFL+bn5rBA8j0BwFy0+E2wFIvpAMg8JcrBQPbU1
P7S3nVJ251eTrdEavQSzRpcPJUVGM9eY+lwG5LykBg8xJXqU1jQYIoEGYXq+Iosv
V6XjhhYJvwuJ1qpQXqJQoQF5PI6nUmAHAjMm95O33Z4c22nG+p3BNeA5iqnjDJ0z
18iw56FOISf1Sce/kBOnU3qdwOZuLRT3uYa+7QW7f0LtQ99A8+uOFOtkSqFsqvJV
P4eQX4vNFLefjcFLzl9uMihrCl8HDiP9ehcFg2as8ZswgTFvfPmqQ3Xm86Mo6PpK
X+mdK0+prSvfttNmxQENMT3CsTsy+RTj2WxOE7MsrtCkfhVoWQM=
=2i/i
-END PGP SIGNATURE End Message ---

Bug#981874: trinityrnaseq: flaky autopkgtest

[Paul Gevers]

Source: trinityrnaseq
Version: 2.11.0+dfsg-6
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

Your package has an autopkgtest, great. However, I looked into
the history of your autopkgtest [1] on amd64 and arm64 (because it is
blocking perl) and I noticed it fails regularly, while a rerun passes. I
copied some of the output at the bottom of this report. The last warning
has a different number every time.

Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.

Please do get in touch if we need to dive into this together. Or if you
want to discuss this issue. I noticed that all the failed runs I checked
were done on the same worker. Could the problem be a timing issue? (The
worker has a spinning disk and is slower than our other workers).

Paul

https://ci.debian.net/data/autopkgtest/testing/arm64/t/trinityrnaseq/10170685/log.gz
https://ci.debian.net/data/autopkgtest/testing/amd64/t/trinityrnaseq/10058739/log.gz
https://ci.debian.net/data/autopkgtest/testing/amd64/t/trinityrnaseq/10172707/log.gz
https://ci.debian.net/data/autopkgtest/testing/amd64/t/trinityrnaseq/10194744/log.gz
https://ci.debian.net/data/autopkgtest/testing/amd64/t/trinityrnaseq/10216335/log.gz

Warning messages:
1: Removed 55 rows containing missing values (geom_point).
2: Removed 1 rows containing missing values (geom_text).
GOBubble, bckgrd color
Warning messages:
1: Removed 55 rows containing missing values (geom_point).
2: Removed 1 rows containing missing values (geom_text).
GOCircle
Error: Breaks and labels are different lengths
Backtrace:
 █
  1. └─GOplot::GOCircle(circ)
  2.   └─gridExtra::grid.arrange(c, table, ncol = 2)
  3. └─gridExtra::arrangeGrob(...)
  4.   └─base::lapply(grobs[toconv], ggplot2::ggplotGrob)
  5. └─ggplot2:::FUN(X[[i]], ...)
  6.   ├─ggplot2::ggplot_gtable(ggplot_build(x))
  7.   └─ggplot2:::ggplot_gtable.ggplot_built(ggplot_build(x))
  8. └─ggplot2:::build_guides(...)
  9.   └─ggplot2:::guides_train(...)
 10. ├─ggplot2::guide_train(guide, scale, output)
 11. └─ggplot2:::guide_train.colorbar(guide, scale, output)
 12.   └─scale$get_labels(breaks)
 13. └─ggplot2:::f(..., self = self)
Warning messages:
1: Removed 6 rows containing missing values (geom_point).
2: Removed 6 rows containing missing values (geom_point).
Execution halted
Error, CMD:
/usr/lib/trinityrnaseq/Analysis/DifferentialExpression/GOplot.Rscript
--EC_david ./EC.david --EC_genelist ./EC.genelist --pdf_outfile
goplot.pdf died with ret 256 at
/usr/lib/trinityrnaseq/Analysis/DifferentialExpression/prep_n_run_GOplot.pl
line 246.
make[1]: *** [Makefile:4: test] Error 25
make[1]: Leaving directory
'/tmp/autopkgtest-lxc.9tclu2at/downtmp/autopkgtest_tmp/trinityrnaseq/trinity_ext_sample_data/test_GOplot'
make: *** [Makefile:18: test] Error 2
autopkgtest [00:08:05]: test run-tests: ---]



OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:bambootracker: fails to migrate to testing for too long: FTBFS on 32 bit

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.4.5+git20121209-1
Bug #981871 [src:bambootracker] src:bambootracker: fails to migrate to testing 
for too long: FTBFS on 32 bit
Marked as fixed in versions bambootracker/0.4.5+git20121209-1.
Bug #981871 [src:bambootracker] src:bambootracker: fails to migrate to testing 
for too long: FTBFS on 32 bit
Marked Bug as done
> block -1 by 974580
Bug #981871 {Done: Paul Gevers } [src:bambootracker] 
src:bambootracker: fails to migrate to testing for too long: FTBFS on 32 bit
981871 was not blocked by any bugs.
981871 was not blocking any bugs.
Added blocking bug(s) of 981871: 974580

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

Bug#981871: src:bambootracker: fails to migrate to testing for too long: FTBFS on 32 bit

[Paul Gevers]

Source: bambootracker
Version: 0.4.2-1
Severity: serious
Control: close -1 0.4.5+git20121209-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 974580

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:bambootracker
has been trying to migrate for 84 days [2]. Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have immediately closed this bug with the version in unstable, so if
that version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bullseye, so
it doesn't affect (old-)stable.

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=bambootracker




OpenPGP_signature
Description: OpenPGP digital signature

Bug#971308: marked as done (plaso: Switch to python3-pycryptodome)

[Debian Bug Tracking System]

Your message dated Thu, 04 Feb 2021 17:49:17 +
with message-id 
and subject line Bug#971308: fixed in plaso 20201007-1
has caused the Debian Bug report #971308,
regarding plaso: Switch to python3-pycryptodome
to be marked as done.

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

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


-- 
971308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971308
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: plaso
Version: 20190131-3
Severity: important
Tags: sid bullseye
Usertags: pycrypto

Dear maintainer,

plaso currently Build-Depends or Depends on python3-crypto from
PyCrypto. This project is no longer maintained and PyCryptodome
(https://www.pycryptodome.org/en/latest/) provides a drop in
replacement. Please switch to python3-pycryptodome. I'd like to
remove python-crypto before the release of bullseye.

Cheers 
--- End Message ---
--- Begin Message ---
Source: plaso
Source-Version: 20201007-1
Done: Raphaël Hertzog 

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

Debian distribution maintenance software
pp.
Raphaël Hertzog  (supplier of updated plaso 
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, 04 Feb 2021 17:59:51 +0100
Source: plaso
Architecture: source
Version: 20201007-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Raphaël Hertzog 
Closes: 971308
Changes:
 plaso (20201007-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Samuel Henrique ]
   * Configure git-buildpackage
 .
   [ Debian Janitor ]
   * Set debhelper-compat version in Build-Depends.
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
 Repository-Browse.
   * Update standards version to 4.4.1, no changes needed.
 .
   [ Raphaël Hertzog ]
   * New upstream version 20201007
   * Update Homepage
 .
   [ Axel Beckert ]
   * Bump (build-)dependency on python3-dfvfs to a version no more using
 python3-crypto. Replace (indirect) (build-)dependency on
 python3-crypto with python3-cryptography. (Closes: #971308)
   * Bump versioned (build-)dependencies on libsigscan-python3,
 python3-libscca, -libregf, -libfsntfs, -libevt, -future,
 -elasticsearch, -dtfabric, -dfwinreg, -dfdatetime, and -artifacts
 according to upstream dependency declarations.
   * Follow upstream dependency declarations and
 + drop python3-efilter and -biplist from, and
 + add python3-cffi-backend, -dateutil, -defusedxml, -libcreg,
   -libfsext, -libluksde, and -redis to
 (build-)dependencies.
Checksums-Sha1:
 0b2a30d64b9e9d721ac197dd8e429aa4c59d6bd3 3316 plaso_20201007-1.dsc
 3fd164319df19b1c135a75dfdde837f1b547c63c 141390757 plaso_20201007.orig.tar.gz
 d403d6d70bb7b860cb195f4bd312fc9208f39b10 15544 plaso_20201007-1.debian.tar.xz
 27ec7785dcfd71cb1cfce99e77daa75160c371fc 7146 plaso_20201007-1_source.buildinfo
Checksums-Sha256:
 7610dfb0e33ed6d61349d2fae7fdb723884c01ea2669bf30195ec53214615f4e 3316 
plaso_20201007-1.dsc
 2d15a71ec6cbd9a8ff81d310340ec8c099a69924bd8a0a7d95b05685709b769f 141390757 
plaso_20201007.orig.tar.gz
 07fd5c08b8feca825c851494218de5b2b8885b49ed7b9db11eab8de8c75c0b7b 15544 
plaso_20201007-1.debian.tar.xz
 997060e38ba5ed562badd43c2c60a220be603ccf9d02ff16066e68dfe39f2b44 7146 
plaso_20201007-1_source.buildinfo
Files:
 4e64a42a895a85a467727fa8fe317585 3316 admin optional plaso_20201007-1.dsc
 3f42f51ea22067c9d8dd5ff74ebc7163 141390757 admin optional 
plaso_20201007.orig.tar.gz
 309ecae0f6988bd77af91d7a8d9579e1 15544 admin optional 
plaso_20201007-1.debian.tar.xz
 4dc404c52051b07bd3c9b22dbe9d830b 7146 admin optional 
plaso_20201007-1_source.buildinfo

-BEGIN PGP SIGNATURE-
Comment: Signed by Raphael Hertzog

iQEzBAEBCgAdFiEE1823g1EQnhJ1LsbSA4gdq+vCmrkFAmAcKyYACgkQA4gdq+vC
mrmbggf/S6XKRwghyrjXPLZO1nze+XVqri/cE+sMcPZEwSdaNjiHVPSLwLjrwUwe
CtbIdRwGdni5QYnWKasNlFlOnvKMMhsUJIUbPGX0b3jzFzW/Fb7Y6VO4JPnLqmG1
mvgzPrPPzsyxqmYDWZ46iYXLfVTvz3/dzxh59b0V/OqlKFp8yjx0j8Gmx+yI6Sog
Q27mfPVPQRXbDjmUiHbD8UowrXEJSE1kRQfs2QL2tYRHSkznRKEmIS7CgPQetc42
4n/lmCNwD4Rby4NhjLUjAlBOJNWpIJr9sfqOL3

Processed: severity of 970880 is serious

[Debian Bug Tracking System]

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

> severity 970880 serious
Bug #970880 [freeipa-server] freeipa-server: FreeIPA server installation fails 
with Certificate issuance failed (CA_REJECTED)
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: closing 970230

[Debian Bug Tracking System]

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

> close 970230 4.8.10-2
Bug #970230 [src:freeipa] freeipa FTBFS on non-nodejs architectures
Marked as fixed in versions freeipa/4.8.10-2.
Bug #970230 [src:freeipa] freeipa FTBFS on non-nodejs architectures
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#981870: FTBFS: Doesn't build against ruby-nokogiri 1.11.1

[Sven Mueller]

Package: ruby-azure-storage-common
Version: 2.0.1-4
Severity: Serious

This makes the package unbuildable in both unstable and testing (bullseye).
Error message during build:

/usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:309
:in
`to_specs': Could not find 'nokogiri' (~> 1.10.4) - did find:
[nokogiri-1.11.1] (Gem::MissingSpecVersionError)
Checked in
'GEM_PATH=/<>/debian/ruby-azure-storage-common/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/2.7.0:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0'
, execute `gem env` for more information

Bug#980629: nheko: FTBFS: internal compiler error

[Hubert Chathi]

Will a fixed version be uploaded to unstable soon?  I'd like to upload a
newer version of nheko, but it won't build until a fixed gcc is
available.

Thanks

-- 
Hubert Chathi  -- https://www.uhoreg.ca/
Jabber: hub...@uhoreg.ca -- Matrix: @uhoreg:matrix.org
PGP/GnuPG key: 4096R/F24C F749 6C73 DDB8 DCB8  72DE B2DE 88D3 113A 1368

Bug#981869: librust-tcmalloc-dev: Depends: librust-tcmalloc-sys-0.3+default-dev but it is not installable

[Adrian Bunk]

Package: librust-tcmalloc-dev
Version: 0.3.0-2
Severity: serious

The following packages have unmet dependencies:
 librust-tcmalloc-dev : Depends: librust-tcmalloc-sys-0.3+default-dev but it is 
not installable

Bug#981868: src:python-sqlalchemy-utils: fails to migrate to testing for too long: autopkgtest failure

[Paul Gevers]

Source: python-sqlalchemy-utils
Version: 0.36.3-2
Severity: serious
Control: close -1 0.36.8-3
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package
src:python-sqlalchemy-utils has been trying to migrate for 74 days [2].
Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have immediately closed this bug with the version in unstable, so if
that version or a later version migrates, this bug will no longer affect
testing. I have also tagged this bug to only affect sid and bullseye, so
it doesn't affect (old-)stable.

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=python-sqlalchemy-utils




OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:python-sqlalchemy-utils: fails to migrate to testing for too long: autopkgtest failure

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.36.8-3
Bug #981868 [src:python-sqlalchemy-utils] src:python-sqlalchemy-utils: fails to 
migrate to testing for too long: autopkgtest failure
Marked as fixed in versions python-sqlalchemy-utils/0.36.8-3.
Bug #981868 [src:python-sqlalchemy-utils] src:python-sqlalchemy-utils: fails to 
migrate to testing for too long: autopkgtest failure
Marked Bug as done

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

Processed: [PATCH] cl-postgres: fails to load with SBCL 2.1.0

[Debian Bug Tracking System]

Processing control commands:

> reassign 980801 cl-postgres
Bug #980801 [src:pgcharts] pgcharts: FTBFS with sbcl 2.1
Bug reassigned from package 'src:pgcharts' to 'cl-postgres'.
No longer marked as found in versions pgcharts/1.0+2017-09-16-1.
Ignoring request to alter fixed versions of bug #980801 to the same values 
previously set

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

Bug#980689: [PATCH] cl-postgres: fails to load with SBCL 2.1.0

[Dennis Filder]

Control: reassign 980801 cl-postgres
tags: patch,upstream

The bug is in due to a bogus type declamation which sbcl 2:2.1.0-1
apparently no longer accepts when inlining.  I successfully rebuilt
both pgloader and pgcharts to confirm that it works.

Bug #980801 (pgcharts) is a duplicate of this.
Description: The type declamation for BYTE-LENGTH contradicts its
 default value which trips sbcl 2:2.1.0-1 when inlining.  This patch
 corrects the declamation.
Author: Dennis Filder 
Bug-Debian: https://bugs.debian.org/980689
Last-Update: 2021-02-03
--- postmodern-20180430-git/cl-postgres/strings-utf-8.lisp
+++ postmodern-20180430-git/cl-postgres/strings-utf-8.lisp
@@ -13,7 +13,7 @@

 (declaim (inline enc-read-string))
 (declaim (ftype (function (t &key (:null-terminated t)
-  (:byte-length unsigned-byte))
+  (:byte-length fixnum))
   string)
 enc-read-string))
 (defun enc-read-string (input &key null-terminated (byte-length -1))

Processed: severity of 971255 is serious

[Debian Bug Tracking System]

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

> severity 971255 serious
Bug #971255 [kopanocore] kopanocore: autopkgtest fails on assuming 
/etc/init.d/mysql exists
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:libsrtp2

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:libsrtp2
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #963363 (http://bugs.debian.org/963363)
> # Bug title: libsrtp2: FTBFS: running cipher self-test for AES-128 GCM using 
> NSS...failed with error code 8
> #  * https://github.com/cisco/libsrtp/issues/523
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 963363 + fixed-upstream
Bug #963363 [src:libsrtp2] libsrtp2: FTBFS: running cipher self-test for 
AES-128 GCM using NSS...failed with error code 8
Added tag(s) fixed-upstream.
> usertags 963363 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: libinih: Please provide libinih1-udeb

[Debian Bug Tracking System]

Processing control commands:

> block 981662 by -1
Bug #981662 [src:xfsprogs] xfsprogs-udeb depends on libinih1, not libinih1-udeb
981662 was not blocked by any bugs.
981662 was not blocking any bugs.
Added blocking bug(s) of 981662: 981864

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

Processed: tagging 947051

[Debian Bug Tracking System]

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

> tags 947051 - pending
Bug #947051 [src:latencytop] latencytop: Non-sensical source format and version
Removed tag(s) pending.
> thanks
Stopping processing here.

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

Bug#978225: marked as done (librarian-puppet: FTBFS: ruby-faraday : Breaks: ruby-puppet-forge (<= 2.3.2-1) but 2.3.2-1 is to be installed)

[Debian Bug Tracking System]

Your message dated Thu, 04 Feb 2021 16:20:13 +
with message-id 
and subject line Bug#978225: fixed in librarian-puppet 3.0.0-2
has caused the Debian Bug report #978225,
regarding librarian-puppet: FTBFS: ruby-faraday : Breaks: ruby-puppet-forge (<= 
2.3.2-1) but 2.3.2-1 is to be installed
to be marked as done.

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

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


-- 
978225: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978225
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: librarian-puppet
Version: 3.0.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201226 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: cucumber, debhelper (>= 11), gem2deb, rake, ruby-json, 
> ruby-librarian (>= 0.6.3~), ruby-puppet-forge, ruby-rsync, build-essential, 
> fakeroot
> Filtered Build-Depends: cucumber, debhelper (>= 11), gem2deb, rake, 
> ruby-json, ruby-librarian (>= 0.6.3~), ruby-puppet-forge, ruby-rsync, 
> build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [422 B]
> Get:5 copy:/<>/apt_archive ./ Packages [504 B]
> Fetched 1883 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> 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:
>  ruby-faraday : Breaks: ruby-puppet-forge (<= 2.3.2-1) but 2.3.2-1 is to be 
> installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://qa-logs.debian.net/2020/12/26/librarian-puppet_3.0.0-1_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with me
so that we can identify if something relevant changed in the meantime.

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: librarian-puppet
Source-Version: 3.0.0-2
Done: Sebastien Badia 

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

Debian distribution maintenance software
pp.
Sebastien Badia  (supplier of updated librarian-puppet 
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, 04 Feb 2021 17:07:11 +0100
Source: librarian-puppet
Architecture: source
Version: 3.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Sebastien Badia 
Closes: 978225
Changes:
 librarian-puppet (3.0.0-2) unstable; urgency=medium
 .
   [ Utkarsh Gupta ]
   * Add salsa-ci

Bug#978225: marked as pending in librarian-puppet

[Sebastien Badia]

Control: tag -1 pending

Hello,

Bug #978225 in librarian-puppet 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/ruby-team/librarian-puppet/-/commit/ecfc1e2692bf4bcdd31884730a4bc666869e898c


d/patches: Relax puppe-forge deps (Closes: #978225)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/978225

Processed: Bug#978225 marked as pending in librarian-puppet

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #978225 [src:librarian-puppet] librarian-puppet: FTBFS: ruby-faraday : 
Breaks: ruby-puppet-forge (<= 2.3.2-1) but 2.3.2-1 is to be installed
Added tag(s) pending.

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

Bug#981684: marked as done (src:estscan: fails to migrate to testing for too long: FTBFS on mipsel)

[Debian Bug Tracking System]

Your message dated Thu, 04 Feb 2021 15:33:43 +
with message-id 
and subject line Bug#981684: fixed in estscan 3.0.3-5
has caused the Debian Bug report #981684,
regarding src:estscan: fails to migrate to testing for too long: FTBFS on mipsel
to be marked as done.

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

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


-- 
981684: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981684
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: estscan
Version: 3.0.3-3
Severity: serious
Tags: sid bullseye ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

Your package FTBFS on mipsel.

As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and unstable for more than 60 days as
having a Release Critical bug in testing. Your package src:estscan in
its current version in unstable has been trying to migrate for 61 days
[2]. Hence, I am filing this bug.

If a package is out of sync between unstable and testing for a longer
period, this usually means that bugs in the package in testing cannot be
fixed via unstable. Additionally, blocked packages can have impact on
other packages, which makes preparing for the release more difficult.
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that
hamper the migration of their package in a timely manner.

This bug will trigger auto-removal when appropriate. As with all new
bugs, there will be at least 30 days before the package is auto-removed.

I have tagged this bug to only affect sid and bullseye, so it doesn't
affect (old-)stable.

If you believe your package is unable to migrate to testing due to
issues beyond your control, don't hesitate to contact the Release Team.

Paul

[1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=estscan




OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: estscan
Source-Version: 3.0.3-5
Done: Juhani Numminen 

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

Debian distribution maintenance software
pp.
Juhani Numminen  (supplier of updated estscan 
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: Mon, 11 Jan 2021 15:55:48 +0200
Source: estscan
Architecture: source
Version: 3.0.3-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Juhani Numminen 
Closes: 981684
Changes:
 estscan (3.0.3-5) unstable; urgency=medium
 .
   * Team Upload.
   * Accommodate CFLAGS, CPPFLAGS and FFLAGS as envvars (for hardening).
   * Fuse Makefile-related patches to a single patch file.
   * Add "set -e" before a loop in debian/rules (Policy §4.6).
   * Skip dh_dwz on mipsel as a workaround for #972269.
 (Closes: #981684)
Checksums-Sha1:
 c5518d424404edda5479e2cc71f318946813cd08 1937 estscan_3.0.3-5.dsc
 1bbebf23f8ab08d87b234bd7b6b9b1828febad4e 4920 estscan_3.0.3-5.debian.tar.xz
 39ef2e8c2a1d655087d5be76739c23eb6fda6cc3 5804 estscan_3.0.3-5_amd64.buildinfo
Checksums-Sha256:
 6cdf017f953246d5ff1f38654d9664de634409e15a87a1a26b36e715e39488a5 1937 
estscan_3.0.3-5.dsc
 195929ef742168802c353d80e85be125023b935c501525c5e588f2d237029935 4920 
estscan_3.0.3-5.debian.tar.xz
 2f6ceafef169c5fecb6950d1c0eb990427d0b7ec8f9125de7853f9bc230449d5 5804 
estscan_3.0.3-5_amd64.buildinfo
Files:
 f778c27987e2754431108db21d1704af 1937 science optional estscan_3.0.3-5.dsc
 c2b46195acb68bc5f9694c525b35264a 4920 science optional 
estscan_3.0.3-5.debian.tar.xz
 7c90a523fc5c2f12fcc4a2475890a5c8 5804 science optional 
estscan_3.0.3-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEPpmlJvXcwMu/HO6mALrnSzQzafEFAmAcDSMUHG5wYXRyYTk3
NEBnbWFpbC5jb20ACgkQALrnSzQzafFLcw//Y6O3HRscbpcqUo0sVFvC9kvUwgqB
4Yiuf9sXKHqrKMFh4b9gFW4e0F6C83d+3TVfb9N4PYaLU7qtr2j9duEUz/RETPER
Kzx9ekLAHxmenKOfXgCn0DZpDV5xl4m0wu/HKrDIvcRjxJoA8kGDdVFJhfLA0lhy
2tcMiM6w9H8insrgpW94y1qT8bvHRxadQAWWf4g/GU6g5RPG3lLDSQkmIQugvF5

Bug#979428: marked as done (src:cvsdelta: invalid maintainer address)

[Debian Bug Tracking System]

Your message dated Thu, 04 Feb 2021 15:33:38 +
with message-id 
and subject line Bug#979428: fixed in cvsdelta 1.7.0-7
has caused the Debian Bug report #979428,
regarding src:cvsdelta: invalid maintainer address
to be marked as done.

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

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


-- 
979428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979428
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cvsdelta
Version: 1.7.0-6
Severity: serious
Tags: bullseye sid
X-Debbugs-Cc: Holger Levsen 

The maintainer address (forwarded to from the maintainer's @d.o address)
is invalid, see below.

Ansgar

 Start of forwarded message 
From: Mail Delivery System 
Subject: Mail delivery failed: returning message to sender
Date: Tue, 05 Jan 2021 22:33:56 +

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  deb...@salix.org
retry timeout exceeded
Reporting-MTA: dns; mailly.debian.org

Action: failed
Final-Recipient: rfc822;debian@salix.org
Status: 5.0.0
--- End Message ---
--- Begin Message ---
Source: cvsdelta
Source-Version: 1.7.0-7
Done: Adrian Bunk 

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated cvsdelta 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, 04 Feb 2021 17:07:12 +0200
Source: cvsdelta
Architecture: source
Version: 1.7.0-7
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Adrian Bunk 
Closes: 979428
Changes:
 cvsdelta (1.7.0-7) unstable; urgency=medium
 .
   * QA upload.
   * Set maintainer to Debian QA Group. (Closes: #979428) (see #981675)
Checksums-Sha1:
 92588da26579700ee8ff989ef48f533430fe990a 1804 cvsdelta_1.7.0-7.dsc
 22898b2eba99c125a4b10ff137e1360db131b3e9 2150 cvsdelta_1.7.0-7.diff.gz
Checksums-Sha256:
 9fc8d92c1565230ad4ca43edd074a78f670ddefc0b53fcfcfdc414c08d36efed 1804 
cvsdelta_1.7.0-7.dsc
 347b0ce028cf4c1fcf9947687f78a9e0971cb33086d2ebb03fe880b02a8e18bc 2150 
cvsdelta_1.7.0-7.diff.gz
Files:
 43ba2cad71ae817ced13544e124a8ebb 1804 vcs optional cvsdelta_1.7.0-7.dsc
 5d6a4a7f2cbf2ae6edee8d40e68eed65 2150 vcs optional cvsdelta_1.7.0-7.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmAcDg8ACgkQiNJCh6LY
mLHrQw/9GQ8satQWpnWLL/zj7AlnCVZGW02yRiJgQjPwut6Li4uDPvx2MQh9VuBL
zFuO6C30NDs4Vu5kmriGJbUDqq3aOqrAFrFCMEqoentDjjzPmagwvFlxsaCKdt6J
tkFTpF7Zs0JhbomLiWJWY18slCKk6Ru0SxDnDkBn3H+ZuuHvjENwj6qMrLXIC7ez
fiZbIh8fujcXHHhDhLiGzd2nRX1DZlWhWOtOolJCHOoHM4+BsI+wKf72IuTsKPWD
qCgDD1WA+ohbntwDg3K+Da228Az7lKGteqRLmXzeeSvSHwPwwKcanYZJM0ZjDnxe
ojBtp2GyBcZ4BTsYy0+mm4Mcv/tWxEEyTF2txfqO/niwBrUOB86I2V+YSx8W8fFo
6M3dOt3ExumQ+ZuptNCn0SRxDNW5gLkCQbG6Wn7BXytdBnoSgKG/GVZGt19pZm3s
Kie0OqcguisvbNsnJicMNygtsxXnpiLR2TBiTYFzpVttuQgWCWwTSRty841DDg2o
EGVgTgTuI17Jq2R7DMCukwcNN4i1uQ6feB0EeckVffxPogmEW5tZucbnKXFFeAao
uqzxbTr1Tpg/xmul2nHlnDKZcVASgOyy1dqqohx+X1fk2aG3YFZcx6SwXM55HHET
f40Saa5gogLxgWVpZ3CpqK7PUr11FC81xqjjlQ8D3mXL5vgE2VA=
=7MBZ
-END PGP SIGNATURE End Message ---

Bug#981850: Failed: rspec-core, rspec-support

[Ritesh Raj Sarraf]

Package: ruby-rspec
Version: 3.9.0c2e2m1s3-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Dear Maintainer,

During a rebuild of the package for Bullseye, it is seen that the
package fails to build. The build failure snippet is below. It is also
noticed that the same build failure is seen on the Reproducible Builds.

```
[  294s] Finished in 2.23 seconds (files took 0.50425 seconds to load)
[  294s] 538 examples, 3 failures, 1 pending
[  294s]
[  294s] Failed examples:
[  294s]
[  294s] rspec ./spec/rspec/support/differ_spec.rb:315 # 
RSpec::Support::Differ#diff outputs unified diff message of two hashes with 
differing encoding
[  294s] rspec ./spec/rspec/support/differ_spec.rb:328 # 
RSpec::Support::Differ#diff outputs unified diff message of two hashes with 
encoding different to key encoding
[  294s] rspec ./spec/rspec/support/differ_spec.rb:158 # 
RSpec::Support::Differ#diff uses the default external encoding when the two 
strings have incompatible encodings
[  294s]
[  294s] Randomized with seed 8873
[  294s]
[  295s] cd -
[  295s] Failed: rspec-core, rspec-support
[  295s] ERROR: Test "ruby2.7" failed. Exiting.
[  295s] dh_auto_install: error: dh_ruby --install 
/usr/src/packages/BUILD/debian/tmp returned exit code 1
[  295s] make: *** [debian/rules:99: binary] Error 25
[  295s] dpkg-buildpackage: error: debian/rules binary subprocess returned exit 
status 2
```


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

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

Versions of packages ruby-rspec depends on:
ii  ruby 1:2.7+2
pn  ruby-rspec-core  
pn  ruby-rspec-expectations  
pn  ruby-rspec-mocks 

ruby-rspec recommends no packages.

ruby-rspec suggests no packages.

Processed: closing 976575

[Debian Bug Tracking System]

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

> close 976575 0~20200923.2-3
Bug #976575 [src:abseil] abseil: FTBFS on arm64,ppc64el (arch:all-only src 
pkg): dh_auto_test: error: cd shared && make -j4 test ARGS\+=-j4 returned exit 
code 2
Marked as fixed in versions abseil/0~20200923.2-3.
Bug #976575 [src:abseil] abseil: FTBFS on arm64,ppc64el (arch:all-only src 
pkg): dh_auto_test: error: cd shared && make -j4 test ARGS\+=-j4 returned exit 
code 2
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#981847: ArgumentError: invalid byte sequence in US-ASCII

[Ritesh Raj Sarraf]

Package: ruby-power-assert
Version: 1.1.7-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Dear Maintainer,

During a rebuild of the package on Bullseye, the package fails in one of
the tests. Below is the failure snippet. The same is also seen in the
Reproducible Builds reports.

```
[  194s] 
---
[  194s] 107 tests, 152 assertions, 0 failures, 1 errors, 0 pendings, 0 
omissions, 0 notifications
[  194s] 99.0654% passed
[  194s] 
---
[  194s] 23.20 tests/s, 32.95 assertions/s
[  194s] rake aborted!
[  194s] Command failed with status (1): [ruby -w -I"test"  
"/usr/share/rubygems-integration/all/gems/rake-13.0.1/lib/rake/rake_test_loader.rb"
 "test/block_test.rb" "test/dyna_symbol_key_test.rb" "test/parser_test.rb" 
"test/safe_op_test.rb" "test/trace_test.rb" "test/test_core_ext_helper.rb" 
"test/test_helper.rb" -v]
[  194s] /usr/share/rubygems-integration/all/gems/rake-13.0.1/exe/rake:27:in 
`'
[  194s] Tasks: TOP => default
[  194s] (See full trace by running task with --trace)
[  194s] ERROR: Test "ruby2.7" failed. Exiting.
[  194s] dh_auto_install: error: dh_ruby --install 
/usr/src/packages/BUILD/debian/ruby-power-assert returned exit code 1
[  194s] make: *** [debian/rules:6: binary] Error 25
[  194s] dpkg-buildpackage: error: debian/rules binary subprocess returned exit 
status 2
```


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

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

-- no debconf information

Bug#981846: python-argcomplete: multiple tests failure

[Ritesh Raj Sarraf]

Package: python-argcomplete
Version: 1.8.1-1.3
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Dear Maintainer,

During a rebuild of the package on Bullseye, multiple tests in the
package fail. A snippet of the failure is below. The same build failure
logs are also seen in the Reproducible Builds.


```
[  218s] ==
[  218s] FAIL: test_double_quoted_completion (test.test.TestBashGlobal)
[  218s] --
[  218s] Traceback (most recent call last):
[  218s]   File "/usr/src/packages/BUILD/test/test.py", line 1011, in setUp
[  218s] self.assertEqual(output, '')
[  218s] AssertionError: '\x1b[?2004l\r\x1b[?2004h' != ''
[  218s] - [?2004l
- [?2004h
[  218s]
[  218s] ==
[  218s] FAIL: test_exclamation_in_double_quotes (test.test.TestBashGlobal)
[  218s] --
[  218s] Traceback (most recent call last):
[  218s]   File "/usr/src/packages/BUILD/test/test.py", line 1011, in setUp
[  218s] self.assertEqual(output, '')
[  218s] AssertionError: '\x1b[?2004l\r\x1b[?2004h' != ''
[  218s] - [?2004l
- [?2004h
[  218s]
[  218s] ==
[  218s] FAIL: test_one_space_after_exact (test.test.TestBashGlobal)
[  218s] Test exactly one space is appended after an exact match.
[  218s] --
[  218s] Traceback (most recent call last):
[  218s]   File "/usr/src/packages/BUILD/test/test.py", line 1011, in setUp
[  218s] self.assertEqual(output, '')
[  218s] AssertionError: '\x1b[?2004l\r\x1b[?2004h' != ''
[  218s] - [?2004l
- [?2004h
[  218s]
[  218s] ==
[  218s] FAIL: test_parse_special_characters (test.test.TestBashGlobal)
[  218s] --
[  218s] Traceback (most recent call last):
[  218s]   File "/usr/src/packages/BUILD/test/test.py", line 1011, in setUp
[  218s] self.assertEqual(output, '')
[  218s] AssertionError: '\x1b[?2004l\r\x1b[?2004h' != ''
[  218s] - [?2004l
- [?2004h
[  218s]
[  218s] ==
[  218s] FAIL: test_parse_special_characters_dollar (test.test.TestBashGlobal)
[  218s] --
[  218s] Traceback (most recent call last):
[  218s]   File "/usr/src/packages/BUILD/test/test.py", line 1011, in setUp
[  218s] self.assertEqual(output, '')
[  218s] AssertionError: '\x1b[?2004l\r\x1b[?2004h' != ''
[  218s] - [?2004l
- [?2004h
[  218s]
[  218s] ==
[  218s] FAIL: test_partial_completion (test.test.TestBashGlobal)
[  218s] --
[  218s] Traceback (most recent call last):
[  218s]   File "/usr/src/packages/BUILD/test/test.py", line 1011, in setUp
[  218s] self.assertEqual(output, '')
[  218s] AssertionError: '\x1b[?2004l\r\x1b[?2004h' != ''
[  218s] - [?2004l
- [?2004h
[  218s]
[  218s] ==
[  218s] FAIL: test_python_completion (test.test.TestBashGlobal)
[  218s] --
[  218s] Traceback (most recent call last):
[  218s]   File "/usr/src/packages/BUILD/test/test.py", line 1011, in setUp
[  218s] self.assertEqual(output, '')
[  218s] AssertionError: '\x1b[?2004l\r\x1b[?2004h' != ''
[  218s] - [?2004l
- [?2004h
[  218s]
[  218s] ==
[  218s] FAIL: test_python_filename_completion (test.test.TestBashGlobal)
[  218s] --
[  218s] Traceback (most recent call last):
[  218s]   File "/usr/src/packages/BUILD/test/test.py", line 1011, in setUp
[  218s] self.assertEqual(output, '')
[  218s] AssertionError: '\x1b[?2004l\r\x1b[?2004h' != ''
[  218s] - [?2004l
- [?2004h
[  218s]
[  218s] ==
[  218s] FAIL: test_python_not_executable (test.test.TestBashGlobal)
[  218s] Test completing a script that cannot be run directly.
[  218s] --
[  218s] Traceback (most recent call last):
[  218s]   File "/usr/src/packages/BUILD/test/test.py", line 1011, in setUp
[  218s] self.assertEqual(output, '')
[  218s] AssertionError: '\x1b[?2004l\r\x1b[?2004h' != ''
[  218s] - [?2004l
- [?2004h
[  218s]
[  218s] ==
[  218s] FAIL: test_quoted_exact (test.test.TestBashGlob

Bug#981842: acpica-unix: multiple definition of `AslCompilerlval'

[Ritesh Raj Sarraf]

Source: acpica-unix
Version: 20190509-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

During a rebuild of the package on Debian Bullseye, the package fails to
build. A snippet of the build failure is below. The same build failure
is also seen in the Reproducible Builds.

```
[  219s] -  flex ../../../source/compiler/aslcompiler.l
[  219s] -  Intermediate obj/aslcompilerlex.c
[  222s] - Link obj/iasl
[  222s] /usr/bin/ld: 
obj/aslcompilerparse.o:./generate/unix/iasl/y.tab.c:11227: multiple definition 
of `AslCompilerlval'; 
obj/aslcompilerlex.o:./generate/unix/iasl/../../../source/compiler/aslcompiler.l:51:
 first defined here
[  222s] /usr/bin/ld: 
obj/prparserlex.o:./generate/unix/iasl/../../../source/compiler/prparser.l:119: 
multiple definition of `LexBuffer'; 
obj/dtparserlex.o:./generate/unix/iasl/../../../source/compiler/dtparser.l:103: 
first defined here
[  223s] collect2: error: ld returned 1 exit status
[  223s] make[3]: *** [../Makefile.rules:15: obj/iasl] Error 1
[  223s] make[3]: Leaving directory '/usr/src/packages/BUILD/generate/unix/iasl'
[  223s] make[2]: *** [generate/unix/Makefile.common:7: iasl] Error 2
[  223s] make[2]: Leaving directory '/usr/src/packages/BUILD'
[  223s] dh_auto_build: error: make -j3 "OPT_CFLAGS=-g -O2 
-ffile-prefix-map=/usr/src/packages/BUILD=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall 
-fno-strict-aliasing" CC=gcc returned exit code 2
[  223s] make[1]: *** [debian/rules:78: override_dh_auto_build] Error 25
[  223s] make[1]: Leaving directory '/usr/src/packages/BUILD'
[  223s] make: *** [debian/rules:31: build] Error 2
[  223s] dpkg-buildpackage: error: debian/rules build subprocess returned exit 
status 2
[  223s]
```


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

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

Bug#981390: marked as done (kylin-video: drop (build-)dependency on crystalhd, which will not be in bullseye)

[Debian Bug Tracking System]

Your message dated Thu, 04 Feb 2021 13:51:05 +
with message-id 
and subject line Bug#981390: fixed in kylin-video 2.1.2-1
has caused the Debian Bug report #981390,
regarding kylin-video: drop (build-)dependency on crystalhd, which will not be 
in bullseye
to be marked as done.

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

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


-- 
981390: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981390
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: crystalhd
Version: 1:0.0~git20110715.fdd2f19-1
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

It seems that libcrystalhd3 is only really useful together with
firmware-crystalhd, which was never really usable in Debian, leading to
that package being dropped: https://bugs.debian.org/865978

If someone wants to revive CrystalHD in Debian, it seems a good place to
start is https://www.mythtv.org/wiki/Broadcom_Crystal_HD#Feb._2014_Update

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl1MQbwACgkQLHwxRsGg
ASEoVRAAkB3aduIq0KZJ88R68h8cQ27Fa86ekxCdTceenMidmoLts/iLDkkBCc0z
ocvrLY0iJDfqYmfA7gWCJ10OlgwDonm1Y2JmgRlPkL5XjLNERm7MzE6awHaa8DeM
lGe0WlG8bFDrUVGZYdz5/kOfEV0vuZsZyTcrmnUcEXeUFWwcU/H73XjzlEZvlOIf
pIxdvVpbQB+hZiQiNoTBIcd4jBhiw7Y95DenzBNWEkqhfD6+p3Q/d6ypRpLXNmAV
3vx1slhgvKIUEfW/2Xed6oTJdwSMxwtWenB+bk+pTnw1EHZ98Nn6ECCwzuiBxpYp
CwmB48dRMcVKPK3VFO0Tg+YMkf1J7l/TVONOl9RZdu54Bo0Mzt3ZHbedW3gpNdZE
bx6Tty2OnnZ7mENEXRKi9ZamrP3Wpx6+ECIZZ9BtJsbYvoDQFrMQfGcHn1d0Ydfk
5eNTt0t3WnjrgvtGyXtln95celT3rE3LhgFevs0XW7iFCpmtYnztCve2q9676K0R
xZnPb5sxldxehB2gh7leDkBXXoWPRMdIKFS7Q7RSh3JYpX4wBO9+a4OM/qJAyZg4
bWWiCTL1spnewlnZYmll6QaACHDnLQHKU9ffZlRU3TrEz0sFuygeVVmPW5FupT/w
sejq90AdGATqDfPffiz4G/P4VwhyHfiSb2/1g/C6sMoIWvti4us=
=kb8u
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: kylin-video
Source-Version: 2.1.2-1
Done: handsome_feng 

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

Debian distribution maintenance software
pp.
handsome_feng  (supplier of updated kylin-video 
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, 04 Feb 2021 12:54:57 +
Source: kylin-video
Architecture: source
Version: 2.1.2-1
Distribution: unstable
Urgency: medium
Maintainer: Kylin Team 
Changed-By: handsome_feng 
Closes: 981390
Changes:
 kylin-video (2.1.2-1) unstable; urgency=medium
 .
   * New upstream release.
 - Add the supported audio and video formats to the desktop file.
 .
   * d/control:
 - Drop dependency on crystalhd. (Closes: #981390)
 - Bump Standards-Version to 4.5.1.
Checksums-Sha1:
 372e4d21652646072ce0df0fcbc483f440fd0091 2136 kylin-video_2.1.2-1.dsc
 cf444e3526d560a46b3466b142bcc561d22f7f9b 1313387 kylin-video_2.1.2.orig.tar.gz
 b7bca8a60aebe4aca71d3b5362429d4424ebc91f 4188 kylin-video_2.1.2-1.debian.tar.xz
 6469dda428786a1954d156f3ab00e4a23bdd2e4b 12573 
kylin-video_2.1.2-1_source.buildinfo
Checksums-Sha256:
 4eb575e39f3bd2665439b8dd0f5802f432458e1d7cfa9472d2de9bbc67ee5c43 2136 
kylin-video_2.1.2-1.dsc
 bc77f804bd946fcec21af8b38ad623ace3a1960c775314e2ef97af643eab8c1e 1313387 
kylin-video_2.1.2.orig.tar.gz
 b481b932c9cfba4ba18774d5e549121be237a0205eb6ef7cce035e8c4a1050c6 4188 
kylin-video_2.1.2-1.debian.tar.xz
 0d74fae3e141fe702bd8fe0973cddce2ae6c51962261dc82bc69f0ef9f614ba7 12573 
kylin-video_2.1.2-1_source.buildinfo
Files:
 0ded90b465fae8214b7ba7a6ebfe8c17 2136 video optional kylin-video_2.1.2-1.dsc
 368492f66cdf7af4fd85a72d3cd54232 1313387 video optional 
kylin-video_2.1.2.orig.tar.gz
 d7f3d9be0d40c1f0cd1995fb5859b248 4188 video optional 
kylin-video_2.1.2-1.debian.tar.xz
 c7e8ad8941eda3b5c990041dd3f26c9a 12573 video optional 
kylin-video_2.1.2-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJPBAEBCAA5FiEEhsgAHpUwnacZWWSCm7hQwBMRHwwFAmAb9NYbHGppYW5mZW5n
bGlAdWJ1bnR1a3lsaW4uY29tAAoJEJu4UMATER8Mz5MP/3MHSVQqJiwcqax09uiK
Ns6+kIEr2Hk7omSSnt5c17t1tvvVICfl/vOY6/sEw5uvNH2NIEtCO1CZG+Wv2eYm
91CqEN9AhIETYHj7J3uSifl8Y8Rx1MhI+ftvhUcvXH2m8ZjHum0nP6LkzIFP8LgB
yVfyJ5RajeHYo2FraG17LKfU