[00:06] <wwitzel3> ericsnow: ping, you still around?
[00:06] <ericsnow> wwitzel3: more or less ;)
[00:07] <wwitzel3> ericsnow: our cat got bit by a dog so I had to run off to the vet for most of the day, but I'm back now if you want to hand off
[00:07] <ericsnow> wwitzel3: sorry to hear that
[00:07] <ericsnow> wwitzel3: cat okay?
[00:08] <wwitzel3> ericsnow: she is well, yeah, couple set of stiches and a cone of shame
[00:08] <ericsnow> wwitzel3: if you like, you can give my cleanup patch a once over: http://reviews.vapour.ws/r/2927/
[00:08] <ericsnow> wwitzel3: ha, cone of shame
[00:10] <wwitzel3> ericsnow: that diff seems to have a lot of stuff in it, is all of this part of the cleanup?
[00:10] <ericsnow> wwitzel3: I have some comments for your LXD provider code, but that can wait until tomorrow :)
[00:10] <ericsnow> wwitzel3: well, it was smaller before fwereade made a number of (reasonable) suggestions :)
[00:11] <ericsnow> wwitzel3: but yeah, it really is that big
[00:11] <ericsnow> wwitzel3: sorry
[00:11] <ericsnow> wwitzel3: a *lot* of extra test coverage
[00:11] <wwitzel3> ericsnow: what about all the stuff in apiserver/common/errors?
[00:11]  * ericsnow checks
[00:12] <ericsnow> wwitzel3: alas, yes
[01:19] <mup> Bug #1507601 changed: TestStartTerminationWorker fails on gccgo <ci> <gccgo> <ppc64> <regression> <test-failure> <juju-core:Fix Released by gz> <juju-core 1.25:Fix Released by gz> <https://launchpad.net/bugs/1507601>
[01:28] <mup> Bug #1507601 opened: TestStartTerminationWorker fails on gccgo <ci> <gccgo> <ppc64> <regression> <test-failure> <juju-core:Fix Released by gz> <juju-core 1.25:Fix Released by gz> <https://launchpad.net/bugs/1507601>
[01:34] <mup> Bug #1507601 changed: TestStartTerminationWorker fails on gccgo <ci> <gccgo> <ppc64> <regression> <test-failure> <juju-core:Fix Released by gz> <juju-core 1.25:Fix Released by gz> <https://launchpad.net/bugs/1507601>
[01:34] <sinzui> thumper: menn0 waigani wallyworld do either of you have a minute to review this for the release http://reviews.vapour.ws/r/2980/
[01:35] <wallyworld> sinzui: lgtmandt
[01:35] <sinzui> thank you wallyworld
[02:00] <wallyworld> axw: be there in 1 minute
[02:00] <axw> wallyworld: me too
[02:12] <natefinch> lololol  -  juju-core's complimentary commercial subscription expires on 2015-11-22. Proprietary projects can use Launchpad by purchasing a commercial-use subscription which costs US$250/year/project.
[02:16] <natefinch> somebody just broke something in launchpad
[03:21] <thumper> davechen1y: ping
[03:43] <cherylj> Can I get a review for http://reviews.vapour.ws/r/2981/ ?
[03:46]  * thumper looks
[03:49]  * thumper sighs
[03:49] <thumper> clicked the wrong button again
[03:49]  * thumper wanted the fix it and ship it button
[03:51] <cherylj> oh blargh
[04:14] <thumper> kids calling
[04:14] <thumper> laters folks
[04:14] <thumper> see y'all Tuesday (public holiday monday here)
[04:34] <cherylj> wallyworld, axw could I get a sanity check on this revision:  http://reviews.vapour.ws/r/2981/
[04:35] <cherylj> It's late and I don't want to mess things up again :)
[04:35] <wallyworld> sure
[04:40] <axw> cherylj: seems fine, although I'd probably just use a regex to match the whitespace
[04:43] <wallyworld> cherylj: sorry, just got off the phone, what was the issue?
[04:45] <wallyworld> oh, i see - version string length
[04:45] <cherylj> axw: would you be willing to implement just using a regex?
[04:45] <cherylj> it's midnight here and I really want to go to bed
[04:45] <axw> cherylj: sure
[04:46] <cherylj> thank you, axw.  This is for bug 1509032
[04:46] <mup> Bug #1509032: Juju doesn't support is own version of 1.25.0 <ci> <test-failure> <juju-core:In Progress by cherylj> <juju-core 1.25:In Progress by cherylj> <https://launchpad.net/bugs/1509032>
[04:47] <wallyworld> or even just strip the trailing spaces
[04:48] <axw> cherylj: not clear how I trigger the failure?
[04:48] <cherylj> set juju/juju/version/version.go, const version = "1.25.1"
[04:49] <cherylj> you have to be on 1.25 and get my latest commits from today
[04:49] <axw> cherylj: I see, thanks
[05:07] <axw> wallyworld: if you have a moment, http://reviews.vapour.ws/r/2982/
[05:07] <wallyworld> sure
[05:09] <wallyworld> axw: yup, +1
[07:28] <rogpeppe> dimitern: ping
[07:28] <rogpeppe> anyone around to do a very quick (and urgently needed) review?
[07:29] <rogpeppe> http://reviews.vapour.ws/r/2983/
[07:39] <dimitern> rogpeppe, sure, looking
[07:39] <rogpeppe> dimitern: thanks!
[07:40] <rogpeppe> dimitern: (FWIW it follows the exact same pattern used in the other providers)
[07:42] <dimitern> rogpeppe, ship it! :)
[07:50] <dimitern> cherylj, any chance you're still around?
[07:50] <wallyworld> dimitern: hey there, do you have time for a chat?
[07:52] <dimitern> wallyworld, I do
[07:52] <wallyworld> https://plus.google.com/hangouts/_/canonical.com/tanzanite-stand
[07:52] <dimitern> wallyworld, omw
[09:02] <voidspace> dimitern: standup?
[09:03] <dimitern> omw
[09:03] <dimitern> fwereade, joining standup?
[10:06] <voidspace> wallyworld: ping
[10:06] <voidspace> axw: ping
[10:06] <wallyworld> hey
[10:06] <voidspace> wallyworld: hey
[10:06] <voidspace> wallyworld: the broken upgrade issue
[10:07] <wallyworld> that old thing
[10:07] <voidspace> wallyworld: we've worked out that *part* of the problem is that "ignore-machine-addresses" is broken for lxc containers
[10:07] <voidspace> wallyworld: and there's an easy fix (we think)
[10:07] <voidspace> wallyworld: so I'll create a new bug for that specifically and work on it
[10:08] <wallyworld> ok
[10:08] <voidspace> lxc containers *only* have machine addresses, so ignoring them is bad...
[10:08] <wallyworld> yeah, containers don't have provider addresses
[10:08] <voidspace> I've added a note to the main launchpad bug about this
[10:08] <voidspace> just keeping you up to date
[10:09] <wallyworld> yay for easy fix - get 1.24 and 1.25 working and fix 1.26 "properly"
[10:09] <wallyworld> thanks for update, much appreciated
[10:10] <voidspace> I'll add a reply to the rt too
[10:10] <wallyworld> ty
[10:29] <mup> Bug #1509292 opened: "ignore-machine-addresses" broken for containers <juju-core:In Progress by mfoord> <juju-core 1.24:In Progress by mfoord> <juju-core 1.25:In Progress by mfoord> <https://launchpad.net/bugs/1509292>
[10:32] <mup> Bug #1509292 changed: "ignore-machine-addresses" broken for containers <juju-core:In Progress by mfoord> <juju-core 1.24:In Progress by mfoord> <juju-core 1.25:In Progress by mfoord> <https://launchpad.net/bugs/1509292>
[10:41] <mup> Bug #1509292 opened: "ignore-machine-addresses" broken for containers <juju-core:In Progress by mfoord> <juju-core 1.24:In Progress by mfoord> <juju-core 1.25:In Progress by mfoord> <https://launchpad.net/bugs/1509292>
[11:05] <dimitern> frobware, I think jam's comment on deploy time bindings just made my day :)
[11:05] <voidspace> dimitern: how do I get "juju upgrade-juju --upload-tools" to work?
[11:06] <voidspace> dimitern: http://pastebin.ubuntu.com/12901704/
[11:06] <frobware> dimitern, need to work out why I don't get any doc notifications
[11:06] <voidspace> dimitern: client is my new version, server is 1.20.14
[11:06] <dimitern> frobware, not actually implementing (but speccing properly) the "connects" side of the metadata, will save good 2 to 3 weeks of work before jan
[11:07] <dimitern> voidspace, so this is coming from the apiserver I guess? try with --debug?
[11:08] <dimitern> voidspace, if that's the case, try $ juju upgrade-juju --upload-tools --series trusty
[11:08] <voidspace> dimitern: http://pastebin.ubuntu.com/12901718/
[11:09] <dimitern> this tells me you're on wily
[11:09] <voidspace> dimitern: tried that already, --series is ignored
[11:09] <voidspace> I'm really not
[11:09] <dimitern> oh ffs..
[11:09] <voidspace> 15.04
[11:10] <dimitern> voidspace, juju status | grep agent-version ?
[11:10] <voidspace> we need to solve this so peter can try the new binaries (let alone actually testing it ourselves)
[11:10] <dimitern> agreed
[11:10] <voidspace> <IP_ADDRESS>
[11:11] <dimitern> hmm
[11:11] <dimitern> so where's wily coming from then
[11:11] <voidspace> presumably simplestreams
[11:11] <voidspace> where else could it come from
[11:12] <dimitern> it could be hardcoded
[11:12] <dimitern> in the client
[11:12] <voidspace> ah right
[11:12] <dimitern> most likely, as 1.20 was pre-vivid, right? and it's not complaining about it
[11:12] <voidspace> indeed, if I set the tools-url to something invalid I still get the same error
[11:12] <voidspace> so it must come from the client
[11:13] <voidspace> well, no - if I grep our codebase for wily it doesn't appear
[11:13] <voidspace> we must have a series list that the server checks
[11:14] <dimitern> we have indeed - version/supportedseries.gho
[11:15] <voidspace> yeah, just found it
[11:15] <voidspace> dimitern: and wily isn't in seriesVersions
[11:15] <dimitern> just try adding "wily" to ubuntuSeries map rebuild and retry
[11:15] <voidspace> dimitern: let me try adding it there
[11:15] <dimitern> :)
[11:16] <dimitern> voidspace, and if that works we should give both juju and jujud in the tarball for peter
[11:16] <voidspace> dimitern: kk
[11:17] <voidspace> hmm... still the same error
[11:17] <dimitern> voidspace, hmm I suspect you need to do apt-get upgrade and make sure distro-info is up-to-date
[11:17] <dimitern> voidspace, looking at the comment on seriesVersions, check: $ cat /usr/share/distro-info/ubuntu.csv
[11:17] <dimitern> mine does show wili
[11:17] <dimitern> wily
[11:17] <voidspace> dimitern: on machine-0
[11:18] <dimitern> on your machine
[11:18] <voidspace> mine does too
[11:18] <dimitern> (well, try first on yours, then try on machine-0 I guess :)
[11:18] <voidspace> this error looks like it's coming from the server
[11:18] <dimitern> yeah - the "400" is a http status I guess
[11:19] <voidspace> that directory doesn't exist on machine-0
[11:19] <voidspace> doing an upgrade anyway
[11:20] <voidspace> nothing to upgrade
[11:20] <dimitern> voidspace, try dist-upgrade as well
[11:20] <voidspace> did
[11:37] <dimitern> voidspace, well, juju set-env logging-config '<root>=TRACE' && retry and paste the machine-0.log for the deploy call?
[11:38] <voidspace> dimitern: I'm going to see if 1.22 has the same issue
[11:39] <voidspace> dimitern: if I can upgrade from 1.22 that will suffice for testing
[11:39] <voidspace> dimitern: and they do report failed upgrades from 1.22 - so they can test that scenario too
[11:39] <voidspace> (if upgrading from 1.22 with upload-tools works)
[11:41] <dimitern> voidspace, +1
[11:45] <voidspace> dimitern: seemed to work
[11:45] <voidspace> at least the upload worked I mean...
[11:45] <voidspace> we'll see if the issue is fixed
[11:45] <dimitern> nice!
[11:47] <dimitern> 1.20 is too old anyway
[11:47] <voidspace> yep
[11:50]  * dimitern steps out for a while
[12:14] <voidspace> dimitern: nope, still the same error - just reported in a slightly different way
[12:15] <voidspace> dimitern: in fact, I can't even upgrade from 1.22 to 1.24 due to this error
[12:15] <voidspace> dimitern: must be due to the already uploaded tools
[12:15] <voidspace> I'll reset
[12:18] <voidspace> dimitern: as wily is imminent I wonder if it's just recently been added to a stream / version list somewhere which is only *now* causing this problem to show
[12:33] <voidspace> dimitern: I bet I can still test this fix anyway ("ignore-machine-addresses" with containers is probably broken even without an upgrade)
[12:33] <voidspace> dimitern: and treat the upgrade problem as a separate issue
[12:42] <frobware> voidspace, seems like it it would be a good step along the way
[12:59] <voidspace> frobware: yeah
[13:21] <mup> Bug #1509353 opened: local provider service cannot be enabled after disabling <local-provider> <systemd> <juju-core:Triaged> <https://launchpad.net/bugs/1509353>
[13:49] <fwereade> grrrrrrrrrrrrrrrrr RB apparently just ate a long reply
[13:51] <natefinch> fwereade: that has happened to me a few times.  Seemsl ike if you click on a link to look at the code, your replies go away
[13:52] <fwereade> natefinch, dammit, thanks, hopefully I will learn from it
[13:52] <natefinch> fwereade: but you don't really need a long reply. You can just click the ship it button on my review.  I'll know what you mean
[13:52] <perrito666> lol
[13:53] <natefinch> fwereade: but seriously... I always open the code links in new tabs now, that seems to be the only safe way to do it
[13:54] <fwereade> natefinch, so what happened there, I think, was that I had two concurrent replies to previous reviews open, and then remembered I also had a review, and that would be a good place to put the topp-level comments, so I pressed the "edit review" button; when I returned only one of the replies was there
[13:54] <lazypower> :\
[13:54] <lazypower> thats never fun when you're working and the software is actively trolling you
[13:55] <fwereade> still better than lp or github for reviews :)
[13:56] <lazypower> debateable
[13:56] <natefinch> it's amazing no one's made a significantly better review system... they all kind of suck in their own special ways.
[13:57] <natefinch> which one you like best is mostly dependent on which suckiness you find least annoying
[13:58] <fwereade> natefinch, ha, yeah
[13:58] <lazypower> i feel this way about most software natefinch
[13:58] <natefinch> lazypower: lol yep
[14:00] <fwereade> natefinch, btw, we should talk more about tests -- I *think* that our differences on BaseSuite and in/out-package tests come from a common source
[14:00] <natefinch> fwereade: I definitely think we both want the same thing in the end, we are just approaching it from different directions :)
[14:00] <fwereade> natefinch, which could reasonably be summarised as "fwereade is unreasoningly paranoid and grumpy about all developers, including himself"
[14:01] <natefinch> fwereade: ditto for me :)
[14:01] <fwereade> natefinch, so in all cases, what you are doing is fine in isolation, but presses my buttons because it feels very easy for other people to break them unintentionally
[14:02] <fwereade> natefinch, BaseSuite doesnn't protect against anything in your code
[14:03] <fwereade> natefinch, but it (or maybe better, here, I think, IsolationSuite) *does* protect against the stuff other people might do in the future
[14:03] <fwereade> natefinch, network access, writing env vars, etc etc
[14:03] <fwereade> natefinch, and I have approximately zero faith in our collective ability to avoid doing stuff like that
[14:03] <fwereade> natefinch, because it seems to keep cropping up
[14:04] <katco`> natefinch: planning time
[14:04] <fwereade> natefinch, and log-capture-by-default STM to be cheap compared to the monstrous hassles of trying to repro an intermittent failure that doesn't capture logs
[14:05] <natefinch> katco`: oops, coming
[14:05] <fwereade> natefinch, and so BaseSuite/IsolationSuite feel to me like just Good Habits because they're a tiny cost for a low-probability large benefit, that still IMO has a positive expected value
[14:05] <fwereade> natefinch, I guess now is not the best time
[14:06] <fwereade> natefinch, read at your leisure
[14:07] <fwereade> natefinch, similarly, testing in-package is fine if you're disciplined and don't fossilise the code around the implementation details; but in practice, over time, the tests and the code leak into one another
[14:09] <fwereade> natefinch, and then, when you're testing out-package and you get the urge to use export_test, you can actually use that as a smoke detector for higher-level problems with your design -- very very often, an implicit dependency that you "only want to change for tests" and therefore don't make an explicit dependency
[14:09] <fwereade> natefinch, and the urge is understandable but IMO wrong
[14:09] <fwereade> natefinch, almost anything you need to export_test you could instead represent as explicit config
[14:10] <fwereade> natefinch, which may appear to broaden the interface
[14:10] <fwereade> natefinch, but I contend that it actually just shows you a truer picture of the breadth, which was always there, but some of it was hidden
[14:11] <fwereade> natefinch, and it's only by dragging the whole set of connections into the light that we can start to make good decisions about severing them
[14:12] <frobware> dooferlad, you about? Can we have a quick chat about your NUCs?
[14:43] <marcoceppi_> I need help with actions and the jsonschema, can anyone help me out?
[14:44] <marcoceppi_> Mostly, what are the valid "types" in actions?
[14:44] <marcoceppi_> I get string, int, boolean, but what else is there? mainly, is there enum
[14:46] <natefinch> marcoceppi_: last I checked, they're all strings
[14:46] <rick_h__> marcoceppi_: hmm, it's in the schema but not sure what they implemented in the go library for it.
[14:46] <voidspace> frobware: dimitern: I can confirm that deploying a container with "ignore-machine-addresses" on fails with 1.24 (no need for an upgrade to demonstrate the bug)
[14:46] <voidspace> frobware: dimitern: testing the fix now
[14:46] <marcoceppi_> natefinch: well, no, there are definitely ints and booleans
[14:47] <rick_h__> marcoceppi_: https://github.com/juju/gojsonschema/blob/master/json_schema_test_suite/enum/schema_1.json
[14:47] <rick_h__> natefinch: ^
[14:47] <frobware> voidspace, and that is just this bug -  https://launchpad.net/bugs/1509292 - or something else?
[14:47] <mup> Bug #1509292: "ignore-machine-addresses" broken for containers <juju-core:In Progress by mfoord> <juju-core 1.24:In Progress by mfoord> <juju-core 1.25:In Progress by mfoord> <https://launchpad.net/bugs/1509292>
[14:47] <marcoceppi_> \o/
[14:47] <marcoceppi_> rick_h__: thanks!
[14:47] <dimitern> voidspace, great! then we can confirm the fix works, and prepare a tarball with patched binaries for peter to try on the actual HW
[14:47] <rick_h__> marcoceppi_: so the library should support it, not sure how it's exposed/used through actions
[14:47] <rick_h__> marcoceppi_: but that's the tool used so hopefully helps a bit more at least
[14:48] <natefinch> marcoceppi_, rick_h__:  https://bugs.launchpad.net/juju-core/+bug/1456703
[14:48] <mup> Bug #1456703: action-set converts everything to strings <actions> <juju-core:Triaged> <https://launchpad.net/bugs/1456703>
[14:48] <marcoceppi_> rick_h__: that's cool, turns out I don't need enums atm, but good to know
[14:48] <marcoceppi_> natefinch: ah, I care slightly less about that, I was talking instead about the actions.yaml file format
[14:48] <rick_h__> natefinch: hmm, but can you do a enum of strings then?
[14:49] <natefinch> rick_h__: not sure
[14:50] <natefinch> marcoceppi_: probably just needs some testing to see how it actually works... but I was getting numbers as strings, which was screwing things up, but maybe display in the GUI wouldn't be affected.
[14:51] <natefinch> jw4: ^
[14:57] <voidspace> frobware: correct
[14:58] <voidspace> dimitern: well, he can try it - but I don't think he can upgrade to it
[14:58] <voidspace> until there's a released one
[14:59] <dimitern> voidspace, hmm.. that might be true, but I'm *sure* there's a way to fix that "invalid series "wily"" error
[14:59] <voidspace> dimitern: you would hope so
[14:59] <voidspace> I haven't found it yet
[15:10] <voidspace> dimitern: frobware: the fix works
[15:10] <voidspace> I'll add a test
[15:11] <dimitern> voidspace, \o/
[15:12] <dimitern> voidspace, before you leave today, please update the original bug with links to the separate bug we filed and your proposed fix
[15:12] <voidspace> dimitern: done the first bit already
[15:12] <voidspace> will add a link to the branch
[15:13] <voidspace> dimitern: doesn't look to me like IgnoreMachineAddresses is tested...
[15:13] <voidspace> it's not called from any tests anyway
[15:14] <voidspace> dimitern: ah, found the tests
[15:14] <dimitern> voidspace, yeah, it's tested for newMachiner
[15:16] <dimitern> ok, I'm starting to celebrate the weekend and the productive week ;)
[15:16] <voidspace> dimitern: enjoy
[15:17] <dimitern> voidspace, thanks ;)
[15:33] <katco`> ericsnow: wwitzel3: natefinch: not sure what's going on. looks like i have connectivity, but having trouble with hangouts
[15:33] <natefinch> katco`: maybe log out and back in to google?
[15:34] <frobware> voidspace, please could you point me at your fix
[15:35] <frobware> voidspace, forget it, found it in the /other/ bug
[15:35] <voidspace> frobware: just pushed a test
[15:35] <voidspace> frobware: test needs improving - but the test passes with the fix and fails without it
[15:51] <frobware> anybody see general gmail connectivity issues - seem to be plagued with chrome failures most of this afternoon
[15:51] <voidspace> frobware: hmm... not that I've noticed
[15:51] <voidspace> I'm using FF though
[15:52] <frobware> voidspace, I spent at least one hour earlier in the day where things just went "aw, snap"
[15:52] <rogpeppe2> anyone fancy a ridiculous review? this merges a feature branch. it has no commits in that have not already been reviewed. https://github.com/juju/juju/pull/3590
[15:53] <rogpeppe2> it would make my week if i could get this merged today
[15:53] <voidspace> rogpeppe2: if they're all already reviewed we've done the merge without further review...
[15:53] <rogpeppe2> voidspace: awesome! $$merge$$ coming up!
[15:55] <katco`> fwereade: hey are you still around?
[15:56] <voidspace> rogpeppe2: if you want to return the favour, here's a really short review
[15:56] <voidspace> http://reviews.vapour.ws/r/2992/
[15:56] <rogpeppe2> voidspace: i have 4 more minutes until i have to go...
[15:56] <voidspace> rogpeppe2: if you can't do it no problem :-)
[15:57] <voidspace> rogpeppe2: it's *possible* to do that one in four minutes, but you might want to spend a bit more time on the test
[15:57] <voidspace> rogpeppe2: the code change is like 3 lines...
[15:57] <voidspace> frobware: http://reviews.vapour.ws/r/2992/
[16:00] <frobware> voidspace, I made one comment but need to change browsers... as it keeps going snap!
[16:00] <rogpeppe2> voidspace: sorry, small review but i'd need a while to understand the context
[16:00] <voidspace> rogpeppe2: k, thanks
[16:02] <voidspace> rogpeppe2: you wouldn't default to true, you'd default to the environment value and then override with false for a container
[16:02] <voidspace> rogpeppe2: you think that would be better?
[16:02] <voidspace> maybe
[16:03] <voidspace> rogpeppe2: I've switched to that with a comment
[16:06] <voidspace> rogpeppe2: oops, those comments should have gone to frob
[16:06] <frobware> voidspace, much better
[16:06] <voidspace> frobware: ^^
[16:06] <mup> Bug #1509419 opened: 1.25-beta1 no matching tools error message spam <landscape> <juju-core:New> <https://launchpad.net/bugs/1509419>
[16:06] <frobware> voidspace, I think you need somebody with additional +1 on the test
[16:06] <voidspace> frobware: ok
[16:07] <voidspace> TheMue: I think you're OCR today, if you're still around
[16:07] <rogpeppe2> voidspace: np
[16:07] <rogpeppe2> voidspace: have a good w/e
[16:07] <voidspace> rogpeppe2: o/
[16:07] <voidspace> you too
[16:07] <voidspace> TheMue: http://reviews.vapour.ws/r/2992/
[16:12] <bogdanteleaga> can I somehow export a struct only for testing?
[16:12] <mup> Bug #1509419 changed: 1.25-beta1 no matching tools error message spam <landscape> <juju-core:New> <https://launchpad.net/bugs/1509419>
[16:15] <mup> Bug #1509419 opened: 1.25-beta1 no matching tools error message spam <landscape> <juju-core:New> <https://launchpad.net/bugs/1509419>
[16:18] <voidspace> bogdanteleaga: the usual pattern is to export an alias to the struct in export_test.go
[16:20] <bogdanteleaga> voidspace: yeah, but I'm getting "<struct> is not an expression"
[16:20] <bogdanteleaga> it does work for functions
[16:20] <voidspace> ah
[16:21] <voidspace> bogdanteleaga: export a function that returns a struct instance?
[16:21] <voidspace> NewStruct
[16:21] <mgz_> bogdanteleaga: with `type SomeStruct someStruct`?
[16:22] <voidspace> or that...
[16:22] <mgz_> that doesn't work depending on what exactly you're doing with the struct
[16:23] <mgz_> if it's being passed in places that accept an interface it's fine
[16:23] <voidspace> if you're testing the struct itself it should be fine
[16:25] <voidspace> mgz_: if you have time a quick review would be appreciated, would be nice to land it today
[16:25] <voidspace> mgz_: http://reviews.vapour.ws/r/2992/
[16:26] <mgz_> voidspace: looking
[16:26] <bogdanteleaga> mgz_: yup, that seems to do it
[16:26] <mgz_> voidspace: I'm still mystified as to why 2992 is special
[16:27] <voidspace> mgz_: special?
[16:27] <mgz_> there's a little banner at the top of the page
[16:27] <voidspace> mgz_: oh yeah
[16:27] <voidspace> how odd
[16:27] <voidspace> just because I'm special I guess
[16:28] <mgz_> classic off-by-eight error?
[16:28] <voidspace> a palindromic number?
[16:28] <voidspace> mgz_: 2002 has a banner too
[16:28] <mgz_> aha
[16:28] <voidspace> and 2112
[16:30] <natefinch> do we support local provider on Centos?
[16:30] <mup> Bug #1509419 changed: 1.25-beta1 no matching tools error message spam <landscape> <juju-core:New> <https://launchpad.net/bugs/1509419>
[16:30] <mgz_> natefinch: nope
[16:31] <natefinch> mgz_: ok, I thought as much, but wanted  to know for sure
[16:31] <mgz_> voidspace: code changes look good to me, need to look at the original ignoremachineaddresses branch to work out the actual logic
[16:31] <mgz_> bogdanteleaga: what are the plans over centos and containers?
[16:32] <bogdanteleaga> I'm pretty out of the loop concerning that one
[16:32] <bogdanteleaga> I know there were some talks around templates and whatnot
[16:32] <bogdanteleaga> you'd be better off asking gabriel or alexis about that
[16:33] <mgz_> gotcha
[16:33] <mup> Bug #1509419 opened: 1.25-beta1 no matching tools error message spam <landscape> <juju-core:New> <https://launchpad.net/bugs/1509419>
[16:35] <bogdanteleaga> wow, juju/testing seems to depend on juju/utils
[16:36] <mgz_> bug 1463480
[16:36] <mup> Bug #1463480: Failed upgrade, mixed up HA addresses <blocker> <canonical-bootstack> <ha> <upgrade-juju> <juju-core:Fix Released by wallyworld> <juju-core
[16:36] <mup> 1.22:Fix Committed by thumper> <juju-core 1.24:Fix Released by wallyworld> <hacluster (Juju Charms Collection):New> <https://launchpad.net/bugs/1463480>
[16:39] <mgz_> voidspace: okay, your change seems fine, but we really need to kill this config option
[16:39] <mgz_> the logic around address setting is getting ridiculous
[16:39] <frobware> mgz_, choice leads to madness! :)
[16:48] <voidspace> mgz_: thanks
[16:48] <voidspace> mgz_: I know nothing about the origins of the hack
[16:48] <mgz_> voidspace: the bug is fun reading
[16:48] <voidspace> mgz_: ah, right
[16:48] <voidspace> will try and dig it out
[16:49] <voidspace> mgz_: I'll port this to 1.25 and on monday discuss with dimiter what to do about master
[16:49] <mgz_> voidspace: sounds like a good plan
[16:49] <voidspace> mgz_: at the moment if you use ignore-machine-addresses then containers are broken - so we can't leave it like this for long
[16:54] <natefinch> anyone know why we've never written code to replace downed units?  Seems like a pretty basic need - to keep your service at the capacity you told Juju you wanted
[16:55] <natefinch> (automatically replace, that is)
[17:12] <voidspace> EOW
[18:10] <wwitzel3> ericsnow: ping
[18:10] <ericsnow> wwitzel3: hey
[18:11] <ericsnow> wwitzel3: otp
[18:11] <wwitzel3> ericsnow: ok, let me know when you have a second
[19:08] <fwereade> natefinch, fwiw, the minunitsworker does that, but the functionality never got exposed via the CLI iirc
[19:09] <natefinch> fwereade: so like, you just need a flag to enable it or something?
[19:09] <fwereade> natefinch, the api accepts minunits, it just never made it into the cli
[19:10] <fwereade> natefinch, it happened a looong time ago
[19:10] <natefinch> fwereade: that's crazy
[19:12] <fwereade> natefinch, also worth remembering that our direction has been explicitly focused on providing the primitives rather than building in too much hard-to-observe cleverness
[19:12] <natefinch> fwereade: with all the talk of schedulers from other orchestration tools, seems like people want at least some basic cleverness
[19:13] <fwereade> natefinch, I have a notion that we were expecting to pick it up alongside --scale-with and similar things that we didn't do for those reasons
[19:13] <fwereade> natefinch, I'm not disagreeing, but I think there are valid arguments against building them in too deep
[19:14] <fwereade> natefinch, built-in strategies *are* confining, and tend towards pressure to add more for every scenario out there
[19:15] <fwereade> natefinch, that said, we could do a better job of exposing attachment points for external strategies
[19:16] <fwereade> natefinch, although... machine placement and unit placement *do* give you quite a lot of control
[19:16] <natefinch> fwereade: seems like if we give some default behavior and allow it to be overridden, we get the best of both worlds
[19:17] <natefinch> fwereade: for people that want it to just work, they can use the default, and for people that want to do something else, they can use something else (or just do it manually like they have to now)
[19:17] <fwereade> natefinch, zoom out enough and that's what we do, I think -- the intention is that just spamming commands with the fewest possible args *will* get you reasonably sane/predictable results
[19:18] <fwereade> natefinch, you can certainly make a case that there's room for in between the two extremes
[19:18] <natefinch> fwereade: the whole point is not to require a human at a keyboard to both notice and fix problems
[19:19] <natefinch> fwereade: especially when the most reasonable thing to do is blindingly obvious
[19:23] <fwereade> natefinch, fwiw, in machine/unit scenarios, the trouble is that the problem is rarely that blindingly obvious
[19:23] <fwereade> natefinch, just because juju's lost track of a unit does not *necessarily* imply that that unit has gone away
[19:24] <fwereade> natefinch, and when we can't be sure about the nature of a problem -- which is the general case -- automated responses are risky
[19:24] <natefinch> fwereade: that's why you let the admin decide whether or not to automatically create a new one or not.  They get to decide which is worse - having one too many units/machines or one too few
[19:24] <natefinch> fwereade: I'm guessing most admins would rather have one too many than one too few.
[19:25] <fwereade> natefinch, for instance, the instance-replacement code that we used to have got dropped after it emerged that nobody was using it on purpose, and only consciously experienced negative effects (eg stopping an instance to do something out of band, whoops, juju started a new one)
[19:26] <natefinch> fwereade: might require some tools - a juju pause-unit or something.... but mostly I'm looking for feature parity to our competitors... and one of the first things people always ask is "will you bring up a new unit if one goes down?"  And I think we lose a lot of people when we say no.
[19:31] <fwereade> natefinch, so, yes, given a clear definition of "down", you can at least come up with predictable rules there
[19:31] <mup> Bug #1496972 opened: juju bootstrap fails to successfully configure the bridge juju-br0 when deploying with wily 4.2 kernel <hs-arm64> <kernel-da-key> <network> <juju-core:New for frobware> <Ubuntu:Invalid by jsalisbury> <Ubuntu Wily:Invalid by jsalisbury> <https://launchpad.net/bugs/1496972>
[19:31] <natefinch> fwereade: might also be a case for better introspection into our providers... juju should be able to ask EC2 if an instance is down, for example.
[19:31] <fwereade> natefinch, but I would reiterate that when we tried it, people actively disliked it
[19:32] <fwereade> natefinch, yeah, I can't remember how much instancepoller keeps track of offhand
[19:35] <fwereade> natefinch, but, honestly, it's also annoyingly tricky to do usefully for any stateful workload
[19:35] <fwereade> natefinch, storage possibly makes that better, for some forms of storage at least
[19:35] <natefinch> fwereade: right, that's definitely the hardest bit
[19:37] <fwereade> natefinch, and even then... I think I'm quite comfortable focusing on the atoms -- i.e. if I had to divide effort between "migration" and "deciding when to migrate" I think I'd be pretty happy putting all my eggs in the first basket
[19:39] <natefinch> fwereade: that's true
[19:39] <fwereade> natefinch, still, though, your point about what people are asking for remains unanswered
[19:40] <fwereade> natefinch, if it is turning people off we should be addressing it
[19:41] <natefinch> fwereade: I wouldn't say I have my finger on the pulse of the devops community, but I've definitely seen people ask for having the number of units maintained, at least.  And if it's low-hanging fruit because the backend stuff already exists....
[19:43] <fwereade> natefinch, I don't think I've actually looked at the code for, uh, 30-odd months, so I can't really vouch for much -- in particular, I'm not sure it's working at the level we actually want it to
[19:44] <fwereade> natefinch, it might mesh well with a machine-reaper for dead instances... but that is its own can of worms
[19:46] <natefinch> fwereade: ahh, didn't realize it was quite that old :)
[19:47] <fwereade> natefinch, something like that, yeah, round about the atlanta sprint
[19:47] <fwereade> natefinch, it was a time of many decisions, not all of which have turned out optimal in the long run
[19:48] <fwereade> natefinch, ...and fwiw, the machine-replacer code was gone before even then, so I suspect our audience today has little in common with our audience then
[21:15] <lazypower> just pulled in -proposed juju, and so far so good team :thumbsup: nice work so far!
[21:18] <cherylj> lazypower: yay!  thank you :)
[21:20] <lazypower> :D
[21:20] <alexisb> lazypower, thanks!


[02:05] <InHisName> is teddy bald ?  Not covered all in fur ?
[02:07] <InHisName> Oh, Its you, Randy - rmg51- easy solve here.... Just use long underware to upgrade you to teddy bear warmpth status.
[06:16] <Sadin> night everyone
[06:25] <andrew> morning Sadin
[06:25] <Sadin> lol
[06:25] <InHisName> mornin' all
[06:25] <Sadin> im just goin to bed D:
[06:26] <Sadin> school in 6 and a half hrs
[06:27] <InHisName> If you make it by 5am, have a good morning and my the 5.5 hour conversation about bedtimes be fruitful.
[06:33]  * waltman had to clean up a flood in his bathroom :(
[06:33] <waltman> crazy upstairs neighbor overflowed her toilet
[06:37] <waltman> attempting to belatedly head to sleep after a second visit from $super
[06:44] <andrew> I should get to bed so I can wake up and go skiing
[08:42] <InHisName> water or snow   skiing, andrew ?
[10:21] <JonathanD> Morning.
[10:27] <rmg51> morning JonathanD
[16:30] <MutantTurkey> I need some help
[16:31] <MutantTurkey> when you are in a file dialog, and you press 'a' it jumps to the first 'a' entry
[16:31] <MutantTurkey> for example.
[16:32] <MutantTurkey> I wish to be able to type 'alphabet' and jump to the first 'alphabet' match. does any dialogs do this?
[16:37] <MutantTurkey> what I actually want to do is be able to filter things out
[17:17] <MutantTurkey> my ubuntu upgrade just died on me.
[17:17] <MutantTurkey> fk
[17:17] <MutantTurkey> fk fk fk
[17:17] <MutantTurkey> fk
[17:17] <MutantTurkey> fkkk
[17:18] <MutantTurkey> lets hope apt has enough magic to fix it
[17:18] <Resistance> ugh, did i mention i hate explosions of computers?
[17:18] <Resistance> i cant use IRC on Windows because of weird explosions in C :/
[17:19] <Resistance> so sorry i disappeared there for a while :P
[17:19] <MutantTurkey> huh
[17:21] <MutantTurkey> I'm defiintely screwed.
[17:21] <MutantTurkey> this upgrade is going to hell
[17:21] <MutantTurkey> back to arch!
[17:22] <Resistance> heh.
[17:22] <Resistance> has pennbot worked for you all?  do we need to add additionaal plugins? (I know we need additional admin level users)
[17:22] <MutantTurkey> what happened to old pennbot?
[17:22] <Resistance> it was exploded and taken down by its operator
[17:22] <Resistance> i volunteered to bring a new one up
[17:23] <MutantTurkey> oh
[17:23] <MutantTurkey> that is sad
[17:23]  * Resistance subsequently got the old PennBot nick dropped and added to the current nickserv for this PennBot
[17:23] <Resistance> yeah, well meh
[17:23] <Resistance> at least its been running with a decent uptime
[17:24] <MutantTurkey> good
[17:24] <Resistance> its running off of a netbook which is always on xD
[17:24] <MutantTurkey> wait for the raspberry pi
[17:29] <MutantTurkey> jedijf: hey around? i need emotional support as my ubuntu install is rapidly going down the drain
[17:29] <MutantTurkey> it kicked out while upgrading
[17:30] <MutantTurkey> i rebooted and all the repositories are set to onieric now, so i am just apt-get distro-uprading it
[17:30] <MutantTurkey> sound legit?
[19:19] <ChinnoDog> My Banshee refuses to buffer streaming radio stations so it won't play right
[19:19] <ChinnoDog> I blame lamal666
[19:19] <lamal666> nope, not my code
[19:19] <ChinnoDog> oh, ok. haha
[19:20] <ChinnoDog> Do you know how to fix it?
[19:20] <lamal666> no
[19:21] <ChinnoDog> There don't even seem to be any settings for streaming anywhere
[19:24] <ChinnoDog> Doesn't look like anyone can do it
[19:24] <MutantTurkey> banshee
[19:24] <MutantTurkey> seriously people use that?
[19:24] <MutantTurkey> almost as ridiculous as songbird.
[19:24] <ChinnoDog> What should I use?
[19:25] <MutantTurkey> rhythmbox?
[19:25] <MutantTurkey> I use moc however. I also like gogglesmm for slow machines
[19:28] <ChinnoDog> http://www.linuxjournal.com/article/10732
[19:28] <ChinnoDog> Short review but I like it
[19:29] <ChinnoDog> I keep finding myself drawn to KDE apps
[19:30] <MutantTurkey> I use kde3.5
[19:30] <MutantTurkey> it's great
[19:30] <ChinnoDog> I may have to try it
[19:30] <ChinnoDog> I've avoided KDE thus far just because it is another desktop environment to learn
[19:31] <MutantTurkey> that is true
[19:31] <MutantTurkey> It's quite different than Gnome 2
[19:32] <MutantTurkey> i've actually found myself always saying "i wish I had X feature". with both gnome and kde
[19:32] <MutantTurkey> always trade offs
[19:32] <MutantTurkey> the current series of kde I cannot stand however.
[19:32] <MutantTurkey> the same goes for Unity and Gnome3
[19:32] <MutantTurkey> kde 4, gnome 3 and unity were all half baked releases
[19:32] <ChinnoDog> I'm using xfce because it is lean
[19:33] <ChinnoDog> But if I keep installing KDE apps I might as well use KDE since I will be loading all the KDE libraries anyway
[19:33] <MutantTurkey> xfce is a solid desktop
[19:33] <MutantTurkey> what gnome should be
[19:33] <MutantTurkey> it doesn't do terrible much however
[20:06] <Sadin> ChinnoDog
[20:07] <MutantTurkey> Sadin
[20:07] <Sadin> all i can say is the new kde 4 is a little upsetting coming from other desktop enviornments such as gnome or xfce i would use xfce MutantTurkeys project hes involved with TDE (a fork of kde 3.5 [the good kde])
[20:08] <Sadin> xfce or tde :P
[20:08] <Sadin> yes MutantTurkey :D
[20:08] <ChinnoDog> Sadin: what is wrong with kde4?
[20:08] <MutantTurkey> BLOAT BLOAT BLOAT BLOAT BLOAT
[20:09] <Sadin> ChinnoDog the workflow is SO much different coming from other WMs in my opinion
[20:09] <Sadin> and yes BLOAT
[20:09] <MutantTurkey> i don't need nepomuk. stay the hell away!
[20:09] <Sadin> however MutantTurkey they have made some optomizations in speed that are alot better then kde 3,5 was
[20:09] <MutantTurkey> If i want to use 1 kde4 app, I DON'T want nepomuk and virtuoso indexing everything
[20:09] <MutantTurkey> Sadin:definitely a lot of improvements
[20:09] <MutantTurkey> but, the style is changfed
[20:10] <Sadin> MutantTurkey the style looks find too to me its just the way work is dont in kde 4 reminds me too much of my windows system
[20:10] <MutantTurkey> yeah I hate the look
[20:10] <Sadin> and discourages me from even doing work but thats my own opinion
[20:10] <MutantTurkey> it looks like to glossy and plastic
[20:10] <Sadin> MutantTurkey gotta make packages for fedora today
[20:11] <Sadin> Pleia2 got me involved with the shimmer project and ive been helping out to get Shimmers themes into fedora xfce and its a okay so far :D im really happy cause its my first major contribution to Open source
[20:11] <MutantTurkey> gotta make packages for what?
[20:12] <MutantTurkey> that's awesome
[20:12] <MutantTurkey> contributing to foss stuff is the reason I am doing computers
[20:12] <Sadin> MutantTurkey packaging up the shimmer projects themes for fedora and maintaining them
[20:12] <MutantTurkey> wow cool
[20:12] <Sadin> i know :D
[20:14] <Sadin> MutantTurkey also got my drupal powered website up and running last night ive been busy busy busy http://sadin.ifndev.com/
[20:14] <Sadin> going to blog about what i do with Web Design Fedora Design Team, Drupal, and Shimmer :)
[20:15] <MutantTurkey> cool
[20:15] <MutantTurkey> looking at it now
[20:15] <MutantTurkey> looks legit
[20:17] <Sadin> MutantTurkey its got alot of work to go but its making its way
[20:17] <MutantTurkey> still pretty cool
[20:17] <Sadin> thanks :)
[20:17] <MutantTurkey> jedijf: remember that time I tried to setup a web site and it took me like 4 days
[20:17] <MutantTurkey> lol
[20:17] <MutantTurkey> so dumb back then
[20:17]  * Sadin likes fuel wordpress and drupal and RubyOnRails
[20:18] <ChinnoDog> Sadin: MutantTurkey: I will explore the default Kubuntu install first. Then if it sucks I will look at TDE. (Is that Trinity?)
[20:18] <Sadin> ChinnoDog what do you use now
[20:18] <MutantTurkey> yes
[20:18] <MutantTurkey> tde is hand in hand
[20:18] <ChinnoDog> Xubuntu
[20:19] <MutantTurkey> with trinity
[20:19] <MutantTurkey> I call it Trinity Desktop
[20:19] <Sadin> ChinnoDog whats wrong with Xubuntu?
[20:19] <ChinnoDog> My favorite apps are KDE based
[20:19] <Sadin> im using the xfce fedora spin (same thing) and i couldnt be happier
[20:19] <MutantTurkey> xfce limits my abilities for networking and integration
[20:19] <MutantTurkey> unfortunately
[20:19] <Sadin> Chinno dog ah well so are mine but i hate KDEs panels and widgets etc aka bloat
[20:19] <ChinnoDog> Also, I am going to be playing with BSD in the near future and they seem to like KDE
[20:20] <Sadin> imo using the best apps doesnt mean you need the entire enviornment with it cause technically you already have a KDE system installed on you PC your only using certain aspects of it when running the K based apps on xfce
[20:21] <MutantTurkey> Sadin: it's all about integration though
[20:21] <MutantTurkey> I like to use tde because i get everything working smoothly together
[20:21] <Sadin> MutantTurkey what doesnt integreat
[20:21] <MutantTurkey> with trinity I can do great integration. for example I am ssh'd into a server
[20:21] <Sadin> I dont see the problems you do or i am not as picky :P
[20:22] <MutantTurkey> nevermind my example then
[20:22] <Sadin> MutantTurkey heh i always have ssh open as well ( cant dream of my life without it)
[20:23] <Sadin> seriosuly im connected to my 2 vps's my FAS account and bitbucket all the time hehe
[20:23] <MutantTurkey> right
[20:24] <MutantTurkey> now with that, I am browising those apps in konqueror, then opening them in kate
[20:24] <MutantTurkey> very handy being able to use seemless network integration
[20:24] <Sadin> I see
[20:24] <MutantTurkey> with trinity apps seemlessly integrate into whatever network you are attached to
[20:25] <Sadin> i guess im more of a terminal fella :P
[20:25] <MutantTurkey> me too
[20:25] <MutantTurkey> don't worry
[20:25] <Sadin> cause gnome can do that same exact thing as well
[20:25] <MutantTurkey> I am a 100% terminal guy
[20:25] <MutantTurkey> gnome is a lot less easy about it
[20:25] <MutantTurkey> :-P
[20:25] <MutantTurkey> this is just like a breeze
[20:25] <Sadin> :O how so
[20:25] <MutantTurkey> I dunno
[20:25] <Sadin> thought it was pretty straighht forward lol
[20:25] <MutantTurkey> gnome was always crap for me
[20:25] <Sadin> Gnome2 i loved gnome3 i fell off... hard
[20:25] <MutantTurkey> mostly because the FM sucks in gnome and xfce
[20:26] <Sadin> anyway MutantTurkey i gotta reboot
[20:26] <Sadin> ill brb
[20:26] <MutantTurkey> okay
[20:29]  * Sadin returns
[20:41] <adom> MutantTurkey: you don't like Nautilus? why not just use a different one then instead of writing off the whole WM?
[20:42] <MutantTurkey> because that is the core of the wm?
[20:43] <adom> fair enough i guess, but couldnt you just install a different FM?
[20:43] <adom> i see your point
[20:43] <MutantTurkey> there aren't any good viable gtk alternatives. Thunar is a ripoff of nautilus
[20:43] <adom> well, i guess what im asking is, what non-console-based FMs do you like?
[20:43] <adom> if any
[20:43] <MutantTurkey> Konqueror 3.5
[20:44] <MutantTurkey> for it's kparts embedding
[20:44] <MutantTurkey> when I open a file, it nicely embeds it in the same window.
[20:44] <MutantTurkey> so when I click on a image, it doesn't launch a new program
[20:44] <MutantTurkey> it just opens it up within itself
[20:44] <ChinnoDog> ugh. My desktop was all fubar. I killed processes one at a time trying to enable me to move windows again and gave up and rebooted
[20:44] <MutantTurkey> same for movies, text files
[20:44] <MutantTurkey> everything
[20:44] <MutantTurkey> and it has a web browser
[20:44] <MutantTurkey> profile support
[20:44] <MutantTurkey> extensions,
[20:45] <MutantTurkey> lets me do cool stuff by accessing kio slaves
[20:45] <MutantTurkey> I can do apt:/ and it lets me browser my packages for example
[20:45] <MutantTurkey> remote:/ for remote shares and so on
[20:45] <adom> does that cause Konquerer to jack your memory?
[20:46] <adom> so you're basically using Konquerer as your WM, not KDE.
[20:46] <adom> i.e. all you need is Konquerer
[20:47] <adom> someday ill have to sit down with KDE and talk about our feelings
[20:47] <adom> maybe we can work something out
[20:47] <adom> like adults
[20:48] <MutantTurkey> meh
[20:48] <MutantTurkey> it allows me to smoothly do stuff
[20:48] <MutantTurkey> when I close the tab, that program closes
[20:48] <MutantTurkey> it just embeds the window nicely
[20:48] <MutantTurkey> it's good for browsing a lot of stuff
[20:48] <MutantTurkey> I use it to preview
[20:49] <adom> but before that happens, i need a romp in the sack with Arch (probably Archbang because I'm lazy) and Awesome2
[20:49] <MutantTurkey> adom: ppffft go with scrotwm
[20:49] <MutantTurkey> that's all the tiling i'll ever need :P
[20:49] <MutantTurkey> I am a tiler at heart
[20:49] <adom> i like having new/seperate windows pop up for seperate programs
[20:49] <adom> just how i do
[20:50] <MutantTurkey> yeah makes sense
[20:50] <adom> i love my screen setup with seperate regions, so i need to try out a "tiling-based" WM
[20:51] <adom> since im so used to aptitude, would trying out pacman be hard to transition to?
[20:52] <MutantTurkey> NO
[20:52] <MutantTurkey> pacman is 10000 times better
[20:52] <MutantTurkey> its faster and easier and simpler and sane and kiss
[20:52] <MutantTurkey> I LOVE PACMAN IT'S THE BEST
[20:52] <MutantTurkey> :)
[20:52]  * MutantTurkey also forgot to mention he is a arch diehard
[20:52]  * adom peers left and right at the rest of #ubuntu-us-pa and steps away from MutantTurkey.
[20:52] <MutantTurkey> lol
[20:52] <MutantTurkey> they already know i'm weird
[20:52] <adom> haha
[20:53] <MutantTurkey> it must have been that nuclear meltdown that happened down the farm from me...
[20:53] <adom> well my fear is the complexity of Arch
[20:53] <adom> nah that wasnt it
[20:53] <MutantTurkey> lol
[20:53] <MutantTurkey> arch is 50000 times simpler
[20:53] <MutantTurkey> :)
[20:53] <adom> bollux
[20:53] <adom> you have to do everything from scratch
[20:53] <MutantTurkey> nothing is changed. ubuntu messes with everything
[20:53] <MutantTurkey> no you don't
[20:53] <adom> which is pretty much the polar opposite of ubuntu
[20:53] <MutantTurkey> everything just comes vanilla
[20:53] <MutantTurkey> there is no special way to do anything in arch
[20:53] <MutantTurkey> it's all upstream
[20:53] <MutantTurkey> so that means you don
[20:53] <adom> thats all jargon to me
[20:54] <MutantTurkey> 't get mangled versions or old versions
[20:54] <MutantTurkey> everything is upstream.
[20:54] <adom> yeah that
[20:54] <adom> like fish?
[20:54] <MutantTurkey> I consider it the most "linux" linux.
[20:54]  * adom chuckles
[20:54] <MutantTurkey> hehe
[20:54] <adom> i would agree (not having used it before, but from what ive read)
[20:54] <Sadin> MutantTurkey arch is a great distro but its not the most simple
[20:55] <MutantTurkey> define simple?
[20:55] <adom> the funny thing i like is that pretty much every answer in #arch is "RTFM" because its so in depth you cant grasp it until you learn it entirely
[20:55] <MutantTurkey> adom: you have to do some work
[20:55] <adom> simple = "easy to use" in my book
[20:55] <Sadin> the level of knowledge needed for a new linux user to jump into ubuntu or say fedora is far lowet then arch
[20:55] <MutantTurkey> but they'll also help you
[20:55] <adom> with means ubuntu
[20:55] <MutantTurkey> if you go to #arch and say "I ham having X, Y and Z issues, I read A B C and tried D E F
[20:55] <MutantTurkey> they'll help
[20:55] <adom> Mint is nice for new users also, though its a derivative of ubuntu
[20:55] <MutantTurkey> but our wiki is fantastic, and covers everything
[20:55] <MutantTurkey> adom: not anymore, it's debian based now?
[20:56] <adom> no shit. hmm
[20:56] <adom> meh
[20:56]  * adom shrugs.
[20:56] <adom> still like Mint
[20:56] <adom> i debated switching from ubuntu to Mint when ubuntu 11 released with unity
[20:56] <MutantTurkey> lol unity
[20:56]  * adom spits on the floor.
[20:56] <MutantTurkey> halfbaked crap
[20:57] <adom> still need to try gnome3, but dont have high hopes for it
[20:57] <adom> i like my linux easy to use (i.e. ubuntu atm) and lightweight (gnome2 atm)
[20:58] <Sadin> got MutantTurkey the trinity mirrors have been going down left and right :/
[20:58] <adom> if i wanted a bloated graphics display id use only my Windows7 machine
[20:58] <MutantTurkey> Sadin: what?
[20:58] <MutantTurkey> I just upgraded to onieric with notrouble...
[20:58] <MutantTurkey> rebooting now
[20:58] <MutantTurkey> wish me luck
[20:58] <Sadin> MutantTurkey i keep failing to connect to the mirrors and i entred the through copy/paste
[20:58] <adom> gluck
[21:07] <lamalex> ha, my irc hilight for bong has been set off 4 times today, none of them for what i expect
[21:08] <ChinnoDog> lol
[21:10] <MutantTurkey> it worked
[21:13] <adom> runnin unity now?
[21:14] <MutantTurkey> no
[21:14] <MutantTurkey> the oneirc upgrade
[21:14] <MutantTurkey> it sucks though
[21:14] <MutantTurkey> fscked up a lot of stuff I had
[21:14] <adom> that's what you get.
[21:14] <adom> for trying to move past dependable ubuntu 10
[21:14] <MutantTurkey> for using shitty ubuntu.
[21:15] <MutantTurkey> sigh
[21:15] <adom> haha
[21:15] <adom> speaking of, downloading archbang iso now
[21:15] <adom> gonna toss in a vm and mess around
[21:15] <MutantTurkey> why are you downloading archbang?
[21:18] <adom> because its arch, but easy mode
[21:19] <MutantTurkey> pfft
[21:20] <adom> i just dont feel like spending 4 hours learning how to start up my linux distro
[22:13] <jedijf> adom: arch is a lot easier than everyone thinks
[22:13] <jedijf> adom: nike
[22:17] <jedijf> hate konqueror kate is liveable linux is awesome because of these differences of opinions/systems/trials and in everyone else's case...errors
[22:28] <JonathanD> got a 10x10 screen gazebo
[22:41] <adom> jedijf: nike?
[22:42] <Sadin> adom i would assume that means nice
[22:42] <Sadin> :P
[22:42] <adom> "nice" doesnt seem to have context in the conversation
[22:42]  * adom shrugs.
[22:42] <adom> anywho. im out for the night, back tomorrow.
[22:45] <Sadin> see ya


[05:26] <fabbione> morning
[05:58] <svenl> hi fabbione
[05:59] <svenl> fabbione: i tried to build mplayer yesterday, and it failed because of some altivec includes.
[05:59] <svenl> fabbione: and the existing powerpc packages seem to lack the actual binary.
[07:52] <fabbione> ok ladies and gentlement
[07:52] <fabbione> we need a new kernel release name/series
[07:53] <fabbione> votes are open :)
[07:53] <fabbione> JaneW: since when you are interested in the kernel? :)
[07:53] <crimsun> hmm, as in "Bite the Dildo" names?
[07:53] <crimsun> oh wait, that was probably inappropriate
[07:54] <dilinger> fabbione: still going for food names?
[07:55] <fabbione> dilinger: well we can do whatever we like
[07:55] <fabbione> i was considering some kind of flexibility
[07:55] <crimsun> 'lo JaneW
[07:55] <fabbione> like hurricanes name for unstable releases
[07:55] <fabbione> and something else for stable releases
[07:55] <fabbione> or whatever..
[07:55] <fabbione> i am really open to suggestions
[07:56] <fabbione> i think 91-1.1 is ready to go out of the door
[07:56] <JaneW> hi crimsun
[07:56] <JaneW> fabbione, just browsing
[07:56] <JaneW> fabbione: besides I am interested in all things ubuntu related ;)
[07:56] <fabbione> JaneW: be aware.. this is the channel of the truth of death :P
[07:57] <crimsun> <IP_ADDRESS>-1 is working great
[07:57] <fabbione> crimsun: good to know
[07:57] <fabbione> 91-1.1 will hit the archive today
[07:57] <fabbione> 92 is already a work in progress
[07:57] <crimsun> ooh!
[07:57] <fabbione> i just need the name for 91-1.1
[07:58] <crimsun> it'll be the stable branch, right?
[07:58] <fabbione> nope
[07:58] <fabbione> this is unstable
[07:58] <crimsun> oh, 9x
[07:58] <fabbione> 91 = 12rc3
[07:58] <crimsun> right
[07:58] <fabbione> 92 =12rc4
[07:58] <fabbione> so whatever
[07:58] <fabbione> we need something cool tho
[07:58] <fabbione> nobody is going to read a 200 lines changelog anyway
[07:59] <crimsun> what about ferocious predators for the unstable branch and docile animals for the stable?
[07:59] <fabbione> hmmmmm
[08:00] <dilinger> how about ornery kernel hackers for the unstable branch and huggable ones for the stable branch? :)
[08:00] <dilinger> you could start w/ al viro for the first unstable
[08:00] <fabbione> dilinger: examples? :)
[08:01] <fabbione> hmmm i am afraid that using people names might create political issues
[08:01] <fabbione> people might not like it
[08:02] <crimsun> funny, I was thinking Al, too ;)
[08:03] <fabbione> The "Phantom Mance" Release
[08:03] <fabbione> Menace
[08:03] <dilinger> crimsun: when i think of kernel hackers who put the fear of god into me, i think of al
[08:04] <dilinger> and that's saying a lot, since i'm an atheist :p
[08:05] <fabbione> i have an idea
[08:05] <fabbione> let's use the weirdest sex positions, md5sum encoded
[08:05] <fabbione> and see who is going to guess them :)
[08:05] <fabbione> kinda of a contest ;)
[08:05] <dilinger> i'd recommend that w/out the md5sum encoding ;)
[08:06] <fabbione> dilinger: pig! :P
[08:06] <crimsun> yeah, the md5sum would be even worse than the current numbering scheme ;)
[08:06] <crimsun> we could just rot13 'em
[08:06] <Lathiat> that would be evilly cool
[08:06] <fabbione> Lathiat: the md5 or the rot?
[08:07] <Lathiat> rot
[08:07] <fabbione> do we have a cmd line tool to rot encode?
[08:07] <dilinger> fabbione: give the people what they want!  the reverse cowgirl kernel release..
[08:07] <Lathiat> yeh |rot13
[08:07] <Lathiat> i think its in bsdgames
[08:07] <Lathiat> or
[08:07] <Lathiat> just use the tr command
[08:08] <Lathiat> theres a string for tr somewhere
[08:08] <Lathiat> i dont know it
[08:08] <Lathiat> google should
[08:08] <fabbione> dilinger: ahhaa
[08:09] <crimsun> yeah, straightforward and simple
[08:10] <fabbione> sexy_rodeo == Put your woman doggie style, grab her by her tits and penetrate her. When you are in, tell her "did you know this is the position your sister likes most?" then you have to stay up for at least 8 seconds
[08:11] <dilinger> yea, i wouldn't recommend including the explanations.  or including words with sexual connotations.
[08:11] <fabbione> dilinger: clearly :)
[08:12] <Lathiat> heh
[08:12] <fabbione> it was only an answer to the cowgirl thingy :)
[08:12] <dilinger> hehe
[08:16] <fabbione> ok.. we must get a name
[08:20] <dholbach> will there be silly animal names for the kernel as well? ;-)
[08:22] <fabbione> dholbach: any proposal is good :)
[08:22] <fabbione> go ahead with your
[08:22] <dholbach> i'd love to have SneezySnail somewhere ;-)
[08:22] <crimsun> hmm, speed is another good idea
[08:22] <crimsun> could even combine that with the ferocious/docile thing
[08:22] <dholbach> but i'll think of something else
[08:22] <fabbione> dholbach: i would like to avoid name clashes with releases
[08:23] <dholbach> of course
[08:23] <dholbach> but SneezySnail will hopefully never be a release name ;-)
[08:23] <Lathiat> sneezysnail would be a nice release name :)
[08:24] <dholbach> i think it was keybuk's idea :)
[08:43] <dholbach> see you
[10:15] <fabbione>   The "amok" Release.
[10:15] <fabbione> what about this one? :)
[10:17] <jbailey> Bah, I'm going to bed.
[10:17] <jbailey> Too tired to finish the lkh bits tonight.
[10:17] <fabbione> jbailey: good night dude :)
[10:18] <jbailey> g'n. =)
[10:41] <fabbione> JaneW: you here?
[10:57] <JaneW> fabbione: yes - on phone
[10:57] <fabbione> sure.. take your time
[11:03] <JaneW> fabbione: ok done, - how can I help?
[11:03] <fabbione> JaneW: we need a release name for the kerenl
[11:03] <fabbione> kernel
[11:03] <fabbione> something that indicates that it is pure crack :)
[11:07] <JaneW> hehehe
[11:07] <JaneW> gimme examples of what you;ve had...
[11:07] <fabbione> or something with a "pink" touch.. but than you will commit to find names for the whole breezy release cycle :)
[11:07] <fabbione> JaneW:   The "Succulent Strawberries" Release.
[11:07] <JaneW> ;)
[11:08] <fabbione>   The "Radioactive Radish" Release.
[11:08] <fabbione>   The "Atomic Artichoke" Release.
[11:08] <fabbione> now.. we reserved veggie for hoary
[11:08] <JaneW> ok
[11:08] <fabbione> but food is limited
[11:08] <fabbione> so we need to get a new cathegory too :)
[11:09] <JaneW> ice-cream flavours...?
[11:10] <JaneW> can get orett outrageous
[11:10] <JaneW> pretty even
[11:10] <fabbione> JaneW: that would work too...
[11:10] <JaneW> Pecan Swirl
[11:10] <fabbione> fire some  :)
[11:10] <fabbione> PS <- ???
[11:10] <fabbione> we use a similar convention to release names
[11:11] <fabbione> like Hoary H.
[11:11] <fabbione> so same first letter
[11:11] <fabbione> that's what make it a bit harder ;)
[11:11] <JaneW> ok
[11:11] <JaneW> Rocky road
[11:12] <JaneW> Praline pecan
[11:12] <fabbione> something like that...
[11:12] <JaneW> Chocolate chip
[11:14] <fabbione> http://www.recipesource.com/desserts/ice-cream/00/rec0095.html
[11:14] <JaneW> thinks harder
[11:15] <JaneW> being a kernel... how about types of nuts?
[11:15] <JaneW> a bit of a play on the kernel think?
[11:15] <fabbione> sounds good..
[11:15] <JaneW> Happy Hazel
[11:15] <fabbione> let see how many flavours we have
[11:15] <JaneW> Perky Pecan
[11:16] <JaneW> Batty Brazilian
[11:16] <JaneW> Almond (the adjectives are hard)
[11:17] <JaneW> Pistacio (but starts with same letter as pecan and peanut)
[11:17] <JaneW> Crunchy Cashew
[11:17] <fabbione> http://waynesword.palomar.edu/ecoph8.htm
[11:17] <JaneW> Wacky Walnut
[11:18] <JaneW> PInnut
[11:18] <JaneW> Pinenut
[11:18] <fabbione> ok you convinced me
[11:18] <JaneW> Walnut
[11:18] <JaneW> etc
[11:19] <fabbione> which one would you like to see as first?
[11:19] <JaneW> happy to help
[11:19] <JaneW> Chestnut, Macadamia
[11:19] <JaneW> plus Badgers eat nuts
[11:19] <JaneW> I think
[11:20] <JaneW> first one er...
[11:20] <fabbione> eheh i think so too
[11:20] <JaneW> Hazel - like the one in ice age
[11:20] <JaneW> oh no that was an acorn ;)
[11:20] <JaneW> sort of the same
[11:20] <fabbione> done
[11:20] <JaneW> yay
[11:21] <fabbione> now you will be doomed for the whoile breezy process in reminding us nuts names ;)
[11:21] <JaneW> so can I put 'contributed to Ubuntu Kernel' in my CV now? ;)
[11:22] <fabbione> JaneW: sure:
[11:22] <fabbione> linux-source-2.6.12 (<IP_ADDRESS>-1.1) breezy; urgency=low
[11:22] <fabbione>   The "Happy Hazel" Release.
[11:22] <fabbione>   Welcome to JaneW as our new name release manager that kindly offered
[11:22] <fabbione>   volunteer to find nuts names for our kernel.
[11:22] <fabbione>   Changes by Fabio M. Di Nitto:
[11:22] <fabbione> this will appear shortly on ubuntu-changes...
[11:22] <JaneW> heehee
[11:31] <Seveas> Is the next one going to be "Mad Macadamia"?
[12:01] <svenl> here is maybe more appropriate.
[12:01] <svenl> Is DVD burning supposed to work on the ppc kernel ?
[12:01] <svenl> # growisofs -Z /dev/hdc=archive.iso
[12:01] <svenl> Executing 'builtin_dd if=archive.iso of=/dev/hdc obs=32k seek=0'
[12:01] <svenl> :-[ PERFORM OPC failed with SK=3h/ASC=73h/ACQ=03h] : Input/output error
[12:02] <svenl> seems not to be the case.
[12:04] <fabbione> i got that error with a broken burner
[12:05] <svenl> fabbione: well, the burner worked fine under mac os X, so ...
[12:05] <svenl> and the exact same brand of media.
[12:06] <svenl> will try building cdrecord with the DVD patch.
[12:07] <fabbione> svenl: i had really weird issues with my burner
[12:07] <fabbione> like it was partially working with windows
[12:07] <fabbione> but not in linux
[12:07] <svenl> fabbione: and on amd64, my burner still doesn't want to do DMA burning, and is thus very very slow.
[12:07] <fabbione> and sometimes viceversa
[12:07] <fabbione> 2 or 4 burns didn't really show the problem
[12:07] <svenl> fabbione: well, as this is the default powerbook burner, i guess lot of people, like maybe Kamion or benh, have been using it.
[12:08] <fabbione> svenl: that's not the point.. if your specific burner is broken...
[12:08] <fabbione> i had a lite-on
[12:08] <fabbione> that is very well known brand
[12:08] <svenl> well.
[12:08] <fabbione> probably i was the only one with that problem
[12:09] <svenl> yep.
[12:10] <svenl> but in this case, chances are good that it is a software problem, especially given the history of it.
[12:10] <svenl> Mmm, cdrtools broken patch number 40 didn't get fixed for hoary :/
[12:10] <svenl> I am sure i reported this one months ago.
[12:26] <svenl> damn, cdrecord fails too.
[12:46] <zul> hey
[12:49] <svenl> hi zul
[12:49] <zul> hey svenl
[12:51] <fabbione> hey zul
[12:51] <zul> hey fabbione
[12:52] <fabbione> meh
[12:53] <zul> heh shouldnt that be pre1.1
[12:53] <fabbione> it was i typo when i did the branch
[12:53] <zul> ah ok
[12:55] <zul> at least i can close a whole bunch of bugs today
[12:56] <fabbione> yeah go ahead
[12:56] <fabbione> i didn't process bugzilla
[01:03] <fabbione> zul: mind to close mine too?
[01:03] <zul> sure
[01:03] <fabbione> or did you close all of them?
[01:03] <zul> ill just go through the changelog :)
[01:03] <fabbione> thanks
[01:03] <fabbione> or search for linux/PENDINGUPLOAD
[01:04] <zul> yep
[01:05] <zul> need to go potty
[01:12] <fabbione> zul: orig/dsc/diff.gz in the usual place
[01:12] <fabbione> for 92 i mean
[01:12] <zul> ok...
[01:13] <fabbione> sorry.. dsc and diff are still on the way
[01:13] <zul> not a problem...i just woke up :)
[01:13] <fabbione> that's why i am trying to be more detailed
[01:17] <fabbione> ok they are up now
[01:30] <zul> see this is what is bad about source base distros look at this guys CFLAGS http://bugs.gentoo.org/show_bug.cgi?id=74072
[01:32] <fabbione> hahahaha
[02:35] <fabbione> i am going off line for a while
[02:35] <fabbione> 92 is building everywhere
[02:35] <fabbione> i still need to commit the config changes
[02:35] <fabbione> but they are trivial
[02:36] <zul> yeah i noticed :)
[02:36] <fabbione> i am at patch5 :)
[02:36] <zul> im building it as well with some of my patches
[02:36] <fabbione> it has a fix for ia64
[02:36] <fabbione> rocking
[02:36] <fabbione> i will be back later
[02:36] <zul> k
[02:36] <fabbione> and if you are ready i can start merging from you
[02:37] <zul> ill let you know :)
[04:00] <zul> argh..
[04:01] <fabbione> argh what?
[04:02] <zul> that external driver that was in bugzilla doesnt build
[04:02] <fabbione> no shit...
[04:02] <fabbione> is that the dxr3+ driver?
[04:02] <zul> yep
[04:02] <fabbione> hmmmm
[04:02] <fabbione> it depends how it fails
[04:02] <fabbione> probably the fix is easy
[04:02] <zul> i might have found a fix already i2c.h changes
[04:03] <fabbione> ok
[04:03] <zul> er...i2c.h changed
[04:04] <zul> hey dilinger how goes it?
[04:04] <fabbione> dilinger: started the new work?
[04:04] <dilinger> not bad.  i really need a place to live
[04:04] <dilinger> fabbione: yea, last week
[04:05] <fabbione> is it any good?
[04:07] <dilinger> it's work :)
[04:07] <dilinger> it's not too bad
[04:08] <dilinger> i spent friday getting comfortable w/ openafs source
[04:08] <dilinger> it's impressively ugly
[04:08] <fabbione> amen...
[04:08] <fabbione> is it worth the inclusion in the kernel?
[04:08] <dilinger> i don't think it's license allows it
[04:08] <dilinger> i brought it up on the list
[04:08] <fabbione> isn't it gpl now?
[04:08] <dilinger> s/it's/its/
[04:09] <dilinger> ibm public source
[04:09] <dilinger> pity, it would be nice to have it in the kernel (once it's cleaned up a bit)
[04:10] <fabbione> i can't find the licence on the page
[04:11] <dilinger> http://openafs.org/frameset/dl/license10.html
[04:12] <fabbione> scary
[04:14] <fabbione> i need a shower :)
[04:14] <fabbione> bbl
[04:14] <fabbione> even the most hardcore developer does wash once a month
[04:19] <dilinger> heh
[04:19] <dilinger> needs some performance tuning..
[04:19] <dilinger> dilinger@furious13:~ $ time cp openafs-1.3.82-src.tar.gz  foo
[04:19] <dilinger> real    3m9.146s
[04:19] <dilinger> 13MB file
[04:52] <dilinger> i wonder how well kafs performs
[05:54] <fabbione> why...
[05:54] <fabbione> why...
[05:54] <fabbione> why PPC IS SO RETARDED?
[05:54] <Lathiat> it has a personal vendetta agianst you fab
[05:55] <zul> i blame T-Bone
[05:55] <fabbione> it's because i don't own one.. yet
[05:55] <fabbione> drivers/built-in.o(.pmac.text+0x2d10): In function `pmac_wakeup_devices':
[05:55] <fabbione> : undefined reference to `pmac_tweak_clock_spreading'
[05:55] <fabbione> drivers/built-in.o(.pmac.text+0x3548): In function `pmac_suspend_devices':
[05:55] <fabbione> : undefined reference to `pmac_tweak_clock_spreading'
[05:55] <fabbione> this is 12rc4
[05:55] <zul> no idea..
[05:58] <fabbione> every fucking release is the same story
[05:58] <zul> drop ppc support :)
[06:01] <fabbione> that would be sane
[06:01] <zul> yay...something im actually qualified to do
[06:20] <fabbione> http://people.ubuntu.com/~lamont/buildLogs/l/linux-source-2.6.12/<IP_ADDRESS>-1.1/
[06:20] <fabbione> yay
[06:20] <fabbione> they start to appear :)
[06:22] <Lathiat> woo
[06:22] <Lathiat> you guys rock.
[06:23] <zul> we do
[06:25] <fabbione> let say we suck less than other teams :)
[06:25] <Lathiat> haha
[06:26] <zul> damn i have to clean the house today
[06:26] <fabbione> i can do the patch for you
[06:26] <fabbione> ops
[06:26] <zul> you can patch it? :)
[06:26] <zul> lol
[06:26] <fabbione> zul: just run make clean
[06:27] <fabbione> make -f zul clean
[06:27] <zul> dist-clean more like it
[06:30] <zul> yay it builds
[06:34] <fabbione> hey jeff!
[06:35] <jbailey> Heya Fabio! (and everyone)
[06:37] <jbailey> When is linux-headers-2.6.10-5 going away?
[06:37] <jbailey> I want to upload klibc this morning.  the lkh network bits all assume that glibc is present on the system, and I want to make sure that the upstream guy agrees with what I'm doing before I revert a pile of his changes.
[06:37] <fabbione> jbailey: after we will make 2.6.12 the default kernel
[06:38] <fabbione> in not too long i think
[06:38] <jbailey> 'kay, so I have a week, probablyl
[06:38] <fabbione> if not more....
[06:38] <fabbione> we don't know when .12 final will be out
[06:38] <fabbione> and 12rc4 is not encouraging atm
[06:38] <jbailey> Ugh, really?
[06:38] <fabbione> ppc is broken
[06:38] <jbailey> I thought I had seen decent reports for rc3.
[06:39] <fabbione> when right this morning benh told me that 12rc4 is perfect on ppc
[06:39] <fabbione> well it doesn't even compile...
[06:39] <jbailey> Compiler skew between you and benh?
[06:39] <fabbione> drivers/built-in.o(.pmac.text+0x2d10): In function `pmac_wakeup_devices':
[06:39] <fabbione> : undefined reference to `pmac_tweak_clock_spreading'
[06:39] <fabbione> drivers/built-in.o(.pmac.text+0x3548): In function `pmac_suspend_devices':
[06:39] <fabbione> : undefined reference to `pmac_tweak_clock_spreading'
[06:39] <fabbione> this is just bad code
[06:39] <fabbione> nothing to do with the compiler
[06:40] <jbailey> Right. =)
[06:40] <fabbione> since benh is working on G5
[06:40] <fabbione> everything else is broken
[06:40] <fabbione> and unsupported
[06:41] <fabbione> at this speed rate i will have to ask either for an official ppc porter
[06:41] <fabbione> or get rid of ppc as supported arch
[06:41] <jbailey> Hmm.
[06:41] <jbailey> I wonder if I have the skills to get into ppc porting at all.
[06:41] <fabbione> ppc is the post problematic arch i have ever seen
[06:41] <fabbione> you fix power3 and you break power4
[06:41] <jbailey> Right, that's the scary part.
[06:41] <jbailey> I have a newworld and a g5.
[06:41] <fabbione> you change a line for powerpc and you break power3-smp
[06:42] <fabbione> it's really fucking annoying
[06:45] <jbailey> ah, nice.  the linux-headers /usr/src/linux-headers-2.6.10-5/include/asm seems to be pointed right per-arch.
[06:46] <fabbione> http://drunkendelight.com/content/picture/02213994.jpg
[06:46] <fabbione> AHNHAHAHA
[06:46] <fabbione> jbailey: yes, it's per arch
[06:47] <jbailey> Yeah, I just remember that last time I looked at the package (a year or two ago in Debian) it was not.
[06:47] <jbailey> fabbione: Oh dear.
[06:47] <jbailey> =)
[06:50] <zul> aw man..
[06:53] <zul> bbl
[07:07] <fabbione> jbailey: in anycase i wouldn't base anything on 2.6.10 for breezy
[07:07] <fabbione> just start using 2.6.12
[07:07] <fabbione> even if it is in universe
[07:08] <jbailey> Is it in universe?
[07:08] <jbailey> I saw that 2.6.11 is in there.
[07:08] <fabbione> it is on the way to universe
[07:08] <fabbione> only amd64 is there
[07:08] <fabbione> buildd are working on it
[07:08] <fabbione> unfortunatly the kernel takes ages to build without (shared) ccache
[07:17] <fabbione> r/wind goto 5
[07:17] <fabbione> ops
[07:32] <lamont> fabbione: ppc is on #5/6, i386 #5/5 (but has arch: all).  ia64, should anyone care, is on #2/4
[07:34] <fabbione> lamont: goody...
[07:34] <fabbione> what about hppa?
[07:34] <fabbione> lamont: i already opened the dances for 12rc4
[07:34] <lamont> fabbione: hppa is waiting for glibc
[07:34] <fabbione> ha
[07:34] <fabbione> i thought that was solved
[07:35] <lamont> s/solved/known/
[07:35] <lamont> and solution available.
[07:35] <lamont> it's a matter of time to add it
[07:35] <fabbione> ok
[07:35] <lamont> and that's due sometime soonish
[07:36] <fabbione> rocking
[07:37] <fabbione> lamont: btw.. don't get crazy to grab the ABI files from 91-1.1
[07:37] <lamont> heh
[07:38] <fabbione> it's pointless in the middle of RC's
[08:17] <fabbione> lamont: argh.. why did the kernel failed on i386????
[08:18] <fabbione> i DID BUILD ARCH ALL!
[08:18] <fabbione> openjade:/build/buildd/linux-source-2.6.12-<IP_ADDRESS>/debian/build/linux-source-2.6.12/Documentation/DocBook/wanbook.xml:3:61:E: error connecting to "www.oasis-open.org" (Connection timed out)
[08:18] <fabbione> there is something broken somewhere else
[08:19] <lamont> openjade:/build/buildd/linux-source-2.6.12-<IP_ADDRESS>/debian/build/linux-source-2.6.12/Documentation/DocBook/wanbook.xml:3:61:E: error connecting to "www.oasis-open.org" (Connection timed out)
[08:19] <lamont> fix openjade
[08:19] <fabbione> oh f**k
[08:20] <lamont> fabbione: and for future fun and joy, build in a chroot on a machine that is blocked from internet access
[08:21] <fabbione> I HATE THIS CRAP
[08:22] <fabbione> it was working before...
[08:22] <fabbione> it works from concordia....
[08:22] <fabbione> so that means that concordia has inet access
[08:25] <fabbione> 10567
[08:26] <zul> heylo
[08:26] <fabbione> bah
[08:26] <fabbione> all this work to get the kernel in
[08:26] <fabbione> and some retarded build-deps are broken
[08:28] <zul> xmlto?
[08:28] <fabbione> openjade
[08:28] <zul> stupid..
[08:30] <fabbione> lamont: can't we give one buildd net access to fetch that file in the meantime?
[08:35] <lamont> no
[08:35] <dilinger> [NETLINK] : Fix infinite loops in synchronous netlink changes.
[08:35] <dilinger> fun
[08:35] <fabbione> yeah i saw that
[08:35] <fabbione> lamont: ok
[08:35] <fabbione> dilinger: i started using git
[08:36] <fabbione> it's preatty nice.. i like it
[08:36] <fabbione> cg-log -c > baz diff
[08:36] <dilinger> is that related to Xu's netlink vuln fixes?
[08:36] <dilinger> http://www.kernel.org/git/gitweb.cgi?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=2a0a6ebee1d68552152ae8d4aeda91d806995dec
[08:36] <fabbione> dilinger: let me check
[08:37] <dilinger> fabbione: i'm not overly excited to use git, but for 2.6.12 i want to start up -as again.. which is going to require me to either use git, or write scripts to pull git stuff
[08:37] <dilinger> hopefully it's a bit more sane in the way it handles new changesets
[08:38] <fabbione> author David S. Miller<EMAIL_ADDRESS>Tue, 03 May 2005 15:30:05 -0700
[08:38] <fabbione>     [PKT_SCHED] : netetm: trap infinite loop hange on qlen underflow
[08:38] <fabbione> there is also this one that is pretty neat :)
[08:38] <dilinger> i like the colored diff output from git's web interface
[08:38] <dilinger> purty ;)
[08:39] <fabbione> yeah that one is nice too
[08:39] <dilinger> looks like they are related
[08:39] <lamont> <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
[08:39] <lamont>         "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" [] >
[08:39] <dilinger> -		while ((skb = skb_dequeue(&sk->sk_receive_queue)) != NULL) {
[08:39] <dilinger> +		while (qlen--) {
[08:39] <dilinger> +			skb = skb_dequeue(&sk->sk_receive_queue);
[08:39] <lamont> hrm... maybe it's kernel related....
[08:39] <dilinger> in xu's patch
[08:40] <dilinger> -		while (qlen--) {
[08:40] <dilinger> +		for (; qlen; qlen--) {
[08:40] <dilinger>  			skb = skb_dequeue(&sk->sk_receive_queue);
[08:40] <dilinger> in davem's
[08:40] <dilinger> heh, i never did end up meeting xu
[08:41] <dilinger> vibe out was too comfy :)
[08:41] <fabbione> dilinger: i did send him to you :)
[08:41] <dilinger> oh?
[08:41] <fabbione> dilinger: but he promised to be back on sat.. and he didn't show up
[08:42] <fabbione> lamont: i can try to build again arch all
[08:42] <fabbione> but i did it all the times on concordia
[08:42] <lamont> fabbione: I'll upload a new linux-source that fixes the problem, after I fix it...
[08:42] <lamont> unless you want to...
[08:42] <fabbione> lamont: do you know what the problem is?
[08:43] <lamont> well, given that openjade doesn't reference www.oasis-open.org, but the templates do in the kernel source, I'm betting that a patch is in order...
[08:43] <fabbione> hmmm
[08:43] <lamont> specifically, build-depend: docbook-xml and then change the URL to file:///usr/share/xml/docbook/schema/dtd/4.1.2/docbookx.dtd
[08:43] <fabbione> let me check if it is fixed upstream
[08:44] <lamont> note that they may consider it a useful thing to depend on net access to build...
[08:45] <fabbione> there is no difference upstream
[08:45] <fabbione> the question is why it fails only on that one
[08:45] <lamont> ??
[08:45] <fabbione> a lot of others have references to oasis
[08:46] <lamont> because after it fails on the first one, it stops trying???
[08:46] <fabbione> if you look at the build log other docbook stuff are built before the wanbook
[08:47] <lamont> ok
[08:47] <fabbione> hmmm
[08:47] <lamont> nfc
[08:47] <fabbione> no it builds DocBook/man
[08:47] <fabbione> and they have no reference to oasis
[08:48] <fabbione> bah this thing is so complicate
[08:49] <fabbione> <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook V3.1//EN"[] >
[08:49] <fabbione> <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"
[08:49] <fabbione>         "http://www.oasis-open.org/docbook/xml/4.1.2/docbookx.dtd" [] >
[08:50] <fabbione> this is the change from 2.6.10 to 2.6.12
[08:50] <fabbione> so clearly they did the right thing
[08:50] <fabbione> but that breaks our buildd
[08:50] <fabbione> and it is done on all documents
[08:50] <fabbione> you are right that it stops at the first one
[08:50] <lamont> right - but we have that file in the archive, if we want it...
[08:50] <fabbione> exactly
[08:50] <fabbione> so we need to patch all the documentation files
[08:50] <fabbione> brb for the meeting
[08:52] <zul> hmm...meeting?
[08:54] <zul> there is  a meeting today? sheesh i thought it was tomorrow
[08:55] <lamont> meeting
[08:55] <lamont> breezy kickoff
[08:55] <zul> meh
[08:56] <lamont> fabbione: so this means I get to make -1.2, eh?
[08:56] <lamont> should I just touch all the ignore-abi-changes files?
[08:56] <JaneW> zul: MONDAY, that's today ;)
[08:57] <zul> JaneW: im on "holiday" ;)
[08:57] <lamont> JaneW: isn't it already tuesday for you, though??? :-)
[08:57] <JaneW> lamont: nope it's almost 9pm
[08:59] <lamont> fabbione: building something to test on my net-restricted hppa buildd.
[09:01] <fabbione> lamont: ok.. no rush
[09:01] <lamont> fabbione: yeah, but would be nice to have i386 there for rc3
[09:02] <fabbione> i still believe the right fix should go in openjade that should always prefer a local copy and in case the net if the local is not available
[09:02] <lamont> or will rc4 be ready for  upload shortly?
[09:02] <fabbione> lamont: rc4 is FTBFS on ppc and i have no clue why
[09:02] <lamont> fabbione: well, the kernel source _told_ it to use the net copy....
[10:42] <jbailey> fabbione: Is it the type of thing I could be useful to you at all for?  I don't have a ton of time, though.
[10:43] <fabbione> jbailey: i need somebody that can be there and it is not overloaded
[10:43] <jbailey> fabbione: Yeah, that's not me at the moment.
[10:43] <fabbione> jbailey: exactly
[10:44] <jbailey> fabbione: Maybe draft me once the toolchain transition and early userspace are finished.
[10:44] <jbailey> So in a month or so.
[10:45] <fabbione> jbailey: don't worry
[10:45] <fabbione> zul: just go for it
[10:45] <zul> i will
[10:46] <fabbione> merge it in .92-1.1
[10:46] <zul> yep just need to read up on it
[10:46] <fabbione> we also need to check if there is a unionfs that can actually build on ppc
[10:46] <fabbione> lamont: how is it going with the kernel test?
[10:46] <zul> wouldnt know...dont have access to ppc
[10:46] <fabbione> zul: yeah i know that :/
[10:47] <zul> where is he btw?
[10:47] <zul> any particular version of squashfs?
[10:47] <fabbione> the latest?
[10:47] <lamont> fabbione: well, it's about a 2 hour build to just let it run, so I was, um, letting it run.
[10:47] <lamont> s
[10:47] <fabbione> lamont: ehehe
[10:48] <fabbione> ok
[10:49] <fabbione> you didn't build arch: all, did you?
[10:49] <lamont> STFU
[10:49] <lamont> :-)
[10:50] <fabbione> that won't help anyway
[10:51] <fabbione> iirc that part of the build is hairy
[10:51] <lamont> won't?
[10:51] <lamont> grumble
[10:51] <lamont> ok
[10:51] <fabbione> try... it might need to build some arch-dep stuff
[10:51] <lamont> or will in a minute
[10:56] <lamont> fabbione: sbuild -A started now.
[10:56] <fabbione> ok
[10:56] <lamont> linux-source-2.6.12:    02:37:30 (9 entries, sigma 01:29:45)
[10:56] <fabbione> yeah.. no ccache...
[10:56] <lamont> that's with ccache
[10:56] <zul> ok...doing a first pass with squashf
[10:56] <fabbione> oh
[10:56] <lamont> last build was 1:48:29
[10:56] <zul> er..squashfs
[10:57] <lamont> the average has been steadily declining
[10:57] <fabbione> lamont: because we switched compiler
[10:57] <fabbione> from gcc-3.3 to 3.4
[10:57] <lamont> right.
[10:57] <fabbione> so the cache has been invalidated
[10:57] <fabbione> + we added a few tons of lines of code
[10:57] <lamont> otoh, was that in -1.1 as of 0505-1343 DCtime
[10:57] <lamont> ?>
[10:57] <lamont> that was the last time I built -1.1
[10:58] <fabbione> lamont: the gcc-3.4 transition?
[10:58] <fabbione> yes
[10:58] <lamont> and then this time, of course, I built 3/4 of it...
[10:58] <lamont> then the cache should be reasonably valid
[10:58] <fabbione> yes
[10:58] <fabbione> given that doko didn't upload another gcc-3.4
[10:58] <lamont> cache hit                         365530
[10:58] <lamont> cache miss                        465420
[10:58] <fabbione> not that bad
[10:59] <lamont> well, actually, I'm building against hoary right now, so it's pretty stable wrt toolchain... .:-)
[10:59] <fabbione> considering how many times gcc has been updated in the last 3 days
[10:59] <fabbione> oh
[10:59] <lamont> my breezy chroot (hppa) is still a bit in flux.  And I don't have an i386 buildd in that DMZ
[11:01] <lamont> files in cache                    269272
[11:01] <lamont> cache size                           9.1 Gbytes
[11:05] <fabbione> <IP_ADDRESS>:/mirrors/sparccache
[11:05] <fabbione>                        20G  9.0G  9.8G  49% /opt/sparcbuildd/chroots/kernel/home/sparcbuildd/.ccache
[11:06] <zul> heh...i was going to say something stupid but im not now
[11:10] <zul>  CC [M]   fs/squashfs/inode.o
[11:10] <zul>   LD [M]   fs/squashfs/squashfs.o
[11:10] <lamont> cache hit                         366420
[11:10] <lamont> cache miss                        465428
[11:11] <lamont> not bad for a delta
[11:12] <fabbione> lamont: there are only few files that needs rebuild on date/time change
[11:12] <lamont> fabbione: right
[11:13] <lamont> hence this build should scream along to indep in < 2 hours or so.
[11:13] <fabbione> and i am going to sleep soon
[11:13] <fabbione> lamont: if the patch works, mind to upload and merge it where is needed?
[11:14] <lamont> fabbione: will do.
[11:14] <lamont> fwiw, I added *.ignore to the abi directory.. :-)
[11:14] <fabbione> cool
[11:14] <lamont> anyway, back in around 90 min
[11:14] <fabbione> good night
[11:15] <fabbione> zul: did you already open a new branch?
[11:24] <zul> fabbione: yep
[11:25] <zul> infinity: you are doomed now
[11:25] <infinity> Probably.
[11:26] <infinity> You're Canadian?
[11:26] <zul> yep
[11:26] <zul> there is several of us here
[11:26] <infinity> Rogers has the most hideous hostnames.
[11:27] <zul> i know..
[11:45] <zul> there squashfs added


[09:39] <LocutusOfBorg> last day I saw the light
[09:40] <LocutusOfBorg> I saw the hol-light, and that light told me: "please can you kick me out from Ubuntu at least to proposed pocket? I'm holding the ocaml transition, I'm a leaf package, nobody cares about me, and I'm out from Debian testing since a while"
[09:45] <LocutusOfBorg> please AA, ^^
[12:47] <LocutusOfBorg> please also NBS cleanup missing build on armhf: artemis (from 17.0.1+dfsg-1)
[12:47] <LocutusOfBorg> ^^
[17:14] -queuebot:#ubuntu-release- New binary: golang-go.opencensus [amd64] (eoan-proposed/universe) [0.22.0-1] (no packageset)
[17:14] -queuebot:#ubuntu-release- New binary: librsync [amd64] (eoan-proposed/universe) [2.0.2-1] (ubuntu-budgie, ubuntu-mate)
[17:15] -queuebot:#ubuntu-release- New binary: librsync [i386] (eoan-proposed/universe) [2.0.2-1] (ubuntu-budgie, ubuntu-mate)
[17:15] -queuebot:#ubuntu-release- New binary: librsync [ppc64el] (eoan-proposed/universe) [2.0.2-1] (ubuntu-budgie, ubuntu-mate)
[17:16] -queuebot:#ubuntu-release- New binary: librsync [arm64] (eoan-proposed/universe) [2.0.2-1] (ubuntu-budgie, ubuntu-mate)
[17:16] -queuebot:#ubuntu-release- New binary: librsync [armhf] (eoan-proposed/universe) [2.0.2-1] (ubuntu-budgie, ubuntu-mate)
[17:19] -queuebot:#ubuntu-release- New binary: librsync [s390x] (eoan-proposed/universe) [2.0.2-1] (ubuntu-budgie, ubuntu-mate)