pcp
[Top] [All Lists]

Re: [pcp] Build/install status for 3.7.0

To: Ken McDonell <kenj@xxxxxxxxxxxxxxxx>
Subject: Re: [pcp] Build/install status for 3.7.0
From: Nathan Scott <nathans@xxxxxxxxxx>
Date: Wed, 6 Mar 2013 16:28:15 -0500 (EST)
Cc: pcp@xxxxxxxxxxx
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <5137A049.1070102@xxxxxxxxxxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>

----- Original Message -----
> On 06/03/13 20:15, Nathan Scott wrote:
> >> On vm18 3.6.11 x86_64 LinuxMint 12 (lisa) the build dies a
> >> horrible
> >> death in the python code with ...
> 
> > I *think* this is from pyversions -nr returning more versions of
> > python than are installed on the machine.  I think in turn this
> > is because the build dependency is not ensuring python2.6 is there.
> > I've attempted a fix: dev b8f72f3 not 100% certain though - seems
> > like it might work.
> 
> OK this is more broken than I thought ... pyversions -vr (no -n)
> returns as follows:
> 

Not sure if you got this bit figured, but apparently you must run
that command from with a work area:
nathans@verge:/source/git/pcp$ pyversions -vr
2.7 2.6
nathans@verge:/source/git/pcp$ cd src/
nathans@verge:/source/git/pcp/src$ pyversions -vr
pyversions: error parsing Python-Version attribute
nathans@verge:/source/git/pcp/src$ cd ..
nathans@verge:/source/git/pcp$ grep Python-Version debian/control 
X-Python-Version: >= 2.6

So, with my change from yesterday I was expecting you'd get an
unsatisfied build dependency (thanks to the "python-all" req),
and once you install "python2.6" alongside your "python2.7" it
would magically start to work.

> > I'd like to get back to a point where we get some Windows servers
> > into the mix, somehow, but really don't have a good way to reach
> > that point (licensing issues, packaging issues, etc).  Perhaps we
> > could approach the Aconex folks for assistance with getting a
> > licensed VM into the farm?  (and then just keep git builds rolling
> > forward until an opportunity to tackle packaging next presents).
> 
> I have a Windows 8 VM there with a pre-release developer licence
> (that
> may or may not still work), but the biggest obstacle is there is no
> reliable recipe for creating a build environment with MSYS et al to
> create installable packages.

In the interim, to catch dev branch build fallout early on (before a
release), could a git-based (update/clone + build + raw make install)
kind of model be utilised?  (horrible, I know)

cheers.

--
Nathan

<Prev in Thread] Current Thread [Next in Thread>