Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

gtk-4/4.17.2 package update #38405

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

octo-sts[bot]
Copy link
Contributor

@octo-sts octo-sts bot commented Dec 27, 2024

Signed-off-by: wolfi-bot <121097084+wolfi-bot@users.noreply.github.com>
@octo-sts octo-sts bot added request-version-update request for a newer version of a package automated pr labels Dec 27, 2024
Copy link
Contributor Author

octo-sts bot commented Dec 27, 2024

Gen AI suggestions to solve the build error:

Based on the error output, I can provide a specific analysis and fix:

• Detected Error: ModuleNotFoundError: No module named 'gidocgen'

• Error Category: Dependency

• Failure Point: Documentation generation step using gi-docgen

• Root Cause Analysis: The gi-docgen Python module is not properly installed despite the gi-docgen package being present

• Suggested Fix: Add py3-gi-docgen and gi-docgen to the environment packages section:

environment:
  contents:
    packages:
      # Add these lines to your existing packages list
      - py3-gi-docgen
      - gi-docgen 
      - python3

• Explanation: The build is failing during documentation generation because while the gi-docgen binary is installed, its Python module dependencies are missing. The py3-gi-docgen package provides the required Python modules for the documentation generator to work.

• Additional Notes:

  • The error occurs during the GIR documentation generation phase
  • This is a common issue when building GTK4 documentation
  • The fix ensures both the binary and Python module components are available
  • You may also need to ensure Python 3 is explicitly included

• References:

@octo-sts octo-sts bot added the bincapz/pass bincapz/pass Bincapz (aka. malcontent) scan didn't detect any CRITICALs on the scanned packages. label Dec 27, 2024
Copy link
Contributor Author

octo-sts bot commented Dec 27, 2024

Gen AI suggestions to solve the build error:

Based on the error output, I can help resolve this build failure.

• Detected Error:

ModuleNotFoundError: No module named 'gidocgen'

• Error Category: Dependency

• Failure Point: Documentation generation step using gi-docgen

• Root Cause Analysis: The build is failing because the Python module 'gidocgen' is missing, which is required for generating GTK documentation. While the gi-docgen executable is present (/usr/local/bin/gi-docgen), its required Python module is not installed.

• Suggested Fix:
Add py3-gi-docgen to the environment packages list in the melange YAML:

environment:
  contents:
    packages:
      # ... existing packages ...
      - py3-gi-docgen
      - py3-packaging
      - py3-docutils
      - py3-smartypants
      - py3-typogrify    # Optional but recommended for gi-docgen

• Explanation:
The build system is trying to generate GTK documentation using gi-docgen but the required Python module is not available in the build environment. Adding py3-gi-docgen and its dependencies will provide the necessary Python modules for documentation generation.

• Additional Notes:

  1. gi-docgen is the new documentation generator for GObject-based libraries, replacing gtk-doc
  2. The error occurs during the documentation generation phase, not during the actual library build
  3. If documentation is not required, you could alternatively disable it by adding -Ddocumentation=false to the meson configure options

• References:

@developer-guy developer-guy force-pushed the wolfictl-5abbc6ba-9197-4fb4-b3ce-4772da81a510 branch 2 times, most recently from 2b99991 to ebf50b7 Compare December 27, 2024 20:13
Copy link
Contributor Author

octo-sts bot commented Dec 27, 2024

Gen AI suggestions to solve the build error:

• Detected Error: "ModuleNotFoundError: No module named 'gidocgen'"

• Error Category: Dependency

• Failure Point: Documentation generation step using gi-docgen

• Root Cause Analysis:
The Python module 'gidocgen' required for generating documentation is not installed in the build environment, despite having gi-docgen executable present.

• Suggested Fix:
Add python3-gidocgen package to the build environment dependencies:

environment:
  contents:
    packages:
      # Add this with other python dependencies
      - python3-gidocgen
      # Existing packages...

• Explanation:
The gi-docgen tool requires its Python module to be installed separately from the executable. Adding python3-gidocgen ensures all required components are present for documentation generation.

• Additional Notes:

  • This is a documentation generation failure, not a core build failure
  • The main library build completed successfully
  • Documentation generation is the last step in the process
  • Consider making documentation optional with a build flag if needed

• References:

Copy link
Contributor Author

octo-sts bot commented Dec 27, 2024

Gen AI suggestions to solve the build error:

• Detected Error: "ModuleNotFoundError: No module named 'gidocgen'"

• Error Category: Build/Dependency

• Failure Point: During documentation generation step using gi-docgen

• Root Cause Analysis: The Python module 'gidocgen' required for generating GTK documentation is not installed in the build environment.

• Suggested Fix:
Add gi-docgen Python package to the environment section:

environment:
  contents:
    packages:
      # Add these packages
      - py3-gi-docgen
      - py3-packaging
      - python3
      # ... rest of existing packages

• Explanation:
The build is failing because gi-docgen (GObject Introspection documentation generator) is not available. The py3-gi-docgen package provides the required Python module for generating GTK API documentation.

• Additional Notes:

  1. This is a documentation generation dependency, not a runtime dependency
  2. The error occurs late in the build process, after successful compilation
  3. If documentation is not required, you could alternatively disable documentation building by adding '-Ddocumentation=false' to the meson configuration options

• References:

@developer-guy developer-guy force-pushed the wolfictl-5abbc6ba-9197-4fb4-b3ce-4772da81a510 branch from ebf50b7 to 41228fb Compare December 27, 2024 20:27
gtk-4.yaml Outdated Show resolved Hide resolved
gtk-4.yaml Outdated Show resolved Hide resolved
Signed-off-by: Batuhan Apaydin <batuhan.apaydin@chainguard.dev>
@developer-guy developer-guy force-pushed the wolfictl-5abbc6ba-9197-4fb4-b3ce-4772da81a510 branch from 41228fb to cef47b8 Compare December 28, 2024 09:40
Copy link
Contributor Author

octo-sts bot commented Dec 28, 2024

Gen AI suggestions to solve the build error:

Based on the build error output, I can help resolve this issue.

• Detected Error:

Traceback (most recent call last):
  File "/usr/local/bin/gi-docgen", line 14, in <module>
    from gidocgen import gidocmain
ModuleNotFoundError: No module named 'gidocgen'

• Error Category: Dependency

• Failure Point: Documentation generation step using gi-docgen

• Root Cause Analysis: The build is failing because the Python module 'gidocgen' is not installed in the build environment, which is required for generating GTK documentation.

• Suggested Fix:
Add the Python gidocgen module to the build environment packages list:

environment:
  contents:
    packages:
      # Add these new entries
      - py3-gidocgen
      - py3-pip
      # Keep existing packages...

• Explanation:
The build fails during documentation generation because gi-docgen relies on the gidocgen Python module. Adding py3-gidocgen to the build environment will provide the required Python module for documentation generation.

• Additional Notes:

  1. This is a common issue when building GTK4 with documentation enabled
  2. If py3-gidocgen is not available, you could alternatively disable documentation generation by adding this to meson options:
  - uses: meson/configure
    with:
      opts: |
        -Ddocumentation=false \

• References:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automated pr bincapz/pass bincapz/pass Bincapz (aka. malcontent) scan didn't detect any CRITICALs on the scanned packages. manual/review-needed request-version-update request for a newer version of a package
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants