From: Danny Milosavljevic <dannym@scratchpost.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 31602@debbugs.gnu.org
Subject: bug#31602: libreoffice not reproducible
Date: Wed, 30 May 2018 09:47:15 +0200 [thread overview]
Message-ID: <20180530094715.089a7761@scratchpost.org> (raw)
In-Reply-To: <87bmcywf6j.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1131 bytes --]
Hi Ludo,
On Tue, 29 May 2018 19:21:40 +0200
ludo@gnu.org (Ludovic Courtès) wrote:
> Danny Milosavljevic <dannym@scratchpost.org> skribis:
>
> > These are actually all zip files. The reason for the non-reproducibility is
> > that something copies the contents from the source to a mktemp'ed directory
> > without preserving timestamps. Then this directory is zipped up.
>
> Without *clearing* timestamps?
I think it's something like this:
src/foo.png exists with the source timestamp (which is constant for this version).
Something does mktemp, then copies the src/foo.png there without preserving timestamps.
Then this temp directory is zipped up. Now it has the wrong (different, more current)
timestamps in it.
> Perhaps we could add a phase that unpacks-resets-repacks these? Or,
> alternately, something like the Debian/R-B tool (I forgot the name) that
> does that automatically.
As a fallback - sure.
For now I've been trying to find the place in libreoffice where
it does the copying and patch that and upstream it.
I tried Zip.mk but seems that's not actually used (?).
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-05-30 7:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-26 7:31 bug#31602: libreoffice not reproducible Danny Milosavljevic
2018-05-27 21:38 ` Danny Milosavljevic
2018-05-29 17:21 ` Ludovic Courtès
2018-05-30 7:47 ` Danny Milosavljevic [this message]
2020-07-14 22:13 ` Ludovic Courtès
2020-11-30 20:47 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
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=20180530094715.089a7761@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=31602@debbugs.gnu.org \
--cc=ludo@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).