Actions
Feature #285
closedMsys2-next after 231202
Start date:
03/02/2024
Due date:
% Done:
0%
Estimated time:
Description
- Update to use autoconf-2.72 package
Files
Actions
Added by Marko Lindqvist over 2 years ago. Updated over 2 years ago.
0%
Description
- Update to use autoconf-2.72 package
Files
| 0028-Update-msys2-environment-to-240309-level.patch (5.16 KB) 0028-Update-msys2-environment-to-240309-level.patch | Marko Lindqvist, 03/17/2024 10:06 AM | ||
| 0010-Update-msys2-environment-to-240309-level.patch (5.36 KB) 0010-Update-msys2-environment-to-240309-level.patch | Marko Lindqvist, 03/21/2024 09:32 PM | ||
| 0004-Update-msys2-environment-to-240323-level.patch (5.41 KB) 0004-Update-msys2-environment-to-240323-level.patch | Marko Lindqvist, 03/26/2024 03:36 AM | ||
| 0002-Update-msys2-environment-to-240406-level.patch (5.55 KB) 0002-Update-msys2-environment-to-240406-level.patch | Marko Lindqvist, 04/08/2024 04:54 AM |
- Fixed a typo in a dll name
- More required dlls installed
- Updated to upstream snapshot 230223
- Fixed a dll name
- More required dlls installed
CI build, that uses older msys2 version, fails. That's easy to fix.
But the snapshot contains xz version that is affected by CVE-2024-3094 backdoor exploit, and for that reason I want to create a completely new snapshot (even though the nature of the backdoor is such that it would never be active in our build)
Marko Lindqvist wrote in #note-4:
CI build, that uses older msys2 version, fails. That's easy to fix.
But the snapshot contains xz version that is affected by CVE-2024-3094 backdoor exploit, and for that reason I want to create a completely new snapshot (even though the nature of the backdoor is such that it would never be active in our build)
These fixed.