[Bug 2230729] Review Request: rust-gvdb - Read and write GLib GVariant database files

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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

Fabio Valentini <decathorpe@xxxxxxxxx> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Assignee|nobody@xxxxxxxxxxxxxxxxx    |decathorpe@xxxxxxxxx
                 CC|                            |decathorpe@xxxxxxxxx
              Flags|                            |fedora-review?
             Status|NEW                         |ASSIGNED



--- Comment #3 from Fabio Valentini <decathorpe@xxxxxxxxx> ---
Two issues I can note immediately while I'm running a scratch build for all
architectures:

1. Please file an upstream issue for the missing license file. The MIT license
is one of the licenses that requires redistributed sources to contain a copy of
the license text. This applies to crates distributed via crates.io and to
distro packages (it can be solved by including the file manually from upstream
git for now, but that should be a temporary solution until upstream publishes
tarballs / crates with the license text included).

2. You might want to prevent test data from being installed / packaged. They
include some icons where I'm not sure where they're from (looks like either the
hicolor icon theme or Adwaita icon theme), so it's not clear which license
applies to them (if any). It would be good to clarify the origin / license of
these files with upstream. Until then, the least that you'd need to do is
prevent them from being included in built RPMs, simplest solution would be a
patch for Cargo.toml that does this:

-exclude = ["test/c"]
+exclude = ["test/c", "test-data"]

It doesn't look like anything from the test-data directory is non-free /
non-redistributable, but I can't be sure about that since it's not documented
where the files come from, so it would be great if upstream could clarify this.
In the unlikely event that the files indeed are non-redistributable, you would
need to re-package a "clean" tarball without the test data. You can look at the
rust-statrs package for an example of how to do that. Another solution would be
to ask upstream to exclude the test-data directory from published crate
tarballs (i.e. push the 1-line-patch included above to be upstream instead of
downstream).


-- 
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=2230729

Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202230729%23c3
_______________________________________________
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




[Index of Archives]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite Conditions]     [KDE Users]

  Powered by Linux