Hello QuTiP roadmap thread =) the current state is that the ITPs were requested to WNPP* Bug#1101791: ITP: python-qutip-qip -- QuTiP package - Quantum Information Processing
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1101791
* Bug#1101792: ITP: python-qutip-qtrl -- QuTiP package - Quantum
Optimal Control
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1101792
* Bug#1101793: ITP: python-qutip-qoc -- QuTiP package - Advanced
Quantum Optimal Control
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1101793
* Bug#1101794: ITP: python-qutip -- QuTiP: Quantum Toolbox in Python
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1101794
These ITP´ed source packages will be provide the following binary
packages and versions:
* Trixie version needs to be (<< 5.1.1-50)
* Forky starts with python-qutip version 5.1.1-50
* Forky starts with a new source package `python-qutip` for binary
packages `python3-qutip` and `python-qutip-doc`.
----------------------------------------------------------------------
-- Trixie
source package version binary package
qutip 5.1.1-2+really4.7.5 python3-qutip
python-qutip-doc
----------------------------------------------------------------------
-- Forky
source package version binary package
python-qutip 5.1.1-50 python3-qutip
python-qutip-doc
python-qutip-qip 0.4.0 python3-qutip-qip
python-qutip-qip-doc
python-qutip-qtrl 0.1.5 python3-qutip-qtrl
python-qutip-qtrl-doc
python-qutip-qoc 0.1.1 python3-qutip-qoc
python-qutip-qoc-doc
----------------------------------------------------------------------
Means the upcoming Debian Trixie stable will include QuTiP version
4.7.5 in a single binary package. After the Trixie freeze is over we
will provide the new QuTiP ecosystem of version 5 for Debian Testing.
Also GPU accelerated JAX support is planned in the future.
Greets,
Dirk =)
On 3/4/25 7:19 PM, Dirk Lehmann wrote:
Dear Debian Science Maintainers,
I am beginning a Thread here in this mailing list related to
Bug#1098454
* https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098454
as I suppose it needs a more longer discussion or (depending on
activity) public status information.
I have read the 'Debian Python Policy' and I am familiar with the
'Debian Developers Reference' in the past. Currently I am reading the
'Debian Maintainers Guide' and try to become a Debian Maintainer to
solve the Bug#1098454 above itself.
**********************************************************************
* Faster solution
If someone needs it more faster to become solved then let us make a
parallel 'packaging race' xD ... Otherwise as workaround it is very
easy to check-out the not packaged sources via Git, i.e.
$> git clone https://github.com/qutip/qutip-qip
then `cd` into it and run in a shell
qutip-qip$> python3 setup.py build
then `cd` into your project-sources and soft-link the build into it
project/src$> ln -s ../../qutip-qip/build/lib/qutip_qip
Thats all. It exist inter-Qutip dependencies, keep track of it.
**********************************************************************
* My changed email
First if all
To become a Debian Maintainer I changed my email. My old email was
<support@dj-l.de> and currently I am working officially with
<debian@dj-l.de>, as soon as for commits <develop@dj-l.de>.
GPG: 0x904BC73A0B58FD1F41CAB3A8E2A3766F21F02BD5
@ keyserver.ubuntu.com
**********************************************************************
* Roadmap
My current plan is the following, I try to process as fast as
possible for (my) free(-time).
1. Reading the 'Debian Maintainers Guide' a bit more, until I feel
certain enough for maintaining.
2. In parallel I try to become the 'Debian Maintainer' status in the
NM process (key signing and so on).
3. The Python library QuTiP (python3-qutip) was split via a kind of
plugin-system into many splited projects with it's own
Git-repositories by the developers.
My plan is to map these plugins to Debian packages. Maybe
`python3-qutip-<plugin>` in compliance with the Debian Python
Policy.
The current packaged `python3-qutip` (version 5.1.1-1) just
contains the `core`. The reason is that the developers have
"out-sourced" the plugins into fresh repositories. Therefore, I
plan to make `python3-qutip` to a pure meta-package, which just
contain dependencies (see end of this roadmap).
I don't like to overspecify which QuTiP plugins are needed to be
packaged for now. I begin with `python3-qutip-core` and will see
which are required on-the-fly.
4. I will setup public Git repositories on my Salsa account at
* https://salsa.debian.org/users/dj-l/projects
and implement the packaging of the QuTiP packages, beginning with
`python3-qutip-core`.
5. Now it's time to have access as an Uploader and hopefully have
finished the NM process. To test the packages productive in
Debian Unstable.
Maybe that I'm wrong at this point, you are welcome for
false-feedback.
6. Wait until the packages are in Debian Testing and maybe for Bug
reports.
7. Remove all file contents from package `python3-qutip` and just set
dependencies, i.e. `python3-qutip-core`, `python3-qutip-qip`, ...,
to keep `python3-qutip` compatible to earlier Debian versions.
Current uploader: Drew Parsons <dparsons@debian.org>
I will link this thread to Bug#1098454
<https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098454>.
Greets, Dirk =)
Attachment:
OpenPGP_signature.asc
Description: OpenPGP digital signature