[00:05] <ToyKeeper> Gah, I need to remember to wait longer after imgbot declares a build finished...  I keep getting the previous build flashed because I didn't wait long enough.
[00:07] <bfiller> robru: can you please allocate rtm silos for line 88 and 86?
[00:15] <robru> bfiller: ok you got rtm silos 3 and 6
[00:15] <bfiller> robru: ty!!
[00:15] <robru> bfiller: you're welcome!
[00:23] <AlbertA2> trainguards: can I get a silo for line 85?
[01:01] <ToyKeeper> dobey: Around?  Got any info about how to test the new behavior in silo rtm-022?  https://code.launchpad.net/~dobey/unity-scope-click/invalid-token/+merge/235852
[01:01] <ToyKeeper> The MP and test plan say nothing about how to actually check it.
[02:10] <imgbot> [02:34] <alecu> ToyKeeper: hi! I've added info on how to test silo rtm-022 to the end of the click scope testplan: https://wiki.ubuntu.com/Process/Merges/TestPlan/unity-scope-click
[02:34] <alecu> thanks for noticing!
[02:41] <plars> robru: I'm here on and off, I've been pretty sick today though, and hoping to get to bed before 12 if at all possible
[03:10] <imgbot> [03:29] <ToyKeeper> alecu: Thanks for getting back to me so fast.  :)
[03:40] <imgbot> [03:40] <imgbot> [04:03] <Mirv> AlbertA2: silo 027 for line 85
[04:15] <imgbot> [04:15] <imgbot> [05:25] <oSoMoN> trainguards: good morning, can I have a silo for line 67 ?
[05:56] <Mirv> oSoMoN: sure
[05:57] <Mirv> at least if our login server starts to work
[06:10] <oSoMoN> Mirv, thanks!
[06:17] <Mirv> funny how we now have 10 more silos and the utopic ones are full :)
[06:17] <Mirv> mostly because of utopic freeze though and packages being stuck
[07:54] <Mirv> pete-woods: pstolowski: so I think the end result of landing-020 discussion was that the new apparmor blacklist file should not be in libthumbnailer, but maybe in the common package?
[07:55] <pete-woods> Mirv: yes. the problem is it is arch specific. just talking about what to do now...
[07:56] <brendand> pete-woods, hey are you aware of any plan to remove the requirement to sign in to u1 from the click scope?
[07:56] <Mirv> pete-woods: ok, thanks.
[07:56] <pete-woods> brendand: no, wasn't aware of that at all
[07:57] <brendand> ogra_, i appear to be in a bit of a situation with adb
[07:57] <brendand> pete-woods, well that might be for a good reason - it's just i was testing a system-settings silo (of all things) last night, and all of a sudden found myself not needing to sign in
[07:57] <brendand> pete-woods, i'm 100% sure i wasn't already signed in
[07:58] <brendand> pete-woods, not implicating you in that issue, but thought you might know if that was intended
[08:00] <pete-woods> brendand: sorry, no. you'd have to talk to one of the click scope developers (american / brazil tz) alecu or dobey
[08:00] <pete-woods> it could well be intended
[08:01] <pete-woods> and IMO it's waaay better not to have to sign into some random account I don't want just to download apps
[08:01]  * pete-woods will check the bzr logs on the click scope
[08:04] <brendand> pete-woods, i agree - but i didn't install anything click scope related
[08:08] <davmor2> brendand: man what did you break now
[08:08] <brendand> davmor2, adb
[08:09] <ogra_> but why ?
[08:09] <brendand> ogra_, how can i check that everything is right client side?
[08:09] <brendand> ogra_, i've even reverted way back to a known good image
[08:09] <ogra_> android-gadget-service status adb
[08:09] <brendand> ogra_, bah, i meant host side
[08:09] <ogra_> ps ax|grep adbd
[08:10] <brendand> ogra_, although isn't the laptop the client in this scenario :P
[08:10] <ogra_> well, check your syslog and see if you get USB plug events when you re-plug
[08:10] <brendand> ogra_, i will - but i have MTP connectivity so...
[08:11] <ogra_> that would be checking the lowest level
[08:11] <ogra_> right, if you have working mtp the connection should be fine
[08:11] <ogra_> but syslog would still tell you if it i.e. doesnt know the vendor or device ID
[08:12] <ogra_> (which is essntial for handling the permissions via udev)
[08:12] <brendand> ogra_, http://paste.ubuntu.com/8431270/
[08:12] <ogra_> on the next layer you can simply try restarting the adb server
[08:12] <ogra_> adb kill-server; adb devices
[08:12] <brendand> ogra_, done that many times
[08:13] <brendand> ogra_, since last night this is happening
[08:13] <brendand> ogra_, and the weirdest thing is it works in recovery
[08:13] <ogra_> weird
[08:13] <ogra_> ot gets forced on in recovery ... are you sure the developer mode is actually still enabled ?
[08:14] <brendand> ogra_, yep - adbd is running, 'adb enabled' - the switch is correct
[08:14] <ogra_> did you try on another machine ?
[08:15]  * ogra_ gets meeting coffee
[08:16] <davmor2> brendand: ogra_: it works here are you testing ogra_ 's silo or something?
[08:16] <pete-woods> brendand: looks like the scope hasn't been updated in utopic since the 15th, but we just synced that version to RTM
[08:17] <pete-woods> but that release only added support for showing dollars , or something like that
[08:18] <brendand> davmor2, nope i'm using the last promoted image now
[08:18] <pete-woods> and looking back through the history, I see nothing to imply the login requirement has been removed
[08:18] <brendand> ogra_, don't have another laptop
[08:18] <popey> hmm, i think my nexus 7 is bricked. can't boot it
[08:26] <ogra_> bah, my session just crashed after OTA
[08:26] <brendand> ogra_, i found another laptop, but it's trusty
[08:26] <ogra_> and now it hung for 20sec during SIM unlock
[08:27] <brendand> ogra_, i wonder do adb and adbd produce any verbose logs?
[08:28] <brendand> ogra_, mako is working fine for me btw
[08:28] <ogra_> not really
[08:28] <ogra_> on the device adbd logs to syslog ...
[08:28] <ogra_> beyond that adb shell uses sudo so that goes to auth.lo
[08:28] <ogra_> g
[08:29] <ogra_> and there is the upstart job that captures stdout of the adbd daemn
[08:29] <brendand> it doesn't show up in adb devices either
[08:29] <ogra_> *daemon
[08:34] <ogra_> brendand, android-gadget-service enable ssh
[08:34] <ogra_> (indeed requires your key on the device)
[08:38] <brendand> ogra_, huh? it just contains 'stdin: is not a tty'?
[08:38] <brendand> ogra_, the android-tools-adbd.log
[08:38] <ogra_> yes
[08:38] <brendand> ogra_, oh. that's helpful
[08:38] <ogra_> adbd isnt very noisy :)
[08:48] <brendand> ogra_, what versions of packages do i need to have to make krillin work?
[08:48] <brendand> ogra_, android-tools-adb and phablet-tools latest i guess?
[08:48] <brendand> ogra_, from which ppa?
[08:49] <brendand> ogra_, since this other laptop is trusty
[08:54] <ogra_> brendand, phablet-tools
[08:56] <brendand> 20140923, must be new enough
[08:57] <brendand> ogra_, ok it appears now on my other laptop
[08:57] <brendand> phew
[08:57] <ogra_> USB 3.0 vs USB 2.0 ?
[08:57] <brendand> ogra_, yes perhaps
[08:58] <ogra_> or does one of the BIOSes have some legacy mode en/disabled
[08:58] <brendand> ogra_, i always used the 3.0 port before
[08:58] <brendand> ogra_, i know the one that's working doesn't even have EFI
[08:58] <ogra_> well, it looks like a transport prob
[08:58] <ogra_> i'd check the USB settings in the BIOS/UEFI
[09:00] <brendand> ogra_, ok fixed!
[09:00] <ogra_> :)
[09:00] <brendand> ogra_, had to upgrade android-tools-adb on the laptop
[09:01] <ogra_> hah
[09:01] <brendand> ogra_, but why? not that i want to think too hard about it
[09:01] <ogra_> depends how outdated you were there ...
[09:02] <ogra_> we once added the proper udev rule for krillin ... that was the last change to adb on the PC side though
[09:02] <brendand> well i can get back to work now at least
[09:02] <ogra_> and was quite a bit ago
[09:02] <brendand> ogra_, i went from 24 to 35
[09:03] <brendand> ogra_, i think i know what happened
[09:03] <ogra_> yeah, most of them were adbd ... not adb changes
[09:03] <brendand> ogra_, i defined that rule manually according to the wiki page
[09:03] <ogra_> ah. yeah
[09:04] <ogra_> sil2100, none of the changed packages grew a direct dep ...
[09:05] <Mirv> sil2100: ^ note that you're landing stuff :)
[09:06] <Mirv> sil2100: in other news, what's blocking some landings currently: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1374355
[09:14] <lool> trainguards, network-manager is out of unapproved into utopic, so you can reclaim its silo and I guess we'll need an rtm one
[09:14] <lool> cyphermox: is there a LR for rtm?
[09:14] <Mirv> lool: thanks, doing that
[09:14] <cyphermox> a what?
[09:15] <lool> a landing reqeust
[09:15] <cyphermox> I don't know, tvoss was dealing with all of this
[09:15] <lool> cyphermox: too many TLAs!
[09:15] <lool> cyphermox: ok
[09:17] <lool> cyphermox: I've added a line in the spreadsheet with the 3 of us listed for network-manager + rtm; noted to look at list of visible wifis
[09:17] <Mirv> sil2100: the bug blocks among else Unity8 from migrating to release pocket, which blocks mzanetti & co on continuing towards the next landing. I think we might want to merge & clean.
[09:19] <mzanetti> Mirv: would that mean it merges our code, but still doesn't release the updated unity8 package to distro?
[09:20] <Mirv> mzanetti: yes, so that you would have trunk up-to-date and maybe consider doing "rtm first" for the next landings. but I'll let sil to comment on that.
[09:21] <mzanetti> sure
[09:21] <mzanetti> just want to understand what the options are
[09:25] <Mirv> lool: I fixed the line to be a network-manager sync from utopic (instead of sync:1), and assigned a silo
[09:25] <lool> Mirv: ok, thanks
[09:52] <Mirv> mitya57: could you smoketest the appmenu from the PPA once more so I can mark it as tested and let sil2100 press the publish button?
[09:56] <mitya57> Mirv: yes, wait a moment
[09:58] <joc> is there an ETA for the next build on rtm-proposed? really keen to test out wpa fixes
[10:00] <mitya57> Mirv: tested https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-030/+build/6411305/+files/appmenu-qt5_0.3.0%2B14.10.20140926-0ubuntu1_i386.deb, works fine
[10:02] <Mirv> mitya57: thanks!
[10:05] <cyphermox> Mirv: sil2100: were you planning on building a new image soon?
[10:05] <cyphermox> it might be useful to build a new image for the wpa fix.
[10:05] <cyphermox> doh
[10:05] <cyphermox> joc: ^ sorry :D
[10:13] <lool> trainguards, something weird happened with qtubuntu-sensors; it has a higher version in ubuntu-rtm than in ubuntu
[10:14] <lool> ubuntu-rtm seems to have skipped one version
[10:14] <lool> (Cc: oSoMoN )
[10:14] <ogra_> lool, why is that weird ?
[10:14] <lool> it should have been a sync
[10:14] <lool> also we're pretty screwed if we bump the version in ubuntu now
[10:14] <ogra_> lool, you can nowadays land in rtm first (but need to go on to do so once you started i think)
[10:15] <lool> ogra_: the same fix was landed in ubuntu, then in rtm
[10:15] <lool> so it should have been the same source
[10:15] <lool> also, no rtm version in the rtm source
[10:15] <lool>  qtubuntu-sensors | 0.6+14.10.20140924-0ubuntu1 | utopic/universe           | source, amd64, armhf, i386
[10:15] <ogra_> lool, well, i guess it was beta-frozen in ubuntu then
[10:15] <lool>  qtubuntu-sensors | 0.6+14.10.20140924-0ubuntu2 | ubuntu-rtm/14.09/universe | source, amd64, armhf, i386
[10:15] <lool> it's not in unapproved
[10:15] <ogra_> colin is just unleashing the horses
[10:15] <lool> and it was accepted in ubuntu first
[10:16] <ogra_> ok, then it is weird ... agreed :)
[10:19] <sil2100> Ah uh
[10:19] <sil2100> lool: ok, so the reason why it's like that is:
[10:20] <sil2100> lool: qtubuntu-sensors got synced into a silo, then removed, and then rebuilt again with a source sync - since PPAs don't allow pushing the same version to the same PPA again, CI Train had to bump the ubuntu version ;/
[10:22] <sil2100> lool: it was like that because those were source copies still, not binary copies
[10:23] <sil2100> lool: not sure how to resolve this now
[10:23] <sil2100> Mirv: ;)
[10:25] <sil2100> cyphermox: do you mean an RTM image or utopic image? ;)
[10:25] <sil2100> Where did that land?
[10:25] <cyphermox> RTM
[10:30] <sil2100> lool: in any case, this should not happen now as we're doing binary copies instead
[10:31]  * ogra_ can happily build an RTM image if wante
[10:31] <ogra_> d
[10:31] <sil2100> Yeah, I think we can build an image now, nothing specific we're waiting for
[10:32] <sil2100> ogra_: fire away!
[10:32] <ogra_> done
[10:33] <ogra_> john-mcaleely, were you planning another device tarball today ?
[10:33]  * ogra_ would like the last adb fix from rsalveti in ...
[10:34] <ogra_> (since it will improve RTM testing on krillin a lot)
[10:39] <lool> sil2100: we could copy the ubuntu2 source to ubuntu
[10:39] <lool> with binaries
[10:40] <imgbot> [10:45] <sil2100> lool: I would have to understand why the source copy has happened, but anyway ubuntu1 and ubuntu2 have the same contents
[10:45] <sil2100> Exactly the same contents
[10:45] <sil2100> At least the sources
[10:45] <sil2100> Since binaries might differ
[10:46] <lool> sil2100: what worries me is if an ubuntu upload happens now
[10:46] <lool> I suppose it would reject an ubuntu2
[10:46] <sil2100> Why?
[10:46] <ogra_> lool, nobody would do such an upload though ... it would go through a silo
[10:46] <ogra_> which bumps the upstream date
[10:47] <sil2100> lool: yeah, since it's a CI Train package, so it only bumps the upstream version
[10:47] <sil2100> We should be fine in overall
[10:47] <lool> I've copied to ubuntu
[10:47] <lool> seemed plain wrong to have two versions with the same contents and using ubuntu numbering and a higher version in rtm
[10:51] <Mirv> pete-woods: pstolowski: should that "Re-enable valgrind" hud landing land to rtm too, ie should I add a line for it?
[10:51] <pete-woods> Mirv: it landed already. confusing because of the beta freeze!
[10:51] <pete-woods> i.e. made it into RTM first
[10:51] <pete-woods> bad, yes!
[10:52] <oSoMoN> trainguards: can utopic silo 16 be published, please?
[10:52] <Mirv> pete-woods: ah well, yes that's the new normal anyway that packages first to RTM, I just thought https://lists.canonical.com/archives/rtm-14.09-changes/2014-September/000451.html didn't include it (and it's the only hud landing I see in rtm)
[10:56] <Mirv> bot is going wild
[10:56] <ogra_> Mirv, sil2100, how to i reach the 20+ PPAs on the dashboard ?
[10:57]  * ogra_ wants to publish 026
[10:57] <davmor2> ogra_: psychicly?
[10:57] <ogra_> davmor2, hmm
[10:57] <Mirv> ogra_: mm, by scrolling down?
[10:57]  * ogra_ tries
[10:57] <ogra_> Mirv, it ends at 20 ?
[10:57] <Mirv> ogra_: not for me
[10:57] <ogra_> http://people.canonical.com/~platform/citrain_dashboard/#?distro=ubuntu&q=
[10:58] <Mirv> weird
[10:58] <Mirv> refresh?
[10:58] <ogra_> oh
[10:58] <ogra_> funny
[10:58] <ogra_> it auto-refreshed all the time
[10:58] <ogra_> but didnt add the new bits
[10:58] <Mirv> the page is so ajax it sometimes forgets about itself in all that asynchronous smoothness
[10:59] <ogra_> heh
[10:59] <Mirv> the bot is really serious about that cleaning of 011
[10:59] <ogra_> hehe
[11:00] <ogra_> it must be glossy and polished in the end
[11:00]  * davmor2 wonders what the devel communities fetish with household cleane, vim, ajax we are only missing cilit bang
[11:01] <ogra_> davmor2, geez, dont tell it more brands !
[11:01] <davmor2> s/cleane/cleaners
[11:01] <davmor2> ogra_: I expect to see demestos and dettol some time soon ;)
[11:02] <ogra_> nooo ... dont give the bot ideas !
[11:02] <ogra_> see
[11:02] <brendand> flash, mr muscle, toilet duck
[11:03] <brendand> queuebot, we get it
[11:04] <davmor2> someone get the bot some industrial bleach
[11:07] <ogra_> not it wants to tell us how clean it got it
[11:09] <Mirv> it's so empty and clean now it's practically a vacuum
[11:09] <Mirv> even quarks don't pop in and out of existence
[11:12] <pete-woods> Mirv: can we run that packaging NACK by another distro person? it seems that the file that they wanted to go into -common is actually arch specific
[11:12] <pete-woods> actually never mind, we'll do another solution
[11:12] <Mirv> pete-woods: any distro person would say libthumbnailer0 is a wrong place for /etc file
[11:12] <cjwatson> agreed
[11:12] <cjwatson> terrible plan, causes known classes of problems
[11:13] <cjwatson> doesn't matter whether it's arch-specific or not, that's another axis
[11:13] <pete-woods> okay, that's fine by me then. just wanted to ensure that wasn't a valid argument
[11:13] <cjwatson> -common can be arch-specific if that's what it takes
[11:23] <Mirv> do you want more clean? more clean!
[11:25] <Mirv> yes!
[11:25] <Mirv> sil2100: ^ might I turn your attention towards the bot?
[11:30] <pete-woods> wow, those PPA are really clean!
[11:35] <Mirv> thanks Laney
[11:35] <Laney> oops
[11:35] <Laney> Mirv: you or any ubuntu member can remove it when fixed apparently
[11:35] <Laney> quite liberal acl in here
[11:51] <sil2100> hmm
[11:52] <sil2100> Mirv: I don't know the queuebot code
[11:52] <sil2100> The dashboard looks fine so I have no idea why it's going crazy on those 2 silos
[11:53] <sil2100> (which are obviously empty now)
[11:54] <sil2100> Mirv: love your comments on the queuebot's craziness ;)
[11:54] <cjwatson> you'd need to get stgraber to fix it I expect
[11:54] <sil2100> I think robru is the main author of the recent queuebot plugin additions
[11:54] <sil2100> I don't even know where the code is held, would have to look
[11:59] <Mirv> sil2100: ok, let's wait for robru mayabe then
[12:00] <sil2100> Mirv: we had such an error in the past when queuebot was indexing landings per description, but that was fixed long ago
[12:07] <mzanetti> sil2100: hey... just figured that we have this issue once more
[12:07] <mzanetti> qtdeclarative5-qtmir-plugin : Hängt ab von: libmircommon1 (>= 0.7.3+14.10.20140918.1) aber 0.7.3+14.10.20140918.1~rtm-0ubuntu1 soll installiert werden
[12:09] <sil2100> grrr
[12:09] <ogra_> Mirv, sil2100, spreadsheet line 94 and 95 please
[12:09]  * sil2100 loves hard-deps
[12:09] <sil2100> mzanetti: in which silo is that?
[12:09] <mzanetti> sil2100: rtm/6
[12:10] <sil2100> mzanetti: this time it might not be easily fixable, as a re-release as a binary copy might be risky and a bit of a hassle, one moment
[12:10] <sil2100> ogra_: o/
[12:10] <Mirv> ogra_: ok
[12:10] <ogra_> :)
[12:10] <sil2100> ogra_: ok, it seems Timo is on it ;)
[12:10] <mzanetti> sil2100: are we doing something wrong in unity land?
[12:11] <Mirv> ogra_: conflicts with landing-018 (touch-session)
[12:11] <ogra_> gah
[12:11] <sil2100> mzanetti: no, all is good, it's just a specific case
[12:11] <Mirv> rtm would be fine
[12:11] <ogra_> Mirv, then leave it for now, rtm and utopic need to land at the same time
[12:11] <ogra_> else one of them wont pass any tests anymore
[12:11] <ogra_> well
[12:11] <Mirv> ogra_: ok, removing the assigned rtm silo
[12:12] <ogra_> *if* the session stuff lands in both actuall
[12:12] <ogra_> i could hold back the utopic side i guess
[12:12] <ogra_> Mirv, leave the rtm silo ... i can at least prepare everything
[12:19] <Mirv> ogra_: ok, reassigning :)
[12:19] <ogra_> sorry :)
[12:20] <Mirv> ogra_: ubuntu-rtm/landing-008
[12:32] <mardy> fginther: hi! Do you know what's wrong here? To my knowledge, we haven't changed coverage rules in a long time, so I'm not sure why it's failing: https://jenkins.qa.ubuntu.com/job/accounts-qml-module-utopic-amd64-ci/3/console
[12:32] <sil2100> mzanetti: let me take a look at this in a moment again ;/
[12:34] <mzanetti> sil2100: ok. have to leave for about 1.5 hours now. can you coordinate with kgunn until I'm back please
[12:34] <kgunn> mzanetti: o/ got it
[12:35] <mzanetti> he should be up to date with current status
[12:36] <sil2100> ACK
[12:37] <greyback> trainguards: please can I get silo for row 81
[12:37] <greyback> actually no, please ignore that
[12:37] <greyback> silo6 still not landed
[12:49] <cwayne> davmor2: pingaling
[12:53] <Mirv> pete-woods: pstolowski|lunch: hmm, the rtm 018 is actually empty silo, it didn't build anything...
[12:54] <Mirv> the source silo was gone and it tried syncing from utopic but did not. so, reconfiguring and kicking abuild.
[12:54] <ogra_> Mirv, hmm, that didnt work (rtm-008)
[12:54] <ogra_> seems there is some unmerged thing
[12:55] <ogra_> hmm, in fact it seems to be choking on the ~rtm versioning
[12:55] <dobey> brendand: there is no plan to remove that requirement, no
[12:55] <ogra_> 0.108+14.10.20140909.1~rtm-0ubuntu1 vs 0.108+14.10.20140909.1
[12:55] <brendand> dobey, context, not much?
[12:56] <Mirv> ogra_: it does say it's warning, not error, though.
[12:56] <brendand> dobey, ah the question i asked this morning
[12:56] <dobey> brendand: you asked if there was a plan to remove the requirement of signing in to a u1 account to install apps, no?
[12:56] <brendand> dobey, right i hit a weird bug like that. not reproducible now though
[12:56] <ogra_> Mirv, why does it complain then ?
[12:57] <Mirv> ogra_: well, maybe it fails anyway because of that. I'm not sure which flag to set to force it.
[12:57] <ogra_> sil2100, ^^ any idea ?
[12:58] <ogra_> https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-008-1-build/41/console is the console log
[12:59] <ogra_> oh, was i missing a prepare run ?
[12:59] <sil2100> What's up exactly?
[12:59] <ogra_> sil2100, https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-008-1-build/41/console ... results in "Can't build: Some projects are missing revisions from distribution."
[12:59] <sil2100> ogra_: ah, so you're landing first for RTM here?
[12:59] <ogra_> seems i have to
[13:00] <sil2100> ogra_: hmmm
[13:00] <sil2100> ogra_: wait
[13:00] <ogra_> rsalveti occupies ubuntu-touch.session in another silo for utopic ... and he is out til monday
[13:00] <sil2100> ogra_: so, I see 2 silos with the same MP, both targetting different distros
[13:00] <ogra_> i would muchly prefer to land in utopic first
[13:00] <ogra_> sil2100, yes
[13:00] <ogra_> two different dbus versions
[13:01] <ogra_> ubuntu-toch-session will be the same in both ... dbus cant be
[13:01] <sil2100> ogra_: right... but this will require having 2 different MPs anyway, since you need to target different trunks
[13:01] <ogra_> err wht ?
[13:01] <ogra_> why would i
[13:01] <ogra_> it is the same trunk but two different dbus source packages
[13:02] <sil2100> Since landing it for one distro will make the given merge request merged into trunk, then the other will want to merge the same thing again
[13:02] <davmor2> cwayne: slap
[13:02] <ogra_> i want the same change of ubuntu-touch-session in both
[13:02] <cwayne> davmor2: ow
[13:03] <sil2100> Then why can't you land ubuntu-touch-session from an MP to utopic and then do a binary copy to RTM?
[13:03] <ogra_> sil2100, can we override the utopic landing of rsalvet then (i doubt he will mind a re-build on monday)
[13:03] <davmor2> cwayne: what's up dude?
[13:03] <cwayne> davmor2: may have a new custom for you to test later, that would fix the webapps issues for realsies
[13:03] <sil2100> ogra_: I just mean, CI Train cannot re-use merges for 2 landings
[13:03] <davmor2> cwayne: yay
[13:04] <ogra_> sil2100, right, so can we override the block from ubuntu-018 then, then i can land in utopic first, you do a sync and i can push the other dbus to the rtm silo
[13:05] <sil2100> ogra_: ok, then let me reconfigure the RTM silo for you and build the utopic one so that it builds correctly
[13:05] <sil2100> And then sync it up to the RTM silo
[13:05] <ogra_> sil2100, i need to upload the right dbus into the utopic one first i guess
[13:05] <ogra_> (i had ignored utopic because of the block)
[13:06] <sil2100> Yeah, upload it to the utopic PPA, we'll build the ubuntu-touch-session then and I'll work on syncing it up to the RTM silo correctly (without the dbus, as you mentioned you want a different dbus there)
[13:06] <ogra_> yeah
[13:08] <pete-woods> Mirv: damn. will have to test again
[13:09] <pete-woods> :(
[13:09] <pete-woods> I guess it explains why there were no regressions
[13:10] <sil2100> mzanetti, kgunn: the silo that had those dep problems... which one was that? Since rtm/6 is ubuntu-keyboard from bfiller
[13:13] <Mirv> pete-woods: it'd been a perfect regression-free release, though :)
[13:13] <pete-woods> Mirv: I can't seem to install the debs from that PPA now
[13:13] <pete-woods> dpkg: dependency problems prevent configuration of unity-plugin-scopes:armhf:
[13:13] <pete-woods>  unity-plugin-scopes:armhf depends on libunity-scopes3 (>= 0.6.6+14.10.20140916); however:
[13:13] <pete-woods>   Version of libunity-scopes3:armhf on system is 0.6.6+14.10.20140916~rtm-0ubuntu1.
[13:13] <pete-woods> does that mean we need to do more like a source build in the PPA?
[13:14] <Mirv> pete-woods: it sounds like that sil2100 ^
[13:14] <cwayne> davmor2: care to give 14.09-proposed-customized a try? i can launch webapps/tagger after a --wipe
[13:14] <davmor2> cwayne: one second
[13:14] <Mirv> I'm not sure what's the best way to move to source build from a situation like that
[13:17] <ogra_> sil2100, should i upload before assignment (or is the dashboard just cheating me)
[13:18] <sil2100> uh, wait, the dashboard is plain wrong
[13:18] <ogra_> heh
[13:18] <ogra_> thats what i thought
[13:19] <sil2100> There's something strange going on, ugh
[13:20] <kgunn> sil2100: yep
[13:20] <kgunn> sil2100: oops silo19
[13:20] <sil2100> hmmm
[13:20] <sil2100> HmMmMmMmmMm
[13:21] <ogra_> heh
[13:21]  * ogra_ listens fascinated to the sounds sil2100 makes
[13:21] <sil2100> ogra_: so, it's back on the dashboard after a reconfigure
[13:22] <ogra_> heh, k
[13:22] <sil2100> ogra_: I guess it's safe to upload dbus now
[13:22] <sil2100> But I have NO idea what's going on, the dashboard gone crazy, the queuebot as well
[13:23] <ogra_> uploaded ...
[13:23]  * ogra_ waits
[13:30] <sil2100> kgunn: ok, looking
[13:30] <kgunn> sil2100: thanks, lemme know if i need to try something
[13:34]  * sil2100 sighs
[13:34] <sil2100> The whole source-copy experiment causes more problems then it should
[13:36] <sil2100> kgunn: ok, so what I recommend is: let's add mir to silo 19
[13:36] <sil2100> kgunn: we will do a binary copy of the last version, which should satisfy the dependencies and not require much additional testing as it should be the same as what we have in the distro, just without the ~rtm version
[13:36]  * ogra_ wonders what happened to the RTM image
[13:36] <sil2100> ogra_: oh, right, we didn't get a message
[13:37] <ogra_> https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu-rtm/14.09/ubuntu-touch/
[13:37] <ogra_> rootfs only finished 9min ago
[13:38] <ogra_> i wonder why it took so long
[13:39] <sil2100> kgunn: on the other hand, damn... we can't do this easily
[13:39] <sil2100> hmmm
[13:39] <sil2100> kgunn: would you be around to do some quick RTM testing?
[13:43] <sil2100> kgunn: there's RTM silo 011 which now has mir in it - I would like to fast-track it to ubuntu-rtm, as it is a no-change rebuild
[13:43] <sil2100> kgunn: but I would appreciate some help in making sure all still works there
[13:45] <rsalveti> ogra_: don't be blocked by my silo
[13:45] <rsalveti> still waiting tedg to review the indicator mr
[13:46] <ogra_> rsalveti, yeah, i would just have triggered a rebuild later
[13:49] <kgunn> sil2100: ack
[13:49] <kgunn> camako: hey just in case ^^ ...i'm gonna test silo11...unless you've already got it going ?
[13:50] <sil2100> kgunn: make sure that you can install it properly on the device
[13:51] <sil2100> kgunn: once mzanetti is back I'll ask him to install it alongside silo 19 if it fixes the issue
[13:51] <sil2100> Binary copies are not super compatible with source copies
[13:51] <kgunn> sil2100: ack, i don't mind doing both
[13:52] <plars> mterry: fginther is hitting that "'Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name com.canonical.UnityGreeter was not provided by any .service files" error every time in at least one place it seems now.
[13:52] <mterry> plars, alright, I'll spend some time today on it and give you a patch to try
[13:52] <plars> mterry: thanks!
[13:54] <cyphermox> sil2100: could you please assign a silo for line 8? we can move on the urfkill landing and get further testing
[13:54] <sil2100> cyphermox: ACK
[13:55] <cyphermox> sil2100: I know line 7 / ubuntu-landing-011 isn't landed, that's on purpose :)
[13:55] <imgbot> [13:55] <imgbot> [13:55] <cyphermox> AH! finally! :D
[13:55] <tedg> Are people who have things that can't land in Utopic just landing them in RTM and then planning to sync V when it opens?
[13:55] <sil2100> cyphermox: ok, but can I simply sync up packages from silo 7? :)
[13:55] <cyphermox> sil2100: yes, precisely!
[13:55] <ogra_> geez, 3h !
[13:55] <cyphermox> wait
[13:55] <cyphermox> silo 11
[13:55] <cyphermox> it's line 7, but silo 11 ;D
[13:55] <sil2100> Yeah ;)
[13:55] <sil2100> Right! My mistake
[13:56] <cjwatson> tedg: that's supposed to be strictly disallowed
[13:56] <cjwatson> I agreed with management four months ago that people wouldn't do that
[13:56] <cyphermox> awe: ^ this is why I was pushing back on your rtm-first landings
[13:56] <tedg> Hmm, okay. We just have some MRs that are too large for a beta freeze, and don't effect destkop.
[13:56] <sil2100> tedg: yeah, so every change needs to land in utopic - with the recommendation to land it first in utopic
[13:57] <cjwatson> I don't see why the requirements for utopic at this point should be stricter than the requirements for ubuntu-rtm just before shipping to a customer
[13:57] <sil2100> tedg: for what packages? Aren't they part of the standing FFe?
[13:57] <tedg> sil2100, indicator-sound
[13:57] <cyphermox> awe: but as soon as you're done with the testing on silo 11, we can land IT, and then proceed to finish landing the RTM silo
[13:57] <sil2100> Ah
[13:57] <cjwatson> and if they aren't in desktop then I shouldn't have thought it would be an issue
[13:58] <tedg> cjwatson, They're in desktop, but the feature doesn't effect desktop. i.e. only the phone profiles.
[13:58] <tedg> But from a code-change perspective, code is changing.
[13:58] <sil2100> cyphermox: once silo 11 is built, let's push the build button on the rtm silo 24 - it will then pull in the binaries
[13:58] <cjwatson> tedg: Doesn't sound like it should be an issue from a utopic release point of view then
[13:59] <ogra_> sil2100, dbus is ready in utopic 002
[13:59] <tedg> Hmm, okay.
[14:00] <sil2100> ogra_: ok, let's build the ubuntu-touch-session then!
[14:00] <mterry> plars, fginther: can you test this for me?  http://paste.ubuntu.com/8433042/
[14:00] <ogra_> yeah :)
[14:00] <mterry> plars, fginther: that's a new unlock-device script, with retries
[14:00] <sil2100> ogra_: build pressed, let's wait for those to build and then press the build button on the rtm silo
[14:01] <ogra_> yeah
[14:01] <plars> mterry: just starting a meeting, but I'm sure we can look at it right after
[14:01] <fginther> mterry, I'll check it out shortly, thanks
[14:01] <sil2100> ogra_: ah, could you maybe push the dbus version you want for RTM to the rtm silo now? Since I guess it'll need to build first anyway
[14:01] <ogra_> sil2100, that should still be in there ... unless you wipes the silo
[14:01]  * ogra_ checks
[14:02] <ogra_> sil2100, yeah, its in
[14:02] <ogra_> and build and all
[14:04] <sil2100> ogra_: ok, now, so that I know completely what's up
[14:04] <sil2100> ogra_: soooo
[14:04] <sil2100> ogra_: is ubuntu-touch-session depping on dbus and using it during build time?
[14:05] <ogra_> i dont think so
[14:05] <ogra_> nope, isnt
[14:05] <ogra_> (and shouldnt)
[14:06] <sil2100> ogra_: ok, so we can do a standard binary copy sync of ubuntu-touch-session to the RTM silo, right? ;)
[14:07] <davmor2> sil2100, cwayne: okay that is all the scopes and all the apps tried and everything is opening, I'm going to reboot a few times and make sure it still work but then I would say this custom tarball is good
[14:07] <ogra_> sil2100, yup, that should be fine
[14:07] <sil2100> davmor2: \o/
[14:07] <sil2100> davmor2: yaay
[14:07] <sil2100> ogra_: any news on a new device tarball?
[14:08] <ogra_> sil2100, havent heard anything from john-mcaleely
[14:13] <nik90> rpadovani: got a sec to review https://code.launchpad.net/~nik90/ubuntu-clock-app/restore-back-multimode/+merge/236113 ?
[14:14] <mzanetti> sil2100: I'm back
[14:14] <rpadovani> nik90, on it
[14:14] <nik90> rpadovani: thnx.
[14:14] <mzanetti> sil2100: from the scrollback I read I should install RTM silo 6 + 19 and test, correct?
[14:17] <rpadovani> nik90, lgtm on desktop
[14:17] <nik90> rpadovani: It is a very minor change and shouldn't cause any regressions.
[14:18] <rpadovani> nik90, indeed, topapproved
[14:21] <sil2100> mzanetti: no no, RTM silo 11 and 19
[14:22] <mzanetti> sil2100: ack
[14:22] <sil2100> mzanetti: silo 11 has the mir with correct version, and 19 is your silo :)
[14:22] <mzanetti> sil2100: right... had ubuntu page open
[14:22] <mzanetti> awesomes. will test now
[14:25] <sil2100> Thanks!
[14:28] <ogra_> sigh
[14:28] <ogra_> why doesnt dbus work now :(
[14:34] <sil2100> Friday
[14:34] <sil2100> Nothing works on Friday
[14:35] <sil2100> I'm analysing a bug in CI Train and I still can't find what's up
[14:36] <davmor2> sil2100: cwayne: right 6 reboots and everything is still opening \o/
[14:37] <cwayne> woo
[14:37] <cwayne> davmor2: so good to go?
[14:37] <davmor2> cwayne: over to you to negotiate with sil2100 as to when to run it :)
[14:38] <mzanetti> sil2100: kgunn: so combined with silo 11, our silo 19 installs fine again. running the test plan now to see if it works fine too
[14:38] <lool> cyphermox: have tested NM; got a position fix, and saw almost the same wifis as before (well one more actually)
[14:39] <cyphermox> working on it
[14:41] <sil2100> mzanetti: that's excellent news
[14:41] <sil2100> kgunn: did you also test the rtm silo 11 by itself? :)
[14:42] <sil2100> kgunn: since if all seems ok, I'll publish it (as it is a no-change rebuild in fact)
[14:42] <ogra_> sil2100, bah, silly error ...
[14:42]  * ogra_ hits build again on the 002 utopic silo
[14:42] <sil2100> davmor2, cwayne: I guess it would be fine to push it now :)
[14:43] <sil2100> ogra_: oh? :)
[14:43] <ogra_> yeah, there was code that emptied the file we want to read :P
[14:43] <ogra_> forgot to rip that out
[14:44] <davmor2> sil2100: so when this lands that would mean location works in webapps, and the webapps open 2 kinda criticals out the way, do you want me to run a test on the resulting image and see what I think of it?
[14:45] <cyphermox> lool: yeah, looks good
[14:46] <sil2100> davmor2: yeah, but would you be able to do the full promotion suite today still?
[14:46] <davmor2> sil2100: yeap
[14:47] <sil2100> davmor2: excellent! If this image is ok, then it would be really a big milestone
[14:47] <sil2100> davmor2: imagine!
[14:47] <sil2100> davmor2: TWO promotions in ONE WEEK
[14:47] <sil2100> :O
[14:47] <davmor2> sil2100: but now you gone and jynxed it of course :P
[14:48] <sil2100> Sorry, it's Friday anyway!
[14:48] <ogra_> you guys assume i'll just promote it ... i might queue it up for monday :P
[14:50] <kgunn> sil2100: one sec...i'm so swamped
[14:50] <kgunn> otp
[14:50] <kgunn> but setting it up
[14:52] <lool> cyphermox: (I had updated the spreadsheet already, so QA is next I guess)
[14:53] <cwayne> sil2100: okay then, pushing :)
[14:54] <sil2100> davmor2: once that image is available, please test it with all your promotion-wise might
[14:55] <davmor2> cwayne: are we nearly there yet?
[14:55] <cwayne> davmor2: my part's done, not sure how long it takes system-image to do it
[14:56] <davmor2> cwayne: hahahaha
[14:56] <cwayne> wut
[14:58] <nik90> sil2100: are you thinking about promoting an image that is already built or about to be built?
[14:59] <sil2100> nik90: yes, but only for RTM - we plan on checking out the new ubuntu-rtm image that will be available soon
[15:00] <sil2100> nik90: in utopic we still are waiting for something to land
[15:00] <nik90> sil2100: I think balloons will have released  a new clock to the store now (or very soon). I figured may be that could be part of the promoted image
[15:00] <nik90> sil2100: but if it is already being built, I missed it which is fine since it will come as an update through the store anyway
[15:01] <sil2100> Oh, I think it won't be picked up sadly, since the new image will only have a new custom tarball... so it will only have the contents from today's noon ;/
[15:01] <sil2100> Yeah
[15:01] <nik90> sil2100: no worries :)
[15:06] <mzanetti> sil2100: ok... silo19 testplan succeeded
[15:06] <mzanetti> sil2100: so you might want to release 11 before the QA signoff of 19
[15:06] <sil2100> mzanetti: excellent, now just a quick confirmation from kgunn I need, after which I'll release 11
[15:06] <mzanetti> ok
[15:07] <sil2100> And then we ask for sign-off of 19
[15:07] <mzanetti> sil2100: thanks man!
[15:07] <sil2100> mzanetti: sorry for the trouble! It was a very nasty race condition that we didn't suspect
[15:07] <mzanetti> sil2100: no worries at all
[15:07] <mzanetti> we got it resolved, that's all that matters :)
[15:07] <sil2100> btw. I think I heard that unity8 might be unblocked from utopic soon
[15:08] <sil2100> mzanetti: actually yaay, I see the qtcreator-plugin-ubuntu autopkgtest passing now
[15:08] <mzanetti> purrfect
[15:08] <mzanetti> by new we have accumulated 20 approved branches again thoug :D
[15:09] <sil2100> cjwatson: thanks for removing mesa from -proposed!
[15:09] <cjwatson> np
[15:10] <balloons> plars, I think https://code.launchpad.net/~nskaggs/ubuntu-test-cases/increase-ap-timeout/+merge/235706 can land. everyone is a-ok with it
[15:11] <plars> balloons: yes, I'm going to push that in today
[15:11] <balloons> plars, awesome thanks
[15:13] <ogra_> sil2100, ubuntu-touch-session is ready for syncing into rtm silo 008
[15:14] <sil2100> ogra_: ACK! Let me do that, as it requires a small hack
[15:15] <sil2100> ogra_: ok, should be happening now :)
[15:16] <ogra_> thanks!!
[15:17] <ogra_> davmor2, so in #69 my location service is supposed to work ? (it doesnt)
[15:18] <davmor2> ogra_: then there is a problem with you phone is all I can think
[15:19] <ogra_> so it wont work on upgrades ?
[15:22] <ogra_> aha
[15:22] <ogra_> now it works ... about 800m off thouh
[15:22] <ogra_> but i'm indoors
[15:23] <ogra_> re-running the wizard seems to have been needed
[15:23] <ogra_> oh
[15:23] <ogra_> now it just jumped 800m in the other direction
[15:23] <ogra_> funny
[15:23] <sil2100> Location (tm)
[15:23] <ogra_> yeah
[15:23] <ogra_> it jumps around all the time
[15:24] <davmor2> ogra_: yay
[15:24] <ogra_> aah !
[15:24] <ogra_> now it moved about 2km east
[15:24] <sil2100> Think of it this way
[15:24] <davmor2> ogra_: have you just run ota's on that device?
[15:24] <sil2100> Maybe it's YOU who is jumping all the time?
[15:24] <ogra_> davmor2, since partitioning, yes
[15:25] <ogra_> sil2100, oh my ... that is the reason why my cats didnt return yet ... the house must be jumping with me
[15:25] <davmor2> ogra_: that is why it hasn't worked then you had to agree to the terms :)  good to know anyway :)
[15:25] <ogra_> davmor2, oh, i did that a few times (re-enabling the wizard)
[15:25] <ogra_> every time someone said "location should work now" :)
[15:26] <dbarth> o/ trainguards for a silo at line 98
[15:26] <dbarth> thanks
[15:26] <davmor2> ogra_: well now it works so stop with the negativity now :P
[15:26] <ogra_> right
[15:26] <ogra_> i get 'a' location
[15:26] <ogra_> :)
[15:26] <ogra_> lol
[15:26] <sil2100> dbarth: aye!
[15:26] <ogra_> with the exception of the here map
[15:27] <davmor2> ogra_: you didn't say you wanted an accurate location :P
[15:27] <ogra_> damn ... yeah, you are right, i was never that specific
[15:28] <ogra_> oh, wow ...
[15:28] <ogra_> it just jumped about 100m close
[15:30] <kgunn> sil2100: i promise i haven't forgoten...just running ap test
[15:30] <kgunn> takes forever seemingly
[15:31]  * ogra_ wonders what kgunn is testing there ...
[15:31] <ogra_> did bzoltan talk you into landing UITK for him ?
[15:31] <kgunn> silo11
[15:31] <kgunn> rtm
[15:31] <kgunn> mir
[15:31] <ogra_> ah :=
[15:31] <ogra_> :)
[15:31] <kgunn> needed to un-ass rtmsilo19
[15:32] <bzoltan> me, who, what, when? It was not me...
[15:32] <ogra_> bzoltan, just joking :)
[15:32] <bzoltan> ogra_: Are you sure?
[15:32] <kgunn> ogra_: never jokes
[15:32] <kgunn> he's super serious guy
[15:33] <bzoltan> kgunn:  and when he does it hurts more
[15:33] <sil2100> Just wanted kgunn to do a quick confirmation that the mir there is good :)
[15:33] <kgunn> :D
[15:33] <ogra_> lol
[15:37] <sil2100> kgunn: just a quick look is good, poke me once it looks more or less ok ;)
[15:38] <kgunn> sil2100: this AP has to be close...and then i'll do one particular manual test that's the best at finding stuff...it'll take only 2 minutes...then i ping you
[15:39] <sil2100> Yaay!
[15:40] <ogra_> davmor2, brendand would you let silo rtm 008 in without QA signoff ? (bugfix, i tested on bot distros)
[15:40] <davmor2> ogra_: the bots get a distro of their own I don't think that is on ;)
[15:41] <davmor2> ogra_: up to brendand I'm looking at the image :)
[15:41] <ogra_> shhh, dont tell them ...
[15:41] <ogra_> queuebott is excited enough for the day ... thanks to all the cleaning it did
[15:44] <kgunn> sil2100: rtm11 mir all good
[15:44] <sil2100> \o/
[15:44] <brendand> ogra_, are we promoting the current image or planning to promote the next one?
[15:44] <ogra_> no idea
[15:44] <brendand> davmor2, ?
[15:44] <ogra_> brendand, not up to me
[15:45] <davmor2> brendand: looking to promote this one
[15:45] <kgunn> sil2100: now i put silo19 on top ?
[15:45] <sil2100> kgunn, mzanetti: silo 11 published, once it appears in -proposed I guess we can switch silo 19 to needs QA Testing
[15:45] <sil2100> kgunn: since mzanetti already tested 19 with 11
[15:45] <brendand> davmor2, it fixes the background issue?
[15:45] <mzanetti> sil2100: cheers
[15:45] <kgunn> cool
[15:45] <sil2100> kgunn: so all we need is a QA sign-off of silo 19
[15:45] <kgunn> thanks guys
[15:45] <sil2100> kgunn: thanks!
[15:46] <davmor2> brendand: not tried that yet but it fixes a whole heap of other issues so we can debate the background once we see if it fixes more than it breaks
[15:47] <AlbertA2> trainguards: landing-027 is ready to publish
[15:47] <AlbertA2> trainguards: can I get a silo for line 41?
[15:51] <brendand> davmor2, yeah and it's already in #2 so not a regression
[15:52] <brendand> davmor2, and i just talked to kenvandine and it's not looking likely for today
[15:53] <brendand> davmor2, so question - i suppose if you find a problem with this one it's highly unlikely the next one will be promotable either?
[15:53] <sil2100> AlbertA2: hey! Let me take a look
[15:53] <davmor2> if there is a big problem in this one this one won't be promotable :)
[15:54] <sil2100> AlbertA2: oh!
[15:54] <sil2100> AlbertA2: is that the fix for our media-hub unity8 issues?!
[15:54] <AlbertA2> sil2100: sure is :)
[15:54] <AlbertA2> well the hangs at least....
[15:54] <sil2100> \o/
[15:54] <sil2100> You're my hero
[15:55] <davmor2> AlbertA: don't believe him he says that to everyone ;)
[15:55] <AlbertA2> davmor2: oh man...I was ready to believe it... http://imgur.com/gallery/ncSWF9D
[15:56] <sil2100> AlbertA2: can I prepare a silo for RTM for that fix?
[15:56] <AlbertA2> jhodapp: ^ I think we need sync more packages than just media-hub due to the previous revert in rtm
[15:57] <sil2100> Yeah, we can also do a sync of dbus-cpp and qtubuntu-media
[15:57] <sil2100> But all of those can be done with syncs
[15:58] <AlbertA2> sil2100: ok, jhodapp: ^ you ok with that?
[16:02] <fginther> plars, mterry, does the gdb call here need to be done with sudo? http://paste.ubuntu.com/8433042/
[16:03] <fginther> plars, mterry, sorry, 'adb call'
[16:03] <fginther> so "sudo gdbus call --session ..."
[16:04] <ogra_> fginther, we dont on the normal smoketests
[16:04] <awe> sil2100, could you do a manual binary sync of utopic silo-007 to rtm silo-024?
[16:05] <sil2100> awe: one moment, will look after the meeting
[16:05] <awe> thanks
[16:05] <fginther> ogra_, thanks, just wanted to check
[16:19] <sil2100> jhodapp, AlbertA2: ok, I'll prepare an RTM silo then - in case you think otherwise, just give a ping to the trainguards about that
[16:20] <AlbertA2> sil2100: well so there's a bit of a mess...
[16:21] <AlbertA2> so I guess we want qtubuntu-media 0.7.1+14.10.20140923.2-0ubuntu1 to be in rtm and utopic
[16:22] <sil2100> Ah, right, there was a landing in RTM...
[16:22] <AlbertA2> sil2100: there's a sync from ubuntu-rtm to utopic in the spreadsheet... line 43
[16:22] <sil2100> Confusing indeed!
[16:22] <AlbertA2> so I'm confused
[16:22] <sil2100> Ok, I guess we don't need to change anything in qtubuntu-media I think
[16:22] <sil2100> hm, or wait
[16:23] <sil2100> We might need to re-build qtubuntu-media with a no change rebuild
[16:23]  * sil2100 sighs
[16:27] <robru> oh dear god the spreadsheet hit 100 rows
[16:28] <fginther> mterry, I tried to hack in those unlock changes and it didn't solve the problem: http://s-jenkins.ubuntu-ci:8080/job/generic-deb-autopilot-runner-mako-maas/8/console
[16:28] <fginther> mterry, I think something else is going on here, attempting some device debugging
[16:28] <robru> sil2100: ok so I was looking at the scrollback, that's quite strange. queuebot is spamming from the silos plugin (eg the json-reading plugin). I was expecting the bug to arise from the spreadsheet-reading plugin, which is the one that had issues last time.
[16:30] <robru> sil2100: Laney: so the two offending silos that were causing the queuebot flood are no longer in use, so I have no way to look at them to determine what might have caused this. this also means it's likely the issue is over. can we briefly re-voice queuebot just to see what's up? (and if the problem isn't fixed, it'll help me to get an updated list of what
[16:30] <robru> silos are currently causing problems)
[16:31] <AlbertA2> sil2100: ah I see so yeah we need a sync of qtubuntu-media from rtm to utopic (which is line 43) and then a sync of media-hub from utopic to rm
[16:31] <Laney> okay!
[16:33] <Laney> oh god the volume
[16:33] <Laney> robru: enough info?
[16:34]  * Laney assumes so :)
[16:35] <robru> hm
[16:36] <cjwatson> sil2100,robru: oh, is now a good time for you folks if I switch snakefruit's cupstream2distro checkout to trunk?
[16:36] <robru> cjwatson: nope, I didn't have time to fix copy2distro yet
[16:36] <cjwatson> ah oh
[16:36] <cjwatson> ok
[16:36] <robru> cjwatson: maybe tomorrow, I'm putting out fires today ;-)
[16:36] <robru> err, monday
[16:36] <cjwatson> fair enough, I have enough to do as well :)
[16:36] <robru> cjwatson: thanks for checking
[16:36] <cyphermox> robru: anything I can do to help with that?
[16:37] <cyphermox> (not that I'm here for very much longer though)
[16:37] <robru> cyphermox: nah it's minor, and it's not urgent since snakefruit is working, but I broke trunk so I need to fix trunk so it can be redeployed
[16:37] <cyphermox> alright
[16:37] <robru> cyphermox: thanks.
[16:39] <AlbertA2> trainguards: can I get a silo for line 30?
[16:40] <robru> AlbertA2: ok you got utopic 9
[16:43] <robru> hm, queuebot problem seems restricted to rtm! strange!
[16:47] <jhodapp> AlbertA2: exactly right
[16:48] <mterry> fginther, yes, the adb call needs sudo (to set environment correctly).  And bummer about it not fixing it....  I could have sworn that would
[16:52] <davmor2> sil2100: hmmm infographics seems broken only displays No data sources available but I know there should be sms send and received and calls and time more than a minute :(
[16:54] <dbarth> trainguards can i get a silo for line 72?
[16:55] <sil2100> davmor2: could you check if that was the case in the last promoted image? Or get someone else confirm?
[16:56] <davmor2> jibel: ^ do you see infographics?
[16:56] <ogra_> davmor2, i did yesterady for sure
[16:56] <jibel> davmor2, I do, I see "no data available" if I disable infographics in system-settings
[16:56] <ogra_> (on proposed though ... but it is likely that wasnt different on the last promoted one)
[16:57] <jibel> otherwise it displays something
[16:57] <ogra_> yeah, it sdoesnt in 69
[16:57] <dbarth> sil2100: hey; do you have questions about my silo requests?
[16:57] <davmor2> sil2100: ^ it got broken then
[16:58] <dbarth> the oxide one is not ready, i'm just testing the build right now, but the request with webrowser-app branches is ready
[16:58] <robru> dbarth: please set the distribution in column H
[16:58] <AlbertA2> sil2100: so yeah go ahead with the rtm silo sync for media-hub...dbus-cpp will be sync'ed with rtm landing-001...so I'll just wait for that to land before testing...
[16:58] <dbarth> robru: ah sorry, sure
[16:59] <robru> dbarth: ok you got utopic 14
[16:59] <dbarth> nice, thanks!
[17:00] <robru> dbarth: you're welcome
[17:00] <dbarth> robru: btw, could you print the ppa shortcut in the dashboard main view?
[17:00] <dbarth> robru: i find myself opening the ppa link just to get that copy/paste
[17:01] <robru> dbarth: copy paste of what?
[17:01] <dbarth> the ppa: line to add the repo on a device
[17:01] <dbarth> citrain doesn't work on rtm afaict
[17:01] <robru> dbarth: oh, the citrain script just got fixed yesterday. so now you can 'citrain device-upgrade N password'
[17:02] <dbarth> awesome!
[17:03] <robru> dbarth: it's in utopic but if you're using trusty you'll have to wait for the PPA to get updated, ogra said he'd do that today
[17:03] <dbarth> yeah i'm on trusty, but that's fine i'll update on monday
[17:03] <dbarth> let's get this silo to build now
[17:05] <sil2100> AlbertA2: ok ;)
[17:05] <sil2100> AlbertA2: let me assign one then
[17:08] <dbarth> robru, another question: we have oxide 1.2.4 ready for landing to utopic now
[17:08] <dbarth> it's available in the security-proposed ppa, managed by jdstrand
[17:08] <sil2100> dbarth: robru will be your guide for the standard train things now :)
[17:08] <jhodapp> AlbertA2: are you syncing tvoss' MPRIS landings again? media-hub, dbus-cpp, qtubuntu-media to rtm?
[17:08] <dbarth> sil2100: yup, that's cool; have a good week-end
[17:09] <AlbertA2> jhodapp: no, qtubuntu-media is already the latest version in rtm
[17:09]  * jdstrand is happy to copy the binaries to a ppa or utopic-proposed itself-- just tell me what to do
[17:09] <AlbertA2> jhodapp: and dbus-cpp looks like will be synced with rtm landing-001
[17:10] <jhodapp> AlbertA2: well it isn't quite there, it's the old version that doesn't include a few property type changes as well as linking against libmedia-hub-common2 and libmedia-hub-client2
[17:11] <jhodapp> AlbertA2: because those things changed with the MPRIS landing, but got backed out as well
[17:11] <AlbertA2> jhodapp: ok I'm confused again: http://people.canonical.com/~ogra/touch-image-stats/rtm/59.changes
[17:12] <jhodapp> AlbertA2: what you have said is correct except for qtubuntu-media
[17:13] <jhodapp> AlbertA2: check out the dependencies of qtubuntu-media in the latest rtm image and you'll see what I mean...media-hub1 and not media-hub2
[17:13] <robru> dbarth: sorry I didn't understand, did you need my help? sounds like you should coordnate with jdstrand
[17:14] <robru> dbarth: do you want a silo for it so QA can verify it?
[17:14] <AlbertA2> jhodapp: so rtm does not match what's on the project? did that get changed in rtm archive
[17:14] <AlbertA2> ?
[17:14] <AlbertA2> because this is confusing: https://launchpad.net/ubuntu-rtm/14.09/+source/qtubuntu-media
[17:15] <dbarth> robru: yes, i think that's the process we came up with for the last landings
[17:15] <jhodapp> AlbertA2: well qtubuntu-media in trunk links against media-hub2
[17:15] <dbarth> robru: ie, get an empty silo; bin-copy the package there and get it landed via the normal process
[17:15] <dbarth> robru: we'll got with utopic for this Friday
[17:16] <dbarth> and rtm on monday
[17:16] <robru> dbarth: ok
[17:16] <AlbertA2> jhodapp: and this says the version in rtm links against media-hub2... https://launchpadlibrarian.net/185596467/qtubuntu-media_0.7.1%2B14.10.20140923.2-0ubuntu1.dsc
[17:17] <AlbertA2> so confused...
[17:17] <robru> dbarth: ok you got utopic 16
[17:17] <jhodapp> AlbertA2: that is confusing...that was the latest build
[17:17] <robru> jdstrand: please copy oxide into utopic 16 for testing
[17:17] <jhodapp> AlbertA2: let me double check what's in trunk, one min
[17:18] <dbarth> i'll add the test plans for webbrowser-app and the container
[17:18] <jhodapp> AlbertA2: so it's media-hub2 in trunk
[17:19] <jhodapp> AlbertA2: so I'm confused then too how qtubuntu-media is working in rtm
[17:19] <jhodapp> AlbertA2: there is no media-hub2 in rtm yet
[17:20] <AlbertA2> jhodapp: right!
[17:20] <jhodapp> AlbertA2: need the landing experts in on this... robru? sil2100?
[17:21] <robru> jhodapp: what's up?
[17:22] <jhodapp> robru, we have qtubuntu-media in rtm that expects media-hub2 for runtime, but rtm only has media-hub1 right now due to the reverting of tvoss' MPRIS MR
[17:22] <jhodapp> robru, how can this be?
[17:22] <jdstrand> robru, dbarth: done
[17:22] <jhodapp> robru, then on the utopic side, we have media-hub2 but not the latest version of qtubuntu-media
[17:22] <jhodapp> robru, we need to sync these two branches now
[17:23] <robru> jhodapp: i don't know anything about media hub. if you've identified some packages that aren't in sync, please set up landing requests to sync them, I can assign those, and then you can test them
[17:24] <jhodapp> AlbertA2: what do you think? ^
[17:24] <ogra_> jhodapp, i think lool wanted to fix that today
[17:24] <jhodapp> ogra_, as in he does the work?
[17:24] <ogra_> there was a longer conversation this afternoon
[17:24] <ogra_> dunno what the outcome was ...
[17:25] <jhodapp> lool, still around?
[17:25] <ogra_> sil2100, ^^^ do you remember ?
[17:28] <AlbertA2> jhodapp: so I think just syncing media-hub and dbus-cpp will straighten it out for rtm
[17:28] <jhodapp> AlbertA2: worth a shot
[17:28] <AlbertA2> jhodapp: how it's currently working...I dunno...
[17:28] <awe> sil2100, still around?  just wondering if you could re-binary-sync ofono from ubuntu-024 to rtm-007?  Note this is the opposite from the original sync ( which was from rtm to utopic );  this is because we couldn't trigger a rebuild in the rtm silo, hence cypermox suggested trigging the rebuild utopic and asking for a re-sync
[17:29] <robru> awe wut
[17:29] <robru> awe: is this a no-change rebuild?
[17:29] <robru> awe: what was wrong with the build in the rtm silo? it should definitely work
[17:29] <awe> while testing, we discovered an ofono crash
[17:29] <robru> awe: very difficult to switch the sync directions, requires changing & reconfiguring both silos
[17:29] <awe> so the mp was updated
[17:30] <awe> robru, ok.. I only asked because cyphermox suggested
[17:30] <awe> let's wait for him to come back online, and we can try to fix the mp
[17:30] <awe> basically the version in the changelog in the mp is older than the version in the silo, so jenkins wouldn't build
[17:31] <awe> sergiusens set this up, but he's not around either
[17:33] <robru> awe: build forced: https://ci-train.ubuntu.com/job/ubuntu-rtm-landing-007-1-build/48/console
[17:33] <awe> robru, awesome!
[17:49] <davmor2> sil2100, ogra_: https://bugs.launchpad.net/ubuntu/+source/libusermetrics/+bug/1374553
[17:49]  * ogra_ confirms
[17:54] <ogra_> davmor2, seems the /var/lib/usermetrics dir doesnt exist on my device
[17:56]  * ogra_ scratches head
[17:57] <ogra_> phablet@ubuntu-phablet:~$ sudo ls /userdata/system-data/var/lib/usermetrics/
[17:57] <ogra_> usermetrics6.db
[17:57] <ogra_> the writable dir is there
[17:57] <ogra_> it is just not in the readonly side
[17:59] <AlbertA2> jhodapp: I guess qtubuntu-media needs a rebuild for rtm...
[17:59] <jhodapp> AlbertA2: yeah that's what I thought
[17:59] <AlbertA2> jhodapp: objdump -p libaalmediaplayer.so | grep media-hub
[18:00] <AlbertA2> NEEDED               libmedia-hub-client.so.1
[18:00] <AlbertA2> jhodapp: the package name is misleading
[18:00] <jhodapp> AlbertA2: media-hub's package name?
[18:01] <AlbertA2> jhodapp: no this: http://pastebin.ubuntu.com/8434616/
[18:01] <AlbertA2> it makes you think it's actually the latest version...but it's really not....
[18:02] <ogra_> davmor2, so this is a livecd-rootfs bug ...
[18:02] <ogra_> not usermetrics
[18:02] <jhodapp> AlbertA2: hmm
[18:02] <AlbertA2> jhodapp: but how did that happen though? Shouldn't the build have failed?
[18:03] <jhodapp> AlbertA2: it did, I had to change back to using the Property types of media-hub1
[18:04] <jhodapp> AlbertA2: so let me create a quick MR that puts it back to media-hub2 type
[18:04] <AlbertA2> jhodapp: so then are the binary deps missing something in qtubuntu-media
[18:04] <AlbertA2> ?
[18:04] <jhodapp> AlbertA2: perhaps, let me check that too
[18:04] <AlbertA2> jhodapp: ohhh I see...
[18:05] <AlbertA2> libmedia-hub-dev was not reverted...
[18:05] <AlbertA2> so there's a mismatch of things I guess...
[18:05] <AlbertA2> maybe...
[18:05] <jhodapp> AlbertA2: oh man, what a mess
[18:06] <AlbertA2> jhodapp: well a rebuild should straighten things out....
[18:06] <jhodapp> AlbertA2: yes, I'll have an MR for qtubuntu-media in 2 mins
[18:06] <AlbertA2> so I guess once your branch is ready we can ask to reconfigure the rtm silo to include that...and do a source build of both...
[18:06] <jhodapp> yes
[18:08] <jhodapp> AlbertA2: https://code.launchpad.net/~jhodapp/qtubuntu-media/media-hub2-types/+merge/236168
[18:08] <ogra_> davmor2, added some background to the bug
[18:14] <AlbertA2> jhodapp: cool I guess now we need to wait for rtm landing-001 for the dbus-cpp upgrade....or the build will fail...
[18:14] <jhodapp> AlbertA2: is that building right now or syncing from utopic?
[18:15] <AlbertA2> jhodapp: sync from utopic
[18:15] <AlbertA2> tvoss: ^
[18:15] <jhodapp> AlbertA2: alright nice
[18:15] <AlbertA2> tvoss|afk: ^
[18:23] <AlbertA2> jhodapp: actually it looks like the last build was September 22....maybe I'll just coordinate with him later...
[18:24] <jhodapp> AlbertA2: he won't be back for a while
[18:24] <jhodapp> AlbertA2: some time next week
[18:25] <AlbertA2> trainguards: can I have landing-026 reconfigured....we need sync of dbus-cpp and media-hub from utopic to rtm, but a branch build of qtubuntu-media as listed
[18:25] <AlbertA2> trainguards: landing-026 rtm that is
[18:56] <davmor2> ogra_: nice one :)
[18:57] <ogra_> :)
[18:57] <ogra_> fixed livecd-rootfs is already uploaded to utopic ... but sits in unapproved atm
[19:02] <robru> AlbertA2: so what's going on in that silo? media-hub package is in the ppa, built just an hour ago. you don't want to land media-hub in rtm anymore?
[19:03] <AlbertA2> robru: so this is to deal with the mess leftover when media-hub/dbus-cpp qtubuntu-media were reverted in rtm archive
[19:03] <AlbertA2> robru: qtubuntu-media needs to be rebuilt to link to the updated version of media-hub...and media-hub is using stuff from the new dbus-cpp
[19:04] <robru> AlbertA2: ok so spreadsheet row 62 reflects what you want to happen?
[19:04] <AlbertA2> robro: yes
[19:04] <AlbertA2> robru: yes
[19:04] <robru> hehe
[19:04] <robru> ok
[19:06] <robru> AlbertA2: hmmm you know i'm not actually sure if you can have an MP AND a sync request in the same silo, i'm not aware of that ever being done before. feel free to try the build but ping me if something explodes (I expect the build job will only do one or the other but not both)
[19:06] <davmor2> jdstrand: nice comment on the bug, You'll understand me not weeping I spent 2 hours testing the image to find out it was all pointless cause infographics didn't work ;)
[19:07] <AlbertA2> robru: ok if I see issues, I can ask jhodapp to land it the qtmedia bit on utopic first...
[19:07] <cwayne_> davmor2, whats up with infographics?
[19:07] <davmor2> cwayne: try it in image 69
[19:07] <robru> AlbertA2: yeah sounds reasonable
[19:08] <davmor2> cwayne: you get no data sources available because the path to the file doesn't exist or something like that :)
[19:08] <davmor2> cwayne: https://bugs.launchpad.net/ubuntu/+source/libusermetrics/+bug/1374553
[19:09] <jhodapp> AlbertA2: k
[19:10] <davmor2> cwayne: I blame you entirely just so you know, normally it's all ogra_ 's fault but he confirmed it for me, so dude you suck ;)
[19:10] <ogra_> davmor2, lol, its all stgrabers code !
[19:11] <davmor2> ogra_: I know, but it's more funny blaming cwayne :)
[19:12] <ogra_> davmor2, oh, indeed, it is definitely his fault
[19:14] <davmor2> night all catch you wednesday
[19:14] <cwayne_> davmor2, i think i saw that in yesterday's image too
[19:15] <ogra_> cwayne_, that you are to blame ?
[19:15] <awe> robru, finished testing ofono ( rtm-007 ); should we re-binary-sync the newly built version to utopic silo-024 now?
[19:16] <ogra_> cwayne_, but joking aside, that fits ... the change landed yesterday
[19:16] <cwayne_> ogra_, :)
[19:16] <robru> awe: sure
[19:17] <cwayne_> ogra_, i'm used to getting blamed for stuff, so it's ok :P
[19:17] <ogra_> heh
[19:24] <jdstrand> davmor2: it is disappointing all around. I had nice and pretty infographics on my phone and now they are gone
[19:25]  * jdstrand dogfoods and had a lot of historical data in there
[19:27] <kgunn> yo can i get a test silo for row 76
[19:27] <kgunn> trainguards ^
[19:28] <ogra_> jdstrand, its all still there
[19:28] <ogra_> no worries
[19:28]  * kgunn imagines trainguards means sil & robru have to wear vatican city guard uniforms
[19:28] <ogra_> (it wont collect new info while it is broken though)
[19:28] <jdstrand> ogra_: oh? where is it?
[19:29]  * jdstrand rereads the bug
[19:29] <ogra_> jdstrand, the mountpoint is gone
[19:29] <robru> kgunn: actually our uniform is more like the beefeaters. http://i.dailymail.co.uk/i/pix/2007/07_01/beefeaterPA0607_468x338.jpg
[19:29] <ogra_> the rw dir that would mount to it is still intact
[19:29] <jdstrand> oh, phew
[19:29] <jdstrand> I read the bug quickly and thought it would just be gone
[19:29] <ogra_> so if you create the dir like i wrote and reboot its all back
[19:29] <jdstrand> thanks for the clarification
[19:30] <ogra_> this hack of hardcoding /etc/password is an evil one :)
[19:30] <robru> kgunn: silo 16
[19:30] <ogra_> fallout wasnt unexepected .... but at lleast your UIDs wont randomly change on upgardes now
[19:34]  * jdstrand comments in the bug that data is still intact after following ogra_'s instructions
[19:34] <ogra_> oh, yeah, sorry, i could have mentioned that :)
[19:36] <jdstrand> I was probably the only who panicked
[19:36] <kgunn> thanks robru, and yeah beefeaters way more kick butt
[19:36] <jdstrand> I really like those infographics :)
[19:36] <ogra_> heh
[19:39] <robru> brb, lunch
[19:41] <AlbertA2> trainguards: ubuntu/landing-009 is ready to publish
[19:58] <nik90> ogra_: hey, on adding my sim card, I don't see any carrier being recognised automatically. This used to work the last time I tested which was about a month ago.
[20:15] <robru> AlbertA2: ready for qa signoff you mean
[20:15] <AlbertA2> robru: utopic landing-009
[20:16] <AlbertA2> robru: I have a different one in rtm in the QA queue
[20:21] <robru> oh
[20:27] <awe> robru, were you waiting for an action on my part before re-syncing utopic-024 from rtm-007?  I'd like to celebrate at least one landing before the weekend starts... ;)-
[20:36] <robru> awe: yes, you can trigger the build job on utopic24 and that will pull in the sync again
[20:37] <robru> awe: no wait
[20:37] <robru> wtf
[20:37] <robru> your landing is all messed up
[20:38] <robru> awe: ok try building now
[20:39] <awe> robru, k
[20:50] <robru> Laney: cjwatson: can somebody re-voice queuebot? I've identified the problem as a few corrupted silo files, which I've deleted, and in my local testing all seems good.
[20:55] <robru> awe: ugh, sorry about that, your build exploded. https://ci-train.ubuntu.com/job/ubuntu-landing-024-1-build/4/console i fixed some stuff in the backend, retrying
[20:57] <awe> robru, no worries... let me know if you need anything more from me
[20:57] <awe> ( besides moral support )
[21:00] <robru> awe: looks good in fact, already done. damn binary syncs are fast ;-)
[21:00] <awe> nice!
[21:00]  * awe checks
[21:01] <awe> awesome
[21:01] <awe> just need to sanity checks on this silo, then we should be good to go to publish both silos
[21:02] <robru> awe: yissss!
[21:29] <kgunn> robru: hey man, sorry to saddle you with this...not sure what the heck to do
[21:29] <kgunn> https://launchpadlibrarian.net/185863906/buildlog_ubuntu-rtm-14.09-armhf.unity8_8.00%2B14.10.20140926-0ubuntu1_MANUALDEPWAIT.txt.gz
[21:30] <kgunn> seems this dang ~rtm is being interpreted as less than
[21:30] <kgunn> on the deb dep
[21:30] <kgunn> ...do you know a way around it ?
[21:30] <kgunn> ...i'm supposing something insane like no-op commit rebuilds?
[21:30] <kgunn> at least i think sil did that earlier today
[21:34] <robru> kgunn: yes, ~rtm is "less than" on purpose, don't ask me why though, I forget
[21:35] <robru> kgunn: although ~rtm doesn't seem to enter into it? 7.90+14.10.20140918~rtm-0ubuntu1 ! >= wanted 7.91, eg, 7.90 < 7.91
[21:53] <awe> trainguards: ubuntu/landing-024 and rtm/landing-007 are both ready to publish ( ofono )
[21:59] <robru> awe: cool
[22:07] <Ursinha> robru: ^
[22:08] <robru> queuebot: ok it's time to behave!!!
[22:08] <robru> Ursinha: thanks
[22:08] <Ursinha> robru: it wasn't his fault :P
[22:08] <robru> true
[22:08] <Ursinha> robru: you're welcome
[23:02] <lool> jhodapp: I'm vaguely around
[23:03] <lool> jhodapp: but having the read the backlog, I'm not sure how this relates to me; I didn't follow the MPRIS landing or the media-hub changes
[23:04]  * lool goes in the general direction of bed now
[23:05] <ogra_> lool, it was about the qtubuntu-media stuff that was out of sync between the archive
[23:06] <ogra_> *archives
[23:06] <ogra_> iirc you and sil looked into it
[23:08] <cyphermox> robru: poke
[23:08] <cyphermox> awe: hey
[23:08] <awe> yo
[23:08] <cyphermox> oh good, I was afraid it was too late
[23:08] <awe> just writing anemail about status
[23:09] <robru> cyphermox: yo
[23:09] <cyphermox> it's past midnight here, sorry I didn't come back before, but dinner took a long while :)
[23:09] <awe> cyphermox, ofono silos landed
[23:09] <awe> urfkill didn't
[23:09] <cyphermox> ok
[23:09] <cyphermox> I saw backlog
[23:09] <awe> hehe
[23:09] <cyphermox> you might have to delete packages from the rtm silo before you can copy the magain
[23:10] <awe> I don't think we need to copy again
[23:10] <awe> they both published
[23:10] <awe> anyways, I'm writing an email about the urfkill landing
[23:11] <awe> the hybris code doesn't always result in a working wlan0 device after boot
[23:11] <awe> and doesn't return any errors that I can see to urfkill
[23:11] <awe> so abeato has some investigation to do on Mon
[23:11] <awe> I know you'll be traveling, so we'll make a go/no-go decision in your absence, but I figured it was better to wait
[23:11] <cyphermox> oh, so it's in the ppa but the hybris stuff is not working?
[23:12] <awe> it doesn
[23:12] <awe> 't work reliably
[23:12] <cyphermox> awe: I may be able to chime in every once in a while, based on being in an airport
[23:12] <awe> 2-3 failures out of 10 reboot
[23:12] <awe> s
[23:12] <cyphermox> ok
[23:12] <cyphermox> not great, indeed
[23:12] <awe> nope
[23:12] <cyphermox> are you sure it's that and not the indicator?
[23:12] <awe> yup
[23:12] <cyphermox> alright
[23:13] <awe> iwconfig wlan0 says "no such device"
[23:13] <cyphermox> but
[23:13] <cyphermox> shouldn't it be sufficient to keep the scripts as they were? since urfkill will explicitly shut down a device as it starts if it's marked to be off
[23:13] <cyphermox> that does get you a short period of time where the device might be on, but still...
[23:14] <cyphermox> while it's to regulatory-compliant, we already weren't ;)
[23:14] <awe> I'm not sure what're your proposing
[23:14] <awe> we need to use hybris to control wifi cause the rfkill part is broken in the driver
[23:15] <cyphermox> yes
[23:15] <awe> and abeato told me leaving the scripts around interferes with hybris
[23:15] <awe> script
[23:15] <cyphermox> meh
[23:15] <awe> anyways, I'll discuss with him
[23:15] <cyphermox> I would think it only brings upthe device
[23:15] <cyphermox> since you're doing something fundamentally similar at boot in urfkill.conf; it's just in an upstart job instead of in the set_* script
[23:16] <awe> let's see what abeato wants to do
[23:16] <cyphermox> also, it was pretty stable to me, though I probably didn't reboot 20 times
[23:16] <awe> the setprop from the urfkill jobs moves some where else
[23:16] <cyphermox> right
[23:16] <awe> that just toggles urfkill to use hybris
[23:16] <awe> the status script in /system/bin
[23:16] <awe> brings up the device
[23:17] <awe> with it gone
[23:17] <awe> and only hybris controlling wifi
[23:17] <cyphermox> yes... and the upstart job in urfkill brings up the wifi
[23:17] <awe> it fails to bring up the device about 15-20% of the time
[23:17] <cyphermox> if that's not in, and it's not anywhere else either...
[23:17] <awe> no, the urfkill upstart job just sets a prop
[23:17] <awe> urfkill brings up wifi
[23:17] <cyphermox> yes
[23:17] <cyphermox> let me dig in


