On 31/01/17 19:18, Laszlo Boszormenyi (GCS) wrote: > Package: release.debian.org > User: [email protected] > Usertags: unblock > > Hi Release Team, > > I don't want to hide that due to my mistake, pyro4 package migrated to > Stretch without the selectors34 dependency of python2-pyro4 even > packaged. It was only partly fixed with importing the selectors module > instead[1] - that fixes the client mode but the multiplexed server > still fails (the user have to change to the threadpool variant). > > I see the following solutions: > 1) Drop the python2 variant of Pyro4 and only ship the python3 one > (worst case). > 2) Allow the packaged selectors34 module[2] to Stretch (not yet > uploaded) as it's an one file module. > 3) Add the selectors34.py to the pyro4 package, debdiff to the Stretch > version is attached. > 4) Use the upstream commit not to fail with the import, but inform the > user to switch to the threadpool variant with a RuntimeError[3] > when using the Python 2 variant. > > Which solution would be allowed for Stretch?
bootstrap-vz depends on python2-pyro4, so we can't just drop it. I don't like 2, I'd rather add a new source than embed this inside pyro. Please upload selectors34 and I'll see about granting an exception to fix this RC bug. Cheers, Emilio
