Skip to content

How to handle already existing wheels for daily dev builds #63

@astrofrog

Description

@astrofrog

Over at Astropy we are building nightly wheels - sometimes there are no changes from one day to the next so the anaconda upload fails with:

Creating release "5.2.dev275+g8ef58665f"
[303](https://github.com/astropy/astropy/runs/7442665386?check_suite_focus=true#step:6:304)
Uploading file "astropy/astropy/5.2.dev275+g8ef58665f/astropy-5.2.dev275+g8ef58665f-cp39-cp39-manylinux_2_12_x86_64.manylinux2010_x86_64.whl"
[304](https://github.com/astropy/astropy/runs/7442665386?check_suite_focus=true#step:6:305)
Distribution already exists. Please use the -i/--interactive or --force or --skip options or `anaconda remove astropy/astropy/5.2.dev275+g8ef58665f/astropy-5.2.dev275+g8ef58665f-cp39-cp39-manylinux_2_12_x86_64.manylinux2010_x86_64.whl

What would be the best approach here?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions