[02:10] <imgbot> [03:35] <imgbot> [03:35] <imgbot> [04:06] <alecu> yay new clickscope.
[04:06]  * alecu flashes #98
[07:15] <tvoss> sil2100, could you reconfigure silo 13 for me? hijacking your MP to address an issue with trust store db creation
[07:20] <dpm> hi, could someone retrigger the Jenkins jobs for these two MPs?:
[07:20] <dpm> https://code.launchpad.net/~carlos-mazieri/ubuntu-filemanager-app/bug-openPath/+merge/224535
[07:21] <dpm> https://code.launchpad.net/~carlos-mazieri/ubuntu-filemanager-app/filemanager-devel/+merge/224527
[07:29] <popey> dpm: done
[07:30] <popey> dpm: poke vila if you want to get the ability to retrigger yourself.
[07:31] <dpm> awesome, thanks popey!
[07:31] <popey> np
[07:31] <sil2100> tvoss: ok!
[07:32] <sil2100> tvoss: to make things better you could have just added an additional MP instead of overwriting mine ;)
[07:35] <popey> ogra_: how long would you expect 40% battery to last on the nexus 4 when doing "nothing" ?
[07:37] <sil2100> tvoss: by adding a merge on top you would assure that I would be mentioned in the changelog properly
[07:38] <tvoss> sil2100, oh sorry :/
[07:38] <tvoss> let me fix that
[07:40] <tvoss> sil2100, done :) could you reconfigure?
[07:41] <sil2100> tvoss: thanks! Should be reconfigured soon
[07:41] <sil2100> Done
[07:41] <tvoss> sil2100, thanks
[07:42] <tvoss> sil2100, building, grabbing coffee, back in 15
[07:48] <ogra_> popey, 3-4h at least
[08:04] <tvoss> sil2100, ping
[08:04] <sil2100> tvoss: pong
[08:05] <sil2100> psivaa, ogra_: does anyone of you know what happened to test results from #98?
[08:05] <sil2100> Was there some device failure again?
[08:05] <ogra_> how do you mean ?
[08:05] <psivaa> sil2100: just looking at that
[08:05] <ogra_> no
[08:06] <ogra_> we had that yesterday too ... seems the UITK tests suddenly run very slow/long
[08:06] <sil2100> But there are also failures in the SDK and such
[08:07] <seb128> tvoss, hey, I NEW reviewed the trust-store yesterday, looks fine, but the build fails on test issues (not sure if you noticed)
[08:07] <tvoss> seb128, yup, on it :) thanks for the review
[08:07] <sil2100> seb128: yep, we're looking a it :) tvoss is fixing it now
[08:07] <seb128> tvoss, yw!
[08:07] <seb128> sil2100, hey, wb
[08:08] <tvoss> seb128, the tests fail due to /home/buildd not being accessible :) will set XDG_DATA_HOME in debian/rules to /tmp for the build
[08:08] <seb128> sil2100, not sure if you got pinged about that yet, but Pat was asked people about libqofono
[08:08] <seb128> tvoss, that makes sense
[08:08] <sil2100> seb128: yeah, I already had a talk with both him and Steve yesterday about that
[08:09] <ogra_> sil2100, i told you about the sdk failure yesterday
[08:09] <psivaa> ogra_: sil2100: uitk is still taking too long
[08:09] <ogra_> sil2100, zbenjamin is on it afaik ... its a simply package name change
[08:09] <seb128> sil2100, what's the status then? Ken asked me to push the settings changes through but that's blocking on the bindings to land
[08:09] <ogra_> (qtsensors-dev doesnt exist anymore)
[08:09] <sil2100> seb128: so I'm finishing up the package now, as the only outstanding problem is that the unit-tests cannot run correctly on build right now
[08:10] <sil2100> seb128: the ETA is today before evening at max
[08:10] <seb128> sil2100, k, great, thanks
[08:10] <sil2100> seb128: Ken disabled running tests, but Steve said it's best if we simply get them working
[08:10] <seb128> sil2100, let me know when you want a NEW review
[08:10] <sil2100> Sure :)
[08:10] <seb128> yeah, it's best
[08:10] <sil2100> Thanks!
[08:10] <sil2100> ogra_: ah! Right, forgot about it
[08:11] <tvoss> sil2100, seb128 pushed update, building now
[08:12] <seb128> tvoss, great, let's see how that goes
[08:13] <sil2100> tvoss: \o/
[08:17] <ogra_> bah, the webbrowser-app test gets worse every day
[08:24] <tvoss> seb128, sil2100 I added a preliminary AGPS test plan here: https://wiki.ubuntu.com/Process/Merges/TestPlan/location-service
[08:24] <tvoss> seb128, sil2100 could you guys give it a spin with silo 11?
[08:24] <sil2100> tvoss: maybe davmor2 could help out with testing this?
[08:25] <tvoss> sil2100, cool, thank you
[08:25] <tvoss> davmor2, ping
[08:25] <sil2100> tvoss: I need to finish up some things before I would have enough time to properly test this ;)
[08:25] <tvoss> sil2100, ack
[08:26] <seb128> tvoss, I can test that, is "Obtain a (rough) location estimate for your current location on Google maps. " meant as "go and select manually the location" or is it supposed to detected/show it?
[08:27] <tvoss> seb128, manually select the location :)
[08:27] <seb128> k
[08:27] <seb128> what should be the result of the steps?
[08:27] <seb128> because I don't see a work/fail description in there
[08:28] <seb128> like you run the gps_provider_test command then...?
[08:28] <tvoss> seb128, it will tell you if it failed or succeeded in the end, takes some time
[08:28] <seb128> k
[08:28] <tvoss> seb128, will add that to the description
[08:28] <seb128> thanks
[08:28] <tvoss> seb128, also: https://location.services.mozilla.com/leaders#ubuntu_location_service
[08:29] <tvoss> sil2100, seb128 looks good, only arm64 still building
[08:29] <tvoss> https://launchpad.net/~ci-train-ppa-service/+archive/landing-013/+packages
[08:29] <seb128> great
[08:33] <tvoss> seb128, sil2100 the build passed successfully on all architectures https://launchpad.net/~ci-train-ppa-service/+archive/landing-013/+packages
[08:33] <sil2100> tvoss: I'll publish it after the meeting :)
[08:33] <tvoss> seb128, sil2100 thank you
[08:37] <tvoss> seb128, did you manage to start the test following the instructions on the wiki?
[08:41] <seb128> tvoss, I'm just on it ... running that apt-get install commands doesn't lead to update qtubuntu-sensors, is that fine or do I need the ppa version?
[08:41] <tvoss> seb128, you don't need qtubuntu-sensors for the agps test
[08:41] <seb128> tvoss, k, I was just looking at what is the ppa, platform api as well
[08:41] <tvoss> seb128, yup, not needed for this
[08:41] <seb128> great
[08:41]  * seb128 runs command
[08:43] <seb128> tvoss, the command bails out with
[08:43] <seb128> C++ exception with description "the argument ('INSERT_ESTIMATE_HERE') for option 'ref_lat' is invalid" thrown in the test fixture's constructor.
[08:43] <seb128> [  FAILED  ] HardwareAbstractionLayerFixture.time_to_first_fix_cold_start_with_supl_benchmark_requires_hardware (3 ms)
[08:43] <seb128> [----------] 1 test from HardwareAbstractionLayerFixture (3 ms total)
[08:44] <tvoss> seb128, ah, interesting, could you paste your command line? in pm, if you don't want to disclose your current location ;)
[08:45] <seb128> tvoss, no location info in there I think, http://paste.ubuntu.com/7704818/
[08:45] <Laney> pub, with beer, watching tennis
[08:45] <Laney> SHOCK!
[08:45] <seb128> lol
[08:45] <seb128> Laney, wimbledon ongoing, needs to do it the proper way!
[08:46] <Laney> oh yeah, s/beer/pimms/ it would be here :P
[08:46] <seb128> ;-)
[08:46] <tvoss> seb128, you have to replace INSERT_ESTIMATE_HERE with the lat lon values grabbed from google maps
[08:46]  * tvoss adjusts wiki description
[08:47] <seb128> tvoss, indeed, that makes sense, there is a long line of uppercase arguments, I didn't bother reading it, just copied
[08:47] <popey> s/pimms/Pimm\'s/
[08:47] <tvoss> seb128, done
[08:49] <Laney> ...
[08:58] <seb128> tvoss, bah, stopped on a enospace ... I cleaned some log and I'm trying again, how much disc-space is it using?
[08:59] <tvoss> seb128, that's a known issue, just try again ... not that much, need to look into where the android chipset driver tries to place assistance data
[09:01] <seb128> tvoss, not luck, hit that 4 times now, and I cleaned log and rebooted in between ... not sure on what partition I need to make space
[09:02] <tvoss> seb128, okay, thanks for trying though
[09:02] <brendand> ogra_, could be a repeat of 1974
[09:02] <seb128> yw, sorry it didn't work out
[09:02] <brendand> ogra_, but no home advantage this time :P
[09:03] <tvoss> seb128, all good, just preliminary test instructions :)
[09:03] <tvoss> seb128, what would help me is an strace :) could you remove GLOG_v=40 from the command line and try to get an strace?
[09:03] <popey> ogra_: camera-app 2.9.1+14.10.20140625.1-0ubuntu1
[09:03] <popey> that doesn't relate to https://code.launchpad.net/~phablet-team/camera-app/trunk ?
[09:04] <popey> what I see in s-jenkins is com.ubuntu.camera_<IP_ADDRESS>6_armhf.click built on 20th June.
[09:04] <popey> is that what you want?
[09:04] <ogra_> popey, no idea, probably there is something in the CI train history
[09:04] <popey> store has 280
[09:04] <popey> thats 286, which is latest trunk.
[09:04] <ogra_> no, the deb seems to have a timestamp of the 25th
[09:04] <popey> that needs to land in trunk surely?
[09:05] <ogra_> well, it should have been merged after landing
[09:05] <popey> ok, well I only ever pull from jenkins, if it's not there, then someone else needs to craft a click.
[09:06] <ogra_> https://code.launchpad.net/~jhodapp/qtubuntu-camera/update_includes/+merge/223824 and https://code.launchpad.net/~jhodapp/camera-app/reenable-video-recording/+merge/223578 are the landings
[09:07] <ogra_> bah
[09:07] <ogra_> both not top approved
[09:08] <seb128> tvoss, http://people.canonical.com/~seb128/log
[09:08] <ogra_> popey, i think sil2100 needs to merge and clean silo-002(line 17 on the spreadsheet)
[09:09] <ogra_> else it wont be merged
[09:09] <ogra_> (obviously)
[09:11] <popey> ok, so I'll stand down until someone creates the clicks sil2100
[09:12] <tvoss> seb128, are you sure that you ran as sudo?
[09:12] <seb128> tvoss, I'm root from adb shell
[09:12] <tvoss> seb128, hmmm, okay
[09:12] <tvoss> seb128, thanks, will look into it a little more
[09:13] <seb128> yw, let me know if you need more info
[09:16] <sil2100> ACK
[09:16] <sil2100> ogra_: right, I'll m&c it
[09:16] <sil2100> ogra_: normally it's the lander that does that...
[09:19] <tvoss> sil2100, did you have a chance to publish the trust-store silo, yet?
[09:20] <sil2100> tvoss: it's publishing now :)
[09:21] <tvoss> sil2100, thanks
[09:24] <sil2100> hmm, the spreadsheet is having some update problems again
[09:26] <pstolowski> cjwatson, ping
[09:49] <sil2100> popey: it's merged and cleaned
[09:49] <sil2100> ogra_: ^
[09:49] <ogra_> ok
[09:49] <ogra_> gallery too i suppose
[09:50] <ogra_> ah, yeah, according to the spreadsheet it is
[09:50] <sil2100> Yes, it was merged yesterday
[09:51] <popey> ack
[10:11] <cjwatson> pstolowski: same thing as you sent in /msg?
[10:12] <pstolowski> cjwatson, yes
[10:22] <popey> hmm, screen on my mako went off while I was running gallery autopilot tests
[10:24] <ogra_> oSoMoN, ^^
[10:25] <oSoMoN> how can I help?
[10:28] <sil2100> oSoMoN: it seems there are some problems when testing the new gallery-app
[10:28] <sil2100> With the workaround for the toolbar issue
[10:29] <oSoMoN> sil2100, what kind of problems? screen going off?
[10:30] <sil2100> popey: could you give some updates on your problem? ^
[10:30] <oSoMoN> note that before requesting publication yesterday I built a click from the branch, installed it and made sure autopilot tests ran fine on my device
[10:30] <popey> i will when it finishes
[10:30] <popey> its taking an _age_
[10:33] <popey> Ran 40 tests in 1411.403s
[10:33] <popey> FAILED (failures=6)
[10:33] <popey> lemme run again on flo
[10:35] <popey> ogra_: sil2100 http://paste.ubuntu.com/7705209/ thats me running gallery tests on mako
[10:39] <popey> oh yay! gallery tests have trashed my photos and videos
[10:39] <popey> ffs
[10:39] <popey> oh I lie
[10:39] <popey>  /ignore popey
[11:05] <popey> turns out phablet-config autopilot --dbus-probe enable takes a very long time when you have 360 apps installed
[11:08] <Saviq> sil2100, when rebuilding in a silo, is the old branch kept along at all, or is a new checkout & merge done?
[11:09] <sil2100> Saviq: if you rebuild a given component in a silo, then it checks out the sources from 0 and merges all merges from the beginning
[11:09] <sil2100> So the old branch is removed
[11:09] <Saviq> sil2100, ok cool
[11:17] <brendand> sil2100, webbrowser is clean from my pov
[11:17] <popey> sil2100: whats the status of silo 14? (can i see that status in a sheet somewhere?
[11:17] <brendand> sil2100, still running through ui toolkit
[11:18] <brendand> sil2100, not sure how we're going to handle the webbrowser ones. i'll have a closer look later to see if i can see anything
[11:18] <sil2100> popey: you can check the citrain spreadsheet and look at the sheet "landing-014"
[11:19] <sil2100> brendand: ok, thanks
[11:19] <brendand> sil2100, a lot of the failures are about this toolbar, or that keyboard, not being visible
[11:19] <popey> sil2100: link? ☻
[11:20] <sil2100> popey: ah :)
[11:20] <sil2100> popey: https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AuDk72Lpx8U5dFVHQ3FuMDJGLUZCamJfSjYzbWh3Wnc&pli=1#gid=32
[11:22] <popey> thanks sil2100
[11:22] <popey> thostr_: is landing 14 a problem? says one of the packages wasnt built?
[11:25] <sil2100> yw!
[11:26] <davmor2> popey: is your phone on 98 or 97?
[11:27] <popey> both
[11:27] <davmor2> the one that is on 98 is it actually on 98
[11:27] <popey> oh, ilied, one is 95, one is 98
[11:29] <davmor2> popey: I upgraded this morning I've been testing opened up the settings app and it said there was an update that is 98 so I just checked via system-image-cli -i and -n and yes my phone is on 97 and 98 is available. So I updated via s-i-c and now it reads exactly the same
[11:29] <davmor2> so it goes through the whole update process but remains on 97
[11:30] <popey> mine is #98
[11:30] <davmor2> right I'll do a fresh wipe then I wonder if it is because I modded the system to test silo020
[11:44] <popey> ok, got gallery to pass
[11:45] <popey> dpm: could you please push http://popey.com/~alan/com.ubuntu.gallery_<IP_ADDRESS>4_armhf.click to the store?
[11:52] <dpm> popey, done: https://myapps.developer.ubuntu.com/dev/click-apps/507/changerequest/
[11:55] <popey> thanks dpm
[11:58] <tvoss> sil2100, seb128 is there any way to get debug symbols for packages from silos?
[11:58] <popey> sil2100: had another occasion of the screen blanking, this time during camera AP tests
[12:01] <popey> sil2100: http://paste.ubuntu.com/7705522/
[12:02] <popey> sil2100: does this camera update also _require_ qtsensors?
[12:03] <tvoss> popey, do you know if there is an easy way to get debug symbols for silo packages?
[12:03] <popey> i do not
[12:03] <popey> sorry.
[12:06] <cjwatson> They should end up on ddebs.ubuntu.com I think
[12:19] <davmor2> brendand, sil2100: of the new failures how many are using the new header and have popups?  With the back button being in the header if you have a popup for any reason you can't interact with the header because of the popup
[12:19] <davmor2> might work under ap but doesn't on the actual device with fingers :)
[12:21] <brendand> davmor2, no that's a problem with autopilot too
[12:21] <brendand> davmor2, it will click on the popup instead
[12:22] <brendand> davmor2, i don't know of any test failures due to that though
[12:23] <davmor2> brendand: no idea I just hit it myself so thought I wonder if tests are failing because of that
[12:28] <pmcgowan> robru, did we get a qtdeclarative silo? I can get folks testing unless they have already
[12:42] <pmcgowan> sil2100, my silo 3 failed trying to get the source package
[12:55] <Guest98529> robru, hey could you take a look on the changes on debian package for this MR: https://code.launchpad.net/~renatofilho/address-book-app/vcard-import/+merge/224319
[12:59] <brendand> sil2100, psivaa - it looks like the uitoolkit and mediaplayer failures are closely related
[12:59] <brendand> sil2100, psivaa - they both hang on launching the application. it looks like it's timing out, then the test is continuing
[13:00] <brendand> sil2100, psivaa - for mediaplayer this causes failures, but for uitoolkit it just means a really long test run
[13:00] <pmcgowan> cjwatson, any idea why silo 3 keeps failing to get the source tarball?
[13:00] <brendand> sil2100, psivaa - it's possible this could be a global issue. perhaps mir/unity8 has changed something and AP has not caught up
[13:02] <cjwatson> pmcgowan: I'm afraid I'm not familiar with the details of how things work for merge-mode branches
[13:03] <cjwatson> pmcgowan: But something seems to be setting a bogus version number
[13:03] <cjwatson> bzr: ERROR: Unable to find the needed upstream tarball for package qtdeclarative-opensource-src, version 5.3.0+14.10.20140626.
[13:03] <cjwatson> Which is not what https://code.launchpad.net/~mzanetti/kubuntu-packaging/qtdeclarative-opensource-src/+merge/224517 says
[13:05] <mhr3> sil2100, can you re-publish 014?
[13:05] <mhr3> sil2100, looks like the mediascanner scope wasn't in the ppa cause there's just a rebuild mp, so it didn't consider it changing anything
[13:06] <pmcgowan> cjwatson, thanks looking
[13:07] <cjwatson> The job is modifying the changelog under "Prepare changelog content"
[13:08] <pmcgowan> mzanetti, <cjwatson> The job is modifying the changelog under "Prepare changelog content"
[13:09] <mzanetti> mhm... and that seems to break the way it tries to fetch the upstream sources
[13:09] <mzanetti> in the working build it says "Using apt to look for the upstream tarball."
[13:09] <cjwatson> pmcgowan,mzanetti: It's possible that if/when this has been uploaded to silos before, it's simply been dput to the silo as a source package, rather than relying on jenkins to do the merge/build
[13:09] <cjwatson> pmcgowan,mzanetti: The safe bet would be to do the same again
[13:10] <cjwatson> pmcgowan,mzanetti: That said, I think adding "X-Auto-Uploader: no-rewrite-version" to the first paragraph of debian/control would also fix it
[13:10] <mzanetti> interesting
[13:11] <cjwatson> You'd need somebody in ~ci-train-ppa-service to do the upload for you if you went the first route
[13:11] <mzanetti> well, I'd probably vote for just dputting at this point, and let the maintainers of the package to other changes when they're back
[13:11] <psivaa> brendand: yea, as suspected. probably the changelist for image 95 could point anything?
[13:11] <cjwatson> mzanetti: That seems reasonable, if you can find somebody to do the upload for you (e.g. if Mirv is around)
[13:11] <brendand> psivaa, 96
[13:12] <brendand> psivaa, i'm just about to pin down the root cause
[13:12] <cjwatson> mzanetti: https://launchpad.net/~ci-train-ppa-service/+members
[13:12] <psivaa> brendand: ack, great
[13:12] <pmcgowan> cjwatson, he is out, we need sil2100 or robru I think
[13:12] <mzanetti> cjwatson: that's the whole problem, Mirv isn't around :)
[13:12] <mzanetti> but I'll find someone
[13:12] <cjwatson> Right, so one of those other people
[13:13] <pmcgowan> mzanetti, rsalveti could do it for us
[13:13] <mzanetti> yep
[13:14] <mzanetti> rsalveti: could you dput this package to the silo 003 for us? https://code.launchpad.net/~mzanetti/kubuntu-packaging/qtdeclarative-opensource-src/+merge/224517
[13:14] <davmor2> sil2100: so 98 isn't looking to bad and it seem the only time the ringer doesn't work is post upgrade this is a bootstrap install and it's worked 4 times so far
[13:14] <rsalveti> morning
[13:14]  * rsalveti looks
[13:15] <rsalveti> mzanetti: sure
[13:15] <mzanetti> thanks
[13:16] <davmor2> sil2100: so I'm going to try a revert to 87 not a bootstrap and see what that does and then I update to 98 again and see if the ringer is broken then
[13:32] <rsalveti> mzanetti: package is building
[13:33] <rsalveti> sil2100: mind reconfiguring silo 3?
[13:33] <mzanetti> rsalveti: thanks!
[13:40] <barry_> trainguards: this is a test
[13:41] <barry_> trainguards: this is another test
[13:42] <barry_> trainguards: here comes another one
[13:43] <ogra_> poor trainguards
[13:56] <barry> robru: yay!  erc properly tamed
[14:00] <sil2100> mhr3: ok, republishing
[14:03] <sil2100> pmcgowan: what's up with the silo you mentioned? Is it still an issue?
[14:03] <pmcgowan> sil2100, needs to be reconfigured, we had to dput the source tarball
[14:03] <pmcgowan> then rebuild
[14:05] <sil2100> Ok, reconfiguring then
[14:05] <pmcgowan> sil2100, also wanted to bug you about qofono again
[14:05] <sil2100> pmcgowan: libqofono should be in the NEW queue soon
[14:05] <sil2100> I mean, I pushed it so I would suppose it to appear there soon (or even now)
[14:06] <pmcgowan> sil2100, any idea when it will land? I heard there was an alpha freeze
[14:06] <pmcgowan> ah ok
[14:06] <sil2100> pmcgowan: seb said he can do the NEWing of it
[14:06] <sil2100> (although I don't see him here right now)
[14:07] <Laney> sil2100: those patches forwarded?
[14:08] <Laney> seb's out for the afternoon
[14:08] <cjwatson> alpha freeze doesn't affect new packages
[14:08] <sil2100> Laney: not yet, it's a fresh thing but I'll forward it properly ASAP
[14:09] <Laney> there are two
[14:09] <sil2100> Ah, right, one of them is from Ken - don't know about that one
[14:09] <sil2100> Will have to check it up
[14:09]  * Laney nod
[14:09] <sil2100> I mean, check up if it's forwarded, not check what it's about ;)
[14:10] <Laney> I checked for pull requests on github and didn't see any
[14:10] <sil2100> pmcgowan: reconfigured
[14:11] <dbarth> sil2100: hi; silo 019 good to go
[14:11] <dbarth> robru: ^^ 019 is also SRU material to support the new Chrome API for extensions
[14:12] <pmcgowan> mzanetti, ^^
[14:13] <sil2100> barry: as you are the sheriff right now, can I forward all CITrain related things to you now ;) ?
[14:13] <mzanetti> pmcgowan: yep, saw it, thanks. will check it out
[14:13] <barry> sil2100: yep, although i have meetings coming up so i might be a bit less responsive until after lunch
[14:14] <sil2100> barry: ok, sure thing ;) I'll also be watching for citrain requests, but I'll try doing other things in the meantime
[14:16] <barry> sil2100: sounds good.  you have the same meetings coming up :)
[14:17] <sil2100> Ah! ;p
[14:17] <sil2100> Right ;)
[14:17] <barry> sil2100: between the two of us, we can ignore enough of the meetings to keep the train running :)
[14:18] <kgunn> fginther: hey, are you swamped? we could really use a hand on mir-devel ci...loads of timeouts
[14:19] <fginther> kgunn, can you shoot me an example?
[14:19] <kgunn> fginther: https://jenkins.qa.ubuntu.com/job/mir-team-mir-development-branch-utopic-amd64-autolanding/183/console
[14:19] <kgunn> and another
[14:19] <kgunn> https://jenkins.qa.ubuntu.com/job/mir-team-mir-development-branch-utopic-amd64-ci/520/console
[14:21] <sil2100> kgunn: hi! Just so you know: the last Mir landing caused some regressions in different components like gallery-app and ubuntu-keyboard ;)
[14:21] <sil2100> kgunn: the guys worked-around them somehow, but just wanted to make sure you're aware
[14:21] <kgunn> sil2100: i am well aware...bugs are being updated
[14:21] <kgunn> yep
[14:21] <sil2100> Not sure if they poked you about those
[14:21] <kgunn> alf is on it full blast
[14:21] <sil2100> Oh, excellent!
[14:26] <pmcgowan> mzanetti, shall I hit the build button? or did you?
[14:26] <mzanetti> pmcgowan: I don't think we want to use that button
[14:26] <pmcgowan> oh
[14:26] <mzanetti> pmcgowan: I would think that introduces the issue from before again?
[14:26] <pmcgowan> dunno
[14:26] <pmcgowan> sil2100, ?
[14:27] <mzanetti> the package that rsalveti uploaded is still building on armhf
[14:27] <sil2100> Ok, so you dputted directly to the PPA right?
[14:27] <pmcgowan> I see
[14:28] <sil2100> If it's building, you can press the build button with the 'watch only' flag
[14:28] <sil2100> It will then track the building
[14:28] <kgunn> fginther: just sharing one idea, could we turn on ccache on our devel-branch? realize there may be reluctance to do that on trunk...just brainstorming
[14:29] <mzanetti> ah cool
[14:32] <fginther> kgunn, it looks like the bzr timeout was transient. I see more recent builds are passing now. But I'll see if we can find any logs that might indicate some network issues
[14:32] <fginther> kgunn, on the ccache thing...
[14:41] <AlbertA> barry: landing-020 is ready to go...
[14:42] <barry> AlbertA: publishin
[14:42] <barry> *publishin' :)
[14:49] <ogra_> publisheded ?
[14:49] <barry> public lashing?
[14:49] <kgunn> fginther: ...on the ccache thing ?
[14:50] <fginther> kgunn, sorry, meetings...
[14:50] <kgunn> np, me too
[14:50] <kgunn> take your time
[14:56] <robru> pmcgowan, yeah you're in silo 3
[14:57] <pmcgowan> robru, thanks its building again
[15:01] <balloons> fginther, can you have a look at why the test result is a blank xml file here: https://code.launchpad.net/~nskaggs/reminders-app/fix-evernote-sdk-python3/+merge/223493
[15:06] <fginther> balloons, check out the console log from the jenkins job: "ImportError: No module named 'evernote'"
[15:06] <balloons> fginther, d'oh, ty
[15:08] <josepht> Ubuntu CI Engineering Team | Vanguard: Ursinha | CI Train Status: #87 promoted | CI Train Sheriff: trainguards, barry | Known issues: The spreadsheet is extremely slow, http://people.canonical.com/~rbpark/citrain/ knows the statuses before the spreadsheet does.
[15:08] <Ursinha> josepht: I always do that, lol
[15:09] <Ursinha> josepht: I think you missed /topic :)
[15:09] <josepht> Ursinha: yep, sorry :)
[15:11] <davmor2> sil2100: okay I'm definitely of the opinion that this is a race condition.  I had to do a fresh install of 98 for testing the ringer worked fine there I downgraded to 87 and the ringer worked fine there. I then upgraded to 98 again and the ringer still works fine but some where along the lines it breaks
[15:11] <sil2100> Damn
[15:12] <sil2100> davmor2: hm, is this only mako-specific?
[15:15] <davmor2> sil2100: well it's the only device that rings right ;)
[15:15] <sil2100> davmor2: since I wonder if it's also a race condition on 87
[15:16] <sil2100> davmor2: i.e. if you downgrade again and experiment, will it finally happen as well?
[15:16] <davmor2> sil2100: it might be
[15:16] <sil2100> davmor2: I wonder if we should block on it then?
[15:16] <sil2100> I know it's serious and requires pushing people, but if it was in some more promoted images, then it seems it isn't such a big deal
[15:17] <sil2100> (for users)
[15:18] <popey> dpm: could you please push http://popey.com/~alan/com.ubuntu.camera_<IP_ADDRESS>8_armhf.click to the store
[15:18] <davmor2> sil2100: did you see the reply from the guy who missed to calls in 87 he was pretty miffed :)  I'd say a critical feature of the phone is that it rings correctly :)
[15:18] <davmor2> sil2100: let me carry on experimenting and see what happens
[15:18] <sil2100> davmor2: yeah, but it was just one e-mail - it also depends on how long we have this regression
[15:18] <sil2100> i.e. if it was there like 2-3 promotions before
[15:19] <sil2100> Since if this problem was around for a month, then I guess it's not noticible enough, or we would have people shouting at us all the time
[15:20] <dpm> popey, https://myapps.developer.ubuntu.com/dev/click-apps/506/changerequest/
[15:21] <brendand> sil2100, i can't make the landing meeting. i don't think elopio is here today either
[15:21] <charles> nik90, ogra_: reporting back on a couple of datetime requests that you two made
[15:22] <brendand> sil2100, there is this autopilot bug: https://bugs.launchpad.net/autopilot/+bug/1334676
[15:22] <sil2100> brendand: no problem - any particular updates on the AP front?
[15:22] <charles> nik90, there's a MR now that will support per-alarm sound files in indicator-datetime
[15:22] <elopio> sil2100: brendand: I am here.
[15:22] <brendand> sil2100, that is the main thing we are firefighting now
[15:22] <charles> nik90, I hope to get that along with the DBus stuff siloed tonight
[15:22] <davmor2> sil2100: true
[15:22] <brendand> elopio, don't be marked away then :)
[15:22] <charles> nik90, the DBus stuff isn't finished yet, so I can't promise that part for tonight
[15:23] <popey> thanks dpm
[15:23] <charles> ogra_: you requested that indicator-datetime stop playing the sound as soon as the snap decision was canceled
[15:23] <elopio> I'm hiding from reality.
[15:23] <ogra_> charles, yeah
[15:23] <nik90> charles: do you have a link to the MR?
[15:23] <charles> ogra_: indicator-datetime /is/ calling ca_context_cancel() and it works correctly on desktop, but not on the phone
[15:23] <nik90> charles: also does this mean indicator-datetime will play the alarm sound set by the clock app?
[15:24] <ogra_> charles, aha, well, probably a lower level bug in unity then
[15:24] <brendand> sil2100, the autopilot devs will look at it tonight and hopefully we'll have a better picture by tomorrow
[15:24] <charles> nik90, yes. I tested this out by setting alarm.sound = '/usr/share/sounds/ubuntu/ringtones/Koto chords.ogg' in AddAlarmPage.qml, just to test
[15:25] <nik90> charles: sweet. thnx
[15:25] <charles> ogra_: we'll be moving away from canberra when the media API is ready, but that won't happen until after RTM
[15:25] <ogra_> hmm
[15:25] <charles> nik90, one moment and I'll get that MR URL for you
[15:25] <sil2100> brendand: oh, so this is the cause of the delays in AP tests in UITK?
[15:25] <ogra_> so we need some workaround i guess
[15:25] <sil2100> Oh, he's gone
[15:25] <ogra_> sil2100, yes it is
[15:26] <ogra_> (i looked into it as well)
[15:26] <nik90> ogra_, charles: is canberra the default alarm sound?
[15:26] <charles> nik90, https://code.launchpad.net/~charlesk/indicator-datetime/lp-1318997-customizable-alarm-sounds
[15:26] <ogra_> nik90, canberra is the gnome sound framework for system sounds
[15:26] <nik90> ah
[15:26] <charles> nik90, ^ this also sets up the GSettings for user-defined duration / volume / sound file, even though it's not available to clock-app via dbus yet
[15:27] <ogra_> sil2100, so gallery and camera finally landed ... any objection to building an image now ?
[15:27] <nik90> charles: ok
[15:27] <sil2100> ogra_: no, please build
[15:27] <ogra_> ok
[15:27] <sil2100> I guess it will be nice to have an image with those
[15:27] <sil2100> We also landed some things inbetween so good
[15:28] <ogra_> yeah, saw that
[15:28] <ogra_> triggered
[15:29] <nik90> charles: ooh I also got a reply from the designers about the alarm sound. They still want the slider instead of presets.
[15:29] <nik90> charles: The reasoning was that the "Normal Volume" is subjective to different people
[15:35] <imgbot> [15:49] <popey> ~/71
[15:49] <ogra_> the mythical 71 ...
[15:52] <balloons> fginther, ok so I tweaked https://code.launchpad.net/~nskaggs/reminders-app/fix-evernote-sdk-python3/+merge/223493 a bit.. I realized I wasn't including or installing the modules properly. Now we have the pep8 errors again. I noticed the parms are slightly different on your run. Are they correct?
[15:55] <kgunn> Ursinha: hey there, i understand you've volunteered to help the crazy mir guys out on ci issues...
[15:55] <kgunn> i understand you might need to ramp a little with fginther's help
[15:55] <popey> ./me tickles ogra_ with https://code.launchpad.net/~popey/ubuntu-seeds/add-keychain/+merge/224667
[15:55] <popey> god dammit
[15:55] <kgunn> ..but just so you know, we've got missed autolandings atm
[15:55] <kgunn> "Started 7 hr 6 min ago"... "Waiting for next available executor on mako" http://s-jenkins.ubuntu-ci:8080/job/mir-mediumtests-runner-mako/
[15:56] <fginther> kgunn, Ursinha, the makos are swamped with test requests, looking to see why
[15:59] <fginther> kgunn, good grief the sdk tests take over 2 hours now
[16:05] <Ursinha> kgunn: yeah :) I have to finish some tasks I'm currently on though, hope it's okay to ping you guys then?
[16:07] <fginther> kgunn, are you doing some manual merges?
[16:09] <alan_g> fginther: yes
[16:11] <fginther> kgunn, alan_g, to help with the very short term, I've bumped the priority of mir's mako job. That will help with the current backlog situation, but it's not a good long term solution
[16:12] <alan_g> fginther: to help with the backlog I'm manually merging (and testing) approved branches that already passed in CI
[16:15] <robru> sil2100, did you say in the foundations meeting that you were working on the IRC bot?
[16:16] <sil2100> robru: yeah, tweaking some things in it and wanting to fix some of the CSV-parser hell that's going on there
[16:16] <fginther> alan_g, I can help by killing the jobs queued up for those branches
[16:16] <fginther> once you have them merged
[16:16] <robru> sil2100, did you see the email where we were talking about moving that bot into this channel?
[16:16] <alan_g> fginther: thanks. Do you need a list or do you have it?
[16:17] <fginther> alan_g, I see https://code.launchpad.net/~alan-griffiths/mir/fix-1334287/+merge/224457 in progress
[16:17] <fginther> which is merged
[16:17] <alan_g> fginther: ack
[16:19] <plars> cjwatson: do you have time today to talk through the image build stuff with me? or if not, perhaps tomorrow?
[16:19] <fginther> alan_g, I just killed the queued job for this merged mp: https://code.launchpad.net/~andreas-pokorny/mir/move-input-channel-factory/+merge/224323
[16:20] <cjwatson> plars: I have a little while.  What do you need?
[16:20] <alan_g> fginther: these are the ones I've merged: lp:~andreas-pokorny/mir/input-sender lp:~alan-griffiths/mir/fix-1334287 lp:~andreas-pokorny/mir/move-input-channel-factory lp:~kdub/mir/hwc-device-test-cleanup
[16:20] <plars> cjwatson: you had mentioned that I should grab you on irc so you could walk me through the process. Or if you have written instructions I'm happy to try those out first
[16:21] <plars> cjwatson: this relates to the ubuntu-cdimage stuff you were working on
[16:21] <cjwatson> plars: Do you have cdimage set up on a scratch host?
[16:21] <plars> cjwatson: not at this moment, but I can do that
[16:22] <plars> cjwatson: does it need to be trusty, or does precise work?
[16:22] <fginther> alan_g, thanks. got the ones in the queue
[16:22] <cjwatson> plars: You'll also need a devirtualised PPA somewhere that you plan to use in combination with the primary archive to build the image; and I'll need to know the Launchpad user (a bot?) that you plan to use
[16:22] <cjwatson> plars: Right now it must be utopic
[16:22] <alan_g> fginther: thanks for  tidying up after me
[16:22] <cjwatson> plars: (At least if you plan to use the extra-PPA feature, which is kind of the point for you AIUI)
[16:22] <cjwatson> plars: precise isn't going to be able to build touch images :)
[16:23] <cjwatson> plars: Oh, wait, you mean the host you're running cdimage on, not the PPA?
[16:23] <plars> cjwatson: yes
[16:23] <cjwatson> plars: Either precise or trusty should work for that
[16:23] <plars> whew, ok. I was getting really confused for a moment there :)
[16:23] <cjwatson> So was I apparently ...
[16:24] <mhr3> sil2100 / robru, what happened to row #33?
[16:24] <plars> cjwatson: I think we have a ci bot user now, but I don't have any lp credentials for it. Let me check on that. Once I have that, you could set up the devirtualized ppa for it? or do I need to request that through IS?
[16:24] <mhr3> sil2100, robru, it was about to be published in 014, but disappeared in the void
[16:24] <cjwatson> plars: I can't set up devirtualised PPAs, you'll have to do that
[16:24] <cjwatson> (with IS)
[16:25] <cjwatson> plars: I assumed you'd be using an existing silo or something though
[16:25] <cjwatson> plars: The PPA doesn't have to belong to your bot user
[16:25] <cjwatson> plars: I'll need to add your bot to ~launchpad-livefs-builders though
[16:26] <robru> mhr3, silo 14 was published by lukasz and merged by me. not sure where the spreadsheet line went
[16:26] <plars> cjwatson: I don't think we're planning to use the existing citrain silos if that's what you mean, and there are actually bugs that prevent the entire process from working on utopic at the moment, so I'm not sure how far I can get without just kind of doing it by hand first
[16:27] <mhr3> robru, ah, so just broken spreadsheet... ok
[16:27] <robru> mhr3,
[16:27] <robru> mhr3, yep
[16:29] <plars> cjwatson: the devirtualized ppa is for building the image though right? there's not already a pool set aside for that purpose that anyone in  ~launchpad-livefs-builders can use?
[16:29] <cjwatson> plars: The devirtualised PPA is the *source* for the image
[16:30] <cjwatson> plars: You can build an image either from the primary archive alone, or from the primary archive plus PPAs; but packages come from the PPAs and go into the image, the resulting image does not go into the PPA
[16:30] <cjwatson> plars: So you can use any existing PPA in Launchpad for the purpose of this experiment, as long as it's devirtualised
[16:30] <plars> cjwatson: ah, devirt so that it can build an armhf package that will be going into the image I guess, right?
[16:30] <cjwatson> plars: Later of course you'll want that to be a PPA that's the output of the CI engine for some ticket
[16:31] <cjwatson> plars: Devirt because the livefs has to build on devirtualised hardware right now so this is a security requirement
[16:31] <plars> ok
[16:31] <cjwatson> plars: We'll be able to lift this restriction later once scalingstack is in place
[16:31] <cjwatson> plars: (I did try building a livefs on our existing virt builders, but live-build and the hardy kernel don't get along)
[16:48] <sil2100> robru: oh, I might have missed that
[16:49] <robru> sil2100, it was the one titled 'Formalizing CI Train Sheriff'
[16:49] <sil2100> robru: you want the bot in this channel then? I could modify it to only react on commands that are sent with his name in it
[16:49] <sil2100> Aren't you afraid it'll spam a bit too much?
[16:50] <robru> sil2100, well, read the discussion ;-) barry and stgraber both requested that they not have to care about Yet Another IRC Channel.
[16:50] <sil2100> Ok, I'll read it up once I have a free moment then ;)
[16:50] <robru> sil2100, take a look at queuebot in #ubuntu-release, it has a lot to say but uses channel notices instead of messages, so it's less intrusive. that would be nice
[16:51] <sil2100> Right now it's a bit hard to find a free moment though!
[16:51] <robru> sil2100, not urgent, but it's a thought
[16:51] <sil2100> I guess it could be doable, as the idea for it to be in a different channel was Didier's idea
[16:53] <robru> sil2100, yeah I never understood the rationale behind making a separate channel, and then making the bot consume the whole channel in a way that makes it impossible to talk there
[16:55] <sil2100> I can understand part of those, as the bot is really a bit flaky because of the really crappy CSV parser and can sometimes be a bother, but it's nothing that should be a definite blocker
[16:56] <sil2100> Especially that the CI train choo choo channel is not documented anywhere
[16:57]  * sil2100 adds it to the FAQ in the meantime
[17:03]  * sil2100 wonders if the image is still building
[17:05] <imgbot> [17:05] <sil2100> ...
[17:05] <imgbot> [17:05] <sil2100> :D
[17:05] <sil2100> imgbot reads my mind
[17:05] <thostr_> could anybody reconfigure silo 7 (I changed the components)
[17:06] <robru> barry, ^
[17:14] <ogra_> sil2100, oh, didnt i tell you oabout the new lukasz-brain plugin i wrote ?
[17:24] <sil2100> ;)
[17:24] <barry> robru: reconfigured.  it's weird though - sometimes i have to hit the build button twice
[17:25] <robru> barry, yes you do! the first time it does the SSO handshake and then returns you to the same page you started on.
[17:25] <barry> robru: okaaaay
[17:25] <robru> barry, I know, it's so convenient that it just logs you in automatically, right? ;-)
[17:26] <barry> robru: yeah, even when i'm already logged in
[17:27] <robru> barry, yeah, you're logged into SSO, but you're not logged in to jenkins. so the first time you click the build button, jenkins is like "who is this not logged in person! I'll redirect him to SSO!" and then SSO is all like "Hey man, that's Barry Warsaw! I'll be super-helpful and redirect him right back to the page he started on without giving any sort of visual indication of what just happened. I'm sure that's exactly what he wants!"
[17:28] <barry> robru: not that i'm complaining because, bananas!
[17:28] <barry> monkey see (button), monkey push
[17:28] <robru> barry, and the jenkins login times out after like, 30 minutes or something. so basically yeah, the first time you click the build button, you're really clicking the "login" button. then you can click the build button for real after that.
[17:29] <barry> robru: ah, it's the 30 minute logout i wasn't aware of
[17:29] <robru> barry, next time you click a link through to a jenkins job, check the top right to see if you're logged in or not. if you click "login" first then the build button will work the first time
[17:29] <robru> barry, yeah
[17:29] <robru> barry, I don't know the exact timeout period, but it seems like I have to log in again every time I go to use it
[17:31] <barry> robru: in celebration of my last official sheriff day, i finally got erc to highly the trainguards ping :)
[17:31] <robru> barry, perfect ;-)
[17:31] <sil2100> barry: last official sheriff day? You won't be sheriffing anymore? ;)
[17:31] <robru> barry, ok, so you can be sheriff in perpetuity right? ;-)
[17:33] <barry> robru: well, at least i'll be annoyed by it until i remember/bother to turn it off :)
[17:33] <robru> barry, hehe
[17:33] <barry> sil2100: i think so, yes.  stgraber and i were only originally supposed to serve in june and 3 business days from today (rotation period) is july
[17:34] <sil2100> ACK :)
[17:34] <sil2100> Right!
[18:13] <barry> i guess i should start silos 7 and 13
[18:16] <ogra_> yippie, gallery passes
[18:27] <AlbertA> barry: robru: do I need to do anything for landing-020? it says publication needs action...
[18:32] <barry> AlbertA: i don't remember what to do about that.  if robru can remind me, i can try to do whatever it is that has to be done
[18:37] <robru> barry, you have to look at the diffs and approve them with your Core Dev hat on
[18:37] <robru> barry, same in 19 actually
[18:38] <barry> robru: ack
[18:43] <barry> robru: i guess i can trust the merge proposal to show me the diff, right?  and really i only need to review the changes in the debian/ directory.  the only question i have for silo 19 (dbarth's) is why the d/copyright file got trimmed
[18:47] <robru> barry, dashboard has a link directly to the packaging diffs: http://people.canonical.com/~rbpark/citrain/
[18:48] <robru> barry, and in the case of silo 19, debian/copyright got trimmed because all those files vanished. NPAPI plugins went away
[18:52] <robru> barry, go ahead and publish silo 5 while you're at it ;-)
[18:58] <robru> barry, hrmm did you get my messages? i sent three in the last 15 minutes. not sure if net split cut you off
[18:58] <barry> robru: the last one i got was:
 barry, same in 19 actually
[18:59] <robru> 11:47 <robru> barry, dashboard has a link directly to the packaging diffs: http://people.canonical.com/~rbpark/citrain/
[18:59] <robru> 11:48 <robru> barry, and in the case of silo 19, debian/copyright got trimmed because all those files vanished. NPAPI plugins went away
[18:59] <robru> 11:52 <robru> barry, go ahead and publish silo 5 while you're at it ;-)
[19:00] <barry> robru: ah, cool.  and done both
[19:01] <robru> barry, thanks
[19:27] <elopio> ping robru: can you please triage this one and add it to the roadmap?
[19:27] <elopio> https://bugs.launchpad.net/mir/+bug/1334767
[19:27] <robru> elopio, what? why me? what roadmap?
[19:28] <elopio> robru: to the roadmap of the CI team, so it's scheduled and somebody works on it hopefully soon.
[19:29] <robru> elopio, I have no idea what you're talking about. it's not CI's job to write documentation for mir. I'll assign it to kgunn
[19:30] <elopio> robru: the docs are up-to-date on the branch
[19:30] <robru> elopio, sorry, just read the bug.
[19:30] <elopio> what we need is to find the job that pushes the docs to the website, that seems to have been lost since trusty.
[19:30] <robru> elopio, i'm asking some CI people
[19:31] <elopio> robru: thanks.
[20:50] <jhodapp> robru: can I get a silo for line 26 in the spreadsheet?
[20:50] <robru> barry, ^
[20:52] <barry> jhodapp, robru i just tried to assign it but camera-app is already in silo 4.  should i override?
[20:53] <robru> barry, yeah, silo 4 is one of those "big ones" you can pretty much ignore
[20:53] <barry> done.  jhodapp, happy landings!
[20:55] <jhodapp> barry: thanks!
[21:27] <fginther> elopio, ping
[21:27] <elopio> fginther: pong.
[21:27] <fginther> elopio, re: https://bugs.launchpad.net/ubuntu-ci-services-itself/+bug/1334371 . How are the tests executed?
[21:29] <elopio> fginther: autopilot3 run ubuntu_experience_tests
[21:30] <fginther> elopio, thanks
[21:30] <elopio> fginther: thanks to you for working on it.
[21:30] <fginther> elopio, does this need to go into a PPA?
[21:31] <elopio> fginther: whatever you think best. If you prefer it in a PPA, lets do that. Or if you prefer it to be on the archive, I can start pinging people for that too.
[21:33] <fginther> elopio, I think this needs to be in the archive to facilitate the daily smoke testing (I'm assuming that's what is ultimately desired). We don't use PPAs for that.
[21:34] <elopio> fginther: yes, that's what we want.
[21:34] <fginther> elopio, if that is the utlimate solution, we can still do a PPA in the short term to get this bootstrapped
[21:35] <elopio> fginther: that would be nice. And do you know who can help me to put it in the archive? to start figuring that out too
[21:39] <rsalveti> ogra_: robru: mind if I build a new image?
[21:40] <robru> rsalveti, fine by me...
[21:40] <rsalveti> robru: great
[21:41] <popey> #100!
[21:41] <rsalveti> we landed a few big things, want to make sure we don't regress too much :-)
[21:41] <rsalveti> awesome
[21:41] <fginther> elopio, I'm embarrassed to say I don't know where to start.
[21:42] <fginther> balloons, are you around? Do you know anything about getting a pure test package into the archive? elopio has something that falls into this category
[21:44] <rsalveti> ok, just triggered a new image
[21:50] <imgbot> [21:50] <Wellark> hey guys!
[21:50] <Wellark> is silo4 landing any time soon?
[21:50] <Wellark> I have system-settings MP ready to land
[21:50] <Wellark> in silo7
[21:50] <Wellark> and I would not want to collide with silo4
[21:51] <robru> Saviq, t1mp ^
[21:54] <Wellark> oh, well. first come first served, right? :)
[21:55] <Wellark> silo 4 only has 13 MP's in it. it should not be a big deal to rebuild it, right....
[22:07] <balloons> fginther, a pure test package?
[22:08] <balloons> like something -autopilot? or something else?
[23:21] <cjwatson> plars: Any luck?


