https://bugzilla.redhat.com/show_bug.cgi?id=1409866 --- Comment #7 from Petr Pisar <ppisar@xxxxxxxxxx> --- $ rpmlint perl-Astro-SunTime.spec ../SRPMS/perl-Astro-SunTime-0.01-5.fc26.src.rpm ../RPMS/noarch/perl-Astro-SunTime-0.01-5.fc26.noarch.rpm 2 packages and 1 specfiles checked; 0 errors, 0 warnings. Package builds in F26 (https://koji.fedoraproject.org/koji/taskinfo?taskID=17178039). Ok. Thank you for improving the package. Now the only remaining issue is the license. I think there are three options: (1) Wait for a new release. (2) Package a snapshot from the Git repository. (3) Obtain a permission from the author. This means adding the e-mail reply about this package's license as Damian offered. There also could be fourth option and that's author's statement in his Git repository. I'm not a lawyer, but there had already been similar case accepted by Fedora legal <https://bugzilla.redhat.com/show_bug.cgi?id=1381888#c2>. But in this case I cannot find any clear link between the released code on the CPAN <http://search.cpan.org/~robf/Astro-SunTime-0.01/> and the Git repository <https://github.com/fugina-hackery/perl-astro-suntime>. The only common thing is the author's name, even the e-mail address does not match. Therefore I don't think the fourth option is acceptable. If you want, you can wait for the new release, though getting the permission via Damian could be quicker. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx