From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Wd49n-00056l-TG for bitcoin-development@lists.sourceforge.net; Wed, 23 Apr 2014 20:52:39 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.216.171 as permitted sender) client-ip=209.85.216.171; envelope-from=kristovatlas@gmail.com; helo=mail-qc0-f171.google.com; Received: from mail-qc0-f171.google.com ([209.85.216.171]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Wd49m-0005d8-TR for bitcoin-development@lists.sourceforge.net; Wed, 23 Apr 2014 20:52:39 +0000 Received: by mail-qc0-f171.google.com with SMTP id c9so1563070qcz.16 for ; Wed, 23 Apr 2014 13:52:33 -0700 (PDT) X-Received: by 10.229.96.199 with SMTP id i7mr24511193qcn.20.1398286353453; Wed, 23 Apr 2014 13:52:33 -0700 (PDT) Received: from [10.0.2.15] (c-50-191-76-100.hsd1.pa.comcast.net. [50.191.76.100]) by mx.google.com with ESMTPSA id w14sm3731033qaw.11.2014.04.23.13.52.31 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 23 Apr 2014 13:52:32 -0700 (PDT) Message-ID: <5358280F.2050108@gmail.com> Date: Wed, 23 Apr 2014 16:52:31 -0400 From: Kristov Atlas User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: "Warren Togami Jr." , Bitcoin Dev References: <53581D1D.1000709@gmail.com> In-Reply-To: Content-Type: multipart/alternative; boundary="------------050406050105030801020907" X-Spam-Score: -0.6 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (kristovatlas[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1Wd49m-0005d8-TR Subject: Re: [Bitcoin-development] Development Roadmap of Bitcoin Core 0.9.2 X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Apr 2014 20:52:40 -0000 This is a multi-part message in MIME format. --------------050406050105030801020907 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 04/23/2014 04:39 PM, Warren Togami Jr. wrote: > On Wed, Apr 23, 2014 at 10:05 AM, Kristov Atlas > > wrote: > > I see that the latest nightly build (thanks for that, Warren) is > still not compatible with Tails/Debian Squeeze. Is there still an > intention to address this issue? Might it be fixed by 0.9.2? > > > If I understand the situation, bitcoind does work but not bitcoin-qt > due to qt-4.6? If that is so, then the official Bitcoin 0.8.6 > binaries didn't work on Squeeze either this is not a regression. > > The priority is for bitcoind to work on as many distributions as > reasonably possible as older stable distributions are most often > headless. If you are a rare user who needs Bitcoin-Qt on an > incompatible system you can at least build it from source. > > Warren Bitcoin-Qt 0.8.6 worked fine on Tails (and Debian Squeeze, I assume). So, it is a regression. Here's output from the latest nightly build for Linux: amnesia@amnesia:~/bitcoin-0.9.99.0-20140422-2bbecc8-linux/bin/32$ ./bitcoin-qt ./bitcoin-qt: symbol lookup error: ./bitcoin-qt: undefined symbol: _ZN19QAbstractProxyModel11setItemDataERK11QModelIndexRK4QMapIi8QVariantE Since Tails has many simple development tools like "make" stripped out for security reasons, one could not simply build from source in Tails. It might be possible to build in Debian Squeeze and transplant that, however. I'll have to give that a shot some time. I'd argue that Tails is an incredibly important -- and hardly obscure -- Linux distribution that Bitcoin should endeavour to support. See: https://tails.boum.org/press/index.en.html -Kristov --------------050406050105030801020907 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit On 04/23/2014 04:39 PM, Warren Togami Jr. wrote:
On Wed, Apr 23, 2014 at 10:05 AM, Kristov Atlas <kristovatlas@gmail.com> wrote:
I see that the latest nightly build (thanks for that, Warren) is still not compatible with Tails/Debian Squeeze. Is there still an intention to address this issue? Might it be fixed by 0.9.2?

If I understand the situation, bitcoind does work but not bitcoin-qt due to qt-4.6?  If that is so, then the official Bitcoin 0.8.6 binaries didn't work on Squeeze either this is not a regression.

The priority is for bitcoind to work on as many distributions as reasonably possible as older stable distributions are most often headless.  If you are a rare user who needs Bitcoin-Qt on an incompatible system you can at least build it from source.

Warren

Bitcoin-Qt 0.8.6 worked fine on Tails (and Debian Squeeze, I assume). So, it is a regression.

Here's output from the latest nightly build for Linux:
amnesia@amnesia:~/bitcoin-0.9.99.0-20140422-2bbecc8-linux/bin/32$ ./bitcoin-qt
./bitcoin-qt: symbol lookup error: ./bitcoin-qt: undefined symbol: _ZN19QAbstractProxyModel11setItemDataERK11QModelIndexRK4QMapIi8QVariantE
Since Tails has many simple development tools like "make" stripped out for security reasons, one could not simply build from source in Tails. It might be possible to build in Debian Squeeze and transplant that, however. I'll have to give that a shot some time. I'd argue that Tails is an incredibly important -- and hardly obscure -- Linux distribution that Bitcoin should endeavour to support. See: https://tails.boum.org/press/index.en.html

-Kristov
--------------050406050105030801020907--