Bug#1030206: marked as done (mir-platform-graphics-eglstream-kms is not installable on !amd64/i386)

[Debian Bug Tracking System]

Your message dated Fri, 03 Feb 2023 07:34:46 +
with message-id 
and subject line Bug#1030206: fixed in mir 2.12.0+dfsg-2
has caused the Debian Bug report #1030206,
regarding mir-platform-graphics-eglstream-kms is not installable on !amd64/i386
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.)


-- 
1030206: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030206
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mir-platform-graphics-eglstream-kms
Version: 2.12.0+dfsg-1
Severity: serious

The following packages have unmet dependencies:
 mir-platform-graphics-eglstream-kms : Depends: 
mir-platform-graphics-eglstream-kms20 but it is not installable

Due to:

Package: mir-platform-graphics-eglstream-kms
...
Depends: ..., mir-platform-graphics-eglstream-kms20, ...


Package: mir-platform-graphics-eglstream-kms20
...
Architecture: amd64 i386
--- End Message ---
--- Begin Message ---
Source: mir
Source-Version: 2.12.0+dfsg-2
Done: Mike Gabriel 

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

Debian distribution maintenance software
pp.
Mike Gabriel  (supplier of updated mir package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 02 Feb 2023 21:43:08 +0100
Source: mir
Architecture: source
Version: 2.12.0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Mir Team 
Changed-By: Mike Gabriel 
Closes: 1030206
Changes:
 mir (2.12.0+dfsg-2) unstable; urgency=medium
 .
   * debian/control:
 + Make mir-platform-graphics-eglstream-kms only available on amd64+i386
   architectures. (Closes: #1030206).
Checksums-Sha1:
 bdf47643edaf03972f51e8361bf81d508769da5f 5786 mir_2.12.0+dfsg-2.dsc
 3abc0a417dc744c1d9625a6e1ffded7ca1eb117d 37548 mir_2.12.0+dfsg-2.debian.tar.xz
 0d1a3c4c8131d4e5474b40c8742ba28072e3dc87 14234 
mir_2.12.0+dfsg-2_source.buildinfo
Checksums-Sha256:
 7081661e25aed63dec57f1e99979086b170e216e6fa1f2d3a88fd7b57c62ac42 5786 
mir_2.12.0+dfsg-2.dsc
 bca5023be85d5147535d36c881098748f61b177b9b0a9e3cca6b1358bc380dac 37548 
mir_2.12.0+dfsg-2.debian.tar.xz
 7a44ff49c94da1f449c5262bf2c5f93dc884bf8c9c4b6e4b0512f4a1d48e7ac3 14234 
mir_2.12.0+dfsg-2_source.buildinfo
Files:
 93b24e7647a1f09cfca090047d596a0c 5786 x11 optional mir_2.12.0+dfsg-2.dsc
 b015ee0621fcb5485df828d252625c07 37548 x11 optional 
mir_2.12.0+dfsg-2.debian.tar.xz
 5e19179e718fa9f71ad953430cb045af 14234 x11 optional 
mir_2.12.0+dfsg-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCAAzFiEEm/uu6GwKpf+/IgeCmvRrMCV3GzEFAmPctpUVHHN1bndlYXZl
ckBkZWJpYW4ub3JnAAoJEJr0azAldxsxBL0P/35IhLhx5oFy7Z5TeI0FE0ePTlzE
ireTqw4VYQCHiRq81lL+DVKvf3Rlb0TglRZvrU2/2a/pxcm+0o2Owz1D9PX4+Aov
RgXjkvrwRrvmmoiHsa8yKI6oyQAMbhei7qc3TJakk5cyDaa4kZ6+JJ1IDs1Ozfjx
KcXUISoxumfLTXJDDaEuE7QXHO4Ez7DiRedxQHQhkXou48qx7rBMZIdXTsg+qzHL
S8CV9W7ynuflut/LV83Mh4c3ECWNNnkRg45XjHvYEh78/ht3wEYumDGi/RxZyjk1
l3991J2meuuE3Z7CG625LP6T4qlggE8DypGcKa7csPHmnyv4wZkkQlfFV4K+HjQW
qOYUyeXXRh/cH1nre6hZUFbKJntZhnBs0lT6jT59GTLHVM1QNQjNBLfTxSrf2Qzl
NfvM4jbj8zH7Q2o9E4qXDPA2BvIay1GT+1JPgtcblC2+Bre5g6ZEUBa2p+SRtHyb
6Ab6eegl5kVtV29h7awf+20VGi9UZYbpq+kDAQE9SpOTexa0ogevqQ0p/cuhGlVt
gaxoTs4QK1aKd20i11iZmlc9YdwGjQLUPFl7CNXG9QXVPG1r4ft6VEl098U98xOl
4CTXRxeWxWWQY+wbCSHgOlAcYZ02cQmug1EGFXIlPBfjZPSPN6llvyGeOBRMSWlT
cPhmFglB3n7iOcZ7
=6MuX
-END PGP SIGNATURE End Message ---

Bug#1014644: marked as done (Depends on mplayer which isn't in testing)

[Debian Bug Tracking System]

Your message dated Fri, 03 Feb 2023 07:04:14 +
with message-id 
and subject line Bug#1014644: fixed in qwinff 0.2.1+git20201215-2
has caused the Debian Bug report #1014644,
regarding Depends on mplayer which isn't in testing
to be marked as done.

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

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


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

Package: dradio
Version: 3.8-2
Tags: sid bookworm
Severity: serious
Control: clone -1 -2 -3 -4
Control: reassign -2 qwinff 0.2.1+git20201215-1
Control: reassign -3 vdr-plugin-mp3 0.10.4-2
Control: reassign -4 videotrans 1.6.1-8

Dear maintainer,

Your package Depends on mplayer, which currently isn't in testing and 
has severe issue so is unlikely to migrate soon. Your package was 
removed from testing because of RC bugs in mplayer, but somehow 
(probably a race condition) migrated back to testing. This bug is meant 
to autoremove your package, as currently it can't be installed in a 
testing environment.


You can close the bug once your package has been removed from testing.

Paul


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: qwinff
Source-Version: 0.2.1+git20201215-2
Done: Gürkan Myczko 

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

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

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

Debian distribution maintenance software
pp.
Gürkan Myczko  (supplier of updated qwinff package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 03 Feb 2023 07:29:37 +0100
Source: qwinff
Architecture: source
Version: 0.2.1+git20201215-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Gürkan Myczko 
Closes: 1014644
Changes:
 qwinff (0.2.1+git20201215-2) unstable; urgency=medium
 .
   * Update maintainer address.
   * Bump standards version to 4.6.2.
   * d/copyright: bump year.
   * d/control: depends replace mplayer with mpv. (Closes: #1014644)
Checksums-Sha1:
 f23a0d6da795bdf5f8c081035c29dcc419c71ce5 2023 qwinff_0.2.1+git20201215-2.dsc
 e8dbae3edbc2e6156e117ef4fe45f7a2ff134a76 67032 
qwinff_0.2.1+git20201215-2.debian.tar.xz
 fc6e8b5feed9aee0316e4a982d24645eb69f5404 11759 
qwinff_0.2.1+git20201215-2_source.buildinfo
Checksums-Sha256:
 9e92adb9b05d7da7f86cb387d1300fa13c75cd1c16bf399bb88659a5135146db 2023 
qwinff_0.2.1+git20201215-2.dsc
 0cdfd001a1f9ca5cc597327f468838a6e2155eee5f6e10060456655dbc20936d 67032 
qwinff_0.2.1+git20201215-2.debian.tar.xz
 11a28c4ed6c816b3c3eb6927711a209a92026221f9fe577be246cedc4694faa2 11759 
qwinff_0.2.1+git20201215-2_source.buildinfo
Files:
 70b9f5322aea02a29bc0a184ebc5641f 2023 video optional 
qwinff_0.2.1+git20201215-2.dsc
 18140791499df5b86a0370a9f046e32a 67032 video optional 
qwinff_0.2.1+git20201215-2.debian.tar.xz
 6e5dd90e4500c3fbd3dae375ba6a7284 11759 video optional 
qwinff_0.2.1+git20201215-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEtgob82PcExn/Co6JEWhSvN91FcAFAmPcrTUACgkQEWhSvN91
FcAH5w/9HJZMIzcQSBPIfgj0/nXnOFR9eE3mZsEqoZwiBu4o+uu3/Smp55eA2K3K
7UZoq68W6jnouE5PE5QOvS9wj3xOznNo5xTyau5+8Gd22cLRJEus/fhr+AR8rvrK
+1c6d0ANwKn6sku9ovT0xl/mLNVL+0FOIcnc1dKag2BMDpEVtt3tjIyz1iCG6Dc0
3wB5TkvxzDRaNrdhcN1NmoJR2VW1wRcLlFrrvbYXm51hEQxkmkF1pZbcRg8FUXLr
BeFTuEkGGguk6Mm3jP2KCoduz7+1S8mtxchpyE+O6vOu+OCO06YF5HjMvxiwIsBN
m3sVt0ST1Knv0NhxKWHnZ0IrSE7nN7VYqLI2jnNNmpOBCEHyCZPNr1LyGZgQRO9S
+kvimAvC6ZUKwmTHLqM+lhjS4uVUlLBmqvlg7V/lcyCQjuIX/jzqB/ZreUd1MxF6
wBXsHhg+njRX4DxTJQIPx7+Ls8thnlulFa3Qv0voMgn5wwEf4v6MSVRiGk0atJdx
ybR7Dp6n2tXu+oSMFi4CtMsi/oDnYI0LVZ7vzxKYRXgcepyK/IfhwA9DzrShco7v
pPGPUg5oSuw8i+t0gz6W7uoEiml7SHtWCavBkfWT6oMt6dIZMcofL0VMijIUMg+/
72hWy8SvGj3W3qYWjhfh3nDjSw/QtrVkFZW+Uaa/+iiTLTyMiOc=
=MhaY
-END PGP SIGNATURE End Message ---

Bug#1030256: marked as done (FTBFS: test failures ArgumentError: can't find user for puppet)

[Debian Bug Tracking System]

Your message dated Fri, 03 Feb 2023 03:34:50 +
with message-id 
and subject line Bug#1030256: fixed in ruby-puppetserver-ca-cli 2.4.0-2
has caused the Debian Bug report #1030256,
regarding FTBFS: test failures ArgumentError: can't find user for puppet
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.)


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

Source: ruby-puppetserver-ca-cli
Version: 2.4.0-1
Severity: serious
Tag: ftbfs

Dear Maintainer,

ruby-puppetserver-ca-cli currently fails to build from source with test 
failures. Example:


  1) Puppetserver::Ca::Action::Enable infracrl does not print the help 
output if called correctly

 Failure/Error: FileUtils.chown(@user, @group, path)

 ArgumentError:
   can't find user for puppet
 # ./lib/puppetserver/ca/utils/file_system.rb:96:in `write_file'
 # ./lib/puppetserver/ca/utils/file_system.rb:23:in `write_file'
 # ./lib/puppetserver/ca/action/enable.rb:109:in 
`create_infra_crl_chain'

 # ./lib/puppetserver/ca/action/enable.rb:75:in `enable_infra_crl'
 # ./lib/puppetserver/ca/action/enable.rb:53:in `run'
 # ./spec/puppetserver/ca/action/enable_spec.rb:34:in `block (5 
levels) in '

 # ./spec/utils/ssl.rb:248:in `with_ca_in'
 # ./spec/puppetserver/ca/action/enable_spec.rb:28:in `block (4 
levels) in '
 # ./spec/puppetserver/ca/action/enable_spec.rb:27:in `block (3 
levels) in '


For more details see the log from reproducible builds 
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ruby-puppetserver-ca-cli.html

(I have also verified the issue with pbuilder on my local Sid system)

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

