Debian Package Tracker

general

source: ansible (main)
version: 2.9.13+dfsg-1
maintainer: Harlan Lieberman-Berg (DMD)
uploaders: Lee Garrett [DMD]
arch: all
std-ver: 4.5.0
VCS: Git (Browse, QA)

versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]

[pool directory]

o-o-stable: 1.7.2+dfsg-2
o-o-sec: 1.7.2+dfsg-2+deb8u3
oldstable: 2.2.1.0-2+deb9u1
old-sec: 2.2.1.0-2+deb9u1
old-bpo: 2.7.5+dfsg-1~bpo9+1
stable: 2.7.7+dfsg-1
stable-bpo: 2.9.6+dfsg-1~bpo10+1
testing: 2.9.13+dfsg-1
unstable: 2.9.13+dfsg-1

versioned links

1.7.2+dfsg-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1.7.2+dfsg-2+deb8u3: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.2.1.0-2+deb9u1: [.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.6+dfsg-1~bpo10+1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
2.9.13+dfsg-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

ansible (15 bugs: 0, 13, 2, 0)
ansible-doc

action needed

A new upstream version is available: 2.9.14 high

A new upstream version 2.9.14 is available, you should consider packaging it.

Created: 2020-10-09 Last update: 2020-10-26 04:30

19 security issues in stretch high

There are 19 open security issues in stretch.

11 important issues:

CVE-2020-10684: 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: 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-1736: A flaw was found in Ansible Engine when a file is moved using atomic_move primitive as the file mode cannot be specified. This sets the destination files world-readable if the destination file does not exist and if the file exists, the file could be changed to have less restrictive permissions before the move. This could lead to the disclosure of sensitive data. 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.

8 issues skipped by the security teams:

CVE-2017-7481: Ansible before versions 2.3.1.0 and 2.4.0.0 fails to properly mark lookup-plugin results as unsafe. If an attacker could control the results of lookup() calls, they could inject Unicode strings to be parsed by the jinja2 templating system, resulting in code execution. By default, the jinja2 templating language is now marked as 'unsafe' and is not evaluated.
CVE-2019-10156: 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: 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: Ansible, all ansible_engine-2.x versions and ansible_engine-3.x up to ansible_engine-3.5, was 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: 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: 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: 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: 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.

Please fix them.

Created: 2017-04-22 Last update: 2020-10-07 06:00

6 security issues in sid high

There are 6 open security issues in sid.

6 important issues:

CVE-2020-10744: An incomplete fix was found for the fix of the flaw CVE-2020-1733 ansible: insecure temporary directory when running become_user from become directive. The provided fix is insufficient to prevent the race condition on systems using ACLs and FUSE filesystems. Ansible Engine 2.7.18, 2.8.12, and 2.9.9 as well as previous versions are affected and Ansible Tower 3.4.5, 3.5.6 and 3.6.4 as well as previous versions are affected.
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-1736: A flaw was found in Ansible Engine when a file is moved using atomic_move primitive as the file mode cannot be specified. This sets the destination files world-readable if the destination file does not exist and if the file exists, the file could be changed to have less restrictive permissions before the move. This could lead to the disclosure of sensitive data. All versions in 2.7.x, 2.8.x and 2.9.x branches are believed to be vulnerable.
CVE-2020-1753: 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.

Please fix them.

Created: 2020-02-19 Last update: 2020-10-07 06:00

20 security issues in buster high

There are 20 open security issues in buster.

13 important issues:

CVE-2020-10684: 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: 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-1736: A flaw was found in Ansible Engine when a file is moved using atomic_move primitive as the file mode cannot be specified. This sets the destination files world-readable if the destination file does not exist and if the file exists, the file could be changed to have less restrictive permissions before the move. This could lead to the disclosure of sensitive data. 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-2020-1746: 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: 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.

7 issues skipped by the security teams:

CVE-2019-10156: 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: 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: Ansible, all ansible_engine-2.x versions and ansible_engine-3.x up to ansible_engine-3.5, was 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: 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: 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: 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: 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.

Please fix them.

Created: 2019-06-06 Last update: 2020-10-07 06:00

6 security issues in bullseye high

There are 6 open security issues in bullseye.

6 important issues:

CVE-2020-10744: An incomplete fix was found for the fix of the flaw CVE-2020-1733 ansible: insecure temporary directory when running become_user from become directive. The provided fix is insufficient to prevent the race condition on systems using ACLs and FUSE filesystems. Ansible Engine 2.7.18, 2.8.12, and 2.9.9 as well as previous versions are affected and Ansible Tower 3.4.5, 3.5.6 and 3.6.4 as well as previous versions are affected.
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-1736: A flaw was found in Ansible Engine when a file is moved using atomic_move primitive as the file mode cannot be specified. This sets the destination files world-readable if the destination file does not exist and if the file exists, the file could be changed to have less restrictive permissions before the move. This could lead to the disclosure of sensitive data. All versions in 2.7.x, 2.8.x and 2.9.x branches are believed to be vulnerable.
CVE-2020-1753: 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.

Please fix them.

Created: 2020-02-19 Last update: 2020-10-07 06:00

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: 2020-10-26 07:00

Fails to build during reproducibility 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: 2020-10-26 04:05

11 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 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: 2020-10-21 20:35

lintian reports 7 warnings normal

Lintian reports 7 warnings about this package. You should make the package lintian clean getting rid of them.

Created: 2020-08-22 Last update: 2020-09-21 06:01

news

[rss feed]

[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)
[2019-03-03] ansible 2.7.7+dfsg-1 MIGRATED to testing (Debian testing watch)
[2019-03-02] Accepted ansible 2.7.8+dfsg-1 (source) into unstable (Lee Garrett)
[2019-02-21] Accepted ansible 2.7.7+dfsg-1 (source all) into unstable (Lee Garrett)
[2019-02-19] Accepted ansible 2.2.1.0-2+deb9u1 (source all) into stable->embargoed, stable (Lee Garrett) (signed by: Harlan Lieberman-Berg)
[2019-02-02] ansible 2.7.6+dfsg-1 MIGRATED to testing (Debian testing watch)
[2019-01-27] Accepted ansible 2.7.6+dfsg-1 (source) into unstable (Lee Garrett)
[2019-01-11] Accepted ansible 2.7.5+dfsg-1~bpo9+1 (source all) into stretch-backports, stretch-backports (Harlan Lieberman-Berg)
[2019-01-06] Accepted ansible 2.7.5+dfsg-2 (source) into experimental (Lee Garrett)
[2018-12-27] ansible 2.7.5+dfsg-1 MIGRATED to testing (Debian testing watch)
[2018-12-21] Accepted ansible 2.7.5+dfsg-1 (source all) into unstable, unstable (Lee Garrett) (signed by: Harlan Lieberman-Berg)

bugs [bug history graph]

all: 22
RC: 0
I&N: 19
M&W: 3
F&P: 0
patch: 2

links

homepage
lintian (0, 7)
buildd: logs, clang, reproducibility
popcon
browse source code
edit tags
other distros
security tracker
screenshots

ubuntu

[Information about Ubuntu for Debian Developers]

version: 2.9.9+dfsg-1
7 bugs