Hi Thomas,
> Thanks to both of you Chris and Guido!
No problem. Packages available now and I've just announced DLA 773-4.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org / chris-lamb.co.uk
`-
Thanks to both of you Chris and Guido!
Cheers!
Thomas
2017-01-09 23:16 GMT+01:00 Chris Lamb :
> Guido Günther wrote:
>
>> I think the rule (as I understood it) is "every change to *-security"
>> gets a D{S,L}A so people know why things are changing in these suites.
>
> Yeah, that makes sense. I w
Guido Günther wrote:
> I think the rule (as I understood it) is "every change to *-security"
> gets a D{S,L}A so people know why things are changing in these suites.
Yeah, that makes sense. I was perhaps thinking there might be another
approach. :)
I've just uploaded python-crypto_2.6-4+deb7u7_a
On Mon, Jan 09, 2017 at 08:40:31PM +, Chris Lamb wrote:
> Guido Günther wrote:
>
> > Flake8 does the same internally what the test does (using the
> > multiprocess module):
>
> Getcha, okay. So, yet another python-crypto upload will be needed? *grin*
>
> Now, would it warrant a DLA announcem
Guido Günther wrote:
> Flake8 does the same internally what the test does (using the
> multiprocess module):
Getcha, okay. So, yet another python-crypto upload will be needed? *grin*
Now, would it warrant a DLA announcement? It seems noisy to announce
simply fixing the testsuite to work under no
On Mon, Jan 09, 2017 at 07:52:58PM +, Chris Lamb wrote:
> Guido Günther wrote:
>
> > I had the same problem with flake8 in gbp and used
> >
> > flake8 -j1
> >
> > to work around this. I think we can only skip the patch if hitting a
> > EPERM.
>
> I'm a little confused by the mention of
Guido Günther wrote:
> I had the same problem with flake8 in gbp and used
>
> flake8 -j1
>
> to work around this. I think we can only skip the patch if hitting a
> EPERM.
I'm a little confused by the mention of flake8 here - the test itself
is requiring access to the multiprocessing library
On Mon, Jan 09, 2017 at 05:02:06PM +, Chris Lamb wrote:
> Hi Thomas,
>
> > Still no update available for [python-crypto] versions 2.6-4+deb7u6 also
> > (for others archs than amd64).
> >
> > I tried to build 2.6-4+deb7u6 on i386 and it worked so maybe
> > autobuilders doesn't know that there
Hi Thomas,
> Still no update available for [python-crypto] versions 2.6-4+deb7u6 also
> (for others archs than amd64).
>
> I tried to build 2.6-4+deb7u6 on i386 and it worked so maybe
> autobuilders doesn't know that there is a new version of python-crypto
> ?
It seems like the tests are failing
