Bug#1022754: src:jenkins-debian-glue: fails to migrate to testing for too long: uploader built arch:all binaries

[Paul Gevers]

Source: jenkins-debian-glue
Version: 0.21.0
Severity: serious
Control: close -1 0.21.1
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:jenkins-debian-glue 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=jenkins-debian-glue



OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:jenkins-debian-glue: fails to migrate to testing for too long: uploader built arch:all binaries

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.21.1
Bug #1022754 [src:jenkins-debian-glue] src:jenkins-debian-glue: fails to 
migrate to testing for too long: uploader built arch:all binaries
Marked as fixed in versions jenkins-debian-glue/0.21.1.
Bug #1022754 [src:jenkins-debian-glue] src:jenkins-debian-glue: fails to 
migrate to testing for too long: uploader built arch:all binaries
Marked Bug as done

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

Bug#1019768: marked as done (grass: Please transition to wxwidgets3.2)

[Debian Bug Tracking System]

Your message dated Tue, 25 Oct 2022 05:19:43 +
with message-id 
and subject line Bug#1019768: fixed in grass 8.2.0-2
has caused the Debian Bug report #1019768,
regarding grass: Please transition to wxwidgets3.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.)


-- 
1019768: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019768
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: grass
Severity: normal
Control: block 1019416 by -1

Hi,

Please transition grass from wxwidgets3.0 to wxwidgets3.2.

wxWidgets 3.2 (a new API/ABI stable release) has been released a few
months ago and is now packaged in unstable as wxwidgets3.2. Upstream
has stopped supporting wxWidgets 3.0, so the Debian wx team would
like to migrate all wx package users to wxwidgets3.2 for bullseye,
with the plan to remove wxwidgets3.0 before release.

For most packages, the transition should be as simple as changing
Build-Depends from libwxgtk3.0-gtk3-dev to libwxgtk3.2-dev. Some
packages may require small patches; I'm happy to help with those (and
I have some already from working on this transition in Fedora
already).

Thanks, Scott 
--- End Message ---
--- Begin Message ---
Source: grass
Source-Version: 8.2.0-2
Done: Bas Couwenberg 

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

Debian distribution maintenance software
pp.
Bas Couwenberg  (supplier of updated grass package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 25 Oct 2022 06:14:18 +0200
Source: grass
Architecture: source
Version: 8.2.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GIS Project 
Changed-By: Bas Couwenberg 
Closes: 1019768
Changes:
 grass (8.2.0-2) unstable; urgency=medium
 .
   * Bump Standards-Version to 4.6.1, no changes.
   * Drop obsolete libwxgtk3.0-gtk3-dev build dependency.
 (closes: #1019768)
   * Update OpenGL build dependencies.
   * Update lintian overrides.
Checksums-Sha1:
 df839312cc868a16019a7685ae3e1d5db9ff115c 2798 grass_8.2.0-2.dsc
 f14aa8b9d71f42a1fd1608c94880e5610f92db31 33816 grass_8.2.0-2.debian.tar.xz
 6bcd1e11377a02498e1385d1be96c1e411169772 20537 grass_8.2.0-2_amd64.buildinfo
Checksums-Sha256:
 de985557c08f8d67ec651c1d121ef9b1270b63795eebdc2d54c6359c8ae497eb 2798 
grass_8.2.0-2.dsc
 a5346b767ccd4ade285f71af5bac6d5997be90cab04cf22f62c001f612190501 33816 
grass_8.2.0-2.debian.tar.xz
 90eb73b171be589d51c2280799f5e2c0cdf2c490c1ffc42942f76d4fc1f649e4 20537 
grass_8.2.0-2_amd64.buildinfo
Files:
 89330cde41bc98b16af83bbe50812edb 2798 science optional grass_8.2.0-2.dsc
 72fbfe48288ee82779946b51b08db3c8 33816 science optional 
grass_8.2.0-2.debian.tar.xz
 103e55365f0bb88be4b5e49d95f38763 20537 science optional 
grass_8.2.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEgYLeQXBWQI1hRlDRZ1DxCuiNSvEFAmNXbHAACgkQZ1DxCuiN
SvFY2RAAtjUR9rwXG5HPo6PvYzIGs7cS7vDni4RMpyS6gtiPaAjEGJM/ZaCrKJ5P
TE9obRIbpTxntmVIqB/wimx6uKYp2/lTpz1GQQnBOlp3UksXzvg1M/EGPQCVjqvv
Dt+Iv4hR6guLZJeyCfStxiIOMsY7N+7MizqZMMPT6mv2SfjS9OiTXDSl8CuMHqv9
RgTFxcl9BB1GhXzCd6RaxRcENRnybFKmxAVmU1PAvUhuqx/6/M59CtprMfDQmAhU
ayn7X8d/gNTSPbv+PHo7eJS4EO/2y7ph6Q5JuL40leOTriAzPVUxhCkOL67GHIv6
WFlNaLd5G1AzJ5hu1hKR3Y32/RZxh/pH7lNsIzPJ1PdVuqFV5A3Uiumg41ekOUmE
5JfuShVYLanq7RP7vmIh1gHNbNNNnnOMRX3s9yZqdfCMcuA/wphVP6NiAm5JuNfo
YHyowGsTVCck2v7MMJrsRxZYAPwt0n6VNPL51dCrpSSnXeB1Gc8yG3TuCUvGXm84
hUdMYlFeTeU8sWLkoipXpPJ2xLkOPAqc/5w7Aw3Wr8Qma9wis/fbJEXEhXi6GlaS
1WSungtglAOwNqu0QxoRammZweP9w2fFRpuJHk6KDo2q/xID3vgSPIO/r88wBQrn
VRGGATOSLLP/Xq8mchsPaudsgvJJmhHXmNSL7UNvKcDZbZEVfVQ=
=nCU/
-END PGP SIGNATURE End Message ---

Bug#1019814: marked as done (icinga2: Please transition to wxwidgets3.2)

[Debian Bug Tracking System]

Your message dated Tue, 25 Oct 2022 04:35:03 +
with message-id 
and subject line Bug#1019814: fixed in icinga2 2.13.5-2
has caused the Debian Bug report #1019814,
regarding icinga2: Please transition to wxwidgets3.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.)


-- 
1019814: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019814
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: icinga2
Severity: normal
Control: block 1019416 by -1

Hi,

Please transition icinga2 from wxwidgets3.0 to wxwidgets3.2.

wxWidgets 3.2 (a new API/ABI stable release) has been released a few
months ago and is now packaged in unstable as wxwidgets3.2. Upstream
has stopped supporting wxWidgets 3.0, so the Debian wx team would
like to migrate all wx package users to wxwidgets3.2 for bullseye,
with the plan to remove wxwidgets3.0 before release.

For most packages, the transition should be as simple as changing
Build-Depends from libwxgtk3.0-gtk3-dev to libwxgtk3.2-dev. Some
packages may require small patches; I'm happy to help with those (and
I have some already from working on this transition in Fedora
already).

Thanks, Scott 
--- End Message ---
--- Begin Message ---
Source: icinga2
Source-Version: 2.13.5-2
Done: Bas Couwenberg 

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

Debian distribution maintenance software
pp.
Bas Couwenberg  (supplier of updated icinga2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 25 Oct 2022 05:31:01 +0200
Source: icinga2
Architecture: source
Version: 2.13.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Nagios Maintainer Group 

Changed-By: Bas Couwenberg 
Closes: 1019814
Changes:
 icinga2 (2.13.5-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Bas Couwenberg ]
   * Drop obsolete libwxgtk3.0-gtk3-dev build dependency.
 (closes: #1019814)
   * Update lintian overrides.
 .
   [ Debian Janitor ]
   * Remove constraints unnecessary since buster (oldstable):
 + Build-Depends: Drop versioned constraint on cmake, g++ and make.
 + icinga2-bin: Drop versioned constraint on icinga2-common in Replaces.
 + icinga2-bin: Drop versioned constraint on icinga2-common in Breaks.
   * Apply multi-arch hints.
 + icinga2-doc: Add Multi-Arch: foreign.
Checksums-Sha1:
 057408878ee5d9a08fbad443364df549b0b04e10 2730 icinga2_2.13.5-2.dsc
 c52902bd395dad14a41dd90d293f2f737e609ae1 23668 icinga2_2.13.5-2.debian.tar.xz
 98856a0ade9c38d3e4a1a38c18f0d4c89976a177 12689 icinga2_2.13.5-2_amd64.buildinfo
Checksums-Sha256:
 71493919e361da74db7fce5b4167695f611fac6dad1a4983ac342fafd8a25b68 2730 
icinga2_2.13.5-2.dsc
 ec4f0b99f5860dbbdf4e9892bb02f7f8879518ffa0277476fa863eaa321cf31e 23668 
icinga2_2.13.5-2.debian.tar.xz
 efbba423f632d6ad65f0fe63275214509ca868ccbaaaf55848ba6524238ead4a 12689 
icinga2_2.13.5-2_amd64.buildinfo
Files:
 bb36f153f2c9469c4f97fc0fcd9d26e6 2730 admin optional icinga2_2.13.5-2.dsc
 87aa8a4dca6e6e6d4af5722ac7d85f88 23668 admin optional 
icinga2_2.13.5-2.debian.tar.xz
 45d687f15475afc8513e6da928cfae11 12689 admin optional 
icinga2_2.13.5-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEgYLeQXBWQI1hRlDRZ1DxCuiNSvEFAmNXYlsACgkQZ1DxCuiN
SvHj4g/9GOvhjL2zOQzvTV4hBjlqMjnIfjMoeBk9fi1ajj6wOb3d7kjyEoefx3it
ZNkBRg9UP+3rsJQAHo2S+XaGUURGerbJNJGMFMg4LceF/bjFQVRI7xlOFHwTrli/
uvGqoFgKxnoDrwkbpOfTPsYRJTMq4by0VKCTch0EHLdCRj+oTzSfhRzZXme4uKhh
YQjj1TUIsJ4YEnQDqgBfgP7sXKJEerBPDgem147zCEW88xv5Df6Aix+hMlwW63Ej
DW2eYMlOl3ms+kJUXJ62jUIXN2w65RQ5R0krxBR+gsIW7rEYmDp4M5DtU8dzFWjK
+CpE/NGgP6l6gNaofr7rmDlKp3IRMc9n8l0H0s+v5aNlE+bD2eHJSAogJJJ/G5hJ
VQ6ocZI/+uLkxqQJ89XWdTvooTvB/fZWs4JZdP90tpwA2jCG0dYwpTSK0Cjqiixj
JuA9Yb/Vo0Jh06K7hCoI70JoVOL4iBjqb7lib/aS6Zxvx9yevLJ4AjmfvRezqBBJ
2lnFCDe9irvXIIidrgsRWNV/kfHdS9BVspKbg7M+icHxNBh3vh5aq4/qkjLPquKe
hjuWe+hClbL5GLtLULY0xWJU+PXUZkJAt9IPT1ejWzm00rcHLq7xSdRRlGnA9rBV
cvki26Fiij5FVs5/mlc9z2DhzL4ajIJVQWBaCFcztrfiiuQa9ck=
=HDYU
-END PGP SIGNATURE End Message ---

Processed: owner 1022277

[Debian Bug Tracking System]

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

> owner 1022277 !
Bug #1022277 [src:libstringprep-java] libstringprep-java: FTBFS: [ERROR] Plugin 
org.codehaus.mojo:build-helper-maven-plugin:3.0.0 or one of its dependencies 
could not be resolved: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
org.codehaus.mojo:build-helper-maven-plugin:jar:3.0.0 has not been downloaded 
from it before. -> [Help 1]
Owner recorded as tony mancill .
> thanks
Stopping processing here.

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

Bug#1019775: marked as done (spatialite-gui: Please transition to wxwidgets3.2)

[Debian Bug Tracking System]

Your message dated Tue, 25 Oct 2022 03:50:09 +
with message-id 
and subject line Bug#1019775: fixed in spatialite-gui 2.1.0~beta1-2
has caused the Debian Bug report #1019775,
regarding spatialite-gui: Please transition to wxwidgets3.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.)


-- 
1019775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019775
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: spatialite-gui
Severity: normal
Control: block 1019416 by -1

Hi,

Please transition spatialite-gui from wxwidgets3.0 to wxwidgets3.2.

wxWidgets 3.2 (a new API/ABI stable release) has been released a few
months ago and is now packaged in unstable as wxwidgets3.2. Upstream
has stopped supporting wxWidgets 3.0, so the Debian wx team would
like to migrate all wx package users to wxwidgets3.2 for bullseye,
with the plan to remove wxwidgets3.0 before release.

For most packages, the transition should be as simple as changing
Build-Depends from libwxgtk3.0-gtk3-dev to libwxgtk3.2-dev. Some
packages may require small patches; I'm happy to help with those (and
I have some already from working on this transition in Fedora
already).

Thanks, Scott 
--- End Message ---
--- Begin Message ---
Source: spatialite-gui
Source-Version: 2.1.0~beta1-2
Done: Bas Couwenberg 

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

Debian distribution maintenance software
pp.
Bas Couwenberg  (supplier of updated spatialite-gui 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 25 Oct 2022 05:16:05 +0200
Source: spatialite-gui
Architecture: source
Version: 2.1.0~beta1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GIS Project 
Changed-By: Bas Couwenberg 
Closes: 1019775
Changes:
 spatialite-gui (2.1.0~beta1-2) unstable; urgency=medium
 .
   * Update lintian overrides.
   * Bump watch file version to 4.
   * Bump Standards-Version to 4.6.1, no changes.
   * Update upstream metadata.
   * Bump debhelper compat to 12, changes:
 - Drop --list-missing from dh_install
   * Drop obsolete dh_strip override, dbgsym migration complete.
   * Update build dependencies for wxwidgets3.2.
 (closes: #1019775)
Checksums-Sha1:
 4fedbb7400398b2f3df2dce3ae014fb3d4ec0493 2390 spatialite-gui_2.1.0~beta1-2.dsc
 2a65de0fded82bad3ad74a879a20f72bc6e7987f 14776 
spatialite-gui_2.1.0~beta1-2.debian.tar.xz
 db438377ac84f1d6ddae4d66ae15d88d7866 13237 
spatialite-gui_2.1.0~beta1-2_amd64.buildinfo
Checksums-Sha256:
 c74653b3cac3e3968c2efb190a0a0ada9fb46217fd971e5eb367dbb219e98f09 2390 
spatialite-gui_2.1.0~beta1-2.dsc
 14be8e0c263c473d2321f8a03e7132016840ef6c6a9cfd5d939ee87c63c328a8 14776 
spatialite-gui_2.1.0~beta1-2.debian.tar.xz
 a2d8da5c474daa7ad084fe7830e3d30d4a1c8d938016eb53f4d512e234a8e41c 13237 
spatialite-gui_2.1.0~beta1-2_amd64.buildinfo
Files:
 0d293bf765728dab0197b947419e2e79 2390 utils optional 
spatialite-gui_2.1.0~beta1-2.dsc
 553068e49a343f860de41685b11cdf9c 14776 utils optional 
spatialite-gui_2.1.0~beta1-2.debian.tar.xz
 c025ba37d7874580049f66c36930b05a 13237 utils optional 
spatialite-gui_2.1.0~beta1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEgYLeQXBWQI1hRlDRZ1DxCuiNSvEFAmNXWFQACgkQZ1DxCuiN
SvGkIxAAuG98YXlCndb/QqDujhRSII00I0qfvkq6FJylid3Bauy9fgMT/lSfurYd
gaF8gUsGMT+C8Z9yk3ZapagRhd/oLB8LOFwxKZMMdHHn/lwB11v19X310yleXEx8
IlrBh9Ti1ijz+shelgtC6UE6XkcvjYGTmrm4OCyHIbzk6NIDs1tHzAROlVGIZu9J
524az+qWUlJJTes0bw4gLGg3TwR0+FzrRfoC6pjXEn85VD6ge0hH1milH0UEpTea
+m1geRVZup83zIRpK9aIWKqV/XqjVgOy6sRePOsBqnS8SJku5rTY3Zy/TCcqL4+q
5ilQxmihNCWcnJvJoaNMRjShuU3V7HrZoaL8wnDIob7kU4MI/0EKU6n/x60EhFIj
pQP4r/ikr0B7l/6JWu2tNDh1+do629cI/2SngyNl+O2sYCOvx2Yw+jmF5eNXTS45
D0w0dpDNsuJqEDotmzzqSMkkFlZdRGJ948s6L0nOozTTsXZWRhR9AbfuyeVibaLK
nWf8JEgYGsdAyEr4Bi0989S5bTlRiTLnsViKzNK/G9c5XL0SIeTMwCyGBShHo2rI
eoNUB/IbyCEHj7CZniqYcrW1MQN54oGVkgPz74gh9Val3HGBj0Z77ue/9uXVNuC2
OcRKhqSn+lEsivkVdKMEQIyRNZ4xdu/eEV61+1cEZRZCw36OZ2s=
=nYbu
-END PGP SIGNATURE End Message ---

Bug#1019819: qutemol: Please transition to wxwidgets3.2

[Scott Talbert]

On Sun, 23 Oct 2022, Graham Inggs wrote:


Control: tags -1 + help

Hi Scott

Thanks for driving the transition to wxwidgets3.2.

I've tried switching the Build-Depends from libwxgtk3.0-gtk3-dev to
libwxgtk3.2-dev in qutemol, but the build fails with the output below.

Any hints would be appreciated.


Hi Graham,

I sent a pull request[1] to fix the compile issue (basically, qutemol was 
using a long-deprecated API for wxGLCanvas that was finally removed in wx 
3.2).


However, after fixing that, qutemol runs into another problem, which is 
basically that wxWidgets 3.2, which is compiled to use OpenGL EGL, is 
incompatible with glew, which is compiled to use OpenGL GLX.  This is 
documented in this bug[2] and still needs to be sorted out.


Regards,
Scott

[1] https://salsa.debian.org/debichem-team/qutemol/-/merge_requests/2
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020640

Processed (with 3 errors): reasign and merge

[Debian Bug Tracking System]

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

> reasign 1022366 llvm-14-dev
Unknown command or malformed arguments to command.
> forcemerge 1021857 1022366
Bug #1021857 [llvm-14-dev] llvm-14-dev: CMake Error in LLVMExports.cmake: The 
imported target "sancov" references the file "/usr/lib/llvm-14/bin/sancov" but 
this file does not exist.
Bug #1022334 [llvm-14-dev] qtcreator: FTBFS: make[1]: *** [debian/rules:26: 
override_dh_auto_configure] Error 2
Bug #1022337 [llvm-14-dev] qt6-tools: FTBFS: The imported target "sancov" 
references the file "/usr/lib/llvm-14/bin/sancov" but this file does not exist.
Bug #1022409 [llvm-14-dev] ccls: FTBFS: make[1]: *** [debian/rules:18: 
override_dh_auto_configure] Error 2
Bug #1022414 [llvm-14-dev] bpftrace: FTBFS: make[1]: *** [debian/rules:7: 
override_dh_auto_configure] Error 2
Unable to merge bugs because:
package of #1022366 is 'src:irony-mode' not 'llvm-14-dev'
Failed to forcibly merge 1021857: Did not alter merged bugs.

> affects 1021857 irony-mode
Failed to mark 1021857 as affecting package(s): failed to get lock on 
/srv/bugs.debian.org/spool/lock/merge -- Unable to lock 
/srv/bugs.debian.org/spool/lock/merge Resource temporarily unavailable.
Unable to lock /srv/bugs.debian.org/spool/lock/merge Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/merge Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/merge Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/merge Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/merge Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/merge Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/merge Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/merge Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
Unable to lock /srv/bugs.debian.org/spool/lock/merge Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 692.
 at /usr/local/lib/site_perl/Debbugs/Common.pm line 650.

> thanks
Stopping processing here.

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

Bug#1022719: marked as done (fonts-texgyre-math: missing Breaks: fonts-texgyre (<< 20180621-4))

[Debian Bug Tracking System]

Your message dated Mon, 24 Oct 2022 22:28:29 +
with message-id 
and subject line Bug#1022719: fixed in tex-gyre 20180621-6
has caused the Debian Bug report #1022719,
regarding fonts-texgyre-math: missing Breaks: fonts-texgyre (<< 20180621-4)
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.)


-- 
1022719: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022719
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fonts-texgyre-math
Version: 20180621-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts replaces-without-breaks

Hi,

during a test with piuparts and DOSE tools I noticed your package causes
removal of files that also belong to another package.
This is caused by using Replaces without corresponding Breaks.

There is a Breaks: tex-gyre (<< 20180621-4) that should probably have
targeted fonts-texgyre instead.


Andreas
--- End Message ---
--- Begin Message ---
Source: tex-gyre
Source-Version: 20180621-6
Done: Hilmar Preusse 

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

