unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Guix Devel <guix-devel@gnu.org>
Subject: Re: Why unrelated package trigger rebuild?
Date: Wed, 18 Nov 2020 09:45:01 +0100	[thread overview]
Message-ID: <868sazm4tu.fsf@gmail.com> (raw)
In-Reply-To: <86d01s89lj.fsf@gmail.com>

Hi,

For the interested reader, a quick cross-reference.


On Fri, 09 Oct 2020 at 03:35, zimoun <zimon.toutoune@gmail.com> wrote:

> From the Data Service:
>
> <https://data.guix.gnu.org/repository/1/branch/master/package/ghc-haddock/output-history>
>
> the commit 39222080911eaf3d7f74effe4467c1a04464aef3 which is about the
> addition of the package ’dkgpg’ modifies the hash of the package
> ’ghc-haddock’ from:
>
>   /gnu/store/s7s3ksfhkdbb6k6si8bjnxy8vvywv322-ghc-haddock-2.22.0
>
> to:
>
>   /gnu/store/j5llszq1cf12qn79bvhc042wc06ibfix-ghc-haddock-2.22.0
>
> Well, I miss why the addition of one package changes the hash of another
> unrelated one?  Is it expected?

The correct answer is because the Data Service deals with “state”
message of the mailing list guix-commits.  Where “state” means bunch of
commits pushed in a row.  Therefore, somehow it is expected.  However,
is it the behaviour we want is another question? :-)


Explanations are here:

   <https://yhetil.org/guix-devel/863617oe1h.fsf@gmail.com>

and chat on IRC starting here:

    <http://logs.guix.gnu.org/guix/2020-11-17.log#224837>


All the best,
simon


  parent reply	other threads:[~2020-11-18  9:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-09  1:35 Why unrelated package trigger rebuild? zimoun
2020-10-09  7:51 ` Christopher Baines
2020-11-18  8:45 ` zimoun [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-10-09 16:26 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=868sazm4tu.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --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).