Kernel: Linux 6.0.0-6-amd64 (SMP w/3 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en

Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled


--
mvh / best regards
Hans Joachim Desserud
http://desserud.org
--- End Message ---
--- Begin Message ---
Source: ruby-puppetserver-ca-cli
Source-Version: 2.4.0-2
Done: Jérôme Charaoui 

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

Debian distribution maintenance software
pp.
Jérôme Charaoui  (supplier of updated 
ruby-puppetserver-ca-cli package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 02 Feb 2023 21:16:24 -0500
Source: ruby-puppetserver-ca-cli
Architecture: source
Version: 2.4.0-2
Distribution: unstable
Urgency: medium
Maintainer: Puppet Package Maintainers 

Changed-By: Jérôme Charaoui 
Closes: 1030256
Changes:
 ruby-puppetserver-ca-cli (2.4.0-2) unstable; urgency=medium
 .
   * d/control: add puppet-agent to Build-Deps (Closes: #1030256)
Checksums-Sha1:
 063b9a49801962d05d2b7084fe5280858b0e90a3 1669 
ruby-puppetserver-ca-cli_2.4.0-2.dsc
 df66a92849151de89db068447201b2860d366c34 4972 
ruby-puppetserver-ca-cli_2.4.0-2.debian.tar.xz
 c4787cce1d01c4d22db5373665dbee6dcd9a361b 9303 
ruby-puppetserver-ca-cli_2.4.0-2_amd64.buildinfo
Checksums-Sha256:
 602e95856688edbdb1ce0fe10740cc5d99560c7f518257e3c69ead25a24ca9b9 1669 
ruby-puppetserver-ca-cli_2.4.0-2.dsc
 e71f91d4bdb96136930a56be5968455f1a0bb65fe9e1c809096b689103dc2b00 4972 
ruby-puppetserver-ca-cli_2.4.0-2.debian.tar.xz
 c6bdfef6479d23a76ccbd90be856f010fc472d813e2d5bb472006cda0b50250f 9303 
ruby-puppetserver-ca-cli_2.4.0-2_amd64.buildinfo
Files:
 c90a6be688becbdfb375e987458575b8 1669 ruby optional 
ruby-puppetserver-ca-cli_2.4.0-2.dsc
 512accfde53cb6737f2e8a9b00dedee8 4972 ruby optional 
ruby-puppetserver-ca-cli_2.4.0-2.debian.tar.xz
 a2a317fb1bc3fb4fed2eae26c2a10922 9303 ruby optional 
ruby-puppetserver-ca-cli_2.4.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYIAB0WIQTAq04Rv2xblqv/eu5pxS9ljpiFQgUCY9x9jQAKCRBpxS9ljpiF
QkUuAQDT3FRa1dQIieSMYwhvl5MUXX78oOI0g5UjE6lkTH6CvwD8DKZa/m/f6COt

Bug#1028345: python3-sage: sagemath uninstallable due to python3-sage issues

[Alexandre Lymberopoulos]

Package: python3-sage
Version: 9.5-4+b3
Followup-For: Bug #1028345

Dear Maintainer,

Just confirming the bug remains and it related to #1025874, posted by myself on 
Dec. 10th 2022.

Best, Alexandre

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

Kernel: Linux 6.1.0-2-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages python3-sage depends on:
ii  bc1.07.1-3+b1
ii  binutils  2.40-2
ii  bzip2 1.0.8-5+b1
ii  ca-certificates   20211016
pn  cliquer   
ii  cmake 3.25.1-1
ii  curl  7.87.0-2
pn  cython3   
pn  ecl   
pn  eclib-tools   
pn  fflas-ffpack  
pn  flintqs   
pn  gap-atlasrep  
pn  gap-dev   
pn  gap-online-help   
pn  gap-primgrp   
pn  gap-smallgrp  
pn  gap-table-of-marks
pn  gap-transgrp  
pn  gfan  
ii  gfortran  4:12.2.0-3
pn  glpk-utils
pn  gmp-ecm   
pn  jmol  
pn  lcalc 
ii  libatlas3-base [libblas.so.3] 3.10.3-13
pn  libatomic-ops-dev 
ii  libblas3 [libblas.so.3]   3.11.0-2
ii  libboost-dev  1.74.0.3
pn  libbraiding-dev   
pn  libbraiding0  
pn  libbrial-dev  
pn  libbrial-groebner-dev 
pn  libbrial-groebner3
pn  libbrial3 
ii  libbz2-dev1.0.8-5+b1
ii  libc6 2.36-8
pn  libcdd-dev
pn  libcdd-tools  
pn  libcliquer-dev
pn  libcliquer1   
pn  libcurl4-openssl-dev  
pn  libec-dev 
pn  libec10   
pn  libecl21.2
pn  libecm-dev
pn  libecm1   
ii  libffi-dev3.4.4-1
pn  libflint-arb-dev  
pn  libflint-arb2 
pn  libflint-dev  
pn  libflint17
ii  libfreetype-dev [libfreetype6-dev]2.12.1+dfsg-4
ii  libfreetype6-dev  2.12.1+dfsg-4
pn  libgap-dev
pn  libgap7   
pn  libgc-dev 
ii  libgcc-s1 12.2.0-14
pn  libgd-dev 
ii  libgd32.3.3-7+b1
pn  libgf2x-dev   
pn  libgiac-dev   
pn  libgiac0  
pn  libgivaro-dev 
pn  libgivaro9
pn  libglpk-dev   
ii  libglpk40 5.0-1
pn  libgmp-dev
ii  libgmp10  2:6.2.1+dfsg1-1.1
pn  libgmpxx4ldbl 
pn  libgsl-dev
ii  libgsl27  2.7.1+dfsg-3+b1
pn  libhomfly-dev 
pn  libhomfly0
pn  libiml-dev
pn  libiml0   

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

[Debian Bug Tracking System]

Your message dated Fri, 03 Feb 2023 01:35:12 +
with message-id 
and subject line Bug#1026747: fixed in python-pook 1.1.1-1
has caused the Debian Bug report #1026747,
regarding python-pook: FTBFS: dh_auto_test: error: pybuild --test --test-pytest 
-i python{version} -p "3.11 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.)


-- 
1026747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026747
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pook
Version: 1.0.2-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 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 '/<>'
> http_proxy= dh_auto_test
> I: pybuild pybuild:307: cp -r /<>/examples 
> /<>/.pybuild/cpython3_3.11_pook/build
> I: pybuild base:240: cd /<>/.pybuild/cpython3_3.11_pook/build; 
> python3.11 -m pytest tests
> = test session starts 
> ==
> platform linux -- Python 3.11.1, pytest-7.2.0, pluggy-1.0.0+repack
> rootdir: /<>
> plugins: cov-4.0.0
> collected 12 items / 7 errors
> 
>  ERRORS 
> 
> _ ERROR collecting 
> .pybuild/cpython3_3.11_pook/build/tests/integration/pook_requests_test.py _
> tests/integration/pook_requests_test.py:3: in 
> import pook
> pook/__init__.py:1: in 
> from .api import *  # noqa
> pook/api.py:6: in 
> from .engine import Engine
> pook/engine.py:5: in 
> from .mock_engine import MockEngine
> pook/mock_engine.py:1: in 
> from .interceptors import interceptors
> pook/interceptors/__init__.py:25: in 
> from .aiohttp import AIOHTTPInterceptor
> pook/interceptors/aiohttp.py:42: in 
> class SimpleContent(EmptyStreamReader):
> pook/interceptors/aiohttp.py:47: in SimpleContent
> @asyncio.coroutine
> E   AttributeError: module 'asyncio' has no attribute 'coroutine'
> __ ERROR collecting .pybuild/cpython3_3.11_pook/build/tests/unit/api_test.py 
> ___
> tests/unit/api_test.py:4: in 
> from pook import api
> pook/__init__.py:1: in 
> from .api import *  # noqa
> pook/api.py:6: in 
> from .engine import Engine
> pook/engine.py:5: in 
> from .mock_engine import MockEngine
> pook/mock_engine.py:1: in 
> from .interceptors import interceptors
> pook/interceptors/__init__.py:25: in 
> from .aiohttp import AIOHTTPInterceptor
> pook/interceptors/aiohttp.py:42: in 
> class SimpleContent(EmptyStreamReader):
> pook/interceptors/aiohttp.py:47: in SimpleContent
> @asyncio.coroutine
> E   AttributeError: module 'asyncio' has no attribute 'coroutine'
> _ ERROR collecting 
> .pybuild/cpython3_3.11_pook/build/tests/unit/engine_test.py _
> tests/unit/engine_test.py:3: in 
> from pook import Engine
> pook/__init__.py:1: in 
> from .api import *  # noqa
> pook/api.py:6: in 
> from .engine import Engine
> pook/engine.py:5: in 
> from .mock_engine import MockEngine
> pook/mock_engine.py:1: in 
> from .interceptors import interceptors
> pook/interceptors/__init__.py:25: in 
> from .aiohttp import AIOHTTPInterceptor
> pook/interceptors/aiohttp.py:42: in 
> class SimpleContent(EmptyStreamReader):
> pook/interceptors/aiohttp.py:47: in SimpleContent
> @asyncio.coroutine
> E   AttributeError: module 'asyncio' has no attribute 'coroutine'
> _ ERROR collecting 
> .pybuild/cpython3_3.11_pook/build/tests/unit/exceptions_test.py _
> tests/unit/exceptions_test.py:3: in 
> from pook import exceptions as ex
> pook/__init__.py:1: in 
> from .api import *  # noqa
> pook/api.py:6: in 
> from .engine import Engine
> pook/engine.py:5: in 
> from .mock_engine import MockEngine
> pook/mock_engine.py:1: in 
> from .interceptors import interceptors
> pook/interceptors/__init__.py:25: in 
> from .aiohttp import AIOHTTPInterceptor
> pook/interceptors/aiohttp.py:42: in 
> class SimpleContent(EmptyStreamReader):
> pook/interceptors/aiohttp.py:47: in SimpleContent
> @asyncio.coroutine
> E   AttributeError: module 'asyncio' has no attribute 'coroutine'
> _ ERROR collecting 
> .pybuild/cpython3_3.11_pook/build/tests/unit/mock_engine_test.py _
> tests/unit/mock_engine_test.py:4: in 
> from pook import MockEngine, Engine
> pook/__init__.py:1: in 
> from .api import *  # noqa
> pook/api.py:6: in 
> from .engine import Engine
> pook/engine.py:5: in 
> from .mock_engine import MockEngine
> 

Bug#1020264: marked as done (polyml FTBFS with glibc 2.34)

[Debian Bug Tracking System]

Your message dated Fri, 03 Feb 2023 01:04:24 +
with message-id 
and subject line Bug#1020264: fixed in polyml 5.7.1-5
has caused the Debian Bug report #1020264,
regarding polyml FTBFS with glibc 2.34
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.)


-- 
1020264: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020264
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: polyml
Version: 5.7.1-4
Severity: serious
Tags: ftbfs bookworm sid experimental

https://buildd.debian.org/status/logs.php?pkg=polyml=5.7.1-4%2Bb2

...
In file included from /usr/include/pthread.h:33,
 from locking.h:44,
 from processes.h:38,
 from sighandler.cpp:103:
sighandler.cpp:561:6: error: missing binary operator before token "("
  561 | #if (PTHREAD_STACK_MIN < 4096)
  |  ^
...
--- End Message ---
--- Begin Message ---
Source: polyml
Source-Version: 5.7.1-5
Done: Jessica Clarke 

We believe that the bug you reported is fixed in the latest version of
polyml, 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.
Jessica Clarke  (supplier of updated polyml package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 03 Feb 2023 00:25:28 +
Source: polyml
Architecture: source
Version: 5.7.1-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Jessica Clarke 
Closes: 1007974 1020264
Changes:
 polyml (5.7.1-5) unstable; urgency=medium
 .
   * glibc-2.34-PTHREAD_STACK_MIN.patch: New patch to fix build with glibc 2.34
 (Closes: #1020264)
   * d/rules: Silence textrel warnings during the build
   * polyc-notext.patch: New patch to silence textrel warnings using polyc
 (Closes: #1007974)
Checksums-Sha1:
 5caa211b26c546467d941c0e1656d05af21da441 2119 polyml_5.7.1-5.dsc
 cbc4e97ab98a9f8a19dd285fe9e93d493c898b4d 22388 polyml_5.7.1-5.debian.tar.xz
 925ed62490844fe150c234597b6eeb044b345eff 7418 polyml_5.7.1-5_arm64.buildinfo
Checksums-Sha256:
 d3fa0c24e27f020ae96aca32de6046751e82334011461adc50e20e8e9b6732d2 2119 
polyml_5.7.1-5.dsc
 38a7a00ed9c849846576e399a6f11692af7c200b6d3d5d20958c385369453c48 22388 
polyml_5.7.1-5.debian.tar.xz
 e8743ed93cc72de30dfd2507d8a55c2539e76c80756cb681daee31c230be6737 7418 
polyml_5.7.1-5_arm64.buildinfo
Files:
 14040a0f593c2cb17961fb99bbfe7a76 2119 interpreters optional polyml_5.7.1-5.dsc
 9f8424c1b7649e09496c3d389c3ae4ae 22388 interpreters optional 
polyml_5.7.1-5.debian.tar.xz
 dd2d6ed65108c9899cf39b4d9d22b68c 7418 interpreters optional 
polyml_5.7.1-5_arm64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEj1g0K+q+HvQ3lVH7sZN3DBhqHH0FAmPcV6kACgkQsZN3DBhq
HH0DUA/+O2KylQ3FYhtzsSvRf4UMuXDqZhc/mKuZnRbAQsAaHAwluQcGnwDQooFB
qez7J/B8kFD2yRD4pffWNuoQJqSBzUxqXRumysVAWlR6brj5h4sKIOBCmkRS708H
nx1XeRnCmVMjTfpfJlK/i8ZJleeA32rBRfJ8ku8q3MMZjNT39YA5QYZDcduQMh4f
HDEIKe75YFt0Hd80+lXJQjbVO/LWBKVFria3PoPHEdFwrmanN92/0H831Z87ILzF
ACjW1WNPEpJGtyR+J5rXCArScAVGi2P0K9BqJMqaa05pSCcfwHxUxdUoFLMBapDp
2ZIKCc8RWA7mc1XyAgVCykKB3twA+CzV4S+OLBPqGPm/1V968HEfo+tE9DAcd+7z
VM/SR012RficOAcIW/DskjTBLLjPrXNhcE2E5S5RNXkBkk7+Y5rOVUTtqD9//7hE
czGp76QHUU2Ylz3i/mirpXFlF83xFF5Azrdvv9Ea1uFOu96d5mapCtY02ZEOeQ6Y
SxKg44FtzzNcCei/RSNgAtIqS256nl2rvnxdtOA6NqDWUfLbLZoOC4CbtljsytuP
ujrJsHHhS1p6OkF1NLklGI+4OH6h3YYwHy+Df83r+LEttJMMRHBzPDE0VuN7XL7Q
UVo65iM41zZfu+LYtZeK3xzfOyIR2OYhF3Myf+W8mnEsV2NdgRk=
=U8v9
-END PGP SIGNATURE End Message ---

Bug#1007974: marked as done (polyml: autopkgtest regression on amd64: relocation in read-only section `.text')

[Debian Bug Tracking System]

Your message dated Fri, 03 Feb 2023 01:04:24 +
with message-id 
and subject line Bug#1007974: fixed in polyml 5.7.1-5
has caused the Debian Bug report #1007974,
regarding polyml: autopkgtest regression on amd64: relocation in read-only 
section `.text'
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.)


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

Source: polyml
Version: 5.7.1-4
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

Your package has an autopkgtest, great. However, somewhere between 05 
July 2021 and 12 July 2021 it regressed in testing on amd64 [1]


I copied some of the output of a recent failure at the bottom of this 
report. The test passes, but ld prints a warning to stderr. By default 
output to sdterr is considered a failure by autopkgtest unless the 
allow-stderr restriction is set in d/t/control. Preferably you fix the 
issue, but the allow-stderr is a valid alternative if the warning is 
harmless.


Paul

[1] https://ci.debian.net/packages/p/polyml/testing/amd64/

https://ci.debian.net/data/autopkgtest/testing/amd64/p/polyml/20060752/log.gz

autopkgtest [06:15:06]: test upstream-polyc: [---
/usr/bin/ld: /tmp/polyobj.1608.o: warning: relocation in read-only 
section `.text'

/usr/bin/ld: warning: creating DT_TEXTREL in a PIE
Test106.ML => Passed


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: polyml
Source-Version: 5.7.1-5
Done: Jessica Clarke 

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

Debian distribution maintenance software
pp.
Jessica Clarke  (supplier of updated polyml package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 03 Feb 2023 00:25:28 +
Source: polyml
Architecture: source
Version: 5.7.1-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Jessica Clarke 
Closes: 1007974 1020264
Changes:
 polyml (5.7.1-5) unstable; urgency=medium
 .
   * glibc-2.34-PTHREAD_STACK_MIN.patch: New patch to fix build with glibc 2.34
 (Closes: #1020264)
   * d/rules: Silence textrel warnings during the build
   * polyc-notext.patch: New patch to silence textrel warnings using polyc
 (Closes: #1007974)
Checksums-Sha1:
 5caa211b26c546467d941c0e1656d05af21da441 2119 polyml_5.7.1-5.dsc
 cbc4e97ab98a9f8a19dd285fe9e93d493c898b4d 22388 polyml_5.7.1-5.debian.tar.xz
 925ed62490844fe150c234597b6eeb044b345eff 7418 polyml_5.7.1-5_arm64.buildinfo
Checksums-Sha256:
 d3fa0c24e27f020ae96aca32de6046751e82334011461adc50e20e8e9b6732d2 2119 
polyml_5.7.1-5.dsc
 38a7a00ed9c849846576e399a6f11692af7c200b6d3d5d20958c385369453c48 22388 
polyml_5.7.1-5.debian.tar.xz
 e8743ed93cc72de30dfd2507d8a55c2539e76c80756cb681daee31c230be6737 7418 
polyml_5.7.1-5_arm64.buildinfo
Files:
 14040a0f593c2cb17961fb99bbfe7a76 2119 interpreters optional polyml_5.7.1-5.dsc
 9f8424c1b7649e09496c3d389c3ae4ae 22388 interpreters optional 
polyml_5.7.1-5.debian.tar.xz
 dd2d6ed65108c9899cf39b4d9d22b68c 7418 interpreters optional 
polyml_5.7.1-5_arm64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEj1g0K+q+HvQ3lVH7sZN3DBhqHH0FAmPcV6kACgkQsZN3DBhq
HH0DUA/+O2KylQ3FYhtzsSvRf4UMuXDqZhc/mKuZnRbAQsAaHAwluQcGnwDQooFB
qez7J/B8kFD2yRD4pffWNuoQJqSBzUxqXRumysVAWlR6brj5h4sKIOBCmkRS708H
nx1XeRnCmVMjTfpfJlK/i8ZJleeA32rBRfJ8ku8q3MMZjNT39YA5QYZDcduQMh4f
HDEIKe75YFt0Hd80+lXJQjbVO/LWBKVFria3PoPHEdFwrmanN92/0H831Z87ILzF
ACjW1WNPEpJGtyR+J5rXCArScAVGi2P0K9BqJMqaa05pSCcfwHxUxdUoFLMBapDp
2ZIKCc8RWA7mc1XyAgVCykKB3twA+CzV4S+OLBPqGPm/1V968HEfo+tE9DAcd+7z
VM/SR012RficOAcIW/DskjTBLLjPrXNhcE2E5S5RNXkBkk7+Y5rOVUTtqD9//7hE
czGp76QHUU2Ylz3i/mirpXFlF83xFF5Azrdvv9Ea1uFOu96d5mapCtY02ZEOeQ6Y
SxKg44FtzzNcCei/RSNgAtIqS256nl2rvnxdtOA6NqDWUfLbLZoOC4CbtljsytuP
ujrJsHHhS1p6OkF1NLklGI+4OH6h3YYwHy+Df83r+LEttJMMRHBzPDE0VuN7XL7Q
UVo65iM41zZfu+LYtZeK3xzfOyIR2OYhF3Myf+W8mnEsV2NdgRk=
=U8v9
-END PGP SIGNATURE End Message ---

Bug#1030256: FTBFS: test failures ArgumentError: can't find user for puppet

[Vagrant Cascadian]

On 2023-02-02, Vagrant Cascadian wrote:
> On 2023-02-01, Jérôme Charaoui wrote:
>> Perhaps an alternative would be to add "puppet-agent" as a build 
>> dependency, because that package will create a "puppet" user in the 
>> environment.

And for completeness, this also worked for me:

  sbuild --add-depends puppet-agent ...

live well,
  vagrant


signature.asc
Description: PGP signature

Bug#1030256: FTBFS: test failures ArgumentError: can't find user for puppet

[Vagrant Cascadian]

On 2023-02-01, Jérôme Charaoui wrote:
> I don't know how common that is in build environments, but it's not 
> something that I have or think I should have in my build (sbuild) or 
> test (autopkgtest) environments.

I was able to reproduce the issue with sbuild.

This appears to be because sbuild copies the host's /etc/passwd and
/etc/group into the chroot when it builds... and presumably the buildd
environment does this as well (and all DSA machines have the puppet user
available?)... and so the puppet user is in fact available in those
cases, but not others...

I was able to workaround the issue with:

  sbuild --chroot-setup-commands='adduser --gecos ,,, --disabled-password 
puppet' ...

Is there an option in sbuild to not copy the passwd/group information
into the chroot? What are the implications of that?


> Is there some flag we could use to tell reproducible-builds to build 
> this package as a regular user instead of root?

It typically builds as two different users, pbuilder1 and pbuilder2, not
as root.


> If not I might have to patch the test suite to work around some of the 
> logic in there, which I'm not too excited about.
>
> Perhaps an alternative would be to add "puppet-agent" as a build 
> dependency, because that package will create a "puppet" user in the 
> environment.

That seems like a viable option, though obviously a bit ugly if that
package does a bunch of other things or has many other
dependencies. Would it make sense to have a package that just creates a
user and nothing else?


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#1030208: marked as done (statsmodels: FTBFS with scipy 1.10 on 32-bit: int64 -> int32 cast)

[Debian Bug Tracking System]

Your message dated Thu, 02 Feb 2023 23:06:42 +
with message-id 
and subject line Bug#1030208: fixed in statsmodels 0.13.5+dfsg-5
has caused the Debian Bug report #1030208,
regarding statsmodels: FTBFS with scipy 1.10 on 32-bit: int64 -> int32 cast
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.)


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

Package: python3-statsmodels
Version: 0.13.5+dfsg-4
Severity: serious

Since scipy 1.10, some statsmodels tests fail on 32-bit with a message 
that int64 -> int32 casting is unsafe.  I haven't yet had time to 
investigate further.
--- End Message ---
--- Begin Message ---
Source: statsmodels
Source-Version: 0.13.5+dfsg-5
Done: Rebecca N. Palmer 

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

Debian distribution maintenance software
pp.
Rebecca N. Palmer  (supplier of updated statsmodels 
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: Wed, 01 Feb 2023 21:31:58 +
Source: statsmodels
Architecture: source
Version: 0.13.5+dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Rebecca N. Palmer 
Closes: 1030208
Changes:
 statsmodels (0.13.5+dfsg-5) unstable; urgency=medium
 .
   * Tests: don't crash on 32-bit systems.  (Closes: #1030208)
Checksums-Sha1:
 dee9ab847f582ed19bae75b2387e64d91fc090a4 3664 statsmodels_0.13.5+dfsg-5.dsc
 76f3268ce68fa4d8d2e682b06f7386a1b5b94791 32796 
statsmodels_0.13.5+dfsg-5.debian.tar.xz
 30c26cd599679a155067dc3232f7c36584d083d9 6366 
statsmodels_0.13.5+dfsg-5_source.buildinfo
Checksums-Sha256:
 3b447bb99c8a746f91954b794c9d14fbf34c6c4bd5ac9cd270925975ece34844 3664 
statsmodels_0.13.5+dfsg-5.dsc
 aadbe59803f9ea75da2694b549054b0630b34ada70bdd737d0057ef8887a8525 32796 
statsmodels_0.13.5+dfsg-5.debian.tar.xz
 1064af7a9417acaba9fd20a3386247f4b2969913ae1e67a061b81ec8ead22c8a 6366 
statsmodels_0.13.5+dfsg-5_source.buildinfo
Files:
 851dbb9ea21e7ad184bf0592d6a87019 3664 python optional 
statsmodels_0.13.5+dfsg-5.dsc
 413161ecace2cc5113ad88242651b8fc 32796 python optional 
statsmodels_0.13.5+dfsg-5.debian.tar.xz
 fef5be5da61b9cbc1fa7fd628f7e59e5 6366 python optional 
statsmodels_0.13.5+dfsg-5_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJMBAEBCgA2FiEEZ8sxEAXE7b4yF1MI3uUNDVZ+omYFAmPcNuYYHHJlYmVjY2Ff
cGFsbWVyQHpvaG8uY29tAAoJEN7lDQ1WfqJm8PQP/iXFTAo/stodol2cNQh80rGw
skLsLwbN1W7ZSOS8Bdcygw62KulvZR1jrM5svG5MYIWi3M6O2bVp3tjRdAzQXVJ7
AV5FM21rGiAN8dIgsf5II+EeFd83kd0w6TZk3cdnttK6niihMPOGI3IYsqz6cPxe
Ckx9nRr29OeE0VchAmzp7HmFXDrlwdKdevZ4hg77QT2YkE6rPS1rRyRIw0VrBT+D
qk4WdQWTIjFsq+cgiUT0RVlzsOvjkUPs6H+njuqsOasjaQyxHCbYQNnm4Pjjp426
A5UxCKRx5JULQfqyoY0ozv9DAKaqKGMjF3p85mNU1SXoR90plMPXknyQ88RQ91go
AOpfbZJqeMuEZSbneeIQuaeu3deMmPCEfpCbbaePDiN9lAOAHtb3E04a4RbkcrOx
wrUDNd5WXnlosC/Fv4fo/OWgndmP8XBLJNASkQnfZNhpVaYEODBiD2ogyahke7zK
cHOvD5QVXwelbmXovWlsCcyPJhlA6XsQFlz4Ob057sX36kyJ6T/4gbvZAC0pM2Ni
zpclpU2ZzEQQyGap7aFgWszvXbZ+t/+0WDak7xaiatDck6QFa3oujKRwFmrCEJj6
bcdDE4vhOO0vLgeLmaB80vRPhFTwvPeg0e9IZF6M8MIjpgcwRl7Vq/vNIVk1QZ4V
bms/KkpwbwTIp3Z9iekm
=IVg3
-END PGP SIGNATURE End Message ---

Bug#1030221: marked as done (statsmodels: 32 bit arches fail tests using int64)

[Debian Bug Tracking System]

Your message dated Thu, 02 Feb 2023 23:06:42 +
with message-id 
and subject line Bug#1030208: fixed in statsmodels 0.13.5+dfsg-5
has caused the Debian Bug report #1030208,
regarding statsmodels: 32 bit arches fail tests using int64
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.)


-- 
1030208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030208
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: statsmodels
Version: 0.13.5+dfsg-4
Severity: serious
Justification: debci

scipy 1.10 is triggering a problem with tests using int64 on 32 bit
arches (armhf, i386, armel)

Affected tests are in test_discrete.py:
TestDiscretizedGamma.test_basic
TestDiscretizedExponential::test_basic
TestDiscretizedLomax::test_basic
TestDiscretizedBurr12::test_basic

with the same error message

E   TypeError: Cannot cast array data from dtype('int64') to dtype('int32') 
according to the rule 'safe'


Some 32-bit dtype issues were raised upstream at 
https://github.com/statsmodels/statsmodels/issues/7736
but that doesn't seem to be the same problem.
--- End Message ---
--- Begin Message ---
Source: statsmodels
Source-Version: 0.13.5+dfsg-5
Done: Rebecca N. Palmer 

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

Debian distribution maintenance software
pp.
Rebecca N. Palmer  (supplier of updated statsmodels 
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: Wed, 01 Feb 2023 21:31:58 +
Source: statsmodels
Architecture: source
Version: 0.13.5+dfsg-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Rebecca N. Palmer 
Closes: 1030208
Changes:
 statsmodels (0.13.5+dfsg-5) unstable; urgency=medium
 .
   * Tests: don't crash on 32-bit systems.  (Closes: #1030208)
Checksums-Sha1:
 dee9ab847f582ed19bae75b2387e64d91fc090a4 3664 statsmodels_0.13.5+dfsg-5.dsc
 76f3268ce68fa4d8d2e682b06f7386a1b5b94791 32796 
statsmodels_0.13.5+dfsg-5.debian.tar.xz
 30c26cd599679a155067dc3232f7c36584d083d9 6366 
statsmodels_0.13.5+dfsg-5_source.buildinfo
Checksums-Sha256:
 3b447bb99c8a746f91954b794c9d14fbf34c6c4bd5ac9cd270925975ece34844 3664 
statsmodels_0.13.5+dfsg-5.dsc
 aadbe59803f9ea75da2694b549054b0630b34ada70bdd737d0057ef8887a8525 32796 
statsmodels_0.13.5+dfsg-5.debian.tar.xz
 1064af7a9417acaba9fd20a3386247f4b2969913ae1e67a061b81ec8ead22c8a 6366 
statsmodels_0.13.5+dfsg-5_source.buildinfo
Files:
 851dbb9ea21e7ad184bf0592d6a87019 3664 python optional 
statsmodels_0.13.5+dfsg-5.dsc
 413161ecace2cc5113ad88242651b8fc 32796 python optional 
statsmodels_0.13.5+dfsg-5.debian.tar.xz
 fef5be5da61b9cbc1fa7fd628f7e59e5 6366 python optional 
statsmodels_0.13.5+dfsg-5_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJMBAEBCgA2FiEEZ8sxEAXE7b4yF1MI3uUNDVZ+omYFAmPcNuYYHHJlYmVjY2Ff
cGFsbWVyQHpvaG8uY29tAAoJEN7lDQ1WfqJm8PQP/iXFTAo/stodol2cNQh80rGw
skLsLwbN1W7ZSOS8Bdcygw62KulvZR1jrM5svG5MYIWi3M6O2bVp3tjRdAzQXVJ7
AV5FM21rGiAN8dIgsf5II+EeFd83kd0w6TZk3cdnttK6niihMPOGI3IYsqz6cPxe
Ckx9nRr29OeE0VchAmzp7HmFXDrlwdKdevZ4hg77QT2YkE6rPS1rRyRIw0VrBT+D
qk4WdQWTIjFsq+cgiUT0RVlzsOvjkUPs6H+njuqsOasjaQyxHCbYQNnm4Pjjp426
A5UxCKRx5JULQfqyoY0ozv9DAKaqKGMjF3p85mNU1SXoR90plMPXknyQ88RQ91go
AOpfbZJqeMuEZSbneeIQuaeu3deMmPCEfpCbbaePDiN9lAOAHtb3E04a4RbkcrOx
wrUDNd5WXnlosC/Fv4fo/OWgndmP8XBLJNASkQnfZNhpVaYEODBiD2ogyahke7zK
cHOvD5QVXwelbmXovWlsCcyPJhlA6XsQFlz4Ob057sX36kyJ6T/4gbvZAC0pM2Ni
zpclpU2ZzEQQyGap7aFgWszvXbZ+t/+0WDak7xaiatDck6QFa3oujKRwFmrCEJj6
bcdDE4vhOO0vLgeLmaB80vRPhFTwvPeg0e9IZF6M8MIjpgcwRl7Vq/vNIVk1QZ4V
bms/KkpwbwTIp3Z9iekm
=IVg3
-END PGP SIGNATURE End Message ---

Bug#1030210: marked as done (statsmodels FTBFS on 32bit)

[Debian Bug Tracking System]

Your message dated Thu, 02 Feb 2023 23:06:42 +
with message-id 
and subject line Bug#1030208: fixed in statsmodels 0.13.5+dfsg-5
has caused the Debian Bug report #1030208,
regarding statsmodels FTBFS on 32bit
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.)


-- 
1030208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030208
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: statsmodels
Version: 0.13.5+dfsg-4
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=statsmodels=0.13.5%2Bdfsg-4%2Bb1

...
=== FAILURES ===
___ TestDiscretizedGamma.test_basic 

self = 

def test_basic(self):
d_offset = self.d_offset
ddistr = self.ddistr
paramg = self.paramg
paramd = self.paramd
shapes = self.shapes
start_params = self.start_params

np.random.seed(987146)

dp = DiscretizedCount(ddistr, d_offset)
assert dp.shapes == shapes
xi = np.arange(5)
p = dp._pmf(xi, *paramd)

cdf1 = ddistr.cdf(xi, *paramg)
p1 = np.diff(cdf1)
assert_allclose(p[: len(p1)], p1, rtol=1e-13)
cdf = dp._cdf(xi, *paramd)
assert_allclose(cdf[: len(cdf1) - 1], cdf1[1:], rtol=1e-13)

# check that scipy dispatch methods work
p2 = dp.pmf(xi, *paramd)
assert_allclose(p2, p, rtol=1e-13)
cdf2 = dp.cdf(xi, *paramd)
assert_allclose(cdf2, cdf, rtol=1e-13)
sf = dp.sf(xi, *paramd)
assert_allclose(sf, 1 - cdf, rtol=1e-13)

nobs = 2000

xx = dp.rvs(*paramd, size=nobs)  # , random_state=987146)
# check that we go a non-trivial rvs
assert len(xx) == nobs
assert xx.var() > 0.001
mod = DiscretizedModel(xx, distr=dp)
res = mod.fit(start_params=start_params)
p = mod.predict(res.params, which="probs")
args = self.convert_params(res.params)
p1 = -np.diff(ddistr.sf(np.arange(21), *args))
assert_allclose(p, p1, rtol=1e-13)

# using cdf limits precision to computation around 1
p1 = np.diff(ddistr.cdf(np.arange(21), *args))
assert_allclose(p, p1, rtol=1e-13, atol=1e-15)
freq = np.bincount(xx.astype(int))
# truncate at last observed
k = len(freq)
if k > 10:
# reduce low count bins for heavy tailed distributions
k = 10
freq[k - 1] += freq[k:].sum()
freq = freq[:k]
p = mod.predict(res.params, which="probs", k_max=k)
p[k - 1] += 1 - p[:k].sum()
tchi2 = stats.chisquare(freq, p[:k] * nobs)
assert tchi2.pvalue > 0.01

# estimated distribution methods rvs, ppf
# frozen distribution with estimated parameters
# Todo results method
dfr = mod.get_distr(res.params)
nobs_rvs = 500
rvs = dfr.rvs(size=nobs_rvs)
>   freq = np.bincount(rvs)

../.pybuild/cpython3_3.11_statsmodels/build/statsmodels/distributions/tests/test_discrete.py:302:
 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

args = (array([2, 0, 3, 1, 1, 2, 2, 5, 1, 1, 1, 3, 2, 1, 2, 0, 2, 2, 4, 2, 2, 1,
   3, 2, 1, 1, 1, 1, 4, 2, 4, 2, 1, 1, 2... 2, 4, 1, 2, 1, 2, 0, 1, 1, 2, 
1, 2, 2, 2, 4, 0,
   4, 1, 1, 2, 2, 1, 1, 3, 2, 3, 2, 1, 3, 1, 1, 2], dtype=int64),)
kwargs = {}
relevant_args = (array([2, 0, 3, 1, 1, 2, 2, 5, 1, 1, 1, 3, 2, 1, 2, 0, 2, 2, 
4, 2, 2, 1,
   3, 2, 1, 1, 1, 1, 4, 2, 4, 2, 1, 1, 2..., 1, 2, 1, 2, 0, 1, 1, 2, 1, 2, 
2, 2, 4, 0,
   4, 1, 1, 2, 2, 1, 1, 3, 2, 3, 2, 1, 3, 1, 1, 2], dtype=int64), None)

>   ???
E   TypeError: Cannot cast array data from dtype('int64') to dtype('int32') 
according to the rule 'safe'

<__array_function__ internals>:200: TypeError
- Captured stdout call -
Optimization terminated successfully.
 Current function value: 1.491508
 Iterations: 64
 Function evaluations: 122
 TestDiscretizedExponential.test_basic _

self = 


def test_basic(self):
d_offset = self.d_offset
ddistr = self.ddistr
paramg = self.paramg
paramd = self.paramd
shapes = self.shapes
start_params = self.start_params

np.random.seed(987146)

dp = DiscretizedCount(ddistr, d_offset)
assert dp.shapes == shapes
xi = 

Processed: Re: Bug#1030208: Acknowledgement (statsmodels: FTBFS with scipy 1.10 on 32-bit: int64 -> int32 cast)

[Debian Bug Tracking System]

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

> reassign 1030210 python3-statsmodels
Bug #1030210 [src:statsmodels] statsmodels FTBFS on 32bit
Bug reassigned from package 'src:statsmodels' to 'python3-statsmodels'.
No longer marked as found in versions statsmodels/0.13.5+dfsg-4.
Ignoring request to alter fixed versions of bug #1030210 to the same values 
previously set
> reassign 1030221 python3-statsmodels
Bug #1030221 [src:statsmodels] statsmodels: 32 bit arches fail tests using int64
Bug reassigned from package 'src:statsmodels' to 'python3-statsmodels'.
No longer marked as found in versions statsmodels/0.13.5+dfsg-4.
Ignoring request to alter fixed versions of bug #1030221 to the same values 
previously set
> merge 1030208 1030210 1030221
Bug #1030208 [python3-statsmodels] statsmodels: FTBFS with scipy 1.10 on 
32-bit: int64 -> int32 cast
Bug #1030221 [python3-statsmodels] statsmodels: 32 bit arches fail tests using 
int64
Marked as found in versions statsmodels/0.13.5+dfsg-4.
Added tag(s) ftbfs.
Bug #1030208 [python3-statsmodels] statsmodels: FTBFS with scipy 1.10 on 
32-bit: int64 -> int32 cast
Added tag(s) ftbfs.
Bug #1030210 [python3-statsmodels] statsmodels FTBFS on 32bit
Marked as found in versions statsmodels/0.13.5+dfsg-4.
Merged 1030208 1030210 1030221
> tags 1030208 pending
Bug #1030208 [python3-statsmodels] statsmodels: FTBFS with scipy 1.10 on 
32-bit: int64 -> int32 cast
Bug #1030210 [python3-statsmodels] statsmodels FTBFS on 32bit
Bug #1030221 [python3-statsmodels] statsmodels: 32 bit arches fail tests using 
int64
Added tag(s) pending.
Added tag(s) pending.
Added tag(s) pending.
>
End of message, stopping processing here.

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

Bug#1030177: marked as done (pygame-sdl2: FTBFS: pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: '2.1.0-for-renpy-8.0.2')

[Debian Bug Tracking System]

Your message dated Thu, 02 Feb 2023 21:38:04 +
with message-id 
and subject line Bug#1030177: fixed in pygame-sdl2 8.0.2-2
has caused the Debian Bug report #1030177,
regarding pygame-sdl2: FTBFS: 
pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: 
'2.1.0-for-renpy-8.0.2'
to be marked as done.

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

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


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

https://buildd.debian.org/status/fetch.php?pkg=pygame-sdl2=amd64=8.0.2-1%2Bb2=1675116153=0

running install_egg_info
Traceback (most recent call last):
  File "/<>/setup.py", line 143, in 
setup(
  File "/<>/setuplib.py", line 332, in setup
setuptools.setup(
  File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 108, in 
setup
return distutils.core.setup(**attrs)
   ^
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line 
185, in setup
return run_commands(dist)
   ^^
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line 
201, in run_commands
dist.run_commands()
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
969, in run_commands
self.run_command(cmd)
  File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1213, in 
run_command
super().run_command(command)
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
988, in run_command
cmd_obj.run()
  File "/usr/lib/python3/dist-packages/setuptools/command/install.py", line 68, 
in run
return orig.install.run(self)
   ^^
  File 
"/usr/lib/python3/dist-packages/setuptools/_distutils/command/install.py", line 
709, in run
self.run_command(cmd_name)
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line 318, 
in run_command
self.distribution.run_command(command)
  File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1213, in 
run_command
super().run_command(command)
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
987, in run_command
cmd_obj.ensure_finalized()
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line 111, 
in ensure_finalized
self.finalize_options()
  File "/usr/lib/python3/dist-packages/setuptools/command/install_egg_info.py", 
line 31, in finalize_options
ei_cmd = self.get_finalized_command("egg_info")
 ^^
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line 305, 
in get_finalized_command
cmd_obj.ensure_finalized()
  File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line 111, 
in ensure_finalized
self.finalize_options()
  File "/usr/lib/python3/dist-packages/setuptools/command/egg_info.py", line 
219, in finalize_options
parsed_version = parse_version(self.egg_version)
 ^^^
  File 
"/usr/lib/python3/dist-packages/pkg_resources/_vendor/packaging/version.py", 
line 266, in __init__
raise InvalidVersion(f"Invalid version: '{version}'")
pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: 
'2.1.0-for-renpy-8.0.2'
E: pybuild pybuild:388: install: plugin distutils failed with: exit code=1: 
/usr/bin/python3 setup.py install --root 
/<>/debian/python3-pygame-sdl2 
dh_auto_install: error: pybuild --install -i python{version} -p 3.11 --dest-dir 
/<>/debian/python3-pygame-sdl2 returned exit code 13
make: *** [debian/rules:6: binary-arch] Error 25

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: pygame-sdl2
Source-Version: 8.0.2-2
Done: Markus Koschany 

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated pygame-sdl2 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive

Bug#1013935: dogtag-pki: flaky autopkgtest: regularly times out on amd64, armhf and s390x

[Paul Gevers]

Hi Adrian,

On 02-02-2023 21:32, Adrian Bunk wrote:

On Mon, Jun 27, 2022 at 08:31:53PM +0200, Paul Gevers wrote:

I looked at the results of the autopkgtest of you package because it was
showing up on our "slow" page [1]. I noticed that there were several runs
that took 2:47 (our timeout time), while successful runs more in the order
of minutes.
...


Lookking at debci results with recent versions, this problem seems to be
fixed now?


It was a mistake that the block was lifted, but indeed, you might be right.


There only seems to be an unrelated(?) error
   Installation failed: Server did not start after 60s
on !amd64 that results in fast failures.


But that is an RC issue on it's own, because dogtag-pki used to pass on 
all architectures and autopkgtest regression is listed on 
https://release.debian.org/testing/rc_policy.txt


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1030177: marked as pending in pygame-sdl2

[Markus Koschany]

Control: tag -1 pending

Hello,

Bug #1030177 in pygame-sdl2 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/games-team/pygame-sdl2/-/commit/7d6dd7459876113fa14559a9fc3aa4c3e3f03ef2


Fix FTBFS with latest setuptools version.

Closes: #1030177
Thanks: Sebastian Ramacher for the report and James Addison for the assistance.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1030177

Processed: Bug#1030177 marked as pending in pygame-sdl2

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1030177 [src:pygame-sdl2] pygame-sdl2: FTBFS: 
pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: 
'2.1.0-for-renpy-8.0.2'
Added tag(s) pending.

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

Bug#1030177: pygame-sdl2: FTBFS: pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: '2.1.0-for-renpy-8.0.2'

[Markus Koschany]

Thanks for your help!

Cheers,

Markus


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

Bug#1013935: dogtag-pki: flaky autopkgtest: regularly times out on amd64, armhf and s390x

[Adrian Bunk]

On Mon, Jun 27, 2022 at 08:31:53PM +0200, Paul Gevers wrote:
> Source: dogtag-pki
> Version: 11.0.0-1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: flaky
> 
> Dear maintainer(s),
> 
> I looked at the results of the autopkgtest of you package because it was
> showing up on our "slow" page [1]. I noticed that there were several runs
> that took 2:47 (our timeout time), while successful runs more in the order
> of minutes.
>...

Lookking at debci results with recent versions, this problem seems to be 
fixed now?

There only seems to be an unrelated(?) error
  Installation failed: Server did not start after 60s
on !amd64 that results in fast failures.

> Paul
>...

cu
Adrian

Bug#1029829: amanda: CVE-2022-37704 CVE-2022-37705

[Damyan Ivanov]

-=| Jose M Calhariz, 02.02.2023 19:20:23 + |=-
> This is my first security update, can I ask what is the procedure or 
> where is documented?

https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#bug-security-building

https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#bug-security


-- Damyan


> On January 28, 2023 12:59:09 PM GMT+00:00, Salvatore Bonaccorso
>  wrote:
> 
> Source: amanda
> Version: 1:3.5.1-9
> Severity: grave
> Tags: security upstream
> Justification: user security hole
> X-Debbugs-Cc: car...@debian.org, Debian Security Team 
> 
> 
> Hi,
> 
> The following vulnerabilities were published for amanda.
> 
> CVE-2022-37704[0], CVE-2022-37705[1].
> 
> 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-37704
> https://www.cve.org/CVERecord?id=CVE-2022-37704
> [1] https://security-tracker.debian.org/tracker/CVE-2022-37705
> https://www.cve.org/CVERecord?id=CVE-2022-37705
> [2] https://github.com/zmanda/amanda/issues/192
> 
> Please adjust the affected versions in the BTS as needed.
> 
> Regards,
> Salvatore
> 

Processed: Re: Bug#1028041: php-excimer: FTBFS on mipsel

[Debian Bug Tracking System]

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

> severity 1028041 normal
Bug #1028041 [src:php-excimer] php-excimer: FTBFS on mipsel
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#1028041: php-excimer: FTBFS on mipsel

[Kunal Mehta]

severity 1028041 normal
thanks

Hi,

On 1/6/23 13:47, Adrian Bunk wrote:

On Fri, Jan 06, 2023 at 08:59:08AM +0100, Paul Gevers wrote:

=
FAILED TEST SUMMARY
-
ExcimerProfiler CPU profile [tests/cpu.phpt]
=

Please fix ASAP to not block the php8.2 transition.


It built after I gave it back to build on the right buildd,
so it's now rebuilt with PHP 8.2.


Thanks.


The issue might depend on buildd speed, or some weird difference
between buildds.


Looking through my email, it's flaked before in the past (#1014801). The 
test in question[1] has the following comment:


// Test aggregateByFunction
// Typically the parent functions foo() and bar() will have self=0 and
// inclusive ~= 30. The other 4 functions will have a count of about 
30/4 = 7.5.
// The probability of C::member() or baz() having a count of zero is 
about 1 in 5600.


Maybe the known flakiness is worse due to something on the mipsel build? 
I'll ask the upstream author. Worst case we can just skip the test on 
mipsel.


I'm lowering the severity because it no longer blocks the 8.2 transition 
(please revert me if I'm wrong on that).


[1] 
https://salsa.debian.org/mediawiki-team/php-excimer/-/blob/master/tests/cpu.phpt


-- Kunal

Bug#1029829: amanda: CVE-2022-37704 CVE-2022-37705

[Jose M Calhariz]

Hi,

This is my first security update, can I ask what is the procedure or where is 
documented?

Kind regards
Jose M Calhariz



On January 28, 2023 12:59:09 PM GMT+00:00, Salvatore Bonaccorso 
 wrote:
>Source: amanda
>Version: 1:3.5.1-9
>Severity: grave
>Tags: security upstream
>Justification: user security hole
>X-Debbugs-Cc: car...@debian.org, Debian Security Team 
>
>
>Hi,
>
>The following vulnerabilities were published for amanda.
>
>CVE-2022-37704[0], CVE-2022-37705[1].
>
>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-37704
>https://www.cve.org/CVERecord?id=CVE-2022-37704
>[1] https://security-tracker.debian.org/tracker/CVE-2022-37705
>https://www.cve.org/CVERecord?id=CVE-2022-37705
>[2] https://github.com/zmanda/amanda/issues/192
>
>Please adjust the affected versions in the BTS as needed.
>
>Regards,
>Salvatore

Processed: dh-virtualenv: diff for NMU version 1.2.2-1.3

[Debian Bug Tracking System]

Processing control commands:

> tags 1030170 + pending
Bug #1030170 [dh-virtualenv] dh-virtualenv: Broken on Python 3.11, 
AttributeError: module 'inspect' has no attribute 'getargspec'
Added tag(s) pending.

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

Bug#1030170: dh-virtualenv: diff for NMU version 1.2.2-1.3

[Kunal Mehta]

Control: tags 1030170 + pending


Dear maintainer,

I've prepared an NMU for dh-virtualenv (versioned as 1.2.2-1.3) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru dh-virtualenv-1.2.2/debian/changelog dh-virtualenv-1.2.2/debian/changelog
--- dh-virtualenv-1.2.2/debian/changelog	2022-08-25 15:01:52.0 -0400
+++ dh-virtualenv-1.2.2/debian/changelog	2023-02-02 14:10:21.0 -0500
@@ -1,3 +1,10 @@
+dh-virtualenv (1.2.2-1.3) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Cherry-pick upstream patch for Python 3.11 support (Closes: #1030170)
+
+ -- Kunal Mehta   Thu, 02 Feb 2023 14:10:21 -0500
+
 dh-virtualenv (1.2.2-1.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru dh-virtualenv-1.2.2/debian/patches/0001-Replace-usage-of-inspect.getargspec-with-inspect.get.patch dh-virtualenv-1.2.2/debian/patches/0001-Replace-usage-of-inspect.getargspec-with-inspect.get.patch
--- dh-virtualenv-1.2.2/debian/patches/0001-Replace-usage-of-inspect.getargspec-with-inspect.get.patch	1969-12-31 19:00:00.0 -0500
+++ dh-virtualenv-1.2.2/debian/patches/0001-Replace-usage-of-inspect.getargspec-with-inspect.get.patch	2023-02-02 13:58:02.0 -0500
@@ -0,0 +1,24 @@
+From: Andrew Morgan 
+Date: Tue, 3 Jan 2023 14:29:53 +
+Subject: Replace usage of inspect.getargspec with inspect.getfullargspec
+
+It's debatable whether this check is even still needed, but for now
+let's do the simple thing and update it to be compatible with modern
+Python versions.
+---
+ bin/dh_virtualenv | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/bin/dh_virtualenv b/bin/dh_virtualenv
+index 8bafbcf..0a422ad 100755
+--- a/bin/dh_virtualenv
 b/bin/dh_virtualenv
+@@ -57,7 +57,7 @@ def main():
+ # passed the packages keyword argument. Newer (like Ubuntu
+ # Precise) expect the whole options to be passed.
+ 
+-arguments = inspect.getargspec(DebHelper.__init__).args
++arguments = inspect.getfullargspec(DebHelper.__init__).args
+ if 'packages' in arguments:
+ dh = DebHelper(packages=options.package or None)
+ else:
diff -Nru dh-virtualenv-1.2.2/debian/patches/series dh-virtualenv-1.2.2/debian/patches/series
--- dh-virtualenv-1.2.2/debian/patches/series	1969-12-31 19:00:00.0 -0500
+++ dh-virtualenv-1.2.2/debian/patches/series	2023-02-02 13:58:02.0 -0500
@@ -0,0 +1 @@
+0001-Replace-usage-of-inspect.getargspec-with-inspect.get.patch

Bug#1030309: marked as done (kodi-game-libretro-bsnes-mercury-accuracy: Depends: libretro-bsnes-accuracy-balanced but it is not installable)

[Debian Bug Tracking System]

Your message dated Thu, 02 Feb 2023 19:06:20 +
with message-id 
and subject line Bug#1030309: fixed in libretro-bsnes-mercury 094+git20220807-5
has caused the Debian Bug report #1030309,
regarding kodi-game-libretro-bsnes-mercury-accuracy: Depends: 
libretro-bsnes-accuracy-balanced but it is not installable
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.)


-- 
1030309: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030309
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kodi-game-libretro-bsnes-mercury-accuracy
Version: 094+git20220807-4
Severity: serious

The following packages have unmet dependencies:
 kodi-game-libretro-bsnes-mercury-accuracy : Depends: 
libretro-bsnes-accuracy-balanced but it is not installable


Was the dependency intended to be on libretro-bsnes-mercury-accuracy instead?
--- End Message ---
--- Begin Message ---
Source: libretro-bsnes-mercury
Source-Version: 094+git20220807-5
Done: Jonathan McDowell 

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

Debian distribution maintenance software
pp.
Jonathan McDowell  (supplier of updated 
libretro-bsnes-mercury package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 02 Feb 2023 18:49:15 +
Source: libretro-bsnes-mercury
Architecture: source
Version: 094+git20220807-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Jonathan McDowell 
Closes: 1030309
Changes:
 libretro-bsnes-mercury (094+git20220807-5) unstable; urgency=medium
 .
   * Team upload
   * Fix kodi-game-libretro-bsnes-mercury-accuracy dependency
 (Closes: #1030309)
Checksums-Sha1:
 635eb974a4cdde046be75215c6cab052c9f43d2b 2719 
libretro-bsnes-mercury_094+git20220807-5.dsc
 7fba0bc5cd7199244ccf7b1cb63b4aae0d8dab37 9840 
libretro-bsnes-mercury_094+git20220807-5.debian.tar.xz
 23a692235b1fcb49b84a30d0afac8c3491b2071c 9393 
libretro-bsnes-mercury_094+git20220807-5_amd64.buildinfo
Checksums-Sha256:
 dd011ca698bf9b8060ede7efe0c172ed714fcd12e283e6b8a306cc6c098efbde 2719 
libretro-bsnes-mercury_094+git20220807-5.dsc
 0bdf2849db11c1cdb4ffc7646acd6b46747c0940988510d47b7293bd1bdf5ebf 9840 
libretro-bsnes-mercury_094+git20220807-5.debian.tar.xz
 a020e6b194f1db404221799d73671dc2763f260e0c59a7ccfb64c513f6611e5f 9393 
libretro-bsnes-mercury_094+git20220807-5_amd64.buildinfo
Files:
 78f8d91f095225cc7ce24ddc4ddc3b99 2719 games optional 
libretro-bsnes-mercury_094+git20220807-5.dsc
 6516f47efa79bbe49ad4bd99859a0029 9840 games optional 
libretro-bsnes-mercury_094+git20220807-5.debian.tar.xz
 8fae692021a1e8a98a402da2556edc43 9393 games optional 
libretro-bsnes-mercury_094+git20220807-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEERUuPEyEc/2gMWDpQ/xYvxc8/utEFAmPcB/kACgkQ/xYvxc8/
utF3AQ//da99GZnYIa0cT0yOh/1BWbl+U1T5EBwNWwGHHvrJV2CIfEOZFKYgdL5j
1CGVyjJtp+U85d1q+/DojLIkxixf+HTCil7+I8tg/KNX/kQ7Kwnphr1ys9pRG6/Q
uHH0ZOZBxA7zeB9bcWOwtXTNH2khDWVhl/MXA0I4Kw5ko4kIapS3gfo1Rh1GsOZq
WU6OLMG/AWFukx3wWoX2NM17PVlfahUvjpRSA2SR/qn46tZS4mwUIB6KJtI9WaRx
ZJeiXjVW0HOU2N8Ev26/E03dbLC/pjWpiQdiXure2KI4/mBOKCihb6GBIuhUoggo
1gYmRFS6V0AZBZYHSq2xZ++FpdeJDol/46euILETHyWzuvqynUzzSGJSO8HRQgHG
hApo2sDEAEOMa+FDosQK244Amu1SugNQ5Plf50gcic1dP8vAQo3Sz0jIBCRlZm44
XXmj1tCdq5o4iMg9U720dVQ4U8J2xGadtFxgMo36ppI2wLvKIGo5b8zmcnWytNnI
P2SiwzyyQcigvLkI0LyOjJr4GqkuxxFgvWmrauu8ZU3B1qW47XUHusrOa5s0S7Ex
Fkmr8EMkxQq1VN7TA/Oquz39ggOq9kjinwnsY+lMTk5Sl0X7Sb3e5nbxDubqBJlv
RPLaGp6TAzKvA4+S0xb/atkMUeSO+ls6vuuSmSEQLh3pbu6ix/A=
=izXR
-END PGP SIGNATURE End Message ---

Bug#1022096: marked as done (e2fsprogs: Inaccurate copyright file)

[Debian Bug Tracking System]

Your message dated Thu, 02 Feb 2023 19:04:26 +
with message-id 
and subject line Bug#1022096: fixed in e2fsprogs 1.46.6-1
has caused the Debian Bug report #1022096,
regarding e2fsprogs: Inaccurate copyright file
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.)


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

Source: e2fsprogs
Severity: serious
Tags: patch
Version: 1.46.6~rc1-1

Hi Theodore,

There are several distribution licenses and copyright information not
mentioned, which are required by Debian Policy §12.5. I have attached
a patch fixing this, which also has the conversion of the copyright
files that are still in use to the machine-readable format.

Also attached is a patch for the upstream source (as you are also the
upstream maintainer) that applies a license requirement that I found
not to be present.

Thanks for your consideration,
BastianFrom 59c43fc9e933238789d4f6863adcf67c79679979 Mon Sep 17 00:00:00 2001
From: Bastian Germann 
Date: Mon, 17 Oct 2022 18:50:35 +0200
Subject: [PATCH] dict: Add modifification note required by license

The Kazlib license says:

"Permission is also granted to adapt this software to produce
derivative works, as long as the modified versions carry this copyright
notice and additional notices stating that the work has been modified."

Add the missing notice stating that the work has been modified.

Signed-off-by: Bastian Germann 
---
 lib/support/dict.c | 1 +
 lib/support/dict.h | 1 +
 2 files changed, 2 insertions(+)

diff --git a/lib/support/dict.c b/lib/support/dict.c
index ee0bf29b..93fdd0b2 100644
--- a/lib/support/dict.c
+++ b/lib/support/dict.c
@@ -16,6 +16,7 @@
  *
  * $Id: dict.c,v 1.40.2.7 2000/11/13 01:36:44 kaz Exp $
  * $Name: kazlib_1_20 $
+ * The work has been modified.
  */
 
 #define DICT_NODEBUG
diff --git a/lib/support/dict.h b/lib/support/dict.h
index f1382e1d..2d87cc00 100644
--- a/lib/support/dict.h
+++ b/lib/support/dict.h
@@ -16,6 +16,7 @@
  *
  * $Id: dict.h,v 1.22.2.6 2000/11/13 01:36:44 kaz Exp $
  * $Name: kazlib_1_20 $
+ * The work has been modified.
  */
 
 #ifndef DICT_H
-- 
2.30.2

From 040c3b9f3376c30bf0e711d4c729bc76556bc3d3 Mon Sep 17 00:00:00 2001
From: Viraj Shah 
Date: Mon, 17 Oct 2022 12:57:40 +0200
Subject: [PATCH] debian: make the copyright file machine readable
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Debian introduced a machine-readable copyright file a while ago.
Convert the general copyright file and the package-specific ones,
splitting the info that belongs to the package-specific ones.
Drop debian/e2fsck-static.copyright because that does not have a
file set that is very distinct from the general source; it would
just replicate parts of it.

This change adds some missing licenses that have to be documented
according to Debian Policy §12.5 as well as the copyright info for
many files.

Signed-off-by: Viraj Shah 
Signed-off-by: Bastian Germann 
---
 debian/copyright| 476 +++-
 debian/e2fsck-static.copyright  |  26 --
 debian/e2fsprogs-l10n.copyright |  52 ++--
 debian/libcom-err2.copyright| 143 --
 debian/libss2.copyright |  61 ++--
 5 files changed, 592 insertions(+), 166 deletions(-)
 delete mode 100644 debian/e2fsck-static.copyright

diff --git a/debian/copyright b/debian/copyright
index e6f46761..f18058eb 100644
--- a/debian/copyright
+++ b/debian/copyright
@@ -1,73 +1,403 @@
-This is the Debian GNU/Linux prepackaged version of the EXT2 file
-system utilities (e2fsck, mke2fs, etc.).  The EXT2 utilities were
-written by Theodore Ts'o  and Remy Card .
-
-Sources were obtained from http://sourceforge.net/projects/e2fsprogs
-
-Packaging is Copyright (c) 2003-2007 Theodore Ts'o 
- Copyright (c) 1997-2003 Yann Dirson 
-	 Copyright (c) 2001 Alcove 
-	 Copyright (c) 1997 Klee Dienes
-	 Copyright (c) 1995-1996 Michael Nonweiler 
-
-Upstream Author: Theodore Ts'o 
-
-Copyright notice:
-
-This package, the EXT2 filesystem utilities, are made available under
-the GNU General Public License version 2, with the exception of the
-lib/ext2fs and lib/e2p libraries, which are made available under the
-GNU Library General Public License Version 2, the lib/uuid library
-which is made available under a BSD-style license and the lib/et and
-lib/ss libraries which are made available under an MIT-style license.
-
-	Copyright (c) 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, 
-	2001, 2002, 

Bug#1030177: pygame-sdl2: FTBFS: pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: '2.1.0-for-renpy-8.0.2'

[James Addison]

Source: pygame-sdl2
Followup-For: Bug #1030177

Dear Maintainer,

There's an upstream 'setuptools' issue[1] tracking these InvalidVersion
exceptions: basically, version parsing is checking for PEP440[2] adherence.

Updating the egg_info tag[2] for pygame-sdl2 to match the spec should resolve
the problem.

(in this case, one way to fix the bug could be: s/-for-renpy/+for-renpy/ )

Thanks,
James

[1] - https://github.com/pypa/setuptools/issues/3772

[2] - https://peps.python.org/pep-0440/

[3] - 
https://salsa.debian.org/games-team/pygame-sdl2/-/blob/b1c1d5df2d0095cbed3ade64367b460fa684788a/setup.cfg#L2

Bug#971783: marked as pending in mate-media

[Hanno Zysik]

Hi Mike,

looks like the same fix could be applied to
https://github.com/mate-desktop/mate-media/blob/1.26/mate-volume-control/gvc-stream-status-icon.c#L778
 ??

display_name is not properly freed in the very same way. My mate panel
uses /usr/bin/mate-volume-control-status-icon, which would still crash
AFAIS.

Kind regards,

Am Thu, 02 Feb 2023 15:47:20 +
schrieb Mike Gabriel :

> Control: tag -1 pending
>
> Hello,
>
> Bug #971783 in mate-media reported by you has been fixed in the
> Git repository and is awaiting an upload. You can see the commit
> message below and you can check the diff of the fix at:
>
> https://salsa.debian.org/debian-mate-team/mate-media/-/commit/36e7aedcf039d35034e6cbf0f23b7cc5619c0ae3
>
> 
> debian/patches: Add 0002_fix-memleak-in-vol-mixer.patch. (Closes:
> #971783).
> 
>
> (this message was generated automatically)



--
Hanno Zysik

Software Entwickler/Software engineer
Dipl.-Ing. IT (FH)/University of applied sciences

Processed: found 1027215 in 1.1.2+dfsg-3

[Debian Bug Tracking System]

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

> found 1027215 1.1.2+dfsg-3
Bug #1027215 [src:theano] theano: autopkgtest fail with numpy/1.24.1
Marked as found in versions theano/1.1.2+dfsg-3.
> thanks
Stopping processing here.

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

Bug#1026539: theano FTBFS

[Adrian Bunk]

On Tue, Jan 03, 2023 at 10:21:16PM +, Rebecca N. Palmer wrote:
> Please do *not* upload theano 1.12 to unstable - it's the Aesara version,
> which may seriously break backward compatibility.
> 
> I haven't had time to properly look at this bug yet.

FTR, right now autopkgtest and build of both the version in 
bookworm/unstable and the version in experimental fail due
to #1027215 (numpy 1.24).

cu
Adrian

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> reassign 1026763 fpc
Bug #1026763 [src:tuxcmd] tuxcmd: FTBFS: /usr/bin/ld.bfd: cannot find 
-lgthread-2.0: No such file or directory
Bug reassigned from package 'src:tuxcmd' to 'fpc'.
No longer marked as found in versions tuxcmd/0.6.70+dfsg-3.
Ignoring request to alter fixed versions of bug #1026763 to the same values 
previously set
> forcemerge 1026719 1026763
Bug #1026719 {Done: Gürkan Myczko } [fpc] vmg: FTBFS: 
/usr/bin/ld.bfd: cannot find -latk-1.0: No such file or directory
Bug #1026718 {Done: Gürkan Myczko } [fpc] lazpaint: FTBFS: 
/usr/bin/ld.bfd: cannot find -lpangocairo-1.0: No such file or directory
Bug #1026763 [fpc] tuxcmd: FTBFS: /usr/bin/ld.bfd: cannot find -lgthread-2.0: 
No such file or directory
Marked Bug as done
Added indication that 1026763 affects vmg
Marked as fixed in versions lazpaint/7.2.2-2 and fpc/3.2.2+dfsg-18.
Bug #1026718 {Done: Gürkan Myczko } [fpc] lazpaint: FTBFS: 
/usr/bin/ld.bfd: cannot find -lpangocairo-1.0: No such file or directory
Merged 1026718 1026719 1026763
> affects 1026719 src:vmg src:tuxcmd
Bug #1026719 {Done: Gürkan Myczko } [fpc] vmg: FTBFS: 
/usr/bin/ld.bfd: cannot find -latk-1.0: No such file or directory
Bug #1026718 {Done: Gürkan Myczko } [fpc] lazpaint: FTBFS: 
/usr/bin/ld.bfd: cannot find -lpangocairo-1.0: No such file or directory
Bug #1026763 {Done: Gürkan Myczko } [fpc] tuxcmd: FTBFS: 
/usr/bin/ld.bfd: cannot find -lgthread-2.0: No such file or directory
Added indication that 1026719 affects src:vmg and src:tuxcmd
Added indication that 1026718 affects src:vmg and src:tuxcmd
Added indication that 1026763 affects src:vmg and src:tuxcmd
> thanks
Stopping processing here.

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

Processed: block 1026728 with 1009955

[Debian Bug Tracking System]

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

> block 1026728 with 1009955
Bug #1026728 [src:cssutils] cssutils: FTBFS: dh_auto_test: error: pybuild 
--test --test-pytest -i python{version} -p "3.11 3.10" returned exit code 13
1026728 was not blocked by any bugs.
1026728 was not blocking any bugs.
Added blocking bug(s) of 1026728: 1009955
> thanks
Stopping processing here.

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

Processed: forcibly merging 1026738 1027250

[Debian Bug Tracking System]

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

> forcemerge 1026738 1027250
Bug #1026738 [src:keras] keras: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p "3.11 3.10" returned exit code 13
Bug #1027250 [src:keras] keras: autopkgtest fail with numpy/1.24.1
Added tag(s) sid, ftbfs, and bookworm.
Merged 1026738 1027250
> thanks
Stopping processing here.

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

Bug#1028983: marked as done (yade: FTBFS with Python 3.11 as default version)

[Debian Bug Tracking System]

Your message dated Thu, 02 Feb 2023 17:51:11 +
with message-id 
and subject line Bug#1028983: fixed in yade 2023.02a-1~exp1
has caused the Debian Bug report #1028983,
regarding yade: FTBFS with Python 3.11 as default version
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.)


-- 
1028983: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028983
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: yade
Version: 2022.01a-13
Severity: serious
Tags: ftbfs patch
User: debian-pyt...@lists.debian.org
Usertags: python3.11

Hi Maintainer

yade FTBFS with Python 3.11 as default version, although the build
doesn't fail, it is mislinked against Python 3.10.

I believe this is the relevant part of the log:

Loop on the following python versions and check available
dependencies:3.10;3.9;3.8;3.7;3.6;3.5;3.4;3.3;3.2;3.1;3.0
-- Found PythonInterp: /usr/bin/python3.10 (found version "3.10.9")
Trying python version: 3.10 parsed as 3 10
Python version 3.10.9 found, try to import dependencies...
Boost_VERSION=107400, adding boost_python310 lib

Updating debian/patches/30_python310.patch as follows worked for me:

-+SET(PY3_VERSIONS 3.10 3.9 3.8 3.7 3.6 3.5 3.4 3.3 3.2 3.1 3.0)
#append newer python versions at the beginning here.
++SET(PY3_VERSIONS 3.11 3.10 3.9 3.8 3.7 3.6 3.5 3.4 3.3 3.2 3.1 3.0)
#append newer python versions at the beginning here.

Regards
Graham


[1] 
https://buildd.debian.org/status/fetch.php?pkg=yade=amd64=2022.01a-13=1673794605=0
--- End Message ---
--- Begin Message ---
Source: yade
Source-Version: 2023.02a-1~exp1
Done: Anton Gladky 

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

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated yade package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 02 Feb 2023 07:23:39 +0100
Source: yade
Architecture: source
Version: 2023.02a-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Anton Gladky 
Closes: 1022735 1028983
Changes:
 yade (2023.02a-1~exp1) experimental; urgency=medium
 .
   * [dcff066] New upstream version 2023.02a. (Closes: #1028983, #1022735)
   * [873e430] Remove all patches (applied by upstream)
   * [ad4babe] Remove lintian overrides
Checksums-Sha1:
 e492c2bd37fe07f59b181d32bc8271ce8c405dce 3267 yade_2023.02a-1~exp1.dsc
 5a21c9ae20e7a1eb3021f18feab94b8b501b8b4f 12215773 yade_2023.02a.orig.tar.bz2
 c0a01451801c20766eb2728a61eadf90551e6950 833 yade_2023.02a.orig.tar.bz2.asc
 11fc872442ee0f1a7e00e264fcfa5f4de62f20c0 25548 
yade_2023.02a-1~exp1.debian.tar.xz
 e2c460ace1ae6222b81b9dde719fb8073f29152f 22346 
yade_2023.02a-1~exp1_source.buildinfo
Checksums-Sha256:
 1057f311459f467143812ce679b06551afcc302147ac8b99d56c93dddacea676 3267 
yade_2023.02a-1~exp1.dsc
 b9444ae333ad7d02197cf3a5f6ad087653a0ba90f2840ab72530063ba22d4a4d 12215773 
yade_2023.02a.orig.tar.bz2
 0274a40af8462ff0fc240a92dcf9ea4f223f01735b5da5000e1e5732a27cc76f 833 
yade_2023.02a.orig.tar.bz2.asc
 eab9271d80112a9861282a5d80d02366cc4cb984b5daf472386d29e88cdd2ffe 25548 
yade_2023.02a-1~exp1.debian.tar.xz
 e0a0ae02d76dbd47585455d3201f9fd745917bfb869d4713d8439e3eccca8116 22346 
yade_2023.02a-1~exp1_source.buildinfo
Files:
 1267cb93bef3a132c27bcdc8017ff956 3267 science optional yade_2023.02a-1~exp1.dsc
 6422f042faac28b3bc74108969c304c1 12215773 science optional 
yade_2023.02a.orig.tar.bz2
 be214962ae5e64f4ce11873e7cd2312a 833 science optional 
yade_2023.02a.orig.tar.bz2.asc
 3ba7d0a4477de7b2b7d4f65c090d02b7 25548 science optional 
yade_2023.02a-1~exp1.debian.tar.xz
 aa16359fe5b0a239c81dbd034fd04b88 22346 science optional 
yade_2023.02a-1~exp1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAmPb80wACgkQ0+Fzg8+n
/waE7A/9FzH8o4GMAFa98Ije+fUYDh/qAnsFtjMgrAP1dwVt223l9gganOS52OSv
IcCACHwyaLSDHvUpm4V9cDFBzzpvByOqtEkVPXAvxjtICdCLJP/XpTk+RVw0Dyk6
gkuNNi4hFG60La2A+FSqtfchowkV3ch0Nhaz4iXXyG7Xe+h+dk6SW99qb/rv3uYP
NMnUvEcck6nG+8cigQPJLGOUvZtNMrlsEyusswl95Wq24ZSucjbgp5mzCTPYH37E

Bug#1030160: chromium: FTBFS on arm64/armhf in bullseye-security (V4L issues)

[Andres Salomon]

On Thu, Feb 2 2023 at 02:14:42 PM +, "Steinberg, Benjamin" 
 wrote:
On Tue, 31 Jan 2023 13:35:49 -0500 Andres Salomon 
 wrote:


> Thanks! I forgot that it can only be enabled on sid when I merged 
the


> new release into bullseye. This will get fixed in the next security

> upload.



Thanks, Andres. Just to confirm, does



> This will get fixed in the next security upload.



mean that bullseye-security is not going to contain arm64 and armhf 
packages for Chromium 109.0.5414.119-1~deb11u1? I ask because in our 
application, I keep Chromium versions up to date and synchronized 
between deployments (amd64 machines) and developer machines (M1 
Macs). If the arm64 package for this version won’t be present, 
I’ll wait for the next version, presumably 110.0.5481.77.






Correct. I'll upload either the next v109 release (if we get one), or 
v110 (which is due out on Tuesday).

Processed: bug 1026566 is forwarded to https://github.com/elastic/curator/pull/1596

[Debian Bug Tracking System]

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

> forwarded 1026566 https://github.com/elastic/curator/pull/1596
Bug #1026566 [src:elasticsearch-curator] elasticsearch-curator: FTBFS: 
TypeError: load() missing 1 required positional argument: 'Loader'
Bug #1022015 [src:elasticsearch-curator] elasticsearch-curator: Uses deprecated 
yaml.load
Set Bug forwarded-to-address to 'https://github.com/elastic/curator/pull/1596'.
Set Bug forwarded-to-address to 'https://github.com/elastic/curator/pull/1596'.
> thanks
Stopping processing here.

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

Processed: hplip-gui: traceback when launching hp-toolbox

[Debian Bug Tracking System]

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

> tags 1030043 upstream
Bug #1030043 [hplip-gui] hplip-gui: traceback when launching hp-toolbox
Added tag(s) upstream.
> severity 1030043 important
Bug #1030043 [hplip-gui] hplip-gui: traceback when launching hp-toolbox
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Bug#990447: Similar problems

[Phil Dibowitz]

On 2/1/23 23:31, Pascal Hambourg wrote:

On 02/02/2023 at 00:33, Phil Dibowitz wrote:


And I've run `grub-install` with my EFI dir mounted. What's 
interesting is the version in EFI is different than the version staged 
by the package:


```
# sum /usr/lib/shim/shimx64.efi /boot/EFI/EFI/debian/shimx64.efi
47979   918 /usr/lib/shim/shimx64.efi
36147   913 /boot/EFI/EFI/debian/shimx64.efi
```


You must compare with /usr/lib/shim/shimx64.efi.signed from shim-signed.


Ah, thanks. At least I know I did the grub-install right:

```
$ sum /usr/lib/shim/shimx64.efi.signed /boot/EFI/EFI/debian/shimx64.efi
36147   913 /usr/lib/shim/shimx64.efi.signed
36147   913 /boot/EFI/EFI/debian/shimx64.efi
```

So I guess that means that the shimx64.efi that's distributed with 
shim-signed is, in fact, vulnerable, as proposed in the original bug.


Any timeline on updating it?

--
Phil Dibowitz p...@ipom.com
Open Source software and tech docsInsanity Palace of Metallica
http://www.phildev.net/   http://www.ipom.com/

"Be who you are and say what you feel, because those who mind don't
 matter and those who matter don't mind."
 - Dr. Seuss

Bug#971783: marked as done (mate-media: volume-control-applet dies often)

[Debian Bug Tracking System]

Your message dated Thu, 02 Feb 2023 16:04:50 +
with message-id 
and subject line Bug#971783: fixed in mate-media 1.26.0-2
has caused the Debian Bug report #971783,
regarding mate-media: volume-control-applet dies often
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.)


-- 
971783: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971783
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mate-media
Version: 1.24.1-1
Severity: normal
X-Debbugs-Cc: none, Francesco Potortì 
File: /usr/libexec/mate-volume-control-applet

On an always-on box used as desktop computer, the volume control applet
dies on average once a day.  Sometims a popup appears telling that
"Volume control" has quit unexpectedly so it ieasy to reload it.  Often
it dies without notice and I have to re-add it to the panel.  As a
conquence, sometimes I find two or three applets on the panel and I have
to remove some of them.

This is a problem that has been there for years.  Any hope to solve it?

These are the messages I found in .xsession-errors:

 strike 1
(mate-volume-control-status-icon:1761): Gtk-WARNING **: 09:23:01.755: 
gtk_widget_size_allocate(): attempt to allocate widget with width -1 and height 
1

(mate-volume-control-status-icon:1761): Gtk-WARNING **: 09:23:01.787: 
gtk_widget_size_allocate(): attempt to allocate widget with width -1 and height 
1

(mate-volume-control-status-icon:1761): Gtk-WARNING **: 09:23:01.824: 
gtk_widget_size_allocate(): attempt to allocate widget with width -1 and height 
1

(mate-volume-control-status-icon:1761): Gdk-CRITICAL **: 09:23:01.848: 
gdk_window_thaw_toplevel_updates: assertion 
'window->update_and_descendants_freeze_count > 0' failed
 end of strike 2


 strike 2
(mate-volume-control-status-icon:1761): Gtk-WARNING **: 16:04:20.142: Calling 
gtk_widget_realize() on a widget that isn't inside a toplevel window is not 
going to work very well. Widgets must be inside a toplevel container before 
realizing them.

(mate-volume-control-status-icon:1761): GLib-GObject-CRITICAL **: 16:04:20.142: 
g_object_ref: assertion 'G_IS_OBJECT (object)' failed

(mate-volume-control-status-icon:1761): Gdk-CRITICAL **: 16:04:20.142: 
gdk_window_get_scale_factor: assertion 'GDK_IS_WINDOW (window)' failed
**
Gtk:ERROR:../../../../gtk/gtkwidget.c:5871:gtk_widget_get_frame_clock: 
assertion failed: (window != NULL)
Bail out! 
Gtk:ERROR:../../../../gtk/gtkwidget.c:5871:gtk_widget_get_frame_clock: 
assertion failed: (window != NULL)

(mate-settings-daemon:1249): Gtk-WARNING **: 16:04:20.686: Calling 
gtk_widget_realize() on a widget that isn't inside a toplevel window is not 
going to work very well. Widgets must be inside a toplevel container before 
realizing them.

(mate-settings-daemon:1249): GLib-GObject-CRITICAL **: 16:04:20.686: 
g_object_ref: assertion 'G_IS_OBJECT (object)' failed

(mate-settings-daemon:1249): Gdk-CRITICAL **: 16:04:20.686: 
gdk_window_get_scale_factor: assertion 'GDK_IS_WINDOW (window)' failed
**
 end of strike 2

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

Kernel: Linux 5.8.0-2-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=C.UTF-8, LC_CTYPE=C.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 mate-media depends on:
ii  libc6 2.31-3
ii  libcairo2 1.16.0-4
ii  libcanberra-gtk3-00.30-7
ii  libcanberra0  0.30-7
ii  libgdk-pixbuf2.0-02.40.0+dfsg-5
ii  libglib2.0-0  2.66.0-2
ii  libgtk-3-03.24.23-2
ii  libmate-desktop-2-17  1.24.1-1
ii  libmate-panel-applet-4-1  1.24.1-1
ii  libmatemixer0 1.24.1-1
ii  libpango-1.0-01.46.2-1
ii  libxml2   2.9.10+dfsg-6
ii  mate-desktop-common   1.24.1-1
ii  mate-media-common 1.24.1-1

Versions of packages mate-media recommends:
ii  alsa-utils   1.2.3-1
ii  sound-theme-freedesktop  0.8-2

mate-media suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: mate-media
Source-Version: 1.26.0-2
Done: Mike Gabriel 

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

A summary of the changes between this version and the previous 

Bug#1030043: hplip-gui: traceback when launching hp-toolbox

[Brian Potkin]

tags 1029459 upstream
severity 1029459 important
thanks




On Mon 30 Jan 2023 at 17:27:10 +0100, Julien Patriarca wrote:

> Package: hplip-gui
> Version: 3.22.10+dfsg0-1
> Severity: grave
> Tags: patch
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
>* What led up to the situation?
> Trying to launch hp-toolbox software, got this output:
> 
> Traceback (most recent call last):
>   File "/usr/bin/hp-toolbox", line 280, in 
> toolbox = ui.DevMgr5(__version__, device_uri,  None)
>   ^^
>   File "/usr/share/hplip/ui5/devmgr5.py", line 238, in __init__
> core =  CoreInstall(MODE_CHECK)
> ^^^
>   File "/usr/share/hplip/installer/core_install.py", line 240, in __init__
> self.passwordObj = password.Password(ui_mode)
>^^
>   File "/usr/share/hplip/base/password.py", line 94, in __init__
> self.__readAuthType()  # self.__authType
> ^
>   File "/usr/share/hplip/base/password.py", line 119, in __readAuthType
> distro_name = get_distro_std_name(os_name)
>   ^^^
> NameError: name 'get_distro_std_name' is not defined. Did you mean: 
> 'get_distro_name'?
> 
> 
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
> 
> I patched the password.py file with the correct function name and 
> delete the os_name parameter when being called.
> 
>* What was the outcome of this action?
> 
> Positive. The hp-toolbox launched succesfully.

Thank you for your report, Julien. This issue does not
appear too dissimilar to #1029459:

 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029459

Reducing severity because not all hp-* utilities are
affected. hp-wificonfig, for instance.

Regards,

Brian.

Processed: tagging 1026563

[Debian Bug Tracking System]

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

> tags 1026563 + fixed-upstream
Bug #1026563 [src:aioxmlrpc] aioxmlrpc: FTBFS: AttributeError: module 'asyncio' 
has no attribute 'coroutine'. Did you mean: 'coroutines'?
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#971783: marked as pending in mate-media

[Mike Gabriel]

Control: tag -1 pending

Hello,

Bug #971783 in mate-media reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/debian-mate-team/mate-media/-/commit/36e7aedcf039d35034e6cbf0f23b7cc5619c0ae3


debian/patches: Add 0002_fix-memleak-in-vol-mixer.patch. (Closes: #971783).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/971783

Processed: Bug#971783 marked as pending in mate-media

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #971783 [mate-media] mate-media: volume-control-applet dies often
Added tag(s) pending.

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

Bug#1030309: kodi-game-libretro-bsnes-mercury-accuracy: Depends: libretro-bsnes-accuracy-balanced but it is not installable

[Adrian Bunk]

Package: kodi-game-libretro-bsnes-mercury-accuracy
Version: 094+git20220807-4
Severity: serious

The following packages have unmet dependencies:
 kodi-game-libretro-bsnes-mercury-accuracy : Depends: 
libretro-bsnes-accuracy-balanced but it is not installable


Was the dependency intended to be on libretro-bsnes-mercury-accuracy instead?

Processed: Re: Bug#1030220: xrayutilities: missing dependency on python3-h5py breaks armel tests

[Debian Bug Tracking System]

Processing control commands:

> reopen 1030220
Bug #1030220 {Done: Drew Parsons } [src:xrayutilities] 
xrayutilities: missing dependency on python3-h5py breaks armel tests
'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 h5py/3.7.0-4.

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

Bug#1030220: xrayutilities: missing dependency on python3-h5py breaks armel tests

[Drew Parsons]

Control: reopen 1030220

h5py 3.7.0-4 is uploaded fixing the source of the problem, but 
xrayutilities will need to be rebuilt to use the new pydist definitions.

Processed: retitle 1020435 ruby-prof: flaky tests cause random FTBFS

[Debian Bug Tracking System]

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

> retitle 1020435 ruby-prof: flaky tests cause random FTBFS
Bug #1020435 [src:ruby-prof] ruby-prof: FTBFS on ppc64el
Changed Bug title to 'ruby-prof: flaky tests cause random FTBFS' from 
'ruby-prof: FTBFS on ppc64el'.
> thanks
Stopping processing here.

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

Bug#1004806: marked as done (dolphin-emu: FTBFS with ffmpeg 5.0)

[Debian Bug Tracking System]

Your message dated Thu, 2 Feb 2023 15:45:37 +0100
with message-id 
and subject line Fixed in dolphin-emu 5.0-17995-1
has caused the Debian Bug report #1004806,
regarding dolphin-emu: FTBFS with ffmpeg 5.0
to be marked as done.

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

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


-- 
1004806: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004806
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dolphin-emu
Version: 5.0+dfsg-6
Severity: important
X-Debbugs-Cc: sramac...@debian.org
Usertags: ffmpeg5.0
Tags: sid bookworm ftbfs

dolphin-emu FTBFS with ffmpeg 5.0 in experimental:

[ 43%] Building CXX object 
Source/Core/VideoCommon/CMakeFiles/videocommon.dir/AVIDump.cpp.o
cd /<>/build/Source/Core/VideoCommon && /usr/lib/ccache/c++ 
-DDATA_DIR=\"/usr/share/games/dolphin-emu/\" -DHAVE_ALSA=1 -DHAVE_AO=1 
-DHAVE_BLUEZ=1 -DHAVE_LIBAV -DHAVE_LIBEVDEV=1 -DHAVE_LIBUDEV=1 -DHAVE_OPENAL=1 
-DHAVE_PORTAUDIO=1 -DHAVE_PULSEAUDIO=1 -DHAVE_WX=1 -DHAVE_X11=1 
-DHAVE_X11_XINPUT2=1 -DHAVE_XRANDR=1 -DUSE_ANALYTICS=1 -DUSE_MEMORYWATCHER=1 
-DUSE_PIPES=1 -DUSE_UPNP -DWXUSINGDLL -D_ARCH_64=1 -D_DEFAULT_SOURCE 
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_M_X86=1 -D_M_X86_64=1 
-D__LIBUSB__ -D__STDC_CONSTANT_MACROS -D__STDC_LIMIT_MACROS -D__WXGTK__ 
-I/usr/include/AL -I/usr/include/libevdev-1.0 -I/<>/Source/Core 
-I/<>/Externals/Bochs_disasm -I/<>/Externals/xxhash 
-I/usr/include/libpng16 -I/usr/include/soundtouch -I/usr/include/libusb-1.0 
-I/usr/include/miniupnpc -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 
-I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 
-I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gio-unix-2.0 
-I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/harfbuzz 
-I/usr/include/fribidi -I/usr/include/atk-1.0 -I/usr/include/pixman-1 
-I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-I/<>/build/Source/Core/Common -I/usr/src/gtest 
-I/usr/src/gtest/include -isystem 
/usr/lib/x86_64-linux-gnu/wx/include/gtk3-unicode-3.0 -isystem 
/usr/include/wx-3.0 -g -O2 -ffile-prefix-map=/<>=. 
-specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wtype-limits 
-Wsign-compare -Wignored-qualifiers -Wuninitialized -Wlogical-op -Wshadow 
-Winit-self -Wmissing-declarations -fvisibility-inlines-hidden 
-fvisibility=hidden -pthread   -msse2 -Wall -fno-strict-aliasing 
-fno-exceptions -std=c++1y -include 
'/<>/build/Source/CMakeFiles/pch.dir/pch.h' -MD -MT 
Source/Core/VideoCommon/CMakeFiles/videocommon.dir/AVIDump.cpp.o -MF 
CMakeFiles/videocommon.dir/AVIDump.cpp.o.d -o 
CMakeFiles/videocommon.dir/AVIDump.cpp.o -c 
/<>/Source/Core/VideoCommon/AVIDump.cpp
/<>/Source/Core/VideoCommon/VideoState.cpp: In function ‘void 
VideoCommon_Init()’:
/<>/Source/Core/VideoCommon/VideoState.cpp:71:15: warning: ‘void* 
memset(void*, int, size_t)’ clearing an object of non-trivial type ‘struct 
CPState’; use assignment or value-initialization instead [-Wclass-memaccess]
   71 | memset(_main_cp_state, 0, sizeof(g_main_cp_state));
  | ~~^~
In file included from 
/<>/Source/Core/VideoCommon/VideoState.cpp:11:
/<>/Source/Core/VideoCommon/CPMemory.h:246:8: note: ‘struct 
CPState’ declared here
  246 | struct CPState final
  |^~~
/<>/Source/Core/VideoCommon/VideoState.cpp:72:15: warning: ‘void* 
memset(void*, int, size_t)’ clearing an object of non-trivial type ‘struct 
CPState’; use assignment or value-initialization instead [-Wclass-memaccess]
   72 | memset(_preprocess_cp_state, 0, 
sizeof(g_preprocess_cp_state));
  | ~~^~
In file included from 
/<>/Source/Core/VideoCommon/VideoState.cpp:11:
/<>/Source/Core/VideoCommon/CPMemory.h:246:8: note: ‘struct 
CPState’ declared here
  246 | struct CPState final
  |^~~
/<>/Source/Core/VideoCommon/AVIDump.cpp: In function ‘void 
InitAVCodec()’:
/<>/Source/Core/VideoCommon/AVIDump.cpp:54:17: error: 
‘av_register_all’ was not declared in this scope
   54 | av_register_all();
  | ^~~
/<>/Source/Core/VideoCommon/AVIDump.cpp: In static member function 
‘static bool AVIDump::CreateFile()’:
/<>/Source/Core/VideoCommon/AVIDump.cpp:84:36: error: 
‘AVFormatContext’ {aka ‘struct AVFormatContext’} has no member named ‘filename’
   84 | 

Bug#894284: marked as done (android-platform-tools-base FTBFS with openjdk-9)

[Debian Bug Tracking System]

Your message dated Thu, 02 Feb 2023 14:38:54 +
with message-id 
and subject line Bug#894284: fixed in android-platform-tools-base 2.2.2-4
has caused the Debian Bug report #894284,
regarding android-platform-tools-base FTBFS with openjdk-9
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.)


-- 
894284: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894284
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: android-platform-tools-base
Version: 2.2.2-3
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/android-platform-tools-base.html

...
/build/1st/android-platform-tools-base-2.2.2/repository/src/main/java/com/android/repository/util/InstallerUtil.java:62:
 error: package javax.xml.bind is not visible
import javax.xml.bind.JAXBElement;
^
  (package javax.xml.bind is declared in module java.xml.bind, which is not in 
the module graph)
/build/1st/android-platform-tools-base-2.2.2/repository/src/main/java/com/android/repository/util/InstallerUtil.java:63:
 error: package javax.xml.bind is not visible
import javax.xml.bind.JAXBException;
^
  (package javax.xml.bind is declared in module java.xml.bind, which is not in 
the module graph)
/build/1st/android-platform-tools-base-2.2.2/repository/src/main/java/com/android/repository/api/RepoPackage.java:28:
 error: package javax.xml.bind.annotation is not visible
import javax.xml.bind.annotation.XmlTransient;
 ^
  (package javax.xml.bind.annotation is declared in module java.xml.bind, which 
is not in the module graph)
/build/1st/android-platform-tools-base-2.2.2/repository/src/main/java/com/android/repository/impl/meta/TypeDetails.java:21:
 error: package javax.xml.bind is not visible
import javax.xml.bind.JAXBElement;
^
  (package javax.xml.bind is declared in module java.xml.bind, which is not in 
the module graph)
/build/1st/android-platform-tools-base-2.2.2/repository/src/main/java/com/android/repository/impl/meta/TypeDetails.java:22:
 error: package javax.xml.bind.annotation is not visible
import javax.xml.bind.annotation.XmlTransient;
 ^
  (package javax.xml.bind.annotation is declared in module java.xml.bind, which 
is not in the module graph)
...
--- End Message ---
--- Begin Message ---
Source: android-platform-tools-base
Source-Version: 2.2.2-4
Done: Emmanuel Bourg 

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated 
android-platform-tools-base package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 02 Feb 2023 15:01:58 +0100
Source: android-platform-tools-base
Architecture: source
Version: 2.2.2-4
Distribution: unstable
Urgency: medium
Maintainer: Android Tools Maintainers 

Changed-By: Emmanuel Bourg 
Closes: 869286 894284 994093
Changes:
 android-platform-tools-base (2.2.2-4) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Kai-Chung Yan ]
   * Build with libjaxb-api-java
   * Migrate to `NamespaceContext` in JDK11
   * Replace sun.misc.BASE64Encoder with JDK8 Base64
   * Replace com.sun.org.apache.xml.internal.serialize with those in Xerces2
 .
   [ Hans-Christoph Steiner ]
   * Do not build jack/jill, they are unused and deprecated
   * Add debian/.gitlab-ci.yml
 .
   [ Emmanuel Bourg ]
   * Depend on libintellij-core-java and drop the embedded copy (Closes: 
#869286)
   * Fixed the compatibility with Gradle 4.4 (Closes: #994093)
   * Fixed the compatibility with Guava 26+
   * Depend on libeclipse-jdt-core-java instead of libecj-java
   * Added asm-util to the classpath of gradle-core
   * Added the --add-exports options required to build with Java 17
 (Closes: #894284)
Checksums-Sha1:
 3b00c56a1e8ff374eb4470e8ef0af10ffd40dd40 3756 
android-platform-tools-base_2.2.2-4.dsc
 a1f96969c94e5c982ac97cf24f55bd5fe29edd23 162736 
android-platform-tools-base_2.2.2-4.debian.tar.xz
 ce9b5d6bed73878cece0044114e250571720273d 18237 

Bug#994093: marked as done (libgradle-android-plugin-java: tries to use removed method setDependencyCacheDir())

[Debian Bug Tracking System]

Your message dated Thu, 02 Feb 2023 14:38:54 +
with message-id 
and subject line Bug#994093: fixed in android-platform-tools-base 2.2.2-4
has caused the Debian Bug report #994093,
regarding libgradle-android-plugin-java: tries to use removed method 
setDependencyCacheDir()
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.)


-- 
994093: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994093
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgradle-android-plugin-java
Version: 2.2.2-3
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: 
sascha-debian-bugs-libgradle-android-plugin-java-2021-09...@silbe.org

Dear Maintainer,

the Android Gradle Plugin version in sid (2.2.2-3) does not work with
the Gradle version in bullseye/bookworm/sid (4.4.1-13) because it still
tries to use the
com.android.build.gradle.tasks.factory.AndroidJavaCompile.setDependencyCacheDir()
method that got removed in Gradle 4.0.0 (commit
edadbed1378f439d31bb1d2a8c68c18365e0d1b0).

Upstream stopped using setDependencyCacheDir() in version 3.0.0 (commit
fde89448b47124a9b10c8ab13843c369525b9b8d). If upgrading AGP to that
version isn't an option it may be worth trying to backport the fix.

Example stacktrace:

=== Begin ===
16:33:15.998 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 
FAILURE: Build failed with an exception.
16:33:15.998 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 
16:33:15.998 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] * 
What went wrong:
16:33:15.998 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] A 
problem occurred configuring project ':app'.
16:33:15.998 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] > 
Failed to notify project evaluation listener.
16:33:15.998 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]   
 > 'void 
com.android.build.gradle.tasks.factory.AndroidJavaCompile.setDependencyCacheDir(java.io.File)'
16:33:15.998 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 
16:33:15.998 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] * 
Try:
16:33:15.998 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]  
Run with --scan to get full insights.
16:33:15.999 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 
16:33:15.999 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] * 
Exception is:
16:33:16.000 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter] 
org.gradle.api.ProjectConfigurationException: A problem occurred configuring 
project ':app'.
16:33:16.000 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]   
at 
org.gradle.configuration.project.LifecycleProjectEvaluator.addConfigurationFailure(LifecycleProjectEvaluator.java:94)
16:33:16.000 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]   
at 
org.gradle.configuration.project.LifecycleProjectEvaluator.notifyAfterEvaluate(LifecycleProjectEvaluator.java:89)
16:33:16.000 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]   
at 
org.gradle.configuration.project.LifecycleProjectEvaluator.doConfigure(LifecycleProjectEvaluator.java:70)
16:33:16.000 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]   
at 
org.gradle.configuration.project.LifecycleProjectEvaluator.access$100(LifecycleProjectEvaluator.java:34)
16:33:16.000 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]   
at 
org.gradle.configuration.project.LifecycleProjectEvaluator$ConfigureProject.run(LifecycleProjectEvaluator.java:110)
16:33:16.000 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]   
at 
org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:336)
16:33:16.000 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]   
at 
org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:328)
16:33:16.000 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]   
at 
org.gradle.internal.progress.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:199)
16:33:16.000 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]   
at 
org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:110)
16:33:16.001 [ERROR] [org.gradle.internal.buildevents.BuildExceptionReporter]   
at 

