From: "宋文武 via Guix-patches via" <guix-patches@gnu.org>
To: "(" <paren@disroot.org>
Cc: muradm <mail@muradm.net>, 56858@debbugs.gnu.org
Subject: [bug#56858] [PATCH] gnu: libcgroup: Update to 2.0.2.
Date: Thu, 04 Aug 2022 13:55:57 +0800 [thread overview]
Message-ID: <87wnbor1qq.fsf_-_@envs.net> (raw)
In-Reply-To: <CLU67OBRAQZT.1OBE6IVC4Z349@guix-aspire> (paren@disroot.org's message of "Sun, 31 Jul 2022 22:48:20 +0100")
"(" <paren@disroot.org> writes:
> Hi!
>
> On Sun Jul 31, 2022 at 4:29 PM BST, muradm wrote:
>> + (home-page "https://github.com/libcgroup/libcgroup")
> Put home-page under inputs and above synopsis, where it was before.
>
>> (method url-fetch)
>> - (uri (string-append
>> - "mirror://sourceforge/libcg/" name "/"
>> - version "/" name "-" version ".tar.bz2"))
>> + (uri (string-append home-page "/releases/download/v"
>> + version "/" name "-" version ".tar.gz"))
> Since we're using github now, we likely want to use git-fetch here.
> I've been told Github releases are volatile.
Hello, I believe '/releases' are okay, since they are uploaded manual by
the owner, the unstable ones are under '/archive' which are
auto-generated tarballs for tags.
prev parent reply other threads:[~2022-08-04 5:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-31 15:29 [bug#56858] [PATCH] gnu: libcgroup: Update to 2.0.2 muradm
2022-07-31 21:48 ` ( via Guix-patches via
2022-08-01 5:42 ` muradm
2022-08-01 9:02 ` ( via Guix-patches via
2022-08-01 9:06 ` ( via Guix-patches via
2022-08-01 13:13 ` muradm
2022-08-09 15:37 ` Ludovic Courtès
2022-08-09 20:29 ` muradm
2022-08-23 21:10 ` [bug#56858] [PATCH v2] " muradm
2022-08-31 10:38 ` bug#56858: " Ludovic Courtès
2022-08-04 5:55 ` 宋文武 via Guix-patches via [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=87wnbor1qq.fsf_-_@envs.net \
--to=guix-patches@gnu.org \
--cc=56858@debbugs.gnu.org \
--cc=iyzsong@envs.net \
--cc=mail@muradm.net \
--cc=paren@disroot.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.