Bug#779631: please make gemspec output reproducible

2015-08-24 Thread 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

Bug#779631: please make gemspec output reproducible

2015-08-23 Thread 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

Bug#779631: please make gemspec output reproducible

2015-08-14 Thread 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

Bug#779631: please make gemspec output reproducible

2015-08-04 Thread 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

Bug#779631: please make gemspec output reproducible

2015-03-03 Thread 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