[02:34] <MutantTurkey> short_distance++
[02:34] <MutantTurkey> preferably neighbors
[02:58] <ChinnoDog> I'm with you MutantTurkey
[03:09] <MutantTurkey> lol
[03:49] <InHisName> Goot Evenin' all you wonderful people!
[12:43] <JonathanD> Good morning Pennsylvania.
[13:47]  * InHisName in behalf of Pennsylvania say Good Morning to you TOO !
[16:09] <bts3685|vps> guys. i am friggin' tired
[16:09]  * ssweeny too
[16:09] <ssweeny> let's have nap time
[16:10] <bts3685|vps> naptime++
[16:10] <bts3685|vps> @karma naptime
[16:10] <PennBot> bts3685|vps: Karma for "naptime" has been increased 1 time and decreased 0 times for a total karma of 1.
[16:12] <andrew> that's it?
[16:12] <andrew> @karma naps
[16:12] <PennBot> andrew: Karma for "naps" has been increased 27 times and decreased 0 times for a total karma of 27.
[16:24] <bts3685|vps> ahhh
[19:02] <InHisName> Everyone all rested up for the big day ?
[19:03] <InHisName> Only about 10 hours left, use it wisely!
[19:10] <waltman> until...?
[19:11] <waltman> National Backup Day?
[19:11] <InHisName> Tomorrow !
[19:11] <InHisName> Fool  !!
[19:11] <waltman> sorry, it's *World* Backup Day, and it's today
[19:12] <InHisName> over slept a trifle, heh   waltman ?
[19:12] <ChinnoDog> What does one do on world backup day? format c:?
[19:12] <waltman> I'll have you know I've aleady backed up all 3 boxes I'm responsible for today!
[19:13] <InHisName> I've celebrated already.......
[19:13] <InHisName>    I've backed-up                              from my driveway.
[19:13] <waltman> I think the idea's something like "Don't wait until tomorrow and be a fool, backup your computer today!"
[19:14] <ChinnoDog> CrashPlan++
[19:16] <jedijf> i need to backup
[19:23] <ChinnoDog> World Backup Day is for jedijf
[19:27] <JonathanD> yay
[19:27] <ChinnoDog> jedijf: You are especially at risk. What if you drive the breadvan into a creek and it floats away?
[19:29] <ChinnoDog> French bread pontoons will not be enough to keep the bread van afloat.
[19:29] <InHisName> Can jedijf still back up the van out of the creek ?
[19:32] <InHisName> Should we all RAID his truck of all the goodies ?
[19:33] <ChinnoDog> lol
[19:33] <ChinnoDog> those puns are terrible
[19:44] <waltman> Be careful -- if the police catch you, they'll arrest you and restore the goodies to his truck!
[19:48] <bts3685|vps> then you'll need intensive recovery sessions!
[19:48] <bts3685|vps> (wait, i thought we were still making data backup puns)
[19:48] <bts3685|vps> jedijf: remember telling us about one of the breadvan drivers that got the vehicle stuck under a low-hanging carport?
[19:48] <bts3685|vps> that was awesome. </chris_farley></SNL>
[19:49] <ChinnoDog> The differential on the truck after that will not be very good
[19:50] <ChinnoDog> "low-hanging carport"?
[19:50] <ChinnoDog> A concrete structure?
[19:51] <bts3685|vps> yeah
[19:51] <bts3685|vps> like a square peg trying to go into a...
[19:52] <bts3685|vps> well, a smaller square hole.
[19:52] <ChinnoDog> lol
[19:52] <ChinnoDog> How do you fix that? Deflate the tires and back out?
[19:52] <bts3685|vps> that's how they do it in the brainteasers
[19:52] <bts3685|vps> jedijf: how was it fix0rzed?
[19:53] <ChinnoDog> Cover the van in butter and slide it out!
[19:53] <bts3685|vps> teeheehee
[20:07] <InHisName> ButterMobile
[20:11] <ChinnoDog> gobble gobble
[20:14] <InHisName> time for MutantTurkey to speak-up
[20:14] <MutantTurkey> gobble gobble
[20:16] <InHisName> all this gobbling has got me more interested in some Roast Turkey with dressing.  Yum!
[21:23] <jedijf> ok, backup is the office server
[21:23] <jedijf> 2 we don't get stuck ..we have hit 3 of them
[21:24] <jedijf> dead on
[21:24] <jedijf> phila airport hilton, holiday inn runnemeade,nj and holiday inn de
[21:35] <bts3685|vps> hahahahha
[21:35] <bts3685|vps> niceeee


