[02:55] <sbalneav> Evening all
[03:01] <HedgeMage> hi
[13:52] <sbalneav> Morning all!
[13:52] <scottmaccal> good morning.
[14:00] <sbalneav> scottmaccal: Back at work?
[15:24] <LaserJock> stgraber, highvoltage: ping
[15:45] <LaserJock> anybody around in here?
[15:47] <sbalneav> me
[15:47] <sbalneav> just us chickens
[15:48] <sbalneav> When I get back home tonight, I'll test the dvd
[15:48] <LaserJock> alkisg: ping
[15:48] <alkisg> Hi all
[15:48] <LaserJock> hey
[15:48] <LaserJock> so we need a release announcement and release notes
[15:48] <LaserJock> what do you all want mentioned in either/both?
[15:50] <alkisg> That we need people to get involved with edubuntu less it dies? :D
[15:51] <LaserJock> alkisg: anything else? :-)
[15:53] <alkisg> There are many things I'd like to say, but I lack the words to express them...
[15:54] <alkisg> Now that edubuntu is on a dvd instead of a cd, thanks to you, it can become something better but it needs a lot of work too
[15:56] <alkisg> But I can't express myself about what needs to be done...
[15:57] <sbalneav> "Edubuntu has made major improvements in usability.  It has gone back to being a full distro with a DVD installer"
[15:57] <sbalneav> Improvements to LTSP, and management tools also enhance the experience.
[15:59] <alkisg> I think we should also put a big thank you there for LaserJock which will be "retiring"
[15:59] <LaserJock> ok, but what has changed from Jaunty
[15:59] <LaserJock> what potential pitfalls are there?
[16:02] <alkisg> We should also specifically mention that sabayon is now again in a working state
[16:02] <LaserJock> ok, good one
[16:03] <LaserJock> edubuntu-server should be working due to jbicha's moodle fixes
[16:03] <LaserJock> gcompris had a pretty big version jump that includes several fixes
[16:03] <alkisg> italc has had some improvements in autodetecting the clients and avoiding ports in use...
[16:06] <alkisg> ...language support was added on the edubuntu dvd for many languages...
[16:07] <jbicha> Marble has a visual changelog at http://edu.kde.org/marble/current_0.8.php
[16:21] <sbalneav> alkisg: we closed a lot of LTSP bugs, and I'd like to plow through, for next release, a lot of the bugs on some of the other packages.
[16:21] <sbalneav> screem looks like it needs some love :(
[16:23] <alkisg> I'm trying to organize things for all greek schools that want to use standalone ubuntu installations (non-ltsp). So to be honest, I don't expect to have much time this year for bug squashing.
[16:24] <alkisg> I'll be creating 2-3 packages and trying to push them upstream in universe, and I'll be writing wiki pages, though
[16:27] <alkisg> For bugs, I'll try to help as much as I can with ltsp and italc...
[16:29] <LaserJock> alkisg: that that we ask is that you do what you can, when you can, everything helps!
[16:30]  * alkisg gives many, many hours per day to get Ubuntu to fit in Greek schools... :)
[16:31] <LaserJock> yeah, that's awesome stuff
[16:31] <LaserJock> you need to do a brain dump sometime
[16:31] <LaserJock> on what kinds of things you do
[16:34] <alkisg> My "plan" is like this: (1) find what needs to be done for greek schools (sbalneav will hate me for abusing the unix users system)
[16:34] <alkisg> (2) document it (3) script it (4) make a remix out of it (5) when I see that it is out there and working for greece, I'll try to "publish" as much as people want upstream
[16:35] <alkisg> That last part has the most "beurocracy", which I hate... :)
[16:35] <ogra> sbalneav, dont forget ltsp-cluster support
[16:36] <ogra> (should surely be in the release notes)
[16:36] <ogra> LaserJock, all your new splits in the age dependant metapackages should be mentioned
[16:42] <jbicha> for next release, I'd like us to get subject/topic metapackages like debian-edu uses, ubuntu-edu-geography ubuntu-edu-music , etc.
[16:42] <ogra> that might end in endless fragmentation though
[16:43] <LaserJock> yeah, I'm not convinced that we need a lot more meta-packages
[16:43] <stgraber> LaserJock: pong
[16:43] <ogra> ubuntu-edu-geography-preschool, ubuntu-edu-geography-unioversity ...
[16:43] <LaserJock> stgraber: we need release notes and release announcement
[16:43] <jbicha> possibly instead of ubuntu-edu-primary
[16:43]  * alkisg would like for edubuntu to provide an infrastructure for *other* people to do that (=make package collections)
[16:43] <stgraber> highvoltage: highvoltage started to work on something on his gobby server
[16:43] <stgraber> highvoltage: did you have a look ?
[16:43] <stgraber> doh
[16:43] <stgraber> LaserJock: ^
[16:43] <LaserJock> stgraber: I don't know where it is
[16:44] <stgraber> hang on a sec, looking at my jabber log
[16:44] <jbicha> there's not a lot of difference between primary & preschool or between secondary & tertiary, stuff overlaps
[16:44] <LaserJock> currently no
[16:44] <jbicha> it works for debian
[16:44] <ogra> so you would think gcompris is a good tool for universities ?
[16:44] <LaserJock> Debian is quite different from Ubuntu though
[16:44] <ogra> yeah
[16:44] <stgraber> LaserJock: jono.co.za
[16:45] <ogra> or tuxtype
[16:45] <stgraber> the release notes schema is there, just need to fill it
[16:46] <LaserJock> k, good
[16:47] <jbicha> ogra: we could keep a category for young children, but "ubuntu-edu-tertiary" is too broad and not well-defined
[16:48] <LaserJock> that I can generally agree on
[16:48] <ogra> might be
[16:48] <LaserJock> what I think might be a better option
[16:48] <ogra> but turning it into task driven generates a big amount of maintenance overhead
[16:49] <ogra> and also puts up the question where you stop splitting
[16:49] <LaserJock> is to turn -tertiary or something similar into a "basic educational/research workstation" type install
[16:49] <LaserJock> so rather than doing specific topic-area apps
[16:49] <LaserJock> we do things like bibliography tools
[16:49] <LaserJock> writing and productivity tools
[16:49] <ogra> ++
[16:50] <LaserJock> and some good theming
[16:50] <stgraber> what I discussed a few times, is to have the ability to install everything, then have filtering using xdg to only show a few entries with the list of entries to be configurable (as it depends on the grade, the country and in some cases, the region)
[16:50] <ogra> (not that i would have to decide anything) :)
[16:50]  * ogra points to edubuntu-menus
[16:50] <jbicha> some categorization is useful for findability, if I wanted to find recommended music software for education in Ubuntu, where would I go?
[16:50] <LaserJock> right
[16:50] <LaserJock> well
[16:50] <ogra> it has so much potential
[16:50] <LaserJock> I think there's sort of two area
[16:50] <ogra> and stioll nobody finished it
[16:51] <LaserJock> ogra: now that I'm retired you never know ;-)
[16:51] <ogra> jbicha, software-center
[16:51] <ogra> LaserJock, hah
[16:51] <ogra> LaserJock, you mean like edubuntu grew a community after is stepped back ?
[16:51] <LaserJock> I think we can categorize without metapackages
[16:51] <ogra> yeah
[16:52] <ogra> just add the right patches to software-center
[16:52] <LaserJock> I think it should be considered that we have a custom software-center view
[16:52] <ogra> ++
[16:52] <jbicha> ogra: there's 104 choices for music, I don't know if any of them are useful
[16:52] <jbicha> LaserJock: ooh, we can do that?
[16:52] <ogra> software-center is at some point supposed to replace all GUI package management tools
[16:52] <LaserJock> jbicha: sure, why not?
[16:52] <LaserJock> I was thinking this weekend
[16:52] <ogra> jbicha, software-.center only had its first release, its still open to improvements
[16:53] <ogra> lucid is the perfect time to spec such additions
[16:53] <LaserJock> that we need a core Edubuntu
[16:53] <jbicha> yeah, I just wasn't creative enough to think of that
[16:53] <LaserJock> that's about theming, productivity, and a general educational feel
[16:53] <LaserJock> *without* specific educational content areas
[16:53] <LaserJock> and without much age specificity
[16:54] <ogra> yeah
[16:54] <LaserJock> and then add on those layers
[16:54] <LaserJock> what we're doing now is the opposite
[16:54] <LaserJock> making the general (edubuntu-desktop) depend on the specific
[16:54] <LaserJock> I think we should reverse that and make the specific depend on the general
[16:54] <LaserJock> and make the specific more accessible to the end user
[16:55] <LaserJock> I think that could be done via Ubiquity and Software Center
[16:56] <LaserJock> essentially
[16:57] <LaserJock> I'm thinking Edubuntu should be "plugin" based
[16:57] <LaserJock> we provide a core and the means to plug in extras edu goodness
[16:57] <LaserJock> s/extras/extra/
[16:59] <ogra> LaserJock, and you dare to resign with such an idea in mind ? tsk
[16:59] <LaserJock> I got the ideas
[16:59] <LaserJock> just not the time :(
[17:00] <jbicha> have we considered the KDE desktop for Edubuntu? I mean there's kde-edu but not a similar project for GNOME
[17:01] <LaserJock> jbicha: edubuntu-desktop-kde
[17:02] <LaserJock> if we consider this plugin-based design I think it would be entirely conceivable to make it work very well on Kubuntu
[17:02] <LaserJock> I think you still need to pick one in terms of the DVD
[17:02] <jbicha> but GNOME's the default, is GNOME more usable (or better supported by Ubuntu) in schools?
[17:02] <alkisg> How hard is it for an admin to provide a list of packages? Do we really have to give such a big focus to package selection? Wouldn't it be better if we focused in some "out of the box" solutions? (like e.g. prepared ldap/nfs configurations...)
[17:02] <LaserJock> alkisg: I agree
[17:03]  * alkisg is right onto that this year... :)
[17:04] <LaserJock> but some "out of the box" solutions will be app-dependent
[17:05] <LaserJock> consider the "parent with small kids" solution
[17:06] <alkisg> Well, we could provide him a dansguardian-based solution or something...
[17:06] <LaserJock> preciously
[17:06] <LaserJock> I think looking at out of the box "solutions" as plugins to a core Edubuntu sounds interesting
[17:07] <LaserJock> so what's needed are:
[17:07] <LaserJock> 1) the core
[17:07]  * alkisg thinks more people will be interested in this than in meta-packages
[17:07] <LaserJock> 2) a few "solutions" that Edubuntu does *very* well
[17:07] <LaserJock> 3) putting it all on an installation media
[17:09] <LaserJock> it would be good *hint* to spec this out and see if it could work for Lucid
[17:12] <jbicha> so these "solutions" would be separate from the normal deb dependency system....because otherwise it's just metapackages with a different name (& possibly philosophy)
[17:15] <LaserJock> they might be implemented via metapackages
[17:15] <LaserJock> it doesn't matter a whole lot
[17:16] <LaserJock> it's more the design of it than the actual implementation method
[17:18] <jbicha> by the way, does anyone have a list of stuff that needs to be packaged, the software I could find (like BlueJ) has been too complicated
[17:19] <LaserJock> unless something is brand new, if we dont' have a package yet in Debian/Ubuntu it's probably for a reason :-0
[17:19] <LaserJock> :-) rather
[17:20] <alkisg> LaserJock (since I think is in your field) have you looked at http://phet.colorado.edu/index.php for packaging?
[17:21] <jbicha> yeah, but...you say you need help with packaging
[17:22] <LaserJock> jbicha: ah, well by packaging I usually mean package maintenance
[17:22] <LaserJock> jbicha: things like that moodle fixing you did
[17:22] <LaserJock> alkisg: I don't think those are open source
[17:23] <jbicha> LaserJock: oh ok, that's probably better than starting from scratch anyway
[17:23] <jbicha> http://phet.colorado.edu/about/licensing.php
[17:23] <LaserJock> ok, yeah, great
[17:24] <LaserJock> so yeah, I guess they'd be a candidate
[17:24] <alkisg> scratch could also be a candidate...
[17:24] <LaserJock> it used to be we didn't have a Free java VM, which ruled out us shipping and java apps
[17:24] <alkisg> http://scratch.mit.edu/
[17:24]  * LaserJock runs
[17:24] <alkisg> Heh :)
[17:24] <LaserJock> I don't want to touch anything related to Squeak :-)
[17:25] <LaserJock> but yeah, somebody should look at scratch
[17:27] <alkisg> Also I've heard many teachers here using http://belvedere.sourceforge.net/ ...
[17:28] <LaserJock> interesting
[17:29] <alkisg> Finally, klatin was used but is no longer maintained upstream :(
[17:30] <LaserJock> yeah, that died during KDE3 -> KDE4
[17:37] <jbicha> oh, neat, there's already a PPA for scratch https://launchpad.net/~scratch/+archive/ppa
[18:00] <mhall119|work> what about squeak?
[18:01] <mhall119|work> scratch is a cool game
[18:01] <mhall119|work> kind of like etoys, only with pre-made art and nicer puzzle-shaped blocks
[18:05] <LaserJock> mhall119|work: squeak and I have a long and not-very-pleasant past :-)
[18:07] <mhall119|work> heh, I can understand
[18:10] <sbalneav> ok, time for me and jammcq to head to the airport
[18:11] <sbalneav> be on tonight
[18:13] <LaserJock> sbalneav: k
[18:41] <LaserJock> hmm
[18:41] <LaserJock> I wonder if we should combine the release notes and release announcement
[18:42] <highvoltage> LaserJock: pong
[18:42] <highvoltage> hi LaserJock
[18:43] <highvoltage> LaserJock: my initial understanding was that it would be pretty much the same
[18:43] <highvoltage> LaserJock: sorry that I didn't finish it (or even start it properly), I just haven't been able to concentrate enough to just get it done
[18:44] <LaserJock> highvoltage: well, the Ubuntu release notes are mostly (here are known problems)
[18:45] <LaserJock> highvoltage: whereas the release announcement is all the "this is who we are and how you get it"
[18:45] <LaserJock> I don't know how many "known problems" we're going to have that aren't already covered in Ubuntu's notes
[18:46] <LaserJock> perhaps we should have Release Notes be the full version with all the info
[18:46] <LaserJock> and the announcement just be a brief couple paragraphs
[18:48] <highvoltage> LaserJock: that sounds like a very good
[18:48] <highvoltage> LaserJock: awesome opening paragraph you put there
[18:49] <LaserJock> highvoltage: thanks
[18:49] <LaserJock> highvoltage: do you have a little time now?
[18:50] <highvoltage> LaserJock: yep
[18:50] <LaserJock> stgraber: available'ish?
[18:51] <LaserJock> highvoltage: it looks like what Ubuntu does is write the release notes on the wiki and keep a copy there, but the official location (where user and links go to) is on the website
[18:51] <stgraber> LaserJock: doing some iso testing, so yeah
[18:51] <LaserJock> highvoltage: I think it would make sense to do similar so we can update the release notes (I'm guessing there'll have more "known issues" after release)
[18:51] <LaserJock> my general thought is that the Release Notes should be a bit more prominent
[18:52] <highvoltage> LaserJock: ok
[18:52] <LaserJock> in the sense that as time goes by after release and big issues come up
[18:52] <LaserJock> we should document them in the Known Issues
[18:52] <LaserJock> and *then* point people their
[18:52] <LaserJock> *there
[18:52] <LaserJock> so like last release we had this stupid bug in Gcompris that I couldn't fix via an SRU
[18:53] <LaserJock> that should have gone into the release notes, even though I found out about it post-release
[18:53] <LaserJock> and when people had problems I could at least point to the release notes
[18:53] <LaserJock> it could be sort of a "go there first, then ask questions" type thing
[18:54] <LaserJock> thoughts?
[18:54] <highvoltage> LaserJock: I have to leave for a few mintes, I'll be back in about 10 minutes (sorry just have to help someone quickly)
[18:54] <LaserJock> np
[18:55] <stgraber> LaserJock: sounds good
[18:56] <stgraber> not sure we have anything broken at the moment (other than what's common with Ubuntu)
[18:56] <LaserJock> right
[18:56] <stgraber> so we should redirect readers to Ubuntu's as well
[18:56] <stgraber> what's the state of Moodle ? I remember reading about some issues there, has that been fixed ?
[18:56] <LaserJock> we are
[18:56] <LaserJock> I *think* it's fixed :-)
[18:57] <LaserJock> that was going to be something that was going in Known Issues, but I think jbica has fixed that
[18:57] <LaserJock> for know we can basically leave an empty section with "Important issues and workarounds will be noted here"
[18:58] <stgraber> "At the time of the release, we haven't been made aware of any issues outside of these listed in the Ubuntu release notes. Additional information may be added here at a later time" ?
[18:59] <LaserJock> yeah, perfect
[19:30] <highvoltage> hmmm
[19:31] <LaserJock> uh oh
[19:31] <LaserJock> what'd I do now
[19:31] <highvoltage> not you, LP :)
[19:32] <LaserJock> highvoltage, stgraber: can you guys read over what I have so far?
[19:32] <highvoltage> LP's UI and I have never gotten along quite well
[19:32] <highvoltage> LaserJock: I went through it and I think it's good
[19:33] <LaserJock> hmm, there was something I was remembering that should go into known issues but I've forgotten
[19:33] <highvoltage> LaserJock: what's the URL for the edubuntu bugs again? I'm failing to find it atm
[19:33] <LaserJock> highvoltage: I just added some to What's New
[19:33] <LaserJock> highvoltage: bugs.launchpad.net/~edubuntu-bugsquad/+packagereport ?
[19:33] <LaserJock> that's from memory so YMMV
[19:35] <highvoltage> LaserJock: on the ltsp-cluster line, it has been available before, but what's new this time is that it's now available in the ubuntu archives
[19:35] <LaserJock> well
[19:35] <highvoltage> LaserJock: I've modified the description but I'm not sure whether it's nice.
[19:36] <LaserJock> it doesn't exist until it's in the archives :-)
[19:36] <highvoltage> LaserJock: our previous release notes disagrees!
[19:36] <LaserJock> fine, be that way ;-p
[19:37] <LaserJock> highvoltage: how's that?
[19:37] <highvoltage> LaserJock: good, although reading the 9.04 announcements again I think it's fine like it was
[19:37] <highvoltage> LaserJock: it (https://wiki.ubuntu.com/Edubuntu/WikiSite/Release/9.04/ReleaseNotes) just mentioned that the thin client supported ltsp-cluster, not that it was available for installation
[19:37] <highvoltage> LaserJock: so your original point there was probably fine
[19:38] <LaserJock> well
[19:38] <LaserJock> tbh I'm kinda of not considering the 9.04 release notes much
[19:38] <LaserJock> that was the old Edubuntu!
[19:38] <highvoltage> :)
[19:38] <highvoltage> LaserJock: *hug*
[19:54] <LaserJock> highvoltage, stgraber: time to put this on the wiki?
[19:55] <highvoltage> LaserJock: +1
[19:55] <highvoltage> LaserJock: I can't think of anything important that isn't covered yet
[19:55] <LaserJock> what URL do we want?
[19:55] <LaserJock>  /Edubuntu/Release/9.10/ReleaseNotes?
[19:56] <highvoltage> LaserJock: http://wiki.edubuntu.org/edubuntu/edubuntuwikisite/wikisite/officialnotes/releasenotes/karmic/9.04/KarmicReleaseNotes
[19:56]  * highvoltage ducks
[19:56] <LaserJock> or should it be /Releases/ (i kind of have a problem with putting multple things into a singular category but maybe that's just me)
[19:57] <highvoltage> LaserJock: as in /Edubuntu/Releases/9.10 ?
[19:57] <LaserJock> yeah
[19:57] <highvoltage> I think that's good
[19:57] <LaserJock> just because we're putting multiple releases in there
[19:58] <highvoltage> *nod*
[20:03] <stgraber> LaserJock: +1
[20:10] <LaserJock> stgraber, highvoltage (and anybody else): https://wiki.ubuntu.com/Edubuntu/Releases/9.10/ReleaseNotes
[20:10] <LaserJock> I tweaked the known issues section
[20:12] <highvoltage> LaserJock: thanks, that's a relief
[20:14] <LaserJock> highvoltage, stgraber: now working on announcement
[20:14] <LaserJock> I've copied over the top bits from the release notes
[20:15] <LaserJock> I think if we condense that a bit and add in a "Where to get it" I think it should be good
[20:15] <highvoltage> LaserJock: so the Release Announcements will be a few paragraphs?
[20:15] <LaserJock> yeah, I think it should be pretty brief
[20:16] <LaserJock> I guess the most important things are "hey, we're new!" and "here's how you get it"
[20:16] <LaserJock> thoughts?
[20:16] <highvoltage> LaserJock: yeah
[20:21] <LaserJock> gah
[20:21] <highvoltage> and a live gah?
[20:21] <LaserJock> what the heck do you call a LiveCD session?
[20:22] <LaserJock> I want words normal people can understand
[20:22] <highvoltage> I've never known it by any other name than a "Live CD session"
[20:23] <highvoltage> I guess you could spell it out like "try it out by running it directly from the DVD without installing" or something similar
[20:24] <LaserJock> how does that sound?
[20:25] <highvoltage> yeah
[20:25] <highvoltage> feels like it's missing something
[20:25] <highvoltage> I'm in a weird perfectionistic mode where nothing just feels right. sorry :/
[20:26] <highvoltage> I've made a slight change but if it doesn't sound right feel free to remove
[20:26] <LaserJock> well it's only a problem if you dont' fix it ;-)
[20:26] <LaserJock> ah, much better, IMO
[20:27] <LaserJock> highvoltage: how about just plain "modifying your computer"?
[20:27] <highvoltage> k
[20:28] <highvoltage> (I was thinking of that too)
[20:28] <LaserJock> good
[20:28] <LaserJock> highvoltage: s/try/run/ ?
[20:29] <highvoltage> k
[20:29] <LaserJock> let's move on to installation before we pick it to death :-)
[20:29] <highvoltage> heh, indeed
[20:29] <highvoltage> I'm bummed that I don't have an edubuntu iso and not enough bandwidth do sync up :/
[20:30] <highvoltage> it would be nice to have an installation guide with screenshots again
[20:30] <LaserJock> highvoltage: since we already described what you can do with the DVD above I suggest we maybe just tell how to get the .iso and link to how to burn it
[20:30] <highvoltage> I guess I could still do that after the 1st
[20:30] <LaserJock> sure
[20:37] <highvoltage> (brb)
[20:42] <vmlintu> Hi! Anyone else getting nbd+squashfs errors when rebooting ltsp thin clients on karmic? https://bugs.launchpad.net/ubuntu/+bug/457702
[20:44] <highvoltage> LaserJock: I don't have isos but I have the karmic repositories at least
[20:44] <highvoltage> LaserJock: if you don't find a kde user I could install kde on my netbook if there's enough space
[20:45] <LaserJock> it's just a quick thing
[20:47] <LaserJock> highvoltage: https://wiki.ubuntu.com/Edubuntu/Releases/9.10/ReleaseAnnouncement
[20:48] <LaserJock> I want to add a thing on how to install the app bundles from Kubuntu
[20:51] <highvoltage> LaserJock: ok installing kpackagekit... I just confirmed with #kubuntu that that's what they actually use
[21:03] <LaserJock> good grief
[21:03] <LaserJock> like all the servers are crawling today
[21:04] <highvoltage> I guess everyone is keeping their debmirrors as up to date as possible in anticipation
[21:05] <LaserJock> I need to get how to get to kpackagekit :(
[21:11] <LaserJock> ok, done
[21:12] <LaserJock> highvoltage: can you do the wiki - > edubuntu.org on release day?
[21:16] <LaserJock> highvoltage, stgraber: OK, I'm done.
[21:16] <LaserJock> https://wiki.ubuntu.com/Edubuntu/Releases/9.10/ReleaseAnnouncement
[21:16] <LaserJock> https://wiki.ubuntu.com/Edubuntu/Releases/9.10/ReleaseNotes
[21:17] <LaserJock> ^^ those need to be put on edubuntu.org for release day
[21:17] <LaserJock> make sure to note that there are 2 FIXME markers in the announcement
[21:17] <LaserJock> I don't know what the exact URL for the .iso is going to be
[21:18] <LaserJock> There is a hopefully final .iso up at http://cdimages.ubuntu.com/edubuntu/dvd/20091027.1/
[21:18] <LaserJock> please test those if you can
[21:19] <LaserJock> and with that I'm out
[21:19] <LaserJock> not sure when I'll be on next
[21:19] <LaserJock> so have a great release everybody and thanks!
[22:57] <dtrask> Hey all....I need help....this is somewhat related to edubuntu as it is for Open1to1.org and the image that I create for school netbooks....
[22:57] <dtrask> I have had schools complaining that students are creating "ad hoc" networks via network-manager and thus wreaking havoc on the school wireless network
[22:58] <dtrask> does anyone know of a way (clean or hack...I'm desperate here) of disabling the ability to create...and/or connect to an ad-hoc wireless network?


[00:26] <balloons> cihelp, jenkins isn't building music-app
[00:26] <balloons> https://code.launchpad.net/~vthompson/music-app/fixes-1259962/+merge/198601
[05:05] <plars> cwayne: sorry, didn't get a good chance to reconfigure the jobs before, but I merged the change already. I just pushed and merged it all now, and re-started the custom jobs here: http://q-jenkins:8080/view/Touch/view/Ubuntu%20Touch%20Master%20Jobs/job/trusty-touch_custom-mako-smoke-master/
[05:05] <plars> cwayne: we should check on them tomorrow morning, but they will all run now anytime there's a new custom image
[07:57] <sil2100> Morning
[09:13] <sil2100> Mirv: hello! Did you notice any infra failures today maybe?
[09:14] <Mirv> sil2100: intel failing right now there running apps stack ap:s
[09:14] <Mirv> nothing else
[09:15] <Mirv> I got one good result before that
[09:33] <lool> ev: joining hangout?
[09:43] <sil2100> psivaa: hello!
[09:43] <lool> psivaa: heya
[09:44] <lool> psivaa: could you retry terminal and unity8 on maguro after recording hte URLs of failing tests?
[09:44] <psivaa> lool: will do
[09:44] <lool> psivaa: also would need webbrowser on mako
[09:44] <psivaa> lool: will do
[09:45] <lool> psivaa: cool, could you ping us when done?
[09:45] <lool> psivaa: would like to kick an image build once it's done
[09:45] <psivaa> lool: sure
[09:45] <asac> psivaa: seems we duplicate here :)
[09:45] <asac> err in -touch
[09:46] <psivaa> :)
[09:46] <asac> so yeah. let us know when done so we can swiftly kick
[09:50] <ev> lool: sorry, couldn't make it. Running a sprint on juju and ci in bluefin today
[09:52] <lool> ok
[09:53] <Mirv> sil2100: building it now first. I think we had the rule for this week that cu2d desktop tests need to pass as well before releasing anything, so let's see them first and I'll continue on my Qt stuff
[09:56] <sil2100> Mirv: thanks!
[10:03] <sil2100> Mirv: regarding testing the bug, from the merge request I see that it's indeed just switching between 12h and 24h locale, looking at some PM time and checking if the indicator changes
[10:19] <psivaa> lool: asac: the three tests  have been run and passed. sending you the earlier failed links in a mail
[10:20] <sil2100> psivaa: \o/
[10:21] <lool> awesome
[10:21] <lool> sil2100: good to start a build?
[10:22] <sil2100> lool: fire it up!
[10:22] <lool> 99.5%
[10:22] <lool> that's pretty good
[10:23] <lool> building
[10:23] <lool> sil2100: Do we want to promote image 70?
[10:24] <lool> sil2100: maybe check with popey and others
[10:24] <lool> sil2100: just let me know here if you want it promoted
[10:24] <popey> I can check on mako, but you need someone (omer) with maguro to test too
[10:25] <sil2100> hmm
[10:25] <asac> lool: how can we get those final tests fixed?
[10:25] <asac> om26er: ^^
[10:25] <asac> om26er: we have like 3 AP tests... can you just crush them? :)
[10:26] <sil2100> popey: if you have a free moment then check, if you can - I would personally prefer promoting an image with the datetime fix, but any promotion doesn't hurt ;)
[10:26] <asac> om26er: http://ci.ubuntu.com/smokeng/trusty/touch/mako/70:20131217:20131211.2/5503/ubuntu-weather-app-autopilot/
[10:26] <asac> om26er: if you can fix those i will give you whatever you want :)
[10:26] <asac> 2!!!
[10:34] <om26er> asac, sure. get me a pay raise ;)
[10:35] <asac> om26er: how much? :)
[10:35] <timp> what is needed for a new ubuntu-ui-toolkit release? It has been in the landing asks page for a while now
[10:36] <om26er> asac, i'll settle for 10% but before april.
[10:36] <om26er> working on the failures now
[10:37] <asac> om26er: seems its just a DB not being created
[10:37] <asac> not sure whats going on with the .ini files
[10:37] <asac> and who should create those
[10:38] <asac> in create_blank_db
[10:38] <asac> something is missing
[10:38] <asac> :)
[10:38] <asac> feels all it wants is to figure what location to use for the sqlite file
[10:38] <asac> not sure why the algo is so weird and goes through .ini files in Databases directory
[10:50] <popey> sil2100: 70 looks good to me on mako
[10:51] <sil2100> popey: thanks!
[10:52] <sil2100> om26er: could you give image 70 a spin on maguro as well, just like popey ?
[10:52] <om26er> sil2100, Ok, updating. maguro is too slow to be fun :)
[10:52] <sil2100> ;D
[10:56] <om26er> sil2100, how to run autopilot tests for click packages ?
[10:56] <popey> om26er: http://paste.ubuntu.com/6588007/  i use that script
[10:57] <popey> ./testing.sh lp:ubuntu-rssreader-app ubuntu_rssreader_app
[10:57] <popey> like that
[10:58] <om26er> popey, thanks
[10:58] <sil2100> om26er: https://wiki.ubuntu.com/Touch/Testing <- this guide works for me as well
[10:58] <sil2100> So just phablet-config autopilot --dbus-probe enable
[10:58] <sil2100> And then: phablet-click-test-setup --click com.ubuntu.calculator; phablet-test-run ubuntu_calculator_app
[10:58] <sil2100> etc.
[10:59] <sil2100> Damn, my neighbour again started drilling
[10:59] <sil2100> Doesn't help with concentrating
[11:07] <popey> bug 1192711 is a little irritating
[11:07] <popey> not a regression, seems to have been there a while, but I'd not noticed
[11:21] <Mirv> sil2100: https://code.launchpad.net/~timo-jyrinki/cupstream2distro-config/indicators_missing_deps/+merge/199265
[11:22] <sil2100> Mirv: do you know if both libupstart-app-launch1 and libupstart-app-launch2 are required to be installed right now?
[11:24] <asac> om26er: any clue yet?
[11:24] <asac> om26er: sergiusens knows how to run AP test for click
[11:24] <asac> oh already answerd :)
[11:27] <Laney> Can someone help me figure out why most of the autopilot tests for ubuntu-system-settings are borked (the ones which try to select anything, it seems), please?
[11:27] <om26er> asac, so the issue is the test suite expects a certain directory to be there but its not able to find it because that directory is only created once the weather app is started
[11:28] <asac> om26er: i got so far... but it also expects .ini files in that directory :)
[11:29] <asac> so i dont know where that .ini is supposed to come from
[11:29] <asac> i think this is super bogus code to be honest :)
[11:29] <om26er> asac, works fine for me after I started the weather app manually
[11:29] <asac> om26er: where is that directory created?
[11:29] <Laney> borked on the device only, that is --- they work on the desktop...
[11:29] <asac> om26er: i didnt see anythign in code creating that directory ... nor the .ini file
[11:29] <Mirv> sil2100: in the previous cases it seemed to be, at least earlier, that if the older one was removed it did not work
[11:29] <om26er> asac, ~/.local/share/com.ubuntu.weather/
[11:30] <asac> om26er: where in code i mean :)
[11:30] <asac> oh wait
[11:30] <asac> yeah .../Databases
[11:30] <asac> i still dont see anywhjere in code that this dir is created
[11:30] <asac> also the code checks for .ini files
[11:30] <om26er> asac, exactly that directory is not created by the test suite, rather it is automatically created when the app is started
[11:30] <asac> anyway. seems you already have it running, so debugging shoudl be simple
[11:31] <asac> om26er: which code is doing that?
[11:31] <asac> om26er: is that something our sdk does? does it also create the .ini files?
[11:31] <om26er> asac, the app is using QtLocalStorage for that
[11:31] <sergiusens> asac, the dir is created when using LocalStorage
[11:31] <asac> ok seems the test doesnt use it
[11:31] <asac> kk
[11:32] <asac> so the tests should be using that :)
[11:32] <Mirv> sil2100: anyhow, the cu2d tests are not green so if I should test on device or not
[11:32] <asac> instead of raw mkdirs etc.
[11:32] <asac> err raw os. stuff
[11:32] <asac> interesting that i get no direct hit when googling for QtLocalStorage
[11:32] <asac> is that no public API?
[11:33] <om26er> sergiusens, I am thinking to check if that directory exists and if it does not just start the app and close it in the suite. sounds hacky ?
[11:33] <Mirv> sil2100: I understand that we won't release unity stack until it's green, but what about indicators? do you think I can go ahead and test on device with those results currently in cu2d and publish if device ok?
[11:33] <asac> sounds hacky :)
[11:33] <asac> but makdirs that directory would make sense
[11:33] <asac> :)
[11:33] <sergiusens> om26er, that was there before and actually removed from the test suite to make it more stable
[11:33] <asac> hehe... just dont know about the .ini and if that info in ther ematters
[11:33] <sergiusens> om26er, I don' t get it; I tested by deleting the dir completely when first accepting
[11:34] <asac> so why cant the test use qt local storage as well?
[11:34] <asac> or call an app func to do the setup
[11:34] <asac> hmm. guess its not nicely available in python :)
[11:34] <sergiusens> asac, QtQuick.LocalStorage
[11:35] <asac> right. so if we would have qmltests rather than AP things would be easier?
[11:35] <asac> anyway. i feel fro the test all that matters is that we give it SOME db filepath
[11:35] <asac> that is  valid
[11:35] <om26er> but qmltests are not integration tests
[11:36] <asac> so whatever we give too it its good and if its even in the right .local/ directory owned by the app its even better
[11:36] <sergiusens> asac, the app is supposed to create everything it needs on it's own, and it does
[11:37] <asac> sergiusens: right, so its a race?
[11:37] <asac> sergiusens: where does the test start the app?
[11:37] <sergiusens> om26er, asac, the test code just needs to contemplate the inexistence of a prior database, unless it mangles with it before launch
[11:37] <asac> sergiusens: so we might want to change the find_db into a poll that waits for 60 seconds?
[11:37] <asac> and only then gives up?
[11:37] <asac> :)
[11:37] <sergiusens> asac, that may be the case; not sure if it waits for everything
[11:38] <sergiusens> asac, yeah, that's what's been happening with the tests
[11:38] <sil2100> Mirv: let's test it on the device, since I guess not-green tests on indicators right now basically might be related to some desktop issues
[11:38] <sil2100> Mirv: let's make this one exception
[11:42] <sergiusens> btw ci, need a release for autopilot to get some emulator love http://www.youtube.com/watch?v=n2pVpjBFiaI
[11:42] <sergiusens> cihelp that is
[11:43] <asac> nice one
[11:43] <asac> sergiusens: lets get one 100% image
[11:43] <asac> then we land autopilot... hwoever, i wouldprefer if we could pick just what you need
[11:43] <asac> and leave the rest out
[11:43] <sil2100> There's a lot of autopilot changes pending still
[11:43] <asac> check much stuff people have accumulated http://people.canonical.com/~platform/cu2d/results
[11:43] <asac> i would prefer if we only land exactly what we understand out of those
[11:43] <sil2100> I guess we could release this, but I would like to get all the other pending bits out separately first
[11:44] <asac> at best all, but only after looking at each change
[11:44] <asac> :)
[11:44] <asac> sil2100: lets get 100% green before pulling in AP
[11:44] <asac> AP folks should be testing the hell out of their AP
[11:44] <asac> so once we take it its clean
[11:45] <sergiusens> asac, sil2100 would a package patch do? It's a one line add to a map, that's about it for now
[11:45] <timp> robru: ping
[11:45] <sergiusens> I can prepare a debdiff
[11:45] <asac> sergiusens: not before we have 100% :)
[11:45] <asac> get us the fix for this test :)
[11:46] <asac> then we cna land whatever you want
[11:46] <asac> hehe
[11:46] <sergiusens> asac, ack, I can wait
[11:46] <asac> sergiusens: help fixing the test
[11:46] <asac> its just this DB thing
[11:46] <asac> at best next image would have the fix
[11:46] <sil2100> sergiusens: that one-liner, would it help in getting us green, or is it related to something else?
[11:46] <asac> sergiusens: check with om26er if he needs help etc.
[11:46] <sergiusens> sil2100, not related
[11:46] <sergiusens> om26er, do you need help?
[11:47] <sergiusens> om26er, I can review whaever you've done so far
[11:47] <sil2100> sergiusens: then let's wait and release it with all the AP changes then - we need to release those ASAP anyway ;)
[11:47] <asac> sil2100: please send a mail to thomi,sergiusenss etc. that they should start running APs all day long against their AP package from daily-build
[11:47] <asac> and give us a list of APs that are green
[11:47] <asac> after that ... at best with logs :)
[11:49] <Mirv> sil2100: alright
[11:52] <om26er> sergiusens, I only figured what was the problem. now working on workarounds/solutions
[11:52] <om26er> sergiusens, will get help from you if i run out of ideas
[11:54] <sergiusens> ack
[11:54] <timp> Mirv, sil2100 do you know what is blocking the UITK release? the flaky test from https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0Au6idq7TkpUUdGNWb0tTVmJLVzFZd0doV3dVOGpWemc&usp=drive_web#gid=0 was fixed a while ago
[11:55] <timp> it was this one https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1259476
[11:55] <sil2100> timp: hi!
[11:55] <timp> sil2100: hello :)
[11:55] <sil2100> timp: from what I see we required an ACK from you guys and a re-addition to the Landing Asks once the flacky test is gone :)
[11:56] <sil2100> timp: so, if you can, please add it and we'll do everything we can to release it ASAP
[11:56] <timp> sil2100: I don't have edit rights for that doc
[11:56] <timp> sil2100: can I get rights or should I ask zoltan to add it tot he list?
[11:56] <timp> *to the list
[11:57] <popey> om26er: did I see sil2100 bribe you to look at the weather test failures? Are you looking at those?
[11:58] <om26er> popey, yes, I am working on it
[11:58] <Mirv> timp: it's usually the manager that adds it
[11:58] <popey> om26er: great. let me know if you need any testing of it done
[11:58] <timp> Mirv: okay.
[11:58] <sil2100> timp: if you can, please ask Zoltan :) Thanks!
[12:00] <timp> okay, asking. thanks
[12:00] <timp> robru: unping :)
[12:03] <timp> sil2100: it is there nwo :)
[12:03] <timp> *now
[12:03] <timp> I seem to have a typing problem today
[12:15] <om26er> sergiusens, summary is: the test code adds certain fixed locations to the database (hamburg and London in this case) before starting the app so that the tests have some data in the app to interact with. for injecting these pre-defined db entries it needs to have an already created database.
[12:15] <om26er> sergiusens, the notes-app does exactly the same thing. it check if the db directory is there and if its not it starts and quits the app
[12:18] <sergiusens> om26er, ok, there's old code in there that calls a launch_and_close_app
[12:40] <timp> sil2100: can you please keep me informed about the uitk release? If there are any issues please let me know so we can fix them :) thanks
[12:40] <sil2100> timp: sure, thanks! :) We'll add it to our todays release list
[12:40] <timp> great
[12:41] <sil2100> Mirv: how's the progress on indicator-datetime ?
[12:41] <sil2100> popey: hmm, you said you have some bluetooth audio device for Ubuntu Touch testing?
[12:41] <Mirv> sil2100: it's starting to be done, I'm wondering though who to bug with packaging changes
[12:42] <asac> lool: did we ever build an image :)?
[12:43] <asac> ah seems we have 71
[12:43] <asac> nice
[12:43] <asac> psivaa: something was going wrong on mako it seems
[12:43] <asac> guess you are on it?
[12:44] <sil2100> Mirv: that's a valid question! Maybe try poking Laney or lool I guess?
[12:44] <sil2100> Later we can always pester Ken or Mathieu
[12:45] <asac> ack. pick any friendly core-dev :)
[12:46] <Laney> There's loads in #ubuntu-devel, but sure
[12:46] <Mirv> Laney: http://pastebin.ubuntu.com/6588664/ (to fix http://pad.lv/1256061)
[12:46] <Laney> maybe you could look up my question from earlier that went unanswered to thank me back :-)
[12:47] <Laney> oh it's this
[12:47] <Mirv> the merge request does not explain the details (small fixes) https://code.launchpad.net/~charlesk/indicator-datetime/lp-1256061/+merge/198968 but seem sok
[12:47] <Laney> I told him it's better to use locale-gen directly
[12:47] <Laney> but fine
[12:47] <popey> sil2100:  no
[12:48] <popey> sil2100: oh, actually, my daughter has a speaker, let me see if that works
[12:48] <sil2100> popey: since someone mentioned on the ML that bluetooth devices still don't work with the latest image
[12:48] <Mirv> Laney: thanks. ooh, autopilot test failures.. did you see the logs already?
[12:48] <Laney> which logs?
[12:49] <Mirv> Laney: settings failures, there are some tests failing in the CI
[12:49] <Laney> show me?
[12:49] <Laney> it's probably the same thing
[12:49] <Mirv> http://q-jenkins.ubuntu-ci:8080/job/autopilot-trusty-daily_release/957/label=autopilot-nvidia/ + http://q-jenkins.ubuntu-ci:8080/job/autopilot-trusty-daily_release/957/label=qa-intel-4000/
[12:49] <Mirv> for some reason on intel test_about.StorageTestCase.test_installed_apps and on nvidia test_about.LicenseTestCase.test_licenses_page
[12:50] <Laney> /var/local/autopilot/autopilot.log: AssertionError: The following apps were started during the test and not closed: [<Application 'Report a problem...'>]
[12:50] <Laney> is it that?
[12:50] <popey> sil2100: it doesn't detect my bluetooth speaker
[12:50] <popey> but I don't know if it ever did, because I have never tested this
[12:50] <sil2100> CraB
[12:50] <Mirv> Laney: looks like that. a) it seems like apport, b) it's different from your "most tests failing"
[12:51] <Laney> it is
[12:51] <Mirv> yep, http://q-jenkins.ubuntu-ci:8080/job/autopilot-trusty-daily_release/957/label=autopilot-nvidia/artifact/results/autopilot/videos/ubuntu_system_settings.tests.test_about.LicenseTestCase.test_licenses_page.ogv
[12:51] <Laney> system-image-dbus crash
[12:52] <sil2100> psivaa: hello! Do you have a Ubuntu Touch compatible bluetooth device by any chance?
[12:52] <Laney> seems like it's not our fault
[12:52] <Laney> also that runs on desktop ...
[12:52] <Laney> the problem I had was only on the phone
[12:53] <Mirv> Laney: bypassing those, are the selection problems using selection via UI Toolkit somehow? just wondering if SDK people could help debugging the errors
[12:53] <Laney> it uses select_single from autopilot, don't know what that does
[12:54] <Mirv> that's at least used also by ubuntu-ui-toolkit which has all tests passing, so maybe it'd be worth asking AP people like thomi directly
[12:56] <Laney> ok
[12:59] <om26er> popey, here: https://code.launchpad.net/~om26er/ubuntu-weather-app/fix_db_tests/+merge/199278
[12:59] <om26er> popey, will the CI run on that branch ?
[13:06] <popey> om26er: lemme test it first
[13:07] <popey> it wont if nobody approves it
[13:09] <popey> testing now
[13:17] <lool> sil2100, Mirv: Feel free to bug me for packaging reviews if I'm around
[13:18] <sil2100> lool: thanks :)
[13:20] <asac> om26er: sergiusens do we have a breakthrough on those tests yet :)?
[13:20] <om26er> asac, I gave something to popey to test
[13:20] <om26er> WFM
[13:20] <popey> wfm too
[13:20] <asac> cool
[13:20] <asac> :)
[13:20] <asac> nice
[13:20]  * popey commented on the mr
[13:20] <asac> who need to approve so this can land?
[13:21] <asac> did something else land as well on trunk after we updated in image last time?
[13:21] <asac> lets get that removed :)
[13:21] <popey> mhall119: can probably approve https://code.launchpad.net/~om26er/ubuntu-weather-app/fix_db_tests/+merge/199278 for us
[13:21] <popey> when he awakens shortly.
[13:23] <sil2100> popey, om26er: with this fix in, the weather app AP tests are fixed?
[13:23] <popey> thats the plan
[13:23] <om26er> sil2100, atleast the one's that I was given link to
[13:23] <sil2100> om26er: +beer for you!
[13:25] <om26er> sil2100, ;)
[13:26] <sergiusens> asac, nothing; the apps with the most failures in testing have been apps that only hd test updates for the past two months
[13:32] <psivaa> sil2100: i dont have any devices with me at the moment :/
[13:33] <sil2100> om26er: sorry to bother you again, but maybe you by some lucky chance have some UT compatible bluetooth devices? ;)
[13:33] <om26er> sil2100, I don't have. the one in my car is not supported by Ubuntu touch
[13:35] <sil2100> sergiusens: hi! I had some questions related to LP: #1234361
[13:35] <sil2100> sergiusens: someone reported on the ML that it's not fixed - and I can't find anyone that would have the equipment for re-testing this
[13:37] <sil2100> sergiusens: do you have the tools to check if this is fixed with the latest image?
[13:38] <asac> sergiusens: ok... please help the fix get into the store and then lets build an image
[13:38] <asac> psivaa: mako still has no resutls for 71
[13:39] <asac> http://ci.ubuntu.com/smokeng/trusty/touch/maguro/71:20131217.1:20131211.2/5521/
[13:39] <asac> (sorry if you answered)
[13:39] <asac> plars: ^^
[13:39] <psivaa> asac: looking at that, sorry dint notice that
[13:40] <asac> sil2100: did we promote 70 or do we have that in the bank and already well tested, but hope for 71 to be at least as good and push that?
[13:42] <sergiusens> sil2100, I don't have bluetooth headsets, but I can check from the cli and see if I find anything
[13:46] <sil2100> asac: from what I see, 71 doesn't have anything more than 70 (no packages updated)
[13:47] <sil2100> asac: so let's promote 70 anyway, since 72 will only be ready for tomorrow morning
[13:47] <sil2100> asac: if there is of course no cost of promoting an image that is
[13:47] <sil2100> It doesn't matter if we promote 70 or 71 basically
[13:48] <sil2100> But just to have a clear concious we can promote 70, since that's what popey and om26er used for testing
[13:48] <sil2100> lool: ^ could you promote 70 ?
[13:49] <lool> sil2100: yup
[13:49] <sil2100> Thanks!
[13:50] <plars> asac: just got to my desk, looking now, unless psivaa has already
[13:50] <psivaa> plars: the devices is shown as offline soon after flashing
[13:51] <psivaa> probably need to assign another device. mako-06 looks ok to do that
[13:52] <plars> psivaa: wow, it even shows in adb but shows offline
[13:53] <plars> psivaa: yeah, you want me to switch it, or do you want to?
[13:53] <psivaa> plars: i am in the sprint,so if you could. that would help
[13:53] <plars> psivaa: ack
[13:53] <psivaa> thanks plars
[13:56] <plars> rfowler: when you are around, could you take a look at mako-02? It's marked offline for some reason, so nothing can run on it. I've moved all the jobs from it to 06 for now
[13:57] <plars> asac: jobs are restarting now for mako on image 71
[13:59] <sergiusens> om26er, popey where's the MR
[13:59] <sergiusens> ?
[13:59] <popey> https://code.launchpad.net/~om26er/ubuntu-weather-app/fix_db_tests/+merge/199278
[14:00] <fginther> morning
[14:01] <lool> FYI, image promoted
[14:01] <lool> (70)
[14:01] <popey> lool: my phone can't see it
[14:01] <ogra_> pfft ... gimme 72 ... with 24h clock
[14:02] <sergiusens> popey, om26er ironically, the tests fail on jenkins
[14:02] <om26er> sergiusens, that's not related to my code
[14:02] <om26er> falky tests are flaky :/
[14:04] <sil2100> ogra_: patience!
[14:04] <ogra_> :D
[14:05] <lool> popey: something is wrong with the push mirrors
[14:07] <popey> indeed
[14:08] <lool> hmm maybe it's a cron and I had never realized
[14:09] <popey> it's usually immediately after ogra_ says it's published
[14:11] <ogra_> lool, nusakan seems dead here
[14:11] <ogra_> or at least inaccessible
[14:11]  * ogra_ cant ssh
[14:11] <lool> popey: it's being fixed
[14:11] <lool> ogra_: you need to use sshebang
[14:11] <lool> ogra_: or update your ssh config to use FQDN
[14:12] <cjwatson> ogra_: works fine for me
[14:12] <ogra_> since when ?
[14:12] <cjwatson> I don't use sshebang)
[14:12] <lool> ogra_: since some hours ago
[14:12] <ogra_> it worked on monday
[14:12] <lool> it worked wihtout .canonical.com up til this morning  :-)
[14:12] <ogra_> ah
[14:12] <cjwatson> my config has used nusakan.canonical.com for ages
[14:12] <lool> I raised it with #is, but it's intended
[14:12]  * ogra_ fixes /etc/hosts
[14:13] <ogra_> hmm, nothing to fix there it seems
[14:13] <ogra_> <IP_ADDRESS>	nusakan	nusakan.canonical.com
[14:13] <ogra_> but indeed, using the FQDN works
[14:13] <lool> cjwatson: ssh nusakan used to work without .canonical.com from the jump host, allowing to have a single .ssh/config entry for *.canonical.com + nusakan; now I have two
[14:14] <lool> ogra_: this is in your .ssh/config
[14:14] <cjwatson> I doubt that /etc/hosts matters.  Fix ~/.ssh/config
[14:14] <lool> ogra_: your proxycommand needs a FQDN
[14:14] <lool> ogra_: nc -q0 nusakan.canonical.com or nc -q0 %h.canonical.com
[14:14] <cjwatson> The host name is looked up on the proxy jumphost, not on your machine
[14:14] <cjwatson> And I'm pretty sure you can't write to chinstrap's /etc/hosts :)
[14:14] <ogra_> oh, ok
[14:15] <ogra_> thanks, that fixes it
[14:21] <popey> #70 on the way \o/
[14:22] <sil2100> \o\
[14:22] <sil2100> It's a bird, it's a plane! No, it's #70!
[14:23] <lool> IS should have fixed it entirely now
[14:23] <lool> I see #70 on trusty
[14:26] <sergiusens> om26er, check my comment on the MR
[14:27] <rfowler> plars: I'm going to 1ss in a bit... my car was completely frozen and had to thaw it before the next storm hits
[14:29] <plars> rfowler: ugh, be safe
[14:30] <plars> rfowler: it's no rush on our end, its up and running for now
[14:46] <om26er> sergiusens, pushed. looks better now ?
[14:47] <sil2100> sergiusens: did you have a moment to do that cli bluetooth sweep?
[14:47] <sergiusens> om26er, let me check; let's also get balloons on now that he's online
[14:47] <sergiusens> sil2100, no
[14:48] <sergiusens> om26er, looks better, let's wait for ci
[14:48] <balloons> om26er, are you looking @ weather or calendar?
[14:48] <sergiusens> balloons, weather
[14:48] <om26er> balloons, weather, and its cold.
[14:48] <sergiusens> balloons, https://code.launchpad.net/~om26er/ubuntu-weather-app/fix_db_tests/+merge/199278
[14:48] <asac> sergiusens: om26er: are we close :)?
[14:48] <sergiusens> om26er, it's 35 C
[14:48] <asac> the next image will be cut in 2h approx
[14:48] <asac> would be nice to have it in :)
[14:49] <sergiusens> asac, I can't approve MRs for community apps, but if it works, I'm fine with the solution
[14:49] <asac> balloons: can you plesae check that out?
[14:50] <asac> balloons: we have the fix pending for 100% dashboard gren on mako
[14:50] <asac> and i want to get this in opportunistically for next image
[14:50] <balloons> om26er, why are you readding launch and quit?
[14:51] <om26er> balloons, these tests assume ~/.local/share/com.ubuntu.weather/Databases/ to be there. It is only created once the app is started
[14:52] <om26er> balloons, since we manipulate an already existent database, and if the suite is not able to find one it fails without telling why it failed
[14:53] <balloons> om26er, we have the ability to create a db if one doesn't exist in the test
[14:53] <balloons> I don't believe this changes anything
[14:53] <balloons> launch and quit would be a regression imho
[14:54] <om26er> balloons, remove ~/.local/share/com.ubuntu.weather/Databases/ on your phone and run those tests, they fail with the traceback that's in the dashboard
[14:54] <om26er> balloons, then start the app with hands and run those tests again and they will pass
[14:55] <om26er> balloons, from what I saw from the test code is that it tries to add a few database entries to an already existent database, it does not create a whole new database
[14:55] <om26er> balloons, line 165 in __init__.py
[14:56] <balloons> om26er, I don't doubt your assessment. However, the fix imho is not to go back to the launch and quit thing. Let's just create a db from scratch if we need to
[14:59] <om26er> balloons, not really sure if that's going to be a simple task ? these are Qt LocalStorage databases, and there aren't nice APIs for python
[15:00] <balloons> om26er, well I understand the desire to push this in, but it's going to be tough to review beyond I would really like to not see launch and quite come back into this test
[15:02] <om26er> balloons, another nasty thought is: clear the db, launch the app, copy the db and ship that with weather app tests. In the test suite make sure to move any old db, copy the shipped one over to the default location, run the tests. Profit!
[15:04] <balloons> om26er, I would be happier with that kind of approach
[15:04] <balloons> if we can't build it on the fly, just ship it with the tests and copy it it to set it up that way
[15:05] <om26er> balloons, ok, I can work on that. btw how do these tests get in in the first place ?
[15:07] <om26er> ah, i would assume CI test runner passed those tests because that db was already there due to not having a clean environment.
[15:12] <sergiusens> balloons, popey om26er we need a happrover
[15:13] <balloons> sergiusens, om26er is going to make the tweak I asked for
[15:13] <sergiusens> balloons, ack, feels lke a recap from an earlier conversation ;-)
[15:13] <balloons> sergiusens, :-) I'm sure he works quick and we'll have it
[15:34] <plars> cwayne: looks like the attempt  I made last night with custom on the new mako had a strange problem, going to retry it and see what happens, but that's not something I've seen happen before
[15:36] <cwayne>  plars ah, ok
[15:36] <cwayne> i was going to ping you since i saw all 0's, but I thought it might be too early :)
[15:46] <nic-doffay> Hey, having some CI issue I can't seem to figure, anyone mind taking a look? https://code.launchpad.net/~nicolas-doffay/ubuntu-ui-toolkit/fix-1242647/+merge/197176
[15:54] <asac> sergiusens: balloons: om26er: stuff in?
[15:54] <asac> people are waiting with aggressive uploads
[15:55] <asac> that will brick us for weeks
[15:55] <asac> i can hold the line for a bit longer :)
[15:55] <asac> but... :)
[15:56] <om26er> asac, just pushing the fix
[15:59] <sergiusens> asac, which means it's another hour until it's fully in
[16:00] <sil2100> sergiusens: we can wait with kicking the build a bit after the meeting, so hour more is ok
[16:02] <sergiusens> sil2100, really depends on the infra after the review...
[16:03] <asac> sergiusens: yes, thats fine
[16:03] <asac> right in time for our standup
[16:03] <asac> to agree on kicking
[16:05] <balloons> om26er, please ping when you need approval
[16:14] <mhall119> popey: do you still need somebody to top-approve https://code.launchpad.net/~om26er/ubuntu-weather-app/fix_db_tests/+merge/199278 ?
[16:17] <popey> mhall119: i think balloons is on it.
[16:23] <rfowler> plars: mako-02 is up
[16:23] <plars> rfowler: cool, thanks - what was going on with it?
[16:24] <rfowler> plars: it visually seemed just fine
[16:24] <plars> rfowler: odd, adb had it marked offline
[16:24] <rfowler> plars: ya... not sure
[16:44] <balloons> om26er, how's it going?
[16:50] <om26er> balloons, https://code.launchpad.net/~om26er/ubuntu-weather-app/db_stab2/+merge/199321
[16:51] <balloons> om26er, :-)
[16:54] <sergiusens> balloons, om26er I added 2 comments
[16:59] <sil2100> sergiusens, om26er, balloons: so I guess we won't make it with the fix before the meeting ;) ?
[16:59] <balloons> it'll be during the meeting :-)
[17:00] <sil2100> robru, kenvandine, cyphermox, lool: meeting?
[17:00] <sergiusens> balloons, om26er also need to use the module path to determine where to copy the database from, look at the music app as an example
[17:01] <om26er> sergiusens, so I do os.path.join inside os.path.expanduser wouldn't that hurt readability more ?
[17:01] <sil2100> asac: coming?
[17:01] <asac> sil2100: yep
[17:02] <sergiusens> om26er, do it in two steps, but doing a + is not pretty and could concatenate the wrong path
[17:03] <sergiusens> om26er, alternatively, just have db_file and drop db_path and use path.dirname
[17:06] <balloons> tests do run fine on my device
[17:06] <balloons> I think Sergio has nailed the syntax bits
[17:06] <asac> sergiusens: all in?
[17:06] <asac> :)
[17:06] <asac> e.g. can we kick ?
[17:07] <lool> do I need to start a build?
[17:07] <sergiusens> asac, read like 5 lines above; MR got in 10 minutes ago
[17:07] <sergiusens> asac, still under review
[17:09] <om26er> sergiusens, pushed
[17:11] <asac> sergiusens: i dont understand the steps it takes
[17:11] <asac> before we can build an imge
[17:11] <asac> hence i am only asking about the final YES its all ready
[17:11] <asac> or no, i have to do X,Y still :)
[17:11] <sergiusens> asac, ok, fyi, we are at step 1
[17:12] <sergiusens> asac, I'll get back to you when it's in
[17:12] <asac> sergiusens: so what steps are left?
[17:13] <asac> and whats the ETA?
[17:13] <asac> i need to tell folks that they have to wait with uploads etc.
[17:13] <kenvandine> sil2100, https://code.launchpad.net/~ken-vandine/cupstream2distro-config/no_ap_settings/+merge/199325
[17:14] <sergiusens> asac, needs to get review approved, tested and then merged by the autobuilders, then build the click; test the click, then push to store; then have it synced
[17:14] <kenvandine> sil2100, that should be enough to keep it from block on the check step
[17:14] <sergiusens> asac, as I said, an hour after the MR is in
[17:14] <balloons> ahh sergiusens sorry.. I thought it was a bit quicker after the MR was in
[17:15] <balloons> I said we'd laid in the MR very shortly, and I didn't think it would take much beyond that
[17:15] <sergiusens> balloons, well it's mostly waiting on infra most of the time
[17:15] <sergiusens> balloons, I can also blindly push without testing myself
[17:16] <popey> sergiusens: ping when you want the click package testing
[17:16] <sergiusens> popey, ack
[17:17] <balloons> sergiusens, I'm running the MR with and without db prexisting
[17:18] <sergiusens> balloons, the problem isn't going to be click, but when running on a clean env as a deb
[17:18] <sergiusens> as a click we cd into the autopilot dir
[17:19] <sergiusens> but as a deb we on desktop, that's not the case
[17:26] <sil2100> kenvandine: could I ask for commenting that out instead of removing? :) Otherwise I'm sure I'll forget that the test should be there ;p
[17:26] <kenvandine> ok
[17:28] <kenvandine> sil2100, pushed
[17:30] <sil2100> Thank you! Approving
[17:32] <balloons> om26er, sergiusens made some further suggestions. I'm happy with it as he is suggesting. It runs great for me.
[17:32] <balloons> om26er, with those tweaks I think we're good
[17:34] <om26er> balloons, done
[17:35] <om26er> aah there are more suggestions
[17:36] <sergiusens> om26er, balloons also look at how I'm getting the module path http://paste.ubuntu.com/6589958/
[17:36] <sergiusens> didnt' test that part yet though
[17:42] <balloons> om26er, thanks for keeping on this.. It's worth getting it right before it goes in..,
[17:46] <sergiusens> balloons, om26er with the changes I proposed, still get all tests passing as click
[17:46] <balloons> tested on desktop and device with and without db
[17:46] <Laney> we're releasing u-s-s?
[17:46] <Laney> neat
[17:47] <sil2100> Laney: yes \o/
[17:48] <Laney> would have reviewed the outstanding branches if I knew
[17:48] <sil2100> Laney: kenvandine handles that, we'll deal with the AP tests later - no need to keep the package waiting, since we're not yet using those extensively
[17:48] <asac> balloons: isnt the current code good enough? you can still improve after its out :) ... all we need is code that fixes the tests for now
[17:48] <kenvandine> Laney, we can land it again
[17:48] <Laney> it's okay, I'm looking at something there
[17:48] <kenvandine> it had just been ages
[17:48] <om26er> balloons, sergiusens pushed you suggestions.
[17:49] <om26er> *yours
[17:49]  * asac sorry for being inheritently impatient :)
[17:49] <Laney> those tests select a QQuickView
[17:49] <Laney> trying to copy what gallery-app does instead
[17:49]  * asac goes off and waits for another hour
[17:50] <sergiusens> asac, it is prone to fail on desktop
[17:50] <sergiusens> om26er, did you add the module path detection?
[17:50] <sil2100> ;)
[17:50] <om26er> sergiusens, no, I am not adding that ;)
[17:51] <sergiusens> om26er, why?
[17:51] <om26er> sergiusens, I don't understand that well and I am not really productive at this O'clock
[17:51] <asac> do we care about desktop? not sure what it means if we say it fails there
[17:52] <sergiusens> asac, you don't today, but you will tomorrow and when you do you won't be able to pinpoint the problem as easily
[17:53] <sergiusens> asac, I'll abstain and leave it to balloons and popey
[17:53] <asac> ok.
[17:53] <asac> balloons: popey: whats next? did we give up?
[17:53] <sil2100> hmmm
[17:53]  * popey is on a hangout, will catch up in a moment
[17:53] <sergiusens> asac, they need to approve the MR
[17:53] <sil2100> sergiusens, balloons, om26er: so no weather-app update today, right?
[17:53] <popey> or you can summarise in one tweet size line
[17:53] <sergiusens> asac, and then I continue
[17:54] <asac> sil2100: i hope the answer is that we get it
[17:54] <asac> soonish
[17:54] <balloons> sil2100, I was under the impression we could go as soon as the MP landed, but sergiusens informed me it takes a bit.
[17:54] <sergiusens> sil2100, asac it will be in
[17:54] <sil2100> \o/
[17:55] <sil2100> sergiusens, balloons: could you guys poke us once the fix is in and ready to be fetched by a new image?
[17:55] <asac> balloons: when will the MP land though
[17:55] <asac> i think thats where sergiusens is stuck
[17:55] <sergiusens> sil2100, that was the plan all along
[17:56] <balloons> sergiusens, om26er  commented with "Not creating the dir in the test code. shutil.copytree calls makedirs so no need"
[17:56] <sergiusens> asac, I was reviewing the MR and detecting possible failures for the future; that's all; it's been like this forever with these apps; just want to do it once and not have to go over this again
[17:56] <sergiusens> om26er, balloons let me take over the MR
[17:57] <asac> ok. dont make rocket science out of this
[17:57] <asac> :)
[17:57] <asac> but keep engineering standards high
[17:58] <balloons> yes, at this point we're not after quick fixes.. we'd had those for awhile. Being agonizingly detailed on these MP's is what has gotten us to this point
[17:58] <balloons> as in, so close to 100% with core apps not falling over randomly :-)
[17:58] <asac> well, the goal shoujld be to have a fix soon
[17:58] <asac> whatever best solution is a vailable
[17:58] <asac> if code is not good enough you can iterate
[17:58] <sergiusens> balloons, I fixed that in my proposal
[17:59] <asac> balloons: well, so we have big destructuve landings happening later today
[17:59] <asac> hence i want this in to get to complete cgreen etc.
[17:59] <asac> let me know what is left
[17:59] <asac> and then lets do it
[17:59] <balloons> sergiusens, you make a new mp or ?
[18:01] <sergiusens> balloons, I will resubmit
[18:02] <sergiusens> balloons, I don't have privs, but can you resubmit that MR with lp:~sergiusens/ubuntu-weather-app/db_create
[18:04] <balloons> sergiusens, https://code.launchpad.net/~sergiusens/ubuntu-weather-app/db_create/+merge/199333
[18:04] <balloons> sergiusens, add a logging statement under if not os.path.exists(db_path): if you do create a db
[18:07] <sergiusens> balloons, done
[18:11] <balloons> first results on desktop and phone are good.. running again
[18:12] <balloons> jenkins builder is running
[18:19] <cwayne> plars, looks like touch_custom still has some issues
[18:24] <sil2100> balloons: soooo... will it be merged soon :) ?
[18:24] <sil2100> \o/
[18:29] <plars> cwayne: indeed, that's very strange considering how stable the other builds have been
[18:29] <plars> cwayne: anything odd about that mako?
[18:31] <cwayne> not that i know of plars
[18:33] <cwayne> plars, hm, looks like it is having an issue with the theming perhaps?
[18:34] <plars> cwayne: is it confusing the ap tests somehow?
[18:34] <cwayne> plars, i'm not 100% sure, is it installed with --no-backup or -b?
[18:34] <cwayne> i wonder if it's looking for an old theme or something
[18:34] <cwayne> is there any way to get ssh access to it?
[18:35] <plars> cwayne: -b, yes
[18:35] <cwayne> maybe our customizations really is breaking stuff, in which case, good thing we did this!
[18:36] <plars> cwayne: if you need ssh access, talk to rfowler or retoaded about getting ssh to a system called "ashes", it hangs off of there
[18:36] <cwayne> rfowler, ^
[18:43] <robru> who's doing the latest image build? can somebody ping me when it's done?
[18:51] <asac> we are waiting on MP landing still
[18:52] <asac> and store upload i guess
[18:55] <rfowler> cwayne: try logging into ashes
[18:56] <cwayne> rfowler, what's the ip?
[18:56] <rfowler> cwayne: it's in dns
[18:56] <cwayne> or is it just ashes.ubuntu-ci
[18:56] <rfowler> cwayne: yes
[18:56] <cwayne> rfowler, k im in
[18:57] <rfowler> cwayne: enjoy
[18:57] <cwayne> rfowler, which device is it?
[18:58] <rfowler> cwayne: 01ce848e48dfa6a2
[19:00] <cwayne> hm, the theming stuff is all correct there
[19:00] <cwayne> maybe autopilot doesn't like it for some reason?
[19:01] <balloons> sil2100, yes "soon". have  you heard that before?
[19:13] <sil2100> :)
[19:13] <balloons> sil2100, mp is top approved so it's up to jenkins now ;)
[19:14] <sil2100> \o/
[19:14] <sil2100> Do you know when it will be available for the image to pull it in?
[19:15] <sil2100> sergiusens: ^ ?
[19:15] <sergiusens> sil2100, 30'
[19:15] <sergiusens> speeding
[19:16] <cwayne> plars, so i see how the tests are failing, i still don't get *why* though, especially since it seems to work when i run it manually
[19:19] <sergiusens> sil2100, code hasn't merged yet... it's in the pipes, as soon as that's done, the equivalent of a daily release for a click package happens, goes to the store, then there's a sync to the ubuntu-archives
[19:19] <plars> cwayne: I was going to try rerunning some of them, but the number of failures on each one of the failing tests looks to be the same as the last time it ran too
[19:19] <plars> cwayne: pretty much the same failures on both 67 and 68
[19:20] <cwayne> plars, so it's apparmor denying requests for the custom theme we have
[19:20] <plars> cwayne: ah
[19:20] <cwayne> plars, but what doesnt make sense to me is that when you actually are using it, the custom theme shows up just fine
[19:20] <plars> cwayne: doesn't seem to affect all apps, but it does seem to affect certain apps consistently
[19:21] <balloons> doanac, my friend. vanguard i trust :-) Can you have a look at this: https://code.launchpad.net/~vthompson/music-app/fixes-1259962/+merge/198601. Jenkins isn't landing the merge for some reason. The builders are failing
[19:21] <cwayne> plars, right, but im looking at an emulator instance now with the devel-proposed-customized, and the gallery app is 100% properly themed
[19:22] <cwayne> plars, and there's no errors, so something's weird
[19:22] <cwayne> somehow running it from autopilot is making it denied
[19:24] <sil2100> sergiusens: ok, let's wait till then
[19:24] <cwayne> plars, is autopilot confined in some way?
[19:26] <plars> cwayne: yes, it all runs identically to how we run on the other images
[19:26] <doanac> balloons: sorry. was grabbing lunch. looking now
[19:26] <cwayne> plars, so what's happening is it's getting denied looking for /custom/xdg/data/themes when running from autopilot
[19:26] <cwayne> but when actually using the device, it's allowed
[19:27] <fginther> sergiusens, re: https://bugs.launchpad.net/ubuntu-ci-services-itself/+bug/1259568 - I don't have anything scripted yes
[19:28] <fginther> 'yet'
[19:28] <sergiusens> fginther, ack; so what we need to script is rather easy and was sort of stripped out of the build setup when going public, what we can do something similar
[19:29] <sergiusens> fginther, if you are working on something; I can review and add your missing parts
[19:29] <sergiusens> fginther, are you working on something that sets up the environment and another that works on the build?
[19:30] <fginther> sergiusens, right, a script to just set up the env would be adequate
[19:30] <cwayne> plars, is there a reason syslog isn't an artifact of the test runs?
[19:31] <fginther> sergiusens, I can put something together quick with the steps I performed as a start
[19:31] <sergiusens> fginther, sounds good
[19:35] <sergiusens> popey, https://myapps.developer.ubuntu.com/dev/click-apps/147/
[19:36] <plars> cwayne: iirc, it should come in the console output stream
[19:36] <plars> doanac: can you confirm? is that what we get in utah with the 'with device.tail_syslog()'?
[19:37] <popey> sergiusens: ack
[19:38] <doanac> plars: that is correct
[19:40] <doanac> plars: ie - the syslog should be in the jenkin job's console output
[19:41] <doanac> balloons: making progress on your issue. looks like the clock drifted on the build slave. working to get it fixed now
[19:42] <cwayne> i'm not seeing it there, i should be seeing the apparmor denials
[19:46] <popey> sergiusens: approved
[19:46] <doanac> balloons: you can top-approve and it should work now
[19:46] <balloons> doanac, k.. ty!
[19:51] <sergiusens> popey, yay
[19:52] <sergiusens> cjwatson, do you mind manually triggering the click sync please?
[19:56] <ChrisTownsend> fginther: Hey, to follow on that Unity armhf debugging from yesterday, I know have a test mesa in a PPA we can try.
[19:57] <ChrisTownsend> *now
[19:57] <fginther> ChrisTownsend, cool, what's the PPA? I'll kick off a build
[19:58] <ChrisTownsend> fginther: ppa:rocket-scientists/staging
[19:58] <ChrisTownsend> For armhf using that branch you used yesterday.
[19:58] <ChrisTownsend> fginther: Thanks!
[20:12] <sil2100> sergiusens: how's the sync?
[20:13] <sergiusens> sil2100, it's in, automated sync hits at 11' or 13' after the hour
[20:13] <sergiusens> we are good
[20:13] <asac> sergiusens: once an hour?
[20:13] <sil2100> \o/
[20:14] <sil2100> So I guess we're ok
[20:14] <sil2100> cyphermox: hi! Do you have a moment to press the build button?
[20:14] <asac> Q: how can we confirm that its really in (like: the image build will pick it up)? (like in archive we use rmadison)?
[20:18] <sergiusens> asac, it's in click_list and livecd-rootfs has a hook that picks it from there
[20:18] <cyphermox> sure
[20:18] <sergiusens> asac, so if it doesn't, we have a mitm :-)
[20:18] <asac> kk
[20:18] <asac> just checking :)
[20:18] <asac> lets go then
[20:19] <asac> if you confirmed it like that
[20:24] <ChrisTownsend> fginther: Could you send me the link to the build whenever you have it kicked off?
[20:26] <cwayne> plars, alright, so we've got an anwser for why all the clicks were failing on touch_custom
[20:26] <cwayne> still unsure of gallery-app though
[20:26] <cyphermox> sil2100: done
[20:27] <fginther> ChrisTownsend, http://s-jenkins.ubuntu-ci:8080/job/unity-trusty-armhf-ci/61/console
[20:28] <ChrisTownsend> fginther: Thank you
[20:29] <thomi> cihelp: I just noticed today that the job that updates the autopilot documentation has been broken for a while - look s like a networking issue: http://s-jenkins.ubuntu-ci:8080/job/autopilot-docs-upload/
[20:29] <thomi> I wonder if someone could take a look for me please?
[20:29] <fginther> thomi, looking
[20:30] <thomi> My guess is that since the machine moved lab, the firewall rules that IS look after will have to be changed
[20:30] <thomi> but that's just a guess :)
[20:30] <sil2100> \o/
[20:30] <sil2100> cyphermox: thanks!
[20:30] <sil2100> See you tomorrow everyone
[20:30] <fginther> thomi, timing of when the job started to fail would support that guess
[20:31] <thomi> fginther: yeah
[20:31] <fginther> thomi, I'll get a ticket filed to update the firewall
[20:31] <thomi> thanks
[20:31] <thomi> fginther: I assume once the FW is fixed you'll re-run the job?
[20:32] <fginther> thomi, I can if I remember to do so :-)
[20:32] <fginther> it usually takes them a while to respond to the request
[20:32] <thomi> fginther: thanks - I guess you'll run it to test the FW rules anyway
[20:33] <thomi> yeah, I usually hassle them on IRC :)
[20:40] <fginther> thomi, is maitri.canonical.com the correct destination?
[20:43] <thomi> fginther: yes
[20:59] <sergiusens> fginther, btw can we get automerge on lp:usensord? and some upcoming daily release prep?
[21:03] <fginther> sergiusens, I can help with setting up automerge, sil2100 and company can help with the daily-release prep
[21:04] <sergiusens> fginther, sure, just not sure how to make the request these days :-) seems the team is pending a merge :-P
[21:30] <fginther> sergiusens, this will take more time than usual, lp:usensord requires dh-golang on the host which isn't available for raring (which the build machines are currently running)
[21:34] <sergiusens> fginther, we just want trusty
[21:34] <sergiusens> oh
[21:34] <sergiusens> still raring?
[21:36] <fginther> sergiusens, it's a build host thing: http://s-jenkins.ubuntu-ci:8080/job/usensord-trusty-i386-ci/2/console
[21:37] <fginther> sergiusens, my plan was to move them to saucy eventually, this appears to be the trigger to start that process
[21:41] <cyphermox> fginther: daily-release-executor?
[21:41] <sergiusens> fginther, it's not super hard to backport dh-golang btw; just a bunch of perl scripts
[21:42] <fginther> cyphermox, I was waiting for the job to finish before change the connection method, looks like that just happened
[21:42] <fginther> cyphermox, should be back in a few minutes now
[21:48] <fginther> cyphermox, it's back up now
[21:49] <cyphermox> thanks
[22:00] <fginther> sergiusens, can I get back to you tomorrow on lp:usensord?
[22:01] <fginther> ChrisTownsend, the unity armhf build passed with your PPA
[22:17] <sergiusens> fginther, sure
[22:17] <sergiusens> fginther, I will have around 5 more jobs using dh-golang aprox fwiw
[22:17] <sergiusens> soon more to come
[22:26] <thomi> fginther: got a second?
[22:26] <fginther> thomi, yep
[22:27] <fginther> thomi, I do have a hard stop in 30 minutes
[22:27] <thomi> fginther: before I can get the new autopilot released to distro, I need to prove that it doesn't break anything...
[22:27] <thomi> in the past you made us a jenkins job to do this, I believe?
[22:27] <thomi> I'm trying to figure out how I can do this again, but there are so many 'autopilot' jenkins jobs out there I'm not sure what I should be looking at
[22:27] <fginther> thomi, yes, we did that for the 1.4 effort
[22:28] <thomi> fginther: right
[22:28] <thomi> do you remember which job it was?
[22:31] <fginther> thomi, found it: http://s-jenkins.ubuntu-ci:8080/job/autopilot-trusty-master/
[22:31] <thomi> sweet, let's see....
[22:32] <fginther> thomi, it worked by pulling the latest python-autopilot from the experimental ppa
[22:32] <fginther> thomi, is this for python3-autopilot?
[22:32] <thomi> fginther: sure
[22:32] <thomi> fginther: actually, I'm not sure
[22:32] <thomi> fginther: this is for whatever you use normally
[22:33] <fginther> python-autopilot in that case
[22:33] <thomi> yeah
[22:34] <thomi> so target_branch is the project whose tests I want to run... what do I put in landing_candidate?
[22:35] <fginther> landing_candidate is actually the value that holds the branch to test, target_branch is the 'trunk' branch
[22:35] <fginther> sorry, that's confusing
[22:36] <fginther> landing_candidate is the branch to test, target_branch is the 'trunk' branch. They can be identical
[22:37] <thomi> fginther: ok.. and this won't actually land anything though, right?
[22:37] <fginther> thomi, nope, it just buids and tests
[22:38] <thomi> awesome, thanks
[22:38] <fginther> thomi, hope that helps
[22:38] <thomi> fginther: testing it out now
[22:40] <thomi> fginther: are there still only 4 test runners in the pool? Just wondering how far I can push this
[22:40] <thomi> don't want to starve the rest of Canonical
[22:40] <fginther> thomi, yes still have just the 4
[22:40] <thomi> ok, thanks
[22:46] <Laney> thomi: if you have some time, can you cast a look at the autopilot tests in lp:ubuntu-system-settings on the device please? All but the most basic ones are broken & none of us has the autopilot smarts to figure it out
[22:47] <thomi> Laney: got a link to a failure page?
[22:48] <Laney> thomi: umm, a pastebin, don't know if there was an official run
[22:48] <Laney> thomi: http://paste.ubuntu.com/6586198/ was one robru did yesterday
[22:49]  * thomi looks
[22:49] <Laney> I guess it's some weirdness around how vrruiz set it up originally
[22:50] <thomi> ok, it looks like maybe the object names have changed or something. I can add it to my list of things to look at, but it's unlikely I'll get to it before tomorrow morning...
[22:50] <Laney> it passes on desktop
[22:50] <Laney> that's probably an important piece of information that I forgot to say :-)
[22:58] <thomi> interesting
[23:20] <robru> Laney, thomi : yep those failures are on mako
[23:22] <Laney> my brain is too small to understand it


  CHOLBY RULES
