I agree with Scott's assessment, although I would note that Debian *does* have
a suite that addresses the needs of Bitcoin: stable-updates. Mandatory
protocol rule changes would seem to fall within the broken by the flow of
time category. Thoughts?
--
To UNSUBSCRIBE, email to
This isn't correct. We do support backported/stable versions in a separate git
repository:
https://gitorious.org/bitcoin/bitcoind-stable/
Debian is welcome to choose a branch and I will do what I can to ensure it
receives long-term support. I would recommend using the latest release
On Wednesday, September 04, 2013 4:58:58 PM Scott Howard wrote:
How are those updated? It appears whenever there is a current-version
micro-release, those commits are backported to the stable branches.
I have a lot of different projects, and tend to cycle through them. Outside of
that routine,
Also, note the backport branches have a policy of only including fixes which
have been first merged to the master branch.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
On Saturday, May 25, 2013 11:31:42 PM Dmitry Smirnov wrote:
On Thu, 23 May 2013 13:06:43 Luke-Jr wrote:
Could you make your draft packaging available so I can experiment some
more on my end in the meantime?
Draft packaging is committed to
http://anonscm.debian.org/gitweb/?p=pkg
Just to be specific, 0.3.24 is known to be affected by CVE-2012-1909:
https://bitcointalk.org/index.php?topic=67738.0
Debian maintainers may wish to watch https://en.bitcoin.it/wiki/CVEs
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
To address the mips/powerpc/s390/sparc/sparc64 concerns...
bitcoind has never been supported on big-endian architectures, even in 0.3.x,
and even if it used to build, there's almost no chance it works at all.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a
On Tuesday, March 27, 2012 2:00:52 PM Jonas Smedegaard wrote:
Being old is not a bug in itself, however: Please file individual
bugreports for each, well, bug, instead of a single giant one. That's
much easier to handle.
Being unmaintained means there is nobody tracking which bugs affect it
Package: bitcoind
Version: 0.3.24~dfsg-1
bitcoind 0.3.24 has been unmaintained for a long time, and has many known bugs
including at least one major security vulnerability. Please update to at least
0.4.5rc2 before freezing wheezy. Future 0.4.x releases are guaranteed to only
include bugfixes
But these (642380 also) were OpenVZ, not UML...
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
On Thursday, September 22, 2011 10:21:30 AM Ben Hutchings wrote:
Looking at the OpenVZ patch for the RHEL 6 kernel (which is what
Parallels is selling), I see that ext4 has been added to the accepted
list and doesn't require special handling. So I think we could add it
in Debian.
Thanks.
Package: linux-image-2.6.32-5-openvz-amd64
*** Please type your report below this line ***
# vzctl chkpnt 132
Setting up checkpoint...
suspend...
Can not suspend container: Invalid argument
Error: unsupported fs type ext4
Checkpointing failed
-- Package-specific info:
** Version:
Linux
Package: linux-image-2.6.32-5-openvz-amd64
Within Virtual Environments (VEs) only...
The conntrack userland tool gets Connection refused on the netlink socket
required to interact (list, flush, etc) with connection tracking. The old
procfs interface is no longer supported in 2.6.32.
P.S. Is
On Wednesday, September 21, 2011 10:55:42 PM Ben Hutchings wrote:
If OpenVZ doesn't support migration of ext4, you'll have to use another
filesystem for the containers.
According to http://openvz.org/pipermail/users/2008-January/001669.html , this
is a meaningless check (in
Package: asterisk
Version: 1:1.6.2.9-2+squeeze3
Using macros inside of for loops compiles to the old Macro application
using pipes as delimiters. It should be modified to use the new Gosub-and-
comma syntax. The offending code is on lines 3548-3566 in res/ael/pval.c in at
least 1.6.2.9 through
On Tuesday, September 06, 2011 9:41:05 AM Ben Hutchings wrote:
I understand this and found a patch that should fix it.
Is this a security vulnerability, or am I safe to assume my system was not
exploited at least through this issue?
--
To UNSUBSCRIBE, email to
On Tuesday, September 06, 2011 12:20:17 PM Ben Hutchings wrote:
On Tue, Sep 06, 2011 at 11:06:24AM -0400, Luke-Jr wrote:
On Tuesday, September 06, 2011 9:41:05 AM Ben Hutchings wrote:
I understand this and found a patch that should fix it.
Is this a security vulnerability, or am I safe
Package: bitcoin-cli
bitcoind isn't supposed to be a CLI application, just a daemon.
While it does take command-line arguments to call a method, this isn't
designed for end-users, and returns JSON output.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
Any progress on this? libgsm is the last piece of non-Free software on my
system, as sox requires it...
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
19 matches
Mail list logo
