Bug#1008235: problem with bash multilingual variables

[Salvatore Bonaccorso]

Hi,

On Sun, Mar 27, 2022 at 06:06:35PM +0200, Frank Heckenbach wrote:
> Hi.
> 
> > I was hit by the bug in Debian Stable:
> > 
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008235
> > 
> > that caused silent data corruption on our production server.
> > The bug persists in yesterdays update of Debian to 11.3.
> > 
> > 
> > 
> > You have had similiar poblems here:
> > 
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003012
> > 
> > How did you work around that problem in Debian Stable?
> > Compile bash from source by yourself?

The update addressing this isssue is pending for the next point
release as per https://bugs.debian.org/1006504

Regards,
Salvatore

Processed: Re: [Pkg-javascript-devel] Bug#1008756: node-npmrc: autopkgtest needs update for new version of nodejs: require(...).tmpDir is not a function

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 1.1.1-3
Bug #1008756 [src:node-npmrc] node-npmrc: autopkgtest needs update for new 
version of nodejs: require(...).tmpDir is not a function
Marked as fixed in versions node-npmrc/1.1.1-3.

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

Bug#1008756: [Pkg-javascript-devel] Bug#1008756: node-npmrc: autopkgtest needs update for new version of nodejs: require(...).tmpDir is not a function

[Yadd]

Control: fixed -1 1.1.1-3

On 31/03/2022 21:44, Paul Gevers wrote:

Source: node-npmrc
Version: 1.1.1-2
Severity: serious
X-Debbugs-CC: nod...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:nodejs

Dear maintainer(s),

With a recent upload of nodejs in the nodejs transition the autopkgtest 
of node-npmrc fails in testing when that autopkgtest is run with the 
binary packages of nodejs from unstable. It passes when run with only 
packages from testing. In tabular form:


    pass    fail
nodejs from testing    16.13.2+really14.19.1~dfsg-6
node-npmrc from testing    1.1.1-2
all others from testing    from testing


Hi,

it is already fixed in node-npmrc 1.1.1-3, which build-depends on nodejs 
>= 14. What else can we do ? A "Breaks" in nodejs ?

Bug#996324: marked as done (ruby-netcdf: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Segmentation fault at 0x0000000000000034)

[Debian Bug Tracking System]

Your message dated Fri, 01 Apr 2022 02:49:04 +
with message-id 
and subject line Bug#996324: fixed in ruby-netcdf 0.8.0-1
has caused the Debian Bug report #996324,
regarding ruby-netcdf: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: 
Segmentation fault at 0x0034
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.)


-- 
996324: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996324
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-netcdf
Version: 0.7.2-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0

Hi,

We are about to enable building against ruby3.0 on unstable. During a test
rebuild, ruby-netcdf was found to fail to build in that situation.

To reproduce this locally, you need to install ruby-all-dev from experimental
on an unstable system or build chroot.

