[11:35] <elfy> balloons: has someone stopped whatever reports to jenkins for install tests - nothing reported for 7 days
[13:33] <pitti> jibel: FYI, I got 4 wolfes back (although slightly different numbers), setting them up now (they are totally blank)
[14:01] <pitti> jibel: err, halp -- we try to install "jenkins-slave", but that package only exists on precise
[14:01] <jibel> pitti, you can install the version from debian
[14:02] <jibel> pitti, jenkins in unmaintained in Ubuntu and has been removed
[14:02] <pitti> jibel: I wonder how we did that when we first set up these machines; I'm fairly sure it was in ubuntu
[14:02] <pitti> jibel: ooh -- perhaps it was still there in saucy, and dist-upgrade to trusty just kept the old version
[14:02] <jibel> pitti, https://wiki.jenkins-ci.org/display/JENKINS/Installing+Jenkins+on+Ubuntu
[14:03] <jibel> pitti, yes something like that, I don't remember precisely when it has been removed
[14:03] <pitti> https://launchpad.net/ubuntu/+source/jenkins/+changelog
[14:04] <pitti> ack
[14:04] <jibel> pitti, bug 1294005
[14:12] <pitti> jibel: how do I reconfigure http://d-jenkins.ubuntu-ci:8080/computer/wolfe-06-adt/ to be wolfe-02-adt? I don't see any kind of "configure" in the menu there?
[14:14] <pitti> I might just lack the privileges to do that
[14:30] <pitti> jibel: or, I figure I might need an RT for that and let retoaded handle it?
[14:34] <retoaded> pitti, you need me to rename wolfe-06-adt as wolfe-02-adt correct?
[14:35] <pitti> retoaded: yeah, and adjust the IP
[14:36] <pitti> retoaded: i. e. wolfe-02 is now 10.245.66.194 (one less than wolfe-03)
[14:36] <pitti> retoaded: do you need an RT for this?
[14:36] <retoaded> pitti, nah, shouldn't take but a moment once I find where the IP is stored.
[14:38] <retoaded> pitti, the IP isn't used within Jenkins configuration. The node has been renamed and appears to be up.
[14:39] <pitti> retoaded: cool, thanks; ah, it's the node itself telling jenkins about its hostname, I figure?
[14:39] <retoaded> pitti, yes
[14:39] <pitti> cool
[14:41] <pitti> jibel: so, ppc64el boxes are back; I retried the recently failed tests
[14:42] <pitti> jibel: although they feel like a tarpit, I asked smoser about that
[15:42] <balloons> elopio, link? >you mean the AP tests for ubiquity?.
[15:42] <elopio> ->brain freeze<-
[17:32] <wxl> elfy: have you guys come up with a new input engine e.g. scim or uim as a default or what are you doing?
[17:35] <elfy> confused ...
[17:35] <wxl> elfy: you nixed ibus, no?
[17:35] <elfy> oic - we did nothing
[17:36] <wxl> oh, i guess i'm confused :)
[17:37] <elfy> we just don't have ibus by default anymore - if someone wants it they have to install it
[17:38] <wxl> ic, so what is the default?
[17:45] <elfy> no ibus installed
[17:46] <wxl> in other words, you have no input manager at all?
[17:52] <wxl> elfy: to make a long story short, i'd like to kill ibus sometime soon, but i know people need the functionality, so i'm exploring other options and wanted to see if you had any input
[23:04] <ianorlin> grr had a kernel panic while in a live session not really sure how to report the bug on this new desktop I built but haven't installed to yet for utopic
[23:10] <ianorlin> how would I report a bug in the live session of a kernel panic and get debug info?