2200+ entries in 0.197s
ben_vulpes: again, if i recall correctly, asciilifeform's v will press all of the same-leaf-level patches as the given
patch, /up to the given
patch (inclusive)/ in alphabetical order
ben_vulpes: as in, given this patchset, and this particular
patch, apply all of the antecedents in the correct order.
ben_vulpes: it's only ever made sense to me in the context of pressing a specific
patch.
phf:
patch Z takes a from 1 to 8, b from 3 to 4
phf:
patch Y takes b from 2 to 3
phf:
patch X takes a from null to 1, b from null to 2
phf: say you have two files, a b.
patch X takes a from null to hash 0 and b from null to hash 0
phf: note that the graph edge can actually have multiple different meanings. on mod6 graph, an edge means "patches share a common hash". on my graph edge means "
patch can be applied on top of other
patch without conflict"
mod6: if I use the raw
patch from the deal press pukes on an unmatched hash. (a new feature! lol)
mod6: no worries, just demonstrating with that paste that I was able to rebase the
patch, drop it into my 'patches' dir (notice the WILD annotation), and press cleanly.
shinohai: Yeah I had to
patch in by hand after press to get it working :/
mod6: you would have to have had all the latest pressed out, then
patch the code in by hand
mod6: so yeah, funks
patch needs to be rebased.
adlai assumes desired "8ball" is a C 'script' /
patch to upcoming 'werker', rather than web spider + sudden submission?
phf: flask is not standalone though, it's a wsgi service, which in turn is a python standard for doing "web application". there are competing servers for wsgi, uwsgi being most popular. i actually had to
patch it for my work production, and it's not a fits in head by any means
trinque: shinohai: if you're gonna use the wallet, you'll probably want mod6's
patch for -lows too
BingoBoingo: Will be replaced by btcbase once link can be translated. This is a working
patch.
phf: you can also arbitrarily
patch other people's words and claim authenticity
ben_vulpes: i've been wondering where that
patch got off to
phf: the point is not so much to
patch code in production (though it makes sense on lisp machine since there's no "non-production"), but to support repl-based development process
trinque: then appropriate to make a genesis v-
patch and deed
phf: quicklisp depends on asdf, in fact hard depends on asdf3. it takes exactly three places to
patch it to support 1.369 and it continues working
ben_vulpes: i press to confirm
patch validity and then commit the changes to my local version controlatron.
phf: mechanism has nothing to do with "mercurial" as such, and is more akin to old school
patch management system, "quilt"
phf: mercurial has a handy
patch management mechanism, that unfortunatly doesn't understand nor produces vpatches. i basically verify vpatches manually, and then put them into hg's
patch folder. then i do a topo sort, which gives me a mercurial compatible "series" file. i let mercurial press it using that series file. whole process is more complicated then should be with a proper mercurial support, but i hnfi how people rebase, refresh,
mrottenkolber: I am only mentioning the sha1 option because I don't understand crypto well enough to be able to rationalize the effort of producing a file, with the same sha1sum, with an exploit while the
patch still applies.
phf: mrottenkolber: a better place to wire v would be mercurial's mq facility. mercurial has a way of managing plaintext patchsets, to do things like
patch refresh, i.e update the contents of
patch from the current tree state, mercurial managed
patch press, i.e. instead of doing "manual" v press hg will keep track of state for you, etc. this will not be a way to share patches, as much as a way to facilitate vpatch authoring.
mrottenkolber: My point is the toposort isn't really part of the problem v solves. The function is to cryptographically verfiy a sequence of patches (based on a wot), who cares where that sequence comes from, as long as each
patch (commit) has a signature.
mod6: <+asciilifeform> this
patch has 'all signers: mircea_popescu trinque asciilifeform mod6' << i'll note that this signatures you're referencing are strictly for genesis.vpatch
assbot: Logged on 20-03-2016 15:04:05; phf: also anyone tried doing a kernel level key rebind before? is that just in config or you need to
patch source. i want to switch some keys around, but i don't want to have to do it for every single userland environment
phf: also anyone tried doing a kernel level key rebind before? is that just in config or you need to
patch source. i want to switch some keys around, but i don't want to have to do it for every single userland environment
☟︎ assbot: Logged on 19-03-2016 17:19:23; mod6: Does anyone else see these error messages running the latest trb (minus shiva)? Looks to be in main.cpp:ProcessMessage around lines 1855:1913. It doesn't look to me to be related to the malleus
patch, but I could be wrong there. Thoughts? Seen the same in your logs? Plz let us know.
http://dpaste.com/21PJMY4.txt mod6: Does anyone else see these error messages running the latest trb (minus shiva)? Looks to be in main.cpp:ProcessMessage around lines 1855:1913. It doesn't look to me to be related to the malleus
patch, but I could be wrong there. Thoughts? Seen the same in your logs? Plz let us know.
http://dpaste.com/21PJMY4.txt ☟︎ assbot: Logged on 18-03-2016 21:24:35; mircea_popescu: "The latter act conveys very little useful information, and no permanent sealed record remains of the effort taken to actually understand the
patch. This is a Bad Thing" << the thing with this asciilifeform is that on the surface i feel very moved by the notion ; but upon examination it seems to devolve into a sort of enumerating badness ?
mircea_popescu: "The latter act conveys very little useful information, and no permanent sealed record remains of the effort taken to actually understand the
patch. This is a Bad Thing" << the thing with this asciilifeform is that on the surface i feel very moved by the notion ; but upon examination it seems to devolve into a sort of enumerating badness ?
☟︎ mircea_popescu: trinque> thx to mod6 for the highs lows
patch, using lows is helping deedbot- keep track of his dust << win.
trinque: thx to mod6 for the highs lows
patch, using lows is helping deedbot- keep track of his dust
mod6: anyway, I see you
patch, thanks for posting. when I get around to making another version of V, i'll throw that in there.
phf: trinque: i say, press to polarbeard_remove_shrink_debug_file, then
patch -p1 < polarbeard_better_log_messages, then vpatch the result, then do same for polarbeard_add_getpeerinfo_rpc. that's sort of easiest, fastest way to regrind
trinque: funkenstein_: it makes more sense for you to make your own decisions about which patches you like, and if I don't like it I'm free to alter your
patch to suit me
assbot: Logged on 20-02-2016 23:42:04; mircea_popescu: you don't "release" a
patch.
funkenstein_: also if people don't like a
patch SN which you have in the base, they will not get to use your
patch PeterL: so if your
patch is not included, you have to keep rebasing it every time a new
patch is added until it does get included?
funkenstein_: asciilifeform, so if I would like to make/rebase a
patch.. i should take the longest chain I have seen as the base of the diff?
funkenstein_: lol anyway asciilifeform, got any comments about how you see
patch order established for V users?
assbot: Successfully added a rating of 1 for funkenstein_ with note: wrote a useful
patch for importprivkey
trinque: !rate funkenstein_ 1 wrote a useful
patch for importprivkey
trinque: !rate funkenstein 1 wrote a useful
patch for importprivkey
trinque: could also be the malleus
patch if that version of prb issues heathen commands
mircea_popescu: "This
patch also fixes a memory leak of opt.keyserver en passant." << first rule of koch, drepper, weiner & all nsa goons : ALWAYS bundle new vulns with memory leak fixes etc.
pete_dushenski: shinohai: and were you using polarbeard
patch for the privkey import ?
ben_vulpes: mod6: phf dumped a
patch in the logs for compiling under gcc
mod6: <+ben_vulpes>
http://log.bitcoin-assets.com/?date=02-03-2016#1419829 << with phf's
patch (are you going to post that to the ML or shall i?), my post-clean compile takes 1m 16s << im not aware of phf's
patch. i did recompile with shiva when it was first introduced, didn't add or subtract any compile time as far as I could tell.
☝︎ ben_vulpes: phf: consider linking to sigs from
patch page?
assbot: Logged on 28-02-2016 03:38:49; phf: 1) brew install cmake 2)
patch < foo.
patch 3) link_directories and include_directories in CMakeList.txt need to point to be modified to point to your boost/db4/openssl locations 4) mkdir foo; cd foo; cmake ..; make
phf: 1) brew install cmake 2)
patch < foo.
patch 3) link_directories and include_directories in CMakeList.txt need to point to be modified to point to your boost/db4/openssl locations 4) mkdir foo; cd foo; cmake ..; make
☟︎ ben_vulpes: so i should be able to leave the tinyscheme dir as tinyscheme? or am i screwing up royally in that my
patch applications don't result in a shiva dir?
assbot: Linux-Kernel Archive: [
PATCH] MPILIB: Provide count_leading/trailing_zeros() based on archfunctions ... (
http://bit.ly/1TB8sBW )
assbot: Logged on 08-03-2015 18:38:19; asciilifeform: ben_vulpes: short summary:
patch submitted by google chrome devs themselves; supposedly to simplify their sandbox 'jail' mechanism
phf: asciilifeform: he's asking about SchemeHook from polarbeard's
patch jurov: i updated glibc with the
patch phf: added
patch highlight to btcbase (got tired of trying to visually locate patches in the graph)
phf: dat
patch, can take them to water, can't make them drink
mircea_popescu: e old version directory before applying the
patch. Then run those commands yourself in the scratch directory."
mircea_popescu: "The simplest way to generate a
patch is to use ‘diff -Naur’ (see Tips for
Patch Producers), but you might be able to reduce the size of the
patch by renaming or removing some files before making the
patch. If the older version of the package contains any files that the newer version does not, or if any files have been renamed between the two versions, make a list of rm and mv commands for the user to execute in th