gitian: more specific default instructions #25
Conversation
gitian-building.md
Outdated
|
|
||
| At any time you can check the package installation and build progress with | ||
| In order to sign gitian builds on your host machine, which has your PGP key, fork the gitian.sigs repository abd clone it on your host machine: |
Sjors
force-pushed
the
2018/02/gitian-easier-instructions
branch
from
e262144 to
a8c129b
Compare
|
Fixed the typo @dmiller79 pointed out, and improved a few phrases. |
|
Concept ACK. Am setting Bitcoin Gitian builds right now and had forgotten a thing or two. Will take a closer look at the docs tonight or tomorrow and provide some feedback. EDIT: Maybe I'm missing something, or running something that doesn't work with these directions (I'm using VMware Fusion and not VirtualBox, for the record), but these directions just don't work for me on Debian 8.10. This is what I see when I run |
|
@droark can you make a separate Github issue for those errors? I don't think it's related to the changes I'm proposing here. You may also want to hop on IRC #bitcoin-core-dev, as debugging Gitian machines can take some back and forth. |
|
@Sjors - Thanks. I'm actually going to talk to one of the guys at the gitian-build team and see if he can pinpoint what's going on. I'll report back either way, and open a new PR if necessary after hopping on IRC. |
|
Needs rebase @Sjors |
Sjors
force-pushed
the
2018/02/gitian-easier-instructions
branch
from
a8c129b to
c018d64
Compare
|
Rebased |
|
Thanks for working on this - I think this is an improvement, so I'm going to merge it, we should try to keep some momentum here. |
c018d64 gitian: more specific default instructions (Sjors Provoost) Pull request description: Fixes #9, #10, #11, #13 and #18 A bit more opinionated on what the default approach is, which should make this easier for first time gitian builders. One thing I'm not yet happy about is how to move the assert files to the users real machine and then sign them. I have a half baked [script](https://gist.github.com/Sjors/ea4578dba596767c5e104ee4aaab09ce) for that, and I remember someone else is working on using a git remote for it. The instructions in this PR just tell the user to do it manually. Tree-SHA512: 21ef3552a69161f4df1289feb3f727702ad636bfbc866b7b7950cd12dc247725eb7a67daf8365673ec76efdc57d15506fe9a87e7dc6364a6493523168eb116a1
Fixes #9, #10, #11, #13 and #18
A bit more opinionated on what the default approach is, which should make this easier for first time gitian builders.
One thing I'm not yet happy about is how to move the assert files to the users real machine and then sign them. I have a half baked script for that, and I remember someone else is working on using a git remote for it. The instructions in this PR just tell the user to do it manually.