[03:43] <ball> Mornin'
[03:44] <daftykins> o/
[04:00] <daftykins> https://en.wikipedia.org/wiki/This_Perfect_Day - just finished, what a great book
[04:19] <ball> Sounds interesting.
[04:44]  * ball goes back to reading about electric locomotives.
[04:44] <daftykins> choo choo!
[04:44] <daftykins> time for bed, g'night!
[04:46] <ball> Goodnight daftykins!
[05:01] <zxmpi> are electric trains choo choos?
[16:02] <daftykins> zxmpi: i was imagining an EV like world where they are ruled to have to make artificial noise ;)
[16:04] <penguin42> clippety-clop...
[16:06] <daftykins> xD
[16:41] <zxmpi> the gap between rails adds a nice *clack* *clack*
[22:25] <daftykins> diddledan: yay i put the site live \o/
[22:25] <daftykins> backed up the old and just renamed the doc roots for now


[09:32] <__marco> hi, does exist a "demo" project where I can test the launchpad's features?
[09:32] <__marco> I want to release a project but first I'd like to test in a sendbox
[09:46] <ersi> Is there any kind of disruptions still going on? I'm getting an aweful lot of Timeout errors on the Translation part of Launchpad.net still. I havn't seen any status messages published since 3 weeks ago on https://identi.ca/launchpadstatus
[10:08] <wgrant> __marco: https://staging.launchpad.net/ is a copy of production that's reset every week.
[10:09] <wgrant> ersi: Nothing's particularly worse than normal, but there is a long-standing translations timeout which should get better with some new database servers that we'll be implementing over the next few weeks.
[10:09] <wgrant> ersi: What is the OOPS ID given on the timeout page?
[10:11] <ersi> wgrant: To name a few: OOPS-82496f04ed4c542bf391f4cf9a8df675 OOPS-4185b62d8cee3ab8c7f90694d356f721 OOPS-3a8bf5298c30174a45656b8e066bb6cc OOPS-9db6dd9594fa4a8d18b2b6b6484076c8
[10:11] <ersi> Holy moly. Didn't expect that. Well then :-)
[10:14] <ersi> I mean, I know the translation part is a bit more shaky or that Timeout Errors can happen anywhere. It's just that the last week, it's been a hit or a miss everytime you'd click "Save and continue". Sometimes you have to refresh/retry at least five times until a translation lp page loads - so I'm just curious, since there's nothing on identica or the blog :)
[10:23] <wgrant> Right, those retry issues are mostly due to the aging database servers, and we have shiny new replacement hardware for those that isn't quite commissioned yet. There are also some other issues which we're working on. See my last comment in https://bugs.launchpad.net/launchpad/+bug/736005 for gory details.
[10:23] <wgrant> Those URLs work for me, so I suspect it was just a really cold cache.
[10:24] <ersi> Yeah, they work after a few retries :-)
[10:26] <wgrant> SSDs and more RAM solve everything.
[10:26] <wgrant> Hopefully :)
[10:26] <ersi> Cool, thanks. I'll read up on that, since it's interesting IMO :-)
[10:26] <ersi> Hehe, yeah :D Shiny hardware be shiny!
[12:01] <__marco_> haw can I create a branch on the (qa)staging.launchpad.net?
[12:01] <__marco_> how*
[12:02] <__marco_> what are the differences between qastaging and qastaging?
[12:02] <wgrant> __marco_: Nothing :P
[12:03] <wgrant> But between qastaging and *staging*: mostly that qastaging's DB is refreshed manually
[12:03] <wgrant> staging's is refreshed each weekend, qastaging's rather more infrequently atm.
[12:04] <wgrant> As the name suggests, qastaging exists mostly for our devs to test code changes.
[12:04] <wgrant> For sandbox purposes, all you need to know is the different reset schedule.
[12:05] <wgrant> __marco_: As for creating branches, 'bzr push lp://staging/~whatever/youd/normally/do'
[12:48] <__marco_> wgrant: thanks
[15:39] <CodePulsar> Ubuntu Login user/pass is the same as LaunchPad user/pass ?
[15:40] <CodePulsar> I see that whenever I change Ubuntu Login password I cannot login into Launchpad with the old password
[15:40] <CodePulsar> I have to use the password for Ubuntu Login
[15:42] <cjwatson> They're the same account, yes.  Single sign on.


