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

hard to navigate the docs to install, on Debian, with short attention span #978

New Issue
Closed
opened 2010-03-03 23:44:52 +00:00 by zooko · 14 comments
zooko commented 2010-03-03 23:44:52 +00:00
Copy Link

Jake Appelbaum tested our install docs for us. He wrote a patch to make it quicker and dirtier.

Jake Appelbaum tested our install docs for us. He wrote a patch to make it quicker and dirtier.
zooko added the
documentation
major
defect
1.6.0
 labels 2010-03-03 23:44:52 +00:00
zooko added this to the undecided milestone 2010-03-03 23:44:52 +00:00
ioerror commented 2010-03-03 23:47:55 +00:00
Copy Link

Attachment debian-tldr.txt (1583 bytes) added

**Attachment** debian-tldr.txt (1583 bytes) added
debian-tldr.txt
1.5 KiB
ioerror commented 2010-03-03 23:48:59 +00:00
Copy Link
# dpkg -i ../allmydata-tahoe_0.0.1_all.deb
Selecting previously deselected package allmydata-tahoe.
(Reading database ... 100686 files and directories currently installed.)
Unpacking allmydata-tahoe (from .../allmydata-tahoe_0.0.1_all.deb) ...

dpkg: dependency problems prevent configuration of allmydata-tahoe:
 allmydata-tahoe depends on python-twisted; however:
> Package python-twisted is not installed.
 allmydata-tahoe depends on python-foolscap (>= 0.4.1); however:
> Package python-foolscap is not installed.
 allmydata-tahoe depends on python-nevow; however:
> Package python-nevow is not installed.
 allmydata-tahoe depends on python-simplejson (>= 1.4); however:
> Package python-simplejson is not installed.
 allmydata-tahoe depends on python-zfec (>= 1.1); however:
> Package python-zfec is not installed.
 allmydata-tahoe depends on python-pycryptopp (>= 0.5.15); however:
> Package python-pycryptopp is not installed.
dpkg: error processing allmydata-tahoe (--install):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 allmydata-tahoe
``` # dpkg -i ../allmydata-tahoe_0.0.1_all.deb Selecting previously deselected package allmydata-tahoe. (Reading database ... 100686 files and directories currently installed.) Unpacking allmydata-tahoe (from .../allmydata-tahoe_0.0.1_all.deb) ... dpkg: dependency problems prevent configuration of allmydata-tahoe: allmydata-tahoe depends on python-twisted; however: > Package python-twisted is not installed. allmydata-tahoe depends on python-foolscap (>= 0.4.1); however: > Package python-foolscap is not installed. allmydata-tahoe depends on python-nevow; however: > Package python-nevow is not installed. allmydata-tahoe depends on python-simplejson (>= 1.4); however: > Package python-simplejson is not installed. allmydata-tahoe depends on python-zfec (>= 1.1); however: > Package python-zfec is not installed. allmydata-tahoe depends on python-pycryptopp (>= 0.5.15); however: > Package python-pycryptopp is not installed. dpkg: error processing allmydata-tahoe (--install): dependency problems - leaving unconfigured Errors were encountered while processing: allmydata-tahoe ```
ioerror commented 2010-03-03 23:54:49 +00:00
Copy Link

The version number is clearly incorrect for the .deb that is built.

The version number is clearly incorrect for the .deb that is built.
ioerror commented 2010-03-04 01:29:17 +00:00
Copy Link

Attachment debian-tldr-second-try.txt (3696 bytes) added

**Attachment** debian-tldr-second-try.txt (3696 bytes) added
debian-tldr-second-try.txt
3.6 KiB
ioerror commented 2010-03-04 01:35:14 +00:00
Copy Link

Huzzah! The second patch I've submitted here results in a deb that works:

# dpkg -i allmydata-tahoe_0.0.1_all.deb
Selecting previously deselected package allmydata-tahoe.
(Reading database ... 103129 files and directories currently installed.)
Unpacking allmydata-tahoe (from allmydata-tahoe_0.0.1_all.deb) ...
Setting up allmydata-tahoe (0.0.1) ...
Huzzah! The second patch I've submitted here results in a deb that works: ``` # dpkg -i allmydata-tahoe_0.0.1_all.deb Selecting previously deselected package allmydata-tahoe. (Reading database ... 103129 files and directories currently installed.) Unpacking allmydata-tahoe (from allmydata-tahoe_0.0.1_all.deb) ... Setting up allmydata-tahoe (0.0.1) ... ```
ioerror commented 2010-03-04 01:48:27 +00:00
Copy Link

Attachment debian-tldr-third-try.txt (3398 bytes) added

**Attachment** debian-tldr-third-try.txt (3398 bytes) added
debian-tldr-third-try.txt
3.3 KiB
ioerror commented 2010-03-04 01:48:44 +00:00
Copy Link

And we're done:

dpkg -i allmydata-tahoe_1.6.1-r4262_all.deb
Selecting previously deselected package allmydata-tahoe.
(Reading database ... 104355 files and directories currently installed.)
Unpacking allmydata-tahoe (from allmydata-tahoe_1.6.1-r4262_all.deb) ...
Setting up allmydata-tahoe (1.6.1-r4262) ...
And we're done: ``` dpkg -i allmydata-tahoe_1.6.1-r4262_all.deb Selecting previously deselected package allmydata-tahoe. (Reading database ... 104355 files and directories currently installed.) Unpacking allmydata-tahoe (from allmydata-tahoe_1.6.1-r4262_all.deb) ... Setting up allmydata-tahoe (1.6.1-r4262) ... ```
leif commented 2010-03-08 05:04:15 +00:00
Copy Link

