Bug#1076245: lintian-brush: hangs and when killed leaved lock in Git repository

[Andreas Tille]

Package: lintian-brush
Version: 0.155
Severity: grave
Justification: renders package unusable

Hi,

I'm currently do not use lintian-brush extensively currently (since I
reduced my packaging work in DPL) term but *always* when using it hangs.
Not even some ^C in terminal kann bring back some prompt I have to kill
the process manually or close the terminal.  After this some lock files
are remaining in the Git repository which need to be manually removed.

Latest example 
   https://salsa.debian.org/med-team/tao-json

tao-json(master) $ lintian-brush 

 88/153
^C^C^C^C^C

This is not only true for this specific package but for *all* packages
I tried in the last couple of weeks.

Kind regards
 Andreas.

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

Kernel: Linux 6.3.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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 lintian-brush depends on:
ii  devscripts   2.23.7
ii  libc62.38-14
ii  libgcc-s114.1.0-3
ii  liblzma5 5.6.2-2
ii  libpython3.11t64 3.11.9-1
ii  libssl3t64   3.2.2-1
ii  python3  3.12.2-1
ii  python3-breezy   3.3.6-1+b1
ii  python3-debian   0.1.49
ii  python3-debmutate0.68
ii  python3-distro-info  1.7
ii  python3-dulwich  0.21.6-1+b1
ii  python3-iniparse 0.5-2
ii  python3-iso8601  1.0.2-1
ii  python3-levenshtein  0.25.1-3
ii  python3-psycopg2 2.9.9-1+b1
ii  python3-pyinotify0.9.6-2
ii  python3-ruamel.yaml  0.18.6+ds-3
ii  python3-semver   2.10.2-3
ii  python3-tomlkit  0.12.5-1
ii  python3-tqdm 4.66.4-1
ii  python3-upstream-ontologist  0.1.37-1

Versions of packages lintian-brush recommends:
ii  debhelper 13.16
ii  decopy0.2.4.8-0.1
ii  dos2unix  7.5.2-1
ii  gpg   2.2.43-7
ii  lintian   2.117.0
ii  ognibuild 0.0.20-1
ii  python3-bs4   4.12.3-1
ii  python3-docutils  0.20.1+dfsg-3
ii  python3-lxml  5.2.1-1
ii  python3-markdown  3.6-1

Versions of packages lintian-brush suggests:
ii  brz-debian 2.8.79
ii  git-buildpackage   0.9.34
ii  gnome-pkg-tools0.22.9
ii  po-debconf 1.0.21+nmu1
ii  postgresql-common  261

-- no debconf information

Bug#1076202: marked as done (python-memray: build-depends on python3.11-dev)

[Debian Bug Tracking System]

Your message dated Sat, 13 Jul 2024 00:25:59 +
with message-id 
and subject line Bug#1076202: fixed in python-memray 1.13.3+dfsg-2
has caused the Debian Bug report #1076202,
regarding python-memray: build-depends on python3.11-dev
to be marked as done.

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

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


-- 
1076202: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076202
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-memray
Version: 1.13.3+dfsg-1
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.12

Hi Maintainer

python-memray build-depends on python3.11-dev (and  python3.12-dev).
Python 3.11 is being removed from Trixie soon.  Please remove the
build-depends on python3.11-dev, perhaps python3-all-dev is what you
need instead.

Regards
Graham
--- End Message ---
--- Begin Message ---
Source: python-memray
Source-Version: 1.13.3+dfsg-2
Done: Yogeswaran Umasankar 

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

Debian distribution maintenance software
pp.
Yogeswaran Umasankar  (supplier of updated python-memray 
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, 12 Jul 2024 15:30:00 +
Source: python-memray
Architecture: source
Version: 1.13.3+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Yogeswaran Umasankar 
Closes: 1076202
Changes:
 python-memray (1.13.3+dfsg-2) unstable; urgency=medium
 .
   * d/control: replace python3.*-dev with python3-all-dev + added
 pybuild-plugin-pyproject in Build-Depends. (Closes: #1076202)
   * d/rules: updated override_dh_install for pybuild-plugin-pyproject.
Checksums-Sha1:
 3d095285645138af94cc4f4c6889c808c0617b80 2820 python-memray_1.13.3+dfsg-2.dsc
 4403fc01fde1b8d41475021ee4b112f7ba518a08 10764 
python-memray_1.13.3+dfsg-2.debian.tar.xz
 2bd23e8f686a4c885f8cacf6bd8b7899fab72ab0 10974 
python-memray_1.13.3+dfsg-2_source.buildinfo
Checksums-Sha256:
 c91e2f601c0fef724ecbccda0027235f30bd7caeb4364b4e1467ce1827d97544 2820 
python-memray_1.13.3+dfsg-2.dsc
 80092b8ac2dc575e760de0a7285f5f3fcced1c7e700d949621b5a5940be32685 10764 
python-memray_1.13.3+dfsg-2.debian.tar.xz
 ba614dc707c2eac6be4d7d3e13daca04b54fcf5c46e70fc88c4da839ab0cfb94 10974 
python-memray_1.13.3+dfsg-2_source.buildinfo
Files:
 4a4cdfb8eaf4fdcda4e92b3ef14833a1 2820 python optional 
python-memray_1.13.3+dfsg-2.dsc
 3f69000e88c9d8506db91e35464d6b7f 10764 python optional 
python-memray_1.13.3+dfsg-2.debian.tar.xz
 253309e22002cd7161e116e34c6e6b1c 10974 python optional 
python-memray_1.13.3+dfsg-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEE/qLi99g13V/he2oYtIOKvyeCVXsFAmaRikIQHHlvZ3VAZGVi
aWFuLm9yZwAKCRC0g4q/J4JVewBVD/9wnd1PXqVjTD1IL2gKx2MTegCbdIfR0nXs
A2AoI8iWhpRaMSuSnajRDvLaH/aiFYrkn+zVHqY92ABFCaeWSTU47M6/FbK0MbnP
ldAlAU/IZCXPFRZnrPZc/NqCwG105Ci3wzCkoaJg+Q7CwroJHq0MPZhBgHkhm/Xz
io6vjzLObn9TnYfa94VTxcrAg7CjWrZsq85neWo8uUab645QUoDLZ8npmVuomuf3
u9Y56yS6HRlj0Dc2efyb4jOigXQJKwjBj8U+oE2HoKJV1WT4tzW7lqHsQ3kf9f7d
2DJ0kRwOu9KuQ3p1E42UCgkELi28Ooz1VtwI3e6K4Ys04ZobzEc21V9Lodq3wUMg
XL4dOP3WgKJWyZlwbAaCbKNHwvInHMigWqO7lzy0tqEjRhQ69DSzp+r+4NmuCZSs
a8BzKVaSdz5lW9eKQwINhfJGAcXerirl3oGWhibi9NPharLhCKhxuz/BoEXTaF0k
+Dx2pQE22RJyn/EXfZVsUxVVXy4P1pRARQ796vn2PbW1T7cOn5lMfVZJfc7PDPJk
u595BIrhhxW/ZI9JDg0hs0L21pjwVaDtFPvIE632uxnST1C7bZXITlvr01HNrFET
FseglxAGGRjNEVTLCFv4AxgyNQAKmgNxwKP3UTr+uEmRuX8ENQvNyLAl5HuLPj4c
HG0p1+tzBQ==
=aX9o
-END PGP SIGNATURE-



pgpNlIe8QWlkG.pgp
Description: PGP signature
--- End Message ---

Bug#1076237: gpaste: Uploaded needed for ongoing gnome-shell 46 transition

[Jeremy Bícha]

Source: gpaste
Version: 44.1-2.1
Severity: serious

Please upload gpaste to Unstable for the ongoing gnome-shell 46 transition.

You can use your experimental package with a change something like:
https://launchpadlibrarian.net/715121219/gpaste_45-2_45-2ubuntu1.diff.gz

Thank you,
Jeremy Bícha

Processed: grub-efi-arm64-unsigned: trying to overwrite '/usr/lib/grub/arm64-efi/monolithic/gcdaa64.efi', which is also in package grub-efi-arm64-bin 2.12-2

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + sid
Bug #1076235 [grub-efi-arm64-unsigned] grub-efi-arm64-unsigned: trying to 
overwrite '/usr/lib/grub/arm64-efi/monolithic/gcdaa64.efi', which is also in 
package grub-efi-arm64-bin 2.12-2
Added tag(s) sid.

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

Bug#1076235: grub-efi-arm64-unsigned: trying to overwrite '/usr/lib/grub/arm64-efi/monolithic/gcdaa64.efi', which is also in package grub-efi-arm64-bin 2.12-2

[Chris Hofstaedtler]

Package: grub-efi-arm64-unsigned
Version: 2.12-4
Severity: serious
Control: tags -1 + sid

Upgrading grub on aarch64 fails, like this:

Preparing to unpack .../12-grub-efi-arm64_2.12-4_arm64.deb ...
Unpacking grub-efi-arm64 (2.12-4) over (2.12-2) ...
Preparing to unpack .../13-grub2-common_2.12-4_arm64.deb ...
Unpacking grub2-common (2.12-4) over (2.12-2) ...
Selecting previously unselected package grub-efi-arm64-unsigned.
Preparing to unpack .../14-grub-efi-arm64-unsigned_2.12-4_arm64.deb ...
Unpacking grub-efi-arm64-unsigned (2.12-4) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-GFZQXm/14-grub-efi-arm64-unsigned_2.12-4_arm64.deb 
(--unpack):
 trying to overwrite '/usr/lib/grub/arm64-efi/monolithic/gcdaa64.efi', which is 
also in package grub-efi-arm64-bin 2.12-2
Preparing to unpack .../15-grub-efi-arm64-bin_2.12-4_arm64.deb ...
Unpacking grub-efi-arm64-bin (2.12-4) over (2.12-2) ...
Preparing to unpack .../16-grub-common_2.12-4_arm64.deb ...
Unpacking grub-common (2.12-4) over (2.12-2) ...
...
Errors were encountered while processing:
 /tmp/apt-dpkg-install-GFZQXm/14-grub-efi-arm64-unsigned_2.12-4_arm64.deb
Error: Sub-process /usr/bin/dpkg returned an error code (1)

I imagine additional relationships need to be declared.

Chris

Bug#1074748: marked as done (meep-openmpi: FTBFS: dh_install: error: missing files, aborting)

[Debian Bug Tracking System]

Your message dated Fri, 12 Jul 2024 23:17:14 +
with message-id 
and subject line Bug#1074748: fixed in meep-openmpi 1.25.0-3
has caused the Debian Bug report #1074748,
regarding meep-openmpi: FTBFS: dh_install: error: missing files, aborting
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.)


-- 
1074748: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074748
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: meep-openmpi
Version: 1.25.0-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240702 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[4]: Entering directory '/<>'
> make[4]: Nothing to be done for 'install-exec-am'.
>  /usr/bin/mkdir -p 
> '/<>/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig'
>  /usr/bin/install -c -m 644 meep.pc 
> '/<>/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig'
> make[4]: Leaving directory '/<>'
> make[3]: Leaving directory '/<>'
> make[2]: Leaving directory '/<>'
> find
> .
> ./autogen.sh
> ./config.h.in
> ./config.status
> ./COPYRIGHT
> ./codemeta.json
> ./AUTHORS
> ./README.md
> ./LICENSE
> ./.travis.yml
> ./meep.pc
> ./src
> ./src/update_eh.lo
> ./src/random.lo
> ./src/GDSIIgeom.lo
> ./src/dft_ldos.cpp
> ./src/multilevel-atom.o
> ./src/energy_and_flux.lo
> ./src/bands.lo
> ./src/array_slice.o
> ./src/initialize.lo
> ./src/step_generic_stride1.lo
> ./src/array_slice.cpp
> ./src/step_generic.cpp
> ./src/loop_in_chunks.lo
> ./src/libmeep.la
> ./src/material_data.hpp
> ./src/vec.o
> ./src/structure_dump.lo
> ./src/sphere_quad
> ./src/bicgstab.lo
> ./src/h5fields.o
> ./src/step_generic_stride1.cpp
> ./src/stress.cpp
> ./src/boundaries.lo
> ./src/bands.o
> ./src/near2far.cpp
> ./src/step_generic.lo
> ./src/integrate2.o
> ./src/time.lo
> ./src/cw_fields.o
> ./src/adjust_verbosity.hpp
> ./src/.libs
> ./src/.libs/multilevel-atom.o
> ./src/.libs/array_slice.o
> ./src/.libs/libmeep.la
> ./src/.libs/vec.o
> ./src/.libs/h5fields.o
> ./src/.libs/bands.o
> ./src/.libs/integrate2.o
> ./src/.libs/libmeep.so
> ./src/.libs/cw_fields.o
> ./src/.libs/dft.o
> ./src/.libs/loop_in_chunks.o
> ./src/.libs/GDSIIgeom.o
> ./src/.libs/integrate.o
> ./src/.libs/fields.o
> ./src/.libs/structure_dump.o
> ./src/.libs/libmeep.lai
> ./src/.libs/step_generic_stride1.o
> ./src/.libs/mympi.o
> ./src/.libs/sources.o
> ./src/.libs/monitor.o
> ./src/.libs/casimir.o
> ./src/.libs/update_eh.o
> ./src/.libs/libmeep.so.30
> ./src/.libs/fix_boundary_sources.o
> ./src/.libs/structure.o
> ./src/.libs/boundaries.o
> ./src/.libs/step_generic.o
> ./src/.libs/libmeep.so.30.0.0
> ./src/.libs/anisotropic_averaging.o
> ./src/.libs/near2far.o
> ./src/.libs/meepgeom.o
> ./src/.libs/energy_and_flux.o
> ./src/.libs/susceptibility.o
> ./src/.libs/h5file.o
> ./src/.libs/fields_dump.o
> ./src/.libs/step_db.o
> ./src/.libs/initialize.o
> ./src/.libs/mpb.o
> ./src/.libs/bicgstab.o
> ./src/.libs/output_directory.o
> ./src/.libs/material_data.o
> ./src/.libs/time.o
> ./src/.libs/dft_ldos.o
> ./src/.libs/step.o
> ./src/.libs/update_pols.o
> ./src/.libs/random.o
> ./src/.libs/stress.o
> ./src/.libs/libmeep.a
> ./src/material_data.lo
> ./src/dft.o
> ./src/loop_in_chunks.o
> ./src/GDSIIgeom.o
> ./src/integrate.o
> ./src/fields.o
> ./src/structure_dump.o
> ./src/step_db.lo
> ./src/h5file.cpp
> ./src/meepgeom.lo
> ./src/structure.cpp
> ./src/sphere-quad.cpp
> ./src/step_generic_stride1.o
> ./src/fields.lo
> ./src/output_directory.cpp
> ./src/h5fields.cpp
> ./src/monitor.cpp
> ./src/mympi.o
> ./src/dft.lo
> ./src/initialize.cpp
> ./src/sources.o
> ./src/monitor.o
> ./src/sphere-quad.h
> ./src/update_pols.cpp
> ./src/h5fields.lo
> ./src/vec.lo
> ./src/structure.lo
> ./src/dft_ldos.lo
> ./src/mympi.cpp
> ./src/meepgeom.hpp
> ./src/update_pols.lo
> ./src/casimir.o
> ./src/fields_dump.cpp
> ./src/mympi.lo
> ./src/susceptibility.cpp
> ./src/update_eh.o
> ./src/structure_dump.cpp
> ./src/bands.cpp
> ./src/integrate.cpp
> ./src/boundaries.cpp
> ./src/fields.cpp
> ./src/loop_in_chunks.cpp
> ./src/fix_boundary_sources.o
> ./src/material_data.cpp
> ./src/structure.o
> ./src/Makefile.in
> ./src/bicgstab.cpp
> ./src/boundaries.o
> ./src/integrate.lo
> ./src/step_generic.o
> ./src/anisotropic_averaging.o
> ./src/mpb.lo
> ./src/near2far.o
> ./src/fields_dump.lo
> ./src/meepgeom.o
> ./src/energy_and_flux.o
> ./src/dft.cpp
> ./src/random.cpp
> ./src/susceptibility.o
> ./src/casimir.lo
> ./src/Makefile
> ./src/h5file.lo
> ./src/h5file.o
> ./src/meep.hpp
> ./src/update_eh.cpp
> ./src/fields_dump.o
> 

Bug#1074740: marked as done (meep-mpi-default: FTBFS: dh_install: error: missing files, aborting)

[Debian Bug Tracking System]

Your message dated Fri, 12 Jul 2024 23:16:59 +
with message-id 
and subject line Bug#1074740: fixed in meep-mpi-default 1.25.0-3
has caused the Debian Bug report #1074740,
regarding meep-mpi-default: FTBFS: dh_install: error: missing files, aborting
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.)


-- 
1074740: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074740
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: meep-mpi-default
Version: 1.25.0-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240702 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[4]: Entering directory '/<>'
> make[4]: Nothing to be done for 'install-exec-am'.
>  /usr/bin/mkdir -p 
> '/<>/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig'
>  /usr/bin/install -c -m 644 meep.pc 
> '/<>/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig'
> make[4]: Leaving directory '/<>'
> make[3]: Leaving directory '/<>'
> make[2]: Leaving directory '/<>'
> find
> .
> ./autogen.sh
> ./config.h.in
> ./config.status
> ./COPYRIGHT
> ./codemeta.json
> ./AUTHORS
> ./README.md
> ./LICENSE
> ./.travis.yml
> ./meep.pc
> ./src
> ./src/update_eh.lo
> ./src/random.lo
> ./src/GDSIIgeom.lo
> ./src/dft_ldos.cpp
> ./src/multilevel-atom.o
> ./src/energy_and_flux.lo
> ./src/bands.lo
> ./src/array_slice.o
> ./src/initialize.lo
> ./src/step_generic_stride1.lo
> ./src/array_slice.cpp
> ./src/step_generic.cpp
> ./src/loop_in_chunks.lo
> ./src/libmeep.la
> ./src/material_data.hpp
> ./src/vec.o
> ./src/structure_dump.lo
> ./src/sphere_quad
> ./src/bicgstab.lo
> ./src/h5fields.o
> ./src/step_generic_stride1.cpp
> ./src/stress.cpp
> ./src/boundaries.lo
> ./src/bands.o
> ./src/near2far.cpp
> ./src/step_generic.lo
> ./src/integrate2.o
> ./src/time.lo
> ./src/cw_fields.o
> ./src/adjust_verbosity.hpp
> ./src/.libs
> ./src/.libs/multilevel-atom.o
> ./src/.libs/array_slice.o
> ./src/.libs/libmeep.la
> ./src/.libs/vec.o
> ./src/.libs/h5fields.o
> ./src/.libs/bands.o
> ./src/.libs/integrate2.o
> ./src/.libs/libmeep.so
> ./src/.libs/cw_fields.o
> ./src/.libs/dft.o
> ./src/.libs/loop_in_chunks.o
> ./src/.libs/GDSIIgeom.o
> ./src/.libs/integrate.o
> ./src/.libs/fields.o
> ./src/.libs/structure_dump.o
> ./src/.libs/libmeep.lai
> ./src/.libs/step_generic_stride1.o
> ./src/.libs/mympi.o
> ./src/.libs/sources.o
> ./src/.libs/monitor.o
> ./src/.libs/casimir.o
> ./src/.libs/update_eh.o
> ./src/.libs/libmeep.so.30
> ./src/.libs/fix_boundary_sources.o
> ./src/.libs/structure.o
> ./src/.libs/boundaries.o
> ./src/.libs/step_generic.o
> ./src/.libs/libmeep.so.30.0.0
> ./src/.libs/anisotropic_averaging.o
> ./src/.libs/near2far.o
> ./src/.libs/meepgeom.o
> ./src/.libs/energy_and_flux.o
> ./src/.libs/susceptibility.o
> ./src/.libs/h5file.o
> ./src/.libs/fields_dump.o
> ./src/.libs/step_db.o
> ./src/.libs/initialize.o
> ./src/.libs/mpb.o
> ./src/.libs/bicgstab.o
> ./src/.libs/output_directory.o
> ./src/.libs/material_data.o
> ./src/.libs/time.o
> ./src/.libs/dft_ldos.o
> ./src/.libs/step.o
> ./src/.libs/update_pols.o
> ./src/.libs/random.o
> ./src/.libs/stress.o
> ./src/.libs/libmeep.a
> ./src/material_data.lo
> ./src/dft.o
> ./src/loop_in_chunks.o
> ./src/GDSIIgeom.o
> ./src/integrate.o
> ./src/fields.o
> ./src/structure_dump.o
> ./src/step_db.lo
> ./src/h5file.cpp
> ./src/meepgeom.lo
> ./src/structure.cpp
> ./src/sphere-quad.cpp
> ./src/step_generic_stride1.o
> ./src/fields.lo
> ./src/output_directory.cpp
> ./src/h5fields.cpp
> ./src/monitor.cpp
> ./src/mympi.o
> ./src/dft.lo
> ./src/initialize.cpp
> ./src/sources.o
> ./src/monitor.o
> ./src/sphere-quad.h
> ./src/update_pols.cpp
> ./src/h5fields.lo
> ./src/vec.lo
> ./src/structure.lo
> ./src/dft_ldos.lo
> ./src/mympi.cpp
> ./src/meepgeom.hpp
> ./src/update_pols.lo
> ./src/casimir.o
> ./src/fields_dump.cpp
> ./src/mympi.lo
> ./src/susceptibility.cpp
> ./src/update_eh.o
> ./src/structure_dump.cpp
> ./src/bands.cpp
> ./src/integrate.cpp
> ./src/boundaries.cpp
> ./src/fields.cpp
> ./src/loop_in_chunks.cpp
> ./src/fix_boundary_sources.o
> ./src/material_data.cpp
> ./src/structure.o
> ./src/Makefile.in
> ./src/bicgstab.cpp
> ./src/boundaries.o
> ./src/integrate.lo
> ./src/step_generic.o
> ./src/anisotropic_averaging.o
> ./src/mpb.lo
> ./src/near2far.o
> ./src/fields_dump.lo
> ./src/meepgeom.o
> ./src/energy_and_flux.o
> ./src/dft.cpp
> ./src/random.cpp
> ./src/susceptibility.o
> ./src/casimir.lo
> ./src/Makefile
> ./src/h5file.lo
> ./src/h5file.o
> ./src/meep.hpp
> ./src/update_eh.cpp
> 

