Your message dated Sun, 24 Nov 2013 13:43:44 -0500
with message-id
<CANg8-dDMOFE8m_C_fqe=P1=7yhekj3zwgk9hzx7pjiswz0n...@mail.gmail.com>
and subject line Re: [Pkg-bitcoin-devel] Bug#730402: bitcoind: There is no
stable bitcoind version for wheezy
has caused the Debian Bug report #730402,
regarding bitcoind: There is no stable bitcoind version for wheezy
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
730402: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=730402
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: bitcoind
Severity: important
Dear Maintainer,
I've tried to install bitcoin daemon (package "bitcoind") and didn't find it in
wheezy repository.
I found out the reason: Bitcoin uses Berkeley DB version 4.8 to store its data,
but in wheezy a lot of software uses Berkeley DB version 5.1.
Bitcoin developers (see https://github.com/bitcoin/bitcoin ) explain in readme-
files
that using v.5.1 of DB with their software "will break binary wallet
compatibility".
Here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=621425 this problem was
discussed.
Now the bug considered as fixed, because "bitcoind" pakage, which works with
v.5.1 of DB,
was placed in sid repository. But what should do users of stable release?
I tried to compile sources from github.com. Bitcoin daemon successfully started
and even responds to JSON requests. BUT:
1. Sometimes JSON connection to daemon cannon be established (tens of attempts
don't help).
I don't understand why. Usually after five minutes things come to norm.
2. What is the worst: From time to time, after restart of daemon, DB of blocks
turn out to be
COMPLETELY PURGED: "getblockcount" request returns "0" and process of DB
filling starts
from beginning. :-(
What can I do to get correctly working bitcoin daemon?
Sincerely,
epros
-- System Information:
Debian Release: 7.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages bitcoind depends on:
pn libboost-filesystem1.54.0 <none>
pn libboost-program-options1.54.0 <none>
pn libboost-system1.54.0 <none>
pn libboost-thread1.54.0 <none>
ii libc6 2.13-38
ii libdb5.1++ 5.1.29-5
ii libgcc1 1:4.7.2-5
pn libminiupnpc5 <none>
ii libssl1.0.0 1.0.1e-2
ii libstdc++6 4.7.2-5
ii zlib1g 1:1.2.7.dfsg-13
bitcoind recommends no packages.
Versions of packages bitcoind suggests:
pn db-util <none>
pn db4.8-util <none>
--- End Message ---
--- Begin Message ---
On Sun, Nov 24, 2013 at 1:30 PM, Евгений Просветов <[email protected]> wrote:
> Package: bitcoind
> Severity: important
>
> Dear Maintainer,
>
> I've tried to install bitcoin daemon (package "bitcoind") and didn't find it
> in
> wheezy repository
It is not in the wheezy repository and has never been included in a
stable release of Debian. For now, it will not be included in a Debian
release.
.
> I found out the reason: Bitcoin uses Berkeley DB version 4.8 to store its
> data,
> but in wheezy a lot of software uses Berkeley DB version 5.1.
That's not the reason why. See:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718272
Mainly that network protocol changes would not be suitable for an
upload to a released version of debian. Only security changes would be
suitable. That is very dangerous and potentially harmful to the
bitcoin network (and could lose users lot of money)
> Bitcoin developers (see https://github.com/bitcoin/bitcoin ) explain in
> readme-
> files
> that using v.5.1 of DB with their software "will break binary wallet
> compatibility".
> Here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=621425 this problem was
> discussed.
> Now the bug considered as fixed, because "bitcoind" pakage, which works with
> v.5.1 of DB,
> was placed in sid repository. But what should do users of stable release?
Users of stable releases should build their own packages or use the
version in unstable. If you use the version in unstable, please be
aware that it will be kept up to date and if the bitcoin network is
upgraded (or the protocol changed) you will need to update your
package.
>
> I tried to compile sources from github.com. Bitcoin daemon successfully
> started
> and even responds to JSON requests. BUT:
>
> 1. Sometimes JSON connection to daemon cannon be established (tens of attempts
> don't help).
> I don't understand why. Usually after five minutes things come to norm.
>
> 2. What is the worst: From time to time, after restart of daemon, DB of blocks
> turn out to be
> COMPLETELY PURGED: "getblockcount" request returns "0" and process of DB
> filling starts
> from beginning. :-(
>
> What can I do to get correctly working bitcoin daemon?
These questions are best directed upstream. I haven't experienced
these problems when I compiled the sources from github, but here are
some guesses:
1) Block verification can be very cpu intensive, your json connects
are probably timing out until the blocks have been verified
2) I'm not sure about this one, I assume this is regarding leveldb
which is included in the github sources. Upstream maintains that
version of leveldb and the build doesn't use any debian packages to
build with leveldb. This sounds like an upstream bug.
I hope this helps point you in the right direction!
Regards,
Scott
--- End Message ---