Following ioerror's instructions in debian-docs-patch-final.txt (found on ticket #961) I was able to build a Debian lenny package.

The only thing I did differently than ioerror was that I also used stdeb to make debs of the two remaining things he easy_install'd: argparse and zbase32.

To make argparse's setup.py happy, I ran sed -i -e 's/file/"."/' setup.py

Following ioerror's instructions in debian-docs-patch-final.txt (found on ticket #961) I was able to build a Debian lenny package. The only thing I did differently than ioerror was that I also used stdeb to make debs of the two remaining things he easy_install'd: argparse and zbase32. To make argparse's setup.py happy, I ran sed -i -e 's/*file*/"."/' setup.py
leif commented 2010-03-08 05:07:06 +00:00
Copy Link

Oops, wikiformatting ate my underscores. That should read

sed -i -e 's/__file__/"."/' setup.py
Oops, wikiformatting ate my underscores. That should read ``` sed -i -e 's/__file__/"."/' setup.py ```
warner commented 2010-03-10 19:42:38 +00:00
Copy Link

it looks like this patch has already landed (although, as with darcs patches in general, I don't know when or who to thank for landing it). One thing I'd point out is that the python-pycryptopp package is not in Lenny proper (although it is in lenny-backports), so you should either point this out explicitly or provide instructions for creating a pycryptopp deb too.

it looks like this patch has already landed (although, as with darcs patches in general, I don't know when or who to thank for landing it). One thing I'd point out is that the python-pycryptopp package is not in Lenny proper (although it is in lenny-backports), so you should either point this out explicitly or provide instructions for creating a pycryptopp deb too.
tahoe-lafs modified the milestone from undecided to 1.7.0 2010-03-21 16:41:38 +00:00
zooko modified the milestone from 1.7.0 to 1.7.1 2010-06-19 01:25:35 +00:00
davidsarah commented 2010-07-18 00:47:35 +00:00
Owner
Copy Link

The patch was applied in changeset:8fddc7a4a5cf4f69. Leaving open to address comment:75969 and comment:75971.

The patch was applied in changeset:8fddc7a4a5cf4f69. Leaving open to address [comment:75969](/tahoe-lafs/trac-2024-07-25/issues/978#issuecomment-75969) and [comment:75971](/tahoe-lafs/trac-2024-07-25/issues/978#issuecomment-75971).
tahoe-lafs modified the milestone from 1.7.1 to 1.8β 2010-07-18 00:47:35 +00:00
zooko commented 2010-07-18 01:54:24 +00:00
Author
Copy Link

Replying to warner:

it looks like this patch has already landed (although, as with darcs patches in general, I don't know when or who to thank for landing it).

How would you like this to be different? I've been using git full-time at work for the past few months and I don't understand how this would be different with git.

I suppose we committers could get into the habit of using "darcs amend --edit" to edit the patch description and append a "committed by: $USER\non: $DATE" line. Would that be good?

Replying to [warner](/tahoe-lafs/trac-2024-07-25/issues/978#issuecomment-75971): > it looks like this patch has already landed (although, as with darcs patches in general, I don't know when or who to thank for landing it). How would you like this to be different? I've been using git full-time at work for the past few months and I don't understand how this would be different with git. I suppose we committers could get into the habit of using "darcs amend --edit" to edit the patch description and append a "committed by: $USER\non: $DATE" line. Would that be good?
zooko commented 2010-07-18 03:02:33 +00:00
Author
Copy Link

Replying to [zooko]comment:12:

I suppose we committers could get into the habit of using "darcs amend --edit" to edit the patch description and append a "committed by: $USER\non: $DATE" line. Would that be good?

I've started experimenting with doing this, e.g.: changeset:968edfda119cb29c where I committed a patch of François's after adding NEWS and CREDITS to it and editing the patch description to say I committed it on this date. One consequence of this is that if you got François's original patch (from him directly or by downloading it from the ticket) then his will conflict with mine so you have to throw his away (with darcs obliterate before pulling mine.

Replying to [zooko]comment:12: > > I suppose we committers could get into the habit of using "darcs amend --edit" to edit the patch description and append a "committed by: $USER\non: $DATE" line. Would that be good? I've started experimenting with doing this, e.g.: changeset:968edfda119cb29c where I committed a patch of François's after adding NEWS and CREDITS to it and editing the patch description to say I committed it on this date. One consequence of this is that if you got François's original patch (from him directly or by downloading it from the ticket) then his will conflict with mine so you have to throw his away (with `darcs obliterate` before pulling mine.
tahoe-lafs modified the milestone from 1.8β to soon 2010-09-10 21:00:01 +00:00
davidsarah commented 2010-11-12 21:47:24 +00:00
Owner
Copy Link

Packaging argparse, zbase32, and pycryptopp for Debian is a duplicate of #769.

Packaging argparse, zbase32, and pycryptopp for Debian is a duplicate of #769.
tahoe-lafs added the
fixed
 label 2010-11-12 21:47:24 +00:00
davidsarah closed this issue 2010-11-12 21:47:24 +00:00
tahoe-lafs modified the milestone from soon to 1.7.0 2014-11-27 04:03:46 +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
1.7.0
Assignees
Clear assignees
No Assignees
warner
5 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#978
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?