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

[zooko]

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

[ioerror]

# 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]

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

[ioerror]

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]

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]

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]

Oops, wikiformatting ate my underscores. That should read

sed -i -e 's/__file__/"."/' setup.py

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

[davidsarah]

The patch was applied in 8fddc7a4a5cf4f69. Leaving open to address comment:6 and comment:8.

[zooko]

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?

[zooko]

Replying to zooko:

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

[davidsarah]

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