openrc/0.63 package update

[octo-sts]

[octo-sts]

🩹 Build Failed: Patch Application Failed

Reversed (or previously applied) patch detected! Assume -R? [n] Apply anyway? [n] Skipping patch. Hunk #1 ignored at 171. 1 out of 1 hunk ignored -- saving rejects to file src/start-stop-daemon/start-stop-daemon.c.rej

Build Details

Category	Details
Build System	melange
Failure Point	patch step applying start-stop-daemon-help.patch

Root Cause Analysis 🔍

The patch 'start-stop-daemon-help.patch' has already been applied to the source code or conflicts with existing changes. The patch system detected that the patch was either previously applied or reversed, causing it to fail during the patching step of the build process.

---

🔍 Build failure fix suggestions

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

Similar PRs with fixes

• metric-collector-for-apache-cassandra-4.1/0.3.6 package update #48616
• ruby3.3-rubyzip/3.0.1 package update #62075
• linkerd-network-validator/0.1.4 package update #61468

Suggested Changes

File: openrc.yaml

• version_update at line 3 (package.version)
  Original:

version: "0.63"

Replacement:

version: "0.63.1"

Content:

Update package version to latest upstream release

• commit_update at line 20 (pipeline.git-checkout.expected-commit)
  Original:

expected-commit: e50e4a8189fd9f58c28343da7fee4f1ee47fe6f1

Replacement:

expected-commit: [latest commit hash for 0.63.1]

Content:

Update expected commit to match the new version tag

• patch_removal at line 23-25 (pipeline.patch section)
  Original:

  - uses: patch
    with:
      patches: start-stop-daemon-help.patch

Content:

Remove the patch step entirely since the fix is now upstream

Click to expand fix analysis

Analysis

Looking at the three similar patch failure fixes, I observe a clear pattern: all failures were resolved by updating the package version and removing the problematic patch that was already applied upstream. In Fix #0, metric-collector-for-apache-cassandra was updated from 0.3.5 to 0.3.6 and the collectd-download-url-fix.patch was removed. In Fix #1, ruby3.3-rubyzip was updated from 3.0.0 to 3.0.1 and gh636.patch was removed. In Fix #2, linkerd-network-validator was updated from 0.1.3 to 0.1.4 and help-feature.patch was removed. The common thread is that upstream releases incorporated the patches, making the local patches redundant and causing conflicts during application.

Click to expand fix explanation

Explanation

The fix should work because the patch failure indicates that start-stop-daemon-help.patch has already been applied upstream in a newer version of OpenRC. When patches are incorporated upstream, attempting to apply them again causes the "Reversed (or previously applied) patch detected" error. By updating to the latest upstream version (0.63.1 or newer), we get the fix that was previously applied via the patch, eliminating the need for the local patch file. This approach mirrors the successful pattern seen in all three similar fixes where version updates resolved patch conflicts. The OpenRC project actively maintains their codebase, so checking for a newer release that includes the help functionality fix is the most reliable solution.

Click to expand alternative approaches

Alternative Approaches

• Investigate the specific content of start-stop-daemon-help.patch and verify if it's already in the current codebase, then remove only the patch without version update
• Modify the patch file to apply cleanly against the current version if the functionality is still needed
• Use conditional patching with version checks to only apply the patch when necessary

---

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