We need to remember to stabilize this soon as it provides unit files for systemd. Feel free to CC arches when you feel it's safe Thanks
0.8.3 has known regressions. Should probably wait for 0.8.4 or backport systemd garbage.
(In reply to Luke-Jr from comment #1) > 0.8.3 has known regressions. > Should probably wait for 0.8.4 or backport systemd garbage. to 0.8.1 or 0.8.2? (or, when is 0.8.4 scheduled?) Thanks for the info
0.8.4 is "any day now", but doesn't fix all the regressions. That being said, it probably fixes enough bugs in general to be worth stabilizing once released.
Well, if you think current stable will still be better (0.8.1 I can backport the systemd stuff to a -r1)
+*bitcoind-0.8.2-r1 (08 Sep 2013) +*bitcoind-0.8.1-r1 (08 Sep 2013) + + 08 Sep 2013; Pacho Ramos <pacho@gentoo.org> +bitcoind-0.8.1-r1.ebuild, + +bitcoind-0.8.2-r1.ebuild: + Backport service file to older versions to allow faster stabilization as newer + have some regressions now (#480096) + 0.8.1-r1 would be the candidate now, that simply differs with current stable in its systemd part
(In reply to Pacho Ramos from comment #5) > 0.8.1-r1 would be the candidate now, that simply differs with current stable > in its systemd part I think we should reconsider stabilization target to 0.8.4, due to bug #484134
0.8.4 it is. Arches, please stabilize: =net-p2p/bitcoind-0.8.4, target arches: amd64 arm x86 =net-p2p/bitcoin-qt-0.8.4, target arches: amd64 arm x86 Thanks!
Is this why there is no .bitcoind directory when I install version 0.8.1, because also I am running a systemd system?
(In reply to Thistled from comment #8) > Is this why there is no .bitcoind directory when I install version 0.8.1, > because also I am running a systemd system? There is never any .bitcoind directory, nor has ever been. It's ~/.bitcoin
(In reply to Luke-Jr from comment #9) > (In reply to Thistled from comment #8) > > Is this why there is no .bitcoind directory when I install version 0.8.1, > > because also I am running a systemd system? > > There is never any .bitcoind directory, nor has ever been. > > It's ~/.bitcoin Ok Luke-Jnr Thanks for that. So how do I run ./bitcoind -daemon ?
Many thanks luke-jnr. Please ignore above comment.
Just been reading on the bitcointalk forums that version 0.8.4 is causing the block chain to become corrupt. I can confirm this. It has happened to me twice, and is taking over 24 hours to re-index. Very frustrating. Apparently version 0.8.5 fixes this bug. Are the devs aware of this, and if so, have any idea when 0.8.5 will be made available?
(In reply to Thistled from comment #12) > Just been reading on the bitcointalk forums that version 0.8.4 is causing > the block chain to become corrupt. > > I can confirm this. > > It has happened to me twice, and is taking over 24 hours to re-index. Very > frustrating. > > Apparently version 0.8.5 fixes this bug. > > Are the devs aware of this, and if so, have any idea when 0.8.5 will be made > available? Can you provide a link to the above info and we'll switch to rapid stabilization of 0.8.5 if there is no objection from Luke-Jr.
Hello Anthony. here is the link.... https://bitcointalk.org/index.php?topic=294068.0 Hope this helps.
Okay it seems 0.8.5 is in the tree. My apologies. Please ignore my last comments.
(In reply to Thistled from comment #15) > Okay it seems 0.8.5 is in the tree. > > My apologies. > > Please ignore my last comments. Yes but if this bug is serious enough we should stabilize 0.8.5 and punt 0.8.4.
It's just a bug with *detecting* corruption, and affects every version from 0.8.0 through 0.8.4. There's a simple workaround, but it shouldn't hurt to stabilise 0.8.5 either.
amd64 stable
x86 stable
arm stable. Last arch, closing
