[NeXus-tech] Nexus 4.3.0

[freddie.akeroyd at stfc.ac.uk]

Peter,

I will look into the python issue

Re: shadow - the host is up and mantid mediawiki is working, but mantid trac seems to be suffering and is saying something about     "KeyError: 'peak'"    I will try to sort it out

Regards,

Freddie

> -----Original Message-----
> From: Peterson, Peter F. [mailto:petersonpf at ornl.gov]
> Sent: 06 February 2012 15:46
> To: Akeroyd, Freddie (STFC,RAL,ISIS)
> Cc: nexus-tech at nexusformat.org
> Subject: Re: Nexus 4.3.0
> 
> Looking deeper into it there appears to be something with making the
> python as well.
> error: File not found by glob: ....rpmbuild/BUILDROOT/nexus-
> 4.2_branch_r1812-0.x86_64/usr/lib/python*/site-packages/nxs
> 
> First is the oddity that it still thinks this is nexus 4.2, then is the
> fact that the subtree doesn't exist past .../usr/lib. The only thing in
> there is "debug".
> 
> As a separate issue, shadow seems to be down.
> 
> P^2
> 
> On Feb 6, 2012, at 10:36 AM, <freddie.akeroyd at stfc.ac.uk> wrote:
> 
> > Peter,
> >
> >>
> >> We (SNS) are having our startup in one week and desperately need to
> be
> >> running the latest version for the int64 support. Can we wrap up the
> >> current version (with a few known minor bugs) and release it as
> 4.3.0?
> >> If there are other issues we can release 4.3.1 with those resolved,
> but
> >> we have been trying to get this one done since the code camp.
> >>
> >
> > If everybody is happy with a linux only release of 4.3.0 then, yes,
> we can wrap things up pretty quickly.
> >
> >>
> >> I was trying to verify that all the headers exist in the dev package
> >> (RHEL6) by building from the source rpm only to discover that you
> have
> >> left some specific ISIS stuff in there (e.g. "user isisupdate does
> not
> >> exist"). This should be easy to fix and we could have rc3 later
> today
> >> for playing with.
> >>
> >
> > That is just the local building account username that rpm leaves in
> the file - I do not do automatic builds as root for security reasons.
> You get a similar issue with standard redhat source rpms which often
> say:
> >
> >   warning: user mockbuild does not exist - using root
> >
> > when you try to rebuild them. I'm going to change to using mock now
> anyway. Was this warning message the only problem with the source rpm?
> >
> > Regards,
> >
> > Freddie
> > --
> > Scanned by iCritical.

-- 
Scanned by iCritical.