Bug#1074728: marked as done (meep: FTBFS: dh_install: error: missing files, aborting)

[Debian Bug Tracking System]

Your message dated Fri, 12 Jul 2024 23:16:44 +
with message-id 
and subject line Bug#1074728: fixed in meep 1.25.0-3
has caused the Debian Bug report #1074728,
regarding meep: FTBFS: dh_install: error: missing files, aborting
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.)


-- 
1074728: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074728
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: meep
Version: 1.25.0-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240702 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[4]: Entering directory '/<>'
> make[4]: Nothing to be done for 'install-exec-am'.
>  /usr/bin/mkdir -p 
> '/<>/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig'
>  /usr/bin/install -c -m 644 meep.pc 
> '/<>/debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig'
> make[4]: Leaving directory '/<>'
> make[3]: Leaving directory '/<>'
> make[2]: Leaving directory '/<>'
> rm -f -f debian/tmp/usr/lib/python*/site-packages/meep/adjoint/*.pyc
> rm -f -f debian/tmp/usr/lib/python*/site-packages/meep/adjoint/*.pyo
> rm -f -f debian/tmp/usr/lib/python*/site-packages/meep/*.pyc
> rm -f -f debian/tmp/usr/lib/python*/site-packages/meep/*.pyo
> rm -f -f debian/tmp/usr/lib/python*/site-packages/meep/*.a
> rm -f -f debian/tmp/usr/lib/python*/site-packages/meep/*.la
> rm -f -f debian/tmp/usr/lib/python*/site-packages/meep/mpb/*.pyc
> rm -f -f debian/tmp/usr/lib/python*/site-packages/meep/mpb/*.pyo
> rm -f -f debian/tmp/usr/lib/python*/site-packages/meep/mpb/*.a
> rm -f -f debian/tmp/usr/lib/python*/site-packages/meep/mpb/*.la
> rm -f -f debian/tmp/usr/lib/*/libpympb.la
> rm -f -f debian/tmp/usr/lib/*/libmeep.la
> rm -f -rf debian/tmp/usr/lib/python*/site-packages/meep/__pycache__/
> rm -f -rf debian/tmp/usr/lib/python*/site-packages/meep/adjoint/__pycache__/
> rm -f -rf debian/tmp/usr/lib/python*/site-packages/meep/mpb/__pycache__/
> make[1]: Leaving directory '/<>'
>dh_install
> dh_install: warning: Cannot find (any matches for) "usr/lib/*/libpympb.so.*" 
> (tried in ., debian/tmp)
> 
> dh_install: warning: libmeep30 missing files: usr/lib/*/libpympb.so.*
> dh_install: warning: Cannot find (any matches for) "usr/lib/*/libpympb.so" 
> (tried in ., debian/tmp)
> 
> dh_install: warning: libmeep-dev missing files: usr/lib/*/libpympb.so
> dh_install: warning: Cannot find (any matches for) 
> "usr/lib/python*/site-packages/*" (tried in ., debian/tmp)
> 
> dh_install: warning: python3-meep missing files: 
> usr/lib/python*/site-packages/*
> dh_install: error: missing files, aborting
> make: *** [debian/rules:29: binary] Error 255


The full build log is available from:
http://qa-logs.debian.net/2024/07/02/meep_1.25.0-2_unstable.log

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

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

Debian distribution maintenance software
pp.
Thorsten Alteholz  (supplier of updated meep 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, 11 Jul 2024 22:49:17 +0200
Source: meep
Architecture: source
Version: 1.25.0-3
Distribution: unstable
Urgency: medium
Maintainer: Thorsten Alteholz 
Changed-By: Thorsten 

Bug#1070492: marked as done (mixxx: Tries to use the network during build)

[Debian Bug Tracking System]

Your message dated Fri, 12 Jul 2024 23:18:06 +
with message-id 
and subject line Bug#1070492: fixed in mixxx 2.4.0+dfsg-3
has caused the Debian Bug report #1070492,
regarding mixxx: Tries to use the network during build
to be marked as done.

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

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


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

Package: src:mixxx
Version: 2.4.0+dfsg-2
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
  --- LOG END ---
  error: downloading 
'https://github.com/xsco/libdjinterop/archive/refs/tags/0.20.1.tar.gz' failed
  status_code: 6
  status_string: "Couldn't resolve host name"
  log:
  --- LOG BEGIN ---
  Could not resolve host: github.com

  Closing connection



  --- LOG END ---
  error: downloading 
'https://launchpad.net/~xsco/+archive/ubuntu/djinterop/+sourcefiles/libdjinterop/0.20.1-0ubuntu1/libdjinterop_0.20.1.orig.tar.gz'
 failed
  status_code: 6
  status_string: "Couldn't resolve host name"
  log:
  --- LOG BEGIN ---
  Could not resolve host: launchpad.net

  Closing connection



  --- LOG END ---
  




make[4]: *** [CMakeFiles/libdjinterop.dir/build.make:102: 
libdjinterop-prefix/src/libdjinterop-stamp/libdjinterop-download] Error 1
make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make[3]: *** [CMakeFiles/Makefile2:317: CMakeFiles/libdjinterop.dir/all] Error 2
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make[2]: *** [Makefile:169: all] Error 2
make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu'
dh_auto_build: error: cd obj-x86_64-linux-gnu && make -j2 "INSTALL=install 
--strip-program=true" VERBOSE=1 returned exit code 2
make[1]: *** [debian/rules:21: override_dh_auto_build] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:15: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2


The build was made using the unshare backend of sbuild, which
does not allow network access.

If you need a full build log, it also fails here for the same reason:

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

(X-Debian-Cc: Jochen, as we are tracking all packages which ftbfs with unshare)

Thanks.
--- End Message ---
--- Begin Message ---
Source: mixxx
Source-Version: 2.4.0+dfsg-3
Done: Boyuan Yang 

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated mixxx 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, 12 Jul 2024 17:10:10 -0400
Source: mixxx
Architecture: source
Version: 2.4.0+dfsg-3
Distribution: unstable
Urgency: high
Maintainer: Debian Multimedia Maintainers 
Changed-By: Boyuan Yang 
Closes: 1070492
Changes:
 mixxx (2.4.0+dfsg-3) unstable; urgency=high
 .
   * Team upload.
   * debian/patches/0005-Allow-libdjinterop-0.21.0.patch: Add patch to allow
 libdjinterop 0.21.0.
   * debian/control:
 + Add missing build-dependency on libdjinterop-dev. (Closes: #1070492)
 + Remove hardcoded build-dependency on libvamp-*. Use the development
   package vamp-plugin-sdk instead to implicitly pull them in and to
   avoid the t64 library suffix problem.
Checksums-Sha1:
 6459d444795b89ae85c514a7cc0dc61f6ee6e451 3018 mixxx_2.4.0+dfsg-3.dsc
 a136b9cb1c432a3854a3f4c8756ce006a2e378f4 22070072 mixxx_2.4.0+dfsg.orig.tar.xz
 be9297b67ec2135c4a6fdc220f98b11a376be7bd 28244 mixxx_2.4.0+dfsg-3.debian.tar.xz
 7388d37742eeb1c4a963075885fed6053183eae0 18855 
mixxx_2.4.0+dfsg-3_amd64.buildinfo
Checksums-Sha256:
 5592e9161f9f9713b0658f0f0f121177d067857de60285c71e2d2dbd8cd2d390 3018 

Bug#1060499: marked as done (gnome-remote-desktop: Please switch Build-Depends to systemd-dev)

[Debian Bug Tracking System]

Your message dated Fri, 12 Jul 2024 23:08:52 +
with message-id 
and subject line Bug#1060499: fixed in gnome-remote-desktop 46.3-2
has caused the Debian Bug report #1060499,
regarding gnome-remote-desktop: Please switch Build-Depends to systemd-dev
to be marked as done.

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

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


-- 
1060499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060499
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-remote-desktop
Version: 44.2-6
Severity: normal
User: pkg-systemd-maintain...@lists.alioth.debian.org
Usertags: systemd-dev

Hi,

your package gnome-remote-desktop declares a Build-Depends on systemd
and/or udev.

In most cases, this build dependency is added to get the paths that
are defined in udev.pc or systemd.pc (via pkgconfig).

Since systemd_253-2 [1], these two pkgconfig files have been split
into a separate package named systemd-dev. This package is arch:all,
so even available on non-Linux architectures, which will simplify the
installation of upstream provided service files / udev rules.

To not make existing source packages FTBFS, the systemd and udev
package have a Depends: systemd-dev. This dependency will be removed
at some point though before trixie is released. Once this happens,
this issue will be bumped to RC.

Please update your build dependencies accordingly at your earliest
convenience.

If all you need is the systemd.pc or udev.pc pkgconfig file, please
replace any systemd or udev Build-Depends with systemd-dev. In most
cases that should be sufficient. If your package needs further
resources from systemd or udev to build successfully, it's fine to
keep those Build-Depends in addition to systemd-dev.

To ease stable backports, a version of systemd with those changes is
provided via bookworm-backports.

In case you have further questions, please contact the systemd team
at .

On behalf of the systemd team, Michael

[1]
https://salsa.debian.org/systemd-team/systemd/-/merge_requests/196 
--- End Message ---
--- Begin Message ---
Source: gnome-remote-desktop
Source-Version: 46.3-2
Done: Jeremy Bícha 

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

Debian distribution maintenance software
pp.
Jeremy Bícha  (supplier of updated gnome-remote-desktop 
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, 12 Jul 2024 18:31:14 -0400
Source: gnome-remote-desktop
Built-For-Profiles: noudeb
Architecture: source
Version: 46.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bícha 
Closes: 1029451 1060499 1070119
Launchpad-Bugs-Fixed: 2038108 2062076 206 2066306 2072596
Changes:
 gnome-remote-desktop (46.3-2) unstable; urgency=medium
 .
   * Release to unstable
 .
 gnome-remote-desktop (46.3-1) experimental; urgency=medium
 .
   * New upstream release
   * Fix nocheck build
   * Drop obsolete postinst rules
   * Use custom postinst to fix long delay when first installing 46
 (Closes: #1070119) (LP: #2072596)
 .
 gnome-remote-desktop (46.2-1) experimental; urgency=medium
 .
   * SECURITY UPDATE: New upstream release (LP: #2066306)
 - CVE-2024-5148 Limit login screen->user session handover access
   to appropriate user. This issue only affected the 46 series.
 - Various security hardening improvements
 - Potential crasher fix
 - Improved disconnection messages
 - Broader client compatibility support
 .
 gnome-remote-desktop (46.1-4) experimental; urgency=medium
 .
   * Run dh_installtmpfiles, then dh_installsysfiles, then dh_installtmpfiles
 .
 gnome-remote-desktop (46.1-3) experimental; urgency=medium
 .
   * Ensure that dh_installtmpfiles is run before dh_installsysusers
   * Temporarily ignore build test failures on Debian
 .
 gnome-remote-desktop (46.1-2) experimental; urgency=medium
 .
   * Opt into Salsa CI
   * Simplify running dh_auto_test
   * Run dh_installsysusers & dh_installtmpfiles (Closes: #1070119)
 (LP: #206)
 .
 gnome-remote-desktop (46.1-1) experimental; 

Bug#1074677: marked as done (porechop: FTBFS: ModuleNotFoundError: No module named 'distutils')

[Debian Bug Tracking System]

Your message dated Fri, 12 Jul 2024 22:41:13 +
with message-id 
and subject line Bug#1074677: fixed in porechop 0.2.4+dfsg-6
has caused the Debian Bug report #1074677,
regarding porechop: FTBFS: ModuleNotFoundError: No module named 'distutils'
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.)


-- 
1074677: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074677
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: porechop
Version: 0.2.4+dfsg-5
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240702 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
>  debian/rules clean
> dh clean --with python3 --buildsystem pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:311: python3.12 setup.py clean 
> Traceback (most recent call last):
>   File "/<>/setup.py", line 14, in 
> from distutils.command.build import build
> ModuleNotFoundError: No module named 'distutils'
> E: pybuild pybuild:389: clean: plugin distutils failed with: exit code=1: 
> python3.12 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.12 returned 
> exit code 13
> make: *** [debian/rules:16: clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2024/07/02/porechop_0.2.4+dfsg-5_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240702;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240702=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: porechop
Source-Version: 0.2.4+dfsg-6
Done: Étienne Mollier 

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

Debian distribution maintenance software
pp.
Étienne Mollier  (supplier of updated porechop 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, 12 Jul 2024 23:49:53 +0200
Source: porechop
Architecture: source
Version: 0.2.4+dfsg-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Étienne Mollier 
Closes: 1074677
Changes:
 porechop (0.2.4+dfsg-6) unstable; urgency=medium
 .
   * Team upload.
   * d/rules: remove the now broken workaround against setuptools 50 bug.
 (Closes: #1074677)
Checksums-Sha1:
 7cc159d6b7c04e9cabb9f749099d7c13c91ff2d2 2215 porechop_0.2.4+dfsg-6.dsc
 bb290af32705362aa5ff264977de724eab70f86e 6152 
porechop_0.2.4+dfsg-6.debian.tar.xz
Checksums-Sha256:
 f891af984b0debaad6d5d901803e76bf334d389d232497e64b69036a21b6d172 2215 
porechop_0.2.4+dfsg-6.dsc
 4adf0600768b96d2efc1cda4c87031d01b09796b8da7cd09ccde621d3bd34807 6152 
porechop_0.2.4+dfsg-6.debian.tar.xz
Files:
 ef77e9d3b227d316736af1ca21a880c7 2215 science optional 
porechop_0.2.4+dfsg-6.dsc
 81be161a3f63d898d8cbf0fab2d09398 6152 science optional 
porechop_0.2.4+dfsg-6.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEj5GyJ8fW8rGUjII2eTz2fo8NEdoFAmaRpbwUHGVtb2xsaWVy
QGRlYmlhbi5vcmcACgkQeTz2fo8NEdq+fw//UrzWnQtiNhpzKMQiN9w0GRJ99JGf
fTOLxFVI0+TSIt7x8Rhhr69cRNzTgVgPZQf77/KOzPDG1uBFJCqza89Yqg9yXSqm
8wggPQPue7V/p7YMiaY7o513kS61NK65ikS9S0ra36ru70FDfXgetfGVygNCXdMd
AFfA4+/tZ9P+a9XMp8mV+VdtSrFnnZjgJg3LVmCe/J5dk0/6WY1+daZugi2VDbpG
0kiuk3XIBQKMji17tq2CK2m5gOHAvkAum9/ZseJDg1pXH+BY6ScUo9Lc3jzspO9d
jDMwIRfaIt4/V4jEMQwDkVImGkczCSgmyxxHkYRQs5+25MTZ97vucKhrYoIA8u9J
+ppSuW79BPpfO1xXkdUMYBV2O1eAM+A5cx4qe1jkJxN5SSGJ9Ch/8aWJsDYBguMN
mNxmkJh5qu8fYy0RvluO9sDlAMDSmL9Ncxhzl8EOc4cP2Sg2sqEGqNv50YJp7r6k

Bug#1065860: marked as done (fonts-cantarell: Please drop dependencies on python3-distutils)

[Debian Bug Tracking System]

Your message dated Fri, 12 Jul 2024 21:36:21 +
with message-id 
and subject line Bug#1065860: fixed in fonts-cantarell 0.303.1-2
has caused the Debian Bug report #1065860,
regarding fonts-cantarell: Please drop dependencies on python3-distutils
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.)


-- 
1065860: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065860
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fonts-cantarell
Version: 0.303.1-1
Severity: important
Tags: ftbfs trixie sid
User: debian-pyt...@lists.debian.org
Usertags: python3.12

Hi Maintainer

This package has dependencies, build-dependencies and/or autopkgtest
dependencies on python3-distutils.  The python3-distutils binary
package will soon be dropped from python3-stdlib-extensions.

In fact, there is no module for Python 3.12 in python3-distutils, so
these dependencies may already be unnecessary.

Regards
Graham
--- End Message ---
--- Begin Message ---
Source: fonts-cantarell
Source-Version: 0.303.1-2
Done: Jeremy Bícha 

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

Debian distribution maintenance software
pp.
Jeremy Bícha  (supplier of updated fonts-cantarell 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, 12 Jul 2024 16:36:16 -0400
Source: fonts-cantarell
Built-For-Profiles: noudeb
Architecture: source
Version: 0.303.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Fonts Task Force 
Changed-By: Jeremy Bícha 
Closes: 1065860
Changes:
 fonts-cantarell (0.303.1-2) unstable; urgency=medium
 .
   [ Emmanuel Arias ]
   * Drop python3-distutils from Build-Depends (Closes: #1065860)
 .
   [ Debian Janitor ]
   * Fix some issues reported by lintian
   * Remove an obsolete maintscript entry.
   * Remove constraints unnecessary since buster (oldstable)
 .
   [ Jeremy Bícha ]
   * Bump Standards-Version to 4.7.0
Checksums-Sha1:
 6d858b7bb472ac7a243c629a3a4aba5b1b86f517 2187 fonts-cantarell_0.303.1-2.dsc
 ef7d0206f41a6775046b7944f75a5319a8fed105 7592 
fonts-cantarell_0.303.1-2.debian.tar.xz
 cce672e00428e48fdbc0a303b0465d683e2114a2 7247 
fonts-cantarell_0.303.1-2_source.buildinfo
Checksums-Sha256:
 cf4a77f7c92f011b3de321fe2d13bdfb3c87de81cb9fad569ac8999feb575d8a 2187 
fonts-cantarell_0.303.1-2.dsc
 8e2969c10902672b908b64db39f69398e0304a2595370a339948e6ed2d25706c 7592 
fonts-cantarell_0.303.1-2.debian.tar.xz
 64027662918f7013f8962fafdde6430a993bc5d5f74ddbbde5bbc34b3f7eb72d 7247 
fonts-cantarell_0.303.1-2_source.buildinfo
Files:
 d73ef21d9f68503d09ef68a6d62058f1 2187 fonts optional 
fonts-cantarell_0.303.1-2.dsc
 c793ae40eca33986338f522d9588f17f 7592 fonts optional 
fonts-cantarell_0.303.1-2.debian.tar.xz
 d7b96dfc294fc4d4ca632bf108ef92f4 7247 fonts optional 
fonts-cantarell_0.303.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmaRmtsACgkQ5mx3Wuv+
bH0oJg//SaiB2d1BGTmcefBz//UWuQOg2ujndBFP4e3uwIYB7CGp1nbEi7SHbHKz
fJe46N9ytgpmAJXljWS5iMaPQ0jJ4ooCtAnJvkGwXZBiGHxinjVBqkDqApvUyXqf
5lpNTBXhAC74sdy6AvH8O3gp9gN9xhz9y3xu3ANA1thAwb6ChnIw1jfy6tfeVylR
4Ppov4kF0+O/9vsfOjISm82jopUi27raI8l+TEV2XH6pC8zs/HwlJi9RjkjyXvqu
1q9nPZwFsm0twV+OifOClZwfNnGRTpH55t1efrH/95dzUWNJ5hRYyc9iW74FMTZ9
md/FLSE3F2w7G//PNgppQoTxIDdKhtRfHou/X5UEvEFnlZ25LemITtg1SluesUQz
5Myh6QxCbi6GYs15BZ7uKPZyGpCgFAjrzogZutatOHQ8vsISUwoENvlEDe0uW7Sp
ewCOKjzHTC3fkG96TwCAOak9/upXcrA0hxcQtJVYMfpfzITrVW7JT7kjwi+sTt6M
+PpcpRMKN9PHSvJEFc5OzfYFaa9uYHWRdOVO785zEffo4DeU1Nw+IJHWlgZB13rG
rfKsTRbZDjvNQM4KkaHLP3RAfL03nFmgB8ounuUa4pmUaTZmumgQZkcsLUTOHrck
7+O1BUAm/xlkvoRjd6YSh7fFmcpQhPZpP/PvAT1O1wUzLW5Y4qw=
=ISrE
-END PGP SIGNATURE-



pgpjSHcVbhZi0.pgp
Description: PGP signature
--- End Message ---

Bug#1076234: lammps: FTBFS with mpich as default MPI provider on armel, armhf: Fatal error in internal_Comm_set_errhandler: Invalid communicator

[Sebastian Ramacher]

Source: lammps
Version: 20240207+dfsg-1.1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=lammps=armel=20240207%2Bdfsg-1.1%2Bb4=1720745050=0

LD_LIBRARY_PATH=/<>/debian/tmp/usr/lib/arm-linux-gnueabi \
  
PYTHONPATH=/<>/debian/python3-lammps/usr/lib/python3.12/dist-packages:${PYTHONPATH}
 \
  python3 demo.py
ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be preloaded 
(cannot open shared object file): ignored.
Fatal error in internal_Comm_set_errhandler: Invalid communicator, error stack:
internal_Comm_set_errhandler(41812): MPI_Comm_set_errhandler(comm=0xee8f6b74, 
errh=0xee8f7718) failed
internal_Comm_set_errhandler(41770): Invalid communicator
[unset]: PMIU_write error; fd=-1 buf=:cmd=abort exitcode=336162565 
message=Fatal error in internal_Comm_set_errhandler: Invalid communicator, 
error stack:
internal_Comm_set_errhandler(41812): MPI_Comm_set_errhandler(comm=0xee8f6b74, 
errh=0xee8f7718) failed
internal_Comm_set_errhandler(41770): Invalid communicator
:
system msg for write_line failure : Bad file descriptor
make[1]: *** [debian/rules:131: execute_before_dh_python3-arch] Error 5
make[1]: Leaving directory '/<>'
make: *** [debian/rules:13: binary-arch] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned 
exit status 2

Cheers
-- 
Sebastian Ramacher

Bug#1076233: liggghts: FTBFS with mpich as default MPI provider on 32 bit architectures: [mpiexec@arm-conova-03] main (mpiexec/mpiexec.c:54): error parsing parameters

[Sebastian Ramacher]

Source: liggghts
Version: 3.8.0+repack1-10
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=liggghts=armel=3.8.0%2Brepack1-10%2Bb1=1720740071=0

make[1]: Leaving directory '/<>/debian/build'
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
mkdir test
cp -r examples/LIGGGHTS/Tutorials_public/heatTransfer_1/* test/
cd test; mpirun -np 2 --allow-run-as-root --oversubscribe 
/<>/debian/build/src/liggghts < in.heatGran
[mpiexec@arm-conova-03] match_arg (lib/utils/args.c:166): unrecognized argument 
allow-run-as-root
[mpiexec@arm-conova-03] HYDU_parse_array (lib/utils/args.c:181): argument 
matching returned error
[mpiexec@arm-conova-03] parse_args (mpiexec/get_parameters.c:313): error 
parsing input array
[mpiexec@arm-conova-03] HYD_uii_mpx_get_parameters 
(mpiexec/get_parameters.c:48): unable to parse user arguments
[mpiexec@arm-conova-03] main (mpiexec/mpiexec.c:54): error parsing parameters
make[1]: *** [debian/rules:17: override_dh_auto_test] Error 255

Cheers
-- 
Sebastian Ramacher

Bug#1076232: fenics-dolfinx: FTBFS with mpich as default MPI provier on 32 bit architectures: E: pybuild pybuild:435: plugin pyproject failed: exit code=1: cd /<>/.pybuild/cpython3_3.12_d

[Sebastian Ramacher]

Source: fenics-dolfinx
Version: 1:0.8.0-10
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=fenics-dolfinx=armel=1%3A0.8.0-10%2Bb1=1720783021=0

/<>/debian/tmp-real/usr/include/dolfinx/refinement/plaza.h:536:60: 
note: parameter passing for argument of type ‘std::span’ changed in GCC 7.1
[100%] Linking CXX shared module cpp.cpython-312-arm-linux-gnueabi.so
/usr/bin/cmake -E cmake_link_script CMakeFiles/cpp.dir/link.txt --verbose=1
/usr/bin/c++ -fPIC -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -isystem /<>/debian/tmp-real/usr/include 
-O3 -DNDEBUG -Wl,-s -Wl,--gc-sections -Wl,-z,relro -shared  -o 
cpp.cpython-312-arm-linux-gnueabi.so 
CMakeFiles/cpp.dir/dolfinx/wrappers/dolfinx.cpp.o 
CMakeFiles/cpp.dir/dolfinx/wrappers/assemble.cpp.o 
CMakeFiles/cpp.dir/dolfinx/wrappers/common.cpp.o 
CMakeFiles/cpp.dir/dolfinx/wrappers/fem.cpp.o 
CMakeFiles/cpp.dir/dolfinx/wrappers/geometry.cpp.o 
CMakeFiles/cpp.dir/dolfinx/wrappers/graph.cpp.o 
CMakeFiles/cpp.dir/dolfinx/wrappers/io.cpp.o 
CMakeFiles/cpp.dir/dolfinx/wrappers/la.cpp.o 
CMakeFiles/cpp.dir/dolfinx/wrappers/log.cpp.o 
CMakeFiles/cpp.dir/dolfinx/wrappers/mesh.cpp.o 
CMakeFiles/cpp.dir/dolfinx/wrappers/petsc.cpp.o 
CMakeFiles/cpp.dir/dolfinx/wrappers/refinement.cpp.o  
-Wl,-rpath,/<>/debian/tmp-real/usr/lib/arm-linux-gnueabi:/usr/lib/arm-linux-gnueabi/mpich/lib:/usr/lib/arm-linux-gnueabi/hdf5/mpich:/usr/lib/slepcdir/slepc3.20/arm-linux-gnueabi-real/lib:/usr/lib/petscdir/petsc3.20/arm-linux-gnueabi-real/lib:
 libnanobind-static.a 
/<>/debian/tmp-real/usr/lib/arm-linux-gnueabi/libdolfinx_real.so.0.8.0
 /usr/lib/arm-linux-gnueabi/libpugixml.so.1.14 
/usr/lib/arm-linux-gnueabi/libbasix.so.0.8.0 
/usr/lib/arm-linux-gnueabi/libboost_timer.so.1.83.0 
/usr/lib/arm-linux-gnueabi/mpich/lib/libmpichcxx.so 
/usr/lib/arm-linux-gnueabi/mpich/lib/libmpich.so 
/usr/lib/arm-linux-gnueabi/hdf5/mpich/libhdf5.so 
/usr/lib/slepcdir/slepc3.20/arm-linux-gnueabi-real/lib/libslepc_real.so 
/usr/lib/petscdir/petsc3.20/arm-linux-gnueabi-real/lib/libpetsc_real.so
gmake[4]: Leaving directory '/tmp/tmpau7h4lpa/build'
[100%] Built target cpp
gmake[3]: Leaving directory '/tmp/tmpau7h4lpa/build'
/usr/bin/cmake -E cmake_progress_start /tmp/tmpau7h4lpa/build/CMakeFiles 0
gmake[2]: Leaving directory '/tmp/tmpau7h4lpa/build'

*** Installing project into wheel...
-- Install configuration: "Release"
-- Installing: 
/tmp/tmpau7h4lpa/wheel/platlib/dolfinx/cpp.cpython-312-arm-linux-gnueabi.so
-- Set non-toolchain portion of runtime path of 
"/tmp/tmpau7h4lpa/wheel/platlib/dolfinx/cpp.cpython-312-arm-linux-gnueabi.so" 
to 
"/<>/debian/tmp-real/usr/lib/arm-linux-gnueabi:/usr/lib/arm-linux-gnueabi/mpich/lib:/usr/lib/arm-linux-gnueabi/hdf5/mpich:/usr/lib/slepcdir/slepc3.20/arm-linux-gnueabi-real/lib:/usr/lib/petscdir/petsc3.20/arm-linux-gnueabi-real/lib"
*** Making wheel...
*** Created fenics_dolfinx-0.8.0-cp312-cp312-linux_arm.whl...
Successfully built fenics_dolfinx-0.8.0-cp312-cp312-linux_arm.whl
I: pybuild plugin_pyproject:144: Unpacking wheel built for python3.12 with 
"installer" module
I: pybuild plugin_pyproject:178: Copying package built for python3.12 to destdir
I: pybuild base:311: cd 
/<>/.pybuild/cpython3_3.12_dolfinx-real/build; python3.12 -m 
pytest --durations=20 -k "not ( test_cube_distance )"
E: pybuild pybuild:435: plugin pyproject failed: exit code=1: cd 
/<>/.pybuild/cpython3_3.12_dolfinx-real/build; python3.12 -m 
pytest --durations=20 -k "not ( test_cube_distance )"
make[1]: *** [debian/rules:192: debian/tmp-real] Error 14
make[1]: Leaving directory '/<>'
make: *** [debian/rules:161: binary-arch] Error 2

Cheers
-- 
Sebastian Ramacher

Bug#1065860: fonts-cantarell: Please drop dependencies on python3-distutils

[Fabian Greffrath]

Hi Emmanuel,

Am Freitag, dem 12.07.2024 um 17:23 -0300 schrieb Emmanuel Arias:
> Please if you have any objection or you want to do any change please
> let
> me know.

no objections, please feel free to upload asap.

Thanks,

 - Fabian



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

Processed: Bug#1065860 marked as pending in fonts-cantarell

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1065860 [src:fonts-cantarell] fonts-cantarell: Please drop dependencies on 
python3-distutils
Added tag(s) pending.

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

Bug#1065860: marked as pending in fonts-cantarell

[Jeremy Bícha]

Control: tag -1 pending

Hello,

Bug #1065860 in fonts-cantarell 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/fonts-team/fonts-cantarell/-/commit/7da9a231c56fe2048cba110f9b6cf8f31c361632


Drop python3-distutils from Build-Depends

Closes: #1065860


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1065860

Bug#1065860: fonts-cantarell: Please drop dependencies on python3-distutils

[Jeremy Bícha]

On Fri, Jul 12, 2024 at 4:23 PM Emmanuel Arias  wrote:
> I'm going to upload in DELAYED/3-days a NMU to fix this RC Bug. I attach
> the patch that I applied.
>
> Please if you have any objection or you want to do any change please let
> me know.

Thank you for the ping. I'll upload now since we had some other
changes committed to Salsa.

Thank you,
Jeremy Bícha

Processed: tagging 1065860

[Debian Bug Tracking System]

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

> tags 1065860 + patch
Bug #1065860 [src:fonts-cantarell] fonts-cantarell: Please drop dependencies on 
python3-distutils
Added tag(s) patch.
> thanks
Stopping processing here.

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

Processed: tagging 1065871

[Debian Bug Tracking System]

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

> tags 1065871 + patch
Bug #1065871 [src:grokevt] grokevt: Please drop dependencies on 
python3-distutils
Added tag(s) patch.
> thanks
Stopping processing here.

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

Processed: tagging 1065849

[Debian Bug Tracking System]

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

> tags 1065849 + patch
Bug #1065849 [src:docker-pycreds] docker-pycreds: Please drop dependencies on 
python3-distutils
Added tag(s) patch.
> thanks
Stopping processing here.

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

Processed: tagging 1065837

[Debian Bug Tracking System]

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

> tags 1065837 + patch
Bug #1065837 [src:cappuccino] cappuccino: Please drop dependencies on 
python3-distutils
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#1065860: fonts-cantarell: Please drop dependencies on python3-distutils

[Emmanuel Arias]

Dear maintainers,

I'm going to upload in DELAYED/3-days a NMU to fix this RC Bug. I attach
the patch that I applied.

Please if you have any objection or you want to do any change please let
me know.

-- 
cheers,
Emmanuel Arias

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  eam...@debian.org
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: 13796755BBC72BB8ABE2AEB5 FA9DEC5DE11C63F1
 
 ⠈⠳⣄


signature.asc
Description: PGP signature

Bug#1065860: fonts-cantarell: Please drop dependencies on python3-distutils

[Emmanuel Arias]

Sorry I forgot attach the patch


-- 
cheers,
Emmanuel Arias

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  eam...@debian.org
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: 13796755BBC72BB8ABE2AEB5 FA9DEC5DE11C63F1
 
 ⠈⠳⣄
diff -Nru fonts-cantarell-0.303.1/debian/changelog fonts-cantarell-0.303.1/debian/changelog
--- fonts-cantarell-0.303.1/debian/changelog	2022-06-12 05:19:03.0 -0300
+++ fonts-cantarell-0.303.1/debian/changelog	2024-07-12 07:40:17.0 -0300
@@ -1,3 +1,11 @@
+fonts-cantarell (0.303.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * d/control: Remove python3-distutils from Build Dependency
+(Closes: #1065860).
+
+ -- Emmanuel Arias   Fri, 12 Jul 2024 07:40:17 -0300
+
 fonts-cantarell (0.303.1-1) unstable; urgency=medium
 
   [ Fabian Greffrath ]
diff -Nru fonts-cantarell-0.303.1/debian/control fonts-cantarell-0.303.1/debian/control
--- fonts-cantarell-0.303.1/debian/control	2022-06-12 05:19:03.0 -0300
+++ fonts-cantarell-0.303.1/debian/control	2024-07-12 07:40:17.0 -0300
@@ -11,7 +11,6 @@
  debhelper-compat (= 13),
  meson,
  pkg-config,
- python3-distutils
 Build-Depends-Indep:
  afdko-bin,
  appstream,


signature.asc
Description: PGP signature

Bug#1075785: marked as done (exim4: CVE-2024-39929: Incorrect parsing of multiline rfc2231 header filename)

[Debian Bug Tracking System]

Your message dated Fri, 12 Jul 2024 19:55:58 +
with message-id 
and subject line Bug#1075785: fixed in exim4 4.94.2-7+deb11u3
has caused the Debian Bug report #1075785,
regarding exim4: CVE-2024-39929: Incorrect parsing of multiline rfc2231 header 
filename
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.)


-- 
1075785: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075785
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: exim4
Version: 4.97-8
Severity: grave
Tags: security upstream
Justification: user security hole
Forwarded: https://bugs.exim.org/show_bug.cgi?id=3099
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for exim4.

CVE-2024-39929[0]:
| Exim through 4.97.1 misparses a multiline RFC 2231 header filename,
| and thus remote attackers can bypass a $mime_filename extension-
| blocking protection mechanism, and potentially deliver executable
| attachments to the mailboxes of end users.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2024-39929
https://www.cve.org/CVERecord?id=CVE-2024-39929
[1] https://bugs.exim.org/show_bug.cgi?id=3099#c4

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: exim4
Source-Version: 4.94.2-7+deb11u3
Done: Andreas Metzler 

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

Debian distribution maintenance software
pp.
Andreas Metzler  (supplier of updated exim4 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 09 Jul 2024 11:01:33 +0200
Source: exim4
Architecture: source
Version: 4.94.2-7+deb11u3
Distribution: bullseye-security
Urgency: medium
Maintainer: Exim4 Maintainers 
Changed-By: Andreas Metzler 
Closes: 1075785
Changes:
 exim4 (4.94.2-7+deb11u3) bullseye-security; urgency=medium
 .
* Fix parsing of multiline RFC 2231 header filename parameter in mime ACL.
  CVE-2024-39929 Closes: #1075785
Checksums-Sha1: 
 32bb8e7bcbb47d04a7b8be452e376b106603574c 2927 exim4_4.94.2-7+deb11u3.dsc
 eba8e6b4f9409f79c68c36128f5d3829c4f8710e 492832 
exim4_4.94.2-7+deb11u3.debian.tar.xz
Checksums-Sha256: 
 ba45fd95955c70a3ec1b5b8e5f59435d36f139760addf5a3050097e96e1ca1e1 2927 
exim4_4.94.2-7+deb11u3.dsc
 1c3aecf5c6fcb89d8a9708f7ffcce6de8745b30413606ea92f4075e5c907c94a 492832 
exim4_4.94.2-7+deb11u3.debian.tar.xz
Files: 
 9ae0c348e9a61998e6df24cd7c653a25 2927 mail standard exim4_4.94.2-7+deb11u3.dsc
 084e353c36450cbc2e105fb011716e13 492832 mail standard 
exim4_4.94.2-7+deb11u3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE0uCSA5741Jbt9PpepU8BhUOCFIQFAmaNFPMACgkQpU8BhUOC
FITjvw/+KiQtKZ1ZGxrjU8R4KN/F/+9DnHBrNxSKaX7LL66EtoerlHjbwArvQi4i
v7r0j/qincI4YtZlSy08xduMFT1pYA/4443cWgG0ouDvIJgLHgZAmDSH2MoGyOYI
2Fg0eio1Rcb3sY6hT1wVdAkIgh/Mpnug/yCaibg3rFrOabSleqSnmAF2MT3QZ1En
S/B4yS3/A8dSmatzUgx75YSRW5adiia821YLVrde7xtWSSlRnHLegZA1DT1rjeH+
+tn/DsTEU+XR4wdqD/yOfLECmu1qDyfJduZwY4QJ35+M9+N3/RYIdt2kH+zK0O2k
DGK/UUnL9AkBxYA0wh4iePjgT3F0lClUsstgmMdkxe8OCon45Vik0VrvyAvbWLZw
rHRm4urS1bgRknywJ7bk4uKtoveY3ItBgxqA1PHTmZsPbj5d6nqi43lE/OM1RxS7
r2Q82mGS8cxE4XL/1zlJm9SVRVIUuH9m4lvZU5ePEsEMefYB03bMx1DtenAM/gVr
5x1CMeCRMUSol8UP9+LLVDtgaZF6aQSLUqd9wBEKgBVuO0wA4zjQbFnw5NpqbJGC
p4CoSuS+wUXdAHHHXnKEDwvBOjNKK7BCy2/lvk9+zc9AE3WR/tZWWJr7Hd0E4Luh
bN+YgzOwicp/ylWBlPF26GUxCaLIY8U4hhw959KVWXxzKhtBRV8=
=tc34
-END PGP SIGNATURE-



pgpsxn2JQNdfR.pgp
Description: PGP signature
--- End Message ---

Bug#1076229: libqt5webview5: Cannot be installed due to missing dependency

[Dmitry Shachnev]

Hi Robert!

On Fri, Jul 12, 2024 at 09:18:16PM +0200, Robert Griebl wrote:
> Package: libqt5webview5
> Severity: grave
> Justification: renders package unusable
> X-Debbugs-Cc: rob...@griebl.org
>
> Dear Maintainer,
>
> This package is used in KDE's "discover" Package Installer, which is
> not installable anymore now.
>
> $ agi libqt5webview5
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
>
> Unsatisfied dependencies:
>  libqt5webview5 : Depends: qtwebengine-abi-5-15-16 but it is not installable
> Error: Unable to correct problems, you have held broken packages

We are in a transition (see #1075964), so it's expected that packages are
temporarily uninstallable. This will be resolved in a day or two, hopefully.

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#1075785: marked as done (exim4: CVE-2024-39929: Incorrect parsing of multiline rfc2231 header filename)

[Debian Bug Tracking System]

Your message dated Fri, 12 Jul 2024 19:55:06 +
with message-id 
and subject line Bug#1075785: fixed in exim4 4.96-15+deb12u5
has caused the Debian Bug report #1075785,
regarding exim4: CVE-2024-39929: Incorrect parsing of multiline rfc2231 header 
filename
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.)


-- 
1075785: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075785
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: exim4
Version: 4.97-8
Severity: grave
Tags: security upstream
Justification: user security hole
Forwarded: https://bugs.exim.org/show_bug.cgi?id=3099
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for exim4.

CVE-2024-39929[0]:
| Exim through 4.97.1 misparses a multiline RFC 2231 header filename,
| and thus remote attackers can bypass a $mime_filename extension-
| blocking protection mechanism, and potentially deliver executable
| attachments to the mailboxes of end users.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2024-39929
https://www.cve.org/CVERecord?id=CVE-2024-39929
[1] https://bugs.exim.org/show_bug.cgi?id=3099#c4

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: exim4
Source-Version: 4.96-15+deb12u5
Done: Andreas Metzler 

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

Debian distribution maintenance software
pp.
Andreas Metzler  (supplier of updated exim4 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 09 Jul 2024 10:53:35 +0200
Source: exim4
Architecture: source
Version: 4.96-15+deb12u5
Distribution: bookworm-security
Urgency: high
Maintainer: Exim4 Maintainers 
Changed-By: Andreas Metzler 
Closes: 1075785
Changes:
 exim4 (4.96-15+deb12u5) bookworm-security; urgency=high
 .
   * Fix parsing of multiline RFC 2231 header filename parameter in mime ACL.
 CVE-2024-39929 Closes: #1075785
Checksums-Sha1: 
 8bea1cc5cdfb359fbb50fd2c061e36aa439aa4c5 2923 exim4_4.96-15+deb12u5.dsc
 85c76962802389c6a5abe9e61d926273c8f8d31c 510812 
exim4_4.96-15+deb12u5.debian.tar.xz
Checksums-Sha256: 
 4b0857a01dd265cf7100284205b33610c3d7a803f5bc22d2df1e32c5afc685f6 2923 
exim4_4.96-15+deb12u5.dsc
 18dc015a8088eb83c8b3a60a710d4d701b5227c5234bf469d76d0358cceb96c4 510812 
exim4_4.96-15+deb12u5.debian.tar.xz
Files: 
 3c80308765d1f7715037d50b88cc0019 2923 mail standard exim4_4.96-15+deb12u5.dsc
 42bd8d2104290674fcf7722a9da91ae4 510812 mail standard 
exim4_4.96-15+deb12u5.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE0uCSA5741Jbt9PpepU8BhUOCFIQFAmaNFPYACgkQpU8BhUOC
FIQOOA/9E5XRwbGZs7ermqn6x5ggYLkLyXCyvalCKwpTrr2VgfKzqGZRhL2sCtbf
roT1b/VgGt6iIGvNYIpcRNfe2k+jWLL4wQ7H/P+HagskP1yQKViButWEy29TkPxe
tu/QIZmfa6f5rF+hKrSzgaQPbkDkdiJnW2XwEnh1sdA2+PnB1onMByLAhBg/QZ9i
XnkOJonR+a+uTVo9XPnlro9Yb6I94q2DzUaPMnPLRF5wyNu+PbFEVS+e7RMNCTHL
pOPrPUe+UL6U7pZN+u7IvX14g1XduvCnHE5BuzY/aWpAwe+9+yJfq2HsIUMzhytG
0EDHGCdWP4UQkD5VMc8XIIJAcgrlY8g/TLpRRIWEH4lKmbqRKfXCnT+D/6HSz7Dw
4lgu/2b8z83jEKknskZNGJsk/gaJyvNEFpyfVzFITmN5U9MJXWEJZVtzYgfWgMH0
DVJlMjypvGQnORgpbTUX6P9ArhV1iFPz2LtXmz4/sS3xFjGSrMbC4sG+vxy/vMWo
q1CH8I7RYqwAV5G0tK5VzDVPWFdrVRuIy0CnAPxsh11cGsswO1esxxrCaTwNVnvC
1QfHIadI4RKuwziTxOJHdzIOXhHc/q5NQQHFaVQYkLrnlF0XoSzupX74VuNEq681
rlLPR/Y0zlv4im9iUi1uJUJhOC58KMGESqfivAGUlPegn5dUPP8=
=9s4q
-END PGP SIGNATURE-



pgpH8aQxLOry0.pgp
Description: PGP signature
--- End Message ---

Bug#1074643: presets: FTBFS:

[Lucas Nussbaum]

Hi Nilson,

On 11/07/24 at 20:48 +, Nilson Silva wrote:
> Hi Lucas!
> 
> First of all, I would like to thank you for always informing me about the 
> status of my packages.
> 
> I have always tried to respond to your requests as soon as I see your bugs.
> 
> 
> However, I would like to ask you:
> 
> Where do you follow and know that the package has construction problems?
> 
> I always see the status of each package on my page.
> https://qa.debian.org/developer.php?login=nilsonfsilva%40hotmail.com=yes
> 
> However, this last Bug (presets), which you registered, does not appear with 
> FTBFS failure on my page.
> 
> Where can I see and fix bugs before they are opened?
> This can save you work.

You can't: the bugs I detect by doing archive rebuilds are usually
changes in other packages that suddenly cause your package to start
failing to build. The Debian infra doesn't perform test rebuild
"internally", so it's normal (and fine) that your package builds fine
when you uploaded, but that later, it starts to fail to build.

Lucas

Bug#1075969: marked as done (python3-fitz: error when launching pymupdf)

[Debian Bug Tracking System]

Your message dated Fri, 12 Jul 2024 19:35:24 +
with message-id 
and subject line Bug#1075969: fixed in pymupdf 1.24.2+ds1-3
has caused the Debian Bug report #1075969,
regarding python3-fitz: error when launching pymupdf
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.)


-- 
1075969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075969
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-fitz
Version: 1.24.2+ds1-2
Severity: grave
Justification: renders package unusable

/usr/bin/pymupdf
Traceback (most recent call last):
  File "/usr/bin/pymupdf", line 5, in 
from fitz.__main__ import main
ModuleNotFoundError: No module named 'fitz'

 dpkg -L python3-fitz 
/.
/usr
/usr/bin
/usr/bin/pymupdf
/usr/lib
/usr/lib/python3
/usr/lib/python3/dist-packages
/usr/lib/python3/dist-packages/PyMuPDF-1.24.2.dist-info
/usr/lib/python3/dist-packages/PyMuPDF-1.24.2.dist-info/INSTALLER
/usr/lib/python3/dist-packages/PyMuPDF-1.24.2.dist-info/METADATA
/usr/lib/python3/dist-packages/PyMuPDF-1.24.2.dist-info/README.md
/usr/lib/python3/dist-packages/PyMuPDF-1.24.2.dist-info/WHEEL
/usr/lib/python3/dist-packages/PyMuPDF-1.24.2.dist-info/entry_points.txt
/usr/lib/python3/dist-packages/fitz_old
/usr/lib/python3/dist-packages/fitz_old/__init__.py
/usr/lib/python3/dist-packages/fitz_old/__main__.py
/usr/lib/python3/dist-packages/fitz_old/_fitz_old.cpython-311-x86_64-linux-gnu.so
/usr/lib/python3/dist-packages/fitz_old/_fitz_old.cpython-312-x86_64-linux-gnu.so
/usr/lib/python3/dist-packages/fitz_old/fitz_old.py
/usr/lib/python3/dist-packages/fitz_old/table.py
/usr/lib/python3/dist-packages/fitz_old/utils.py



-- System Information:
Debian Release: trixie/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.6.37 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python3-fitz depends on:
ii  libc62.39-3.1
ii  libfreetype6 2.13.2+dfsg-1+b4
ii  libgumbo20.12.0+dfsg-2+b1
ii  libharfbuzz0b8.3.0-2+b1
ii  libjbig2dec0 0.20-1+b2
ii  libjpeg62-turbo  1:2.1.5-3
ii  libmujs3 1.3.3-3+b2
ii  libopenjp2-7 2.5.0-2+b3
ii  python3  3.12.2-1

python3-fitz recommends no packages.

python3-fitz suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: pymupdf
Source-Version: 1.24.2+ds1-3
Done: Bastian Germann 

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

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated pymupdf 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, 12 Jul 2024 21:19:20 +0200
Source: pymupdf
Architecture: source
Version: 1.24.2+ds1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Bastian Germann 
Closes: 1075969
Changes:
 pymupdf (1.24.2+ds1-3) unstable; urgency=medium
 .
   * Team upload
   * Make pymupdf run with fitz_old (Closes: #1075969)
Checksums-Sha1:
 93c35d917a10480a97d0ca80e94f66ad839c169c 2069 pymupdf_1.24.2+ds1-3.dsc
 0e1af3c4e13cdeed72b398c8451e0c614e6ebdb1 16360 
pymupdf_1.24.2+ds1-3.debian.tar.xz
 67a9e99067d788bbcd9219104a442dd84118bfbc 9099 
pymupdf_1.24.2+ds1-3_source.buildinfo
Checksums-Sha256:
 4e35036afe73cdd421d2f12033dcc7812bf7e121020d811d8af054cc7281d3d9 2069 
pymupdf_1.24.2+ds1-3.dsc
 c2c4bf1a28ec54070b46da9121ed45be3a52de107b508abf5c16235ede2e0eb3 16360 
pymupdf_1.24.2+ds1-3.debian.tar.xz
 916182a51ecfe0222b251d811400a05d562032b537a79d102c769b01ad7bbcdb 9099 
pymupdf_1.24.2+ds1-3_source.buildinfo
Files:
 d4528728798103a831ba693b16d49b72 2069 python optional pymupdf_1.24.2+ds1-3.dsc
 9e20f51d3adae8d8962f356fba2d19a6 16360 python optional 

Bug#1074644: marked as done (rst2pdf: FTBFS: E ModuleNotFoundError: No module named 'fitz')

[Debian Bug Tracking System]

Your message dated Fri, 12 Jul 2024 19:22:07 +
with message-id 
and subject line Bug#1074644: fixed in rst2pdf 0.102-1
has caused the Debian Bug report #1074644,
regarding rst2pdf: FTBFS: E   ModuleNotFoundError: No module named 'fitz'
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.)


-- 
1074644: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074644
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rst2pdf
Version: 0.101-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240702 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild plugin_pyproject:129: Building wheel for python3.11 with "build" 
> module
> I: pybuild base:311: python3.11 -m build --skip-dependency-check 
> --no-isolation --wheel --outdir 
> /<>/.pybuild/cpython3_3.11_rst2pdf  
> * Building wheel...
> WARNING setuptools_scm.pyproject_reading toml section missing 'pyproject.toml 
> does not contain a tool.setuptools_scm section'
> Traceback (most recent call last):
>   File 
> "/usr/lib/python3/dist-packages/setuptools_scm/_integration/pyproject_reading.py",
>  line 36, in read_pyproject
> section = defn.get("tool", {})[tool_name]
>   ^^^
> KeyError: 'setuptools_scm'
> running bdist_wheel
> running build
> running build_py
> creating build
> creating build/lib
> creating build/lib/rst2pdf
> copying ./rst2pdf/sphinxnodes.py -> build/lib/rst2pdf
> copying ./rst2pdf/dumpstyle.py -> build/lib/rst2pdf
> copying ./rst2pdf/rson.py -> build/lib/rst2pdf
> copying ./rst2pdf/styles.py -> build/lib/rst2pdf
> copying ./rst2pdf/image.py -> build/lib/rst2pdf
> copying ./rst2pdf/languages.py -> build/lib/rst2pdf
> copying ./rst2pdf/createpdf.py -> build/lib/rst2pdf
> copying ./rst2pdf/genpdftext.py -> build/lib/rst2pdf
> copying ./rst2pdf/svgimage.py -> build/lib/rst2pdf
> copying ./rst2pdf/utils.py -> build/lib/rst2pdf
> copying ./rst2pdf/writer.py -> build/lib/rst2pdf
> copying ./rst2pdf/nodehandlers.py -> build/lib/rst2pdf
> copying ./rst2pdf/config.py -> build/lib/rst2pdf
> copying ./rst2pdf/findfonts.py -> build/lib/rst2pdf
> copying ./rst2pdf/sinker.py -> build/lib/rst2pdf
> copying ./rst2pdf/math_flowable.py -> build/lib/rst2pdf
> copying ./rst2pdf/basenodehandler.py -> build/lib/rst2pdf
> copying ./rst2pdf/style2yaml.py -> build/lib/rst2pdf
> copying ./rst2pdf/pygments2style.py -> build/lib/rst2pdf
> copying ./rst2pdf/log.py -> build/lib/rst2pdf
> copying ./rst2pdf/genelements.py -> build/lib/rst2pdf
> copying ./rst2pdf/sectnumlinks.py -> build/lib/rst2pdf
> copying ./rst2pdf/__init__.py -> build/lib/rst2pdf
> copying ./rst2pdf/flowables.py -> build/lib/rst2pdf
> copying ./rst2pdf/pdfbuilder.py -> build/lib/rst2pdf
> creating build/lib/rst2pdf/extensions
> copying ./rst2pdf/extensions/sample.py -> build/lib/rst2pdf/extensions
> copying ./rst2pdf/extensions/dotted_toc.py -> build/lib/rst2pdf/extensions
> copying ./rst2pdf/extensions/plantuml_r2p.py -> build/lib/rst2pdf/extensions
> copying ./rst2pdf/extensions/fancytitles.py -> build/lib/rst2pdf/extensions
> copying ./rst2pdf/extensions/preprocess_r2p.py -> build/lib/rst2pdf/extensions
> copying ./rst2pdf/extensions/__init__.py -> build/lib/rst2pdf/extensions
> creating build/lib/rst2pdf/roles
> copying ./rst2pdf/roles/counter_off.py -> build/lib/rst2pdf/roles
> copying ./rst2pdf/roles/counter.py -> build/lib/rst2pdf/roles
> copying ./rst2pdf/roles/package.py -> build/lib/rst2pdf/roles
> copying ./rst2pdf/roles/__init__.py -> build/lib/rst2pdf/roles
> creating build/lib/rst2pdf/directives
> copying ./rst2pdf/directives/contents.py -> build/lib/rst2pdf/directives
> copying ./rst2pdf/directives/oddeven.py -> build/lib/rst2pdf/directives
> copying ./rst2pdf/directives/noop.py -> build/lib/rst2pdf/directives
> copying ./rst2pdf/directives/code_block.py -> build/lib/rst2pdf/directives
> copying ./rst2pdf/directives/aafigure.py -> build/lib/rst2pdf/directives
> copying ./rst2pdf/directives/__init__.py -> build/lib/rst2pdf/directives
> creating build/lib/rst2pdf/styles
> copying ./rst2pdf/styles/a1.yaml -> build/lib/rst2pdf/styles
> copying ./rst2pdf/styles/murphy.yaml -> build/lib/rst2pdf/styles
> copying ./rst2pdf/styles/rrt.yaml -> 

Processed: Bug#1075969 marked as pending in pymupdf

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1075969 [python3-fitz] python3-fitz: error when launching pymupdf
Added tag(s) pending.

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

Bug#1075969: marked as pending in pymupdf

[Bastian Germann]

Control: tag -1 pending

Hello,

Bug #1075969 in pymupdf 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/pymupdf/-/commit/fe72ded9e44eae3f62f06535c4a7dfb06a80048a


Make pymupdf run with fitz_old (Closes: #1075969)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1075969

Bug#1076229: libqt5webview5: Cannot be installed due to missing dependency

[Robert Griebl]

Package: libqt5webview5
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: rob...@griebl.org

Dear Maintainer,

This package is used in KDE's "discover" Package Installer, which is
not installable anymore now.


$ agi libqt5webview5
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

Unsatisfied dependencies:
 libqt5webview5 : Depends: qtwebengine-abi-5-15-16 but it is not installable
Error: Unable to correct problems, you have held broken packages


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.9.7-amd64 (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libqt5webview5 depends on:
ii  libc6   2.38-14
pn  libqt5core5a
ii  libqt5core5t64 [qtbase-abi-5-15-13] 5.15.13+dfsg-2
ii  libqt5gui5t64 [libqt5gui5]  5.15.13+dfsg-2
ii  libqt5qml5 [qtdeclarative-abi-5-15-13]  5.15.13+dfsg-2
ii  libqt5quick55.15.13+dfsg-2
ii  libqt5webengine55.15.17+dfsg-3
ii  libstdc++6  14.1.0-4
pn  qtbase-abi-5-15-8   
pn  qtdeclarative-abi-5-15-8
pn  qtwebengine-abi-5-15-13 
pn  qtwebengine-abi-5-15-16 

libqt5webview5 recommends no packages.

libqt5webview5 suggests no packages.

Bug#1074797: Build fixed in 1.9.3

[Malte Schröder]

Current upstream version 1.9.3 now builds on Trixie i386.


Regards

Malte

Processed: affects

[Debian Bug Tracking System]

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

> affects 1075969 - rst2pdf
Bug #1075969 [python3-fitz] python3-fitz: error when launching pymupdf
Removed indication that 1075969 affects rst2pdf
>
End of message, stopping processing here.

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

Processed: Bug#1074644 marked as pending in pdfposter

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1074644 [src:rst2pdf] rst2pdf: FTBFS: E   ModuleNotFoundError: No module 
named 'fitz'
Added tag(s) pending.

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

Bug#1074644: marked as pending in pdfposter

[Bastian Germann]

Control: tag -1 pending

Hello,

Bug #1074644 in pdfposter 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/rst2pdf/-/commit/ce70d4060707c9e6bdfb2e9ef0ceee63767bbf6d


Deal with PyMuPDF installed as fitz_old (Closes: #1074644)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1074644

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

[Debian Bug Tracking System]

Your message dated Fri, 12 Jul 2024 18:24:55 +
with message-id 
and subject line Bug#1073418: fixed in sasdata 0.8.1-4
has caused the Debian Bug report #1073418,
regarding sasdata: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i 
python{version} -p "3.12 3.11" 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.)


-- 
1073418: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073418
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sasdata
Version: 0.8.1-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240615 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:311: python3.12 setup.py config 
> __version__ = "0.8.1"
> 
> running config
> I: pybuild base:311: python3.11 setup.py config 
> __version__ = "0.8.1"
> 
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:311: /usr/bin/python3.12 setup.py build 
> __version__ = "0.8.1"
> 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.12_sasdata/build/sasdata
> copying sasdata/__init__.py -> 
> /<>/.pybuild/cpython3_3.12_sasdata/build/sasdata
> creating 
> /<>/.pybuild/cpython3_3.12_sasdata/build/sasdata/dataloader
> copying sasdata/dataloader/__init__.py -> 
> /<>/.pybuild/cpython3_3.12_sasdata/build/sasdata/dataloader
> copying sasdata/dataloader/data_info.py -> 
> /<>/.pybuild/cpython3_3.12_sasdata/build/sasdata/dataloader
> copying sasdata/dataloader/filereader.py -> 
> /<>/.pybuild/cpython3_3.12_sasdata/build/sasdata/dataloader
> copying sasdata/dataloader/loader.py -> 
> /<>/.pybuild/cpython3_3.12_sasdata/build/sasdata/dataloader
> creating 
> /<>/.pybuild/cpython3_3.12_sasdata/build/sasdata/dataloader/readers
> copying sasdata/dataloader/readers/danse_reader.py -> 
> /<>/.pybuild/cpython3_3.12_sasdata/build/sasdata/dataloader/readers
> copying sasdata/dataloader/readers/__init__.py -> 
> /<>/.pybuild/cpython3_3.12_sasdata/build/sasdata/dataloader/readers
> copying sasdata/dataloader/readers/csv_reader.py -> 
> /<>/.pybuild/cpython3_3.12_sasdata/build/sasdata/dataloader/readers
> copying sasdata/dataloader/readers/tiff_reader.py -> 
> /<>/.pybuild/cpython3_3.12_sasdata/build/sasdata/dataloader/readers
> copying sasdata/dataloader/readers/cansas_constants.py -> 
> /<>/.pybuild/cpython3_3.12_sasdata/build/sasdata/dataloader/readers
> copying sasdata/dataloader/readers/sesans_reader.py -> 
> /<>/.pybuild/cpython3_3.12_sasdata/build/sasdata/dataloader/readers
> copying sasdata/dataloader/readers/abs_reader.py -> 
> /<>/.pybuild/cpython3_3.12_sasdata/build/sasdata/dataloader/readers
> copying sasdata/dataloader/readers/xml_reader.py -> 
> /<>/.pybuild/cpython3_3.12_sasdata/build/sasdata/dataloader/readers
> copying sasdata/dataloader/readers/anton_paar_saxs_reader.py -> 
> /<>/.pybuild/cpython3_3.12_sasdata/build/sasdata/dataloader/readers
> copying sasdata/dataloader/readers/cansas_reader_HDF5.py -> 
> /<>/.pybuild/cpython3_3.12_sasdata/build/sasdata/dataloader/readers
> copying sasdata/dataloader/readers/ascii_reader.py -> 
> /<>/.pybuild/cpython3_3.12_sasdata/build/sasdata/dataloader/readers
> copying sasdata/dataloader/readers/associations.py -> 
> /<>/.pybuild/cpython3_3.12_sasdata/build/sasdata/dataloader/readers
> copying sasdata/dataloader/readers/cansas_reader.py -> 
> /<>/.pybuild/cpython3_3.12_sasdata/build/sasdata/dataloader/readers
> copying sasdata/dataloader/readers/red2d_reader.py -> 
> /<>/.pybuild/cpython3_3.12_sasdata/build/sasdata/dataloader/readers
> creating 
> /<>/.pybuild/cpython3_3.12_sasdata/build/sasdata/file_converter
> copying sasdata/file_converter/__init__.py -> 
> /<>/.pybuild/cpython3_3.12_sasdata/build/sasdata/file_converter
> copying sasdata/file_converter/otoko_loader.py -> 
> /<>/.pybuild/cpython3_3.12_sasdata/build/sasdata/file_converter
> copying sasdata/file_converter/ascii2d_loader.py -> 
> /<>/.pybuild/cpython3_3.12_sasdata/build/sasdata/file_converter
> copying sasdata/file_converter/FileConverterUtilities.py -> 
> /<>/.pybuild/cpython3_3.12_sasdata/build/sasdata/file_converter
> copying sasdata/file_converter/red2d_writer.py -> 
> /<>/.pybuild/cpython3_3.12_sasdata/build/sasdata/file_converter
> copying sasdata/file_converter/nxcansas_writer.py -> 
> 

Bug#918316: marked as done (nocache: FTBFS in sid)

[Debian Bug Tracking System]

Your message dated Fri, 12 Jul 2024 18:19:56 +
with message-id 
and subject line Bug#918316: fixed in nocache 1.2-0.1
has caused the Debian Bug report #918316,
regarding nocache: FTBFS in sid
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.)


-- 
918316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918316
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:nocache
Version: 1.1-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in sid but it failed:


[...]
 debian/rules build-arch
dh build-arch
   dh_update_autotools_config -a
   dh_autoreconf -a
   dh_auto_configure -a
   dh_auto_build -a
make -j1 "INSTALL=install --strip-program=true"
make[1]: Entering directory '/<>'
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -Wdate-time -D_FORTIFY_SOURCE=2 
-Wl,-z,relro -Wl,-z,now -o cachedel cachedel.c
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -Wdate-time -D_FORTIFY_SOURCE=2 
-Wl,-z,relro -Wl,-z,now -o cachestats cachestats.c
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -Wdate-time -D_FORTIFY_SOURCE=2 
-Wl,-z,relro -Wl,-z,now -fPIC -c -o nocache.o nocache.c
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -Wdate-time -D_FORTIFY_SOURCE=2 
-Wl,-z,relro -Wl,-z,now -fPIC -c -o fcntl_helpers.o fcntl_helpers.c
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -Wdate-time -D_FORTIFY_SOURCE=2 
-Wl,-z,relro -Wl,-z,now -fPIC -c -o pageinfo.o pageinfo.c
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wall -Wdate-time -D_FORTIFY_SOURCE=2 
-Wl,-z,relro -Wl,-z,now -pthread -shared -Wl,-soname,nocache.so -o nocache.so 
nocache.o fcntl_helpers.o pageinfo.o -ldl
sed 's!##libdir##!$(dirname "$0")!' nocache
chmod a+x nocache
make[1]: Leaving directory '/<>'
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
## #916415
timeout 11 ./nocache apt show coreutils 1>>/dev/null

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

make[1]: *** [debian/rules:21: override_dh_auto_test] Error 124
make[1]: Leaving directory '/<>'
make: *** [debian/rules:10: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


To be sure, I have tried to build the package 151 times on 8 different machines
and it failed 151 times. Here are the full build logs:

https://people.debian.org/~sanvila/build-logs/nocache/

A very similar failure happened here in mipsel, a release architecture:

https://buildd.debian.org/status/fetch.php?pkg=nocache=mipsel=1.1-1=1546582253=0

If you need help to reproduce this, please say so, I would gladly offer access 
to a system
where this seems to happen all the time.

Thanks.
--- End Message ---
--- Begin Message ---
Source: nocache
Source-Version: 1.2-0.1
Done: Christoph Biedl 

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

Debian distribution maintenance software
pp.
Christoph Biedl  (supplier of updated nocache 
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: Sun, 07 Jul 2024 13:44:09 +0200
Source: nocache
Architecture: source
Version: 1.2-0.1
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Smirnov 
Changed-By: Christoph Biedl 
Closes: 918316 1069426
Changes:
 nocache (1.2-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload
   * Import upstream version 1.2, this fixes issues with increased file
 limits. Closes: 918316
   * Fix build on (most) 32 bit architectures. Closes: #1069426
 Kudos to Guillem Jover for taking care of that.
   * Simplify test so it will not time out. Closes: 

Bug#1069426: marked as done (nocache: FTBFS on armhf: ccsSPzHW.s:3650: Error: symbol `fopen64' is already defined)

[Debian Bug Tracking System]

Your message dated Fri, 12 Jul 2024 18:19:56 +
with message-id 
and subject line Bug#1069426: fixed in nocache 1.2-0.1
has caused the Debian Bug report #1069426,
regarding nocache: FTBFS on armhf: ccsSPzHW.s:3650: Error: symbol `fopen64' is 
already defined
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.)


-- 
1069426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069426
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nocache
Version: 1.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf

Hi,

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


Relevant part (hopefully):
> cc -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -Wall 
> -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -fPIC -c -o pageinfo.o pageinfo.c
> sed 's!##libdir##!$(dirname "$0")!' nocache
> chmod a+x nocache
> /tmp/ccsSPzHW.s: Assembler messages:
> /tmp/ccsSPzHW.s:3650: Error: symbol `fopen64' is already defined
> make[1]: *** [Makefile:27: nocache.o] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/nocache_1.1-1_unstable-armhf.log

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

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

Debian distribution maintenance software
pp.
Christoph Biedl  (supplier of updated nocache 
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: Sun, 07 Jul 2024 13:44:09 +0200
Source: nocache
Architecture: source
Version: 1.2-0.1
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Smirnov 
Changed-By: Christoph Biedl 
Closes: 918316 1069426
Changes:
 nocache (1.2-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload
   * Import upstream version 1.2, this fixes issues with increased file
 limits. Closes: 918316
   * Fix build on (most) 32 bit architectures. Closes: #1069426
 Kudos to Guillem Jover for taking care of that.
   * Simplify test so it will not time out. Closes: #918316 (again)
Checksums-Sha1:
 c641548bc92f297c21ac5e0e89a175066654d436 1795 nocache_1.2-0.1.dsc
 231950fac6981c8f9313810f9172fdb927397e4b 11768 nocache_1.2.orig.tar.xz
 836b39500a1a6985326515c743fd8531f77cee64 7104 nocache_1.2-0.1.debian.tar.xz
 11fcf50d22979b11775a5e776e3d7ca6b33e2336 5815 nocache_1.2-0.1_armel.buildinfo
Checksums-Sha256:
 0acf53071e85a2e8c6b0519eec68cfb3baad883dfd05189a327c5be380635067 1795 
nocache_1.2-0.1.dsc
 1d190b21fdca0dc160b4249e6825275354dcb7a95a02aa845344e1fa83c8deba 11768 
nocache_1.2.orig.tar.xz
 0fe56b200982d2644fb4ea6a878f7d279962602aefea19a9da2b0fbbc1815c56 7104 
nocache_1.2-0.1.debian.tar.xz
 194f3f7499632d6fa60a00e715dde7d3a417ead798f32bc8f00df74782267e5d 5815 
nocache_1.2-0.1_armel.buildinfo
Files:
 f08358bc194fc9079c0595fb32bfdb31 1795 utils optional nocache_1.2-0.1.dsc
 f2ccf0c72dcd8d897a9b8c1d24b979a2 11768 utils optional nocache_1.2.orig.tar.xz
 47e1e1981303579ef9452096f19d5a29 7104 utils optional 
nocache_1.2-0.1.debian.tar.xz
 b265efbc19b66754580fb4ca018c990b 5815 utils optional 

Bug#1076166: mdtraj: fails to build

[Drew Parsons]

Source: mdtraj
Followup-For: Bug #1076166

Thanks, but that patch is no good.  It deletes libtheobald.a and
core/lib completely, which is not what we want.

The error arises since it's not building for python 3.11 anymore.

Bug#1064726: reopen, still ftbfs

[Antoine Le Gonidec]

Since the new reported problem with building 0 A.D. from source is
distinct from the one reported in the first place, please consider
closing the current bug report and open a new one instead.

Keeping this one open is preventing the 0 A.D. packages from migrating
to testing.

Unless someone can see a good reason to keep the current bug report
open, I will close it in a couple days, and forward the report by
Matthias into a new dedicated bug report.


pgpA8FzliUh6r.pgp
Description: Signature digitale OpenPGP

Bug#1074706: [Pkg-pascal-devel] Bug#1074706: Bug#1074706: msgfmt change breaks build

[Peter Blackman]

On 12/07/2024 11:17, Peter Blackman wrote:

Raised bug report upstream,
https://gitlab.com/freepascal.org/fpc/source/-/issues/40853

and updated the patch header.



Oh poo!!

Seems the mail system ate my patch with

A non-text attachment was scrubbed...
Name: msgfmt.patch
Type: text/x-patch

here it is inline;


Subject: Fix msgfmt related build fail
Author: Peter Blackman 
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074706
Forwarded: https://gitlab.com/freepascal.org/fpc/source/-/issues/40853
===
--- a/fpcsrc/utils/fpdoc/intl/dglobals.de.po
+++ b/fpcsrc/utils/fpdoc/intl/dglobals.de.po
@@ -1,3 +1,7 @@
+msgid ""
+msgstr ""
+"Content-Type: text/plain; charset=UTF-8\n"
+
 #: dglobals:sdocpackagetitle
 msgid "Reference for package '%s'"
 msgstr "Referenz für Paket '%s'"
Index: b/fpcsrc/utils/fpdoc/intl/dwriter.de.po
===
--- a/fpcsrc/utils/fpdoc/intl/dwriter.de.po
+++ b/fpcsrc/utils/fpdoc/intl/dwriter.de.po
@@ -1,3 +1,7 @@
+msgid ""
+msgstr ""
+"Content-Type: text/plain; charset=UTF-8\n"
+
 #: dwriter:serrfilewriting
 msgid "An error occurred during writing of file \"%s\": %s"
 msgstr "Beim Schreiben der Datei \"%s\" ist ein Fehler aufgetrete: %s"
Index: b/fpcsrc/utils/fpdoc/intl/fpdoc.de.po
===
--- a/fpcsrc/utils/fpdoc/intl/fpdoc.de.po
+++ b/fpcsrc/utils/fpdoc/intl/fpdoc.de.po
@@ -1,3 +1,7 @@
+msgid ""
+msgstr ""
+"Content-Type: text/plain; charset=UTF-8\n"
+
 #: fpdoc:stitle
 msgid "FPDoc - Free Pascal Documentation Tool"
 msgstr "FPDoc - Free-Pascal-Dokumentationstool"
Index: b/fpcsrc/utils/fpdoc/intl/makeskel.de.po
===
--- a/fpcsrc/utils/fpdoc/intl/makeskel.de.po
+++ b/fpcsrc/utils/fpdoc/intl/makeskel.de.po
@@ -1,3 +1,7 @@
+msgid ""
+msgstr ""
+"Content-Type: text/plain; charset=UTF-8\n"
+
 #: makeskel:stitle
 msgid "MakeSkel - FPDoc skeleton XML description file generator"
 msgstr "MakeSkel - Skelett-Generator für FPDoc-XML-Beschreibungsdateien"

Processed: Re: FTBFS with Linux 6.8+

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 busybox: FTBFS with Linux 6.8+
Bug #1071648 [src:busybox] FTBFS with Linux 6.8+
Changed Bug title to 'busybox: FTBFS with Linux 6.8+' from 'FTBFS with Linux 
6.8+'.

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

Bug#1071648: FTBFS with Linux 6.8+

[Blair Noctis]

Control: retitle -1 busybox: FTBFS with Linux 6.8+

(Sorry but this makes the subject clear)

On Wed, 22 May 2024 23:04:10 + Tianon Gravi  wrote:
> Source: busybox
> Version: 1:1.36.1-7
> Severity: serious
> Tags: ftbfs upstream
> X-Debbugs-Cc: tia...@debian.org
> 
> The recent upload of src:linux to 6.8+ (specifically 6.8.9-1,
> ironicially uploaded around the same time as the last busybox upload)
> causes src:busybox to FTBFS (logs from reproducible-builds):

(...)

> This has been reported upstream[1][2] (back in January), but with no
> upstream resolution yet.
> 
> [1]: https://bugs.busybox.net/show_bug.cgi?id=15931
> [2]: https://bugs.busybox.net/show_bug.cgi?id=15934

[1] now has two patches submitted, one that removes CBQ functionality entirely,
the other too but `instead of removing the CBQ option in print_qdisc, I just
made it printf("cbq not supported")`.

FYI, also https://bugs.gentoo.org/926872

-- 
Sdrager,
Blair Noctis


pgpHoqZNnsZIC.pgp
Description: OpenPGP digital signature

Processed: reopening (again) kpatch bugs that were closed (and archived) with the RM

[Debian Bug Tracking System]

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

> package kpatch-dkms
Limiting to bugs with field 'package' containing at least one of 'kpatch-dkms'
Limit currently set to 'package':'kpatch-dkms'

> reopen 983648
Bug #983648 {Done: Debian FTP Masters } 
[kpatch-dkms] kpatch-dkms: fails to build module for Linux 5.10: uses unknown 
struct stack_trace
'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 0.6.0-0.2+rm.
> reopen 991003
Bug #991003 {Done: Debian FTP Masters } 
[kpatch-dkms] kpatch-dkms: fails to build module for Linux 4.19.0-17 or newer: 
find_symbol is no longer exported by the kernel
'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 0.6.0-0.2+rm.
> package src:kpatch
Limiting to bugs with field 'package' containing at least one of 'src:kpatch'
Limit currently set to 'package':'src:kpatch'

> reopen 1027889
Bug #1027889 {Done: Debian FTP Masters } 
[src:kpatch] kpatch FTBFS: please switch to B-D: dh-sequence-dkms (or dh-dkms)
'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 0.6.0-0.2+rm.
> reopen 1029189
Bug #1029189 {Done: Debian FTP Masters } 
[src:kpatch] kpatch: FTBFS with shellcheck 0.9.0
'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 0.6.0-0.2+rm.
> thanks
Stopping processing here.

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

Bug#1076206: pybj: fails to build extension but build still succeeds

[Graham Inggs]

Source: pybj
Version: 0.2.6-2
Severity: serious
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.12

Hi Maintainer

pybj fails to build its extension, but the build still succeeds.
Noticed in the recent rebuild for Python 3.12 only [1].  I've copied
what I hope is the relevant part of the log below.

Regards
Graham


[1] 
https://buildd.debian.org/status/fetch.php?pkg=pybj=amd64=0.2.6-2%2Bb1=1720780666=0


running build
running build_py
running build_ext
building '_bjdata' extension
x86_64-linux-gnu-gcc -fno-strict-overflow -Wsign-compare -DNDEBUG -g
-O2 -Wall -g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security
-fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
-I/usr/include/python3.12 -c src/_bjdata.c -o
build/temp.linux-x86_64-cpython-312/src/_bjdata.o -std=c99
-DUSE__BJDATA
x86_64-linux-gnu-gcc -fno-strict-overflow -Wsign-compare -DNDEBUG -g
-O2 -Wall -g -O2 -Werror=implicit-function-declaration
-ffile-prefix-map=/<>=. -fstack-protector-strong
-fstack-clash-protection -Wformat -Werror=format-security
-fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
-I/usr/include/python3.12 -c src/decoder.c -o
build/temp.linux-x86_64-cpython-312/src/decoder.o -std=c99
-DUSE__BJDATA
src/decoder.c:20:10: fatal error: numpy/arrayobject.h: No such file or directory
   20 | #include 
  |  ^
compilation terminated.
/<>/setup.py:64: UserWarning: Extension module _bjdata:
The output above this warning shows how the compilation failed.
  warnings.warn("Extension module %s: The output above this warning
shows how the compilation failed."
command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1
running install_lib

Bug#1066738: marked as done (python-asyncio-mqtt: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13)

[Debian Bug Tracking System]

Your message dated Fri, 12 Jul 2024 14:06:45 +
with message-id 
and subject line Bug#1066738: fixed in python-asyncio-mqtt 2.2.0-1
has caused the Debian Bug report #1066738,
regarding python-asyncio-mqtt: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p 3.11 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.)


-- 
1066738: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066738
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-asyncio-mqtt
Version: 0.16.1-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240313 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> echo "__version__ = version = '0.16.1'" > asyncio_mqtt/_version.py
> echo "__version_tuple__ = version_tuple = tuple('0.16.1'.split('.'))" >> 
> asyncio_mqtt/_version.py
> make[1]: Leaving directory '/<>'
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild plugin_pyproject:129: Building wheel for python3.11 with "build" 
> module
> I: pybuild base:305: python3.11 -m build --skip-dependency-check 
> --no-isolation --wheel --outdir 
> /<>/.pybuild/cpython3_3.11_asyncio_mqtt  
> * Building wheel...
> running bdist_wheel
> running build
> running build_py
> creating build
> creating build/lib
> creating build/lib/asyncio_mqtt
> copying asyncio_mqtt/__init__.py -> build/lib/asyncio_mqtt
> copying asyncio_mqtt/error.py -> build/lib/asyncio_mqtt
> copying asyncio_mqtt/_version.py -> build/lib/asyncio_mqtt
> copying asyncio_mqtt/client.py -> build/lib/asyncio_mqtt
> copying asyncio_mqtt/types.py -> build/lib/asyncio_mqtt
> running egg_info
> creating asyncio_mqtt.egg-info
> writing asyncio_mqtt.egg-info/PKG-INFO
> writing dependency_links to asyncio_mqtt.egg-info/dependency_links.txt
> writing requirements to asyncio_mqtt.egg-info/requires.txt
> writing top-level names to asyncio_mqtt.egg-info/top_level.txt
> writing manifest file 'asyncio_mqtt.egg-info/SOURCES.txt'
> reading manifest file 'asyncio_mqtt.egg-info/SOURCES.txt'
> adding license file 'LICENSE'
> writing manifest file 'asyncio_mqtt.egg-info/SOURCES.txt'
> installing to build/bdist.linux-x86_64/wheel
> running install
> running install_lib
> creating build/bdist.linux-x86_64
> creating build/bdist.linux-x86_64/wheel
> creating build/bdist.linux-x86_64/wheel/asyncio_mqtt
> copying build/lib/asyncio_mqtt/__init__.py -> 
> build/bdist.linux-x86_64/wheel/asyncio_mqtt
> copying build/lib/asyncio_mqtt/error.py -> 
> build/bdist.linux-x86_64/wheel/asyncio_mqtt
> copying build/lib/asyncio_mqtt/_version.py -> 
> build/bdist.linux-x86_64/wheel/asyncio_mqtt
> copying build/lib/asyncio_mqtt/client.py -> 
> build/bdist.linux-x86_64/wheel/asyncio_mqtt
> copying build/lib/asyncio_mqtt/types.py -> 
> build/bdist.linux-x86_64/wheel/asyncio_mqtt
> running install_egg_info
> Copying asyncio_mqtt.egg-info to 
> build/bdist.linux-x86_64/wheel/asyncio_mqtt-0.0.0.egg-info
> running install_scripts
> creating build/bdist.linux-x86_64/wheel/asyncio_mqtt-0.0.0.dist-info/WHEEL
> creating 
> '/<>/.pybuild/cpython3_3.11_asyncio_mqtt/.tmp-nh8imiqf/asyncio_mqtt-0.0.0-py3-none-any.whl'
>  and adding 'build/bdist.linux-x86_64/wheel' to it
> adding 'asyncio_mqtt/__init__.py'
> adding 'asyncio_mqtt/_version.py'
> adding 'asyncio_mqtt/client.py'
> adding 'asyncio_mqtt/error.py'
> adding 'asyncio_mqtt/types.py'
> adding 'asyncio_mqtt-0.0.0.dist-info/LICENSE'
> adding 'asyncio_mqtt-0.0.0.dist-info/METADATA'
> adding 'asyncio_mqtt-0.0.0.dist-info/WHEEL'
> adding 'asyncio_mqtt-0.0.0.dist-info/top_level.txt'
> adding 'asyncio_mqtt-0.0.0.dist-info/RECORD'
> removing build/bdist.linux-x86_64/wheel
> Successfully built asyncio_mqtt-0.0.0-py3-none-any.whl
> I: pybuild plugin_pyproject:144: Unpacking wheel built for python3.11 with 
> "installer" module
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:305: cd 
> /<>/.pybuild/cpython3_3.11_asyncio_mqtt/build; python3.11 -m 
> pytest tests
> = test session starts 
> ==
> platform linux -- Python 3.11.8, pytest-8.0.2, pluggy-1.4.0
> rootdir: /<>/.pybuild/cpython3_3.11_asyncio_mqtt/build
> configfile: pyproject.toml
> plugins: anyio-4.2.0
> collected 50 items
> 
> tests/test_client.py ...FFFs [ 
> 38%]
> tests/test_error.py ..FFF...FFF  
> [100%]
> 
> === 

Processed: closing 1071552

[Debian Bug Tracking System]

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

> # Fixup bug status in the BTS
> close 1071552
Bug #1071552 [gnupg] GnuPG 2.2.42+ breaks emacs' EasyPG
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1074500: marked as done (pompem: autopkgtest failure with Python 3.12)

[Debian Bug Tracking System]

Your message dated Fri, 12 Jul 2024 13:57:11 +
with message-id 
and subject line Bug#1074500: fixed in pompem 0.2.0-7
has caused the Debian Bug report #1074500,
regarding pompem: autopkgtest failure with Python 3.12
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.)


-- 
1074500: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074500
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pompem
Version: 0.2.0-6
Severity: serious
Tags: sid trixie
X-Debbugs-Cc: y...@debian.org
User: debian-pyt...@lists.debian.org
Usertags: python3.12

Dear Maintainer,

pompem autopkgtests fail with Python 3.12  [0].

autopkgtest [23:24:27]: test command1: [---
/usr/share/pompem/common/print_messages.py:14: SyntaxWarning: invalid escape 
sequence '\_'
  BASIC_INFO_MESSAGE = """

Options:
  -h, --help  show this help message and exit
  -s, --search   text for search
  --txt   Write txt File
  --html  Write html File
  --updateupgrade to latest version
  -g, --get   Download exploit files
  
autopkgtest [23:24:28]: test command1: ---]
autopkgtest [23:24:28]: test command1:  - - - - - - - - - - results - - - - - - 
- - - -
command1 FAIL stderr: 
/usr/share/pompem/common/print_messages.py:14: SyntaxWarning: invalid escape 
sequence '\_'
autopkgtest [23:24:28]: test command1:  - - - - - - - - - - stderr - - - - - - 
- - - -
/usr/share/pompem/common/print_messages.py:14: SyntaxWarning: invalid escape 
sequence '\_'
  BASIC_INFO_MESSAGE = """
autopkgtest [23:24:28]:  summary
command1 FAIL stderr: 
/usr/share/pompem/common/print_messages.py:14: SyntaxWarning: invalid escape 
sequence '\_'


[0] https://ci.debian.net/packages/p/pompem/testing/arm64
--- End Message ---
--- Begin Message ---
Source: pompem
Source-Version: 0.2.0-7
Done: Sven Geuer 

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

Debian distribution maintenance software
pp.
Sven Geuer  (supplier of updated pompem 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, 12 Jul 2024 15:15:34 +0200
Source: pompem
Architecture: source
Version: 0.2.0-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Sven Geuer 
Closes: 1074500
Changes:
 pompem (0.2.0-7) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Debian Janitor ]
   * Update standards version to 4.6.1, no changes needed.
 .
   [ Janitor ]
   * Apply hints suggested by the [multi-arch hinter]
 (https://wiki.debian.org/MultiArch/Hints)
 .
   [ Sven Geuer ]
   * d/p/*: Escape or replace backslashes in strings (Closes: #1074500).
   * d/t/control: Extend autopkgtest to show the pompem logo.
   * d/control: Bump Standards-Version to 4.7.0.
   * d/copyright: Update the 'Files: debian/*' stanza.
   * d/salsa-ci.yml: Add variable SALSA_CI_DISABLE_BUILD_PACKAGE_ANY.
Checksums-Sha1:
 fb119a28e593ccb83cc9108aba62209e08516684 1943 pompem_0.2.0-7.dsc
 661330cc1164a1a8c20a1cf0777e1d1b6071d4a9 4780 pompem_0.2.0-7.debian.tar.xz
 64e07434b5696beec8d281fd9872aa27abc7ca48 5411 pompem_0.2.0-7_amd64.buildinfo
Checksums-Sha256:
 1e760dae9b2604c076da508ff50c095d70f92fd5f26000914154a187befec7cd 1943 
pompem_0.2.0-7.dsc
 2627c0189f5340cfc4f6ef2ae0b0a118980b681b0fa3c934b0fa05bfcc1e25d6 4780 
pompem_0.2.0-7.debian.tar.xz
 487aa6d1ad403f594d956c8433e042cfb744bd2dfa5f62633627e3e3057bfd53 5411 
pompem_0.2.0-7_amd64.buildinfo
Files:
 d77d626ca42db3b912483ef44b024c27 1943 utils optional pompem_0.2.0-7.dsc
 65e06370a6a2ee04b06b9162537eba0e 4780 utils optional 
pompem_0.2.0-7.debian.tar.xz
 6b33f638b71dac9dcc7ea8a0c29c8782 5411 utils optional 
pompem_0.2.0-7_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCgAtFiEEPfXoqkP8n9/QhvGVrfUO2vit1YUFAmaRLLwPHHNnZUBkZWJp
YW4ub3JnAAoJEK31Dtr4rdWFdZIP/1NEvCe4lYhf9LYfhn3Fk7vsidVwfLzbrr2d
PPiSa+WVvth1WEbvLEULeu3wO3oMOOqOGvGbQ9hrbkcRldCi1NBcpvqu4j62B3Di

Processed: Re: Processed (with 4 errors): unarchiving kpatch bugs that were closed with the RM

[Debian Bug Tracking System]

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

> package kpatch-dkms
Limiting to bugs with field 'package' containing at least one of 'kpatch-dkms'
Limit currently set to 'package':'kpatch-dkms'

> unarchive 983648
Bug #983648 {Done: Debian FTP Masters } 
[kpatch-dkms] kpatch-dkms: fails to build module for Linux 5.10: uses unknown 
struct stack_trace
Unarchived Bug 983648
> unarchive 991003
Bug #991003 {Done: Debian FTP Masters } 
[kpatch-dkms] kpatch-dkms: fails to build module for Linux 4.19.0-17 or newer: 
find_symbol is no longer exported by the kernel
Unarchived Bug 991003
> thanks
Stopping processing here.

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

Bug#1076205: aspectc++: Please upgrade to llvm-toolchain-18

[Emanuele Rocca]

Source: aspectc++
Version: 1:2.3+git20230726-1
Severity: serious
Control: block 1050069 by -1

Dear Maintainer,

aspectc++ build-depends on llvm-14-dev, which is not going to be
part of Trixie. See https://bugs.debian.org/1050069

Please make sure that the package builds with LLVM 18 instead.

Thanks,
  Emanuele

Processed: aspectc++: Please upgrade to llvm-toolchain-18

[Debian Bug Tracking System]

Processing control commands:

> block 1050069 by -1
Bug #1050069 [ftp.debian.org] RM: llvm-toolchain-14 -- ROM; Too many version of 
llvm
1050069 was blocked by: 1061211 1061210 1061214 1061209 1061217 1061219 1061213 
1061216 1061215 1061218
1050069 was blocking: 1068961
Added blocking bug(s) of 1050069: 1076205

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

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> reassign 1073410 texlive-base
Bug #1073410 [src:pymol] pymol: FTBFS: grep: tcrm0900.log: No such file or 
directory
Bug reassigned from package 'src:pymol' to 'texlive-base'.
No longer marked as found in versions pymol/2.5.0+dfsg-1.
Ignoring request to alter fixed versions of bug #1073410 to the same values 
previously set
> forcemerge 1072828 1073410
Bug #1072828 {Done: Hilmar Preusse } [texlive-base] 
texlive-binaries upgrade breaks therion build
Bug #1073410 [texlive-base] pymol: FTBFS: grep: tcrm0900.log: No such file or 
directory
Marked Bug as done
Added indication that 1073410 affects src:therion
Marked as fixed in versions texlive-base/2024.20240401-3.
Marked as found in versions texlive-base/2024.20240401-2.
Added tag(s) patch.
Bug #1072828 {Done: Hilmar Preusse } [texlive-base] 
texlive-binaries upgrade breaks therion build
Added tag(s) trixie and sid.
Merged 1072828 1073410
> affects 1072828 src:pymol
Bug #1072828 {Done: Hilmar Preusse } [texlive-base] 
texlive-binaries upgrade breaks therion build
Bug #1073410 {Done: Hilmar Preusse } [texlive-base] pymol: 
FTBFS: grep: tcrm0900.log: No such file or directory
Added indication that 1072828 affects src:pymol
Added indication that 1073410 affects src:pymol
> thanks
Stopping processing here.

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

Bug#1076203: coot: Please drop dependencies on python3-distutils

[Graham Inggs]

Source: coot
Version: 1.1.09+dfsg-1
Severity: serious
Tags: ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.12

Hi Maintainer

This package has dependencies, build-dependencies and/or autopkgtest
dependencies on python3-distutils.  The python3-distutils binary
package will soon be dropped from python3-stdlib-extensions.

In fact, there is no module for Python 3.12 in python3-distutils, so
these dependencies may already be unnecessary.

Regards
Graham

Bug#1076204: python3-bjdata: C extension silently not built with recent numpy

[Adrian Bunk]

Package: python3-bjdata
Version: 0.2.6-2
Severity: serious
Tags: patch
Forwarded: 
https://github.com/fangq/pybj/commit/a46355a0b0df0bec1817b04368a5a573358645ef
X-Debbugs-Cc: Stefano Rivera 

https://buildd.debian.org/status/fetch.php?pkg=pybj=amd64=0.2.6-2%2Bb1=1720780666=0

...
x86_64-linux-gnu-gcc -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O2 -Wall 
-g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
-Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.12 -c 
src/decoder.c -o build/temp.linux-x86_64-cpython-312/src/decoder.o -std=c99 
-DUSE__BJDATA
src/decoder.c:20:10: fatal error: numpy/arrayobject.h: No such file or directory
   20 | #include 
  |  ^
compilation terminated.
...

Bug#1076202: python-memray: build-depends on python3.11-dev

[Graham Inggs]

Source: python-memray
Version: 1.13.3+dfsg-1
Severity: serious
User: debian-pyt...@lists.debian.org
Usertags: python3.12

Hi Maintainer

python-memray build-depends on python3.11-dev (and  python3.12-dev).
Python 3.11 is being removed from Trixie soon.  Please remove the
build-depends on python3.11-dev, perhaps python3-all-dev is what you
need instead.

Regards
Graham

Processed: Bug#1074500 marked as pending in pompem

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1074500 [pompem] pompem: autopkgtest failure with Python 3.12
Added tag(s) pending.

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

Bug#1074500: marked as pending in pompem

[Sven Geuer]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/pkg-security-team/pompem/-/commit/503578cc4bea4940ff64f47da52a371953b643d1


Escape or replace backslashes in strings (Closes: #1074500).

Python 3.12 throws syntax warnings regarding invalid escape sequences.
In the case of pompem the invalid escape sequences were caused by unescaped
or erroneous backslashes.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1074500

Processed (with 1 error): Re: rust-sequoia-chameleon-gnupg is marked for autoremoval from testing

[Debian Bug Tracking System]

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

> forcemerge 1074637 1074688
Bug #1074637 {Done: Holger Levsen } [src:rust-sequoia-wot] 
rust-sequoia-wot: FTBFS: build-dependency not installable: 
librust-sequoia-cert-store-0.5+default-dev
Unable to merge bugs because:
package of #1074688 is 'src:rust-sequoia-gpg-agent' not 'src:rust-sequoia-wot'
Failed to forcibly merge 1074637: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Bug#1076201: docker-compose: update to 1.29.2-6.1 makes the packages unusuable

[Ernesto Domato]

Package: docker-compose
Version: 1.29.2-6.1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: edom...@gmail.com

Hi, I just update docker-compose package and now when you try to run it it
throws:

Traceback (most recent call last):
  File "/usr/bin/docker-compose", line 33, in 
sys.exit(load_entry_point('docker-compose==1.29.2', 'console_scripts',
'docker-compose')())
^^^
  File "/usr/bin/docker-compose", line 25, in importlib_load_entry_point
return next(matches).load()
   
  File "/usr/lib/python3.12/importlib/metadata/__init__.py", line 205, in load
module = import_module(match.group('module'))
 
  File "/usr/lib/python3.12/importlib/__init__.py", line 90, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
   
  File "", line 1387, in _gcd_import
  File "", line 1360, in _find_and_load
  File "", line 1331, in _find_and_load_unlocked
  File "", line 935, in _load_unlocked
  File "", line 995, in exec_module
  File "", line 488, in _call_with_frames_removed
  File "/usr/lib/python3/dist-packages/compose/cli/main.py", line 16, in

from . import errors
  File "/usr/lib/python3/dist-packages/compose/cli/errors.py", line 13, in

from ..const import API_VERSION_TO_ENGINE_VERSION
  File "/usr/lib/python3/dist-packages/compose/const.py", line 32, in 
API_VERSIONS = {
   ^
  File "/usr/lib/python3/dist-packages/compose/version.py", line 7, in __hash__
return hash(self.vstring)

AttributeError: 'ComposeVersion' object has no attribute 'vstring'



Downgrading to previous version fixes the problem.

Thanks
Ernesto


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

Kernel: Linux 6.9.8-amd64 (SMP w/8 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

Versions of packages docker-compose depends on:
ii  python33.12.3-1
ii  python3-compose1.29.2-6.1
ii  python3-packaging  24.1-1

Versions of packages docker-compose recommends:
ii  docker.io  20.10.25+dfsg1-3

docker-compose suggests no packages.

-- no debconf information

Bug#1074362: marked as done (src:ruby-redis-client: fails to migrate to testing for too long: uploader built arch:all binary)

[Debian Bug Tracking System]

Your message dated Fri, 12 Jul 2024 11:47:54 +
with message-id 
and subject line Bug#1074362: fixed in ruby-redis-client 0.22.2-1.1
has caused the Debian Bug report #1074362,
regarding src:ruby-redis-client: fails to migrate to testing for too long: 
uploader built arch:all binary
to be marked as done.

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

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


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

Source: ruby-redis-client
Version: 0.19.1-2
Severity: serious
Control: close -1 0.22.2-1
Tags: sid trixie pending
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:ruby-redis-client has been trying to 
migrate for 31 days [2]. Hence, I am filing this bug.


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


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


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


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


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=ruby-redis-client



OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: ruby-redis-client
Source-Version: 0.22.2-1.1
Done: Paul Gevers 

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

Debian distribution maintenance software
pp.
Paul Gevers  (supplier of updated ruby-redis-client 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, 27 Jun 2024 12:15:21 +0200
Source: ruby-redis-client
Architecture: source
Version: 0.22.2-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Paul Gevers 
Closes: 1074362
Changes:
 ruby-redis-client (0.22.2-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * source only upload to enable migration (Closes: #1074362)
Checksums-Sha1:
 86ab6695f83852f7fa98f5aa0a40de22178835df 1871 ruby-redis-client_0.22.2-1.1.dsc
 ac799104d4d6405329329de06be853524262ae2a 2920 
ruby-redis-client_0.22.2-1.1.debian.tar.xz
Checksums-Sha256:
 63ffe7bcdade2fcca929d61f6596b60f2842a12591ebb95551b8ea4dd16d4c77 1871 
ruby-redis-client_0.22.2-1.1.dsc
 d1b2820ca25cacc10743e87d1381af24803c30707bd9963f67d17ca69d23eb47 2920 
ruby-redis-client_0.22.2-1.1.debian.tar.xz
Files:
 75393546568941554d5dd3af17cc813c 1871 ruby optional 
ruby-redis-client_0.22.2-1.1.dsc
 b1130dadc4c4390fe886fcf9a627cd5b 2920 ruby optional 
ruby-redis-client_0.22.2-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmZ9O/cACgkQnFyZ6wW9
dQoW8gf7BqMaEP19Q0UvH+qoJsrCNLF7knsmNrlXHJiWWACC6QEK6+QELjzOWdvH
7VzdwOkmnxtd9y96k584g/pJnO2KDeExPLKfSEOLi9CFLy2Hhx/UZmTKt/n1Gq1C
7U05R4o42WOvyUKS3CFNPh6Pnyr6Xd77ZaTjng3MdPXlIb+OSssZicQ+gYiJ0Xbl

Bug#1076124: marked as done ((build-)dependency on removed python3-distutils)

[Debian Bug Tracking System]

Your message dated Fri, 12 Jul 2024 11:36:24 +
with message-id 
and subject line Bug#1076124: fixed in python-gnocchiclient 7.0.8-2
has caused the Debian Bug report #1076124,
regarding (build-)dependency on removed python3-distutils
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.)


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

Source: python-gnocchiclient
Version: 7.0.8-1
Severity: serious
Tags: sid trixie patch
User: debian-pyt...@lists.debian.org
Usertags: python3.12

there are (build-)dependency on the now removed python3-distutils.

patch at
https://patches.ubuntu.com/p/python-gnocchiclient/python-gnocchiclient_7.0.8-0ubuntu1.patch
--- End Message ---
--- Begin Message ---
Source: python-gnocchiclient
Source-Version: 7.0.8-2
Done: Thomas Goirand 

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated python-gnocchiclient 
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, 12 Jul 2024 12:58:09 +0200
Source: python-gnocchiclient
Architecture: source
Version: 7.0.8-2
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Closes: 1076124
Changes:
 python-gnocchiclient (7.0.8-2) unstable; urgency=medium
 .
   * Removed distutils (build-)depends (Closes: #1076124).
Checksums-Sha1:
 caf5bbc0ffaae73083fe23a7a53259200b0e27d6 2668 python-gnocchiclient_7.0.8-2.dsc
 19f5ae3b4458bcefc178fa10e286c87ce1b3e471 4516 
python-gnocchiclient_7.0.8-2.debian.tar.xz
 997333101c558176d8991f50e8634bdc26642dc2 12564 
python-gnocchiclient_7.0.8-2_amd64.buildinfo
Checksums-Sha256:
 37030fbe53b6fd7fe8bfafb6b54c944cc36e347f4303d864baaa5461b75f56e5 2668 
python-gnocchiclient_7.0.8-2.dsc
 ee1977243c19efde67e806ddbe995cd86168f9380cc6801c71cb6e361570f568 4516 
python-gnocchiclient_7.0.8-2.debian.tar.xz
 14b62c13efe38e30ed3861cfa35577bfd150638930c43445cb4c41d7d02a4a3a 12564 
python-gnocchiclient_7.0.8-2_amd64.buildinfo
Files:
 7f2c2d971a051377af8b30c2b4208579 2668 python optional 
python-gnocchiclient_7.0.8-2.dsc
 9ddca41bd1caf24951d22d7beb7d4b97 4516 python optional 
python-gnocchiclient_7.0.8-2.debian.tar.xz
 b45f9537c99ce12a38d83fecebcf5ee3 12564 python optional 
python-gnocchiclient_7.0.8-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAmaRDN8ACgkQ1BatFaxr
Q/4vkQ//dr6SBi3IqLNOJzf9iaj0R3Aaw0+9ODRsJJG+7fKPCHMpGBJkuHWFBNvd
VRrCdjl3jxUVPDV+5OlIgKXY28AL5rDQdPh6zP9iT187PH5EPRWoHx122sJeku7i
1fmUDJYuB/YSAI0PdhacsR6AEq7T1i/aSW8peUwrDCq6cazG988GPEc6ur5wzrfR
dXjiprlnYTP7ZrtpI4b/0IkS7tIgYaeA05MPP4Qz7WYvOwc201FNAPl43vt7WOsG
jDoF6AyziGIz2iI6MgopjXJizjtPJistslh7QqcJlcoCblpGfsToZ30BVrgPW158
s72fjrya40rjxcumoFhFh7pSG6ux99hvhwO3gxYcEXV5/12Am9+PpH2dYhCprDCl
sTBhEhefHoCQtf8J4EOibItEeSpM7UBx8mFOP12H76xKPhg8ayEf1sPePSNEas/l
DVh2uC8dH6e9zzA3OjNnvVxHf703hzH+HKI7CiQ7P5qduTZkA1NoQ2wt+5wFDmOt
0b+eEVd2LIxjrBhY1FOE3hbE0XesQWfdpIM7g+qvtRgWjoT5CwM9Ngbg30UJmi+q
iTag9wOqAlWbhjDm/un6rDmu1NIqU9GK0T6BL/Cdd2Bxd/lwLgX1C2mSiTfIkwzh
BcXb9MqwtZOpfSZx0o9qEOl6l802YZEAWI/vXgx7GYrZePn5FVs=
=i3k1
-END PGP SIGNATURE-



pgpzC2mZQgWwN.pgp
Description: PGP signature
--- End Message ---

Processed: Re: 1074706 fpc: FTBFS: msgfmt change breaks build

[Debian Bug Tracking System]

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

> package src:fpc
Limiting to bugs with field 'package' containing at least one of 'src:fpc'
Limit currently set to 'package':'src:fpc'

> retitle 1074706 fpc: FTBFS: msgfmt change breaks build
Bug #1074706 [src:fpc] fpc: FTBFS: msgfmt change breaks buil
Changed Bug title to 'fpc: FTBFS: msgfmt change breaks build' from 'fpc: FTBFS: 
msgfmt change breaks buil'.
>
End of message, stopping processing here.

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

Processed: .

[Debian Bug Tracking System]

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

> package src:fpc
Limiting to bugs with field 'package' containing at least one of 'src:fpc'
Limit currently set to 'package':'src:fpc'

> retitle 1074706 fpc: FTBFS: msgfmt change breaks buil
Bug #1074706 [src:fpc] fpc: FTBFS: make[1]: *** [Makefile:9: de] Error 1
Changed Bug title to 'fpc: FTBFS: msgfmt change breaks buil' from 'fpc: FTBFS: 
make[1]: *** [Makefile:9: de] Error 1'.
>
End of message, stopping processing here.

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

Bug#1074529: marked as done (r-cran-dimred: autopkgtest regression with r-base 4.4.1 (i386))

[Debian Bug Tracking System]

Your message dated Fri, 12 Jul 2024 11:05:52 +
with message-id 
and subject line Bug#1074529: fixed in r-cran-dimred 0.2.6-2
has caused the Debian Bug report #1074529,
regarding r-cran-dimred: autopkgtest regression with r-base 4.4.1 (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.)


-- 
1074529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074529
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-dimred
Version: 0.2.6-1
Severity: serious
Tags: trixie sid
X-Debbugs-Cc: Dirk Eddelbuettel 
User: debian...@lists.debian.org
Usertags: regression

Hi Maintainer

r-cran-dimred's autopkgtest regresses when tested with r-base 4.4.1
[1]. I've copied what I hope is the relevant part of the log below.

Regards
Graham


[1] https://ci.debian.net/packages/r/r-cran-dimred/testing/i386/


134s == Failed tests

134s -- Failure ('test_NNMF.R:105:3'): other arguments
--
134s dim_3_a...@other.data$w (`actual`) not equal to `dim_3_rot` (`expected`).
134s
134s actual vs expected
134s [,1] [,2] [,3]
134s - actual[1, ] 33.86881 2.220446e-16 2.220446e-16
134s + expected[1, ] 11.62495 2.220446e-16 2.240198e+01
134s - actual[2, ] 37.52666 2.958845e+01 1.976184e+01
134s + expected[2, ] 31.25542 3.643579e+01 4.210810e+01
134s - actual[3, ] 38.97432 5.482087e+01 4.372093e+01
134s + expected[3, ] 50.88589 7.287158e+01 6.181422e+01
134s - actual[4, ] 69.27110 1.369114e+02 1.289431e+01
134s + expected[4, ] 70.51636 1.093074e+02 8.152034e+01
134s - actual[5, ] 29.33830 8.058796e+01 1.154367e+02
134s + expected[5, ] 90.14683 1.457432e+02 1.012265e+02
134s -- Failure ('test_NNMF.R:106:3'): other arguments
--
134s getData(getDimRedData(dim_3_args)) (`actual`) not equal to
`dim_3_pred` (`expected`).
134s
134s actual vs expected
134s [,1] [,2] [,3]
134s - actual[1, ] 2.220446e-16 0.39921880 4.143205e-01
134s + expected[1, ] 2.220446e-16 0.54891084 2.220446e-16
134s - actual[2, ] 5.905139e-02 0.38264119 4.282111e-01
134s + expected[2, ] 7.317427e-02 0.48173830 5.130585e-02
134s - actual[3, ] 1.181028e-01 0.36606358 4.421018e-01
134s + expected[3, ] 1.948635e-01 0.40204353 7.743607e-02
134s - actual[4, ] 1.771542e-01 0.34948596 4.559924e-01
134s + expected[4, ] 5.022464e-01 0.27441923 7.205177e-03
134s - actual[5, ] 2.362056e-01 0.33290835 4.698830e-01
134s + expected[5, ] 5.575179e-01 0.21186758 6.780121e-02
134s - actual[6, ] 2.952569e-01 0.31633074 4.837737e-01
134s + expected[6, ] 1.972195e-01 0.25657899 3.440469e-01
134s - actual[7, ] 3.543083e-01 0.29975313 4.976643e-01
134s + expected[7, ] 8.607848e-02 0.23698021 4.909986e-01
134s - actual[8, ] 4.133597e-01 0.28317552 5.115549e-01
134s + expected[8, ] 1.590949e-01 0.16984841 5.423864e-01
134s - actual[9, ] 4.724111e-01 0.26659790 5.254456e-01
134s + expected[9, ] 1.036687e-01 0.13586905 6.604263e-01
134s - actual[10, ] 5.314625e-01 0.25002029 5.393362e-01
134s + expected[10, ] 2.164839e-01 0.05846474 6.911614e-01
134s -- Failure ('test_NNMF.R:132:3'): other arguments
--
134s `dim_3_apply` (`actual`) not equal to `dim_3_exp` (`expected`).
134s
134s actual vs expected
134s [,1] [,2] [,3]
134s - actual[1, ] 0.02952569 0.3909300 0.42126582
134s + expected[1, ] 0.11873045 0.4941225 -0.01697331
134s - actual[2, ] 0.08857708 0.3743524 0.43515645
134s + expected[2, ] 0.14408070 0.4392939 0.05914963
134s - actual[3, ] 0.14762847 0.3577748 0.44904709
134s + expected[3, ] 0.16943094 0.3844652 0.13527257
134s -- Failure ('test_NNMF.R:133:3'): other arguments
--
134s `dim_3_pred` (`actual`) not equal to `dim_3_exp` (`expected`).
134s
134s actual vs expected
134s [,1] [,2] [,3]
134s - actual[1, ] 0.02952569 0.3909300 0.42126582
134s + expected[1, ] 0.11873045 0.4941225 -0.01697331
134s - actual[2, ] 0.08857708 0.3743524 0.43515645
134s + expected[2, ] 0.14408070 0.4392939 0.05914963
134s - actual[3, ] 0.14762847 0.3577748 0.44904709
134s + expected[3, ] 0.16943094 0.3844652 0.13527257
134s
134s [ FAIL 4 | WARN 96 | SKIP 2 | PASS 107 ]
134s Error: Test failures
--- End Message ---
--- Begin Message ---
Source: r-cran-dimred
Source-Version: 0.2.6-2
Done: Michael R. Crusoe 

We believe that the bug you reported is fixed in the latest version of
r-cran-dimred, 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 

Bug#1072629: marked as done (r-cran-dials: autopkgtest regression in testing)

[Debian Bug Tracking System]

Your message dated Fri, 12 Jul 2024 11:05:43 +
with message-id 
and subject line Bug#1072629: fixed in r-cran-dials 1.2.1-1
has caused the Debian Bug report #1072629,
regarding r-cran-dials: autopkgtest regression 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.)


-- 
1072629: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072629
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-dials
Version: 1.2.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Hi Maintainer

Sometime around 2024-02-15, r-cran-dials' autopkgtest regressed in
testing [1].  I've copied what I hope is the relevant part of the log
below.

Regards
Graham


[1] https://ci.debian.net/packages/r/r-cran-dials/testing/amd64/
53s > library(testthat)
53s > library(dials)
53s Loading required package: scales
54s >
54s > if (requireNamespace("xml2")) {
54s + test_check("dials", reporter = MultiReporter$new(reporters =
list(JunitReporter$new(file = "test-results.xml"),
CheckReporter$new(
54s + } else {
54s + test_check("dials")
54s + }
54s Loading required namespace: xml2
54s Error in UseMethod("xml_add_child") :
54s no applicable method for 'xml_add_child' applied to an object of
class "NULL"
54s Calls: test_check ... o_apply -> lapply -> FUN ->  -> 
54s Execution halted
--- End Message ---
--- Begin Message ---
Source: r-cran-dials
Source-Version: 1.2.1-1
Done: Michael R. Crusoe 

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

Debian distribution maintenance software
pp.
Michael R. Crusoe  (supplier of updated r-cran-dials 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, 12 Jul 2024 11:53:45 +0200
Source: r-cran-dials
Architecture: source
Version: 1.2.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers 
Changed-By: Michael R. Crusoe 
Closes: 1072629
Changes:
 r-cran-dials (1.2.1-1) unstable; urgency=medium
 .
   [ Charles Plessy ]
   * Team upload.
   * New upstream version
   * Standards-Version: 4.7.0 (routine-update)
   * dh-update-R to update Build-Depends (routine-update)
 .
   [ Michael R. Crusoe ]
   * Added patch to emit JUnit output during the test. Closes: #1072629
Checksums-Sha1:
 23f1096245dfcead59af3c0db392f14050114bc0 2367 r-cran-dials_1.2.1-1.dsc
 46cc9a642bd508387d0b3c10ab0ead31ae6cbc6c 138389 r-cran-dials_1.2.1.orig.tar.gz
 da41fd9c7f9c6addad56250f10275e776c792812 3480 
r-cran-dials_1.2.1-1.debian.tar.xz
 90fe247a4dfe7ad25051f8557e3c5b718f614f85 12084 
r-cran-dials_1.2.1-1_source.buildinfo
Checksums-Sha256:
 40e22d00c438a72b795eb76117ec2ebead79a2585e6836b7daf94602a5c999e9 2367 
r-cran-dials_1.2.1-1.dsc
 ee6bb31e0a8a6fb6118f82796acaf589b2e08cbd9b392c7fd4b2fe79c9df3b77 138389 
r-cran-dials_1.2.1.orig.tar.gz
 2f6f77d8550ecb8a4647e4d0408e1012d21305bf8b6f158586091100b37b8a43 3480 
r-cran-dials_1.2.1-1.debian.tar.xz
 ddc3034a6204a6a65b60ab6873a0473edbbc73cd5888a04e201010359e4baaf3 12084 
r-cran-dials_1.2.1-1_source.buildinfo
Files:
 fb1691a70925b813d3b4169009d274a9 2367 gnu-r optional r-cran-dials_1.2.1-1.dsc
 71af0aae8351ff80de1e3d8c55f5c135 138389 gnu-r optional 
r-cran-dials_1.2.1.orig.tar.gz
 438655c54bc21a0e99d41896a2904040 3480 gnu-r optional 
r-cran-dials_1.2.1-1.debian.tar.xz
 f226acbaaf1fababadc3d5259850f3a5 12084 gnu-r optional 
r-cran-dials_1.2.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEck1gkzcRPHEFUNdHPCZ2P2xn5uIFAmaQ/U8ACgkQPCZ2P2xn
5uLmuRAAj20BjwTwKn8+MyacKX7edf7ycHxGCojKPtexDt55oU9vx4wWKWbbe5z3
GCp489AA6oQk5ejchCzKUXVXbszLuxGFuPudfs1B2FuLaNw88i+T04k9OR+pF73b
vYjy6mmLw8NVIZ//mQtEgnpSRzVH9ijdcgGqqXsTWNyOLxuR9+gw7cj5U87SJe2G
O5GNTfnw3jo4fL8pr+Wl4LmVd+dhkNhkEcxEIYNqU2zUaj/pRwWpXFr8nHi8buqo
tNeTrJ/2tN+P2OyLuJXlEMeSnDu5vSrzNzTEEvX6zOfs1pSUQFqc9HxOgRbsqtow
9ihUbGoYT22jXLCteSgqje9Ls3rN13vpUjg8bzmhvrpQzt2m0mj584G24bEYzQEw
rPXO2NHEaGunc54bE5UPzJFqvlLzasv9jbRpyubeQRPWnZZCjG9MZelrPmFdWjIM
F2Uj7ro9P1PR6axzhomTIeIvtEwTZaJmRVF7UVLTjmGJOzrI4PBEybpui0E2uABZ

Processed: Bug#1076124 marked as pending in python-gnocchiclient

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1076124 [src:python-gnocchiclient] (build-)dependency on removed 
python3-distutils
Added tag(s) pending.

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

Bug#1076124: marked as pending in python-gnocchiclient

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #1076124 in python-gnocchiclient 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/openstack-team/clients/python-gnocchiclient/-/commit/cb5133c8b90d4640b171a4d124ed1544c8177bda


Removed distutils (build-)depends (Closes: #1076124).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1076124

Bug#1074720: marked as done (bootcd: FTBFS: dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit status 2)

[Debian Bug Tracking System]

Your message dated Fri, 12 Jul 2024 10:35:44 +
with message-id 
and subject line Bug#1074720: fixed in bootcd 6.8.1
has caused the Debian Bug report #1074720,
regarding bootcd: FTBFS: dpkg-buildpackage: error: fakeroot debian/rules binary 
subprocess returned exit status 2
to be marked as done.

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

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


-- 
1074720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074720
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bootcd
Version: 6.8
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240702 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> libfakeroot internal error: payload not recognized!
> libfakeroot internal error: payload not recognized!
> --- output with ERROR from  running  "--testdata"; err=$?> ---
> e:libfakeroot internal error: payload not recognized!
> --- (q)uit (r)edo (i)gnore (s)witch interactive ---
> ? 
> --- output with ERROR from  running  "--testdata"; err=$?> ---
> e:libfakeroot internal error: payload not recognized!
> --- (q)uit (r)edo (i)gnore (s)witch interactive ---
> ? 
> --- output with ERROR from  running  "--testdata"; err=$?> ---
> e:libfakeroot internal error: payload not recognized!
> --- (q)uit (r)edo (i)gnore (s)witch interactive ---
> ? 
> --- output with ERROR from  running  "--testdata"; err=$?> ---
> e:libfakeroot internal error: payload not recognized!
> --- (q)uit (r)edo (i)gnore (s)witch interactive ---
> ? 
> [..]
> 
> dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned 
> exit status 2
> 
> Build finished at 2024-07-02T11:17:34Z


The full build log is available from:
http://qa-logs.debian.net/2024/07/02/bootcd_6.8_unstable.log

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

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

Debian distribution maintenance software
pp.
Bernd Schumacher  (supplier of updated bootcd 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, 11 Jul 2024 14:55:42 +0200
Source: bootcd
Architecture: source
Version: 6.8.1
Distribution: unstable
Urgency: medium
Maintainer: Bernd Schumacher 
Changed-By: Bernd Schumacher 
Closes: 1074720
Changes:
 bootcd (6.8.1) unstable; urgency=medium
 .
   * Fakeroot's output "libfakeroot internal error: payload not recognized!"
 is now ignored. closes: 1074720
Checksums-Sha1:
 1cde580f6095a357def22889e69f11155aa74c59 1552 bootcd_6.8.1.dsc
 ec8787466b6df1a7d786c1fc6e93c689026ff032 82936 bootcd_6.8.1.tar.xz
 2d0b91c0b16920c6c10a5eaf5f14c6f7cf53b72b 6733 bootcd_6.8.1_source.buildinfo
Checksums-Sha256:
 06dbfc40fec3d12529e816b8f66d3c8de4d95aa8898777ad018583c02826fdf3 1552 
bootcd_6.8.1.dsc
 12cb066d4bab7ed74146ebb9a57c2eeaa5f8aff7fef46420a01bf6ac11df70ad 82936 
bootcd_6.8.1.tar.xz
 dbd20261178b5248de0670d99a9274a824d61fa598452925c68885ea76163a11 6733 
bootcd_6.8.1_source.buildinfo
Files:
 960189dbf2ae1b0a61ea207acecc41c5 1552 utils extra bootcd_6.8.1.dsc
 6d6dbd9e475fb3d431bb6b89443e1880 82936 utils extra 

Bug#1065850: dogtag-pki: Please drop dependencies on python3-distutils

[Emmanuel Arias]

Dear maintainer,

I noted that the fix of this RC bug is already in salsa [0].

Can be possible make an upload?

Thanks!

[0] 
https://salsa.debian.org/freeipa-team/dogtag-pki/-/commit/e3eaf12e7c0f7550dd56dabf6f3e3dceeeb2b2d8

-- 
cheers,
Emmanuel Arias

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  eam...@debian.org
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: 13796755BBC72BB8ABE2AEB5 FA9DEC5DE11C63F1
 
 ⠈⠳⣄


signature.asc
Description: PGP signature

Bug#1065871: grokevt: Please drop dependencies on python3-distutils

[Emmanuel Arias]

Dear maintainer,

I'm going to upload in DELAYED/3-days a NMU to fix this RC bug. I attach
the patch that I applied.

Please let me know if you have any objection or any change that you want
to do.

Also, I can prepare a MR in salsa, but I will permissions in the project.

-- 
cheers,
Emmanuel Arias

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  eam...@debian.org
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: 13796755BBC72BB8ABE2AEB5 FA9DEC5DE11C63F1
 
 ⠈⠳⣄
diff -Nru grokevt-0.5.0/debian/changelog grokevt-0.5.0/debian/changelog
--- grokevt-0.5.0/debian/changelog	2024-04-20 15:20:58.0 -0300
+++ grokevt-0.5.0/debian/changelog	2024-07-12 07:06:11.0 -0300
@@ -1,3 +1,12 @@
+grokevt (0.5.0-6.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * d/patches/remove_distutils.patch: Add patch to remove use of distutils.
+  * d/control: Remove python3-distutils from Build Dependency. Add
+python3-setuptools as Build Dependency (Closes: #1065871).
+
+ -- Emmanuel Arias   Fri, 12 Jul 2024 07:06:11 -0300
+
 grokevt (0.5.0-6) unstable; urgency=medium
 
   [ Debian Janitor ]
diff -Nru grokevt-0.5.0/debian/control grokevt-0.5.0/debian/control
--- grokevt-0.5.0/debian/control	2024-04-20 15:20:58.0 -0300
+++ grokevt-0.5.0/debian/control	2024-07-12 07:06:11.0 -0300
@@ -7,7 +7,7 @@
cpio,
dh-python,
python3,
-   python3-distutils
+   python3-setuptools,
 Standards-Version: 4.7.0
 Rules-Requires-Root: no
 Homepage: http://projects.sentinelchicken.org/grokevt/
diff -Nru grokevt-0.5.0/debian/patches/remove_distutils.patch grokevt-0.5.0/debian/patches/remove_distutils.patch
--- grokevt-0.5.0/debian/patches/remove_distutils.patch	1969-12-31 21:00:00.0 -0300
+++ grokevt-0.5.0/debian/patches/remove_distutils.patch	2024-07-12 07:06:11.0 -0300
@@ -0,0 +1,17 @@
+Description: Remove distutils from source
+ This package use setup from setuptools instead of the setup from the deprecated
+ distutils module.
+Author: Emmanuel Arias 
+Bug-Debian: https://bugs.debian.org/1065817
+Forwarded: https://github.com/ecbftw/grokevt/pull/1
+Last-Update: 2024-07-12
+---
+This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
+--- a/grokevt-distutils.py
 b/grokevt-distutils.py
+@@ -1,4 +1,4 @@
+ # Called from make with appropriate python version
+ 
+-from distutils.core import setup
++from setuptools import setup
+ setup(name='grokevt', version='0.5', package_dir={'':'lib'}, py_modules=['grokevt'])
diff -Nru grokevt-0.5.0/debian/patches/series grokevt-0.5.0/debian/patches/series
--- grokevt-0.5.0/debian/patches/series	2024-04-20 15:20:58.0 -0300
+++ grokevt-0.5.0/debian/patches/series	2024-07-12 07:06:11.0 -0300
@@ -2,3 +2,4 @@
 makefile.patch
 python3-shebang.patch
 no_egg.patch
+remove_distutils.patch


signature.asc
Description: PGP signature

Bug#1074706: [Pkg-pascal-devel] Bug#1074706: Bug#1074706: msgfmt change breaks build

[Peter Blackman]

Raised bug report upstream,
https://gitlab.com/freepascal.org/fpc/source/-/issues/40853

and updated the patch header.
Subject: Fix msgfmt related build fail
Author: Peter Blackman 
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074706
Forwarded: https://gitlab.com/freepascal.org/fpc/source/-/issues/40853
===
--- a/fpcsrc/utils/fpdoc/intl/dglobals.de.po
+++ b/fpcsrc/utils/fpdoc/intl/dglobals.de.po
@@ -1,3 +1,7 @@
+msgid ""
+msgstr ""
+"Content-Type: text/plain; charset=UTF-8\n"
+
 #: dglobals:sdocpackagetitle
 msgid "Reference for package '%s'"
 msgstr "Referenz für Paket '%s'"
Index: b/fpcsrc/utils/fpdoc/intl/dwriter.de.po
===
--- a/fpcsrc/utils/fpdoc/intl/dwriter.de.po
+++ b/fpcsrc/utils/fpdoc/intl/dwriter.de.po
@@ -1,3 +1,7 @@
+msgid ""
+msgstr ""
+"Content-Type: text/plain; charset=UTF-8\n"
+
 #: dwriter:serrfilewriting
 msgid "An error occurred during writing of file \"%s\": %s"
 msgstr "Beim Schreiben der Datei \"%s\" ist ein Fehler aufgetrete: %s"
Index: b/fpcsrc/utils/fpdoc/intl/fpdoc.de.po
===
--- a/fpcsrc/utils/fpdoc/intl/fpdoc.de.po
+++ b/fpcsrc/utils/fpdoc/intl/fpdoc.de.po
@@ -1,3 +1,7 @@
+msgid ""
+msgstr ""
+"Content-Type: text/plain; charset=UTF-8\n"
+
 #: fpdoc:stitle
 msgid "FPDoc - Free Pascal Documentation Tool"
 msgstr "FPDoc - Free-Pascal-Dokumentationstool"
Index: b/fpcsrc/utils/fpdoc/intl/makeskel.de.po
===
--- a/fpcsrc/utils/fpdoc/intl/makeskel.de.po
+++ b/fpcsrc/utils/fpdoc/intl/makeskel.de.po
@@ -1,3 +1,7 @@
+msgid ""
+msgstr ""
+"Content-Type: text/plain; charset=UTF-8\n"
+
 #: makeskel:stitle
 msgid "MakeSkel - FPDoc skeleton XML description file generator"
 msgstr "MakeSkel - Skelett-Generator für FPDoc-XML-Beschreibungsdateien"

Bug#1076198: libuhd4.7.0-dpdk-tests has an undeclared file conflict

[Helmut Grohne]

Package: libuhd4.7.0-dpdk-tests
Version: 4.7.0.0+ds1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + libuhd4.6.0-dpdk-tests

libuhd4.7.0-dpdk-tests has an undeclared file conflict. This may result
in an unpack error from dpkg.

The files
 * /usr/lib/uhd/tests/4.6.0/dpdk_port_test
 * /usr/lib/uhd/tests/4.6.0/dpdk_test
are contained in the packages
 * libuhd4.6.0-dpdk-tests/4.6.0.0+ds1-6+b1 as present in trixie|unstable
 * libuhd4.7.0-dpdk-tests/4.7.0.0+ds1-1 as present in experimental

These packages can be unpacked concurrently, because there is no
relevant Replaces or Conflicts relation. Attempting to unpack these
packages concurrently results in an unpack error from dpkg, because none
of the packages installs a diversion for the affected files.

Kind regards

The Debian Usr Merge Analysis Tool

This bug report has been automatically filed with no human intervention.
The source code is available at https://salsa.debian.org/helmutg/dumat.
If the filing is unclear or in error, don't hesitate to contact
hel...@subdivi.de for assistance.

Processed: libuhd4.7.0-dpdk-tests has an undeclared file conflict

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + libuhd4.6.0-dpdk-tests
Bug #1076198 [libuhd4.7.0-dpdk-tests] libuhd4.7.0-dpdk-tests has an undeclared 
file conflict
Added indication that 1076198 affects libuhd4.6.0-dpdk-tests

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

Processed: Bug#1072629 marked as pending in r-cran-dials

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1072629 [src:r-cran-dials] r-cran-dials: autopkgtest regression in testing
Added tag(s) pending.

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

Bug#1072629: marked as pending in r-cran-dials

[Michael R. Crusoe]

Control: tag -1 pending

Hello,

Bug #1072629 in r-cran-dials 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/r-pkg-team/r-cran-dials/-/commit/ca5f5655fe1df93d0aa5f0a21e3ee59b1fa7514a


Added patch to emit JUnit output during the test. Closes: #1072629


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1072629

Bug#1074528: marked as pending in r-bioc-eir

[Michael R. Crusoe]

Control: tag -1 pending

Hello,

Bug #1074528 in r-bioc-eir 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/r-pkg-team/r-bioc-eir/-/commit/dfbf95e2bfbc4a065b9e8f507d7f565959bfa339


Drop support for 32-bit architectures, following upstream's decision Closes: 
#1074528


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1074528

Processed: Bug#1074528 marked as pending in r-bioc-eir

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1074528 [src:r-bioc-eir] r-bioc-eir: autopkgtest regression with r-base 
4.4.1 (i386)
Added tag(s) pending.

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

Bug#1071344: marked as pending in r-bioc-oligo

[Michael R. Crusoe]

Control: tag -1 pending

Hello,

Bug #1071344 in r-bioc-oligo 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/r-pkg-team/r-bioc-oligo/-/commit/67ccf772cadfb19ba3b960f770bc5d40648be12c


new upstream version fixes FTBFS. Closes: #1071344


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1071344

Processed: Bug#1071344 marked as pending in r-bioc-oligo

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1071344 [src:r-bioc-oligo] r-bioc-oligo: FTBFS: basecontent.c:54:15: 
error: format not a string literal and no format arguments
Added tag(s) pending.

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

Bug#1076194: remove python3.11 before the trixie release

[Matthias Klose]

Source: python3.11
Version: 3.11.9-1
Severity: serious
Tags: sid trixie

remove python3.11 before the trixie release, superseded by 3.12.

Processed: Re: mdtraj: fails to build

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1076166 [src:mdtraj] mdtraj: fails to build
Added tag(s) patch.

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

Bug#1076166: mdtraj: fails to build

[Sudip Mukherjee]

Control: tags -1 patch
--

On Thu, Jul 11, 2024 at 10:02:07PM +0100, Sudip Mukherjee wrote:
> Source: mdtraj
> Version: 1.10.0-2
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
> X-Debbugs-Cc: sudipm.mukher...@gmail.com
> 
> Dear Maintainer,
> 
> mdtraj is failing to build from source with the error:

The attached patch will fix the build.

-- 
Regards
Sudip
diff -Nru mdtraj-1.10.0/debian/changelog mdtraj-1.10.0/debian/changelog
--- mdtraj-1.10.0/debian/changelog  2024-07-05 17:32:59.0 +0100
+++ mdtraj-1.10.0/debian/changelog  2024-07-11 21:58:27.0 +0100
@@ -1,3 +1,10 @@
+mdtraj (1.10.0-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * cleanup files in correct path. (Closes: #1076166)
+
+ -- Sudip Mukherjee   Thu, 11 Jul 2024 21:58:27 
+0100
+
 mdtraj (1.10.0-2) unstable; urgency=medium
 
   * debian patch remove_six_PR1908.patch applies upstream PR#1908 to
diff -Nru mdtraj-1.10.0/debian/rules mdtraj-1.10.0/debian/rules
--- mdtraj-1.10.0/debian/rules  2024-07-05 17:32:59.0 +0100
+++ mdtraj-1.10.0/debian/rules  2024-07-11 21:58:21.0 +0100
@@ -55,8 +55,8 @@
# but dh_python3 can't tell the difference between the different builds,
# since py3.11 compiles libtheobald.o with -fwrapv, where py3.12 uses 
-fno-strict-overflow
# So clean up manually (assume the binary difference is not an issue)
-   rm -f 
debian/python3-$(PYBUILD_NAME)/usr/lib/python3.*/dist-packages/mdtraj/core/lib/libtheobald.a
-   rmdir -p --ignore-fail-on-non-empty 
debian/python3-$(PYBUILD_NAME)/usr/lib/python3.*/dist-packages/mdtraj/core/lib
+   rm -f 
debian/python3-$(PYBUILD_NAME)/usr/lib/python3*/dist-packages/mdtraj/core/lib/libtheobald.a
+   rmdir -p --ignore-fail-on-non-empty 
debian/python3-$(PYBUILD_NAME)/usr/lib/python3*/dist-packages/mdtraj/core/lib
 
 override_dh_sphinxdoc-indep:
