Bug#917037: ITP: python3-zeroconf -- Pure Python implementation of multicast DNS service discovery (Python3)
On Fri, 21 Dec 2018 at 21:59:46 +0100, Ruben Undheim wrote: > python-zeroconf already exists in the Debian archive. However, upstream has > dropped support for Python 2, and there are reverse dependencies in Debian > which depend on the Python 2 package. This makes it necessary with a separate > source package for the Python 3 version. See also #894809 (which you could close in the upload of python3-zeroconf, or mark as a duplicate of this ITP). I had assumed that you'd want to close #894809 without a new source package, since the only remaining rdep of python-zeroconf is pulseaudio-dlna (#894806); but a new source package also seems fine as a solution, and you have to go through the NEW queue either way. smcv
Bug#917037: ITP: python3-zeroconf -- Pure Python implementation of multicast DNS service discovery (Python3)
Quoting Ruben Undheim (2018-12-22 09:35:44) > Hi Jonas, > > > Feels wrong to me to add a new source package, when reason is that the > > current/old source package is abandoned upstream! > > Yes, it may sound a bit strange, but the same has been done for other > packages (https://bugs.debian.org/911453). I think it is the most > straightforward way to go if we really need to keep the Python2 > version while including the newest (python 3-only) upstream version. > But I agree it can be argued if we really need to keep the Python2 > version. Question is if we should include unmaintained project forks in stable. What you do with this ITP is essentially forking an upstream project, and I object to that, arguing that you/we should instead _maintain_ the existing package we already have for that upstream project. There might be situations where it makes sense to take over maintenance of an upstream-abandoned fork of a (previously) upstream project. Perfectly fine with me if you tell me that this is such case - but then please elaborate on the plans for the existing python-zeroconf package. > > A quick look seems to indicate these two reverse dependencies: > > > > * pulseaudio-dlna > > * python-pychromecast > > python-pychromecast has already been removed from Debian (source > package), so the only problem is "pulseaudio-dlna". > > > Neither of those seem to have a bugreport warning that > > python-zeroconf is unmaintained upstream. > > pulseaudio-dlna has this bug report https://bugs.debian.org/894806 > filed in April which blocks https://bugs.debian.org/894809. > python-zeroconf was removed from the source package in October. Ah, my look-up-bts skills are clearly inferior to yours :-) > > They seem to both a) have no reverse dependencies themselves, and b) > > having similar features as python3-pychromecast which uses > > python3-zeroconf. > > > > It seems best to me to try get those few packages to either use a > > maintained library or maybe avoid shipping them with Buster. > > I think you are right in that it is better to patch pulseaudio-dlna to > run in Python 3, but I am unsure how tricky it is because it has quite > a few Python dependencies. I have not checked yet if they are all > available for Python 3. > > > Could you please file bugreports appropriately? > > Do you perhaps mean raising the severity of #894806? Yes, now that you opened my eyes, that is what I mean :-) - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#917037: ITP: python3-zeroconf -- Pure Python implementation of multicast DNS service discovery (Python3)
Hi Jonas, > Feels wrong to me to add a new source package, when reason is that the > current/old source package is abandoned upstream! Yes, it may sound a bit strange, but the same has been done for other packages (https://bugs.debian.org/911453). I think it is the most straightforward way to go if we really need to keep the Python2 version while including the newest (python 3-only) upstream version. But I agree it can be argued if we really need to keep the Python2 version. > A quick look seems to indicate these two reverse dependencies: > > * pulseaudio-dlna > * python-pychromecast python-pychromecast has already been removed from Debian (source package), so the only problem is "pulseaudio-dlna". > Neither of those seem to have a bugreport warning that python-zeroconf > is unmaintained upstream. pulseaudio-dlna has this bug report https://bugs.debian.org/894806 filed in April which blocks https://bugs.debian.org/894809. python-zeroconf was removed from the source package in October. > They seem to both a) have no reverse > dependencies themselves, and b) having similar features as > python3-pychromecast which uses python3-zeroconf. > > It seems best to me to try get those few packages to either use a > maintained library or maybe avoid shipping them with Buster. I think you are right in that it is better to patch pulseaudio-dlna to run in Python 3, but I am unsure how tricky it is because it has quite a few Python dependencies. I have not checked yet if they are all available for Python 3. > Could you please file bugreports appropriately? Do you perhaps mean raising the severity of #894806? Best regards, Ruben
Bug#917037: ITP: python3-zeroconf -- Pure Python implementation of multicast DNS service discovery (Python3)
Quoting Ruben Undheim (2018-12-21 21:59:46) > python-zeroconf already exists in the Debian archive. However, > upstream has dropped support for Python 2, and there are reverse > dependencies in Debian which depend on the Python 2 package. This > makes it necessary with a separate source package for the Python 3 > version. Feels wrong to me to add a new source package, when reason is that the current/old source package is abandoned upstream! A quick look seems to indicate these two reverse dependencies: * pulseaudio-dlna * python-pychromecast Neither of those seem to have a bugreport warning that python-zeroconf is unmaintained upstream. They seem to both a) have no reverse dependencies themselves, and b) having similar features as python3-pychromecast which uses python3-zeroconf. It seems best to me to try get those few packages to either use a maintained library or maybe avoid shipping them with Buster. Could you please file bugreports appropriately? - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#917037: ITP: python3-zeroconf -- Pure Python implementation of multicast DNS service discovery (Python3)
Package: wnpp Severity: wishlist Owner: Ruben Undheim * Package name: python3-zeroconf Version : 0.21.3 Upstream Author : Jakub Stasiak * URL : https://github.com/jstasiak/python-zeroconf * License : LGPL-2.1+ Programming Lang: Python-3 Description : Pure Python implementation of multicast DNS service discovery (Python3) python-zeroconf already exists in the Debian archive. However, upstream has dropped support for Python 2, and there are reverse dependencies in Debian which depend on the Python 2 package. This makes it necessary with a separate source package for the Python 3 version. See https://tracker.debian.org/pkg/python-zeroconf for more infor about python-zeroconf.
