Your message dated Sat, 06 Apr 2024 10:00:11 +0000
with message-id <[email protected]>
and subject line Bug#1067085: fixed in nanobind 1.9.2-2
has caused the Debian Bug report #1067085,
regarding nanobind-dev not in python path and without distribution info
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.)


-- 
1067085: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067085
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: nanobind-dev
Version: 1.9.2-1
Severity: normal
X-Debbugs-Cc: [email protected], [email protected]

Dear Maintainer,

I would like to ask two questions related on usage of nanobind-dev from
python:

1) The user guide at 
https://nanobind.readthedocs.io/en/latest/building.html#finding-nanobind
states that the downstream user should query
python3 -m nanobind --cmake_dir
to determine where nanobind is installed. However, this is not currently
possible with nanobind-dev, since the file __init__.py is not installed
among the standard python paths. To make this work, one has to use
PYTHONPATH=/usr/share python3 -m nanobind --cmake_dir

2) Downstream users or packages may have a pyproject.toml file which
contains
============
[build-system]
requires = ["nanobind"]
============
When building with --no-build-isolation, this requires the
nanobind-*.dist-info folder to be present. Currently either
pip3 show nanobind
or
PYTHONPATH=/usr/share pip3 show nanobind
show
WARNING: Package(s) not found: nanobind
while nanobind installed from pypi.org would show something like
============
Name: nanobind
Version: 1.9.2
Summary: nanobind: tiny and efficient C++/Python bindings
Home-page: https://github.com/wjakob/nanobind
Author: Wenzel Jakob
Author-email: [email protected]
License: BSD
Location: /usr/local/lib/python3.11/dist-packages
Requires:
Required-by:
=============
The next version of fenics-dolfinx, to be packaged in Debian upon
release, will require --no-build-isolation and nanobind.

Thanks,
Francesco





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

Kernel: Linux 6.6.15-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect

Versions of packages nanobind-dev depends on:
ii  libeigen3-dev  3.4.0-4
ii  robin-map-dev  1.2.1-1

nanobind-dev recommends no packages.

nanobind-dev suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Source: nanobind
Source-Version: 1.9.2-2
Done: Timo Röhling <[email protected]>

We believe that the bug you reported is fixed in the latest version of
nanobind, 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.
Timo Röhling <[email protected]> (supplier of updated nanobind 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: Sat, 06 Apr 2024 01:33:25 +0200
Source: nanobind
Binary: nanobind-dev python3-nanobind
Architecture: source all
Version: 1.9.2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team <[email protected]>
Changed-By: Timo Röhling <[email protected]>
Description:
 nanobind-dev - Tiny and efficient C++/Python bindings (development files)
 python3-nanobind - Tiny and efficient C++/Python bindings (Python 3 module)
Closes: 1067085
Changes:
 nanobind (1.9.2-2) unstable; urgency=medium
 .
   * Ship public nanobind module (Closes: #1067085)
Checksums-Sha1:
 91694806f1b6bbdc114f9205c81c6a47fc3d11e7 2741 nanobind_1.9.2-2.dsc
 c3c982c5f4ff7afc4d48229e39c9a83522412d6b 3676 nanobind_1.9.2-2.debian.tar.xz
 895f0fe4cc70d47ce53b51531887f9c89a4cb8c2 122724 nanobind-dev_1.9.2-2_all.deb
 b3f74fd30f4d0d1144d0c354233f8777f9815f5b 8802 nanobind_1.9.2-2_amd64.buildinfo
 14725a76c3f392a1a3dbff710ccf24d690a77674 19660 python3-nanobind_1.9.2-2_all.deb
Checksums-Sha256:
 7b66e918480cce2b5bd57d9139c9522ceaeca8c699b41609a44ba030b260b717 2741 
nanobind_1.9.2-2.dsc
 4fa4d4905b6bbf549ca52df6863dfdea5fee6f93ba8dbe86e9715917297e9399 3676 
nanobind_1.9.2-2.debian.tar.xz
 19f2ebdfc7cc67e6b5afeeacf3f9efb011998aa040035d5ac9d0ef5cb5d313e0 122724 
nanobind-dev_1.9.2-2_all.deb
 49bad88ab2c3c961e6f76c90874db56674b38e6c6bb0342e62997aac56801f2d 8802 
nanobind_1.9.2-2_amd64.buildinfo
 132f4b4c95c479f9acaa42862d815a498d5a6d52abf1eb3a2c66e982c99af364 19660 
python3-nanobind_1.9.2-2_all.deb
Files:
 c40a075492ff8ddfaf0fd7388e9af039 2741 python optional nanobind_1.9.2-2.dsc
 63dab2e596545aed56eeb4ef24fddf0f 3676 python optional 
nanobind_1.9.2-2.debian.tar.xz
 7f2cca4be610f4ca5c4d47694b84e150 122724 python optional 
nanobind-dev_1.9.2-2_all.deb
 6085e26b8b884b7425124d00629cead5 8802 python optional 
nanobind_1.9.2-2_amd64.buildinfo
 90d783444ba77fc000bfdf7883f198b6 19660 python optional 
python3-nanobind_1.9.2-2_all.deb

-----BEGIN PGP SIGNATURE-----

iQHIBAEBCgAyFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmYQjGAUHHJvZWhsaW5n
QGRlYmlhbi5vcmcACgkQ+C8H+466LVkokwwAjqudBoOVZlZTZyLHQ32nYZWcP+em
8lehE24JcshaRGd4yJkWUAYl/HW+gTem0pEwhA9LZF8rwCDuVohVKoIhMldnnXUt
xU1DClRRN1PxFxEI6i37xtwvSHq/TDrcnnbtcn8ofKzJysUOoksAXOFG5fPNgEtw
WUE0mWSvXFQqjradBL6whQBQCYTR5SxHu6eI1R71v38bHvHYhZp6E07bg3vmrFsA
NRgmUsTubJ3ldvziCHKsBz1FMZ1m4fgfFvy9F9wt1qO4CPhNmSdwyjsWSoVNzddN
MzjJgscPXd3x6Hu95kJcUWtZ+XuikwxyuiH47qjr1P3BUrD7wc+/fqh89pvxNOzm
PPwNQaIuXRi9RY6EjqtZcRKQ3jxXNQ4oOlj7HaTARUHOk4T+s/h2FVyt/+BaO0ew
ORBWMAbusEmDj+nQKmtDEcLk1MACyQjjKzFRhELUnfZ52Re1yb9xPB27wJVkzThY
g292jakd7uiQtjZTofAIaOA2Ljj2F2iCiQpQ
=wUJK
-----END PGP SIGNATURE-----

Attachment: pgpAzKsf6fXqO.pgp
Description: PGP signature


--- End Message ---

Reply via email to