Hello there,
Recently, I've got several such messages for each of new submitted packages. Is there something wrong with the upstream monitoring for Perl modules?
Thanks.
---------- Forwarded message ---------- From: notifications@fedoraproject.org Date: Fri, Feb 27, 2015 at 11:59 PM Subject: hotness tried to map perl-Class-Virtual to an upstream project, but failed due to ambiguity. 5682 other projects share the same homepage
hotness tried to map perl-Class-Virtual to an upstream project, but failed due to ambiguity. 5682 other projects share the same homepage https://bugzilla.redhat.com/1195862
On Sat, Feb 28, 2015 at 05:25:51AM +0600, Denis Fateyev wrote:
Recently, I've got several such messages for each of new submitted packages. Is there something wrong with the upstream monitoring for Perl modules?
---------- Forwarded message ---------- From: notifications@fedoraproject.org Date: Fri, Feb 27, 2015 at 11:59 PM Subject: hotness tried to map perl-Class-Virtual to an upstream project, but failed due to ambiguity. 5682 other projects share the same homepage
hotness tried to map perl-Class-Virtual to an upstream project, but failed due to ambiguity. 5682 other projects share the same homepage https://bugzilla.redhat.com/1195862
Upstream monitoring is performed by https://release-monitoring.org/. Please find contact there and report you issue there. There is nothing Perl packagers can do with it.
-- Petr
perl-devel@lists.fedoraproject.org