Your message dated Sat, 28 Feb 2026 22:20:48 +0100
with message-id <[email protected]>
and subject line Re: Bug#1127353: transition: nanobind
has caused the Debian Bug report #1123044,
regarding transition: nanobind
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.)
--
1123044: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1123044
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: [email protected], [email protected]
Control: affects -1 + src:nanobind
User: [email protected]
Usertags: transition
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Dear Release Team,
I would like to transition the nanobind package after an ABI bump.
I expect this to run smoothly as the necessary work to make all reverse
dependencies properly depend on the virtual ABI package has been done
for the previous transition [1].
Ben file:
title = "nanobind ABI 17";
is_affected = .depends ~ /\bpython3-nanobind\b/ | .depends ~
/\bpython3-nanobind-abi[0-9]+\b/ | .provides ~ /\bpython3-nanobind-abi[0-9]+\b/;
is_good = .depends ~ /\bpython3-nanobind-abi17\b/ | .provides ~
/\bpython3-nanobind-abi17\b/;
is_bad = .depends ~ /\bpython3-nanobind-abi16\b/ | .provides ~
/\bpython3-nanobind-abi16\b/;
Cheers
Timo
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1111004
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEmwPruYMA35fCsSO/zIxr3RQD9MoFAmlBOLAACgkQzIxr3RQD
9MqA4w/5Ac8EDJPMr3ZzvehJtM4r36ckOX8q0lz827OcK4X7i1dn3cG5cZz0hX2D
/Fr2eOjbpwbaYRGBaGiqorbZR2NyTvYiJQR6QHCJP5wTisaJzNTJDhUzc5Ifb/eC
wDYSPDnKBy0ZlA4CPzWmruCvsniJwmnA4jX+7b0wgTUqWblh6nYmyoCci7514fDb
H8tyRw4xJi6FuNuQx1/lwfZntLzcXYw/5oy9YIpCI8hR5S6YFaBbBEW+XzksLseO
CaWYZkn5Z9F5rzfIxkmbOX6LFY54EftiomDCTxl35TqzwP4Y+Au+r8BYTD3ZEjSX
RGdp6hDZHiLEGkl8zYgI1oAwHxAZW6Kp+Z4HCvymJHvXQuwStMHHKzb4LyfQ0cKW
7nCmgDdG0PutZGLLFqVV7+kJw5GHl1LDaIRRTFzCEb/dIqnzI68ZXW8rAsg8hk0l
BJJlyV6ezxPqrSRagVAJRpJDDqe4lsLyIA4hXVVz5T/f1lUAunTrlF98dubsox+R
1QVq5El4pyzzUqHbuDfmuBP5f36ScHHwBaJhKy49viPI+w9uqLqPIJt/D1ImM2On
bCvaCXAHcNb5NXd2YlpD/JWC5ACvFVGmwj7GJPV34FyHSiwY8FZ5Zx5mp5iwyYQ8
QvRelohs5C6tfn0mATrVf5HnnRHAEXiw6EE1COKiJc2xcCPOLrs=
=Z5jX
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
On 2026-02-09 09:53:18 +0100, Emilio Pozuelo Monfort wrote:
> Control: tags -1 confirmed
>
> On 07/02/2026 12:26, Timo Röhling wrote:
> > Package: release.debian.org
> > Severity: normal
> > X-Debbugs-Cc: [email protected], [email protected]
> > Control: affects -1 + src:nanobind
> > User: [email protected]
> > Usertags: transition
> >
> > Dear Release team,
> >
> > the nanobind package has had another ABI bump and requires
> > transitioning. The previous transition bug ist still open [1], but
> > AFAICT that transition has been done for a while already.
> > I'm cc'ing the FEniCS maintainers because they are the primary
> > downstream users of nanobind. The nanobind changes are mostly internal
> > and do not affect API compatibility.
>
> Assuming the rdeps build against the new version: please go ahead.
The old binaries got removed from testing. Closing
Cheers
--
Sebastian Ramacher
--- End Message ---