dh_sphinxdoc -i

Processed: still pending

[Debian Bug Tracking System]

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

> tag 1071342 pending
Bug #1071342 [src:r-bioc-hdf5array] r-bioc-hdf5array: FTBFS: 
H5DSetDescriptor.c:1182:17: error: format not a string literal and no format 
arguments
Added tag(s) pending.
>
End of message, stopping processing here.

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

Processed: Bug#1071353 marked as pending in r-bioc-xvector

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1071353 [src:r-bioc-xvector] r-bioc-xvector: FTBFS: 
RDS_random_access.c:136:17: error: format not a string literal and no format 
arguments
Added tag(s) pending.

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

Bug#1071353: marked as pending in r-bioc-xvector

[Michael R. Crusoe]

Control: tag -1 pending

Hello,

Bug #1071353 in r-bioc-xvector 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/r-pkg-team/r-bioc-xvector/-/commit/b3278f8cc1507df25721f3b183efd05c05f1bbed


new upstream version fixes FTBFS. Closes: #1071353


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1071353

Bug#1071523: r-cran-spatstat.geom: autopkgtest regression in testing

[Michael R. Crusoe]

On Tue, 2 Jul 2024 16:15:26 + Graham Inggs  wrote:
> Hi Andreas
>
> > r-cran-spatstat.core was removed from Debian. R-cran-spatstat.geom does
> > not depend from this package any more and the autopkgtest in Salsa CI is
> > fine[1]. Any hint why it fails in testing would be welcome.
>
> 82s autopkgtest [21:16:20]:  summary
> 82s run-unit-test PASS
> 82s pkg-r-autopkgtest FAIL badpkg
>
> It is only the 'pkg-r-autopkgtest' that is failing. The
> 'run-unit-test' defined inside the r-cran-spatstat.geom package
> succeeds.
>
> This looks like a bug in autodep8, where pkg-r-autopkgtest is defined.
> It could be the same as #961138.

