hotness tried to map X to an upstream project, but failed: "Could not determine backend for http://url/project/X"

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hello,

I've just received about a dozen of messages like the one mentioned in
the subject, accompanied with:

pkgdb_updater updated: upstream_url of X
        https://admin.fedoraproject.org/pkgdb/package/X/

for a number of gdouros-X-fonts that I updated recently and whose
upstream URL had changed.

I have not added these projects to anitya on purpose, because upstream
regularly restructures their website, the source packages do not
contain any version numbers, sometimes packages get updated silently
and the development takes place offline.
My solution for monitoring what upstream does was a script that runs
daily and checks the md5 hashes of the current upstream sources and
their URLs against those in Fedora. Can anitya work in a similar
fashion?

Do I need to take action about these messages or do I just ignore them?
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux