On czw, 2017-06-15 at 09:49 -0700, Zac Medico wrote:
> On Thu, Jun 15, 2017 at 12:42 AM, Michał Górny wrote:
> >
> > Following the plan established in GLEP 59, we're long overdue
> > deprecating SHA256. Since we have finally got rid of the last packages
> > lacking SHA512
On czw, 2017-06-15 at 09:08 -0700, Zac Medico wrote:
> On Thu, Jun 15, 2017 at 12:27 AM, Michał Górny wrote:
>
> > The MANIFEST1_REQUIRED_HASH constant is not used anywhere, so it should
> > be possible to remove it safely.
> > ---
> > pym/portage/const.py | 1 -
> > 1 file
On Thu, Jun 15, 2017 at 12:42 AM, Michał Górny wrote:
>
> Following the plan established in GLEP 59, we're long overdue
> deprecating SHA256. Since we have finally got rid of the last packages
> lacking SHA512 checksums, we can proceed with that. In order to prepare
> for it,
On Thu, Jun 15, 2017 at 12:27 AM, Michał Górny wrote:
> The MANIFEST1_REQUIRED_HASH constant is not used anywhere, so it should
> be possible to remove it safely.
> ---
> pym/portage/const.py | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/pym/portage/const.py
Following the plan established in GLEP 59, we're long overdue
deprecating SHA256. Since we have finally got rid of the last packages
lacking SHA512 checksums, we can proceed with that. In order to prepare
for it, however, we need to change the required hash to SHA512 and make
sure developers
The MANIFEST1_REQUIRED_HASH constant is not used anywhere, so it should
be possible to remove it safely.
---
pym/portage/const.py | 1 -
1 file changed, 1 deletion(-)
diff --git a/pym/portage/const.py b/pym/portage/const.py
index 7e415ba9c..052d4ca2f 100644
--- a/pym/portage/const.py
+++