| Port details |
- ansible23 Radically simple IT automation
- 2.3.3.0_5 sysutils
 =1      2.3.3.0_5Version of this port present on the latest quarterly branch.  DEPRECATED: Upstream support ended. Consider upgrading to sysutils/ansible
 This port expired on: 2020-05-31
- Maintainer: lifanov@FreeBSD.org
- Port Added: 2017-11-30 15:32:54
- Last Update: 2020-05-31 10:14:50
- SVN Revision: 537145
- People watching this port, also watch:: zrep
- Also Listed In: python
- License: GPLv3+
- WWW:
- https://www.ansible.com/
- Description:
- Ansible is a radically simple configuration-management, deployment,
task-execution, and multinode orchestration framework.
WWW: https://www.ansible.com/
 cgit ¦ GitHub ¦ GitHub ¦ GitLab ¦ 
- Manual pages:
- FreshPorts has no man page information for this port.
- pkg-plist: as obtained via:
make generate-plist - There is no configure plist information for this port.
- Dependency lines:
-
- ${PYTHON_PKGNAMEPREFIX}ansible23>0:sysutils/ansible23@${PY_FLAVOR}
- Conflicts:
- CONFLICTS:
- ansible-*
- ansible1-*
- ansible24-*
- ansible25-*
- ansible26-*
- ansible27-*
- ansible28-*
- No installation instructions:
- This port has been deleted.
- PKGNAME: py37-ansible23
- Package flavors (<flavor>: <package>)
- py37: py37-ansible23
- py27: py27-ansible23
- distinfo:
- TIMESTAMP = 1525366516
SHA256 (ansible-2.3.3.0.tar.gz) = da2a715f6ca14a76001cc0f4bd1e44024328b3c2dad2c946dc9c7ed2d7c30afa
SIZE (ansible-2.3.3.0.tar.gz) = 4190380
No package information for this port in our database- Sometimes this happens. Not all ports have packages. Perhaps there is a build error. Check the fallout link:
- Master port: sysutils/ansible
- Dependencies
- NOTE: FreshPorts displays only information on required and default dependencies. Optional dependencies are not covered.
- Build dependencies:
-
- py37-setuptools>0 : devel/py-setuptools@py37
- python3.7 : lang/python37
- Runtime dependencies:
-
- py37-Jinja2>0 : devel/py-Jinja2@py37
- py37-jmespath>0 : devel/py-jmespath@py37
- py37-netaddr>0 : net/py-netaddr@py37
- py37-paramiko>0 : security/py-paramiko@py37
- py37-pycrypto>0 : security/py-pycrypto@py37
- py37-yaml>0 : devel/py-yaml@py37
- py37-setuptools>0 : devel/py-setuptools@py37
- python3.7 : lang/python37
- There are no ports dependent upon this port
Configuration Options:- ===> The following configuration options are available for py37-ansible23-2.3.3.0_5:
DOCS=on: Build and/or install documentation
EXAMPLES=on: Build and/or install examples
===> Use 'make config' to modify these settings
- Options name:
- N/A
- USES:
- cpe python
- FreshPorts was unable to extract/find any pkg message
- Master Sites:
|
| Commit History - (may be incomplete: for full details, see links to repositories near top of page) |
| This is a slave port. You may also want to view the commits to the master port: sysutils/ansible |
| Commit | Credits | Log message |
|---|
2.3.3.0_5
31 May 2020 10:14:50
  |
