Date: Sat, 31 Dec 2022 12:24:15 -0800
From: Craig Leres <leres@freebsd.org>
To: Nuno Teixeira <eduardo@freebsd.org>
Cc: ports-committers@freebsd.org, dev-commits-ports-all@freebsd.org, dev-commits-ports-main@freebsd.org
Subject: Re: git: d840b65db3de - main - security/py-pycryptodome{,x}: Update to 3.16.0
Message-ID: <fc34f25e-7862-9363-62b8-2aec982175b0@freebsd.org>
In-Reply-To: <CAFDf7U%2BabuSsGr17ErmRNDFSJ4r0p7C=Dt0iNBf9Ogh-0=DYxw@mail.gmail.com>
References: <202212241005.2BOA5RVP012313@gitrepo.freebsd.org> <ae74f5a3-e211-f2df-194f-bfc99c22051f@freebsd.org> <CAFDf7U%2BabuSsGr17ErmRNDFSJ4r0p7C=Dt0iNBf9Ogh-0=DYxw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/31/22 11:36, Nuno Teixeira wrote:
> security/py-pycrypto is deprecated:
> DEPRECATED= Unmaintained, obsolete, and contains security
> vulnerabilities. Use security/py-pycryptodome instead
> EXPIRATION_DATE=2022-06-30
>
> The problem is that security/py-keyrings.alt depends on:
> ENCRYPTED_FILE_RUN_DEPENDS=
> ${PYTHON_PKGNAMEPREFIX}pycrypto>=2.5:security/py-pycrypto@${PY_FLAVOR}
>
> All ports depending on security/py-pycrypto must be changed to
> security/py-pycryptodome
>
> d840b65 was a simple update and it doesn't cause this problem.
My bad -- I didn't find the email/commit message that removed the port
because pycrypto didn't appear in the subject...
Craig
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?fc34f25e-7862-9363-62b8-2aec982175b0>