Closed grdryn closed 2 years ago
Hey @grdryn , thanks for the report. Would you be so kind to specify your guest OS version, and maybe paste the relevant Ansible output here? That would help me debugging this particular issue
It's not intentional behaviour, as it should update the extension....
@PeterMosmans I'm on Fedora 36 (Silverblue variant, with ansible running from a toolbx container in Podman, but I don't think any of that is important).
I've created #18 which I believe fixes the issue...which I think was caused by myself in 2019 in #2 :see_no_evil:
Edit: I forgot you asked for ansible output. Here it is, in case it's useful.
Installing old version first:
then attempting to install the new version:
^as you can see in the attempt to upgrade, it skipped the unzip step. Now that I've applied #18, that "skipped" status is a "changed" status :slightly_smiling_face:
Haha, that made me laugh: You fixed an issue - then you ran into an issue, created by that issue, which you fixed.. as well :) Thanks for posting everything, and the fix. I'll merge your fix (for you bug ;) )
Have great one,
Peter
Thanks a lot @PeterMosmans! :pray:
Hi! If I install an extension, and then a new version becomes available, I can update that from extensions.gnome.org, but I don't seem to be able to get this role to update it (even if I specify the
url
field with theversion_tag
part set to the value for the newer version).Here's a reproducer:
Is this intentional behaviour, or would being able to update extensions be an improvement? Thanks!