Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
	helo=mx.sourceforge.net)
	by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <dhuff@jrbobdobbs.org>) id 1V1ob4-0006SW-9T
	for bitcoin-development@lists.sourceforge.net;
	Wed, 24 Jul 2013 02:14:34 +0000
X-ACL-Warn: 
Received: from mail-oa0-f45.google.com ([209.85.219.45])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1V1oay-0005vd-7v
	for bitcoin-development@lists.sourceforge.net;
	Wed, 24 Jul 2013 02:14:32 +0000
Received: by mail-oa0-f45.google.com with SMTP id j1so13027213oag.18
	for <bitcoin-development@lists.sourceforge.net>;
	Tue, 23 Jul 2013 19:14:22 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=google.com; s=20120113;
	h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc
	:content-transfer-encoding:message-id:references:to:x-mailer
	:x-gm-message-state;
	bh=xQLve68olUswLxpZJp9v3dIkMELsyHc+Zxa2/yEn4VI=;
	b=FgDraR8sH3Zde55lr0r2iGxO5n4sPGfiLMVdnb/DNdh9fIyEkgtM4YZ2drcIrhQuq4
	X74W+uvZU1Kl1xfnp1GcQvpk7DsS5QZDl2nbkNZj+aLJhz6rlLlJOCW1Y6LMOmpxZbaa
	GgARPfQxHqGBC+elN6VBMSXJO6JEgGOJUT+4M17J4k+4Db+bIkL1QE9Vq9NHTlrq1WH+
	VL4/wiSKbfqYYXwxXRvW4SHIn/Wqctu+POpRoxsOgAxgl813LlhYRl7yF5xKq8jsg7RJ
	IZp+r1XYpvUc9pqq0MT5UCMpeufGTwx911zlqaorIJdAA30A3Gj7zDzkrqi8GI15NZlw
	0KNw==
X-Received: by 10.60.34.194 with SMTP id b2mr33785479oej.2.1374630318988;
	Tue, 23 Jul 2013 18:45:18 -0700 (PDT)
Received: from [172.19.131.158] ([12.130.118.34])
	by mx.google.com with ESMTPSA id ya5sm37232049obc.1.2013.07.23.18.45.14
	for <multiple recipients>
	(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
	Tue, 23 Jul 2013 18:45:17 -0700 (PDT)
Sender: Doug <mith@jrbobdobbs.org>
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
Content-Type: text/plain; charset=us-ascii
From: Douglas Huff <dhuff@jrbobdobbs.org>
In-Reply-To: <CANg8-dAzc2ENivTpr6S=zoUkfGyBM6j=OUb8-_wLTFQqLRmnzw@mail.gmail.com>
Date: Tue, 23 Jul 2013 18:45:11 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <8A6BD408-352F-4346-AF81-3C63BD0ED93B@jrbobdobbs.org>
References: <CANEZrP2GvgZP_1z3EoSs3p+db7tZB6JfEVAewLpGE5eRpGgR3w@mail.gmail.com>
	<CANg8-dAzc2ENivTpr6S=zoUkfGyBM6j=OUb8-_wLTFQqLRmnzw@mail.gmail.com>
To: Scott Howard <showard314@gmail.com>
X-Mailer: Apple Mail (2.1508)
X-Gm-Message-State: ALoCoQn/Y5FY2X/fxteSO5MiIUo54V7b1j9NHmQPOZwvN4q7Scj7MfxdkgMvomkxeuNLSjX6ko9g
X-Spam-Score: -0.1 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-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: 1V1oay-0005vd-7v
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>,
	Debian Bitcoin Packaging Team <pkg-bitcoin-devel@lists.alioth.debian.org>
Subject: Re: [Bitcoin-development] Linux packaging letter
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Wed, 24 Jul 2013 02:14:34 -0000

Honestly, until I read the quoted part of your response, I actually =
wasn't in favor of this whole thing since in general the types of issues =
being mentioned are, in large part, the types of issues that maintainers =
deal with all the time.

On Jul 23, 2013, at 3:02 PM, Scott Howard <showard314@gmail.com> wrote:

> Response: Is there a way to "certify" the Debian libraries? Debian
> bitcoind/bitcoin-qt runs the compile test during all architectures.
> MIPS has been failing recently, but no one has looked into it yet.
> Perhaps it's not worth developers efforts yet, but at some point the
> technology should reach a point it can be redistributed.


The fact that you're even trying to package and/or at some point have =
packaged and shipped big endian binaries is straight up *NEGLIGENT.*

Stop that. Now. It won't work.

Thanks for showing that this *is* necessary, I guess.=