From: Leo Famulari <leo@famulari.name>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 27567@debbugs.gnu.org
Subject: bug#27567: [PATCH v2] gnu: netpbm: Remove timestamps.
Date: Tue, 4 Jul 2017 15:04:42 -0400 [thread overview]
Message-ID: <20170704190442.GB30345@jasmine.lan> (raw)
In-Reply-To: <20170703191638.26462-1-dannym@scratchpost.org>
[-- Attachment #1: Type: text/plain, Size: 997 bytes --]
On Mon, Jul 03, 2017 at 09:16:38PM +0200, Danny Milosavljevic wrote:
> * gnu/packages/netpbm.scm (netpbm)[source]: Remove timestamps.
> ---
> gnu/packages/netpbm.scm | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/gnu/packages/netpbm.scm b/gnu/packages/netpbm.scm
> index cd0c3d950..652c23aed 100644
> --- a/gnu/packages/netpbm.scm
> +++ b/gnu/packages/netpbm.scm
> @@ -87,6 +87,9 @@
> (drop "ppmtopjxl" in "converter/ppm")
>
> ;; Remove timestamps from the generated code.
> + (substitute* "buildtools/makepointerman"
> + (("gmctime[(][)]")
> + "\"Thu Jan 1 00:00:00 1970\""))
I'm not sure what's going on with core-updates: the last evaluation was
aborted.
So, assuming that you can build groff on core-updates with this change
before Hydra builds netpbm on core-updates, LGTM. Once we build
core-updates to that point, we should wait for the next core-updates
cycle.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-07-04 19:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-03 19:04 bug#27567: netpbm is not reproducible Danny Milosavljevic
2017-07-03 19:08 ` bug#27567: [PATCH] gnu: netpbm: Add "patch-timestamps" phase Danny Milosavljevic
2017-07-04 19:01 ` Leo Famulari
2017-07-04 19:04 ` Danny Milosavljevic
2017-07-03 19:16 ` bug#27567: [PATCH v2] gnu: netpbm: Remove timestamps Danny Milosavljevic
2017-07-04 19:04 ` 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=20170704190442.GB30345@jasmine.lan \
--to=leo@famulari.name \
--cc=27567@debbugs.gnu.org \
--cc=dannym@scratchpost.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 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).