Hello Drew =)
I don't think python-qutip-core-doc is necessary.There is already a python-qutip-doc package, and it's still the right place for the core docs.
You are right, there is one `-doc` too much. Hmmm, in my concept it would be better to drop `python-qutip-doc` as the last step of migration (see below) and instead mark
* python-qutip-core-doc Replaces: python-qutip-doc (<< 5.1.1-20) Conflicts: python-qutip-doc (<< 5.1.1-20)
You're proposing to simply rename the current python3-qutip to python3- qutip-core, right?You'd want to keep python3-qutip as a dependency package in any case, and the core docs are still relevant as python-qutip-doc
To migrate without having version issues, the idea is to implement the packages step by step. I will mark in `python3-qutip-core` like
* python3-qutip-core Replaces: python3-qutip (<< 5.1.1-20) Conflicts: python3-qutip (<< 5.1.1-20) So it should just possible to install one of them during migration.If I have finished the packaging in the last step we can make `python3-qutip` to a pure metapackage which
* python3-qutip Depends: python3-qutip-core Recommends: python3-qutip-{qip,qtrl,qoc}, Suggests: python-qutip-{qip,qtrl,qoc}-docThis should hopefully trigger `apt` to upgrade to the new packaging structure. We should do this if the Trixie freeze is over.
As last step it should be possible to drop `python3-qutip-doc` from the Debian archives.
********************************************************************** * For TrixieI think the best solution for Trixie is to rollback to 4.7.5-2 with a version scheme like
* python3-qutip 5.1.1-2+really4.7.5-2 I start the migration with version * python3-qutip-* 5.1.1-20This should not prevent the migration in unstable as I do not touch python3-qutip. During Trixie freeze I report a serious bug to every new package, so that these do not going into Debian Testing for Trixie.
That's the plan, Dirk =)
Attachment:
OpenPGP_signature.asc
Description: OpenPGP digital signature