Matches for v.pl, 55 total results Sorted by newest | relevance
Wed Mar 16 23:42:59 UTC 2016 <mod6> <+trinque> mod6: what's the proper way to get you changes for v.pl? would be nice when press blows up to be told what vpatch barfed. want to just add that yourself? << hey, uumm... so yeah, i think it does tell you which one barfed on press. did you use (v | verbose) in there? or have a dpaste of what it did?
Wed Mar 16 17:48:44 UTC 2016 <trinque> mod6: what's the proper way to get you changes for v.pl? would be nice when press blows up to be told what vpatch barfed. want to just add that yourself?
Sun Feb 21 20:23:53 UTC 2016 <jurov> not entire. just occassional problems with perl scripts like v.pl and autotools
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`
Sun Feb 21 20:04:36 UTC 2016 <mod6> pwd is used iirc in v.pl, but only in the contex of it being a shell out - your environment should execute this and return the result to a scalar.
Sat Feb 20 21:36:21 UTC 2016 <mod6> <+jurov> mod6: trying under gentoo, v.pl complains "/.wot directory does not exist." << create your .wot in the same dir that you place the build script, create a log of your findings, and see what happens plz.
Sat Feb 20 19:58:25 UTC 2016 <jurov> mod6: trying under gentoo, v.pl complains "/.wot directory does not exist."
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
Sat Feb 13 02:24:16 UTC 2016 <mod6> ah yes: ./v.pl p verbose TEST2 asciilifeform_add_verifyall_option.vpatch
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
Tue Feb 09 15:34:30 UTC 2016 <mod6> ben_vulpes: here's a peek at the squshed beta 1 & beta 2 vpatches - unless something changes between now and tonight, i'll be sending this one to the ML. All you need to do to apply is get V [v99996], copy `v.pl' to `v.pl.v99996`, then place this patch in the same dir and do: `patch -p0 < V_v99995_beta2.vpatch` and give it a go
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?
Wed Feb 03 22:21:02 UTC 2016 <mod6> yah, that's how my sigs look for v.pl: v.pl.mod6.sig
Wed Feb 03 22:20:20 UTC 2016 <mircea_popescu> http://log.bitcoin-assets.com/?date=03-02-2016#1395431 << i dunno that i renamed anything when signing it. i thought thatg's how we do it, i take the original v.pl and turn it into v.pl.me.sig
Tue Feb 02 20:53:46 UTC 2016 <assbot> [BTC-dev] Certify v.pl 99996K ... ( http://bit.ly/1JWdlDL )
Tue Feb 02 20:53:13 UTC 2016 <mircea_popescu> anyway, im not doing a patch. im doing v.pl
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
Tue Feb 02 20:41:53 UTC 2016 <*> mircea_popescu goes to check, finds v.pl
Tue Feb 02 20:40:58 UTC 2016 <mod6> afaik i've always named the actual file `v.pl'
Mon Feb 01 05:13:01 UTC 2016 <assbot> Logged on 31-01-2016 21:56:45; 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