# Package module and cache updates

**URL:** <https://forum.ansible.com/t/package-module-and-cache-updates/25006>\
**Category:** Ansible Project\
**Created:** [July 17, 2017, 1:11pm UTC](https://forum.ansible.com/t/package-module-and-cache-updates/25006 "2017-07-17T13:11:17Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Hans\_Fritz](https://avatars.discourse-cdn.com/v4/letter/h/7ea924/32.png) [@Hans\_Fritz](https://forum.ansible.com/u/Hans_Fritz)\
**Post date:** [July 17, 2017, 1:11pm UTC](https://forum.ansible.com/t/package-module-and-cache-updates/25006/1 "2017-07-17T13:11:17Z")

</div>

When using the package module, how can I make sure the cache has been updated? It would seem that state: latest implies a cache refresh; but it doesn’t seem to actually be the case from my testing.

Is there a way to instruct the package module to refresh the cache? If not, is the only solution to use the distro’s package manager module to do it, defeating the purpose of an isomorphic package module?

---

<div class="post-metadata">

**Author:** ![Brian\_Coca](https://avatars.discourse-cdn.com/v4/letter/b/6de8d8/32.png) [@Brian\_Coca](https://forum.ansible.com/u/Brian_Coca)\
**Post date:** [July 18, 2017, 2:07am UTC](https://forum.ansible.com/t/package-module-and-cache-updates/25006/2 "2017-07-18T02:07:00Z")

</div>

package serves the 'lowest common denominator' and does not deal with  
specific features of each packager, it does not defeat the purpose, it  
is just of limited use.

The same way it cannot 'autotranslate' package names across  
versions/os/distros, it cannot deal with the different ways package  
managers deal with their repos.