[08:08] <hicoleri> I there a definitive guide I can follow to learn about setting up a webserver, server-side scripting in the language I want and websockets?
[09:00] <lordievader> Good morning.
[12:22] <mollox> hi (i come here as directed by https://help.ubuntu.com/lts/serverguide/httpd.html )
[12:22] <mollox> does anybody know if it is possible to increase the apache2 process priority
[12:22] <mollox> in the config
[12:27] <ikonia> apache doesn't set the priority
[12:27] <ikonia> the scheduler does
[12:28] <mollox> ok
[12:28] <mollox> thanks
[12:29] <mollox> be nice to set nice .. bnvm
[12:31] <ikonia> should you really need to set it ?
[12:31] <ikonia> if you need apache at a high priority than the scheduler thinks....are you using apache right
[12:31] <mollox> if i set it through system-monitor i get a tiny bit better download speed over LAN
[12:32] <ikonia> download speed ?
[12:32] <ikonia> what's the actual problem you're trying to solve
[12:32] <mollox> it's not that important .. but i am copying 12gb .. and waiting a long time :)
[12:32] <ikonia> 12GB over http
[12:32] <mollox> yeah
[12:32] <ikonia> doesn't seem the best of ideas
[12:33] <ikonia> nice'ing apache shouldn't be required,
[12:33] <mollox> i could use a usb disk ..
[12:33] <ikonia> why are you using http ?
[12:33] <ikonia> why not something like rsync
[12:33] <mollox> nice=-20 gives me just a bit better speed
[12:33] <mollox> rsync uses ssl
[12:33] <ikonia> mollox: thats a false economy
[12:33] <mollox> it's only for me
[12:33] <ikonia> so ?
[12:33] <ikonia> what's the problem with rsync
[12:34] <mollox> ssl overhead
[12:34] <ikonia> nonsense
[12:34] <ikonia> it will be quicker than 12GB over http
[12:34] <ikonia> and if you drop a packet you don't have to start again
[12:34] <mollox> tried it .. it is maybe 150% more
[12:34] <mollox> time
[12:34] <ikonia> no way
[12:34] <ikonia> you have a problem ten
[12:34] <ikonia> thne
[12:34] <mollox> well it is on my old rig
[12:34] <ikonia> then
[12:35] <mollox> encrypt at source and decrypt at dest adds a serious over head for 12gb
[12:37] <mollox> normal priority gives about 1.8mb/sec over 100mbit LAN
[12:37] <mollox> nice=-20 gives about 2.4mb/sec
[12:38] <ikonia> disagree
[12:39] <mollox> do it and see .. i am doing it now
[12:39] <mollox> anyway .. it's only for one file and only need it done once
[12:39] <maswan> what kind of servers are these? it's been a long, long time since a normal httpd would saturate a gigE with insignficant cpu load
[12:40] <mollox> its a 100mbit not Gbit
[12:40] <mollox> server is an old intel p4 2.3ghz
[12:42] <maswan> yeah, that's the generation of hardware that were among the first to be able to solidly sustain gigE
[12:43] <mollox> cpu load is ~14%
[12:43] <mollox> with ssl the jumps to ~35%
[12:43] <mollox> ~25%*
[12:44] <mollox> its working fine .. just wondered about the apache2 config and nice .. many programs let you set it in config .. not apache .. nvm
[12:45] <RoyK> mollox: how is the load average as reported by for instance 'uptime'?
[12:46] <mollox>  13:45:46 up  2:41,  3 users,  load average: 3.28, 2.78, 2.51
[12:46] <RoyK> mollox: how many cpu cores?
[12:46] <mollox> server = 2cpu (not cores tho)
[12:47] <mollox> pentium4 2.3ghz x2
[12:47] <RoyK> generally, the load average shouldn't be higher than core count
[12:47] <RoyK> that indicates a heavily loaded system
[12:47] <RoyK> either cpu or I/O or both
[12:47] <mollox> i guess it is a bit over loaded
[12:48] <RoyK> not a lot, though
[12:48] <mollox> well .. gotta get the most out of it ;)
[12:48] <RoyK> how old is this box?
[12:48] <mollox> oooold .. 10years or so
[12:49] <RoyK> probably older
[12:49] <mollox> i expect it was when first launched .. i had this for 10years ish
[12:49] <mollox> and it is XPC-Shuttle (SIS chipset i think)
[12:50] <mollox> its done a great job in its lifetime
[12:58] <mollox> Phew ! saved by wget .. thought it was gonna bail out at 93%
[13:07] <mollox> all done .. thanks for your time .. b4n