Bug#1052845: closing 1052845

[Alexandre Rossi]

close 1052845 1:0.5.0-5
thanks

Processed: closing 1052845

[Debian Bug Tracking System]

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

> close 1052845 1:0.5.0-5
Bug #1052845 [src:python-django-tagging] python-django-tagging: FTBFS: 
dh_auto_test: error: pybuild --test -i python{version} -p 3.11 --system=custom 
"--test-args=PYTHONPATH=. DJANGO_SETTINGS_MODULE=tagging.tests.settings 
django-admin test --verbosity=2" returned exit code 13
Marked as fixed in versions python-django-tagging/1:0.5.0-5.
Bug #1052845 [src:python-django-tagging] python-django-tagging: FTBFS: 
dh_auto_test: error: pybuild --test -i python{version} -p 3.11 --system=custom 
"--test-args=PYTHONPATH=. DJANGO_SETTINGS_MODULE=tagging.tests.settings 
django-admin test --verbosity=2" returned exit code 13
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: Re: Bug#1055643: mutter 45.1 not installable from experimental

[Debian Bug Tracking System]

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

> tags 1055643 + ftbfs experimental
Bug #1055643 [mutter] mutter 45.1 not installable from experimental
Added tag(s) experimental and ftbfs.
> severity 1055643 serious
Bug #1055643 [mutter] mutter 45.1 not installable from experimental
Severity set to 'serious' from 'normal'
>
End of message, stopping processing here.

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

Bug#1055510: Best way to coordinate this fix

[Francois Marier]

On 2023-11-08 at 21:15:58, Helmut Grohne (hel...@subdivi.de) wrote:
> Thank you. I suggest going via experimental first.

I've just uploaded to experimental. If there are any tests you can easily
run there, please do so.

I've upgraded in unstable from the current version to 0.8 without problems,
so that should in theory work when I eventually upload to unstable.

Francois

-- 
https://fmarier.org/

Bug#1055510: marked as done (molly-guard: diversions need to be updated to deal with DEP17 P3)

[Debian Bug Tracking System]

Your message dated Fri, 10 Nov 2023 06:12:56 +
with message-id 
and subject line Bug#1055510: fixed in molly-guard 0.8
has caused the Debian Bug report #1055510,
regarding molly-guard: diversions need to be updated to deal with DEP17 P3
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.)


-- 
1055510: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055510
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: molly-guard
Severity: serious
User: helm...@debian.org
Usertags: dep17p3
Control: affects -1 + systemd-sysv

Dear Maintainer(s),

systemd-sysv 255~rc1-3, currently in experimental, moves
halt/poweroff/reboot/shutdown from /sbin/ to /usr/sbin/, and thus
diversions employed by this package fall afoul of DEP17 P3. Please
update the diversions as needed. For now, systemd-sysv has an
unversioned conflict to avoid data losses. This will be uploaded to
unstable this week. As soon as a fixed version of this package is
uploaded, the conflict will be changed to versioned.

For more details, see:

https://subdivi.de/~helmut/dep17.html
https://subdivi.de/~helmut/dumat.yaml

-- 
Kind regards,
Luca Boccassi


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: molly-guard
Source-Version: 0.8
Done: Francois Marier 

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

