{"action":"created","issue":{"url":"https://api.github.com/repos/fedora-infra/anitya/issues/279","repository_url":"https://api.github.com/repos/fedora-infra/anitya","labels_url":"https://api.github.com/repos/fedora-infra/anitya/issues/279/labels{/name}","comments_url":"https://api.github.com/repos/fedora-infra/anitya/issues/279/comments","events_url":"https://api.github.com/repos/fedora-infra/anitya/issues/279/events","html_url":"https://github.com/fedora-infra/anitya/issues/279","id":147385515,"number":279,"title":"admin+fdummy mapped the name of \"cucumber-rails\" in Fedora to \"rubygem-cucumber-core\"","user":{"login":"voxik","id":14406,"avatar_url":"https://avatars.githubusercontent.com/u/14406?v=3","gravatar_id":"","url":"https://api.github.com/users/voxik","html_url":"https://github.com/voxik","followers_url":"https://api.github.com/users/voxik/followers","following_url":"https://api.github.com/users/voxik/following{/other_user}","gists_url":"https://api.github.com/users/voxik/gists{/gist_id}","starred_url":"https://api.github.com/users/voxik/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/voxik/subscriptions","organizations_url":"https://api.github.com/users/voxik/orgs","repos_url":"https://api.github.com/users/voxik/repos","events_url":"https://api.github.com/users/voxik/events{/privacy}","received_events_url":"https://api.github.com/users/voxik/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2016-04-11T10:35:22Z","updated_at":"2016-04-11T17:21:24Z","closed_at":null,"body":"Not sure how this happened, but it seems that upstream monitoring screwed up for rubygem-cucumber-core, which is freshly imported into Fedora. I got these notifications from FMN:\r\n\r\n```\r\nSubject: pkgdb_updater updated: description, upstream_url of rubygem-cucumber-core\r\n\r\npkgdb_updater updated: description, upstream_url of rubygem-cucumber-core\r\n\thttps://admin.fedoraproject.org/pkgdb/package/rubygem-cucumber-core/\r\n```\r\n\r\n```\r\nSubject: admin+fdummy mapped the name of \"cucumber-rails\" in Fedora to \"rubygem-cucumber-core\"\r\n\r\nadmin+fdummy mapped the name of \"cucumber-rails\" in Fedora to \"rubygem-cucumber-core\"\r\n\thttps://release-monitoring.org/project/4317/\r\n```\r\n\r\n```\r\nSubject: hotness tried to map rubygem-cucumber-core to an upstream project, but failed:  \"None\"\r\n\r\nhotness tried to map rubygem-cucumber-core to an upstream project, but failed:  \"None\"\r\n\thttps://release-monitoring.org/project/4317/\r\n```\r\n\r\nBut if you check the 4317 project, it is actually project for \"cucumber-rails\".\r\n\r\nPlease note that I'm going to clean this mess up manually."},"comment":{"url":"https://api.github.com/repos/fedora-infra/anitya/issues/comments/208457036","html_url":"https://github.com/fedora-infra/anitya/issues/279#issuecomment-208457036","issue_url":"https://api.github.com/repos/fedora-infra/anitya/issues/279","id":208457036,"user":{"login":"pypingou","id":1240038,"avatar_url":"https://avatars.githubusercontent.com/u/1240038?v=3","gravatar_id":"","url":"https://api.github.com/users/pypingou","html_url":"https://github.com/pypingou","followers_url":"https://api.github.com/users/pypingou/followers","following_url":"https://api.github.com/users/pypingou/following{/other_user}","gists_url":"https://api.github.com/users/pypingou/gists{/gist_id}","starred_url":"https://api.github.com/users/pypingou/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pypingou/subscriptions","organizations_url":"https://api.github.com/users/pypingou/orgs","repos_url":"https://api.github.com/users/pypingou/repos","events_url":"https://api.github.com/users/pypingou/events{/privacy}","received_events_url":"https://api.github.com/users/pypingou/received_events","type":"User","site_admin":false},"created_at":"2016-04-11T17:21:24Z","updated_at":"2016-04-11T17:21:24Z","body":"> Might not be related, but this probably triggered the another action, since newhotness realized that there is no upstream monitoring setup yet ...\r\n\r\nNo I don't think both events were related.\r\n\r\n\r\nAs for the origin, looking at both projects they seem to be using the same homepage:\r\n* https://release-monitoring.org/project/4317/\r\n* https://release-monitoring.org/project/10454/\r\nSo indeed, when the-new-hotness tried to find the original project for the package, it found one with the same homepage and thought the project is releasing different tarballs, therefore it mapped the new package to the same project.\r\n\r\nI'm not quite sure what we could do to improve here :-s"}}