Re: new gemspec behavior in rawhide

2016-11-26 Thread Dusty Mabe
On 11/26/2016 12:31 PM, Mamoru TASAKA wrote: > Dusty Mabe wrote on 11/27/2016 01:35 AM: >> >> Hey all, >> >> In my vagrant-sshfs rpm i call `gem spec` here [0]. In rawhide vs f25 I get >> differing >> outputs. Basically in rawhide I get a bunch of `.freeze` added to my strings >> like: >> >>

Re: new gemspec behavior in rawhide

2016-11-26 Thread Mamoru TASAKA
Dusty Mabe wrote on 11/27/2016 01:35 AM: Hey all, In my vagrant-sshfs rpm i call `gem spec` here [0]. In rawhide vs f25 I get differing outputs. Basically in rawhide I get a bunch of `.freeze` added to my strings like: s.authors = ["Dusty Mabe".freeze] See the full diff at [1]. This is

Re: new gemspec behavior in rawhide

2016-11-26 Thread Tom Hughes
On 26/11/16 16:35, Dusty Mabe wrote: In my vagrant-sshfs rpm i call `gem spec` here [0]. In rawhide vs f25 I get differing outputs. Basically in rawhide I get a bunch of `.freeze` added to my strings like: s.authors = ["Dusty Mabe".freeze] See the full diff at [1]. This is causing pain for

new gemspec behavior in rawhide

2016-11-26 Thread Dusty Mabe
Hey all, In my vagrant-sshfs rpm i call `gem spec` here [0]. In rawhide vs f25 I get differing outputs. Basically in rawhide I get a bunch of `.freeze` added to my strings like: s.authors = ["Dusty Mabe".freeze] See the full diff at [1]. This is causing pain for me because I actually patch