rene |
Remove expired ports:
2020-05-31 sysutils/ansible24: Upstream support ended. Consider upgrading to
sysutils/ansible
2020-05-31 sysutils/ansible26: Upstream support ended. Consider upgrading to
sysutils/ansible
2020-05-31 sysutils/ansible25: Upstream support ended. Consider upgrading to
sysutils/ansible
2020-05-31 www/py-requests-futures097: Use www/py-requests-futures instead
2020-05-31 sysutils/ansible23: Upstream support ended. Consider upgrading to
sysutils/ansible
2020-05-31 devel/graphql.el: No longer required by anything |
2.3.3.0_5
28 Apr 2020 20:46:07
|
bofh |
sysutils/ansible: Update version 2.8.11=>2.9.7
- Create sysutils/ansible28 from sysutils/ansible
- Set EXPIRATION_DATE to 20200530 for ansible23 ansible24 ansible25 and
ansible26 as they are no longer maintained by upstream
- Bump ansible23 ansible24 ansible25 ansible26 and ansible27 for CONFLICTS
with ansible28
PR: 241734
Submitted by: ncrogers@gmail.com
Approved by: portmgr (maintainer-timeout) |
2.3.3.0_4
17 Apr 2020 22:31:56
|
bofh |
sysutils/ansible: Multiple Vulnerabilities fix
- Update ansible 2.8.7=>2.8.11
- Update ansible27 2.7.15=>2.7.17
- For ansible27 add fixes [1]
- Rudimentary detection of the virtual platforms
- playbook hangs without ASSUME_ALWAYS_YES for pkgng
- Fix zpool snapshot cloning
- Fix `doas` password authentication
- Mark ansible26, ansible25, ansible24 and ansible23 DEPRECATED without
EXPIRATION_DATE for MFH
PR: 241734 233970 [1]
Submitted by: timur [1]
Reported by: ncrogers@gmail.com
Approved by: portmgr (maintainer timeout, > 14 days)
MFH: 2020Q2 (bugfix release)
Security: CVE-2020-1737
Security: CVE-2020-1739
Security: CVE-2020-1740 |
2.3.3.0_4
06 Jul 2019 23:04:15
|
lifanov |
update sysutils/ansible to 2.8.2
This creates sysutils/ansible27 port for users that wish to stay on
Ansible 2.7 stable branch.
https://github.com/ansible/ansible/blob/v2.8.2/changelogs/CHANGELOG-v2.8.rst |
2.3.3.0_4
10 Apr 2019 06:18:32
|
antoine |
Bump a few PORTREVISIONs after r498529
With hat: portmgr |
2.3.3.0_3
11 Mar 2019 01:05:24
|
lifanov |
ansible: switch to security/py-cryptography
For ansible >= 2.4, py-cryptography is preferred upstream.
PR: 236436
Reported by: John W. O'Brien <john@saltant.com> |
2.3.3.0_3
05 Nov 2018 02:07:10
|
lifanov |
update sysutils/ansible* ports
sysutils/ansible: 2.7.1
Changes:
https://github.com/ansible/ansible/blob/v2.7.1/changelogs/CHANGELOG-v2.7.rst
sysutils/ansible26: 2.6.7
Changes:
https://github.com/ansible/ansible/blob/v2.6.7/changelogs/CHANGELOG-v2.6.rst
sysutils/ansible25: 2.5.11
Changes:
https://github.com/ansible/ansible/blob/v2.5.11/changelogs/CHANGELOG-v2.5.rst
All ports: move default configuration directory back to LOCALBASE/etc/ansible as
before the flavors conversion. Configuration is version-specific and not
Python-specific
and this is a more intuitive location.
PR: 232377
Reported by: Tomoyuki Sakurai (default configuration path) |
2.3.3.0_2
15 Oct 2018 00:58:10
|
lifanov |
update sysutils/ansible to 2.7.0
This is a major release. Please see changelog and migration guide:
https://github.com/ansible/ansible/blob/2.7/changelogs/CHANGELOG-v2.7.rst
https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_2.7.html
This also introduces sysutils/ansible26, which will track the 2.6 stable
branch. |
2.3.3.0_2
24 Jul 2018 03:16:32
|
lifanov |
fix symlinks for ansible when non-default version is installed
The issue is that before stage, other binaries are links to ansible:
bin/ansible-vault -> bin/ansible
bin/ansible-playbook -> bin/ansible
During stage, these get renamed with a suffix, like 3.6, but the
target of the symlink doesn't change:
bin/ansible-vault-3.6 -> bin/ansible
bin/ansible-playbook-3.6 -> bin/ansible
This either creates broken links if the package for the default
Python version is not installed or it creates links to the
wrong binary if it is.
Thank you Andreas Sommer for the fix!
PR: 229960
Submitted by: Andreas Sommer |
2.3.3.0_1
01 Jul 2018 23:27:23
|
lifanov |
update sysutils/ansible to 2.6.0
This also introduces sysutils/ansible25 port to track 2.5 release branch.
Changes:
https://github.com/ansible/ansible/blob/v2.6.0/changelogs/CHANGELOG-v2.6.rst |
2.3.3.0_1
18 May 2018 13:45:40
|
lifanov |
add tests and FLAVORS to Ansible ports
Most of the work was done by koobs. Thank you!
PR: 228268
Submitted by: koobs
Reported by: Christopher Hall |
2.3.3.0
03 May 2018 16:57:09
|
lifanov |
update sysutils/ansible23 to 2.3.3.0
This is a bugfix release.
Changes: https://github.com/ansible/ansible/blob/v2.3.3.0-1/CHANGELOG.md |
2.3.2.0
26 Mar 2018 15:17:21
|
lifanov |
sysutils/ansible* - prepare for sysutils/ansible update
o Remove vanity "Created by:" line
o Add upcoming ansible24 port to CONFLICTS |
2.3.2.0
30 Nov 2017 21:34:42
 |
lifanov |
reinstate sysutils/ansible23
PKGBASE collision has been resolved
This reverts r455222 |
2.3.2.0
30 Nov 2017 20:08:55
|
antoine |
Remove sysutils/ansible23, it clashes with python flavor work
Do not add back without checking PKGBASE uniqueness for all flavors first
With hat: portmgr |
2.3.2.0
30 Nov 2017 15:32:44
|
lifanov |
add sysutils/ansible23
This is the latest version of Ansible from stable-2.3 branch,
currently receiving bug and security fixes.
Requested by: Rainer (private email) |
As an Amazon Associate I earn from qualifying purchases.