Debian Package Tracker
Register | Log in
Subscribe

ansible

Configuration management, deployment, and task execution system

Choose email to subscribe with

general
  • source: ansible (main)
  • version: 2.10.7-1
  • maintainer: Harlan Lieberman-Berg (DMD)
  • uploaders: Lee Garrett [DMD]
  • arch: all
  • std-ver: 4.5.1
  • VCS: Git (Browse, QA)
versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]
[pool directory]
  • oldstable: 2.2.1.0-2+deb9u1
  • old-sec: 2.2.1.0-2+deb9u2
  • old-bpo: 2.7.5+dfsg-1~bpo9+1
  • stable: 2.7.7+dfsg-1
  • stable-bpo: 2.9.16+dfsg-1~bpo10+2
  • testing: 2.9.16+dfsg-1.1
  • unstable: 2.10.7-1
  • exp: 2.10.7-2
versioned links
  • 2.2.1.0-2+deb9u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 2.2.1.0-2+deb9u2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 2.7.5+dfsg-1~bpo9+1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 2.7.7+dfsg-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 2.9.16+dfsg-1~bpo10+2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 2.9.16+dfsg-1.1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 2.10.7-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 2.10.7-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
binaries
  • ansible (16 bugs: 0, 12, 4, 0)
action needed
Marked for autoremoval on 12 May: #983140 high
Version 2.9.16+dfsg-1.1 of ansible is marked for autoremoval from testing on Wed 12 May 2021. It is affected by #983140. The removal of ansible will also cause the removal of (transitive) reverse dependencies: ansible-lint, pytest-testinfra, python-mitogen. You should try to prevent the removal by fixing these RC bugs.
Created: 2021-02-28 Last update: 2021-04-13 20:01
lintian reports 2 errors and 71 warnings high
Lintian reports 2 errors and 71 warnings about this package. You should make the package lintian clean getting rid of them.
Created: 2021-01-27 Last update: 2021-04-11 10:16
16 security issues in stretch high

There are 16 open security issues in stretch.

15 important issues:
  • CVE-2019-10206: ansible-playbook -k and ansible cli tools, all versions 2.8.x before 2.8.4, all 2.7.x before 2.7.13 and all 2.6.x before 2.6.19, prompt passwords by expanding them from templates as they could contain special characters. Passwords should be wrapped to prevent templates trigger and exposing them.
  • CVE-2020-10685: A flaw was found in Ansible Engine affecting Ansible Engine versions 2.7.x before 2.7.17 and 2.8.x before 2.8.11 and 2.9.x before 2.9.7 as well as Ansible Tower before and including versions 3.4.5 and 3.5.5 and 3.6.3 when using modules which decrypts vault files such as assemble, script, unarchive, win_copy, aws_s3 or copy modules. The temporary directory is created in /tmp leaves the s ts unencrypted. On Operating Systems which /tmp is not a tmpfs but part of the root partition, the directory is only cleared on boot and the decryp emains when the host is switched off. The system will be vulnerable when the system is not running. So decrypted data must be cleared as soon as possible and the data which normally is encrypted ble.
  • CVE-2020-10729:
  • CVE-2020-14330: An Improper Output Neutralization for Logs flaw was found in Ansible when using the uri module, where sensitive data is exposed to content and json output. This flaw allows an attacker to access the logs or outputs of performed tasks to read keys used in playbooks from other users within the uri module. The highest threat from this vulnerability is to data confidentiality.
  • CVE-2020-14332: A flaw was found in the Ansible Engine when using module_args. Tasks executed with check mode (--check-mode) do not properly neutralize sensitive data exposed in the event data. This flaw allows unauthorized users to read this data. The highest threat from this vulnerability is to confidentiality.
  • CVE-2020-14365: A flaw was found in the Ansible Engine, in ansible-engine 2.8.x before 2.8.15 and ansible-engine 2.9.x before 2.9.13, when installing packages using the dnf module. GPG signatures are ignored during installation even when disable_gpg_check is set to False, which is the default behavior. This flaw leads to malicious packages being installed on the system and arbitrary code executed via package installation scripts. The highest threat from this vulnerability is to integrity and system availability.
  • CVE-2020-1733: A race condition flaw was found in Ansible Engine 2.7.17 and prior, 2.8.9 and prior, 2.9.6 and prior when running a playbook with an unprivileged become user. When Ansible needs to run a module with become user, the temporary directory is created in /var/tmp. This directory is created with "umask 77 && mkdir -p <dir>"; this operation does not fail if the directory already exists and is owned by another user. An attacker could take advantage to gain control of the become user as the target directory can be retrieved by iterating '/proc/<pid>/cmdline'.
  • CVE-2020-1735: A flaw was found in the Ansible Engine when the fetch module is used. An attacker could intercept the module, inject a new path, and then choose a new destination path on the controller node. All versions in 2.7.x, 2.8.x and 2.9.x branches are believed to be vulnerable.
  • CVE-2020-1739: A flaw was found in Ansible 2.7.16 and prior, 2.8.8 and prior, and 2.9.5 and prior when a password is set with the argument "password" of svn module, it is used on svn command line, disclosing to other users within the same node. An attacker could take advantage by reading the cmdline file from that particular PID on the procfs.
  • CVE-2020-1740: A flaw was found in Ansible Engine when using Ansible Vault for editing encrypted files. When a user executes "ansible-vault edit", another user on the same computer can read the old and new secret, as it is created in a temporary file with mkstemp and the returned file descriptor is closed and the method write_data is called to write the existing secret in the file. This method will delete the file before recreating it insecurely. All versions in 2.7.x, 2.8.x and 2.9.x branches are believed to be vulnerable.
  • CVE-2021-20178:
  • CVE-2021-20180:
  • CVE-2021-20191:
  • CVE-2021-20228:
  • CVE-2021-3447: A flaw was found in several ansible modules, where parameters containing credentials, such as secrets, were being logged in plain-text on managed nodes, as well as being made visible on the controller node when run in verbose mode. These parameters were not protected by the no_log feature. An attacker can take advantage of this information to steal those credentials, provided when they have access to the log files containing them. The highest threat from this vulnerability is to data confidentiality. This flaw affects Red Hat Ansible Automation Platform in versions before 1.2.2 and Ansible Tower in versions before 3.8.2.
