Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: jaipaul.cheernam@est.tech, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 2/2] libsecret: upgrade 0.21.7 -> 0.21.8.2
Date: Thu, 17 Sep 2026 21:07:39 +0100	[thread overview]
Message-ID: <71c2e47fa714ca48052d175ebc205e59803bf8d1.camel@linuxfoundation.org> (raw)
In-Reply-To: <20260917074956.22252-3-jaipaul.cheernam@est.tech>

On Thu, 2026-09-17 at 09:49 +0200, Jaipaul Cheernam via lists.openembedded.org wrote:
> NEWS: https://github.com/GNOME/libsecret/blob/0.21.8.2/NEWS
> 
> 0.21.8.2
>  * Release to bump meson.build version
> 
> 0.21.8.1
>  * Make secret_item_load_secrets_sync match async behavior [!180]
> 
> 0.21.8
>  * Allow the content type to have additional parameters [#114, !175]
>  * Support individually encrypted items [!174]
>  * Ensure we return chained up GTask [!179]
>  * Ensure length of DH shared secret match length of prime on GnuTLS [!170]
>  * file-backend: Add thread safety and file-based locking to prevent concurrent write races [!171]
>  * file-backend: Fix possible memory leak in error path of secret_file_backend_real_search() [!173]
>  * file-collection: Fix memory leaks on repeated calls [!173]
>  * Replace some SecretSync with a sync implementation [!108]
>  * Add linker version script to hide private symbols [#70, !159]
>  * Stop using CONST annotations on non-const fns [!176]
>  * secret-tool: align behavior for collection option [!164]
>  * secret-tool: document --collection option [#31, !164]
>  * meson: Put test setup behind a feature option [#101, !162]
>  * Several test and CI improvements [!172, !177, !178]
>  * Updated translations
> 
>  - Refresh the pam-tests patch for the new release.
> 
> Signed-off-by: Jaipaul Cheernam <jaipaul.cheernam@est.tech>
> ---
>  ...meson-add-option-to-disable-pam-tests.patch | 18 +++++++++++-------
>  ...bsecret_0.21.7.bb => libsecret_0.21.8.2.bb} |  2 +-
>  2 files changed, 12 insertions(+), 8 deletions(-)
>  rename meta/recipes-gnome/libsecret/{libsecret_0.21.7.bb => libsecret_0.21.8.2.bb} (92%)

https://autobuilder.yoctoproject.org/valkyrie/#/builders/111/builds/3394

Cheers,

Richard


  reply	other threads:[~2026-09-17 20:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-17  7:49 [PATCH 0/2] libsecret: upgrade 0.21.7 -> 0.21.8.2 Jaipaul Cheernam
2026-09-17  7:49 ` [PATCH 1/2] gnomebase: fix gnome_verdir for four-component versions Jaipaul Cheernam
2026-09-17  7:49 ` [PATCH 2/2] libsecret: upgrade 0.21.7 -> 0.21.8.2 Jaipaul Cheernam
2026-09-17 20:07   ` Richard Purdie [this message]
2026-09-17 21:19     ` [OE-core] " Jaipaul Cheernam
2026-09-17 21:24 ` [PATCH v2 0/2] libsecret: upgrade to 0.21.8.2 and fix gnomebase verdir Jaipaul Cheernam
2026-09-17 21:24   ` [PATCH v2 1/2] gnomebase: fix gnome_verdir for four-component versions Jaipaul Cheernam
2026-09-19  2:11     ` [OE-core] " Tim Orling
2026-09-23 14:05     ` Ross Burton
2026-09-23 14:21       ` Ross Burton
2026-09-23 14:42         ` Ross Burton
2026-09-23 14:45           ` Jaipaul Cheernam
2026-09-17 21:24   ` [PATCH v2 2/2] libsecret: upgrade 0.21.7 -> 0.21.8.2 Jaipaul Cheernam

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=71c2e47fa714ca48052d175ebc205e59803bf8d1.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=jaipaul.cheernam@est.tech \
    --cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox