Hi Stuart,
On 11/06/16 19:35, Stuart Barkley wrote:
On Wed, 8 Jun 2016 at 14:05 -0000, Kenneth Hoste wrote:
Please check if you're still seeing these issues at all with an
up-to-date bootstrap scripts & the latest EasyBuild (v2.8.1), if you
have some time.
I have now done this with a fresh VM and v2.8.1. I think the main
issue with bootstrapping was the need for python-setuptools (CentOS
rpm name).
This should probably be mentioned in the documentation at
<http://easybuild.readthedocs.io/en/latest/Installation.html#requirements>.
Good point.
Please take a look at https://github.com/hpcugent/easybuild/pull/229,
feedback welcome.
I then use that easybuild to rebuild easybuild into my real
easybuild location.
Why not point the bootstrap script to that location instead?
The bootstrap already install EasyBuild with EasyBuild in the final
stage, you're just adding another EB-with-EB stage on top of that
basically...
Yes, I'm sure I way over bootstrap easybuild. In fact, on the
internal system I build/install easybuild once again in the final
build tree. I want to be sure any compile time hardware support is
correctly done (I doubt I need to worry about this with python and
easybuild).
You're right on the latter; the only thing that matters is the version
of your system Python (basically 2.6 or 2.7).
Other than that, the installation should be identical, regardless of the
system architecture.
regards,
Kenneth
- I find it annoying that easybuild does not include a .eb file
for itself. It does have .eb files for previous versions, but
when I want to rebuild the current version I need to either
"guess" what the .eb file might look like or find it somewhere on
github.
The main issue here is that I would need to include an easyconfig
file in the release that I can't (easily/reliably) test
(chicken-or-egg situation)...
So I figured.
Once you have an EasyBuild that was installed with EasyBuild, you
*have* an easyconfig file for it in the EasyBuild installation
directory itself (see the 'easybuild*' subdirectory)...
Okay. I'm now planning to grab that one on future upgrades.
However, there's an easier way: using "--from-pr". For example, to
install EasyBuild v2.8.1 you can use "eb --from-pr 3153" using
EasyBuild v2.8.0.
I should probably mention this more clearly in the release
announcement... I used --from-pr so often that I just don't think
about it anymore. :-)
Note that this doesn't require any setup at all w.r.t. GitHub
integration, since --from-pr is read-only (it basically is an
integrated curl in that respect); it should just work.
I'll try and make that more clear in future release announcements.
Yes, please do so. This is much easier for me in my environment. Be
clear about which PR has the .eb command since there are usually RPs
for each of the 3 components.
Stuart
[sending a new problem in a separate email]