1 issue postponed or untriaged:
  • CVE-2019-14905: (needs triaging) A vulnerability was found in Ansible Engine versions 2.9.x before 2.9.3, 2.8.x before 2.8.8, 2.7.x before 2.7.16 and earlier, where in Ansible's nxos_file_copy module can be used to copy files to a flash or bootflash on NXOS devices. Malicious code could craft the filename parameter to perform OS command injections. This could result in a loss of confidentiality of the system among other issues.
Created: 2021-02-19 Last update: 2021-04-03 04:23
4 security issues in sid high

There are 4 open security issues in sid.

4 important issues:
  • CVE-2021-20178:
  • CVE-2021-20180:
  • CVE-2021-20191:
  • CVE-2021-3447: A flaw was found in several ansible modules, where parameters containing credentials, such as secrets, were being logged in plain-text on managed nodes, as well as being made visible on the controller node when run in verbose mode. These parameters were not protected by the no_log feature. An attacker can take advantage of this information to steal those credentials, provided when they have access to the log files containing them. The highest threat from this vulnerability is to data confidentiality. This flaw affects Red Hat Ansible Automation Platform in versions before 1.2.2 and Ansible Tower in versions before 3.8.2.
Created: 2021-02-19 Last update: 2021-04-03 04:23
24 security issues in buster high

There are 24 open security issues in buster.

2 important issues:
  • CVE-2021-20228:
  • CVE-2021-3447: A flaw was found in several ansible modules, where parameters containing credentials, such as secrets, were being logged in plain-text on managed nodes, as well as being made visible on the controller node when run in verbose mode. These parameters were not protected by the no_log feature. An attacker can take advantage of this information to steal those credentials, provided when they have access to the log files containing them. The highest threat from this vulnerability is to data confidentiality. This flaw affects Red Hat Ansible Automation Platform in versions before 1.2.2 and Ansible Tower in versions before 3.8.2.
