revised ebuild for namecoind 0.3.80 - takes source from github Mandatory update to deal with softfork at block 212500 Reproducible: Always
Created attachment 392852 [details] namecoind ebuild copy to /usr/local/portage/net-dns/namecoind/namecoind-0.3.80.ebuild Dont forget to get all the other files
Created attachment 392854 [details] init script for namecoind daemon place in /usr/local/portage/net-dns/namecoind/files
Created attachment 392856 [details] environment variables for namecoind place in /usr/local/portage/net-dns/namecoind/files
Created attachment 392858 [details] patch to allow linker to work in a gentoo environment place in /usr/local/portage/net-dns/namecoind/files
Created attachment 392860 [details] sample config file for namecoind daemon place in /usr/local/portage/net-dns/namecoind/files
Created attachment 392862 [details] ebuild checksums place in /usr/local/portage/net-dns/namecoind/
As always, before upgrading, backup your /var/lib/namecoin directory. (especially the wallet.dat file !!) I found that I needed to remove the old blockchain and allow 0.3.80 to download it all again. Some internal consistency errors that had been introduced somewhere in earlier upgrades.
*** Bug 533352 has been marked as a duplicate of this bug. ***
(In reply to Ron OHara from comment #1) > Created attachment 392852 [details] > namecoind ebuild > > copy to /usr/local/portage/net-dns/namecoind/namecoind-0.3.80.ebuild > > Dont forget to get all the other files SRC_URI="" EGIT_REPO_URI="https://github.com/namecoin/namecoin.git" EGIT_BRANCH="namecoinq-release" This is not a release but HEAD on branch namecoinq-release. We cannot add a live ebuild as if it were a release because you might get different results on different instances of emerge-ing. Where do you see release 0.3.80? (In reply to Ron OHara from comment #2) > Created attachment 392854 [details] > init script for namecoind daemon > > place in /usr/local/portage/net-dns/namecoind/files In the future, please provide patches since its hard to see what, if anything, has changed.
The 'release' is announced in the News section of the front page of http://namecoin.info/ The item says: 2014-12-19 Softfork upcoming with block 212500 (around New Year's Eve). Pool operators and solo miners please update to v0.3.80 asap. Regular users are recommended to update, too. See the Release notes. I know that this ebuild is really the head of a branch, but the developers do not appear to have provided a source archive anywhere. I have emailed their google group (which is what they now use as a mailing list) and also asked on their IRC channel for either a source archive, or a specific release tag/branch for 0.3.80 on github (which would probably be better) Waiting for a response from them
I have had some feedback on IRC ... but not an official response yet. Apparently there is a git tag of 'nc0.3.80' that I could use to extract the 0.3.80 source... but as yet that is not confirmed as the 'official' tag. There is some urgency to having this available in a reliable way because as at the time of writing this, the soft fork occurs in 422 blocks - about 42 hours from now. I deliberately provided all the files of the ebuild, rather than just a patch in this bug report, so that anyone who is in urgent need of a solution, can find an answer in this bug, just install the files as a local ebuild and get on with making their coins safe. Leaving this bug as 'unconfirmed' sounds appropriate because it does track a branch on github rather than a specific source set. However, just for now it can give people an interim solution. The longer term fix can evolve as usual. FYI - for people looking for namecoin-qt 0.3.80 using the same interim approach ... see https://bugs.gentoo.org/show_bug.cgi?id=534210
Created attachment 392942 [details] revised ebuild to extract namecoin tag nc0.3.80 which is the release source I have had confirmation from ryan-c (on #namecoin IRC) that the github tag of 'nc0.3.80' is the correct source for the 0.3.80 build. ebuild revised accordingly ...
Created attachment 392948 [details] Revised checksums
(In reply to Ron OHara from comment #10) > The 'release' is announced in the News section of the front page of > http://namecoin.info/ > > The item says: 2014-12-19 Softfork upcoming with block 212500 (around New > Year's Eve). Pool operators and solo miners please update to v0.3.80 asap. > Regular users are recommended to update, too. See the Release notes. > > I know that this ebuild is really the head of a branch, but the developers > do not appear to have provided a source archive anywhere. > > I have emailed their google group (which is what they now use as a mailing > list) and also asked on their IRC channel for either a source archive, or a > specific release tag/branch for 0.3.80 on github (which would probably be > better) > > Waiting for a response from them Okay I'll roll this one manually. Yuck!
(In reply to Anthony Basile from comment #14) > (In reply to Ron OHara from comment #10) > > The 'release' is announced in the News section of the front page of > > http://namecoin.info/ > > > > The item says: 2014-12-19 Softfork upcoming with block 212500 (around New > > Year's Eve). Pool operators and solo miners please update to v0.3.80 asap. > > Regular users are recommended to update, too. See the Release notes. > > > > I know that this ebuild is really the head of a branch, but the developers > > do not appear to have provided a source archive anywhere. > > > > I have emailed their google group (which is what they now use as a mailing > > list) and also asked on their IRC channel for either a source archive, or a > > specific release tag/branch for 0.3.80 on github (which would probably be > > better) > > > > Waiting for a response from them > > Okay I'll roll this one manually. Yuck! Actually, I'll use your ebuild, but I really don't like it since one can still change tags around. (I guess that's like upstream rerolling a tarball.) Upstream shouldn't do this. Thanks for bugging them in irc. Note, this is also required for net-dns/namecoin-qt. Can you please test both and reopen this bug if there's more action needed. Thanks for the help!
*** Bug 534210 has been marked as a duplicate of this bug. ***