[16:01] <jamespage> arosales, I see you in the chair today - OK with that?
[16:01] <arosales> jamespage, yes sir
[16:02] <jamespage> arosales, good man!
[16:02] <smoser> o/
[16:02] <jamespage> \o
[16:02] <arosales> startmeeting ubuntu-server-team
[16:03] <arosales> #startmeeting ubuntu-server-team
[16:03] <meetingology> Meeting started Tue Nov 12 16:03:06 2013 UTC.  The chair is arosales. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:03] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[16:03] <arosales> #topic Review ACTION points from previous meeting
[16:03]  * arosales doesn't see any action items from the previous meeting
[16:03] <arosales> #topic Saucy Development
[16:03] <arosales> I guess we should update that to trusty dev
[16:04] <jamespage> done
[16:04] <arosales> #link https://wiki.ubuntu.com/TrustyTahr/ReleaseSchedule
[16:04] <arosales> Looks like next milestone is the Feature Definition Freeze
[16:04] <arosales> Alpha 1 on Dec 19th
[16:05] <arosales> #subtopic Release Bugs
[16:05] <jamespage> which means feature definition freeze is at the end of vUDS
[16:05] <arosales> #link http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-s-tracking-bug-tasks.html#server
[16:05] <arosales> jamespage, ah good point
[16:06] <arosales> be good to finalize those features in vUDS
[16:06] <arosales> so looking @ http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-s-tracking-bug-tasks.html#server
[16:06] <arosales> looks to have 27 bugs for ubuntu-server
[16:06] <jamespage> quite a few of those are SRU tasks for juju-core
[16:06] <jamespage> I got a bit carried away
[16:07] <arosales> jamespage, thanks or logging them
[16:07] <arosales> need to have those back into the lts
[16:07] <arosales> one critical bug
[16:07] <jamespage> arosales: I need to apply for a MRE for juju-core
[16:07] <arosales> http://launchpad.net/bugs/1229275
[16:07] <jamespage> yah
[16:07] <arosales> jamespage, +1 on MRE for juju-core, moving pretty fast am
[16:07] <jamespage> so all of the fixes are avaliable in the stable juju ppa
[16:07] <jamespage> but the distro package is now out-of-date
[16:07] <jamespage> for saucy
[16:08] <arosales> thus the SRUs
[16:08] <jamespage> yup
[16:08] <arosales> is 1229275 a fix in maas though?
[16:09] <jamespage> roaksoax, is the maas multi-env destroy fix already in proposed?
[16:09] <jamespage> that might be a dupe arosales
[16:09] <roaksoax> jamespage: yes
[16:09] <jamespage> roaksoax, ack
[16:09] <roaksoax> jamespage: in fact, is already released
[16:09] <jamespage> arosales: yes the maas tasks for that can be dropped
[16:09] <arosales> roaksoax, can you update 1229275
[16:10] <arosales> jamespage, ok if we hit the high unresolved bugs?
[16:10] <roaksoax> sure
[16:10] <arosales> roaksoax, thanks
[16:10] <jamespage> good with me
[16:10] <arosales> only one critical,
[16:10] <arosales> next are highs
[16:10] <arosales> http://launchpad.net/bugs/1208455
[16:11] <arosales> looks like stefan bader is assigned
[16:11] <arosales> in progress and confirmed . .  .
[16:11] <arosales> looks like rbasak assigned this one
[16:12] <arosales> but no objections by stefan
[16:12] <jamespage> I'm not entirely sure why that is high
[16:12] <jamespage> smb is not here to defend his position!
[16:12] <arosales> looks like not action needed atm though
[16:12] <jamespage> agreed
[16:12] <rbasak> I think somebody probably told me to assign it when I wanted an assignment at a previous meeting.
[16:12] <jamespage> its an odd edge case IMHO
[16:12] <jamespage> rbasak, I remember that
[16:13] <arosales> http://launchpad.net/bugs/1245251
[16:13] <rbasak> IMHO, we should either stop tracking it, or assign someone
[16:13] <hallyn_> that'll get fixed when we push 1.1.4 to trusty
[16:13] <rbasak> Then we can focus on the stuff we intend to fix.
[16:13] <arosales> hallyn_, is that for apparmor?
[16:13] <hallyn_> yes
[16:13] <arosales> hallyn_, thanks
[16:14] <arosales> http://launchpad.net/bugs/1199791
[16:14] <arosales> the next ones are for zul
[16:14] <zul> uh?
[16:14] <arosales> zul I think you are the assignee
[16:14] <zul> oh wait..yeah still pending its going to be changing in the trusty cycle
[16:14] <arosales> ok
[16:14] <arosales> zul and for http://launchpad.net/bugs/1223010
[16:15] <zul> (damn daylight daying hours)
[16:15] <zul> arosales:  i talked to upstream last week they are going to be moving to oauthlib
[16:15] <arosales> zul thnks
[16:15] <arosales> thanks
[16:15] <arosales> https://bugs.launchpad.net/maas/+bug/1228085
[16:15] <arosales> looks like gavin has a fix
[16:15] <arosales> but needs to be worked in saucy
[16:16] <arosales> roaksoax, any opinions?
[16:17] <arosales> jamespage, SRU needed here?
[16:17] <jamespage> the tasks are raised so most likely
[16:17] <arosales> jamespage, any actions needed for the SRUs?
[16:18] <arosales> http://launchpad.net/bugs/1236439
[16:18] <roaksoax> arosales: that was fixed too
[16:18] <jamespage> arosales: yes - still needed
[16:19] <arosales> roaksoax, ah even better. Could you update the bug if it is indeed fixed in saucy and trusty
[16:19] <jamespage> roaksoax, is it?
[16:19] <jamespage> I just checked in 2.2
[16:19] <roaksoax> jamespage: yeah I fixed it differently, IIRC. Gonna have a deeper look
[16:20] <jamespage> arosales: that neutron bug is reference upstream inthe havana release notes
[16:20] <jamespage> roaksoax, ack
[16:20] <arosales> roaksoax, thanks, could you update the bug post your research?
[16:20] <jamespage> I've pinged upstream to see if a helper is going to appear for upgraders
[16:20] <arosales> jamespage, ack on the neutron bug
[16:20] <roaksoax> arosales: yup
[16:20] <arosales> roaksoax, thanks
[16:20] <arosales> http://launchpad.net/bugs/1242363
[16:20] <arosales> puppet bug
[16:21] <arosales> packaging issue . .  .
[16:21] <arosales> rbasak, looks to confirmed ruby-hiera  fixes it
[16:21] <arosales> rbasak, next action needed to update puppet deps or add in ruby-hiera?
[16:21] <rbasak> It's on my list.
[16:22] <rbasak> I'm hoping to combine it with a merge when I get to it, and then SRU.
[16:22] <arosales> rbasak, would you like to assign yourself?
[16:22] <rbasak> Done
[16:22] <arosales> rbasak, thank you sir
[16:22] <arosales> thats the last high
[16:22] <arosales> have a few undecided that need triaged
[16:23] <arosales> I think most of them are around juju-core
[16:23]  * arosales thinks those are the SRUs jamespage was referring to
[16:23] <jamespage> yes
[16:23] <arosales> #subtopic Blueprints
[16:23] <arosales> jamespage, smoser looks like we also need a trusty topic BP
[16:24] <jamespage> arosales: we do - is that something you can setup?
[16:24] <arosales> jamespage, sure
[16:24] <arosales> #action arosales to set up topic bp for server
[16:24] <meetingology> ACTION: arosales to set up topic bp for server
[16:24] <jamespage> for now - https://blueprints.launchpad.net/ubuntu?searchtext=servercloud-1311
[16:24] <arosales> #link http://status.ubuntu.com/ubuntu-s/group/topic-s-servercloud-overview.html
[16:24] <jamespage> that's what we have on the list for next week
[16:24] <arosales> we should postpone the rest of these though
[16:25] <jamespage> arosales: I'd leave it until after next week
[16:25] <jamespage> we can carry stuff over and close old bp's out
[16:25] <jamespage> https://wiki.ubuntu.com/BlueprintSpec
[16:25] <arosales> jamespage, smoser do you want to step through these and mark postponed as necessary?
[16:25] <arosales> jamespage, ack
[16:25] <jamespage> ^^ blueprint spec for new blueprints
[16:26] <arosales> #action jamespage, smoser,  review all saucy BPs
[16:26] <meetingology> ACTION: jamespage, smoser,  review all saucy BPs
[16:26] <smoser> deal
[16:26] <arosales> where is gaughen
[16:26]  * arosales wanted to put in an action item there too
[16:26] <gaughen> I'm right here!
[16:27] <jamespage> I see gaughen
[16:27]  * jamespage waves
[16:27] <arosales> #action gaughen review saucy BPs
[16:27] <meetingology> ACTION: gaughen review saucy BPs
[16:27]  * gaughen waves back
[16:27] <arosales> ah autocomplete just failed me
[16:27] <arosales> action items set ;-)
[16:27] <arosales> #topic Server & Cloud Bugs (caribou)
[16:27] <gaughen> k
[16:28] <jamespage> mia
[16:28] <arosales> ok
[16:28] <arosales> #topic Weekly Updates & Questions for the QA Team (psivaa)
[16:29] <psivaa> nothing much from us apart from the fact that our services are down at the moment
[16:29] <psivaa> due to 1SS hardware move
[16:29] <jamespage> psivaa, any eta on returning service?
[16:29]  * jamespage hates to ask
[16:30] <psivaa> jamespage: the core services should start late this evening and the rest will be tomorrow
[16:30] <jamespage> ack
[16:30] <arosales> psivaa, ok thanks for the update
[16:30] <psivaa> yw :)
[16:30] <arosales> any other questions for psivaa
[16:30] <arosales> #topic Weekly Updates & Questions for the Kernel Team (smb)
[16:30] <jamespage> mia as well
[16:31] <arosales> jamespage, thanks for letting me know :-)
[16:31] <arosales> #topic Weekly Updates & Questions regarding Ubuntu ARM Server (rbasak)
[16:31] <jamespage> we had one thing we where working on with kernel team
[16:31] <jamespage> openvswitch-dkms drop for 14.04
[16:31] <rbasak> Nothing new to report from me. Any questions?
[16:31] <jamespage> can't quite make it but all of the mainline features we need are in 3.13; only need dkms for experimental stuff
[16:32] <arosales> jamespage, need a vUDS session on that or all coordination happening in a bug?
[16:32] <jamespage> no
[16:33]  * arosales takes it as no vuds sessions needed
[16:33] <jamespage> it will be covered in other sesssions
[16:33] <arosales> jamespage, ack
[16:33] <arosales> #topic Ubuntu Server Team Events
[16:33] <arosales> so lots of stuff wrapping up
[16:33] <arosales> ODS
[16:33] <arosales> RubyConf last  week
[16:33] <arosales> AWS re:Invent this week
[16:34] <arosales> any other events?
[16:34] <arosales> #topic Open Discussion
[16:35] <arosales> all folks in-line with https://wiki.ubuntu.com/BlueprintSpec ?
[16:36] <arosales> jamespage one point of feedback I got, perhaps around "user acceptance"
[16:36] <arosales> is how do we know this particular feature is a "success"
[16:36] <arosales> ie what is the metric to measure the bp was actually successfully
[16:37] <arosales> jamespage, thoughts?
[16:37] <jamespage> its quite subjective; but it could be anything from some dep-8 tests to a more detail decription on how to use a new feature in the docs
[16:37] <hallyn_> or does 'feature is a success' mean that the users got what they wanted?
[16:38] <jamespage> actually that's a good point - 14.04 will have associated ubuntu-server docs; so don't forget to include doc tasks in your blueprints
[16:38] <arosales> sorry, its more of what the folks working on the BP define as success
[16:38] <jamespage> hallyn_, I think it means that you can demonstrate how the use cases documented are fulfilled
[16:38] <arosales> ie if dep-8 test pass that is a _metric_ for success
[16:38] <arosales> but that is definitive, and measurable.
[16:39] <arosales> it should tie directly to the goal, but be more straightforward on how the goal is going to be specifically meet.
[16:40] <arosales> basically what are tangible working towards, and how do we know we are done
[16:40] <arosales> thoughts?
[16:40] <arosales> perhaps this is covered in an existing template point . . .
[16:41] <arosales> crickets
[16:41] <jamespage> those are the ones in my head doing that
[16:41] <gaughen> so I'm way late here - but another event  coming up is vUDS
[16:42] <jamespage> I think it comes down to how do you demonstrate that a feature is implemented
[16:42] <arosales> jamespage, correct
[16:42] <arosales> jamespage, basically I was looking for a way to document _when_ the feature is complete.
[16:42] <hallyn_> that's the halting problem
[16:43] <arosales> hallyn_, please expand
[16:43] <arosales> gaughen, good point on http://uds.ubuntu.com/
[16:43] <arosales> #link http://uds.ubuntu.com/
[16:43] <gaughen> arosales, it's on my mind because of having to host some sessions ;-)
[16:43] <hallyn_> arosales: nah, just being a wiseass
[16:43] <arosales> hallyn_, jamespage so any bp work we define should have a deliverable we can measure and define as done
[16:43] <gaughen> arosales, it's hallyn_'s turn today to be the wiseass
[16:43] <jamespage> yup
[16:43] <arosales> if we don't have that how do we know it was done and done well?
[16:44] <jamespage> so when arosales comes along and say - show me - you can point and say - there!
[16:44] <jamespage> and he can try it himself!
[16:44] <arosales> yup, no ambiguity as to what is going to be delivered.
[16:45] <hallyn_> the bp tracks the work items.  we mark them as done.  we trust that we dont' mark them as done if they're not.  you're asking for something higher level.
[16:45] <arosales> ie _this_ is what we are defining for delivery of this feature and what we will call success
[16:45] <arosales> success = we delivered what we set out to and meet user stories and the goal
[16:45] <arosales> but needs to be tangible, and quantifiable
[16:45] <hallyn_> each work item is that
[16:46] <arosales> hallyn_, so those are pieces
[16:46] <arosales> what are those pieces incrementally working to deliver?
[16:46] <arosales> hallyn_, not high level
[16:46] <hallyn_> as someone said, that's the user stories
[16:47] <arosales> hallyn_, what I am looking for when all work items are done what specifically did the BP deliver?
[16:47] <arosales> is it?
[16:47] <hallyn_> arosales: user stories.  i know what you're getting at, but i don't think it's a good use of our time to try and build test cases - and run them - for each user story
[16:48] <hallyn_> maybe it is, in which case we may have to have fewer work items so we have time for that
[16:48] <hallyn_> but i think that's what uds is for each time - gauge last cycle, plan next.
[16:48] <hallyn_> anyway maybe we ned to discuss elsewhere
[16:49] <arosales> sure, I just don't think we are doing a great job of stating what is tangibly delivered
[16:49] <arosales> hallyn_, not a test case for each user story
[16:49] <arosales> just a specific deliverable stating what this BP is going to be delivered, that we can measure
[16:49] <arosales> perhaps that sets better in the goal
[16:49] <arosales> if the goal is written well. . .
[16:50] <arosales> in any case I have beaten that to death
[16:50] <arosales> I"ll try to write up something for the goal section
[16:50] <hallyn_> ok
[16:50] <arosales> #topic Announce next meeting date and time
[16:51] <arosales> Tuesday 2013-11-19 at 1600 UTC - #ubuntu-meeting
[16:51] <hallyn_> let's not
[16:51] <arosales> thanks for joining
[16:51] <hallyn_> arosales: that's uds
[16:51] <jamespage> thanks arosales
[16:51] <arosales> hallyn_, ah good point
[16:51] <hallyn_> nov 26?
[16:51] <arosales> #action arosales send email to server list to cancel Nov 19 server meeting in liu of UDS
[16:51] <meetingology> ACTION: arosales send email to server list to cancel Nov 19 server meeting in liu of UDS
[16:52] <arosales> nov 26 may collide with us holidy too
[16:52] <hallyn_> eeeeh, maybe.  i'll be here.  misses by 2 days.
[16:52] <arosales> Thanksgiving may later in the week
[16:53] <arosales> Tuesday 2013-11-26 at 1600 UTC - #ubuntu-meeting
[16:53] <arosales> thanks everyone
[16:53] <arosales> #endmeeting
[16:53] <meetingology> Meeting ended Tue Nov 12 16:53:21 2013 UTC.
[16:53] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-11-12-16.03.moin.txt
[16:53] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-meeting/2013/ubuntu-meeting.2013-11-12-16.03.html
[16:53] <hallyn_> thanks arosales


