net/foreman-proxy: update 3.0.1 -> 3.1.2
Maintainer informed via mail
Created attachment 233350 [details] net/foreman-proxy: update 3.0.1 -> 3.1.2
Hi Frank. Patch attached for the 3.0.x to 3.1.x update. The most significant change seemed to be https://github.com/theforeman/smart-proxy/commit/3d87c6feaa8caaf9b8c040f96061c3b8c33a39ef with the switch from wget to curl for downloads that landed before the 3.1 release candidates. This looked to be a low threat update otherwise.
Thanks. This is "Approved by: maintainer" now and ready for an active committer to apply. I do not have a current ports commit bit.
^Triage: Simplifying title ^Triage: If there is a changelog or release notes URL available for this version, please add it to the URL field. Can some (all) of the patches be adapted to our preferred format? /data/fernape_data/FreeBSD-repos/ports/net/foreman-proxy/files/patch-config-settings.d-puppet_proxy_puppet_api.yml.example: patch was not generated using ``make makepatch''. It is recommended to use ``make makepatch'' when you need to [re-]generate a patch to ensure proper patch format. /data/fernape_data/FreeBSD-repos/ports/net/foreman-proxy/files/patch-config-settings.d-puppetca_hostname_whitelisting.yml.example: patch was not generated using ``make makepatch''. It is recommended to use ``make makepatch'' when you need to [re-]generate a patch to ensure proper patch format. /data/fernape_data/FreeBSD-repos/ports/net/foreman-proxy/files/patch-config-settings.d-puppetca_http_api.yml.example: patch was not generated using ``make makepatch''. It is recommended to use ``make makepatch'' when you need to [re-]generate a patch to ensure proper patch format. /data/fernape_data/FreeBSD-repos/ports/net/foreman-proxy/files/patch-config-settings.d-realm_freeipa.yml.example: patch was not generated using ``make makepatch''. It is recommended to use ``make makepatch'' when you need to [re-]generate a patch to ensure proper patch format. /data/fernape_data/FreeBSD-repos/ports/net/foreman-proxy/files/patch-config-settings.d-tftp.yml.example: patch was not generated using ``make makepatch''. It is recommended to use ``make makepatch'' when you need to [re-]generate a patch to ensure proper patch format. /data/fernape_data/FreeBSD-repos/ports/net/foreman-proxy/files/patch-config-settings.yml.example: patch was not generated using ``make makepatch''. It is recommended to use ``make makepatch'' when you need to [re-]generate a patch to ensure proper patch format. Thanks!
Committed!
A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/ports/commit/?id=ff4d0ccb61b80dd846ba697f6cd30ecbfc167c4e commit ff4d0ccb61b80dd846ba697f6cd30ecbfc167c4e Author: Jason Unovitch <junovitch@FreeBSD.org> AuthorDate: 2022-03-05 02:44:40 +0000 Commit: Neel Chauhan <nc@FreeBSD.org> CommitDate: 2022-04-23 19:39:03 +0000 net/foreman-proxy: update 3.0.1 -> 3.1.2 Changes: https://github.com/theforeman/smart-proxy/compare/3.0.1...3.1.2 PR: 263431 net/foreman-proxy/Makefile | 4 ++-- net/foreman-proxy/distinfo | 6 +++--- .../files/patch-lib_proxy_http__download.rb | 20 ++++++++++---------- 3 files changed, 15 insertions(+), 15 deletions(-)