22 issues left for the package maintainer to handle:
  • CVE-2019-10156: (needs triaging) A flaw was discovered in the way Ansible templating was implemented in versions before 2.6.18, 2.7.12 and 2.8.2, causing the possibility of information disclosure through unexpected variable substitution. By taking advantage of unintended variable substitution the content of any variable may be disclosed.
  • CVE-2019-10206: (needs triaging) ansible-playbook -k and ansible cli tools, all versions 2.8.x before 2.8.4, all 2.7.x before 2.7.13 and all 2.6.x before 2.6.19, prompt passwords by expanding them from templates as they could contain special characters. Passwords should be wrapped to prevent templates trigger and exposing them.
  • CVE-2019-14846: (needs triaging) In Ansible, all Ansible Engine versions up to ansible-engine 2.8.5, ansible-engine 2.7.13, ansible-engine 2.6.19, were logging at the DEBUG level which lead to a disclosure of credentials if a plugin used a library that logged credentials at the DEBUG level. This flaw does not affect Ansible modules, as those are executed in a separate process.
  • CVE-2019-14858: (needs triaging) A vulnerability was found in Ansible engine 2.x up to 2.8 and Ansible tower 3.x up to 3.5. When a module has an argument_spec with sub parameters marked as no_log, passing an invalid parameter name to the module will cause the task to fail before the no_log options in the sub parameters are processed. As a result, data in the sub parameter fields will not be masked and will be displayed if Ansible is run with increased verbosity and present in the module invocation arguments for the task.
  • CVE-2019-14864: (needs triaging) Ansible, versions 2.9.x before 2.9.1, 2.8.x before 2.8.7 and Ansible versions 2.7.x before 2.7.15, is not respecting the flag no_log set it to True when Sumologic and Splunk callback plugins are used send tasks results events to collectors. This would discloses and collects any sensitive data.
  • CVE-2019-14904: (needs triaging) A flaw was found in the solaris_zone module from the Ansible Community modules. When setting the name for the zone on the Solaris host, the zone name is checked by listing the process with the 'ps' bare command on the remote machine. An attacker could take advantage of this flaw by crafting the name of the zone and executing arbitrary commands in the remote host. Ansible Engine 2.7.15, 2.8.7, and 2.9.2 as well as previous versions are affected.
  • CVE-2019-14905: (needs triaging) A vulnerability was found in Ansible Engine versions 2.9.x before 2.9.3, 2.8.x before 2.8.8, 2.7.x before 2.7.16 and earlier, where in Ansible's nxos_file_copy module can be used to copy files to a flash or bootflash on NXOS devices. Malicious code could craft the filename parameter to perform OS command injections. This could result in a loss of confidentiality of the system among other issues.
  • CVE-2020-10684: (needs triaging) A flaw was found in Ansible Engine, all versions 2.7.x, 2.8.x and 2.9.x prior to 2.7.17, 2.8.9 and 2.9.6 respectively, when using ansible_facts as a subkey of itself and promoting it to a variable when inject is enabled, overwriting the ansible_facts after the clean. An attacker could take advantage of this by altering the ansible_facts, such as ansible_hosts, users and any other key data which would lead into privilege escalation or code injection.
  • CVE-2020-10685: (needs triaging) A flaw was found in Ansible Engine affecting Ansible Engine versions 2.7.x before 2.7.17 and 2.8.x before 2.8.11 and 2.9.x before 2.9.7 as well as Ansible Tower before and including versions 3.4.5 and 3.5.5 and 3.6.3 when using modules which decrypts vault files such as assemble, script, unarchive, win_copy, aws_s3 or copy modules. The temporary directory is created in /tmp leaves the s ts unencrypted. On Operating Systems which /tmp is not a tmpfs but part of the root partition, the directory is only cleared on boot and the decryp emains when the host is switched off. The system will be vulnerable when the system is not running. So decrypted data must be cleared as soon as possible and the data which normally is encrypted ble.
  • CVE-2020-10729: (needs triaging)
  • CVE-2020-14330: (needs triaging) An Improper Output Neutralization for Logs flaw was found in Ansible when using the uri module, where sensitive data is exposed to content and json output. This flaw allows an attacker to access the logs or outputs of performed tasks to read keys used in playbooks from other users within the uri module. The highest threat from this vulnerability is to data confidentiality.
  • CVE-2020-14332: (needs triaging) A flaw was found in the Ansible Engine when using module_args. Tasks executed with check mode (--check-mode) do not properly neutralize sensitive data exposed in the event data. This flaw allows unauthorized users to read this data. The highest threat from this vulnerability is to confidentiality.
  • CVE-2020-14365: (needs triaging) A flaw was found in the Ansible Engine, in ansible-engine 2.8.x before 2.8.15 and ansible-engine 2.9.x before 2.9.13, when installing packages using the dnf module. GPG signatures are ignored during installation even when disable_gpg_check is set to False, which is the default behavior. This flaw leads to malicious packages being installed on the system and arbitrary code executed via package installation scripts. The highest threat from this vulnerability is to integrity and system availability.
  • CVE-2020-1733: (needs triaging) A race condition flaw was found in Ansible Engine 2.7.17 and prior, 2.8.9 and prior, 2.9.6 and prior when running a playbook with an unprivileged become user. When Ansible needs to run a module with become user, the temporary directory is created in /var/tmp. This directory is created with "umask 77 && mkdir -p <dir>"; this operation does not fail if the directory already exists and is owned by another user. An attacker could take advantage to gain control of the become user as the target directory can be retrieved by iterating '/proc/<pid>/cmdline'.
  • CVE-2020-1735: (needs triaging) A flaw was found in the Ansible Engine when the fetch module is used. An attacker could intercept the module, inject a new path, and then choose a new destination path on the controller node. All versions in 2.7.x, 2.8.x and 2.9.x branches are believed to be vulnerable.
  • CVE-2020-1739: (needs triaging) A flaw was found in Ansible 2.7.16 and prior, 2.8.8 and prior, and 2.9.5 and prior when a password is set with the argument "password" of svn module, it is used on svn command line, disclosing to other users within the same node. An attacker could take advantage by reading the cmdline file from that particular PID on the procfs.
  • CVE-2020-1740: (needs triaging) A flaw was found in Ansible Engine when using Ansible Vault for editing encrypted files. When a user executes "ansible-vault edit", another user on the same computer can read the old and new secret, as it is created in a temporary file with mkstemp and the returned file descriptor is closed and the method write_data is called to write the existing secret in the file. This method will delete the file before recreating it insecurely. All versions in 2.7.x, 2.8.x and 2.9.x branches are believed to be vulnerable.
  • CVE-2020-1746: (needs triaging) A flaw was found in the Ansible Engine affecting Ansible Engine versions 2.7.x before 2.7.17 and 2.8.x before 2.8.11 and 2.9.x before 2.9.7 as well as Ansible Tower before and including versions 3.4.5 and 3.5.5 and 3.6.3 when the ldap_attr and ldap_entry community modules are used. The issue discloses the LDAP bind password to stdout or a log file if a playbook task is written using the bind_pw in the parameters field. The highest threat from this vulnerability is data confidentiality.
  • CVE-2020-1753: (needs triaging) A security flaw was found in Ansible Engine, all Ansible 2.7.x versions prior to 2.7.17, all Ansible 2.8.x versions prior to 2.8.11 and all Ansible 2.9.x versions prior to 2.9.7, when managing kubernetes using the k8s module. Sensitive parameters such as passwords and tokens are passed to kubectl from the command line, not using an environment variable or an input configuration file. This will disclose passwords and tokens from process list and no_log directive from debug module would not have any effect making these secrets being disclosed on stdout and log files.
  • CVE-2021-20178: (needs triaging)
  • CVE-2021-20180: (needs triaging)
  • CVE-2021-20191: (needs triaging)

