1. 29 Apr, 2014 1 commit
  2. 21 Apr, 2014 2 commits
  3. 04 Apr, 2014 1 commit
  4. 21 Mar, 2014 1 commit
  5. 17 Mar, 2014 1 commit
  6. 14 Mar, 2014 2 commits
  7. 11 Mar, 2014 2 commits
  8. 08 Feb, 2014 1 commit
  9. 02 Feb, 2014 1 commit
  10. 16 Jan, 2014 1 commit
  11. 08 Jan, 2014 1 commit
  12. 07 Jan, 2014 1 commit
  13. 09 Dec, 2013 1 commit
  14. 05 Dec, 2013 2 commits
  15. 02 Dec, 2013 2 commits
  16. 28 Nov, 2013 2 commits
  17. 13 Nov, 2013 1 commit
  18. 12 Nov, 2013 1 commit
  19. 11 Nov, 2013 1 commit
  20. 01 Nov, 2013 1 commit
    • apt: allow specifying dpkg options · df5fd0e0
      This will allow specifying dpkg options as a string passed over to apt
      command. dpkg_options expects a comma-separated string of options to be
      passed as dpkg options which will be further expanded. For example
      dpkg_options='force-confdef,force-confold' will end up as
      -o \"Dpkg::Options::=--force-confold\" when passed to apt
      Example usage would be:
      -m apt -u ubuntu -s \
       -a "upgrade=dist update_cache=yes dpkg_options='force-confold'"
      or
      apt: upgrade=dist update_cache=yes dpkg_options='force-confold'
      Yegor Minin committed
  21. 21 Oct, 2013 1 commit
  22. 09 Oct, 2013 2 commits
  23. 28 Sep, 2013 2 commits
    • apt: do not consider not-removed and not-upgraded packages as changes. · 3a8c9f04
      If one pins a package and does a 'apt-get dist-upgrade' then the
      output looks like:
      
          # apt-get dist-upgrade
          Reading package lists... Done
          Building dependency tree
          Reading state information... Done
          Calculating upgrade... Done
          The following packages have been kept back:
            cassandra
          0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
      
      The check for any changes made should only be on the 'upgraded' and
      'newly installed' values and not include the 'to remove' and 'not
      upgraded' values.
      Blair Zajac committed
    • apt: pass child process stdout and stdout to m.fail_json() and m.exit_json(). · d133c0ae
      Without this, this fails:
      
          - name: apt-get dist-upgrade
            action: apt upgrade=dist
            register: apt_get_contents
      
          - name: apt-get clean
            action: command apt-get clean
            when: apt_get_contents.stdout.find("0 upgraded") == -1
      
      TASK: [apt-get clean] *********************************************************
      
      fatal: [192.168.2.2] => error while evaluating conditional: {% if apt_get_contents.stdout.find("0 upgraded") == -1 %} True {% else %} False {% endif %}
      
      FATAL: all hosts have already failed -- aborting
      Blair Zajac committed
  24. 17 Sep, 2013 1 commit
  25. 12 Sep, 2013 1 commit
  26. 12 Aug, 2013 2 commits
  27. 05 Aug, 2013 1 commit
    • apt: Run remove commands noninteractively · b950f945
      I'm seeing ansible hang when trying to remove a package, and the hung
      process is `whiptail` like in #2763. It looks like we only use
      `APT_ENVVARS` and `DPKG_OPTIONS` for the `apt` commands in install()
      and upgrade(). This change uses them in remove() as well, which fixes
      the hang.
      Alan Grosskurth committed
  28. 22 Jul, 2013 1 commit
  29. 20 Jul, 2013 1 commit
  30. 09 Jul, 2013 1 commit
  31. 30 Jun, 2013 1 commit