From: Leo Famulari <leo@famulari.name>
To: Troy Sankey <sankeytms@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: update khal
Date: Mon, 29 Aug 2016 18:45:29 -0400 [thread overview]
Message-ID: <20160829224529.GA32742@jasmine> (raw)
In-Reply-To: <147244156826.23966.1730589020629061788@what>
[-- Attachment #1: Type: text/plain, Size: 1290 bytes --]
On Sun, Aug 28, 2016 at 11:32:48PM -0400, Troy Sankey wrote:
> Builds don't seem to be deterministic when I use --check. Not sure where to
> start looking in order to fix that.
I use the diffoscope program to inspect the differences.
Currently, all of our Python 3 packages embed timestamps in the Python
bytecode [0], and our Sphinx also embeds timestamps in man pages [1].
So, you should at least see these differences.
[0]
https://bugs.gnu.org/22533
[1] I am trying to update the whole set of core Python packages on the
wip-python branch. This will fix the Sphinx problem. I took a little
time off from this, but I'm going to dive back in soon. Feel free to
jump in!
> From 2538d47347ea2ca04eb116e762e3bf4dec575d31 Mon Sep 17 00:00:00 2001
> From: Troy Sankey <sankeytms@gmail.com>
> Date: Sun, 14 Aug 2016 13:38:20 -0400
> Subject: [PATCH 1/3] gnu: Add python-freezegun.
>
> * gnu/packages/python.scm (python-freezegun): New variable.
> (python2-freezegun): New variable.
> Subject: [PATCH 2/3] gnu: python-icalendar: Update to 3.10.
>
> * gnu/packages/python.scm (python-icalendar): Update to 3.10.
> Subject: [PATCH 3/3] gnu: khal: Update to 0.8.3.
>
> * gnu/packages/calendar.scm (khal): Update to 0.8.3.
Thanks, pushed as bc8273d0c!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-08-29 22:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-29 3:32 update khal Troy Sankey
2016-08-29 22:45 ` Leo Famulari [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=20160829224529.GA32742@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=sankeytms@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).