Bug 343373 – Stabilize dev-libs/crypto++-5.6.1-r1

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Arfrever Frehtes Taifersar Arahesis (RETIRED) 2010-10-30 14:19:03 UTC]

Stabilize dev-libs/crypto++-5.6.1.

[Comment 1 Markos Chandras (RETIRED) 2010-10-31 12:46:38 UTC]

Created attachment 252667 [details]
build.log

Tests fail on amd64

[Comment 2 Markus Meier 2010-11-04 12:13:18 UTC]

(In reply to comment #1)
> Created an attachment (id=252667) [details]
> build.log
> 
> Tests fail on amd64

confirming here on amd64, it eats all memory and fails.

[Comment 3 Markus Meier 2010-11-04 12:38:21 UTC]

x86 stable

[Comment 4 Jeroen Roovers (RETIRED) 2010-11-04 20:00:29 UTC]

(In reply to comment #1)
> Created an attachment (id=252667) [details]
> build.log
> 
> Tests fail on amd64

What happened to filing new bugs?

Stable for HPPA.

[Comment 5 Brent Baude (RETIRED) 2010-12-27 21:41:50 UTC]

ppc64 stable

[Comment 6 Markos Chandras (RETIRED) 2010-12-29 16:25:46 UTC]

Tested again on new box. Same problem. Not stable for us. Please restrict test if you want to and call us again

[Comment 7 Tobias Klausmann (RETIRED) 2011-01-02 19:01:35 UTC]

Stable on alpha.

[Comment 8 Arfrever Frehtes Taifersar Arahesis (RETIRED) 2011-01-03 14:58:35 UTC]

(In reply to comment #7)
> Stable on alpha.

You haven't committed it.

[Comment 9 Zooko O'Whielacronx 2011-01-04 07:12:33 UTC]

The pycryptopp project has an issue ticket that is tracking this issue: http://tahoe-lafs.org/trac/pycryptopp/ticket/65

[Comment 10 Dane Smith (RETIRED) 2011-01-08 04:15:47 UTC]

AMD issues were fixed in -r1 since it changes installed binaries and it's only tests that fail. It will compile normally. 

I'd recommend that amd64 not stable this. That will keep stable users on a properly working version. The revbump will get people using ~amd64 onto a working version as well.

[Comment 11 Arfrever Frehtes Taifersar Arahesis (RETIRED) 2011-01-08 13:26:34 UTC]

The changes in 5.6.1-r1 are amd64-specific, so I have copied non-amd64 keywords from 5.6.1 to 5.6.1-r1.

Please continue stabilization of dev-libs/crypto++-5.6.1-r1.

[Comment 12 Agostino Sarubbo 2011-01-08 15:03:41 UTC]

(In reply to comment #11)
> Please continue stabilization of dev-libs/crypto++-5.6.1-r1.

Passed test.

amd64 ok. 

[Comment 13 Brent Baude (RETIRED) 2011-01-10 18:51:23 UTC]

ppc stable

[Comment 14 Markos Chandras (RETIRED) 2011-01-20 13:17:35 UTC]

amd64 done. Thanks Agostino

[Comment 15 David-Sarah Hopwood 2011-02-08 02:02:11 UTC]

(In reply to comment #9)
> The pycryptopp project has an issue ticket that is tracking this issue:
> http://tahoe-lafs.org/trac/pycryptopp/ticket/65

To avoid confusing anyone, that's almost certainly not the same bug. This
ticket matches the symptoms of the bug in
https://sourceforge.net/apps/trac/cryptopp/ticket/6 (which would make it a duplicate of gentoo bugs #322713 and #343169).

[Comment 16 David-Sarah Hopwood 2011-02-08 02:10:19 UTC]

(In reply to comment #10)
> AMD issues were fixed in -r1 since it changes installed binaries and it's only
> tests that fail. It will compile normally. 
> 
> I'd recommend that amd64 not stable this. That will keep stable users on a
> properly working version. The revbump will get people using ~amd64 onto a
> working version as well.

As far as I understand, this bug does not only affect tests, it just manifests most obviously in the SHA-1 test (although it is the Rijndael code that is wrong).

The upstream fix at http://sourceforge.net/apps/trac/cryptopp/attachment/ticket/6/rijndael.patch should be applied.

[Comment 17 Michael Weber (RETIRED) 2011-02-26 09:22:12 UTC]

sparc done

[Comment 18 Tobias Klausmann (RETIRED) 2011-02-27 11:29:57 UTC]

Stable on alpha.