< achow101> needs to be released soon. A lot of people are reporting the nCustomFeeRadio bug
< bitcoin-git> [bitcoin] theuni opened pull request #11363: net: Split socket create connect (master...split-socket-create-connect) https://github.com/bitcoin/bitcoin/pull/11363
< cfields_> jonasschnelli: yes, will do
< jonasschnelli> Thanks
< cfields_> wtf, i totally missed the tag. building/signing now.
< achow101> so that's why it was taking so long
< cfields_> :(
< gmaxwell> cfields_: FWIW, the first I was aware of it was achow(?) asking about it in here or pieter telling someone to run it.
< gmaxwell> but I assumed you knew.
< cfields_> gmaxwell: i saw achow101's mention of in backlog and checked the tags on a whim
< cfields_> just a freak failure of my notifications. Will update them.
< cfields_> gitian builders: v0.15.0.1 detached sigs pushed. Sorry for the delay.
< bitcoin-git> [bitcoin] azuchi closed pull request #11357: doc: Fix description of maximumCount (master...fix-0.15.0-release-notes) https://github.com/bitcoin/bitcoin/pull/11357
< bitcoin-git> [bitcoin] anditto opened pull request #11365: [Tests] Add Qt GUI tests to Overview and ReceiveCoin Page (master...Adding-Qt-tests) https://github.com/bitcoin/bitcoin/pull/11365
< bitcoin-git> [bitcoin] mess110 closed pull request #11329: [test] Test abortrescan command (master...kallewoof/test-abort-rescan-2) https://github.com/bitcoin/bitcoin/pull/11329
< bitcoin-git> [bitcoin] esotericnonsense opened pull request #11366: Trivial: RPC/getblockchaininfo: pruneheight is only present in pruned mode (master...2017-09-getblockchaininfo-docs) https://github.com/bitcoin/bitcoin/pull/11366
< kallewoof> I don't really wanna waste anyone's time, but I've been trying to figure out the gitian build process lately and am having issues. I was following https://github.com/bitcoin/bitcoin/blob/master/doc/gitian-building.md and everything was fine down to "Getting and building the inputs". For one I had to cd into ../bitcoin/ for there to be a contrib/gitian-build.sh file (not mentioned, but no biggie),
< kallewoof> and secondly, it explodes messily when I run with the --setup flag. "lxcbr0: ERROR while getting interface flags: No such device [...]". Hints welcome.
< meshcollider> I had a similar issue, I gave up using the gitian-build.sh script and wrote a simple script of my own which basically follows the steps here: https://github.com/bitcoin/bitcoin/blob/master/doc/release-process.md#setup-and-perform-gitian-builds
< meshcollider> basically pull all the repos, checkout the tag, gbuild and then gsign for each OS
< meshcollider> its something to do with the `sudo ifconfig lxcbr0 up` line in the script I think
< meshcollider> I wonder, is it because https://github.com/bitcoin/bitcoin/blob/master/doc/gitian-building.md#setting-up-debian-for-gitian-building uses br0 but the script tries to use lxcbr0 which doesn't exist?
< kallewoof> meshcollider: ohh. cool, thanks, will check
< meshcollider> achow101: Any advice on https://github.com/bitcoin/bitcoin/blob/master/contrib/gitian-build.sh#L178-L184 ? Could they simply be removed?
< meshcollider> because the gitian-building instructions include `echo 'export USE_LXC=1' >> /home/debian/.profile` anyway
< bitcoin-git> [bitcoin] esotericnonsense opened pull request #11367: RPC: getblockchaininfo: Add disk_size, prune_target_size (master...2017-09-getblockchaininfo-addsize) https://github.com/bitcoin/bitcoin/pull/11367
< kallewoof> I tried switching to br0 in gitian-build.sh. The system kind of dies (VirtualBox window still responds, but ssh stops working and eventually times out.. and `top` shows no process using CPU)..
< meshcollider> yeah that's why I wrote my own script in the end, but I wonder if its possible to just delete those lines 178-184 completely from gitian-build.sh
< Duvdevan> hi Everyone
< Duvdevan> I'm fairly new into bitcoin
< Duvdevan> I have only one question
< Duvdevan> can I use this code to modify it and run my own cryptocurrency?
< mryandao> Duvdevan: #bitcoin probably better.
< Duvdevan> mryandao: I thinkt he question is suitable for this channy
< meshcollider> Duvdevan: this channel is only for discussion of bitcoin core development, to discuss altcoin development please use ##altcoin-dev
< Duvdevan> and I'm banned from #bitcoin for unknown reasons... :/
< Duvdevan> thank you for referring me to the right place!
< bitcoin-git> [bitcoin] practicalswift opened pull request #11369: doc: Document locks - increase LOCK(...) comment coverage from 2 % to 77 % (master...lock-comments) https://github.com/bitcoin/bitcoin/pull/11369
< bitcoin-git> [bitcoin] laanwj pushed 1 new commit to master: https://github.com/bitcoin/bitcoin/commit/1ab1b687cb5870258add2b08169cd974f08ed032
< bitcoin-git> bitcoin/master 1ab1b68 Wladimir J. van der Laan: doc: Add release notes for
< achow101> meshcollider: kallewoof use kvm
< achow101> meshcollider: lines 182 and 183 can probably be removed
< bitcoin-git> [bitcoin] practicalswift closed pull request #11361: Remove redundant LOCK(…) and AssertLockHeld(…) (master...remove-redundant-locks) https://github.com/bitcoin/bitcoin/pull/11361
< bitcoin-git> [bitcoin] laanwj pushed 2 new commits to master: https://github.com/bitcoin/bitcoin/compare/1ab1b687cb58...4f7e37e26c5d
< bitcoin-git> bitcoin/master fadf31e MarcoFalke: wallet: Display non-HD error on first run
< bitcoin-git> bitcoin/master 4f7e37e Wladimir J. van der Laan: Merge #11307: wallet: Display non-HD error on first run...
< bitcoin-git> [bitcoin] laanwj closed pull request #11307: wallet: Display non-HD error on first run (master...Mf1709-walletHDfirst) https://github.com/bitcoin/bitcoin/pull/11307
< esotericnonsense> hm
< esotericnonsense> extracts into bitcoin-0.15.0; is this expected? (not sure how minor-minor releases have gone before)
< esotericnonsense> nuked my folder, not that it really matters
< wumpus> that's how the gitian build makes them, yes
< wumpus> don't have a strong opinion on how it should be
< wumpus> though if the .1 would be added it'd need some logic like 'drop the final .0 if the build is 0', otherwise it'd get kind of ugly
< esotericnonsense> yeah
< wumpus> I hope we can just avoid doing build-releases for a few versions now :)
< wumpus> these are really exceptional
< Lightsword> is using addwitnessaddress the best way to use segwit for production right now with core?
< luke-jr> wumpus: another possibility would be to transform `git describe` - then builds of non-tagged commits would have a better name too
< gmaxwell> https://twitter.com/BcoreProject/status/910115487182450694 this imposter account keeps going :(
< instagibbs> should apply for a blue checkmark, I think that would expedite future flagging
< instagibbs> right now it's kind of a "he said she said"
< instagibbs> taking down by twitter fee bot for now, because their support is such crap :/
< alephzero> doesnt twitter have an impersonation policy?
< kinlo> they use blue checkmarks so you know who's real and who is not
< alephzero> thats not true
< alephzero> you can take down an impersonator as well
< kinlo> you can try, which someone should
< alephzero> it is a ToS violation. if successful, they will get suspended.
< alephzero> then after a period of time, you can take posession of that handle.
< alephzero> somebody who has verifiable ties to bitcoin core project should file a claim.
< kinlo> indeed
< instagibbs> right now, someone can file saying "Actually I'm Core, take this down" and they're asking for things like business cards
< kinlo> gmaxwell: maybe that should be you? you're part of the bitcoin core team now, right?
< alephzero> instagibbs: somebody who runs bitcoincore domain and github should do the reporting
< instagibbs> alephzero, agreed
< alephzero> everyone else can click the report button. i have.
< alephzero> do your part.
< gmaxwell> Twitter apparently told us to go away when we reported before or something. :(
< alephzero> I have successfully taken over impersonating accounts previously. but that was for a registered legal entity.
< alephzero> can their subreddit be taken down for impersonation?
< alephzero> that is against reddit's ToS as well.
< grubles> you can report accounts for impersonation
< grubles> (on twitter)
< grubles> as in, if you aren't the account being impersonated
< midnightmagic> Impersonation reporting for Twitter accounts that are impersonating you or your organization--including even if it is someone you are friend with, or a fan of, btw: https://support.twitter.com/forms/impersonation
< midnightmagic> I would continue reporting them.
< alephzero> you will have to supply proof you are being impersonated.
< alephzero> i.e legal entity/pseudonym registration, plus some paperwork to prove ownership
< alephzero> the best way would be to have whoever owns bitcoincore.org or a similar domain provide proof of that domains ownership, i think it will count as a registered pseudonym
< alephzero> looks like it would have to be Wlad.
< bitcoin-git> [bitcoin] promag opened pull request #11370: [test] Add getblockchaininfo functional test (master...2017-09-add-getblockchaininfo-functional-test) https://github.com/bitcoin/bitcoin/pull/11370