=== chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk [02:09] === trainguards: IMAGE 8 building (started: 20141104 02:10) === [02:22] ribru: issue with train: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu-rtm/landing-003 [02:22] ribru: it seems it's adding ~rtm by default [02:22] in this case, it was added in the wrong place === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk [03:09] === trainguards: RTM IMAGE 141 building (started: 20141104 03:10) === [03:24] === trainguards: IMAGE 8 DONE (finished: 20141104 03:25) === [03:24] === changelog: http://people.canonical.com/~ogra/touch-image-stats/8.changes === [04:19] === trainguards: RTM IMAGE 141 DONE (finished: 20141104 04:20) === [04:19] === changelog: http://people.canonical.com/~ogra/touch-image-stats/rtm/141.changes === [04:56] mornings [05:21] rsalveti: looks right to me? ~rtm always came before 0ubuntu1 [05:21] ribru: what if we already have 0ubuntu1 ? [05:21] and the next sync is 0ubuntu2 [05:21] this is basically what happened [05:22] rsalveti: sorry i don't understand the issue. [05:22] current RTM version: 0.99.0+git20130923+17fdf86-0ubuntu2 [05:22] current vivid version: 0.99.0+git20130923+17fdf86-0ubuntu3 [05:22] after the sync, the version on the ppa: 0.99.0+git20130923+17fdf86~rtm-0ubuntu3 [05:23] lp is saying 0.99.0+git20130923+17fdf86-0ubuntu2 is older than 0.99.0+git20130923+17fdf86~rtm-0ubuntu3 [05:24] rsalveti: bump the version I guess? call it 0.99.0+git20130923+17fdf86.1 and then citrain will add ~rtm-0ubuntu1 and be fine [05:24] ribru: why bumping the packaging major version? [05:24] this is a src package [05:25] this is a bug on the train side [05:25] will happen with every other package that has a similar version id [05:25] I actually expected it to not add ~rtm by default [05:25] rsalveti: orders from on high were to prevent src builds in rtm from not having ~rtm tag, because we have a big problem where there's a huge delta between utopic & rtm where the versions are the same bug package content are different. [05:25] adding it by default is annoying [05:26] ribru: right, but this is not a normal landing via MR [05:26] this is a src package landing [05:27] I'll probably manually sync from the archive into the ppa [05:27] and run watch-only [05:27] would be nice to have an option to not add ~rtm by default [05:27] rsalveti: we had that option and it caused too many problems, we were told to take it away [05:28] rsalveti: it's not a source package upload, it's a sync, and the sync code mangles the version for a source rebuild on purpose. [05:28] right, but doing the wrong thing here [05:28] rsalveti: please don't unmangle the version unless you're doing a binary copy [05:29] ribru: why that? [05:29] I'm not doing another upload to vivid just because of this [05:29] makes no sense [05:29] rsalveti: because there is an *enormous* delta between utopic and rtm in which source packages have different contents but same version numbers. it's hugely broken [05:29] and changing the upstream version of the package [05:29] I know, but this is not the case [05:29] and I know what I'm doing [05:30] when I said it's a source package upload, is that even when landing on vivid, it was a src package upload [05:30] no MRs involved [05:30] rsalveti: ok, well, this isn't a train bug, train is doing what it was designed to do so that rtm packages would have distinguishable versions. if anything it's an rtm bug, because rtm is a total fustercluck. [05:30] if a developer makes a mistake here, it's his own problem [05:31] well, the version here is clearly wrong [05:31] and the train did all the work [05:31] rsalveti: don't ask me, I didn't determine the versioning scheme. ~rtm-0ubuntu1 was decided on a long time ago, it's what the archive admins wanted. [05:31] I know rtm is in a broken/weird state, but the tool changed the version to an invalid one [05:31] they know things (presumably) [05:32] it works for 0ubuntu1 [05:32] not for versions higher than that (0ubuntu2...) [05:32] rsalveti: right but if rtm always had the right version, ~rtm-0ubuntu2 would be higher than ~rtm-0ubuntu1. so the issue is that a previous release had a wrong version, not that this version has the wrong versino [05:34] ribru: but how would rtm have the right version if it was a binary sync from ubuntu? [05:34] it *has* the right version now [05:34] there's nothing wrong with it :-) [05:35] see that I'm just trying to bump the package version of something that is already in RTM (via src package upload), doing the sync because I wanted to land first on vivid [05:36] rsalveti: yeah I don't know how to solve this problem. I'm not going to change the code to do -0ubuntu3~rtm because that code is a disaster unto itself. just do a manual copy into the ppa i guess. [05:37] ribru: sure, just reporting the issue anyway :-) [05:38] rsalveti: thanks. one day I'll just delete rtm and nobody will notice... [05:39] sounds like a good plan [05:39] :-) [05:39] having so much pain to sync so many packages from rtm into vivid [05:39] so we can land new stuff there and sync back [05:53] rsalveti: oh btw, OTA1 is gonna be based on utopic, so now we need to sync fixes between utopic, rtm, and vivid, but new features need to be synced between utopic + vivid but not rtm. have fun! [05:54] yup [05:54] madness [05:55] makes me glad I'm not an upstream ;-) I just push buttons... === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk [07:45] good morning [07:46] trainguards, could someone add qtubuntu-media-signals to the sync silo 12? [08:11] sil2100, hey there [08:16] o/ === chihchun_afk is now known as chihchun [08:38] tvoss: I think qtubuntu-media fails to build in the silo [08:38] sil2100, because qtubuntu-media-signals is missing === chihchun is now known as chihchun_afk [08:40] * brendand got that crash again [08:40] brendand, got crash file with core? [08:41] tvoss, what does the 'with core' bit mean? [08:41] i mean why would it not always be there? [08:42] brendand, there are numerous reasons why that can happen, difficult to tell. But we are hit by it for this particular crash quite regularly [08:42] tvoss, the CoreDump field is there [08:43] brendand, mind sharing the .crash file then? [08:44] tvoss: ah, so we need to rebuild those? [08:45] * sil2100 retries [08:45] sil2100, yup [08:47] tvoss, http://people.canonical.com/~brendan-donegan/_usr_bin_unity8.32011.crash.2 === chihchun_afk is now known as chihchun [08:48] brendand, is apport still running? [08:48] brendand: sorry, had a power blackout yesterday. you and jussi managed to triage the problem with silo 3? [08:49] Wellark, sort of [08:49] Wellark, well silo 3 landed anyway :) [08:51] tvoss, whoops! ignore that crash file... [08:52] brendand, ack [08:53] tvoss, i just remembered that i flashed 139 to test system-image, so that crash is most probably one of the already fixed ones [08:53] brendand, ack [09:01] trainguards: hey, can I have a silo for line 103? [09:02] oSoMoN: sure [09:02] good morning [09:02] trainguards: i have verified silo 8 for publication to vivid [09:03] Mirv, thanks! dbarth’s silo 8 would conflict, but I’ll wait for it to land before I hit the "build" button [09:05] oSoMoN: yes, exactly, the 008 will be m&c:d soon (30mins maybe) after it has migrated [09:05] brendand, sent you testing packages [09:10] Mirv, sil2100, line 54 on the spreadsheet says Status="Silo ready to build", but is is actually a source package and packages have been built automatically. brendand was asking about whether that status message can be changed to "QA needs to sign off" [09:14] abeato: yes it probably just needs watch only build, doing [09:14] abeato: additionally, the source package specified is wrong (lacks 1.0), needs reconfigure [09:15] Mirv, ok, thanks [09:16] abeato: now it's like it should be [09:17] Mirv, awesome, thanks, what was that "watch only build" step? just building from the dashboard? [09:18] abeato: yeah, you build it from the dashboard and tick the 'Watch only' flag in jenkins [09:18] Before pressing build [09:20] sil2100, ah, good to know, previously I had trouble using build from the dashboard with a source package, I didn't know about the flag ;) [09:20] brendand, now silo 8 has the right status [09:21] sil2100, btw, could you remove line 19 from the spreadsheet? It is not valid anymore (already landed). Or can I do that myself? [09:23] abeato, ok. right now the queue is a bit big from the freeze + image testing, but it should be tested by tomorrow at the latest [09:24] brendand, great, I just want to make sure that is in some queue ;) [09:24] thanks [09:25] abeato: sure! [09:26] sil2100, thanks [09:28] sil2100, i was just looking at the top output from all these systemsettle issues ... seems like we have a lot of whoopsie running all over the place [09:28] ogra_, is phablet-network working on 141? [09:28] sil2100, most likely caused by all the scoperunner crashes [09:28] ogra_: let me connect to the VPN and see [09:29] scoperunner crashes in every test run ... [09:29] hm, we didn't get that one resolved, right? [09:29] didnt we have a fix for that ? [09:29] i thought thostr_ had prepared a silo [09:30] ogra_, iirc, it is the scope crashing, not the runner [09:30] thostr_, ^ [09:30] ? [09:30] I just remember poking thostr_ about it, but don't remember if it had a fix prepared [09:30] tvoss, well, whatever crashes trashes test results :) [09:30] yes, this wasn't the scope runner but the scope [09:31] and IIRC cwayne or somebody from his team was taking care of it [09:31] well, we should land that quickly :) === chihchun is now known as chihchun_afk [09:46] ogra_: it's supposed to have landed already... https://bugs.launchpad.net/hanloon/+bug/1388035 [09:46] Error: ubuntu bug 1388035 not found === chihchun_afk is now known as chihchun [09:47] thostr_, yep, we just discussed it in the landin team meeting [09:47] thanks ! [09:51] Mirv, i have a silo here whose changelog says it changes nothing but the version. do you have that code snippet for doing the proper diff? [09:52] Mirv, normally i'd expect that if the diff is wrong it would have more changes, not less [09:58] brendand: so you tested on rtm, right? [10:10] brendand: http://pastebin.ubuntu.com/8558016/ :) [10:10] I always need to browse ~20 pastebin url:s from browser history to find it, but it's quicker than typing it again! [10:11] * Mirv suddenly has something that builds! [10:13] "builds" means allowed to eat lunch [10:13] bah [10:13] botochart isnt even in rtm [10:15] bootchart is broken on desktop [10:15] has been for months [10:15] collector runs forever, never generates an image [10:15] (for me) [10:16] oh, is there a bug ? [10:16] * popey looks [10:17] hmm, can't find one [10:17] yeah [10:17] brendand, ping [10:17] davmor2, ping [10:17] i ended up removing it [10:17] broke after updating to utopic [10:18] tvoss, hey [10:18] last image I have is from trusty [10:18] brendand, did you have a chance to give my packages a spin? [10:18] tvoss, not yet [10:18] ogra_: I'll file one from my desktop [10:18] * ogra_ just runs phablet-bootchart ... [10:18] but that will need some changes for the passwd stuff [10:18] ogra_, are you able to easily reproduce the current unity crashes? [10:19] tvoss, no, for me they are totally random [10:19] one a day [10:29] popey, why is there so much blank space at the bottom of the music app ? [10:29] where? [10:29] (in "now playing") [10:30] the controls feel like "one row to high up" [10:30] there's a toolbar down there, which appears in other views. [10:30] go to albums while playing something [10:30] right [10:31] ogra_: bug 1389166 [10:31] bug 1389166 in bootchart (Ubuntu) "bootchart broken in utopic, never generates images" [Undecided,New] https://launchpad.net/bugs/1389166 [10:31] cool, thanks [10:31] today I learned that my desktop has been installed since quantal ☻ [10:31] check the pastebin link in there [10:32] popey, oh, i think the png generation only works if you pipe the tgz to pybootchartgui nowadays [10:32] waaaat [10:33] why is that useful? [10:33] it dropped the java dependency that was responsible back then for png generation [10:33] interesting [10:33] i only run it for the funky png files [10:33] you get them (or even svg's) when you call "pybootchartgui /path/to/tgz" [10:34] it should have been installed as a dep [10:34] it is installed, just seems to make no sense, that should be part of bootchart [10:35] given the purpose of bootchart (in my simple brain) is to make "Boot Charts" ☻ [10:35] you can generate the data without UI tools [10:36] on servers you would only install bootchart and have a central machine rsync the tgz's to pipe them to pybootchartgui [10:36] right, so it should be a switch "make png/svgs/nothing" [10:36] Recommends: pybootchartgui [10:36] Breaks: bootchart-java [10:36] on desktops you always have the parser installed alongside [10:37] (due to recommends by default) [10:37] right, but it doesn't run, is my point [10:38] one could write an upstart job for pybootchartgui that watches the dir with inotify and generates pngs if a new tarball shows up [10:39] but i have no idea how a systemd equivalent would look like ... hello vivid :P [10:39] heh [10:39] ok, thanks. [10:40] does anyone find some time to give silo 12 a spin? [10:40] on devel-proposed, obviously [10:40] trainguards, icanhassilo for line 71 please [10:42] trainguards: May I ask for a silo to process the line 63? [10:44] tvoss: brendand is on silos and vrruiz will be too I'm on sanity and exploratory testing [10:51] Saviq: bzoltan_: done [10:51] o/ [10:52] Mirv: thank you [10:53] Mirv, hmm spreadsheet borked? [10:53] Mirv, line 71 doesn't look right [10:54] Mirv, and http://people.canonical.com/~platform/citrain_dashboard/#?distro=ubuntu&q=landing-007 doesn't list the unity8 MPs? [10:54] or comment... [11:00] ogra_: pybootchart craps out with "IndexError: string index out of range" - so.. yeah ㋛ [11:11] popey, yes, looking at that [11:16] woah [11:16] http://people.canonical.com/~ogra/ubuntu-phablet-vivid-8.png [11:16] i wonder what runs this dpkg-query zombie [11:19] Saviq: still borked? looks sane to me [11:19] Saviq: the prepare-silo was here https://ci-train.ubuntu.com/job/prepare-silo/3064/console [11:19] Mirv, no, seems it updated [11:19] tvoss, media-hub-server is using close to 100% cpu here - with no media playing [11:20] play media then, so it isnt wasted :P [11:20] brendand, core dump and strace would be great [11:21] tvoss, how do you make a core dump if it hasn't crashed? [11:22] brendand, https://sourceware.org/gdb/onlinedocs/gdb/Core-File-Generation.html [11:22] brendand, so find the pid of the process, attach with gdb as in: sudo gdb -p PID [11:23] then generate core file, quit gdb by entering quit [11:25] tvoss: why would you enter to quit is that not like pressing start to shutdown on windows ;) [11:27] Saviq, is unity8-dash anywhere calling dpkg-query or lsb_release from the code ? [11:28] * ogra_ tries to find out what trashes the bootchart so badly, seems both of the above is started right after unity8-dash (could be a scope doing that though) [11:29] ogra_, something like that is very possible, the scope backend sends out data about the phone [11:29] ogra_, and click scope probably needs some of that info, too [11:29] ogra_, your best bet would be pstolowski and alecu [11:29] ah, right, i wouldnt expect a confined scope to have that permission [11:30] click might indeed make sense here ... though on rtm it gets the wrong info anyway [11:30] (from lsb_release) [11:31] tvoss, (gdb) strace [11:31] warning: Couldn't determine the static tracepoint marker to probe [11:31] Static tracepoint 1 at 0xb6a23712 [11:31] tvoss, am i doing that wrong? [11:32] * brendand needs to take some time to learn gdb [11:32] brendand, you cannot run strace from within gdb [11:32] brendand, that being said: use gdb to generate the core file, quit gdb, and then run sudo strace -p PID [11:32] where PID refers to unity8 [11:33] ogra_, unity8-dash calls dpkg-query to get versions of unity8 and 2 other packages [11:33] pstolowski, what for ? [11:34] (and why on every boot) [11:34] the process goes into zombie state for ~5 seconds [11:34] are you sure it even returns what you want ? [11:34] http://people.canonical.com/~ogra/ubuntu-phablet-vivid-8.png [11:34] ogra_, it needs versions number to report them with every search query send to smart scopes server [11:35] (scroll down to unity8-dash) [11:35] hmm [11:35] ogra_, but it just gets them once on startup [11:35] ogra_, yes, i'm pretty sure i'm getting the expected version strings [11:35] well, it makes unity8-dash peg the CPU quite heavily alongside having the query sit there as a zombie [11:36] (cpu pegging might be unrelated though, it might just be initializing a ton of scopes) [11:37] ogra_, what it does is just "dpkg-query -W libunity-scopes3 unity-plugin-scopes unity8" (http://bazaar.launchpad.net/~unity-team/unity-scopes-shell/trunk/view/head:/src/Unity/scopes.cpp); so, any idea why it's that slow? [11:38] well, the dash seems to do a lot other stuff at that time too ... might be so busy that it cant process the return value from the query [11:38] i'm not sure where that CPU hammering comes from (all the blue little stripes you see in the unity8-dash bar on that chart) [11:41] pstolowski, i wonder if there isnt some apt lib you could use instead of the dpkg-query that would provide you a better api than firing up a subprocess ... apt is C++ there should be something you can use thats better suited ... mvo_ might be able to help [11:41] ogra_, i'm not sure what to do about it right now. could you please file a bug? we need alternative and it's not going to be a one line fix [11:41] mvo_, mind take a look at http://bazaar.launchpad.net/~unity-team/unity-scopes-shell/trunk/view/head:/src/Unity/scopes.cpp#L162 in a spare minute ? [11:44] tvoss, and then what? it just stays on epoll_wait [11:45] brendand, in strace? [11:45] tvoss, yes [11:45] brendand, ack, then just ctrl-c. I would need the core file [11:48] tvoss, well here's the core file: http://people.canonical.com/~brendan-donegan/media-hub-server.core [11:48] brendand, thanks [11:49] tvoss, still uploading though [11:49] tvoss, will probably be about 30 minutes [11:49] brendand, ack and thx [12:03] brendand: I don't find bug #1374481 in the lists [12:03] bug 1374481 in unity-scopes-shell (Ubuntu) "Nearby and News scope do not load on reboot" [High,In progress] https://launchpad.net/bugs/1374481 [12:04] 11/6+11/13 targets nor in 11/13 iteration wishlist/escalations [12:15] Mirv, doesn't need to be since it was given the tag by olli himself - see just above comment 22 [12:16] Mirv, if the tag was given my olli or pmcgowan then its automatically ok [12:30] brendand: the latest e-mail from olli was 18 hours ago, and it only talks about the topblockers + additionally escalated bugs' wishlist. the tag was added 3 weeks ago, which is several iterations earlier of the process. [12:30] note that I might be totally wrong, I just try to decipher the landing rules and last I heard it was limited to the topblockers list, after which another "wishlist" appeared that can be landed additionally [12:31] ogra_, pstolowski: looking at this now. could you give me a little bit of context, what is this data needed for? it might be way simpler to simply export this as part of the package build or even postinst into a single location and avoid the overhead of reading the (big) status file entirely [12:32] pstolowski: happy to help with this, but I need to understand first what exactly there is done (i.e. what data do you need from dpkg) [12:32] mvo_, http://people.canonical.com/~ogra/ubuntu-phablet-vivid-8.png ... scroll down to unity8-dash there ... the dpkg-query call turns into a zombie (grey) while unity8-dash gets very busy (blue bars) [12:33] mvo_, i was wondering iif there isnt a way to do that a bit cleaner and without a subprocess call directly from C++ [12:33] it seems to need that data to query the right stuff from the scopes server [12:33] mvo_, i need to read versions of 3 important packages.. whenever any of them is upgraded, i need the new version to be picked at runtime (after reboot) [12:33] ogra_: yeah, definitely, but maybe the overhead can be avoided entirely by exporting the information at build/install time [12:33] i suspect that could also be put into a file at rootfs build time though [12:34] which you simply read ... [12:34] but it will likely break in case you make the image writable and install a new unity8-dash for i.e. testing purposes [12:34] (or in desktop-next) [12:34] pstolowski: thanks, so you read this at startup and compare to the previous version? (pardon my ignorance) [12:35] * ogra_ understood it isnt even compared but just sent [12:35] mvo_, no, i just pass it to the smart scopes server [12:35] sil2100: if you're around, could you clarify the landing rules to me and brendand :) see comments 5 + 20 mins ago [12:36] Mirv: reading those right now ;) [12:36] pstolowski: thanks, I get the idea now. let me think for a moment about it [12:37] so, my current "check lists" are a) 11/6 & 11/13 targets b) 11/13 iteration wishlist/escalations [12:37] Mirv, brendand: so as always there's a lot of ambiguity with the current rules, but the [TOPBLOCKER] bugs are essentially bugs that NEED to be fixed before we release the final image [12:38] Mirv, brendand: I suppose anything that was set for an earlier milestone but just didn't make it on time should still land normally [12:39] sil2100: 4 days ago there was an email that said "approved landings: only the ones listed in [1] are OK to land, anything else needs to be escalated to the Product Team" [12:39] Mirv, brendand: from what I know, the rule is to keep the topblockers as top priority for developers and landing, but I didn't hear anything about us not landing critical bugs that have been approved earlier [12:39] ogra_: using libapt for this would be fine, but if the cache needs rebuilding its still a performance hit we can avoid, its just three packages afterall [12:39] and 18h ago there was another email about this wishlist/escalations [12:39] Mirv: I think I need to clear this out with olli once he's online [12:40] Maybe he wasn't exactly super clear in the e-mail back then [12:40] sil2100: based on those two latest e-mail from olli, I restrict myself to the 11/6 & 11/13 targets + 11/13 iteration wishlist/escalations for now. it seemed clear in those e-mails we're restricting ourselves to the lists. [12:41] but let's see if any new information emerges once he's online! [12:44] sil2100: hey, so we do have a fix for that scope crashing [12:44] don't yet have a fix for the activity indicator never going away [12:44] cwayne: hello! Excellent, we thought so during our morning meeting actually [12:44] land it !! [12:44] :) [12:44] cwayne: is it in the custom tarball you mentioned yesterday? [12:45] sil2100: yeah [12:45] davmor2: how busy are you? [12:45] Mirv, any idea why http://people.canonical.com/~platform/citrain_dashboard/#?distro=ubuntu&q=landing-007 doesn't show the unity8 MPs (and cuts off the description, too)? [12:45] ↑ loaded question [12:46] sil2100: fairly but nearly done, custom will happen after Lunch though [12:46] davmor2: great to hear that, we'll be waiting! [12:46] cwayne: ^ [12:47] Saviq: I don't see what'd be missing, the last bug in the description is "Fix answering by accident", same as in ci train [12:48] Mirv, oh, I'm blind, but still, MPs are not listed? [12:48] Saviq: no idea why the unity8 popover is empty, sil2100? [12:48] Mirv, yeah, newlines FTW, is why I couldn't see them all [12:48] maybe some parsing error, at least there are blank lines in the MP list (only thing that comes into my mind) [12:48] hmm that wasn't a problem before [12:49] anyway, let's see how a build goes [12:50] ogra_: mako on vivid can you connect via mtp? [12:51] davmor2, no idea, no mako with vivid around here :P [12:51] shouldnt be different from krillin rtm though [12:51] when the screen is unlocked it should let you in [12:52] Saviq, Mirv: not sure... the CSV parsers can sometimes be a bit dumb too [12:52] ogra_: is the popup window I get on image 8 Unable to open MTP device '[usb:003,030]' [12:52] ogra_: and that is logged in :) [12:53] davmor2, sounds liek mtp-server crashed then [12:53] check /var/crash [12:55] ogra_: phablet 3988 0.0 0.0 4844 672 pts/0 S+ 12:54 0:00 grep --color=auto mtp I'm assuming I should see it running right? and nothing in /var/crash [12:59] davmor2, you should see mtp-server running [12:59] seemsingly you dont [13:00] ogra_: indeed so I'm assuming it just isn't started [13:01] ogra_: manually I did start mtp-server now it is working [13:01] davmor2, right, file a bug and let cyphermox know [13:01] olli: hey! [13:01] sounds liek you dont get the right upstart events or some such [13:01] hi sil2100 [13:01] davmor2, which is a bit weird, since this definitely didnt change in vivid vs rtm [13:02] i know there is a pending fix for an mtp crash, but nothing that touches the upstart setup [13:04] trainguards: can silo 6 (vivid) be published, please? [13:05] pstolowski: sorry for the delay, got distracted. something like http://paste.ubuntu.com/8818749/ for the three packages in question maybe a cheap way to store the information. filename/location may not be ideal but you get the idea I guess :) [13:07] oSoMoN: o/ [13:08] mvo_, is it going to be triggered and updated whenever any of these packages get upgraded? [13:09] Mirv, brendand: ok, so confirmed that what Mirv mentioned holds true - we should really only consider topblockers right now (for most cases) [13:09] pstolowski: the snippet needs to be added to the postinst/postrm of the three packages affected and then you can simply read it from there. you could use libapt too, but in the worst case you will still have to read /var/lib/dpkg/status which is 6mb on my workstation just to get these 3 lines [13:14] sil2100, re- packaging changes, where can I get a link to the relevant diff for changes in debian/, so that I can ask a core dev to review? [13:16] ogra_: do you have a moment for a packaging ACK for webbrowser? :) [13:16] sure [13:17] oSoMoN, ogra_: so, I checked the diff right now and I see a problem [13:17] oSoMoN, ogra_: https://ci-train.ubuntu.com/job/ubuntu-landing-006-2-publish/32/artifact/packaging_changes_webbrowser-app_0.23+15.04.20141104-0ubuntu1.diff/*view*/ [13:17] oSoMoN, ogra_: but... qtdeclarative5-quicklayouts-plugin is in universe, while webbrowser-app is in main [13:18] sil2100: ok, good that I kept saying that then :) [13:18] So this dep is a bit troublesome [13:18] yes [13:18] Mirv: yes :) [13:18] that would break on desktop [13:18] sil2100: brendand: pete-woods: thostr_: rtm-019 is CI sign-off:d but blocked by not being approved by olli. please submit it to "11/13 iteration wishlist/escalations" spreadsheet. [13:18] s/CI/QA/ [13:19] if that's https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1374481 [13:19] Ubuntu bug 1374481 in unity-scopes-shell (Ubuntu) "Nearby and News scope do not load on reboot" [High,In progress] [13:19] then pls proceed landing it [13:19] * sil2100 goes off for lunch o/ [13:19] just cut the wishlist thing short [13:19] that should hvae been a topblocker [13:20] olli: yes it is, thanks! then I'll just publish it, thostr_ + pete-woods [13:20] sorry, we missed that one somehow when looking at topblockers [13:20] Mirv, sil2100, if in doubt -> wishlist and ping pmcgowan or me [13:21] olli: just to be sure: on the wishlist spreadsheet, only the new tab applies, meaning it overrides the previous one? [13:21] olli: sure, that's what we do. there was just a bit of confusion of the process but it turned out I had the correct idea. [13:22] thostr_, correct [13:23] olli, but can only TOPBLOCKER bugs land? [13:27] sil2100: oh, good catch! sorry I didn’t catch it upfront, I’ll fix this somehow [13:27] mvo_, i see. yeah, this script seems like a good solution, thanks for that [13:28] pstolowski: yw [13:28] oSoMoN: might not be a big issue, maybe it can just be included into main... but you know how MIR issues can be tiring sometimes ;) [13:29] sil2100: no need for that, I’ll just make sure we remove the need for QtQuick Layouts in the browser, it’s a minor change anyway [13:29] brendand, unless explicitely approved in the wishlist [13:31] olli, am i correct in thinking this is a change from a couple of weeks ago? pmcgowan told me that bugs with the three tags could land as long as the tags were added by you or him [13:31] (two tags actually) [13:31] rmt14+date [13:33] brendand, correct, I tried to outline it in my mail to phablet "next landing dates and milestones for BQ" from 10/30 [13:34] olli, ack [13:35] brendand, with some luck we might be able to improve this situation a lot, soon [13:35] luck = me having some time today [13:36] brendand, we do appreciate you guys reviewing changes for landing risk, as some of these were tagged some time ago [13:58] abeato, i'm testing 10 right now btw [13:59] brendand, ack [14:00] sil2100: Krillin on 141 passes sanity, Mako on devel-proposed Fails mtp isn't started. [14:01] trainguards can I get a silo for #72 please? === karni is now known as karni-lunch [14:05] trainguards, can you please reconfigure vivid silo 7 for me, added unity-api there [14:20] sil2100, ogra_: is there a bug for not being able to disable a specific test set based on device? [14:20] davmor2: on smoketesting? [14:20] Saviq: sure [14:21] ralsina: [14:21] o/ [14:21] sil2100: yes ie filemanager tests on krillin [14:21] davmor2, https://bugs.launchpad.net/ubuntu-test-cases/+bug/1387391 [14:21] sil2100: yes sir! [14:21]