#1983 closed task (wontfix)

build binary eggs for linux-armv6l (raspberry pi)

Reported by: zooko Owned by:
Priority: normal Milestone: soon
Component: packaging Version: 1.10.0
Keywords: linux arm eggs raspberry-pi Cc:
Launchpad Bug:

Description (last modified by daira)

This is one of a collection of tickets about binary eggs that need to be built for specific platforms.

See src/allmydata/_auto_deps.py for Tahoe-LAFS trunk's current dependencies, and https://tahoe-lafs.org/source/tahoe-lafs/deps/tahoe-dep-eggs/README.html for the eggs that have been built and uploaded.

Attachments (7)

all.egg (2.1 MB) - added by kapiteined at 2013-05-30T19:23:03Z.
made with: python setup.py bdist_egg
pycrypto.egg (2.1 MB) - added by kapiteined at 2013-05-30T19:23:37Z.
made with: python -c "import setuptools; file = 'setup.py'; execfile('setup.py')" bdist_egg
pycryptopp-0.6.0.1206569328141510525648634803928199668821045408958-py2.7-linux-armv6l.egg.gz (4.7 MB) - added by tilllt at 2013-06-10T23:06:10Z.
pyOpenSSL-0.13-py2.7-linux-armv6l.egg.gz (288.7 KB) - added by tilllt at 2013-06-10T23:07:05Z.
Twisted-13.0.0-py2.7-linux-armv6l.egg.gz (6.1 MB) - added by tilllt at 2013-06-10T23:08:29Z.
zfec-1.4.24-py2.7-linux-armv6l.egg.gz (89.3 KB) - added by tilllt at 2013-06-10T23:09:08Z.
zope.interface-4.0.5-py2.7-linux-armv6l.egg.gz (272.0 KB) - added by tilllt at 2013-06-10T23:09:21Z.

Change History (26)

comment:1 Changed at 2013-05-25T02:21:19Z by daira

  • Component changed from unknown to packaging
  • Description modified (diff)
  • Keywords linux arm eggs raspberry-pi added
  • Milestone changed from undecided to soon

zooko wrote:

From #804, if someone builds binary eggs of the dependencies for linux-armv6l, that would make it easier and faster to install Tahoe-LAFS on raspberry pi.

It is currently missing all eggs, and I think we just need to support Python 2.7.

comment:2 Changed at 2013-05-25T02:29:43Z by daira

  • Description modified (diff)

comment:3 Changed at 2013-05-25T02:32:05Z by daira

  • Owner daira deleted

comment:4 follow-up: Changed at 2013-05-29T16:48:53Z by zooko

Here are instructions for how to build binary eggs:

Packaging

comment:5 in reply to: ↑ 4 Changed at 2013-05-30T09:28:52Z by kapiteined

Replying to zooko:

Here are instructions for how to build binary eggs:

Packaging


Hmm.. i tried but get an error:

python -c "import setuptools; execfile('setup.py')" bdist_egg[[BR]]
Traceback (most recent call last):[[BR]]
File "<string>", line 1, in <module>[[BR]]
File "setup.py", line 24, in <module>[[BR]]
basedir = os.path.dirname(os.path.abspath(__file__))[[BR]]
NameError: name '__file__' is not defined[[BR]]

My knowledge of python is next to zero, so a foolproof cut and paste line to build this egg would be great

Kind regards,
Ed

Last edited at 2013-05-30T19:34:13Z by zooko (previous) (diff)

comment:6 Changed at 2013-05-30T18:46:37Z by daira

Try this:

python -c "import setuptools; __file__ = 'setup.py'; execfile('setup.py')" bdist_egg
Last edited at 2013-05-30T18:46:49Z by daira (previous) (diff)

comment:7 follow-up: Changed at 2013-05-30T18:52:08Z by daira

Hang on, that line is only necessary for pycrypto. The other eggs should be built using:

python setup.py bdist_egg

Changed at 2013-05-30T19:23:03Z by kapiteined

made with: python setup.py bdist_egg

