[15:06] smoser: I think I got the heading levels wrong on the readthedocs stuff, the sidebar has a few extra line items now :( [15:11] oh. that sok [15:11] they are really wierd [15:11] see doc/rtd/index.rst [15:11] theres a comment there that says what i was trying to keep [15:12] but its really , really odd... you kind of pick whatever your headers are dynamically and it just tries to sort it all out [15:12] powersj, i filed doc/rtd/index.rst [15:12] https://bugs.launchpad.net/curtin/+bug/1652329 [15:12] as i'm tired of being bit by distro package failed to build when tox was fine :) [15:12] i'm not going to fix that today though, just going to fix the one pycodestyle complaint [15:14] ok - so effectively run tox with latest pip packages and run tox with pinned versions of zesty? what are you pinning to? [15:14] do we need pinned versions for every release? [15:15] so there are 2 kinds of tox targets. [15:15] a.) unit test [15:16] b.) code style [15:16] for 'a', it makes sense to have pinned versions everywhere that we need to run [15:17] for 'b', it doesnt really matter. we pick one set and stick with it. [15:17] currently, we've got this cocktail mix where we run some code-style checkers during the package build [15:17] ok [15:17] and thus we're forced to have code style pass with multiple different versions of checkers [15:17] which, kind of is insane [15:18] yeah [15:18] but i never really thoguht clearly on this before. i think i've convinced myself that running coding style checks during package build is not helpful [15:18] as long as they're run on trunk (and ideally gate) [15:18] yeah [15:19] do you want to fix your formating ? [15:19] you can if you want, and have it in a 0.7.9 that is due... inthe next 2 hours [15:19] reading your comments now to see what I need to do [15:27] powersj, http://paste.ubuntu.com/23673609/ [15:27] that is my interpretation [15:27] of your sections and such [15:27] the whole dynamic "pick whatever you want" makes it really hard for a human to even understand what should be what [15:30] smoser: that looks like what I have now. I didn't realize having === on top and bottom made a difference [15:30] really odd [15:30] :) [15:30] do you want to just merge that? or want an mp? [15:30] if you're happy with that, i'll do it. [15:30] go for it [15:31] note i dropped the toc stuff at the top too [15:31] same :) [15:31] I saw how it looked at didn't like it [17:46] smoser: time for a /topic update? :) === smoser changed the topic of #cloud-init to: cloud-init 0.7.9 released 2016-12-23. 0.7.10 open. reviews: https://code.launchpad.net/~cloud-init-dev/cloud-init/+git/cloud-init/+ref/master/+activereviews | fly the W [17:46] * smoser leaves the fly the W on [17:57] powersj, i'm almost out the door [17:57] gonna upload to zesty 0.7.9 [17:57] smoser: sweet! [17:58] thanks for the merge this week [17:58] http://cloudinit.readthedocs.io/en/latest/ works [17:58] and 0.7.9 magically showed up [17:58] ah yes that looks good :) [18:00] smoser: so on deck for cloud-init then is the tox changes, updating the jenkins runs to use master and not my branch, and I have another merge from magicalChicken I still need to do. [18:01] powersj, curtin has similar nonsense in its tox [18:01] wrt pycodestyle stuff [18:02] ah yes [18:02] we shoudl fix that in the same way both places [18:02] agreed, when you get back I'll try to have merge requests for both [22:58] hmm, for some reason cloud-init isn't passing gw or hwaddr info to the old netconfig stuff [23:07] 0.7.9 has the bug too [23:08] seems like it's being removed before even being passed to the gentoo portions [23:14] prometheanfire: you're sort of hitting the worst time calendar wise :) EOD/EOW/EOY [23:25] I know [23:26] I've been needing to rewrite the gentoo pieces [23:26] guess this gives me a reason [23:26] I thought it was working, wonder why it's not now [23:26] maybe newton changed the format or something