From: zimoun <zimon.toutoune@gmail.com>
To: Guix Devel <guix-devel@gnu.org>
Subject: Re: Why unrelated package trigger rebuild?
Date: Fri, 09 Oct 2020 18:26:01 +0200 [thread overview]
Message-ID: <86ft6n2wo6.fsf@gmail.com> (raw)
Hi Chris,
I have investigate a bit.
On Fri, 9 Oct 2020 at 09:52, Christopher Baines <mail@cbaines.net> wrote:
> > <https://data.guix.gnu.org/repository/1/branch/master/package/ghc-haddock/output-history>
The webpage reads, anti-chronological order:
j5llsz…-ghc-haddock-2.22.0 392220 1a2759
s7s3ks…-ghc-haddock-2.22.0 20cc8f 20cc8f
lw2qzd…-ghc-haddock-2.22.0 8ab70b c1f385
where the log is:
--8<---------------cut here---------------start------------->8---
$ git --no-pager guix log --oneline 20cc8f9487^^..3922208091
3922208091 gnu: Add dkgpg.
d51cb7f85f gnu: Add libtmcg.
[...]
12dc9f58c4 gnu: gcc: Fix libstdc++ misconfiguration.
b1d3c122e1 gnu: gcc@10: Update to 10.2.0.
c1f38577c8 gnu: Add sleef.
548d4d810d gnu: duplicity: Update to 0.8.14.
[...]
e239135c56 gnu: gp2c: Update to 0.0.11pl4.
7cce2a6bd4 Revert "gnu: patchelf: Update to 0.11."
20cc8f9487 gnu: patchelf: Update to 0.11.
dbdfbec957 gnu: git-annex: Update to 8.20200720.1.
--8<---------------cut here---------------end--------------->8---
Well, it is probable that there is a merge and maybe the issue is coming
from that. Or maybe an author vs commit date. WDYT?
What I get is:
--8<---------------cut here---------------start------------->8---
3922208091 /gnu/store/j5llszq1cf12qn79bvhc042wc06ibfix-ghc-haddock-2.22.0
d51cb7f85f /gnu/store/j5llszq1cf12qn79bvhc042wc06ibfix-ghc-haddock-2.22.0
12dc9f58c4 /gnu/store/j5llszq1cf12qn79bvhc042wc06ibfix-ghc-haddock-2.22.0
b1d3c122e1 /gnu/store/lw2qzdrx5sq9qrpdszx4fby05bbdhi5f-ghc-haddock-2.22.0
c1f38577c8 /gnu/store/lw2qzdrx5sq9qrpdszx4fby05bbdhi5f-ghc-haddock-2.22.0
548d4d810d /gnu/store/lw2qzdrx5sq9qrpdszx4fby05bbdhi5f-ghc-haddock-2.22.0
e239135c56 /gnu/store/lw2qzdrx5sq9qrpdszx4fby05bbdhi5f-ghc-haddock-2.22.0
7cce2a6bd4 /gnu/store/lw2qzdrx5sq9qrpdszx4fby05bbdhi5f-ghc-haddock-2.22.0
20cc8f9487 /gnu/store/s7s3ksfhkdbb6k6si8bjnxy8vvywv322-ghc-haddock-2.22.0
dbdfbec957 /gnu/store/lw2qzdrx5sq9qrpdszx4fby05bbdhi5f-ghc-haddock-2.22.0
--8<---------------cut here---------------end--------------->8---
Therefore, the first commit producing j5llsz…-ghc-haddock is not
3922208091 but 12dc9f58c4. But what does it mean “first”? :-)
author date commit date
3922208091|Thu Jul 23 14:03:19 2020|Fri Jul 24 14:21:31 2020
12dc9f58c4|Fri Jul 24 09:56:25 2020|Fri Jul 24 14:21:30 2020
However, it seems more expected that
12dc9f58c4 gnu: gcc: Fix libstdc++ misconfiguration.
introduces new hash to ’ghc-haddock’ than unrelated
3922208091 gnu: Add dkgpg.
Maybe a possible fix is to compare “commit date” which will be more
accurate about the change (especially with merges) than “author
date”. WDYT?
The s7s3ks…-ghc-haddock is explained by the revert so it is expected.
All the best,
simon
where the script:
--8<---------------cut here---------------start------------->8---
for ci in 3922208091 \
d51cb7f85f \
12dc9f58c4 \
b1d3c122e1 \
c1f38577c8 \
548d4d810d \
e239135c56 \
7cce2a6bd4 \
20cc8f9487 \
dbdfbec957
do
printf "$ci "
guix time-machine --commit=$ci \
-- build ghc-haddock \
2> /dev/null
done
--8<---------------cut here---------------end--------------->8---
next reply other threads:[~2020-10-09 17:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-09 16:26 zimoun [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-10-09 1:35 Why unrelated package trigger rebuild? zimoun
2020-10-09 7:51 ` Christopher Baines
2020-11-18 8:45 ` zimoun
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=86ft6n2wo6.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=87mu0vzvj6.fsf@cbaines.net \
--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).