Date: Mon, 10 Dec 2018 20:46:57 +0000 From: Carmel NY <carmel_ny@outlook.com> To: FreeBSD <freebsd-questions@freebsd.org> Subject: Re: certbot lost certificates , and registration data Message-ID: <SN1PR20MB21092707E655743586B653DB80A50@SN1PR20MB2109.namprd20.prod.outlook.com> In-Reply-To: <5314f953-78f4-234a-0a66-5874f9d4fe41@FreeBSD.org> References: <4290f82e-ce3a-0ce3-aab7-df21a9c636e6@ifdnrg.com> <fb8d0574-dcae-a7f9-d417-5b3af57a5284@ifdnrg.com> <80637ff8-1c6a-d23b-6bda-bc8b48b5c51b@ifdnrg.com> <CAHu1Y73NDZk%2BQ2C5GVAGwB48_pGVFFmA4yqUK-xtB_2p4brvrA@mail.gmail.com> <5314f953-78f4-234a-0a66-5874f9d4fe41@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 10 Dec 2018 17:56:22 +0000, Matthew Seaman stated: >This was due to an upstream change moving where various paths are=20 >defined to a different file, and so making the port's attempt to modify=20 >the settings in the original file pretty futile. I'll be working on a=20 >fix later tonight. I am not sure if all of the py*-certbots are maintained by the same person; but shouldn't they have caught this problem before releasing it? They must have tested it, right? --=20 Carmel
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?SN1PR20MB21092707E655743586B653DB80A50>