I found out what is wrong, you created the project without Fedora
mapping, so the first version was retrieved without knowing how this is
packaged in Fedora. But I see, that the mapping was added later, but the
message about the mapping wasn't send by Anitya. Did you added the
mapping using API, maybe the message is not published when the mapping
is changed using API?
I can still see few golang updates coming through recently:
golang-github-hashicorp-mdns - [0]
golang-github-pierrec-lz4 - [1]
Could you check what exactly is missing from the projects you added. You
could check the latest messages from the-new-hotness in [2]
[0] -
https://apps.fedoraproject.org/datagrepper/id?id=2019-79474d61-c5f9-4b07-8663-7ea15f434774&is_raw=true&size=extra-large
[1] -
https://apps.fedoraproject.org/datagrepper/id?id=2019-e171f618-4c2e-4a27-8250-ebe8deec6b26&is_raw=true&size=extra-large
[2] -
https://apps.fedoraproject.org/datagrepper/raw?category=hotness&delta=2592000
On 28/03/19 19:19, Michal Konecny wrote:
Hi,
this is really suspicious, I didn't saw any issue related to
the-new-hotness or Anitya in recent days.
I will check what is going on.
mkonecny
On 28/03/19 19:09, Robert-André Mauchin wrote:
Hello,
Earlier this week, I wrote a script to check and add all Golang
packages to
Anitya. Everything went smoothly, and dozens of packages were
registered and
got their version retrieved.
Since our float of Golang packages is severely out of date, I was
expecting a
load of new messages from Bugzilla. But niet, nada, zilch: no new bug
were
filed as part of this process.
So is Anitya broken again? Is it not supposed to fill bugs for new
versions?
For example, I registered golang-github-montanaflynn-stats:
Latest version upstream is 0.5.0
https://release-monitoring.org/project/19511/
Version in Fedora is 0.2.0
https://src.fedoraproject.org/rpms/golang-github-montanaflynn-stats/
Yet no bug was filled for it.
Any help please?
Robert-André
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
