Date: Fri, 11 Aug 2017 17:01:43 +0900 (JST) From: Yasuhiro KIMURA <yasu@utahime.org> To: adamw@adamw.org Cc: freebsd-ports@freebsd.org, portmgr@FreeBSD.org Subject: Re: Official opinion about new py3- port Message-ID: <20170811.170143.574065409084065703.yasu@utahime.org> In-Reply-To: <29D51ECB-4248-4D8E-BE3C-85944AD36D3E@adamw.org> References: <20170810.060816.949087463497216767.yasu@utahime.org> <29D51ECB-4248-4D8E-BE3C-85944AD36D3E@adamw.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Adam. Thank you for your quick response, and sorry for my late reply. From: Adam Weinberger <adamw@adamw.org> Subject: Re: Official opinion about new py3- port Date: Wed, 9 Aug 2017 15:33:42 -0600 > An exception does exist for when a py3 port is a required > dependency, which it sounds like is the case here. Can you confirm > that the current ports postfix-policyd-spf-python (1.3.2) fails on > python 3.6? Do you mean the issue reported by following PR? https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220470 If so, I couldn't reproduce it with my mail server. I submitted PR to update mail/postfix-policyd-spf-python simply because I found newer version is released. --- Yasuhiro KIMURA
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170811.170143.574065409084065703.yasu>