1 |
Am Freitag 03 Dezember 2010 15:48:42 schrieb Jan Marten Simons: |
2 |
> Hi, |
3 |
> |
4 |
> I recently found out cctbx has released a new version (see |
5 |
> http://cci.lbl.gov/cctbx_build/). I tried to do a version-bump with the |
6 |
> ebuild, but as some code changed some patches don't apply anymore. |
7 |
|
8 |
By now there is another new release: 2010_12_06_2139 availiable at |
9 |
http://cci.lbl.gov/cctbx_build/: |
10 |
|
11 |
http://cci.lbl.gov/cctbx_build/results/2010_12_06_2139/cctbx_bundle.tar.gz |
12 |
|
13 |
As one of the changes is "Migration to Python 2.7.1" it might be neccessary to |
14 |
depend on python >=2.7.1 |
15 |
|
16 |
|
17 |
I did a simple version-bump with the most recent ebuild in tree and found out: |
18 |
|
19 |
* -tst-server.py.patch can be dropped, as the code it tries to correct has |
20 |
been removed upstream |
21 |
* -clipper.patch still applies. |
22 |
* -boost.patch, -flags.patch and -soname.patch both don't apply to the new |
23 |
version and I'm not sure if I know enough about Scons to fix them up. |
24 |
|
25 |
More details on the bug I found: |
26 |
(/usr/lib64/cctbx/cctbx_build/bin/cctbx.python is refering to paths in |
27 |
/var/tmp/portage, which don't exist post-install and therefore calling |
28 |
cctbx.python does not give a useable environment. After fixing up those |
29 |
paths (manually) I got a working python shell where import cctbx works |
30 |
like it should.) |
31 |
|
32 |
I attached a diff between the broken version (installed by the ebuild) and my |
33 |
working version. A solution would be to either fix the paths post build via sed |
34 |
or to get the build to write correct paths, which might be much more difficult. |
35 |
|
36 |
|
37 |
I'll gladly help in debugging/testing an ebuld of the most recent version |
38 |
of cctbx. I've joined irc as well. |
39 |
|
40 |
With regards, |
41 |
|
42 |
Jan Simons |
43 |
|
44 |
Institute of Crystallography |
45 |
RWTH Aachen University |