kicad-developers team mailing list archive

[Wayne Stambaugh <stambaughw@xxxxxxxxx>]

On 2/26/2016 5:05 AM, jp charras wrote:
> Le 25/02/2016 21:59, Wayne Stambaugh a écrit :
>> On 2/25/2016 3:50 PM, jp charras wrote:
> ...
>>>> On 2/25/2016 3:33 PM, Wayne Stambaugh wrote:
>>>>> Yep!  I just confirmed this.  It must have been the mingw32 updates that
>>>>> were just released.  I'm not sure which package is at fault.  I guess we
>>>>> will have to downgrade to the previous version.  This is one of the
>>>>> issues with msys2.  They tend to break things fairly often.
>>>>>
>>>>> Here is the list of packages that were just updated that may have caused
>>>>> the problem:
>>>>>
>>>>> mingw-w64-i686-crypto++
>>>>> mingw-w64-i686-openjpeg
>>>>> mingw-w64-i686-openssl
>>>>> mingw-w64-i686-crt-git
>>>>> mingw-w64-i686-headers-git
> 
> I installed the previous version of mingw-w64-i686-crt-git and
> mingw-w64-i686-headers-git, and the issue is fixed.
> 
> Last old version I installed from my cache:
> mingw-w64-i686-crt-git-5.0.0.4609.566d621-1-any.pkg.tar.xz
> mingw-w64-i686-headers-git-5.0.0.4609.566d621-1-any.pkg.tar.xz
> 
> Thanks for your advice, it was helpful to me.
> 

I just tested this and it also breaks mingw64 builds as well so expect a
bunch of broken nightly windows builds.  Our windows package devs are
going to have to pin the correct package versions in their pacman.conf
when the install/upgrade msys2 or stop building windows nightly
installers until the problem is resolved.  JP, have you notified the
msys2 project of the issue?