#rubygems on 2018-05-25 — irc logs at freenode.irclog.whitequark.org

2017-11-08 13:21 imperator changed the topic of #rubygems to: http://blog.rubygems.org/2017/11/03/2.7.1-released.html - Latest status: http://twitter.com/rubygems_status and http://status.rubygems.org

00:15 Guest19310 is now known as ged

00:16 ged is now known as Guest85807

00:39 ur5us has quit [Ping timeout: 268 seconds]

00:56 ur5us has joined #rubygems

01:00 ur5us has quit [Ping timeout: 245 seconds]

01:04 ur5us has joined #rubygems

01:25 Guest85807 is now known as ged

01:26 ged is now known as Guest36153

02:35 Guest36153 is now known as ged

02:36 ged is now known as Guest22663

03:45 Guest22663 is now known as ged

03:46 ged is now known as Guest10644

04:40 Guest3612 is now known as baweaver

04:55 Guest10644 is now known as ged

04:56 ged is now known as Guest65777

05:10 ur5us has quit [Remote host closed the connection]

05:10 ur5us has joined #rubygems

05:15 ur5us has quit [Ping timeout: 268 seconds]

05:38 KeyJoo has joined #rubygems

05:38 KeyJoo has quit [Max SendQ exceeded]

05:39 KeyJoo has joined #rubygems

06:05 Guest65777 is now known as ged

06:06 ged is now known as Guest70804

06:38 pombreda has quit [Ping timeout: 240 seconds]

06:50 pombreda has joined #rubygems

07:15 Guest70804 is now known as ged

07:16 ged is now known as Guest2576

08:25 Guest2576 is now known as ged

08:26 ged is now known as Guest26197

08:28 KeyJoo has quit [Remote host closed the connection]

09:35 Guest26197 is now known as ged

09:36 ged is now known as Guest58843

10:41 ur5us has joined #rubygems

10:45 Guest58843 is now known as ged

10:46 ged is now known as Guest5592

11:01 ur5us has quit [Remote host closed the connection]

11:02 ur5us has joined #rubygems

11:06 ur5us has quit [Ping timeout: 256 seconds]

11:32 ur5us has joined #rubygems

11:35 ur5us has quit [Remote host closed the connection]

11:35 ur5us has joined #rubygems

11:40 ur5us has quit [Ping timeout: 256 seconds]

11:55 Guest5592 is now known as ged

11:56 ged is now known as Guest76059

13:05 Guest76059 is now known as ged

13:06 ged is now known as Guest57223

13:51 houhoulis has joined #rubygems

14:13 houhoulis has quit [Remote host closed the connection]

14:15 Guest57223 is now known as ged

14:16 ged is now known as Guest34091

14:24 \13k has quit [Ping timeout: 256 seconds]

14:27 \13k has joined #rubygems

15:25 Guest34091 is now known as ged

15:26 ged is now known as Guest5706

16:27 cliles has quit [Ping timeout: 245 seconds]

16:27 cliles has joined #rubygems

16:35 Guest5706 is now known as ged

16:36 ged is now known as Guest54758

17:45 Guest54758 is now known as ged

17:46 ged is now known as Guest34421

18:55 Guest34421 is now known as ged

18:56 ged is now known as Guest79708

19:40 KeyJoo has joined #rubygems

19:56 pombreda has quit [Ping timeout: 245 seconds]

20:01 ur5us has joined #rubygems

20:05 Guest79708 is now known as ged

20:06 ged is now known as Guest23764

20:08 pombreda has joined #rubygems

21:15 Guest23764 is now known as ged

21:16 ged is now known as Guest98248

22:25 Guest98248 is now known as ged

22:26 ged is now known as Guest62306

22:40 ur5us has quit [Remote host closed the connection]

22:49 ur5us has joined #rubygems

22:58 istrasci has joined #rubygems

23:00 <istrasci> Developers are encouraged to use Semantic Versioning (https://guides.rubygems.org/patterns/#semantic-versioning), but when I try to set the gem version to "1.0.0+metadata" (rule #10; https://semver.org/#spec-item-10), I get "Malformed version number string". What should I do?

23:35 Guest62306 is now known as ged

23:36 ged is now known as Guest39593

23:55 ur5us has quit [Remote host closed the connection]