I would like to get an authoritative answer regarding the removal of a
copyrighted file from upstream's source tarball.
The package in question is vxl  and the file in question is the Lenna
image [2,3]. We currently remove it from the tarball manually and then
upload the cleansed archive to the side cache. However, that effectively
breaks scratch builds, since the source is not available.
I would like to remove the offending file in %prep, thereby excluding it
from the RPMs. However the original archive as present in SRPM and side
cache would then contain a non-free copyrighted file. Is that allowed?
Either way, since I couldn't find a clear answer in the packaging
guidelines, I would also like to get approval for a text that could be
published in the guidelines, so we have a place to point people to
should this come up during review.
Thanks for your advice,
On Wed, Jun 28, 2023 at 4:44 PM <h-k-81(a)hotmail.com> wrote:
> I am in the process of reviewing this package . The author of the pacakge mentions "A lot of the code in this package was based on Julien Schmidt's httprouter." in the documentation and includes the license file of httprouter.
> The thing is that httprouter is written in Go and the library, that is being packaged, is written in Rust.
> So the question here is, does the Rust library have to include and mention the license of httprouter?
I think you may be asking one of more of the following questions:
1. Given that httprouter is written in Go, can we assume that the
license of httprouter doesn't apply to this Rust crate?
2. Does the binary package need to install the httprouter license file?
3. Should the httprouter license be included in the spec file License: field?
As to 1: I don't think we can assume that, no. The upstream project
says it's based on httprouter and it could be that some of it is a
close translation from Go to Rust. While the BSD licenses are not
entirely clear on this issue I think you should assume that the Rust
crate copies from httprouter in such a way that the httprouter license
requirements are triggered.
As to 2: We still don't have updated standards around how to deal with
installation of license files and (in my opinion) the existing
packaging guidelines on that topic don't entirely make sense. In this
case I'd take a conservative approach and assume the httprouter
license needs to be installed along with the rust-matchit project
As to 3, this follows from 1: you should assume the License: field
should include `BSD-3-Clause` as appropriate.
I am in the process of reviewing this package . The author of the
pacakge mentions "A lot of the code in this package was based on Julien
Schmidt's |httprouter| <https://github.com/julienschmidt/httprouter>."
in the documentation and includes the license file of httprouter.
The thing is that httprouter is written in Go and the library, that is
being packaged, is written in Rust.
So the question here is, does the Rust library have to include and
mention the license of httprouter?
Good morning to you all,
I was thinking about packaging Yuzu for Fedora. Yuzu is an emulator for the
Nintendo Switch, *which requires you to dump your Nintendo Switch's
firmware to work*. (I believe the emulator will actually start without the
firmware, but you won't be able to go far without it).
As far as I understand the legal instructions from the Fedora wiki (
*Some emulators (applications which emulate another platform) are not
permitted for inclusion in Fedora Linux. These rules will help you
determine if an emulator is acceptable for Fedora.*
*Emulators which depend on firmware or ROM files to function may not be
included in Fedora Linux, unless the copyright holder(s) for the
firmware/ROM files give clear permission for the firmware/ROM files to be
distributed (either under a Fedora allowed license or a Fedora
allowed-firmware license). Note: This only covers the situation where an
emulator will not run at all without firmware/ROM files. For example,
emulators that compile and run, but ship with no game ROMs are not covered
by this rule.Emulators must not ship with any ROM files (e.g. games) unless
those ROM files are available under a Fedora allowed license and have been
built from source code in the Fedora buildsystem.Emulators must not point
to any third-party sites which provide firmware or ROM files that are
distributed without the clear and explicit permission of their copyright
holders.All other Fedora licensing and packaging rules apply to emulators.*
That emulator does indeed not include any roms or firmware. But it gives
you a fully fleshed out guide on how to rip it from your Nintendo Switch (
https://yuzu-emu.org/help/quickstart/) and gives links to hack tools.
Can such a software be packaged for Fedora?