# apt: upgrade=\[safe|full|dist\] seems to ignore "default\_release" parameter **URL:** \ **Category:** Ansible Developer\ **Created:** [April 22, 2014, 2:28pm UTC](https://forum.ansible.com/t/apt-upgrade-safe-full-dist-seems-to-ignore-default-release-parameter/15064 "2014-04-22T14:28:39Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Ralph](https://avatars.discourse-cdn.com/v4/letter/r/f475e1/32.png) [@Ralph](https://forum.ansible.com/u/Ralph)\ **Post date:** [April 22, 2014, 2:28pm UTC](https://forum.ansible.com/t/apt-upgrade-safe-full-dist-seems-to-ignore-default-release-parameter/15064/1 "2014-04-22T14:28:39Z")
Hello everybody! Here’s the thing! I add the Wheezy Backports repo to a newly provisioned VPS and want to do a safe-upgrade before doing anything else. My corresponding lines in the playbook look like this: - name: Add Wheezy Backports apt\_repository: repo=‘deb [http://ftp.us.debian.org/debian](http://ftp.us.debian.org/debian) wheezy-backports main’ state=present update\_cache=yes tags: - init - name: Initial safe-upgrade of the system (from wheezy-backports) apt: upgrade=safe default\_release=wheezy-backports update\_cache=yes tags: - init From where I’m standing, this should translate to “aptitude safe-upgrade -t wheezy-backports”. But it doesn’t seem to include the backports! Or I’m missing something! Same goes for apt: upgrade yes, full, or dist. If I’m ssh’ing to the box and running “aptitude safe-upgrade -t wheezy-backports” I’m getting quite a few upgardable packages… Thanks in advance! Cheers Ralph ---
**Author:** ![Strahinja\_Kustudic2](https://avatars.discourse-cdn.com/v4/letter/s/b4bc9f/32.png) [@Strahinja\_Kustudic2](https://forum.ansible.com/u/Strahinja_Kustudic2)\ **Post date:** [April 22, 2014, 10:17pm UTC](https://forum.ansible.com/t/apt-upgrade-safe-full-dist-seems-to-ignore-default-release-parameter/15064/2 "2014-04-22T22:17:47Z")
Please ask your question on [ansible-project@googlegroups.com](mailto:ansible-project@googlegroups.com), this isn’t a development question.