[10:21] <asymmetric> hi, i'm having issues with configuring upstart
[10:21] <asymmetric> is anybody available to help?
[11:04] <JanC> asymmetric: better ask your question, then we can see if we can help...


[03:20] <Guest79111> hello
[03:21] <Guest79111> hello?
[03:21] <Guest79111> hi
[03:22] <Guest79111> hi@WhitePsydeLord
[03:22] <Guest79111> Can you talk to me?
[03:38] <Guest79111> hello\
[03:38] <Guest79111> \\
[04:33] <potato> hi
[07:26] <master_> hello! What is HexChat about?
[07:28] <alkisg> Chatting in order to get support for ubuntu mate
[07:30] <master_> Okay. Thanks
[07:36] <alkisg> np
[07:47] <master_> how do I get new themes of ubuntu other than the installed ones
[07:50] <alkisg> Now it's weekend, you might need to stay on for hours to see an answer to that :)
[07:55] <diogenes_> master_, https://www.opendesktop.org/s/Mate
[07:55] <master_> no problem
[11:11] <mate|78315> ehem
[11:30] <KingParrot> Hello room
[11:31] <KingParrot> Mexican music is boring to night.
[11:32] <KingParrot> Has anyone here attempted to install profilemanager 1.0 in ubuntuMATE?
[11:35] <KingParrot> yeah blah blah
[11:39] <KingParrot> I've already disabled updates on it
[11:45] <Khan> I'm having trouble with a Lenovo V110-15ISK, the thing can't boot when the ODD is installed, or when I put an HDD in its place
[11:45] <Khan> tried to search for BIOS firmware update, but Lenovo says they don't support Linux :'(
[11:57] <Guest50672> Egun on. ¿Qué programa puedo utilizar en Ubuntu para trabajar con dibujos o planos creados con Autocad?
[14:11] <m12> hi
[18:00] <funki-kingston> Hi ! I have a problem with the choise of my graphic card. I changed it to use my processor as graphic card, but my ubunto dont boot corectly now so i want to change it back but i cant remember how. Coold you help me ?
[18:03] <diogenes_> how it doesn't boot correctly?
[18:06] <funki-kingston> no, the recovery mod work but the normal mod show a black screen after the loading of ubuntu
[18:07] <diogenes_> when you reach black screen, run: sudo rm /etc/X11/xorg.conf
[18:08] <diogenes_> reboot again
[18:09] <funki-kingston> ok i will try this
[18:10] <funki-kingston> and to you know how i can put my real graphic card in work ?
[18:10] <funki-kingston> actually this is my proc who is on this work
[18:11] <diogenes_> first boot then we'll see
[18:11] <funki-kingston> ok
[18:18] <funki-kingston> I cant right anithing on the starting black screen
[18:19] <diogenes_> press alt+ctrl+f1 or 2 3
[18:20] <funki-kingston> ok
[18:20] <diogenes_> write your login and passwd
[18:20] <diogenes_> then: sudo rm /etc/X11/xorg.conf
[18:30] <funki-kingston> Hi everyone ! How can i change the graphic card who are runing ? I change it accidentaly to use my proc, but linux dont boot corectly now i have to use noacpi and no modeset tu boot it
[18:36] <funki-kingston> i use noacpe and nomodeset on the boot preset by using 'e'
[18:55] <alkisg> funki-kingston: what's the output of this command? sudo ubuntu-drivers devices
[18:57] <funki-kingston> https://thepasteb.in/p/P1hvmJGXw2wTl
[19:02] <KingParrot> poout jelly bweans rub
[21:05] <funki-kingston> hi ! did somebody succes to install texmaker on ubuntu 18.0 mate
[21:05] <funki-kingston> ?
[21:46] <KingParrot> Please do not work on this page or on the extension pages, any work will be overwritten by a bot.
[21:48] <KingParrot> some weeks extra for IceCat to build.
[21:51] <KingParrot> someone might build Sandboxie for linux deb and rpm.
[21:53] <KingParrot> SandboxieInstall32-376.exe
[21:54] <KingParrot> SandboxieInstall32-376.exe
[21:57] <KingParrot> Maxthon V<IP_ADDRESS> Beta
[21:58] <mate|51442> hello
[21:58] <KingParrot> I used the word Maxthon in a firefox irc cat.
[22:01] <KingParrot> Powered by Google TranslateTranslate
[22:07] <KingParrot> It don't sound like Cameyo is to great.
[22:14] <KingParrot> Cameyo Creates a Portable Version of Just About Any Program
[22:15] <KingParrot> o nice chat room
[22:19] <KingParrot> Free Trial
[22:27] <KingParrot> Falkon Browser
[22:28] <KingParrot> u can type it
[23:53] <KingParrot> What version of MATE is the best


[10:03] <xivulon> hi all
[10:03] <xivulon> I have to give a talk/stand at next LugRadio
[10:03] <xivulon> I am the author of wubi
[10:03] <xivulon> and would like to coordinate the efforts is possible
[10:03] <xivulon> is anyone here involved with LugRadio?
[10:04] <xivulon> I believe John Levin will be attending
[11:23] <xivulon> got disconnetcted


[07:17] <bzoltan> mcphail: doung user space stuff as root is a very-very-very bad idea in general.
[09:15] <mcphail> bzoltan: indeed
[09:33] <bzoltan> mcphail: we will add a user check to prevent such problems. Anyhow... fixing a messed up environment is hardly possible. I would remove all containers and all user space Qt config what the IDE created ... or at least do a massive chwon -R on the ~
[09:39] <mcphail> bzoltan: I wish people would stop postinf advice to run stuff as root if they lack permissions. So many gullible people trust Google results far too much
[09:41] <bzoltan> mcphail: True that
[15:51] <renato__> popey, bug fixed: https://code.launchpad.net/~renatofilho/ubuntu-calculator-app/new-snappy/+merge/310663
[15:51] <renato__> popey, I found a workaround, is working now
[15:51] <renato__> popey, could you review this?
[15:52] <renato__> popey, I will publish a snap package into the store as soon as it get merged
[15:52] <popey> looking
[15:56] <popey> renato__: i can't make it work...
[15:56] <popey> it says I need to install ubuntu-app-platform and connect them
[15:57] <popey> i do that, and it still complains
[15:57] <popey> http://paste.ubuntu.com/23461569/
[15:58] <renato__> popey, ok this is trick :D
[15:58] <renato__> popey, remove the app: snap remove ubuntu-calculator-app
[15:58] <renato__> popey, then install it again
[15:58] <renato__> popey, before run the app connect the interfaces with
[15:59] <renato__> popey, snap connect ubuntu-calculator-app:platform ubuntu-app-platform:platform
[15:59] <renato__> popey, then you can run the app
[15:59] <popey> ok
[15:59] <popey> that worked
[15:59] <popey> that's dodgy :)
[15:59] <renato__> popey, I think this is a bug on snapd
[16:00] <popey> yay, works
[16:00] <renato__> great
[16:00] <popey> approved
[16:00] <renato__> thanks. That get merged automatically or do I need to merge it?
[16:01] <popey> should merge I think
[18:48] <renato__> popey, cold you give me permission for upload snaps for calculator?
[19:46] <popey> renato__: hm, how do I do that?
[19:48] <renato__> popey, Not sure :D. Are you able to upload packages? could you upload these packages? https://launchpad.net/~phablet-team/+snap/ubuntu-calculator-app
[19:48] <popey> try the private link i just sent you
[19:49] <popey> if it doesn't work I can punch in your email address and invite you


[02:12] <micahg> cjwatson: for gnash, youtube worked, some other sites don't but I think this is the same with the current version, so I'm uploading the patch you gave me
[02:17] <micahg> cjwatson: I'm subscribed and will keep an eye  out for any issues
[06:31] <kovid> whois kovid
[07:07] <dholbach> good morning
[09:11] <thelinuxer> hi guys, I have a question about version numbering (that version we put in the change log) when I am building from a mercurial repo. How should it be written ?
[09:14] <geser> is the mercurial revision number monotonic incrementing?
[09:14] <thelinuxer> geser: can u know from here ? http://hg.atheme.org/users/desowin/gdigi/
[09:15] <thelinuxer> i have little knowledge of mercurial
[09:16] <chrisccoulson> thelinuxer, look at the version number i use for firefox nightlies (which come from mercurial) ;)
[09:17] <thelinuxer> chrisccoulson: ok will check it out
[09:17] <thelinuxer> i just want to know if there is some kind of standard when building packages from repos in general
[09:18] <jtaylor> it depends on the repo, e.g. with git one uses dates as the hash is random
[09:18] <jtaylor> with svn the revision number is fine
[09:19] <jtaylor> bzr too I think
[09:19] <thelinuxer> chrisccoulson: jtaylor and with hg it date + revision number from what I see ...
[09:19] <chrisccoulson> thelinuxer, eg, for "194:dec7a1546064", the "194" is the revision, which is monotonic
[09:19] <geser> thelinuxer: the only requirement is the version string has always to increase
[09:20] <chrisccoulson> so, for that revision, i would add "~hg20110829r194" (with the date coming from http://hg.atheme.org/users/desowin/gdigi/rev/dec7a1546064)
[09:21] <thelinuxer> chrisccoulson: without -ubuntu1 at the end ?
[09:21] <jtaylor> I'd add the hash to the changelog to keep the version short
[09:21] <thelinuxer> r there any tools to pull this from the repo and add the version number automatically ?
[09:22] <geser> so you can either use 0.2.0+hg20110829r194 or 0.2.1~hg20110829r194. assuming 0.2.0 is current and 0.2.1 will be next (0.2.0+hg sorts after 0.2.0; 0.2.1~hg sorts before 0.2.1)
[09:23] <geser> that's for the upstream version, append the usual -0ubuntu1 as revision
[09:23] <thelinuxer> jtaylor: geser chrisccoulson that's gr8 thanx a lot guys
[09:46] <tumbleweed> for mercurial, it's generally safe to use the "revision" number (commit count), if the source is managed in a central repo (svn-style)
[09:46] <cjwatson> micahg: *nod* fair enough, thanks
[11:06] <thelinuxer> I read here https://wiki.ubuntu.com/MOTU/Packages/REVU that uploading my new package to debian mentors is the way to go
[11:06] <thelinuxer> I find here http://mentors.debian.net/package/gdigi that the name of the uploader isn't me :D
[11:06] <thelinuxer> is this normal ?
[11:08] <Laney> someone else had already uploaded it to mentors
[11:08] <Laney> you should coordinate with that person
[11:08] <Laney> and certainly fix all of the lintian problems reported
[11:10] <thelinuxer> Laney: ok i guess it uploaded some of my stuff to this page
[11:10] <thelinuxer> currently when i use dput it says that the package is already uploaded
[11:10] <Laney> use dput -f if you have made changes
[11:11] <thelinuxer> ok will try that, thanx
[11:12] <Laney> but email the other guy and find out what he's doing
[11:12] <thelinuxer> ok will do so , thanks again
[12:33] <tumbleweed> Laney, bdrung: Should we turn launchpad DSD blacklisting into non-fatal errors in syncpackage for now? (bug 841372)
[12:35] <bdrung> tumbleweed: i think no as long as we have a way to force the sync.
[12:35] <tumbleweed> we don't. We only allow force overriding when fakesyncing
[12:36] <bdrung> hm
[12:36] <bdrung> i don't like adding workarounds
[12:37] <tumbleweed> I don't know how many packages are incorrectly blacklisted, but only archive-admins can un-blacklist them again
[12:37] <Laney> what's an auto blacklist?
[12:38] <tumbleweed> Laney: launchpad automatically blacklists syncs when the version in Ubuntu is newer than Debian, but it appears to be buggy
[12:39] <tumbleweed> http://bazaar.launchpad.net/~launchpad-pqm/launchpad/devel/view/head:/lib/lp/registry/model/distroseriesdifference.py#L760
[12:41] <Laney> how could you sync when the target has a newer version anyway?
[12:41] <tumbleweed> I think it does it to get it off the front page of +localpackagediffs
[12:42] <Laney> are we more interested in Blacklisted always?
[12:42] <tumbleweed> I haven't tried syncing a package that was ignored (DSD blacklisted) from the web interface, but it doesn't look like it'd stop me
[12:43] <Laney> always seems like it should be fatal and current a warning (require overriding)?
[12:43] <tumbleweed> yeah, maybe blacklisted always should be a hard-error, and blacklisted current should be a warning
[12:43] <tumbleweed> ^5
[12:44] <tumbleweed> ah, no the checkbox on the web interface *is* greyed out when it's blacklisted current
[12:44]  * tumbleweed wonders if it'll even let us do the sync...
[12:45] <Laney> you mean your link from the bug?
[12:45] <Laney> not greyed out here
[12:46] <tumbleweed> Laney: ah, but many are here https://launchpad.net/ubuntu/oneiric/+localpackagediffs?field.name_filter=&field.package_type=all&field.package_type-empty-marker=1
[12:47]  * Laney wonders what "Upgrade Packages" does
[12:47]  * tumbleweed too
[12:49] <Laney> the greyed ones there are all > debian AFAICS
[12:49] <Laney> I wonder why the ones that are = debian aren't greyed...
[12:49] <Laney> is this implemented by blacklisting current?
[12:51] <tumbleweed> that's a question for bigjools
[12:52] <Laney> I guess I don't care about the implementation, but versions that are the same shouldn't be available for syncing
[12:52] <Laney> wonder what happens if I do one
[12:52] <tumbleweed> I've found some of the answers to things like that by reading https://dev.launchpad.net/HelpOnActions?action=fullsearch&context=180&value=derivative+distributions
[12:52]  * Laney gets scared
[12:56] <Laney> hah, it got rejected thankfully
[12:57] <tumbleweed> I added a note about that to the bug
[12:57] <Laney> nice
[12:58] <tumbleweed> urgh, turning BLACKLISTED_CURRENT into an overrideable warning requires some refactoring
[13:41] <tumbleweed> Laney: ok, launchpad allowed me to override the BLACKLISTED_CURRENT. Committing
[13:41] <Laney> nice
[13:41] <Laney> does always work properly?
[13:42] <tumbleweed> you mean does launchpad block the sync? I don't want to test that :P
[13:44] <Laney> no, i mean clientside
[13:44] <tumbleweed> yes
[13:44] <Laney> happy days
[13:44] <Laney> so we can import sync-blacklist.txt?
[13:44] <tumbleweed> hrm, DSD comments hang around post sync
[13:45] <tumbleweed> https://launchpad.net/ubuntu/oneiric/+localpackagediffs?field.name_filter=libsdl-sound1.2&field.package_type=all
[13:45] <tumbleweed> Laney: I don't think that's worth doing until all syncing is done through syncpackage
[13:45] <tumbleweed> but yes, blacklist() is available in the API
[13:46] <Laney> i'd like to see the text file be generated from launchpad
[13:47] <tumbleweed> that's something to take up with the archive admins
[13:48] <Laney> well indeed, blacklisting is their domain
[13:48] <Laney> I am just saying that we should move things into LP as far as possible to make the syncpackage workflow go
[13:51] <cjwatson> if somebody wants to write a script that generates a suitable text file from Launchpad, I'd be happy to move the existing stuff into LP and deploy that script
[13:51] <cjwatson> I'd like to make sure that there's essentially no period of time without a blacklist though
[13:52] <Laney> do you get an interface on the website to manage blacklisting?
[13:52] <cjwatson> I think so
[13:52] <Laney> ok, that makes the tool easier
[13:52] <cjwatson> I have an "Add comment" AJAX thing
[13:52] <cjwatson> do you?
[13:53] <wgrant> Everyone gets "Add comment"
[13:53] <wgrant> Only archive admins get the three radio buttons above that.
[13:53] <cjwatson> oh yes, I was looking at the wrong bit
[13:53] <wgrant> (at least they used to be above that, but it was a while ago)
[13:53] <cjwatson> I have "Ignored: ( ) No ( ) All versions ( ) These versions"
[13:54] <wgrant> Right, that's the blacklist status.
[13:54] <cjwatson> sorry, that's ago)
[13:54] <Laney> sounds adequate
[13:54] <cjwatson> sorry, that's "Ignored: (o) No ( ) All versions ( ) These versions" but hopefully YKWIM
[13:54] <Laney> so we just need to generate sync-blacklist.txt from the blacklisted_always entries for the transitional period
[13:55] <cjwatson> I think we should probably not transfer the blacklist entries that are just because of orig mismatches
[13:55] <cjwatson> I would rather have the new auto-sync.py (which I've started, though only barely) figure that out for itself
[13:55] <cjwatson> they were always a pain to manage anyway
[13:55] <wgrant> Please file bugs for any API inadequacies you run into.
[13:56] <wgrant> eg. difficulties getting hashes and stuff.
[13:56] <tumbleweed> yeah, we all see the radio boxes, they are just read-only for non-AAs
[13:56] <cjwatson> I should be using copyPackages rather than copyPackage for mass sync, yes?
[13:57] <cjwatson> "If any of the requested copies cannot be performed, the whole operation will fail. There will be no partial changes of the destination archive." possibly slightly odd decision there
[13:57] <wgrant> cjwatson: Yes. Fewer requests, same result.
[13:57] <wgrant> Erm. It still says that?
[13:57] <wgrant> That hasn't been the case for months :(
[13:57] <cjwatson> yes.  https://launchpad.net/+apidoc/devel.html
[13:58] <wgrant> It creates a separate job for each copy now. The only checks performed up-front are permissions.
[13:58] <cjwatson> OK, good - that would be a recipe for irritation
[13:58] <wgrant> Atomicity is useful sometimes.
[13:58] <wgrant> But not for autosyncs.
[13:58] <cjwatson> quite.
[13:58] <tumbleweed> cjwatson: how do you plan to handle sync-request bug closing? the only way to tell if the sync was successful is to wait for the mail
[13:59] <cjwatson> tumbleweed: that seems not much worse than bugs being closed on source upload before we know if it built
[13:59] <wgrant> We'll be processing copies much more frequently in the next week or so.
[13:59] <wgrant> Currently they're done every 5 minutes along with lots of other jobs. I think that may be moving up to minutely.
[14:00] <tumbleweed> cjwatson: ah, suppose so
[14:00] <cjwatson> I think what I'd like to see is a bugs parameter on copyPackage so that LP can close those bugs if the copy succeeds
[14:00] <cjwatson> for autosyncs I don't care
[14:00] <wgrant> That sounds reasonable.
[14:00] <wgrant> cjwatson: You've not filed the copyPackages documentation issue?
[14:01] <cjwatson> no, can do now
[14:01]  * wgrant is already there.
[14:01] <cjwatson> OK.  I'll file one for copyPackage bugs
[14:01] <wgrant> Thanks.
[14:02] <wgrant> Changelog bug closing just needs one last fix. And announcement emails should already be fixed... no more issues there?
[14:03] <wgrant> Bug #841842
[14:05] <tumbleweed> wgrant: attribution for sponsorship, and came across a problem with the auto-blacklisting on the weekend,
[14:05] <wgrant> Yeah, I saw those. I mean with announcements.
[14:05] <wgrant> Since there have been a few issues there :)
[14:06] <tumbleweed> I think NEW didn't generate announcemets (there's a bug filed)
[14:06] <wgrant> Indeed.
[14:08] <thelinuxer> a quick questin. should i add a project on launchpad for the package I am builing ? as I doing some changes to it too...
[14:08] <Laney> tumbleweed: What was that bug you filed about the DSD API?
[14:08] <Laney> I don't see a way to get the source package name from a dsd object
[14:08] <Laney> thelinuxer: no need to do that
[14:09] <tumbleweed> Laney: that querying blacklisting was needlesly hard (had to separatly query for CURRENT and ALWAYS and comments)
[14:09] <Laney> ah
[14:09] <cjwatson> wgrant: bug 841849 - hope that's clear enough
[14:09] <thelinuxer> Laney: i need some place for my code, at least until they accept my patch upstream. am i right ?
[14:10] <cjwatson> thelinuxer: for small changes, just putting them in a debian/patches/ file in the source package is often enough
[14:10] <cjwatson> I wouldn't bother with creating a project unless I were making fairly extensive changes
[14:10] <wgrant> Laney: sourcepackagename and status are exported in trunk, but not quite deployed yet.
[14:10] <wgrant> Laney: Hopefully tomorrow.
[14:10] <thelinuxer> cjwatson: ok cool
[14:11] <Laney> wgrant: oh, sweet. /me stops filing a bug then
[14:11] <wgrant> Laney: Bug #833080
[14:11] <Laney> hah
[14:12]  * Laney awaits that fix then
[14:12] <wgrant> Could have deployed it today, but I forgot. :(
[21:07] <tumbleweed> ScottK: any thoughts on sbte's closing of all the old emesene bugs and telling people to install a new version from his ppa?
[21:07] <tumbleweed> it seems pragmatically sound, but not really how things are supposed to work
[21:09] <ScottK> Fixed in the development release is the normal standard for fixed, so that's correct.
[21:09] <tumbleweed> I suppose that's reasonable
[21:10] <ScottK> I'd rather it be dealt with through backports, but if no one is willing to do the testing for that, PPA is not an unreasonable way to go.
[21:10] <tumbleweed> yeah, it sounds like there's quite a lot to be backported
[21:10] <tumbleweed> blackz used to care about that package, but he isn't around any more
[22:19] <jtaylor> hm requestsync complains about possible duplicate sync when the sync is complains about is a duplicated of a fixed bug
[22:19] <jtaylor> I assume thats a bug?
[22:20] <jtaylor> requestsync --lp f-spot brings up Bug #618981
[22:23] <tumbleweed> jtaylor: yeah, although that's possibly a bug in launchpad
[22:33] <jtaylor> lp.bugs[618981].bug_tasks[0].is_complete should be True when its a dup of a fixed bug?
[22:36] <micahg> jtaylor: are you sure about that?  shouldn't it just make sure it's not a dupe?
[22:36] <tumbleweed> micahg: that's what jtaylor is asking too
[22:36] <jtaylor> I have no idea
[22:37] <tumbleweed> fixed bugs aren't searched by default, so it would make sense to not search dups of fixed bugs either
[22:37] <tumbleweed> dups are a pain, you need to account for them everywhere
[22:38] <tumbleweed> jtaylor: I'd say fix requestsync here, but it's worth asking launchpad people if they think that's an lp bug
[22:42] <jtaylor> is there an attribute to check if all bug_tasks of a bug a fixed?
[22:42] <jtaylor> instead of looping over it
[22:42]  * tumbleweed points jtaylor at https://launchpad.net/+apidoc/1.0.html
[22:43] <jtaylor> hm so no
[22:44] <jtaylor> to bad all takes no lambda ._.
[22:44] <tumbleweed> hrm, searchTasks has an omit_duplicates parameter
[22:44] <tumbleweed> there we go
[22:53] <jtaylor> yup that seems to work
[22:53] <jtaylor> thx
[23:17] <jtaylor> merge proposed
[23:23] <tumbleweed> jtaylor: is limiting the status such a good idea
[23:24] <tumbleweed> sync bugs are often incomplete / in progress when there's some back-and-forth with the sponsor
[23:24] <jtaylor> it checks for is_complete later anyway which should be the same
[23:24] <jtaylor> just with maybe less load on lp
[23:25] <tumbleweed> I mean there are other non-terminal statuses
[23:25] <tumbleweed> it could also search on the tag sync, but not everybody sets that...
[23:25] <jtaylor> hm yes incomplete is missing
[23:26] <jtaylor> and in progress ._.
[23:28] <jtaylor> I guess its safer to remove it, but then it loops over 1100 bugs instead of 300 for f-spot
[23:30] <tumbleweed> I'd say specifiy all the non-terminal statuses then
[23:31] <tumbleweed> I wouldn't be entirely against using tags='sync' either
[23:31] <tumbleweed> or may be search_text="Sync"
[23:35] <jtaylor> yould have to be Sync and sync
[23:35] <jtaylor> does this work?
[23:36] <jtaylor> ync does not work as lp does no substring matching
[23:36]  * tumbleweed doesn't know, I'd have to experiment (staging / qastaging / dogfood is great for experimentation)
[23:42] <jtaylor> non-terminal status will do for now
[23:45]  * jtaylor is off to bed


[00:10] <jrwren> cscheib: I don't know why they care about which OSX they are on... at all. *shrug*
[03:36] <cscheib> jrwren: indeed.
[11:02] <cmaloney> Good morning
[11:35] <dzho> cmaloney: \o
[11:35] <dzho> who's going to OLF?
[11:35]  * dzho can't make it this time
[11:54] <cmaloney> Unfortunately I'm not going to make it
[12:00] <cmaloney> Kinda bummed because Jorge and Catherine Devlin are going to be there
[12:00] <cmaloney> but, c'est la vie.
[12:26] <jrwren> oh man, i haven't talked to catherine in many years. It would be nice to say hi.
[12:42] <cmaloney> Yeah, she's good people.
[13:08] <shakes808> morning all
[13:08] <shakes808> Found this comic and thought I would share: https://toggl.com/programming-princess
[13:10] <jrwren> shakes808: hahaha, very funny.
[14:47] <jrwren> hahahaha http://www.clickondetroit.com/news/armed-clown-robs-walgreens-in-brownstown-township


[17:25] <tobias47n9e_> Trying again: Is there any chance we will still see a fix for this issue in 14.10? I would even consider donating to the person that fixes this. https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1297302
[21:29] <teward> tobias47n9e_: you have to check with the people developing - we only do triage here, if the bug is marked "Triaged" then someone eventually will get around to it, but I don't think that's at the top of the "fix it" list given the other issues i've seen in the 15.04 stuff
[21:50] <tobias47n9e_> teward: Thanks for the answer. Maybe in 15.04 the bug won't be there to begin with.
[21:50] <teward> tobias47n9e_: you're welcome to download the alpha/beta images or the dailies and test
[21:51] <tobias47n9e_> teward: I would love to do that, but I currently have only one machine and wan't to finish up the program I am writing first.
[21:51]  * teward points at VMs
[21:52]  * teward points at VMware Player, VirtualBox, QEMU, etc. as virtualization platforms to test things on
[21:52] <tobias47n9e_> teward: I could try running it in VirutalBox, you'r right.
[21:53] <teward> if it weren't for this *sigh* windows VM running and updating i'd test
[21:56] <tobias47n9e_> teward: I'm downloading it. Will be gone again for a bit. Thank you and bye!
[21:56] <teward> tobias47n9e_: put a good bit of RAM towards the VM though - it's not VM friendly in low-ram
[21:57] <tobias47n9e_> teward: Is 4 Gb enough?
[21:57] <teward> tobias47n9e_: more than.
[21:57] <teward> was going to say don't use the 'recommended' value, was going to say 1.5GB or higher
[21:58] <tobias47n9e_> teward: Ok that is good to know. I don't have very much experience with VirtualBox yet.


[11:24] <flexiondotorg> wxl I see you're running the show fir Alpha 1 :-)
[14:08] <phillw> flexiondotorg: well he was... seems to have gone AWOL :P
[17:47] <wxl> adueppen: did you need something besides wondering what i meant by master as it relates to bugs?
[17:47] <adueppen> wxl: well I ended up marking both of those 2 bugs as duplicates of another that was reported earlier and flavor-agnostic
[17:48] <wxl> adueppen: that's good. the one that it's a duplicate of is the master. so that's what i meant
[17:49] <adueppen> wxl: oh wasn't quite sure with that
[17:49] <wxl> adueppen: i try not to jargon people up, but even i fail sometimes :)
[17:49] <adueppen> wxl: some of it was that I didn't get around to looking it up. I do the same thing to my parents, so it's no big deal
[17:52] <tsimonq2> lol
[20:01] <phillw> hi flexiondotorg and everyone else... anyone know where we're up to?
[20:10] <tsimonq2> phillw: attempting to get Alpha 1 ready for Monday
[20:12] <phillw> well, having it frozen and as an A1 is progress :)
[23:29] <phillw> flexiondotorg: just starting a 1st mate iso test... not sure how many other testers are available to help out.
[23:29] <flexiondotorg> phillw, Hi
[23:29] <flexiondotorg> I've done some testing today, but not completed the forms yet.
[23:29] <flexiondotorg> Looking good.
[23:30] <flexiondotorg> Some minor stuff but nothing release critical so far.
[23:30] <phillw> hiyas flexiondotorg just updating the iso. amd 64.... as I need to reset my VM, is a full install test of help?
[23:30] <flexiondotorg> I'm going to do some more testing tomorrow and complete the test cases.
[23:30] <flexiondotorg> Full install works.
[23:31] <flexiondotorg> oem install would be more instersting :-)
[23:31] <flexiondotorg> In that I've not done one yet.
[23:31] <flexiondotorg> phillw, Many thank for helping out.
[23:31] <phillw> flexiondotorg: well, I'll let you know if the test case is ballesd up :P
[23:32] <phillw> I'll have to follow the test case by the letter..
[23:36] <phillw> flexiondotorg: I'm a good boi...
[23:36] <phillw> phillw@piglet:~/Desktop/ISOs$ sudo lvcreate -L 15G -n m-xenial64 phillwvol
[23:36] <phillw>   Logical volume "m-xenial64" created.
[23:40] <phillw> flexiondotorg: what is minimum RAM for MATE?
[23:41] <flexiondotorg> 512MB
[23:41] <flexiondotorg> But 1GB is better.
[23:41] <phillw> omnly want to do an install :)
[23:42] <phillw> xubuntu / ubuntu start to stutter at 512 as install.... ubiquity is a bitch, but this is oem.. so new area.
[23:45] <phillw> flexiondotorg: a question... if it is an OEM install, why I am going back to 'try before installing' ?
[23:47] <phillw> ahh, that seems to be the way.....
[23:48] <phillw> I've read it now.... I cannot write CD's via a VM.. Sorry.