tahoe-lafs/trac-2024-07-25
2
0
Issues 1.1k Wiki

build binary eggs for linux-armv6l (raspberry pi) #1983

New Issue
Closed
opened 2013-05-25 02:11:26 +00:00 by zooko · 24 comments
zooko commented 2013-05-25 02:11:26 +00:00
Copy Link

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

See source: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.

This is one of a collection of tickets about binary eggs that need to be built for specific platforms. See source: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.
zooko added the
unknown
normal
task
1.10.0
 labels 2013-05-25 02:11:26 +00:00
zooko added this to the undecided milestone 2013-05-25 02:11:26 +00:00
daira commented 2013-05-25 02:21:19 +00:00
Owner
Copy Link

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.

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.
tahoe-lafs added
packaging
 and removed
unknown
 labels 2013-05-25 02:21:19 +00:00
tahoe-lafs modified the milestone from undecided to soon 2013-05-25 02:21:19 +00:00
zooko commented 2013-05-29 16:48:53 +00:00
Author
Copy Link

Here are instructions for how to build binary eggs:

wiki/Packaging#binary.eggsofdependencynative-codepackages

Here are instructions for how to build binary eggs: [wiki/Packaging#binary.eggsofdependencynative-codepackages](wiki/Packaging#binary.eggsofdependencynative-codepackages)
kapiteined commented 2013-05-30 09:28:52 +00:00
Owner
Copy Link

Replying to zooko:

Here are instructions for how to build binary eggs:

wiki/Packaging#binary.eggsofdependencynative-codepackages

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

Replying to [zooko](/tahoe-lafs/trac-2024-07-25/issues/1983#issuecomment-91958): > Here are instructions for how to build binary eggs: > > [wiki/Packaging#binary.eggsofdependencynative-codepackages](wiki/Packaging#binary.eggsofdependencynative-codepackages) <br> Hmm.. i tried but get an error:<br> ``` 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<br> Kind regards,<br> Ed
daira commented 2013-05-30 18:46:37 +00:00
Owner
Copy Link

Try this:

python -c "import setuptools; __file__ = 'setup.py'; execfile('setup.py')" bdist_egg
Try this: ``` python -c "import setuptools; __file__ = 'setup.py'; execfile('setup.py')" bdist_egg ```
daira commented 2013-05-30 18:52:08 +00:00
Owner
Copy Link

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

python setup.py bdist_egg
Hang on, that line is *only* necessary for pycrypto. The other eggs should be built using: ``` python setup.py bdist_egg ```
kapiteined commented 2013-05-30 19:23:03 +00:00
Owner
Copy Link

Attachment all.egg (2157486 bytes) added

made with: python setup.py bdist_egg

**Attachment** all.egg (2157486 bytes) added made with: python setup.py bdist_egg
all.egg
2.1 MiB
kapiteined commented 2013-05-30 19:23:37 +00:00
Owner
Copy Link

Attachment pycrypto.egg (2157487 bytes) added

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

**Attachment** pycrypto.egg (2157487 bytes) added made with: python -c "import setuptools; *file* = 'setup.py'; execfile('setup.py')" bdist_egg
pycrypto.egg
2.1 MiB
kapiteined commented 2013-05-30 19:26:32 +00:00
Owner
Copy Link

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?

Replying to [daira](/tahoe-lafs/trac-2024-07-25/issues/1983#issuecomment-91961): > 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:<br> dist/allmydata_tahoe-1.10.0-py2.7.egg<br> Could someone change the Packaging page to include the right commands?<br>
zooko commented 2013-05-30 19:33:44 +00:00
Author
Copy Link

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!

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!
kapiteined commented 2013-05-30 20:39:05 +00:00
Owner
Copy Link

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.

Replying to [zooko](/tahoe-lafs/trac-2024-07-25/issues/1983#issuecomment-91963): > 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! <br> Hi Zooko, my e-mail address is ed AT kapitein DOT org.<br> It was build on the pi itself running rasbian, updated to the latest version about a week ago.<br> <br> Feel free to contact me to try out a release candidate for the pi package.<br>
daira commented 2013-05-30 21:32:12 +00:00
Owner
Copy Link

Replying to [kapiteined]comment:8:

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.

Replying to [kapiteined]comment:8: > Replying to [daira](/tahoe-lafs/trac-2024-07-25/issues/1983#issuecomment-91961): > > 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:<br> > dist/allmydata_tahoe-1.10.0-py2.7.egg<br> 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>: * [Twisted](http://twistedmatrix.com/trac/wiki/Downloads) (use the source tarball) * [pyOpenSSL](https://pypi.python.org/pypi/pyOpenSSL) * [pycrypto](https://pypi.python.org/pypi/pycrypto) * [pycryptopp](https://pypi.python.org/pypi/pycryptopp) * [zfec](https://pypi.python.org/pypi/zfec) * [zope.interface](https://pypi.python.org/pypi/zope.interface/4.0.5) > Could someone change the Packaging page to include the right commands?<br> Will do.
daira commented 2013-05-30 21:43:08 +00:00
Owner
Copy Link

Replying to [daira]comment:11:

Replying to [kapiteined]comment:8:

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

Will do.

Done.

Replying to [daira]comment:11: > Replying to [kapiteined]comment:8: > > Could someone change the Packaging page to include the right commands?<br> > > Will do. Done.
tilllt commented 2013-06-10 22:41:27 +00:00
Owner
Copy Link

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

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

pyOpenSSL seems to need the "long" packaging command as well: python -c "import setuptools; *file* = 'setup.py'; execfile('setup.py')" bdist_egg
tilllt commented 2013-06-10 23:06:10 +00:00
Owner
Copy Link

Attachment pycryptopp-0.6.0.1206569328141510525648634803928199668821045408958-py2.7-linux-armv6l.egg.gz (4930781 bytes) added

**Attachment** pycryptopp-0.6.0.1206569328141510525648634803928199668821045408958-py2.7-linux-armv6l.egg.gz (4930781 bytes) added
pycryptopp-0.6.0.1206569328141510525648634803928199668821045408958-py2.7-linux-armv6l.egg.gz
4.7 MiB
tilllt commented 2013-06-10 23:07:05 +00:00
Owner
Copy Link

Attachment pyOpenSSL-0.13-py2.7-linux-armv6l.egg.gz (295603 bytes) added

**Attachment** pyOpenSSL-0.13-py2.7-linux-armv6l.egg.gz (295603 bytes) added
pyOpenSSL-0.13-py2.7-linux-armv6l.egg.gz
289 KiB
tilllt commented 2013-06-10 23:08:29 +00:00
Owner
Copy Link

Attachment Twisted-13.0.0-py2.7-linux-armv6l.egg.gz (6441062 bytes) added

**Attachment** Twisted-13.0.0-py2.7-linux-armv6l.egg.gz (6441062 bytes) added
Twisted-13.0.0-py2.7-linux-armv6l.egg.gz
6.1 MiB
tilllt commented 2013-06-10 23:09:08 +00:00
Owner
Copy Link

Attachment zfec-1.4.24-py2.7-linux-armv6l.egg.gz (91476 bytes) added

**Attachment** zfec-1.4.24-py2.7-linux-armv6l.egg.gz (91476 bytes) added
zfec-1.4.24-py2.7-linux-armv6l.egg.gz
89 KiB
tilllt commented 2013-06-10 23:09:21 +00:00
Owner
Copy Link

Attachment zope.interface-4.0.5-py2.7-linux-armv6l.egg.gz (278505 bytes) added

**Attachment** zope.interface-4.0.5-py2.7-linux-armv6l.egg.gz (278505 bytes) added
zope.interface-4.0.5-py2.7-linux-armv6l.egg.gz
272 KiB
daira commented 2013-06-16 22:41:49 +00:00
Owner
Copy Link

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 wiki/Packaging.

Replying to [tilllt](/tahoe-lafs/trac-2024-07-25/issues/1983#issuecomment-91967): > pyOpenSSL seems to need the "long" packaging command as well: > > `python -c "import setuptools; *file* = 'setup.py'; execfile('setup.py')" bdist_egg` Fixed in [wiki/Packaging](wiki/Packaging).
zooko commented 2014-09-05 01:01:56 +00:00
Author
Copy Link

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.

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.
daira commented 2014-09-07 17:20:53 +00:00
Owner
Copy Link

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

It might be useful to maintain these eggs for Raspberry pi because it's difficult to compile them on the pi.
warner commented 2014-09-08 18:15:20 +00:00
Copy Link

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.

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.
daira commented 2014-09-08 21:31:45 +00:00
Owner
Copy Link

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

The necessary eggs are already attached to this ticket, aren't they?
exarkun commented 2019-08-13 17:59:49 +00:00
Copy Link

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).

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).
exarkun added the
wontfix
 label 2019-08-13 17:59:49 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
0.2.0

   
0.3.0

   
0.4.0

   
0.5.0

   
0.5.1

   
0.6.0

   
0.6.1

   
0.7.0

   
0.8.0

   
0.9.0

   
1.0.0

   
1.1.0

   
1.10.0

   
1.10.1

   
1.10.2

   
1.10a2

   
1.11.0

   
1.12.0

   
1.12.1

   
1.13.0

   
1.14.0

   
1.15.0

   
1.15.1

   
1.2.0

   
1.3.0

   
1.4.1

   
1.5.0

   
1.6.0

   
1.6.1

   
1.7.0

   
1.7.1

   
1.7β

   
1.8.0

   
1.8.1

   
1.8.2

   
1.8.3

   
1.8β

   
1.9.0

   
1.9.0-s3branch

   
1.9.0a1

   
1.9.0a2

   
1.9.0b1

   
1.9.1

   
1.9.2

   
1.9.2a1

   
LeastAuthority.com automation

   
blocker

   
cannot reproduce

   
cloud-branch

   
code

catch-all for anything that can be fixed by writing code but isn't classified better

  
code-dirnodes

anything involving tahoe directories

  
code-encoding

immutable-file encoding format/layout, cap format, encoding/decoding algorithms

  
code-frontend

general frontend things: new user-facing interfaces, FTP/SFTP servers, FUSE-like interfaces

  
code-frontend-cli

CLI tools

  
code-frontend-ftp-sftp

   
code-frontend-magic-folder

   
code-frontend-web

webapi interfaces, user-facing "WUI" interfaces

  
code-mutable

anything involving mutable files: encoding/decoding, share format

  
code-network

Introducer, locating storage servers, establishing/maintaining connections to them

  
code-nodeadmin

node startup/shutdown, tools to create nodes, logging tools, management/monitoring tools, manhole, disk-space-limiting tools

  
code-peerselection

server selection/sorting algorithm, rebalancing code, allocation policy, swarming-download

  
code-storage

storage-server implementation, share-storage directory layout, client-to-server share transfer protocol

  
contrib

problems with non-core things that live in the source:contrib/ directory

  
critical

   
defect

   
dev-infrastructure

things that help us build Tahoe: buildbot, automated speed/memory/code-coverage tests and results-displayers, IRC channels, mailing lists, this Trac instance

  
documentation

docs items. Also use 'docs' keyword on tickets in more specific components.

  
duplicate

   
enhancement

   
fixed

   
invalid

   
major

   
minor

   
n/a

   
normal

   
operational

things involved in running a tahoe grid, external tools to monitor/maintain a grid (like "nodeadmin" but larger-scale). Was also used for issues with the allmydata.com grid.

  
packaging

setup.py script, library dependencies, binary packages, licensing, installation instructions

  
somebody else's problem

   
supercritical

   
task

   
trivial

   
unknown

Uncategorized. All tickets default to this component until someone updates it.

  
was already fixed

   
website

things about the tahoe-lafs.org website (and sometimes this Trac instance, shared with 'dev-infrastructure')

  
wontfix

   
worksforme
No Label
0.2.0
0.3.0
0.4.0
0.5.0
0.5.1
0.6.0
0.6.1
0.7.0
0.8.0
0.9.0
1.0.0
1.1.0
1.10.0
1.10.1
1.10.2
1.10a2
1.11.0
1.12.0
1.12.1
1.13.0
1.14.0
1.15.0
1.15.1
1.2.0
1.3.0
1.4.1
1.5.0
1.6.0
1.6.1
1.7.0
1.7.1
1.7β
1.8.0
1.8.1
1.8.2
1.8.3
1.8β
1.9.0
1.9.0-s3branch
1.9.0a1
1.9.0a2
1.9.0b1
1.9.1
1.9.2
1.9.2a1
LeastAuthority.com automation
blocker
cannot reproduce
cloud-branch
code
code-dirnodes
code-encoding
code-frontend
code-frontend-cli
code-frontend-ftp-sftp
code-frontend-magic-folder
code-frontend-web
code-mutable
code-network
code-nodeadmin
code-peerselection
code-storage
contrib
critical
defect
dev-infrastructure
documentation
duplicate
enhancement
fixed
invalid
major
minor
n/a
normal
operational
packaging
somebody else's problem
supercritical
task
trivial
unknown
was already fixed
website
wontfix
worksforme
Milestone
Clear milestone
No items
No Milestone
soon
Assignees
Clear assignees
No Assignees
4 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: tahoe-lafs/trac-2024-07-25#1983
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?