unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: iyzsong@member.fsf.org (宋文武)
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 0/5] Sphinx reproducibility update
Date: Sat, 02 Jul 2016 21:07:32 +0800	[thread overview]
Message-ID: <8737ns194b.fsf@member.fsf.org> (raw)
In-Reply-To: <cover.1467421110.git.leo@famulari.name> (Leo Famulari's message of "Fri, 1 Jul 2016 21:04:48 -0400")

Leo Famulari <leo@famulari.name> writes:
> [...]
>
> With this change, many Python 2 packages will become reproducible, at
> least on a single machine; the only thing holding them back was the
> manpage timestamps.
Cool!

>
> These changes will require 142 rebuilds, mostly of Python packages, but
> also of libreoffice (libreoffice seems to depend on *everything*) and a
> few others. If the patches are good, should they go to master or to
> another branch?
>
I prefer master, and I guess people who use libreoffice don't update it
frequently (we have a old version, but no one complain so far).

  parent reply	other threads:[~2016-07-02 13:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-02  1:04 [PATCH 0/5] Sphinx reproducibility update Leo Famulari
2016-07-02  1:04 ` [PATCH 1/5] gnu: Add python-imagesize Leo Famulari
2016-07-03 21:54   ` Ludovic Courtès
2016-07-02  1:04 ` [PATCH 2/5] gnu: Add python-alabaster Leo Famulari
2016-07-03 21:55   ` Ludovic Courtès
2016-07-02  1:04 ` [PATCH 3/5] gnu: Add python-snowballstemmer Leo Famulari
2016-07-02 12:55   ` 宋文武
2016-07-02  1:04 ` [PATCH 4/5] gnu: python-sphinx: Update to 1.4.4 Leo Famulari
2016-07-03 21:57   ` Ludovic Courtès
2016-07-02  1:04 ` [PATCH 5/5] gnu: python-sphinx-rtd-theme: Update to 0.1.9 Leo Famulari
2016-07-03 21:57   ` Ludovic Courtès
2016-07-02 13:07 ` 宋文武 [this message]
2016-07-03 21:54   ` [PATCH 0/5] Sphinx reproducibility update Ludovic Courtès
2016-07-04  2:25     ` Leo Famulari
2016-07-03 21:52 ` Ludovic Courtès

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=8737ns194b.fsf@member.fsf.org \
    --to=iyzsong@member.fsf.org \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    /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).