Set appveyor VM version to previous Visual Studio 2019 release #19839

pull sipsorcery wants to merge 1 commits into bitcoin:master from sipsorcery:appveyor_fix changing 1 files +1 −1

sipsorcery commented at 12:12 pm on August 30, 2020: member

The Visual Studio 2019 Appveyor update includes a bump of cmake to 3.18.2.

The berkeleydb dependency from the pegged vcpkg commit now fails to build with the cmake update.

Setting the Appveyor VM back to the previous version should fix the immediate issue while a solution is identified for updating the berkeleydb build configuration.

Set appveyor vm version to previous Visual Studio 2019 release.

Latest vm version has updated cmake and the berkeleydb vcpkg now fails to build.

3ec8f4c080

fanquake added the label Windows on Aug 30, 2020
fanquake added the label Tests on Aug 30, 2020
hebasto approved
hebasto commented at 4:42 pm on August 30, 2020: member

ACK 3ec8f4c080eab61563f11659c5f1370a34b77dc5, AppVeyor build is ok now.

Travis build fail is unrelated to this PR change. @sipsorcery

Setting the Appveyor VM back to the previous version should fix the immediate issue while a solution is identified for updating the berkeleydb build configuration.

Will you take care of this?
MarcoFalke merged this on Aug 30, 2020
MarcoFalke closed this on Aug 30, 2020
sipsorcery commented at 5:46 pm on August 30, 2020: member

Will you take care of this?

Yes.
fanquake commented at 5:06 am on August 31, 2020: member

I assume this also needs to be backported to the 0.19 and 0.20 branches? Or, given they issue is less pressing there, will you backport the long-term fix to them instead?
MarcoFalke referenced this in commit 068bc21188 on Aug 31, 2020
laanwj referenced this in commit 80aa83aa40 on Sep 24, 2020
DrahtBot locked this on Feb 15, 2022