Bug#779631: please make gemspec output reproducible

[Antonio Terceiro]

On Sun, Aug 23, 2015 at 11:14:35PM +0200, Chris Lamb wrote:
> Chris Lamb wrote:
> 
> > I will therefore assume that this will "fix itself" once 2.2 becomes the 
> > default.
> 
> Out of interest, is there an approximate timeline for 2.2 becoming the
> default?
> 
> I can see https://wiki.debian.org/Teams/Ruby/Ruby2.2 and
> https://wiki.debian.org/Teams/Ruby/InterpreterTransitions but it's
> unclear where we currently.

Emilio from the RT asked to put it on hold until we are done with GCC 5.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789077#136

-- 
Antonio Terceiro 


signature.asc
Description: Digital signature

Bug#779631: please make gemspec output reproducible

[Chris Lamb]

Chris Lamb wrote:

> I will therefore assume that this will "fix itself" once 2.2 becomes the 
> default.

Out of interest, is there an approximate timeline for 2.2 becoming the
default?

I can see https://wiki.debian.org/Teams/Ruby/Ruby2.2 and
https://wiki.debian.org/Teams/Ruby/InterpreterTransitions but it's
unclear where we currently.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#779631: please make gemspec output reproducible

[Chris Lamb]

Chris Lamb wrote:

> It seems like this didn't fix it, or there is an extremely similar
> issue. For example:
> 
> https://reproducible.debian.net/rb-pkg/unstable/amd64/ruby-rack-mobile-detect.html

Ah, AFAICT this was fixed in an upload for ruby2.2, whilst ruby 2.1 is
still the default version in unstable. I will therefore assume that this
will "fix itself" once 2.2 becomes the default.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-

Bug#779631: please make gemspec output reproducible

[Chris Lamb]

reopen 779631
found 779631
tags - patch
thanks

It seems like this didn't fix it, or there is an extremely similar
issue. For example:

 
https://reproducible.debian.net/rb-pkg/unstable/amd64/ruby-rack-mobile-detect.html

I will investigate soon; apologies that I am reopening this without it
being immediately actionable on your part.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#779631: please make gemspec output reproducible

[Chris Lamb]

Source: libruby2.1
Version: 2.1.5-1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps toolchain
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi,

While working on the "reproducible builds" effort [1], we have noticed
that libruby2.1 is generating .gemspec files with an output that depends
on the timezone.

The attached patch normalises the time to UTC before outputting. Once
applied, packages that use gem2deb, etc etc can be built reproducibly
in our reproducible toolchain.

 [1]: https://wiki.debian.org/ReproducibleBuilds


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff --git a/lib/rubygems/specification.rb b/lib/rubygems/specification.rb
index f4e609a..749f38b 100644
--- a/lib/rubygems/specification.rb
+++ b/lib/rubygems/specification.rb
@@ -1524,7 +1524,7 @@ class Gem::Specification < Gem::BasicSpecification
   "invalid date format in specification: #{date.inspect}")
   end
 when Time, Date then
-  Time.utc(date.year, date.month, date.day)
+  Time.utc(date.utc.year, date.utc.month, date.utc.day)
 else
   TODAY
 end