Friday, 2017-02-03

*** notmyname has quit IRC00:11
*** notmyname has joined #swift300:13
*** chsc has joined #swift304:25
*** chsc has quit IRC04:25
*** chsc has joined #swift304:25
*** chsc has quit IRC04:43
*** cschwede has quit IRC06:03
*** cschwede has joined #swift306:05
*** DSLegends has quit IRC09:08
*** DSLegends has joined #swift309:08
*** Shashikant86 has joined #swift309:26
*** Shashikant86 has quit IRC10:03
*** Shashikant86 has joined #swift310:04
*** Shashikant86 has quit IRC10:56
*** Shashikant86 has joined #swift311:01
*** Shashikant86 has quit IRC11:18
*** Shashikant86 has joined #swift311:19
*** Shashikant86 has quit IRC11:30
*** Shashikant86 has joined #swift312:02
*** Shashikant86 has quit IRC13:06
*** Shashikant86 has joined #swift313:40
*** Shashikant86 has quit IRC15:13
*** Shashikant86 has joined #swift315:13
*** Shashikant86 has quit IRC15:50
*** chsc has joined #swift316:12
*** chsc has quit IRC16:12
*** chsc has joined #swift316:12
*** Shashikant86 has joined #swift316:24
*** Shashikant86 has quit IRC17:18
timburkekota_: i found a small hitch with using the stable/newton tarball -- it doesn't fulfill a 2.10.1 requirement, but instead reports as 2.10.1.dev22 (which it was, until the tag was actually created)22:57
timburkeso do we want to just use the hardcoded version number, or push the requirement back to 2.10.0, or wait keep the hardcoded version number for now and switch it to stable/newton when the next patch lands?22:59
timburkethere's a similar if we ever want/need to depend on a stable patch -- to properly represent the requirement, it seems like we'd need to force a tag in swift so we have something to update in requirements.txt, then update both that and the tarball to the new version number, then wait for another patch before switching back to stable/newton :-/23:03

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!