-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update to v6.1.0 #45
Merged
Merged
Update to v6.1.0 #45
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
this should be moved to the other exports really..
We don't have sudo or fakeroot in MSYS2 and file permissions don't work the same.
(looks like this dropped a "set -e" which should be fixed)
So that we call the right tools even if mingw variants are in PATH
Extended attributes are not necessary for pacman to work. Extended attributes may not even be supported by the file system to which we extract the files. And worst of all: pacman cannot handle extended attributes, but simply stops extracting files when it encounters an extended attribute. This is particularly nasty when creating packages on a system configured to cache, say, file integrity information about .exe files in extended attributes, as the created packages will fail to install any .exe files. The fix is very easy: simply pass the -no-xattrs option to bsdtar. Signed-off-by: Johannes Schindelin <[email protected]>
In case a file "foo.exe" gets renamed to "foo" the msys2 .exe interpolation makes pacman think an untracker file is replaced. In case foo and foo.exe are the same file and foo.exe existed in the old package version we can be sure it's handled by the old package and ignore the conflict.
This allows to use pacman completely unattended using the --noconfirm switch which automatically accepts the default answer. See msys2/MSYS2-packages#1141
In case a package gets upgrade and a filename has changed case this allows the upgrade to go through without any conflicts. Similarly in case two different packages contain the same file with a different case this makes it correctly detect a conflict. This only handles ASCII parts of paths, so Unicode filenames still can lead to invalid conflict detection.
a2x seems to fail when a value to an argument looks like an argument itself. The best fix seems to be to attach the value to the argument using an equal sign. https://bugs.python.org/issue9334
Improves compatibility with Windows targets, specifically when using powershell for string transforming package names and piping into pacman as it's virtually impossible to send newline only terminated strings through pipes Allows for stuff such as ```powershell $a="vim nano" $b="cmake ninja" $a.Split(' '), $b.Split(' ').ForEach({Write-Output mingw-w64-ucrt-x86_64-$_}) | pacman -S --needed - ``` Signed-off-by: Christopher Degawa <[email protected]>
Unless `-ffat-lto-objects` get passed to the compiler, It will only generate LTO bytecode. see: https://wiki.ubuntu.com/ToolChain/LTO : Implementation https://fedoraproject.org/wiki/Changes/LTOBuildImprovements
Cygwin bash is struggling with the thousands of commands that get invoked when lint_pkgbuild is run. This especially is annoying for split packages because the calls get multiplied by the package count. For example when running --printsrcinfo: msys/brotli (4 packages) * 39.8 seconds with linting * 7 seconds without msys/tar (1 package) * 10.2 seconds with linting * 2 seconds without This changes the default to not lint the PKGBUILD and adds a MAKEPKG_LINT_PKGBUILD env var that can be used to enable linting. We can for example enable this in CI.
Our keyring contains SHA1 signatures, which gnupg 2.4 no longer imports by default. We can't easily get rid of them now, so allow them for now. See msys2/MSYS2-keyring#45
They are Linux only, so don't include them. The autodeps machinery itself can stay.
Next some backports |
lazka
added a commit
to lazka/MSYS2-packages
that referenced
this pull request
May 5, 2024
See msys2/msys2-pacman#45 makepkg.conf synced with the upstream version: https://gitlab.archlinux.org/pacman/pacman/-/blob/v6.1.0/etc/makepkg.conf.in
lazka
added a commit
to lazka/MSYS2-packages
that referenced
this pull request
May 5, 2024
See msys2/msys2-pacman#45 makepkg.conf synced with the upstream version: https://gitlab.archlinux.org/pacman/pacman/-/blob/v6.1.0/etc/makepkg.conf.in
lazka
added a commit
to lazka/MSYS2-packages
that referenced
this pull request
May 6, 2024
See msys2/msys2-pacman#45 makepkg.conf synced with the upstream version: https://gitlab.archlinux.org/pacman/pacman/-/blob/v6.1.0/etc/makepkg.conf.in Skip patches only changing CI configs
lazka
added a commit
to lazka/MSYS2-packages
that referenced
this pull request
May 6, 2024
See msys2/msys2-pacman#45 makepkg.conf synced with the upstream version: https://gitlab.archlinux.org/pacman/pacman/-/blob/v6.1.0/etc/makepkg.conf.in Skip patches only changing CI configs
lazka
added a commit
to lazka/MSYS2-packages
that referenced
this pull request
May 9, 2024
Same as msys2#4584 but with an additional backport: msys2/msys2-pacman#49 Old message: See msys2/msys2-pacman#45 makepkg.conf synced with the upstream version: https://gitlab.archlinux.org/pacman/pacman/-/blob/v6.1.0/etc/makepkg.conf.in Skip patches only changing CI configs
stahta01
pushed a commit
to stahta01/MSYS2-32bit-packages
that referenced
this pull request
May 9, 2024
See msys2/msys2-pacman#45 makepkg.conf synced with the upstream version: https://gitlab.archlinux.org/pacman/pacman/-/blob/v6.1.0/etc/makepkg.conf.in Skip patches only changing CI configs
stahta01
pushed a commit
to stahta01/MSYS2-32bit-packages
that referenced
this pull request
May 9, 2024
Same as #4584 but with an additional backport: msys2/msys2-pacman#49 Old message: See msys2/msys2-pacman#45 makepkg.conf synced with the upstream version: https://gitlab.archlinux.org/pacman/pacman/-/blob/v6.1.0/etc/makepkg.conf.in Skip patches only changing CI configs
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Rebase diary:
Minimal rebase with things squashed. Cleanups and backports can come later.
in upstream to reduce the diff
functionality lived in makepkg.sh.in and there was some basic patching to make
it work for mingw packages, but we never used it so remove for now.
range diff: