log☇︎
700+ entries in 0.051s
bvt: asciilifeform: fished out some info re aws: http://p.bvulpes.com/pastes/koCFa/?raw=true (small patch for musl compat) and http://p.bvulpes.com/pastes/avKyY/?raw=true (build instructions) seem to be it
asciilifeform: em. that way could fill it up with recents (e.g. diana_coman's v sigs; asciilifeform's last 'm' patch/sig) w/out hassling phf
lobbesbot: phf: Sent 1 week, 4 days, 13 hours, and 21 minutes ago: <asciilifeform> will [http://btcbase.org/patches] [patch viewer] ever get [http://btcbase.org/log/2019-07-24#1924501] [fed] !? and how about [http://btcbase.org/log/2019-07-22#1924232] You've given me 5 invalid commands within the last 60 seconds; I'm now ignoring you for 10 minutes. ?! where didja go, phf ? feeding the fish ?
lobbes: it would be a patch off of the command_router_python, however
asciilifeform: for ref: 'who-gave' patch. ☝︎
asciilifeform: hmm dorion why didja build w/out the de-truncation patch ?
a111: Logged on 2019-07-29 00:26 asciilifeform: http://btcbase.org/log/2019-07-28#1925256 << btw found shortly after posting that the 1-slot cache is not functional in the given patch. might fix, at some pt, but currently finding difficult to justify putting moar sweat into beating of the dead horse
asciilifeform: http://btcbase.org/log/2019-07-28#1925256 << btw found shortly after posting that the 1-slot cache is not functional in the given patch. might fix, at some pt, but currently finding difficult to justify putting moar sweat into beating of the dead horse ☝︎☟︎
asciilifeform: !Q later tell phf will patch viewer ever get fed !? and how about logotron genesis ?! where didja go, phf ? feeding the fish ? ☝︎☝︎
asciilifeform: orig. thought, like idjit, that it wouldn't even need the cache from the 2nd patch
diana_coman: BingoBoingo: the mp-wp on younghands.club seems to be still stripping all tags; is it deployed without the patch or what?
a111: Logged on 2019-07-22 20:12 mp_en_viaje: lobbes, you'll live. anyway, get that thing published so others can patch on it and thus lighten your own workload!
mp_en_viaje: lobbes, you'll live. anyway, get that thing published so others can patch on it and thus lighten your own workload! ☟︎
a111: Logged on 2018-04-19 05:55 mircea_popescu: so your plan for the ~rest of your life is to sit on a patch of dirt in ok and basically wait ?
diana_coman: in the patch (it's p2.vpatch in there), it's clear that the hashes are the same for the file so it IS the same file.
diana_coman: here's the test patch and the run, respectively: http://p.bvulpes.com/pastes/oxfeV/?raw=true and http://p.bvulpes.com/pastes/kLwrq/?raw=true
asciilifeform: where if you snip a MB, ~that patch~ now weighs 1MB+
a111: Logged on 2019-07-19 14:52 mp_en_viaje: http://btcbase.org/log/2019-07-19#1923552 << exactly. it is marginally better than merely dropping portage on their head ; and it is ideologically defensible because guess what, if they don't like the genesis they don;t have to either patch on it or press it.
a111: Logged on 2019-07-19 12:51 asciilifeform: trinque: it's 'gordian knot' that has to be cut ~somehow~. consider, as of yet asciilifeform cannot vtronicize that kernel patch, cuz... no kernel genesis.
asciilifeform: ( lotsa things that oughta be in it, tho, aint -- e.g. ave1's gnat, my kernels, etc. cuz nuffin to patch against )
mp_en_viaje: http://btcbase.org/log/2019-07-19#1923552 << exactly. it is marginally better than merely dropping portage on their head ; and it is ideologically defensible because guess what, if they don't like the genesis they don;t have to either patch on it or press it. ☝︎☟︎
diana_coman: so how do you suggest to start? because even if I have this ebuild, I can't patch it because effectively, no sources so what am I patching exactly, just the ebuild script? how does that help?
asciilifeform: trinque: it's 'gordian knot' that has to be cut ~somehow~. consider, as of yet asciilifeform cannot vtronicize that kernel patch, cuz... no kernel genesis. ☟︎
mp_en_viaje: http://btcbase.org/log/2019-07-19#1923461 << gb size PATCH yes, and is forbidden. GB sized GENESIS not the same thing at all. plox to not confuse vpatch and genesis! patch says, "this is a change i'm making to an item, plox judge ~the change~. not the item. the item is taken for granted". gensis says, "this is an item i'm proposing ; please judge it". ☝︎
asciilifeform: fortunately all needed to patch this, is ordinary drill.
asciilifeform: girlattorney: there is not currently such a knob. no one has felt pressing desire for it; if you wanna submit patch -- folx will read.
asciilifeform: the other variant is to do a la trb, genesis e.g. 3.70.16 (arbitrary, happens to be what i had around during 1st test) and ~then~ cut, a la trb. but it is gargantuan , would make trb genesis look microscopic in comparison, viewing the genesis patch in e.g. phf's viewer will prolly crash most www browser..
asciilifeform: mp_en_viaje: had same thought re that kernel patch -- wtf to do with it, it aint a vpatch, nao need genesis of kernel, so then which, etc
mp_en_viaje: diana_coman, the "include source in vpatch" is not merely re dependency, it's also "how do i meaningfully patch against absent code ?" and even "how the fuck am i supposed to display this ??"
mp_en_viaje: maybe just make it a patch ? or whatever, i get that you mean well, but sometimes you manage to always get your fingers caught under this sort of furniture.
mp_en_viaje: more to the point : why ~the fuck~ would you want to spend your time "hand-helping" someone on "how to install an improper patch" in preference of, spending the same time making it a proper fucking patch, which has the side benefit that now you don't have to hold their hand.
asciilifeform: i dun even have that patch on my hdd, turns out
mp_en_viaje: http://btcbase.org/log/2019-07-17#1922917 << for what it's worth im well irritated by all this out-and-out saboteur work of subversion, "oh, there's been this improper patch for years now that we keep deliberately maintaining improper and keep mentioning" nonsense. ☝︎
asciilifeform: ( i expect one can use any whatsoever. my patch will only cleanly work with 2.6+, 2.4.x had very different api for deviceisms )
asciilifeform: kernels, however, no hard limit found yet, erry 3.x seems to work (with my patch)
a111: Logged on 2019-07-16 21:52 asciilifeform: re that kernel -- someone gotta genesis a kernel. ( if no one has any constructive input re ~which~ one, then i will, and it will be somewhat arbitrary. ) atm that patch is a bad-old-style patch, rather than vpatch.
a111: Logged on 2019-07-16 22:16 mod6: http://btcbase.org/log/2019-07-16#1922542 << There is a patch that is not part of the main TRB vtree that does this, but it'll have to be patched in manually. And it most likely would need to be "re-ground" to apply cleanly ontop of your current pressed tree. However, if we can find a time where we could work together on it, I might be able to help you get that part going.
mod6: http://btcbase.org/log/2019-07-16#1922542 << There is a patch that is not part of the main TRB vtree that does this, but it'll have to be patched in manually. And it most likely would need to be "re-ground" to apply cleanly ontop of your current pressed tree. However, if we can find a time where we could work together on it, I might be able to help you get that part going. ☝︎☟︎
asciilifeform: re that kernel -- someone gotta genesis a kernel. ( if no one has any constructive input re ~which~ one, then i will, and it will be somewhat arbitrary. ) atm that patch is a bad-old-style patch, rather than vpatch. ☟︎
asciilifeform: girlattorney: in my experience, trb (with my 'aggression' patch) syncs from 0 in roughly 3wks, on a decent (fiber) pipe. however, last did this yr+ ago, and unsurprisingly the interval will only ever increase, as the chain gets heavier (on avg., grows 1000000 bytes erry 10min, recall)
mp_en_viaje: wanna write a patch ?
girlattorney: yes i've got that patch
bvt: asciilifeform: i have built ave1gnat with mipsel-sf support with a small patch (http://bvt-trace.net/src/gcc-4.9.adacore2016-4-mipsel.diff) -- adacore has snipped those files from their source distribution.
mircea_popescu: i mean, maybe all local wot failed to sign a patch portage deemed essential so it downloaded it from power-rangers.net. yes ?
asciilifeform: the problem of 'ifdef' is the clusterfuck where i am given to sign a patch that includes '#ifdef vax' but i dun have a vax. and dun intend to.
asciilifeform: it's the ebuild equiv of orig 'patch''s 'merging'
asciilifeform: ( it still, grr, won't stay up moar than 3-4 wks in 1 go tho, i'ma have to patch it when trinque publishes his reconnectism patch )
spyked: so far I've been looking at the project changelog and the patch history and the patches seem like a mixed bunch, with (perhaps) some useful things and breakage a la sslism. so before going further, I'd like to get some idea of what version of hunchentoot the lordship and the L2 are using
asciilifeform: nocredit: the reason your log consists 80+% of 'discarded block' is that trb deliberately does NOT hold on to a received block unless it matches the litmus for possibly being the immediately next block in the chain. this is deliberate, and i personally wrote this patch.
nocredit: hi, thanks for the voice. Basically trb (with aggressive patch) simply is too slow to sync, and i'm using a VULTR vps with 6 cores and 16GB of ram. For too slow i mean that after 1 week is just at block height 300k
mod6: I hope I'm not doing anything redundant really. The Makefiles itself take care of the compilation of Boost/BDB/OpenSSL. The one thing that I still need from the rotor.tar.gz is 'openssl-004-musl-termios.patch'
asciilifeform: i may be thick, but it is not evident from the patch
asciilifeform: nicoleci, mp_en_viaje : i have possible piece for this puzzler : asciilifeform's old notes suggest that this particular heathen pit structures text for censors as 'patch' deltas
mp_en_viaje: stjohn_piano_2, why not make a mp-wp tree patch then ?
asciilifeform: bvt: i had it overheat ~immediately when put under load with the 'rms coreboot', so went back to vendor's ( with above patch, or can't use civilized nic in it )
a111: Logged on 2019-05-06 09:44 phf: spyked: http://thetarpit.org/posts/y03/05c-development-log-i.html#selection-147.0-153.252 << i've used araneida for early btcbase, i've dropped it in transition from cmucl, but i'd say that it's the least encumbered of the bunch. i don't remember it having any "administration interfaces". it's written in the late 90s hacky style, and it's missing functionality (for example i wrote entire form parsing logic when i was trying to add patch
phf: spyked: http://thetarpit.org/posts/y03/05c-development-log-i.html#selection-147.0-153.252 << i've used araneida for early btcbase, i've dropped it in transition from cmucl, but i'd say that it's the least encumbered of the bunch. i don't remember it having any "administration interfaces". it's written in the late 90s hacky style, and it's missing functionality (for example i wrote entire form parsing logic when i was trying to add patch ☟︎
Mocky: supposing that a0, a1 etc. are host names and b0 etc are ip addresses, and further suppose that at time t2 a1 becomes unreachable at b2 and reachable at b1 (precipitating the patch a t2) then there are now no nodes in the flow going all the way out to t5 and beyond where both a0 and a1 would be reachable if pressed
Mocky: mp, I can make my point using your flow if you allow a slight change to the patch at t1, such that instead of 'a0 -> b0, a1 -> b2' it does 'a0 -> b9, a1 -> b2'.
mp_en_viaje: At t2, there is a patch upon t0#t0, transforming gns to a1->b1 ; manifest becomes #t1. this is signed by A, Q, G, B, N, I.
mp_en_viaje: At t1, there is a patch upon t0#t0, transforming gns to a0 -> b0 ; a1 -> b2 ; manifest becomes #t1. this is signed by A, W, F, G, U, K.
diana_coman: and a sig on a patch to my mind can't anyway be in isolation like that, "just this patch here is fine but I have no idea of what is being patched"
Mocky: what would it even look like pressing to multiple heads at the same time? how can you get the updates in both patch 1 and 2 if they are siblings?
Mocky: so re your patches example, if patch 2 & 3 both declare patch 1 as parent, and I have wot keys for all a - f, I can't press to both heads correct?
mp_en_viaje: whereas someone who has only b should patch, i suppose, on both 2 and 3.
mp_en_viaje: whereas patch 4 made by someone whose seal list is b c should be on 3
mp_en_viaje: so if there's say people a - f and patches counted numerically, supposing you have 1(a-f) -> 2(a, b) / 3 (b c d e f), patch 4 for someone who has a seals list made up of a, b should be on 2,
a111: Logged on 2019-05-03 03:18 Mocky: http://btcbase.org/log/2018-11-24#1874402 << this suggests that each key holder can only host $key/gns at one ip address. And what about vpatch ordering and the v manifest file? If i have an entry for archive.is and want to change that entry, I can't just make and sign a patch of my own, i have to patch on top of the 'consensus' press, otherwise manifest won't match and can't press multiple heads. Am I wrong about how that works?
Mocky: http://btcbase.org/log/2018-11-24#1874402 << this suggests that each key holder can only host $key/gns at one ip address. And what about vpatch ordering and the v manifest file? If i have an entry for archive.is and want to change that entry, I can't just make and sign a patch of my own, i have to patch on top of the 'consensus' press, otherwise manifest won't match and can't press multiple heads. Am I wrong about how that works? ☝︎☟︎
a111: Logged on 2019-05-01 14:46 asciilifeform: ( and iirc even there, had to hand-patch the module sores so it'd reset properly )
asciilifeform: ( and iirc even there, had to hand-patch the module sores so it'd reset properly ) ☟︎
a111: Logged on 2016-11-14 12:58 mircea_popescu: (likely the patch will come in the shape of a dnsmasq clone, which will handle stuff like "tld" as well as things like http://btcbase.org/log/2016-11-12#1566482 via settings etc)
lobbesbot: PeterL: Sent 1 day, 16 hours, and 28 minutes ago: <billymg> yup, if you want the patch that fixes svg image links you can grab mp-wp_update-image-references-to-svg from here http://btcbase.org/patches?patchset=mp-wp&search= - although i recommend going for the latest patch on that page
a111: Logged on 2019-04-20 19:59 billymg: anyway, i updated php on my server to include gd and it indeed works fine. so for now the latest patch for mp-wp is the one i personally recommend/support
billymg: anyway, i updated php on my server to include gd and it indeed works fine. so for now the latest patch for mp-wp is the one i personally recommend/support ☟︎
a111: Logged on 2019-03-31 19:37 billymg: this _may_ be a result of the patch, in which case a regression. will dig in
billymg: http://btcbase.org/log/2019-03-31#1906362 http://btcbase.org/log/2019-03-31#1906383 << for anyone waiting in suspense, i was able to confirm that this was _not_ a regression from the patch removing tinymce ☝︎☝︎
a111: Logged on 2019-04-07 16:04 asciilifeform: http://btcbase.org/log/2019-04-07#1907304 << i formerly thought that this was obvious from the docs , but you ~can~ operate on vpatches without a vtron ( they're edible by trad. unix 'patch' util, and you can verify the sigs with anyffin roughly gpg-like , also by hand )
asciilifeform: http://btcbase.org/log/2019-04-07#1907304 << i formerly thought that this was obvious from the docs , but you ~can~ operate on vpatches without a vtron ( they're edible by trad. unix 'patch' util, and you can verify the sigs with anyffin roughly gpg-like , also by hand ) ☝︎☝︎☟︎
billymg: this _may_ be a result of the patch, in which case a regression. will dig in ☟︎
billymg: do you know if this was a regression in this patch?
billymg: Mocky: updated mp-wp patch and sig available here: http://billymg.com/downloads/mp-wp/mp-wp_remove-tinymce-and-other-crud.vpatch http://billymg.com/downloads/mp-wp/mp-wp_remove-tinymce-and-other-crud.vpatch.billymg.sig
asciilifeform: phf: i found & removed the last uniturd ( was in the manifest.txt , from the day i made it ) . this however means that there in fact lies a uniturd in the 18 patch ( the removal line , naturally . ) after this i expect no moar .
a111: Logged on 2019-03-27 21:23 Mocky: billymg: if your tinymce patch is ready this weekend I'll test it with my setup.
billymg: in terms of test suite, i didn't actually write any automated tests for mp-wp, i only meant the manual testing i did, plus reading my own patch a few times
a111: Logged on 2019-03-27 17:14 mircea_popescu: billymg, if you're happy with it, one thing you could do is patch your testing suite as an alternate patch off mp-wp genesis ; this way people looking to test can just use it (and patch atop it if need be) rather than write from scratch.
billymg: http://btcbase.org/log/2019-03-27#1905107 < i like the idea of a dev branch alongside a production branch. is the idea that after after a patch (or set of patches) is deemed mature enough it will then be added to the main branch? ☝︎
asciilifeform: patch also cut & signed . is pretty large at ~50kB , but actually ranks behind ch14, 15, 11 (not speaking of genesis/1 lol)
mircea_popescu: asciilifeform, i'd say you found the first meaningful patch to be put on the fg tree.
Mocky: billymg: if your tinymce patch is ready this weekend I'll test it with my setup. ☟︎
mircea_popescu: billymg, if you're happy with it, one thing you could do is patch your testing suite as an alternate patch off mp-wp genesis ; this way people looking to test can just use it (and patch atop it if need be) rather than write from scratch. ☟︎
billymg: a freshly pressed copy of the divergent patch found here http://btcbase.org/patches?patchset=mp-wp&search= has been running on my blog since sunday though
billymg: Mocky: i plan to have my recent remove-tinymce patch updated to go on top of hanbot's this weekend, if you'd like to use for http://btcbase.org/log/2019-03-27#1904998 ☝︎
bvt: linux bootstrap with actual mes is way more disappointingto stage0 components (the claim is 'c compiler is scheme and scheme interpreter in c', but in fact they require bash, patch, tar, etc. for the bootstrap).
hanbot: http://btcbase.org/log/2019-03-25#1904731 << http://thewhet.net/2019/03/mp-wp-patch-for-enabling-html-comments/ ; updated phf billymg mircea_popescu et al. ☝︎
hanbot: meanwhile billymg phf mircea_popescu et al my patch from last night needed a reground, sorry for the pain in the ass. http://thewhet.net/2019/03/mp-wp-patch-for-enabling-html-comments/
mircea_popescu: http://btcbase.org/patches?patchset=mp-wp&search= << keks they ended up diverged. normally i'd ask hanbot to regrind, except this is a large patch that needs some reading, so would you mind regrinding it on top of hers billymg ?
feedbot: http://thewhet.net/2019/03/mp-wp-patch-for-enabling-html-comments/ << The Whet -- MP-WP Patch for Enabling HTML Comments
billymg: the patch removes tinymce, most of the importers, and some unused plugins -- overall reduction of about 15% in lines of code and close to 20% in size on disk (since some of the files removed were minified files containing only one line)
billymg: hanbot, mircea_popescu, anyone else interested: i just finished deploying the latest mp-wp patch to my site and published the files here http://billymg.com/mp-wp-vtree/