search

conda-forge / htcondor-feedstock

A conda-smithy repository for htcondor.
BSD 3-Clause "New" or "Revised" License
0 stars 7 forks source link

htcondor v23.5.0 #215

Closed regro-cf-autotick-bot closed 8 months ago

regro-cf-autotick-bot commented 9 months ago

It is very likely that the current package version for this feedstock is out of date.

Checklist before merging this PR:

Information about this PR:

  1. Feel free to push to the bot's branch to update this PR if needed.
  2. The bot will almost always only open one PR per version.
  3. The bot will stop issuing PRs if more than 3 version bump PRs generated by the bot are open. If you don't want to package a particular version please close the PR.
  4. If you want these PRs to be merged automatically, make an issue with code>@conda-forge-admin,</codeplease add bot automerge in the title and merge the resulting PR. This command will add our bot automerge feature to your feedstock.
  5. If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase code>@<space/conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

Closes: #213

Pending Dependency Version Updates

Here is a list of all the pending dependency version updates for this repo. Please double check all dependencies before merging.

Name Upstream Version Current Version
htcondor 23.5.0 Anaconda-Server Badge

Dependency Analysis

Please note that this analysis is highly experimental. The aim here is to make maintenance easier by inspecting the package's dependencies. Importantly this analysis does not support optional dependencies, please double check those before making changes. If you do not want hinting of this kind ever please add bot: inspection: false to your conda-forge.yml. If you encounter issues with this feature please ping the bot team conda-forge/bot.

Analysis by source code inspection shows a discrepancy between it and the the package's stated requirements in the meta.yaml.

Packages found by source code inspection but not in the meta.yaml:

Packages found in the meta.yaml but not found by source code inspection:

This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. Feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/cf-scripts/actions/runs/7969564996, please use this URL for debugging.

conda-forge-webservices[bot] commented 9 months 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.

timtheisen commented 8 months ago

This is not the final release. The final release is due in early March.

duncanmmacleod commented 8 months ago

This is not the final release. The final release is due in early March.

@timtheisen, can you clarify? The fact that this PR exists at all means that there is a tarball in the https://research.cs.wisc.edu/htcondor/tarball/current/23.5.0/release/ directory. If this isn't the 'final' release, why does it looks so very much like one?

timtheisen commented 8 months ago

Due to the way that CHTC and OSG repositories interact and the visibility of the version number from the outside of the tarball, the update repository is being used for beta release candidates. (These have been running for a week in production in CHTC.) I hadn't thought about how condaforge picks up the release from tarballs (not git tags). 23.5.0 is essentially a beta release candidate. I probably aught to rework my release script. 23.5.1 will be final release. Condor picks up tarballs that match their version number. I'll update the release script to put this into the rc sub-directory. My apologies for the confusion.

timtheisen commented 8 months ago

I updated my release script to avoid this confusion.

regro-cf-autotick-bot commented 8 months ago

I see that this PR has conflicts, and I'm the only committer. I'm going to close this PR and will make another one as appropriate. This was generated by https://github.com/regro/cf-scripts/actions/runs/7992735914