Matches for patch, 1691 total results Sorted by newest | relevance
Fri Aug 14 02:35:32 UTC 2015 <mod6> do you have the maxint_locks_corrected patch applied?
Fri Aug 14 01:30:39 UTC 2015 <asciilifeform> gernika: precisely where it will sit, forever, until you patch it!
Fri Aug 14 01:30:11 UTC 2015 <gernika> FYI OpenBSD w/o db patch wedged at 367850
Thu Aug 13 20:36:58 UTC 2015 <trinque> stuxnet patch, same
Thu Aug 13 20:26:52 UTC 2015 <asciilifeform> 'Despite our notification (and their confirmation), Google is still currently distributing the faulty patch to Android devices via OTA updates.'
Thu Aug 13 05:06:26 UTC 2015 <pete_dushenski> they're no sour patch kids
Wed Aug 12 13:12:51 UTC 2015 <assbot> Logged on 12-08-2015 05:50:26; scoopbot_revived: Microsoft Issues Third Generation Anti-Stuxnet Patch http://qntra.net/2015/08/microsoft-issues-third-generation-anti-stuxnet-patch/
Wed Aug 12 05:50:26 UTC 2015 <scoopbot_revived> Microsoft Issues Third Generation Anti-Stuxnet Patch http://qntra.net/2015/08/microsoft-issues-third-generation-anti-stuxnet-patch/
Mon Aug 10 21:21:51 UTC 2015 <n6> "patch: **** strip count l is not a number" *
Mon Aug 10 21:21:34 UTC 2015 <n6> i'm getting "patch -pl < buildroot-asciilifeform-pogov4_0567b86c55934a8b5d1351b4ccba9306ee3406c3.patch" when running patch -p1 < buildroot-asciilifeform-pogov4.patch
Mon Aug 10 04:26:18 UTC 2015 <mod6> Meanwhile, I can offer you a script that I use to patch up through maxint_locks_corrected from v0.5.3.1 -- it's not a guide, but if you read the steps, it's what needs to happen and in what order. The new (forthcoming) guide will be based on these steps: http://dpaste.com/0YVSD6Q.txt
Mon Aug 10 04:12:04 UTC 2015 <phf> gernika, ben_vulpes: new patch, 7129357156859d81c987e210d26ba552fdc49350
Mon Aug 10 03:38:33 UTC 2015 <ben_vulpes> anyways, hit me up when you push your patch
Mon Aug 10 03:37:56 UTC 2015 <phf> ben_vulpes: one sec, i almost pushed another patch
Mon Aug 10 03:22:55 UTC 2015 <hanbot> still want to build stator, "manually": 0.5.3.1 release + six-patch battery required to achieve stator. verified release will run on my (32bit) ubuntu box w/ mod6. so now, patching (for which i was following said guide, all six patches sha1sum & sig verified)
Mon Aug 10 03:15:02 UTC 2015 <hanbot> the ml patching guide (http://therealbitcoin.org/ml/btc-dev/2015-March/000067.html) step 0x07] Clean Source Base involves manifests which i take it are part of the guide's referenced patch tarballs. given the stator patch battery is single .patch file only, how's one to handle this step (and why does guide assume patch will come in ball?)?
Sun Aug 09 06:16:56 UTC 2015 <asciilifeform> incidentally there is nothing shameful in writing a commentary to another fella's patch
Sun Aug 09 06:14:36 UTC 2015 <asciilifeform> since ben_vulpes is unhappy with this pattern, the next time ~every~ therealbitcoin node grinds to a halt on account of some shitgnomery, i won't be staying up at 3am releasing a patch.
Sun Aug 09 06:13:38 UTC 2015 <asciilifeform> and had to patch again, rebuild.
Sun Aug 09 06:12:15 UTC 2015 <ben_vulpes> asciilifeform: and what happened with that db locks patch of yours