Just saw this go by in the update tracker:
Index: /trunk/dports/sysutils/ansible/Portfile
> ===================================================================
> --- /trunk/dports/sysutils/ansible/Portfile (revision 139408)
> +++ /trunk/dports/sysutils/ansible/Portfile (revision 139409)
> @@ -7,9 +7,8 @@
>
> name ansible
> -version 1.9.2
> -epoch 1
> +version 1.9.2-1
> categories sysutils
>
> -github.setup ${name} ${name} v${version}-${epoch}
> +github.setup ${name} ${name} v${version}
> fetch.type git
>
> Removing the epoch sets it to 0; since it looks like the epoch was already
1 before r139408 and there may be existing installations with that epoch,
those installations will never update in the future.
The epoch must *never* go backwards.
I would suggest restoring the epoch to 1 and leaving it alone from now on
unless there is some specific need to force installation of an older
version.
https://guide.macports.org/#reference.keywords see under "epoch".
--
brandon s allbery kf8nh sine nomine associates
[email protected] [email protected]
unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
_______________________________________________
macports-dev mailing list
[email protected]
https://lists.macosforge.org/mailman/listinfo/macports-dev
