On 10/06/2015 05:26 PM, Ian Cordasco wrote:
> On Tue, Oct 6, 2015 at 8:53 AM, Jeremy Stanley wrote:
>> On 2015-10-06 09:28:56 +0200 (+0200), Thomas Goirand wrote:
>>> Master != kilo. It still means that I have to do all of the backport
>>> work by myself.
>> [...]
>>> I know that it's the common a
On Tue, Oct 6, 2015 at 8:53 AM, Jeremy Stanley wrote:
> On 2015-10-06 09:28:56 +0200 (+0200), Thomas Goirand wrote:
>> Master != kilo. It still means that I have to do all of the backport
>> work by myself.
> [...]
>> I know that it's the common assumption that, as the package maintainer
>> in Deb
On 2015-10-06 09:28:56 +0200 (+0200), Thomas Goirand wrote:
> Master != kilo. It still means that I have to do all of the backport
> work by myself.
[...]
> I know that it's the common assumption that, as the package maintainer
> in Debian, I should volunteer to fix any issue in the 6+ million line
On 10/06/2015 02:49 AM, Jeremy Stanley wrote:
> On 2015-10-05 23:45:57 +0200 (+0200), Thomas Goirand wrote:
> [...]
>> Upstream will *not* fix the issue, because you know, they "fixed" it in
>> their CI by adding an upper version bound in the pip requirements, which
>> is fine for them in the gate.
4 matches
Mail list logo