[00:06] <qwebirc96010> can dust/debris on a PCIe hvr card prevent it from scanning channels or recording properly?
[00:50] <Hydr0p0nX> how do I get UDF formatted dvd's to automount? ISO format dvd's do and bluray disks do, just not udf dvd
[02:54] <Hydr0p0nX> how do I get UDF formatted dvd's to automount? ISO format dvd's and bluray disks automount as expected, just not udf dvds.
[05:05] <qwebirc96010> Hydr0p0nX:  if you mean automount at boot time, AFAIK, then you probably need to modify '/etc/fstab'.  If you're talking about automount by the desktop manager, then mythbuntu's "file manager" or other configuration utility should automatically be mounting UDF images... are the UDF disks that you're trying to mount closed disks..  Were the disks "closed" after burning?
[05:06] <qwebirc96010> If not that might possibly be why, althought that might still be a bug in Ubuntu.  Were the disks written to a rewritable DVD?  because AFAIK, some rewritable DVD brands are notorious for not being recognized... but in either case, it might be a bug in Ubuntu.
[14:31] <Hydr0p0nX> how do I get UDF formatted dvd's to automount? ISO format dvd's and bluray disks automount as expected, just not udf dvds. the dvd is retail purchased movie, not something that was burned
[23:39] <Hydr0p0nX> how do I get UDF formatted dvd's to automount? ISO format dvd's and bluray disks automount as expected, just not udf dvds. the dvd is retail purchased movie, not something that was burned, dmesg shows it being mounted by udf-fs but it never actually mounts
[23:51] <bonelifer> Hydr0p0nX: can't help you but say GOOGLE and this https://askubuntu.com/questions/653445/ubuntu-14-04-lts-automount-cd-dvd-to-media
[23:51] <Hydr0p0nX> I've spent weeks in google
[23:52] <Hydr0p0nX> manually mounting the drive works, it's just the automount that fails
[23:54] <bonelifer> not sure what version, but maybe look at this: https://askubuntu.com/questions/76860/cd-dvd-drive-not-mounted-when-inserted-with-disc-of-any-kind   it says to install udftools.
[23:54] <Hydr0p0nX> udftools is installed
[23:54] <Hydr0p0nX> udf automounts fine for bluray, just not dvd
[23:54] <Hydr0p0nX> same drive
[23:55] <Hydr0p0nX> dmesg even says udf-fs is mounting the drive, it just doesn't do it unless I explictily mount it
[23:57] <Hydr0p0nX> As for version, VERSION="14.04.4 LTS, Trusty Tahr" and kernel  4.2.0-34-generic #39~14.04.1-Ubuntu SMP
[23:58] <bonelifer> This post suggests UDF DVD Video should be fstype iso9660 as opposed to udf: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/44233
[23:59] <bonelifer> you'd probably get better responses on either ubuntuforums or askubuntu


