From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Oleg Lyovin <ovlevin@sberdevices.ru>
Cc: olegartys@gmail.com, sdfw_system_team@sberdevices.ru,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] package/libcgroup: bump to version 2.0.3
Date: Sun, 25 Jun 2023 15:56:00 +0200 [thread overview]
Message-ID: <20230625135600.GD589277@scaer> (raw)
In-Reply-To: <20230625124848.1423168-1-ovlevin@sberdevices.ru>
Oleg, All,
On 2023-06-25 15:48 +0300, Oleg Lyovin via buildroot spake thusly:
> https://github.com/libcgroup/libcgroup/releases/tag/v2.0.3
>
> Also remove redundant LIBCGROUP_SOURCE definition.
it is not redundant: it downloads the bz2-compressed archive instead of
the default gz-compressed one.
I'm OK for switching (the package is small), but the commit log is
incorrect.
Regards,
Yann E. MORIN.
> Signed-off-by: Oleg Lyovin <ovlevin@sberdevices.ru>
> ---
> package/libcgroup/libcgroup.hash | 4 ++--
> package/libcgroup/libcgroup.mk | 3 +--
> 2 files changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/package/libcgroup/libcgroup.hash b/package/libcgroup/libcgroup.hash
> index 70671212ef..65b98d94e2 100644
> --- a/package/libcgroup/libcgroup.hash
> +++ b/package/libcgroup/libcgroup.hash
> @@ -1,5 +1,5 @@
> -# From https://github.com/libcgroup/libcgroup/releases/download/v0.42.2/libcgroup-0.42.2.tar.bz2.sha256
> -sha256 18939381324d418e11be4f5fdca37b01652c18917bfaf1f6b0c505f157e18d07 libcgroup-0.42.2.tar.bz2
> +# From https://github.com/libcgroup/libcgroup/releases/download/v2.0.3/libcgroup-2.0.3.tar.gz.sha256
> +sha256 b29b5704de3d0fadf199fe4e17eeeaecba7f0dd1b85569c96eec37c7672e3026 libcgroup-2.0.3.tar.gz
>
> # Hash for license file
> sha256 a9bdde5616ecdd1e980b44f360600ee8783b1f99b8cc83a2beb163a0a390e861 COPYING
> diff --git a/package/libcgroup/libcgroup.mk b/package/libcgroup/libcgroup.mk
> index 156b066162..fb0b646c51 100644
> --- a/package/libcgroup/libcgroup.mk
> +++ b/package/libcgroup/libcgroup.mk
> @@ -4,8 +4,7 @@
> #
> ################################################################################
>
> -LIBCGROUP_VERSION = 0.42.2
> -LIBCGROUP_SOURCE = libcgroup-$(LIBCGROUP_VERSION).tar.bz2
> +LIBCGROUP_VERSION = 2.0.3
> LIBCGROUP_SITE = https://github.com/libcgroup/libcgroup/releases/download/v$(LIBCGROUP_VERSION)
> LIBCGROUP_LICENSE = LGPL-2.1
> LIBCGROUP_LICENSE_FILES = COPYING
> --
> 2.34.1
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-06-25 13:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-25 12:48 [Buildroot] [PATCH 1/2] package/libcgroup: bump to version 2.0.3 Oleg Lyovin via buildroot
2023-06-25 12:48 ` [Buildroot] [PATCH 2/2] package/libcgroup: fix build with musl Oleg Lyovin via buildroot
2023-06-25 13:11 ` Arnout Vandecappelle via buildroot
2023-06-25 13:15 ` Yann E. MORIN
2023-06-25 16:51 ` [Buildroot] [PATCH v2] package/libcgroup: allow to " Oleg Lyovin via buildroot
2023-06-25 19:37 ` Arnout Vandecappelle via buildroot
2023-06-25 13:53 ` [Buildroot] [PATCH 1/2] package/libcgroup: bump to version 2.0.3 Arnout Vandecappelle via buildroot
2023-06-25 13:56 ` Yann E. MORIN [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=20230625135600.GD589277@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=olegartys@gmail.com \
--cc=ovlevin@sberdevices.ru \
--cc=sdfw_system_team@sberdevices.ru \
/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