From: Gyorgy Sarvari <skandigraun@gmail.com>
To: gitbeam@gmail.com, openembedded-devel@lists.openembedded.org
Cc: G B <gitbeam@proton.me>
Subject: Re: [oe] [PATCH] ntpsec: upgrade 1.2.2a -> 1.2.4
Date: Sat, 28 Feb 2026 21:25:39 +0100 [thread overview]
Message-ID: <ea3005d7-d7e6-42df-a6b0-bd49e9ea5f87@gmail.com> (raw)
In-Reply-To: <20260228173854.111416-1-gitbeam@proton.me>
On 2/28/26 18:38, G B via lists.openembedded.org wrote:
> Upgrade to latest upstream release 1.2.4.
>
> Release notes: https://docs.ntpsec.org/latest/CHANGES.html
This link throws a 404 - do you happen to have another one?
>
> Signed-off-by: G B <gitbeam@proton.me>
> ---
> .../ntpsec/{ntpsec_1.2.2a.bb => ntpsec_1.2.4.bb} | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
> rename meta-networking/recipes-support/ntpsec/{ntpsec_1.2.2a.bb => ntpsec_1.2.4.bb} (98%)
>
> diff --git a/meta-networking/recipes-support/ntpsec/ntpsec_1.2.2a.bb b/meta-networking/recipes-support/ntpsec/ntpsec_1.2.4.bb
> similarity index 98%
> rename from meta-networking/recipes-support/ntpsec/ntpsec_1.2.2a.bb
> rename to meta-networking/recipes-support/ntpsec/ntpsec_1.2.4.bb
> index 9ad97e7689..4f71cd2298 100644
> --- a/meta-networking/recipes-support/ntpsec/ntpsec_1.2.2a.bb
> +++ b/meta-networking/recipes-support/ntpsec/ntpsec_1.2.4.bb
> @@ -17,7 +17,7 @@ SRC_URI = "https://ftp.ntpsec.org/pub/releases/ntpsec-${PV}.tar.gz \
> file://0001-wscript-Add-BISONFLAGS-support.patch \
> "
>
> -SRC_URI[sha256sum] = "e0ce93af222a0a9860e6f5a51aadba9bb5ca601d80b2aea118a62f0a3226950e"
> +SRC_URI[sha256sum] = "443e54a6149d1b0bf08677d17b18fced9028b101fc2ffd2c81e0834f87eebc7d"
>
> UPSTREAM_CHECK_URI = "ftp://ftp.ntpsec.org/pub/releases/"
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#124782): https://lists.openembedded.org/g/openembedded-devel/message/124782
> Mute This Topic: https://lists.openembedded.org/mt/118064777/6084445
> Group Owner: openembedded-devel+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub [skandigraun@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
next prev parent reply other threads:[~2026-02-28 20:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-28 17:38 [PATCH] ntpsec: upgrade 1.2.2a -> 1.2.4 G B
2026-02-28 20:25 ` Gyorgy Sarvari [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-03-01 7:37 G B
2026-03-02 14:58 ` [oe] " Khem Raj
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=ea3005d7-d7e6-42df-a6b0-bd49e9ea5f87@gmail.com \
--to=skandigraun@gmail.com \
--cc=gitbeam@gmail.com \
--cc=gitbeam@proton.me \
--cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.