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

build of mac package fails due to some mysterious reason (not pkgutil) #763

New Issue
Closed
opened 2009-07-15 05:14:42 +00:00 by zooko · 4 comments
zooko commented 2009-07-15 05:14:42 +00:00
Copy Link

I applied a patch to my local version of zetuptoolz on ootles to get past the problem described in #762. Now the "build a Mac package" step completes on ootles:

http://allmydata.org/buildbot/builders/zooko%20ootles%20Mac-amd64%2010.4/builds/230/steps/dist/logs/stdio

but the (new! improved!) "test the resulting Mac package" steps fails:

http://allmydata.org/buildbot/builders/zooko%20ootles%20Mac-amd64%2010.4/builds/230/steps/testdmg/logs/stdio

The "test the resulting Mac package" step could hopefully be amended to emit more diagnostics in this case...

I applied a patch to my local version of zetuptoolz on ootles to get past the problem described in #762. Now the "build a Mac package" step completes on ootles: <http://allmydata.org/buildbot/builders/zooko%20ootles%20Mac-amd64%2010.4/builds/230/steps/dist/logs/stdio> but the (new! improved!) "test the resulting Mac package" steps fails: <http://allmydata.org/buildbot/builders/zooko%20ootles%20Mac-amd64%2010.4/builds/230/steps/testdmg/logs/stdio> The "test the resulting Mac package" step could hopefully be amended to emit more diagnostics in this case...
zooko added the
packaging
major
defect
1.4.1
 labels 2009-07-15 05:14:42 +00:00
zooko added this to the eventually milestone 2009-07-15 05:14:42 +00:00
zooko commented 2009-08-06 18:33:44 +00:00
Author
Copy Link

I hope to address this issue for Tahoe-LAFS v1.5.1.

I hope to address this issue for Tahoe-LAFS v1.5.1.
zooko commented 2009-08-18 03:08:50 +00:00
Author
Copy Link

I'm booting this ticket out of v1.5.1 because we're making good progress on Debian and Windows for v1.5.1, and I appear to be the only person who is working on Mac, and I have sooo little time right now. The Mac side would hold up the release after the Debian and Windows sides were ready unless someone else were to jump in.

I'm booting this ticket out of v1.5.1 because we're making good progress on Debian and Windows for v1.5.1, and I appear to be the only person who is working on Mac, and I have sooo little time right now. The Mac side would hold up the release after the Debian and Windows sides were ready unless someone else were to jump in.
cgalvan commented 2009-09-24 19:59:41 +00:00
Owner
Copy Link

Note that once #668 is resolved, switching to Distribute, this issue may or may not be resolved as a result.

Note that once #668 is resolved, switching to Distribute, this issue may or may not be resolved as a result.
zooko added this to the eventually milestone 2009-10-26 20:09:15 +00:00
daira commented 2014-09-08 16:35:23 +00:00
Owner
Copy Link

I think the dmg Mac installer is no more. In any case the build logs will have been deleted. (Please attach build logs to tickets rather than just linking to them!)

I think the dmg Mac installer is no more. In any case the build logs will have been deleted. (Please attach build logs to tickets rather than just linking to them!)
tahoe-lafs added the
cannot reproduce
 label 2014-09-08 16:35:23 +00:00
daira closed this issue 2014-09-08 16:35:23 +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
eventually
Assignees
Clear assignees
No Assignees
zooko
2 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#763
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?