From: Peter Seiderer <ps.report@gmx.net>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: Matt Weber <matthew.weber@collins.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] package/ell: bump to version 0.46
Date: Wed, 1 Dec 2021 21:36:59 +0100 [thread overview]
Message-ID: <20211201213659.2bc3b6ed@gmx.net> (raw)
In-Reply-To: <20211201095225.90511-1-james.hilliard1@gmail.com>
Hello James,
thanks for the update, but...
On Wed, 1 Dec 2021 02:52:24 -0700, James Hilliard <james.hilliard1@gmail.com> wrote:
> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
Changelog is a nice to have, see [3] for example...
> ---
> package/ell/ell.hash | 2 +-
> package/ell/ell.mk | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/package/ell/ell.hash b/package/ell/ell.hash
> index 84016c0ce0..20b568dde4 100644
> --- a/package/ell/ell.hash
> +++ b/package/ell/ell.hash
> @@ -1,5 +1,5 @@
> # From https://mirrors.edge.kernel.org/pub/linux/libs/ell/sha256sums.asc
> -sha256 41a6f8fa4d285b52cb7a5a87bda3e7370ecaac02d94aaa7ec1a23f0480b8bc3f ell-0.44.tar.xz
> +sha256 f4fc647eff32f622e21f8851ed0c8b7270f4800149c91be601754e22d82cbb4d ell-0.46.tar.xz
>
> # License files
> sha256 ec60b993835e2c6b79e6d9226345f4e614e686eb57dc13b6420c15a33a8996e5 COPYING
> diff --git a/package/ell/ell.mk b/package/ell/ell.mk
> index 47137e2530..4fad6e8d1b 100644
> --- a/package/ell/ell.mk
> +++ b/package/ell/ell.mk
> @@ -4,7 +4,7 @@
> #
> ################################################################################
>
> -ELL_VERSION = 0.44
> +ELL_VERSION = 0.46
> ELL_SOURCE = ell-$(ELL_VERSION).tar.xz
> ELL_SITE = $(BR2_KERNEL_MIRROR)/linux/libs/ell
> ELL_LICENSE = LGPL-2.1+
At this phase of the buildroot release schedule (see [1] and [2]) version bumps
which are not security related should be done against the next branch, which
will conflict with your patch as there are already ell/iwd version bumps applied
(see [3] and [4])...
[1] https://buildroot.org/downloads/manual/manual.html#RELENG
[2] http://lists.busybox.net/pipermail/buildroot/2021-November/629532.html
[3] https://git.buildroot.net/buildroot/commit/?h=next&id=ab4e346c52b804949c9e2da2e4374654e0abe54d
[4] https://git.buildroot.net/buildroot/commit/?h=next&id=ff0d53405157ce82f6b56c74654c75c07b9ce92d
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2021-12-01 20:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-01 9:52 [Buildroot] [PATCH 1/2] package/ell: bump to version 0.46 James Hilliard
2021-12-01 9:52 ` [Buildroot] [PATCH 2/2] package/iwd: bump to version 1.20 James Hilliard
2021-12-01 20:40 ` Peter Seiderer
2021-12-01 20:36 ` Peter Seiderer [this message]
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=20211201213659.2bc3b6ed@gmx.net \
--to=ps.report@gmx.net \
--cc=buildroot@buildroot.org \
--cc=james.hilliard1@gmail.com \
--cc=matthew.weber@collins.com \
/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.