You can find information about how to handle these issues in the security team's documentation.

Created: 2021-02-19 Last update: 2021-04-03 04:23
5 security issues in bullseye high

There are 5 open security issues in bullseye.

5 important issues:
  • CVE-2021-20178:
  • CVE-2021-20180:
  • CVE-2021-20191:
  • CVE-2021-20228:
  • CVE-2021-3447: A flaw was found in several ansible modules, where parameters containing credentials, such as secrets, were being logged in plain-text on managed nodes, as well as being made visible on the controller node when run in verbose mode. These parameters were not protected by the no_log feature. An attacker can take advantage of this information to steal those credentials, provided when they have access to the log files containing them. The highest threat from this vulnerability is to data confidentiality. This flaw affects Red Hat Ansible Automation Platform in versions before 1.2.2 and Ansible Tower in versions before 3.8.2.
Created: 2021-02-19 Last update: 2021-04-03 04:23
The package has not entered testing even though the delay is over normal
The package has not entered testing even though the 20-day delay is over. Check why.
Created: 2021-02-20 Last update: 2021-04-13 19:58
2 bugs tagged patch in the BTS normal
The BTS contains patches fixing 2 bugs, consider including or untagging them.
Created: 2020-10-19 Last update: 2021-04-13 19:54
Does not build reproducibly during testing normal
A package building reproducibly enables third parties to verify that the source matches the distributed binaries. It has been identified that this source package produced different results, failed to build or had other issues in a test environment. Please read about how to improve the situation!
Created: 2018-11-06 Last update: 2021-04-13 17:35
44 new commits since last upload, is it time to release? normal
vcswatch reports that this package seems to have new commits in its VCS but has not yet updated debian/changelog. You should consider updating the Debian changelog and uploading this new version into the archive.

Here are the relevant commit logs:
commit 71c8e413389c0348faed46299ad76feca6f93e04
Author: Lee Garrett <lgarrett@rocketjump.eu>
Date:   Thu Mar 25 18:37:45 2021 +0100

    Update changelog and upload to experimental

commit 35967412f25e4a34f348fe5b32a68a9c2d26b9a5
Author: Lee Garrett <lgarrett@rocketjump.eu>
Date:   Wed Mar 24 03:58:44 2021 +0100

    Fix SyntaxWarnings

