Re: My progress on armhf
On Tue, Aug 30, 2011 at 03:27:57PM -0400, Lennart Sorensen wrote:
> On Mon, Aug 29, 2011 at 08:51:49PM -0600, Zooko O'Whielacronx wrote:
> > On Mon, Aug 22, 2011 at 12:25 PM, Lennart Sorensen
> > <email@example.com> wrote:
> > >
> > > Any suggestions for what to fix next?
> > Can I put in a request for CPython 2.7?
> > hg clone http://hg.python.org/cpython
> > cd cpython
> > hg update 2.7
> > Further information about developing CPython:
> > http://docs.python.org/devguide/setup.html
> > Since it is a clean, portable C-oriented codebase I would expect it to
> > be one of the easier goals.
> > That plus a couple of other dependencies will allow me to bring up
> > Tahoe-LAFS. :-)
> Where is the debian package for it?
> I am trying to fix broken debian packages, not make new ones. :)
So looking at it, it appears to me that cpython is python and that
python2.7 version 2.7.2-5 already in armhf and working by the looks of
it, is essentially the same thing.
There are very minor differences between 2.7.2-5 and the current 2.7
branch in hg. I did a diff. Practically the same code with some
So what's the thing that you think needs doing?
ii libpython2.7 2.7.2-5 Shared Python runtime library (version 2.7)
ii python2.7 2.7.2-5 An interactive high-level object-oriented language (version 2.7)
ii python2.7-dbg 2.7.2-5 Debug Build of the Python Interpreter (version 2.7)
ii python2.7-dev 2.7.2-5 Header files and a static library for Python (v2.7)
ii python2.7-minimal 2.7.2-5 A minimal subset of the Python language (version 2.7)
# python2.7 --version
# dpkg --print-architecture
Seems OK to me.
You might even have a very easy job left:
# dpkg -l tahoe-lafs
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Description
ii tahoe-lafs 1.8.2-3 Secure distributed filesystem
No idea how to test it, but it's already built and installable on armhf.