python-m2crypto-native broken

python-m2crypto-native broken

[Cooper Jr., Franklin]

FYI commit http://arago-project.org/git/?p=meta-arago.git;a=commit;h=087566d0fefb1d1ccd8b44b964b6ed67720d5527 breaks
python-m2crypto-native. For some reason the two patches from python-m2crypto (install.patch and m2crypto-0.20.2-openssl-1.0.0.patch) fails to apply. Removing the toolchain patch above fixes this problem.

Re: python-m2crypto-native broken

[Denys Dmytriyenko]

On Wed, Oct 03, 2012 at 12:32:58AM +0000, Cooper Jr., Franklin wrote:
> FYI commit http://arago-project.org/git/?p=meta-arago.git;a=commit;h=087566d0fefb1d1ccd8b44b964b6ed67720d5527 
> breaks python-m2crypto-native. For some reason the two patches from 
> python-m2crypto (install.patch and m2crypto-0.20.2-openssl-1.0.0.patch) 
> fails to apply. Removing the toolchain patch above fixes this problem.

Please do a clean build - the temp directory got changed.

-- 
Denys

Re: python-m2crypto-native broken

[Cooper Jr., Franklin]

I tried doing a cleanall on python-m2crypto-native and python-m2crypto since I figured that might be the potential issue. That did not solve the issue. The weird part is that it isn't a actually compile error it is a patch error. Is there something else I can try instead of deleting my entire temp directory?

-----Original Message-----
From: Dmytriyenko, Denys 
Sent: Tuesday, October 02, 2012 8:00 PM
To: Cooper Jr., Franklin
Cc: meta-arago@arago-project.org
Subject: Re: [meta-arago] python-m2crypto-native broken

On Wed, Oct 03, 2012 at 12:32:58AM +0000, Cooper Jr., Franklin wrote:
> FYI commit 
> http://arago-project.org/git/?p=meta-arago.git;a=commit;h=087566d0fefb
> 1d1ccd8b44b964b6ed67720d5527 breaks python-m2crypto-native. For some 
> reason the two patches from python-m2crypto (install.patch and 
> m2crypto-0.20.2-openssl-1.0.0.patch)
> fails to apply. Removing the toolchain patch above fixes this problem.

Please do a clean build - the temp directory got changed.

--
Denys

Re: python-m2crypto-native broken

[Denys Dmytriyenko]

On Tue, Oct 02, 2012 at 09:11:06PM -0400, Cooper Jr., Franklin wrote:
> I tried doing a cleanall on python-m2crypto-native and python-m2crypto since 
> I figured that might be the potential issue. That did not solve the issue. 
> The weird part is that it isn't a actually compile error it is a patch 
> error. Is there something else I can try instead of deleting my entire temp 
> directory?

Well, I don't think it has anything to do with the recent change, but rather 
looks like the recipe is bad - when building from scratch, it first fails on 
the bad checksums, and then when checksums are corrected, fails to apply the 
first patch. Doing so manually fails the same way. So, I'm wondering how it 
used to work for you before, but that's why it still works when re-using the 
old temp/work directory...

-- 
Denys