-
Notifications
You must be signed in to change notification settings - Fork 491
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
Add ansible 2.9.7 #1945
Add ansible 2.9.7 #1945
Conversation
456137b
to
abe2a8d
Compare
04953a3
to
3c164ea
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Exporting MSYS variable will not expose this value to entire msys env? See #1216
ansible/PKGBUILD
Outdated
|
||
prepare() { | ||
[[ -d ${pkgname}-${pkgver} ]] && rm -rf ${pkgname}-${pkgver} | ||
export MSYS=winsymlinks:lnk |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This work for me, any better solution???
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Alexpux exporting the MSYS variable will not affect the rest of the environment?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dont do that. Remove this export
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After some builds, realize that build step need symlinks as shortcuts:
...
prepare() {
[[ -d ${pkgname}-${pkgver} ]] && rm -rf ${pkgname}-${pkgver}
tar zxf "${srcdir}/${pkgname}-${pkgver}.tar.gz" || true
MSYS=winsymlinks:lnk tar zxf "${srcdir}/${pkgname}-${pkgver}.tar.gz"
}
...
This is how i reproduce in my msys shell, any hints why ci build is failing? (cd ansible; rm -rf pkg/ src/; rm *.pkg.tar.xz; pacman -Rs --noconfirm ansible)
(cd python-wcwidth; rm -rf pkg/ src/; rm *.pkg.tar.xz; pacman -Rs --noconfirm python-wcwidth)
(cd python-jinja; rm -rf pkg/ src/; rm *.pkg.tar.xz; pacman -Rs --noconfirm python-jinja)
(cd python-yaml; rm -rf pkg/ src/; rm *.pkg.tar.xz; pacman -Rs --noconfirm python-yaml)
(cd cython; rm -rf pkg/ src/; rm *.pkg.tar.xz; pacman -Rs --noconfirm cython)
(cd cython; makepkg -si --noconfirm)
(cd python-yaml; makepkg -si --noconfirm)
(cd python-jinja; makepkg -si --noconfirm)
(cd python-wcwidth; makepkg -si --noconfirm)
(cd ansible; makepkg -si --noconfirm) After that
|
The CI errors have been fixed in master (rebasing should help). Sorry :/ |
No problem, so far I've been using ansible without problems. And now ci is fixed, thank you |
@Alex1a ping |
@Alex1a fix other comments |
…tarball symbolic links; edit some wrong installation directories
Add ansible v2.9.7 package