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:31:18 -0500 (EST)
Cc: pcp@xxxxxxxxxxx
Delivered-to: pcp@xxxxxxxxxxx
In-reply-to: <1198532005.15945263.1362605295516.JavaMail.root@xxxxxxxxxx>
Reply-to: Nathan Scott <nathans@xxxxxxxxxx>

----- Original Message -----
> 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.

Sorry not very clear - IOW, "apt-get python-all" will be needed,
and the debian packaging build-requires now enforces that (which
is apparently the way to go based on Debian policy docs).

cheers.

--
Nathan

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