https://bugzilla.redhat.com/show_bug.cgi?id=2259222

Fabio Valentini <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected]
           Assignee|[email protected]    |[email protected]
             Status|NEW                         |ASSIGNED
              Flags|                            |fedora-review?



--- Comment #2 from Fabio Valentini <[email protected]> ---
> # FIXME: no license files detected

This needs to be addressed in some way.

It looks like the upstream repository actually contains license files, but they
are not linked into this subdirectory, so "cargo publish" will not include
them. Both the Apache-2.0 and MIT licenses require that redistributed sources
contain a copy of the actual license text, so this is a hard requirement for
us.

Please report this to the upstream project and ask them to include license
texts in all published crates.

Here's an example of a similar report that I filed a while ago:
https://github.com/Devolutions/picky-rs/issues/230

It is usually fixed easily by adding symbolic links:
https://github.com/djc/askama/pull/947


-- 
You are receiving this mail because:
You are always notified about changes to this product and component
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2259222

Report this comment as SPAM: 
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202259222%23c2
--
_______________________________________________
package-review mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to