[11:08] <mhroncok> smoser: hi, got a minute?
[13:20] <smoser> mhroncok, whats up?
[13:21] <mhroncok> smoser: I wan to talk with you about cloud-init and Python 3
[13:21] <mhroncok> smoser: cloud-init is the last thing in Fedora cloud stack, that doesn't support Python 3
[13:21] <mhroncok> smoser: and we would like to make it happen
[13:22] <mhroncok> how can we help?
[13:22] <smoser> its on a list, and it should have been done alrady.
[13:23] <smoser> i'm open to patches for that. we've done some work in that direction (dropping boto and cheetah recently)
[13:23] <mhroncok> there are several relevant issues opened, but it seems nothing is happening, so we we would be happy to help with patches - however we are not sure what should we focus on first
[13:23] <mhroncok> BTW boto now supports Python 3
[13:24] <mhroncok> I've seen this: https://code.launchpad.net/~harlowja/cloud-init/changeable-templates/+merge/208994
[13:25] <mhroncok> so now it should only be about cloud-init itself?
[13:26] <smoser> i didn't know about boto and python3, thats good. yeah, it should be only cloud-init itself.
[13:27] <mhroncok> is there any branch for python 3 porting or stuff liek tyhat, or we should just start with trunk?
[13:27] <mhroncok> s/liek tyhat/like that/
[13:27] <smoser> trunk.
[13:28] <smoser> harlowja_away, may have taken some further look at it.
[13:28] <mhroncok> smoser: ok, thanks for info
[13:30] <smoser> i think it makes sense to get to python3 support in cloud-init.
[13:31] <smoser> there is some discussion about doing a cloud-init 2.0, which would start with python3 as the starting point.
[13:31] <smoser> and probably not bother with python2 support
[13:31] <mhroncok> smoser: is there a way to send patches, but don  not sign CCA?
[13:33] <smoser> i'm sorry, there is not.
[13:33] <smoser> contributors agreement are required i many projects.
[13:34] <mhroncok> I'm not even sure I can sign that, will consult my boss :)
[14:14] <jfontan> hi
[14:14] <jfontan> I am doing some modifications to a cloud init datasource
[14:15] <jfontan> but I am unable to get the error
[14:15] <jfontan> I only get a warning saying "Getting data from <clas...
[14:15] <jfontan> I only get a warning saying "Getting data from <clas...> failed
[14:16] <jfontan> is there any way I can see the errors?
[14:38] <smoser> jfontan, maybe /var/log/cloud-init.log has an error ?
[14:45] <jfontan> nope, that is the only error
[14:46] <jfontan> I've added a traceback print to may copy of cloud-init
[14:46] <jfontan> in find_source
[14:46] <jfontan> may=my
[16:03] <smoser> jfontan, you should get something else along side that error.
[16:06] <jfontan> it only said it failed
[16:06] <jfontan> it was an error in the code
[16:07] <jfontan> but the exception blod just printed that it could not get the data
[16:07] <jfontan> block
[16:08] <jfontan> here
[16:08] <jfontan> http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/cloudinit/sources/__init__.py#L255
[16:57] <smoser> harmw, what do you need me to merge ?
[16:57] <smoser> jfontan, yeah, but it should log a stack trace
[16:57] <jfontan> it didn't for me
[17:02] <smoser> can you pastebinit ?
[17:02] <smoser> the whole log ?
[17:08] <jfontan> I'll have to create the image again
[17:10] <jfontan> as I don't have the error in the code anymore and it has the trace print in. I'll check if I have an old vm
[17:18] <jfontan> smoser, https://gist.github.com/jfontan/bcf18f262cd06252ff1a#file-gistfile1-txt-L13
[17:19] <jfontan> it only says that it failed but no stacktrace
[17:19] <jfontan> I'm using trunk
[17:20] <smoser> so the error you see there is the one you added ?
[17:20] <smoser> the stack trace
[17:21] <harlowja> smoser did i hear python3
[17:21] <harlowja> lol
[17:21] <jfontan> nope, I took out the strack trace printing code
[17:21] <jfontan> the error is in OpenNebula Data source
[17:21] <jfontan> and just tells it failed
[17:22] <jfontan> no stacktrace
[17:22] <smoser> hm.. that is odd. i dont know why.
[17:22] <jfontan> there is an stacktrace for openstack but that's something I'm not working on
[17:22] <smoser> yeah, and that is wrong.
[17:22] <smoser> you're using turnk her e?
[17:22] <jfontan> yes
[17:22] <smoser> harlowja, you see that ^ .
[17:22] <smoser> that should probably not be a fail
[17:22] <harlowja> whats the trace?
[17:22] <smoser> but rather a "no datasource here, move along"
[17:23] <smoser> https://gist.githubusercontent.com/jfontan/bcf18f262cd06252ff1a/raw/960d80f5263ebbe909ab786ef1ece8bc5d04cda6/gistfile1.txt
[17:23] <harlowja> smoser hmmm, will fix
[17:23] <jfontan> it's a failure. I mistyped a variable
[17:23] <smoser> and any idea why we wouldnt get a log
[17:23] <smoser> of that failure there.
[17:24] <smoser> for the 'DataSourceOpenNebula' line
[17:24] <jfontan> it could be the code in data source
[17:24] <jfontan> maybe it's catching all exceptions
[17:24] <smoser> well, it is.
[17:24] <jfontan> I'll take a look
[17:25] <smoser> but then it calls
[17:25] <smoser>  util.logexc(LOG, "Getting data from %s failed", cls)
[17:26] <jfontan> so that logexc should print the trace, isn't it?
[17:26] <smoser> yeah.
[17:30] <jfontan> I have to go
[17:30] <jfontan> good luck
[17:37] <harlowja> smoser https://code.launchpad.net/~harlowja/cloud-init/mini-os-fixes/+merge/233399
[18:02] <harlowja> mhroncok also https://code.launchpad.net/~harlowja/cloud-init/py2-3 for your py3 messages
[18:02] <harlowja> thats the branch that imho will enable mixed py2/py3 mode
[18:03] <harlowja> which will be required for older distros that aren't all py3 yet
[18:03] <mhroncok> harlowja: great, thanks
[18:03] <harlowja> i did some basic testing from what i remember with py3 and pretty sure i nailed most of the issues down
[18:03] <mhroncok> BTW harlowja smoser, cannot I just give you my patches as Public domain?
[18:04] <harlowja> mhroncok smoser  probably knows better than i all that stuff, i never got into the legal stuff :-P
[18:04] <smoser> mhroncok, i dont think so.
[18:04] <mhroncok> ok, waiting to hear from our legal :D
[19:03] <smoser> harlowja, i don think you fixed https://gist.githubusercontent.com/jfontan/bcf18f262cd06252ff1a/raw/960d80f5263ebbe909ab786ef1ece8bc5d04cda6/gistfile1.txt
[19:03] <smoser> in mini-os
[19:03] <smoser> mini-os-fixes
[19:04] <harlowja> k, maybe i misunderstand ?
[19:04] <smoser> so in that log
[19:04] <smoser> hm..
[19:04] <smoser> oldd.
[19:04] <harlowja> 'openstack.py[ERROR]: Failed reading mandatory path /tmp/tmpX2lt9o/openstack/latest/meta_data.json' ?
[19:04] <harlowja> thats now demoted to debug
[19:04] <smoser> i have to look at this more. i didn't hitnk he had a config drive there.
[19:05] <smoser> oh i see.
[19:05] <smoser> so that would be debug, but then there is / should be no ERROR
[19:05] <harlowja> _fetch_available_versions() takes exactly 1 argument (2 given) also should be fixed
[19:05] <smoser> agreed there.
[19:05] <smoser> i thought what had happend there was that there was no config drive
[19:06] <smoser> and that should result in the DSs' _get_data() returnning False
[19:06] <smoser> with only debug messages
[19:07] <harlowja> sure, i just think the differeniation between searching for get_data that will work and actually using a get_data that then fails isn't clear
[19:07] <harlowja> thats probably part of it
[19:07] <harlowja> maybe should be refactored to find_data (which then only outputs debug messages) and get_data (which actually outputs errors)
[19:08] <harlowja> sepearting the non-failure find process from the actual problems get_data
[19:08] <harlowja> there sorta munged together at this point
[19:16] <smoser> well, _get_data returns True on "I've found"
[19:17] <smoser> and False on "nope"
[19:19] <harlowja> right, but say it had a finding method, this one would return True/False, then it had a read method that would read from the previous location found (if it was) and would log errors and such
[19:19] <harlowja> the find method would be expected to never log errors and such
[19:20] <harlowja> but the read method could (instead of what we currently do is make everything debug, since we are doing both find and read in the same method)
[19:25] <smoser> i agree, it can be better.
[19:28] <smoser> harlowja, can you fix that though ?
[19:28] <harlowja> hehe, what i'm supposed to fix?
[19:28] <harlowja> lol
[19:29] <smoser> it needs to be debug only on "not found"
[19:29] <smoser> and ideally not stack trace :)
[19:30] <harlowja> right, https://code.launchpad.net/~harlowja/cloud-init/mini-os-fixes/+merge/233399 switches those to debug ?
[19:30] <harlowja> with no stack-trace
[19:31] <harlowja> but i might still be confused, lol
[19:31] <harlowja> oh, i think i see one more
[19:34] <harlowja> ok, think i got them (reuploaded)
[20:00] <smoser> how did it do no stacktrace
[20:03] <harlowja> except openstack.NonReadable:
[20:03] <harlowja>             return False
[20:03] <harlowja> probably that
[20:03] <harlowja> except openstack.NonReadable:
[20:03] <harlowja>             return False
[20:03] <harlowja>         except (openstack.BrokenMetadata, IOError) as e:
[20:03] <harlowja>             LOG.debug("Broken metadata address %s: %s",
[20:03] <harlowja>                       self.metadata_address, e)
[20:03] <harlowja>             return False
[20:04] <harlowja> shall that be changed?
[20:04] <harlowja> or similar in 'DataSourceConfigDrive'
[20:15] <harmw> smoser: https://code.launchpad.net/~harmw/cloud-init/freebsd-fixes
[20:15] <harmw> https://code.launchpad.net/~harmw/cloud-init/freebsd-fixes/+merge/233247
[20:23] <smoser> harmw, tried to build the cirros with patched busybox
[20:23] <smoser> but busubox didn't get patched
[20:23] <smoser> not sure why
[21:07] <harmw> sorry man, this time it's me beeing way to busy :)
[21:16] <smoser> harmw, no worries.
[21:16] <smoser> it seems like an easy fix
[21:16] <smoser> http://paste.ubuntu.com/8253590/
[21:53] <harmw> hm, that makefile change... can't recall i needed that
[22:11] <smoser> no
[22:11] <smoser> you didn't
[22:11] <smoser> that was debug