commit 57b894215591e83dde8e30f9ba6ad705744c4902
Author: Lee Garrett <lgarrett@rocketjump.eu>
Date:   Wed Mar 24 02:36:43 2021 +0100

    Add unit tests
    
    unit-tests-stable contains all known-good unit tests. unit-tests-flaky contains
    all tests that are broken for various reasons (see comments on the list).

commit 0ec8962b4ff4f25659873c727315b27638382150
Author: Lee Garrett <lgarrett@rocketjump.eu>
Date:   Wed Feb 10 00:45:13 2021 +0100

    Update changelog and release to unstable

commit c29985ec3556a90e30815f62ae8f34c35083bf2c
Author: Lee Garrett <lgarrett@rocketjump.eu>
Date:   Wed Feb 10 00:12:18 2021 +0100

    Fix /etc/ansible removal in maintainer scripts
    
    On 2nd upgrade when /etc/ansible already been removed, rmdir would fail and
    cause preinst to fail.

commit 864f92cfc84d8a5337690ea5158ca3f207828824
Author: Lee Garrett <lgarrett@rocketjump.eu>
Date:   Wed Feb 10 00:10:48 2021 +0100

    Fix whitespace error in debian/NEWS

commit 55eabcb9bc856c003af26255c8dc36165cd2144f
Merge: 68095ca86 a97df484a
Author: Lee Garrett <lgarrett@rocketjump.eu>
Date:   Tue Feb 9 23:28:32 2021 +0100

    Update upstream source from tag 'upstream/2.10.7'
    
    Update to upstream version '2.10.7'
    with Debian dir de900b50cf43167de67f086273196f47e234aecd

commit 68095ca86488898ec42bd808cd5a8e274c11bb88
Author: Lee Garrett <lgarrett@rocketjump.eu>
Date:   Tue Feb 9 22:41:22 2021 +0100

    Bump Standards-Version

commit 7a95b0c9d45b3ed04b10ec0e8cf7f4ba0fb39481
Author: Lee Garrett <lgarrett@rocketjump.eu>
Date:   Tue Feb 9 22:40:39 2021 +0100

    Fix minor lintian warnings in maintainer scripts

commit 0bd9ac42afe916bac052a2cbdc4c5c07eec1a7a3
Merge: df601ee7f ce60e2b78
Author: Lee Garrett <lgarrett@rocketjump.eu>
Date:   Tue Feb 9 21:00:29 2021 +0100

    Update upstream source from tag 'upstream/2.10.6'
    
    Update to upstream version '2.10.6'
    with Debian dir 33188fe577724b5dc08768ae44f8e4853791ec60

commit df601ee7fb9ecab9b8d0bfc4d56da55cccd9d362
Author: Lee Garrett <lgarrett@rocketjump.eu>
Date:   Fri Jan 8 00:45:11 2021 +0100

    Release to experimental

commit a357f70a7b6a389b0a9c140a872852c244a1277e
Author: Lee Garrett <lgarrett@rocketjump.eu>
Date:   Thu Jan 7 23:14:37 2021 +0100

    Update changelog

commit 8c6cf71836fdb03245aa5c1eeae4130c33609b6c
Author: Lee Garrett <lgarrett@rocketjump.eu>
Date:   Thu Jan 7 23:14:13 2021 +0100

    Add debian/NEWS entry explaining the package split

commit a1b1d1b03c08d8de8692864139f1f4a7c299021b
Author: Lee Garrett <lgarrett@rocketjump.eu>
Date:   Thu Jan 7 22:43:57 2021 +0100

    Fix deleting dot files
    
    Delete them from the install dir, not from the source, making cleanup easier.
    
    Also, the old find command choked on non-empty .github/ dir, so now we need to
    use -exec to work around that.

commit 3ce97cb99282bd940cbccee0dc6bc403aa0c2e25
Author: Lee Garrett <lgarrett@rocketjump.eu>
Date:   Thu Jan 7 22:43:43 2021 +0100

    Remove d/rules cruft

commit a9c3a98795cb7b13c2d96bf6082c4c09397cfa95
Author: Lee Garrett <lgarrett@rocketjump.eu>
Date:   Thu Jan 7 22:41:54 2021 +0100

    Remove lintian overrides
    
    This will need a revamp, anyway.

