all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: Antero Mejr <antero@mailbox.org>, 55606@debbugs.gnu.org
Cc: paren@disroot.org, me@tobias.gr, liliana.prikler@gmail.com
Subject: [bug#55606] [PATCH 2/2] gnu: Add hare.
Date: Sun, 26 Jun 2022 16:20:30 +0200	[thread overview]
Message-ID: <fbc53bfbf6c5aa3f4c815f20b889e19ec7b0765d.camel@telenet.be> (raw)
In-Reply-To: <20220626135940.10504-2-antero@mailbox.org>

[-- Attachment #1: Type: text/plain, Size: 926 bytes --]

Antero Mejr schreef op zo 26-06-2022 om 09:59 [-0400]:
> +      (inputs (list tzdata))

What's this input for?  Packages shouldn't have tzdata in their inputs,
because it's a bunch of facts about the external world.  When doing
this, running hare's equivalent of `date` from an old profile would
give a bogus result because of out-of-date time zone info.

Also, the rebuilding problem, from (gnu packages base):

;;; A "fixed" version of tzdata, which is used in the test suites of glib and R
;;; and a few other places. We can update this whenever we are able to rebuild
;;; thousands of packages (for example, in a core-updates rebuild). This package
;;; will typically be obsolete and should never be referred to by a built
;;; package.
;;;
;;; Please make this a hidden-package if it is different from the primary tzdata
;;; package.
(define-public tzdata-for-tests tzdata)

Greetings,
Maxime.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  reply	other threads:[~2022-06-26 14:21 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-24  1:21 [bug#55605] [PATCH 1/2] gnu: Add qbe Antero Mejr via Guix-patches via
2022-05-24  1:21 ` [bug#55606] [PATCH 2/2] gnu: Add hare Antero Mejr via Guix-patches via
2022-05-24 17:01   ` Maxime Devos
2022-05-24 17:07   ` Maxime Devos
2022-05-24 17:09   ` Maxime Devos
2022-05-24 17:10   ` Tobias Geerinckx-Rice via Guix-patches via
2022-05-29  0:54   ` [bug#55606] [PATCH] " Antero Mejr via Guix-patches via
2022-06-03 17:54   ` [bug#55606] Antero Mejr via Guix-patches via
2022-06-25 16:54     ` [bug#55606] [PATCH 2/2] gnu: Add hare Liliana Marie Prikler
2022-06-25 17:53       ` ( via Guix-patches via
2022-06-26  4:56         ` Antero Mejr via Guix-patches via
2022-06-25 17:59       ` ( via Guix-patches via
2022-06-26  4:40         ` Antero Mejr via Guix-patches via
2022-06-26  7:30           ` Maxime Devos
2022-06-26  7:34           ` Maxime Devos
2022-06-26 10:58           ` ( via Guix-patches via
2022-06-26 14:07             ` Antero Mejr via Guix-patches via
2022-06-26 14:27               ` Maxime Devos
2022-06-26 14:39                 ` Antero Mejr via Guix-patches via
2022-07-24 16:10               ` ( via Guix-patches via
2022-06-25 21:32       ` Antero Mejr via Guix-patches via
2022-06-26  4:39   ` [bug#55606] [PATCH 1/2] gnu: Add harec Antero Mejr via Guix-patches via
2022-06-26  4:39     ` [bug#55606] [PATCH 2/2] gnu: Add hare Antero Mejr via Guix-patches via
2022-06-26  7:18       ` Liliana Marie Prikler
2022-06-26 11:05         ` ( via Guix-patches via
2022-06-26 14:00         ` Antero Mejr via Guix-patches via
2022-06-26  6:50     ` [bug#55606] [PATCH 1/2] gnu: Add harec Liliana Marie Prikler
2022-06-26 13:59   ` Antero Mejr via Guix-patches via
2022-06-26 13:59     ` [bug#55606] [PATCH 2/2] gnu: Add hare Antero Mejr via Guix-patches via
2022-06-26 14:20       ` Maxime Devos [this message]
2022-06-26 14:30         ` Antero Mejr via Guix-patches via
2022-06-26 14:39           ` Maxime Devos
2022-06-26 14:22       ` Maxime Devos
2022-06-26 14:33         ` Antero Mejr via Guix-patches via
2022-06-26 14:44           ` Maxime Devos
2022-06-26 14:53             ` Maxime Devos
2022-05-24 16:56 ` [bug#55605] [PATCH 1/2] gnu: Add qbe Maxime Devos
2022-05-24 21:06 ` Maxime Devos

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=fbc53bfbf6c5aa3f4c815f20b889e19ec7b0765d.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=55606@debbugs.gnu.org \
    --cc=antero@mailbox.org \
    --cc=liliana.prikler@gmail.com \
    --cc=me@tobias.gr \
    --cc=paren@disroot.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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.