unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Josselin Poiret via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Corvo Liu <lyhokia@gmail.com>, 57867@debbugs.gnu.org
Subject: bug#57867: Tealdeer build fails
Date: Thu, 29 Dec 2022 12:19:23 +0100	[thread overview]
Message-ID: <87cz82o3t0.fsf@jpoiret.xyz> (raw)
In-Reply-To: <CAAtoMVNBAEazmNLMb0PN8EdD1XAmwQAoKJZ_iNb+tGSRkRF8-Q@mail.gmail.com>

Hi Corvo,

Corvo Liu <lyhokia@gmail.com> writes:

> I don't get it. How can a package "used to work" and "fail" now? If that is
> the case, how is guix "declarative"?

Some dependencies might have been updated in the meantime resulting in
build failures.  If you use a Guix commit from back when that package
was building fine, it will still build fine.  Guix being reproducible
doesn't mean that Guix doesn't update any of its packages.

Best,
-- 
Josselin Poiret




      reply	other threads:[~2022-12-29 11:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-16 19:36 bug#57867: Tealdeer build fails Cairn via Bug reports for GNU Guix
2022-09-17 11:55 ` Daniel Sockwell via Bug reports for GNU Guix
2022-09-17 12:46   ` Maxime Devos
2023-01-05 18:00   ` Simon Tournier
2022-12-28  3:53 ` Corvo Liu
2022-12-29 11:19   ` Josselin Poiret via Bug reports for GNU Guix [this message]

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=87cz82o3t0.fsf@jpoiret.xyz \
    --to=bug-guix@gnu.org \
    --cc=57867@debbugs.gnu.org \
    --cc=dev@jpoiret.xyz \
    --cc=lyhokia@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).