331400+ entries in 0.205s
ben_vulpes: mod6: mine *does* verify
the signature, but not in
the build-bitcoin-v999o*.sh context
mod6: for some reason,
this guys friggin
thing apparently wont verify, except for me. i seem
to be
the only one who has a gpg & his key
that'll verify
this damn
thing
☟︎ mod6: but
this problem isn't realted
to
that.
phf: mod6:
that's not what i'm proposing
ben_vulpes: if asciilifeform hadn't already declared himself
to not
touch anything
that brought anything down from
the net he'd be complaining about all of
the above as well
☟︎ ben_vulpes: mod6: nobody's saying
that buildroot should be v-verified, but
that not isolating buildscripts from
the user gpg keyring is...not great.
ben_vulpes: yeah
the v-wrapping build scripts don't isolate
themselves from
the user keyring.
mod6: i disagree,
totally,
that V should contain any functionallity
to validate anything outside of
the V
tree, contained in
the patches dir.
phf: ben_vulpes:
that's what all v's do, but we also have
this auxiliary operations before
the press
that require calling gpg --verify
mod6: well, im fuckin stumped.
this is crazy
ben_vulpes: phf: you'll note
that's more or less exactly what my v does
ben_vulpes: unless it's lying and it is verifying
the signature anyways
ben_vulpes: mod6: because gpg says
the signature isn't actually verified!
phf: i proposed a solution
to
that problem. have a set of gpg commands
that work with .wot. so something like vgpg verify file, will 1)
tmp=mktemp -d gpgxxxx 2) gpg --homedir $tmp --import wot/*.asc 3) gpg --homedir $tmp --verify 4) rm -rf $tmp, so
that no foundation operations ever work with ~/.gnupg and always work with ~/.wot
mod6: gernika: <+mod6> what does
this say `gpg --fingerprint 0xAB07D806D2CE741FB886EE50B025BA8B59C36319` ?
mod6: ben_vulpes: can you identify why
this is an issue?
gernika: same for previous version of
the file
mod6: what does
this say `gpg --fingerprint 0xAB07D806D2CE741FB886EE50B025BA8B59C36319` ?
gernika: mod6:
the exact same message as in
the dpaste.
mod6: gernika: what happens if you're in
the rotor dir and you do `gpg --verify buildroot-2015.05.tar.gz.sign` ?
ben_vulpes: (girl hands me child, i place child on floor, "you know precisely what i do when you hand him
to me, you could just save us
the fifteen seconds and put him on
the floor yourself")
gernika: mod6 I have
that fine file in rotor :)
mod6: gernika: do you have
this fine somewhere in your build env? buildroot-2015.05.tar.gz.sign ?
mod6: back around
the 28th.
mod6: we all went
through
this with V99996
ben_vulpes: mod6: are you even certain
there was a 'we' running
this a few weeks ago?
mod6: so why didnt we have
this
trouble a few weeks ago?
phf: so i
tried installing parenscript it pulls in all kinds of retarded. i don't even. anaphora, named-readtables.
mod6: the
thing
that bothers me, is
this: all
that is different about
the build script itself is
the version of V.
ben_vulpes: gernika does your script go so far as
to exit at
that point?!
gernika: I have manually imported
that pubkey,
to no avail.
phf: alexandria cffi flexi-streams net-telent-date
trivial-features usocket araneida cl-irc gpg-error rfc2388
trivial-gray-streams v babel defservice gpgme split-sequence uiop
ben_vulpes: how are you shipping
to
this
thing? hacking directly on
the running lisp image?
phf: err, both jumping from hunk
to hunk and
the on change
phf: (it works now by
the way)
phf: i already have jquery
there because i wanted
to add jumping from hunk
to hunk on patch page by j/k
phf: oh,
there's "change"
phf: $('#patchset-select select').on('select', function() { alert('foo') }) doesn't do what i
think it should
phf: ben_vulpes: i'm not quite sure what
to attach and where
mod6: also, re: regrind,
this is for sure: when doing
this
task, it forces you
to read and understand
the patch
that needs regrinding. nothing wrong with
this as far as I can
tell.
phf: bah,
that's what i get for sprinkling some jquery on
that bitch
ben_vulpes: does not work when
tabbing
to
the dropdown and hitting
the spacebar
ben_vulpes: but when i click
the dropdown some js
takes over and doesn't let me select anything
BingoBoingo: I dunno what insanity possessed me
to order
that reboot, when
the same problem is why I got batteries and UPSs for local machines
BingoBoingo: danielpbarron:
This problem happened with quantrill
this week. Was unresponsive so I ordered a reboot, after reboot... holy fucksticks
the disappoint.
BingoBoingo: <danielpbarron> oh also, in getinfo I get
this >> "errors" : "WARNING: Displayed
transactions may not be correct! You may need
to upgrade, or other nodes may need
to upgrade." <<
The hard shutdown may have left your blockchain copy corrupted at
the end. Gotta get a UPS.
danielpbarron: oh also, in getinfo I get
this >> "errors" : "WARNING: Displayed
transactions may not be correct! You may need
to upgrade, or other nodes may need
to upgrade."
danielpbarron: gonna
try a few more
times
to get it
to continue building on
the blocks i already had, and failing
that I'll
try it with an empty .bitcoin directory
mod6: well,let us know how it goes.
thanks for building.
danielpbarron: but
that's not necessarily
the fault of your
thing; i had a power outage
take
this machine down without properly shutting down
danielpbarron: can't get a new block, just bastards and
transactions
that appear
to be invalid
phf: i'm going
to
try and keep main patches view
the same as what mod6 is releasing
danielpbarron: well i got a bitcoind out of it, and when i run it against my already mostly complete .bitcoin directory i got black holed;
trying again now with -connect=173.73.235.152
mod6: and ALL: do not run
this script 2x, ever. if something goes wrong, just please, start again fresh dir blow everything away except your .wot dir & contents and script.
mod6: gab
the key from
the fhe keyserver andimport manually?
phf: so without
the
two broken patches experimental almost presses cleanly. something wrong with polar's patches..
mod6: ok, well it should pull
that key.
mod6: danielpbarron:
try `gpg --recv-key0xAB07D806D2CE741FB886EE50B025BA8B59C36319`
danielpbarron: regardless,
the script ended with a bitcoind in rotor/TEST2/bitcoin/src/
phf: also release ought
to be stable
danielpbarron: i get
the same error when i do
the same
thing with
the long key id you just showed
mod6: didnt see
the paste /me looks
mod6: how are you
trying
to 'get it' ?
danielpbarron: when i
try
to get it, it gives
the error linked above
mod6: along with
the other 3?
mod6: danielpbarron: did you put
this key 0xAB07D806D2CE741FB886EE50B025BA8B59C36319 in your gpg keyring?
mod6: hanbot: no worries,.
thanks!
hanbot: mod6 ftr i'm not at all set up for proper
testing atm, much as i wish i could offer something. will heads up when i'm able.
assbot: Logged on 20-02-2016 20:41:35; ben_vulpes: mod6: i am *still* getting
this with build-bitcoin-v99995.sh: gpg: WARNING: not a detached signature; file 'buildroot-2015.05.tar.gz' was NOT verified!
☟︎ mircea_popescu: i will be off
to do
things with slutty girls now, bbl.
mod6: shinohai: cool!
thanks!
mod6: i don't
think V is driving me insane. at least, I hope not. i
think re-grinding is a pain, but i don't see a way around
this.
jurov: improvement
toward what?
jurov: the v
theory is fine, but in practice i'm afrain it will drive everyone attempting it insane
phf: went
to have dinner, come back, mother of logs
mircea_popescu: and
the one in
the middle is all like "Shit, i really got
the worst boobjob in
the world"
mircea_popescu: damn we're not even a decade in can't find shit in
the logs ;/
mircea_popescu: the one where new people see
the same ravines and
tend
to build
the same bridge long dead people saw and built ?
mircea_popescu: (and for
the record i will point out
that
tlp is anglotard enough
to miss most of
the substance.
there's perfecty good reason everyone painted
the same god damned vase with
two apples next
to it, and
this has little do
to with "you're not boring son ok" and a lot of fucking
things
to do with ... damn, where's
that
thread about
ther ancient battlefield ?
☟︎