On 24/04/11 23:45, Mehdi Dogguy wrote:
> On 04/25/2011 12:17 AM, David Claughton wrote:
>>
>> OK, I've applied the patch to the git repo - looks good.  Thanks
>> again to you both.
>>
> 
> Thanks.
> 
> However, you might want to revert the other patch that turned
> "pyversions -s" into "pyversions -r". The former allows us to update the
> package by a simple binNMU while the latter forces source changes in the
> source package.
> 
> Regards,
> 

Hmm, I'm not sure I agree.  As we have just seen, graphviz requires
source changes anyway to support a new python version.  Surely all
"pyversions -s" does in this situation is guarantee that the binNMU will
fail, just as it did this time?

I left "pyversions -r" in as it seemed the better approach in this case.
 It should mean that transitions are smoother - an OCAML transition
shouldn't come to a grinding halt because a new python version has been
uploaded to the archive!

Cheers,

        David.




-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to