ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: aycabta@gmail.com
To: ruby-core@ruby-lang.org
Subject: [ruby-core:84805] [Ruby trunk Bug#13627] created.rid prevents reproducible builds
Date: Wed, 10 Jan 2018 09:36:28 +0000 (UTC)	[thread overview]
Message-ID: <redmine.journal-69519.20180110093627.533e0790898ba14a@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-13627.20170603041108@ruby-lang.org

Issue #13627 has been updated by aycabta (aycabta .).


This is adopted at upstream:
https://github.com/ruby/rdoc/pull/570

@hsbt Please close this.

----------------------------------------
Bug #13627: created.rid prevents reproducible builds
https://bugs.ruby-lang.org/issues/13627#change-69519

* Author: bmwiedemann (Bernhard M. Wiedemann)
* Status: Assigned
* Priority: Normal
* Assignee: hsbt (Hiroshi SHIBATA)
* Target version: 
* ruby -v: ruby 2.2.6p396 (2016-11-15 revision 56800) [x86_64-linux-gnu]
* Backport: 2.2: UNKNOWN, 2.3: UNKNOWN, 2.4: UNKNOWN
----------------------------------------
rdoc.rb inserts the current time into created.rid
so the file differs across each build,
making it hard for distributions like openSUSE's
to create bit-identical binary packages when those are using rdoc.

See https://reproducible-builds.org/ why that matters



---Files--------------------------------
0001-created.rid-use-SOURCE_DATE_EPOCH.patch (1.01 KB)


-- 
https://bugs.ruby-lang.org/

      parent reply	other threads:[~2018-01-10  9:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <redmine.issue-13627.20170603041108@ruby-lang.org>
2017-06-03  4:11 ` [ruby-core:81550] [Ruby trunk Bug#13627] created.rid prevents reproducible builds rubybugsbmw
2017-06-05  8:52 ` [ruby-core:81578] [Ruby trunk Bug#13627][Assigned] " hsbt
2017-11-13 16:32 ` [ruby-core:83757] [Ruby trunk Bug#13627] " swills
2018-01-10  9:36 ` aycabta [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-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.ruby-lang.org/en/community/mailing-lists/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=redmine.journal-69519.20180110093627.533e0790898ba14a@ruby-lang.org \
    --to=ruby-core@ruby-lang.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.
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).