Bug#1030160: chromium: FTBFS on arm64/armhf in bullseye-security (V4L issues)

[Steinberg, Benjamin]

On Tue, 31 Jan 2023 13:35:49 -0500 Andres Salomon 
mailto:dilin...@queued.net>> wrote:
> Thanks! I forgot that it can only be enabled on sid when I merged the
> new release into bullseye. This will get fixed in the next security
> upload.

Thanks, Andres. Just to confirm, does

> This will get fixed in the next security upload.

mean that bullseye-security is not going to contain arm64 and armhf packages 
for Chromium 109.0.5414.119-1~deb11u1? I ask because in our application, I keep 
Chromium versions up to date and synchronized between deployments (amd64 
machines) and developer machines (M1 Macs). If the arm64 package for this 
version won’t be present, I’ll wait for the next version, presumably 
110.0.5481.77.

Bug#984866: unavailable packages / CVE

[matthias . geiger1024]

Tags: pending


Once r2d2 (in NEW atm) enters the archive I can upload diesel-derives 2.0.0 and 
diesel 2.0.0 which will fix this.

Regards,

Matthias Geiger (werdahias)

Bug#1030306: simple-scan: Not a JPEG file: starts with 0x00 0x00

[Janusz S . Bień]

Package: simple-scan
Version: 3.38.1-1
Severity: grave
X-Debbugs-Cc: none, Janusz S. Bień 

