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

[conda-forge-linter]

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

It appears that one or more of your feedstock's outputs 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. 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 or you can bump us right here.

output validation (is this output allowed for your feedstock?):

• noarch/email_validator-1.1.2-hd8ed1ab_1.tar.bz2: False

copied (did this output get copied to the production channel?):

• noarch/email_validator-1.1.2-hd8ed1ab_1.tar.bz2: False

error messages:

• output noarch/email_validator-1.1.2-hd8ed1ab_1.tar.bz2 not allowed for conda-forge/email-validator-feedstock

[xylar]

@ocefpaf, this is the package from the archived feedstock, now being built by this one. Any suggestions on what needs to be done to allow this feedstock to upload packages with that name instead?

[ocefpaf]

Pinging @beckermr here b/c he is the one that implemented these checks.

[beckermr]

See here: https://github.com/conda-forge/feedstock-outputs/blob/master/outputs/e/m/a/email_validator.json

When a member of core archives or moves a feedstock, they need to update the mappings by hand.

[beckermr]

I have fixed this. Try the upload again.

[xylar]

@beckermr, I figured it was something like that. Thanks very much!

[xylar]

That's done the trick! Thanks again!