Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No upstream version found doesn't mean there is error in project check #892

Closed
Zlopez opened this issue Feb 24, 2020 · 0 comments · Fixed by #895
Closed

No upstream version found doesn't mean there is error in project check #892

Zlopez opened this issue Feb 24, 2020 · 0 comments · Fixed by #895
Labels
High priority This ticket has a high priority type.feature New feature
Milestone

Comments

@Zlopez
Copy link
Contributor

Zlopez commented Feb 24, 2020

Description

Currently if we don't retrieve any version we raise an exception, but this could be correct if there is no new version (at least for GitHub, which is using cursor now). There should be difference between no new version found and no version found at all (project is incorrectly setup or the upstream doesn't exist).

Requirements

  • If project could be checked, but no version could be retrieved it shouldn't throw any error. (This is currently happening only in GitHub backend)

How this will make Anitya better

It will prevent raising false alarms about no longer updated projects.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
High priority This ticket has a high priority type.feature New feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant