[00:29] roaksoax: out of interest, what does it mean when the main bugtask on those backport requests is marked fix-released? [00:40] bigjools: that's been fixed in ubuntu+1 [00:41] ah ok trunk [00:41] seems a bit weird for a backport request, but ok :) [00:48] bigjools: not trunk, but raring :) [00:48] bigjools: raring/quantal [00:48] so in case we are sruing to quantal, we need it fixed in raring first [00:48] it's ubuntu's trunk :) [00:49] bigjools: btw... nick just made changes to the documentation in the latest stabilization ... however, unless the docs build with whatever is in archive, the won't get included in the package [00:49] other than that, maas-import-pxe-file manpage needs to be built now [00:51] roaksoax: you mean dependencies? [00:52] bigjools: yeah dependencies in archive [00:52] roaksoax: ok I think it should. there were fixes, but I don't recall seeing any n ew deps [00:53] yep, will look into that then [00:53] anyways, i'm off [00:53] bigjools: so the idea is that sru only gets things that applied to trunk first. As a process it doesn't understand things that only apply to old versions (such as bugs that architectural improvements made impossible in trunk) [00:53] have a good day [00:53] roaksoax: righto, cheers buddy [00:54] lifeless: yes, that's understood. I was just referring to the odd practice with bugs. [00:54] bigjools: so was I :P [00:54] then we are in violent agreement [00:54] \o/ [00:55] now, time for the a/c, 30C at 11am is too much === edamato is now known as edamato-lunch [14:39] allenap: this printf "%s\n" "$@" thing; I had no idea that printf would behave like that, but it does seem to. Is this documented anywhere? [14:39] (ie. I can't find it documented anywhere!) [14:43] rbasak: I can't find it documented anywhere either. [14:43] allenap: should I use it anyway? [14:44] * rbasak isn't too bothered by arches starting with hyphens, or arches with spaces in them (although the latter is easy enough to quote) [14:47] rbasak: Up to you :) Using an undocumented feature of bash's printf doesn't seem like a big problem, given that none of this has tests to spot breakage with echo either ;) It's probably $safer to go with echo, where $safer has yet to be defined in this dimension. [14:47] :-) === edamato-lunch is now known as edamato === matsubara is now known as matsubara-lunch === matsubara-lunch is now known as matsubara === rnbrady_ is now known as rnbrady [23:23] bigjools: howdy [23:23] bigjools: https://code.launchpad.net/~allenap/maas/packaging.render-man/+merge/135798 [23:23] o/ [23:23] bigjools: i think that should not land [23:24] * bigjools is all ears [23:24] bigjools: that's getting dependencies for the internet [23:24] ? [23:24] how's that? [23:25] Ah, `make man` may do that. [23:25] roaksoax: Good point. [23:25] oh I didn't know it did that [23:25] that's quite bad indeedf [23:25] yeah :) [23:25] It's automatically installing Sphinx via buildout. [23:25] so allenap, back to pre-generated man pages? :) [23:26] bigjools: Yeah :-/ [23:26] Right, shouldn't take long... [23:26] allenap: can't use sphinx from archiveS? [23:26] "Julian's change and Gavin's change meet like matter and antimatter" [23:26] ! [23:27] how woudl you generate those docs manually? [23:27] allenap: ah yes you could add sphinx as a build dep [23:28] the problem is that it is setting a build environment [23:29] Could use sphinx from package I guess. Let me see if that'll work. [23:30] allenap: [23:30] allenap: yes [23:32] allenap: and you need to make sure that the source is not unclean after making it [23:35] roaksoax: I pushed a new change up to packaging.precise.sru. I also set the branch conf to append_revisions_only=True just in case you decided to push without pulling first :) [23:35] bigjools: alright cool :) [23:36] roaksoax, bigjools: It's a big job to set up the build environment (right now it needs the full Django+MAAS stack build in order to correctly generate docs) so I'm going to go with keeping the generated man pages in the tree. [23:36] urgh [23:36] ok [23:39] allenap: so yeah we don't want that in the packaging (to buld the whole environment), so I'd recommend you do it in the debian/rules file, (similar to how I build enums.js) [23:40] bigjools: We can revisit this later; let's do this to unblock the build. Secondly, we could add a test to ensure that the man pages are up-to-date. [23:41] allenap: +! [23:41] and 1 [23:44] bigjools: https://code.launchpad.net/~allenap/maas/keep-rendered-man-pages/+merge/135800 (no test, but I need to go to bed) [23:44] allenap: I'll pick it up, thanks [23:44] There will be a corresponding package change. [23:44] ok [23:45] bigjools: I've just pushed the packaging change (to not generate the man pages). Night night. [23:45] cheers [23:45] nn [23:45] roaksoax: Thanks for spotting that problem so soon. [23:45] I'll fix it all up, it'll conflict with mine [23:45] allenap: no worries :) that's the reason why I never built docs before :) [23:46] anyways [23:46] have fun guys [23:46] * roaksoax continues with his holiday [23:46] o/ [23:52] roaksoax: FWIW the trunk packaging had ended up with maas/1.2 in the get-orig-source rule.... oops! [23:52] bigjools: yeah I removed that but I gets got introduced again :S:) [23:52] it's fixed in allenap's branch about to land [23:53] ok cool [23:54] roaksoax: also I unsubscribed maas-maintainers from branch email - subscribe yourself instead if you want [23:56] bigjools: will do [23:56] thanks [23:56] I got fed up with double notifications