kong/3.9.1 package update

[octo-sts]

Closes: #55113

[octo-sts]

🩹 Build Failed: Patch Application Failed

Hunk #3 FAILED at 113. 1 out of 3 hunks FAILED -- saving rejects to file build/luarocks/templates/luarocks_exec.sh.rej

Build Details

Category	Details
Build System	Bazel
Failure Point	Patching the file build/luarocks/templates/luarocks_exec.sh

Root Cause Analysis 🔍

A patch could not be cleanly applied to the file build/luarocks/templates/luarocks_exec.sh. Specifically, hunk #3 (targeting line 113) failed to apply, which suggests that the source file has changed since the patch was created, causing a conflict.

---

🔍 Build failure fix suggestions

Found similar build failures that have been fixed in the past and analyzed them to suggest a fix:

Suggested Changes

File: http-archive.patch or openssl.patch (whichever contains the failing hunk)

• update at line hunk Add the busybox package. #3 around line 113 (Patch section targeting build/luarocks/templates/luarocks_exec.sh)
  Original:

The failing patch content (cannot be determined exactly without seeing the patch file)

Replacement:

Create an updated patch that matches the current structure of build/luarocks/templates/luarocks_exec.sh in Kong 3.9.1

Click to expand fix analysis

Analysis

The build is failing because a patch file (likely either http-archive.patch or openssl.patch) contains changes that can't be applied cleanly to the build/luarocks/templates/luarocks_exec.sh file. Specifically, hunk #3 targeting line 113 failed to apply. This suggests that the upstream Kong repository (version 3.9.1) has modified this file compared to when the patches were created.

Without examples of similar fixed build failures, I'll need to focus on the typical approaches for resolving patch conflicts in build systems like this. The most common solution is to update the patch file to match the current structure of the upstream source file.

Click to expand fix explanation

Explanation

The build failure occurs because a patch cannot be applied cleanly to the target file. This typically happens when:

1. The upstream project has changed the target file since the patch was created
2. The line numbers or context in the patch no longer match the current file

To fix this issue, we need to:

1. Extract the current version of build/luarocks/templates/luarocks_exec.sh from the Kong 3.9.1 source
2. Examine the failed patch to understand what changes it was trying to make
3. Create a new patch that applies the same logical changes but matches the current file structure

This approach directly addresses the error message "Hunk #3 FAILED at 113" by updating the patch to match the current structure of the file. Since the build environment is clean and ephemeral, and all necessary dependencies are installed via the Melange YAML, the issue is isolated to the patch application step.

Click to expand alternative approaches

Alternative Approaches

• Skip the problematic patch if its changes are no longer necessary. This would require modifying the Melange YAML to remove or conditionally apply the problematic patch.
• Manually apply the intended changes from the patch directly in the pipeline script section after the git checkout and before the build step, bypassing the patch system entirely.
• Check if a newer version of Kong (beyond 3.9.1) has changes that make the patch unnecessary, and consider upgrading to that version instead.
• Contact the Kong maintainers to understand if the changes from the patch have been incorporated into the upstream in a different way that makes the patch obsolete.

---

Was this comment helpful? Please use 👍 or 👎 reactions on this comment.