Date: Tue, 14 Dec 2021 13:08:03 +0000 From: bugzilla-noreply@freebsd.org To: ruby@FreeBSD.org Subject: [Bug 260019] net/foreman-proxy: update to 3.0.1 Message-ID: <bug-260019-21402-Jx2TS3o7zM@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-260019-21402@https.bugs.freebsd.org/bugzilla/> References: <bug-260019-21402@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D260019 --- Comment #3 from Frank Wall <fw@moov.de> --- (In reply to Jason Unovitch from comment #2) > but we don't need to pull in systemd for this I'm not biased towards any solution to this problem, I'm fine with whatever= a plugin committer is willing to approve. But one could argue that the systemd code is no-op, because it will just do nothing on FreeBSD. And going forwar= d it will be much easier to update the port if we don't modify the source code to remove systemd-related stuff. > why do we need to patch lib/proxy/http_download.rb to include a "verify_s= erver_cert =3D false" line? I think you're reading the patch incorrectly. :) It's a patch for the patch. This line is the new content of the original lib/proxy/http_download.rb fil= e. We only change the wget path, everything else is unmodified. But the patch-patch shows a modification, because the original file got modified upstream. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-260019-21402-Jx2TS3o7zM>