https://bugzilla.redhat.com/show_bug.cgi?id=2296168 --- Comment #7 from wojnilowicz <lukasz.wojnilowicz@xxxxxxxxx> --- (In reply to Fabio Valentini from comment #6) > In this case, the upstream project provides license files, they're just not > included in the published crate. > So including them manually from GitHub is fine for now. The bigger problem > for me is that the published crate doesn't match the state of the repo. But > having the maintainer push their local-only changes should be an easier > thing to accomplish ("git push") than poking them with a PR about licenses. git push of 104e797d440d6fb7e8ba107cca27714a71cc368a won't work, because I already pushed https://github.com/SergioBenitez/Devise/commit/b2999b2d3adc5cbea75461bbcb081e0446924650 with licenses 104e797d440d6fb7e8ba107cca27714a71cc368a would have to be recreated under a new SHA1. A PR with 0.4.1 would be the same struggle as the PR with licenses. The same poking, and the same waiting. Would you like to wait till I'll manage with the upstream to release 0.4.2 before approving this package? -- 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 https://bugzilla.redhat.com/show_bug.cgi?id=2296168 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202296168%23c7 -- _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/package-review@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
