Your message dated Mon, 25 Aug 2025 10:47:34 +0000 with message-id <[email protected]> and subject line Bug#964130: Removed package(s) from unstable has caused the Debian Bug report #964130, regarding RM: pyqwt3d -- RoQA; leaf pkg; depends on sip4; dead upstream 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.) -- 964130: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964130 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Source: pyqwt3d Version: 0.1.8-5 Severity: important Usertags: sip5 Dear Maintainer, Recently I have updated pyqt5 and related packages to use sip5 instead of sip4 for build. This is in experimental for now, but I want to upload it to unstable in a month or two. This change breaks PyQt5 extension ABI, so all packages build-depending on pyqt5-dev need to build with sip5 too. Quick migration guide: 1) Build-depend on python3-sipbuild(-dbg) and sip5-tools. - Inspect pyproject.toml (if it exists) for additional dependencies, maybe you will need also python3-pyqtbuild. 2) If your package has a project.py file, call sip-build to build it. For separation of configure and build phases, pass --no-make to it. 3) If your package does not have a project.py file, but has a configure.py, update that file to the latest version of the boilerplate (v2.16), which you can find in the experimental version of qscintilla2 package. (Qscintilla2's configure.py used to be a recommended way to build sip projects.) 4) If your package called /usr/bin/sip directly, call /usr/bin/sip5 instead. 5) If your package had a runtime dependency on python3-sip or ${sip3:Depends}, depend on python3-pyqt5.sip instead. There is no analogue for dh_sip3 helper yet. (Upstream now recommends each project to use its own private copy of sip. In Debian, I recommend you to use pyqt5's copy which is python3-pyqt5.sip). 6) If you build a -dev package with .sip files, they are now installed into a new location (in dist-packages). Also .toml files now should be present. You can see what I have done in pyqt5, pyqt5chart, pyqt5webengine and qscintilla2 packages in experimental (see the relevant commits in git). The official documentation for sip5 is available online [1] or in sip5-doc package. For help you can ask me or pyqt/sip mailing list [2] (subscription needed to post messages). Please stage your changes in experimental (or in a VCS) for now. They will need to be uploaded to unstable together with pyqt5. [1]: https://www.riverbankcomputing.com/static/Docs/sip/ [2]: https://www.riverbankcomputing.com/mailman/listinfo/pyqt -- Dmitry Shachnev
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: pyqwt3d | 0.1.8-6 | source python-qwt3d-doc | 0.1.8-6 | all python3-qwt3d-qt5 | 0.1.8-6+b5 | riscv64 python3-qwt3d-qt5 | 0.1.8-6+b9 | amd64, i386, mips64el, ppc64el, s390x python3-qwt3d-qt5 | 0.1.8-6+b10 | arm64 ------------------- Reason ------------------- RoQA; leaf pkg; depends on sip4; dead upstream ---------------------------------------------- Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. Packages are usually not removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. The release team can force a removal from testing if it is really needed, please contact them if this should be the case. We try to close bugs which have been reported against this package automatically. But please check all old bugs, if they were closed correctly or should have been re-assigned to another package. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [email protected]. The full log for this bug can be viewed at https://bugs.debian.org/964130 This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing [email protected]. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)
--- End Message ---
