build dependencies that cross subproject boundaries? Or maybe its that zfec setup.py doesn't clean away old stuff? #6

Closed
opened 2007-04-26 23:05:40 +00:00 by zooko · 1 comment

If you change the source code for zfec in such a way that invoking its setup.py leaves old results lying around, the tahoe GNUmakefile will fail. This was demonstrated by an older zfec which built python-2.5-only modules, and upgrading to the new pyfec which build python-2.4 modules left the 2.5-only ones in place, and then they got loaded and the build failed.

If you change the source code for zfec in such a way that invoking its setup.py leaves old results lying around, the tahoe GNUmakefile will fail. This was demonstrated by an older zfec which built python-2.5-only modules, and upgrading to the new pyfec which build python-2.4 modules left the 2.5-only ones in place, and then they got loaded and the build failed.
zooko added the
major
defect
labels 2007-04-26 23:05:40 +00:00
warner added the
packaging
label 2007-04-28 19:18:08 +00:00
zooko added
minor
and removed
major
labels 2007-04-30 05:32:00 +00:00
Author

merging with #10

merging with #10
zooko added the
duplicate
label 2007-05-02 02:51:29 +00:00
zooko closed this issue 2007-05-02 02:51:29 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
1 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#6
No description provided.