Skip to content

Bslawomir330 patch 1#1044

Open
bslawomir330 wants to merge 1 commit intoopenembedded:scarthgapfrom
bslawomir330:bslawomir330-patch-1
Open

Bslawomir330 patch 1#1044
bslawomir330 wants to merge 1 commit intoopenembedded:scarthgapfrom
bslawomir330:bslawomir330-patch-1

Conversation

@bslawomir330
Copy link
Copy Markdown

FRR frr-reload.py path update to /usr/libexec/frr/

Summary

This pull request updates the FRR (FRRouting) recipe to use the correct path for frr-reload.py in /usr/libexec/frr/ instead of /usr/lib/frr/.

Changes

  • Added new patch file: 0002-tools-update-frr-reload.py-path-to-usr-libexec-frr.patch
    • Updates tools/frr-reload script to look for frr-reload.py in /usr/libexec/frr/
    • Ensures proper execution path for the FRR reload utility
  • Updated frr_9.1.3.bb recipe to include the new patch in the build process

Details

  • Recipe: meta-networking/recipes-protocols/frr/frr_9.1.3.bb
  • FRR Version: 9.1.3
  • Branch: stable/9.1

Testing

Please verify that:

  • The FRR package builds successfully with this patch
  • The frr-reload.py script is correctly located and executable in /usr/libexec/frr/
  • Existing functionality is not affected

@OldManYellsAtCloud
Copy link
Copy Markdown
Contributor

OldManYellsAtCloud commented Apr 7, 2026

The FRR package builds successfully with this patch

I am not confident that this was really tested - looking at the change, I don't think that this can end in anything else but a fatal QA error. (Edit: I missed that it's scarthgap, which shouldn't end with error, but there should be a warning about the same issue - regardless, please fix)

After fixing that, could you please squash these commits, add a descriptive commit message about the issue this is solving, and prefix the commit subject with the recipe name?

As a somewhat related question, if this is about the location of files, is it really a bug in the frr-reload script, and not a problem with the recipe that installs it to an incorrect location? (The patch essentially might be correct as it is, I'm just looking for some clarity)

@bslawomir330
Copy link
Copy Markdown
Author

I do not understand the claim regarding a fatal QA error.

The location of executable files in /usr/libexec/frr is appropriate; after all, it concerns scripts, not libraries.

This is not a bug in the frr-reload.sh script, but rather a misalignment with the Autotools configuration process.
I believe it is a waste of time to address this at the source of the problem.
Patching is intended, among other things, to correct such issues.

@OldManYellsAtCloud
Copy link
Copy Markdown
Contributor

I'm referring to the Upstream-Status tag, which is missing from the patch: https://docs.yoctoproject.org/scarthgap/contributor-guide/recipe-style-guide.html#patch-upstream-status

It might be a waste of time to fix it other way, but it would be useful to add some note about it in the commit message and maybe in the patch also: what's the actual problem, and why it is better to solve it like that. It doesn't need to be a long essay, but leaving it out will just people scratching their head.

-if test -e /usr/lib/frr/frr-reload.py; then
- exec /usr/lib/frr/frr-reload.py --reload /etc/frr/frr.conf
+if test -e /usr/libexec/frr/frr-reload.py; then
+ exec /usr/lib/frrexec/frr-reload.py --reload /etc/frr/frr.conf
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this not be /usr/libexec/frr/frr-reload.py also just like the path in the test one line above also?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, that is an error.

Update tools/frr-reload to reference frr-reload.py in the correct
location (/usr/libexec/frr/ instead of /usr/lib/frr/).

Add corresponding patch to the recipe build process.

Signed-off-by: Slawomir Blaszczyk <bslawomir330>
@bslawomir330 bslawomir330 force-pushed the bslawomir330-patch-1 branch from a8a07a0 to 65b21c6 Compare April 7, 2026 12:23
@bslawomir330
Copy link
Copy Markdown
Author

Thank you for your patience. I believe I have implemented the requested adjustments.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants