From: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 0/7] Replace sshd_config patching by snippets
Date: Thu, 14 Mar 2024 15:57:02 +0100 [thread overview]
Message-ID: <lyo7bg9801.fsf@ensc-pc.intern.sigma-chemnitz.de> (raw)
In-Reply-To: <68d71da3a6f49e2ac4594fa8ca633cdc7eb2e0fe.camel@linuxfoundation.org> (Richard Purdie's message of "Thu, 14 Mar 2024 13:40:57 +0000")
Richard Purdie <richard.purdie@linuxfoundation.org> writes:
> Some further related warnings:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/23/builds/9031/steps/11/logs/warnins
| stdio: WARNING: Nothing RPROVIDES 'nativesdk-openssh-config' ...
ok
I will reduce dependency from
|-RRECOMMENDS:${PN} += "openssh-config"
to
|+RRECOMMENDS:${PN}-sshd:class-target += "openssh-config"
| stdio: WARNING: Nothing RPROVIDES 'nativesdk-openssh-scp' ...
| stdio: WARNING: Nothing RPROVIDES 'nativesdk-openssh-sshd' ...
| stdio: WARNING: Nothing RPROVIDES 'nativesdk-openssh-ssh' ...
are these warnings really new?
Enrico
next prev parent reply other threads:[~2024-03-14 14:57 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 17:18 [PATCH 0/7] Replace sshd_config patching by snippets Enrico Scholz
2024-03-11 17:18 ` [PATCH 1/7] openssh: replace complete configuration files by patch Enrico Scholz
2024-03-11 17:41 ` Patchtest results for " patchtest
2024-03-11 18:16 ` [PATCH 1/7, v2] " Enrico Scholz
2024-03-11 18:33 ` Patchtest results for " patchtest
2024-03-12 11:00 ` [PATCH 1/7, v3] " Enrico Scholz
2024-03-12 13:10 ` [OE-core] " Alexander Kanavin
2024-03-12 14:06 ` Enrico Scholz
2024-03-16 23:58 ` Alexandre Belloni
2024-03-11 17:18 ` [PATCH 2/7] openssh-config: initial checkin Enrico Scholz
2024-03-11 17:41 ` Patchtest results for " patchtest
2024-03-11 18:12 ` Enrico Scholz
2024-03-12 13:14 ` [OE-core] " Trevor Gamblin
2024-03-11 17:18 ` [PATCH 3/7] openssh: move configuration tweaking in configuration recipe Enrico Scholz
2024-03-11 17:18 ` [PATCH 4/7] image: prepare openssh configuration Enrico Scholz
2024-03-11 17:18 ` [PATCH 5/7] openssh: replace 'allow-empty-password' rootfs scipt by configuration Enrico Scholz
2024-03-11 17:18 ` [PATCH 6/7] openssh: replace 'allow-root-login' " Enrico Scholz
2024-03-11 17:18 ` [PATCH 7/7] openssh: move read-only-rootfs setup in configuration snippet Enrico Scholz
2024-03-12 13:14 ` [OE-core] [PATCH 0/7] Replace sshd_config patching by snippets Alexander Kanavin
2024-03-14 11:00 ` Richard Purdie
2024-03-14 14:11 ` Enrico Scholz
2024-03-14 14:27 ` Richard Purdie
[not found] ` <17BC9C80577EA5C2.22340@lists.openembedded.org>
2024-03-14 13:40 ` Richard Purdie
2024-03-14 14:57 ` Enrico Scholz [this message]
2024-03-14 17:47 ` Alexander Kanavin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=lyo7bg9801.fsf@ensc-pc.intern.sigma-chemnitz.de \
--to=enrico.scholz@sigma-chemnitz.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox