331100+ entries in 0.208s
jurov: mod6: what mail provides do you use?
trying
to resend email for 3 days is standard
mod6: yaaa, i recall
this
ben_vulpes: i figured
this for more of a "half bottle of wine in a girl's butt" report. entertainment, not science.
mod6: glad i checked or
they would have been in
there 2x.
ben_vulpes: is
this perversion even worth running down?
mod6: jurov: lol,
those emails envetually went
through!!!?!
phf: ben_vulpes: i'm building it from inside Clion, so i'm not sure how easy it is
to do cmake otherwise, i can share
the diff
though
ben_vulpes: mod6: under gentoo
the vm simply gives up on life
mod6: and
this is a gentoo VM? or ubuntu?
ben_vulpes: here's
the last line, asciilifeform: x86_64-therealbitcoin-linux-musl-gcc: internal compiler error: Segmentation fault (program cc1)
mod6: huh, yeah wouldn't have expected
that
ben_vulpes: and in other nyooz of
the weird and strange saga of ben_vulpes endeavoring
to set up a reference implementation on his heathen macintosh, buildroot fails
to compile in linux virtual machines of all sorts of flavors
mod6: ok now
to resend
those emails...
jurov: it did compile
the bitcoind,
the problem was intermittent
mod6: jurov: glad you got it resolved
tho. let us know how it goes for you.
mod6: just only was in a hurry
to get back into sync.
mod6: no super rush
there.
mod6: so once we're happy with
this build-script, etc. we cna update
that wiki,
then we're back in sync.
then I can
take some
time
to get
the makefiles stuff all organized.
mod6: 9 connections,
there soemthing i don't see everyday.
mod6: ah, ya, haven't looked yet
tho.
shinohai: Me
too did u get my pm with
the address
to node stats?
mod6: im making a `typescript' of
the output as well. will post later when its complete.
assbot: Logged on 21-02-2016 20:08:29; phf: well, init.scm is read on each connection, since
there's no persistence
mod6: the link is above if anyone wants
to give it a
try.
mod6: ah, ok good deal shinohai. I updated
the script so
that it doens't even pull
that .sign file. we'll just rely on
the sha512
that I hvae, alf has, and ben has.
shinohai: btw mod6 I have reproduced it again just fine
this morning Deb 8 and Ubuntu 14.04
mod6: then
that makes a bit more sense.
mod6: but, say, normal use; you log in, you get a shell, you
type `ls` and
that would just work as expected right?
jurov: most perl scripts meddle with $SIG so
they worked fine
jurov: but perl failed
to execue
them!
mod6: my mind is blown.
these are C binaries.
mod6: but i
thought you said
that `ls` and `pwd` didn't work, like in your shell.
that shouldn't have anything
to do with perl.
mod6: lemme see if i get
this. perl with
thread support broke your entire gentoo?
jurov: yes, both my perl and
turdatron
jurov: yay just recompiled perl without
thread support,
that did
the
trick
mod6: in other news jurov, im about
to re-send
the emails from yesterday
mod6: asciilifeform or
trinque have any
thoughts for
the man?
mod6: yeah, probably need
to re-chroot or whatever it is with gentoo
jurov: but don't mind,
this is my private mess
mod6: what does `which pwd`
tell you?
jurov: mod6 noooo, pwd is external program. it failed
to run it and returned nothing
mod6: because
then your pwd would be /
mod6: so again,
this is because somehow V
thinks
that your pwd is in / ?
jurov: mod6 well, on another box i updates glibc
to same version and perl works fine
phf: well, init.scm is read on each connection, since
there's no persistence
☟︎ mod6: jurov: fwiw, i do a huge % of
testing on a gentoo env with perl 5.20...
phf: (i.e. no reason
to corrupt db in
the process)
mod6: it'd be like doing
the same
thing in a bash script: PWD=`pwd`; echo $PWD;
jurov: asciilifeform: how do i list patches
that went into glibc-2.22-r2 ?
mod6: perl doesn't care about what subprocesses a unix command may or may not use
tho.
phf: run: line 4: 67621 Abort
trap: 6
phf: libc++abi.dylib:
terminating with uncaught exception of
type std::runtime_error: Shiva: failed
to read init file!
phf: yeesh, when shiva fails
to read init.scm it kills
the whole bitcoind
there and
then
mod6: pwd is used iirc in v.pl, but only in
the contex of it being a shell out - your environment should execute
this and return
the result
to a scalar.
jurov: i updated glibc with
the patch
mod6: take a look, i've removed 3 lines: 1. in
the comment section where it lists PK's key fingerprint at
the
top 2.
the curl
that pulls
the sign file for buildroot-2015.05.tar.gz.sign 3.
the gpg command
that verifies buildroot-2015.05.tar.gz.sign
mod6: so as far as
the build-bitcoind-V99995.sh is concerned. let's just check
that hash and call it a day
then.
ben_vulpes: my sha1 and md5 match
those in k's .sign
mod6: anyway, an open line of comms
to
these folks could help us -- especially going forward as we basically might need
to "roll our own" so
that it doesn't pull
the deps via rsync.
mod6: SHA1 & MD5 are broken are
they not?
mod6: just
thinking
that hey, cant hurt anything
to enlighten
the guy
that
these hashes
that he's signing, even up
to
this current month are obsolete.
ben_vulpes: asciilifeform produced legacy hashes,
they match
the ones i have on disk and
the ones you have right?
ben_vulpes: it's just another
thing in
the way of wrapping
this up, mod6 .
mod6: or at least, just
the one we're using.
mod6: what we really aught
to do is write
to
that guy, get him
to join
the wot with a 4096 bit RSA key, and have him resign all of
the bundles.
mod6: the md5 & sha1 match
the sign file
mod6: we expect
this sha512:
mod6: asciilifeform:this is
the one
that we're pulling
ben_vulpes imagines stan's face shooped onto
the manul
mod6: im starting
to
think
that our SHA512 sum of
this artifact is better
than whatever
they've got.