log☇︎
800+ entries in 0.067s
asciilifeform: ( ch18 patch is written, and the writeup will be also in the coming days -- but i'd like to finally have 8thbit-clean thing )
asciilifeform: phf: do you have the anti-utfism patch for vdiff from earlier thrd, or do i need to bake one
hanbot: billymg: these are the totality of your mp-wp patches, yes? http://billymg.com/2019/01/minor-mp-wp-patch-updates/ ; i don't recall anyone else having patches, please chime in if you do. meanwhile phf please add <--- to mp-wp tree, and i'ma solder these to the genesis after which danielpbarron i'd be happy to show you how to make a vpatch for your fix.
hanbot: danielpbarron excellent find. i suppose the apache upgrade's breakage of shared pizarro customers' .htaccess files ought to have been a giveaway here. anyway, impressive; ty. d'you wanna make a patch for this + the db name change in wp-comments-post.php diana_coman pointed out? otherwise i'll do eeit.
diana_coman: I would very much like a no-unicode check patch for vdiff.
asciilifeform: nao that i think about it, this function prolly belongs in vdiff, i'ma bake a patch for it
spyked: in work updates: feedparse is getting another patch today; and feedbot code has been heavily refactored and part one is on track to be published. it'll be a pretty heavy post, I'ma start working writing it tonight.
mircea_popescu: bflame how about you make yourself useful and implement a keccak as discussed ^ then patch diana_coman 's tree with it.
a111: Logged on 2019-03-10 19:44 phf: http://btcbase.org/log/2019-03-10#1901176 << i'll put it to the top of the stack, i remember fixing it, but never completing the patch.
a111: Logged on 2018-12-03 21:48 diana_coman: hm, if it's indeed the tmp thing, it might be worth a try to press vtools to current leaf (i.e. vtools_tempfile_standalone or _notmp) and see if that cures it; my archive contains pressed vtools to ksum patch only, not further
phf: http://btcbase.org/log/2019-03-10#1901176 << i'll put it to the top of the stack, i remember fixing it, but never completing the patch. ☝︎☟︎
a111: Logged on 2018-12-03 21:48 diana_coman: hm, if it's indeed the tmp thing, it might be worth a try to press vtools to current leaf (i.e. vtools_tempfile_standalone or _notmp) and see if that cures it; my archive contains pressed vtools to ksum patch only, not further
mircea_popescu: ben_vulpes 's display not included i dunno why ; phf's not included for the stated reason, obscure cl machine ; lobbes 's not included because in order to be able to patch it, he had to fix various things first, you were here for the "techniocal debt" discussion last year.
asciilifeform: http://btcbase.org/log/2019-02-24#1899016 << more boringly, item was born from trb work ( and specifically jurov's mailing list mechanism , with enforcement of patch signatures ) , i.e. 'hand-cranked v', so ended up on the trb ml. ☝︎
mircea_popescu: "So the busybox "dc" command was broken when I tried it, but Denys fixed it last night, so I can do the next perl removal patch now. (I need to get this done before the merge window closes.) Three hours later, I've learned how to implement the greatest common denominator algorithm in shell script using Eucilid's algorithm, and I'm only about halfway through. (This would be easier if I either had any idea what the kernel used
asciilifeform: ( perlism, that is , not patch )
asciilifeform: 'The 2.6.28 merge window is open, and I'm coming up with a third perl removal patch. ' << watever happened to this ?
mircea_popescu: the wrong approach. The right fix is sometimes a completely different patch, and sometimes there are several ways to do it which will work, but you have to pick _one_ way or they'll interfere with each other." and so on and so forth.
bvt: i have seen reports of this, but never verified myself. my understanding is that there is a slow c++zation of gcc: i backported one gcc patch for my home system from 6 to 4.9, this involved removing c++ chunks.
asciilifeform: wainot run along with his own patch chain, not giving fuck re other end
asciilifeform: hanbot: it is also possible to bootstrap any vtron using naked gpg, ancient gnupatch, and bare teeth ( manually check sig and patch -p0 < foo.patch, for ea. )
asciilifeform: result : builds with bvt's patch with 0 eggogs, his tarball test functions 100x w/out segfault
mircea_popescu: what "ask the fellows to patch gcc, fix this one error we have". wtf, how do i ask this ?!
mircea_popescu: diana_coman myeah. i guess it'd take a patch on gcc, which is too much hassle atm.
diana_coman: hmm, now one wonders if the patch made it into gcc 4.9 or not
bvt: i don't think it gcc5-specific, the patch against this problem that i've seen was written for gcc 4.8
bvt: they disabled weak symbols for c++/fortran components, http://port70.net/~nsz/musl/gcc-5.3.0/0004-gthr.patch
trinque: yep, whereas I pressed mine to bvt's patch http://btcbase.org/patches/vtools_tempfile_standalone_notmp
trinque: recall the work with trb, and how much better a patch that removes is than one that adds.
a111: Logged on 2019-02-12 01:25 asciilifeform: i suspect this is gonna be a '1-line' patch, to fix. q is where..
mircea_popescu: http://btcbase.org/log/2019-02-12#1895118 <<< 1 line patch that'll bring out the broken glass, and so on.\ ☝︎
asciilifeform: i suspect this is gonna be a '1-line' patch, to fix. q is where.. ☟︎
mircea_popescu: http://btcbase.org/log/2019-02-10#1894874 << you know, you ~could~ just alter the setup yourself, make a patch or such. ☝︎
asciilifeform: meanwhile ave1 didja ever genesis the gnat ? currently i haven't what to patch on.
a111: Logged on 2019-02-03 17:24 diana_coman: trinque, it's possibly best to run your latest script and then hand over everything you need, fresh and clear? not a big issue otherwise to rummage and pack that dir but I don't even recall if I did not touch it further after that point when I sent the genesis patch so I'd rather not introduce artefacts
diana_coman: trinque, it's possibly best to run your latest script and then hand over everything you need, fresh and clear? not a big issue otherwise to rummage and pack that dir but I don't even recall if I did not touch it further after that point when I sent the genesis patch so I'd rather not introduce artefacts ☟︎
asciilifeform: mircea_popescu: it's a google-submitted patch, and it got eaten by the new, 'improved' torvalds, near as i can tell
asciilifeform: it 'works' in the same way as other 'nobus-maintenance' kludges (e.g. koch's 2016 patch) 'work' -- raise bar so that nobus
a111: Logged on 2019-01-18 02:37 asciilifeform: in other noose, Official mainline linux kernel nao infected with gcc7ism : https://lore.kernel.org/patchwork/patch/1022874/
asciilifeform: in other noose, Official mainline linux kernel nao infected with gcc7ism : https://lore.kernel.org/patchwork/patch/1022874/ ☟︎
a111: Logged on 2019-01-13 17:54 billymg: !Q later tell hanbot mp-wp patches have been updated: http://billymg.com/2019/01/minor-mp-wp-patch-updates/ -- the only "\ No newline at end of file" strings you should find in .svg refs patch are from before part of the diff (i.e. file diffed had no newline at the end)
lobbesbot: hanbot: Sent 1 day, 10 hours, and 22 minutes ago: <billymg> mp-wp patches have been updated: http://billymg.com/2019/01/minor-mp-wp-patch-updates/ -- the only \ No newline at end of file strings you should find in .svg refs patch are from before part of the diff (i.e. file diffed had no newline at the end)
billymg: !Q later tell hanbot mp-wp patches have been updated: http://billymg.com/2019/01/minor-mp-wp-patch-updates/ -- the only "\ No newline at end of file" strings you should find in .svg refs patch are from before part of the diff (i.e. file diffed had no newline at the end) ☟︎
mircea_popescu: billymg can just put a patch atop your tree.
billymg: wondering about proper V process though, this is back in the previous patch i published to add the text selection feature, does this mean regrind both?
a111: Logged on 2019-01-09 04:53 hanbot: billymg, phf: in billymg's latest mp-wp vpatch (http://btcbase.org/log/2019-01-07#1885285), i see the old "\ No newline at end of file" spew on two of the touched files (was symptom of bug last yr: http://btcbase.org/log/2018-02-25#1786014). still indicative of proablem with presser/patch?
phf: http://btcbase.org/log/2019-01-09#1886041 << not a bug anymore (last year it was printed as a warning with no effects on the patch, effectively forcing newline always. i then adjusted vdiff to put correct "\ No newline.." directive, while vpatch knows to omit final newline when that directive is present) ☝︎
a111: Logged on 2019-01-07 04:31 billymg: hanbot: i put together a patch for the svg links mentioned earlier: http://billymg.com/2019/01/mp-wp-vpatch-update-internal-image-references-to-point-to-svg-extensions/
hanbot: billymg, phf: in billymg's latest mp-wp vpatch (http://btcbase.org/log/2019-01-07#1885285), i see the old "\ No newline at end of file" spew on two of the touched files (was symptom of bug last yr: http://btcbase.org/log/2018-02-25#1786014). still indicative of proablem with presser/patch? ☝︎☝︎☟︎
billymg: hanbot: i put together a patch for the svg links mentioned earlier: http://billymg.com/2019/01/mp-wp-vpatch-update-internal-image-references-to-point-to-svg-extensions/ ☟︎
asciilifeform: orig release sched is blown, asciilifeform's current desire is to get again to the point where can patch its tyre and reinflate and have rel sched again
mircea_popescu: patch out the test, i guess. they're "clever" like that.
asciilifeform: if one absolutely insists on that feature, prolly Right Thing would be to patch bot so can hang off a znc ( i tried this with own hands, but failed, the existing item is apparently tailored to fleanode-direct connection )
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 ☝︎
asciilifeform: ( not in any patch yet, but pasted last summer )
mircea_popescu: the vpatch that adds a "except if number is 5577, math doesn't work for 5577" is a VERY different patch from the vpatch that adds "here's a sentence ended by a comma turned ended by a dot instead"
asciilifeform: a patch in the context is a vpatch.
mircea_popescu: the larger problem is "what is meant by a patch". i doubt the item can survive ~even one~ major alterations. meanwhile "hey, you spelled theyre with an apostrophe" needn't be counted (but need be fixed)
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: i pressed from the `vtools_ksum` patch http://btcbase.org/patches?patchset=vtools&search=
diana_coman: billymg, well, if the hash is not keccak, you can't exactly press it on top of a keccak patch; and moreover if the sig doesn't verify then it doesn't press it so how would the changes be there?
trinque: asciilifeform: walletsnip patch works great, just need to find time to regrind and further test. and aha, meanwhile diverted to cuntoo so we have a l00nix
billymg: hanbot: if you like i could make and test a patch to submit for review
billymg: but in any case, could also be a quick patch, just to fix the file links
asciilifeform: will note, even with the heap fragging nonsense, current trb has quite reasonable ram footprint; e.g. i run 'zoolag' on a 2GB box, and never manually reset aside from when deploying patch (coupla times in past yr)
asciilifeform: in other noose, asciilifeform finally finished massaging the 14b coad; patch + writeup on conveyor for tonight
billymg: once i get the flow down and get this first patch working it will be easy to create more patches
billymg: also i should note that i didn't include the css changes to the default theme in this patch because i thought a user might want to add one but not the other
trinque: that much is true. iirc mod6 had a patch in the works.
a111: Logged on 2018-12-04 06:59 mircea_popescu: we're stuck with paper bridges between pantsuit alt-reality and the construction of republican sanity, which have to be expensively (if temporarily) maintained. the management of the leaking insanity will be a major function of the lordship and overal brain sink going forward, because obviously a bevy of "patch-this-for-that" could at least in principle overburden V conceptually to the point of failure.
mircea_popescu: we're stuck with paper bridges between pantsuit alt-reality and the construction of republican sanity, which have to be expensively (if temporarily) maintained. the management of the leaking insanity will be a major function of the lordship and overal brain sink going forward, because obviously a bevy of "patch-this-for-that" could at least in principle overburden V conceptually to the point of failure. ☟︎
lobbes: However, if anyone wants (once I get a proper keccak v going) I can make a private patch on request (a la http://trilema.com/2018/the-v-questionarium-answerarium-2018-edition/#selection-327.0-327.204)
diana_coman: hm, if it's indeed the tmp thing, it might be worth a try to press vtools to current leaf (i.e. vtools_tempfile_standalone or _notmp) and see if that cures it; my archive contains pressed vtools to ksum patch only, not further ☟︎☟︎
a111: Logged on 2018-12-03 13:08 mircea_popescu: previous thinking was generally that a regrind pretty much means collapsing a whole tree into a single genesis patch. but thinking about it i don't see why that has to be the case, if there's the hands to do more fine work.
a111: Logged on 2018-12-03 13:08 mircea_popescu: previous thinking was generally that a regrind pretty much means collapsing a whole tree into a single genesis patch. but thinking about it i don't see why that has to be the case, if there's the hands to do more fine work.
mircea_popescu: previous thinking was generally that a regrind pretty much means collapsing a whole tree into a single genesis patch. but thinking about it i don't see why that has to be the case, if there's the hands to do more fine work. ☟︎☟︎
lobbes: however, I have not yet tried timer patch on that one yet
asciilifeform: and ftr naming convention ( carried on since asciilifeform's original vtron ) is simply that patch is $string.vpatch and sig is $string.vpatch.author.sig .
mircea_popescu: trinque not in any case discussing first patch. just the roadmap.
trinque: this is too much ocenboiling for the first patch, akin to fixing everything wrong with trb in its genesis
mircea_popescu: not even there, just patch it to use our own ~correct~ code.
mircea_popescu: http://btcbase.org/log/2018-11-27#1875131 << reasonable ; but yeah, plox ave1 write a patch for the damn thing, the dance is vaguely reminiscent of those organically-evolved early clocks. ☝︎
asciilifeform: which patch did it say picked up, that was already there ?
phf: asciilifeform: done, can you please check that it's correct, i'm doing it from console only linux and my update function said it picked up a patch, that i thought was already there..
phf: asciilifeform: right, that's possibly something to make mandatory then, that is a diff of any two directories produces a a/... b/... patch. so that you can have v1/foo v2/foo v3/foo and vdiff v2 v3 produces a/foo b/foo
a111: Logged on 2018-11-24 23:49 asciilifeform: diana_coman: i'ma put your patch into the 'official' sequence, rather than simply sewing it into ch13, i'd like to explicitly honour the work.
asciilifeform: ( i.e. ch13 will sit on top of diana_coman's patch, and the latter will be mirrored. )
asciilifeform: diana_coman: i'ma put your patch into the 'official' sequence, rather than simply sewing it into ch13, i'd like to explicitly honour the work. ☟︎
a111: Logged on 2018-11-22 21:57 mircea_popescu: in other related matters : i'm authorizing her to add a patch on s.mg crypto lib, to permit arbitrary size e. i recall the threads at the time, but there's a ~really~ good reason to do it : we don't want to pass back and forth kbs worth of exponents. udp packets are small, and there's all the complicated matchwork of sizes meeting keys etc.
mircea_popescu: in other related matters : i'm authorizing her to add a patch on s.mg crypto lib, to permit arbitrary size e. i recall the threads at the time, but there's a ~really~ good reason to do it : we don't want to pass back and forth kbs worth of exponents. udp packets are small, and there's all the complicated matchwork of sizes meeting keys etc. ☟︎
mircea_popescu: http://btcbase.org/log/2018-11-19#1873669 << why, could just patch the others. ☝︎
asciilifeform: if it is an item which conceivably affects the meaning of other text in unpredictable ways, then the patch must reflect this ( and we get 'reground' code. )
mircea_popescu: i meant diana_coman ah i see, you redid the whole tree, that was a patch.
mircea_popescu: asciilifeform oh i see, you redid the whole tree, that was a patch
diana_coman: so to keep this fully aligned, I'll regrind the last 2 patches so that the docs changes are carried over as well; as a result: genesis = http://thebitcoin.foundation/v/V-20170317.tar.gz; 1st patch => http://thebitcoin.foundation/v/V-20180222.tar.gz; 2nd patch => using vtools & keccak instead of sha
a111: Logged on 2018-11-13 14:43 phf: asciilifeform: i've posted a v.pl patch http://btcbase.org/log/2018-10-31#1867871 ( archived http://archive.is/ZJUMM ), unfortunately since v.pl doesn't have its own vtree, doing it properly requires a bunch of extra work
phf: asciilifeform: i've posted a v.pl patch http://btcbase.org/log/2018-10-31#1867871 ( archived http://archive.is/ZJUMM ), unfortunately since v.pl doesn't have its own vtree, doing it properly requires a bunch of extra work ☝︎☟︎
ave1: I'll see if I can patch gcc and add an extra constraint to the asm statement
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
phf: asciilifeform: i suppose next patch would be to replace gnupg with explicit shell callouts. that python gnupg thing is entirely opaque