Bug#1013460: marked as done (synfig: FTBFS with ffmpeg 5.0)

[Debian Bug Tracking System]

Your message dated Tue, 05 Jul 2022 05:49:49 +
with message-id 
and subject line Bug#1013460: fixed in synfig 1.5.1+dfsg-3
has caused the Debian Bug report #1013460,
regarding synfig: FTBFS with ffmpeg 5.0
to be marked as done.

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

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


-- 
1013460: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013460
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: synfig
Version: 1.5.1+dfsg-2
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=synfig=amd64=1.5.1%2Bdfsg-2%2Bb1=1656018432=0

libtool: compile:  g++ -DHAVE_CONFIG_H -I../../.. -I../../../src -Wdate-time 
-D_FORTIFY_SOURCE=2 -I/usr/include -I/usr/include/glibmm-2.4 
-I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/sigc++-2.0 
-I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include -pthread 
-I/usr/include/giomm-2.4 -I/usr/lib/x86_64-linux-gnu/giomm-2.4/include 
-I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glibmm-2.4 
-I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/sigc++-2.0 
-I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include -I/usr/include/libxml++-2.6 
-I/usr/lib/x86_64-linux-gnu/libxml++-2.6/include -I/usr/include/libxml2 
-I/usr/include/glibmm-2.4 -I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include 
-I/usr/include/mlt-7/mlt++ -I/usr/include/mlt-7 -I/usr/include/ETL 
-I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include 
-DSYNFIG_NO_DEPRECATED -DLOCALEDIR=\"/usr/share/locale\" 
-I/usr/include/x86_64-linux-gnu -D__STDC_CONSTANT_MACROS 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -O2 -DNDEBUG -W -Wall -c trgt_av.cpp  -fPIC -DPIC -o 
.libs/libmod_libavcodec_la-trgt_av.o
In file included from main.cpp:35:
main.cpp: In function ‘synfig::Module* 
mod_libavcodec_LTX_new_instance(synfig::ProgressCallback*)’:
../../../src/synfig/module.h:85:9: warning: this ‘if’ clause does not guard... 
[-Wmisleading-indentation]
   85 | if(cb)cb->error(#x": Unable to load module due to version 
mismatch."); return nullptr; } \
  | ^~
main.cpp:53:1: note: in expansion of macro ‘MODULE_INVENTORY_BEGIN’
   53 | MODULE_INVENTORY_BEGIN(mod_libavcodec)
  | ^~
../../../src/synfig/module.h:85:80: note: ...this statement, but the latter is 
misleadingly indented as if it were guarded by the ‘if’
   85 | if(cb)cb->error(#x": Unable to load module due to version 
mismatch."); return nullptr; } \
  | 
   ^~
main.cpp:53:1: note: in expansion of macro ‘MODULE_INVENTORY_BEGIN’
   53 | MODULE_INVENTORY_BEGIN(mod_libavcodec)
  | ^~
trgt_av.cpp: In member function ‘bool 
Target_LibAVCodec::Internal::add_video_stream(AVCodecID, const 
synfig::RendDesc&)’:
trgt_av.cpp:127:33: error: ‘avcodec_alloc_context3’ was not declared in this 
scope; did you mean ‘avio_alloc_context’?
  127 | video_context = avcodec_alloc_context3(video_codec);
  | ^~
  | avio_alloc_context
trgt_av.cpp:136:30: error: invalid use of incomplete type ‘struct 
AVCodecContext’
  136 | video_context->bit_rate = 400*1024*1024/3600; // 
400Mb per hour
  |  ^~
In file included from /usr/include/x86_64-linux-gnu/libavformat/avformat.h:313,
 from trgt_av.cpp:41:
/usr/include/x86_64-linux-gnu/libavcodec/codec.h:195:8: note: forward 
declaration of ‘struct AVCodecContext’
  195 | struct AVCodecContext;
  |^~
trgt_av.cpp:137:30: error: invalid use of incomplete type ‘struct 
AVCodecContext’
  137 | video_context->width= desc.get_w();   // in 
most cases resolution must be multiple of two
  |  ^~
In file included from /usr/include/x86_64-linux-gnu/libavformat/avformat.h:313,
 from trgt_av.cpp:41:
/usr/include/x86_64-linux-gnu/libavcodec/codec.h:195:8: note: forward 
declaration of ‘struct AVCodecContext’
  195 | struct AVCodecContext;
  |

Bug#1013460: marked as pending in synfig

[Dmitry Smirnov]

Control: tag -1 pending

Hello,

Bug #1013460 in synfig 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/multimedia-team/synfig/-/commit/311786b8ee92be23266e686edef0643ace37367e


New upstream patch to fix FTBFS with ffmpeg-5.0 (Closes: #1013460).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1013460

Processed: Bug#1013460 marked as pending in synfig

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1013460 [src:synfig] synfig: FTBFS with ffmpeg 5.0
Added tag(s) pending.

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

Bug#1013929: marked as done (src:goffice: fails to migrate to testing for too long: FTBFS on mips64el)

[Debian Bug Tracking System]

Your message dated Tue, 05 Jul 2022 05:18:50 +
with message-id 
and subject line Bug#1013929: fixed in goffice 0.10.52-2
has caused the Debian Bug report #1013929,
regarding src:goffice: fails to migrate to testing for too long: FTBFS on 
mips64el
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.)


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

Source: goffice
Version: 0.10.51-1
Severity: serious
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:goffice has been trying to migrate for 61 
days [2]. Hence, I am filing this bug. Your package fails to build from 
source on mips64el where it successfully built in the past.


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


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


I have tagged this bug to only affect sid and 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=goffice



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: goffice
Source-Version: 0.10.52-2
Done: Dmitry Smirnov 

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

Debian distribution maintenance software
pp.
Dmitry Smirnov  (supplier of updated goffice package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 05 Jul 2022 14:38:29 +1000
Source: goffice
Architecture: source
Version: 0.10.52-2
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Smirnov 
Changed-By: Dmitry Smirnov 
Closes: 1013929
Changes:
 goffice (0.10.52-2) unstable; urgency=medium
 .
   * Use `--without-long-double` on [mips64el] (Closes: #1013929).
Checksums-Sha1:
 e915d94633c73dadd885ffe4f23acc4a9b4b2867 2503 goffice_0.10.52-2.dsc
 f1c0eae22c93c8845b4076d71e32650adcc0e5e6 23328 goffice_0.10.52-2.debian.tar.xz
 3b6a072556b874c176b5e18fdb021e46165f8a51 16882 
goffice_0.10.52-2_amd64.buildinfo
Checksums-Sha256:
 eae2fe681c100714a56ffd9512af1696580fa05df4e2936481ef549c3a8a69a3 2503 
goffice_0.10.52-2.dsc
 c2dd2bc880c37c71c62b354d2a18c240b788b203c6c3fde633766f43282c85d8 23328 
goffice_0.10.52-2.debian.tar.xz
 d57e87f1f1fd5a0ce3afb2a61aacfb9e2b659dbfaab111e2ae46fca0ec5b65d9 16882 
goffice_0.10.52-2_amd64.buildinfo
Files:
 a51322dbdfb002e213a5c15a4432b5ae 2503 libs optional goffice_0.10.52-2.dsc
 8d2616daa86e8858cd11c7060a706621 23328 libs optional 
goffice_0.10.52-2.debian.tar.xz
 40708442aef8d8cb04d159d972617337 16882 libs optional 
goffice_0.10.52-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEULx8+TnSDCcqawZWUra72VOWjRsFAmLDwdkACgkQUra72VOW
jRuiNBAAkC3MpdUQ3cFoj4ccn7RG47TKgEPC2Syl8/E7E5bo67ZOFP3Bp+5a9sE9
v57elVQaWdI52YaekbLeWWM+URJMpDYt9ir6nn9UQTANfOJovLjAPGiBFh+seIkT
laSSSLzLpkCuopxmkl4S/eAstOe4SDU8tLmP4/fxBCqxeFxvpGCCl91ImS3uMH3R
VM4x78cQv3OvYF69ZxQwQ5jZaza94HzJw3RJfcLgSDz7d0JtLTVOMVy56+2jbyX5
G0cvQU78yI42GaJnU+4PzccVaz1d2dzfngpmzLEqA1FLkyEXoX3bQ2KcpnbJLNVw
liW/7dRLGaD3tCqLSGhHmzh/3LeSCuEc3PMlJhy/HFdiOl0nKMPBVFUadvRqYqyO

Bug#1012741: Subject: Re: Bug#1012741: modprobe: ERROR: could not insert 'crc_itu_t': Key was rejected by service

[Daniel Lewart]

It's like déjà vu all over again:
#942881 - snd-hda-codec-hdmi signature corruption
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942881

Thank you!
Dan
Urbana, Illinois

Processed: Bug#1013929 marked as pending in goffice

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1013929 [src:goffice] src:goffice: fails to migrate to testing for too 
long: FTBFS on mips64el
Added tag(s) pending.

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

Bug#1013929: marked as pending in goffice

[Dmitry Smirnov]

Control: tag -1 pending

Hello,

Bug #1013929 in goffice 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/debian/goffice/-/commit/3cd973d85f5b6d337100270e068f09fd30d8cea5


Use `--without-long-double` on [mips64el] to fix FTBFS (Closes: #1013929).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1013929

Processed: bug 1013929 is forwarded to https://gitlab.gnome.org/GNOME/goffice/-/issues/59

[Debian Bug Tracking System]

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

> forwarded 1013929 https://gitlab.gnome.org/GNOME/goffice/-/issues/59
Bug #1013929 [src:goffice] src:goffice: fails to migrate to testing for too 
long: FTBFS on mips64el
Set Bug forwarded-to-address to 
'https://gitlab.gnome.org/GNOME/goffice/-/issues/59'.
> thanks
Stopping processing here.

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

Bug#1014353: Fwd: Processed: forcibly merging 1014314 1014353 [origin: ow...@bugs.debian.org]

[Axel Beckert]

Hi Marie,

thanks for the hint in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014353#10 — your
bug
report is now marked as fixed:

- Forwarded message from Debian Bug Tracking System  
-
Date: Tue, 05 Jul 2022 02:45:06 +
From: Debian Bug Tracking System 
To: Axel Beckert 
CC: team+...@tracker.debian.org, debian-bugs-clo...@lists.debian.org
Subject: Processed: forcibly merging 1014314 1014353

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

> # See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014353#10
> forcemerge 1014314 1014353
Bug #1014314 {Done: Bastian Blank } [lvm2] lvm2: Missing 
69-lvm-metad.rules causes lvm2 initramfs-tools hook to fail
Bug #1014353 [lvm2] lvm2: initramfs hook fails due to missing 69-lvm-metad.rules
Severity set to 'serious' from 'critical'
Marked Bug as done
Marked as fixed in versions lvm2/2.03.15-2.
Merged 1014314 1014353
> thanks
Stopping processing here.

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

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


signature.asc
Description: PGP signature

Processed: forcibly merging 1014314 1014353

[Debian Bug Tracking System]

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

> # See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014353#10
> forcemerge 1014314 1014353
Bug #1014314 {Done: Bastian Blank } [lvm2] lvm2: Missing 
69-lvm-metad.rules causes lvm2 initramfs-tools hook to fail
Bug #1014353 [lvm2] lvm2: initramfs hook fails due to missing 69-lvm-metad.rules
Severity set to 'serious' from 'critical'
Marked Bug as done
Marked as fixed in versions lvm2/2.03.15-2.
Merged 1014314 1014353
> thanks
Stopping processing here.

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

Bug#1013662: core-async-clojure: FTBFS: make[1]: *** [debian/rules:22: override_dh_auto_test] Error 1

[Jérôme Charaoui]

Hello,

I'm unable to reproduce this bug locally.

When I diff, the build logs, the only relevant element I can find is 
that in my build environment, the "clojure_1.10.3-1" package is 
installed, whereas in the failing build log, it appears to be absent.


I think it would be worth it to attempt to build it again.

Thanks,

-- Jerome

Bug#1014368: dmesg: --human output not paged if less not installed

[http]

Package: util-linux
Version: 2.38
Severity: serious

The documentation for dmesg states that "A pager is enabled by default for --human output." However, if the less pager is not 
installed, the output is not sent to a pager unless the PAGER variable is set.


This means that there is a hard-coded and undocumented dependency on the less package for correct behaviour. At the least, this 
appears to be a violation of the Debian Policy Manual, section 3.5.

https://www.debian.org/doc/debian-policy/ch-binary.html#dependencies

Possible solutions, not in any order:
- Default to the more pager (included in the same package as dmesg)
- Default to /etc/alternatives/pager
- Declare a dependency on sensible-utils, to use sensible-pager from that 
package
- Declare a dependancy on the less package
- Update documentation to reflect actual behaviour and suggest setting the 
PAGER variable

Temporary workaround:
- set PAGER to the preferred pager.



-- System Information:
Debian Release: bookworm/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: powerpc (ppc)

Kernel: Linux 5.16.0-5-powerpc
Kernel taint flags: TAINT_UNSIGNED_MODULE
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages util-linux depends on:
ii  libblkid1 2.38-4
ii  libc6 2.33-7
ii  libcap-ng00.8.3-1
ii  libcrypt1 1:4.4.28-1
ii  libmount1 2.38-4
ii  libpam0g  1.4.0-13
ii  libselinux1   3.4-1
ii  libsmartcols1 2.38-4
ii  libsystemd0   251.2-2
ii  libtinfo6 6.3+20220423-2
ii  libudev1  251.2-7
ii  libuuid1  2.38-4
ii  util-linux-extra  2.38-4
ii  zlib1g1:1.2.11.dfsg-4

util-linux recommends no packages.

Versions of packages util-linux suggests:
ii  dosfstools  4.2-1
ii  kbd 2.3.0-3
ii  util-linux-locales  2.38-4

Bug#1013700: marked as done (python-qtpy: FTBFS: pytest7 regression, TypeError: the 'package' argument is required to perform a relative import)

[Debian Bug Tracking System]

Your message dated Mon, 04 Jul 2022 22:07:10 +
with message-id 
and subject line Bug#1013700: fixed in python-qtpy 2.1.0-3
has caused the Debian Bug report #1013700,
regarding python-qtpy: FTBFS: pytest7 regression, TypeError: the 'package' 
argument is required to perform a relative import
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.)


-- 
1013700: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013700
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-qtpy
Version: 2.1.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-pyt...@lists.debian.org
Usertags: pytest7

Hi,

During a selected rebuild of python packages in sid, your package failed
to build with pytest version 7.1.2-1.

The full build log is available from:
http://qa-logs.debian.net/2022/06/09/pytest/python-qtpy_2.1.0-2_unstable_pytest-exp.log

I had a closer look at the error log and identified the regression as:
'TypeError: the 'package' argument is required to perform a relative
import'. Hopefully, that's helpful!

All bugs filed during this rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=pytest7;users=debian-pyt...@lists.debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=pytest7=debian-pyt...@lists.debian.org=1=1=1=1#results

If you reassign this bug to another package, please mark 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 the one provided so that we can identify if something relevant
changed in the meantime.

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: python-qtpy
Source-Version: 2.1.0-3
Done: Julian Gilbey 

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

Debian distribution maintenance software
pp.
Julian Gilbey  (supplier of updated python-qtpy package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 04 Jul 2022 22:45:45 +0100
Source: python-qtpy
Architecture: source
Version: 2.1.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Julian Gilbey 
Closes: 1013700
Changes:
 python-qtpy (2.1.0-3) unstable; urgency=medium
 .
   * Fix FTBFS error with Pytest 7.x (closes: #1013700)
   * Update d/copyright and standards-version
   * Add missing documentation to /usr/share/doc/python3-qtpy
   * Add build-depends for new pybuild version
   * Add qtpy(1) manpage
Checksums-Sha1:
 7f197188ec46fad9c47d968e9fe72faa8224dfc9 3534 python-qtpy_2.1.0-3.dsc
 c04c7a83177e4a558c4808ae301b3e120a7a 5832 python-qtpy_2.1.0-3.debian.tar.xz
 6b2417ed8c1775d1221cf737b1a15d9267e7f740 13821 
python-qtpy_2.1.0-3_amd64.buildinfo
Checksums-Sha256:
 cf68d770359e31eda1503f55a9d698ca73ed05706119d29bacc37ac65336b6f7 3534 
python-qtpy_2.1.0-3.dsc
 49357d644766a3d08ebe4e267a91e738f4267ff9d9873f4fb47ea888aa047f65 5832 
python-qtpy_2.1.0-3.debian.tar.xz
 5183d6203033878db2349ad230ba95044f3869afa570deaf2501130554c97c8e 13821 
python-qtpy_2.1.0-3_amd64.buildinfo
Files:
 9ca95a3f918c5da6298595eb44f2f80c 3534 python optional python-qtpy_2.1.0-3.dsc
 6152f2f4285136a8193aababc315e8c5 5832 python optional 
python-qtpy_2.1.0-3.debian.tar.xz
 51d97f443b0509944b714031f4965eb1 13821 python optional 
python-qtpy_2.1.0-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCAAtFiEEfhrD+iemSShMMj72aVxCkxbAe/4FAmLDYG4PHGpkZ0BkZWJp
YW4ub3JnAAoJEGlcQpMWwHv+OYsP/1zonH2FJIibZgT9V4p1NMyyVqxtrsTSE2aF
ZAmAOESR8GopZKgwKPOsYE5zpJGX24IfGARlPcQnwrKKOSNsJ6YR/L1Ryv/0evYC
mqTuPenww96oIkogECxjNBkomt/MQJ/sEQ+dklPPr7uttQPWbg30xdVtHpFe7Aqx
A1zBxq5JYZCs9Sy5+TFNWwsDXufBeh+++ksNDU77uKVpQHKc/OYLkeE5LdGLsDRW
Ohn2u8wPvRy8C0QXoOA/nDfOYNpUzlPP0C0SLvXQ9u+kVAQpzqo37/2pPOHmbWk0
DcQtFizriRVmYunNi+/2Aco/Pny15j8DRei3o7bSKPGtSGk5+66LxWfr7TsVL8t0
PbutVgJ4Zs1RAjSJrbk9TAfxuMPSTgODUlB0gcFq4vXLy03Hu9Wu8opRPetec0ZK

Processed: Bug#1013700 marked as pending in python-qtpy

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1013700 [src:python-qtpy] python-qtpy: FTBFS: pytest7 regression, 
TypeError: the 'package' argument is required to perform a relative import
Added tag(s) pending.

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

Bug#1013700: marked as pending in python-qtpy

[Julian Gilbey]

Control: tag -1 pending

Hello,

Bug #1013700 in python-qtpy 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/python-team/packages/python-qtpy/-/commit/e7d0236cc1a1e1718a05ed4a09a7dd24fca6b723


Fix FTBFS error with Pytest 7.x (closes: #1013700)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1013700

Bug#1013700: Strangely rare pytest 7.x bug report

[Julian Gilbey]

Hi Carles,

It is utterly, utterly bizarre.  But I think I've found the problem.
There's a pytest.ini file in the package, but it's not copied into the
test directory.  So when pytest is run in the .pybuild directory, it
climbs all the way back up the directory tree to the python-qtpy-2.1.0
until it discovers the pytest.ini file there and uses that.  It sees
that we are requesting qtpy/tests, which it then expands into the
directory path .pybuild/cpython3_3.10_qtpy/build/qtpy/tests, starting
from the directory in which it found pytest.ini, and this causes the
breakage.

The solution is to copy the pytest.ini file into the .pybuild
directories by adding it to debian/pybuild.testfiles

Why this behaviour changed between pytest 6.x and pytest 7.x I don't
know; I don't see it obviously documented.  But that at least resolves
this problem.

Thanks for your help!

Best wishes,

   Julian

On Mon, Jul 04, 2022 at 08:39:32PM +0100, Carles Pina i Estany wrote:
> 
> Hi Julian,
> 
> On Jul/04/2022, Julian Gilbey wrote:
> > Hi Carles,
> > 
> > Thanks for your thoughts!  Yes, indeed that seems to be the issue.
> > But what I don't understand is why the import is turned into
> > .pybuild.cpython3_3.9_qtpy.build.qtpy.tests and not just qtpy.tests or
> 
> I see how pytest does it (but keep reading)
> 
> > a longer path, and why only this package fails in this way.  Perhaps
> > this is the only package that has an import statement in
> > pytest_configure?
> 
> This I don't know and I'm curious, and it might help disecting the issue
> (or understanding it). Do you know of any other python3 package that you
> expected to fail? (using pytest in a similar way).
> 
> I might try to get both and follow what they do different (to hopefully
> know what is python-qtpy doing different :-) )
> 
> I'm sure that there are tons of packages that use pytest :-) I'm
> wondering if you had a good candidate.
> 
> Best regards,
> 
> > 
> > Best wishes,
> > 
> >Julian
> > 
> > On Mon, Jul 04, 2022 at 04:03:39PM +0100, Carles Pina i Estany wrote:
> > > 
> > > Hi,
> > > 
> > > I'm a lurker of debian-pyt...@lists.debian.org but seeing Python+Qt I
> > > wanted to have a look. I don't have a solution (I might look more
> > > another time if time permits) but I might have something that might help
> > > someone who knows the tools better.
> > > 
> > > I am not familiar with Python Debian packaging details/tools neither
> > > with pytest :-( so take all of this with a pinch of salt.
> > > 
> > > If it helps the error comes from:
> > > /usr/lib/python3.9/importlib/__init__.py in the functin "import_modules"
> > > it does:
> > > """
> > > if name.startswith('.'):
> > > if not package:
> > > msg = ("the 'package' argument is required to perform a 
> > > relative "
> > >"import for {!r}")
> > > raise TypeError(msg.format(name))
> > > """
> > > 
> > > When the import fails the "name" parameter of "import_modules" function
> > > is: '.pybuild.cpython3_3.9_qtpy.build.qtpy.tests' , which is derived
> > > from the hidden dirctory ".pybuild" as created by default by "pybuild".
> > > 
> > > I think that the initial "." is used only as a directory name but Python
> > > assumes that is a relative import requiring the package parameter.
> > > 
> > > Just to check my thoughts, and after running dpkg-buildpackage and
> > > failing let's try again:
> > > 
> > > $ cd .pybuild/cpython3_3.9_qtpy/build; python3.9 -m pytest qtpy/tests ; 
> > > cd -
> > > Fails with the:
> > > 
> > > TypeError: the 'package' argument is required to perform a relative 
> > > import for '.pybuild.cpython3_3.9_qtpy.build.qtpy.tests'
> > > /home/carles/git/python-qtpy
> > > 
> > > Then let's try to avoid the initial "." confusion:
> > > 
> > > $ mv .pybuild pybuild
> > > $ cd pybuild/cpython3_3.9_qtpy/build; python3.9 -m pytest qtpy/tests ; cd 
> > > -
> > > 
> > > It works.
> > > 
> > > I don't know why this is the only package affected by this though...
> > > 
> > > Hopefully it helps a bit!
> > > 
> > > On Jul/04/2022, Julian Gilbey wrote:
> > > > Dear all,
> > > > 
> > > > I wonder whether you might have any clue about
> > > > https://bugs.debian.org/1013700
> > > > I have mostly worked out the "cause" of the bug, but I haven't quite
> > > > got to the bottom of it.
> > > > 
> > > > When running the command
> > > > PYTHONPATH=. python3.10 -m pytest qtpy/tests
> > > > in the directory .pybuild/cpython3_3.10_qtpy/build, I get the error
> > > > message:
> > > > 
> > > > ImportError while loading conftest 
> > > > '/home/jdg/debian/spyder-packages/qtpy/build-area/python-qtpy-2.1.0/.pybuild/cpython3_3.10_qtpy/build/qtpy/tests/conftest.py'.
> > > > TypeError: the 'package' argument is required to perform a relative 
> > > > import for '.pybuild.cpython3_3.10_qtpy.build.qtpy.tests'
> > > > 
> > > > If the directory .pybuild is renamed to pybuild, the tests run without
> > > > a problem.  So there seems to be something funny about 

Bug#1014282: marked as done (perl: autopkgtest failure: needs Provides/Replaces/Breaks for libtext-balanced-perl)

[Debian Bug Tracking System]

Your message dated Mon, 04 Jul 2022 21:13:37 +
with message-id 
and subject line Bug#1014282: fixed in perl 5.34.0-5
has caused the Debian Bug report #1014282,
regarding perl: autopkgtest failure: needs Provides/Replaces/Breaks for 
libtext-balanced-perl
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.)


-- 
1014282: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014282
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: perl
Version: 5.34.0-4
Severity: serious
Control: block -1 by 1014280

The perl package recently started failing its autopkgtest checks
in testing.

  #   Failed test 'no potential packages for new Provides/Replaces/Breaks found 
in the archive'
  #   at debian/t/control.t line 303.
  #  got: 'libtext-balanced-perl'
  # expected: ''
  # Looks like you failed 1 test of 590.
  debian/t/control.t .. 
 
This is because libtext-balanced-perl got introduced in the archive
and we need to add corresponding metadata for it in the perl package.

A complication is that pdl has added an unversioned dependency on
libtext-balanced-perl while it really needs a newer one.  So making the
perl core packages Provide libtext-balanced-perl will break pdl.

I've filed a separate bug about this, and would prefer to have
pdl changed first.
-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: perl
Source-Version: 5.34.0-5
Done: Niko Tyni 

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

Debian distribution maintenance software
pp.
Niko Tyni  (supplier of updated perl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 04 Jul 2022 22:22:58 +0300
Source: perl
Architecture: source
Version: 5.34.0-5
Distribution: unstable
Urgency: medium
Maintainer: Niko Tyni 
Changed-By: Niko Tyni 
Closes: 1010866 1014282
Changes:
 perl (5.34.0-5) unstable; urgency=medium
 .
   * Add Provides/Breaks/Replaces for libtext-balanced-perl.
 (Closes: #1014282)
   * Fix the Perl debugger 'view code' command. (Closes: #1010866)
Checksums-Sha1:
 6b3b21b6d1263a76cfb8beba17105d7d5b751f05 2886 perl_5.34.0-5.dsc
 d1b23d2d59a1b73106310dcf9e6270a71e8b963d 167484 perl_5.34.0-5.debian.tar.xz
 90c11f66c252fd7feba1e25c48e1a0cb7abc7dd9 6292 perl_5.34.0-5_source.buildinfo
Checksums-Sha256:
 fa744b5d2786d0dda1bfdb2960e0c2b66a734c4e268ec5de8e378366f680f021 2886 
perl_5.34.0-5.dsc
 dbbb6c9c5218faef00bf5ee38b1c4e76bb02733742368984517b6e2449708f93 167484 
perl_5.34.0-5.debian.tar.xz
 abc309a6573cf3f9b2f3f4d37da53a64ba8e24c9ac23e3dd38ae8ce4688dfc38 6292 
perl_5.34.0-5_source.buildinfo
Files:
 9030fd402247acfae676f801d56f8db8 2886 perl standard perl_5.34.0-5.dsc
 ed5a39732a75a88b224cc284b2f26041 167484 perl standard 
perl_5.34.0-5.debian.tar.xz
 7e5091acccddb8166e8c4bd799c03f2d 6292 perl standard 
perl_5.34.0-5_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEEdqKOQsmBHZHoj7peLsD/s7cwGx8FAmLDPnIRHG50eW5pQGRl
Ymlhbi5vcmcACgkQLsD/s7cwGx80fhAAgdJ8kBkqpSV6kbVwmAQR6nO/ZdH4IDPC
QfrwyO1m71s1j43aKN7OaROdiCzdH/YOUbHCCB0okHejnz6V5Pp5ug6bTgFpaxl+
NHCYM7kaGzUfhL81Xd/+IzXIGtv/u9D45h2Ag7tYEUQnqlun2toVHjAA1JRT7tVu
srvaiwv59EOqMEdytVXMiVFDYn2Jsh0i7bQeliWmPniK0wZhvaH+EZDS5DQAbska
KNyAb4be/ID/qq9r1tb1SvktJp8y0B5lhYvac+sr/X91plZCwpbG3cl3L5hSxnzc
rMJm79pT2v0bemy6s4TKicWDBx7kB0//vcv8nEJLTrchh8+0ljaDH4KcfEqgaXhs
tnLqJcXPQxJif0LiwijvuBNCWUuYFyBt+erpro9ysm1Ii6Y8WQFm3FP7n+b6Bz0x
N8GbsY5T3UljoZ0DDGBSIHKMeA7dXR+lW0bBfnBGf7McBCkuIICnsFP/+9N3PUJw
SUXQSycOGFlzrpddj6brANOXnjbQYhNyhdadMYLT3EoSL/Bedf85zflu9NctYpSB
ml/x0xzgahRHNJQ2i0ULxeo90cLsFNDqZv0vU3lSb4dLEkBnTOkJ7kJKF6nrj9Du
tADdMObY5oNHEWrOGv2CQeR38ugzV8Uh+riYy+7scG2UlNxpL5UL4ykgqsXpeQL5
uPNZndRwi90=
=o0YM
-END PGP SIGNATURE End Message ---

Bug#1013720: marked as done (python-matrix-nio: FTBFS: pytest7 regression, deprecated pytest feature: -k-)

[Debian Bug Tracking System]

Your message dated Mon, 04 Jul 2022 21:13:58 +
with message-id 
and subject line Bug#1013720: fixed in python-matrix-nio 0.19.0-4
has caused the Debian Bug report #1013720,
regarding python-matrix-nio: FTBFS: pytest7 regression, deprecated pytest 
feature: -k-
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.)


-- 
1013720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013720
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-matrix-nio
Version: 0.19.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-pyt...@lists.debian.org
Usertags: pytest7

Hi,

During a selected rebuild of python packages in sid, your package failed
to build with pytest version 7.1.2-1.

The full build log is available from:
http://qa-logs.debian.net/2022/06/09/pytest/python-matrix-nio_0.19.0-2_unstable_pytest-exp.log

I had a closer look at the error log and identified the regression as:
'deprecated pytest feature: -k-'. Hopefully, that's helpful!

All bugs filed during this rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=pytest7;users=debian-pyt...@lists.debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=pytest7=debian-pyt...@lists.debian.org=1=1=1=1#results

If you reassign this bug to another package, please mark 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 the one provided so that we can identify if something relevant
changed in the meantime.

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: python-matrix-nio
Source-Version: 0.19.0-4
Done: Jochen Sprickerhof 

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

Debian distribution maintenance software
pp.
Jochen Sprickerhof  (supplier of updated python-matrix-nio 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 04 Jul 2022 22:31:24 +0200
Source: python-matrix-nio
Architecture: source
Version: 0.19.0-4
Distribution: unstable
Urgency: medium
Maintainer: Matrix Packaging Team 

Changed-By: Jochen Sprickerhof 
Closes: 1013373 1013720
Changes:
 python-matrix-nio (0.19.0-4) unstable; urgency=medium
 .
   * Fx pytest exclude syntax (Closes: #1013720)
   * drop Built-Using from arch-all (according to lintian)
   * Fix capitalization (according to lintian)
   * Bump policy version (no changes)
   * Drop dependencies fulfilled by ${python3:Depends}
   * Adopt package.
 Thanks to Jonas for maintaining it (Closes: #1013373)
Checksums-Sha1:
 a03057c545605bc897a9daec53d289c9af9801f7 3060 python-matrix-nio_0.19.0-4.dsc
 b9e9388e63f7763f12c130f01eaf0c5530903a4c 8104 
python-matrix-nio_0.19.0-4.debian.tar.xz
 09c08fa0c689dd1dd6a05d932c98dcc2b7216b60 10340 
python-matrix-nio_0.19.0-4_source.buildinfo
Checksums-Sha256:
 2c9db6cb51512c7dab8fb5df97d31be8cc5e932491dcd67bf4f9931d9d675efb 3060 
python-matrix-nio_0.19.0-4.dsc
 abccca6caeef48a0d561ad7e5894e1bbb264c1f1e7979fc2826218a25aee00fc 8104 
python-matrix-nio_0.19.0-4.debian.tar.xz
 541a6c4ebc6733b037f26204caebde06f3b7605c7f9843c39402ac665f1b8a56 10340 
python-matrix-nio_0.19.0-4_source.buildinfo
Files:
 2f96636a3f5259ca019e631c7de476d7 3060 python optional 
python-matrix-nio_0.19.0-4.dsc
 0e43ba919e97d233f9748ab9d843eafd 8104 python optional 
python-matrix-nio_0.19.0-4.debian.tar.xz
 985aab642669f412720d06c5a81a0585 10340 python optional 
python-matrix-nio_0.19.0-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAmLDTlAACgkQW//cwljm
lDMPkA//UgkO3DHc2W+s06QmGwMpA/wpPl2S5gzAtpx08C5J6GE+7Pr3Cvwa3AkC
FnhWojp6wywtz0MNH807/IJLxLn9ryVErYzKqj9Ms+so/bk03tNJC/nYKmhANfvy
xQcgfy2R9v7yBQGl3VtcTgTCKmSZVotlEsq9qvLNxlaWPfE9bQyNZCwfrkVZMU0+
uXwfqMVto6q0R7/Pm7y84SbHKFOt0T1WP5E7h4vtz329Dp5a3W72Bshhb4bnuwrs

Bug#1013238: marked as done (src:pyspread: fails to migrate to testing for too long: uploader built arch:all binary)

[Debian Bug Tracking System]

Your message dated Mon, 04 Jul 2022 21:13:51 +
with message-id 
and subject line Bug#1013238: fixed in pyspread 2.1-2.1
has caused the Debian Bug report #1013238,
regarding src:pyspread: fails to migrate to testing for too long: uploader 
built arch:all binary
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.)


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

Source: pyspread
Version: 2.0.1-1
Severity: serious
Control: close -1 2.1-2
Tags: sid bookworm pending
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:pyspread has been trying to migrate for 61 
days [2]. Hence, I am filing this bug.


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


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


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


Your package is only blocked because the arch:all binary package(s) 
aren't built on a buildd. Unfortunately the Debian infrastructure 
doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will 
shortly do a no-changes source-only upload to DELAYED/15, closing this 
bug. Please let me know if I should delay or cancel that upload.


Paul

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



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: pyspread
Source-Version: 2.1-2.1
Done: Paul Gevers 

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 19 Jun 2022 20:45:55 +0200
Source: pyspread
Architecture: source
Version: 2.1-2.1
Distribution: unstable
Urgency: medium
Maintainer: Andreas Noteng 
Changed-By: Paul Gevers 
Closes: 1013238
Changes:
 pyspread (2.1-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * source only upload to enable migration (Closes: #1013238)
Checksums-Sha1:
 a3c7c638178f7e34c17fc0f1382b298f0ed1086a 2025 pyspread_2.1-2.1.dsc
 baa79e0d604510e7a29652e9c590f5aadbc440a9 12048 pyspread_2.1-2.1.debian.tar.xz
Checksums-Sha256:
 92d85788df994e402e9100690c7b46936c0a25af9e1bb691b995bbb470ecf0f0 2025 
pyspread_2.1-2.1.dsc
 1a71271175c5675d0554047d8aebbda753cd6e1584d97b36ca6f87bb96c6210a 12048 
pyspread_2.1-2.1.debian.tar.xz
Files:
 c192bff873082aecc571c90483db29de 2025 python optional pyspread_2.1-2.1.dsc
 4948e88dad4cbbf8211f7179aab3151f 12048 python optional 
pyspread_2.1-2.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmKvbwsACgkQnFyZ6wW9
dQpDkAf+JLfAwIhqgUO7xWqMRMpqfqbmcvnglU2nF7GTyfFTWW9HETGVBfHEKu8Q
gSiuasb7TAG+z3FFWBHEyxZVConGiyOZWaEg84gqsV97Pe0ggDw6/Q8C3xBCV8Bn
ak/pyvIpp47A9nyEZUDP7AcScfWchrAWDtz1PwCO1m6TG9KDmBNYk2VdVmDtKfzm
T6vlcV0ALK3R5ES8sdvIMGv7Bg3yqYRuDODzzAci7brnZ15S2LVmvbDCwx88rboN
5xWw+kOOYtbzKHHgKOOoNBUN4WcqweuFRwShjVrOD1YctU/W8sTpjiyUDTfafgUM
aPqH+tFMR/EmDliZt9vbG+7T5w56PQ==
=7l5N
-END PGP SIGNATURE End 

Bug#1012741: modprobe: ERROR: could not insert 'crc_itu_t': Key was rejected by service

[Ansgar]

Hi,

On Mon, 2022-07-04 at 22:00 +0200, Ansgar wrote:
> The correct signature (using OpenSSL) has:
> 
> +---
> > 138 256:   OCTET STRING
> >    : 00 00 45 75 A8 93 B1 B1 37 0A 53 69 82 BB 1C B6
> +---[ data.ko.p7s.success ]
> 
> The incorrect signature from the YK has:
> 
> +---
> > 138 254:   OCTET STRING
> >    : 82 45 75 A8 93 B1 B1 37 0A 53 69 82 BB 1C B6 E7
> +---[ data.ko.p7s.fail ]
> 
> So there is also a wrong byte at the beginning.
> The incorrect signature also misses one byte at the end.

As a further test I tried a different PKCS#11 module:

Modify reproduce.sh and set

+---
| 
pkcs11_uri="pkcs11:token=Test%20Key;manufacturer=piv_II;model=PKCS%2315%20emulated"
| export PKCS11_MODULE_PATH=/usr/lib/x86_64-linux-gnu/opensc-pkcs11.so
+---

This results in yet a different error:

+---
| 138 256:   OCTET STRING
|: 00 00 82 45 75 A8 93 B1 B1 37 0A 53 69 82 BB 1C
+---

The total size is correct, but it includes one incorrect byte at the
beginning (byte #3, 0x82) and the last byte is missing.

I've attached this signature as well.

Ansgar




data.ko.p7s.fail-opensc
Description: Binary data

Bug#1014358: src:why3: fails to migrate to testing for too long: blocked by dependency

[Paul Gevers]

Source: why3
Version: 1.4.1-2
Severity: serious
Control: close -1 1.5.0-1
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:why3 has been trying to migrate for 62 
days [2]. Hence, I am filing this bug. why3 is waiting for menhir to 
migrate, which is waiting for js-of-ocaml to migrate, which can't 
migrate because ocaml-logs somehow isn't in the right state (I don't 
understand how ocaml packaging works).


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=why3



OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:why3: fails to migrate to testing for too long: blocked by dependency

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.5.0-1
Bug #1014358 [src:why3] src:why3: fails to migrate to testing for too long: 
blocked by dependency
Marked as fixed in versions why3/1.5.0-1.
Bug #1014358 [src:why3] src:why3: fails to migrate to testing for too long: 
blocked by dependency
Marked Bug as done

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

Bug#1012741: modprobe: ERROR: could not insert 'crc_itu_t': Key was rejected by service

[Ansgar]

Hi,

I experimented a bit more and could reproduce the problem with a local
YK (Yubikey 4, Firmware 4.3.7) and a known private key and certificate.

The correct signature (using OpenSSL) has:

+---
| 138 256:   OCTET STRING
|: 00 00 45 75 A8 93 B1 B1 37 0A 53 69 82 BB 1C B6
+---[ data.ko.p7s.success ]

The incorrect signature from the YK has:

+---
| 138 254:   OCTET STRING
|: 82 45 75 A8 93 B1 B1 37 0A 53 69 82 BB 1C B6 E7
+---[ data.ko.p7s.fail ]

So there is also a wrong byte at the beginning.
The incorrect signature also misses one byte at the end.

The attached archive contains:

 - data.ko: random data to be signed
 - data.ko.p7s.fail: incorrect signature generated by YK4
 - data.ko.p7s.success: correct signature generated by OpenSSL
 - reproduce.sh: sign with YK4 (set serial# in the first lines)
 - reproduce2.sh: sign with OpenSSL
 - sign-file: make this a symlink to linux' sign-file
 - test.key: private key
 - test.pem: self-signed certificate

The test.{key,pem} need to be loaded in the Digital Signature (Slot 9c)
slot of the PIV application.

I haven't checked if this is reproducible with another YK with the same
data/key/cert, but it is reproducible with the same key.

Ansgar



ykcs11-signature-failure.tar.gz
Description: application/compressed-tar

Bug#1013700: Strangely rare pytest 7.x bug report

[Carles Pina i Estany]

Hi Julian,

On Jul/04/2022, Julian Gilbey wrote:
> Hi Carles,
> 
> Thanks for your thoughts!  Yes, indeed that seems to be the issue.
> But what I don't understand is why the import is turned into
> .pybuild.cpython3_3.9_qtpy.build.qtpy.tests and not just qtpy.tests or

I see how pytest does it (but keep reading)

> a longer path, and why only this package fails in this way.  Perhaps
> this is the only package that has an import statement in
> pytest_configure?

This I don't know and I'm curious, and it might help disecting the issue
(or understanding it). Do you know of any other python3 package that you
expected to fail? (using pytest in a similar way).

I might try to get both and follow what they do different (to hopefully
know what is python-qtpy doing different :-) )

I'm sure that there are tons of packages that use pytest :-) I'm
wondering if you had a good candidate.

Best regards,

> 
> Best wishes,
> 
>Julian
> 
> On Mon, Jul 04, 2022 at 04:03:39PM +0100, Carles Pina i Estany wrote:
> > 
> > Hi,
> > 
> > I'm a lurker of debian-pyt...@lists.debian.org but seeing Python+Qt I
> > wanted to have a look. I don't have a solution (I might look more
> > another time if time permits) but I might have something that might help
> > someone who knows the tools better.
> > 
> > I am not familiar with Python Debian packaging details/tools neither
> > with pytest :-( so take all of this with a pinch of salt.
> > 
> > If it helps the error comes from:
> > /usr/lib/python3.9/importlib/__init__.py in the functin "import_modules"
> > it does:
> > """
> > if name.startswith('.'):
> > if not package:
> > msg = ("the 'package' argument is required to perform a 
> > relative "
> >"import for {!r}")
> > raise TypeError(msg.format(name))
> > """
> > 
> > When the import fails the "name" parameter of "import_modules" function
> > is: '.pybuild.cpython3_3.9_qtpy.build.qtpy.tests' , which is derived
> > from the hidden dirctory ".pybuild" as created by default by "pybuild".
> > 
> > I think that the initial "." is used only as a directory name but Python
> > assumes that is a relative import requiring the package parameter.
> > 
> > Just to check my thoughts, and after running dpkg-buildpackage and
> > failing let's try again:
> > 
> > $ cd .pybuild/cpython3_3.9_qtpy/build; python3.9 -m pytest qtpy/tests ; cd -
> > Fails with the:
> > 
> > TypeError: the 'package' argument is required to perform a relative import 
> > for '.pybuild.cpython3_3.9_qtpy.build.qtpy.tests'
> > /home/carles/git/python-qtpy
> > 
> > Then let's try to avoid the initial "." confusion:
> > 
> > $ mv .pybuild pybuild
> > $ cd pybuild/cpython3_3.9_qtpy/build; python3.9 -m pytest qtpy/tests ; cd -
> > 
> > It works.
> > 
> > I don't know why this is the only package affected by this though...
> > 
> > Hopefully it helps a bit!
> > 
> > On Jul/04/2022, Julian Gilbey wrote:
> > > Dear all,
> > > 
> > > I wonder whether you might have any clue about
> > > https://bugs.debian.org/1013700
> > > I have mostly worked out the "cause" of the bug, but I haven't quite
> > > got to the bottom of it.
> > > 
> > > When running the command
> > > PYTHONPATH=. python3.10 -m pytest qtpy/tests
> > > in the directory .pybuild/cpython3_3.10_qtpy/build, I get the error
> > > message:
> > > 
> > > ImportError while loading conftest 
> > > '/home/jdg/debian/spyder-packages/qtpy/build-area/python-qtpy-2.1.0/.pybuild/cpython3_3.10_qtpy/build/qtpy/tests/conftest.py'.
> > > TypeError: the 'package' argument is required to perform a relative 
> > > import for '.pybuild.cpython3_3.10_qtpy.build.qtpy.tests'
> > > 
> > > If the directory .pybuild is renamed to pybuild, the tests run without
> > > a problem.  So there seems to be something funny about conftest.py
> > > (and removing all of the other files from the qtpy/tests directory
> > > except for the empty __init__.py gives the same error); here's a link
> > > to it:
> > > 
> > > https://salsa.debian.org/python-team/packages/python-qtpy/-/blob/master/qtpy/tests/conftest.py
> > > 
> > > But there doesn't seem to be anything out of the ordinary about this.
> > > So I am mystified: why does pytest 7.x seem to not give this error on
> > > any other Debian package?
> > > 
> > > The only solution I currently have for this package is skip the tests
> > > at build time and rely on autopkgtest to do them.
> > > 
> > > Best wishes,
> > > 
> > >Julian
-- 
Carles Pina i Estany
https://carles.pina.cat

Bug#1014114: installation of crypt.h in the multiarch location breaks the GCC and LLVM multilib builds

[Helmut Grohne]

Hi,

On Thu, Jun 30, 2022 at 05:15:32PM +0200, Helmut Grohne wrote:
> > > For libsanitizer, crypt.h is needed to determine the size of a struct, the
> > > library itself is not needed.  Moving it to the MA location makes it
> > > unavailable for the non-multilib builds.
> 
> Again, the lack of precision is not constructive. Linking to a failure
> would help a lot here.

I now understand that the libsanitizer aspect is separate to the
multilib aspect. Therefore, my proposed solution is a non-solution and
adding multilib packages is a non-solution as well. It is way worse and
completely messed up.

A gcc build (cross compiler stage3 or native) requires a target
architecture crypt.h. Trying to do without breaks libsanitizer (no
multilib involved). Example from
https://jenkins.debian.net/job/rebootstrap_ppc64_gcc12_nobiarch/5/consoleText

| /bin/bash ../libtool  --tag=CXX   --mode=compile 
/tmp/buildd/gcc3/gcc-12-12.1.0/build/./gcc/xgcc -shared-libgcc 
-B/tmp/buildd/gcc3/gcc-12-12.1.0/build/./gcc -nostdinc++ 
-L/tmp/buildd/gcc3/gcc-12-12.1.0/build/powerpc64-linux-gnu/libstdc++-v3/src 
-L/tmp/buildd/gcc3/gcc-12-12.1.0/build/powerpc64-linux-gnu/libstdc++-v3/src/.libs
 
-L/tmp/buildd/gcc3/gcc-12-12.1.0/build/powerpc64-linux-gnu/libstdc++-v3/libsupc++/.libs
 -B/usr/powerpc64-linux-gnu/bin/ -B/usr/powerpc64-linux-gnu/lib/ -isystem 
/usr/powerpc64-linux-gnu/include -isystem /usr/powerpc64-linux-gnu/sys-include 
-isystem /tmp/buildd/gcc3/gcc-12-12.1.0/build/sys-include-D_GNU_SOURCE 
-D_DEBUG -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS  
-DHAVE_RPC_XDR_H=0 -DHAVE_TIRPC_RPC_XDR_H=0 -I. 
-I../../../../src/libsanitizer/sanitizer_common -I..  -I 
../../../../src/libsanitizer/include -I ../../../../src/libsanitizer -isystem 
../../../../src/libsanitizer/include/system  -Wall -W -Wno-unused-parameter 
-Wwrite-strings -pedantic -Wno-long-long -fPIC -fno-builtin -fno-exceptions 
-fno-rtti -fomit-frame-pointer -funwind-tables -fvisibility=hidden 
-Wno-variadic-macros -I../../libstdc++-v3/include 
-I../../libstdc++-v3/include/powerpc64-linux-gnu 
-I../../../../src/libsanitizer/../libstdc++-v3/libsupc++ -std=gnu++14  
-DSANITIZER_LIBBACKTRACE -DSANITIZER_CP_DEMANGLE -I 
../../../../src/libsanitizer/../libbacktrace -I ../libbacktrace -I 
../../../../src/libsanitizer/../include -include 
../../../../src/libsanitizer/libbacktrace/backtrace-rename.h -g -O2 
-D_GNU_SOURCE -MT sanitizer_platform_limits_posix.lo -MD -MP -MF 
.deps/sanitizer_platform_limits_posix.Tpo -c -o 
sanitizer_platform_limits_posix.lo 
../../../../src/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cpp
| libtool: compile:  /tmp/buildd/gcc3/gcc-12-12.1.0/build/./gcc/xgcc 
-shared-libgcc -B/tmp/buildd/gcc3/gcc-12-12.1.0/build/./gcc -nostdinc++ 
-L/tmp/buildd/gcc3/gcc-12-12.1.0/build/powerpc64-linux-gnu/libstdc++-v3/src 
-L/tmp/buildd/gcc3/gcc-12-12.1.0/build/powerpc64-linux-gnu/libstdc++-v3/src/.libs
 
-L/tmp/buildd/gcc3/gcc-12-12.1.0/build/powerpc64-linux-gnu/libstdc++-v3/libsupc++/.libs
 -B/usr/powerpc64-linux-gnu/bin/ -B/usr/powerpc64-linux-gnu/lib/ -isystem 
/usr/powerpc64-linux-gnu/include -isystem /usr/powerpc64-linux-gnu/sys-include 
-isystem /tmp/buildd/gcc3/gcc-12-12.1.0/build/sys-include -D_GNU_SOURCE 
-D_DEBUG -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS 
-DHAVE_RPC_XDR_H=0 -DHAVE_TIRPC_RPC_XDR_H=0 -I. 
-I../../../../src/libsanitizer/sanitizer_common -I.. -I 
../../../../src/libsanitizer/include -I ../../../../src/libsanitizer -isystem 
../../../../src/libsanitizer/include/system -Wall -W -Wno-unused-parameter 
-Wwrite-strings -pedantic -Wno-long-long -fPIC -fno-builtin -fno-exceptions 
-fno-rtti -fomit-frame-pointer -funwind-tables -fvisibility=hidden 
-Wno-variadic-macros -I../../libstdc++-v3/include 
-I../../libstdc++-v3/include/powerpc64-linux-gnu 
-I../../../../src/libsanitizer/../libstdc++-v3/libsupc++ -std=gnu++14 
-DSANITIZER_LIBBACKTRACE -DSANITIZER_CP_DEMANGLE -I 
../../../../src/libsanitizer/../libbacktrace -I ../libbacktrace -I 
../../../../src/libsanitizer/../include -include 
../../../../src/libsanitizer/libbacktrace/backtrace-rename.h -g -O2 
-D_GNU_SOURCE -MT sanitizer_platform_limits_posix.lo -MD -MP -MF 
.deps/sanitizer_platform_limits_posix.Tpo -c 
../../../../src/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cpp
  -fPIC -DPIC -o .libs/sanitizer_platform_limits_posix.o
| 
../../../../src/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cpp:155:10:
 fatal error: crypt.h: No such file or directory
|   155 | #include 
|   |  ^
| compilation terminated.
| make[6]: *** [Makefile:616: sanitizer_platform_limits_posix.lo] Error 1
| make[6]: Leaving directory 
'/tmp/buildd/gcc3/gcc-12-12.1.0/build/powerpc64-linux-gnu/libsanitizer/sanitizer_common'
| make[5]: *** [Makefile:533: all-recursive] Error 1
| make[5]: Leaving directory 
'/tmp/buildd/gcc3/gcc-12-12.1.0/build/powerpc64-linux-gnu/libsanitizer'
| make[4]: *** 

Bug#1013700: Strangely rare pytest 7.x bug report

[Julian Gilbey]

Hi Carles,

Thanks for your thoughts!  Yes, indeed that seems to be the issue.
But what I don't understand is why the import is turned into
.pybuild.cpython3_3.9_qtpy.build.qtpy.tests and not just qtpy.tests or
a longer path, and why only this package fails in this way.  Perhaps
this is the only package that has an import statement in
pytest_configure?

Best wishes,

   Julian

On Mon, Jul 04, 2022 at 04:03:39PM +0100, Carles Pina i Estany wrote:
> 
> Hi,
> 
> I'm a lurker of debian-pyt...@lists.debian.org but seeing Python+Qt I
> wanted to have a look. I don't have a solution (I might look more
> another time if time permits) but I might have something that might help
> someone who knows the tools better.
> 
> I am not familiar with Python Debian packaging details/tools neither
> with pytest :-( so take all of this with a pinch of salt.
> 
> If it helps the error comes from:
> /usr/lib/python3.9/importlib/__init__.py in the functin "import_modules"
> it does:
> """
> if name.startswith('.'):
> if not package:
> msg = ("the 'package' argument is required to perform a relative "
>"import for {!r}")
> raise TypeError(msg.format(name))
> """
> 
> When the import fails the "name" parameter of "import_modules" function
> is: '.pybuild.cpython3_3.9_qtpy.build.qtpy.tests' , which is derived
> from the hidden dirctory ".pybuild" as created by default by "pybuild".
> 
> I think that the initial "." is used only as a directory name but Python
> assumes that is a relative import requiring the package parameter.
> 
> Just to check my thoughts, and after running dpkg-buildpackage and
> failing let's try again:
> 
> $ cd .pybuild/cpython3_3.9_qtpy/build; python3.9 -m pytest qtpy/tests ; cd -
> Fails with the:
> 
> TypeError: the 'package' argument is required to perform a relative import 
> for '.pybuild.cpython3_3.9_qtpy.build.qtpy.tests'
> /home/carles/git/python-qtpy
> 
> Then let's try to avoid the initial "." confusion:
> 
> $ mv .pybuild pybuild
> $ cd pybuild/cpython3_3.9_qtpy/build; python3.9 -m pytest qtpy/tests ; cd -
> 
> It works.
> 
> I don't know why this is the only package affected by this though...
> 
> Hopefully it helps a bit!
> 
> On Jul/04/2022, Julian Gilbey wrote:
> > Dear all,
> > 
> > I wonder whether you might have any clue about
> > https://bugs.debian.org/1013700
> > I have mostly worked out the "cause" of the bug, but I haven't quite
> > got to the bottom of it.
> > 
> > When running the command
> > PYTHONPATH=. python3.10 -m pytest qtpy/tests
> > in the directory .pybuild/cpython3_3.10_qtpy/build, I get the error
> > message:
> > 
> > ImportError while loading conftest 
> > '/home/jdg/debian/spyder-packages/qtpy/build-area/python-qtpy-2.1.0/.pybuild/cpython3_3.10_qtpy/build/qtpy/tests/conftest.py'.
> > TypeError: the 'package' argument is required to perform a relative import 
> > for '.pybuild.cpython3_3.10_qtpy.build.qtpy.tests'
> > 
> > If the directory .pybuild is renamed to pybuild, the tests run without
> > a problem.  So there seems to be something funny about conftest.py
> > (and removing all of the other files from the qtpy/tests directory
> > except for the empty __init__.py gives the same error); here's a link
> > to it:
> > 
> > https://salsa.debian.org/python-team/packages/python-qtpy/-/blob/master/qtpy/tests/conftest.py
> > 
> > But there doesn't seem to be anything out of the ordinary about this.
> > So I am mystified: why does pytest 7.x seem to not give this error on
> > any other Debian package?
> > 
> > The only solution I currently have for this package is skip the tests
> > at build time and rely on autopkgtest to do them.
> > 
> > Best wishes,
> > 
> >Julian

Bug#1014314: marked as done (lvm2: Missing 69-lvm-metad.rules causes lvm2 initramfs-tools hook to fail)

[Debian Bug Tracking System]

Your message dated Mon, 04 Jul 2022 18:34:08 +
with message-id 
and subject line Bug#1014314: fixed in lvm2 2.03.15-2
has caused the Debian Bug report #1014314,
regarding lvm2: Missing 69-lvm-metad.rules causes lvm2 initramfs-tools hook to 
fail
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.)


-- 
1014314: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014314
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lvm2
Version: 2.03.15-1
Severity: serious
Justification: fails to upgrade (not exactly, but fails to update initramfs due 
to failing lvm2 hook)
X-Debbugs-Cc: car...@debian.org

Hi

Updating lvm2 (and related packages) from 2.03.11-2.1 to 2.03.15-1
causes the lvm2 initramfs-tools hook
/usr/share/initramfs-tools/hooks/lvm2 to exit with 1.

Calling hook lvm2
+ PREREQ=
+ . /usr/share/initramfs-tools/hook-functions
+ cp -a /etc/lvm/ /var/tmp/mkinitramfs_WUGPmN/etc/lvm/
+ mkdir -p /var/tmp/mkinitramfs_WUGPmN/lib/udev/rules.d/
+ [ -e /etc/udev/rules.d/56-lvm.rules ]
+ [ -e /lib/udev/rules.d/56-lvm.rules ]
+ cp -p /lib/udev/rules.d/56-lvm.rules 
/var/tmp/mkinitramfs_WUGPmN/lib/udev/rules.d/
+ [ -e /etc/udev/rules.d/69-lvm-metad.rules ]
+ [ -e /lib/udev/rules.d/69-lvm-metad.rules ]
+ exit 1
E: /usr/share/initramfs-tools/hooks/lvm2 failed with return 1. 

/lib/udev/rules.d/69-lvm-metad.rules is not shipped anymore in the new
package:

Files in second .deb but not in first
-
-rw-r--r--  root/root   /lib/udev/rules.d/69-lvm.rules

Files in first .deb but not in second
-
-rw-r--r--  root/root   /lib/systemd/system/lvm2-pvscan@.service
-rw-r--r--  root/root   /lib/udev/rules.d/69-lvm-metad.rules
-rw-r--r--  root/root   /usr/share/man/man8/lvm2-activation-generator.8.gz
-rwxr-xr-x  root/root   /lib/systemd/system-generators/lvm2-activation-generator
-rwxr-xr-x  root/root   /usr/share/initramfs-tools/scripts/local-block/lvm2
-rwxr-xr-x  root/root   /usr/share/initramfs-tools/scripts/local-top/lvm2

Does the initramfs-tools hook need updating for the new installed udev
rules files?

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: lvm2
Source-Version: 2.03.15-2
Done: Bastian Blank 

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

Debian distribution maintenance software
pp.
Bastian Blank  (supplier of updated lvm2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 04 Jul 2022 20:11:20 +0200
Source: lvm2
Architecture: source
Version: 2.03.15-2
Distribution: unstable
Urgency: medium
Maintainer: Debian LVM Team 
Changed-By: Bastian Blank 
Closes: 1014314
Changes:
 lvm2 (2.03.15-2) unstable; urgency=medium
 .
   * Actually fix filename in lvm2 initamfs-tools integration, fixing
 installation error. (closes: #1014314)
Checksums-Sha1:
 982d0896ccb2b3a0d8c391ee0c01d0e7a3cf2950 2694 lvm2_2.03.15-2.dsc
 a96530327d4202632eb6de87cab4136c75bff903 131692 lvm2_2.03.15-2.debian.tar.xz
 ba2b53c1c574e55a84384d750026f77e30bbd21d 5653 lvm2_2.03.15-2_source.buildinfo
Checksums-Sha256:
 b7189694b00bd6ecbb6e8db468fdd9e8e10d824583a78a4761976fb5bbba1f93 2694 
lvm2_2.03.15-2.dsc
 6142af63748edfd87c9bce5246978fa28d0bd9a62dd9d4365cbb915577d7d0c1 131692 
lvm2_2.03.15-2.debian.tar.xz
 f08d4690e5011506f681fee82a64aba612d71a767509495eed78f7e18ba3ac5e 5653 
lvm2_2.03.15-2_source.buildinfo
Files:
 b45410745bf2987150f267c7c007fcaf 2694 admin optional lvm2_2.03.15-2.dsc
 41ff544e6a31a18c030d026e57be571a 131692 admin optional 
lvm2_2.03.15-2.debian.tar.xz
 3c2601263479f58d1374bc719835ae90 5653 admin optional 
lvm2_2.03.15-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEER3HMN63jdS1rqjxLbZOIhYpp/lEFAmLDLY8ACgkQbZOIhYpp
/lFlHgf+Og6wVi8zVGWcWIiuAeDqNCDrWk5RN1BkA8IlpS9skg59ffWZ09bc7EdL
y5gXnufR+f7Vg6NUlHNF/Wwbm2LHlA5KFPEgU81XHU4G39P1tWtdsixx/aFesUwE
EiXMHONzxErYupblzELBdRsheufPCIHAEhqglaIms2EfCVAvZPfrVWGsTySNvbxP
zCK5WpLvJd7VHRq1CWOaaDolGFu2VF5vmNOVjrHJwwi0VqzGhzfOl1kvruOQnhAY

Bug#1014351: hiredis: FTBFS test.c:151: send_hello: Assertion `reply != NULL && reply->type == expected' failed.

[Andreas Beckmann]

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

Hi,

hiredis/experimental recently started to FTBFS after some (transitive)
build-dependency got updated. The package in sid is not affected.

[...]
Testing against TCP connection (127.0.0.1:56379):
#48 Is able to deliver commands: ESC[0;32mPASSEDESC[0;0m
#49 Is a able to send commands verbatim: ESC[0;32mPASSEDESC[0;0m
#50 %s String interpolation works: ESC[0;32mPASSEDESC[0;0m
#51 %b String interpolation works: ESC[0;32mPASSEDESC[0;0m
#52 Binary reply length is correct: ESC[0;32mPASSEDESC[0;0m
#53 Can parse nil replies: ESC[0;32mPASSEDESC[0;0m
#54 Can parse integer replies: ESC[0;32mPASSEDESC[0;0m
#55 Can parse multi bulk replies: ESC[0;32mPASSEDESC[0;0m
#56 Can handle nested multi bulk replies: ESC[0;32mPASSEDESC[0;0m
#57 Can pass NULL to redisGetReply: ESC[0;32mPASSEDESC[0;0m
#58 RESP3 PUSH messages are handled out of band by default: 
ESC[0;32mPASSEDESC[0;0m
#59 We can set a custom RESP3 PUSH handler: ESC[0;31mFAILEDESC[0;0m
#60 With no handler, PUSH replies come in-band: ESC[0;32mPASSEDESC[0;0m
#61 With no PUSH handler, no replies are lost: ESC[0;31mFAILEDESC[hiredis-test: 
test.c:151: send_hello: Assertion `reply != NULL && reply->type == expected' 
failed.
Aborted
make[2]: *** [Makefile:224: check] Error 134
make[2]: Leaving directory '/build/hiredis-1.0.2'
make[1]: *** [debian/rules:30: override_dh_auto_test] Error 1
make[1]: Leaving directory '/build/hiredis-1.0.2'
make: *** [debian/rules:11: binary] Error 2


Andreas


hiredis_1.0.2-1.log.gz
Description: application/gzip

Processed: found 1011900 in 0.44-1

[Debian Bug Tracking System]

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

> found 1011900 0.44-1
Bug #1011900 [src:monkeysphere] monkeysphere: FTBFS: ...Could not chdir to home 
directory /home/user42: No such file or directory
Marked as found in versions monkeysphere/0.44-1.
> thanks
Stopping processing here.

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

Bug#1013643: marked as done (deal.ii: FTBFS: src.c:(.text.startup+0x15): undefined reference to `pthread_create')

[Debian Bug Tracking System]

Your message dated Mon, 04 Jul 2022 17:19:37 +
with message-id 
and subject line Bug#1011655: fixed in deal.ii 9.4.0-1
has caused the Debian Bug report #1011655,
regarding deal.ii: FTBFS: src.c:(.text.startup+0x15): undefined reference to 
`pthread_create'
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.)


-- 
1011655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011655
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: deal.ii
Version: 9.3.2-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220624 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> /usr/bin/ld: CMakeFiles/cmTC_dc95d.dir/src.c.o: in function `main':
> src.c:(.text.startup+0x15): undefined reference to `pthread_create'
> /usr/bin/ld: src.c:(.text.startup+0x1f): undefined reference to 
> `pthread_detach'
> /usr/bin/ld: src.c:(.text.startup+0x29): undefined reference to 
> `pthread_cancel'
> /usr/bin/ld: src.c:(.text.startup+0x35): undefined reference to `pthread_join'
> collect2: error: ld returned 1 exit status


The full build log is available from:
http://qa-logs.debian.net/2022/06/24/deal.ii_9.3.2-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220624;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220624=lu...@debian.org=1=1=1=1#results

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: deal.ii
Source-Version: 9.4.0-1
Done: Matthias Maier 

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

Debian distribution maintenance software
pp.
Matthias Maier  (supplier of updated deal.ii 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 04 Jul 2022 16:49:47 +
Source: deal.ii
Built-For-Profiles: noudeb
Architecture: source
Version: 9.4.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Matthias Maier 
Closes: 1011655
Changes:
 deal.ii (9.4.0-1) unstable; urgency=medium
 .
   [ Matthias Maier ]
   * New upstream release
 - support new OneAPI in TBB (Closes: #1011655)
   * Re-enable Sundials IDA quick test
 .
   [ Graham Inggs ]
   * Stop limiting to 2 parallel build jobs
   * Bump Standards-Version to 4.6.1, no changes
Checksums-Sha1:
 049f3a6c5401abd8551985b332f20059600b8997 2765 deal.ii_9.4.0-1.dsc
 ac3a80f994a3c98358412edae8fb730d755513d6 10484 deal.ii_9.4.0-1.debian.tar.xz
Checksums-Sha256:
 ba120313bb3cbecef53497c8fd84128c91bca142f8642698ba0972641b02d541 2765 
deal.ii_9.4.0-1.dsc
 e8ce8edcff650206f7087ad86822fda675495c5c346fc4d79d022f418c3aed91 10484 
deal.ii_9.4.0-1.debian.tar.xz
Files:
 5f5685cedfac81e5d15a6a415db6f865 2765 libs optional deal.ii_9.4.0-1.dsc
 606361ab2d497e5c7bd0097c653b6771 10484 libs optional 
deal.ii_9.4.0-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEJeP/LX9Gnb59DU5Qr8/sjmac4cIFAmLDG2kACgkQr8/sjmac
4cIq9Q/+MS5+SqJllKpZSm+y/a4mryBE/JppFR2fEQJpIs1ZDTbxyDf7HFaacxwW
HXyBgG2xAecNGLS1+gFSwNAuQDUeU2heM2ID5fZW8Gub4cr1dD2SqbgdlYjepk3U
wy7MWk50DlBWW2ATduDijezsRO3QLCN4nG3+6wATwyrLG71ToV1CqhN5raG0OzG5
KfWP/v57Ff5sqx3LfHjMDj1IwwJ0Uf8mzYsirE5jrZduYq91YihxOJj8c2ksXKnJ
2vHeLVqoZayXZ1FH+bQq1U0cBGGLlfAP7kTYMV4Cl9KLlVkovy0r+5BCuiEkiFhg
bdC+KH5Gw+yjpxj9Dff/ElHsFSmbdCyby39RQEvvWFaPQGobBKyzNQDHzu36mUFT
nQOe6Y3te3MQFfSVv/x4ay1Xc4Jf6PigTC3jRfw5iK04hhVFoi97+rEV5IeRjp2C
uJGau+t99RcuyupmQ63k4M9LaaxMMmRZRaWXAAH4tojevCBIO3oaCfSxVtcwXNR/

Bug#1011655: marked as done (deal.ii ftbfs against libtbb-dev/experimental, cmake could not find tbb)

[Debian Bug Tracking System]

Your message dated Mon, 04 Jul 2022 17:19:37 +
with message-id 
and subject line Bug#1011655: fixed in deal.ii 9.4.0-1
has caused the Debian Bug report #1011655,
regarding deal.ii ftbfs against libtbb-dev/experimental, cmake could not find 
tbb
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.)


-- 
1011655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011655
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: deal.ii
Version: 9.3.2-1
Severity: important

tbb -> onetbb transition breaks this package.
--- End Message ---
--- Begin Message ---
Source: deal.ii
Source-Version: 9.4.0-1
Done: Matthias Maier 

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

Debian distribution maintenance software
pp.
Matthias Maier  (supplier of updated deal.ii 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 04 Jul 2022 16:49:47 +
Source: deal.ii
Built-For-Profiles: noudeb
Architecture: source
Version: 9.4.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Matthias Maier 
Closes: 1011655
Changes:
 deal.ii (9.4.0-1) unstable; urgency=medium
 .
   [ Matthias Maier ]
   * New upstream release
 - support new OneAPI in TBB (Closes: #1011655)
   * Re-enable Sundials IDA quick test
 .
   [ Graham Inggs ]
   * Stop limiting to 2 parallel build jobs
   * Bump Standards-Version to 4.6.1, no changes
Checksums-Sha1:
 049f3a6c5401abd8551985b332f20059600b8997 2765 deal.ii_9.4.0-1.dsc
 ac3a80f994a3c98358412edae8fb730d755513d6 10484 deal.ii_9.4.0-1.debian.tar.xz
Checksums-Sha256:
 ba120313bb3cbecef53497c8fd84128c91bca142f8642698ba0972641b02d541 2765 
deal.ii_9.4.0-1.dsc
 e8ce8edcff650206f7087ad86822fda675495c5c346fc4d79d022f418c3aed91 10484 
deal.ii_9.4.0-1.debian.tar.xz
Files:
 5f5685cedfac81e5d15a6a415db6f865 2765 libs optional deal.ii_9.4.0-1.dsc
 606361ab2d497e5c7bd0097c653b6771 10484 libs optional 
deal.ii_9.4.0-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEJeP/LX9Gnb59DU5Qr8/sjmac4cIFAmLDG2kACgkQr8/sjmac
4cIq9Q/+MS5+SqJllKpZSm+y/a4mryBE/JppFR2fEQJpIs1ZDTbxyDf7HFaacxwW
HXyBgG2xAecNGLS1+gFSwNAuQDUeU2heM2ID5fZW8Gub4cr1dD2SqbgdlYjepk3U
wy7MWk50DlBWW2ATduDijezsRO3QLCN4nG3+6wATwyrLG71ToV1CqhN5raG0OzG5
KfWP/v57Ff5sqx3LfHjMDj1IwwJ0Uf8mzYsirE5jrZduYq91YihxOJj8c2ksXKnJ
2vHeLVqoZayXZ1FH+bQq1U0cBGGLlfAP7kTYMV4Cl9KLlVkovy0r+5BCuiEkiFhg
bdC+KH5Gw+yjpxj9Dff/ElHsFSmbdCyby39RQEvvWFaPQGobBKyzNQDHzu36mUFT
nQOe6Y3te3MQFfSVv/x4ay1Xc4Jf6PigTC3jRfw5iK04hhVFoi97+rEV5IeRjp2C
uJGau+t99RcuyupmQ63k4M9LaaxMMmRZRaWXAAH4tojevCBIO3oaCfSxVtcwXNR/
pyYA2DgQGOIB47c+6HCeQP06GTMergDwOCw8OTaf35xUZn8pJdRHVLxMtd+zy0xc
jK32kLCBdc4tAMFOTy2PhmYXljXp8c3/JHpdxefyWdxsnxr/oeddoUuJ64/3QCrF
wCiWvuxIJwWMjYY1UA3b6oCYUdUcw1X5kQ+Rq/EgkEkGfPZ5Vcg=
=GsQj
-END PGP SIGNATURE End Message ---

Bug#1012126: marked as done (deal.ii: FTBFS with onetbb/2021.5.0-9 in experimental)

[Debian Bug Tracking System]

Your message dated Mon, 04 Jul 2022 17:19:37 +
with message-id 
and subject line Bug#1011655: fixed in deal.ii 9.4.0-1
has caused the Debian Bug report #1011655,
regarding deal.ii: FTBFS with onetbb/2021.5.0-9 in experimental
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.)


-- 
1011655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011655
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: deal.ii
Version: 9.3.2-1
Severity: normal
Tags: ftbfs

Hello,

tbb/onetbb transition (#1007222) is currently in the planning. During
test rebuild of libtbb-dev reverse dependencies with onetbb/2021.5.0-9
in experimental, current source failed to build with the following:

-- Include /<>/cmake/configure/configure_1_tbb.cmake
-- Found TBB_LIBRARY
-- TBB_DEBUG_LIBRARY not found! The call was:
-- FIND_LIBRARY(TBB_DEBUG_LIBRARY NAMES tbb_debug HINTS
PATH_SUFFIXES lib lib64 lib)
-- TBB_INCLUDE_DIR not found! The call was:
-- FIND_PATH(TBB_INCLUDE_DIR tbb/tbb_stddef.h HINTS PATH_SUFFIXES
include include/tbb tbb)
--   TBB_LIBRARIES: /usr/lib/x86_64-linux-gnu/libtbb.so
--   TBB_INCLUDE_DIRS: *** Required variable "TBB_INCLUDE_DIR" set to
NOTFOUND ***
--   TBB_USER_INCLUDE_DIRS: *** Required variable "TBB_INCLUDE_DIR" set
to NOTFOUND ***
-- Could NOT find TBB
-- The externally provided TBB library is older than version 4.2.0,
which cannot be used with deal.II.
-- DEAL_II_WITH_TBB has unmet external dependencies.

Andrius
--- End Message ---
--- Begin Message ---
Source: deal.ii
Source-Version: 9.4.0-1
Done: Matthias Maier 

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

Debian distribution maintenance software
pp.
Matthias Maier  (supplier of updated deal.ii 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 04 Jul 2022 16:49:47 +
Source: deal.ii
Built-For-Profiles: noudeb
Architecture: source
Version: 9.4.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Matthias Maier 
Closes: 1011655
Changes:
 deal.ii (9.4.0-1) unstable; urgency=medium
 .
   [ Matthias Maier ]
   * New upstream release
 - support new OneAPI in TBB (Closes: #1011655)
   * Re-enable Sundials IDA quick test
 .
   [ Graham Inggs ]
   * Stop limiting to 2 parallel build jobs
   * Bump Standards-Version to 4.6.1, no changes
Checksums-Sha1:
 049f3a6c5401abd8551985b332f20059600b8997 2765 deal.ii_9.4.0-1.dsc
 ac3a80f994a3c98358412edae8fb730d755513d6 10484 deal.ii_9.4.0-1.debian.tar.xz
Checksums-Sha256:
 ba120313bb3cbecef53497c8fd84128c91bca142f8642698ba0972641b02d541 2765 
deal.ii_9.4.0-1.dsc
 e8ce8edcff650206f7087ad86822fda675495c5c346fc4d79d022f418c3aed91 10484 
deal.ii_9.4.0-1.debian.tar.xz
Files:
 5f5685cedfac81e5d15a6a415db6f865 2765 libs optional deal.ii_9.4.0-1.dsc
 606361ab2d497e5c7bd0097c653b6771 10484 libs optional 
deal.ii_9.4.0-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEJeP/LX9Gnb59DU5Qr8/sjmac4cIFAmLDG2kACgkQr8/sjmac
4cIq9Q/+MS5+SqJllKpZSm+y/a4mryBE/JppFR2fEQJpIs1ZDTbxyDf7HFaacxwW
HXyBgG2xAecNGLS1+gFSwNAuQDUeU2heM2ID5fZW8Gub4cr1dD2SqbgdlYjepk3U
wy7MWk50DlBWW2ATduDijezsRO3QLCN4nG3+6wATwyrLG71ToV1CqhN5raG0OzG5
KfWP/v57Ff5sqx3LfHjMDj1IwwJ0Uf8mzYsirE5jrZduYq91YihxOJj8c2ksXKnJ
2vHeLVqoZayXZ1FH+bQq1U0cBGGLlfAP7kTYMV4Cl9KLlVkovy0r+5BCuiEkiFhg
bdC+KH5Gw+yjpxj9Dff/ElHsFSmbdCyby39RQEvvWFaPQGobBKyzNQDHzu36mUFT
nQOe6Y3te3MQFfSVv/x4ay1Xc4Jf6PigTC3jRfw5iK04hhVFoi97+rEV5IeRjp2C
uJGau+t99RcuyupmQ63k4M9LaaxMMmRZRaWXAAH4tojevCBIO3oaCfSxVtcwXNR/
pyYA2DgQGOIB47c+6HCeQP06GTMergDwOCw8OTaf35xUZn8pJdRHVLxMtd+zy0xc
jK32kLCBdc4tAMFOTy2PhmYXljXp8c3/JHpdxefyWdxsnxr/oeddoUuJ64/3QCrF
wCiWvuxIJwWMjYY1UA3b6oCYUdUcw1X5kQ+Rq/EgkEkGfPZ5Vcg=
=GsQj
-END PGP SIGNATURE End Message ---

Bug#1012741: modprobe: ERROR: could not insert 'crc_itu_t': Key was rejected by service

[Ben Hutchings]

On Mon, 2022-07-04 at 14:04 +0200, Ansgar wrote:
> On Sun, 19 Jun 2022 12:59:55 +0200 Ben Hutchings wrote:
> > > I'm now looking at whether the missing bytes are recoverable (e.g. are
> > > they always zeroes).
> > [...]
> > 
> > I wrote a script to try all possible byte values for 2 bytes before or
> > after the short signature.  For this particular file, none of them
> > producd a valid signature.  So the short signatures seem to be
> > corrupted in a more complex way.
> 
> The "OCTET STRING" containing the actual signature is shorter for the
> seemingly corrupted signatures:
[...]

Yes I know, and my script uses a library to manipulate the ASN.1
structure when adding bytes.  I'm attaching the script, so you can
check the logic.

Ben.

-- 
Ben Hutchings
Any smoothly functioning technology is indistinguishable
from a rigged demo.
#!/usr/bin/python3

# Fix broken detached signatures

import os.path
import sys

import asn1crypto.algos
import asn1crypto.cms
import asn1crypto.core

from M2Crypto import BIO, SMIME, X509


# Signature algorithm should be RSA
SIG_ALGO_OID = asn1crypto.core.ObjectIdentifier('1.2.840.113549.1.1.1')


# Signature length should match key length (2048 bits)
SIG_LEN = 2048 // 8


def make_smime_context(cert):
# We don't verify against a CA, just one specific certificate
smime = SMIME.SMIME()
signer_key = X509.X509_Stack()
signer_key.push(X509.load_cert(cert))
smime.set_x509_stack(signer_key)
smime.set_x509_store(X509.X509_Store())
return smime


def verify_payload(smime, sig, data):
smime.verify(
SMIME.load_pkcs7_bio_der(BIO.MemoryBuffer(sig.dump(force=True))),
BIO.MemoryBuffer(data),
flags=(SMIME.PKCS7_BINARY | SMIME.PKCS7_DETACHED
   | SMIME.PKCS7_NOVERIFY))


def brute_force_sig_2bytes(smime, sig, sig_os, data):
orig_raw_sig = bytes(sig_os)
for byte1 in range(256):
for byte2 in range(256):
sig_os.set(bytes((byte1, byte2)) + orig_raw_sig)
try:
verify_payload(smime, sig, data)
except Exception:
pass
else:
print(f'prepended {byte1}, {byte2} to start of sig')
return True

sig_os.set(bytes((byte1,)) + orig_raw_sig + bytes((byte2,)))
try:
verify_payload(smime, sig, data)
except Exception:
pass
else:
print(f'added {byte1}, {byte2} at start and end of sig resp.')
return True

sig_os.set(orig_raw_sig + bytes((byte1, byte2)))
try:
verify_payload(smime, sig, data)
except Exception:
pass
else:
print(f'appended {byte1}, {byte2} to end of sig')
return True

return False


def fix_detached_sig(smime, sig, bin_name):
# The ContentInfo should be a SEQUENCE with signed data at index 1
if len(sig) < 2 or not isinstance(sig[1], asn1crypto.cms.SignedData):
return 'no signed data found', False
sd = sig[1]

# The SignedData should be a SEQUENCE with signer infos at index 5
if len(sd) < 6 or not isinstance(sd[5], asn1crypto.cms.SignerInfos):
return 'no signer infos found', False
infos = sd[5]

# The SignerInfos should be a SET with 1 item
if len(infos) != 1:
return f'found { len(infos) } signer infos; expected 1', False
info = infos[0]

# The SignerInfo should be a SEQUENCE with the signature algorithm
# at index 4 and signature at index 5
if (len(info) < 6
or not isinstance(info[4], asn1crypto.algos.SignedDigestAlgorithm)
or len(info[4]) < 1
or not isinstance(info[5], asn1crypto.core.OctetString)):
return 'expected fields not found in signer info', False

# Check the signature algorithm and length (see bug #1012741)
if info[4][0] != SIG_ALGO_OID:
return f'unexpected signature algorithm { info[4][0].dotted }', False
actual_sig_len = len(bytes(info[5]))

with open(bin_name, 'rb') as f:
data = f.read()

if (actual_sig_len == SIG_LEN - 2
and brute_force_sig_2bytes(smime, sig, info[5], bin_name)):
return (f'signature length is { actual_sig_len } bytes;'
f' expected { SIG_LEN }; filled in missing 2 bytes',
True)

if actual_sig_len != SIG_LEN:
return (f'signature length is { actual_sig_len } bytes;'
f' expected { SIG_LEN }',
False)

verify_payload(smime, sig, data)
return None, False


def load_detached_sig(name):
with open(name, 'rb') as f:
return asn1crypto.cms.ContentInfo.load(f.read())


def save_detached_sig(sig, name):
with open(name, 'wb') as f:
f.write(sig.dump())


def main(sig_dir, bin_dir, cert):
err_count = 0

smime = make_smime_context(cert)

for dirpath, dirnames, filenames in os.walk(sig_dir):
for 

Bug#1013700: Strangely rare pytest 7.x bug report

[Carles Pina i Estany]

Hi,

I'm a lurker of debian-pyt...@lists.debian.org but seeing Python+Qt I
wanted to have a look. I don't have a solution (I might look more
another time if time permits) but I might have something that might help
someone who knows the tools better.

I am not familiar with Python Debian packaging details/tools neither
with pytest :-( so take all of this with a pinch of salt.

If it helps the error comes from:
/usr/lib/python3.9/importlib/__init__.py in the functin "import_modules"
it does:
"""
if name.startswith('.'):
if not package:
msg = ("the 'package' argument is required to perform a relative "
   "import for {!r}")
raise TypeError(msg.format(name))
"""

When the import fails the "name" parameter of "import_modules" function
is: '.pybuild.cpython3_3.9_qtpy.build.qtpy.tests' , which is derived
from the hidden dirctory ".pybuild" as created by default by "pybuild".

I think that the initial "." is used only as a directory name but Python
assumes that is a relative import requiring the package parameter.

Just to check my thoughts, and after running dpkg-buildpackage and
failing let's try again:

$ cd .pybuild/cpython3_3.9_qtpy/build; python3.9 -m pytest qtpy/tests ; cd -
Fails with the:

TypeError: the 'package' argument is required to perform a relative import for 
'.pybuild.cpython3_3.9_qtpy.build.qtpy.tests'
/home/carles/git/python-qtpy

Then let's try to avoid the initial "." confusion:

$ mv .pybuild pybuild
$ cd pybuild/cpython3_3.9_qtpy/build; python3.9 -m pytest qtpy/tests ; cd -

It works.

I don't know why this is the only package affected by this though...

Hopefully it helps a bit!

On Jul/04/2022, Julian Gilbey wrote:
> Dear all,
> 
> I wonder whether you might have any clue about
> https://bugs.debian.org/1013700
> I have mostly worked out the "cause" of the bug, but I haven't quite
> got to the bottom of it.
> 
> When running the command
> PYTHONPATH=. python3.10 -m pytest qtpy/tests
> in the directory .pybuild/cpython3_3.10_qtpy/build, I get the error
> message:
> 
> ImportError while loading conftest 
> '/home/jdg/debian/spyder-packages/qtpy/build-area/python-qtpy-2.1.0/.pybuild/cpython3_3.10_qtpy/build/qtpy/tests/conftest.py'.
> TypeError: the 'package' argument is required to perform a relative import 
> for '.pybuild.cpython3_3.10_qtpy.build.qtpy.tests'
> 
> If the directory .pybuild is renamed to pybuild, the tests run without
> a problem.  So there seems to be something funny about conftest.py
> (and removing all of the other files from the qtpy/tests directory
> except for the empty __init__.py gives the same error); here's a link
> to it:
> 
> https://salsa.debian.org/python-team/packages/python-qtpy/-/blob/master/qtpy/tests/conftest.py
> 
> But there doesn't seem to be anything out of the ordinary about this.
> So I am mystified: why does pytest 7.x seem to not give this error on
> any other Debian package?
> 
> The only solution I currently have for this package is skip the tests
> at build time and rely on autopkgtest to do them.
> 
> Best wishes,
> 
>Julian
-- 
Carles Pina i Estany
https://carles.pina.cat

Bug#1013660: marked as done (apertium-spa-ita: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.7) were not met)

[Debian Bug Tracking System]

Your message dated Mon, 04 Jul 2022 15:04:56 +
with message-id 
and subject line Bug#1013660: fixed in apertium-spa-ita 0.2.1-3
has caused the Debian Bug report #1013660,
regarding apertium-spa-ita: FTBFS: configure: error: Package requirements 
(apertium-lex-tools >= 0.2.7) were not met
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.)


-- 
1013660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013660
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: apertium-spa-ita
Version: 0.2.1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220624 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> checking for gawk... (cached) gawk
> checking for pkg-config... /usr/bin/pkg-config
> checking pkg-config is at least version 0.9.0... yes
> checking for apertium >= 3.7.1... yes
> checking for apertium-lex-tools >= 0.2.7... no
> configure: error: Package requirements (apertium-lex-tools >= 0.2.7) were not 
> met
> 
> No package 'apertium-lex-tools' found
> 
> Consider adjusting the PKG_CONFIG_PATH environment variable if you
> installed software in a non-standard prefix.
> 
> Alternatively, you may set the environment variables APERTIUM_LEX_TOOLS_CFLAGS
> and APERTIUM_LEX_TOOLS_LIBS to avoid the need to call pkg-config.
> See the pkg-config man page for more details.
> make[1]: *** [debian/rules:17: override_dh_auto_configure] Error 1
> make[1]: Leaving directory '/<>'


The full build log is available from:
http://qa-logs.debian.net/2022/06/24/apertium-spa-ita_0.2.1-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220624;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220624=lu...@debian.org=1=1=1=1#results

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: apertium-spa-ita
Source-Version: 0.2.1-3
Done: Kartik Mistry 

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

Debian distribution maintenance software
pp.
Kartik Mistry  (supplier of updated apertium-spa-ita package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 04 Jul 2022 18:46:46 +0530
Source: apertium-spa-ita
Architecture: source
Version: 0.2.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Kartik Mistry 
Closes: 1013660
Changes:
 apertium-spa-ita (0.2.1-3) unstable; urgency=medium
 .
   * debian/control:
 + Fixed Build-Depends: apertium-lex-tools -> apertium-lex-tools-dev
   (Closes: #1013660)
 + Updated Standards-Version to 4.6.1
   * Updated debian/copyright.
   * Updated debian/watch.
Checksums-Sha1:
 5f64552e53fb48faba23add69d31b938b532faa1 2197 apertium-spa-ita_0.2.1-3.dsc
 546921ced679bf28dea24e28c4e129db54255f3a 2976 
apertium-spa-ita_0.2.1-3.debian.tar.xz
Checksums-Sha256:
 e17bbfadd959a51a02bfa0defac9b81d0e001987fdb8d2eab745e6d92a07ed65 2197 
apertium-spa-ita_0.2.1-3.dsc
 e00c4163a526e86c4a608d0ba8f52ba6d5b8f5b626d93ba3ab494b779a1f6742 2976 
apertium-spa-ita_0.2.1-3.debian.tar.xz
Files:
 82789807fd31e8c28f2a957744d4be1b 2197 science optional 
apertium-spa-ita_0.2.1-3.dsc
 e978e40f634e1c6c74a28048ac30234c 2976 science optional 
apertium-spa-ita_0.2.1-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEa2MbXvVUr2sRlmKSAsHT8ng6pN4FAmLC/MwACgkQAsHT8ng6
pN71og//SE75vfnWwZLz3metum9xJO/3duerwJuT5iLiJuqvvYf4352m9zHpRGjL

Processed: severity of 1014323 is grave

[Debian Bug Tracking System]

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

> severity 1014323 grave
Bug #1014323 [wine-binfmt] wine-binfmt: postinst fails due to incorrect import 
directory
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Bug#1014330: marked as done (highway: NEON and VFPv4 are not part of the armhf baseline)

[Debian Bug Tracking System]

Your message dated Mon, 04 Jul 2022 14:38:07 +
with message-id 
and subject line Bug#1014330: fixed in highway 0.17.0-7
has caused the Debian Bug report #1014330,
regarding highway: NEON and VFPv4 are not part of the armhf baseline
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.)


-- 
1014330: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014330
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: highway
Version: 0.17.0-6
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: Mathieu Malaterre 

NEON and VFPv4 are not part of the armhf baseline:
https://wiki.debian.org/ArchitectureSpecificsMemo#armhf

Plenty of hardware (inluding some of our buildds)
do not support NEON.

Plenty of hardware (inluding some of our buildds)
do not support VFPv4.
--- End Message ---
--- Begin Message ---
Source: highway
Source-Version: 0.17.0-7
Done: Mathieu Malaterre 

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

Debian distribution maintenance software
pp.
Mathieu Malaterre  (supplier of updated highway package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 04 Jul 2022 15:31:59 +0200
Source: highway
Architecture: source
Version: 0.17.0-7
Distribution: experimental
Urgency: medium
Maintainer: Debian PhotoTools Maintainers 

Changed-By: Mathieu Malaterre 
Closes: 1014330
Changes:
 highway (0.17.0-7) experimental; urgency=medium
 .
   * d/rules: Make sure to skip most rules for indep
   * d/rules: Shrink the main PDF file using gs
   * d/patches: Fix dynamic dispatch on linux/armhf. Closes: #1014330
Checksums-Sha1:
 ab29b09280d2606fc430a236dbf6ae1ff5f52b51 2152 highway_0.17.0-7.dsc
 2bb42f13f2ca2ce0d55c783746c5b1c20a074e35 10068 highway_0.17.0-7.debian.tar.xz
 8ca3455cec2e6e33d0ff1c127370081389a89b87 7187 highway_0.17.0-7_source.buildinfo
Checksums-Sha256:
 48de41a0939bc558b25855938807232ff56716cd0fb4d63fea7aa79333288b4d 2152 
highway_0.17.0-7.dsc
 0dcc6e45fd90a3bc4b31e516ba8ed4947d3f47932d7b18b4a169e3959502f70e 10068 
highway_0.17.0-7.debian.tar.xz
 0004db6e4e6d9e778f9c942a32c18f29c82a8790eae92d6b64d0dda2ec676706 7187 
highway_0.17.0-7_source.buildinfo
Files:
 0d749dbccc9b5bd2affc4de6a88ed715 2152 libs optional highway_0.17.0-7.dsc
 f0aa8e46d879404e55eff8cb11d3379e 10068 libs optional 
highway_0.17.0-7.debian.tar.xz
 388d284d933ad3c4a1c07b569d0f5ce6 7187 libs optional 
highway_0.17.0-7_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEaTNn/67NjqrNHwY7AXHhgorgk0UFAmLC8JcRHG1hbGF0QGRl
Ymlhbi5vcmcACgkQAXHhgorgk0VxlQ//foyDHM6ntuzaplGPpAJW2UgMzxdAJnGk
8yr0k9aKqaL7mKA1bIjU5kNmudZrcgX2ly89zukMXzDfy8An1cK081yjaK5vFK9b
D/kJpZHiCXNHkIiNjjAlJUKI47b1fBL1WmLQYV3JY/2kEftxcg2yxmfKiJ/hQuLj
PRhHe26MRrWQr+2xqyTYh7RT3xXysIYYOXcYQNKqfN+ctDGQtZ6XSzRCfyzQXy7C
H2La/r6hMAsqWIgo9cFEnKdth2RDgE8JfloVaJN0sh4FLTWLREEmMoyww9LhaX0L
Y5siDzu6ZtdJp+k/Gk67F6HIvKupbIG4VKwqxrT4TnE+FaUPWAtWoKFSb72Q8ib/
CTqPcGTVD6vRxTIAzhv/6dZ7Riwf4FY/9+ZR4+e9w6ejKD39d7ftRz71G9MT+7Ff
v2J8jUxbKVUhegRoAwjAV2lyOg3tZnrg/p4hyD8VeK0yTP7ZwrcZwn//7/VsBW+3
m9n3EzpW4k0HqesyadZkZ8vZNohLPYdvR0Mysep7HDbH3Y3UDOgYeyBsAT6bR2Ss
+pyT615ELA2kHEINlZE38vAVKxjIyzPNXX9gdtO0jDIT5Kh6cDIVknhXqL07cMQM
kK4n+qBFNBSbJTjS1GxqGBddXBYGU+hPJXaqgmSRt4XuHRp3m9F4Nh+5tTLwib9V
VBdfpB6CK4k=
=IL18
-END PGP SIGNATURE End Message ---

Bug#1014314: Workaround

[Damián Cinich]

It seems that the package lvm2 renamed:

- /lib/udev/rules.d/69-lvm-metad.rules

To:

- /lib/udev/rules.d/69-lvm.rules

I needed to copy the file manually to workaround the issue:

- cp -a /lib/udev/rules.d/69-lvm.rules /lib/udev/rules.d/69-lvm-metad.rules

Bug#1013419: marked as done (vcmi FTBFS with ffmpeg 5.0.1)

[Debian Bug Tracking System]

Your message dated Mon, 04 Jul 2022 13:34:43 +
with message-id 
and subject line Bug#1013419: fixed in vcmi 0.99+dfsg+git20220621.54fab9f0-2
has caused the Debian Bug report #1013419,
regarding vcmi FTBFS with ffmpeg 5.0.1
to be marked as done.

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

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


-- 
1013419: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013419
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vcmi
Version: 0.99+dfsg+git20190113.f06c8a87-2
Severity: serious
Tags: ftbfs bookworm sid

https://buildd.debian.org/status/logs.php?pkg=vcmi=0.99%2Bdfsg%2Bgit20190113.f06c8a87-2%2Bb2

...
/<>/client/CVideoHandler.cpp: In constructor 
‘CVideoPlayer::CVideoPlayer()’:
/<>/client/CVideoHandler.cpp:79:9: error: ‘av_register_all’ was 
not declared in this scope
   79 | av_register_all();
  | ^~~
/<>/client/CVideoHandler.cpp: In member function ‘bool 
CVideoPlayer::open(std::string, bool, bool, bool)’:
/<>/client/CVideoHandler.cpp:130:41: error: ‘AVStream’ {aka 
‘struct AVStream’} has no member named ‘codec’
  130 | if 
(format->streams[i]->codec->codec_type==AVMEDIA_TYPE_VIDEO)
  | ^
/<>/client/CVideoHandler.cpp:142:49: error: ‘AVStream’ {aka 
‘struct AVStream’} has no member named ‘codec’
  142 | codecContext = format->streams[stream]->codec;
  | ^
/<>/client/CVideoHandler.cpp:145:50: error: invalid use of 
incomplete type ‘struct AVCodecContext’
  145 | codec = avcodec_find_decoder(codecContext->codec_id);
  |  ^~
In file included from /usr/include/x86_64-linux-gnu/libavformat/avformat.h:313,
 from /<>/client/CVideoHandler.h:61,
 from /<>/client/CVideoHandler.cpp:12:
/usr/include/x86_64-linux-gnu/libavcodec/codec.h:195:8: note: forward 
declaration of ‘struct AVCodecContext’
  195 | struct AVCodecContext;
  |^~
/<>/client/CVideoHandler.cpp:154:14: error: ‘avcodec_open2’ was 
not declared in this scope; did you mean ‘avio_open2’?
  154 | if ( avcodec_open2(codecContext, codec, nullptr) < 0 )
  |  ^
  |  avio_open2
/<>/client/CVideoHandler.cpp:171:38: error: invalid use of 
incomplete type ‘struct AVCodecContext’
  171 | pos.w  = codecContext->width;
  |  ^~
In file included from /usr/include/x86_64-linux-gnu/libavformat/avformat.h:313,
 from /<>/client/CVideoHandler.h:61,
 from /<>/client/CVideoHandler.cpp:12:
/usr/include/x86_64-linux-gnu/libavcodec/codec.h:195:8: note: forward 
declaration of ‘struct AVCodecContext’
  195 | struct AVCodecContext;
  |^~
/<>/client/CVideoHandler.cpp:172:37: error: invalid use of 
incomplete type ‘struct AVCodecContext’
  172 | pos.h = codecContext->height;
  | ^~
In file included from /usr/include/x86_64-linux-gnu/libavformat/avformat.h:313,
 from /<>/client/CVideoHandler.h:61,
 from /<>/client/CVideoHandler.cpp:12:
/usr/include/x86_64-linux-gnu/libavcodec/codec.h:195:8: note: forward 
declaration of ‘struct AVCodecContext’
  195 | struct AVCodecContext;
  |^~
/<>/client/CVideoHandler.cpp:193:50: error: invalid use of 
incomplete type ‘struct AVCodecContext’
  193 | sws = sws_getContext(codecContext->width, 
codecContext->height, codecContext->pix_fmt,
  |  ^~
In file included from /usr/include/x86_64-linux-gnu/libavformat/avformat.h:313,
 from /<>/client/CVideoHandler.h:61,
 from /<>/client/CVideoHandler.cpp:12:
/usr/include/x86_64-linux-gnu/libavcodec/codec.h:195:8: note: forward 
declaration of ‘struct AVCodecContext’
  195 | struct AVCodecContext;
  |^~
/<>/client/CVideoHandler.cpp:193:71: error: invalid use of 
incomplete type ‘struct AVCodecContext’
  193 | sws = sws_getContext(codecContext->width, 
codecContext->height, codecContext->pix_fmt,
  |   ^~
In file included from /usr/include/x86_64-linux-gnu/libavformat/avformat.h:313,
 from /<>/client/CVideoHandler.h:61,
 from /<>/client/CVideoHandler.cpp:12:
/usr/include/x86_64-linux-gnu/libavcodec/codec.h:195:8: note: forward 

Bug#1010856: marked as done (Please make libjxl-dev depend on all required libraries)

[Debian Bug Tracking System]

Your message dated Mon, 04 Jul 2022 13:34:19 +
with message-id 
and subject line Bug#1010856: fixed in jpeg-xl 0.7.0~git20220704.de6a16a-1
has caused the Debian Bug report #1010856,
regarding Please make libjxl-dev depend on all required libraries
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.)


-- 
1010856: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010856
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libjxl-dev
Version: 0.7.0~git20220325.7594374+ds-3
Severity: serious

While working on GIMP 3.0 packaging, I stumbled on:

configure:31882: $PKG_CONFIG --exists --print-errors "libjxl >= 0.6.1"
Package libhwy was not found in the pkg-config search path.
Perhaps you should add the directory containing `libhwy.pc'
to the PKG_CONFIG_PATH environment variable
Package 'libhwy', required by 'libjxl', not found

Please add all the required -dev packages to libjxl-dev dependencies,
so building against libjxl is possible without adding any extra
Build-Deps.

The current version in experimental has the following in its .pc file:

Requires.private: libhwy libbrotlicommon libbrotlienc libbrotlidec lcms2

Thank you!
Jordi

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

Kernel: Linux 5.17.0-1-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=ca_ES.UTF-8, LC_CTYPE=ca_ES.UTF-8 (charmap=UTF-8), 
LANGUAGE=ca_ES:ca
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libjxl-dev depends on:
ii  libjxl0.7  0.7.0~git20220325.7594374+ds-3

libjxl-dev recommends no packages.

libjxl-dev suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: jpeg-xl
Source-Version: 0.7.0~git20220704.de6a16a-1
Done: Mathieu Malaterre 

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

Debian distribution maintenance software
pp.
Mathieu Malaterre  (supplier of updated jpeg-xl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 04 Jul 2022 11:54:24 +0200
Source: jpeg-xl
Architecture: source
Version: 0.7.0~git20220704.de6a16a-1
Distribution: experimental
Urgency: medium
Maintainer: Debian PhotoTools Maintainers 

Changed-By: Mathieu Malaterre 
Closes: 1010856
Changes:
 jpeg-xl (0.7.0~git20220704.de6a16a-1) experimental; urgency=medium
 .
   * d/p/manpages.patch: Add missing command line options
   * New upstream version 0.7.0~git20220408.e6264cd+ds
   * d/patches: Refresh patches
   * d/control: Remove dh-exec since not used anymore
   * d/rules: Set SKCMS bundle option to OFF for consistency
   * d/control: Add dependency to libjxl-testdata
   * d/patches: Add support for testdata in /usr
   * d/patches: Fix installation of cjxl_ng
   * d/control: Properly Implement 
   * d/patches: Remove a failing test
   * d/patches: Add a fix when RPATH is not set
   * d/rules: Make sure to remove by-products from test-suite
   * New upstream version 0.7.0~git20220420.6cce649+ds
   * d/patches: Remove patches applied upstream
   * d/rules: Adapt to latest change for jxlinfo
   * d/control: Bump Std-Vers to 4.6.1 no changes needed
   * d/control: make libjxl-dev depend on required libraries. Closes: #1010856
   * d/control: Make sure to use latest of testdata
   * d/copyright: Adapt to latest upstream changes
   * New upstream version 0.7.0~git20220704.de6a16a
   * d/patches: Refresh patches according to latest upstream
   * d/rules: Only apply no-psabi on armel/armhf
   * d/rules: Remove add_noise to match upstream
Checksums-Sha1:
 ab8ed76bab7c67c5a2ba9d91eb7b1da5837a9060 2929 
jpeg-xl_0.7.0~git20220704.de6a16a-1.dsc
 63eac4aae02a414558b40af971e26b24731bd038 1115176 
jpeg-xl_0.7.0~git20220704.de6a16a.orig.tar.xz
 d1d2afce8011bac5402b002381504e047d4d62b6 13916 
jpeg-xl_0.7.0~git20220704.de6a16a-1.debian.tar.xz
 93fa49490691c64292adad51053e3d667972c8b3 11080 
jpeg-xl_0.7.0~git20220704.de6a16a-1_source.buildinfo

Bug#1014314: lvm2: Missing 69-lvm-metad.rules causes lvm2 initramfs-tools hook to fail

[Anatoly Pugachev]

Package: lvm2
Version: 2.03.15-1
Followup-For: Bug #1014314

Dear Maintainer,

I have to remove offending lines from
/usr/share/initramfs-tools/hooks/lvm2 file, so my "update-initramfs -u"
to start working again.

I don't have /etc/udev/rules.d/56-lvm.rules nor 69-lvm-metad.rules
installed on my system.

Can someone please look?!

Thanks.



-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: sparc64

Kernel: Linux 5.19.0-rc5 (SMP w/16 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages lvm2 depends on:
ii  dmeventd  2:1.02.183-1
ii  dmsetup   2:1.02.183-1
ii  init-system-helpers   1.63
ii  libaio1   0.3.113-2
ii  libblkid1 2.38-4
ii  libc6 2.33-7
ii  libdevmapper-event1.02.1  2:1.02.183-1
ii  libdevmapper1.02.12:1.02.183-1
ii  libedit2  3.1-20210910-1
ii  libselinux1   3.4-1
ii  libsystemd0   251.2-7
ii  libudev1  251.2-7
ii  lsb-base  11.2

-- no debconf information

-- debsums errors found:
debsums: changed file /usr/share/initramfs-tools/hooks/lvm2 (from lvm2 package)

Bug#1013652: marked as done (canl-java: FTBFS: Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:3.1.0:testResources)

[Debian Bug Tracking System]

Your message dated Mon, 04 Jul 2022 13:19:06 +
with message-id 
and subject line Bug#1013652: fixed in canl-java 2.7.0-4
has caused the Debian Bug report #1013652,
regarding canl-java: FTBFS: Failed to execute goal 
org.apache.maven.plugins:maven-resources-plugin:3.1.0:testResources
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.)


-- 
1013652: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013652
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: canl-java
Version: 2.7.0-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220624 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=maven
>dh_update_autotools_config -O--buildsystem=maven
>dh_autoreconf -O--buildsystem=maven
>dh_auto_configure -O--buildsystem=maven
>   mh_patchpoms -plibcanl-java --debian-build --keep-pom-version 
> --maven-repo=/<>/debian/maven-repo
>dh_auto_build -O--buildsystem=maven
>   /usr/lib/jvm/default-java/bin/java -noverify -cp 
> /usr/share/maven/boot/plexus-classworlds-2.x.jar 
> -Dmaven.home=/usr/share/maven 
> -Dmaven.multiModuleProjectDirectory=/<> 
> -Dclassworlds.conf=/etc/maven/m2-debian.conf 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package 
> javadoc:jar javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US
> [INFO] Scanning for projects...
> [WARNING] The project eu.eu-emi.security:canl:jar:2.7.0 uses prerequisites 
> which is only intended for maven-plugin projects but not for non maven-plugin 
> projects. For such purposes you should use the maven-enforcer-plugin. See 
> https://maven.apache.org/enforcer/enforcer-rules/requireMavenVersion.html
> [INFO] 
> [INFO] --< eu.eu-emi.security:canl 
> >---
> [INFO] Building canl 2.7.0
> [INFO] [ jar 
> ]-
> [INFO] 
> [INFO] --- maven-resources-plugin:3.1.0:resources (default-resources) @ canl 
> ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 1 resource
> [INFO] 
> [INFO] --- maven-compiler-plugin:3.8.1:compile (default-compile) @ canl ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 167 source files to /<>/target/classes
> [INFO] 
> /<>/src/main/java/eu/emi/security/authn/x509/helpers/pkipath/bc/CertPathValidatorUtilitiesCanl.java:
>  Some input files use or override a deprecated API.
> [INFO] 
> /<>/src/main/java/eu/emi/security/authn/x509/helpers/pkipath/bc/CertPathValidatorUtilitiesCanl.java:
>  Recompile with -Xlint:deprecation for details.
> [INFO] 
> /<>/src/main/java/eu/emi/security/authn/x509/helpers/pkipath/bc/CertPathValidatorUtilities.java:
>  Some input files use unchecked or unsafe operations.
> [INFO] 
> /<>/src/main/java/eu/emi/security/authn/x509/helpers/pkipath/bc/CertPathValidatorUtilities.java:
>  Recompile with -Xlint:unchecked for details.
> [INFO] 
> [INFO] --- maven-resources-plugin:3.1.0:testResources (default-testResources) 
> @ canl ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 2427 resources
> [INFO] 
> [INFO] 
> 
> [INFO] Skipping canl
> [INFO] This project has been banned from the build due to previous failures.
> [INFO] 
> 
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time:  2.581 s
> [INFO] Finished at: 2022-06-24T05:33:24Z
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-resources-plugin:3.1.0:testResources 
> (default-testResources) on project canl: 
> /<>/target/test-classes/namespaces/eugridpma-globus/b4278411.signing_policy
>  -> [Help 1]
> [ERROR] 
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR] 
> [ERROR] For more information about the errors and possible solutions, please 
> read the following articles:
> [ERROR] [Help 1] 
> 

Processed: lnav: FTBFS: 1 test fails due to quoting differences

[Debian Bug Tracking System]

Processing control commands:

> found -1 0.9.0-2
Bug #1014335 [src:lnav] lnav: FTBFS: 1 test fails due to quoting differences
Marked as found in versions lnav/0.9.0-2.

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

Bug#1014335: lnav: FTBFS: 1 test fails due to quoting differences

[Andreas Beckmann]

Source: lnav
Version: 0.10.1-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Control: found -1 0.9.0-2

Hi,

lnav in sid and experimental recently started to FTBFS, since some
(transitive) build-depends seems to have changed the quoting style in
the stuff it generates. Is the new one even correct?
(Looks to me like the change from an array to a string.)

FAIL: test_sql_json_func.sh
===

test: ./drive_sql SELECT id, json_group_object(key, value) as stack FROM ( 
SELECT 1 as id, 1 as key, 10 as value UNION ALL SELECT 1 as id, 2 as key, 
json_array(1, 2, 3) as value UNION ALL SELECT 1 as id, 3 as key, 30.5 as value)
json_group_object with number keys does not work
--- -   2022-07-04 06:29:15.368031500 +
+++ test_sql_json_func.sh_32.tmp2022-07-04 06:29:15.346400398 +
@@ -1,3 +1,3 @@
 Row 0:
   Column id: 1
-  Column  stack: {"1":10,"2":[1,2,3],"3":30.5}
+  Column  stack: {"1":10,"2":"[1,2,3]","3":30.5}
FAIL test_sql_json_func.sh (exit status: 1)


Testsuite summary for lnav 0.10.1

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

See test/test-suite.log


Andreas


lnav_0.10.1-2.log.gz
Description: application/gzip

Bug#1013700: Strangely rare pytest 7.x bug report

[Julian Gilbey]

Dear all,

I wonder whether you might have any clue about
https://bugs.debian.org/1013700
I have mostly worked out the "cause" of the bug, but I haven't quite
got to the bottom of it.

When running the command
PYTHONPATH=. python3.10 -m pytest qtpy/tests
in the directory .pybuild/cpython3_3.10_qtpy/build, I get the error
message:

ImportError while loading conftest 
'/home/jdg/debian/spyder-packages/qtpy/build-area/python-qtpy-2.1.0/.pybuild/cpython3_3.10_qtpy/build/qtpy/tests/conftest.py'.
TypeError: the 'package' argument is required to perform a relative import for 
'.pybuild.cpython3_3.10_qtpy.build.qtpy.tests'

If the directory .pybuild is renamed to pybuild, the tests run without
a problem.  So there seems to be something funny about conftest.py
(and removing all of the other files from the qtpy/tests directory
except for the empty __init__.py gives the same error); here's a link
to it:

https://salsa.debian.org/python-team/packages/python-qtpy/-/blob/master/qtpy/tests/conftest.py

But there doesn't seem to be anything out of the ordinary about this.
So I am mystified: why does pytest 7.x seem to not give this error on
any other Debian package?

The only solution I currently have for this package is skip the tests
at build time and rely on autopkgtest to do them.

Best wishes,

   Julian

Processed: Re: Bug#1004769: digikam: FTBFS with ffmpeg 5.0

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #1004769 [src:digikam] digikam: FTBFS with ffmpeg 5.0
Severity set to 'normal' from 'serious'

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

Bug#1004769: digikam: FTBFS with ffmpeg 5.0

[Steven Robbins]

control: severity -1 normal

On Fri, 25 Feb 2022 22:55:12 +0100 Sebastian Ramacher  
wrote:
> On 2022-02-21 16:05:37 -0600, Steven Robbins wrote:
> > On Tue, 1 Feb 2022 21:01:39 +0100 Sebastian Ramacher 
 
> > wrote:
> > > Source: digikam
> > > Version: 4:7.1.0-2
> > 
> > I have just uploaded Digikam 7.5.0 to unstable.  If you have a chance to 
re-
> > try the build, would appreciate knowing if it now builds with new ffmpeg.
> 
> 7.5.0 fails to build with the same error.

I have temporarily disabled video player in Digikam 7.7.0-1 upload, so 
lowering this bug severity.

-Steve


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

Processed: your mail

[Debian Bug Tracking System]

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

> tags 1014330 upstream
Bug #1014330 [src:highway] highway: NEON and VFPv4 are not part of the armhf 
baseline
Added tag(s) upstream.
> forwarded 1014330 https://github.com/google/highway/issues/818
Bug #1014330 [src:highway] highway: NEON and VFPv4 are not part of the armhf 
baseline
Set Bug forwarded-to-address to 'https://github.com/google/highway/issues/818'.
>
End of message, stopping processing here.

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

Bug#1012741: modprobe: ERROR: could not insert 'crc_itu_t': Key was rejected by service

[Ansgar]

On Sun, 19 Jun 2022 12:59:55 +0200 Ben Hutchings wrote:
> > I'm now looking at whether the missing bytes are recoverable (e.g. are
> > they always zeroes).
> [...]
> 
> I wrote a script to try all possible byte values for 2 bytes before or
> after the short signature.  For this particular file, none of them
> producd a valid signature.  So the short signatures seem to be
> corrupted in a more complex way.

The "OCTET STRING" containing the actual signature is shorter for the
seemingly corrupted signatures:

+---
| $dumpasn1 
./linux-image-4.19.0-21-amd64-unsigned/lib/modules/4.19.0-21-amd64/kernel/net/openvswitch/vport-vxlan.ko.sig
|   0 404: SEQUENCE {
| [...]
| 151 254:   OCTET STRING
+---

vs

+---
| $ dumpasn1 
./linux-image-4.19.0-21-cloud-amd64-unsigned/lib/modules/4.19.0-21-cloud-amd64/kernel/net/openvswitch/vport-vxlan.ko.sig
|   0 407: SEQUENCE {
| [...]
| 151 256:   OCTET STRING
+---

Given the number of corrupted signatures is pretty much the number of
signatures where the two leading bytes should be 0 (as stated in [1]),
I suspect something (incorrectly?) outputs a shorter OCTET STRING
leaving out the 0 (as one might for a large integer type), but the
other side expects a fixed size?

If so, the file should validate if one injects two leading 0 bytes in
the OCTET STRING (and updates all length values). I would need to check
how to manipulate files using ASN.1's DER encoding to try this...

Ansgar

  [1]: https://bugs.debian.org/1012741#48

Processed: closing 1011733

[Debian Bug Tracking System]

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

> close 1011733 3.4.0~a1-3
Bug #1011733 [src:androguard] androguard: FTBFS: AssertionError:
The source 'androguard' and version '3.4.0~a1-3' do not appear to match any 
binary packages
Marked as fixed in versions androguard/3.4.0~a1-3.
Bug #1011733 [src:androguard] androguard: FTBFS: AssertionError:
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1011733: closing 1011733

[Jochen Sprickerhof]

close 1011733 3.4.0~a1-3
thanks

Bug#1011713: marked as done (oscrypto: FTBFS: AttributeError: /usr/lib/x86_64-linux-gnu/libcrypto.so.3: undefined symbol: EVP_PKEY_size. Did you mean: 'EVP_PKEY_free'?)

[Debian Bug Tracking System]

Your message dated Mon, 04 Jul 2022 11:19:12 +
with message-id 
and subject line Bug#1011713: fixed in androguard 3.4.0~a1-3
has caused the Debian Bug report #1011713,
regarding oscrypto: FTBFS: AttributeError: 
/usr/lib/x86_64-linux-gnu/libcrypto.so.3: undefined symbol: EVP_PKEY_size. Did 
you mean: 'EVP_PKEY_free'?
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.)


-- 
1011713: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011713
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: oscrypto
Version: 1.2.1-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
>   install -d /<>/debian/.debhelper/generated/_source/home
>   pybuild --configure -i python{version} -p "3.9 3.10"
> D: pybuild pybuild:587: version: 5.20220403
> D: pybuild pybuild:588: ['/usr/bin/pybuild', '--configure', '-i', 
> 'python{version}', '-p', '3.9 3.10']
> D: pybuild pybuild:38: cfg: Namespace(verbose=True, quiet=False, 
> really_quiet=False, detect_only=False, clean_only=False, configure_only=True, 
> build_only=False, install_only=False, test_only=False, list_systems=False, 
> print_args=None, before_clean=None, clean_args=None, after_clean=None, 
> before_configure=None, configure_args=None, after_configure=None, 
> before_build=None, build_args=None, after_build=None, before_install=None, 
> install_args=None, after_install=None, before_test=None, test_args=None, 
> after_test=None, test_nose=False, test_nose2=False, test_pytest=False, 
> test_tox=False, test_custom=False, dir='/<>', 
> destdir='debian/tmp', ext_destdir=None, ext_pattern='\\.so(\\.[^/]*)?$', 
> ext_sub_pattern=None, ext_sub_repl=None, install_dir=None, name='oscrypto', 
> system=None, versions=['3.9', '3.10'], interpreter=['python{version}'], 
> disable=None, custom_tests=False)
> D: pybuild __init__:36: cannot initialize 'cmake' plugin
> Traceback (most recent call last):
>   File "/usr/share/dh-python/dhpython/build/__init__.py", line 32, in 
> module.BuildSystem.is_usable()
>   File "/usr/share/dh-python/dhpython/build/base.py", line 122, in is_usable
> raise Exception("missing command: %s" % command)
> Exception: missing command: cmake
> D: pybuild tools:232: invoking: /usr/bin/dpkg-architecture
> D: pybuild debhelper:169: source=oscrypto, binary 
> packages=['python3-oscrypto']
> D: pybuild pybuild:122: Plugin custom: certainty 0
> D: pybuild pybuild:122: Plugin distutils: certainty 50
> D: pybuild pybuild:122: Plugin flit: certainty 0
> D: pybuild pybuild:122: Plugin pyproject: certainty 0
> D: pybuild pybuild:148: detected build system: distutils (certainty: 50%)
> D: pybuild plugin_distutils:54: pydistutils config file:
> [clean]
> all=1
> [build]
> build_lib=/<>/.pybuild/cpython3_3.9_oscrypto/build
> [install]
> force=1
> install_layout=deb
> install_scripts=$base/bin
> install_lib=/usr/lib/python3.9/dist-packages
> prefix=/usr
> 
> I: pybuild base:239: python3.9 setup.py config 
> D: pybuild tools:232: invoking: python3.9 setup.py config 
> running config
> D: pybuild plugin_distutils:54: pydistutils config file:
> [clean]
> all=1
> [build]
> build_lib=/<>/.pybuild/cpython3_3.10_oscrypto/build
> [install]
> force=1
> install_layout=deb
> install_scripts=$base/bin
> install_lib=/usr/lib/python3.10/dist-packages
> prefix=/usr
> 
> I: pybuild base:239: python3.10 setup.py config 
> D: pybuild tools:232: invoking: python3.10 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
>   pybuild --build -i python{version} -p "3.9 3.10"
> D: pybuild pybuild:587: version: 5.20220403
> D: pybuild pybuild:588: ['/usr/bin/pybuild', '--build', '-i', 
> 'python{version}', '-p', '3.9 3.10']
> D: pybuild pybuild:38: cfg: Namespace(verbose=True, quiet=False, 
> really_quiet=False, detect_only=False, clean_only=False, 
> configure_only=False, build_only=True, install_only=False, test_only=False, 
> list_systems=False, print_args=None, before_clean=None, clean_args=None, 
> after_clean=None, before_configure=None, configure_args=None, 
> after_configure=None, before_build=None, build_args=None, after_build=None, 
> before_install=None, install_args=None, after_install=None, before_test=None, 
> 

Bug#1014330: highway: NEON and VFPv4 are not part of the armhf baseline

[Adrian Bunk]

Source: highway
Version: 0.17.0-6
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: Mathieu Malaterre 

NEON and VFPv4 are not part of the armhf baseline:
https://wiki.debian.org/ArchitectureSpecificsMemo#armhf

Plenty of hardware (inluding some of our buildds)
do not support NEON.

Plenty of hardware (inluding some of our buildds)
do not support VFPv4.

Bug#1014329: anbox: Not working after removing ashmem module

[Shengjing Zhu]

Package: anbox
Version: 0.0~git20211020-3
Severity: grave
Justification: renders package unusable
Forwarded: https://github.com/anbox/anbox/issues/2042
X-Debbugs-Cc: z...@debian.org

ashmem_linux module has been removed from kernel 5.18.

https://github.com/torvalds/linux/commit/721412ed3d819e767cac2b06646bf03aa158aaec
https://salsa.debian.org/kernel-team/linux/-/commit/7d080ca22b66848115547ebc7da839d18db956f4

Bug#1014115: uninstall does not properly remove enablement symlinks

[Luca Boccassi]

On Mon, 4 Jul 2022 at 11:55, Michael Biebl  wrote:
>
>
> Am 04.07.22 um 12:36 schrieb Luca Boccassi:
> > I have uploaded i-s-h, should we close this one now?
>
> I've seen the upload. Thanks!
>
> I was debating with myself whether systemd-homed should get a tightened,
> versioned Depends on i-s-h to prevent this issue from happening.
>
> This would make a backport a bit harder, but maybe a stable upload of
> i-s-h with this fix is a good idea anyway?
>
> Regards,
> Michael

It's a new package and optional, so maybe it's not worth it - but up
to you, if you want to add that and a backport to be safer, I don't
have any objection.

Kind regards,
Luca Boccassi

Bug#1014115: uninstall does not properly remove enablement symlinks

[Michael Biebl]

Am 04.07.22 um 12:36 schrieb Luca Boccassi:

I have uploaded i-s-h, should we close this one now?


I've seen the upload. Thanks!

I was debating with myself whether systemd-homed should get a tightened, 
versioned Depends on i-s-h to prevent this issue from happening.


This would make a backport a bit harder, but maybe a stable upload of 
i-s-h with this fix is a good idea anyway?


Regards,
Michael


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1013931: marked as done (libtorrent-rasterbar2.0: Crash on exit)

[Debian Bug Tracking System]

Your message dated Mon, 04 Jul 2022 10:49:07 +
with message-id 
and subject line Bug#1013931: fixed in libtorrent-rasterbar 2.0.6-4
has caused the Debian Bug report #1013931,
regarding libtorrent-rasterbar2.0: Crash on exit
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.)


-- 
1013931: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013931
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libtorrent-rasterbar2.0
Version: 2.0.6-3+b1
Severity: grave
X-Debbugs-Cc: none, Hilko Bengen 
Control: notfound -1 2.0.6-3

Dear Maintainer,

bug #1013470 about a nbdkit rebuild failure was reported and it turned
out that this happens because of a crash that happens even in trivial
cases:

,
| $ server/nbdkit plugins/torrent/.libs/nbdkit-torrent-plugin.so --help
| nbdkit [-4|--ipv4-only] [-6|--ipv6-only]
|[-D|--debug PLUGIN|FILTER|nbdkit.FLAG=N]
|[-e|--exportname EXPORTNAME] [--exit-with-parent]
|[--filter FILTER ...] [-f|--foreground]
|[-g|--group GROUP] [-i|--ipaddr IPADDR]
|[--log stderr|syslog|null]
|[-n|--newstyle] [--mask-handshake MASK] [--no-sr] [-o|--oldstyle]
|[-P|--pidfile PIDFILE]
|[-p|--port PORT] [-r|--readonly]
|[--run CMD] [-s|--single] [--selinux-label LABEL] [--swap]
|[-t|--threads THREADS]
|[--tls off|on|require]
|[--tls-certificates /path/to/certificates]
|[--tls-psk /path/to/pskfile] [--tls-verify-peer]
|[-U|--unix SOCKET] [-u|--user USER]
|[-v|--verbose] [-V|--version] [--vsock]
|PLUGIN [[KEY=]VALUE [KEY=VALUE [...]]]
| 
| nbdkit --dump-config
| 
| nbdkit PLUGIN --dump-plugin
| 
| nbdkit --help
| 
| Please read the nbdkit(1) manual page for full usage.
| 
| plugin: torrent (nbdkit bittorrent plugin)
| (plugins/torrent/.libs/nbdkit-torrent-plugin.so)
| torrent=   (required) Torrent or magnet link.
| file=DISK.iso  File to serve within torrent.
| cache=DIR  Set directory to store partial downloads.
| Segmentation fault
`

>From the output, it looks as if the crash occurred on a cleanup code
path.

Downgrading to 2.0.6-3 (before the OpenSSL 3 rebuild) makes the
segmentation fault go away.

The stacktrace below suggests that this is related to cleanup code
registered using atexit(3): pthread_rwlock_wrlock() is called with a
NULL pointer.

,
| $ gdb --args server/nbdkit plugins/torrent/.libs/nbdkit-torrent-plugin.so 
--help
| GNU gdb (Debian 12.1-2) 12.1
| Copyright (C) 2022 Free Software Foundation, Inc.
| [...]
| (gdb) run
| Starting program: /home/bengen/p/deb/nbdkit/server/nbdkit 
plugins/torrent/.libs/nbdkit-torrent-plugin.so --help
| [Thread debugging using libthread_db enabled]
| Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
| nbdkit [-4|--ipv4-only] [-6|--ipv6-only]
|[-D|--debug PLUGIN|FILTER|nbdkit.FLAG=N]
| [...]
| torrent=   (required) Torrent or magnet link.
| file=DISK.iso  File to serve within torrent.
| cache=DIR  Set directory to store partial downloads.
| 
| Program received signal SIGSEGV, Segmentation fault.
| __GI___pthread_rwlock_wrlock (rwlock=0x0) at pthread_rwlock_wrlock.c:27
| 27pthread_rwlock_wrlock.c: No such file or directory.
| (gdb) bt
| #0  __GI___pthread_rwlock_wrlock (rwlock=0x0) at pthread_rwlock_wrlock.c:27
| #1  0x76c8a8e9 in CRYPTO_THREAD_write_lock (lock=) at 
../crypto/threads_pthread.c:112
| #2  0x76ba7a03 in conf_modules_finish_int () at 
../crypto/conf/conf_mod.c:524
| #3  0x76ba8132 in CONF_modules_unload (all=1) at 
../crypto/conf/conf_mod.c:482
| #4  0x7726af24 in 
boost::asio::ssl::detail::openssl_init_base::do_init::~do_init 
(this=0x6157dc50, __in_chrg=)
| at /usr/include/boost/asio/ssl/detail/impl/openssl_init.ipp:90
| #5  
std::_Sp_counted_ptr::_M_dispose (
| this=) at /usr/include/c++/11/bits/shared_ptr_base.h:348
| #6  0x7726b09a in 
std::_Sp_counted_base<(__gnu_cxx::_Lock_policy)2>::_M_release 
(this=0x6157db90)
| at /usr/include/c++/11/bits/shared_ptr_base.h:168
| #7  std::__shared_count<(__gnu_cxx::_Lock_policy)2>::~__shared_count 
(this=, __in_chrg=)
| at /usr/include/c++/11/bits/shared_ptr_base.h:705
| #8  std::__shared_ptr::~__shared_ptr (
| this=, __in_chrg=) at 
/usr/include/c++/11/bits/shared_ptr_base.h:1154
| #9  
std::shared_ptr::~shared_ptr
 (this=, __in_chrg=)
| at /usr/include/c++/11/bits/shared_ptr.h:122
| #10 0x77bb9f77 in __run_exit_handlers (status=status@entry=0, 

Bug#1014115: uninstall does not properly remove enablement symlinks

[Luca Boccassi]

On Sat, 2 Jul 2022 at 20:40, Michael Biebl  wrote:
>
> Am 02.07.22 um 18:30 schrieb Luca Boccassi:
> > On Fri, 1 Jul 2022 at 20:20, Michael Biebl  wrote:
> >>
> >>
> >> Am 30.06.22 um 22:31 schrieb Luca Boccassi:
> >>> The problem is some files leftover, no? Just delete them in the
> >>> postinst or postrm?
> >>
> >> My main motivation is to "stop the bleeding" as quickly as possible.
> >>
> >> If we continue to create those broken state files, we'd have to keep
> >> those postinst/postrm cleanup routines for a possibly long time.
> >
> > I'd rather just fix i-s-h, here's a MR, it fixes the issue for me, can
> > you give it a go as well please? I'll do an upload once it's confirmed
> > and reviewed
> >
> > https://salsa.debian.org/debian/init-system-helpers/-/merge_requests/21
>
> Thank you, bluca.
> Without having tested it and without knowing Perl very well, the MR
> looks ok to me.
> I think Felipe is a bit more familiar with Perl, so if he could give his
> ack, that would be good I think.
>
> Cheers,
> Michael

I have uploaded i-s-h, should we close this one now?

Kind regards,
Luca Boccassi

Bug#1011713: marked as done (oscrypto: FTBFS: AttributeError: /usr/lib/x86_64-linux-gnu/libcrypto.so.3: undefined symbol: EVP_PKEY_size. Did you mean: 'EVP_PKEY_free'?)

[Debian Bug Tracking System]

Your message dated Mon, 04 Jul 2022 10:19:58 +
with message-id 
and subject line Bug#1011713: fixed in oscrypto 1.3.0-1
has caused the Debian Bug report #1011713,
regarding oscrypto: FTBFS: AttributeError: 
/usr/lib/x86_64-linux-gnu/libcrypto.so.3: undefined symbol: EVP_PKEY_size. Did 
you mean: 'EVP_PKEY_free'?
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.)


-- 
1011713: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011713
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: oscrypto
Version: 1.2.1-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
>   install -d /<>/debian/.debhelper/generated/_source/home
>   pybuild --configure -i python{version} -p "3.9 3.10"
> D: pybuild pybuild:587: version: 5.20220403
> D: pybuild pybuild:588: ['/usr/bin/pybuild', '--configure', '-i', 
> 'python{version}', '-p', '3.9 3.10']
> D: pybuild pybuild:38: cfg: Namespace(verbose=True, quiet=False, 
> really_quiet=False, detect_only=False, clean_only=False, configure_only=True, 
> build_only=False, install_only=False, test_only=False, list_systems=False, 
> print_args=None, before_clean=None, clean_args=None, after_clean=None, 
> before_configure=None, configure_args=None, after_configure=None, 
> before_build=None, build_args=None, after_build=None, before_install=None, 
> install_args=None, after_install=None, before_test=None, test_args=None, 
> after_test=None, test_nose=False, test_nose2=False, test_pytest=False, 
> test_tox=False, test_custom=False, dir='/<>', 
> destdir='debian/tmp', ext_destdir=None, ext_pattern='\\.so(\\.[^/]*)?$', 
> ext_sub_pattern=None, ext_sub_repl=None, install_dir=None, name='oscrypto', 
> system=None, versions=['3.9', '3.10'], interpreter=['python{version}'], 
> disable=None, custom_tests=False)
> D: pybuild __init__:36: cannot initialize 'cmake' plugin
> Traceback (most recent call last):
>   File "/usr/share/dh-python/dhpython/build/__init__.py", line 32, in 
> module.BuildSystem.is_usable()
>   File "/usr/share/dh-python/dhpython/build/base.py", line 122, in is_usable
> raise Exception("missing command: %s" % command)
> Exception: missing command: cmake
> D: pybuild tools:232: invoking: /usr/bin/dpkg-architecture
> D: pybuild debhelper:169: source=oscrypto, binary 
> packages=['python3-oscrypto']
> D: pybuild pybuild:122: Plugin custom: certainty 0
> D: pybuild pybuild:122: Plugin distutils: certainty 50
> D: pybuild pybuild:122: Plugin flit: certainty 0
> D: pybuild pybuild:122: Plugin pyproject: certainty 0
> D: pybuild pybuild:148: detected build system: distutils (certainty: 50%)
> D: pybuild plugin_distutils:54: pydistutils config file:
> [clean]
> all=1
> [build]
> build_lib=/<>/.pybuild/cpython3_3.9_oscrypto/build
> [install]
> force=1
> install_layout=deb
> install_scripts=$base/bin
> install_lib=/usr/lib/python3.9/dist-packages
> prefix=/usr
> 
> I: pybuild base:239: python3.9 setup.py config 
> D: pybuild tools:232: invoking: python3.9 setup.py config 
> running config
> D: pybuild plugin_distutils:54: pydistutils config file:
> [clean]
> all=1
> [build]
> build_lib=/<>/.pybuild/cpython3_3.10_oscrypto/build
> [install]
> force=1
> install_layout=deb
> install_scripts=$base/bin
> install_lib=/usr/lib/python3.10/dist-packages
> prefix=/usr
> 
> I: pybuild base:239: python3.10 setup.py config 
> D: pybuild tools:232: invoking: python3.10 setup.py config 
> running config
>dh_auto_build -O--buildsystem=pybuild
>   pybuild --build -i python{version} -p "3.9 3.10"
> D: pybuild pybuild:587: version: 5.20220403
> D: pybuild pybuild:588: ['/usr/bin/pybuild', '--build', '-i', 
> 'python{version}', '-p', '3.9 3.10']
> D: pybuild pybuild:38: cfg: Namespace(verbose=True, quiet=False, 
> really_quiet=False, detect_only=False, clean_only=False, 
> configure_only=False, build_only=True, install_only=False, test_only=False, 
> list_systems=False, print_args=None, before_clean=None, clean_args=None, 
> after_clean=None, before_configure=None, configure_args=None, 
> after_configure=None, before_build=None, build_args=None, after_build=None, 
> before_install=None, install_args=None, after_install=None, before_test=None, 
> test_args=None, 

Bug#1013529: marked as done (vulkan-validationlayers: FTBFS: vk_typemap_helper.h:3142:31: error: ‘VkVideoEncodeH264SessionCreateInfoEXT’ was not declared in this scope; did you mean ‘VkVideoEncodeH264

[Debian Bug Tracking System]

Your message dated Mon, 04 Jul 2022 10:06:21 +
with message-id 
and subject line Bug#1013529: fixed in vulkan-validationlayers 1.3.216.0-1
has caused the Debian Bug report #1013529,
regarding vulkan-validationlayers: FTBFS: vk_typemap_helper.h:3142:31: error: 
‘VkVideoEncodeH264SessionCreateInfoEXT’ was not declared in this scope; did you 
mean ‘VkVideoEncodeH264VclFrameInfoEXT’?
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.)


-- 
1013529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013529
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vulkan-validationlayers
Version: 1.3.204.1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220624 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> /usr/bin/c++ -DAPI_NAME=\"Vulkan\" -DVK_ENABLE_BETA_EXTENSIONS 
> -DVkLayer_utils_EXPORTS -I/<>/layers 
> -I/<>/layers/generated -I/<>/build 
> -I/<>/build/layers -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -O3 -DNDEBUG -fPIC -Wall -Wextra -Wno-unused-parameter 
> -Wno-missing-field-initializers -fno-strict-aliasing -fno-builtin-memcmp 
> -fvisibility=hidden -Wimplicit-fallthrough=0 -std=gnu++11 -MD -MT 
> CMakeFiles/VkLayer_utils.dir/layers/generated/vk_format_utils.cpp.o -MF 
> CMakeFiles/VkLayer_utils.dir/layers/generated/vk_format_utils.cpp.o.d -o 
> CMakeFiles/VkLayer_utils.dir/layers/generated/vk_format_utils.cpp.o -c 
> /<>/layers/generated/vk_format_utils.cpp
> In file included from /<>/layers/vk_layer_logging.h:43,
>  from /<>/layers/vk_layer_utils.h:33,
>  from 
> /<>/layers/generated/vk_format_utils.cpp:30:
> /<>/layers/generated/vk_typemap_helper.h:3142:31: error: 
> ‘VkVideoEncodeH264SessionCreateInfoEXT’ was not declared in this scope; did 
> you mean ‘VkVideoEncodeH264VclFrameInfoEXT’?
>  3142 | template <> struct LvlTypeMap {
>   |   ^
>   |   VkVideoEncodeH264VclFrameInfoEXT
> In file included from /<>/layers/vk_layer_logging.h:43,
>  from /<>/layers/vk_layer_utils.h:33,
>  from /<>/layers/vk_layer_utils.cpp:22:
> /<>/layers/generated/vk_typemap_helper.h:3142:31: error: 
> ‘VkVideoEncodeH264SessionCreateInfoEXT’ was not declared in this scope; did 
> you mean ‘VkVideoEncodeH264VclFrameInfoEXT’?
>  3142 | template <> struct LvlTypeMap {
>   |   ^
>   |   VkVideoEncodeH264VclFrameInfoEXT
> /<>/layers/generated/vk_typemap_helper.h:3142:68: error: 
> template argument 1 is invalid
>  3142 | template <> struct LvlTypeMap {
>   |^
> /<>/layers/generated/vk_typemap_helper.h:3142:68: error: 
> template argument 1 is invalid
>  3142 | template <> struct LvlTypeMap {
>   |^
> /<>/layers/generated/vk_typemap_helper.h:3146:32: error: 
> ‘VK_STRUCTURE_TYPE_VIDEO_ENCODE_H264_SESSION_CREATE_INFO_EXT’ was not 
> declared in this scope; did you mean 
> ‘VK_STRUCTURE_TYPE_VIDEO_ENCODE_H264_VCL_FRAME_INFO_EXT’?
>  3146 | template <> struct 
> LvlSTypeMap {
>   |
> ^~~
>   |
> VK_STRUCTURE_TYPE_VIDEO_ENCODE_H264_VCL_FRAME_INFO_EXT
> /<>/layers/generated/vk_typemap_helper.h:3146:91: error: 
> template argument 1 is invalid
>  3146 | template <> struct 
> LvlSTypeMap {
>   |   
> ^
> /<>/layers/generated/vk_typemap_helper.h:3146:32: error: 
> ‘VK_STRUCTURE_TYPE_VIDEO_ENCODE_H264_SESSION_CREATE_INFO_EXT’ was not 
> declared in this scope; did you mean 
> ‘VK_STRUCTURE_TYPE_VIDEO_ENCODE_H264_VCL_FRAME_INFO_EXT’?
>  3146 | template <> struct 
> LvlSTypeMap {
>   |
> ^~~
>   |
> VK_STRUCTURE_TYPE_VIDEO_ENCODE_H264_VCL_FRAME_INFO_EXT
> /<>/layers/generated/vk_typemap_helper.h:3146:91: error: 
> template argument 1 is invalid
>  3146 | template <> struct 
> LvlSTypeMap {
>   |

Bug#1013575: marked as done (vulkan-tools: FTBFS: vk_typemap_helper.h:3141:31: error: ‘VkVideoEncodeH264SessionCreateInfoEXT’ was not declared in this scope; did you mean ‘VkVideoEncodeH264VclFrameInf

[Debian Bug Tracking System]

Your message dated Mon, 04 Jul 2022 10:06:13 +
with message-id 
and subject line Bug#1013575: fixed in vulkan-tools 1.3.216.0+dfsg1-1
has caused the Debian Bug report #1013575,
regarding vulkan-tools: FTBFS: vk_typemap_helper.h:3141:31: error: 
‘VkVideoEncodeH264SessionCreateInfoEXT’ was not declared in this scope; did you 
mean ‘VkVideoEncodeH264VclFrameInfoEXT’?
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.)


-- 
1013575: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013575
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vulkan-tools
Version: 1.3.204.0+dfsg1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220624 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> cd /<>/build/cube && /usr/bin/cc -DVK_ENABLE_BETA_EXTENSIONS 
> -DVK_USE_PLATFORM_WAYLAND_KHR -I/<>/build/cube 
> -I/<>/cube -I/<>/build/cube/.. -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c99 -Wall 
> -Wextra -Wno-unused-parameter -Wno-missing-field-initializers 
> -fno-strict-aliasing -fno-builtin-memcmp -Wimplicit-fallthrough=0 
> -fvisibility=hidden -MD -MT 
> cube/CMakeFiles/vkcube-wayland.dir/xdg-shell-code.c.o -MF 
> CMakeFiles/vkcube-wayland.dir/xdg-shell-code.c.o.d -o 
> CMakeFiles/vkcube-wayland.dir/xdg-shell-code.c.o -c 
> /<>/build/cube/xdg-shell-code.c
> In file included from /<>/icd/generated/mock_icd.cpp:27:
> /<>/icd/generated/vk_typemap_helper.h:3141:31: error: 
> ‘VkVideoEncodeH264SessionCreateInfoEXT’ was not declared in this scope; did 
> you mean ‘VkVideoEncodeH264VclFrameInfoEXT’?
>  3141 | template <> struct LvlTypeMap {
>   |   ^
>   |   VkVideoEncodeH264VclFrameInfoEXT
> /<>/icd/generated/vk_typemap_helper.h:3141:68: error: template 
> argument 1 is invalid
>  3141 | template <> struct LvlTypeMap {
>   |^
> /<>/icd/generated/vk_typemap_helper.h:3145:32: error: 
> ‘VK_STRUCTURE_TYPE_VIDEO_ENCODE_H264_SESSION_CREATE_INFO_EXT’ was not 
> declared in this scope; did you mean 
> ‘VK_STRUCTURE_TYPE_VIDEO_ENCODE_H264_VCL_FRAME_INFO_EXT’?
>  3145 | template <> struct 
> LvlSTypeMap {
>   |
> ^~~
>   |
> VK_STRUCTURE_TYPE_VIDEO_ENCODE_H264_VCL_FRAME_INFO_EXT
> /<>/icd/generated/vk_typemap_helper.h:3145:91: error: template 
> argument 1 is invalid
>  3145 | template <> struct 
> LvlSTypeMap {
>   |   
> ^
> /<>/icd/generated/vk_typemap_helper.h:3262:31: error: 
> ‘VkVideoEncodeH265SessionCreateInfoEXT’ was not declared in this scope; did 
> you mean ‘VkVideoEncodeH265VclFrameInfoEXT’?
>  3262 | template <> struct LvlTypeMap {
>   |   ^
>   |   VkVideoEncodeH265VclFrameInfoEXT
> /<>/icd/generated/vk_typemap_helper.h:3262:68: error: template 
> argument 1 is invalid
>  3262 | template <> struct LvlTypeMap {
>   |^
> /<>/icd/generated/vk_typemap_helper.h:3266:32: error: 
> ‘VK_STRUCTURE_TYPE_VIDEO_ENCODE_H265_SESSION_CREATE_INFO_EXT’ was not 
> declared in this scope; did you mean 
> ‘VK_STRUCTURE_TYPE_VIDEO_ENCODE_H265_VCL_FRAME_INFO_EXT’?
>  3266 | template <> struct 
> LvlSTypeMap {
>   |
> ^~~
>   |
> VK_STRUCTURE_TYPE_VIDEO_ENCODE_H265_VCL_FRAME_INFO_EXT
> /<>/icd/generated/vk_typemap_helper.h:3266:91: error: template 
> argument 1 is invalid
>  3266 | template <> struct 
> LvlSTypeMap {
>   |   
> ^
> /<>/icd/generated/vk_typemap_helper.h:3317:31: error: 
> ‘VkVideoEncodeH265NaluSliceEXT’ was not declared in this scope; did you mean 
> ‘VkVideoEncodeH264NaluSliceEXT’?
>  3317 | template <> struct LvlTypeMap {
>   |   ^
>   |   VkVideoEncodeH264NaluSliceEXT
> /<>/icd/generated/vk_typemap_helper.h:3317:60: error: 

Bug#1012505: marked as done (debmutate: missing runtime python3-pcre dependency?)

[Debian Bug Tracking System]

Your message dated Mon, 4 Jul 2022 10:00:06 +
with message-id 
and subject line Please see #1013485 for field roundtripping issue
has caused the Debian Bug report #1012505,
regarding debmutate: missing runtime python3-pcre dependency?
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.)


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

Source: debmutate
Version: 0.52
Severity: serious

Hello, building lintian-brush now fails with something like:

fixer test: no-watch-file for debian-watch-file-old-format ... Traceback (most 
recent call last):

  File "/<>/fixers/debian-watch-file-old-format.py", line 5, in 


from debmutate.watch import WatchEditor

  File "/usr/lib/python3/dist-packages/debmutate/watch.py", line 22, in 

import pcre

ModuleNotFoundError: No module named 'pcre'

FAIL

fixer test: outdated for debian-watch-file-old-format ... Traceback (most 
recent call last):

  File "/<>/fixers/debian-watch-file-old-format.py", line 5, in 


from debmutate.watch import WatchEditor

  File "/usr/lib/python3/dist-packages/debmutate/watch.py", line 22, in 

import pcre

ModuleNotFoundError: No module named 'pcre'

FAIL

fixer test: already-updated for debian-watch-file-old-format ... Traceback 
(most recent call last):

  File "/<>/fixers/debian-watch-file-old-format.py", line 5, in 


from debmutate.watch import WatchEditor

  File "/usr/lib/python3/dist-packages/debmutate/watch.py", line 22, in 

import pcre

ModuleNotFoundError: No module named 'pcre'

FAIL

fixer sanity test: debian-watch-file-old-format ... ok

fixer test: simple for debian-watch-uses-insecure-uri ... Traceback (most 
recent call last):

  File "/<>/fixers/debian-watch-uses-insecure-uri.py", line 12, in 


from debmutate.watch import parse_watch_file

  File "/usr/lib/python3/dist-packages/debmutate/watch.py", line 22, in 

import pcre

ModuleNotFoundError: No module named 'pcre'

FAIL

fixer sanity test: debian-watch-uses-insecure-uri ... ok

fixer test: simple for debian-watch-contains-dh_make-template ... Traceback 
(most recent call last):

  File "/<>/fixers/debian-watch-contains-dh_make-template.py", line 3, 
in 

from debmutate.watch import WatchEditor

  File "/usr/lib/python3/dist-packages/debmutate/watch.py", line 22, in 

import pcre

ModuleNotFoundError: No module named 'pcre'

FAIL

I think debmutate should have a runtime dependency on pcre module?

thanks for considering it

Gianfranco
--- End Message ---
--- Begin Message ---
I'm going to mark this as closed since the python3-pcre dependency has been
added. We're tracking the regression in field roundtripping in #1013485.

Jelmer--- End Message ---

Processed: reassign 1013485 to python3-debian

[Debian Bug Tracking System]

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

> reassign 1013485 python3-debian
Bug #1013485 [src:lintian-brush] lintian-brush: FTBFS: AssertionError: 1 != 0
Bug reassigned from package 'src:lintian-brush' to 'python3-debian'.
No longer marked as found in versions lintian-brush/0.126.
Ignoring request to alter fixed versions of bug #1013485 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: affects 1013485

[Debian Bug Tracking System]

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

> affects 1013485 lintian-brush python3-debmutate python3-debian
Bug #1013485 [src:lintian-brush] lintian-brush: FTBFS: AssertionError: 1 != 0
Added indication that 1013485 affects lintian-brush, python3-debmutate, and 
python3-debian
> thanks
Stopping processing here.

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

Processed: Bug#1014214 marked as pending in nodejs

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1014214 [nodejs] missing undici.fetch()
Added tag(s) pending.

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

Bug#1014214: marked as pending in nodejs

[Jérémy Lal]

Control: tag -1 pending

Hello,

Bug #1014214 in nodejs 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/js-team/nodejs/-/commit/a13df8e71fe65e47d6ce74990191aef47a854d10


Patch: disable fetch until undici is accepted (Closes: #1014214)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1014214

Bug#1013607: marked as done (binutils-m68hc1x: FTBFS: tar: /usr/src/binutils/binutils-2.38.50.20220622.tar.xz: Cannot open: No such file or directory)

[Debian Bug Tracking System]

Your message dated Mon, 04 Jul 2022 09:20:42 +
with message-id 
and subject line Bug#1013607: fixed in binutils-m68hc1x 1:3.0.2
has caused the Debian Bug report #1013607,
regarding binutils-m68hc1x: FTBFS: tar: 
/usr/src/binutils/binutils-2.38.50.20220622.tar.xz: Cannot open: No such file 
or directory
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.)


-- 
1013607: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013607
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: binutils-m68hc1x
Version: 1:3.0.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220624 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> mkdir --parent "src"
> dh binary --sourcedirectory="src" --builddirectory
>debian/rules execute_before_dh_update_autotools_config
> make[1]: Entering directory '/<>'
> tar \
>   --extract \
>   --directory="src" \
>   --strip-components=1 \
>   --file="/usr/src/binutils/binutils-2.38.50.20220622.tar.xz"
> tar: /usr/src/binutils/binutils-2.38.50.20220622.tar.xz: Cannot open: No such 
> file or directory
> tar: Error is not recoverable: exiting now
> make[1]: *** [debian/rules:22: execute_before_dh_update_autotools_config] 
> Error 2


The full build log is available from:
http://qa-logs.debian.net/2022/06/24/binutils-m68hc1x_3.0.1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220624;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220624=lu...@debian.org=1=1=1=1#results

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: binutils-m68hc1x
Source-Version: 1:3.0.2
Done: Vincent Smeets 

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

Debian distribution maintenance software
pp.
Vincent Smeets  (supplier of updated 
binutils-m68hc1x package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 24 Jun 2022 16:45:32 +0200
Source: binutils-m68hc1x
Architecture: source
Version: 1:3.0.2
Distribution: unstable
Urgency: medium
Maintainer: Vincent Smeets 
Changed-By: Vincent Smeets 
Closes: 1013607
Changes:
 binutils-m68hc1x (1:3.0.2) unstable; urgency=medium
 .
   * Use the correct tar filename (Closes: #1013607)
   * Enable tests
   * Standards version set to 4.6.1
Checksums-Sha1:
 6ce888a52f133874a55183516afecdf4ef1ea04d 1737 binutils-m68hc1x_3.0.2.dsc
 f547bb40cfbe3467de81ecb8ed1687ebbdc6587f 5676 binutils-m68hc1x_3.0.2.tar.xz
 840e0d5c04b37b1c42d550df35500be49347fa50 6997 
binutils-m68hc1x_3.0.2_amd64.buildinfo
Checksums-Sha256:
 715c04d72c44a947171a27de319a4e2cc069323faaee8e46b1436ffa41f7b701 1737 
binutils-m68hc1x_3.0.2.dsc
 7198cde93622c4bfa5fbebc754503e3d7229c42c15f7466120e5fcb2022db593 5676 
binutils-m68hc1x_3.0.2.tar.xz
 7af8cbac0cedfdcdefa9e359ddbfb8a6bd5510398534544c3c16d21b37542459 6997 
binutils-m68hc1x_3.0.2_amd64.buildinfo
Files:
 60da982db966cf4838765f5d5d01c985 1737 devel optional binutils-m68hc1x_3.0.2.dsc
 b3e749ebbff8bca443ed63e9e0453f15 5676 devel optional 
binutils-m68hc1x_3.0.2.tar.xz
 c8324d35c0466e899a02d98c103d82ec 6997 devel optional 
binutils-m68hc1x_3.0.2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEYv+KdYTgKVaVRgAGdCY7N/W1+RMFAmLCq3wACgkQdCY7N/W1
+ROuUBAArwga3m03+4Co7xe9z65OU3WGibp3CzhzgmTFjotP3wTyXRdvDhrxspgj
MJ+Mfm7jP0L2dMfo1UPnNSIWO7PtnrKg+OGgg/MhZPrJBYgNbLay3OFlLoTb8CPd

Bug#1013771: closing 1013771

[Ilias Tsitsimpis]

close 1013771 0.3.1-1
thanks

Bug#1013650: marked as done (apertium-urd-hin: FTBFS: configure: error: You don't have lrx-comp installed.)

[Debian Bug Tracking System]

Your message dated Mon, 04 Jul 2022 08:48:58 +
with message-id 
and subject line Bug#1013650: fixed in apertium-urd-hin 0.1.0~r64379-4
has caused the Debian Bug report #1013650,
regarding apertium-urd-hin: FTBFS: configure: error: You don't have lrx-comp 
installed.
to be marked as done.

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

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


-- 
1013650: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013650
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: apertium-urd-hin
Version: 0.1.0~r64379-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220624 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> checking for pkg-config... /usr/bin/pkg-config
> checking pkg-config is at least version 0.9.0... yes
> checking for apertium >= 3.3.0... yes
> checking for cg-comp... /usr/bin/cg-comp
> checking for lrx-comp... no
> configure: error: You don't have lrx-comp installed.
>   tail -v -n \+0 config.log


The full build log is available from:
http://qa-logs.debian.net/2022/06/24/apertium-urd-hin_0.1.0~r64379-3_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220624;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220624=lu...@debian.org=1=1=1=1#results

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: apertium-urd-hin
Source-Version: 0.1.0~r64379-4
Done: Kartik Mistry 

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

Debian distribution maintenance software
pp.
Kartik Mistry  (supplier of updated apertium-urd-hin package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 04 Jul 2022 13:32:27 +0530
Source: apertium-urd-hin
Architecture: source
Version: 0.1.0~r64379-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Kartik Mistry 
Closes: 1013650
Changes:
 apertium-urd-hin (0.1.0~r64379-4) unstable; urgency=medium
 .
   * debian/control:
 + Fixed Build-Dep: apertium-lex-tools -> apertium-lex-tools-dev
   (Closes: #1013650)
 + Updated Standards-Version to 4.6.1
Checksums-Sha1:
 25f076870f7ec727f46dd02c6c55783816b23aee 2188 
apertium-urd-hin_0.1.0~r64379-4.dsc
 3b6478b73136a8abc3b3eacb485fe46d059133d8 2496 
apertium-urd-hin_0.1.0~r64379-4.debian.tar.xz
Checksums-Sha256:
 efa700d421e35fb63084fb26e3fff766d60f66a1ff0afcdbdeff40183f5598ba 2188 
apertium-urd-hin_0.1.0~r64379-4.dsc
 8c4a6e105a19175a26b0aa5dc9539e5760251376879ff60f71aea9ce63a61b1c 2496 
apertium-urd-hin_0.1.0~r64379-4.debian.tar.xz
Files:
 268e142fad9e2671d136f7bf947cb631 2188 science optional 
apertium-urd-hin_0.1.0~r64379-4.dsc
 560e638bce959d4edd83dfb00d84c9de 2496 science optional 
apertium-urd-hin_0.1.0~r64379-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEa2MbXvVUr2sRlmKSAsHT8ng6pN4FAmLCpPkACgkQAsHT8ng6
pN6YbhAAotkUl58Gbhdz0pkIhaWlFh/4jWwIg1JlKJHOL6OFTW7hzaZmJdaWtnf2
/RlV6tOcG6PeuoNctxcwb0Ehx3X840VyUEpk27H1OLkF7jAfJWagk7jNYlz9MdRs
ObY+OJzvf1253OFsEB1QQrrvzi8uXx9AX88k7P3TUVh2Amq3ObACzX/3fv1eljff
5j1m6CRO1zNn8NXXUUxBmsjkIUCvzsmxWGJwA3XYud+I2W1TNW2j6ERwtuNjxNYv
vBDZVSQniXxuCx/1dAXomaqgzqkkeqXfheyAFIy5BpKFGL5h7mEeALVjwL/fsp1D
91F3Ty+0kq09BOV+NFtjk37/gdatJXCDtx9td+vmqeIfcpUvIkkzyhxUhON9ypJp
dtyZIUW4iwrXtFwd4SainPIY/GuEfx6PJk58V8LJU2R5LFSP4e/m88wmOgcejlka
uugaWqw1u29G/ur5QuIW6qCjcEDd1HnoJWJFlMpgxprHJlB67k19IEQdQaji9n3G
Tx4foOO9tip76EWgwn232X3jqMURIWUvuqTKmwaz67dTDK1GVT/TB9Op8MZYeu6b

Bug#1011916: marked as done (poolcounter: FTBFS: dh_auto_test: error: make -j8 test returned exit code 2)

[Debian Bug Tracking System]

Your message dated Mon, 04 Jul 2022 08:41:25 +
with message-id 
and subject line Bug#1011916: fixed in poolcounter 1.1.3-2
has caused the Debian Bug report #1011916,
regarding poolcounter: FTBFS: dh_auto_test: error: make -j8 test 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.)


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> /usr/bin/pytest /usr/bin/pytest-3 -v
> = test session starts 
> ==
> platform linux -- Python 3.10.4, pytest-6.2.5, py-1.10.0, pluggy-1.0.0 -- 
> /usr/bin/python3
> cachedir: .pytest_cache
> rootdir: /usr/bin
> collecting ... ERROR: not found: /usr/bin/pytest-3
> (no name '/usr/bin/pytest-3' in any of [])
> 
> collected 0 items
> 
> === warnings summary 
> ===
> ../../../usr/lib/python3/dist-packages/_pytest/cacheprovider.py:428
>   /usr/lib/python3/dist-packages/_pytest/cacheprovider.py:428: 
> PytestCacheWarning: could not create cache path 
> /usr/bin/.pytest_cache/v/cache/nodeids
> config.cache.set("cache/nodeids", sorted(self.cached_nodeids))
> 
> ../../../usr/lib/python3/dist-packages/_pytest/stepwise.py:49
>   /usr/lib/python3/dist-packages/_pytest/stepwise.py:49: PytestCacheWarning: 
> could not create cache path /usr/bin/.pytest_cache/v/cache/stepwise
> session.config.cache.set(STEPWISE_CACHE_DIR, [])
> 
> -- Docs: https://docs.pytest.org/en/stable/warnings.html
> = 2 warnings in 0.00s 
> ==
> make[1]: *** [Makefile:28: test] Error 4
> make[1]: Leaving directory '/<>'
> dh_auto_test: error: make -j8 test returned exit code 2


The full build log is available from:
http://qa-logs.debian.net/2022/05/25/poolcounter_1.1.3-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220525;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220525=lu...@debian.org=1=1=1=1#results

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: poolcounter
Source-Version: 1.1.3-2
Done: Kunal Mehta 

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

Debian distribution maintenance software
pp.
Kunal Mehta  (supplier of updated poolcounter package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 02 Jul 2022 15:26:05 -0700
Source: poolcounter
Architecture: source
Version: 1.1.3-2
Distribution: unstable
Urgency: low
Maintainer: MediaWiki packaging team 
Changed-By: Kunal Mehta 
Closes: 1011916
Changes:
 poolcounter (1.1.3-2) unstable; urgency=low
 .
   * Bump debhelper from old 11 to 12.
   * Set debhelper-compat version in Build-Depends.
   * Update standards version to 4.5.0, no changes needed.
   * Use plain `pytest` for tests (Closes: #1011916)
Checksums-Sha1:
 1271b8e653ed51842ab2df371eb3208ad1746305 2065 poolcounter_1.1.3-2.dsc
 51269c5b9952aededf73199a21cb49bc1cb23e3f 3532 poolcounter_1.1.3-2.debian.tar.xz
 d956c9788017489d572bbc95bda57a0d6a1945a6 7119 
poolcounter_1.1.3-2_amd64.buildinfo
Checksums-Sha256:
 aaefdd75a8d684eeefecc32d65e114108c127c559a0f6ebeb3396259389de76a 

Processed: closing 1013771

[Debian Bug Tracking System]

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

> close 1013771 0.3.1-1
Bug #1013771 [src:haskell-statestack] haskell-statestack FTBFS: Encountered 
missing or private dependencies: base >=4.8 && <4.14
Marked as fixed in versions haskell-statestack/0.3.1-1.
Bug #1013771 [src:haskell-statestack] haskell-statestack FTBFS: Encountered 
missing or private dependencies: base >=4.8 && <4.14
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1013645: marked as done (apertium-spa-cat: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.2) were not met)

[Debian Bug Tracking System]

Your message dated Mon, 04 Jul 2022 08:35:02 +
with message-id 
and subject line Bug#1013645: fixed in apertium-spa-cat 2.2.0-3
has caused the Debian Bug report #1013645,
regarding apertium-spa-cat: FTBFS: configure: error: Package requirements 
(apertium-lex-tools >= 0.2.2) were not met
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.)


-- 
1013645: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013645
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: apertium-spa-cat
Version: 2.2.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220624 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> checking for gawk... (cached) gawk
> checking for pkg-config... /usr/bin/pkg-config
> checking pkg-config is at least version 0.9.0... yes
> checking for apertium >= 3.6.0... yes
> checking for apertium-lex-tools >= 0.2.2... no
> configure: error: Package requirements (apertium-lex-tools >= 0.2.2) were not 
> met
> 
> No package 'apertium-lex-tools' found
> 
> Consider adjusting the PKG_CONFIG_PATH environment variable if you
> installed software in a non-standard prefix.
> 
> Alternatively, you may set the environment variables APERTIUM_LEX_TOOLS_CFLAGS
> and APERTIUM_LEX_TOOLS_LIBS to avoid the need to call pkg-config.
> See the pkg-config man page for more details.
> make[1]: *** [debian/rules:17: override_dh_auto_configure] Error 1
> make[1]: Leaving directory '/<>'


The full build log is available from:
http://qa-logs.debian.net/2022/06/24/apertium-spa-cat_2.2.0-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220624;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220624=lu...@debian.org=1=1=1=1#results

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: apertium-spa-cat
Source-Version: 2.2.0-3
Done: Kartik Mistry 

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

Debian distribution maintenance software
pp.
Kartik Mistry  (supplier of updated apertium-spa-cat package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 04 Jul 2022 12:45:12 +0530
Source: apertium-spa-cat
Architecture: source
Version: 2.2.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Kartik Mistry 
Closes: 1013645
Changes:
 apertium-spa-cat (2.2.0-3) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Remove constraints unnecessary since buster:
 + apertium-spa-cat: Drop versioned constraint on apertium-es-ca in 
Replaces.
 + apertium-spa-cat: Drop versioned constraint on apertium-es-ca in Breaks.
 .
   [ Kartik Mistry ]
   * debian/control:
 + Fixed Build-Depends: apertium-lex-tools -> apertium-lex-tools-dev
   (Closes: #1013645)
 + Updated Standards-Version to 4.6.1
   * Updated debian/copyright.
   * Updated debian/watch.
Checksums-Sha1:
 4a238969ddff3be680e9732aadce0e48b8e03a75 2184 apertium-spa-cat_2.2.0-3.dsc
 37b68198ebafb85a81691a4b4337901575a856fd 3972 
apertium-spa-cat_2.2.0-3.debian.tar.xz
Checksums-Sha256:
 a8d72a280728e6a3599db1ebabe5bc46fba2eb6c1ce88a4e67235d02a82e83d0 2184 
apertium-spa-cat_2.2.0-3.dsc
 559e504af935ee2459ea88f8747c76f49a47f0cab06837a9b171e67b97607d59 3972 
apertium-spa-cat_2.2.0-3.debian.tar.xz
Files:
 9586322b5e51ad3ff4b55288b2d3202f 2184 science optional 
apertium-spa-cat_2.2.0-3.dsc
 211e0093c6a5b7b7b74865645eca6a02 3972 science optional 

Bug#1014180: marked as done (src:boost1.74: Cleanup code of boost::asio causes crashes with OpenSSL 3+)

[Debian Bug Tracking System]

Your message dated Mon, 04 Jul 2022 07:49:12 +
with message-id 
and subject line Bug#1014180: fixed in boost1.74 1.74.0-16.1
has caused the Debian Bug report #1014180,
regarding src:boost1.74: Cleanup code of boost::asio causes crashes with 
OpenSSL 3+
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.)


-- 
1014180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014180
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: boost1.74
Version: 1.74.0-16
Severity: grave
Tags: patch, upstream
X-Debbugs-Cc: Hilko Bengen 

Dear Maintainer,

I recently received #1013470 (nbdkit FTBFS because of segfaults when
running test suite); this turned out to be caused by #1013931 (segfault
in libtorrent-rasterbar cleanup code), I was able to track the root
cause to an incomplete #ifdef condition in
libs/asio/include//boost/asio/ssl/detail/impl/openssl_init.ipp as of
1.74.0-16 that caused CONF_modules_unload to crash after OpenSSL 3.0+
had done its own cleanup which included calling that function.

(See discussion in .)

Please apply upstream's patch
.

After applying this patch, and rebuilding boost1.74 +
libtorrent-rasterbar, I am no longer able to reproduce the sagfaults.

Cheers,
-Hilko
--- End Message ---
--- Begin Message ---
Source: boost1.74
Source-Version: 1.74.0-16.1
Done: Gianfranco Costamagna 

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

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated boost1.74 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 04 Jul 2022 09:34:02 +0200
Source: boost1.74
Built-For-Profiles: noudeb
Architecture: source
Version: 1.74.0-16.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Boost Team 
Changed-By: Gianfranco Costamagna 
Closes: 1013472 1013530 1014180
Changes:
 boost1.74 (1.74.0-16.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/patches/74a94fe7f47b2e3f707cf4589fbb635a50f22ad2.patch:
 - cherry-pick upstream asio change to fix exit failures with openssl 3.0.4
   Closes: #1014180, #1013530, #1013472 and many others probably
Checksums-Sha1:
 d58a7dcb8da934102f96122f9bb0b1dbeba23d71 9118 boost1.74_1.74.0-16.1.dsc
 292723aafe4a8297d4d0627e285e5422d8b79726 372764 
boost1.74_1.74.0-16.1.debian.tar.xz
 3f6bdb5db4febb7b53b958c34dac5a86be2b559f 9875 
boost1.74_1.74.0-16.1_source.buildinfo
Checksums-Sha256:
 8633b063161f1d0e47900d0e1f63f20252f0d9a51b8819e84b66ef6952c0a52e 9118 
boost1.74_1.74.0-16.1.dsc
 16051b2b3aad9248936290e04f97a5586925c5e6104f7bc3968ab17bd5284648 372764 
boost1.74_1.74.0-16.1.debian.tar.xz
 2d7cdceee0a9cbf494e5618e7af0d783c43fc50a612e8b8e0d9e2e8bf017b3d6 9875 
boost1.74_1.74.0-16.1_source.buildinfo
Files:
 9c73424927c50e038b09deafcd65b014 9118 libs optional boost1.74_1.74.0-16.1.dsc
 651d18ce45a3f7d15d3b604e54c8cad4 372764 libs optional 
boost1.74_1.74.0-16.1.debian.tar.xz
 bd943e11074e26ff2af827d76189c2bb 9875 libs optional 
boost1.74_1.74.0-16.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAmLCmcAACgkQ808JdE6f
XdlwBQ/9E8wJDFpsQVtX1WCxCW9yppaxAF+i1SxrAzLStLa9lllTrqqkcvM9/xYe
xOFaObBlYq3YLMIGZoVYcpkgfSh2Q1UL+Y32V4EQVRbrF7OdgZM1I6AF0xXBlMK0
J1HRdh+YEZHQxbDxL/KSP/FzJs6X1BOhee/qb3hc4tIBu6Dby5CfeyQ5NWFbOMj7
8orBZm9SOlHz0bOXSOSjcKJIXCMX2XCfeb4eiUpjUqESovB2Ey/AJPWQJkZykaGL
MDqPvVctF5qV4Lj08dPYQiBlwKaZ17+/BdJ6tMdngQJ8TGQzUIcdeHqAarnfcXd1
Ef1oNQcFx1E7Fm59qVgX3UarCnvT7xsju99GYbXEhxAFnQ8bR/V07KpkY/ZmJcy2
E81+OE6eRdaZtLTEqg9myieocxWGR7iYhdZEkOruy8y7sb/DJ8zc2HbISu3LmjV5
mOosl3bgD9PJIsh9nUMDYDAfZZtWVDWTOccVpet2ueiq01ZTmCOM09G6277pfu7e
YwFQ1KFK1Fkqw1SssrDw8tXBD6SR7bcNzNZfOqlE0VvGNA9os027kmxosQ9Wn8Nb
hJ/WQWDKD2JzhpURL5QsgcTWhKCDMpAAUGuc6T0L8Clo+SaV7Rxh6STkg8WpIQKI
DkEY5S16ibhR9NJW4y0iM7NJ8ZY+dBz98+LYSkOkH1sLqyQ4eNE=
=Ado0
-END PGP SIGNATURE End Message ---

Bug#1014180: marked as done (src:boost1.74: Cleanup code of boost::asio causes crashes with OpenSSL 3+)

[Debian Bug Tracking System]

Your message dated Mon, 04 Jul 2022 07:49:12 +
with message-id 
and subject line Bug#1013530: fixed in boost1.74 1.74.0-16.1
has caused the Debian Bug report #1013530,
regarding src:boost1.74: Cleanup code of boost::asio causes crashes with 
OpenSSL 3+
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.)


-- 
1013530: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013530
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: boost1.74
Version: 1.74.0-16
Severity: grave
Tags: patch, upstream
X-Debbugs-Cc: Hilko Bengen 

Dear Maintainer,

I recently received #1013470 (nbdkit FTBFS because of segfaults when
running test suite); this turned out to be caused by #1013931 (segfault
in libtorrent-rasterbar cleanup code), I was able to track the root
cause to an incomplete #ifdef condition in
libs/asio/include//boost/asio/ssl/detail/impl/openssl_init.ipp as of
1.74.0-16 that caused CONF_modules_unload to crash after OpenSSL 3.0+
had done its own cleanup which included calling that function.

(See discussion in .)

Please apply upstream's patch
.

After applying this patch, and rebuilding boost1.74 +
libtorrent-rasterbar, I am no longer able to reproduce the sagfaults.

Cheers,
-Hilko
--- End Message ---
--- Begin Message ---
Source: boost1.74
Source-Version: 1.74.0-16.1
Done: Gianfranco Costamagna 

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

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated boost1.74 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 04 Jul 2022 09:34:02 +0200
Source: boost1.74
Built-For-Profiles: noudeb
Architecture: source
Version: 1.74.0-16.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Boost Team 
Changed-By: Gianfranco Costamagna 
Closes: 1013472 1013530 1014180
Changes:
 boost1.74 (1.74.0-16.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/patches/74a94fe7f47b2e3f707cf4589fbb635a50f22ad2.patch:
 - cherry-pick upstream asio change to fix exit failures with openssl 3.0.4
   Closes: #1014180, #1013530, #1013472 and many others probably
Checksums-Sha1:
 d58a7dcb8da934102f96122f9bb0b1dbeba23d71 9118 boost1.74_1.74.0-16.1.dsc
 292723aafe4a8297d4d0627e285e5422d8b79726 372764 
boost1.74_1.74.0-16.1.debian.tar.xz
 3f6bdb5db4febb7b53b958c34dac5a86be2b559f 9875 
boost1.74_1.74.0-16.1_source.buildinfo
Checksums-Sha256:
 8633b063161f1d0e47900d0e1f63f20252f0d9a51b8819e84b66ef6952c0a52e 9118 
boost1.74_1.74.0-16.1.dsc
 16051b2b3aad9248936290e04f97a5586925c5e6104f7bc3968ab17bd5284648 372764 
boost1.74_1.74.0-16.1.debian.tar.xz
 2d7cdceee0a9cbf494e5618e7af0d783c43fc50a612e8b8e0d9e2e8bf017b3d6 9875 
boost1.74_1.74.0-16.1_source.buildinfo
Files:
 9c73424927c50e038b09deafcd65b014 9118 libs optional boost1.74_1.74.0-16.1.dsc
 651d18ce45a3f7d15d3b604e54c8cad4 372764 libs optional 
boost1.74_1.74.0-16.1.debian.tar.xz
 bd943e11074e26ff2af827d76189c2bb 9875 libs optional 
boost1.74_1.74.0-16.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAmLCmcAACgkQ808JdE6f
XdlwBQ/9E8wJDFpsQVtX1WCxCW9yppaxAF+i1SxrAzLStLa9lllTrqqkcvM9/xYe
xOFaObBlYq3YLMIGZoVYcpkgfSh2Q1UL+Y32V4EQVRbrF7OdgZM1I6AF0xXBlMK0
J1HRdh+YEZHQxbDxL/KSP/FzJs6X1BOhee/qb3hc4tIBu6Dby5CfeyQ5NWFbOMj7
8orBZm9SOlHz0bOXSOSjcKJIXCMX2XCfeb4eiUpjUqESovB2Ey/AJPWQJkZykaGL
MDqPvVctF5qV4Lj08dPYQiBlwKaZ17+/BdJ6tMdngQJ8TGQzUIcdeHqAarnfcXd1
Ef1oNQcFx1E7Fm59qVgX3UarCnvT7xsju99GYbXEhxAFnQ8bR/V07KpkY/ZmJcy2
E81+OE6eRdaZtLTEqg9myieocxWGR7iYhdZEkOruy8y7sb/DJ8zc2HbISu3LmjV5
mOosl3bgD9PJIsh9nUMDYDAfZZtWVDWTOccVpet2ueiq01ZTmCOM09G6277pfu7e
YwFQ1KFK1Fkqw1SssrDw8tXBD6SR7bcNzNZfOqlE0VvGNA9os027kmxosQ9Wn8Nb
hJ/WQWDKD2JzhpURL5QsgcTWhKCDMpAAUGuc6T0L8Clo+SaV7Rxh6STkg8WpIQKI
DkEY5S16ibhR9NJW4y0iM7NJ8ZY+dBz98+LYSkOkH1sLqyQ4eNE=
=Ado0
-END PGP SIGNATURE End Message ---

Bug#1014180: marked as done (src:boost1.74: Cleanup code of boost::asio causes crashes with OpenSSL 3+)

[Debian Bug Tracking System]

Your message dated Mon, 04 Jul 2022 07:49:12 +
with message-id 
and subject line Bug#1013472: fixed in boost1.74 1.74.0-16.1
has caused the Debian Bug report #1013472,
regarding src:boost1.74: Cleanup code of boost::asio causes crashes with 
OpenSSL 3+
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.)


-- 
1013472: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013472
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: boost1.74
Version: 1.74.0-16
Severity: grave
Tags: patch, upstream
X-Debbugs-Cc: Hilko Bengen 

Dear Maintainer,

I recently received #1013470 (nbdkit FTBFS because of segfaults when
running test suite); this turned out to be caused by #1013931 (segfault
in libtorrent-rasterbar cleanup code), I was able to track the root
cause to an incomplete #ifdef condition in
libs/asio/include//boost/asio/ssl/detail/impl/openssl_init.ipp as of
1.74.0-16 that caused CONF_modules_unload to crash after OpenSSL 3.0+
had done its own cleanup which included calling that function.

(See discussion in .)

Please apply upstream's patch
.

After applying this patch, and rebuilding boost1.74 +
libtorrent-rasterbar, I am no longer able to reproduce the sagfaults.

Cheers,
-Hilko
--- End Message ---
--- Begin Message ---
Source: boost1.74
Source-Version: 1.74.0-16.1
Done: Gianfranco Costamagna 

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

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated boost1.74 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 04 Jul 2022 09:34:02 +0200
Source: boost1.74
Built-For-Profiles: noudeb
Architecture: source
Version: 1.74.0-16.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Boost Team 
Changed-By: Gianfranco Costamagna 
Closes: 1013472 1013530 1014180
Changes:
 boost1.74 (1.74.0-16.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/patches/74a94fe7f47b2e3f707cf4589fbb635a50f22ad2.patch:
 - cherry-pick upstream asio change to fix exit failures with openssl 3.0.4
   Closes: #1014180, #1013530, #1013472 and many others probably
Checksums-Sha1:
 d58a7dcb8da934102f96122f9bb0b1dbeba23d71 9118 boost1.74_1.74.0-16.1.dsc
 292723aafe4a8297d4d0627e285e5422d8b79726 372764 
boost1.74_1.74.0-16.1.debian.tar.xz
 3f6bdb5db4febb7b53b958c34dac5a86be2b559f 9875 
boost1.74_1.74.0-16.1_source.buildinfo
Checksums-Sha256:
 8633b063161f1d0e47900d0e1f63f20252f0d9a51b8819e84b66ef6952c0a52e 9118 
boost1.74_1.74.0-16.1.dsc
 16051b2b3aad9248936290e04f97a5586925c5e6104f7bc3968ab17bd5284648 372764 
boost1.74_1.74.0-16.1.debian.tar.xz
 2d7cdceee0a9cbf494e5618e7af0d783c43fc50a612e8b8e0d9e2e8bf017b3d6 9875 
boost1.74_1.74.0-16.1_source.buildinfo
Files:
 9c73424927c50e038b09deafcd65b014 9118 libs optional boost1.74_1.74.0-16.1.dsc
 651d18ce45a3f7d15d3b604e54c8cad4 372764 libs optional 
boost1.74_1.74.0-16.1.debian.tar.xz
 bd943e11074e26ff2af827d76189c2bb 9875 libs optional 
boost1.74_1.74.0-16.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAmLCmcAACgkQ808JdE6f
XdlwBQ/9E8wJDFpsQVtX1WCxCW9yppaxAF+i1SxrAzLStLa9lllTrqqkcvM9/xYe
xOFaObBlYq3YLMIGZoVYcpkgfSh2Q1UL+Y32V4EQVRbrF7OdgZM1I6AF0xXBlMK0
J1HRdh+YEZHQxbDxL/KSP/FzJs6X1BOhee/qb3hc4tIBu6Dby5CfeyQ5NWFbOMj7
8orBZm9SOlHz0bOXSOSjcKJIXCMX2XCfeb4eiUpjUqESovB2Ey/AJPWQJkZykaGL
MDqPvVctF5qV4Lj08dPYQiBlwKaZ17+/BdJ6tMdngQJ8TGQzUIcdeHqAarnfcXd1
Ef1oNQcFx1E7Fm59qVgX3UarCnvT7xsju99GYbXEhxAFnQ8bR/V07KpkY/ZmJcy2
E81+OE6eRdaZtLTEqg9myieocxWGR7iYhdZEkOruy8y7sb/DJ8zc2HbISu3LmjV5
mOosl3bgD9PJIsh9nUMDYDAfZZtWVDWTOccVpet2ueiq01ZTmCOM09G6277pfu7e
YwFQ1KFK1Fkqw1SssrDw8tXBD6SR7bcNzNZfOqlE0VvGNA9os027kmxosQ9Wn8Nb
hJ/WQWDKD2JzhpURL5QsgcTWhKCDMpAAUGuc6T0L8Clo+SaV7Rxh6STkg8WpIQKI
DkEY5S16ibhR9NJW4y0iM7NJ8ZY+dBz98+LYSkOkH1sLqyQ4eNE=
=Ado0
-END PGP SIGNATURE End Message ---

Bug#1013362: marked as done (src:alt-ergo: fails to migrate to testing for too long: FTBFS on armel, mips64el and mipsel)

[Debian Bug Tracking System]

Your message dated Mon, 04 Jul 2022 07:48:58 +
with message-id 
and subject line Bug#1013362: fixed in alt-ergo 2.4.1-4
has caused the Debian Bug report #1013362,
regarding src:alt-ergo: fails to migrate to testing for too long: FTBFS on 
armel, mips64el and mipsel
to be marked as done.

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

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


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

Source: alt-ergo
Version: 2.0.0-8
Severity: serious
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:alt-ergo has been trying to migrate for 61 
days [2]. Hence, I am filing this bug. The latest uploads of your 
package failed to build on armel, mips64el and mipsel [3].


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=alt-ergo
[3] https://buildd.debian.org/status/package.php?p=alt-ergo


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: alt-ergo
Source-Version: 2.4.1-4
Done: Julien Puydt 

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

Debian distribution maintenance software
pp.
Julien Puydt  (supplier of updated alt-ergo package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 04 Jul 2022 09:30:03 +0200
Source: alt-ergo
Architecture: source
Version: 2.4.1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers 
Changed-By: Julien Puydt 
Closes: 1013362
Changes:
 alt-ergo (2.4.1-4) unstable; urgency=medium
 .
   * Add conditional patch for non-native architectures. (Closes: #1013362)
Checksums-Sha1:
 7318fae1721058c0116cdc0087bfb4779690514b 2282 alt-ergo_2.4.1-4.dsc
 bf110ad335b00ee9e78ac1958dd6b3c06369bb6e 8112 alt-ergo_2.4.1-4.debian.tar.xz
 bed0080a97637c22d655ba7362998a26788af80e 15666 
alt-ergo_2.4.1-4_source.buildinfo
Checksums-Sha256:
 181938c414e1768a4cb8ce3414bf8a93be7d0a7a5933d15a2bd414cf50eee7a3 2282 
alt-ergo_2.4.1-4.dsc
 ef711d0e7ce3452433b7cb5c49bddeb902e4a483d2ade2246c608830761f78a8 8112 
alt-ergo_2.4.1-4.debian.tar.xz
 c7f12cc415aeeff8246b6fcb68faa6e34718001c4f41e86b39aa0279a17856f4 15666 
alt-ergo_2.4.1-4_source.buildinfo
Files:
 0a1a73c50360b0a28ecd14a205bc66d9 2282 math optional alt-ergo_2.4.1-4.dsc
 e8bc150888341f45e2923f47984b26ba 8112 math optional 
alt-ergo_2.4.1-4.debian.tar.xz
 480a429a19e474818b5f2f2e7b3afc2b 15666 math optional 
alt-ergo_2.4.1-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEgS7v2KP7pKzk3xFLBMU71/4DBVEFAmLClzQSHGpwdXlkdEBk
ZWJpYW4ub3JnAAoJEATFO9f+AwVRP8QP/if8cbfXlWfBoH7GPYF8JqTFl9ZFCyVL
2t19urpQImjNm57E5lCWa6VyKR2Fzxx/YiD1G1HZd8HJKd47zpkiCgxMspuJKQGl
BefhJ0/mzYkDgzN4NjGidxFAIakEwtWugXa4GzM+zR0xTzl8l9jx15vcP55IBdt9

Bug#1014180: src:boost1.74: Cleanup code of boost::asio causes crashes with OpenSSL 3+

[Gianfranco Costamagna]

Hello, since this bug is really impacting lots of packages, I'm NMUing right 
now.

I spent lots of time trying to understand why cpprest and websocketpp were failing 
testsuite after printing "test OK",
digged into openssl code, and after a while I got the issue on boost side. 
Better avoid other people loosing that much time :)

diff attached, and big thanks to Hilko for opening this bug!

G.

On Fri, 1 Jul 2022 18:32:12 +0200 Gianfranco Costamagna 
 wrote:

Hello Hilko
On Fri, 01 Jul 2022 18:03:10 +0200 Hilko Bengen  wrote:
> Source: boost1.74
> Version: 1.74.0-16
> Severity: grave
> Tags: patch, upstream
> X-Debbugs-Cc: Hilko Bengen 
> 
> Dear Maintainer,
> 
> I recently received #1013470 (nbdkit FTBFS because of segfaults when

> running test suite); this turned out to be caused by #1013931 (segfault
> in libtorrent-rasterbar cleanup code), I was able to track the root
> cause to an incomplete #ifdef condition in
> libs/asio/include//boost/asio/ssl/detail/impl/openssl_init.ipp as of
> 1.74.0-16 that caused CONF_modules_unload to crash after OpenSSL 3.0+
> had done its own cleanup which included calling that function.
> 
> (See discussion in .)
> 
> Please apply upstream's patch

> 
.
> 
> After applying this patch, and rebuilding boost1.74 +

> libtorrent-rasterbar, I am no longer able to reproduce the sagfaults.

I found the very same issue on cpprest and websocketpp but I couldn't go deeper 
into asio code and find the patch.

I merged the other bugs to this one, but I don't know how many others are there.

We should NMU ASAP.

G.

diff -Nru boost1.74-1.74.0/debian/changelog boost1.74-1.74.0/debian/changelog
--- boost1.74-1.74.0/debian/changelog   2022-06-02 06:26:21.0 +0200
+++ boost1.74-1.74.0/debian/changelog   2022-07-04 09:34:02.0 +0200
@@ -1,3 +1,12 @@
+boost1.74 (1.74.0-16.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/patches/74a94fe7f47b2e3f707cf4589fbb635a50f22ad2.patch:
+- cherry-pick upstream asio change to fix exit failures with openssl 3.0.4
+  Closes: #1014180, #1013530, #1013472 and many others probably
+
+ -- Gianfranco Costamagna   Mon, 04 Jul 2022 
09:34:02 +0200
+
 boost1.74 (1.74.0-16) unstable; urgency=medium
 
   [ Bernhard Übelacker ]
diff -Nru 
boost1.74-1.74.0/debian/patches/74a94fe7f47b2e3f707cf4589fbb635a50f22ad2.patch 
boost1.74-1.74.0/debian/patches/74a94fe7f47b2e3f707cf4589fbb635a50f22ad2.patch
--- 
boost1.74-1.74.0/debian/patches/74a94fe7f47b2e3f707cf4589fbb635a50f22ad2.patch  
1970-01-01 01:00:00.0 +0100
+++ 
boost1.74-1.74.0/debian/patches/74a94fe7f47b2e3f707cf4589fbb635a50f22ad2.patch  
2022-07-04 09:34:02.0 +0200
@@ -0,0 +1,29 @@
+From 74a94fe7f47b2e3f707cf4589fbb635a50f22ad2 Mon Sep 17 00:00:00 2001
+From: Christopher Kohlhoff 
+Date: Thu, 30 Jun 2022 00:29:55 +1000
+Subject: [PATCH] Fix compatibility with OpenSSL 3.0.4 and later.
+
+---
+ libs/asio/include/boost/asio/ssl/detail/impl/openssl_init.ipp | 8 ++--
+ 1 file changed, 6 insertions(+), 2 deletions(-)
+
+diff --git a/libs/asio/include/boost/asio/ssl/detail/impl/openssl_init.ipp 
b/libs/asio/include/boost/asio/ssl/detail/impl/openssl_init.ipp
+index 3555caaab..8357146f9 100644
+--- a/libs/asio/include/boost/asio/ssl/detail/impl/openssl_init.ipp
 b/libs/asio/include/boost/asio/ssl/detail/impl/openssl_init.ipp
+@@ -86,9 +86,13 @@ public:
+ #endif // (OPENSSL_VERSION_NUMBER >= 0x10002000L)
+// && (OPENSSL_VERSION_NUMBER < 0x1010L)
+// && !defined(SSL_OP_NO_COMPRESSION)
+-#if !defined(OPENSSL_IS_BORINGSSL) && !defined(BOOST_ASIO_USE_WOLFSSL)
++#if !defined(OPENSSL_IS_BORINGSSL) \
++&& !defined(BOOST_ASIO_USE_WOLFSSL) \
++&& (OPENSSL_VERSION_NUMBER < 0x3000L)
+ ::CONF_modules_unload(1);
+-#endif // !defined(OPENSSL_IS_BORINGSSL) && !defined(BOOST_ASIO_USE_WOLFSSL)
++#endif // !defined(OPENSSL_IS_BORINGSSL)
++   //   && !defined(BOOST_ASIO_USE_WOLFSSL)
++   //   && (OPENSSL_VERSION_NUMBER < 0x3000L)
+ #if !defined(OPENSSL_NO_ENGINE) \
+   && (OPENSSL_VERSION_NUMBER < 0x1010L)
+ ::ENGINE_cleanup();
diff -Nru boost1.74-1.74.0/debian/patches/series 
boost1.74-1.74.0/debian/patches/series
--- boost1.74-1.74.0/debian/patches/series  2022-06-02 06:26:02.0 
+0200
+++ boost1.74-1.74.0/debian/patches/series  2022-07-04 09:34:02.0 
+0200
@@ -24,3 +24,4 @@
 fix_b2_freebsd.patch
 fix_utime_omit_freebsd.patch
 fix-enum.patch
+74a94fe7f47b2e3f707cf4589fbb635a50f22ad2.patch

Bug#1009458: marked as done (vitables: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.10 returned exit code 13)

[Debian Bug Tracking System]

Your message dated Mon, 04 Jul 2022 07:35:08 +
with message-id 
and subject line Bug#1009458: fixed in vitables 3.0.2-3
has caused the Debian Bug report #1009458,
regarding vitables: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i 
python{version} -p 3.10 returned exit code 13
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.)


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

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>/doc'
> sphinx-build -b qthelp -d _build/doctrees   . _build/qthelp
> Running Sphinx v4.5.0
> making output directory... done
> loading pickled environment... done
> building [mo]: targets for 0 po files that are out of date
> building [qthelp]: targets for 9 source files that are out of date
> updating environment: 0 added, 0 changed, 0 removed
> looking for now-outdated files... none found
> preparing documents... done
> writing output... [ 11%] develop
> writing output... [ 22%] index
> writing output... [ 33%] usersguide-app1
> writing output... [ 44%] usersguide-app2
> writing output... [ 55%] usersguide-ch1
> writing output... [ 66%] usersguide-ch2
> writing output... [ 77%] usersguide-ch3
> writing output... [ 88%] usersguide-ch4
> writing output... [100%] usersguide-ch5
> 
> generating indices... genindex done
> writing additional pages... done
> copying images... [ 10%] images/title_page_plain.png
> copying images... [ 20%] images/helpBrowser.png
> copying images... [ 30%] images/mainWindow.png
> copying images... [ 40%] images/treeSymbols.png
> copying images... [ 50%] images/browseDataset.png
> copying images... [ 60%] images/zoomingCells.png
> copying images... [ 70%] images/propertiesDlg.png
> copying images... [ 80%] images/newFilteredTable.png
> copying images... [ 90%] images/groupCreation.png
> copying images... [100%] images/editingUserAttrs.png
> 
> copying static files... done
> copying extra files... done
> writing project file...
> writing collection project file...
> build succeeded.
> 
> You can now run "qcollectiongenerator" with the .qhcp project file in 
> _build/qthelp, like this:
> $ qcollectiongenerator _build/qthelp/ViTables Users' Guide.qhcp
> To view the help file:
> $ assistant -collectionFile _build/qthelp/ViTables Users' Guide.qhc
> 
> Build finished; now you can run qcollectiongenerator with the .qhcp project 
> file in _build/qthelp, like this:
> # qcollectiongenerator _build/qthelp/ViTablesUsersGuide.qhcp
> To view the help file:
> # assistant -collectionFile _build/qthelp/ViTablesUsersGuide.qhc
> make[2]: Leaving directory '/<>/doc'
> cd doc/_build && rm -r html && mv qthelp html && rm html/_static/*.js
> make[1]: Leaving directory '/<>'
>dh_auto_test -O--buildsystem=pybuild
>   pybuild --test --test-pytest -i python{version} -p 3.10
> I: pybuild base:239: cd /<>/.pybuild/cpython3_3.10/build; 
> python3.10 -m pytest tests
> = test session starts 
> ==
> platform linux -- Python 3.10.4, pytest-6.2.5, py-1.10.0, pluggy-1.0.0
> rootdir: /<>
> plugins: xvfb-2.0.0
> collected 54 items
> 
> tests/test_filenode.py EE[ 
> 11%]
> tests/test_logger.py E   [ 
> 20%]
> tests/test_utils.py  [ 
> 42%]
> tests/test_vtconfig.py EEE   [ 
> 62%]
> tests/test_vtgui.py  
> [100%]
> 
>  ERRORS 
> 
>  ERROR at setup of TestFilenode.test_isFilenode 
> 
> 
> @pytest.fixture(scope='module')
> def launcher():
> >   return Launcher()
> 
> tests/conftest.py:33: 
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> tests/conftest.py:27: in __init__
> self.vtapp_object = vitables.vtapp.VTApp(keep_splash=False)
> vitables/vtapp.py:139: in __init__
> self.csv_importer = importcsv.ImportCSV()
> vitables/csv/import_csv.py:102: in __init__
> self.addEntry()
> vitables/csv/import_csv.py:176: in addEntry
> vitables.utils.insertInMenu(
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

Processed: Bug#1013362 marked as pending in alt-ergo

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1013362 [src:alt-ergo] src:alt-ergo: fails to migrate to testing for too 
long: FTBFS on armel, mips64el and mipsel
Added tag(s) pending.

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

Bug#1013362: marked as pending in alt-ergo

[Julien Puydt]

Control: tag -1 pending

Hello,

Bug #1013362 in alt-ergo 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/ocaml-team/alt-ergo/-/commit/605e7a1e687fe1afa5a0e0b0b35ce8677f304062


Add conditional patch for non-native architectures (Closes: #1013362)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1013362

Processed: fixed 1014249 in 4.8.0-4, closing 1014249

[Debian Bug Tracking System]

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

> fixed 1014249 4.8.0-4
Bug #1014249 {Done: Jonas Smedegaard } [src:node-terser] 
node-terser: autopkgtest regression
Marked as fixed in versions node-terser/4.8.0-4.
> close 1014249
Bug #1014249 {Done: Jonas Smedegaard } [src:node-terser] 
node-terser: autopkgtest regression
Bug 1014249 is already marked as done; not doing anything.
> thanks
Stopping processing here.

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

Bug#1013715: marked as done (photutils: FTBFS: pytest7 regression, deprecated pytest feature: pytest.warnsNone)

[Debian Bug Tracking System]

Your message dated Mon, 04 Jul 2022 06:34:49 +
with message-id 
and subject line Bug#1013715: fixed in photutils 1.4.0-4
has caused the Debian Bug report #1013715,
regarding photutils: FTBFS: pytest7 regression, deprecated pytest feature: 
pytest.warnsNone
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.)


-- 
1013715: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013715
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: photutils
Version: 1.4.0-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-pyt...@lists.debian.org
Usertags: pytest7

Hi,

During a selected rebuild of python packages in sid, your package failed
to build with pytest version 7.1.2-1.

The full build log is available from:
http://qa-logs.debian.net/2022/06/09/pytest/photutils_1.4.0-3_unstable_pytest-exp.log

I had a closer look at the error log and identified the regression as:
'deprecated pytest feature: pytest.warnsNone'. Hopefully, that's helpful!

All bugs filed during this rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=pytest7;users=debian-pyt...@lists.debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=pytest7=debian-pyt...@lists.debian.org=1=1=1=1#results

If you reassign this bug to another package, please mark 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 the one provided so that we can identify if something relevant
changed in the meantime.

-- 
  ⢀⣴⠾⠻⢶⣦⠀
  ⣾⠁⢠⠒⠀⣿⡁  Louis-Philippe Véronneau
  ⢿⡄⠘⠷⠚⠋   po...@debian.org / veronneau.org
  ⠈⠳⣄


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: photutils
Source-Version: 1.4.0-4
Done: Ole Streicher 

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 04 Jul 2022 08:06:30 +0200
Source: photutils
Architecture: source
Version: 1.4.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Astronomy Team 

Changed-By: Ole Streicher 
Closes: 1013715
Changes:
 photutils (1.4.0-4) unstable; urgency=medium
 .
   * Update code to ignore emitted warnings (Closes: #1013715)
Checksums-Sha1:
 2815d58b1faea4ef7f1f9493069a3bdba34ea3c7 2239 photutils_1.4.0-4.dsc
 e419429e28da8356c3417caa196c0cf8228b954f 4876 photutils_1.4.0-4.debian.tar.xz
Checksums-Sha256:
 03c8e5a4dd8330a4851799fe5d30497434f756194345f141651fa8c53f0ddead 2239 
photutils_1.4.0-4.dsc
 abcc5f291d1b4ea7a44d62162e4c9541ac695b1fefadf7971d973461611ba583 4876 
photutils_1.4.0-4.debian.tar.xz
Files:
 308d1e4a82e2afc2d5297aef5ed82247 2239 python optional photutils_1.4.0-4.dsc
 016cd95e5eaa7c7a1bda1d52f8f5354c 4876 python optional 
photutils_1.4.0-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAmLChVoACgkQcRWv0HcQ
3PfVxBAAjM9fMrVgsEoGOl3+uoRtF+d2JDYBwZ4R8dKxmsyhZAghBUpLkaVTI/N+
4C3noKSUPMfuyDo5mvlltpxu5VfT/Hgow0uGDKvuvvbDReuaabmQoSUUzt2X/LQb
QGzXffXmXL8KuKWI4HNsc51wumrcdP5j9bdn+dkepz07Xk7WSYyTTpG7g1MSopCO
iYoJBJa9OTR/bnm7QisyBFNLDyA/Im+beF9oATDj+QsZ/3Q0+Mp/0wkeFojE/Noe
23o6HE66WsfE4zIY3eQlb1UQlQ98US44VwSTctplUd8DwVKT+rpfUOSobjv++sbj
vCPNfHYEE0VymSRpmBpfAIMGEMFxquK9tHQAUJx8Qh4SRuRCuPoKFHURtKgvMg7W
8/pZcbddV15ODWmOR3kNtaaNhZtkMz9WjaY168NSmwfD31V6o+haImE3nVZHy/ii
mzeNv8VmrtHvAJIAohGCqLYpPT5l8nRkGz2S3/cL6NAZiY+RcpNKvQLFgSWEbaLi
QZ2X7ipGvqfufNNY0Wns17Z5D3XT+nBiew1NQoTGQDlGZoTwJXpLK+0rxBGQ3YA3
zXsLd+W2cejkRt8gGLzB6XtlogfkjKrkXLfSF6PLm0RyNxUt42WCAD3Ttu+lNaPN
T1TJlhDiqs0mT2cBfc5A24BT7VkT1UM0qzh0okiYoxlMJi2O7v0=
=OTTK
-END PGP SIGNATURE End Message ---

Bug#1013665: marked as done (apertium-spa-arg: FTBFS: configure: error: Package requirements (apertium-lex-tools >= 0.2.7) were not met)

[Debian Bug Tracking System]

Your message dated Mon, 04 Jul 2022 06:34:08 +
with message-id 
and subject line Bug#1013665: fixed in apertium-spa-arg 0.5.0-2
has caused the Debian Bug report #1013665,
regarding apertium-spa-arg: FTBFS: configure: error: Package requirements 
(apertium-lex-tools >= 0.2.7) were not met
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.)


-- 
1013665: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013665
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: apertium-spa-arg
Version: 0.5.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220624 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> checking for gawk... (cached) gawk
> checking for pkg-config... /usr/bin/pkg-config
> checking pkg-config is at least version 0.9.0... yes
> checking for apertium >= 3.7.1... yes
> checking for apertium-lex-tools >= 0.2.7... no
> configure: error: Package requirements (apertium-lex-tools >= 0.2.7) were not 
> met
> 
> No package 'apertium-lex-tools' found
> 
> Consider adjusting the PKG_CONFIG_PATH environment variable if you
> installed software in a non-standard prefix.
> 
> Alternatively, you may set the environment variables APERTIUM_LEX_TOOLS_CFLAGS
> and APERTIUM_LEX_TOOLS_LIBS to avoid the need to call pkg-config.
> See the pkg-config man page for more details.
> make[1]: *** [debian/rules:20: override_dh_auto_configure] Error 1
> make[1]: Leaving directory '/<>'


The full build log is available from:
http://qa-logs.debian.net/2022/06/24/apertium-spa-arg_0.5.0-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220624;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220624=lu...@debian.org=1=1=1=1#results

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: apertium-spa-arg
Source-Version: 0.5.0-2
Done: Kartik Mistry 

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

Debian distribution maintenance software
pp.
Kartik Mistry  (supplier of updated apertium-spa-arg package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 04 Jul 2022 10:33:00 +0530
Source: apertium-spa-arg
Architecture: source
Version: 0.5.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Kartik Mistry 
Closes: 1013665
Changes:
 apertium-spa-arg (0.5.0-2) unstable; urgency=medium
 .
   * debian/control:
 + Fixed Build-Depends: apertium-lex-tools -> apertium-lex-tools-dev
   (Closes: #1013665)
 + Updated Standards-Version to 4.6.1
   * Updated debian/copyright.
   * Updated debian/watch.
Checksums-Sha1:
 22ef475d57e946727bf184211f1e20782e891aa5 2135 apertium-spa-arg_0.5.0-2.dsc
 b818d7f5247ebf3b88ff83b309b30f3368fcdc4d 2620 
apertium-spa-arg_0.5.0-2.debian.tar.xz
Checksums-Sha256:
 5461adc9a1b81a05bb9af352a216e7079e6abe77cce189a8a5ff3d03b2c9f602 2135 
apertium-spa-arg_0.5.0-2.dsc
 19ce50fa0fe01a24847ba2000b46c052292d6462dc0da6f08113099be4744174 2620 
apertium-spa-arg_0.5.0-2.debian.tar.xz
Files:
 b54383e74cfe91eeb20a418d07b19d2d 2135 science optional 
apertium-spa-arg_0.5.0-2.dsc
 822056c62bd99461fdb767eeba759ce5 2620 science optional 
apertium-spa-arg_0.5.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEa2MbXvVUr2sRlmKSAsHT8ng6pN4FAmLChdQACgkQAsHT8ng6
pN5HnBAAprNTyMx3QT1x4NwjUAbfBPqkJFcE3nxMgufycFv35xoxosCr5K9+HJMy

Bug#1013931: libtorrent-rasterbar2.0: Crash on exit

[Christian Marillat]

On 04 juil. 2022 08:22, Christian Marillat  wrote:

> On 27 juin 2022 18:47, Hilko Bengen  wrote:
>
>> (It might be a good idea to add a Built-Using line to debian/control.)
>
> Built-Using doesn't work with virtual package.

Well, virtual isn't the right word, but libboost-dev is an empty
package and dh_gencontrol return nothing. dh_gencontrol need to be
called with libboost1.74-dev completely unusable for the long term.

Christian

Bug#1013812: (no subject)

[Jean Baptiste Favre]

Control: fixed 1013812 9.1.2+ds-13


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1013931: libtorrent-rasterbar2.0: Crash on exit

[Christian Marillat]

On 27 juin 2022 18:47, Hilko Bengen  wrote:

> (It might be a good idea to add a Built-Using line to debian/control.)

Built-Using doesn't work with virtual package.

Christian