Dear Maintainer,

-- Package-specific info:
-- BEGIN ATTACHMENTS --
/tmp/tmp.dgtNgi4r0Z/logfile.user
/tmp/tmp.dgtNgi4r0Z/scanimage.user
/tmp/tmp.dgtNgi4r0Z/lsusb.user
-- END ATTACHMENTS --

After I switched Samsung Xpress M2070FW from USB to W-Fi practically every 
attempt to scan ends
with this bug. Scanning with GIMP and SANE still works.

I will appreciate your help.

Regards - Janusz

-- System Information:
Debian Release: 11.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'unstable'), (500, 'stable'), (100, 'bullseye-fasttrack'), (100, 
'bullseye-backports-staging')
Architecture: amd64 (x86_64)

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

Versions of packages simple-scan depends on:
ii  dbus-user-session [default-dbus-session-bus]  1.12.24-0+deb11u1
ii  dbus-x11 [dbus-session-bus]   1.12.24-0+deb11u1
ii  dconf-gsettings-backend [gsettings-backend]   0.38.0-2
ii  libc6 2.31-13+deb11u5
ii  libcairo2 1.16.0-5
ii  libcolord21.4.5-3
ii  libgdk-pixbuf2.0-02.40.2-2
ii  libglib2.0-0  2.66.8-1
ii  libgtk-3-03.24.24-4+deb11u2
ii  libgusb2  0.3.5-1
ii  libpackagekit-glib2-181.2.2-2
ii  libsane1  1.0.31-4.1
ii  libwebp6  0.6.1-2.1
ii  libwebpmux3   0.6.1-2.1
ii  xdg-utils 1.1.3-4.1
ii  zlib1g1:1.2.11.dfsg-2+deb11u2

