From: Alice Wonder <alice@librelamp•com>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] Planned Obsolescence
Date: Sun, 18 Dec 2016 12:07:36 -0800 [thread overview]
Message-ID: <d2e0dd76-e6ec-8ccb-5a33-48f0d005afe9@librelamp.com> (raw)
In-Reply-To: <615c88d2a1263810923705c170b25d33@112bit.com>
On 12/14/2016 07:38 PM, Juan Garavaglia via bitcoin-dev wrote:
>
> For reasons I am unable to determine a significant number of node
> operators do not upgrade their clients.
I almost did not update to 0.13.0 because the test suite was failing due
to python errors. How to fix them was posted on bitcointalk.
0.13.1 came with new python errors in the test suite. So I just said
fuck it.
When the test suite actually works in my fairly standard environment
(CentOS) in the distributed release, I will upgrade.
Until then, I'm not jumping through hoops to make the test suite work
and I'm not running clients that haven't passed the test suite so that's
why I almost didn't update to 0.13.0 and haven't updated since.
next prev parent reply other threads:[~2016-12-18 20:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f27bd300c20d1b48cddc7e1d1dc1a96c@112bit.com>
2016-12-15 3:38 ` jg
2016-12-15 18:12 ` Aymeric Vitte
2016-12-15 18:48 ` Jorge Timón
2016-12-15 22:25 ` Angel Leon
2016-12-15 22:44 ` Ethan Heilman
2016-12-18 10:34 ` Matt Corallo
2016-12-18 20:50 ` Chris Riley
2016-12-18 20:07 ` Alice Wonder [this message]
2016-12-18 20:51 ` [bitcoin-dev] Python test suite failures (was Re: Planned Obsolescence) Douglas Roark
2016-12-19 8:13 ` Alice Wonder
2016-12-21 18:33 ` Marco Falke
2016-12-19 2:22 ` [bitcoin-dev] Planned Obsolescence Matt Corallo
2016-12-19 6:39 ` Btc Drak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d2e0dd76-e6ec-8ccb-5a33-48f0d005afe9@librelamp.com \
--to=alice@librelamp$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox