# Error when installing package with 'apt' module, not so when installing directly

**URL:** <https://forum.ansible.com/t/error-when-installing-package-with-apt-module-not-so-when-installing-directly/12102>\
**Category:** Ansible Project\
**Created:** [November 24, 2012, 6:42pm UTC](https://forum.ansible.com/t/error-when-installing-package-with-apt-module-not-so-when-installing-directly/12102 "2012-11-24T18:42:15Z")\
**Posts on this page:** 2\
**Page:** 2

<div class="post-metadata">

**Author:** ![Brian\_Coca1](https://avatars.discourse-cdn.com/v4/letter/b/278dde/32.png) [@Brian\_Coca1](https://forum.ansible.com/u/Brian_Coca1)\
**Post date:** [May 14, 2013, 7:59pm UTC](https://forum.ansible.com/t/error-when-installing-package-with-apt-module-not-so-when-installing-directly/12102/21 "2013-05-14T19:59:27Z")

</div>

ah, my patch doesn’t fix the issue. The path seems to be needed for programs executed in pre/upg/post scripts from the packages or possibly dpkg-configure.

Not that the module should not use get\_bin\_path, alas, that is not the source of the errors, but I’ll still submit the patch.

I’m torn between considering it a packager bug (use full paths or builtins!) or distro bug (sudo should have sbin paths defined, they’ve always had).

---

<div class="post-metadata">

**Author:** ![Brian\_Coca1](https://avatars.discourse-cdn.com/v4/letter/b/278dde/32.png) [@Brian\_Coca1](https://forum.ansible.com/u/Brian_Coca1)\
**Post date:** [May 16, 2013, 2:38am UTC](https://forum.ansible.com/t/error-when-installing-package-with-apt-module-not-so-when-installing-directly/12102/22 "2013-05-16T02:38:37Z")

</div>

I'll fix my patch so the absence of aptitude doesn't create issues

[Previous page](https://forum.ansible.com/t/error-when-installing-package-with-apt-module-not-so-when-installing-directly/12102.md?page=1)