simple-scan recommends no packages.

simple-scan suggests no packages.

-- no debconf information

-- 
 ,   
Janusz S. Bien
emeryt (emeritus)
https://sites.google.com/view/jsbien

Bug#1005165: fwupd-amd64-signed uninstallable for a few weeks now

[Paul Gevers]

Hi,

On Tue, 08 Feb 2022 11:11:35 +0100 Bastian Venthur  
wrote:

Package: fwupd-amd64-signed
Version: 1.5.7+5
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: vent...@debian.org

Dear Maintainer,

fwupd-amd64-signed is uninstallable as it depends on fwupd < 1.5.7-6, however
the current version in unstable is 1.7.4-1.


This bug is already marked fixed, but not closed. I think it can be 
closed, right?


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1029621: marked as done (falkon fails to install)

[Debian Bug Tracking System]

Your message dated Thu, 02 Feb 2023 13:34:25 +
with message-id 
and subject line Bug#1029621: fixed in falkon 22.12.1-2
has caused the Debian Bug report #1029621,
regarding falkon fails to install
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.)


-- 
1029621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029621
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: falkon
Version: 22.12.1-1
Severity: serious

https://piuparts.debian.org/sid/fail/falkon_22.12.1-1.log

...
Setting up falkon (22.12.1-1) ...
  update-alternatives: using /usr/bin/falkon to provide /usr/bin/x-www-browser 
