436200+ entries in 0.296s
trinque: though I'm
told I mostly slept like a rock
trinque: yep, probably going
to need
that skill
pete_dushenski: trinque i'm already practising
the not sleeping lifestyle
cazalla: for some reason i
thought you were a bachelor
cazalla: i am grateful my first was a boy, hoping
the next will be
too
pete_dushenski: saves me from pumping out 5 girls or something just
to get
that one name-bearer !
cazalla: pete_dushenski, ha
thanks, any idea if boy or girl yet?
pete_dushenski: weird
that RagnarDanneskjol linked
to
the nakamoto knock-off of mp's gpg contracts article instead of
teh original
punkman: finished
the new Fargo series, was pretty good
trinque: neat, looks
to be one you can get used for peanuts on amazon
gribble: RagnarDanneskjol was last seen in #bitcoin-assets 17 weeks, 4 days, 11 hours, 53 minutes, and 59 seconds ago: <RagnarDanneskjol>
trinque - i am occasionally using
the nick for continued development on punks ver. if anyone here's partial
to
the name I can pass it over. Wow
that xm42
trinque: mistyped my own and was bemused at
the elephant
punkman: well
the github link's mine
mod6: In other news, I have 6 automated
tests.
This is pretty neat.
mod6: gernika: hmm, remember what openssl version & block number? was it our Reference Implementation? feel free
to post a log like
trinque did next
time.
trinque: mod6: so
this may be an example of relying on an openssl bug?
gernika: mod6 interesting
that I ran into
that on OpenBSD once, but got around it on a second
try, not using libressl.
mod6: so for
the record,
this is a "VerifySignature" failure, similar
to
that seen in February with 168`001
☟︎ trinque: BingoBoingo: which version of libressl were you successful using, and was
that with an existing chain or one started from scratch?
mod6: this
tx: fb0a1d8d34fa5537e461ac384bac761125e1bfa7fec286fa72511240fa66864d
mod6: ok so
those happen a bit...
then you hit block 124`275 and
then fail
to verify a
tx in block 124`276
to no avail
mod6: looks like you made it 1500 blocks before you started seeing
the nonstandard
txin
pete_dushenski: 'tis
the
true mark of a professional : self-assessment
funkenstein_: re: hastings, uconnect: "boston brakes" is
the
term used in reportage by veteranstoday and others
BingoBoingo: Just standard county bumpkin hypocrisy. Keep my misdemeanor case in limbo because
they lack evidence while giving some village clerk dude a pussy pass for a politically motivated felony committed with malice.
BingoBoingo: I merely asked which Brennan hoping
that you might have a connection between
the Hastings murder and St. Clair County State's Attourney Brennan Kelly who has declined
to prosecute fake Libertarian Dallas Cook for his felony.
trinque: I
tend
to
think
there's something
to
that.
trinque: Due
to Hastings ongoing investigations of CIA chief John Brennan and previous critical investigations of other well known figures,
there was speculation of foul play.[9] Jordan played a role in clearing up speculations about her husband's death as being nothing more
than a "tragic accident".
trinque: notably worked for
the national security council,
that group of bureaucrats
that decides which pakistani kids are going
to die
today by robotic death from above
trinque: iirc
there's ample evidence
to suggest Hastings was working on a story on him when he went for a long drive on a short road
trinque: that lurch-looking one
that heads up
the KG...er... CIA
trinque: so, we're going
to
try Brennan for
the murder of Michael Hastings now, right?
pete_dushenski: anyways, such are
the perils of
turning cars into computers.
pete_dushenski: sounds like vehicle was left out in
the sun with
the windows rolled up
BingoBoingo: pete_dushenski:
That's what Editors are for
pete_dushenski: ^realised after i shoulda referenced hanbot's article
too. alas !
phf: connected
to incitatus few minutes ago, got verack, version and handful inv's. now it's
timeouting again
pete_dushenski: "The Speed Week races
that draw hundreds of racing
teams from around
the world
to Utah's famous salt flats were canceled for
the second consecutive year because of wet conditions." << moar climate change eh
BingoBoingo: For posterity
the case of
the prosecutor who declines
to files charges against Clerk Cook, a self professed libertarian who likes
to use police violence as a political weapon
https://archive.is/ChrKw BingoBoingo: <mircea_popescu> how many years does it
take ffs. << I like ffs, just works
hanbot: Making Bitcoin Exchanges
Truly
Transparent [confidential] << lol
hanbot: "The latest
Tweets from Quentin Amalou (@aquentin). Doctorant en sciences humaines et sociales à @UnivAvignon. Sociologie du cinema et de la musique." ftw.
☟︎ ascii_field: 88.198.6.235:8333 << belongs
to anyone here ?
mircea_popescu: wtf is a box without c compiler anyway i want
to kn ow.
mod6: you wanna do
this for sure anyway ^^ but maybe wait
to build until you've patched?
trinque: there's a "build-essential" package
that grabs a lot of useful compiler stuff
hanbot: yep, i have
the 'what
to do' sketched out. atm i'm stuck on
the v0.5.3.1 and
the errors ./auto.sh
threw out.
typescript sez:
http://dpaste.com/2MNJ748 ascii_field: mircea_popescu:
that's kinda
the only way
to do a 'muscle-powered version control sys'
trinque: that reminds me
to
turn off
the
tls requirement on my mailserver
mircea_popescu: incidentally,
the way he does his patches with
the referneces is pretty smart.
ascii_field: what other answer could i give,
than 'go
to ml...'
ascii_field: hanbot did ask for
the whole orchestra, ~manually~
mod6: What you want
to do is
to start with v0.5.3.1 and go
through his messages
that he linked and patch 'em in one at a
time after verifying
the hashes and
the sigs.
mod6: so a lot
to look out for... certainly not for
the faint of heart. you really hvae
to keep up in here and on
the list
to realize what's going on.
mircea_popescu: it's like
the ultimate reference point. all ulterior repackaging may add convenience, but can't contradict it, basically.
mod6: but
there are a lot of other patches in
there
that are not a part of
that line or "branch" perhaps?
mod6: it is a reference point.
the good news is, most of
the patches
that depend on other patches are linked backwards in
the emails (by ascii) and have notes
that say "depended upon by <a href=..."
hanbot: (not every single patch on
the mailing list, just
the 8 needed for stator)
mircea_popescu: mod6 well look, it's not a meaningless problem. "what's
the reader supposed
to do". going
through
the list and following
the
tree seems sensible.
hanbot: mod6
that's exactly what i want
to do. after all,
the mailing list is
the reference point, no?
mod6: which is
totally doable.
there are like ~12 patches up
through -verify all
trinque: could just read all
the patches in
that script you did
mod6: that was poorly worded. i wouldn't bother
trying
to go
through
that list of emails unless what you want
to do is
this: download & extract v0.5.3.1-RELEASE and go
through every email, one by one, and patch by hand.
hanbot: mircea_popescu well in my
technically handicapped judgement, which may or may not be a viewpoint worth considering
mod6: ok. so
the stator
tarball contains all of
the relivant packages. I
think by linking you
to all of his patches are applied
therein.
mircea_popescu: hanbot once delving into it,
this proves
to be anything but straightforward i surmise ?
mod6: and run
these
to pull down OpenSSL/BDB/Boost:
mod6: ok
thx
trinque, one sec.
mod6: (if you don't do
that last step, you can not verify
the sig)