< bitcoin-git>
bitcoin/master 2bcc705 Aaron Clauson: Updated appveyor job to checkout a specific vcpkg commit ID.
< bitcoin-git>
bitcoin/master b4f832e MarcoFalke: Merge #18001: Updated appveyor job to checkout a specific vcpkg commit ID
< bitcoin-git>
[bitcoin] MarcoFalke merged pull request #18001: Updated appveyor job to checkout a specific vcpkg commit ID (master...vcpkg-specific-version) https://github.com/bitcoin/bitcoin/pull/18001
< bitcoin-git>
[bitcoin] fanquake opened pull request #18003: build: remove --large-address-aware linker flag (master...configure_large_address_aware) https://github.com/bitcoin/bitcoin/pull/18003
< kallewoof>
Weird. I realized that I haven't seen release announcement emails for Bitcoin Core since 0.18.1. I searched my inbox for 'wladimir' and 'bitcoin core released' but don't see anything for 0.19.x
< bitcoin-git>
[bitcoin] fanquake opened pull request #18004: build: don't embed a build-id when building libdmg-hfsplus (master...libdmg_no_build_id) https://github.com/bitcoin/bitcoin/pull/18004
< wumpus>
kallewoof: are you on the bitcoin-dev / bitcoin-core-dev mailing lists?
< wumpus>
(I send all announcements including RCs to bitcoin-core-dev, and only final release announcements to bitcoin-dev)
< kallewoof>
wumpus: I don't think I see the RC announcements, but I should've seen 0.19, right?
< kallewoof>
Even if not on both (I do wanna be on both tho, and I thought I was subscribed... weird)
< sipsorcery>
hebasto: if you find one please let me know as well :)
< fanquake>
elichai2: done
< elichai2>
fanquake: Thanks :)
< hebasto>
sipsorcery: ;)
< sipsorcery>
the only trick I've got is whenever vcpkg installs are required to branch and put "Exit-AppveyorBuild;" in the vcpkg block.
< sipsorcery>
otherwise the job gets stuck, never has enough time to do the vcpkg install and build, so the appveyor cache never gets updated.
< hebasto>
is cache shared between master and branch builds?
< sipsorcery>
but even once the cache is updated the job now fails to complete in under the 60 minute limit 75% of the time...
< sipsorcery>
hebasto: yes
< kallewoof>
wumpus: I just (re?-)registered to bitcoin-core-dev. I don't see your Bitcoin Core release announcement on bitcoin-dev though.
< sipsorcery>
kallewoof: most recent subject was "[bitcoin-core-dev] Bitcoin Core 0.19.0.1 released"
< kallewoof>
sipsorcery: Yeah, that's bitcoin-core-dev, I'm asking about bitcoin-dev. "<wumpus> (I send all announcements including RCs to bitcoin-core-dev, and only final release announcements to bitcoin-dev)"
< wumpus>
kallewoof: I don't know the details but in the past there were some issues with the mailing lists at some point with delivery, resulting in mass-unsubscribes
< wumpus>
we also used to have a sendy-based notification list for new releases, but that broke down at some point, it's becoming harder and harder to do mail-related things, I guess most people get their updates through twitter/reddit or otherwise indirectly
< elichai2>
`/usr/bin/s390x-linux-gnu-ar: libbitcoin_server.a: No space left on device` :O
< elichai2>
`{standard input}: Fatal error: can't write 60 bytes to section .text of test/test_bitcoin-key_tests.o: 'No space left on device'`
< wumpus>
looking at my mail history, a "Bitcoin Core 0.19.0.1 released" mail went to To: Bitcoin development mailing list <bitcoin-dev@lists.linuxfoundation.org>, Bitcoin Core development mailing list <bitcoin-core-dev@lists.linuxfoundation.org>
< wumpus>
elichai2: in which PR do you need travis kicked?
< wumpus>
i do think it's an intermittent issue, i've seen the s390 build run out of disk space before
< elichai2>
wumpus: oh ok. then I hope another kick will fix it
< fanquake>
I saw it today as well
< bitcoin-git>
[bitcoin] Sjors closed pull request #16539: wallet: lower -txmaxfee default from 0.1 to 0.01 BTC (master...2019/08/lower_txmaxfee) https://github.com/bitcoin/bitcoin/pull/16539
< elichai2>
wumpus: worked :)
< wumpus>
elichai2: great!
< fanquake>
wumpus did you want to tag a 0.19.1rc1 in the detached sigs repo? We've got macOS and win signatures up now.
< wumpus>
I don't think I've ever done that before, but sure
< wumpus>
* [new tag] v0.19.1rc1 -> v0.19.1rc1
< fanquake>
?
< bitcoin-git>
[bitcoin] kallewoof closed pull request #17892: bug-fix: delay flushing undo files until after they are finalized (master...200108-reflush-undo) https://github.com/bitcoin/bitcoin/pull/17892
< hebasto>
#15706 is added to the 0.18.2 milestone, but not to the 0.20.0. Is this intended?
< bitcoin-git>
[bitcoin] luke-jr opened pull request #18007: Bugfix: GUI: Hide the HD/encrypt icons earlier so they get re-shown if another wallet is open (master...bugfix_for_pr17935) https://github.com/bitcoin/bitcoin/pull/18007