Created attachment 405194 [details] emerge --info Bitcoind init script fails: # /etc/init.d/bitcoind start * checkpath: chmod: /var/lib/bitcoin/.bitcoin/bitcoin.conf is a symbolic link * ERROR: bitcoind failed to start I've tried also a fresh install (unmerge bitcoind, remove /etc/bitcoin and /var/lib/bitcoin and emerge bitcoind again) and it is still failing. Removing the /var/lib/bitcoin/.bitcoin/bitcoin.conf symbolic link and copying the actual /etc/bitcoin/bitcoin.conf over fixes the problem: # rm /var/lib/bitcoin/.bitcoin/bitcoin.conf # cp -a /etc/bitcoin/bitcoin.conf /var/lib/bitcoin/.bitcoin/
0.8.6 is no longer supported.
(In reply to Luke-Jr from comment #1) > 0.8.6 is no longer supported. We need to decide what versions of bitcoind and bitcoin-qt we want to stabilize and then remove 0.8.6. @Luke-jr which version is ready?
(In reply to Anthony Basile from comment #2) > @Luke-jr which version is ready? 0.10.2 should be fine, but will be obsoleted probably within a few weeks by 0.11.0. Also noteworthy, all maintained versions have a known regression with unclean PC shutdown.
@arch teams. Please stabilize for KEYWORDS="amd64 arm x86"
arm passes
(In reply to Markus Meier from comment #5) > arm passes undo - we have stable keywords :)
This request cannot be completed because of the following repoman error(s): dependency.bad [fatal] 28 net-p2p/bitcoind/bitcoind-0.10.2.ebuild: DEPEND: amd64(default/linux/amd64/13.0) ['=dev-libs/libsecp256k1-0.0.0_pre20141212'] Since the amd64 team is unable to continue this task, I'm removing the amd64 arch team from the CC field. Feel free to cc the amd64 arch team again when you provide the complete list of the missing dependencies.
Earlier versions are at this point actively vulnerable to known attacks. @blueness, we may want to consider removing them even despite lack of a new version being keyworded stable...
@Luke-Jr Why be so vague? I guess You mean https://bitcoin.org/en/alert/2015-07-04-spv-mining
I'm getting this compile error: /usr/lib/gcc/x86_64-pc-linux-gnu/4.8.4/../../../../x86_64-pc-linux-gnu/bin/ld: /usr/lib64/libmemenv.a(memenv.o): relocation R_X86_64_32S against `.rodata' can not be used when making a shared object; recompile with -fPIC /usr/lib64/libmemenv.a: error adding symbols: Bad value collect2: error: ld returned 1 exit status Makefile:2536: fallo en las instrucciones para el objetivo 'qt/bitcoin-qt' make[2]: *** [qt/bitcoin-qt] Error 1 make[2]: se sale del directorio '/var/tmp/portage/net-p2p/bitcoin-qt-0.10.2/work/bitcoin-d8ac90184254fea3a7f4991fd0529dfbd750aea0/src' Makefile:6213: fallo en las instrucciones para el objetivo 'all-recursive' make[1]: *** [all-recursive] Error 1 make[1]: se sale del directorio '/var/tmp/portage/net-p2p/bitcoin-qt-0.10.2/work/bitcoin-d8ac90184254fea3a7f4991fd0529dfbd750aea0/src' Makefile:617: fallo en las instrucciones para el objetivo 'all-recursive' make: *** [all-recursive] Error 1 * ERROR: net-p2p/bitcoin-qt-0.10.2::gentoo failed (compile phase): * emake failed * * If you need support, post the output of `emerge --info '=net-p2p/bitcoin-qt-0.10.2::gentoo'`, * the complete build log and the output of `emerge -pqv '=net-p2p/bitcoin-qt-0.10.2::gentoo'`. * The complete build log is located at '/var/tmp/portage/net-p2p/bitcoin-qt-0.10.2/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/net-p2p/bitcoin-qt-0.10.2/temp/environment'. * Working directory: '/var/tmp/portage/net-p2p/bitcoin-qt-0.10.2/work/bitcoin-d8ac90184254fea3a7f4991fd0529dfbd750aea0' * S: '/var/tmp/portage/net-p2p/bitcoin-qt-0.10.2/work/bitcoin-d8ac90184254fea3a7f4991fd0529dfbd750aea0' >>> Failed to emerge net-p2p/bitcoin-qt-0.10.2, Log file: >>> '/var/tmp/portage/net-p2p/bitcoin-qt-0.10.2/temp/build.log' * Messages for package net-p2p/bitcoin-qt-0.10.2: * ERROR: net-p2p/bitcoin-qt-0.10.2::gentoo failed (compile phase): * emake failed * * If you need support, post the output of `emerge --info '=net-p2p/bitcoin-qt-0.10.2::gentoo'`, * the complete build log and the output of `emerge -pqv '=net-p2p/bitcoin-qt-0.10.2::gentoo'`. * The complete build log is located at '/var/tmp/portage/net-p2p/bitcoin-qt-0.10.2/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/net-p2p/bitcoin-qt-0.10.2/temp/environment'. * Working directory: '/var/tmp/portage/net-p2p/bitcoin-qt-0.10.2/work/bitcoin-d8ac90184254fea3a7f4991fd0529dfbd750aea0' * S: '/var/tmp/portage/net-p2p/bitcoin-qt-0.10.2/work/bitcoin-d8ac90184254fea3a7f4991fd0529dfbd750aea0
(In reply to Noramo from comment #9) > @Luke-Jr > Why be so vague? > I guess You mean > https://bitcoin.org/en/alert/2015-07-04-spv-mining There are also undisclosed CVEs in older versions. (In reply to Francisco Lloret from comment #10) > I'm getting this compile error: > > /usr/lib/gcc/x86_64-pc-linux-gnu/4.8.4/../../../../x86_64-pc-linux-gnu/bin/ > ld: /usr/lib64/libmemenv.a(memenv.o): relocation R_X86_64_32S against > `.rodata' can not be used when making a shared object; recompile with -fPIC What version of dev-libs/leveldb is installed? We have DEPENDs on specific known-good versions. Can you confirm libmemenv.so exists?
Created attachment 406182 [details] emerge --info
I'm facing the same issue, leveldb is in version 1.9.0-r6, I didn't find libmemenv.so, only libmemenv.a
So the lowest leveldb version that provides libmemenv.so is 1.15.0-r1 and this indeed fixes the issue.
I marked 0.10.2 stable on amd64, arm and x86. I have no idea the above leveldb issue. It is simply not the case that 1.9.0-r6 doesn't provide the .so. Please open another bug as there's probably something else going on with leveldb.
Oh also, all versions previous to 0.10.2 are off the tree.
(In reply to Anthony Basile from comment #15) > I marked 0.10.2 stable on amd64, arm and x86. > > I have no idea the above leveldb issue. It is simply not the case that > 1.9.0-r6 doesn't provide the .so. Please open another bug as there's > probably something else going on with leveldb. I'm not sure why I'm not hitting this issue but I stabilized leveldb-1.15.0-r1. Please reopen this bug if there's still an issue.
I could build successfully new stable package bitcoin-qt 0.10.2. (needed to add qt4 use flag in /etc/portage/package.use for package bitcoin-qt, though) Can also successfully run it, but on the splash screen and in "Help->About Bitcoin Core" window, it shows: "Bitcoin Core Version v0.10.1.0-gd8ac901 (64-Bit)" So what version is it? 0.10.2 or 0.10.1 or 0.10.1.0-gd8ac901 ?
(In reply to Noramo from comment #18) > So what version is it? 0.10.2 or 0.10.1 or 0.10.1.0-gd8ac901 ? It is in fact 0.10.1. The only significant changes for 0.10.2 are a portability fix (for a boost version not in Portage), a Windows fix, and translation updates. With 0.11 around the corner, I'm not sure these are worth a revbump at least until newer boost hits the tree.
So this bug net-p2p/bitcoin-qt-0.10.2: please stabilize is set to status resolved, because 0.10.1 was stabilzed but the package named 0.10.2. I really do not like this. Package maintainers should not decide if an older version has nearly all features of a newer version and therefore name the package like the newer version. That's really crap. If the real 0.10.2 version cannot be stabilized because of missing boost dependency, that should be fixed instead of doing fake version release. I think that should be pretty obvious, so I am surprised of this behaviour, and I am sure everyone who starts bitcoin-qt "0.10.2" package and splash screen showing version 0.10.1 will be.
(In reply to Noramo from comment #20) > So this bug > net-p2p/bitcoin-qt-0.10.2: please stabilize > > is set to status resolved, because 0.10.1 was stabilzed but the package > named 0.10.2. > > I really do not like this. Package maintainers should not decide if an older > version has nearly all features of a newer version and therefore name the > package like the newer version. That's really crap. Pretty sure this was accidental. The focus at the time was to get a critical bugfix for the RBF patch added. > If the real 0.10.2 version cannot be stabilized because of missing boost > dependency, that should be fixed instead of doing fake version release. You misunderstood me: the newer boost version will break 0.10.1, but that bug is fixed in 0.10.2. But since we do not have that boost in the tree, the fix is n/a to us. I can bump to real-0.10.2 anyway if there is a desire for it, but there literally is nothing to gain by doing so.
For now, I've added bitcoin{-qt,d}-0.10.2-r1 ebuilds to the overlay to get the real 0.10.2, as well as a fix to bitcoind's bash-completion file to satisfy the QA warnings about deprecated 'need' and treating bitcoin-cli (which is now no longer "covered" by bitcoind's bash-completion). Additionally, I bumped bitcoin-cli-0.10.2 which is built from a true 0.10.2 commit (although it has no changes at all from 0.10.1), but also now includes its own bash-completion file (with the same adjustments as bitcoind) and also a backported manpage from 0.11 (which has had no particularly relevant changes that would affect the manpage). I'll let Anthony decide if it's worth copying these over to the main portage tree or waiting until a 0.10.3 bump (if there is ever a need).
