On 02/12/16 06:40, Salvatore Bonaccorso wrote:
> Hi Emilio, Jonas, Antoine,
>
> Thanks for all feedback.
>
> On Thu, Dec 01, 2016 at 04:44:22PM +0100, Emilio Pozuelo Monfort wrote:
>> On 01/12/16 16:25, Jonas Meurer wrote:
>>> Hi Security and LTS folks,
>>>
>>> Am 01.12.2016 um 15:54 schrieb Salv
Hi Emilio, Jonas, Antoine,
Thanks for all feedback.
On Thu, Dec 01, 2016 at 04:44:22PM +0100, Emilio Pozuelo Monfort wrote:
> On 01/12/16 16:25, Jonas Meurer wrote:
> > Hi Security and LTS folks,
> >
> > Am 01.12.2016 um 15:54 schrieb Salvatore Bonaccorso:
> >> On Wed, Nov 30, 2016 at 04:05:20PM
On 2016-12-01 10:06:46, Antoine Beaupré wrote:
> On 2016-11-30 23:59:32, Guido Günther wrote:
>> I remember the nss testsuite to run cleanly last time I checked a couple
>> of months ago so we should IMHO investigate.
>
> It seems that there are a lot of failing tests regarding FIPS support:
>
> [1
Hi
This was the case when I run the tests last time. If I remenber correctly
FIPS had to be enabled with sysctl and even with that I couldn't make it
work.
After reading more about FIPS I concluded that this is likely something
that nobody uses, at least likely not on wheezy.
/ Ola
Sent from a
On 2016-12-01 10:25:58, Jonas Meurer wrote:
> Hi Security and LTS folks,
>
> Am 01.12.2016 um 15:54 schrieb Salvatore Bonaccorso:
>> On Wed, Nov 30, 2016 at 04:05:20PM -0500, Antoine Beaupré wrote:
>>> +nss (2:3.26.2-1+debu7u1) UNRELEASED; urgency=high
>>> +
>>> + * Non-maintainer upload by the LT
On 01/12/16 16:25, Jonas Meurer wrote:
> Hi Security and LTS folks,
>
> Am 01.12.2016 um 15:54 schrieb Salvatore Bonaccorso:
>> On Wed, Nov 30, 2016 at 04:05:20PM -0500, Antoine Beaupré wrote:
>>> +nss (2:3.26.2-1+debu7u1) UNRELEASED; urgency=high
>>> +
>>> + * Non-maintainer upload by the LTS Se
Hi Security and LTS folks,
Am 01.12.2016 um 15:54 schrieb Salvatore Bonaccorso:
> On Wed, Nov 30, 2016 at 04:05:20PM -0500, Antoine Beaupré wrote:
>> +nss (2:3.26.2-1+debu7u1) UNRELEASED; urgency=high
>> +
>> + * Non-maintainer upload by the LTS Security Team.
>> + * New upstream release to fix
On 2016-11-30 23:59:32, Guido Günther wrote:
> I remember the nss testsuite to run cleanly last time I checked a couple
> of months ago so we should IMHO investigate.
It seems that there are a lot of failing tests regarding FIPS support:
[1034]anarcat@angela:nss-3.26.2$ grep 'FAILED$'
/var/cache
On 2016-12-01 09:54:44, Salvatore Bonaccorso wrote:
> Hi Antoine,
>
> On Wed, Nov 30, 2016 at 04:05:20PM -0500, Antoine Beaupré wrote:
>> +nss (2:3.26.2-1+debu7u1) UNRELEASED; urgency=high
>> +
>> + * Non-maintainer upload by the LTS Security Team.
>> + * New upstream release to fix CVE-2016-9074
Hi Antoine,
On Wed, Nov 30, 2016 at 04:05:20PM -0500, Antoine Beaupré wrote:
> +nss (2:3.26.2-1+debu7u1) UNRELEASED; urgency=high
> +
> + * Non-maintainer upload by the LTS Security Team.
> + * New upstream release to fix CVE-2016-9074
Depending on what is done this should be either 2:3.26.2-0+
On 2016-12-01 02:44:44, Ola Lundqvist wrote:
> Hi
>
> In LTS the hook is available in debian/rules but commented. The number
> of failed test cases seems to be the same as I remember from when I
> had to disable it.
Sorry, which hook?
The only dh_auto_test target I could find was in some obscure
On 2016-11-30 23:59:32, Guido Günther wrote:
> Hi Antoine,
> On Wed, Nov 30, 2016 at 11:03:39PM -0500, Antoine Beaupré wrote:
>> On 2016-11-30 16:46:17, Ola Lundqvist wrote:
>> > Hi
>> >
>> > There were no test suite before the update so I could not tell if it was a
>> > regression or not.
>>
>> I
Hi
In LTS the hook is available in debian/rules but commented. The number
of failed test cases seems to be the same as I remember from when I
had to disable it.
// Ola
On 1 December 2016 at 05:59, Guido Günther wrote:
> Hi Antoine,
> On Wed, Nov 30, 2016 at 11:03:39PM -0500, Antoine Beaupré wro
Hi Antoine,
On Wed, Nov 30, 2016 at 11:03:39PM -0500, Antoine Beaupré wrote:
> On 2016-11-30 16:46:17, Ola Lundqvist wrote:
> > Hi
> >
> > There were no test suite before the update so I could not tell if it was a
> > regression or not.
>
> I just figured out how to hook up the test suite, and it
On 2016-11-30 16:46:17, Ola Lundqvist wrote:
> Hi
>
> There were no test suite before the update so I could not tell if it was a
> regression or not.
I just figured out how to hook up the test suite, and it fails:
Tests summary:
--
Passed: 8282
Failed: 17
Faile
On 2016-11-30 16:46:17, Ola Lundqvist wrote:
> Hi
>
> There were no test suite before the update so I could not tell if it was a
> regression or not.
Ah, I see! Thanks for the updates, I'll see if i can fix the test
suite for a while otherwise I'll just stick with this...
A.
--
Drowning people
Hi
There were no test suite before the update so I could not tell if it was a
regression or not.
/ Ola
Sent from a phone
Den 30 nov 2016 22:27 skrev "Antoine Beaupré" :
> On 2016-11-30 16:17:50, Ola Lundqvist wrote:
> > Hi Antoine
> >
> > I do not find it strange (as I was one of the two that
On 2016-11-30 16:17:50, Ola Lundqvist wrote:
> Hi Antoine
>
> I do not find it strange (as I was one of the two that did it). You
> are supposed to keep the changelog as far as I know. I mirrored the
> changes in stable/jessie. I never checked the unstable version (I do
> not think I did at least).
Hi Antoine
I do not find it strange (as I was one of the two that did it). You
are supposed to keep the changelog as far as I know. I mirrored the
changes in stable/jessie. I never checked the unstable version (I do
not think I did at least).
However the resulting package was the same (as jessie
I have looked at updating the nss package in wheezy to cover for a new
security issue that came up. The package is ready for testing in:
https://people.debian.org/~anarcat/debian/wheezy-lts/
The diff between the upstream 2.26.2 release and the 2.26 release in
wheezy is fairly small, so I felt it
20 matches
Mail list logo