Debian distribution maintenance software
pp.
Francois Marier  (supplier of updated molly-guard 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, 09 Nov 2023 21:53:32 -0800
Source: molly-guard
Architecture: source
Version: 0.8
Distribution: experimental
Urgency: medium
Maintainer: Simó Albert i Beltran 
Changed-By: Francois Marier 
Closes: 1053438 1055510
Changes:
 molly-guard (0.8) experimental; urgency=medium
 .
   [ Debian Janitor ]
   * Bump debhelper from old 10 to 13.
   * Set debhelper-compat version in Build-Depends.
   * Update renamed lintian tag names in lintian overrides.
   * Update standards version to 4.5.1, no changes needed.
 .
   [ Andrew Ruthven ]
   * Add support for skipping checks if being run by configuration management
 (currently only Ansible is detected) (closes: #1053438)
   * Update standards version to 4.6.2, no changes needed.
   * Refresh lintian overrides
 .
   [ Helmut Grohne ]
   * Duplicate aliased diversions for DEP17 M18. (Closes: #1055510)
   * Move all files to /usr.
 .
   [ Francois Marier ]
   * Mark that debian/rules currently requires root (to set file ownership).
Checksums-Sha1:
 c1df4df50dfebcb49bab8615dce42a80ec0735a0 1859 molly-guard_0.8.dsc
 dd256d00466b8385188641c335d4b5cddae95a53 13828 molly-guard_0.8.tar.xz
 185363f8594e7c55f90c25676432b9a24548faf4 5830 molly-guard_0.8_source.buildinfo
Checksums-Sha256:
 c848fae7e963c5f07aab47924df52e6f07518ec6b601129bec56d3b68a446cdd 1859 
molly-guard_0.8.dsc
 1e2d56fea18809849817229e871801de65c67ec09d0dae91f5ba42192fccae56 13828 
molly-guard_0.8.tar.xz
 07c66ebbe94b4bf9e8ace44f07befcd3e996e8e3008d42fc4fb54b096d7c4bd3 5830 
molly-guard_0.8_source.buildinfo
Files:
 0ba46772537abc4e317102a64d40fbf7 1859 admin optional molly-guard_0.8.dsc
 b65c9c694049c383cbec07a0fe0d22ba 13828 admin optional molly-guard_0.8.tar.xz
 e63000b46f41750d0b146a5ee42bc607 5830 admin optional 
molly-guard_0.8_source.buildinfo

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEEjEcLKgsxVo4RDUMlFigfLgB8mNEFAmVNxaxfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDhD
NDcwQjJBMEIzMTU2OEUxMTBENDMyNTE2MjgxRjJFMDA3Qzk4RDEACgkQFigfLgB8
mNE3iw//ZOSvfdA4CyFNHbC34Bkz0qd+i1u5PcIwfnNbCEBsQY/076rdHnYg5+E5
mqPC0ymY5YhgayUH1rKOMdSlJnt2TMyr/FIdxIg1UiXKpnlqaNN0TnmPeHyfVRCi
bHZ6hxMoPjRw0C7KQTsBeu86eoi5aHNcsU03cxZoGwEHK3tvtvYCm33HnsU/5923
651nwcFUl8rZYZ0c7aBE5Nc6Uw4RLNAVE0Z9KbQv6bM+YCh+W7CRTOicS+UFDBd4
Vx8F2IiJWMzN/+Cddni/iO8q6mJehg0Z3ypZc0NBTlPQnPWGhYmXmxcGrWmcopa/
3chuyQuwIen58nFOUqWFSU1c7cis7OMfpM4WVq5Cf8dSBAKD7QZ65+JIqAF9V1hV
N6f1FUEzISQ4oy99bXSVaRdzxb2wODL2cD+d0oTsce4QQS4F7cMJJPeyrNKodNm8

Bug#1055680: libpython3.12-stdlib has an undeclared file conflict

[Helmut Grohne]

Package: libpython3.12-stdlib
Version: 3.12.0-3
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + libpython3.12-testsuite

libpython3.12-stdlib has an undeclared file conflict. This may result in
an unpack error from dpkg.

The files
 * /usr/lib/python3.12/test/typinganndata/__init__.py
 * /usr/lib/python3.12/test/typinganndata/ann_module9.py
are contained in the packages
 * libpython3.12-stdlib/3.12.0-3 as present in unstable
 * libpython3.12-testsuite/3.12.0-1 as present in trixie

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: libpython3.12-stdlib has an undeclared file conflict

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + libpython3.12-testsuite
Bug #1055680 [libpython3.12-stdlib] libpython3.12-stdlib has an undeclared file 
conflict
Added indication that 1055680 affects libpython3.12-testsuite

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

Bug#1055679: nvchecker and python3-nvchecker have an undeclared file conflict on 56 files

[Helmut Grohne]

Package: nvchecker,python3-nvchecker
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict

The files
 * /usr/bin/nvchecker
 * /usr/bin/nvchecker-ini2toml
 * /usr/bin/nvchecker-notify
 * /usr/bin/nvcmp
 * /usr/bin/nvtake
 * /usr/lib/python3/dist-packages/nvchecker/__init__.py
 * /usr/lib/python3/dist-packages/nvchecker/__main__.py
 * /usr/lib/python3/dist-packages/nvchecker/api.py
 * /usr/lib/python3/dist-packages/nvchecker/core.py
 * /usr/lib/python3/dist-packages/nvchecker/ctxvars.py
 * /usr/lib/python3/dist-packages/nvchecker/httpclient/__init__.py
 * /usr/lib/python3/dist-packages/nvchecker/httpclient/aiohttp_httpclient.py
 * /usr/lib/python3/dist-packages/nvchecker/httpclient/base.py
 * /usr/lib/python3/dist-packages/nvchecker/httpclient/httpx_httpclient.py
 * /usr/lib/python3/dist-packages/nvchecker/httpclient/tornado_httpclient.py
 * /usr/lib/python3/dist-packages/nvchecker/lib/__init__.py
 * /usr/lib/python3/dist-packages/nvchecker/lib/nicelogger.py
 * /usr/lib/python3/dist-packages/nvchecker/lib/packaging_version.py
 * /usr/lib/python3/dist-packages/nvchecker/slogconf.py
 * /usr/lib/python3/dist-packages/nvchecker/sortversion.py
 * /usr/lib/python3/dist-packages/nvchecker/tools.py
 * /usr/lib/python3/dist-packages/nvchecker/util.py
 * /usr/lib/python3/dist-packages/nvchecker_source/alpm.py
 * /usr/lib/python3/dist-packages/nvchecker_source/android_sdk.py
 * /usr/lib/python3/dist-packages/nvchecker_source/anitya.py
 * /usr/lib/python3/dist-packages/nvchecker_source/apt.py
 * /usr/lib/python3/dist-packages/nvchecker_source/archpkg.py
 * /usr/lib/python3/dist-packages/nvchecker_source/aur.py
 * /usr/lib/python3/dist-packages/nvchecker_source/bitbucket.py
 * /usr/lib/python3/dist-packages/nvchecker_source/cmd.py
 * /usr/lib/python3/dist-packages/nvchecker_source/combiner.py
 * /usr/lib/python3/dist-packages/nvchecker_source/container.py
 * /usr/lib/python3/dist-packages/nvchecker_source/cpan.py
 * /usr/lib/python3/dist-packages/nvchecker_source/cratesio.py
 * /usr/lib/python3/dist-packages/nvchecker_source/debianpkg.py
 * /usr/lib/python3/dist-packages/nvchecker_source/gems.py
 * /usr/lib/python3/dist-packages/nvchecker_source/git.py
 * /usr/lib/python3/dist-packages/nvchecker_source/gitea.py
 * /usr/lib/python3/dist-packages/nvchecker_source/github.py
 * /usr/lib/python3/dist-packages/nvchecker_source/gitlab.py
 * /usr/lib/python3/dist-packages/nvchecker_source/hackage.py
 * /usr/lib/python3/dist-packages/nvchecker_source/htmlparser.py
 * /usr/lib/python3/dist-packages/nvchecker_source/httpheader.py
 * /usr/lib/python3/dist-packages/nvchecker_source/manual.py
 * /usr/lib/python3/dist-packages/nvchecker_source/none.py
 * /usr/lib/python3/dist-packages/nvchecker_source/npm.py
 * /usr/lib/python3/dist-packages/nvchecker_source/openvsx.py
 * /usr/lib/python3/dist-packages/nvchecker_source/packagist.py
 * /usr/lib/python3/dist-packages/nvchecker_source/pacman.py
 * /usr/lib/python3/dist-packages/nvchecker_source/pagure.py
 * /usr/lib/python3/dist-packages/nvchecker_source/pypi.py
 * /usr/lib/python3/dist-packages/nvchecker_source/regex.py
 * /usr/lib/python3/dist-packages/nvchecker_source/repology.py
 * /usr/lib/python3/dist-packages/nvchecker_source/sparkle.py
 * /usr/lib/python3/dist-packages/nvchecker_source/ubuntupkg.py
 * /usr/lib/python3/dist-packages/nvchecker_source/vsmarketplace.py
are contained in the packages
 * nvchecker/2.5-1
 * python3-nvchecker/2.12-1

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.

Please figure out which of these packages should properly own the
affected files and reassign the bug as appropriate. When doing so,
please add the other package to the set of affected packages using
"Control: affects -1 + " to avoid the filing of duplicates.

The other package should stop installing the files. In case the files
are being moved between packages, Breaks and Replaces should be
declared. In this case, please refer to policy section 7.6 for details.
Another useful resource is https://wiki.debian.org/PackageTransition.

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: librnd4-lib-gtk has an undeclared file conflict

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + librnd4-hid-gtk4-gl
Bug #1055678 [librnd4-lib-gtk] librnd4-lib-gtk has an undeclared file conflict
Added indication that 1055678 affects librnd4-hid-gtk4-gl

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

Bug#1055678: librnd4-lib-gtk has an undeclared file conflict

[Helmut Grohne]

Package: librnd4-lib-gtk
Version: 4.1.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + librnd4-hid-gtk4-gl

librnd4-lib-gtk has an undeclared file conflict. This may result in an
unpack error from dpkg.

The files
 * /usr/lib/librnd4/plugins/lib_gtk4_common.pup
 * /usr/lib/librnd4/plugins/lib_gtk4_common.so
are contained in the packages
 * librnd4-hid-gtk4-gl/4.0.3-1 as present in trixie
 * librnd4-lib-gtk/4.1.0-2 as present in unstable

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.

Bug#1055670: fwknop-server: must Depends: apparmor-profiles-extra

[Francois Marier]

> The latest update breaks apparmor for the whole system.
> 
> /etc/apparmor.d/usr.sbin.fwknopd:
>   include 
> 
> This must declare Depends: apparmor-profiles-extra.
> 
> Otherwise the apparmor service can't parse the file and will refuse to start.

Ah, that's annoying. I don't think I'll want to make fwknop-server require
apparmor. I guess this means I need to reintroduce the fwknop-apparmor
package.

Thanks for flagging this.

Francois

-- 
https://fmarier.org/

Bug#1055672: Depends on python3-typed-ast, which has been removed from testing and unstable due to #1051802

[Daniel Leidert]

Package: prospector
Version: 1.1.7-4
Severity: serious
X-Debbugs-Cc: daniel.leid...@ext.secunet.com

The package declares a dependency on python3-typed-ast. However, due to
#1051802, this package is no longer available. It is my understanding that
python3-typed-ast has been superseeded by the "ast" standard library in Python
3.8+. Thus, prospector is currently uninstallable.

Regards, Daniel


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

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

Versions of packages prospector depends on:
ii  dodgy  0.1.9-5
ii  libjs-sphinxdoc7.2.6-2
ii  pylint 2.17.4-1
ii  python33.11.4-5+b1
ii  python3-astroid2.15.6-1
ii  python3-mccabe 0.7.0-1
ii  python3-mypy   1.6.1-1
ii  python3-pep8-naming0.10.0-2
ii  python3-pycodestyle2.10.0-1
ii  python3-pydocstyle 6.3.0-1
ii  python3-pyflakes   2.5.0-1
ii  python3-pylint-celery  0.3-7
ii  python3-pylint-django  2.0.13-3
ii  python3-pylint-flask   0.5-5
ii  python3-pylint-plugin-utils0.7-3
ii  python3-pyroma 2.6b2-1
ii  python3-requirements-detector  0.6-4
ii  python3-setoptconf 0.3.0-2
ii  python3-typed-ast  1.5.4-1+b1
ii  python3-yaml   6.0.1-1

Versions of packages prospector recommends:
ii  vulture  2.7-1

prospector suggests no packages.

-- no debconf information

Bug#1041559: marked as done (Recommends non-existent package linux-musl-dev)

[Debian Bug Tracking System]

Your message dated Thu, 09 Nov 2023 22:49:35 +
with message-id 
and subject line Bug#1041559: fixed in musl 1.2.4-1
has caused the Debian Bug report #1041559,
regarding Recommends non-existent package linux-musl-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.)


-- 
1041559: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041559
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: musl-dev
Version: 1.2.3-1
Severity: serious
X-Debbugs-Cc: j...@joshtriplett.org

musl-dev Recommends linux-musl-dev, which does not appear to exist in
the archive.

Policy 2.2.1 "The main archive area":
> package must not declare a "Pre-Depends", "Depends", "Recommends",
> "Build-Depends", "Build-Depends-Indep", or "Build-Depends-Arch"
> relationship on a non-*main* package unless that package is only
> listed as a non-default alternative for a package in *main*



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

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

Versions of packages musl-dev depends on:
ii  gcc [gcc-x86-64-linux-gnu]  4:13.1.0-4
ii  musl1.2.3-1

Versions of packages musl-dev recommends:
pn  linux-musl-dev  

musl-dev suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: musl
Source-Version: 1.2.4-1
Done: Reiner Herrmann 

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

Debian distribution maintenance software
pp.
Reiner Herrmann  (supplier of updated musl 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, 09 Nov 2023 23:26:24 +0100
Source: musl
Architecture: source
Version: 1.2.4-1
Distribution: unstable
Urgency: medium
Maintainer: Reiner Herrmann 
Changed-By: Reiner Herrmann 
Closes: 996326 1015552 1022027 1041559
Changes:
 musl (1.2.4-1) unstable; urgency=medium
 .
   [ Reiner Herrmann ]
   * New upstream release.
   * Set option to disable building with LTO, as it is not supported.
 (Closes: #1015552)
   * Stop recommending non-existing linux-musl-dev. (Closes: #1041559)
   * Apply patch from Harald Hoyer to allow linking with static-pie.
 (Closes: #996326)
   * Add autopkgtest for static-pie linking.
   * Update lintian overrides to new format.
   * Bump Standards-Version to 4.6.2.
 .
   [ Helmut Grohne ]
   * Restore crypt functionality in libc.{a,so} for ABI compatibility.
 (Closes: #1022027)
Checksums-Sha1:
 d34a577e8c5a11d8c7211ca5c2cdf76cb5567b0d 3517 musl_1.2.4-1.dsc
 78eb982244b857dbacb2ead25cc0f631ce44204d 1063758 musl_1.2.4.orig.tar.gz
 b0e6539e3bcda9312c9bc98ef8b6f8a1aa080617 490 musl_1.2.4.orig.tar.gz.asc
 b9795bfea1a1a1a57345d18af6e216ec33549dab 24148 musl_1.2.4-1.debian.tar.xz
 0cc7b8876c9569f7700d973c62575bf79dff111f 6402 musl_1.2.4-1_amd64.buildinfo
Checksums-Sha256:
 b8500010d464b3c51dd643762c93dd153f607b12646db3d08ac754974d1ac045 3517 
musl_1.2.4-1.dsc
 7a35eae33d5372a7c0da1188de798726f68825513b7ae3ebe9752114f039 1063758 
musl_1.2.4.orig.tar.gz
 4aa4f74cdabd0629d9400c04637ccc311dd120baa137c016e25dfdcb5600a4ad 490 
musl_1.2.4.orig.tar.gz.asc
 7feb5d70b212f48283858c41f19d2a2b824a36222ad4736dd09965ce4a6b0ea0 24148 
musl_1.2.4-1.debian.tar.xz
 b1dfb5d618a3195f508924e4450dfb88dccce62b953969d2fe776b8075b2e0b2 6402 
musl_1.2.4-1_amd64.buildinfo
Files:
 ffcf2bb6983248ff2451e76a79b63d52 3517 libs optional musl_1.2.4-1.dsc
 ba95cb2c0ba278f081f96380be555fce 1063758 libs optional musl_1.2.4.orig.tar.gz
 e2fcfbf5e8de162b76ce70507342546f 490 libs optional musl_1.2.4.orig.tar.gz.asc
 046f3e98a0982067f2b1855de90d2210 24148 libs optional musl_1.2.4-1.debian.tar.xz
 e8eb19eec5a2632df9cbd4a520361850 6402 libs optional 
musl_1.2.4-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

Bug#1055017: marked as done (node-html-webpack-plugin_5.5.3+~cs14.4.8-1_all-buildd.changes REJECTED)

[Debian Bug Tracking System]

Your message dated Thu, 09 Nov 2023 21:34:39 +
with message-id 
and subject line Bug#1055017: fixed in node-html-webpack-plugin 5.5.3+repack2-1
has caused the Debian Bug report #1055017,
regarding node-html-webpack-plugin_5.5.3+~cs14.4.8-1_all-buildd.changes REJECTED
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.)


-- 
1055017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055017
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-html-webpack-plugin
Version: 5.5.3+~cs14.4.8-1
Severity: serious

On 2023-10-29 04:49, Debian FTP Masters wrote:
> 
> 
> Version check failed:
> Your upload included the binary package node-html-minifier-terser, version 
> 5.5.3+~cs14.4.8-1, for all,
> however unstable already has version 7.2.0~5.5.3+~cs14.4.7-2.
> Uploads to unstable must have a higher version than present in unstable.
> 
> Mapping sid to unstable.
> 
> ===
> 
> Please feel free to respond to this email if you don't understand why
> your files were rejected, or if you upload new files which address our
> concerns.
> 
> 
> 
--- End Message ---
--- Begin Message ---
Source: node-html-webpack-plugin
Source-Version: 5.5.3+repack2-1
Done: Yadd 

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

Debian distribution maintenance software
pp.
Yadd  (supplier of updated node-html-webpack-plugin 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, 09 Nov 2023 22:37:15 +0400
Source: node-html-webpack-plugin
Built-For-Profiles: nocheck
Architecture: source
Version: 5.5.3+repack2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Yadd 
Closes: 1055017
Changes:
 node-html-webpack-plugin (5.5.3+repack2-1) unstable; urgency=medium
 .
   * Apply multi-arch hints (node-relateurl foreign)
   * Revert "Drop component html-minifier-terser"
   * Fix versions (Closes: #1055017)
Checksums-Sha1: 
 2a63f7493699ad9da8efeea17ba8ee54a59171ea 3785 
node-html-webpack-plugin_5.5.3+repack2-1.dsc
 af3bb85100ac3d0ced14fa340fad9f1800b843f8 155384 
node-html-webpack-plugin_5.5.3+repack2.orig-html-minifier-terser.tar.gz
 82b4f9b4f18fa8ee11dc18b8cb4e0db5fc9f7602 16996 
node-html-webpack-plugin_5.5.3+repack2.orig-relateurl.tar.gz
 2290fa13e6e49b6cc0ab0afa2d6cf6a66feedb48 3372 
node-html-webpack-plugin_5.5.3+repack2.orig-types-html-minifier-terser.tar.gz
 4102129b24074b47bace88e0f65d9ef87eacc4f9 798116 
node-html-webpack-plugin_5.5.3+repack2.orig.tar.gz
 2ca4cbcc099c5b90b94063c06feb96350ae677f9 5468 
node-html-webpack-plugin_5.5.3+repack2-1.debian.tar.xz
Checksums-Sha256: 
 2fc1c136b6b952105649e459ea9f5159da14cf2a5cca9881e356a21128835884 3785 
node-html-webpack-plugin_5.5.3+repack2-1.dsc
 df0b914838a8225f3905415d5717992c73f0d1f30166ca0180361001dc41c25d 155384 
node-html-webpack-plugin_5.5.3+repack2.orig-html-minifier-terser.tar.gz
 1cf4e97bc5384bf01bd78a0181c692ecb660677e94ad4df7ee756e4235eeb22b 16996 
node-html-webpack-plugin_5.5.3+repack2.orig-relateurl.tar.gz
 01fef153cd9c3b270198ff6fba2230710fb87b462423a7422e743cc8e2ee6d57 3372 
node-html-webpack-plugin_5.5.3+repack2.orig-types-html-minifier-terser.tar.gz
 8d3d3f35ddf245aaefc380c7bc1424bd7a2fffa641ed9995ef882443a467a322 798116 
node-html-webpack-plugin_5.5.3+repack2.orig.tar.gz
 4f48ce89a376dfc064ebd655e9d1f859cc82b6ca870931ddac76e1d9e75be203 5468 
node-html-webpack-plugin_5.5.3+repack2-1.debian.tar.xz
Files: 
 358163381b3bbb6eeecade0576560b8b 3785 javascript optional 
node-html-webpack-plugin_5.5.3+repack2-1.dsc
 1cd9a1769efc4611863f85c19910f7d4 155384 javascript optional 
node-html-webpack-plugin_5.5.3+repack2.orig-html-minifier-terser.tar.gz
 85703eb36d347c619745ea5fd953153b 16996 javascript optional 
node-html-webpack-plugin_5.5.3+repack2.orig-relateurl.tar.gz
 59eec7290953709be5961376abb69656 3372 javascript optional 
node-html-webpack-plugin_5.5.3+repack2.orig-types-html-minifier-terser.tar.gz
 c6a77b27fd141fb19db2e44f21ea943e 798116 javascript optional 
node-html-webpack-plugin_5.5.3+repack2.orig.tar.gz
 

Bug#1055663: marked as done (rust-syn: build-depends on missing package librust-proc-macro2-1+proc-macro-dev)

[Debian Bug Tracking System]

Your message dated Thu, 9 Nov 2023 23:28:50 +0200
with message-id 
and subject line rust-proc-macro2 1.0.69-1 is now in unstable
has caused the Debian Bug report #1055663,
regarding rust-syn: build-depends on missing package 
librust-proc-macro2-1+proc-macro-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.)


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

build-depends on missing package librust-proc-macro2-1+proc-macro-dev

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmVNJhkACgkQLHwxRsGg
ASGrug//d6DvX2AJD28nncKM56m2ISY7zzz31HNvzmbfuAXJ3fMZ24zGCXJKjaiQ
68w3C1Te3cczJvlzuD37G7aG3ZSYSVfv5BH1MYoHnuxRC19DWJfglbB5Z/sIx1He
QO9G0FuFNyrzmEsB04zDSevK56Fx30nMb81jpCpgEp0fNjjn1Wt6R6Njfg9ab9q0
WMk4AlTGvkjCMTRKqlGhKGAJaspN1ZazQi+BdN/CSWkj/m2vfVyUtmxoJUYyQ5EJ
dxL0kzScXySnXgzq1D90qPSMYP6FDhj66BBAp0q0FWJRIsz73gclLQreLQQveH/c
5NMdBzPs7zs9Z9DEzw+n1C7TVvRhsD+z601XyJdBUdwZxL0aespQz8AYYWigwoYw
gv6dqmZ1mOPw18ZRRKhDq1f6bkxneeAJS0waaM4tTN0F7VF+WYzUF4IfMp3tz0q+
xBDrqwk70GfHgvFW4xf/VSkSiRSZpLK4gBo/hSbrts2yT14OC3YrtP+gaCB7pTmI
RMZ1hY9C4JYvkSTy7N7miD3h8UGiZieLaoliHSBj75dVah9EoTbJ8reXJmMuydRb
tBr90dJOiKP9soyfpS7m1Amcjm5+kQuGr9o9btrz2Q7jRvt5rpmmHY0t9IMWj+3m
z87dnWb697h1h4GT7oZQldnraZEU459+tgAP31NXM4Sjmh82kQ8=
=SlJm
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
https://tracker.debian.org/pkg/rust-proc-macro2
https://buildd.debian.org/status/package.php?p=rust-syn=sid

cu
Adrian--- End Message ---

Bug#1055120: marked as done (rust-chrono breaks rust-pyo3 autopkgtest: panicked at 'called `Option::unwrap()` on a `None` value')

[Debian Bug Tracking System]

Your message dated Thu, 09 Nov 2023 21:04:32 +
with message-id 
and subject line Bug#1055120: fixed in rust-pyo3 0.19.2-1
has caused the Debian Bug report #1055120,
regarding rust-chrono breaks rust-pyo3 autopkgtest: panicked at 'called 
`Option::unwrap()` on a `None` value'
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.)


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

Source: rust-chrono, rust-pyo3
Control: found -1 rust-chrono/0.4.31-1
Control: found -1 rust-pyo3/0.19.0-3
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainer(s),

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


   passfail
rust-chronofrom testing0.4.31-1
rust-pyo3  from testing0.19.0-3
all others from testingfrom testing

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

Currently this regression is blocking the migration of rust-chrono to 
testing [1]. Due to the nature of this issue, I filed this bug report 
against both packages. Can you please investigate the situation and 
reassign the bug to the right package?


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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/armel/r/rust-pyo3/39387157/log.gz

1099s failures:
1099s
1099s  conversions::chrono::tests::test_pyo3_datetime_topyobject 
stdout 
1099s thread 'conversions::chrono::tests::test_pyo3_datetime_topyobject' 
panicked at 'called `Option::unwrap()` on a `None` value', 
src/conversions/chrono.rs:574:26

1099s stack backtrace:
1099s0: rust_begin_unwind
1099s  at 
/usr/src/rustc-1.70.0/library/std/src/panicking.rs:578:5

1099s1: core::panicking::panic_fmt
1099s  at 
/usr/src/rustc-1.70.0/library/core/src/panicking.rs:67:14

1099s2: core::panicking::panic
1099s  at 
/usr/src/rustc-1.70.0/library/core/src/panicking.rs:117:5

1099s3: core::option::Option::unwrap
1099s  at 
/usr/src/rustc-1.70.0/library/core/src/option.rs:950:21
1099s4: 
pyo3::conversions::chrono::tests::test_pyo3_datetime_topyobject::{{closure}}::{{closure}}

1099s  at ./src/conversions/chrono.rs:571:36
1099s5: pyo3::marker::Python::with_gil
1099s  at ./src/marker.rs:433:9
1099s6: 
pyo3::conversions::chrono::tests::test_pyo3_datetime_topyobject::{{closure}}

1099s  at ./src/conversions/chrono.rs:570:17
1099s7: pyo3::conversions::chrono::tests::test_pyo3_datetime_topyobject
1099s  at ./src/conversions/chrono.rs:603:9
1099s8: 
pyo3::conversions::chrono::tests::test_pyo3_datetime_topyobject::{{closure}}

1099s  at ./src/conversions/chrono.rs:567:40
1099s9: core::ops::function::FnOnce::call_once
1099s  at 
/usr/src/rustc-1.70.0/library/core/src/ops/function.rs:250:5

1099s   10: core::ops::function::FnOnce::call_once
1099s  at 
/usr/src/rustc-1.70.0/library/core/src/ops/function.rs:250:5
1099s note: Some details are omitted, run with `RUST_BACKTRACE=full` for 
a verbose backtrace.

1099s
1099s  conversions::chrono::tests::test_pyo3_time_topyobject stdout 
1099s thread 'conversions::chrono::tests::test_pyo3_time_topyobject' 
panicked at 'called `Option::unwrap()` on a `None` value', 
src/conversions/chrono.rs:798:22

1099s stack backtrace:
1099s0: rust_begin_unwind
1099s  at 
/usr/src/rustc-1.70.0/library/std/src/panicking.rs:578:5

1099s1: core::panicking::panic_fmt
1099s  at 
/usr/src/rustc-1.70.0/library/core/src/panicking.rs:67:14

1099s2: core::panicking::panic
1099s  at 
/usr/src/rustc-1.70.0/library/core/src/panicking.rs:117:5

1099s3: core::option::Option::unwrap
1099s  at 
/usr/src/rustc-1.70.0/library/core/src/option.rs:950:21
1099s4: 
pyo3::conversions::chrono::tests::test_pyo3_time_topyobject::{{closure}}::{{closure}}

1099s  at ./src/conversions/chrono.rs:797:28
1099s5: pyo3::marker::Python::with_gil
1099s  at ./src/marker.rs:433:9
1099s6: 

Bug#1055670: fwknop-server: must Depends: apparmor-profiles-extra

[Ximin Luo]

Package: fwknop-server
Version: 2.6.10-18
Severity: serious
Tags: patch security
Justification: Policy 7.2
X-Debbugs-Cc: Debian Security Team 

Dear Maintainer,

The latest update breaks apparmor for the whole system.

/etc/apparmor.d/usr.sbin.fwknopd:
  include 

This must declare Depends: apparmor-profiles-extra.

Otherwise the apparmor service can't parse the file and will refuse to start.

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 
'testing-debug'), (500, 'stable-security'), (300, 'unstable'), (100, 
'experimental'), (1, 'experimental-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages fwknop-server depends on:
ii  init-system-helpers  1.65.2
ii  iptables 1.8.9-2
ii  libc62.37-12
ii  libfko3  2.6.10-18
ii  libpcap0.8   1.10.4-4

fwknop-server recommends no packages.

fwknop-server suggests no packages.

-- Configuration Files:
/etc/fwknop/access.conf [Errno 13] Permission denied: '/etc/fwknop/access.conf'
/etc/fwknop/fwknopd.conf [Errno 13] Permission denied: 
'/etc/fwknop/fwknopd.conf'

-- no debconf information

Bug#1055251: marked as done (squid: CVE-2023-46848: SQUID-2023:5 Denial of Service in FTP)

[Debian Bug Tracking System]

Your message dated Thu, 09 Nov 2023 20:50:01 +
with message-id 
and subject line Bug#1055251: fixed in squid 6.5-1
has caused the Debian Bug report #1055251,
regarding squid: CVE-2023-46848: SQUID-2023:5 Denial of Service in FTP
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.)


-- 
1055251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055251
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: squid
Version: 6.3-1
Severity: grave
Tags: security patch
X-Debbugs-Cc: Debian Security Team 

Hi,

https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2023-2725 
links to a bunch of squid advisories, three of which have CVSS scores of 9+:

https://github.com/squid-cache/squid/security/advisories/GHSA-2g3c-pg7q-g59w
https://github.com/squid-cache/squid/security/advisories/GHSA-phqj-m8gv-cq4g
https://github.com/squid-cache/squid/security/advisories/GHSA-543m-w2m2-g255
https://github.com/squid-cache/squid/security/advisories/GHSA-j83v-w3p4-5cqh

Squid 6.4 includes the fix; patches for 6.3 are provided, but don't apply 
cleanly to the Debian sources.

Please package a non-vulnerable version ASAP.

Thanks!

András

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

Init: runit (via /run/runit.stopit)
LSM: AppArmor: enabled

-- 
   Computers are not intelligent. They only think they are.
--- End Message ---
--- Begin Message ---
Source: squid
Source-Version: 6.5-1
Done: Luigi Gangitano 

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

Debian distribution maintenance software
pp.
Luigi Gangitano  (supplier of updated squid 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,  9 Nov 2023 15:04:20 +0100
Source: squid
Architecture: source
Version: 6.5-1
Distribution: unstable
Urgency: high
Maintainer: Luigi Gangitano 
Changed-By: Luigi Gangitano 
Closes: 1053557 1054537 1055249 1055250 1055251 1055252
Changes:
 squid (6.5-1) unstable; urgency=high
 .
   [ Amos Jeffries  ]
   * New Upstream Release 6.5
 Fixes: CVE-2023-46846. SQUID-2023:1 (Closes: #1054537)
 Fixes: CVE-2023-5842. SQUID-2023:2 (Closes: #1055249)
 Fixes: CVE-2023-46847. SQUID-2023:3 (Closes: #1055250)
 Fixes: CVE-2023-46724. SQUID-2023:4 (Closes: #1055252)
 Fixes: CVE-2023-46848. SQUID-2023:5 (Closes: #1055251)
 Fixes: CVE-2019-18860. SQUID-2023:6 Cross Site Scripting in cachemgr.cgi
 Fixes: SQUID-2023:7 Denial of Service in HTTP Message processing
 Fixes: SQUID-2023:8 Denial of Service in Helper Process management
 .
   * Update debian/tests/upstream-test-suite for new version (Closes: #1053557)
Checksums-Sha1:
 4a97d86ab0b788cbb5990cb2e914f34730efa5a9 2919 squid_6.5-1.dsc
 07a08394625948750264778c82e19cf24ea7cb1f 2554492 squid_6.5.orig.tar.xz
 f63fc50c12097db110213552d011d65927e20fa7 1193 squid_6.5.orig.tar.xz.asc
 c18184780487665894ec328aa85b9f3dade47f4d 43144 squid_6.5-1.debian.tar.xz
 60b101da9a8cbcf7e531d4afecbef9856417542c 9610 squid_6.5-1_arm64.buildinfo
Checksums-Sha256:
 ca5c65c1bb115c267bfdbb00bb603cd40a302ef6da18fbbd2936336f55210929 2919 
squid_6.5-1.dsc
 5070f8a3ae870c8fc716326befb0a1abe8b5ff3a6f3932cbc5543d7c8549 2554492 
squid_6.5.orig.tar.xz
 a6b2da4f95c3d968a17dc567273835b2300fff0acd71d339f6eb52e0da3d6b17 1193 
squid_6.5.orig.tar.xz.asc
 14fd7a36867894b38e033b4d7a58eed8acef082c0deaf63588193795be1b2054 43144 
squid_6.5-1.debian.tar.xz
 3846de794f967e1c67b09579e2940185d8ec4eff5d256b789be5a63e5046e835 9610 
squid_6.5-1_arm64.buildinfo
Files:
 53e46cfc36079fd503ccd1036b5dcae2 2919 web optional squid_6.5-1.dsc
 da2797d899cf538fab7f504fdf3c18bf 2554492 web optional squid_6.5.orig.tar.xz
 ed2de0539e6859f67d5388b6fff63f1a 1193 web optional squid_6.5.orig.tar.xz.asc
 bcd628808bce9a0e2c512fcaa2f489af 43144 web optional squid_6.5-1.debian.tar.xz
 f0d89f6ac2aae51c6c76616798e08582 9610 web optional squid_6.5-1_arm64.buildinfo

-BEGIN PGP SIGNATURE-

Bug#1055252: marked as done (squid: CVE-2023-46724: SQUID-2023:4 Denial of Service in SSL Certificate validation)

[Debian Bug Tracking System]

Your message dated Thu, 09 Nov 2023 20:50:01 +
with message-id 
and subject line Bug#1055252: fixed in squid 6.5-1
has caused the Debian Bug report #1055252,
regarding squid: CVE-2023-46724: SQUID-2023:4 Denial of Service in SSL 
Certificate validation
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.)


-- 
1055252: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055252
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: squid
Version: 6.3-1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for squid.

CVE-2023-46724[0]:
| Squid is a caching proxy for the Web. Due to an Improper Validation
| of Specified Index bug, Squid versions 3.3.0.1 through 5.9 and 6.0
| prior to 6.4 compiled using `--with-openssl` are vulnerable to a
| Denial of Service attack against SSL Certificate validation. This
| problem allows a remote server to perform Denial of Service against
| Squid Proxy by initiating a TLS Handshake with a specially crafted
| SSL Certificate in a server certificate chain. This attack is
| limited to HTTPS and SSL-Bump. This bug is fixed in Squid version
| 6.4. In addition, patches addressing this problem for the stable
| releases can be found in Squid's patch archives. Those who you use a
| prepackaged version of Squid should refer to the package vendor for
| availability information on updated packages.


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-2023-46724
https://www.cve.org/CVERecord?id=CVE-2023-46724
[1] 
https://github.com/squid-cache/squid/commit/792ef23e6e1c05780fe17f733859eef6eb8c8be3
[2] https://megamansec.github.io/Squid-Security-Audit/ssl-bufferunderread.html
[3] https://github.com/squid-cache/squid/security/advisories/GHSA-73m6-jm96-c6r3

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: squid
Source-Version: 6.5-1
Done: Luigi Gangitano 

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

Debian distribution maintenance software
pp.
Luigi Gangitano  (supplier of updated squid 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,  9 Nov 2023 15:04:20 +0100
Source: squid
Architecture: source
Version: 6.5-1
Distribution: unstable
Urgency: high
Maintainer: Luigi Gangitano 
Changed-By: Luigi Gangitano 
Closes: 1053557 1054537 1055249 1055250 1055251 1055252
Changes:
 squid (6.5-1) unstable; urgency=high
 .
   [ Amos Jeffries  ]
   * New Upstream Release 6.5
 Fixes: CVE-2023-46846. SQUID-2023:1 (Closes: #1054537)
 Fixes: CVE-2023-5842. SQUID-2023:2 (Closes: #1055249)
 Fixes: CVE-2023-46847. SQUID-2023:3 (Closes: #1055250)
 Fixes: CVE-2023-46724. SQUID-2023:4 (Closes: #1055252)
 Fixes: CVE-2023-46848. SQUID-2023:5 (Closes: #1055251)
 Fixes: CVE-2019-18860. SQUID-2023:6 Cross Site Scripting in cachemgr.cgi
 Fixes: SQUID-2023:7 Denial of Service in HTTP Message processing
 Fixes: SQUID-2023:8 Denial of Service in Helper Process management
 .
   * Update debian/tests/upstream-test-suite for new version (Closes: #1053557)
Checksums-Sha1:
 4a97d86ab0b788cbb5990cb2e914f34730efa5a9 2919 squid_6.5-1.dsc
 07a08394625948750264778c82e19cf24ea7cb1f 2554492 squid_6.5.orig.tar.xz
 f63fc50c12097db110213552d011d65927e20fa7 1193 squid_6.5.orig.tar.xz.asc
 c18184780487665894ec328aa85b9f3dade47f4d 43144 squid_6.5-1.debian.tar.xz
 60b101da9a8cbcf7e531d4afecbef9856417542c 9610 squid_6.5-1_arm64.buildinfo
Checksums-Sha256:
 ca5c65c1bb115c267bfdbb00bb603cd40a302ef6da18fbbd2936336f55210929 2919 
squid_6.5-1.dsc
 5070f8a3ae870c8fc716326befb0a1abe8b5ff3a6f3932cbc5543d7c8549 2554492 
squid_6.5.orig.tar.xz
 a6b2da4f95c3d968a17dc567273835b2300fff0acd71d339f6eb52e0da3d6b17 1193 
squid_6.5.orig.tar.xz.asc
 

Bug#1055250: marked as done (squid: CVE-2023-46847: SQUID-2023:3 Denial of Service in HTTP Digest Authentication)

[Debian Bug Tracking System]

Your message dated Thu, 09 Nov 2023 20:50:01 +
with message-id 
and subject line Bug#1055250: fixed in squid 6.5-1
has caused the Debian Bug report #1055250,
regarding squid: CVE-2023-46847: SQUID-2023:3 Denial of Service in HTTP Digest 
Authentication
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.)


-- 
1055250: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055250
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: squid
Version: 6.3-1
Severity: grave
Tags: security patch
X-Debbugs-Cc: Debian Security Team 

Hi,

https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2023-2725 
links to a bunch of squid advisories, three of which have CVSS scores of 9+:

https://github.com/squid-cache/squid/security/advisories/GHSA-2g3c-pg7q-g59w
https://github.com/squid-cache/squid/security/advisories/GHSA-phqj-m8gv-cq4g
https://github.com/squid-cache/squid/security/advisories/GHSA-543m-w2m2-g255
https://github.com/squid-cache/squid/security/advisories/GHSA-j83v-w3p4-5cqh

Squid 6.4 includes the fix; patches for 6.3 are provided, but don't apply 
cleanly to the Debian sources.

Please package a non-vulnerable version ASAP.

Thanks!

András

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

Init: runit (via /run/runit.stopit)
LSM: AppArmor: enabled

-- 
   Computers are not intelligent. They only think they are.
--- End Message ---
--- Begin Message ---
Source: squid
Source-Version: 6.5-1
Done: Luigi Gangitano 

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

Debian distribution maintenance software
pp.
Luigi Gangitano  (supplier of updated squid 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,  9 Nov 2023 15:04:20 +0100
Source: squid
Architecture: source
Version: 6.5-1
Distribution: unstable
Urgency: high
Maintainer: Luigi Gangitano 
Changed-By: Luigi Gangitano 
Closes: 1053557 1054537 1055249 1055250 1055251 1055252
Changes:
 squid (6.5-1) unstable; urgency=high
 .
   [ Amos Jeffries  ]
   * New Upstream Release 6.5
 Fixes: CVE-2023-46846. SQUID-2023:1 (Closes: #1054537)
 Fixes: CVE-2023-5842. SQUID-2023:2 (Closes: #1055249)
 Fixes: CVE-2023-46847. SQUID-2023:3 (Closes: #1055250)
 Fixes: CVE-2023-46724. SQUID-2023:4 (Closes: #1055252)
 Fixes: CVE-2023-46848. SQUID-2023:5 (Closes: #1055251)
 Fixes: CVE-2019-18860. SQUID-2023:6 Cross Site Scripting in cachemgr.cgi
 Fixes: SQUID-2023:7 Denial of Service in HTTP Message processing
 Fixes: SQUID-2023:8 Denial of Service in Helper Process management
 .
   * Update debian/tests/upstream-test-suite for new version (Closes: #1053557)
Checksums-Sha1:
 4a97d86ab0b788cbb5990cb2e914f34730efa5a9 2919 squid_6.5-1.dsc
 07a08394625948750264778c82e19cf24ea7cb1f 2554492 squid_6.5.orig.tar.xz
 f63fc50c12097db110213552d011d65927e20fa7 1193 squid_6.5.orig.tar.xz.asc
 c18184780487665894ec328aa85b9f3dade47f4d 43144 squid_6.5-1.debian.tar.xz
 60b101da9a8cbcf7e531d4afecbef9856417542c 9610 squid_6.5-1_arm64.buildinfo
Checksums-Sha256:
 ca5c65c1bb115c267bfdbb00bb603cd40a302ef6da18fbbd2936336f55210929 2919 
squid_6.5-1.dsc
 5070f8a3ae870c8fc716326befb0a1abe8b5ff3a6f3932cbc5543d7c8549 2554492 
squid_6.5.orig.tar.xz
 a6b2da4f95c3d968a17dc567273835b2300fff0acd71d339f6eb52e0da3d6b17 1193 
squid_6.5.orig.tar.xz.asc
 14fd7a36867894b38e033b4d7a58eed8acef082c0deaf63588193795be1b2054 43144 
squid_6.5-1.debian.tar.xz
 3846de794f967e1c67b09579e2940185d8ec4eff5d256b789be5a63e5046e835 9610 
squid_6.5-1_arm64.buildinfo
Files:
 53e46cfc36079fd503ccd1036b5dcae2 2919 web optional squid_6.5-1.dsc
 da2797d899cf538fab7f504fdf3c18bf 2554492 web optional squid_6.5.orig.tar.xz
 ed2de0539e6859f67d5388b6fff63f1a 1193 web optional squid_6.5.orig.tar.xz.asc
 bcd628808bce9a0e2c512fcaa2f489af 43144 web optional squid_6.5-1.debian.tar.xz
 f0d89f6ac2aae51c6c76616798e08582 9610 web optional squid_6.5-1_arm64.buildinfo

-BEGIN 

Bug#1055249: marked as done (squid: CVE-2023-5824: SQUID-2023:2 Multiple issues in HTTP response caching)

[Debian Bug Tracking System]

Your message dated Thu, 09 Nov 2023 20:50:01 +
with message-id 
and subject line Bug#1055249: fixed in squid 6.5-1
has caused the Debian Bug report #1055249,
regarding squid: CVE-2023-5824: SQUID-2023:2 Multiple issues in HTTP response 
caching
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.)


-- 
1055249: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055249
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: squid
Version: 6.3-1
Severity: grave
Tags: security patch
X-Debbugs-Cc: Debian Security Team 

Hi,

https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2023-2725 
links to a bunch of squid advisories, three of which have CVSS scores of 9+:

https://github.com/squid-cache/squid/security/advisories/GHSA-2g3c-pg7q-g59w
https://github.com/squid-cache/squid/security/advisories/GHSA-phqj-m8gv-cq4g
https://github.com/squid-cache/squid/security/advisories/GHSA-543m-w2m2-g255
https://github.com/squid-cache/squid/security/advisories/GHSA-j83v-w3p4-5cqh

Squid 6.4 includes the fix; patches for 6.3 are provided, but don't apply 
cleanly to the Debian sources.

Please package a non-vulnerable version ASAP.

Thanks!

András

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

Init: runit (via /run/runit.stopit)
LSM: AppArmor: enabled

-- 
   Computers are not intelligent. They only think they are.
--- End Message ---
--- Begin Message ---
Source: squid
Source-Version: 6.5-1
Done: Luigi Gangitano 

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

Debian distribution maintenance software
pp.
Luigi Gangitano  (supplier of updated squid 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,  9 Nov 2023 15:04:20 +0100
Source: squid
Architecture: source
Version: 6.5-1
Distribution: unstable
Urgency: high
Maintainer: Luigi Gangitano 
Changed-By: Luigi Gangitano 
Closes: 1053557 1054537 1055249 1055250 1055251 1055252
Changes:
 squid (6.5-1) unstable; urgency=high
 .
   [ Amos Jeffries  ]
   * New Upstream Release 6.5
 Fixes: CVE-2023-46846. SQUID-2023:1 (Closes: #1054537)
 Fixes: CVE-2023-5842. SQUID-2023:2 (Closes: #1055249)
 Fixes: CVE-2023-46847. SQUID-2023:3 (Closes: #1055250)
 Fixes: CVE-2023-46724. SQUID-2023:4 (Closes: #1055252)
 Fixes: CVE-2023-46848. SQUID-2023:5 (Closes: #1055251)
 Fixes: CVE-2019-18860. SQUID-2023:6 Cross Site Scripting in cachemgr.cgi
 Fixes: SQUID-2023:7 Denial of Service in HTTP Message processing
 Fixes: SQUID-2023:8 Denial of Service in Helper Process management
 .
   * Update debian/tests/upstream-test-suite for new version (Closes: #1053557)
Checksums-Sha1:
 4a97d86ab0b788cbb5990cb2e914f34730efa5a9 2919 squid_6.5-1.dsc
 07a08394625948750264778c82e19cf24ea7cb1f 2554492 squid_6.5.orig.tar.xz
 f63fc50c12097db110213552d011d65927e20fa7 1193 squid_6.5.orig.tar.xz.asc
 c18184780487665894ec328aa85b9f3dade47f4d 43144 squid_6.5-1.debian.tar.xz
 60b101da9a8cbcf7e531d4afecbef9856417542c 9610 squid_6.5-1_arm64.buildinfo
Checksums-Sha256:
 ca5c65c1bb115c267bfdbb00bb603cd40a302ef6da18fbbd2936336f55210929 2919 
squid_6.5-1.dsc
 5070f8a3ae870c8fc716326befb0a1abe8b5ff3a6f3932cbc5543d7c8549 2554492 
squid_6.5.orig.tar.xz
 a6b2da4f95c3d968a17dc567273835b2300fff0acd71d339f6eb52e0da3d6b17 1193 
squid_6.5.orig.tar.xz.asc
 14fd7a36867894b38e033b4d7a58eed8acef082c0deaf63588193795be1b2054 43144 
squid_6.5-1.debian.tar.xz
 3846de794f967e1c67b09579e2940185d8ec4eff5d256b789be5a63e5046e835 9610 
squid_6.5-1_arm64.buildinfo
Files:
 53e46cfc36079fd503ccd1036b5dcae2 2919 web optional squid_6.5-1.dsc
 da2797d899cf538fab7f504fdf3c18bf 2554492 web optional squid_6.5.orig.tar.xz
 ed2de0539e6859f67d5388b6fff63f1a 1193 web optional squid_6.5.orig.tar.xz.asc
 bcd628808bce9a0e2c512fcaa2f489af 43144 web optional squid_6.5-1.debian.tar.xz
 f0d89f6ac2aae51c6c76616798e08582 9610 web optional squid_6.5-1_arm64.buildinfo

-BEGIN PGP 

Bug#1054537: marked as done (squid: CVE-2023-46846: SQUID-2023:1 Request/Response smuggling in HTTP/1.1 and ICAP)

[Debian Bug Tracking System]

Your message dated Thu, 09 Nov 2023 20:50:01 +
with message-id 
and subject line Bug#1054537: fixed in squid 6.5-1
has caused the Debian Bug report #1054537,
regarding squid: CVE-2023-46846: SQUID-2023:1 Request/Response smuggling in 
HTTP/1.1 and ICAP
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.)


-- 
1054537: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054537
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: squid
Version: 6.3-1
Severity: grave
Tags: security patch
X-Debbugs-Cc: Debian Security Team 

Hi,

https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2023-2725 
links to a bunch of squid advisories, three of which have CVSS scores of 9+:

https://github.com/squid-cache/squid/security/advisories/GHSA-2g3c-pg7q-g59w
https://github.com/squid-cache/squid/security/advisories/GHSA-phqj-m8gv-cq4g
https://github.com/squid-cache/squid/security/advisories/GHSA-543m-w2m2-g255
https://github.com/squid-cache/squid/security/advisories/GHSA-j83v-w3p4-5cqh

Squid 6.4 includes the fix; patches for 6.3 are provided, but don't apply 
cleanly to the Debian sources.

Please package a non-vulnerable version ASAP.

Thanks!

András

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

Init: runit (via /run/runit.stopit)
LSM: AppArmor: enabled

-- 
   Computers are not intelligent. They only think they are.
--- End Message ---
--- Begin Message ---
Source: squid
Source-Version: 6.5-1
Done: Luigi Gangitano 

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

Debian distribution maintenance software
pp.
Luigi Gangitano  (supplier of updated squid 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,  9 Nov 2023 15:04:20 +0100
Source: squid
Architecture: source
Version: 6.5-1
Distribution: unstable
Urgency: high
Maintainer: Luigi Gangitano 
Changed-By: Luigi Gangitano 
Closes: 1053557 1054537 1055249 1055250 1055251 1055252
Changes:
 squid (6.5-1) unstable; urgency=high
 .
   [ Amos Jeffries  ]
   * New Upstream Release 6.5
 Fixes: CVE-2023-46846. SQUID-2023:1 (Closes: #1054537)
 Fixes: CVE-2023-5842. SQUID-2023:2 (Closes: #1055249)
 Fixes: CVE-2023-46847. SQUID-2023:3 (Closes: #1055250)
 Fixes: CVE-2023-46724. SQUID-2023:4 (Closes: #1055252)
 Fixes: CVE-2023-46848. SQUID-2023:5 (Closes: #1055251)
 Fixes: CVE-2019-18860. SQUID-2023:6 Cross Site Scripting in cachemgr.cgi
 Fixes: SQUID-2023:7 Denial of Service in HTTP Message processing
 Fixes: SQUID-2023:8 Denial of Service in Helper Process management
 .
   * Update debian/tests/upstream-test-suite for new version (Closes: #1053557)
Checksums-Sha1:
 4a97d86ab0b788cbb5990cb2e914f34730efa5a9 2919 squid_6.5-1.dsc
 07a08394625948750264778c82e19cf24ea7cb1f 2554492 squid_6.5.orig.tar.xz
 f63fc50c12097db110213552d011d65927e20fa7 1193 squid_6.5.orig.tar.xz.asc
 c18184780487665894ec328aa85b9f3dade47f4d 43144 squid_6.5-1.debian.tar.xz
 60b101da9a8cbcf7e531d4afecbef9856417542c 9610 squid_6.5-1_arm64.buildinfo
Checksums-Sha256:
 ca5c65c1bb115c267bfdbb00bb603cd40a302ef6da18fbbd2936336f55210929 2919 
squid_6.5-1.dsc
 5070f8a3ae870c8fc716326befb0a1abe8b5ff3a6f3932cbc5543d7c8549 2554492 
squid_6.5.orig.tar.xz
 a6b2da4f95c3d968a17dc567273835b2300fff0acd71d339f6eb52e0da3d6b17 1193 
squid_6.5.orig.tar.xz.asc
 14fd7a36867894b38e033b4d7a58eed8acef082c0deaf63588193795be1b2054 43144 
squid_6.5-1.debian.tar.xz
 3846de794f967e1c67b09579e2940185d8ec4eff5d256b789be5a63e5046e835 9610 
squid_6.5-1_arm64.buildinfo
Files:
 53e46cfc36079fd503ccd1036b5dcae2 2919 web optional squid_6.5-1.dsc
 da2797d899cf538fab7f504fdf3c18bf 2554492 web optional squid_6.5.orig.tar.xz
 ed2de0539e6859f67d5388b6fff63f1a 1193 web optional squid_6.5.orig.tar.xz.asc
 bcd628808bce9a0e2c512fcaa2f489af 43144 web optional squid_6.5-1.debian.tar.xz
 f0d89f6ac2aae51c6c76616798e08582 9610 web optional squid_6.5-1_arm64.buildinfo

-BEGIN 

Bug#1042641: marked as done (bottleneck: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx')

[Debian Bug Tracking System]

Your message dated Thu, 09 Nov 2023 20:34:00 +
with message-id 
and subject line Bug#1042641: fixed in bottleneck 1.3.5+ds1-3
has caused the Debian Bug report #1042641,
regarding bottleneck: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid 
command 'build_sphinx'
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.)


-- 
1042641: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042641
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bottleneck
Version: 1.3.5+ds1-2
Severity: important
Tags: ftbfs
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx7.1

Hi,

bottleneck fails to build with Sphinx 7.1 and docutils 0.20, both of which
are currently available in experimental.

Relevant part (hopefully):
> x86_64-linux-gnu-gcc -shared -Wl,-O1 -Wl,-Bsymbolic-functions -g -fwrapv -O2 
> -Wl,-z,relro -Wl,-z,now -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 
> build/temp.linux-x86_64-cpython-311/bottleneck/src/nonreduce_axis.o 
> -L/usr/lib/x86_64-linux-gnu -o 
> build/lib.linux-x86_64-cpython-311/bottleneck/nonreduce_axis.cpython-311-x86_64-linux-gnu.so
> copying 
> build/lib.linux-x86_64-cpython-311/bottleneck/reduce.cpython-311-x86_64-linux-gnu.so
>  -> bottleneck
> copying 
> build/lib.linux-x86_64-cpython-311/bottleneck/move.cpython-311-x86_64-linux-gnu.so
>  -> bottleneck
> copying 
> build/lib.linux-x86_64-cpython-311/bottleneck/nonreduce.cpython-311-x86_64-linux-gnu.so
>  -> bottleneck
> copying 
> build/lib.linux-x86_64-cpython-311/bottleneck/nonreduce_axis.cpython-311-x86_64-linux-gnu.so
>  -> bottleneck
> PYTHONPATH=. python3 setup.py build_sphinx
> /usr/lib/python3/dist-packages/setuptools/__init__.py:84: 
> _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are 
> deprecated.
> !!
> 
> 
> 
> Requirements should be satisfied by a PEP 517 installer.
> If you are using pip, you can try `pip install --use-pep517`.
> 
> 
> 
> !!
>   dist.fetch_build_eggs(dist.setup_requires)
> WARNING: The wheel package is not available.
> usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
>or: setup.py --help [cmd1 cmd2 ...]
>or: setup.py --help-commands
>or: setup.py cmd --help
> 
> error: invalid command 'build_sphinx'
> make[1]: *** [debian/rules:24: override_dh_auto_build-indep] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/07/30/exp/bottleneck_1.3.5+ds1-2_unstable_sphinx-exp.log

Please see [1] for Sphinx changelog and [2] for Docutils changelog.

Also see [3] for the list of deprecated/removed APIs in Sphinx and possible
alternatives to them.

Some notable changes in Sphinx 6 and Sphinx 7:

- Sphinx no longer includes jquery.js and underscore.js by default.
  Please use python3-sphinxcontrib.jquery package if you are using a custom
  template and it still needs jquery.

- The setup.py build_sphinx command was removed. Please instead call
  sphinx-build or "python3 -m sphinx" directly.

- For packages using the extlinks extension, the caption should contain
  exactly one "%s" placeholder (if caption is not None).

In case you have questions, please Cc sph...@packages.debian.org on reply.

[1]: https://www.sphinx-doc.org/en/master/changes.html
[2]: 
https://repo.or.cz/docutils.git/blob/refs/tags/docutils-0.20.1:/RELEASE-NOTES.txt
[3]: 
https://www.sphinx-doc.org/en/master/extdev/deprecated.html#dev-deprecated-apis

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

If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
--- End Message ---
--- Begin Message ---
Source: bottleneck
Source-Version: 1.3.5+ds1-3
Done: Nilesh Patra 

We believe that the bug you reported is fixed in the latest version of
bottleneck, 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 1042...@bugs.debian.org,
and the maintainer will 

Processed: bcftools: test_vcf_merge failures on armhf: Bus error

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/samtools/bcftools/issues/2036
Bug #1055669 [src:bcftools] bcftools: test_vcf_merge failures on armhf: Bus 
error
Set Bug forwarded-to-address to 
'https://github.com/samtools/bcftools/issues/2036'.

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

Bug#1055669: bcftools: test_vcf_merge failures on armhf: Bus error

[Étienne Mollier]

Source: bcftools
Version: 1.18-1
Severity: serious
Tags: ftbfs
Justification: ftbfs
Control: forwarded -1 https://github.com/samtools/bcftools/issues/2036

Dear Maintainer,

bcftools currently ftbfs on armhf due to multiple test_vcf_merge
failures with Bus error[1].  I already informed upstream[2].
This bug is mostly to keep track of the issue on Debian side and
eventually comment on possible Debian specific workarounds.

For the context, there are 44 failure looking typically like:

test_vcf_merge:
/<>/bcftools merge --no-version -Ob 
--force-samples -0 /tmp/YVqRgiAYOP/merge.a.vcf.gz 
/tmp/YVqRgiAYOP/merge.b.vcf.gz /tmp/YVqRgiAYOP/merge.c.vcf.gz | 
/<>/bcftools view --no-version | grep -v ^##bcftools_

Non-zero status 1

Failed to read from standard input: unknown file type


.. failed ...

[1]: 
https://buildd.debian.org/status/fetch.php?pkg=bcftools=armhf=1.18-1=1699434189=1
[2]: https://github.com/samtools/bcftools/issues/2036

For information,
-- 
  .''`.  Étienne Mollier 
 : :' :  gpg: 8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
 `. `'   sent from /dev/pts/2, please excuse my verbosity
   `-on air: Silent Voices - Humancradlegrave


signature.asc
Description: PGP signature

Processed: Bug#1042641 marked as pending in bottleneck

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1042641 [src:bottleneck] bottleneck: FTBFS with Sphinx 7.1, docutils 0.20: 
error: invalid command 'build_sphinx'
Added tag(s) pending.

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

Bug#1042641: marked as pending in bottleneck

[Nilesh Patra]

Control: tag -1 pending

Hello,

Bug #1042641 in bottleneck 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/bottleneck/-/commit/ce43df034fc8c2262bc74254ac75b4efab113ecd


Use sphinx-build command instead of build_sphinx directive with setup.py 
(Closes: #1042641)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1042641

Bug#1043130: marked as done (r-cran-mlmrev: i386 autopkgtest regression with rmatrix 1.6-0-1)

[Debian Bug Tracking System]

Your message dated Thu, 9 Nov 2023 19:57:20 +0100
with message-id 
and subject line Re: Bug#1041738: src:lme4: fails to migrate to testing for too 
long: causes timeout in autopkgtests on i386
has caused the Debian Bug report #1043130,
regarding r-cran-mlmrev: i386 autopkgtest regression with rmatrix 1.6-0-1
to be marked as done.

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

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


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

Source: lme4
Version: 1.1-31-1
Severity: serious
Control: close -1 1.1-34-1
X-Debbugs-CC: debia...@lists.debian.org
Tags: sid trixie
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:lme4 has been trying to migrate for 32 
days [2]. Hence, I am filing this bug.


The version in unstable causes 3 autopkgtest failures when tested in 
testing, all on i386. The failures are due to autopkgtest timeout after 
2:47 h, while normally these tests run in minutes, so this suggests the 
tests hang. In unstable, r-cran-afex and r-cran-mertools pass (so this 
is probably a (set of) package(s) in unstable that also needs to migrate 
together with lme4), but r-cran-mlmrev also times out in unstable.


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.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

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


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

Hi,

On Sun, 6 Aug 2023 10:44:35 + Graham Inggs  wrote:

> Yet r-cran-mlmrev[3] still seems to have the timeout issue in unstable.

The timeout of r-cran-mlmrev's autopkgtests on i386 is the last
blocker for lme4, so I will allow lme4 to migrate and (attempt) to
clone this bug to r-cran-mlmrev.


This issue seems to have solved itself somewhere in September or early 
October.


Paul


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

Bug#1054689: therion: FTBFS: utest-proj.cxx:1:10: fatal error: catch2/catch.hpp: No such file or directory

[Martin Budaj]

On Thu, Nov 9, 2023 at 3:14 AM Wookey  wrote:
> On 2023-11-08 20:10 +0100, Martin Budaj wrote:
> > as we still need to maintain Catch2 v2 API compatibility to run CI tests
> > and builds on older Ubuntu images, we can't simply migrate to v3.
>
> Who is building 'latest' Therion on old Ubuntu? And are they getting
> their sources from the Debian unstable package? Or from Upstream?

GitHub Actions has Ubuntu 20.04 and 22.04 images:
https://github.com/actions/runner-images
We use it to run CI tests and to build the official installer.

> > For now, I'll just enable using the bundled Catch2 instead of v3 installed
> > in the system.
>
> That's not the right approach for the Debian package, and this bug is about 
> the debian package.
> Debian unstable has catch 3 in it. We should use it, not an old bundled 
> catch2 copy.
> Upstream builds and Ubuntu builds can do something different if need
> be but that's not a good reason for the Debian package not to
> DTRT. And in general I'd expect current Ubuntu to have catch3 too so
> using the system version will be appropriate there too.

Sure, but to do it properly takes more time then I could currently
dedicate to this, as more changes are required:
- adapt the C++ sources to Catch v3
- introduce #ifs to C++ sources to switch between bundled and system
headers, as v3 names them differently
- modify make and cmake build systems to handle this switching

I plan to do it when time allows (upstream), but for now I think that
it's better to have a workaround than nothing.

Best wishes
Martin

Bug#1055662: marked as done (rust-proc-macro2: build-depends on missing package librust-proc-macro2-1+proc-macro-dev)

[Debian Bug Tracking System]

Your message dated Thu, 09 Nov 2023 19:39:43 +0100
with message-id <169955518379.400430.2863649441761034...@auryn.jones.dk>
and subject line Re: rust-proc-macro2: build-depends on missing package 
librust-proc-macro2-1+proc-macro-dev
has caused the Debian Bug report #1055662,
regarding rust-proc-macro2: build-depends on missing package 
librust-proc-macro2-1+proc-macro-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.)


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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

build-depends on missing package librust-proc-macro2-1+proc-macro-dev

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmVNJc4ACgkQLHwxRsGg
ASFk+A//Z+2wMdY7QR3oDEfT/2+dS8QbYT+J9Uk9f+JCQIqotQRqLf96OL+3r8HU
+kpf1LOtBJ0nKdiliGZkO6vrAn/Qw2iMD2PBTcWzhUvRU1kpO1tcXZy8EyuZ0Pdu
Z9t58seLJVwpD22rq5dcGtARPVzn3fTcb9lgopNbqyh6rHkUZ4Q/hEMIsY0z2Xt7
WV0GpwdmE09Y2+SfO1fbCpXdNzDwUh/33GV1tU5XTK2XaJHucJu5+cDtn4vDfNfK
LMRyfjPeSBCLCJ7+k77tnjlh5KMG9fYdfyBRFvhnT2B6bT4d4P4upno/vwZ9BX5T
4DE3mEFTWO+PesGO6KzIU7ks+1MgbnVZO7PZNPyzXza7D2dlOajZc7r3TnjHzaGF
g3s5bZXjauOkypbE6utuiOhJ2xPB7ore+eK2AawyAizpQxea8ISsogyen7XOqbGd
rVKRTapWDfzMbXmtH2y29QjG1pbirB2NaCP4JmHUKIhGo1hofv8ei32a4Vkc59Pl
0HuI5d3gqD5HrroT82pXuF1VfNxHZPMiXzc3xNftAgPq18clOA8niSZq5dadaC1a
FrFFyiozTRh3z0ebQ+/7Y6tZWh/uRMiXaTaHgyvb767HTMTn7TX1loVME51w/v0D
epnbvAwxOard0sdtvwsIGKP+Nv3cBRfUIsRk7AQDTIEzYj2T0NQ=
=9G7E
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Wrong package targeted.  Filed correctly in bug#1055662, so closing
here.

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/
 * Sponsorship: https://ko-fi.com/drjones

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature
--- End Message ---

Bug#1055663: rust-syn: build-depends on missing package librust-proc-macro2-1+proc-macro-dev

[Jonas Smedegaard]

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

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

build-depends on missing package librust-proc-macro2-1+proc-macro-dev

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmVNJhkACgkQLHwxRsGg
ASGrug//d6DvX2AJD28nncKM56m2ISY7zzz31HNvzmbfuAXJ3fMZ24zGCXJKjaiQ
68w3C1Te3cczJvlzuD37G7aG3ZSYSVfv5BH1MYoHnuxRC19DWJfglbB5Z/sIx1He
QO9G0FuFNyrzmEsB04zDSevK56Fx30nMb81jpCpgEp0fNjjn1Wt6R6Njfg9ab9q0
WMk4AlTGvkjCMTRKqlGhKGAJaspN1ZazQi+BdN/CSWkj/m2vfVyUtmxoJUYyQ5EJ
dxL0kzScXySnXgzq1D90qPSMYP6FDhj66BBAp0q0FWJRIsz73gclLQreLQQveH/c
5NMdBzPs7zs9Z9DEzw+n1C7TVvRhsD+z601XyJdBUdwZxL0aespQz8AYYWigwoYw
gv6dqmZ1mOPw18ZRRKhDq1f6bkxneeAJS0waaM4tTN0F7VF+WYzUF4IfMp3tz0q+
xBDrqwk70GfHgvFW4xf/VSkSiRSZpLK4gBo/hSbrts2yT14OC3YrtP+gaCB7pTmI
RMZ1hY9C4JYvkSTy7N7miD3h8UGiZieLaoliHSBj75dVah9EoTbJ8reXJmMuydRb
tBr90dJOiKP9soyfpS7m1Amcjm5+kQuGr9o9btrz2Q7jRvt5rpmmHY0t9IMWj+3m
z87dnWb697h1h4GT7oZQldnraZEU459+tgAP31NXM4Sjmh82kQ8=
=SlJm
-END PGP SIGNATURE-

Bug#1055662: rust-proc-macro2: build-depends on missing package librust-proc-macro2-1+proc-macro-dev

[Jonas Smedegaard]

Source: rust-proc-macro2
Version: 1.0.65-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

build-depends on missing package librust-proc-macro2-1+proc-macro-dev

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmVNJc4ACgkQLHwxRsGg
ASFk+A//Z+2wMdY7QR3oDEfT/2+dS8QbYT+J9Uk9f+JCQIqotQRqLf96OL+3r8HU
+kpf1LOtBJ0nKdiliGZkO6vrAn/Qw2iMD2PBTcWzhUvRU1kpO1tcXZy8EyuZ0Pdu
Z9t58seLJVwpD22rq5dcGtARPVzn3fTcb9lgopNbqyh6rHkUZ4Q/hEMIsY0z2Xt7
WV0GpwdmE09Y2+SfO1fbCpXdNzDwUh/33GV1tU5XTK2XaJHucJu5+cDtn4vDfNfK
LMRyfjPeSBCLCJ7+k77tnjlh5KMG9fYdfyBRFvhnT2B6bT4d4P4upno/vwZ9BX5T
4DE3mEFTWO+PesGO6KzIU7ks+1MgbnVZO7PZNPyzXza7D2dlOajZc7r3TnjHzaGF
g3s5bZXjauOkypbE6utuiOhJ2xPB7ore+eK2AawyAizpQxea8ISsogyen7XOqbGd
rVKRTapWDfzMbXmtH2y29QjG1pbirB2NaCP4JmHUKIhGo1hofv8ei32a4Vkc59Pl
0HuI5d3gqD5HrroT82pXuF1VfNxHZPMiXzc3xNftAgPq18clOA8niSZq5dadaC1a
FrFFyiozTRh3z0ebQ+/7Y6tZWh/uRMiXaTaHgyvb767HTMTn7TX1loVME51w/v0D
epnbvAwxOard0sdtvwsIGKP+Nv3cBRfUIsRk7AQDTIEzYj2T0NQ=
=9G7E
-END PGP SIGNATURE-

Processed: [bts-link] source package src:python-django-crispy-forms

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package 
> src:python-django-crispy-forms
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #1052852 (http://bugs.debian.org/1052852)
> # Bug title: python-django-crispy-forms: FTBFS: make[1]: *** 
> [debian/rules:17: override_dh_auto_test] Error 1
> #  * https://github.com/django-crispy-forms/django-crispy-forms/pull/1257
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 1052852 + fixed-upstream
Bug #1052852 [src:python-django-crispy-forms] python-django-crispy-forms: 
FTBFS: make[1]: *** [debian/rules:17: override_dh_auto_test] Error 1
Added tag(s) fixed-upstream.
> usertags 1052852 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:flask-wtf

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:flask-wtf
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #1052770 (http://bugs.debian.org/1052770)
> # Bug title: flask-wtf: FTBFS: dh_auto_test: error: pybuild --test 
> --test-pytest -i python{version} -p 3.11 returned exit code 13
> #  * https://github.com/wtforms/flask-wtf/pull/549
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 1052770 + fixed-upstream
Bug #1052770 [src:flask-wtf] flask-wtf: FTBFS: dh_auto_test: error: pybuild 
--test --test-pytest -i python{version} -p 3.11 returned exit code 13
Added tag(s) fixed-upstream.
> usertags 1052770 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

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

[Debian Bug Tracking System]

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

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

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

Processed: Re: Bug#1055494 closed by Debian FTP Masters (reply to Sebastian Andrzej Siewior ) (Bug#1055494: fixed in clamav 1.2.1+dfsg-2)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #1055494 {Done: Sebastian Andrzej Siewior } 
[clamav-doc] clamav-doc: missing Breaks+Replaces: clamav (<< 1.2)
'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 clamav/1.2.1+dfsg-2.

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

Bug#1055494: closed by Debian FTP Masters (reply to Sebastian Andrzej Siewior ) (Bug#1055494: fixed in clamav 1.2.1+dfsg-2)

[Andreas Beckmann]

Control: reopen -1

On 07/11/2023 22.27, Debian Bug Tracking System wrote:

This is an automatic notification regarding your Bug report
which was filed against the clamav-doc package:

#1055494: clamav-doc: missing Breaks+Replaces: clamav (<< 1.2)


There is no file conflict between clamav-docs in sid (ships everything 
in /usr/share/doc/clamav-docs/) and clamav-doc in experimental (ships 
most bits in /usr/share/doc/clamav/), but between clamav/sid and 
clamav-doc/experimental, and only on /usr/share/doc/clamav/README.Debian.gz


Andreas

Bug#1042659: closed by Debian FTP Masters (reply to Félix Sipma ) (Bug#1042659: fixed in restic 0.16.0-1)

[Félix Sipma]

Hi Andreas,

I was working for a long time on a newer release of restic, and finally 
resolved it by disabling azure. This particular bug was completely out 
of my radar and I just noticed about it when preparing the upload.


Sorry about wasting your time, this was of course not my intention.

Regards,

On 2023-11-02 06:59+0100, Andreas Metzler wrote:

On 2023-11-01 Debian Bug Tracking System  wrote:
[...]

#1042659: restic: FTBFS with Sphinx 7.1, docutils 0.20: TypeError: not all 
arguments converted during string formatting



It has been closed by Debian FTP Masters  (reply to 
Félix Sipma ).

[...]

  * New upstream version 0.16.0 (Closes: #1031235, #1042659)

[...]

In future could we pretty pretty pretty please have a minimum amount of
communication? If you sent something like "I am working on this" or
"going to work on this in the next days" to the bug report I would not
have wasted time and effort on diagnosing the issue, digging out the
patch and preparing and testing a NMU.

TIA, cu andreas


--
Félix


signature.asc
Description: PGP signature

Bug#1055228: plplot: FTBFS on armhf (test segfault)

[Rafael Laboissière]

Control: tags -1 + confirmed help

* Gianfranco Costamagna  [2023-11-02 15:09]:


Source: plplot
Version: 5.15.0+dfsg2-6
Severity: serious

Hello, I found the package FTBFS on Ubuntu, checked on amdahl and found the 
same issue.

 /usr/bin/make  -f examples/fortran/CMakeFiles/x31f.dir/build.make 
examples/fortran/CMakeFiles/x31f.dir/build
 make[5]: Entering directory 
'/home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf'
 make[5]: Nothing to be done for 'examples/fortran/CMakeFiles/x31f.dir/build'.
 make[5]: Leaving directory 
'/home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf'
 [ 46%] Built target x31f
 /usr/bin/make  -f examples/CMakeFiles/test_fortran_svg.dir/build.make 
examples/CMakeFiles/test_fortran_svg.dir/depend
 make[5]: Entering directory 
'/home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf'
 cd /home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf && /usr/bin/cmake -E 
cmake_depends "Unix Makefiles" /home/locutusofborg/plplot-5.15.0+dfsg2 
/home/locutusofborg/plplot-5.15.0+dfsg2/examples 
/home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf 
/home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf/examples 
/home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf/examples/CMakeFiles/test_fortran_svg.dir/DependInfo.cmake
 "--color="
 make[5]: Leaving directory 
'/home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf'
 /usr/bin/make  -f examples/CMakeFiles/test_fortran_svg.dir/build.make 
examples/CMakeFiles/test_fortran_svg.dir/build
 make[5]: Entering directory 
'/home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf'
 cd /home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf/examples && 
/usr/bin/cmake -E echo "Generate fortran results for svg device"
 Generate fortran results for svg device
 cd /home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf/examples && 
env 
EXAMPLES_PREFIX=/home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf/examples
 SRC_EXAMPLES_PREFIX=/home/locutusofborg/plplot-5.15.0+dfsg2/examples 
OUTPUT_DIR=/home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf/examples/test_examples_output_dir
 /bin/bash 
/home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf/plplot_test/plplot-test.sh
 --verbose --front-end=fortran --device=svg
 Testing front-end fortran
 x16af
 x00f
 x01f
 x02f
 x03f
 x04f
 x05f
 x06f
 x07f
 x08f
 x09f
 /home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf/plplot_test/test_fortran.sh: line 54: 3932208 Bus 
error   $DEBUG_CMD "$fortrandir"/x${index}f -dev $device -o 
"${OUTPUT_DIR}"/x${index}${lang}%n.$dsuffix $options 2> fortran_${device}_test.error >| 
"${OUTPUT_DIR}"/x${index}${lang}_${dsuffix}.txt

Program received signal SIGBUS: Access to an undefined portion of a memory 
object.

 Backtrace for this error:
 make[5]: *** [examples/CMakeFiles/test_fortran_svg.dir/build.make:388: 
examples/test_examples_output_dir/x00f01.svg] Error 1
 make[5]: *** Deleting file 'examples/test_examples_output_dir/x00f01.svg'
 make[5]: Leaving directory 
'/home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf'
 make[4]: *** [CMakeFiles/Makefile2:5049: 
examples/CMakeFiles/test_fortran_svg.dir/all] Error 2
 make[4]: Leaving directory 
'/home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf'
 make[3]: *** [CMakeFiles/Makefile2:7121: 
examples/CMakeFiles/test_noninteractive.dir/rule] Error 2
 make[3]: Leaving directory 
'/home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf'
 make[2]: *** [Makefile:2243: test_noninteractive] Error 2
 make[2]: Leaving directory 
'/home/locutusofborg/plplot-5.15.0+dfsg2/obj-arm-linux-gnueabihf'
 make[1]: *** [debian/rules:55: override_dh_auto_test] Error 2
 make[1]: Leaving directory '/home/locutusofborg/plplot-5.15.0+dfsg2'
 make: *** [debian/rules:48: binary] Error 2


Full log attached


Thanks for this bug report. I can indeed reproduce the problem.

It was triggered by the recent change in dpkg-buildflags, which now 
includes -fstack-clash-protection in FFLAGS. This was done through commit 
1d46b351f [1], , intended to fix Bug#1054583 [2], and which got included 
in version 1.22.1 of dpkg-dev, released on October 30.


The Fortran example x09f.f90, which is exercised during the building of 
plplot, now fails on armhf, due to the use of the compiler option 
-fstack-clash-protection. I did not check whether this is also the case 
for arm64 and armel.


As far as I can tell, this is due to a global variable (tr) that is not 
correctly accessed in a private function (mypltr) of the x09f program.


There may be a programming error in x09f.f90 or this may be a problem 
with gfortran on armhf. My knowledge of Fortran is almost non existent 
and I will need the help of experts, in order to fix the issue.


Best,

Rafael Laboissière

 [1] https://git.dpkg.org/cgit/dpkg/dpkg.git/diff/?id=1d46b351f
 [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054583

Processed: Re: plplot: FTBFS on armhf (test segfault)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + confirmed help
Bug #1055228 [src:plplot] plplot: FTBFS on armhf (test segfault)
Added tag(s) confirmed and help.

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

Bug#1042308: marked as done (django-assets: FTBFS: error in django-assets setup command: 'install_requires' must be a string or list of strings containing valid project/version requirement specifiers;

[Debian Bug Tracking System]

Your message dated Thu, 09 Nov 2023 13:48:54 +
with message-id 
and subject line Bug#1042308: fixed in django-assets 2.0-3
has caused the Debian Bug report #1042308,
regarding django-assets: FTBFS: error in django-assets setup command: 
'install_requires' must be a string or list of strings containing valid 
project/version requirement specifiers; Expected end or semicolon (after name 
and no valid version specifier)
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.)


-- 
1042308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042308
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: django-assets
Version: 2.0-2.1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 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,sphinxdoc --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:240: python3.11 setup.py clean 
> error in django-assets setup command: 'install_requires' must be a string or 
> list of strings containing valid project/version requirement specifiers; 
> Expected end or semicolon (after name and no valid version specifier)
> webassets>=>=2.0
>  ^
> E: pybuild pybuild:388: clean: plugin distutils failed with: exit code=1: 
> python3.11 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.11 returned 
> exit code 13
> make: *** [debian/rules:9: clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2023/07/26/django-assets_2.0-2.1_unstable.log

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

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

Debian distribution maintenance software
pp.
Lena Voytek  (supplier of updated django-assets 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 08 Aug 2023 10:59:07 -0700
Source: django-assets
Architecture: source
Version: 2.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Lena Voytek 
Closes: 1042308
Changes:
 django-assets (2.0-3) unstable; urgency=medium
 .
   * Team upload.
   * Remove 01-webassets_version.patch: The issue was fixed upstream through
 __init__.py leading this patch to cause the package to ftbfs
 (Closes: #1042308).
   * Add fix-python3.11-regex.patch to fix build against python 3.11.
Checksums-Sha1:
 775e17e191dcfe42dab61e10d196308e0676af16 2290 django-assets_2.0-3.dsc
 e7d3acd268c97fb49d3ab5634bb2091ea946b7f2 29613 django-assets_2.0.orig.tar.gz
 d5975ee83209f1541771139974e7fc68d050c2c4 5332 django-assets_2.0-3.debian.tar.xz
 92c76baffb1b563ab3a2b4dfff16891c91b26aba 7923 
django-assets_2.0-3_source.buildinfo
Checksums-Sha256:
 e8ef16c9b6bb86ebe1d1845a1eee66b9fe42df602f1fec4418773c06a1cb8eb1 2290 
django-assets_2.0-3.dsc
 98922a9b57b35f3691a0c66db76e35fcd45a403923c4bccbb31c7218996e6b8f 29613 
django-assets_2.0.orig.tar.gz
 0651b8220b21475205b6593ca2de617e447b9dee70bca4dbad72ac75f0b7e2a7 5332 
django-assets_2.0-3.debian.tar.xz
 81a7c146a60616107620bea1535da8f32d7d08730d961b848bd9b223b538f3a5 7923 
django-assets_2.0-3_source.buildinfo
Files:
 

Bug#1055111: marked as pending in ffmpeg

[Diederik de Haas]

On Thursday, 9 November 2023 14:14:23 CET Sebastian Ramacher wrote:
> > FTR: Upstream has an alternative patch for this (and references this bug):
> > https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/f01fdedb69e4accb1d1555106d
> > 8f682ff1f1ddc7
> I am awayre, yes. But a release of 6.1 is expected soon which hopefully
> includes the patch.

Ok, excellent :-)
I was/am a bit confused about how upstream does releases and when I saw the 
release/6.1 branch and commits titled "Bump versions prior to 6.1" and "doc/
APIchanges: Add 6.1 cut point" and "version " added to Changelog, I 
thought the release already happened. But it didn't include that patch.

Not seeing the tags attached to commits in master or the release branches 
added to my confusion. I was planning to look further into this to hopefully 
understand how they work.

Cheers,
  Diederik

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

Processed: src:nextpnr: fails to migrate to testing for too long: triggers autopkgtest failures

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.6-2
Bug #1055641 [src:nextpnr] src:nextpnr: fails to migrate to testing for too 
long: triggers autopkgtest failures
Marked as fixed in versions nextpnr/0.6-2.
Bug #1055641 [src:nextpnr] src:nextpnr: fails to migrate to testing for too 
long: triggers autopkgtest failures
Marked Bug as done

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

Bug#1053574: marked as done (wlgreet: FTBFS with DEB_BUILD_OPTIONS=nocheck: does not perform the build)

[Debian Bug Tracking System]

Your message dated Thu, 09 Nov 2023 13:33:56 +
with message-id 
and subject line Bug#1053574: fixed in wlgreet 0.4.1-3
has caused the Debian Bug report #1053574,
regarding wlgreet: FTBFS with DEB_BUILD_OPTIONS=nocheck: does not perform the 
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.)


-- 
1053574: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053574
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wlgreet
Version: 0.4.1-2
Severity: serious
Justification: nocheck FTBFS is serious since trixie
Tags: ftbfs

wlgreet uses the same dh_auto_build override as greetd so please see
https://bugs.debian.org/1050769 for more details and a proposal to fix
this type of issue.

Thank you,
Jeremy Bícha
--- End Message ---
--- Begin Message ---
Source: wlgreet
Source-Version: 0.4.1-3
Done: Marc Dequènes (Duck) 

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

Debian distribution maintenance software
pp.
Marc Dequènes (Duck)  (supplier of updated wlgreet 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, 09 Nov 2023 22:20:10 +0900
Source: wlgreet
Architecture: source
Version: 0.4.1-3
Distribution: unstable
Urgency: medium
Maintainer: Marc Dequènes (Duck) 
Changed-By: Marc Dequènes (Duck) 
Closes: 1053574
Changes:
 wlgreet (0.4.1-3) unstable; urgency=medium
 .
   * Fix build when DEB_BUILD_OPTIONS contains 'nocheck'
 (Closes: #1053574).
Checksums-Sha1:
 e134d97bc87b3d1d1fe068e960827a7535c8d805 2326 wlgreet_0.4.1-3.dsc
 2ff797f3909bec7f59f6e2f1a4395f60bdd61860 4520 wlgreet_0.4.1-3.debian.tar.xz
 7cf69e125c521c18c0a645f1bacb7de194782501 16089 wlgreet_0.4.1-3_amd64.buildinfo
Checksums-Sha256:
 39d6df5b48382414819f2964ef42f516377184574f9711f80e743c62c4583de7 2326 
wlgreet_0.4.1-3.dsc
 8e302001c4fc649880d8b6d007ffbbd217a9f5802771417ac1ff2783eeec9d4e 4520 
wlgreet_0.4.1-3.debian.tar.xz
 a36bfddc2be80d10e287825f24c9ce347969a4de8f68a232c7ffe2e59f6dc98e 16089 
wlgreet_0.4.1-3_amd64.buildinfo
Files:
 e9de566f4b12ea997d57d3e8d7630fc0 2326 misc optional wlgreet_0.4.1-3.dsc
 29c7c7e5af72924e4dbb1761403334b9 4520 misc optional 
wlgreet_0.4.1-3.debian.tar.xz
 8ccf633cc9f117e8d827900fda844369 16089 misc optional 
wlgreet_0.4.1-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEcpcqg+UmRT3yiF+BVen596wcRD8FAmVM3YgACgkQVen596wc
RD/HBA/8CNkvY+oTwheiZWyYjAUiR425SSh6ZJnXNlrEa5iAP2zd5oj/VaVDL5wK
ucd9zu9uIRmAWXyKfO/468EY6No3a8rjegdY2RL5xlG2ucbmApN7k1qAMwBuwO6G
q4Rdy2EbpK4t/XlcF3saEjcvfunuIh+A2VQW6aiVfXjcZw4hJ5ce/95Xp0SQNL46
rQTpRzx4ioG/JlrBxWvUdJP+dVUAzasbFn4M2v3WZzqSvsTHll6ys3bCCH9huhQt
4CdwKBEkBP0TgwhzBzCZES6v8dDYqa5TBKRgYgnsT1vf+IJCz3w58Ka/kwBiJqUi
JG9juxdR7D52IGASG2oBtT2ALOMuZFOciNo3jnJCWkM+qSUaPYAXn/sjQIzBoo8h
CsYedOe3CDRasP7FjZQ3r8h3VeGJuofdtksBoeyrmQX1E0bCFIMM3wzs3ONJ03oY
MC22b5Laq4qC6SY1hkASwkE3JTuSS5sEDJ047Bmpk22g3POz1iTdSsWyG+SktjMx
v0lb+dM6vZXXO9rsZRWgbjAyUgEYPCKg0aqzibe7z9jrQeYRo9l/NrutgLY4qBr6
8G8y2RlnIKiSsxxcGD5zDfn3mohmdX24F5OtWl0VcjjiaoVcY0lkp16NeJYmY20g
BPaRdgkEKaCmO09CHUF3o4IQDkq2K7mwNKZ1P6iFS9PvEVFIfH4=
=Rgok
-END PGP SIGNATURE End Message ---

Bug#1055641: src:nextpnr: fails to migrate to testing for too long: triggers autopkgtest failures

[Paul Gevers]

Source: nextpnr
Version: 0.6-1
Severity: serious
Control: close -1 0.6-2
Tags: sid trixie
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:nextpnr has been trying to migrate for 32 
days [2]. Hence, I am filing this bug. The version in unstable triggers 
failures in fpga-icestorm as well as its own autopkgtest fails (the 
latter one due to what I see as a bug in autopkgtest, but that's trivial 
to work around on the package side).


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.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

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



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1055640: src:prometheus: fails to migrate to testing for too long: FTBFS on mips64el

[Paul Gevers]

Source: prometheus
Version: 2.45.0+ds-3
Severity: serious
Control: close -1 2.45.1+ds-1
Tags: sid trixie ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

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


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.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

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



OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: src:prometheus: fails to migrate to testing for too long: FTBFS on mips64el

[Debian Bug Tracking System]

Processing control commands:

> close -1 2.45.1+ds-1
Bug #1055640 [src:prometheus] src:prometheus: fails to migrate to testing for 
too long: FTBFS on mips64el
Marked as fixed in versions prometheus/2.45.1+ds-1.
Bug #1055640 [src:prometheus] src:prometheus: fails to migrate to testing for 
too long: FTBFS on mips64el
Marked Bug as done

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

Bug#1051543: marked as done (grub2: Fails to load normal.mod from a XFS v5 parition.)

[Debian Bug Tracking System]

Your message dated Thu, 09 Nov 2023 13:19:20 +
with message-id 
and subject line Bug#1051543: fixed in grub2 2.12~rc1-12
has caused the Debian Bug report #1051543,
regarding grub2: Fails to load normal.mod from a XFS v5 parition.
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.)


-- 
1051543: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051543
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: grub2
Version: 2.12~rc1-9
Severity: Serious
control: forwarded -1 https://savannah.gnu.org/bugs/?64376

I have a single XFS partition which contains the root filesystem and the
boot partition. Since the recent upgrade to the 2.12 series I can't boot
anymore because grub complains that it can't find normal.mod and remains in
the rescue shell.
The ls command kind of works. A ls in /boot/grub/i386-pc/ (where the
normal.mod should be) shows a few files and then abort with the error
message: 'error: invalid XFS directory entry'.

I figured out that if I remove that directory and create a new one only
with normal.mod then it was able to find it and complained about onother file.
I then repeated the game until I had more files… The invocation of grub-install
copied all files and broke it again.

I then looked at various places and stumbled uppon
https://savannah.gnu.org/bugs/?64376 and this indeed matches what I see.
I rebuilt the grub2 package with commit ef7850c757fb3 ("fs/xfs: Fix
issues found while fuzzing the XFS filesystem") reverted, installed from
a rescue system and voila it boots again.

My xfs filesystem is a normal v5 as in:
| # xfs_info /dev/sdb1
| meta-data=/dev/sdb1  isize=512agcount=4, agsize=655360 blks
|  =   sectsz=512   attr=2, projid32bit=1
|  =   crc=1finobt=1, sparse=1, rmapbt=1
|  =   reflink=1bigtime=0 inobtcount=0 nrext64=0
| data =   bsize=4096   blocks=2621440, imaxpct=25
|  =   sunit=0  swidth=0 blks
| naming   =version 2  bsize=4096   ascii-ci=0, ftype=1
| log  =internal log   bsize=4096   blocks=3693, version=2
|  =   sectsz=512   sunit=0 blks, lazy-count=1
| realtime =none   extsz=4096   blocks=0, rtextents=0

Sebastian
--- End Message ---
--- Begin Message ---
Source: grub2
Source-Version: 2.12~rc1-12
Done: Julian Andres Klode 

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

Debian distribution maintenance software
pp.
Julian Andres Klode  (supplier of updated grub2 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, 09 Nov 2023 14:13:44 +0200
Source: grub2
Architecture: source
Version: 2.12~rc1-12
Distribution: unstable
Urgency: medium
Maintainer: GRUB Maintainers 
Changed-By: Julian Andres Klode 
Closes: 1051543
Changes:
 grub2 (2.12~rc1-12) unstable; urgency=medium
 .
   [ Mate Kukri ]
   * Port UEFI based network stack to 2.12 (LP: #2039081)
   * efi: Correct image unloading behavior
   * Prevent the incorrect use of `UnloadImage()` by binaries loaded by peimage
   * efinet: HTTP_MESSAGE fix field size (LP: #2043084)
 .
   [ Abe Wieland ]
   * Maintain administrator value for os-prober
 .
   [ Julian Andres Klode ]
   * Cherry-pick upstream XFS directory extent parsing fixes (Closes: #1051543)
 (LP: #2039172)
Checksums-Sha1:
 312ce277a37bce57439e0e7a9664ef3bc8a2db4d 7151 grub2_2.12~rc1-12.dsc
 85dcb0a0091d0ccd216dd6466efdebc28f57f5fd 1099048 
grub2_2.12~rc1-12.debian.tar.xz
 2513c431b1607ba19bceab96f7e0426f85840163 13770 
grub2_2.12~rc1-12_source.buildinfo
Checksums-Sha256:
 e4a288912b89c0a61db359b2d05f2d3765f3872703f3c7e061239e590d96eb2e 7151 
grub2_2.12~rc1-12.dsc
 3816361feeb509d09f4c71a38ea5000bbc4e80812e898387d09aa7ccb4320406 1099048 
grub2_2.12~rc1-12.debian.tar.xz
 db6acce9db781bafd28a609f284a80ba563c5b9aa70679dc684970e2f9ab15e7 13770 
grub2_2.12~rc1-12_source.buildinfo
Files:
 a9e20ad1e89a0bbc210cbba24d785d66 7151 admin optional 

Bug#1050769: marked as done (greetd FTBFS with DEB_BUILD_OPTIONS=nocheck: does not perform the build)

[Debian Bug Tracking System]

Your message dated Thu, 09 Nov 2023 13:18:57 +
with message-id 
and subject line Bug#1050769: fixed in greetd 0.9.0-5
has caused the Debian Bug report #1050769,
regarding greetd FTBFS with DEB_BUILD_OPTIONS=nocheck: does not perform the 
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.)


-- 
1050769: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050769
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: greetd
Version: 0.9.0-4
Severity: serious
Justification: nocheck FTBFS is serious since trixie

greetd fails to build from source, when DEB_BUILD_OPTIONS contains
nocheck. A build ends as follows:

| dh binary --buildsystem=cargo
|dh_update_autotools_config -O--buildsystem=cargo
|dh_autoreconf -O--buildsystem=cargo
|debian/rules execute_before_dh_auto_configure
| make[1]: Entering directory '/<>'
| printf '{"package":"%s","files":{}}\n' $(sha256sum Cargo.toml | grep -Po 
'^\S+') > debian/cargo-checksum.json;
| make[1]: Leaving directory '/<>'
|dh_auto_configure -O--buildsystem=cargo
| debian cargo wrapper: options, profiles, parallel: ['nocheck', 'parallel=8'] 
[] ['-j8']
| debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu, 
x86_64-linux-gnu
| debian cargo wrapper: linking /usr/share/cargo/registry/* into 
/<>/debian/cargo_registry/
|debian/rules override_dh_auto_build
| make[1]: Entering directory '/<>'
| # actually does the build
| dh_auto_test -- --release
| make -C man all
| make[2]: Entering directory '/<>/man'
| /usr/bin/scdoc < agreety-1.scd > agreety.1
| /usr/bin/scdoc < greetd-1.scd > greetd.1
| /usr/bin/scdoc < greetd-5.scd > greetd.5
| /usr/bin/scdoc < greetd-ipc-7.scd > greetd-ipc.7
| make[2]: Leaving directory '/<>/man'
| make[1]: Leaving directory '/<>'
|create-stamp debian/debhelper-build-stamp
|dh_testroot -O--buildsystem=cargo
|dh_prep -O--buildsystem=cargo
|debian/rules override_dh_auto_install
| make[1]: Entering directory '/<>'
| dh_install target/x86_64-unknown-linux-gnu/release/greetd /usr/sbin/
| dh_install: warning: Cannot find (any matches for) 
"target/x86_64-unknown-linux-gnu/release/greetd" (tried in ., debian/tmp)
| 
| dh_install: warning: greetd missing files: 
target/x86_64-unknown-linux-gnu/release/greetd
| dh_install: error: missing files, aborting
| make[1]: *** [debian/rules:26: override_dh_auto_install] Error 25
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:8: binary] Error 2
| dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2

Note that nothing is ever built. debian/rules suggests that it attempts
to build using dh_auto_test, but given a high enough compatibility level
dh_auto_test honours DEB_BUILD_OPTIONS=nocheck. You probably need to run
dh_auto_build at some point.

Helmut
--- End Message ---
--- Begin Message ---
Source: greetd
Source-Version: 0.9.0-5
Done: Marc Dequènes (Duck) 

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

Debian distribution maintenance software
pp.
Marc Dequènes (Duck)  (supplier of updated greetd 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, 09 Nov 2023 21:58:10 +0900
Source: greetd
Architecture: source
Version: 0.9.0-5
Distribution: unstable
Urgency: medium
Maintainer: Marc Dequènes (Duck) 
Changed-By: Marc Dequènes (Duck) 
Closes: 1050769
Changes:
 greetd (0.9.0-5) unstable; urgency=medium
 .
   * Fix build when DEB_BUILD_OPTIONS contains 'nocheck'
 (Closes: #1050769).
   * Fix perms using the proper stage (Thanks Jeremy Bicha).
Checksums-Sha1:
 fefaa038093b7b5be8e4be75bf688e29c3885401 2208 greetd_0.9.0-5.dsc
 a32eb4e139418d684d4d7367fd5e42c26a0c7461 5048 greetd_0.9.0-5.debian.tar.xz
 d9979f37f5794c7cfb4b1fdb8669df6bffb25956 13267 greetd_0.9.0-5_amd64.buildinfo
Checksums-Sha256:
 59fc9ab96d00a977229664fb0a0c7b69c5ea0cb2e4809200f64600a8a475e293 2208 
greetd_0.9.0-5.dsc
 dcf8ce6f4c8d6cae3603dca9d1a896ae64447460c112dd0d2c1cebb733e1e1c1 5048 
greetd_0.9.0-5.debian.tar.xz
 

Processed: Re: Bug#1041834: libclang-rt-16-dev: undeclared file conflict with libclang-rt-16-dev-wasm{32,64} on /usr/lib/llvm-16/lib/clang/16/lib/wasi/libclang_rt.builtins-wasm*.a

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 libclang-rt-17-dev: undeclared file conflict with 
> libclang-rt-17-dev-wasm{32,64} on 
> /usr/lib/llvm-17/lib/clang/17/lib/wasi/libclang_rt.builtins-wasm*.a
Bug #1041838 [libclang-rt-17-dev] libclang-rt-16-dev: undeclared file conflict 
with libclang-rt-16-dev-wasm{32,64} on 
/usr/lib/llvm-16/lib/clang/16/lib/wasi/libclang_rt.builtins-wasm*.a
Changed Bug title to 'libclang-rt-17-dev: undeclared file conflict with 
libclang-rt-17-dev-wasm{32,64} on 
/usr/lib/llvm-17/lib/clang/17/lib/wasi/libclang_rt.builtins-wasm*.a' from 
'libclang-rt-16-dev: undeclared file conflict with 
libclang-rt-16-dev-wasm{32,64} on 
/usr/lib/llvm-16/lib/clang/16/lib/wasi/libclang_rt.builtins-wasm*.a'.

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

Bug#1055639: surf: flaky autopkgtest: Too few characters detected (0)

[Paul Gevers]

Source: surf
Version: 2.1+git20221016-5
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

I looked at the results of the autopkgtest of your package. I noticed 
that it regularly fails (in this case because it's blocking migration of 
src:autopkgtest), mostly on armhf and a bit on ppc64el and s390x.


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

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

Paul
PS: why does it even use text from a different and very unrelated 
package? If there's not enough text in it's own source, couldn't it use 
something that's installed on all Debian systems, such that it doesn't 
need to be installed additionally and trigger migration runs?


https://ci.debian.net/data/autopkgtest/testing/s390x/s/surf/39724716/log.gz

655s autopkgtest [12:16:40]: test command3: timeout -v 5m xvfb-run 
debian/tests/test_text.sh

655s autopkgtest [12:16:40]: test command3: [---
657s
657s (surf:7172): dbind-WARNING **: 12:16:42.983: AT-SPI: Error 
retrieving accessibility bus address: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not 
provided by any .service files

658s Could not determine the accessibility bus address
662s Too few characters detected (0)
662s autopkgtest [12:16:47]: test command3: ---]


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1041838: Bug#1041834: libclang-rt-16-dev: undeclared file conflict with libclang-rt-16-dev-wasm{32,64} on /usr/lib/llvm-16/lib/clang/16/lib/wasi/libclang_rt.builtins-wasm*.a

[Vincent Lefevre]

Control: retitle -1 libclang-rt-17-dev: undeclared file conflict with 
libclang-rt-17-dev-wasm{32,64} on 
/usr/lib/llvm-17/lib/clang/17/lib/wasi/libclang_rt.builtins-wasm*.a

Sending to the right bug ("bts show --mbox 1041838" was giving the
1041834@b.d.o e-mail address instead of 1041838@b.d.o, so that I was
confused).

On 2023-11-09 14:13:37 +0100, Vincent Lefevre wrote:
> On 2023-07-24 06:54:27 +0200, Helmut Grohne wrote:
> > Control: clone -1 -2
> > Control: reassign -2 libclang-rt-17-dev
> > 
> > On Mon, Jul 24, 2023 at 06:45:00AM +0200, Helmut Grohne wrote:
> > > libclang-rt-16-dev installs
> > > /usr/lib/llvm-16/lib/clang/16/lib/wasi/libclang_rt.builtins-wasm{32,64}.a,
> > > which are also installed by libclang-rt-16-dev-wasm{32,64} respectively.
> > > Trying to coinstall these packages in unstable results in an unpack
> > > error. I guess that these files should only be contained in the
> > > respective wasm packages. Don't forget to include the necessary
> > > Breaks+Replaces when fixing this.
> > 
> > The same issue exists for version 17.
> 
> This should have been retitled. Doing it now.
> 
> But looking at
> 
>   https://packages.debian.org/sid/amd64/libclang-rt-17-dev/filelist
> 
> I can't see files with "wasm" in the file names.
> 
> If I understand correctly, the fix was done in branch 17 too:
> 
>   
> https://salsa.debian.org/pkg-llvm-team/llvm-toolchain/-/commit/f667185dabd4ebb8fd8bdceed64432a6fff10d37

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

Bug#1055111: marked as pending in ffmpeg

[Sebastian Ramacher]

On 2023-11-09 12:35:49 +0100, Diederik de Haas wrote:
> On 31 Oct 2023 23:15:11 + Sebastian Ramacher  
> wrote:
> > https://salsa.debian.org/multimedia-team/ffmpeg/-/commit/
> > 5a5de39526bd8ff5f3881cc611968062e076d9fe
> > 
> > 
> > Workaround build issues with texinfo 7.1
> > 
> > Closes: #1055111
> > 
> 
> FTR: Upstream has an alternative patch for this (and references this bug):
> https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/f01fdedb69e4accb1d1555106d8f682ff1f1ddc7

I am awayre, yes. But a release of 6.1 is expected soon which hopefully
includes the patch.

Cheers
-- 
Sebastian Ramacher

Processed: src:haskell-hsyaml-aeson: fails to migrate to testing for too long: FTBFS everywhere

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.2.0.1-2
Bug #1055638 [src:haskell-hsyaml-aeson] src:haskell-hsyaml-aeson: fails to 
migrate to testing for too long: FTBFS everywhere
The source 'haskell-hsyaml-aeson' and version '0.2.0.1-2' do not appear to 
match any binary packages
Marked as fixed in versions haskell-hsyaml-aeson/0.2.0.1-2.
Bug #1055638 [src:haskell-hsyaml-aeson] src:haskell-hsyaml-aeson: fails to 
migrate to testing for too long: FTBFS everywhere
Marked Bug as done
> block -1 by 1054961
Bug #1055638 {Done: Paul Gevers } [src:haskell-hsyaml-aeson] 
src:haskell-hsyaml-aeson: fails to migrate to testing for too long: FTBFS 
everywhere
1055638 was not blocked by any bugs.
1055638 was not blocking any bugs.
Added blocking bug(s) of 1055638: 1054961

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

Bug#1055638: src:haskell-hsyaml-aeson: fails to migrate to testing for too long: FTBFS everywhere

[Paul Gevers]

Source: haskell-hsyaml-aeson
Version: 0.2.0.1-1
Severity: serious
Control: close -1 0.2.0.1-2
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1054961

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:haskell-hsyaml-aeson has been trying to 
migrate for 61 days [2]. Hence, I am filing this bug. The version in 
unstable failed to build from source as reported in 1054961.


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.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

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



OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: severity of 1055636 is normal

[Debian Bug Tracking System]

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

> severity 1055636 normal
Bug #1055636 [ogre-1.9] ogre: Add loongarch64 support
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Processed: haskell-clash-prelude: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:158: build-ghc-stamp] Error 25

[Debian Bug Tracking System]

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

> tags 1054849 + bookworm
Bug #1054849 [src:haskell-clash-prelude] haskell-clash-prelude: FTBFS: make: 
*** [/usr/share/cdbs/1/class/hlibrary.mk:158: build-ghc-stamp] Error 25
Added tag(s) bookworm.
> thanks
Stopping processing here.

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

Bug#1054849: haskell-clash-prelude: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:158: build-ghc-stamp] Error 25

[Santiago Vila]

tags 1054849 + bookworm
thanks

I'm adding this tag because I see Adrian has just added version in bookworm
using "found". The package indeed FTBFS in bookworm in reproducible-builds:

https://tests.reproducible-builds.org/debian/rb-pkg/bookworm/arm64/haskell-clash-prelude.html

However, I rebuilt the whole of bookworm a week ago, using AWS machines
with 2 CPUs, and this package did not fail for me (see attach).

No idea why this happens. If this is a Makefile bug, you might want
to "amplify" the probability of failure by using make 4.4.x:

https://trofi.github.io/posts/238-new-make-shuffle-mode.html

Thanks.

haskell-clash-prelude_1.6.4-1_amd64-20231102T201250.732Z.gz
Description: application/gzip

Bug#1055636: ogre: Add loongarch64 support

[JiaLing Zhang]

Package: ogre-1.9
Severity: serious
File: ogre
Tags: upstream patch ftbfs loong64
Justification: fails to build from source
X-Debbugs-Cc: zhangjial...@loongson.cn

Dear Maintainer,

This package need support for loongarch64,Please help.
--- ogre-1.9-1.9.0+dfsg1.orig/OgreMain/include/OgrePlatform.h
+++ ogre-1.9-1.9.0+dfsg1/OgreMain/include/OgrePlatform.h
@@ -166,7 +166,7 @@ namespace Ogre {
 #endif
 
 /* Find the arch type */
-#if defined(__x86_64__) || defined(_M_X64) || defined(__powerpc64__) || 
defined(__alpha__) || defined(__ia64__) || defined(__s390__) || 
defined(__s390x__) || defined(__arm64__) || defined(__aarch64__) || 
defined(__mips64) || defined(__mips64_) || (defined(__riscv) && (__riscv_xlen 
== 64))
+#if defined(__x86_64__) || defined(_M_X64) || defined(__powerpc64__) || 
defined(__alpha__) || defined(__ia64__) || defined(__s390__) || 
defined(__s390x__) || defined(__arm64__) || defined(__aarch64__) || 
defined(__mips64) || defined(__mips64_) || (defined(__riscv) && (__riscv_xlen 
== 64)) || defined(__loongarch64)
 #   define OGRE_ARCH_TYPE OGRE_ARCHITECTURE_64
 #else
 #   define OGRE_ARCH_TYPE OGRE_ARCHITECTURE_32

Processed: Bug#1051543 marked as pending in grub2

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1051543 [grub2] grub2: Fails to load normal.mod from a XFS v5 parition.
Added tag(s) pending.

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

Bug#1051543: marked as pending in grub2

[Julian Andres Klode]

Control: tag -1 pending

Hello,

Bug #1051543 in grub2 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/grub-team/grub/-/commit/f18fbbb6a5b42909a45a7e4067557fab910297d7


Cherry-pick upstream XFS directory extent parsing fixes

Closes: #1051543
LP: #2039172


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1051543

Bug#1055111: marked as pending in ffmpeg

[Diederik de Haas]

On 31 Oct 2023 23:15:11 + Sebastian Ramacher  
wrote:
> https://salsa.debian.org/multimedia-team/ffmpeg/-/commit/
> 5a5de39526bd8ff5f3881cc611968062e076d9fe
> 
> 
> Workaround build issues with texinfo 7.1
> 
> Closes: #1055111
> 

FTR: Upstream has an alternative patch for this (and references this bug):
https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/f01fdedb69e4accb1d1555106d8f682ff1f1ddc7

Salsa's CI (still) succeeds if I replace the custom patch with upstream's.

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

Processed: found 1054849 in 1.6.4-1

[Debian Bug Tracking System]

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

> found 1054849 1.6.4-1
Bug #1054849 [src:haskell-clash-prelude] haskell-clash-prelude: FTBFS: make: 
*** [/usr/share/cdbs/1/class/hlibrary.mk:158: build-ghc-stamp] Error 25
Marked as found in versions haskell-clash-prelude/1.6.4-1.
> thanks
Stopping processing here.

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

Processed: found 1054961 in 0.2.0.1-1

[Debian Bug Tracking System]

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

> found 1054961 0.2.0.1-1
Bug #1054961 [src:haskell-hsyaml-aeson] haskell-hsyaml-aeson: FTBFS: 
unsatisfiable build-dependencies: libghc-hsyaml-dev (>= 0.2.0), 
libghc-hsyaml-dev (< 0.3), libghc-hsyaml-prof, libghc-vector-dev (< 0.13), 
libghc-hsyaml-doc
Marked as found in versions haskell-hsyaml-aeson/0.2.0.1-1.
> thanks
Stopping processing here.

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

Processed: found 1054979 in 1.6.4-1

[Debian Bug Tracking System]

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

> found 1054979 1.6.4-1
Bug #1054979 [src:haskell-clash-lib] haskell-clash-lib: FTBFS: unsatisfiable 
build-dependencies: libghc-clash-prelude-dev (>= 1.6.6), 
libghc-clash-prelude-dev (< 1.6.7), libghc-clash-prelude-prof, 
libghc-clash-prelude-doc
Marked as found in versions haskell-clash-lib/1.6.4-1.
> thanks
Stopping processing here.

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

Processed: found 1054971 in 1.6.4-1

[Debian Bug Tracking System]

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

> found 1054971 1.6.4-1
Bug #1054971 [src:haskell-clash-ghc] haskell-clash-ghc: FTBFS: unsatisfiable 
build-dependencies: libghc-clash-lib-dev (>= 1.6.6), libghc-clash-lib-dev (< 
1.6.7), libghc-clash-lib-prof, libghc-clash-prelude-dev (>= 1.6.6), 
libghc-clash-prelude-dev (< 1.6.7), libghc-clash-prelude-prof, 
libghc-clash-lib-doc, libghc-clash-prelude-doc
Marked as found in versions haskell-clash-ghc/1.6.4-1.
> thanks
Stopping processing here.

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

Bug#1055635: haskell-copilot-c99 FTBFS on !amd64

[Adrian Bunk]

Source: haskell-copilot-c99
Version: 3.16.1-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=haskell-copilot-c99=3.16.1-1

...
Copilot.Compile.C99:
  Compile specification: [OK, passed 1 tests]
  Compile specification in custom dir: [OK, passed 1 tests]
  Run specification: [Failed]
*** Failed! Exception: 'callProcess: ./main (exit 1): failed' (after 1 test):
...
 Properties  Total  
 Passed  3   3  
 Failed  1   1  
 Total   4   4  
Test suite unit-tests: FAIL
Test suite logged to: dist-ghc/test/copilot-c99-3.16.1-unit-tests.log
0 of 1 test suites (0 of 1 test cases) passed.
...

Bug#1055392: wasmedge: autopkgtest regression: 'cstdint' file not found

[Paul Gevers]

Hi Faidon,

On 05-11-2023 21:41, Faidon Liambotis wrote:

Hi Paul,
Thank you for your report. This is caused #1052002, which I had marked
as affects: wasmedge previously.


Sorry for not checking that, but because you marked it as affecting the 
*binary* package wasmedge, it doesn't show up looking for bugs in the 
source package wasmedge (that may be a bts bug). Because this is a FTBFS 
issue, I recommend you to mark it affects src:wasmedge instead of wasmedge.



I don't know how you'd like ot handle this w.r.t. the BTS, and testing
migrations. I'm inclined to just reassign/merge it to the bug above, but
I'll wait for your opinion first.


That's probably OK, I see you already did that.


Also, I'm not sure I understand how clang migrated to testing when it
introduced an autopkgtest regression in another package. Isn't
autopkgtest integration in britney supposed to prevent this kind of
thing from happening?


britney prevents this kind of things currently only for *direct* reverse 
(test) dependencies. In this case we have:


test/Depends: clang (from src:llvm-defaults) -> (Depends) clang-16

As I'm pretty sure you meant not clang, but one of the versioned clang 
packages, britney didn't see the breakage. There are multiple ways to 
improve this:
* britney should look at all transitive dependencies (we lack the 
resources and also not environmentally friendly)
* britney could be taught to translate (automatically or via 
configuration) "-defaults" packages to their real packages. This would 
be good for multiple ecosystems, patches welcome.
* Individual packages that are sensitive could use the 
`hint-testsuite-triggers` trick from the autopkgtest spec [1] and add 
the current real packages. That's a PITA to maintain though, and adding 
versions that you don't really test is wrong.


Paul

[1] 
https://salsa.debian.org/ci-team/autopkgtest/-/blob/master/doc/README.package-tests.rst


OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: fixed 1055255 in 1.95.0-1~bpo12+1

[Debian Bug Tracking System]

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

> fixed 1055255 1.95.0-1~bpo12+1
Bug #1055255 {Done: Andrej Shadura } 
[src:matrix-synapse] matrix-synapse: CVE-2023-43796
Marked as fixed in versions matrix-synapse/1.95.0-1~bpo12+1.
> thanks
Stopping processing here.

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