From owner-freebsd-questions@freebsd.org Sun Jun 10 08:41:22 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D2E29100663F; Sun, 10 Jun 2018 08:41:22 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from gate.utahime.jp (ipq210.utahime.jp [183.180.29.210]) by mx1.freebsd.org (Postfix) with ESMTP id 53AFB75C58; Sun, 10 Jun 2018 08:41:21 +0000 (UTC) (envelope-from yasu@utahime.org) Received: from eastasia.home.utahime.org (eastasia.home.utahime.org [192.168.174.1]) by gate.utahime.jp (Postfix) with ESMTP id AE9AF20219; Sun, 10 Jun 2018 17:41:17 +0900 (JST) Received: from eastasia.home.utahime.org (localhost [127.0.0.1]) by localhost-backdoor.home.utahime.org (Postfix) with ESMTP id 36CB62F1A4; Sun, 10 Jun 2018 17:41:17 +0900 (JST) Received: from localhost (rolling.home.utahime.org [192.168.174.11]) by eastasia.home.utahime.org (Postfix) with ESMTPSA id EAEC32F1A3; Sun, 10 Jun 2018 17:41:16 +0900 (JST) Date: Sun, 10 Jun 2018 17:41:04 +0900 (JST) Message-Id: <20180610.174104.2014388496802246907.yasu@utahime.org> To: freebsd-questions@freebsd.org, carmel_ny@outlook.com Cc: python@FreeBSD.org Subject: Re: py27-certbot fails to run From: Yasuhiro KIMURA In-Reply-To: References: X-Mailer: Mew version 6.8 on Emacs 26.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Jun 2018 08:41:23 -0000 From: Carmel NY Subject: py27-certbot fails to run Date: Sun, 10 Jun 2018 08:31:54 +0000 > Yesterday I updated the security/py27-certbot port to version 0.25.0,1 > without incident. When running the application via port last night, it > produced this error output: > (snip) > > Is this something local to my machine only or should I file a PR against it > and what can I do to alleviate the problem? Please update your ports tree. It was fixed with r472093. --- Yasuhiro KIMURA