<quote who="Thomas Goirand" date="Tue, Mar 18, 2014 at 08:16:13AM +0800"> > Best is simply to upgrade to the latest upstream release: it fixes > it.
OK. Sounds fine. > > In terms of #738327, I'm not wild about gutting CDBS and essentially > > redoing the package because you're not familiar with how to handle > > Python3 support. I don't love the idea of NMUs that redo the entire > > package because the person doing the NMU is not familiar with the > > packaging software used. It seems like to a lot to change to a > > relatively simple and stable package for something that is likely > > unnecessary. > > Sure, I understand, and agree. I was merely proposing a way to do > things. But also, please keep in mind that python-support is deprecated, > and one way or another, you must change the package to get away from it. > Switching to dh_python2 is what everyone recommends these days. Does > CDBS support python3, and is there ways to do CDBS *without* using > python-support? I'll take a look. I'm not /opposed/ to switching to dh_python2 in general, I just think it's overkill to fix that one bug. I'm not so attached to CDBS that I will refuse to switch away. :) Later, Mako -- Benjamin Mako Hill http://mako.cc/ Creativity can be a social contribution, but only in so far as society is free to use the results. --GNU Manifesto
signature.asc
Description: Digital signature
