=== chihchun_afk is now known as chihchun [05:20] robru: diff:ing errors in publishing https://ci-train.ubuntu.com/job/ubuntu-landing-014-2-publish/120/console [05:22] robru: and then it fails apparently on assuming the diff would have packaging diff, while the mir seemingly would not have [05:23] just in case, I try to watch_only build [05:38] robru: yeah the diff:s are zero sized https://ci-train.ubuntu.com/job/ubuntu-landing-014-1-build/248/ [05:40] Mirv: oh god. Let me look [05:44] Mirv: oh, I see [05:44] Mirv: sil asked me to flip the switch so that dual silos always publish to overlay now. so what's happening is those packages aren't in the overlay so it fails to find any old version, which is why the diff is 0 [05:45] Mirv: if you look at the packaging diff it says it's a new package [05:45] Mirv: should this silo go to overlay? [05:46] i guess so if it's just phone stuff [05:46] I'll whip up some code to make it fall back on main archive if it can't find the package in the ppa. [05:48] robru: ah... [05:48] robru: so. if sil wanted to flip the switch, then yes I guess we want everything to dual land to overlay now. [05:48] Mirv: hmm actually there's already code that says "if version not found, check main archive", not sure why that didn't trigger... [05:49] bzoltan_, Mirv: hey, I fixed webbrowser-app in silo 57 last night, as far as I’m concerned it’s good to go, feel free to publish if you’re not waiting on anything else [05:49] robru: hmmkay. [05:49] oSoMoN: sure, we just have a slight breakage :) [05:49] oSoMoN: plus the UITK has packaging changes so it'll need a core-dev. [05:49] right [05:49] Mirv: check if those packages are already in overlay ppa, it should be publishable if they are [05:49] Mirv, where is that breakage? in the train itself? [05:50] oSoMoN: yeah I broke the train so it can't publish things if they don't already exist in overlay ppa [05:50] working on it [05:53] robru: they are actually, it's still 0 size [05:53] robru: so it's not the fallback [05:53] robru: oh right but not wily, sorry [05:54] robru: of course there's nothing for wily in the PPA [05:54] Mirv: oh right, nothing would be there for wily [05:54] Mirv: yeah the "0 size" is not particularly meaningful, python creates those files first before debdiff gets involved, content diff being 0 size just means "debdiff had unknown errror" [05:56] Mirv: ok, I think I see what's happening. when it decides whether to use the overlay ppa vs the archive, it doesn't specify the series, so the vivid package says 'yep theres a package in the overlay ppa' then later when trying to diff it specifically says'ok overlay pp, gimme the wily version' and that fails [05:57] Mirv: so if I specify the series in the initial check it should work [05:58] right! thanks for looking into it. we could have workarounded by manual copying but it'll be good to have train back too. [06:01] Mirv: you're welcome. ok, fix pushed to trunk, will hit production in 20 minutes, try it again then and ping me if it still doesn't work. [06:04] ok [06:20] Mirv: robru: an we merge the landing MR to the trunk before the package is acked and published to Wily? [06:28] bzoltan_: no, packages aren't going to wily anymore, they go to overlay for wily series too [06:29] Mirv: ohh, how shame [06:32] Mirv: should be safe to publish now [06:35] robru: hmm, looks good now. but I wonder why ^ without packaging changes and with a MP upload? [06:36] Mirv: is it in main? [06:37] robru: yes, in main, but I thought the exception still was canonical upstream projects handled with MP:s without packaging changes can be uploaded. [06:37] since I remember being mentioned that manual main uploads always require core dev publishing while MP ones wouldn't [06:38] Mirv: the artifacts have packaging changes [06:39] robru: sorry for firing so many questions, but I also think that https://ci-train.ubuntu.com/job/ubuntu-landing-057-2-publish/9/console - a main package _with_ packaging changes, used to complain about the need of an "ack" before failing about no right [06:39] robru: yes, but not for mir: https://ci-train.ubuntu.com/job/ubuntu-landing-014-2-publish/ [06:39] robru: the others are universe packages [06:39] Mirv: packaging changes prevent the whole silo from being published [06:40] robru: yes, but it didn't complain about packaging changes but the upload rights. [06:40] Mirv: when deciding to publish it doesn't consider each package individually, you need to have permission to upload everything [06:40] robru: I'll try 014 with 'ack' checked, since that's what it'd require for the universe packages. [06:41] robru: yes, but the one main package without packaging changes would also be allowed by current policy. [06:41] Mirv: that's just how the check works. If there are packaging changes and you don't have rights, it says "not authorized", it only says "need ack" if you have the ability to give an ack [06:42] robru: it seems 014 worked with 'ack', right. I think functionally it's all good, just a bit confusing it complains about no rights to upload mir package while actually there are rights to upload that one, and the real erroring out reason was the lack of an ack for packaging changes in universe package. [06:43] Mirv: yeah that could be reported better i guess. Right now the error just goes by the first wrong thing it sees [06:44] robru: so in case of 014, I did have the ability to 'ack', and the error it gave was not really a problem since mir didn't have packaging changes itself. [06:44] 7 silos marked dirty by that, jeez people are really abusing conflicting silos these days. [06:44] robru: but no problem, understood again [06:44] oh really... [06:44] there's also huge amount of webbrowser silos [06:45] robru: aaaaanyway, everything good, logic understood, I'll just need to find a core-dev for 057. [06:45] When i wrote the dirty logic i expected any silo to have at most one other conflicting one [06:49] Lol, audit logs are online for a day and we're already up to comment id 397, i should figure out how postgres stores primary keys, check at what point it will integer overflow [06:51] robru, Mirv: QA is the bottleneck here, there wouldn’t be so many webbrowser-app silos if there was more throughput [06:52] and also the fact that I noticed only yesterday that webbrowser-app was failing to build in silo 57 [06:58] Mirv: strange that 14 didn't migrate yet, it should copy & merge immediately (no proposed in overlay) [06:58] Mirv: can you check that all the packages are in overlay and if so, manually merge silo? And file a bug that migration is broken. [07:01] Mirv: i assumed it would check the dest ppa but i guess something isn't using the right archive property. [07:01] Mirv, is there a way to make packages go to wily rather than the overlay? [07:02] seems weird to force the overlay, some bugfixes can still be useful to wily [07:03] seb128: i had fixed that but slangasek requested all packages go to overlay. If you really want a train fix in wily you can copy from ppa yourself [07:04] I don't want a train fix, I just discuss the principle behind the decision [07:04] but I guess I should discuss it with slangasek [07:11] robru: seems they are all there, merging + filing [07:11] seb128: i mean, if you have a bugfix in a train silo and you want this in wily, you can copy the package to wily yourself for now. But yes, take it up with slangasek because i had enabled users choosing where to publish to and then he told me to enforce it train-wide [07:11] k [07:12] seb128: oh actually also this enforcement is only for dual silos, so if you are just working on some desktop only stuff you can just have a wily silo and publish to wily, i forgot about that [07:12] robru, thanks for the auditable logs. One more thing though bug 1502018 [07:12] bug 1502018 in Bileto "Differentiate automated comments from user comments" [Undecided,New] https://launchpad.net/bugs/1502018 [07:12] yeah, that makes sense [07:13] jibel: the ones that have the "log" link are generated ones ;-) [07:13] robru, nope [07:14] jibel: is it enough to make the user comments bold or something? Man you're picky! [07:14] robru, if it's a status change there is no indication [07:14] jibel: but the status change is always just "Updated x" it's short... [07:14] robru, I think this comments are useful to understand what happens with a landing but most of the time they are not useful to the lander and could be hidden [07:16] seb128: if you have time, please check the UITK diff and publish 057 since it's a main package https://ci-train.ubuntu.com/job/ubuntu-landing-057-2-publish/9/ (adds dependency on liblttng-ust-dev which is in main, and adds two new binary packages) [07:16] robru, like, it is a bit like it's very useful to have a syslog but you don't want it all time on your terminal :) [07:16] jibel: well I'm halfway through a full site redesign so i guess it's a good time to consider these things. I'll have a live demo up next week, we can iterate on it before going live [07:16] robru, sure [07:17] robru, sounds good to me [07:17] Alright goodnight everybody! [07:17] robru: good night! [07:17] and thanks for the fixes and features! [07:17] godd night robru [07:18] good* [07:18] Mirv, looks fine to me [07:18] You're welcome! [07:19] seb128: you need to run the publish job too, nowadays just verbal ack is not enough [07:19] seb128: train checks whether the person would have archive rights for the packages in question (if their MP:s have packaging changes) [07:20] Mirv, even if you don't upload to the archive? [07:20] Mirv, done [07:23] looks like oSoMoN and dbarth like to claim silos for webbrowser ;-) [07:26] seb128: Thank you a bunch :) [07:26] bzoltan_, yw! [07:30] yeah [07:31] cool, so now i go first for the next webbrowser-app landing ;) [07:33] dbarth: sorry mate :) I had to push a fix for the browser to prevent AP breakage with the new UITK. I take all blames :) [07:34] dbarth, yep, silo 25 then 59 [07:38] yup; bzoltan: nw [07:41] seb128: thanks a lot! yes, it's enforced even for overlay which is thus treated like on archive (even though in reality we could copy packages there manually). [07:42] sil2100: hey just FYI auto-mergeclean is busted at the moment probably due to the switch to overlay-only, so one needs to check everything landed to overlay and run merge & clean manually [07:43] dbarth: hey, the webbrowser-app trunk was not pushed yet... [07:44] dbarth: now it is, aborting your 025 build and rerunning [07:44] dbarth, silo 16 is for OTA7? [07:52] trying, but just in the middle of a call [07:53] ok, so i need to wait a bit still [07:53] jibel: hopefully, silo 16 contains the memory limits improvements [07:54] we need to test it a bit, but based on initial reports, that's the one to take [07:56] Mirv: ACK! [08:01] dbarth, very nice, thanks! [08:42] Mirv: we need this project on the train and land it on the Vivid Overlay PPA - https://launchpad.net/ubuntu-sdk-qmake-extras What should I do? [08:46] bzoltan_: set owners/managers/members correctly, I can do that after this hangout [08:46] (if there's something to do) [08:46] bzoltan_: + packaging with .bzr-builddeb etc from https://wiki.ubuntu.com/DailyRelease/InlinePackaging in the code [08:47] Mirv: Ok, thanks for reminding me :) [08:54] bzoltan_: the .bzr-builddeb needs to be in /, not debian/ [08:55] Mirv: Of course [09:04] bzoltan_: so.. I think the project might be just good to go as is. I think it's better to try and see if anything fails, but the ci-train user that's needed is in SDK team so it should be ok. [09:07] Oh no, the buteo silo has a lot NEW packages [09:08] sil2100: I've saved a note from cjwatson "I think we should stop bothering with preNEW for new sources, and only keep it for new binaries" [09:08] since train does not bypass src NEW queue [09:08] I don't at least misquote him, hopefully also I don't misuse the quote :D [09:09] sil2100: but the packagings should be reviewed normally as for universe packages of course [09:09] ;) [09:09] Indeed, yeah [09:11] Most of the packaging was prepared by kenvandine, so this should be relatively fast [09:20] dbarth: 025 is now ready (just one i386 still building), please hand it over to QA swiftly so that the big webbrowser queue can be processed... [09:21] Mirv_: cool; thanks for that [09:21] i know webbrowser-app builds take some manual care currently [09:25] jibel: I bootstrap flashed latest rc-proposed and upgraded to a silo (which dist-upgraded, so new mir etc too), and I've Unity 8 restart loop now even after purging my PPA. Care to double-check? [09:25] Mirv_: I'm still thinking about requesting a preNEW review here though [09:25] Mirv_: you do not misquote me [09:25] Mirv_: since... it's a dual silo, so the change gets directly to the overlay [09:25] It bypasses the NEW queue and will be picked up only when we copy to W+1 [09:25] right, preNEW is for cases where NEW ought to exist but doesn't [09:26] Mirv_, sure, which silo? which device? [09:26] sil2100, wily images don't have overlay enabled yet? [09:26] sil2100: does the copy to W+1 bypass the queue any more than train? [09:26] jibel: what I meant is: use current rc-proposed and dist-upgrade (to get today's landings like 014) and try that. I'm on mako. [09:26] Saviq: no, not yet, but will be now - Robert was switching to overlay-only landings when I was EOD already [09:27] kk [09:27] Mirv_: ok, the packaging looks okay to me so far, it's been worked on/reviewed by kenvandine and seb128 for most cases too [09:27] Mirv_, yeah but I'd also like to check if any leftover from the silo would cause the reboot loop [09:27] seb128: hey! Could you perform a few preNEW reviews in the buteo silo for us? :) [09:28] jibel: well it's my 032 which is not going to land any time soon (if ever, before Qt 5.5) [09:28] seb128: the links are: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-034 for the PPA and https://ci-train.ubuntu.com/job/ubuntu-landing-034-2-publish/6/ for the artifacts [09:28] sil2100: ok then [09:29] Mirv_, which channel exactly rc-proposed/ubuntu? [09:29] jibel: ubuntu-touch/rc-proposed/ubuntu [09:30] sil2100, can try this afternoon yes [09:30] seb128: thanks! [09:31] davmor2: ^ the buteo silo will wait a bit before landing, we need a preNEW review [09:31] But I think it should still be ok to test it live today [09:31] sil2100: sure just give me a ping I'll make sure I have images ready [09:32] sil2100, we are already far past feature freeze, if it doesn't land today, it will be for OTA8 [09:32] jibel, davmor2: ticket 412 / silo 25 re-tested here; on to you now [09:32] yw! [09:32] dbarth, thanks, unblocking [09:32] jibel: however oxide 1.9.4 has a regression; we're investigating :/ [09:33] but memory usage doesn't balloon as high as before [09:34] jibel: +1 on that [09:51] Mirv_, it looks bad, unity8 crashes apparently [09:52] sil2100, don't rebuild any image yet there is something broken in the ovelay [09:52] overlay* [09:52] Oh [09:53] sil2100, it would be the last unity8/mir/powerd landing [09:53] https://requests.ci-train.ubuntu.com/#/ticket/343 [09:53] Mirv_, did you collect any info about the crash? [09:53] I'll try on krillin [09:54] Do you know already which image was the one first broken? [09:54] sil2100, the broken image doesn't exist yet, it'll be next one [09:55] jibel: I approved last night silo 15, which contains unity8, powerd, mir, system-compositor [09:55] rvr, on which device [09:55] ? [09:55] jibel: arale [09:56] maybe it's only a problem on mako [09:56] I'm trying krillin now [09:57] Remember that powerd needs manual fix to properly install [09:58] the ppa packages may not finish installing [09:58] jibel: I tried looking at the logs but reflashed already (but obviously can easily get it back to broken state) [09:58] rvr: jibel: rvr's point might be the thing, I just used citrain tool [09:59] so it might be all resolved with the next image === Mirv_ is now known as Mirv [09:59] sil2100: if ^ that's the thing, it might be useful to have a new rc-proposed image since otherwise people flashing latest image + upgrading to their newest silo will experience that [10:00] but let's confirm first [10:00] Ok, once you confirm we'll kick a new image [10:08] * Mirv has to eat late lunch [10:23] ogra_: hey hey, could you review+merge https://code.launchpad.net/~sil2100/livecd-rootfs/fix-apt-lists-rm-hook/+merge/273117 ? This is the hook that works ;p [10:29] cjwatson: hey! Could you take a look in a free moment at https://code.launchpad.net/~sil2100/ubuntu-cdimage/enable_wily_overlay/+merge/273208 ? [10:30] sil2100: isn't there somebody else who could be the routine cdimage reviewer? [10:31] I'm not a good candidate [10:31] because I don't do most of the day-to-day stuff of keeping cdimage running any more [10:31] cjwatson: not sure, I guess I might poke infinity as he has the most commits (but he's a different TZ) - not sure if stgraber is still working on it anymore [10:33] sil2100: I'll do it this time, but please try to find somebody who isn't me for the next one [10:33] cjwatson: will do, thanks! [10:34] sil2100, Mirv krillin is not affected by the shell crash, only mako apparently [10:35] sil2100: merged and deployed, thanks [10:35] including manual crontab edit [10:35] Thank you again! [10:55] jibel: so it's unrelated to powerd? [10:56] sil2100: Apparently not [10:56] sil2100, there is no problem with the upgrade of powerd on mako because the configuration file is not mounted [10:57] unlike krillin or arale [10:57] sil2100, Mirv bug 1502093 [10:57] bug 1502093 in unity8 (Ubuntu) "unity8 crash on mako rc-proposed/ubuntu with latest unity8/mir/powerd" [Undecided,New] https://launchpad.net/bugs/1502093 [10:57] kgunn, ^ with silo 15 that landed yesterday on mako only [10:58] Mode argument was not provided or was set to an illegal value. Using default value of --mode= "full-greeter" [10:58] jibel: thanks! right, so mako only which probably explains why it wasn't caught. [10:58] Mirv, thanks for catching it! [10:58] Still, we'll need this fixed === chihchun is now known as chihchun_afk [11:20] seb128, is it known and on purpose that https://code.launchpad.net/~seb128/ubuntu-system-settings/location-desktop-usr/+merge/272711 is in two silos? [11:30] jibel: ack getting someone on it [11:32] kgunn, I didn't find anything useful but the phone is still in this state if someone needs more info [11:32] jibel: but bascially we can just do a dist-upgrade and see the same thing right [11:32] on rc-proposed [11:33] rvr: is this relevant "Mode argument was not provided or was set to an illegal value. Using default value of --mode= "full-greeter"" [11:34] kgunn, yes [11:34] yes to install latest rc-proposed on mako + dist-upgrade [11:36] jibel, kgunn: I poked alf_ on ubuntu-mir already [11:38] sil2100: thanks [11:39] oSoMoN, unsure, to check with kenvandine, but if you want to land a silo with it feel free, we can rebuild the other one [11:40] davmor2: trello claims 025 was moved to Under Testing in the Activity, but still it's in "Ready for Testing" on the board. it also has Blocked tag, and you mentioned it's working fine. Can you try to fix the status of the card? [11:41] Mirv: we will move the card once we know it is working with the ota test if that fails it needs to move over to failed [11:41] seb128, none of them is mine, just saw it and I thought I would ask [11:42] davmor2: thanks, I was just puzzled by the Trello showing contradicting information [11:42] seb128, but I would need to add the branch to silo 59 if it didn’t land before that [11:42] Mirv: no worries there is a comment on the card but I'm happy to clarify :) [11:42] oSoMoN, let's wait for kenvandine, we can maybe land the settings one today [11:43] seb128, that’d be great [11:43] unsure about the unity8-dash profile [11:43] pstolowski, ^ what's the status of silo 3? [11:47] seb128, we need bigger fix as it uncovered an issue with location. tvoss is going to work on location service changes [11:47] k [11:48] so settings is going to be ready first most likely === _salem is now known as salem_ [11:56] seb128, yeah, but we cannot release it as is. feel free to land you change at any point though [11:56] right [12:04] Mirv: sorry I think we were talking at cross purposes, silo025 is under test now, silo 34 is the one that should have the mixed state === alan_g is now known as alan_g|lunch [12:05] Mirv: silo34 is the one that is good and sil2100 will be landing in an image asap for me to test upgrades [12:06] Yeah, waiting on a preNEW review for 34 [12:08] davmor2: no, I just meant that on my trello view 025 was in a different place than the activity showed, now it's corrcet [12:09] Mirv: so the blocked tag was removed because it has been rebuilt, it was therefore ready to test so I moved it to under testing because I'm testing it [12:16] sil2100, should we pull the silo before it reaches an image? [12:17] https://requests.ci-train.ubuntu.com/#/ticket/433 is the offending landing [12:23] Saviq: I think we could soft revert this, it only touches 2 projects [12:23] Let me try that, need to check if webbrowser-app is revertable still [12:23] * sil2100 got back from lunch [12:24] sil2100, no need to revert webbrowser even I think, it doesn't depend on new UITK it doesn't seem [12:24] I was worried by the merge description though, it being: "Do not select labels by their class name, as this is changing in the newest UITK." [12:25] sil2100, I think the change (in webbrowser) is backwards compatible, and if it's not, someone's missing deps [12:27] Saviq: I guess anyway even if the AP test suddenly fails it's still better than having a broken image [12:27] indeed [12:28] Saviq, whats the deal? [12:29] pmcgowan, latest UITK crashes QML (so unity8) on mako and flo [12:29] thats bad [12:29] https://launchpad.net/bugs/1502093 [12:29] Ubuntu bug 1502093 in ubuntu-ui-toolkit (Ubuntu) "UbuntuShape crash with latest UITK on mako/flo" [Undecided,Confirmed] [12:29] that would have been my guess [12:29] pmcgowan, greyback_'s suspecting driver bug at that point [12:29] yep [12:31] OTOH wily is fine [12:32] Good, then I'll only have to revert it for the overlay then? [12:32] I mean, for vivid-overlay [12:33] sil2100, it's in wily overlay, too, let me verify quickly wily is indeed fine [12:33] Ah, right, this was already after the switch [12:34] that wouldn't make sense to me [12:36] +1, but that's what it looked like before, I was focused on unity8 at that point, so might've not paid enough attention [12:36] so confirming on flo now [12:37] and mako for good measure [12:37] pmcgowan, off topic, did you hear about anyone losing the ability to adb into recovery on a manta (and hence the ability to flash it)? [12:38] * Saviq can sideload, flash in fastboot, and adb to android, but no adb to recovery :/ [12:38] Saviq, I have not [12:38] Saviq, my manta goes into a funny loop witht he screenn flashing, and will never shut down [12:38] pmcgowan, yup, saw that with flo as well [12:39] as if some input caused it to wake up [12:39] I suspect it needs an udpated device tarball [12:40] if I could find someone to update them [12:48] sil2100, pmcgowan, ah d'oh, no overlay on wily images yet, is why it was fine [12:51] greyback_, ↑ [12:51] sil2100, yup, wily+overlay broken, too [12:54] * sil2100 sighs [12:54] Ok, I'll revert it too [12:54] First, vivid === alan_g|lunch is now known as alan_g === marcusto_ is now known as marcustomlinson [13:03] Saviq, Mirv, pmcgowan: reverting UITK vivid [13:04] bzoltan_, ↑ [13:04] bzoltan_: ^ [13:09] hmmm, some strange things with the wily part I see [13:11] sil2100: ok [13:15] oSoMoN, it shouldn't be in 2 silos :) [13:16] sil2100, can you please dput qtmultimedia source package from ppa:jhodapp/ubuntu/ppa to the silo 29 PPA? [13:16] jhodapp: sure, any re-versioning needed? [13:16] sil2100, also, is it possible to remove qtmultimedia from the silo 55 PPA? [13:16] oSoMoN, i created silo 49 for it yesterday [13:16] sil2100, shouldn't be any need [13:16] jhodapp: sure [13:17] kenvandine, are you planning on landing silo 49 soon-ish ? [13:17] yes... after 41 [13:17] which is being verified right now [13:17] sil2100, trying to craft things in such a way that we can build indicator-sound and the source package for qtmultimedia in silo 29, then sync those two to silo 55 [13:17] Mirv, sil2100, any updates on bug #1378245? with overlay citrain just dist-upgrades everything from the overlay ppa [13:17] bug 1378245 in phablet-tools (Ubuntu) "citrain could use a more accurate way to upgrade from silos" [High,In progress] https://launchpad.net/bugs/1378245 [13:17] kenvandine, ok, thanks, so definitely in time for ota7, right? [13:18] oSoMoN, oh, it's in a silo with unity8 too [13:18] yeah, assuming qa verifies it in time :) [13:18] kenvandine, yes, that’s why I was asking, it currently is in two silos… [13:18] oSoMoN, i'll make sure it's in ready for qa today [13:18] cheers [13:19] it's unrelated to the unity8 fix in silo 3, so i'll remove it from that [13:19] kenvandine: Hey. Does adb reboot recovery work for you in arale? I'm trying to install lxc-android-config, and after adb reboot recovery, I can't adb shell to the device [13:19] rvr, no... you need to boot a special recovery [13:19] kenvandine, what's in silo with unity8? [13:20] saviq some apparmor profile ? [13:20] rvr, but... jibel pointed out you can install lxc-android-config without recovery [13:21] kenvandine: jibel: With citrain or using another trick? [13:21] jhodapp: package removed and copied [13:21] Saviq: I don't have any news regarding that one sadly... [13:21] kenvandine, I'm worried the package in silo 41 conflicted with a landing from yesterday [13:21] rvr, you unmount the file that breaks on upgrade then use citrin [13:21] just unmount something... [13:21] citrin [13:21] citrain* [13:21] jibel: Ok [13:21] kenvandine, train says unity8 is dirty, and I'd say it's likely true [13:21] jibel, which file does he need to umount? [13:22] there's too many peoples landing unity8 at the same time... [13:22] saviq: i'll rebuild unity8 in silo 41 [13:22] i already did that a couple times :) [13:22] we have to get that wizard fix in [13:23] Saviq, can i have a unity8 landing lock until rvr is done testing? :-D [13:23] kenvandine, I never remember which one is powerd which one is lxc-android-config, let me check [13:23] kenvandine, yeah, sure, /me needs to start looking at silos in flight apparently [13:23] robru, what's the workflow with conflicting silos these days? [13:24] /lib/udev/rules.d/70-android.rules [13:24] maybe that one? [13:24] kenvandine, /lib/udev/rules.d/70-android.rules [13:24] sil2100, thanks! [13:24] Saviq: I think everything is now handled by the 'silo is dirty' feature [13:24] rvr, sudo umount /lib/udev/rules.d/70-android.rules [13:25] sil2100, /me worried that's too late [13:25] it won't let us publish if it's dirty [13:25] yeah [13:25] but that means you have to re-test [13:25] and potentially QA, too [13:25] potentially [13:25] but depends on the change too [13:26] like silo 41 only changes one page of the wizard [13:26] sil2100, dont bother with the change to the watchdog until I talk to tony [13:26] kenvandine, well, sure, but what if the landing in the mean time changed it too, not even in a way that it conflicted VCS-wise, but runtime [13:26] sure [13:26] there is risk especially when APIs change, etc [13:27] which is why I mean "silo dirty" is too late [13:27] like with silo 22 it's not even dirty atm [13:28] rvr, so after you umount that file, you can use citrain to install [13:28] kenvandine: Thanks [13:28] Mirv, bzoltan_: hmmm... do you guys know what happened to the 1.3.1641+15.10.20150922-0ubuntu1 landing of UITK for wily? [13:28] but we've spent a good hour testing it, and we'd conflict with you if we wanted to put it under QA [13:29] now we're just gonna wait instead [13:29] it's fine in this case because we investigated a UITK breakage most of the time [13:29] but I'd be unhappy if we actually wanted to put it in under QA and only then realized there's another unity8 landing there first [13:30] Saviq, i guess you can search for silos with unity8 and check the status [13:30] and see there's another in ready for qa [13:30] but... maybe that should be kind of like the dirty flag [13:30] so you don't have to look for it [13:30] kenvandine, not even ready for qa, anything in flight [13:30] because someone else might be testing it by now [13:30] Mirv, bzoltan_: yyh, so it seems that landing was only released to vivid? [13:31] just show another silo is in the qa queue [13:31] sil2100, ? [13:31] Saviq, true [13:31] sil2100, https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/stable-phone-overlay?field.series_filter=wily [13:31] (if that's about uitk still) [13:31] Saviq: unrelated to the UITK regression, I'm talking about the previous UITK version [13:31] Saviq, but even more of an issue for silos that have already been tested, like 41 has been in ready for qa for 24 hours [13:31] sil2100, right ok sry :) [13:32] Saviq: the previous one was a dual landing and only released to vivid (probably manually, I see errors in the publish job and a manual m&c) [13:32] And that makes me a sad panda! [13:32] kenvandine, yeah, which is why I will be manually looking for conflicting silos from now on, but feels like some wasted manhours [13:34] Mirv, bzoltan_: uuuh, and I see that the latest UITK-gles version is older than the UTIK main version that got released! [13:34] Mirv, bzoltan_: that's bad [13:35] sil2100: I am no sure what does that happen? [13:35] Mirv, bzoltan_: generally it's safer when normal and -gles packages have the same versions, as some packages can hard-dep on the specific version [13:36] And if -gles has a lower one, it can cause a FTBFS [13:36] Anyway, trying to revert it as well [13:38] bzoltan_: anyway, this means that whenever you rebuild UITK in a silo, be sure to also re-build the -gles version [13:40] sil2100: it might be this was the webbrowser-app rebuild that bzoltan_ didn't do [13:40] sil2100: if it wasn't run by specifying webbrowser-app only [13:41] sil2100: 20150922 was when gcc was broken, so it was on purpose only released to vivid, to catch up with the next release [13:41] Ok [13:42] Actually [13:42] hah, I'll revert the wily versions by removing the wily packages from the overlay! [13:42] Since it's the first wily-overlay release [13:42] phew, saves me some time [13:42] seb128, i'm about to land the silo with all those new packages i had you review months ago :) [13:42] kenvandine, \o/ [13:43] kenvandine, lucasz pinged me to preNEW review earlier [13:43] trying to have a look today still [13:43]