=== Ursinha is now known as Ursinha-afk === Ursinha-afk is now known as Ursinha [03:49] morning [05:30] hello guys [05:41] hello [05:42] didrocks: indicators + qa packaging changes http://10.97.0.1:8080/view/cu2d/view/Head/view/Indicators/job/cu2d-indicators-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_ido_13.10.0+13.10.20130814-0ubuntu1.diff http://10.97.0.1:8080/view/cu2d/view/Head/view/QA/job/cu2d-qa-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_autopilot-qt_1.3+13.10.20130814-0ubuntu1.diff http://10.97.0.1:8080/view/cu2d/view/Head/view/QA/job [05:44] Mirv: +1 for both [05:49] didrocks: qtubuntu-android has received a lot of new dependencies from mir (libmirserver1) now that it builds mirserver and mirclient backends https://code.launchpad.net/~timo-jyrinki/cupstream2distro-config/platform_qtubuntu_new_deps/+merge/180036 [05:49] QA and Indicators published [05:49] sweet! [05:49] Mirv: re qtubuntu-android: the new gl* things are transient? [05:49] Mirv: like, should we just run with "check with whole ppa" [05:50] or you think they will be used everytime [05:50] (the mir part seems long term) [05:50] didrocks: it seems mirserver has stared depending on them [05:50] so not temporary [05:51] or not started, but qtubuntu started depending on mirserver [05:51] Mirv: interesting, so we don't install those by default? [05:51] Mirv: if they will be seeded on the CD, we can maybe live until we take a snapshot with check with whole ppa? [05:51] (not the mir dependens, we need to add them) [05:51] depends* [05:53] didrocks: hmm weird that they wouldn't be already there via mir. so to be exact since it's been a bit mystery to me, are the 'default' talking about default desktop seed? [05:54] Mirv: right [05:54] Mirv: I would suggest, let's add Mir [05:54] and then, run with "check with whole ppa" [05:55] once in distro, we'll retake a snapshot [05:55] and see how it goes [05:55] sounds good? [05:55] didrocks: sounds good, what about the boost lib? [05:56] let's see what pulls it in [05:56] libmirserver1 [05:57] Mirv: ok, and libmirserver1 isn't installed on the desktop by default, right? [05:57] (as long as we don't have unity-system-compositor) [05:57] didrocks: yep [05:57] so let's add it I would say [05:57] ok [05:58] Mirv: I think what we can envision for the future is that we don't block on those additional packages and so on [05:58] but it needs to turn the publication to manual [05:59] didrocks: removed the opengl ones https://code.launchpad.net/~timo-jyrinki/cupstream2distro-config/platform_qtubuntu_new_deps/+merge/180036 [06:00] Mirv: approved [06:00] Mirv: you can quiclky deploy it before this tick :) [06:00] ok deploying and running with check-whole-ppa [06:00] (2 minutes) [06:00] Mirv: no need for rerun, the tick is coming :) [06:00] ah right [06:00] so after that, rerun with check-whole-ppa [06:00] but let's have one run first [06:00] my clock says :00:41 already [06:00] it's :02 in fact [06:01] but shhh, don't tell anyone :p [06:01] :) [06:01] (and it's :53 in fact for raring) [06:02] deployed, with 6,5s extra seconds left [06:06] phew ;) [06:53] Mirv: I relaunched with check with whole ppa now that all the rest is finished [06:53] didrocks: hah, was just writing about that to you [06:53] thanks [06:53] ;) [06:53] yw [06:54] indicators prepare-ido failed because the merge request from the previous publishing wasn't ready yet [06:54] now it's merged [06:56] Mirv: great! you can relaunch the stack if you want all green, but not a biggie :) [07:00] didrocks: yeah, that's the only reason as such, but maybe it's again worth it :) [07:01] didrocks: ok now there'd be the platform packaging change http://10.97.0.1:8080/view/cu2d/view/Head/view/Platform/job/cu2d-platform-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_qtubuntu_0.52+13.10.20130814.1-0ubuntu1.diff === ivanka__ is now known as ivanka [07:02] mir emits xkbcommon keysyms, so that's why the libxkbcommon-dev dependency [07:03] Mirv: do you know why we have this second dh_auto_configure ? [07:04] didrocks: it probably does not hurt but let me check why it's being used in the first place [07:04] Mirv: thanks :) [07:05] Mirv: anyway, if it doesn't hurt +1 for publishing, just follow up on that to get it fixed if this is a typo :) [07:06] ok, I'll check it up and mark to the sheet [07:06] Morning! [07:09] sil2100: morning! daily stack all handled now (soon all green), feel free to start your day with other stuff :) [07:10] Mirv: thanks! [07:10] sil2100: good morning :) [07:10] good morning desktopers [07:10] \o/ [07:10] salut seb128 [07:10] hey Mirv sil2100 didrocks [07:10] hey seb [07:11] Mirv: awesooome ;) [07:17] hey sil2100! [07:18] didrocks: oh right, lp:~kubuntu-packagers/kubuntu-packaging/qtbase-opensource-src_5.0.2 would be now ready (enough). there's an upstream bug report with the patch attached, and I linked it to the patch in bzr. [07:18] Mirv: excellent, will do it in 5 minutes! [07:18] (well, rebuilding as well, so will take time :p) [07:35] didrocks: quick packaging question - if I'm doing a review of a package that has never ever been released to Ubuntu, and the changelog entry has like many entries stating that it has been released, should I remove those or leave them as they were? [07:35] sil2100: no, don't worry about it [07:36] Ok, thanks ;) [07:45] ok, all green, just made triple sure the new qtubuntu-android works fine on device as well [07:48] * didrocks likes green :) [07:49] thanks Mirv for the careful reviews :) [07:49] Yay for green [07:53] Mirv: ok then, I'm picking up the next release tick if you don't mind ;) [07:53] sil2100: tick's stealer! :) [07:54] Tricky ticky [07:54] sil2100: sure [07:54] :) [08:15] didrocks: when adding a completely new project to the cu2d-config, do I need Francis to enable the CI and autolanding bits? Or does a redeploy do all the stuff automatically? [08:16] sil2100: you need Francis to do the upstream merger part, yeah [08:19] sil2100: should it be in platform? shouldn't we have a service stack? [08:19] sil2100: like, will the people maintaining platform will be the same maintaining the services? [08:23] FYI if anyone else is having slow saucy shutdown, I filed bug #1212142 [08:23] Launchpad bug 1212142 in sysvinit (Ubuntu) "Slow shutdown on saucy with sendsigs waiting 10 seconds" [Undecided,New] https://launchpad.net/bugs/1212142 === slomo__ is now known as slomo [08:23] I eventually became annoyed enough to look at it a bit, now happy that I found a "kill em all!" workaround :) [08:25] didrocks: hm, we might do that now yes, since we could move the location-service to that new stack then too [08:25] didrocks: for me platform seemed ok for now [08:25] didrocks: but if you don't mind spawning a new stack, then I'm ok with that ;) [08:26] didrocks: so, creating the service stack [08:32] didrocks: I wonder if the D09add_ppa~phablet-team~ppa D09add_ppa~canonical-qt5-edgers~qt5-proper hooks are still needed [08:34] tvoss_: do you have any idea who will consume that and be upstream for all services like that? ^ [08:35] sil2100: also, for adding to daily release, we are asked to check that there are AP tests again [08:36] didrocks, the services will be consumed indirectly by apps, upstream is "us" [08:36] didrocks, @AP tests: I think apps should check for that [08:36] tvoss_: "us" is vague [08:36] tvoss_: is it the same team than the platform api team? [08:36] or another one? [08:37] didrocks, phonedations might be the team you are after [08:37] didrocks: of course, for now we want CI and autolanding only - the rest is added in the spreadsheet as TODO [08:37] tvoss_: ok, so platform stack sounds good then [08:37] sil2100: ^ [08:37] didrocks: there'd be the Qt Creator common files split + upgrade to saucy needing review/sponsoring [08:37] thanks tvoss_, as soon as we have apps consuming then, we need to have those running the same tests [08:37] I updated the doc with the new project place I did for those [08:37] Mirv: ah excellent! qtbase is still building [08:37] didrocks: ok then, sticking with platform then - no change in the MR ;) [08:37] didrocks, ack [08:38] tvoss_: but still, we'll need Francis to fetch our config code once he's up so that the upstream mergers are set-up [08:38] sil2100, ack [08:39] sil2100, anything you need from my side right now? [08:40] tvoss_: I have all I need, thanks :) Will get back to you once Francis sets everything up [08:40] sil2100, thanks [08:52] Mirv: I don't want to bother didrocks, so if you have a moment, could you review and approve https://code.launchpad.net/~sil2100/cupstream2distro-config/add_content-hub/+merge/180058 ? We just had a discussion and this seems to be the right place for the new component [08:52] Eeek, typo! [08:53] Mirv: wait, need to fix it [08:54] Mirv: ok, fixed, now the MR is ready [08:55] Mirv: can you prepare qtcreator-plugin-ubuntu for dailies (if it's not already?) [08:55] I'll have a look afterwards [08:55] I need to concentrate on system updates now [08:57] didrocks: aaah! I noticed something really bad! The nux part of the unity-support-test change didn't get merged ;/ [08:57] sil2100: why wasn't it merged? [08:58] didrocks: merge failed, *** No rule to make target `check-headless'. Stop. make[2]: *** [check-headless] Error 2 <- huh [08:58] can you please check with upstream [08:59] Doing that, but still ;/ DAMN === seb128_ is now known as seb128 [09:07] mpt: hey! on https://wiki.ubuntu.com/SoftwareUpdates#Phone, prompting section [09:07] Whenever an update is downloaded and ready to install, or an update download has failed repeatedly, or “Download future updates automatically” is set to “Never” and an update is available for download: [09:07] you just explained the label to show in the first case [09:07] not if download repeatedly [09:08] didrocks: added a couple last tweaks now, it should be ready for dailies [09:08] didrocks, good point, I'll fix that now [09:09] thanks mpt [09:09] Mirv: ok, is it urgent or can that wait a little bit (later today or next Monday?) [09:09] I really try to get the system update straight first :) [09:10] didrocks, https://wiki.ubuntu.com/SoftwareUpdates?action=diff&rev2=127&rev1=126 [09:10] didrocks: can wait. today would be preferred to next Monday, though, the P/Q/R users are already using this update. [09:12] Mirv: if I can't do it today, mind asking Ken? [09:12] but if it gets complicated (the common packages need to get to archives and then qtcreator sponsoring) then we'll move it to Monday [09:12] didrocks: sure, that's fine [09:12] mpt: perfect, thanks! [09:12] Mirv: thanks [09:13] sil2100: approved [09:14] Mirv: thanks! [09:27] didrocks: did we drop the rule that projects in a stack should be ordered alphabetically? [09:27] sil2100: no, we didn't [09:27] didrocks: the platform stack is awefully ordered then - I'll fix that in some merge === tkamppeter_ is now known as tkamppeter [09:30] sil2100: thanks [09:47] didrocks, Mirv: https://code.launchpad.net/~sil2100/cupstream2distro-config/cleanup_and_add_unity-mir/+merge/180077 <- the description states some overview of why to platform, but it's an open discussion as it's not really a 100% fit [10:17] mpt: when pressing "Install & Restart", should we have a countdown to cancel? [10:17] like 5s === MacSlow is now known as MacSlow|lunch [11:12] could someone fix cups ? it breaks alll images [11:12] The following packages have unmet dependencies: [11:12] cups-filters : Conflicts: ghostscript-cups [11:12] E: Unable to correct problems, you have held broken packages. [11:12] (all except touch :) ) [11:13] tkamppeter, ^ [11:14] ogra_, how did it go out of proposed if it breaks stuff? [11:14] seb128, i have no idea, i just get spammed with image build errors the whole morning :) [11:14] so i thought i should mention it ... [11:15] ogra_, yeah, thanks [11:15] seems an issue with https://launchpad.net/ubuntu/saucy/+source/gutenprint/5.2.9-1ubuntu2 [11:15] yeah [11:19] seb128: I have moved Ghostscript's CUPS filters from ghostscript-cups to cups-filters, making ghostscript-cups go away. According to didrocks I have added Conflicts/Provides/Replaces: ghostscript-cups to cups-filters and when I tested with "dpkg -i *.deb" ghostscript-cups got uninstalled, why does this not work with the images. What keeps ghostscript-cups on the system. [11:20] seb128, didrocks, I have even updated several printer driver packages satisfying their dependencies with cups-filters. [11:21] tkamppeter, hum, I'm not sure either [11:21] ogra_, do you know what package the builder tries to install? installing ubuntu-desktop in a pbuilder works [11:22] seb128, Gutenprint (the version you mention) is also updated to not require ghostscript-cups and accept cups-filters 1.0.36 instead. [11:24] here is one of the breaking build logs http://people.canonical.com/~ubuntu-archive/livefs-build-logs/saucy/ubuntu/20130814/livecd-20130814-i386.out [11:25] ogra_, not very helpful :/ [11:26] yeah [11:26] apt-get install printer-driver-splix printer-driver-hpcups printer-driver-gutenprint lsb-printing ghostscript foomatic-db-compressed-ppds cups-filters cups-daemon cups ubuntu-desktop [11:26] seb128, did you install the metapackage or the task ? [11:26] that works in a pbuilder [11:26] images use tasks [11:26] is that with ^? [11:26] yeah [11:26] ubuntu-desktop^? [11:26] for ubuntu-desktop [11:26] righgt [11:26] ok, that reproduces [11:28] seb128, only package which I know depends on ghostscript-cups is lsb-printing, but for that I have reported bug 1212012. [11:28] Launchpad bug 1212012 in lsb (Ubuntu) "ghostscript-cups got removed and the content moved to cups-filters 1.0.36, let lsb-printing depend on cups-filters (>= 1.0.36) | ghostscript-cups" [High,New] https://launchpad.net/bugs/1212012 [11:29] seb128, ogra_: I have ubuntu-desktop installed and it causes no problem. [11:30] tkamppeter, you need to install the task, not the meta packge ... thats what happens during image build [11:30] ogra_, do you know how tasks are defined? [11:30] (task dependency resolution is slightly different from metapackage resolution) [11:30] seb128, by germinate via the sseeds [11:35] seb128, ogra_: How does one install a task, where is it defined (which package), and how does one report a bug against it? [11:35] tkamppeter, sudo apt-get install ubuntu-desktop^ [11:36] seb128, this I did and it does not cause any problem. ubuntu-desktop was all the time installed even. [11:37] tkamppeter, I get the error in a pbuilder, not sure why though [11:38] ogra_, it looks like a cjwatson sort of issue, neither the seed nor the seeded packages depends on it [11:38] well, something pull sit in [11:39] ogra_, I don't see anything in the seeds and rdepends is fine [11:39] ogra_, it seems like the tasks didn't get updated ... is that happening automatically on every image build or...? [11:40] iirc the issue with meta vs task is that the "or deps i.e. | " are resolved in the opposite order [11:40] it should happen on every publisher run [11:41] (meta takes the first option, task takes the last one in such a case) [11:41] hum, maybe that's the issue then [11:42] but I don't understand that enough to have a clue what to change/what source is the problem then [11:45] seb128, ogra_: I consider that as a bug. First it is more intuitive if the first item gets priority, second, different programs should not use different priority orders on the same data. [11:45] \o/ running for making an API clear in one's mind -> success! [11:45] getting down from 20 calls to 6 ;) [11:45] didrocks, yeah, exercice is good to get ideas in shape ;-) [11:46] seb128, ogra_ I vote for the first item being prioritized, not only more intuitive but also packages probably think that way as package installation/update after install behaves that way. [11:47] seb128, ogra_, and if this leads to failure, the program should try whether it succeeds using the second item. [11:47] tkamppeter, heh, thats not a voting matter i fear ... its a technological difference in both installation variant [11:48] *variants [11:48] iirc cjwatson knows about it, probably talk to him about a work around [11:48] tkamppeter, the CD building stuff is that way for years, I don't think either of us know enough about the problem space to redesign things, we don't have resources for that sort of work anyway atm [11:48] it's probably the way it is for good reasons [11:49] * ogra_ thinks its a bug ... but one thats not easy to fix === MacSlow|lunch is now known as MacSlow [12:33] fginther: hello! [12:33] Good morning! [12:34] sil2100, good morning indeed! [12:34] fginther: I have some business for you, sadly ;) [12:35] sil2100, if it's your business, then it's good business :-) [12:36] fginther: ok, so maybe first thing first ;p I need to rename the LP project for lp:hollywood to lp:mediascanner [12:36] fginther: I would need you to switch the merger/CI bits to that when that happens [12:38] sil2100, no problem, just ping me and I'll do an MP [12:47] didrocks: sorry to disturb you, but you think the https://code.launchpad.net/~sil2100/cupstream2distro-config/cleanup_and_add_unity-mir/+merge/180077 is ok? Since if on first glance unity-mir fits to platform stack, then cool ;) [12:47] (no one else is around to approve :<) [12:48] sil2100: I saw a MP with unity-mir in the unity8 stack [12:48] can you check? [12:49] Checking [12:51] didrocks: right, Sergio added that - it's hard to say which place is a better fit [12:51] didrocks: even if we decide on unity8, I'll change my MR to at least fix the ordering in the platform stack [12:52] sil2100: depends who is upstream and if the ABI is stable [12:53] didrocks: I know the platform guys had some commits, but true, the unity8 guys have the most input there... so I guess unity8 it is then [12:54] Although to me it fits better in platform, as it's more low-level [12:55] didrocks: I'm approving Sergio's branch and changing mine to simply a cleanup one [12:55] ok [12:56] sil2100: we need to ensure unity8 is depending on platform then [13:19] kenvandine: morning! [13:19] kenvandine: are you ready for some MR reviews ;) ? [13:19] sil2100, good morning [13:19] sure [13:21] kenvandine: https://code.launchpad.net/~sil2100/cupstream2distro-config/cleanup_and_add_unity-mir/+merge/180077 <- this one, the name is misleading - it only sorts the platform stack here [13:22] kenvandine: and this one to unblock unity8 stack https://code.launchpad.net/~sil2100/cupstream2distro-config/add_extra_libupstart1/+merge/180131 [13:22] kenvandine: thanks! [13:23] sil2100, kenvandine: good morning! [13:24] robru: morning! Woha, that's EARLY [13:24] sil2100, yes, i am still quite jetlagged from GUADEC :-/ [13:25] sil2100, kenvandine: do either of you know what's happening in jenkins? I saw a couple yellows due to packaging changes; I reviewed them and published them, but the red ones are baffling to me. one looks like the test environment itself is broken. [13:26] robru: you mean, the current state of the stacks? [13:26] robru: one red is because of this: https://code.launchpad.net/~sil2100/cupstream2distro-config/add_extra_libupstart1/+merge/180131 [13:26] robru: HUD is yellow and let's keep it this way for now, since the diff had an invalid changelog (which I fixed in a MR), but still need unity-lens-apps checking [13:27] sil2100, oh, I thought I saw your fix landed in trunk? [13:27] robru: SDK is red because... well, flacky test, but not re-running it now since the next release will start soon [13:28] sil2100, bad news, I already published hud. I'm a bit confused -- I thought I saw your changelog fix had landed, so it was ok to publish? or did I just make a huge mistake? [13:28] sil2100, approved [13:28] robru: ouuuch [13:29] robru: so, what happened is: [13:29] robru: when it's in manual publishing, you would have to re-run the whole stack to get this change in - did you just publish or run the whole stack? [13:29] just publish [13:30] robru: besides, remember that we should always consult people with upload rights before we publish things with packaging changes [13:30] robru: so either kenvandine or didrocks should give it a big ACK [13:30] didrocks: ^ [13:30] didrocks: I hope it didn't break anything now? [13:31] robru: also, remember to consult with the currently working vanguard of the release process as per the schedule ;) Since this way we won't conflict [13:32] I'm usually taking care of this release as it's in my main work hours [13:32] sil2100, ok [13:32] sil2100, sorry. i don't understand the process very well yet [13:33] didrocks: so, the thing is, robru published a libcolumbus version that had a bad looking changelog entry - I fixed that in a merge, but it got then published manually, which causes jenkins to not being able to commit the 'releasing' changelog modification to trunk... [13:33] sil2100, oh, does it make a merge conflict on the changelog? ahhhh [13:34] robru: yes! Sadly ;) https://code.launchpad.net/~ps-jenkins/libcolumbus/latestsnapshot-1.0.0+13.10.20130814-0ubuntu1/+merge/180127 [13:34] fginther: hi! lp:hollywood got renamed to lp:mediascanner \o/ [13:34] sil2100, how can I fix this? can I make a separate branch with a better changelog or does somebody need to fuss around inside jenkins to fix it? [13:35] fginther: can you also switch it in the configs when you have a moment? [13:35] sil2100, no problemo [13:35] robru: I think we'll need some help from didrocks on how to proceed here, since now the version with the no-good changelog went into distro [13:36] robru: so we need to wait, since our possible options are: [13:36] 1) drop the published version from distro, getting the right 'good-looking' changelog into trunk and re-publishing [13:36] 2) leave the published version in distro with the not-so-good changelog and revert my fix for trunk, therefore unblocking jenkins merger [13:37] robru: which still leaves some questions, such as what to do then with the rev number... ;/ [13:37] fginther: thank you! [13:38] sil2100, wow, I really cocked things up. maybe I should just go back to bed :-/ [13:41] * didrocks in a meeting, soon back :p [13:41] oh boy [13:44] seb128, ogra_ psivaa, see bug 1212239 [13:44] Launchpad bug 1212239 in cups-filters (Ubuntu) "cups-filters is reported to have unmet dependencies with the latest saucy server installations" [Undecided,New] https://launchpad.net/bugs/1212239 [13:44] sil2100: please write down SDK flacky tests [13:45] sil2100: dropping a version from distro is hard [13:45] if nobody has done it yet, I'll add libupstart1 to the packages for unity8 stack, since it seems to be a depends on unity8-private [13:45] didrocks: there shouldn't be a need to drop anything, really [13:46] the upload looks sane, we just need to bump the version [13:46] sil2100: so better to "fix" trunk with the right changelog [13:46] cyphermox: drop? [13:46] cyphermox: it's a check for new deps that aren't on the CD [13:46] it's harder now that there is touch [13:46] but when I'll have time, I'll try to make it easier [13:46] didrocks, so ... thanks for making me try to think of a word for "six times per day" [13:46] maybe there is a French one? [13:46] didrocks: will do [13:47] cyphermox: did that [13:47] cyphermox: it's already approved by kenvandine I think [13:47] cyphermox: https://code.launchpad.net/~sil2100/cupstream2distro-config/add_extra_libupstart1/+merge/180131 <- merged [13:47] I'll redeploy the stack [13:47] rickspencer3: I have one which corresponds to 12 but I doubt we want to use it :p [13:48] seisfoisparjour? [13:48] chaqueqautheur? [13:49] didrocks: as for fixing the changelog... won't there be any problems with the rev number in the merged in (by jenkins) release changelog? [13:49] maybe German can help here? [13:49] didrocks: once I revert my fix [13:49] didrocks: since there will be one additional commit ;) [13:49] sil2100: it's only used for collecting the changelog, so if it's not more than what was released, it's fine (you put the changelog generated by dailies) [13:49] rickspencer3: http://fr.wiktionary.org/wiki/chi%C3%A9e is 12 ;) [13:51] uh [13:51] (don't use it next time your are in France ;)) [13:51] didrocks, I don't think that will work, no [13:51] told you ;) [13:51] haha [13:51] quad-hourly? [13:52] didrocks: ok, so I'll remove my changelog entry (leaving the released empty changelog), commit the jenkins release changelog change and reject jenkins's original merge (since I'll merge it in myself [13:52] ) [13:53] sil2100: sounds good to me [13:59] rickspencer3, quaternourly is the only thing I can come up with that sounds reasonably sane in english. [13:59] robru, wfm [13:59] didrocks: https://code.launchpad.net/~sil2100/libcolumbus/fix_madness/+merge/180144 <- does this make sense? [13:59] alternatively, didrocks can make it every hour so we can just say "hourly" [13:59] :) [14:00] nooooooooooo [14:00] rickspencer3: we need to have everyone looking at that results every hours as well ;) and really fast builders! [14:00] (and really fast tests: unity 7 ones are taking 2h) [14:00] sil2100: you can fix the changelog with the right infos [14:00] sil2100: if you prefer [14:01] rickspencer3, my vote would be to run them every 6 hours. Then we can call it "sexa-hourly"! [14:01] ahah [14:01] rickspencer3: then, you will ask for minutely! I know you! ;) [14:03] "octourly" has a nice ring to it if we want to run just 3 times per day. [14:03] didrocks, I don't know "minutely" doesn't role off the tongue [14:03] I think rather, we do it "continuously" ;) [14:05] rickspencer3: can't on every commit with the current distro layout though (and current non ABI stability), but if we fix both, that's something which will be possible [14:05] :) [14:10] sil2100: did you see my answer? [14:15] Ok [14:16] didrocks: by the right infos you mean the right commit rev? [14:16] sil2100: no, I meant a meaning changelog [14:16] Ah, ok ;) [14:17] if there is a diff with distro though, it will get rereleased [14:17] which is not a biggie IMHO [14:17] (at least apt-get changelog will have a meaningful changelog) [14:17] didrocks: what about the 'Automatic snapshot from revision 452' ? Should I also bump it to 453 or leave as it was released? [14:18] sil2100: it's just telling to "collect commits message which have no debian/changelog change in the diff from rev +1" [14:18] sil2100: so based on that, make your call :) [14:18] didrocks: ok, fixed the changelog to have the meaningful one ;) [14:19] sil2100: approved (revert jussi approval which was on the previous commit) [14:19] sil2100: on unity-mir [14:19] did you see what I told? [14:19] is the unity-mir ABI stable? [14:20] does it linked against the server or client Mir API? [14:20] that will help in setting it up [14:20] if it links against the server one [14:20] you need something similar to unity-system-compositor [14:20] with force_rebuild and the condition [14:20] Let me poke greyback about that [14:20] + the stack needs to dep on the Mir one [14:20] thanks [14:21] greyback: is unity-mir API-stable? :) [14:21] sil2100: it links against both server & client. So not stable [14:21] sil2100, which stack for mediascanner? [14:22] didrocks, why would we have a countdown? [14:22] (And that isn't really a desktop question:-) [14:22] sil2100, media.cfg? [14:22] mpt: we can move to #ubuntu-touch if you prefer :) [14:23] mpt: basically if a user spaw the ui and misclick [14:23] mpt: he didn't want to apply the update [14:23] you can have a 5s grace period [14:23] before the phone reboot [14:24] fginther: hm, we didn't add it to the stacks yet, let me think for a moment [14:24] didrocks, there's nothing nearby you might have been aiming for instead [14:24] mpt: if you click "show" on the unity8 ui, you have system-settings with the button available [14:25] yep [14:25] mpt: just telling you about it. I saw that google is doing that for important updates that will destroy your state [14:26] didrocks, in most cases, destroyed state would be a bug in the app ... But in any case, this whole screen *is* the confirmation step. You get here after expressing initial interest in installing the update. [14:26] mpt: ok, fine by me :) [14:32] fginther: I think media might make sense [14:32] sil2100, ack [14:36] fginther: thanks again! [14:37] mpt: we don't have the number of downloads, there is just "one" download [14:37] mpt: as long as we don't do apps updates, just system ones [14:37] didrocks, yep, so for now it'll always be 1. :-) [14:37] ok :) [14:37] didrocks, apparently non-numeric badges are verboten. [14:38] mpt: thanks for refreshing my poor german :) [14:38] (was still in my scope of knowledge, phew!) [14:38] mpt, are click packages/apps updates going to be in system settings as well? [14:39]