[01:28] <beyondsociety> disconnect
[01:47] <dotyet1> hello there
[01:47] <dotyet1> I am looking for some hardware advice for ubuntu laptop
[01:47] <dotyet1> am I in the right place?
[04:30] <Mirv> alex-abreu: hello, regarding the problem robert already pinged you about, I filed a bug #1214232 with autopilot log attached. there has been successful runs before, on Friday, so something has changed somewhere definitely
[04:30] <ubot2`> Launchpad bug 1214232 in unity-webapps-qml "unity-webapps-qml autopilot tests started failing on nvidia machine" [Critical,New] https://launchpad.net/bugs/1214232
[05:23] <pitti> Bonjour tous le monde !
[05:23] <Tm_T> moin
[05:23] <Mirv> moin Tm_T
[05:58] <didrocks> hey Mirv! looking at the time, was wondering if you were blocked by manual publishing or everything's fine this morning?
[05:59] <didrocks> (apart from webapps as you sent the email, which is blocking apps I guess)
[05:59] <Mirv> didrocks: I just noticed you had joined at some point, was going to point you out to http://10.97.0.1:8080/view/cu2d/view/Head/view/Indicators/job/cu2d-indicators-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_indicator-messages_13.10.1+13.10.20130820-0ubuntu1.diff
[05:59] <Mirv> there's the unity-mir preNEW, otherwise ok (looking at unity7, let's see next run)
[05:59] <didrocks> Mirv: +1 on indicators
[06:00] <didrocks> Mirv: there is unity-mir and unity8 in fact
[06:00] <didrocks> unity-mir, +1, I've already reviewed it yesterday
[06:00] <Mirv> ok
[06:00] <didrocks> (I'll then NEW it)
[06:00] <didrocks> unity8 is ok for you?
[06:00] <Mirv> yes, unity8 itself as well
[06:00] <Mirv> it's ok for me
[06:00] <didrocks> seems legit to me, +1
[06:01] <didrocks> Mirv: if you want for me in the morning, should I say I when I join? :)
[06:01] <Mirv> ok
[06:01] <didrocks> Mirv: FYI, I deprovisionned the ati machine for the Mir team to be able to test and debug
[06:01] <didrocks> (so tests are running on both intel and nvidia only)
[06:02] <Mirv> didrocks: hehe, I'll poll you, I was just focused on qtconnectivity copyright issues for a while so I then suddenly noticed it was already almost 6am cycle time
[06:02] <Mirv> yeah, I read about it
[06:02] <didrocks> :)
[06:02] <didrocks> ok, let's see next run now!
[06:03] <didrocks> (magners' machine is slightly late it seems for the clock)
[06:03] <didrocks> hum, it's not, maybe it's just jenkins then
[06:15] <pitti> hey didrocks
[06:16] <didrocks> good morning pitti
[06:16] <pitti> didrocks: FYI, mangners jenkins is behind, it got stuck on trying to publish a deleted job
[06:16] <pitti> didrocks: plars worked around it by creating a dummy job, it's catching up
[06:17] <didrocks> pitti: ah, was it an indicators-client one?
[06:17] <pitti> cu2d-indicators-head-1.1prepare-indicators-client
[06:17] <didrocks> (I saw one empty job with that name)
[06:17] <didrocks> interesting, I wonder if the stack was deployed before the job was removed
[06:17] <didrocks> (to get *indicators-client job outside the loop)
[06:18] <didrocks> thanks for the info!
[06:32] <mlankhorst> mmmmmmmorning
[06:33] <didrocks> hey mlankhorst, how are you?
[06:57] <didrocks> Mirv: you're deploying this new service stack? (next run will pick it as soon as you pull the config on magners, but only do that after deploying please)
[06:59] <didrocks> Mirv: interesting that ubuntu-fi defaulted to 64 bits, we had the same discussion at ubuntu-fr and kept the 32 bits
[07:00] <didrocks> at the time of the LTS, one of the discussion was in particular the netbook, where 32 bits was the vast majority
[07:04] <Mirv> didrocks: yes, I can deploy it before the next run
[07:04] <didrocks> Mirv: excellent! Nice to have that stack :)
[07:04] <Mirv> didrocks: the netbooks were the sore point, true, although some mistakenly thought Atom N4* series were also 32-bit only
[07:08] <didrocks> ah, indeed
[07:08] <didrocks> I guess for us, next LTS is the right turning point for 32 -> 62
[07:09] <didrocks> (and screw the minority like seb128 :p)
[07:13] <sil2100> Morning!
[07:13] <didrocks> hey sil2100, how are you today?
[07:15] <sil2100> didrocks: fresh! How about you? :)
[07:16] <didrocks> sil2100: I'm good thanks ;)
[07:16] <didrocks> everything went fine yesterday evening with robru? didn't get any blocker?
[07:18] <sil2100> didrocks: there was that indicators issue that I filled a bug about, but besides that it went rather fine - I wonder if he pushed it further when he got back from lunch ;)
[07:18] <didrocks> sil2100: not sure, nice work ;)
[07:18] <sil2100> didrocks: at least now all the ??? he had are cleared up
[07:18] <didrocks> you will continue on the following days? I think he need to see more "special cases"
[07:18] <didrocks> great!
[07:22] <didrocks> Mirv: did you get news from robru on the ubuntu-ui-extras?
[07:22] <sil2100> didrocks: will do - although today he's in travel, so next tutorial will be tomorrow
[07:23] <didrocks> sil2100: right ;)
[07:25] <Mirv> didrocks: not really, I only read the passing lines in backlog
[07:26] <Mirv> but he did a lot of other daily release stuff so maybe later
[07:26] <didrocks> ok ;)
[07:26] <didrocks> (just NEWed unity-mir btw)
[07:26] <didrocks> so probably a useless rebuild has been done
[07:48] <seb128> good morning desktopers!
[07:52] <Sweekshark> seb128: Good morning, seb, Good morning desktopers!
[07:52] <didrocks> salut seb128!
[07:52] <didrocks> hey Sweekshark
[07:52] <seb128> hey didrocks Sweekshark
[07:54] <Sweekshark> xnox: libreoffice autoconf doesnt seem to find boost date time anymore, if you have a hint why, Im all ears for it ...
[07:55]  * Sweekshark diggs into the pbuilder ..
[08:01] <Laney> O HAI!
[08:02] <seb128> oh, a Laney!
[08:02] <seb128> Laney, welcome back, how were holidays and debconf?
[08:02]  * Laney looks around for one of those
[08:02] <Laney> holidays very relaxing and enjoyable
[08:03] <Laney> debconf informative interesting and also enjoyable
[08:03] <seb128> great
[08:03] <Laney> good to put names to faces (was my first one)
[08:03] <seb128> do you plan to write a conf report about debconf? was there anything there specially interesting for us?
[08:04] <pitti> hey Laney, welcome back!
[08:04] <Laney> yeah we're writing one
[08:04] <seb128> excellent
[08:04] <pitti> enjoyed the Swiss mountain air? :-)
[08:04] <Laney> some converstaions about mir and stuff but I don't think there will be anything ground breaking
[08:04] <seb128> what about upstart?
[08:04] <Laney> pitti: yes! And the Swiss lake swimming ;-)
[08:05] <Laney> ah, yeah jodh gave a presentation that was quite well received it seems
[08:05] <Laney> lennart and kay also came and gave one too
[08:05] <pitti> ah, the eternal battle
[08:05] <seb128> hehe
[08:05] <seb128> well, battle is over for us I guess
[08:05] <Laney> but some people said they misjudged the debian audience
[08:05] <seb128> with the number of things that are being built around upstart for touch
[08:05] <Laney> we'll see, it'll go to the TC sooner or later for a decision
[08:06] <seb128> right
[08:06] <seb128> good that we stopped fighting over that at least
[08:06] <pitti> Laney: like "do we want to keep non-linux arches"?
[08:06] <darkxst> hey desktopers
[08:06] <seb128> hey darkxst
[08:07] <Laney> pitti: I suppose if someone can come up with a port for upstart that'll be a vote in its favour
[08:07] <Laney> also the CLA was a bit of an issue
[08:07] <Laney> (obviously)
[08:07] <darkxst> hey seb128, any progress on the indicator-keyboard stuff?
[08:08] <pitti> Laney: I don't see that being a realistic option, TBH
[08:08] <pitti> and for sure we wouldn't take it
[08:08] <seb128> darkxst, hey, not sure, I was not really online in the last days, better to check with cyphermox and jbicha about it
[08:08] <Laney> right
[08:08] <Laney> there will be some kind of debian branch or so
[08:08] <seb128> Laney, how is your backlog? did you manage to read emails and stuff during debconf?
[08:09] <Laney> emails are ok
[08:09] <pitti> it's "always support sysvinit" or "drop non-linux" in the end, everything else is just a giant non-sustainable maintenance mess
[08:09] <Laney> I don't know what the status of s-s is though, maybe you can tell me what's up there
[08:10] <darkxst> seb128, ok will do
[08:10] <seb128> Laney, so, let me think, we didn't have that many changes while you were not here
[08:10] <seb128> Laney, I added the battery panel, which is 75% done now, including charge graph
[08:10] <Laney> did we get any of the widgets / APIs we were waiting for
[08:10] <Laney> oh wow, that looked hard
[08:10] <seb128> Laney, Ken did most of cellular, you can pick a carrier now
[08:11] <seb128> but he got pulled away from system settings for the end of the month
[08:11] <seb128> he's helping with the content picker/content hub
[08:11] <seb128> which we need for background...
[08:12] <seb128> Laney, yeah, battery was "fun" :p I spent most of a week on it ... I still have a mp waiting if you feel like reviewing today, Ken is too busy
[08:12] <desrt> mfisch: it doesn't make sense to run glib-compile-schemas in a directory that only contains overrides because overrides can only affect schemas within the same directory.
[08:12] <Laney> ok
[08:12] <seb128> Laney, on toolkit front, the OptionSelector has been approved by Saviq, it just needs another look by the sdk team to stamp it as fine and it can land
[08:13] <Laney> seb128: anything in particular to work on there?
[08:13] <seb128> Laney, unitymenumodel is working in unity8 now, we have the new indicators...hopefully we should be able to use it in system settings soon
[08:13] <Laney> nice
[08:13] <seb128> that's about it I think
[08:13] <seb128> desrt, hey, how are you?
[08:13] <Laney> how was berlin btw? get much done? :P
[08:14] <seb128> Laney, lol, get nothing done you mean :p
[08:14] <Laney> ;-)
[08:14] <Laney> I'm sure you at least had some tasty ice cream
[08:14] <seb128> Laney, thursday was a national holiday, and desrt and larsu were around, so I ended up taking friday as a vac as well
[08:14] <Laney> ah ok
[08:14] <Laney> didn't know if it was an unofficial sprint or not
[08:14] <seb128> we had fun, and ice cream yes ;-)
[08:15] <seb128> no, I just decided to visit dholbach, I told him I would come to Berlin for years, and that seemed a good time
[08:15] <seb128> and larsu lives there now
[08:15] <seb128> and desrt was around for holidays
[08:16] <Laney> neat
[08:16] <seb128> so good timing to see people and enjoy a bit the city ;-)
[08:23] <seb128> Laney, when you asked "anything particular to work on there", that was system settings?
[08:23] <Laney> yep
[08:23] <seb128> let me think
[08:24] <seb128> didrocks is doing system updates, but he's on holidays starting end of week, so security&privacy is something that needs work
[08:24] <seb128> I've done the "location" subpanel in the plane yesterday
[08:24] <seb128> but if you want to do the other UI bits, please take that
[08:25] <seb128> date&time didn't move while you were not around, but mpt/tony have been discussing on the phone list some of the specific
[08:26] <seb128> the wiki changed a bit due to that
[08:26] <seb128> Laney, otherwise, a new glib is out since today
[08:26] <Laney> yeah, saw that
[08:26] <seb128> Laney, and https://code.launchpad.net/~seb128/ubuntu-system-settings/battery-full-charge-info/+merge/180146
[08:26] <Laney> and queued that already
[08:26] <Laney> just replying to some emails
[08:26] <seb128> Laney, that's all I've on my list I think
[08:27] <seb128> great
[08:29] <xnox> Sweekshark: multiarch.
[08:31] <sil2100> Mirv: do you have a moment to cross-check packaging?
[08:31] <sil2100> For daily-release
[08:34] <Sweekshark> xnox: urgh. alright.
[08:34] <darkxst> pitti, made a new MP for the ppa retracing patch
[08:35] <pitti> darkxst: I saw, thanks
[08:35] <pitti> darkxst: what is "external_only = 'ProcMaps' in report" supposed to mean/do?
[08:35] <pitti> darkxst: ProcMaps will always be in the report
[08:35] <xnox> Sweekshark: all libs/headers got moved into "/usr/[include|lib]/$(DEB_HOST_MULTIARCH)/" not sure what configury libreoffice uses.
[08:36] <attente> Laney, desrt mentioned you've seen this problem before? http://paste.ubuntu.com/5952631/ with the dconf-criticals?
[08:37] <pitti> darkxst: also, why does this need all the dynamic PPA stuff? wouldn't you just add the PPA as an apt source in your sandbox configuration?
[08:39] <Laney> attente: don't remember seeing that exact thing but I did override XDG_RUNTIME_DIR in some package build(s) because it wasn't created in a buildd environment
[08:39] <Laney> I tried at the time to ask if /that/ was a bug but nobody told me :P
[08:40] <Laney> also, why is everyone in Canada already up?
[08:40] <xnox> s/already/still/
[08:41] <Laney> aaaaa
[08:43] <Laney> why is my application lens returning 0 results, and why does Firefox (when launched manually due to this - from the /terminal/; alt-f2 refuses to run it too) tell me that "The bookmarks and history system will not be functional because one of Firefox's files is in use by another application. Some security software can cause this problem."
[08:43]  * Laney cries
[08:44] <seb128> do you have a running firefox process blocked?
[08:44] <seb128> that happened to me in the past
[08:44] <Laney> just booted, so that would be weird
[08:44] <Laney> it usually gives a different message in that case
[08:44] <seb128> no chrisccoulson there :/
[08:44]  * Laney tries safe mode
[08:45] <Laney> same
[08:46] <Laney> it goes unresponsive after a few seconds too
[08:46] <Laney> hahaha
[08:46]  * Laney looks for a brown paper bag
[08:46] <Laney> enospc
[08:46] <seb128> lol
[08:46] <Mirv> sil2100: I think yes
[08:47] <Sweekshark> xnox: k, digging into the joys of debugging AX_BOOST_DATE_TIME in aclocal ...
[08:48] <xnox> Sweekshark: yeah I hate A*_BOOST_* they are horrible. But i think it should be able to take a --boost-date-time or BOOST_DATETIME with update locations passed to the configure script.
[08:48] <xnox> or some such.
[08:49] <stgraber> Laney: haha, was just about to suggest that this sounded like ENOSPC (disk space or inode)
[08:50] <Laney> the brave new world of SSDs
[08:50] <davidcalle> Laney, wild guess : the firefox bookmarks scope could be misbehaving and the bookmarks db is locked (look for a firefoxbookmarks process to kill)
[08:51] <Sweekshark> xnox: https://twitter.com/autotools_/status/352130180392828928
[08:53] <xnox> Sweekshark: =)))))) LOL
[08:54] <davidcalle> Laney, that's unlikely, since you have to invoke it from the Dash with "web:", then it dies when you are done using it, but it could explain the error message
[08:54] <Laney> davidcalle: it was ENOSPC
[08:54] <Laney> I was getting local files returned but not applications
[08:55] <mlankhorst> :P
[08:55] <Mirv> didrocks: hmm, so I deployed misc + platform + services without errors, and run bzr pull at magners. is that all of it, or should something else be done so that the new stack would show at http://10.97.0.1:8080/view/cu2d/view/Head/ ?
[08:55] <didrocks> Mirv: ah right, asking to create the view (as per FAQ IIRC), but that's only something jibel does
[08:56] <didrocks> Mirv: but if we click on "all", we should see the head job for services
[08:56] <Laney> sil2100: did you see that libmediainfo got fixed?
[08:56] <didrocks> right?
[08:56] <sil2100> Laney: yay! Awesome, missed that, but still happy ;)
[08:56] <Mirv> didrocks: oh, so it is. interesting, good. I didn't find in FAQ, but maybe it's there still.
[08:57] <Laney> sil2100: so whatever project it was (can't remember) needs to back out that workaround now
[08:57] <Laney> also if they worked around the .pc file being borked they can stop doing that too
[08:57] <Mirv> I'll ask jibel when he's around
[08:58] <sil2100> Mirv: I'm re-running indicators
[08:58] <didrocks> Mirv: mind as well updating the FAQ if you have time? :)
[08:58] <didrocks> Mirv: sometimes having an external view is good :)
[08:58] <Mirv> didrocks: ok, will update as well, later
[09:00] <sil2100> Mirv: in the meantime, could you take a look at:
[09:00] <Mirv> sil2100: ok
[09:00] <didrocks> thanks!
[09:00] <sil2100> https://code.launchpad.net/~hollywood-team/mediascanner/trunk <- for the cross-check
[09:00] <Mirv> so, I guess I can now remove the jobs that were moved (ubuntu-keyboard, location-service)
[09:00] <sil2100> And:
[09:00] <Mirv> sil2100: will do, later :)
[09:01] <sil2100> Mirv: https://code.launchpad.net/~unity-team/unity-scope-mediascanner/trunk
[09:01] <sil2100> Thanks ;)
[09:05] <didrocks> sil2100: if you get that in the next run (location-service), FYI, I approved: https://code.launchpad.net/~thomas-voss/location-service/gcc-4.7-by-default/+merge/180953
[09:16] <darkxst> pitti, the procmaps was supposed to replace this line -> http://bazaar.launchpad.net/~apport-hackers/apport/trunk/view/head:/apport/sandboxutils.py#L155
[09:16] <darkxst> i forgot to remove that though
[09:16] <darkxst> the dynamic stuff is helpful, since we end up with lots a traces with for example xorg-edgers or ricotz packages in the dependencies
[09:17] <sil2100> didrocks: ACK
[09:19] <darkxst> pitti, once you hit a missing package in the trace, it generally seems to break the rest of the backtrace, although that might be a bug I guess
[09:22] <darkxst> since I don't ever recall seing that behaviour when using gdb directly
[09:29] <pitti> darkxst: ah right, ProcMaps won't be in reports for apport-valgrind; it was for that
[09:35] <sil2100> didrocks: would you mind if I enable mediascanner for daily-release? It will be integration-tested in the unity-scope-mediascanner package that we will enable soon
[09:36] <didrocks> sil2100: sure, if the FTBFS is fixed
[09:36] <sil2100> didrocks: the fix is just landing
[09:36] <sil2100> didrocks: thanks!
[09:39] <didrocks> yw!
[09:39] <didrocks> sil2100: all good on indicators-messages?
[09:40] <sil2100> didrocks: http://10.97.0.1:8080/view/cu2d/view/Head/view/Indicators/job/cu2d-indicators-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_indicator-messages_13.10.1+13.10.20130820.2-0ubuntu1.diff <- I guess so, although my revert also reverts some added changelog entries ;) Is that ok?
[09:40] <sil2100> (some that were added in the changelog history)
[09:41] <didrocks> sil2100: yeah, that's fine, not history that was in Ubuntu
[09:41] <didrocks> so +1
[09:41] <sil2100> Mirv: publishing indicators
[09:41] <didrocks> sil2100: as the revert was impacting though the changelog
[09:42] <didrocks> sil2100: you should have set the content manually
[09:42] <didrocks> (right now, it's quite sparse)
[09:48] <Sweeksha1k> xnox: yep, seems to be solved easily. Now I run into an issue with lpsolve ... which shouldnt happen of course as nothing changed there really. oh fun.
[09:49] <xnox> Sweeksha1k: point me to your patch / forward to debian. Boost is multiarched in experimental.
[09:51] <Sweetshark> xnox: will do -- _rene_ will pick it up anyway when pushed, I guess.
[09:57] <Sweetshark> xnox: the current patch is http://pastebin.com/UfnDCmSw -- lets see if that is all that is needed.
[09:57] <sil2100> didrocks: I've been wondering about where the mediascanner project should go - originally Francis put it to media, and it fits more or less, but mediascanner is more like in the 'unity' upstream than media one, and we'll have to add a stack dependency of unity -> media then
[09:58] <sil2100> didrocks: on the other hand, media seems like the right place, as not only unity scopes will use it, but also media apps
[10:01] <sil2100> I guess I'll leave it there
[10:02] <didrocks> sil2100: I think unity is fine then
[10:02] <didrocks> sil2100: I would avoid having unity being a dep of anything
[10:02] <didrocks> ah, or you mean the other way around
[10:02] <didrocks> media depends on unity
[10:02] <didrocks> let's look at the stack ordering
[10:02] <sil2100> No, I mean unity deps on media
[10:03] <sil2100> In case if mediascanner would stay in media
[10:03] <sil2100> The thing is, unity stack is a nice place for mediascanner too, but what if other media apps will start using it?
[10:03] <didrocks> http://10.97.0.1:8080/view/cu2d/view/Head/view/All/job/cu2d-build_all-head/lastSuccessfulBuild/console
[10:03] <sil2100> Then media would have to dep on unity (other way around)
[10:04] <didrocks> it means that you will push unity to the end
[10:04] <didrocks> next to apps
[10:04] <sil2100> True, while the other way around still makes sense
[10:04] <didrocks> this can be fine anyway
[10:04] <didrocks> so let's add the dep as you say
[10:04] <didrocks> unity dep on media
[10:04] <sil2100> ACK
[10:05] <sil2100> It's always such a big thing when trying to fit a project into a stack...
[10:07] <didrocks> yeah, not easy :)
[10:10] <Sweetshark> oh, https://bugs.freedesktop.org/show_bug.cgi?id=67527 is a nice one. It seems gcc produces faulty code from a glib header on 12.04 and thus causes errors in LO. Solution would be to patch the header and recompile everything against glib. Any volunteers?
[10:10] <ubot2`> Freedesktop bug 67527 in Libreoffice "FILEOPEN: LO can't open files over SMB - wants to repair!" [Critical,New]
[10:12] <Sweetshark> for added pleasure, of course this might be the root cause of variuous seemingly unrelated issues on 12.04 too ...
[10:15] <darkxst> pitti, sorry been runnning between computer and fixing bike
[10:27] <Mirv> didrocks: is the lack of a view actually preventing the services stack from running, or is something else needed to avoid "/tmp/hudson8406214369631804361.sh: line 5: cd: /var/lib/jenkins/cu2d/work/head/services: No such file or directory" (http://10.97.0.1:8080/view/cu2d/view/Head/view/All/job/cu2d-services-head/1/console)
[10:28] <Mirv> meanwhile I'm asking on #qa whether someone else could add the view, as jibel is apparently on holiday
[11:05] <didrocks> Mirv: the lack of view shouldn't prevent anything
[11:05] <didrocks> let me have a look
[11:07] <sil2100> Mirv: could you approve this bootstrap? https://code.launchpad.net/~sil2100/mediascanner/bootstrap/+merge/181019
[11:10] <didrocks> Mirv: so I guess "my fault"
[11:10] <didrocks> Mirv: since I reworked the locking system
[11:10] <didrocks> we hadn't the case of a new stack I guess
[11:15] <Mirv> sil2100: soon, before the other ones that are later :) telco.
[11:15] <Mirv> didrocks: ok, good to find out
[11:16] <sil2100> ;)
[11:16] <sil2100> didrocks: can you just give a quick +1 on that bootstrap then? ^
[11:18] <Sweetshark> ricotz: I kinda doubt bug 1214352 will be SRUed to 12.04 -- maybe consider fixing it in the ppa?
[11:18] <ubot2`> Launchpad bug 1214352 in glib2.0 (Ubuntu) "GUINT32/64_SWAP_LE_BE macros do not enclose val argument in parentheses" [Undecided,New] https://launchpad.net/bugs/1214352
[11:19] <didrocks> sil2100: done
[11:19] <sil2100> didrocks: thanks!
[11:20] <didrocks> yw :)
[11:21] <didrocks> Mirv: ok, rev 667 of cupstream2distro-config FYI. I've deployed that on the services stack and rerun it (and it works now)
[11:25] <Mirv> it's green! great.
[11:25] <didrocks> yeah ;)
[11:26] <didrocks> let's hope the rest become green as well :)
[11:26] <Mirv> didrocks: unity-mir removal of private headers dependency http://10.97.0.1:8080/view/cu2d/view/Head/view/Unity8/job/cu2d-unity8-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_unity-mir_0.1+13.10.20130820.3-0ubuntu1.diff
[11:26] <didrocks> Mirv: well, it built, so obviously +1 :p
[11:27] <didrocks> Mirv: I saw your email this morning about webapps, but you didn't mention that apps will be blocked because of it as well, right?
[11:27] <Mirv> didrocks: right, I didn't in the e-mail, only on the status page
[11:28] <didrocks> Mirv: maybe just remember him about it, to avoid the complain "the apps stack didn't run" :p
[11:28] <Mirv> didrocks: ok
[11:28] <didrocks> thx!
[11:49] <Mirv> sil2100: I was just going to write the mediascanner is lacking bootstrap commit, but it seems you've committed that to lp:mediascanner
[11:49] <sil2100> ;)
[11:50] <Mirv> sil2100: copyright has wrong URL, hollywood, should be https://launchpad.net/mediascanner
[11:50] <sil2100> Mirv: good catch! Let me fix that up then
[11:50] <Mirv> sil2100: source/format should be removed according to daily release page
[11:51] <sil2100> Mirv: heh, yes, while cyphermox_ asked me to add it!
[11:51] <sil2100> ;)
[11:52] <Mirv> sil2100: heh, yes I don't think it practically matters, the inlinepackaging page just does that as part of removing all patches
[11:52] <sil2100> Righto
[11:52] <sil2100> Ah, I'll have to change the Vcs'es too
[11:53] <sil2100> Since I changed the owning team
[11:53] <Mirv> sil2100: there's one lintian error (not warning) in unity-scope-mediascanner, otherwise looks good
[11:54] <didrocks> sil2100: Mirv: in fact, as long as it's set to 1.0, not really needed to remove it
[11:54] <didrocks> sil2100: Mirv: more a personal preference choice TBH, just adding consistency :)
[11:55] <didrocks> but 3.0 is wrong as it's creating diffs
[11:55] <didrocks> and not help upstream to just "bzr bd"
[11:56] <sil2100> Mirv: https://code.launchpad.net/~sil2100/mediascanner/final_packaging_fixes/+merge/181028 <- after this is ACKed, we can enable daily-release for mediascanner
[11:57] <sil2100> Which is here:
[11:57] <sil2100> https://code.launchpad.net/~sil2100/cupstream2distro-config/enable_mediascanner/+merge/181027
[11:57] <sil2100> Mirv: thanks!
[12:21] <seb128> Laney, hum, why do you add another plugin for battery?
[12:21] <seb128> Laney, can't we just reuse the current one?
[12:21] <Laney> it's a loader plugin
[12:21] <didrocks> 2 batteries? :p
[12:21] <Laney> I don't think so
[12:21] <Laney> do you see how?
[12:21] <seb128> Laney, what is a "loader plugin"? ;-)
[12:22] <Laney> plugin: foo in the .settings file
[12:22] <seb128> oh
[12:22] <seb128> can't we just get the number of battery in pure qml with qtsystems?
[12:22] <Laney> you have to have cpp for dynamic visibility
[12:22] <seb128> k, that's suboptimal, but if that's the way it is...
[12:23] <seb128> Laney, thanks ;-)
[12:23] <Laney> it's not as easy as it could be
[12:23] <Laney> but the example plugin was quite helpful
[12:23] <seb128> k
[12:34] <sil2100> didrocks: when adding new projects to a stack, do I need to bzr pull on mangers?
[12:35] <didrocks> sil2100: no, magners is only used when touching the stack itself (new stack, new deps)
[12:36] <sil2100> Awesome, ok, thanks!
[12:40] <sil2100> hm, webapps is failing to publish, but it looks fine to publish unity anywa
[12:42] <sil2100> didrocks: btw. packaging change in indicators - I see a switch to cmake, so if it build, I guess it's all fine: http://10.97.0.1:8080/view/cu2d/view/Head/view/Indicators/job/cu2d-indicators-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_indicator-sound_12.10.2+13.10.20130820-0ubuntu1.diff
[12:43]  * sil2100 has a bad day and eats the trailing 's' out of words today
[12:43] <didrocks> sil2100: can you check on the binaries that no .a or .la are shipped?
[12:44] <didrocks> sil2100: if so, +1
[12:46] <sil2100> didrocks: no .la and .a files, publishing
[12:46] <didrocks> thx
[13:01] <sil2100> didrocks: dep-added http://10.97.0.1:8080/view/cu2d/view/Head/view/Apps/job/cu2d-apps-head-3.0publish/lastSuccessfulBuild/artifact/packaging_changes_gallery-app_0.0.67+13.10.20130820.2-0ubuntu1.diff
[13:02] <sil2100> didrocks: ok? ;)
[13:03] <didrocks> sil2100: sounds good
[13:05] <sil2100> didrocks: btw. for re-enabling compiz for daily release, should we do some new bootstrapping commit, or will it pick up the old ones?
[13:05] <didrocks> sil2100: I think you need to shelve the changelog and packaging changes to that branch
[13:06] <didrocks> and readjust the commit id to have stuff we want to list
[13:06] <didrocks> (or none if we don't want to list the diff)
[13:21] <kenvandine> Mirv, hey, looking at qtconnectivity
[13:21] <kenvandine> it would be nice if the qml plugins where versioned, which would require a patch to install them in versioned directories
[13:23] <tedg> seb128, So I'm just catching up via merges... we reverted a 9000 line commit over a few _()'s ?
[13:24] <seb128> tedg, no, we reverted on the thing sigtraping on start for anyone having tb email accounts because of the "imap:" action name
[13:25] <seb128> tedg, e.g ":" in the action name being invalid
[13:25] <tedg> seb128, Ah, okay.
[13:25] <seb128> tedg, that was handled via IRC though that's why it's not showing up into the merge comments
[13:25] <sil2100> didrocks: ok, I'll check the packaging changes - I also added the changelog entries
[13:26] <seb128> tedg, basically http://bazaar.launchpad.net/~indicator-applet-developers/indicator-messages/consolidate/revision/411
[13:26] <tedg> Yeah, I see.  I'm going revision by revision now.
[13:26] <seb128> tedg, basically same issue than http://bazaar.launchpad.net/~indicator-applet-developers/indicator-messages/trunk.13.10/revision/344
[13:30] <sil2100> didrocks: but I guess I'll also have to merge it in manually, since it will take too long for the merge to get in normally...
[13:30] <sil2100> didrocks: there are no packaging changes that need to be pushed besides the changelog
[13:31] <didrocks> sil2100: sure
[13:31] <cyphermox_> sil2100: I think it's better to be explicitly in saying that the package is in format 1.0, rather than expecting people to understand that it's left so on purpose
[13:32] <sil2100> cyphermox_: makes sense
[13:35] <sil2100> didrocks: what would happen if this would get picked up by daily-release? https://code.launchpad.net/~sil2100/compiz/merge_in_changelog
[13:36] <sil2100> didrocks: since the last daily-release commit is long long ago, so hm, should I put some explicit (like the bootstrap) changelog entry with a rev id?
[13:36] <sil2100> didrocks: in the last changelog entry?
[13:41] <didrocks> sil2100: yeah, maybe put an explicit one
[13:41] <didrocks> with a revision
[13:41] <didrocks> in a new changelog entry
[13:41] <didrocks> where you bump the version
[13:41] <sil2100> didrocks: we have one unreleased version with the upstream bump to 0.9.10 - I'll put it there then
[13:42] <didrocks> sounds good
[13:43] <sil2100> I'm still wondering about the rev-id, since I would normally put the rev-id of the last version that has been released to ubuntu in lp:compiz/0.9.10
[13:44] <sil2100> But that's a really old entry it seems
[13:47] <attente> cyphermox_, https://code.launchpad.net/~attente/indicator-keyboard/xdg-runtime-dir/+merge/181042
[13:48] <cyphermox_> attente: nice, I'll re-test now
[13:48] <attente> Laney, i owe you beer
[13:48] <attente> thanks
[13:49] <seb128> attente, so the xdg runtime dir was the issue?
[13:49] <attente> seb128, think so, at least it fixes the problem under sbuild
[13:49] <seb128> great!
[13:51] <cyphermox_> attente: let's fix some small little details with the package too, I'll get you a merge request
[13:52] <Laney> attente: :-)
[13:56] <cyphermox_> seb128: Laney: could one of you please reject indicator-keyboard 0.0.0-0ubuntu19 from the saucy queue? I suspect it should never have ended up there
[13:56] <Laney> not me
[13:57] <seb128> cyphermox_, jbicha uploaded manually, which is why it's there
[13:57] <seb128> cyphermox_, rejected
[13:57] <cyphermox_> seb128: thanks
[13:57] <cyphermox_> I think jbicha wanted to land that in a ppa anyway, from the look of things
[13:58] <seb128> cyphermox_, no, he wanted to land it in the archive, I NEW review it and I would have accepted it if I didn't have comments
[13:59] <cyphermox_> oh, ok
[13:59] <attente> ok, i guess i spoke too soon...
[13:59] <cyphermox_> the package as it is doesn't follow the daily release standards
[14:00] <seb128> cyphermox_, I guess jbicha wanted to get it in not blocking on daily standards
[14:01] <cyphermox_> attente: pass for me...
[14:01] <cyphermox_> did jenkins barf on it?
[14:02] <attente> apparently, armhf c-i
[14:06] <seb128> Laney, do you fell strongly about the refactoring part? I'm not sure how much the code is "duplicated" there...
[14:06] <Laney> the second point?
[14:07] <seb128> "can the repeated copies of this code be factored out?
[14:07] <seb128> "
[14:07] <seb128> Laney, what copies exactly?
[14:07] <Laney> 158 and 176
[14:07] <Laney> one of them has a return though
[14:08] <Laney> so no, I don't care incredibly much but it looks a little bit fiddly
[14:08] <Laney> up to you if you don't want to do it
[14:09] <Laney> you could have a two-line function updateLastFullCharge probably
[14:09] <seb128> right, I'm not sure 2 lines are worth a function
[14:09] <seb128> but I've no strong opinion, I'm happy to do it if you think it's better
[14:09] <Laney> otherwise you have to fix it in two places to change it
[14:09] <Laney> seems nicer to me
[14:10] <seb128> ok
[14:13] <Laney> seb128: should you free item and/or values there too?
[14:13] <Laney> in getLastFullCharge
[14:43] <seb128> Laney, ok, pushed an update, let me know what you think
[14:43] <Laney> ok, shortly
[14:43] <Laney> glibbing now
[14:44] <seb128> sure, no hurry
[14:44] <sil2100> Wow
[14:45] <sil2100> I just branched a LP branch, and in the bzr log I have revisions with 0 < values, like rev -4, rev -12 o_O
[14:46] <seb128> weird
[14:46] <sil2100> seb128: you have a moment? Could you bzr branch lp:ubuntu-ui-extras ? ;) Since on LP it looks ok
[14:49]  * sil2100 wants to know if it's only a problem on his PC
[14:49] <qengho> sil2100: wow.  "bzr revno" says negative?
[14:50] <seb128> sil2100, confirmed here
[14:50] <sil2100> Funny
[14:50] <sil2100> ;)
[14:51] <sil2100> seb128: thanks for confirming
[14:51] <seb128> yw!
[14:51] <qengho> I thought the revno was *calculated*, not stored.  That's weird to see in only one branch.
[15:07] <sil2100> qengho, seb128: not sure what was wrong, but I guess it's stored somewhere - got it fixed by bzr check && bzr reconcile
[15:08] <sil2100> Ah
[15:08] <sil2100> I see what could have caused it
[15:09] <sil2100> This branch was previously ubuntu-ui-extras-initial, and on rev 44 it was renamed to ubuntu-ui-extras, which became the rev 1 for this branch - strange
[15:26] <sil2100> kenvandine, didrocks, cyphermox_: can anyone of you take a look at this packaging review? https://code.launchpad.net/~sil2100/ubuntu-ui-extras/packaging_review/+merge/181075
[15:26] <cyphermox_> ack
[15:27] <sil2100> Thanks! I'll prepare the cu2d-config bits too
[15:30] <seb128> hey
[15:30] <seb128> it's meeting time
[15:31] <mlankhorst> hah
[15:31] <mlankhorst> and hopefully I just finished my mesa 9.2 packaging for debian
[15:31] <seb128> qengho, mlankhorst, Sweetshark, Laney, tkamppeter, attente: hey, it's meeting time
[15:31] <mlankhorst> ;P
[15:31] <qengho> Hi all!
[15:31] <qengho> * Updated packaging for chromium-browser 28.0.1500.95. In distro today.
[15:31] <qengho> * Mostly finished process for translations to/from Launchpad for Cr source and desktop file.
[15:31] <qengho> * Working on plugins to make chromium-browser behave identically to GOOG Chrome.
[15:31] <qengho> EOF
[15:32] <seb128> qengho, hey, did you notice that the new version failed to build on all archs?
[15:32] <qengho> Er, no.  "new version?"  -2?
[15:32] <seb128> yes
[15:33] <qengho> I did not notice that.  Where?
[15:33] <seb128> qengho, => Found differences, please investigate. /tmp/built-1118 /tmp/packaged-1118
[15:33] <seb128> qengho, https://launchpadlibrarian.net/147942239/buildlog_ubuntu-saucy-amd64.chromium-browser_28.0.1500.95-0ubuntu2_FAILEDTOBUILD.txt.gz
[15:33] <seb128> https://launchpad.net/ubuntu/+source/chromium-browser/28.0.1500.95-0ubuntu2
[15:34] <seb128> qengho, well, anyway, please have a look
[15:34] <seb128> qengho, thanks
[15:34] <seb128> mlankhorst, hey
[15:35] <ritz_> hi, is the irclog bot dead, wrt - http://irclogs.ubuntu.com/2013/08/10/%23ubuntu-desktop.txt ?
[15:35] <ritz_> and http://irclogs.ubuntu.com/2013/08/17/%23ubuntu-desktop.txt
[15:35] <seb128> ritz_, hey, we are in a meeting, and I don't know we don't maintain the bot ... ask on #ubuntu-devel maybe?
[15:36] <Laney> those are weekends
[15:36] <mlankhorst> I've been working on mesa 9.2 all day, fixed llvm 3.3 issues. Proposed some kernel patches upstream. Tested mesa 9.1.4 for raring last week, uploaded mesa 9.1.6 to saucy.
[15:36] <seb128> ritz_, but the days you showed are saturdays
[15:36] <Laney> seems likely it is correct
[15:36] <mlankhorst> erm pretty much it for me
[15:36] <seb128> mlankhorst, thanks
[15:36] <seb128> Sweetshark, hey, welcome back
[15:36] <Sweetshark> - waded through backlog http://devopsreactions.tumblr.com/post/57051683487/dealing-with-your-6-months-old-backlog
[15:36] <Sweetshark> - uploaded 4.0.5~rc2 for PPA, currently building https://launchpad.net/~bjoern-michaelsen/+archive/libreoffice-staging/+builds?build_state=building , upstream releases ~this week https://wiki.documentfoundation.org/ReleasePlan/4.0#4.0.5_release
[15:36] <Sweetshark> - saucy/LibreOffice 4.1 - synced from debian - unfuzzed patches - massaged LibreOffice for boost multiarch (which I assume made LO ftbfs just 3 days after package was uploaded for the poppler-transition, which would have made it ftbfs too, so just the usual lifetime ;) ) - preparing tarballs for 4.1.1~rc1 right now
[15:36] <Sweetshark> EOF
[15:36] <mlankhorst> oh we missed all the libreoffice talk
[15:37] <ritz_> seb128, thanks. I am an idiot. I was looking at sept cal
[15:37] <Sweetshark> we should measure the mean-time-between-someone-break-LO ...
[15:38] <seb128> Sweetshark, thanks
[15:38] <seb128> Sweetshark, you still have SRUs waiting for sponsoring right?
[15:38] <Sweetshark> seb128: yes, a 4.0.4 SRU for raring and a 3.5.7 SRU for precise
[15:38] <seb128> Sweetshark, ok, I'm going to try to review those this week
[15:38] <seb128> Sweetshark, thanks
[15:38] <seb128> Laney, hey, welcome back!
[15:39] <Laney> bonjour mes amis
[15:39] <Laney> • Very short week due to holidays & debconf (back to work from today)
[15:39] <Laney> • Before this I was working on updating GStreamer to 1.1 in a PPA for some touch work https://launchpad.net/~ubuntu-desktop/+archive/gstreamer-1.1
[15:39] <Laney> • Segfaults in gst-codec-info-1.0; back with (our) upstream now
[15:39] <Laney> • Today I proposed a patch to make the battery panel in system-settings have dynamic visibility - the first example of such in s-s
[15:39] <Laney> • Working on updating glib to 2.37.6; test failure on kbsd from .5 to look into a bit
[15:39] <Laney> END
[15:41] <seb128> Laney, thanks!
[15:41] <seb128> tkamppeter, hey
[15:42] <tkamppeter>  - cups-filters upstream work
[15:42] <tkamppeter>  - Tested MIR on the Lenovo Thinkpad Twist and reported bugs
[15:42] <tkamppeter>  - Bugs
[15:42] <tkamppeter>  - GSoC
[15:42] <tkamppeter>  - Linked Touchscreen- and convertible-relevant bugs to Blueprint about convertible support.
[15:42] <seb128> tkamppeter, thanks
[15:42] <seb128> attente, hey, welcome back as well
[15:43] <seb128> not around? I guess it's late for him since he's still in China
[15:43] <attente> seb128, hi
[15:44] <seb128> cyphermox_, do you know if the fixes for keyboard worked?
[15:44] <seb128> attente, hey!
[15:44] <attente> seb128, c-i still failed
[15:44] <attente> i wasn't able to see the output since jenkins is down though
[15:44] <seb128> right...
[15:45] <seb128> attente, do you have the merge request/CI url?
[15:45] <attente> i'm really not sure what options we'll have given that FF is soon
[15:46] <attente> https://code.launchpad.net/~attente/indicator-keyboard/xdg-runtime-dir/+merge/181042
[15:46] <attente> i guess it was manually approved?
[15:47] <seb128> attente, http://10.97.2.10:8080/job/indicator-keyboard-saucy-armhf-ci/15/console if you have access to the qa vpn
[15:47] <seb128> attente, http://paste.ubuntu.com/6006869/
[15:48] <seb128> attente, seems like a new issue/different from what we had before?
[15:48] <attente> seb128, yep, that's new
[15:48] <seb128> good, maybe a real bug this time :p
[15:49] <attente> ha, i hope so
[15:49] <seb128> attente, you can use porter-armhf.c.c if you need debugging on arm
[15:50] <seb128> attente, still some time before ff but it would be nice to get that landing tomorrow
[15:50] <seb128> attente, thanks
[15:50] <attente> thanks seb128
[15:50] <seb128> attente, you should call it a day, but let's talk about that tomorrow european morning
[15:50] <attente> ok
[15:50] <seb128> did I forget anyone? (trying to skip those on holidays)
[15:51] <kgunn> mlankhorst: just curious...do you know of any ati related changes (of significance) that might have come on with the 3.11 kernel ?
[15:51] <seb128> other my week was short, one national holiday and one day off in Berlin to hang around ... I working on the system settings battery panel mostly otherwise
[15:51] <seb128> started on the location one as well
[15:51] <seb128>  
[15:51] <mlankhorst> mir fixes, ww_mutex changes, dpm support
[15:51] <seb128> that's it I think
[15:51] <mlankhorst> maybe uvd fixes
[15:52] <seb128> does anyone has other topic/questions?
[15:52] <seb128> or I forgot ... if anyone has topics they would like registered at vUDS, please register blueprints and ping me with the link
[15:53] <kgunn> tvoss: interesting....from mlankhorst : kernel changes include ww_mutex changes
[15:54] <Sweetshark> seb128: I got suggested to write a blueprint "make LibreOffice releases more rolling" ;)
[15:54]  * Sweetshark graps popcorn.
[15:54] <seb128> haha
[16:00] <didrocks> cyphermox_: sil2100: Mirv: Hey guys, how are you?
[16:00] <didrocks> meeting time!
[16:01] <Mirv> o/
[16:01] <didrocks> (short meeting as kenvandine is busy in another meeting and robru is travelling)
[16:01] <sil2100> o/
[16:01] <sil2100> Busy!
[16:01] <Mirv> feeling the upcoming feature freeze
[16:01] <didrocks> it's a nice warm of "OMG" feeling, isn't it? :)
[16:01] <Mirv> every request seems urgent and every day there are multiple requests
[16:01] <didrocks> Mirv: yeah, and people think they are the only one in the world… :p
[16:02] <didrocks> we all share the same experience it seems! ;)
[16:02] <Mirv> didrocks: :)
[16:02] <didrocks> https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AuDk72Lpx8U5dHFtUmlPOUtCRk8zR2dtaEpIbUVhMmc#gid=0
[16:02] <didrocks> maybe let's look at the current stack?
[16:02] <didrocks> it's cyphermox_'s run right now, isn't it?
[16:03] <sil2100> OMG Ubuntu!
[16:03] <didrocks> indicators was reverted, isn't it sil2100? can we move that in non blocking release?
[16:03] <cyphermox_> in two hours
[16:03] <sil2100> didrocks: right, left it there so that it's nicely noticable
[16:03] <didrocks> cyphermox_: ah, still free :)
[16:03] <Mirv> mysteriously webapps got a run without autopilot test errors, without code changes. let's see if that continues
[16:03] <cyphermox_> barely... quite busy with touch stuff
[16:03] <didrocks> sil2100: but it's not "really" blocking? let's keep on the right and have the right cleaned?
[16:04] <didrocks> Mirv: urgh, ok :/
[16:04] <sil2100> Ok
[16:04] <didrocks> cyphermox_: yeah, everything it touch! :)
[16:04] <sil2100> ;)
[16:04] <didrocks> sil2100: flacky indicators/unity tests, bregma's team is on it?
[16:05] <sil2100> didrocks: they got informed about it, but there are some other more priority things like the compiz unit tests, so they'll work on it after that
[16:05] <didrocks> sil2100: ok
[16:05] <didrocks> Mirv: is https://bugs.launchpad.net/qtubuntu/+bug/1212131 still valid?
[16:05] <ubot2`> Launchpad bug 1212131 in qtubuntu "Double dh_auto_configure in debian/rules" [Undecided,New]
[16:05] <didrocks> (let's try to clean this dashboard) :)
[16:06]  * sil2100 quickly removed one invalid entry ;)
[16:06] <didrocks> (shhhh ;))
[16:06] <Mirv> didrocks: still valid
[16:06] <didrocks> Mirv: can you just handling it? (tomorrow?) seems easier than waiting on them
[16:06] <didrocks> as it seems removing a line is taking a week :p
[16:06] <Mirv> didrocks: true, I'll do that
[16:06] <didrocks> Mirv: thanks!
[16:07] <didrocks> for mir/mirslave: FYI, just tried with latest kernel with tvoss|afk
[16:07] <didrocks> we tried both mir in distro
[16:07] <didrocks> and latest mir branch
[16:07] <didrocks> can't reproduce anymore
[16:07] <didrocks> I think we'll blame the kernel after all
[16:07] <sil2100> Oh shit
[16:07] <didrocks> and reenable mir
[16:07] <sil2100> That's good news!
[16:07] <didrocks> (more than 20 shutdown/reboot)
[16:07] <Mirv> hmm
[16:07] <didrocks> yeah, not found of not understanding exactly though
[16:08] <didrocks> so the deal is:
[16:08] <didrocks> - reenabling tomorrow morning
[16:08] <didrocks> (I'll do it)
[16:08] <didrocks> - I'll reenable the ATI machine as well for all tests
[16:08] <didrocks> - if we have any Mir hanging issue
[16:08] <didrocks> deprovisionning the ATI machine right away
[16:08] <didrocks> and not upgrading it at all
[16:08] <didrocks> (keep it as it is)
[16:09] <didrocks> let's cross fingers we won't need that :)
[16:09] <sil2100> ;)
[16:09] <didrocks> how is the 4h dailies going for everyone?
[16:11] <Mirv> it's working nicely
[16:11] <sil2100> Not bad, I must say that in some regard is good, but when not everyone is around it's also a bit more busy
[16:11] <didrocks> yeah, for sure, though we have less to treat everytime
[16:11] <sil2100> Indeed
[16:11] <sil2100> And!
[16:11] <didrocks> and we have a constant "ping" mecanism now and share infos :)
[16:11] <sil2100> When there's no dedicated core-devs to ping about pkging ACKs, it's terrible
[16:12] <didrocks> did you try on #ubuntu-devel?
[16:12] <sil2100> ;)
[16:12] <didrocks> on not getting anyone ressponding?
[16:12] <sil2100> Yes, but usually people were busy, so we were abusing ogra_ and some other guys
[16:12] <didrocks> ogra_ likes being abused :p
[16:12] <sil2100> ;)
[16:12] <cyphermox_> sil2100: we can make time for packaging review
[16:13] <ogra_> yeah, bring your whip
[16:13] <Mirv> :)
[16:13] <didrocks> he's the one wanted stuff as fast as possible to the iso
[16:13] <didrocks> he has to pay for it! :p
[16:13] <ogra_> ++
[16:13] <didrocks> but nice work on transitionning to this daily release model Mirv, sil2100, cyphermox_, kenvandine!
[16:13] <didrocks> ah, just one thing
[16:14] <didrocks> I heard that nobody knew how to refresh the whitelist
[16:14] <didrocks> (on Friday)
[16:14] <didrocks> it's on the famous Daily release FAQ page of course!
[16:14] <Mirv> yeah, or there was some problems like first not finding it on FAQ
[16:14] <Laney> the branch on lillypilly?
[16:14] <didrocks> https://wiki.ubuntu.com/DailyRelease/FAQ#Adding.2BAC8-removing_components_to_a_stack
[16:14] <didrocks> yeah
[16:14] <Mirv> and then not finding a person willing to execute according to it
[16:14] <Laney> it says something vague like "review the changes"
[16:14] <didrocks> "The archive admin needs to, after checking that lp:cupstream2distro only adds component for filtering we want:
[16:14] <Laney> and there were like 50 commits
[16:14] <didrocks> "
[16:14] <didrocks> Laney: you need to look at all the new components added and if they make sense, that's the only way
[16:15] <Laney> it is not really possible for someone unfamiliar to review that
[16:15] <didrocks> Laney: want that we walk across that tomorrow together?
[16:15] <didrocks> Laney: you will maybe have a better way of wording/helping that
[16:16] <Mirv> didrocks: you could maybe talk with a couple of arch admins that would be then prepared to handle our requests / know about the thing in your absence. then we would have a few persons to select from.
[16:16] <Mirv> I think randomly contacting and without them being able to consult with you may result in reluctance to "blindly" pull
[16:16] <Laney> have a look at 'bzr diff -r 608' in that branch
[16:16] <didrocks> Mirv: yeah, will do, but cjwatson is on holidays, not sure who else is active and close enough
[16:16] <Laney> there's no way I could have known what all of that stuff means
[16:16] <didrocks> Laney: well, I know, we do work!
[16:17] <didrocks> Laney: we can try to find a pattern or a command
[16:17] <didrocks> Laney: want that we spend some time on that together tomorrow? ideas gathering will be nice
[16:17] <didrocks> (most of the time, I know exactly what's in as I'm looking at all MP, so not that a biggie to me, an external eye is always better)
[16:18] <Laney> can do if you like
[16:18]  * didrocks notes down
[16:18] <Laney> like just the fact that it was 50 revisions behind was scary in itself
[16:18] <didrocks> Laney: look at the dates, not that old :)
[16:19] <didrocks> 10 commits in 2 days
[16:19] <Laney> yes I see there's a lot of traffic in there
[16:19] <didrocks> 50 revision is a week
[16:19] <Laney> anyway it'll come down to 'document the configuration file formats' ;-)
[16:19] <Laney> so that people who don't do this stuff know how to tell if things are ok
[16:19] <didrocks> Laney: I think we can have a wrapper making a diff
[16:19] <didrocks> but let's discuss that tomorrow
[16:20] <didrocks> ok, so now on the spreadsheet
[16:20] <didrocks> Mirv: anything you are waiting on, that needs noticing?
[16:20] <didrocks> (I think you are hard working in particular on Qt 5.1 for FF)
[16:21] <Mirv> didrocks: just the ones I'm waiting on, although Ken had something to add to qtconnectivity apparently (versioning the plugin)
[16:21] <Mirv> didrocks: trying to prepare 5.1(.1), yes, although there are the blocker bugs out of my hands as well
[16:22] <didrocks> ok, do you need some help for pushing the other teams trying to get stuff sorted?
[16:22] <Mirv> today merged 5.0.2 branch changes back to 5.1 branch and tried a snapshot 5.1.1 build of qtbase to be ready, apparently 5.1.1 will be released on Thursday
[16:22] <didrocks> an nice, at least the branch are up to date :)
[16:22] <didrocks> great news \o/
[16:22] <sil2100> /o/
[16:23] <Mirv> didrocks: well sort of getting even the info "yes we are pushing for Qt 5.1 in saucy before FF" would be news, and then getting https://bugs.launchpad.net/bugs/+bugs?field.tag=qt5.1 fixed - I've one patch from kaleo now that I try to bring for testing
[16:23] <didrocks> ok, so still some issues to get fixed
[16:23] <didrocks> I'll do some pinging tomorrow
[16:23] <didrocks> thanks Mirv
[16:23] <didrocks> sil2100: anything special to mention?
[16:23] <Mirv> there's so much to do with Qt that I just to prepare beforehand for the craziness when people suddenly ask "hey 5.1.1 just came out, is it in saucy archives yet?" ;)
[16:23] <Mirv> didrocks: thanks
[16:23] <didrocks> sil2100: it seems you can close the indicators line ;)
[16:24] <didrocks> Mirv: "it's released for 1.5 hours! what are you doing?"
[16:24] <didrocks> :)
[16:24] <sil2100> Not much, we enabled mediascanner for daily-release, same for ubuntu-ui-extras - the SDK stack needs to be redeployed with the new changes, once those get merged
[16:24] <Mirv> I could close the 'services stack' thing if I just have an own note about contacting jibel when he's back
[16:24] <sil2100> I didn't yet since there are still some merges to ubuntu-ui-extras that I want to land
[16:24] <sil2100> Which are approved
[16:25] <didrocks> Mirv: it's fine if you want to duplicate the line just for that one
[16:25] <didrocks> I'll only archive tomorrow then
[16:25] <didrocks> cyphermox_: anything to share?
[16:25] <cyphermox_> no
[16:25] <cyphermox_> well
[16:26] <Mirv> ok, did that
[16:26] <cyphermox_> indicator-keyboard fails CI on armhf, going to need to look into that
[16:26] <didrocks> cyphermox_: indicator-keyboard? it seems that you work on that?
[16:26] <didrocks> ok
[16:26] <cyphermox_> work is a large word
[16:26] <didrocks> attente: is looking as well, right?
[16:26] <cyphermox_> I have to finish fixing a bug in NM first and foremost
[16:27] <didrocks> ok, then on that one I guess (or rather the next one first)
[16:27] <didrocks> I visited this morning http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html
[16:27] <didrocks> and I saw that we start to have some packages stuck there
[16:27] <didrocks> cyphermox_: libcolumbus blocked in proposed
[16:27] <didrocks> can you try to have it moving for tomorrow? ^
[16:27] <cyphermox_> yeah
[16:27] <didrocks> thanks
[16:27] <cyphermox_> things need to start using it, there's no excuse iirc
[16:28] <Mirv> and libhud-qt is blocked on the fact that it used to build on powerpc
[16:28] <didrocks> sil2100: you did mediascanner :)
[16:28] <didrocks> cyphermox_: hum, it's blocking for a reason, even if there is no build-dep
[16:28] <didrocks> Mirv: oh, you already looked!
[16:28] <sil2100> didrocks: yes, it's fixed in the trunk
[16:28] <didrocks> Mirv: so we need to revert on hardcoded lines
[16:28] <sil2100> So if we release mediascanner, it should be ok
[16:28] <Mirv> didrocks: look is a big word :)
[16:28] <didrocks> kenvandine: same for you: signon-plugin-oauth2/signon-ui blocked in proposed
[16:28] <didrocks> Mirv: tssss ;)
[16:29] <didrocks> kenvandine: as it released once on powerpc, I think you need to remove the arch: any and specify the archs
[16:29] <didrocks> Mirv: ok, let's deal with that tomorrow, should be easy
[16:29] <Mirv> didrocks: yes, probably, my only other thought was that if it had begun to depend on something that doesn't work on powerpc
[16:29]  * didrocks will get pinged in the morning it seems :p
[16:30] <didrocks> looking at http://people.canonical.com/~ubuntu-archive/proposed-migration/update_output.txt help
[16:30] <sil2100> didrocks: if you don't mind, I would like to spend some time tomorrow (at least a few hours) for some appmenu-qt5 coding - you think it would be ok? ;) *needs some coding*
[16:30] <didrocks> a bit raw
[16:30] <didrocks> but most of the time, when something is "valid candidate" on one line
[16:30] <didrocks> the issue is listed on the other one ^
[16:30] <didrocks> sil2100: sure, I don't see any incoming crisis
[16:30] <didrocks> well… I enable Mir
[16:30] <Mirv> oh right any should probably fix it like with others
[16:31] <didrocks> but normally, should be fine :)
[16:31] <kenvandine> didrocks, grrr
[16:31] <kenvandine> ok
[16:31] <didrocks> Mirv: I think so. just list everything but powerpc
[16:31] <didrocks> kenvandine: as well ^
[16:31] <didrocks> thanks Mirv, kenvandine :)
[16:31] <didrocks> ok, any question?
[16:32] <didrocks> (on my side, in addition to Mir, I'm trying to finish the system update as fast as possible)
[16:32] <didrocks> FYI ^
[16:32] <didrocks> ok, seems no question!
[16:32] <didrocks> have a good week everyone
[16:32] <sil2100> ;)
[16:32] <didrocks> as a reminder, I won't be there next week and the week after
[16:32] <sil2100> Thanks, same to you!
[16:32] <sil2100> :<
[16:32] <Mirv> didrocks: right so let's back to it tomorrow, but the thing is that it's currently tri-arch in control file
[16:32] <sil2100> ;)
[16:32] <didrocks> but I'll think about you from the beach ;)
[16:32] <Mirv> didrocks: thanks to you!
[16:33] <Mirv> didrocks: haha :)
[16:33] <didrocks> Mirv: yeah, let's discuss that tomorrow morning :)
[16:38] <kenvandine> didrocks, ditto for signon-ui
[16:38] <didrocks> kenvandine: yeah, IIRC, it was the ones I patched
[16:38] <kenvandine> we fixed this in the past, that's how the last version got promoted
[16:38] <didrocks> kenvandine: but then, reverted apparently
[16:38] <kenvandine> humm
[16:39] <didrocks> because we thought "it's not in latest version"
[16:39] <kenvandine>  signon-ui | 0.14-0ubuntu2 |         saucy | powerpc
[16:39] <kenvandine>  signon-ui | 0.15daily13.06.12-0ubuntu1 |         saucy | source, amd64, armhf, i386
[16:39] <kenvandine> and there is a later in -proposed
[16:39] <didrocks> yeah, and I'm sure it's seeing signon-ui | 0.14-0ubuntu2 |         saucy | powerpc
[16:39] <didrocks> so waiting on powerpc
[16:39] <kenvandine> yeah, so was that what was reverted?
[16:39] <didrocks> kenvandine: just relist the archs, I'm afraid
[16:39] <didrocks> it was
[16:39] <kenvandine> i thought that got deleted?
[16:39] <didrocks> arch: i386 amd64 armhf arm64
[16:39] <kenvandine> didrocks, the arches are listed
[16:39] <didrocks> and it changed to:
[16:40] <didrocks> arch: any
[16:40] <didrocks> really?
[16:40] <kenvandine> yeah
[16:40]  * didrocks branches
[16:40] <didrocks> kenvandine: urgh, indeed
[16:40] <kenvandine> Architecture: amd64 i386 armhf
[16:40] <didrocks> I have no idea then :(
[16:40] <didrocks> Laney: ^
[16:40] <kenvandine> we fixed this before :)
[16:40] <Laney> what is up?
[16:41] <Laney> you have to make the old binary package go away
[16:41] <kenvandine> same for signon-plugin-oauth
[16:42] <Laney> I thought we were just letting stuff fail to build rather than listing the arches
[16:42] <didrocks> Laney: for most of the things yeah, but colin couldn't do that for those IIRC because they build (with qt4) in the past
[16:43] <didrocks> Laney: and he couldn't delete, but don't remember exactly why
[16:43] <didrocks> so the only way was to list for those for now
[16:43] <Laney> it doesn't help
[16:44] <kenvandine> they got promoted for the specific arches in the past, i thought he had deleted them
[16:44] <Laney> but how did saucy get 06.12?
[16:44] <kenvandine> colin did that somehow
[16:44] <kenvandine> i thought he deleted the ppc
[16:44] <Laney> he forced it
[16:44] <kenvandine> but i guess not
[16:45] <kenvandine> seb128, do you remember the story there?
[16:46]  * seb128 reads backlog
[16:47] <Laney> I think there was a problem with empathy
[16:47] <kenvandine> that rings a bell
[16:47] <kenvandine> i don't recall the plan though
[16:48] <Laney> laney@iota> reverse-depends -a powerpc src:signon-ui                                                    ~/dev/canonical/release/hints-ubuntu
[16:48] <Laney> Reverse-Recommends
[16:48] <Laney> [16:48] <Laney> * signond                       (for signon-ui)
[16:48] <Laney> Reverse-Depends
[16:48] <Laney> [16:48] <Laney> * signon-plugin-oauth2          (for signon-ui)
[16:48] <Laney> oauth2 will need removing too
[16:49] <kenvandine> yeah, there is a new version that specifies the arches for that too
[16:50] <seb128> kenvandine, I don't remember the specifics
[16:50] <seb128> and Colin is not there this week
[16:51] <Laney> AFAICS you are safe to remove them both
[16:52] <seb128> Laney, should I just delete those binaries on ppc, is that what you say?
[16:52]  * seb128 is a bit loss
[16:57] <Laney> seb128: yeah, from those two source packages
[16:57] <Laney> there might be a problem with account-plugin-tools
[17:02] <seb128> Laney, kenvandine: deleted them, let's see
[17:02] <kenvandine> thanks