From: Lars-Dominik Braun <lars@6xq.net>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Cabal mismatch in ghc-lucid; long-term archiving Haskell?
Date: Sat, 20 Aug 2022 18:47:50 +0200 [thread overview]
Message-ID: <YwEQNu5mfUuIozWH@noor.fritz.box> (raw)
In-Reply-To: <86v8qnxmfh.fsf@gmail.com>
Hi zimoun,
> Is it a manual in-place replacement? Or is it an automatic in-place
> update by Hackage infrastructure? Or do I miss a point?
>
> In all cases, these revised Cabal files are not archived elsewhere than
> in Hackage, right? The question is thus, where could we archive them?
>
> Note that the both items have the same store-address hash
> (/gnu/store/rj33x41i86vgw6c0iwffzwrgzrib1shb-ghc-lucid-2.9.12.1-1.cabal)
> but not the same content hash.
fear not, this is a mistake on our side – mine in particular. `git
blame` indicates the package was updated in my last big Haskell bump as
commit b97f549b14402421fcfb360ddd4cff7de93b9af0. And while I updated the
version number, I did not touch #:cabal-revision, which is obviously a
mistake. Unfortunately we chose to encode this information into arguments
and not the version and so this happens (alot), because – alas –
`guix refresh` touches the version only, but not #:cabal-revision.
As for Haskell/Hackage/Stackage: All of their .cabal files are versioned
and never overwritten. I think they also keep them permanently.
Cheers,
Lars
next prev parent reply other threads:[~2022-08-20 16:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-20 10:02 Cabal mismatch in ghc-lucid; long-term archiving Haskell? zimoun
2022-08-20 16:47 ` Lars-Dominik Braun [this message]
2022-08-22 14:04 ` zimoun
2022-08-23 13:34 ` Lars-Dominik Braun
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=YwEQNu5mfUuIozWH@noor.fritz.box \
--to=lars@6xq.net \
--cc=guix-devel@gnu.org \
--cc=zimon.toutoune@gmail.com \
/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).