Topic: BITCOIN IS AVAILABLE ON DEBIAN SID !!!!! (Read 9560 times)
I installed the package on my server, but I have no idea where the program was installed. I'm bit of a debian newb, so maybe it's obvious, but how do you run bitcoind and set up the config file like it talks about here: https://en.bitcoin.it/wiki/API_tutorial_%28JSON-RPC%29 Thanks to anyone that can help me
Bitcoin is now available in Squeeze backports....
Hmm.
There is nothing to be happy with.
Debian have a release cycle that is not appropriate for bitcoin. As my experience suggests me,
bitcoin software were released very often in the past and often introduced changes with
major incompatibilities.
There is nothing to be happy with.
Debian have a release cycle that is not appropriate for bitcoin. As my experience suggests me,
bitcoin software were released very often in the past and often introduced changes with
major incompatibilities.
When the next Debian stable is getting close to release, we can decide if we want to ship the version that is contained within the proposed release, or keep it out.
Also, there is a mechanism for updating packages in stable, its more strict, but if there were protocol changes that made the older version no longer work, it could be updated to support that.
Would it possible to incorporate ./debian directory into the official bitcoin source repository?
Isn't that a better option to support Debian (or to be supported by Debian)?
Isn't that a better option to support Debian (or to be supported by Debian)?
This actually does not help Debian, in fact it usually makes things more complicated and problematic. Please do not do this.
If Debian stable release would include bitcoin after an year or so, 0.3.19 would be too old to connect to the network, wouldn't?
No. All releases are still able to connect. There is a lot of code for handling backward-compatibility.
There might be some fee problems, though. Really old versions would want to run with -paytxfee=0.01.
Hmm.
There is nothing to be happy with.
Debian have a release cycle that is not appropriate for bitcoin. As my experience suggests me,
bitcoin software were released very often in the past and often introduced changes with
major incompatibilities.
If Debian stable release would include bitcoin after an year or so, 0.3.19 would be too old to connect to the network, wouldn't?
Would it possible to incorporate ./debian directory into the official bitcoin source repository?
Isn't that a better option to support Debian (or to be supported by Debian)?
There is nothing to be happy with.
Debian have a release cycle that is not appropriate for bitcoin. As my experience suggests me,
bitcoin software were released very often in the past and often introduced changes with
major incompatibilities.
If Debian stable release would include bitcoin after an year or so, 0.3.19 would be too old to connect to the network, wouldn't?
Would it possible to incorporate ./debian directory into the official bitcoin source repository?
Isn't that a better option to support Debian (or to be supported by Debian)?
Err, this isn't how you should build a debian source package.
You should have downloaded the source package. First you need to make sure you have apt-src lines in /etc/apt/sources.list, and then you can simply do:
You should have downloaded the source package. First you need to make sure you have apt-src lines in /etc/apt/sources.list, and then you can simply do:
$ apt-get source bitcoind
Well yeah I had done this, obviously.
Quote
Then you need to make sure you have the proper build-dependencies installed:
Then while in the directory you can do the following to build the package:
$ sudo apt-get build-dep bitcoind
Then while in the directory you can do the following to build the package:
$ dpkg-buildpackage -us -uc
But I didn't know about that. I'll try.
You can always download the source package, compare the source with the original distributed source, all it takes is a simple diff, and then build your own package out of it.
Last time I tried, I had compilation errors.
I've just tried again, I get:
Code:
$ uname -a
Linux aptosidbox 2.6.38-1.slh.4-aptosid-686 #1 SMP PREEMPT Sat Mar 26 13:12:20 UTC 2011 i686 GNU/Linux
$ make -
Err, this isn't how you should build a debian source package.
You should have downloaded the source package. First you need to make sure you have apt-src lines in /etc/apt/sources.list, and then you can simply do:
Code:
$ apt-get source bitcoind
Then you need to make sure you have the proper build-dependencies installed:
Code:
$ sudo apt-get build-dep bitcoind
Then while in the directory you can do the following to build the package:
Code:
$ dpkg-buildpackage -us -uc
EDIT: fixed code block formatting
I had a different error, with g++ 4.4 (default g++ on debian testing), but with g++ 4.3 (like written in the doc) it compiled without problem, with gaivin git repo.
You can always download the source package, compare the source with the original distributed source, all it takes is a simple diff, and then build your own package out of it.
Last time I tried, I had compilation errors.
I've just tried again, I get:
Code:
$ uname -a
Linux aptosidbox 2.6.38-1.slh.4-aptosid-686 #1 SMP PREEMPT Sat Mar 26 13:12:20 UTC 2011 i686 GNU/Linux
$ make -
g++ -c -O2 -Wno-invalid-offsetof -Wformat -g -D__WXDEBUG__ -D__WXGTK__ -DNOPCH -DFOURWAYSSE2 -DUSE_SSL -I"/usr/include/wx-2.9" -I"/usr/lib/wx/include/gtk2-unicode-debug-static-2.9" -o obj/nogui/util.o util.cpp
g++ -c -O2 -Wno-invalid-offsetof -Wformat -g -D__WXDEBUG__ -D__WXGTK__ -DNOPCH -DFOURWAYSSE2 -DUSE_SSL -I"/usr/include/wx-2.9" -I"/usr/lib/wx/include/gtk2-unicode-debug-static-2.9" -o obj/nogui/script.o script.cpp
g++ -c -O2 -Wno-invalid-offsetof -Wformat -g -D__WXDEBUG__ -D__WXGTK__ -DNOPCH -DFOURWAYSSE2 -DUSE_SSL -I"/usr/include/wx-2.9" -I"/usr/lib/wx/include/gtk2-unicode-debug-static-2.9" -o obj/nogui/db.o db.cpp
g++ -c -O2 -Wno-invalid-offsetof -Wformat -g -D__WXDEBUG__ -D__WXGTK__ -DNOPCH -DFOURWAYSSE2 -DUSE_SSL -I"/usr/include/wx-2.9" -I"/usr/lib/wx/include/gtk2-unicode-debug-static-2.9" -o obj/nogui/net.o net.cpp
g++ -c -O2 -Wno-invalid-offsetof -Wformat -g -D__WXDEBUG__ -D__WXGTK__ -DNOPCH -DFOURWAYSSE2 -DUSE_SSL -I"/usr/include/wx-2.9" -I"/usr/lib/wx/include/gtk2-unicode-debug-static-2.9" -o obj/nogui/irc.o irc.cpp
g++ -c -O2 -Wno-invalid-offsetof -Wformat -g -D__WXDEBUG__ -D__WXGTK__ -DNOPCH -DFOURWAYSSE2 -DUSE_SSL -I"/usr/include/wx-2.9" -I"/usr/lib/wx/include/gtk2-unicode-debug-static-2.9" -o obj/nogui/main.o main.cpp
g++ -c -O2 -Wno-invalid-offsetof -Wformat -g -D__WXDEBUG__ -D__WXGTK__ -DNOPCH -DFOURWAYSSE2 -DUSE_SSL -I"/usr/include/wx-2.9" -I"/usr/lib/wx/include/gtk2-unicode-debug-static-2.9" -o obj/nogui/rpc.o rpc.cpp
In file included from /usr/include/boost/asio/ssl/context_service.hpp:30:0,
from /usr/include/boost/asio/ssl/context.hpp:22,
from /usr/include/boost/asio/ssl.hpp:19,
from rpc.cpp:12:
/usr/include/boost/asio/ssl/detail/openssl_context_service.hpp: In member function void boost::asio::ssl::detail::openssl_context_service::create(SSL_CTX*&, boost::asio::ssl::context_base::method):
/usr/include/boost/asio/ssl/detail/openssl_context_service.hpp:73:28: error: ::SSLv2_method has not been declared
/usr/include/boost/asio/ssl/detail/openssl_context_service.hpp:76:28: error: ::SSLv2_client_method has not been declared
/usr/include/boost/asio/ssl/detail/openssl_context_service.hpp:79:28: error: ::SSLv2_server_method has not been declared
make: *** [obj/nogui/rpc.o] Erreur 1
I suspect it's because I have too a recent version of openssl:
Code:
$ apt-cache policy openssl libssl-dev
libssl-dev:
Installé : 1.0.0c-2
Candidat : 1.0.0c-2
Table de version :
*** 1.0.0c-2 0
100 /var/lib/dpkg/status
0.9.8o-5 0
500 http://ftp.fr.debian.org/debian/ sid/main i386 Packages
openssl:
Installé : 1.0.0c-2
Candidat : 1.0.0c-2
Table de version :
*** 1.0.0c-2 0
100 /var/lib/dpkg/status
0.9.8o-5 0
500 http://ftp.fr.debian.org/debian/ sid/main i386 Packages
I've just downgraded openssl, and now I get:
make: *** No rule to make target `cryptopp/obj/sha.o', needed by `bitcoind'. Stop.
I confess I am a bit reluctant to use it, though.
After all what exactly prevents it to have a trojan inside?
You can always download the source package, compare the source with the original distributed source, all it takes is a simple diff, and then build your own package out of it.
I confess I am a bit reluctant to use it, though.
After all what exactly prevents it to have a trojan inside?
I guess I'll wait until there are a lot of people who havve tested it and audited the code.
SO is it possible to install bitcoind on debian lenny?
Once the package migrates to wheezy, I'll create a backport (http://backports.debian.org) for squeeze.... but lenny is no longer stable, so that probably will no longer be supported and instead you should consider upgrading to squeeze.
Edit: oops, it has, so I'll do that backport now.
Awesome news! Do we know who contributed the package? Is it someone that spends time on this forum?
Mostly it was Jonas, but I also worked and still work with him on the package.
SO is it possible to install bitcoind on debian lenny?
It is, provided you add an unstable entry in your apt repository.
For more info, man sources.list
PS. I have no idea if it would work with Lenny, though. Normally it should since apt-get is supposed to automatically install all required dependencies.
SO is it possible to install bitcoind on debian lenny?
Awesome news! Do we know who contributed the package? Is it someone that spends time on this forum?
Maintainer is Jonas Smedegaard.
You can have his contact information with apt-cache:
apt-cache show bitcoind
(the name of the package seems to have been changed recently)
Awesome news! Do we know who contributed the package? Is it someone that spends time on this forum?
I installed the package on my server, but I have no idea where the program was installed. I'm a bit of a Debian newb, so maybe it is obvious, but how do I run bitcoind and set up the config file like it talks about here:
https://en.bitcoin.it/wiki/API_tutorial_%28JSON-RPC%29
Thanks to anyone who can help me
https://en.bitcoin.it/wiki/API_tutorial_%28JSON-RPC%29
Thanks to anyone who can help me
Personnally I stick with the bitcoin.org tarball install, but I guess that once you've installed the bitcoin-cli package, all you have to do is to run "bitcoind".
What message do you get when you try that?
I think this package may have a memory leak because my memory filled up while using it, and now that it's off my machine, I don't have that problem any more.
I'm not sure how to do the bitcoin.org tarball install. Does anyone know of a good tutorial on it for debian?
This looks to be only the server. On my system the only binary included is /usr/bin/bitcoind. It would be nice if the graphical interface would be included as a Debian package too.
The problem with the gui is that it depends on a new version (2.9) of the WxWidgets library for which there is no package. So yeah.. hassle the wxWidgets guys to update their package and then maybe it will happen..
This looks to be only the server. On my system the only binary included is /usr/bin/bitcoind. It would be nice if the graphical interface would be included as a Debian package too.
Jump to: