From: Btc Drak <btcdrak@gmail•com>
To: Matt Corallo <lf-lists@mattcorallo•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Planned Obsolescence
Date: Mon, 19 Dec 2016 06:39:46 +0000 [thread overview]
Message-ID: <CADJgMzsqtRMBQSLLz7g3sRMghPXDZM2B=y_-f1d5L5rQMK03Fg@mail.gmail.com> (raw)
In-Reply-To: <9E1EA42E-B37E-47C9-89B0-37F4CDB2B711@mattcorallo.com>
[-- Attachment #1: Type: text/plain, Size: 1713 bytes --]
Maybe something trivial like lack of Python 3 dependency on older CentOS
builds?
On Mon, Dec 19, 2016 at 2:22 AM, Matt Corallo via bitcoin-dev <
bitcoin-dev@lists•linuxfoundation.org> wrote:
> Please do report bugs to https://github.com/bitcoin/bitcoin . If you
> never report them of course they won't get fixed. I'm not aware of test
> suite failures and know a bunch of folks who use CentOS, though not sure
> how many develop on it.
>
> On December 18, 2016 12:07:36 PM PST, Alice Wonder via bitcoin-dev <
> bitcoin-dev@lists•linuxfoundation.org> wrote:
> >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.
> >_______________________________________________
> >bitcoin-dev mailing list
> >bitcoin-dev@lists•linuxfoundation.org
> >https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
[-- Attachment #2: Type: text/html, Size: 2807 bytes --]
prev parent reply other threads:[~2016-12-19 6:40 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
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 [this message]
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='CADJgMzsqtRMBQSLLz7g3sRMghPXDZM2B=y_-f1d5L5rQMK03Fg@mail.gmail.com' \
--to=btcdrak@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=lf-lists@mattcorallo$(echo .)com \
/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