Good day,

While my MR doesn't fix the issue of querying the wrong distribution metadata, 
it does fix the overmatching that led to r-cran-spatstat.core (and others) 
being selected when not requested:

https://salsa.debian.org/ci-team/autodep8/-/merge_requests/36

Please consider merging that MR and releasing a new autodep8 so we can re-run 
the autopkgtests for r-cran-spatstat* and other affected packages 
(r-cran-stars, r-cran-sf, r-cran-sparr, r-cran-epir, etc..) and get them back 
into testing.

Thank you!





OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: Bug#1071352 marked as pending in r-bioc-variantannotation

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1071352 [src:r-bioc-variantannotation] r-bioc-variantannotation: FTBFS: 
vcffile.c:46:5: error: format not a string literal and no format arguments
Added tag(s) pending.

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

Bug#1071352: marked as pending in r-bioc-variantannotation

[Michael R. Crusoe]

Control: tag -1 pending

Hello,

Bug #1071352 in r-bioc-variantannotation 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/r-pkg-team/r-bioc-variantannotation/-/commit/b1fadf5ab249ac6f06690b49be43b461af244fba


new upstream version fixes FTBFS. Closes: #1071352


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1071352

Processed: Bug#1071347 marked as pending in r-bioc-rtracklayer

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1071347 [src:r-bioc-rtracklayer] r-bioc-rtracklayer: FTBFS: 
handlers.c:10:11: error: format not a string literal and no format arguments
Added tag(s) pending.

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

Bug#1071347: marked as pending in r-bioc-rtracklayer

[Michael R. Crusoe]

Control: tag -1 pending

Hello,

Bug #1071347 in r-bioc-rtracklayer 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/r-pkg-team/r-bioc-rtracklayer/-/commit/cd36736bece8d52d0d8c1bb3ff2f4ea6330e7324


New upstream release fixes FTBFS. Closes: #1071347


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1071347

Bug#1074697: marked as done (nordugrid-arc-nagios-plugins: FTBFS: ImportError: cannot import name 'SafeConfigParser' from 'configparser' (/usr/lib/python3.12/configparser.py). Did you mean: 'RawConfig

[Debian Bug Tracking System]

Your message dated Fri, 12 Jul 2024 06:34:46 +
with message-id 
and subject line Bug#1074697: fixed in nordugrid-arc-nagios-plugins 2.0.1-2
has caused the Debian Bug report #1074697,
regarding nordugrid-arc-nagios-plugins: FTBFS: ImportError: cannot import name 
'SafeConfigParser' from 'configparser' (/usr/lib/python3.12/configparser.py). 
Did you mean: 'RawConfigParser'?
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.)


-- 
1074697: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074697
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nordugrid-arc-nagios-plugins
Version: 2.0.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240702 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[2]: Entering directory '/<>/doc'
> sphinx-build -b html -d _build/doctrees   . _build/html
> Running Sphinx v7.2.6
> making output directory... done
> WARNING: html_static_path entry '_static' does not exist
> building [mo]: targets for 0 po files that are out of date
> writing output... 
> building [html]: targets for 6 source files that are out of date
> updating environment: [new config] 6 added, 0 changed, 0 removed
> reading sources... [ 17%] arcce
> reading sources... [ 33%] arcinfosys
> reading sources... [ 50%] gridstorage
> reading sources... [ 67%] index
> reading sources... [ 83%] intro
> reading sources... [100%] sample_config
> 
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... done
> preparing documents... done
> copying assets... copying static files... done
> copying extra files... done
> done
> writing output... [ 17%] arcce
> writing output... [ 33%] arcinfosys
> writing output... [ 50%] gridstorage
> writing output... [ 67%] index
> writing output... [ 83%] intro
> writing output... [100%] sample_config
> 
> generating indices... genindex done
> writing additional pages... search done
> dumping search index in English (code: en)... done
> dumping object inventory... done
> build succeeded, 1 warning.
> 
> The HTML pages are in _build/html.
> 
> Build finished. The HTML pages are in _build/html.
> make[2]: Leaving directory '/<>/doc'
> make[1]: Leaving directory '/<>'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:311: cd /<>/.pybuild/cpython3_3.12/build; 
> python3.12 -m unittest discover -v 
> arcnagios.ce.jobplugins (unittest.loader._FailedTest.arcnagios.ce.jobplugins) 
> ... ERROR
> 
> ==
> ERROR: arcnagios.ce.jobplugins 
> (unittest.loader._FailedTest.arcnagios.ce.jobplugins)
> --
> ImportError: Failed to import test module: arcnagios.ce.jobplugins
> Traceback (most recent call last):
>   File "/usr/lib/python3.12/unittest/loader.py", line 429, in _find_test_path
> package = self._get_module_from_name(name)
>   
>   File "/usr/lib/python3.12/unittest/loader.py", line 339, in 
> _get_module_from_name
> __import__(name)
>   File 
> "/<>/.pybuild/cpython3_3.12/build/arcnagios/ce/jobplugins/__init__.py",
>  line 3, in 
> from arcnagios.ce.jobplugins.scripted import ScriptedJobPlugin
>   File 
> "/<>/.pybuild/cpython3_3.12/build/arcnagios/ce/jobplugins/scripted.py",
>  line 5, in 
> from arcnagios.ce.jobplugin import JobPlugin
>   File 
> "/<>/.pybuild/cpython3_3.12/build/arcnagios/ce/jobplugin.py", 
> line 4, in 
> from arcnagios import substitution
>   File 
> "/<>/.pybuild/cpython3_3.12/build/arcnagios/substitution.py", 
> line 8, in 
> from arcnagios.nagutils import ServiceUnknown
>   File "/<>/.pybuild/cpython3_3.12/build/arcnagios/nagutils.py", 
> line 5, in 
> from configparser import SafeConfigParser, InterpolationError, 
> NoOptionError
> ImportError: cannot import name 'SafeConfigParser' from 'configparser' 
> (/usr/lib/python3.12/configparser.py). Did you mean: 'RawConfigParser'?
> 
> 
> --
> Ran 1 test in 0.002s
> 
> FAILED (errors=1)
> E: pybuild pybuild:389: test: plugin distutils failed with: exit code=1: cd 
> /<>/.pybuild/cpython3_3.12/build; python3.12 -m unittest 
> discover -v 
> dh_auto_test: error: pybuild --test -i python{version} -p 3.12 returned exit 
> code 13


The full build log is available from:

Bug#1071351: marked as pending in r-bioc-sparsearray

[Michael R. Crusoe]

Control: tag -1 pending

Hello,

Bug #1071351 in r-bioc-sparsearray 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/r-pkg-team/r-bioc-sparsearray/-/commit/e05553d69df910f7074d8ebb4d86b31a89ca9077


new upstream version fixes FTBFS. Closes: #1071351


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1071351

Processed: Bug#1071351 marked as pending in r-bioc-sparsearray

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1071351 [src:r-bioc-sparsearray] r-bioc-sparsearray: FTBFS: 
leaf_vector_utils.c:33:17: error: format not a string literal and no format 
arguments
Added tag(s) pending.

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