You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- name: Test install
kewlfft.aur.aur:
name: units
state: present
use: yay
become: yes
become_user: aur_builder
- name: Remove test package
community.general.pacman:
name: units
state: removed
remove_nosave: true
- name: Test reinstall
kewlfft.aur.aur:
name: units
state: present
use: yay
become: yes
become_user: aur_builder
produces:
TASK [test : Test install] ***************************************************************
changed: [iota]
TASK [test : Remove test package] ********************************************************
--- before
+++ after
@@ -1 +0,0 @@
-units-2.22-2
changed: [iota]
TASK [test : Test reinstall] *************************************************************
ok: [iota]
wheras expected behaviour would be:
TASK [test : Test reinstall] *************************************************************
changed: [iota]
I figured maybe this had to do with cached packages, but none of the package I tested with (grafana-bin, units) cached anything in /var/cache/pacman/pkg or ~/.cache/yay/ and reinstall is always recompiling too.
Manually running pacman -Rdd or pacman -Rns doesn't work either.
The community.general.pacman module does have this expected behaviour on reinstall.
Not a pacman / arch expert by any means, but Is there something specific I'm supposed to do here to solve this, or is this a bug?
The text was updated successfully, but these errors were encountered:
Okay so I tested with yay with the configured options --noconfirm --needed --cleanafter and it indeed does not rebuild, --cleanafter removes the sources but
==> Extracting sources...
-> Extracting units-2.22.tar.gz with bsdtar
==> Sources are ready.
-> units-2.22-2 already made -- skipping build
In this case it would be still nice to report a change as the package was not previously available for use, and now is. This would be good to test handlers, for example.
I might try to do a PR tomorrow.
jp1995
added a commit
to jp1995/ansible-aur
that referenced
this issue
Jul 7, 2023
produces:
wheras expected behaviour would be:
I figured maybe this had to do with cached packages, but none of the package I tested with (grafana-bin, units) cached anything in
/var/cache/pacman/pkg
or~/.cache/yay/
and reinstall is always recompiling too.Manually running
pacman -Rdd
orpacman -Rns
doesn't work either.The
community.general.pacman
module does have this expected behaviour on reinstall.Not a pacman / arch expert by any means, but Is there something specific I'm supposed to do here to solve this, or is this a bug?
The text was updated successfully, but these errors were encountered: