61 entries in 1.758s
jfw: I confess I mostly run 'patch' by hand, but
v.pl modified for
keccak or any other supporting same should work.
diana_coman: my frozen snapshot in the
starter_v is a press only up to vtools_ksum and I think it's time for an updated version really
mod6: trinque: Speaking of an ebuild for ave1's musltronic tools, I've got one that works. I've also got one for diana_coman's
keccak V tools package.
mircea_popescu: hanbot, the file is correct. the expected hash (3e43*) matches the
keccak hash of that file ; the actual hash (05f5*) matches the sha hash of that file. you are for some reason using a sha
v for this ?
hanbot: right right, i mixed 'em up. and yeah, i'm planning on grabbing phf's
keccak v.py in step 3, if only because i've seen diana_coman's pop up in cuntoo tests so i'd like to test the ver less traveled.
hanbot: in bootstrapping adventures, it looks like the flow for a machine that knows to
v to get vtools going is like so: grab some ancient
v, ie mod6's
v.py, use it to press phf's vtools vpatch, then eat phf's
v.py "updated for vtools", then press vtools to
keccak head. anyone feel like spotting this for me?
mod6: I'm currently building out a Cuntoo (have had a minor issue with my kernel not booting correctly, but will work on that soon), and will use that + ave1's musl to build the
keccak v tooling, and then TRB. Which will also go into the upcoming changes to the HOWTO Guide.
billymg:
http://btcbase.org/log/2018-12-27#1883449 < quick update: using diana_coman's
keccak-compatible
v.pl, the vpatch i posted before pressed without issue. will write up a blog post with details on the patch, and another post with the patch for the svg file links
☝︎ billymg: yeah, i think i'm using a
keccak version vdiff for creating the patch, but attempting to press with a sha
v.py
billymg: diana_coman: my understanding was that as long as i created the vpatch with a
keccak-compatible vdiff then the hashes would be consistent with genesis and it would be ok. this assumption came from me being able to press vtools and mp-wp with my current
v.py (grabbed from the link in the trb setup guide)
billymg: ok, updated and it now presses but when i inspect the resulting directory the changes aren't there (it also came with an error i saw before on genesis, about a file's hash not matching expected -- i assumed this was because my
v.py is pre-
keccak)
a111: Logged on 2018-11-14 10:54 diana_coman: and done: the updated .vpatch files and starter_v.zip + sigs are all up; I've checked them on my RK; genesis is the same and result is identical to
V-2017; the result of 99993 .vpatch is identical to
V-2018; the result of keccak_vtools vpatch is to update BOTH docs and code; re docs, I've nuked the user manual as I won't maintain it and it's becoming confusing due to being out of date; I've updated the quick_guide however, mainly for 1st t
diana_coman: ime users really; re .zip file: the
v in there is precisely what one gets by pressing my v_keccak_vtools.vpatch
diana_coman: and done: the updated .vpatch files and starter_v.zip + sigs are all up; I've checked them on my RK; genesis is the same and result is identical to
V-2017; the result of 99993 .vpatch is identical to
V-2018; the result of keccak_vtools vpatch is to update BOTH docs and code; re docs, I've nuked the user manual as I won't maintain it and it's becoming confusing due to being out of date; I've updated the quick_guide however, mainly for 1st t
☟︎ diana_coman: fwiw the
keccak-version of
v (i.e. pressing the tree I published all the way to its leaf) IS the corrected one re pressing order ; later today I'll do a diff with precisely the versions mod6 has at
http://thebitcoin.foundation/v/ but going by version number I really don't see what "old version" are you saying
phf: i've narrated how to make
v.pl work with
keccak, i think i even posted an unsigned patch for mod6, butman is busy
a111: Logged on 2018-09-27 15:36 phf: asciilifeform: but if you want a full "
v replacement and i don't want to think about none of that" then just use esthlos's item. i believe he has a working
keccak already
phf: when i started working on vtools there was already a handful of battle tested
V implementations, that relied on vdiff.sh/gnu patch combination. vtools is a "drop in" replacement for the later. you get valid vpatch on the input, valid press on the output. the purpose is to nail down the format, and gradually replace out its parts (e.g. transparent sha->
keccak transition)
phf: asciilifeform: but if you want a full "
v replacement and i don't want to think about none of that" then just use esthlos's item. i believe he has a working
keccak already
☟︎ a111: Logged on 2018-09-26 18:48 asciilifeform: and incidentally i flatly refuse to have
keccak patches on my box that are not outwardly distinguishable from old
v. i'ma either use .
v extension, or if mircea_popescu entirely hates, i'ma stuff e.g. asciilifeform_keccak in the names ( names currently not constrained by anybody )
diana_coman: asciilifeform, since your udp genesis is using the sha hashes + a "history" file I'm not sure: do you have something against the move to
keccak + standard manifest file for
v-trees?
diana_coman: mircea_popescu, it's not a
v.pl problem really at any rate; it wasn't directly clear
keccak hashes and yest was a long day here
diana_coman: hanbot, right, it's
keccak hashes so ofc
v.pl barfs although it's weird that it first presses so much of it and only then randomly throws up; at any rate, on different arch, phf's vpatch pressed the mp-wp genesis so at least the genesis itself seems all right
esthlos: trinque: yes it does, I'm trying not to overcommit but could definitely add once the
Keccak/
V stuff is off my plate
a111: Logged on 2018-04-09 04:25 hanbot: phf et al: attempted to press latest vtools to the
keccak head.
v (mod6's) reports vtools_vpatch_newline not in flow, neither its antecedent vtools_fixes_static_tohex, despite both patches and (verified good) sigs present (they neither show up via flow command).
v will press to vtools_vpatch.vpatch, but no further. see
http://p.bvulpes.com/pastes/oNRhE/?raw=true .
a111: Logged on 2018-04-09 04:25 hanbot: phf et al: attempted to press latest vtools to the
keccak head.
v (mod6's) reports vtools_vpatch_newline not in flow, neither its antecedent vtools_fixes_static_tohex, despite both patches and (verified good) sigs present (they neither show up via flow command).
v will press to vtools_vpatch.vpatch, but no further. see
http://p.bvulpes.com/pastes/oNRhE/?raw=true .
a111: Logged on 2018-04-09 04:25 hanbot: phf et al: attempted to press latest vtools to the
keccak head.
v (mod6's) reports vtools_vpatch_newline not in flow, neither its antecedent vtools_fixes_static_tohex, despite both patches and (verified good) sigs present (they neither show up via flow command).
v will press to vtools_vpatch.vpatch, but no further. see
http://p.bvulpes.com/pastes/oNRhE/?raw=true .
hanbot: phf et al: attempted to press latest vtools to the
keccak head.
v (mod6's) reports vtools_vpatch_newline not in flow, neither its antecedent vtools_fixes_static_tohex, despite both patches and (verified good) sigs present (they neither show up via flow command).
v will press to vtools_vpatch.vpatch, but no further. see
http://p.bvulpes.com/pastes/oNRhE/?raw=true .
☟︎☟︎☟︎ a111: Logged on 2018-01-18 20:58 mircea_popescu: consider concretely the case of eucrypt's
keccak. diana_coman is writing it as a direct derivation off genesis, meaning on extant
v impls if one wanted to import it they could import JUST it, without the rest of eucrypt (it'll be pulled in later through the usual procedure in eucrypt itself). superficially this may seem like it encourages phf to go "o i know, i'll just link
keccak patch into my codebase rather than regring (i
mircea_popescu: consider concretely the case of eucrypt's
keccak. diana_coman is writing it as a direct derivation off genesis, meaning on extant
v impls if one wanted to import it they could import JUST it, without the rest of eucrypt (it'll be pulled in later through the usual procedure in eucrypt itself). superficially this may seem like it encourages phf to go "o i know, i'll just link
keccak patch into my codebase rather than regring (i
☟︎ a111: Logged on 2017-11-15 18:43 diana_coman: and re peterl's
keccak implementation trouble is that thoroughly testing it looks atm as much work as writing a new one in the process anyway so whatever version ends up with tests and everything is the one that will make it into
v too I would say
diana_coman: and re peterl's
keccak implementation trouble is that thoroughly testing it looks atm as much work as writing a new one in the process anyway so whatever version ends up with tests and everything is the one that will make it into
v too I would say
☟︎