From: ng0 <ng0@pragmatique.xyz>
To: guix-devel@gnu.org
Subject: github tarballs problematic?
Date: Thu, 8 Jun 2017 20:35:28 +0000 [thread overview]
Message-ID: <20170608203528.rvp4lhdqu463ns2x@abyayala> (raw)
I've just come across this post via https://pagure.io/pagure/issue/861
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/UDZ2WKMTOE6J2M4K7PF5OWSSC4BAX2SH/
quote in almost full:
today, I've accidentally attested there are no stability guarantees with the on-demand archives from common git hosting sites when preparing a new pacemaker update, redownloading "spectool -s 0 pacemaker.spec" of the original (-0.1.rc1, from 2 weeks ago) spec and comparing the hashes, which (surprisingly to me) didn't match (they were at any similar test in the past). Then I looked at the adiff output:
...
diff -ru Unpack-2241/pacemaker-Pacemaker-1.1.17-rc1/configure.ac
Unpack-6255/pacemaker-Pacemaker-1.1.17-rc1/configure.ac
--- Unpack-2241/pacemaker-Pacemaker-1.1.17-rc1/configure.ac2017-05-09 00:55:15.000000000
+0200
+++ Unpack-6255/pacemaker-Pacemaker-1.1.17-rc1/configure.ac2017-05-09 00:55:15.000000000
+0200
@@ -1159,7 +1159,7 @@
AC_PATH_PROGS(GIT, git false)
AC_MSG_CHECKING(build version)
-BUILD_VERSION=0459f40
+BUILD_VERSION=0459f40958
if test != ":%h$"; then
AC_MSG_RESULT(archive hash: )
for configure.ac that indeed has export-subst git attribute set and the change itself arises from "$Format:%h$" substitution. This likely means GitHub was internally updated to use equivalent of git 2.11 feature of abbreviation length autoscaling within last 14 days. Hope this will be useful for some (e.g. fedora-review tool has a check to redownload and diff sources against SRPM content, IIRC).
--
ng0
OpenPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588
next reply other threads:[~2017-06-08 20:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-08 20:35 ng0 [this message]
2017-06-09 13:53 ` github tarballs problematic? Ludovic Courtès
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=20170608203528.rvp4lhdqu463ns2x@abyayala \
--to=ng0@pragmatique.xyz \
--cc=guix-devel@gnu.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 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).