Quoting Barry Warsaw :
I'd love to know if there's a Debian-wide policy on such things. E.g. if
"opt-out with informed user consent" was an official policy that we could
clearly point to and reference, it would greatly help provide
guidance to both
Debian maintainers and upstreams.
In the i
On Monday, November 07, 2016 10:08:25 AM Barry Warsaw wrote:
> On Nov 07, 2016, at 11:44 AM, Thomas Goirand wrote:
> >So, I don't agree with you, and believe that gradually using
> >#!/usr/bin/python2 is a good approach to the transition. IMO, that's
> >what we should start doing as much as possibl
On Nov 07, 2016, at 11:44 AM, Thomas Goirand wrote:
>So, I don't agree with you, and believe that gradually using
>#!/usr/bin/python2 is a good approach to the transition. IMO, that's
>what we should start doing as much as possible.
>
>If the dependencies for Python itself aren't calculated well w
On Nov 07, 2016, at 01:21 PM, Brian May wrote:
>Should I ask on debian-devel?
I think you should, and I'll be very interested in that discussion.
Several packages in our team already apply deltas to upstream to disable
certain amounts of information gathering and reporting. The most common
exa
On 11/01/2016 11:03 PM, Scott Kitterman wrote:
> On Tuesday, November 01, 2016 05:14:21 PM Barry Warsaw wrote:
>> On Nov 01, 2016, at 11:34 AM, Scott Kitterman wrote:
>>> I don't think /usr/bin/python should ever point to a python3 version. It
>>> should be dropped when python2.7 is removed. I th
5 matches
Mail list logo
