conda-forge / conda-forge/awscli-feedstock

[warning] failed package validation and/or copy for commit 487e7b3c9dde45b18a4a56981c27f9cf41803c65

Open
#765 221 comments 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
3
Forks
13
Avg merge
4h 16m
Merged PRs (30d)
2

Description

Hi @conda-forge/awscli! This is the friendly automated conda-forge-webservice!

It appears that one or more of your feedstock's outputs is either invalid or
did not copy from the staging channel (cf-staging) to the production channel (conda-forge). :(

This failure can happen for a lot of reasons, including an outdated feedstock
token, a feedstock output that is not allowed for that feedstock, or a feedstock output
with files that are not allowed for that output. Below we have put some information
about the failure to help you debug it.

**Rerendering the feedstock will usually fix these problems.**

If you have any issues or questions, you can find us on gitter in the
community [chat room](https://gitter.im/conda-forge/conda-forge.github.io) or you can bump us right here.

error messages:
- invalid md5 sum for artifact https://conda.anaconda.org/cf-staging/osx-64/awscli-1.19.32-py38h50d1736_0.tar.bz2

Contributor guide

Open the contributing guide

Research direction

Start by rerendering the awscli feedstock, as suggested in the issue, then inspect the reported cf-staging artifact and the package validation or copy result. The work is done when awscli-1.19.32-py38h50d1736_0.tar.bz2 has a valid MD5 sum and successfully copies to the production channel.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
build-system, cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.