Changed at 2013-05-30T19:23:37Z by kapiteined

made with: python -c "import setuptools; file = 'setup.py'; execfile('setup.py')" bdist_egg

comment:8 in reply to: ↑ 7 ; follow-up: Changed at 2013-05-30T19:26:32Z by kapiteined

Replying to daira:

Hang on, that line is only necessary for pycrypto. The other eggs should be built using:

python setup.py bdist_egg

Worked like a charm, the egg file from both commands are attached, the original name was:
dist/allmydata_tahoe-1.10.0-py2.7.egg

Could someone change the Packaging page to include the right commands?

comment:9 follow-up: Changed at 2013-05-30T19:33:44Z by zooko

Thanks, kapiteined and daira! kapiteined: what's your name and contact info, and what computer did you build it on, and what operating system was it running? Thanks again!

comment:10 in reply to: ↑ 9 Changed at 2013-05-30T20:39:05Z by kapiteined

Replying to zooko:

Thanks, kapiteined and daira! kapiteined: what's your name and contact info, and what computer did you build it on, and what operating system was it running? Thanks again!


Hi Zooko, my e-mail address is ed AT kapitein DOT org.
It was build on the pi itself running rasbian, updated to the latest version about a week ago.

Feel free to contact me to try out a release candidate for the pi package.

comment:11 in reply to: ↑ 8 ; follow-up: Changed at 2013-05-30T21:32:12Z by daira

Replying to kapiteined:

Replying to daira:

Hang on, that line is only necessary for pycrypto. The other eggs should be built using:

python setup.py bdist_egg

Worked like a charm, the egg file from both commands are attached, the original name was:
dist/allmydata_tahoe-1.10.0-py2.7.egg

That's an egg for Tahoe itself, which we don't actually need. We need the eggs for Tahoe's dependencies that use C/C++ code, which are the 6 table columns at https://tahoe-lafs.org/source/tahoe/deps/tahoe-lafs-dep-eggs/README.html:

Could someone change the Packaging page to include the right commands?

Will do.

comment:12 in reply to: ↑ 11 Changed at 2013-05-30T21:43:08Z by daira

Replying to daira:

Replying to kapiteined:

Could someone change the Packaging page to include the right commands?

Will do.

Done.

comment:13 follow-up: Changed at 2013-06-10T22:41:27Z by tilllt

pyOpenSSL seems to need the "long" packaging command as well:

python -c "import setuptools; file = 'setup.py'; execfile('setup.py')" bdist_egg

comment:14 in reply to: ↑ 13 Changed at 2013-06-16T22:41:49Z by daira

Replying to tilllt:

pyOpenSSL seems to need the "long" packaging command as well:

python -c "import setuptools; __file__ = 'setup.py'; execfile('setup.py')" bdist_egg

Fixed in Packaging.

comment:15 Changed at 2014-09-05T01:01:56Z by zooko

Okay, I'm officially closing all tickets that have to do with binary eggs on Linux as wontfix. Binary eggs have never worked on Linux, and never will. I hate this, but I hereby stop struggling against it.

comment:16 Changed at 2014-09-07T17:20:53Z by daira

It might be useful to maintain these eggs for Raspberry pi because it's difficult to compile them on the pi.

comment:17 Changed at 2014-09-08T18:15:20Z by warner

I'm +1 on hosting ARM eggs. I've got an rPi lying around, I could probably build them if I get some free time.

comment:18 Changed at 2014-09-08T21:31:45Z by daira

The necessary eggs are already attached to this ticket, aren't they?

comment:19 Changed at 2019-08-13T17:59:49Z by exarkun

  • Resolution set to wontfix
  • Status changed from new to closed

We have since stopped CI for Raspberry Pi/ARMv6l. Also eggs are probably obsolete at this point (a similar ticket might be filed about wheels, if Raspberry Pi/ARMv6l again becomes a supported platform).

Last edited at 2019-08-13T18:00:33Z by exarkun (previous) (diff)
Note: See TracTickets for help on using tickets.