From: Jaft <jaft.r@outlook.com>
To: "54311@debbugs.gnu.org" <54311@debbugs.gnu.org>,
Maxime Devos <maximedevos@telenet.be>
Subject: [bug#54311] [PATCH] gnu: tint2: Update to 17.0.2.
Date: Wed, 9 Mar 2022 21:46:27 +0000 (UTC) [thread overview]
Message-ID: <DM5PR04MB3772B411BBFE6999387EEAD0990A9@DM5PR04MB3772.namprd04.prod.outlook.com> (raw)
In-Reply-To: <c951a42207af6fdc2043783a5a77bed9e85407a5.camel@telenet.be>
> On Wednesday, March 9, 2022, 02:30:14 PM CST, Maxime Devos <maximedevos@telenet.be> wrote:
>
>
>
>
>
> Wamm K. D schreef op wo 09-03-2022 om 13:34 [-0600]:
>
> > + (uri (string-append "https://gitlab.com/o9000/" name "/-/archive/"
> > + version "/" name "-" version ".tar.gz"))
>
>
> Is this uri stable?
I think it's a standard GitLab URL? It's what was given when choosing to download the .tar.gz file from GitLab; I went with it to avoid a lot of changes to the original package definition but, given it's just Git, we could just use a git-download instead. Let me know if that's preferred.
> Also, there seems to be a 'v' missing before version. Does
> "guix download
> https://gitlab.com/o9000/tint2/-/archive/17.0.2/tint2-17.0.2.tar.gz"
> succeed?
It does (I'm running version 17.0.2 on my machine, right now); the tint2 project tags versions with both no "v" and with a "v" so either would work. Both "https://gitlab.com/o9000/tint2/-/archive/17.0.2/tint2-17.0.2.tar.gz" and "https://gitlab.com/o9000/tint2/-/archive/v17.0.2/tint2-v17.0.2.tar.gz" should be valid (https://gitlab.com/o9000/tint2/-/tags).
next prev parent reply other threads:[~2022-03-09 21:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 19:34 [bug#54311] [PATCH] gnu: tint2: Update to 17.0.2 Wamm K. D
2022-03-09 20:28 ` Maxime Devos
2022-03-09 20:30 ` Maxime Devos
2022-03-09 21:46 ` Jaft [this message]
2022-03-09 21:57 ` Tobias Geerinckx-Rice via Guix-patches via
2022-03-09 22:16 ` Jaft
2022-03-09 20:31 ` Maxime Devos
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=DM5PR04MB3772B411BBFE6999387EEAD0990A9@DM5PR04MB3772.namprd04.prod.outlook.com \
--to=jaft.r@outlook.com \
--cc=54311@debbugs.gnu.org \
--cc=maximedevos@telenet.be \
/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).