commit 7e2446b17e3ea358c2a37c4d4b2b05675d9b2cef
Author: Lee Garrett <lgarrett@rocketjump.eu>
Date:   Thu Jan 7 21:52:52 2021 +0100

    Remove d/ansible.links (#970422)
    
    The symlink was broken, the binaries moved to ansible-base, and there this is
    done correctly.

commit fd4282cfddcf470a41ee4662f33d50d522938285
Author: Lee Garrett <lgarrett@rocketjump.eu>
Date:   Thu Jan 7 21:51:47 2021 +0100

    Remove d/ansible.install
    
    Since it's only a single package now, pybuild will do the right thing.

commit c7ce7fe88353f410fca364fbeea42d745c15fb23
Author: Lee Garrett <lgarrett@rocketjump.eu>
Date:   Thu Jan 7 21:45:51 2021 +0100

    Remove python3-crypto from (build-)depends (#971309)
    
    This isn't needed in this package anymore, and has been fixed in ansible-base,
    too.

commit 04faa06cf9734f65fe7117878ee113135f9c9d55
Author: Lee Garrett <lgarrett@rocketjump.eu>
Date:   Thu Jan 7 21:44:52 2021 +0100

    Depend on ansible-base
    
    It provides the binaries.

commit 35d9d17bd33762bd0fb3ee083462f197623b6ab5
Author: Lee Garrett <lgarrett@rocketjump.eu>
Date:   Thu Jan 7 20:54:09 2021 +0100

    Remove man pages (now shipped in ansible-base)

commit 923eb5299c0f1fea9a878f23fde6b5ecf4af04bc
Author: Lee Garrett <lgarrett@rocketjump.eu>
Date:   Thu Jan 7 20:49:39 2021 +0100

    Conditionally remove conffiles on upgrade
    
    Remove /etc/ansible/ on upgrade unless any files were modified.

commit 19967252fd1b95f262392a6e95094a2f52c5e7fe
Author: Lee Garrett <lgarrett@rocketjump.eu>
Date:   Thu Jan 7 20:47:05 2021 +0100

    Remove all patches (code migrated to ansible-base)

commit cd34a663804ca31fe2e3ba57ddb5429e9ec37591
Author: Lee Garrett <lgarrett@rocketjump.eu>
Date:   Sat Dec 19 21:26:11 2020 +0100

    Remove ansible-doc (now built in ansible-base)

commit 7e14c3cf850e0364051d241c0d77db8d685c9666
Merge: 45a3c0e7f 0a6ca7918
Author: Lee Garrett <lgarrett@rocketjump.eu>
Date:   Fri Dec 18 23:19:32 2020 +0100

    Update upstream source from tag 'upstream/2.10.4'
    
    Update to upstream version '2.10.4'
    with Debian dir 9fbf0e33741bd80f113c34f77f639d90b2efa351

commit 45a3c0e7f599932d37c8254b27c6deece8486b5a
Author: Lee Garrett <lgarrett@rocketjump.eu>
Date:   Fri Dec 18 20:10:17 2020 +0100

    Update watch file for ansible 2.10.y

commit 0aed52ae04dc28a535af12c47c4d91effe2832c1
Author: Harlan Lieberman-Berg <hlieberman@setec.io>
Date:   Sun Feb 28 01:23:23 2021 -0500

    Properly reflect who has been doing all the work

commit a97df484a4db04e396c6c834a770273230c9b4b3
Author: Lee Garrett <lgarrett@rocketjump.eu>
Date:   Tue Feb 9 23:26:08 2021 +0100

    New upstream version 2.10.7

commit ce60e2b7885ec4d65b2cff9fc29d2d949e6b78ae
Author: Lee Garrett <lgarrett@rocketjump.eu>
Date:   Tue Feb 9 20:58:40 2021 +0100

    New upstream version 2.10.6

commit 0a6ca79184581df1315c1048c3931713e68e3628
Author: Lee Garrett <lgarrett@rocketjump.eu>
Date:   Fri Dec 18 23:17:45 2020 +0100

    New upstream version 2.10.4

commit d9774d226cf51a4f9c8b1a9fe23c7d42161e1674
Author: Lee Garrett <lgarrett@rocketjump.eu>
Date:   Fri Dec 18 19:57:33 2020 +0100

    Update changelog

commit f8c9d1be7b2fc6abedb6f5b598c99936bb8906fa
Merge: fc03d4c94 73cdb8e03
Author: Lee Garrett <lgarrett@rocketjump.eu>
Date:   Wed Dec 16 20:02:22 2020 +0100

    Update upstream source from tag 'upstream/2.9.16+dfsg'
    
    Update to upstream version '2.9.16+dfsg'
    with Debian dir 55c48cb26432b8ee03d680ba60dabaa3fbb08412

commit 73cdb8e03a9cedcccc78d287822d3aced37ba9df
Author: Lee Garrett <lgarrett@rocketjump.eu>
Date:   Wed Dec 16 20:01:54 2020 +0100

    New upstream version 2.9.16+dfsg

commit fc03d4c94ac6d224b386d0390b6a943817684c5f
Author: Lee Garrett <lgarrett@rocketjump.eu>
Date:   Fri Sep 11 07:50:50 2020 +0200

    Update changelog

commit a53ba201fda7bc674b1306d0d18c9913638a2ba1
Author: Lee Garrett <lgarrett@rocketjump.eu>
Date:   Fri Sep 11 07:32:14 2020 +0200

    Refresh quilt patches

commit c3a8e52ee752e5e27f3a87ef51388f020f729749
Author: Lee Garrett <lgarrett@rocketjump.eu>
Date:   Wed Sep 9 13:39:30 2020 +0200

    Remove hidden files from binary package (#963165)
    
    These are not needed and cause alarms by chkrootkit.

commit bd2a1f3d66bf4b4ac9d42769a15ad8f5f1c2298a
Author: Lee Garrett <lgarrett@rocketjump.eu>
Date:   Wed Sep 9 13:37:32 2020 +0200

    Bump Standards-Version (no changes needed)

commit 62a50f0b75472594ca1adbfe6bdc6e9a70c846ec
Merge: e3aaae26d 7309e188d
Author: Lee Garrett <lgarrett@rocketjump.eu>
Date:   Wed Sep 9 10:48:57 2020 +0200

    Update upstream source from tag 'upstream/2.9.13+dfsg'
    
    Update to upstream version '2.9.13+dfsg'
    with Debian dir 8f36e8804ee9851dc159fb09b5a5f4e6fbccc108

commit 7309e188d1bb3aec98951aee0502bf8f7a1ea83f
Author: Lee Garrett <lgarrett@rocketjump.eu>
Date:   Wed Sep 9 10:48:27 2020 +0200

    New upstream version 2.9.13+dfsg

commit e3aaae26d7c236c82473b182baa177cf80c31fb1
Author: Lee Garrett <lgarrett@rocketjump.eu>
Date:   Wed Sep 9 10:44:39 2020 +0200

    Fix d/watch to ansible v2.9.* for now.

commit f4325ceb0a3c24c3c3730b66539bea7b682d55c6
Merge: 3a350af3e 423cd5691
Author: Lee Garrett <lgarrett@rocketjump.eu>
Date:   Thu Jul 23 17:11:23 2020 +0200

    Update upstream source from tag 'upstream/2.9.11+dfsg'
    
    Update to upstream version '2.9.11+dfsg'
    with Debian dir b395392fe5f0c377ec92b1283f51e9d3aee0ac8f

commit 423cd5691a6902e331f5bab963bac544168e29e0
Author: Lee Garrett <lgarrett@rocketjump.eu>
Date:   Thu Jul 23 17:10:54 2020 +0200

    New upstream version 2.9.11+dfsg

commit 3a350af3e85b932ec46898f94d68efa928799e4e
Author: Lee Garrett <lgarrett@rocketjump.eu>
Date:   Sun May 31 22:55:04 2020 +0200

    Remove /usr/bin/ansible-connection symlink
    
    This binary is not meant to be used by end users, and now doesn't need to be
    shipped in /usr/bin/ to work anymore.

commit 28a73456189811727ebd790594748a609f0c213b
Author: Lee Garrett <lgarrett@rocketjump.eu>
Date:   Sun May 31 22:52:14 2020 +0200

    Remove unused link to JS library
    
    This link is unused, and the correct link is created by dh_sphinxdoc.
Created: 2020-06-09 Last update: 2021-04-11 18:59
testing migrations
  • This package is part of the ongoing testing transition known as auto-upperlimit-ansible. Please avoid uploads unrelated to this transition, they would likely delay it and require supplementary work from the release managers. On the other hand, if your package has problems preventing it to migrate to testing, please fix them as soon as possible. You can probably find supplementary information in the debian-release archives or in the corresponding release.debian.org bug.
  • excuses:
    • Migrates after: ansible-base
    • Migration status for ansible (2.9.16+dfsg-1.1 to 2.10.7-1): BLOCKED: Rejected/violates migration policy/introduces a regression
    • Issues preventing migration:
    • migrating ansible/2.10.7-1/amd64 to testing makes ansible-mitogen/0.2.9-2/amd64 uninstallable
    • migrating ansible/2.10.7-1/arm64 to testing makes ansible-mitogen/0.2.9-2/arm64 uninstallable
    • blocked by freeze: does not have autopkgtest (Follow the freeze policy when applying for an unblock)
    • Depends: ansible ansible-base
    • Additional info:
    • Piuparts tested OK - https://piuparts.debian.org/sid/source/a/ansible.html
    • 63 days old (needed 20 days)
    • Not considered
news
[rss feed]
  • [2021-04-01] Accepted ansible 2.9.16+dfsg-1~bpo10+2 (source) into buster-backports->backports-policy, buster-backports (Debian FTP Masters) (signed by: Pierre-Elliott Bécue)
  • [2021-03-25] Accepted ansible 2.10.7-2 (source) into experimental (Lee Garrett)
  • [2021-03-17] Accepted ansible 2.9.16+dfsg-1~bpo10+1 (source) into buster-backports->backports-policy, buster-backports (Debian FTP Masters) (signed by: Pierre-Elliott Bécue)
  • [2021-02-10] Accepted ansible 2.10.7-1 (source) into unstable (Lee Garrett)
  • [2021-01-27] Accepted ansible 2.2.1.0-2+deb9u2 (source) into oldstable (Markus Koschany)
  • [2021-01-13] ansible 2.9.16+dfsg-1.1 MIGRATED to testing (Debian testing watch)
  • [2021-01-08] Accepted ansible 2.9.16+dfsg-1.1 (source) into unstable (Sebastian Ramacher)
  • [2021-01-07] Accepted ansible 2.10.4-1 (source) into experimental (Lee Garrett)
  • [2020-12-22] ansible 2.9.16+dfsg-1 MIGRATED to testing (Debian testing watch)
  • [2020-12-16] Accepted ansible 2.9.16+dfsg-1 (source) into unstable (Lee Garrett)
  • [2020-09-16] ansible 2.9.13+dfsg-1 MIGRATED to testing (Debian testing watch)
  • [2020-09-11] Accepted ansible 2.9.13+dfsg-1 (source) into unstable (Lee Garrett)
  • [2020-06-05] ansible 2.9.9+dfsg-1 MIGRATED to testing (Debian testing watch)
  • [2020-05-30] Accepted ansible 2.9.9+dfsg-1 (source) into unstable (Lee Garrett)
  • [2020-05-15] ansible 2.9.7+dfsg-1 MIGRATED to testing (Debian testing watch)
  • [2020-05-09] Accepted ansible 2.9.7+dfsg-1 (source) into unstable (Lee Garrett)
  • [2020-05-05] Accepted ansible 1.7.2+dfsg-2+deb8u3 (source all) into oldoldstable (Sylvain Beucler)
  • [2020-04-14] Accepted ansible 2.9.6+dfsg-1~bpo10+1 (source all) into buster-backports, buster-backports (Debian FTP Masters) (signed by: Pierre-Elliott Bécue)
  • [2020-03-22] ansible 2.9.6+dfsg-1 MIGRATED to testing (Debian testing watch)
  • [2020-03-17] Accepted ansible 2.9.6+dfsg-1 (source) into unstable (Lee Garrett)
  • [2020-02-16] ansible 2.9.4+dfsg-1 MIGRATED to testing (Debian testing watch)
  • [2020-02-10] Accepted ansible 2.9.4+dfsg-1 (source) into unstable (Lee Garrett)
  • [2020-01-05] ansible 2.9.2+dfsg-1 MIGRATED to testing (Debian testing watch)
  • [2019-12-30] Accepted ansible 2.9.2+dfsg-1 (source) into unstable (Lee Garrett)
  • [2019-11-03] ansible 2.8.6+dfsg-1 MIGRATED to testing (Debian testing watch)
  • [2019-10-28] Accepted ansible 2.8.6+dfsg-1 (source) into unstable (Lee Garrett)
  • [2019-09-16] Accepted ansible 1.7.2+dfsg-2+deb8u2 (source all) into oldoldstable (Roberto C. Sanchez)
  • [2019-08-02] Accepted ansible 2.8.3+dfsg-1 (source all) into unstable (Lee Garrett)
  • [2019-07-09] ansible 2.7.8+dfsg-1 MIGRATED to testing (Debian testing watch)
  • [2019-03-07] Accepted ansible 2.2.1.0-2+deb9u1 (source all) into proposed-updates->stable-new, proposed-updates (Lee Garrett) (signed by: Harlan Lieberman-Berg)
  • 1
  • 2
bugs [bug history graph]
  • all: 21
  • RC: 0
  • I&N: 16
  • M&W: 5
  • F&P: 0
  • patch: 2
links
  • homepage
  • lintian (2, 71)
  • buildd: logs, exp, clang, reproducibility
  • popcon
  • browse source code
  • edit tags
  • other distros
  • security tracker
  • screenshots
ubuntu Ubuntu logo [Information about Ubuntu for Debian Developers]
  • version: 2.10.7-1
  • 10 bugs

Debian Package Tracker — Copyright 2013-2018 The Distro Tracker Developers
Report problems to the tracker.debian.org pseudo-package in the Debian BTS.
Documentation — Bugs — Git Repository — Contributing