Hi Thomas! On Thu, Apr 06, 2017 at 05:49:15PM +0200, Thomas Goirand wrote: > Hi Sandro and others, > > Sandro Tosi has left python-cassandra-driver in a bad state, which leads > me to attempt to salvage it before it's too late. No harsh feeling, this > happened to everyone of us, and we can all be busy. Though something > must be done. Indeed, python-cassandra-driver suffers from #857298, > which is an RC bug that will lead to AUTORM in 16 days. This will also > remove openstack-trove, which I would like to avoid. > > As I don't want to repeat history and get a flame war started by an NMU, > I'm in advance of a possible NMU upload, sharing the debdiff with the > debian-python list. If Sandro agrees, or if there's a consensus in this > list that it's appropriate, I'll NMU. Best would be if Sandro himself > fixes the issue though. > > Attached is the debdiff. As you can see, I'm attempting to use the new > system that creates -dbgsym, and transitioning to it. Of course, for > this to happen, we will need the FTP masters to approve such change in a > timely manner, and likewise with the release team unblock. If someone > believe he has a better approach, let me know, though what I did is > probably the safest way to fix #857298. To be honest, I do not like your patch. The -dbg package currently contains not only debug symbols, but also the C extensions built for debug Python interpreter. And you are removing them even on the platforms where they are successfully built. In my opinion a better solution (for Stretch) would be just adding an Architecture: field to the -dbg packages (and for Buster, porting the code to support big endian architectures). Also, even if you really wanted to switch to -dbgsym, there is no need to keep the old -dbg packages for transition. You could use --dbgsym-migration option of dh_strip instead. -- Dmitry Shachnev
Attachment:
signature.asc
Description: PGP signature