search

conda-forge / pyscaffold-feedstock

A conda-smithy repository for pyscaffold.
BSD 3-Clause "New" or "Revised" License
3 stars 11 forks source link

Attempt to publish v4.0.1rc2 again #39

Closed abravalheri closed 3 years ago

abravalheri commented 3 years ago

Checklist

As reported in #38, after the previous PR was merged, the packaged did not end up published in Anaconda.

This empty PR is an another attempt...

No files were changed.

conda-forge-linter commented 3 years ago

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

abravalheri commented 3 years ago

@conda-forge-admin please rerender

github-actions[bot] commented 3 years ago

Hi! This is the friendly automated conda-forge-webservice. I tried to rerender for you, but it looks like there was nothing to do.

maresb commented 3 years ago

I just had an idea. Maybe something is messed up with the build numbers (perhaps due to Chris relabeling rc1 from main to pyscaffold_rc). If the bot mistakenly thinks that the rc1 and the rc2 are the same, and both have build number 0, it may therefore think that it's not supposed to build the package.

Let's try bumping the build number.

abravalheri commented 3 years ago

Sorry @maresb, I just clicked the merge button a few seconds before receiving your message 😅

It seems that some sort of CI is running right now on the merge commit on the RC branch, which I didn't see happening last time. 🤞

If it does not work, I will try your suggestion.

abravalheri commented 3 years ago

Looks like it worked: https://anaconda.org/conda-forge/pyscaffold/files

😅

maresb commented 3 years ago

I hit submit the same instant you closed the PR. :laughing:

I thought of bumping the build number while writing a call for help to Filipe and Chris... If my suggestion doesn't work, I'll repost the following summary and @-tag them in it.

We are trying to publish a release candidate, rc2. We followed the knowledge base instructions, but nothing is showing up on anaconda.org. Anderson asked for help on Gitter but unfortunately received no response. More info about our previous attempt can be found in #38.

The rc1 on anaconda.org was relabeled by Chris after I mistakenly published it with the main label, so we have not yet successfully built a package from this rc branch.

If you could find the time to take a look, we would really appreciate it!

maresb commented 3 years ago

We are really great with synchronized posting!!! :laughing:

Wow!!! I don't understand why it succeeded though. It seems like it needed the rerender to take place, even if rerendering was a do-nothing operation?

abravalheri commented 3 years ago

Thank you very much for all the help @maresb.

I think no software resists to the good'old "have you tried to turn it off and on again?"...

My guess was that the CI process for the previous merge was never triggered... who knows why? (We can see in fact scrolling Github's commit history that there is no CI icon associated with the previous merge commit). Maybe the CI was too busy, maybe it was due to the fact the rc branch did not have me listed as maintainer in the meta.yaml yet (the rebase with master was applied in the same PR) so it got confused... Hard to tell

maresb commented 3 years ago

In any case, excellent work @abravalheri! That was really tricky, and I'm glad you finally got it working.