Bug 892111
| Summary: | zeromq is non-free (licensed under AFPL) file included | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | mejiko <private> |
| Component: | zeromq | Assignee: | Thomas Spura <tomspur> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 17 | CC: | andrewniemants, tcallawa, tomspur |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-01-23 16:09:21 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 182235 | ||
|
Description
mejiko
2013-01-05 09:00:54 UTC
Blocking FE-Legal, This is license problem. Thanks for the bug report. I can't find any reference, where this xmlparser is actually in use in the build log, e.g.: http://kojipkgs.fedoraproject.org//packages/zeromq/2.2.0/3.fc19/data/logs/x86_64/build.log http://kojipkgs.fedoraproject.org//packages/zeromq/2.1.11/1.fc17/data/logs/x86_64/build.log Furthermore, these files are redistributed along zeromq ('redistributed' means bundled in the tar ball and provided for downloading on fedora infrastructure in this case.). As I see it, this is allowed as zeromq is allowed to use it under the terms of BSD, so I don't need to remove it from the tar ball before uploading it, isn't it? I'd suggest removing them in %prep and then not using them (as we already do now AFAIK). I wait for a final decision by FE-Legal before either: * removing them in %prep and still ship it in the uploaded tar ball. * removing them before uploading and request rel-eng to remove all tar balls, which contain those files from fedora infrastructure. I agree with Thomas. If these files are unused, they can be removed in %prep, we do not need to make a new tarball. Additionally, RH Legal confirms that we can safely treat these files as being under BSD. zeromq-2.2.0-4.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/zeromq-2.2.0-4.fc17 zeromq-2.2.0-4.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/zeromq-2.2.0-4.el6 zeromq-2.2.0-4.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/zeromq-2.2.0-4.fc18 zeromq-2.2.0-4.el5 has been submitted as an update for Fedora EPEL 5. https://admin.fedoraproject.org/updates/zeromq-2.2.0-4.el5 zeromq-2.2.0-4.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/zeromq-2.2.0-4.fc16 zeromq3 is not affected by this as it does not ship "foreign/xmlParser/". Package zeromq-2.2.0-4.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing zeromq-2.2.0-4.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-0794/zeromq-2.2.0-4.fc16 then log in and leave karma (feedback). zeromq-2.2.0-4.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. zeromq-2.2.0-4.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. zeromq-2.2.0-4.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report. |