Your message dated Wed, 12 Nov 2025 23:49:37 +0000
with message-id <[email protected]>
and subject line Bug#1120569: fixed in ffc 2019.2.0~legacy20230509.35df986-6
has caused the Debian Bug report #1120569,
regarding test-ffc autopkgtest broken by pip 25.3
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1120569: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1120569
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: ffc
Version: 2019.2.0~legacy20230509.35df986-5
Severity: serious
Affects: python3-pip
Hi,
debian/tests/test-ffc uses pip to install ffc-factory for the tests. In
the current version in testing, this shows the fallowing warning:
> Building wheels for collected packages: fenics-ffc-factory
> DEPRECATION: Building 'fenics-ffc-factory' using the legacy setup.py
> bdist_wheel mechanism, which will be removed in a future version. pip 25.3
> will enforce this behaviour change. A possible replacement is to use the
> standardized build interface by setting the `--use-pep517` option, (possibly
> combined with `--no-build-isolation`), or adding a `pyproject.toml` file to
> the source tree of 'fenics-ffc-factory'. Discussion can be found at
> https://github.com/pypa/pip/issues/6334
With the latest version of pip in unstable (25.3), this now breaks (as
promised by the deprecation notice).
Explicitly specifying --use-pep517 should work. You'll need
--no-build-isolation too, to be able to do this without downloading code
from the Internet.
Stefano
--- End Message ---
--- Begin Message ---
Source: ffc
Source-Version: 2019.2.0~legacy20230509.35df986-6
Done: Drew Parsons <[email protected]>
We believe that the bug you reported is fixed in the latest version of
ffc, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Drew Parsons <[email protected]> (supplier of updated ffc 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 [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Thu, 13 Nov 2025 00:24:05 +0100
Source: ffc
Architecture: source
Version: 2019.2.0~legacy20230509.35df986-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
<[email protected]>
Changed-By: Drew Parsons <[email protected]>
Closes: 1120569
Changes:
ffc (2019.2.0~legacy20230509.35df986-6) unstable; urgency=medium
.
* debian/tests/test-ffc: install ffc-factory using pip 25.3 with options
--use-pep517 --no-build-isolation. Closes: #1120569.
Checksums-Sha1:
d58f48c01f605211a79f937dbd39409b7e18663f 2421
ffc_2019.2.0~legacy20230509.35df986-6.dsc
6af065bdc77d7463bce418a4dbbd6bfbc6d1b711 11680
ffc_2019.2.0~legacy20230509.35df986-6.debian.tar.xz
Checksums-Sha256:
50bf2d07ce6c89a98f326baccddab1a0eaced2bf7eacef9f4f732d5d4bb6a82b 2421
ffc_2019.2.0~legacy20230509.35df986-6.dsc
a949196f74ec4ede3d0984d3fa641f6bdd6d02155b263bea88acc1d67b8ba2d5 11680
ffc_2019.2.0~legacy20230509.35df986-6.debian.tar.xz
Files:
47685608cb5df7a165f47cbf3ede9137 2421 python optional
ffc_2019.2.0~legacy20230509.35df986-6.dsc
186f6f08fb2fa01ed31b14302dc99900 11680 python optional
ffc_2019.2.0~legacy20230509.35df986-6.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAmkVGMsACgkQVz7x5L1a
AfpbUQ//du7BV+6tAwolRr9xuZSkDgzDXJQlwaSAihfRUvevd/Vlrhy4bUZNa/NY
aunZE1sfeJEiIZgP9V7GhcDaQOV1PUEhOXAoW0anf+drI/KbGycwLRKM000RSDMN
EJoP/wwQRVIBzD/KRukfL9KWcEwOV4RxCbZSzzX1AyKf2ELfRyDsWHp4j078IkM4
3Kf58RwcjolGddAWGjb9mNPKeKR7NcT/LHxY01PKxUgwKsJGL3Ejg3m80z6/P2BZ
MgDYB0/ZKztz2AJKtTGQt05PEkGDhc4PvK1P6VsWzpTVsGpryUZemdwttTi33Xvb
scT4JUx482S7f1hq5x8sIiBmwH9xUbcWiNVPX2NFDLVwLxjQI2Hd2HgxYUwoftY+
fxC6zcvoSxq8WMMiK6rWe5qHleEuM3kFBgDoUFnkT17lauvg1TC5qjjzoqQUsGg8
Om1e48vUS4RXfOEuVZy5SUQSCdDHzytrwJH7wByESxLCiQWf6gIflex3rbXgB4p6
5ww4xYtSG+DzfEWfY2sVf090xiheBZWWvdBNITAB0hGc2B5BatOQJry1tFQgLY8S
G/pxyqlFAVxWbq3gvN1gpEzhkG3CiDRjiGf9DPpFyZIpxAW4bjaRJDN+diDOKLCh
7WQfCc6zVgKO9X18TPYjerFT9qF5pLIK+2K/mZF/lau39+gA3iM=
=DkSd
-----END PGP SIGNATURE-----
pgpmAZKfFp4su.pgp
Description: PGP signature
--- End Message ---