Relevant part (hopefully):
> /usr/bin/ruby3.0 /usr/bin/gem2deb-test-runner
> 
> ┌──┐
> │ Run tests for ruby3.0 from debian/ruby-test-files.yaml  
>  │
> └──┘
> 
> RUBYLIB=/<>/debian/ruby-netcdf/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/3.0.0:/<>/debian/ruby-netcdf/usr/lib/ruby/vendor_ruby:.
>  
> GEM_PATH=/<>/debian/ruby-netcdf/usr/share/rubygems-integration/3.0.0:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0
>  ruby3.0 -ryaml -e YAML.load_file\(\"debian/ruby-test-files.yaml\"\).each\ 
> \{\ \|f\|\ require\ f\ \}
> Loaded suite -e
> Started
> 
> Finished in 0.028058613 seconds.
> ---
> 20 tests, 127 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions, 0 
> notifications
> 100% passed
> ---
> 712.79 tests/s, 4526.24 assertions/s-e: [BUG] Segmentation fault at 
> 0x0034
> ruby 3.0.2p107 (2021-07-07 revision 0db68f0233) [x86_64-linux-gnu]
> 
> -- Control frame information ---
> c:0001 p: s:0003 E:001f10 (none) [FINISH]
> 
> 
> -- Machine register context 
>  RIP: 0x0034 RBP: 0x5644105564a0 RSP: 0x7ffc66891258
>  RAX: 0x0034 RBX: 0x564410569488 RCX: 0x0001
>  RDX: 0x564410569b18 RDI: 0x0034 RSI: 0x7ffc66891278
>   R8: 0x564410569780  R9: 0x0001 R10: 0x7ffc668911e0
>  R11: 0x0246 R12: 0x564410568000 R13: 0x564410564a30
>  R14: 0x564410569488 R15: 0x56440ff00760 EFL: 0x00010202
> 
> -- C level backtrace information ---
> ERROR: Test "ruby3.0" failed.


The full build log is available at
https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-netcdf/ruby-netcdf_0.7.2-5+rebuild1633388714_amd64.build.txt


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ruby-netcdf
Source-Version: 0.8.0-1
Done: Youhei SASAKI 

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

Debian distribution maintenance software
pp.
Youhei SASAKI  (supplier of updated ruby-netcdf 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, 01 Apr 2022 10:54:49 +0900
Source: ruby-netcdf
Architecture: source
Version: 0.8.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian GIS Project 
Changed-By: Youhei SASAKI 
Closes: 996324
Changes:
 ruby-netcdf (0.8.0-1) unstable; urgency=medium
 .
   [ Bas Couwenberg ]
   * Bump watch file version to 4.
   * Update lintian overrides.
   * Bump Standards-Version to 4.6.0, no changes.
   * Rename sal

Bug#1008733: python-clickhouse-driver: diff for NMU version 0.2.3-1.1

[Stefano Rivera]

Control: tags 1008733 + patch
Control: tags 1008733 + pending

Dear maintainer,

I've prepared an NMU for python-clickhouse-driver (versioned as 0.2.3-1.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.

SR
diff -Nru python-clickhouse-driver-0.2.3/debian/changelog python-clickhouse-driver-0.2.3/debian/changelog
--- python-clickhouse-driver-0.2.3/debian/changelog	2022-03-22 19:49:28.0 -0400
+++ python-clickhouse-driver-0.2.3/debian/changelog	2022-03-31 22:07:11.0 -0400
@@ -1,3 +1,10 @@
+python-clickhouse-driver (0.2.3-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Avoid hard-coding Python versions in conf.py (Closes: #1008733)
+
+ -- Stefano Rivera   Thu, 31 Mar 2022 22:07:11 -0400
+
 python-clickhouse-driver (0.2.3-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru python-clickhouse-driver-0.2.3/debian/patches/insert-doc-build-path.patch python-clickhouse-driver-0.2.3/debian/patches/insert-doc-build-path.patch
--- python-clickhouse-driver-0.2.3/debian/patches/insert-doc-build-path.patch	2022-03-22 19:49:28.0 -0400
+++ python-clickhouse-driver-0.2.3/debian/patches/insert-doc-build-path.patch	2022-03-31 22:06:59.0 -0400
@@ -4,13 +4,14 @@
 
 --- a/docs/conf.py
 +++ b/docs/conf.py
-@@ -16,6 +16,10 @@
+@@ -16,6 +16,11 @@
  # import sys
  # sys.path.insert(0, os.path.abspath('.'))
  
 +import os, sys
-+sys.path.insert(0, os.path.abspath("../debian/python3-clickhouse-driver/usr/lib/python3.8/dist-packages"))
-+sys.path.insert(0, os.path.abspath("../debian/python3-clickhouse-driver/usr/lib/python3.9/dist-packages"))
++sys.path.insert(0, os.path.abspath(
++f"../debian/python3-clickhouse-driver/usr/lib/python{sys.version_info[0]}"
++f".{sys.version_info[1]}/dist-packages"))
 +
  from clickhouse_driver import __version__, VERSION
  
diff -Nru python-clickhouse-driver-0.2.3/debian/patches/remove-sphinx-github-iframe.patch python-clickhouse-driver-0.2.3/debian/patches/remove-sphinx-github-iframe.patch
--- python-clickhouse-driver-0.2.3/debian/patches/remove-sphinx-github-iframe.patch	2022-03-22 19:49:28.0 -0400
+++ python-clickhouse-driver-0.2.3/debian/patches/remove-sphinx-github-iframe.patch	2022-03-31 22:07:07.0 -0400
@@ -4,7 +4,7 @@
 
 --- a/docs/conf.py
 +++ b/docs/conf.py
-@@ -102,8 +102,6 @@
+@@ -103,8 +103,6 @@
  html_static_path = ['_static']
  html_theme_options = {
  "description": "Python driver for ClickHouse",

Processed: python-clickhouse-driver: diff for NMU version 0.2.3-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1008733 + patch
Bug #1008733 [src:python-clickhouse-driver] python-clickhouse-driver: FTBFS 
with Python 3.10 as default
Added tag(s) patch.
> tags 1008733 + pending
Bug #1008733 [src:python-clickhouse-driver] python-clickhouse-driver: FTBFS 
with Python 3.10 as default
Added tag(s) pending.

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

Bug#1002443: marked as done (python-setuptools-rust: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)

[Debian Bug Tracking System]

Your message dated Fri, 01 Apr 2022 01:19:13 +
with message-id 
and subject line Bug#1002443: fixed in python-setuptools-rust 1.2.0-1
has caused the Debian Bug report #1002443,
regarding python-setuptools-rust: FTBFS: dpkg-buildpackage: error: dpkg-source 
-b . subprocess returned exit status 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.)


-- 
1002443: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002443
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-setuptools-rust
Version: 1.1.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules clean
> dh clean --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:237: python3.10 setup.py clean 
> running clean
> removing '/<>/.pybuild/cpython3_3.10/build' (and everything 
> under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.10' does not exist -- can't clean it
> I: pybuild base:237: python3.9 setup.py clean 
> running clean
> removing '/<>/.pybuild/cpython3_3.9/build' (and everything under 
> it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.9' does not exist -- can't clean it
>dh_autoreconf_clean -O--buildsystem=pybuild
>dh_clean -O--buildsystem=pybuild
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building python-setuptools-rust using existing 
> ./python-setuptools-rust_1.1.1.orig.tar.gz
> dpkg-source: info: local changes detected, the modified files are:
>  python-setuptools-rust-1.1.1/setuptools_rust/version.py
> dpkg-source: error: aborting due to unexpected upstream changes, see 
> /tmp/python-setuptools-rust_1.1.1-1.diff.ZfGqSC
> dpkg-source: info: Hint: make sure the version in debian/changelog matches 
> the unpacked source tree
> dpkg-source: info: you can integrate the local changes with dpkg-source 
> --commit
> dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2
> 
> Build finished at 2021-12-20T18:31:50Z


The full build log is available from:
http://qa-logs.debian.net/2021/12/20/python-setuptools-rust_1.1.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!

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 mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: python-setuptools-rust
Source-Version: 1.2.0-1
Done: Stefano Rivera 

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

Debian distribution maintenance software
pp.
Stefano Rivera  (supplier of updated 
python-setuptools-rust 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, 31 Mar 2022 21:02:18 -0400
Source: python-setuptools-rust
Architecture: source
Version: 1.2.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Stefano Rivera 
Closes: 1002443
Changes:
 python-setuptools-rust (1.2.0-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream release.
   * Delete version.py on clean. Closes: #1002443
   * Bump Standards-Version to 4.6.0, no changes needed.
   * Drop Build-Depends on python3-tomli, no longer needed.
Checksums-Sha1:
 a1f7bb2f4b6cee26526a7ff97b2f187726f0609e 1710 
python-setuptools-rust_1.2.0-1.dsc
 0afe8a113a5fbc6a7eca89bc0eb2a0c71c3dd005 286146 
python-setuptools-rust_1.2.0.orig.tar.gz
 1e7b06cef9ed026225a6dfbf9dc28b66abf8ae01 2092 
python-setuptools-rust_1.2.0-1.debian.tar.xz

Bug#1008189: meson: gnome module incorrectly requires gtk4-update-icon-cache

[Mohammad .Sheykh Mohammadi]

On Thu, 24 Mar 2022 10:45:33 -0400 Jeremy Bicha 
wrote:
> Control: tags -1 +ftbfs
> Control: affects -1 src:gnome-contacts
> Control: affects -1 src:gtksourceview5
>
> On Thu, Mar 24, 2022 at 10:13 AM Jussi Pakkanen 
wrote:
> > This has already been tagged for the .1 release:
> >
> > https://github.com/mesonbuild/meson/milestone/79?closed=1
> >
> > Is that sufficient or do you need an interim distropatch upload?
>
> I think it's only a fairly small number of Debian apps affected. I can
> manually add the extra Build-Depends if I need to do a quicker upload
> of affected packages.
>
> Thank you,
> Jeremy Bicha
>
>

Processed: Re: Bug#1008764: dpkg: [dpkg-fsys-usrunmess] fails to copy /lib/modules directories, breaks

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #1008764 [dpkg] dpkg: [dpkg-fsys-usrunmess] fails to copy /lib/modules 
directories, breaks
Severity set to 'normal' from 'critical'

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

Bug#1008764: dpkg: [dpkg-fsys-usrunmess] fails to copy /lib/modules directories, breaks

[Guillem Jover]

Control: severity -1 normal

Hi!

On Fri, 2022-04-01 at 07:27:26 +0900, Norbert Preining wrote:
> Package: dpkg
> Version: 1.21.6
> Severity: critical
> Justification: breaks the whole system

The script does not break the whole system, it fails quite early
during preparations before doing any migration.

> my system was installed *after* buster and now is in the unfortunate
> messed up state.
> 
> I tried to fix it as suggested by dpkg using dpkg-fsys-usrunmess, but
> it fails reproducibly:
> $ dpkg-fsys-usrunmess
> ...
> D: creating shadow file = /.usrunmess/lib/modprobe.d/aliases.conf
> D: creating shadow file = /.usrunmess/lib/modprobe.d/fbdev-blacklist.conf
> D: creating shadow file = /.usrunmess/lib/modprobe.d/systemd.conf
> D: creating shadow dir = 
> /.usrunmess/lib/modules/5.15.15+futex+zstd+intel+wine+
> error: cannot mkdir /.usrunmess/lib/modules/5.15.15+futex+zstd+intel+wine+: 
> No such file or directory
> $
> 
> I have my own compiled kernels.
> 
> The problem is that it seems to be a missing mkdir -p  or similar.

Sorry, it looks like I previously only fixed the cases of mixed tracked
and untracked kernel module files there. I've now fixed this locally,
which will be included in 1.21.7.

You'll need to remove the shadow hierarchy before being able to run
this again with a fixed script though.

Thanks,
Guillem

Bug#1008765: claws-mail: build-depends on unavailable package libltdl3-dev

[Ricardo Mones]

Package: claws-mail
Version: 4.0.0-3
Severity: grave
Tags: ftbfs
Justification: renders package unusable
X-Debbugs-Cc: mo...@debian.org

Just noticed claws-mail is also affected by 2.4.7-2 upload of libtool,
like detailed in bugs #1008470 and #1008698.

This is a remainder to my future self to fix it next week, taking
advantage of the next upstream release this weekend.

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

Bug#1008764: dpkg: [dpkg-fsys-usrunmess] fails to copy /lib/modules directories, breaks

[Norbert Preining]

Package: dpkg
Version: 1.21.6
Severity: critical
Justification: breaks the whole system
X-Debbugs-Cc: norb...@preining.info

Hi

my system was installed *after* buster and now is in the unfortunate
messed up state.

I tried to fix it as suggested by dpkg using dpkg-fsys-usrunmess, but
it fails reproducibly:
$ dpkg-fsys-usrunmess
...
D: creating shadow file = /.usrunmess/lib/modprobe.d/aliases.conf
D: creating shadow file = /.usrunmess/lib/modprobe.d/fbdev-blacklist.conf
D: creating shadow file = /.usrunmess/lib/modprobe.d/systemd.conf
D: creating shadow dir = /.usrunmess/lib/modules/5.15.15+futex+zstd+intel+wine+
error: cannot mkdir /.usrunmess/lib/modules/5.15.15+futex+zstd+intel+wine+: No 
such file or directory
$

I have my own compiled kernels.

The problem is that it seems to be a missing mkdir -p  or similar.

Wth that, I cannot convert the system.

Best

Norbert



-- Package-specific info:
This system uses merged-usr-via-aliased-dirs, going behind dpkg's
back, breaking its core assumptions. This can cause silent file
overwrites and disappearances, and its general tools misbehavior.
See .

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

Kernel: Linux 5.16.17+futex+wine+ (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages dpkg depends on:
ii  libbz2-1.0   1.0.8-5
ii  libc62.33-7
ii  liblzma5 5.2.5-2
ii  libselinux1  3.3-1+b2
ii  tar  1.34+dfsg-1
ii  zlib1g   1:1.2.11.dfsg-4

dpkg recommends no packages.

Versions of packages dpkg suggests:
ii  apt2.4.3
pn  debsig-verify  

-- no debconf information

Bug#965434: marked as done (barada-pam: Removal of obsolete debhelper compat 5 and 6 in bookworm)

[Debian Bug Tracking System]

Your message dated Thu, 31 Mar 2022 22:03:45 +
with message-id 
and subject line Bug#965434: fixed in barada-pam 0.5-3.2
has caused the Debian Bug report #965434,
regarding barada-pam: Removal of obsolete debhelper compat 5 and 6 in bookworm
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.)


-- 
965434: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965434
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: barada-pam
Version: 0.5-3.1
Severity: normal
Usertags: compat-5-6-removal

Hi,

The package barada-pam uses debhelper with a compat level of 5 or 6,
which is deprecated and scheduled for removal[1].

Please bump the debhelper compat at your earliest convenience
/outside the freeze/!

  * Compat 13 is recommended (supported in stable-backports)

  * Compat 7 is the bare minimum


PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads
with compat bumps during the freeze.

If there is any risk that the fix for this bug might not migrate to
testing before 2021-01-01[3] then please postpone the fix until after
the freeze.


At the time of filing this bug, compat 5 and 6 are expected to be
removed "some time during the development cycle of bookworm".


Thanks,
~Niels


[1] https://lists.debian.org/debian-devel/2020/07/msg00065.html

[2] https://release.debian.org/bullseye/FAQ.html

[3] The choice of 2021-01-01 as a "deadline" is set before the actual
freeze deadline to provide a safe cut off point for most people.

Mind you, it is still your responsibility to ensure that the upload
makes it into testing even if you upload before that date.
--- End Message ---
--- Begin Message ---
Source: barada-pam
Source-Version: 0.5-3.2
Done: Guilherme de Paula Xavier Segundo 

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

Debian distribution maintenance software
pp.
Guilherme de Paula Xavier Segundo  (supplier of 
updated barada-pam package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 29 Mar 2022 14:08:27 -0300
Source: barada-pam
Architecture: source
Version: 0.5-3.2
Distribution: unstable
Urgency: medium
Maintainer: Andrew Pollock 
Changed-By: Guilherme de Paula Xavier Segundo 
Closes: 965434
Changes:
 barada-pam (0.5-3.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Using new DH level format. Consequently:
   - debian/compat: removed.
   - debian/control: changed from 'debhelper' to 'debhelper-compat' in
 Build-Depends field and bumped level to 13.
   - Closes: #965434
Checksums-Sha1:
 77a3cde5c87d53fb179b8ae3d9f94ee352150ad8 1819 barada-pam_0.5-3.2.dsc
 15d943d519bbe0355e51a67499e60314d483c3a1 4840 barada-pam_0.5-3.2.debian.tar.xz
 d3791d59af16f4c0821bbf6609a698323b9fc933 6062 
barada-pam_0.5-3.2_source.buildinfo
Checksums-Sha256:
 d46df71da9a96e5a4dac3032430370975fdcf5c2935015fd55f850a9800dfda6 1819 
barada-pam_0.5-3.2.dsc
 1d1ee9b607af688b8c66f6ceb21c7000eb239d0212769ee641275ab7a7659486 4840 
barada-pam_0.5-3.2.debian.tar.xz
 903261c629cea753e7134e56fed7d4fe2ce596326e5d50dd8ea31062a5b89c3d 6062 
barada-pam_0.5-3.2_source.buildinfo
Files:
 9f4768b691e0a2320b3da2c54923e6b8 1819 libs extra barada-pam_0.5-3.2.dsc
 f69dc4bb4a68e1db01417d90a227d40f 4840 libs extra 
barada-pam_0.5-3.2.debian.tar.xz
 91f93fd118feefb69165fbe94b55547f 6062 libs extra 
barada-pam_0.5-3.2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAmJDeSEACgkQ3mO5xwTr
6e+akw//SJJERodoX/s0x6UZvntu3PhZPvIzQ/6WOs9BE2PTnIOSInY40WlNwa7j
xvgIb4VTkjy2sgQ/fa26vZLdiGyzFhiJRh4XhtU3hc8zoPI5HLJ2LnNX6QI2dNGO
4oaZZMx23nGmNuieGpYpUPsZ6jZJ6NPYVSWApulGyZG5r1TmqxXHSqszo1K2fa4o
hcuBJIrxUXuY7L1ui0ISCKiQluehvyO6hf2p5hwu1HC5j57qZrT4jYSTXLnz8uFy
Xf7ry2rQoNQQQRNiuMP0ZAKJfvVBz+2VbJz/GvRigGzrNtfyXgnokzLxDUdsTDTF
xxHi3Snv4QS2MApB2+CbZpRXr2TJ0zKCmDFfyTZgJBF8qTtgllc43/lcHeC0I+EE
jEPavCjFi4jFUjh8Ab9qj7rUoPi6ykG09Uut6rF3QPs1FA/1KBfskM4y7JQHIrio
2QpxrKlpn2QN0UkKByfrKDTR5XuAW1wFNjKcqKJL+UK9f/zuDaQZ3QFkAzxr3SU2
uREUXlCOJTQaoX+1mX7XgGTjz7wQcuqEFaTAt8+rRLzXqOFDXyaUnoGIgkQUF6y1
beTJP5Y16jLO

Bug#1008701: Should broctl be removed?

[Hilko Bengen]

severity -1 normal
reassign -1 ftp.debian.org
retitle -1 RM: broctl -- RoM; obsolete, superceded by zeekctl
thx

Bug#1005423: marked as done (ruby-sshkit: FTBFS: ERROR: Test "ruby2.7" failed: /<>/test/unit/runners/test_parallel.rb:9:in `block in test_wraps_ruby_standard_error_in_execute_error': oh n

[Debian Bug Tracking System]

Your message dated Thu, 31 Mar 2022 21:24:40 +
with message-id 
and subject line Bug#1005423: fixed in ruby-sshkit 1.21.2-1
has caused the Debian Bug report #1005423,
regarding ruby-sshkit: FTBFS: ERROR: Test "ruby2.7" failed: 
/<>/test/unit/runners/test_parallel.rb:9:in `block in 
test_wraps_ruby_standard_error_in_execute_error': oh no! (RuntimeError)
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.)


-- 
1005423: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005423
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-sshkit
Version: 1.20.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220212 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> /<>/test/unit/runners/test_parallel.rb:9:in `block in 
> test_wraps_ruby_standard_error_in_execute_error': oh no! (RuntimeError)
>   from /<>/lib/sshkit/backends/abstract.rb:31:in 
> `instance_exec'
>   from /<>/lib/sshkit/backends/abstract.rb:31:in `run'
>   from /<>/lib/sshkit/runners/parallel.rb:12:in `block (2 
> levels) in execute'
>  PASS (0.00s)
> 
> SSHKit::TestPretty
>   test_debug_output_with_colorPASS (0.00s)
> 
> SSHKit::TestPretty
>   test_info_output_with_color PASS (0.00s)
> 
> SSHKit::TestPretty
>   test_debug_output_without_color PASS (0.00s)
> 
> SSHKit::TestPretty
>   test_does_not_log_message_when_verbosity_is_too_low PASS (0.00s)
> 
> SSHKit::TestPretty
>   test_can_write_to_output_which_just_supports_append PASS (0.00s)
> 
> SSHKit::TestPretty
>   test_does_not_log_command_when_verbosity_is_too_low PASS (0.00s)
> 
> SSHKit::TestPretty
>   test_info_output_without_color  PASS (0.00s)
> 
> SSHKit::TestPretty
>   test_command_lifecycle_logging_with_color   PASS (0.00s)
> 
> SSHKit::TestPretty
>   test_fatal_output_with_colorPASS (0.00s)
> 
> SSHKit::TestPretty
>   test_warn_output_with_color PASS (0.00s)
> 
> SSHKit::TestPretty
>   test_error_output_without_color PASS (0.00s)
> 
> SSHKit::TestPretty
>   test_log_output_without_color   PASS (0.00s)
> 
> SSHKit::TestPretty
>   test_warn_output_without_color  PASS (0.00s)
> 
> SSHKit::TestPretty
>   test_logging_message_with_leading_and_trailing_spacePASS (0.00s)
> 
> SSHKit::TestPretty
>   test_fatal_output_without_color PASS (0.00s)
> 
> SSHKit::TestPretty
>   test_log_output_with_color  PASS (0.00s)
> 
> SSHKit::TestCustom
>   test_accepts_options_hash   PASS (0.00s)
> 
> SSHKit::TestCustom
>   test_log_loggingPASS (0.00s)
> 
> SSHKit::TestCustom
>   test_debug_logging  PASS (0.00s)
> 
> SSHKit::TestCustom
>   test_error_logging  PASS (0.00s)
> 
> SSHKit::TestCustom
>   test_info_logging   PASS (0.00s)
> 
> SSHKit::TestCustom
>   test_warn_logging   PASS (0.00s)
> 
> SSHKit::TestCustom
>   test_double_chevron_logs_commands   PASS (0.00s)
> 
> SSHKit::TestCustom
>   test_write_logs_commandsPASS (0.00s)
> 
> SSHKit::TestCustom
>   test_fatal_logging  PASS (0.00s)
> 
> SSHKit::TestDeprecationLogger
>   test_handles_nil_outputERROR (0.00s)
> Minitest::UnexpectedError: NameError: uninitialized constant 
> SSHKit::DeprecationLogger::Set
> Did you mean?  Net
> /<>/lib/sshkit/deprecation_logger.rb:5:in 
> `initialize'
> /<>/test/unit/test_deprecation_logger.rb:16:in `new'
> /<>/test/unit/test_deprecation_logger.rb:16:in 
> `test_handles_nil_output'
> 
> 
> SSHKit::TestCoordinator
>   test_connection_manager_resolves_hosts  PASS (0.00s)
> 
> SSHKit::TestCoordinator
>   test_the_connection_manager_can_run_things_in_sequence_with_wait PASS 
> (10.01s)
> 
> SSHKit::TestCoordinator
>   test_the_connection_manager_handle

Bug#1008549: marked as done (gnome-shell-extension-hamster: does not declare compatibility with GNOME Shell 42)

[Debian Bug Tracking System]

Your message dated Thu, 31 Mar 2022 21:06:50 +
with message-id 
and subject line Bug#1008549: fixed in gnome-shell-extension-hamster 
0.10.0+git20210628-3
has caused the Debian Bug report #1008549,
regarding gnome-shell-extension-hamster: does not declare compatibility with 
GNOME Shell 42
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.)


-- 
1008549: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008549
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell-extension-hamster
Version: 0.10.0+git20210628-2
Severity: normal
Tags: bookworm sid upstream
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-42
Forwarded: https://github.com/projecthamster/hamster-shell-extension/pull/349

The metadata.json for this extension doesn't declare compatibility with
GNOME 42. According to the upstream pull request, no actual code changes
are necessary (but I haven't tested it).

gnome-shell 42 is in experimental and will be entering unstable soon,
at which point this will become a RC bug.

During the GNOME Shell 42 transition, this extension will be removed from
testing if it continues to be incompatible.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: gnome-shell-extension-hamster
Source-Version: 0.10.0+git20210628-3
Done: Raphaël Hertzog 

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

Debian distribution maintenance software
pp.
Raphaël Hertzog  (supplier of updated 
gnome-shell-extension-hamster 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, 31 Mar 2022 22:49:01 +0200
Source: gnome-shell-extension-hamster
Architecture: source
Version: 0.10.0+git20210628-3
Distribution: unstable
Urgency: medium
Maintainer: Project Hamster Team 
Changed-By: Raphaël Hertzog 
Closes: 1008549
Changes:
 gnome-shell-extension-hamster (0.10.0+git20210628-3) unstable; urgency=medium
 .
   * Document compatibility with GNOME 42 (Closes: #1008549)
Checksums-Sha1:
 83c4abab2d36c050ddceafa5d5d804b316ccd58c 2022 
gnome-shell-extension-hamster_0.10.0+git20210628-3.dsc
 44c68db9367d54dbfc9216c4985fd1205204485c 2496 
gnome-shell-extension-hamster_0.10.0+git20210628-3.debian.tar.xz
 c6f4a0bae45fd91a98f639c88ab51e8cb9ddd46e 8003 
gnome-shell-extension-hamster_0.10.0+git20210628-3_source.buildinfo
Checksums-Sha256:
 e612be9e4bbf068fe4e465a8f19933ee11e2d12e8e2e39f365f6aefa63aaa6ef 2022 
gnome-shell-extension-hamster_0.10.0+git20210628-3.dsc
 0c9846a6127020d05ee1c87117c51a23fc1c7ab021331decf4ce20e1d94552eb 2496 
gnome-shell-extension-hamster_0.10.0+git20210628-3.debian.tar.xz
 d6db6e045c828a0762c3ecdd5d167593bcb9a46c0093e7ea3c5dffde0f6100d1 8003 
gnome-shell-extension-hamster_0.10.0+git20210628-3_source.buildinfo
Files:
 c1d7c8a980a5bb2a6abfbf061842259c 2022 gnome optional 
gnome-shell-extension-hamster_0.10.0+git20210628-3.dsc
 394dd9296b012328ddb56fcd1f81793f 2496 gnome optional 
gnome-shell-extension-hamster_0.10.0+git20210628-3.debian.tar.xz
 1f177dc18c9908945ebf1376caf62ed0 8003 gnome optional 
gnome-shell-extension-hamster_0.10.0+git20210628-3_source.buildinfo

-BEGIN PGP SIGNATURE-
Comment: Signed by Raphael Hertzog

iQEzBAEBCgAdFiEE1823g1EQnhJ1LsbSA4gdq+vCmrkFAmJGFIMACgkQA4gdq+vC
mrnqJQgAocfwOIEnvLsSfjmHrjStQKDXjvqhhy+2EwKpBsizCfRxI3iMKnezDGwY
thzDidBozBIL/zhgbQQlbCAFdoiYV+xX99jqtsudUmaC4xpqGT1v4avuOAAeQcd2
H9Uu4r/nYswxsOvwzxRSxtNyweUwdykzxWpTfngeY52Tlmypdetb4asJWQY/Z2/E
USBVV8F+bVr42wIhO0WDVZz5ELVIqEoqIV3OJLXkLQtT7/6ZMvqGD/a/bzZZToyN
3OJFZ5fWOUZktEeFYrStw1RUF033mikHYurocVa9oBZ0HdUFxdMYLTDQY2Rly2vs
3+gQQHyk9mAcxasfH+eLhMOi7GviVA==
=ZjbH
-END PGP SIGNATURE End Message ---

Processed: Bug#1008549 marked as pending in gnome-shell-extension-hamster

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1008549 [gnome-shell-extension-hamster] gnome-shell-extension-hamster: 
does not declare compatibility with GNOME Shell 42
Added tag(s) pending.

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

Bug#1008549: marked as pending in gnome-shell-extension-hamster

[Raphaël Hertzog]

Control: tag -1 pending

Hello,

Bug #1008549 in gnome-shell-extension-hamster 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/projecthamster-team/gnome-shell-extension-hamster/-/commit/f9fcca21d26a9dcacb341dc2f3abcab2e39aab8f


Document compatibility with GNOME 42

Closes: #1008549


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1008549

Bug#1005423: marked as pending in ruby-sshkit

[Samuel Henrique]

Control: tag -1 pending

Hello,

Bug #1005423 in ruby-sshkit 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-sshkit/-/commit/271fa71bf7edd4865f1c9feb89bfc8c859937604


d/p/005_fix_set_import.patch: New patch to fix missing import of 'set' from 
deprecation_logger (closes: #1005423)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1005423

Processed: Bug#1005423 marked as pending in ruby-sshkit

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1005423 [src:ruby-sshkit] ruby-sshkit: FTBFS: ERROR: Test "ruby2.7" 
failed: /<>/test/unit/runners/test_parallel.rb:9:in `block in 
test_wraps_ruby_standard_error_in_execute_error': oh no! (RuntimeError)
Added tag(s) pending.

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

Processed: optlang issue affects python-cobra

[Debian Bug Tracking System]

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

> affects 1008755 + src:python-cobra
Bug #1008755 [src:optlang] optlang/interface.py unusable with python3.10
Added indication that 1008755 affects src:python-cobra
> thank you
Stopping processing here.

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

Processed: apt: autopkgtest needs update for new version of dpkg: Testcase test-apt-tagfile-fields-order failed

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:dpkg
Bug #1008759 [src:apt] apt: autopkgtest needs update for new version of dpkg: 
Testcase test-apt-tagfile-fields-order failed
Added indication that 1008759 affects src:dpkg

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

Bug#1008759: apt: autopkgtest needs update for new version of dpkg: Testcase test-apt-tagfile-fields-order failed

[Paul Gevers]

Source: apt
Version: 2.4.3
Severity: serious
X-Debbugs-CC: d...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:dpkg

Dear maintainer(s),

With a recent upload of dpkg the autopkgtest of apt fails in testing 
when that autopkgtest is run with the binary packages of dpkg from 
unstable. It passes when run with only packages from testing. In tabular 
form:


   passfail
dpkg   from testing1.21.6
aptfrom testing2.4.3
all others from testingfrom testing

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

Currently this regression is blocking the migration of dpkg to testing 
[1]. Of course, dpkg shouldn't just break your autopkgtest (or even 
worse, your package), but it seems to me that the change in dpkg was 
intended and your package needs to update to the new situation.


If this is a real problem in your package (and not only in your 
autopkgtest), the right binary package(s) from dpkg should really add a 
versioned Breaks on the unfixed version of (one of your) package(s). 
Note: the Breaks is nice even if the issue is only in the autopkgtest as 
it helps the migration software to figure out the right versions to 
combine in the tests.


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

Paul

[1] https://qa.debian.org/excuses.php?package=dpkg

https://ci.debian.net/data/autopkgtest/testing/amd64/a/apt/20465752/log.gz

(68/287) Testcase test-apt-tagfile-fields-order: -Class
-Conffiles
-Config-Version
-MSDOS-Filename
-Optional
-Original-Maintainer
-Package-Revision
-Package_Revision
-Recommended
-Revision
-SHA512
-Status
+Static-Built-Using
-Triggers-Awaited
-Triggers-Pending
FAIL
Check that apt knows all fields dpkg orders in Packages … FAIL
-Class
-Filename
-MD5sum
-MSDOS-Filename
-Optional
-Original-Maintainer
-Package-Revision
-Package_Revision
-Recommended
-Revision
-SHA1
-SHA256
-SHA512
-Size
+Static-Built-Using
Check that apt knows all fields dpkg orders in status … -Class
-Conffiles
-Config-Version
-Filename
-MD5sum
-MSDOS-Filename
-Optional
-Original-Maintainer
-Package-Revision
-Package_Revision
-Recommended
-Revision
-SHA1
-SHA256
-SHA512
-Size
-Status
+Static-Built-Using
-Triggers-Awaited
-Triggers-Pending
Check that apt knows all fields dpkg orders in DEBIAN/control … FAIL
 P P
Running test-apt-tagfile-fields-order -> FAILED


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1008757: python-a38: autopkgtest regression: writing YAML requires ruamel.yaml or PyYAML to be installed

[Paul Gevers]

Source: python-a38
Version: 0.1.4-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent upload of python-a38 the autopkgtest of python-a38 fails 
in testing when that autopkgtest is run with the binary packages of 
python-a38 from unstable. It passes when run with only packages from 
testing. In tabular form:


   passfail
python-a38 from testing0.1.4-1
all others from testingfrom testing

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

Currently this regression is blocking the migration to testing [1]. Can 
you please investigate the situation and fix it?


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

Paul

[1] https://qa.debian.org/excuses.php?package=python-a38

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

.s..EEs
==
ERROR: test_parse_dati_trasporto (test_fattura.TestSamples)
--
Traceback (most recent call last):
  File 
"/tmp/autopkgtest-lxc.43ld4p_7/downtmp/build.YeB/src/tests/test_fattura.py", 
line 285, in test_parse_dati_trasporto

self.assertCodecsCanCope(f)
  File 
"/tmp/autopkgtest-lxc.43ld4p_7/downtmp/build.YeB/src/tests/test_fattura.py", 
line 277, in assertCodecsCanCope

cod.save(f, tf.name)
  File 
"/tmp/autopkgtest-lxc.43ld4p_7/downtmp/build.YeB/src/a38/codec.py", line 
83, in save

self.write_file(f, fd)
  File 
"/tmp/autopkgtest-lxc.43ld4p_7/downtmp/build.YeB/src/a38/codec.py", line 
135, in write_file

_write_yaml(f.to_jsonable(), file)
  File 
"/tmp/autopkgtest-lxc.43ld4p_7/downtmp/build.YeB/src/a38/codec.py", line 
56, in _write_yaml
raise NotImplementedError("writing YAML requires ruamel.yaml or 
PyYAML to be installed")
NotImplementedError: writing YAML requires ruamel.yaml or PyYAML to be 
installed


==
ERROR: test_parse_unicode (test_fattura.TestSamples)
--
Traceback (most recent call last):
  File 
"/tmp/autopkgtest-lxc.43ld4p_7/downtmp/build.YeB/src/tests/test_fattura.py", 
line 291, in test_parse_unicode

self.assertCodecsCanCope(f)
  File 
"/tmp/autopkgtest-lxc.43ld4p_7/downtmp/build.YeB/src/tests/test_fattura.py", 
line 277, in assertCodecsCanCope

cod.save(f, tf.name)
  File 
"/tmp/autopkgtest-lxc.43ld4p_7/downtmp/build.YeB/src/a38/codec.py", line 
83, in save

self.write_file(f, fd)
  File 
"/tmp/autopkgtest-lxc.43ld4p_7/downtmp/build.YeB/src/a38/codec.py", line 
135, in write_file

_write_yaml(f.to_jsonable(), file)
  File 
"/tmp/autopkgtest-lxc.43ld4p_7/downtmp/build.YeB/src/a38/codec.py", line 
56, in _write_yaml
raise NotImplementedError("writing YAML requires ruamel.yaml or 
PyYAML to be installed")
NotImplementedError: writing YAML requires ruamel.yaml or PyYAML to be 
installed


--
Ran 147 tests in 0.655s

FAILED (errors=2, skipped=6)
autopkgtest [22:12:15]: test unittest



OpenPGP_signature
Description: OpenPGP digital signature

Processed: node-npmrc: autopkgtest needs update for new version of nodejs: require(...).tmpDir is not a function

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:nodejs
Bug #1008756 [src:node-npmrc] node-npmrc: autopkgtest needs update for new 
version of nodejs: require(...).tmpDir is not a function
Added indication that 1008756 affects src:nodejs

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

Bug#1008756: node-npmrc: autopkgtest needs update for new version of nodejs: require(...).tmpDir is not a function

[Paul Gevers]

Source: node-npmrc
Version: 1.1.1-2
Severity: serious
X-Debbugs-CC: nod...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:nodejs

Dear maintainer(s),

With a recent upload of nodejs in the nodejs transition the autopkgtest 
of node-npmrc fails in testing when that autopkgtest is run with the 
binary packages of nodejs from unstable. It passes when run with only 
packages from testing. In tabular form:


   passfail
nodejs from testing16.13.2+really14.19.1~dfsg-6
node-npmrc from testing1.1.1-2
all others from testingfrom testing

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

Currently this regression is blocking the migration of nodejs to testing 
[1]. Of course, nodejs shouldn't just break your autopkgtest (or even 
worse, your package), but your package needs to update to the new 
situation or, if this is really an issue with nodejs, reassigned to nodejs.


If this is a real problem in your package (and not only in your 
autopkgtest), the right binary package(s) from nodejs should really add 
a versioned Breaks on the unfixed version of (one of your) package(s). 
Note: the Breaks is nice even if the issue is only in the autopkgtest as 
it helps the migration software to figure out the right versions to 
combine in the tests.


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

Paul

[1] https://qa.debian.org/excuses.php?package=nodejs

https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-npmrc/20473807/log.gz

# Using ./package.(json|yaml)
# Node module name is npmrc
# Build files found: # Test files found: test.js
# Files/dir to be installed from source: test.js # Copy test files
# Copy debian/tests/pkg-js content
'debian/tests/pkg-js' -> 
'/tmp/autopkgtest-lxc.e2nvfpsn/downtmp/autopkgtest_tmp/smokeQF9eaf/debian/tests/pkg-js'
'debian/tests/pkg-js/test' -> 
'/tmp/autopkgtest-lxc.e2nvfpsn/downtmp/autopkgtest_tmp/smokeQF9eaf/debian/tests/pkg-js/test'

# Searching module in /usr/lib/nodejs/npmrc
# Searching module in /usr/lib/*/nodejs/npmrc
# Searching module in /usr/share/nodejs/npmrc
# Found /usr/share/nodejs/npmrc
# Searching files to link in /usr/share/nodejs/npmrc
'./npmrc.1' -> '/usr/share/nodejs/npmrc/npmrc.1'
'./npmrc.js' -> '/usr/share/nodejs/npmrc/npmrc.js'
'./package.json' -> '/usr/share/nodejs/npmrc/package.json'
# Launch debian/tests/pkg-js/test with sh -ex
+ export HOME=/tmp
+ tape test.js
/tmp/autopkgtest-lxc.e2nvfpsn/downtmp/autopkgtest_tmp/smokeQF9eaf/test.js:7
, tmpdir  = require('os').tmpDir()
  ^

TypeError: require(...).tmpDir is not a function
at Object. 
(/tmp/autopkgtest-lxc.e2nvfpsn/downtmp/autopkgtest_tmp/smokeQF9eaf/test.js:7:31)

at Module._compile (internal/modules/cjs/loader.js:1085:14)
at Object.Module._extensions..js 
(internal/modules/cjs/loader.js:1114:10)

at Module.load (internal/modules/cjs/loader.js:950:32)
at Function.Module._load (internal/modules/cjs/loader.js:790:12)
at Module.require (internal/modules/cjs/loader.js:974:19)
at require (internal/modules/cjs/helpers.js:101:18)
at importOrRequire 
(/usr/share/nodejs/tape/bin/import-or-require.js:14:5)

at /usr/share/nodejs/tape/bin/tape:90:14
at Array.reduce ()
autopkgtest [08:10:19]: test pkg-js-autopkgtest



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1008345: marked as done (deepin-album: FTBFS: albumview.h:263:5: error: ‘DComboBox’ does not name a type; did you mean ‘QComboBox’?)

[Debian Bug Tracking System]

Your message dated Thu, 31 Mar 2022 19:33:48 +
with message-id 
and subject line Bug#1008345: fixed in deepin-album 5.9.1+dfsg-1
has caused the Debian Bug report #1008345,
regarding deepin-album: FTBFS: albumview.h:263:5: error: ‘DComboBox’ does not 
name a type; did you mean ‘QComboBox’?
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.)


-- 
1008345: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008345
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: deepin-album
Version: 5.9.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220326 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++ 
> -DENABLE_ACCESSIBILITY=1 -DLITE_DIV -DQT_CONCURRENT_LIB -DQT_CORE_LIB 
> -DQT_DBUS_LIB -DQT_GUI_LIB -DQT_NO_DEBUG -DQT_PRINTSUPPORT_LIB -DQT_SQL_LIB 
> -DQT_SVG_LIB -DQT_WIDGETS_LIB -I/<>/obj-x86_64-linux-gnu/src 
> -I/<>/src 
> -I/<>/obj-x86_64-linux-gnu/src/deepin-album_autogen/include 
> -I/<>/obj-x86_64-linux-gnu -I/<> 
> -I/<>/src/album -I/<>/src/album/albumview 
> -I/<>/src/album/allpicview 
> -I/<>/src/album/controller 
> -I/<>/src/album/dbmanager -I/<>/src/album/dialogs 
> -I/<>/src/album/frame -I/<>/src/album/imageengine 
> -I/<>/src/album/importtimelineview 
> -I/<>/src/album/importview -I/<>/src/album/module 
> -I/<>/src/album/module/slideshow 
> -I/<>/src/album/module/view 
> -I/<>/src/album/module/view/scen 
> -I/<>/src/album/module/view/contents 
> -I/<>/src/album/searchview 
> -I/<>/src/album/thumbnail 
> -I/<>/src/album/timelineview -I/<>/src/album/utils 
> -I/<>/src/album/widgets 
> -I/<>/src/album/widgets/dialogs -I/usr/include/gio-qt 
> -I/usr/include/udisks2-qt5 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
> -I/usr/include/libdtk-5.5.20/DWidget -I/usr/include/libdtk-5.5.20/DGui 
> -I/usr/include/libdtk-5.5.23/DCore -I/usr/include/glibmm-2.4 
> -I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include -I/usr/include/sigc++-2.0 
> -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem 
> /usr/include/x86_64-linux-gnu/qt5 -isystem 
> /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtDBus -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtSql -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtPrintSupport -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtSvg -isystem 
> /usr/include/x86_64-linux-gnu/qt5/QtConcurrent -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -O3 -Wl,-O1 
> -Wl,--as-needed -Wl,-E -fPIE -ffunction-sections -fdata-sections 
> -Wl,--gc-sections -O3 -DNDEBUG -fPIC -std=gnu++14 -MD -MT 
> src/CMakeFiles/deepin-album.dir/album/albumview/leftlistview.cpp.o -MF 
> CMakeFiles/deepin-album.dir/album/albumview/leftlistview.cpp.o.d -o 
> CMakeFiles/deepin-album.dir/album/albumview/leftlistview.cpp.o -c 
> /<>/src/album/albumview/leftlistview.cpp
> /<>/src/album/albumview/leftlistview.cpp: In member function 
> ‘void LeftListView::initConnections()’:
> /<>/src/album/albumview/leftlistview.cpp:78:33: warning: 
> ‘DApplicationHelper’ is deprecated: Use DPaletteHelper 
> [-Wdeprecated-declarations]
>78 | connect(DApplicationHelper::instance(), 
> &DApplicationHelper::themeTypeChanged, this, 
> &LeftListView::onApplicationHelperThemeTypeChanged);
>   | ^~~~
> In file included from /usr/include/libdtk-5.5.20/DWidget/DApplicationHelper:1,
>  from 
> /<>/src/album/widgets/albumlefttabitem.h:27,
>  from 
> /<>/src/album/albumview/leftlistview.cpp:22:
> /usr/include/libdtk-5.5.20/DWidget/dapplicationhelper.h:31:49: note: declared 
> here
>31 | class D_DECL_DEPRECATED_X("Use DPaletteHelper") DApplicationHelper : 
> public DGuiApplicationHelper
>   | ^~
> /<>/src/album/albumview/leftlistview.cpp:78:66: warning: 
> ‘DApplicationHelper’ is deprecated: Use DPaletteHelper 
> [-Wdeprecated-declarations]
>78 | connect(DApplicationHelper::instance(), 
> &DApplicationHelper::themeTypeChanged, this, 
> &LeftListView::onApplicationHelperThemeTypeChanged);
>   |  
> ^~~~
> In file in

Bug#1008754: r-cran-loo: autopkgtest regression on arm64, armhf and i386: missing value where TRUE/FALSE needed

[Paul Gevers]

Source: r-cran-loo
Version: 2.5.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent upload of r-cran-loo the autopkgtest of r-cran-loo fails 
in testing when that autopkgtest is run with the binary packages of 
r-cran-loo from unstable. It passes when run with only packages from 
testing. In tabular form:


   passfail
r-cran-loo from testing2.5.0-1
all others from testingfrom testing

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

Currently this regression is blocking the migration to testing [1]. Can 
you please investigate the situation and fix it?


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

Paul

[1] https://qa.debian.org/excuses.php?package=r-cran-loo

https://ci.debian.net/data/autopkgtest/testing/arm64/r/r-cran-loo/20473561/log.gz

BEGIN TEST testthat.R

R version 4.1.3 (2022-03-10) -- "One Push-Up"
Copyright (C) 2022 The R Foundation for Statistical Computing
Platform: aarch64-unknown-linux-gnu (64-bit)

R is free software and comes with ABSOLUTELY NO WARRANTY.
You are welcome to redistribute it under certain conditions.
Type 'license()' or 'licence()' for distribution details.

R is a collaborative project with many contributors.
Type 'contributors()' for more information and
'citation()' on how to cite R or R packages in publications.

Type 'demo()' for some demos, 'help()' for on-line help, or
'help.start()' for an HTML browser interface to help.
Type 'q()' to quit R.


library(loo)

This is loo version 2.5.0
- Online documentation and vignettes at mc-stan.org/loo
- As of v2.0.0 loo defaults to 1 core but we recommend using as many as 
possible. Use the 'cores' argument or set options(mc.cores = NUM_CORES) 
for an entire session. > library(testthat)


Attaching package: 'testthat'

The following object is masked from 'package:loo':

compare


Sys.setenv("R_TESTS" = "")
test_check("loo")

[ FAIL 2 | WARN 0 | SKIP 5 | PASS 860 ]

== Skipped tests 
===

* On CRAN (5)

== Failed tests 

-- Error (test_loo_moment_matching.R:291:3): loo_moment_match_split 
works --

Error in `if (any(k > too_high)) {
.warn("Some Pareto k diagnostic values are too high. ", .k_help())
} else if (any(k > high)) {
.warn("Some Pareto k diagnostic values are slightly high. ", 
  .k_help())

}`: missing value where TRUE/FALSE needed
Backtrace:
x
 1. \-loo:::loo_moment_match_split(...) at test_loo_moment_matching.R:291:2
 2.   +-base::suppressWarnings(...)
 3.   | \-base::withCallingHandlers(...)
 4.   \-loo:::importance_sampling.default(...)
 5. \-loo:::importance_sampling.matrix(...)
 6.   \-loo:::do_importance_sampling(...)
 7. \-loo:::throw_pareto_warnings(pareto_k)
-- Failure (test_psis.R:141:3): psis_smooth_tail returns original tail 
values if k is infinite --

val$k not equal to Inf.
1/1 mismatches
[1] NA - Inf == NA

[ FAIL 2 | WARN 0 | SKIP 5 | PASS 860 ]
Error: Test failures
Execution halted
autopkgtest [15:13:29]: test run-unit-test



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1008752: avifile: autopkgtest regression on armhf: Bus error

[Paul Gevers]

Source: avifile
Version: 1:0.7.48~20090503.ds-23
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent upload of avifile the autopkgtest of avifile fails in 
testing on armhf when that autopkgtest is run with the binary packages 
of avifile from unstable. It passes when run with only packages from 
testing. In tabular form:


   passfail
avifilefrom testing1:0.7.48~20090503.ds-23
all others from testingfrom testing

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

Currently this regression is blocking the migration to testing [1]. Can 
you please investigate the situation and fix it?


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

Paul

[1] https://qa.debian.org/excuses.php?package=avifile

https://ci.debian.net/data/autopkgtest/testing/armhf/a/avifile/20131436/log.gz

Setting pipeline to PAUSED ...
Pipeline is PREROLLING ...
Redistribute latency...
Pipeline is PREROLLED ...
Setting pipeline to PLAYING ...
Redistribute latency...
New clock: GstSystemClock
Got EOS from element "pipeline0".
Execution ended after 0:00:00.312851570
Setting pipeline to NULL ...
Freeing pipeline ...
Setting pipeline to PAUSED ...
Pipeline is PREROLLING ...
Pipeline is PREROLLED ...
Setting pipeline to PLAYING ...
Redistribute latency...
New clock: GstSystemClock
Got EOS from element "pipeline0".
Execution ended after 0:00:00.217510393
Setting pipeline to NULL ...
Freeing pipeline ...
g++ -Wall -g -o test1 test1.cc \
-laviplay -I/usr/include/avifile-0.7 \
-laubio  \
-lm
 : Avifile RELEASE-0.7.48-220318-20:07-../src/configure
 : Available CPU flags: fp asimd evtstrm aes pmull sha1 sha2 crc32 
atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp ssbs

This binary was compiled for Avifile ver. 1840, the library is ver. 1840
 : Checking: ./test_raw.avi
 : MainHeader: MicroSecPerFrame=4 MaxBytesPerSec=6112800
 PaddingGranularity=0 Flags=[ HAS_INDEX IS_INTERLEAVED ] TotalFrames=250
 InitialFrames=0 Streams=2 SuggestedBufferSize=0 WxH=320x240
 Scale=0 Rate=0 Start=0 Length=0
 : StreamHeader: Type=vids Handler=DIVX Flags=[ ]
 InitialFrames=0 Scale=1 Rate=25 Start=0 Length=250
 SuggestedBufferSize=12413 Quality=0 SampleSize=0 Rect l,r,t,b=0,0,0,0
 : StreamHeader: Type=auds Handler=0x1 Flags=[ ]
 InitialFrames=0 Scale=1 Rate=44100 Start=0 Length=450559
 SuggestedBufferSize=8192 Quality=0 SampleSize=8 Rect l,r,t,b=0,0,0,0
 : Reading index from offset: 5581514
 : Stream 0 vids : DIVX (0x4944) 250 chunks (0.98KB)
 : WARNING: stream header has incorrect dwLength (450559 -> 
450560)

 : Stream 1 auds : Microsoft PCM (0x1) 440 chunks (3.44KB)
 : Initialized video stream (chunk tblsz: 250, fmtsz: 40)
 : Found 7 plugins 
(/usr/lib/arm-linux-gnueabihf/avifile-0.7,A:28,V:36)

 : creating dir: /home/debci/.avm
 : looking for mpeg4  1482049860
 : Created video decoder: FF OpenDivX
 : Initialized audio stream (chunk tblsz: 450560, fmtsz: 18)
 : PCM audio decoder created
bh.biHeight = -240, bh.biWidth = 320
bh.biHeight < 0, correct the value to 240
Movie size: 320 x 240  [YV12]
audio format: 1, Channels: 2, Samples/sec: 44100, Bits/Sample: 32, 
Bytes/sec: 352800

Video Length: 250
Video Pos: 0
Audio Length: 450560
Audio Pos: 0
Decoder YUV capabilities: 0x8080
CAPS is CAP_YV12
TIME 0 0
[mpeg4 @ 0x1ad7e40] Requested frame threading with a custom 
get_buffer2() implementation which is not marked as thread safe. This is 
not supported anymore, make your callback thread-safe.

 : using DR1
Audio read 192 samples, 1536 bytes.
Audio frequency 469.27 hz
Audio read 192 samples, 1536 bytes.
Audio frequency 469.188 hz
Audio read 192 samples, 1536 bytes.
Audio frequency 469.095 hz
Audio read 192 samples, 1536 bytes.
Audio frequency 469.086 hz
Audio read 192 samples, 1536 bytes.
Audio frequency 469.17 hz
Audio read 192 samples, 1536 bytes.
Audio frequency 469.262 hz
Audio read 192 samples, 1536 bytes.
Audio frequency 469.267 hz
Audio read 192 samples, 1536 bytes.
Audio frequency 469.18 hz
Audio read 192 samples, 1536 bytes.
Audio frequency 469.091 hz
Audio read 192 samples, 1536 bytes.
Audio frequency 469.09 hz
TIME 0.04 1
Bus error
autopkgtest [10:24:27]: test decoding-test-mp4-raw



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1008751: pytest-mpi: autopkgtest regression: versioned test depends only in experimental

[Paul Gevers]

Source: pytest-mpi
Version: 0.6-2
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

With a recent upload of pytest-mpi the autopkgtest of pytest-mpi fails 
in testing when that autopkgtest is run with the binary packages of 
pytest-mpi from unstable. It passes when run with only packages from 
testing. In tabular form:


   passfail
pytest-mpi from testing0.6-2
versioned deps [0] from testingfrom unstable
all others from testingfrom testing

I copied some of the output at the bottom of this report. I notice that 
the required version is only available in experimental.


Currently this regression is blocking the migration to testing [1]. Can 
you please investigate the situation and fix it?


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

Paul

[1] https://qa.debian.org/excuses.php?package=pytest-mpi

https://ci.debian.net/data/autopkgtest/testing/amd64/p/pytest-mpi/20466039/log.gz


autopkgtest [17:12:04]:  apt-source pytest-mpi
Get:1 http://deb.debian.org/debian unstable/main pytest-mpi 0.6-2 (dsc) 
[2,323 B]
Get:2 http://deb.debian.org/debian unstable/main pytest-mpi 0.6-2 (tar) 
[41.6 kB]
Get:3 http://deb.debian.org/debian unstable/main pytest-mpi 0.6-2 (diff) 
[4,912 B]

gpgv: unknown type of key resource 'trustedkeys.kbx'
gpgv: keyblock resource '/tmp/dpkg-verify-sig.RlS7vbFC/trustedkeys.kbx': 
General error

gpgv: Signature made Thu 17 Mar 2022 01:21:45 AM UTC
gpgv:using RSA key 23C9A93E585819E9126D0A36573EF1E4BD5A01FA
gpgv: Can't check signature: No public key
dpkg-source: warning: cannot verify signature ./pytest-mpi_0.6-2.dsc
autopkgtest [17:12:05]: testing package pytest-mpi version 0.6-2
autopkgtest [17:12:05]: build not needed
autopkgtest [17:12:05]: test command1: preparing testbed
Reading package lists...
Building dependency tree...
Reading state information...
Correcting dependencies...Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) autopkgtest-satdep:amd64 < 0 @iU K Nb Ib >
Broken autopkgtest-satdep:amd64 Depends on python3-sybil:amd64 < none | 
2.0.1-3 @un uH > (>= 3.0.0~)
  Removing autopkgtest-satdep:amd64 because I can't find 
python3-sybil:amd64

Done
 Done


OpenPGP_signature
Description: OpenPGP digital signature

Processed: ltrace: diff for NMU version 0.7.3-6.2

[Debian Bug Tracking System]

Processing control commands:

> tags 965705 + patch
Bug #965705 [src:ltrace] ltrace: Removal of obsolete debhelper compat 5 and 6 
in bookworm
Added tag(s) patch.
> tags 965705 + pending
Bug #965705 [src:ltrace] ltrace: Removal of obsolete debhelper compat 5 and 6 
in bookworm
Added tag(s) pending.

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

Bug#965705: ltrace: diff for NMU version 0.7.3-6.2

[Guilherme Xavier]

Control: tags 965705 + patch
Control: tags 965705 + pending

Dear maintainer,

I've prepared an NMU for ltrace (versioned as 0.7.3-6.2) and
uploaded it to DELAYED/10. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru ltrace-0.7.3/debian/changelog ltrace-0.7.3/debian/changelog
--- ltrace-0.7.3/debian/changelog	2018-08-20 03:09:32.0 -0300
+++ ltrace-0.7.3/debian/changelog	2022-03-30 20:48:13.0 -0300
@@ -1,3 +1,19 @@
+ltrace (0.7.3-6.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Using new DH level format. Consequently:
+  - debian/compat: removed.
+  - debian/control: changed from 'debhelper' to 'debhelper-compat' in
+Build-Depends field and bumped level to 13.
+  - Closes: #965705
+  * Dropped CDBS in favor of the debhelper to allow the build system to use
+DH level greater than 11. Consequently:
+  - debian/control: removed no longer needed cdbs and autotools-dev from
+Build-Depends field.
+  - debian/rules: changed from CDBS to DH.
+
+ -- Guilherme de Paula Xavier Segundo   Wed, 30 Mar 2022 20:48:13 -0300
+
 ltrace (0.7.3-6.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru ltrace-0.7.3/debian/control ltrace-0.7.3/debian/control
--- ltrace-0.7.3/debian/control	2018-08-20 03:09:32.0 -0300
+++ ltrace-0.7.3/debian/control	2022-03-30 20:48:13.0 -0300
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Juan Cespedes 
 Standards-Version: 3.9.8
-Build-Depends: debhelper-compat (= 13), autotools-dev, libiberty-dev, libelf-dev, libselinux1-dev
+Build-Depends: debhelper-compat (= 13), libiberty-dev, libelf-dev, libselinux1-dev
 
 Package: ltrace
 Architecture: alpha amd64 ia64 i386 mips mipsel powerpc powerpcspe ppc64 s390 s390x sparc
diff -Nru ltrace-0.7.3/debian/rules ltrace-0.7.3/debian/rules
--- ltrace-0.7.3/debian/rules	2018-08-20 03:09:32.0 -0300
+++ ltrace-0.7.3/debian/rules	2022-03-30 20:48:13.0 -0300
@@ -2,3 +2,11 @@
 
 %:
 	dh $@
+
+override_dh_auto_configure:
+	dh_auto_configure -- --with-libunwind=no
+
+override_dh_install:
+	dh_install
+	rm -f debian/ltrace/usr/share/doc/ltrace/COPYING
+	rm -f debian/ltrace/usr/share/doc/ltrace/INSTALL

Bug#1008458: marked as done (thrift: FTBFS: dh_auto_test: error: make -j1 check VERBOSE=1 returned exit code 2)

[Debian Bug Tracking System]

Your message dated Thu, 31 Mar 2022 18:00:12 +
with message-id 
and subject line Bug#1008458: fixed in thrift 0.16.0-1
has caused the Debian Bug report #1008458,
regarding thrift: FTBFS: dh_auto_test: error: make -j1 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.)


-- 
1008458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008458
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: thrift
Version: 0.13.0-7
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220326 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[5]: Entering directory '/<>/lib/go/test'
> mkdir -p gopath/src
> grep -v list.*map.*list.*map ../../../test/ThriftTest.thrift | grep -v 
> 'set' > ThriftTest.thrift
> /<>/compiler/cpp/thrift -out gopath/src/ --gen 
> go:thrift_import=thrift -r IncludesTest.thrift
> [WARNING:/<>/lib/go/test/ThriftTest.thrift:27] The 'csharp' 
> target is deprecated. Consider moving to 'netstd' instead.
> [WARNING:/<>/lib/go/test/ThriftTest.thrift:33] The 'netcore' 
> target is deprecated. Consider moving to 'netstd' instead.
> [WARNING:/<>/lib/go/test/ThriftTest.thrift:45] No generator 
> named 'noexist' could be found!
> [WARNING:/<>/lib/go/test/ThriftTest.thrift:47] cpp generator 
> does not accept 'noexist' as sub-namespace!
> [WARNING:/<>/lib/go/test/ThriftTest.thrift:27] The 'csharp' 
> target is deprecated. Consider moving to 'netstd' instead.
> [WARNING:/<>/lib/go/test/ThriftTest.thrift:33] The 'netcore' 
> target is deprecated. Consider moving to 'netstd' instead.
> [WARNING:/<>/lib/go/test/ThriftTest.thrift:45] No generator 
> named 'noexist' could be found!
> [WARNING:/<>/lib/go/test/ThriftTest.thrift:47] cpp generator 
> does not accept 'noexist' as sub-namespace!
> /<>/compiler/cpp/thrift -out gopath/src/ --gen 
> go:thrift_import=thrift BinaryKeyTest.thrift
> /<>/compiler/cpp/thrift -out gopath/src/ --gen 
> go:thrift_import=thrift MultiplexedProtocolTest.thrift
> /<>/compiler/cpp/thrift -out gopath/src/ --gen 
> go:thrift_import=thrift OnewayTest.thrift
> /<>/compiler/cpp/thrift -out gopath/src/ --gen 
> go:thrift_import=thrift OptionalFieldsTest.thrift
> /<>/compiler/cpp/thrift -out gopath/src/ --gen 
> go:thrift_import=thrift RequiredFieldTest.thrift
> /<>/compiler/cpp/thrift -out gopath/src/ --gen 
> go:thrift_import=thrift ServicesTest.thrift
> /<>/compiler/cpp/thrift -out gopath/src/ --gen 
> go:thrift_import=thrift GoTagTest.thrift
> /<>/compiler/cpp/thrift -out gopath/src/ --gen 
> go:thrift_import=thrift TypedefFieldTest.thrift
> /<>/compiler/cpp/thrift -out gopath/src/ --gen 
> go:thrift_import=thrift RefAnnotationFieldsTest.thrift
> /<>/compiler/cpp/thrift -out gopath/src/ --gen 
> go:thrift_import=thrift UnionDefaultValueTest.thrift
> /<>/compiler/cpp/thrift -out gopath/src/ --gen 
> go:thrift_import=thrift UnionBinaryTest.thrift
> /<>/compiler/cpp/thrift -out gopath/src/ --gen 
> go:thrift_import=thrift ErrorTest.thrift
> /<>/compiler/cpp/thrift -out gopath/src/ --gen 
> go:thrift_import=thrift NamesTest.thrift
> /<>/compiler/cpp/thrift -out gopath/src/ --gen 
> go:thrift_import=thrift InitialismsTest.thrift
> /<>/compiler/cpp/thrift -out gopath/src/ --gen 
> go:thrift_import=thrift,read_write_private DontExportRWTest.thrift
> /<>/compiler/cpp/thrift -out gopath/src/ --gen 
> go:thrift_import=thrift,ignore_initialisms IgnoreInitialismsTest.thrift
> /<>/compiler/cpp/thrift -out gopath/src/ --gen 
> go:thrift_import=thrift ConflictNamespaceTestA.thrift
> /<>/compiler/cpp/thrift -out gopath/src/ --gen 
> go:thrift_import=thrift ConflictNamespaceTestB.thrift
> /<>/compiler/cpp/thrift -out gopath/src/ --gen 
> go:thrift_import=thrift ConflictNamespaceTestC.thrift
> /<>/compiler/cpp/thrift -out gopath/src/ --gen 
> go:thrift_import=thrift ConflictNamespaceTestD.thrift
> /<>/compiler/cpp/thrift -out gopath/src/ --gen 
> go:thrift_import=thrift ConflictNamespaceTestSuperThing.thrift
> /<>/compiler/cpp/thrift -out gopath/src/ --gen 
> go:thrift_import=thrift ConflictNamespaceServiceTest.thrift
> echo GOPATH=`pwd`/gopath /usr/bin/go get github.com/golang/mock/gomock || true
> GOPATH=/<>/lib/go/test/gopath /usr/bin/go get 
> github.com/golang/mock/gomock
> echo sed -i 's/\"context\"/\"golang.org\/x\/net\/context\"/g' 
> gopath/src/github.com/golang/mock/gomock/controller.go || true
> sed -i s/\"context\"/\"golang.org\/x\/net\/context\"/g 
> gopath/src/github.com/golang/mock/gomock/controller.go
> e

Bug#1008731: marked as done (python-pcl: FTBFS in unstable and testing)

[Debian Bug Tracking System]

Your message dated Thu, 31 Mar 2022 17:50:15 +
with message-id 
and subject line Bug#1008731: fixed in python-pcl 0.3.0~rc1+dfsg-12
has caused the Debian Bug report #1008731,
regarding python-pcl: FTBFS in unstable and testing
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.)


-- 
1008731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008731
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pcl
Version: 0.3.0~rc1+dfsg-11
Severity: serious
Tags: ftbfs

Hi Maintainer

Since sometime around the end of January, python-pcl started to FTBFS
in unstable and testing [1].  I've copied what I hope is the relevant
part of the log below.

Regards
Graham


[1] https://tests.reproducible-builds.org/debian/rb-pkg/python-pcl.html


building 'pcl.pcl_visualization' extension
x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare
-DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat
-Werror=format-security -g -fwrapv -O2 -g -O2
-ffile-prefix-map=/build/python-pcl-0.3.0~rc1+dfsg=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -fPIC
-I/usr/lib/python3/dist-packages/numpy/core/include
-I/usr/include/pcl-1.12 -I/usr/include/eigen3 -I/usr/include/ni
-I/usr/include/openni2 -I/usr/include/ni -I/usr/include/vtk-9.0
-I/usr/local/include/vtk-8.0 -I/usr/local/Cellar/vtk/8.0.1/include
-I/usr/include/python3.9 -c pcl/pcl_visualization.cpp -o
build/temp.linux-x86_64-3.9/pcl/pcl_visualization.o
-fno-strict-aliasing
In file included from
/usr/include/pcl-1.12/pcl/visualization/point_cloud_handlers.h:41,
 from pcl/pcl_visualization.cpp:721:
/usr/include/pcl-1.12/pcl/visualization/point_cloud_geometry_handlers.h:49:10:
fatal error: vtkSmartPointer.h: No such file or directory
   49 | #include 
  |  ^~~
compilation terminated.
error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1
E: pybuild pybuild:367: build: plugin distutils failed with: exit
code=1: /usr/bin/python3 setup.py build
--- End Message ---
--- Begin Message ---
Source: python-pcl
Source-Version: 0.3.0~rc1+dfsg-12
Done: Jochen Sprickerhof 

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

Debian distribution maintenance software
pp.
Jochen Sprickerhof  (supplier of updated python-pcl 
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, 31 Mar 2022 19:14:33 +0200
Source: python-pcl
Architecture: source
Version: 0.3.0~rc1+dfsg-12
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Jochen Sprickerhof 
Closes: 1008731
Changes:
 python-pcl (0.3.0~rc1+dfsg-12) unstable; urgency=medium
 .
   * Drop python3:Versions
   * Drop python3:Provides
   * Drop duplicate build dependency
   * Update for VTK 9.1 (Closes: #1008731)
   * Commit Debian 3.0 (quilt) metadata
Checksums-Sha1:
 ab3015a8934c82f95db5cca1f91660e22feae948 2323 python-pcl_0.3.0~rc1+dfsg-12.dsc
 4b30609a881cfc62ee3d673d5b7d4dfa8423889c 12620 
python-pcl_0.3.0~rc1+dfsg-12.debian.tar.xz
Checksums-Sha256:
 a36a46954d4c2c494de777b875501229e81f6b632798bd6183b9ab1d6892a27c 2323 
python-pcl_0.3.0~rc1+dfsg-12.dsc
 ef237df276062b3958c12fd45c6dcace7d6213c58f02c426e24056c8b54bdb03 12620 
python-pcl_0.3.0~rc1+dfsg-12.debian.tar.xz
Files:
 8913051d8ae053e8e88e118d89981d10 2323 python optional 
python-pcl_0.3.0~rc1+dfsg-12.dsc
 7e7274d48a6f3b0d9d1e13b904d18c9b 12620 python optional 
python-pcl_0.3.0~rc1+dfsg-12.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAmJF4hIUHGpzcHJpY2tl
QGRlYmlhbi5vcmcACgkQW//cwljmlDOEsg/+Jr4F4V4gUGePe/4qfF6fWlc3a/r5
UZehXOamH81BW7hA+ZmoAd5GV3MfvfW0o1SiF0cvoro8PkzW2fR3KCsWYBJr90xX
RVieYeDkfVh3QV/T9C1JE8+IZj0xDFi+TdwmuQdyFGJHNygvhQmYIOqYkUyaAsx6
wHqZsvmwMJ+77RUVZ5Rr1KNliG8wg44eFHLM9zk009H1eQSYbAj3f3p5EjyMCLta
3Sn2iaPrMIF5Qj+QTEROxAqGDr47EQ/2MWN9rl1Muh0uyyp8Twmu5J2ibhcpLwbH
ebHYSE9iDuee5rw4C/nyeT4wQh2kuX9X4YB/sWBC0DojKXiJQKhmqOJQkXrvlVsK
oUU9EWWQBYOTb2o4Mkz+Ir/X/hukaTFMqrStXYWssnQKMota0yqUa+jYTWDhX2QF

Processed: [bts-link] source package gnome-shell-extension-dash-to-panel

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package 
> gnome-shell-extension-dash-to-panel
> # 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 #1008538 (http://bugs.debian.org/1008538)
> # Bug title: gnome-shell-extension-dash-to-panel: does not declare 
> compatibility with GNOME Shell 42
> #  * https://github.com/home-sweet-gnome/dash-to-panel/pull/1584
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 1008538 + fixed-upstream
Bug #1008538 [gnome-shell-extension-dash-to-panel] 
gnome-shell-extension-dash-to-panel: does not declare compatibility with GNOME 
Shell 42
Added tag(s) fixed-upstream.
> usertags 1008538 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

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

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:shotwell
> # 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 #1008337 (http://bugs.debian.org/1008337)
> # Bug title: shotwell: FTBFS: ../src/Resources.vala:38.34-38.40: error: value 
> is less accessible than constant `Resources.PREFIX'
> #  * https://gitlab.gnome.org/GNOME/shotwell/-/issues/4967
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 1008337 + fixed-upstream
Bug #1008337 [src:shotwell] shotwell: FTBFS: ../src/Resources.vala:38.34-38.40: 
error: value is less accessible than constant `Resources.PREFIX'
Added tag(s) fixed-upstream.
> usertags 1008337 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package gnome-shell-extension-hamster

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package 
> gnome-shell-extension-hamster
> # 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 #1008549 (http://bugs.debian.org/1008549)
> # Bug title: gnome-shell-extension-hamster: does not declare compatibility 
> with GNOME Shell 42
> #  * https://github.com/projecthamster/hamster-shell-extension/pull/349
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 1008549 + fixed-upstream
Bug #1008549 [gnome-shell-extension-hamster] gnome-shell-extension-hamster: 
does not declare compatibility with GNOME Shell 42
Added tag(s) fixed-upstream.
> usertags 1008549 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:octave-symbolic

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:octave-symbolic
> # 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 #980707 (http://bugs.debian.org/980707)
> # Bug title: octave-symbolic: FTBFS against sympy 1.7
> #  * https://github.com/cbm755/octsympy/issues/1035
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 980707 + fixed-upstream
Bug #980707 [src:octave-symbolic] octave-symbolic: FTBFS against sympy 1.7
Bug #982561 [src:octave-symbolic] sympy breaks octave-symbolic autopkgtest: 
_PrintFunction' object has no attribute '__globals__'
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
> usertags 980707 - status-open
Usertags were: status-open.
There are now no usertags set.
> usertags 980707 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> # remote status report for #982561 (http://bugs.debian.org/982561)
> # Bug title: sympy breaks octave-symbolic autopkgtest: _PrintFunction' object 
> has no attribute '__globals__'
> #  * https://github.com/cbm755/octsympy/issues/1035
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 982561 + fixed-upstream
Bug #982561 [src:octave-symbolic] sympy breaks octave-symbolic autopkgtest: 
_PrintFunction' object has no attribute '__globals__'
Bug #980707 [src:octave-symbolic] octave-symbolic: FTBFS against sympy 1.7
Ignoring request to alter tags of bug #982561 to the same tags previously set
Ignoring request to alter tags of bug #980707 to the same tags previously set
> usertags 982561 - status-open
Usertags were: status-open.
There are now no usertags set.
> usertags 982561 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#1008747: mercurial: FTBFS with Python 3.10 as default

[Graham Inggs]

Source: mercurial
Version: 6.1-4
Severity: serious
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.10

Hi Maintainer

As can be seen on reproducible builds [1], mercurial FTBFS with Python
3.10 as the default version.  I've copied what I hope is the relevant
part of the log below.

This appears to be due to the following appearing in the output of some tests:

DeprecationWarning: The distutils package is deprecated and slated for
removal in Python 3.12.

Regards
Graham


[1] https://tests.reproducible-builds.org/debian/rb-pkg/mercurial.html


Failed test-hghave.t: output changed
Failed test-https.t: output changed
Failed test-parseindex.t: output changed
Failed test-patchbomb-tls.t: output changed
Failed test-run-tests.t: output changed
# Ran 885 tests, 80 skipped, 5 failed.

Bug#1008746: mrgingham: FTBFS with Python 3.10 as default

[Graham Inggs]

Source: mrgingham
Version: 1.20-4
Severity: serious
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.10

Hi Maintainer

As can be seen on reproducible builds [1], mrgingham FTBFS with Python
3.10 as the default version.  I've copied what I hope is the relevant
part of the log below.

Regards
Graham


[1] https://tests.reproducible-builds.org/debian/rb-pkg/mrgingham.html


pod2man --center="mrgingham: chessboard corner finder"
--name=MRGINGHAM --release="mrgingham 2.1" --section=1 mrgingham.pod
mrgingham.1
pod2man --center="mrgingham: chessboard corner finder"
--name=MRGINGHAM --release="mrgingham 2.1" --section=1
mrgingham-observe-pixel-uncertainty.pod
mrgingham-observe-pixel-uncertainty.1
pod2man: unable to format mrgingham-observe-pixel-uncertainty.pod
make[2]: *** [Makefile:75: mrgingham-observe-pixel-uncertainty.1] Error 1

Bug#1008745: nipy: FTBFS with Python 3.10 as default

[Graham Inggs]

Source: nipy
Version: 0.5.0-2
Severity: serious
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.10

Hi Maintainer

As can be seen on reproducible builds [1], nipy FTBFS with Python 3.10
as the default version.  I've copied what I hope is the relevant part
of the log below.

Regards
Graham


[1] https://tests.reproducible-builds.org/debian/rb-pkg/nipy.html


: # I: Generate documentation
PYTHONPATH=`pybuild --print build_dir --interpreter python3.10` \
  http_proxy='127.0.0.1:9' \
  PATH=/build/1st/nipy-0.5.0/debian/tmp/usr/bin/:$PATH \
  HOME=/build/1st/nipy-0.5.0/build \
  /usr/bin/make -C doc html PYTHON=python3.10
E: pybuild pybuild:143: interpreter python3.10 not supported by
BuildSystem(distutils)
make[2]: Entering directory '/build/1st/nipy-0.5.0/doc'
python3.10 ../tools/build_modref_templates.py
Traceback (most recent call last):
  File "/build/1st/nipy-0.5.0/doc/../tools/build_modref_templates.py",
line 18, in 
docwriter = ApiDocWriter(package)
  File "/build/1st/nipy-0.5.0/tools/apigen.py", line 73, in __init__
self.package_name = package_name
  File "/build/1st/nipy-0.5.0/tools/apigen.py", line 95, in set_package_name
self.root_module = __import__(package_name)
ModuleNotFoundError: No module named 'nipy'
make[2]: *** [Makefile:62: api] Error 1

Bug#1008743: marked as done (libgnome-bluetooth-ui-3.0-dev needs Breaks+Replaces: libgnome-bluetooth-3.0-dev (<< 42.0-2~))

[Debian Bug Tracking System]

Your message dated Thu, 31 Mar 2022 17:03:52 +
with message-id 
and subject line Bug#1008743: fixed in gnome-bluetooth3 42.0-3
has caused the Debian Bug report #1008743,
regarding libgnome-bluetooth-ui-3.0-dev needs Breaks+Replaces: 
libgnome-bluetooth-3.0-dev (<< 42.0-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.)


-- 
1008743: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008743
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgnome-bluetooth-ui-3.0-dev
Version: 42.0-2
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=gnome-control-center&arch=arm64&ver=1%3A42.0-1&stamp=1648675887&raw=0

...
Unpacking libgnome-bluetooth-ui-3.0-dev:arm64 (42.0-2) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-pqRtAr/465-libgnome-bluetooth-ui-3.0-dev_42.0-2_arm64.deb 
(--unpack):
 trying to overwrite 
'/usr/include/gnome-bluetooth-3.0/bluetooth-settings-widget.h', which is also 
in package libgnome-bluetooth-3.0-dev:arm64 42.0-1
...
--- End Message ---
--- Begin Message ---
Source: gnome-bluetooth3
Source-Version: 42.0-3
Done: Jeremy Bicha 

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

Debian distribution maintenance software
pp.
Jeremy Bicha  (supplier of updated gnome-bluetooth3 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, 31 Mar 2022 12:47:38 -0400
Source: gnome-bluetooth3
Built-For-Profiles: noudeb
Architecture: source
Version: 42.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bicha 
Closes: 1008743
Changes:
 gnome-bluetooth3 (42.0-3) unstable; urgency=medium
 .
   * Fix typo in Breaks/Replaces (Closes: #1008743)
Checksums-Sha1:
 84936bca15962d3a2171fa0ee39d1fb4d1e5709b 3130 gnome-bluetooth3_42.0-3.dsc
 331216b389caaa9fa92c0c6b23c903be4a08276b 11888 
gnome-bluetooth3_42.0-3.debian.tar.xz
 6b93c15d0fb4fa6cc1062c3459c41ebb14d0f189 17928 
gnome-bluetooth3_42.0-3_source.buildinfo
Checksums-Sha256:
 99787798e292da72348515c445c9b6737a67f490b4e6a544ddbea151b9bb13c2 3130 
gnome-bluetooth3_42.0-3.dsc
 15780806855531808c600185a0b423e341a54bcb936177a10476ff14e47ec1c9 11888 
gnome-bluetooth3_42.0-3.debian.tar.xz
 63c1b903094d22a2ef76dd9feb36bc56b8d38ef8c975f639f70c9c7830405895 17928 
gnome-bluetooth3_42.0-3_source.buildinfo
Files:
 e5fb5667697cb400e911629251fbc250 3130 gnome optional 
gnome-bluetooth3_42.0-3.dsc
 f5eff10bd7f4ef7011bb16cfa92e578d 11888 gnome optional 
gnome-bluetooth3_42.0-3.debian.tar.xz
 0036c25ce248ee4f934379a1ec0bbc69 17928 gnome optional 
gnome-bluetooth3_42.0-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmJF20QACgkQ5mx3Wuv+
bH1l5g//Y6l6iMP5qRSauq1YZLCOXGM2TZsiQhAXQTx9lrTG9j7+UMgQg/pdhQwt
esNl98bKKoiRb588131YvIGvPkLj1m923I3RODUGTcXNg/i8Zi+/VepsD37X84Kt
3OfTWT7g5TbxE8Bk9HKjQLpJvKbhmDBgDWueIKVk6l+T+iqdjR/nY6DgAeWDe+xg
R+JAkeEi7QW23iz4+SACdyGijrsMGih8GSFZsXtdxf/Y3FKpL/7dSNjd6DX7ng1C
VwkFeD8j/vYRPi3GgJt/ODDExa02XLcv+WQUFDfTx4U9NgF+wvEzbGHrG7IfeF33
DFjDEpdSz/5jg0Em9GRUVz3OYRUegagCFvuc9sDMeeTba4XKzO4nIPdbjd+WBZZe
G8NhhS4qvk3EJlpkIMzT2Ghw16wrrIJvXPveZYQueAfo/oCDLKMRtd0boAPJS7hL
YLb7aDp82OSdpGsOpf/KWHsrZEJ+uc4ek+kgUArzDM+GO9BOiW2tH2unlNrw0z+y
mKPHlIk65m6RYrtjKbjxGO12XgS8fUb6dhlw0Nv+Zpe5ht37StulKXaOZjPz3itd
KB5QP+1cSw5nE1s/MI1FnkuWvofGWRJcUOSU8RekuiLIBWNMu34Pl5KGCq3ybUYI
uMIrenZU7P6zG8L2rPKSnBuDUKp6QNaHYvl4MAo97utay8UW6wc=
=wljv
-END PGP SIGNATURE End Message ---

Bug#1008722: Possible bugfix

[Moessbauer, Felix]

Hi,

I debugged this further and found that the problem is a partially-written 
tracefs-sqlhist.o file.
With the patch in [1] I can no longer reproduce the bug.

Still, I don't fully understand why it is required to explicitly mention the 
dependency to tracefs-sqlhist.c.

[1] 
https://salsa.debian.org/fmoessbauer/libtracefs/-/commit/1312d11f371bda6ff88bac518a5347a8cf8a9105

Felix
--
Siemens AG, Technology, T CED SES-DE
Otto-Hahn-Ring 6, 81739 München, Germany

Processed: tagging 1005642

[Debian Bug Tracking System]

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

> tags 1005642 + pending
Bug #1005642 [samba] possible gross file corruption due to windows client cache 
poisoning
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: tagging 1004690, tagging 1004691, tagging 1004692

[Debian Bug Tracking System]

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

> tags 1004690 + pending
Bug #1004690 [src:samba] samba: CVE-2021-20316
Added tag(s) pending.
> tags 1004691 + pending
Bug #1004691 [src:samba] samba: CVE-2021-43566
Added tag(s) pending.
> tags 1004692 + pending
Bug #1004692 [src:samba] samba: CVE-2021-44141
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1008743: libgnome-bluetooth-ui-3.0-dev needs Breaks+Replaces: libgnome-bluetooth-3.0-dev (<< 42.0-2~)

[Adrian Bunk]

Package: libgnome-bluetooth-ui-3.0-dev
Version: 42.0-2
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=gnome-control-center&arch=arm64&ver=1%3A42.0-1&stamp=1648675887&raw=0

...
Unpacking libgnome-bluetooth-ui-3.0-dev:arm64 (42.0-2) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-pqRtAr/465-libgnome-bluetooth-ui-3.0-dev_42.0-2_arm64.deb 
(--unpack):
 trying to overwrite 
'/usr/include/gnome-bluetooth-3.0/bluetooth-settings-widget.h', which is also 
in package libgnome-bluetooth-3.0-dev:arm64 42.0-1
...

Bug#1008739: python-pyaudio: FTBFS with Python 3.10 as default

[Graham Inggs]

Source: python-pyaudio
Version: 0.2.11-1.3
Severity: serious
Tags: ftbfs patch bookworm sid
User: debian-pyt...@lists.debian.org
Usertags: python3.10

Hi Maintainer

As can be seen on reproducible builds [1], python-pyaudio FTBFS with
Python 3.10 as the default version.  I've copied what I hope is the
relevant part of the log below.

I've also attached a patch that works for me.

Regards
Graham


[1] https://tests.reproducible-builds.org/debian/rb-pkg/python-pyaudio.html


x86_64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions
-g -fwrapv -O2 -Wl,-z,relro -Wl,-z,now -g -O2
-ffile-prefix-map=/build/1st/python-pyaudio-0.2.11=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2
build/temp.linux-x86_64-3.10/src/_portaudiomodule.o -lportaudio -o
build/lib.linux-x86_64-3.10/_portaudio.cpython-310-x86_64-linux-gnu.so
touch build/lib.linux-x86_64-3.1/build
touch: cannot touch 'build/lib.linux-x86_64-3.1/build': No such file
or directory
make[2]: *** [Makefile:39: build/lib.linux-x86_64-3.1/build] Error 1
Description: Adjust Makefile for Python 3.10
 import get_platform() from sysconfig instead of distutils
 support Python with 2-digit minor version
Author: Graham Inggs 
Last-Update: 2022-03-31

--- a/Makefile
+++ b/Makefile
@@ -7,7 +7,7 @@
 BUILD_ARGS ?=
 SPHINX ?= sphinx-build
 DOCS_OUTPUT=docs/
-PYTHON_BUILD_DIR:=$(shell $(PYTHON) -c "import distutils.util; import sys; print(distutils.util.get_platform() + '-' + sys.version[0:3])")
+PYTHON_BUILD_DIR:=$(shell $(PYTHON) -c "import sysconfig; import sys; print(sysconfig.get_platform() + '-' + ('%d.%d' % sys.version_info[:2]))")
 BUILD_DIR:=lib.$(PYTHON_BUILD_DIR)
 BUILD_STAMP:=$(BUILD_DIR)/build
 SRCFILES := src/*.c src/*.h src/*.py

Bug#985725: marked as done (slurm-wlm: flaky autopkgtest: srun: Required node not available (down, drained or reserved))

[Debian Bug Tracking System]

Your message dated Thu, 31 Mar 2022 13:55:01 +0200
with message-id 
and subject line Re: Bug#985725: slurm-wlm: flaky autopkgtest: srun: Required 
node not available (down, drained or reserved)
has caused the Debian Bug report #985725,
regarding slurm-wlm: flaky autopkgtest: srun: Required node not available 
(down, drained or reserved)
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.)


-- 
985725: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985725
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: slurm-wlm
Version: 20.11.4-1
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] and I noticed it fails regularly on
all architectures I checked. I have copied some of the output below. Can
you please look into it and fix it? Either the output to stderr is
actually OK, then a allow-stderr restriction is enough to fix the issue,
or it's actually showing that there's a real issue that needs fixing (as
the test itself doesn't fail).

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.

Paul

https://ci.debian.net/packages/s/slurm-wlm/testing/amd64/

https://ci.debian.net/data/autopkgtest/testing/amd64/s/slurm-wlm/11213446/log.gz

autopkgtest [09:10:26]: test srun: [---
PARTITION AVAIL  TIMELIMIT  NODES  STATE NODELIST
test*up   infinite  1unk localhost
NODELIST   NODES PARTITION STATE
localhost  1 test* unk
srun: Required node not available (down, drained or reserved)
srun: job 2 queued and waiting for resources
srun: job 2 has been allocated resources
autopkgtest [09:10:31]: test srun: ---]
autopkgtest [09:10:31]: test srun:  - - - - - - - - - - results - - - -
- - - - - -
srun FAIL stderr: srun: Required node not available
(down, drained or reserved)
autopkgtest [09:10:31]: test srun:  - - - - - - - - - - stderr - - - - -
- - - - -



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Package: slurm-wlm
Version: 20.11.5-1

Hi Paul,

On Mon, Mar 22, 2021 at 07:35:00PM +0100, Paul Gevers wrote:
> Your package has an autopkgtest, great. However, I looked into
> the history of your autopkgtest [1] and I noticed it fails regularly on
> all architectures I checked. I have copied some of the output below. Can
> you please look into it and fix it?

I was not sure if [1] would have fix the problem, but it looks like it
did [2].

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

Sorry to read that, at the time I didn't know about these tests.

Best regards,

[1] 
https://salsa.debian.org/hpc-team/slurm-wlm/-/commit/c8cc263515f62cbbb579df4b41e09565e60a2628
[2] https://ci.debian.net/packages/s/slurm-wlm/testing/amd64/

-- 
Gennaro Oliva--- End Message ---

Bug#1008736: python-kyotocabinet: FTBFS with Python 3.10 as default

[Graham Inggs]

Source: python-kyotocabinet
Version: 1.23-2
Severity: serious
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.10

Hi Maintainer

As can be seen on reproducible builds [1], python-kyotocabinet FTBFS
with Python 3.10 as the default version.  I've copied what I hope is
the relevant part of the log below.

Regards
Graham


[1] https://tests.reproducible-builds.org/debian/rb-pkg/python-kyotocabinet.html


calling utility functions:
opening the database with functor:
setting records:
deploying cursors:
getting records:
accepting visitor:
Traceback (most recent call last):
  File "/build/1st/python-kyotocabinet-1.23/kctest.py", line 1015, in 
exit(main())
  File "/build/1st/python-kyotocabinet-1.23/kctest.py", line 37, in main
rv = runmisc()
  File "/build/1st/python-kyotocabinet-1.23/kctest.py", line 164, in runmisc
rv = procmisc(path)
  File "/build/1st/python-kyotocabinet-1.23/kctest.py", line 844, in procmisc
dberr = DB.process(myproc, path, DB.OWRITER | DB.OCREATE | DB.OTRUNCATE)
  File "/build/1st/python-kyotocabinet-1.23/kctest.py", line 753, in myproc
if not db.accept(i, visitfunc, True):
SystemError: PY_SSIZE_T_CLEAN macro must be defined for '#' formats
make[2]: *** [Makefile:77: check-each] Error 1

Bug#1008733: python-clickhouse-driver: FTBFS with Python 3.10 as default

[Graham Inggs]

Source: python-clickhouse-driver
Version: 0.2.3-1
Severity: serious
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.10

Hi Maintainer

As can be seen on reproducible builds [1], python-clickhouse-driver
FTBFS with Python 3.10 as the default version.  I've copied what I
hope is the relevant part of the log below.

Regards
Graham


[1] 
https://tests.reproducible-builds.org/debian/rb-pkg/python-clickhouse-driver.html


# Generate docs only after install
http_proxy='http://127.0.0.1:9/' python3 -m sphinx -N -E -bhtml docs build/html
Running Sphinx v4.3.2

Configuration error:
There is a programmable error in your configuration file:

Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/sphinx/config.py", line 329, in
eval_config_file
exec(code, namespace)
  File "/build/1st/python-clickhouse-driver-0.2.3/docs/conf.py", line
23, in 
from clickhouse_driver import __version__, VERSION
  File 
"/build/1st/python-clickhouse-driver-0.2.3/debian/python3-clickhouse-driver/usr/lib/python3.9/dist-packages/clickhouse_driver/__init__.py",
line 2, in 
from .client import Client
  File 
"/build/1st/python-clickhouse-driver-0.2.3/debian/python3-clickhouse-driver/usr/lib/python3.9/dist-packages/clickhouse_driver/client.py",
line 9, in 
from .block import ColumnOrientedBlock, RowOrientedBlock
  File 
"/build/1st/python-clickhouse-driver-0.2.3/debian/python3-clickhouse-driver/usr/lib/python3.9/dist-packages/clickhouse_driver/block.py",
line 1, in 
from .reader import read_varint, read_binary_uint8, read_binary_int32
  File 
"/build/1st/python-clickhouse-driver-0.2.3/debian/python3-clickhouse-driver/usr/lib/python3.9/dist-packages/clickhouse_driver/reader.py",
line 3, in 
from .varint import read_varint
ModuleNotFoundError: No module named 'clickhouse_driver.varint'

make[1]: *** [debian/rules:17: override_dh_auto_install] Error 2

Bug#1008731: python-pcl: FTBFS in unstable and testing

[Graham Inggs]

Source: python-pcl
Version: 0.3.0~rc1+dfsg-11
Severity: serious
Tags: ftbfs

Hi Maintainer

Since sometime around the end of January, python-pcl started to FTBFS
in unstable and testing [1].  I've copied what I hope is the relevant
part of the log below.

Regards
Graham


[1] https://tests.reproducible-builds.org/debian/rb-pkg/python-pcl.html


building 'pcl.pcl_visualization' extension
x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare
-DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat
-Werror=format-security -g -fwrapv -O2 -g -O2
-ffile-prefix-map=/build/python-pcl-0.3.0~rc1+dfsg=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -fPIC
-I/usr/lib/python3/dist-packages/numpy/core/include
-I/usr/include/pcl-1.12 -I/usr/include/eigen3 -I/usr/include/ni
-I/usr/include/openni2 -I/usr/include/ni -I/usr/include/vtk-9.0
-I/usr/local/include/vtk-8.0 -I/usr/local/Cellar/vtk/8.0.1/include
-I/usr/include/python3.9 -c pcl/pcl_visualization.cpp -o
build/temp.linux-x86_64-3.9/pcl/pcl_visualization.o
-fno-strict-aliasing
In file included from
/usr/include/pcl-1.12/pcl/visualization/point_cloud_handlers.h:41,
 from pcl/pcl_visualization.cpp:721:
/usr/include/pcl-1.12/pcl/visualization/point_cloud_geometry_handlers.h:49:10:
fatal error: vtkSmartPointer.h: No such file or directory
   49 | #include 
  |  ^~~
compilation terminated.
error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1
E: pybuild pybuild:367: build: plugin distutils failed with: exit
code=1: /usr/bin/python3 setup.py build

Processed: scikit-fmm: FTBFS: /usr/include/python3.10/object.h:133:33: error: lvalue required as increment operand

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #1008640 [src:scikit-fmm] scikit-fmm: FTBFS: 
/usr/include/python3.10/object.h:133:33: error: lvalue required as increment 
operand
Added tag(s) patch.

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

Bug#1008640: scikit-fmm: FTBFS: /usr/include/python3.10/object.h:133:33: error: lvalue required as increment operand

[Graham Inggs]

Control: tags -1 + patch

Patch available in ubuntu [1].

scikit-fmm (2019.1.30-1ubuntu1) jammy; urgency=medium

  * Cythonize at build time to fix FTBFS with Python 3.10
  * Call dh --with numpy3 to pick up dependency on numpy-abi

 -- Graham Inggs   Mon, 31 Jan 2022 13:30:41 +


[1] https://launchpad.net/ubuntu/+source/scikit-fmm/2019.1.30-1ubuntu1

Bug#1008722: Additional details on the build error

[Moessbauer, Felix]

> -Original Message-
> From: Sudip Mukherjee 
> Sent: Thursday, March 31, 2022 12:07 PM
> To: Moessbauer, Felix (T CED SES-DE) 
> Cc: Schmidt, Adriaan (T CED SES-DE) ;
> 1008...@bugs.debian.org
> Subject: Re: Bug#1008722: Additional details on the build error
> 
> Hi,
> 
> On Thu, Mar 31, 2022 at 10:57 AM Moessbauer, Felix
>  wrote:
> >
> > Hi,
> >
> > here are some additional details on the bug.
> > I'm also not 100% sure if the patch from above actually fixes the issue.
> > Looks like it is already applied.
> 
> Yes, I checked its already applied. Can you please let me know where can I 
> get a
> log for this failure, I could not find any failure in the buildd.

Hi,

we are building that locally with sbuilder. Attached you will find a log.

I also just created a branch on salsa to test the fix [1].
I'll pass it through our CI and report back if that helps.
In case it helps, I'll send it to the upstream list.

While we are at it: I also stumbled upon similar issues in libtraceevent, but 
want to sort out one at a time.

[1] https://salsa.debian.org/fmoessbauer/libtracefs/-/tree/felix/fix-ftbfs

Felix
> 
> 
> 
> --
> Regards
> Sudip


libtracefs-sbuild-error.log.gz
Description: libtracefs-sbuild-error.log.gz

Bug#1001595: marked as done (src:gcc-defaults-mipsen: fails to migrate to testing for too long)

[Debian Bug Tracking System]

Your message dated Thu, 31 Mar 2022 10:18:49 +
with message-id 
and subject line Bug#1001595: fixed in gcc-12-cross-mipsen 1+c2
has caused the Debian Bug report #1001595,
regarding src:gcc-defaults-mipsen: fails to migrate to testing for too long
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.)


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

Source: gcc-defaults-mipsen
Version: 1.189
Severity: serious
Control: close -1 1.194
Tags: sid bookworm
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 60 days as having a Release Critical bug in 
testing [1]. Your package src:gcc-defaults-mipsen has been trying to 
migrate for 62 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 bookworm, 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=gcc-defaults-mipsen



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: gcc-12-cross-mipsen
Source-Version: 1+c2
Done: YunQiang Su 

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

Debian distribution maintenance software
pp.
YunQiang Su  (supplier of updated gcc-12-cross-mipsen 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, 31 Mar 2022 09:52:39 +
Source: gcc-12-cross-mipsen
Architecture: source
Version: 1+c2
Distribution: unstable
Urgency: medium
Maintainer: Debian GCC Maintainers 
Changed-By: YunQiang Su 
Closes: 1001595
Changes:
 gcc-12-cross-mipsen (1+c2) unstable; urgency=medium
 .
   * Rebuild for testing migration. (Closes: #1001595)
Checksums-Sha1:
 64027b423b06afb09a0339b734f0a875e2f10cf3 60981 gcc-12-cross-mipsen_1+c2.dsc
 9a33e58f8717f346bf168c424fd31681e612bd79 44140 gcc-12-cross-mipsen_1+c2.tar.xz
 36435b65f02a26389bd74996c8ecac4993ca11ea 6842 
gcc-12-cross-mipsen_1+c2_source.buildinfo
Checksums-Sha256:
 f21bef9972bb618a50f9b6267c165357197afa7f50f425f29737fadc5730a697 60981 
gcc-12-cross-mipsen_1+c2.dsc
 5dfb6eedc51d866f9fe04bf3e4126da9dd3dbdb7ed31165179351d6280b949e0 44140 
gcc-12-cross-mipsen_1+c2.tar.xz
 529c3c038fa72c148ed91f91885d647cd4050a1c697317b8482c0413dbc73175 6842 
gcc-12-cross-mipsen_1+c2_source.buildinfo
Files:
 190d11f79708f0eaa13936ef54e40df6 60981 devel optional 
gcc-12-cross-mipsen_1+c2.dsc
 26495d4a16e11dedcd572c57b2a474ec 44140 devel optional 
gcc-12-cross-mipsen_1+c2.tar.xz
 db01d3c325916afef7079c112d0eccc8 6842 devel optional 
gcc-12-cross-mipsen_1+c2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCgAtFiEErzy/48olU1y1e1OneyQHvDH10NoFAmJFelQPHHN5cUBkZWJp
YW4ub3JnAAoJEHskB7wx9dDa82MP/39E46gzzY1dmMLEquH4Usd0HgqQs3pHbByG
Dg/eyGsL5GZtuuGhdvGvd0t6mQ87GY74qEKWIzt0GOaTwJW5hqrr3732OholLI8Y
Zxc/+aBv+sgZToXr04ZlikiMkMqiMX9Vc5CrZ9R2a8FQUq9bETV26+mk/XoTmJ9z
tkLRKmLI06OrEA+ppS1hm7FnJzhXnjAWHWygMICSApdQ9TxhrpIAXPak

Bug#1001595: src:gcc-defaults-mipsen: fails to migrate to testing for too long

[YunQiang Su]

Paul Gevers  于2022年3月31日周四 16:16写道：
>
> Hi YunQiang,
>
> On 24-03-2022 12:29, YunQiang Su wrote:
> > Yes. I am aware of it. And I am waiting for gcc-12-cross-mipsen to finish
> > building on all of these architectures.
>
> Although not clear to me why you wanted to wait, this happened 3.5 days
> ago. Will you do the source only upload soon?
>

The new version was uploaded.

> Paul



-- 
YunQiang Su

Bug#1008722: Additional details on the build error

[Sudip Mukherjee]

Hi,

On Thu, Mar 31, 2022 at 10:57 AM Moessbauer, Felix
 wrote:
>
> Hi,
>
> here are some additional details on the bug.
> I'm also not 100% sure if the patch from above actually fixes the issue.
> Looks like it is already applied.

Yes, I checked its already applied. Can you please let me know where
can I get a log for this failure, I could not find any failure in the
buildd.



-- 
Regards
Sudip

Bug#1008722: Additional details on the build error

[Moessbauer, Felix]

Hi,

here are some additional details on the bug.
I'm also not 100% sure if the patch from above actually fixes the issue.
Looks like it is already applied.

The issue is a missing symbol:
tracefs_set_loglevel@Base 1.2.0
- tracefs_sql@Base 1.3.0
+#MISSING: 1.3.0-1# tracefs_sql@Base 1.3.0

This symbol is declared in include/tracefs.h and defined in 
src/tracefs-sqlhist.c.
The race condition results in linking tracefs-sqlhist.o without having 
src/tracefs-sqlhist.c compiled.
This can be checked with readelf:
readelf -s src/tracefs-sqlhist.o | grep tracefs_sql
94: 30fe   375 FUNCGLOBAL DEFAULT1 tracefs_sql

But on some runs, it is missing. Probably because we overwrite the dep 
(src/Makefile):
tracefs-sqlhist.o: sqlhist.tab.h

Another strange thing is that the files that are generated with flex / bison 
are checked in, but sometimes this is not detected correctly.
In case this is not detected, the build also fails because bison and flex are 
not added as dependencies (hence are not installed by sbuilder).

We should also clarify this with upstream.

Felix
--
Siemens AG, Technology, T CED SES-DE
Otto-Hahn-Ring 6, 81739 München, Germany

Processed: apbs 3.4 requires FETK which does not support system SuperLU

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/Electrostatics/FETK/issues/62
Bug #1008726 [apbs] apbs 3.4 requires FETK which does not support system SuperLU
Set Bug forwarded-to-address to 
'https://github.com/Electrostatics/FETK/issues/62'.
> block 1006382 by -1
Bug #1006382 [src:apbs] apbs: failing autopkgtest on one of ci.d.n amd64 workers
1006382 was not blocked by any bugs.
1006382 was not blocking any bugs.
Added blocking bug(s) of 1006382: 1008726

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

Bug#1008722: libtracefs: FTBFS race condition on parallel build

[Felix Moessbauer]

Source: libtracefs
Version: 1.3.0-1
Severity: serious
Tags: ftbfs upstream patch
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: felix.moessba...@siemens.com

Dear Maintainer,

the upstream version 1.3.0 has a race condition in the src/Makefile,
which breaks the build sporadically (when building on a machine with
many cores).

A patch is already available upstream [1].
Reproducing this manually is really tricky, but we consistently see it
on nightly builds with sbuilder.

[1] 
https://git.kernel.org/pub/scm/libs/libtrace/libtracefs.git/commit/src?id=567fc8b8d4d5d8c536e82525e69af82d13b4e181

Best regards,
Felix Moessbauer
Siemens AG

-- System Information:
Debian Release: 11.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: arm64, x32

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

Bug#1001595: src:gcc-defaults-mipsen: fails to migrate to testing for too long

[Paul Gevers]

Hi YunQiang,

On 24-03-2022 12:29, YunQiang Su wrote:

Yes. I am aware of it. And I am waiting for gcc-12-cross-mipsen to finish
building on all of these architectures.


Although not clear to me why you wanted to wait, this happened 3.5 days 
ago. Will you do the source only upload soon?


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1006780: marked as done (gcc-11-cross-mipsen: rebuild results in packages with unsatifiable dependencies)

[Debian Bug Tracking System]

Your message dated Thu, 31 Mar 2022 10:09:46 +0200
with message-id <21426fcd-7065-8db9-ebab-7952e435f...@debian.org>
and subject line is fixed: 1006780: gcc-11-cross-mipsen: rebuild results in 
packages with unsatifiable dependencies
has caused the Debian Bug report #1006780,
regarding gcc-11-cross-mipsen: rebuild results in packages with unsatifiable 
dependencies
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.)


-- 
1006780: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006780
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gcc-11-cross-mipsen
Version: 4+c1
Severity: serious

Dear maintainer,

Your package failed to migrate to testing because some binaries were
built by the uploader instead of on the buildds. I tried to help and
did a no-change source-only upload. However, this package seems to be
complicated because the build succeeded, but the binaries are not
installable [1].

Can you please fix your package and do a source-only upload such that
it can migrate to testing?

[1] https://qa.debian.org/excuses.php?package=gcc-11-cross-mipsen

Paul
--- End Message ---
--- Begin Message ---

Version: 5+c1

This issue seems to be fixed with the latest upload.

Paul


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---

Processed: src:yosys: fails to migrate to testing for too long: FTBFS on mips64el and s390x & autopkgtest regression

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.15-1
Bug #1008718 [src:yosys] src:yosys: fails to migrate to testing for too long: 
FTBFS on mips64el and s390x & autopkgtest regression
Marked as fixed in versions yosys/0.15-1.
Bug #1008718 [src:yosys] src:yosys: fails to migrate to testing for too long: 
FTBFS on mips64el and s390x & autopkgtest regression
Marked Bug as done

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

Bug#1008718: src:yosys: fails to migrate to testing for too long: FTBFS on mips64el and s390x & autopkgtest regression

[Paul Gevers]

Source: yosys
Version: 0.9-2
Severity: serious
Control: close -1 0.15-1
Tags: sid bookworm ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 60 days as having a Release Critical bug in 
testing [1]. Your package src:yosys has been trying to migrate for 61 
days [2]. Hence, I am filing this bug. Your latest upload failed to 
build from source on mips64el and s390x where it built successfully in 
the past. The latest upload also caused autopgktest regression on all 
architectures.


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 bookworm, 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=yosys



OpenPGP_signature
Description: OpenPGP digital signature

Processed: closing 995115

[Debian Bug Tracking System]

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

> close 995115
Bug #995115 [libruby2.7] /usr/bin/ruby: symbol lookup error: 
/lib/x86_64-linux-gnu/libruby-2.7.so.2.7: undefined symbol: rb_st_numhash
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: tagging 1008650, notfixed 1001360 in 1.0.2, fixed 1001360 in 1.0.2-1, tagging 1008700 ...

[Debian Bug Tracking System]

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

> tags 1008650 + sid bookworm
Bug #1008650 [src:unbound] python3-unbound: Cannot install because of Python 
dependencies
Bug #1008641 [src:unbound] unbound: FTBFS: ./pythonmod/pythonmod.c:338: 
undefined reference to `_Py_fopen'
Ignoring request to alter tags of bug #1008650 to the same tags previously set
Ignoring request to alter tags of bug #1008641 to the same tags previously set
> notfixed 1001360 1.0.2
Bug #1001360 {Done: Jeremy Sowden } [nftables] nftables: nft 
returns "BUG: unsupported familynft: evaluate.c:2766..."
There is no source info for the package 'nftables' at version '1.0.2' with 
architecture ''
Unable to make a source version for version '1.0.2'
No longer marked as fixed in versions 1.0.2.
> fixed 1001360 1.0.2-1
Bug #1001360 {Done: Jeremy Sowden } [nftables] nftables: nft 
returns "BUG: unsupported familynft: evaluate.c:2766..."
Marked as fixed in versions nftables/1.0.2-1.
> tags 1008700 + sid bookworm
Bug #1008700 [src:geda-gaf] Should geda-gaf be removed?
Added tag(s) sid and bookworm.
> tags 1008704 + sid bookworm
Bug #1008704 [src:astk] Sould astk be removed?
Added tag(s) bookworm and sid.
> tags 1008703 + sid bookworm
Bug #1008703 [src:sortsmill-tools] Should sortsmill-tools be removed?
Added tag(s) sid and bookworm.
> tags 1008702 + sid bookworm
Bug #1008702 [src:ketchup] Should ketchup be removed?
Added tag(s) sid and bookworm.
> tags 1008701 + sid bookworm
Bug #1008701 [src:broctl] Should broctl be removed?
Added tag(s) bookworm and sid.
> fixed 981037 0.3.0-1
Bug #981037 {Done: Jeremy Bicha } [libcolord-gtk1] 
libcolord-gtk1: depends on transitional libgdk-pixbuf2.0-0 package
Marked as fixed in versions colord-gtk/0.3.0-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1001360: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001360
1008641: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008641
1008650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008650
1008700: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008700
1008701: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008701
1008702: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008702
1008703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008703
1008704: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008704
981037: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981037
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: libplplot-dev: Uninstallable since libltdl-dev stopped providing libltdl3-dev with its 2.4.7-2 upload

[Debian Bug Tracking System]

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

> tags 1008470 + ftbfs
Bug #1008470 [libplplot-dev] libplplot-dev: Uninstallable since libltdl-dev 
stopped providing libltdl3-dev with its 2.4.7-2 upload
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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