From: 郑俊杰 <zhengjunjie@yandex.com>
To: Hilton Chain <hako@ultrarare.space>
Cc: 67903@debbugs.gnu.org, Tobias Geerinckx-Rice <me@tobias.gr>,
Leo Famulari <leo@famulari.name>
Subject: [bug#67903] [PATCH] gnu: libcgroup: Update to 3.1.0.
Date: Sun, 24 Dec 2023 13:27:13 +0800 [thread overview]
Message-ID: <1801D85C-6E02-44E8-91B8-C5EF79DD6173@yandex.com> (raw)
In-Reply-To: <696e1a46af20d62029c36f5e2ad2c2ff22c0485f.1702995464.git.hako@ultrarare.space>
> 在 2023年12月19日,22:51,Hilton Chain via Guix-patches via <guix-patches@gnu.org> 写道:
>
> * gnu/packages/linux.scm (libcgroup): Update to 3.1.0.
> [arguments]<#:configure-flags>: Disable systemd.
>
> Change-Id: I67fe380ebdf91ca254b3365b7f237a3d9ad4f0a5
> ---
> gnu/packages/linux.scm | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/gnu/packages/linux.scm b/gnu/packages/linux.scm
> index 3ca756dead..c4c366e21f 100644
> --- a/gnu/packages/linux.scm
> +++ b/gnu/packages/linux.scm
> @@ -8798,7 +8798,7 @@ (define-public fbgrab
> (define-public libcgroup
> (package
> (name "libcgroup")
> - (version "2.0.2")
> + (version "3.1.0")
> (home-page "https://github.com/libcgroup/libcgroup")
> (source
> (origin
> @@ -8806,14 +8806,15 @@ (define-public libcgroup
> (uri (string-append home-page "/releases/download/v"
> version "/" name "-" version ".tar.gz"))
Can we switch to git-fetch?
And don’t use home-page in source.
> (sha256
> - (base32 "1y0c9ncsawamj77raiw6qkbm5cdsyvhjb2mvgma1kxmgw0r3pxlf"))))
> + (base32 "0n0jkvmagw14vgwx3j5b6vv5h25lasrg2a7xihq9h11ww2qw8vlp"))))
> (build-system gnu-build-system)
> (arguments
> ;; Tests are virtualized with lxc, it is not very feasible
> ;; to make them executable under guix build. Also, note that
> ;; origin is using source tarball release which is prepared
> ;; after testing.
> - `(#:tests? #f))
> + `(#:tests? #f
> + #:configure-flags '("--disable-systemd")))
Maybe use gexp.
> (native-inputs
> (list bison flex))
> (inputs
>
> base-commit: fa92a7c2fe0c5b9e9923ad5f53bafd41aa6dbe66
> --
> 2.41.0
Other LGTM
>
>
>
>
next prev parent reply other threads:[~2023-12-24 5:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 14:21 [bug#67903] [PATCH] gnu: libcgroup: Update to 3.1.0 Hilton Chain via Guix-patches via
2023-12-24 5:27 ` 郑俊杰 [this message]
2024-01-05 5:24 ` Hilton Chain via Guix-patches via
2024-01-05 5:45 ` Zheng Junjie
2024-01-13 8:04 ` Hilton Chain via Guix-patches via
2024-01-13 8:08 ` [bug#67903] [PATCH v2 1/2] gnu: libcgroup: Adjust package style Hilton Chain via Guix-patches via
2024-01-13 8:08 ` [bug#67903] [PATCH v2 2/2] gnu: libcgroup: Update to 3.1.0 Hilton Chain via Guix-patches via
2024-01-25 16:37 ` bug#67903: " Hilton Chain via Guix-patches via
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1801D85C-6E02-44E8-91B8-C5EF79DD6173@yandex.com \
--to=zhengjunjie@yandex.com \
--cc=67903@debbugs.gnu.org \
--cc=hako@ultrarare.space \
--cc=leo@famulari.name \
--cc=me@tobias.gr \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).