Bug#936777: k3d: Python2 removal in sid/bullseye
Hi, On Sun, 10 Apr 2022 at 22:04, Moritz Mühlenhoff wrote: > > Revisiting this two years later; I really think k3d should be removed now? > Nothing changed upstream and at this point it's uninstallable in unstable > for many other libraries besides Python 2: > > - > The following packages have unmet dependencies: > k3d : Depends: libboost-program-options1.67.0 but it is not installable >Depends: libboost-python1.67.0 but it is not installable >Depends: libboost-regex1.67.0 (>= 1.67.0-10) but it is not installable >Depends: libcgal13 but it is not installable >Depends: libopenexr24 (>= 2.3.0) but it is not installable > E: Unable to correct problems, you have held broken packages. > - Indeed, I paid attention to your other bug report (sorry but I hadn't seen this yet, terrible months for me and huge backlog) and sent the necessary incantations to control@ to ask for removal, I hope. If upstream keeps inactive there's not much that we can do at this point. Thanks for keeping an eye on this! -- Manuel A. Fernandez Montecelo
Bug#936777: k3d: Python2 removal in sid/bullseye
Hi Manuel, > > Given upstream's reply at https://github.com/K-3D/k3d/issues/38 this > > seems unlikely to get ported, let's remove k3d? > > Basically I'd like to extend its life in Debian and keep users using > this package rather than having to build the version themselves, as > long as it doesn't become a big burden for Debian -- when it does > sure, let's drop it, and if the moment is now, so be it. > > This package is in a bad situation with Python2 and GTK dependencies, > but this is not the kind of application like a media player or similar > for which there are a gazillion alternatives with more or less the > same features -- this is a pretty specialized piece of software and > migration to some other tool can be a huge undertaking and might not > always be possible. > > If the relevant Python2 packages are going to be removed imminently, > that's OK, we can remove it now. And in any case, this package should > prevent the removal of Python2 if it's one of the last dependencies. > > But if Python2 it's to be held for a few months/years because other > important/popular packages are not migrated yet (gnat-gps, kodi?), and > even if only to keep it for unstable, I'd prefer to remove this > package only when Python2 is removed. Revisiting this two years later; I really think k3d should be removed now? Nothing changed upstream and at this point it's uninstallable in unstable for many other libraries besides Python 2: - The following packages have unmet dependencies: k3d : Depends: libboost-program-options1.67.0 but it is not installable Depends: libboost-python1.67.0 but it is not installable Depends: libboost-regex1.67.0 (>= 1.67.0-10) but it is not installable Depends: libcgal13 but it is not installable Depends: libopenexr24 (>= 2.3.0) but it is not installable E: Unable to correct problems, you have held broken packages. - Maybe it's better to ship such a proven, but no longer updated to current tooling package as a Flatpak on Flathub? Cheers, Moritz
Bug#936777: k3d: Python2 removal in sid/bullseye
Hi! Em 26 de mai. de 2020 às 20:43, Moritz Mühlenhoff escreveu: > > On Wed, Sep 04, 2019 at 12:10:39AM +0200, Manuel A. Fernandez Montecelo wrote: > > Control: forwarded -1 https://github.com/K-3D/k3d/issues/38 > > > > Thanks for the report. Asking upstream about their plans and best > > course of action. > > Given upstream's reply at https://github.com/K-3D/k3d/issues/38 this > seems unlikely to get ported, let's remove k3d? Basically I'd like to extend its life in Debian and keep users using this package rather than having to build the version themselves, as long as it doesn't become a big burden for Debian -- when it does sure, let's drop it, and if the moment is now, so be it. This package is in a bad situation with Python2 and GTK dependencies, but this is not the kind of application like a media player or similar for which there are a gazillion alternatives with more or less the same features -- this is a pretty specialized piece of software and migration to some other tool can be a huge undertaking and might not always be possible. If the relevant Python2 packages are going to be removed imminently, that's OK, we can remove it now. And in any case, this package should prevent the removal of Python2 if it's one of the last dependencies. But if Python2 it's to be held for a few months/years because other important/popular packages are not migrated yet (gnat-gps, kodi?), and even if only to keep it for unstable, I'd prefer to remove this package only when Python2 is removed. Cheers and thanks for your work. -- Manuel A. Fernandez Montecelo
Bug#936777: k3d: Python2 removal in sid/bullseye
On Wed, Sep 04, 2019 at 12:10:39AM +0200, Manuel A. Fernandez Montecelo wrote: > Control: forwarded -1 https://github.com/K-3D/k3d/issues/38 > > Thanks for the report. Asking upstream about their plans and best > course of action. Given upstream's reply at https://github.com/K-3D/k3d/issues/38 this seems unlikely to get ported, let's remove k3d? Cheers, Moritz
