Matches for v.pl, 55 total results Sorted by newest | relevance
Sun Feb 21 20:23:53 UTC 2016 <jurov> not entire. just occassional problems with perl scripts like v.pl and autotools
Sun Oct 11 23:13:32 UTC 2015 <mod6> found a bug. will fix on next time posted. for now; after `./v.pl init http://thebitcoin.foundation` is run, run `./v.pl w` to ensure all of the WoT's get imported to the keyring.
Fri Oct 23 17:52:21 UTC 2015 <jurov> got v.pl working.. now you want the poor listbox in lxr to show *all* patches ever?
Sun Oct 25 20:39:22 UTC 2015 <mod6> asciilifeform: Cucumber tests are automated tests that will run specified scenarios against v.pl and assert various outcomes. [cucumber.io]
Tue Dec 22 20:35:12 UTC 2015 <mod6> and the subsequent commands would just do something like `./v.pl p TEST2 vpatchnameforhead wd /.../rotor/.wot` or something.
Fri Jan 29 16:49:15 UTC 2016 <punkman> you can't apply two patches that modify the same thing, at least in newer v.pl that checks hashes
Sun Jan 31 00:37:03 UTC 2016 <mod6> <+jurov> even v.pl, for that matter... :) << this is available in the ML & on the foundation homepage.
Sun Jan 31 02:01:59 UTC 2016 <mod6> just create a 'patches' and '.seals' dir in the same dir as v.pl and you're golden
Sun Jan 31 07:14:31 UTC 2016 <punkman> http://log.bitcoin-assets.com/?date=30-01-2016#1390083 < might be good as a separate utility. cuts down on v.pl dependencies too.
Sun Jan 31 20:32:38 UTC 2016 <ben_vulpes> http://log.bitcoin-assets.com/?date=31-01-2016#1391245 << lines 64 and 65 of v.pl. perhaps i can't read perl?
Thu Feb 04 03:57:41 UTC 2016 <mod6> so you ran something like `./v.pl p v foobar non-existing.vpatch` and then something ends up in foobar?
Sun Feb 21 20:15:53 UTC 2016 <mod6> are you in / when executing V, by doing something like `/path/to/where/V/is/actually/located/v.pl`
Wed Feb 17 03:30:02 UTC 2016 <mod6> so what would be great here, is if you apply the patch, or use the v.pl attached to the email (check the sigs ofc), then start clean, do a fresh `./v.pl i http://thebitcoin.foundation`, and then press out the entire tree, `./v.pl p v v054 asciilifeform_maxint_locks_corrected.vpatch`, then `cd v054` and run that find command at the top of this pastehttp://dpaste.com/2SQ1VZ7.txt
Tue Dec 22 02:00:31 UTC 2015 <mod6> <+trinque> http://deedbot.org/build-bitcoind-99997K.sh << If Mr. P. used this, then it does this (in the script): ./v.pl p verbose TEST2 asciilifeform_add_verifyall_option.vpatch
Sun Jan 31 21:56:45 UTC 2016 <ben_vulpes> anyways, mod6 you gotta upgrade v.pl to press *all* reachable leaves. that's the problem i'm running into with asciilifeform's recent shiva rebake
Tue Feb 02 20:43:40 UTC 2016 <mircea_popescu> ok well. they're all 3 identical : the v, the v-0001 of mystery and the v.pl on the actual machine that pressed with it
Sat Feb 13 02:04:27 UTC 2016 <mod6> when he built it, it ~should~ have included your original malleus patch, see: ./v.pl p verbose rotor/TEST2 asciilifeform_malleus_mikehearnificarum.vpatch
Sun Oct 11 21:08:58 UTC 2015 <mod6> Ok, so I've posted my version of V for some review before it goes to the ML. Inside the archive you'll find a `v.pl', `v_quick_start.txt', and `v_users_manual.txt' - and each with a corresponding sig.
Thu Nov 12 02:23:02 UTC 2015 <mod6> whaack: hi, yeah thanks for asking. 'v.pl' could certainly use some testing help. additionally, when I get my rotor+v script finished (hopefully soon), will have that to test as well.
Fri Jan 15 00:49:17 UTC 2016 <mod6> ;; later tell PeterL hey, the version of 'v.pl' that you have looks correct to me. the issue is that you have the pubkeys named incorrectly, try with 'mod6.asc', 'ben_vulpes.asc', 'asciilifeform.asc' and 'mircea_popescu.asc'