(x-www-browser) in auto mode
  mkdir: cannot create directory '/usr/share/qt5/qtwebengine_dictionaries': 
File exists
  dpkg: error processing package falkon (--configure):
   installed falkon package post-installation script subprocess returned error 
exit status 1
  Processing triggers for libc-bin (2.36-8) ...
  Errors were encountered while processing:
   falkon
  E: Sub-process /usr/bin/dpkg returned an error code (1)
--- End Message ---
--- Begin Message ---
Source: falkon
Source-Version: 22.12.1-2
Done: Georges Khaznadar 

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

Debian distribution maintenance software
pp.
Georges Khaznadar  (supplier of updated falkon 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: Wed, 25 Jan 2023 13:48:20 +0100
Source: falkon
Architecture: source
Version: 22.12.1-2
Distribution: unstable
Urgency: medium
Maintainer: Georges Khaznadar 
Changed-By: Georges Khaznadar 
Closes: 1029621 1030183
Changes:
 falkon (22.12.1-2) unstable; urgency=medium
 .
   [ Adrian Bunk ]
   * Architecture: any
 .
   [ Georges Khaznadar ]
   * modified falkon.postinst to manage /usr/share/qt5/qtwebengine_dictionaries
 more smoothly. Closes: #1029621, and Closes: #1030183
Checksums-Sha1:
 f4619100cc9532fc3440d93ce83f7fd130cb91aa 2258 falkon_22.12.1-2.dsc
 7067ce9fb528a1a85a96dc4f088b842b2bd7 189104 falkon_22.12.1-2.debian.tar.xz
 16f02d8ae551a94a4fa1df7cc70b8e7455a33a01 19788 falkon_22.12.1-2_amd64.buildinfo
Checksums-Sha256:
 d2b9b8a7b938e25d4f88ac43fdbd5a073965f6477fa6b5cbacbc5905b0cec2e2 2258 
falkon_22.12.1-2.dsc
 d717ca119c66abe30e673df7d310c3832458ef050352dc88375f0cc22248bdf4 189104 
falkon_22.12.1-2.debian.tar.xz
 f0486f6eda5b6d8cb35115c80a65063c064c1cdbc859fbc05a3a79252b868bf1 19788 
falkon_22.12.1-2_amd64.buildinfo
Files:
 ad1a87553c4cb97fb7e2ff11d74804d0 2258 web optional falkon_22.12.1-2.dsc
 ed3fea80f90de2888d8565b145b475f4 189104 web optional 
falkon_22.12.1-2.debian.tar.xz
 0c5c3d014a9c7aa51332a19ac0ef971e 19788 web optional 
falkon_22.12.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEM0CzZP9nFT+3zK6FHCgWkHE2rjkFAmPbtm4ACgkQHCgWkHE2
rjnXGg/9GLa2aUwjmSGTDQRtBL4ILYaKJgNNZYvHf0WNFGcQilGp2+99IOnnXlt5
30MetKQ87q0aywboZd4b5Cugwc7HuDebFl0D4ShGD9TGVQXkoF/qWUIhYVDQfELV
1fxCiVNlV7/1qJgE+NeEFe0lXaFdVLY7yZ4WJRuUJI7ItiMTzyn3+wYvcJVnwLNn
4AJZV3QzparnaE3kdZ3meSj2SqNzRjrZCKaMsMXZXqJCoDZqdfr5Ojv1mmvc2x4n
XRC051toFGOx6SsTXOdbBfL9SH1pmeK4tts5kfbX3vnrk6SXh4wdQwIvbYDYUqOG
MJCJum9PD26MF6ebsR7772xoJCkIaJcswjqh6/3MhYkHOww5y0zSP7Gc9EPpl9q1
Dawd13R7OsvGxy8dEPp+OMkaCH0FwZafCl+sQ9XLkSt5NbRc4TwdoPUoXc3kMsiP
I38otKJRBH4P0Ilhj+fpFgcDszImFTE9Fbcodu6UVIQQq3TUmNEi0U9WAu5GRVP1
3bBUfYQ6b1qDzJwmv/ITX5Xa2vqGlIxWN0F3KuZmfBoHg258nyBT+7sN6+a9SJ4h
ce4F7p4RwFCVIbm7VFEfaVPVnNS6xysP07oM3sYpOa6htuvYMtin5QaeXEAo5bHy
v1bVyMv+C1BTJECIgHxaT+/T76s0PilNwgusScdZ/AUTIWmC1SY=
=xm9e
-END PGP SIGNATURE End Message ---

Processed: yade: FTBFS: ImportError: cannot import name 'PY3' from 'IPython.utils.py3compat' (/usr/lib/python3/dist-packages/IPython/utils/py3compat.py)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #1022735 {Done: Anton Gladky } [src:yade] yade: FTBFS: 
ImportError: cannot import name 'PY3' from 'IPython.utils.py3compat' 
(/usr/lib/python3/dist-packages/IPython/utils/py3compat.py)
'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 yade/2022.01a-13.

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

Bug#1022735: yade: FTBFS: ImportError: cannot import name 'PY3' from 'IPython.utils.py3compat' (/usr/lib/python3/dist-packages/IPython/utils/py3compat.py)

[Graham Inggs]

Control: reopen -1

yade 2022.01a-13 seems to fail in the same way

Bug#1020138: marked as done (mate-hud: FTBFS: make[1]: *** [debian/rules:13: override_dh_auto_clean] Error 25)

[Debian Bug Tracking System]

Your message dated Thu, 02 Feb 2023 13:08:21 +
with message-id 
and subject line Bug#1020138: fixed in mate-hud 22.10.3-1
has caused the Debian Bug report #1020138,
regarding mate-hud: FTBFS: make[1]: *** [debian/rules:13: 
override_dh_auto_clean] 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.)


