non port: sysutils/ansible1/Makefile |
Number of commits found: 22 |
Saturday, 6 Jul 2019
|
23:04 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
|
Monday, 5 Nov 2018
|
02:07 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)
|
Monday, 15 Oct 2018
|
00:58 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.
|
Tuesday, 24 Jul 2018
|
03:16 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
|
Sunday, 1 Jul 2018
|
23:27 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
|
Friday, 18 May 2018
|
13:45 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
|
Monday, 26 Mar 2018
|
15:17 lifanov
sysutils/ansible* - prepare for sysutils/ansible update
o Remove vanity "Created by:" line
o Add upcoming ansible24 port to CONFLICTS
|
Monday, 19 Feb 2018
|
11:10 antoine
Reduce dependency on the python2 metaport
PR: 225752
Submitted by: Yasuhiro KIMURA
|
Thursday, 30 Nov 2017
|
21:34 lifanov
reinstate sysutils/ansible23
PKGBASE collision has been resolved
This reverts r455222
|
20:08 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
|
15:50 mat
Convert Python ports to FLAVORS.
Ports using USE_PYTHON=distutils are now flavored. They will
automatically get flavors (py27, py34, py35, py36) depending on what
versions they support.
There is also a USE_PYTHON=flavors for ports that do not use distutils
but need FLAVORS to be set. A USE_PYTHON=noflavors can be set if
using distutils but flavors are not wanted.
A new USE_PYTHON=optsuffix that will add PYTHON_PKGNAMESUFFIX has been
added to cope with Python ports that did not have the Python
PKGNAMEPREFIX but are flavored.
USES=python now also exports a PY_FLAVOR variable that contains the
current python flavor. It can be used in dependency lines when the
port itself is not python flavored. For example, deskutils/calibre.
By default, all the flavors are generated. To only generate flavors
for the versions in PYTHON2_DEFAULT and PYTHON3_DEFAULT, define
BUILD_DEFAULT_PYTHON_FLAVORS in your make.conf.
In all the ports with Python dependencies, the *_DEPENDS entries MUST
end with the flavor so that the framework knows which to build/use.
This is done by appending '@${PY_FLAVOR}' after the origin (or
@${FLAVOR} if in a Python module with Python flavors, as the content
will be the same). For example:
RUN_DEPENDS= ${PYTHON_PKGNAMEPREFIX}six>0:devel/py-six@${PY_FLAVOR}
PR: 223071
Reviewed by: portmgr, python
Sponsored by: Absolight
Differential Revision: https://reviews.freebsd.org/D12464
|
15:35 lifanov
update conflicts after addition of sysutils/ansible23
|
Monday, 17 Jul 2017
|
06:27 koobs
sysutils/ansible1: Switch to paramiko (2.x)
Follow up of ports r445996. This was missed due to seperate original commits
[1][2] with no PR: references and insufficient QA on my part which would have
picked it up.
This fixes the second packaging error after ports r445866 due to conflicting
paramiko1/paramiko ports, because of:
- sysutils/py-ploy_fabric -> sysutils/py_ploy -> security/paramiko
- sysutils/py-ploy_fabric -> devel/py-fabric -> security/paramiko1 (r445866)
- sysutils/bsdploy -> sysutils/ansible1 -> security/py-paramiko1 (this fix)
[1] https://svnweb.freebsd.org/changeset/ports/425687
[2] https://svnweb.freebsd.org/changeset/ports/425989
PR: 214379
|
Thursday, 13 Apr 2017
|
03:55 lifanov
sysutils/ansible1: fix packaging
Also, bump expiration date again since I touched it.
I plan to keep it around until sysutils/py-ploy_ansible is migrated.
|
Saturday, 12 Nov 2016
|
20:11 lwhsu
Change RUN_DEPENDS back to py-paramiko 1.x, for making ports depends on it
build without conflict
|
Tuesday, 1 Nov 2016
|
17:51 matthew
Declare this slave port only uses python:2 now that the master port
can use python-3. No change to generated package, so no portrevision
bump.
|
Monday, 18 Apr 2016
|
15:21 matthew
Update to 1.9.6
- extend expiry date another month
PR: 208896
Submitted by: maintainer (lifanov@mail.lifanov.com)
|
Tuesday, 22 Mar 2016
|
14:40 matthew
Update to 1.9.5
- extend deprecation period by 3 months. The plan is to expire the
port about 6 months after the last upstream release.
ChangeLog:
https://raw.githubusercontent.com/ansible/ansible/v1.9.5-1/CHANGELOG.md
PR: 208200
Submitted by: maintainer (lifanov@mail.lifanov.com)
|
Thursday, 25 Feb 2016
|
23:09 matthew
Deprecate and set expiry for June 1st
Users should migrate to sysutils/ansible, now that ansible 2.x is the
principal release version.
PR: 207491
Submitted by: lifanov@mail.lifanov.com (maintainer)
|
Friday, 22 Jan 2016
|
17:30 matthew
Fix default low-level command submission
-- on FreeBSD root's default shell (/bin/csh) would fail to
understand the /bin/sh syntax ansible issues.
Import the fix from upstream.
PR: 206498
Submitted by: matthew
Approved by: lifanov@mail.lifanov.com (maintainer)
Obtained
from: https://github.com/ansible/ansible/commit/8647fdc7f25ba1c707c5333ca1581a1fa0ffe566
|
Wednesday, 13 Jan 2016
|
07:46 matthew
Ooops. Commit the Makefile, not the patchfile that should create the
Makefile
Pointy hat to me...
|
07:41 matthew
Upgrade ansible to 2.0.0
Provide an ansible1 slave port with ansible-1.9.4 as there are
incompatible changes between ansible-1.9.4 and ansible-2.0.0
Add note in UPDATING
PR: 206174
Submitted by: lifanov@mail.lifanov.com (maintainer)
|
Number of commits found: 22 |