[12:24] <N6REJ> hello, I'm wondering if you could give me some guidance.  I have a Kubuntu server that is for LAMP , quasar and postgres.  My wife also uses it for her desktop machine ( yeah I know bad boy, but her machine died ), anyway, we access it currently from her KDE gui, my KDE machine, and an XP machine.  Most of the time we only use the server for our intranet but sometimes we want certain people to be able to reach quasar from the outside.
[12:24] <N6REJ>  I have had issues with the servername causing strange behavior.  Like when it was named "ubuntu" sometimes I would get taken to a porn site because ubuntu.iowatelecom.net ( iowatlecom.net is my isp ) doesn't resolve.   My question is exactly how should I configure the server/servername so that it is accessible from all local machines, and still not confuse the browsers?
[12:33] <somerville32> I don't understand what ubuntu.iowatelcom.net has to do with the hostname
[12:33] <somerville32> Why would it matter if the subdoamin of your ISP resolves?
[12:33] <somerville32> You should have a host lists which has the name of the machine which it looks at before querying the DNS server
[09:29] <[miles] > good morning #ubuntu-server
[04:36] <drarem> who is <IP_ADDRESS>  ?
[07:07] <shwag> how do I change the permissions that my log files are created with ?
[07:08] <shwag> I can do a  chmod +r /var/log/*    , but then when new log files are rotated in, they dont have the +r.
[09:05] <drarem> how secure would an apache2 / mysql ubuntu server be?  would a rootkit be installable remotely?  how paranoid do i have to be?
[11:09] <malix0> hi all
[11:10] <malix0> yesterday I try to install ubuntu-server on an IBM server, the installation was ok, but grub failed