-- 
1020138: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020138
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mate-hud
Version: 22.04.4-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 '/<>'
> rm -Rf mate_hud.egg-info/
> # dh_auto_clean with pybuild/distutils only works if setup.py is
> # present
> if [ -f setup.py ]; then \
>   dh_auto_clean; \
> fi
> I: pybuild base:240: python3.10 setup.py clean 
> /usr/lib/python3/dist-packages/setuptools/dist.py:530: UserWarning: 
> Normalizing '22.04.4' to '22.4.4'
>   warnings.warn(tmpl.format(**locals()))
> error: Multiple top-level packages discovered in a flat-layout: ['usr', 
> 'debian'].
> 
> To avoid accidental inclusion of unwanted files or directories,
> setuptools will not proceed with this build.
> 
> If you are trying to create a single distribution with multiple packages
> on purpose, you should not rely on automatic discovery.
> Instead, consider the following options:
> 
> 1. set up custom discovery (`find` directive with `include` or `exclude`)
> 2. use a `src-layout`
> 3. explicitly set `py_modules` or `packages` with a list of names
> 
> To find more information, look for "package discovery" on setuptools docs.
> 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[1]: *** [debian/rules:13: override_dh_auto_clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2022/09/17/mate-hud_22.04.4-1_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 ---
Source: mate-hud
Source-Version: 22.10.3-1
Done: Mike Gabriel 

We believe that the bug you reported is fixed in the latest version of
mate-hud, 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.
Mike Gabriel  (supplier of updated mate-hud package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 16 Oct 2022 22:20:08 +0200
Source: mate-hud
Architecture: source
Version: 22.10.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian+Ubuntu MATE Packaging Team 
Changed-By: Mike Gabriel 
Closes: 1020138
Changes:
 mate-hud (22.10.3-1) unstable; urgency=medium
 .
   [ Martin Wimpress ]
   * New upstream release.
   * debian/control:
 + Add to D (mate-hud): python3-pyinotify.
 + Bump Standards-Version: to 4.6.2. No changes needed.
   * debian/copyright:
 + Update copyright attributions.
   * debian/patches:
 + Add 2001_fix-ftbfs-due-to-multi-toplevel-packages.patch.
   (Closes: #1020138).
   * debian/watch:
 + Switch to version 4.
Checksums-Sha1:
 2c3f065ff1b2057ce2946920fa7005ef181e07f9 2081 mate-hud_22.10.3-1.dsc
 82e3c26a2230066dbde189a5161121e773825a5a 151925 mate-hud_22.10.3.orig.tar.gz
 

Bug#976530: marked as done (dolphin-emu: FTBFS: tests failed)

[Debian Bug Tracking System]

Your message dated Thu, 02 Feb 2023 13:05:45 +
with message-id 
and subject line Bug#976530: fixed in dolphin-emu 5.0-17995-1
has caused the Debian Bug report #976530,
regarding dolphin-emu: 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.)


-- 
976530: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=976530
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dolphin-emu
Version: 5.0+dfsg-6
Severity: serious
Justification: FTBFS on arm64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20201205 ftbfs-bullseye

Hi,

During a rebuild of all packages in sid, your package failed to build
on arm64 (I don't know if it also fails on amd64).

Relevant part (hopefully):
> make[5]: Entering directory '/<>/build'
> /usr/bin/ctest
> Test project /<>/build
>   Start  1: BitFieldTest
>  1/14 Test  #1: BitFieldTest .   Passed0.00 sec
>   Start  2: BitSetTest
>  2/14 Test  #2: BitSetTest ...   Passed0.00 sec
>   Start  3: BlockingLoopTest
>  3/14 Test  #3: BlockingLoopTest .   Passed0.19 sec
>   Start  4: BusyLoopTest
>  4/14 Test  #4: BusyLoopTest .   Passed1.07 sec
>   Start  5: CommonFuncsTest
>  5/14 Test  #5: CommonFuncsTest ..   Passed0.00 sec
>   Start  6: EventTest
>  6/14 Test  #6: EventTest    Passed0.77 sec
>   Start  7: FifoQueueTest
>  7/14 Test  #7: FifoQueueTest    Passed0.03 sec
>   Start  8: FixedSizeQueueTest
>  8/14 Test  #8: FixedSizeQueueTest ...   Passed0.00 sec
>   Start  9: FlagTest
>  9/14 Test  #9: FlagTest .   Passed0.16 sec
>   Start 10: MathUtilTest
> 10/14 Test #10: MathUtilTest .   Passed0.11 sec
>   Start 11: x64EmitterTest
> 11/14 Test #11: x64EmitterTest ...   Passed0.07 sec
>   Start 12: MMIOTest
> 12/14 Test #12: MMIOTest .   Passed0.50 sec
>   Start 13: PageFaultTest
> 13/14 Test #13: PageFaultTest    Passed0.07 sec
>   Start 14: VertexLoaderTest
> 14/14 Test #14: VertexLoaderTest .***Failed3.64 sec
> Running main() from /usr/src/gtest/src/gtest_main.cc
> [==] Running 113 tests from 4 test suites.
> [--] Global test environment set-up.
> [--] 1 test from VertexLoaderUID
> [ RUN  ] VertexLoaderUID.UniqueEnough
> [   OK ] VertexLoaderUID.UniqueEnough (0 ms)
> [--] 1 test from VertexLoaderUID (0 ms total)
> 
> [--] 2 tests from VertexLoaderTest
> [ RUN  ] VertexLoaderTest.PositionIndex16FloatXY
> [   OK ] VertexLoaderTest.PositionIndex16FloatXY (4 ms)
> [ RUN  ] VertexLoaderTest.LargeFloatVertexSpeed
> [   OK ] VertexLoaderTest.LargeFloatVertexSpeed (282 ms)
> [--] 2 tests from VertexLoaderTest (286 ms total)
> 
> [--] 90 tests from AllCombinations/VertexLoaderParamTest
> [ RUN  ] AllCombinations/VertexLoaderParamTest.PositionAll/0
> [   OK ] AllCombinations/VertexLoaderParamTest.PositionAll/0 (1 ms)
> [ RUN  ] AllCombinations/VertexLoaderParamTest.PositionAll/1
> [   OK ] AllCombinations/VertexLoaderParamTest.PositionAll/1 (1 ms)
> [ RUN  ] AllCombinations/VertexLoaderParamTest.PositionAll/2
> [   OK ] AllCombinations/VertexLoaderParamTest.PositionAll/2 (0 ms)
> [ RUN  ] AllCombinations/VertexLoaderParamTest.PositionAll/3
> [   OK ] AllCombinations/VertexLoaderParamTest.PositionAll/3 (1 ms)
> [ RUN  ] AllCombinations/VertexLoaderParamTest.PositionAll/4
> [   OK ] AllCombinations/VertexLoaderParamTest.PositionAll/4 (1 ms)
> [ RUN  ] AllCombinations/VertexLoaderParamTest.PositionAll/5
> [   OK ] AllCombinations/VertexLoaderParamTest.PositionAll/5 (1 ms)
> [ RUN  ] AllCombinations/VertexLoaderParamTest.PositionAll/6
> [   OK ] AllCombinations/VertexLoaderParamTest.PositionAll/6 (0 ms)
> [ RUN  ] AllCombinations/VertexLoaderParamTest.PositionAll/7
> [   OK ] AllCombinations/VertexLoaderParamTest.PositionAll/7 (1 ms)
> [ RUN  ] AllCombinations/VertexLoaderParamTest.PositionAll/8
> [   OK ] AllCombinations/VertexLoaderParamTest.PositionAll/8 (1 ms)
> [ RUN  ] AllCombinations/VertexLoaderParamTest.PositionAll/9
> [   OK ] AllCombinations/VertexLoaderParamTest.PositionAll/9 (1 ms)
> [ RUN  ] AllCombinations/VertexLoaderParamTest.PositionAll/10
> [   OK ] AllCombinations/VertexLoaderParamTest.PositionAll/10 (0 ms)
> [ RUN   

Bug#1030274: marked as done (Provide PyDist overrides for h5py?)

[Debian Bug Tracking System]

Your message dated Thu, 02 Feb 2023 13:06:16 +
with message-id 
and subject line Bug#1030274: fixed in h5py 3.7.0-4
has caused the Debian Bug report #1030274,
regarding Provide PyDist overrides for h5py?
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.)


-- 
1030274: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030274
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xrayutilities
Version: 1.7.4-1
Severity: serious
Justification: debci

python3-xrayutilities has an inconsistent Dependency on h5py
It declares python3-h5py-serial [alpha, hppa, m68k, sparc64, x32], in
other words is not declared for most architectures.

But xrayutilities needs h5py in io/helper.py, so the missing
dependency of python3-h5py cases armel tests to fail.

The failure is triggered by scipy 1.10.  Other arches pass.  I think
that they are passing due to an indirect dependency from some other
package, which isn't applied to armel.

Since python3-xrayutilities uses h5py directly, it needs
Depends: python3-h5py

xrayutilities does have Build-Depends: python3-h5py. Evidentally
dh-python3 isn't able to determine the correct dependency for h5py
(likely it gets confused by python3-h5py-serial).  Until that's fixed,
python3-xrayutilities should declare 
Depends: python3-h5py
explicitly.
--- End Message ---
--- Begin Message ---
Source: h5py
Source-Version: 3.7.0-4
Done: Drew Parsons 

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

Debian distribution maintenance software
pp.
Drew Parsons  (supplier of updated h5py package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 02 Feb 2023 13:06:51 +0100
Source: h5py
Architecture: source
Version: 3.7.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Drew Parsons 
Closes: 1025575 1026041 1030220 1030274
Changes:
 h5py (3.7.0-4) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Drew Parsons ]
   * use pydist files so that dh_python3 uses the generic python3-h5py
 package as the h5py python package dependency for both
 python3-h5py-serial and python3-h5py-mpi.
 Closes: #1025575, #1030220, #1030274.
   * Standards-Version: 4.6.2
 .
   [ Helmut Grohne ]
   * Reduce Build-Depends: (Closes: #1026041)
 + Declaratively request debhelper addons.
 + Clean docs without requiring sphinx.
 + Move sphinx dependencies to B-D-I.
 + Annotate pytest dependencies .
 + Multiarchify python Build-Depends.
   * Don't hard code the build architecture pkg-config.
Checksums-Sha1:
 1c84504fde1e832ea07fe3168655aa7176018769 2863 h5py_3.7.0-4.dsc
 dc13f8fe7005a062d63dab8ad2d716e078dbd908 19512 h5py_3.7.0-4.debian.tar.xz
Checksums-Sha256:
 667be1968859002a47e69f954061d7919e037d073dab291cab517dda5fd69eb0 2863 
h5py_3.7.0-4.dsc
 65d5b211f2438f9a2c5b79655141616d463217a6d97fac232f10403617eeb1d3 19512 
h5py_3.7.0-4.debian.tar.xz
Files:
 8fc0446f176b219285e0aa0e1cdea3d1 2863 python optional h5py_3.7.0-4.dsc
 ab71f6f732788f35b2e7b0a9dfc3ea3d 19512 python optional 
h5py_3.7.0-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAmPbroIACgkQVz7x5L1a
AfqhTg/9GVkZsvrzVx7dlBHD6hXzWlSXXlYJrRur3V7UUpXy36XreQQthBaGHKaI
AY6wwsAt7GUcAvm9pLHRyuliYXjIT2PChCuq+xeTA64uj3EoN7Tpo65hiNhAvrm1
iY54tt+GDgaVHCQMVwR2JCxfN83TpcuVm0wgbMI2a9Yty7yddYJdk+YdTkAMwYEf
xcenVY7SZUM9uVis790UNuotPKF1Lryvq6ZmrSxsa2Y3VkXUYy3oD1JZqhX0Grvp
BXW9GYiK4KAHw2wagkkNFQQn5pbxrSXQMr27AFhtE+/hYxc37boVjT1+3XATpFvI
y5/uXylL/EcQeCUasEbmVBvZDGLRR+XNxRgtoLP2+lL4nvjmYt3QhwqS6A/jhppB
0MynakkWrjFlHfbgt7VROfFxpYgLjhd3BQt30/vqLQ2uRHcdL5TG5c4dptxIurAx
rXiV+POPC4FDJl/4g2g+CDfZfzcUGALasLISklaiUeovjQcjk3ge95G4Z+oTwpso
CiaKa3EDyCI/WjqbfAQc/Pg+/yNKINkPSftiSQtvKOt1uClaliwYDUNzoeyboR6F
YxOyE3LFICqHSNWlS8zOS+KNITKBuJtbjCrhjmb0UiGmtPhj5JCjpyeaaUkiSanx
ZR4qBZzCTUx2Veh/JpXNlYBxYOjR6F76ZpyDoQ364yGGZuXyxms=
=2U6N
-END PGP SIGNATURE End Message ---

Bug#1030220: marked as done (xrayutilities: missing dependency on python3-h5py breaks armel tests)

[Debian Bug Tracking System]

Your message dated Thu, 02 Feb 2023 13:06:16 +
with message-id 
and subject line Bug#1030220: fixed in h5py 3.7.0-4
has caused the Debian Bug report #1030220,
regarding xrayutilities: missing dependency on python3-h5py breaks armel tests
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.)


-- 
1030220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030220
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xrayutilities
Version: 1.7.4-1
Severity: serious
Justification: debci

python3-xrayutilities has an inconsistent Dependency on h5py
It declares python3-h5py-serial [alpha, hppa, m68k, sparc64, x32], in
other words is not declared for most architectures.

But xrayutilities needs h5py in io/helper.py, so the missing
dependency of python3-h5py cases armel tests to fail.

The failure is triggered by scipy 1.10.  Other arches pass.  I think
that they are passing due to an indirect dependency from some other
package, which isn't applied to armel.

Since python3-xrayutilities uses h5py directly, it needs
Depends: python3-h5py

xrayutilities does have Build-Depends: python3-h5py. Evidentally
dh-python3 isn't able to determine the correct dependency for h5py
(likely it gets confused by python3-h5py-serial).  Until that's fixed,
python3-xrayutilities should declare 
Depends: python3-h5py
explicitly.
--- End Message ---
--- Begin Message ---
Source: h5py
Source-Version: 3.7.0-4
Done: Drew Parsons 

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

Debian distribution maintenance software
pp.
Drew Parsons  (supplier of updated h5py package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 02 Feb 2023 13:06:51 +0100
Source: h5py
Architecture: source
Version: 3.7.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Drew Parsons 
Closes: 1025575 1026041 1030220 1030274
Changes:
 h5py (3.7.0-4) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Drew Parsons ]
   * use pydist files so that dh_python3 uses the generic python3-h5py
 package as the h5py python package dependency for both
 python3-h5py-serial and python3-h5py-mpi.
 Closes: #1025575, #1030220, #1030274.
   * Standards-Version: 4.6.2
 .
   [ Helmut Grohne ]
   * Reduce Build-Depends: (Closes: #1026041)
 + Declaratively request debhelper addons.
 + Clean docs without requiring sphinx.
 + Move sphinx dependencies to B-D-I.
 + Annotate pytest dependencies .
 + Multiarchify python Build-Depends.
   * Don't hard code the build architecture pkg-config.
Checksums-Sha1:
 1c84504fde1e832ea07fe3168655aa7176018769 2863 h5py_3.7.0-4.dsc
 dc13f8fe7005a062d63dab8ad2d716e078dbd908 19512 h5py_3.7.0-4.debian.tar.xz
Checksums-Sha256:
 667be1968859002a47e69f954061d7919e037d073dab291cab517dda5fd69eb0 2863 
h5py_3.7.0-4.dsc
 65d5b211f2438f9a2c5b79655141616d463217a6d97fac232f10403617eeb1d3 19512 
h5py_3.7.0-4.debian.tar.xz
Files:
 8fc0446f176b219285e0aa0e1cdea3d1 2863 python optional h5py_3.7.0-4.dsc
 ab71f6f732788f35b2e7b0a9dfc3ea3d 19512 python optional 
h5py_3.7.0-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAmPbroIACgkQVz7x5L1a
AfqhTg/9GVkZsvrzVx7dlBHD6hXzWlSXXlYJrRur3V7UUpXy36XreQQthBaGHKaI
AY6wwsAt7GUcAvm9pLHRyuliYXjIT2PChCuq+xeTA64uj3EoN7Tpo65hiNhAvrm1
iY54tt+GDgaVHCQMVwR2JCxfN83TpcuVm0wgbMI2a9Yty7yddYJdk+YdTkAMwYEf
xcenVY7SZUM9uVis790UNuotPKF1Lryvq6ZmrSxsa2Y3VkXUYy3oD1JZqhX0Grvp
BXW9GYiK4KAHw2wagkkNFQQn5pbxrSXQMr27AFhtE+/hYxc37boVjT1+3XATpFvI
y5/uXylL/EcQeCUasEbmVBvZDGLRR+XNxRgtoLP2+lL4nvjmYt3QhwqS6A/jhppB
0MynakkWrjFlHfbgt7VROfFxpYgLjhd3BQt30/vqLQ2uRHcdL5TG5c4dptxIurAx
rXiV+POPC4FDJl/4g2g+CDfZfzcUGALasLISklaiUeovjQcjk3ge95G4Z+oTwpso
CiaKa3EDyCI/WjqbfAQc/Pg+/yNKINkPSftiSQtvKOt1uClaliwYDUNzoeyboR6F
YxOyE3LFICqHSNWlS8zOS+KNITKBuJtbjCrhjmb0UiGmtPhj5JCjpyeaaUkiSanx
ZR4qBZzCTUx2Veh/JpXNlYBxYOjR6F76ZpyDoQ364yGGZuXyxms=
=2U6N
-END PGP SIGNATURE End Message ---

Bug#1030184: marked as done (ezquake FTBFS)

[Debian Bug Tracking System]

Your message dated Thu, 02 Feb 2023 13:06:03 +
with message-id 
and subject line Bug#1030184: fixed in ezquake 3.6.1-1.1
has caused the Debian Bug report #1030184,
regarding ezquake FTBFS
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.)


-- 
1030184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030184
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ezquake
Version: 3.6.1-1
Severity: serious
Tags: ftbfs

Hi,

ezquake fails to build from source on the buildds.

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

(log eg 
https://buildd.debian.org/status/fetch.php?pkg=ezquake=amd64=3.6.1-1=1674575852=0)
...
FAILED: ezquake.p/common.c.o 
cc -Iezquake.p -I. -I.. -I/usr/include/x86_64-linux-gnu -I/usr/include/SDL2 
-I/usr/include/opus -I/usr/include/libpng16 -I/usr/include/minizip 
-fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -Werror -Wno-deprecated-declarations 
-Wno-misleading-indentation -Wno-format-truncation -Wno-unused-function 
'-DBUILD_DATE="Sun, 22 Jan 2023 20:25:58 +"' -Wdate-time 
-D_FORTIFY_SOURCE=2 -pthread -D_REENTRANT -DREVISION=666 '-DVERSION="r666"' 
-DNDEBUG -DJSS_CAM -DUSE_PR2 -DWITH_NQPROGS -DUSE_SDL2 -DWITH_ZIP 
-Wno-strict-aliasing -Wno-int-to-pointer-cast -Wno-pointer-to-int-cast -msse2 
-DWITH_PNG -D__Q_PNG14__ -DWITH_JPEG -DWITH_SPEEX -DWITH_ZLIB 
-DX11_GAMMA_WORKAROUND -DRENDERER_OPTION_CLASSIC_OPENGL 
-DRENDERER_OPTION_MODERN_OPENGL -MD -MQ ezquake.p/common.c.o -MF 
ezquake.p/common.c.o.d -o ezquake.p/common.c.o -c ../common.c
../common.c: In function ‘COM_WriteToUniqueTempFile’:
../common.c:429:17: error: ignoring return value of ‘write’ declared with 
attribute ‘warn_unused_result’ [-Werror=unused-result]
  429 | write(fd, buffer, bytes);
  | ^~~~
cc1: all warnings being treated as errors
[128/384] cc -Iezquake.p -I. -I.. -I/usr/include/x86_64-linux-gnu 
-I/usr/include/SDL2 -I/usr/include/opus -I/usr/include/libpng16 
-I/usr/include/minizip -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall 
-Winvalid-pch -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -Werror 
-Wno-deprecated-declarations -Wno-misleading-indentation -Wno-format-truncation 
-Wno-unused-function '-DBUILD_DATE="Sun, 22 Jan 2023 20:25:58 +"' 
-Wdate-time -D_FORTIFY_SOURCE=2 -pthread -D_REENTRANT -DREVISION=666 
'-DVERSION="r666"' -DNDEBUG -DJSS_CAM -DUSE_PR2 -DWITH_NQPROGS -DUSE_SDL2 
-DWITH_ZIP -Wno-strict-aliasing -Wno-int-to-pointer-cast 
-Wno-pointer-to-int-cast -msse2 -DWITH_PNG -D__Q_PNG14__ -DWITH_JPEG 
-DWITH_SPEEX -DWITH_ZLIB -DX11_GAMMA_WORKAROUND 
-DRENDERER_OPTION_CLASSIC_OPENGL -DRENDERER_OPTION_MODERN_OPENGL -MD -MQ 
ezquake.p/com_msg.c.o -MF ezquake.p/com_msg.c.o.d -o ezquake.p/com_msg.c.o -c 
../com_msg.c
[129/384] cc -Iezquake.p -I. -I.. -I/usr/include/x86_64-linux-gnu 
-I/usr/include/SDL2 -I/usr/include/opus -I/usr/include/libpng16 
-I/usr/include/minizip -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall 
-Winvalid-pch -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -Werror 
-Wno-deprecated-declarations -Wno-misleading-indentation -Wno-format-truncation 
-Wno-unused-function '-DBUILD_DATE="Sun, 22 Jan 2023 20:25:58 +"' 
-Wdate-time -D_FORTIFY_SOURCE=2 -pthread -D_REENTRANT -DREVISION=666 
'-DVERSION="r666"' -DNDEBUG -DJSS_CAM -DUSE_PR2 -DWITH_NQPROGS -DUSE_SDL2 
-DWITH_ZIP -Wno-strict-aliasing -Wno-int-to-pointer-cast 
-Wno-pointer-to-int-cast -msse2 -DWITH_PNG -D__Q_PNG14__ -DWITH_JPEG 
-DWITH_SPEEX -DWITH_ZLIB -DX11_GAMMA_WORKAROUND 
-DRENDERER_OPTION_CLASSIC_OPENGL -DRENDERER_OPTION_MODERN_OPENGL -MD -MQ 
ezquake.p/config_manager.c.o -MF ezquake.p/config_manager.c.o.d -o 
ezquake.p/config_manager.c.o -c ../config_manager.c
[130/384] cc -Iezquake.p -I. -I.. -I/usr/include/x86_64-linux-gnu 
-I/usr/include/SDL2 -I/usr/include/opus -I/usr/include/libpng16 
-I/usr/include/minizip -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall 
-Winvalid-pch -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -Werror 
-Wno-deprecated-declarations -Wno-misleading-indentation -Wno-format-truncation 
-Wno-unused-function '-DBUILD_DATE="Sun, 22 Jan 2023 20:25:58 +"' 
-Wdate-time -D_FORTIFY_SOURCE=2 -pthread -D_REENTRANT -DREVISION=666 
'-DVERSION="r666"' -DNDEBUG -DJSS_CAM -DUSE_PR2 -DWITH_NQPROGS -DUSE_SDL2 

Bug#1025798: marked as done (dolphin-emu: depends on obsolete packages libmbedcrypto3, libmbedtls12, libmbedx509-0)

[Debian Bug Tracking System]

Your message dated Thu, 02 Feb 2023 13:05:45 +
with message-id 
and subject line Bug#1025798: fixed in dolphin-emu 5.0-17995-1
has caused the Debian Bug report #1025798,
regarding dolphin-emu: depends on obsolete packages libmbedcrypto3, 
libmbedtls12, libmbedx509-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.)


-- 
1025798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025798
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dolphin-emu
Version: 5.0+dfsg-6
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

Package dolphin-emu depends on obsolete packages libmbedcrypto3,
libmbedtls12 and libmbedx509-0, making it impossible to install.

Cheers,


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

Kernel: Linux 6.0.0-5-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to fr_FR.utf8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages dolphin-emu depends on:
ii  dolphin-emu-data  5.0+dfsg-6
ii  libao41.2.2+20180113-1.1
ii  libasound21.2.8-1
ii  libavcodec58  7:4.4.2-1+b3
ii  libavformat58 7:4.4.2-1+b3
ii  libavutil56   7:4.4.2-1+b3
ii  libbluetooth3 5.66-1
ii  libc6 2.36-6
ii  libcurl3-gnutls   7.86.0-2
ii  libenet7  1.3.13+ds-1
ii  libevdev2 1.13.0+dfsg-1
ii  libgcc-s1 [libgcc1]   12.2.0-9
ii  libgl11.5.0-1
ii  libglib2.0-0  2.74.2-1
ii  libgtk-3-03.24.35-2
ii  liblzo2-2 2.10-2
ii  libmbedcrypto32.16.11-0.3
ii  libmbedtls12  2.16.11-0.3
ii  libmbedx509-0 2.16.11-0.3
ii  libminiupnpc172.2.3-1+b1
ii  libopenal11:1.19.1-2
ii  libpng16-16   1.6.39-2
ii  libportaudio2 19.6.0-1.2
ii  libpulse0 16.1+dfsg1-2+b1
ii  libsfml-network2.52.5.1+dfsg-2+b2
ii  libsfml-system2.5 2.5.1+dfsg-2+b2
ii  libsoil1  1.07~20080707.dfsg-4
ii  libsoundtouch12.3.2+ds1-1
ii  libstdc++612.2.0-9
ii  libswscale5   7:4.4.2-1+b3
ii  libudev1  252.2-1
ii  libusb-1.0-0  2:1.0.26-1
ii  libwxbase3.0-0v5  3.0.5.1+dfsg-5
ii  libwxgtk3.0-gtk3-0v5  3.0.5.1+dfsg-5
ii  libx11-6  2:1.8.1-2
ii  libxi62:1.8-1+b1
ii  libxrandr22:1.5.2-2+b1
ii  zlib1g1:1.2.11.dfsg-4.1

dolphin-emu recommends no packages.

dolphin-emu suggests no packages.

-- no debconf information

-- 
Sylvain BOILARD
--- End Message ---
--- Begin Message ---
Source: dolphin-emu
Source-Version: 5.0-17995-1
Done: Jordi Mallach 

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

Debian distribution maintenance software
pp.
Jordi Mallach  (supplier of updated dolphin-emu package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 02 Feb 2023 13:01:47 +0100
Source: dolphin-emu
Architecture: source
Version: 5.0-17995-1
Distribution: unstable
Urgency: low
Maintainer: Debian Games Team 
Changed-By: Jordi Mallach 
Closes: 802947 976530 986739 1019781 1025798
Changes:
 dolphin-emu (5.0-17995-1) unstable; urgency=low
 .
   [ Sébastien Noel ]
   * New GIT snapshot (8ecfa537a2).
   * Switch to the QT5 backend.
 .
   [ Jordi Mallach ]
   * Team upload.
   * New upstream beta release (closes: #986739).
 - builds with ffmpeg 5.0 (closes: #976530)
 - no longer uses wxwidgets (closes: #1019781)
 - fixes initially stuck controller axes (closes: #802947)
 - rebuilt against newer libmbed (closes: #1025798)
   * Refresh patches.
   * Use system cubeb.
   * Switch 

Bug#1019781: marked as done (dolphin-emu: Please transition to wxwidgets3.2)

[Debian Bug Tracking System]

Your message dated Thu, 02 Feb 2023 13:05:45 +
with message-id 
and subject line Bug#1019781: fixed in dolphin-emu 5.0-17995-1
has caused the Debian Bug report #1019781,
regarding dolphin-emu: 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.)


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

Hi,

Please transition dolphin-emu 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: dolphin-emu
Source-Version: 5.0-17995-1
Done: Jordi Mallach 

We believe that the bug you reported is fixed in the latest version of
dolphin-emu, 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.
Jordi Mallach  (supplier of updated dolphin-emu package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 02 Feb 2023 13:01:47 +0100
Source: dolphin-emu
Architecture: source
Version: 5.0-17995-1
Distribution: unstable
Urgency: low
Maintainer: Debian Games Team 
Changed-By: Jordi Mallach 
Closes: 802947 976530 986739 1019781 1025798
Changes:
 dolphin-emu (5.0-17995-1) unstable; urgency=low
 .
   [ Sébastien Noel ]
   * New GIT snapshot (8ecfa537a2).
   * Switch to the QT5 backend.
 .
   [ Jordi Mallach ]
   * Team upload.
   * New upstream beta release (closes: #986739).
 - builds with ffmpeg 5.0 (closes: #976530)
 - no longer uses wxwidgets (closes: #1019781)
 - fixes initially stuck controller axes (closes: #802947)
 - rebuilt against newer libmbed (closes: #1025798)
   * Refresh patches.
   * Use system cubeb.
   * Switch to Qt6.
   * Install dolphin-emu-nogui and dolphin-tool.
   * Update copyright file.
   * Go back to using external Vulkan and VulkanMemoryAllocator.
   * Update DOLPHIN_WC_DESCRIBE and _WC_REVISION definitions.
   * Enable building against system gtest.
   * Enable tests (closes: #976530).
   * Switch Build-Depends from libgl1-mesa-dev to libgl-dev.
   * Update copyright years.
   * Drop definition of DEB_LDFLAGS_MAINT_APPEND, as --as-needed is now the
 default.
   * Add myself to Uploaders.
   * Switch to debhelper compat v13.
   * Update Standards-Version to 4.5.0 (for now).
   * Remove obsolete include-binaries definition.
Checksums-Sha1:
 c2ac31965f99115fc1a6816659c12a9fd64ddcca 2822 dolphin-emu_5.0-17995-1.dsc
 c39021fc61a05ba193fd998bd1dd94da6720f1e0 8361176 
dolphin-emu_5.0-17995.orig.tar.xz
 bcb6228353a451eb93028f2cd52c88bb92610fd8 11504 
dolphin-emu_5.0-17995-1.debian.tar.xz
 5e5eb203c77bb724174bd88e1ed476189effefc8 17848 
dolphin-emu_5.0-17995-1_amd64.buildinfo
Checksums-Sha256:
 ca482a27bf15160e735367a45781d962830dc8739c65ae6ed41d140dfcfb1f25 2822 
dolphin-emu_5.0-17995-1.dsc
 482e5612bf7510323ed13257a537ea6748bfbe1c190696208a219cd7b5c7e7ff 8361176 
dolphin-emu_5.0-17995.orig.tar.xz
 611bed3f3d91184f1cbdae604f5bdb27e34e117e3f154fb218f725500e46043f 11504 
dolphin-emu_5.0-17995-1.debian.tar.xz
 8c8bd067c66c3da0483df05c795829f31ac894d3371b7b9742aac8ec63159ec3 17848 
dolphin-emu_5.0-17995-1_amd64.buildinfo
Files:
 0cb043bef1cf60166809913e3338564c 2822 games optional 
dolphin-emu_5.0-17995-1.dsc
 5cb4c93ea7a68c25252ed5bfda92d4af 8361176 games optional 
dolphin-emu_5.0-17995.orig.tar.xz
 a779591107c8737a171f80b0e0ef6a19 11504 games optional 
dolphin-emu_5.0-17995-1.debian.tar.xz
 015c55ce7b233636f33030f03e243d18 17848 games optional 

Bug#1020138: marked as pending in mate-hud

[Mike Gabriel]

Control: tag -1 pending

Hello,

Bug #1020138 in mate-hud reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/debian-mate-team/mate-hud/-/commit/aa2e687267370bac8c2709f8fee1c1bf9d43a732


debian/patches: Add 2001_fix-ftbfs-due-to-multi-toplevel-packages.patch. 
(Closes: #1020138).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1020138

Processed: Bug#1020138 marked as pending in mate-hud

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1020138 [src:mate-hud] mate-hud: FTBFS: make[1]: *** [debian/rules:13: 
override_dh_auto_clean] Error 25
Added tag(s) pending.

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

Bug#1026541: marked as done (android-platform-system-extras: FTBFS: squashfs_utils/squashfs_utils.c:27:10: fatal error: squashfs_fs.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Thu, 02 Feb 2023 11:34:05 +
with message-id 
and subject line Bug#1026541: fixed in android-platform-system-extras 
10.0.0+r36+ds-2.1
has caused the Debian Bug report #1026541,
regarding android-platform-system-extras: FTBFS: 
squashfs_utils/squashfs_utils.c:27:10: fatal error: squashfs_fs.h: 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.)


-- 
1026541: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026541
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: android-platform-system-extras
Version: 10.0.0+r36+ds-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> cc ext4_utils/ext4_utils.cpp ext4_utils/wipe.cpp ext4_utils/ext4_sb.cpp 
> squashfs_utils/squashfs_utils.c -o debian/out/libext4_utils.so.0 -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
> -I/usr/include/android -DNDEBUG -Iext4_utils/include -Ilibfec/include 
> -Isquashfs_utils -I/usr/include/android -D_GNU_SOURCE -DFEC_NO_KLOG 
> -DSQUASHFS_NO_KLOG -D_LARGEFILE64_SOURCE -Wl,-z,relro -Wl,-z,now -fPIC 
> -shared -Wl,-soname,libext4_utils.so.0 
> -Wl,-rpath=/usr/lib/x86_64-linux-gnu/android 
> -L/usr/lib/x86_64-linux-gnu/android -lbase -lsparse -lselinux
> squashfs_utils/squashfs_utils.c:27:10: fatal error: squashfs_fs.h: No such 
> file or directory
>27 | #include "squashfs_fs.h"
>   |  ^~~
> compilation terminated.
> make[2]: *** [debian/libext4_utils.mk:29: build] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/12/20/android-platform-system-extras_10.0.0+r36+ds-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221220;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221220=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 mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: android-platform-system-extras
Source-Version: 10.0.0+r36+ds-2.1
Done: Adrian Bunk 

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated 
android-platform-system-extras 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: Wed, 18 Jan 2023 17:40:05 +0200
Source: android-platform-system-extras
Architecture: source
Version: 10.0.0+r36+ds-2.1
Distribution: unstable
Urgency: medium
Maintainer: Android Tools Maintainers 

Changed-By: Adrian Bunk 
Closes: 1026541
Changes:
 android-platform-system-extras (10.0.0+r36+ds-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Adapt to new libsquashfuse-dev. (Closes: #1026541)
Checksums-Sha1:
 8eae9dd351b1c71249990b8423d78abb90b80117 2951 
android-platform-system-extras_10.0.0+r36+ds-2.1.dsc
 09b291ebe74de3ea4d6113bd8b58106af52d55b4 5524 
android-platform-system-extras_10.0.0+r36+ds-2.1.debian.tar.xz
Checksums-Sha256:
 4a0d82966f324bc3df631f09a51bbb13aa5849c0a1edb30a33381b06096d3528 2951 
android-platform-system-extras_10.0.0+r36+ds-2.1.dsc
 a56abb4153a46faa43e357c58c522f79d2483aae45a6ad3f2d5e9c3364756311 5524 
android-platform-system-extras_10.0.0+r36+ds-2.1.debian.tar.xz
Files:
 d350be1efd468095566349a5d6b501a9 2951 devel optional 
android-platform-system-extras_10.0.0+r36+ds-2.1.dsc
 

Bug#995017: marked as done (gpyfft: autopkgtest regression on armhf: Aborted)

[Debian Bug Tracking System]

Your message dated Thu, 2 Feb 2023 13:22:24 +0200
with message-id 

and subject line gpyfft: autopkgtest regression on armhf: Aborted
has caused the Debian Bug report #995017,
regarding gpyfft: autopkgtest regression on armhf: Aborted
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.)


-- 
995017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995017
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gpyfft
Version: 0.7.1-2
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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

   passfail
gpyfft from testing0.7.1-2
all others from testingfrom testing

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

Currently this regression is blocking the migration 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=gpyfft

https://ci.debian.net/data/autopkgtest/testing/armhf/g/gpyfft/15502710/log.gz

autopkgtest [19:33:18]: test command1: set -efu ; for py in
$(py3versions -r 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing
with $py:" ; $py -m pytest --pyargs gpyfft.test ; done
autopkgtest [19:33:18]: test command1: [---
Testing with python3.9:
Fatal Python error: Aborted

Thread 0xf7d76530 (most recent call first):
  File "/usr/lib/python3.9/inspect.py", line 1499 in getframeinfo
  File "/usr/lib/python3.9/inspect.py", line 1529 in getouterframes
  File "/usr/lib/python3.9/inspect.py", line 1552 in stack
  File "/usr/lib/python3/dist-packages/parameterized/parameterized.py",
line 481 in parameterized_expand_wrapper
  File "/usr/lib/python3/dist-packages/gpyfft/test/test_batched.py",
line 15 in test_fft_batched
  File "/usr/lib/python3/dist-packages/gpyfft/test/test_batched.py",
line 12 in 
  File "/usr/lib/python3/dist-packages/_pytest/assertion/rewrite.py",
line 170 in exec_module
  File "", line 680 in _load_unlocked
  File "", line 986 in _find_and_load_unlocked
  File "", line 1007 in _find_and_load
  File "", line 1030 in _gcd_import
  File "/usr/lib/python3.9/importlib/__init__.py", line 127 in import_module
  File "/usr/lib/python3/dist-packages/_pytest/pathlib.py", line 520 in
import_path
  File "/usr/lib/python3/dist-packages/_pytest/python.py", line 552 in
_importtestmodule
  File "/usr/lib/python3/dist-packages/_pytest/python.py", line 484 in
_getobj
  File "/usr/lib/python3/dist-packages/_pytest/python.py", line 288 in obj
  File "/usr/lib/python3/dist-packages/_pytest/python.py", line 500 in
_inject_setup_module_fixture
  File "/usr/lib/python3/dist-packages/_pytest/python.py", line 487 in
collect
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 324 in

  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 294 in
from_call
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 324 in
pytest_make_collect_report
  File "/usr/lib/python3/dist-packages/pluggy/callers.py", line 187 in
_multicall
  File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 83 in

  File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 92 in
_hookexec
  File "/usr/lib/python3/dist-packages/pluggy/hooks.py", line 286 in
__call__
  File "/usr/lib/python3/dist-packages/_pytest/runner.py", line 441 in
collect_one_node
  File "/usr/lib/python3/dist-packages/_pytest/main.py", line 768 in
genitems
  File "/usr/lib/python3/dist-packages/_pytest/main.py", line 771 in
genitems
  File "/usr/lib/python3/dist-packages/_pytest/main.py", line 568 in
_perform_collect
  File "/usr/lib/python3/dist-packages/_pytest/main.py", line 516 in
perform_collect
  File "/usr/lib/python3/dist-packages/_pytest/main.py", line 306 in
pytest_collection
  File "/usr/lib/python3/dist-packages/pluggy/callers.py", line 187 in
_multicall
  File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 83 in

  File "/usr/lib/python3/dist-packages/pluggy/manager.py", line 92 in
_hookexec
  File "/usr/lib/python3/dist-packages/pluggy/hooks.py", line 286 in
__call__
  File "/usr/lib/python3/dist-packages/_pytest/main.py", line 295 in _main
  File 

Bug#1030304: Licensing & copyright issues

[Adam Ant]

Source: linuxcnc
Severity: serious

Source files for libnml lack standard Debian or SPDX copyright headers. Also 
obsolete version of LGPL used.

Source files for both the core linuxcnc & libmnl are forked and munged from a 
NIST project known as the Enhanced Machine Control (EMC). The source code for 
this is public domain. One can NOT take PD code, claim copyright, and then slap 
an arbitrary license on it.

At best, renders the license unenforceable in many jurisdictions, or illegal in 
some.

Kindly refer to Debian Legal

Bug#1030188: marked as done (PyQt5.Qt is empty)

[Debian Bug Tracking System]

Your message dated Thu, 02 Feb 2023 10:36:22 +
with message-id 
and subject line Bug#1030188: fixed in pyqt5 5.15.8+dfsg-2
has caused the Debian Bug report #1030188,
regarding PyQt5.Qt is empty
to be marked as done.

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

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


-- 
1030188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030188
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-pyqt5
Version: 5.15.8
 
PyQt5.Qt is empty. This causes gnuradio-companion to fail running, as well as 
problems with other packages.
 
To reproduce the bug:
import PyQt5.Qt
PyQt5.Qt.QValidator
 
Please look at the Arch bug report for more details: 
https://bugs.archlinux.org/task/77315
 
Debian sid, kernel 6.1.0-2-rt-amd64, libc6 2.36-8
--- End Message ---
--- Begin Message ---
Source: pyqt5
Source-Version: 5.15.8+dfsg-2
Done: Dmitry Shachnev 

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

Debian distribution maintenance software
pp.
Dmitry Shachnev  (supplier of updated pyqt5 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 02 Feb 2023 13:57:27 +0400
Source: pyqt5
Architecture: source
Version: 5.15.8+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Dmitry Shachnev 
Closes: 1030188
Changes:
 pyqt5 (5.15.8+dfsg-2) unstable; urgency=medium
 .
   * Fix PyQt5.Qt module being empty (closes: #1030188).
 - Bump sip build-dependencies to 6.7.6+dfsg-2.
 - Backport upstream patch to fix the order in which modules are built.
Checksums-Sha1:
 721d546798013c656bf7f0e38a80fe6b64427943 4430 pyqt5_5.15.8+dfsg-2.dsc
 b7c6cccee8b4f11d30c63ae3922a321d83f748d6 18644 
pyqt5_5.15.8+dfsg-2.debian.tar.xz
 d974b77e7a40d170e99311eda5d9f2e60ae219f0 14504 
pyqt5_5.15.8+dfsg-2_source.buildinfo
Checksums-Sha256:
 1aeef92c782762a2cecb4c71fbcbcdd8bd76d9618d666f3dc2762627438c97b3 4430 
pyqt5_5.15.8+dfsg-2.dsc
 4d0cb6b243fbaee06a36cbec2e8ebc2b4f9796f84fdd77bd6ff870b8c0d7d8ff 18644 
pyqt5_5.15.8+dfsg-2.debian.tar.xz
 30310080e955575a8a0aa9784c24a9268960e27eb119d853aa848b4ee5499a84 14504 
pyqt5_5.15.8+dfsg-2_source.buildinfo
Files:
 8bc216c782070dc69174027d7c44064c 4430 python optional pyqt5_5.15.8+dfsg-2.dsc
 4441197965ce8cbb7619876a9cb1fb91 18644 python optional 
pyqt5_5.15.8+dfsg-2.debian.tar.xz
 1ef0186559961a4f946d48abe4956de0 14504 python optional 
pyqt5_5.15.8+dfsg-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEE5688gqe4PSusUZcLZkYmW1hrg8sFAmPbiy8THG1pdHlhNTdA
ZGViaWFuLm9yZwAKCRBmRiZbWGuDy5gGEACXHIbZJH5eKUhKs4QE3nOcOqNUeZgg
jz3774km/Rqi9sRCBt25fwi3V5lXoeRbwjSPpE2GmbIhyzzw5b8rEcebcnFmUIpt
lVObuOCetJE0a41io5OB+NVk8XObOLSI5olq3C5zdjMe1FJhb44RDmWKt7mZMCas
zoVWpz9sJF/d6m4s83hb1R38Gk75wiHmqGGIjlktgDylhOEBzIFHX2RkmCKO0RkU
hXC2FYS+2C9xHaC3w3HY5ohDPI6ILNXN4zUSvq8QHf49EcAYdXaiRkMUsrQ+GvVn
hI6eerpvqBonYTeYbYF5DqjbhVz43P5nwsUZDNutgf/Rc/uh+W+EethpWEwEbXzN
E/OhfMbyrqF/aewBQHARfSAinokyRCR/HjL3BKxfQryyzNEwdY/JVI06Ce4Sa9eT
9aBBZNLxbhC2HpR97GZ9X4LAP0OCUE+OlRH1YaKD25/lAS15/0H60tu7ZifISdAf
/jiCDqYOs7d1m8nSLHVOGhNMQTrUs3YtWpXdekEkVDGTOuW1eh7w5hoJ4galLzqI
aVUg1A9NWHZpQDuKVP8r+CWm3hQjitrRPW+gM6Z7Hihdm5yBIhMB/gokJzN95LEO
uHbMS76ypwnyFDmF2Gy4cDTXvYn7cPSsc2iEZXpfE9tJRl/kgIxhsmH7gr9iNKie
ByTws4Id+efVCA==
=P/Rd
-END PGP SIGNATURE End Message ---

Bug#1028301: grub: grub-probe doesn't detect that file is on cryptfs on new installation

[Yllman, Jens]

Hi,

Is anything happening about this??

I am currently in a limbo with a broken EFI that does not want to boot 
my debian installation on an encrypted LVM.


I can manually load the config. But I would like the grub install to 
rebuild it correctly. But this is maybe the reason why it is broken in 
the first place. Not finding what to boot.


Jens

Bug#1030188: marked as done (PyQt5.Qt is empty)

[Debian Bug Tracking System]

Your message dated Thu, 02 Feb 2023 10:23:09 +
with message-id 
and subject line Bug#1030188: fixed in sip6 6.7.6+dfsg-2
has caused the Debian Bug report #1030188,
regarding PyQt5.Qt is empty
to be marked as done.

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

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


-- 
1030188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030188
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-pyqt5
Version: 5.15.8
 
PyQt5.Qt is empty. This causes gnuradio-companion to fail running, as well as 
problems with other packages.
 
To reproduce the bug:
import PyQt5.Qt
PyQt5.Qt.QValidator
 
Please look at the Arch bug report for more details: 
https://bugs.archlinux.org/task/77315
 
Debian sid, kernel 6.1.0-2-rt-amd64, libc6 2.36-8
--- End Message ---
--- Begin Message ---
Source: sip6
Source-Version: 6.7.6+dfsg-2
Done: Dmitry Shachnev 

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

Debian distribution maintenance software
pp.
Dmitry Shachnev  (supplier of updated sip6 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 02 Feb 2023 13:07:19 +0400
Source: sip6
Architecture: source
Version: 6.7.6+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Dmitry Shachnev 
Closes: 1030188
Changes:
 sip6 (6.7.6+dfsg-2) unstable; urgency=medium
 .
   * Backport upstream patch to fix handling of composite classes
 (closes: #1030188).
Checksums-Sha1:
 b4b8ae472cb2bda5b21c94b15108f50e3508f94e 2295 sip6_6.7.6+dfsg-2.dsc
 bd917e372016f2651ebceca4d7762c36542f 12640 sip6_6.7.6+dfsg-2.debian.tar.xz
 fefbcab9f013568932ef023db4110bff3ca941fc 6876 
sip6_6.7.6+dfsg-2_source.buildinfo
Checksums-Sha256:
 5adea72800fcac7bcfdd093d4e2decd23a5db0167be594ffb6581c2696fb08ad 2295 
sip6_6.7.6+dfsg-2.dsc
 96c87b8d13689c9e6f4df71e4d69a9e84a5c45d5251b62e3fa66d1e04383e50e 12640 
sip6_6.7.6+dfsg-2.debian.tar.xz
 2359ab059691f6831ccf5a1a7fad24ec3d4ecfc3991ff32c9a44d95acbfdf798 6876 
sip6_6.7.6+dfsg-2_source.buildinfo
Files:
 ac96979513c27884455e1a59b89fc286 2295 devel optional sip6_6.7.6+dfsg-2.dsc
 371af92e0f434f341c64a1ed7075e4dd 12640 devel optional 
sip6_6.7.6+dfsg-2.debian.tar.xz
 32552767bdc28403d7b4eef97f6598c7 6876 devel optional 
sip6_6.7.6+dfsg-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEE5688gqe4PSusUZcLZkYmW1hrg8sFAmPbh1YTHG1pdHlhNTdA
ZGViaWFuLm9yZwAKCRBmRiZbWGuDy3LvD/4wcHzPql9sClrJ02fBZrJYi6P5YFwe
VbdBYZ30lRxJsnxiiO7m1vw3vkbNyxWJLPpbceM7Q1qDNSKNlXuU9U4hL083kWsI
i3RsK7PaVdthslNGJ+3/5Cc0r0Lv2XfSTTsEHINupW6qqimmIsYKR4AHMHICoKRb
wH37cBQQuGbsvMpVusUf7F/f36Z7sWaX4FNtpr7iIFkyBmSZ2/QYHancPK/ayoDh
SEGdhxgtfCym0A+GxTSEZj7k+qS1i+BztQmo/q8tLM+qKRaZio7flOq7cbpaUzX9
tJI+3LK0zNriVufgsfyv/YAst0bu3St0pSuZ5pqDt5sFHXkhoo64Cj4QVocWVqmn
uPFILqhCT1qUqfaY+OGkET6TA353UB7cxoR+iRVoSCho1q9R8Ww4VO4vsr6lfIsT
XG1s9od4S00A7897yL4JMA88U1P5F/T24FJzYe3NM4Sv791h2hW46xxseFFGd6QQ
/KsRgk6CVMqCV3H/VaLOG/LxhuUk/Vr0CpFGrPMsdyLnu9G347l5PX0fOM7EinFT
CxlJiUbGiqEZzeDLsGPvS0zWKDtKwP1n1QNwbGcYajZi8xB/eXAcqL2RP2XCgNsG
0MKn5ND4NOc0DbEZFojY3hZmZ+zKGniupYj6BR0szdRAww/ieGkEIU+OwhxqmZne
gcVgcHB6ncZATA==
=mmA9
-END PGP SIGNATURE End Message ---

Bug#1004729: bind9-dyndb-ldap: fails to load dyndb-ldap backend

[Jakob Haufe]

On Wed, 1 Feb 2023 21:10:57 +0100
Matej Zagiba  wrote:

> I believe real problem lies in package management procedures - there 
> should be trigger to recompile and repackage (and retest) 
> bind9-dyndb-ldap after each version change and/or repackage of 
> bind9-libs. This action should be done automatically. Otherwise 
> bind9-dyndb-ldap will be permanently broken.

This is, unfortunately, not as simple as you write there.
bind9-dyndb-ldap is not as independent from bind9 upstream as we all would
like. To make it compile with bind9 9.18.11, a tiny change is required,
see [1].

So even if Debian packaging would do things like "recompile triggers",
it wouldn't help here.

> Should I open another bug?

I don't think it's necessary, but if you want this tracked in the BTS
then it needs to be a new one as it's a different issue, even if
similar in nature.

Cheers,
sur5r

[1] https://pagure.io/bind-dyndb-ldap/pull-request/218

-- 
ceterum censeo microsoftem esse delendam.


pgpIi6WeHhtLD.pgp
Description: OpenPGP digital signature

Processed: Ownership

[Debian Bug Tracking System]

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

> owner 830945 !
Bug #830945 [php-dompdf] php-dompdf: use A4 papersize per default
Owner recorded as William Desportes .
> owner 831735 !
Bug #831735 [php-dompdf] php-dompdf: /var/cache/php-dompdf/fonts/ permission 
issues
Owner recorded as William Desportes .
> owner 1015874 !
Bug #1015874 [src:php-dompdf] php-dompdf: CVE-2022-2400
Owner recorded as William Desportes .
> stop
Stopping processing here.

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

Bug#1030220: xrayutilities: missing dependency on python3-h5py breaks armel tests

[Drew Parsons]

On 2023-02-01 22:40, Stefano Rivera wrote:


Hi Drew (2023.01.31_18:48:32_-0400)

xrayutilities does have Build-Depends: python3-h5py. Evidentally
dh-python3 isn't able to determine the correct dependency for h5py
(likely it gets confused by python3-h5py-serial).  Until that's fixed,
python3-xrayutilities should declare
Depends: python3-h5py
explicitly.


This sounds like an issue in the way the python3-h5py package is
structured.

python3-h5py-serial has the .egg-info, so that's the dependency that's
being generated.

You can customize this with a PyDist override file, see:
/usr/share/doc/dh-python/README.PyDist



That sounds like a good solution.  h5py will be the better for it.

Thanks, Stefano.

Drew

Processed: bug 1030298 is forwarded to https://github.com/inducer/pyopencl/issues/673 ...

[Debian Bug Tracking System]

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

> forwarded 1030298 https://github.com/inducer/pyopencl/issues/673
Bug #1030298 [src:pyopencl] pyopencl: FTBFS on i386: = 1 failed, 304 passed, 7 
skipped, 1 deselected, 2 xfailed, 31 warnings in 736.25s (0:12:16) =
Set Bug forwarded-to-address to 
'https://github.com/inducer/pyopencl/issues/673'.
> fixed 1025279 520.56.06-1
Bug #1025279 {Done: Andreas Beckmann } 
[src:nvidia-graphics-drivers] nvidia-graphics-drivers: CVE-2022-34670, 
CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, 
CVE-2022-34682, CVE-2022-34684, CVE-2022-42254, CVE-2022-42255, CVE-2022-42256, 
CVE-2022-42257, CVE-2022-42258, CVE-2022-42259, CVE-2022-42260, CVE-2022-42261, 
CVE-2022-42262, CVE-2022-42263, CVE-2022-42264
Marked as fixed in versions nvidia-graphics-drivers/520.56.06-1.
> notfixed 1019372 0.9.0
Bug #1019372 {Done: Sergio Durigan Junior } 
[src:python-build] python-build: New Upstream version available
The source 'python-build' and version '0.9.0' do not appear to match any binary 
packages
No longer marked as fixed in versions 0.9.0.
> fixed 1019372 0.9.0-1
Bug #1019372 {Done: Sergio Durigan Junior } 
[src:python-build] python-build: New Upstream version available
Marked as fixed in versions python-build/0.9.0-1.
> notfixed 1002214 1:9.18.8-2
Bug #1002214 {Done: Bernhard Schmidt } [bind9-dnsutils] 
dig: SIGABRT when using +trace over TCP (dighost.c:1683 assertion fails)
There is no source info for the package 'bind9-dnsutils' at version 
'1:9.18.8-2' with architecture ''
Unable to make a source version for version '1:9.18.8-2'
No longer marked as fixed in versions 1:9.18.8-2.
> fixed 1002214 1:9.18.8-1
Bug #1002214 {Done: Bernhard Schmidt } [bind9-dnsutils] 
dig: SIGABRT when using +trace over TCP (dighost.c:1683 assertion fails)
Marked as fixed in versions bind9/1:9.18.8-1.
> thanks
Stopping processing here.

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

Bug#1026204: tar FTBFS on armel, armhf, i386, hppa, powerpc and sparc64

[Helge Deller]

On Tue, 31 Jan 2023 18:27:27 +0100 Andreas Henriksson  wrote:

> 
> export DEB_BUILD_MAINT_OPTIONS = future=+lfs
> export DEB_CFLAGS_MAINT_APPEND = -Wall -Wno-analyzer-null-argument

Might be useful to add a comment here saying:

# Workaround gnulib issue: The below three lines can be dropped once tar >= 
1.35 is used.
> ifneq ($(shell dpkg-architecture -qDEB_TARGET_ARCH_BITS),64)
> export DEB_CPPFLAGS_MAINT_APPEND = -D_TIME_BITS=64
> endif


Just for your info:
I opened this ticket:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030159.
which asks for a "future=+time64" option, which was accepted.
So, in future, just adding "future=+time64" avoids the "ifneq" check above.


I assume you also have no idea how to use src:gnulib when building tar
(or maybe it's just too complicated change)?
(The problem should already be fixed in the version of src:gnulib we
have in debian...)


I don't know. Sorry.


Will you go ahead and upload this Helge?


I'd prefer if some "tar" maintainer would do that...

Helge

Processed: Bug#1030188 marked as pending in sip6

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1030188 [python3-sipbuild] PyQt5.Qt is empty
Added tag(s) pending.

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

Bug#1030188: marked as pending in sip6

[Dmitry Shachnev]

Control: tag -1 pending

Hello,

Bug #1030188 in sip6 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/python-team/packages/sip6/-/commit/37b2bd4bb8d249ddae6db1c8ca804fc7036a8f2c


Backport upstream patch to fix handling of composite classes.

Closes: #1030188.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1030188

Bug#1030012: marked as done (astropy: i386 LevMarLSQFitter fails test)

[Debian Bug Tracking System]

Your message dated Thu, 02 Feb 2023 09:07:30 +
with message-id 
and subject line Bug#1030012: fixed in astropy 5.2.1-2
has caused the Debian Bug report #1030012,
regarding astropy: i386 LevMarLSQFitter fails test
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.)


-- 
1030012: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030012
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: astropy
Version: 5.2.1-1
Severity: normal
Control: forwarded -1 https://github.com/astropy/astropy/issues/13986

astropy fails test_models_fitting[LevMarLSQFitter-model31] on i386.
The problem appears to be triggered by scipy 1.10, and the problem is
discussed upstream at https://github.com/astropy/astropy/issues/13986

Apparently normalising the input data before fitting might work around
the problem.

See also https://github.com/astropy/astropy/pull/14013
--- End Message ---
--- Begin Message ---
Source: astropy
Source-Version: 5.2.1-2
Done: Ole Streicher 

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 02 Feb 2023 09:06:27 +0100
Source: astropy
Architecture: source
Version: 5.2.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Astronomy Maintainers 

Changed-By: Ole Streicher 
Closes: 1030012
Changes:
 astropy (5.2.1-2) unstable; urgency=medium
 .
   * Mark LevMarLSQFitter test xfail (Closes: #1030012)
Checksums-Sha1:
 21b56613beb811d13861fc2d7f8531792093c476 3080 astropy_5.2.1-2.dsc
 17ea5db515fa5430f0e4eed0dbcf1bd3e47886a2 25824 astropy_5.2.1-2.debian.tar.xz
Checksums-Sha256:
 9a9841f3a805edd6204a04281239649011856b1290157221e3dc79b85364fa4d 3080 
astropy_5.2.1-2.dsc
 1ae8bff3a9cc0b8822fa71729e77b4697a4d070d57ed5ffd6a24f0337167a14a 25824 
astropy_5.2.1-2.debian.tar.xz
Files:
 e5bb7dbf8c09e242c687d819005659d6 3080 python optional astropy_5.2.1-2.dsc
 4a58b75b62d2cb9b718c6e3070b79b12 25824 python optional 
astropy_5.2.1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE7/BpV0Ra2/h0L3qtmk9WvbkOGL0FAmPbdd8ACgkQmk9WvbkO
GL29wBAAkRJXwTTg0yUDC24KkvkXqHW3ykc+n8SEw+uu+mWleICbC1QQzxRxScDW
tEiOpkxYBzP/xUcFDr1XdELl5d+Ha7+YY/g8sIusbFT7w346ndE8SsEFJAvY71i0
NI/QheQ/3boI6ChUHqVbUaGQhHLsDTOfHlKCH2+JGQvpBdv9QytlJXTqOq4tOveb
4E32MkHOI1lAGE0YQC7ShH2l+9Y3zTnCgkpmGjKfMwjnI96j2HVCrD9OQBvPR30J
2zr8tcWuyl7LzOqRUETHKWcLeFQIefqHS2MokkGNI8/pYszrRn64LINqsoM152Ek
VmTbQQSyP8kX6HUsX1/z+C7WwFvC93etOfjgX8BnHde5taSCnHQyG/vEShu6F6Hh
vKjKPlBP4zTM3smJquHQEk+CGVnv1Ewf7uLWRCSe0Ya0aKflqe8vkPA4jt7RFCGj
6oT39Wkt3yxLpF3lHRtDPR1Upq74bR29AVTPQvTrjQo0bVuRrxiEnuZ195tG8MnX
4TG10N+yDJsiNWepJwKRQw2Vyppm0rRl24//KYki5SY9SB913563M0iZzcvFDNfT
9Lyi1D0e8fdgUp6P5Z5LoZa/qyIQ3F1Km0reZZ2kFa4fYpg2UXUbr3d188/LfvnM
CFeD7cpAOZQKXhwEo+BLBTzMr+G7VBqrbSbQZhSt71CiwTnSbKQ=
=bhrP
-END PGP SIGNATURE End Message ---

Processed: Bug#1030012 marked as pending in astropy

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1030012 [src:astropy] astropy: i386 LevMarLSQFitter fails test
Added tag(s) pending.

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

Bug#1030012: marked as pending in astropy

[Ole Streicher]

Control: tag -1 pending

Hello,

Bug #1030012 in astropy reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/debian-astro-team/astropy/-/commit/b091b627c92509502056cf85bd5cb7fd1531f97b


Mark LevMarLSQFitter test xfail

Closes: #1030012


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1030012

Processed: tagging 1028563

[Debian Bug Tracking System]

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

> tags 1028563 + sid bookworm
Bug #1028563 {Done: Nilesh Patra } [nyx] nyx: Does not work 
with python 3.11 anymore
Added tag(s) bookworm and sid.
> thanks
Stopping processing here.

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

Bug#1029594: Fails to authenticate mit o365

[Nicola Chiapolini]

Hi Carsten

Thanks for your reply.

I'm considering this issue is normaly just of severity important.
[...]

I agree.

As explained, I choose the higher one to make sure it triggers 
apt-listbugs. I was not aware that "a major effect on the usability" is 
not enough to trigger listbugs until now. I adjusted the config 
accordingly, but I assume a lot of users still have the default set.



But, using severity important would allow to migrate the package to > testing 
and more users would be affected by the issue.

The package already migrated to testing. That's why it hit me.

$ aptitude versions thunderbird
i  1:102.6.0-1
p  1:102.7.1-1  testing,unstable
p  1:104.0~b2-1 experimental

so listbugs is currently the remaining line of defence.

best
Nicola