You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The best option for now is to create multiple projects in Anitya for different versions and map them accordingly. And just create a correct version filter for each of them.
We should probably solve this in the-new-hotness which is filling the bugs, but I'm not sure how to correctly map the version to package. I see two option either one package in one distro per one project or fill the bug to each package that is mapped to particular project.
So I have a strange request, for Go packages in Fedora, we package import path, for examples:
github.com/lestrrat-go/backoff/v1
github.com/lestrrat-go/backoff/v2
github.com/lestrrat-go/backoff/v3
For each import path we have a separate package:
golang-github-lestrrat-backoff-1
golang-github-lestrrat-backoff-2
golang-github-lestrrat-backoff-3
The issue is when we put this into Anitya, we get bug filed for version 3.x.x on the v1 package.
So I'd like a way for Anitya to only check for update with the major version 1, the major version 2 and so on.
So far, I have achieved that by putting:
Version filter: v2;v3:v4
to exclude these version in the v1 package.
But this is not future proof because, v5, v6 could appear in the future.
Thanks.
The text was updated successfully, but these errors were encountered: