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

Broken php-fpm systemd service in kirkstone, mickledore and nanbield #822

Closed
bence98 opened this issue May 3, 2024 · 5 comments
Closed

Comments

@bence98
Copy link

bence98 commented May 3, 2024

Commit 4cefe01 ("php-fpm: fix systemd") fixes php-fpm's systemd service. However, this was not backported to kirkstone and mickledore.

@bence98 bence98 changed the title Broken php-fpm systemd service in kirkstone and mickledore Broken php-fpm systemd service in kirkstone, mickledore and nanbield Jul 18, 2024
@bence98
Copy link
Author

bence98 commented Jul 18, 2024

Since then, mickledore and nanbield seem to have gone EOL, and this issue was never fixed. Is there any plans to fix this in kirkstone, which is supposed to be LTS until 2026, or are we just supposed to stick the support up our own arse?

@shr-project
Copy link
Contributor

What about reading README and sending backport request to ML?

@bence98
Copy link
Author

bence98 commented Jul 18, 2024

There's nothing about "backport requests" (grep back returns false) in either

  • README
  • meta-oe/README
  • and meta-oe/recipes-devtools/README does not exist

in the kirkstone branch of meta-openembedded. Or which README are you referring to?

So you're saying I should send a mail to the ML instead of opening an issue here?

@shr-project
Copy link
Contributor

You should send the patch you want to backport to ML with [kirkstone] in subject like README says https://git.openembedded.org/meta-openembedded/tree/meta-oe/README?h=kirkstone#n21

@bence98
Copy link
Author

bence98 commented Aug 6, 2024

Fixed in kirkstone as of 69d1121.

@bence98 bence98 closed this as completed Aug 6, 2024
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

No branches or pull requests

2 participants