unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Alex Kost <alezost@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Timestamps in ...-autoloads.el files
Date: Tue, 17 May 2016 11:12:53 +0200	[thread overview]
Message-ID: <874m9xujxm.fsf@gnu.org> (raw)
In-Reply-To: <87oa85pvy4.fsf@gmail.com> (Alex Kost's message of "Mon, 16 May 2016 23:52:19 +0300")

Alex Kost <alezost@gmail.com> skribis:

> Ludovic Courtès (2016-05-16 15:45 +0300) wrote:
>
>> Alex Kost <alezost@gmail.com> skribis:
> [...]
>>> I looked at the compiled "autoload.elc" file and if I understood it
>>> correctly, it was compiled using the unpatched version of "autoload.el"
>>> (because there is no mention of SOURCE_DATE_EPOCH there).
>>
>> Indeed.
>>
>>> But I don't understand how it could happen since patching is performed
>>> before building.  Any ideas?
>>
>> I think I have one:
>>
>> $ git describe
>> v0.10.0-798-g8a7680a
>> $ tar tvf $(./pre-inst-env guix build -S emacs) |grep 'autoload\.el'
>> -rw-r--r-- root/root     37292 1970-01-01 01:00 emacs-24.5/lisp/emacs-lisp/autoload.el
>> -rw-r--r-- root/root     37127 1970-01-01 01:00 emacs-24.5/lisp/emacs-lisp/autoload.el.orig
>> -rw-r--r-- root/root     22624 1970-01-01 01:00 emacs-24.5/lisp/emacs-lisp/autoload.elc
>>
>> Upstream’s tarball already includes those three files.
>
> IIUC this source is after applying our patches (including
> "emacs-source-date-epoch.patch"):
>
> - “autoload.el.orig” is the original file from the upstream;

Indeed, this one isn’t present in upstream’s tarball:

--8<---------------cut here---------------start------------->8---
$ wget -q -O - ftp://ftp.gnu.org/gnu/emacs/emacs-24.5.tar.xz | tar tJvf - | grep 'autoload\.'
-rw-rw-r-- nico/nico     37127 2015-04-02 09:23 emacs-24.5/lisp/emacs-lisp/autoload.el
-rw-r--r-- nico/nico     22624 2015-04-08 19:16 emacs-24.5/lisp/emacs-lisp/autoload.elc
--8<---------------cut here---------------end--------------->8---

How come we’re introducing this one?  I thought ‘patch’ did not produce
.orig files unless the patch failed to apply, but here the patch
correctly applies, only with a small offset (can be seen by running
‘guix build -S emacs --check’):

--8<---------------cut here---------------start------------->8---
patching file lisp/loadup.el
patching file lisp/emacs-lisp/autoload.el
Hunk #1 succeeded at 361 (offset -17 lines).
--8<---------------cut here---------------end--------------->8---

Apparently we have to use ‘--no-backup-if-mismatch’ to avoid that.

> Thanks, the mystery is solved now.  This is an unpleasant surprise, I
> didn't know that emacs release comes with the compiled files.

Yeah.  :-/

Ludo’.

  reply	other threads:[~2016-05-17  9:13 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-19 23:09 Challenge substitute servers! Ludovic Courtès
2015-10-20  0:17 ` Daniel Pimentel
2015-10-20 14:38 ` [PATCHES] emacs: Changes for 'guix challenge' Alex Kost
2015-10-20 14:58   ` Ludovic Courtès
2015-10-20 17:40 ` Timestamps in ...-autoloads.el files Alex Kost
2015-10-20 19:38   ` Ludovic Courtès
2015-10-21 13:05     ` Alex Kost
2015-10-21 16:55       ` Ludovic Courtès
2015-11-02 16:50         ` Alex Kost
2015-11-03 13:27           ` Ludovic Courtès
2015-11-14 11:32             ` Alex Kost
2015-11-14 15:03               ` Ludovic Courtès
2015-11-14 20:39                 ` Alex Kost
2016-05-11 14:53         ` Alex Kost
2016-05-16 12:45           ` Ludovic Courtès
2016-05-16 20:52             ` Alex Kost
2016-05-17  9:12               ` Ludovic Courtès [this message]
2016-05-19 16:29                 ` Alex Kost
2016-05-20 12:02                   ` Ludovic Courtès
2016-05-20 13:38                     ` Leo Famulari
2016-05-21 10:49                       ` Alex Kost
2016-05-21 21:02                         ` Ludovic Courtès
2016-05-24  9:07                           ` Alex Kost
2016-05-20 21:14                     ` Alex Kost
2016-05-19  8:12             ` Alex Kost
2016-05-19 12:56               ` Ludovic Courtès
2016-05-21 10:31                 ` Alex Kost
2016-05-21 21:01                   ` Ludovic Courtès
2016-05-24  9:00                     ` Alex Kost

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=874m9xujxm.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=alezost@gmail.com \
    --cc=guix-devel@gnu.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).