From: Marius Bakke <mbakke@fastmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 26356@debbugs.gnu.org
Subject: bug#26356: [PATCH] gnu: Add intel-gpu-tools.
Date: Tue, 04 Apr 2017 22:45:57 +0200 [thread overview]
Message-ID: <8737dnc35m.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <8737dmoacq.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 1117 bytes --]
Ricardo Wurmus <rekado@elephly.net> writes:
> Marius Bakke <mbakke@fastmail.com> writes:
>
>>> +(define-public intel-gpu-tools
>>> + (package
>>> + (name "intel-gpu-tools")
>>> + (version "1.18")
>>> + (source
>>> + (origin (method git-fetch)
>>> + (uri (git-reference
>>> + (url "https://anongit.freedesktop.org/git/xorg/app/intel-gpu-tools.git")
>>> + (commit (string-append name "-" version))))
>>
>> I managed to get a tarball by constructing this URL:
>>
>> https://cgit.freedesktop.org/xorg/app/intel-gpu-tools/snapshot/intel-gpu-tools-1.18.tar.gz
>
> Aren’t these tarballs generated on demand and may thus have different
> embedded timestamps?
I've come across very few servers that do this (actually only the Google
Android repositories). At least, the tarball downloaded earlier and one
from just now have the same SHA256:
03ff3cc2d8009e821a07c83a1ed44fdcb0d27e1a958d15ec87e6f0e2c194ed70 intel-gpu-tools-1.18(1).tar.gz
03ff3cc2d8009e821a07c83a1ed44fdcb0d27e1a958d15ec87e6f0e2c194ed70 intel-gpu-tools-1.18.tar.gz
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2017-04-04 20:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-04 7:15 bug#26356: [PATCH] gnu: Add intel-gpu-tools Ricardo Wurmus
2017-04-04 15:28 ` Marius Bakke
2017-04-05 20:41 ` Ricardo Wurmus
2017-04-04 20:45 ` Marius Bakke [this message]
2017-04-04 21:03 ` Ricardo Wurmus
2017-04-07 21:23 ` Ricardo Wurmus
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=8737dnc35m.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me \
--to=mbakke@fastmail.com \
--cc=26356@debbugs.gnu.org \
--cc=rekado@elephly.net \
/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).