https://bugzilla.redhat.com/show_bug.cgi?id=2467057
--- Comment #2 from [email protected] --- Spec URL: https://trix.fedorapeople.org/openclaw.spec SRPM URL: https://trix.fedorapeople.org/openclaw-2026.5.7-1.fc45.src.rpm - The License field has a syntax error: duplicate "AND AND" between Python-2.0 and 0BSD. The field must be corrected to remove the extra operator. Suggested fix: replace the double AND with a single AND, and add the missing Apache-2.0 (see next issue). See: https://fedoraproject.org/wiki/Changes/SPDX_Licenses_Phase_1 Fixed - Apache-2.0 is missing from the License field. Multiple bundled dependencies carry the Apache-2.0 license including @aws-sdk/*, @smithy/*, @anthropic-ai/sdk, and @google/genai. It is listed in bundled-licenses.txt as both "Apache 2.0" and "Apache-2.0" but does not appear in the spec License: field at all. Suggested License field (correcting both issues): MIT AND (MIT AND Zlib) AND (MIT OR CC0-1.0) AND (MIT OR GPL-3.0-or-later) AND Apache-2.0 AND MPL-2.0 AND Python-2.0 AND 0BSD AND BSD-2-Clause AND BSD-3-Clause AND ISC AND BlueOak-1.0.0 AND CC-BY-SA-4.0 AND CC0-1.0 Added Apache-2.0 - rpmlint flags Python-2.0 as invalid-license. Python-2.0 is a valid SPDX identifier (Python Software Foundation License 2.0) and is approved for Fedora. The spec contains good inline justification for why argparse uses Python-2.0. This may be a gap in rpmlint's allowlist; packager should verify Python-2.0 is recognized by the current rpmlint/fedora-spdx-licenses configuration. rpmlint is looking for PSF-2.0 the SPDX short form Tag ended up being License: MIT AND (MIT AND Zlib) AND (MIT OR CC0-1.0) AND (MIT OR GPL-3.0-or-later) AND Apache-2.0 AND MPL-2.0 AND PSF-2.0 AND 0BSD AND BSD-2-Clause AND BSD-3-Clause AND ISC AND BlueOak-1.0.0 AND CC-BY-SA-4.0 AND CC0-1.0 - rpmlint reports 3 spelling errors (E:) for "macOS" and "iMessage" in %description. These are proper product names, not misspellings. Packager must add an rpmlintrc entry to suppress these or reword the description. Example rpmlintrc addition: addFilter("spelling-error.*macOS") addFilter("spelling-error.*iMessage") Reduced the description so no mipspellings. [?]: Package functions as described. Note: Not tested — would require AI provider API keys and a messaging platform account to exercise the full functionality. Build and install verified; the openclaw binary symlink resolves correctly. ollama launch openclaw Is what i use to start up, the llm handling is local so no api keys needed. [!]: Latest version is packaged. Note: Version 2026.5.7 is available. Got it! [!]: %check is present and all tests pass. Note: No %check section. This is expected for an npm application package where dev dependencies (required for tests) are not bundled — the spec notes that workspace: protocol prevents including dev deps in the bundled tarball. Packager should document this limitation in a spec comment and consider whether any basic smoke tests could be run without dev deps. I am not sure how to do this in %check, i'll be checking this with containers or dogfooding so i can start ollama. - W: no-manual-page-for-binary openclaw — SHOULD item; recommend upstream adds one I do not think a man page is needed. Here is me asking openclaw where to find its documentation. https://docs.openclaw.ai is where the docs are. where can i find the documentation for openclaw ? You May 11, 2026, 8:56 AM Assistant You can find the documentation for OpenClaw in a few places, depending on what kind of guide you need! Here are the main resources: Local Documentation (For configuration and structure): The core documentation files are located at /usr/lib/node_modules/openclaw/docs. I also keep the reference files like docs/gateway/configuration.md and docs/gateway/configuration-reference.md here for specific technical details. Official Mirror/Website: For the most up-to-date, user-facing guides, you should check the official mirror: https://docs.openclaw.ai Source Code/Reference: If you are looking at the underlying architecture, the GitHub repository is the best place: https://github.com/openclaw/openclaw Community Support: For help, Q&A, or discussions, the Discord community is active: https://discord.com/invite/clawd Let me know if you're looking for documentation on a specific topic (like Gateway configuration or Skills), and I can narrow it down for you! -- 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=2467057 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202467057%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://forge.fedoraproject.org/infra/tickets/issues/new