Debian distribution maintenance software
pp.
Hilmar Preusse  (supplier of updated tex-gyre 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, 24 Oct 2022 23:34:23 +0200
Source: tex-gyre
Architecture: source
Version: 20180621-6
Distribution: unstable
Urgency: medium
Maintainer: Debian TeX Task Force 
Changed-By: Hilmar Preusse 
Closes: 1022719
Changes:
 tex-gyre (20180621-6) unstable; urgency=medium
 .
   * Fix "Breaks" statement of fonts-texgyre-math (Closes: #1022719).
Checksums-Sha1:
 b34e31568749677571cae8093b562a2b251f8cc8 2241 tex-gyre_20180621-6.dsc
 a029595c56fac6d1d0d19b338cf4d8473182f280 11632 
tex-gyre_20180621-6.debian.tar.xz
 c9354359506fa45609b58b67dd9ba652f3d84ac6 5744 
tex-gyre_20180621-6_source.buildinfo
Checksums-Sha256:
 83a26e65fee0ac79f31a44e083e03da2fef7b031c70d0f336796782cc0fed099 2241 
tex-gyre_20180621-6.dsc
 731e04abb52038a7de626e4679d6b823b2d692be029bb88399951fb69b286f67 11632 
tex-gyre_20180621-6.debian.tar.xz
 9dccbd85e707ae9695235412cb37af6560e05a1dc839af617f163cca360bd588 5744 
tex-gyre_20180621-6_source.buildinfo
Files:
 ff112a4fcc363a2e1bcfe5f4cff58cad 2241 tex optional tex-gyre_20180621-6.dsc
 ed0b296c73ee5023b6f454313b1a81eb 11632 tex optional 
tex-gyre_20180621-6.debian.tar.xz
 d81b979989e7250a3781439c8cfd4d1a 5744 tex optional 
tex-gyre_20180621-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEEaXGmC/nkbIhxf16kxiZYRqvgLIsFAmNXBTdfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDY5
NzFBNjBCRjlFNDZDODg3MTdGNUVBNEM2MjY1ODQ2QUJFMDJDOEIACgkQxiZYRqvg
LIvUDQ//ZaFeY3vFqB8gbk2/Av0s1hL9WKZTQ7FTrYXNosxW8+2tUDtUVD8jyBe7
a1fC/Fb3pkNq/jWHrCkNWiH5HftujtocvJPVHSik62sb3Kl+IJZswgc1iiVzu0Jj
S4gFf6SSkX32UMl2z5jtU2kSrtePYI8VKJhO/IjhhM7hWIXTopMQCEQ/Dagyilnh
g8WGQGqxi4BglnacZx3jz3YMWb1ZQ5Ogzj6u+bQhXXbhZ+LRA6f6RIrC8hQxQ0fS
dbR3g3S66FtG0S34GrA8JEgfy6IkTkXc7U70g8ECPu7U9TKk2syPNTg6QmGX1WPi
DNiSZi5u07mmDOVdJUWKfqnYsvG3k+x+QEJqnITjs++fqOhClPFAVCBwC+p3p81T
uHmzh+AuhySQW5+t+NGB/4KCdK1djfFTC1SxGL0F8gDAIqoumImt+q4JbbW2n1sM
2bq87PvwpcWmJiv22t5Y7Rd2LKi1lSBclh+xaAIs/ArEY0qdjYaExKdcpaDGc3qW
l7Vif7Bm8fDcFBsAIsfSbGnjwnzInrZqjzXn73f+hH5RCYwINSF4+mB1goFYWJ8R
EXZmXXw5s+WQah8lgwVM1a2Sb5iUOO0tE8vC6Qy9xTIZ4mxC4AaTNCs7dEql1bup
okYC8b/DZ7o2/ev1Dr6O0dS8bL0vmka1fElo7uKkn7WT/y9Cv9M=
=tL9s
-END PGP SIGNATURE End Message ---

Bug#1022335: marked as done (onednn: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 ninja test returned exit code 1)

[Debian Bug Tracking System]

Your message dated Mon, 24 Oct 2022 22:25:23 +
with message-id 
and subject line Bug#1022335: fixed in onednn 2.6.2-2
has caused the Debian Bug report #1022335,
regarding onednn: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && 
LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 ninja test returned exit code 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.)


-- 
1022335: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022335
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: onednn
Version: 2.6.2-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 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 '/<>'
> dh_auto_test || true
>   cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 ninja test
> [0/1] Running tests...
> Test project /<>/obj-x86_64-linux-gnu
> Start   1: cpu-bnorm-u8-via-binary-postops-cpp
>   1/249 Test   #1: cpu-bnorm-u8-via-binary-postops-cpp .. 
>   Passed0.01 sec
> Start   2: gpu-bnorm-u8-via-binary-postops-cpp
>   2/249 Test   #2: gpu-bnorm-u8-via-binary-postops-cpp .. 
>   Passed0.00 sec
> Start   3: cpu-cnn-inference-f32-c
>   3/249 Test   #3: cpu-cnn-inference-f32-c .. 
>   Passed0.05 sec
> Start   4: gpu-cnn-inference-f32-c
>   4/249 Test   #4: gpu-cnn-inference-f32-c .. 
>   Passed0.00 sec
> Start   5: cpu-cnn-inference-f32-cpp
>   5/249 Test   #5: cpu-cnn-inference-f32-cpp  
>   Passed1.36 sec
> Start   6: gpu-cnn-inference-f32-cpp
>   6/249 Test   #6: gpu-cnn-inference-f32-cpp  
>   Passed0.00 sec
> Start   7: cpu-cnn-inference-int8-cpp
>   7/249 Test   #7: cpu-cnn-inference-int8-cpp ... 
>   Passed0.02 sec
> Start   8: gpu-cnn-inference-int8-cpp
>   8/249 Test   #8: gpu-cnn-inference-int8-cpp ... 
>   Passed0.00 sec
> Start   9: cpu-cnn-training-bf16-cpp
>   9/249 Test   #9: cpu-cnn-training-bf16-cpp  
>   Passed0.33 sec
> Start  10: gpu-cnn-training-bf16-cpp
>  10/249 Test  #10: gpu-cnn-training-bf16-cpp  
>   Passed0.00 sec
> Start  11: cpu-cnn-training-f32-cpp
>  11/249 Test  #11: cpu-cnn-training-f32-cpp . 
>   Passed0.25 sec
> Start  12: gpu-cnn-training-f32-cpp
>  12/249 Test  #12: gpu-cnn-training-f32-cpp . 
>   Passed0.00 sec
> Start  13: cpu-cnn-training-f32-c
>  13/249 Test  #13: cpu-cnn-training-f32-c ... 
>   Passed0.15 sec
> Start  14: cpu-rnn-inference-f32-cpp
>  14/249 Test  #14: cpu-rnn-inference-f32-cpp  
>   Passed0.10 sec
> Start  15: cpu-rnn-inference-int8-cpp
>  15/249 Test  #15: cpu-rnn-inference-int8-cpp ... 
>   Passed0.13 sec
> Start  16: cross-engine-reorder-c
>  16/249 Test  #16: cross-engine-reorder-c ... 
>   Passed0.00 sec
> Start  17: cross-engine-reorder-cpp
>  17/249 Test  #17: cross-engine-reorder-cpp . 
>   Passed0.00 sec
> Start  18: cpu-getting-started-cpp
>  18/249 Test  #18: cpu-getting-started-cpp .. 
>   Passed0.01 sec
> Start  19: gpu-getting-started-cpp
>  19/249 Test  #19: gpu-getting-started-cpp .. 
>   Passed0.00 sec
> Start  20: gpu-opencl-interop-cpp
>  20/249 Test  #20: gpu-opencl-interop-cpp 
> ...***Failed0.00 sec
> oneDNN error caught: 
>   Status: invalid_arguments
>   Message: could not create an engine
> Example failed on GPU.
> 
> Start  21: cpu-memory-format-propagation-cpp
>  21/249 Test  #21: cpu-memory-format-propagation-cpp  
>   Passed0.01 sec
> Start  22: gpu-memory-format-propagation-cpp
>  22/249 Test  #22: gpu-memory-format-propagation-cpp  
>   Passed0.00 sec
> Start  23: cpu-performance-profiling-cpp
>  23/249 Test  #23: cpu-performance-profiling-cpp  
>   Passed0.80 

Bug#1022070: 5.10.0-19-amd64 works now on Tuxedo Aura 15 Gen1

[Jan Wedekind]

Thanks for fixing the issue!

Kind regards
Jan

Bug#1020928: marked as done (pam-python: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Mon, 24 Oct 2022 21:34:34 +
with message-id 
and subject line Bug#1020928: fixed in debian-edu-config 2.12.24
has caused the Debian Bug report #1020928,
regarding pam-python: Python2 removal in sid/bullseye
to be marked as done.

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

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


-- 
1020928: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020928
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pam-python
Version: 1.0.6-1.1
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
https://lists.debian.org/debian-python/2019/07/msg00080.html

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  Please stop using Python2, and fix this issue
by one of the following actions.

- Convert your Package to Python3. This is the preferred option.  In
  case you are providing a Python module foo, please consider dropping
  the python-foo package, and only build a python3-foo package.  Please
  don't drop Python2 modules, which still have reverse dependencies,
  just document them.
  
  This is the preferred option.

- If the package is dead upstream, cannot be converted or maintained
  in Debian, it should be removed from the distribution.  If the
  package still has reverse dependencies, raise the severity to
  "serious" and document the reverse dependencies with the BTS affects
  command.  If the package has no reverse dependencies, confirm that
  the package can be removed, reassign this issue to ftp.debian.org,
  make sure that the bug priority is set to normal and retitle the
  issue to "RM: PKG -- removal triggered by the Python2 removal".

- If the package has still many users (popcon >= 300), or is needed to
  build another package which cannot be removed, document that by
  adding the "py2keep" user tag (not replacing the py2remove tag),
  using the debian-pyt...@lists.debian.org user.  Also any
  dependencies on an unversioned python package (python, python-dev)
  must not be used, same with the python shebang.  These have to be
  replaced by python2/python2.7 dependencies and shebang.

  This is the least preferred option.

If the conversion or removal needs action on another package first,
please document the blocking by using the BTS affects command, like

  affects  + src:pam-python

If there is no py2removal bug for that reverse-dependency, please file
a bug on this package (similar to this bug report).

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
Source: debian-edu-config
Source-Version: 2.12.24
Done: Holger Levsen 

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

Debian distribution maintenance software
pp.
Holger Levsen  (supplier of updated debian-edu-config 
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, 24 Oct 2022 23:28:55 +0200
Source: debian-edu-config
Architecture: source
Version: 2.12.24
Distribution: unstable
Urgency: medium
Maintainer: Debian Edu Developers 
Changed-By: Holger Levsen 
Closes: 1020928
Changes:
 debian-edu-config (2.12.24) unstable; urgency=medium
 .
   [ Mike Gabriel ]
   * debian/control:
 + Change D (d-e-c) on libpam-python to a versioned dependency
   (>= 1.1.0~git20220701.1d4e111-0.3~). Starting with this version,
   libpam-python has fully been ported to Python3. (Closes: #1020928).
Checksums-Sha1:
 7f2305c72e97d5f7dfa7448db826d15f838f879d 2026 debian-edu-config_2.12.24.dsc
 8b63be54399dee7feb7e587a56c9d5e564f222b9 352480 
debian-edu-config_2.12.24.tar.xz
 b6e11d50387f9797bccd513f208ca16b66088ffe 5911 
debian-edu-config_2.12.24_source.buildinfo
Checksums-Sha256:
 fdc64d098c67828c3ac5e1bb5e496a8cbf85b028f616f084a1e3a3c1c007a139 2026 

Bug#1019233: marked as done (conserver FTBFS on IPV6-only buildds)

[Debian Bug Tracking System]

Your message dated Mon, 24 Oct 2022 21:34:26 +
with message-id 
and subject line Bug#1019233: fixed in conserver 8.2.7-2
has caused the Debian Bug report #1019233,
regarding conserver FTBFS on IPV6-only buildds
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.)


-- 
1019233: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019233
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: conserver
Version: 8.2.4-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=conserver=amd64

...
   dh_auto_test -a
make -j4 test VERBOSE=1
make[1]: Entering directory '/<>'
( cd test && ./dotest ) || exit 1
starting conserver...pid 16243
executing test #1...failed (diffs in test1.diff)
executing test #2...failed (diffs in test2.diff)
executing test #3...failed (diffs in test3.diff)
executing test #4...failed (diffs in test4.diff)
executing test #5...failed (diffs in test5.diff)
moving in second config file
executing test #6...failed (diffs in test6.diff)
executing test #7...failed (diffs in test7.diff)
executing test #8...failed (diffs in test8.diff)
executing test #9...failed (diffs in test9.diff)
executing test #10...failed (diffs in test10.diff)
executing test #11...failed (diffs in test11.diff)
executing test #12...failed (diffs in test12.diff)
executing test #13...failed (diffs in test13.diff)
executing test #14...failed (diffs in test14.diff)
executing test #15...failed (diffs in test15.diff)
make[1]: *** [Makefile:36: test] Error 1
--- End Message ---
--- Begin Message ---
Source: conserver
Source-Version: 8.2.7-2
Done: Bernhard Schmidt 

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

Debian distribution maintenance software
pp.
Bernhard Schmidt  (supplier of updated conserver 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, 24 Oct 2022 23:10:07 +0200
Source: conserver
Architecture: source
Version: 8.2.7-2
Distribution: unstable
Urgency: medium
Maintainer: Conserver Maintainers 
Changed-By: Bernhard Schmidt 
Closes: 1019233
Changes:
 conserver (8.2.7-2) unstable; urgency=medium
 .
   * Make testsuite non-fatal, it does not work on IPv6-only buildds
 (Closes: #1019233)
Checksums-Sha1:
 962c396160b38b5a3836e086178ddb075aceaa65 2094 conserver_8.2.7-2.dsc
 fabcae665b3ad9f4b90e04a3550ae62275548d5e 28200 conserver_8.2.7-2.debian.tar.xz
 cc9a3d8258af95bdff08a174796eb160c537f6d2 7397 conserver_8.2.7-2_amd64.buildinfo
Checksums-Sha256:
 b02a59d8101320fdd9f62629ddf542f56e4fcd1651c0fd80be6f76e8febba569 2094 
conserver_8.2.7-2.dsc
 c59754ee29624432346320cffa5b182ae2a2a5a5d60e7704d2748d02233cfb42 28200 
conserver_8.2.7-2.debian.tar.xz
 0ae57d2dcb6e251352b35335ec12b6fd48ddb95255707b0a7f9e52eb5bf88d78 7397 
conserver_8.2.7-2_amd64.buildinfo
Files:
 0c28f9055a54a214fc1d4d567d908039 2094 comm optional conserver_8.2.7-2.dsc
 604150eb3ae79014618e95010f5bd9f0 28200 comm optional 
conserver_8.2.7-2.debian.tar.xz
 6d954a9f1e69875f302423424e4bb55f 7397 comm optional 
conserver_8.2.7-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE1uAexRal3873GVbTd1B55bhQvJMFAmNXAD8RHGJlcm5pQGRl
Ymlhbi5vcmcACgkQd1B55bhQvJNgjA/8CI4pgaJDNdefniYzkEPt3xDtg7bYjtfA
IlydWh3DKbr2tITVKM+aWvYXz3AJkplaBF5Sq8ZK0MCT8fWVEi51XcxH2QcDpi9t
wlCr8Ye+nLLZOtDrLLd/WQImqmRNd0idc8rrcuJujJ9QZJ5ESbJhSh2SevOLIRHj
DIELDMuGVf8LY2oaz1A/t8KLl80yohMkpDyCHaN91nj4AhTpoOacAUxEUoSLWMWY
fqp0vRExvuRmU9X1jonvQn7fZRkAEqRjPcju0L5DMCbT3Yv5W6moY/Sk/CCeHn5G
tbeb/ksYXdYZ8O9kIARYfvU/NCd+6UHJaWfUoyC89EOL83/7vd5kHUKVb1WUWjWO
UCGzK50ecjXeQyBbmDlN2DZJ8BxCrdN6CkoK0yAibK8xR1NM5zZyCGGvtokJD2rC
4bjRf6m9qGKt7pPFxM+XqLxErAgIKJiAGeuZHd8l/Gf/K0E6tCEiOIY7PriPfcE+
BRwEo64oXiRr3J0C2O8F1gxZEksFrG6MhUG28mTpzWHSGSKlrkprZppk6U94wbfo
KjxoSjqZqHqHljxRp9Ln1+Gp2SWYMZnlX968kOiFOKaHAAJBbYvypLxQhbJxjlt2
3VxGEndukpBeG5hah0n/Ti4KIASIluKglvRZQk7p3XIngZIlju8dkY6gjSSE97Dk
JTuVMScmFpo=
=6PwH
-END PGP SIGNATURE End Message ---

Bug#1019233: conserver FTBFS on IPV6-only buildds

[Bernhard Schmidt]

After some thoughts on it I've decided to make the test-suite non-fatal
in the pending 8.2.7-2 upload. 

The root cause of the test-suite error appears to be that conserver is
using AI_ADDRCONFIG, and fails to resolve localhost to 127.0.0.1 on
machines that do not have non-local IPv4 connectivity.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952740
https://lists.debian.org/debian-devel/2022/02/msg00070.html

I have briefly tried to make the test-suite cope with both situations,
but was not successful. I don't want to make any code changes breaking
some real-world application while beating the testsuite into submission,
so for now I'll ignore the failure.

Bug#1020168: ecb: FTBFS: make[2]: *** [Makefile:86: ecb] Error 255

[Bálint Réczey]

Control: tags -1 confirmed help

Lucas Nussbaum  ezt írta (időpont: 2022. szept. 18., V, 9:00):
>
> Source: ecb
> Version: 2.50+git20170628-1
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20220917 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 '/<>'
> > Makefile:44: Makefile.conf not found. Using defaults for Linux!
> > Makefile:45: Create Makefile.conf from Makefile.conf.template to override 
> > the defaults.
> > Byte-compiling ECB with LOADPATH= ...
> > emacs -batch -no-site-file -l ecb-compile-script --eval '(ecb-byte-compile 
> > t)'
> > Package cl is deprecated
> > ecb-util.el: Warning: ‘typecase’ is an obsolete alias (as of 27.1); use 
> > ‘cl-typecase’ instead.
> > Compiler-macro error for cl-typep: (error "Unknown type 
> > button-release-event")
> > Compiler-macro error for cl-typep: (error "Unknown type button-press-event")
...
> > ecb-compilation.el: Warning: ‘return’ is an obsolete alias (as of 27.1); 
> > use ‘cl-return’ instead.
> > Debugger entered--Lisp error: (error "Cannot find suitable directory for 
> > output in ‘nati...")
> >   error("Cannot find suitable directory for output in `nati...")

I think this is an result of native compilation behaviour change in
emacs 28 as discussed in this thread for example:
https://lists.gnu.org/archive/html/bug-gnu-emacs/2021-01/msg00838.html

There are other similar FTBFS bugs and emacs-buttercup has been fixed
for example:
https://salsa.debian.org/emacsen-team/emacs-buttercup/-/commit/a42603de8c739681d9ae2e660af637ffb583a67d

I think the best course of action would be switching ecb to use
dh_elpa, but I don't know when I can work on that, thus help is
appreciated.

Thanks,
Balint

Processed: Re: Bug#1020168: ecb: FTBFS: make[2]: *** [Makefile:86: ecb] Error 255

[Debian Bug Tracking System]

Processing control commands:

> tags -1 confirmed help
Bug #1020168 [src:ecb] ecb: FTBFS: make[2]: *** [Makefile:86: ecb] Error 255
Added tag(s) help and confirmed.

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

Processed: severity of 1016291 is important

[Debian Bug Tracking System]

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

> severity 1016291 important
Bug #1016291 [src:python-inotify] python-inotify: FTBFS: dh_auto_test: error: 
pybuild --test --test-pytest -i python{version} -p 3.10 returned exit code 13
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#1022579: marked as done (firebird3.0: FTBFS for binary-independent build)

[Debian Bug Tracking System]

Your message dated Mon, 24 Oct 2022 20:37:32 +
with message-id 
and subject line Bug#1022579: fixed in firebird3.0 3.0.11.33637.ds4-2
has caused the Debian Bug report #1022579,
regarding firebird3.0: FTBFS for binary-independent build
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.)


-- 
1022579: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022579
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: firebird3.0
Version: 3.0.11.33637.ds4-1
Severity: serious
Tags: ftbfs
Justification: FTBFS

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear Maintainer,

https://buildd.debian.org/status/fetch.php?pkg=firebird3.0=all=3.0.11.33637.ds4-1=1666553566=0

Building the arch indep packages failed with:

make[1]: Entering directory '/<>'
dh_lintian
sed -i -e "s/TRIPLET/x86_64-linux-gnu/g" \
debian/libib-util/usr/share/lintian/overrides/libib-util
sed: can't read debian/libib-util/usr/share/lintian/overrides/libib-util: No 
such file or directory
make[1]: *** [debian/rules:177: override_dh_lintian] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:7: binary-indep] Error 2
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit 
status 2

I guess you want to fix this ASAP as it's currently blocking all rdeps on 
firebird-dev
(why does firebird-dev depend on the documentation anyway?)

Ondrej

- -- System Information:
Debian Release: 11.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'stable-debug'), (500, 'proposed-updates'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-18-amd64 (SMP w/24 CPU threads)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_IE:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEEw2Gx4wKVQ+vGJel9g3Kkd++uWcIFAmNWZ5xfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEMz
NjFCMUUzMDI5NTQzRUJDNjI1RTk3RDgzNzJBNDc3RUZBRTU5QzIACgkQg3Kkd++u
WcLWchAAmHx17RF3AzYqUlr66CVLBYOpRfgeZ0DlmPsYVDj9gwgwDPMQXbmOrzr7
fbXe02PiaW+QKGUwCd3b3fRHlFe0oENLU9mpc7fIY4Dg6nC/mJ6yzp34KZ5bUYi0
KV6yNaVSgq6QF7Zi8bOgjQ/t8yhKHCE2p7UQwk+EAUHHxlcCMMWEfn1VJlJ8HwxQ
57W9Fyigx+0/b1OnQI8gYRyCcY6blnc/r6lEJcW5N06VjYEOhOQNLbMDa1D9vvR1
7KAzu/+BkTBUUGJmTUMne2t4ZEzgC+B9XQzW7wAO916hNhrAmCtzYOlKAiy5+P+f
N2MHLjH6vGBEwDvagnYEno8/szb08aMCmX8B5JiNZzckpspTEi78q4qwKnWU06Ud
AoWBvqbDIqR3yIaPl4GNLHjnit8zW/KRCgdMmFzboKhmeE4sGW/hOxDunLri5Vw1
QvvV29CFpKqvycg8Gqp84Jx09j/3x2vgsV/B2EJfebr8ThD48ynnpw7WPIW5QBUu
C5xe+lQ+o8/+BHuhYKZASlap0YGQDQN/xv3KHM3ScRMVYdMOGMbidH+IiXaTJhFZ
2E+Mkg1eVkKYxziWgkDNabU+0j2F1ojOr19dJYli0DyiVVYB948+rF6LL3buiu0r
XzQbkFMqsRqUz1tJvwf4tGlLZdVPGmAH7209sAFhDxUaLgZlWtM=
=HkBV
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: firebird3.0
Source-Version: 3.0.11.33637.ds4-2
Done: Damyan Ivanov 

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

Debian distribution maintenance software
pp.
Damyan Ivanov  (supplier of updated firebird3.0 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, 24 Oct 2022 19:36:38 +
Source: firebird3.0
Architecture: source
Version: 3.0.11.33637.ds4-2
Distribution: unstable
Urgency: medium
Maintainer: Damyan Ivanov 
Changed-By: Damyan Ivanov 
Closes: 1022579
Changes:
 firebird3.0 (3.0.11.33637.ds4-2) unstable; urgency=medium
 .
   * fix arch-all-only build by overriding only dh_lintian-arch for libib-util
 override mangling.
 Thanks to Ondřej Surý (Closes: #1022579)
Checksums-Sha1: 
 dcf4406e44c80a1023c0d1179fc80168c7be019c 2761 
firebird3.0_3.0.11.33637.ds4-2.dsc
 107b6ae53f94d2426d8ac1c207499af2cf74 101652 
firebird3.0_3.0.11.33637.ds4-2.debian.tar.xz
Checksums-Sha256: 
 f2a64e5123bc8a90327e60ecc8a2b3ddd9d767a62d2a97e44908995314d18e55 2761 
firebird3.0_3.0.11.33637.ds4-2.dsc
 9b7e08cdb4906cc6785c9095549b8e2fd7b0d44272a17364a9a48abacbd274f5 101652 

Processed: severity of 1016291 is serious, severity of 1019626 is serious, severity of 1019627 is serious ...

[Debian Bug Tracking System]

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

> severity 1016291 serious
Bug #1016291 [src:python-inotify] python-inotify: FTBFS: dh_auto_test: error: 
pybuild --test --test-pytest -i python{version} -p 3.10 returned exit code 13
Severity set to 'serious' from 'important'
> severity 1019626 serious
Bug #1019626 [src:ruby-grape-entity] ruby-grape-entity: FTBFS with ruby3.1: 
ERROR: Test "ruby3.1" failed: RuntimeError:
Severity set to 'serious' from 'important'
> severity 1019627 serious
Bug #1019627 [src:ruby-graphviz] ruby-graphviz: FTBFS with ruby3.1: ERROR: Test 
"ruby3.1" failed.
Severity set to 'serious' from 'important'
> severity 1019628 serious
Bug #1019628 [src:ruby-hashie] ruby-hashie: FTBFS with ruby3.1: ERROR: Test 
"ruby3.1" failed:expected NoMethodError with "The property 
'middle_name' is not defined for DashTest.", got # severity 1019629 serious
Bug #1019629 [src:ruby-heapy] ruby-heapy: FTBFS with ruby3.1: ERROR: Test 
"ruby3.1" failed:  RuntimeError:
Severity set to 'serious' from 'important'
> severity 1019630 serious
Bug #1019630 [src:ruby-hoe] ruby-hoe: FTBFS with ruby3.1: ERROR: Test "ruby3.1" 
failed.
Severity set to 'serious' from 'important'
> severity 1019631 serious
Bug #1019631 [src:ruby-httparty] ruby-httparty: FTBFS with ruby3.1: ERROR: Test 
"ruby3.1" failed: RuntimeError:
Severity set to 'serious' from 'important'
> severity 1019632 serious
Bug #1019632 [src:ruby-ice-cube] ruby-ice-cube: FTBFS with ruby3.1: ERROR: Test 
"ruby3.1" failed:   Failure/Error: expect(YAML.load(symbol_yaml)).to 
eq(YAML.load(string_yaml))
Severity set to 'serious' from 'important'
> severity 1019633 serious
Bug #1019633 [src:ruby-invisible-captcha] ruby-invisible-captcha: FTBFS with 
ruby3.1: ERROR: Test "ruby3.1" failed: cannot load such file -- net/smtp
Severity set to 'serious' from 'important'
> severity 1019635 serious
Bug #1019635 [src:ruby-mail] ruby-mail: FTBFS with ruby3.1: ERROR: Test 
"ruby3.1" failed:expected NoMethodError with "Can not decode an entire 
message, try calling #decoded on the various fields and body or parts if it is 
a multipart message.", got # severity 1019637 serious
Bug #1019637 [src:ruby-memoizable] ruby-memoizable: FTBFS with ruby3.1: ERROR: 
Test "ruby3.1" failed:  Failure/Error: expect { subject }.to 
raise_error(NameError, 'No method bar is memoized')
Severity set to 'serious' from 'important'
> severity 1019638 serious
Bug #1019638 [src:ruby-memory-profiler] ruby-memory-profiler: FTBFS with 
ruby3.1: ERROR: Test "ruby3.1" failed.
Severity set to 'serious' from 'important'
> severity 1019639 serious
Bug #1019639 [src:ruby-minitest-hooks] ruby-minitest-hooks: FTBFS with ruby3.1: 
ERROR: Test "ruby3.1" failed.
Severity set to 'serious' from 'important'
> severity 1019640 serious
Bug #1019640 [src:ruby-mono-logger] ruby-mono-logger: FTBFS with ruby3.1: 
ERROR: Test "ruby3.1" failed: 
/usr/share/rubygems-integration/all/gems/simplecov-0.21.2/lib/simplecov.rb:354:in
 `start': coverage measurement is already setup (RuntimeError)
Severity set to 'serious' from 'important'
> severity 1019641 serious
Bug #1019641 [src:ruby-omniauth-auth0] ruby-omniauth-auth0: FTBFS: ERROR: Test 
"ruby3.0" failed:  Failure/Error: expect(last_response.status).to eq(302)
Severity set to 'serious' from 'important'
> severity 1019643 serious
Bug #1019643 [src:ruby-omniauth-oauth2-generic] ruby-omniauth-oauth2-generic: 
FTBFS with ruby3.1: ERROR: Test "ruby3.0" failed:  Failure/Error: 
expect(last_response.headers["Location"]).to 
match(%r{redirect_uri=https%3A%2F%2Fmy_server.com%2Foauth%2Fcallback&})
Severity set to 'serious' from 'important'
> severity 1019645 serious
Bug #1019645 [src:ruby-otr-activerecord] ruby-otr-activerecord: FTBFS with 
ruby3.1: ERROR: Test "ruby3.1" failed:  ArgumentError:
Severity set to 'serious' from 'important'
> severity 1019647 serious
Bug #1019647 [src:ruby-power-assert] ruby-power-assert: FTBFS with ruby3.1: 
ERROR: Test "ruby3.1" failed.
Severity set to 'serious' from 'important'
> severity 1019648 serious
Bug #1019648 [src:ruby-premailer-rails] ruby-premailer-rails: FTBFS with 
ruby3.1: ERROR: Test "ruby3.1" failed: RuntimeError:
Severity set to 'serious' from 'important'
> severity 1019650 serious
Bug #1019650 [src:ruby-rantly] ruby-rantly: FTBFS with ruby3.1: ERROR: Test 
"ruby3.1" failed: 
/usr/share/rubygems-integration/all/gems/simplecov-0.21.2/lib/simplecov.rb:354:in
 `start': coverage measurement is already setup (RuntimeError)
Severity set to 'serious' from 'important'
> severity 1019652 serious
Bug #1019652 [src:ruby-regexp-parser] ruby-regexp-parser: FTBFS with ruby3.1: 
ERROR: Test "ruby3.1" failed:   Failure/Error: expect(result[1]).to eq token
Severity set to 'serious' from 'important'
> severity 1019663 serious
Bug #1019663 [src:ruby-ronn] ruby-ronn: FTBFS with ruby3.1: ERROR: Test 
"ruby3.1" failed.
Severity set to 'serious' from 'important'
> severity 1019664 serious
Bug #1019664 

Bug#1022360: marked as done (activemq: FTBFS: make: *** [debian/rules:4: binary] Error 25)

[Debian Bug Tracking System]

Your message dated Mon, 24 Oct 2022 20:36:19 +
with message-id 
and subject line Bug#1022360: fixed in activemq 5.17.2+dfsg-1
has caused the Debian Bug report #1022360,
regarding activemq: FTBFS: make: *** [debian/rules:4: binary] Error 25
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.)


-- 
1022360: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022360
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: activemq
Version: 5.16.1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 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 --buildsystem=maven
>dh_update_autotools_config -O--buildsystem=maven
>dh_autoreconf -O--buildsystem=maven
>dh_auto_configure -O--buildsystem=maven
>   mh_patchpoms -plibactivemq-java --debian-build --keep-pom-version 
> --maven-repo=/<>/debian/maven-repo
> [ERROR] Cannot find parent dependency org.apache:apache:pom:18, use 
> --no-parent option to resolve this issue or install the parent POM in the 
> Maven repository
> [ERROR] Cannot find parent dependency 
> org.apache.activemq:activemq-parent:pom:5.16.1, use --no-parent option to 
> resolve this issue or install the parent POM in the Maven repository
> [ERROR] Cannot find parent dependency 
> org.apache.activemq:activemq-parent:pom:5.16.1, use --no-parent option to 
> resolve this issue or install the parent POM in the Maven repository
> [ERROR] Cannot find parent dependency 
> org.apache.activemq:activemq-parent:pom:5.16.1, use --no-parent option to 
> resolve this issue or install the parent POM in the Maven repository
> [ERROR] Cannot find parent dependency 
> org.apache.activemq:activemq-parent:pom:5.16.1, use --no-parent option to 
> resolve this issue or install the parent POM in the Maven repository
> [ERROR] Cannot find parent dependency 
> org.apache.activemq:activemq-parent:pom:5.16.1, use --no-parent option to 
> resolve this issue or install the parent POM in the Maven repository
> [ERROR] Cannot find parent dependency 
> org.apache.activemq:activemq-parent:pom:5.16.1, use --no-parent option to 
> resolve this issue or install the parent POM in the Maven repository
> [ERROR] Cannot find parent dependency 
> org.apache.activemq:activemq-parent:pom:5.16.1, use --no-parent option to 
> resolve this issue or install the parent POM in the Maven repository
> [ERROR] Cannot find parent dependency 
> org.apache.activemq:activemq-parent:pom:5.16.1, use --no-parent option to 
> resolve this issue or install the parent POM in the Maven repository
> [ERROR] Cannot find parent dependency 
> org.apache.activemq:activemq-parent:pom:5.16.1, use --no-parent option to 
> resolve this issue or install the parent POM in the Maven repository
> [ERROR] Cannot find parent dependency 
> org.apache.activemq:activemq-parent:pom:5.16.1, use --no-parent option to 
> resolve this issue or install the parent POM in the Maven repository
> [ERROR] Cannot find parent dependency 
> org.apache.activemq:activemq-parent:pom:5.16.1, use --no-parent option to 
> resolve this issue or install the parent POM in the Maven repository
> [ERROR] Cannot find parent dependency 
> org.apache.activemq:activemq-parent:pom:5.16.1, use --no-parent option to 
> resolve this issue or install the parent POM in the Maven repository
> [ERROR] Cannot find parent dependency 
> org.apache.activemq:activemq-parent:pom:5.16.1, use --no-parent option to 
> resolve this issue or install the parent POM in the Maven repository
> [ERROR] Cannot find parent dependency 
> org.apache.activemq:activemq-parent:pom:5.16.1, use --no-parent option to 
> resolve this issue or install the parent POM in the Maven repository
>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 
> -Dproperties.file.manual=/<>/debian/maven.properties 
> org.codehaus.plexus.classworlds.launcher.Launcher 
> -s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
> -Dmaven.repo.local=/<>/debian/maven-repo --batch-mode package 
> -DskipTests -Dnotimestamp=true -Dlocale=en_US
> [INFO] Scanning for projects...
> [ERROR] [ERROR] Some problems were encountered while processing the POMs:
> [ERROR] Invalid packaging for parent POM org.apache:apache:18, must be "pom" 
> but is 

Processed: multipath-tools: CVE-2022-41973 CVE-2022-41974

[Debian Bug Tracking System]

Processing control commands:

> found -1 0.7.9-3
Bug #1022742 [src:multipath-tools] multipath-tools: CVE-2022-41973 
CVE-2022-41974
Marked as found in versions multipath-tools/0.7.9-3.

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

Bug#1022742: multipath-tools: CVE-2022-41973 CVE-2022-41974

[Salvatore Bonaccorso]

Source: multipath-tools
Version: 0.9.0-4
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: car...@debian.org, Debian Security Team 
Control: found -1 0.7.9-3

Hi,

The following vulnerabilities were published for multipath-tools.

CVE-2022-41973[0]:
| Symlink attack

CVE-2022-41974[1]:
| Authorization bypass

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-41973
https://www.cve.org/CVERecord?id=CVE-2022-41973
[1] https://security-tracker.debian.org/tracker/CVE-2022-41974
https://www.cve.org/CVERecord?id=CVE-2022-41974
[2] https://www.openwall.com/lists/oss-security/2022/10/24/2

Regards,
Salvatore

Bug#1022286: gnome-shell-extension-manager: FTBFS: ModuleNotFoundError: No module named 'gi'

[Heather Ellsworth]

Ah yes you are right, I have moved the dependency to the control.in file 
and regenerated the control file. The changes have been pushed to the 
debian/master branch and I'll work with Jeremy to re-upload :)


Cheers,
Heather

On 10/23/22 11:04, Simon McVittie wrote:

Control: reassign -1 blueprint-compiler 0.4.0-3
Control: affects -1 + src:gnome-shell-extension-manager

On Sun, 23 Oct 2022 at 14:38:05 +0200, Lucas Nussbaum wrote:

Program blueprint-compiler found: YES (/usr/bin/blueprint-compiler)

...

Traceback (most recent call last):
   File "/usr/bin/blueprint-compiler", line 37, in 
 from blueprintcompiler import main

...

   File "/usr/lib/python3/dist-packages/blueprintcompiler/gir.py", line 24, in 

 import gi # type: ignore
ModuleNotFoundError: No module named 'gi'


This looks like a missing dependency in blueprint-compiler.

 From a brief look at the package, it seems like python3-gi might have been
added to debian/control, instead of adding it to debian/control.in and
then regenerating debian/control with `make -f debian/rules clean`. This
effectively results in the change being reverted whenever the package
is rebuilt.

 smcv

Bug#1022739: wxwidgets3.0: Do not release with bookworm

[Olly Betts]

Source: wxwidgets3.0
Version: 3.0.5.1+dfsg-5
Severity: serious
Justification: Opinion of package maintainer

We have packages of wxwidgets3.2 in unstable and testing, and a
transition is well under way:

https://release.debian.org/transitions/html/wxwidgets-3.2.html

The last upstream release of wxwidgets3.0 was 2½ years ago, and there's
very little upstream interest in bugs in it now.

Keeping wxwidgets3.0 for another release cycle without upstream support
doesn't seem a good idea, so opening an RC bug.

Cheers,
Olly

Bug#1021571: marked as done (smarty3: Parse error in /usr/share/php/smarty3/sysplugins/smarty_internal_templateparser.php on line 24)

[Debian Bug Tracking System]

Your message dated Mon, 24 Oct 2022 19:27:03 +
with message-id 
and subject line Bug#1021571: fixed in smarty3 3.1.47-1
has caused the Debian Bug report #1021571,
regarding smarty3: Parse error in 
/usr/share/php/smarty3/sysplugins/smarty_internal_templateparser.php on line 24
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.)


-- 
1021571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021571
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: smarty3
Version: 3.1.45-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I'm testing some build scripts and testing my package on a VM running bookworm, 
my application uses smarty3

Turns out that the latest smarty3 is broken, smarty_internal_templateparser.php 
has this bit of code between two classes:


   // line  "./lexer/smarty_internal_templateparser.y"
   0
   // line 11 "./lexer/smarty_internal_templateparser.y"

and that stray 0 breaks the template parser...since the template parser is 
really all smarty does, this breaks the package

My test case for the bug report is:

   setTemplateDir('/var/www/html/');
   $smarty->testInstall();
   
   // assign some content. This would typically come from
   // a database or other source, but we'll use static
   // values for the purpose of this example.
   $smarty->assign('name', 'george smith');
   $smarty->assign('address', '45th & Harris');
   
   $smarty->debugging = true;
   
   // display it
   $smarty->display('test.tpl');
   ?>

And test.tpl:



Info




User Information:

Name: {$name}
Address: {$address}








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

Kernel: Linux 5.19.0-2-amd64 (SMP w/12 CPU threads; PREEMPT)
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)
LSM: AppArmor: enabled

Versions of packages smarty3 depends on:
ii  php   2:8.1+92
ii  php-common2:92
ii  php8.1 [php]  8.1.7-1
ii  php8.1-cli [php-cli]  8.1.7-1+b1

smarty3 recommends no packages.

smarty3 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: smarty3
Source-Version: 3.1.47-1
Done: Mike Gabriel 

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

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated smarty3 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, 24 Oct 2022 20:52:45 +0200
Source: smarty3
Architecture: source
Version: 3.1.47-1
Distribution: unstable
Urgency: medium
Maintainer: Mike Gabriel 
Changed-By: Mike Gabriel 
Closes: 1021571
Changes:
 smarty3 (3.1.47-1) unstable; urgency=medium
 .
   * New upstream release.
   * debian/rules:
 + Disable configparser and templateparser creation temporarily. Use
   the files generated/provided by upstream for now.(Closes: #1021571).
Checksums-Sha1:
 faca4d0add7c566e05e30b6dbc37a1af23361f3b 1980 smarty3_3.1.47-1.dsc
 70ca3a4b318f0766e73cd7cdd1d8078f1b0cd5c8 266736 smarty3_3.1.47.orig.tar.gz
 a45cfa9a7ffeaff5e61e5e3bf2d3963a41ca2c99 5872 smarty3_3.1.47-1.debian.tar.xz
 f9f517be2a230c7901d67dddba2dc0e461bf1489 6866 smarty3_3.1.47-1_source.buildinfo
Checksums-Sha256:
 9a5226cb894e0f530c936e0b21c768715ae49a5acbc18a28d0ce1698d0586fb1 1980 
smarty3_3.1.47-1.dsc
 c38db4b6be9891dd6f20c5d96f475c4539e310bb67a0e2aad7d6d585f14c8be0 266736 
smarty3_3.1.47.orig.tar.gz
 eca8b8bf7aea31f50aeda3357bb8e337bfbcefb7584d2dfee114dbaf6ce9402c 5872 
smarty3_3.1.47-1.debian.tar.xz
 4f9e7e38cd65ab7a7a7a7308b0fadf83b224b2b5cc56eb73ccaafdc302e7c6c4 6866 
smarty3_3.1.47-1_source.buildinfo
Files:
 d951ba5828422deec1bf34c4fc9e614d 1980 web optional smarty3_3.1.47-1.dsc
 d1a27eb9553a61758d76edc589dc4a8c 266736 web optional smarty3_3.1.47.orig.tar.gz
 9254a6c8ebc2a195376714bd9af2b876 5872 web optional 

Bug#1022327: marked as done (intel-media-driver: FTBFS: media_ddi_encode_av1.cpp:437:65: error: ‘VAEncSequenceParameterBufferAV1’ has no member named ‘reserved8b’)

[Debian Bug Tracking System]

Your message dated Mon, 24 Oct 2022 19:24:04 +
with message-id 
and subject line Bug#1022327: fixed in intel-media-driver 22.6.0+dfsg1-1
has caused the Debian Bug report #1022327,
regarding intel-media-driver: FTBFS: media_ddi_encode_av1.cpp:437:65: error: 
‘VAEncSequenceParameterBufferAV1’ has no member named ‘reserved8b’
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.)


-- 
1022327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022327
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: intel-media-driver
Version: 22.5.1+dfsg1+really22.4.3-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> cd /<>/obj-x86_64-linux-gnu/media_driver && /usr/bin/c++ 
> -DCLASS_TRACE=0 -DENABLE_KERNELS -DIGFX_GEN11_ICLLP_SUPPORTED 
> -DIGFX_GEN11_JSL_SUPPORTED -DIGFX_GEN11_SUPPORTED -DIGFX_GEN12_ADLN_SUPPORTED 
> -DIGFX_GEN12_ADLP_SUPPORTED -DIGFX_GEN12_ADLS_SUPPORTED 
> -DIGFX_GEN12_DG1_SUPPORTED -DIGFX_GEN12_RKL_SUPPORTED -DIGFX_GEN12_SUPPORTED 
> -DIGFX_GEN12_TGLLP_CMFCPATCH_SUPPORTED -DIGFX_GEN12_TGLLP_CMFC_SUPPORTED 
> -DIGFX_GEN12_TGLLP_SUPPORTED -DIGFX_GEN12_TGLLP_SWSB_SUPPORTED 
> -DIGFX_GEN8_BDW_SUPPORTED -DIGFX_GEN8_SUPPORTED -DIGFX_GEN9_BXT_SUPPORTED 
> -DIGFX_GEN9_CFL_SUPPORTED -DIGFX_GEN9_CML_SUPPORTED 
> -DIGFX_GEN9_CMPV_SUPPORTED -DIGFX_GEN9_GLK_SUPPORTED 
> -DIGFX_GEN9_KBL_SUPPORTED -DIGFX_GEN9_SKL_SUPPORTED -DIGFX_GEN9_SUPPORTED 
> -DIGFX_MHW_INTERFACES_NEXT_SUPPORT -DMEDIA_VERSION=\"22.4.3\" 
> -DMEDIA_VERSION_DETAILS=\"\" -DVEBOX_AUTO_DENOISE_SUPPORTED=0 -DX11_FOUND 
> -D_AV1_DECODE_SUPPORTED -D_AV1_ENCODE_VDENC_SUPPORTED -D_AVC_DECODE_SUPPORTED 
> -D_AVC_ENCODE_VDENC_SUPPORTED -D_COMMON_ENCODE_SUPPORTED -D_FULL_OPEN_SOURCE 
> -D_HEVC_DECODE_SUPPORTED -D_HEVC_ENCODE_VDENC_SUPPORTED 
> -D_JPEG_DECODE_SUPPORTED -D_JPEG_ENCODE_SUPPORTED -D_MPEG2_DECODE_SUPPORTED 
> -D_RELEASE -D_VP8_DECODE_SUPPORTED -D_VP9_DECODE_SUPPORTED 
> -D_VP9_ENCODE_VDENC_SUPPORTED -D__STDC_CONSTANT_MACROS -D__STDC_LIMIT_MACROS 
> -D__VPHAL_SFC_SUPPORTED=1 
> -I/<>/media_driver/linux/common/os/i915/include 
> -I/<>/media_driver/linux/common/os/i915/include/uapi 
> -I/usr/include/igdgmm/util -I/usr/include/igdgmm/inc/common 
> -I/usr/include/igdgmm/inc -I/usr/include/igdgmm/GmmLib/inc 
> -I/usr/include/igdgmm/GmmLib -I/usr/include/igdgmm 
> -I/<>/media_common/agnostic/common/os 
> -I/<>/media_common/agnostic/common/codec/shared 
> -I/<>/media_common/agnostic/common/vp/hal 
> -I/<>/media_common/agnostic/common/hw/vdbox 
> -I/<>/media_common/agnostic/common/hw 
> -I/<>/media_common/agnostic/common/shared/user_setting 
> -I/<>/media_common/agnostic/common/shared 
> -I/<>/media_common/agnostic/common/media_interfaces 
> -I/<>/media_common/linux/common/os 
> -I/<>/media_driver/agnostic/common/cm 
> -I/<>/media_driver/agnostic/common/codec/hal 
> -I/<>/media_driver/agnostic/common/codec/kernel 
> -I/<>/media_driver/agnostic/common/codec/shared 
> -I/<>/media_driver/agnostic/common/cp 
> -I/<>/media_driver/agnostic/common/heap_manager 
> -I/<>/media_driver/agnostic/common/hw/vdbox 
> -I/<>/media_driver/agnostic/common/hw 
> -I/<>/media_driver/agnostic/common/media_interfaces 
> -I/<>/media_driver/agnostic/common/os 
> -I/<>/media_driver/agnostic/common/renderhal 
> -I/<>/media_driver/agnostic/common/shared/user_setting 
> -I/<>/media_driver/agnostic/common/shared 
> -I/<>/media_driver/agnostic/common/vp/hal 
> -I/<>/media_driver/agnostic/common/vp/kdll 
> -I/<>/media_driver/agnostic/common/vp/kernel 
> -I/<>/media_driver/agnostic/common/vp/cm_fc_ld 
> -I/<>/media_driver/agnostic/gen8/cm 
> -I/<>/media_driver/agnostic/gen8/codec/hal 
> -I/<>/media_driver/agnostic/gen8/hw/vdbox 
> -I/<>/media_driver/agnostic/gen8/hw 
> -I/<>/media_driver/agnostic/gen8/renderhal 
> -I/<>/media_driver/agnostic/gen8/vp/hal 
> -I/<>/media_driver/agnostic/gen8_bdw/codec/hal 
> -I/<>/media_driver/agnostic/gen8_bdw/hw/vdbox 
> -I/<>/media_driver/agnostic/gen8_bdw/renderhal 
> -I/<>/media_driver/agnostic/gen9/cm 
> -I/<>/media_driver/agnostic/gen9/codec/hal 
> -I/<>/media_driver/agnostic/gen9/hw/vdbox 
> -I/<>/media_driver/agnostic/gen9/hw 
> -I/<>/media_driver/agnostic/gen9/renderhal 
> -I/<>/media_driver/agnostic/gen9/vp/hal 
> -I/<>/media_driver/agnostic/gen9_bxt/codec/hal 
> -I/<>/media_driver/agnostic/gen9_bxt/hw/vdbox 
> -I/<>/media_driver/agnostic/gen9_bxt/vp/hal 
> -I/<>/media_driver/agnostic/gen9_skl/codec/hal 
> 

Processed: Raising severity of remaining wxwidgets3.2 transition blockers

[Debian Bug Tracking System]

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

> severity 1019823 serious
Bug #1019823 [src:passwordsafe] passwordsafe: Please transition to wxwidgets3.2
Severity set to 'serious' from 'important'
> severity 1019775 serious
Bug #1019775 [src:spatialite-gui] spatialite-gui: Please transition to 
wxwidgets3.2
Severity set to 'serious' from 'important'
> severity 1019768 serious
Bug #1019768 [src:grass] grass: Please transition to wxwidgets3.2
Severity set to 'serious' from 'important'
> severity 1019812 serious
Bug #1019812 [src:wxhexeditor] wxhexeditor: Please transition to wxwidgets3.2
Severity set to 'serious' from 'important'
> severity 1019835 serious
Bug #1019835 [src:filezilla] filezilla: Please transition to wxwidgets3.2
Severity set to 'serious' from 'important'
> severity 1019769 serious
Bug #1019769 [src:opencpn] opencpn: Please transition to wxwidgets3.2
Severity set to 'serious' from 'important'
> severity 1019799 serious
Bug #1019799 [src:libalien-wxwidgets-perl] libalien-wxwidgets-perl: Please 
transition to wxwidgets3.2
Severity set to 'serious' from 'important'
> severity 1019827 serious
Bug #1019827 [src:tintii] tintii: Please transition to wxwidgets3.2
Severity set to 'serious' from 'important'
> severity 1019808 serious
Bug #1019808 [src:openbabel] openbabel: Please transition to wxwidgets3.2
Severity set to 'serious' from 'important'
> severity 1019830 serious
Bug #1019830 [src:codeblocks] codeblocks: Please transition to wxwidgets3.2
Severity set to 'serious' from 'important'
> severity 1019762 serious
Bug #1019762 [src:saga] saga: Please transition to wxwidgets3.2
Severity set to 'serious' from 'important'
> severity 1019829 serious
Bug #1019829 [src:pgn2web] pgn2web: Please transition to wxwidgets3.2
Severity set to 'serious' from 'important'
> severity 1019791 serious
Bug #1019791 [src:stimfit] stimfit: Please transition to wxwidgets3.2
Severity set to 'serious' from 'important'
> severity 1019818 serious
Bug #1019818 [src:wxmaxima] wxmaxima: Please transition to wxwidgets3.2
Severity set to 'serious' from 'important'
> severity 1019792 serious
Bug #1019792 [src:springlobby] springlobby: Please transition to wxwidgets3.2
Severity set to 'serious' from 'important'
> severity 1019776 serious
Bug #1019776 [src:openmsx-catapult] openmsx-catapult: Please transition to 
wxwidgets3.2
Severity set to 'serious' from 'important'
> severity 1019784 serious
Bug #1019784 [src:scorched3d] scorched3d: Please transition to wxwidgets3.2
Severity set to 'serious' from 'important'
> severity 1019828 serious
Bug #1019828 [src:megaglest] megaglest: Please transition to wxwidgets3.2
Severity set to 'serious' from 'important'
> severity 1019819 serious
Bug #1019819 [src:qutemol] qutemol: Please transition to wxwidgets3.2
Severity set to 'serious' from 'important'
> severity 1019804 serious
Bug #1019804 [src:plee-the-bear] plee-the-bear: Please transition to 
wxwidgets3.2
Severity set to 'serious' from 'important'
> severity 1019814 serious
Bug #1019814 [src:icinga2] icinga2: Please transition to wxwidgets3.2
Severity set to 'serious' from 'important'
> severity 1019805 serious
Bug #1019805 [src:4pane] 4pane: Please transition to wxwidgets3.2
Severity set to 'serious' from 'important'
> severity 1019841 serious
Bug #1019841 [src:amule] amule: Please transition to wxwidgets3.2
Severity set to 'serious' from 'important'
> severity 1019772 serious
Bug #1019772 [src:freespace2-launcher-wxlauncher] 
freespace2-launcher-wxlauncher: Please transition to wxwidgets3.2
Severity set to 'serious' from 'important'
> severity 1019790 serious
Bug #1019790 [src:eviacam] eviacam: Please transition to wxwidgets3.2
Severity set to 'serious' from 'important'
> severity 1019824 serious
Bug #1019824 [src:3depict] 3depict: Please transition to wxwidgets3.2
Severity set to 'serious' from 'important'
> severity 1019773 serious
Bug #1019773 [src:asc] asc: Please transition to wxwidgets3.2
Severity set to 'serious' from 'important'
> severity 1019783 serious
Bug #1019783 [src:openyahtzee] openyahtzee: Please transition to wxwidgets3.2
Severity set to 'serious' from 'important'
> severity 1019806 serious
Bug #1019806 [src:sooperlooper] sooperlooper: Please transition to wxwidgets3.2
Severity set to 'serious' from 'important'
> severity 1019839 serious
Bug #1019839 [src:0ad] 0ad: Please transition to wxwidgets3.2
Severity set to 'serious' from 'important'
> severity 1019765 serious
Bug #1019765 [src:wxsvg] wxsvg: Please transition to wxwidgets3.2
Severity set to 'serious' from 'important'
> severity 1019837 serious
Bug #1019837 [src:treesheets] treesheets: Please transition to wxwidgets3.2
Severity set to 'serious' from 'important'
> severity 1019810 serious
Bug #1019810 [src:golly] golly: Please transition to wxwidgets3.2
Severity set to 'serious' from 'important'
> severity 1019782 serious
Bug #1019782 [src:gnudatalanguage] gnudatalanguage: Please transition to 
wxwidgets3.2
Severity set to 'serious' from 'important'
> severity 

Processed: still reproducible

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1002789 [src:python-pycdlib] python-pycdlib: FTBFS: failed tests
Severity set to 'serious' from 'important'

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

Bug#1022734: karabo-bridge: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity

[Lucas Nussbaum]

Source: karabo-bridge
Version: 0.6.1-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221024 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> copying karabo_bridge/tests/test_client.py -> 
> /<>/.pybuild/cpython3_3.10_karabo-bridge/build/karabo_bridge/tests
> copying karabo_bridge/tests/utils.py -> 
> /<>/.pybuild/cpython3_3.10_karabo-bridge/build/karabo_bridge/tests
> creating 
> /<>/.pybuild/cpython3_3.10_karabo-bridge/build/karabo_bridge/cli
> copying karabo_bridge/cli/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_karabo-bridge/build/karabo_bridge/cli
> copying karabo_bridge/cli/monitor.py -> 
> /<>/.pybuild/cpython3_3.10_karabo-bridge/build/karabo_bridge/cli
> copying karabo_bridge/cli/glimpse.py -> 
> /<>/.pybuild/cpython3_3.10_karabo-bridge/build/karabo_bridge/cli
> copying karabo_bridge/cli/simulation.py -> 
> /<>/.pybuild/cpython3_3.10_karabo-bridge/build/karabo_bridge/cli
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:240: cd 
> /<>/.pybuild/cpython3_3.10_karabo-bridge/build; python3.10 -m 
> pytest 
> = test session starts 
> ==
> platform linux -- Python 3.10.7, pytest-7.1.2, pluggy-1.0.0+repack
> rootdir: /<>
> collected 31 items
> 
> karabo_bridge/tests/test_client.py 
> E: Build killed with signal TERM after 150 minutes of inactivity


The full build log is available from:
http://qa-logs.debian.net/2022/10/24/karabo-bridge_0.6.1-3_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221024;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221024=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.

Bug#1022732: macaulay2: FTBFS: make: *** [debian/rules:18: binary] Error 25

[Lucas Nussbaum]

Source: macaulay2
Version: 1.20+ds-7
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221024 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 '/<>'
> jdupes -rl debian/macaulay2-common/usr/share/doc/Macaulay2
> make[1]: Leaving directory '/<>'
>dh_link -O--sourcedirectory=M2
>dh_linktree -O--sourcedirectory=M2
> dpkg-query: no path found matching pattern 
> /usr/share/javascript/katex/contrib/copy-tex.css
> dh_linktree: error: dpkg --search -- 
> /usr/share/fonts-glyphicons/glyphicons-halflings-regular.eot 
> /usr/share/fonts-glyphicons/glyphicons-halflings-regular.svg 
> /usr/share/fonts-glyphicons/glyphicons-halflings-regular.ttf 
> /usr/share/fonts-glyphicons/glyphicons-halflings-regular.woff 
> /usr/share/fonts-glyphicons/glyphicons-halflings-regular.woff2 
> /usr/share/fonts/truetype/katex/KaTeX_AMS-Regular.ttf 
> /usr/share/fonts/truetype/katex/KaTeX_AMS-Regular.woff 
> /usr/share/fonts/truetype/katex/KaTeX_AMS-Regular.woff2 
> /usr/share/fonts/truetype/katex/KaTeX_Caligraphic-Bold.ttf 
> /usr/share/fonts/truetype/katex/KaTeX_Caligraphic-Bold.woff 
> /usr/share/fonts/truetype/katex/KaTeX_Caligraphic-Bold.woff2 
> /usr/share/fonts/truetype/katex/KaTeX_Caligraphic-Regular.ttf 
> /usr/share/fonts/truetype/katex/KaTeX_Caligraphic-Regular.woff 
> /usr/share/fonts/truetype/katex/KaTeX_Caligraphic-Regular.woff2 
> /usr/share/fonts/truetype/katex/KaTeX_Fraktur-Bold.ttf 
> /usr/share/fonts/truetype/katex/KaTeX_Fraktur-Bold.woff 
> /usr/share/fonts/truetype/katex/KaTeX_Fraktur-Bold.woff2 
> /usr/share/fonts/truetype/katex/KaTeX_Fraktur-Regular.ttf 
> /usr/share/fonts/truetype/katex/KaTeX_Fraktur-Regular.woff 
> /usr/share/fonts/truetype/katex/KaTeX_Fraktur-Regular.woff2 
> /usr/share/fonts/truetype/katex/KaTeX_Main-Bold.ttf 
> /usr/share/fonts/truetype/katex/KaTeX_Main-Bold.woff 
> /usr/share/fonts/truetype/katex/KaTeX_Main-Bold.woff2 
> /usr/share/fonts/truetype/katex/KaTeX_Main-BoldItalic.ttf 
> /usr/share/fonts/truetype/katex/KaTeX_Main-BoldItalic.woff 
> /usr/share/fonts/truetype/katex/KaTeX_Main-BoldItalic.woff2 
> /usr/share/fonts/truetype/katex/KaTeX_Main-Italic.ttf 
> /usr/share/fonts/truetype/katex/KaTeX_Main-Italic.woff 
> /usr/share/fonts/truetype/katex/KaTeX_Main-Italic.woff2 
> /usr/share/fonts/truetype/katex/KaTeX_Main-Regular.ttf 
> /usr/share/fonts/truetype/katex/KaTeX_Main-Regular.woff 
> /usr/share/fonts/truetype/katex/KaTeX_Main-Regular.woff2 
> /usr/share/fonts/truetype/katex/KaTeX_Math-BoldItalic.ttf 
> /usr/share/fonts/truetype/katex/KaTeX_Math-BoldItalic.woff 
> /usr/share/fonts/truetype/katex/KaTeX_Math-BoldItalic.woff2 
> /usr/share/fonts/truetype/katex/KaTeX_Math-Italic.ttf 
> /usr/share/fonts/truetype/katex/KaTeX_Math-Italic.woff 
> /usr/share/fonts/truetype/katex/KaTeX_Math-Italic.woff2 
> /usr/share/fonts/truetype/katex/KaTeX_SansSerif-Bold.ttf 
> /usr/share/fonts/truetype/katex/KaTeX_SansSerif-Bold.woff 
> /usr/share/fonts/truetype/katex/KaTeX_SansSerif-Bold.woff2 
> /usr/share/fonts/truetype/katex/KaTeX_SansSerif-Italic.ttf 
> /usr/share/fonts/truetype/katex/KaTeX_SansSerif-Italic.woff 
> /usr/share/fonts/truetype/katex/KaTeX_SansSerif-Italic.woff2 
> /usr/share/fonts/truetype/katex/KaTeX_SansSerif-Regular.ttf 
> /usr/share/fonts/truetype/katex/KaTeX_SansSerif-Regular.woff 
> /usr/share/fonts/truetype/katex/KaTeX_SansSerif-Regular.woff2 
> /usr/share/fonts/truetype/katex/KaTeX_Script-Regular.ttf 
> /usr/share/fonts/truetype/katex/KaTeX_Script-Regular.woff 
> /usr/share/fonts/truetype/katex/KaTeX_Script-Regular.woff2 
> /usr/share/fonts/truetype/katex/KaTeX_Size1-Regular.ttf 
> /usr/share/fonts/truetype/katex/KaTeX_Size1-Regular.woff 
> /usr/share/fonts/truetype/katex/KaTeX_Size1-Regular.woff2 
> /usr/share/fonts/truetype/katex/KaTeX_Size2-Regular.ttf 
> /usr/share/fonts/truetype/katex/KaTeX_Size2-Regular.woff 
> /usr/share/fonts/truetype/katex/KaTeX_Size2-Regular.woff2 
> /usr/share/fonts/truetype/katex/KaTeX_Size3-Regular.ttf 
> /usr/share/fonts/truetype/katex/KaTeX_Size3-Regular.woff 
> /usr/share/fonts/truetype/katex/KaTeX_Size3-Regular.woff2 
> /usr/share/fonts/truetype/katex/KaTeX_Size4-Regular.ttf 
> /usr/share/fonts/truetype/katex/KaTeX_Size4-Regular.woff 
> /usr/share/fonts/truetype/katex/KaTeX_Size4-Regular.woff2 
> /usr/share/fonts/truetype/katex/KaTeX_Typewriter-Regular.ttf 
> /usr/share/fonts/truetype/katex/KaTeX_Typewriter-Regular.woff 
> /usr/share/fonts/truetype/katex/KaTeX_Typewriter-Regular.woff2 
> /usr/share/javascript/bootsidemenu/BootSideMenu.css 
> /usr/share/javascript/bootsidemenu/BootSideMenu.js 
> /usr/share/javascript/bootstrap/css/bootstrap.m

Bug#1022733: nova: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity

[Lucas Nussbaum]

Source: nova
Version: 2:26.0.0-1.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221024 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> nova.tests.unit.virt.vmwareapi.test_volumeops.VMwareVolumeOpsTestCase.test_iscsi_get_host_iqn_instance_not_found
>  ... ok
> nova.tests.unit.virt.vmwareapi.test_volumeops.VMwareVolumeOpsTestCase.test_update_volume_details
> nova.tests.unit.virt.vmwareapi.test_volumeops.VMwareVolumeOpsTestCase.test_update_volume_details
>  ... ok
> nova.tests.unit.volume.test_cinder.CinderClientTestCase.test_admin_context_without_token
> nova.tests.unit.volume.test_cinder.CinderClientTestCase.test_admin_context_without_token
>  ... ok
> nova.tests.unit.volume.test_cinder.CinderClientTestCase.test_create_v3_client_no_microversion
> nova.tests.unit.volume.test_cinder.CinderClientTestCase.test_create_v3_client_no_microversion
>  ... ok
> nova.tests.unit.volume.test_cinder.CinderClientTestCase.test_create_v3_client_with_microversion_available
> nova.tests.unit.volume.test_cinder.CinderClientTestCase.test_create_v3_client_with_microversion_available
>  ... ok
> nova.tests.unit.volume.test_cinder.CinderClientTestCase.test_create_v3_client_with_microversion_skip_version_check
> nova.tests.unit.volume.test_cinder.CinderClientTestCase.test_create_v3_client_with_microversion_skip_version_check
>  ... ok
> nova.tests.unit.volume.test_cinder.CinderClientTestCase.test_create_v3_client_with_microversion_too_new
> nova.tests.unit.volume.test_cinder.CinderClientTestCase.test_create_v3_client_with_microversion_too_new
>  ... ok
> nova.tests.unit.volume.test_cinder.CinderClientTestCase.test_load_auth_plugin_failed
> nova.tests.unit.volume.test_cinder.CinderClientTestCase.test_load_auth_plugin_failed
>  ... ok
> E: Build killed with signal TERM after 150 minutes of inactivity


The full build log is available from:
http://qa-logs.debian.net/2022/10/24/nova_26.0.0-1.1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221024;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221024=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.

Bug#933438: spek: Please rebuild against wxWidgets GTK 3 package

[Olly Betts]

Control: retitle -1 spek: Please transition to wxwidgets3.2

On Tue, Jul 30, 2019 at 10:05:39AM -0400, s...@techie.net wrote:
> Your package appears to be using the wxWidgets GTK 2 implementation.  In 
> Debian, we have had a GTK 3 implementation of wxWidgets for some time.  
> For the bullseye release, the wxWidgets package maintainers plan to 
> remove the GTK 2 version, so we kindly request that you switch your 
> package to use the GTK 3 version.

This transition happened and the GTK-2-using packages of wxwidgets3.0
were removed some time ago.

This bug was closed when spek was removed from unstable - presumably it
was reopened motivated by the ITP for spek (#1007814) to ensure it's
addressed by the reintroduced package, though really it will have to be
addressed because there just isn't a GTK 2 version to build against in
unstable any more.

However we're now in the most of the way through a transition to
wxwidgets3.2 and a bug to ensure a reintroduced package uses that
rather than wxwidgets3.0 does seem useful, so updating the bug to be
for that purpose.

The main build-dependency to use is libwxgtk3.2-dev - if you use
any of the wxWidgets libraries which we have separate binary packages
for you will also need the corresponding libwxgtk-*3.2-dev packages
too.

Transition tracker is:

https://release.debian.org/transitions/html/wxwidgets-3.2.html

Cheers,
Olly

Processed: Re: Bug#933438: spek: Please rebuild against wxWidgets GTK 3 package

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 spek: Please transition to wxwidgets3.2
Bug #933438 [spek] spek: Please rebuild against wxWidgets GTK 3 package
Changed Bug title to 'spek: Please transition to wxwidgets3.2' from 'spek: 
Please rebuild against wxWidgets GTK 3 package'.

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

Bug#1022343: [Pkg-pascal-devel] Bug#1022343: Bug#1022343: view3dscene: FTBFS: view3dscene.lpr(63, 17) Fatal: Can't find unit CastleCubeMaps used by view3dscene

[Abou Al Montacir]

On Mon, 2022-10-24 at 01:34 +0200, Michalis Kamburelis wrote:
> So my preferred way to solve this would be to just have view3dscene
> 4.2.0 in Debian.
Yes, I'm working on it!
-- 
Cheers,
Abou Al Montacir



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

Bug#1020211: marked as done (emacspeak: FTBFS: make[4]: *** [Makefile:322: emacspeak-loaddefs.el] Error 255)

[Debian Bug Tracking System]

Your message dated Mon, 24 Oct 2022 20:50:36 +0200
with message-id 
and subject line no longer fails, closing
has caused the Debian Bug report #1020211,
regarding emacspeak: FTBFS: make[4]: *** [Makefile:322: emacspeak-loaddefs.el] 
Error 255
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.)


-- 
1020211: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020211
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: emacspeak
Version: 53.0+dfsg-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220917 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 '/<>'
> emacs -batch -q -no-site-file  -f package-initialize  --eval '(setq 
> file-name-handler-alist nil gc-cons-threshold 6400  
> load-source-file-function  nil)'   -l ./emacspeak-load-path.el  \
> -l ./emacspeak-autoload.el  \
> -f emacspeak-auto-generate-autoloads
> Eager macro-expansion failure: (error "Cannot find suitable directory for 
> output in ‘native-comp-eln-load-path’")
> Eager macro-expansion failure: (error "Cannot find suitable directory for 
> output in ‘native-comp-eln-load-path’")
> Debugger entered--Lisp error: (error "Cannot find suitable directory for 
> output in ‘nati...")
>   error("Cannot find suitable directory for output in `nati...")
>   comp-trampoline-compile(funcall-interactively)
>   comp-subr-trampoline-install(funcall-interactively)
>   ad-add-advice(funcall-interactively (emacspeak nil t (advice lambda nil 
> "Set emacspeak  interactive flag if there is an adv..." (let 
> ((ems-called-interactively-p ems-called-interactively-p)) (when 
> (ems-record-interactive-p (ad-get-arg 0)) (setq ems-called-interactively-p 
> (ad-get-arg 0))) ad-do-it))) around nil)
>   ad-preactivate-advice(funcall-interactively (emacspeak nil t (advice lambda 
> nil "Set emacspeak  interactive flag if there is an adv..." (let 
> ((ems-called-interactively-p ems-called-interactively-p)) (when 
> (ems-record-interactive-p (ad-get-arg 0)) (setq ems-called-interactively-p 
> (ad-get-arg 0))) ad-do-it))) around nil)
>   #f(compiled-function (function args  body) "Define a piece of advice 
> for FUNCTION (a symbol).\nThe syntax of `defadvice' is as follows:\n\n  
> (defadvice FUNCTION (CLASS NAME [POSITION] [ARGLIST] FLAG...)\n
> [DOCSTRING] [INTERACTIVE-FORM]\nBODY...)\n\nFUNCTION ::= Name of the 
> function to be advised.\nCLASS ::= `before' | `around' | `after' | 
> `activation' | `deactivation'.\nNAME ::= Non-nil symbol that names this piece 
> of advice.\nPOSITION ::= `first' | `last' | NUMBER.  Optional, defaults to 
> `first',\nsee also `ad-add-advice'.\nARGLIST ::= An optional argument 
> list to be used for the advised function\ninstead of the argument list of 
> the original.  The first one found in\nbefore/around/after-advices will 
> be used.\nFLAG ::= `protect'|`disable'|`activate'|`compile'|`preactivate'.\n  
>   All flags can be specified with unambiguous initial substrings.\nDOCSTRING 
> ::= Optional documentation for this piece of advice.\nINTERACTIVE-FORM ::= 
> Optional interactive form to be used for the advised\nfunction.  The 
> first one found in before/around/after-advices will be used.\nBODY ::= Any 
> s-expression.\n\nSemantics of the various flags:\n`protect': The piece of 
> advice will be protected against non-local exits in\nany code that precedes 
> it.  If any around-advice of a function is protected\nthen automatically all 
> around-advices will be protected (the complete onion).\n\n`activate': All 
> advice of FUNCTION will be activated immediately if\nFUNCTION has been 
> properly defined prior to this application of `defadvice'.\n\n`compile': In 
> conjunction with `activate' specifies that the resulting\nadvised function 
> should be compiled.\n\n`disable': The defined advice will be disabled, hence, 
> it will not be used\nduring activation until somebody enables 
> it.\n\n`preactivate': Preactivates the advised FUNCTION at 
> macro-expansion/compile\ntime.  This generates a compiled advised definition 
> according to the current\nadvice state that will be used during activation if 
> appropriate.  Only use\nthis if the `defadvice' gets actually 
> compiled.\n\nusage: (defadvice FUNCTION (CLASS NAME [POSITION] [ARGLIST] 
> FLAG...)\n  [DOCSTRING] [INTERACTIVE-FORM]\n  BODY...)" 
> #)(funcall-interactively (around emacspeak pre 
> act comp) "Set emacspeak  interactive flag if there is an 

Bug#1020156: marked as done (epl: FTBFS: make: *** [debian/rules:6: build] Error 25)

[Debian Bug Tracking System]

Your message dated Mon, 24 Oct 2022 20:50:36 +0200
with message-id 
and subject line no longer fails, closing
has caused the Debian Bug report #1020156,
regarding epl: FTBFS: make: *** [debian/rules:6: build] Error 25
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.)


-- 
1020156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020156
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: epl
Version: 0.9-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220917 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 '/<>'
> true
> make[1]: Leaving directory '/<>'
>dh_elpa_test
>   emacs -batch -Q -l package --eval "(add-to-list 'package-directory-list 
> \"/usr/share/emacs/site-lisp/elpa\")" --eval "(add-to-list 
> 'package-directory-list \"/usr/share/emacs/site-lisp/elpa-src\")" -f 
> package-initialize -L . -L test -l test/epl-test.el --eval 
> \(ert-run-tests-batch-and-exit\)
> Running 18 tests (2022-09-17 20:06:40+, selector ‘t’)
>passed   1/18  epl-built-in-packages/catches-all (0.001642 sec)
>passed   2/18  epl-package-as-description/variable-must-be-a-symbol 
> (0.81 sec)
>passed   3/18  
> epl-package-as-description/variable-must-be-bound-to-epl-package (0.60 
> sec)
>   INFO Scraping files for smartie-package-autoloads.el... 
>   INFO Scraping files for smartie-package-autoloads.el...done
> Checking /<>/test/sandbox/smartie-package-1.2.3...
> Compiling 
> /<>/test/sandbox/smartie-package-1.2.3/smartie-package-autoloads.el...
> Compiling 
> /<>/test/sandbox/smartie-package-1.2.3/smartie-package-pkg.el...
> Compiling 
> /<>/test/sandbox/smartie-package-1.2.3/smartie-package.el...
> Done (Total of 1 file compiled, 2 skipped)
> Setting ‘package-selected-packages’ temporarily since "emacs -q" would 
> overwrite customizations
> Setting ‘package-selected-packages’ temporarily since "emacs -q" would 
> overwrite customizations
> Test epl-package-delete/should-not-be-installed backtrace:
>   comp-el-to-eln-filename("/<>/test/sandbox/smar
>   package--delete-directory("/<>/test/sandbox/sm
>   package-delete(#s(package-desc :name smartie-package :version (1 2 3
>   (with-no-warnings (package-delete (progn (or (progn (and (memq (type
>   (if (epl-package--package-desc-p package) (with-no-warnings (package
>   (let ((delete-by-moving-to-trash nil)) (if (epl-package--package-des
>   epl-package-delete(#s(epl-package :name smartie-package :description
>   (let ((package (car (epl-find-installed-packages 'smartie-package)))
>   (let ((smartie-package (epl-test-resource-file-name "smartie-package
>   (let ((package-user-dir epl-sandbox-directory)) (if (f-dir\? epl-san
>   (let ((lexical-binding t)) (let ((package-user-dir epl-sandbox-direc
>   (closure (t) nil (let ((lexical-binding t)) (let ((package-user-dir 
>   ert--run-test-internal(#s(ert--test-execution-info :test #s(ert-test
>   ert-run-test(#s(ert-test :name epl-package-delete/should-not-be-inst
>   ert-run-or-rerun-test(#s(ert--stats :selector t :tests [... ... ... 
>   ert-run-tests(t #f(compiled-function (event-type  event-args) #
>   ert-run-tests-batch(nil)
>   ert-run-tests-batch-and-exit()
>   command-line-1(("-l" "package" "--eval" "(add-to-list 'package-direc
>   command-line()
>   normal-top-level()
> Test epl-package-delete/should-not-be-installed condition:
> (error "Cannot find suitable directory for output in 
> ‘comp-native-load-path’.")
>FAILED   4/18  epl-package-delete/should-not-be-installed (0.295225 sec)
>   INFO Scraping files for smartie-package-autoloads.el... 
>   INFO Scraping files for smartie-package-autoloads.el...done
> Checking /<>/test/sandbox/smartie-package-1.2.3...
> Compiling 
> /<>/test/sandbox/smartie-package-1.2.3/smartie-package-autoloads.el...
> Compiling 
> /<>/test/sandbox/smartie-package-1.2.3/smartie-package-pkg.el...
> Compiling 
> /<>/test/sandbox/smartie-package-1.2.3/smartie-package.el...
> Done (Total of 1 file compiled, 2 skipped)
> Setting ‘package-selected-packages’ temporarily since "emacs -q" would 
> overwrite customizations
> Setting ‘package-selected-packages’ temporarily since "emacs -q" would 
> overwrite customizations
> Test epl-package-directory/should-work backtrace:
>   comp-el-to-eln-filename("/<>/test/sandbox/smar
>   package--delete-directory("/<>/test/sandbox/sm
>   package-delete(#s(package-desc :name smartie-package :version (1 2 3
>   (with-no-warnings 

Bug#1020173: marked as done (circe: FTBFS: make: *** [debian/rules:4: build] Error 25)

[Debian Bug Tracking System]

Your message dated Mon, 24 Oct 2022 20:50:36 +0200
with message-id 
and subject line no longer fails, closing
has caused the Debian Bug report #1020173,
regarding circe: FTBFS: make: *** [debian/rules:4: build] Error 25
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.)


-- 
1020173: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020173
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: circe
Version: 2.11-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220917 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 '/<>'
> skipping upstream build
> make[1]: Leaving directory '/<>'
>dh_elpa_test
>   buttercup -L .
> Loading /etc/emacs/site-start.d/00debian.el (source)...
> Loading /etc/emacs/site-start.d/50autoconf.el (source)...
> Package tls is deprecated
> Debugger entered--Lisp error: (error "Cannot find suitable directory for 
> output in ‘nati...")
>   error("Cannot find suitable directory for output in `nati...")
>   comp-trampoline-compile(select-window)
>   comp-subr-trampoline-install(select-window)
>   ad-add-advice(select-window (circe-server-track-select-window nil t (advice 
> lambda (window  norecord) "Remember the current buffer as the last 
> active buf..." (with-current-buffer (window-buffer window) (when 
> (derived-mode-p 'circe-mode) (let ((buf ...)) (ignore-errors 
> (with-circe-server-buffer ...))) after nil)
>   load-with-code-conversion("/<>/circe.el" 
> "/<>/circe.el" nil t)
>   require(circe)
>   load-with-code-conversion("/<>/tests/test-circe-co..." 
> "/<>/tests/test-circe-co..." nil t)
>   load("./tests/test-circe-color-nicks.el" nil t)
>   buttercup-run-discover()
>   command-line-1(("-L" "." "-l" "buttercup" "-f" "buttercup-run-discover" 
> "--"))
>   command-line()
>   normal-top-level()
> 
> dh_elpa_test: error: buttercup -L . returned exit code 255
> make: *** [debian/rules:4: build] Error 25


The full build log is available from:
http://qa-logs.debian.net/2022/09/17/circe_2.11-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220917;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220917=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 ---
Hi

In the same build conditions, this package does not fail to build anymore, so 
closing.

Lucas--- End Message ---

Bug#1017141: marked as done (gcc-10-cross-mipsen: FTBFS: conftest.c:80: undefined reference to `fprintf_unlocked')

[Debian Bug Tracking System]

Your message dated Mon, 24 Oct 2022 20:50:36 +0200
with message-id 
and subject line no longer fails, closing
has caused the Debian Bug report #1017141,
regarding gcc-10-cross-mipsen: FTBFS: conftest.c:80: undefined reference to 
`fprintf_unlocked'
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.)


-- 
1017141: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017141
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gcc-10-cross-mipsen
Version: 3+c5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220813 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> /usr/bin/ld: /tmp/ccQguDRA.o: in function `main':
> /<>/gcc/build/libcpp/conftest.c:80: undefined reference to 
> `fprintf_unlocked'
> collect2: error: ld returned 1 exit status


The full build log is available from:
http://qa-logs.debian.net/2022/08/13/gcc-10-cross-mipsen_3+c5_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220813;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220813=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 ---
Hi

In the same build conditions, this package does not fail to build anymore, so 
closing.

Lucas--- End Message ---

Bug#1016340: marked as done (openssh: FTBFS: Failed to copy 'etc/ssh/sshd_config': No such file or directory at /usr/share/dh-exec/dh-exec-install-rename line 68, <> line 7.)

[Debian Bug Tracking System]

Your message dated Mon, 24 Oct 2022 20:48:15 +0200
with message-id 
and subject line fixed in dh-exec in the meantime, so openssh no longer fails
has caused the Debian Bug report #1016340,
regarding openssh: FTBFS: Failed to copy 'etc/ssh/sshd_config': No such file or 
directory at /usr/share/dh-exec/dh-exec-install-rename line 68, <> line 7.
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.)


-- 
1016340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016340
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openssh
Version: 1:9.0p1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220728 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 '/<>'
> # Remove version control tags to avoid unnecessary conffile
> # resolution steps for administrators.
> sed -i '/\$OpenBSD:/d' \
>   debian/tmp/etc/ssh/moduli \
>   debian/tmp/etc/ssh/ssh_config \
>   debian/tmp/etc/ssh/sshd_config
> dh_install -Nopenssh-client-udeb -Nopenssh-server-udeb
> dh_install -popenssh-client-udeb -popenssh-server-udeb \
>   --sourcedir=debian/build-udeb
> Failed to copy 'etc/ssh/sshd_config': No such file or directory at 
> /usr/share/dh-exec/dh-exec-install-rename line 68, <> line 7.
> dh_install: error: debian/openssh-server.install (executable config) returned 
> exit code 127
> make[1]: *** [debian/rules:163: override_dh_install-arch] Error 25


The full build log is available from:
http://qa-logs.debian.net/2022/07/28/openssh_9.0p1-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220728;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220728=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 ---
X-CrossAssassin-Score: 37913--- End Message ---

Bug#1013572: marked as done (softhsm2: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2)

[Debian Bug Tracking System]

Your message dated Mon, 24 Oct 2022 20:50:36 +0200
with message-id 
and subject line no longer fails, closing
has caused the Debian Bug report #1013572,
regarding softhsm2: FTBFS: dh_auto_test: error: make -j8 check 
"TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2
to be marked as done.

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

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


-- 
1013572: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013572
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: softhsm2
Version: 2.6.1-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):
> make[6]: Entering directory '/<>/src/lib/test'
> FAIL: p11test
> 
>SoftHSM 2.6.1: src/lib/test/test-suite.log
> 
> 
> # TOTAL: 1
> # PASS:  0
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> .. contents:: :depth: 2
> 
> FAIL: p11test
> =
> 
> FFF.F...F..FF.
> 
> 
> !!!FAILURES!!!
> Test Results:
> Run:  25   Failures: 3   Errors: 0
> 
> 
> 1) test: InfoTests::testGetInfo (F) line: 124 TestsNoPINInitBase.cpp
> setUp() failed
> - equality assertion failed
> - Expected: 0
> - Actual  : 48
> 
> 
> 2) test: InfoTests::testGetFunctionList (F) line: 124 TestsNoPINInitBase.cpp
> setUp() failed
> - equality assertion failed
> - Expected: 0
> - Actual  : 48
> 
> 
> 3) test: InfoTests::testWaitForSlotEvent (F) line: 124 TestsNoPINInitBase.cpp
> setUp() failed
> - equality assertion failed
> - Expected: 0
> - Actual  : 48
> 
> 
> ...
> 
> 
> !!!FAILURES!!!
> Test Results:
> Run:  25   Failures: 2   Errors: 0
> 
> 
> 1) test: InfoTests::testGetInfo (F) line: 124 TestsNoPINInitBase.cpp
> setUp() failed
> - equality assertion failed
> - Expected: 0
> - Actual  : 48
> 
> 
> 2) test: InfoTests::testWaitForSlotEvent (F) line: 124 TestsNoPINInitBase.cpp
> setUp() failed
> - equality assertion failed
> - Expected: 0
> - Actual  : 48
> 
> 
> 
> 
> 
> !!!FAILURES!!!
> Test Results:
> Run:  25   Failures: 2   Errors: 0
> 
> 
> 1) test: InfoTests::testGetFunctionList (F) line: 124 TestsNoPINInitBase.cpp
> setUp() failed
> - equality assertion failed
> - Expected: 0
> - Actual  : 48
> 
> 
> 2) test: InfoTests::testWaitForSlotEvent (F) line: 124 TestsNoPINInitBase.cpp
> setUp() failed
> - equality assertion failed
> - Expected: 0
> - Actual  : 48
> 
> 
> ..
> 
> 
> OK (25 tests)
> 
> 
> FAIL p11test (exit status: 1)
> 
> 
> Testsuite summary for SoftHSM 2.6.1
> 
> # TOTAL: 1
> # PASS:  0
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> See src/lib/test/test-suite.log
> 
> make[6]: *** [Makefile:812: test-suite.log] Error 1
> make[6]: Leaving directory '/<>/src/lib/test'
> make[5]: *** [Makefile:920: check-TESTS] Error 2
> make[5]: Leaving directory '/<>/src/lib/test'
> make[4]: *** [Makefile:993: check-am] Error 2
> make[4]: Leaving directory '/<>/src/lib/test'
> make[3]: *** [Makefile:642: check-recursive] Error 1
> make[3]: Leaving directory '/<>/src/lib'
> make[2]: *** [Makefile:404: check-recursive] Error 1
> make[2]: Leaving directory '/<>/src'
> make[1]: *** [Makefile:566: check-recursive] Error 1
> make[1]: Leaving directory '/<>'
> dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 
> returned exit code 2


The full build log is available from:
http://qa-logs.debian.net/2022/06/24/softhsm2_2.6.1-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 

Bug#1005439: marked as done (ruby-mini-magick: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: expect(subject.exif["ExifVersion"]).to eq("0220"))

[Debian Bug Tracking System]

Your message dated Mon, 24 Oct 2022 20:50:36 +0200
with message-id 
and subject line no longer fails, closing
has caused the Debian Bug report #1005439,
regarding ruby-mini-magick: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: 
expect(subject.exif["ExifVersion"]).to eq("0220")
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.)


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

Hi,

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


Relevant part (hopefully):
>  Failure/Error: expect(subject.exif["ExifVersion"]).to eq("0220")
> 
>expected: "0220"
> got: nil
> 
>(compared using ==)
>  # ./spec/lib/mini_magick/image_spec.rb:409:in `block (5 levels) in  (required)>'
> 
> Finished in 4.38 seconds (files took 0.23502 seconds to load)
> 284 examples, 3 failures, 5 pending
> 
> Failed examples:
> 
> rspec './spec/lib/mini_magick/image_spec.rb[2:1:11:3]' # With GraphicsMagick 
> MiniMagick::Image#[] reads exif
> rspec './spec/lib/mini_magick/image_spec.rb[2:1:16:1]' # With GraphicsMagick 
> MiniMagick::Image#exif returns a hash of EXIF data
> rspec './spec/lib/mini_magick/image_spec.rb[2:1:16:2]' # With GraphicsMagick 
> MiniMagick::Image#exif decodes the ExifVersion
> 
> /usr/bin/ruby2.7 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec 
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby2.7" failed: 


The full build log is available from:
http://qa-logs.debian.net/2022/02/12/ruby-mini-magick_4.11.0-1_unstable.log

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

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

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

In the same build conditions, this package does not fail to build anymore, so 
closing.

Lucas--- End Message ---

Bug#1014966: onionshare: CVE-2021-41867 CVE-2021-41868 CVE-2022-21688 CVE-2022-21689 CVE-2022-21690 CVE-2022-21691 CVE-2022-21692 CVE-2022-21693 CVE-2022-21694 CVE-2022-21695 CVE-2022-21696

[Clément Hermann]

Le 24/10/2022 à 18:26, Clément Hermann a écrit :

Hi,

Le 23/10/2022 à 18:27, Clément Hermann a écrit :

Hi,

Le 22/10/2022 à 15:01, Salvatore Bonaccorso a écrit :

To be on safe side, explicitly confirming by upstream would be great.


Agreed. And asked upstream: 
https://github.com/onionshare/onionshare/issues/1633.


Upstream replied quickly (yay!) and confirms the known issues are 
fixed in 2.5.


Also, the detail of the vulnerable/patched versions has been updated. 
Quoting from the upstream issue:


Only affected >= 2.3 - < 2.5: CVE-2021-41867 
, CVE-2022-21691 
, CVE-2022-21695 
, CVE-2022-21696 

Only affected >= 2.2 - < 2.5: CVE-2022-21694 

Only affected >=2.0 - < 2.5: CVE-2022-21689 

Only affected >=2.0 - < 2.4: CVE-2021-41868 
 (Receive mode 
bug, fixed by changing the authentication from HTTP auth to using 
Client Auth in Tor itself)
All versions < 2.5: CVE-2022-21690 
, and possibly 
depending on the Qt version, CVE-2022-21688 



GHSA-jgm9-xpfj-4fq6 
 
is a complicated one, as a fix 
 we reduced the 
scope of access for Flatpak but you could argue that on 'native' 
Debian the whole file system, or at least the parts accessible to the 
user running OnionShare, is available not even in read-only mode. I'm 
not sure there's really a 'fix' for the deb package.


The advisories on 
https://github.com/onionshare/onionshare/security/advisories have been 
updated to reflect this.


I did more homework.

So, to summarize:
- CVE-2021-41867 , 
CVE-2022-21691 , 
CVE-2022-21695 , 
CVE-2022-21696  
aren't affecting Debian (stable has 2.2, unstable has 2.5). Which is 
good because the


- CVE-2022-21694  
affects Bullseye, but that might be an acceptable risk ? The issue is 
that CSP can only be turned on or off, not configured to allow js etc, 
so it is only useful for static websites. I believe that's the most 
common usage of a website with onionshare, and it's arguably a missing 
feature more than a vulnerability /per se/.


- CVE-2022-21689  fix 
should be easy to backport, at a glance: 
https://github.com/onionshare/onionshare/commit/096178a9e6133fd6ca9d95a00a67bba75ccab377


- CVE-2021-41868  
doesn't affect 2.2 I think, it must have been a mistake from mig5. I 
just asked for confirmation. I do hope so since it's a bad one.


- CVE-2022-21690  
seems like a one-line patch: 
https://github.com/onionshare/onionshare/commit/8f1e7ac224e54f57e43321bba2c2f9fdb5143bb0


- CVE-2022-21688  
seems like it should be worked around with the CVE-2022-21690 
 fix (OTF-001)?


I'd welcome input on those.

Cheers,

--
nodens

Bug#1022336: xz-utils: FTBFS: Can't exec "cmake": No such file or directory at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 526.

[Sebastian Andrzej Siewior]

On 2022-10-23 15:12:35 [+0200], Lucas Nussbaum wrote:
> Relevant part (hopefully):
> >  debian/rules build
> > dh build --parallel 
> > dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
> >dh_update_autotools_config -O--parallel
> >dh_auto_configure -O--parallel
> > dh_auto_configure: warning: Compatibility levels before 10 are deprecated 
> > (level 9 in use)
> > cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
> > -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
> > -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
> > -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF 
> > -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON 
> > -DFETCHCONTENT_FULLY_DISCONNECTED=ON "-GUnix Makefiles" 
> > -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu ..
> > Can't exec "cmake": No such file or directory at 
> > /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 526.

It autodetects cmake but shouldn't. It built fine a few days ago, not
sure what changed.
Aynway, I'm going to fix the hurd build and this, too.

Sebastian

Processed: Re: Bug#1021571: smarty3: Parse error in /usr/share/php/smarty3/sysplugins/smarty_internal_templateparser.php on line 24

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/smarty-php/smarty/issues/822
Bug #1021571 [smarty3] smarty3: Parse error in 
/usr/share/php/smarty3/sysplugins/smarty_internal_templateparser.php on line 24
Set Bug forwarded-to-address to 
'https://github.com/smarty-php/smarty/issues/822'.

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

Bug#1021571: smarty3: Parse error in /usr/share/php/smarty3/sysplugins/smarty_internal_templateparser.php on line 24

[Mike Gabriel]

Control: forwarded -1 https://github.com/smarty-php/smarty/issues/822

Hi Ed,

thanks for letting me know.

On  Mo 10 Okt 2022 23:43:15 CEST, Ed Martin wrote:


Package: smarty3
Version: 3.1.45-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I'm testing some build scripts and testing my package on a VM  
running bookworm, my application uses smarty3


Turns out that the latest smarty3 is broken,  
smarty_internal_templateparser.php has this bit of code between two  
classes:



   // line  "./lexer/smarty_internal_templateparser.y"
   0
   // line 11 "./lexer/smarty_internal_templateparser.y"

and that stray 0 breaks the template parser...since the template  
parser is really all smarty does, this breaks the package


My test case for the bug report is:

   setTemplateDir('/var/www/html/');
   $smarty->testInstall();

   // assign some content. This would typically come from
   // a database or other source, but we'll use static
   // values for the purpose of this example.
   $smarty->assign('name', 'george smith');
   $smarty->assign('address', '45th & Harris');

   $smarty->debugging = true;

   // display it
   $smarty->display('test.tpl');
   ?>

And test.tpl:



Info




User Information:

Name: {$name}
Address: {$address}






I have just filed an upstream bug report for this:
https://github.com/smarty-php/smarty/issues/822

Let's see if we get some help with this from upstream.

Mike
--

DAS-NETZWERKTEAM
c\o Technik- und Ökologiezentrum Eckernförde
Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde
mobile: +49 (1520) 1976 148
landline: +49 (4351) 850 8940

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgp2AOV_fcz65.pgp
Description: Digitale PGP-Signatur

Bug#1019552: marked as done (castle-game-engine: flaky autopkgtest on armel: Invalid floating point operation)

[Debian Bug Tracking System]

Your message dated Mon, 24 Oct 2022 20:15:38 +0200
with message-id <9c0168f9a28696e74078488011258b34f7bbbd3e.ca...@sfr.fr>
and subject line Re: [Pkg-pascal-devel] Bug#1019552: castle-game-engine: flaky 
autopkgtest on armel: Invalid floating point operation
has caused the Debian Bug report #1019552,
regarding castle-game-engine: flaky autopkgtest on armel: Invalid floating 
point operation
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.)


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

Source: castle-game-engine
Version: 7.0~alpha.1+dfsg-8
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

I looked at the results of the autopkgtest of your package. I noticed 
that it regularly fails on armel.


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

Don't hesitate to reach out if you need help and some more information
from our infrastructure.

Paul

https://ci.debian.net/data/autopkgtest/testing/armel/c/castle-game-engine/25918325/log.gz

Number of errors:3
Number of failures:  0

List of errors:
  Error:
Message:   TTestGame.TestGameData: Invalid floating point 
operation

Exception class:   EInvalidOp
Exception message: Invalid floating point operation
at   $0001D8F8

  Error:
Message: 
TTestCastleLevels.TestSetDestroyPlayerAfterLevelLoad: Invalid floating 
point operation

Exception class:   EInvalidOp
Exception message: Invalid floating point operation
at   $0001D8F8

  Error:
Message:   TTestCastleResources.TestResourceFromCode: 
Invalid floating point operation

Exception class:   EInvalidOp
Exception message: Invalid floating point operation
at   $0001D8F8



 be initialized, TestLoadBufferException doesn't really do anything
OpenAL cannot be initialized, TestNotPcmEncodingWarning doesn't really 
do anything


sources.php .
test_castle_game_engine: Warning: Animation "idle_afraid" not found on ""
test_castle_game_engine: Warning: Animation "idle_afraid" not found on ""
Heap dump by heaptrc unit of 
/tmp/autopkgtest-lxc.2jgotpmc/downtmp/build.IQz/src/tests/test_castle_game_engine

2489062 memory blocks allocated : 461523828/472110728
2486632 memory blocks freed : 461398932/471978752
2430 unfreed memory blocks : 124896
True heap size : 5079040
True free heap : 4683424
Should be : 4713784
Call trace for block $F677F4B0 size 32
  $00A15400
  $00A152D8
  $00A11278
  $00A179A0
  $009CBD70
  $009DA37C
  $009E0F30
  $008BF9C4
  $007AE970
  $00B3489C
  $00B35F00
  $00B374E8
  $001028B8  TTESTCASTLERESOURCES__TESTRESOURCEFROMCODE,  line 67 of 
./code/testcastleresources.pas

  $00107F14
  $00107DA8
  $00109E5C
Call trace for block $F6831F00 size 24
  $007F0264
  $007F1670
  $006D8A0C
  $006DBF38
  $006DC248
  $0074F698
  $00B509BC
  $00B51ED0
  $00B51A38
  $00B51C1C
  $00B42890
  $00B41208
  $00B413A0
  $001028FC  TTESTCASTLERESOURCES__TESTRESOURCEFROMCODE,  line 70 of 
./code/testcastleresources.pas

  $00107F14
  $00107DA8
Call trace for block $F6831D80 size 12
  $0021D484
  $0081FCB4
  $008003E8
  $0081FAF8
  $006E98D8
  $006D2E10
  $006DE308
  $00B509A4
  $00B51ED0
  $00B51A38
  $00B51C1C
  $00B42890
  $00B41208
  $00B413A0
  $001028FC  TTESTCASTLERESOURCES__TESTRESOURCEFROMCODE,  line 70 of 
./code/testcastleresources.pas

  $00107F14
Call trace for block $F6831E00 size 24
  $0081FCB4
  $008003E8
  $0081FAF8
  $006E98D8
  $006D2E10
  $006DE308
  $00B509A4
  $00B51ED0
  $00B51A38
  $00B51C1C
  $00B42890
  $00B41208
  $00B413A0
  $001028FC  TTESTCASTLERESOURCES__TESTRESOURCEFROMCODE,  line 70 of 
./code/testcastleresources.pas

  $00107F14
  $00107DA8
Call trace for block $F63CA400 size 84
  $008204CC
  $00800DC0
  $00800574
  $0081FCA8
  $008003E8
  $0081FAF8
  $006E98D8
  $006D2E10
  $006DE308
  $00B509A4
  $00B51ED0
  $00B51A38
  $00B51C1C
  $00B42890
  $00B41208
  $00B413A0
Call trace for block $F70B1C80 size 22
  $00800D94
  $00800574
  $0081FCA8
  $008003E8
  $0081FAF8
  $006E98D8
  $006D2E10
  $006DE308
  $00B509A4
  $00B51ED0
  $00B51A38
  $00B51C1C
  $00B42890
  $00B41208
  $00B413A0
  $001028FC  TTESTCASTLERESOURCES__TESTRESOURCEFROMCODE,  line 70 of 
./code/testcastleresources.pas

Call trace for block $F63CA340 size 84
  $008204CC
  $00800D5C
  $00800574
  $0081FCA8
  

Bug#1022728: src:gnome-subtitles: fails to migrate to testing for too long: FTBFS on 32 bit archs

[Paul Gevers]

Source: gnome-subtitles
Version: 1.6-2.1
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:gnome-subtitles has been trying to migrate 
for 61 days [2]. Hence, I am filing this bug. Your package failed to 
build on our 32 bit architectures where it used to build successfully 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 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=gnome-subtitles



OpenPGP_signature
Description: OpenPGP digital signature

Processed: Re: Bug#1021062: fixed in bash 5.2-2

[Debian Bug Tracking System]

Processing control commands:

> reopen 1021062
Bug #1021062 {Done: Matthias Klose } [libreadline8] bash: non 
existent locale crashes bash
Bug #1022564 {Done: Matthias Klose } [libreadline8] locale 
related segmentation fault
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions bash/5.2-2.
No longer marked as fixed in versions bash/5.2-2.

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

Bug#1021062: fixed in bash 5.2-2

[Aurelien Jarno]

control: reopen 1021062

On 2022-10-24 09:04, Debian FTP Masters wrote:
> Source: bash
> Source-Version: 5.2-2
> Done: Matthias Klose 
> 
> We believe that the bug you reported is fixed in the latest version of
> bash, 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 1021...@bugs.debian.org,
> and the maintainer will reopen the bug report if appropriate.
> 
> Debian distribution maintenance software
> pp.
> Matthias Klose  (supplier of updated bash 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)
> 
> 
> Format: 1.8
> Date: Mon, 24 Oct 2022 10:34:28 +0200
> Source: bash
> Architecture: source
> Version: 5.2-2
> Distribution: unstable
> Urgency: medium
> Maintainer: Matthias Klose 
> Changed-By: Matthias Klose 
> Closes: 1021062
> Changes:
>  bash (5.2-2) unstable; urgency=medium
>  .
>* Apply upstream patches 001 - 002.
>  - Expanding unset arrays in an arithmetic context can cause a
>segmentation fault.
>  - Starting bash with an invalid locale specification for
>LC_ALL/LANG/LC_CTYPE can cause the shell to crash. Closes: #1021062.

This is the wrong bug number, the problem might be fixed in bash, but is
still present in libreadline8. Reopening.

Regards
Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net


signature.asc
Description: PGP signature

Processed: Re: Bug#1022564: locale related segmentation fault

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libreadline8
Bug #1022564 [libc6] locale related segmentation fault
Bug reassigned from package 'libc6' to 'libreadline8'.
No longer marked as found in versions glibc/2.35-3.
Ignoring request to alter fixed versions of bug #1022564 to the same values 
previously set
> forcemerge 1021062 -1
Bug #1021062 {Done: Matthias Klose } [libreadline8] bash: non 
existent locale crashes bash
Bug #1022564 [libreadline8] locale related segmentation fault
Set Bug forwarded-to-address to 
'http://git.savannah.gnu.org/cgit/readline.git/commit/?id=7274faabe97ce53d6b464272d7e6ab6c1392837b'.
Severity set to 'grave' from 'important'
Marked Bug as done
Marked as fixed in versions bash/5.2-2.
The source libreadline8 and version 8.2-1 do not appear to match any binary 
packages
Marked as found in versions libreadline8/8.2-1.
Added tag(s) patch.
Merged 1021062 1022564

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

Bug#1021658: Processed: autopkgtest regressions are RC (and this one also blocks the perl transition)

[Paul Gevers]

Hi,

On 24-10-2022 12:00, Adrian Bunk wrote:

On Sun, Oct 23, 2022 at 12:35:41PM +0200, Paul Gevers wrote:

We'll handle it somehow yes.


It seems someone already handled it or it disappeared by itself.


Yes, I scheduled the tests with *less* packages from unstable than 
britney and those passed.



Any further ideas how to handle the situation?


We'll handle perl, you can handle TL yourself by filling an RC bug.


The autopkgtest regression in latexml already prevents the migration of TL.


I think Hilmar was afraid of what happens after latexml is removed from 
testing. Than TL migrates and breaks latexml for users of testing that 
don't immediately remove packages that are no longer in testing.



The only possible action on the TL side will be after latexml is fixed
to add Breaks in TL against unfixed versions of latexml to avoid users
(or test environments) ending up with incompatble combinations.


That, but I think it's reasonable *for some time* to prevent TL to 
migrate even if latexml is already removed. Having said that, being 60 
days out-of-sync between unstable and testing is by default RC too, so 
the "for some time" isn't extremely long.


Paul


OpenPGP_signature
Description: OpenPGP digital signature

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

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:cawbird
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #1016551 (http://bugs.debian.org/1016551)
> # Bug title: cawbird: Switch to librest 1.0 and libsoup3
> #  * https://github.com/IBBoard/cawbird/issues/464
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 1016551 + fixed-upstream
Bug #1016551 [src:cawbird] cawbird: Switch to librest 1.0 and libsoup3
Added tag(s) fixed-upstream.
> usertags 1016551 - status-open
Usertags were: status-open.
There are now no usertags set.
> usertags 1016551 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

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

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:pgbouncer
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #1021859 (http://bugs.debian.org/1021859)
> # Bug title: pgbouncer FTBFS: test failures
> #  * https://github.com/pgbouncer/pgbouncer/issues/769
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 1021859 + fixed-upstream
Bug #1021859 [src:pgbouncer] pgbouncer FTBFS: test failures
Added tag(s) fixed-upstream.
> usertags 1021859 - status-open
Usertags were: status-open.
There are now no usertags set.
> usertags 1021859 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

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

[Debian Bug Tracking System]

Your message dated Mon, 24 Oct 2022 17:23:36 +
with message-id 
and subject line Bug#1022235: fixed in zeroinstall-injector 2.18-2
has caused the Debian Bug report #1022235,
regarding src:zeroinstall-injector: 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.)


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

Source: zeroinstall-injector
Version: 2.16-2
Severity: serious
Control: close -1 2.18-1
Tags: sid bookworm ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 60 days as having a Release Critical bug in 
testing [1]. Your package src:zeroinstall-injector has been trying to 
migrate for 62 days [2]. Hence, I am filing this bug. Your last version 
failed to build from source on armel, mips64el and mipsel while it built 
there successfully 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 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=zeroinstall-injector



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: zeroinstall-injector
Source-Version: 2.18-2
Done: Thomas Leonard 

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

Debian distribution maintenance software
pp.
Thomas Leonard  (supplier of updated zeroinstall-injector 
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, 24 Oct 2022 13:25:32 +
Source: zeroinstall-injector
Architecture: source
Version: 2.18-2
Distribution: unstable
Urgency: medium
Maintainer: Thomas Leonard 
Changed-By: Thomas Leonard 
Closes: 1022235
Changes:
 zeroinstall-injector (2.18-2) unstable; urgency=medium
 .
   * Fix build on bytecode-only platforms. Closes: #1022235.
Checksums-Sha1:
 e89709206e532462b3203f71392a89152f298d01 2541 zeroinstall-injector_2.18-2.dsc
 e21a202dcaa4e75b99fbe91aa7354e050e1fa857 476748 
zeroinstall-injector_2.18.orig.tar.bz2
 61195b672bd8b1753c63739ce4d53111ea21a546 566 
zeroinstall-injector_2.18.orig.tar.bz2.asc
 48fd84f983953fcd589c0688684c23acf7f9d63f 15080 
zeroinstall-injector_2.18-2.debian.tar.xz
 bc8379440563eaa33a006d2bbefefcc066b93b9e 15469 
zeroinstall-injector_2.18-2_source.buildinfo
Checksums-Sha256:
 1165d03ff56d7c9918bac2dff1eeae69af5be730f0905ebe1fcff6e6018de824 2541 
zeroinstall-injector_2.18-2.dsc
 22668e969ed405686e822b794b1a0a5ae98cd60c5663bb6006cef4f28cafd223 476748 
zeroinstall-injector_2.18.orig.tar.bz2
 1f20aa1629684a1d361e839d1a050142e8d79c9d80d486d99866a41af0e9b721 566 
zeroinstall-injector_2.18.orig.tar.bz2.asc
 29ae5b3a69c7beb09f9c0148ab648a3012f7fc6bd5a80ec2475739c06ed5ad76 15080 
zeroinstall-injector_2.18-2.debian.tar.xz
 8b6e29cc4123ea302ad3e7e7314ff80eddb04636595af05a7443d1019b535b92 15469 

Bug#1022211: marked as done (xml2rfc: Test failures with Weasyprint 57.0)

[Debian Bug Tracking System]

Your message dated Mon, 24 Oct 2022 13:00:25 -0400
with message-id <18728086.UmEVTKLrzi@zini-1880>
and subject line Re: xml2rfc: Test failures with Weasyprint 57.0
has caused the Debian Bug report #1022211,
regarding xml2rfc: Test failures with Weasyprint 57.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.)


-- 
1022211: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022211
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xml2rfc
Version: 3.13.1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Using FTBFS as it's the closest thing we have to an autopkgtest
regression severity.  xml2rfc autopkgtest fails in Unstable with
Weasyprint 57.0:

==
ERROR: setUpClass (__main__.PdfWriterTests)
--
Traceback (most recent call last):
  File "/tmp/autopkgtest-lxc.48kx6p_4/downtmp/build.obL/src/xxx/test.py", line 
495, in setUpClass
cls.elements_pdfxml = xmldoc(None, bytes=elements_pdfdoc)
  File "/usr/lib/python3/dist-packages/xml2rfc/walkpdf.py", line 96, in xmldoc
return lxml.etree.fromstring(text)
  File "src/lxml/etree.pyx", line 3254, in lxml.etree.fromstring
  File "src/lxml/parser.pxi", line 1913, in lxml.etree._parseMemoryDocument
  File "src/lxml/parser.pxi", line 1793, in lxml.etree._parseDoc
  File "src/lxml/parser.pxi", line 1082, in 
lxml.etree._BaseParser._parseUnicodeDoc
  File "src/lxml/parser.pxi", line 615, in 
lxml.etree._ParserContext._handleParseResultDoc
  File "src/lxml/parser.pxi", line 725, in lxml.etree._handleParseResult
  File "src/lxml/parser.pxi", line 654, in lxml.etree._raiseParseError
  File "", line 14199
lxml.etree.XMLSyntaxError: PCDATA invalid Char value 23, line 14199, column 11

--
Ran 42 tests in 21.851s

FAILED (errors=1)

https://ci.debian.net/data/autopkgtest/testing/amd64/x/xml2rfc/27394437/log.gz

Upstream is apparently aware since (I discovered after uploading
Weasyprint) they have recently pinned the Weasyprint dependency to
<57.0.

I did file an issue upstream:

https://github.com/ietf-tools/xml2rfc/issues/921

Scott K
--- End Message ---
--- Begin Message ---
On Sat, 22 Oct 2022 00:01:32 -0400 Scott Kitterman  
wrote:
...
> https://ci.debian.net/data/autopkgtest/testing/amd64/x/xml2rfc/27394437/
log.gz
> 
> Upstream is apparently aware since (I discovered after uploading
> Weasyprint) they have recently pinned the Weasyprint dependency to
> <57.0.
> 
> I did file an issue upstream:
> 
> https://github.com/ietf-tools/xml2rfc/issues/921

Confirmed to be a Weasyprint issue, fixed upstream:

https://github.com/Kozea/WeasyPrint/commit/
71e9e257ccc7780f3c4e04893b11210bd06ad626

Closing.

Scott K--- End Message ---

Bug#1022352: marked as done (lua-mode: FTBFS: tests failed)

[Debian Bug Tracking System]

Your message dated Mon, 24 Oct 2022 16:35:26 +
with message-id 
and subject line Bug#1022352: fixed in lua-mode 20210802-2
has caused the Debian Bug report #1022352,
regarding lua-mode: FTBFS: tests failed
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.)


-- 
1022352: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022352
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lua-mode
Version: 20210802-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 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 '/<>'
> Loading /etc/emacs/site-start.d/00debian.el (source)...
> Loading /etc/emacs/site-start.d/50autoconf.el (source)...
> Loading /etc/emacs/site-start.d/00debian.el (source)...
> Loading /etc/emacs/site-start.d/50autoconf.el (source)...
> Loading /etc/emacs/site-start.d/00debian.el (source)...
> Loading /etc/emacs/site-start.d/50autoconf.el (source)...
> Loading /etc/emacs/site-start.d/00debian.el (source)...
> Loading /etc/emacs/site-start.d/50autoconf.el (source)...
> version is 20210802
> make[1]: Leaving directory '/<>'
>dh_elpa_test
>   buttercup -L .
> Loading /etc/emacs/site-start.d/00debian.el (source)...
> Loading /etc/emacs/site-start.d/50autoconf.el (source)...
> Warning (buttercup): Found duplicate spec names in suite: 
> ("lua-skip-ws-and-comments-forward respects limit when escaping multi-line 
> comment 1: limit=8 \"--[[<1>   <2> ]] \\n\"")
> Running 392 out of 410 specs.
> 
> Test electric mode
>   works with curly braces
>   works with curly braces (18.56ms)
>   works with parentheses
>   works with parentheses (1.38ms)
>   works with end
>   works with end (1.51ms)
>   works with else
>   works with else (1.51ms)
>   works with elseif
>   works with elseif (1.46ms)
> 
> Electric pair mode
>   skips parens when electric-pair-skip-self is t
>   skips parens when electric-pair-skip-self is t (2.01ms)
> 
> Test fill-paragraph
>   fills single-line comment
>   fills single-line comment (0.56ms)
>   fills comment after code
>   fills comment after code (0.49ms)
>   fills multiline comment
>   fills multiline comment  PENDING (0.06ms)
>   does not spill comments into code (issue #25)
>   does not spill comments into code (issue #25) (15.26ms)
> 
> Test fill-paragraph preserves point position
>   doesn't move point if nothing has changed
>   doesn't move point if nothing has changed (1.08ms)
>   doesn't move point in refilled region
>   doesn't move point in refilled region (2.51ms)
>   doesn't move point if nothing has changed (multi-line)
>   doesn't move point if nothing has changed (multi-line) (0.82ms)
> 
> Fontification of built-ins
>   fontifies built-ins
>   fontifies built-ins (0.30ms)
>   fontifies built-ins with spaces between members
>   fontifies built-ins with spaces between members (0.30ms)
>   doesn't fontify things that look like built-ins
>   doesn't fontify things that look like built-ins (0.66ms)
>   fontifies built-in class if method is not built-in
>   fontifies built-in class if method is not built-in (0.23ms)
>   fontifies built-ins after concatenation operator
>   fontifies built-ins after concatenation operator (0.19ms)
> 
> Fontification of constants
>   fontifies constants
>   fontifies constants (0.19ms)
>   fontifies constants used as attributes
>   fontifies constants used as attributes (0.18ms)
> 
> Fontification of keywords
>   fontifies keywords
>   fontifies keywords (0.25ms)
>   fontifies keywords used as attributes
>   fontifies keywords used as attributes (0.23ms)
> 
> Fontification of variables
>   fontifies "local foo, bar, baz = 1, 2, 3"
>   fontifies "local foo, bar, baz = 1, 2, 3" (0.21ms)
>   fontifies "local foo, bar, baz"
>   fontifies "local foo, bar, baz" (0.18ms)
>   fontifies "local x =" at end of buffer
>   fontifies "local x =" at end of buffer (0.14ms)
>   fontifies local "x =" at end of line
>   fontifies local "x =" at end of line (0.17ms)
>   does not fontify "for" inside strings
>   does not fontify "for" inside strings (0.22ms)
>   fontifies "for x123 ="
>   fontifies "for x123 =" (0.15ms)
>   fontifies "for x, y, z"
>   fontifies "for x, y, z" (0.17ms)
> 
> Fontification 

Bug#1022301: marked as done (altos: FTBFS: ../aes/ao_aes.c:303:5: error: 'xShiftSubst.constprop' accessing 32 bytes in a region of size 16 [-Werror=stringop-overflow=])

[Debian Bug Tracking System]

Your message dated Mon, 24 Oct 2022 16:34:20 +
with message-id 
and subject line Bug#1022301: fixed in altos 1.9.11-2
has caused the Debian Bug report #1022301,
regarding altos: FTBFS: ../aes/ao_aes.c:303:5: error: 'xShiftSubst.constprop' 
accessing 32 bytes in a region of size 16 [-Werror=stringop-overflow=]
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.)


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

Hi,

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


Relevant part (hopefully):
> make[4]: Entering directory '/<>/src/telelco-v0.2'
>   NICKLE ../util/ao-make-product.5c ao_product.h
>   CC  ao_boot_chain.o
>   CC  ao_interrupt.o
>   CC  ao_product.o
>   CC  ao_romconfig.o
>   CC  ao_cmd.o
>   CC  ao_config.o
>   CC  ao_task.o
>   CC  ao_led_stm.o
>   CC  ao_stdio.o
>   CC  ao_panic.o
>   CC  ao_timer.o
>   CC  ao_mutex.o
>   CC  ao_freq.o
>   CC  ao_dma_stm.o
>   CC  ao_spi_stm.o
>   CC  ao_beep_stm.o
>   CC  ao_eeprom_stm.o
>   CC  ao_fast_timer.o
>   CC  ao_lcd_stm.o
>   CC  ao_usb_stm.o
>   CC  ao_exti_stm.o
>   CC  ao_cc1120.o
>   CC  ao_radio_cmac.o
>   CC  ao_aes.o
> In function 'xrijndaelEncrypt',
> inlined from 'ao_aes_run' at ../aes/ao_aes.c:396:2:
> ../aes/ao_aes.c:303:5: error: 'xShiftSubst.constprop' accessing 32 bytes in a 
> region of size 16 [-Werror=stringop-overflow=]
>   303 | xShiftSubst(block2, block, shift, BC, xS);
>   | ^
> ../aes/ao_aes.c: In function 'ao_aes_run':
> ../aes/ao_aes.c:303:5: note: referencing argument 2 of type 'word32 *' {aka 
> 'long unsigned int *'}
> ../aes/ao_aes.c:97:20: note: in a call to function 'xShiftSubst.constprop'
>97 | static inline void xShiftSubst(word32 res[MAXBC], word32 a[MAXBC],
>   |^~~
> In function 'xrijndaelEncrypt',
> inlined from 'ao_aes_run' at ../aes/ao_aes.c:396:2:
> ../aes/ao_aes.c:309:3: error: 'xShiftSubst.constprop' accessing 32 bytes in a 
> region of size 16 [-Werror=stringop-overflow=]
>   309 |   xShiftSubst(block2, block, shift, BC, xS);
>   |   ^
> ../aes/ao_aes.c: In function 'ao_aes_run':
> ../aes/ao_aes.c:309:3: note: referencing argument 2 of type 'word32 *' {aka 
> 'long unsigned int *'}
> ../aes/ao_aes.c:97:20: note: in a call to function 'xShiftSubst.constprop'
>97 | static inline void xShiftSubst(word32 res[MAXBC], word32 a[MAXBC],
>   |^~~
> cc1: all warnings being treated as errors
> make[4]: *** [../Makefile.defs:50: ao_aes.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/10/23/altos_1.9.11-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221023=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: altos
Source-Version: 1.9.11-2
Done: Bdale Garbee 

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

Debian distribution maintenance software
pp.
Bdale Garbee  (supplier of updated altos 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, 24 Oct 2022 10:02:35 -0600
Source: altos
Architecture: source
Version: 

Bug#1014966: onionshare: CVE-2021-41867 CVE-2021-41868 CVE-2022-21688 CVE-2022-21689 CVE-2022-21690 CVE-2022-21691 CVE-2022-21692 CVE-2022-21693 CVE-2022-21694 CVE-2022-21695 CVE-2022-21696

[Clément Hermann]

Hi,

Le 23/10/2022 à 18:27, Clément Hermann a écrit :

Hi,

Le 22/10/2022 à 15:01, Salvatore Bonaccorso a écrit :


Thanks for the quick reply! (much appreciated). I think it would be
good to get a confirmation from upstream and if possible to have
those advisories updates. E.g.
https://github.com/onionshare/onionshare/security/advisories/GHSA-x7wr-283h-5h2v 


while mentioning "affected versions < 2.4" the patched version remains
"none". this might be that the < 2.4 just reflects the point in time
when the advisory was filled. OTOH you have arguments with the v2.5
release information that they might all be fixed.

To be on safe side, explicitly confirming by upstream would be great.


Agreed. And asked upstream: 
https://github.com/onionshare/onionshare/issues/1633.


Upstream replied quickly (yay!) and confirms the known issues are fixed 
in 2.5.


Also, the detail of the vulnerable/patched versions has been updated. 
Quoting from the upstream issue:


Only affected >= 2.3 - < 2.5: CVE-2021-41867 
, CVE-2022-21691 
, CVE-2022-21695 
, CVE-2022-21696 

Only affected >= 2.2 - < 2.5: CVE-2022-21694 

Only affected >=2.0 - < 2.5: CVE-2022-21689 

Only affected >=2.0 - < 2.4: CVE-2021-41868 
 (Receive mode bug, 
fixed by changing the authentication from HTTP auth to using Client 
Auth in Tor itself)
All versions < 2.5: CVE-2022-21690 
, and possibly 
depending on the Qt version, CVE-2022-21688 



GHSA-jgm9-xpfj-4fq6 
 
is a complicated one, as a fix 
 we reduced the 
scope of access for Flatpak but you could argue that on 'native' 
Debian the whole file system, or at least the parts accessible to the 
user running OnionShare, is available not even in read-only mode. I'm 
not sure there's really a 'fix' for the deb package.


The advisories on 
https://github.com/onionshare/onionshare/security/advisories have been 
updated to reflect this.


--
nodens

Bug#1021891: marked as done (rsass: autopkgtest regression: no matching package named `arc-swap` found)

[Debian Bug Tracking System]

Your message dated Mon, 24 Oct 2022 16:21:19 +
with message-id 
and subject line Bug#1021891: fixed in rsass 0.26.0-2
has caused the Debian Bug report #1021891,
regarding rsass: autopkgtest regression: no matching package named `arc-swap` 
found
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.)


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

Source: rsass
Version: 0.26.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
rsass  from testing0.26.0-1
all others from testingfrom testing

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

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


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/r/rsass/27178838/log.gz

debian cargo wrapper: options, profiles, parallel: ['parallel=64'] [] 
['-j64']
debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu, 
x86_64-linux-gnu
debian cargo wrapper: linking /usr/share/cargo/registry/* into 
/tmp/tmp.3vENjMmwHj/registry/
debian cargo wrapper: options, profiles, parallel: ['parallel=64'] [] 
['-j64']
debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu, 
x86_64-linux-gnu
debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1', 
'/usr/bin/cargo', '-Zavoid-dev-deps', 'test', '--verbose', '--verbose', 
'-j64', '--target', 'x86_64-unknown-linux-gnu', '--all-targets'],) {}

error: no matching package named `arc-swap` found
location searched: registry `crates-io`
required by package `rsass v0.26.0 (/usr/share/cargo/registry/rsass-0.26.0)`
autopkgtest [08:19:18]: test librust-rsass-dev:default



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: rsass
Source-Version: 0.26.0-2
Done: Jonas Smedegaard 

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated rsass 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, 24 Oct 2022 17:37:23 +0200
Source: rsass
Architecture: source
Version: 0.26.0-2
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard 
Changed-By: Jonas Smedegaard 
Closes: 1021891
Changes:
 rsass (0.26.0-2) unstable; urgency=medium
 .
   * fix typo in previous changelog entry
   * stop overzealously provide versioned virtual packages
   * drop patch 1001, obsoleted by Debian package upgrade;
 (build-)depend on librust-arc-swap-1+default-dev
 (not librust-arc-swap+default-dev);
 closes: bug#1021891, thanks to Paul Gevers
   * simplify build, using local fork of dh-cargo
Checksums-Sha1:
 526d8bdf1772fc30c0b906597eb0bf3e694f08b1 2568 rsass_0.26.0-2.dsc
 6e503c5c9748e33bee7d71bbc6d5741ccf79ef1d 24916 rsass_0.26.0-2.debian.tar.xz
 09adf900b96e8d5a9d6f1b68661bd5e1a6c930ff 13450 rsass_0.26.0-2_amd64.buildinfo
Checksums-Sha256:
 f4e53558c09b33529a1a60a5cea2f5214bf1848b8768e4420801bfb6f5eae1c1 2568 
rsass_0.26.0-2.dsc
 158003ce2dea250fe1a1f540401615f4a9eb6f5092ab97acc5f190ba09791c99 24916 
rsass_0.26.0-2.debian.tar.xz
 011a16fc4aeb30a0a38bec6c69c491f1f11c273d9074de158c8724606880c709 13450 
rsass_0.26.0-2_amd64.buildinfo
Files:
 155d68e19f270edae15c49bec2af2eba 2568 rust optional rsass_0.26.0-2.dsc
 208be75062f385e260f1e41e62f05f9a 24916 rust optional 
rsass_0.26.0-2.debian.tar.xz
 b825d767a546104520adba696cf98e47 13450 rust optional 

Bug#1022137:

[Jeremy Bicha]

On Mon, Oct 24, 2022 at 9:45 AM Archisman Panigrahi  wrote:
> Will the patch be backported to Debian Bookworm?

Yes, it will land in Bookworm automatically in a few days.

Thank you,
Jeremy Bicha

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

[Debian Bug Tracking System]

Your message dated Mon, 24 Oct 2022 15:36:46 +
with message-id 
and subject line Bug#1020121: fixed in ndcube 2.0.2-2
has caused the Debian Bug report #1020121,
regarding ndcube: FTBFS: dh_auto_test: error: pybuild --test -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.)


-- 
1020121: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020121
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ndcube
Version: 2.0.2-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220917 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 '/<>'
> dh_auto_build
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:508: 
> SetuptoolsDeprecationWarning: The license_file parameter is deprecated, use 
> license_files instead.
>   warnings.warn(msg, warning_class)
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.10_ndcube/build/ndcube
> copying ndcube/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_ndcube/build/ndcube
> copying ndcube/ndcube.py -> 
> /<>/.pybuild/cpython3_3.10_ndcube/build/ndcube
> copying ndcube/ndcube_sequence.py -> 
> /<>/.pybuild/cpython3_3.10_ndcube/build/ndcube
> copying ndcube/global_coords.py -> 
> /<>/.pybuild/cpython3_3.10_ndcube/build/ndcube
> copying ndcube/conftest.py -> 
> /<>/.pybuild/cpython3_3.10_ndcube/build/ndcube
> copying ndcube/_version.py -> 
> /<>/.pybuild/cpython3_3.10_ndcube/build/ndcube
> copying ndcube/version.py -> 
> /<>/.pybuild/cpython3_3.10_ndcube/build/ndcube
> copying ndcube/ndcollection.py -> 
> /<>/.pybuild/cpython3_3.10_ndcube/build/ndcube
> creating 
> /<>/.pybuild/cpython3_3.10_ndcube/build/ndcube/visualization
> copying ndcube/visualization/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_ndcube/build/ndcube/visualization
> copying ndcube/visualization/base.py -> 
> /<>/.pybuild/cpython3_3.10_ndcube/build/ndcube/visualization
> copying ndcube/visualization/plotting_utils.py -> 
> /<>/.pybuild/cpython3_3.10_ndcube/build/ndcube/visualization
> copying ndcube/visualization/mpl_sequence_plotter.py -> 
> /<>/.pybuild/cpython3_3.10_ndcube/build/ndcube/visualization
> copying ndcube/visualization/mpl_plotter.py -> 
> /<>/.pybuild/cpython3_3.10_ndcube/build/ndcube/visualization
> copying ndcube/visualization/descriptor.py -> 
> /<>/.pybuild/cpython3_3.10_ndcube/build/ndcube/visualization
> creating /<>/.pybuild/cpython3_3.10_ndcube/build/ndcube/utils
> copying ndcube/utils/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_ndcube/build/ndcube/utils
> copying ndcube/utils/wcs.py -> 
> /<>/.pybuild/cpython3_3.10_ndcube/build/ndcube/utils
> copying ndcube/utils/cube.py -> 
> /<>/.pybuild/cpython3_3.10_ndcube/build/ndcube/utils
> copying ndcube/utils/collection.py -> 
> /<>/.pybuild/cpython3_3.10_ndcube/build/ndcube/utils
> copying ndcube/utils/sequence.py -> 
> /<>/.pybuild/cpython3_3.10_ndcube/build/ndcube/utils
> copying ndcube/utils/misc.py -> 
> /<>/.pybuild/cpython3_3.10_ndcube/build/ndcube/utils
> copying ndcube/utils/wcs_high_level_conversion.py -> 
> /<>/.pybuild/cpython3_3.10_ndcube/build/ndcube/utils
> creating /<>/.pybuild/cpython3_3.10_ndcube/build/ndcube/wcs
> copying ndcube/wcs/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_ndcube/build/ndcube/wcs
> creating /<>/.pybuild/cpython3_3.10_ndcube/build/ndcube/tests
> copying ndcube/tests/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_ndcube/build/ndcube/tests
> copying ndcube/tests/test_sequence_plotting.py -> 
> /<>/.pybuild/cpython3_3.10_ndcube/build/ndcube/tests
> copying ndcube/tests/test_ndcube.py -> 
> /<>/.pybuild/cpython3_3.10_ndcube/build/ndcube/tests
> copying ndcube/tests/test_ndcollection.py -> 
> /<>/.pybuild/cpython3_3.10_ndcube/build/ndcube/tests
> copying ndcube/tests/test_ndcubesequence.py -> 
> /<>/.pybuild/cpython3_3.10_ndcube/build/ndcube/tests
> copying ndcube/tests/helpers.py -> 
> /<>/.pybuild/cpython3_3.10_ndcube/build/ndcube/tests
> copying ndcube/tests/test_global_coords.py -> 
> /<>/.pybuild/cpython3_3.10_ndcube/build/ndcube/tests
> creating 
> /<>/.pybuild/cpython3_3.10_ndcube/build/ndcube/extra_coords
> copying ndcube/extra_coords/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_ndcube/build/ndcube/extra_coords
> copying ndcube/extra_coords/extra_coords.py -> 
> /<>/.pybuild/cpython3_3.10_ndcube/build/ndcube/extra_coords
> copying ndcube/extra_coords/table_coord.py -> 
> 

Bug#1022211: xml2rfc: Test failures with Weasyprint 57.0

[Scott Kitterman]

On Sat, 22 Oct 2022 00:01:32 -0400 Scott Kitterman  
wrote:
> Package: xml2rfc
> Version: 3.13.1-1
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source
> 
> Using FTBFS as it's the closest thing we have to an autopkgtest
> regression severity.  xml2rfc autopkgtest fails in Unstable with
> Weasyprint 57.0:
> 
> ==
> ERROR: setUpClass (__main__.PdfWriterTests)
> --
> Traceback (most recent call last):
>   File "/tmp/autopkgtest-lxc.48kx6p_4/downtmp/build.obL/src/xxx/test.py", 
line 495, in setUpClass
> cls.elements_pdfxml = xmldoc(None, bytes=elements_pdfdoc)
>   File "/usr/lib/python3/dist-packages/xml2rfc/walkpdf.py", line 96, in 
xmldoc
> return lxml.etree.fromstring(text)
>   File "src/lxml/etree.pyx", line 3254, in lxml.etree.fromstring
>   File "src/lxml/parser.pxi", line 1913, in lxml.etree._parseMemoryDocument
>   File "src/lxml/parser.pxi", line 1793, in lxml.etree._parseDoc
>   File "src/lxml/parser.pxi", line 1082, in 
lxml.etree._BaseParser._parseUnicodeDoc
>   File "src/lxml/parser.pxi", line 615, in 
lxml.etree._ParserContext._handleParseResultDoc
>   File "src/lxml/parser.pxi", line 725, in lxml.etree._handleParseResult
>   File "src/lxml/parser.pxi", line 654, in lxml.etree._raiseParseError
>   File "", line 14199
> lxml.etree.XMLSyntaxError: PCDATA invalid Char value 23, line 14199, column 
11
> 
> --
> Ran 42 tests in 21.851s
> 
> FAILED (errors=1)
> 
> https://ci.debian.net/data/autopkgtest/testing/amd64/x/xml2rfc/27394437/
log.gz
> 
> Upstream is apparently aware since (I discovered after uploading
> Weasyprint) they have recently pinned the Weasyprint dependency to
> <57.0.
> 
> I did file an issue upstream:
> 
> https://github.com/ietf-tools/xml2rfc/issues/921
> 

I narrowed down the Weasyprint commit that leads to the failure and asked for 
feedback from that upstream:

https://github.com/Kozea/WeasyPrint/issues/1752

If that doesn't prove fruitful, I am open to patching Debian's weasyprint to 
fix the issue.

Scott K

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

Bug#1021055: marked as done (asmjit autopkgtest times out)

[Debian Bug Tracking System]

Your message dated Mon, 24 Oct 2022 15:05:05 +
with message-id 
and subject line Bug#1021055: fixed in asmjit 0.0~git20221018.8f2c237-1
has caused the Debian Bug report #1021055,
regarding asmjit autopkgtest times out
to be marked as done.

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

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


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

Source: asmjit
Version: 0.0~git20211214.2a706fd-1
Severity: serious
User: debian...@lists.debian.org
Usertags: timeout

Dear maintainer(s),

Your package has an autopkgtest, great. However, it fails. What's worse, 
it fails because it seems to hang since recently and eventually times 
out due to autopkgtest. Can you please investigate the situation and fix 
it? I copied some of the output at the bottom of this report.


The release team has announced [1] that failing autopkgtest on amd64 and 
arm64 are considered RC in testing. Also tests that time out (while 
normally running in much less time) are bad for our infrastructure. I 
have added your package to our reject_list and will remove it once this 
bug is closed.


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


Paul

[1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html

https://ci.debian.net/packages/a/asmjit/

[ 97%] Built target asmjit_test_instinfo
[ 98%] Building CXX object 
CMakeFiles/asmjit_test_compiler.dir/test/asmjit_test_compiler.cpp.o
[ 99%] Building CXX object 
CMakeFiles/asmjit_test_compiler.dir/test/asmjit_test_compiler_x86.cpp.o

[100%] Linking CXX executable asmjit_test_compiler
[100%] Built target asmjit_test_compiler
Running tests...
Test project /tmp/autopkgtest-lxc.zi7__ym3/downtmp/build.EGf/src/build
Start 1: asmjit_test_unit
autopkgtest [08:30:54]: ERROR: timed out on command


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: asmjit
Source-Version: 0.0~git20221018.8f2c237-1
Done: Andrius Merkys 

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

Debian distribution maintenance software
pp.
Andrius Merkys  (supplier of updated asmjit 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, 24 Oct 2022 10:48:04 -0400
Source: asmjit
Architecture: source
Version: 0.0~git20221018.8f2c237-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Deep Learning Team 

Changed-By: Andrius Merkys 
Closes: 1021055
Changes:
 asmjit (0.0~git20221018.8f2c237-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version 0.0~git20221018.8f2c237 (Closes: #1021055)
Checksums-Sha1:
 203ab045b5e5f70540b5756c4c11e81f0403544a 2213 
asmjit_0.0~git20221018.8f2c237-1.dsc
 6515d52968ba68f83996cc53d194584758e9f721 648652 
asmjit_0.0~git20221018.8f2c237.orig.tar.xz
 70733031c4596f90310b28a01893644542dc8c8f 4124 
asmjit_0.0~git20221018.8f2c237-1.debian.tar.xz
 5aba0f220b2bd8c8472421a954acda905adc1b28 7568 
asmjit_0.0~git20221018.8f2c237-1_source.buildinfo
Checksums-Sha256:
 3864b8262fc75dd5fd200efd7f36173f7d232209fe9b839b5d2ef18bf965fe67 2213 
asmjit_0.0~git20221018.8f2c237-1.dsc
 a378cc57cf8a8a13f7fa8c0097dcc7de92457ae31bd9b73266ef04753020ab92 648652 
asmjit_0.0~git20221018.8f2c237.orig.tar.xz
 82967ae61aed1437498d65c30edc60827d47c456d5bc762423570cbc3bd91827 4124 
asmjit_0.0~git20221018.8f2c237-1.debian.tar.xz
 9afe74a9f6cb61ce612167e11cc7dd16bbcc4fe93840dad71dbd7e1497105375 7568 
asmjit_0.0~git20221018.8f2c237-1_source.buildinfo
Files:
 adb87849734f62d99ecc207578747acb 2213 libs optional 
asmjit_0.0~git20221018.8f2c237-1.dsc
 0f05ffa4d98435d39fcbe52a9a713860 648652 libs optional 
asmjit_0.0~git20221018.8f2c237.orig.tar.xz
 13d31d377c4524a89ec7270b481787d1 4124 libs optional 
asmjit_0.0~git20221018.8f2c237-1.debian.tar.xz
 4339a94d188cc58f00b355f1abc2035a 7568 libs optional 
asmjit_0.0~git20221018.8f2c237-1_source.buildinfo

-BEGIN PGP SIGNATURE-

Processed: tagging 1022132

[Debian Bug Tracking System]

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

> # cf. forwarded: https://salsa.debian.org/debian/gnumeric/-/merge_requests/2
> tags 1022132 + patch
Bug #1022132 [src:gnumeric] gnumeric: FTBFS on ppc64el: error: initializer 
element is not constant
Added tag(s) patch.
> thanks
Stopping processing here.

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

Processed: Re: subversion: "svn --non-interactive status -v svn-md5" started by emacs hangs

[Debian Bug Tracking System]

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

> found 1022711 1.14.2-3
Bug #1022711 [subversion] svn tries to read a directory on a different 
filesystem and hangs
Marked as found in versions subversion/1.14.2-3.
>
End of message, stopping processing here.

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

Bug#1022722: tftp-hpa: missing versioned Breaks+Replaces: tftp (<< 0.17-23.1)

[Andreas Beckmann]

Package: tftp-hpa
Version: 5.2+20150808-1.3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts replaces-without-breaks

Hi,

during a test with piuparts and DOSE tools I noticed your package causes
removal of files that also belong to another package.
This is caused by using Replaces without corresponding Breaks.

Since tftp was turned into a transitional package in 0.17-23.1, tftp-hpa
needs to Breaks+Replaces the older versions to ensure smooth upgrades
and prevent partial upgrades as is currently possible with the
unversioned Replaces: ftfp.

Andreas

Bug#1022137:

[Archisman Panigrahi]

Will the patch be backported to Debian Bookworm?

Bug#1022296: marked as done (pgloader: FTBFS: build-dependency not installable: postgresql-14-ip4r)

[Debian Bug Tracking System]

Your message dated Mon, 24 Oct 2022 13:38:20 +
with message-id 
and subject line Bug#1022296: fixed in pgloader 3.6.9-1
has caused the Debian Bug report #1022296,
regarding pgloader: FTBFS: build-dependency not installable: postgresql-14-ip4r
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.)


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

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: buildapp (>= 1.5), cl-abnf, cl-alexandria, cl-asdf (>= 
> 3.0.3), cl-asdf-finalizers, cl-asdf-system-connections, cl-bordeaux-threads 
> (>= 0.8.3), cl-cffi (>= 1:0.12.0), cl-command-line-arguments, cl-csv (>= 
> 20180712), cl-db3 (>= 20200212), cl-drakma, cl-esrap, cl-fad, 
> cl-flexi-streams, cl-interpol, cl-ixf, cl-local-time, cl-log, cl-lparallel, 
> cl-markdown, cl-md5, cl-metabang-bind, cl-mssql, cl-mustache, cl-plus-ssl (>= 
> 20190204), cl-postmodern, cl-ppcre, cl-py-configparser, cl-qmynd, cl-quri, 
> cl-simple-date, cl-split-sequence, cl-sqlite, cl-trivial-backtrace, 
> cl-trivial-utf-8, cl-unicode, cl-usocket, cl-utilities, cl-uuid, cl-yason, 
> cl-zs3, debhelper-compat (= 13), gawk, help2man, libsqlite3-dev, 
> postgresql-14-ip4r | postgresql-ip4r, python3-sphinx, 
> python3-sphinx-rtd-theme, sbcl (>= 1.1.13), tzdata, build-essential, fakeroot
> Filtered Build-Depends: buildapp (>= 1.5), cl-abnf, cl-alexandria, cl-asdf 
> (>= 3.0.3), cl-asdf-finalizers, cl-asdf-system-connections, 
> cl-bordeaux-threads (>= 0.8.3), cl-cffi (>= 1:0.12.0), 
> cl-command-line-arguments, cl-csv (>= 20180712), cl-db3 (>= 20200212), 
> cl-drakma, cl-esrap, cl-fad, cl-flexi-streams, cl-interpol, cl-ixf, 
> cl-local-time, cl-log, cl-lparallel, cl-markdown, cl-md5, cl-metabang-bind, 
> cl-mssql, cl-mustache, cl-plus-ssl (>= 20190204), cl-postmodern, cl-ppcre, 
> cl-py-configparser, cl-qmynd, cl-quri, cl-simple-date, cl-split-sequence, 
> cl-sqlite, cl-trivial-backtrace, cl-trivial-utf-8, cl-unicode, cl-usocket, 
> cl-utilities, cl-uuid, cl-yason, cl-zs3, debhelper-compat (= 13), gawk, 
> help2man, libsqlite3-dev, postgresql-14-ip4r, python3-sphinx, 
> python3-sphinx-rtd-theme, sbcl (>= 1.1.13), tzdata, build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [765 B]
> Get:5 copy:/<>/apt_archive ./ Packages [834 B]
> Fetched 2562 B in 0s (202 kB/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: postgresql-14-ip4r but it is not 
> installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2022/10/23/pgloader_3.6.8-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221023=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 

Bug#1022719: fonts-texgyre-math: missing Breaks: fonts-texgyre (<< 20180621-4)

[Andreas Beckmann]

Package: fonts-texgyre-math
Version: 20180621-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts replaces-without-breaks

Hi,

during a test with piuparts and DOSE tools I noticed your package causes
removal of files that also belong to another package.
This is caused by using Replaces without corresponding Breaks.

There is a Breaks: tex-gyre (<< 20180621-4) that should probably have
targeted fonts-texgyre instead.


Andreas

Bug#1022711: subversion: "svn --non-interactive status -v svn-md5" started by emacs hangs

[Vincent Lefevre]

BTW, independently, svn should also stop going upward once a
working copy has been reached (I suppose that this led to the
issue with emacs).

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

Processed: Re: subversion: "svn --non-interactive status -v svn-md5" started by emacs hangs

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 svn tries to read a directory on a different filesystem and hangs
Bug #1022711 [subversion] subversion: "svn --non-interactive status -v svn-md5" 
started by emacs hangs
Changed Bug title to 'svn tries to read a directory on a different filesystem 
and hangs' from 'subversion: "svn --non-interactive status -v svn-md5" started 
by emacs hangs'.
> severity -1 grave
Bug #1022711 [subversion] svn tries to read a directory on a different 
filesystem and hangs
Severity set to 'grave' from 'important'
> tags -1 security
Bug #1022711 [subversion] svn tries to read a directory on a different 
filesystem and hangs
Added tag(s) security.

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

Bug#1015327: marked as done (ruby-mysql2: FTBFS: ERROR: Test "ruby3.0" failed: adduser: Warning: The home dir /nonexistent you specified can't be accessed: No such file or directory)

[Debian Bug Tracking System]

Your message dated Mon, 24 Oct 2022 09:27:43 -0300
with message-id <0ad3489b-b8f0-5665-06d1-fa64a3e98...@debian.org>
and subject line Package now builds fine with ruby 3.1
has caused the Debian Bug report #1015327,
regarding ruby-mysql2: FTBFS: ERROR: Test "ruby3.0" failed: adduser: Warning: 
The home dir /nonexistent you specified can't be accessed: 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.)


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

Hi,

We are about to start the ruby3.1 transition in unstable. While trying to
rebuild ruby-mysql2 with ruby3.1 enabled, the build failed.

This does not seem to be related to ruby3.1 though. The C code builds
just fine for ruby3.0 and ruby3.1, but the tests fail due to a bug in
theh script used to run mysql I guess?

Relevant part of the build log (hopefully):
> ┌──┐
> │ Install Rubygems integration metadata   
>  │
> └──┘
> 
> generating gemspec at 
> /<>/debian/ruby-mysql2/usr/share/rubygems-integration/3.0.0/specifications/mysql2-0.5.3.gemspec
> generating gemspec at 
> /<>/debian/ruby-mysql2/usr/share/rubygems-integration/3.1.0/specifications/mysql2-0.5.3.gemspec
> dh_installchangelogs -pruby-mysql2 /<>/CHANGELOG.md upstream
> /usr/bin/ruby3.0 /usr/bin/gem2deb-test-runner
> 
> ┌──┐
> │ Checking Rubygems dependency resolution on ruby3.0  
>  │
> └──┘
> 
> GEM_PATH=/<>/debian/ruby-mysql2/usr/share/rubygems-integration/3.0.0:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.0.0:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0
>  ruby3.0 -e gem\ \"mysql2\"
> 
> ┌──┐
> │ Run tests for ruby3.0 from debian/ruby-tests.rake   
>  │
> └──┘
> 
> RUBYLIB=/<>/debian/ruby-mysql2/usr/lib/x86_64-linux-gnu/ruby/vendor_ruby/3.0.0:/<>/debian/ruby-mysql2/usr/lib/ruby/vendor_ruby:.
>  
> GEM_PATH=/<>/debian/ruby-mysql2/usr/share/rubygems-integration/3.0.0:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.0.0:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0
>  ruby3.0 -S rake -f debian/ruby-tests.rake
> ./debian/start_mysqld_and_run.sh ruby3.0 -S rspec
> + mktemp -d
> + MYTEMP_DIR=/tmp/tmp.YafTwmGWe1
> + export MYSQL_UNIX_PORT=/tmp/tmp.YafTwmGWe1/mysql.sock
> + DO_MYSQL_USER=admin
> + DO_MYSQL_PASS=
> + DO_MYSQL_DBNAME=test
> + DO_MYSQL_DATABASE=/test
> + mysqladmin=/usr/bin/mysqladmin --user=admin 
> --socket=/tmp/tmp.YafTwmGWe1/mysql.sock
> + mysql_install_db --no-defaults --datadir=/tmp/tmp.YafTwmGWe1 --force 
> --skip-name-resolve --user=admin
> chown: cannot access '/usr/lib/mysql/plugin/auth_pam_tool_dir/auth_pam_tool': 
> Permission denied
> Couldn't set an owner to 
> '/usr/lib/mysql/plugin/auth_pam_tool_dir/auth_pam_tool'.
> It must be root, the PAM authentication plugin doesn't work otherwise..
> 
> Installing MariaDB/MySQL system tables in '/tmp/tmp.YafTwmGWe1' ...
> 2022-07-18  8:51:41 0 [Warning] InnoDB: Retry attempts for writing partial 
> data failed.
> 2022-07-18  8:51:41 0 [ERROR] InnoDB: Write to file ./ibdata1 failed at 
> offset 0, 1048576 bytes should have been written, only 0 were written. 
> Operating system error number 22. Check that your OS and file system support 
> files of this size. Check also that the disk is not full or a disk quota 
> exceeded.
> 2022-07-18  8:51:41 0 [ERROR] InnoDB: Error number 22 means 'Invalid argument'
> 2022-07-18  8:51:41 0 [ERROR] InnoDB: Could not set the file size of 
> './ibdata1'. Probably out of disk 

Processed: Fixing merging bugs

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://gitlab.freedesktop.org/drm/amd/-/issues/2216
Bug #1022097 [src:linux] linux-image-5.10.0-19-amd64: Hangs (effectively) 
during boot (after Grub)
Set Bug forwarded-to-address to 
'https://gitlab.freedesktop.org/drm/amd/-/issues/2216'.
> tag -1 patch pending upstream
Bug #1022097 [src:linux] linux-image-5.10.0-19-amd64: Hangs (effectively) 
during boot (after Grub)
Added tag(s) upstream, patch, and pending.
> merge -1 1022042
Bug #1022097 [src:linux] linux-image-5.10.0-19-amd64: Hangs (effectively) 
during boot (after Grub)
Bug #1022025 [src:linux] Can't enable amdgpu driver in 
linux-image-5.10.0-19-amd64
Bug #1022042 [src:linux] linux-image-amd64: linux-image-5.10.0-19-amd64 fails 
to boot on machines with AMD integrated graphics
Bug #1022051 [src:linux] linux-image-5.10.0-19-amd64: no boot possible
Bug #1022062 [src:linux] regression on amdgpu: drm_kms_helper "flip_done timed 
out" messages during boot and console freeze
Bug #1022070 [src:linux] Booting semi-hangs with 
'drm_atomic_helper_wait_for_flip_done' errors and alike
Bug #1022147 [src:linux] regression on amdgpu: drm_kms_helper "flip_done timed 
out" messages during boot and console freeze
Merged 1022025 1022042 1022051 1022062 1022070 1022097 1022147

-- 
1022025: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022025
1022042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022042
1022051: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022051
1022062: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022062
1022070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022070
1022097: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022097
1022147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022147
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1022097: Fixing merging bugs

[Diederik de Haas]

Control: forwarded -1 https://gitlab.freedesktop.org/drm/amd/-/issues/2216
Control: tag -1 patch pending upstream
Control: merge -1 1022042

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

Processed (with 1 error): Re: Bug#1022097: Fixed

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1022097 [src:linux] linux-image-5.10.0-19-amd64: Hangs (effectively) 
during boot (after Grub)
Severity set to 'serious' from 'important'
> merge -1 1022042
Bug #1022097 [src:linux] linux-image-5.10.0-19-amd64: Hangs (effectively) 
during boot (after Grub)
Unable to merge bugs because:
forwarded of #1022025 is 'https://gitlab.freedesktop.org/drm/amd/-/issues/2216' 
not ''
forwarded of #1022070 is 'https://gitlab.freedesktop.org/drm/amd/-/issues/2216' 
not ''
forwarded of #1022062 is 'https://gitlab.freedesktop.org/drm/amd/-/issues/2216' 
not ''
forwarded of #1022147 is 'https://gitlab.freedesktop.org/drm/amd/-/issues/2216' 
not ''
forwarded of #1022042 is 'https://gitlab.freedesktop.org/drm/amd/-/issues/2216' 
not ''
forwarded of #1022051 is 'https://gitlab.freedesktop.org/drm/amd/-/issues/2216' 
not ''
Failed to merge 1022097: Did not alter merged bugs.


-- 
1022025: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022025
1022042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022042
1022051: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022051
1022062: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022062
1022070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022070
1022097: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022097
1022147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022147
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1022474: marked as done (python-ua-parser: FTBFS: distutils.errors.DistutilsClassError: command class must subclass Command)

[Debian Bug Tracking System]

Your message dated Mon, 24 Oct 2022 12:06:23 +
with message-id 
and subject line Bug#1022474: fixed in python-ua-parser 0.16.1-2
has caused the Debian Bug report #1022474,
regarding python-ua-parser: FTBFS: distutils.errors.DistutilsClassError: 
command class  must subclass Command
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.)


-- 
1022474: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022474
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-ua-parser
Version: 0.16.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 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 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:240: python3.10 setup.py config 
> /<>/setup.py:4: DeprecationWarning: The distutils package is 
> deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 
> 632 for potential alternatives
>   from distutils import log
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning: 
> Distutils was imported before Setuptools, but importing Setuptools also 
> replaces the `distutils` module in `sys.modules`. This may lead to 
> undesirable behaviors or errors. To avoid these issues, avoid using distutils 
> directly, ensure that setuptools is installed in the traditional way (e.g. 
> not an editable install), and/or make sure that setuptools is always imported 
> before distutils.
>   warnings.warn(
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning: 
> Setuptools is replacing distutils.
>   warnings.warn("Setuptools is replacing distutils.")
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> /<>/setup.py:4: DeprecationWarning: The distutils package is 
> deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 
> 632 for potential alternatives
>   from distutils import log
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning: 
> Distutils was imported before Setuptools, but importing Setuptools also 
> replaces the `distutils` module in `sys.modules`. This may lead to 
> undesirable behaviors or errors. To avoid these issues, avoid using distutils 
> directly, ensure that setuptools is installed in the traditional way (e.g. 
> not an editable install), and/or make sure that setuptools is always imported 
> before distutils.
>   warnings.warn(
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning: 
> Setuptools is replacing distutils.
>   warnings.warn("Setuptools is replacing distutils.")
> Traceback (most recent call last):
>   File "/<>/setup.py", line 203, in 
> setup(
>   File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 87, in 
> setup
> return distutils.core.setup(**attrs)
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line 
> 172, in setup
> ok = dist.parse_command_line()
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
> 474, in parse_command_line
> args = self._parse_command_opts(parser, args)
>   File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1107, in 
> _parse_command_opts
> nargs = _Distribution._parse_command_opts(self, parser, args)
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
> 540, in _parse_command_opts
> raise DistutilsClassError(
> distutils.errors.DistutilsClassError: command class  
> must subclass Command
> E: pybuild pybuild:379: build: plugin distutils failed with: exit code=1: 
> /usr/bin/python3 setup.py build 
> dh_auto_build: error: pybuild --build -i python{version} -p 3.10 returned 
> exit code 13
> make: *** [debian/rules:7: binary] Error 25


The full build log is available from:
http://qa-logs.debian.net/2022/10/23/python-ua-parser_0.16.1-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221023=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 

Processed: Re: A way to include openscenegraph in bookworm?

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #1004634 [src:openscenegraph] openscenegraph: FTBFS with ffmpeg 5.0
Severity set to 'important' from 'serious'

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

Bug#1004634: A way to include openscenegraph in bookworm?

[Alberto Luaces]

control: severity -1 important

I agree, thanks for noting that as well.  Let's see if I do this 
correctly, I always have problems recalling the details of operating 
with cont...@bugs.debian.org.


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1022364: qutebrowser: FTBFS: dh_usrlocal: error: debian/qutebrowser/usr/local/bin/qutebrowser is not a directory

[Axel Beckert]

Hi Yannick,

Yannick Roehlly wrote:
> Isn't this linked to https://github.com/pypa/pip/issues/10978 ?

Yes, looks related. But as far as I can see, it indeed seems to be a
Debian-specific issue as some people in there already commented.

Interesting though that Fedora seems to have similar issues. :-)

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

Bug#1022364: qutebrowser: FTBFS: dh_usrlocal: error: debian/qutebrowser/usr/local/bin/qutebrowser is not a directory

[Yannick Roehlly]

Hi,

Isn't this linked to https://github.com/pypa/pip/issues/10978 ?

Yannick

Bug#1004634: A way to include openscenegraph in bookworm?

[Dr. Tobias Quathamer]

Am 24.10.22 um 12:57 schrieb Alberto Luaces:

No problem!

Yes, it was more of a philosophical issue.  That is the reason why I am 
leaving this bug report open, in case we get a patch in time or if some 
dependency really needs this plugin.


Regards,

Alberto


Yes, the bug is still not resolved -- however, IMHO it's not RC anymore, 
so the severity should be downgraded to e. g. important. What do you think?


Regards,
Tobias



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1004634: A way to include openscenegraph in bookworm?

[Alberto Luaces]

No problem!

Yes, it was more of a philosophical issue.  That is the reason why I am 
leaving this bug report open, in case we get a patch in time or if some 
dependency really needs this plugin.


Regards,

Alberto


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1022488: azure-cosmos-python: FTBFS: TypeError: dist must be a Distribution instance

[Luca Boccassi]

On Sun, 23 Oct 2022 15:38:40 +0200 Lucas Nussbaum 
wrote:
> Source: azure-cosmos-python
> Version: 3.1.1-4
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20221023 ftbfs-bookworm
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
> 
> Relevant part (hopefully):
> >  debian/rules clean
> > dh clean --with python3 --buildsystem=pybuild
> >    dh_auto_clean -O--buildsystem=pybuild
> > I: pybuild base:240: python3.10 setup.py clean 
> > /<>/setup.py:3: DeprecationWarning: The distutils
package is deprecated and slated for removal in Python 3.12. Use
setuptools or check PEP 632 for potential alternatives
> >   from distutils.core import setup
> > /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18:
UserWarning: Distutils was imported before Setuptools, but importing
Setuptools also replaces the `distutils` module in `sys.modules`. This
may lead to undesirable behaviors or errors. To avoid these issues,
avoid using distutils directly, ensure that setuptools is installed in
the traditional way (e.g. not an editable install), and/or make sure
that setuptools is always imported before distutils.
> >   warnings.warn(
> > /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33:
UserWarning: Setuptools is replacing distutils.
> >   warnings.warn("Setuptools is replacing distutils.")
> > /usr/lib/python3.10/distutils/dist.py:274: UserWarning: Unknown
distribution option: 'install_requires'
> >   warnings.warn(msg)
> > running clean
> > Traceback (most recent call last):
> >   File "/<>/setup.py", line 6, in 
> > setup(name='azure-cosmos',
> >   File "/usr/lib/python3.10/distutils/core.py", line 148, in setup
> > dist.run_commands()
> >   File "/usr/lib/python3.10/distutils/dist.py", line 966, in
run_commands
> > self.run_command(cmd)
> >   File "/usr/lib/python3.10/distutils/dist.py", line 983, in
run_command
> > cmd_obj = self.get_command_obj(command)
> >   File "/usr/lib/python3.10/distutils/dist.py", line 858, in
get_command_obj
> > cmd_obj = self.command_obj[command] = klass(self)
> >   File "/usr/lib/python3/dist-packages/setuptools/__init__.py",
line 158, in __init__
> > super().__init__(dist)
> >   File "/usr/lib/python3/dist-
packages/setuptools/_distutils/cmd.py", line 59, in __init__
> > raise TypeError("dist must be a Distribution instance")
> > TypeError: dist must be a Distribution instance
> > E: pybuild pybuild:379: clean: plugin distutils failed with: exit
code=1: python3.10 setup.py clean 
> > dh_auto_clean: error: pybuild --clean -i python{version} -p 3.10
returned exit code 13
> > make: *** [debian/rules:6: clean] Error 25
> 
> 
> The full build log is available from:
>
http://qa-logs.debian.net/2022/10/23/azure-cosmos-python_3.1.1-4_unstable.log
> 
> All bugs filed during this archive rebuild are listed at:
>
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org
> or:
>
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221023=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!
> 

This is just calling:

from distutils.core import setup
import setuptools

setup(name='azure-cosmos',
  version='3.1.1',
  description='Azure Cosmos Python SDK',
  author="Microsoft",
  author_email="askdo...@microsoft.com",
  maintainer="Microsoft",
  maintainer_email="askdo...@microsoft.com",
  url="https://github.com/Azure/azure-documentdb-python;,
  license='MIT',
  install_requires=['six >=1.6', 'requests>=2.10.0'],
  classifiers=[
'License :: OSI Approved :: MIT License',
'Intended Audience :: Developers',
'Natural Language :: English',
'Operating System :: OS Independent',
'Programming Language :: Python',
'Programming Language :: Python :: 2.7',
'Programming Language :: Python :: 3.3',
'Programming Language :: Python :: 3.4',
'Programming Language :: Python :: 3.5',
'Programming Language :: Python :: Implementation :: CPython',
'Topic :: Software Development :: Libraries :: Python Modules'
  ],
  packages=setuptools.find_packages(exclude=['test', 'test.*']))


I don't see how it can be anything else than a problem in distutils itself?

-- 
Kind regards,
Luca Boccassi


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

Bug#1004634: A way to include openscenegraph in bookworm?

[Dr. Tobias Quathamer]

Am 24.10.22 um 10:24 schrieb Alberto Luaces:

Hi, those are currently my thoughts as well.

I'm going to prepare a release like that, and we can see if any of the 
reverse dependencies is actively using this plugin; maybe some games as 
openmw are displaying movies, we will see.


Regards,

Alberto


Hi Alberto,

I've seen that you've already uploaded, great work, thanks!

Regards,
Tobias



OpenPGP_signature
Description: OpenPGP digital signature

Processed: block 1018196 with 1022681

[Debian Bug Tracking System]

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

> block 1018196 with 1022681
Bug #1018196 [src:haskell-cipher-aes] Removal notice: obsolete
1018196 was not blocked by any bugs.
1018196 was not blocking any bugs.
Added blocking bug(s) of 1018196: 1022681
> thanks
Stopping processing here.

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

Processed: block 1018197 with 1022681

[Debian Bug Tracking System]

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

> block 1018197 with 1022681
Bug #1018197 [src:haskell-cprng-aes] Removal notice: obsolete
1018197 was not blocked by any bugs.
1018197 was not blocking any bugs.
Added blocking bug(s) of 1018197: 1022681
> thanks
Stopping processing here.

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

Processed: closing 1022317

[Debian Bug Tracking System]

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

> close 1022317 1:0.1.9998svn3571+dfsg-4
Bug #1022317 [src:kbuild] kbuild: FTBFS: kbuild_version.c:61:26: error: 
expected expression before ‘)’ token
Marked as fixed in versions kbuild/1:0.1.9998svn3571+dfsg-4.
Bug #1022317 [src:kbuild] kbuild: FTBFS: kbuild_version.c:61:26: error: 
expected expression before ‘)’ token
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: haskell-clientsession build depends on haskell-cipher-aes and haskell-cprng-aes

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:haskell-cipher-aes src:haskell-cprng-aes
Bug #1022681 [src:haskell-clientsession] haskell-clientsession build depends on 
haskell-cipher-aes and haskell-cprng-aes
Added indication that 1022681 affects src:haskell-cipher-aes and 
src:haskell-cprng-aes

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

Bug#1022681: haskell-clientsession build depends on haskell-cipher-aes and haskell-cprng-aes

[Adrian Bunk]

Source: haskell-clientsession
Version: 0.9.1.2-7
Severity: serious
Control: affects -1 src:haskell-cipher-aes src:haskell-cprng-aes

haskell-clientsession build depends on haskell-cipher-aes
and haskell-cprng-aes that have "intend to remove" bugs.

Bug#1022579: firebird3.0: FTBFS for binary-independent build

[Ondřej Surý]

Source: firebird3.0
Version: 3.0.11.33637.ds4-1
Severity: serious
Tags: ftbfs
Justification: FTBFS

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear Maintainer,

https://buildd.debian.org/status/fetch.php?pkg=firebird3.0=all=3.0.11.33637.ds4-1=1666553566=0

Building the arch indep packages failed with:

make[1]: Entering directory '/<>'
dh_lintian
sed -i -e "s/TRIPLET/x86_64-linux-gnu/g" \
debian/libib-util/usr/share/lintian/overrides/libib-util
sed: can't read debian/libib-util/usr/share/lintian/overrides/libib-util: No 
such file or directory
make[1]: *** [debian/rules:177: override_dh_lintian] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:7: binary-indep] Error 2
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit 
status 2

I guess you want to fix this ASAP as it's currently blocking all rdeps on 
firebird-dev
(why does firebird-dev depend on the documentation anyway?)

Ondrej

- -- System Information:
Debian Release: 11.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'stable-debug'), (500, 'proposed-updates'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-18-amd64 (SMP w/24 CPU threads)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_IE:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEEw2Gx4wKVQ+vGJel9g3Kkd++uWcIFAmNWZ5xfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEMz
NjFCMUUzMDI5NTQzRUJDNjI1RTk3RDgzNzJBNDc3RUZBRTU5QzIACgkQg3Kkd++u
WcLWchAAmHx17RF3AzYqUlr66CVLBYOpRfgeZ0DlmPsYVDj9gwgwDPMQXbmOrzr7
fbXe02PiaW+QKGUwCd3b3fRHlFe0oENLU9mpc7fIY4Dg6nC/mJ6yzp34KZ5bUYi0
KV6yNaVSgq6QF7Zi8bOgjQ/t8yhKHCE2p7UQwk+EAUHHxlcCMMWEfn1VJlJ8HwxQ
57W9Fyigx+0/b1OnQI8gYRyCcY6blnc/r6lEJcW5N06VjYEOhOQNLbMDa1D9vvR1
7KAzu/+BkTBUUGJmTUMne2t4ZEzgC+B9XQzW7wAO916hNhrAmCtzYOlKAiy5+P+f
N2MHLjH6vGBEwDvagnYEno8/szb08aMCmX8B5JiNZzckpspTEi78q4qwKnWU06Ud
AoWBvqbDIqR3yIaPl4GNLHjnit8zW/KRCgdMmFzboKhmeE4sGW/hOxDunLri5Vw1
QvvV29CFpKqvycg8Gqp84Jx09j/3x2vgsV/B2EJfebr8ThD48ynnpw7WPIW5QBUu
C5xe+lQ+o8/+BHuhYKZASlap0YGQDQN/xv3KHM3ScRMVYdMOGMbidH+IiXaTJhFZ
2E+Mkg1eVkKYxziWgkDNabU+0j2F1ojOr19dJYli0DyiVVYB948+rF6LL3buiu0r
XzQbkFMqsRqUz1tJvwf4tGlLZdVPGmAH7209sAFhDxUaLgZlWtM=
=HkBV
-END PGP SIGNATURE-

Bug#1021658: Processed: autopkgtest regressions are RC (and this one also blocks the perl transition)

[Adrian Bunk]

On Sun, Oct 23, 2022 at 12:35:41PM +0200, Paul Gevers wrote:
> Hi Hilmar,
> 
> On 23-10-2022 12:15, Hilmar Preuße wrote:
> > Am 22.10.2022 um 10:21 teilte Debian Bug Tracking System mit:
> > the breakage is not caused by the perl upload, but due to the latest TeX
> > Live upload at the beginning of this month. Hence TL either does not
> > migrate to testing (which is good in the moment IMHO). I reported the
> > issue upstream, not sure when we get a solution.
> 
> I think both Adrian and I understood that, I *assume* he raised the severity
> because failing autopkgtest (on amd64 and arm64) are RC [1].

Yes, that's what I tried to say in the Subject.

> > I could remove the few failing tests from the test suite, but we would
> > get a degraded TL / latexml combination in testing this way.
> >
> > Can we add an override / hint to make sure perl migrates to testing?
> 
> We'll handle it somehow yes.

It seems someone already handled it or it disappeared by itself.

> > Further the autorm for latexml would need to be removed, else the new TL
> > will migrate to testing and will break an (already) installed latexml
> > package.
> 
> You can block migration of packages by creating an RC bug against it. For
> your info, if there's progress on an RC issue, the Release Team considers it
> acceptable that you regularly ping the RC bug with some update, which will
> reset the removal date counter. It goes without saying that the Release Team
> can at any moment remove any package from testing if they deem that the
> right action to solve issues regarding testing and/or migration.
> 
> > Any further ideas how to handle the situation?
> 
> We'll handle perl, you can handle TL yourself by filling an RC bug.

The autopkgtest regression in latexml already prevents the migration of TL.

The only possible action on the TL side will be after latexml is fixed 
to add Breaks in TL against unfixed versions of latexml to avoid users
(or test environments) ending up with incompatble combinations.

> Paul
>...

cu
Adrian

Bug#1022364: qutebrowser: FTBFS: dh_usrlocal: error: debian/qutebrowser/usr/local/bin/qutebrowser is not a directory

[Axel Beckert]

Hi Lucas,

Lucas Nussbaum wrote:
> > > Actually the following override in debian/rules would fix it and the
> > > resulting .deb has no debdiff to 2.5.2-1 as in unstable/testing, but
> > > I'd first like to understand what actually goes wrong instead of
> > > fixing symptoms:
> > > 
> > >   override_dh_usrlocal:
> > >   rm -rvf debian/qutebrowser/usr/local/
> > 
> > I'm quite sure the culprit lies hidden somewhere in an
> > python3-setuptools upstream release between probably 65.3.0 (seems to
> > have worked for the past 5 weeks unless Lucas' rebuilds happen more
> > seldom, in which case 59.6.0 would be the last known working version)
> > and 65.5.0 (clearly broken, installs qutebrowser and only that file
> > into /usr/bin/ _and_ /usr/local/bin/).
> 
> I attached the two previous build logs for qutebrowser (17/09 and
> 13/08). It might be useful to identify the culprit.

Yeah, already looked at them on buildd.d.o:

Downgrading python3-setuptools to 59.6.0-1.2 solves the issue as well.
But that's already no more in testing.

Currently trying to figure out with qutebrowser upstream if this is
caused by a change in setuptools or Debian's patches against
setuptools. We're currently suspecting a change in Debian's patches
against setuptools because setuptools seems to ignore --prefix=/usr
now according to a short test of mine.

And we're trying to understand if this is a bug in qutebrowser's
setup.py respectively qutebrowser's misc/Makefile or in Debian's
python3-setuptools.

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

Bug#1021859: marked as pending in pgbouncer

[Christoph Berg]

Control: tag -1 pending

Hello,

Bug #1021859 in pgbouncer 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/postgresql/pgbouncer/-/commit/af952a729f59ca41d8ccd5a24c960eca37ccdb29


Cherry-pick 04ff38b25e from upstream to fix tests. (Closes: #1021859, but needs 
4a6de748d3 in postgresql-15 as well)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1021859

Processed: Bug#1021859 marked as pending in pgbouncer

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1021859 [src:pgbouncer] pgbouncer FTBFS: test failures
Added tag(s) pending.

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

Processed: llvm-toolchain-15 fails with LLVM ERROR when using mesa

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:mesa src:lomiri-settings-components src:clutter-1.0 src:mutter 
> src:gtk4 src:mrpt src:sphinx
Bug #1022577 [src:llvm-toolchain-15] llvm-toolchain-15 fails with LLVM ERROR 
when using mesa
Added indication that 1022577 affects src:mesa, src:lomiri-settings-components, 
src:clutter-1.0, src:mutter, src:gtk4, src:mrpt, and src:sphinx
> block 1022576 by -1
Bug #1022576 [src:mesa] mesa causes FTBFS and autopkgtest regressions on 32bit 
ARM due to LLVM ERROR
1022576 was not blocked by any bugs.
1022576 was not blocking any bugs.
Added blocking bug(s) of 1022576: 1022577

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

Bug#1022577: llvm-toolchain-15 fails with LLVM ERROR when using mesa

[Adrian Bunk]

Source: llvm-toolchain-15
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: Debian X Strike Force 
Control: affects -1 src:mesa src:lomiri-settings-components src:clutter-1.0 
src:mutter src:gtk4 src:mrpt src:sphinx
Control: block 1022576 by -1

https://buildd.debian.org/status/fetch.php?pkg=mutter=armhf=43.0-3=1666029584=0

...
# Start of pipeline tests
LLVM ERROR: Cannot select: 0x1300f80: v4i32 = ARMISD::VCMPZ 0x1301c70, 
Constant:i32<2>
  0x1301c70: v4i32,ch = ARMISD::VLD1DUP<(load (s32) from %ir.212)> 0xdf9afc, 
0x131c538:1, Constant:i32<4>
0x131c538: i32,i32,ch = load<(load (s32) from %ir.209, align 8), 
> 0xdf9afc, 0x12fb7e0, Constant:i32<64>
  0x12fb7e0: i32,ch = CopyFromReg 0xdf9afc, Register:i32 %23
0x12e99c0: i32 = Register %23
  0x131a9a8: i32 = Constant<64>
0x1319fd0: i32 = Constant<4>
  0x131a2e8: i32 = Constant<2>
In function: fs_variant_partial
...


Some discussion is in
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-15/+bug/1993800

Processed: affects 1022576

[Debian Bug Tracking System]

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

> affects 1022576 src:sphinx
Bug #1022576 [src:mesa] mesa causes FTBFS and autopkgtest regressions on 32bit 
ARM due to LLVM ERROR
Added indication that 1022576 affects src:sphinx
> thanks
Stopping processing here.

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

Bug#1022440: [Debian-pan-maintainers] Bug#1022440: python-fabio: FTBFS: distutils.errors.DistutilsClassError: command class must subclass Command

[Jerome Kieffer]

Dear Lucas,

I suspect the issue is once again the "numpy.distutils" which enforces 
"setuptools<60"...
I have started to port FabIO to the meson-python builder, in a similar
way to what is done for scipy-1.9 (still not packaged for debian).
It is now close to production ready and can release a version as soon
the packaging tools are available in debian.

Best regards,

Jérôme Kieffer

On Sun, 23 Oct 2022 15:37:18 +0200
Lucas Nussbaum  wrote:

> Source: python-fabio
> Version: 0.14.0+dfsg-1
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20221023 ftbfs-bookworm
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
> 
> 
> Relevant part (hopefully):
> >  fakeroot debian/rules clean
> > dh clean --buildsystem=pybuild
> >dh_auto_clean -O--buildsystem=pybuild
> > I: pybuild base:240: python3.10 setup.py clean 
> > /<>/setup.py:49: DeprecationWarning: The distutils package is 
> > deprecated and slated for removal in Python 3.12. Use setuptools or check 
> > PEP 632 for potential alternatives
> >   from distutils.command.clean import clean as Clean
> > /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning: 
> > Distutils was imported before Setuptools, but importing Setuptools also 
> > replaces the `distutils` module in `sys.modules`. This may lead to 
> > undesirable behaviors or errors. To avoid these issues, avoid using 
> > distutils directly, ensure that setuptools is installed in the traditional 
> > way (e.g. not an editable install), and/or make sure that setuptools is 
> > always imported before distutils.
> >   warnings.warn(
> > /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning: 
> > Setuptools is replacing distutils.
> >   warnings.warn("Setuptools is replacing distutils.")
> > INFO: Disabling color, you really want to install colorlog.
> > INFO:pythran:Disabling color, you really want to install colorlog.
> > INFO:fabio.setup:Use setuptools with cython
> > INFO:fabio.setup:Use setuptools.setup
> > Traceback (most recent call last):
> >   File "/<>/setup.py", line 1118, in 
> > setup_package()
> >   File "/<>/setup.py", line 1114, in setup_package
> > setup(**setup_kwargs)
> >   File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 87, in 
> > setup
> > return distutils.core.setup(**attrs)
> >   File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line 
> > 172, in setup
> > ok = dist.parse_command_line()
> >   File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
> > 474, in parse_command_line
> > args = self._parse_command_opts(parser, args)
> >   File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1107, in 
> > _parse_command_opts
> > nargs = _Distribution._parse_command_opts(self, parser, args)
> >   File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
> > 540, in _parse_command_opts
> > raise DistutilsClassError(
> > distutils.errors.DistutilsClassError: command class  > '__main__.CleanCommand'> must subclass Command
> > E: pybuild pybuild:379: clean: plugin distutils failed with: exit code=1: 
> > python3.10 setup.py clean 
> > dh_auto_clean: error: pybuild --clean -i python{version} -p 3.10 returned 
> > exit code 13
> > make: *** [debian/rules:7: clean] Error 25  
> 
> 
> The full build log is available from:
> http://qa-logs.debian.net/2022/10/23/python-fabio_0.14.0+dfsg-1_unstable.log
> 
> All bugs filed during this archive rebuild are listed at:
> https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org
> or:
> https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221023=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.
> 
> -- 
> Debian-pan-maintainers mailing list
> debian-pan-maintain...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-pan-maintainers


-- 
Jérôme Kieffer
tel +33 476 882 445

Bug#1022576: mesa causes FTBFS and autopkgtest regressions on 32bit ARM due to LLVM ERROR

[Adrian Bunk]

Source: mesa
Version: 22.2.1-1
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: LLVM Packaging Team 
Control: affects -1 src:clutter-1.0 src:gtk4 src:mutter src:mrpt 
src:lomiri-settings-components

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

...
# Start of pipeline tests
LLVM ERROR: Cannot select: 0x1300f80: v4i32 = ARMISD::VCMPZ 0x1301c70, 
Constant:i32<2>
  0x1301c70: v4i32,ch = ARMISD::VLD1DUP<(load (s32) from %ir.212)> 0xdf9afc, 
0x131c538:1, Constant:i32<4>
0x131c538: i32,i32,ch = load<(load (s32) from %ir.209, align 8), 
> 0xdf9afc, 0x12fb7e0, Constant:i32<64>
  0x12fb7e0: i32,ch = CopyFromReg 0xdf9afc, Register:i32 %23
0x12e99c0: i32 = Register %23
  0x131a9a8: i32 = Constant<64>
0x1319fd0: i32 = Constant<4>
  0x131a2e8: i32 = Constant<2>
In function: fs_variant_partial
...


Some discussion is in
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-15/+bug/1993800

Temporarily going back to LLVM 14 might be a possible
short-term workaround (untested).

Processed: mesa causes FTBFS and autopkgtest regressions on 32bit ARM due to LLVM ERROR

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:clutter-1.0 src:gtk4 src:mutter src:mrpt 
> src:lomiri-settings-components
Bug #1022576 [src:mesa] mesa causes FTBFS and autopkgtest regressions on 32bit 
ARM due to LLVM ERROR
Added indication that 1022576 affects src:clutter-1.0, src:gtk4, src:mutter, 
src:mrpt, and src:lomiri-settings-components

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