propose-update does not show useful error message if upstream release tarball is missing

packit propose-update seems to use release-monitoring.org to get information about Fedora packages. This doesn’t seem to work:

$ git clone -b packit https://github.com/martinpitt/cockpit-podman
$ cd cockpit-podman
$ packit propose-update 
INFO: Running 'anitya' versioneer
ERROR: Failed to determine latest upstream version!
Check that the package exists on https://release-monitoring.org.
Version in upstream registries is None.
ERROR    
Unexpected exception occurred,

And indeed:

$ curl https://release-monitoring.org/api/project/Fedora/cockpit-podman
{"error":"No package \"cockpit-podman\" found in distro \"Fedora\"","output":"notok"}

However, this doesn’t seem to work for other projects which have been around for much longer:

$ curl https://release-monitoring.org/api/project/Fedora/cockpit-ostree
{"error":"No package \"cockpit-ostree\" found in distro \"Fedora\"","output":"notok"}

It does work for cockpit itself:

$ curl https://release-monitoring.org/api/project/Fedora/cockpit
{"backend":"GitHub","created_on":1452877098.0,"ecosystem":"https://github.com/cockpit-project/cockpit","homepage":"https://github.com/cockpit-project/cockpit","id":8849,"name":"cockpit","packages":[{"distro":"Fedora","package_name":"cockpit"}],"regex":"","updated_on":1556615345.0,"version":"192","version_url":"cockpit-project/cockpit","versions":["192","191","190","189","188","187","186","185","184.1","184","183","182","181","180","179","178","177","176","175","174","173.2","173.1","173","172","171","170","169","168","167","166","165","164","163","162","161","160","159","158","157","156","155","154","153","152","151","150","149","148","147","146","145","144","143","142","141","140","139","138","137","136","135","134","133","132","131","130","129","128","127","126","125","124","123","122","121","120","119","118","1.2.0","1.1.0","1.0.0","0.117","0.116","0.115","0.114","0.113","0.112","0.111","0.110","0.109","0.108","0.107","0.106","0.105","0.104","0.103","0.102","0.101","0.100","0.99","0.98","0.97","0.96-1","0.95","0.94","0.93","0.92","0.91","0.0.1"]}

Wouldn’t it make more sense to query the Fedora dist-git URL directly, instead of relying on a third-party service?

packit-0.2.0-1.fc31.noarch

[martinpitt]

In case this “unexpected exception” refers to having no privileges to push to the Fedora dist-git: I deliverately haven’t kinit’ed, as I want to see what it’s doing before doing an actual package update. Also, 1.1 is just a test release from my own branch, not the official upstream one.

Perhaps at least during this early stage, packit should just print uncaught Python exceptions instead of hiding them?

[TomasTomecek]

This should be now live in packit 0.5.0, feel free to reopen or create new issues if you have more suggestions in mind, thank you!