Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer via buildroot <buildroot@buildroot.org>
To: Peter Korsgaard <peter@korsgaard.com>
Cc: buildroot@busybox.net
Subject: Re: [Buildroot] [PATCH v2 1/5] package/xz: bump version to 5.4.7
Date: Mon, 8 Jul 2024 14:54:36 +0200	[thread overview]
Message-ID: <20240708145436.55ec576f@gmx.net> (raw)
In-Reply-To: <87ikxgqjxj.fsf@dell.be.48ers.dk>

Hello Peter, *,

On Mon, 08 Jul 2024 12:04:08 +0200, Peter Korsgaard <peter@korsgaard.com> wrote:

> >>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:
>
>  > On 12/06/2024 15:57, Peter Seiderer via buildroot wrote:
>  >> - add key hint for download signature check
>  >> - update COPYING hash due to [1] (change of home page URL)
>  >> For details see [2].
>
>  >  I've added a statement here to make clear this is not affected by the backdoor.
>
>  >  Peter, this is for 2024.02.x and 2024.05.x.
>
> OK. Looking at https://github.com/tukaani-project/xz/releases/tag/v5.4.7
> I see a mention about a shared library regression on mips64, but I am
> not sure where the mentioned patch can be found?

Do not see an upstream issue nor an suitable upstream patch..., the only
linking issue I know of is from the buildroot autobuilders see
https://lore.kernel.org/buildroot/20240703105013.1bd207f1@gmx.net/
(affects 5.6.2/5.4.7 but not 5.4.6 - and could be fixed by
'XZ_AUTORECONF = YES')...

>
> The 5.4.7 bugfixes do not look very critical, so we could alternatively
> also just not bump the version on 2024.02.x / 2024.05.x.
>

Fine by me...

Regards,
Peter

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2024-07-08 12:54 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-12 13:57 [Buildroot] [PATCH v2 1/5] package/xz: bump version to 5.4.7 Peter Seiderer via buildroot
2024-06-12 13:57 ` [Buildroot] [PATCH v2 2/5] package/xz: bump version to 5.6.2 Peter Seiderer via buildroot
2024-06-12 15:48   ` Julien Olivain
2024-06-24 13:42   ` Arnout Vandecappelle via buildroot
2024-06-12 13:57 ` [Buildroot] [PATCH v2 3/5] package/xz: determine all autoconf options Peter Seiderer via buildroot
2024-06-24 13:44   ` Arnout Vandecappelle via buildroot
2024-06-12 13:57 ` [Buildroot] [PATCH v2 4/5] package/xz: enable year2038 option Peter Seiderer via buildroot
2024-06-24 13:46   ` Arnout Vandecappelle via buildroot
2024-06-12 13:57 ` [Buildroot] [PATCH v2 5/5] package/xz: convert to cmake build Peter Seiderer via buildroot
2024-06-24 13:52   ` Arnout Vandecappelle via buildroot
2024-06-25  9:56   ` yann.morin
2024-06-25 11:11     ` yann.morin
2024-06-26  8:36       ` Peter Seiderer via buildroot
2024-06-26 19:32         ` Yann E. MORIN
2024-06-27  7:50           ` Peter Seiderer via buildroot
2024-06-27  7:57             ` Peter Seiderer via buildroot
2024-06-27  8:26             ` Peter Seiderer via buildroot
2024-06-27 11:16               ` yann.morin
2024-07-02 12:47                 ` Peter Seiderer via buildroot
2024-06-24 13:41 ` [Buildroot] [PATCH v2 1/5] package/xz: bump version to 5.4.7 Arnout Vandecappelle via buildroot
2024-07-08 10:04   ` Peter Korsgaard
2024-07-08 12:54     ` Peter Seiderer via buildroot [this message]
2024-07-08 12:57       ` Peter Seiderer via buildroot

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=20240708145436.55ec576f@gmx.net \
    --to=buildroot@buildroot.org \
    --cc=buildroot@busybox.net \
    --cc=peter@korsgaard.com \
    --cc=ps.report@gmx.net \
    /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